Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ethereum Core Devs Meeting 46 Agenda #56

Closed
lrettig opened this issue Sep 4, 2018 · 73 comments
Closed

Ethereum Core Devs Meeting 46 Agenda #56

lrettig opened this issue Sep 4, 2018 · 73 comments

Comments

@lrettig
Copy link
Contributor

lrettig commented Sep 4, 2018

Ethereum Core Devs Meeting 46 Agenda

Meeting Date/Time: Friday 14 Sept 2018 at 14:00 UTC

Meeting Duration 1.5 hours

YouTube Live Stream Link

Livepeer Stream Link

Constantinople Progress

Agenda

  1. Testing
  2. Client Updates
  3. Research Updates
  4. Constantinople
    a. Client progress.
    b. Ropsten block number.
    c. Can we do it before Devcon?

Time-allowing:

  1. EIP-1380: Reduced gas cost for call to self
  2. EIP-1108: Reduce alt_bn128 precompile gas costs
  3. EIP-1057 (ProgPoW) and EIP-1355 (Ethash1a)
@jacqueswww
Copy link

jacqueswww commented Sep 4, 2018

Hi There! I am eager to discuss reducing the gas fee on self-calls (private/internal calls). EIP-1380 https://github.com/ethereum/EIPs/pull/1380/files.

@chfast
Copy link
Member

chfast commented Sep 5, 2018

I don't mind having it this week, but we agreed to have it one week later.

@5chdn
Copy link
Contributor

5chdn commented Sep 5, 2018

Please make it Sept 14 👍

@lrettig
Copy link
Contributor Author

lrettig commented Sep 5, 2018

Hi guys, if it was already agreed that the next meeting would be next week, no worries. My fault for being out of the loop thanks to burning man :) I pinged @Souptacular to check but I think he's in transit to Berlin. Fixed!

@MoneroCrusher
Copy link

MoneroCrusher commented Sep 8, 2018

In my opinion issuance reduction & ASIC fork-off has to happen at the same time. With a issuance reduction only you are only accomodating 'investors' who have a very biased view and only want to make money by reducing inflation, it won't work anyway. As a bad side-effect the network will also experience an extreme shift towards hashrate centralization.
What is far more important is utility tokens & projects wanting to build their platform on the Ethereum network to have a stable underlying protocol without the risk of a centralized network and its implications.

Potential industries will only adopt or even consider their projects when they know the underlying protocol - Ethereum - is absolutely secure as a disruption (i.e. 51% attack, censoring of certain transactions, just imagine one industry trying to sabotage ERC20 token transaction of a competitor for a huge shipment in the shipping industry) could cause huge problems & uncertainty. The real & ultimate value in Ethereum lies in the utility tokens & smart contracts, not in reducing inflation from i.e. 7% to 4.5%. That's just gimmick & fairy dust and a desperate attempt from 'investors' to easen their bags.

Behold, miners are not less greedy (actually they are supposed to be greedy in this game theoretical protocol) but unlike 'investors' they fulfill a crucial function and bring actual value: security of the network.
So I'd advise you to reconsider your last stance of making a issuance-only without a ASIC-fork-off.

In the meantime ProgPOW is already live on a mainnet. Check out Bitcoin Interest (no endorsement). The block height for the fork was reached today and they're officially & successfully running ProgPOW. You can use that as a 'testnet' if you will & see that the algorithm is flawless and works as intended.
Now it's up to you to lead this project into a success and it will only happen if you uphold the core value of the protocol: smart contracts & decentralization (AKA security).

Edit
as a bonus: Investors will most likely even make a bigger return that way, in the longer term

@sinabl
Copy link

sinabl commented Sep 11, 2018

I’m in full agreement with what Monerocrusher has written. In addition, centralization by miners will force the Eth team to ultimately cater more to their demands than the original neutral vision that It was founded upon. Let’s have a serious discussion on this topic in the meeting, There is absolutely nothing wrong with performing another fork in November if its decided in the meeting to move forward with ProgPOW

@MoneroCrusher
Copy link

MoneroCrusher commented Sep 12, 2018

Absolutely agree. I don't want to imagine the propaganda that will be thrown around by the big ASIC manufacturers when ETH finally switches to PoS.
Their hardware value & investments will go to zero, while GPU's value doesn't (it can be used for a lot of other stuff and also other coins).
Therefore you will have a smoother transition to PoS if you keep GPU miners in the game.

If you embrace ASICs now, miners will slowly adapt & get ASICs themselves and it will be even harder to get consensus and the community split will be more drastic.

It is absolutely critical to form an opinion about ASICs fast and clearly communicate what you will do about it. It's a big problem and I feel like the devs don't even fully realize it yet.

@Nmining
Copy link

Nmining commented Sep 12, 2018

