FlareBank docs / Governance
Governance docs
Vote with your BANK without depositing or locking it. See the DAO treasury, the vault and the protocol's fees in one place.
Voting runs on the Coston testnet as a rehearsal. Treasury and analytics show live Flare mainnet data.
1 · What the site is
The governance site has three tabs:
| Tab | What it shows | Network |
|---|---|---|
| Treasury | The DAO treasury's holdings, the BANK vault and bonding curve, fee streams, lifetime fees and growth charts | Flare mainnet |
| Proposals | Every proposal, its result and the voting panel; create a new proposal | Coston testnet |
| Electorate | Who can vote, the share of BANK that is enfranchised, and the balances that can't vote | Flare mainnet |
The defining feature: you never deposit, lock or delegate BANK to vote. It stays in your wallet, and your weight is proven from a snapshot of balances (see Your voting power).
2 · Testnet and mainnet
- To see and vote on proposals, connect a wallet switched to Coston. Without a wallet you can browse the Coston proposals read-only; a wallet left on Flare mainnet sees a prompt to switch, because the DAO isn't deployed there yet.
- Coston rehearsals run with short settings (minutes instead of days); the planned mainnet settings are in Passing, timing and the timelock.
3 · Your voting power
BANK doesn't record past balances the way most governance tokens do, so FlareBank proves them another way — without asking anyone to deposit:
- A random past block is picked. After a proposal is created, Flare's secure random number picks a block from a window before the proposal existed (the last 600 blocks on Coston; about 144,000 blocks, roughly 2 days, planned for mainnet). Nobody can buy BANK after seeing a proposal and vote with it, or predict the block in advance.
- Balances at that block are published. A snapshot tool reads every holder's balance at that block and publishes the list with a fingerprint (a Merkle root) on-chain.
- A challenge window follows (2 minutes on Coston; 24 hours planned for mainnet), during which a wrong list can be voided and replaced. The block itself can never be changed.
- Your weight is your BANK balance at that block, proven against the published fingerprint when you vote.
Some balances can't vote: liquidity pools, the BANK contract's own balance, the airdrop contract and the founder's initial mint. See The electorate.
4 · How to vote
- Connect your wallet on Coston and open a proposal under Proposals.
- The panel shows your weight at the snapshot block.
- Choose For, Against or Abstain and send the vote. You pay a small amount of gas — the gas-free (signed ballot) option isn't switched on.
- One vote per address, final. You can't change it once cast. A zero balance at the snapshot block can't vote.
- Smart-contract wallets (such as a Safe) can vote too.
- The contract also accepts signed ballots that someone else submits for you. If that is switched on, you sign this message and pay nothing:
Ballot(uint256 proposalId, uint8 support, address voter) support: 0 Against · 1 For · 2 Abstain domain: FlareBankGovernor · version 1 · chain id · the governor contract
5 · Proposals
Creating one needs at least the proposal threshold in BANK — 100 BANK on Coston, 25,000 BANK planned for mainnet — both when you create it and at the snapshot block. Choose a voting period (5 minutes and 1 hour are testnet-only; 1, 3, 7 or 14 days). The page shows exactly what the proposal will do before you sign.
| Proposal type | What passing it does |
|---|---|
| Signal / poll (default) | Records the result on-chain. Nothing is executed. |
| Change quorum, threshold or default voting period | Changes the governor's own settings, through the timelock. |
| Change DAO deployment | Hands the timelock to a new governor contract. |
| Pay from the treasury | Not usable yet — the treasury isn't controlled by the DAO (see The DAO treasury). |
| Raw call | Any contract call the timelock can make — for advanced users. |
Lifecycle: Created (Pending) → snapshot block sealed → balances published and challenge window passed → Activated (voting opens) → voting period ends → Succeeded or Defeated → for action proposals, Queued in the timelock → Executed. During the test, sealing, publishing and activation are run by the FlareBank team. A proposal not activated within 30 days expires.
6 · Passing, timing and the timelock
passes when For > Against and For + Against + Abstain ≥ quorum quorum = 10% of the electorate at the snapshot block (Abstain counts towards quorum, not towards the result)
| Setting | Coston (now) | Mainnet (planned) |
|---|---|---|
| Proposal threshold | 100 BANK | 25,000 BANK |
| Quorum | 10% | 10% (can be set 1–60% by vote) |
| Default voting period | 5 minutes | 5 days (1–28 days per proposal) |
| Snapshot look-back window | 600 blocks | ~144,000 blocks (~2 days) |
| Snapshot challenge window | 2 minutes | 24 hours |
| Timelock delay before execution | 2 minutes | 2 days |
| Time to queue/execute after passing | 1 hour | 14 days |
| Activation deadline | 30 days | 30 days |
| Actions per proposal | Up to 10 | Up to 10 |
Passed action proposals wait in the timelock before they run, so everyone can see what is coming. Anyone can queue and execute a passed proposal; signal proposals stop at Succeeded. A passed proposal that isn't queued in time expires.
7 · Who can cancel or veto
| Who | Can |
|---|---|
| The proposer | Cancel their proposal before voting ends |
| Guardian (the deployer wallet during the test) | Cancel any proposal before voting ends |
| Timelock canceller (same wallet) | Cancel a queued action before it executes |
| Snapshot guardian (same wallet) | Void a published balance list during its challenge window |
| Snapshot submitter (same wallet) | Publish balance lists — every proposal currently depends on it |
The governor's own settings can only be changed by a passed proposal through the timelock. Handing these test-phase roles to a multisig and the timelock is part of the mainnet plan.
8 · The DAO treasury
The DAO treasury is 0xaA68BC4BAb9a63958466f49f5a58c54A412D4906 on Flare mainnet. It holds BANK and WFLR, liquidity positions, staked FLR, positions in other Flare protocols and small balances on other chains. The Treasury tab lists every position and its value; borrowings are shown separately as “Less debt”, with the net below.
What flows in:
- BANK's fee receiver share — 5% of every buy, sell and transfer fee BANK charges (the treasury is BANK's fee receiver). It builds up in the BANK contract until claimed.
- Dividends on the BANK the treasury holds, and on its wBANK collateral in FlareBank Lending.
- Lending: 2% of liquidators' profit when they use the liquidate-and-sell router.
- Bankroll: its 0.15% open and close fees and 10% of its funding.
Only BANK held directly in the treasury wallet counts as voting weight; the page notes how much of the BANK it owns it can actually vote.
9 · Treasury analytics
| Section | What it shows | Where the numbers come from |
|---|---|---|
| The Vault | WFLR backing BANK, BANK supply, backing per BANK, BANK price, dividends owed | The BANK contract on Flare, read live |
| Bonding curve | What 1 BANK sells for, what buying costs, WFLR in the vault, amounts owed out | The BANK contract |
| Fee streams | The DAO's and team's unclaimed fee shares | The BANK contract |
| Lifetime fees paid | All mint, sell, reinvest and transfer fees since launch | BANK's on-chain events, refreshed every 15 minutes |
| Floor & backing over time | A hypothetical floor per sellable BANK, with and without the treasury | Monthly on-chain samples; clearly labelled hypothetical |
| Growth | BANK price (curve vs pool), treasury value, WFLR in FlareBank, fees, vault flows, addresses reached | On-chain events and archive reads |
The treasury total is priced by FTSO in your browser and then by a server-side portfolio scan using DeFiLlama prices, with BANK priced from its deepest pool. If an outside data source is down, the page shows a “Partial total” banner. Per-app analytics, such as Bankroll's House and markets, live in each app (Bankroll analytics).
10 · The electorate
The electorate — the total that quorum is measured against — is BANK's supply minus BANK that has no one to vote it: liquidity pools, the BANK contract itself, the airdrop contract and other addresses with no key holder, plus the founder's initial mint. The Electorate tab shows the figure live, the largest voter and the share of supply that can vote.
Holdings are concentrated: today the largest holder alone has more than the 10% quorum, and the top 10 hold about 80%. Quorum and threshold can be changed by vote.
11 · Limitations and risks
- Testnet only. No vote binds anything on mainnet yet.
- Advisory treasury. The treasury wallet is controlled by its key holder, not by votes.
- BANK's admin. The BANK contract is upgradeable, and its upgrade and admin rights are held by a single wallet. A mainnet DAO would not change that by itself; moving those rights to a multisig or the timelock is part of the mainnet plan.
- Test-phase operator roles. One wallet can cancel proposals, void balance lists, and is the only publisher of balance lists — if it doesn't publish, a proposal can't open and expires after 30 days.
- Concentration. A few holders can reach quorum alone.
- You pay gas to vote until a relayer is switched on.
- Unverified test contracts. The Coston governance contracts aren't source-verified on the explorer.
12 · Contracts
| Contract | Network | Role |
|---|---|---|
FlareBankGovernor0xf2582788f2CA7E91673Bc7993A9e36ce2fc13AB0 | Coston | Proposals, votes, results |
TimelockController0x5D466C5E155480BA6487921D9FDbBb78c9d879C8 | Coston | Delays and executes passed actions |
BankVoteSnapshots0xd007D0cf0C8ad720677921bd20D7CC70542CCa47 | Coston | Random snapshot block and published balance lists |
BANK0x194726F6C2aE988f1Ab5e1C943c17e591a6f6059 | Flare | The voting token (balances are snapshotted from mainnet) |
DAO treasury0xaA68BC4BAb9a63958466f49f5a58c54A412D4906 | Flare | Treasury wallet and BANK's fee receiver |
Governance uses Flare's secure random number (RandomNumberV2), found through Flare's official contract registry.