Skip to content

Releases: attestantio/dirk

Release 1.2.0

28 Aug 14:43
e9fd39f
Compare
Choose a tag to compare

This is a feature release of Dirk. It focuses on long-term performance of signing operations, along with maintenance items.

Changes include:

  • add Amazon Secrets Manager (ASM) confidant
  • provide clearer error message on configuration issues
  • update tracing implementation to use opentelemetry
  • support batched wallets

The full changelog can be found at https://github.com/attestantio/dirk/blob/master/CHANGELOG.md

A note on upgrading

Dirk 1.2.0 instances are compatible with Dirk 1.1.0 instances. As such, in a multi-instance Dirk environment it is possible to upgrade individual Dirk instances to confirm their correct operation without upgrading all instances at the same time. A potential upgrade strategy is to upgrade a minority of instances (for example in a 2-of-3 setup upgrading a single instance) and confirm via metrics and/or logs that the instance operating correctly before upgrading further instances.

Additional configuration parameters

This release provides the following additional configuration parameters:

  • process.generation-timeout the time allowed for the distributed key generation operation before erroring (default 70s)

Release 1.1.0

10 Dec 10:56
v1.1.0
26d103a
Compare
Choose a tag to compare

This is a feature release of Dirk. It focuses on long-term performance of signing operations, along with maintenance items.

Changes include:

  • garbage collect the slashing database on startup to reduce on-disk size
  • provide release metric in dirk_release
  • use internal account cache for both positive and negative caching
  • run signing rules in parallel, increasing responsiveness for large requests
  • use hierarchical log levels in configuration; details in the configuration docs

Release 1.0.2

02 Feb 21:34
v1.0.2
350cabd
Compare
Choose a tag to compare

This is a maintenance release for Dirk 1.0.x. It is recommended that users upgrade to this version.

Changes in this release:

  • upgrade dependencies

Release 1.0.1

19 Jan 09:13
v1.0.1
60703ff
Compare
Choose a tag to compare

This is a maintenance release for Dirk 1.0.x. It is recommended that users upgrade to this version.

Changes in this release:

  • Do not ignore storage-path configuration value
  • Move server.storage-path to storage-path
  • Explicitly close database on shutdown, with delay to allow completion
  • Wrap batch account locking with a parent mutex

Release 1.0.0

26 Nov 20:24
v1.0.0
7ec1518
Compare
Choose a tag to compare

The is the initial mainnet release. Further releases in the 1.0.x series will be made as/when bug fixes and performance improvements are required, with additional features coming in 1.x.0 releases.

Release 0.9.6

17 Nov 11:55
v0.9.6
2f19dec
Compare
Choose a tag to compare

This is a pre-mainnet release containing the following updates:

  • Update slashing protection import/export format to version 5

It is expected that a mainnet release will follow within 7 days.

Release 0.9.3

12 Nov 10:51
v0.9.3
ce87314
Compare
Choose a tag to compare
v0.9.3

Update dependencies.

Release 0.9.2

08 Nov 20:34
v0.9.2
17411eb
Compare
Choose a tag to compare
v0.9.2

Remove go-ssz.

Release 0.9.1

24 Oct 07:41
v0.9.1
3de7e6f
Compare
Choose a tag to compare

This is a maintenance release. Changelog:

  • Ensure GRPC service shuts down on context cancel
  • Add --version flag to print software version

Release 0.9.0

17 Oct 15:07
v0.9.0
39636ca
Compare
Choose a tag to compare

This is a feature release. Main features are:

  • support for the slashing protection interchange format, and related commands to import and export the data
  • support for the eth2-signer-api multisign API for attestations

Changelog:

  • Use fastssz for calculating hash tree roots
  • Add endpoint to sign multiple attestations in a single call
  • Provide hard-coded daemon for testing (see testing directory)
  • Add commands to import and export slashing protection data
  • Provide additional trace logging for distributed key generation
  • Enforce requirement that peer names cannot be the same
  • Exit early in distributed key generation if execution fails
  • Allow process.generation-passphrase to be a Majordomo URL
  • Add comments to rules functions
  • Log location of wallet stores on startup