- launch testnet 3.2 (few days)
- announce test phase 2 (few days in advance to allow everyone to set up their nodes)
- run test 2 ( few days (they said max 20, which is already not possible)
- announce test phase 3 (few days)
- run test 3 (1 days)
I’m already 19+ days, but lets continue:
- launch mainnet (few days to prepare, ASSUMING nog large bugs or issues coming from test 2&3)
- do token swap (multiple weeks)
And then we also have christmas,, and we have new years eve (during which nobody will be working)
And we have 3 weekends (during which cs has proven to be not working)
So of the 19 days, i have effectively 13 left.
Deduct christmas and new hears eve, and I have 10 left.
10 days to run 2 tests, process all bugs found, launch mainnet, and do a swap.
Add to that credits’ consistent behaviour of ignoring deadlines, and the conclusion is:
- swap: not gonna happen before everything is stable is heavily tested, so aim for q2/3-19
- mainnet: likely q2/3-19
Test phase 3: likely q1-19
Test phase 2: likely q1-19
Testnet 3.0: likely end if q4
Prepare for a massive price drop when they, inevitably, communicate the delay on 31-12 (just like they did in july), as the moon sheeps following this project are too dumb to see this coming, and will sell in panic when their lambos dont arrive on 31-12.
Remember, if you discount it for the 6 months that have passed, almost 0 progress has been booked on the front-end (wallet has still bugs in v 2.2).
Back-end still shows errors and sync problems in v2.2. Add to that consensus protoal changes in v3.2 (really, right before mainnet launch you change consensus mechanism?)
Just compare it with Ziliqa, the amount of progress booked there is massive, as both projects started with testnet 1 before the summer holiday
You're wrong since the commence of your post, they don't celebrate any holidays in December, that's why your calculations are wrong, as a tester I have to say about substantial progress, I'm following all updates from the beginning and this is really huge, bugs on the front-end are minor as the bugs on the back-end, errors are possible on any stage, especially testnet phase, I'm sure they have more important development goals than bugs about which you are talking, you can't estimate a degree of changes in consensus without a closer look what developers are doing there, they are promising to fix them by the end of this week, if no, I don't care as the quality is the priority for me personally, I feel a huge potential here, your points are senseless and you are trying to create doubts for these "sheep", it's not fair boy, if you don't have an interest, just leave this place and don't try to be "hero" for public