Bartek Nowotarski

Do you still experience this issue? There were some ingestion delays in the order book graph that `/paths` is using to find offers.

This is fine except I think `js-xdr` should stay in it's own repo. It can be useful in other projects and committers shouldn't have to pull all Stellar-related code. However,...

https://github.com/stellar/go/pull/4518 clears orphans from `history_claimable_balances` and `history_liquidity_pools`. The last two remaining tables (`history_accounts` and `history_assets`) require indexes in other tables like `horizon_operation_participants`. @ire-and-curses agreed that new indexes should be add...

> So in this example, Horizon must be able to understand protocol 9 (and should fail to ingest) even though core can generate version 10 at some point (you may...

I'd vote for showing `fee_charged` in a separate panel or showing both values. The advantage of `max_fee` is that it shows you the bids so it's helpful for setting a...

I don't have any data for users behaviour so I'm not sure if this is used by users to set fees. However, `fee_charged` gives you very little information about the...

Do we need this? I'm 100% sure HDD are just to slow for Horizon.

Last week I run `ingest.CheckpointChangeReader` without anything else and it consumes 3.6GB at one of the latest checkpoints but database ingestion instances can consume even 8GB. We need to understand...

Can you share actual transaction that failed with `op_underfunded`?

Created two issues in Go SDK that should fix the behaviour described here: https://github.com/stellar/go/issues/2514 https://github.com/stellar/go/issues/2515.