★★DigiByte|极特币★★[DGB]✔ Core v6.16.5.1 - DigiShield, DigiSpeed, Segwit

[piratfx]

Change simple scrypt to other metod  NOW, coz as we see on cryptys, big asic miners attacking ! >
014-04-23 03:59:36   Sell   0.00000031   4972.15164604   0.00154137
2014-04-23 03:59:36   Sell   0.00000031   7801.99002191   0.00241862
2014-04-23 03:59:36   Sell   0.00000031   7801.99002164   0.00241862
2014-04-23 03:59:36   Sell   0.00000031   4423.86831041   0.00137140
2014-04-23 03:59:36   Sell   0.00000031   7801.99002396   0.00241862
2014-04-23 03:58:43   Sell   0.00000031   7801.99002100   0.00241862
2014-04-23 03:58:42   Sell   0.00000031   7801.99002143   0.00241862
2014-04-23 03:58:41   Sell   0.00000031   7801.99002164   0.00241862
2014-04-23 03:58:41   Sell   0.00000031   7801.99002191   0.00241862
2014-04-23 03:58:41   Sell   0.00000031   7801.99002396   0.00241862
2014-04-23 03:58:41   Sell   0.00000031   7801.99002296   0.00241862
2014-04-23 03:58:41   Sell   0.00000031   7801.99002228   0.00241862
2014-04-23 03:57:51   Sell   0.00000031   7801.99002191   0.00241862
2014-04-23 03:57:51   Sell   0.00000031   7801.99002100   0.00241862
2014-04-23 03:57:50   Sell   0.00000031   7801.99002143   0.00241862
2014-04-23 03:57:49   Sell   0.00000031   7801.99002164   0.00241862
2014-04-23 03:57:49   Sell   0.00000031   7801.99002296   0.00241862
2014-04-23 03:57:49   Sell   0.00000031   7801.99002396   0.00241862
2014-04-23 03:57:49   Sell   0.00000031   7801.99002228   0.00241862
2014-04-23 03:56:53   Sell   0.00000031   7801.99002191   0.00241862
2014-04-23 03:56:49   Sell   0.00000031   7219.91217977   0.00223817
2014-04-23 03:56:50   Sell   0.00000031   7801.99002100   0.00241862
2014-04-23 03:56:50   Sell   0.00000031   7801.99002143   0.00241862
2014-04-23 03:56:49   Sell   0.00000031   7801.99002396   0.00241862
2014-04-23 03:56:49   Sell   0.00000031   582.07784319   0.00018044
2014-04-23 03:56:49   Sell   0.00000031   7801.99002164   0.00241862
2014-04-23 03:56:49   Sell   0.00000031   7801.99002228   0.00241862
2014-04-23 03:54:31   Sell   0.00000031   7801.99002100   0.00241862
2014-04-23 03:54:30   Sell   0.00000031   7801.99002143   0.00241862
2014-04-23 03:54:29   Sell   0.00000031   7801.99002191   0.00241862

[1715214437]

1715214437

[Moxymore]

Change simple scrypt to other metod  NOW, coz as we see on cryptys, big asic miners attacking ! >
014-04-23 03:59:36   Sell   0.00000031   4972.15164604   0.00154137
2014-04-23 03:59:36   Sell   0.00000031   7801.99002191   0.00241862
2014-04-23 03:59:36   Sell   0.00000031   7801.99002164   0.00241862
2014-04-23 03:59:36   Sell   0.00000031   4423.86831041   0.00137140
2014-04-23 03:59:36   Sell   0.00000031   7801.99002396   0.00241862
2014-04-23 03:58:43   Sell   0.00000031   7801.99002100   0.00241862
2014-04-23 03:58:42   Sell   0.00000031   7801.99002143   0.00241862
2014-04-23 03:58:41   Sell   0.00000031   7801.99002164   0.00241862
2014-04-23 03:58:41   Sell   0.00000031   7801.99002191   0.00241862
2014-04-23 03:58:41   Sell   0.00000031   7801.99002396   0.00241862
2014-04-23 03:58:41   Sell   0.00000031   7801.99002296   0.00241862
2014-04-23 03:58:41   Sell   0.00000031   7801.99002228   0.00241862
2014-04-23 03:57:51   Sell   0.00000031   7801.99002191   0.00241862
2014-04-23 03:57:51   Sell   0.00000031   7801.99002100   0.00241862
2014-04-23 03:57:50   Sell   0.00000031   7801.99002143   0.00241862
2014-04-23 03:57:49   Sell   0.00000031   7801.99002164   0.00241862
2014-04-23 03:57:49   Sell   0.00000031   7801.99002296   0.00241862
2014-04-23 03:57:49   Sell   0.00000031   7801.99002396   0.00241862
2014-04-23 03:57:49   Sell   0.00000031   7801.99002228   0.00241862
2014-04-23 03:56:53   Sell   0.00000031   7801.99002191   0.00241862
2014-04-23 03:56:49   Sell   0.00000031   7219.91217977   0.00223817
2014-04-23 03:56:50   Sell   0.00000031   7801.99002100   0.00241862
2014-04-23 03:56:50   Sell   0.00000031   7801.99002143   0.00241862
2014-04-23 03:56:49   Sell   0.00000031   7801.99002396   0.00241862
2014-04-23 03:56:49   Sell   0.00000031   582.07784319   0.00018044
2014-04-23 03:56:49   Sell   0.00000031   7801.99002164   0.00241862
2014-04-23 03:56:49   Sell   0.00000031   7801.99002228   0.00241862
2014-04-23 03:54:31   Sell   0.00000031   7801.99002100   0.00241862
2014-04-23 03:54:30   Sell   0.00000031   7801.99002143   0.00241862
2014-04-23 03:54:29   Sell   0.00000031   7801.99002191   0.00241862

