02Sheet 02.03.022 · Entries

A muxed ScAddress as a contract-data key traps

CAP-0067: a muxed ScAddress may not appear in a contract-data key.

FIG. · Where it sits · inside LedgerCloseMetaCAP-0067 · CAP-0046 · H-A11 · H-C6
muxed ScAddress inside a contract-data key: trapped
Soroban failure: trapped

The shape

CAP-0067: a muxed ScAddress may not appear in a contract-data key. The address is valid in the arguments and even in the footprint's LedgerKey, but the put traps.

Variants

VariantProtocolNetworkSourceSizesha256
p30-mainnet-generatedP30mainnet passphrasegenerated by stellar-core v30.0.02,376 Bd9ed4d3aad1f…
p28-mainnet-generatedP28mainnet passphrasegenerated by stellar-core v30.0.02,368 B348b1dab127c…
p30-testnet-generatedP30testnet passphrasegenerated by stellar-core v30.0.02,376 B42b8c11c5c41…
p28-testnet-generatedP28testnet passphrasegenerated by stellar-core v30.0.02,368 Bf1a9be02db27…
p30-mainnet-generated-galexieP30mainnet passphrasegenerated by stellar-core v30.0.0
change order varies: 2 orderings in 2 runs
4,820 B1dc6b9099964…

What a correct reader returns

A correct reader findsValueBacked by
The call fails: the host traps.trappedconstructionsnapshotcorewalker
The footprint's read-write key holds the muxed address M(bob, 42).MCDNGZ7NJFNBWBP7DXYQKJRBG2VAIR5DCCCLUDBZW5B3VGUFKDG5AAAAAAAAAAAAFITJAconstructionsnapshotcorewalker
With diagnostic events the host says why: storage error invalid_input, "muxed addresses should not be used in the storage keys".
p30-mainnet-generated-galexie
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 scval.muxed-address-key-trapped · compiled from catalog/scval.muxed-address-key-trapped.json · entry.json

On this page