Skip to content

Releases: kaspanet/rusty-kaspa

Testnet 11 Only v0.15.4

29 Nov 06:58
Compare
Choose a tag to compare
Pre-release

WARNING: INTENDED FOR USE IN TESTNET 11 ONLY

This is a special release with code not in the mainline yet. It is intended to hardfork the testnet-11 environment and should only be used by Testnet-11 node maintainers.

The TN11 HF includes:

  • Enabling KIP10
  • Switching KIP9 to use the Beta version in consensus
  • Enabling Payloads for transactions

In addition, this includes all the optimizations that we have been working on which will allow us to determine a minimum recommended hardware spec for 10bps in mainnet.

Instructions for Node Maintainers

  • This is the first release that includes the database version upgrade introduced in #494. When you run this version with an existing datadir, you may be asked to upgrade your database version in CLI. To proceed, type y or yes and hit enter. Alternatively, you can run this version with a --yes flag to skip the interactive question.
    • This database upgrade is a one-way path, which means after updating your datadir to the new version, you won't be able to go back to an earlier version.

Instruction to build from source

  1. Git pull and checkout the kip10-tn11-hf branch
  2. Build your binary from there. This release is on the commit 14b1e10

Release v0.15.2

20 Sep 11:37
9fae376
Compare
Choose a tag to compare

Released mainly for Integrators using GetVirtualChainFromBlock

NOTE: If you do not use GetVirtualChainFromBlock in your integration, you do not need to update to this version.

This release updates the GetVirtualChainFromBlock so that it operates in batches. This solves an issue where the call to GetVirtualChainFromBlock would previously take a long time to complete if the client has to sync virtual chain state from a deep chain block after a period of being unsynced. Each call will now return very promptly, but it also means you now have to call GetVirtualChainFromBlock multiple times if you're syncing from a deep chain block.

To take advantage of this new batching mechanism, you only need to make sure that you continue calling GetVirtualChainFromBlock until your software has caught up to the tips of the network. For reference, the pseudo-code is:

startHash = <the_last_hash_you_synced_from>
isCatchingUp = true

// Catch-Up code. Expecting to do faster catch up logic here
while isCatchingUp:
  batch = GetVirtualChainFromBlock(startHash, includeTransactionIds: true)
  // Do your processing with batch
  // ...
  startHash = batch.added[<last_element_index>]

  if len(batch.added) < 10:
    // if the response was batched it will contain at least 10 chain blocks
    // (because we limit the number of merged blocks by mergeset limit x 10),
    // otherwise, we've caught up and can proceed with normal batch processing
    isCatchingUp = false

// Continue your normal pace of processing next batches with GetVirtualChainFromBlock
// ...

What's Changed

  • Fix WASM interface typo for normalBuckets and lowBuckets in IFeerateBucket by @Cryptok777 in #557
  • Fix new gRPC methods to use camel case (non-breaking change) by @michaelsutton in #560
  • virtual chain from block batching. by @D-Stacks in #454
  • A few CLI rpc query fixes by @michaelsutton in #563
  • Deploy linux binary without musl in its name + various minor miscellaneous things towards v0.15.2 by @michaelsutton in #564

New Contributors

Full Changelog: v0.15.1...v0.15.2

Release Candidate v0.15.2-rc1

19 Sep 20:41
b14537f
Compare
Choose a tag to compare
Pre-release

Note to Integrators using GetVirtualChainFromBlock

IMPORTANT: If you do not use GetVirtualChainFromBlock in your integration, you do not need to update to this version.

This release updates the GetVirtualChainFromBlock so that it operates in batches. This solves an issue where the call to GetVirtualChainFromBlock would previously take a long time to complete if the client has to sync virtual chain state from a deep chain block after a period of being unsynced. Each call will now return very promptly, but it also means you now have to call GetVirtualChainFromBlock multiple times if you're syncing from a deep chain block.

To take advantage of this new batching mechanism, you only need to make sure that you continue calling GetVirtualChainFromBlock until your software has caught up to the tips of the network. For reference, the pseudo-code is:

startHash = <the_last_hash_you_synced_from>
isCatchingUp = true

