"What is the process to have someone do the PR for this? Or I do it and
most likely it will be a very shxtty one since I am not a C/C++ expert,
then wasting the time of everybody

It's urgently required, I did consider OP_RETURN as a dart in the past
but changed my mind, it's adapted to the current evolutions, not
flooding bitcoin with 2 txs while only 1 is needed

If not the best 1 tx solution is super simple: store in addresses, and
super bad at the end because burning bitcoins, while still not expensive
if you don't need to store big things"

Le 05/02/2023 à 19:12, Russell O'Connor via bitcoin-dev a écrit :
> On Sat., Feb. 4, 2023, 21:01 Peter Todd, <
> <>> wrote:
>     On February 5, 2023 1:11:35 AM GMT+01:00, Russell O'Connor via
>     bitcoin-dev <
>     <>> wrote:
>     >Since bytes in the witness are cheaper than bytes in the script
>     pubkey,
>     >there is a crossover point in data size where it will simply be
>     cheaper to
>     >use witness data.  Where that crossover point is depends on the finer
>     >details of the overhead of the two methods, but you could make some
>     >reasonable assumptions.  Such a calculation could form the basis of a
>     >reasonable OP_RETURN proposal.  I don't know if it would be
>     persuasive, but
>     >it would at least be coherent.
>     I don't think it's worth the technical complexity trying to
>     carefully argue a specific limit. Let users decide for themselves
>     how they want to use OpReturn.
> Even better.
> _______________________________________________
> bitcoin-dev mailing list

Sophia-Antipolis, France
GitHub :
A Universal Coin Swap system based on Bitcoin:
A bitcoin NFT system:
Move your coins by yourself (browser version):
Bitcoin transactions made simple:
node-Tor :
Anti-spies and private torrents, dynamic blocklist:
Peersm :

bitcoin-dev mailing list

Reply via email to