02Sheet 02.03.079 · Entries

Four trustlines from three operation sources in one transaction, one alphanum-12 at the int64-max limit

One transaction, three operation sources (alice, bob, mm), alphanum-4 and alphanum-12 assets, and a trustline limit of 922337203685.4775807 (int64 max stroops).

FIG. · Where it sits · inside LedgerCloseMetapre-cap · H-C5 · H-B9 · H-B3
one transaction with operations from three different sources
CHANGE_TRUST to an alphanumeric-12 asset
trustline limit at int64 max

The shape

One transaction, three operation sources (alice, bob, mm), alphanum-4 and alphanum-12 assets, and a trustline limit of 922337203685.4775807 (int64 max stroops). Readers that attribute every operation to the transaction source, or parse the limit as a float, get it wrong.

Variants

VariantProtocolNetworkSourceSizesha256
p30-mainnet-generatedP30mainnet passphrasegenerated by stellar-core v30.0.04,684 B95f6d76bd916…
p30-testnet-generatedP30testnet passphrasegenerated by stellar-core v30.0.04,684 Bfadfc19e878c…

What a correct reader returns

A correct reader findsValueBacked by
Operation 1 has source bob.GCDNGZ7NJFNBWBP7DXYQKJRBG2VAIR5DCCCLUDBZW5B3VGUFKDG5ALZFconstructionsnapshotcorewalker
Operation 3 trusts the alphanum-12 code XPFLONGCODE1 with limit 9223372036854775807 stroops.9223372036854775807constructionsnapshotcorewalker
A trustline for XPFLONGCODE1 is created for mm.some change where 2 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 trustline.multi-source-alphanum12-max-limit · compiled from catalog/trustline.multi-source-alphanum12-max-limit.json · entry.json

On this page