Ligder Gazette
Governance, LITE, forums & Liteboards
A paper on how Ligder ties a Solana token to an oldschool forum—wallet-native identity, stake-weighted voice, on-chain attestations where we relay them, per-token Liteboards for pump.fun communities, and a stack you can read and fork.
Ligder pairs a governance token (LITE) with a stratified forum—think bitcointalk with wallets. You register with a single sign message; we read your LITE balance on-chain and show it on your profile and beside your posts. The forum is not flat: casual boards stay open; governance and treasury-facing discussion sit behind thresholds. Separately, Liteboards attach a small two-channel forum (announcement + general) to any pump.fun–listed SPL mint you verify and deploy, so each token community can host discussion beside the main Ligder boards. Where we relay them, new threads and replies are attested on Solana Memo so hashes can be checked against what you see; full bodies stay in the database for speed and search. Nothing here is meant to be opaque: the repo is public, and the dividend-claim path for pool fees is there for anyone to verify.
- Network: Solana
- Governance token: LITE (mint configured in deployment)
- Identity: Phantom (or compatible) wallet + optional username registration
- Forum: Sections, boards, markdown, per-board minimum rank for threads/replies
- Liteboards: Optional mini-forums per pump.fun token mint (owner + registered users)
- Code: Open source—fork, tune config, ship your own deployment
I. Why a forum
Back in 2013, many of us had one thing: a forum and an idea. No roadmap theatre—just people arguing, disagreeing, and building. Ligder is that spirit on Solana: your wallet is your identity, and your LITE balance is how much weight you carry in the room. The more you hold, the more representable you are in the tiers that matter for governance—not in a backroom, but in threads and votes that line up with what the chain already knows about commitment.
II. Registration & balance
Registration uses a sign message flow—no custody, no broad token permissions beyond what you approve for that signature. The app reads your LITE balance on-chain and stores it with your profile; that balance appears under your posts so alignment is visible. We do not ask for your other assets or your keys; we show what the chain shows for LITE.
III. Forum structure
Boards are grouped into sections (official, general, technical, governance, and so on). Each board can set minimum LITE holdings to start threads or to reply. Post voting (up and down) lives with the forum data model. Governance-heavy and treasury-facing rooms stay behind thresholds so casual discussion stays cheap while serious decisions meet a higher bar.
The live board list and rules are always those shown in the app under Forums.
IV. Liteboards
Liteboards are a second layer of discussion: small, mint-keyed forums for individual
tokens—without replacing the main Ligder forum. Deploy is self-serve for tokens that appear
on pump.fun (we verify the mint against their public index and related checks). After you
prove control of the mint workflow and register on Ligder, you can create a board at
/liteboard/<mint> with exactly two channels:
- Announcement
- Owner-only: the wallet that deployed the Liteboard may start threads here—suitable for official project updates, same spirit as Ligder Official megaphone-style boards.
- General
- Any registered Ligder user may participate—community chat in the spirit of Ligder General, but scoped to that token’s page.
Market cap and implied per-token figures shown on the hub and explorer come from pump.fun
metadata where available (for example implied $/token from their market-cap convention). The
Liteboard Explorer lists boards, sorts by activity or market cap, and
supports search by mint. Deploy lives at Deploy a Liteboard. Liteboard
threads and posts are stored in their own tables and APIs; they do not use the same forum_boards
slug model as the main forum, but the experience—sign to post, registered identity—is aligned.
Not every SPL mint qualifies: other launchpads and arbitrary mints may be excluded until the same class of verification exists. Treat the in-app deploy screen as the source of truth.
V. On-chain attestations & archive
Where the stack relays them, new threads and replies are attested on-chain via Solana Memo (hashes align with what you read in the UI). Full post bodies remain in the database for latency and search. The Archive & Verify flow is there so anyone can compare chain commitments with forum content. If something does not match, you can see it—not because we promise perfection, but because the design assumes verification.
Liteboard posts are not necessarily relayed through the same Memo pipeline as main-forum posts; check the implementation for the current behavior.
VI. Fees, dividends & verification
Liquidity-pool fees flow into a dividend-claim system: the plumbing is in the repo so holders and auditors can trace how pool fees become claims for LITE holders. Treat every number in the UI as something you can reconcile against on-chain configuration and the published code—not as a marketing curve.
VII. What we do not claim
Ligder is experimental software. Token price, liquidity, and third-party infrastructure are outside this document. Nothing here is investment, legal, or tax advice.
- Smart contracts and deployments can have bugs; audits do not guarantee safety.
- Governance outcomes depend on participation and on-chain reality, not this HTML file.
- RPC endpoints, wallets, and bridges can fail or behave unexpectedly.
- Liteboard eligibility and pump.fun listings depend on third-party services and policy; they can change.
VIII. Conclusion
Ligder is a toolkit for communities that want to own governance: no VC carve-out, no team allocation story in this design—just holders, a forum, optional per-token Liteboards for aligned communities, and code you can inspect. The Gazette is not a contract; it is orientation. If the implementation drifts, the repository and the chain win over this page.
Ship honestly. Argue in public. Let the chain and the repo be the referee.
Links
Ligder home · Forums · Archive & Verify · Liteboard Explorer · Deploy Liteboard
Source code: see the project repository for contracts, API, and frontend.