# CipherMarket CipherMarket is GlyphVoid's dedicated secondary marketplace. It exists as a separate smart contract deployed alongside the collection. It is purpose-built for CIPHER tokens — it does not support any other collection. **Why a dedicated marketplace?** General marketplaces like OpenSea and Blur are designed for discovery across millions of collections. They offer flexibility that comes at a cost — royalties can be bypassed on some platforms depending on their policies at any given time. CipherMarket enforces a permanent 5% creator royalty on every sale at the contract level. This cannot be bypassed. It is not a recommendation or a request — it is enforced by the code that executes the sale. Beyond royalties, CipherMarket is integrated directly into the GlyphVoid experience. The vault balance is visible alongside listings. The puzzle map shows which tokens are listed and which are not. Suspected puzzle tokens can be tracked in the community context that a general marketplace cannot provide. **How it works** CipherMarket uses an approval model. When you list a token, you approve the marketplace contract to transfer it on your behalf when a buyer purchases. Your token stays in your wallet until the sale executes. The marketplace never takes custody. A purchase is atomic — the token transfer, the royalty payment, the marketplace fee, and the proceeds to the seller all happen in a single transaction or the entire thing reverts. There is no partial execution. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://glyphvoiddocs.gitbook.io/undefined/the-marketplace/ciphermarket.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.