Nguyen Nhu Viet
Nguyen Nhu Viet
Ref: https://github.com/celestiaorg/celestia-node/issues/923
Grooming 12/07/2022: - Changing the issue from Post-Mainnet to Mainnet - it's still a low priority one - we can defer it again to Post-Mainnet if we don't have the...
Relies on share-exchange protocol Reasonable timeout should be defined properly after we get the telemetry data to analyse and decide Still relevant post-mainnet status of 12/07/2022
Can be the same root cause Ref: https://github.com/celestiaorg/celestia-node/issues/985
Grooming 12/07/2022: - if we are fine with the current stack, we need to have this implemented before Incentivized Testnet
Grooming 20/09: Let's async do a deep dive for this and later on have a call to finalise our decision cc: @Wondertan @distractedm1nd @renaynay
Thanks for the reply @laurentsenta 👍 Let's say I have 90 IPs assigned to 90 instances. And 90 instances are divided into 3 groups(thanks to composition) -> A, B, C...
It boils down to the misunderstanding of information that is presented in the docs. Here is what you can try to do: 1. If you switch the docs to master...
> These are the default values. Are these values causing issues @Bidon15 ? For testing purposes, to get 4MB blocks, you need 4 1mb txs to get it. I wonder...
> If I understand correctly, you're proposing increasing max_tx_bytes from the default 1 MiB to 4 MiB so that a block can be filled with just one transaction. Yes >...