Published · Open-source release

DigiCoinLib 0.0.3: A stronger foundation for DigiByte Wallet

November 5, 2026 · DigiByte Wallet development news · 7-minute read

A meaningful wallet update does not always begin with a new button or screen. Sometimes it starts deeper in the software, making sure the technology behind a wallet stays dependable as devices and developer tools evolve.

DigiCoinLib 0.0.3 release: stronger compatibility and testing for DigiByte — DigiCoinLib 0.0.3 is available for developers.

Today we are announcing the publication of two updated open-source software packages: DigiCoinLib 0.0.3 and DigiCoinLib Flutter 0.0.3. These are developer tools used to help build DigiByte-compatible applications. They are not a new mobile wallet version, but they strengthen the foundation for future development.

This release is focused on three things that matter to anyone building or maintaining a cryptocurrency wallet: compatibility with today's software, dependable handling of DigiByte network information, and tests that can catch problems before software reaches users.

The short version: DigiCoinLib 0.0.3 improves the underlying tools developers rely on. Standard DigiByte mainnet wallet behavior was intentionally preserved. DigiByte Wallet 0.1.5 is a separate app update being prepared for release.

Why this work matters

Mobile operating systems and development tools change every year. An app that worked well with an older Android build system may become difficult to compile after the next tooling upgrade. Older tests can also give a false impression of reliability when they contain data copied from another cryptocurrency.

Those were practical issues we addressed. Instead of reinventing the software that signs DigiByte transactions, this update concentrates on the surrounding code: the parts that tell the library which DigiByte network it is working with, how optional key-derivation settings behave, and how the Flutter integration fits into a modern Android project.

The result is a cleaner, more maintainable starting point for future DigiByte wallet work. That helps development move forward while avoiding unnecessary changes to existing mainnet wallet behavior.

What's improved in plain English?

1. Better compatibility with newer Android development tools

Android's build system now expects information that older Flutter plugins did not always provide. In previous DigiCoinLib Flutter releases, this could stop a developer from compiling an otherwise valid Android app. Version 0.0.3 adds the required Android namespace and modernizes the example application.

What this means: developers have fewer avoidable obstacles when maintaining and updating DigiByte-powered apps. This does not mean that everyone needs to replace their current wallet today, or that the library alone delivers a new wallet version to app stores.

2. More accurate DigiByte test-network handling

Software developers should test payment and address-handling logic on non-production networks before trying it with real funds. We corrected a test-network address prefix and added built-in configurations for two additional DigiByte development networks, known as signet and regtest.

What this means: developers can create and check test addresses using settings that better match DigiByte Core. These configurations help with controlled testing; they do not automatically connect the app to a test network or scan it for transactions.

3. Correct behavior when developers choose special key settings

Wallet software turns recovery information into keys and addresses by following precise rules. One optional setting in the library previously appeared configurable but was silently ignored. We fixed that behavior, so developers who deliberately use a custom setting now get the result they requested.

What this means: the library behaves more predictably. Just as importantly, we kept the standard key-generation behavior unchanged, because switching the rules for an existing wallet could point it to completely different addresses.

4. Better tests for the DigiByte code that already exists

Some older tests still contained addresses and signatures inherited from a different cryptocurrency codebase. Those examples were replaced or corrected to use DigiByte-compatible test data, and new checks were added for network settings and wallet key behavior.

The core library passed 285 automated tests, and the release changes passed four GitHub CI checks. A test suite is never a substitute for real-world validation, but it is an important defense against accidental regressions.

What stayed the same?

We deliberately avoided changes to the basic rules used by existing DigiByte mainnet wallets. Mainnet address prefixes, the default master-key derivation method, and transaction serialization logic were preserved in this release. Existing signing algorithms and the Flutter loader's public API were not replaced.

That distinction matters. A library update should not casually change where a user's recovery phrase points or the form of a transaction simply to add a few new features. Preserving those defaults was a central design decision.

For wallet users: this is not a request to re-enter your recovery phrase, move your coins, or download an unofficial build. Never type your seed phrase into a website, support chat, price tracker, or software-release page.

What comes next for DigiByte Wallet?

While the developer library is now published, DigiByte Wallet 0.1.5 is being prepared as a separate mobile app update. The current release notes focus on updated security-related dependencies, improvements to iPhone startup and Apple Keychain handling, better readability with large text settings, and more sensible placement of ad banners.

These improvements are being validated in the wallet application. The wallet repository currently still references the older DigiCoinLib Flutter dependency, so this announcement does not claim that DigiCoinLib 0.0.3 is already integrated into the upcoming store build. Read the 0.1.5 preview for the app-specific details.

Why open source?

DigiCoinLib's source code, release history, and implementation changes are available for independent inspection. Other developers can review the fixes, reproduce the tests, suggest improvements, and build their own applications around the published packages.

We believe transparent engineering is particularly important for tools that may be used in self-custody software. Publishing source code does not guarantee that software is free from defects, but it does make independent review possible.

Download the current DigiByte Wallet app

The current DigiByte Wallet app remains available through its established App Store listing for iPhone and iPad, and for compatible Macs with Apple silicon. If you use an existing wallet, keep your recovery phrase stored safely offline and wait for an official app update rather than attempting to install developer libraries directly.

View DigiByte Wallet in the App Store

Developer details: technical changes and compatibility notes

Library version: digicoinlib 0.0.3; Flutter plugin digicoinlib_flutter 0.0.3.

DigiByte testnet Bech32 HRP corrected from tdgb to dgbt. This intentionally changes testnet address encoding.
Added Network.signet with dgbt and Network.regtest with dgbrt.
HDPrivateKey.fromSeed(seed, key: ...) now honors the explicitly supplied HMAC label. The standard BIP32 default Bitcoin seed remains unchanged; this is a standard name, not Bitcoin-only address generation.
Android namespace declared for the Flutter plugin; modern Gradle and Kotlin setup used for the example project.
DigiByte-specific fixtures and network compatibility tests added, with inherited fixtures corrected.
Mainnet prefixes, secp256k1 algorithms, transaction serialization and the public Flutter loader API were not intentionally changed.

See migration notes, validation notes, and the published package changelogs for complete technical detail.

Where to find the release

About DigiByte Wallet. DigiByte Wallet is a self-custody DigiByte application: users remain responsible for safeguarding their recovery phrases and private keys. For information about the wallet and official downloads, visit digibytewallet.org. Press and development inquiries: digibytewalletorg@gmail.com.