Callum Waters
Callum Waters
Closing this as no longer relevant
I guess this isn't a problem if you use the Tendermint RPC to call `BroadcastTx`? I think the culprit is here: https://github.com/celestiaorg/cosmos-sdk/blob/0aef7ba8d215a3978de8c298dc40d9fa65041695/client/broadcast.go#L111 I'm not sure why you would want to...
> It's not clear to me what the benefits are from doing this. It seems like a small performance improvement that we should only pursue if we have data indicating...
Would be interested to see how much time the application is also handling `CheckTx` requests in a height
Yeah I suggested v8 without looking into much detail around the decision but purely basing it on the fact that the later the version, the longer we have before it's...
This is to be expected but not desired. When "fast syncing" a different component is responsible for executing the blocks and thus `consensus` actually doesn't know what the current height...
What I thought happened was if you grant something to an account that doesn't exist you would create that account such that the account could sign a transaction and part...
If you look here we should be creating the account: https://github.com/cosmos/cosmos-sdk/blob/7799bba7bc889288607576aa11655b5fc31a2da9/x/feegrant/keeper/keeper.go#L43-L48
> I don't quite follow how a TTL of 10 blocks results in the tx never being executed again. Does this mean the tx can't be executed after the 10...
Yeah, the model for estimating works on the assumption that there are no added options to the transaction i.e. it's just a vanialla PFB