Terms of Use and Privacy Policy

Elysian runs on Elysium mainnet, the chain Kinetiq built for the Hyperliquid ecosystem (an Arbitrum Orbit chain that settles to HyperEVM). HYPE on Elysium mainnet is real, and tokens launched here can lose all of their value. A confirmed transaction cannot be reversed, and this interface may be changed or withdrawn at any time.

You must be at least 18 years old to use this site. You must not use it from any jurisdiction where doing so is prohibited, and you are responsible for knowing whether that applies to you. We do not verify identity and we do not check location, so this is your representation, not our assessment.

Each token launches against a bonding curve priced in HYPE. The price follows a constant-product formula against the curve reserves, so it rises as tokens are bought and falls as they are sold. There is no presale and no team allocation, and the creator has no ability to withdraw the trading reserves: no function exists for it.

You pay and are paid in HYPE, the same HYPE that pays for gas on Elysium. Inside the contracts that HYPE is held as wrapped HYPE (WHYPE), the standard token form of HYPE, because the curve and the locked liquidity position account in it. The contracts wrap what you send and unwrap what they pay you, so you never hold, approve or unwrap WHYPE yourself. The tokens themselves are ordinary tokens in your wallet: a buy sends them to you, and a sell first asks your wallet to approve the contract that takes the amount you are selling (the curve, or the swap router once a token trades on its pool), then pays you the proceeds in HYPE.

Selling is never paused. A guardian can halt buys, and even while buys are halted the curve continues to honor sells. When a buy lifts the HYPE held in a token's curve (after the fee parts that leave it, section 4) to its graduation threshold, the token graduates; sells take HYPE back out, so they lower the progress. The same transaction normally migrates the reserves one way into a permanently locked liquidity position, opened at the curve's last price; the buy that crosses the threshold pays the network fee for that migration. Unsold tokens the position does not need to match that price are sent to a burn address, where no one can move them. Tokens bought back by a token's Buyback & Burn share go to the same address. If the migration does not complete in that transaction, the curve keeps trading until anyone triggers it separately, which the contracts allow only while the curve still holds at least its threshold: if sells take it below, buys have to lift it back first, so no migration opens the pool with less. Trading then continues on the pool. The migration cannot be reversed and the locked liquidity cannot be withdrawn.

A fee is charged on every buy and every sell, on the curve and, after graduation, on the pool. It has two parts, and the rates below are what a token launched now pays, read live from the contracts rather than written into this page. The platform share accrues to the treasury. Its rate is fixed for each token when the token launches: the token pays that rate on its curve and, after graduation, on its pool, and nothing can change it for that token; a change to the rate applies only to tokens launched after the change. The creator-directed share is split, once, by the token's creator when the token launches, between four uses, and is written into the token's contracts so that nobody can change it afterwards: the creator share accrues to the token's creator and is withdrawn as HYPE (for a token launched through this site, that creator is the token's fee vault, which shares it out as described below under Fee sharing); Buyback & Burn spends its part inside the same trade to buy the token and send it to a burn address no one controls; holder rewards are paid in HYPE to the token's holders in proportion to their balances and are claimed on the token page; LP Support is kept inside the curve, outside the HYPE that prices it, up to half of the curve's starting virtual HYPE, and the part of the fee past that cap buys back and burns instead; at graduation what was kept moves into the locked liquidity position with the reserves. Each token page shows its own split.

Buyback & Burn HYPE stays in the curve's reserve, which is what graduation is measured on, so trading the same tokens back and forth moves a token toward graduation through the buyback share paid (apart from a few wei of rounding): by less than that share when the tokens are bought and then sold back, and by more when they are sold and then bought back, because the buyback after a sale burns tokens at the lower price the sale left. Either way, doing that always costs more than buying the same amount outright.

The buyback runs after your trade, at the price your trade left, inside the same transaction, with no minimum of its own. Someone who buys just before your transaction and sells just after it can capture part of that buyback's price effect as well as part of your trade's; the minimum you set on your trade still limits what you receive.

