Alternatively, it can be done by providing the criteria's hash beforehand.
The hash can prove that you have not changed the criteria since everyone can compute the its hash once it's revealed.
I'd recommend SHA256 for this.
I picked a Bitcoin signed message over SHA256, because I assumed more users here would be able to verify it on their own.The hash can prove that you have not changed the criteria since everyone can compute the its hash once it's revealed.
I'd recommend SHA256 for this.
Option 3: Use your PGP key! It's more secure than any of the options above.
PGP is more complicated to verify than either of the other 2 options.Let's do an experiment:
-----BEGIN BITCOIN SIGNED MESSAGE-----
Signed message will be revealed on 10/29/2022
-----BEGIN SIGNATURE-----
IIVa9HxfBRnnOFfks0sRBqlK5vd9tOzh6zgA6L6OFLfjCedQocGY6jxeg7tJLAnPKJrAk0RCf1rV6A6 ZSALY9tA=
-----END BITCOIN SIGNED MESSAGE-----
Address staked here.
Would that be OK?
I'll tell you on October 29 -----BEGIN BITCOIN SIGNED MESSAGE-----
Signed message will be revealed on 10/29/2022
-----BEGIN SIGNATURE-----
IIVa9HxfBRnnOFfks0sRBqlK5vd9tOzh6zgA6L6OFLfjCedQocGY6jxeg7tJLAnPKJrAk0RCf1rV6A6 ZSALY9tA=
-----END BITCOIN SIGNED MESSAGE-----
Address staked here.
Would that be OK?
Fuck you all 😘
Wrong topic, orgies happen here.Quote
Maybe you thinks it's complicated hearing those complicated words encrypt/decrypt 😂
It's meant to be easy but not sure why you think it's complected LOL
Load precipitants public key and sign the message. You need only recipients public key.
I tried it a few times, and it was annoyingly complicated. What's worse, is that it didn't give me any confidence that I know what I'm doing.It's meant to be easy but not sure why you think it's complected LOL
Load precipitants public key and sign the message. You need only recipients public key.
Quote
It's as simple as sending an email.
If that would be true, everyone would use PGP by default for all their emails.