Skip to content
This repository has been archived by the owner on Mar 1, 2024. It is now read-only.

Releases: subspace/pulsar

v0.8.0-alpha

10 Feb 17:54
ed48e9d
Compare
Choose a tag to compare

Description

This is the first release of pulsar compatible with gemini-3h. This release is updated with gemini-3h-2024-feb-05 snapshot of monorepo without the farmer metrics support.

Please see release notes of gemini-3h-2024-feb-05 snapshot for more information: https://github.com/subspace/subspace/releases/tag/gemini-3h-2024-feb-05

Full Changelog: v0.7.4-alpha...v0.8.0-alpha

v0.7.4-alpha

19 Jan 14:09
d55065a
Compare
Choose a tag to compare

Description

This release fixes a critical bug in pulsar that was not allowing it to sync to the tip.

What's Changed

  • Enable subspace block relay for gemini3g and devnet by @ParthDesai in #288

Full Changelog: v0.7.3-alpha...v0.7.4-alpha

v0.7.3-alpha

18 Jan 09:16
062f6b0
Compare
Choose a tag to compare

Description

This release fixes critical bug preventing pulsar to be farm and make it up-to-date with gemini-3g-2024-jan-08 snapshot.

What's Changed

  • Bug where pulsar is panicking after syncing is fixed in #284. Please note that the solution employed to fix this issue removes votes and rewards counting functionality from pulsar. So, it won't be able to display votes and rewards accumulated while it is running.
  • Update the pulsar to be up-to-date with gemini-3g-2024-jan-08 snapshot. Changes can be seen here: https://github.com/subspace/subspace/releases
  • As part of the update, we added numa support. It can be enabled by building the pulsar with numa feature enabled.

Full Changelog: v0.7.2-alpha...v0.7.3-alpha

v0.7.2-alpha

03 Jan 16:06
e8a1f9b
Compare
Choose a tag to compare

Description

This release upgrades pulsar to gemini-3g-2023-dec-22 monorepo snapshot from gemini-3g-2023-dec-01 snapshot. It is the bugfix release supporting Gemini3g network.

What's changed? (Major changes copied from monorepo release)

  • Farmer processes archived segments in more graceful way fixing large gaps in block production and massively reducing network usage spikes
  • fix for farm locking that prevents farmer from starting (--no-info was a workaround, shouldn't be necessary anymore)
  • --farm-during-initial-plotting now takes true/false argument and defaults to true on machines with more than 8 logical cores, which means most users shouldn't need to specify it anymore 🎉
  • only process canonical consensus blocks by operator, decreasing computation required and avoiding crashes in case there are many forks
  • acquire farm lock on the farmer in order to prevent accidental use of the same farm by two farmer instances that will inevitably lead to slashing and other issues
  • graceful shutdown in case piece cache sync is still in progress (fixed subspace/subspace#2241)
  • avoid sync errors on node restart if stopped at unfortunate block (subspace/subspace#2336)

v0.7.1-alpha

02 Dec 10:39
f1702c7
Compare
Choose a tag to compare

Description

This release upgrades pulsar to gemini-3g-2023-dec-1 monorepo snapshot. It is the bugfix release supporting Gemini3g network.

What's changed? (Copied from monorepo release)

This release improves networking by maintaining the same number of connections, but preferring more useful (incoming) connections when approaching limits of connected peers.

v0.7.0-alpha

25 Nov 04:41
0a21528
Compare
Choose a tag to compare

Description

This release upgrades pulsar to gemini-3g-2023-nov-21 monorepo snapshot. It is the first release supporting Gemini3g network.

What's Changed

  • New version of the network includes major upgrades to the protocol like Proof of Time as well as various security enhancements and optimizations across the board.
  • Lots of networking fixes/optimizations.
  • Detailed changes in monorepo from last gemini-3f release to latest gemini-3g release (gemini-3g-2023-nov-21) are described here: https://github.com/subspace/subspace/releases

Known issues

It is known that sync can get stuck in some cases on node restart. Give it 30 minutes and if there is no progress in 30 minutes restart the node. This was happening on all Gemini 3f releases and we are still looking into it.

Full Changelog: v0.6.14-alpha...v0.7.0-alpha

v0.6.14-alpha

10 Oct 12:58
27e8849
Compare
Choose a tag to compare

Description

This PR updates pulsar to use latest monorepo snapshot gemini-3f-2023-oct-6

Changelog:

  • Improves auditing performance on Windows to approximately the level of sep-25 release while retaining most other optimizations.
  • Networking tuning that should improve node sync and plotting performance.

v0.6.13-alpha

04 Oct 17:59
0ec0a5c
Compare
Choose a tag to compare

Description

This release updates pulsar to sdk with gemini-3f-2023-oct-4

What's changed?

This release improves auditing performance on large farms and reduces peak memory usage during plotting/replotting.

v0.6.12-alpha

04 Oct 09:12
a545550
Compare
Choose a tag to compare

Description

This release updates pulsar to be up-to-date with gemini-3f-2023-oct-3 monorepo snapshot.

Notable changes:

  • This release fixes solution sorting order, while last release was supposed to improve network security, it didn't because highest quality solution was still not preferred, actually the opposite happened in practice.

Link to the monorepo snapshot: https://github.com/subspace/subspace/releases/tag/gemini-3f-2023-oct-03

v0.6.11-alpha

02 Oct 08:03
2df851c
Compare
Choose a tag to compare

Description

This release updates the pulsar to use SDK up-to-date with gemini-3f-2023-oct-1 monorepo snapshot.

This release brings farmer tuning and has a minor improvement that should help to reduce forking/improve apparent space pledged:

  • better thread management for plotting/farming (configurable with new CLI options)
  • replotting will only use half of the threads by default to not impact farming as much (configurable with new CLI options)
  • memory-mapped I/O was replaced with regular file operations that should fix apparent large memory usage on Windows and improve performance/reduce overhead on all platforms
  • prefer higher quality solution rather than the first one