The missing layer for modern systems: portable, verifiable proof of digital actions

The missing proof layer for digital actions.

DAR is an open, minimal receipt for a digital action — a portable record that can be independently verified later without special access, shared systems, or trust assumptions.

SV-DAR strengthens this foundation for high-stakes environments where incentives conflict: audits, disputes, and cross-organization automation.

DAR is open. You can issue/store receipts anywhere. We monetize optional tools (verification, chain operations, intelligence) and SV-DAR capabilities.

Digital action API, approval, transaction, agent decision Receipt emitted payload hashed (+ optional envelope) Stored append-only any storage chosen by parties Independent verification tools + SV-DAR Stronger guarantees

Value

Most systems can tell you what happened internally. DAR makes that evidence portable and verifiable — when trust breaks down, vendors change, or an audit/dispute happens months later.

Disputes

Proof beats explanations

Reduce “he said / she said” by producing a cryptographic receipt of the action — without exposing internal logs or special access.

Audit & risk

Evidence that survives time

Verify what happened even after teams, vendors, or systems change. Receipts stay valid as long as the artifacts are available.

AI & automation

Accountability for agents

When autonomous systems make decisions, DAR provides a neutral record of the action — not a judgment of correctness.

Plain English

Receipts for software

A DAR is like a bank receipt: it proves a thing occurred. You can hand it to someone else and they can verify it without trusting you.

What it is not

Not a compliance engine

DAR doesn’t enforce policy or decide who was “right.” It creates a shared evidence layer so parties can verify what happened.

Workflow

DAR is simple: create a minimal payload, canonicalize it, hash it, optionally wrap it in an envelope, store it append-only, and verify later. SV-DAR adds stronger guarantees when incentives conflict.

Steps

From action → proof → verification

Tap a step to see what it means.
A digital action is committed. A receipt is emitted at (or immediately after) the commit point.
Demo

See a receipt and verify it

The payload is the hashed object. The envelope is transport metadata. Verification recomputes the receipt hash from the payload only.

Status: ready
{}
What “verify” means: canonicalize payload → compute hash → compare. It does not judge business correctness — only that the receipt is cryptographically consistent.

SV-DAR

DAR works when parties are aligned. SV-DAR is for when they aren’t: disputes, regulatory scrutiny, and cross-vendor automation where incentives conflict.

Commercial focus
Stronger guarantees

Self-verifying trust

Designed for environments where basic signatures are not enough for independent confidence at scale.

Cross-organization

Vendor-to-vendor proof

Built for workflows spanning parties who don’t share systems, policies, or trust assumptions.

Dispute-ready

Defensible evidence

Premium guarantees and tool support for cases where evidence must remain defensible under scrutiny.

Where SV-DAR typically matters

  • Third-party and vendor workflows (no special access)
  • Audit-heavy environments and regulated operations
  • Disputes, claims, chargebacks, incident reviews
  • Autonomous agents operating with material impact

Tools

Optional services applied to DAR/SV-DAR: verification at scale, chain operations, intelligence, and audit-ready reporting. Receipts are free to exist and verify independently. You pay only when systems are asked to do work.

View tools

Verification

Verify receipts

Signature validity (if present), schema compliance, and hash integrity — single or batch verification.

Open in Tools →

Chain operations

Traverse timelines

Detect gaps, ordering conflicts, and broken references across receipt chains and graphs.

Open in Tools →

Intelligence

Reason & report

Summaries, anomaly detection, policy checks, and audit-ready exports when accountability is required.

Open in Tools →

Usage-based

Fairness model

Receipts are free to exist, share, and verify. Fees apply only when systems perform computation — traversal, aggregation, anchoring, analysis, or reporting — never to access or verify truth.

Tools

Explore the toolset

The verifier is the first tool. Additional optional tooling will support chain operations, exports, and audit-ready evidence bundles.

Go to tools

Code

Start in minutes with open specs and reference code. Keep production systems vendor-neutral and independently verifiable.

Quickstart

Issue + verify (minimal)

// Issue a receipt (self-hosted)
const receipt = issueDAR(payload, privateKey)

// Verify a receipt (anywhere)
const result = verifyDAR(receipt)
if (!result.ok) throw new Error(result.reason)

Keep it simple: payload → canonicalize → hash → store → verify.

Repo contents

Minimum viable open source

  • spec/ invariants + versioning
  • dar-core.md normative spec
  • dar-payload-schema.json canonical payload (hashed)
  • dar-schema.json envelope (payload + transport)

Pricing

Keep the foundation open. Monetize the work: verification at scale, chain operations, intelligence, and SV-DAR premium guarantees.

Free
$0
DAR spec + open repo
  • Open schema & examples
  • Self-hosted usage
Pro
$99/mo
Tools (starter)
  • Verification API + batch
  • Basic chain operations
  • Usage-based overages
Enterprise
Custom
SV-DAR + SLAs
  • SV-DAR premium guarantees
  • Advanced tooling + reporting
  • Support, onboarding, and SLAs

Commercial focus

SV-DAR and tools are the monetized layer. DAR remains open and implementation-agnostic.