Re: [bitcoin-dev] OP_RETURN inside TapScript

2022-02-25 Thread Zac Greenwood via bitcoin-dev
Hi ZmnSCPxj, To me it seems that more space can be saved. The data-“transaction” need not specify any output. The network could subtract the fee amount of the transaction directly from the specified UTXO. A fee also need not to be specified. It can be calculated in advance both by the network and

Re: [bitcoin-dev] Draft-BIP: Ordinal Numbers

2022-02-25 Thread Billy Tetrud via bitcoin-dev
> what if/when we introduce some Monero-like system and hide coin amounts? I really don't see a world where bitcoin goes that route. Hiding coin amounts would make it impossible to audit the blockchain and verify that there hasn't been inflation and the emission schedule is on schedule. It would

Re: [bitcoin-dev] OP_RETURN inside TapScript

2022-02-25 Thread ZmnSCPxj via bitcoin-dev
Good morning Zac, > Hi ZmnSCPxj, > > To me it seems that more space can be saved. > > The data-“transaction” need not specify any output. The network could > subtract the fee amount of the transaction directly from the specified UTXO. That is not how UTXO systems like Bitcoin work. Either you co

Re: [bitcoin-dev] Draft-BIP: Ordinal Numbers

2022-02-25 Thread AdamISZ via bitcoin-dev
> I really don't see a world where bitcoin goes that route. Hiding coin amounts > would make it impossible to audit the blockchain and verify that there hasn't > been inflation and the emission schedule is on schedule. It would inherently > remove unconditional soundness from bitcoin and replace

Re: [bitcoin-dev] OP_RETURN inside TapScript

2022-02-25 Thread Zac Greenwood via bitcoin-dev
Hi ZmnSCPxj, > Either you consume the entire UTXO (take away the "U" from the "UTXO") completely and in full, or you do not touch the UTXO Ok, so enabling spending a UTXO partly would be a significant departure from the systems’ design philosophy. I have been unclear about the fee part. In my pr

Re: [bitcoin-dev] Draft-BIP: Ordinal Numbers

2022-02-25 Thread Billy Tetrud via bitcoin-dev
> El Gamal commitments, for example, are perfectly binding but only computationally hiding. That's very interesting. I stand corrected in that respect. Thanks for the information Adam! On Fri, Feb 25, 2022, 05:17 AdamISZ wrote: > > I really don't see a world where bitcoin goes that route. Hidin

Re: [bitcoin-dev] Recursive covenant opposition, or the absence thereof, was Re: TXHASH + CHECKSIGFROMSTACKVERIFY in lieu of CTV and ANYPREVOUT

2022-02-25 Thread Anthony Towns via bitcoin-dev
On Thu, Feb 24, 2022 at 12:03:32PM +, ZmnSCPxj via bitcoin-dev wrote: > > > Logically, if the construct is general enough to form Drivechains, and > > > we rejected Drivechains, we should also reject the general construct. > > Not providing X because it can only be used for E, may generalise to

Re: [bitcoin-dev] Recursive covenant opposition, or the absence thereof, was Re: TXHASH + CHECKSIGFROMSTACKVERIFY in lieu of CTV and ANYPREVOUT

2022-02-25 Thread ZmnSCPxj via bitcoin-dev
Good morning AJ, > ZmnSCPaj, are you arguing that drivechains are bad for bitcoin or are you > arguing that it would be unwise to opt into a drivechain? Those are very > different arguments. If drivechains compromised things for normal bitcoin > nodes that ignore drivechains, then I agree that

Re: [bitcoin-dev] A Comparison Of LN and Drivechain Security In The Presence Of 51% Attackers

2022-02-25 Thread ZmnSCPxj via bitcoin-dev
Good morning Paul, > I don't think I can stop people from being ignorant about Drivechain. But I > can at least allow the Drivechain-knowledgable to identify each other. > > So here below, I present a little "quiz". If you can answer all of these > questions, then you basically understand Dri