Skip to content

Standards Engagement

Building agentic commerce in the open.

Rivier and Tenzro engage the standards bodies defining the agentic-payments stack — W3C, IETF, FIDO, Linux Foundation, ChainAgnostic, SatoshiLabs, and the working groups around x402, AP2, MPP, A2A, and ERC-8004. Below is the live log of what's filed, where, and what state it's in. Updated when GitHub state changes.

Rivier · RIVR (stablecoin & mandate-bound primitives)Tenzro · rail (chain identity, payment rails)

12

Active artifacts

12

Open · awaiting review

9

Tenzro · rail layer

3

Rivier · RIVR layer

Last checked 2026-05-02 · refresh against gh search prs --author=hilarl

Why two surfaces

Tenzro is the rail. Rivier is the stablecoin and the agentic-commerce layer that runs on it.

Both surfaces are authored by the same founding team. The standards work splits cleanly because the artifacts themselves do: a CAIP namespace registers a chain, an ERC drafts a token primitive, an x402 scheme defines a payment rule. Some belong to the chain layer; some belong to the stablecoin. Listed separately so the lineage is legible to anyone reading.

Tenzro · rail

Validator on the Canton Global Synchronizer and EVM/SVM chain. Standards work registers the chain identity (DID, SLIP-44, CAIP), wires it into agent payment rails (x402, MPP, A2A), and indexes it in ecosystem catalogues (ERC-8004).

Rivier · RIVR

USD-pegged settlement stablecoin with mandate validation, agent attestation, programmable batching, and continuous settlement streams as token-contract primitives. Standards work proposes the upstream protocol shapes (mandate-bound x402, AP2 on-chain binding) that RIVR's contracts already implement.

The Log

Active filings, grouped by body.

Every entry links directly to the GitHub artifact. State reflects the artifact's status as of 2026-05-02 — page is regenerable from gh search prs --author=hilarl.

W3C

Web identity, DID methods, verifiable credentials

1 filing

SatoshiLabs SLIPs

BIP-44 coin types and HD-wallet derivation paths

1 filing

ChainAgnostic CAIP

Chain-agnostic identifiers (CAIP-2/10/19/25)

1 filing

x402 Foundation (Linux Foundation)

HTTP-402 agentic-payment protocol

2 filings

Coinbase x402

Reference implementation of x402

1 filing

AP2 (Google Agentic Commerce, FIDO)

Agent Payments Protocol — mandate-bound auth

1 filing

A2A (Google Agentic Commerce)

Agent-to-agent protocol extensions

1 filing

verifiable-intent

Cross-protocol agentic-intent landscape

1 filing

Tempo MPP-specs (IETF)

Merchant Payment Protocol method specs

2 filings

awesome-erc8004

ERC-8004 ecosystem index

1 filing

What's Next

The recognition pathway from here.

The filings above register the rail layer and propose upstream agent-payment shapes. The RIVR-specific stablecoin pathway adds three more load-bearing artifacts. Listed without dates because they don't exist yet — the page updates when they ship.

  • Pending — Audit

    Trail of Bits / OpenZeppelin / Spearbit class audit of the RIVR launch contracts.

    113/113 forge tests pass today including the dryRun byte-equivalence invariant. Every subsequent submission cites the audit lineage.

  • Pending — ERC

    Ethereum Magicians thread → eips.ethereum.org draft for a Programmable Mandate-Bound Stablecoin Standard.

    The RIVR-named standards artifact. Generalises the transferWithMandate primitive so other stablecoins can adopt it.

  • Pending — Conferences

    Devcon 8 (Mumbai, Nov 2026) and Financial Cryptography 2027 (Tokyo, Apr 2027) CFP submissions.

    Merit-track venues, not sponsor slots. Talks cite the audit + ERC + the live deployment, not marketing announcements.

House Rules

How we contribute upstream.

  • Read CONTRIBUTING.md first. Every PR drafted only after direct verification of each project's CLA, DCO, signed-commits, AI policy, and merge style.
  • No spam. Filings staggered across weeks. One coherent change per artifact. Maintainer time is the scarce resource.
  • Status reflects reality. A PR is "open" until it isn't. We don't claim merged when in-flight, or in-flight when closed-for-scope.
  • Discussion before draft. Where the body requires it (Solana SIMD, Ethereum EIPs, OpenZeppelin scope), the discussion lands first; the draft only after engagement.

Engage

Working on the same standards? Let's compare notes.

If your team is on x402 / AP2 / MPP / A2A / ERC-8004 or shipping mandate-bound payment infrastructure, we'd like to read your work and share ours. Standards converge faster when the implementations talk.

standards@rivier.aiContact sales