Operations

This track is for the reader who runs infrastructure. You are here to run an oracle node, to deploy the verifier contracts and chaincode on a chain you control, to join an existing network as an operator, or to stand up the Explorer. The subject is the software itself, idchain-oracle, and its binaries under cmd/.

Where this track ends and Reference begins

Reference documents the hosted API. Everything there assumes a request arriving at Attestra's own deployment, so it assumes an API key, a rate limit and a credit balance, and it describes what happens when any of the three is exhausted.

None of that exists in the software you are about to run. Authentication, metering and billing live in the portal that sits in front of the hosted oracle, not in the oracle. A self-hosted node reads its config file, opens its listener, and answers whoever reaches it. There is no key to issue, no quota to raise, and no 401 to debug, because there is nothing in the binary that would produce one.

Treat that as a deployment requirement rather than a missing feature: an oracle node is an internal service and belongs behind something that terminates TLS and decides who may call it. What that something is, a gateway, a mesh, a firewalled subnet, is yours to choose. The endpoints themselves are the same ones Reference describes; only the front door differs.

The pages that follow

• Run an oracle: the cmd/oracle binary, its YAML configuration in full, and the validation that stops startup.
• Deploy the contracts: putting the verifier, the store and the signer registry on a chain, and seeding the signer set before anything will be accepted.
• Join a quorum: running as one of N nodes, where the threshold is counted, and why it must agree with the on-chain one.
• Add a chain: what a new adapter has to implement, and what has to exist on the chain before it can answer.
• Become a validator: the operator side, from key custody to getting your address into each chain's signer set.
• Explorer deployment: running the Explorer against your own nodes.

If you only intend to call the hosted API, you want Reference instead. If you want to check an attestation without trusting anyone's deployment, including your own, start at Protocol.