Hello everyone,
Third Key Solutions is preparing a draft proposal for an addition to CCSS.
We are proposing the introduction of "Consensus Monitoring and Maintenance Programme". With the recent unplanned fork, we feel we should address consensus more directly in the standard. The proposal is not specific to a single currency or set of consensus rules. It will require process for monitoring and maintaining consensus sensitive code including:
- Making explicit choices about consensus-sensitive decisions (voting via block-version, transaction version or bitcoin core version)
- Implementing and testing the alert mechanism for notifying operators of long consensus forks or other emergency notices
- Having process for selecting code version, upgrading and testing of consensus sensitive code.
- Having process for handling consensus impacting emergencies, such as unplanned forks, including process for freezing transaction processing during such emergencies.
We plan to offer a proposed draft (which I will introduce here first) within the next few weeks. Please hold us accountable for that. If you have ideas to add or are working on something similar, please let me know.
Thanks
Andreas
Michael Perklin, CBP CISSP CISA EnCE ACE
Crypto
Currency
Certification
Consortium
--
You received this message because you are subscribed to the Google Groups "CCSS Steering Committee" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ccss-steering-com...@googlegroups.com.
To post to this group, send email to ccss-steeri...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ccss-steering-committee/CAFmyj8zLbX5gEZGn4QFqEV3CDZErOcYWXm6XLVpn36nDQL2U-Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
To view this discussion on the web visit https://groups.google.com/d/msgid/ccss-steering-committee/A132AEFE-F2D9-4441-98D1-ADC8440664C2%40cryptoconsortium.org.