One for one.
How it works.

Wrap and unwrap

Native HYPE to WHYPE

Choose an amount of native HYPE. Sleeve prepares a payable deposit() call to the wrapper. Successful execution credits the same number of WHYPE units to your wallet.

WHYPE to native HYPE

Choose a WHYPE amount. Sleeve prepares withdraw(amount). Successful execution burns that wrapped balance and returns the matching native HYPE amount to the same wallet.

Neither action needs an ERC-20 spending approval. The 1:1 relationship describes HYPE units, not a dollar peg or yield. Network gas is additional.

The existing wrapper

0xbA876237B0F021A6c6D852d6c26E107997cC5E81 ↗

There is no new Sleeve contract, custody account or platform fee. Your wallet interacts directly with this existing third-party wrapper.

Sleeve checks the chain ID, wrapper runtime hash, implementation slot and implementation runtime hash before preparing an action. An unexpected change stops it. The wrapper is upgradeable. These checks do not remove contract, administrator or network risk.

Network delivery

Sleeve uses Elysium mainnet, chain 99901, with HYPE for gas. HyperEVM, chain 999, is the separate parent network with a separate HYPE balance. Sleeve does not bridge funds between them.

The web app submits through your selected EVM wallet. Early-access wallet RPC services may restrict transaction types or fail to relay them. A returned hash is not proof of execution.

Browser-wallet delivery for Sleeve has not yet been verified by a funded public transaction. When a submission is unclear, the app retains its record and asks you to check the original hash. Do not send the same operation again because a response timed out.

The optional local MAINNET launcher signs on your computer and can deliver a signed Elysium operation through the checked Inbox on HyperEVM. It consumes gas on both chains, requires explicit confirmation and does not deploy a new contract.

What Sleeve verifies

Confirmation requires a successful Elysium execution receipt, the exact owner, wrapper, amount and call data, plus the corresponding WHYPE mint or burn event. A receipt is checked against its canonical block.

Automated checks cover exact decimal conversion, request construction and receipt validation. A local fork test completed a wrap and unwrap against the pinned wrapper and implementation, restoring the wrapped balance and accounting for gas exactly.

Live chain and wrapper reads are verified separately. Local fork tests are not public transactions or an independent security audit. A Sleeve-funded public wrap and unwrap are still pending.

Your wallet stays yours

The website never asks for a private key. Your wallet confirms operations. Connected addresses, pending transaction hashes and operation amounts may be stored in this browser to recover an interrupted operation.

RPC operators receive the addresses and contract reads they serve. Blockchain transactions are public. Clearing a local record does not cancel an onchain operation.

Network reference

Kinetiq Elysium documentation ↗

Published network documentation can lag live infrastructure. Sleeve checks chain identity instead of choosing a network only by name.