Sanaz Taheri

I would also consider including the following metrics: - Transaction throughput measured in bytes/second, calculated as block size/block time. This metric would allow us to compare the rate of traffic...

> mind elaborating on the data we need here? Do you think it would be possible to get that data by tracking at the mempool or even after the blocks...

While working on this task, it became evident that additional metrics need to be tracked within txsim. Consequently, adopting a core instrumentation strategy would offer greater viability and sustainability. With...

Need to wait on #2429

Per conversation with @evan-forbes, I'd like to provide more detail on the attack scenario that prompted the opening of this issue: Malicious consensus nodes could produce and commit a block,...

It might be already covered by the existing bad encoding fraud proof https://github.com/celestiaorg/celestia-node/blob/main/share/eds/byzantine/bad_encoding.go, we need to check. Update: The current bad encoding fraud proof logic does not capture this issue,...

During my call with @evan-forbes, we discussed the potential benefits of enabling light nodes to identify out-of-order leaves when sampling and verifying their inclusion proof, in addition to the full...

Thanks for opening this issue! Do we want to proceed with this [PR](https://github.com/celestiaorg/nmt/pull/220) or do we want to wait for this fix before merging https://github.com/celestiaorg/nmt/pull/220?

> When we push data to the tree, we are using prefixed data, but when we verify proofs, we are using non-prefixed data. Whatever the API ends up being, we...

Is the requested modification in this issue still required?