// Catch-Up code. Expecting to do faster catch up logic here
while isCatchingUp:
  batch = GetVirtualChainFromBlock(startHash, includeTransactionIds: true)
  // Do your processing with batch
  // ...
  startHash = batch.added[<last_element_index>]

  if len(batch.added) < 10:
    // if the response was batched it will contain at least 10 chain blocks
    // (because we limit the number of merged blocks by mergeset limit x 10),
    // otherwise, we've caught up and can proceed with normal batch processing
    isCatchingUp = false

// Continue your normal pace of processing next batches with GetVirtualChainFromBlock
// ...

What's Changed

  • Fix WASM interface typo for normalBuckets and lowBuckets in IFeerateBucket by @Cryptok777 in #557
  • Fix new gRPC methods to use camel case (non-breaking change) by @michaelsutton in #560
  • virtual chain from block batching. by @D-Stacks in #454

New Contributors

Full Changelog: v0.15.1...v0.15.2-rc1

Stable Mainnet Release & WASM SDK v0.15.1

11 Sep 18:16
f335376
Compare
Choose a tag to compare

Kaspa on Rust — Mempool-Focused Release (second stable release)

This version focuses on introducing mempool features required for users and wallets for adopting to fee market conditions.

The main mempool features include:

  • Replace-By-Fee (RBF)
  • A fee estimation API based on real-time mempool state
  • A new mempool evict policy based on fee rate

The version also includes the following major changes:

  • Major performance enhancements in the block template transaction selection algorithm. This operation now takes only ~100 microseconds even under heavy load, and that is achieved without compromising on the most profitable selection strategy.
  • Important improvement in header processing performance
  • Many more accumulated enhancements, improvements and non-critical fixes

It is highly recommended that miners and pools gradually shift to this version both for stability reasons and for better supporting the network under upcoming expected fee market conditions.

What's Changed

New Contributors

Full Changelog: v0.14.1...v0.15.1

Release Candidate v0.15.1-rc4

10 Sep 08:04
d1dc5dd
Compare
Choose a tag to compare
Pre-release

A minor RC update without node-related changes. Includes an important hotfix to the Wasm SDK as well as removal of openssl dep which fixes a problem in the Linux release binary.


Version will show as 0.14.7


What's Changed

  • WIP: Updates for 15-rc3 by @aspect in #546
  • Replace openssl with rustls + ring + webpki_roots by @elichai in #547
  • Fix CLI not showing incorrect URL on connect + add disconnect() before connect() by @aspect in #549
  • Simple wRPC client example by @thesheepcat in #550

New Contributors

Full Changelog: v0.15.1-rc3...v0.15.1-rc4

Release Candidate v0.15.1-rc3

06 Sep 03:45
afbcf9e
Compare
Choose a tag to compare
Pre-release

What's Changed

  • Transaction pool -- fix rare cases where byte size tracking was inaccurate by @michaelsutton in #535
  • Feerate estimator outliers: capture block slot by the specific mass of the outlier transaction by @michaelsutton in #537
  • Refactoring of mass calculator utilities by @aspect in #538
  • Various miscellaneous changes towards 0.15.1 RC2 by @michaelsutton in #543
  • Add optional proxy socket limit info to utils::SystemInfo() by @aspect in #544
  • Deprecate zigbuild and glibc in favor of static musl binaries for Linux builds. by @starkbamse in #541
  • Change directory back to repo root. by @starkbamse in #545
  • Fix Rust 1.81 lints

Full Changelog: v0.15.1-rc1...v0.15.1-rc3

Release Candidate v0.15.1-rc1

28 Aug 00:48
c839a9d
Compare
Choose a tag to compare
Pre-release

What's Changed

New Contributors

Full Changelog: v0.14.1...v0.15.1-rc1

Stable Mainnet Release & WASM SDK v0.14.1

05 May 18:28
4364f37
Compare
Choose a tag to compare

Kaspa on Rust — First Stable Release

What's Changed

New Contributors

Full Changelog: v0.13.6...v0.14.1

Mainnet RC v0.13.6

10 Apr 19:47
1eebd4d
Compare
Choose a tag to compare

What's Changed

New Contributors

  • @orgr made their first contribution in #429

Full Changelog: v0.13.4...v0.13.6

v0.13.4

24 Jan 12:24
b746950
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v0.13.3...v0.13.4