With diagnostic events on, every contract event appears twice
Galexie's default flags include ENABLE_SOROBAN_DIAGNOSTIC_EVENTS.
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
| Variant | Protocol | Network | Source | Size | sha256 |
|---|---|---|---|---|---|
p30-mainnet-generated | P30 | mainnet passphrase | generated by stellar-core v30.0.0 | 2,972 B | 744986731d97… |
p30-mainnet-generated-galexie | P30 | mainnet passphrase | generated by stellar-core v30.0.0 change order varies: 2 orderings in 2 runs | 5,080 B | 8b0cf4eb7738… |
What a correct reader returns
| A correct reader finds | Value | Backed by |
|---|---|---|
| With Galexie flags, the diagnostic events include the contract event with topic put. p30-mainnet-generated-galexie | some change where 2 fields match | snapshotcorewalker |
| and a core_metrics invoke_time_nsecs event. p30-mainnet-generated-galexie | some change where 1 fields match | snapshotcorewalker |
| With base flags there are no diagnostic events. p30-mainnet-generated | length 0 | snapshot |
Sightings
stellar-etl#452Check 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 walkerEntry id profiles.galexie-diagnostic-double-emission · compiled from catalog/profiles.galexie-diagnostic-double-emission.json · entry.json
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.
Mined ledgers
37 real mainnet and testnet ledgers from the public data lake, for shapes a standalone generator cannot produce, or that are worth having as real network bytes: eviction at the cap, settings votes, a mainnet freeze, protocol-12 V0 envelopes.