docs: add BACKERS.md (public sponsors)#14
Merged
Conversation
Add a BACKERS.md at the repo root listing public GitHub Sponsors of the DIG Network, with a link to sponsor and a note on private sponsors. Docs-only change, no behavior/API impact -> patch bump (0.11.1 -> 0.11.2), workspace version + regenerated Cargo.lock entries for the 5 in-workspace crates that track it. Closes #408 (digstore portion) Co-Authored-By: Claude <noreply@anthropic.com>
dkackman
pushed a commit
to dkackman/digstore
that referenced
this pull request
Jul 11, 2026
… (Wave-1 DIG-Network#5/DIG-Network#6/DIG-Network#13/DIG-Network#14) Close the biggest journey gaps before a developer ever spends DIG. Everything in this slice is FREE — no wallet, no chain, no spend — so a developer can scaffold, preview through the real read path, and preview cost before the one paid step. DIG-Network#5 `digstore new <template>` — a free, no-mint scaffolder (today the only on-ramp, `init`, mints 100 DIG into an empty dir). Five templates embedded in the binary (include_str!): static-site, vite-react, next-static, nft-drop, dapp-window-chia. Each writes a runnable local project — a `dig.toml`, a starter app, and (dapp/NFT) a `window.chia` usage example. Refuses a non-empty dir without --force; creates no `.dig` and never touches chain. DIG-Network#6 `digstore dev` — the local inner loop: build-on-save + serve the REAL dig:// read path locally (init_store → add → commit → host runtime → merkle-verify → AES-GCM-decrypt, the same plumbing as compile/cat), with live reload + an injected dev `window.chia` shim. So "renders under dev" == "renders after deploy". Poll-based watcher (no notify dep); multi-thread tokio runtime so a page's asset burst doesn't stall; SPA fallback for routes but a true 404 for missing assets; shims injected only into HTML at request time (never baked into the served bytes). DIG-Network#13 `digstore doctor` + `commit --dry-run` — `doctor` runs pre-publish checks (seed present/unlocked, funds vs 100 DIG + XCH fee, dighub login, default remote reachable, content dir exists) as pass/fail, exits non-zero on a hard fail, never spends. `commit --dry-run` computes + prints the resulting version (root) and the exact DIG/XCH cost with NO seed unlock, NO wallet scan, NO anchor, NO finalize. DIG-Network#14 task-first CLI help — one-line `about` strings lead with the task (commit = "Publish your staged files as a new version"); the commit success line is now a plain "Published a new version — it's live and permanent." with the capsule id below it and the module/coin protocol detail behind --verbose. Shared `dig.toml` reader extracted to `dig_toml::DigToml` (deploy + dev + doctor; removes deploy's private copy). Templates/assets embedded via include_str!. TDD: failing tests first throughout. 178 lib tests + new integration suites (cli_new, cli_dev, cli_doctor, cli_commit_dryrun, cli_help additions) green against the installed binary; cargo fmt + clippy -D warnings clean. Guest wasm built and binary reinstalled per digstore discipline. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GjQgGAisBupqs7vpkmUhuN
dkackman
pushed a commit
to dkackman/digstore
that referenced
this pull request
Jul 11, 2026
…pletion (Wave-1/2 DIG-Network#8/DIG-Network#19/DIG-Network#20/DIG-Network#21/DIG-Network#27) Drives the digstore developer-platform roadmap initiatives: - DIG-Network#8 deploy: add `--if-changed` (skip the 100 DIG + XCH spend + push when the built output reproduces the store's current on-chain version — CI-safe no-op guard) and `--dry-run` (preview resulting root + exact cost, no spend/adopt/ push). Print the hub URL on a real deploy. Refactor stage_to_root into a shared build_prepared + staged_root_or_noop so the deploy guard SEES the root without the no-op error (one root-computation path). - DIG-Network#19 dig.toml: extend the committable manifest with `ignore` globs (applied via a transient .digignore at staging), a `private` policy bit (the secret recovery key is NEVER stored — supplied via --salt/DIGSTORE_STORE_SALT), and a [metadata] table. Add the DIGSTORE_* env layer with uniform precedence flags > env > dig.toml > defaults (read_with_env), wired into deploy/dev/doctor. - DIG-Network#20 link: `digstore link <storeId|urn>` attaches the CWD to an existing project (writes dig.toml + remote), offline, no mint/spend/seed. - DIG-Network#21 setup/auth: one guided first-run (seed import/generate -> fund check w/ get-XCH/DIG pointer -> optional dighub login), explaining seed-signs-chain vs login-gates-push. Reuses the seed/login command paths. - DIG-Network#27 completion/schema/man: `digstore completion <shell>` (clap_complete), `digstore --help-json` (machine-readable command schema), and generated man pages (clap_mangen, library fn for docs tooling) — all derived from the clap model so they never drift from the binary. - DIG-Network#14: demote `trusted host key:` + confirmed `anchored (coin …)` in `init` output behind --verbose (task-first default surface). TDD throughout: failing tests first; full integration suite green against the reinstalled binary; fmt + clippy -D warnings clean. Docs: SYSTEM.md digstore Exposes + runbooks/digstore.md updated. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GjQgGAisBupqs7vpkmUhuN
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds
BACKERS.mdat the repo root: a public thank-you/sponsors page listing GitHub Sponsors of the DIG Network, with a link to https://github.com/sponsors/DIG-Network and a note that private sponsors are appreciated too.Why
Issue #408 asks for a standard sponsors/backers page across DIG Network repos so public sponsors get visible attribution and the sponsor link is easy to find from the repo itself.
Verified
Cargo.tomlworkspace version bumped0.11.1->0.11.2.Cargo.lockviacargo metadata(no build) so the 5 in-workspace crates (digstore-chain,digstore-chunker,digstore-cli,digstore-core,digstore-remote) that useversion.workspace = truestay in sync with the manifest -- avoids a--lockedCI failure.Bump rationale
Patch (
0.11.1->0.11.2): docs-only addition, no public-API or behavior change.Closes #408 (digstore portion)
Co-Authored-By: Claude noreply@anthropic.com