MultiBit

[OmegaStarScream]

Hi there Jim , Are you planning to do this or you are totally against the BitcoinXT ? : https://bitcointalk.org/index.php?topic=1153684.0

[jim618]

Hi OmegaStarScream,

We quite like Bitcoin XT as we think the block size needs to increase.

As to what will happen if/ when there is a hardfork:

Currently MultiBit Classic and HD both will follow the chain with the most work done in it.
Thus in a hardfork all the existing MultiBit code will follow the 'winner'. This is how the normal one or two block forks (that occur reasonably frequently) get resolved so it should just be the same but on a larger scale.

Both MultiBit Classic and HD connects to Bitcoin Core and XT happily and they should work correctly with larger blocks. The bloom filtered blocks Core/ XT send back to MultiBit are the same - MultiBit is agnostic about connecting to Core or XT.

Thus at the moment we don't think we will have to make any code changes because of a block size increase/ hardfork

There is also a checkpoint file in MultiBit that is used to speed up wallet replays. That specifies which is the 'correct' block header every 2000ish blocks. After a fork that file will specify the block header in the 'winning' fork. That'll be a couple of weeks after a fork occurs so it should be cut and dried then.

Jim

[lunarboy]

Any plan to introduce a promt for sliding competitive fees?

September could be an awkward month otherwise http://www.ibtimes.co.uk/coinwallet-plans-bitcoin-dust-attack-september-create-30-day-transaction-backlog-1515981

[nikona]

Hey jim, was wondering if you had any updates on the issue here

https://bitcointalk.org/index.php?topic=43616.msg11313861#msg11313861

I still do get it occasionally.

[jim618]

Any plan to introduce a promt for sliding competitive fees?

September could be an awkward month otherwise http://www.ibtimes.co.uk/coinwallet-plans-bitcoin-dust-attack-september-create-30-day-transaction-backlog-1515981

