Mainnet setup guide

Set up RuleWallet with real assets under explicit rules.

Follow one clear path from connecting your wallet to creating an account, setting limits, and authorizing a bounded schedule.

Open command center Open mainnet console Documentation

Choose your language

Simple and Pro expose the same mainnet capabilities. Only the wording changes.

Simple mode

Simple

Every feature in everyday language.

Pro

Contract and operator terminology.

Mainnet onboarding

Four steps from wallet to bounded automation.

Every state-changing step is simulated before your wallet opens.

Step 1

Connect to Robinhood Chain

Connect your wallet and switch to mainnet chain ID 4663. The interface reads your public address only.

Connect and continue

Step 2

Create a policy account

Deploy a personal non-upgradeable account with separate owner, guardian, agent, and approver addresses.

Create account

Step 3

Set spending rules

Enable assets and recipients, then set transaction, rolling, daily, weekly, monthly, and approval limits.

Configure rules

Step 4

Authorize exact automation

Sign an EIP-712 strategy that fixes the account, asset, recipient, amount, schedule, nonce, expiry, and execution cap.

Open strategy controls

Capabilities

One mainnet product, from account creation to recovery.

Personal accounts

Create named spending accounts without giving RuleWallet your private key.

Separate roles

Keep ownership, emergency pause, automation, and approvals intentionally separate.

Onchain budgets

The policy registry enforces merchant, asset, category, amount, and time limits.

Pause and recover

Stop automation, revoke agents, and keep wallet-signed owner withdrawal available.

Exact simulations

Review target, value, calldata, expected result, and gas before each wallet request.

Bounded schedules

Autonomous execution fails closed unless the production signer and infrastructure gates pass.

Robinhood Chain mainnet uses real assets

Review the chain, target, value, calldata, and expected result in every wallet prompt. Autonomous transfers remain fail-closed whenever a production gate is missing.

Complete setup

What happens from start to finish.

Each mutation is separately simulated and wallet-signed. The backend cannot bypass account policy.

1Connect ownerUse Robinhood Chain mainnet, chain ID 4663, from the wallet that will own the account.

2Deploy accountCreate the personal V3 account through the pinned factory with separate operational roles.

3Configure policyEnable canonical ETH or USDG and define merchants, categories, budgets, approvals, and time windows.

4Fund accountDeposit only after the deployed account and every role address have been verified.

5Authorize strategySign exact EIP-712 strategy data; the signature cannot change policy or expand authority.

6Monitor and recoverTrack receipts, rehearse pause and revocation, and confirm owner withdrawal before scaling.

Who can do what

Four roles. No shared super-key.

Wallet	Purpose	Boundary
Main wallet	Creates the account, chooses rules, authorizes plans, and withdraws funds.	Every owner change needs your wallet signature
Emergency wallet	Stops activity if something looks wrong.	Can pause but cannot take funds
Automation wallet	Makes only transfers that match every rule.	Cannot change rules or ownership
Payment reviewer	Reviews transfers above the amount you choose.	Cannot approve a transfer that breaks a hard limit

Quick answers

What to know before connecting and signing.

Which network does RuleWallet use?

Robinhood Chain mainnet only, chain ID 4663.

Does RuleWallet see my seed phrase?

No. Connection exposes a public address; owner signatures stay inside your wallet.

Can an agent spend everything?

No. Agent transfers require an active role, enabled asset, trusted recipient, sufficient limits, and any required approvals.

When can schedules run automatically?

Only when the owner-signed strategy, onchain policy, non-exportable signer, durable locks, RPC checks, and monitoring gates all pass.

No seed phrase entered into RuleWallet

Configure rules first. Fund last.

Start with the command center, verify every role, then use the separate mainnet console for exact wallet-signed actions.

Open command center Open mainnet console

Wallet

Purpose

Boundary

Main wallet

Creates the account, chooses rules, authorizes plans, and withdraws funds.

Every owner change needs your wallet signature

Emergency wallet

Stops activity if something looks wrong.

Can pause but cannot take funds

Automation wallet

Makes only transfers that match every rule.

Cannot change rules or ownership

Payment reviewer

Reviews transfers above the amount you choose.

Cannot approve a transfer that breaks a hard limit

Set up RuleWallet with real assets under explicit rules.

Four steps from wallet to bounded automation.

One mainnet product, from account creation to recovery.

What happens from start to finish.

Four roles. No shared super-key.

Quick answers

Configure rules first. Fund last.

Preparing RuleWallet

Set up RuleWallet with real assets under explicit rules.

Four steps from wallet to bounded automation.

One mainnet product, from account creation to recovery.

What happens from start to finish.

Four roles. No shared super-key.

Quick answers

Configure rules first. Fund last.