Pending Listings
After transfer-lock, sellers can publish a non-buyable pending listing at the permanent /listing/name URL. The page becomes active after the final proof is uploaded.
Shakedex Docs
Shakedex.org is the canonical home for Shakedex-specific documentation: pending listings, permanent listing pages, sale history, channels, and Bob Wallet integration.
After transfer-lock, sellers can publish a non-buyable pending listing at the permanent /listing/name URL. The page becomes active after the final proof is uploaded.
Use /listing/name as the public permalink for pending, active, sold, and later relisted names. Older /pending/name links should redirect there.
Each listing page should preserve historical sales for that name, even if it is relisted later. Buyers get context and sellers keep a public market record.
A channel combines Shakedex proof validation, a synced/indexed HSD node, marketplace APIs, pending records, active listings, and sold history.
Bob can browse Shakedex channels, show readiness state, buy active listings in SPV when channel coin data is available, and guide sellers through safer flows.
Buy Now is the simple MVP path. Reverse auctions remain part of the original Shakedex model for sellers who want gradual price discovery.
Generating a proof creates a local signed sale file. It does not send an on-chain transaction and it does not publish the listing until the proof is submitted to a channel.
Seller listing data is local. Back up Marketplace JSON before switching computers, uninstalling Bob, or reinstalling your operating system.
A seller can change the Buy Now price before generating a proof. If an older proof was already shared or uploaded, that old proof may remain fillable until the listing lock is cancelled.
Pending: publish a transfer-lock announcement with POST /api/v2/pending-listings.
Canonical page: link users to /listing/name, even before the listing is buyable.
Active: upload the Shakedex proof; the marketplace promotes the pending row to active.
History: sold or archived rows stay attached to the listing page for future reference.
Transfer lock: the seller starts a real on-chain transfer into a Shakedex lock that the seller controls. This is not buyable yet.
Finalize lock: after the Handshake transfer lockup, the seller sends the on-chain finalize transaction for the locked name.
Generate proof: Bob creates a local signed proof at the selected price. No HNS moves, no miner fee is paid, and the market does not see it yet.
Download: save a backup copy of that generated proof. This is local only.
Submit: upload the generated proof to the selected Shakedex channel, such as LearnHNS Market. This is what makes the listing visible to buyers.
Cancel: start returning the locked name to the seller wallet. This is an on-chain action and is the safe way to invalidate previously shared proofs.
Price warning: changing the price before submitting is normal. But if an older proof was already shared or uploaded at a lower price, a buyer may still be able to fill that older proof until the listing is cancelled.
Required Seller Backup
Shakedex seller listings depend on local Bob Wallet Marketplace data. When Bob starts the seller flow, it creates listing records, encrypted Shakedex keys, and proof data on that computer. A public pending page on a market proves the channel saw the announcement, but it is not a full backup of the seller data.
Before uninstalling Bob, wiping a computer, switching from Windows to Linux, or moving to another device, open Bob and export a Marketplace backup JSON from Settings / Marketplace. Keep that file with your wallet backups.
If the original Bob data and Marketplace backup are both lost, the wallet seed may recover normal wallet funds and names, but it may not recover the special Shakedex listing key needed to finalize, cancel, regenerate, or submit a locked seller listing.