본문으로 건너뛰기

29개 문서가 "anchoring" 태그에 분류되었습니다

모든 태그 보기

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.

Command reference

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

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.

Deploy keys

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란?

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

For app developers

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

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.

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.

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.

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.

L5 · §21 transport & push

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.

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.

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.

Proofs & Security

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

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.

Sharing over a remote

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

Store Structure

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

The dig-store WASM Store Format

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

Troubleshooting

Fixes for the most common DIG failures — funding, confirmation timeouts, push conflicts, verification errors, and wallet/session problems.

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