Forked FelinesHouse Manual
Live product

Changelog

Changelog

Notable changes to the Forked Felines public documentation. Product changes are reflected here when they change what a collector should know.

Unreleased documentation corrections

  • Held batch items and payment evidence. Each Feline keeps its own traits, fulfillment state, and portrait confirmation gate. Payment confirmation is separate from delivery; last-check evidence carries its observation time. Eligible held cases can recover automatically after verification. A consumed original payment requires guarded recovery funded by an operator wallet, never another buyer payment.

  • Table for Two. The supper club card room at /game is documented: tonight's seating shared by everyone from the UTC date, open seating at 6, 8, or 12 tables with an optional timed service, the tab, the game portraits, accessibility, and what the browser keeps.

  • The capacity document now keeps answering from its last snapshot for up to 60 seconds while dependency evidence is being refreshed, and the house holds a healthy dependency observation for 45 seconds through a momentary stall before reporting it unavailable. cacheAgeMs tells you how old the answer is.

  • Market guidance now distinguishes listing publication, signed transactions, node preflight, uncertain broadcast and chain confirmation. Saved-operation recovery, separate wallet roles and address proofs are described without claiming a production rollout.

  • Remediation guidance explains atomic election retries, credit refresh from the ledger and the distinction between a refund obligation, a sent refund and confirmation.

  • Funded offers, the collector batch flow and airdrop inscription execution are identified as unavailable where their complete contracts are not implemented. Future snapshot and claim gates remain in force.

  • Public API caching guidance now treats growing manifests, ownership and reorg-sensitive history as changing representations, and separates unknown data from empty results.

These notes accompany application validation. They are not a release announcement or evidence of deployed wallet or transaction success.

2026-09-07

Changed

  • Zero service fee on all-credit mints. An order made entirely of free-mint credits now carries a 0-sat service fee, initial and per accepted fee bump (fee policy FREE_MINT_WAIVER_V1). Paid and mixed orders keep the 1,500-sat initial service fee and 1,500 sats per accepted RBF bump. Signed quotes issued before the change keep the fee terms of their own pricing version. The product contract now publishes pricing.freeMintServiceFeeSats: "0"; every price page, the product facts, the terminology and the README say where the fee applies.
  • How remediation refunds are paid. A refund is paid manually by an authenticated administrator from the administrator's own connected wallet, one refund at a time, to the immutable original payment address; there is no treasury wallet. The signed transaction is kept as a durable record and relayed again automatically until a node accepts it.
  • Transaction links. A mainnet transaction id on the kitchen ticket links to the public Ordinals explorer at https://ordinals.com/tx/<txid>, never to a raw IP address or an internal host.
  • Smaller public status documents. /api/v1/mint/capacity and /api/health/ready publish a fixed public schema: network, mint state, coarse reason codes such as BACKUP_RESTORE_VERIFICATION_STALE, freshness, build identity, block height, and coarse worker and financial readiness. Detailed worker and provider diagnostics are shown only to administrators.

The 2026-08-28 entry below records the initial service fee of 1,500 sats as it applied to every mint at first publication; that was accurate then and is superseded by this entry.

2026-09-02

Added

  • The Wallet Bridge, current owner and chain history, collector ledger, Transfer Desk, Trading House, Airdrop Desk, Collection Seal, holder rights, and portable proof guides.
  • The versioned /api/public/v1 data platform, including collection manifests, per-edition inclusion proofs, confirmed history, market reads, airdrop status, event replay, the typed SDK, and the ff command-line client.

Changed

  • Provenance now explains the collection manifest, per-edition Merkle proof, and seal verification path that replaced the earlier list-only membership check.
  • Market documentation now separates verified house reads from third-party claims and never infers a floor from stale or incomplete data.

2026-09-01

Removed from the 2026-09-01 live manual

Three endpoints and one whole page were written against a design rather than the product that was live that day. None had been published to the live manual, so they were removed until the product shipped them. The 2026-09-02 release above supersedes those availability statements.

  • A market desk page, describing a read-only order book, its actionability checks and its floor logic. On 2026-09-01 the application had no trading surface, served no market endpoint, and returned no answer at GET /api/v1/market.
  • GET /api/v1/collection/manifest and GET /api/v1/collection/proof/{edition}, documented in Public API and used as a verification workflow in Provenance. Both returned 404 on 2026-09-01, so the manual reverted to the collection listing until the replacement /api/public/v1 manifest and proof contracts shipped.
  • A verifier command in Provenance referring to a tool in the application repository. There is no such tool.

A reader who follows a documented endpoint into a 404 has lost more than the time: they have lost the reason to believe the next page. Every endpoint on the Public API page now answered when it was checked, and the page says so at the top.

Added

  • The plates: eight confirmed Felines hung at full size with a museum catalogue entry each, showing plate, edition, medium, dimensions, byte length, digest, setting odds and inscription. The artwork is the real thing, saved from the public artwork endpoint into this repository, so the digest printed under each frame is the digest of the file the page just served you.
  • Trait catalogue: what the ten traits decide, and every value that has appeared on a confirmed Feline, with a filter. It states its own two limits on the page: the list is a floor rather than the whole recipe, because unreleased values are deliberately not published, and the tallies are mint progress rather than odds.
  • Verify a Feline: a task guide for checking artwork against its committed digest, with the command line steps, the failure states, and a checker that computes SHA-256 inside your own browser. Nothing is uploaded, because this site has no server to upload it to.
  • Traits and odds now explains what a one-in figure means against a maximum supply of 3,333, and records that the tier words overlap in the confirmed Felines published so far, so a tier word cannot be read as a ranking of the figure.
  • Order states now publishes the complete transition table. Two rows explain most of the surprises: an expired reservation can still see a late payment and refund it, and a recoverable failure leads back into the flow rather than out of it.
  • Whole on Bitcoin now describes the actual inscription envelope, including that the SVG is carried Brotli compressed and that the published digest is of the decompressed drawing. A holder hashing raw witness bytes would otherwise get a digest that correctly fails to match.
  • docs.manifest.json, llms.txt, a documentation manifest link and machine-readable copies of the pinned facts, so the central platform and other readers can ingest this repository without scraping it.

