Arc Testnet - intelligent self-custody

Self-custody on Arc, with intelligence at the point of action.

iArcana brings Vault, Circle-powered USDC flows and Mind into one wallet built for deliberate signing, readable operations and local control.

Arc
Core testnet
Circle
USDC rails
Mind
Built in

Local signing. Structured review. Mind where it matters.

Vault
Self-custody core
USDC
Circle-powered flows
Mind
Read-only intelligence
01 / VAULT

A focused self-custody home.

Wallets, balances, tokens and actions stay organized around the next decision, not scattered across disconnected screens.

  • Designed for repeated mobile workflows
  • Readable before the user signs
02 / ACTIVITY

History grouped around what really happened.

Explorer events and local Gateway records become a practical timeline, with details available when the user needs proof.

  • Designed for repeated mobile workflows
  • Readable before the user signs
03 / MIND

Contextual help inside the signing moment.

Mind opens over review screens and reads the operation in front of the user: route, fees, warnings and next steps.

  • Designed for repeated mobile workflows
  • Readable before the user signs
04 / HUB

Advanced controls without crowding the Vault.

Hub keeps Gateway, Bridge, approvals, Daily Briefs, WalletConnect and network settings in one operational surface.

  • Designed for repeated mobile workflows
  • Readable before the user signs
Meet Mind
01

Wallet data with a sharper lens.

Mind combines loaded wallet state with public Arc explorer data, so answers can cover transactions, contracts, routes and warnings without touching secrets.

What happened in this transaction?
MindI can read the hash, identify the method, trace token movement and summarize the result.
In context
02

Mind appears where decisions happen.

The chat opens over reviews, result screens, token details and activity details, then responds from the screen the user is already viewing.

Explain this Gateway Spend before I sign.
MindI can check amount, destination chain, gasless mode, fees, recipient and missing requirements.
Explorer aware
03

Contracts become readable.

For verified Arc contracts, Mind can inspect read functions, contract metadata and public address data without signing access.

What functions does this contract expose?
MindIf it is verified, I can list readable functions and translate what they return.
Risk checks
04

More than balances.

Mind can review approvals, connected dapps, suspicious contracts, swap routers, bridge groups and Gateway records from the data iArcana loads.

Is this approval risky?
MindI can compare allowance size, spender, token and known app data before you decide to revoke.
Secrets excluded
05

Private material stays out.

Seed phrases, private keys, passwords, vault keys, biometrics and API keys are never sent to Mind.

MindI can use loaded wallet data, but I cannot see or export your recovery phrase.
Circle rails

USDC movement without guesswork.

iArcana uses Circle Gateway for unified USDC balance and CCTP for bridge flows, then presents each operation before it becomes a signature.

Gateway

Deposit, spend and withdraw unified USDC with source and destination details visible.

CCTP Bridge

Bridge operations are grouped as one journey, while each hash stays available.

Destination checks

Mint requirements, gasless options and fees are surfaced before review.

Activity records

Explorer events and local Gateway records appear as wallet history the user can inspect.

Hub controls

The control room for advanced wallet work.

Hub gathers the tools that deserve their own space: approvals, WalletConnect, Daily Briefs, network settings and deeper activity views.

Approvals and revoke

Large allowances can be flagged, opened directly and revoked after the user reviews the spender.

WalletConnect risk

Connected dapps, requested chains and signing methods are shown before approval.

Daily Brief

Mind can generate scheduled wallet summaries in the language selected by the user.

Network settings

RPC URL, chain ID and explorer links can be adjusted when an endpoint fails.

Built secure

Self-custody first, intelligence second.

iArcana can guide complex actions, but private keys and recovery phrases stay local.

On-device keys

Generated or imported keys stay on the device and are used only inside signing flows.

Biometric gates

Sensitive actions can require biometric or password confirmation.

Screen protection

Screenshot and recording protection can be enabled from settings.

Mind boundaries

Mind receives wallet context, never private keys, seed phrases, passwords or API keys.

FAQ

Questions, answered.

The important details about custody, Mind and Circle rails.

Yes. iArcana keeps signing local. The wallet can create, import and restore accounts, but private keys and recovery phrases stay on the device and are never sent to Mind or remote services.
Mind can use loaded balances, activity, approvals, dapp sessions, Gateway records and public Arc explorer data. It can inspect transaction hashes, verified contracts and read-only contract functions, but it cannot access private material.
iArcana uses Circle Gateway for unified USDC flows and CCTP for bridge operations on supported testnet routes. Source chain, destination chain, fees and status are shown before the user signs.
Yes. iArcana supports WalletConnect sessions and signing flows. The wallet shows connected dapps, chains, methods and relevant warnings so users understand what a session can request.
Hub is where iArcana groups operational controls: Gateway, Bridge, approvals, revoke, WalletConnect, Daily Briefs and network settings. It keeps advanced wallet actions available without crowding the Vault.