goat.navy / did-plc-p2p-guard-rails
Design for P2P timestamping guardrails for DID:PLC
fork atom

consistency

goat.navy 7f7bb1a7 65be24ad

options
unified split
Changed files
+1 -1
README.md
+1 -1
README.md
··· 172 172 173 173 ### Why only guardrails? 174 174 175 - We could solve the problems listed in "problems we don't solve" by removing the timestamping servers entirely and just putting all the updates on a public blockchain. However this will tend to be slower and more expensive than using a semi-trusted timestamping server, and this proposal aims to avoid damaging the experience of users to the extent that a server they trust is running honestly and working well. 175 + We could solve the problems listed in "problems we don't solve" by removing the sequencers entirely and just putting all the updates on a public blockchain. However this will tend to be slower and more expensive than using a semi-trusted timestamping server, and this proposal aims to avoid damaging the experience of users to the extent that a server they trust is running honestly and working well.