Topic: BitCoin Core Funds Transfer (Read 382 times)

This is of course a way more elegant way to perform the conversion as we assume Electrum to be a trustworthy wallet and tool. It avoids the need for additional software, which is great for such cases. Thank you for pointing it out! I will edit my earlier post to point to it.

Now that you wrote this, I should've taken a look at my "Electrum console magic cheat sheet card" where I had this already, too. I try to collect such stuff to not forget it, haha, because as far as I know, there's no cool collection of handy Electrum console commands and functions. Cough, cough, someone should really compile it.


I checked with keys of my example and it works flawlessly in the Electrum console (make console visible by ticking "Console" in Electrum's menu bar item "View"):


To further check and verify that external and internal Native Segwit addresses are identical in example Bitcoin Core descriptor wallet and resulting Electrum deterministic wallet, you can request Bitcoin Core to show an arbitrary number of addresses with the command  deriveaddresses "descriptor" "range" 

In above described example you get the following output in the Bitcoin Core console (also works from command-line with bitcoin-cli), the first block are external, the second block are internal/change addresses:

Here a more complete list of the addresses in Electrum:

I think there is no way to "take the funds out without having to wait the full block chain download sync'.  Otherwise it would be possible to double spend your   $500.

I don't know what your hardware setup is but if you use SSD ^{preferably NVMe type}, at least 16 Gb of RAM, fast CPU and correct dbcache entry in bitcoin.conf file it takes around 24- 26 hours to reach the full sync.

It's similar to the link in my previous reply (here) but it doesn't cover the conversion from xprv to zprv/yprv since the OP in that post use legacy (pkh).
Yours is a complete version well suited for this topic.

For the conversion part, the convenient tool to use for that is already available: Electrum's console. ("View->Console" for those who aren't familiar)
e.g.: for P2SH-SegWit,
or  for Native SegWit

I was curious and had it also on my long-term agenda to walk through the steps required to successfully import e.g. a Native Segwit derivation from a Bitcoin Core descriptor wallet (which usually contains descriptors for all main four address types) into an Electrum wallet.

I'm not entirely sure if my steps haven't been already documented somewhere in the forum. Anyway, you learn more when you do the steps on your own.

I created a sample test wallet as descriptor wallet with keys in my Bitcoin Core v28.0.0 node. The descriptors will be published here, so anybody can check and verify to get to the same result and/or do the walkthrough with their own sample wallet.

With  getnewaddress "" "bech32"  in Bitcoin Core's console window, executed twice, I got the following two receive addresses of this brand new sample wallet, their full derivation path added as second column:

bc1qjvr5fjgccey8q6u88l9h382w6pj4n63wqy8qnf		m/84h/0h/0h/0/0
bc1qkv0cysnqztsrfs296jtcsag85dcjdxu7nrn3yr		m/84h/0h/0h/0/1

Important:
If you do theses steps with a real funded wallet, do this in a safe computing environment. Boot Tails or another suitable Live Linux from trusty media storage, download only necessary software from their designated safe sources, verify it's genuine. I recommend to disconnect any network connection when you work with private keys or BIP32 master private keys.
It would be utterly stupid to execute the steps with your daily internet-shit machine whoes safety status you likely only can guess.
For obvious reasons, you should NOT use any of my published descriptors for any wallet with real coins! Stealing bots will digest publicly available descriptors/private keys into their databases.


Here is the output of  listdescriptors true  in the Bitcoin Core console (you can also do it on your command-line with  bitcoin-cli -rpcwallet=walletname listdescriptors true):

