Bitcoin Forum
November 02, 2024, 12:47:25 PM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Bitcoin Forum > Alternate cryptocurrencies > Announcements (Altcoins) > [BCN] Bytecoin. Secure, private, untraceable since 2012
Warning: One or more bitcointalk.org users have reported that they strongly believe that the creator of this topic is a scammer. (Login to see the detailed trust ratings.) While the bitcointalk.org administration does not verify such claims, you should proceed with extreme caution.
Pages: « 1 ... 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 [184] 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 ... 417 »
« previous topic next topic »
  Print  
Author Topic: [BCN] Bytecoin. Secure, private, untraceable since 2012  (Read 1070233 times)
saYRam
Newbie
*
Offline Offline

Activity: 19
Merit: 0


View Profile
August 19, 2014, 10:01:22 AM
Last edit: August 19, 2014, 10:31:17 AM by saYRam
 #3661
Quote from: Rytir_fik on August 19, 2014, 08:44:43 AM
Quote from: saYRam on August 19, 2014, 08:29:27 AM

couldnt syncronized. I get this messages. Whats wrong with it?

win7 x64 en (7600)
i7 2600k
do you use the last binary 1.0.1? If not update it. https://bitcointalk.org/index.php?topic=512747.msg8351704#msg8351704

cur version is v1.0.1.316 for deamon and wallet.

See the new logs. I can see
2014-Aug-19 12:51:48.788573 [P2P9][95.211.224.150:8080 OUT] SYNCHRONIZED OK
but news lines weird. Cant refresh the wallet and demon always go on "SYNCHRONIZATION started" err lines "SYNCHRONIZATION started" err lines.

btw i use this command to start deamon

Code:
bytecoind --rpc-bind-port=8080 --p2p-bind-port=8081

ty for ur answer.

