Governance
DAO & Voting
SIGNS token holders govern the protocol through on-chain-verified, off-chain snapshot voting. Proposals cover treasury, protocol, and community decisions. Every vote is wallet-signed, publicly verifiable, and binding on the team.
5
days
Voting window
2
days
Execution window
5%
of snapshot supply
Quorum threshold
>50%
of weighted votes
Pass threshold
What we built
Rather than relying on a third-party protocol like Realms, Signs Club built its own governance layer directly into the platform. This means we own the full stack. Every proposal, vote, snapshot, and execution record lives in our own database and is verifiable by any community member.
V1 uses a trusted off-chain model: votes are cryptographically signed by your Solana wallet and stored alongside the signature. The team cannot forge votes. Trustless on-chain verification is planned for V2.
Who Can Submit a Proposal
Proposal submission requires meaningful skin in the game. Not everyone can open a vote.
Team
The Signs Club team wallet can always submit proposals, regardless of balance. This covers operational decisions that require a quick community vote.
Community
Any wallet holding at least 5,000,000 SIGNS can submit a proposal. This threshold keeps governance signal-to-noise high. The threshold itself is adjustable by future proposal.
To submit a proposal, connect your wallet and visit /dao/propose. If your wallet is eligible, the form will load. Proposals are reviewed before activation, they do not go live immediately.
Proposal Lifecycle
Every proposal moves through the same six stages from submission to execution.
Proposal submitted
An eligible wallet submits a title, summary, body, and category. The proposal is saved as a Draft.
Team review
The team reviews the draft for completeness. No edits are made without the author's knowledge.
Snapshot & activation
The team activates the proposal. At the exact moment of activation, Helius DAS captures every SIGNS holder's balance. This snapshot is immutable. Wallets that buy in after activation are not eligible.
Voting window (5 days)
Eligible wallets connect, sign a vote message with their Solana wallet, and submit. Each wallet can vote once. Votes are weighted by the balance captured at snapshot time, subject to the 5% per-wallet cap.
Auto-close & tally
When the voting deadline passes, an automated process tallies votes and resolves the proposal to Passed, Failed, or No Quorum. Results are immediately public.
Execution window (2 days)
If passed, the team has 2 days to execute the decision via Squads multisig. The Solana transaction hash and any execution notes are recorded on the proposal.
Proposal Statuses
A proposal badge tells you exactly where it sits in the lifecycle.
Proposal has been submitted and is under review. Only visible to the team. Voting has not opened.
Voting window is open. The token snapshot has been taken and eligible wallets can cast their vote.
Quorum was met and more than 50% of weighted votes chose the winning option. Awaiting team execution.
Quorum was met but the proposal did not reach a majority. No action will be taken.
Fewer than 5% of the total snapshot supply cast votes. The result is non-binding.
The team has carried out the decision on-chain and recorded the transaction hash.
Voting Mechanics
Votes are weighted by SIGNS holdings. The system is designed to prevent any single wallet from swinging an outcome unilaterally.
Snapshot at activation
The moment a proposal is activated, every SIGNS token account on Solana is queried via Helius DAS. The resulting list of wallets and balances is frozen and stored. Tokens transferred after this point do not affect voting weight for either side.
Token-weighted votes
Each wallet's raw token balance from the snapshot becomes its vote weight. A wallet with 10,000,000 SIGNS carries 10× the weight of a wallet with 1,000,000 SIGNS.
5% Per-Wallet Cap
No single wallet can exceed 5% of the total snapshot supply in effective vote weight, regardless of raw balance.
effectiveWeight = min(rawBalance, snapshotTotal × 0.05)Quorum & pass threshold
How to Cast a Vote
Voting requires your Solana wallet. No gas, no transaction. The signature is the vote.
Connect your wallet
Open the DAO portal and connect the wallet that held SIGNS at the time the proposal was activated. If your wallet was not in the snapshot, you will see a notice that voting is not available.
Select your choice
Most proposals offer Yes / No / Abstain. Some proposals may have additional custom options defined by the author.
Sign the vote message
Your wallet signs a short message that encodes the proposal ID, your choice, your wallet address, and a timestamp. This is a free off-chain signature. It never hits the blockchain and costs no SOL.
Submission
The signed message is submitted to the server, which verifies the Ed25519 signature against your public key, confirms you are in the snapshot, and records your vote. Double-voting is not possible. Each wallet can only vote once per proposal.
Votes cannot be changed after submission. Signatures include a 5-minute timestamp window to prevent replay attacks. If you leave the vote modal open for too long, you will need to re-sign.
Execution
When a proposal passes, the team is responsible for carrying it out. The 2-day execution window begins the moment voting closes.
On-chain execution via Squads
Passed proposals are carried out through the Signs Club Squads multisig, the same treasury management system used for all fund movements. Execution requires multiple team signers. No single team member can act unilaterally.
Transaction recorded on the proposal
Once the on-chain action is complete, the team records the Solana transaction hash and any execution notes directly on the proposal. The proposal status changes to Executed. Every holder can verify the action on-chain using the recorded hash.
Failed and No Quorum proposals
No action is taken. The proposal remains in the record permanently for transparency.
Transparency & Auditability
Ready to participate?
Connect your wallet and check the DAO portal for open votes.