Quote from: thesnat21 on June 12, 2018, 06:21:22 PM

Quote from: bible_pay on June 12, 2018, 06:15:40 PM

I would be pushing to be late on the mandatory for June and wait for it - if it were not for our June 26th cascading superblock bug that gives us a black eye.

Anyway there is also the possibility that we release the token as a leisure - because exchanges don't need the token. I'm focusing on this plan for now. In this way we might be able to have our mandatory before the superblock bug hits, but it's already the 12th, and we need to test for a couple weeks and also give the exchanges 10 days notice to upgrade, so we might not make it anyway. Let's see how testnet goes.

The exchange is not a masternode, do they really need the DCC info to be correct?

I suppose the concern would be their client rejecting the rules and forking?

I said in the prior post the token could be done as a leisure. So yes, the token is not part of a mandatory upgrade.

The reason the token is important for scheduling is the mandatory upgrade is a point where the network comes together with consistent rules. So it is a consideration to release the token if possible, if for example we hear from IBM a timeline on the release. At this point we don't even know if the download business logic is changing, so lets wait to hear from IBM.