Author

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

legendary
Activity: 2968
Merit: 1198
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.

That is incorrect on all three counts. Take a look at the details (proportion attributable to these factors, etc.) and you will see that these are not the main reasons for the block chain being smaller and faster. Even the difference in PoW is relatively unimportant right now (but might have some advantage -- or disadvantage -- in the future). My friend othe was right it is almost all a difference right now is lower BBR usage causing the chain to be much smaller.
sr. member
Activity: 378
Merit: 250
root@cami009:~/cpuminer-multi# LDFLAGS="-static" ./configure
[..]
checking for curl-config... /usr/bin/curl-config
checking for the version of libcurl... 7.35.0
checking for libcurl >= version 7.15.2... yes
checking whether libcurl is usable... no
configure: error: Missing required libcurl >= 7.15.2



Can you first tell why you want to link it statically?
http://www.akkadia.org/drepper/no_static_linking.html
When you use -static flag for ld, you need libcurl.a.  And "./configure --enable-static --with-pic" for curl.


I have > 50 machines with a variety of different Linux distros and having to go through the hassle of building on every single machine is rather painful (I work at cloud provider).
hero member
Activity: 742
Merit: 501
I tried to recreate your issue in my box. It looks like the problem is with your curl install. When I use the system curl it just works fine with the static build.

Code:
/usr/lib/x86_64-linux-gnu

Code:
 curl --version
curl 7.35.0 (x86_64-pc-linux-gnu) libcurl/7.35.0 OpenSSL/1.0.1f zlib/1.2.8 libidn/1.28 librtmp/2.3
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtmp rtsp smtp smtps telnet tftp
Features: AsynchDNS GSS-Negotiate IDN IPv6 Largefile NTLM NTLM_WB SSL libz TLS-SRP

Code:
LDFLAGS="-static" ./configure

Those other configure options that you are trying to pass to disable libs are not supported.


root@cami009:~/cpuminer-multi# curl --version
curl 7.35.0 (x86_64-pc-linux-gnu) libcurl/7.35.0 OpenSSL/1.0.1f zlib/1.2.8 libidn/1.28 librtmp/2.3
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtmp rtsp smtp smtps telnet tftp
Features: AsynchDNS GSS-Negotiate IDN IPv6 Largefile NTLM NTLM_WB SSL libz TLS-SRP



root@cami009:~/cpuminer-multi# LDFLAGS="-static" ./configure
[..]
checking for curl-config... /usr/bin/curl-config
checking for the version of libcurl... 7.35.0
checking for libcurl >= version 7.15.2... yes
checking whether libcurl is usable... no
configure: error: Missing required libcurl >= 7.15.2



And to add to otila,

resolution is to build static curl, posted in Wolf0's thread https://bitcointalksearch.org/topic/m.8186180
sr. member
Activity: 336
Merit: 250
root@cami009:~/cpuminer-multi# LDFLAGS="-static" ./configure
[..]
checking for curl-config... /usr/bin/curl-config
checking for the version of libcurl... 7.35.0
checking for libcurl >= version 7.15.2... yes
checking whether libcurl is usable... no
configure: error: Missing required libcurl >= 7.15.2



Can you first tell why you want to link it statically?
http://www.akkadia.org/drepper/no_static_linking.html
When you use -static flag for ld, you need libcurl.a.  And "./configure --enable-static --with-pic" for curl.
legendary
Activity: 1176
Merit: 1134
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
I didnt realize the effect of PoW on block loading time. So not only is the blockchain smaller, it syncs faster. Thats faster faster!
Installs faster, runs faster, user friendly GUI and some internal improvements hard to explain to users but just having all the user visible improvements and knowing there are many more internal ones, this is very good

We can compare other cryptonotes as using a steam engine and BBR using internal combustion engine with advanced electronic injection system. Nothing wrong with a steam engine if you are using it for a locomotive.

I see the market is properly revaluing BBR to its rightful place at the top of the cryptonotes. Keep spreading the word about how good the BBR tech is and when anybody compares the two, BBR price parity goes in our rear view mirror. Next stop, marketcap parity.

Instead of "choo, choo" its "zoom zoom!"

James
sr. member
Activity: 378
Merit: 250
I tried to recreate your issue in my box. It looks like the problem is with your curl install. When I use the system curl it just works fine with the static build.

Code:
/usr/lib/x86_64-linux-gnu

Code:
 curl --version
