The Bitxor SDK is the primary software development tool to create Bitxor components, such as additional tools, libraries, or applications. It enables developers to focus on their product rather than on the specific API details due to its higher abstraction.
The Bitxor SDK shares the same design between programming languages to accomplish the next properties:
Fast language adaptation: For example, there is a Bitxor SDK for Java, but you need to work on C++. As both SDKs share the same design, you could re-write the library faster, adapting the syntax to your language. The same principle also applies to code examples, projects, applications…
Cohesion/shared knowledge across developers: Every developer should be able to change between projects that use Bitxor. By sharing the same design, we also share the same best practices among projects.
Fast SDK updates: Migrating any improvement from a Bitxor SDK to the other is faster. Also, if any bug appears in one language, it is quicker to check and fix it.
Language |
Repository |
Reference |
---|---|---|
TypeScript& JavaScript SDK |
||
Java SDK |
Learn how to use Bitxor’s SDK following the guided implementation examples.
If you want to create a new SDK, check the development guidelines.
Bitxor developers have created other libraries that improve and add new features on top of Bitxor.
Name |
Description |
---|---|
Transferable, updatable, branded, and conjointly owned blockchain notarizations. |
|
Hierarchical-deterministic wallets library for Bitxor. |
|
QR library for Bitxor. |
|
URI Scheme library for Bitxor. |
|
Implementing Shamir’s secret sharing on Bitxor. |
To make a library official, the library should be proposed through the BITXOR Improvement Proposal process.
The reason behind the BITXOR Improvement Proposal is to ensure that:
The specification has been discussed and accepted.
The new library is reviewed, tested and shared among Bitxor developers.
The library is compatible with third-party projects that uses the same specification.