F2Pool supposedly signed a document claiming that they would only run "Core compatible" consensus code:
[source]We will only run Bitcoin Core-compatible consensus systems, eventually containing both SegWit and the hard-fork, in production, for the foreseeable future.
Well, "Bitcoin Core-compatible consensus systems" is interpreted by F2Pool to include the following gem:
And what about this one!We are testing Classic mining on stratum.f2xtpool.com at port 3333. F2XTPool is currently powered by Bitcoin Core v0.12.0, with -mempoolreplacement=false, only block version is set to 0x30000000. We are not going to run Classic node in production, for the “foreseeable ”future.
So, they are "honoring" their agreement, in their own way I guess, by running a Core node configured as Classic.[–]macbook-air 16 points 2 hours ago
- We have agreed in Hong Kong that we are not going to run Classic in production, for the “foreseeable” future.
- Classic is compatible with Bitcoin Core unless 75% target is met, which is not “foreseeable”.