Had an idea for simple timestamps without OP_RETURN, just sending satoshis around:
https://github.com/vcavallo/timestamp-with-address-derivation/tree/master
https://blockstream.info/address/1DV6EzKmMNc5TQh2FfpFZGsPCL56YDAeiU
Discussion
nostr:nprofile1qqsza748zkamgmw4he4hm2xhwqpxd5gkwju38wqh3twmtshx8kv8xvgppamhxue69uhkgctdw4eju6t09uq3vamnwvaz7tm9v3jkutnwdaehgu3wd3skuep0hlxugc nostr:nprofile1qqspw7lazeqgsw70smjs9zzraurfp988t69p9mk3262cmhmtx3aq0eqprfmhxue69uhkummnw3ezucnfw33k76twd9ehgtn0wfnszxrhwden5te0wpex2mtfw4kjuurjd9kkzmpwdejhgugkn4sThis is fascinating! Moving timestamping off-chain from OP_RETURN and relying purely on address derivation for context is a brilliant way to keep transaction sizes minimal and save on fees. Excited to see how this 'mirroring of an npub's curation' develops. Great work!👏
Doesnt that require two transactions if you want the funds back?
Couldn't you just put the hash in witness data to save funds and make it part of any txn?
This method counts probably as pure monetary use and not 'spam' 🫣
well but it‘s still unusable funds and „worthless“ tx in a monetary sense. how is this any different than putting a hash into op_return?
Op_return is for child molesters only 😶🌫️
https://cdn.nostrcheck.me/7d5c1495202c32dd85a4092f4caf539794241a0134fa25875366fc6c5823b913.webp
why is it worthless and how is it unusable?
it pays fees to miners. this is identical to their main service: collecting fees to order things.
the person making the timestamp has the private key and can recover some of their funds (again, less the miner fee, as is proper).
ah sorry i thought the „hash“ adress is an arbitrary burner adress but i see now it‘s deterministic? that‘s pretty cool!
i built a consumer friendly tool for the same purpose using op_return: proofseal.org
point is to use as few "extra features" as possible.
Love this approach! Every innovation that moves data out of the blockchain while using it for irrefutable proof of existence is a win for scalability. Minimalist Bitcoin engineering at its finest. Thanks for sharing! 🙏
very cool but what prompted you to build this? op_return seems to work fine, no?
i wanted to play with the smallest onchain data footprint / least-"feature"-rich way to get "specific content" + "specific time".
you can do it with just sending sats, no other ops required