Code:
2014-Aug-19 12:50:12.985093 bytecoin v1.0.1.316()
2014-Aug-19 12:50:12.986093 Module folder: bytecoind
2014-Aug-19 12:50:12.988094 Initializing p2p server...
2014-Aug-19 12:50:13.199106 Binding on 0.0.0.0:8081
2014-Aug-19 12:50:13.201106 Net service binded on 0.0.0.0:8081
2014-Aug-19 12:50:13.203106 Attempting to add IGD port mapping.
2014-Aug-19 12:50:14.226164 Added IGD port mapping.
2014-Aug-19 12:50:14.229165 P2p server initialized OK
2014-Aug-19 12:50:14.230165 Initializing cryptonote protocol...
2014-Aug-19 12:50:14.232165 Cryptonote protocol initialized OK
2014-Aug-19 12:50:14.234165 Initializing core rpc server...
2014-Aug-19 12:50:14.235165 Binding on 127.0.0.1:8080
2014-Aug-19 12:50:14.237165 Core rpc server initialized OK on port: 8080
2014-Aug-19 12:50:14.239165 Initializing core...
2014-Aug-19 12:50:14.271167 Loading blockchain...
2014-Aug-19 12:50:14.274167 No actual blockchain cache found, rebuilding internal structures...
2014-Aug-19 12:51:46.092419 Rebuilding internal structures took: 91.8153
2014-Aug-19 12:51:46.240427 Blockchain initialized. last block: 548780, d0.h0.m9.s4 time ago, current difficulty: 76912305
2014-Aug-19 12:51:46.350434 Core initialized OK
2014-Aug-19 12:51:46.352434 Starting core rpc server...
2014-Aug-19 12:51:46.354434 Run net_service loop( 2 threads)...
2014-Aug-19 12:51:46.366435 [SRV_MAIN]Core rpc server started ok
2014-Aug-19 12:51:46.369435 [SRV_MAIN]Starting p2p net loop...
2014-Aug-19 12:51:46.371435 [SRV_MAIN]Run net_service loop( 10 threads)...
2014-Aug-19 12:51:46.393436 [P2P1][27.72.105.127:17026 INC]Sync data returned unknown top block: 548781 -> 548785 [4 blocks (0 days) behind] 
SYNCHRONIZATION started
2014-Aug-19 12:51:46.393436 [P2P2][124.121.82.93:56540 INC]Sync data returned unknown top block: 548781 -> 546611 [2170 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:51:46.393436 [P2P3][109.197.253.113:56853 INC]Sync data returned unknown top block: 548781 -> 546611 [2170 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:51:46.393436 [P2P0][216.8.146.119:57880 INC]Sync data returned unknown top block: 548781 -> 546611 [2170 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:51:47.371492 [P2P0]
**********************************************************************
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>" command*, where <level> is between 0 (no details) and 4 (very verbose).

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

Note: in case you need to interrupt the process, use "exit" command. Otherwise, the current progress won't be saved.
**********************************************************************
2014-Aug-19 12:51:47.633507 [P2P7][95.211.224.150:8080 OUT]Sync data returned unknown top block: 548781 -> 548785 [4 blocks (0 days) behind] 
SYNCHRONIZATION started
2014-Aug-19 12:51:48.788573 [P2P9][95.211.224.150:8080 OUT] SYNCHRONIZED OK
2014-Aug-19 12:51:48.791573 [P2P9]
**********************************************************************
You are now synchronized with the network. You may now start simplewallet.

Please note, that the blockchain will be saved only after you quit the daemon with "exit" command or if you use "save" command.
Otherwise, you will possibly need to synchronize the blockchain again.

Use "help" command to see the list of available commands.
**********************************************************************
2014-Aug-19 12:52:13.148966 [P2P2][86.9.233.2:18063 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:52:20.314376 [P2P7][216.8.146.119:58041 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:52:29.477900 [P2P9]----- BLOCK ADDED AS ALTERNATIVE ON HEIGHT 546603
id:	<91e836cd2a9b30a32a3858f2f9162a3453a7d96747c3ef993c8c07a9a3e52d67>
PoW:	<82b6f74a4c92bd28cce4d2eeac96f202110b0af9528ab4f44e11271f05000000>
difficulty:	95882153
2014-Aug-19 12:52:29.489901 [P2P9]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:52:29.494901 [P2P9][216.8.146.119:58041 INC]Block verification failed, dropping connection
2014-Aug-19 12:52:47.196914 [P2P7][124.121.82.93:56576 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:52:57.445500 [P2P5]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:52:57.451500 [P2P5][124.121.82.93:56576 INC]Block verification failed, dropping connection
2014-Aug-19 12:53:02.879811 [P2P9]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:53:02.885811 [P2P9][86.9.233.2:18063 INC]Block verification failed, dropping connection
2014-Aug-19 12:53:15.001504 [P2P6][109.197.253.113:56921 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:53:27.092196 [P2P2]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:53:27.099196 [P2P2][109.197.253.113:56921 INC]Block verification failed, dropping connection
2014-Aug-19 12:53:33.732576 [P2P0][159.118.166.237:37672 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:53:40.068938 [P2P8]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:53:40.075938 [P2P8][159.118.166.237:37672 INC]Block verification failed, dropping connection
2014-Aug-19 12:53:46.972333 [P2P7][182.161.177.27:5892 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:53:55.358812 [P2P3]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:53:55.365813 [P2P3][182.161.177.27:5892 INC]Block verification failed, dropping connection
2014-Aug-19 12:54:21.811325 [P2P7]ERROR c:\projects\sorrybigbro\contrib\epee\include\net\levin_protocol_handler_async.h:440 [127.0.0.1:65524 INC]Signature mismatch, connection will be closed
2014-Aug-19 12:54:21.827326 [P2P5]ERROR c:\projects\sorrybigbro\contrib\epee\include\net\levin_protocol_handler_async.h:440 [127.0.0.1:65525 INC]Signature mismatch, connection will be closed
2014-Aug-19 12:54:25.681547 [P2P4][159.118.166.237:37689 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:54:30.474821 [P2P8]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:54:30.481821 [P2P8][159.118.166.237:37689 INC]Block verification failed, dropping connection
2014-Aug-19 12:54:32.626944 [P2P3][216.8.146.119:58348 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:54:41.221436 [P2P1]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:54:41.228436 [P2P1][216.8.146.119:58348 INC]Block verification failed, dropping connection
2014-Aug-19 12:54:45.137660 [P2P9][182.161.177.27:5902 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:54:51.038997 [P2P2]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:54:51.045998 [P2P2][182.161.177.27:5902 INC]Block verification failed, dropping connection
2014-Aug-19 12:54:56.352301 [P2P7][109.197.253.113:56972 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:55:00.212522 [P2P1][182.161.177.27:5907 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:55:06.343873 [P2P9][159.118.166.237:37699 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:55:08.077972 [P2P8]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:55:08.083972 [P2P8][182.161.177.27:5907 INC]Block verification failed, dropping connection
2014-Aug-19 12:55:08.200979 [P2P7]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:55:08.207979 [P2P7][109.197.253.113:56972 INC]Block verification failed, dropping connection
2014-Aug-19 12:55:14.639347 [P2P4][124.121.82.93:56615 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:55:22.606803 [P2P9]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:55:22.612803 [P2P9][159.118.166.237:37699 INC]Block verification failed, dropping connection
2014-Aug-19 12:55:23.095831 [P2P1][86.9.233.2:18171 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:55:23.958880 [P2P4]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:55:23.964880 [P2P4][124.121.82.93:56615 INC]Block verification failed, dropping connection
2014-Aug-19 12:55:45.080088 [P2P8]ERROR c:\projects\sorrybigbro\contrib\epee\include\net\levin_protocol_handler_async.h:440 [127.0.0.1:49187 INC]Signature mismatch, connection will be closed
2014-Aug-19 12:55:45.087089 [P2P8]ERROR c:\projects\sorrybigbro\contrib\epee\include\net\levin_protocol_handler_async.h:440 [127.0.0.1:49188 INC]Signature mismatch, connection will be closed
2014-Aug-19 12:55:51.152435 [P2P5]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:55:51.158436 [P2P5][86.9.233.2:18171 INC]Block verification failed, dropping connection
2014-Aug-19 12:56:51.446884 [P2P0][sock 816] Some problems at write: An existing connection was forcibly closed by the remote host:10054
2014-Aug-19 12:57:15.676270 [P2P9][sock 468] Some problems at write: An existing connection was forcibly closed by the remote host:10054
2014-Aug-19 12:57:27.175928 [P2P3][216.8.146.119:58730 INC]Sync data returned unknown top block: 548786 -> 546611 [2175 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:57:35.750418 [P2P4]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:57:35.756418 [P2P4][216.8.146.119:58730 INC]Block verification failed, dropping connection
2014-Aug-19 12:57:38.458573 [P2P6][109.197.253.113:57051 INC]Sync data returned unknown top block: 548786 -> 546611 [2175 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:57:49.636212 [P2P0]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:57:49.643213 [P2P0][109.197.253.113:57051 INC]Block verification failed, dropping connection
2014-Aug-19 12:57:51.929344 [P2P2][sock 844] Some problems at write: An existing connection was forcibly closed by the remote host:10054
2014-Aug-19 12:57:54.616497 [P2P2][159.118.166.237:37746 INC]Sync data returned unknown top block: 548787 -> 546611 [2176 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:57:56.347596 [P2P1][182.161.177.27:8080 OUT]Sync data returned unknown top block: 548787 -> 546611 [2176 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:58:01.011863 [P2P6][sock 820] Some problems at write: An existing connection was forcibly closed by the remote host:10054
2014-Aug-19 12:58:02.880970 [P2P6]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:58:02.886970 [P2P6][182.161.177.27:8080 OUT]Block verification failed, dropping connection
2014-Aug-19 12:58:07.111212 [P2P1][124.121.82.93:56661 INC]Sync data returned unknown top block: 548787 -> 546611 [2176 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:58:10.099383 [P2P3]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:58:10.106383 [P2P3][159.118.166.237:37746 INC]Block verification failed, dropping connection
2014-Aug-19 12:58:14.305623 [P2P2][109.197.253.113:57080 INC]Sync data returned unknown top block: 548787 -> 546611 [2176 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:58:14.843654 [P2P0]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:58:14.850655 [P2P0][124.121.82.93:56661 INC]Block verification failed, dropping connection
2014-Aug-19 12:58:18.823882 [P2P3]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:58:18.829882 [P2P3][109.197.253.113:57080 INC]Block verification failed, dropping connection
Rias
Sr. Member
****
Offline Offline

Activity: 373
Merit: 250


View Profile
August 19, 2014, 10:07:44 AM
 #3662
Quote from: saYRam on August 19, 2014, 10:01:22 AM
Quote from: Rytir_fik on August 19, 2014, 08:44:43 AM
Quote from: saYRam on August 19, 2014, 08:29:27 AM

couldnt syncronized. I get this messages. Whats wrong with it?

win7 x64 en (7600)
i7 2600k
do you use the last binary 1.0.1? If not update it. https://bitcointalk.org/index.php?topic=512747.msg8351704#msg8351704

cur version is v1.0.1.316 for deamon and wallet.

See the new logs. I can see
2014-Aug-19 12:51:48.788573 [P2P9][95.211.224.150:8080 OUT] SYNCHRONIZED OK
but news lines weird. Cant refresh the wallet and demon always go on "SYNCHRONIZATION started" err lines "SYNCHRONIZATION started" err lines.

btw i use this command to start deamon

Code:
bytecoind --rpc-bind-port=8080 --p2p-bind-port=8081

ty for ur answer.

Code:
2014-Aug-19 12:50:12.985093 bytecoin v1.0.1.316()
2014-Aug-19 12:50:12.986093 Module folder: bytecoind
2014-Aug-19 12:50:12.988094 Initializing p2p server...
2014-Aug-19 12:50:13.199106 Binding on 0.0.0.0:8081
2014-Aug-19 12:50:13.201106 Net service binded on 0.0.0.0:8081
2014-Aug-19 12:50:13.203106 Attempting to add IGD port mapping.
2014-Aug-19 12:50:14.226164 Added IGD port mapping.
2014-Aug-19 12:50:14.229165 P2p server initialized OK
2014-Aug-19 12:50:14.230165 Initializing cryptonote protocol...
2014-Aug-19 12:50:14.232165 Cryptonote protocol initialized OK
2014-Aug-19 12:50:14.234165 Initializing core rpc server...
2014-Aug-19 12:50:14.235165 Binding on 127.0.0.1:8080
2014-Aug-19 12:50:14.237165 Core rpc server initialized OK on port: 8080
2014-Aug-19 12:50:14.239165 Initializing core...
2014-Aug-19 12:50:14.271167 Loading blockchain...
2014-Aug-19 12:50:14.274167 No actual blockchain cache found, rebuilding internal structures...
2014-Aug-19 12:51:46.092419 Rebuilding internal structures took: 91.8153
2014-Aug-19 12:51:46.240427 Blockchain initialized. last block: 548780, d0.h0.m9.s4 time ago, current difficulty: 76912305
2014-Aug-19 12:51:46.350434 Core initialized OK
2014-Aug-19 12:51:46.352434 Starting core rpc server...
2014-Aug-19 12:51:46.354434 Run net_service loop( 2 threads)...
2014-Aug-19 12:51:46.366435 [SRV_MAIN]Core rpc server started ok
2014-Aug-19 12:51:46.369435 [SRV_MAIN]Starting p2p net loop...
2014-Aug-19 12:51:46.371435 [SRV_MAIN]Run net_service loop( 10 threads)...
2014-Aug-19 12:51:46.393436 [P2P1][27.72.105.127:17026 INC]Sync data returned unknown top block: 548781 -> 548785 [4 blocks (0 days) behind] 
SYNCHRONIZATION started
2014-Aug-19 12:51:46.393436 [P2P2][124.121.82.93:56540 INC]Sync data returned unknown top block: 548781 -> 546611 [2170 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:51:46.393436 [P2P3][109.197.253.113:56853 INC]Sync data returned unknown top block: 548781 -> 546611 [2170 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:51:46.393436 [P2P0][216.8.146.119:57880 INC]Sync data returned unknown top block: 548781 -> 546611 [2170 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:51:47.371492 [P2P0]
**********************************************************************
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>" command*, where <level> is between 0 (no details) and 4 (very verbose).

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

Note: in case you need to interrupt the process, use "exit" command. Otherwise, the current progress won't be saved.
**********************************************************************
2014-Aug-19 12:51:47.633507 [P2P7][95.211.224.150:8080 OUT]Sync data returned unknown top block: 548781 -> 548785 [4 blocks (0 days) behind] 
SYNCHRONIZATION started
2014-Aug-19 12:51:48.788573 [P2P9][95.211.224.150:8080 OUT] SYNCHRONIZED OK
2014-Aug-19 12:51:48.791573 [P2P9]
**********************************************************************
You are now synchronized with the network. You may now start simplewallet.

Please note, that the blockchain will be saved only after you quit the daemon with "exit" command or if you use "save" command.
Otherwise, you will possibly need to synchronize the blockchain again.

Use "help" command to see the list of available commands.
**********************************************************************
2014-Aug-19 12:52:13.148966 [P2P2][86.9.233.2:18063 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:52:20.314376 [P2P7][216.8.146.119:58041 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:52:29.477900 [P2P9]----- BLOCK ADDED AS ALTERNATIVE ON HEIGHT 546603
id:	<91e836cd2a9b30a32a3858f2f9162a3453a7d96747c3ef993c8c07a9a3e52d67>
PoW:	<82b6f74a4c92bd28cce4d2eeac96f202110b0af9528ab4f44e11271f05000000>
difficulty:	95882153
2014-Aug-19 12:52:29.489901 [P2P9]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:52:29.494901 [P2P9][216.8.146.119:58041 INC]Block verification failed, dropping connection
2014-Aug-19 12:52:47.196914 [P2P7][124.121.82.93:56576 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:52:57.445500 [P2P5]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:52:57.451500 [P2P5][124.121.82.93:56576 INC]Block verification failed, dropping connection
2014-Aug-19 12:53:02.879811 [P2P9]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:53:02.885811 [P2P9][86.9.233.2:18063 INC]Block verification failed, dropping connection
2014-Aug-19 12:53:15.001504 [P2P6][109.197.253.113:56921 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:53:27.092196 [P2P2]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:53:27.099196 [P2P2][109.197.253.113:56921 INC]Block verification failed, dropping connection
2014-Aug-19 12:53:33.732576 [P2P0][159.118.166.237:37672 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:53:40.068938 [P2P8]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:53:40.075938 [P2P8][159.118.166.237:37672 INC]Block verification failed, dropping connection
2014-Aug-19 12:53:46.972333 [P2P7][182.161.177.27:5892 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:53:55.358812 [P2P3]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:53:55.365813 [P2P3][182.161.177.27:5892 INC]Block verification failed, dropping connection
2014-Aug-19 12:54:21.811325 [P2P7]ERROR c:\projects\sorrybigbro\contrib\epee\include\net\levin_protocol_handler_async.h:440 [127.0.0.1:65524 INC]Signature mismatch, connection will be closed
2014-Aug-19 12:54:21.827326 [P2P5]ERROR c:\projects\sorrybigbro\contrib\epee\include\net\levin_protocol_handler_async.h:440 [127.0.0.1:65525 INC]Signature mismatch, connection will be closed
2014-Aug-19 12:54:25.681547 [P2P4][159.118.166.237:37689 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:54:30.474821 [P2P8]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:54:30.481821 [P2P8][159.118.166.237:37689 INC]Block verification failed, dropping connection
2014-Aug-19 12:54:32.626944 [P2P3][216.8.146.119:58348 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:54:41.221436 [P2P1]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:54:41.228436 [P2P1][216.8.146.119:58348 INC]Block verification failed, dropping connection
2014-Aug-19 12:54:45.137660 [P2P9][182.161.177.27:5902 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:54:51.038997 [P2P2]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:54:51.045998 [P2P2][182.161.177.27:5902 INC]Block verification failed, dropping connection
2014-Aug-19 12:54:56.352301 [P2P7][109.197.253.113:56972 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:55:00.212522 [P2P1][182.161.177.27:5907 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:55:06.343873 [P2P9][159.118.166.237:37699 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:55:08.077972 [P2P8]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:55:08.083972 [P2P8][182.161.177.27:5907 INC]Block verification failed, dropping connection
2014-Aug-19 12:55:08.200979 [P2P7]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:55:08.207979 [P2P7][109.197.253.113:56972 INC]Block verification failed, dropping connection
2014-Aug-19 12:55:14.639347 [P2P4][124.121.82.93:56615 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:55:22.606803 [P2P9]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:55:22.612803 [P2P9][159.118.166.237:37699 INC]Block verification failed, dropping connection
2014-Aug-19 12:55:23.095831 [P2P1][86.9.233.2:18171 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:55:23.958880 [P2P4]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:55:23.964880 [P2P4][124.121.82.93:56615 INC]Block verification failed, dropping connection
2014-Aug-19 12:55:45.080088 [P2P8]ERROR c:\projects\sorrybigbro\contrib\epee\include\net\levin_protocol_handler_async.h:440 [127.0.0.1:49187 INC]Signature mismatch, connection will be closed
2014-Aug-19 12:55:45.087089 [P2P8]ERROR c:\projects\sorrybigbro\contrib\epee\include\net\levin_protocol_handler_async.h:440 [127.0.0.1:49188 INC]Signature mismatch, connection will be closed
2014-Aug-19 12:55:51.152435 [P2P5]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:55:51.158436 [P2P5][86.9.233.2:18171 INC]Block verification failed, dropping connection
2014-Aug-19 12:56:51.446884 [P2P0][sock 816] Some problems at write: An existing connection was forcibly closed by the remote host:10054
2014-Aug-19 12:57:15.676270 [P2P9][sock 468] Some problems at write: An existing connection was forcibly closed by the remote host:10054
2014-Aug-19 12:57:27.175928 [P2P3][216.8.146.119:58730 INC]Sync data returned unknown top block: 548786 -> 546611 [2175 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:57:35.750418 [P2P4]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:57:35.756418 [P2P4][216.8.146.119:58730 INC]Block verification failed, dropping connection
2014-Aug-19 12:57:38.458573 [P2P6][109.197.253.113:57051 INC]Sync data returned unknown top block: 548786 -> 546611 [2175 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:57:49.636212 [P2P0]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:57:49.643213 [P2P0][109.197.253.113:57051 INC]Block verification failed, dropping connection
2014-Aug-19 12:57:51.929344 [P2P2][sock 844] Some problems at write: An existing connection was forcibly closed by the remote host:10054
2014-Aug-19 12:57:54.616497 [P2P2][159.118.166.237:37746 INC]Sync data returned unknown top block: 548787 -> 546611 [2176 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:57:56.347596 [P2P1][182.161.177.27:8080 OUT]Sync data returned unknown top block: 548787 -> 546611 [2176 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:58:01.011863 [P2P6][sock 820] Some problems at write: An existing connection was forcibly closed by the remote host:10054
2014-Aug-19 12:58:02.880970 [P2P6]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:58:02.886970 [P2P6][182.161.177.27:8080 OUT]Block verification failed, dropping connection
2014-Aug-19 12:58:07.111212 [P2P1][124.121.82.93:56661 INC]Sync data returned unknown top block: 548787 -> 546611 [2176 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:58:10.099383 [P2P3]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:58:10.106383 [P2P3][159.118.166.237:37746 INC]Block verification failed, dropping connection
2014-Aug-19 12:58:14.305623 [P2P2][109.197.253.113:57080 INC]Sync data returned unknown top block: 548787 -> 546611 [2176 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:58:14.843654 [P2P0]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:58:14.850655 [P2P0][124.121.82.93:56661 INC]Block verification failed, dropping connection
2014-Aug-19 12:58:18.823882 [P2P3]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:58:18.829882 [P2P3][109.197.253.113:57080 INC]Block verification failed, dropping connection


This has been discussed already: https://bitcointalk.org/index.php?topic=512747.msg8403069#msg8403069

Your daemon is totally ok. It is synchronized. However, there are some daemons that are outdated and send invalid data. If you check the top block your daemon is trying to synchronize to, it's way below your current one (by more than 2000 blocks), so the connection to the outdated daemon is dropped and nothing happens. As there are might several older daemons you keep receiving such messages.

However, the software works fine, just give it a try in your wallet.
creepywheepy
Member
**
Offline Offline

Activity: 87
Merit: 10


View Profile
August 19, 2014, 10:19:34 AM
 #3663
Hello! What are the advantages of the multi-signature technology being included in BCN framework?
Donations - d5737925-d46d-47ec-9941-94a12a68861b
cyrpi4
Member
**
Offline Offline

Activity: 85
Merit: 10


View Profile
August 19, 2014, 10:23:09 AM
 #3664
Quote from: Rias on August 19, 2014, 10:07:44 AM
Quote from: saYRam on August 19, 2014, 10:01:22 AM
Quote from: Rytir_fik on August 19, 2014, 08:44:43 AM
Quote from: saYRam on August 19, 2014, 08:29:27 AM

couldnt syncronized. I get this messages. Whats wrong with it?

win7 x64 en (7600)
i7 2600k
do you use the last binary 1.0.1? If not update it. https://bitcointalk.org/index.php?topic=512747.msg8351704#msg8351704

cur version is v1.0.1.316 for deamon and wallet.

See the new logs. I can see
2014-Aug-19 12:51:48.788573 [P2P9][95.211.224.150:8080 OUT] SYNCHRONIZED OK
but news lines weird. Cant refresh the wallet and demon always go on "SYNCHRONIZATION started" err lines "SYNCHRONIZATION started" err lines.

btw i use this command to start deamon

Code:
bytecoind --rpc-bind-port=8080 --p2p-bind-port=8081

ty for ur answer.

Code:
2014-Aug-19 12:50:12.985093 bytecoin v1.0.1.316()
2014-Aug-19 12:50:12.986093 Module folder: bytecoind
2014-Aug-19 12:50:12.988094 Initializing p2p server...
2014-Aug-19 12:50:13.199106 Binding on 0.0.0.0:8081
2014-Aug-19 12:50:13.201106 Net service binded on 0.0.0.0:8081
2014-Aug-19 12:50:13.203106 Attempting to add IGD port mapping.
2014-Aug-19 12:50:14.226164 Added IGD port mapping.
2014-Aug-19 12:50:14.229165 P2p server initialized OK
2014-Aug-19 12:50:14.230165 Initializing cryptonote protocol...
2014-Aug-19 12:50:14.232165 Cryptonote protocol initialized OK
2014-Aug-19 12:50:14.234165 Initializing core rpc server...
2014-Aug-19 12:50:14.235165 Binding on 127.0.0.1:8080
2014-Aug-19 12:50:14.237165 Core rpc server initialized OK on port: 8080
2014-Aug-19 12:50:14.239165 Initializing core...
2014-Aug-19 12:50:14.271167 Loading blockchain...
2014-Aug-19 12:50:14.274167 No actual blockchain cache found, rebuilding internal structures...
2014-Aug-19 12:51:46.092419 Rebuilding internal structures took: 91.8153
2014-Aug-19 12:51:46.240427 Blockchain initialized. last block: 548780, d0.h0.m9.s4 time ago, current difficulty: 76912305
2014-Aug-19 12:51:46.350434 Core initialized OK
2014-Aug-19 12:51:46.352434 Starting core rpc server...
2014-Aug-19 12:51:46.354434 Run net_service loop( 2 threads)...
2014-Aug-19 12:51:46.366435 [SRV_MAIN]Core rpc server started ok
2014-Aug-19 12:51:46.369435 [SRV_MAIN]Starting p2p net loop...
2014-Aug-19 12:51:46.371435 [SRV_MAIN]Run net_service loop( 10 threads)...
2014-Aug-19 12:51:46.393436 [P2P1][27.72.105.127:17026 INC]Sync data returned unknown top block: 548781 -> 548785 [4 blocks (0 days) behind] 
SYNCHRONIZATION started
2014-Aug-19 12:51:46.393436 [P2P2][124.121.82.93:56540 INC]Sync data returned unknown top block: 548781 -> 546611 [2170 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:51:46.393436 [P2P3][109.197.253.113:56853 INC]Sync data returned unknown top block: 548781 -> 546611 [2170 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:51:46.393436 [P2P0][216.8.146.119:57880 INC]Sync data returned unknown top block: 548781 -> 546611 [2170 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:51:47.371492 [P2P0]
**********************************************************************
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>" command*, where <level> is between 0 (no details) and 4 (very verbose).

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

Note: in case you need to interrupt the process, use "exit" command. Otherwise, the current progress won't be saved.
**********************************************************************
2014-Aug-19 12:51:47.633507 [P2P7][95.211.224.150:8080 OUT]Sync data returned unknown top block: 548781 -> 548785 [4 blocks (0 days) behind] 
SYNCHRONIZATION started
2014-Aug-19 12:51:48.788573 [P2P9][95.211.224.150:8080 OUT] SYNCHRONIZED OK
2014-Aug-19 12:51:48.791573 [P2P9]
**********************************************************************
You are now synchronized with the network. You may now start simplewallet.

Please note, that the blockchain will be saved only after you quit the daemon with "exit" command or if you use "save" command.
Otherwise, you will possibly need to synchronize the blockchain again.

Use "help" command to see the list of available commands.
**********************************************************************
2014-Aug-19 12:52:13.148966 [P2P2][86.9.233.2:18063 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:52:20.314376 [P2P7][216.8.146.119:58041 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:52:29.477900 [P2P9]----- BLOCK ADDED AS ALTERNATIVE ON HEIGHT 546603
id:	<91e836cd2a9b30a32a3858f2f9162a3453a7d96747c3ef993c8c07a9a3e52d67>
PoW:	<82b6f74a4c92bd28cce4d2eeac96f202110b0af9528ab4f44e11271f05000000>
difficulty:	95882153
2014-Aug-19 12:52:29.489901 [P2P9]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:52:29.494901 [P2P9][216.8.146.119:58041 INC]Block verification failed, dropping connection
2014-Aug-19 12:52:47.196914 [P2P7][124.121.82.93:56576 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:52:57.445500 [P2P5]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:52:57.451500 [P2P5][124.121.82.93:56576 INC]Block verification failed, dropping connection
2014-Aug-19 12:53:02.879811 [P2P9]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:53:02.885811 [P2P9][86.9.233.2:18063 INC]Block verification failed, dropping connection
2014-Aug-19 12:53:15.001504 [P2P6][109.197.253.113:56921 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:53:27.092196 [P2P2]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:53:27.099196 [P2P2][109.197.253.113:56921 INC]Block verification failed, dropping connection
2014-Aug-19 12:53:33.732576 [P2P0][159.118.166.237:37672 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:53:40.068938 [P2P8]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:53:40.075938 [P2P8][159.118.166.237:37672 INC]Block verification failed, dropping connection
2014-Aug-19 12:53:46.972333 [P2P7][182.161.177.27:5892 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:53:55.358812 [P2P3]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:53:55.365813 [P2P3][182.161.177.27:5892 INC]Block verification failed, dropping connection
2014-Aug-19 12:54:21.811325 [P2P7]ERROR c:\projects\sorrybigbro\contrib\epee\include\net\levin_protocol_handler_async.h:440 [127.0.0.1:65524 INC]Signature mismatch, connection will be closed
2014-Aug-19 12:54:21.827326 [P2P5]ERROR c:\projects\sorrybigbro\contrib\epee\include\net\levin_protocol_handler_async.h:440 [127.0.0.1:65525 INC]Signature mismatch, connection will be closed
2014-Aug-19 12:54:25.681547 [P2P4][159.118.166.237:37689 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:54:30.474821 [P2P8]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:54:30.481821 [P2P8][159.118.166.237:37689 INC]Block verification failed, dropping connection
2014-Aug-19 12:54:32.626944 [P2P3][216.8.146.119:58348 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:54:41.221436 [P2P1]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:54:41.228436 [P2P1][216.8.146.119:58348 INC]Block verification failed, dropping connection
2014-Aug-19 12:54:45.137660 [P2P9][182.161.177.27:5902 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:54:51.038997 [P2P2]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:54:51.045998 [P2P2][182.161.177.27:5902 INC]Block verification failed, dropping connection
2014-Aug-19 12:54:56.352301 [P2P7][109.197.253.113:56972 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:55:00.212522 [P2P1][182.161.177.27:5907 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:55:06.343873 [P2P9][159.118.166.237:37699 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:55:08.077972 [P2P8]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:55:08.083972 [P2P8][182.161.177.27:5907 INC]Block verification failed, dropping connection
2014-Aug-19 12:55:08.200979 [P2P7]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:55:08.207979 [P2P7][109.197.253.113:56972 INC]Block verification failed, dropping connection
2014-Aug-19 12:55:14.639347 [P2P4][124.121.82.93:56615 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:55:22.606803 [P2P9]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:55:22.612803 [P2P9][159.118.166.237:37699 INC]Block verification failed, dropping connection
2014-Aug-19 12:55:23.095831 [P2P1][86.9.233.2:18171 INC]Sync data returned unknown top block: 548785 -> 546611 [2174 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:55:23.958880 [P2P4]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:55:23.964880 [P2P4][124.121.82.93:56615 INC]Block verification failed, dropping connection
2014-Aug-19 12:55:45.080088 [P2P8]ERROR c:\projects\sorrybigbro\contrib\epee\include\net\levin_protocol_handler_async.h:440 [127.0.0.1:49187 INC]Signature mismatch, connection will be closed
2014-Aug-19 12:55:45.087089 [P2P8]ERROR c:\projects\sorrybigbro\contrib\epee\include\net\levin_protocol_handler_async.h:440 [127.0.0.1:49188 INC]Signature mismatch, connection will be closed
2014-Aug-19 12:55:51.152435 [P2P5]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:55:51.158436 [P2P5][86.9.233.2:18171 INC]Block verification failed, dropping connection
2014-Aug-19 12:56:51.446884 [P2P0][sock 816] Some problems at write: An existing connection was forcibly closed by the remote host:10054
2014-Aug-19 12:57:15.676270 [P2P9][sock 468] Some problems at write: An existing connection was forcibly closed by the remote host:10054
2014-Aug-19 12:57:27.175928 [P2P3][216.8.146.119:58730 INC]Sync data returned unknown top block: 548786 -> 546611 [2175 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:57:35.750418 [P2P4]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:57:35.756418 [P2P4][216.8.146.119:58730 INC]Block verification failed, dropping connection
2014-Aug-19 12:57:38.458573 [P2P6][109.197.253.113:57051 INC]Sync data returned unknown top block: 548786 -> 546611 [2175 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:57:49.636212 [P2P0]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:57:49.643213 [P2P0][109.197.253.113:57051 INC]Block verification failed, dropping connection
2014-Aug-19 12:57:51.929344 [P2P2][sock 844] Some problems at write: An existing connection was forcibly closed by the remote host:10054
2014-Aug-19 12:57:54.616497 [P2P2][159.118.166.237:37746 INC]Sync data returned unknown top block: 548787 -> 546611 [2176 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:57:56.347596 [P2P1][182.161.177.27:8080 OUT]Sync data returned unknown top block: 548787 -> 546611 [2176 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:58:01.011863 [P2P6][sock 820] Some problems at write: An existing connection was forcibly closed by the remote host:10054
2014-Aug-19 12:58:02.880970 [P2P6]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:58:02.886970 [P2P6][182.161.177.27:8080 OUT]Block verification failed, dropping connection
2014-Aug-19 12:58:07.111212 [P2P1][124.121.82.93:56661 INC]Sync data returned unknown top block: 548787 -> 546611 [2176 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:58:10.099383 [P2P3]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:58:10.106383 [P2P3][159.118.166.237:37746 INC]Block verification failed, dropping connection
2014-Aug-19 12:58:14.305623 [P2P2][109.197.253.113:57080 INC]Sync data returned unknown top block: 548787 -> 546611 [2176 blocks (25620477880152152 days) ahead] 
SYNCHRONIZATION started
2014-Aug-19 12:58:14.843654 [P2P0]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:58:14.850655 [P2P0][124.121.82.93:56661 INC]Block verification failed, dropping connection
2014-Aug-19 12:58:18.823882 [P2P3]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 12:58:18.829882 [P2P3][109.197.253.113:57080 INC]Block verification failed, dropping connection


This has been discussed already: https://bitcointalk.org/index.php?topic=512747.msg8403069#msg8403069

Your daemon is totally ok. It is synchronized. However, there are some daemons that are outdated and send invalid data. If you check the top block your daemon is trying to synchronize to, it's way below your current one (by more than 2000 blocks), so the connection to the outdated daemon is dropped and nothing happens. As there are might several older daemons you keep receiving such messages.

However, the software works fine, just give it a try in your wallet.


So, the problem is not in new bin files? It's in the old ver of daemon?   
Donations: 2235fa09-d5b3-4d5d-9b28-d1281abc1ccb
saYRam
Newbie
*
Offline Offline

Activity: 19
Merit: 0


View Profile
August 19, 2014, 10:34:02 AM
 #3665
Quote from: Rias on August 19, 2014, 10:07:44 AM
Quote from: saYRam on August 19, 2014, 10:01:22 AM
Quote from: Rytir_fik on August 19, 2014, 08:44:43 AM
Quote from: saYRam on August 19, 2014, 08:29:27 AM

couldnt syncronized. I get this messages. Whats wrong with it?

win7 x64 en (7600)
i7 2600k
do you use the last binary 1.0.1? If not update it. https://bitcointalk.org/index.php?topic=512747.msg8351704#msg8351704

cur version is v1.0.1.316 for deamon and wallet.

See the new logs. I can see
2014-Aug-19 12:51:48.788573 [P2P9][95.211.224.150:8080 OUT] SYNCHRONIZED OK
but news lines weird. Cant refresh the wallet and demon always go on "SYNCHRONIZATION started" err lines "SYNCHRONIZATION started" err lines.

btw i use this command to start deamon

Code:
bytecoind --rpc-bind-port=8080 --p2p-bind-port=8081

ty for ur answer.

Code:

**********************************************************************
2014-Aug-19 12:51:47.633507 [P2P7][95.211.224.150:8080 OUT]Sync data returned unknown top block: 548781 -> 548785 [4 blocks (0 days) behind] 
SYNCHRONIZATION started
2014-Aug-19 12:51:48.788573 [P2P9][95.211.224.150:8080 OUT] SYNCHRONIZED OK
2014-Aug-19 12:51:48.791573 [P2P9]
**********************************************************************


This has been discussed already: https://bitcointalk.org/index.php?topic=512747.msg8403069#msg8403069

Your daemon is totally ok. It is synchronized. However, there are some daemons that are outdated and send invalid data. If you check the top block your daemon is trying to synchronize to, it's way below your current one (by more than 2000 blocks), so the connection to the outdated daemon is dropped and nothing happens. As there are might several older daemons you keep receiving such messages.

However, the software works fine, just give it a try in your wallet.

so we have to wait now?

and in the update msg it says delete your wallet.bin file.

isnt it my wallet? why i have to delete it?
tyvm for ur attention.
Meggie
Member
**
Offline Offline

Activity: 78
Merit: 10


View Profile
August 19, 2014, 10:34:27 AM
 #3666
Quote from: creepywheepy on August 19, 2014, 10:19:34 AM
Hello! What are the advantages of the multi-signature technology being included in BCN framework?

You're so random.
Get Free Bitcoins -->>BitcoInvest
SimpleMachines
Newbie
*
Offline Offline

Activity: 27
Merit: 0


View Profile
August 19, 2014, 10:39:54 AM
 #3667
Quote from: creepywheepy on August 19, 2014, 10:19:34 AM
Hello! What are the advantages of the multi-signature technology being included in BCN framework?

The implementation of multi-signature technology allows for development of higher security wallets that will , probably, increase the interest from wider audience of people involved in crypto currency world, in other words, it will increase the  number of exchanges, stores and services accepting BCN.
creepywheepy
Member
**
Offline Offline

Activity: 87
Merit: 10


View Profile
August 19, 2014, 10:57:30 AM
 #3668
Quote from: Meggie on August 19, 2014, 10:34:27 AM
Quote from: creepywheepy on August 19, 2014, 10:19:34 AM
Hello! What are the advantages of the multi-signature technology being included in BCN framework?

You're so random.

What do you mean?  I didn't understand you.

Quote from: SimpleMachines on August 19, 2014, 10:39:54 AM
Quote from: creepywheepy on August 19, 2014, 10:19:34 AM
Hello! What are the advantages of the multi-signature technology being included in BCN framework?

The implementation of multi-signature technology allows for development of higher security wallets that will , probably, increase the interest from wider audience of people involved in crypto currency world, in other words, it will increase the  number of exchanges, stores and services accepting BCN.

Well, these are good reasons to implement it in BCN code. Glad to know that they've made such decision and looking forward to see more exchanges and services accepting BCN
Donations - d5737925-d46d-47ec-9941-94a12a68861b
SimpleMachines
Newbie
*
Offline Offline

Activity: 27
Merit: 0


View Profile
August 19, 2014, 10:59:47 AM
 #3669
Quote from: creepywheepy on August 19, 2014, 10:57:30 AM
Quote from: Meggie on August 19, 2014, 10:34:27 AM
Quote from: creepywheepy on August 19, 2014, 10:19:34 AM
Hello! What are the advantages of the multi-signature technology being included in BCN framework?

You're so random.

What do you mean?  I didn't understand you.

Quote from: SimpleMachines on August 19, 2014, 10:39:54 AM
Quote from: creepywheepy on August 19, 2014, 10:19:34 AM
Hello! What are the advantages of the multi-signature technology being included in BCN framework?

The implementation of multi-signature technology allows for development of higher security wallets that will , probably, increase the interest from wider audience of people involved in crypto currency world, in other words, it will increase the  number of exchanges, stores and services accepting BCN.

Well, these are good reasons to implement it in BCN code. Glad to know that they've made such decision and looking forward to see more exchanges and services accepting BCN

That's gonna happen soon. Keep calm! Rome wasn't built in a day  Smiley
creepywheepy
Member
**
Offline Offline

Activity: 87
Merit: 10


View Profile
August 19, 2014, 11:08:55 AM
 #3670
Quote from: SimpleMachines on August 19, 2014, 10:59:47 AM
Quote from: creepywheepy on August 19, 2014, 10:57:30 AM
Quote from: Meggie on August 19, 2014, 10:34:27 AM
Quote from: creepywheepy on August 19, 2014, 10:19:34 AM
Hello! What are the advantages of the multi-signature technology being included in BCN framework?

You're so random.

What do you mean?  I didn't understand you.

Quote from: SimpleMachines on August 19, 2014, 10:39:54 AM
Quote from: creepywheepy on August 19, 2014, 10:19:34 AM
Hello! What are the advantages of the multi-signature technology being included in BCN framework?

The implementation of multi-signature technology allows for development of higher security wallets that will , probably, increase the interest from wider audience of people involved in crypto currency world, in other words, it will increase the  number of exchanges, stores and services accepting BCN.

Well, these are good reasons to implement it in BCN code. Glad to know that they've made such decision and looking forward to see more exchanges and services accepting BCN

That's gonna happen soon. Keep calm! Rome wasn't built in a day  Smiley

 Grin You are absolutely right, Roma wasn't built in a day! I'll try to be calm and believe in a better future
Donations - d5737925-d46d-47ec-9941-94a12a68861b
Rias
Sr. Member
****
Offline Offline

Activity: 373
Merit: 250


View Profile
August 19, 2014, 11:17:26 AM
 #3671
Quote from: saYRam on August 19, 2014, 10:34:02 AM
Quote from: Rias on August 19, 2014, 10:07:44 AM
This has been discussed already: https://bitcointalk.org/index.php?topic=512747.msg8403069#msg8403069

Your daemon is totally ok. It is synchronized. However, there are some daemons that are outdated and send invalid data. If you check the top block your daemon is trying to synchronize to, it's way below your current one (by more than 2000 blocks), so the connection to the outdated daemon is dropped and nothing happens. As there are might several older daemons you keep receiving such messages.

However, the software works fine, just give it a try in your wallet.

so we have to wait now?

The devs promised to move it to a lower loggin level as there's totally nothing bad about these messages.
https://bitcointalk.org/index.php?topic=512747.msg8403069#msg8403069

Alternatively, the older daemons may be eventually updated and the problem will disappear.

Quote
and in the update msg it says delete your wallet.bin file.

isnt it my wallet? why i have to delete it?
tyvm for ur attention.

I think this message was regarding moving from daemon v.1.0.0 to v.1.0.1. You should delete "wallet.bin" file in case you suspect that something is wrong with the balance or your transactions can't be sent. Otherwise, you should be good.

"Wallet.bin" stands for your wallet name. If you've called it "my-wallet", then you have to delete "my-wallet.bin" file. However, do not delete the .keys file or you'll delete your wallet.
madzooka
Full Member
***
Offline Offline

Activity: 150
Merit: 100


View Profile
August 19, 2014, 11:20:05 AM
 #3672
Quote from: Hexah on August 18, 2014, 02:19:18 PM
Quote from: cryptrol on August 18, 2014, 09:51:57 AM
It seems that there is someone out there with an enormous amount of hashing power.


This screencap is taken from Minergate.


Quote from: smooth on August 18, 2014, 02:03:56 PM
Quote from: restless on August 18, 2014, 10:51:06 AM
His hashrate is equivalent of 1000 Radeon 290.... or 6000 intel haswell cores

Most likely explanation is a botnet.

I read that the devs of BCN use botnet to make fake demand for this coin. Is it true ?



Nope, it's Monero botnet is mining Monero as usual:




That's not the first time Monero developers use botnet and instamine coins
Bytecoin (BCN) - true anonymity, privacy protection and only CPU-mining

Bytecoin address - 21eQrEa2wVcdnf8viyaDu78anS4aX3Kvqiyidan25UBCWRokFoTpAHk6hduLR1oBeJ7Map75dCQv4an r2meEiH4wKc1tbQh
creepywheepy
Member
**
Offline Offline

Activity: 87
Merit: 10


View Profile
August 19, 2014, 11:21:50 AM
 #3673
Quote from: madzooka on August 19, 2014, 11:20:05 AM
Quote from: Hexah on August 18, 2014, 02:19:18 PM
Quote from: cryptrol on August 18, 2014, 09:51:57 AM
It seems that there is someone out there with an enormous amount of hashing power.


This screencap is taken from Minergate.


Quote from: smooth on August 18, 2014, 02:03:56 PM
Quote from: restless on August 18, 2014, 10:51:06 AM
His hashrate is equivalent of 1000 Radeon 290.... or 6000 intel haswell cores

Most likely explanation is a botnet.

I read that the devs of BCN use botnet to make fake demand for this coin. Is it true ?



Nope, it's Monero botnet is mining Monero as usual:




That's not the first time Monero developers use botnet and instamine coins

Seriously ?? I haven't heard about it - any links?
Donations - d5737925-d46d-47ec-9941-94a12a68861b
madzooka
Full Member
***
Offline Offline

Activity: 150
Merit: 100


View Profile
August 19, 2014, 11:35:30 AM
 #3674
That was discussed a long ago on Monero thread  - https://bitcointalk.org/index.php?topic=583449.msg6593768#msg6593768 
Note there was Hexah and he was absolutely right in his arguments and until he and other guys made some noise monero devs were not thinking about sharing theire optimizer with the usual miners
Bytecoin (BCN) - true anonymity, privacy protection and only CPU-mining

Bytecoin address - 21eQrEa2wVcdnf8viyaDu78anS4aX3Kvqiyidan25UBCWRokFoTpAHk6hduLR1oBeJ7Map75dCQv4an r2meEiH4wKc1tbQh
fluffypony
Donator
Legendary
*
Offline Offline

Activity: 1274
Merit: 1060


GetMonero.org / MyMonero.com


View Profile WWW
August 19, 2014, 12:27:53 PM
 #3675
Quote from: madzooka on August 19, 2014, 11:35:30 AM
That was discussed a long ago on Monero thread  - https://bitcointalk.org/index.php?topic=583449.msg6593768#msg6593768 
Note there was Hexah and he was absolutely right in his arguments and until he and other guys made some noise monero devs were not thinking about sharing theire optimizer with the usual miners

Talk about resurrecting an old topic for the sake of spewing nonsense;)

Start here: https://bitcointalk.org/index.php?topic=583449.msg6597057#msg6597057

NoodleDoodle released the binaries in public on IRC. His changes were subsequently submitted as a pull request and committed. All of this happened in the space of 36 hours (between May 6th and May 7th). He was under no obligation to release the binaries or his changes, and from the hashrate graph it's clear that the earliest time he could have begin using the improved code was May 6th. Nobody had any significant advantage from this, even though they absolutely could have. Something to think about next time you want to throw a spurious argument out.
AtomicDoge
Member
**
Offline Offline

Activity: 163
Merit: 10


View Profile
August 19, 2014, 01:53:55 PM
 #3676
I like how monero supporters immediately show up with a bunch of arguments.

What are we having here? A graph vs somebody's post that were supposed to take on trust i guess.

Graph wins.
mirny
Legendary
*
Offline Offline

Activity: 1108
Merit: 1005



View Profile
August 19, 2014, 02:27:01 PM
 #3677
when I'm trying to send BCN's, wallet is saying:
Error: wrong address
I've tried two exchanges, tried to generate new payment ID, but still getting this error.
What the fuck is wrong?
This crap is useless now.
This is my signature...
Rias
Sr. Member
****
Offline Offline

Activity: 373
Merit: 250


View Profile
August 19, 2014, 02:46:07 PM
 #3678
Quote from: mirny on August 19, 2014, 02:27:01 PM
when I'm trying to send BCN's, wallet is saying:
Error: wrong address
I've tried two exchanges, tried to generate new payment ID, but still getting this error.
What the fuck is wrong?
This crap is useless now.

There's a new transfer command format. The payment id should be now indicated after "-p":

Code:
transfer <mixin> <address> <sum> [-p <payment_id>]

So just add -p before the payment id and you're fine.
mirny
Legendary
*
Offline Offline

Activity: 1108
Merit: 1005



View Profile
August 19, 2014, 04:54:40 PM
 #3679
thank you, it work now,
it would be fine, to add some changelog to the directory, to avoid this
This is my signature...
fluffypony
Donator
Legendary
*
Offline Offline

Activity: 1274
Merit: 1060


GetMonero.org / MyMonero.com


View Profile WWW
August 19, 2014, 11:00:59 PM
 #3680
Quote from: AtomicDoge on August 19, 2014, 01:53:55 PM
I like how monero supporters immediately show up with a bunch of arguments.

What are we having here? A graph vs somebody's post that were supposed to take on trust i guess.

Graph wins.


Wow, really? Ok, here:

Link to aforementioned post with graph: https://bitcointalk.org/index.php?topic=583449.msg6593768#msg6593768

Link I ALREADY MENTIONED with NoodleDoodle explaining his changes: https://bitcointalk.org/index.php?topic=583449.msg6597057#msg6597057

Link to github commit confirming commit date: https://github.com/monero-project/bitmonero/commit/3cc45e9324a402aee91e2f46861b2ca393d711aa

Link to my previous comment explaining the connection: https://bitcointalk.org/index.php?topic=512747.msg8434298#msg8434298

Also, I'm not a "supporter", I'm part of the Monero Core Team. I am not suddenly showing up because I have nothing to do. I was responding to this specific comment: "That's not the first time Monero developers use botnet and instamine coins". They were talking about the Monero developers...they were talking about a group of people...they were talking about ME! How can I let that stand? Would you keep quiet if someone said "AtomicDoge is stupid and is seriously overweight, he's going to die of myocardial infarction lol"? Or would you feel the need to comment?

I see it happen often on this thread - the same accounts are quick to say "XMR developers copy and paste code!" or "Monero is scam and developers have instamine" or "Of course they just bought their position on Mintpal because MRO developers are scam". You're talking to ME. You're insulting a group of people of which I am a part. It's hurtful, it's untrue, and it's uneccessary. Think about that next time you decide to throw out an insult.
Pages: « 1 ... 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 [184] 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 ... 417 »
  Print  
Bitcoin Forum > Alternate cryptocurrencies > Announcements (Altcoins) > [BCN] Bytecoin. Secure, private, untraceable since 2012
 « previous topic next topic »
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!