Callum Waters
Callum Waters
Yeah it would have to be integrated with state sync. Maybe then we would need to add it to state.
What is this limit? You have 32 bytes for a hash and 10 blocks to maintain the cache for. With 10k transactions per block, it's 3.2mb of memory. That's not...
> I discovered one more follow-up while working on this. It doesn't look like ResetTally is actually invoked anywhere when I think it should be invoked [here](https://github.com/rootulp/celestia-app/blob/5d37f3e7dc1216613a4c34bf07c46543b7d76832/app/app.go#L698-L708). This makes sense...
> I thought about that edge case and I don't think it's possible because [these lines](https://github.com/celestiaorg/celestia-app/blob/1d73e334a48732ba2ef07caf064a7060175381f0/x/signal/keeper.go#L67-L72). In other words, when the app version is 1, the nodes that try to...
Yeah I had thought of time based estimates for when the transaction is estimated to be included which should capture a users preference to the urgency of the transaction
I think this can be closed now. Or at least can be tied with https://github.com/celestiaorg/celestia-app/issues/3305
@evan-forbes Is this something we want to punt till after mainnet?
Yeah that makes sense. I was under the impression that the reserved namespaces could also have padding (i.e. they were still part of the blob share commitment rules)
Is it possible to quickly identify a padding share without checking that all the raw bytes are 0?
> With Option 1, do we add new things to the square, or do we add it to the state? It's added to the square, not to state or to...