28 篇文档带有标签「store」

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.

Full walkthrough of the dig-store CLI: initialize a store, commit files, and read content back. The parallel track to the web-first quickstart.

Complete command reference for the dig-store CLI, including wallet, store, staging, history, content, remote, and maintenance commands.

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

Auto-publish your built site or dapp to your existing DIG store on every push with the dig-network/deploy-action — git-push-to-deploy, free PR previews, and a PR comment + GitHub deployment status. Keyless CI auth, no long-lived hub secret.

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.

DIG Network 各基础原语概览：用于内容可寻址发布的 dig-store、用于盲目托管与检索的 dig RPC，以及用于内容访问的 DIG Browser。

发布一个你真正拥有的网站或应用 —— 作为你自己的链上资产铸造出来，而不是租来的。构建与预览完全免费；只有在发布时才需要支付少量统一 $DIG 价格，文件在你的浏览器中加密，因此任何主机都无法读取它们。

Every store gets a public, shareable tip page, and a one-line script embeds a Tip button on any site. Visitors tip you directly in $DIG, wallet to wallet — no account, no backend, no middleman.

The shortest path through DIGHUb: create a store, publish a capsule, give it a web address, and get tipped — all from the browser, wallet connected only when you publish or spend.

The shortest path through the dig-store CLI: install it, scaffold and preview for free, publish a capsule on-chain, share it over a remote, and read it back — each task linked to the page that walks it.

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.

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 §21 transport: dig:// locator resolution, the REST surface, the JSON-outer / Chia-codec-inner envelope, 2-leg push v1 (inline | presigned), the authenticated head (PUSH_DST), per-request §21.9 auth with exact signing messages, ETag/delta/pull, tombstone revocation, and decoy indistinguishability.

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

The committable dig.toml manifest and how to inject PUBLIC build-time config (RPC endpoint, asset/CAT ids, feature flags) into a dapp — plus the one hard rule: a blind static capsule holds no server secrets.

Merkle proofs, verified downloads, signed roots, revocation, and host attestation for dig-store security.

Publishing stores to remotes, downloading with verification, revoking roots, and understanding public vs. private access models.

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

List your dApp on the DIG Network dApp store (explore.dig.net): connect your wallet on DIGHUb, fill in the submission form, and an admin reviews it. Once approved, DIGHUb opens the listing for you automatically — no repository, no pull request, no waiting on infrastructure.

A content-addressed protocol for opening stores and resources directly from the DIG Network, with URN and shorthand forms.

Architecture of the content-addressable, encrypted WebAssembly store format: identity, generations, URNs, and compiled modules.

Git-style remote protocol via dig:// URLs, per-request BLS signing, clone/pull/push operations, and self-hosted node setup.

URN format and semantics, derivation of retrieval and decryption keys, AES-256-GCM-SIV encryption, and public vs. private store differences.

Workflow for initializing projects, managing staging areas, running multiple stores in one workspace, and typical release loops.

Register an HTTPS endpoint to be notified when a deployment changes state — queued, building, ready, or error. Each event is signed so you can verify it came from DIGHUb. The event contract — payload shape and signature — is stable; delivery is rolling out.

Git 形态、内容可寻址的项目格式，内置加密与基于 URN 的寻址；编译为单一的自我防护 WebAssembly 模块。

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