02Sheet 02.03.090 · Entries

A claimable balance created by operation 1 with a muxed operation source, inside a fee bump

The balance ID is the hash of (inner source base account, inner sequence number, operation index 1); the muxed operation source and the fee bump must not change it.

FIG. · Where it sits · inside LedgerCloseMetaCAP-0023 · CAP-0015 · CAP-0027 · H-A10
ClaimableBalanceID from inner source + seq + op index 1, muxed op source, fee bump

The shape

The balance ID is the hash of (inner source base account, inner sequence number, operation index 1); the muxed operation source and the fee bump must not change it. Readers that derive it from the fee source, the M address or index 0 get another ID.

Variants

VariantProtocolNetworkSourceSizesha256
p30-mainnet-generatedP30mainnet passphrasegenerated by stellar-core v30.0.05,268 Bb0e89827d9c1…
p30-testnet-generatedP30testnet passphrasegenerated by stellar-core v30.0.05,268 B7a71c27cdc22…

What a correct reader returns

A correct reader findsValueBacked by
The result returns the ID derived from alice, her sequence and index 1.BAAANG6COYO3EGDOKHVFLH4J7DBXNOQ73V45ZEGHS56ELW7KYCF4IVW6NEconstructionsnapshotcorewalker
Operation 1's source is alice muxed with ID 9.MBQXLZZTGUKRRRYDQNQOMKWL7DN3PGIBPNBIHDIO5KFPPPIFAHHQIAAAAAAAAAAABG4BUconstructionsnapshotcorewalker

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 claimable-balance.id-op-index-1-muxed-source-in-fee-bump · compiled from catalog/claimable-balance.id-op-index-1-muxed-source-in-fee-bump.json · entry.json

On this page