The Agentic Trust Gap
Every existing approach forces a tradeoff between autonomy, security, and privacy. AURA eliminates all three.
| Approach | The Reality | Status |
|---|---|---|
| Raw Key Access | One prompt injection or model bug drains the treasury. The agent holds the keys — there is no safety net. | CRITICAL RISK |
| Public Spending Limits | Limits visible on-chain let MEV bots read your strategy, front-run trades, and route around known thresholds. | EXPOSED |
| Centralized Approval Server | A single off-chain server decides every spend. It becomes the bottleneck, the honeypot, and the single point of failure. | FRAGILE |
| AURA — FHE + dWallet | Limits are encrypted ciphertexts. Policy runs over secrets via Ika Encrypt. Execution is co-signed by dWallet — no raw key, no readable limits, no central gatekeeper. | AUTONOMOUS |
Policy Evaluation
Over Encrypted State
AURA uses Fully Homomorphic Encryption (FHE) via Ika's Encrypt network. Daily limits, per-transaction caps, and running spend counters are stored as FHE scalar ciphertexts on-chain. The policy engine evaluates them without ever decrypting the values.
- Encrypted on-chain limitsSpending policy is stored as FHE scalar or vector ciphertexts. No validator or observer can read the actual values.
- Ika dWallet co-signingApproved proposals are co-signed by Ika dWallet records, enabling native multi-chain execution without raw key exposure.
- MEV-resistant by designHidden limits mean bots cannot calculate your thresholds, front-run your trades, or infer your strategy from on-chain data.
Built for real operators, not mock treasury demos
Every component is production-grade and deployed on Solana devnet. Cryptographic guarantees, not configuration flags.
FHE Encrypted Limits
Daily limits, per-transaction caps, and running spend counters stored as FHE scalar ciphertexts on-chain via Ika's Encrypt network. No validator, observer, or MEV bot can read the actual values.
dWallet Multi-Chain Execution
Approved proposals are co-signed by Ika dWallet records. Native execution on Ethereum, Bitcoin, Solana, Polygon, Arbitrum, and Optimism — no bridges, no raw key exposure.
17-Rule Policy Engine
Public rules evaluated locally before any FHE call: per-tx and daily limits, velocity, time windows, slippage, protocol allowlists, counterparty risk, reputation scaling, approval ladders, budget envelopes, swarm pool, and scoped pauses.
Agent Swarms
Multiple agents share a single treasury with a unified spending pool. Aggregate spend is tracked across all members — one agent can't exceed the collective cap.
Governance and Safety
Emergency multisig override, guardian co-signing, AI authority rotation, dangerous-config timelocks, session keys, and scoped pauses for break-glass scenarios.
Audit and Observability
Append-only audit trail, policy receipts, decision history, activity logs, health scoring, snapshots, and invariant reports — full operational visibility without exposing strategy.
Native Multi-Chain Settlement
Co-sign transactions directly on the destination layer via dWallet tech.
How AURA Works
From encrypted policy setup to multi-chain execution — every step is cryptographically enforced on Solana.
Encrypt Your Policy
Set daily limits, per-transaction caps, and spend counters. AURA encrypts these into FHE ciphertexts stored on-chain — no one can read the actual values, including validators.
Agent Proposes, FHE Decides
Your AI agent submits a transaction proposal. Ika's Encrypt network runs the policy graph over the encrypted values and returns an encrypted violation code — approved or denied, without revealing the limits.
dWallet Co-Signs, Chain Settles
Approved proposals are co-signed by an Ika dWallet record. The agent never holds a raw private key — execution happens natively on Ethereum, Bitcoin, Solana, and more.
Frequently Asked Questions
Everything you need to know about AURA's encrypted treasury guardrails and autonomous agent operations.
Ready to secure the agentic future?
Join the waitlist for the AURA v1 Mainnet release.