Quote from: samadamsbeer on Today at 12:29:33 PM

Quote from: DaveF on February 04, 2024, 07:37:50 PM

So what you are looking to do is:

Text:

Code:

This is DaveF saying this

Signature:

Code:

IGd595fz/NXdZJSV0DDA4grRZAf4kDqBB7fa8LnI7wuIf7Ihu8chopvTsWWXGieVFqysnZ3laZZzAJ0Enw5x8cc=

BUT not tell people what address it's signed with.

So, until there is a NEED to prove you wrote something there is no way to know if it's valid or not.

So in theory 10 years from now I could prove that on 4-Feb-2024 because of the above text and signature I controlled the address bc1qugdlj4sghspzyx5w74xm77mn67auyzc2y6huls

I cannot see another need other than that.

-Dave

Yes that is what I was trying to explain I was trying to do. If the document is public, this allows people to view it, but I can selectively prove the ownership to parties I want to do that with. Sounds like a 2nd hashing is a good way to do this.

The issue is that once you let the proof out, no matter who you reveal it to, it's out there because they can then tell anyone.
The other side is you show them in a way that they can see but not duplicate, BUT and this is a big important BUT, they have to then trust that you are not doing something shady in the background.

If you want to give them the process / address / info to prove it then you are giving them the ability to prove it to the world.

Don't know if that matters for what you are trying to do, but it's something to think about.

-Dave