Asics, maybe, but i'm not sure for DGB. It's multipools who are usually doing this on DGB markets.

[piratfx]

Change simple scrypt to other metod  NOW, coz as we see on cryptys, big asic miners attacking ! >
014-04-23 03:59:36   Sell   0.00000031   4972.15164604   0.00154137
2014-04-23 03:59:36   Sell   0.00000031   7801.99002191   0.00241862
2014-04-23 03:59:36   Sell   0.00000031   7801.99002164   0.00241862
2014-04-23 03:59:36   Sell   0.00000031   4423.86831041   0.00137140
2014-04-23 03:59:36   Sell   0.00000031   7801.99002396   0.00241862
2014-04-23 03:58:43   Sell   0.00000031   7801.99002100   0.00241862
2014-04-23 03:58:42   Sell   0.00000031   7801.99002143   0.00241862
2014-04-23 03:58:41   Sell   0.00000031   7801.99002164   0.00241862
2014-04-23 03:58:41   Sell   0.00000031   7801.99002191   0.00241862
2014-04-23 03:58:41   Sell   0.00000031   7801.99002396   0.00241862
2014-04-23 03:58:41   Sell   0.00000031   7801.99002296   0.00241862
2014-04-23 03:58:41   Sell   0.00000031   7801.99002228   0.00241862
2014-04-23 03:57:51   Sell   0.00000031   7801.99002191   0.00241862
2014-04-23 03:57:51   Sell   0.00000031   7801.99002100   0.00241862
2014-04-23 03:57:50   Sell   0.00000031   7801.99002143   0.00241862
2014-04-23 03:57:49   Sell   0.00000031   7801.99002164   0.00241862
2014-04-23 03:57:49   Sell   0.00000031   7801.99002296   0.00241862
2014-04-23 03:57:49   Sell   0.00000031   7801.99002396   0.00241862
2014-04-23 03:57:49   Sell   0.00000031   7801.99002228   0.00241862
2014-04-23 03:56:53   Sell   0.00000031   7801.99002191   0.00241862
2014-04-23 03:56:49   Sell   0.00000031   7219.91217977   0.00223817
2014-04-23 03:56:50   Sell   0.00000031   7801.99002100   0.00241862
2014-04-23 03:56:50   Sell   0.00000031   7801.99002143   0.00241862
2014-04-23 03:56:49   Sell   0.00000031   7801.99002396   0.00241862
2014-04-23 03:56:49   Sell   0.00000031   582.07784319   0.00018044
2014-04-23 03:56:49   Sell   0.00000031   7801.99002164   0.00241862
2014-04-23 03:56:49   Sell   0.00000031   7801.99002228   0.00241862
2014-04-23 03:54:31   Sell   0.00000031   7801.99002100   0.00241862
2014-04-23 03:54:30   Sell   0.00000031   7801.99002143   0.00241862
2014-04-23 03:54:29   Sell   0.00000031   7801.99002191   0.00241862

Asics, maybe, but i'm not sure for DGB. It's multipools who are usually doing this on DGB markets.

This is not multipools coz as U see there is amount of one block ( 7801.99002191 ) in every 5-10 sec. , on cryptsy is option " auto selling" that's why we see this ( and now is time for ASIC ... ). I think this is unfair ASIC VS simple GPU, DEVS just talking about changing but soo far nothing really happend, and ASIC miners makeing milions per day when I making 20 000 per day with GPU ... .

[piratfx]

DGB is really good coin, have big community, but nothing really happend, there is no new merchants , no new ideas. Price 0.00000035 ?? , it's the most non profitable coin for now for GPU miners, and this price is not fault of greate community ...

[Magice]

Hi, I have seen this story: http://www.followthecoin.com/blackcoin-supports-dogecon-first-coin-to-ever-support-a-conference/

It would be interesting, given the good relations with the doge, also supporting the conference as bc. Would give us a lot of publicity. Since they are three major communities, would be great to work together. For many of the functions that we would have to digi participate and make a good revenue collection.

Also would recommend enlarging the link to the video of the conference on the first page because it goes very unnoticed.

I think Jared did a fantastic presentation and everyone should see it.

I am convinced that the digi reached the proper place, but it is essential to have one person do the work of marketing, someone experienced.

Thanks for the good work

[Bitock]

How I can to compile the linux wallet. I perform qmake USE_UPNP=- and get next. What I am doing wrong? Help!

try qmake "USE_UPNP=1" or 0

The building process has changed some with the new client. Make sure your up to date with the git repository and run the following to compile.

Code:

./autogen.sh
./configure
make

The complete guide for building on linux can be found at https://github.com/digibyte/DigiByteProject/blob/master/doc/build-unix.md

Thanks! But after make I get next:

make: *** No targets specified and no makefile found.  Stop.

