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

[crypto_zoidberg]

If you look at the long term chart, it is clear we still have a long hill to climb, but it is just a matter of getting the message out that BBR has the only cryptonote dev that changed the block format. This is no tweaking of a constant change, but the actual blocks! For those not so technical, this is like replacing the engine while making it more fuel efficient and get more power. In other words not something for a garage mechanic, but rather for an engine designer.

So next time someone is making disparaging comments on BBR, just ask if their coin devs were able to change (dont even need to require improving), just change the block format. That should make 90% of them say something silly and go away.

James

I still don't get it. How is it more efficient/more powerful? Does every block take less hardware space or what?

Hi Jungian!

We had a few innovations on top of CryptoNote technology:
* Different PoW hash WildKeccak that is secure(from our point of view) and much faster. This leads to faster sync with blockchain, compared to regular CryptoNote coins. Try to synchronize BCN daemon with one day blockchain, Monero daemon with one day blockchain, and Boolberry with one day blockchain. You'll see the difference.
* We have privacy improvement
* We have blockchain bloat improvement with ring signatures pruning.

That's most important things.
Also we have a number of secondary features: aliases for address, p2p-based alerting for critical updates, and well... we have more fair(from our point of view) emission curve, compared with BCN and XMR.


Zoidberg

[luckygenough56]

I can confirm boolberry blockchain is syncing 1000x faster than Monero and is less bloated.

Monero blockchain is so big and such a slow ass it's desperating. So i was supposing that cryptonote was crap for everyday use.

Can't believe i didn't check on Boolberry before  

And Boolberry qt is the best among cryptonotes !!!

[dr_chen]

If you look at the long term chart, it is clear we still have a long hill to climb, but it is just a matter of getting the message out that BBR has the only cryptonote dev that changed the block format. This is no tweaking of a constant change, but the actual blocks! For those not so technical, this is like replacing the engine while making it more fuel efficient and get more power. In other words not something for a garage mechanic, but rather for an engine designer.

So next time someone is making disparaging comments on BBR, just ask if their coin devs were able to change (dont even need to require improving), just change the block format. That should make 90% of them say something silly and go away.

James

I still don't get it. How is it more efficient/more powerful? Does every block take less hardware space or what?

Hi Jungian!

We had a few innovations on top of CryptoNote technology:
* Different PoW hash WildKeccak that is secure(from our point of view) and much faster. This leads to faster sync with blockchain, compared to regular CryptoNote coins. Try to synchronize BCN daemon with one day blockchain, Monero daemon with one day blockchain, and Boolberry with one day blockchain. You'll see the difference.
* We have privacy improvement
* We have blockchain bloat improvement with ring signatures pruning.

That's most important things.
Also we have a number of secondary features: aliases for address, p2p-based alerting for critical updates, and well... we have more fair(from our point of view) emission curve, compared with BCN and XMR.


Zoidberg

The most important is the excellent GUI wallet

[ebite]

If you look at the long term chart, it is clear we still have a long hill to climb, but it is just a matter of getting the message out that BBR has the only cryptonote dev that changed the block format. This is no tweaking of a constant change, but the actual blocks! For those not so technical, this is like replacing the engine while making it more fuel efficient and get more power. In other words not something for a garage mechanic, but rather for an engine designer.

So next time someone is making disparaging comments on BBR, just ask if their coin devs were able to change (dont even need to require improving), just change the block format. That should make 90% of them say something silly and go away.

James

I still don't get it. How is it more efficient/more powerful? Does every block take less hardware space or what?

Hi Jungian!

We had a few innovations on top of CryptoNote technology:
* Different PoW hash WildKeccak that is secure(from our point of view) and much faster. This leads to faster sync with blockchain, compared to regular CryptoNote coins. Try to synchronize BCN daemon with one day blockchain, Monero daemon with one day blockchain, and Boolberry with one day blockchain. You'll see the difference.
* We have privacy improvement
* We have blockchain bloat improvement with ring signatures pruning.

That's most important things.
Also we have a number of secondary features: aliases for address, p2p-based alerting for critical updates, and well... we have more fair(from our point of view) emission curve, compared with BCN and XMR.


Zoidberg

The most important is the excellent GUI wallet

Only the miner can make alias for address, is it correct?

[eddywise]

I can confirm boolberry blockchain is syncing 1000x faster than Monero and is less bloated.

Monero blockchain is so big and such a slow ass it's desperating. So i was supposing that cryptonote was crap for everyday use.

