Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Add support for ecosystem specific consensus hashes #502
This PR adds support for ecosystem specific consensus hashes.
The purpose is to allow the quick verification of consensus for a specific ecosystem rather than for the entire state. For example clients may allow new transaction types such as UIT in the test ecosystem which would cause a differing consensus hash between clients when the whole state is considered. With this amendment we can thus generate a hash specifically for the main (or test) ecosystem.
The default is still to generate a hash that covers both ecosystems, but an optional ecosystem parameter can be supplied with the consensus hash RPCs that will specify an ecosystem.
Probably easiest to explain with an example. Craig wants to run UIT in the test ecosystem before activation which means at least OW & OE would need to be running a client that supports UIT. Once UIT transactions are in the test ecosystem, clients that understand them are going to give a different consensus hash for the test ecosystem than clients that don't understand them.
The only way to make sure that the production ecosystem is unaffected and all these clients are still in production eco consensus is to split out the consensus hash.
Hopefully that makes sense! Let me know if it's still unclear and I'll try and be clearer dude :)