ls -l DigiByteProject-master

Specify which file for the make?

HELP!!!

[Moxymore]

Change simple scrypt to other metod  NOW, coz as we see on cryptys, big asic miners attacking ! >
014-04-23 03:59:36   Sell   0.00000031   4972.15164604   0.00154137
2014-04-23 03:59:36   Sell   0.00000031   7801.99002191   0.00241862
2014-04-23 03:59:36   Sell   0.00000031   7801.99002164   0.00241862
2014-04-23 03:59:36   Sell   0.00000031   4423.86831041   0.00137140
2014-04-23 03:59:36   Sell   0.00000031   7801.99002396   0.00241862
2014-04-23 03:58:43   Sell   0.00000031   7801.99002100   0.00241862
2014-04-23 03:58:42   Sell   0.00000031   7801.99002143   0.00241862
2014-04-23 03:58:41   Sell   0.00000031   7801.99002164   0.00241862
2014-04-23 03:58:41   Sell   0.00000031   7801.99002191   0.00241862
2014-04-23 03:58:41   Sell   0.00000031   7801.99002396   0.00241862
2014-04-23 03:58:41   Sell   0.00000031   7801.99002296   0.00241862
2014-04-23 03:58:41   Sell   0.00000031   7801.99002228   0.00241862
2014-04-23 03:57:51   Sell   0.00000031   7801.99002191   0.00241862
2014-04-23 03:57:51   Sell   0.00000031   7801.99002100   0.00241862
2014-04-23 03:57:50   Sell   0.00000031   7801.99002143   0.00241862
2014-04-23 03:57:49   Sell   0.00000031   7801.99002164   0.00241862
2014-04-23 03:57:49   Sell   0.00000031   7801.99002296   0.00241862
2014-04-23 03:57:49   Sell   0.00000031   7801.99002396   0.00241862
2014-04-23 03:57:49   Sell   0.00000031   7801.99002228   0.00241862
2014-04-23 03:56:53   Sell   0.00000031   7801.99002191   0.00241862
2014-04-23 03:56:49   Sell   0.00000031   7219.91217977   0.00223817
2014-04-23 03:56:50   Sell   0.00000031   7801.99002100   0.00241862
2014-04-23 03:56:50   Sell   0.00000031   7801.99002143   0.00241862
2014-04-23 03:56:49   Sell   0.00000031   7801.99002396   0.00241862
2014-04-23 03:56:49   Sell   0.00000031   582.07784319   0.00018044
2014-04-23 03:56:49   Sell   0.00000031   7801.99002164   0.00241862
2014-04-23 03:56:49   Sell   0.00000031   7801.99002228   0.00241862
2014-04-23 03:54:31   Sell   0.00000031   7801.99002100   0.00241862
2014-04-23 03:54:30   Sell   0.00000031   7801.99002143   0.00241862
2014-04-23 03:54:29   Sell   0.00000031   7801.99002191   0.00241862

Asics, maybe, but i'm not sure for DGB. It's multipools who are usually doing this on DGB markets.

This is not multipools coz as U see there is amount of one block ( 7801.99002191 ) in every 5-10 sec. , on cryptsy is option " auto selling" that's why we see this ( and now is time for ASIC ... ). I think this is unfair ASIC VS simple GPU, DEVS just talking about changing but soo far nothing really happend, and ASIC miners makeing milions per day when I making 20 000 per day with GPU ... .

We have to wait, dev's are working hard on their project. You have (like for us) to wait. Digibyte has said few days ago that some interesting news will be revealed soon. And, moreover, DGB is a coin with long term view... so, be patient enough.

[Bitock]

I don't understand who it doing!!!!! I can't find the file makefile.unix. Where is it?

[DigiByte]

Change simple scrypt to other metod  NOW, coz as we see on cryptys, big asic miners attacking ! >
014-04-23 03:59:36   Sell   0.00000031   4972.15164604   0.00154137
2014-04-23 03:59:36   Sell   0.00000031   7801.99002191   0.00241862
2014-04-23 03:59:36   Sell   0.00000031   7801.99002164   0.00241862
2014-04-23 03:59:36   Sell   0.00000031   4423.86831041   0.00137140
2014-04-23 03:59:36   Sell   0.00000031   7801.99002396   0.00241862
2014-04-23 03:58:43   Sell   0.00000031   7801.99002100   0.00241862
2014-04-23 03:58:42   Sell   0.00000031   7801.99002143   0.00241862
2014-04-23 03:58:41   Sell   0.00000031   7801.99002164   0.00241862
2014-04-23 03:58:41   Sell   0.00000031   7801.99002191   0.00241862
2014-04-23 03:58:41   Sell   0.00000031   7801.99002396   0.00241862
2014-04-23 03:58:41   Sell   0.00000031   7801.99002296   0.00241862
2014-04-23 03:58:41   Sell   0.00000031   7801.99002228   0.00241862
2014-04-23 03:57:51   Sell   0.00000031   7801.99002191   0.00241862
2014-04-23 03:57:51   Sell   0.00000031   7801.99002100   0.00241862
2014-04-23 03:57:50   Sell   0.00000031   7801.99002143   0.00241862
2014-04-23 03:57:49   Sell   0.00000031   7801.99002164   0.00241862
2014-04-23 03:57:49   Sell   0.00000031   7801.99002296   0.00241862
2014-04-23 03:57:49   Sell   0.00000031   7801.99002396   0.00241862
2014-04-23 03:57:49   Sell   0.00000031   7801.99002228   0.00241862
2014-04-23 03:56:53   Sell   0.00000031   7801.99002191   0.00241862
2014-04-23 03:56:49   Sell   0.00000031   7219.91217977   0.00223817
2014-04-23 03:56:50   Sell   0.00000031   7801.99002100   0.00241862
2014-04-23 03:56:50   Sell   0.00000031   7801.99002143   0.00241862
2014-04-23 03:56:49   Sell   0.00000031   7801.99002396   0.00241862
2014-04-23 03:56:49   Sell   0.00000031   582.07784319   0.00018044
2014-04-23 03:56:49   Sell   0.00000031   7801.99002164   0.00241862
2014-04-23 03:56:49   Sell   0.00000031   7801.99002228   0.00241862
2014-04-23 03:54:31   Sell   0.00000031   7801.99002100   0.00241862
2014-04-23 03:54:30   Sell   0.00000031   7801.99002143   0.00241862
2014-04-23 03:54:29   Sell   0.00000031   7801.99002191   0.00241862

Asics, maybe, but i'm not sure for DGB. It's multipools who are usually doing this on DGB markets.

This is not multipools coz as U see there is amount of one block ( 7801.99002191 ) in every 5-10 sec. , on cryptsy is option " auto selling" that's why we see this ( and now is time for ASIC ... ). I think this is unfair ASIC VS simple GPU, DEVS just talking about changing but soo far nothing really happend, and ASIC miners makeing milions per day when I making 20 000 per day with GPU ... .

We have to wait, dev's are working hard on their project. You have (like for us) to wait. Digibyte has said few days ago that some interesting news will be revealed soon. And, moreover, DGB is a coin with long term view... so, be patient enough.

This is interesting, after looking at the Hash Rate history this does appear to be a an auto selling bot. But the block times to not match up directly with blocks as they were discovered. We will look more into this.

As to the algorithm change we are looking very hard at several options. We still have time as the KNC miners are not expected until the June/ July time frame.

The truth is by switching algos we are simply delaying the inevitable. Which could be a wise choice to take right now.

We are still looking at the X11 algo. What are peoples feedback on it? Are your GPU's running cooler, or has someone released updated mining software yet?

[Bitock]

Where I get a normal working wallet for ubuntu? From github nothing works.

[piratfx]

What about "HEFTY1", is it possible to implementation?

[DigiByte]

Where I get a normal working wallet for ubuntu? From github nothing works.

Have you followed the guide here: https://github.com/digibyte/DigiByteProject/blob/master/doc/build-unix.md

If so which step are you getting stuck on?

Code:

./autogen.sh
./configure
make

Should be all you need to run if the dependencies are in the right place.

[DigiByte]

What about "HEFTY1", is it possible to implementation?

Do you have any documentation on it?

[the_game1224]

This is interesting, after looking at the Hash Rate history this does appear to be a an auto selling bot. But the block times to not match up directly with blocks as they were discovered. We will look more into this.

As to the algorithm change we are looking very hard at several options. We still have time as the KNC miners are not expected until the June/ July time frame.

The truth is by switching algos we are simply delaying the inevitable. Which could be a wise choice to take right now.

We are still looking at the X11 algo. What are peoples feedback on it? Are your GPU's running cooler, or has someone released updated mining software yet?

I go back and forth on this after doing quite a bit of reading on the subject.  Yes it would be delaying the inevitable as ASICs WILL be created for those algorithms if profitable, but that delay may be necessary.
IMO there are two options:
1) Switch to avoid getting destroyed by the big ASICs supposedly being released later this year.  Current net hashrate is ~640MH/s and some of the ASICs slated for release are half of that for just ONE of them and you know there will be warehouses full of them.
2) Stay with Scrypt and move to merged mining with Dogecoin.  Is this still an option?

[Bitock]

Where I get a normal working wallet for ubuntu? From github nothing works.

Have you followed the guide here: https://github.com/digibyte/DigiByteProject/blob/master/doc/build-unix.md

If so which step are you getting stuck on?

Code:

./autogen.sh
./configure
make

Should be all you need to run if the dependencies are in the right place.

I installed the all dependencies for ubuntu 13.10. Then extract DigiByteProject-master.zip -> cd DigiByteProject-master/

After ./autogen.sh:

Code:

configure.ac:12: installing 'src/build-aux/config.guess'
configure.ac:12: installing 'src/build-aux/config.sub'
configure.ac:37: installing 'src/build-aux/install-sh'
configure.ac:37: installing 'src/build-aux/missing'
configure.ac:698: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
configure.ac:698: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
src/Makefile.am: installing 'src/build-aux/depcomp'
configure.ac:698: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
configure.ac:698: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
parallel-tests: installing 'src/build-aux/test-driver'
configure.ac:698: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')

and ./configure: i get folow error configure: error: Found Berkeley DB other than 4.8, required for portable wallets (--with-incompatible-bdb to ignore)

Code:

checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... yes
checking whether make supports nested variables... (cached) yes
checking for g++... g++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of g++... gcc3
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking how to run the C++ preprocessor... g++ -E
checking for gcc... gcc
checking whether we are using the GNU Objective C compiler... no
checking whether gcc accepts -g... no
checking dependency style of gcc... gcc3
checking for g++... g++
checking whether we are using the GNU Objective C++ compiler... no
checking whether g++ accepts -g... no
checking dependency style of g++... gcc3
checking for a sed that does not truncate output... /bin/sed
checking for ar... /usr/bin/ar
checking for ranlib... /usr/bin/ranlib
checking for strip... /usr/bin/strip
checking for gcov... /usr/bin/gcov
checking for lcov... no
checking for java... /usr/bin/java
checking for genhtml... no
checking for git... /usr/bin/git
checking for ccache... no
checking for xgettext... /usr/bin/xgettext
checking for hexdump... /usr/bin/hexdump
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.26... yes
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking whether byte ordering is bigendian... no
checking if compiler needs -Werror to reject unknown flags... no
checking for the pthreads library -lpthreads... no
checking whether pthreads work without any flags... no
checking whether pthreads work with -Kthread... no
checking whether pthreads work with -kthread... no
checking for the pthreads library -llthread... no
checking whether pthreads work with -pthread... yes
checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE
checking if more special flags are required for pthreads... no
checking for PTHREAD_PRIO_INHERIT... yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking whether the linker accepts -Wl,--large-address-aware... no
checking whether C++ compiler accepts -Wstack-protector... yes
checking whether C++ compiler accepts -fstack-protector-all... yes
checking whether C++ compiler accepts -fPIE... yes
checking whether C++ preprocessor accepts -D_FORTIFY_SOURCE=2... yes
checking whether C++ preprocessor accepts -U_FORTIFY_SOURCE... yes
checking whether the linker accepts -Wl,--dynamicbase... no
checking whether the linker accepts -Wl,--nxcompat... no
checking whether the linker accepts -Wl,-z,relro... yes
checking whether the linker accepts -Wl,-z,now... yes
checking whether the linker accepts -pie... yes
checking stdio.h usability... yes
checking stdio.h presence... yes
checking for stdio.h... yes
checking for stdlib.h... (cached) yes
checking for unistd.h... (cached) yes
checking for strings.h... (cached) yes
checking for sys/types.h... (cached) yes
checking for sys/stat.h... (cached) yes
checking for MSG_NOSIGNAL... yes
checking for Berkeley DB C++ headers... default
configure: error: Found Berkeley DB other than 4.8, required for portable wallets (--with-incompatible-bdb to ignore)
atlas@mech:~/Downloads/DigiByteProject-master$ ./configure 
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... yes
checking whether make supports nested variables... (cached) yes
checking for g++... g++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of g++... gcc3
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking how to run the C++ preprocessor... g++ -E
checking for gcc... gcc
checking whether we are using the GNU Objective C compiler... no
checking whether gcc accepts -g... no
checking dependency style of gcc... gcc3
checking for g++... g++
checking whether we are using the GNU Objective C++ compiler... no
checking whether g++ accepts -g... no
checking dependency style of g++... gcc3
checking for a sed that does not truncate output... /bin/sed
checking for ar... /usr/bin/ar
checking for ranlib... /usr/bin/ranlib
checking for strip... /usr/bin/strip
checking for gcov... /usr/bin/gcov
checking for lcov... no
checking for java... /usr/bin/java
checking for genhtml... no
checking for git... /usr/bin/git
checking for ccache... no
checking for xgettext... /usr/bin/xgettext
checking for hexdump... /usr/bin/hexdump
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.26... yes
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking whether byte ordering is bigendian... no
checking if compiler needs -Werror to reject unknown flags... no
checking for the pthreads library -lpthreads... no
checking whether pthreads work without any flags... no
checking whether pthreads work with -Kthread... no
checking whether pthreads work with -kthread... no
checking for the pthreads library -llthread... no
checking whether pthreads work with -pthread... yes
checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE
checking if more special flags are required for pthreads... no
checking for PTHREAD_PRIO_INHERIT... yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking whether the linker accepts -Wl,--large-address-aware... no
checking whether C++ compiler accepts -Wstack-protector... yes
checking whether C++ compiler accepts -fstack-protector-all... yes
checking whether C++ compiler accepts -fPIE... yes
checking whether C++ preprocessor accepts -D_FORTIFY_SOURCE=2... yes
checking whether C++ preprocessor accepts -U_FORTIFY_SOURCE... yes
checking whether the linker accepts -Wl,--dynamicbase... no
checking whether the linker accepts -Wl,--nxcompat... no
checking whether the linker accepts -Wl,-z,relro... yes
checking whether the linker accepts -Wl,-z,now... yes
checking whether the linker accepts -pie... yes
checking stdio.h usability... yes
checking stdio.h presence... yes
checking for stdio.h... yes
checking for stdlib.h... (cached) yes
checking for unistd.h... (cached) yes
checking for strings.h... (cached) yes
checking for sys/types.h... (cached) yes
checking for sys/stat.h... (cached) yes
checking for MSG_NOSIGNAL... yes
checking for Berkeley DB C++ headers... default
configure: error: Found Berkeley DB other than 4.8, required for portable wallets (--with-incompatible-bdb to ignore)
atlas@mech:~/Downloads/DigiByteProject-master$ ./configure --with-incompatible-bdb
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... yes
checking whether make supports nested variables... (cached) yes
checking for g++... g++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of g++... gcc3
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking how to run the C++ preprocessor... g++ -E
checking for gcc... gcc
checking whether we are using the GNU Objective C compiler... no
checking whether gcc accepts -g... no
checking dependency style of gcc... gcc3
checking for g++... g++
checking whether we are using the GNU Objective C++ compiler... no
checking whether g++ accepts -g... no
checking dependency style of g++... gcc3
checking for a sed that does not truncate output... /bin/sed
checking for ar... /usr/bin/ar
checking for ranlib... /usr/bin/ranlib
checking for strip... /usr/bin/strip
checking for gcov... /usr/bin/gcov
checking for lcov... no
checking for java... /usr/bin/java
checking for genhtml... no
checking for git... /usr/bin/git
checking for ccache... no
checking for xgettext... /usr/bin/xgettext
checking for hexdump... /usr/bin/hexdump
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.26... yes
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking whether byte ordering is bigendian... no
checking if compiler needs -Werror to reject unknown flags... no
checking for the pthreads library -lpthreads... no
checking whether pthreads work without any flags... no
checking whether pthreads work with -Kthread... no
checking whether pthreads work with -kthread... no
checking for the pthreads library -llthread... no
checking whether pthreads work with -pthread... yes
checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE
checking if more special flags are required for pthreads... no
checking for PTHREAD_PRIO_INHERIT... yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking whether the linker accepts -Wl,--large-address-aware... no
checking whether C++ compiler accepts -Wstack-protector... yes
checking whether C++ compiler accepts -fstack-protector-all... yes
checking whether C++ compiler accepts -fPIE... yes
checking whether C++ preprocessor accepts -D_FORTIFY_SOURCE=2... yes
checking whether C++ preprocessor accepts -U_FORTIFY_SOURCE... yes
checking whether the linker accepts -Wl,--dynamicbase... no
checking whether the linker accepts -Wl,--nxcompat... no
checking whether the linker accepts -Wl,-z,relro... yes
checking whether the linker accepts -Wl,-z,now... yes
checking whether the linker accepts -pie... yes
checking stdio.h usability... yes
checking stdio.h presence... yes
checking for stdio.h... yes
checking for stdlib.h... (cached) yes
checking for unistd.h... (cached) yes
checking for strings.h... (cached) yes
checking for sys/types.h... (cached) yes
checking for sys/stat.h... (cached) yes
checking for MSG_NOSIGNAL... yes
checking for Berkeley DB C++ headers... default
configure: WARNING: Found Berkeley DB other than 4.8; wallets opened by this build will not be portable!
checking for main in -ldb_cxx-4.8... no
checking for main in -ldb_cxx... yes
checking miniupnpc/miniwget.h usability... yes
checking miniupnpc/miniwget.h presence... yes
checking for miniupnpc/miniwget.h... yes
checking for main in -lminiupnpc... yes
checking miniupnpc/miniupnpc.h usability... yes
checking miniupnpc/miniupnpc.h presence... yes
checking for miniupnpc/miniupnpc.h... yes
checking for main in -lminiupnpc... (cached) yes
checking miniupnpc/upnpcommands.h usability... yes
checking miniupnpc/upnpcommands.h presence... yes
checking for miniupnpc/upnpcommands.h... yes
checking for main in -lminiupnpc... (cached) yes
checking miniupnpc/upnperrors.h usability... yes
checking miniupnpc/upnperrors.h presence... yes
checking for miniupnpc/upnperrors.h... yes
checking for main in -lminiupnpc... (cached) yes
checking for boostlib >= 1.20.0... yes
checking whether the Boost::System library is available... yes
checking for exit in -lboost_system... yes
checking whether the Boost::Filesystem library is available... yes
checking for exit in -lboost_filesystem... yes
checking whether the Boost::Program_Options library is available... yes
checking for exit in -lboost_program_options... yes
checking whether the Boost::Thread library is available... yes
checking for exit in -lboost_thread... yes
checking whether the Boost::Chrono library is available... yes
checking for exit in -lboost_chrono... yes
checking whether the Boost::Unit_Test_Framework library is available... yes
configure: error: Could not link against boost_chrono !
atlas@mech:~/Downloads/DigiByteProject-master$ cd
atlas@mech:~$ 
atlas@mech:~$ 
atlas@mech:~$ cd Downloads/DigiByteProject-master/
atlas@mech:~/Downloads/DigiByteProject-master$ ./autogen.sh 
configure.ac:12: installing 'src/build-aux/config.guess'
configure.ac:12: installing 'src/build-aux/config.sub'
configure.ac:37: installing 'src/build-aux/install-sh'
configure.ac:37: installing 'src/build-aux/missing'
configure.ac:698: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
configure.ac:698: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
src/Makefile.am: installing 'src/build-aux/depcomp'
configure.ac:698: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
configure.ac:698: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
parallel-tests: installing 'src/build-aux/test-driver'
configure.ac:698: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
atlas@mech:~/Downloads/DigiByteProject-master$ ./configure 
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... yes
checking whether make supports nested variables... (cached) yes
checking for g++... g++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of g++... gcc3
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking how to run the C++ preprocessor... g++ -E
checking for gcc... gcc
checking whether we are using the GNU Objective C compiler... no
checking whether gcc accepts -g... no
checking dependency style of gcc... gcc3
checking for g++... g++
checking whether we are using the GNU Objective C++ compiler... no
checking whether g++ accepts -g... no
checking dependency style of g++... gcc3
checking for a sed that does not truncate output... /bin/sed
checking for ar... /usr/bin/ar
checking for ranlib... /usr/bin/ranlib
checking for strip... /usr/bin/strip
checking for gcov... /usr/bin/gcov
checking for lcov... no
checking for java... /usr/bin/java
checking for genhtml... no
checking for git... /usr/bin/git
checking for ccache... no
checking for xgettext... /usr/bin/xgettext
checking for hexdump... /usr/bin/hexdump
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.26... yes
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking whether byte ordering is bigendian... no
checking if compiler needs -Werror to reject unknown flags... no
checking for the pthreads library -lpthreads... no
checking whether pthreads work without any flags... no
checking whether pthreads work with -Kthread... no
checking whether pthreads work with -kthread... no
checking for the pthreads library -llthread... no
checking whether pthreads work with -pthread... yes
checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE
checking if more special flags are required for pthreads... no
checking for PTHREAD_PRIO_INHERIT... yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking whether the linker accepts -Wl,--large-address-aware... no
checking whether C++ compiler accepts -Wstack-protector... yes
checking whether C++ compiler accepts -fstack-protector-all... yes
checking whether C++ compiler accepts -fPIE... yes
checking whether C++ preprocessor accepts -D_FORTIFY_SOURCE=2... yes
checking whether C++ preprocessor accepts -U_FORTIFY_SOURCE... yes
checking whether the linker accepts -Wl,--dynamicbase... no
checking whether the linker accepts -Wl,--nxcompat... no
checking whether the linker accepts -Wl,-z,relro... yes
checking whether the linker accepts -Wl,-z,now... yes
checking whether the linker accepts -pie... yes
checking stdio.h usability... yes
checking stdio.h presence... yes
checking for stdio.h... yes
checking for stdlib.h... (cached) yes
checking for unistd.h... (cached) yes
checking for strings.h... (cached) yes
checking for sys/types.h... (cached) yes
checking for sys/stat.h... (cached) yes
checking for MSG_NOSIGNAL... yes
checking for Berkeley DB C++ headers... default
configure: error: Found Berkeley DB other than 4.8, required for portable wallets (--with-incompatible-bdb to ignore)

