hive-kcc: a fork of ethereum hive with cases for KCC

Run all available integration test cases against kcc:

hive --sim kcc --client kcc,kcc_v1.0.3

available cases:

• A general smoke test
• Ishikari hardfork: hardfork test with a single node
• Ishikari hardfork: hardfork test between multiple nodes
• Ishikari hardfork: distribute block reward
• Ishikari hardfork: punishment
• kcc-issue-9: failure on synchronization due to CVE-2021-39137
• Ishikari hardfork: An inactive validator becomes active after voting for it

Why do we need to specify two different versions of clients?

• kcc should be the latest version of kcc
• kcc v1.0.3 is a reference client for testing a synchronization issue(kcc-issue-9)

---

---

---

---

hive - Ethereum end-to-end test harness

Hive is a system for running integration tests against Ethereum clients.

Ethereum Foundation maintains a public Hive instance to check for consensus, p2p and blockchain compatibility. You can find the latest test results here.

To read more about hive, please check the documentation.

Trophies

If you find a bug in your client implementation due to this project, please be so kind as to add it here to the trophy list. It could help prove that hive is indeed a useful tool for validating Ethereum client implementations.

• go-ethereum:
  • Genesis chain config couldn't handle present but empty settings: #2790
  • Data race between remote block import and local block mining: #2793
  • Downloader didn't penalize incompatible forks hashly enough: #2801
• Nethermind:
  • Bug in p2p whith bonding nodes algorithm found by Hive: #1894
  • Difference in return value for 'r' parameter in getTransactionByHash: #2372
  • CREATE/CREATE2 behavior when account already has max nonce #3698
  • Blake2 performance issue with non-vectorized code #3837

Contributions

This project takes a different approach to code contributions than your usual FOSS project with well ingrained maintainers and relatively few external contributors. It is an experiment. Whether it will work out or not is for the future to decide.

We follow the Collective Code Construction Contract (C4), code contribution model, as expanded and explained in The ZeroMQ Process. The core idea being that any patch that successfully solves an issue (bug/feature) and doesn't break any existing code/contracts must be optimistically merged by maintainers. Followup patches may be used to for additional polishes – and patches may even be outright reverted if they turn out to have a negative impact – but no change must be rejected based on personal values.

License

The hive project is licensed under the GNU General Public License v3.0. You can find it in the COPYING file.