Author

Topic: Sweep pivate key from Legacy address to Nested/ Native Segwit or Taproot (Read 99 times)

legendary
Activity: 2394
Merit: 5531
Self-proclaimed Genius
I saw your threads in this board, two of them can be easily tested with a testnet wallet, preferably Electrum testnet.

If you're interested in using it for your tests, read this thread created by tranthidung for more info about testnet:
Testnet Bitcoin. Activate, experience it, but don't trade and get scammed.

Read the info about the steps to run Electrum in testnet mode and the list of testnet faucets to get some test funds.
legendary
Activity: 1568
Merit: 6660
bitcoincleanup.com / bitmixlist.org


Sweeping is an operation that only depends on public keys, so address formats do not play a part in the sweeping process.

In Electrum, I think if I want to use only one seed and if my bosses require me to use different address types for salary payment. I can use import and has different address types for my receiving address in a same wallet file.

Use one native segwit wallet ("bc1"), and a separate nested segwit ("3") wallet whenever someone is trying to pay you from an exchange [some exchanges do not have bech32 code and cannot send to bc1 addresses] and then sweep from the "3" wallet to the "bc1" wallet.

Quote
With sweep, all UTXOs will be sent to a receiving address I type. Does it include dust UTXOs?

Absolutely. All UTXOs will be combined in a single transaction into a new output.
legendary
Activity: 3444
Merit: 10558
Is it worse or better than create three wallet files for three address types?
What is better?
It is hard to say which one is better because it depends on what you want to achieve. Generally speaking it is more convenient to have one deterministic wallet where you store a single seed phrase so that you can recover everything with that one.
Also after 5 years there shouldn't be anybody left who doesn't accept a simple native SegWit address. But if you have no other choice it is best to keep things to a minimum, like 2 wallets one Nested SegWit and another Native SegWit.

Quote
With sweep, all UTXOs will be sent to a receiving address I type. Does it include dust UTXOs?
Yes.
If you are receiving payments you don't need to sweep the keys though. Just spend the coins whenever you need to. If you want to combine the outputs from your 2 wallets as I explained above and you are using Electrum, you could create a new wallet from private keys that contain those coins from each of those addresses and combine UTXOs that way. Although this is a privacy hazard as it would link your addresses.
sr. member
Activity: 602
Merit: 387
Rollbit - the casino for you. Take $RLB token!
Thank you.

In Electrum, I think if I want to use only one seed and if my bosses require me to use different address types for salary payment. I can use import and has different address types for my receiving address in a same wallet file.

Is it worse or better than create three wallet files for three address types?

What is better?

With sweep, all UTXOs will be sent to a receiving address I type. Does it include dust UTXOs?
legendary
Activity: 3444
Merit: 10558
Sweep and import are fundamentally the same operation, they both receive a private key and either check for all possible addresses derived from that key or let the user explicitly define the address type (like Electrum does), then fetch all the UTXOs from each address.
Only the last step is different, in sweeping the wallet creates a transaction where it sends all the UTXOs to one of the addresses from your wallet but in importing it just creates an entry inside the wallet file.
sr. member
Activity: 602
Merit: 387
Rollbit - the casino for you. Take $RLB token!
Is it possible?

It is possible to import a private key and get different address type as long as a software supports it.

But is it possible to sweep with same private key?

I know I can import, get different receiving address types and move my Bitcoin to an address I want. Is it possible to simplify it with sweep?
Jump to: