ProtocolIntelligence Layer
Real-time operational view of NEXUS Finance on Arbitrum Sepolia. This page aggregates live protocol state, risk verdicts, oracle state, and collateral ratio into a single control surface. It is the primary surface for evaluating protocol state before acting.
Protocol state snapshot
Fetched directly from Arbitrum Sepolia on each request. Refreshes every 30 seconds. The panel below is the authoritative real-time view of protocol state.
Reading the verdict
The overall_verdict is a deterministic aggregation of three sovereignty pillars. It has three values. Each has specific operational meaning that should guide how integrations respond.
All three sovereignty pillars are in acceptable state. Protocol solvency is intact. Oracle is live. Collateral ratio is within defined safety parameters. No conditions require operator attention.
Integrations may proceed with full confidence in protocol state signals.
SOV_001 (Economic Constitution) is passing — no insolvency risk — but SOV_003 (Capital Adequacy) is failing. Typical causes: oracle stale, CR approaching minimum threshold, or testnet environment constraints.
Integrations should inspect the pillar details before acting. On testnet, WARN is the expected operating state.
SOV_001 (Economic Constitution) is failing. The protocol has breached its primary solvency invariant — collateral ratio below 100%, vault paused under distress, or a structural protocol failure.
Integrations that extend credit, accept NXUSD, or depend on protocol solvency should halt or restrict behavior immediately.
The verdict is derived from three sovereignty pillars. Each governs a distinct protocol invariant. All three are evaluated on every engine tick and exposed in the live status and audit packages.
overall_verdict: FAIL.overall_verdict: WARN./api/receipts.FAIL — overrides all other pillar statesWARN — degraded, not unsafePASS — regardless of SOV_005 stateoverall_verdict. Available independently in pillar data and audit packages.Where to go from here
This page is the central control surface. Each other section of the protocol specializes in a specific function. Use the map below to navigate based on what you need to do.
Intelligence surfaces
Four specialized surfaces extend the protocol intelligence layer. Each exposes a distinct function of the system at a level of detail suited to a specific role.
Live position management and structured testing against the deployed VaultManager contract. Deposit WETH, mint NXUSD, repay debt, and withdraw collateral. Follow structured flows and verify every state change across the full observability layer.
System-wide watchlist for undercollateralized positions. Enumerates all active vaults from on-chain Deposit logs, computes per-vault CR server-side, and classifies positions as safe, active, liquidatable, or oracle_stale. Updates every 30 seconds.
Canonical AUD_001 receipt packages generated hourly by the NEXUS-120 Engine via GitHub Actions. Each package contains a full protocol state snapshot, pillar verdicts, fail classification breakdown, and a SHA-256 hash for integrity verification.
Machine-readable protocol state via three REST endpoints. GET /api/status for live solvency signals, /api/vaults for per-position data, /api/receipts for engine-generated audit packages. No auth. Edge cached. Verdict semantics documented for programmatic use.
Oracle & data quality
All protocol operations — on-chain and off-chain — depend on a reliable ETH/USD price. The protocol uses a two-layer price stack with automatic fallback. Understanding oracle state is required to correctly interpret any data this system produces.
OracleModule.getPrice() — protocol-managed oracle with a freshness window enforced by maxDelay(). Reverts if the Chainlink feed has not updated within the window.AggregatorV3Interface.latestRoundData() directly on the Chainlink ETH/USD feed. Active when OracleModule reverts. No additional freshness enforcement applied.oracle_stale: true on all endpoints when OracleModule has reverted. Indicates fallback is active. Does not indicate the fallback price itself is unreliable.isLiquidatable() — will revert when oracle is stale. Use CR from the API instead.oracle_stale: falsePrimary oracle is returning a valid price within its freshness window. All CR computations use this price. On-chain operations including isLiquidatable() will not revert. Vault status classifications are fully reliable.
Liquidation keeper execution is safe. All API data can be acted upon.
oracle_stale: trueOracleModule has reverted. The API falls back to raw Chainlink feed data. CR computations are still valid — fallback price is on-chain — but on-chain protocol operations that invoke OracleModule will revert. Vault status classifications via the API remain accurate relative to the fallback price but may not match what the contract reports.
Expected steady state on Arbitrum Sepolia testnet. API data remains useful for monitoring. Liquidation execution requires caution.
eth_price_usd: 0Both OracleModule and the Chainlink fallback have failed or returned zero. CR computation is not possible. All vault statuses will reflect oracle_stale. The API returns the best available data but price and CR fields are not reliable.
Do not use CR or vault status data for any decision. Alert and halt integrations until a reliable price source is confirmed.
Testnet context & signal interpretation
This deployment is on Arbitrum Sepolia. All signals on this page are real protocol output from deployed contracts and a live engine. Some conditions are environment-driven. The table below defines what each observation means in this environment so the signals can be interpreted correctly.
The correct interpretation of the current WARN verdict on Arbitrum Sepolia is:
Protocol lifecycle validation
Every lifecycle stage executed on Arbitrum Sepolia with real transactions. No simulation. Each item below was validated against deployed contracts.
Deployment details
Protocol roadmap
All contracts are public and verified on Arbiscan. All audit packages are SHA-256 hashed and immutably committed to the public receipts repository. Both are independent of this site.