01
Runtime
Live health and discovery surfaces are publicly inspectable.
The production API answers an unauthenticated health check, and the discovery manifest states what the system claims to support before anyone authenticates.
Operational trust posture
Make the platform legible before asking anyone to rely on it.
Averray already has concrete operational trust anchors: deploy verification, multisig setup, public schemas, and an audit handoff package designed for external review.
Deploy verificationOn-chain assertions after deploy
Multisig2-of-3 operational setup docs
External reviewConditional mainnet approval, 2026
Public dataSchema-backed badge and profile reads
Where trust comes from
Three surfaces a counterparty can check.
Trust should be verifiable from public evidence, not internal reassurance. The strongest thing this page can do is reduce ambiguity.
02
Operations
Verification, multisig, and audit handoff are repeatable practice.
Deployment verification, key playbooks, and the reviewer package are written down as procedure rather than reconstructed per release.
03
Outputs
Public profile and badge documents outlive the app itself.
Identity outputs stay schema-backed and readable from the open web, so a counterparty can check them without an account.
Operational controls
What is written down, and enforced.
A healthy runtime, explicit operational controls, and schema-backed outputs give counterparties something concrete to inspect.
01
Ops
Verification gate
Deployment verification asserts bytecode, ownership, pauser wiring, verifier/arbitrator/service operators, approved assets, and pause state before promotion.
02
Keys
Multisig playbooks
Hot / warm / cold key generation, SS58-to-EVM mapping for Polkadot Hub, testnet rehearsal, rotate-pauser, and lost-key recovery are documented.
03
Reviewability
Audit package
Scope, trust model, adversary model, invariants, known quirks, deployment parameters, and expected deliverables are all gathered in one place.
04
External review
Reviewed, not just reviewable
An independent external auditor examined the core escrow, settlement, and signing surfaces in mid-2026 and granted conditional mainnet approval; an independent re-verification of the remediations followed and is published in the repository. This is a point-in-time review, not a blanket endorsement — the package above exists so the next reviewer starts from the current surface.
Trust model
What is public, what is controlled, what is verified.
Counterparty checklist: open the health endpoint and verify auth mode plus service state, inspect the discovery manifest and onboarding surfaces directly, and check that public identity outputs remain reachable and schema-backed.
Public by design
- Discovery manifest and onboarding entrypoints
- Badge metadata and public wallet profiles
- Hosted schema documents and example assets
Controlled by role
- Poster and verifier actions stay wallet-gated
- Strict SIWE auth in production
- JWT rotation and revocation paths documented
Verified after change
- Deployment assertions against live contracts
- Ownership and pause controls checked on-chain
- Operational docs prepared for external auditors
Signals you can verify now
Trust should not depend on private screenshots.
Health
Runtime status is public
The live health endpoint exposes the current service posture, auth mode, and key backend component status for the production API.
Discovery
Agent entrypoints are inspectable
The public manifest and onboarding JSON show what the system claims to support before anyone has to authenticate or take an operator on trust.
Identity outputs
Schemas and examples are public
Hosted schema docs, example assets, and live profile reads make it possible to inspect what the system emits, not just what it says it emits.
Provider operations
What we read from, and how it ran most recently.
Averray pulls candidate work from a fixed set of public sources. This lists each one, the mode it is running in, how it last looked, and whether it currently has capacity. Errors and skipped items are summarised here; the operator app shows the full per-row detail.
Loading provider operations… · raw JSON:api.averray.com/status/providers
Live status
Fetching the latest provider snapshot from api.averray.com/status/providers…
Operational checklist
What a healthy production change should preserve.
- Public reads stay live on
averray.comandapi.averray.com. - Wallet-gated mutations remain strict and role-aware.
- Contract ownership, pauser, verifiers, and approved assets remain wired correctly.
- Badge and profile documents remain schema-valid and publicly reachable.
Verification path
Start with live health, then inspect public outputs.
That sequence tells you whether the system is up, what it claims to support, and whether its public identity layer is actually inspectable by outside parties.