# Two deployments, one schedule each: staking on Base and Robinhood Chain

> Canonical: https://blazephoenix.xyz/learn/two-staking-deployments/
> License: CC BY-NC-ND 4.0 (attribution + link) · © 2026 BlazePhoenix
> Updated: 2026-11-16

The 180,000,000 BZPX staking budget is two vaults, not one: the staking contract is deployed once on Base and once on Robinhood Chain, each independent, with its own 90,000,000 BZPX emission cap, reserves and clock. The engine is pre-launch, with its launch given as Q2 2027.

Short answer: two. The staking contract is deployed twice, on Base and on Robinhood Chain, and the deployments are independent. Each carries its own 90,000,000 BZPX emission cap. The staking line of the allocation, 180,000,000 BZPX, is the sum of the two caps. The contract does not know about its twin.

The staking engine is pre-launch. The site gives its launch as Q2 2027, a schedule and not a deployment, so there is no staking address to quote yet.

## What each deployment owns

In the words of the repository, these are 'two independent deployments of this contract, each capped at 90,000,000 BZPX'. Each has its own contract, reward reserve, protocol reserve and emission clock. A position, a debt, a reserve or a breaker state in one deployment is invisible to the other, and a trip, an emergency or a haircut in one does not touch the other.

## Funded at deploy, in the same run

The deploy script places one contract per run. It requires the deployer to hold at least 90,000,000 BZPX and funds the emission in the same run as the deployment, through `fundEmission`, then checks that the reward reserve holds the full 90,000,000 and that the contract reports itself solvent. It does not fix the chain, so the same bytecode can be placed on two networks.

The consequence is that each deployment's whole budget sits in its own reserve before the script finishes. Nothing is promised from one contract to the other, and nothing can be moved between them.

## Where 180 million comes from

The token allocation reads: market liquidity 520,000,000, staking emission 180,000,000, airdrop and bounties 130,000,000, team and operations 103,000,000, partners and ecosystem 60,000,000, marketing 7,000,000. The staking line is two budgets of 90,000,000, each on its own eight-year schedule.

A reader who wants one deployment's schedule reads the emission-curve table once. The other deployment's schedule is the same table on its own clock, starting when that contract's emission starts.

## What this does not claim

It does not say the two deployments launch on the same day. Scheduled emission is an upper bound on what a deployment can pay, never a payment: a window in which no position holds weight emits nothing.

**Verify it yourself:** In a checkout of the staking repository at commit c0366cf, read script/Deploy.s.sol: it deploys one contract per run and calls fundEmission for 90,000,000 BZPX in the same script. Then, on a deployed contract once one exists, call TOTAL_REWARDS() and expect 90,000,000 BZPX. Reading: section 25.8 of the 2.4 whitepaper.

Related: https://blazephoenix.xyz/learn/the-halving-schedule/ · https://blazephoenix.xyz/learn/proof-of-solvency/ · https://blazephoenix.xyz/learn/one-clock-per-chain/
