Author

Topic: ★★DigiByte|极特币★★[DGB]✔ Core v6.16.5.1 - DigiShield, DigiSpeed, Segwit - page 1395. (Read 3058812 times)

legendary
Activity: 1722
Merit: 1051
Official DigiByte Account
A new DigiByte article will be up on CryptoArticles.com tomorrow, stay tuned Smiley
Awesome! Thank you! Smiley
legendary
Activity: 1596
Merit: 1010
A new DigiByte article will be up on CryptoArticles.com tomorrow, stay tuned Smiley
legendary
Activity: 1722
Merit: 1051
Official DigiByte Account
,./,./, I haven't sent any feedback because for me, even if the video is looking greater and greater each day you improve it, something is missing : a digiman animation at beginning and at the end. I said since the beginning that digiman can be a way to attract people. But for this, we need to make him alive.

I have PM digibyte few weeks ago, and I have asked him two times to take a look into his bitcointalk inbox... without any answer. Maybe he will see it now Wink

In my PM, I have asked him if Digiman was modeled by someone with a 3DS Studio Max like app or if this was a plastic made Digiman. Why this question? Because I found an active french (I'm french) community of Blender (3DS Studio Max like app, open source) which will maybe be interested in taking part of this project. But to gain some time and to facilitate their work, this would be awesome to have this file with Digiman model, because by this way they will only work for animation, and not for the model (which will be 50% of work less).

Here's 2 lil video which shows you the strenght of this open source app :

http://www.youtube.com/watch?v=eRsGyueVLvQ

http://www.youtube.com/watch?v=Z4C82eyhwgU

I don't promise that someone can accept to be part of this project, but i can try to find some people (in english speaking forum or french speaking forum). I'm confident because 2x small animation of 10 sec each doesn't need a lot of work and a lot of computer power. I just need, Digibyte, your feeling about what I'm speaking about Wink
We apologize for the delay in response! We messaged the original artist and have not heard back on to how the DigiMan was created. We also do not have any of the original development/raw files for him. All we have is the existing jpeg/ png files.
legendary
Activity: 1722
Merit: 1051
Official DigiByte Account
What should DigiByte do about the coming Scrypt ASIC problem? Vote & here and tell us the pros and cons of your choice:

https://bitcointalksearch.org/topic/m.6358181
full member
Activity: 159
Merit: 100
,./,./, I haven't sent any feedback because for me, even if the video is looking greater and greater each day you improve it, something is missing : a digiman animation at beginning and at the end. I said since the beginning that digiman can be a way to attract people. But for this, we need to make him alive.

I have PM digibyte few weeks ago, and I have asked him two times to take a look into his bitcointalk inbox... without any answer. Maybe he will see it now Wink

In my PM, I have asked him if Digiman was modeled by someone with a 3DS Studio Max like app or if this was a plastic made Digiman. Why this question? Because I found an active french (I'm french) community of Blender (3DS Studio Max like app, open source) which will maybe be interested in taking part of this project. But to gain some time and to facilitate their work, this would be awesome to have this file with Digiman model, because by this way they will only work for animation, and not for the model (which will be 50% of work less).

Here's 2 lil video which shows you the strenght of this open source app :

http://www.youtube.com/watch?v=eRsGyueVLvQ

http://www.youtube.com/watch?v=Z4C82eyhwgU

I don't promise that someone can accept to be part of this project, but i can try to find some people (in english speaking forum or french speaking forum). I'm confident because 2x small animation of 10 sec each doesn't need a lot of work and a lot of computer power. I just need, Digibyte, your feeling about what I'm speaking about Wink
sr. member
Activity: 392
Merit: 250
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

Very awesome improvements good sir! What are other peoples feedback? This is very close to where we need to be with the video!

this is the only feedback at the moment:


I like this.  10k digibytes for support u.




SO, devs, we must create a muti-pool for dgb. Wink

hi, thats a great things for digibyte, also for altcoins.
We need a awesome coin and perfect video, i can see u and digibyte comm going up every day.

Just work hard, and keep going, do the best we can, we will get the moon.

Change the people style, change the world. Smiley

Also, i send 80k for support u again.

Status: 0/unconfirmed, broadcast through 3 nodes
Date: 4/23/14 22:49
To: D5SU47NvEHjuRsgrKyPWiCnV8M27vSUFr9
Debit: -80000.00 DGB
Net amount: -80000.00 DGB
Transaction ID: 08e01183d10e62b07c24118371af18282e3f7e6d032360d1fdb4b0d26a69b358


Good man, Keep going!


thank you very much for the 90K digibyes!
legendary
Activity: 1722
Merit: 1051
Official DigiByte Account

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?

If you havent already, read this for some thoughts regarding X11:
http://www.reddit.com/r/dogecoin/comments/23fk2i/very_long_very_serious_development_summary_week/
Thank you for posting, this is very insightful! We agree with most of the views expressed there.
sr. member
Activity: 252
Merit: 250

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?

If you havent already, read this for some thoughts regarding X11:
http://www.reddit.com/r/dogecoin/comments/23fk2i/very_long_very_serious_development_summary_week/
full member
Activity: 300
Merit: 103
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

Very awesome improvements good sir! What are other peoples feedback? This is very close to where we need to be with the video!

this is the only feedback at the moment:


I like this.  10k digibytes for support u.




SO, devs, we must create a muti-pool for dgb. Wink

hi, thats a great things for digibyte, also for altcoins.
We need a awesome coin and perfect video, i can see u and digibyte comm going up every day.

Just work hard, and keep going, do the best we can, we will get the moon.

Change the people style, change the world. Smiley

Also, i send 80k for support u again.

Status: 0/unconfirmed, broadcast through 3 nodes
Date: 4/23/14 22:49
To: D5SU47NvEHjuRsgrKyPWiCnV8M27vSUFr9
Debit: -80000.00 DGB
Net amount: -80000.00 DGB
Transaction ID: 08e01183d10e62b07c24118371af18282e3f7e6d032360d1fdb4b0d26a69b358


Good man, Keep going!
newbie
Activity: 17
Merit: 0
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?

It is Heavycoin (HVC) ( ALG "HEFTY1" )
sr. member
Activity: 392
Merit: 250
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

Very awesome improvements good sir! What are other peoples feedback? This is very close to where we need to be with the video!

this is the only feedback at the moment:


I like this.  10k digibytes for support u.




SO, devs, we must create a muti-pool for dgb. Wink
legendary
Activity: 1722
Merit: 1051
Official DigiByte Account
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

Very awesome improvements good sir! What are other peoples feedback? This is very close to where we need to be with the video!
sr. member
Activity: 392
Merit: 250
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
legendary
Activity: 1722
Merit: 1051
Official DigiByte Account
legendary
Activity: 1722
Merit: 1051
Official DigiByte Account
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?
legendary
Activity: 1722
Merit: 1051
Official DigiByte Account
@Bitock, here is a post from a user (sovereignindividual) on Reddit.

Quote
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.
newbie
Activity: 17
Merit: 0
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
full member
Activity: 213
Merit: 100
Where I get a normal working wallet for ubuntu?HuhHuhHuhHuhHuhHuhHuhHuhHuhHuh 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?Huh


sr. member
Activity: 252
Merit: 250

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?
legendary
Activity: 1722
Merit: 1051
Official DigiByte Account
What about "HEFTY1", is it possible to implementation?
Do you have any documentation on it?
Jump to: