(red letters)
Help / Hint?
Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 1715. (Read 4670614 times)
Ok, i got the error here, which (when happens), blockchain after that happens becomes unusable:
(red letters)
Help / Hint?
(red letters)
Help / Hint?
This thread is my last hope, as all my attemps to install wallet and miner in lubuntu 14.04 failed.
This are the errors I got:
This are the errors I got:
Quote
/home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp: In function ‘void cryptonote::mul(uint64_t, uint64_t, uint64_t&, uint64_t&)’:
/home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp:33:22: error: expected unqualified-id before ‘__int128’
typedef unsigned __int128 uint128_t;
^
/home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp:34:5: error: ‘uint128_t’ was not declared in this scope
uint128_t res = (uint128_t) a * (uint128_t) b;
^
/home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp:35:22: error: ‘res’ was not declared in this scope
low = (uint64_t) res;
^
make[3]: *** [src/CMakeFiles/cryptonote_core.dir/cryptonote_core/difficulty.cpp.o] Fehler 1
make[3]: Verlasse Verzeichnis '/home/user/bitmonero/bitmonero/build/release'
make[2]: *** [src/CMakeFiles/cryptonote_core.dir/all] Fehler 2
make[2]: Verlasse Verzeichnis '/home/user/bitmonero/bitmonero/build/release'
make[1]: *** [all] Fehler 2
make[1]: Verlasse Verzeichnis '/home/user/bitmonero/bitmonero/build/release'
make: *** [build-release] Fehler 2
I would be very glad to find help here, but have to say that my knowledge in Linux is pretty limited./home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp:33:22: error: expected unqualified-id before ‘__int128’
typedef unsigned __int128 uint128_t;
^
/home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp:34:5: error: ‘uint128_t’ was not declared in this scope
uint128_t res = (uint128_t) a * (uint128_t) b;
^
/home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp:35:22: error: ‘res’ was not declared in this scope
low = (uint64_t) res;
^
make[3]: *** [src/CMakeFiles/cryptonote_core.dir/cryptonote_core/difficulty.cpp.o] Fehler 1
make[3]: Verlasse Verzeichnis '/home/user/bitmonero/bitmonero/build/release'
make[2]: *** [src/CMakeFiles/cryptonote_core.dir/all] Fehler 2
make[2]: Verlasse Verzeichnis '/home/user/bitmonero/bitmonero/build/release'
make[1]: *** [all] Fehler 2
make[1]: Verlasse Verzeichnis '/home/user/bitmonero/bitmonero/build/release'
make: *** [build-release] Fehler 2
It shouldnt be too hard on Ubuntu 14.04, have you been following the instructions or using the install script from http://monero.cc/getting-started/index.html ?
I havent bothered to put the foreign bits through translator, but at a guess you might just need to try "sudo make"
Of course, I have kept to the instructions and various obstacles - such as the right boost version, for example - already circumnavigated. Also, "sudo" is quite familiar to me, otherwise the make command had not been executed.
But with the error messages shown above, I can not do anything. I do not expect complete solution, a hint in which direction I should look for, would help me.
Code:
cd ~ && rm -f install_monero.sh && wget https://monero.cc/downloads/install_monero.sh && bash install_monero.sh
It will install all the pre-requirements and then it'll compile it for you. hello i have tried this method and it says my password is still invalid... i dont understand why as its the same password, is there another method... or do you think i will have more luck with the new gui wallet?
thanks for you help
it kinda seems like you just forgot your password. did you try 'x' for password? or nothing? capslock?
dude theres no way i could have forgotten, i had it written on two docs, ive gone through all the previous versions of the txt doc i put it on, and the password is correct, so i dont know why i cant get into my wallet
i took extra precautions with xmr for the fact that i didnt want to lose money and its a great coin... i dont understand why it worked before and not now if its literally exactly same password
This thread is my last hope, as all my attemps to install wallet and miner in lubuntu 14.04 failed.
This are the errors I got:
This are the errors I got:
Quote
/home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp: In function ‘void cryptonote::mul(uint64_t, uint64_t, uint64_t&, uint64_t&)’:
/home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp:33:22: error: expected unqualified-id before ‘__int128’
typedef unsigned __int128 uint128_t;
^
/home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp:34:5: error: ‘uint128_t’ was not declared in this scope
uint128_t res = (uint128_t) a * (uint128_t) b;
^
/home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp:35:22: error: ‘res’ was not declared in this scope
low = (uint64_t) res;
^
make[3]: *** [src/CMakeFiles/cryptonote_core.dir/cryptonote_core/difficulty.cpp.o] Fehler 1
make[3]: Verlasse Verzeichnis '/home/user/bitmonero/bitmonero/build/release'
make[2]: *** [src/CMakeFiles/cryptonote_core.dir/all] Fehler 2
make[2]: Verlasse Verzeichnis '/home/user/bitmonero/bitmonero/build/release'
make[1]: *** [all] Fehler 2
make[1]: Verlasse Verzeichnis '/home/user/bitmonero/bitmonero/build/release'
make: *** [build-release] Fehler 2
I would be very glad to find help here, but have to say that my knowledge in Linux is pretty limited./home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp:33:22: error: expected unqualified-id before ‘__int128’
typedef unsigned __int128 uint128_t;
^
/home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp:34:5: error: ‘uint128_t’ was not declared in this scope
uint128_t res = (uint128_t) a * (uint128_t) b;
^
/home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp:35:22: error: ‘res’ was not declared in this scope
low = (uint64_t) res;
^
make[3]: *** [src/CMakeFiles/cryptonote_core.dir/cryptonote_core/difficulty.cpp.o] Fehler 1
make[3]: Verlasse Verzeichnis '/home/user/bitmonero/bitmonero/build/release'
make[2]: *** [src/CMakeFiles/cryptonote_core.dir/all] Fehler 2
make[2]: Verlasse Verzeichnis '/home/user/bitmonero/bitmonero/build/release'
make[1]: *** [all] Fehler 2
make[1]: Verlasse Verzeichnis '/home/user/bitmonero/bitmonero/build/release'
make: *** [build-release] Fehler 2
It shouldnt be too hard on Ubuntu 14.04, have you been following the instructions or using the install script from http://monero.cc/getting-started/index.html ?
I havent bothered to put the foreign bits through translator, but at a guess you might just need to try "sudo make"
Of course, I have kept to the instructions and various obstacles - such as the right boost version, for example - already circumnavigated. Also, "sudo" is quite familiar to me, otherwise the make command had not been executed.
But with the error messages shown above, I can not do anything. I do not expect complete solution, a hint in which direction I should look for, would help me.
hello i have tried this method and it says my password is still invalid... i dont understand why as its the same password, is there another method... or do you think i will have more luck with the new gui wallet?
thanks for you help
it kinda seems like you just forgot your password. did you try 'x' for password? or nothing? capslock?
so i delete the address.txt file and wallet.bin?? and save or keep the .keys file... should i place the .keys file in app roaming?? or in same folder as simplewallet....
i also created it in windows ... so you had similar issue with invalid password??
thanks a bunch for you assitance i appreciate it
i also created it in windows ... so you had similar issue with invalid password??
thanks a bunch for you assitance i appreciate it
Download the latest binaries, extract to a new folder, place the [wallet.bin].keys file in there, start simple wallet, load your wallet name (without the .keys extension), enter password, and it will rebuild the wallet file
hello i have tried this method and it says my password is still invalid... i dont understand why as its the same password, is there another method... or do you think i will have more luck with the new gui wallet?
thanks for you help
I don't know if it have been asked but what is the formula for calculating fees ?
Flat 0.005 fee + small quantities to burn off dust in you use dust inputsOh ok thanks.
Will it increase or decrease in a near future ?
I'd hope with the flat fee of 0.005 (which was just increased from 0.000001 I think a few weeks ago) we'd be ok for a good long while.
1000 blocks downloaded, 103k to go 
If this does not get the thing to work, I DON'T care if it would be even a golden coin.
Dev team should think about it BEFORE they even started publishing anything.
And if dev team fails - success is equal to zero.
If this does not get the thing to work, I DON'T care if it would be even a golden coin.
Dev team should think about it BEFORE they even started publishing anything.
And if dev team fails - success is equal to zero.
Failure to cross-platform serialize was an internal failure from the ByteCoin code, hence we updated our codebase to include mnemonic seeds to generate keys that function easily across platforms.
Unfortunately, we inherited a lot of bad code, but we're doing our best to fix it now.
Can see that.
I've been downloading a blockchain from 0.
It took me about 12 hours to finish it.
After I did, I started my wallet and all was fine.
BUT, now, again, the same problem is present.
I have backup of blockchain I've downloaded(updated) and I tried to replace the existing one, but nothing change that state.
Can anyone explain what the real problem could be?
If you type set_log 2 or set_log 3 into the daemon command window you can increase the logging messages it displays, that might show what is causing the problem.
Yes, I tried that, and here are (is) result(s) from the .log file:
Code:
2014-Jun-29 20:59:26.112671 [P2P1][94.244.155.113:18080 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-Jun-29 20:59:26.114625 [P2P4][94.244.155.113:18080 OUT]CONNECTION HANDSHAKED OK.
2014-Jun-29 20:59:26.117554 [P2P4]Random connection index=6(x=14, max_index=20)
2014-Jun-29 20:59:26.119507 [P2P4]Selected peer: 18170737938260944790 178.41.54.60:18080[white=0] last_seen: d0.h0.m7.s16
2014-Jun-29 20:59:26.124390 [P2P4]Connecting to 178.41.54.60:18080(white=0, last_seen: d0.h0.m7.s16)...
2014-Jun-29 20:59:26.889039 [P2P6][94.244.155.113:18080 OUT]NOTIFY_REQUEST_CHAIN: m_block_ids.size()=27
2014-Jun-29 20:59:27.242554 [P2P6][94.244.155.113:18080 OUT]-->>NOTIFY_RESPONSE_CHAIN_ENTRY: m_start_height=100914, m_total_height=106847, m_block_ids.size()=5933
2014-Jun-29 20:59:27.247437 [P2P6][94.244.155.113:18080 OUT] post struct cryptonote::NOTIFY_RESPONSE_CHAIN_ENTRY -->
2014-Jun-29 20:59:31.127320 [P2P4]Failed to connect to 178.41.54.60:18080, because of timeout (5000)
2014-Jun-29 20:59:31.140992 [P2P4][sock 4294967295] Socket destroyed without shutdown.
2014-Jun-29 20:59:31.152710 [P2P4][sock 4294967295] Socket destroyed
2014-Jun-29 20:59:31.162476 [P2P4][0.0.0.0:0 OUT]Connect failed to 178.41.54.60:18080
2014-Jun-29 20:59:31.170289 [P2P4]Random connection index=1(x=8, max_index=20)
2014-Jun-29 20:59:31.176148 [P2P4]Selected peer: 9506295159526218340 46.229.50.42:18080[white=0] last_seen: d0.h0.m0.s21
2014-Jun-29 20:59:31.186890 [P2P4]Connecting to 46.229.50.42:18080(white=0, last_seen: d0.h0.m0.s21)...
2014-Jun-29 20:59:31.294312 [P2P4]Connected success to 46.229.50.42:18080
2014-Jun-29 20:59:31.305054 [P2P4][sock 872] new connection from 46.229.50.42:18080 OUT to 192.168.0.101:51883, total sockets objects 11
2014-Jun-29 20:59:31.323609 [P2P4][46.229.50.42:18080 9d3cf0d6-659e-41d7-aedb-6eaaab3b4324 OUT] NEW CONNECTION
2014-Jun-29 20:59:31.848023 [P2P2][46.229.50.42:18080 OUT]REMOTE PEERLIST: TIME_DELTA: 4, remote peerlist size=252
2014-Jun-29 20:59:31.861695 [P2P2][46.229.50.42:18080 OUT]REMOTE PEERLIST: 35627ce00922a0aa 97.94.210.82:18080 last_seen: d0.h0.m0.s0
2014-Jun-29 20:59:26.114625 [P2P4][94.244.155.113:18080 OUT]CONNECTION HANDSHAKED OK.
2014-Jun-29 20:59:26.117554 [P2P4]Random connection index=6(x=14, max_index=20)
2014-Jun-29 20:59:26.119507 [P2P4]Selected peer: 18170737938260944790 178.41.54.60:18080[white=0] last_seen: d0.h0.m7.s16
2014-Jun-29 20:59:26.124390 [P2P4]Connecting to 178.41.54.60:18080(white=0, last_seen: d0.h0.m7.s16)...
2014-Jun-29 20:59:26.889039 [P2P6][94.244.155.113:18080 OUT]NOTIFY_REQUEST_CHAIN: m_block_ids.size()=27
2014-Jun-29 20:59:27.242554 [P2P6][94.244.155.113:18080 OUT]-->>NOTIFY_RESPONSE_CHAIN_ENTRY: m_start_height=100914, m_total_height=106847, m_block_ids.size()=5933
2014-Jun-29 20:59:27.247437 [P2P6][94.244.155.113:18080 OUT] post struct cryptonote::NOTIFY_RESPONSE_CHAIN_ENTRY -->
2014-Jun-29 20:59:31.127320 [P2P4]Failed to connect to 178.41.54.60:18080, because of timeout (5000)
2014-Jun-29 20:59:31.140992 [P2P4][sock 4294967295] Socket destroyed without shutdown.
2014-Jun-29 20:59:31.152710 [P2P4][sock 4294967295] Socket destroyed
2014-Jun-29 20:59:31.162476 [P2P4][0.0.0.0:0 OUT]Connect failed to 178.41.54.60:18080
2014-Jun-29 20:59:31.170289 [P2P4]Random connection index=1(x=8, max_index=20)
2014-Jun-29 20:59:31.176148 [P2P4]Selected peer: 9506295159526218340 46.229.50.42:18080[white=0] last_seen: d0.h0.m0.s21
2014-Jun-29 20:59:31.186890 [P2P4]Connecting to 46.229.50.42:18080(white=0, last_seen: d0.h0.m0.s21)...
2014-Jun-29 20:59:31.294312 [P2P4]Connected success to 46.229.50.42:18080
2014-Jun-29 20:59:31.305054 [P2P4][sock 872] new connection from 46.229.50.42:18080 OUT to 192.168.0.101:51883, total sockets objects 11
2014-Jun-29 20:59:31.323609 [P2P4][46.229.50.42:18080 9d3cf0d6-659e-41d7-aedb-6eaaab3b4324 OUT] NEW CONNECTION
2014-Jun-29 20:59:31.848023 [P2P2][46.229.50.42:18080 OUT]REMOTE PEERLIST: TIME_DELTA: 4, remote peerlist size=252
2014-Jun-29 20:59:31.861695 [P2P2][46.229.50.42:18080 OUT]REMOTE PEERLIST: 35627ce00922a0aa 97.94.210.82:18080 last_seen: d0.h0.m0.s0
Code:
2014-Jun-29 20:59:32.791382 [P2P2][46.229.50.42:18080 OUT]Sync data returned unknown top block: 106847 -> 107148 [301 blocks (0 days) behind]
SYNCHRONIZATION started
2014-Jun-29 20:59:32.802125 [P2P2]Remote top block height: 107148, id: <7a32a4d3735f0cd3be23cad8a3d80b8669550c2a2f9d9baa1f05292cfc3ca1e2>
2014-Jun-29 20:59:32.810914 [P2P2][46.229.50.42:18080 OUT]requesting callback
2014-Jun-29 20:59:32.816773 [P2P2][46.229.50.42:18080 OUT] request_callback
2014-Jun-29 20:59:32.821656 [P2P2][46.229.50.42:18080 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-Jun-29 20:59:32.828492 [P2P4][46.229.50.42:18080 OUT]CONNECTION HANDSHAKED OK.
2014-Jun-29 20:59:32.834351 [P2P4]Random connection index=17(x=19, max_index=20)
2014-Jun-29 20:59:32.839234 [P2P4]Selected peer: 7870288044270691678 188.239.94.255:18080[white=0] last_seen: d0.h0.m30.s43
2014-Jun-29 20:59:32.848023 [P2P4]Connecting to 188.239.94.255:18080(white=0, last_seen: d0.h0.m30.s43)...
2014-Jun-29 20:59:32.828492 [P2P8][46.229.50.42:18080 OUT] fired_callback
2014-Jun-29 20:59:32.860718 [P2P8][46.229.50.42:18080 OUT]callback fired
2014-Jun-29 20:59:32.866578 [P2P8][46.229.50.42:18080 OUT]-->>NOTIFY_REQUEST_CHAIN: m_block_ids.size()=27
2014-Jun-29 20:59:32.874390 [P2P8][46.229.50.42:18080 OUT] post struct cryptonote::NOTIFY_REQUEST_CHAIN -->
2014-Jun-29 20:59:33.444703 [P2P8][46.229.50.42:18080 OUT]NOTIFY_RESPONSE_CHAIN_ENTRY: m_block_ids.size()=302, m_start_height=106846, m_total_height=107148
2014-Jun-29 20:59:33.468140 [P2P8][46.229.50.42:18080 OUT]-->>NOTIFY_REQUEST_GET_OBJECTS: blocks.size()=200, txs.size()=0
2014-Jun-29 20:59:33.479859 [P2P8][46.229.50.42:18080 OUT] post struct cryptonote::NOTIFY_REQUEST_GET_OBJECTS -->
2014-Jun-29 20:59:34.936890 [P2P9][1.57.95.76:18080 OUT]NOTIFY_RESPONSE_GET_OBJECTS
2014-Jun-29 20:59:34.969117 [P2P9]tx <8eede40872a1885835eb8d87dcead63676462f1fa70f9e579efe1073d7949aec> already have transaction in blockchain
2014-Jun-29 20:59:34.981812 [P2P9]txalready have transaction in tx_pool
2014-Jun-29 20:59:34.991578 [P2P9]txalready have transaction in tx_pool
2014-Jun-29 20:59:35.089234 [P2P9]tx with id: <793bde1b414a7c8b04c696fba8b8b980cc569891a61d86bd36296707654bd73f> in block id: <525e0e014351ff15b2d199e8f9ed42557a00785bd74816ed0139aff7d0530853> already in blockchain
2014-Jun-29 20:59:35.100953 [P2P9]Block with id: <525e0e014351ff15b2d199e8f9ed42557a00785bd74816ed0139aff7d0530853> failed to add transaction to blockchain storage
2014-Jun-29 20:59:35.110718 [P2P9][1.57.95.76:18080 OUT]Block verification failed, dropping connection
2014-Jun-29 20:59:35.117554 [P2P5][sock 924] Some not success at read: A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call:10058
2014-Jun-29 20:59:35.129273 [P2P5][sock 924] Some problems at read: A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call:10058
2014-Jun-29 20:59:35.140015 [P2P5][sock 924] Socket destroyed
2014-Jun-29 20:59:35.143921 [P2P5][1.57.95.76:18080 d2fb375f-38b5-4640-8ff0-c31e6e1eead5 OUT] CLOSE CONNECTION
SYNCHRONIZATION started
2014-Jun-29 20:59:32.802125 [P2P2]Remote top block height: 107148, id: <7a32a4d3735f0cd3be23cad8a3d80b8669550c2a2f9d9baa1f05292cfc3ca1e2>
2014-Jun-29 20:59:32.810914 [P2P2][46.229.50.42:18080 OUT]requesting callback
2014-Jun-29 20:59:32.816773 [P2P2][46.229.50.42:18080 OUT] request_callback
2014-Jun-29 20:59:32.821656 [P2P2][46.229.50.42:18080 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-Jun-29 20:59:32.828492 [P2P4][46.229.50.42:18080 OUT]CONNECTION HANDSHAKED OK.
2014-Jun-29 20:59:32.834351 [P2P4]Random connection index=17(x=19, max_index=20)
2014-Jun-29 20:59:32.839234 [P2P4]Selected peer: 7870288044270691678 188.239.94.255:18080[white=0] last_seen: d0.h0.m30.s43
2014-Jun-29 20:59:32.848023 [P2P4]Connecting to 188.239.94.255:18080(white=0, last_seen: d0.h0.m30.s43)...
2014-Jun-29 20:59:32.828492 [P2P8][46.229.50.42:18080 OUT] fired_callback
2014-Jun-29 20:59:32.860718 [P2P8][46.229.50.42:18080 OUT]callback fired
2014-Jun-29 20:59:32.866578 [P2P8][46.229.50.42:18080 OUT]-->>NOTIFY_REQUEST_CHAIN: m_block_ids.size()=27
2014-Jun-29 20:59:32.874390 [P2P8][46.229.50.42:18080 OUT] post struct cryptonote::NOTIFY_REQUEST_CHAIN -->
2014-Jun-29 20:59:33.444703 [P2P8][46.229.50.42:18080 OUT]NOTIFY_RESPONSE_CHAIN_ENTRY: m_block_ids.size()=302, m_start_height=106846, m_total_height=107148
2014-Jun-29 20:59:33.468140 [P2P8][46.229.50.42:18080 OUT]-->>NOTIFY_REQUEST_GET_OBJECTS: blocks.size()=200, txs.size()=0
2014-Jun-29 20:59:33.479859 [P2P8][46.229.50.42:18080 OUT] post struct cryptonote::NOTIFY_REQUEST_GET_OBJECTS -->
2014-Jun-29 20:59:34.936890 [P2P9][1.57.95.76:18080 OUT]NOTIFY_RESPONSE_GET_OBJECTS
2014-Jun-29 20:59:34.969117 [P2P9]tx <8eede40872a1885835eb8d87dcead63676462f1fa70f9e579efe1073d7949aec> already have transaction in blockchain
2014-Jun-29 20:59:34.981812 [P2P9]tx
2014-Jun-29 20:59:34.991578 [P2P9]tx
2014-Jun-29 20:59:35.089234 [P2P9]tx with id: <793bde1b414a7c8b04c696fba8b8b980cc569891a61d86bd36296707654bd73f> in block id: <525e0e014351ff15b2d199e8f9ed42557a00785bd74816ed0139aff7d0530853> already in blockchain
2014-Jun-29 20:59:35.100953 [P2P9]Block with id: <525e0e014351ff15b2d199e8f9ed42557a00785bd74816ed0139aff7d0530853> failed to add transaction to blockchain storage
2014-Jun-29 20:59:35.110718 [P2P9][1.57.95.76:18080 OUT]Block verification failed, dropping connection
2014-Jun-29 20:59:35.117554 [P2P5][sock 924] Some not success at read: A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call:10058
2014-Jun-29 20:59:35.129273 [P2P5][sock 924] Some problems at read: A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call:10058
2014-Jun-29 20:59:35.140015 [P2P5][sock 924] Socket destroyed
2014-Jun-29 20:59:35.143921 [P2P5][1.57.95.76:18080 d2fb375f-38b5-4640-8ff0-c31e6e1eead5 OUT] CLOSE CONNECTION
I don't know if it have been asked but what is the formula for calculating fees ?
Flat 0.005 fee + small quantities to burn off dust in you use dust inputsOh ok thanks.
Will it increase or decrease in a near future ?
Have you deleted your p2pstate.bin and poolstate.bin? They will be found with you blockchain.bin file and will be recreated upon re-opening the wallet/daemon. Also, are you using the latest daemon in the OP?
I'm running v0.8.8.1.
And, yes, I deleted that 2 files (stored in \AppData\Roaming\bitmonero) and the problem is still present. Not moving from block 105314.
Is it me only, or anyone else have the same problem?
Started my daemon today and have the same problem ... stuck at block 100228. Nothing happens. Also no error messages.
A network problem or something ?
If you type set_log 2 or set_log 3 into the daemon command window you can increase the logging messages it displays, that might show what is causing the problem.
I deleted p2pstate and poolstate, started the deamon again with set_log command and I get lot of 'socket destroyed (whitout shutdown)' messages and in green 'connection handshake ok and closed' messages.
Don't know what to do ?
EDIT : problem solved. Restarted my router and now its syncing again.
we just need to have some of the other components integrated first eg database.
Thank you for working on this. I'd guess the database may be the most important step at the moment.
By the way, I can confirm the fix for the deterministic seed/date restore bug is good. Tested on 64bit Arch Linux.
Cool, thanks!
I don't know if it have been asked but what is the formula for calculating fees ?
Flat 0.005 fee + small quantities to burn off dust in you use dust inputs
I have been using the command line simplewallet for a couple weeks and I really love the simplicity and ease of use. It would be nice to have the following options if possible.
-Sanity check to confirm transfer of funds. Something like "You are about to send 10 XMR with a mixin factor of 3 to with payment ID. Are you sure? [y/n]". Right now it seems too easy for a user to make a careless mistake.
-Some way to view a history of outgoing transfers.
Thank you for your great work so far I am excited about the future of Monero.
-Sanity check to confirm transfer of funds. Something like "You are about to send 10 XMR with a mixin factor of 3 to with payment ID
-Some way to view a history of outgoing transfers.
Thank you for your great work so far I am excited about the future of Monero.
Have you deleted your p2pstate.bin and poolstate.bin? They will be found with you blockchain.bin file and will be recreated upon re-opening the wallet/daemon. Also, are you using the latest daemon in the OP?
I'm running v0.8.8.1.
And, yes, I deleted that 2 files (stored in \AppData\Roaming\bitmonero) and the problem is still present. Not moving from block 105314.
Is it me only, or anyone else have the same problem?
Started my daemon today and have the same problem ... stuck at block 100228. Nothing happens. Also no error messages.
A network problem or something ?
If you type set_log 2 or set_log 3 into the daemon command window you can increase the logging messages it displays, that might show what is causing the problem.
Have you deleted your p2pstate.bin and poolstate.bin? They will be found with you blockchain.bin file and will be recreated upon re-opening the wallet/daemon. Also, are you using the latest daemon in the OP?
I'm running v0.8.8.1.
And, yes, I deleted that 2 files (stored in \AppData\Roaming\bitmonero) and the problem is still present. Not moving from block 105314.
Is it me only, or anyone else have the same problem?
Started my daemon today and have the same problem ... stuck at block 100228. Nothing happens. Also no error messages.
A network problem or something ?
1 Monero to 1 million dollars in 10 years 
This is what I refer to as the brass ring. The developed economies all have far more debt than they can support. Negative interest rates fix this, but are not sustainable because the major stakeholders in the political economy are the debt holders. The end-game for debt-based currency is unstable. Innovation will revolutionize the system, inevitably. Digitization and globalization of currency is inevitable, because of the efficiencies offered. Any system which is not digital and global, rent-free, and instantaneous will fail to compete with a system which is. The leading candidates for transparent and private liquidity, respectively, are BTC and XMR. Which of those two markets is larger, I dare not speculate. The maximum entropy assumption is that they are equal. Since XMR asymptotic emission is less than BTC asymptotic emission, the rational best effort estimate is that 1 XMR > 1 BTC at some point in the future. To denominate all transactions, the million dollar (USD 2014) XMR is a necessity, in this least-assumption scenario.
10 years is a reasonable estimate of the time frame. The U.S. demographic cycle troughs in 2024. Baby boomers sell their real estate, their stocks, their bonds to fund retirement. The effect is compounded by a lack of buyers in the X,Y,millennial generations, due to cultural changes, and especially declining household formation rates. The result is price deflation in savings assets, declining rentier incomes. This creates a peak of destabilizing pressure on the debt-based money system, and is the most likely time for it to collapse.
Unless you see these points, you may think the slogan-like trite simplicity of 1 Monero to 1 million dollars in 10 years discredits the idea. To me, it seems almost inevitable. The future is ours to lose. Do not lose it.
OK my golden quotes hours are past me as well it seems some of the $.05 words you have used here. Can you start a discussion thread around this topic without any affinity for particular p2p systems. I very much wonder like to participate/follow that. Cheers
1 Monero to 1 million dollars in 10 years
This is what I refer to as the brass ring. The developed economies all have far more debt than they can support. Negative interest rates fix this, but are not sustainable because the major stakeholders in the political economy are the debt holders. The end-game for debt-based currency is unstable. Innovation will revolutionize the system, inevitably. Digitization and globalization of currency is inevitable, because of the efficiencies offered. Any system which is not digital and global, rent-free, and instantaneous will fail to compete with a system which is. The leading candidates for transparent and private liquidity, respectively, are BTC and XMR. Which of those two markets is larger, I dare not speculate. The maximum entropy assumption is that they are equal. Since XMR asymptotic emission is less than BTC asymptotic emission, the rational best effort estimate is that 1 XMR > 1 BTC at some point in the future. To denominate all transactions, the million dollar (USD 2014) XMR is a necessity, in this least-assumption scenario.
10 years is a reasonable estimate of the time frame. The U.S. demographic cycle troughs in 2024. Baby boomers sell their real estate, their stocks, their bonds to fund retirement. The effect is compounded by a lack of buyers in the X,Y,millennial generations, due to cultural changes, and especially declining household formation rates. The result is price deflation in savings assets, declining rentier incomes. This creates a peak of destabilizing pressure on the debt-based money system, and is the most likely time for it to collapse.
Unless you see these points, you may think the slogan-like trite simplicity of 1 Monero to 1 million dollars in 10 years discredits the idea. To me, it seems almost inevitable. The future is ours to lose. Do not lose it.
I don't know if it have been asked but what is the formula for calculating fees ?
fucking github won't let you search code on a fork, but here are some starting points from bytecoin's code:
https://github.com/amjuarez/bytecoin/search?q=fee&ref=cmdform&type=Code
1 Monero to 1 million dollars in 10 years
Hi guys, need to test my XMR wallet. Please send some to:
49Tk6cTxcLw3wDh1wC1XamYHgZvWHaCXyjBe2NDHZgxhdUubYcVsroTZEgF4HMgdWbVKbNzcnH5PHPV XFjGANDB3T98KurA
I install the wallet and miner and the computers that was on were hit with a reboot. How do I open up the wallet to check what XMR if any has been deposited by my i5 mining the last few days?49Tk6cTxcLw3wDh1wC1XamYHgZvWHaCXyjBe2NDHZgxhdUubYcVsroTZEgF4HMgdWbVKbNzcnH5PHPV XFjGANDB3T98KurA
I advise you to take a look as this monero wallet tutorial if you are on windows
https://monerotalk.org/t/bounty-create-a-useful-tutorial-on-how-to-setup-monero/13/8
cheers
Thanks I will check it out.. This coin is such a breath of fresh air
Jump to: