Search content
Sort by

Showing 2 of 2 results by Stantcheva
Post
Topic
Board Development & Technical Discussion
Re: Making Bitcoin and its Forks Turing Complete
by
Stantcheva
on 05/04/2022, 12:45:44 UTC
would you prefer i store a 60KB picture of my daughter's cat using 700 transactions or 1 transaction?   Cheesy
What we prefer is for bitcoin to be used as it was meant to, meaning as a payment system not a distributed database where arbitrary data is being stored.

The reason why OP_RETURN was introduced is to discourage exactly what you are doing (creating UTXO bloat) and the 80-byte limit is another discouragement telling you that bitcoin blockchain is not a place to store arbitrary data, even if you could.

just found this paper from 2019 has discussed whether metadata negatively impact on the effectiveness of Bitcoin with respect to its primary function, including different methods containing UTXO bloat and OP_RETURN, hope this can provide more perspectives~~ Grin

https://www.researchgate.net/profile/Livio-Pompianu/publication/330385593_A_Journey_into_Bitcoin_Metadata/links/5e3990baa6fdccd96587d6df/A-Journey-into-Bitcoin-Metadata.pdf
Post
Topic
Board Development & Technical Discussion
Merits 1 from 1 user
Re: Making Bitcoin and its Forks Turing Complete
by
Stantcheva
on 04/04/2022, 07:52:17 UTC
⭐ Merited by embii (1)
Quote
no, they are all valid transactions to users who just haven't been born yet
But you could just use OP_RETURN! Better: you could use OP_RETURN inside TapScript and just commit to the blockchain, instead of burning coins! There is no reason to burn anything, there is also no reason to bloat the chain. Another thing is that one commitment for the whole network would be cheaper than pushing every commitment for every user.

this paper from ledger compares the efficiency and costs of P2FKH technology employed by apertus.io with other methods to insert data in bitcoin blockchain, hope this can provide some help;D
https://ledger.pitt.edu/ojs/ledger/article/view/101/93