Get Involved
And help develop Technical Standards for Bitcoin SV


There are 3 ways to get involved in developing Bitcoin SV technical standards:

Register as contributor

Individual or groups of industry players are encouraged to participate in the standardisation lifecycle via diverse roles:

ProposerThe individual or group of industry players who collectively identify the need for a standard. They submit a proposal to form a working group to help to improve Bitcoin SV utility.
AuthorsIndividuals from the industry tasked with writing the standard. Proposers are the preferred candidates for the role of Author. However, the TSC will, on occasion, welcome expressions of interest to join a working group as an author from another source. These opportunities will be published in the standard catalogue under In Consideration.
ReviewersSelected individuals from the industry who will confidentially review drafts produced by authors prior to public review. Standards in consideration allowing expressions of interest to join a workgroup as reviewers will be published in the standard catalogue under In Consideration.
PublicStandards at the public review stage are open for comments. To comment on them, register, and then, visit the standards catalogue.

How it works?

Now that the Bitcoin SV protocol is set in stone, we can start developing a library of Bitcoin SV technical standards for the benefit of all. Using these technical standards will save the need for multiple organisations to solve the same problems over and over. The technical standards are analogous to software design patterns in that they provide solutions to common problems and are based on solid industry experience and expertise. You too can contribute to the future Bitcoin SV ecosystem by offering your technical skills and knowledge to help build a new technical standard or influence an existing Bitcoin SV standard.

The Technical Standards Committee (TSC), consisting of seasoned Bitcoin SV professionals, that govern the development of standards and work with a wide variety of authors and reviewers from across industry, to produce world-class technical content.

A major strength of Bitcoin SV technical standards is that they are developed by the people that need them. Industry experts are involved at all stages of the standard development process, from deciding whether a new standard is needed, to defining all the technical content and reviewing and monitoring industry adoption once published.

Getting involved in this process can bring significant advantages to you and to your business.

For example:

  • Give you early access to information that could shape the market of the future.
  • Give your company a voice in the development of standards.
  • Boost you personally knowing that your contributions have been recognised.
  • Help to keep market access open.

Technical standards cooperation

Development of technical standards is made from 3 levels of cooperation: Governance, Admin Support and the actual standard development.

Level 1 – Governance. The Technical Standard Committee will provide governance to all working groups, developing standards. TSC members commit to supporting working groups with processes, tooling and resources when the proposal from industry is aligned with the goals of the TSC. The committee is focused on nurturing and publishing the standards that will add the most value to the Bitcoin ecosystem.

Level 2 – Admin Support. Working groups will receive administrative support from a dedicated project coordinator. The project coordinator will ensure all working group members have open communication channels and keep within the necessary stage timelines. The project coordinator will also ensure all documentation is available and easily shared within the group.

Level 3 – Standards Development. Standards are developed by working groups of experts from across industry. Working groups consist of a sponsor (a full TSC committee member) and suitable authors and reviewers. Proposers of standards are the preferred authors; however, a suitable author can be sourced by the TSC and project coordinator if more appropriate.