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
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
use ARID;
use Envelope;
use crateResult;
/// Unified trait for key-value storage backends using ARID-based addressing.
///
/// All implementations provide write-once semantics: once an envelope is stored
/// at an ARID, subsequent attempts to write to the same ARID will fail with an
/// `AlreadyExists` error.
///
/// # Security Model
///
/// - ARID holder can read (by deriving storage key)
/// - ARID creator can write once (by deriving storage key)
/// - Storage networks see only derived keys, never ARIDs themselves
/// - ARIDs shared only via secure channels (GSTP, Signal, QR codes)
///
/// # Implementations
///
/// - `MainlineDhtKv`: Fast, lightweight DHT storage (≤1 KB messages)
/// - `IpfsKv`: Large capacity, content-addressed storage (up to 10 MB messages)
/// - `HybridKv`: Automatic optimization by size, combining DHT speed with IPFS
/// capacity
///
/// # Thread Safety
///
/// The `KvStore` trait requires `Send + Sync`, meaning implementations can be
/// safely shared across threads. However, the futures returned by async methods
/// are **not required to be `Send`** (note the `?Send` bound on `async_trait`).
///
/// **What this means in practice:**
///
/// - ✓ You can share a `KvStore` instance across threads
/// - ✓ You can call methods and await them on any thread
/// - ✓ Multiple threads can perform concurrent operations
/// - ✗ You cannot move an in-flight future to another thread
///
/// **Working pattern:**
/// ```no_run
/// # use hubert::{ipfs::IpfsKv, KvStore};
/// # use bc_components::ARID;
/// # use bc_envelope::Envelope;
/// use std::sync::Arc;
///
/// # async fn example() {
/// let store = Arc::new(IpfsKv::new("http://127.0.0.1:5001"));
///
/// // Spawn threads that each do async work locally
/// let store1 = Arc::clone(&store);
/// let handle = std::thread::spawn(move || {
/// tokio::runtime::Runtime::new().unwrap().block_on(async {
/// let arid = ARID::new();
/// let env = Envelope::new("data");
/// store1.put(&arid, &env, None, false).await
/// })
/// });
/// # }
/// ```
///
/// **Non-working pattern:**
/// ```compile_fail
/// # use hubert::{ipfs::IpfsKv, KvStore};
/// # use bc_components::ARID;
/// # use bc_envelope::Envelope;
/// # async fn example() {
/// let store = IpfsKv::new("http://127.0.0.1:5001");
/// let arid = ARID::new();
/// let env = Envelope::new("data");
///
/// // ERROR: Cannot spawn !Send future across threads
/// tokio::spawn(async move {
/// store.put(&arid, &env, None, false).await
/// });
/// # }
/// ```
///
/// This limitation comes from underlying network client libraries and is
/// typical for async I/O code. It does not prevent concurrent operations - each
/// thread simply needs to `.await` its own futures locally.