Can't believe i didn't check on Boolberry before  

And Boolberry qt is the best among cryptonotes !!!

I DO agree,so I have dump my XMR long ago and turn to BBR

[othe]

I can confirm boolberry blockchain is syncing 1000x faster than Monero and is less bloated.

Monero blockchain is so big and such a slow ass it's desperating. So i was supposing that cryptonote was crap for everyday use.

Can't believe i didn't check on Boolberry before  

And Boolberry qt is the best among cryptonotes !!!

if your known in the monero thread you should cross post this

A BBR TX is as big as a XMR TX, so no the blockchain is smaller because its less used and that´s about it.

PS: Bitcoin has also a bigger Blockchain than all other coins, for that reason.

[dga]

I can confirm boolberry blockchain is syncing 1000x faster than Monero and is less bloated.

Monero blockchain is so big and such a slow ass it's desperating. So i was supposing that cryptonote was crap for everyday use.

Can't believe i didn't check on Boolberry before  

And Boolberry qt is the best among cryptonotes !!!

if your known in the monero thread you should cross post this

A BBR TX is as big as a XMR TX, so no the blockchain is smaller because its less used and that´s about it.

PS: Bitcoin has also a bigger Blockchain than all other coins, for that reason.

That's not entirely accurate.  With ring signature pruning, transactions with mixins will, after a while, get pruned down to use less space than they would in XMR or other cryptonotes.

[othe]

This isn´t implemented yet DGA.

So the reason the XMR bc bigger is because of the number of tx, the faster blocktimes just give a little to no overhead.

[othe]

Whats the sense of your post?

The RS deletion isn´t implemented yet.

[dga]

Whats the sense of your post?

The RS deletion isn´t implemented yet.

That in the long run, BBR will *remain* faster than other cryptonote coins.

Sure - its major advantage right now derives from its better choice of block time, the fact that it didn't have an early-stage dust problem, and that its transaction fees weren't as easily exploitable for DoS attacks.

But that advantage will be supported in the long term under increasing transaction volume through ring signature pruning.

*shrugs*

[othe]

You got my post wrong, i just explained why its "less bloated" currently.

[tifozi]

@James

Some good press will be great I think there is some excitement and new folks discovering BBR.

[crypto_zoidberg]

Whats the sense of your post?

The RS deletion isn´t implemented yet.

Implemented core support(which is important), but pruning is not enabled yet since i don't whant to move checkpoint forward to blockchain head with so young blockchain.
It was the same when you guys talked to everyone in rpietila thread that this feature is simply not possible. But when we published presentation you suddenly realized how it works.

Anyway, i think you in partly right - it may looks like we announcing features that is not working. Well.... i think it's time to go. After i'll finish current tasks i think i'll move checkpoint forward and add code for prununing RS. And add some tests, just to be sure that there no bugs ! After that i hope discussion will be over.

Zoidberg

[dga]

You got my post wrong, i just explained why its "less bloated" currently.

Sorry for misinterpreting.   Just wanted to be clear that there are actually several factors involved.

Speaking of which, I note from the BBR stats that the TX volume is *way* up over the last few weeks.

Has someone been trying to attack the coin/blockchain in the same way XMR was under attack, and we just didn't notice?

[othe]

You got my post wrong, i just explained why its "less bloated" currently.

Sorry for misinterpreting.   Just wanted to be clear that there are actually several factors involved.

Speaking of which, I note from the BBR stats that the TX volume is *way* up over the last few weeks.

Has someone been trying to attack the coin/blockchain in the same way XMR was under attack, and we just didn't notice?

The attack was creating transactions with large mixins (>100) as no CN coin has fees per kb implemented yet afaik. Had nothing todo with normal tx volume.
As you know CN has a "average moving max blocksize" and the more mixin the bigger the tx get and may not fit into the block till the median blocksize gets bigger, this can cause stuck transactions.
If you look at the tx fees of most Cn coins, i can´t see how they couldn´t be attacked currently, if we convert the fees to usd value - such an attack doesn´t cost much.

[coins101]

As BTC-Mike is involved, if you can get DwarfPool on board, I'll point some mining rigs onto BBR.

Cheers.

[Hotmetal]

Has anyone managed to get miner (https://github.com/cryptozoidberg/cpuminer-multi) built statically?
I've tried various linux distros (CentOS bleh, Ubuntu), various combinations of curl (statically built) etc and not having any luck at all..

[root@cpt-cloud001 cpuminer-multi]# make
make  all-recursive
make[1]: Entering directory `/root/cpuminer-multi'
Making all in compat
make[2]: Entering directory `/root/cpuminer-multi/compat'
Making all in jansson
make[3]: Entering directory `/root/cpuminer-multi/compat/jansson'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/root/cpuminer-multi/compat/jansson'
make[3]: Entering directory `/root/cpuminer-multi/compat'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/root/cpuminer-multi/compat'
make[2]: Leaving directory `/root/cpuminer-multi/compat'
make[2]: Entering directory `/root/cpuminer-multi'
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -pthread -fno-strict-aliasing -I./compat/jansson -I/tmp/curl/include  -O3 -march=native -fPIC  -I/tmp/curl/include -MT minerd-cpu-miner.o -MD -MP -MF .deps/minerd-cpu-miner.Tpo -c -o minerd-cpu-miner.o `test -f 'cpu-miner.c' || echo './'`cpu-miner.c
mv -f .deps/minerd-cpu-miner.Tpo .deps/minerd-cpu-miner.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -pthread -fno-strict-aliasing -I./compat/jansson -I/tmp/curl/include  -O3 -march=native -fPIC  -I/tmp/curl/include -MT minerd-util.o -MD -MP -MF .deps/minerd-util.Tpo -c -o minerd-util.o `test -f 'util.c' || echo './'`util.c
mv -f .deps/minerd-util.Tpo .deps/minerd-util.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -pthread -fno-strict-aliasing -I./compat/jansson -I/tmp/curl/include  -O3 -march=native -fPIC  -I/tmp/curl/include -MT minerd-wildkeccak.o -MD -MP -MF .deps/minerd-wildkeccak.Tpo -c -o minerd-wildkeccak.o `test -f 'wildkeccak.c' || echo './'`wildkeccak.c
wildkeccak.c:106:2: warning: #warning using SSE2 optimizations
mv -f .deps/minerd-wildkeccak.Tpo .deps/minerd-wildkeccak.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -pthread -fno-strict-aliasing -I./compat/jansson -I/tmp/curl/include  -O3 -march=native -fPIC  -I/tmp/curl/include -MT minerd-xmalloc.o -MD -MP -MF .deps/minerd-xmalloc.Tpo -c -o minerd-xmalloc.o `test -f 'xmalloc.c' || echo './'`xmalloc.c
mv -f .deps/minerd-xmalloc.Tpo .deps/minerd-xmalloc.Po
gcc -std=gnu99 -O3 -march=native -fPIC  -I/tmp/curl/include -pthread -pie -static -L/tmp/curl/lib -o minerd minerd-cpu-miner.o minerd-util.o minerd-wildkeccak.o minerd-xmalloc.o -L/tmp/curl/lib -lcurl -lrt compat/jansson/libjansson.a -lpthread  
/usr/bin/ld: /usr/lib/gcc/x86_64-redhat-linux/4.4.7/crtbeginT.o: relocation R_X86_64_32 against `__DTOR_END__' can not be used when making a shared object; recompile with -fPIC
/usr/lib/gcc/x86_64-redhat-linux/4.4.7/crtbeginT.o: could not read symbols: Bad value
collect2: ld returned 1 exit status
make[2]: *** [minerd] Error 1
make[2]: Leaving directory `/root/cpuminer-multi'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/cpuminer-multi'
make: *** [all] Error 2

[tifozi]

The miner is known to build just fine on various platforms. The problem might be related to you configure options if you used static and or your gcc version (4.4.x is quite dated). Have you tried building with -fPIC

working gcc version on my rig = gcc (Ubuntu 4.8.2-19ubuntu1) 4.8.2

[Hotmetal]

The miner is known to build just fine on various platforms. The problem might be related to you configure options if you used static and or your gcc version (4.4.x is quite dated). Have you tried building with -fPIC

working gcc version on my rig = gcc (Ubuntu 4.8.2-19ubuntu1) 4.8.2

Well, I'm trying to get it built statically. Building normally works fine.
Even with gcc 4.9.1 it isn't building statically..

[coinits]

The miner is known to build just fine on various platforms. The problem might be related to you configure options if you used static and or your gcc version (4.4.x is quite dated). Have you tried building with -fPIC

working gcc version on my rig = gcc (Ubuntu 4.8.2-19ubuntu1) 4.8.2

How about a version for us Windows NVIDIA chumps? Now that would be special.