InterLayer Wallet
Gravity Testnet
Capability-gated product surface

One InterLayer account,
multiple execution paths
with honest runtime guardrails.

This wallet suite is built for the live Gravity Testnet using the public RPC, WSS, and VM endpoints from the current network topology. Native wallet flows are production-ready now, while multi-VM routes stay clearly marked as send-enabled, linked-only, or read-only according to live capability checks.

Network posture

Mainnet-grade behavior on a real testnet.

Live
Preferred RPC
https://rpc.interlayer.one
Preferred WSS
wss://ws.interlayer.one
VM hosts
EVM and SVM are exposed as active binding targets today. Move, CosmWasm, and PolkaVM remain visible but guarded until verified spend support is live.

Native account wallet

Create, import, recover, transfer IL, and manage canonical handles on the live Gravity Testnet.

Capability-aware bindings

EVM and SVM binding flows are exposed with explicit verification context, while unsupported routes stay gated.

Diagnostics and posture

The product now checks the live RPC, WSS, VM endpoints, and operator-facing wallet posture from inside the app.

Runtime reality

What this wallet claims, and what it refuses to fake.

The suite is already strong for native account operations, canonical handles, web and extension approval flows, and live endpoint diagnostics. Anything the chain does not safely expose yet stays visibly gated.

Live now

Native IL, handles, EVM/SVM binding studio, web and extension smoke coverage

Guarded

Move, CosmWasm, and PolkaVM remain linked or read-only until verified execution is live

Not claimed yet

MPC external-asset deposit addresses, cross-VM bundle spend, and unrestricted external-asset execution

Operator path

Run the wallet like a control surface.

Use the dashboard, address matrix, handles, diagnostics, and transfer preview to manage the live testnet with production-style visibility.

Launch scope

Production-ready for the current Gravity Testnet scope.

The suite is ready for native wallet use and guarded binding workflows today. The remaining gap is not the app shell anymore. It is the runtime-backed activation of broader MPC external-asset flows and cross-VM spend routes.

Release references

Privacy and support routes are now part of the shipped wallet surface.