BSV Blockchain is pleased to announce that the Software Development Kit (SDK) for JavaScript and TypeScript is now available. The TypeScript SDK is designed to provide an updated and unified core library for developing scalable applications on the BSV blockchain. This SDK provides a replacement for the previously popular bsvjs library, which is no longer maintained. The library enables developers to build applications with a peer-to-peer approach in mind. It makes Simplified Payment Verification (SPV) easy, which enables privacy and scalability.
The launch of the new SDK forms part of the wider BSV Blockchain Libraries Project, which aims to structure and maintain a middleware layer of the BSV blockchain technology stack. By facilitating the development and maintenance of core libraries, it serves as an essential toolkit for developers looking to build on the BSV blockchain.
Below, Darren Kellenschwiler (Technical Lead of Utilisation) gives an overview of the new SDK and what to expect from his team going forward.
Can you give a brief explainer on what the TypeScript SDK is and how it will benefit more developers?
‘It’s a core library for application development which provides a set of convenient and intuitive developer interfaces for building and validating transactions and related data structures you’ll need while building on the BSV blockchain,’ said Kellenschwiler.
Why TypeScript over other languages?
‘JavaScript is among the most popular languages with developers building applications on BSV. TypeScript was chosen to gain the benefits of static types and interface abstractions while being able to compile down to JavaScript for browsers and backend projects alike. IDEs can better hint how you should use each function, what arguments it’s expecting and what may be causing an error when debugging. Coding AI assistants also have more context to go on, so auto-completions will be more likely to be accurate and helpful,’ said Kellenschwiler.
He added that the TypeScript SDK has been launched, with plans to launch both Go and Python SDKs within the year.
What is the testing process like for the TypeScript SDK?
Kellenschwiler noted that automated testing is part of the library build process, with 88% test coverage thus far. ‘The test vectors were gathered from previous libraries and SVnode to ensure everything built by the library will function on-chain. He said efforts will continue towards 100% coverage and general maintenance in line with protocol stewardship.
What’s next?
The project team will release a wealth of associated educational materials in the coming weeks and months so that developers can take full advantage of the new SDK. He added that a Go SDK is already underway and that community feedback nominated Python as the one to tackle after that.
The Utilisation team are considering which languages ought to come next in this effort to facilitate a common understanding across programming languages and ensure there are well-maintained libraries for developers coming from a variety of professional backgrounds.
The push for standardised open-source libraries comes with the promise of higher-quality products across the ecosystem. The aim is to encourage businesses to move towards best practices by offering the solution without vendor lock-in. It then starts making economic sense for them to contribute to the libraries with their developers. This should also grow the overall talent pool capable of building scalable applications on the BSV blockchain.
The focus on standardisation is not just about creating a uniform codebase; it’s about cultivating a competitive yet cooperative array of innovators who can help realise the full potential of blockchain technology. By clarifying the open-source governance and guidelines, BSV Blockchain is moving toward open innovation by leveraging the involvement of key players acting for their mutual benefit.
Developers are encouraged to contribute to the open-source libraries and their feedback will be reviewed and accepted by those responsible for library repositories aligned with open-source guidelines and standards.