Documentation
Start here for a first session, the trading guide and the markets. The methodology, API and event references each have their own page.
A first session on Elysium mainnet: connect, claim test collateral, deposit, place an order. Every step is a transaction your wallet signs, and every page shows the transaction it sent.
faucet() mints 10,000 tUSD to the caller once every 24 hours. The Vault page has the button; the call is public if you prefer a script.What the terminal shows you before you sign
qty × price × IMF, rounded up), the taker fee (notional × takerFee, rounded up) and, for market orders, the worst price the engine will accept. The transaction is simulated first; a revert is explained in words (see the error dictionary) before the wallet ever opens.Two order kinds, four times in force, one flag. Everything below is enforced by the order book and the risk engine, not by the interface.
| Order | Behaviour | Rests in the book |
|---|---|---|
| Limit · GTC | Executes against resting orders that cross its price, then rests at its limit until filled, cancelled or expired. | Yes |
| Limit · IOC | Executes what crosses immediately; the remainder is cancelled in the same transaction. | No |
| Limit · FOK | Executes only if the whole quantity can fill at or better than the limit; otherwise the transaction reverts and nothing happens. | No |
| Limit · Post-only | Rests without executing. If it would cross the book the transaction reverts (PostOnlyWouldCross). Pays the maker fee when filled. | Yes |
| Market · IOC | An immediate limit at the mark moved by the market’s maximum impact (1% at launch), tightened by your protection price. Executes what it can; the rest is cancelled. | No |
| Market · FOK | The same protective limit, but all-or-nothing. | No |
A reduce-only order may only shrink the position you already hold in that market: it must be on the opposite side, no larger than the position, and the risk engine caps every fill at what is left to close. It reserves no collateral. When a market is in ReduceOnly status, only reduce-only orders are accepted. Use it to close without any risk of flipping.
cancelExpired, returning the collateral to its owner.Makers pay 0.02% (0.0002) and takers 0.05% (0.0005) of the filled notional at launch, charged from available collateral at the fill and split half to the insurance fund, half to protocol fees. The estimate shown before you sign uses the same rounding as the contract.
A fill on the same side increases your position and averages the entry price; a fill on the opposite side reduces it, realizing PnL at the fill price and releasing margin in proportion, and any excess opens the other way. You can add margin to a position at any time and remove it while the position stays above its initial requirement. Funding is settled whenever the position is touched. The methodology gives every formula with worked examples.
Thirteen launch markets in four asset classes, each with its own tick, lot, leverage and session. The live registry on the markets page is authoritative; this is the catalogue they were listed from.
| Market | Class | Max leverage | Tick | Lot | Max order | Session | Feed |
|---|---|---|---|---|---|---|---|
| BTC-USD | Crypto | 20x | 0.1 | 0.0001 | 10 | Continuous | hypercore:BTC |
| ETH-USD | Crypto | 20x | 0.01 | 0.001 | 200 | Continuous | hypercore:ETH |
| SOL-USD | Crypto | 20x | 0.001 | 0.01 | 5,000 | Continuous | hypercore:SOL |
| HYPE-USD | Crypto | 10x | 0.001 | 0.1 | 10,000 | Continuous | hypercore:HYPE |
| AAPL-USD | Equities | 10x | 0.01 | 0.01 | 2,000 | Mon–Fri, UTC | hypercore:xyz:AAPL |
| TSLA-USD | Equities | 10x | 0.01 | 0.01 | 2,000 | Mon–Fri, UTC | hypercore:xyz:TSLA |
| NVDA-USD | Equities | 10x | 0.01 | 0.01 | 5,000 | Mon–Fri, UTC | hypercore:xyz:NVDA |
| XAU-USD | Commodities | 10x | 0.1 | 0.001 | 100 | Mon–Fri, UTC | hypercore:xyz:GOLD |
| XAG-USD | Commodities | 10x | 0.001 | 0.1 | 10,000 | Mon–Fri, UTC | hypercore:xyz:SILVER |
| WTI-USD | Commodities | 10x | 0.01 | 0.01 | 5,000 | Mon–Fri, UTC | hypercore:xyz:CL |
| NG-USD | Commodities | 5x | 0.001 | 1 | 100,000 | Mon–Fri, UTC | hypercore:xyz:NATGAS |
| SPX-USD | Indices | 20x | 0.1 | 0.001 | 100 | Mon–Fri, UTC | hypercore:xyz:SP500 |
| XYZ100-USD | Indices | 20x | 1 | 0.001 | 50 | Mon–Fri, UTC | hypercore:xyz:XYZ100 |
Every launch market shares one policy: initial margin fraction = 1 / max leverage, maintenance = half of that; 60-minute funding capped at 0.0375% per interval (0.000375); a 1% liquidation fee split 50% to the liquidator; maker 0.02% (0.0002) and taker 0.05% (0.0005) with 50% of fees to the insurance fund; a 1% market-order impact cap and a 1% mark band; oracle deviation 2%, widening to 20% after a 2-hour gap, with 120 seconds to confirm a deviation. These are launch values, not a claim about production risk limits. Changes are permissioned and event-logged (RiskParamsUpdated, FeeParamsUpdated, ExecutionParamsUpdated).
Crypto markets are continuous. Scheduled markets are open Monday to Friday, 00:00 to 24:00 UTC, closed Saturday and Sunday; holidays are set per market and per UTC day by a market manager (HolidaySet). Outside the session no order can be placed or matched, but cancellation works, positions stay open with their margin, funding keeps accruing while the index is valid, and liquidation remains possible while the index is valid. If the feed stops publishing outside the session, the index goes stale after the heartbeat and the market halts, which also suspends liquidation and funding until a fresh price arrives; the reopening gap rule then allows a larger first move.
Market status is one of Inactive (listed, never traded), Active, ReduceOnly, Paused (by an administrator) and Halted (by the oracle or by bad debt). The market directory and the status page show it live.
Every calculation the protocol performs, with its formula, precision, rounding and worked examples.
REST and WebSocket, generated from the published contract between the API and this application.
Fourteen REST endpoints under /api/v1 for markets, order books, trades, candles, funding, accounts, history, protocol status, the insurance fund, liquidations and the leaderboard; one WebSocket with five channels. Every response says where its figures came from and at which block.
Every event of the four contracts, from the compiled ABIs, with what emits it and where the indexer puts it.
The chain is the record. If you want to verify a balance, a fill or a liquidation without trusting Elysta’s indexer, the event specification tells you which logs to read and how to interpret every field.
Short answers; each points at the rule that decides it.
Limit prices must sit within the market’s price band of the index (5% for crypto, 3% for scheduled markets at launch). A limit far from the index is almost always a typo, and a resting order far from the market would reserve collateral for nothing.
The matching budget (24 fills or 12 price levels per transaction) ran out while your order still crossed the book. Resting it would have left the book crossed, so the engine cancelled the remainder and released its reservation. Resubmit for the remaining quantity.
Yes, if the index is still valid. Liquidation checks the market status (not halted or inactive) and the index, not the session. Scheduled markets whose feed goes quiet outside the session become stale after the heartbeat and halt, in which case nothing can be liquidated until a fresh price arrives.
The vault’s token balance equals the sum of every account’s three buckets plus the insurance fund, protocol fees and the PnL pool. The status page reads solvency() on the vault and reports whether that equation holds at the block it was read.
From the index. With a one-sided or empty book the mark is the index itself, and with a two-sided book it is the mid clamped to ±1% around the index. The last trade never sets the mark.
The rate is settled into the market’s cumulative index every interval, but your position only pays or receives when it is touched (a fill, a margin change, a liquidation). The amount is exactly what accrued in between, so timing changes nothing.
No function allows it. The ledger is written only by the risk engine contract through documented settlements, and no role can edit a balance, force a fill or write a price. The one real power an administrator holds is role administration, which is why the roadmap puts a multisig and timelock in front of it before mainnet. The protocol page spells this out.
No. It is a test token with a public faucet, used so anyone can try the exchange without risking money. Elysta settles in it on every network it runs on today; gas on Elysium is paid in HYPE, which does have value.