keep-ecdsa icon indicating copy to clipboard operation
keep-ecdsa copied to clipboard

The smart contracts and client behind the Keep ECDSA client

Results 94 keep-ecdsa issues
Sort by recently updated
recently updated
newest added

Added more complex tests to cover `node` package where we execute DKG and signature calculation and publish results to the chain. We were able to separate DKG from signing tests...

Chain functions should return promises. To generate promises we should use `keep-common` library as per example in https://github.com/keep-network/keep-core/pull/1049.

Sometimes it happens that after fresh migration client is not registered on-chain and logs `operator is not yet registered for application` message continuously. ``` 03:08:09.132 INFO keep-ecdsa: generating new tss...

πŸ› bug
πŸ•΅οΈ system tests

For tBTC, a closed keep may still have BTC in the associated wallet (say, in case of collateralization liquidation). In these cases, the signers may want to do some additional...

``` Installing NPM dependencies... audited 189227 packages in 6.24s found 18 vulnerabilities (12 low, 6 high) run `npm audit fix` to fix them, or `npm audit` for details ```

β›“chain

On the client's start, we run `checkAwaitingSignature` function to see if there are any pending signing requests and execute protocol if needed. The function performs a couple of calls to...

πŸ“Ÿ client

This issue is a followup from https://github.com/keep-network/keep-ecdsa/pull/409. We added retry delays for retries loops as a temporary solution. We should replace them with an elegant solution using exponential backoff (e.g....

πŸ“Ÿ client

## Client Configuration Start client with: * [x] valid configuration * Client starts successfully. * [x] missing config file * Client fails to start. * [x] config file in default...

πŸ•΅οΈ system tests

A keep with a single member can be created, we need to implement single signer support in the client. This issue is a followup from https://github.com/keep-network/keep-ecdsa/issues/392

enhancement

The client starts key generation after restart even though keep is already closed. Steps to reproduce: 1. Open keep. 2. Kill client. 3. Close keep. 4. Start client.

πŸ› bug
πŸ“Ÿ client
πŸ•΅οΈ system tests