Topic: ToominCoin aka "Bitcoin_Classic" #R3KT - page 102. (Read 157137 times)

From what I've seen so far none of them have adequate experience when it comes to technology. Most of the time they are talking nonsense or just hanging on the threads of propaganda that they've heard somewhere. It is quite unfortunate that the community became this toxic.

ToominCoin officially REKT. 

So this is ~90% of hash power against a contentious hardfork.Awesome!
That's a clear statement I would say.

Well , I am glad this is over and we can move on to improving the bitcoin ecosystem?

https://medium.com/@bitcoinroundtable/a-call-for-consensus-d96d5560d8d6#.3219xm7af

So "grâce period" is the new buzzword in Town?
 Why all the proposals always omit attackers and selfish behaviors?

lets look at it from a different angle, which do you think is more logical

target criteria based on just 7 days(1000 blocks) that triggers a change in the future.. and then a 28 day grace period for laggers who havnt reacted.. to react
or target criteria based on 70 days(10,000 blocks) that triggers a change in the future.. and then a XX day grace period for laggers who havnt reacted.. to react

to me, people who are running true full nodes are already devoted to bitcoin. Enough to be watching the network and notice changes way before the trigger is met.
EG if they know the trigger is 750 out of 1000. then obvious maths suggests:
seeing 3 out of 6 in any hour means people can start thinking its a possibility because 50% is running the update.
seeing 4 out of 6 in any hour means people should really start thinking its a possibility because 66% is running the update.
seeing 5 out of 6 in any hour means people really need to accept that its a possibility because 83% is running the update.

so my first thought was without even having to wait for the 7th day(1000th block), they could start reacting. even from day 1 if the pattern emerges. rather than waiting for the trigger to happen on day 7 and then panicking..

but then i thought that basing it on just 7 days of data (1000 blocks) is too soon and is going to be a shock, even with a larger grace period.. as people may not be monitoring it every day or the short period can be abused by things like a sybil attack, and people would end up debating. denying it, ignoring it rather then preparing for the grace period to lapse

whereas if its based on 70 days(10,000 blocks)..followed by a grace period.. then people have over 2 months to randomly monitor the network and if they start noticing a pattern arising(before trigger date) implying that the trigger might be hit, then people can react and prepare sooner, giving them more time to react before the 10,000th block is hit and then the grace period is just a grace period.

i think its foolish for people to wait until the trigger occurs after just 7 days(1000 blocks) and then go into panic mode thinking they were not given any notice to code a change to be compatible.

i think people need to start reacting and know that at 50%, the possibility is there.. and thus maybe start thinking about coding a compatible update. by 66% have the code ready to release and then be using it by 75% or during the grace period.
 
even if this 50%-75% pattern is noticed in the first 100 blocks. knowing there is still 69 days of data to solidify the trigger into activating, it would give people more peace and time to react, code and release an update.. instead of ignoring it or sitting on their hands until trigger day, and pretend to be shocked.

so.. my main question, would you say maybe something like
10,000 blocks and maybe 28 days grace period?
10,000 blocks and maybe days grace period?

to you what would be your perfect ratio of monitoring the data live to prepare and react. and then a grace period to sort out the lagger minority that have not reacted(remaining 25%)

I've wondered if any of them have any experience with large scale production systems at all-- esp any that must have multi-vendor interop.  It's unbelievable.

if numbskulls who havnt upgraded see that there are 50% then they better get started thinking about upgrading before 75%..  if at 75% they havnt got their act together, theres still 28day cool-off period.

after the 28 day period. there is NOTHING!!! forcing miner to make blocks over 1mb.. nothing at all.. the 2000000 limit is a buffer and it can sit there forever if no miner decides its worth risking moving forward.

infact even with the setting inplace, most miners wont risk it as the orphan rate would be a factor as there is still 25% chance of old miners reaching blockheigh and orphaning off the bigger blocks because the old miners versions dont contain them.
so miners even with the rule set wont risk it until more consensus is reached..

and that means that even with 1 weeks accumulation of blocks to get the 750 out of 1000 blocks (1000 blocks being 7 days). and then the 28 day cool off period after that.. if people haven't moved forward.. then thats their fault for sticking to minority..

if anything shoud change about the roll out period... rather than a 28 day cooling off period being extended. which is just a gesture of goodwill for any laggers.. a more plausible thing would be 7500 blocks out of 10,000 (70 days) to ensure that miners are ready and that its not just a 1 week worth of sybil attack.. thats what i think would be more logical

It seems like even Garzik doesn't agree with the '28 days' nonsense.
I've told the 'forkers' this several times.

I can't remember saying nodes doesn't matter, they're still in favour of Core though. But if nobody mines with Classic it won't matter even if Classic were to have the majority of nodes. Classic was released today so we'll see in the coming weeks if any of the miners will adopt it.

Apparently the number of nodes is only a irrelevant metric when it is in favor of Core. As soon as the number of 'altcoin nodes' start going up it becomes very accurate and relevant. 

'REKT' since day one.

That place is horrible.

so a hundred desperate VC-funded businesses almost out of runway, and a handful of disaffected zealots who hate themselves because they can't code, running 6 nodes each ... all on the same 3 silicon valley data-centers?

https://coin.dance/nodes

So is Classic actually REKT or are the 2 sides still FUDDING each other without a winner either way?

You're hanging out in the mental ward over at bitco.in forums, you've reached a new level of crazy.

Your attempt to insinuate that the the parent was compromised is literally straight out of the CBGB public communication subversion handbook!

Seriously, this whole thread perfectly characterises everything that is wrong right now. nullc should know better. so should I, topping this bile fest is probably ill advised, but at least I'm not a 'core dev'.

Real people with real opinions just aren't this level of crazy.

Ah, now we see the violence inherent in the system!
TL;DR of everything: https://youtu.be/fxGqcCeV3qk?t=59

Let me just add that there are downvote robots on /r/btc and elsewhere.