27 डॉक्स टैग की गईं "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 DigStore CLI: initialize a store, commit files, and read content back. The parallel track to the web-first quickstart.

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

मुख्य DIG Network entities का वन-पेज इंडेक्स — capsule, store, generation, URN, retrieval key, dig RPC, chia:// protocol, और on-chain anchoring — हर एक को एक बार परिभाषित किया गया और उसके गहन डॉक से लिंक किया गया।

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.

DigStore (कंटेंट-एड्रेसेबल पब्लिशिंग के लिए), dig RPC (ब्लाइंड होस्टिंग और रिट्रीवल के लिए), और DIG Browser (कंटेंट एक्सेस के लिए) — DIG Network के प्रिमिटिव्स का अवलोकन।

एक वेबसाइट या ऐप शिप करें जिसे आप सच में ओन करते हैं — ऑन-चेन आपकी अपनी संपत्ति के रूप में mint किया गया, किराए पर नहीं। मुफ़्त में बनाएं और प्रीव्यू करें; पब्लिश करते समय ही एक छोटी यूनिफॉर्म $DIG कीमत चुकाएं, फाइलें आपके ब्राउज़र में एन्क्रिप्टेड होती हैं ताकि कोई host उन्हें पढ़ न सके।

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 digstore 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 DigStore 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 DigStore 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.

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

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

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

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 मॉड्यूल में कंपाइल होता है।

JSON-RPC 2.0 के ज़रिए DigStore capsules के लिए नेटवर्क-व्यापी read इंटरफेस; संरचना से ब्लाइंड, बिना भरोसे के सत्यापन योग्य, और किसी भी साइज़ पर स्ट्रीम करने योग्य।