Bitcoin Forum
June 23, 2024, 08:33:22 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 [39] 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 ... 181 »
761  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [XMR] Monero - A secure, private, untraceable cryptocurrency on: May 20, 2017, 09:09:49 AM
Please vote for Monero here:

https://twitter.com/bobbyclee/status/865851769116475392
762  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [XMR] Monero - A secure, private, untraceable cryptocurrency on: May 18, 2017, 07:50:10 PM
Quote from: LawBC on May 18, 2017, 06:27:45 PM
Some modest advice

- New website. You guys should be now able to hire the best web designer out there.

This is in the works, see:

https://forum.getmonero.org/8/funding-required/87558/getmonero-com-redesign?page=&noscroll=1

Quote from: LawBC on May 18, 2017, 06:27:45 PM
Some modest advice

- Refine further the GUI ergonomy
All the uneccessary settings for transactions should be hidden. It needs maximum simplification so the non-techy users don't feel confused. Even the tax ID field. Show them on click.
The design as well coud be greatly refined as it's still looking a bit gross and heavy.


Kind of agree, some advanced stuff is already hidden though. Would you be able to open an issue here with your suggestions?

https://github.com/monero-project/monero-core/issues

Quote from: LawBC on May 18, 2017, 06:27:45 PM
Some modest advice

- The paper against Monero published by Zcash devs is showing up on Google search. I'm afraid it's bringing confusion for people searching about Monero. I don't know If you made a blog entry about this in order to clarify. But if not you should.

You can find an (unofficial) response here:

https://getmonero.org/2017/04/19/an-unofficial-response-to-an-empirical-analysis-of-linkability.html
763  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [XMR] Monero - A secure, private, untraceable cryptocurrency on: May 18, 2017, 10:34:38 AM
Disclosure of a Major Bug in CryptoNote Based Currencies (patched in Monero already)

Quote
To clarify, we patched it quite some time ago, and confirmed that the Monero blockchain had NEVER been exploited using this, but until the hard fork that we had a few weeks ago we were unsure as to whether or not the entire network had updated.

https://getmonero.org/2017/05/17/disclosure-of-a-major-bug-in-cryptonote-based-currencies.html
764  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [XMR] Monero - A secure, private, untraceable cryptocurrency on: May 17, 2017, 12:21:01 PM
Quote from: monerostruggles1111 on May 17, 2017, 11:46:29 AM
Well I ditched the armv7 for an armv8 machine and after importing the blockchain from the old box and firing up the daemon it seems to be syncing again.

