Callum Waters
Callum Waters
### Summary To provide bridging for ZK based rollups, we need to prototype a snark based ZK verifier that complies with the [IBC client interface](https://github.com/cosmos/ibc-go/blob/2ddd5cf69e6aac9488b9c27814d4d1e4d19f39b9/modules/core/exported/client.go#L43) This should ideally use the...
### Summary As we look to increase block size, we'd like to make sure that there's no path for transactions that are computationally heavy from significantly affecting the block production...
### Summary We want to prevent situations that could lead to excessive computation which could also slow down the network (This could happen if all the transactions in an 8MB...
### Summary The tools we provide users to assist in tx submission has come a long way and we're starting to see a more production grade system that can be...
why does the default here not match the default used on mainnet? IMO only one test (max square size test) should override this value and the rest of our tests...
### Summary The most often use case of the `txsim` is to simulate transaction load to a network. ### Problem Definition This is a bit cumbersome and repetitive and could...
Currently we just have this cip: https://github.com/celestiaorg/CIPs/blob/main/cips/cip-21.md But it makes sense to have the share versions clearly documented. I will need to think about where the best place for that...
Description Tested this using the single-node.sh script in celestia-app. Note that the moniker should stay as it's set in the init and sometimes used by the CLI Closes: https://github.com/celestiaorg/celestia-core/issues/1518
Ref: https://github.com/celestiaorg/celestia-app/issues/3768 This cleans up the LRUTxCache which had two implementations. It exposes the IsRejectedTx method which the RPC server uses to pass on to callers of `TxStatus`. This wil...
Ref: https://github.com/celestiaorg/celestia-core/issues/1532 As the prototype shows more promising results and the design becomes almost finalized, we should then take the prototype and write up a comprehensive specification of the protocol...