VGA — LOCAL LIVE MISSIONS

1. Run Start-VGA.ps1 (Node.js 22+).
2. Open http://127.0.0.1:4391/explorer.html in a browser with Phantom.
3. Use Connections to test your own Meta or xAI API key, then assign the engine to an agent. API use may cost money.
4. Choose Live missions, connect Phantom, and enter a public destination you control.
5. Preview, then prepare. Review exact SOL amount, destination contract, minimum output, refund wallet and network fee. Approve in Phantom to submit a real transfer.
6. Track the deposit in Live missions. Export your receipt. Never resend while status is pending or unknown.

Only user-approved SOL-funded bridges are supported: Zcash ZEC, catalog-supported assets on Starknet, and wNEAR/NEAR/USDC on NEAR when available. wNEAR is wrapped NEAR. NEAR token accounts may require prior registration. Legacy sample balances remain simulated; the new network shows actual wallet jobs and finite heartbeat rules. The separate Agent wallets module supports encrypted local SOL wallets and bounded recurring bridges.

The provider does not report a complete bridge fee percentage. Preparation requires an explicit manual override of the agent total-fee rule for that transaction; the SOL network fee cap is enforced. The rate is not guaranteed until execution.

Optional server environment variables: SOLANA_RPC_URL (HTTPS mainnet endpoint), NEAR_INTENTS_API_KEY, XAI_API_KEY, MODEL_API_KEY. Provider keys remain in server memory; never put secrets in HTML or local storage.

A server restart expires prepared unsigned routes. Existing receipts remain in the browser and can still be checked by deposit address. Agent operations adds separately owned NEAR mainnet and Starknet mainnet wallets with bounded native actions. Zallet receiving accounts and inspection need a separately configured local wallet; autonomous outbound ZEC spending remains disabled. The original NEAR missions and seasons remain testnet.

AGENT-OWNED WALLETS
Open Agent wallets, create a vault password, then create a distinct SOL wallet for an agent. Download the encrypted backup before funding; keep its password separately. There is no password recovery. Restore by stopping the server and placing your encrypted backup at data/agents-vault.enc.json next to connector-server.cjs, then unlock with its original password. Never overwrite a newer vault without saving it first.

Autonomy requires an explicit exact rule: asset ID, recipient, fixed amount, per-transfer and rolling 24-hour caps including network fee reserve, minimum output, interval and expiry. Grok/Muse can only execute or wait within that rule. Fixed-rule mode uses no AI. The first scheduled run is after one minute. The vault locks after 30 minutes; the local server must remain running. Unlocking resumes unexpired enabled rules.

Unknown or pending deposits block another run. Interrupted jobs that were never submitted can be recovered without resending. Confirmed transfers and unknown submissions retain their spending reservations. No agent funds are sent by installation or wallet creation. SOL bridges deliver only the exact catalog-supported asset reviewed by the operator. Native STRK can fund an owned, verified Starknet account. The observed NEAR catalog supplies tokens such as wNEAR; native NEAR for activation and gas needs separate funding. Native actions have their own permissions, fees and receipts. Testnet wallets and seasons stay separate; outbound native ZEC signing is disabled.

GUILD NETWORK
The Mission board, Squads, Heartbeats, Reputation, Strategies and Marketplace use the local server. No sample jobs or profitability rankings appear in these views. Squad roles run quote, permission, signing and receipt checks around one authorized operator wallet. Grok/Muse decide execute or wait; the signing guard enforces the rule independently.

Each heartbeat has 1–1000 permitted checks. Started attempts including wait or blocked consume a run; initial pending/cap refusals do not. Pause/resume preserves the approved rule and remaining checks. The last run pauses the rule after finishing.

Strategy copies and imports contain only safe route parameters. They grant no permission and copy no recipient. Applying a strategy opens a wallet rule for a new destination, minimum output, preview and explicit consent.

The marketplace is local to this computer. Publish an offering with a verified agent wallet as fee recipient and a fixed SOL price (0 to 1 SOL). A free order needs no Phantom fee. Paid orders require a separate personal Phantom payment, exact-price review and Solana confirmation before one execution attempt is unlocked. The fee buys an attempt, not guaranteed delivery or an automatic refund. The buyer agent bridge budget remains separately approved. Pending/unknown payments cannot be paid again automatically.

Reputation counts actual source signatures and provider-reported outcomes. Source confirmation is checked by Solana RPC; destination completion is reported by the bridge provider and is not an independent destination-chain balance proof.

Catalog data lives in data/guild-network.json; wallet keys and execution history remain in the encrypted vault. Back up both files for local continuity. Runtime data is excluded from the distribution ZIP. This is a single local operator instance, with no public marketplace discovery, multi-user login or hosted always-on custody.

NATIVE NEAR TESTNET MISSIONS
Open NEAR missions, unlock the same encrypted vault and select an existing agent wallet. Create its separate NEAR testnet wallet after checking the explicit creation box. Its private key remains encrypted in the vault; the displayed 64-character implicit account is a public funding address. Download an updated encrypted vault backup after adding the NEAR key. Wallet creation grants no spending permission and sends no funds.

Fund the account with testnet NEAR before approving a mission. If a faucet does not accept a new implicit account, fund an existing testnet wallet with the faucet, then transfer testnet NEAR from that wallet to the agent’s exact 64-character account. The first funding transfer activates the implicit account. Use Check balance to verify the account and its available testnet balance. Send only testnet NEAR. A mainnet SOL-to-NEAR bridge delivers mainnet assets and cannot fund this native TESTNET wallet.

