02Sheet 02.03.117 · Entries
A data entry whose name and value are both 64 bytes
string64 dataName and DataValue<64> both full.
FIG. · Where it sits · inside LedgerCloseMetapre-cap · H-B12 · H-B6
ManageDataOp.dataName at its 64-byte maximum
DataValue at its 64-byte maximum
The shape
string64 dataName and DataValue<64> both full. Core requires the name to be printable ASCII (ManageDataOpFrame.cpp:115).
Variants
| Variant | Protocol | Network | Source | Size | sha256 |
|---|---|---|---|---|---|
p30-mainnet-generated | P30 | mainnet passphrase | generated by stellar-core v30.0.0 change order varies: 20 orderings in 20 runs | 21,176 B | 0ec4a1c8d0a2… |
p30-testnet-generated | P30 | testnet passphrase | generated by stellar-core v30.0.0 change order varies: 2 orderings in 2 runs | 21,176 B | 38004ed92e2d… |
What a correct reader returns
| A correct reader finds | Value | Backed by |
|---|---|---|
| The name is 64 characters. | xdrproof.data-name-at-the-64-byte-maximum.xxxxxxxxxxxxxxxxxxxxxx | constructionsnapshotcorewalker |
| The value is 64 bytes of 0x5a. | 5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a | constructionsnapshotcorewalker |
Check it yourself
make verify # schema, hashes, the byte-for-byte round trip and every fact above
make oracle # the facts' values, re-read by stellar-core and the schema walkerEntry id max-length.data-name-64 · compiled from catalog/max-length.data-name-64.json · entry.json
A claimable balance with the maximum 10 claimants and a predicate at the maximum depth
claimants<10> full; the first claimant's predicate nests and/or/not to depth 4, the deepest core accepts (CreateClaimableBalanceOpFrame.cpp:78).
A transaction with the maximum 2 extra signers
Preconditions v2 extraSigners<2> full: two signed-payload keys, each needing its own signature; the transaction carries three.