Client SDK

The Djinn SDK handles client-side cryptography so your plaintext pick never leaves your device. The API only ever sees encrypted data.

What the SDK does

Signal creation flow

import { encryptSignal, generateDecoys } from "@djinn/sdk";

// 1. Fetch network config (cached, do once)
const config = await fetch("https://djinn.gg/api/network/config")
  .then(r => r.json());

// 2. Fetch odds data for decoy generation
const odds = await fetch("https://djinn.gg/api/odds?sport=basketball_nba")
  .then(r => r.json());

// 3. Generate decoys locally (NEVER use server suggestions)
const realPick = {
  event_id: "abc123",
  market: "spreads",
  pick: "Celtics -4.5",
  odds: -110,
  bookmaker: "DraftKings",
};
const decoys = generateDecoys({
  realPick,
  availableLines: odds,  // from The Odds API
});

// 4. Encrypt signal locally (plaintext never leaves this device)
const encrypted = await encryptSignal({
  pick: realPick,
  decoys,
  validators: config.validators,
  shamirK: config.shamir.k,
});

// 5. Commit on-chain (your wallet signs this)
// const tx = await signalCommitment.commit(...)

// 6. Distribute shares via API (only ciphertext sent)
await fetch("https://djinn.gg/api/genius/signal/commit", {
  method: "POST",
  headers: { "Authorization": "Bearer ...", "Content-Type": "application/json" },
  body: JSON.stringify({
    encrypted_blob: encrypted.blob,
    commit_hash: encrypted.hash,
    shares: encrypted.shares,
    commit_tx_hash: "0x...",
    event_id: realPick.event_id,
  }),
});

Security properties