CSV Adapter Core

Chain-agnostic core traits and types for CSV (Client-Side Validation) adapters.

Overview

This crate provides the foundational types and traits for the CSV protocol, a client-side validation system built on the Universal Seal Primitive (USP). Rights are anchored to single-use seals on any chain. To transfer a Right, the seal is consumed on-chain and the new owner verifies the consumption proof locally — no bridges, no minting, no cross-chain messaging.

Key Types

• Right — A verifiable, single-use digital right that can be transferred cross-chain
• Hash — A 32-byte cryptographic hash (SHA-256 based)
• Commitment — A binding between a right's state and its anchor on a blockchain
• SealRef / AnchorRef — References to consumed seals and published anchors
• InclusionProof / FinalityProof / ProofBundle — Cryptographic proofs
• AnchorLayer — The core trait each blockchain adapter implements
• SignatureScheme — Supported signing algorithms (secp256k1, Ed25519)

Installation

cargo add csv-adapter-core

Or in your Cargo.toml:

[dependencies]
csv-adapter-core = "0.1"

Features

Quick Start

Creating a Right

use csv_adapter_core::{Right, Hash, OwnershipProof, SignatureScheme};

// Create a commitment hash
let commitment = Hash::new([0xAB; 32]);

// Create an ownership proof
let owner = OwnershipProof {
    proof: vec![/* signature bytes */],
    owner: vec![/* owner address bytes */],
    scheme: Some(SignatureScheme::Secp256k1),
};

// Create a Right
let right = Right::new(commitment, owner, b"unique-salt");

// Transfer to a new owner
let new_owner = OwnershipProof {
    proof: vec![/* new signature bytes */],
    owner: vec![/* new owner address bytes */],
    scheme: Some(SignatureScheme::Secp256k1),
};
let transferred = right.transfer(new_owner, b"transfer-salt");

Working with Commitments

use csv_adapter_core::{Commitment, SealRef};

// Create a commitment with all fields
let commitment = Commitment::simple(
    contract_id,       // What Right this is for
    previous_commitment, // Hash of previous commitment (or zero for genesis)
    payload_hash,       // What changed
    &seal_ref,          // What seal was consumed
    domain_separator,   // Chain-specific isolation
);

Verifying Signatures

use csv_adapter_core::{verify_signatures, SignatureScheme};

let signatures = vec![/* signature data */];
let public_keys = vec![/* public key data */];

let is_valid = verify_signatures(&signatures, &public_keys, SignatureScheme::Secp256k1);

Architecture

The core crate defines the Universal Seal Primitive — a chain-agnostic abstraction for single-use enforcement:

┌──────────────────────────────────────────────────────────────┐
│                    csv-adapter-core                           │
│                                                               │
│   Right ────────────── Portable digital right                 │
│   Commitment ──────── Hash chain of state transitions         │
│   SealRef ─────────── Reference to consumed seal              │
│   AnchorLayer ─────── Trait: per-chain implementation         │
│   ProofBundle ─────── Inclusion + finality proofs             │
│   SealRegistry ────── Cross-chain double-spend prevention     │
└──────────────┬──────────┬──────────┬──────────────────────────┘
               │          │          │
      ┌────────┴┐  ┌─────┴┐  ┌─────┴────┐
      │Bitcoin  │  │Ethereum│  │Sui/Aptos │
      │Adapter  │  │Adapter │  │Adapters  │
      └─────────┘  └────────┘  └──────────┘

Each chain adapter implements AnchorLayer using its native single-use mechanism:

Examples

See the examples/ directory for usage patterns:

• basic_right — Creating, transferring, and verifying Rights
• commitment_chain — Building and validating commitment chains

Run examples with:

cargo run --example basic_right
cargo run --example commitment_chain

License

This project is dual-licensed under either:

• Apache License, Version 2.0 (LICENSE-APACHE or https://www.apache.org/licenses/LICENSE-2.0)
• MIT license (LICENSE-MIT or https://opensource.org/licenses/MIT)

at your option.

Contributing

We welcome contributions! Please see our GitHub repository for more information.