Skip to content

Releases: software-mansion/starknet-validator-attestation

v0.5.2

Choose a tag to compare

@github-actions github-actions released this 11 Nov 12:37
v0.5.2
f1c807e

This is a minor release adding more controls over the transaction tip used when submitting attestations. The tip is now calculated like this: MAX(latest_median_tip * ${tip_boost}, ${minimum_tip}) where latest_median_tip is the median value of tip in the latest block (at the time of submission) and tip_boost and minimum_tip is controllable by the --tip-boost and --minimum-tip CLI arguments.

What's Changed

Full Changelog: v0.5.1...v0.5.2

v0.5.1

Choose a tag to compare

@github-actions github-actions released this 26 Sep 13:20
v0.5.1
a5a9487

This is a minor release adding a check for the version of the JSON-RPC API when starting up, plus a new metric (validator_attestation_attestation_confirmations_observed_count) for the total number of attestation confirmations observed for the configured staker.

What's Changed

  • feat: check JSON-RPC API compatibility upon starting up by @kkovaacs in #58
  • chore(cargo): upgrade dependencies by @kkovaacs in #60
  • feat(metrics): add new metric for total confirmations observed by @kkovaacs in #61
  • chore: bump version to 0.5.1 by @kkovaacs in #62

Full Changelog: v0.5.0...v0.5.1

v0.5.0

Choose a tag to compare

@github-actions github-actions released this 01 Sep 07:01
v0.5.0
c12ca5c

Major changes

  • ⚠️ This version of the tool requires access to a JSON-RPC 0.9.0 API. We have tested the tool with Pathfinder 0.20.0. Please make sure you upgrade your Starknet JSON-RPC URLs (should now end in v0_9). ⚠️
  • Starknet 0.14.0 has introduced a fee market. The attestation tool now uses a non-zero tip value for attestation transactions. The median tip value of recently included transactions is used to improve the chance of getting the attestation transactions included.

What's Changed

Full Changelog: v0.4.0...v0.5.0

v0.4.0

Choose a tag to compare

@github-actions github-actions released this 24 Jul 11:49
v0.4.0
7b17f5e

What's Changed

New Contributors

Full Changelog: v0.3.3...v0.4.0

v0.3.3

Choose a tag to compare

@github-actions github-actions released this 20 Jun 05:43
v0.3.3

What's Changed

  • Use Websocket keep-alives to avoid timeout problems with subscriptions by @xJonathanLEI in #29
  • Install TLS root certificate package in the Docker image by @kkovaacs in #30

Full Changelog: v0.3.2...v0.3.3

v0.3.2

Choose a tag to compare

@github-actions github-actions released this 17 Jun 13:09
v0.3.2

What's Changed

  • Fix TLS connection setup, allowing using HTTPS and WSS node URLs.

Full Changelog: v0.3.1...v0.3.2

v0.3.1

Choose a tag to compare

@github-actions github-actions released this 05 Jun 07:36
v0.3.1

What's Changed

  • Added contract address for attestation contract on Mainnet.

Full Changelog: v0.3.0...v0.3.1

v0.3.0

Choose a tag to compare

@github-actions github-actions released this 21 May 11:39
v0.3.0

What's Changed

  • Register metrics so that they show up on the metrics interface right after startup.
  • Use starknet-rs for Websocket subscription. (Thanks to @xJonathanLEI).
  • The attestation tool can now be started before registering yourself as a staker, avoiding potential slashing. The tool will wait for the registration to be performed and start attesting.
  • Support for non-ECDSA signatures via the remote signing API. The attestation tool now uses the signature in the response as is.
  • Avoid double confirmation log.
  • Log detailed transaction submission errors.

New Contributors

Full Changelog: v0.2.0...v0.3.0

v0.2.0

Choose a tag to compare

@github-actions github-actions released this 25 Apr 16:37
v0.2.0

What's Changed

  • The remote signing API now supports clear signing. Please check the README for details on the API.
  • We're now using an HTTP timeout of 30s for JSON-RPC and signing requests.
  • Linux / x86_64 binaries are now available for releases.
  • We're now providing Docker images for linux/arm64.
  • Specifying staking and attestation contract addresses with CLI (or environment variables) is now optional. The attestation tool defaults to using the well-known published addresses for the network served by the JSON-RPC node. Note that since no attestation contract has been deployed for mainnet yet, this currently works on the Sepolia testnet only. We will add support for mainnet once the attestation contract has been deployed there.

Full Changelog: v0.1.2...v0.2.0

v0.1.2

Choose a tag to compare

@kkovaacs kkovaacs released this 08 Apr 12:04
v0.1.2

This is a small release fixing compatibility with Juno.

Changes:

  • Fix compatibility with Juno by making block_number optional in Websocket event notifications.