ethcore/res: bump canon fork hash for mordor and kotti testnets

[q9f]

both testnets were recently recovered. the fork hashes help clients to identify healthy peers.

bonus: updated kotti bootnodes. ref hyperledger/besu#590 etclabscore/core-geth#84

[q9f]

that block didn't make it into the main chain

> eth.getBlock(0xcd16a)
{
  difficulty: 921182,
  extraData: "0x",
  gasLimit: 4712388,
  gasUsed: 0,
  hash: "0x17f6cc524412278600cd196fdd387bec899146ac6bf360eac419e3b75192888c",
  logsBloom: "0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
  miner: "0xd4616c89247a4bb2fbebaef15fd10fa38eca15dc",
  mixHash: "0x13404b3486d29847c27caab5bf1da828d9b7854eed2e4f554f6f784dcdc4678c",
  nonce: "0x70631a4f60bea2b2",
  number: 840042,
  parentHash: "0x3ba097fdcd4c2ffa0ffac294bf56bf7473f172ef55276f62c679e4052a7cf13d",
  receiptsRoot: "0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421",
  sha3Uncles: "0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347",
  size: 514,
  stateRoot: "0x4b85846591018b090e11497a2f4f77876d25c0983a5c4776fcbe80032ce5373d",
  timestamp: 1581212828,
  totalDifficulty: 1025372183168,
  transactions: [],
  transactionsRoot: "0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421",
  uncles: []
}

[dvdplm]

both testnets were recently recovered.

Can you elaborate on what happened? Was there a mistake in the spec file? Or…?

[q9f]

both testnets were recently recovered.

Can you elaborate on what happened? Was there a mistake in the spec file? Or…?

The Aztlan ECIP 1061 was proposed to be appended with ECIP 1078 and this was implemented on the testnets for testing purposes. Both ECIP 1061 and 1078 were meant to be a bundle, therefore they had the same block number on the mainnet.

However, the timing of the hardforks for testing purposes was less conservative, and therefore ECIP 1061 already activated on both testnets before 1078 could be scheduled. That time between 1061 and 1078 activation on Mordor and Kotti lead to a series of side-effects including consensus split between Besu and Geth/Parity. See ethereum/EIPs#2526 ethereum/EIPs#2514 ethereum/go-ethereum#20646 and #11474

Eventually, it was decided to pull 1061 and 1078 altogether and replace it cleanly with a single hardfork (ECIP 1088) that would not have these issues. ETC Labs Core, ChainSafe, and Byzantine Fault advised to go that route. https://medium.com/ethereum-classic-labs/advisory-to-reject-ecip-1061-aztlan-and-ecip-1078-phoenixfix-for-ethereum-classic-28df21a206c

The community accepted that path with 1088 and rejected 1061, 1078, and 1086 ethereumclassic/ECIPs#298 ethereumclassic/ECIPs#297

There is a lot of background information on Github ethereumclassic/ECIPs#217 ethereumclassic/ECIPs#226 ethereumclassic/ECIPs#227 ethereumclassic/ECIPs#262

This Gist explains the historical context reaching all the way back to Constantinople issues on Ethereum network https://gist.github.com/meowsbits/ddf54e7cb225e7f89b3ed0b7d92b8a37

So, for the testnets it required some reconfiguration and invalidating the Aztlan chain in favor of a Phoenix chain. I hope that answers your question.