I´m afraid there is already wavering in networks ,and miners are already switching coins. Eth value is getting very low(173usd) . https://ethermine.org/statistics. Moving to Progpow asap should at least give more hope for gpu mining in Eth.

@5chdn
Copy link
Contributor

5chdn commented Sep 12, 2018

Don't want to rush things, but regarding 4) Constantinople:

  • Shall we discuss a block number for Ropsten? (Would be nice.)
  • Is Constantinople still realistically happening before Devcon4? (Doubt that.)

Edit, also let's update Meta EIP-1013: ethereum/EIPs#1366

@ghost
Copy link

ghost commented Sep 12, 2018

@5chdn I think it is a right time to discuss a block number for ropsten network, most of the clients are now ready 👍

@ytrezq
Copy link

ytrezq commented Sep 12, 2018

@lrettig what about ᴇɪᴘ86 which was planned to be implemented in Metropolis ?

@MariusVanDerWijden
Copy link
Member

I would like to talk about EIP-1057 (ProgPoW) and EIP-1355 (Ethash1a)
to give a timeline what we, the ethminer community, think what has to happen before we use them. Forking the consensus algorithm isn't as easy as Bitcoin Interest makes it seem. All miners, nodes and even light clients such as wallets have to be updated in order to accommodate the new algorithm.

My main concern with ProgPoW is, that it was introduced by a company that specialize in providing special mining software. The open source community needs more time to analyse the characteristics of ProgPow before we can fork. Otherwise for profit companies could sell their mining software which outperforms the open source variants not by 3-5% (like now) but by way more (15+%). This would lead to a centralization of mining power again, controlled by the companies that provide the mining software.

Therefore, we propose with Ethash1a EIP-1355 a minor change in the algorithm which would buy us more time to analyse ProgPoW.

@MoneroCrusher
Copy link

@MariusVanDerWijden
Supporting this. Buys time and allows for everyone to look into a permanent solution. I would even suggest making a dedicated HF for the permanent ASIC resistant PoW solution. Why wait for Istanbul HF if the solution is found after i.e. 2-3 months?
No need to risk the big masses adopting to ASICs because then you've crossed the event horizon and you can't go back without a community split.
Luckily right now ASICs are exotic and only found in huge farms and manufacturer's farms. But they will try to get them out there in the wild as fast as possible once they see that there is a serious interest in forking their ASICs off.

@mdaria510
Copy link

If issuance is reduced without something done about ASICs then it will be completely counter productive. There are no hobbyist ASIC miners. All ASIC miners will ever do is sell everything they mine, and they will sell quickly. Not dealing with this problem now is making a deal with the devil and making it more difficult to change things further down the line.

Fact: Reducing issuance will put pressure on mining economics, such that the proportional of hash owned by ASICs must go up. At best you could argue that it might only go up a little bit, but it can only increase.

Supposedly the issuance reduction is to throw a bone to "investors" by cutting down on inflation. I know many "investors", and I have never met a single "investor" that said "the reason I'm selling ETH is because inflation is too high." No. The reason they're selling ETH is because the price is bleeding more and more, and they're losing faith. Average joe investor is very quickly shedding the belief that ETH is "the next bitcoin."

Cutting the inflation will obviously prop up the price to some degree - in the long run. But you can't make a case for it turning around the current bleeding. The total effect is going to be a few % at best, the kind of swing we see on a daily basis. The net effect of that change will take months to years to work out.

Cut off the GPU miners though, and you've dramatically increased selling pressure on day one after the fork because a much larger percent of mined ETH is going to be dumped by big centralized miners starting immediately after the fork, and it'll never stop. The block reward issuance will reduce the amount of ETH rewarded, but will not significantly reduce the amount of ETH sold by miners on the market. It might even increase it. There is a very real risk that it actually suppresses price in the short term. And at this stage, suppressing price in the short term is suppressing price in the long term.

At this early stage you should never lose sight of how immature the market is. "Investors" are not responding to fundamentals like inflation rate. "Investors" are not looking at supply. They're just not. Most don't even know what it is or where to find it. How else can you explain XLM and XRP having such huge valuations even though only a tiny fraction of the supply is even circulating, and the rest is held by centralized power? By fundamentals those tokens should be near worthless, but instead they're near the top of the pack. All "investors" are looking at is the price and the direction it's heading, and handing over mining to ASIC farms is going to increase selling pressure, suppress the price and drive new investors away.

