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
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
//! Core trait abstractions and dependency inversion interfaces for the Kinetic engine.
//!
//! Defines the abstract contracts for Kinetic's three primary pluggable backends:
//!
//! - `VdfEngine`: CPU-bound Wesolowski VDF proof evaluation and verification (chiavdf).
//! - `StorageEngine`: Key-value persistence and prefix scanning (Sled B-tree).
//! - `GovernanceEngine`: Protocol proposal verification and state transitions.
//!
//! These traits enable `kinetic-core` to be network-agnostic. The concrete implementations
//! live in `kinetic-vdf`, `kinetic-storage`, and `kinetic-core/src/governance/engine/`
//! respectively. The active `GovernanceEngine` is selected at compile time from `network.json`
//! via the `GOVERNANCE_MODEL` constant.
use crate;
use crate;
use crate;
/// Abstract interface for Verifiable Delay Function (VDF) computation engines.
///
/// The canonical implementation in `kinetic-vdf` wraps the `chiavdf` Wesolowski
/// VDF library. The challenge is always a 32-byte SHA-256 hash derived from
/// `network_id || name || salt || drand_signature_hex`.
/// Abstract interface for local embedded database storage engines.
///
/// The canonical implementation in `kinetic-storage` wraps a Sled B-tree database.
/// All keys in Kinetic are namespaced with a `{NETWORK_ID}_` prefix so that multiple
/// TLD networks can share a physical database file without key collisions.
/// Abstract interface for protocol governance state verification and action execution.
///
/// Four concrete engines are available (selected at compile time via `GOVERNANCE_MODEL`):
/// `sovereign`, `council`, `permissionless`. See `kinetic-core/src/governance/engine/`.
///
/// The engine is always called in a two-step sequence:
/// 1. [`verify_action`](Self::verify_action) — validates signatures, thresholds, and timelocks.
/// 2. [`execute_action`](Self::execute_action) — mutates state and returns side effects.