This repository has been archived by the owner on May 22, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 23
Initial implementation of app-specific actions #580
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added a new sections to the config file. It allows to configure some properties needed by the app-specific actions feature.
Implemented a starting point for TBTC-specific actions. This also includes several chain extensions needed by TBTC actions.
`Connect` function should return struct instead of the chain interface. This is because the caller invokes that function explicitly to obtain a specific implementation of the chain. That change also follows the Go `accept interfaces return structs` principle.
Added initialization of the app-specific actions directly in the start command.
lukasz-zimnoch
changed the title
App specific actions
Initial implementation of app-specific actions
Oct 14, 2020
pdyraga
reviewed
Oct 14, 2020
Removed the `DepositLog` binding usage in favor of `TBTCSystem` binding as it is the actual contract emitting deposit lifecycle events. Apart that, a refactoring of the config structure has been made.
Move the app-specific parts of the chain implementation into the application package.
Implemented the backbone for TBTC actions and added the `retrievePubkey` action.
pdyraga
reviewed
Oct 19, 2020
pdyraga
reviewed
Oct 19, 2020
pdyraga
reviewed
Oct 19, 2020
pdyraga
reviewed
Oct 19, 2020
pdyraga
reviewed
Oct 19, 2020
pdyraga
reviewed
Oct 19, 2020
Implemented a basic unit test checking the happy path of the retrieve pubkey TBTC extension using a local chain implementation.
pdyraga
reviewed
Oct 19, 2020
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some comments on general naming and logs.
Implemented new unit test scenarios for retrieve pubkey TBTC extension using a local chain implementation.
@pdyraga all comments addressed! I'm starting tests on my local environment but I don't expect any big changes in the code. Also, I think those TODOs listed in |
Merged
pdyraga
reviewed
Oct 22, 2020
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some additional comments, mostly about naming, docs, and logs.
Reviewing tests now.
pdyraga
reviewed
Oct 22, 2020
pdyraga
reviewed
Oct 23, 2020
pdyraga
approved these changes
Oct 23, 2020
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Refs: #574
Depends on: keep-network/tbtc#739
Here we introduce the backbone which allows adding application-specific actions straight into the
keep-ecdsa
client. As its first use, we also add the TBTC extension which allows invokingretrieveSignerPubkey
action on new deposits which are close to exceeding the signing group formation timeout. Here is a brief summary of major changes:[Extensions.TBTC]
section in the config which allows configuring the TBTC extensionretrieveSignerPubkey
action allowing to add new actions as well