Is there any built in nostr "verification" method?
I'm imagining something like a bip-32 label that would indicate a user completed some form of verification, which applications can use as an anti-spam measure. The specific form of verification is irrelevant, and many providers could exist, they'd publish an event to indicate the result:
{
"tags": [
["p": "verifiedpubkey...", ...],
["L": "verification"],
["l": "captcha-verified", "verification"],
],
...
}
{
"tags": [
["p": "verifiedpubkey...", ...],
["L": "verification"],
["l": "captcha-verified"],
["l": "email-verified", "verification"],
],
...
}
{
"tags": [
["p": "verifiedpubkey...", ...],
["L": "verification"],
["l": "phone-verified", "verification"],
],
...
}
{
"tags": [
["p": "verifiedpubkey...", ...],
["L": "verification"],
["l": "payment-verified", "verification"],
],
...
}
"payment-verified" might include the amount paid
{
"tags": [
["p": "verifiedpubkey...", ...],
["L": "verification"],
["l": "fidelity-bonded", "verification"],
],
...
}
"fidelity-bonded" might include a UTXO and BIP-127 proof
{
"tags": [
["p": "verifiedpubkey...", ...],
["L": "verification"],
["l": "twitter-verified", "verification"],
],
...
}
"twitter-verified" might include the URL of a tweet committing to the verifiedpubkey (and something from the verifiedpubkey committing to the twitter account?)
I'm not sure if the extra information might warrant a different kind than normal labels.