* switch iavl store to use ics proof
* fix proofs to return for correct height
* appease linter
* Register commitment op correctly
* Make CommitmentOp generic over all ics23 specs (#6331)
* Make the CommitmentOp generic over all ics23 ProofSpecs, using Type to distinguish
* Register SimpleMerkle ics23 proof op as well
* Addressed linter issues
* move commitment proof to types
* Apply suggestions from code review
Co-authored-by: colin axner <25233464+colin-axner@users.noreply.github.com>
* address review comments:
* Apply suggestions from code review
Co-authored-by: Federico Kunze <31522760+fedekunze@users.noreply.github.com>
* allow proofs against empty store
* address review comments
* Update store/types/proof.go
Co-authored-by: Alexander Bezobchuk <alexanderbez@users.noreply.github.com>
* add changelog
Co-authored-by: Ethan Frey <ethanfrey@users.noreply.github.com>
Co-authored-by: colin axner <25233464+colin-axner@users.noreply.github.com>
Co-authored-by: Federico Kunze <31522760+fedekunze@users.noreply.github.com>
Co-authored-by: Alexander Bezobchuk <alexanderbez@users.noreply.github.com>
Co-authored-by: Marko <marbar3778@yahoo.com>
The command processes list of transactions from file
(one StdTx each line), generate signed transactions
or signatures and print their JSON encoding, delimited
by '\n'. As the signatures are generated, the command
increments the sequence number automatically.
Author: @jgimeno
Reviewed-by: @alessio
* fix#6287 sending multiple transactions from an account make nonce sequence stuck
* add change log
* fix ante unit test after #6287 fix
* Update x/auth/ante/sigverify.go
Co-authored-by: Alessio Treglia <alessio@tendermint.com>
Co-authored-by: Alessio Treglia <quadrispro@ubuntu.com>
Co-authored-by: Alexander Bezobchuk <alexanderbez@users.noreply.github.com>
* baseapp: append AnteHandler events to tx result
* changelog
* baseapp tests
* fix test
* update changelog
* update log
* move event out from conditional
* minor update
* fix panic
* add switch case
* remove result on error
* change conditional
* check for event len
* update tests
* add string method to gas meter
* update changelog
* Update store/types/gas.go
Co-authored-by: Alexander Bezobchuk <alexanderbez@users.noreply.github.com>
Co-authored-by: Alexander Bezobchuk <alexanderbez@users.noreply.github.com>
--validate-signatures should not be a flag of the sign command
as the operation performed (transaction signatures verification)
is logically distinct.
cli_test is and has always been an horrible name for package
directory as it's very much Go anti-idiomatic - _test is the
suffix used by test packages, not directories. Plus, CLI test
cases can and should live alongside other testcases that don't
require binaries to be built beforehand. Thus:
x/module/client/cli_test/*.go -> x/module/client/cli/
Test files that require sim{cli,d} shall be tagged with // +build cli_test
With regard to cli test auxiliary functions, they should live in:
x/module/client/testutil/
Co-authored-by: Alexander Bezobchuk <alexanderbez@users.noreply.github.com>
* server: remove deprecated UpgradeOldPrivValFile
OldFilePV was deprecated in Tendermint Core v0.28 and will be removed in
upcoming v0.34.5 release.
* remove imports
* Add changelog entries
Co-authored-by: Aleksandr Bezobchuk <aleks.bezobchuk@gmail.com>
Co-authored-by: Alessio Treglia <alessio@tendermint.com>
* Use correct API and add TODO
* Allow unjail without signing info
* Add unit test
* Update godoc
* Add changelog entries
* Fix TestUndelegateSelfDelegationBelowMinSelfDelegation
* Fix delegation tests
* Revert API call
* x/evidence: simulations
* update app
* evidence store decoder
* add evidence to sim import export
* fix test
* prevent zero values on randomized genesis
* return empty evidences for genesis state
* address comments from review
* temporal commit
* add random consensus params
* make format
* make random pass
* remove comment
* revert change
* update ub key types
* extract Evidence params from state
* extract the random parameters from state
* clean the code
* update imports!
* mispelled back
* mispelled back
* add misspelled command
* update changelog
* remove useless linter to avoid misspell
* remove function
* use tendermint constants
Co-authored-by: Alexander Bezobchuk <alexanderbez@users.noreply.github.com>
github.com/spf13/viper's recent releases introduced a semantic
change in some public API such as viper.IsSet(), which have
broken some of our flags checks. Instead of checking whether
users have changed a flag's default value we should rely on such
defaults and adjust runtime behaviour accordingly. In order to do
so, it's important that we pick sane defaults for all our flags.
The --pruning flag and configuration option now allow for a
fake custom strategy. When users elect custom, then the
pruning-{keep,snapshot}-every options are interpreted and
parsed; else they're ignored.
Zero is pruning-{keep,snapshot}-every default value. When
users choose to set a custom pruning strategy they are
signalling that they want more fine-grainted control, therefore
it's legitimate to expect them to know what they are doing and
enter valid values for both options.
Ref #5964