1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
# dig-chainsource-interface — the DIG Network canonical ChainSource provider interface.
#
# The SINGLE pure trait + query types every Chia chain-source provider implements and every
# consumer depends on. There is ONE ChainSource contract for the whole ecosystem — never a
# per-crate copy that could byte-drift. This crate is a pure LEAF: trait + query/result types +
# a typed error + KATs + docs. It performs NO I/O, holds NO keys, opens NO network, and ships NO
# concrete provider — those live in the provider crates and in chia-query (the registry +
# aggregating canonical source). See SPEC.md for the normative contract.
[]
= "dig-chainsource-interface"
# PATCH, not major. The chia-sdk-* uplift below is INTERNAL: every `chia-sdk-*`, `clvm*` and
# `chia-puzzle*` import is confined to `src/walk.rs`, and no type from any of them crosses a public
# signature — `LineageWalkError<E>` carries only `E`/`String`/`Bytes32`/`usize`/`Duration`, and the
# walk functions take and return `Bytes32`/`SingletonLineage`/`WalkBounds`. The one chia crate that
# IS on the public surface, `chia-protocol`, is unchanged at 0.36.1. So no consumer — including the
# `lineage-walk` ones — can observe this bump, and nine consumers pinning "0.3" must not be forced
# to edit a manifest for a change that cannot reach them.
= "0.3.2"
= "2021"
= "1.75.0"
= "Apache-2.0 OR MIT"
= "The DIG Network canonical ChainSource provider interface: the single pure trait + query types every Chia chain-source provider implements and every consumer depends on. Reads-only, no I/O, no keys, no network — chia-* deps only."
= "https://github.com/DIG-Network/dig-chainsource-interface"
= "README.md"
= ["dig", "chia", "chainsource", "coin", "provider"]
= ["cryptography::cryptocurrencies", "api-bindings"]
[]
= "0.36.1"
= "2"
# --- `lineage-walk` only (see [features]) ------------------------------------------------------
# The canonical launcher -> tip singleton walk DERIVES each successor by running the parent's inner
# puzzle, so it needs a CLVM evaluator and the vetted singleton layer/puzzle types. Every version is
# pinned to the same coherent chia-* set the rest of the DIG on-chain line rides; the SDK's own
# SingletonLayer is reused rather than re-implemented so the walk cannot byte-drift from the puzzle
# it authenticates against.
#
# The ceiling is chia-wallet-sdk 0.36.0 and the versions below are ITS dependency set, NOT the
# newest on crates.io: the primitives publish at 0.48 but the SDK cannot reach them, so 0.36.1
# primitives beside 0.36.0 `chia-sdk-*` is the coherent maximum. Raising either family past its
# own ceiling re-splits this crate rather than modernising it.
= { = "0.36.1", = true }
= { = "0.20.3", = true }
= { = "0.36.0", = true }
= { = "0.36.0", = true }
= { = "0.36.1", = true }
= { = "0.36.1", = true }
= { = "0.16.2", = true }
[]
= []
= []
# The canonical singleton lineage walk (`walk_singleton_lineage`). NON-DEFAULT: it pulls in a CLVM
# evaluator, and a consumer that only depends on the trait should not pay for one. Enabling it is
# purely additive — no existing item changes shape.
= [
"dep:chia-puzzle-types",
"dep:chia-puzzles",
"dep:chia-sdk-driver",
"dep:chia-sdk-types",
"dep:clvm-traits",
"dep:clvm-utils",
"dep:clvmr",
]
[]
= "0.36.1"
= "0.4"
# The in-process Chia Simulator: the lineage-walk tests authenticate against REAL singleton spends
# (launcher, eve, recreation, melt) rather than hand-built fixtures, so the adversarial cases are
# genuine chain data.
= "0.36.0"
= "0.36.1"
= "1"