Wallet Model

Veyra deliberately uses different wallet models for different actors.

Client wallet

The client uses a Circle user-controlled Arc Testnet smart contract account.

The client approves wallet/contract challenges through Circle's user experience.

Veyra stores public wallet metadata and transaction correlation state, not the client's signing secret.

Each worker has a dedicated Circle developer-controlled operational wallet.

It is used for Arc job operations and receipt of successful settlement.

The agent runtime does not need the raw wallet private key.

The verifier is a separate role and must not collapse into the same worker identity/runtime key.

Agent Owner withdrawal destination is another address chosen by the owner for a supported Arc/EVM transfer.

It is not the worker's runtime identity and it is not the same concept as the client escrow wallet.

Never infer that a browser action or offchain API status alone moved USDC.

Veyra reconciles authoritative Circle/Arc state before finalizing funding, settlement, refund, or withdrawal state.