-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Sassafras Protocol v0.3.2 #14139
Sassafras Protocol v0.3.2 #14139
Conversation
| /// Typically, the implementers of this trait are its associated types themselves. | ||
| /// This provides a convenient way to access generic information about the scheme | ||
| /// given any of the associated types. | ||
| pub trait AppCrypto: 'static + Send + Sync + Sized + CryptoType + Clone { |
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.
Why?
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.
AppCrypto is required to be implemented by any Pair and thus for the new bandersnatch::Pair as well.
Unfortunately bandersnatch_vrf::SecretKey embeds the SecretScalar (here) AND SecretScalar is defined to contain an UnsafeCell (here). Thus can't be Sync.
Nevertheless, Sync is not a hard requirement for our internals. So far, Send seems sufficient for all our use cases
|
(Not ready. Ignore the bogus review request...) |
|
The CI pipeline was cancelled due to failure one of the required jobs. |
Partially Addresses paritytech/polkadot-sdk#41
Delivers:
bandersnatch-vrfsFlows into main Sassafras PR #11879