I haven't dug into it deeply, but I think every PDS opens a websocket to relays that they want to send updates to, and push them into the relay (mainly the bsky one).
If a relay sees msgs that point at a PDS it doesn't have, it can call out to that PDS to directly fetch and/or open a socket.
If a relay sees msgs that point at a PDS it doesn't have, it can call out to that PDS to directly fetch and/or open a socket.
November 4, 2024 at 3:21 PM
I haven't dug into it deeply, but I think every PDS opens a websocket to relays that they want to send updates to, and push them into the relay (mainly the bsky one).
If a relay sees msgs that point at a PDS it doesn't have, it can call out to that PDS to directly fetch and/or open a socket.
If a relay sees msgs that point at a PDS it doesn't have, it can call out to that PDS to directly fetch and/or open a socket.
Fore either, it's because it enables you to sell services that less sophisticated actors can't.
For Ethereum, there's a single commitment (the current block) that enables anyone to verify accuracy from any archive node.
For AT, there's one commitment per PDS, so verifying archives is harder.
For Ethereum, there's a single commitment (the current block) that enables anyone to verify accuracy from any archive node.
For AT, there's one commitment per PDS, so verifying archives is harder.
November 2, 2024 at 11:31 AM
Fore either, it's because it enables you to sell services that less sophisticated actors can't.
For Ethereum, there's a single commitment (the current block) that enables anyone to verify accuracy from any archive node.
For AT, there's one commitment per PDS, so verifying archives is harder.
For Ethereum, there's a single commitment (the current block) that enables anyone to verify accuracy from any archive node.
For AT, there's one commitment per PDS, so verifying archives is harder.
That's a full node, not an archive node in ethereum terminology. Even so, the slashing example isn't useful to the role of the really in AT as I understand it, the relay doesn't require consensus, it can change its mind about PDS history, right?
November 2, 2024 at 2:24 AM
That's a full node, not an archive node in ethereum terminology. Even so, the slashing example isn't useful to the role of the really in AT as I understand it, the relay doesn't require consensus, it can change its mind about PDS history, right?
FYI, slashing is very narrow, and only applies to voting for 2 conflicting views of the chain tip. There is no financial incentive to store past state (an archive node) or even txn history (a full node), though not serving history may cause you to lose peers.
November 2, 2024 at 2:13 AM
FYI, slashing is very narrow, and only applies to voting for 2 conflicting views of the chain tip. There is no financial incentive to store past state (an archive node) or even txn history (a full node), though not serving history may cause you to lose peers.
Do you know if the upcoming content-addressed mempool for celestia is ipfs/ipld? Would be super cool if it was just pluggable, and you could anchor timestamped PDS with blobstream.
November 2, 2024 at 2:01 AM
Do you know if the upcoming content-addressed mempool for celestia is ipfs/ipld? Would be super cool if it was just pluggable, and you could anchor timestamped PDS with blobstream.
