…with the exact same keys if that wasn’t obvious. I’m wondering if there is some data, or hash, or entropy of some sort that’s unique to the device and time of the signing that would make it seem like I signed the same message and posted it two different times, or if it will just look like both devices are “relaying” the same message.

Reply to this note

Please Login to reply.

Discussion

The signature will be different every time you sign even if the event is exactly the same

I worried this would be the case. Would be easier if I could somehow force it to be the same.

My understanding is that randomness is used in the signature to prevent some kind of cryptographic attack

Relays don’t care. As long as they know 1 valid signature it does not matter

Oh I know they wouldn’t care, it was more about preventing from having duplicate posts filling up a feed and trying to prevent that, but having redundant signers available without needing a system of “this device already signed so don’t do anything” that has to get around the whole network… basically a pseudo consensus system among my own devices if they are all in a closed network so one doesn’t repeat the actions of another and flood the feed with the same stuff 2, 3 or more times

They will look as one post if they have the same created_at and data

Why do you want it to be the same?

nostr:note1yfutz0f50pswrqdfxz84v8hspu6y27px0ejp0gdskp8kn9vnftjq2849qy

The signature is different, but the id is the same. Clients and relays have to deduplicate anyway, so whichever signature ends up on the event, only one will ever be displayed or stored in any given place.

Oh sweet! So it’s purely the ID that matters and the signature doesn’t denote anything about whether the post is a duplicate or not? Thats actually great!

Yep, the id is the hash of the event, so that's what makes it content addressable rather than the sig