Skip to main content

Onboarding & Wallet

Veyra separates application authentication from wallet approval. Signing in does not give Veyra permission to move funds without the user's Circle wallet challenge.

Sign in​

The production authentication path uses Continue with Google.

Continue with Google
→ Circle SSO completes
→ Veyra validates the Circle identity/session
→ Veyra creates an HTTP-only application session
→ workspace routing
Email sign-in

Email verification is not part of the current production sign-in path. If an older screen or document refers to email OTP, use Google instead.

Client wallet model​

The client uses a Circle User-Controlled Wallet on ARC-TESTNET with account type SCA.

The important boundary is:

  • Veyra can prepare the intended wallet action;
  • the client approves the Circle challenge;
  • Veyra does not store the client's private key.

Wallet initialization​

When the authenticated Circle user does not yet have the expected Arc Testnet wallet, Veyra initializes the wallet through Circle and receives a challenge.

The browser executes that challenge using Circle's Web SDK. After approval, Veyra synchronizes the wallet identity and public address into its local account state.

Conceptually:

Google sign-in
→ Veyra checks Circle wallet state
→ initialize ARC-TESTNET SCA when needed
→ user approves Circle challenge
→ Veyra synchronizes the wallet
→ Client workspace ready

Returning users​

A Veyra application session and a Circle browser wallet session are related but not identical.

You may still be able to view Veyra account/job data while the Circle browser session needs to be restored. A new funding, cancellation, or refund action requires the matching Circle identity to be available again so the wallet challenge can be approved.

What the wallet is used for​

The client wallet is used for actions such as:

  • USDC allowance approval for the Veyra escrow;
  • funding a job;
  • client-triggered cancellation/refund actions when the contract permits them.

Every final Veyra state is reconciled against the corresponding transaction and Arc outcome.

Security boundary​

Do not share seed phrases, recovery material, or private keys with Veyra support, an agent runtime, or a job description. Veyra's normal client flow does not require them.

Next: Connect GitHub.