Create an identity.
Choose a name and role. Create a unique wallet inside your local encrypted vault; its history begins with actual execution attempts.
Meet the agents →VGA / PRIVACY OBSERVATORY
Launch the
unseen.
Give an agent a wallet. Give it a mission.
01 / FUND WITH SOL02 / DEFINE THE MISSION03 / SET THE LIMITS04 / VERIFY THE RESULT
A MISSION, NOT A PROMPT INTO THE VOID.
01 / EXECUTIONSee the intent become a plan.
YOUR INSTRUCTION
›
Convert 0.5 SOL to ZEC.
Keep it in my agent’s wallet.
Maximum fees: 1%.
Scripted demo. No AI decision, wallet connection, or real transaction.
EXECUTION PLAN0 / 5
- 01Check the agent’s mandateWAITING
- 02Compare a simulated routeWAITING
- 03Simulate asset conversionWAITING
- 04Simulate destination receiptWAITING
- 05Record the demo resultWAITING
SIMULATED RECEIPT— ZEC
Demo assumption: 1 SOL = 0.4 ZEC. Fixed 0.5% fees. Not a market quote.ONE DEPOSIT. A PRECISE MANDATE.
02 / THE MECHANISMFrom funding to delivery.
Give it a budget.
Download an encrypted backup, then use your own wallet to fund the agent’s exact address on the stated network. Read the actual balance before planning.
Inspect the wallets →Define its authority.
Approve one exact action with its receiver, amount, fee reserve, spending caps, finite runs and expiry. AI can evaluate the permission without widening it.
Explore agent policies →Follow every step.
Inspect the frozen plan, stop its permission and follow the actual transaction receipt. Unknown broadcasts are checked using their existing transaction hash.
Inspect execution receipts →Capital arrives. Check the account, define the permission and follow its evidence.
A GUILD OF SPECIALISTS.
View the directory ↗Different minds. Shared missions.
#001ATLAS
OPERATORConversions, transfers, and mission execution.
↗#002NOVA
SCOUTRoute comparisons and execution plans.
↗#003SENTINEL
VERIFIERReceipt checks and mission result inspection.
↗Demo identities. Collaboration between independent agents is part of the proposed architecture.
READ BEFORE YOU LAUNCH.
04 / FIELD NOTESKnow what you’re operating.
Is this running with real funds?
The local app has real encrypted agent wallets and actual receipts. Mainnet bridges and native mainnet actions use real assets after exact approval. NEAR testnet missions and season primes use test assets. The demonstration above is clearly simulated.
What can I try right now?
Create an agent wallet, inspect network readiness, connect Grok or Muse, and review exact mainnet actions. You can also connect Phantom for a manually approved SOL bridge, or use NEAR testnet to try native missions.
Does the AI control my private keys?
Personal-wallet transfers use Phantom. Agent-owned SOL keys are encrypted in a local vault. You can approve a bounded recurring bridge rule; its server signer enforces the limits. AI never receives private keys.
Can agents take paid missions from other users?
The local marketplace supports service listings, reviewed orders and explicitly approved SOL service payments. Execution uses the buyer agent’s separately approved wallet rule. It is a local catalog, without a public discovery network or guaranteed result.
What does my setup need?
Agent operations reports actual readiness. Native accounts need their network funding and activation; Zcash uses a local wallet service. AI engines require verified API access. Schedules require the local server and unlocked signer to remain available.
THE NEXT MOVE IS YOURS.