I can't take the "there's no time to do anything" argument seriously if there's actually a simple way to brick current ASICs and at least buy some time. If you ignore the concerns of GPU miners, not only would you be biting the hand that fed you over the past few years, you're trading a friendly idealistic bunch with a large percentage of holders and true believers for ruthless corporations that will not hesitate to bite back. If you dismiss this threat today, by the time you casually get around to dealing with it you'll have a much steeper hill to climb with much more resistance from organized opponents that have no interest in Ethereum whatsoever beyond mining and selling it. They will stir up an order of magnitude more chaos and divisiveness than a bunch of random GPU miners could ever hope to. If the price of ETH actually does pump over the next few years, that's going to be worth billions to Bitmain and friends. If the price dumps, mining returns will drop so low (especially with the BR decrease) that they'll end up owning more and more of it of the mining rewards. In either case, they'll have incentive to battle devs at every step, especially when they're an entrenched power. They're not going to roll over without a fight like most GPU miners. They will not be casually dismissed, and they will derail every and any plan developers have that goes against their interests. You need to cut the cancer out before it grows and spreads. That's why ASIC resistance was a core tenet of Ethereum from the start right? Assuming you can handle this at your leisure is not a safe assumption. Ignore it at your peril.

I get that punting ASIC resistance to the next fork is the easy thing to do, and reducing inflation is the easy thing to do to increase price. But the easy thing to do is rarely the right thing to do, there will be a price to pay down the line for taking the easy way out today. Every plan the dev team has is in jeopardy if you hand over running the network to people who have zero interest in seeing those plans come to fruition.

@NoBey
Copy link

NoBey commented Sep 14, 2018

@mdaria510
The price of eth picks up again. The news of the production cut has changed the market, reducing the output of eth but not the revenue of gpu

@pdyraga
Copy link

pdyraga commented Sep 14, 2018

Hey, me or someone else from the team would like to join the meeting to discuss EIP-1108 on behalf of the Keep Network. We're happy to take lead on EIP updates and implementation across clients if an agreement can be reached.

@mdaria510
Copy link

mdaria510 commented Sep 14, 2018

@NoBey Wishful thinking is not a way to run a billion dollar blockchain. The news of the production cut already happened weeks ago. You already got your bump. Turns out people care a lot more about misinterpreting Vitalik’s tweets than fundamentals.

Difficulty is already down like 5% in the last week. GPU miners are already leaving. It’s one thing to cut rewards and ignore ASICs when the price is way up. Things have changed a lot since that decision was made, and for all we know ETH could be <$100 by October. At that point a block reward reduction would be a complete and total handover to big ASIC farms.

@winsvega
Copy link

I am ready to start all tests review (which is done before every hardfork)
This means all tests will be regenerated and a new version probably be added for most of the test cases (constantinople version)

the test we are pending to add:

more sstore tests
extcodehash tests
transition tests around the fork point
difficulty change tests (not blokchain format)
fuzztests integration in form of state tests

@lrettig
Copy link
Contributor Author

lrettig commented Sep 14, 2018

I added the requested topics to the agenda. Please note that we may not have time to get to all of them today; also, that I haven't been able to coordinate as closely with @Souptacular as usual given timezone differences and travel post-ETHBerlin, so I'll of course defer to his judgment regarding the agenda for today's call. @ytrezq my understanding of EIP-86 is that it was postponed due to the complexity of implementation and that it won't make it into Constantinople. I'll have to check the notes for more details on this but don't have time to do so before today's call.

@mhluongo
Copy link
Contributor

mhluongo commented Sep 14, 2018

I'd also be interested in a discussion of EIP-1109 if it's not been covered in a previous call @jbaylina, as its relevant to precompile gas reduction

Sorry, I see it was discussed- avoiding it means a restriction on aggregate BLS signatures, but I see the complexity was a concern.

@holiman
Copy link

holiman commented Sep 14, 2018

@ytrezq Epi 86 was considered, but eventually dropped, for a number of reasons. See the discusson the EIP PR for more context.

@Nmining
Copy link

Nmining commented Sep 14, 2018

Very little was happening with asic resistance in meeting. Pushing it 8 months and more forward.

@MoneroCrusher
Copy link

As expected, ASIC resistance request from community is blatantly ignored and they think they can easily get away with it. This will backfire, and if done properly, I will join the backfire with my hashpower.

Would anyone here support a 0% fee ETH pool representing the community as a signal to the devs and that will collectively show support for an ASIC resistant implementation in Constantinople (ProgPOW, EIP-1355, or another ASIC-resistant solution)? I don't know how to run a pool properly (and to protect it from DDoS attacks), if anyone does this I will for sure support it.

@MoneroCrusher
Copy link

MoneroCrusher commented Sep 15, 2018

BREAKING NEWS

It will become worse and worse, the "E9" is announced.
https://www.coindesk.com/a-new-line-of-powerful-asic-miners-is-coming-to-ethereum/
Just as I have said, when they fear their investment becoming worthless, which an Ethereum ASIC-fork-off would do, they will try ANYTHING to get ASICs to the masses.
Now what would you do if you have developped an ASIC 7.37x 62.2x more efficient than Bitmain's and you feel a sentiment becoming stronger in the Ethereum community (to fork ASICs off)? EXACTLY I would put out a PR right then and there saying I will release 7.37x 62.2x more efficient ASIC miners to the market in the beginning of the next year.
This way they can kill 2 birds with one stone:

  1. Put Bitmain, their competitor, under massive pressure, who will now sell their ASICs for throwaway prices, getting ASICs to the masses.
  2. Getting ASICs to the masses prevents Ethereum to fork because community doesn't want to when they own ASICs. This protects their investment.

