Saylor is trying to create a trust anchor. But since anyone can create their own DID:BTC without Microstrategy's approval (lots of spam), the anchor must be Microstrategy's KYC platform.
Microstrategy will have select DID:BTCs they have approved and probably KYCed to receive the Orange check. This means, Orange check verifiers must not only check the DID Document but verify if the DID itself was signed by Microstrategy's master key.
Like ODELL (nprofile…awa6) would say: ORANGE CHECKS ARE JUST BLUE CHECKS FROM A DIFFERENT COMPANY.
Vitor Pamplona
npub1gc…fnj5z
2024-05-02 13:13:12
Author Public Key
npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5zPublished at
2024-05-02 13:13:12Event JSON
{
"id": "ee5aa97b0d1b508c3d5e96106e8e2c9fce872540e7bbafbb090f5a316d614ccc",
"pubkey": "460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c",
"created_at": 1714655592,
"kind": 1,
"tags": [
[
"p",
"04c915daefee38317fa734444acee390a8269fe5810b2241e5e6dd343dfbecc9",
"wss://relay.nostr.band/",
"ODELL"
]
],
"content": "Saylor is trying to create a trust anchor. But since anyone can create their own DID:BTC without Microstrategy's approval (lots of spam), the anchor must be Microstrategy's KYC platform. \n\nMicrostrategy will have select DID:BTCs they have approved and probably KYCed to receive the Orange check. This means, Orange check verifiers must not only check the DID Document but verify if the DID itself was signed by Microstrategy's master key. \n\nLike nostr:nprofile1qythwumn8ghj7un9d3shjtnwdaehgu3wvfskuep0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgawaehxw309ahx7um5wghx6at5d9h8jampd3kx2apwvdhk6tcqyqzvj9w6alhrsvtl5u6ygjkwuwg2sf5lukqskgjpuhnd6dpal0kvjr7awa6 would say: ORANGE CHECKS ARE JUST BLUE CHECKS FROM A DIFFERENT COMPANY.",
"sig": "a7b10080d9fd9674e2b86a5f3804754c41c3b3bb58f9211844c23d8ab6894cbdd697125f5be4327bfd843c2a53738945f68517337d0297ce412b5d446a32b7a9"
}