Alin Tomescu

I ran into the same bug [here](https://github.com/scipr-lab/libff/issues/108), for what it's worth.

Intriguing. The math is a bit above my pay grade, but I guess I can wrap my own pairing function to check for & prevent this bug. Thank you!

Uhm, what's the question exactly? Is it about whether we should specify the hashing algorithm used to compute an NFT's content hash? If so, that seems reasonable to me as...

> Any ETA as to when this is going to land? Not yet :( Currently blocked by (1) other priorities and (2) complications in estimating gas for these primitives.

> > > > Well - a vote of support for this capability from Nutrios. Lots of things we would leverage this for. That's great to know! Tell us more:...

> * Is this ready? Nope. See TODOs. > * VeiledCoin is not ready -- maybe move to another PR? there's currently no way to go from VeiledCoin to Coin....

Hey folks, Thanks for opening this issue! Please submit a PR that introduces **only** the `rotate_authentication_key_simplified` functionality which: 1. Replaces the signer with an address, thereby removing the need for...

I will reply with thoughts in a few days; a little too busy with other things to think through this carefully right now. Apologies.

Hi @JackyWYX, Apologies for the delay. The **bad news** is what you are trying to do will likely get you into trouble via _signature replay attacks_. Specifically, consider your `pubkey1`...

Indeed, for transaction signatures, they will be domain-separated by other things, like the address of the account. Nonetheless, people could still shoot themselves in the foot when verifying MultiEd25519 signatures...