Pages:
Author

Topic: The Barry Silbert segwit2x agreement with >80% miner support. - page 84. (Read 120014 times)

sr. member
Activity: 277
Merit: 250
I'm very dissapointed of BitFury starting to collaborate with obvious Bitcoin foes like CIA snitch Gavin Andressen or altcoin cheer girl Roger Ver. We should procede with UASF
legendary
Activity: 1372
Merit: 1252
So it is O.K. for big mining companies to make deals without asking the community's opinion behind the closed doors but it is not O.K. to change the PoW algo to prevent these kind of situations.

I didn't sign up for a centralized piece of shit coin and a toy for big companies.

We must drain the swamp.

What are you specifically proposing?

We change the PoW algo to something else... then what? For how long is the hashrate decentralized until china, which is positioned with a perpetual advantage due cheap electricity and cheap human labor, can develop again specialized machines for cheap and run them for cheap and keep staking more and more machines?

You have to think about what you are going to do long term with a PoW change. Changing to some other algo is useless, we need something clever to avoid future miner centralization if we have to resort to that.
hero member
Activity: 1092
Merit: 552
Retired IRCX God
So it is O.K. for big mining companies to make deals without asking the community's opinion behind the closed doors but it is not O.K. to change the PoW algo prevent these kind of situations.

I didn't sign up for a centralized piece of shit coin and a toy for big companies.

We must drain the swamp.
You're right, it's bad for companies (like Bitcoin Core) to make deals/decisions without asking the community's opinion behind the closed doors.  Cheesy It's almost entertaining to watch you ignore the fact that everything you say applies to the group you seem to be a fanboy of.  Undecided
legendary
Activity: 3276
Merit: 2442
So it is O.K. for big mining companies to make deals without asking the community's opinion behind the closed doors but it is not O.K. to change the PoW algo to prevent these kind of situations.

I didn't sign up for a centralized piece of shit coin and a toy for big companies.

We must drain the swamp.
sr. member
Activity: 286
Merit: 251
Extension Blocks <3 Rootstock <3
Does anyone know if ASICBoost is addressed?
Will the segwit be a HF Segwit without OP_RETURN commitment?
So - will covert ASICBoost continue to work as is?

I'm not conviced this is a fair compromise.
hero member
Activity: 1176
Merit: 501
Has been any response from Core already? I don´t understand the euphoria of Charlie Shrem in his messages a few hours ago. With what has been announced so far, the solution to the conflict is still far away. It´s true that it´s a small approach when compared to previous positions but I don´t think that bitcoin can advance without taking Core into account. Highly announcing this agreement, given its terms, doesn´t make sense.
hero member
Activity: 1092
Merit: 552
Retired IRCX God
...Everything else is just human ego.
Devs? Ego?  Surely not!  Tongue

Anyone else see a Bitcoin Classic on the horizon?  Cry
sr. member
Activity: 602
Merit: 250
Anyone at NYC Consensus 2017 today ?

They should make the segwit announcement today or tomorrow, no ?
hero member
Activity: 770
Merit: 629
As far as I understand the new proposition, it has two advantages that I can see.  It can avoid a huge clusterfuck because it is a hard fork, so that once it is set up, it will split cleanly and nicely in two prongs that cannot unite any more.   As such, the immense clusterfuck that could happen if a minority soft fork splits off, making two coins, and taking over (becoming majority), orphaning the original one after a month or so, erasing all transactions on one prong in a go, can be avoided.

But if I understand correctly, this new proposition has a "power amplifier" built into it, even if initially there was a 50/50 split in hash rate on the two prongs.  Indeed, in that case, both prongs (both bitcoins, the original one and the new one) will only make blocks at half rate, so every 20 minutes.   However, the new one, having standard blocks of 2 MB, can accommodate just as many transactions as the old bitcoin did before the split, while the original chain has now half transaction rate.  

If the two coins are listed on exchanges, people will curse the old chain, that is now totally asphyxiated at HALF the current transaction rate (a 1 MB every 20 minutes !), while the new chain with same block rate can continue to work like old bitcoin used to.  This will give an edge to the new chain for users.

It can also have the opposite effect, that people do not even succeed in putting their old chain coins on an exchange to sell them and are hence constrained to hold them, thus increasing the market value of the old chain.  This could be even a danger if the split is too favourable to the new chain, and the split is 20% - 80%, and exchanges list both of them.   The old chain will only have about a block every hour (imagine !!) while the new one will essentially double bitcoin's transaction capacity.   But people will not be able to sell their old coins, so maybe the few of them on exchanges will explode in price, reversing the hash rate distribution.

Normally, once both chains are active and separated, the market will determine the market cap split, and the miners will follow with their hash rate.  

If the new chain doesn't asphyxiate entirely the old chain, two bitcoin will emerge, but at least, the two coins will never mingle again, and all transactions on both chains will continue to exist.
legendary
Activity: 1946
Merit: 1055
I think it's ok. First they activate SegWit. Then everyone will see that hardfork is redundant. But if some fools try to hard fork after SW they will end up with alt on their hands.


Yes this is exactly why the 2Mb folks want the block size increase after SegWit activation but before the lock.

So is it an attempt to stop the User activated fork getting traction ?

yes, because the period from august 2017 to november 2017 is the enforced period for Segwit ... not the LOCK period.
https://github.com/bitcoin/bips/blob/master/bip-0148.mediawiki

so Segwit2Mb is a trap.
they want introduce the 2Mb before SegWit LOCK.

So the folks who want 2Mb don't trust the SegWit people not to break away after SegWit is locked and block a later block size increase?

Sounds understandable given the emotionalism on this issue. It would be very disruptive to activate SegWit and then deactivate it before LOCK. Seems unlikely the miners would do this. It seems far more likely that the SegWit folks would increase their opposition to a block size increase to 2 Mb once they already have what they want.

