02Sheet 02.03.202 · Entries

With diagnostic events on, every contract event appears twice

Galexie's default flags include ENABLE_SOROBAN_DIAGNOSTIC_EVENTS.

FIG. · Where it sits · inside LedgerCloseMetaCAP-0067 · H-E3 · H-F9
contract event repeated in diagnostic_events
diagnostic events only under the galexie profile

The shape

Galexie's default flags include ENABLE_SOROBAN_DIAGNOSTIC_EVENTS. The put's contract event appears in the operation's events and again, type contract, among the diagnostic events; a core_metrics event invoke_time_nsecs carries wall-clock time, so the bytes differ between nodes. stellar-etl#452.

Variants

VariantProtocolNetworkSourceSizesha256
p30-mainnet-generatedP30mainnet passphrasegenerated by stellar-core v30.0.02,972 B744986731d97…
p30-mainnet-generated-galexieP30mainnet passphrasegenerated by stellar-core v30.0.0
change order varies: 2 orderings in 2 runs
5,080 B8b0cf4eb7738…

What a correct reader returns

A correct reader findsValueBacked by
With Galexie flags, the diagnostic events include the contract event with topic put.
p30-mainnet-generated-galexie
some change where 2 fields matchsnapshotcorewalker
and a core_metrics invoke_time_nsecs event.
p30-mainnet-generated-galexie
some change where 1 fields matchsnapshotcorewalker
With base flags there are no diagnostic events.
p30-mainnet-generated
length 0snapshot

Sightings

stellar-etl#452

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.galexie-diagnostic-double-emission · compiled from catalog/profiles.galexie-diagnostic-double-emission.json · entry.json

On this page