CIPHR is being rebuilt with Chutes confidential inference on Bittensor SN64 and Phala dstack TDX key custody. The current holder authorizes a CVM request with a wallet signature, and the contract requires an enrolled enclave seal before minting. A public visor reveal is permanent. The collection and confidential service are not deployed or verified yet.
Status
The three-step picture
You buy the token from the pool.
Your wallet approves a specific request to the enrolled CVM, which seals the visor before your wallet submits the mint.
You hold the piece. Its visor reads as noise to anyone else until you unlock it, or choose to reveal it for good.
Read next
Each page stands on its own, but they read best in order.
How it works: the path of one buy, step by step, with a diagram of the buyer, the pool, the server, and the collection, and where sealing and submitting the mint fits in.
The piece: the anatomy of a piece, its helmet shape, edge colour and visor noise, and the lock states a piece moves through.
Rarity: the five weight tables, how 1 in N is worked out, and a calculator you can play with.
Contract: for developers, the functions, events, errors and the EIP-712 signing shape, plus the seal, reseal and reveal functions.
Keeper: the signing route your wallet calls before you seal and submit, and why there is no funded keeper standing between your buy and your piece.
FAQ: short, plain answers to the questions a buyer asks first.
Brand: the name, the mark, the colours and the type.
What CIPHR is not, yet
Limit
No contract is deployed. No token, pool or collection address is published. Every number on these pages that looks like a real result is computed live from the same arithmetic the eventual contract uses, on example fields, never on a real buy. The private visor is drawn in the browser; the public artwork a revealed piece shows on chain is planned to match it and is not built yet.