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
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
//! Event-related database record types.
//!
//! Events in Rostra form a DAG (Directed Acyclic Graph) where each event
//! references parent events. The event "envelope" (metadata + signature) is
//! stored separately from the event "content" (payload) to allow content
//! pruning while maintaining DAG integrity.
use Cow;
use ;
use ;
use ;
use Serialize;
/// Record for the main `events` table.
///
/// Contains the signed event envelope (metadata + signature). The actual
/// content is stored separately in `content_store`.
/// Record for the `events_missing` table.
///
/// When we receive an event that references a parent we don't have, we create
/// a "missing" record for that parent. This drives sync to fetch the missing
/// event.
/// Marker record for the `events_heads` table.
///
/// The key `(author, event_id)` identifies the head; this empty struct just
/// marks its existence. A "head" is an event with no known children - the
/// current tip of the DAG for that author.
;
/// Authoritative value retained for a social-vote singleton winner.
/// Authoritative current projection retained for a social-vote winner.
/// Record for singleton event tables (`events_singletons`,
/// `events_singletons_new`).
///
/// All singleton records retain their source ID for deterministic ordering and
/// attribution. Social-vote records also retain their authoritative current
/// full-target/value projection so incremental updates do not depend on
/// GC-eligible source content.
// ============================================================================
// Content Deduplication Types (V1)
//
// These types support storing content by hash for deduplication across events.
// ============================================================================
/// Content stored in the `content_store` table, keyed by ContentHash.
///
/// This enables content deduplication - identical content (e.g., the same
/// image posted by multiple users) is stored only once.
;
/// Owned record for the `content_store` table.
pub type ContentStoreRecordOwned = ;
/// Per-event content processing state stored in `events_content_state` table.
///
/// This enum tracks the content processing lifecycle for each event:
///
/// ## State Transitions
///
/// ```text
/// Event inserted ──► Missing ──► (no entry) ──► Deleted/Pruned
/// │ │
/// │ └─ Content processed successfully
/// │ (side effects applied)
/// │
/// ├─ Can also go directly to Deleted/Pruned
/// │
/// └─► Invalid ──► Deleted
/// ```
///
/// Note: Events with `content_len == 0` skip the `Missing` state entirely. They
/// go straight to "no entry" (processed) unless they start in `Deleted`.
///
/// ## Interpretation
///
/// - **No entry in table**: Content has been processed for this event. This is
/// the normal state after successful content processing. Side effects (reply
/// counts, follow updates, etc.) have been applied. Also the state for events
/// with no content (`content_len == 0`) unless they start in `Deleted`.
///
/// - **`Missing`**: Event was inserted but content hasn't been received or
/// processed yet. The event's content side effects have NOT been applied.
///
/// - **`Invalid`**: Content was received but failed validation (e.g. CBOR
/// deserialization). RC has been decremented. Content bytes are discarded.
///
/// - **`Deleted` / `Pruned`**: Content is unwanted. RC has been decremented. An
/// eligible Deleted social-post edit may still contribute immutable
/// replacement metadata without ordinary content processing.
///
/// ## Idempotency Guarantee
///
/// The `Missing` state ensures content processing is idempotent:
/// - `process_event_content_tx` checks for `Missing` before processing
/// - If `Missing` → process content, then remove the marker
/// - If no entry → skip (already processed)
/// - If `Deleted`/`Pruned`/`Invalid` → skip ordinary processing; the narrow
/// Deleted social-post lineage exception remains idempotent table insertion
///
/// This prevents duplicate side effects (e.g., incrementing reply_count twice)
/// when the same content is received multiple times for the same event.
/// Result of looking up event content.
///
/// This is returned by `get_event_content_full_tx` and combines the per-event
/// state with the actual content from the content store.
// ============================================================================
// Event Reception Tracking (V6)
//
// These types track when and how we received each event.
// ============================================================================
use IrohNodeId;
use RostraId;
/// How we acquired an event.
///
/// Tracks the source and method by which we received an event, useful for
/// debugging sync issues, understanding network propagation, and analytics.
/// Information about when and how we received an event.
///
/// Stored in the `events_received_at` table, keyed by `(Timestamp,
/// reception_order)`.
///
/// The key `(Timestamp, u64)` is allocated durably from the database-local
/// reception sequence. Insertion fails without replacement if the key is
/// occupied. The event ID is stored in the value for lookup.