Djinn

  • Name: Djinn
  • URL: https://www.djinn.gg/
  • Category: encrypted information marketplace / accountable prediction-sale protocol / TLSNotary-backed executability middleware / collateralized signal-audit infrastructure
  • Summary: Djinn is worth cataloging not as just another sports-picks app or betting frontend, but as an attempt to turn sell-side intelligence into a reusable crypto control plane. Its primary materials split the system into encrypted signal creation, validator-held Shamir key shares, miner-side line-availability checks, collateral-backed service-level guarantees, audit settlement, and public track-record reporting. That makes Djinn a useful comparison point for prediction markets, copy-trading systems, TLSNotary-style web-proof rails, and reputation middleware, because the real mechanism is not market making or gambling settlement itself. It is the separation of information sale from execution, plus cryptographic and economic machinery that tries to make private signals saleable without revealing them to the marketplace operator.
  • What it does:
    • Lets analysts post encrypted prediction signals with per-signal pricing, SLA multipliers, expiries, and collateral backing
    • Commits signal hashes on Base while masking the real pick among decoy lines so observers cannot tell which committed line is the live signal
    • Splits signal decryption keys across Bittensor validators with Shamir secret sharing so buyers reconstruct signals locally after purchase instead of receiving plaintext from a central server
    • Uses miner-side sportsbook checks and later TLSNotary proofs to attest that a signal was actually executable at purchase time
    • Settles repeated buyer-analyst relationships through audit cycles that compare finalized outcomes against a collateral-backed quality score rather than through one-off refunds
    • Exposes public track records, purchase-success metrics, and protocol accounting through onchain contracts and an open subgraph rather than only through hosted screenshots or chat logs
    • Offers a separate public web-attestation flow that turns TLSNotary proofs into a burn-gated service, showing the project is also packaging web-proof infrastructure beyond its sports-prediction niche
  • Key claims:
    • The core reusable insight is that Djinn is trying to unbundle who knows what to do from who can execute, then price the first capability without forcing the analyst to reveal the underlying signal to the marketplace operator or to non-buyers.
    • The strongest mechanism is the combination of encrypted commitment, decoy masking, threshold-style key custody across validators, and local buyer-side decryption. That makes Djinn more analytically useful than filing it as a generic picks marketplace.
    • The purchase flow exposes an unusual control surface: executability is checked through validator/miner coordination before decryption, so the system is not only selling analysis but also brokering a claim that the analysis was still actionable at the moment of sale.
    • The audit design matters because Djinn does not simply offer refund policy or reputation stars. It turns analyst accountability into a repeated collateralized SLA relationship with fixed audit windows, quality-score computation, and capped USDC-versus-credit settlement tranches.
    • The TLSNotary layer is important for comparison work. Miners are not only generic data fetchers; they are supposed to prove line availability with HTTPS transcript attestations, which makes Djinn a useful bridge between web-proof infrastructure and application-level information markets.
    • The repository’s DEVIATIONS.md is especially valuable because it shows the live system is not identical to the whitepaper. The repo says some earlier ZK-track-record machinery was removed in favor of public onchain audit-settlement computation, idiot-side wallet recovery is still staged, and MPC / OT / MAC-hardening work has evolved through multiple implementation phases. That makes Djinn analytically useful as a living stack with explicit design-versus-implementation tension, not just as a polished protocol narrative.
    • Djinn belongs in the active corpus because it provides a rare comparison point for private but saleable intelligence as infrastructure. Without it, sports prediction, copy trading, web attestation, and reputation systems are too easy to flatten into one vague bucket.
  • Whitepaper: Djinn publishes a repository whitepaper and links to a site-hosted PDF. The strongest reviewed primary materials for this pass are collected in ../whitepapers/djinn-primary-sources-2026-05-13.md.
  • Sources:
  • Last reviewed: 2026-05-13 UTC