Provenance
Provenance is the chain of evidence from the frozen seed to the bytes at your address. Forked Felines records it before each Feline is reserved and publishes it once the Feline is confirmed.
The evidence on every Feline's card
| Line | What it proves |
|---|---|
| Frozen seed | The single input the whole collection was drawn from |
| Recipe digest | The exact recipe, traits and weights included, that drew this Feline |
| Artwork digest | SHA-256 of the exact SVG bytes that were inscribed |
| Artwork bytes | The exact byte length of the inscribed SVG |
| Release identity | The pinned studio release that drew the bytes |
| Inscription ID | Where those bytes live on Bitcoin |
Each value is recorded at reservation time, before inscription. The inscription is then constructed only if freshly generated bytes hash to the recorded digest, and portraits are only ever served after the same check. One record, enforced at every step.
How to verify a Feline yourself
- Open the Feline's page at
forkedfelines.art/collection/<edition>and note its artwork digest, byte length, and inscription ID. - Follow the inscription link on that page, which uses the designated Forked Felines Ord authority, or fetch the bytes from your own node using the inscription ID.
- Hash the bytes with SHA-256 and compare with the digest on the card. Check the byte length too.
If they match, the artwork at that inscription is exactly what the house committed to before it was inscribed. You have verified provenance with no trust in the house's servers.
# example: hash downloaded inscription bytes
shasum -a 256 feline.svgProve collection membership
Proving the artwork is right is one question. Proving that an edition belongs to the declared collection is another. Forked Felines publishes both the complete manifest and one compact Merkle proof per edition.
- Fetch
GET /api/public/v1/collection/manifestand record its manifest hash and Merkle root. - Fetch
GET /api/public/v1/felines/<edition>/proof. - Recompute the leaf from the returned edition record, then fold the proof path into a root. The result must equal the manifest root.
- When a Collection Seal is confirmed, fetch
GET /api/public/v1/collection/sealand verify that the seal names the same manifest hash and root. - Verify the artwork bytes against the digest on the edition page using the check above.
The @forked-felines/sdk verifier and the ff command-line client perform the same proof calculation offline. A proof that names another edition, inscription, manifest, or root is refused rather than repaired.
GET /api/v1/collection remains the simple confirmed collection listing. Unreleased editions never appear there, while the manifest and proof routes provide the portable membership evidence.
Why a bare list of IDs is not enough
Most collections circulate as an ad-hoc list of inscription IDs, which explorers and venues cannot check against anything. Forked Felines binds each ID to a digest, a recipe, and a seed recorded before reservation, so what the artwork is remains a checkable fact rather than a claim, whatever list the ID happens to travel in.
What is deliberately not in the evidence
No market data, no price history, no ranking. Provenance here is about what the object is, not what someone paid for it.