Documentation

NODERA app guide

The NODERA app turns short, plain-language intents into on-chain transactions. Each one is simulated against the live chain and checked against your own spending policy. Then your wallet asks you to sign.

01 Quick start

1. Open the app. Press Launch App anywhere on the website.
2. Connect your wallet. Click Connect wallet, top right. If your wallet is on another network, click Switch wallet to Robinhood Chain. The app adds the network for you if needed.
3. Start a session. In Policy, press Start 30-min session. Without an active session, no transfer can be signed.
4. Type an intent. For example balance or send 0.0001 ETH to 0x…, then press Simulate.
5. Review and sign. Check the preview and the policy checks, press Sign & send, then confirm in your wallet.

02 Connect a wallet

Any browser wallet that supports the standard wallet APIs (EIP-1193 / EIP-6963) works, for example MetaMask or Rabby. If several wallets are installed, the app lets you pick one. It remembers your choice and reconnects without a popup next time.

Add the network manually

If you prefer to add the network yourself, use these values:

To disconnect, open the address menu (top right) and choose Disconnect. This also asks your wallet to drop the app's permission, if the wallet supports it.

03 Token

No token contract has been published yet. Once it is, the official address will appear here and in the app.

When a token is set, the app's Token panel shows its name, symbol, total supply and your balance. Add token to wallet adds it to your wallet's asset list. You can also send it with intents (see below).

04 Intent console

Type a command into the console and press Simulate (or Enter). The chips under the input fill in common commands.

Rules

• Verbs: send, transfer and pay all work. The word to is optional.
• Amounts are decimal numbers. A comma also works as the decimal separator (0,5). You can use up to as many decimals as the asset has (18 for ETH).
• Asset: leave it out to send ETH. For the token, use its ticker (with or without $) or simply TOKEN.
• Recipient: a full 0x address (40 hex characters) or the name of a saved contact.
• Other commands: bal and balances work like balance. fee works like gas. inspect and lookup work like check.

05 Transaction pipeline

Every intent moves through the six stages shown above the console output. If a stage fails, the pipeline stops there and tells you why.

01 Decode

The text is matched against the intent rules.

02 Resolve

The recipient (address or contact), the asset and the exact amount are worked out. Sends to the zero address are refused.

03 Simulate

The real transaction is run against current chain state using eth_estimateGas, plus eth_call for tokens. This catches reverts, insufficient funds and tokens that would reject the transfer, before anything is signed.

04 Policy

Your session, limits and allowlist are checked (see Policy). Warnings, such as sending to yourself or to a contract, are shown but don't block the transfer.

05 Sign

The transaction goes to your wallet with a gas limit 20% above the estimate. Rejecting it in the wallet sends nothing.

06 Confirm

The app tracks the receipt until the transaction is mined (success or reverted). You can keep using the console in the meantime.

The preview shows the network, sender, recipient, estimated gas and fee, and your balance after the transfer. If you change your policy while a preview is open, the checks update immediately.

06 Policy & sessions

Policies are guardrails that stop mistakes before they reach your wallet. Every transfer must pass all of them.

Policies, session, contacts and today's spending are stored in this browser (localStorage). A different browser or device starts with the defaults.

07 Contacts

Save frequently used addresses under a short name, then use the name in intents: send 0.01 ETH to ops. Names may contain lowercase letters, numbers, - and _ (max 20 characters). Contacts also serve as the allowlist when Only send to saved contacts is on.

08 Activity

Every submitted transaction appears in Activity with its status (pending, success or failed) and a link to the explorer. Pending transactions keep being tracked after a page reload. Clear removes finished entries; pending ones stay.

09 Security model

• Keys stay in your wallet. The app asks your wallet to sign. It never sees or stores private keys or seed phrases. NODERA will never ask for your seed phrase.
• Read-only server. The NODERA server forwards only read and simulation calls to the network (see Public API). It cannot send transactions; requests that try are refused.
• Simulate first. Every transfer is simulated against live state before you're asked to sign.
• Verify in the wallet. Always compare the recipient and amount in your wallet's confirmation with the app's preview.
• Check the URL and CA. Only use the official website. Compare the token address with the one on this page.

10 Troubleshooting

11 Public API

Two endpoints are public. They're useful for integrations and monitoring.

GET /api/config

Public site configuration: contract address, X account, launch URL and network.

{
  "ca": "",
  "chain": "",
  "x": "",
  "xHandle": "",
  "launchUrl": "",
  "network": {
    "chainId": 4663,
    "name": "Robinhood Chain",
    "rpcUrl": "https://rpc.mainnet.chain.robinhood.com",
    "explorerUrl": "https://robinhoodchain.blockscout.com",
    "symbol": "ETH"
  }
}

POST /api/rpc

A read-only JSON-RPC proxy to the configured network. It accepts a single call or a batch of up to 20 calls, with Content-Type: application/json. The limit is 240 requests per minute per IP.

Allowed methods: eth_chainId, eth_blockNumber, eth_getBalance, eth_call, eth_estimateGas, eth_gasPrice, eth_maxPriorityFeePerGas, eth_getCode, eth_getTransactionReceipt, eth_getTransactionByHash, eth_getTransactionCount, eth_getBlockByNumber. Any other method returns 403.

curl -X POST http://localhost:3000/api/rpc \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'

12 Roadmap

These are planned and not available yet:

• SDK. The TypeScript snippet on the homepage (@nodera/sdk) shows the planned developer API. The package isn't published yet.
• AI intent parsing. Free-form language in place of the fixed rules described in Intent console.
• On-chain session keys. Limits enforced by a smart account rather than by the app.

Follow the official NODERA channels for announcements.