ACC MVP / music only

Operate catalog certification

200,000Catalog tracks
0Live ledger events
0Live anchor batches

Ledger

Bulk catalog certification simulator

Model how ACC processes an evergreen catalog: metadata and audio enter once, certificates are issued in batches, ledger events are created, and batch roots are anchored to the blockchain layer.

BETA note: ACC Core creates real ledger events, calculates a deterministic batch root and stores an OpenTimestamps-ready proof object in R2. Bitcoin confirmation is shown only after a real attestation exists.

Estimated completion4.0 min
Certificates200,000
Batches8
Blockchain anchors200
Throughput is operator-set.Existing catalog metadata reduces intake time.Blockchain anchors batch roots, not every audio file individually.

ACC Core

Live anchor engine

Unbatched live certificates0
Ready for first batch
Live ledger events0
Anchor batches0
Blockchain layerNot batched yet
{
  "jobType": "acc.core.anchor",
  "liveCertificatesIssued": 0,
  "liveCertificatesBatched": 0,
  "liveLedgerEvents": 0,
  "anchorBatches": 0,
  "latestBatch": "none",
  "latestRoot": "pending",
  "latestBatchStatus": "Ready for first batch",
  "otsStatus": "Not batched yet",
  "automation": "private ops cycle runs outside the public UI"
}

Anchor batches

Blockchain proof queue

No live anchor batch yet. Issue one or more real ACC certificates, then run anchor batch.

Ledger events

Recent hash-chain events

No live ledger events yet. Real events appear after ACC Core certificate issuance.

Information flow

Where data enters, where proof exits

INCatalog metadata

ISRC, title, artist, rights owner and source system.

INAudio assets

Files or existing asset hashes enter the ACC intake queue.

ACCDeclaration layer

HUMAN, SEMI-MIX or AI GEN declaration is bound to each work.

ACCCertificate issue

ACC ID, audio hash, declaration hash and status are created.

LEDGERBatch root

Certificate events are grouped into a ledger batch root.

BLOCKCHAINAnchor transaction

The batch root is anchored externally for timestamped integrity.

OUTAPI objects

Partners read certificates, ISRC lookup and verification state.

OUTPublic proof

Each work receives a public verification URL and market signal.

Input points
  • Catalog CSV / DDEX feed
  • Audio files or asset hashes
  • Creator or label declarations
Blockchain guarantees
  • Tamper-evident batch root
  • Timestamped anchor
  • Hash continuity across ledger events
Output points
  • Public certificate URLs
  • Partner API records
  • Blockchain anchor receipts