Re: [bitcoin-dev] how to disable segwit in my build?

2017-07-29 Thread Troy Benjegerdes via bitcoin-dev
On Thu, Jul 13, 2017 at 01:04:19AM +, Gregory Maxwell via bitcoin-dev wrote: > On Wed, Jul 12, 2017 at 6:17 AM, Dan Libby via bitcoin-dev > wrote: > > Hi! > > > > Up to now, I have purposefully been running bitcoin releases prior to > > 0.13.1 as a way

Re: [bitcoin-dev] how to disable segwit in my build?

2017-07-14 Thread Hampus Sjöberg via bitcoin-dev
> sounds good, though I'm unclear on how exactly to achieve (2) given that any party I have ever transacted with (or otherwise knows an address of mine) can send me coins at any time. So it seems the only possible way to be certain is to run a node that has never published an address to a 3rd

Re: [bitcoin-dev] how to disable segwit in my build?

2017-07-14 Thread Tier Nolan via bitcoin-dev
On Fri, Jul 14, 2017 at 12:20 AM, Dan Libby via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: > On 07/13/2017 03:50 PM, Hampus Sjöberg wrote: > > 2. Avoid any chain of transaction that contains a SegWit transaction > > sounds good, though I'm unclear on how exactly to achieve (2)

Re: [bitcoin-dev] how to disable segwit in my build?

2017-07-13 Thread Lucas Clemente Vella via bitcoin-dev
2017-07-13 18:58 GMT-03:00 Dan Libby via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org>: > If I understand correctly, my node will accept the incoming tx inputs > but obviously will not perform any segwit related validation, thus those > inputs are not fully validated. I don't yet

Re: [bitcoin-dev] how to disable segwit in my build?

2017-07-13 Thread Dan Libby via bitcoin-dev
Hampus, thanks for the explanation! On 07/13/2017 03:50 PM, Hampus Sjöberg wrote: > Yes. > So you have two choices to be fully secure: > 1. Validate using the new rules of the network (in other words, run a > SegWit node) > 2. Avoid any chain of transaction that contains a SegWit transaction

Re: [bitcoin-dev] how to disable segwit in my build?

2017-07-13 Thread Hampus Sjöberg via bitcoin-dev
> I would like to understand it a bit better, as I think it applies equally to any pre-segwit node, yes? So let's say I am running 0.13.0 and someone sends me bitcoins to a P2PKH address, but that person previously received them to a P2WPKH address. Yes, this applies to all non-SegWit nodes. >

Re: [bitcoin-dev] how to disable segwit in my build?

2017-07-13 Thread Dan Libby via bitcoin-dev
On 07/13/2017 09:35 AM, Jameson Lopp wrote: > > > On Thu, Jul 13, 2017 at 12:19 PM, Dan Libby via bitcoin-dev > > wrote: > > On 07/13/2017 06:39 AM, Hampus Sjöberg via bitcoin-dev wrote: > >> I

Re: [bitcoin-dev] how to disable segwit in my build?

2017-07-13 Thread Jameson Lopp via bitcoin-dev
On Thu, Jul 13, 2017 at 12:19 PM, Dan Libby via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: > On 07/13/2017 06:39 AM, Hampus Sjöberg via bitcoin-dev wrote: > >> I believe that a good reason not to wish your node to be segwit > > compliant is to avoid having to deal with the extra

Re: [bitcoin-dev] how to disable segwit in my build?

2017-07-13 Thread Dan Libby via bitcoin-dev
On 07/13/2017 06:39 AM, Hampus Sjöberg via bitcoin-dev wrote: >> I believe that a good reason not to wish your node to be segwit > compliant is to avoid having to deal with the extra bandwidth that > segwit could require. Running a 0.14.2 node means being ok with >1MB > blocks, in case segwit is

Re: [bitcoin-dev] how to disable segwit in my build?

2017-07-13 Thread Dan Libby via bitcoin-dev
On 07/12/2017 06:48 PM, Anthony Towns via bitcoin-dev wrote: > I think that terminology isn't quite precise. I think your options are: > > - if you're a miner or run a mining pool, you can *signal* (or not >signal) support for segwit activation; you do this by controlling >the block

Re: [bitcoin-dev] how to disable segwit in my build?

2017-07-13 Thread Hampus Sjöberg via bitcoin-dev
> I believe that a good reason not to wish your node to be segwit compliant is to avoid having to deal with the extra bandwidth that segwit could require. Running a 0.14.2 node means being ok with >1MB blocks, in case segwit is activated and widely used. Users not interested in segwit

Re: [bitcoin-dev] how to disable segwit in my build?

2017-07-13 Thread Federico Tenga via bitcoin-dev
On 13 July 2017 at 03:04, Gregory Maxwell via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: > > Can you explain why you wish to do this? It should have absolutely no > adverse impact on you-- if you don't use segwit, you don't use it-- it > may be the case that there is some

Re: [bitcoin-dev] how to disable segwit in my build?

2017-07-12 Thread Anthony Towns via bitcoin-dev
On Tue, Jul 11, 2017 at 11:17:24PM -0700, Dan Libby via bitcoin-dev wrote: > At this time, I would like to have some of the more recent features, but > without the possibility that my node will activate segwit, until I > choose to. I think that terminology isn't quite precise. I think your

Re: [bitcoin-dev] how to disable segwit in my build?

2017-07-12 Thread Gregory Maxwell via bitcoin-dev
On Wed, Jul 12, 2017 at 6:17 AM, Dan Libby via bitcoin-dev wrote: > Hi! > > Up to now, I have purposefully been running bitcoin releases prior to > 0.13.1 as a way to avoid the (possible) segwit activation, at least > until such time as I personally am

[bitcoin-dev] how to disable segwit in my build?

2017-07-12 Thread Dan Libby via bitcoin-dev
Hi! Up to now, I have purposefully been running bitcoin releases prior to 0.13.1 as a way to avoid the (possible) segwit activation, at least until such time as I personally am comfortable with it. At this time, I would like to have some of the more recent features, but without the possibility