02Sheet 02.03.019 · Entries

A map whose five keys collide on native conversion, used as a storage key

The colliding map (u32 1, i32 1, u64 1, string "1", symbol 1) is the contract-data KEY: it sits in the LedgerKey and the event topic.

FIG. · Where it sits · inside LedgerCloseMetaCAP-0046 · H-B2 · H-D10
colliding ScMap as a ContractData key and event topic
contract-data identity depends on the exact ScVal key

The shape

The colliding map (u32 1, i32 1, u64 1, string "1", symbol 1) is the contract-data KEY: it sits in the LedgerKey and the event topic. Converting it to a native object collapses the keys and changes the entry identity. js-stellar-sdk#1789.

Variants

VariantProtocolNetworkSourceSizesha256
p30-mainnet-generatedP30mainnet passphrasegenerated by stellar-core v30.0.02,940 Bbeeffd7903fd…
p28-mainnet-generatedP28mainnet passphrasegenerated by stellar-core v30.0.02,932 Bb127b3718d5a…
p30-testnet-generatedP30testnet passphrasegenerated by stellar-core v30.0.02,940 B2f79b2787a7d…
p28-testnet-generatedP28testnet passphrasegenerated by stellar-core v30.0.02,932 B006598dd5639…

What a correct reader returns

A correct reader findsValueBacked by
The created entry's key is a map with 5 entries.some change where 1 fields matchconstructionsnapshotcorewalker

Sightings

js-stellar-sdk#1789

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 scval.map.colliding-keys-as-key · compiled from catalog/scval.map.colliding-keys-as-key.json · entry.json

On this page