Integration and monitoring
Read protocol state, submit authorized actions, and track obligations through final resolution.
Contracts record the authoritative state
Business Validator writes are role-scoped contract actions signed by an authorized operator or submitted through a permitted public entry point. The indexed API and dashboard make those records easier to inspect; they do not replace the contract's authorization checks.
Separate transaction submission from confirmation. After a write, inspect the receipt and resulting state, then allow for the indexer to catch up before expecting the dashboard to match.
Start with the testnet tools
- Dashboard: inspect the protocol information exposed by the application.
- Block explorer: inspect transactions, logs, and deployed contracts.
- Network metadata: inspect the API's environment metadata.
- Endpoint directory: find the REST API and application event WebSocket.
Confirm the chain and release before signing. A wallet connection and an API response do not prove that a BVID has been admitted or that a role can accept new volume.
Monitor obligations, not just balances
| Area | Information to track |
|---|---|
| Identity | Current operator, roles, and BVID status |
| Collateral | Posted and withdrawable stake, reservations, health, price freshness |
| Asset service | Metadata events, re-attestations, scoring coverage, and liability portfolios |
| Scoring | Publication cadence, evaluable cohorts, and completed evaluation results |
| Insurance | Policy ownership, expiry, claim state, and full-payment status |
| Enforcement | Provisional penalties, dispute deadlines, and final outcomes |
| Exit and rewards | Auction progress, remaining obligations, finalized epochs, and claims |
The protocol read API covers validators, assets, policies, claims, obligations, calibrations, disputes, reward epochs, auctions, and events. Use the verified contract reference for direct reads. A complete endpoint/schema catalogue remains pending.
Keepers provide progress
Many checks require a transaction after a deadline. Keepers watch for these conditions and submit calls that the contracts verify. They help the protocol progress; they do not make elapsed wall-clock time execute a transaction by itself.
Distinguish these calls from privileged inputs. Payment reporting and price updates use authorized sources. A general statement that all off-chain services are trustless would hide these dependencies.
Handle delayed and repeated observations
The indexer tracks canonical blocks and rebuilds projections after a detected reorganization. The application WebSocket supports event delivery, but it is not the chain's Ethereum subscription endpoint.
Reconcile against current state after a reconnect, avoid treating repeated events as new obligations, and record transaction and case identifiers in your operations system. An alert should point to a specific payment, penalty, dispute, or auction that an operator can inspect and act on.