adu-crypto
adu-crypto
@calvinaco should we clarify that the `extraData` should be encoded outside of the evm call and passed into the contract call as the input, otherwise if the contract encoded the...
> ## Remove tx_index.db > Currently we rely on tx indexer to query tx by eth tx hash, an alternative solution is to store that index in a standalone kv...
hold txs in mempool after we propose the block could be done by ABCI++ via `PrepareProposal`: > If the Application considers that tx should not be proposed in this block,...
> As a workaround you could implement a stub Consume function (using Do function) and then check your function is called that way. this worked for me. we just need...
> this will need some sort of migration to catch all previous data. yes, exactly.
@alexanderbez should we migrate vesting module instead of `x/auth` as now vesting module has its own store and become a standalone module?
> Is this something that can easily be done or does this require a lot of additional plumbing? I would say I'm reading the docs and migration example of the...
> This doesn't do what the title says it does. It is not keeping track of total locked coins By exposing `IterateVestingAccounts`, the other modules should be able to calculate...
okay, I shall refactor to do what the title suggests
are we planning on switching to the JMT and refactoring the whole storage?