You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm a little hesitant on recommending things like this as -- in my view -- it's promoting using deterministic nonce generation schemes which we know is dangerous if not used in a very narrow specific way.
I'm a little hesitant on recommending things like this as -- in my view -- it's promoting using deterministic nonce generation schemes which we know is dangerous if not used in a very narrow specific way.
I see your point, but most likely people will want to use a deterministic way. Imo the spec should assume the implementer knows what they are doing and not try to write around them not.
Also, having something like will hopefully be listed right next to the docs saying how to correctly and safely do deterministic nonces, so it could end up stopping someone from making a mistake.
Related to #90
Curious on people's thoughts on claiming a DLC Oracle specific SLIP 44 coin type for deterministically generating nonces.
This could help ensure that oracles do not reuse any keys if they are using a seed for multiple purposes.
In my project, krystal bull, I am using 585 because it is unclaimed.
The text was updated successfully, but these errors were encountered: