Monero Support

[smooth]

Now that the terminology has been changed from "wallet" to "account", this breaks readability of old wallet.bin files, correct? How does one convert a wallet.bin to an account.bin?

I don't think so, you can rename your wallet .bin file to anything you want. Doesn't have to be wallet.bin

Yes the files can be renamed but rename all three of them. Alternatively use --wallet to specify the file name.

[1714804353]

1714804353

[1714804353]

1714804353

[1714804353]

1714804353

[mmortal03]

Now that the terminology has been changed from "wallet" to "account", this breaks readability of old wallet.bin files, correct? How does one convert a wallet.bin to an account.bin?

I don't think so, you can rename your wallet .bin file to anything you want. Doesn't have to be wallet.bin

Yes the files can be renamed but rename all three of them. Alternatively use --wallet to specify the file name.

Hmm, okay, must be something broken in the newest version of the .NET GUI, then. I tried renaming all three of them and tried to load them in the newest version of the .NET GUI (supposedly you can't create wallets with the latest version but it can still read them) and it would crash. I'll go mention it in the other thread.

[Spekulatius]

Hi,

I just downloaded the latest version for Windows 64bit (v0.8.8.2) and pasted it over my older v0.8.5 install.

I left everything else in the folder, including my wallet.bin and wallet.bin.keys files (which I called "mein_wallet.bin" and "mein_wallet.bin.keys").

After starting bitmonerod.exe it synchronizes with the network for some time till it tells me that it is synchronized and I can start up simplewallet.exe
When I do, it synchronizes as well until it reaches the last block and shuts itself down with out warning. Restarting simplewallet.exe yields the same result.

This is the simplewallet.log print out:

Code:

2014-Aug-31 14:41:37.393025 bitmonero wallet v0.8.8.2(0.1-g1b8a68f)
2014-Aug-31 14:42:19.646442 bitmonero wallet v0.8.8.2(0.1-g1b8a68f)
2014-Aug-31 14:42:22.131584 ERROR ..\..\src\wallet\wallet2.cpp:552 e || !exists. THROW EXCEPTION: error::file_not_found
2014-Aug-31 14:42:22.132584 ..\..\src\wallet\wallet2.cpp:552:struct tools::error::file_error_base<1>: file not found "mein_wallet.bin.keys"
2014-Aug-31 14:42:22.132584 Error: failed to load wallet: file not found "mein_wallet.bin.keys"
2014-Aug-31 14:42:22.135584 ERROR ..\..\src\simplewallet\simplewallet.cpp:387 could not open account
2014-Aug-31 14:42:22.135584 ERROR ..\..\src\simplewallet\simplewallet.cpp:1199 Failed to initialize wallet

[Spekulatius]

Hi,

I just downloaded the latest version for Windows 64bit (v0.8.8.2) and pasted it over my older v0.8.5 install.

I left everything else in the folder, including my wallet.bin and wallet.bin.keys files (which I called "mein_wallet.bin" and "mein_wallet.bin.keys").

After starting bitmonerod.exe it synchronizes with the network for some time till it tells me that it is synchronized and I can start up simplewallet.exe
When I do, it synchronizes as well until it reaches the last block and shuts itself down with out warning. Restarting simplewallet.exe yields the same result.

This is the simplewallet.log print out:

Code:

2014-Aug-31 14:41:37.393025 bitmonero wallet v0.8.8.2(0.1-g1b8a68f)
2014-Aug-31 14:42:19.646442 bitmonero wallet v0.8.8.2(0.1-g1b8a68f)
2014-Aug-31 14:42:22.131584 ERROR ..\..\src\wallet\wallet2.cpp:552 e || !exists. THROW EXCEPTION: error::file_not_found
2014-Aug-31 14:42:22.132584 ..\..\src\wallet\wallet2.cpp:552:struct tools::error::file_error_base<1>: file not found "mein_wallet.bin.keys"
2014-Aug-31 14:42:22.132584 Error: failed to load wallet: file not found "mein_wallet.bin.keys"
2014-Aug-31 14:42:22.135584 ERROR ..\..\src\simplewallet\simplewallet.cpp:387 could not open account
2014-Aug-31 14:42:22.135584 ERROR ..\..\src\simplewallet\simplewallet.cpp:1199 Failed to initialize wallet

Ok, I made some progress: In order to start up simplewallet.exe I made a shortcut of it, already containing the parameters like "--wallet-file=mein_wallet.bin", etc. I forgot to change the path in the shortcut's target field to the correct install directory of Monero, so it was looking for the .keys file in the wrong folder all the time (the folder where I unzipped the update in originally). Now the .keys file is found correctly and my account can be accessed but only for the fraction of a second after starting up simplewallet.exe because it shuts itself down right after catching up to the blockchain and I cant do anything there. The simplewallet.log reads:

Code:

2014-Aug-31 17:00:20.798096 bitmonero wallet v0.8.8.2(0.1-g1b8a68f)
2014-Aug-31 17:00:21.659146 Loaded wallet keys file, with public address: XXXXXXxXwmDs3R6rGkRHFJmjtk78KH87LsJSanmnxDF1xkyxeH3MeJZhZNdzNNF4DgYV8aGZoFFqNSfqVmhuUHhGyvvxgK
2014-Aug-31 17:00:21.692148 Opened wallet: XXXXXXxXwmDs3R6rGkRHFJmjtk78KH87LsJSanmnxDF1xkyxeH3MeJZhZNdzNNF4DgYV8aGZoFFqNSfqVmhuUHhGyvvxgK
2014-Aug-31 17:00:21.706148 Starting refresh...
2014-Aug-31 17:00:25.287353 Block is already in blockchain: 88dcff2abdaa6d274230015bb81ffb2cc56be538c3fb07703636dfff6c8c89c1
2014-Aug-31 17:00:25.287353 Refresh done, blocks received: 0, balance: XXX.XXX068362138, unlocked: XXX.XXX068362138
2014-Aug-31 17:00:25.289353 Refresh done, blocks received: 0
2014-Aug-31 17:00:25.290353 balance: XXX.XXX068362138, unlocked balance: XXX.XXX068362138
2014-Aug-31 17:00:25.292353 **********************************************************************
Use "help" command to see the list of available commands.
**********************************************************************

I redacted the first digits of my public address and balance for privacy reasons.

[jwinterm]

After starting bitmonerod.exe it synchronizes with the network for some time till it tells me that it is synchronized and I can start up simplewallet.exe

You can try deleting/moving your binary wallet file (default name wallet.bin) and just keep your keys file (wallet.bin.keys), and then let simplewallet rebuild the binary file. If you're moving a wallet file from 32-bit to 64-bit this can definitely be an issue, also moving from *nix to windows I think.

[GreekBitcoin]

After starting bitmonerod.exe it synchronizes with the network for some time till it tells me that it is synchronized and I can start up simplewallet.exe

You can try deleting/moving your binary wallet file (default name wallet.bin) and just keep your keys file (wallet.bin.keys), and then let simplewallet rebuild the binary file. If you're moving a wallet file from 32-bit to 64-bit this can definitely be an issue, also moving from *nix to windows I think.

make some backups btw.

[nuxxer]

is there any difference of profit between low diff and high diff ?  #same hardware in this case.

[GreekBitcoin]

is there any difference of profit between low diff and high diff ?  #same hardware in this case.

You mean at pools? Generally no. Pools will find optimal diff for your miners after some time. If you have really low end miners just use low diff.

[nuxxer]

is there any difference of profit between low diff and high diff ?  #same hardware in this case.

You mean at pools? Generally no. Pools will find optimal diff for your miners after some time. If you have really low end miners just use low diff.

yes, at pools. but how about pools with static diff ? if we choose diff for default hardware, it will keep on default hardware.

[netmonk]

yes there is a difference.

In fact you have to submit validshare in the limited time of validity (before getting new job).

So for a given hashrate power there is a maximum diff which will let you submit your work before beeing too late.

The reward will be calculated like this : (sum(all your submitted share diff)*reward)/sum(all submitted share diff)

So if for exemple you submitted 5 valid share at 1000 diff, and in the same time another miner submitted 1 validshare at 10000 diff, your reward will be
(5000)*reward/15000: 1/3 reward.

Bit if you raise the diff to 2000 and its too big for your computer and only submit 2 valid share your reward will be 4/15 of rewards which is less than 1/3.

So if you read your log and see that pool reject some of your share, it means the diff is too big for your computer and then must be lowered.

And if you think continue the analysis, you can also understand that sometime raising a little the diff is not so efficient. Given the fact that you will may be have more rejected share.

[smooth]

This is not really accurate. Whether you find a share is random. So if you raise diff from 1000 to 2000 and your average shares drops from 5 to 2.5, you will sometimes submit 2 but sometimes 3, on average (of course other numbers are also possible -- this is just an illustration). Those times when you submit 3, you will get 6/15 of the reward, which is higher than 1/3. It averages out. But your rewards will be more volatile (sometimes 2 sometimes 3).

yes there is a difference.

In fact you have to submit validshare in the limited time of validity (before getting new job).

So for a given hashrate power there is a maximum diff which will let you submit your work before beeing too late.

The reward will be calculated like this : (sum(all your submitted share diff)*reward)/sum(all submitted share diff)

So if for exemple you submitted 5 valid share at 1000 diff, and in the same time another miner submitted 1 validshare at 10000 diff, your reward will be
(5000)*reward/15000: 1/3 reward.

Bit if you raise the diff to 2000 and its too big for your computer and only submit 2 valid share your reward will be 4/15 of rewards which is less than 1/3.

So if you read your log and see that pool reject some of your share, it means the diff is too big for your computer and then must be lowered.

And if you think continue the analysis, you can also understand that sometime raising a little the diff is not so efficient. Given the fact that you will may be have more rejected share.

[Spekulatius]

After starting bitmonerod.exe it synchronizes with the network for some time till it tells me that it is synchronized and I can start up simplewallet.exe

You can try deleting/moving your binary wallet file (default name wallet.bin) and just keep your keys file (wallet.bin.keys), and then let simplewallet rebuild the binary file. If you're moving a wallet file from 32-bit to 64-bit this can definitely be an issue, also moving from *nix to windows I think.

make some backups btw.

Thx, I already did. Anyway my problem still persists, any ideas how to fix it?

[GreekBitcoin]

After starting bitmonerod.exe it synchronizes with the network for some time till it tells me that it is synchronized and I can start up simplewallet.exe

You can try deleting/moving your binary wallet file (default name wallet.bin) and just keep your keys file (wallet.bin.keys), and then let simplewallet rebuild the binary file. If you're moving a wallet file from 32-bit to 64-bit this can definitely be an issue, also moving from *nix to windows I think.

make some backups btw.

Thx, I already did. Anyway my problem still persists, any ideas how to fix it?

I dont really have any other ideas. Did you try to make another wallet and see if it works? I am asking on IRC to check for a fix...

[smooth]

After starting bitmonerod.exe it synchronizes with the network for some time till it tells me that it is synchronized and I can start up simplewallet.exe

You can try deleting/moving your binary wallet file (default name wallet.bin) and just keep your keys file (wallet.bin.keys), and then let simplewallet rebuild the binary file. If you're moving a wallet file from 32-bit to 64-bit this can definitely be an issue, also moving from *nix to windows I think.

make some backups btw.

Thx, I already did. Anyway my problem still persists, any ideas how to fix it?

My guess is that it is still finding a bin file somewhere. Post the log file again from simplewallet (redacting private stuff is fine, only the messages are important).

[Spekulatius]

After starting bitmonerod.exe it synchronizes with the network for some time till it tells me that it is synchronized and I can start up simplewallet.exe

You can try deleting/moving your binary wallet file (default name wallet.bin) and just keep your keys file (wallet.bin.keys), and then let simplewallet rebuild the binary file. If you're moving a wallet file from 32-bit to 64-bit this can definitely be an issue, also moving from *nix to windows I think.

make some backups btw.

Thx, I already did. Anyway my problem still persists, any ideas how to fix it?

My guess is that it is still finding a bin file somewhere. Post the log file again from simplewallet (redacting private stuff is fine, only the messages are important).

Thats the latest one (I cut a lot of lines out where it only processes blocks -> [...]:

Code:

2014-Aug-31 21:11:28.188406 bitmonero wallet v0.8.8.2(0.1-g1b8a68f)
2014-Aug-31 21:11:29.567485 Loaded wallet keys file, with public address: XXXXXXxXwmDs3R6rGkRHFJmjtk78KH87LsJSanmnxDF1xkyxeH3MeJZhZNdzNNF4DgYV8aGZoFFqNSfqVmhuUHhGyvvxgK
2014-Aug-31 21:11:29.597487 Opened wallet: XXXXXXxXwmDs3R6rGkRHFJmjtk78KH87LsJSanmnxDF1xkyxeH3MeJZhZNdzNNF4DgYV8aGZoFFqNSfqVmhuUHhGyvvxgK
2014-Aug-31 21:11:29.612488 Starting refresh...
2014-Aug-31 21:11:29.657490 Block is already in blockchain: e7e865e736fad684a7d7f6cd5bef581bfe1050d6a533622c2431ec8e0d7f106e
2014-Aug-31 21:11:29.660491 Processed block: <946ec45ee7c878c63a7c8e8d4fff28fc7585d0ba70a6a06cca8a9fad9c0a937d>, height 197737, 0(0/0)ms
2014-Aug-31 21:11:29.736495 Processed block: <cfdd3ade82e54af89c7e191a87d1b88f82c250fb9b98ac795fd193c773259afe>, height 197738, 62(0/62)ms

[...]

2014-Aug-31 21:11:30.868560 Refresh done, blocks received: 110, balance: XXX, unlocked: XXX
2014-Aug-31 21:11:30.870560 Refresh done, blocks received: 110
2014-Aug-31 21:11:30.871560 balance: XXX, unlocked balance: XXX
2014-Aug-31 21:11:30.874560 **********************************************************************
Use "help" command to see the list of available commands.
**********************************************************************

[smooth]

I'm not quite following. What is the problem here. It looks like it synced up to me. Is it not synced?

[Spekulatius]

I'm not quite following. What is the problem here. It looks like it synced up to me. Is it not synced?

The problem is that simplewallet.exe shuts down the nanosecond it finishes syncing. Bitmonero.exe keeps running without complaint, but I cant access my wallet this way.

[smooth]

I'm not quite following. What is the problem here. It looks like it synced up to me. Is it not synced?

The problem is that simplewallet.exe shuts down the nanosecond it finishes syncing. Bitmonero.exe keeps running without complaint, but I cant access my wallet this way.

That's odd. Nothing in the log file would indicate a failure. Are you still using a script to start it? How about starting it directly, without the script?

[rikkejohn]

You need to run it from DOS, it works fine.

[DawnInTokyo]

where can I download the official wallet with graphics I mean not that console thing. It's very confusing for me on your website I beg your pardon. how to use?