Just use OP_RETURN for a Nostr note ID and be done with it

Your welcome

Reply to this note

Please Login to reply.

Discussion

Simpler than an OTS?

I was thinking just about a globally unique id, but, yes, a signature or a hash of a signature makes more sense

This is stupid simple. I love it.

I was looking at Open Timestamps, but a tx with the event id in op_return does the job!

The event id is all you need. That could be put in a tx, and the resulting txid when published in a block could be referenced in another nostr event.

What’s a Nostr note ID?

#asknostr

A hash of a signature?

What is the benefit of posting the hash of your Nostr signature in the Op_Return of a Bitcoin transaction?

#asknostr

As a pointer to whatever data you were going to clog up my nodes with

Ohhhhhhh, so it’s like a link to the Nostr protocol. Got it! Thanks brother!

No sweat

I don’t think they’re relaying their true goal. I think what they really want is to eventually turn Bitcoin into a type of Ethereum for their shitcoins.

THIS. And fuck that shit

To obtain the event.id, we sha256 the serialized event. The serialization is done over the UTF-8 JSON-serialized string (which is described below) of the following structure:

[

0,

,

,

,

,

]

That doesn’t work because have ulterior motives.