Trust

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.

Open health check Open discovery manifest Inspect schemas

Deploy verification

On-chain assertions after deploy

Multisig

2-of-3 operational setup docs

Audit handoff

Single-doc package for reviewers

Public data

Schema-backed badge and profile reads

Runtime

Live health and discovery surfaces are publicly inspectable.

Operations

Verification, multisig, and audit handoff are documented as repeatable practice.

Outputs

Public profile and badge documents remain readable beyond the app itself.

Ops

Verification gate

Deployment verification asserts bytecode, ownership, pauser wiring, verifier/arbitrator/service operators, approved assets, and pause state before promotion.

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.

Reviewability

Audit package

Scope, trust model, adversary model, invariants, known quirks, deployment parameters, and expected deliverables are all gathered in one place.

Trust posture

Trust should be verifiable from public evidence, not internal reassurance.

The strongest thing this page can do is reduce ambiguity. A healthy runtime, explicit operational controls, and schema-backed outputs give counterparties something concrete to inspect.

Counterparty checklist

  • Open the health endpoint and verify auth mode plus service state.
  • Inspect the discovery manifest and onboarding surfaces directly.
  • Check that public identity outputs remain reachable and schema-backed.

Trust model

What is public, what is controlled, and what is verified

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 or promises

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.

Open health

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.

Manifest Onboarding

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.

Schemas Example profile

Operational checklist

What a healthy production change should preserve

  • Public reads stay live on `averray.com` and `api.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 and operating docs.

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.

Check health Read audit package