Execution Architecture
6 specialized nodes. Each with a defined role, authorized actions, and cryptographic audit trail.
Rebalance Node
LIVE · MAINNET · INVITE-ONLYAutonomous rebalancing between USDC and CETES (Etherfuse) based on operator thresholds. Operates 24/7 with zero human intervention.
Cycle / Trigger
Continuous / 24h active — Spread exceeds operator-configured threshold
Authorized Action
Invest and Unwind between the vault own strategies — no swaps, no destination address
Audit Trail
SHA-256 + IPFS anchor per execution
Disbursement Node (Bulk Payouts)
MAINNET · EARLY ACCESSDisburse funds from one treasury to up to 100 recipients (contractors, freelancers, B2B partners) in a single signed batch payment. Non-custodial — the company signs in its own wallet, Nirium never holds funds.
Cycle / Trigger
On-demand / per run — Company builds and signs a payout run
Authorized Action
Batch USDC/XLM payment (≤100 recipients) + sponsored USDC trustline onboarding
Audit Trail
Immutable IPFS receipt per run (optional LCP legal layer — in legal review)
Compliance Sentinel
PROPOSEDNot built. The intent is to validate every proposed transfer against a policy before it is signed. What exists today is the agent-to-agent x402 client pattern in coordinationService; the auditor endpoint it calls does not exist yet, and the call fails open by design so a downed auditor never blocks execution. Do not rely on this as a control.
Cycle / Trigger
Continuous — Any vault event
Authorized Action
Transaction validation, event filtering, policy enforcement
Audit Trail
Audit logs anchored on IPFS
Settlement Hub
LIVE · MAINNETOrchestrates x402 micro-billing and MPP Charge settlement, per request. Direct integration with the Horizon API.
Cycle / Trigger
On-demand — Authenticated API calls
Authorized Action
Payment verification, on-chain settlement
Audit Trail
Transaction hash anchored per payment
Audit Node
LIVE · MAINNETAnchors every operation to IPFS as an immutable, publicly verifiable receipt, and powers institutional-format exports. Optional Legal Context Protocol layer in legal review.
Cycle / Trigger
Continuous — Every signed execution
Authorized Action
IPFS pinning, report generation, signature verification
Audit Trail
Self-auditing — every report is verifiable on IPFS
Vault Operations Node
2-OF-3 MULTISIG · TESTNETCritical treasury operations requiring human 2-of-3 multisig authorization. This node never executes autonomously.
Cycle / Trigger
Manual only — Multisig request from Owner/Cosigners
Authorized Action
Protocol pause/unpause · cosigner changes · vault closure
Audit Trail
On-chain multisig event history
What we removed and why
Previous versions showed 26 experimental agent names (Astra, Titan, Eliza, etc.) running "spread condition" checks. These were testnet research nodes that confused the institutional narrative. The 6 nodes above represent the actual production architecture — each with a defined role, authorized scope, and audit trail.
Access Experimental LabsSecurity Status
Non-custodial nodes (settlement, audit, reporting) run on mainnet without holding funds. Payouts also runs on mainnet, invite-only while legal review closes. The treasury vault has not yet undergone a formal third-party audit and remains testnet-only until one is completed.