Issue a DAO-ready governance token

ERC20Votes checkpoints + timelocked admin + Safe handoff in one go. Compatible with Tally, Aragon, and Snapshot.

Governance tokens fail in two predictable ways: vote tracking that doesn't snapshot cleanly, and an admin key that nobody trusts. This preset solves both — ERC20Votes gives you per-block checkpoints that any major governance UI (Tally, Aragon, Snapshot) can read, and the timelock + Safe handoff move the admin role to a multisig with a public delay everyone can see.

What's included

• Immutable Metadata: Token metadata (name, symbol, icon) cannot be changed after creation
• Governance Votes (ERC20Votes): Checkpoint-based vote tracking for OpenZeppelin Governor or off-chain Snapshot. Requires Gasless Approvals (ERC-2612).
• Gasless Approvals (ERC-2612): Enable gasless token approvals via signed messages.
• Admin Timelock (recommended for DAOs): Deploys an OpenZeppelin TimelockController and assigns it the token's admin role. All admin actions (pause, freeze, fee changes, etc.) queue through the timelock and wait the configured delay before they execute — giving users time to exit before a privileged action takes effect.
• Capped Supply: Set a maximum token supply that can never be exceeded
• Burnable: Token holders can burn their own tokens

Why this stack

Vote checkpoints let proposals settle on a frozen snapshot, so a flash-loaned majority can't sway a live vote. The timelock gives users a window to exit before any privileged action takes effect. The Safe handoff is the part most projects forget — without it, your governance token has a single private key that can pause transfers. With it, the admin role lives behind a multisig + delay anyone can verify on-chain.

Do I need the timelock if my multisig is a Safe?

Yes. The Safe is who can act; the timelock is when those actions take effect. Together they make admin actions predictable and reversible by the community. A Safe without a timelock can still drain trust the moment a holder notices a queued vote.

How do I plug this into Tally?

After deploy, paste the contract address into Tally's import flow. ERC20Votes is part of their standard support — your token's checkpoint data will populate the governance UI automatically.

Can I add an OpenZeppelin Governor later?

The Governor is a separate contract — Toqqo doesn't deploy one in this preset, but the token is fully compatible. You can deploy a Governor against this token any time using OpenZeppelin's tooling or Tally.