Re: [bitcoin-dev] 32-byte public keys in Schnorr and Taproot

On Fri, Aug 9, 2019 at 11:17 AM Pieter Wuille via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: > if we're going to change things, it's perhaps best to do it as cleanly as > possible and also drop that byte. > I personally lean toward just dropping the byte. I like the simplicity

Re: [bitcoin-dev] Taproot proposal

On Fri, 9 Aug 2019 at 08:02, Elichai Turkel via bitcoin-dev wrote: > > Hi, Since the idea of implicitly even pubkeys has potentially more general implications, I've started a separate thread [1] about that idea. > I want to add to John Newbery's suggestion of using implicit even/odd only >

[bitcoin-dev] 32-byte public keys in Schnorr and Taproot

Hello all, It has been suggested [1] to drop the Y oddness bit in the witness program for Taproot outputs. This seems like a worthwhile change, as: * The bit doesn't actually contribute to security. * It avoids Taproot outputs from being more expensive to create than v0 P2WSH. * It doesn't

Re: [bitcoin-dev] Taproot proposal

Hi, I want to add to John Newbery's suggestion of using implicit even/odd only public keys and tweaked public keys in taproot and suggest the following: If everything is implicit then the only reason for the first byte of the control block(`c[0]`) is the tapscript leaf version. I suggest that

Re: [bitcoin-dev] OP_LOOKUP_OUTPUT proposal

Good morning Haoyu LIN et al., > We have investigated this problem in very detail. We analysed how profitable > the arbitrage can be given the default timelock setting (24/48 hrs). Our > result shows that the profit can be approximately 1% ~ 2.3%, which is > non-negligible compared with 0.3%

[bitcoin-dev] Bitcoin Core 0.18.1 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Bitcoin Core version 0.18.1 is now available from: Or through BitTorrent:

[bitcoin-core-dev] Bitcoin Core 0.18.1 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Bitcoin Core version 0.18.1 is now available from: Or through BitTorrent: