The relationship between Proof-of-Publication and Anti-Replay Oracles



Summary:

In a discussion about the creation of new primitives operating on message, pubkey, and signature, Adam Back and Peter Todd debate the security implications of such a system. Todd suggests that using a trusted third party to implement AntiReplaySign(), which is only usable once for a given pubkey, would be more secure than trying to prevent double-spending with math alone. Back goes on to suggest an alternative method using one-show signatures, but Todd argues that it's not necessary to get into the specifics of crypto math so early and that verifying ECDSA signatures directly through Bitcoin scripting would work just as well. The main concern raised is the risk of Sybil attacks, but the details of how double-spend punishment would be implemented are considered premature optimization.


Updated on: 2023-06-09T15:00:35.752087+00:00