For Native Segwit the derivation path is m/84h/0h/0h/0/* for receiving addresses and m/84h/0h/0h/1/* for internal/change addresses. The relevant descriptors are:

The BIP32 Root Key in my example is
and has to be entered in an offline copy of the iancoleman script (online version https://iancoleman.io/bip39/, download and verify offline version from https://github.com/iancoleman/bip39/releases/latest/):


Don't click on Generate or anything else when you start with a clean empty offline iancoleman script page! The first entry into the script is the copied xprv key into the box labeled BIP32 Root Key.

Scroll down a bit in the script to section Derivation Path and bring the tab BIP84 to the front (click on BIP84). In my example it should look like this:


We need what's labeled as Account Extended Private Key in the iancoleman script, because Electrum uses the following derivation when you create a standard, aka Native Segwit wallet with the option "Use a master key": m/0/* for receiving, m/1/* for internal/change addresses. The m for Electrum has to be the underlined part of the standard BIP84 derivation m/84h/0h/0h/0/*, which is the mentioned Account Extended Private Key.

But we can't feed the Account Extended Private Key
as master key in Electrum, because with a xprv key Electrum derives legacy addresses, those that start with 1..., as in the Electrum GUI at this step you don't have any option to specify a particular address type. Bummer?

We need the Account Extended Private Key in the zprv form! Fortunately you can convert a xprv to zprv (or yprv) and vice-versa.

Post edit:
See below post from nc50lc which shows how to do the conversion in the Electrum console! No additional Python or external commands needed which is great!
I checked in my reply to nc50lc's post that it works as suggested.

I used few lines of Python code which I found here: https://gist.github.com/openoms/4e8a527e4c9757162a53f2dc96e3d229
Below code is already with the xprv from my example and the resulting zprv we need for Electrum:

(I had Python3 and pip already installed, so for this solution you'd need that too. You have to install the base58 library with pip install base58. I didn't do anything fancy, just executed python3 without further parameters and pasted the lines into the Python prompt, quick'n'dirty:


Finally we can take this resulting zprv master key to feed it into Electrum. Start Electrum, create new wallet, at "What kind of wallet do you want to create?" you select Standard wallet and click Next, for Keystore you choose Use a master key and click Next.

At "Create keystore from a master key" you paste the zprv key from our little conversion, i.e. in my example I entered

The resulting Electrum wallet now has the same addresses as the Bitcoin Core descriptor wallet. Mission accomplished, even when it's a bit fiddly. The first two receiving addresses are the same as taken from the Bitcoin Core wallet (you can check also that addresses match with what the iancoleman script lists.

bc1qjvr5fjgccey8q6u88l9h382w6pj4n63wqy8qnf		m/84h/0h/0h/0/0		Electrum derivation: m/0/0
bc1qkv0cysnqztsrfs296jtcsag85dcjdxu7nrn3yr		m/84h/0h/0h/0/1		Electrum derivation: m/0/1

For future reference, I have created this post.

https://bitcointalksearch.org/topic/--5524851

Exactly and I wonder why centrally isn't able to click e.g. on the Info button that is in the Electrum dialog Create/Restore wallet > Import Bitcoin Addresses or Private Keys above the entry box where you paste public addresses or private keys.

When you click the Info button you get what you need to properly import private keys so that your desired address type is derived:



Oh and centrally, please stop posting consecutive replies after few minutes or even hours when the last post on same day is yours. You can simply edit your last post to add something. Consecutive posts are not allowed by forum rule #32 when it is not an allowed bump and bumps aren't allowed within less than 24h or when they are annoying.

let's suppose this is the wallet you are interested in iancoleman:
The WIF private key would be this:


starting with bc1 means it is a p2wpkh address, and you would import it into electrum like this:

'create new wallet'

'import bitcoin addresses or private keys'

paste your WIF like this: p2wpkh:KzBWczgXjttLkj8FxyMqw88FNVoAYKzLqZvwz4sMmrNzkGVwbZb6

Yep. The address in bitcoin core that has my funds i used it as a watch only wallet in a different wallet, like the address, from the receive section, and yes i did follow your steps but after i put in the rootkey and go into derived addresses i did derive 100 more and my address was not in it.

I found everything and did everything up until the derived address part where i can't find it. I see bc1 wallets but none match mine

---

OK so update, i just put a diff xprv key, and i see my bitcoin wallet's address in the derived address, i try using the private key, and it still says 0 balance on electrum, same with the extended private account (funds are in that same exact wallet, i've checked from wallet watching, and i have the txid.)

AND when i go to addresses on electrum when i import the key it shows a address starting with 1, instead of bc again, and the xprv key that worked was a random one with active on false, and no internal

when you use
you get the xpriv, follow the steps I gave you and you will get the corresponding keys.

it should not be difficult, I suppose, you downloaded bitcoin core, created the wallet and generated an address, sent it to your friend and nothing else.

or what process did you follow?, did you generate more wallets?, did you generate more addresses?, can you see your address in question in bitcoin core?

how do i know which one to use when i export them?

---

UPDATE just tried it, but could not find my wallet address in the derived addresses?

BALANCE always says 0 when trying i have no idea what im doing wrong, im taking the BIP32 Extended Private Key and putting it into electrum.

I also checked derived addresses, none were matching my wallet in bitcoin core. I used Bip84 cause i have a bc1 wallet in bitcoin core.

Also when using bip84, i also tried using the extended private key, but my address was not showing it was all addresses saying 1Kblabla none of them started with bc1

In the link provided by DaveF, scroll-down to the third reply and follow the link for the full instructions. (or follow the post above)

This is difficult since it's the actual block that's corrupted, not just your block index or chainstate.
Usually, --reindex is used to try to fix this.
You can also solve this "dirty", by deleting the bad 'blk.dat' file containing the corrupted block, you can also delete the entire "blocks" and "chainstate" folders to start from scratch if losing 188698 blocks is not an issue.
Doing either on pruned mode will restart initial block download, by the way.

If you don't want to sync Bitcoin Core even after fixing the crash;
An alternative to the "BIP39 tool method", you can migrate your entire wallet to Electrum by following this: https://bitcointalksearch.org/topic/--5523526
Your master private key can be exported with listdescriptors true command in Bitcoin Core's console (Window->Console).
Don't forget to read the "Important Notes" to derive the correct 'extended private key'. (BIP44 (pkh) legacy '1', BIP84 (wpkh) Native SegWit 'bc1q' and BIP49 (sh-wpkh) P2SH-SegWit '3')

However, the wallet is not properly backed-up for Electrum that restoring it in the future might confuse you.
And keeping the long "master private key" as backup could be problematic so you should consider sending all to a "normally" created wallet on the wallet of your choice.
If you want to keep using Electrum, create a new standard wallet there and send your bitcoins to it.
(do not use a machine with compromised security since it's a Hot wallet, consider "hardware wallet" or "cold-storage" for better security)

First:

try extracting their xpriv from the Bitcoin Core console with:


you will get something like this:


you are only interested in the xpriv that has this:


Second: download the offline version from GitHub of Ian Coleman https://iancoleman.io/bip39/ 

Third:  Paste the xpriv in the offline page of Ian Coleman where it says 'BIP32 Root Key'

then in 'Derivation Path' select 'bip84',

in 'Derived Addresses' you will see a list of addresses, public keys, and the private key in WIF format

one of them is yours. Once you have the WIF, import it into Electrum by using

'create new wallet'

'import bitcoin addresses or private keys'

paste your WIF like this: p2wpkh:'your WIF here'

example:


done!

Yes i did

I mean that it is not advisable to download from third parties even if they seem legitimate, for the security of your coins.

Did you set a password when creating the wallet?

txid, i know they hit i can see it on blockchain ALSO yeah because it keeps crashing i was half way done before lol but thats the error

That is block # 188698 from ~ 12 years ago so your wallet is WAY out of sync.
How were you able to see that you got the funds if you wallet was never fully up to date?

-Dave

I cant get seeds from a bitcoin node wallet, and okay how do i sync if it crashes though, and for the node if i download that how do i use it?

---

also what do you mean not advisable, will i still have my balance? and be able to move it out and never use bitcoin core again

both Legacy and SegWit seeds can be imported into Electrum.

If you have a relatively high amount of BTC, I recommend waiting for synchronization.

However, some users download the pruned node from here: https://github.com/Blockchains-Download/Bitcoin/releases/, which saves time.

However, this is not advisable unless you only use that node to contribute to the network without involving your bitcoin, due to the potential security risks it may entail(Use it at your own discretion).

No when i mentioned mnemoic it was about something else, i can't get a seed from bitcoin core, its a none legacy wallet

---

PS the error i keep getting:


2024-12-30T00:50:44Z ERROR: ConnectTip: ConnectBlock 0000000000000460b3ff23b68db39eff1c0fa29d1f5e89bb10daaa49ad24aecf failed, bad-txnmrklroot, hashMerkleRoot mismatch
2024-12-30T00:50:44Z ERROR: ProcessNewBlock: ActivateBestChain failed (bad-txnmrklroot, hashMerkleRoot mismatch)
2024-12-30T00:50:44Z *** Corrupt block found indicating potential hardware failure; shutting down
2024-12-30T00:50:44Z Error: A fatal internal error occurred, see debug.log for details


this is the reason i cant sync

Have you tried these steps:

1- Open Electrum and select "Create a new wallet".

2- click "Next".

3- Choose "Standard Wallet" and click "Next".

4- Select "I already have a seed" and click "Next".

5- Enter your mnemonic seed (the words you have).

Click "Next".

bc, and its bitcoin core, where u have to sync ur thing to blockchain but i cant cause of the errors, so idk what to do, cant dumpprivkey cause of none legacy wallet either

it starts with bc

---

Can you show me like where to downlaod a pruned node or use it?

If you have the seed, you can enter it into Electrum or another wallet. Your address starts with? 1,3,bc1?

Yes but how do i download a pruned node? I keep getting errors when trying to download

PS. i literally only need the December 28th transaction yesterday, cause thats when i got the big payment

Are you talking about having a mnemonic? If you don't know how to create a raw transaction, it's not recommended. A mistake could leave your funds lost forever. I'd prefer that you download a pruned node and restore your wallet.dat backup.

Can you tell me in detail how i could do a raw transaction like i have no idea, i want to empty my whole balance into a new acc, and electrum doesnt support .dat files i think

---

Also when i try the bip39 method, do i click generate after i put my thing into the rootkey, like where is the priv key after i put it in

You can also try this method:
https://bitcointalksearch.org/topic/--5482984

Seems to work, or at lest when I tested it on an empty wallet it did.

-Dave

You could try using Electrum or a pruned node to avoid a long wait time. Before attempting anything, make sure to backup your wallet.dat file!


In theory, yes, you can. You shouldn't have any issues if you know the address that received the balance.
To send it, you can use online sites like https://www.blockchain.com/explorer/assets/btc/broadcast-transaction.
Other options include extracting the private keys using tools like pywallet or btcrecover.

No i did that error was from when i reinstalled i was 40% in the first time

You haven't even synchronized the blockheaders? Could you retry running bitcoind with -resync, and also could you share your configuration file? (Obviously with hidden anywhere sensitive.)

I wouldn't say so, no. And don't try it. Just fix your node.

2024-12-29T22:35:11Z Synchronizing blockheaders, height: 33559 (~4.09%)
2024-12-29T22:35:11Z tor: Thread interrupt
2024-12-29T22:35:11Z Shutdown: In progress...
2024-12-29T22:35:11Z addcon thread exit
2024-12-29T22:35:11Z torcontrol thread exit
2024-12-29T22:35:11Z opencon thread exit
2024-12-29T22:35:11Z net thread exit
2024-12-29T22:35:11Z msghand thread exit
2024-12-29T22:35:12Z DumpAnchors: Flush 2 outbound block-relay-only peer addresses to anchors.dat started
2024-12-29T22:35:12Z DumpAnchors: Flush 2 outbound block-relay-only peer addresses to anchors.dat completed (0.08s)
2024-12-29T22:35:12Z scheduler thread exit
2024-12-29T22:35:12Z Writing 0 unbroadcast transactions to disk.
2024-12-29T22:35:12Z Dumped mempool: 0.000s to copy, 0.081s to dump
2024-12-29T22:35:13Z [haha] Releasing wallet
2024-12-29T22:35:13Z Shutdown: done



Is there any detailed way to get my priv key from a descriptor wallet?

What errors? Would you mind sharing the debug.log?

I can't lol, it keeps failing, and giving errors on failure ive tried uninstalling i have a lot of funds in this account i cant risk losing it

Caution:

If you don't know what commands such as createrawtransaction and signrawtransaction do, don't meddle with them. As I said, let your node sync with the network; that is the easiest and safest option for you.

into what wallet can i use a dat file though? and okay ill try it

---

UPDATE:
Also i can't do raw transactions if wallet isn't synced i have no idea how eitherway

I still need help

You might consider creating a raw transaction using the createrawtransaction command and then signing it using signrawtransaction in Bitcoin Core.

Alternatively, you could import your wallet.datfile into another wallet that is not Bitcoin Core (following the appropriate security precautions).

Absolutely don't share your wallet file with anyone who wants to "help" you.

Here's an answer from Bitcoin Core developer, Ava Chow:

It is theoretically possible to export the private keys, but not implemented in the client, so you'll have to manually meddle with the client (using the changed client in the pull request link). If I wasn't experienced with Bitcoin Core (which is true), I'd choose not to do that, and just let it finish syncing. Is there a reason why you're not choosing this route?

you can put your privatekey to blockchain.com for ex

Hey so i downloaded bitcoin core, and had recieved $500 from my friend, but the thing is i didnt know i had to download the core, i dont want to wait this time, the bitcoin core wallet has the funds, any way i can take the funds out without having to wait the full block chain download sync?

keep in mind this is a non legacy wallet due to newest update on bitcoin core so dumprivkey isn't working for me

---

or just help with on how to get private key from new bitcoin core, none legacy wallets