I try ./configure --with-incompatible-bdb, but I get next error configure: error: Could not link against boost_chrono !:

Code:

checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... yes
checking whether make supports nested variables... (cached) yes
checking for g++... g++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of g++... gcc3
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking how to run the C++ preprocessor... g++ -E
checking for gcc... gcc
checking whether we are using the GNU Objective C compiler... no
checking whether gcc accepts -g... no
checking dependency style of gcc... gcc3
checking for g++... g++
checking whether we are using the GNU Objective C++ compiler... no
checking whether g++ accepts -g... no
checking dependency style of g++... gcc3
checking for a sed that does not truncate output... /bin/sed
checking for ar... /usr/bin/ar
checking for ranlib... /usr/bin/ranlib
checking for strip... /usr/bin/strip
checking for gcov... /usr/bin/gcov
checking for lcov... no
checking for java... /usr/bin/java
checking for genhtml... no
checking for git... /usr/bin/git
checking for ccache... no
checking for xgettext... /usr/bin/xgettext
checking for hexdump... /usr/bin/hexdump
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.26... yes
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking whether byte ordering is bigendian... no
checking if compiler needs -Werror to reject unknown flags... no
checking for the pthreads library -lpthreads... no
checking whether pthreads work without any flags... no
checking whether pthreads work with -Kthread... no
checking whether pthreads work with -kthread... no
checking for the pthreads library -llthread... no
checking whether pthreads work with -pthread... yes
checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE
checking if more special flags are required for pthreads... no
checking for PTHREAD_PRIO_INHERIT... yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking whether the linker accepts -Wl,--large-address-aware... no
checking whether C++ compiler accepts -Wstack-protector... yes
checking whether C++ compiler accepts -fstack-protector-all... yes
checking whether C++ compiler accepts -fPIE... yes
checking whether C++ preprocessor accepts -D_FORTIFY_SOURCE=2... yes
checking whether C++ preprocessor accepts -U_FORTIFY_SOURCE... yes
checking whether the linker accepts -Wl,--dynamicbase... no
checking whether the linker accepts -Wl,--nxcompat... no
checking whether the linker accepts -Wl,-z,relro... yes
checking whether the linker accepts -Wl,-z,now... yes
checking whether the linker accepts -pie... yes
checking stdio.h usability... yes
checking stdio.h presence... yes
checking for stdio.h... yes
checking for stdlib.h... (cached) yes
checking for unistd.h... (cached) yes
checking for strings.h... (cached) yes
checking for sys/types.h... (cached) yes
checking for sys/stat.h... (cached) yes
checking for MSG_NOSIGNAL... yes
checking for Berkeley DB C++ headers... default
configure: WARNING: Found Berkeley DB other than 4.8; wallets opened by this build will not be portable!
checking for main in -ldb_cxx-4.8... no
checking for main in -ldb_cxx... yes
checking miniupnpc/miniwget.h usability... yes
checking miniupnpc/miniwget.h presence... yes
checking for miniupnpc/miniwget.h... yes
checking for main in -lminiupnpc... yes
checking miniupnpc/miniupnpc.h usability... yes
checking miniupnpc/miniupnpc.h presence... yes
checking for miniupnpc/miniupnpc.h... yes
checking for main in -lminiupnpc... (cached) yes
checking miniupnpc/upnpcommands.h usability... yes
checking miniupnpc/upnpcommands.h presence... yes
checking for miniupnpc/upnpcommands.h... yes
checking for main in -lminiupnpc... (cached) yes
checking miniupnpc/upnperrors.h usability... yes
checking miniupnpc/upnperrors.h presence... yes
checking for miniupnpc/upnperrors.h... yes
checking for main in -lminiupnpc... (cached) yes
checking for boostlib >= 1.20.0... yes
checking whether the Boost::System library is available... yes
checking for exit in -lboost_system... yes
checking whether the Boost::Filesystem library is available... yes
checking for exit in -lboost_filesystem... yes
checking whether the Boost::Program_Options library is available... yes
checking for exit in -lboost_program_options... yes
checking whether the Boost::Thread library is available... yes
checking for exit in -lboost_thread... yes
checking whether the Boost::Chrono library is available... yes
checking for exit in -lboost_chrono... yes
checking whether the Boost::Unit_Test_Framework library is available... yes
configure: error: Could not link against boost_chrono !

