Skip to content
Cosmic

Robinhood Chain · chain id 4663

Deploy the contracts

For the project owner. Each step below is one transaction that your wallet signs. This site holds no key and sends nothing by itself.

Before you start

  • The connected wallet pays the gas and becomes the owner of every contract it deploys. Ownership can be handed over later in two steps, from the owner console.
  • The owner can add vaults, publish terms for new positions and pause deposits. It cannot withdraw principal, change the terms of an existing position or stop exits and withdrawals.
  • The contracts have not been audited. Their source, tests and specification are in the repository.
  • After the last step, the deployment file below is checked on chain and published with the site. Until then the public pages keep saying that nothing is deployed.

Wallet

Connect the wallet that will own the contracts.

This site is already published with a deployment.

The vault and the campaigns contract below come from the published manifest. The buyback module can still be added below.

1. Vault and campaigns

The vault holds every lock. The campaigns contract holds sponsor budgets in escrow. Both work without a COSM token.

Epoch length

A position becomes eligible for community rewards at the first epoch boundary after its deposit and stops at an epoch boundary at maturity. No lock duration can be shorter than one epoch. The value is fixed at deployment and can never be changed. The project's tests and the examples in its specification use one hour; the choice is yours.

01CosmicVaultConfirming

Constructor: owner = the connected wallet, epoch = the length chosen above.

Sent from this browser. Waiting for the chain to confirm it; it is not offered again in the meantime.

02CosmicCampaignsConfirming

Constructor: owner = the connected wallet, vault = the contract from step 1.

Sent from this browser. Waiting for the chain to confirm it; it is not offered again in the meantime.

2. Buyback module

Optional, and possible at any later time. The module is bound to one COSM token for good and can only ever pull the vault's buyback reserves. Without it those reserves simply accumulate in the vault.

COSM token
0x9D91628b808A784CD15D1a866B964bEBD550C54ePublished in config/token.json on 2026-10-04.
What the token answers
This address does not answer as an ERC-20 token on Robinhood Chain.
Swap router for the adapter
0xCaf681a66D020601342297493863E78C959E5cb2Uniswap v3 SwapRouter02, verified for this network (docs/NETWORKS.md).

How bought COSM is destroyed

burn() calls the token's burn(uint256) and requires total supply to fall by exactly the amount; a buyback is refused otherwise. Dead address sends the tokens to 0x…dEaD: supply is unchanged and the page reports those amounts separately. Fixed at deployment.

Delay before a new swap adapter can be used

Every adapter the owner authorises becomes usable only after this delay, which gives lockers time to see a new route before it can spend reserves. Fixed at deployment.

03CosmicBuybackNot done

Constructor: owner = the connected wallet, the vault, the COSM token, the burn method and the adapter delay.

Finish section 1 first.

04Attach the module to the vaultNot done

vault.setBuybackModule(module). A vault accepts one module, once: this cannot be changed or undone.

05UniswapV3BuybackAdapterNot done

Constructor: the swap router above. The adapter only forwards a swap whose path starts at the reserve token and ends at COSM.

06Authorise the adapterNot done

buyback.authorizeAdapter(adapter). It becomes usable after the adapter delay.

3. Publish the deployment

The deployment file appears here once the vault and the campaigns contract exist.