Aleo Shield proves a transaction was private. HiveWallet proves it was authorized, the agent was not compromised, and the record is complete. Three cryptographic proofs at the moment of signing. One self-verifying receipt. Regulators verify the math themselves — no trust required.
Not a new chain. Not a token. Not custodial. A wallet layer that wraps Base L2, Aleo, and Canton with behavioral attestation at the moment of signing.
For consumer transactions, privacy is the priority. For enterprise agents moving regulated value where regulators can subpoena records and fiduciaries have legal obligations, integrity is more valuable than privacy. A tier-one investment bank's autonomous trading agent moving $50M is not trying to hide the trade. It is trying to prove it was done correctly.
Aleo Shield and HiveWallet are not competitors — they are complementary. An Aleo transaction with a HiveWallet receipt is private and provably legitimate. That combination does not exist anywhere else.
Every HiveWallet transaction emits one receipt carrying three independent proofs. Each is signed end-to-end with Ed25519. Each is verifiable against the agent's public key. None of them require trusting Hive.
Six independent guard layers cleared this transaction before execution. The receipt records which layers ran, which passed, and what the L4 anomaly score was.
shod_receipt: {
layers_passed: ["L1","L2","L3","L4","L5"],
l4_anomaly_score: 0.00,
final_decision: "APPROVED",
shod_signature: "ed25519:..."
}
Behavioral fingerprint captured within 30 seconds of signing. Frequency-domain hash of the agent's compute pattern. Proves the agent was not under prompt injection or model poisoning at the moment it authorized the transfer.
spectral_ticket: {
behavioral_fingerprint: "0x7f3a...",
anomaly_score: 0.02,
model_id: "claude-sonnet-4",
timestamp_captured: "<30s",
zk_proof: "..."
}
Each transaction commits to the previous entry's hash. The chain is self-authenticating against the DID's public key. No entry can be modified without breaking the chain. ViewKey gives regulators selective access without exposing the agent's full history.
ctef_entry: {
chain_position: 847,
previous_hash: "0xc1d8...",
entry_hash: "0xa940...",
chain_intact: true,
ctef_signature: "ed25519:..."
}
The full surface of HiveWallet at hive-mcp-wallet.onrender.com. Every transfer endpoint is gated by SHOD + Spectral-ZK + CTEF before settlement.
Pricing is not per transaction. It is per wallet per month — once an enterprise deploys HiveWallet for their agent fleet, every transaction that fleet ever makes generates a HiveDNA proof. Every proof requires HiveWallet. The infrastructure is permanent.
Every enterprise agent that moves value needs a wallet. Currently they use standard crypto wallets or custodial solutions. Neither produces behavioral attestation. HiveWallet is the wallet that compliance-requiring enterprises actually need — not because it is private, because it is provably legitimate.
Once an enterprise deploys HiveWallet for their agent fleet, every transaction that fleet ever makes generates a HiveDNA proof. Every proof requires HiveWallet. Every HiveWallet requires a subscription. The subscription never stops because the transactions never stop.
No signup. No mock. The button below calls the live wallet_info tool on hive-mcp-wallet.onrender.com and returns the verifier public key your software will pin. This is the same endpoint Claude, Cursor, and Cline talk to.
// click the button above to hit the live MCP server // real rails — no mock, no simulation
Want the full surface? Add HiveWallet to Claude Desktop or Cursor as an MCP server pointing at https://hive-mcp-wallet.onrender.com/mcp — you get all five tools, including wallet_provision ($0.01 USDC via x402) and wallet_transfer.
The compliance revenue funds the wallet development. The wallet makes the compliance revenue permanent. The sequence matters. Spec is complete. Trigger ships when the first HiveAudit client signs.