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.

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-store, 블라인드 호스팅 및 검색을 위한 dig RPC, 콘텐츠 접근을 위한 DIG Browser 등 DIG Network 프리미티브 개요.

JSON-RPC 2.0을 통해 dig-store capsule을 읽기 위한 네트워크 전역 읽기 인터페이스; 구조적으로 블라인드이며, 신뢰 없이 검증 가능하고, 어떤 크기든 스트리밍할 수 있습니다.

내장 암호화와 URN 기반 주소 지정을 갖춘 Git 형태의 콘텐츠 주소 지정 방식 프로젝트 포맷으로, 단일 자기방어형 WebAssembly 모듈로 컴파일됩니다.

진짜로 소유하는 웹사이트나 앱을 배포하세요 — 대여하는 것이 아니라 온체인에서 나만의 자산으로 민팅됩니다. 빌드와 미리보기는 무료이며, 게시할 때만 소액의 균일한 $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.

capsule, store, generation, URN, retrieval key, dig RPC, chia:// 프로토콜, 온체인 앵커링 등 DIG Network의 핵심 엔티티를 한 페이지에 정리한 색인 — 각 항목을 한 번씩 정의하고 관련 심화 문서로 연결합니다.