Accord

01 Core Model

Accord gives programmable cells a controlled way to use external facts. The network request is converted into protocol state before it affects execution. Validators fetch the source, commit to their observation, reveal the response, and finalize a canonical result only when stake agreement is reached.

02 Data Flow

Accord finalization produces an OracleResult. Cell-specific settlement remains an application or ABI decision; the node finalizes the result and exposes it to execution.

03 Request Identity

Each request has a deterministic ID derived from the request fields. Validators observing the same URL, method, body, response format, and schema ID derive the same request identity.

04 URL Governance

Public external data access is governed by URL pattern proposals. A proposer posts a bond, validators vote by active stake, and approval requires two-thirds stake support. Approved patterns become eligible for public cell requests.

URL patterns support exact matches and wildcard suffixes such as https://api.example.com/*. Public cells use approved URL proposals. Private cells use the private visibility path.

05 Commit And Reveal

Accord uses commit-reveal to keep validator observations accountable. The commit phase records a hash of the validator key, request ID, response body, and HTTP status. The reveal phase submits the body and status. The chain recomputes the hash and counts only reveals that match their commits.

06 Response Formats

Cells can request the price normalization path by adding accord_format=price_usd to the URL. Validators remove that marker before making the upstream HTTP request.

https://api.example.com/btc.json?accord_format=price_usd

07 Schema Projection

Approved schemas allow Accord to project a JSON response to declared keys before finalization. Projection keeps only the fields that the cell declared and sorts them deterministically. Nested keys can be referenced with dot notation, such as data.price.

08 Axiom Cell Surface

Axiom cells use Accord through explicit request and read operations. The request path queues external data. The read path consumes a finalized result when quorum has produced one.

let req_id = accord::request("https://api.example.com/data.json", "GET", "");
let result = accord::read(req_id);

09 Return Codes

10 CLI Usage

The Axiom CLI exposes URL governance commands for operators and validators. Amounts are accepted in TRTH notation or raw axi notation where supported by the CLI parser.

Propose a URL pattern

axiom propose-url \
  --from ./operator.keys.json \
  --url-pattern "https://api.example.com/*" \
  --bond 1000 \
  --voting-period-blocks 7200

Vote as a validator

axiom vote-url \
  --from ./validator.keys.json \
  --url-pattern "https://api.example.com/*" \
  --approve true

Report a malicious URL pattern

axiom report-malicious-url \
  --from ./operator.keys.json \
  --url-pattern "https://api.example.com/*" \
  --evidence "provider returned manipulated settlement data"

11 Explorer And API

Accord activity appears as ordinary chain activity. Commits, reveals, URL proposals, votes, and reports carry transaction hashes, actors, block references, request IDs, and raw intent fields.

12 Operating Guidance

• Use URL proposals for public data dependencies that many cells or applications will rely on.
• Use schema projection for JSON APIs with extra fields, volatile metadata, or nested response shapes.
• Use PriceUsd for price feeds that need tolerance grouping and stake-weighted median finalization.
• Keep response bodies small and stable. Large responses are rejected by protocol limits.
• Design cells to handle ORACLE_PENDING and retry after finalization.
• Inspect commits and reveals in the explorer when diagnosing data finalization.