Paul Bellamy

To be fair, the "right" solution here is to also process liquidity pool claim atoms for strict receives in reverse order (like core does), which would keep the pool reserves...

Blocking https://github.com/stellar/go/pull/4178

@sydneynotthecity suggests we prioritize the fields which cannot be looked up elsewhere. That seems like path ordering is the least important (can be looked up from the operation). But! the...

Unfortunately, fixing this probably implies a full reingestion, since it will change the generated effects for strict-receive txns.

Goal for this stage is something we could use for the end-to-end example dapp https://github.com/stellar/jump-cannon-deliverables/issues/18 for now.

XDR Updates are in https://github.com/stellar/js-stellar-base/pull/538

These are done in the `soroban` branches of `js-stellar-base` and `js-stellar-sdk`. Maybe that is good enough for now? Will the npm release process even let us do better than that?...

This is low priority, given https://github.com/stellar/go/pull/4390

There were a couple of missed points in the initial version of the linked docs sent out.\n\nFirst, there is also a /liquidity_pools/:pool_id/trades api endpoint for retrieving the trades which have...

Related js sdk: https://github.com/stellar/js-stellar-sdk/issues/787