How a raise works
I · Fixed
Seed
A creator writes down the whole raise in one transaction: the token and its supply, what the raise is denominated in, the caps, the window, the wallets that will receive the money, and the schedules that release the held-back tokens. The factory checks the arithmetic before anything exists. The supply has to add up, the wallet shares have to total 100%, the window needs a beginning and an end. A raise that gets through that function is internally consistent for the rest of its life.
The token is deployed at the same moment and its entire supply is minted into the raise. Nobody else holds a unit of it, so there is nothing to trade and nothing to front-run.
II · Fixed
Sowing
The window opens when it said it would and shuts when it said it would. There is no function anywhere that extends it, shortens it or reopens it.
While it runs, anyone may commit. A raise with an allowlist takes only proven addresses until that window shuts. Commitments are recorded against the sending address and can be topped up at any point. A commitment that would cross the hard cap takes what is left and returns the rest in the same transaction. The raise fills exactly rather than reverting a queue of transactions at the line.
Nothing leaves while the window is open. Not to the creator, not to the platform, not to anyone. The only balance-reducing action available is a contributor's own early exit, which costs 10.0% of their position.
III · Fixed
Rooting
The close is the hinge. What the raise recorded is what it will act on, and from that second the record does not move.
Below the soft cap the raise failed. Every contributor takes their whole commitment back, with no penalty and no deadline. The creator takes the token supply back. At or above it the raise succeeded, and anyone willing to pay the gas can run the launch.
IV · One transaction
Season
The launch does four things and then it is over:
The platform takes 2.00% of the gross, less whatever referrers earned out of it. A share of what is left is paired with the liquidity tokens and minted as a full-range Uniswap v3 position. That position goes straight into a locker with no admin and no early exit. The rest is credited to the wallets the raise named. Allocations with a cliff or a schedule go into the vesting vault. One with neither is sent to its wallet there and then.
Every payout is a pull. The launch writes numbers into mappings and moves on. A wallet that cannot receive a transfer never blocks the launch for everybody else.
V · On a schedule
Turning
Contributors claim on the schedule the raise published; team allocations release from the vault on theirs. The vault has no owner and no admin function. A schedule, once written, pays the beneficiary it names and nobody else. Anyone can call the release; the tokens still go to that wallet.
The liquidity position stays locked for the term the raise published. The trading fees it earns over that term go to the platform, not to the creator. The unlock time can be pushed further out; it can never be brought closer.
When it expires, the creator takes the whole position back. Both sides of the pair, the tokens and the raised asset alike. So the lock fixes a date, and nothing about it fixes how deep the market stays. Read that date before you commit. Every raise page carries it as “Liquidity unlocks”.
VI · Afterwards
After the raise
If the raise was denominated in a tokenised asset, the project keeps holding that asset after launch. It doesn’t get sold or converted. So the treasury is worth more when the stock goes up.
The raise page shows two figures: the treasury at launch, and the treasury now. Next to the second one it says where the price came from, which is either the oracle listed for that asset or the asset’s own pools on this chain when there’s no oracle.
One thing to be clear about. That number tells you what the project holds. It doesn’t mean you can redeem your tokens for a slice of it. No contract does that and nobody has promised to.
What is actually being trusted
- The window
- Enforced. Start and end are written at creation and no function moves them.
- The split
- Enforced. The wallets and their shares are written at creation; the launch credits exactly those wallets in exactly those shares.
- The lock
- Enforced as a date. The locker has no owner and no early release. When the date passes the creator withdraws the whole position.
- Vesting
- Enforced. The vault has no revoke and no accelerate.
- The refund
- Enforced. Below the soft cap, or after a cancellation, every commitment is withdrawable in full.
- The project
- Not enforced. Nothing here obliges a team to build anything, to spend the money on what they said, or to keep the treasury in the asset they raised in once it is in their wallets.
- The description
- Hash-checked, not vetted. The interface proves a description is the one the team committed to. It has no opinion on whether it is true.
- The creator
- A creator can cancel a raise before it launches. That refunds everybody in full; it cannot take anything.
- The platform
- Can pause new raises, change its own fees for future raises, and cancel a raise before it launches. A cancellation refunds every contributor in full and returns the token supply to the creator. It curates the asset list, and can swap the price feed behind an asset a live raise is denominated in. Every dollar figure on that page moves with it. The platform cannot move a contributor's money, take a fee it did not publish, alter a schedule, unlock liquidity, change a window, or touch a raise that has already launched.
GAIA
The platform’s own token. One billion, minted once, no mint function. Half of it is locked on chain today, on the schedules below.
- Supply
- 1,000,000,000 GAIA
- Locked
- 500,000,000 GAIA · 50% of supply
locked 50%unlocked 50%
The locks
Each one is a separate transaction. Cliff means nothing releases until that date; after it, the rest unlocks steadily until the final date.
- 250,000,000 GAIA
- no cliff, fully unlocked 10 Sept 2027 · transaction
- 100,000,000 GAIA
- cliff 9 Mar 2027, fully unlocked 9 Sept 2028 · transaction
- 75,000,000 GAIA
- no cliff, fully unlocked 10 Sept 2027 · transaction
- 75,000,000 GAIA
- no cliff, fully unlocked 9 Mar 2027 · transaction
The contracts
Deployed on Robinhood Chain, chain id 4663.
- RaiseFactory
- 0xfce41678b67027ca6d094314a692b57f227485b4
- AssetRegistry
- 0xab3204c0e67977a8831db1cf889a0d9411815af1
- VestingVault
- 0x6db25317cc3b8a0293828c256330a68da8aa0392
- LiquidityLocker
- 0x68e180bd1a79eecd6a37544af0cdcd25f7e48b5b
RaiseLens holds no state and no privileges. It exists so a page costs one request instead of twenty. Everything it returns is a projection of the contracts above, and it can be redeployed at any time without touching a single raise.