Vlad

Thanks for pointing that out! You're right that the first Bridge node will need to request from a consensus node. Maybe we can add a trusted_height configuration, so we can...

I see this as a configuration issue. We can determine if trusted_hash is the genesis block by comparing it with a hardcoded constant. If it matches, we can request block...

It does not seem like proper blob proofs would be enough. We need to make all proofs to be to dataroot. But good news are it is wip: - https://github.com/celestiaorg/celestia-node/issues/4308...

@damiannolan The issue I linked has more ambitious goal. New API will have only dataroot proofs and you no longer need would need to know about `DAH` or `row roots`...

Since otel bump in https://github.com/celestiaorg/celestia-node/pull/3068 custom buckets are now possible. We need to revise our histogram definitions and set up sensible buckets values.

There are multiple components that needs to be monitored to get an idea of rps / load: - [x] shrex/eds server - metric:`shrex_eds_server_total_responses` - [x] shrex/nd server - metric:`shrex_nd_server_total_responses` -...

Sometimes, a node fails to discover any peers on startup. Without discovered peers, the node is unable to perform most of its P2P logic. The downside of a longer cooldown...

Do we have numbers/metrics data that shows how often instabilities happen? We are going to migrate away from bitswap in near future and unless instability affecting functionality or user experience,...

Should be solved by https://github.com/celestiaorg/celestia-node/issues/4218

I would like to clarify that propagating retrieval results, indicating which namespaces were retrieved successfully and which resulted in errors, is very messy with the existing multi-namespace API. Handling such...