Skip to content

Releases: getoptimum/optimum-keysync

Release list

optimum-keysync 1.1.1

optimum-keysync 1.1.1 Latest
Latest

Choose a tag to compare

View all tags
@CryptoFewka CryptoFewka released this 25 Jun 21:05
Immutable release. Only release title and notes can be modified.
v1.1.1
b11e61b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Documentation and packaging release. No functional or API changes since 1.1.0.

Changed

  • Quickstart now leads with KEYSYNC_INDICES_FILE (a JSON records file, no beacon node required) and presents the BLS-pubkeys + beacon path as an alternative, instead of implying keysync runs next to a validator or beacon host. (#20)

Packaging

  • Added the MIT LICENSE file, now included in the sdist and wheel metadata. (#20)
Assets 3
Loading

optimum-keysync 1.1.0

optimum-keysync 1.1.0

Choose a tag to compare

View all tags
@CryptoFewka CryptoFewka released this 25 Jun 20:46
Immutable release. Only release title and notes can be modified.
v1.1.0
74b53c6
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Maintenance and hardening release. No breaking changes; upgrade in place with pip install -U optimum-keysync.

Added

  • Network safety check: when a beacon node is configured, keysync verifies the beacon's chain id matches KEYSYNC_CHAIN_ID before planning any changes, and fails fast on a mismatch (for example a testnet beacon left on the mainnet default) or a wrong KEYSYNC_BEACON_URL, instead of resolving an empty set that looks like a mass exit. (#17)

Changed

  • The indices JSON file is validated more strictly: a non-integer or negative validator_index is rejected up front rather than being silently coerced to a wrong index. (#17)
  • Malformed console API responses (a non-JSON body, or a non-numeric count) now surface as a clean error with the documented exit code instead of an opaque traceback. (#17)
  • Key registration reports progress per batch, so a failure partway through a large import logs what actually landed. (#17)
  • KEYSYNC_LOG_FORMAT is validated (console or json); a URL without a scheme now gives a clearer error; validators excluded by beacon status (for example withdrawn) are logged. (#18)

Fixed

  • HTTP clients are now closed cleanly via context-manager support, avoiding a connection-pool leak when keysync is used as a library. (#16, closes #5)
Loading

optimum-keysync 1.0.0

optimum-keysync 1.0.0

Choose a tag to compare

View all tags
@CryptoFewka CryptoFewka released this 25 Jun 17:16
v1.0.0
6b0e146
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Reconcile a customer's Ethereum validator set against Optimum's validator registry. A one-shot, cron-friendly CLI: --dry-run by default, --apply to write.

  • Authenticates with an ovi_live_* operator API key (direct auth, no JWT exchange).
  • Inputs: a JSON indices file (no beacon node needed), or BLS pubkeys / validator indices resolved via a beacon node.
  • Sensible defaults for the Optimum console and auth endpoints and Ethereum mainnet; override for testnets.
  • Idempotent: a steady state reports nothing to do, with a --max-deletes guardrail against accidental mass unassignment.

Install:

pip install optimum-keysync
Loading