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
// SPDX-License-Identifier: Apache-2.0
// SPDX-FileCopyrightText: 2026 Nirapod Labs
//! The wrapper that marks a value as proven against a block.
use BlockIdExt;
/// A value proven to sit in the state of a block the caller trusts.
///
/// The value's Merkle proofs were checked to root at the [anchor](Self::anchor)'s hash,
/// and the value was bound to that block's state by hash. Nothing the server said was
/// taken on trust along the way, including which shard block held the account.
///
/// # What this does and does not say
///
/// The claim is relative: the value is as trustworthy as the block in its
/// [anchor](Self::anchor), and no more. That block's own worth depends on where it came
/// from. Handing [`account_at`](crate::Client::account_at) a head read from the same
/// server proves only that the server is internally consistent, which a server making
/// things up can also manage. A block from [`Client::sync`](crate::Client::sync), and so
/// from [`Client::account`](crate::Client::account), was walked to from the key block the
/// config pins with a validator signature set checked at every step, and rests on nothing
/// the server chose.
///
/// # Why it cannot be forged
///
/// There is no public constructor. A `Verified<T>` exists only where this crate checked
/// the proofs, so a value of this type in a signature is a claim the type system keeps
/// honest rather than a convention a caller can opt out of.