Also, I can't seem to find the topic I was reading somewhere the other day. It was the only story I ever heard where the corrupt 0.5.1 wallet was brute forced and the password looked similar, but had some characters altered. I am curious as to the structure the corruption looks like as I have been throwing tokens, wildcards and other additional switches (--typos-delete, --typos-swap..etc) at it for weeks now. Does anyone know if the character count is always the same or is there truncation of any type? What kind of characters where involved as in were they all english characters.

Also, I assume if this could have been done, it would have by now.
Why hasn't someone made a script that replicates the bug of 0.5.1 where you input the original password and it outputs at least a rough idea of what it became?

Maybe I am wrong too because I have read 2 different things that make the claim to the password not working.
The UTF-16 BE issue as well as another issue with the version number being included in 1 part of the encryption and not later on through.

I am pretty techy, but some of this is not entirely clear.

Description: Domain - AFFBIT.COM 
Starting bid: None
Buy it now: $1501
End date and time: No Expiration Set
Payment methods accepted: Anything GoDaddy accepts
Additional information: Nice Short 6L Domain. Search for it on Godaddy or use the domain itself goes to the GoDaddy landing page.

I originally purchased this domain with the intent to create an affiliate bitcoin site for making affiliate referral money like referring users to coinbase. I also entertained the idea of creating a private forum where it would accept bitcoin, but allow the members to refer others and get paid a referral or commision for the new member.

Also a noteworthy mention. There are some junk file left from the old install you may want to clear off before installing .5.0 just to guarantee a clean install.

That I think is the same boat the author and myself am currently in. HD also had the bug as well in it's .5.1 version.

I would try another copy of the original in case somehow 0.5.1 tainted that copy. Try to open it with Multibit .5.0

0.5.1 had a known bug of UTF16 having characters dropped and can indeed result in a password getting mistranslated into other characters. It is known with the exact version you are using e.g.
https://pascal-bergeron.com/en/posts/multibit-corrupt-password/

Look at the section regarding "When things don't go so well"
Some of the most basic recovery attempts in this case was to try opening with the prior version. Hopefully it was just a .5.0 version wallet considering you stated you were able to open "both" wallets but couldn't send. If you got in initially, that may actually have been the case because if it were the .5.14 bug in the software you would not have even been able to get into that wallet. If .5.0 gets you in....export your data..words..etc and recover with the private keys in something like electrum.

Hey if trying to open it with a prior version works...Share some love 

On this same note...Shouldn't someone have been able to make a script by now that would take a user's known password and simulate the bug in order to find out what it became?

This is a pretty deep issue I have been working on and off at for the last few years for somebody and my bounty is .2 bitcoin out of the deal.

It is a tricky situation, but maybe someone might know of a way...

Wallet was affected by the 0.5.1 bug where you know the password, but upon reopening the wallet it tells you that the password is incorrect. From what I have read among the issues of Multibit's downfall was that there was issues with how UTF16 and UTF8 worked. Some of the characters would end up mangled into other characters for some people.

What makes the issue more complex is that this was the 1 time the person did not write down the seed words.

I have tried many different ways, but I am really curious about what I find in the .YAML files.

0.5.1 version YAML files contain values for:
encryptedPassword: "88 Characters with /, + and 2 = signs at the end"
encryptedBackupKey: "64 Characters with / symbols"

Not sure if I am missing a step, but when I run base64 decode I get an output of ">����P�......etc"

I feel I am missing something, but maybe someone can clarify what I am doing wrong here.

Does anyone at all know what these 2 values in the YAML file could be used for?
I guess I am going to do a deep dive into the Multibit HD code itself to find out how it gets utilized, but if in the meantime anybody actually knows something about this.

I hope I can figure this out because my cut is about $20K worth of the BTC.

Yeah I have decoded it, but what is the use of it? Is this only a part of what is needed for decrypting the backup files?

     I have a Multibit HD wallet that has more than .5 BTC in it that needs recovering.
It is a pretty rough situation I am trying to workout for someone and is as follows.
The person was really good about keeping seed words up until this last time.
He then became affected by the error of knowing the password, but it doesn't unlock the wallet.

