Voidnx Chain — testnet live

If it isn't compliant, it doesn't move.

Architecture decisions and software supply chain packages become EIP-7943 tokens with verifiable custody. The contract self-regulates: an unreviewed AI decision auto-freezes, a dependency with an open CVE is force-quarantined — no intermediary, no override. zk proofs verify compliance without exposing data. Anchored to Ethereum, time-proofed on Bitcoin.

adr-ledger beta Explore the protocol

EIP-7943 (uRWA) · zk proofs · software supply chain custody · open-source Rust clients

Built on proven, open standards

EIP-7943zk proofsOP StackEthereum L1Bitcoin · OTSNix · flake.lockOPA · RegoGrype · SBOMEd25519Chain of custody

How the protocol works

Three views of one guarantee

The same primitive — an EIP-7943 token whose transfer is gated by compliance state — applied to architecture decisions, your software supply chain, and the full lifecycle of a record. Explore each view; click any component for its architecture.

Hover any node to inspect it. Click a component to open its full architecture.

ADRToken (EIP-7943) lives inside an OP Stack L2 executed by op-reth. Every transfer runs through canSend / canReceive and a frozen check, with policy supplied by owasaka and roles split across MINTER, ENFORCER and COMPLIANCE. The chain settles to Ethereum and notarizes to Bitcoin.

EIP-7943 asset

Execution / index

Anchor / scan

Rust client

Compliance policy

Human review

Frozen / quarantine

The six primitives

Custody, compliance, and trust — verified end to end

The contract self-regulates. Make the artifact a token, chain its custody, gate movement on compliance, verify without exposing. No company enforces it — the protocol does.

Tokenize the artifact

Architecture decisions and software packages are minted as EIP-7943 tokens. Identity is deterministic — tokenId is keccak256 of the content, creating an immutable chain of custody from source to deployment.

Chain of custody

Every artifact carries its full provenance: who authored it, when it was anchored, which dependencies it trusts. The supply chain becomes a verifiable graph where each node is a token with traceable lineage.

Gate transfer on state

canSend, canReceive and a frozen check run in the contract. A package is non-transferable unless CLEAN; a decision can't move until reviewed. Compliance is a state machine, not a promise.

zk-verified compliance

Zero-knowledge proofs allow compliance verification without exposing sensitive data. Prove a package passed audit, a decision was human-reviewed, or custody chain is intact — all without revealing the underlying content.

Auto-freeze the risky

An AI-generated decision with no human review freezes on mint. A dependency with a Grype-detected CVE is force-transferred to quarantine. Phantom is the human gate that releases or rejects.

Anchor the trust

Three independent trust anchors: Ethereum for settlement finality, Bitcoin via OpenTimestamps for temporal proof, Ed25519 for cryptographic authorship. Verification never depends on a single party.

The toolchain

Open clients, contracts, services

A coherent set of Rust clients and Solidity contracts that take a decision or a dependency from source to a minted, audit-gated, indexed and supervised token on-chain. Open any project for its full architecture.