When the median time past[1] of the most recent 11 blocks (MTP-11) is greater than or equal to UNIX timestamp 1510600000 Bitcoin Cash will execute a hardfork according to this specification. Starting from the next block these three consensus rules changes will take effect:
...

LGTM, tested ok.

LGTM, tests ok

See previous comments for list of BCC occurrences that I think should be added.

I applied this diff to HEAD, and used a grep program to scan for more BCC. Found some which maybe you can still replace together with those you have already in this Diff:

Thanks for testing @jjz . It definitely it takes a long time when the caches are not filled.
Depending on if you're lucky or not (get a slow Travis instance or a faster one) it can even time out at the 50min limit for that first build (did for me).
In which case a platform build may error out and need to be restarted until it passes.

Explicit conversion to int64_t

Another grammar fix

Formatting was still bad, fix

Fix up the commenting that the lint auto-adjusted

Looks good and tests fine.

For consideration of 0.16.0 release: It is better to have Travis working for a subset of platforms than to have it constantly fail the entire suite

Resolved by D605

Ah, thank you @jasonbcox . The task is not currently assigned to anyone, but I think anyone can grab it and close it.

Test result on Travis with these changes in a private branch:

In D621#11300, @deadalnix wrote:

Why is the test flacky ? Why does this fixes it ?

Fix dropped parenthesis

Move PIE_FLAGS to more appropriate location

I tested on a machine with previous failure rate of > 10% , for more than 100 iterations without problem.

Test results:

This has been verified in a Travis-checked branch:
https://travis-ci.org/ftrader-bitcoinabc/bitcoin-abc/builds/275536583

Travis is also happy again

Generally: I think it would be nice to have an RPC interface to allow miners to get/set the current blockprioritypercentage . This might be more involved though, so it's best dealt with in a separate diff at some stage I think (it's also not very urgent, a configuration parameter is a good start).

Looks good, didn't find any other instances of Bitcoin-Qt that we want to change at this point
(there are some, but it's been noted that they affect the app id as far as Qt is concerned, and if we change them it will make the preferences files and Windows registry keys have a different unique id,
so users would lose their GUI preferences - these will be dealt with by migration code in further diff.

In D510#8986, @CCulianu wrote:

Ok, I can do that at a later time (like later tonight or tomorrow morning) -- or freetrader -- if you're already set up mind doing it since.. well.. you're already set up?

Fix CFBundleURLSchemes

Fix broken URL

Travis test passed:
https://travis-ci.org/ftrader-bitcoinabc/bitcoin-abc/builds/269961272

Gitian builds and the extended tests worked alright.
Travis testing seems blocked by a hanging test on HEAD at the moment - I'll push this on a branch off the last passing commit to test.

@deadalnix : after the T97 crash showed up on Travis, I compared the recent (0.15) Core proxy_test.py with ours, and indeed they applied the same fix by moving that code into setup_nodes().

All ok with me.