Don't trust the badge.Open the evidence.
Explorer is where MIRCO turns status into proof. Network state, finality, execution, privacy, availability and external-data assurance remain separate — so “Ready” can always answer one question: why?
The network is presented as ready only when the selected operating model has enough live authority and its readiness gates are satisfied.
The selected BFT profile has enough reachable validator authority for quorum. Process health alone would not be enough.
Search the object.
Then inspect its proof path.
A block, transaction, address or network should not end in a detail page full of fields. Explorer should show the lifecycle that produced the current claim.
Authority and network context are identified before execution.
Execution result is recorded separately from consensus assurance.
Finality comes from the active consensus profile, not from a UI timer.
The explorer can now explain which assurance dimensions support “Finalized.”
Explorer presents the consequence and the evidence without collapsing distinct assurance dimensions.
Five dimensions.
Never one fake score.
Consensus, execution, external data, privacy and availability answer different questions. Explorer keeps them separate instead of inventing a single green “secure” badge.
External data can be useful.
It cannot silently become consensus.
What the adapter observed
XRPC or another external-network source can report balances, payments, fees, finality or events. Explorer should preserve provider, freshness and trust context.
What MIRCO can actually assert
MIRCO consensus remains independent of external providers. A source observation is presented as external-data assurance, not relabeled as native consensus truth.
Explorer should show uncertainty
instead of painting it green.
Unavailable privacy, stale external data, insufficient quorum or unreachable evidence should remain visible as the reason a claim cannot be made.
The correct explorer state is paused / insufficient quorum — not “degraded but finalized.”
The correct state is privacy unavailable. The transaction must not be shown as privately satisfied through a weaker fallback.
The observation may still be displayed, but its assurance state must remain stale / insufficient rather than “verified.”
Every important status
should survive the question: why?
Explorer closes the MIRCO core journey by turning network operation into inspectable evidence rather than decorative confidence.