crypto: Use BLS for AuthorityKeyPair #4645
Conversation
joyqvq
force-pushed
the
bls-switching11
branch
from
6358cc3
to
6dcf716
Compare
|
Running on legacy list auth sigs view works: Also works on new auth sig in one string: |
joyqvq
force-pushed
the
bls-switching11
branch
from
6dcf716
to
4d4a2c0
Compare
|
💳 Wallet Extension has been built, you can download the packaged extension here: https://github.com/MystenLabs/sui/actions/runs/3068352636#artifacts |
joyqvq
force-pushed
the
bls-switching11
branch
5 times, most recently
from
f4c8908
to
41bcda7
Compare
| }; | ||
| } else { | ||
| validatorSignatureData = { | ||
| title: 'Aggregated Validator Signature', |
There was a problem hiding this comment.
After rebasing, check again w/ @huitseeker if we're good to go, so we can merge asap to avoid conflicts that would probably require an extra cycle of retesting locally for incompatibilities etc
|
This is awesome, thank you so much @joyqvq for helping with the BLS PR splitting and pushing this to completion! |
| if (Array.isArray(txdata.authSignInfo.signature)) { | ||
| validatorSignatureData = { | ||
| title: 'Validator Signatures', | ||
| content: txdata.authSignInfo.signature.map( |
There was a problem hiding this comment.
Just curious, why do we need this? Don't we wipe the whole DB anyways for each devnet launch?
There was a problem hiding this comment.
yes, just doing this for precaution, we can eventually deprecate the legacy display
joyqvq
force-pushed
the
bls-switching11
branch
from
41bcda7
to
1b095ae
Compare
joyqvq
force-pushed
the
bls-switching11
branch
from
1b095ae
to
aee0ba3
Compare
narwhal pointer using BLS