02Sheet 02.03.198 · Entries

An offer match in a protocol-12 result decodes as ClaimOfferAtomV0: the seller is a raw ed25519 key

Before protocol 18 an offer claim was a ClaimOfferAtom whose seller was an AccountID.

FIG. · Where it sits · inside LedgerCloseMetaCAP-0038 · H-F8 · H-C7
ClaimAtom.CLAIM_ATOM_TYPE_V0 in a P12 result: the seller as raw ed25519, not an AccountID
an offer claim recorded as ClaimOfferAtomV0
pre-P18 result bytes

The shape

Before protocol 18 an offer claim was a ClaimOfferAtom whose seller was an AccountID. CAP-0038 turned it into the ClaimAtom union and kept old bytes readable: the AccountID discriminant (0) now reads as CLAIM_ATOM_TYPE_V0, and the seller as a bare 32-byte ed25519 key (Stellar-transaction.x, "ClaimOfferAtomV0 is a ClaimOfferAtom with the AccountID discriminant stripped"). Old results in SDF's lake still carry it. Readers that only handle ORDER_BOOK and LIQUIDITY_POOL claim atoms, or that print the seller without converting it to a G address, fail on every pre-P18 trade.

Variants

VariantProtocolNetworkSourceSizesha256
p12-mainnet-mined-l26588352P12mainnet passphrasemined from history887,884 B039ba91a4dfd…

What a correct reader returns

A correct reader findsValueBacked by
The claimed offer's seller is a raw ed25519 key in a V0 claim atom.ad0713a07a84a069367932edf2b6155c69aed69446e564168ab8fcd78d728785snapshotcorewalker
The claimed offer is offer 127478113.127478113snapshotcorewalker
The same seller, as the offer's ledger entry names it, is the G address of that key.some change where 2 fields matchsnapshotcorewalker
The seller's account entry carries liabilities in extension v1 with no v2 extension.some change where 1 fields matchsnapshot

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 walker

Entry id backfill.claim-atom-v0-p12 · compiled from catalog/backfill.claim-atom-v0-p12.json · entry.json

On this page