SBIX Docs — Démarrage rapide

Créer une preuve (≤3s P50)

Copier

BASE="https://demo.sbix.io"
API="<YOUR_API_KEY>"

curl -s -X POST "$BASE/certify/" \
  -H "Content-Type: application/json" \
  -H "X-API-Key: $API" \
  -H "Idempotency-Key: $(uuidgen || echo demo-uuid)" \
  -d '{"leaves":["TX-AB12","TX-34CD","TX-EEFF"]}'
# → { "proof_id": "...", "merkle_root": "...", "timestamp": "..." }

Lister les proofs

Copier

curl -s "$BASE/certify/proofs?limit=50" -H "X-API-Key: $API"
# → { "items":[...], "next_cursor":"..." }

Exports audit (JSON/CSV/ZIP)

Copier

PID="sbix-1a2b3c4d"

# Preuve complète
curl -s -L "$BASE/certify/export/proof/$PID.json" -H "X-API-Key: $API" -o proof.json
curl -s -L "$BASE/certify/export/proof/$PID.csv"  -H "X-API-Key: $API" -o proof.csv
curl -s -L "$BASE/certify/export/proof/$PID.zip"  -H "X-API-Key: $API" -o proof.zip

# Chemin d'inclusion (fichier .proof)
curl -s -L "$BASE/certify/export/inclusion/$PID.proof?target=TX-AB12" \
  -H "X-API-Key: $API" -o inclusion.proof

Le ZIP peut inclure manifest, proofs, anchors et README auditeur (selon configuration).

import requests
BASE = "https://demo.sbix.io"; API = "<YOUR_API_KEY>"
H = {"X-API-Key": API}

# 1) Create
p = requests.post(f"{BASE}/certify/", json={"leaves":["TX-AB12","TX-34CD"]}, headers=H).json()
pid = p["proof_id"]

# 2) Export a path for TX-AB12
inc = requests.get(f"{BASE}/certify/proof/{pid}/path", params={"target":"TX-AB12"}, headers=H).json()
print("root:", inc["root"], "steps:", len(inc.get("path") or inc.get("proof") or []))

Vérification côté serveur (format D)

Copier

# Serveur recharge le proof par proof_id et reconstruit
curl -s -X POST "$BASE/verify/" \
  -H "Content-Type: application/json" \
  -d '{"proof_id":"<PID>","target":"TX-AB12"}'
# → { "valid": true, "used_strategy": "strict" }

Pratique pour les auditeurs : ils ne manipulent pas les étapes Merkle.

Vérification client/offline (format A)

Copier

# Avec root + chemin d'inclusion normalisé
curl -s -X POST "$BASE/verify/" \
  -H "Content-Type: application/json" \
  -d '{
    "leaf":"TX-AB12",
    "root":"4f1a...e8",
    "proof":[{"position":"right","hash":"aa..."},{"position":"left","hash":"bb..."}]
  }'
# → { "valid": true }

Position ∈ {left,right}. Le serveur normalise les strings avant hashing.

Valider / Enregistrer un ruleset

Copier

# GET ruleset courant
curl -s "$BASE/compliance/ruleset"

# Valider (mode=validate)
curl -s -X POST "$BASE/compliance/ruleset" \
  -H "Content-Type: application/json" \
  -d '{"mode":"validate","ruleset":"version: \"1.0\"\nrules:\n  - field: amount\n    condition: greater_than\n    value: 10000\n    reason: Large movement"}'

# Enregistrer (mode=save)
curl -s -X POST "$BASE/compliance/ruleset" \
  -H "Content-Type: application/json" \
  -d '{"mode":"save","ruleset":"version: \"1.0\"\nrules:\n  - field: aml_risk\n    condition: greater_than\n    value: 0.8\n    reason: High AML score"}'

Tester / Rejouer / Lister alertes

Copier

# Test unitaire
curl -s -X POST "$BASE/compliance/test" \
  -H "Content-Type: application/json" \
  -d '{"tx":{"tx_id":"TX-1","amount":20000,"jurisdiction":"IR","aml_risk":0.9,"tx_type":"DEX"}}'

# Replay du ledger
curl -s -X POST "$BASE/compliance/replay"

# Lister les alertes
curl -s "$BASE/compliance/alerts?limit=50&offset=0"