Jeff Burdges
Lightning then? ;)
Is this done?
Around this, there is an interesting note on page 80 of https://csrc.nist.gov/files/pubs/fips/203/ipd/docs/fips-203-initial-public-comments-2023.pdf > NIST removed the step to hash system randomness; see page 2, lines 309 to 314. If you...
Appears that's not a concern: https://github.com/simplex-chat/simplexmq/blob/538dcb6a4c53e115655dc07266c4ff386d45511d/protocol/pqdr.md?plain=1#L210
I'd just say "post-quantum anonymity" as opposed to "post-quantum financial soundness" because "forward-private" sounds too much like "forward-secure", which always denotes an improvement, not a weakening. If folk want post-quantum...
If the orphan rules block this, then one work around looks like: ``` use ark_serialize::{CanonicalDeserialize, CanonicalSerialize, Compress, Valid, Validate, SerializationError}; use ark_std::{borrow::{Borrow,Cow,ToOwned}, convert::AsRef, io::{Read,Write}, ops::{Deref}, vec::Vec}; #[derive(Clone,Debug,Default,PartialEq,Eq,PartialOrd,Ord)] pub struct CowVec);...
In future, the //polkadot//.. derivation paths will be kinda dead once the RC accounts are gone, so the privacy reasons for distinguishing it becomes somewhat moot. You could therefore add...
A priori, it's too late for tech fixes, since many people would not upgrade their signers, hence my outreach suggestion, but.. > Change the derivation path for the Polkadot Asset...
Alright @ERussel I've a better suggestion: Vault sees both the public key ands the chain id when it gives you this error, right? If Vualt knows the key on some...
An unsafe counter maybe useful, and easier to maintain, so this code would hard error on `something_unsafe_4`: ``` unsafe(3) { something_unsafe_1( something_unsafe_2(something_unsafe_3()), something_unsafe_4() ); } ``` This code would error...