[ANN]🌀 Blur Network(BLUR) 🌀 | PoW Cryptonight-Dynamic | CPU/Solo Mining | DPoW

[qq386437050]

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!
https://i.postimg.cc/FKfD4xdW/7643.png
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?

I encountered the same situation.

[blurnetwork]

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?

This is occurring because of Microsoft's use of ANSI & wide-set characters in their codepages, and not utf-8 like the rest of the world.  As our entire codebase relies on unicode, things get particularly wonky on Windows, at times.  If you research, Monero, and every other cryptonote coin also experienced this issue and others.... again, only on Windows.  Linux Wallets and Mac wallets have never had errors like this.  If you know a Windows developer, kindly, refer him or her our way

As for whether or not the software is tested for free... No, it is not, it is tested at the cost of my time and effort -- just the same as yours.  Only, I don't test stringently on Windows because I have spent 5 months developing software for you to bash .... for free.


You will need to import your 25-word seed that was given to you with the wallet, when you created it.  You should have this backed up.  Open a Powershell and start with the flag

Code:

.\blur-wallet-cli.exe --restore-deterministic

and follow the prompts.

[blurnetwork]

I encountered the same situation.

Please join our Discord (link is in the first post of this thread) for troubleshooting in the future.  I am active on there almost all day, and we have a few hundred active community members participating in discussion and helping each other troubleshoot, or work out simple mistakes.  Very helpful for everyone involved.

[economist2000]

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!

This is occurring because of Microsoft's use of ANSI & wide-set characters in their codepages, and not utf-8 like the rest of the world.  As our entire codebase relies on unicode, things get particularly wonky on Windows, at times.  If you research, Monero, and every other cryptonote coin also experienced this issue and others.... again, only on Windows.  Linux Wallets and Mac wallets have never had errors like this.  If you know a Windows developer, kindly, refer him or her our way

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

[blurnetwork]

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.

There is no Windows developer. I am the only core developer working on this entire project, currently. Anyone can contribute code on Git but very few do so.  We are always open to working with new developers, too.

It is not a keyboard layout that the issue concerns.  Rather, its the way your text is rendered.  Windows uses Wide-set UTF-16 (which is no longer backwards compatible with ASCII). So the fact that it is composed of numbers holds zero difference, as it is still a string of text, not bytes.  Just because you read a number doesn't mean that a machine reads it at all.

Our code runs on UTF-8 so that means that anywhere that Windows has to process text, necessitates a special condition and conversion into windows-compatible text.  Your machine reading text differently than you do, and needing to convert it, is the reason your password is showing as incorrect.  

For those who use computers for devops or anything in compsci really, Windows is nothing more than a huge headache with restraints.  Due to this, Windows developers are harder to come by. Windows is intentionally unwieldy.  Microsoft's doing.  (My opinion, although I'm certain many would agree)

[blurnetwork]

https://docs.microsoft.com/en-us/windows/desktop/Intl/unicode

Further reading if you care to learn more about it. ^^^

[Rabinovitch]

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?

I have the same issue with newest cli wallet.



The wallet can be opened with the same password in previous versions (blur-v0.1.7-win-x86_64 to be exact).

[economist2000]

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.

[pomartin]

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.

In new projects some issues are expected. Small team means slower problem solving but in most cases more robust design. It is normal.
For one that is less computer-literate this can present a bigger problem, I agree. But a working solution is avaliable for anyone and community would be there to help you set up temporary solution if only you'd present them your problem. Visit discord once in a while, it is there for a reason.

[TheVeteran]

The note to restore the Windows wallet in version 0.1.7.6 with the seed worked like a charm. As long as I don't have to do that every time a new wallet version comes out I don't mind.

[kyriores]

In case you didn't write down your 25-word mnemonic, here's how to get it back and restore the wallet under the new version:

* Open the blur-wallet-cli.exe of an older version
* Sign in to your wallet
* Type encrypted_seed and hit enter
* Enter your password again and hit enter
* Hit enter twice (unless you have an optional seed encryption passphrase)
* Copy the 25 words
* Go to the folder where you saved the files of the newest version
* Type powershell in the address bar of that folder and hit enter
* Type .\blur-wallet-cli.exe --restore-deterministic and hit enter
* Create a wallet file and paste the 25 word mnemonic when prompted (it asks you to paste it line by line)
* You should have the new wallet files in the folder

[blurnetwork]

The note to restore the Windows wallet in version 0.1.7.6 with the seed worked like a charm. As long as I don't have to do that every time a new wallet version comes out I don't mind.

You shouldn't have to now that the code has been updated with specificity for Windows cases.

Credit to the RYO currency guys for their code which I ported over for these changes.

[blurnetwork]

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.

In new projects some issues are expected. Small team means slower problem solving but in most cases more robust design. It is normal.
For one that is less computer-literate this can present a bigger problem, I agree. But a working solution is avaliable for anyone and community would be there to help you set up temporary solution if only you'd present them your problem. Visit discord once in a while, it is there for a reason.

In case you didn't write down your 25-word mnemonic, here's how to get it back and restore the wallet under the new version:

* Open the blur-wallet-cli.exe of an older version
* Sign in to your wallet
* Type encrypted_seed and hit enter
* Enter your password again and hit enter
* Hit enter twice (unless you have an optional seed encryption passphrase)
* Copy the 25 words
* Go to the folder where you saved the files of the newest version
* Type powershell in the address bar of that folder and hit enter
* Type .\blur-wallet-cli.exe --restore-deterministic and hit enter
* Create a wallet file and paste the 25 word mnemonic when prompted (it asks you to paste it line by line)
* You should have the new wallet files in the folder

Thank you both for supporting the project and helping others find solutions

[blurnetwork]

For the errors when running blurd.exe with startup flags on Windows:

If you are seeking to run the daemon with start-up flags (i.e. --start-mining or similar) the argument for the flag must be passed with an = sign instead of a space.  Such that, what would have previously been written --log-level 3 must now be written --log-level=3.  Similarly, to start mining to an address in daemon, the following is an example of the correct syntax:
 
Using cmd.exe:

Code:

blurd.exe --start-mining=<address> --mining-threads=<# of threads>  

Fill the bracketed areas with your subjective values, omitting the brackets.

Using powershell:

Code:

.\blurd.exe --start-mining=<address> --mining-threads=<# of threads>

[economist2000]

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.

[rattle99]

How are the earnings on this?
How much are you guys making with what CPU?

[economist2000]

How are the earnings on this?
How much are you guys making with what CPU?

Price = 0.

[blurnetwork]

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.

Sounds like the issue is on your end.

[blurnetwork]

How are the earnings on this?
How much are you guys making with what CPU?

We are currently awaiting listing on Bisq.  Join our discord for p2p trades until then.  We are hopeful with some other prospects for listing as well.

[economist2000]

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.

Sounds like the issue is on your end.

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.