Re: [bitcoin-dev] [bitcoin-core-dev] Bitcoin Core 0.18.0 released

Two addenda from me: * Beginning with Bitcoin Core 0.18.0, Windows builds for 32-bit Windows will no longer be provided. Please let us know if and why you can not use the 64-bit build. * There is an experimental Bitcoin Core snap package in the snap store. There should be a "track" for the latest

Re: [bitcoin-dev] Adding xpub field to PSBT to make multisig more secure

Hi Stepan, I think that this would be a good extension. Just for clairty, by xpub, do you mean the extended serialization format defined in BIP 32 or the Base58 check encoded string of that serialization? Andrew On 4/26/19 11:21 AM, Stepan Snigirev via bitcoin-dev wrote: > Hi list, > > I was

[bitcoin-dev] Bitcoin Core 0.18.0 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Bitcoin Core version 0.18.0 is now available from: or through bittorrent:

Re: [bitcoin-dev] IsStandard

Thanks for the answer, indeed for the redeem script and someone attempting a 0/1 of 3, good example So to summarize everything is standard as long as it matches P2PKH, P2SH, P2WPKH or P2WSH , the redeem scripts for the sha bounties are in op_return Still the case of bch is unclear (it's related

Re: [bitcoin-dev] IsStandard

There is not a single document that describes what is standard and what is not. Transaction relay policy (including minimum relay fees) may change over time, across different implementations or different versions of the same implementation. Generally you can assume that commonly used scripts that

Re: [bitcoin-dev] IsStandard

On Saturday 27 April 2019 10:37:29 Aymeric Vitte via bitcoin-dev wrote: > Maybe trivial question but asking here because I can't find anything > clear (or updated) about it: is somewhere explained in details what txs > are considered standard and non standard today without having to read > the

Re: [bitcoin-dev] IsStandard

Good morning Aymeric, Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ On Tuesday, April 30, 2019 5:43 PM, Aymeric Vitte wrote: > I must badly explain my point (or just wondering things that do not > exist finally), the question is indeed whether nodes will relay non >

Re: [bitcoin-dev] IsStandard

I must badly explain my point (or just wondering things that do not exist finally), the question is indeed whether nodes will relay non usual transactions or not and how to know what they will accept or not: - my modified multisig 2 of 3: I did put OP_2 out of the usual redeem script, the redeem

Re: [bitcoin-dev] IsStandard

Good morning Aymeric, Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ On Monday, April 29, 2019 5:30 PM, Aymeric Vitte wrote: > ZmnSCPxj, OK, but you can put whatever you like in the different > standard output script you mention (my example below whether legacy or >

Re: [bitcoin-dev] IsStandard

Good morning Aymeric, Different versions may consider different output scripts standard. Your rule of thumb, post-SegWit, should be: * If not P2PKH or P2WPKH, then wrap it in a P2SH or P2WSH. There are more standard outputs accepted, but you can be reasonably sure that P2PKH, P2WPKH, P2SH,

Re: [bitcoin-dev] IsStandard

ZmnSCPxj, OK, but you can put whatever you like in the different standard output script you mention (my example below whether legacy or segwit) Luke, I am still confused or missing something, from your answer I understand that everything is accepted, so if we take the past example of bch coins

Re: [bitcoin-core-dev] Bitcoin Core 0.18.0 released

Two addenda from me: * Beginning with Bitcoin Core 0.18.0, Windows builds for 32-bit Windows will no longer be provided. Please let us know if and why you can not use the 64-bit build. * There is an experimental Bitcoin Core snap package in the snap store. There should be a "track" for the latest