-
Notifications
You must be signed in to change notification settings - Fork 47
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: single signature DID calls/creation #551
Conversation
dispatch did calls without a second signature
No need to have all the details since we can simply batch update calls with `dispatch_as`.
f5cba9b
to
fe32789
Compare
reorder the tests so that the successful test comes first
@@ -79,6 +79,7 @@ | |||
|
|||
#![cfg_attr(not(feature = "std"), no_std)] | |||
#![allow(clippy::unused_unit)] | |||
#![recursion_limit = "256"] |
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 was necessary because of the new benchmarks. We probably have too many benchmarks. 😁
@@ -28,6 +28,33 @@ use crate::{ | |||
mock_utils::*, | |||
}; | |||
|
|||
#[test] |
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 pulled the "successful-case" test to the top
// Measured: `353` | ||
// Estimated: `5777` | ||
// Minimum execution time: 186_836_000 picoseconds. | ||
Weight::from_parts(189_377_000, 0) |
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.
weights will be calculated on our benchmark server. They were done with debug builds
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.
3 minor comments. I like the modular test setup. 🥳
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.
Love it! I just don't understand why the widespread use of AsRef<[u8]>
for DID keys?
This enables individual tests for each benchmark.
fix https://github.com/KILTprotocol/ticket/issues/2849
This PR enables blockchain accounts to manage DIDs on the KILT chain.
Sending DID calls and creating DIDs will be possible with any substrate enabled wallet (polkadotJS, Nova, ...).
Creating a DID will also be possible but still requires two signatures. By supporting wrapped payloads as a special signature type, wallets that support
signRaw
or similar will be able to create DIDs. With this wrapped type the default way of sending DIDCalls would also work, but still require a second signature.Metadata Diff to Develop Branch
Peregrine Diff
Spiritnet Diff
Checklist:
array[3]
useget(3)
, ...)