LogicallyMinded on Nostr: I fear that the addition of DIDs on #Bitcoin by #Saylor may lead to the normalization ...
I fear that the addition of DIDs on #Bitcoin by #Saylor may lead to the normalization of KYCed BTCs which could then be used as a standard for authorizing bitcoins to be off-ramped to fiat. Is this fear unfounded? What’s the use case of #DigitalID for #MicroStrategy?
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.
Published at
2024-05-02 16:04:17Event JSON
{
"id": "cf87ba75c183da6bf98b5d82b5ccad2660519aa58714087022e6ee6e0ec02246",
"pubkey": "83d302b5c25ed43e5b75532fa6a6bda21c4b63e9f516826798f516fc4159b9c7",
"created_at": 1714658657,
"kind": 1,
"tags": [
[
"q",
"ee5aa97b0d1b508c3d5e96106e8e2c9fce872540e7bbafbb090f5a316d614ccc"
],
[
"p",
"460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
],
[
"p",
"460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
],
[
"t",
"bitcoin"
],
[
"t",
"saylor"
],
[
"t",
"digitalid"
],
[
"t",
"microstrategy"
]
],
"content": "I fear that the addition of DIDs on #Bitcoin by #Saylor may lead to the normalization of KYCed BTCs which could then be used as a standard for authorizing bitcoins to be off-ramped to fiat. Is this fear unfounded? What’s the use case of #DigitalID for #MicroStrategy? nostr:note1aed2j7cdrdggc027jcgxar3vnl8gwf2qu7a6lwcfpadrzmtpfnxq7vg9s3",
"sig": "d5d127ffb772b865462b911c86c329b8e785d783852983c7165ee51863aab20700f5a2dad2c58bfff7811ed1bcbc07cb1e87076f5a629ec45cfefb51e7664122"
}
