|
Happy New Year friends!
Sorry for long delay with new version, we(me, Bitcrea, Scruffy) still finalizing and fixing bugs in new build. Hope it will come in next week.
I want to wish a luck to evey person related with crypto, i hope we are making this world better!
Zoidberg
|
|
|
|
I'm trying to install Boolberry wallet headless in Ubuntu. As far as i know it needs libboost1.55-all-dev which can be downloaded from repo ppa:boost-latest/ppa. But if i do sudo apt-get -y install gcc-4.8 g++-4.8 libboost1.55-all-dev git cmake, i get this: $ sudo apt-get -y install gcc-4.8 g++-4.8 libboost1.55-all-dev git cmake
Reading package lists... Done
Building dependency tree
Reading state information... Done
cmake is already the newest version.
g++-4.8 is already the newest version.
g++-4.8 set to manually installed.
gcc-4.8 is already the newest version.
gcc-4.8 set to manually installed.
git is already the newest version.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libboost1.55-all-dev : Depends: libboost1.55-dev but it is not going to be installed
Depends: libboost1.55-tools-dev
Depends: libboost-atomic1.55-dev but it is not going to be installed
Depends: libboost-chrono1.55-dev but it is not going to be installed
Depends: libboost-context1.55-dev but it is not going to be installed
Depends: libboost-coroutine1.55-dev but it is not going to be installed
Depends: libboost-date-time1.55-dev but it is not going to be installed
Depends: libboost-exception1.55-dev but it is not going to be installed
Depends: libboost-filesystem1.55-dev but it is not going to be installed
Depends: libboost-graph1.55-dev but it is not going to be installed
Depends: libboost-graph-parallel1.55-dev but it is not going to be installed
Depends: libboost-iostreams1.55-dev but it is not going to be installed
Depends: libboost-locale1.55-dev but it is not going to be installed
Depends: libboost-log1.55-dev but it is not going to be installed
Depends: libboost-math1.55-dev but it is not going to be installed
Depends: libboost-mpi1.55-dev but it is not going to be installed
Depends: libboost-mpi-python1.55-dev but it is not going to be installed
Depends: libboost-program-options1.55-dev but it is not going to be installed
Depends: libboost-python1.55-dev but it is not going to be installed
Depends: libboost-random1.55-dev but it is not going to be installed
Depends: libboost-regex1.55-dev but it is not going to be installed
Depends: libboost-serialization1.55-dev but it is not going to be installed
Depends: libboost-signals1.55-dev but it is not going to be installed
Depends: libboost-system1.55-dev but it is not going to be installed
Depends: libboost-test1.55-dev but it is not going to be installed
Depends: libboost-thread1.55-dev but it is not going to be installed
Depends: libboost-timer1.55-dev but it is not going to be installed
Depends: libboost-wave1.55-dev but it is not going to be installed
E: Unable to correct problems, you have held broken packages. Anyone an idea how to solve this? EDIT: i had to install libboost1.55-dev first But now i got this: $ cd boolberry; make -j
mkdir -p build/release
cd build/release && cmake -D CMAKE_BUILD_TYPE=Release ../..
-- Boost version: 1.55.0
-- Found the following Boost libraries:
-- system
-- filesystem
-- thread
-- date_time
-- chrono
-- regex
-- serialization
-- atomic
-- program_options
-- Found Git: /usr/bin/git
-- Configuring done
-- Generating done
-- Build files have been written to: /home/badass/boolberry/build/release
cd build/release && make
make[1]: Entering directory `/home/badass/boolberry/build/release'
make[2]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Leaving directory `/home/badass/boolberry/build/release'
[ 1%] [ 14%] [ 15%] make[3]: Leaving directory `/home/badass/boolberry/build/release'
Building CXX object src/CMakeFiles/common.dir/common/util.cpp.o
Built target upnpc-static
[ 27%] Building CXX object src/CMakeFiles/common.dir/common/base58.cpp.o
[ 27%] [ 33%] Built target crypto
Built target version
Built target crypto-tests
make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[3]: Leaving directory `/home/badass/boolberry/build/release'
Scanning dependencies of target hash-tests
make[3]: Entering directory `/home/badass/boolberry/build/release'
[ 34%] make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
[ 35%] make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
[ 36%] [ 37%] Built target gtest
[ 38%] [ 39%] make[3]: Entering directory `/home/badass/boolberry/build/release'
Building CXX object src/CMakeFiles/currency_core.dir/currency_core/tx_pool.cpp.o
[ 40%] Building CXX object src/CMakeFiles/currency_core.dir/currency_core/currency_format_utils.cpp.o
Building CXX object src/CMakeFiles/rpc.dir/rpc/core_rpc_server.cpp.o
Building CXX object src/CMakeFiles/wallet.dir/wallet/wallet_rpc_server.cpp.o
Scanning dependencies of target gtest_main
Building CXX object tests/CMakeFiles/hash-tests.dir/hash/main.cpp.o
Building CXX object src/CMakeFiles/wallet.dir/wallet/wallet2.cpp.o
make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
[ 41%] Building CXX object tests/gtest/CMakeFiles/gtest_main.dir/src/gtest_main.cc.o
Linking CXX executable hash-tests
Linking CXX static library libgtest_main.a
make[3]: Leaving directory `/home/badass/boolberry/build/release'
[ 41%] Built target gtest_main
make[3]: Leaving directory `/home/badass/boolberry/build/release'
[ 41%] Built target hash-tests
Linking CXX static library libcommon.a
make[3]: Leaving directory `/home/badass/boolberry/build/release'
[ 41%] Built target common
Linking CXX static library libcurrency_core.a
make[3]: Leaving directory `/home/badass/boolberry/build/release'
[ 48%] Built target currency_core
make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
Scanning dependencies of target connectivity_tool
make[3]: Entering directory `/home/badass/boolberry/build/release'
Scanning dependencies of target simpleminer
make[3]: Entering directory `/home/badass/boolberry/build/release'
Scanning dependencies of target core_proxy
make[3]: Entering directory `/home/badass/boolberry/build/release'
Scanning dependencies of target coretests
make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
Scanning dependencies of target difficulty-tests
Scanning dependencies of target net_load_tests_clt
make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[3]: Leaving directory `/home/badass/boolberry/build/release'
Scanning dependencies of target hash-target-tests
make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Leaving directory `/home/badass/boolberry/build/release'
[ 49%] make[3]: Entering directory `/home/badass/boolberry/build/release'
Scanning dependencies of target net_load_tests_srv
make[3]: Entering directory `/home/badass/boolberry/build/release'
[ 50%] make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
Scanning dependencies of target performance_tests
make[3]: Leaving directory `/home/badass/boolberry/build/release'
Building CXX object tests/CMakeFiles/core_proxy.dir/core_proxy/core_proxy.cpp.o
[ 51%] [ 52%] make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
[ 53%] make[3]: Entering directory `/home/badass/boolberry/build/release'
make[3]: Leaving directory `/home/badass/boolberry/build/release'
[ 54%] Building CXX object src/CMakeFiles/connectivity_tool.dir/connectivity_tool/conn_tool.cpp.o
Building CXX object tests/CMakeFiles/difficulty-tests.dir/difficulty/difficulty.cpp.o
make[3]: Entering directory `/home/badass/boolberry/build/release'
Building CXX object src/CMakeFiles/simpleminer.dir/miner/simpleminer.cpp.o
[ 55%] Building CXX object tests/CMakeFiles/hash-target-tests.dir/hash-target.cpp.o
Building CXX object tests/CMakeFiles/net_load_tests_srv.dir/net_load_tests/srv.cpp.o
[ 56%] Building CXX object tests/CMakeFiles/net_load_tests_clt.dir/net_load_tests/clt.cpp.o
Building CXX object tests/CMakeFiles/performance_tests.dir/performance_tests/main.cpp.o
Linking CXX executable core_proxy
make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[3]: Entering directory `/home/badass/boolberry/build/release'
[ 57%] [ 58%] [ 59%] Building CXX object tests/CMakeFiles/coretests.dir/core_tests/pruning_ring_signatures.cpp.o
Building CXX object tests/CMakeFiles/coretests.dir/core_tests/double_spend.cpp.o
[ 60%] Building CXX object tests/CMakeFiles/coretests.dir/core_tests/block_reward.cpp.o
[ 61%] Building CXX object tests/CMakeFiles/coretests.dir/core_tests/block_validation.cpp.o
[ 62%] [ 63%] Building CXX object tests/CMakeFiles/coretests.dir/core_tests/tx_validation.cpp.o
Building CXX object tests/CMakeFiles/coretests.dir/core_tests/chain_switch_1.cpp.o
Building CXX object tests/CMakeFiles/coretests.dir/core_tests/integer_overflow.cpp.o
[ 64%] Building CXX object tests/CMakeFiles/coretests.dir/core_tests/chaingen_main.cpp.o
[ 65%] [ 66%] [ 67%] make[3]: Leaving directory `/home/badass/boolberry/build/release'
Building CXX object tests/CMakeFiles/coretests.dir/core_tests/chaingen001.cpp.o
Building CXX object tests/CMakeFiles/coretests.dir/core_tests/mixin_attr.cpp.o
[ 67%] [ 68%] Building CXX object tests/CMakeFiles/coretests.dir/core_tests/ring_signature_1.cpp.o
Built target core_proxy
Building CXX object tests/CMakeFiles/coretests.dir/core_tests/alias_tests.cpp.o
[ 69%] [ 70%] [ 71%] Building CXX object tests/CMakeFiles/coretests.dir/core_tests/get_random_outs.cpp.o
Building CXX object tests/CMakeFiles/coretests.dir/core_tests/transaction_tests.cpp.o
[ 72%] Building CXX object tests/CMakeFiles/coretests.dir/core_tests/chaingen.cpp.o
Building CXX object tests/CMakeFiles/coretests.dir/core_tests/chain_split_1.cpp.o
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions.
make[3]: *** [src/CMakeFiles/rpc.dir/rpc/core_rpc_server.cpp.o] Error 4
make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[2]: *** [src/CMakeFiles/rpc.dir/all] Error 2
make[2]: *** Waiting for unfinished jobs....
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions.
make[3]: *** [tests/CMakeFiles/coretests.dir/core_tests/chaingen001.cpp.o] Error 4
make[3]: *** Waiting for unfinished jobs....
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions.
make[3]: *** [src/CMakeFiles/wallet.dir/wallet/wallet2.cpp.o] Error 4
make[3]: *** Waiting for unfinished jobs....
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions.
make[3]: *** [tests/CMakeFiles/coretests.dir/core_tests/chaingen_main.cpp.o] Error 4
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions.
make[3]: *** [tests/CMakeFiles/net_load_tests_clt.dir/net_load_tests/clt.cpp.o] Error 4
make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[2]: *** [tests/CMakeFiles/net_load_tests_clt.dir/all] Error 2
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions.
make[3]: *** [tests/CMakeFiles/hash-target-tests.dir/hash-target.cpp.o] Error 4
make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[2]: *** [tests/CMakeFiles/hash-target-tests.dir/all] Error 2
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions.
make[3]: *** [tests/CMakeFiles/coretests.dir/core_tests/chain_switch_1.cpp.o] Error 4
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions.
make[3]: *** [tests/CMakeFiles/coretests.dir/core_tests/block_reward.cpp.o] Error 4
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions.
make[3]: *** [tests/CMakeFiles/coretests.dir/core_tests/chain_split_1.cpp.o] Error 4
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions.
make[3]: *** [src/CMakeFiles/wallet.dir/wallet/wallet_rpc_server.cpp.o] Error 4
make[3]: Leaving directory `/home/badass/boolberry/build/release'
make[2]: *** [src/CMakeFiles/wallet.dir/all] Error 2
Linking CXX executable difficulty-tests
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions.
make[3]: *** [tests/CMakeFiles/coretests.dir/core_tests/chaingen.cpp.o] Error 4
Connection to 89.248.X.X closed by remote host.
Connection to 89.248.X.X closed. It also shuts down my VPS all of a sudden....did it twice. Anyone has an idea? Seems that you try to complie project on VPS which is usualy ha e low RAM, and even worse - you try to do that with "-j" parametr, that to complie with multiple processes. I recommend you to do following: 1. run "make" without -j key 2. enable virtual memory on VPS if it is not enableed yet. 3. increase size of RAM (at least 1-2GB) This should helps. Let me know it is still not working. Zoidberg |
|
|
|
Boolberry's a great name. Not sure about Louis d'Or yet.
Zoidberg, who are your friends and why are they wanting you to make this coin?
All i can say that this is group of enthusiastic people, who spent about 2 years learning crypto-currencies and actually have strong marketing and economics background. As is see - with this project they want to build currency as a friendly and clear product, that will be close to fiat money as well. I actually can't reveal more detalis atm - keep watching. Zoidberg |
|
|
|
Boolberry, Louisd'or
You're a good dev but not at finding names...
I could agree with you, but "Louisd'or" is just a codename, and it was chosen by different team, as i said - i do this project for my friends, but i responsible only for technical stuff here. Zoidberg |
|
|
|
|
Hey guys!
Boostrap nodes was offline for some time due to hoster's problems (nodes was restarted).
Now everything is fine!
Zoidberg
|
|
|
|
So nice to have trolls around.
I've had my eyes on Boolberry for months now out of all CryptoNote currencies it's the best out there with a real chance of achieving success. oh  I'm a troll right! btw you make it Doged 3 compulsive liers 0. So where's the whitepaper? Can you post this question in Doged's thread?? Not ethical to discuss it here  Btw any real reason why the price for bbr still falling? Because of many reasons, but first is the long waiting for next build i guess. Zoidberg |
|
|
|
For people who want full anonymity right down to the network level Teleport(network level anonymity) and BBR(unlinkable inputs and outputs) is the solution. And the only way to use those two technologies together is via SuperNET. So BBR is a critical piece of the privacy puzzle.
And SuperNET itself is a massive project to increase adoption of currencies. In fact ~$100k was just budgeted for marketing to start off 2015. BBR being a core part of SuperNET is a big deal. I myself am working on a SuperNET related project that will target real world use and I hope to be able to include BBR in my plans as well.
SuperNET intends to grow a large user base and as a result of that BBR should gain users as well since it is quite good itself.
I'm sorry but this is not true. I already challenged the Monero team when they compared Monero to DarkCoin AnonCoin, etc to compare it with DogeCoinDark and they ran from it. Mind you it was the second time as the first time a lady blogger in another thread said how it's impossible to achieve anonymity again I challenged her facts and she ran from the discussion. The only coin out there that can achieved practical anonymity it a "free coin" what all others are promising for months DogeCoinDark and the only reason I'm posting this is because you statement is false and misleading. wtf is DogeCoinDark ? |
|
|
|
BTW: we still have some 4-5 BTC for people who'll find a flaws!
Zoidberg
"BTW: we still have some 4-5 BTC for people who'll find a flaws!" should read "BTW: We still have 4-5 BTC for anyone who finds flaws!" That'll be 4-5 BTC please. 18YJ3QPWA6XgDLMTfQ8ov6sJXUoSxNcpBw Fixed |
|
|
|
|
BTW: we still have 4-5 BTC for people who'll find a flaws!
Zoidberg
|
|
|
|
Hey folk, seems that it was first success test network launch. Here is difficulty behaviour graph(just FYI):  Actually redline shows adjusted difficulty that used for cumulative difficulty, that used for switching blockchain. There also blue points of PoW difficulty under red points, but googl's spreadsheets not so flexible to let it shown both. Next iteration will lead code to more close-to-white-paper imlementation, network will be restarted in next 1-2 days. Zoidberg |
|
|
|
Hi Guys Just a couple of thoughts, CZ announcing a new project is pretty cool. People that can make things happen have that choice, and I know most if not all would agree that CZ has the ability and integrity to do it. However the more interesting question for me at least, is what name will the new coin have? After the amount that were submitted here a while ago.  On a more serious note, I would be happy to send a miner CZs way if we get a heads up here about the new project before its release. I think it would be a great chance to get in on the ground floor with a trusted DEV It would be a first for me at least. Jon  For Lui project i'm responsibe for research and development team. Marketing and business is doing by other group of people. |
|
|
|
I feel this is a betrayal of loyal BBR investors/supporters. Why not eventually add POS to BBR? Is there any plan to distribute any of the new coins to BBR bag holders?  I'll write it only once for all who interested. There was two ways to survive: 1. Transform BBR to some kind of scam with hard fork (any radical changes gonna be scam, including converting BBR into a PoS, since many people don't like PoS coins) and to seize money from BBR. This would be true betrayal. As you may know, i've decided to not kill this project in that way, since i have a future plans for this project. 2. The second was to work out some other interesting project with the same codebase, to cover live spendings, and to keep BBR as it originally was conceived. I've chosed second way. Befor new year we going to release new GUI, and next release will be the new wallet mode, that actualy utilize fully anonymouse outputs feature. But still, if someone don't like this my attitude - i don't have time and intention to convince you - feel free to quit. Zoidberg |
|
|
|
Just to be clear, this is still just testnet?
Yes, this is definately testnet! And this testnet is usualy restarted every 2-3 days since i add some changes or do some experiments. Everyone is free to hack or broke this net! Zoidberg |
|
|
|
how fat(er) will become the blockchain with all these additional transaction ?
What additional transactions you mean? |
|
|
|
Hello folk! During last weeks I was working on CN-based PoS project for my friends and i’m happy to introduce this work for technical review if anyone interested. As i said, this is CryptoNote-based PoS/PoW hybrid, it seems to be first anonymous PoS project (PoS mining is also anonymous). According to my experience in bitcointalk forum here is a lot of people who like to criticize my work, especially from Monero clan, so you guys is welcome to fight! We have about 4-5 BTC of bounties for people who gonna find bugs/flaws in design or implementation: most serious critical flaw gonna get 2 BTC, next less critical 1 BTC, next 0.5 BTC and so on. Here is thread for discussion: https://bitcointalk.org/index.php?topic=887482PS About Boolberry: In any case Boolbery is my primary project, and since both this projects based on the same code base - it will be win-win for both of this project from technology point of view. ATM scruffy is working on BBR new wallet version since i want to have second developer who familiar with BBR code, so this took more time that i expected, but this is need for project safety, a lot of people were talked about it before in this thread. Zoidberg |
|
|
|
Hello! I’m glad to announce our project, that we were working on last weeks and keep working on. This is CryptoNote-based currency with first anonymous PoS engine(that use PoW as well). This is the part of big project (which have codename Louisd’or), that we do for my friends, so this is just technology announce and first rough implementation of CN-based PoS, and working network, this is more like proposal, so i shared this to get public review and feedback about PoS approach we gonna use. The “Louisd’or” project itself have a wide feature list and have a lot of development ahead, so we have a great team of talented people who worked on this, and expect to release it in the middle of spring. According to my experience in bitcointalk forum, here is a lot of people who like to criticize my work, especially from Monero clan, so you guys is welcome to fight! We have about 4-5 BTC of bounties for people who gonna find bugs/flaws in design or implementation: most serious critical flaw gonna get 2 BTC, next less critical 1 BTC, next 0.5 BTC and so on. Brief description link(mini-whitepaper): http://162.243.101.90/lui_share.pdfImplementation: https://github.com/cryptobender/luiNotice: Implementation does not completely reflect mini-whitepaper description, it still in development, so i often do some commits and restart test network every 2-3 days. Atm we have network that running about of couple of days and seems to be okay. Feel free to post any questions and ideas here or to PM. Zoidberg |
|
|
|
Hey guys! I'm back Now have internet, and can work, again! How is it going ? Congratulations on your successful relocation!  Thanks! |
|
|
|
Hey guys! I'm back Now have internet, and can work, again! How is it going ? |
|
|
|
|
Hey guys!
I was changed my location to different country and now looking for home, where i could live and work, so this explains my rare activity on forum and development - i'm literally can't work atm.
Anyway, i'm in touch with Bitcrea and Scruffy, and some other people with skype, so no worries folk!
Zoidberg
|
|
|
|
I forgot about that video. I like the first one as well. I like the others also but they seem a little too glitzy. That look is great for a video game intro. No disrespect to the author of the video. They have skills for sure. The first one just seems more clean and professional for a cryptocurrency. But that's just my opinion. As i know (i was talked with guy who made this video) this animation was build on some template scripts, so it was just rendered for Boolberry, but actually there could be any text or image. |
|
|
|
|
Show Posts
