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).
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
| Variant | Protocol | Network | Source | Size | sha256 |
|---|---|---|---|---|---|
p30-mainnet-generated | P30 | mainnet passphrase | generated by stellar-core v30.0.0 change order varies: 7 orderings in 20 runs | 4,120 B | 52a9b11a883e… |
p30-testnet-generated | P30 | testnet passphrase | generated by stellar-core v30.0.0 | 4,120 B | 886eea358d19… |
What a correct reader returns
| A correct reader finds | Value | Backed by |
|---|---|---|
| mm transfers XLM to the pool, whose address is an L… strkey. | some change where 2 fields match | snapshotcorewalker |
| Operation 0 (CHANGE_TRUST) creates the pool entry, keyed by the same L… ID. | some change where 1 fields match | snapshotcorewalker |
| Operation 1 (the deposit) only updates it. | some change where 1 fields match | snapshotcorewalker |
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 walkerEntry id pool.deposit-l-address-event · compiled from catalog/pool.deposit-l-address-event.json · entry.json
MANAGE_SELL_OFFER updates an existing offer
An offer ID in the operation updates that offer in place: the result says updated.
A path payment filled by a liquidity pool, not the order book
The claim atom is CLAIM_ATOM_TYPE_LIQUIDITY_POOL: readers that expect order-book atoms with a seller and offer ID fail.