Skip to main content

16 docs tagged with "anchoring"

View all tags

Build a dapp on Chia

End-to-end: scaffold a React app, wire the in-page Chia wallet (window.chia + WalletConnect fallback) with the dig-sdk, build and sign a spend via the chip35 wasm, then deploy on-chain and add a custom domain — one thread through every DIG primitive.

CLI tutorial

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

Command reference

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

Concepts & glossary

One-page index of the core DIG Network entities — capsule, store, generation, URN, retrieval key, the dig RPC, the chia:// protocol, and on-chain anchoring — each defined once and linked to its deep doc.

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, with a PR comment + GitHub deployment status.

On-chain anchoring

Wallet seed setup, on-chain costs, funding, anchor status, and chain-verified downloads for DigStore 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 DigStore security.

Quickstart

Ship your first site on DIG — free to build and preview, you only spend 100 DIG 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 DigStore 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 DigStore in your project

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

What is DigStore?

Git-shaped, content-addressable project format with built-in encryption and URN-based addressing; compiles to a single self-defending WebAssembly module.