SDKs
Two flavors that share the over-the-wire SPUR-IC receipt protocol: TypeScript for the browser and Node, Python for backends and the dait-cli command. Receipts round-trip bit-for-bit between languages.
| SDK | Package | Targets |
|---|---|---|
| TypeScript | @dait/core, @dait/browser, @dait/compute | Node 20+, modern browsers (ESM) |
| Python | dait-sdk | Python 3.11+, sync + asyncio |
What you can do with either SDK
- Submit a compute job to the marketplace (
x/compute_market). - Open a state channel with a winning host (
x/state_channel). - Verify host TEE attestation quotes (
x/tee_attest). - Co-sign updated channel states + verify host receipts client-side.
- Close cooperatively, or initiate a dispute and present the receipt trail.
- Query Proof-of-Useful-Work credit accrual (
x/pouw). - Send / receive wallet-to-wallet encrypted messages (
x/messaging). - Issue first-class agent accounts (
x/agent).
SPUR-IC receipt format
The HTTP framing (X-DAIT-Receipt, X-DAIT-State, X-DAIT-Channel-Id, X-DAIT-Version) is identical between TypeScript, Python, and the Go reference daemon. See SPUR-IC spec for the full wire format.
Status
Phase 0 scaffold. Cryptography primitives are stubbed with TODO Phase 1 until the on-chain modules are wired. No live signing keys ship in this tree.