then you are just wasting sats putting it on chain
Post by chris co
except you would get the timestamp
What the chain says
- Block
- 963 635
- Time
- 2026-08-24T00:55:26Z
- Signer
- 1Pif9p9Cdd7mngkkU1CUZ3RvmT5ToP3xcE
- App
- twetch
- Type
- reply
- Content type
- text/markdown
Fields the transaction did not carry are omitted. Open the payload to see the bytes as stored.
Signed by
1Pif9p9Cdd7mngkkU1CUZ3RvmT5ToP3xcE UnverifiedReplies (10)
but it is encrypted
and you do not have the decrypt key
so all you have is a time stamp to something you cannot decrypt
so it proves nothing
that's like proper Creg Vision
you could encrypt one half. put the hash of the decrypted content next to the encrypted content. and keep a local copy of the content itself. that way you publish encrypted but have a timestamp to show provenance.
you might as well only put the hash on chain
as that is all that matters then
This thread is longer than one page shows. Open a reply to see what follows it.