Callum Waters

Results 110 issues of Callum Waters

### Summary Implement a standard interface for clients to query gas and gas price from a trusted endpoint of their choosing. ### Problem Definition All clients wishing to submit transactions...

WS: TxUX🐧

### Summary This issue presents an alternative to the current replay protection mechanism: nonces. Nonces should remain but become an optional feature for those wanting serialisability of their transactions. Instead...

enhancement
proposal
WS: BestTxs
ice-box

### Implementation ideas This is a tracking issue for the celestia-node component of the gas estimator interface as outlined in [CIP-18](https://github.com/celestiaorg/CIPs/blob/main/cips/cip-18.md). Specifically, this constitutes implementing the client side, which will...

area:state
area:core_and_app
external
v0.15.0

NMT is built on top of some existing data structure. It is used to prove the absence or presence of some subset of data. In the case of Celestia, it...

As a celestia-oriented optimization, the following padding shares with - TxNamespace - PFBNamespace - TailPaddingNamespace Could have the sha256 precomputed. In the `HashLeaf` method, we could simply identify if it...

enhancement

This CIP is in reference to this issue: https://github.com/celestiaorg/celestia-app/issues/3316 Note that there is a diagram so when changing the name of the file and folders, make sure to change the...

## Summary Inclusion proofs aren't yet working as indicated in https://github.com/celestiaorg/celestia-core/issues/918. Some of the tests and code in the Cosmos SDK rely on this feature and have therefore been disabled...

## Feature Request When blocks are full, inclusion is decided based on a first price auction of the gas price of the transactions. Currently it's difficult to get information to...

C:documentation

This is meant to show a quick way for implementing a dynamic timeout commit aimed at achieving more consistent block times. The approach is to model how the size of...

### Summary Celestia currently has hardcoded limits to the block size (in bytes) and square size (in shares). These guardrails are in place to prevent on chain governance from picking...

needs:triage