Closed luizstacio closed 3 months ago
This seems completely incorrect. The ED19 "payload" is a message hash, typically sha-2-256. Using the instruction with a non-hashed value is cryptographically unsound. The payload is not hashed again by the instruction. To use ED19
with any message of any size, you must first hash it, typically using S256
instruction to do so.
@Dentosal
https://en.wikipedia.org/wiki/EdDSA on Signature verification
$$ H(R \parallel A \parallel M) A $$
From my understanding the message is required by the algo to be able to perform the hash on the validation. Forcing to hash the message is not an option as you can't control the environment where the signature is going to happen, ex.: Wallets.
When using EdDSA (Ed25519) to verify a signature, the payload is not limited by 32 bytes.
After merging, notify other teams