Vote-Escrow Staking for Token Teams and Live ve8020 Systems
Protofire builds time locks, a distributor you fund and exit rules for token teams that want long-term holders to hold vote weight. Your accounts keep the admin roles. Live ve8020 systems get exit steps. We built the open-source ve8020 Launchpad with Balancer's core team, and Certora audited its Solidity contracts.

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026
On this page
Work shipped for 60+ networks and 95+ protocols, including
Vote-escrow staking contracts for a token you choose
Protofire builds vote-escrow staking contracts for a token you choose. Teams weighing vote-escrow staking ask who should steer their protocol: the wallet that bought yesterday, or the wallet that committed for a term. They answer that question in contracts: the lock, the weekly distribution, the exit rules and the holders of each admin role.
Protofire's work suits a token team that has written down its lock, exit and funding rules. It also suits a team whose ve8020 system locks a Balancer pool token.
Locking is not reversible and veCRV tokens are non-transferable. If a user decides to vote-lock their CRV tokens, they will only be able to reclaim the CRV tokens after the lock duration has ended.
Holders, roles and contracts of a vote-escrow system
The client's Safe holds the lock and distributor admin roles. Addresses that the client names hold the early unlock and unlock all roles, or no address holds them. The faucet has no admin.
Holders' wallets
Claims
Lock token
Lock and distributor admin
Early unlock and unlock all roles
Weekly funding
Lock contract
Distributor and faucet
Gauges (optional)
Lock and claim app, indexer
Balancer's 2026 votes rule out new locks on its pool tokens
BAL holders ended veBAL and approved Balancer's wind-down in 2026, so a new ve8020 lock on a Balancer pool token is ruled out.In BIP-919, which closed on 7 April 2026, BAL holders approved halting BAL emissions and discontinuing veBAL. BIP-928, which closed on 29 September 2026, set the terms of the wind-down. Under those terms, pools move to withdrawals only from 30 October 2026, "where the contracts allow it".
BIP-936, which closed on 27 October 2026, lists the onchain steps. BIP-936 schedules a pause of the v3 Vault for 30 November 2026. It also notes that the Vault unpauses by itself on 12 May 2029.
A lock opened today would hold a position in a protocol being wound down. So a new system locks the project's governance token, or a pool token from an AMM you pick.
Live ve8020 locks are a separate case. Each live lock runs to its end date, unless its early unlock admin or its unlock all admin opens an earlier exit.
Our record: the ve8020 Launchpad, built with Balancer's core team
Protofire built the open-source ve8020 Launchpad with Balancer's core team.Certora audited the Solidity contracts. On 22 August 2023, Balancer Grants announced that Protofire had been awarded a grant to build the Launchpad after a vote of veBAL holders. Certora published its report on 6 March 2024.
The Launchpad's code is public at protofire/ve8020-launchpad. The last commit was made on 2 May 2024, and the repository was archived on 1 September 2026. By the framework's own metric, per-project setup went from about 17 days to about 3, as our Balancer case study records.
The Launchpad's design is a starting point for a new system. Its factory deployed a lock, a distributor and a faucet for each project as minimal-proxy clones, as the Launchpad docs describe.
What Protofire builds for vote-escrow staking
Locks whose vote weight falls to zero at the end date
A holder's vote weight falls to zero on the lock's end date. A holder keeps that weight by adding tokens or extending the lock. Protofire builds the lock contract for your token, with one lock per address and end dates rounded to whole weeks. A whitelist names the vaults or multisigs you allow to lock.
A weekly distributor that you fund
A lock produces no distribution by itself. Each week, holders claim a share of what you or another address deposits. A week with no deposit gives them nothing. Protofire builds the weekly distributor and a faucet that spreads one deposit over a set number of weeks. We also build your funding calendar as Safe transactions.
Exit rules that holders see before they lock
Before they commit, holders see the early unlock option, its penalty and who can call unlock all. You choose between no early exit and an exit with a penalty. Protofire writes the exit table, which lists each setting and what the admin of that setting can still change.
Optional gauges for your own emissions
With gauges, lock holders weight your own emissions across pools or products. Protofire builds a gauge controller and gauges from Curve's GaugeController design or from a codebase you name. The build includes weekly weight checkpoints and a vote history that a holder can recompute.
A lock and claim screen that shows the exit terms
Before signing, a holder sees the end date, the vote weight and the exit terms. Protofire builds screens to lock, add, extend, claim and withdraw. The screens read from a subgraph that indexes lock and claim events. The app shows no forecast amounts.
Exit steps for a live ve8020 system
If your holders lock a Balancer pool token today, you need to know what the contracts and the pool allow. Protofire reads the deployed clones, the pool's pause state and its recovery mode against the steps of BIP-936. You get a snapshot of locks and unclaimed balances, and a runbook for the role holders. For a system built elsewhere, our independent review of a system another team wrote can come first.
How a governance-token lock differs from a pool-token lock
Both lock types give the holder a non-transferable vote weight that decays to zero, and a claim on what the distributor receives.The two types differ in what the lock holds while it runs.
What the holder gives up
Governance-token lock (the veCRV model): Use of the governance token until the lock ends
80/20 pool-token lock (the ve8020 model): Use of the whole pool position, paired asset included
Price exposure while locked
Governance-token lock (the veCRV model): The governance token alone
80/20 pool-token lock (the ve8020 model): Both pool assets at the pool's weights, plus the pool contract's risk
When the lock ends
Governance-token lock (the veCRV model): Withdraw returns the token
80/20 pool-token lock (the ve8020 model): Withdraw returns the pool token, and the holder exits the pool through the AMM's own path
If the venue changes
Governance-token lock (the veCRV model): There is no pool behind the lock
80/20 pool-token lock (the ve8020 model): A paused pool or one in withdrawals only leaves holders the pool's exit path, as BIP-928 set for Balancer from 30 October 2026
How the build runs, from parameter sheet to Safe deployment
- Step 1
You sign a parameter sheet
You decide the lock token and the maximum lock. You also decide whether early unlock exists, and at what penalty. You decide who may call unlock all, and what goes into the distributor and when. Protofire implements the sheet. We give no tokenomics, legal or tax advice. - Step 2
Protofire writes the contracts and the tests
The build starts from a vote-escrow codebase that you accept, such as Curve's contracts or the Launchpad's. The proposal names that codebase's release and license. Protofire's tests cover a lock that ends mid-week and a deposit on an expired lock. - Step 3
An audit firm you choose reviews the code
Before launch, the audit firm reviews the lock, distributor and gauge code that Protofire wrote, and we fix what the firm reports. A review covers the code it was given. The review does not promise a system free of bugs. - Step 4
Your Safe deploys the contracts
Protofire's deployment script prepares the Launchpad's deploy call as a transaction for your Safe, and your owners sign it. In the Launchpad's design, the caller becomes admin of the lock and the distributor. The call also names the early unlock admin and the unlock all admin. No function changes either address later. A zero address disables that feature "forever", according to the Launchpad docs. On a chain with no Safe yet, Safe deployment on a new network comes first. - Step 5
Holders lock and claim, and you hold the roles
Holders use the app and your indexer. Protofire holds no admin, early unlock or unlock all role. We also hold no distributor, gauge or funding role. Your own key, or your Safe, runs the deployment.
How work with Protofire starts
With Protofire, a new system starts from the lock token, maximum lock, exit rules and funding rules you have in mind.Work on an exit from a live system starts from the addresses of the deployed lock, distributor and faucet. You can add a lock export if you have one, shared under NDA with holders' wallet addresses stripped out.
- Proposal
- In writing, one business day after the discovery call: findings, a plan in phases and the first step we recommend.
- Price
- Fixed per phase when you commission it, against written acceptance criteria. Overruns inside them are ours to absorb, invoices follow delivered milestones, and you can stop at any phase boundary. Anything we operate after launch is priced in the proposal as its own recurring line, with the notice to end it.
- Ownership
- Code we write for you, contracts, the keys and credentials this work creates and the accounts your infrastructure runs in are yours by contract, within the license of any third-party software involved. Keys that a custody platform or a staking provider holds under its own key model stay with it under your contract; every other custody key stays with you or the custodian you appoint. Where the scope places something on servers we rent, it says what moves to you and when. An NDA is available from your first message, and we sign a data processing agreement (DPA) together with it.
- After launch
- Delivery closes with a hypercare window and a defect warranty, with their terms written into the proposal. A service we operate continues under its written scope until that scope ends.
- Access
- Read-only by default. A role that can start requests only if your written scope names one; never a signer, approver, administrator, key holder or recovery role on your contracts, wallets or custody platform. Services we build call each platform on credentials your staff issue and keep in your vault. Anything that approves or moves funds runs in your environment, and a scope under which we operate a service lists every write call it makes. Where the scope has us operate nodes, validators, monitors, explorers or indexers, it names the role and any key we hold on those servers, and in your own cloud account you can remove it.
- Licenses
- Protofire is an engineering firm and holds no financial or crypto-asset license; licensed activity stays with you and your providers.
How we work shows a worked proposal.
When you do not need a new vote-escrow contract
Some locking jobs need no new vote-escrow contract.
- A holder who locks CRV for veCRV uses Curve's own interface. No contract gets written. A holder who leaves a Balancer pool or a veBAL lock uses Balancer's own path. BIP-928 keeps a withdrawal interface and documentation available until the veBAL locks expire. The interface and documentation include the way out of veBAL locks.
- Stake, unbond and claim for a network's or protocol's token, with no time-weighted vote, belongs to staking module development. A transferable receipt over staked assets is a liquid staking token.
- Proposals, delegation, timelocks and execution belong to DAO tooling, whose votes can read lock balances.
- To put tokens in holders' hands before a lock exists, a team needs an airdrop and its claim contract.
FAQ
What is vote-escrow staking, and which contracts does Protofire build?
How do ve8020, veCRV and ve(3,3) differ?
Can a new ve8020 system still lock a Balancer 80/20 pool token?
Our ve8020 system locks a Balancer pool token. What can we do now?
What happens in a week when nobody funds the distributor?
Does Protofire build gauge-voting contracts?
Do securities or staking rules apply to a vote-escrow lock?
Get a proposal
Tell us what you are building. An engineer reads it, we have a short call, and the written proposal follows within one business day.
