02Sheet 02.03.084 · Entries

A pool deposit: transfer events to an L… address

CHANGE_TRUST to pool shares creates the liquidity-pool entry (not the deposit, which only updates it), and LIQUIDITY_POOL_DEPOSIT emits transfer events whose destination is the pool, rendered as an L… strkey (CAP-0067).

FIG. · Where it sits · inside LedgerCloseMetaCAP-0038 · CAP-0067 · H-C8 · H-A5
pool entry created by ChangeTrust to pool shares; LiquidityPoolDeposit only updates it
liquidity-pool address L… in a CAP-0067 event topic

The shape

CHANGE_TRUST to pool shares creates the liquidity-pool entry (not the deposit, which only updates it), and LIQUIDITY_POOL_DEPOSIT emits transfer events whose destination is the pool, rendered as an L… strkey (CAP-0067). Readers that create pools on deposit, or expect G or C addresses in event topics, get both wrong.

Variants

VariantProtocolNetworkSourceSizesha256
p30-mainnet-generatedP30mainnet passphrasegenerated by stellar-core v30.0.0
change order varies: 7 orderings in 20 runs
4,120 B52a9b11a883e…
p30-testnet-generatedP30testnet passphrasegenerated by stellar-core v30.0.04,120 B886eea358d19…

What a correct reader returns

A correct reader findsValueBacked by
mm transfers XLM to the pool, whose address is an L… strkey.some change where 2 fields matchsnapshotcorewalker
Operation 0 (CHANGE_TRUST) creates the pool entry, keyed by the same L… ID.some change where 1 fields matchsnapshotcorewalker
Operation 1 (the deposit) only updates it.some change where 1 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 pool.deposit-l-address-event · compiled from catalog/pool.deposit-l-address-event.json · entry.json

On this page