-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: ADR-005: Support multisig chain link #708
Conversation
e2f37e7
to
7bb7535
Compare
7bb7535
to
b476e11
Compare
Hi, @RiccardoM @bragaz
because I propose that we can convert it to hex string from the proto, instead. What do you think? |
@dadamu What if we use the |
@RiccardoM Unfortunately, |
@dadamu I have just finished experimenting with this problem, and I think that we can do as follows: 1. Create a new interface called Then, we only need to register the new This will allow us to use I have tried implementing all of this and pushed the changes to a new branch named |
@RiccardoM Okay, got it. will extend the interface with the same way as |
Codecov Report
@@ Coverage Diff @@
## master #708 +/- ##
==========================================
- Coverage 84.23% 78.81% -5.42%
==========================================
Files 91 53 -38
Lines 6624 4320 -2304
==========================================
- Hits 5580 3405 -2175
+ Misses 833 737 -96
+ Partials 211 178 -33
Continue to review full report at Codecov.
|
@@ -0,0 +1,345 @@ | |||
package v230 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
v230 is the copy paste of the latest chain link file for the v210 store_test.
@@ -87,6 +88,7 @@ func (AppModuleBasic) GetQueryCmd() *cobra.Command { | |||
|
|||
// RegisterInterfaces registers interfaces and implementations of the profiles module. | |||
func (AppModuleBasic) RegisterInterfaces(registry codectypes.InterfaceRegistry) { | |||
v230.RegisterInterfaces(registry) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is for v210 store_test as mentioned in v230 files.
Co-authored-by: Leonardo Bragagnolo <leo.braga95@gmail.com>
…mos-labs/desmos into paul/adr-005-multisig-chainlink-impl
Signed-off-by: Riccardo Montagnin <riccardo.montagnin@gmail.com>
…mos-labs/desmos into paul/adr-005-multisig-chainlink-impl � Conflicts: � app/desmos/cmd/chainlink/create_json.go � app/desmos/cmd/chainlink/create_json_test.go
Signed-off-by: Riccardo Montagnin <riccardo.montagnin@gmail.com>
@dadamu I've improved the code organization by splitting apart the various getters and creating a new builder interface. The multi-sig chain link test is however failing. Can you check why please? I didn't change pretty much anything except forcing the |
@RiccardoM Fixed. |
.changeset/entries/a492eff6c4ec45c98cb555b14de9f27ba50da5b147ff05b7a4cb1707af73655c.yaml
Outdated
Show resolved
Hide resolved
} | ||
|
||
// Get the sign mode | ||
signMode := signing.SignMode_SIGN_MODE_LEGACY_AMINO_JSON |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One thing I don't understand if it's correct or not is this line: the transaction could be signed using SIGN_MODE_DIRECT
as well from what I know. Isn't this valid for multi-sig transactions as well? Or are they all signed using the SIGN_MODE_LEGACY_AMINO_JSON
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They are all signed in SIGN_MODE_LEGACY_AMINO_JSON
if it is the multi-sig tx as well as the ledger tx.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dadamu Perfect, thanks for the reference link as well! 🙏
…f05b7a4cb1707af73655c.yaml Co-authored-by: Riccardo Montagnin <riccardo.montagnin@gmail.com>
Signed-off-by: Riccardo Montagnin <riccardo.montagnin@gmail.com>
…impl' into paul/adr-005-multisig-chainlink-impl
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've just updated the create-chain-link-json
documentation to include extensive explanation on what it's required when using it with multi-sig accounts. I've also added the missing docs to the generatePubKeyAndMultiSignatureData
testing method.
I think the implementation is correct and ready to go.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ready to ship
Description
Closes: #633
This PR implements ADR-005.
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...
!
to the type prefix if API or client breaking changeCHANGELOG.md
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...
!
in the type prefix if API or client breaking change