Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: implement of btc-staker improvement 107 (#134) #139

Merged
merged 3 commits into from
Feb 20, 2025

Conversation

KonradStaniec
Copy link
Collaborator

@wnjoon and b-harvest contribution - simplifing btc-staker program greatly

  • feat: remove watch-staking endpoint, post-approval flow

  • feat: remove db fields - state, fpkey and pop

  • feat: update CHANGELOG

  • feat: remove stakingoutputIdx, btcTxHash. refactoring UnbondingTxData and etc

  • feat: remove confirmation fields and modify WithdrawableTransactions

  • feat: cleanup codes including comments, error wrapping etc.

  • feat: change WithdrawableTransactions logic and set pagination

* feat: remove watch-staking endpoint, post-approval flow

* feat: remove db fields - state, fpkey and pop

* feat: update CHANGELOG

* feat: remove stakingoutputIdx, btcTxHash. refactoring UnbondingTxData and etc

* feat: remove confirmation fields and modify WithdrawableTransactions

* feat: cleanup codes including comments, error wrapping etc.

* feat: change WithdrawableTransactions logic and set pagination
@@ -131,10 +131,6 @@ var stakeCmd = cli.Command{
Usage: "Staking time in BTC blocks",
Required: true,
},
cli.BoolFlag{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why remove this option?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

because after this pr staker will only support two flows:

  • pre-registration flow
  • and phase-1 / phase-2 transition flow (which is handled by separate command)

There is no longer post-registration flow, which was source of complexity and required a lot of state in DB.

Copy link
Contributor

@RafilxTenfen RafilxTenfen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tested against deployments, LGTM

@RafilxTenfen RafilxTenfen merged commit 957cbb6 into main Feb 20, 2025
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants