stellar

The asset ordering in the /trades endpoint is not deterministic. See, for example how responses are different for the same request ( /trades?cursor=133053547049738241-0&limit=10&order=asc ) in https://horizon.stellar.org/ vs https://horizon-stg-pubnet.stellar.org/.

The ordering sho

CAP 23 (as part of Stellar Protocol 14 and released with Horizon 1.9.0) allows creating and claiming Claimable Balances.

Those balances are queried and claimed using their ID which can be obtained:

1. Before submitting the transaction creating the claim. The Claim ID is internally just a Hash which can be inferred even before Core accepts the transaction. A helper function would be useful in

The option dinitIceSheetHeight in POISE allows negative arguments, which shouldn't be allowed. It'd be better to change it so that if the user inputs a negative value, it defaults to meters since the ice sheet height is positive definite.

stellar/laboratory#363 (comment):

state is a term of art in React, so I avoid using that as the name. It might have been clearer to name this prop 'signatureCheckState' or something.