df-elysium-core

Rust SDK for Elysium, Kinetiq's Arbitrum Orbit chain on HyperEVM: Nitro's JSON-RPC, ArbOS precompiles, gas, HyperEVM bridging, deploys and polling, with exact amounts, signing and native or wasm transports, on df-hyperliquid-core. Testnet only until Kinetiq publishes mainnet.

SDK

df-elysium-core
├── client          the Client, the network, sends with a kept nonce
│   ├── network     testnet: chain, nodes, explorer, faucet, HyperEVM and the rollup's contracts
│   ├── rpc         receipts with L1 gas, blocks with send roots, sync sends, log windows
│   ├── records     Nitro's receipts, blocks and transaction types
│   ├── method      typed calls, events and reads
│   ├── native      reqwest, from df-hyperliquid-core (feature native)
│   └── web         fetch, from df-hyperliquid-core (feature web)
├── nitro           ArbOS's precompiles and the NodeInterface
│   ├── sys         height, chain, ArbOS version, aliasing, the way out
│   ├── gas_info    prices, HyperEVM's data price, limits, backlog
│   ├── retryable   tickets: redeem, keep alive, cancel
│   ├── wasm        Stylus: activation, parameters, cache
│   ├── node        gas split, outbox proofs, batches, confirmations
│   └── owner       chain owners, fee accounts, scheduled upgrades, and the rest
├── gas             fee caps, estimates split between Elysium and HyperEVM, costs in HYPE
├── account         signers, the kept nonce
├── transfer        HYPE, ERC-20s, Multicall3, Permit2
├── bridge          HyperEVM and back
│   ├── deposit     HYPE in through the inbox, its hash on Elysium before it lands
│   ├── retryable   calls paid on HyperEVM, ticket ids, submission fees
│   ├── withdraw    HYPE and calls out through ArbSys
│   ├── claim       BoLD assertions, outbox proofs, execution
│   └── message     what the parent chain logged, aliasing
├── deploy          creations, CREATE2, Stylus, Sourcify verification
├── live            new heads and followed logs, polled
└── utils           addresses, decimals, hex, HYPE's units

flowchart TB
    app["<b>your app</b>"]

    subgraph sdk ["df-elysium-core"]
        direction TB
        domains["<b>nitro, gas, transfer</b><br/><b>bridge, deploy, live</b><br/>reads and calls"]
        client["<b>client</b><br/>sign, send, Nitro's RPC"]
    end

    subgraph hl ["df-hyperliquid-core"]
        direction LR
        evm["<b>client::evm</b><br/>RPC, ABI, RLP, EIP-1559"]
        keys["<b>account</b><br/>keys, signatures"]
        utils["<b>utils</b><br/>decimals, hex, keccak"]
    end

    subgraph chains ["Elysium and HyperEVM"]
        direction LR
        elysium["<b>Elysium</b><br/>99801"]
        hyperevm["<b>HyperEVM</b><br/>998: rollup, inbox, outbox"]
    end

    app --> domains
    app --> client
    domains --> client
    client --> evm
    client --> keys
    domains --> utils
    evm --> elysium
    evm --> hyperevm

Examples

Each runs against Elysium testnet. The ones that move funds sign with ELYSIUM_TEST_KEY (from the environment or the workspace's .env) and only send with --send; without it they prepare, simulate and print.

Reference app

packages/core/examples/reference-app is all of the above in one page in the browser: Leptos client side, the SDK over fetch, a burner key or the browser's wallet. Live at https://elysium-sdk-app.builder.markets. To run it locally:

rustup target add wasm32-unknown-unknown
cargo install wasm-bindgen-cli --version 0.2.129
brew install just binaryen
cd packages/core/examples/reference-app
just serve    # then open http://localhost:8080

Tests

packages/core
├── src/**/tests       unit: records, calldata, events, precompiles, bridge hashes and proofs, nonces, polling
├── tests
│   ├── conformance    transactions, CREATE2, calldata and events match viem and @arbitrum/sdk
│   ├── mocked         whole journeys through Client against a fake Elysium and HyperEVM
│   ├── live           testnet, read only: every read, every precompile, a real claim simulated
│   └── send           testnet, real transactions from the key in .env
├── fixtures           recorded Sourcify answers
└── vectors            recorded chain answers, and what other implementations produce