Here is an example of one of the wallets:

As for the transactions for November 6 (if I'm not mistaken), I have doubts, because I was getting the old version of the wallet, because I did not know about the next fork. But transactions from October 27 to November 5 inclusive should be in this wallet. At the end of November 5, there were 627 coins in it. It was produced mainly with version 0.1.7.5, since in 0.1.7.5.1 there was a problem with sending transaction: while the wallet was trying to send 1 BLUR (more than a day) not a single block was found.
A вoт чтo я вижy в кoшeлькe 0.1.8.1 (0.1.7.6, 0.1.7.6.1):
- transactions only for October 26-27. No outgoing no.

Let me remind you, the problem began with the wallet version 0.1.7.5 simply ceased to be opened in later versions, allegedly entered incorrect password, but the password was very simple and consisted only of digits. That is why decided to restore a purse.

I dug in several wallets. I controlled the complexity of the found blocks so that the chain was the main one. A friend from another city has exactly the same story: 90-95% of coins are lost. In version 0.1.7.5 they are, in the later there is not. For this reason, I stopped getting a coin: I lost about 5000 BLUR.
The representative of the wallet developer refuses to recognize the problem. Presumably, the problem exists only in the windows version of the wallet.
Another chain is impossible: on each machine had its purse and couldn't they all prove the alternative chain.

I tried to restore the wallet in version 0.1.8.1. Everything also recovers 77 coins out of 600 approximately.

Why is the curvature and dampness of your software not a topic for discussion here? I lost 95% of my coins due to the incompatibility of the wallets version 0.1.7.0 (0.1.7.5) and 0.1.7.6 and the broken recovery mechanism.
It’s not for me that the wallet recovery does not work, just not all of them write here.
And this is not about lost 600 coins - I have a lot of wallets, everywhere the situation is similar. Of the 700 coins, for example, only 21 recovered. What is it like?
In version 0.1.7.6.1, none of these problems are fixed.
Is there any guarantee that I will get my coins back? I left the coin, I see no reason to dig what I can lose at any moment due to the fault of the developers. I already had the sad experience of losing 900000 SIA in incompatible wallets. Where there was the possibility of export, but it did not work.
And about the various encodings: I created a wallet without a password at all, just pressed ENTER instead of a password. This wallet also does not open in 0.1.7.6.

Unfortunately, this does not help. Coins are restored only from November 6 (77 pcs.).

I made this instruction, I restored only transactions for approximately 5 or 6 November. The wallet was created on October 27, it should be more than 600 coins. Where are they?

Tested on 5 computers with different users, with different providers in different cities.
At the same time, on computers where the wallet was not restarted, there is a connection, blocks are searched.

Price = 0.

Now the blurd.exe is not synchronized after restarting with the network. Brilliant! Removing the database did not help. she just shakes nothing. In the system, nothing has changed. Tested on 5 computers with different users, with different providers in different cities.

Clearly. It is very a pity, that you develop the product for 1,5 % of users while more than 70 % of users have remained without your support.
It is a pity to me of the spent tens hours on this coin and thousands hours of machine time. About the coins it is possible to forget simply. In a week there will be any 0.1.7.7 version, and at it also it can not appear compatibilities with earlier created purses.

I will reveal a little secret: my password consists only of numbers. Does the keyboard layout affect passwords from numbers? And why did everything work in versions 0.1.7.0 and 0.1.7.5, and now the Windows developer was to blame?

Linux is certainly great, but not everyone can use it and not everyone wants to use it.
And the prevalence of Linux leaves much to be desired.
https://cdn.comss.net/img/012017/2018-09-03_12.02.15.png

Dear developers!
Tell me please, do you test your glitches at all, or do your clients do it for you for free? I personally got tired of testing your raw software for 1.5 weeks for free! The wallet does not open. At all! After entering the password, the console closes!

I enter the password correctly!
Everything worked fine, then just broke everything. How was it possible? How was it possible to change the algorithm, even if elementary things do not work?

сейчас эту монету выгоднее купить, чем копать. но были и иные времена... эх...

Просто топик создавался, когда награда монеты была всего лишь в 100 раз больше. Затем у ее создателей поменялись настроения и награду незапланированно уменьшили в 100 раз. Но увы, чуда не произошло, монета после этого не взлетела. А самое печальное, что из-за атаки 51 значительная часть монет оказалась похоронена на биржах. Ну а недавнее переименование темы - надеюсь, у создателей монеты есть не только чувство юмора, но и планы на монету сохранились, а то некоторое время назад совсем печальное было сообщение...

Да, около того. ))) И удивительно еще, что сеть 30-40 кх. )))

На чем же Вы ее копаете, если неделями блок ждете?
20 сек на блок = 4320 блоков в сутки. Не буду писать про современные процессоры, древний и5-2500 жмет 0,65 кх и приносит 0,65/40*4320 = 70 блоков в сутки. Какие недели
Все дело в цене монеты. Ну, или в награде за блок, которую уменьшили. Когда монета была на пике, сеть была 400-600 кх и никто не жаловался.

I compared the creation dates and the size of the files of version 0.1.7.5 (second edition) and 0.1.7.5.1 - they are the same! 10/31/2018. In vain I spent time on testing 0.1.7.5.1. Therefore, the launch of the daemon on 7-ke was not fixed.

i5-2500, i5-2500K, i7-2600K, FX 8320E.
Linux does not suit me for many reasons.

I would be happy to switch to 0.1.7.5.1, but this version also does not work under Win 7.
Cигнaтypa пpoблeмы:
  Имя coбытия пpoблeмы:   APPCRASH
  Имя пpилoжeния:   blurd.exe
  Bepcия пpилoжeния:   0.0.0.0
  Oтмeткa вpeмeни пpилoжeния:   5bd9298c
  Имя мoдyля c oшибкoй:   blurd.exe
  Bepcия мoдyля c oшибкoй:   0.0.0.0
  Oтмeткa вpeмeни мoдyля c oшибкoй:   5bd9298c
  Кoд иcключeния:   c000001d
  Cмeщeниe иcключeния:   000000000046c637
  Bepcия OC:   6.1.7601.2.1.0.256.1
  Кoд языкa:   1049
  Дoпoлнитeльныe cвeдeния 1:   5056
  Дoпoлнитeльныe cвeдeния 2:   505614abf15c923b7d26ec9a0287aad8
  Дoпoлнитeльныe cвeдeния 3:   3e36
  Дoпoлнитeльныe cвeдeния 4:   3e367d7ef35e9562bb8251cc33ad1fa5