"dighub" ile etiketlenmiş 29 doküman etiketlendi

What changed across the DIG developer surfaces — the dig-store CLI, the dig RPC, and the window.chia provider — including breaking changes and the versioning rules for each.

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.

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.

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 ile içerik adresli yayınlama, kör barındırma ve alma için dig RPC ile içerik erişimi için DIG Browser dahil olmak üzere DIG Network temel bileşenlerine genel bakış.

Tamamen makine tarafından okunabilir bir platform — OpenAPI/OpenRPC, kataloglanmış bir hata taksonomisi, canlı fiyatlandırma, JWKS, sayfa başına JSON ve tipli bir @dignetwork/dig-sdk — böylece tek bir satır insan düzyazısını bile taramadan uygulamanıza bir cüzdan + doğrulanmış okumalar bağlarsınız.

Every DIG error code in one place: dig RPC JSON-RPC codes, dig-store CLI exit codes, and DIGHUb user-facing codes — each with what it means and what to do.

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.

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.

Where to get help with DIG — the community Discord, GitHub issues, and how to file a report that gets answered fast.

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.

Step-by-step: connect a Chia wallet to DIGHUb, including exactly where Sage's WalletConnect setting lives.

Earn commemorative NFT badges for using DIGHUb, then stake them into the DIG rewards vault to earn a share of $DIG — all from the browser, with your wallet connected only when you stake or claim.

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.

Two proof types: synchronous Merkle inclusion proofs that pin served bytes to an on-chain root, and asynchronous ZK / risc0 execution receipts that attest faithful serving — gated on the control plane.

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.

Sanatı kalıcı olarak kurcalamaya karşı kanıtlı bir DIG capsule'ünde yaşayan tam bir CHIP-0007 koleksiyonu basın — tek bir atomik imzalı demet, gerçek telif hakları ve zincir üzerinde henüz kanıtlayamadıkları şeyi asla sahtelemeyen dürüst drop mekanikleri.

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.

Where to check the health of the DIG services — the dig RPC (rpc.dig.net), DIGHUb (hub.dig.net), and the resolver (on.dig.net) — plus how RPC and provider versions are signalled.

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.

The integrating-developer reference for the DIG window.chia wallet provider — the provider object fields, connect, events, every read and write method with params and returns, and the CHIP-0002 error codes to branch on.

Git-style remote protocol via dig:// URLs, per-request BLS signing, clone/pull/push operations, and self-hosted node setup.

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

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.

Detect and use the DIG Browser's injected Chia wallet provider for permission-gated key and signing operations.

Public RPC endpoint usage, portability across nodes, operating your own node, and rate limiting policies.

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.

How the DIG Chrome extension's built-in Chia wallet protects your keys: encryption at rest, phishing and scam warnings, revocable site permissions, and the Argon2id/AES-256-GCM crypto behind it.

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.