19 篇文件帶有標籤「chip-0035」

Every on-chain action is built by the canonical CHIP-0035 wasm, signed by the user's wallet, and broadcast — the build → sign → broadcast split. Never hand-roll a spend bundle.

The canonical CHIP-0035 wasm builder constructs every store-coin spend; admin / writer / oracle delegation is the on-chain primitive behind Teams and revocable CI deploy tokens — never hand-rolled.

Give your CI or an agent a revocable key that can publish new versions of your store — but never your wallet seed, and never the power to change ownership. Issue it once in DIGHUb, drop it into CI as DIGSTORE_WRITER_KEY, and revoke it any time.

The shortest path for integrating developers: connect a wallet, read verified content, build a spend the right way, and deploy from CI — using the typed @dignetwork/dig-sdk and the dig RPC, no prose-scraping required.

Layer 0 of the DIG Protocol: store vs capsule vs generation. store_id is the CHIP-0035 singleton launcher id. A store is an ordered sequence of capsules.

The DIG CAT TAIL asset id, the treasury inner puzzle hash, 3-decimal units, the dynamic USD-pegged per-capsule amount (no protocol constant), the atomic commit-bundle convention, and its non-enforcement caveat.

store = a CHIP-0035 singleton; capsule = a singleton update + root-advance. Free mint vs DIG-paid commit, the owner-discovery memo hint, and admin/writer/oracle delegation as the Teams / deploy-token primitive.

The provider-blindness invariant, serve_blind (framing-only decode), the root-pinned immutable response cache, the *.on.dig.net + custom-domain resolver, the /v1 control plane (CHIP-0002 login, JWT sessions, refresh reuse-detection, action re-auth, GitHub-OIDC CI), and the accept-on-signature push trust model.

The dig RPC is THE machine interface of the protocol: JSON-RPC 2.0 over HTTP POST, the full method catalogue, the chunk wire object (chunk_lens first-window-only, NO decoy field), range/window math, error codes incl. -32004, and the node profile vs the network profile.

The four ordered integrity gates (merkle inclusion → authenticated decryption → anchored-root pinning → risc0 execution), anchored-root pinning against the CHIP-0035 singleton via coinset.org, the authenticated head, tombstones, the MOCK-by-default risc0 caveat, the freshness contract, and provenance UX surfacing.

Complete dig RPC method set: dig.getContent, dig.getProof, dig.getCapsule, dig.getManifest, dig.listCapsules, dig.listCollectionItems, dig.getCollection, and service discovery methods.

Wallet seed setup, on-chain costs, funding, anchor status, and chain-verified downloads for DigStore projects.

Store identity via on-chain singleton launcher id, generations as capsules, content root, on-disk layout, and compiled module structure.

@dignetwork/dig-sdk — ChiaProvider (injected window.chia + WalletConnect→Sage), DigClient (verified reads), Paywall (pay-to-unlock / NFT-gating), and the canonical CHIP-0035 spends at the /spend subpath.

透過 JSON-RPC 2.0 讀取 DigStore capsule 的全網通用讀取介面；天生具有盲目性、無需信任即可驗證，且可在任何大小下進行串流傳輸。

從頭到尾完整流程：建立一個 React 應用骨架、用 dig-sdk 接上頁內 Chia 錢包（window.chia 加上 WalletConnect 備援）、透過 chip35 wasm 建構並簽署一筆花費，接著上鏈部署並加上自訂網域——一條主線串起每一個 DIG 核心元件。

DIG Network 核心實體的單頁索引——capsule、store、generation、URN、retrieval key、dig RPC、chia:// 協定，以及鏈上錨定——每個詞彙都僅定義一次，並連結到其深入文件。

鑄造一整個 CHIP-0007 收藏系列，其藝術作品永久存放在防竄改的 DIG capsule 中——一個原子性的已簽署花費包、真實的版稅機制，以及誠實的發行機制，絕不假裝提供尚無法在鏈上證明的保證。

一個完全機器可讀的平台——OpenAPI／OpenRPC、一套已編目的錯誤分類系統、即時定價、JWKS、逐頁 JSON，以及具型別的 @dignetwork/dig-sdk——讓你把錢包與經過驗證的讀取功能接進你的應用，完全不需要爬梳任何一行人類可讀的說明文字。