In Bluesky like in all proper systems, there is a single server that you write to, think like in WebDAV or in Google Drive or Proton Drive...
Because you have that, you also have a merkle tree that is built on top of the entire tree and signed with one key at the root.
The moment you change your server, and thus you also change the delegation to the signer over the merkle tree, apps realize that your identity is now pointing to a new signer of the merkle tree..
So they abandon all previous events signed by the previous delegated server key, transitively with merkle proof and then go fetch the same event again from the new server with the new signer.
That if they care of course, in reality if anyone is suspicious whether or not a Post that is featured on a feed is actually created by you, the simplest solution is just go read it from your Homeserver, and they know that Homeserver the same way they know the signer, they read it from the PLC directory which acts as a centralized ledger instead of a Blockchain.
The same applies in systems that use Rootstock instead of the centralized ledger.
Nuh
npub1jv…s7yqz
2026-06-01 12:35:35 UTC
in reply to nevent1q…4khh
Author Public Key
npub1jvxvaufrwtwj79s90n79fuxmm9pntk94rd8zwderdvqv4dcclnvs9s7yqzSeen on
wss://relay.primal.netPublished at
2026-06-01 12:35:35 UTCEvent JSON
{
"id": "513e1ff2364e5a4191f9f9b0fe314a7fadfbc8bda3db74af92a35943a3024bea",
"pubkey": "930ccef12372dd2f16057cfc54f0dbd94335d8b51b4e2737236b00cab718fcd9",
"created_at": 1780317335,
"kind": 1,
"tags": [
[
"e",
"15fde76baeb9bac55815115d43bc4be5a67cfb611a78f718d0c599dc9b40b7e9",
"wss://relay.primal.net/",
"root",
"930ccef12372dd2f16057cfc54f0dbd94335d8b51b4e2737236b00cab718fcd9"
],
[
"e",
"610081244721ce400ab27350ebd0f63bbbcafac4c6b33c1056f3939d51edee99",
"wss://relay.primal.net/",
"reply",
"d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23"
],
[
"p",
"d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23"
]
],
"content": "In Bluesky like in all proper systems, there is a single server that you write to, think like in WebDAV or in Google Drive or Proton Drive...\n\nBecause you have that, you also have a merkle tree that is built on top of the entire tree and signed with one key at the root. \n\nThe moment you change your server, and thus you also change the delegation to the signer over the merkle tree, apps realize that your identity is now pointing to a new signer of the merkle tree..\n\nSo they abandon all previous events signed by the previous delegated server key, transitively with merkle proof and then go fetch the same event again from the new server with the new signer.\n\nThat if they care of course, in reality if anyone is suspicious whether or not a Post that is featured on a feed is actually created by you, the simplest solution is just go read it from your Homeserver, and they know that Homeserver the same way they know the signer, they read it from the PLC directory which acts as a centralized ledger instead of a Blockchain.\n\nThe same applies in systems that use Rootstock instead of the centralized ledger.",
"sig": "1dc3633865b8cd4e3173112dde791a5efe214141fe0aaa270406d4e795a8f2fa4e29b0f2791a95dbbeb6e516b45006f12933edb6e4d7feb29203aec050d1aff9"
}