Why choose Elyvatum for private self-custody?
No single device, server or seed phrase can move your funds. Two of three shards must agree, with policy checks and passkey recovery built in.
Stored on this device
One leaked key drains the wallet.
Single-key hot wallet
The whole private key lives in one browser or device, so one compromise can approve any transaction.
0.05 HYPE
Hardware wallet
Keeps the key offline, but adds device cost, firmware trust, shipping and a seed phrase to back up.
2-of-3 threshold quorum
Signing power is split between Shard A (device keystore), Shard B (co-signer policy engine) and Shard C (hardware passkey). No single party can move funds.
The 5-step signing pipeline
Each payment is an ERC-4337 UserOperation for your Elyvatum account on Elysium. Shards sign separately and only partial signatures meet.
Build
Prepares an unsigned UserOperation for a USDC, HYPE or kHYPE transfer, with a fresh stealth address for the recipient.
unsigned userOpHashClient sign
The client unlocks Shard A with device credentials (Keychain, DPAPI or libsecret) and signs the userOpHash.
sigA (65 bytes)Co-sign
The payload goes to the policy engine over TLS. It checks daily limits, velocity and allowlists, then signs with Shard B.
sigB (65 bytes)Combine
The two partial signatures merge into one threshold payload. The root key is never assembled.
sigA || sigB (130B)Settle
A bundler submits the operation to the EntryPoint and your account contract executes it. Gas is paid in HYPE, or sponsored if you stake $ELYV.
handleOps → ElysiumElysium specifications and endpoints
Co-signer engine API endpoints
| Method | Endpoint | Description | Payload / notes |
|---|---|---|---|
| GET | /health | Service health, version and Elysium chain check | { status: "ok", chain: "elysium" } |
| POST | /v1/wallets | Registers a new 2-of-3 threshold smart account | { address, shardAPubkey, shardBEncrypted, shardCPasskeyPubkey } |
| POST | /v1/cosign | Submits a UserOp for policy checks and the Shard B signature | { walletAddress, asset, amount, userOpHash, recipient } |
| POST | /v1/recover | Rotates onto a new device with Shard B + Shard C | { walletAddress, passkeyAssertion, newShardAPubkey } |
Private payments built for Elysium
Who paid whom stays off the block explorer. Balances live in your account; links between sender and receiver do not.
Private send
Pay a handle like @name.ely or any address. The payment goes to a one-time address, so the recipient's public wallet never appears.
Stealth receive
Share one handle. Every incoming payment lands on a new ERC-5564 stealth address that only your wallet can find and spend.
Download Elyvatum Desktop
The native command center for your shards, payments and policy. Mobile follows in a later phase.
Windows
Windows 10 and 11, x64.
macOS
Apple silicon and Intel.
Linux
Debian, Ubuntu and AppImage.
Bridge into Elysium and earn the spread back
Bridge through Elyvatum and 25% of the relayer spread comes back to you in $ELYV, claimable on Elysium.
Bridge through Elyvatum
Pick a route in the app. The spread is measured from the actual quote you received, not estimated after the fact.
Claim in $ELYV
Rebates collect in your account and can be claimed at any time, or staked straight away for gasless sends.
Add private payments to any Elysium app
A TypeScript SDK built on viem wraps the account contract, the shard flow and stealth addresses. MIT licensed.
Private send
Send to handles or addresses through one call.
Stealth receive
Generate invoices on one-time addresses.
In-wallet swaps
Route HYPE, kHYPE and USDC through Elysium pools.
Policy hooks
Set limits and allowlists for the co-signer.
Roadmap to native privacy
Custody first, then developers, then shielded balances.
Elysium custody MVP
ERC-4337 accounts, three-shard signing, passkey recovery and the desktop client.
Open SDK and developer ecosystem
TypeScript SDK, docs and example apps for Elysium builders.
Swaps and $ELYV staking
HYPE, kHYPE and USDC swaps; staking for sponsored gas.
Stealth receive and handles
ERC-5564 one-time addresses and @name.ely handles.
Privacy pools
Shielded balances so amounts stay private too.
Mobile and multichain
iOS and Android, plus rebates on more bridge routes.
Common questions
Can Elyvatum move my funds?
No. Elyvatum runs the co-signer that holds Shard B, but one shard alone cannot sign. Your device (Shard A) or your passkey (Shard C) must agree.
What if I lose my laptop?
Use your passkey (Shard C) with the co-signer (Shard B) to rotate onto a new device. The old Shard A is retired. There is no seed phrase to find.
What if the co-signer goes offline?
Shard A and Shard C can still sign together, so you can always move funds without us.
Are the amounts private?
At launch, private send and stealth receive hide who paid whom. Hiding amounts arrives with privacy pools in Phase 05.
Do I need HYPE for gas?
Yes, unless you stake $ELYV. Stakers get gas sponsored by the protocol, so they can send USDC without holding HYPE.
Build private payments on Elysium
Read the docs, explore the architecture and follow the roadmap to native privacy.