Re: [bitcoin-dev] Flag day activation of segwit

2017-03-26 Thread praxeology_guy via bitcoin-dev
.. if they are still manipulated now then its time for us to give up on helping them see the light and instead let them learn the hard way. Cheers, Praxeology Guy Original Message ---- Subject: Re: [bitcoin-dev] Flag day activation of segwit Local Time: March 13, 2017 5:18 PM UTC Time:

Re: [bitcoin-dev] Flag day activation of segwit

2017-03-13 Thread Nick ODell via bitcoin-dev
>time >= 1506816000 && time <= 1510704000 && !IsWitnessEnabled() This has a different start time from the first post. >if (pindex->GetMedianTimePast() >= 1538352000 && pindex->GetMedianTimePast() <= 1510704000 ... Thanks, --Nick On Mon, Mar 13, 2017 at 4:36 AM, shaolinfry via bitcoin-dev <

Re: [bitcoin-dev] Flag day activation of segwit

2017-03-13 Thread shaolinfry via bitcoin-dev
endeavour, which is the basis of the strong assumption of Bitcoin that PoW/revenue incentives will keep miners honest. If that assumption is broken, Bitcoin has bigger problems. Original Message Subject: Re: [bitcoin-dev] Flag day activation of segwit From: nickodell The problem

Re: [bitcoin-dev] Flag day activation of segwit

2017-03-13 Thread shaolinfry via bitcoin-dev
From: l...@dashjr.org On Sunday, March 12, 2017 3:50:27 PM shaolinfry via bitcoin-dev wrote: > // mandatory segwit activation between Oct 1st 2017 and Nov 15th 2017 > inclusive if (pindex->GetMedianTimePast() >= 1538352000 && > pindex->GetMedianTimePast() <= 1510704000 && >

Re: [bitcoin-dev] Flag day activation of segwit

2017-03-13 Thread David Vorick via bitcoin-dev
That's simply a 51% attack choosing to censor transactions. We could do that today, ban all transactions that aren't approved by the PBoC. You respond to that with a PoW hardfork, or by finding some way to prop up / subsidize non-censorship miners. On Mar 13, 2017 5:59 AM, "Nick ODell via

Re: [bitcoin-dev] Flag day activation of segwit

2017-03-12 Thread Nick ODell via bitcoin-dev
The problem with modifying Bitcoin to work around community norms is that it's a two-way street. Other people can do it too. Let me propose a counter-fork, or a "Double UASF." This is also a BIP9 fork, and it uses, say, bit 2. starttime is 1489449600, and the end time is 1506812400. It enforces

Re: [bitcoin-dev] Flag day activation of segwit

2017-03-12 Thread Luke Dashjr via bitcoin-dev
On Sunday, March 12, 2017 3:50:27 PM shaolinfry via bitcoin-dev wrote: > // mandatory segwit activation between Oct 1st 2017 and Nov 15th 2017 > inclusive if (pindex->GetMedianTimePast() >= 1538352000 && > pindex->GetMedianTimePast() <= 1510704000 && > !IsWitnessEnabled(pindex->pprev,

Re: [bitcoin-dev] Flag day activation of segwit

2017-03-12 Thread shaolinfry via bitcoin-dev
Before setting a flag day, I think we should get written cooperation agreements from the largest economic players in Bitcoin. This would include: There isn't a flag day to set. If the major economic organs like exchanges run the BIP, non-signalling miners simply wont get paid (starting October

[bitcoin-dev] Flag day activation of segwit

2017-03-12 Thread shaolinfry via bitcoin-dev
I recently posted about so called "user activated soft forks" and received a lot of feedback. Much of this was how such methodologies could be applied to segwit which appears to have fallen under the miner veto category I explained in my original proposal, where there is apparently a lot of