"80 bytes is standard policy on the network" -Adam Back
https://nitter.net/adam3us/status/1733409334577541162?s=20
"Samourai has no obligation of any kind to 'fix', they're using network standard..." -Adam Back
https://nitter.net/adam3us/status/1733409758508367972
"Luke often is correct, but sometimes only with a non-standard definition." -Adam Back
https://nitter.net/adam3us/status/173309859612219830
"I think it's an accident." -Adam Back
nostr:npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk's rationale is "see? I was right." That's it. But there are no "right and wrong" when it comes to OP_RETURN.
That being said, Wasabi only has to implement storing the message they need somewhere else, hashing it and then store the hash in a 40 byte OP_RETURN transaction. The client validates the message comparing its hash to the hash stored in Luke's 40 byte version of OP_RETURN, problem solved, everyone happy.
It's an easy solution and takes minutes to develop.