Write an exact instruction such as Send 0.01 NEAR to your-account.testnet, replacing the receiver with your own testnet account. Fixed-rule mode parses an exact instruction without an AI provider; connected Grok or Muse can propose a plan. The advanced form describes one contract receiver, one exact method, fixed JSON arguments, attached deposit and gas limit. A chat or advanced request produces a draft only: it never broadcasts a transaction or silently grants a wallet permission.

Review the frozen receiver, transfer amount or method/arguments/deposit, testnet network, live fee reserve and plan expiry. If the account is unfunded or the live preview fails, approval stays disabled and the fee is shown as unavailable. Fund the account and generate a fresh successful plan. Check the separate approval box and set the maximum cost per action including fee reserve, rolling 24-hour cap and maximum fee reserve. Approval permits only that exact frozen action. Each permission allows 1–20 runs and expires within 24 hours. Cadence 0 keeps execution manual; a cadence of 1–60 minutes authorizes finite scheduled repetitions while the vault is unlocked and the local server is running.

For a manual action, choose Review & run, review it again and check the independent one-run execution box. Before signing and broadcasting, the server rechecks the approved action, current permission, fee, balance, network and nonce. The receipt records the actual attempt and links to the same transaction on the NEAR testnet explorer. No fabricated success or profit score is assigned.

STOP / pause prevents further authorized broadcasts and remains available while a run is checking its conditions. It cannot cancel or reverse a transaction already broadcast. Paused, expired, exhausted or locked permissions cannot start a new broadcast. A pending or unknown receipt blocks another run; use Check status to reconcile the same transaction. Never send another payment merely because the request timed out. Signed native transactions are not stored in the browser and are never automatically resent.

This native module is testnet only. It does not sign on NEAR mainnet, Starknet or Zcash, and it does not add generic trading, arbitrary destination signing or a public hosted agent service. Existing mainnet bridge permissions remain separate.

MISSION ARENA / VERIFIED WORK
Open Mission Arena to publish a task from an existing exact wallet permission. Native tasks require one manual NEAR TESTNET run. Bridge tasks use a separately approved Solana MAINNET bridge rule; claiming holds its schedule for manual execution without increasing caps. Each task stays bound to its reviewed signing wallet. Only one live claim or unresolved arena attempt can occupy an agent. A finite lease can be released or expire before any attempt; an attempted task never re-enters the queue.

Claiming reserves work, not spending. Review the frozen action, caps and lease, then separately consent to its one execution. STOP revokes further signing/broadcast and cannot reverse funds already sent. Changed permissions, expired leases, closed seasons, pending receipts and unknown submissions block another attempt. Inspect the existing receipt after any uncertainty; installation and task creation never broadcast funds.

Verify native work against NEAR testnet RPC: exact sender, receiver, amount or method/arguments/deposit/gas, FINAL transaction and successful receipts. A successful contract call proves execution, not an inferred application or profit goal. Bridge proofs establish the Solana deposit and provider-reported destination completion; they do not independently prove destination balance. A transaction cannot credit two tasks.

OBSERVATORY
The live terminal reads observable wallet events while the vault is unlocked: balance/quote checks, decisions, signing, broadcast and receipts, with actual reserves and permission limits. It contains no private keys, signed transaction bytes or hidden model reasoning. Refresh reconciles existing evidence and never resends transactions.

AGENT FORKS / CAPABILITY LEVELS
Forks create a real new encrypted SOL wallet and, if the parent owns one, a separate NEAR testnet wallet. Role, engine and an optional strategy draft form its configuration; permissions, keys, funds, execution history and earned reputation are not copied. Create and approve the child's own plan before it operates. Levels derive from unique verified arena work: Observer, Transfer, ContractOperator and Coordinator. Levels never expand spending permissions. Download an updated encrypted vault backup after wallet or treasury creation.

FINITE SEASONS / TESTNET BOUNTIES
Create a season lasting 1–168 hours with its own encrypted NEAR TESTNET treasury. Fund its displayed exact public account manually with testnet NEAR, then Check funding. Mainnet SOL or NEAR cannot fund it. Bounties reserve only confirmed available treasury funds; additional funding must cover payment fees. This is a local custody treasury, not a deployed escrow smart contract. No payout or guaranteed return is created by a funding transfer.

Only verified work can earn a reserved bounty. Review the exact amount, worker recipient, fresh fee and treasury caps, then approve the separate single payment. Payouts use the real NEAR testnet signing adapter. They count as paid only after exact finalized chain evidence; pending or unknown outcomes cannot automatically retry. Payouts may settle earned work after a season ends. Closing a season stops new/unstarted work; an already broadcast task may still be verified. Leaderboards count verified work and finalized payouts. Installation sends no rewards or funds.

Arena data is in data/mission-arena.json; keys and signing history remain in the encrypted vault. Back up the arena catalog, guild catalog and encrypted vault together. The download ZIP includes no runtime catalogs, test wallets, credentials or signing data. The application remains a single local operator instance.

NATIVE OPERATIONS SETUP
Open explorer.html#agent-operations for actual wallet owners, provider status, native account setup, exact permissions and receipts. See NATIVE-AGENTS-SETUP.txt for the complete mainnet and local Zallet setup. The Starknet SDK 10.8.0 is bundled for Node.js; no node_modules or private runtime state is required in the download. Operating-system setup, wallet funding, account deployment and money-moving approvals remain explicit operator actions. The distribution includes code and assets only. It does not include any operator wallet, account, balance or execution history.
