Ed Hennis

See also #4730

> Related, it's misleading that the `feature` command shows retired amendments as `"enabled": false` even though the functionality associated with them is _always_ enabled. Previous ticket: [#4014](https://github.com/XRPLF/rippled/issues/4014). Without adding a...

> According to XRPL protocol rules, an account should be removed from the ledger once its balance reaches 0, provided there are no additional dependencies (trust lines, escrows, AMM positions,...

> An account can only have a lower balance than its reserve if it burns all that XRP. That's a rare enough occurrence. One of the design philosophies of the...

Quick thoughts: 1. When a peer is dropped, it's resource charge is still tracked and decreases over time. 2. If a peer reconnects before the charge gets below an acceptable...

> cat /etc/opt/ripple/rippled.cfg | grep dropped That's the config file, not the log. 😊

> dope lol... fixed command, but still very little across the 3 instances. > (When sharing logs and such, please copy and paste them as text. They're much easier for...

I formatted the JSON blocks to be a little more readable. This can probably most easily be accomplished by reordering the code in the handler function to initialize `transactions` _after_...

> Why is the synchronization of previous XRP blocks so slow? I’ve been running it for 4 days, and it has only synced data from the past month. * [Details...

Data point for comparison: ``` [...] "build_version": "2.4.0+72e076b6941446188d40fc917f8738b010c10600.DEBUG", "complete_ledgers": "95128227-95146722", [...] "initial_sync_duration_us": "657362241", "io_latency_ms": 1, "jq_trans_overflow": "0", [...] "load_factor": 1, "node_size": "huge", "peer_disconnects": "1", "peer_disconnects_resources": "0", "peers": 21, [...] "server_state":...