What's the problem?

[piratfx]

What about "HEFTY1", is it possible to implementation?

Do you have any documentation on it?

Nop , but we can ask devs about it, I think for now this is best algo, silent, less power, low temp. I just want to see new amazing changes, and feel "safe" ( anti asic ), coz I still buying and mining this coin , don't want to lose it !
Cheers

[DigiByte]

@Bitock, here is a post from a user (sovereignindividual) on Reddit.

this procedure worked for me:
if you don’t download and install Berkeley db 4.8 you will get an error during configure like this:
configure: error: Found Berkeley DB other than 4.8, required for portable wallets
so, install it as follows:
wget http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz

tar -xzvf db-4.8.30.NC.tar.gz

cd db-4.8.30.NC/build_unix

../dist/configure --enable-cxx

make

sudo make install
then you need to make a couple of symlinks so that the make process and resulting wallet can find this version of the DB:
sudo ln -s /usr/local/BerkeleyDB.4.8/lib/libdb-4.8.so /usr/lib/libdb-4.8.so

sudo ln -s /usr/local/BerkeleyDB.4.8/lib/libdb_cxx-4.8.so /usr/lib/libdb_cxx-4.8.so
Next get the system ready to build the wallet (i hope, but cannot promise, that this list is complete, as I have been compiling other wallets as well. If not you will soon find out what's missing...):
sudo apt-get install qt4-qmake libqt4-dev build-essential \
    libboost-dev libboost-system-dev libboost-filesystem-dev \
    libboost-program-options-dev libboost-thread-dev \
    libssl-dev build-essential libtool autotools-dev autoconf \
    protobuf-compiler libboost-all-dev
download and extract the v2.9.1 tar.gz package from here.
cd to the extracted directory, then
cd src/qt

protoc --cpp_out=./ paymentrequest.proto

cd ../../
the regeneration step above is important or else the compile will fail horribly.
once back in the main directory:
./autogen.sh

./configure CPPFLAGS="-I/usr/local/BerkeleyDB.4.8/include -O2" LDFLAGS="-L/usr/local/BerkeleyDB.4.8/lib"

make
after a LONG build process, the wallet binary is "digibyte-qt" to be found in src/qt
to make it like it "used to be" I copy it out to the root of the extracted folder
cp src/qt/digibyte-qt .
As I've said in another comment, the digibyte-qt binary builds as a elf shared library (approx 100mb, even when stripped) instead of an elf executable, which can be seen using the file command. Whether it builds this way because of something incorrectly set up on my system, I am unable to say, but I don't see how.
Whatever the case, the digibyte code is significantly different to 2.0 which I built on my old ubuntu (raring), which I cannot seem to do again.
If I have been doing this wrong, I'll be glad to be set on the right path.
Regards.

[DigiByte]

What about "HEFTY1", is it possible to implementation?

Do you have any documentation on it?

Nop , but we can ask devs about it, I think for now this is best algo, silent, less power, low temp. I just want to see new amazing changes, and feel "safe" ( anti asic ), coz I still buying and mining this coin , don't want to lose it !
Cheers

Which coin implemented it?

[DigiByte]

@Bitock

Reddit Post building on Ubuntu 14.04:
http://www.reddit.com/r/Digibyte/comments/238w0e/hey_the_ubuntu_wallet_download_is_broken/

[,./,./]

update 2.1.1

promo video digibyte

what's new in version 2.1.1?
-all the animations are new (some videos are the same)
-not one moment that the digibyte logo turned!
-digibyte media teaser is added to the end of the video
-black ground is a little bit more gray. (some times blue)

do you like the video
give a donation:
DGB:D5SU47NvEHjuRsgrKyPWiCnV8M27vSUFr9

if you don't like some parts I change it. feedback is always welcome