Stefan Thomas
Stefan Thomas
Fending off that code rot!
Five Bells Ledger should ship with a dataset like this: https://gist.github.com/Fluidbyte/2973986 That way, users can configure a currency by ISO code and have symbol etc. chosen automatically.
Currently, subscribing to all transfers is done using the `/accounts/*/transfers/` endpoint. A better and more logical URL would be `/transfers/`.
We are about to remove reliable notification support via REST hooks. Do we need a new facility (e.g. using MQTT/[mosca](https://github.com/mcollina/mosca)) to replace it?
Currently, we use exponential backoff. But jittering backoff [may be better](http://www.awsarchitectureblog.com/2015/03/backoff.html). It's unlikely to matter much for our use case, but it's also a pretty simple change.
When the ledger sends out notifications about transfers, it would be useful to include the old and new balances, similar to "metadata" in rippled. Let's use this issue to discuss...
### Description When converting between different kinds of byte arrays like Buffer and Uint8Array, it is very easy to forget offset and length. Consider this example: ``` ts function makeUint8Array()...
When initially selecting a currency, we now have a huge list and it takes some scrolling to find the currency you want. Given that 99% of our users are going...
@my8bird posted the following test error: ``` bash ✖ 1 of 41 tests failed: 1) Iterator db.forRange() should iterate until limit key: actual expected 107 AssertionError: "107" == "" at...
Right now it's impossible to tell what document you're reading unless you scroll to the top:  On mobile, the menu is placed above the content: ![screenshot...