The Bitcoin SV Technical Standards Committee (TSC) roadmap is designed to summarise the current standardisation landscape for the Bitcoin SV ecosystem. The roadmap aims to provide clear technical direction for the industry at large, in line with the committee’s mission to promote technical excellence and improve the utility of Bitcoin SV by enhancing interoperability through standardisation. It is intended to help people navigate emerging standards and includes several proposed areas for future development based on feedback received from stakeholders. It also lists some prior art, in addition to proposals for consideration.
Standards listed under prior art or in consideration in the roadmap have not been proposed for development, rather, these are commonly adopted ways of solving a problem that could be adapted into a standard, as well as proposals that could be considered for standardisation in the future. The TSC does not decide when to develop a new standard; the process is industry-driven. Individuals or companies who wish to see these proposals being actioned are encouraged to come forward and submit a proposal for consideration.
Read more about how to get involved.
As an organising body, the purpose of the Bitcoin SV Technical Standards Committee (TSC) is to facilitate industry collaboration; its success relies on the participation of industry stakeholders and ecosystem businesses.
In the development of the roadmap, the TSC extended several open invitations for interested stakeholders to submit feedback, which was was followed by a public review of the amended roadmap. The stakeholders’ comments and feedback from the public review have defined the final roadmap content and serve as supporting data for the plans and goals that the roadmap details.
It is important to note that the roadmap is a living document; monitoring and updating the roadmap is essential, with a formal review scheduled to take place every six months. In conjunction with the formal review process, TSC members will, on an ongoing basis, review and reassess the priorities and dependencies of the TSC with a separate matrix document.