Topic: [BCN] Bytecoin. Secure, private, untraceable since 2012 - page 235. (Read 1070171 times)

Yea, i have the same problem. It doesnt synch! Transactions seem to work fine but i dont know if mining works.

I have just tried to sync my deamon and I have sync OK at the end but numer of days in some rows is really strange.
2014-Aug-19 10:46:36.415911 [P2P9][108.61.17.178:8080 OUT] SYNCHRONIZED OK
2014-Aug-19 10:47:03.265429 [P2P6][75.73.71.143:8080 OUT]Sync data returned unknown top block: 548760 -> 546611 [2149 blocks (25620477880152152 days) ahead]

Looks like the new update caused a little mess... Idk though, everything works fine for me.

do you use the last binary 1.0.1? If not update it. https://bitcointalksearch.org/topic/m.8351704

2014-Aug-19 11:12:17.035008 [P2P9][46.228.6.35:56351 INC]Sync data returned unknown top block: 548747 -> 546611 [2136 blocks (25620477880152152 days) ahead]
SYNCHRONIZATION started
2014-Aug-19 11:12:19.172131 [P2P3]----- BLOCK ADDED AS ALTERNATIVE ON HEIGHT 546603
id:   <91e836cd2a9b30a32a3858f2f9162a3453a7d96747c3ef993c8c07a9a3e52d67>
PoW:   <82b6f74a4c92bd28cce4d2eeac96f202110b0af9528ab4f44e11271f05000000>
difficulty:   95882153
2014-Aug-19 11:12:19.182131 [P2P3]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 11:12:19.187131 [P2P3][46.228.6.35:56351 INC]Block verification failed, dropping connection
2014-Aug-19 11:12:26.463548 [P2P6][46.173.12.157:50443 INC]Sync data returned unknown top block: 548747 -> 546611 [2136 blocks (25620477880152152 days) ahead]
SYNCHRONIZATION started
2014-Aug-19 11:12:31.424831 [P2P0]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 11:12:31.430832 [P2P0][46.173.12.157:50443 INC]Block verification failed, dropping connection
2014-Aug-19 11:12:45.034610 [P2P8][159.118.166.237:36153 INC]Sync data returned unknown top block: 548747 -> 546611 [2136 blocks (25620477880152152 days) ahead]
SYNCHRONIZATION started
2014-Aug-19 11:12:57.270310 [P2P5][182.161.177.27:4518 INC]Sync data returned unknown top block: 548747 -> 546611 [2136 blocks (25620477880152152 days) ahead]
SYNCHRONIZATION started
2014-Aug-19 11:13:02.998637 [P2P6]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 11:13:03.004638 [P2P6][159.118.166.237:36153 INC]Block verification failed, dropping connection
2014-Aug-19 11:13:06.555841 [P2P9]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 11:13:06.562841 [P2P9][182.161.177.27:4518 INC]Block verification failed, dropping connection
2014-Aug-19 11:13:09.810027 [P2P7][sock 724] Some problems at write: An established connection was aborted by the software in your host machine:10053
2014-Aug-19 11:13:13.816256 [P2P3][216.8.146.119:60569 INC]Sync data returned unknown top block: 548748 -> 546611 [2137 blocks (25620477880152152 days) ahead]
SYNCHRONIZATION started
2014-Aug-19 11:13:17.184449 [P2P5][101.109.248.27:55014 INC]Sync data returned unknown top block: 548748 -> 546611 [2137 blocks (25620477880152152 days) ahead]
SYNCHRONIZATION started
2014-Aug-19 11:13:18.491523 [P2P8][159.118.166.237:36161 INC]Sync data returned unknown top block: 548748 -> 546611 [2137 blocks (25620477880152152 days) ahead]
SYNCHRONIZATION started
2014-Aug-19 11:13:25.695935 [P2P5]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 11:13:25.702936 [P2P5][216.8.146.119:60569 INC]Block verification failed, dropping connection
2014-Aug-19 11:13:28.351087 [P2P7]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 11:13:28.358088 [P2P7][101.109.248.27:55014 INC]Block verification failed, dropping connection
2014-Aug-19 11:13:42.731910 [P2P6]Block <8d364fb9dbdc730e96186f640557a875132d515ca96dae5ab2ecd16f30fdb706> has wrong major version: 1, at height 546604 expected version is 2
2014-Aug-19 11:13:42.737910 [P2P6][159.118.166.237:36161 INC]Block verification failed, dropping connection
2014-Aug-19 11:14:25.035329 [P2P2][sock 640] Some problems at write: An existing connection was forcibly closed by the remote host:10054

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

win7 x64 en (7600)
i7 2600k

One more reason to start supporting smaller pools.

I think you again have big troubles with blockchain

When you will fix it?

2014-Aug-19 08:47:38.886102 [P2P5][78.184.136.209:8080 OUT]Sync data returned unknown top block: 548719 -> 546611 [2108 blocks (2562047
7880152152 days) ahead]

with new wallet, i cant send coins anywhere,
it's a new feature?

"Solomining" is much less possible as the botnet miners on the affected PCs are likely to be just the mining software which is dependent on centralized control center (I might be totally off though). Thus, it requires a pool. I assume it is way more convenient to use the existing one than maintain yours.

noob questions. ...than why they do it such a visible way.. in the pools? Would not be better to do it on their private pool or something like solomining?

Operators hire their botnets to the highest bidder, or use them to mine cryptocurrencies or break passwords.
There are known botnets with hundreds of thousands of computers under their control.

What's this?

 

yes, Monero mining zombies, and not the only botherder have this idea .

Looks like you are trolls, guys  

Looks like it's actually the Quazarcoin botnet mining Quazarcoin as usual:

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

Hi, just started solo mining BCN and got many in just one day  
Problem is, that next day i checked my wallet, there was 0 balance I am pretty sure i closed bytecoind with »exit« command the other day, so it should save balance. Does anyone have any idea what went wrong?

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 ?

Maybe the main reason for that is the few pools operating and lack of p2pool.
This is high centralized coin
I was thinking on moving to this coin to test, but I better not.