keep-ecdsa
keep-ecdsa copied to clipboard
keep-network
The smart contracts and client behind the Keep ECDSA client
This construction was used only to log the generated key in `node.go`
Include selection scheme candidates for a ticket-based scheme and an optimized 16-ary tree sortition pool scheme
Keep ECDSA client offers plenty of [metrics and diagnostics](https://github.com/keep-network/keep-ecdsa/blob/f1625856b94887ac36c2fa33f5b853b65a715296/configs/config.toml.SAMPLE#L98-L126) allowing to monitor the health of the node. However, there is no obvious way to monitor the health of third-party nodes...
In some places of ECDSA client there is a risk of submitting the same transaction (but with an increased nonce) again if the original one was not mined in a...
Nodes announce RFC1918/localhost addresses to the rest of the network by default. This causes ecdsa-client to attempt to connect to addresses it can never reach. There are use cases, esp...
Hey there :hand: Actually this is a suggestion to improve how dependent PRs are handled in this project. Example of a PR that depends on another one: https://github.com/keep-network/keep-ecdsa/pull/634. And after...
As currently implemented in https://github.com/keep-network/keep-ecdsa/pull/616, the client starts the signature confirmation process once it exits the signature publication delay. A nice improvement to the code presented in the referenced PR...
https://github.com/keep-network/keep-ecdsa/pull/616 calculates the order in which signers should submit a signature by determining signer's position in `address[] public members` field of `AbstractBondedECDSAKeep` and then calculating the delay based on signer's...
Certain applications that use ECDSA keeps (e.g., tBTC) benefit strongly from additional actions beyond the base ECDSA keep actions. As a specific example, tBTC deposits have certain state transitions that...
Metadata
Owner
Metadata
The smart contracts and client behind the Keep ECDSA client