Skip to content

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.

Luis Medeiros

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026

On this page
  1. Overview
  2. Balancer wind-down
  3. Our record
  4. What you get
  5. Lock types
  6. How the work goes
  7. How work starts
  8. Not the right fit
  9. Related services
  10. FAQ

Work shipped for 60+ networks and 95+ protocols, including

  • Chainlink
  • Ethereum
  • Solana
  • Safe
  • Ripple
  • Aave

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.
Curve Finance, VotingEscrow developer documentation, Curve DAO · Developer documentation, read November 2026

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.

Token holders

Holders' wallets

Holders sign each lock, extension and withdrawal.

Claims

A claim collects the tokens that the distributor holds for the holder.
Client

Lock token

The lock token is the project's governance token, or a pool token from an AMM the client picks.

Lock and distributor admin

The admin allows distribution tokens and admits smart-contract lockers. It can also pass the admin role on.

Early unlock and unlock all roles

These roles switch early unlock on or off, change its penalty and call unlock all.

Weekly funding

The client deposits allowed tokens for each week, directly or through the faucet.
Protofire builds

Lock contract

The lock contract holds each lock until its end date, while vote weight falls to zero.

Distributor and faucet

The distributor and faucet split each week's deposits by lock balances.

Gauges (optional)

Gauges let lock holders weight the client's own emissions.

Lock and claim app, indexer

The app prepares holders' transactions, and the indexer reads locks, weights and claims from events.

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

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.

FAQ

What is vote-escrow staking, and which contracts does Protofire build?
Vote-escrow staking locks a token for a chosen term. In exchange, the holder gets vote weight that decays to zero when the lock ends, and a pro-rata claim on deposits made for lockers. Curve's veCRV locks CRV, and ve8020 locks an 80/20 Balancer pool token. Protofire builds the lock, the distributor and the exit rules. We also build the lock and claim app, and gauges if you want them.
How do ve8020, veCRV and ve(3,3) differ?
The three designs differ in what is locked and what the lock steers. veCRV locks CRV and gives voting power "on proposals and gauge weight votes that determine CRV emissions", per Curve's docs. ve8020 locks an 80/20 Balancer pool token, and Launchpad systems had no gauges of their own. ve(3,3) names the family that follows Solidly. One example is Velodrome's v2, which its repository describes as "an AMM on Optimism inspired by Solidly". The choice follows the client's written requirements.
Can a new ve8020 system still lock a Balancer 80/20 pool token?
No, a new lock on such a pool token is ruled out. The contracts would accept the token. But the pool behind the token is part of a protocol whose holders voted to wind it down. BIP-919 ended BAL emissions and veBAL. Under BIP-928, pausable pools take withdrawals only from 30 October 2026. A new system locks the project's governance token, or a pool token from an AMM the client picks.
Our ve8020 system locks a Balancer pool token. What can we do now?
What you can do depends on what the deployed contracts allow. Launchpad clones cannot be upgraded, and they cannot move a lock to another contract. A lock ends on its end date, or earlier in two cases. In the first case, an early unlock admin was named at deployment and has switched early unlock on. In the second, an unlock all admin calls set_all_unlock, which cannot be undone. Protofire prepares the final deposits as transactions for the accounts that hold those roles. Where an unlock all admin exists, we also prepare unlock all as a transaction for that admin's account, only once nothing remains to distribute. Protofire also writes exit steps for holders.
What happens in a week when nobody funds the distributor?
Holders receive nothing for that week. The distributor splits what is deposited. Its docs describe it as "requiring regular deposits". A faucet schedule can lag when nobody calls the distributor. An address can then call distributePastRewards to move up to ten past weeks across. Locks and vote weight do not change.
Does Protofire build gauge-voting contracts?
Yes, Protofire builds gauge-voting contracts when you ask for them. The build is a gauge controller and gauges through which lock holders weight your own emissions. On Balancer itself, BIP-919 set the weight of Balancer's own gauge types to zero.
Do securities or staking rules apply to a vote-escrow lock?
Your counsel decides whether these rules apply. In an interpretive release dated 17 March 2026, the SEC uses the name "Protocol Staking" for staking digital commodities "on PoS Networks" (SEC release 33-11412). The release does not address vote-escrow locks. In June 2026, the FCA described staking as "the practice of locking up cryptoassets to help secure and validate transactions on a blockchain network" (FCA PS26/11). Tax on distributions is for your tax adviser.

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.

Luis MedeirosField CTO, reads every request · LinkedIn

A demo or repository link also works.