0R10N15-8374 — governed crossings for machines

0R10N15-8374 — governed-crossing endpoint (StegVerse LLC, 8374@StegVerse.ai)

What it is

Governed crossings for machine transactions. One receipt pair per crossing — ALLOW or NON-ALLOW — and the fee is paid either way. Pair-first: the proof issues on locally-decidable evidence at the crossing; settlement is an eventual leg, receipted when it lands.

The protocol

A machine submits a transaction or action for evaluation before it commits. Every submission is dispositioned under the ecosystem disposition grammar — ALLOW, DENY, or FAIL_CLOSED — and only an ALLOW commits, at the signing boundary the service controls; execution paths that do not pass through this evaluation are outside that boundary. Every crossing, including refusals, returns a dual-recorded, hash-chained receipt pair: one matched pair of records, one per side of the crossing, constituting a portable settlement proof that either side can verify against the chain’s anchors without trusting the other party’s internal log. The pair is issued locally and unconditionally at the crossing, before any network call; settlement is an eventual leg, receipted when it lands. A refused or fail-closed attempt likewise produces a receipt — the refusal record. Independent retention of the pair by the customer is not yet demonstrated; it is being established as separate work.

Availability is a property of the crossing, not of a destination: the 0R10N15 protocol is to be available at every crossing, on every rail.

The one promise

There is only one promise in this purview: evidence, in receipted interactions. No promise of revenue, outcomes, or adoption is made anywhere on this page or in any instance under it.

Terms (from the live offer)

Offer version 07 · receptor: exact on eip155:8453, asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913, payTo 0x7721aB66161e60fCcA59CCe2A86817cbdd9b16Be (fixed, server-side).

tiergovernance fee
full-evaluation15000 micro-USDC
receipt-only500 micro-USDC

Settlement charge: governance fee + settlement charge; the charge is quoted live at challenge time from Base gas conditions (86,679 gas units basis) and the live ETH/USD rate; under an egress outage the last successful quote is served with quote_stale: true

Live quote at page time: {"settlement_charge_micro_usdc": 1599, "gas_units_basis": 86679, "base_fee_per_gas_wei": 5000000, "priority_fee_per_gas_wei": 1000000, "max_fee_per_gas_wei": 11000000, "eth_usd": 1676.4, "quoted_at_unix": 1795314472, "quote_stale": false, "quote_ttl_seconds": 45, "formula": "ceil(gas_units_basis * (2*base_fee_per_gas + priority_fee_per_gas) * eth_usd / 1e18, to the next micro-USDC)"} · full terms at /offer.

How it works

  1. Challenge. An unpaid POST /crossing returns the 402 challenge (x402 v1 + v2), quoting the governance fee plus the settlement charge as one total.
  2. Authorization. The payer signs an EIP-3009 transferWithAuthorization for the quoted total; the payee is fixed server-side and cannot be redirected by the payer.
  3. Pair. The endpoint decides on locally-decidable predicates — signature recovery, receptor and amount match against its own offer, validity window, evidence rules, and the authorization's nonce checked against the registry the receipt chain itself is — and writes the receipt pair first, with settlement_state PENDING, before any network call.
  4. Settlement. The relayer submits on-chain; the outcome is appended as a record bound to the pair (SETTLEMENT, or SETTLEMENT-FAILURE on terminal on-chain failure). The pair's disposition never changes.

The outage property

When the network drops at the moment of a crossing, the crossing still completes: the pair is the proof, issued locally, and settlement waits for the network and lands exactly once. Pair-first is built and live in production (record, 2026-11-18). Proof: the outage battery, 8/8 run twice — RPC blackholed, the crossing returned ALLOW with its pair written PENDING, the same nonce re-presented was refused locally (PAYMENT_NONCE_REUSED), settlement on restore was exact, and replay verified MATCH including the outage pairs. The frozen test lets any framework run the same scenario: /frozen-test.

Live state

62 pairs · replay MATCH · terminal anchor 5513a484b9709c531143b886d47dc7d5cc75beec526ac0ffeac35d4759d64080 · settlement pending on 0 pairs (computed at page time; the full live determination is at /inspect).

Inspect and conform

Declared surfaces

The complete public surface of this origin. Every route named here is live; operator routes are not declared. The same index is carried in the root document's JSON form.

routepurpose
/this landing document: what 8374 is, the live terms, and this declared-surfaces index
/healthservice liveness and identity
/offerthe public offer: terms, tiers, and the declared receptor
/crossingthe governed-crossing receptor: POST a crossing (unpaid requests return the x402 402 challenge)
/openapi.jsonthe OpenAPI document for the crossing
/.well-known/x402the x402 resource list for directories, with the chain-export references
/inspectone-link live inspection and determination
/comparethe frozen test's comparison page: the reference result and the open reporting table
/conformancesuite, batteries, and discovery standing
/standardthe 8374 Standard: the predicates any announcing service may be evaluated against, and 8374's standing under them
/frozen-testthe frozen pair-first outage test document (byte-exact; hash it)
/verifyverify any x402 row: its terms and whether it publishes a replayable record
/verify/checkthe verify check API (JSON; ?url=<resource>)
/chainthe public chain export page: the receipt chain for independent recompute
/chain/export.ndjsonthe production receipt chain, exported live as NDJSON
/chain/manifest.jsonthe chain export manifest: counts, terminal anchor, file hashes
/chain/verifier.pythe standalone chain verifier: recompute the replay verdict locally
/routerthe router service document and route contract
/router/catalogthe router catalog: registered sellers and their provenance
/router/provenanceprovenance for a registered origin, recomputed from its record
/router/quotea routed-crossing quote
/router/registerfree self-serve seller registration (POST)
/router/routeroute a call through a registered seller (POST; two-leg governed crossing)
/router/discovery/resourcesthe Bazaar-schema discovery feed, generated live from the registry
/router/openapi.jsonthe router's OpenAPI document

Standing, per the /inspect determination: supported — functional, settled on-chain, chain integrity. Not claimed — external demand, profitability.

Contact: StegVerse on LinkedIn · stegverse@stegverse.org


Patent pending (U.S. Prov. App. No. 64/198,910) · StegVerse LLC · 8374@StegVerse.ai