Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Feb 28 2019 19:45
    @Arachnid banned @merkle_tree_twitter
  • Feb 17 2019 00:56
    @jpitts banned @Aquentson_twitter
  • Apr 09 2018 04:14
    @holiman banned @JennyJennywren_twitter
  • Oct 21 2017 19:12
    @Arachnid banned @Musk11
James Hancock
@MadeofTin
Are you using ether scan charts? @econoar
econoar
@econoar
Ya
James Hancock
@MadeofTin
Okay, so biggest confirmation that eric is indeed right is that the increase to 14 second blocktimes happened around https://etherscan.io/block/8900000
which we know the ice age increments every 100k blocks
@econoar
econoar
@econoar
Yup. Agree.
James Hancock
@MadeofTin
Nov-09-2019 03:07:30 AM
November 10th we see the average block time increase
econoar
@econoar
Also we pushed it 2mn blocks and last time it started around 6.9mn and this time first visibile bump was 8.9mn. But I’ll admit again I’m just eyeing charts and loose remembering of how this works.
sassal
@sassal
seems my data was a little off (it was very rough) but good to know that it still fits
Hudson Jameson
@Souptacular
James Hancock
@MadeofTin
good find!
Paweł Bylica
@chfast
@Souptacular The Istanbul ready release of Aleth is 1.7.1: https://github.com/ethereum/aleth/releases/tag/v1.7.1
James Hancock
@MadeofTin
I can confirm it is the Ice-age. The next bump will be in about 5 days.
Hudson Jameson
@Souptacular
@chfast thanks, I included a link to it in the blog already
@MadeofTin Eeeek
sassal
@sassal
will it require an out-of-schedule hard fork to stop it from freezing the chain @MadeofTin?
Hudson Jameson
@Souptacular
@sassal with the new EIP centric model there isn't exactly a "schedule" but we did have a rough time for Berlin or something. @MadeofTin can explain it better.
sassal
@sassal
yah haha i meant if its going to have to be before Berlin (seems like it will be)
James Hancock
@MadeofTin
Berlin hasn't been scheduled. It may be that Berlin happens sooner then march.
If we want to call it Berlin still
sassal
@sassal
yeah i was going off the march date
James Hancock
@MadeofTin
It should be around 16 second block times.
20 second block times will be around 18 days later, so in 23 Days from now.
Micah Zoltu
@MicahZoltu
I thought the ice age wasn't for another 6 months or something, which is why we aren't bumping it in Istanbul?
20 second blocktimes within a month feels like worth addressing in Istanbul.
James Hancock
@MadeofTin
Blocktimes have been been faster, as well as the difficulty is different
so it is showing up earlier than expected
James Hancock
@MadeofTin
I would recommend a fork right after istanbul. We only have 14 days until Istanbul launches.
Hudson Jameson
@Souptacular
Why would you reccommend it happening so soon?
James Hancock
@MadeofTin
Depends on the groups tolernace for longer block times.
  • in 5 days - 16 second blocktimes
  • in 23 days - 20 second blocktimes
  • in 47 Days - maybe 25-30
Hudson Jameson
@Souptacular
I remember us polling the community sort of using reddit and twitter a while ago when we asked "what is the highest block times you are willing to endure", but I'll have to find the links tomorrow.
James Hancock
@MadeofTin
  • November 25th - - 16
  • December 13, 2019 -- 20
  • January 6, 2020 -- 25-30
The next period would be the end of january
Hudson Jameson
@Souptacular
My opinion: The community would be able to handle 25-30 second block times max. So if we can have a fork happen mid January that would be ideal :/
sassal
@sassal
i remember 30s block times... that was not pretty
+1 @Souptacular
James Hancock
@MadeofTin
I see two options. Fork fast and only change the number. Or, Fork a little slower and fix the ice-age mechansim so this doesn't happen again.
Mid january would fit either of those options imo
Hudson Jameson
@Souptacular

I have heard differing opinions as to:
a) Why the ice age was originally added to Ethereum.
b) What that means for the chain today.

So I hope we can quickly rehash those opinions as a community to see if we even want it anymore.

James Hancock
@MadeofTin
Yes
Hudson Jameson
@Souptacular
I don't know where I stand on the issue.
James Hancock
@MadeofTin
I believe in the intention, but not in the mechansim.
sassal
@sassal
given that eth2 is being deployed as a separate chain, i lean towards the ice age being unnecessary and something that could be removed without much consequence
but i dont know the current consensus around it in the community
James Hancock
@MadeofTin
The ice-age means that any contentious fork would need to be proactively made. And not retrofit onto any previous ethereum fork. It effectively bricks the legacy chain, and the only way to resurrect it is to make an update to client code.
Hudson Jameson
@Souptacular
@sassal @econoar can we include the explanation as to why we have the difficulty bomb and not just how it works in the EthHub article? I can then point people there when I ask them what their opinion is on it.
James Hancock
@MadeofTin
with the deploying of ETH2, i don't think we want old versions of Eth1 being shadow deployed. Better to leave all chains before us dead.
sassal
@sassal
@Souptacular can do
James Hancock
@MadeofTin
Shadow meaning, just grab an old version of Geth and start mining on it.