02Sheet 02.03.095 · Entries

A sponsorship sandwich: entries created under another account's reserve

BEGIN_SPONSORING / manage_data and change_trust by eve / END_SPONSORING: the data entry and trustline are eve's, their reserve is sponsor's.

FIG. · Where it sits · inside LedgerCloseMetaCAP-0033 · H-C3
BeginSponsoringFutureReserves … EndSponsoringFutureReserves around two entries

The shape

BEGIN_SPONSORING / manage_data and change_trust by eve / END_SPONSORING: the data entry and trustline are eve's, their reserve is sponsor's.

Variants

VariantProtocolNetworkSourceSizesha256
p30-mainnet-generatedP30mainnet passphrasegenerated by stellar-core v30.0.0
change order varies: 3 orderings in 20 runs
3,216 Bcd573c9fc562…
p30-testnet-generatedP30testnet passphrasegenerated by stellar-core v30.0.0
change order varies: 2 orderings in 2 runs
3,216 B942e4cab42a8…

What a correct reader returns

A correct reader findsValueBacked by
Operation 1 creates eve's data entry "sponsored".some change where 2 fields matchsnapshotcorewalker
The created data entry names sponsor as its sponsor.some change where 1 fields matchsnapshotcorewalker

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 sponsorship.sandwich · compiled from catalog/sponsorship.sandwich.json · entry.json

On this page