01ELYSIUM
Fill the curve
Buy and sell the project token against HYPE. At the graduation threshold, curve trading pauses and a migration job begins.
HYPE Project token
Stocks in Paradise
The path
to paradise.
Born on Elysium.
Paired with the stocks you know.
How funds move, what contracts may do, and what anyone can verify. A blueprint for launching tokens with stock-paired liquidity.
Explore the mechanismStart withHYPE on Ely
Source stock onHyperCore spot
Graduate intoToken / stock pool
02 / THE MECHANISMOne journey.
One journey.
Every step accounted for.
The curve raises HYPE. Graduation converts the designated purchase funds into a stock token and brings it back to Elysium. The project token never leaves Ely.
02RELAY
Move the funds
Bridge the designated HYPE to a HyperEVM execution contract, with a fixed recipient, spending cap and minimum amount received.
Ely HyperEVM
03HYPERCORE
Acquire the stock
The contract funds its own Core account, converts HYPE to USDC, and buys the selected stock token through a bounded spot order.
HYPE USDC Stock
04HYPEREVM
Confirm delivery
After the fill is confirmed, send the stock from Core to its linked HyperEVM token. Check the actual received balance before continuing.
Core stock ERC-20 stock
05OFFICIAL BRIDGE
Return to Ely
Use Elysium’s official token gateway to bridge the stock from HyperEVM. The migration remains pending until the stock arrives on Ely.
HyperEVM Elysium
06ELYSIUM
Seed the pool
Pair the received stock with reserved project tokens. Mark the project graduated only after pool creation and the required LP custody checks.
Project token wNVDAx*
* NVDA is the first research example. Stock eligibility and final launch parameters remain under review.
A sequence, not a single transaction
Confirm. Then advance.
Core orders and cross-chain transfers settle asynchronously. Each migration needs its own state, balances and completion checks. A queued order is not a fill; a submitted bridge transaction is not delivery. Partial fills, timeouts and recovery rules must be implemented before launch.
A stock-paired pool is a trading pair. It does not make the project token an equity share, guarantee a price floor, or create a right to redeem it for the underlying stock.
03 / ANTI-RUG DESIGN
Rules over discretion.
The design goal is to prevent creators or administrators from diverting purchase funds or removing liquidity principal. That protection must come from enforceable contracts.
A launch requirement · Not yet implemented
No discretionary
liquidity withdrawals.
The final LP ownership and locking rules must remove creator and administrator access to withdraw liquidity principal. These rules must be published, implemented and verified before fundraising opens.
Fixed destinations
Purchase funds, returned stock and LP positions may only reach defined protocol contracts. An operator must not be able to substitute a personal recipient.
Bounded execution
Bind each migration to its asset, maximum spend, minimum stock amount, fee limits and unique job ID. Bots may trigger permitted steps, never arbitrary calls or duplicate purchases.
Published permissions
Disclose token minting powers, administrator roles, upgrades, fee rights and recovery paths. No hidden privilege should be able to bypass the liquidity restrictions.
Verifiable graduation
Check stock arrival, pool balances and LP custody on-chain. Publish the deployed addresses and verified source so anyone can inspect the rules and resulting positions.
What “anti-rug” means here
These are proposed constraints against privileged fund diversion and LP removal, not a claim of absolute safety. The final locking mechanism is not yet implemented. Market losses, issuer restrictions, bridge failures and contract vulnerabilities remain possible.
04 / OPEN REVIEWOpen to scrutiny.
Open to scrutiny.
Before funds move.
Inspect the design and the research behind it. The boundary between a local simulation and live execution should be as visible as the results.
NVDA research scenario8,000 USDC
A modeled purchase budget.
No real funds used.
Local guard checks15 / 15
Expected reverts verified.
Not a security audit.
Research scopeEVM fork
EVM fork
+ Core model
Real Core matching and automatic
withdrawal remain unverified.
| Component | Status | What this establishes |
|---|---|---|
| Mechanism specification | Reviewable | This design and its current limits are available for review. |
| Core execution prototype | Tests passed | Real CoreWriter bytecode on a local fork; Core balances, fills and fees are explicitly modeled. |
| Stock bridge & pool | Tests passed | Gateway payload, token delivery, pool creation and swaps checked locally. Cross-chain transport was simulated; test LP was withdrawable. |
| Live end-to-end execution | In progress | No real Core fill, automatic withdrawal or full cross-chain graduation has been completed. |
| Production contracts | In progress | Research code is not a production fundraising contract. |
| LP withdrawal restrictions | In progress | The final locking and permission rules still need implementation and verification. |
| Independent security audit | Not completed | Internal simulations do not replace independent review. |
Research you can inspect
SOL
Core execution prototypeResearch source · includes explicit Core model
JSONVerification summaryChecks, assumptions and outstanding work
Research only. Do not deploy this prototype to accept funds. Production source, addresses, LP custody and privileged permissions must be published before launch.
Protocol references
05 / QUESTIONS
A few things, made clear.
Does “anti-rug” mean a rug is impossible?
No. The requirement is to prevent creator or administrator withdrawals of liquidity principal and diversion of purchase funds. Those restrictions are not deployed yet. Even after implementation, they cannot eliminate issuer, bridge, market or smart-contract risk.
Does the project token cross chains?
No. In the proposed design, the project token stays on Elysium. Only the purchase funds travel out, and the acquired stock token comes back to seed the graduation pool.
Does bringing the stock to Ely take seven days?
The official bridge documents HyperEVM → Elysium deposits as typically taking about a minute. The multi-day withdrawal challenge period applies in the reverse direction. This is not a guaranteed delivery time, and it does not include procurement or retries. Read the bridge documentation
Can this all happen in one smart-contract transaction?
No. The design uses multiple asynchronous steps. A keeper can trigger bounded contract actions, but Relay still depends on quotes and external execution, Core must process orders, and the bridge must deliver its message. Contracts must verify each result before advancing.
What happens if a stock purchase or bridge step fails?
The intended state machine keeps graduation pending instead of claiming success. Partial-fill handling, timeout recovery, refunds and retry permissions are still implementation work. These rules must be finalized and reviewed before real fundraising.
Which stocks will be available?
NVDA is the first research example; SPY and QQQ are additional candidates. Launch eligibility will depend on the exact token version, supported Core and EVM links, bridge mapping, transferable balances and sufficient liquidity. Ticker names on the landing page are decorative, not a supported-asset list.
Built in the openKnow the rules.
Join the waitlist