I am not understanding why this is not a reasonable roadmap forward.


This is an issue that is not going to have a "winner" it can only be solved by compromise and consensus.
legendary
Activity: 2912
Merit: 1068
WOLF.BET - Provably Fair Crypto Casino
I don't like all this games, it looks like some kind of bi war where everyone will loose at the end. Is the final goal of all of this for someone to control the Bitcoin and to become centralized? If this continues to go this way it will not end well, something constructive should be done very fast.
sr. member
Activity: 277
Merit: 250
I think it's ok. First they activate SegWit. Then everyone will see that hardfork is redundant. But if some fools try to hard fork after SW they will end up with alt on their hands.
legendary
Activity: 1946
Merit: 1055

Nothing's being forced until someone pulls the trigger.  If you set yourself down the path of activating UASF, you're pulling the trigger and forcing their hand.  If they set themselves down the path of activating a non-consensual hard fork, they're pulling the trigger and forcing your hand.  No one has pulled the trigger yet, so simmer down and start negotiating before things escalate any further.

What is it you don't understand? Devs set the rules.

Pffft.  Not even close.  Devs can only propose rules, consensus sets them.  Maybe you're thinking of Ripple or some other closed-source shitcoin based on centralised development and the users having no say in the code they choose to run.  Like so many people out there, you're willing to sacrifice the freedom of choice you've been given and surrender yourself to one centralised authority because you're scared of another one taking over.

The time of the cypherpunks was all too short, now only the cypherpussies remain, pleading for someone in power to trust with their hopes and dreams.  Pathetic.   Cry

+1

I strongly agree with the arguments above.

What all parties need to be looking at is not who is in "control" or what signal bit is used but does the solution

1) Allow for long term scaling
2) Maintain consensus

Everything else is just human ego.
legendary
Activity: 3066
Merit: 1188
Bitbay now rallying on the disagreement over the Barry Silbert "agreement".

Dash also taking off.

Toys & prams in short supply.

yeah...that agreement is a piece of shit. just another attempt at a delaying tactic.

copper member
Activity: 2324
Merit: 1348
hero member
Activity: 574
Merit: 502
waiting to explode
Watching this thread
legendary
Activity: 1204
Merit: 1028
Who is going to develop for them?

Where there any developers to discuss this "agreement"?
The only group amongst them that has any software developers to speak of is RSK. I don't believe any actual bitcoin developers had anything to do with it. The rest are all mining companies or services which have no real history of bitcoin core development.

Looks like Sergio Damian or whatever he is called, has been bribed by the PBOC money. Anyway, he has been selling vaporware for ages, he's incompetent compared to Core devs.

If this nonsense goes through, then Core must officially support UASF. What else is there? it's not like there are many other chances left.

It's either that, or Core officially supporting a 2MB increase, even tho doing a hardfork for only 1MB increase is pretty dumb, let alone rushed in 4 months, since I would like to see further tech improvements that would come with a properly planned HF, but we are running out of time, Chinacoin is coming.
legendary
Activity: 3948
Merit: 3191
Leave no FUD unchallenged
What is it you don't understand? Devs set the rules.

Pffft.  Not even close.  Devs can only propose rules, consensus sets them.  Maybe you're thinking of Ripple or some other closed-source shitcoin based on centralised development and the users having no say in the code they choose to run.  Like so many people out there, you're willing to sacrifice the freedom of choice you've been given and surrender yourself to one centralised authority because you're scared of another one taking over.

The time of the cypherpunks was all too short, now only the cypherpussies remain, pleading for someone in power to trust with their hopes and dreams.  Pathetic.   Cry
hero member
Activity: 1792
Merit: 534
Leading Crypto Sports Betting & Casino Platform
The core Devs were too late to act...
ASIC Mining = Centralized business
...
There seems to be a confused irony in your statements. It seems that you think that a decentralized Bitcoin should remain centralized around the devs of a specific wallet. Or am I reading that all wrong?

What is it you don't understand? Devs set the rules. If the rules are broken, the whole system becomes broken. This system is broken for what it is and devs should fix it.

Everything has a starting point. Satoshi created bitcoin and he was in the center of the bitcoin's blockchain system for a while. Means bitcoin was centralized around Satoshi but he didn't like it so he tried to make it decentralized with the support of the people, us. Cool ASIC companies hacked the code, he failed.

Now the core devs can accomplish what satoshi couldn't. They can set new rules and save bitcoin from being centralized.
...No.  If devs could just change anything that they wanted to, they could completely destroy Bitcoin at any point.  That's the whole reason that we have consensus systems like hashrate.
hero member
Activity: 770
Merit: 629
Bitcoin was meant to be mined but never thought about times like now, miners being separated from users/supporters. in the eyes of code, miners are users and users are miners/community.

One always forgets Satoshi's understanding of this from 2008:

http://satoshi.nakamotoinstitute.org/emails/cryptography/2/

Quote
At first, most users would run network nodes, but as the
network grows beyond a certain point, it would be left more and more to
specialists with server farms of specialized hardware
. A server farm would
only need to have one node on the network and the rest of the LAN connects with
that one node.

This is not to "quote authority", it is simply to show you that to its creator, this was understood, that one would separate users and miners (the "specialists with server farms of specialized hardware").

That said, Satoshi erroneously thought that there wouldn't be pools, and that there would be more of these "specialists" than the handfull right now.  But the idea that one would develop ASICS "specialized hardware", and that this would result in an industry of "specialists" was understood by him.  In other words, one cannot "discover this with horror" right now.  It was understood as part of the logical consequence of his design.  Maybe not desired, but at least logically understood.

Pages:
Jump to: