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
Build and run open Handshake markets
Shakedex.org is the canonical home for Shakedex-specific documentation: pending listings, permanent listing pages, sale history, channels, and Bob Wallet integration.
Lost a listing after restoring a wallet? A seed phrase does not restore Shakedex seller data.
Permanent Listing Pages
Use /listing/name as the public permalink for pending, active, sold, and later relisted names. Older /pending/name links should redirect there.
Sale History
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.
Run a Shakedex Channel
A channel combines Shakedex proof validation, a synced/indexed HSD node, marketplace APIs, pending records, active listings, and sold history.
Bob Wallet Integration
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.
Reverse Auctions and Buy Now
Buy Now is the simple MVP path. Reverse auctions remain part of the original Shakedex model for sellers who want gradual price discovery.
Generate vs Submit
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 Backups
A seed phrase restores on-chain HNS and names. It leaves Shakedex listings behind. Export Backup Marketplace Data from Bob before you reinstall, switch computers, or delete the Bob data folder.
Price Changes
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.
Current Marketplace Contract
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.
Seller Flow Terms
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
A seed phrase does not restore Shakedex listings
There is no way to rebuild an open Shakedex listing from a wallet seed or master key alone.
Importing a seed into Bob restores on-chain HNS, names, and bids after sync finishes. Shakedex seller data is a separate local record. Bob creates a lock key for the listing, encrypts it with the wallet password, and stores it in the app database under that wallet's name. The Marketplace backup JSON is the copy of that record.
A public page on a Shakedex channel shows buyers a proof you already submitted. It does not contain the seller lock key. With the public page alone you cannot finalize, cancel, regenerate, or submit that listing.
What comes back from the seed
- Spendable HNS after the wallet sync finishes.
- Names and bids that are already on chain.
- A sale that already finalized on chain. It returns as normal wallet history.
What stays on this computer
- Open, pending, and unsold Shakedex listings.
- The encrypted lock key those listings need.
- Generated proofs and fill records that were never exported.
If Bob still has the old profile
Importing the seed under a new wallet name leaves the old listings in place. They stay filed under the previous wallet name. If that wallet is still in Bob's wallet list, open it and export the backup below. Then use Restore listing on the wallet you want to keep using.
If you never exported JSON, the same records can still be in Bob's app database. Do not delete this folder to fix a sync or startup problem.
- macOS: ~/Library/Application Support/Bob LearnHNS/db
- Windows: %APPDATA%\Bob LearnHNS\db
- Linux: ~/.config/Bob LearnHNS/db
If that db folder and the Marketplace JSON are both gone, the open listing is gone with them. Keep the computer, the old user account, and any disk copy until you have exported the JSON.
Back up while Bob opens
- Open the wallet that created the listings.
- Go to Settings → Shakedex Marketplace.
- Choose Backup Marketplace Data.
- Store that JSON with your wallet backups, on a second disk or drive.
Also keep any proof file you downloaded. The Marketplace JSON is the full seller record, including the encrypted lock key. Do this before uninstalling Bob, reinstalling the operating system, or moving to another computer.
Restore on a new install
- Restore the wallet from the seed and let it sync.
- Go to Settings → Shakedex Marketplace.
- Choose Restore listing and select the Marketplace JSON.
The seed restore and the listing restore are two separate steps. Finishing the first one leaves Shakedex empty until the JSON is restored.