Event JSON
{
"id": "2211c0a6f42d27cfa71ab62643e3225ec51ca9076fc63c2e2b6018c68cdf45d0",
"pubkey": "c753c77b1c78b2c815d52e009e96444308d844ea2e7a6ded754dfe5f7247fc3f",
"created_at": 1731800577,
"kind": 1,
"tags": [
[
"e",
"67665526a53c29eefc282bfa8a8e723faf71b9cc52f39242f82b8472ee9f9f41",
"wss://ditto.pub/relay",
"root",
"3d2e51508699f98f0f2bdbe7a45b673c687fe6420f466dc296d90b908d51d594"
],
[
"e",
"ec6842cf3fffb615f453e4272eb2cde78ebb12ac956fda0aef01f753ec66b904",
"wss://ditto.pub/relay",
"reply",
"32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245"
],
[
"p",
"32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245",
"wss://ditto.pub/relay"
],
[
"p",
"ff2bfabafea9d5c3b00fe6a285139239012680f3cbf43ac5532a8736a95f8070",
"wss://ditto.pub/relay"
],
[
"p",
"3d2e51508699f98f0f2bdbe7a45b673c687fe6420f466dc296d90b908d51d594",
"wss://ditto.pub/relay"
],
[
"r",
"https://app.ilograph.com/@mikestaub/atprotocol%2520overview/Protocol%2520Overview/_walkthrough/1"
]
],
"content": "I did a deep-dive on the code and the only part of the architecture that is not currently decentralized is the plc-service, which resolves the DIDs with a custom method. You can literally run any other component yourself. Arguably this is the most important piece, so criticism is valid. But it's not clear how to decentralize governance of such a system while preserving the UX. Bitcoin 'gave up' on trying by just piggybacking off physics with PoW for consensus, which was not obviously going to work when it was created. I think perhaps the ultimate solution is just to use Bitcoin for the ID consensus with something like the did:btc or did:ion methods. The incentives to host decentralized infra without a token are not strong. Even nostr struggles with this currently. https://app.ilograph.com/@mikestaub/atprotocol%2520overview/Protocol%2520Overview/_walkthrough/1",
"sig": "a2ef2ae2861441d7bfb58dbbbad70216ce77e801a688395dcf12cd56d90fbd3aeb048271e0f18c306327453ba275d5e7e3316bc46bb57fe31ff89c7a390f78aa"
}
