Products

A product is a step above a recipe. Where a recipe selects capabilities, a product assembles a state machine or composite profile, a domain contract, a read API, a client, and often a CLI into one installable thing with an opinion about a use case. Every “Try it” below runs from an extracted yano-x-jvm-<version>.zip.

Product	What it does	For	Try it	Maturity
Evidence	Publishes a document through threshold approval, stores it in object storage and IPFS, notifies Kafka, and proves each step.	Teams releasing records several organizations approve	`examples/evidence/demo.sh` (Docker)	`preview`
Cardano History	Proves historical Cardano parameters, epoch stake, DRep distribution, and proposals instead of trusting an indexer.	Governance, reward, and validator tooling	Showcase `cardano-history-chain`	`preview`
Attest	Records a document’s digest and hands out a certificate that anyone can verify offline.	Proof of existence; auditors	Showcase `documents-chain` with `tools/yano-attest`	`preview`
Evidence Desk	Propose, approve with browser-held actor keys, release once, and read every record back with its proof.	Issuers, auditors, and reviewers	Showcase `document-review-chain` with `product-ui/evidence`	`preview`
Trust Registry	Answers credential status and issuer authorization with proofs, and serves status lists tied to the ledger.	Credential issuers and verifiers	`examples/trust-registry/registry.sh`	`preview`
Verifiable Explorer	Indexes stock ledgers after verifying each block; rows and states export as bundles that verify offline.	Operators, support, and auditors	`examples/explorer/explorer.sh`	`preview`
DPP Starter	A prototype product passport registry: governed records, independent certification, and passports that verify offline.	Teams exploring Digital Product Passports	`examples/dpp/dpp.sh`	`reference` (prototype)
Attestation Feed	Sources sign readings, every verifier recomputes each round, and two organizations approve the record.	Consortia combining readings from known sources	`examples/attestation-feed/feed.sh`	`experimental` (starter)
eUTxO ledger	A Cardano-shaped UTxO ledger with an optional federated bridge, for test funds only.	Researchers and protocol teams	`./yano.sh appchain eutxo demo`	`experimental`

Choosing one

Which product fits?Decision aid

What you're seeing: a few questions about what you need to prove or share. Each answer names a product and how to try it.

What do you need to prove or share?

A document existed, unchanged
Who has to approve the document?
- Nobody: I need a timestamped digest and a portable certificate
  Attest
  Records a document's SHA-256 on a doc-trail ledger and hands out a certificate that verifies offline against member keys or a Cardano anchor.
  Maturity
  preview
  Try it
  the showcase's documents-chain with tools/yano-attest
  Attest →
- Several organizations, before it is released
  Must the released document also be stored and announced to other systems?
  For example, kept in object storage and IPFS and announced on Kafka.
  - Yes, with connectors to external systems
    Evidence
    Publishes an immutable document through a threshold-approved workflow, preserves it in object storage and IPFS, notifies Kafka, and proves the chain of events.
    Maturity
    preview
    Try it
    examples/evidence/demo.sh (needs Docker)
    Evidence →
  - No, approvers work from a browser and the ledger is enough
    Evidence Desk
    An issuer proposes, auditors from distinct organizations approve with keys held in their browsers, and the approved release is applied once.
    Maturity
    preview
    Try it
    the showcase's document-review-chain with product-ui/evidence
    Evidence Desk →
A credential, issuer, or identifier is still valid
Trust Registry
Answers credential status and issuer authorization with proofs bound to a certified block, and serves Bitstring Status Lists that hash to the ledger's value.
Maturity
preview
Try it
examples/trust-registry/registry.sh up
Trust Registry →
A product's records across its life
DPP Starter
A prototype product passport registry: governed product, version, claim, and event records, certification by two independent auditors, and passports that verify offline.
Maturity
reference (prototype)
Try it
examples/dpp/dpp.sh up
DPP Starter →
One agreed value from several data sources
Attestation Feed
Sources sign their own readings, every verifier recomputes each round's aggregate, and publishers from two organizations approve the record. Not a public price oracle.
Maturity
experimental (starter)
Try it
examples/attestation-feed/feed.sh up
Attestation Feed →
What Cardano's parameters, stake, or proposals were at a past epoch
Cardano History
Records Cardano epoch facts on an app ledger and answers with compact proofs instead of trusted indexer responses.
Maturity
preview
Try it
the showcase's cardano-history-chain with tools/yano-cardano-history
Cardano History →
A readable, verifiable view of an existing ledger
Verifiable Explorer
Indexes stock ledgers only after verifying each block, and exports rows and states as bundles that verify offline. The index adds convenience, never trust.
Maturity
preview
Try it
examples/explorer/explorer.sh up against the showcase
Verifiable Explorer →
Cardano-shaped transactions on an app ledger
eUTxO ledger
A deterministic Cardano-shaped UTxO ledger, with an optional federated bridge. For disposable test funds only.
Maturity
experimental
Try it
./yano.sh appchain eutxo demo up --scenario ledger …
eUTxO ledger →

Products are not mutually exclusive with recipes; a product is the recipe for its domain. Start from choosing a recipe when no product matches your problem, and reach for the plugin framework when no recipe does either. Check first whether a composite of existing components gets you there. The use cases page maps common problems to the building blocks.

What products have in common

Products reuse the platform’s state machines, authenticated state, and proof verification, but they are packaged differently:

Evidence, Cardano History, and the eUTxO ledger add runtime plugin behavior.
Attest is a client, CLI, and UI over the stock doc-trail state machine.
Trust Registry, DPP Starter, and Attestation Feed configure the stock governed authenticated map and add application tooling outside consensus.
Evidence Desk is a browser UI over the role workflow.
Verifiable Explorer maintains a derived read index and its own service.

Runtime contributions use the plugin catalog. Plain clients, CLIs, static UIs, and configuration-only products do not need a new runtime plugin. Product services can expose their own APIs; /api/v1/plugins/<bundle-id>/ is the host route for plugin-contributed APIs, not the route for every product.

What products deliberately do not claim

A proof establishes a specific recorded claim under a stated trust policy. It does not establish the truth of the underlying business event. The platform proves what identified participants finalized and what they authorized; it does not decide what counts as a valid product event, an acceptable inspection, or a correct settlement. That stays with the domain.

Most product verifiers report one of Yano’s five trust levels, from INTERNAL_CONSISTENCY_ONLY (consistent with itself) through CALLER_PINNED_ROOT (members you pinned) to INDEPENDENTLY_VERIFIED_L1_ANCHOR (an anchor you read from Cardano yourself). Treat only the pinned and anchored levels as verified. Keys and trust explains what each one rests on.