RZRelayZero
RELAYZERO DOCUMENTATION · WEB PWA

Money moves by message.

RelayZero binds a verified phone to a recovery-owned, bounded smart wallet. Carrier SMS can initiate and confirm a payment without mobile data; signed packets can also be prepared and carried while every device is disconnected.

Ethereum logoSettles nativeETHTwilio logoCarrier messagingPowered by Twilio
The settlement boundary is always on-chain.

Offline preparation is not blockchain finality. A connected relay must eventually submit the immutable signed packet to Robinhood Chain mainnet.

01

Quick start

  1. 1
    Open the web wallet

    Create or import a locally encrypted EVM owner wallet.

  2. 2
    Verify a phone

    Receive a Twilio Verify code, then sign a non-spending phone-binding message.

  3. 3
    Review strict limits

    Deploy a recovery-owned smart wallet with per-payment, daily, lifetime, and fee caps.

  4. 4
    Fund the SMS wallet

    Deposit native ETH on Robinhood Chain mainnet to the displayed smart-wallet address.

  5. 5
    Text RelayZero

    Use BALANCE, SEND, HISTORY, LIMITS, LOCK, or HELP from the verified number.

Start in the app
02

SMS command reference

Commands are normalized and authenticated against the sender’s private phone binding. A SEND command prepares a proposal; it does not spend until the exact confirmation code returns from the same registered sender.

BALANCERead the bounded SMS smart-wallet balance.
P 0.001 0x…Short carrier-friendly address transfer command.
P 0.001 +1…Short carrier-friendly registered-phone transfer command.
SEND 0.001 ETH TO 0x…Prepare an exact address transfer for confirmation.
SEND 0.001 ETH TO +1…Resolve a registered phone recipient and prepare a transfer.
YES 123456Approve one exact, unexpired SMS proposal.
NOCancel the pending proposal. Never text CANCEL; carriers reserve it for opt-out.
HISTORYReturn the authenticated recent SMS activity snapshot.
LIMITSRead the currently approved contract limits.
LOCKDisable new SMS authorization at the RelayZero policy layer.
HELPList supported commands without moving funds.
One confirmation, one transaction.

Expired codes, wrong senders, changed amounts, duplicate webhooks, reused nonces, and out-of-policy fees fail closed.

03

Offline operation

SMS onlyWorks without mobile data

The phone talks to the carrier. Twilio and RelayZero still need connected infrastructure.

Fully disconnectedPrepare and carry

The installed PWA can unlock locally, prepare, sign, and retain a bounded packet.

Connectivity returnsRelay and settle

A connected device validates the packet, submits once, and waits for chain confirmation.

Transport options include QR, encrypted JSON, copy and paste, Web NFC where supported, and the device share sheet. Transport can carry a signature but cannot rewrite its recipient, amount, chain, nonce, fee ceiling, or expiry.

04

Architecture

User boundaryLocal owner + verified phone
01
CoordinationTwilio webhook + policy engine
02
AuthorizationBounded smart-wallet executor
03
SettlementRobinhood Chain mainnet 4663

The server stores keyed phone digests and encrypted recovery material, not a public phone directory. The SMS executor is a restricted permission on a recovery-owned contract—not possession of the owner key.

05

Security model

Local custodyOwner secret material stays encrypted in the browser vault.
Bounded executionContract caps limit value, daily exposure, lifetime exposure, and network fees.
Recovery separationThe recovery owner can disable policy and permanently revoke the SMS executor.
Fail-closed relayUncertain submissions are not automatically rebroadcast.

LOCK immediately blocks new RelayZero SMS authorizations. Emergency recovery requires a fresh recovery-owner approval before an exact on-chain revocation transaction is prepared.

06

AI assistant boundary

The connected assistant uses DeepSeek through OpenRouter to explain RelayZero and build reviewable drafts. Deterministic command parsing remains available locally for supported exact commands.

Can explain, summarize, and draftYes
Can read or reveal owner secretsNo
Can sign, confirm SMS, change limits, or broadcastNo
07

Status language

01Prepared offline
02Signed offline
03Waiting for relay
04Submitted
05Confirmed on-chain

Submitted is not confirmed. Final receipts use the chain result; they never infer settlement from a signed message or a successful carrier delivery.

08

How it is built

Interface

Next.js App Router, React, TypeScript, Geist, composable CSS tokens, and progressive PWA behavior.

Chain access

Viem clients read Robinhood Chain 4663 through independent RPC paths and link to the mainnet explorer.

Messaging

Twilio Verify establishes phone possession. Signed webhooks, delivery receipts, replay defense, and idempotency protect SMS flows.

Testing

Type checks, deterministic unit tests, Playwright flows, production builds, and viewport checks cover the release.

09

Current limitations

  • Carrier SMS requires cellular service and supported carrier routing.
  • New phone registration and uncached phone-directory resolution require connectivity.
  • Mainnet settlement always requires some relay to regain internet access.
  • Browser NFC availability varies; QR, file, and copy transport are fallbacks.
  • The current settlement asset is native ETH on Robinhood Chain mainnet.
  • RelayZero does not claim offline blockchain finality, FHE, zero-knowledge privacy, swaps, bridges, or autonomous AI spending.