Changed

  • The manual is now a gallery. New homepage, new typography, artwork plates with proper mattes, catalogue entries set as catalogue entries, and a daylight and after-hours theme that both meet WCAG 2.2 AA. Every page carries a provenance block naming its owning repository, source path, chain, network, lifecycle, product contract and verification date.
  • Supported wallets stops implying that every listed wallet can pay. The site asks the connected provider what it exposes and labels it from the answer, so the same wallet can be ready for checkout on one machine and address only on another. The page also states which recipient script types are accepted: Taproot and native SegWit yes, legacy and nested SegWit no.
  • Prices and fees names the 546 sats of inscription postage as postage rather than fee, since it arrives at your address with the Feline, and records that the commit transaction is funded by the house. Order quantity is 1 to 20, and up to 3 unpaid orders may be held at once.
  • Status contract lists all five values of mintState. FINISHED was missing.
  • My Booth separates reading a booth from acting on one. Anyone can look up any address; cancelling is authorized by a token held only by the browser that created the order.

Product facts

  • Supply, pricing, holder snapshot, and settlement facts are unchanged.

2026-08-29

Added

  • Stay safe now says which parts of the house are jokes and which are never jokes. The guest book is written by the house, and every card in the product now says so on the card itself, including where a single card is lifted out of the book and set beside an FAQ answer, the portrait wall, or a booth. The portraits on those cards are real published KNOT HEADS inscriptions, which is exactly what made an unlabelled card read as a customer testimonial.

Changed

  • The Knot Heads press claim on the product is now dated. A marketplace position is a reading taken on a day, so the day it was reported travels with it.

  • The roadmap no longer says the collection is upcoming before it has read the capacity document. The served page previously told search engines and every first paint that a collection currently minting had not started.

  • The expired-order row in Order status no longer tells a visitor to "just order again". The house copy rules ban that word where it would make a money-adjacent act sound trivial, and a reservation that expired is the state where a reader is most likely to be worried about a payment. The product says the same thing, in the same words.

  • The collection wall: the wall now arrives hung. Its frames are in the page the server sends, so a search engine, a link preview, and a phone on a slow connection all see the same portraits a browser shows. Previously the wall was fetched only in the browser, and the served page linked to none of the confirmed Felines. A wall that is already hung now stays hung when a refresh fails.

  • Every page of the product now carries a proper preview card when its link is shared. Previously only the support page did, so a link pasted into a chat arrived as a bare row of text.

  • The holder entitlement is called a free-mint credit everywhere. A few product surfaces still used a name from a retired policy; the documentation always used the current one, and now the product agrees with it.

Publication gate

  • An unreachable product endpoint no longer blocks publication. The live-contract check now exits 75 for "could not reach the product" and 1 for "the facts disagree", and only the second stops a publish. A 404 counts as the second: if the contract moves, the endpoint answers, and that is the event this check exists to catch. It stays counted even if the path drops afterwards, so a real 404 cannot be masked by later noise. The two shared an exit code, so a runner that could not open a socket blocked the publication of correct documentation while the site kept serving an older build, which is the worse of the two outcomes. The facts stay guarded either way: they are pinned offline and that check runs first.

  • No word may be published twice in a row. Markdown wraps prose across source lines, so a word typed twice reads as two clean lines in a diff and as a defect on the page.

  • One verification date. The README, the reference page, and facts/facts.json must agree on when the facts were last checked against the live product contract.

Product facts

  • Unchanged. Re-verified against the live GET /api/v1/product contract on 2026-08-29.

2026-08-28

Added

  • First public release of the House Manual: start-here guides, collector guides, collection and provenance explanations, safety guidance, help, and the public API reference.
  • facts/facts.json: the machine-checked product facts this documentation is validated against, themselves verified against the live GET /api/v1/product contract.
  • The documentation site, built from this repository's Markdown and published through GitHub Pages.

Product facts at first publication

  • Maximum supply 3,333; public collection price 8,888 sats; community (credited) price 0 sats; initial service fee 1,500 sats; holder snapshot at Bitcoin block 963,238; pricing contract forked-felines.community-remediation/v4.
  • Every confirmed Feline has its own page at forkedfelines.art/collection/<edition> with traits, frozen odds, a hand-written house note, and full provenance evidence.
  • Portraits are served with byte-level verification and a second Universe-operated artwork source that survives index rebuilds.

Where this page comes from

Owning repository
bitcoinuniverseio/forked-felines-docs
Source path
CHANGELOG.md
Page kind
Changelog
Chain and network
bitcoin mainnet
Lifecycle
stable
Product contract
forked-felines.public-product/v5, pricing forked-felines.community-remediation/v4
Facts last verified
against the live product contract
Built from
c6fdbca5703e

Financial facts are never jokes here. Everything else is fair game. A collectible, not an investment.