How do I abandon Multibit Classic with leaving 0 balance behind ?

JohnBitCo

sr. member

Activity: 2030

Merit: 356

Quote from: sajrajs on June 08, 2017, 02:06:15 PM

Need advice please.

After waiting weeks for Multibit Classic 0.5.19 (latest) outbound transactions with default 0.0001 fee to confirm (forced viaBTC at the end), (which also left hanging one receiving address' balance as unspendable till fully confirmed) I want to abandon Classic and move to HD (any better wallet suggestions?).

Now I want to send 100% (- fee) of my balance to new wallet (leave 0 BTC in old one) but if I send something with default fee 0.0001 (can not find the way to adjust fee despite latest multibit's release notes says it has slider to adjust fee) it wil be stuck unconfirmed forever ...

What should I do:
- send with default fee of 0.0001 and hope this will ever confirm (or hope to be one of 100 to force viaBTC accelerator)?
- increase the fee, how do I do that in 0.5.19? no slider or setting where this could be changed identified on GUI ... I found somewhere it can be increased to max 0.0005 which would not help anyway, still no idea where this could be set .. and even if set perhaps useless

thanks for hint!

It may never come up, may never be an issue, but it is just too easy to keep at least one address that has been with you for some time.

MFahad

hero member

Activity: 2506

Merit: 645

Eloncoin.org - Mars, here we come!

Quote from: sajrajs on June 08, 2017, 02:06:15 PM

Need advice please.

After waiting weeks for Multibit Classic 0.5.19 (latest) outbound transactions with default 0.0001 fee to confirm (forced viaBTC at the end), (which also left hanging one receiving address' balance as unspendable till fully confirmed) I want to abandon Classic and move to HD (any better wallet suggestions?).

Now I want to send 100% (- fee) of my balance to new wallet (leave 0 BTC in old one) but if I send something with default fee 0.0001 (can not find the way to adjust fee despite latest multibit's release notes says it has slider to adjust fee) it wil be stuck unconfirmed forever ...

What should I do:
- send with default fee of 0.0001 and hope this will ever confirm (or hope to be one of 100 to force viaBTC accelerator)?
- increase the fee, how do I do that in 0.5.19? no slider or setting where this could be changed identified on GUI ... I found somewhere it can be increased to max 0.0005 which would not help anyway, still no idea where this could be set .. and even if set perhaps useless

thanks for hint!

Import and export is def the way to go. There is no reason to abandon the address, you never know when you might want to have a little "history" in a single account and show that you have been around for some time in the Bitcoin arena. There are a lot of paranoid people out there that have issues with the belief that someone is always trying to steal from them and that could make the difference.

HCP

legendary

Activity: 2086

Merit: 4361

Honestly... MultiBit HD is a "Bad Idea"™ right at this point in time...

Dev's have known about a fairly critical bug for a while... no fix as yet: https://github.com/keepkey/multibit-hd/issues/982

Just check all of the "Password did not unlock the wallet" threads here... Undecided

sajrajs

newbie

Activity: 3

Merit: 0

Much appreciated prompt responses.
Will consolidate my BTC in Multibit HD (like the key words approach with paper DR option) and considering HW wallet anyway. .. at least I am off legacy Multibit now so kudos to you!

NeuroticFish

legendary

Activity: 3668

Merit: 6382

Looking for campaign manager? Contact icopress!

Quote from: sajrajs on June 08, 2017, 03:26:30 PM

Thank you sir!
this worked!

I am using already electrum-ltc but unsure if electrum is fit for btc for me ... any risks to keep 2 electrums (1x btx, 1x ltc) on same VMware PC?

I don't have LTC nor electrum-ltc.
But I don't see any risk in use both, if they are well implemented they should act like 2 different programs with different data folders and so on.
If you are scared of this perspective, you can use electrum portable. That one keeps all its data in the folder you've unpacked it in and it will surely not interfere with anything else.

sajrajs

newbie

Activity: 3

Merit: 0

Thank you sir!
this worked!

I am using already electrum-ltc but unsure if electrum is fit for btc for me ... any risks to keep 2 electrums (1x btx, 1x ltc) on same VMware PC?

NeuroticFish

legendary

Activity: 3668

Merit: 6382

Looking for campaign manager? Contact icopress!

With Multibit Classic you usually have only one address in the wallet.
This means that you can export the private key (without password protection), copy/paste that private key into Electrum (one of the "create new wallet" options allows that) and you can use the very same wallet in Electrum.
From this point you can send your money with whatever fee, there are plenty of tutorials, or you can continue to use the very same address.

sajrajs

newbie

Activity: 3

Merit: 0

Need advice please.

After waiting weeks for Multibit Classic 0.5.19 (latest) outbound transactions with default 0.0001 fee to confirm (forced viaBTC at the end), (which also left hanging one receiving address' balance as unspendable till fully confirmed) I want to abandon Classic and move to HD (any better wallet suggestions?).

Now I want to send 100% (- fee) of my balance to new wallet (leave 0 BTC in old one) but if I send something with default fee 0.0001 (can not find the way to adjust fee despite latest multibit's release notes says it has slider to adjust fee) it wil be stuck unconfirmed forever ...

What should I do:
- send with default fee of 0.0001 and hope this will ever confirm (or hope to be one of 100 to force viaBTC accelerator)?
- increase the fee, how do I do that in 0.5.19? no slider or setting where this could be changed identified on GUI ... I found somewhere it can be increased to max 0.0005 which would not help anyway, still no idea where this could be set .. and even if set perhaps useless

thanks for hint!

Topic: How do I abandon Multibit Classic with leaving 0 balance behind ? (Read 689 times)