본문으로 건너뛰기

45개 문서가 "capsule" 태그에 분류되었습니다

모든 태그 보기

Build a dapp on Chia

처음부터 끝까지: React 앱을 스캐폴딩하고, dig-sdk로 인페이지 Chia 지갑(window.chia + WalletConnect 폴백)을 연결하고, chip35 wasm으로 스펜드를 빌드 및 서명한 다음, 온체인에 배포하고 커스텀 도메인을 추가합니다 — 모든 DIG 프리미티브를 하나로 잇는 흐름입니다.

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.

CLI tutorial

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

Conformance & Security

Blind serving model, decoy streams, CORS, caching, rate limiting, and conformance checklist for dig RPC endpoints.

Deploy an existing app (web upload)

Already have a built site or SPA? How DIG serves it — the store as your file set, index.html + assets + routes, the anchored-root serve model — and a worked example: upload a real dist/ folder through DIGHUb's web upload and reach it.

Deploy from GitHub Actions

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.

DIG Network

콘텐츠 주소 지정 방식 게시를 위한 dig-store, 블라인드 호스팅 및 검색을 위한 dig RPC, 콘텐츠 접근을 위한 DIG Browser 등 DIG Network 프리미티브 개요.

dig RPC란?

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

dig-store란?

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

Example gallery

Example DIG dapps you can clone and open in a template — a static site, a wallet-wired React app, and an NFT drop page. Start from working code instead of a blank folder.

FAQ

Frequently asked questions about DIG — what it costs, whether you can iterate for free, how the host can't read your app, custom domains, and updates.

For app developers

진짜로 소유하는 웹사이트나 앱을 배포하세요 — 대여하는 것이 아니라 온체인에서 나만의 자산으로 민팅됩니다. 빌드와 미리보기는 무료이며, 게시할 때만 소액의 균일한 $DIG 가격을 지불합니다. 파일은 브라우저에서 암호화되므로 어떤 호스트도 그 내용을 읽을 수 없습니다.

For content consumers

Open chia:// content that your own browser verifies against the blockchain — no host can alter or fake it, private content stays private from the host, and it's permanent and re-hostable anywhere, so nobody can take it down or lock you in.

For NFT developers

위변조가 불가능한 DIG capsule에 예술 작품이 영구적으로 저장되는 CHIP-0007 컬렉션 전체를 민팅하세요 — 하나의 원자적 서명 번들, 실제 로열티, 그리고 온체인에서 아직 증명할 수 없는 것을 절대 거짓으로 내세우지 않는 정직한 드롭 메커니즘까지.

Get tipped for your store

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.

How do I… use DIGHUb?

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.

How do I… use the dig-store CLI?

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.

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.

L0 · URN & addressing

The normative urn:dig:chia URN grammar, the rootless retrieval_key = SHA-256(canonical) invariant, resourceKey normalization, the three-way scheme split (chia:// vs §21 dig:// vs dig://* browser), and the salt addressing extension.

L1 · BLS signatures & domain separation

Chia AugScheme (G1 48B / G2 96B), the five mutually-distinct role DSTs (PUSH/NODE/TOMB/REQ/ATTEST) with their exact signing-message preimages, rogue-key rejection, and the host↔guest parity fixtures.

L1 · Cryptography

Layer 1 read-crypto: HKDF-SHA256 key derivation (salt-mixed secret), AES-256-GCM-SIV fixed-nonce seal, the byte-exact constants table, and the one-crypto-implementation invariant (producer = host = verifier = dig-client-wasm).

L1 · Merkle inclusion proofs

The D5 per-resource UNTAGGED leaf = SHA-256(ciphertext), the NODE_TAG fold, odd-node carry-up, the proof-length ≤ ceil(log2 n) binding contract (D8), and the base64 X-Dig-Inclusion-Proof wire layout.

L2 · Capsule format (the DIGS data section)

BINDING contract D1: the DIGS blob byte layout (big-endian, self-describing), all 12 SectionIds and their body formats (KeyTable D3, ChunkPool D4, MerkleNodes D5, ChainState, Filler), and the big-endian rationale.

L2/L3 · The self-defending module

Fixed-size obfuscation (128 MiB uniform blob, deterministic ChaCha20 filler), WASM injection memory layout (BINDING D2: 2 MiB offset, 384 MiB ceiling), the self-serving guest pipeline, oblivious gather, decoy generation, and the disabled host-attestation gate.

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 digs projects.

Project config & build-time values

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.

Protocol: Overview

DIG 프로토콜을 하위에서 상위로 이어지는 7개 레이어로 정리한 규범적/구현 정의 문서. capsule(storeId:rootHash)이 기본 단위이며, 호스트는 내용을 알지 못하고 리더가 체인을 기준으로 검증합니다. 이 문서가 권위 있는 프로토콜 레퍼런스입니다.

Quickstart

Ship your first site on DIG — free to build and preview, you only pay the uniform capsule price when you publish. Web-first path (no wallet to start) plus a parallel CLI track.

Run a DIG node

What a dig-node is, why you'd run one, and how to install it — the apt repository for Ubuntu/Debian or the cross-platform DIG Installer.

Scaffold an app (create-dig-app)

npm create dig-app — scaffold a wallet-wired, deployable DIG app in one command. Five templates (static, vite-react, next-static, nft-drop, dapp-window-chia), all free to build and preview; you pay the uniform capsule price only when you publish.

Store Structure

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

Streaming

Streaming chunk model for byte methods: chunk object structure, 64 KiB alignment, reassembly, proof verification, and reference client loop.

The dig-store WASM Store Format

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

Troubleshooting — get unstuck

Every failure gives you a stable code and a request-id that ties straight to the server log, on-chain spends are race-guarded so you never double-pay, and clear pre-flight guards stop wasted capsules before you spend $DIG.

Using dig-store in your project

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

Webhooks

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의 핵심 엔티티를 한 페이지에 정리한 색인 — 각 항목을 한 번씩 정의하고 관련 심화 문서로 연결합니다.