It's not about delaying the transaction. If you only rely on CLTV, a spammer can mine a notarization transaction today and pretend that it has been published a long time ago.
But you are right, the software could additionally check that the notarization was mined N blocks before the locktime. This introduces an extra parameter, and it feels a bit like misusing CLTV, but it would indeed allow for longer time delays than CSV.
Login to reply
Replies (1)
The extreme case of this could be very interesting for game theory, leading to just one notary getting a very large monopoly
Imagine a single notary does a deal with all the big mining pools which together control 90% of hashrate
That notary could advertise: "give me 10 sats and I'll notarise it as 50 sats".
As they control 90% of hashrate, they will on average get 45 sats back from those 50, and hence the real cost to the notary is just 5 sats (on average) compared to the 10 sats that they earn from the creator of the nostr content
With CSV, the delay is just about 15 months, and that's short enough that the big notary is happy to wait
I think the only solution is to really make sure that today's miners don't see any value from the burning, so either notarizing to an OP_RETURN, or use CLTV to send it very far in the future
@c03rad0r , is this the right npub for Espen?: @npub16dzd...g7ac I think he had the same idea