POW for creating AES ciphers #10
Conversation
| impl AesCipher { | ||
| pub(crate) fn new(challenge: &[u8; 32], nonce: u32, params: ScryptParams) -> Self { | ||
| let mut key = [0u8; 16]; | ||
| scrypt(challenge, &nonce.to_le_bytes(), params, &mut key); |
There was a problem hiding this comment.
is there a specific reason why scrypt was chosen here instead of blake3?
There was a problem hiding this comment.
I think that scrypt was chosen because of its ASIC-resistance. @fasmat could you help answering?
There was a problem hiding this comment.
The reason why we hash the challenge and the nonce is because we want checking part of the post data with many nonces to be more costly than checking the full data with few nonces.
Scrypt serves better as a proof of work in this regard and was suggested by the research team.
As to why we are using scrypt + keccak instead of scrypt + blake3: because we are already using the former for label creation and won't change that before genesis.
If at any point we switch to scrypt+blake for label generation we can do that here as well.
No description provided.