History

Amaury b2b29d4909 chore: Audit crypto folder (#11932 ) ## Description ref: #11362 I did NOT review the following folders, as they contain cryptography which I don't think I'm competent enough to give a useful review: - [ ] `crypto/xsalsa20symmetric` (new in v046, ported from TM i think) - [ ] `crypto/keys/secp256k1` (some new stuff in v046 too) Also performed some manual tests as part of #11939: - [x] Create keys on v0.45, make sure they still work in v0.46 https://github.com/cosmos/cosmos-sdk/issues/11939#issuecomment-1124881492 - [x] Create new keys in v0.46 https://github.com/cosmos/cosmos-sdk/issues/11939#issuecomment-1124881492 - [x] `--multisig` flag works with an address that's not in the keyring (see [repro](https://github.com/cosmos/cosmos-sdk/issues/9553)) --- ### Author Checklist All items are required. Please add a note to the item if the item is not applicable and please add links to any relevant follow up issues. I have... - [ ] included the correct [type prefix](https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.json) in the PR title - [ ] added `!` to the type prefix if API or client breaking change - [ ] targeted the correct branch (see [PR Targeting](https://github.com/cosmos/cosmos-sdk/blob/main/CONTRIBUTING.md#pr-targeting)) - [ ] provided a link to the relevant issue or specification - [ ] followed the guidelines for [building modules](https://github.com/cosmos/cosmos-sdk/blob/main/docs/building-modules) - [ ] included the necessary unit and integration [tests](https://github.com/cosmos/cosmos-sdk/blob/main/CONTRIBUTING.md#testing) - [ ] added a changelog entry to `CHANGELOG.md` - [ ] included comments for [documenting Go code](https://blog.golang.org/godoc) - [ ] updated the relevant documentation or specification - [ ] reviewed "Files changed" and left comments if necessary - [ ] confirmed all CI checks have passed ### Reviewers Checklist All items are required. Please add a note if the item is not applicable and please add your handle next to the items reviewed if you only reviewed selected items. I have... - [ ] confirmed the correct [type prefix](https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.json) in the PR title - [ ] confirmed `!` in the type prefix if API or client breaking change - [ ] confirmed all author checklist items have been addressed - [ ] reviewed state machine logic - [ ] reviewed API design and naming - [ ] reviewed documentation is accurate - [ ] reviewed tests and test coverage - [ ] manually tested (if applicable)		2022-05-15 13:02:53 +00:00
..
cosmos	chore: Audit crypto folder (#11932 )	2022-05-15 13:02:53 +00:00
tendermint	feat: Add `MsgSoftwareUpgrade` and `MsgCancelUpgrade` (for new msgs-based gov proposals) (#11116 )	2022-03-03 16:45:02 +01:00
README.md	docs: Code blocks in SDK docs are broken (#11189 )	2022-02-14 23:39:35 +01:00
buf.gen.gogo.yaml	feat: full api module building alongside gogo proto files with buf schema registry support (#10669 )	2022-01-06 14:57:55 -05:00
buf.gen.pulsar.yaml	chore: api sub-module vanity URL (#11941 )	2022-05-12 10:19:04 +00:00
buf.lock	feat: full api module building alongside gogo proto files with buf schema registry support (#10669 )	2022-01-06 14:57:55 -05:00
buf.md	docs: Improve markdownlint configuration (#11104 )	2022-02-10 12:07:01 +00:00
buf.yaml	feat: full api module building alongside gogo proto files with buf schema registry support (#10669 )	2022-01-06 14:57:55 -05:00

README.md

Maintaining Cosmos SDK Proto Files

All of the Cosmos SDK proto files are defined here. This folder should be synced regularly with buf.build/cosmos/cosmos-sdk regularly by a maintainer by running buf push in this folder.

User facing documentation should not be placed here but instead goes in buf.md and in each protobuf package following the guidelines in https://docs.buf.build/bsr/documentation.