跳到主要内容

19 篇文档带有标签「chip-0035」

查看所有标签

Build a dapp on Chia

端到端教程:搭建一个 React 应用,用 dig-sdk 接入页内 Chia 钱包(window.chia + WalletConnect 回退),通过 chip35 wasm 构建并签名一笔支出,然后上链部署并添加自定义域名 —— 一条贯穿每个 DIG 基础原语的完整线索。

Building spends

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.

CHIP-0035 store-coin spends & delegation

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.

Concepts & glossary

DIG Network 核心实体的单页索引 —— capsule、store、generation、URN、retrieval key、dig RPC、chia:// 协议以及链上锚定 —— 每个术语只定义一次,并链接到其详细文档。

Deploy keys

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.

For integration developers

一个完全机器可读的平台 —— OpenAPI/OpenRPC、一套完整分类的错误体系、实时定价、JWKS、逐页 JSON,以及一个类型化的 @dignetwork/dig-sdk —— 让你无需抓取一行人类阅读的文字说明,就能将钱包与已验证的读取能力接入你的应用。

For NFT developers

铸造一整套 CHIP-0007 合集,其艺术作品永久存放于一个防篡改的 DIG capsule 中 —— 一个原子性的已签名支出包、真实的版税,以及诚实的发行机制,绝不会假装能证明尚未在链上得到证实的事情。

How do I… integrate DIG into my app?

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.

L0 · Identity & naming

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.

L4 · DIG CAT payment & pricing

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.

L4 · On-chain anchoring (CHIP-0035)

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.

L6 · The blind host model

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.

L6 · The dig RPC (machine interface)

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.

L6 · Verification, provenance & anchoring

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.

Methods

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

On-chain anchoring

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

Store Structure

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

The DIG SDK

@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.

What is the dig RPC?

用于读取 DigStore capsule 的全网统一读取接口,基于 JSON-RPC 2.0;天生盲态、无需信任即可验证,且可在任意大小下流式传输。