Skip to content

Changelog

Aggregated release notes across Navio repositories. Regenerated nightly.

All releases on GitHub

v0.1.7 — 2026-08-08

What's Changed

Full Changelog: https://github.com/nav-io/navio-core/compare/v0.1.6...v0.1.7

v0.1.6 — 2026-07-28

What's Changed

Full Changelog: https://github.com/nav-io/navio-core/compare/v0.1.5...v0.1.6

v0.1.5 — 2026-07-11

What's Changed

Full Changelog: https://github.com/nav-io/navio-core/compare/v0.1.4...v0.1.5

v0.1.4 — 2026-07-08

What's Changed

Full Changelog: https://github.com/nav-io/navio-core/compare/v0.1.3...v0.1.4

v0.1.3 — 2026-07-03

What's Changed

Full Changelog: https://github.com/nav-io/navio-core/compare/v0.1.2...v0.1.3

v0.1.2 — 2026-07-01

What's Changed

Full Changelog: https://github.com/nav-io/navio-core/compare/v0.1.1...v0.1.2

v0.1.1 — 2026-06-28

What's Changed

Full Changelog: https://github.com/nav-io/navio-core/compare/v0.1.0...v0.1.1

v0.1.0 — 2026-06-28

Navio Core version 0.1.0 Release Notes

Navio Core version 0.1.0 is now available from:

https://github.com/nav-io/navio-core/releases/tag/v0.1.0

This is the first stable release of Navio Core and the launch of the Navio mainnet. It is built on the Bitcoin Core codebase with BLSCT (Boneh-Lynn-Shacham Confidential Transactions) for private, confidential transfers.

Please report bugs using the issue tracker at GitHub:

https://github.com/nav-io/navio-core/issues

Mainnet Launch

This release activates the Navio mainnet. The mainnet genesis block was mined for this launch:

  • Genesis hash: 0af3c23ae1ac4910693b7187ac61641d16d1cf49cba7acf8649d48e831d86b13
  • Merkle root: 96f8dfcc3c433012bc9d4b42e85fe543936609f87fce2cc9d5484383ee2f9aaf
  • Timestamp: 2026-07-01 13:00:00 UTC (1782910800)

The genesis coinbase is a plain unspendable OP_RETURN output.

How to Install

Download the binaries for your platform and run the installer (Windows), copy naviod to /Applications (macOS), or copy naviod into your path (Linux).

Verify the signed checksums in SHA256SUMS / SHA256SUMS.asc before running.

Compatibility

Navio Core is supported and tested on operating systems using the Linux Kernel 3.17+, macOS 11.0+, and Windows 7 and newer. Other Unix-like systems may work but are not regularly tested.

Notable changes

  • BLSCT confidential transactions: confidential amounts and stealth (nav1...) subaddresses.
  • PoPS staking.
  • Network parameters finalized for mainnet launch (message start, default port 48470, address prefixes, nav bech32 modifier HRP for BLSCT addresses).

Credits

Thanks to everyone who contributed to this release, and to the Bitcoin Core developers whose work Navio Core is built upon.

v0.1rc36 — 2026-06-22

What's Changed

Full Changelog: https://github.com/nav-io/navio-core/compare/v0.1rc34...v0.1rc35

v0.1rc34 — 2026-06-21

What's Changed

Full Changelog: https://github.com/nav-io/navio-core/compare/v0.1rc33...v0.1rc34

v0.1rc33 — 2026-06-21

What's Changed

Full Changelog: https://github.com/nav-io/navio-core/compare/v0.1rc32...v0.1rc33

v0.1rc32 — 2026-06-07

Full Changelog: https://github.com/nav-io/navio-core/compare/v0.1rc30...v0.1rc32

v0.1-rc31 — 2026-06-24

v0.1rc30 — 2026-06-01

What's Changed

All releases on GitHub

v0.1.29 — 2026-08-14

No changelog entry for 0.1.29.

v0.1.28 — 2026-07-27

Added

  • mintNfts(): mint several NFTs from a collection in a SINGLE transaction (one broadcast, one fee, one block). Per-NFT metadata and optional per-NFT destination addresses; returns the full NFT token ids in input order.
  • getAssetBalances NFT entries now carry nftMetadata — the metadata the specific NFT was minted with (from the collection's on-chain minted list) — alongside the collection metadata/totalSupply.

Fixed

  • Token-registry lookup failures were cached for the client's lifetime, so a single transient server error left assets without metadata for the rest of a long-lived session ("received NFT has no metadata"). Misses now expire after 5 minutes, and NFT-collection entries refresh on the same interval so newly minted NFTs pick up their metadata; fungible collection info stays cached forever (it is immutable).

Full Changelog: https://github.com/nav-io/navio-sdk/compare/v0.1.27...v0.1.28

v0.1.27 — 2026-07-22

Fixed

  • NAV balance no longer reads 0 while the wallet's own change is unconfirmed. Mempool processing stored the change output's token id as TokenId.serialize()'s NAV spelling (zero hash + ffff… no-subid marker), which the databases' NAV balance filters (null / bare zero hash) did not match — so after any send or mint the entire balance disappeared until the next block. Token ids are now normalized to null for NAV at the single write choke point, and both database filters additionally accept the legacy spelling so existing wallet databases heal without a resync.

Full Changelog: https://github.com/nav-io/navio-sdk/compare/v0.1.26...v0.1.27

v0.1.26 — 2026-07-21

Fixed

  • Minting an NFT no longer kills the process. Mint outputs carry their amount as a transparent value and an empty range proof, and RangeProof.recoverAmounts on an empty proof terminates the process with an uncatchable native exception. The mempool-processing path that runs right after every own broadcast called it unconditionally, so any app died the moment it minted an NFT (the mint transaction itself was already broadcast and confirmed — only the local process crashed). All three amount-recovery sites now detect the empty proof and use the transparent value instead.
  • Investigation of the same incident (testnet block 48020, the network's first NFT mint — made with this SDK's README example) uncovered the companion server-side bug: the ElectrumX indexer over-read empty range proofs by 304 bytes, corrupting the served keys, output hashes, and raw transaction for mint-carrying blocks. Fixed in nav-io/electrumx (rfq-swap-bridge branch); affected servers need a reindex of blocks containing mint outputs. The 0.1.25 malformed-key guard keeps wallets syncing past still-corrupted servers in the meantime.

Full Changelog: https://github.com/nav-io/navio-sdk/compare/v0.1.25...v0.1.26

v0.1.25 — 2026-07-21

Fixed

  • Sync no longer aborts permanently on outputs whose BLSCT keys are not valid curve points. Anyone can broadcast such an output (testnet block 48020 contains one); the server serves its keys verbatim, and PublicKey.deserialize threw, killing every sync attempt at that block — wallets stalled and re-scanned from their creation height in a loop (reported as "stuck at 48019, rolls back to 46700"). An output with invalid keys is spendable by no wallet, so it is now skipped and the rest of the block processes normally.

Full Changelog: https://github.com/nav-io/navio-sdk/compare/v0.1.24...v0.1.25

v0.1.24 — 2026-07-21

Added

  • publicTokenId on CreateCollectionResult, MintAssetResult, and CreatedCollectionInfo: the public on-chain token id (hash of the token public key, computed locally) — the id explorers, gettoken, and the balance methods report. Collections from listCreatedCollections can now be joined directly against getAssetBalances/getTokenBalances rows. collectionTokenId (the creation id, needed for minting on any backend) is unchanged.
  • getAssetBalances (and therefore getTokenBalances/getNftBalances) entries now carry the collection metadata and totalSupply when resolvable — from the wallet's own creation records, or from the server's token registry, cached for the client's lifetime (collection info is immutable). One call returns balances and display metadata. Pass { includeMetadata: false } to skip.

Full Changelog: https://github.com/nav-io/navio-sdk/compare/v0.1.23...v0.1.24

v0.1.23 — 2026-07-21

Added

  • listCreatedCollections(): list the token/NFT collections this wallet created. Creations are recorded in the wallet database at broadcast time; for restored wallets the method additionally discovers collections from chain in two ways — every distinct held token is looked up via blockchain.token.get_token, and the wallet's own transactions are scanned for create-token predicates (the create transaction spends the wallet's NAV, so its hash is known after a sync — this recovers collections that were created but never minted or held). A collection is reported when its on-chain token public key re-derives from the wallet's seed (the same ownership proof minting uses). Returned collectionTokenId is the creation id, directly usable with mintToken/mintNft. { discoverFromChain: false } skips the chain passes.
  • Wallet database: new created_collections table (SQLite) / store (IndexedDB, schema v2 — upgrades automatically).

Full Changelog: https://github.com/nav-io/navio-sdk/compare/v0.1.22...v0.1.23

v0.1.22 — 2026-07-21

Added

  • createTokenCollection accepts initialMint: { address, amount } to mint the first supply of the new token in the same transaction as the collection creation (consensus executes output predicates in order, so the collection is registered before the mint is validated). Result gains mintedAmount. Without this, a mint can only be broadcast after the collection transaction has confirmed — two separate transactions cannot land in the same block because mempool validation cannot see an unconfirmed collection.
  • This CHANGELOG.md; the GitHub release body now carries the version's changelog section.

Full Changelog: https://github.com/nav-io/navio-sdk/compare/v0.1.21...v0.1.22

v0.1.21 — 2026-07-21

Full Changelog: https://github.com/nav-io/navio-sdk/compare/v0.1.20...v0.1.21

v0.1.20 — 2026-07-08

Full Changelog: https://github.com/nav-io/navio-sdk/compare/v0.1.18...v0.1.20

v0.1.19 — 2026-07-07

What's Changed

New Contributors

Full Changelog: https://github.com/nav-io/navio-sdk/compare/v0.1.17...v0.1.19

v0.1.18 — 2026-07-07

What's Changed

New Contributors