/Bridge Mechanism

The bridge mechanism is designed to give locked COOK holders a clean path out, then establish a 1:1 relayer bridge between Solana COOK and Cookie Chain COOK.

# Token roles

• Pumpfun token: a new token created on Solana to bootstrap the unlock and bridge-out process.
• sCOOK: Solana-side COOK. (Created on pump.fun)
• cCOOK: Cookie Chain-side COOK. (The native COOK)
• Locked COOK: the acquired locked allocation representing 27% of the supply. (on Solana Side)

# Locked holder bridge-out

The plan is to create the Pumpfun token on Solana and acquire locked COOK tokens, equal to 27% of the supply. That acquired allocation is used to let locked holders bridge out freely instead of being trapped by the original lock structure.

# 1:1 conversion bridge

After the locked-holder path is live, the next phase is a 1:1 conversion relayer bridge between Solana COOK and Cookie Chain COOK. Users will be able to move between sCOOK and cCOOK through the relayer bridge at parity.

# Fee usage

Pump.fun creator fees from the Solana-side token launch will be routed back into the ecosystem. The intended uses are upcoming validator incentives, infrastructure, and hackathons.

# Bridge custody

Bridge funds are maintained by community-led multisigs across both chains. The custody layer uses Squads multisig vaults so bridge funds are not controlled by a single party.

The bridge custody setup is inspectable in public. Community members can follow signer actions, votes, and vault state from the multisig dashboard at sig.cookiechain.wtf/community.

# Operating principles

• Locked holders first: the mechanism prioritizes a free bridge-out path for locked participants.
• Parity between chains: sCOOK and cCOOK conversion is designed around 1:1 movement.
• Community custody: multisig vaults on both chains maintain bridge funds.
• Ecosystem reinvestment: creator fees support validators, infrastructure, and builder events.