Execution Architecture
6 nodes: what each one does, what it is allowed to sign, and on which network it runs.
Activity by node · testnet
Testnet, no real value. Payments, receipts and payout runs come from the public reporting API; vaults are read from the verified contract. Mostly our own tests and workshops. Switch to MAIN to see mainnet.
Reading live data from the network. It can take a few seconds.
-
Vaults on the verified NiriumVault contract (since 9 Nov 2026)
Earlier contracts are listed on /security
Rebalance Node
MAINNET · INVITE-ONLYAutonomous rebalancing between USDC and CETES (Etherfuse) based on thresholds the vault owner sets, no human approval per call. Designed to run continuously; to date, 4 real rebalances, self-funded, all on 6 Aug 2026, none since.
Cycle / Trigger
Checks every 10 minutes by default - The vault's CETES rate reaches the owner's entry threshold (invest idle cash) or drops to the exit threshold (unwind); between the two, it does nothing
Authorized Action
Invest and Unwind between the vault's own strategies - no swaps, no destination address
Audit Trail
SHA-256 + IPFS anchor when a run is recorded (opt-in)
Disbursement Node (Bulk Payouts)
MAINNET · EARLY ACCESS · INVITE-ONLYDisburse 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) + USDC trustline the recipient adds and signs itself
Audit Trail
Immutable IPFS receipt per run (optional LCP legal layer - in legal review)
Policy Gate
SHIPPED · NPM PACKAGERoutes every outgoing x402 payment through your own policy engine before it is signed. Binds the ALLOW to the exact authorization (contract, amount, destination, nonce) via initX402({ policy }); a DENY, timeout, stale answer, or anything not bound to that exact payment signs nothing. Not a remote key-custody control: it wraps the signing call inside the same process that holds the key, so code with direct access to that signer can still bypass it.
Cycle / Trigger
Per x402 payment - Every outgoing x402Fetch() call
Authorized Action
Transfer-only (contract, amount, destination, nonce) - the policy engine never sees anything else
Audit Trail
Full decision record via onDecision (ALLOWED/SIGNED/DENY/TIMEOUT/...), kept by the integrator
Settlement Hub
MAINNETOn mainnet, Nirium's own x402 test endpoint (/premium/market, $0.05) settles on-chain; signals and execute answer 501 there without charging. x402Serve() lets you charge for your own API the same way. Third-party use on mainnet is not something we promote while its legal review closes, and compliance is the integrator's own responsibility.
Cycle / Trigger
On-demand - Paid HTTP requests (x402)
Authorized Action
Payment verification, on-chain settlement
Audit Trail
Payment receipt logged per call; the settlement hash is on Horizon
Audit Node
LIVE · MAINNETAnchors a record to IPFS as an immutable, publicly verifiable receipt when the caller asks for it (opt-in per call), and powers institutional-format exports. Optional Legal Context Protocol layer in legal review.
Cycle / Trigger
On request - A POST /api/audit/log call, opt-in per call
Authorized Action
IPFS pinning, report generation, signature verification
Audit Trail
Every anchored receipt is verifiable on IPFS by anyone
Vault Operations Node
TESTNET · CONTRACT ADMINEmergency controls of the NiriumVault contract. The contract supports a 2-of-3 pause (admin plus one cosigner), but the testnet deployment has no cosigners registered yet (checked on-chain, 8 Nov 2026), so today pausing or resuming takes the admin's signature alone. Each owner closes their own vault with their own signature. Never runs autonomously.
Cycle / Trigger
Manual only - Admin request (no cosigners registered yet)
Authorized Action
Contract pause/unpause · cosigner changes (admin only)
Audit Trail
Pause and unpause emit on-chain events
Security Status
Non-custodial nodes (settlement, audit, reporting) run on mainnet without holding funds. Payouts also runs on mainnet, invite-only while legal review closes. Treasury rebalancing runs on mainnet over DeFindex vaults (third-party, already audited), invite-only. NiriumVault, Nirium's own vault contract, has not yet undergone a formal third-party audit and stays on testnet until one is completed.
Agent log feed
Testnet and mainnet events mixed, each line tagged. Includes our own agent paying our own testnet endpoint.