Vibestarter is built for raises on Base and Robinhood Chain. When third-party raises open, founders pick their chain as the first decision of the launch flow and backers fund on the chain the raise lives on. The platform token was the one piece still pinned to a single chain. From today, $VIBES lives on both.

If the platform supports raises on a chain, the platform's own token should be available there too: to hold, to trade, and in time to use, without leaving the chain the raise is on. In July we called Robinhood Chain a second venue on the same rails. A venue where the platform token cannot be held is not that.

The $VIBES contract on Robinhood Chain is 0x9A73D60b9c8C2d330EB6D885E69fCc1399c33C18. Check the address before you trade; it is the only $VIBES contract on Robinhood Chain.

One supply, two chains

$VIBES is a fixed-supply token: 1,000,000,000, all allocated at launch, nothing minted since. That does not change. The token on Base remains the canonical supply, and every other function of $VIBES (staking, the backer challenge mechanism, the holder snapshot) keeps reading it there.

On Robinhood Chain, $VIBES is a second contract of the same token: the same source code as the Base contract, the same name and symbol, the same 1,000,000,000 minted at deploy. Both contracts report the full supply, so a wallet, an explorer or an aggregator reading either chain sees the same token with the same total.

What keeps the two in step is a pair of bridge adapters. On Base, an adapter holds every $VIBES that has been sent across. On Robinhood Chain, an adapter holds the part of that chain's supply that has not been bridged: the reserve. Sending $VIBES from Base locks it in the Base adapter and releases the same amount from the reserve on Robinhood Chain; sending it back locks it into the reserve and releases the original on Base. At every moment, the amount locked on Base covers the amount in circulation on Robinhood Chain (the full supply minus what sits in the reserve); the two are equal whenever no crossing is in flight. The bridge issues, sells and distributes nothing; it moves quantity, one for one, and nothing else.

The addresses, so you can check any of this yourself:

The check is one subtraction. Read the Robinhood Chain token's total supply, subtract the reserve adapter's balance of it, and compare the result with the Base adapter's $VIBES balance. The two numbers match, and an automated watcher (below) confirms that every five minutes.

How to bridge

The bridge lives in the app at app.vibestarter.xyz/bridge. It needs a connected wallet, not a Vibestarter account.

1. Connect the wallet holding your $VIBES and pick the direction. Base to Robinhood Chain is the default; one control flips it.
2. Enter an amount. The panel shows your balance on the source chain, the LayerZero message fee (paid in the source chain's ETH and quoted before you sign), and how much room the hourly limit has left right now.
3. Approve, then send. The first crossing in each direction needs a one-time token approval for that chain's adapter, because the adapter pulls the tokens it locks. After that, a crossing is a single transaction.
4. Watch it cross. The page shows the message leaving the source chain, each of the two verifiers signing it, and the tokens landing. A crossing typically lands within a few minutes; the page shows the expected arrival time before you sign. Every transfer is also traceable on LayerZero Scan, and a History link under the panel lists your own crossings, both directions.

If your wallet holds no ETH on Robinhood Chain for gas, use one of the two routes the app itself links: Relay or the Arbitrum portal. Bridge look-alikes exist; take the link from this page or from the app, not from a search result.

The limits

• 30,000,000 $VIBES per hour, per direction. The limit refills continuously rather than resetting on the hour, and the panel shows the current room before you type an amount. The page will not let you send more than the current room. If a message ever exceeds the budget on arrival, the tokens stay locked on the source chain and the message waits, verified, at the destination; once the room has refilled, anyone can retry the delivery from LayerZero Scan and it completes.
• Six decimals cross the bridge. Amounts are rounded down to 0.000001 $VIBES; anything smaller stays in your wallet.
• Staking stays on Base. The staking contract holds the Base token, so $VIBES on Robinhood Chain cannot be staked; bridge it back first.
• Bridging carries no credit of its own. No quest, eligibility or allocation comes from moving tokens across.
• Holder counts read Base. The platform's holder snapshot counts Base wallets only for now; a wallet holding $VIBES only on Robinhood Chain is not in it yet.
• The two prices are independent. The Base pool on Aerodrome and the Robinhood Chain pool on Uniswap price separately. The two pools can trade at different prices, and a thin pool can sit far from the other for hours. The platform's price feed reads Base; the Robinhood Chain price is a second market, not the $VIBES price.

The pool on Robinhood Chain

Trading needs liquidity, so the treasury seeded a WETH / $VIBES pool on Uniswap v3 at the 1% fee tier, priced at the Base price at the moment of seeding, in one full-range position.

The $VIBES side did not cross the bridge. When the Robinhood Chain contract was deployed, 15,184,149.566018 $VIBES were already locked in the Base adapter, so the same amount of the new token went to the treasury at deploy and the rest went into the reserve. The books balanced from the first block: locked on Base equals in circulation on Robinhood Chain. The pool's $VIBES came out of that amount; the ETH side is the treasury's.

This position is seed liquidity for a second venue, held by the treasury's 2-of-3 multisig, and that multisig can withdraw it. It is not the locked liquidity that every Vibestarter raise creates at finalization, which sits in a contract with no withdrawal path; that mechanism is unchanged and applies to raises on both chains.

The technology

The bridge is a LayerZero OFT (Omnichain Fungible Token), a widely used standard for tokens that live on more than one chain. Each crossing is a message between the two adapters, one on each chain. The parts that matter for your risk:

• Two independent verifiers, both required. Every message must be attested by LayerZero Labs and by Nethermind before it can execute. One verifier alone cannot move anything; if either is offline, messages wait and funds stay put.
• One owner, on both chains. Both bridge adapters are owned by the same 2-of-3 multisig that administers the platform, at the same address on both chains. The deployer key held them only during deployment; ownership passed to the multisig when it accepted the handoff, before the bridge was opened to traffic. The token contracts themselves have no owner and no admin functions on either chain.
• A rate limit and a pause switch. The hourly limit above bounds what any fault could move in a window. Either end can be paused; an in-flight message that arrives during a pause is not lost: it waits, verified, and is delivered on retry once the pause lifts.
• A watcher that acts on its own. Every five minutes an automated check compares the amount locked on Base with the amount in circulation on Robinhood Chain, and matches every credit to the send that caused it. If circulation ever exceeds locked, or a credit appears with no matching send, the watcher pauses both ends itself and pages us. Its key can halt the bridge and do nothing else; only the multisig can resume.
• Everything is public. Every crossing is visible on both chains and on LayerZero Scan. The Base adapter's source is verified on Basescan, the Robinhood Chain token is the same source as the Base token, and both adapters are thin subclasses of LayerZero's audited OFT library.

Bridges are where cross-chain systems have historically broken, and no design removes that risk. Ours narrows it: two verifiers instead of one, a bounded window, an automated halt, and a multisig at the top. What it cannot remove is the risk of the chains themselves. Robinhood Chain's trust model differs from Base's, and our Risk Disclosure covers what that means, chain by chain.

What comes next

The app's token surfaces now show both contracts, and the bridge is linked from them. Robinhood Chain wallets in the holder snapshot and trade links on the token surfaces are on the list. We will say what ships when it ships.

Follow X / Twitter and the Discord for updates. $VIBES is a utility token, not a security and not an investment. Bridging and trading carry risk, including the risk of loss, and nothing here is financial advice.