The command bus
for Ethereum.
Control any backend with a signed transaction. Send JSON in calldata — your backend interprets it. Build anything. Your users never connect a wallet again.
Bring your own command language.
Define your own JSON commands and handlers on top of Keyless dApps. One engine runs everyone's app — spin up a game, a dApp, a vote, or an automation in minutes, with no protocol of your own.
Never connect a wallet again.
No Connect Wallet button. No session. No approve-this-site popups. Users sign and send a transaction from a wallet app, CLI, script, or agent. The frontend never touches keys.
From signed calldata to a real action.
A command is JSON in a signed transaction. The relayer reads it over WebSocket; the interpreter validates, authorizes, and executes. Try the simulated flow below.
Command Bus Demo
Build a JSON command, sign it, broadcast as calldata.
Press Build Command to begin
Build a JSON command and sign a transaction with the calldata. No connection.
A signed transaction in. A real action out.
Every command flows through the same path. Because it is signed, you get authentication for free. Because it is on-chain, you get ordering, timestamps and a public audit trail for free.
Relayer + interpreter
✓ LIVETestnet command bus on Sepolia. WebSocket stream with backfill — nothing missed.
Live console
✓ IN PROGRESSFire a command through the real interpreter and watch received → done in real time.
TypeScript SDK
✓ PLANNEDregisterApp, schema validation, authorization — your whole backend in one package.
On-chain receipts
✓ PLANNEDOptional provable round-trip from signed calldata to executed handler.
Hosted relayer
✓ PLANNEDManaged infrastructure so you focus on commands, not ops.
$KEY token
✓ PLANNEDERC-20 on Ethereum. Value from usage, not from a gate.
Transport
Calldata
JSON in signed tx
Auth
Signature
No wallet connect
Delivery
WebSocket
Ordered + backfill
Execution
Per-app serial
No command races
Frontend
100% static
Keys never touch UI
What makes Keyless dApps different?
Command bus architecture vs wallet-connect dApps vs calldata locked inside smart contracts only.
Commands
128
processed
Apps
4
active
Block
#21 356 402
Latency
~1.2s
Watch commands move from received to done.
The relayer streams signed transactions in real time. The interpreter validates schema, checks authorization, dedupes by tx hash, and executes handlers serially per app. Every step is visible — simulated here until the console ships.
$KEY network token.
Value from usage, not from a gate.
An ERC-20 on Ethereum. Protocol utility tied to relayer usage and hosted infrastructure — not a presale or insider allocation. Contract address announced at launch.
Network
Ethereum
Model
Fair Launch
Allocation
0% team
Verify now
Network token planned for mainnet.
Utility from relayer usage and hosted infrastructure. No presale. No whitelist. No team allocation at launch.
See it live.
No wallet required.
Open the console, fire a command through the interpreter, and watch it move from received to done in real time. Console shipping soon — try the demo above.