Community Voting

Lester Gov

Snapshot-style governance planning for LitVM communities. Draft proposals, set clear snapshots, and keep execution separate from voting.

VotingOff-chain

StyleSnapshot

ExecutionManual review

CostNo vote gas

Legacy on-chain governance is read-only. Its token ownership and timelock admin/canceller roles remain tied to the compromised controller, and the deployed Governor has no executable path. Voting, proposals, queueing, execution, and governance-token delegation stay blocked until a distinct, independently reviewed token/Governor/timelock set and exact runtime hashes are source-pinned.

Mainnet recommendation: Snapshot-style off-chain voting

Lester Labs is standardising on an off-chain, signature-based governance workflow for community voting. The website now reflects that safer model instead of offering placeholder on-chain proposal and vote actions.

Snapshot-style

Lester Core

lester-core

Protocol-wide signalling for treasury policy, product priorities, and governance standards.

Per-project

Launchpad Projects

project-spaces

Each launch can run its own token-holder vote with a clear forum thread and fixed balance snapshot.

Human review

Execution Track

manual-execution

Passed votes are executed manually by the responsible team or multisig after public review.

Operating Standard

Use the governance page to prepare proposals and explain the voting flow. Publishing, signature collection, and execution remain intentionally separate until the full Snapshot/IPFS pipeline is shipped.

Publish the proposal text in a forum thread or project announcement channel before opening the vote.

Set a clear balance snapshot so holders know exactly when voting power is measured.

Keep choices simple: For, Against, and Abstain unless the proposal genuinely needs multiple options.

Treat the result as signalling until the execution transaction or multisig action is posted publicly.