02Sheet 02.03.201 · Entries

The same classic payment under three node-flag profiles

The same ledger as written by a node with base flags, with Galexie's six flags, and with none.

FIG. · Where it sits · inside LedgerCloseMetaCAP-0067 · H-F9 · H-F7
same ledger, three emitter-flag profiles
LedgerCloseMetaExt v1 under base and galexie flags, v0 under bare

The shape

The same ledger as written by a node with base flags, with Galexie's six flags, and with none. The ledger is identical; the metadata is not: with no flags the classic transfer event and the fee events are absent and LedgerCloseMeta has no ext v1.

Variants

VariantProtocolNetworkSourceSizesha256
p30-mainnet-generatedP30mainnet passphrasegenerated by stellar-core v30.0.02,180 B7436cc49fd42…
p30-mainnet-generated-galexieP30mainnet passphrasegenerated by stellar-core v30.0.02,180 B7436cc49fd42…
p30-mainnet-generated-bareP30mainnet passphrasegenerated by stellar-core v30.0.01,844 Bb77b8058d2c1…

What a correct reader returns

A correct reader findsValueBacked by
With base or Galexie flags the payment emits one transfer event.
p30-mainnet-generated
length 1snapshot
With base or Galexie flags the payment emits one transfer event.
p30-mainnet-generated-galexie
length 1snapshot
With no flags it emits none.
p30-mainnet-generated-bare
length 0snapshot
With no flags LedgerCloseMeta ext is v0.
p30-mainnet-generated-bare
v0snapshot
The ledger header hash is identical under all three profiles: the same ledger.177573c752d0bc49ca452cc142a3ea39d7c730cee78987d67c89b58992d715f8snapshotcorewalker

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 profiles.classic-payment-meta-by-flags · compiled from catalog/profiles.classic-payment-meta-by-flags.json · entry.json

On this page