Runtime evidence

The runtime describes itself.

Machine-readable contracts expose the node's exact public surface; the consensus manifest turns network cryptography into a verifiable inventory.

Node 0.5.0Schema 1265 RPC91 REST15 capabilities

Public-safe is not unrestricted. Privacy, safe-mode, read-only, quota, role and gateway policies can still mask or deny a listed surface.

Verified inventory

Node package
0.5.0
Runtime contract schema 1
RPC methods
265
Full inventory
REST routes
91
Transport endpoints counted separately
Capabilities
15
Status and maturity entries

From inventory to proof

The consensus manifest is a cryptographically verifiable inventory — a CBOM — that binds the node's cryptographic rules and runtime contracts into one agreed network description. Every node confirms the same description.

Coordinated manifest transitions make cryptographic change explicit: participants move together from one agreed inventory and ruleset to the next. The mechanism is public; exact release-identifying cryptographic values are not.

Read the CBOM architecture

Public machine-readable summaries

Surface summary

node-runtime-surface-contract.json

Public counts, policy categories and public-safe method and route lists.

Capability summary

node-runtime-capabilities.json

All 15 capability labels with status, maturity, exposure and precise publication wording.

Release summary

node-release-manifest.json

Version, schema, chain ID and inventory counters only.