Skip to content

Known limitations

You will get from this page: everything the product cannot do today, stated plainly. If a limitation is not on this list and not on the status page, the product is expected to do it; report the gap.

Wallet signing and marketplace journeys have passed public-testnet campaigns. The production inspection on 17 September 2026 still found older serving artifacts without the current indexer receipt contracts and replay identity evidence. Those source tests do not establish production marketplace readiness. Check current status and the action’s own availability before signing or paying.

Exact total-price full-lot asks are a version 3 candidate. They cover ZRunes and each ZRC-20 ruleset separately, including 0, 6 and 18 decimal quantities. They do not open partial fills, bids or auctions. Execution also requires an explicit confirmation policy; publishing an order does not satisfy it.

Observed on 9 October 2026: the serving indexer had reached the newest block and reported itself up, but its replay had started late, so it was not qualified. Answers that need the complete history, such as strict ZkMap block availability, said they were unavailable (replay_incomplete) rather than showing an empty or free result. Qualification is not a condition for creating; each create page states its own availability. A replay from block 0 is running on separate, non-serving infrastructure; until a qualified release is serving, treat those answers as unavailable, not empty. Read is not the same as qualified.

The protocol activates at block 3,470,000. Below that height no ZRune can exist, by protocol rule. Reaching that height does not prove that the serving indexer has completed the required history or can provide settlement receipts. An unavailable ZRune route is not evidence that its market is empty. ZRunes.

Some ZRC-20 questions are deliberately unanswered

Section titled “Some ZRC-20 questions are deliberately unanswered”

Where the two historical rule sets disagree in ways that cannot be settled without inventing a fact (an unrecorded activation height, a shielded accounting choice), the product lists the difference as undecided rather than guessing. ZRC-20, and its two readings.

An inscription spent into a shielded pool is untrackable forever; a ZRune balance shielded with no transparent successor is burned. These are protocol facts, not product gaps, but they are listed here because people look for a recovery path that does not exist. Transparent and shielded.

Some artifacts point at content that is not on Zcash

Section titled “Some artifacts point at content that is not on Zcash”

12,881 indexed inscriptions, better than one in ten, are records naming content stored somewhere else rather than content written into the chain. The record is permanent; what it points at is not, and no transaction proves what that content currently is.

The product marks these references and distinguishes them from content written into the chain. Its NFT artwork service can retain bytes it successfully retrieves, but cannot reconstruct missing content from an IPFS identifier alone. If the source disappears before it is preserved, the chain still carries the record and nothing more. Collections and pointer records.

ZGODS is the only ZRC-721 collection on this chain. 8,503 mint inscriptions were made against it and 7,171 counted: 1,319 claimed an id an earlier mint had already taken, and 13 were inscribed before the collection was deployed.

Those 1,332 inscriptions cost a fee and hold no item. This is the chain as it happened rather than a product gap, and it is listed here because somebody holding one will go looking for the item. The collection page lists the rejections by reason so that search ends with an answer.

Watchlists, the visit mark, recent searches, and prepared orders live in your browser on this device, by design (there are no accounts and no server-side profiles). Clearing browser data or switching devices resets them. Portfolio and watchlists.

Listed prices, floors and volume describe this service’s orders and confirmed settlements. They are not chain-wide valuations or price guarantees. The two ZRC-20 rulesets retain separate quantities and prices.

Token price charts cover at most the last 30 days and leave out sales made through version 1 orders. Those sales are on chain but are not drawn. See A token’s page.

Open an issue in the documentation repository or follow the product’s support path. Security reports have their own channel.