curl 7.35.0 (x86_64-pc-linux-gnu) libcurl/7.35.0 OpenSSL/1.0.1f zlib/1.2.8 libidn/1.28 librtmp/2.3
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtmp rtsp smtp smtps telnet tftp
Features: AsynchDNS GSS-Negotiate IDN IPv6 Largefile NTLM NTLM_WB SSL libz TLS-SRP

Code:
LDFLAGS="-static" ./configure

Those other configure options that you are trying to pass to disable libs are not supported.


root@cami009:~/cpuminer-multi# curl --version
curl 7.35.0 (x86_64-pc-linux-gnu) libcurl/7.35.0 OpenSSL/1.0.1f zlib/1.2.8 libidn/1.28 librtmp/2.3
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtmp rtsp smtp smtps telnet tftp
Features: AsynchDNS GSS-Negotiate IDN IPv6 Largefile NTLM NTLM_WB SSL libz TLS-SRP



root@cami009:~/cpuminer-multi# LDFLAGS="-static" ./configure
[..]
checking for curl-config... /usr/bin/curl-config
checking for the version of libcurl... 7.35.0
checking for libcurl >= version 7.15.2... yes
checking whether libcurl is usable... no
configure: error: Missing required libcurl >= 7.15.2

hero member
Activity: 976
Merit: 646
hero member
Activity: 742
Merit: 501
hero member
Activity: 938
Merit: 1001
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.

It's available

https://bitcointalksearch.org/topic/bbr-boolberry-gpu-miner-discussion-amd-nvidia-opencl-cuda-693118

You need to use the OpenCL version.
legendary
Activity: 896
Merit: 1001
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.

It's available

https://bitcointalksearch.org/topic/bbr-boolberry-gpu-miner-discussion-amd-nvidia-opencl-cuda-693118
sr. member
Activity: 378
Merit: 250
sr. member
Activity: 378
Merit: 250
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



root@cami001:~/curl-7.37.1# ./configure --disable-ftp --disable-ldap --disable-ldaps --disable-rtsp --disable-proxy --disable-dict --disable-telnet --disable-tftp --disable-pop3 --disable-imap --disable-smtp --disable-gopher --disable-manual --disable-ipv6 --disable-verbose --disable-sspi --disable-crypto-auth --disable-ntlm-wb --disable-tls-srp --disable-cookies --disable-soname-bump --without-zlib --without-winssl --without-darwinssl --without-ssl --without-gnutls --without-polarssl --without-cyassl --without-nss --without-axtls --without-libmetalink --without-libssh2 --without-librtmp --without-winidn --without-libidn --without-nghttp2 --prefix=/tmp/curl
root@cami001:~/curl-7.37.1# make -j 20; make install

root@cami001:~/cpuminer-multi# CFLAGS="-I/tmp/curl/include" LDFLAGS="-static -L/tmp/curl/lib" ./configure --with-libcurl=/tmp/curl
[..]
checking for curl_free... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating compat/Makefile
config.status: creating compat/jansson/Makefile
config.status: creating cpuminer-config.h
config.status: cpuminer-config.h is unchanged
config.status: executing depfiles commands


root@cami001:~/cpuminer-multi# make
[..]
gcc -std=gnu99 -std=gnu11 -O3 -march=native -fPIC -flto  -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 compat/jansson/libjansson.a -lpthread  
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/4.9/crtbeginT.o: relocation R_X86_64_32 against `__TMC_END__' can not be used when making a shared object; recompile with -fPIC
/usr/lib/gcc/x86_64-linux-gnu/4.9/crtbeginT.o: error adding symbols: Bad value
collect2: error: 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


root@cami001:~/cpuminer-multi# gcc --version
gcc (Ubuntu 4.9.1-3ubuntu2~14.04.1) 4.9.1

legendary
Activity: 1582
Merit: 1019
011110000110110101110010
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.
sr. member
Activity: 378
Merit: 250
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..
hero member
Activity: 742
Merit: 501
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
sr. member
Activity: 378
Merit: 250
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
legendary
Activity: 1456
Merit: 1000
As BTC-Mike is involved, if you can get DwarfPool on board, I'll point some mining rigs onto BBR.

Cheers.
hero member
Activity: 532
Merit: 500
You got my post wrong, i just explained why its "less bloated" currently.

Sorry for misinterpreting. Smiley  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.

dga
hero member
Activity: 737
Merit: 511
You got my post wrong, i just explained why its "less bloated" currently.

Sorry for misinterpreting. Smiley  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?
hero member
Activity: 976
Merit: 646
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 Smiley! After that i hope discussion will be over.

Zoidberg
Jump to: