[BBR] Boolberry: Privacy and Security - Guaranteed Since 2014 - page 85.

teknohog

sr. member

Activity: 520

Merit: 253

555

Quote from: irukandji on June 12, 2017, 01:21:58 AM

If this coin changes it's name I will buy some...but...Boolberry?? Huh

Do you ever use Google? That's a childish company name if I ever heard one. In fact, its original form "googol" was actually made up by a 9-year old child. Also, look at other cool technology companies of today. No "grownup" names whatsoever.

Most importantly, the naming issue has already been discussed earlier, and there's nothing to add. So please do as I say, not as I do, and stop commenting about it Wink

Tuck Fheman

sr. member

Activity: 363

Merit: 250

Quote from: b4h4mu7 on June 11, 2017, 10:28:37 PM

No, this means that I'm contributing my own resources to the project. crypto_zoidberg is one of the brightest minds in this space and having him operate in any capacity is a positive. If we run into any technical issues during this process we'll be in contact with him. If not, we're going to continue working towards a release and focus on collaborating with him when it comes time to commit to the repo.

Thanks for stepping up!

irukandji

sr. member

Activity: 631

Merit: 258

If this coin changes it's name I will buy some...but...Boolberry?? Huh

Aby Normal

jr. member

Activity: 48

Merit: 2

Any crypto project that depends on only one man is not a legit crypto project - did Satoshi (whoever he might be) retired from BTC? - yes, and that was long time ago, and BTC is now where it is just because of community efforts ...
So, if CZ wants to be to BBR just like Satoshi was to BTC just let it be. If anyone here really wants BBR to have a future - don't just wait for CZ to make a miracle for you. If you really wanted that, why you haven't invested in ETH or some other centralized ICO scam, at least those that pray to Vitalik got some profit from it now.
BBR has a chance to be second best cryptonote project and that's not a small thing in crypto. I'll follow this trail and donate 1k BBR to this effort of reviving it (as soon as I sync my BBR wallet lol), hope that more bagholders will follow Wink

b4h4mu7

sr. member

Activity: 337

Merit: 315

Quote from: Randy Labs on June 11, 2017, 12:13:38 AM

Quote from: b4h4mu7 on June 10, 2017, 05:02:45 PM

Development Progress Update:

As some of you may know, I donated 20,000 Boolberry to zoidberg for development during the last major growth cycle but the donations didn't end up going towards development. After 6 months of waiting and some research I've decided to take a more hands-on approach to reviving this project in a direction that will benefit everyone in the shortest period of time.

I've managed to secure a senior level C++ developer to contribute to the project full-time. Our first major milestone will be merging the Bytecoin codebase with Boolberry's to bring it up to date with the advancements made over the years. In my view, the combination of Boolberry's unique features like its hashing algorithm, blockchain bloat reduction and privacy improvements along with Bytecoin 2.0's vast array of performance, usability and stability improvements will position Boolberry as the most advanced and efficient Cyptonote project.

In addition to the code merge, Clintar2 is working on his LMDB integration which is now in a working state. His LMDB work will eventually replace our RocksDB implementation when the update goes live.

I've had cordial exchanges with both crypto_zoidberg and clintar2; neither of whom have shown any reserves about this proposal. I'm funding this project by myself so I would appreciate any donations from the community as everyone here will be benefitting from the overall growth of the project.

Donations: 1FB1xJe7suSN6QW1x2Yt2X5YPGpRNDzeyLMdDyDEg8tictHPYEaRSXFUqjwU85wUt41pDPnJdeGYy9t 8e3MzqRn29tTo33E

Does this mean zoidberg has retired from bbr, or he is collaborating with you?

No, this means that I'm contributing my own resources to the project. crypto_zoidberg is one of the brightest minds in this space and having him operate in any capacity is a positive. If we run into any technical issues during this process we'll be in contact with him. If not, we're going to continue working towards a release and focus on collaborating with him when it comes time to commit to the repo.

Randy Labs

newbie

Activity: 17

Merit: 0

Quote from: b4h4mu7 on June 10, 2017, 05:02:45 PM

Development Progress Update:

As some of you may know, I donated 20,000 Boolberry to zoidberg for development during the last major growth cycle but the donations didn't end up going towards development. After 6 months of waiting and some research I've decided to take a more hands-on approach to reviving this project in a direction that will benefit everyone in the shortest period of time.

I've managed to secure a senior level C++ developer to contribute to the project full-time. Our first major milestone will be merging the Bytecoin codebase with Boolberry's to bring it up to date with the advancements made over the years. In my view, the combination of Boolberry's unique features like its hashing algorithm, blockchain bloat reduction and privacy improvements along with Bytecoin 2.0's vast array of performance, usability and stability improvements will position Boolberry as the most advanced and efficient Cyptonote project.

In addition to the code merge, Clintar2 is working on his LMDB integration which is now in a working state. His LMDB work will eventually replace our RocksDB implementation when the update goes live.

I've had cordial exchanges with both crypto_zoidberg and clintar2; neither of whom have shown any reserves about this proposal. I'm funding this project by myself so I would appreciate any donations from the community as everyone here will be benefitting from the overall growth of the project.

Donations: 1FB1xJe7suSN6QW1x2Yt2X5YPGpRNDzeyLMdDyDEg8tictHPYEaRSXFUqjwU85wUt41pDPnJdeGYy9t 8e3MzqRn29tTo33E

Does this mean zoidberg has retired from bbr, or he is collaborating with you?

b4h4mu7

sr. member

Activity: 337

Merit: 315

Development Progress Update:

As some of you may know, I donated 20,000 Boolberry to zoidberg for development during the last major growth cycle but the donations didn't end up going towards development. After 6 months of waiting and some research I've decided to take a more hands-on approach to reviving this project in a direction that will benefit everyone in the shortest period of time.

I've managed to secure a senior level C++ developer to contribute to the project full-time. Our first major milestone will be merging the Bytecoin codebase with Boolberry's to bring it up to date with the advancements made over the years. In my view, the combination of Boolberry's unique features like its hashing algorithm, blockchain bloat reduction and privacy improvements along with Bytecoin 2.0's vast array of performance, usability and stability improvements will position Boolberry as the most advanced and efficient Cyptonote project.

In addition to the code merge, Clintar2 is working on his LMDB integration which is now in a working state. His LMDB work will eventually replace our RocksDB implementation when the update goes live.

I've had cordial exchanges with both crypto_zoidberg and clintar2; neither of whom have shown any reserves about this proposal. I'm funding this project by myself so I would appreciate any donations from the community as everyone here will be benefitting from the overall growth of the project.

Donations: 1FB1xJe7suSN6QW1x2Yt2X5YPGpRNDzeyLMdDyDEg8tictHPYEaRSXFUqjwU85wUt41pDPnJdeGYy9t 8e3MzqRn29tTo33E

adous

newbie

Activity: 13

Merit: 0

Quote from: DeCryptIcon on February 07, 2017, 02:58:03 PM

Nice job on the donation. If we can confirm the donations will spark new development I'll contribute as well.

mine too...same here for me....if there will be so i will ready to join it...

cryptohunter

legendary

Activity: 2100

Merit: 1167

MY RED TRUST LEFT BY SCUMBAGS - READ MY SIG

is there an active bbr slack that is worth joining to learn about any kind of development ongoing with bbr?
or is bbr currently in a resting phase?

sowle

newbie

Activity: 20

Merit: 0

Quote from: joggel on June 03, 2017, 05:29:58 AM

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.

Good solution!!
I don't see much good nodes in connection list either.

joggel

newbie

Activity: 4

Merit: 0

Quote from: sowle on June 01, 2017, 03:05:43 PM

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.

crypto_zoidberg

hero member

Activity: 976

Merit: 646

Quote from: sowle on June 01, 2017, 06:00:53 PM

Quote from: crypto_zoidberg on June 01, 2017, 04:54:08 PM

Thank you, buddy, jut one little question: why you acquire m_blockchain_lock (it's already owned by this code at the beginning of function)?

my fault) fixed

Merged!
Thanks!

Any ideas who could make these transactions?

Zoidberg

sowle

newbie

Activity: 20

Merit: 0

Quote from: crypto_zoidberg on June 01, 2017, 04:54:08 PM

Thank you, buddy, jut one little question: why you acquire m_blockchain_lock (it's already owned by this code at the beginning of function)?

my fault) fixed

crypto_zoidberg

hero member

Activity: 976

Merit: 646

Quote from: sowle on June 01, 2017, 01:24:31 PM

Quote from: joggel on May 30, 2017, 06:24:38 AM

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

Got the same issue.

I found out there are txs with invalid key_image in the blockchain. The first one is at block 757131.
On May 9th zoidberg commited a security fix from monero (https://getmonero.org/2017/05/17/disclosure-of-a-major-bug-in-cryptonote-based-currencies.html) and now each input is being checked against invalid key_image. That's good.
Unfortunately, by the time he commited the fix there had already been malformed txs in the blockchain. That's why blockchain can't be resyncronized from the beginning now.

I send a pull request to address this issue: https://github.com/cryptozoidberg/boolberry/pull/54

Thank you, buddy, jut one little question: why you acquire m_blockchain_lock (it's already owned by this code at the beginning of function)?

Code:

    CRITICAL_REGION_BEGIN(m_blockchain_lock);
    top_block_height = m_blocks.size() - 1;
    CRITICAL_REGION_END();

joggel

newbie

Activity: 4

Merit: 0

Quote from: sowle on June 01, 2017, 03:05:43 PM

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?

sowle

newbie

Activity: 20

Merit: 0

Quote from: joggel on June 01, 2017, 02:06:06 PM

What i can do now for sync the blockhain?
Without syncing no transaction is possible, because simplewallet say the demon are busy.

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

joggel

newbie

Activity: 4

Merit: 0

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.

sowle

newbie

Activity: 20

Merit: 0

As to invalid txs with invalid key_images. There are 7 in the blockchain. Thanks to zoidberg's fix it's completely fixed now.

Invalid txs:

Code:

Invalid key image: <26e8958fc2b227b045c3f489f2ef98f0d5dfac05d3c63339b13802886d53fc05>, amount: 0.990000000000, tx: <9f395234de50d836337dacef0133031f34d7ccf77ff261fdd710494675383e69>
Invalid key image: , amount: 0.990000000000, tx: 
Invalid key image: <26e8958fc2b227b045c3f489f2ef98f0d5dfac05d3c63339b13802886d53fc85>, amount: 899.980000000000, tx: 
Invalid key image: <0000000000000000000000000000000000000000000000000000000000000000>, amount: 899.980000000000, tx: <6130a0cbc7a19ba662d7bef35cd07bb948045e5d942d8db699748d781b2a73a4>
Invalid key image: <0000000000000000000000000000000000000000000000000000000000000080>, amount: 1799.990000000000, tx: <9584905ab31a2cda1ee2def9a853b02103cd66af67c9c525762e031ed7fa8d96>
Invalid key image: , amount: 1799.990000000000, tx: <8b02b0477493f6d86c7f9067ada619bb877faedc7d4312f3947ff8b67cc4422b>
Invalid key image: , amount: 1799.990000000000, tx: <38999f6326860e4f48543c978a3f79e135d8ff0e7ce2ad5f5f169d455ecbcd6e>

Invalid txs with relation to blocks and timestamps:

Code:

tx                                                               amount  block  timestamp
9f395234de50d836337dacef0133031f34d7ccf77ff261fdd710494675383e69    0.99 757131 2017-04-10 22:54:06
ff43d5b09e49d619a14ea243ebc2640a187813b2afd67f1090da948204b949c2    0.99 757134 2017-04-10 22:58:09
d2a66d7dc40b8a618d15f878c9153a61d0a87dde703df8185f41b0c6078d0a56  899.98 757183 2017-04-11 00:03:48
6130a0cbc7a19ba662d7bef35cd07bb948045e5d942d8db699748d781b2a73a4  899.98 757190 2017-04-11 00:14:17
9584905ab31a2cda1ee2def9a853b02103cd66af67c9c525762e031ed7fa8d96 1799.99 757235 2017-04-11 01:05:33
8b02b0477493f6d86c7f9067ada619bb877faedc7d4312f3947ff8b67cc4422b 1799.99 757237 2017-04-11 01:10:58
38999f6326860e4f48543c978a3f79e135d8ff0e7ce2ad5f5f169d455ecbcd6e 1799.99 757241 2017-04-11 01:13:46

As you can see, an attacker tried with small amount tx, then went further.
It was performed in ~2 hours at April 11th midnight.

sowle

newbie

Activity: 20

Merit: 0

Quote from: joggel on May 30, 2017, 06:24:38 AM

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

Got the same issue.

I found out there are txs with invalid key_image in the blockchain. The first one is at block 757131.
On May 9th zoidberg commited a security fix from monero (https://getmonero.org/2017/05/17/disclosure-of-a-major-bug-in-cryptonote-based-currencies.html) and now each input is being checked against invalid key_image. That's good.
Unfortunately, by the time he commited the fix there had already been malformed txs in the blockchain. That's why blockchain can't be resyncronized from the beginning now.

I send a pull request to address this issue: https://github.com/cryptozoidberg/boolberry/pull/54

joggel

newbie

Activity: 4

Merit: 0

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

Topic: [BBR] Boolberry: Privacy and Security - Guaranteed Since 2014 - page 85. (Read 1210749 times)