Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Feb 28 19:45
    @Arachnid banned @merkle_tree_twitter
  • Feb 17 00:56
    @jpitts banned @Aquentson_twitter
  • Apr 09 2018 04:14
    @holiman banned @JennyJennywren_twitter
  • Oct 21 2017 19:12
    @Arachnid banned @Musk11
Lefteris Karapetsas
@LefterisJP

I mean if we had a split for four days, how bad would that be?

Pretty bad. At such point I would prefer a new PoW testnet.

A testnet is supposed to be light and easy to use, but Ropsten became way too heavy already. I don't mind if it breaks up and joins Morden in history.

For us and our testing consistency with older data is not required. We can easily afford to re-deploy to a new PoW testnet (that's lighter than Ropsten) that can be used by both clients. As long as such a testnet exists and we don't have to do that often.

Péter Szilágyi
@karalabe

Pretty bad. At such point I would prefer a new PoW testnet.

Well, you could gasp wait 4 days with resuming testing on the public testnet ;P

or perhaps run your own private testnet for heavy testing?
Noel Maersk
@veox
Continuing to run the pre-fork Ropsten is also an option.
AFAIK, Raiden is in public testing. As in, the general public has been invited to use this version, prior to the main-net release.
Lefteris Karapetsas
@LefterisJP

Continuing to run the pre-fork Ropsten is also an option.

That is an option.

or perhaps run your own private testnet for heavy testing?

What @veox said. It's not just us testing.

Well, you could gasp wait 4 days with resuming testing on the public testnet ;P

We are on a feature freeze so testing is our main focus right now. 4 days of development is a lot

Péter Szilágyi
@karalabe
You've been working on raiden for 3 years ;P
Ok, I don't want to come off as an asshole really. Someone will be unhappy either way imho :)
Lefteris Karapetsas
@LefterisJP
If you want to break Ropsten, please provide an alternative ethereum testnet that is compatible with both major clients and we will switch to it.
If not then I would appreciate not breaking Ropsten.
EOS Classic
@eosclassicteam
If Ropsten is being a problem we can launch a new, clean testnet as it was discussed on last dev call
But it will require us to manage a new chain for "test" purpose which is useless :joy:
Péter Szilágyi
@karalabe
Yes, I obviously want to break rospten
Preferrably mainnet too
Ideally the entire internet
Mikhail Kalinin
@mkalinin
:joy_cat:
EOS Classic
@eosclassicteam
:joy:
Still we can break ASIC miners on ethereum :joy:
Martin Holst Swende
@holiman
.... Can we please use the testnet for testing for a few weeks, we have a hardfork coming up
EOS Classic
@eosclassicteam
If someone rent nicehash we can make the fork today :joy:
Martin Holst Swende
@holiman
Let's launch a hashimoto-progow testnet when we've gotten further on that part, that can replace ropsten, but probably not for a few weeks
Before that, I personally would like if we can go ahead as planned
EOS Classic
@eosclassicteam
@holiman +1 for the suggestion, we need testnet for further implemention like Pool and Miners
ledgerwatch
@AlexeyAkhunov
I would like to remind everyone that the fact that teams like Raiden and their users are testing on the public test net is actually good for that public testnet. It is much more likely to get bugs discovered than a testnet without any users (because it was broken for few days and everyone had to migrate to another). I would still recommend to complete pre-testnet testing before pushing for the test net.
I would even say that it makes sense to create a new PoW chain just for core devs for a little while, and once it has gone for a few days without issues, do Ropsten fork
We have to respect the users of Ropsten, because they help us test the new release
EOS Classic
@eosclassicteam
:thumbsup:
I am a side-chain developer but I still use ropsten to test my contract
ledgerwatch
@AlexeyAkhunov
I don't see the point of making a tweet asking for objections to break Ropsten, hear the objections, but then do it anyway :)
EOS Classic
@eosclassicteam
If we can't make the fork the answer is always "Classic" :joy:
Let them use Ropsten "Classic" chain :joy:
Lefteris Karapetsas
@LefterisJP

@holiman you made the tweet asking for projects to tell you if they use Ropsten. I just did. We would have more work on our plate if Ropsten breaks this month and this is a critical month for us.

It's obvious that our priorities are very different and in the end it's not my decision. From the way my comments here were received it sounds like a done deal, so we will try to plan accordingly.

EOS Classic
@eosclassicteam
I propose next version of pow testnet needs to remove diff bomb since it is bothering our workflow, we do not need higher blocktime for sure
ledgerwatch
@AlexeyAkhunov
I suggest to launch a temporary testnet just for core devs (like a DEV environment) to just see if there any obvious problems and do a bit of poking there. If that works, move it to Ropsten (UAT environment :) ). That obviously requires delaying Ropsten, and I actually thinks it sends a positive signal rather than negative (if this is a worry). And, if the worry is to start testing as soon as possible - by keeping Ropsten stable, rather than shaking all the users off, the quality of testing will be better, even though it will start later
Martin Holst Swende
@holiman
Ok. I'm fine with either. I can live with postponing it, but we need a decision now
We're about to make a release
Wei Tang
@sorpaas
TBH, if there're still miners running older version of Ropsten, then technically we already have two networks after the split.
So as long as people are still mining, I don't think it will actually matter a lot to @LefterisJP's workflow -- there may be higher blocktime variance, and his/her transactions may get confirmed on another chain, but that's all.
Martin Holst Swende
@holiman
Yes, @veox pointed that out too
Continuing to run the pre-fork Ropsten is also an option.
ledgerwatch
@AlexeyAkhunov
@holiman Let me offer you a carrot - I will do more code reviews of CREATE2 before the Ropsten fork if you decide to postpone :)
Martin Holst Swende
@holiman
It's not like it's up to me to decide
ledgerwatch
@AlexeyAkhunov
who?
Péter Szilágyi
@karalabe
We need a decision together with @5chdn and Parity
I don't care either way, as long as Geth and Parity agrees on the same thing
Martin Holst Swende
@holiman
I agree
@5chdn @folsen call it please
Fredrik Harrysson
@folsen
I'm fine with postponing