「chip-0035」タグのついた19記事

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.

エンドツーエンド：Reactアプリを足場作りし、dig-sdkでページ内Chiaウォレット（window.chia + WalletConnectフォールバック）を組み込み、chip35 wasmで支出を構築・署名し、オンチェーンにデプロイしてカスタムドメインを追加する — DIGのすべてのプリミティブを1本の流れで。

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.

JSON-RPC 2.0によるDigStore capsule向けのネットワーク全体の読み取りインターフェース。構造上盲目であり、信頼なしに検証可能で、あらゆるサイズでストリーミング可能です。

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.

アートが改ざん検知可能なDIG capsuleに永続的に存在するCHIP-0007コレクション全体をmintする — 1つのアトミックな署名済みバンドル、実在するロイヤリティ、そしてオンチェーンでまだ証明できないことを決して偽らない誠実なドロップの仕組み。

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.

capsule、store、generation、URN、取得キー、dig RPC、chia://プロトコル、オンチェーンアンカリングなど、DIG Networkの中核となるエンティティの1ページ索引 — それぞれ一度だけ定義し、詳細ドキュメントへリンクします。

OpenAPI/OpenRPC、体系化されたエラー分類、リアルタイム価格、JWKS、ページごとのJSON、そして型付きの@dignetwork/dig-sdkを備えた、完全に機械可読なプラットフォーム — 人間向けの文章を一行もスクレイピングすることなく、ウォレットと検証済みの読み取りをアプリに組み込めます。