That's a neat idea. I worked for a client who wanted to verify writing was human-generated. There was a way around it, but overall it worked pretty well.
The only real flaw I see is that it could be mimicked very easily. What may be better would be to have the hash be uploaded to a server or use some cloud provider's free tier and serverless functions (within free tier) to verify the transaction hash is correct (e.g., right email sender, time). I wouldn't store the body or title of the email.
thanks! i thought about server version, but decided to keep it fully local for now.
it has ssh-like mechanism of public key + signature generation on first contact, so just mimicking the badge or adding random signature won't work – recepient will see it's not verified signature.
"I accepted that doomscrolling is an addiction, not a lack of discipline; the goal isn't willpower, it's friction." - the most important insight in here.
I have an extension as well that generates affiliate links in Amazon. Though I love the idea and think it's neat, I would highly doubt you will recoup the AI costs given the affiliate percentage on most items.
The only real flaw I see is that it could be mimicked very easily. What may be better would be to have the hash be uploaded to a server or use some cloud provider's free tier and serverless functions (within free tier) to verify the transaction hash is correct (e.g., right email sender, time). I wouldn't store the body or title of the email.