I have tried:
mbexport and forked version
decrypt_bitcoinj_seed-master
I have run many different token variations on the password in hopes that it gets a bite if just some of the characters were off (from what I read that bug related to how UTF 16 translated?).

     What I do find interesting is that the old YAML files from the prior wallets (version 0.4.1) of Multibit HD only had some basic preferences settings (Show balance: true..etc). However, the YAML files for the 0.5.1 version of Multibit HD has 2 values show as:
encryptedPassword: 88 Characters with +, / and == at the end
encryptedBackupKey: 64 Characters with / and + but no = sign

     My main question for the post is to find out where these would be useful as I do have the rolling and zip backup files as well.

Bump

What do you mean by that exactly...especially with the interest part?

I am talking about one-time commissions for sales or say a membership referral.

bump

They are not asking to purchase it, but rather develop on it as a partnership. If they offered to purchase it I would be totally willing if the price was right. The name is HashRules.com that is getting the most requests for these "partnership" deals.

I am surprised they haven't noticed I have HashOnDelivery.com which is probably just asking for it...lol

bump

Bump!

Agreed. I am a newbie too, but if you don't respect forums for what they will provide back for legitimate use, then you probably shouldn't be using it. Plus the topic rules states this should not be meaningless posting.

"Due to an abundance of topics filled with low quality replies, we are banning all topics where the only reasonable reply is insubstantial content. This was already the rule:

1. No zero or low value, pointless or uninteresting posts or threads.
...
3. No pointless or uninteresting threads."


Also, I wonder what number 2 was 

So...
I purchased many domain names revolving around hashing. I thought they would be great for starting a mining pool, developing my own miner...etc. Turns out my email is receiving requests from people who want to use my names in a partnership for the other double entendre of the word hash   I mean I heard of silk road and all that was involved with it, but is this still a big thing online with doing drug deals (personally I don't think hash should be illegal anyways).

Anyways, I can only assume these partnership requests are really just to run the illegal operation with me being the only scapegoat liable.

Bump! I am probably more flexable than most people trying to sell domains (and mine are not all that bad). I'll be humble in saying I know some are not the greatest, but come on...HashRules.com? ReadyHash.com

Anyways I could really go so many ways with these. If anyone wants to collectively start a mining pool of our own, I am down. I have 3 different hosting accounts for various reasons.

I have one one that allows Whois lookups the be performed (Port 43 is open). Many Hosting companies will not do that for you because it allows you to compete with them by offering domain availability lookup.

I actually have way more domains available to me in my portfolio (medical, lawyer, technology, dating...etc), but didn't see a point in advertising them for sale/trade.

Has anyone used any good bitcoin related affiliate scripts for site referrals   ? I'd plan to setup a site with my domain AFFBIT.com in the near future.

"Bit" and "Hash" related domain names. Feel free to make a reasonable offer. I am open to trading for bitcoin or selling.

HASHRULES.COM - Hash Rules .COM ........lol on so many levels
HASHRULES.INFO - Hash Rules .INFO

PDBIT.COM - 5 Characters

AFFBIT.COM - 6 Characters - Perfect for an affiliate site

BFGBIT.COM - 6 Characters
BITBFG.COM - 6 Characters

UNABIT.COM - 6 Characters

OSHASH.COM - 6 Characters - Perfect for a dedicated mining Operating System

ABITROUGH.COM - A Bit Rough .COM
BITCRISIS.COM - Bit Crisis .COM
BITNOSEY.COM - Bit Nosey .COM
BITOFACTION.COM - Bit of Action .COM
BITROUGH.COM - Bit Rough .COM
BITTHEBULLET.COM - Bit the Bullet .COM
BULLETBIT.COM - Bullet Bit .COM

ATIHASH.COM - ATI Hash .COM
HASHandPRIZES.COM - Hash and Prizes .COM
HASHBUST.COM - Hash Bust .COM
HASHONDELIVERY.COM - Hash on Delivery .COM
HEXHASH.COM - Hex Hash .COM
INAHASH.COM - In a Hash .COM
READYHASH.COM - Ready Hash .COM
STRAPPEDFORHASH.COM - Strapped for Hash .COM


Non Crypto/Mining Related
OLEDSHOPPING.COM - OLED Shopping .COM
QRCODEDSHIRT.COM - QR Coded Shirt .COM
WHOCOULDRESIST.COM - Who Could Resist .COM