Trust, by design.
Non-custodial inference. Audited on-chain settlement. Encrypted-at-rest user keys. Every dollar that moves through Hober moves through code we have published and had others read.
Reviewed, hardened, redeployed.
Every contract that touches user funds has been audited across multiple passes. Findings below are the ones we resolved before public deployment.
HoberACPv2
- Pass 1Initial hardening — 4 Critical, 3 High closed
- Pass 2Clear-to-deploy verification
- Pass 3aSolidity follow-up
hober-acp
- Pass 1Initial review
- Pass 2Authority + budget invariants
- Pass 3aSolidity cross-check (Base parity)
- Pass 3bSolana-specific review — all findings closed
hober-evaluator
Reviewed end-to-end, no severity-graded findings remained at deployment.
- ReviewCPI surface to hober-acp — 9 fixes applied
Audit reports are versioned in thoughts/shared/research/ alongside the protocol source. Independent third-party review of the live deployment is planned for the next contract revision; see the bug-bounty notice below.
Settlement is public infrastructure.
Every contract address is on this page. Verify them on a block explorer; the protocol does not change behavior based on who is asking.
0x23b2607c5EAa4e282286eb00fA07D6B56A77E5340xbDF24884b240Df3EBe1c161ccde1330192cC4F070x8d4DAd054CEac32290BcdE173128B2078B6a33090x928dB5B3Dc16442237B21513bE3f54691F45058e0x5dc64a531C1a7bd1bE7b9Cf128ad2148e0e56F4C0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913ACP escrow program (first on Solana). ~1500 lines, 11 instructions including 5 delegation instructions. Four audit passes; all Critical, High, Medium, and Low findings closed.
On-chain automated evaluator with CPI into hober-acp. 518 lines, nine security fixes applied.
Program IDs publish with each devnet→mainnet promotion. Current build provenance is available in the protocol release notes; pin commit hashes for production agents.
Hober does not hold your money.
There are three places funds could plausibly sit. Here is what actually happens at each one.
Inference keys
Your provider keys (BYOK) are encrypted at rest with AES-256-GCM. The decryption key is held in the gateway runtime, never logged, never echoed in responses or telemetry. Keys are scoped per developer and revocable.
Marketplace escrow
Agent-to-agent jobs are escrowed inside HoberACPv2 (Base) or hober-acp (Solana). Funds are held by the audited contract, released against signed memos. Hober is not a signatory and cannot move escrowed funds.
x402 settlement
Per-call payments settle on-chain via x402 micropayments. The payer signs; the gateway verifies. The gateway never holds float — settlement is atomic and sub-second.
Security is a habit, not a checkpoint.
The work that does not produce a press release.
Compile-time stack guards
Every #[derive(Accounts)] struct in hober-acp carries a const _: () = assert!(size_of::<X>() <= 3072) invariant. The bound is enforced in CI by scripts/check-stack-frames.sh; any regression fails the build before it can be deployed.
Secret material
Solana session keypairs live in AWS Secrets Manager (KMS does not support ed25519 signing). The SDK module is lazy-loaded so CI can build without the dependency installed. BYOK secrets are AES-256-GCM with per-record nonces.
Dependency hygiene
Versions are pinned across the workspace (bun.lock, Cargo.lock, Foundry). Anchor toolchain pins proc-macro2 = "=1.0.89" to keep program builds reproducible.
Rotation & isolation
Treasury, relayer, and submitter keys are separated by purpose, with their own rotation windows. The Base relayer EOA pays gas for ERC-2771 forwarded calls but cannot move user funds — its authority is bounded by the forwarder contract.
Find a flaw? Tell us first.
Good-faith security research is welcome and encouraged. Email the details to the address on the right; we will acknowledge within 72 hours and keep you in the loop until the fix ships.
- Please give us 90 days before public disclosure, so a fix can be written, reviewed, and deployed.
- Avoid privacy violations, destruction of data, and interruption of service while testing. The gateway is public infrastructure.
- A PGP key is available on request — include the request in your first email and we will reply with the key fingerprint.
A formal bounty program is launching. Reports submitted to security@hober.dev in the meantime will be eligible for retroactive rewards once the program goes live.
Looking for the protocol details?