JuneoJS: why we wrote the SDK before the wallets

Without a shared SDK, you fix the same bug everywhere.

Building several blockchain products without a shared SDK means accepting that you will fix the same bugs in several places.

That is exactly what we wanted to avoid.

Before the web wallet, the mobile app, and the Chrome extension, we wrote JuneoJS.

JuneoJS is an open-source TypeScript library that exposes the Juneo network primitives: keys, transactions, signatures, node interactions, cross-chain assets.

The alternative was simple: wire each product directly to the node APIs. On paper, it is faster.

In practice, that is how the same logic ends up duplicated across the web wallet, the mobile app, the Chrome extension, and the on-chain bots.

We preferred a single package. One fix benefits every product. A network change becomes available everywhere. The surface for bugs stays manageable.

The point was never "to have an open-source SDK on npm". The point was to keep the entire application stack from becoming fragile.

In a blockchain ecosystem, the SDK is not a bonus. It is often the layer that decides whether products stay reliable and maintainable.

If you are building a protocol, a wallet stack, or several products around the same network, that is often where the debt begins.