horizon

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

display_bsod internally calls the map_framebuffer syscall to map the framebuffer, because we . were lazy and didn't want to duplicate code. However this syscall retrieves the current process to map it in its process memory.

When we're panicking during early boot, CURRENT_PROCESS is None and this panics in the panic handler.

We should instead do a second function that maps it in the k