Code:
2017-05-17 11:37:08.045 [P2P9]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:293     [118.92.17.92:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1312076 [Your node is 112075 blocks (155 days) behind]
SYNCHRONIZATION started
2017-05-17 11:37:51.965 [P2P9]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:1004    [24.20.159.188:18080 OUT]  Synced 1200201/1312076
2017-05-17 11:38:33.269 [P2P9]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:1004    [74.222.20.106:18080 OUT]  Synced 1200401/1312077
2017-05-17 11:39:04.353 [P2P9]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:1004    [104.244.73.123:18080 OUT]  Synced 1200601/1312077

Maybe there's something wrong with armv7?

Apparently the issue is known and is being investigated by the devs:

https://github.com/monero-project/monero/issues/1991

&Chicken76.
765  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [XMR] Monero - A secure, private, untraceable cryptocurrency on: May 16, 2017, 05:22:56 PM
Quote from: Chicken76 on May 16, 2017, 12:34:17 PM
Quote from: dEBRUYNE on May 16, 2017, 10:45:44 AM
Which OS? I presume Linux / Mac OS X, but I'd like to know for sure. Anyway, it should be in $HOME/bitmonero. The directory itself may be hidden, so you have to manually browse to it. Alternatively, on Linux you can unhide directories by using CTRL + H.

I've tried your suggestion with "--block-sync-size" (even a value of 1) and it doesn't get it past 1200001. I'll delete the blockchain and let it resync from scratch.
I'm running the same linuxarm7 build as monerostruggles1111

EDIT: Stopped the daemon and tried to run it on the testnet, to see if it syncs. I got the same behavior, only this time it's stuck on block 3, hehe.

EDIT 2: I've restarted it with "--log-level 4" in hope the details might shed some light on the problem.
Right now it's dumping a 100MB log file every 2 minutes mostly with messages like:
Code:
2017-05-16 18:47:27.212 [P2P0]  TRACE   blockchain      src/cryptonote_core/blockchain.cpp:2105 Blockchain::have_block
2017-05-16 18:47:27.212 [P2P7]  TRACE   blockchain.db.lmdb      src/blockchain_db/lmdb/db_lmdb.cpp:1434 BlockchainLMDB::block_exists
2017-05-16 18:47:27.212 [P2P7]  TRACE   blockchain.db.lmdb      src/blockchain_db/lmdb/db_lmdb.cpp:2445 BlockchainLMDB::block_rtxn_start
2017-05-16 18:47:27.212 [P2P7]  TRACE   blockchain.db.lmdb      src/blockchain_db/lmdb/db_lmdb.cpp:1445 Block with hash 170fd80f88150c79fb52776d5088f253c8cbf9cc7257ba467cada590586a827f not found in db
2017-05-16 18:47:27.213 [P2P7]  TRACE   blockchain.db.lmdb      src/blockchain_db/lmdb/db_lmdb.cpp:305  mdb_txn_safe: destructor


Could you check in the logs whether there are any "Block fails to get added" messages? It's probably easier to spot if you restart monerod with --log-level 1.
766  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [XMR] Monero - A secure, private, untraceable cryptocurrency on: May 16, 2017, 10:45:44 AM
Quote from: monerostruggles1111 on May 16, 2017, 06:37:05 AM
I'm having the same problem as Chiken76, daemon that is stuck on block 1200001 on my VPS that I'm setting up for the first time.

I'd like to follow dEBRUYNE's advice but I can't find the p2pstate.bin file. I'm quite new to this so I could be doing something dumb.

Code:
root@scw-c6201dNode:~# ls -LR
.:
bitmonero  linuxarm7  

./bitmonero:
monero-v0.10.3.1

./bitmonero/monero-v0.10.3.1:
monero-blockchain-export  monero-blockchain-import  monerod  monero-utils-deserialize  monero-wallet-cli  monero-wallet-rpc

Here's the stuck daemon
Code:
root@scw-c6213dNode:~/bitmonero/monero-v0.10.3.1# screen ./monerod
2017-05-16 06:22:56.104         b6ff43b0        INFO    global  contrib/epee/src/mlog.cpp:145   New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO
2017-05-16 06:22:56.105         b6ff43b0        INFO    global  src/daemon/main.cpp:282 Monero 'Wolfram Warptangent' (v0.10.3.1-release)
2017-05-16 06:22:56.106         b6ff43b0        INFO    global  src/daemon/protocol.h:55        Initializing cryptonote protocol...
2017-05-16 06:22:56.106         b6ff43b0        INFO    global  src/daemon/protocol.h:60        Cryptonote protocol initialized OK
2017-05-16 06:22:56.107         b6ff43b0        INFO    global  src/daemon/p2p.h:63     Initializing p2p server...
2017-05-16 06:23:00.505         b6ff43b0        INFO    global  src/daemon/p2p.h:68     P2p server initialized OK
2017-05-16 06:23:00.505         b6ff43b0        INFO    global  src/daemon/rpc.h:58     Initializing core rpc server...
2017-05-16 06:23:00.506         b6ff43b0        INFO    global  contrib/epee/include/net/http_server_impl_base.h:70     Binding on 127.0.0.1:18081
2017-05-16 06:23:00.506         b6ff43b0        INFO    global  src/daemon/rpc.h:63     Core rpc server initialized OK on port: 18081
2017-05-16 06:23:00.506         b6ff43b0        INFO    global  src/daemon/core.h:73    Initializing core...
2017-05-16 06:23:00.518         b6ff43b0        INFO    global  src/cryptonote_core/cryptonote_core.cpp:326     Loading blockchain from folder /root/.bitmonero/lmdb ...
2017-05-16 06:23:01.326         b6ff43b0        INFO    global  src/blockchain_db/lmdb/db_lmdb.cpp:571  [batch] DB resize needed
2017-05-16 06:23:01.326         b6ff43b0        INFO    global  src/blockchain_db/lmdb/db_lmdb.cpp:487  LMDB Mapsize increased.  Old: 12608MiB, New: 13632MiB
2017-05-16 06:23:02.595         b6ff43b0        INFO    global  src/daemon/core.h:78    Core initialized OK
2017-05-16 06:23:02.596         b6ff43b0        INFO    global  src/daemon/rpc.h:68     Starting core rpc server...
2017-05-16 06:23:02.598 [SRV_MAIN]      INFO    global  src/daemon/rpc.h:73     Core rpc server started ok
2017-05-16 06:23:02.598 [SRV_MAIN]      INFO    global  src/daemon/p2p.h:78     Starting p2p net loop...
2017-05-16 06:23:03.600 [P2P1]  INFO    global  src/cryptonote_core/cryptonote_core.cpp:1098
**********************************************************************
The daemon will start synchronizing with the network. It may take up to several hours.

You can set the level of process detailization* through "set_log <level|categories>" command*,
where <level> is between 0 (no details) and 4 (very verbose), or custom category based levels (eg, *:WARNING)

Use the "help" command to see the list of available commands.
**********************************************************************

2017-05-16 06:23:04.110 [P2P7]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:293     [73.110.98.19:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1311217 [Your node is 111216 blocks (154 days) behind]
SYNCHRONIZATION started
2017-05-16 06:28:40.896 [P2P1]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:293     [5.9.2.145:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1311218 [Your node is 111217 blocks (154 days) behind]
SYNCHRONIZATION started
2017-05-16 06:31:06.531 [P2P3]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:293     [217.182.73.97:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1311220 [Your node is 111219 blocks (154 days) behind]
SYNCHRONIZATION started

Thanks for any help.

Which OS? I presume Linux / Mac OS X, but I'd like to know for sure. Anyway, it should be in $HOME/bitmonero. The directory itself may be hidden, so you have to manually browse to it. Alternatively, on Linux you can unhide directories by using CTRL + H.
767  Alternate cryptocurrencies / Speculation (Altcoins) / Re: [XMR] Monero Speculation on: May 15, 2017, 12:28:06 PM
Quote from: hoertest on May 15, 2017, 07:00:47 AM
When creating a paper wallet with the gui do you create a view only wallet? Or a regular one and then delete the wallet file from the computer after writing down the seed?
Thanks

Regular one. View wallets are created from regular wallets, i.e., a view wallet is basically the private view key + the public address of a regular wallet.
768  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [XMR] Monero - A secure, private, untraceable cryptocurrency on: May 13, 2017, 11:23:15 PM
Quote from: revaen on May 13, 2017, 10:52:19 PM
I sent some XMR to my light wallet. It seems it is not working any more. I downloaded the new Light Wallet version. But cannot sent the XMR coins to another wallet. What can I do or is their link with an explanation. Thanks.

Could you please try as follows?

[1] Download the GUI Beta 2 from here:

https://getmonero.org/2017/03/29/monero-gui-beta-2-released.html

[2] It's preferable to run your own node. However, it may be more convenient for you to run a remote node. If you want to do so, change (in the wizard) localhost:18081 to node.xmrbackb.one:18081.

[3] In the wizard select "Open a wallet from file".

[4] Choose the .keys file Light Wallet created.

[5] If you incur an error, delete the accompanying wallet cache and try again. See:

https://monero.stackexchange.com/questions/3122/how-do-i-delete-the-wallet-cache/3123
769  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [XMR] Monero - A secure, private, untraceable cryptocurrency on: May 13, 2017, 11:19:39 PM
Quote from: Chicken76 on May 13, 2017, 03:14:00 PM
Was there something special about block 1200002 ? I have a daemon that is stuck on block 1200001 for a few days now. I've restarted the daemon, but it won't go past 1200001.
Code:
2017-05-13 01:05:34.801	        76fc9250	INFO 	global	contrib/epee/src/mlog.cpp:145	New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO
2017-05-13 01:05:34.802	        76fc9250	INFO 	global	src/daemon/main.cpp:282	Monero 'Wolfram Warptangent' (v0.10.3.1-release)
2017-05-13 01:05:34.811	        76fc9250	WARN 	daemon	src/daemon/executor.cpp:62	Monero 'Wolfram Warptangent' (v0.10.3.1-release) Daemonised
2017-05-13 01:05:34.812	        76fc9250	INFO 	global	src/daemon/protocol.h:55	Initializing cryptonote protocol...
2017-05-13 01:05:34.812	        76fc9250	INFO 	global	src/daemon/protocol.h:60	Cryptonote protocol initialized OK
2017-05-13 01:05:34.816	        76fc9250	INFO 	global	src/daemon/p2p.h:63	Initializing p2p server...
2017-05-13 01:05:43.861	        76fc9250	INFO 	global	src/daemon/p2p.h:68	P2p server initialized OK
2017-05-13 01:05:43.861	        76fc9250	INFO 	global	src/daemon/rpc.h:58	Initializing core rpc server...
2017-05-13 01:05:43.861	        76fc9250	INFO 	global	contrib/epee/include/net/http_server_impl_base.h:70	Binding on 127.0.0.1:18081
2017-05-13 01:05:43.862	        76fc9250	INFO 	global	src/daemon/rpc.h:63	Core rpc server initialized OK on port: 18081
2017-05-13 01:05:43.862	        76fc9250	INFO 	global	src/daemon/core.h:73	Initializing core...
2017-05-13 01:05:43.883	        76fc9250	INFO 	global	src/cryptonote_core/cryptonote_core.cpp:326	Loading blockchain from folder .bitmonero/lmdb ...
2017-05-13 01:05:43.887	        76fc9250	WARN 	blockchain.db.lmdb	src/blockchain_db/lmdb/db_lmdb.cpp:1138	LMDB memory map needs to be resized, doing that now.
2017-05-13 01:05:43.887	        76fc9250	INFO 	global	src/blockchain_db/lmdb/db_lmdb.cpp:487	LMDB Mapsize increased.  Old: 9431MiB, New: 10455MiB
2017-05-13 01:06:17.598	        76fc9250	INFO 	global	src/blockchain_db/lmdb/db_lmdb.cpp:571	[batch] DB resize needed
2017-05-13 01:06:17.599	        76fc9250	INFO 	global	src/blockchain_db/lmdb/db_lmdb.cpp:487	LMDB Mapsize increased.  Old: 10455MiB, New: 11479MiB
2017-05-13 01:06:18.385	        76fc9250	INFO 	global	src/blockchain_db/lmdb/db_lmdb.cpp:571	[batch] DB resize needed
2017-05-13 01:06:18.385	        76fc9250	INFO 	global	src/blockchain_db/lmdb/db_lmdb.cpp:487	LMDB Mapsize increased.  Old: 11479MiB, New: 12503MiB
2017-05-13 01:06:19.083	        76fc9250	INFO 	global	src/daemon/core.h:78	Core initialized OK
2017-05-13 01:06:19.083	        76fc9250	INFO 	global	src/daemon/rpc.h:68	Starting core rpc server...
2017-05-13 01:06:19.085	[SRV_MAIN]	INFO 	global	src/daemon/rpc.h:73	Core rpc server started ok
2017-05-13 01:06:19.085	[SRV_MAIN]	INFO 	global	src/daemon/p2p.h:78	Starting p2p net loop...
2017-05-13 01:06:20.086	[P2P1]	INFO 	global	src/cryptonote_core/cryptonote_core.cpp:1098	
**********************************************************************
The daemon will start synchronizing with the network. It may take up to several hours.

You can set the level of process detailization* through "set_log <level|categories>" command*,
where <level> is between 0 (no details) and 4 (very verbose), or custom category based levels (eg, *:WARNING)

Use the "help" command to see the list of available commands.
**********************************************************************

2017-05-13 01:06:21.494	[P2P5]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[59.46.181.116:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308818 [Your node is 108817 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 01:13:43.096	[P2P6]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[66.228.41.201:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308819 [Your node is 108818 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 01:16:24.838	[P2P3]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[46.255.20.102:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308824 [Your node is 108823 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 01:17:35.108	[P2P2]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[104.218.50.245:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308825 [Your node is 108824 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 01:18:39.924	[P2P9]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[37.142.29.160:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308827 [Your node is 108826 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 01:18:46.141	[P2P4]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[104.218.50.245:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308828 [Your node is 108827 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 01:24:22.074	[P2P7]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[121.78.158.99:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308829 [Your node is 108828 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 01:33:27.674	[P2P7]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[138.68.56.11:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308835 [Your node is 108834 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 01:37:27.947	[P2P8]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[163.172.191.158:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308838 [Your node is 108837 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 01:38:47.954	[P2P6]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[176.9.0.89:8180 OUT] Sync data returned a new top block candidate: 1200001 -> 1308839 [Your node is 108838 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 01:54:57.178	[P2P7]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[163.172.191.158:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308845 [Your node is 108844 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 01:59:24.163	[P2P5]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[138.68.56.11:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308847 [Your node is 108846 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 02:09:04.134	[P2P6]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[47.18.126.206:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308852 [Your node is 108851 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 02:09:37.339	[P2P7]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[77.47.204.155:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308853 [Your node is 108852 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 02:16:01.298	[P2P3]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[46.255.20.102:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308855 [Your node is 108854 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 02:16:28.159	[P2P0]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[104.140.20.191:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308856 [Your node is 108855 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 02:22:54.650	[P2P7]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[138.68.56.11:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308858 [Your node is 108857 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 02:30:08.503	[P2P0]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[138.68.56.11:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308859 [Your node is 108858 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 02:44:40.332	[P2P9]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[79.137.75.116:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308861 [Your node is 108860 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 02:47:47.751	[P2P3]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[79.137.75.116:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308863 [Your node is 108862 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 02:56:45.177	[P2P3]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[60.226.94.228:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308869 [Your node is 108868 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 03:02:30.161	[P2P2]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[163.172.191.158:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308870 [Your node is 108869 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 03:02:33.446	[P2P4]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[66.228.41.201:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308871 [Your node is 108870 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 03:08:34.621	[P2P6]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[46.255.20.102:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308875 [Your node is 108874 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 03:13:11.883	[P2P2]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[163.172.191.158:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308877 [Your node is 108876 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 03:14:12.017	[P2P5]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[138.68.56.11:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308878 [Your node is 108877 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 03:32:19.129	[P2P2]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[121.78.158.99:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308889 [Your node is 108888 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 03:48:18.765	[P2P0]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[77.47.204.155:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308894 [Your node is 108893 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 03:53:21.767	[P2P2]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[66.228.41.201:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308895 [Your node is 108894 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 04:05:40.664	[P2P0]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[104.218.50.245:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308902 [Your node is 108901 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 04:16:45.765	[P2P3]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[77.47.204.155:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308907 [Your node is 108906 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 04:22:47.722	[P2P6]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[60.226.94.228:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308909 [Your node is 108908 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 04:27:54.592	[P2P6]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[79.137.75.116:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308912 [Your node is 108911 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 04:40:41.263	[P2P0]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[52.231.32.220:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308916 [Your node is 108915 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 04:46:08.712	[P2P6]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[73.248.31.11:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308920 [Your node is 108919 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 04:53:23.395	[P2P8]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[95.147.163.106:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308922 [Your node is 108921 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 05:04:52.068	[P2P5]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[60.226.94.228:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308926 [Your node is 108925 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 05:12:10.958	[P2P2]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[60.226.94.228:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308930 [Your node is 108929 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 05:19:34.649	[P2P2]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[73.248.31.11:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308932 [Your node is 108931 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 05:26:25.192	[P2P4]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[96.231.192.214:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308935 [Your node is 108934 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 05:27:00.474	[P2P5]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[31.10.75.158:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308936 [Your node is 108935 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 05:43:05.416	[P2P1]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[37.142.29.160:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308947 [Your node is 108946 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 05:43:32.993	[P2P0]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[73.248.31.11:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308948 [Your node is 108947 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 05:54:13.537	[P2P3]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[66.228.41.201:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308957 [Your node is 108956 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 05:55:27.544	[P2P1]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[73.248.31.11:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308958 [Your node is 108957 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 05:56:20.229	[P2P6]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[24.90.41.64:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308959 [Your node is 108958 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 06:01:01.135	[P2P8]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[37.59.49.7:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308964 [Your node is 108963 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 06:09:53.160	[P2P2]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[95.147.163.106:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308968 [Your node is 108967 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 06:23:19.072	[P2P0]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[37.142.29.160:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308976 [Your node is 108975 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 06:34:34.768	[P2P0]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[121.78.158.99:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308980 [Your node is 108979 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 06:34:40.740	[P2P7]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[52.231.32.220:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308981 [Your node is 108980 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 06:41:41.529	[P2P7]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[31.10.75.158:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308983 [Your node is 108982 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 06:42:05.544	[P2P8]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[176.9.0.89:8180 OUT] Sync data returned a new top block candidate: 1200001 -> 1308984 [Your node is 108983 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 06:48:16.107	[P2P8]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[163.172.10.45:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308986 [Your node is 108985 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 06:54:13.710	[P2P1]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[88.99.218.75:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308989 [Your node is 108988 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 06:59:11.951	[P2P9]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[88.99.218.75:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308992 [Your node is 108991 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 07:00:34.694	[P2P8]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[91.181.63.218:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1308993 [Your node is 108992 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 07:12:21.719	[P2P2]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[60.226.94.228:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309000 [Your node is 108999 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 07:16:23.920	[P2P2]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[88.99.218.75:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309007 [Your node is 109006 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 07:17:14.835	[P2P9]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[37.59.49.7:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309008 [Your node is 109007 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 07:34:59.357	[P2P3]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[37.142.29.160:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309013 [Your node is 109012 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 07:35:22.006	[P2P5]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[88.99.218.75:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309016 [Your node is 109015 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 07:42:24.049	[P2P1]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[45.55.241.132:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309018 [Your node is 109017 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 07:59:54.343	[P2P8]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[220.239.105.31:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309024 [Your node is 109023 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 08:04:56.059	[P2P9]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[24.90.41.64:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309026 [Your node is 109025 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 08:05:26.286	[P2P6]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[163.172.10.45:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309027 [Your node is 109026 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 08:06:40.534	[P2P3]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[95.147.163.106:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309028 [Your node is 109027 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 08:21:18.853	[P2P7]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[52.228.24.37:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309035 [Your node is 109034 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 08:44:07.474	[P2P8]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[60.226.94.228:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309041 [Your node is 109040 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 08:44:31.724	[P2P7]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[52.231.32.220:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309045 [Your node is 109044 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 08:51:04.335	[P2P4]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[37.59.49.7:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309049 [Your node is 109048 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 09:02:21.309	[P2P9]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[60.226.94.228:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309055 [Your node is 109054 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 09:03:17.525	[P2P5]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[37.59.49.7:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309056 [Your node is 109055 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 09:19:13.385	[P2P2]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[163.172.10.45:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309067 [Your node is 109066 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 09:36:00.208	[P2P1]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[88.99.218.75:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309074 [Your node is 109073 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 09:37:24.971	[P2P7]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[163.172.10.45:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309075 [Your node is 109074 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 09:52:14.527	[P2P5]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[37.59.49.7:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309076 [Your node is 109075 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 09:52:32.234	[P2P2]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[31.10.75.158:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309081 [Your node is 109080 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 10:00:35.011	[P2P1]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[88.99.218.75:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309083 [Your node is 109082 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 10:08:05.004	[P2P7]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[37.59.49.7:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309086 [Your node is 109085 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 10:08:06.924	[P2P2]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[60.226.94.228:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309088 [Your node is 109087 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 10:14:58.555	[P2P3]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[176.9.0.89:8180 OUT] Sync data returned a new top block candidate: 1200001 -> 1309090 [Your node is 109089 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 10:22:58.924	[P2P6]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[88.99.218.75:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309092 [Your node is 109091 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 10:31:01.130	[P2P8]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[37.59.49.7:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309094 [Your node is 109093 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 10:31:29.634	[P2P8]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[37.142.29.160:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309095 [Your node is 109094 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 10:31:47.234	[P2P3]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[37.59.49.7:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309096 [Your node is 109095 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 10:38:48.525	[P2P5]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[37.59.49.7:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309103 [Your node is 109102 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 10:45:39.796	[P2P6]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[163.172.10.45:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309104 [Your node is 109103 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 10:50:55.738	[P2P6]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[60.226.94.228:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309105 [Your node is 109104 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 10:56:46.392	[P2P0]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[60.226.94.228:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309111 [Your node is 109110 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 10:57:17.554	[P2P8]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[198.100.144.155:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309112 [Your node is 109111 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 11:03:04.344	[P2P5]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[24.90.41.64:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309115 [Your node is 109114 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 11:08:40.140	[P2P2]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[176.9.0.89:8180 OUT] Sync data returned a new top block candidate: 1200001 -> 1309119 [Your node is 109118 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 11:16:39.390	[P2P7]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[24.90.41.64:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309122 [Your node is 109121 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 11:16:58.424	[P2P1]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[60.226.94.228:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309128 [Your node is 109127 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 11:18:09.304	[P2P7]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[198.100.144.155:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309129 [Your node is 109128 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 11:18:17.533	[P2P8]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[31.10.75.158:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309131 [Your node is 109130 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 11:24:42.638	[P2P8]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[163.172.10.45:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309132 [Your node is 109131 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 11:25:17.700	[P2P8]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[24.90.41.64:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309133 [Your node is 109132 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 11:31:05.254	[P2P9]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[176.9.0.89:8180 OUT] Sync data returned a new top block candidate: 1200001 -> 1309135 [Your node is 109134 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 11:42:40.602	[P2P7]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[24.90.41.64:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309141 [Your node is 109140 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 11:59:06.329	[P2P8]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[163.172.10.45:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309152 [Your node is 109151 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 12:03:24.624	[P2P3]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[31.10.75.158:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309153 [Your node is 109152 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 12:03:25.655	[P2P3]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[95.147.163.106:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309154 [Your node is 109153 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 12:18:36.455	[P2P9]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[198.100.144.155:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309156 [Your node is 109155 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 12:25:34.900	[P2P0]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[198.100.144.155:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309160 [Your node is 109159 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 12:27:12.844	[P2P1]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[45.55.241.132:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309161 [Your node is 109160 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 12:27:34.244	[P2P8]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[50.161.22.252:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309162 [Your node is 109161 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 12:44:14.767	[P2P9]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[60.226.94.228:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309170 [Your node is 109169 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 12:44:45.254	[P2P6]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[45.55.241.132:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309174 [Your node is 109173 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 12:51:35.850	[P2P2]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[37.10.71.249:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309180 [Your node is 109179 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 13:05:51.423	[P2P4]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[37.10.71.249:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309187 [Your node is 109186 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 13:08:01.834	[P2P6]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[31.10.75.158:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309188 [Your node is 109187 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 13:08:08.865	[P2P6]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[52.228.24.37:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309189 [Your node is 109188 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 13:23:20.835	[P2P6]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[88.99.218.75:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309196 [Your node is 109195 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 13:24:37.834	[P2P5]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[37.59.49.7:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309197 [Your node is 109196 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 13:24:59.454	[P2P4]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[88.99.218.75:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309198 [Your node is 109197 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 13:32:26.258	[P2P6]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[88.99.218.75:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309202 [Your node is 109201 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 13:37:08.799	[P2P4]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[88.99.218.75:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309203 [Your node is 109202 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 13:37:55.234	[P2P6]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[24.90.41.64:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309205 [Your node is 109204 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 13:49:19.419	[P2P9]	INFO 	global	src/p2p/net_node.inl:250	IP 148.251.83.237 blocked.
2017-05-13 13:52:18.866	[P2P7]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[45.55.241.132:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309207 [Your node is 109206 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 13:53:49.134	[P2P4]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[52.228.24.37:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309208 [Your node is 109207 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 13:59:47.300	[P2P7]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[88.99.218.75:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309209 [Your node is 109208 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 14:15:03.061	[P2P1]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[24.90.41.64:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309213 [Your node is 109212 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 14:15:08.839	[P2P0]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[163.172.10.45:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309214 [Your node is 109213 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 14:16:12.828	[P2P6]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[37.10.71.249:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309215 [Your node is 109214 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 14:33:51.675	[P2P0]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[45.55.241.132:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309219 [Your node is 109218 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 14:41:32.075	[P2P7]	INFO 	global	src/p2p/net_node.inl:250	IP 88.99.218.75 blocked.
2017-05-13 14:46:27.990	[P2P1]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[139.162.217.31:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309220 [Your node is 109219 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 14:55:09.157	[P2P2]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[51.15.7.236:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309227 [Your node is 109226 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 14:57:42.084	[P2P6]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[52.228.24.37:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309228 [Your node is 109227 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 14:58:11.174	[P2P5]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[45.55.241.132:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309229 [Your node is 109228 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 15:04:09.813	[P2P2]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[81.96.233.246:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309234 [Your node is 109233 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 15:10:51.497	[P2P2]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[52.228.24.37:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309240 [Your node is 109239 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 15:22:22.798	[P2P7]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[50.161.22.252:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309246 [Your node is 109245 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 15:23:09.824	[P2P2]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[176.9.0.89:8180 OUT] Sync data returned a new top block candidate: 1200001 -> 1309247 [Your node is 109246 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 15:40:07.909	[P2P2]	INFO 	global	src/p2p/net_node.inl:250	IP 176.9.0.89 blocked.
2017-05-13 15:43:33.487	[P2P5]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[45.55.241.132:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309254 [Your node is 109253 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 15:43:34.484	[P2P5]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[95.147.163.106:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309255 [Your node is 109254 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 15:45:23.623	[P2P4]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[139.162.217.31:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309257 [Your node is 109256 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 16:05:54.612	[P2P0]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[81.96.233.246:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309262 [Your node is 109261 blocks (151 days) behind] 
SYNCHRONIZATION started
2017-05-13 16:06:47.994	[P2P3]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:293	[139.162.217.31:18080 OUT] Sync data returned a new top block candidate: 1200001 -> 1309270 [Your node is 109269 blocks (151 days) behind] 
SYNCHRONIZATION started

I'll restart the machine and fsck the filesystem and report back.

Could you try as follows:

[1] Exit monerod

[2] Delete p2pstate.bin (on Windows it's in C:\ProgramData\bitmonero | Linux & Mac OS X it's in $HOME/bitmonero)

[3] Restart monerod with the following command:

Code:
monerod --block-sync-size 20

If you could give your operating system I could give some more detailed instructions (if aforementioned aren't sufficient).
770  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [XMR] Monero - A secure, private, untraceable cryptocurrency on: May 12, 2017, 07:26:24 PM
"Monero GUI Wallet Guide"

https://www.deepdotweb.com/2017/05/01/monero-gui-wallet-guide/

Probably the most comprehensive guide out there currently.
771  Alternate cryptocurrencies / Speculation (Altcoins) / Re: [XMR] Monero Speculation on: May 12, 2017, 07:26:05 PM
"Monero GUI Wallet Guide"

https://www.deepdotweb.com/2017/05/01/monero-gui-wallet-guide/

Probably the most comprehensive guide out there currently.
772  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [XMR] Monero - A secure, private, untraceable cryptocurrency on: May 09, 2017, 10:33:39 AM
Quote from: yakpimp on May 09, 2017, 05:08:08 AM
If so, does the QT wallet support RPC?

You probably have to use the CLI, see:

https://getmonero.org/getting-started/accepting

or:

https://github.com/TheKoziTwo/xmr-integration
773  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [XMR] Monero - A secure, private, untraceable cryptocurrency on: May 06, 2017, 09:36:42 AM
For speculation and price talk, please use this thread:

https://bitcointalk.org/index.php?topic=753252.0
774  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [XMR] Monero - A secure, private, untraceable cryptocurrency on: May 02, 2017, 01:32:20 PM
Quote from: nzminer on May 02, 2017, 06:24:12 AM
Can someone help me here?

Ive finally synced my blockchain after 4 solid days and now when i come to running a sweep_unmixable command, its saying mixin too low.

Any ideas whats wrong?


TIA Smiley

Could you try the sweep_all command?
775  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [XMR] Monero - A secure, private, untraceable cryptocurrency on: April 28, 2017, 02:24:21 PM
Quote from: george888055 on April 28, 2017, 08:09:18 AM
My wallet can't sync again.
 Huh Huh Huh
the only way to solve the problem is delete blockchain. but i don't want to do it anymore..

Could you provide a bit more information about your issue(s)?
776  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [XMR] Monero - A secure, private, untraceable cryptocurrency on: April 28, 2017, 02:22:46 PM
Quote from: GingerAle on April 28, 2017, 12:05:44 PM
Quote from: coomme on April 28, 2017, 10:43:57 AM
and any help to me ?
when I transfer xmr to exchange on my wallet, its say:

Error: transaction <f1f67363aefccfa2de64d0b014f4ff4544aeaa0f70d2d823e1938b52fe76835a> was rejected by daemon with status
: Failed
Error: Reason: double spend

I tryed twice, restart wallet, etc, its always : double spend

and daemon info:

daemon.rpc said: On_send_raw_tx: tx verification  Failed

maybe low transfer fee wrong ? but cant set it

any good idea ?

So, its not on the chain, so its a problem with your wallet:

https://xmrchain.net/search?value=f1f67363aefccfa2de64d0b014f4ff4544aeaa0f70d2d823e1938b52fe76835a

You can fix the cache with this I think:

https://monero.stackexchange.com/questions/3122/how-do-i-delete-the-wallet-cache

edited to add: or the transaction could be stuck in your daemons mempool for some reason and not being relayed. Are you running your own daemon?



Removing the cache would result in losing the private tx keys (which are needed in case of disputes) and recipient addresses (which may come in handy from time to time). In this case it's better to first open monerod and type "flush_txpool". Subsequently, open monero-wallet-cli and type "rescan_spent".
777  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [XMR] Monero - A secure, private, untraceable cryptocurrency on: April 27, 2017, 09:49:00 AM
Quote from: nzminer on April 27, 2017, 09:38:35 AM
Quote from: dEBRUYNE on April 27, 2017, 12:18:41 AM
Quote from: nzminer on April 26, 2017, 11:43:58 PM
What's wrong with my wallet? I cant get into it?

C:\monero>monerod
2017-04-27 11:42:03.327 324     INFO    global  contrib/epee/src/mlog.cpp:145
New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,v
erify:FATAL,stacktrace:INFO
2017-04-27 11:42:03.328 324     INFO    global  src/daemon/main.cpp:282 Monero '
Wolfram Warptangent' (v0.10.3.1-release)
2017-04-27 11:42:03.329 324     INFO    global  src/daemon/protocol.h:55
Initializing cryptonote protocol...
2017-04-27 11:42:03.330 324     INFO    global  src/daemon/protocol.h:60
Cryptonote protocol initialized OK
2017-04-27 11:42:03.331 324     INFO    global  src/daemon/p2p.h:63     Initiali
zing p2p server...
2017-04-27 11:42:04.748 324     INFO    global  src/daemon/p2p.h:68     P2p serv
er initialized OK
2017-04-27 11:42:04.748 324     INFO    global  src/daemon/rpc.h:58     Initiali
zing core rpc server...
2017-04-27 11:42:04.750 324     INFO    global  contrib/epee/include/net/http_se
rver_impl_base.h:70     Binding on 127.0.0.1:18081
2017-04-27 11:42:04.750 324     INFO    global  src/daemon/rpc.h:63     Core rpc
 server initialized OK on port: 18081
2017-04-27 11:42:04.751 324     INFO    global  src/daemon/core.h:73    Initiali
zing core...
2017-04-27 11:42:04.753 324     INFO    global  src/cryptonote_core/cryptonote_c
ore.cpp:326     Loading blockchain from folder C:\ProgramData\bitmonero\lmdb ...

2017-04-27 11:42:04.757 324     WARN    blockchain.db.lmdb      src/blockchain_d
b/lmdb/db_lmdb.cpp:71   Failed to get a record from props: MDB_NOTFOUND: No matc
hing key/data pair found
2017-04-27 11:42:04.758 324     ERROR   cn      src/cryptonote_core/cryptonote_c
ore.cpp:395     Error opening database: Failed to get a record from props: MDB_N
OTFOUND: No matching key/data pair found
2017-04-27 11:42:04.758 324     INFO    global  src/daemon/rpc.h:90     Deinitia
lizing rpc server...
2017-04-27 11:42:04.759 324     INFO    global  src/daemon/p2p.h:90     Deinitia
lizing p2p...
2017-04-27 11:42:04.760 324     INFO    global  src/daemon/core.h:89    Deinitia
lizing core...
2017-04-27 11:42:04.762 324     ERROR   daemon  src/daemon/core.h:94    Failed t
o deinitialize core...
2017-04-27 11:42:04.763 324     INFO    global  src/daemon/protocol.h:77
Stopping cryptonote protocol...
2017-04-27 11:42:04.763 324     INFO    global  src/daemon/protocol.h:81
Cryptonote protocol stopped successfully

Which version are you using?

I just downloaded the latest version.

I also see that simplewallet is missing from it.

Could you delete the bitmonero folder and restart monerod? On Windows it's in C:\ProgramData. In addition, simplewallet was renamed to monero-wallet-cli.
778  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [XMR] Monero - A secure, private, untraceable cryptocurrency on: April 27, 2017, 12:18:41 AM
Quote from: nzminer on April 26, 2017, 11:43:58 PM
What's wrong with my wallet? I cant get into it?

C:\monero>monerod
2017-04-27 11:42:03.327 324     INFO    global  contrib/epee/src/mlog.cpp:145
New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,v
erify:FATAL,stacktrace:INFO
2017-04-27 11:42:03.328 324     INFO    global  src/daemon/main.cpp:282 Monero '
Wolfram Warptangent' (v0.10.3.1-release)
2017-04-27 11:42:03.329 324     INFO    global  src/daemon/protocol.h:55
Initializing cryptonote protocol...
2017-04-27 11:42:03.330 324     INFO    global  src/daemon/protocol.h:60
Cryptonote protocol initialized OK
2017-04-27 11:42:03.331 324     INFO    global  src/daemon/p2p.h:63     Initiali
zing p2p server...
2017-04-27 11:42:04.748 324     INFO    global  src/daemon/p2p.h:68     P2p serv
er initialized OK
2017-04-27 11:42:04.748 324     INFO    global  src/daemon/rpc.h:58     Initiali
zing core rpc server...
2017-04-27 11:42:04.750 324     INFO    global  contrib/epee/include/net/http_se
rver_impl_base.h:70     Binding on 127.0.0.1:18081
2017-04-27 11:42:04.750 324     INFO    global  src/daemon/rpc.h:63     Core rpc
 server initialized OK on port: 18081
2017-04-27 11:42:04.751 324     INFO    global  src/daemon/core.h:73    Initiali
zing core...
2017-04-27 11:42:04.753 324     INFO    global  src/cryptonote_core/cryptonote_c
ore.cpp:326     Loading blockchain from folder C:\ProgramData\bitmonero\lmdb ...

2017-04-27 11:42:04.757 324     WARN    blockchain.db.lmdb      src/blockchain_d
b/lmdb/db_lmdb.cpp:71   Failed to get a record from props: MDB_NOTFOUND: No matc
hing key/data pair found
2017-04-27 11:42:04.758 324     ERROR   cn      src/cryptonote_core/cryptonote_c
ore.cpp:395     Error opening database: Failed to get a record from props: MDB_N
OTFOUND: No matching key/data pair found
2017-04-27 11:42:04.758 324     INFO    global  src/daemon/rpc.h:90     Deinitia
lizing rpc server...
2017-04-27 11:42:04.759 324     INFO    global  src/daemon/p2p.h:90     Deinitia
lizing p2p...
2017-04-27 11:42:04.760 324     INFO    global  src/daemon/core.h:89    Deinitia
lizing core...
2017-04-27 11:42:04.762 324     ERROR   daemon  src/daemon/core.h:94    Failed t
o deinitialize core...
2017-04-27 11:42:04.763 324     INFO    global  src/daemon/protocol.h:77
Stopping cryptonote protocol...
2017-04-27 11:42:04.763 324     INFO    global  src/daemon/protocol.h:81
Cryptonote protocol stopped successfully

Which version are you using?
779  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [XMR] Monero - A secure, private, untraceable cryptocurrency on: April 24, 2017, 07:56:33 PM
[Funding] Monero Bounty for HackerOne

https://forum.getmonero.org/8/funding-required/87597/monero-bounty-for-hackerone

https://www.reddit.com/r/Monero/comments/67bfqw/funding_monero_bounty_for_hackerone/


[Funding] Hire PhD mathematician (Surae Noether) to look into post-quantum crypto, ZK protocols, blockchain bloat

https://forum.getmonero.org/8/funding-required/87652/hire-phd-mathematician-to-look-into-post-quantum-crypto-zk-protocols-blockchain-bloat

https://www.reddit.com/r/Monero/comments/67apo7/funding_surae_noether_lets_get_this_funded_guys/
780  Alternate cryptocurrencies / Speculation (Altcoins) / Re: [XMR] Monero Speculation on: April 24, 2017, 07:56:22 PM
[Funding] Monero Bounty for HackerOne

https://forum.getmonero.org/8/funding-required/87597/monero-bounty-for-hackerone

https://www.reddit.com/r/Monero/comments/67bfqw/funding_monero_bounty_for_hackerone/


[Funding] Hire PhD mathematician (Surae Noether) to look into post-quantum crypto, ZK protocols, blockchain bloat

https://forum.getmonero.org/8/funding-required/87652/hire-phd-mathematician-to-look-into-post-quantum-crypto-zk-protocols-blockchain-bloat

https://www.reddit.com/r/Monero/comments/67apo7/funding_surae_noether_lets_get_this_funded_guys/
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 [39] 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 ... 181 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!