Can we simply import wallets and .keys from the old Monero client into Hydrogen Helix?
yes i copy/pasted them in Hydrogen Helix folder and when open with simple wallet just type refresh command and that is it.
Thank you.
Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 714. (Read 4671660 times)
January 03, 2016, 11:11:17 AM
yes i copy/pasted them in Hydrogen Helix folder and when open with simple wallet just type refresh command and that is it.
Thank you.
January 03, 2016, 10:09:54 AM
Can we simply import wallets and .keys from the old Monero client into Hydrogen Helix?
yes i copy/pasted them in Hydrogen Helix folder and when open with simple wallet just type refresh command and that is it.
January 03, 2016, 08:38:09 AM
Can we simply import wallets and .keys from the old Monero client into Hydrogen Helix?
January 03, 2016, 07:37:38 AM
I have just re-synced from scratch the blockchain by new 0.9 release Win64 binaries. All things seem to be SUCCESS. Below I leave some number facts:
Total time to re-sync from scratch = 2h 25m
Maximum memory usage visible in standard Windows 7 task manager during re-sync = 60Mb
Overall Monero database files under c:\ProgramData\bitmonero = 7.6Gb
Simplewallet.exe have requested to import my wallet from old format - done instantly.
Note, 'refresh' command must be typed in simplewallet console to see up-to-date balance!
!!! MONERO DEVS CONGRATULATIONS !!!
Total time to re-sync from scratch = 2h 25m
Maximum memory usage visible in standard Windows 7 task manager during re-sync = 60Mb
Overall Monero database files under c:\ProgramData\bitmonero = 7.6Gb
Simplewallet.exe have requested to import my wallet from old format - done instantly.
Note, 'refresh' command must be typed in simplewallet console to see up-to-date balance!
!!! MONERO DEVS CONGRATULATIONS !!!
I agree, the DEVS KICK ASS.
I have also just synced the blockchain from scratch using ver0.9 binaries released for Win64. All seems to be a SUCCESS for me as well.
Total time to re-sync from scratch = ~50mins
Very fast! Unfortunately, it does not work happen as such in my PC (Windows 7 64bit). It took me 2 hour sync-ing 128k block (out of ~900k block)
Probably because you have an HDD, syncing is way faster with an SSD than an HDD.
January 03, 2016, 06:56:46 AM
thank you fluffy, deleting the .bin helped. balances are in sync again now
January 03, 2016, 06:11:28 AM
2016-Jan-02 20:05:06.652046 [RPC1]ERROR C:/msys64/DISTRIBUTION-BUILD/src/crypton
ote_core/miner.cpp:239 Starting miner but it's already started
ote_core/miner.cpp:239 Starting miner but it's already started
Isn't this clear?
Your daemon is already mining. The wallet has commands to start and stop mining but once you start, as long as the daemon is still running it will continue to mine even after the wallet exits.
No it wasn't clear to me because that message was immediately followed by:
2016-Jan-02 20:05:06.652046 [RPC1]Failed, mining not started
as well as a similar message from simplewallet.
Also I always stop_mining before exiting but after checking things out it seems this time I didn't and just exited. I had no idea you needed simple wallet to start and stop mining but not to continue to mine once started.
Signed, resident idiot
January 03, 2016, 05:48:45 AM
hi guys i have around 1k xmr that always stays locked and never gets unlocked.
i do not know if those 1000 are real or if they somehow magically summed up becasue i did send money to myself several times...
anyway, yesterday i tranfsered money to my cold wallet...later i realized it did not work, money was still here in my normal wallet..very strange, i rescant everything and now have this crazy behaviour. this event shoked me, if i wouldnt have used rescan_spent i wouldntn have noticed it was not send to my cold wallet. i hope this did not happen with my old hot wallet i deleted ..
dont want to open cold wallet to see whats up.
allready did rescan_spent + rescan_bc, without success, the 1k stays locked, also if i wait over night.
any ideas ? i know people had similar problems but they didn have a corrupted balance later no?
i do not know if those 1000 are real or if they somehow magically summed up becasue i did send money to myself several times...
anyway, yesterday i tranfsered money to my cold wallet...later i realized it did not work, money was still here in my normal wallet..very strange, i rescant everything and now have this crazy behaviour. this event shoked me, if i wouldnt have used rescan_spent i wouldntn have noticed it was not send to my cold wallet. i hope this did not happen with my old hot wallet i deleted ..
dont want to open cold wallet to see whats up.
allready did rescan_spent + rescan_bc, without success, the 1k stays locked, also if i wait over night.
any ideas ? i know people had similar problems but they didn have a corrupted balance later no?
Two things that occur to me:
1. Can you try restore from .keys file rather than rescan, just to eliminate potential rescan bugs? Just delete the .bin and reopen it.
2. When you transferred did you get a txid? If so, did you check if it hasn't been mined yet (on a block explorer)?
It sounds like you might be rescanning whilst a tx is not (yet) mined, but that's just a guess based on the info.
January 03, 2016, 05:17:15 AM
hi guys i have around 1k xmr that always stays locked and never gets unlocked.
i do not know if those 1000 are real or if they somehow magically summed up becasue i did send money to myself several times...
anyway, yesterday i tranfsered money to my cold wallet...later i realized it did not work, money was still here in my normal wallet..very strange, i rescant everything and now have this crazy behaviour. this event shoked me, if i wouldnt have used rescan_spent i wouldntn have noticed it was not send to my cold wallet. i hope this did not happen with my old hot wallet i deleted ..
dont want to open cold wallet to see whats up.
allready did rescan_spent + rescan_bc, without success, the 1k stays locked, also if i wait over night.
any ideas ? i know people had similar problems but they didn have a corrupted balance later no?
i do not know if those 1000 are real or if they somehow magically summed up becasue i did send money to myself several times...
anyway, yesterday i tranfsered money to my cold wallet...later i realized it did not work, money was still here in my normal wallet..very strange, i rescant everything and now have this crazy behaviour. this event shoked me, if i wouldnt have used rescan_spent i wouldntn have noticed it was not send to my cold wallet. i hope this did not happen with my old hot wallet i deleted ..
dont want to open cold wallet to see whats up.
allready did rescan_spent + rescan_bc, without success, the 1k stays locked, also if i wait over night.
any ideas ? i know people had similar problems but they didn have a corrupted balance later no?
January 03, 2016, 03:56:23 AM
I'm also getting this error on 0.9 running on Windows 10
Code:
2016-Jan-03 10:48:19.168135 [P2P9]WARNING: no two valid MoneroPulse DNS checkpoint records were received
January 03, 2016, 02:28:22 AM
I have just re-synced from scratch the blockchain by new 0.9 release Win64 binaries. All things seem to be SUCCESS. Below I leave some number facts:
Total time to re-sync from scratch = 2h 25m
Maximum memory usage visible in standard Windows 7 task manager during re-sync = 60Mb
Overall Monero database files under c:\ProgramData\bitmonero = 7.6Gb
Simplewallet.exe have requested to import my wallet from old format - done instantly.
Note, 'refresh' command must be typed in simplewallet console to see up-to-date balance!
!!! MONERO DEVS CONGRATULATIONS !!!
Total time to re-sync from scratch = 2h 25m
Maximum memory usage visible in standard Windows 7 task manager during re-sync = 60Mb
Overall Monero database files under c:\ProgramData\bitmonero = 7.6Gb
Simplewallet.exe have requested to import my wallet from old format - done instantly.
Note, 'refresh' command must be typed in simplewallet console to see up-to-date balance!
!!! MONERO DEVS CONGRATULATIONS !!!
I agree, the DEVS KICK ASS.
I have also just synced the blockchain from scratch using ver0.9 binaries released for Win64. All seems to be a SUCCESS for me as well.
Total time to re-sync from scratch = ~50mins
Very fast! Unfortunately, it does not work happen as such in my PC (Windows 7 64bit). It took me 2 hour sync-ing 128k block (out of ~900k block)
January 03, 2016, 01:17:51 AM
I'll focus on a side point, since I have no clue why the windows version would silently die:
That is odd. Can you ping checkpoints.moneropulse.co, checkpoints.moneropulse.se ?
If you have dig, what is the output of:
dig -t TXT checkpoints.moneropulse.co
dig -t TXT checkpoints.moneropulse.se
If you have another DNS tool to run on the same machine bitmonerod runs on, you can use it instead to query the TXT record for these two hosts.
2015-Dec-31 17:43:17.718750 WARNING: no two valid MoneroPulse DNS checkpoint records were received
That is odd. Can you ping checkpoints.moneropulse.co, checkpoints.moneropulse.se ?
If you have dig, what is the output of:
dig -t TXT checkpoints.moneropulse.co
dig -t TXT checkpoints.moneropulse.se
If you have another DNS tool to run on the same machine bitmonerod runs on, you can use it instead to query the TXT record for these two hosts.
I go the same error on version v0.9.0.0-release running on Ubuntu 14.04 and Trisquel 7 Here is the dig output:
Code:
$ dig -t TXT checkpoints.moneropulse.co
; <<>> DiG 9.9.5-3ubuntu0.6-Ubuntu <<>> -t TXT checkpoints.moneropulse.co
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21580
;; flags: qr rd ra; QUERY: 1, ANSWER: 9, AUTHORITY: 2, ADDITIONAL: 3
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;checkpoints.moneropulse.co. IN TXT
;; ANSWER SECTION:
checkpoints.moneropulse.co. 600 IN TXT "450000:4d098b511ca97723e81737c448343cfd4e6dadb3d8a0e757c6e4d595e6e48357"
checkpoints.moneropulse.co. 600 IN TXT "250000:f59d31839bd909ec8830b4f7f66ff213f0bd006334c8523daee452725e5c7a79"
checkpoints.moneropulse.co. 600 IN TXT "300000:0c1cd46df6ccff90ec4ab493281f2583c344cd62216c427628990fe9db1bb8b6"
checkpoints.moneropulse.co. 600 IN TXT "275000:c003a351a091d30c769edce5005d3fc4cfca95a841f7189584e2c3f93cc7281a"
checkpoints.moneropulse.co. 600 IN TXT "350000:74da79f6a136969abd6364bd3d37af273c408d6471e8ab598e80569b42415f86"
checkpoints.moneropulse.co. 600 IN TXT "325000:4260d56368267bc2a70dd58d73c5ecf23b4e4d96e63c29a868e4a679b0741c7f"
checkpoints.moneropulse.co. 600 IN TXT "400000:1b2b0e7a30e59691491529a3d506d1ba3d6052d0f6b52198b7330b28a6f1b6ac"
checkpoints.moneropulse.co. 600 IN TXT "233000:4f69bec2af6c0852412bdd10c19e6af10c8d738fe2618b5511a98efd03ab477e"
checkpoints.moneropulse.co. 600 IN TXT "375000:c80c23e387585e12ffb6649d678e9ba328181797b9583a6d8911b77e25375737"
;; AUTHORITY SECTION:
MONEROPULSE.co. 3600 IN NS TIMEWARP-AGAIN.MONEROPULSE.co.
MONEROPULSE.co. 3600 IN NS IS-IT-TRUE.MONEROPULSE.co.
;; ADDITIONAL SECTION:
IS-IT-TRUE.MONEROPULSE.co. 5866 IN A 216.69.185.52
TIMEWARP-AGAIN.MONEROPULSE.co. 5866 IN A 208.109.255.52
;; Query time: 390 msec
;; SERVER: 127.0.1.1#53(127.0.1.1)
;; WHEN: Sat Jan 02 22:05:17 PST 2016
;; MSG SIZE rcvd: 909
$ dig -t TXT checkpoints.moneropulse.se
; <<>> DiG 9.9.5-3ubuntu0.6-Ubuntu <<>> -t TXT checkpoints.moneropulse.se
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4548
;; flags: qr rd ra; QUERY: 1, ANSWER: 9, AUTHORITY: 2, ADDITIONAL: 3
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;checkpoints.moneropulse.se. IN TXT
;; ANSWER SECTION:
checkpoints.moneropulse.se. 600 IN TXT "275000:c003a351a091d30c769edce5005d3fc4cfca95a841f7189584e2c3f93cc7281a"
checkpoints.moneropulse.se. 600 IN TXT "375000:c80c23e387585e12ffb6649d678e9ba328181797b9583a6d8911b77e25375737"
checkpoints.moneropulse.se. 600 IN TXT "250000:f59d31839bd909ec8830b4f7f66ff213f0bd006334c8523daee452725e5c7a79"
checkpoints.moneropulse.se. 600 IN TXT "350000:74da79f6a136969abd6364bd3d37af273c408d6471e8ab598e80569b42415f86"
checkpoints.moneropulse.se. 600 IN TXT "233000:4f69bec2af6c0852412bdd10c19e6af10c8d738fe2618b5511a98efd03ab477e"
checkpoints.moneropulse.se. 600 IN TXT "325000:4260d56368267bc2a70dd58d73c5ecf23b4e4d96e63c29a868e4a679b0741c7f"
checkpoints.moneropulse.se. 600 IN TXT "300000:0c1cd46df6ccff90ec4ab493281f2583c344cd62216c427628990fe9db1bb8b6"
checkpoints.moneropulse.se. 600 IN TXT "450000:4d098b511ca97723e81737c448343cfd4e6dadb3d8a0e757c6e4d595e6e48357"
checkpoints.moneropulse.se. 600 IN TXT "400000:1b2b0e7a30e59691491529a3d506d1ba3d6052d0f6b52198b7330b28a6f1b6ac"
;; AUTHORITY SECTION:
moneropulse.se. 3599 IN NS is-it-true.moneropulse.se.
moneropulse.se. 3599 IN NS timewarp-again.moneropulse.se.
;; ADDITIONAL SECTION:
is-it-true.moneropulse.se. 74110 IN A 216.69.185.52
timewarp-again.moneropulse.se. 74110 IN A 208.109.255.52
;; Query time: 1107 msec
;; SERVER: 127.0.1.1#53(127.0.1.1)
;; WHEN: Sat Jan 02 22:06:32 PST 2016
;; MSG SIZE rcvd: 897
; <<>> DiG 9.9.5-3ubuntu0.6-Ubuntu <<>> -t TXT checkpoints.moneropulse.co
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21580
;; flags: qr rd ra; QUERY: 1, ANSWER: 9, AUTHORITY: 2, ADDITIONAL: 3
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;checkpoints.moneropulse.co. IN TXT
;; ANSWER SECTION:
checkpoints.moneropulse.co. 600 IN TXT "450000:4d098b511ca97723e81737c448343cfd4e6dadb3d8a0e757c6e4d595e6e48357"
checkpoints.moneropulse.co. 600 IN TXT "250000:f59d31839bd909ec8830b4f7f66ff213f0bd006334c8523daee452725e5c7a79"
checkpoints.moneropulse.co. 600 IN TXT "300000:0c1cd46df6ccff90ec4ab493281f2583c344cd62216c427628990fe9db1bb8b6"
checkpoints.moneropulse.co. 600 IN TXT "275000:c003a351a091d30c769edce5005d3fc4cfca95a841f7189584e2c3f93cc7281a"
checkpoints.moneropulse.co. 600 IN TXT "350000:74da79f6a136969abd6364bd3d37af273c408d6471e8ab598e80569b42415f86"
checkpoints.moneropulse.co. 600 IN TXT "325000:4260d56368267bc2a70dd58d73c5ecf23b4e4d96e63c29a868e4a679b0741c7f"
checkpoints.moneropulse.co. 600 IN TXT "400000:1b2b0e7a30e59691491529a3d506d1ba3d6052d0f6b52198b7330b28a6f1b6ac"
checkpoints.moneropulse.co. 600 IN TXT "233000:4f69bec2af6c0852412bdd10c19e6af10c8d738fe2618b5511a98efd03ab477e"
checkpoints.moneropulse.co. 600 IN TXT "375000:c80c23e387585e12ffb6649d678e9ba328181797b9583a6d8911b77e25375737"
;; AUTHORITY SECTION:
MONEROPULSE.co. 3600 IN NS TIMEWARP-AGAIN.MONEROPULSE.co.
MONEROPULSE.co. 3600 IN NS IS-IT-TRUE.MONEROPULSE.co.
;; ADDITIONAL SECTION:
IS-IT-TRUE.MONEROPULSE.co. 5866 IN A 216.69.185.52
TIMEWARP-AGAIN.MONEROPULSE.co. 5866 IN A 208.109.255.52
;; Query time: 390 msec
;; SERVER: 127.0.1.1#53(127.0.1.1)
;; WHEN: Sat Jan 02 22:05:17 PST 2016
;; MSG SIZE rcvd: 909
$ dig -t TXT checkpoints.moneropulse.se
; <<>> DiG 9.9.5-3ubuntu0.6-Ubuntu <<>> -t TXT checkpoints.moneropulse.se
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4548
;; flags: qr rd ra; QUERY: 1, ANSWER: 9, AUTHORITY: 2, ADDITIONAL: 3
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;checkpoints.moneropulse.se. IN TXT
;; ANSWER SECTION:
checkpoints.moneropulse.se. 600 IN TXT "275000:c003a351a091d30c769edce5005d3fc4cfca95a841f7189584e2c3f93cc7281a"
checkpoints.moneropulse.se. 600 IN TXT "375000:c80c23e387585e12ffb6649d678e9ba328181797b9583a6d8911b77e25375737"
checkpoints.moneropulse.se. 600 IN TXT "250000:f59d31839bd909ec8830b4f7f66ff213f0bd006334c8523daee452725e5c7a79"
checkpoints.moneropulse.se. 600 IN TXT "350000:74da79f6a136969abd6364bd3d37af273c408d6471e8ab598e80569b42415f86"
checkpoints.moneropulse.se. 600 IN TXT "233000:4f69bec2af6c0852412bdd10c19e6af10c8d738fe2618b5511a98efd03ab477e"
checkpoints.moneropulse.se. 600 IN TXT "325000:4260d56368267bc2a70dd58d73c5ecf23b4e4d96e63c29a868e4a679b0741c7f"
checkpoints.moneropulse.se. 600 IN TXT "300000:0c1cd46df6ccff90ec4ab493281f2583c344cd62216c427628990fe9db1bb8b6"
checkpoints.moneropulse.se. 600 IN TXT "450000:4d098b511ca97723e81737c448343cfd4e6dadb3d8a0e757c6e4d595e6e48357"
checkpoints.moneropulse.se. 600 IN TXT "400000:1b2b0e7a30e59691491529a3d506d1ba3d6052d0f6b52198b7330b28a6f1b6ac"
;; AUTHORITY SECTION:
moneropulse.se. 3599 IN NS is-it-true.moneropulse.se.
moneropulse.se. 3599 IN NS timewarp-again.moneropulse.se.
;; ADDITIONAL SECTION:
is-it-true.moneropulse.se. 74110 IN A 216.69.185.52
timewarp-again.moneropulse.se. 74110 IN A 208.109.255.52
;; Query time: 1107 msec
;; SERVER: 127.0.1.1#53(127.0.1.1)
;; WHEN: Sat Jan 02 22:06:32 PST 2016
;; MSG SIZE rcvd: 897
January 02, 2016, 11:35:12 PM
Worth another listen!
New Monero Mixxive: https://www.mixcloud.com/Vanderi/monero-mixxives-6-2015-hydrogen-helix-the-new-era/
Please give our friend the talented Vanderi some love with listens, favorites, shares and follows!
Please give our friend the talented Vanderi some love with listens, favorites, shares and follows!
January 02, 2016, 10:46:09 PM
So can I just copy over my old wallet file in Windows or do I have to recover my wallet?
January 02, 2016, 09:51:07 PM
*moneromooo has added the option to supply custom entropy instead of using the PRNG. enjoy!
Wow, such boss!
http://hackaday.com/2012/01/15/turn-your-camera-phone-into-a-geiger-counter/
https://bitcointalksearch.org/topic/m.10333851
January 02, 2016, 09:33:15 PM
2016-Jan-02 20:05:06.652046 [RPC1]ERROR C:/msys64/DISTRIBUTION-BUILD/src/crypton
ote_core/miner.cpp:239 Starting miner but it's already started
ote_core/miner.cpp:239 Starting miner but it's already started
Isn't this clear?
Your daemon is already mining. The wallet has commands to start and stop mining but once you start, as long as the daemon is still running it will continue to mine even after the wallet exits.
January 02, 2016, 08:17:25 PM
@saddam, yes I see that there is a setting for autorefresh which I guess is the default.
now I can't get simplewallet to start mining again. I am using just as before including --trusted-daemon
In simple wallet I get......
Error: mining has NOT been started: Failed, mining not started
In the daemon I get............
2016-Jan-02 20:05:06.652046 [RPC1]ERROR C:/msys64/DISTRIBUTION-BUILD/src/crypton
ote_core/miner.cpp:239 Starting miner but it's already started
2016-Jan-02 20:05:06.652046 [RPC1]Failed, mining not started
So I closed the wallet and reopened it = the same.
I closed the wallet and daemon and restarted and it's ok.
When exiting the daemon I had to hit enter twice, the same as the beta.
now I can't get simplewallet to start mining again. I am using just as before including --trusted-daemon
In simple wallet I get......
Error: mining has NOT been started: Failed, mining not started
In the daemon I get............
2016-Jan-02 20:05:06.652046 [RPC1]ERROR C:/msys64/DISTRIBUTION-BUILD/src/crypton
ote_core/miner.cpp:239 Starting miner but it's already started
2016-Jan-02 20:05:06.652046 [RPC1]Failed, mining not started
So I closed the wallet and reopened it = the same.
I closed the wallet and daemon and restarted and it's ok.
When exiting the daemon I had to hit enter twice, the same as the beta.
January 02, 2016, 07:50:36 PM
@nioc: I think it is constantly up to date if you are mining. Type bc_height and see if you're up to date.
Monero-nodejs Update:
https://github.com/PsychicCat/monero-nodejs
version 2.0.0
*callbacks have been removed in favor of a promise friendly format.
example:
Moneroaddress.org Update:
https://moneroaddress.org
*moneromooo has added the option to supply custom entropy instead of using the PRNG. enjoy!
Monero-nodejs Update:
https://github.com/PsychicCat/monero-nodejs
version 2.0.0
*callbacks have been removed in favor of a promise friendly format.
example:
Code:
Wallet.address().then(function(address){
console.log(address);
});
console.log(address);
});
Moneroaddress.org Update:
https://moneroaddress.org
*moneromooo has added the option to supply custom entropy instead of using the PRNG. enjoy!
January 02, 2016, 07:22:59 PM
downloaded and installed 0.9 64bit windows on an 8.1 machine, synced the daemon, recovered a wallet, refreshed the wallet and my balance is correct, started mining 3 hrs ago with that wallet, confirmed my HR was the same as before.
I just refreshed the wallet and the message I get is: Refresh done, blocks received: 0
I just refreshed the wallet and the message I get is: Refresh done, blocks received: 0
January 02, 2016, 06:34:14 PM
I have just re-synced from scratch the blockchain by new 0.9 release Win64 binaries. All things seem to be SUCCESS. Below I leave some number facts:
Total time to re-sync from scratch = 2h 25m
Maximum memory usage visible in standard Windows 7 task manager during re-sync = 60Mb
Overall Monero database files under c:\ProgramData\bitmonero = 7.6Gb
Simplewallet.exe have requested to import my wallet from old format - done instantly.
Note, 'refresh' command must be typed in simplewallet console to see up-to-date balance!
!!! MONERO DEVS CONGRATULATIONS !!!
Total time to re-sync from scratch = 2h 25m
Maximum memory usage visible in standard Windows 7 task manager during re-sync = 60Mb
Overall Monero database files under c:\ProgramData\bitmonero = 7.6Gb
Simplewallet.exe have requested to import my wallet from old format - done instantly.
Note, 'refresh' command must be typed in simplewallet console to see up-to-date balance!
!!! MONERO DEVS CONGRATULATIONS !!!
I agree, the DEVS KICK ASS.
I have also just synced the blockchain from scratch using ver0.9 binaries released for Win64. All seems to be a SUCCESS for me as well.
Total time to re-sync from scratch = ~50mins
January 02, 2016, 03:39:24 PM
I have just re-synced from scratch the blockchain by new 0.9 release Win64 binaries. All things seem to be SUCCESS. Below I leave some number facts:
Total time to re-sync from scratch = 2h 25m
Maximum memory usage visible in standard Windows 7 task manager during re-sync = 60Mb
Overall Monero database files under c:\ProgramData\bitmonero = 7.6Gb
Simplewallet.exe have requested to import my wallet from old format - done instantly.
Note, 'refresh' command must be typed in simplewallet console to see up-to-date balance!
!!! MONERO DEVS CONGRATULATIONS !!!
Total time to re-sync from scratch = 2h 25m
Maximum memory usage visible in standard Windows 7 task manager during re-sync = 60Mb
Overall Monero database files under c:\ProgramData\bitmonero = 7.6Gb
Simplewallet.exe have requested to import my wallet from old format - done instantly.
Note, 'refresh' command must be typed in simplewallet console to see up-to-date balance!
!!! MONERO DEVS CONGRATULATIONS !!!
Jump to: