Topic: Bitcoin nodes (Read 122 times)

Right, encrypted or not.
The descriptors that you'll import only contain extended public keys (xpub), it can only derive its child public keys.
Your private keys stay in your Trezor.

One warning though: never export even a single private key from your hardware wallet (e.g.: manually derived from the seed phrase using tools)
Because almost all wallets are now using non-hardened derivation paths after the 'account_index' to be able to achieve watching-only HD wallets.
If even single private key and its parent's pair 'extended public key' are compromised, it could compromise all the child keys of its xprv parent.

Bitcoin Core is a software that acts as a bitcoin node, which means it keeps a full copy of the blockchain and validates transactions communicating with other nodes. At the same time, yes! it allows you to generate a wallet too, which means it gives you access to receiving and sending funds.

But let's go to the initial job of Bitcoin Core for a bit. As I said, it validates transactions and keeps the blockchain. Doing that, it allows you to connect other wallets to it. Those other wallets will do the sending / receiving / signing stuff and Bitcoin Core will do the "behind the scenes" job of validating incoming transactions and broadcasting outgoing transactions. But in order for this to happen it must be connected to the internet.

The scheme of what I explain above looks like this:

Bitcoin Core <--- Sparrow <--- Hardware Wallets (like trezor)

Summary
The node (Bitcoin Core) is essentially responsible for the communication with the whole bitcoin network. Then Sparrow will only act as a layer on top of that. It will allow you to give instructions what you want to do (send X sats to someone, receive sats to a specific address etc). Connecting hardware wallets will give another layer on top of all of that. It will allow you to sign transactions offline, on the device. Then the signed transaction will go Sparrow. Then Bitcoin Core will transmit the transaction (broadcast it) to the Bitcoin network.

Useful Links
1. Set Sparrow to connect to your node.
2. Connect Trezor to Sparrow.

The sparrow wallet is really good i looked into it and im still trying to connect it back to my node. Although you have specified the use of external signers directly with Bitcoin Core which actually is more of what i was looking for so ill have to see what's up with that. I think that if i manage to set up it up ill just use the bitcoin core as a cold wallet since its encrypted and anybody that would want to do any transaction would need the Trezor, right?

I do really like the sparrow wallet though so if the external signer works on my bitcoin core ill keep some holding in there and some holdings inside of my sparrow wallets that is connected back to my node.
Im not trying to keep all of my coins in one wallet if that makes any sense and i dont have any trouble making new wallets its just i wanted to make sure all wallets had a Hardwallet and that i owned my nodes.


Anyways sorry to confuse you in any sort lol  






 

If it's just that feature that's complicating things, just remove the password of your Electrum wallet and it wont ask you to plug the device if you need to open it,
That way, it will only require you to plug the device if you need to use the private keys from your Trezor. (signing transaction or message)

Or do you mean that you've setup an Electrum server to connect your Electrum client where you've connected your Trezor?
Because that's actually more complicated than what you've written.

There's is an "External Signer" feature that you can use but it's arguably as complicated as your previous setup.
Here's some info: https://github.com/bitcoin/bitcoin/blob/master/doc/external-signer.md

Basically, you'll have to setup Bitcoin Core with its path either in command line or GUI settings under "Settings->Options->Wallet".
And use the External Signer tool to create the descriptors that you can import to a new Bitcoin Core wallet with "disable private key" and "blank" options.
Then, you can use that watching-only wallet as interface and the External Signer for txn signing purposes.

oh thank you that seems like a really good option ill definitely try that

You can connect Electrum to Bitcoin Core node rather than to public nodes. Here you can find a tutorial on how to do this.

However, to pair your Trezor, I would advocate Sparrow wallet  instead of Electrum. The relevant procedure for Sparrow is more straightforward.

Got my bitcoin core on my computer with some bitcoin inside, file is encrypted and i also have Trezor wallets with some bitcoin inside of it also.
Im wondering is there anyway i can connect my trezor to my node with my private keys stored in my trezor?
Ive got down the rabbit hole with this and found out its electrum i had to download.
So i did and connected my trezor wallet to my electrum wallet for whenever i log in.
But isn't it too much complicated for nothing?
Can't i connect my hard wallet directly to my Bitcoin core and thats it? Im trying to have some Bitcoins on me whenever i leave the house or the city so i carry a Hard wallet. But whenever im at home ill just use my wallet on the Core directly to the node just like the old days. I think its weird that electrum lets you connect the hard wallet to login but when its the bitcoin core is just the seed. There isn't anything on the program that lets me connect my hard wallet to give it more of a secure feature. Any help on how i can connect a trezor wallet to my node and to have a Hard wallet to be added as a security feature on Bitcoin core?