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

Can't claim peg-in because of invoking getpeginaddress during initial sync #1343

Closed
matvore opened this issue Jul 23, 2024 · 4 comments
Closed

Comments

@matvore
Copy link

matvore commented Jul 23, 2024

I invoked getpeginaddress immediately after my node started syncing and it gave me 33EwSsVa9ssxcWvZ283aFaUQb9rmrR2Tt7

After 102 confirmations, I invoked claimpegin with the transaction data and proof for https://mempool.space/tx/dae4e62bb96a6da501d03bba33a0ad370cadcfc457e0fe5dcee1fc060b6772b3 - plus the claim script given in the original command.

Expected behavior

L-BTC deposited into my local wallet.

That may not be possible, so in the future it would be nice to see an error or warning if the sync is more than one day behind?

I checked the directions that I originally followed to do this, and it turns out it did say a fully-synced node was required at the top of the directions. https://help.blockstream.com/hc/en-us/articles/900000632703-How-do-I-peg-in-BTC-to-the-Liquid-Network

Actual behavior

I got the error: Given claim_script does not match the given Bitcoin transaction. (code -8)

System information

Elements v23.2.1, downloaded pre-built from GitHub

BitcoinCore 27.0.0, downloaded pre-built

Running on MX Linux 23.3

Steps to reproduce

getpeginaddress

<wait for sync to finish, send BTC to given address>

claimpegin 02000000000101770532e111170173afede88f6cd38362062cc6fabd46511e9534bffb4ae927480000000000fdffffff0136d400000000000017a9141101b30290a8ec4df288d4d97b3ebeef2d8fc91e8702473044022047ce015370ba545378dc029b0c112ab4cfd64f6e019e17acc3590a8ecf6b545002206383fa62f9c927ef5b2bb3863b287da7f21f821571cc2ee31896859804f365e20121020814b7edd815762e8f16e50a0b2aef69a17cd7f3b4a38c071943cb212ffbfa4800000000 0000eb289bbfdf3e62dbd6b4ae6453b5a430481d3d3829444c070000000000000000000057d7b9982505987e886a1ffceeea906568d5387d2beeb54d5dec631bda6c86636f289c663a6e03176a008ebc941200000e8ef6ca030df629297050423e4bcf65a1703683d9e3d4712dd25cbc891813808e796fee745c7ecb896bb1b031c70a58dca81bcfa2ace5abb326f5a17014c00d7eb14d46592f1d64c1e37257893d3cc083cc9098b2afe16ea0e3b8e77ee42dc36fb837e9877e897fc416328e883b1b1d7e85bc4b44e17b2fff757416b985d8287f8620c70b3118aa39305500a1bfb862eeb8192368b2729a37730c1c07795104ac55b2c7fc8611e7977d8ce454f57bfb0b8b933260ad1c4ab27fdd0df7a5ef21518bf699efd9f23a382a8bacd9e8ada8747cb95ca61723c9488bf6fdc139e295eab372670b06fce1ce5dfee057c4cfad0c37ada033ba3bd001a56d6ab92be6e4dafdf66ea54be0dbcd5d9261b8813a3b9854df72a4b9665377bd974b227eee2c4f8d42ddf95b8514b2b257036ed3a39b2ac2d0ede1f90ee6de2d798743cf4273a16f4b39b4e5b04e6e1de7170d45b1968cc98b9f634341169c106596ddc78228bc8ab7a1da5c9072a0cf2095dec3d7849d1dba0cfe93a13f8203db374309f36e444979b13458805d0402f03fffd472d80a639526a905586f94df5b06967c4806e7243bbde180d9f92e971b731cd5216cc3ef9fb3aa566dbfad5c8d9c43465493570457571700 <claim_script_here>

Note

I still have the claim script.

@ElementsProject ElementsProject deleted a comment Jul 23, 2024
@matvore
Copy link
Author

matvore commented Nov 2, 2024

@psgreco I think you originally asked me to file this issue. I have Telegram but wasn't able to find you on it. My username on Telegram is @mdevore - would you please drop me a line?

@psgreco
Copy link
Contributor

psgreco commented Nov 10, 2024

@matvore I can't find our conversation either. Please ping me on Telegram (make sure I'm the right me)

@matvore
Copy link
Author

matvore commented Jan 8, 2025

Here is my reimbursement address (sent on Telegram as well): lq1qqvs279drw66hnp2866pcg5sgptmwdalmhsyraxcwr5ww46jzw7kdxj24eq6vsnn5sacmyv60z7jjdr5hk3jaxnrcsrf7z46aw

@psgreco
Copy link
Contributor

psgreco commented Jan 8, 2025

@psgreco psgreco closed this as completed Jan 8, 2025
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

No branches or pull requests

2 participants