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.

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.

01CosmicVaultNot done

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

02CosmicCampaignsNot done

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

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: CA: SoonThe token address is not published yet (CA: Soon).
Swap router for the adapter: 0xCaf681a66D020601342297493863E78C959E5cb2Uniswap v3 SwapRouter02, verified for this network (docs/NETWORKS.md).

The buyback module waits for the $COSM address.

It is deployed with the token's address and cannot be pointed at another token afterwards. Once the address is published on this site, these steps open. The vault and campaigns work in the meantime.

3. Publish the deployment

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