Running knots on 2 nodes. Didn’t make any config changes

Reply to this note

Please Login to reply.

Discussion

Good man, I respect your opinion then.

FWIW while the data might be arbitrary in respect to Bitcoin’s core function, I think that tying together two freedom protocols in a useful way would be beneficial for both.

Storing arbitrary data is more cost-effective and useful in other locations other than the Bitcoin Blockchain.

(the note was stored in nine locations, worldwide, without permission)

Bitcoin provides a trustless time stamp accurate within 1hr which is not provided by relays

Nostr is free and doesn’t require proof of work

Exactly, not saying it should be any different. But I should be able to pay *voluntarily* to have certain events immutable and timestamped without trusting anyone. Right now, anyone can publish any timestamp (even future) and any relay can do whatever they want in terms of dumping events. If your nsec was compromised for example, you’d want to publish an immutable timestamped event that says “this nsec is pwned”… only one example that I would GLADLY pay for and is not securely & trustlessly possible (without NIP03: which relies on a 3rd party and no client implements).

Totally. Just keeping under 83 bytes 🫡 for old times sake

Word… the issue is when it’s too small you need 3rd party services to make it useful. Like Opentimestamps