How do I… integrate DIG into my app?
Wire a wallet + verified reads into your own app. One typed package —
@dignetwork/dig-sdk— plus a node-agnostic JSON-RPC read path gives you everything: connect a wallet, read verified content, build and broadcast spends, and deploy from CI. This page maps each task to the page that does it.
The mental model — two surfaces, kept separate
- A REST control plane —
hub.dig.net/v1, bearer-JWT — for managing stores, domains, teams, and webhooks. - A dig JSON-RPC 2.0 read path —
rpc.dig.net, spoken identically by every node — that streams verified ciphertext you decrypt client-side.
One wallet surface (CHIP-0002 window.chia) over two transports (injected, or WalletConnect → Sage), unified by the SDK's ChiaProvider. Spends are always built by the canonical CHIP-0035 wasm and signed by the user's wallet — never hand-rolled.
How do I connect a wallet?
Use ChiaProvider.connect() — it prefers the injected window.chia (DIG Browser) and falls back to WalletConnect → Sage, with the same method names and result shapes either way.
→ The DIG SDK → ChiaProvider · Using window.chia
How do I read verified content?
Use DigClient — it streams ciphertext + inclusion proofs over the dig RPC and verifies, then decrypts client-side. Pass the on-chain root as the trust anchor; the SDK does the rest.
→ The DIG SDK → DigClient · What is the dig RPC? · Methods
How do I build and broadcast a spend?
Build the spend bundle with the canonical CHIP-0035 wasm (re-exported by the SDK at the /spend subpath), have the wallet sign it, then broadcast. Build → sign → broadcast — never assemble a coin spend by hand.
→ Building spends · CHIP-0035 store-coin spends & delegation
How do I gate content behind a payment or an NFT?
Use the SDK's Paywall — a high-level pay-to-unlock / NFT-or-collection-ownership gate that composes the provider with the spend builder.
→ The DIG SDK → Paywall · Build a dapp on Chia
How do I deploy from CI?
Wire dig-network/deploy-action for push-to-publish with free PR previews, or drive digstore deploy yourself. Authorize CI with a revocable deploy key, not your wallet seed.
→ Deploy from GitHub Actions · Deploy keys
How do I get notified about deploys?
Register a webhook to receive a signed event when a deployment changes state — for a bot, a dashboard, or follow-on work.
→ Webhooks
How do I integrate without reading prose?
Every surface is machine-readable: /openapi.json, /openrpc.json, /error-codes.json, /llms.txt, and a knowledge graph. Branch on stable error codes, never on message text.
→ Machine-readable surfaces · Error codes
Build the whole thing end-to-end
The single thread from scaffold to a wallet-aware app live on your own domain.
→ Build a dapp on Chia · Example gallery
Go deeper
- The full integration overview → For integration developers
- Verified reads & proofs → Inclusion vs execution proofs · Streaming
- The normative wallet contract → The window.chia provider spec
- Everything → Protocol deep-dive · Concepts & glossary