Uçtan uca: bir React uygulaması iskeleleyin, dig-sdk ile sayfa içi Chia cüzdanını (window.chia + WalletConnect geri dönüşü) bağlayın, chip35 wasm'ı üzerinden bir harcama oluşturun ve imzalayın, ardından zincir üzerinde dağıtın ve özel bir alan adı ekleyin — her DIG temel bileşeni tek bir iplikten geçirilir.
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.
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.
Yerleşik şifreleme ve URN tabanlı adresleme ile Git şekilli, içerik adresli proje formatı; tek, kendini savunan bir WebAssembly moduline derlenir.
DIG üzerinde ilk sitenizi gönderin — inşa etmek ve önizlemek ücretsizdir, yayınladığınız anda yalnızca tek tip capsule fiyatını ödersiniz. Web öncelikli yol (başlangıçta cüzdan gerekmez) artı paralel bir CLI yolu.
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.
Temel DIG Network varlıklarının tek sayfalık dizini — capsule, store, generation, URN, alma anahtarı, dig RPC, chia:// protokolü ve zincir üzeri sabitleme — her biri bir kez tanımlanmış ve derinlemesine belgesine bağlanmış.
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.
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.
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.
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.
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.
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.
Normatif ve uygulamaya bağlı olarak yedi alttan üste katman şeklinde DIG Protokolü. capsule (storeId:rootHash) temel birimdir; host kördür ve okuyucu zincire karşı doğrular. Bu, yetkili protokol referansıdır.
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.
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.
Fixes for the most common DIG failures — funding, confirmation timeouts, push conflicts, verification errors, and wallet/session problems.
Workflow for initializing projects, managing staging areas, running multiple stores in one workspace, and typical release loops.
Gerçekten SAHİP OLDUĞUNUZ bir web sitesi veya uygulama gönderin — kiralanan değil, zincir üzerinde kendi varlığınız olarak basılmış. Ücretsiz inşa edin ve önizleyin; yalnızca yayınladığınızda küçük bir tek tip $DIG fiyatı ödeyin, dosyalar tarayıcınızda şifrelenir, böylece hiçbir host onları okuyamaz.
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.