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

Register Staketab as a finality provider #31

Closed
wants to merge 5 commits into from
Closed

Register Staketab as a finality provider #31

wants to merge 5 commits into from

Conversation

duccas
Copy link
Contributor

@duccas duccas commented May 15, 2024

No description provided.

@vitsalis
Copy link
Member

@duccas Signature and staking transaction seem to be invalid

@RafilxTenfen
Copy link
Contributor

@duccas can you check if the btc_pk used to create the staking tx is the same as the one in the .json file ?

@duccas
Copy link
Contributor Author

duccas commented May 15, 2024

@duccas can you check if the btc_pk used to create the staking tx is the same as the one in the .json file ?

We did the staking transactions according to this guide with the command below, is this wrong?
https://github.com/babylonchain/btc-staker/blob/1b1ea49d4e8421041e6748f537af6a9b252990a6/docs/create-phase1-staking.md

stakercli transaction create-phase1-staking-transaction \
  --staker-pk a77975899eededc731d80eee488b21fbee5715a16e3aba5ec83400c6d551af2c
  --staking-amount 15000000 --staking-time 52560 \
  --magic-bytes 62627434 \
  --finality-provider-pk 76cd2bea40e8226eb87cf5d3f07b66327fc8afc7c9d52e2e73bb711b9a6fd8e1 \
  --covenant-quorum 3 \
  --covenant-committee-pks 05149a0c7a95320adf210e47bca8b363b7bd966be86be6392dd6cf4f96995869 \
  --covenant-committee-pks e8d503cb52715249f32f3ee79cee88dfd48c2565cb0c79cf9640d291f46fd518 \
  --covenant-committee-pks fe81b2409a32ddfd8ec1556557e8dd949b6e4fd37047523cb7f5fefca283d542 \
  --covenant-committee-pks bc4a1ff485d7b44faeec320b81ad31c3cad4d097813c21fcf382b4305e4cfc82 \
  --covenant-committee-pks 001e50601a4a1c003716d7a1ee7fe25e26e55e24e909b3642edb60d30e3c40c1 \
  --network signet

Our FP pubkey:

pub_key_hex": "76cd2bea40e8226eb87cf5d3f07b66327fc8afc7c9d52e2e73bb711b9a6fd8e1"

Our Staker key is:

bitcoin-cli -signet \
-rpcuser=$BTC_USER \
-rpcpassword=$BTC_PASS \
-rpcport=38332 \
-rpcwallet=$BTC_WALLET_NAME \
getaddressinfo tb1qrus6f7gr4vlxyeyj7see3ad0y4gp6qtxxr0mds | jq -r '.pubkey[2:]'
a77975899eededc731d80eee488b21fbee5715a16e3aba5ec83400c6d551af2c

@RafilxTenfen
Copy link
Contributor

@duccas can you check if the btc_pk used to create the staking tx is the same as the one in the .json file ?

We did the staking transactions according to this guide with the command below, is this wrong? https://github.com/babylonchain/btc-staker/blob/1b1ea49d4e8421041e6748f537af6a9b252990a6/docs/create-phase1-staking.md

stakercli transaction create-phase1-staking-transaction \
  --staker-pk a77975899eededc731d80eee488b21fbee5715a16e3aba5ec83400c6d551af2c
  --staking-amount 15000000 --staking-time 52560 \
  --magic-bytes 62627434 \
  --finality-provider-pk 76cd2bea40e8226eb87cf5d3f07b66327fc8afc7c9d52e2e73bb711b9a6fd8e1 \
  --covenant-quorum 3 \
  --covenant-committee-pks 05149a0c7a95320adf210e47bca8b363b7bd966be86be6392dd6cf4f96995869 \
  --covenant-committee-pks e8d503cb52715249f32f3ee79cee88dfd48c2565cb0c79cf9640d291f46fd518 \
  --covenant-committee-pks fe81b2409a32ddfd8ec1556557e8dd949b6e4fd37047523cb7f5fefca283d542 \
  --covenant-committee-pks bc4a1ff485d7b44faeec320b81ad31c3cad4d097813c21fcf382b4305e4cfc82 \
  --covenant-committee-pks 001e50601a4a1c003716d7a1ee7fe25e26e55e24e909b3642edb60d30e3c40c1 \
  --network signet

it is wrong, take a look here

Where it specifies that the flags

  --covenant-committee-pks=50929b74c1a04954b78b4b6035e97a5e078a5a0f28ec96d547bfee9ace803ac0 \
  --covenant-quorum=1 --network=signet

since this is a lock only tx, the committee is a key that no one has access to withdraw and the funds will only be available in 52560 sBTC blocks '-'

@filippos47 could you send 0.1sBTC for Staketab again?

@duccas
Copy link
Contributor Author

duccas commented May 15, 2024

@RafilxTenfen I get your point, the documentation is very extensive and the commands are different in some places. I thought that might be the reason.

@RafilxTenfen
Copy link
Contributor

@duccas my recomendation is to start from scratch to avoid missing any step

@duccas
Copy link
Contributor Author

duccas commented May 15, 2024

@duccas my recomendation is to start from scratch to avoid missing any step

The error is clear. Thank you!

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