Do you believe an ASIC 7.37x 62.2x more efficient than the E3 isn't long mining on the network?
If that doesn't make eth devs fork, we definitely know they have a hidden agenda and that [tinfoil hat on] maybe some of the devs are compromised by Bitmain/other ASIC manufacturers. This is a multi billion dollar market after all. [tinfoil hat off]

EDIT:
ASIC manufacturers are systemically exploiting and straight out scamming consumers out of their hard-earned money, the best case would be the new Zcash miners, let me lay it out for you:
In June a Zmaster A9 had a price of USD $10,000 and a break even time of around 70-80 days.
In July/August Zmaster A9 had a price of USD $5000-$6000 and a break even time of around 70-80 days
In September Zmaster A9 had a price of USD $3000-4000 and a break even time of around 70-80 days
Personal prediction:
In October-November Zmaster will be USD $1500-2000 and will have a break even time of around 70-80 days
Note: The ones who bought the Zmaster A9 in June still haven't broken even.

Do you see the pattern?
First they pre-mine, then they manufacture their second gen, then they sell their miners in a very shady way laid out above. Once they sold them they crush difficulty slowly and will soon release their "Zmaster A9 Grande" and will do the whole thing over. Each time milking the miner community, as many people are naive and buying into this shady scheme, blinded by break even time which mostly only last 2-3 weeks.

NVIDIA and AMD are not doing this because

  1. They are reputable decades old public companies that haven't their core business in crypto at all
  2. They would get sued immediately for running a fraudulent scheme

Conclusion:
If ETH doesn't fork ASICs off they are the enabler that allows small time miners to get scammed by ASIC manufacturers. I wonder how they can square that with their conscience.
Edit: https://www.youtube.com/watch?v=q52CepI1DD8
And this isn't just about Innosilicon, I already was interested in mining back in 2012/2013 and I did mine a little with my GPU and I wanted to get myself an ASIC. Back then you would order in march and get your product in November, by that time a more efficient ASIC would have been on the market and youd be delivered a couple thousand dollar brick to your doorstep. It's gotten better but the manufacturers will continue this until there's real world-wide competition. We got another couple years until that happens. So ASICs are bad as of this moment, not because ASICs are bad themselves, but without exception all manufacturers are. You can't even hold them accountable since all are in China.
So just fork it and be done with this discussion, it's obvious to everyone what has to be done. If Monero can do it I'm sure you can too.

At present, the company is still working on developing the product. Customers may begin receiving their miners in April 2019, according to the presentation.

If anyone believes that I'm sorry to tell you: You're straight out stupid or the most naive person I have ever met.

@Nmining
Copy link

Nmining commented Sep 15, 2018

So.. This morning with a cup of coffee I´ve been walking around this few-gigahashes gpu farm as usual. Steadily not a single drop on floor. And machines are doing well. But after reading this, I must look outside. So I let my coffee cup stay on table . Because I fear the worst. Through window, I can see the sun is shining... but not for long I know, more and more clouds will come and maybe some thunder. Unless someone push those ASICS away.

@OhGodAGirl
Copy link

I would like to talk about EIP-1057 (ProgPoW) and EIP-1355 (Ethash1a)
to give a timeline what we, the ethminer community, think what has to happen before we use them. Forking the consensus algorithm isn't as easy as Bitcoin Interest makes it seem. All miners, nodes and even light clients such as wallets have to be updated in order to accommodate the new algorithm.

My main concern with ProgPoW is, that it was introduced by a company that specialize in providing special mining software. The open source community needs more time to analyse the characteristics of ProgPow before we can fork. Otherwise for profit companies could sell their mining software which outperforms the open source variants not by 3-5% (like now) but by way more (15+%). This would lead to a centralization of mining power again, controlled by the companies that provide the mining software.

Therefore, we propose with Ethash1a EIP-1355 a minor change in the algorithm which would buy us more time to analyse ProgPoW.

Good lord this again.

ProgPoW is open source. Anyone with a brain can verify what it does and does not do.

On top of that, no, it wasn't introduced by a company - it was a side project worked on by IfDefElse, of which I happen to be a member. This algorithm has nothing to do with OhGodACompany or The Mineority Group.

We've literally walked everyone through the code, and the code is nicely commented too on what it does and how it works.

Regardless, the E9 is out now. Here's a fun fact for you: it's not an ASIC. As in, it's going to be resistant to any of your tweaks. How, you ask? Well, that's a ton of HBM2 in there. And those cores are going to be resistant in algorithm tweaks, because they can just be reprogrammed with some firmware.

It's lightcache churn, to the max.

And guess what? There's an even better version coming.

Enterprise miners will snap them all up, and control a majority of the hashpower, and when you have more than 20%, there are some wonderful exploits you can do.

I'd like to make a point to the community: I would not throw my real identity in the mix if ProgPoW was not going to do what it says it can do, and if I would somehow personally profit. Have a think, for a long, hard moment, what that would possibly accomplish, and how stupid that would possibly be when everyone and their mother knows who I am.

@Souptacular I would really like for misinformation and second guessing to stop happening, and I'd like to directly answer any questions the Parity and Ethminer teams have. If the timezones allow, we'll pull in Def and Else, too.

@MoneroCrusher
Copy link

@lrettig @vbuterin @5chdn @Souptacular It's so quiet around ASIC resistance talk. I think the community is no longer buying it. Come out and let us know what you think about hashrate centralization. And what you think about the new super ASIC that the company that announced it has full control over (that is 1 single entity).
Hypothetically: Would you guys be fine with me owning 80% of the Ethereum chain?

@MoneroCrusher
Copy link

MoneroCrusher commented Sep 15, 2018

Also, do you support the censorship on r/Ethereum? I made an anti-ASIC thread and it gained huge traction and was #1 on the frontpage quickly accelerating in upvotes.
First it was taken off the frontpage, then they even deleted my OP (https://i.imgur.com/26OBf8q.jpg or https://web.archive.org/web/20180915123751/https://www.reddit.com/r/ethereum/comments/9fyldx/breaking_news_new_asic_with_737x_efficiency_of_e3/)
Now its back on (while still being removed from frontpage), and I havent heard anything from a MOD why this has happened. NOW it's again back on. Thanks @5chdn there was still no proper reason though.
https://www.reddit.com/r/ethereum/comments/9fyldx/breaking_news_new_asic_with_737x_efficiency_of_e3/

Clearly you have a hidden agenda. Luckily you can't censor me on github. (me to myself: easy on the sips there) but there certainly is one mod who deleted this and it doesnt show in the logfile according to @5chdn

I hope as many people as possible see this.
It's very strange how quiet that ASIC question by @Souptacular was in dev meeting 46. A little too quiet. Did some of the ETH devs have behind the doors meeting with ASIC manufacturers?

I was just informed that it was deleted, I'm the only one that can see it. Maybe still in my cache. Here you go:
absolutely censored

@benefit14snake
Copy link

This is crazy why are we being ignored?

What happens if they decide it’s more profitable to double spend on binance and bittrex instead of selling the miners to the public?

Please don’t ignore this security threat.

@ghost
Copy link

ghost commented Sep 18, 2018

If ProgPOW doesn't make time with Constantinople we still have a chance to fork ethereum to anti-asic with different time schedule ( and I think this will help developers who are implementing Constantinople and help miners for implementing anti-asic algorithm )

@ghost
Copy link

ghost commented Sep 18, 2018

Just think of previous forks without roadmap, there was DAO, EIP-150, EIP-155 and these hardforks were all patches for ethereum network, to fix vulnerability of it.

If we think ASIC is a real threat to ethereum , why can't we fork later? With more development support??

@holiman
Copy link

holiman commented Sep 18, 2018

I would agree, @eosclassicteam. It's not in Constantinople, but there's nothing preventing it from being implemented soon after -- if there's dev support, and it's considered a high enough threat/priority.

@mdaria510
Copy link

mdaria510 commented Sep 18, 2018

      Seriously. A lot of people are NOT happy with the broken promises. If you want to push your most staunch supporters away at a time where every centralized shitshow is claiming to be the next ETH killer - go ahead. Weird, I feel completely helpless as both a miner and a user so who really has say? Because it’s not the community. Maybe the initial ICO investors?

Edit: I watched Zcash hashrate fluctuate from 1.05gh to 1.61gh today. Which means one entity (likely Bitmain) could easily pull off a double spend off any major exchange.
I know what you are thinking - that’s not half. Well they don’t need half if the other pools are split up. They just need the longest PoW - how much high than 50% dictates how far back in time you can reorganize.
When these new ASICS come online there will be a time where no miner can “defend” against this security break since we won’t have to proper power to Claim longest POW.
The exchanges stopped trading one time - will they do it again when several hundred million are stolen? Or will they just delist us?

You shouldn't feel helpless as a miner. You are empowered as a miner. Don't underestimate how much hash power GPU miners can collectively wield if someone were to effectively organize even a small percentage of them. We don't necessarily have to have the longest chain. We just have to have enough power to credibly back the existing chain and force exchanges to consider listing both chains, and insist that our chain is called "Ethereum", and nothing else. There needs to be enough of an uproar that press starts spreading the word that Ethereum is struggling to keep itself together while the price is already tanking. That alone will be enough to further tank the price to counteract any supposed benefit from the issuance reduction. It needs to be a no-win situation for the devs until they compromise. Think back to segwit2x - up until the cancellation there was enough theoretical support on both sides to force exchanges to consider the possibility that both would exist. No one ever had to mine a fork, they just had to believe that it plausibly could happen.

@MoneroCrusher
As soon as you fork and rename it you've lost. It's not an option. The only plausible way forward for GPU miners is to "go on strike" and commit to continuing to mine the existing chain and undermine the unity of Ethereum and force compromise.

Because it's pretty clear that the devs consider us as second class citizens and not their most devoted users. It's time to remind them what decentralization actually looks like.

Devs don't control the blockchain. They issue proposals in the form of code, and users and particularly miners choose whether or not to approve those proposals by running that updated code. I do not approve of this proposal, and I will not run this code.

If there are pool operators out there that will publicly commit to continue running the existing chain past the fork, please step forward now and I will do everything in my power to spread the word. You have a good incentive to do so - it would make your pool unique and attract the attention of GPU miners worldwide, and you would therefore benefit from a significant increase in income prior to the fork, no matter what happens. I would do it myself if I wasn't prohibited in my state.

In either case if there's no movement on this before the end of September, I'll personally make it a quest to ensure that every and anyone with an incentive to take Ethereum down a peg or two is aware of the situation, and I'm sure it won't be terribly difficult to find at least a few wealthy individuals that will throw some resources at it, whether its hash, mining pools, propaganda, or whatever. I can already think of more than a few that would love nothing more than to see Ethereum crash and burn.

@MoneroCrusher
Copy link

MoneroCrusher commented Sep 19, 2018

@mdaria510
That's a far greater idea than mine. Only when shit hits the fan we could think about it.
In your "resistance" scenario all that miners have to do is nothing. This is great.
We need to get some pools on our side because the pools will also get less revenue since ASICs & big farms will mine on their own private pools.
I for sure will not provide any hashing power to the new chain.

Edit:
That is if no plan to address this issue is laid out by the EF this month. And no, Istanbul is not an option to me and many others. This needs to be implemented shortly after Constantinople.

@5chdn
Copy link
Contributor

5chdn commented Sep 19, 2018

This needs to be implemented shortly after Constantinople.

Then start working on it. I'm happy to accept any ASIC-resistant engine and tests for Parity Ethereum.

@MoneroCrusher
Copy link

@5chdn Would me getting a private testnet running help you with that? I got instructions on how to set one up with ProgPOW. I'm not a programmer though, but as far as I know OhGodAGirl is already in contact with you guys.

@theWUJustin
Copy link

I would agree, @eosclassicteam. It's not in Constantinople, but there's nothing preventing it from being implemented soon after -- if there's dev support, and it's considered a high enough threat/priority.

I think this is a very high threat against Ethereum, for the following reasons:

  1. GPU miners are being pushed out of the market. This leads to higher levels of centralization with ASICs. Of course this is bad for one of the central pillars of blockchain, which is robust decentralization.

  2. We have many instances of ASICs completely dominating a coin and forcing them to make policy decisions at gun-point, and I don't think Ethereum core devs want to put themselves in this situation.

  3. The argument "ASICs aren't a threat because POS is 'around the corner' is a failed argument considering that by the time even the first implementation of POS rolls out, the E9 miner will already have shipped and be mining, and most GPUs will have dropped off the network. This makes transitioning to POS much harder since you'll be fighting all the ASICs with their break even timelines who won't want to switch. That will cause another divide in the community and result in an "Ethereum Classic Classic The Remix Part II The Sequel feat. The Zombie Doppelganger Twins" which is a disaster squared.

ProgPow and EIP 1355 should be a priority because:

  1. You literally have people like OhGodAGirl offering to do all the work, and the attitude is basically "we don't need your help". That seems very arrogant and is not in character with the open source community where everyone tries to help each other.

  2. The GPU miners are pissed that they are getting a block reduction down to 2, and not changing the POW to address ASICs is like a slap in the face. We need to get them back on-board, or else they will mine other coins just to spite ETH, and we are seeing that already with threats of this, and also spreading FUD, which brings me to my next point.

  3. Endless sources of FUD surrounding this will happen and further tank the price. Ethereum cannot be successful at any stage if the ETH price is low. Investors will flee and interest will wane, and if there's only the hardcore developers there building "for the tech, man" you'll never get the holy grail of blockchain that everyone is supposedly building for: Mass Adoption

Thanks for reading

@holiman
Copy link

holiman commented Sep 19, 2018

You literally have people like OhGodAGirl offering to do all the work, and the attitude is basically "we don't need your help". That seems very arrogant and is not in character with the open source community where everyone tries to help each other.

@OhGodAGirl has been very helpful, and nobody (afaik) has said "we don't need your help". But it's a fact that switching consensus engine require quite a lot of work:

The TODO list for ProgPoW adoption: https://ethereum-magicians.org/t/what-has-to-be-done-to-get-progpow-on-ethereum/1361.

@HiddeHoogland
Copy link

HiddeHoogland commented Sep 19, 2018

Why aren't we pursuing the decentralization that we intended Ethereum to be?

Having 6000 running GPU's on the Ethereum network for a while, i never thought we would need this discussion. My hashrate will be supporting XMR for the time being.

@mdaria510
Copy link

mdaria510 commented Sep 19, 2018

@holiman

I’ve lost count of how many times the roadmap has slipped because of things taking longer than expected, so it’s not like devs are in some double bind where there’s an immovable deadline and they’re being forced to do the impossible. The deadlines are self imposed. So they need to push the fork back if they have to and get it done.

Ethereum mining is big business now. There are millions of GPUs mining ETH. Which means billions of dollars of investment is on the line for people. Some of that is hobby miners but a lot of that is people who have made very, very significant investments in running the software they write. What devs consider an inconvenience and extra work is threatening people’s livelihood. Devs actually have the choice to implement this or not - anyone’s who’s livelihood is at stake doesn’t even have a choice, the only logical course of action for them is to oppose and derail the fork. I don’t know if that’s getting through to them - for people heavily invested in ETH mining on GPUs, ASIC resistance isn’t a “nice to have”, it’s a necessity. They can’t just wave this away and expect people to acquiesce because they don’t consider it a high priority. It’s the only priority for many people.

I also don’t want to hear any excuses about the difficulty bomb either. That was a cute idea when ETH wasn’t far and away the primary source of income for GPU miners. That idea worked when there was something else for millions of GPUs to mine, because then any miners that didn’t agree would just shrug and mine something else. That doesn’t work in a bear market where most miners are barely scraping by. It’s a gun to everyone’s head now - but GPU miners are the only party here backed into a corner with no other option but brinksmanship.

@lrettig
Copy link
Contributor Author

lrettig commented Sep 20, 2018

it’s not like devs are in some double bind where there’s an immovable deadline and they’re being forced to do the impossible. The deadlines are self imposed. So they need to push the fork back if they have to and get it done.

This is not entirely true. The difficulty bomb is the immovable deadline. Call it an "excuse" if you like, but it requires us to hard fork relatively often, relatively on schedule. It's doing its job quite well.

@mdaria510
Copy link

mdaria510 commented Sep 20, 2018

It requires us to hard fork if we want to keep the chain running. But GPU miners are now being put in a position where there is effectively no difference between Constantinople making their hardware and investment obsolete or the difficulty bomb making their hardware and investment obsolete. I'd love nothing more than to see it removed because the only reason it exists in the first place was to get miners to act against their own self interest. Vitalik has said as much himself. Maybe they didn't forsee the perfect storm of a rally that brought in millions of miners only to have the price dump shortly thereafter, ultra efficient ASICs that made a joke of ETH's ASIC resistance and being the only chain keeping those millions of GPUs afloat - but these are the consequences of the game theory inherent in that ploy. The road to hell is paved with good intentions.

We both know it's no big deal to remove it in a fork, so it is unequivocally a self-imposed deadline. It requires a fork to keep Ethereum functioning, but it says nothing about what that fork contains beyond than an extension or removal of the bomb.

@MoneroCrusher
Copy link

MoneroCrusher commented Sep 20, 2018

Good news: https://twitter.com/nicksdjohnson/status/1042382028837203968
Nick Johnson now supports ProgPOW after chatting with @OhGodAGirl and wants to implement it!
Hope my reddit thread helped accelerate that happening!

Timing is critical too, though. Devs knew about this since May. I think to restore miner community faith it should be done as fast as possible, not in Istanbul HF.
Why not in Istanbul HF? Because the network will punctually centralize with Constantinople HF at the end of October. Many GPUs will be turned off or turned to other coins and new hashrate growth will only come from ASICs.

So when Istanbul HF comes closer and they want to implement ProgPOW then, we will have even more of a community chaos, since some people will have switched to ASICs by then.

Edit: I think it's worth pushing Constantinople back 1 month to be able to implement it, if this is deemed urgent.

@5chdn
Copy link
Contributor

5chdn commented Sep 20, 2018

Edit: I think it's worth pushing Constantinople back 1 month to be able to implement it, if this is deemed urgent.

My estimation is ~12 months. Instead of pushing back Constantinople for another year, let's just do another hardfork.

@MoneroCrusher
Copy link

MoneroCrusher commented Sep 20, 2018

@5chdn According to @OhGodAGirl 's last claim she said she could easily do it until Constantinople. What makes you think it's going to take 12 months? She has repeatedly said that the hard part is already done. Only thing that's left is basically client work and that she would provide manpower for it, free of charge.

@nootropicat
Copy link

@MoneroCrusher

Getting ASICs to the masses prevents Ethereum to fork because community doesn't want to when they own ASICs. This protects their investment.

If they manage to sell ASICs to the masses, ASIC mining is no longer centralized, making the decentralization argument moot.
Asic mining behaves as a physical proof of stake, offering much higher security than gpu mining (for the same block rewards).

@MoneroCrusher
Copy link

@nootropicat yeah unless they sell the ASIC that is 1:1 the efficiency of GPU to the masses for cheap and keep the one that is 8x more efficient to themselves, which is what they do.
Alternatively check out the Zcash problem or the Dash problem.

@holiman
Copy link

holiman commented Sep 20, 2018

Well, if it's "ok" to push back Constantinople one month, how can it not be acceptible to roll it out in a HF one month after the non-pushed Constantinople?

I would also support a switch to ProgPOW, but I do not think we should cram it into Constantinople. The implementation of the algorithm is one aspect, but there are other things that need to be done to ensure a switch goes smoothly, and those things needs testing.

My opinion is that we should consider a dedicated pow-switching HF shortly after Constantinople.

@nootropicat
Copy link

@MoneroCrusher there are at least two ethash asics providers now (Canaan and Bitmain) and they're competing, making that scenario unlikely and temporary at best. Keeping best products from the market invites new competition.
If you think it's a realistic long-term danger, why that's not the case in bitcoin?

Alternatively check out the Zcash problem or the Dash problem.

That's too vague. What 'zcash problem'?

@MoneroCrusher
Copy link

MoneroCrusher commented Sep 20, 2018

@nootropicat With Bitcoin it's becoming less and less of a problem but it still is one (because after many years now we are finally seeing some competition). But Constantinople is coming soon and there won't be any free market competition (competition for the Ethereum chain between manufacturers at most) until then. They'd milk ETH as much as they can then create some FUD in the end and sell their miners to gullible people.
The problem with Zcash ASICs is that the manufacturer already has a better faster generation and is now smartly phasing out the gen1 ASIC to get as much out of customers as possible. They started out at $10k and 70-80 break even days in June, in the beginning of September they were $3-3.5k (same manufacturer), also with 70-80 days break-even. Guess where we're at? 300 days for the june batch (assuming it was mining from June until now) and 180 days break even for the newest one. Those things will never break-even. They're not designed to. They're only designed to deceive gullible customers and generate revenue & off-roll risk for the manufacturer who is already mining on gen2. As soon as the last gen 1 is sold and gen 3 is manufactured they'll do the whole thing over with gen 2. Zcash miners are fucked over for years. Their governance completely failed them.

@holiman I don't care, it can also be a separate hardfork. I feel like if it's included in Constantinople it'll get done in a faster manner. And more importantly because you make yourself susceptible to 51% attacks in that time, especially when going from 2 ETH / ethash chain to 2 ETH / ProgPOW chain. Think those ASICs will just sit idle and do nothing while their value goes to 0? So in everyone's interest besides ASIC manufacturer's it's better to do the thing in one swift switch and be done with it. Don't forget: there are hundred of millions of dollars at stake.

tl;dr doing a separate HF after issuance reduction will increase drama unnecessarily.
Either do it with Constantinople OR take issuance reduction out of Constantinople and introduce it in the ProgPOW fork.

@mdaria510
Copy link

@holiman For various reasons that should be obvious enough that I don’t need to list them, I have very little faith in it actually being implemented in a timely manner (or at all) once the pressure is off.

@Nmining
Copy link

Nmining commented Sep 20, 2018

Grabs coffee cup from table. So what is going to happen to Etherium and stuff and is Ripple going to kick Etherium down to position 3 today? Oh!! #### this is cold...

@theWUJustin
Copy link

@holiman I also agree about putting the transition to ProgPow in Constantinople. By reducing issuance to 2 ETH per block, suddenly many GPU miners are not profitable and will switch off the network. We've already seen a hashrate drop. This is the perfect opportunity for ASICs to sweep in and control the network. By delaying Constantinople to include ProgPow you don't risk anything except maybe a FudDesk article "Ethereum misses key hard fork deadline." or some garbage click-bait like that. Not a big deal.

But not including it in Constantinople you risk ASICs owning the network, which opens the door to a very contentious HF "soon after" Constantinople if it happens at all before it is too late. Nobody wants Part II The Sequel of Ethereum Classic Classic.

@lrettig
Copy link
Contributor Author

lrettig commented Sep 21, 2018

Closing in favor of #58

@lrettig lrettig closed this as completed Sep 21, 2018
lrettig pushed a commit that referenced this issue Mar 4, 2019
* Creating minutes #55.md

Adding minutes of #55

* Notes Meeting 56.md

Creating notes #56

* Delete Meeting 55.md

This file was already added in #81
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests