Control is enforced on-chain, not promised.
VEYRA is built so that an agent can only do what its owners allowed, and so that the hard ceiling holds even if VEYRA itself misbehaves: it lives in the Squads multisig on Solana.
Who owns the capital?
The owners of the Squads v4 multisig. Funds sit in its vaults on Solana, and only owner wallets hold Vote permission.
Who may use it?
Agents you authorize. Each gets an executor key added as a multisig member with Initiate and Execute only. It can never vote.
Within what limits?
On-chain Squads spending limits per asset, per period and to allow-listed destinations, plus VEYRA policies evaluated before every signature.
Who approves exceptions?
Owners, with their wallets. Vault funds need an on-chain Squads proposal vote; agent-wallet swaps need a wallet-signed approval.
What happens before a signature?
Validation, deterministic policy evaluation, then simulation on mainnet compared with the declared intent. Any mismatch blocks.
How is it stopped?
Pause an agent, pause all execution, freeze a vault, or revoke the agent on-chain through the multisig.
How is it audited?
Every action is written to an append-only, hash-chained activity log, and every settlement carries its Solana signature.
Agents operate. Owners keep control. The chain enforces the ceiling.
Layered, so no single layer has to be perfect.
Squads v4 multisig accounts
Each account is a Squads v4 multisig on Solana mainnet. Owners hold Initiate, Vote and Execute. Agents are members without Vote, so they can never approve their own transactions.
Bounded executor keys
Executor keys are derived server-side with HKDF-SHA256 from a server secret and the agent id. They are never stored in the database. On-chain, each is bounded by Squads spending limits: amount per period, mint and a destination allow-list.
Deterministic policy engine
Limits, thresholds, assets, protocols, counterparties, actions, time windows, frequency and slippage are checked with fixed rules. No language model is in the decision path.
Simulation and intent matching
Every transaction is simulated against mainnet before signing. Programs, balance changes and slippage are compared with the declared intent. A mismatch blocks execution.
Owner approvals
Spends from vault funds above a threshold become on-chain Squads proposals that owners vote on. Swaps from an agent's working wallet and agent change requests use wallet-signed off-chain approvals.
Circuit breakers
Pause one agent. Pause all execution for the organization. Freeze a vault. Revoke an agent on-chain, which removes its executor and spending limits from the multisig.
Loop protection, rate limits, idempotency
Agents that exceed their action rate or repeat the same intent are paused for human review. Requests are rate limited per credential and organization. Idempotency keys make retries safe.
Append-only audit log
Activity events are hash-chained: each event commits to the previous one, so any edit or deletion breaks the chain. Integrity can be verified from the app.
Sign in with Solana
Owners sign in by signing a message with a short-lived, server-issued nonce. No passwords. Sessions are signed, http-only cookies.
Hashed credentials
API keys and agent session tokens are shown once and stored only as SHA-256 hashes. Session tokens are scoped to one agent, expire and can be revoked at any time.
Signed webhooks
Every delivery carries an HMAC-SHA256 signature over a timestamp and the body. Receivers verify in constant time and reject stale timestamps.
No seed phrases. Ever.
VEYRA never asks for a seed phrase or private key. Owners sign with their own wallets. Anyone asking for your seed phrase is not VEYRA.
What VEYRA is, and what it is not.
- VEYRA software is not a custodian.
Funds are held in your Squads vaults on Solana. Owners can move them with their wallets without VEYRA.
- Executor key security depends on the deployment.
Executor keys are derived from the deployment's VEYRA_SIGNER_SECRET. Whoever controls that secret can act as your agents, within their on-chain spending limits. Keep it in an HSM or a managed KMS, restrict access, and revoke and recreate agents if it is ever exposed.
- Limits are yours to set.
The on-chain spending limits you approve are the ceiling for each agent. Set them to an amount you are prepared to delegate per period.
- No audit or certification claims.
This page describes how the software is designed. It does not claim third-party audits or certifications for VEYRA.