Holder rewards are paid only to ordinary holders: the curve, the pool, the burn address and the protocol's own contracts hold tokens but earn nothing. A wallet keeps what it earned after it sells. A contract that holds tokens but cannot call the claim keeps its share in the token forever; nothing can sweep it. A token with holder rewards costs a little more gas on every transfer, because it records each holder's share. While almost no tokens are in ordinary hands (under 0.01% of the supply, as when a token launches with its creator's first buy), the holder rewards part of a trade is held in the token and paid to whoever holds when the next trade pays its own. So when a creator makes a first buy at launch, the creator is normally the only holder at the next trade, and normally receives both the holder rewards part of that first buy and the whole holder rewards part of the next trade.

Once a token has migrated, it trades on its Uniswap V4 pool, through this interface's swap router or any other router, and the pool's own contract takes the same two parts in HYPE on every buy and sell: the platform share at the token's own launch rate, and the token's same four-way split. Its Buyback & Burn part is swapped into the token in the same transaction and burned. Its LP Support part is mostly swapped into the token and added to the token's locked liquidity position, which no one can withdraw; when that cannot happen in a swap, it buys back and burns instead. The pool charges no fee of its own, so these swaps pay nothing more, and adding liquidity in a swap costs that swap more gas, which the trader pays. A pool records its token's platform share and split when it graduates and charges them for good: no role can change either (section 5). The contract code limits the platform share to at most 1%, and to at most 2% with the token's split. Whatever estimate this interface shows before you sign, every trade carries the minimum you accept to receive, and the contract reverts the trade rather than pay you less.

Fee sharing. A token launched through this site has its own fee vault, a contract that is the token's creator on chain and so receives its whole creator share, on the curve and on the pool. The vault pays whoever launched the token a fixed launcher share of everything it receives, set for every launch when the contracts were deployed and read live below, and splits the rest between 1 to 100 earners the launcher named, by shares that add up to the whole. An earner can be a wallet, the wallet that holds an Elysian handle, or a wallet made in advance for an X or GitHub account through our login provider, Privy, which the account's owner reaches by logging in with that account on the claim page. Being named does not mean the person agreed to it or endorses the token. Each earner claims its own HYPE whenever it likes, and anyone may send a claim for an earner, which always pays the earner. The launcher is the token's fee admin: the admin can replace the list, hand the role to another wallet or give it up for good, and nothing else can change the list. A new list applies from the moment it is recorded; what anyone earned before stays theirs and stays claimable.

A launch through this site can also name an approved partner. The partner then receives part of the platform's fee on that token: the platform share described above, which the token's trades pay on its curve and, after graduation, on every swap of its pool, through any router. A graduated pool charges no trading fee of its own, so there is no other fee to share. The partner's part is taken at the rate approved when the token launched, which the contracts cap at half of the platform's fee, and the creator-directed share is not reduced. The fee-sharing contract this site launches through attaches the partner as the token launches, and only then. Partners are approved by the account that receives the platform share, and a launch naming one is refused until that account has switched partners on (section 5). The keys of wallets made in advance are held by Privy, a third party, and their owner can export a key from the claim page; Privy's own terms apply to its login.

The contracts cannot be upgraded: no one, including us, can replace their code. A few settings are held by roles, and this is everything each role can and cannot do, from the contracts themselves.

• Guardian. Can pause and unpause. A pause stops buys on every bonding curve and the creation of new tokens. It cannot stop sells (a sale's own Buyback & Burn part still runs inside it), trading on a graduated token's pool, creator fee withdrawals, holder rewards claims or token transfers, and it cannot change any setting or move any funds.
• Admin. Sets the platform share for tokens launched after the change (at most 1%, so that with the creator-directed share it is at most 2%); a token that already exists keeps its own on its curve and on its pool, even when it graduates after the change. Can also move, for later launches, the graduation threshold and the cap on a creator's own first buy, but only inside limits the contracts enforce: the threshold stays within 1% of three times the fixed virtual HYPE amount that sets every curve's starting price, and the cap can never let a creator's first buy take more than 15% of the supply. Grants and revokes the guardian and timelock roles. It cannot grant the role that lets the graduation contract open a graduated token's pool and record its creator, its split and its platform share: that role was given once, to that contract, at deployment, and no one can give it to anyone else, so no role can use it to block a graduation or to record a pool's terms itself.
• Timelock role. Can change a pool fee tier setting that this deployment's graduations do not use: its Uniswap V4 pools have no fee of their own. It cannot set any platform share: a pool charges its token's launch rate. It cannot choose where graduations go: the deployment fixed, for good, the one contract every graduating token migrates into (the one that opens its locked pool), and no role, this one and the admin included, can replace or disable it. (A guardian pause stops buys, and so the buy that would graduate a token, but never the migration of a token that has graduated.)
• Protocol recipient. The account that receives the platform share approves partners and sets their rates (at most half of the platform's fee), or withdraws an approval. A change applies only to launches that name the partner afterwards: a token keeps the rate it launched with, and an approval withdrawn later leaves its earlier launches paying. It also sets, once and for good, the one address allowed to attach a partner to a token, which is meant to be the fee-sharing contract this site launches through; until it has, no partner can be attached and a launch naming one is refused. A partner's part only ever comes out of the platform's fee. It cannot change any token's earners, its creator share or its split.
• Fee admin, one per token. Whoever launched a token through this site, until they hand the role on or give it up. Can replace that token's list of earners and their shares, and nothing else: not the split, not the launcher share, and not anything an earner has already earned.
• Pool manager. A graduated token's pool lives in a Uniswap V4 pool manager that other projects' pools share. Its owner, an account outside this platform, can switch on a protocol share of at most 0.1% of a swap's input on any of its pools, and nothing else: it cannot pause a pool, touch its liquidity or change the parts a pool of this platform charges.

Fixed for every token, whatever any role does: its supply (the token contract has no owner, and nothing can mint, burn, freeze or block transfers of it, and holder rewards never move anyone's balance); its fee split and its platform share, on its curve and, once it graduates, on its pool; its curve's graduation threshold, starting price and creator; where it goes when it graduates; its pool's terms once its pool is open (it charges no trading fee of its own); and the locked liquidity position, which no one can withdraw. A curve's reserves pay out only to sellers, and move only when it graduates, into that token's locked pool. No role can change a token's split, its platform share, its holder rewards or where its LP Support goes; no role can redirect a creator's fees or the treasury's recipient (a token's own fee admin can change who its fee vault pays, and only that); and no role can move anything out of your wallet.

Nothing on this site is financial, investment, legal, or tax advice, and nothing here is a recommendation to acquire or dispose of anything. We do not know your circumstances and we are not your advisor. Meme tokens are speculative by design, most lose value, and you are solely responsible for your own decisions and for any tax consequences of them.

Do not use this site to break the law, to impersonate anyone, to launch tokens infringing someone else's trademark or copyright, or to promote content that is illegal where you are. Do not attempt to disrupt the service.

The contracts are permissionless and cannot be upgraded: we cannot delete a token, reverse a trade, or recover funds sent in error, for you or for anyone else. The roles in section 5 hold settings, not your funds. What we control is this interface, and we may stop displaying a token here without that having any effect on the chain.

When you connect a wallet, this site sees its public address. That is the same address already published on a public blockchain by every transaction you have ever sent, so connecting reveals nothing that was previously private. We never see your private key or your seed phrase, and no part of this site asks for either. Every transaction is signed in your own wallet.

In your own browser, and never sent to us:

• Whether you have closed the welcome message.
• Which wallet addresses have acknowledged these terms on this device.
• Which creators you watch.
• Any profile picture you set for your wallet on this device.
• Your trade settings: the quick buy amounts, the slippage tolerance, and the tokens you chose to approve for selling without a limit.
• For each wallet whose own profile you view, the block the profile was up to when you last viewed it, so it can point out tokens that graduated since your last visit.
• The checks this site has already made against the chain for a token you trade, kept only until the tab closes, so a slow read later does not stop you selling.

Your browser also keeps cookies for two things: your wallet's connection state (which wallet is connected, and its address), and the colours you chose for rising and falling prices. They are sent to this site's own server with each page request and are used only to render the page that way: already connected, and in your colours. Clearing this site's browser data removes all of it.

Our service reads the public blockchain and serves it back. Beyond that, it keeps a small set of records of its own:

• A handle, if you claim one. It is stored against your wallet address, and anyone can look it up through our read service.
• For each image or token details document you publish from the create page: its content identifier, a fingerprint and the size of the file, the wallet address that published it, and when. A count of how many files each address has published that day is kept to enforce a daily limit.
• Reports of content. A report stores the reported content identifier, the reason you give, and when it arrived. It stores nothing that identifies who sent it: no wallet address and no IP address.
• A list of fingerprints of files that may not be published again.
• For each X or GitHub account a launcher names as a fee earner: the platform, the account's numeric id, its username, display name and picture link as the platform returned them, the wallet made for it, our login provider's id for it, and when it was looked up. This is public information about the account, kept so the same account is never given two wallets, and anyone can see through our read service which wallet a named account was given.

Signing in with your wallet (to claim a handle, publish a file or look up an account to name as a fee earner) creates a session that our service holds in memory only. It is never written to storage, and it ends after a day without use, after seven days at most, or whenever the service restarts. There is no account, no email and no password, because there are no accounts.

Using this site means sending requests to this site's own server and to our read service, and both necessarily see your IP address, as any web request does. Reads from the Elysium chain go through this site's own server, which forwards them to an Elysium RPC provider: our server sees each read, and the provider sees the reads arriving from our server. When you sign a transaction, your wallet sends it through whichever Elysium RPC endpoint your wallet is configured to use.

We count visits with Vercel Web Analytics, run by Vercel, which hosts this site. Each page you open sends Vercel the page's address, the page that linked to it, and your browser, operating system, device type and country, which Vercel works out from your IP address. It sets no cookie and stores nothing in your browser, and it tells visitors apart only by a hash that changes every day, so no visit can be tied to you or to an earlier visit. We see only the totals. It records no wallet address, and nothing you type or sign.

Files you publish from the create page are sent through our service to Pinata, a pinning provider, and published to IPFS, a public network where anyone can retrieve a file by its content identifier. Token images and details are fetched by our read service from public IPFS gateways and passed on to you, so your browser does not contact those gateways itself. Your wallet extension is a third party governed by its own policy, not this one.

When a launcher names an X or GitHub account, our service looks it up with that platform and with Privy, our login provider, which finds or creates the account's user and its wallet; those three see the lookup coming from our service. On the claim page, logging in goes to Privy and to the platform you log in with, and Privy may show a Cloudflare check; the wallet's key is held in Privy's own frame, on Privy's site, and this site never sees it. Privy's own privacy policy governs what it keeps.

The Connect wallet window is Reown's AppKit. It loads its typeface and the wallet list's names and pictures from Reown's servers, which see your IP address, and once a wallet is connected it may look that wallet's address up with them. If you connect with WalletConnect (a QR code, or a wallet app on your phone), the connection runs through WalletConnect's relay, run by Reown, which sees that this site and your wallet are talking and when; what they send each other is encrypted between the two. The window's own analytics are switched off. Reown's own privacy policy governs what it keeps.

Disconnect your wallet at any time from the wallet menu, and clear the browser-stored items above by clearing this site's browser data. There is no account to delete and no subscription to cancel. A handle, once claimed, stays bound to its wallet address: this site offers no way to change or release it. A published file is public on IPFS: we can stop pinning it, but copies others have made may remain. On-chain activity is public and permanent, and is beyond anyone's ability to erase, including ours.