Skip to content

fix(digstore-chain): pinned-root verification without full lineage walk (#1431) #31

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
MichaelTaylor3d merged 2 commits into from
Jul 21, 2026
Merged

fix(digstore-chain): pinned-root verification without full lineage walk (#1431) #31

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d4ec594
chore(digstore-chain): stub for pinned-root verify (#1431)
MichaelTaylor3d Jul 21, 2026
d6823f2
fix(digstore-chain): add fail-closed verify_pinned_root without linea…
MichaelTaylor3d Jul 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions Cargo.lock
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ exclude = ["crates/digstore-prover/guest", "crates/dig-client-wasm"]

[workspace.package]
edition = "2021"
version = "0.18.0"
version = "0.19.0"
license = "GPL-2.0-only"

[workspace.dependencies]
Expand Down
20 changes: 20 additions & 0 deletions SPEC.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -215,6 +215,26 @@ byte-format contract — it is kept here because it is a public surface an indep
- A writer delegate may advance the store's root (publish capsules) but can never change
ownership or the delegated set itself — only the owner key can.

### 9.1 Pinned-root chain-anchored verification (loopback read tier)

Scope note: like §9, this is a chain-authority contract exposed by `digstore_chain::singleton`,
not a `.dig` byte-format contract. It is normative for how a node serving a root-pinned URN
(`dig://<store_id>:<pinned_root>`) over the §5.3 loopback tier chain-anchors the request.

- `verify_pinned_root(chain, store_id, pinned_root) -> Result<()>` returns `Ok(())` **iff**
`pinned_root` equals the store's CURRENT on-chain generation root, and `Err` otherwise. It is
**fail-closed**: a chain-read failure, an absent unspent singleton, or any root mismatch is an
`Err` — never a false `Ok`. A caller MUST treat any `Err` as "do not serve".
- It is a **bounded** verification, NOT a lineage walk: every datastore generation is created
hinted to its `launcher_id` (the first `DataStore::get_recreation_memos` memo, == `store_id`),
so the current unspent singleton is located with a single `unspent_coins_by_hint(store_id)`
query and its root read from the ONE spend that created it (the tip's parent). Earlier
generations are never parsed. This deliberately sidesteps the full forward walk
(`sync_datastore`), which aborts if any single intermediate generation's spend is unparseable.
- **Anti-rollback**: only the current on-chain root passes; a root that was never on-chain and a
stale (superseded) generation are both rejected. Verifying a historical-but-real generation is
intentionally out of scope (it would require the per-generation enumeration this API avoids).

## 10. Per-capsule $DIG price (commit / deploy)

Scope note: like §9, this is a CLI/economic contract, not a `.dig` byte-format contract; it is
Expand Down
Loading
Loading