Yeah we have a version 0.5.19 in the works with a fee slider (it's the MultiBit HD fee slider, backported).
I saw that article too.

[jim618]

Hey jim, was wondering if you had any updates on the issue here

https://bitcointalk.org/index.php?topic=43616.msg11313861#msg11313861

I still do get it occasionally.

Yes, most of the time restarting MultiBit fixes this as it retransmits the transaction.

[pawel7777]

Any plan to introduce a promt for sliding competitive fees?

September could be an awkward month otherwise http://www.ibtimes.co.uk/coinwallet-plans-bitcoin-dust-attack-september-create-30-day-transaction-backlog-1515981

Yeah we have a version 0.5.19 in the works with a fee slider (it's the MultiBit HD fee slider, backported).
I saw that article too.

Nice.

Could you bump this thread when 0.5.19 is released?

[IanFoxley]

Hi Guys.

Question

I am using still old version of Multibit Version 0.5.18 and recently I am getting payments with the following error message.

This transaction is not standard and should be not be trusted.

I emailed the support of where I get the payouts from and they told that they recently started using Bitcoin XT.

So is this error just related to this?

I am going to upgrade my wallet soon so I guess this might not be an issue.

Just putting it out there anyway.

Ian

[Tstar]

why do we have to synchronize multibit everytime we open it ,i dont get the point involved in it
and plus it would be better if there were names to the wallet's.

[jim618]

You can minimise the amount of synchronising by never closing the wallet using the 'File | Close wallet' option. If you simply close the app then when you restart it will just sync from the last block it knew about.

The wallets DO have names. In MultiBit Classic you can click on the name of the wallet in the list of wallets and simply type in the name you want.

In MultiBit HD the sync is simpler as you don't have the 'open/close' wallet paradigm and you have both a wallet name and (longer) comment field.

[tspacepilot]

Hi Guys.

Question

I am using still old version of Multibit Version 0.5.18 and recently I am getting payments with the following error message.

This transaction is not standard and should be not be trusted.

I emailed the support of where I get the payouts from and they told that they recently started using Bitcoin XT.

So is this error just related to this?

I am going to upgrade my wallet soon so I guess this might not be an issue.

Just putting it out there anyway.

Ian

That is an interesting little message.  As far as I understand it, even if the transaction was mined with an XT node, as long as you keep an eye on the blockchain and can see that the chain has not forked (with your transaction in the wrong chain) for several blocks, you shouldn't have to worry about a double-spend attempt.  The original Satoshi whitepaper has a bunch of info on just how increasingly difficult it is to try to double-spend with each successive confirmation (NB: it's pretty hard!).

[z0n0]

Anyone else having problems with password?
It says wrong password when I want to send - is there a way I can recheck the password?

[OmegaStarScream]

Anyone else having problems with password?
It says wrong password when I want to send - is there a way I can recheck the password?

Check this page out : https://multibit.org/en/help/v0.5/help_lostOrForgottenPassword.html All you need to know is here .

If you have really, truly lost or forgotten your password and you only have encrypted wallets, then it is likely that you have lost access to your bitcoin. There is absolutely no way that the MultiBit team can possibly recover them.

You should keep the encrypted files safe just in case inspiration strikes. Never delete a private key, just archive it safely

[z0n0]

Anyone else having problems with password?
It says wrong password when I want to send - is there a way I can recheck the password?

Check this page out : https://multibit.org/en/help/v0.5/help_lostOrForgottenPassword.html All you need to know is here .

If you have really, truly lost or forgotten your password and you only have encrypted wallets, then it is likely that you have lost access to your bitcoin. There is absolutely no way that the MultiBit team can possibly recover them.

You should keep the encrypted files safe just in case inspiration strikes. Never delete a private key, just archive it safely

fuck me
the thing is i'm 99,9% i didn't forget it, cuz I have it written on paper

[z0n0]

The removal of the password failed. The error was "Could not decrypt bytes". --------> that's worng pasword or something else?
I'm using 0.5.18 version

[nikona]

Hey jim, was wondering if you had any updates on the issue here

https://bitcointalk.org/index.php?topic=43616.msg11313861#msg11313861

I still do get it occasionally.

Yes, most of the time restarting MultiBit fixes this as it retransmits the transaction.

Thanks for the answer. Also can you address the first issue as well ?

https://bitcointalk.org/index.php?topic=43616.msg11230732#msg11230732

[f3tus]

The removal of the password failed. The error was "Could not decrypt bytes". --------> that's worng pasword or something else?
I'm using 0.5.18 version

https://bitcointalk.org/index.php?topic=813278.0

[RustyNomad]

Are there any plans in the works for MultiBit to support multiple account on a Trezor?

If not mistaken it currently still just support the first account in a wallet. I have 4 accounts in my wallet on the Trezor and because of this cannot use MultiBit but would like to.

[jim618]

Hi Rusty,

Unfortunately no - we are expecting only to be able to support the first account going forward.
This is for reasons to do with how we bloom filter the data coming from Bitcoin Core/ XT nodes. There is a more technical description of why in the blog article here:

https://multibit.org/en/help/hd0.1/how-spv-works.html

It's the section: Bloom filtering and single HD account support


It's one of the limitations of connecting directly to the Bitcoin Core/ XT nodes that there isn't a practical way round, IMHO.

Jim

[RustyNomad]

Hi Rusty,

Unfortunately no - we are expecting only to be able to support the first account going forward.
This is for reasons to do with how we bloom filter the data coming from Bitcoin Core/ XT nodes. There is a more technical description of why in the blog article here:

https://multibit.org/en/help/hd0.1/how-spv-works.html

It's the section: Bloom filtering and single HD account support


It's one of the limitations of connecting directly to the Bitcoin Core/ XT nodes that there isn't a practical way round, IMHO.

Jim

Thanks for the reply and the link, missed it somehow when I was on the site.

I now understand the reasons why only the first account is supported.