Djinn is not mainly a sportsbook or prediction market. It is trying to build an encrypted-information marketplace where analysts sell signals without revealing them to the platform operator or to non-buyers.
The core stack is explicitly layered: Base contracts for escrow / collateral / audit / accounts, Bittensor validators for key shares and outcome coordination, Bittensor miners for line checks and TLSNotary proofs, and a client that decrypts signals locally after purchase.
The distinctive mechanism is not just encrypted picks; it is encrypted picks plus executability verification plus collateral-backed SLA-style audits. Djinn tries to make sold information both private and accountable.
The README makes the web-attestation sidecar explicit. Djinn is also packaging a public TLSNotary-backed proof service, which strengthens its value as a comparison point between web-proof rails and application-specific information markets.
The whitepaper is useful because it names the deeper split clearly: information versus execution. That framing is more reusable than the sports niche itself.
The deviation log is one of the most important primary sources. It shows the implementation is a moving target rather than a frozen whitepaper replica, including changes to MPC design, staged wallet-recovery behavior, and removal of some earlier ZK track-record machinery.
Specific source signals worth retaining
README.md: best concise map of the current stack — Base contracts, Bittensor validators/miners, The Graph, TLSNotary-backed attestation, and operational posture.
docs/whitepaper.md: strongest articulation of the intended mechanism — encrypted commitments, decoy lines, Shamir-split key custody, audit windows, quality-score settlement, and the claim that signals stay secret while track records stay verifiable.
DEVIATIONS.md: most important caveat source because it records concrete implementation drift from whitepaper claims instead of hiding it.
www.djinn.gg/docs: useful as the highest-level public product framing, especially the language around decentralized information marketplace, cryptographically verifiable track records, and Base-settled USDC flows.
Why this entry belongs in the corpus
It adds a rare mechanism class: sale of private intelligence with cryptographic accountability rather than public market making or social-proof reputation alone.
It gives the corpus a comparison point connecting TLSNotary-style provenance, Bittensor validator/miner roles, escrow/collateral settlement, and public track-record policy.
The durable insight is that Djinn is best analyzed as infrastructure for accountable information sale, not merely as a betting app or a prediction product.