Releases: Fairblock/fairyringclient
Releases · Fairblock/fairyringclient
v0.5.3
v0.5.2
Whats New ?
- Fixed client will submit incorrect keyshares when the current public key got overrode
Full Changelog: V0.5.1...v0.5.2
V0.5.1
v0.5.0
- Updated client to get share on chain instead of getting it from API (For fairyring v0.5.0)
- Removed multiple validators support
- Removed ShareGenerationAPI in the config
- Updated
PrivateKeys
toPrivateKey
in config - Updated
keys list
andkeys add
command tokeys show
andkeys update
v0.4.0
v0.3.2
v0.3.1
v0.3.0
Updates
- Client will now wait for next round instead of exiting when there is no pub key at start
- Client will keep try to get commitment instead of exiting when there is error on getting commitment after got a new pub key
- Removed
fairyringclient keys rsa
command - Moved
fairyringclient keys cosmos
command tofairyringclient keys
- Removed
--no-rsa-key
flag onfairyringclient init
command - Removed all RSA related code
init
command will no longer createkeys
directory for RSA keys- Updated get share request to sign body with cosmos key instead of RSA key
- Updated client to decrypt share with cosmos key instead of RSA key
v0.2.0
New Features
- Added Prometheus metrics.
- Added verify key share after getting the key share from API, client will be paused until next round if the key share is invalid.
- Added a auto pause mechanism that if total invalid share submitted in a row is larger than the threshold, client will be paused until next round.
Updates
- Update default chain id to
fairytest-3
- Updated log
- Bump
google.golang.org/grpc
version fromv1.58.0
tov1.58.3
- Bump
golang.org/x/net
version fromv0.15.0
tov0.17.0