Search content
Sort by

Showing 4 of 4 results by joggel
Post
Topic
Re: [BBR] Boolberry: Privacy and Security - Guaranteed[Bittrex/Poloniex]GPU Released
by
joggel
on 03/06/2017, 09:29:58 UTC

You should wait for fixed binaries from zoidbeg.
My fix seem to solve the issue (my build synced from the scratch normally) so I hope zoidbeg will accept it very soon.
Or you can get somewhere blockchain.bin past 750k block — your current daemon will work because it will sync past the critical point

I solved also the sync problem with first use a demon what no have the "check the security bug" and past block 780000. Then use a newer demon what check the security bug.
Post
Topic
Re: [BBR] Boolberry: Privacy and Security - Guaranteed[Bittrex/Poloniex]GPU Released
by
joggel
on 01/06/2017, 20:27:42 UTC
You should wait for fixed binaries from zoidbeg.
My fix seem to solve the issue (my build synced from the scratch normally) so I hope zoidbeg will accept it very soon.
Or you can get somewhere blockchain.bin past 750k block — your current daemon will work because it will sync past the critical point

hope zoidberg will accept it soon.
Now the blockchain is over 3GB and i dont know where to dowload.
It´s also not easy to get seed nodes, as the white list is only 8 nodes, for me what i can see.
How much nodes do you see?
Post
Topic
Re: [BBR] Boolberry: Privacy and Security - Guaranteed[Bittrex/Poloniex]GPU Released
by
joggel
on 01/06/2017, 18:06:06 UTC
thank you for replay.

i found this error when i want to sync the blockchain:

Code:
2017-May-30 20:08:08.443502 [P2P8]ERROR /home/2017/boolberry/src/currency_core/blockchain_storage.cpp:2046[bool currency::blockchain_storage::check_tx_input(const currency::txin_to_key&, const crypto::hash&, const std::vector&, uint64_t*)]Failed to validate key image
2017-May-30 20:08:08.443541 [P2P8]Failed to check ring signature for tx <9f395234de50d836337dacef0133031f34d7ccf77ff261fdd710494675383e69>
2017-May-30 20:08:08.443559 [P2P8]Transaction verification impossible: <9f395234de50d836337dacef0133031f34d7ccf77ff261fdd710494675383e69>
2017-May-30 20:08:08.498263 [P2P8]ERROR /home/2017/boolberry/src/currency_core/blockchain_storage.cpp:2046[bool currency::blockchain_storage::check_tx_input(const currency::txin_to_key&, const crypto::hash&, const std::vector&, uint64_t*)]Failed to validate key image
2017-May-30 20:08:08.498293 [P2P8]Failed to check ring signature for tx <9f395234de50d836337dacef0133031f34d7ccf77ff261fdd710494675383e69>
2017-May-30 20:08:08.498307 [P2P8]Block with id: have at least one transaction (id: <9f395234de50d836337dacef0133031f34d7ccf77ff261fdd710494675383e69>) with wrong inputs.
2017-May-30 20:08:08.498443 [P2P8]ERROR /home/2017/boolberry/src/currency_core/blockchain_storage.cpp:2046[bool currency::blockchain_storage::check_tx_input(const currency::txin_to_key&, const crypto::hash&, const std::vector&, uint64_t*)]Failed to validate key image
2017-May-30 20:08:08.498457 [P2P8]Failed to check ring signature for tx <9f395234de50d836337dacef0133031f34d7ccf77ff261fdd710494675383e69>
2017-May-30 20:08:08.498483 [P2P8]BLOCK ADDED AS INVALID:
, prev_id=<435692792d7790e86e455b2211814fab0a4b480222cd216f0bc8b6164561e8c9>, m_invalid_blocks count=1
2017-May-30 20:08:08.498508 [P2P8]Block with id added as invalid becouse of wrong inputs in transactions
2017-May-30 20:08:08.498526 [P2P8][213.239.213.235:10101 OUT]Block verification failed, dropping connection
2017-May-30 20:08:09.428587 [P2P6]Connecting to 213.239.213.235:10101(white=1, last_seen: d0.h0.m0.s36)...
2017-May-30 20:08:09.968004 [P2P5][213.239.213.235:10101 OUT]Sync data returned unknown top block: 757131 -> 791910 [34779 blocks (48 days) behind]
SYNCHRONIZATION started
2017-May-30 20:08:09.968144 [P2P5][213.239.213.235:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2017-May-30 20:08:19.970070 [P2P3]Connecting to 122.54.174.141:10101(white=1, last_seen: d0.h1.m1.s23)...
2017-May-30 20:08:22.409997 [P2P6][122.54.174.141:10101 OUT]Sync data returned unknown top block: 757131 -> 526966 [230165 blocks (-319 days) ahead]
SYNCHRONIZATION started
2017-May-30 20:08:22.410143 [P2P6][122.54.174.141:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2017-May-30 20:08:22.410322 [P2P3]Connecting to 51.255.193.7:10101(white=1, last_seen: d0.h0.m54.s42)...
2017-May-30 20:08:23.088519 [P2P1][51.255.193.7:10101 OUT]Sync data returned unknown top block: 757131 -> 791910 [34779 blocks (48 days) behind]
SYNCHRONIZATION started
2017-May-30 20:08:23.088666 [P2P1][51.255.193.7:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2017-May-30 20:08:23.088851 [P2P3]Connecting to 195.154.161.46:10101(white=1, last_seen: d0.h0.m54.s21)...
2017-May-30 20:08:24.535188 [P2P8][195.154.161.46:10101 OUT]Sync data returned unknown top block: 757131 -> 791910 [34779 blocks (48 days) behind]
SYNCHRONIZATION started
2017-May-30 20:08:24.535328 [P2P8][195.154.161.46:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2017-May-30 20:08:24.768700 [P2P6]Block recognized as orphaned and rejected, id =
2017-May-30 20:08:24.768729 [P2P6][66.228.37.171:10101 OUT]Block received at sync phase was marked as orphaned, dropping connection
2017-May-30 20:08:25.632576 [P2P6]Block recognized as orphaned and rejected, id =
2017-May-30 20:08:25.632621 [P2P6][213.239.213.235:10101 OUT]Block received at sync phase was marked as orphaned, dropping connection

try to sync many times, allways stick on the same place.
What i can do now for sync the blockhain?
Without syncing no transaction is possible, because simplewallet say the demon are busy.



 
Post
Topic
Re: [BBR] Boolberry: Privacy and Security - Guaranteed[Bittrex/Poloniex]GPU Released
by
joggel
on 30/05/2017, 10:24:38 UTC
I can not sync BBR Blockchain.
At Block 757131 get a "Block recognized as orphaned and rejected" message.
And this for hours.
i use a seed node 5.9.44.154:10101