How Genesis Works
Genesis is a smart-contract process with explicit states and onchain transitions. Time can make an action eligible, but time alone never finalizes, cancels, unlocks, refunds, or redeems a position.
The founding commission six movements
One window. One settlement.
The successful route carries every contribution from a common window into one locked founding position.
- The endowment
Fund the commission
The fixed $RAPH allocation enters the Genesis contract before the window can open.
- The window
Commit ETH
The window opens. Every contribution joins one recorded total under the committing address.
- The settlement
Form the market
Finalization creates the canonical pool and stakes the complete contributor LP position.
- The working position
Keep liquidity at work
LP remains locked in the gauge while contributors claim harvested $RAPH rewards.
- The expiry
Open the lock
After the immutable expiry, anyone may submit the permissionless unlock transaction.
- The return
Redeem the position
Each contributor claims proportional LP and settles any remaining reward entitlement.
Mainnet launch terms
The deployed mainnet Genesis contract is 0x127a3f4E28F99461ac88f59FBAD2cb88F8782aB5. In one atomic Safe batch, the opening transaction opened deposits and recorded the protocol administrator Safe's 0.01 ETH first commitment on 17 August 2026. It anchored the schedule. The Safe later finalized the launch successfully on 31 Aug 2026 at 17:27:10 UTC.
| Launch boundary | Exact time (UTC) | What changes |
|---|---|---|
| Deposits opened | 17 Aug 2026, 17:00:18 | Participants may commit ETH |
| Deposits close | 31 Aug 2026, 17:00:18 | No further commitments are accepted; administrator-only finalization begins |
| Public finalization | 31 Aug 2026, 18:00:18 | Anyone may submit finalization if the launch remains pending |
| Failure deadline | 7 Sep 2026, 17:00:18 | Finalization closes; permissionless failure cancellation becomes available if still pending |
| LP lock expiry | 5 Jan 2027, 17:00:18 | If the launch finalized successfully, anyone may trigger LP unlock |
The schedule is fixed by the contract, but reaching a boundary does not execute the next action automatically. The interface and verified contract state remain authoritative for the current phase.
The immutable launch terms behind those dates are:
| Term | Mainnet value |
|---|---|
| Fixed pool allocation | 10 million $RAPH |
| Commitment window | 14 days from the onchain start |
| First global commitment minimum | 0.01 ETH |
| Administrator-only finalization period | 1 hour after deposits close |
| Finalization failure deadline | 7 days after deposits close |
| LP lock expiry | 127 days after deposits close (120 days after the failure deadline) |
Mainnet settlement result
Successful finalization paired 116.967472 WETH with 10 million RAPH in the canonical RAPH/WETH pool. It minted and staked 34,200.507598572276160157 contributor LP in the Genesis gauge. The pool also permanently locked its standard 1,000 LP base units (0.000000000000001 LP).
Those amounts describe the initial settlement. Trading began once the transaction succeeded, so current reserves and price must be read from the pool. Genesis is now in state 1 (FinalizedStaked), cancellation and refunds are unavailable, and the contributor LP remains staked until 5 Jan 2027 at 17:00:18 UTC, exactly 127 days after the commitment window closed.
Before deposits
The protocol administrator funds the Genesis contract with the fixed $RAPH allocation. Funding and schedule activation are separate actions: the deposit window cannot open until the allocation is present, and no schedule boundary exists until the administrator starts the window onchain.
This sequencing prevents deployment or review delays from consuming part of the public commitment window.
During the commitment window
Participants call the Genesis contract with native ETH. The contract records only commitments made through that function.
- The same address may commit more than once.
- Every additional commitment increases both the address total and the launch total.
- The position remains attached to the committing address. There is no receipt token, NFT, transfer, reassignment, or administrator recovery path for a lost key.
- A participant cannot withdraw, cancel, or edit a pending commitment.
- ETH sent by unsupported routes does not create contributor ownership.
On mainnet, the first commitment recorded across the entire launch must be at least 0.01 ETH. This is not a per-wallet minimum: after the first global commitment exists, later calls need only send a nonzero amount at contract level. The interface should still be used for the live window status and transaction preview.
After deposits close
The final aggregate ratio is fixed when no more ETH can enter:
implied ratio = total ETH / fixed $RAPH
This is an implied starting ratio for the founding liquidity, not a direct token sale. Contributors receive claims on LP, not a liquid $RAPH balance.
Finalization then moves through two relative phases:
| Phase | Who may finalize |
|---|---|
| Before deposits close | Nobody |
| Initial finalization phase | Protocol administrator only |
| Public finalization phase | Anyone |
| At or after the failure deadline | Nobody; cancellation becomes available instead |
The administrator and public callers receive no contributor assets or special LP share for finalizing.
Successful atomic settlement
Finalization succeeds as one transaction or reverts completely. A successful call:
- revalidates the reviewed protocol dependencies and the still-empty future market;
- creates the canonical pool factory, volatile $RAPH/WETH pool, and gauge;
- neutralizes raw token donations sent to the predicted pool before reserves exist;
- wraps exactly the recorded contributor ETH;
- adds the complete fixed $RAPH allocation and all recorded WETH as liquidity;
- measures the LP minted for contributors; and
- stakes the complete contributor LP position in the gauge.
If any required step fails, the whole transaction reverts. No successful branch can leave a partial pool, consume only part of the recorded commitments, or leave contributor LP intentionally unstaked. Before the failure deadline, finalization can be retried after the blocking condition is resolved.
Cancellation and exact refunds
There are two routes into the same failed-launch outcome:
- The protocol administrator may cancel while the launch is still pending, including while deposits are open.
- If the launch remains pending when its failure deadline is reached, anyone may cancel it.
Cancellation is a denial-of-launch control, not an ETH withdrawal right for the administrator. After the failed state is recorded, every contributor independently claims:
refund = contributor's recorded ETH commitment
The amount is independent of the contract's raw ETH balance, pool prices, and other contributors' claims. The unused $RAPH allocation is returned separately and cannot reduce contributor refunds.
From locked LP to redemption
After successful finalization, cancellation is impossible. The aggregate LP remains staked until the immutable lock expiry, exactly 127 days after the mainnet commitment window closed. No administrator, emergency action, or contributor claim can shorten that lock.
Expiry only makes unlock eligible. Anyone may submit the unlock transaction, which withdraws the aggregate LP from the gauge and attempts a final reward checkpoint. Participants then redeem their proportional LP independently. See Rewards and Redemption for the complete claim flow.
The launch interface and verified contract state determine which action is currently available. A browser clock or static documentation page cannot establish the contract's phase by itself.