Alessio Treglia
764cfe33aa
Don't use pointer receivers for PubKeyMultisigThreshold (#3100)
* Don't use pointer receivers for PubKeyMultisigThreshold * test that showcases panic when PubKeyMultisigThreshold are used in sdk: - deserialization will fail in `readInfo` which tries to read a `crypto.PubKey` into a `localInfo` (called by cosmos-sdk/client/keys.GetKeyInfo) * Update changelog * Rename routeTable to nameTable, multisig key is no longer a pointer * sed -i 's/PubKeyAminoRoute/PubKeyAminoName/g' `grep -lrw PubKeyAminoRoute .` upon Jae's request * AminoRoutes -> AminoNames * sed -e 's/PrivKeyAminoRoute/PrivKeyAminoName/g' * Update crypto/encoding/amino/amino.go Co-Authored-By: alessio <quadrispro@ubuntu.com> |
6 years ago | |
---|---|---|
.. | ||
bench_test.go | crypto: Add benchmarking code for signature schemes (#2061) | 7 years ago |
ed25519.go | Don't use pointer receivers for PubKeyMultisigThreshold (#3100) | 6 years ago |
ed25519_test.go | crypto: Remove interface from crypto.Signature | 6 years ago |