[ANN][CRT] Certurium || a digital asset engineered for the ages

[lovelysingh]

Certurium

https://images.squarespace-cdn.com/content/v1/5d0c7665ecbb3000011dee2b/1582391198788-CIP7RIHW2BPZS9ZEEKAI/ke17ZwdGBToddI8pDm48kFhLK62tsOypOcYpkjdlszJZw-zPPgdn4jUwVcJE1ZvWEtT5uBSRWt4vQZAgTJucoTqqXjS3CfNDSuuf31e0tVEyKIuthxjPu_2w8YL9F4zpDzD-t2zpP1ojhDIsn2ak75u3E9Ef3XsXP1C_826c-iU/certurium+logo+transparent.png?format=500w

Dear Argentum NT Community,
Argentum NT has been rebranded to Certurium. You will have to install the newest version of the full node, because a soft fork has taken place which incorporates various improvements and recalibrations to the protocol at https://github.com/Certurium/certurium/releases/tag/v0.18.0.5
You will be able to find the website at Certuriumcoin.com.
Trading continues as usual

Thanks for timely update and information as you had Rebraded Argentum NT to Certurium and we have install latest version of the full node.

[braconier]

Trading continues as usual

and when will the wallets update on exchanges?
p2pb2b
stex

??

[vitimers]

Trading continues as usual

and when will the wallets update on exchanges?
p2pb2b
stex

??

Hi,

Sorry for the long wait. CRT has finally been listed on both Stex and p2pb2b! Coins have already been airdropped on Stex and are soon to be airdropped on p2pb2b

[chosenone123]

Is there an Electrum wallet avaiable for CRT?

I have finally (I guess) set up the node myself but I get an address starting with P, whereas other addresses according to the block explorer start with A or a 3. Is the P adress legit?

[vitimers]

Is there an Electrum wallet avaiable for CRT?

I have finally (I guess) set up the node myself but I get an address starting with P, whereas other addresses according to the block explorer start with A or a 3. Is the P adress legit?

There is currently no electrum wallet for CRT. Also, addresses generated in the new CRT node will always be generated with a "3" prefix. The "A" addresses are addresses from before the hardfork. An address starting with a "P" can thus not be correct.

all the best

[chosenone123]

well, shit Can you help me where I fucked up? I'm not very techy. What I did is the following:

On Kubuntu:

Code:

sudo apt-get update;
sudo apt-get install git;
mkdir -p certurium-source && cd certurium-source
git clone https://github.com/certurium/certurium.git;
sudo apt-get install build-essential libtool autotools-dev automake pkg-config libssl-dev libevent-dev bsdmainutils python3;
sudo apt-get install libboost-all-dev;
wget http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz;
echo '12edc0df75bf9abd7f82f821795bcee50f42cb2e5f76a6a281b85732798364ef  db-4.8.30.NC.tar.gz' | sha256sum -c;
tar -xvf db-4.8.30.NC.tar.gz;
cd db-4.8.30.NC/build_unix;
mkdir -p build;
BDB_PREFIX=$(pwd)/build;
../dist/configure --disable-shared --enable-cxx --with-pic --prefix=$BDB_PREFIX;
sudo make install;
cd ../..;
sudo apt-get install libminiupnpc-dev;
sudo apt-get install libzmq3-dev;
sudo apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler;
sudo apt-get install libqrencode-dev;
cd certurium;
git checkout tags/v0.19.1.1;
./autogen.sh;
./configure CPPFLAGS="-I${BDB_PREFIX}/include/ -O2" LDFLAGS="-L${BDB_PREFIX}/lib/" --with-gui --disable-shared;
make;
sudo make install;
bitcoin-qt

Afterwards it starts syncing and finishes pretty fast (around 150MB), when I create a new receive address it generates addresses starting with PC1......  

The bitcoin-qt information window shows Client version v0.19.1.1, User Agend /Certurium:0.19.1/, Berkeley DB 4.8.30. Also the current block number matches with the one on chainz.cryptoID.info/crt.

Soo... Why is it generating wrong addresses

Thanks

EDIT: just tried it with

Code:

git checkout tags/v0.18.0.5

as I saw your previous post from February. Now it generates an address starting with 3 but how can I be sure that it actually is able to receive CRT? Client version now shows v0.18.05, user agent Certurium:0.18.0

Also, it's correct that it says BTC and not CRT, right?

EDIT2: ah, shit, with v0.18.0.5 it stalls at block 392235 (May 28) which didn't happen with v0.19.1.1...

from debug.log (last few entries):
2020-08-24T18:56:54Z UpdateTip: new best=74945ae028634b8c3142ca7ec7e84de46d44360d1d7eac7c60197be0a56c5b4d height=392431 version=0x20000000 log2_work=53.46046 tx=394911 date='2020-05-28T21:06:53Z' progress=0.071564 cache=67.8MiB(496053txo)
2020-08-24T18:56:54Z UpdateTip: new best=b42c4f8132f7479c74f5a52211219cc6055da8564fc180a6eb3a71e5a82ce3c1 height=392432 version=0x20000000 log2_work=53.46046 tx=394912 date='2020-05-28T21:07:02Z' progress=0.071564 cache=67.8MiB(496054txo)
2020-08-24T18:56:54Z UpdateTip: new best=e878cab8097ebf11130dfd14ce288526110340e7acfcfbde67acdae1c3fbabcf height=392433 version=0x20000000 log2_work=53.46046 tx=394913 date='2020-05-28T21:09:51Z' progress=0.071565 cache=67.8MiB(496055txo)
2020-08-24T18:56:54Z UpdateTip: new best=1d5bc8ed5a0f9f58669ca25f5a1c4431ce2d7d828d2c75b0cde7f2dbdf2b393e height=392434 version=0x20000000 log2_work=53.46046 tx=394914 date='2020-05-28T21:10:02Z' progress=0.071565 cache=67.8MiB(496056txo)
2020-08-24T18:56:54Z UpdateTip: new best=8d96c1cef0f010e17363b2ca48b888902b8114dbb54d900a8cd265f41b0637c2 height=392435 version=0x20000000 log2_work=53.46046 tx=394915 date='2020-05-28T21:10:04Z' progress=0.071565 cache=67.8MiB(496057txo)
2020-08-24T18:56:54Z UpdateTip: new best=0301b90dd6abd2347e3cf1ce048dc6bd47f63cda66d5f5be7bbb7f9d051a04a6 height=392436 version=0x20000000 log2_work=53.46046 tx=394916 date='2020-05-28T21:10:08Z' progress=0.071565 cache=67.8MiB(496058txo)
2020-08-24T18:56:54Z UpdateTip: new best=2e51fa5aaf017a05b93e4da2b878ee8904455482e88727d8bdc0dfcafac6182b height=392437 version=0x20000000 log2_work=53.46046 tx=394917 date='2020-05-28T21:10:11Z' progress=0.071565 cache=67.8MiB(496059txo)
2020-08-24T18:56:54Z ERROR: AcceptBlock: bad-cb-payout, softfork consensus: 32RkqiLFR6UbhuULowSQUjWEy4jGfANRqH address needs to receive 99.000000% of coinbase reward. Current share is: 0%. (code 16)
2020-08-24T18:56:54Z ERROR: ProcessNewBlock: AcceptBlock FAILED (bad-cb-payout, softfork consensus: 32RkqiLFR6UbhuULowSQUjWEy4jGfANRqH address needs to receive 99.000000% of coinbase reward. Current share is: 0%. (code 16))
2020-08-24T18:56:54Z New outbound peer connected: version: 70015, blocks=392437, peer=6
2020-08-24T18:59:20Z ERROR: CheckSignature: verify signature failed
2020-08-24T18:59:20Z ERROR: CheckSignature: verify signature failed
2020-08-24T18:59:20Z ERROR: CheckSignature: verify signature failed
2020-08-24T18:59:20Z ERROR: AcceptBlockHeader: prev block not found
2020-08-24T18:59:20Z ERROR: CheckSignature: verify signature failed
2020-08-24T18:59:20Z ERROR: AcceptBlockHeader: prev block not found
2020-08-24T18:59:20Z ERROR: AcceptBlockHeader: prev block not found
2020-08-24T18:59:20Z ERROR: AcceptBlockHeader: prev block not found
2020-08-24T19:00:17Z Potential stale tip detected, will try using extra outbound peer (last tip update: 203 seconds ago)
2020-08-24T19:03:43Z ERROR: CheckSignature: verify signature failed
2020-08-24T19:03:43Z ERROR: CheckSignature: verify signature failed
2020-08-24T19:03:43Z ERROR: AcceptBlockHeader: prev block not found
2020-08-24T19:03:43Z ERROR: AcceptBlockHeader: prev block not found
2020-08-24T19:03:43Z ERROR: CheckSignature: verify signature failed
2020-08-24T19:03:43Z ERROR: AcceptBlockHeader: prev block not found
2020-08-24T19:03:43Z ERROR: CheckSignature: verify signature failed
2020-08-24T19:03:43Z ERROR: AcceptBlockHeader: prev block not found
2020-08-24T19:03:55Z ERROR: AcceptBlockHeader: prev block not found
2020-08-24T19:03:55Z ERROR: CheckSignature: verify signature failed
2020-08-24T19:03:55Z ERROR: CheckSignature: verify signature failed
2020-08-24T19:03:55Z ERROR: AcceptBlockHeader: prev block not found
2020-08-24T19:03:55Z ERROR: AcceptBlockHeader: prev block not found
2020-08-24T19:03:55Z ERROR: AcceptBlockHeader: prev block not found
2020-08-24T19:04:16Z ERROR: AcceptBlockHeader: prev block not found
2020-08-24T19:04:19Z New outbound peer connected: version: 70015, blocks=161251, peer=9
2020-08-24T19:04:19Z ERROR: CheckSignature: verify signature failed
2020-08-24T19:04:19Z ERROR: AcceptBlockHeader: prev block not found
2020-08-24T19:06:28Z ERROR: CheckSignature: verify signature failed
2020-08-24T19:06:50Z ERROR: CheckSignature: verify signature failed
2020-08-24T19:07:27Z ERROR: CheckSignature: verify signature failed
2020-08-24T19:07:33Z ERROR: CheckSignature: verify signature failed
2020-08-24T19:07:37Z ERROR: CheckSignature: verify signature failed
2020-08-24T19:07:43Z ERROR: CheckSignature: verify signature failed
2020-08-24T19:07:47Z ERROR: CheckSignature: verify signature failed

Is there an Electrum wallet avaiable for CRT?

I have finally (I guess) set up the node myself but I get an address starting with P, whereas other addresses according to the block explorer start with A or a 3. Is the P adress legit?

There is currently no electrum wallet for CRT. Also, addresses generated in the new CRT node will always be generated with a "3" prefix. The "A" addresses are addresses from before the hardfork. An address starting with a "P" can thus not be correct.

all the best

[chosenone123]

No help? 

[vitimers]

No help? 

Hi,
Sorry for the belated answer, we were very busy in recent times and forgot to check bitcointalk. Do you still need help or have you figured it out by now? 

[chosenone123]

No help? 

Hi,
Sorry for the belated answer, we were very busy in recent times and forgot to check bitcointalk. Do you still need help or have you figured it out by now? 

Hi there, I still need help, I am a noob and it is the first time I use Linux and want to set up a CRT Node. Can you maybe write me a noob-proof step-by-step guide to set up the node and generate addresses myself? :-D

[vitimers]

No help? 

Hi,
Sorry for the belated answer, we were very busy in recent times and forgot to check bitcointalk. Do you still need help or have you figured it out by now? 

Hi there, I still need help, I am a noob and it is the first time I use Linux and want to set up a CRT Node. Can you maybe write me a noob-proof step-by-step guide to set up the node and generate addresses myself? :-D

Can do

1. You have to install dependencies that Certurium needs

Open your terminal and copy paste the following commands

Code:

sudo apt-get install build-essential libtool autotools-dev automake pkg-config bsdmainutils python3

and

Code:

sudo apt-get install libssl-dev libevent-dev libboost-system-dev libboost-filesystem-dev libboost-chrono-dev libboost-test-dev libboost-thread-dev

2. Next, you have to clone the certurium code into any folder you want, usually where you save your other programs, by typing

Code:

git clone https://github.com/Certurium/certurium.git

3. cd into your certurium folder

If you want wallet capabilites, refer to this part of the docs on how to install berkeley-db

https://github.com/Certurium/certurium/blob/master/doc/build-unix.md#berkeley-db

4. Last thing you have to do, is run these commands one after another.

Code:

./autogen.sh
./configure --disable-shared
make
make install

If you did everything right, you can finally run certurium by typing

Code:

certuriumd

in the terminal.

Use the certurium daemon, as some people have had issues with the certurium-qt.
By the way, the reason things didn't work for you with version v0.18 is because it's actually running on a different chain, as we have gone through a hard fork since.

Hope this helps. If you get stuck somewhere, let me know 

P.S. If you have problems with berkeley DB, as I've had in the past, you can install a different version of berkeley DB like so:

Code:

sudo apt-get install libdb-dev++

(may not work for all distros)

and then you have to specify

Code:

./configure --disable-shared --with-incompatible-bdb

[chosenone123]

hey, thanks for taking the time. unfortunately I get stuck at the "make" step.
 it says:
make: *** No targets specified and no makefile found. Stop.

Seems like the configure command doesn't do what it should do, see below. How can I fix?

satoshi@nakamoto:~/certurium$ ./configure --disable-shared --with-incompatible-bdb
checking for gcc... gcc
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 gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-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 dependency style of gcc... gcc3
checking whether to enable maintainer-specific portions of Makefiles... yes
checking whether make supports nested variables... (cached) yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking whether g++ supports C++11 features with -std=c++11... yes
checking whether std::atomic can be used without link library... yes
checking whether we are using the GNU Objective C++ compiler... no
checking whether g++ -std=c++11 accepts -g... no
checking dependency style of g++ -std=c++11... gcc3
checking how to print strings... printf
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-pc-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /bin/dd
checking how to truncate binary pipes... /bin/dd bs=4096 count=1
checking for mt... mt
checking if mt is a manifest tool... no
checking how to run the C preprocessor... gcc -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 for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... no
checking whether to build static libraries... yes
checking how to run the C++ preprocessor... g++ -std=c++11 -E
checking for ld used by g++ -std=c++11... /usr/bin/ld -m elf_x86_64
checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ -std=c++11 linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking for g++ -std=c++11 option to produce PIC... -fPIC -DPIC
checking if g++ -std=c++11 PIC flag -fPIC -DPIC works... yes
checking if g++ -std=c++11 static flag -static works... yes
checking if g++ -std=c++11 supports -c -o file.o... yes
checking if g++ -std=c++11 supports -c -o file.o... (cached) yes
checking whether the g++ -std=c++11 linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
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 python3.5... no
checking for python3.6... /usr/bin/python3.6
checking for genhtml... no
checking for git... /usr/bin/git
checking for ccache... no
checking for xgettext... no
checking for hexdump... /usr/bin/hexdump
checking for readelf... /usr/bin/readelf
checking for c++filt... /usr/bin/c++filt
checking for objcopy... /usr/bin/objcopy
checking for doxygen... no
configure: WARNING: Doxygen not found
checking whether C++ compiler accepts -Werror... yes
checking whether C++ compiler accepts -Wall... yes
checking whether C++ compiler accepts -Wextra... yes
checking whether C++ compiler accepts -Wformat... yes
checking whether C++ compiler accepts -Wvla... yes
checking whether C++ compiler accepts -Wswitch... yes
checking whether C++ compiler accepts -Wformat-security... yes
checking whether C++ compiler accepts -Wthread-safety-analysis... no
checking whether C++ compiler accepts -Wrange-loop-analysis... no
checking whether C++ compiler accepts -Wredundant-decls... yes
checking whether C++ compiler accepts -Wunused-parameter... yes
checking whether C++ compiler accepts -Wself-assign... no
checking whether C++ compiler accepts -Wunused-local-typedef... no
checking whether C++ compiler accepts -Wdeprecated-register... no
checking whether C++ compiler accepts -Wimplicit-fallthrough... yes
checking whether C++ compiler accepts -msse4.2... yes
checking whether C++ compiler accepts -msse4.1... yes
checking whether C++ compiler accepts -mavx -mavx2... yes
checking whether C++ compiler accepts -msse4 -msha... yes
checking for assembler crc32 support... yes
checking for SSE4.1 intrinsics... yes
checking for AVX2 intrinsics... yes
checking for SHA-NI intrinsics... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking whether byte ordering is bigendian... no
checking whether gcc is Clang... no
checking whether pthreads work with -pthread... yes
checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE
checking whether 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 strerror_r is declared... yes
checking for strerror_r... yes
checking whether strerror_r returns char *... yes
checking whether the linker accepts -Wl,--large-address-aware... no
checking for __attribute__((visibility))... yes
checking for __attribute__((dllexport))... no
checking for __attribute__((dllimport))... no
checking for library containing clock_gettime... none required
checking whether C++ compiler accepts -fPIC... yes
checking whether C++ compiler accepts -fstack-reuse=none... yes
checking whether C++ compiler accepts -Wstack-protector... yes
checking whether C++ compiler accepts -fstack-protector-all... 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,--high-entropy-va... no
checking whether the linker accepts -Wl,-z,relro... yes
checking whether the linker accepts -Wl,-z,now... yes
checking whether the linker accepts -fPIE -pie... yes
checking endian.h usability... yes
checking endian.h presence... yes
checking for endian.h... yes
checking sys/endian.h usability... no
checking sys/endian.h presence... no
checking for sys/endian.h... no
checking byteswap.h usability... yes
checking byteswap.h presence... yes
checking for byteswap.h... 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 sys/select.h usability... yes
checking sys/select.h presence... yes
checking for sys/select.h... yes
checking sys/prctl.h usability... yes
checking sys/prctl.h presence... yes
checking for sys/prctl.h... yes
checking FD_ZERO memcpy dependence... no
checking whether getifaddrs is declared... yes
checking whether freeifaddrs is declared... yes
checking whether strnlen is declared... yes
checking whether daemon is declared... yes
checking whether le16toh is declared... yes
checking whether le32toh is declared... yes
checking whether le64toh is declared... yes
checking whether htole16 is declared... yes
checking whether htole32 is declared... yes
checking whether htole64 is declared... yes
checking whether be16toh is declared... yes
checking whether be32toh is declared... yes
checking whether be64toh is declared... yes
checking whether htobe16 is declared... yes
checking whether htobe32 is declared... yes
checking whether htobe64 is declared... yes
checking whether bswap_16 is declared... yes
checking whether bswap_32 is declared... yes
checking whether bswap_64 is declared... yes
checking whether __builtin_clz is declared... yes
checking whether __builtin_clzl is declared... yes
checking whether __builtin_clzll is declared... yes
checking for getmemoryinfo... yes
checking for mallopt M_ARENA_MAX... yes
checking for visibility attribute... yes
checking for thread_local support... yes
checking for Linux getrandom syscall... yes
checking for getentropy... yes
checking for getentropy via random.h... yes
checking for sysctl KERN_ARND... no
checking for if type char equals int8_t... no
checking for std::system... yes
checking for ::_wsystem... no
checking whether to build Bitcoin Core GUI... no
checking for Berkeley DB C++ headers... no
configure: error: libdb_cxx headers missing, Bitcoin Core requires this library for wallet functionality (--disable-wallet to disable wallet functionality)
satoshi@nakamoto:~/certurium$ make
make: *** No targets specified and no makefile found.  Stop.

[vitimers]

hey, thanks for taking the time. unfortunately I get stuck at the "make" step.
 it says:
make: *** No targets specified and no makefile found. Stop.

Seems like the configure command doesn't do what it should do, see below. How can I fix?

satoshi@nakamoto:~/certurium$ ./configure --disable-shared --with-incompatible-bdb
checking for gcc... gcc
.
.
.

checking for Berkeley DB C++ headers... no
configure: error: libdb_cxx headers missing, Bitcoin Core requires this library for wallet functionality (--disable-wallet to disable wallet functionality)
satoshi@nakamoto:~/certurium$ make
make: *** No targets specified and no makefile found.  Stop.

Hey,
the problem lies in the last line:

configure: error: libdb_cxx headers missing, Bitcoin Core requires this library for wallet functionality

Berkeley db has not been correctly installed. You had it installed two months ago when you first reported you needed help. I don't know what you did different this time, but try to install it just the way you installed it last time.

All the best,
Vitimers

[chosenone123]

Hey Vitimers, thank you for your patience. unfortunately, I still dont get it... the berkeley DB I install with the following commands:

It is from this tutorial: https://hackernoon.com/a-complete-beginners-guide-to-installing-a-bitcoin-full-node-on-linux-2018-edition-cb8e384479ea

Code:

wget http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz;
echo '12edc0df75bf9abd7f82f821795bcee50f42cb2e5f76a6a281b85732798364ef  db-4.8.30.NC.tar.gz' | sha256sum -c;
tar -xvf db-4.8.30.NC.tar.gz;
cd db-4.8.30.NC/build_unix;
mkdir -p build;
BDB_PREFIX=$(pwd)/build;
../dist/configure --disable-shared --enable-cxx --with-pic --prefix=$BDB_PREFIX;
sudo make install;
cd ../..;

But then I get this error again:

Code:

checking for ::_wsystem... no
checking whether to build Bitcoin Core GUI... no
checking for Berkeley DB C++ headers... no
configure: error: libdb_cxx headers missing, Bitcoin Core requires this library for wallet functionality (--disable-wallet to disable wallet functionality)

Where am I dumbass failing??

[vitimers]

Hey Vitimers, thank you for your patience. unfortunately, I still dont get it... the berkeley DB I install with the following commands:

It is from this tutorial: https://hackernoon.com/a-complete-beginners-guide-to-installing-a-bitcoin-full-node-on-linux-2018-edition-cb8e384479ea

Code:

wget http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz;
echo '12edc0df75bf9abd7f82f821795bcee50f42cb2e5f76a6a281b85732798364ef  db-4.8.30.NC.tar.gz' | sha256sum -c;
tar -xvf db-4.8.30.NC.tar.gz;
cd db-4.8.30.NC/build_unix;
mkdir -p build;
BDB_PREFIX=$(pwd)/build;
../dist/configure --disable-shared --enable-cxx --with-pic --prefix=$BDB_PREFIX;
sudo make install;
cd ../..;

But then I get this error again:

Code:

checking for ::_wsystem... no
checking whether to build Bitcoin Core GUI... no
checking for Berkeley DB C++ headers... no
configure: error: libdb_cxx headers missing, Bitcoin Core requires this library for wallet functionality (--disable-wallet to disable wallet functionality)

Where am I dumbass failing??

Maybe try installing a different version of berkeley DB and set the --with-incompatible-bdb flag. I remember having the same problem as you when I first installed it, but using a different version of Berkeley DB solved it for me. Just remember that wallet compatibility with full nodes using other version of berkeley db is not given.

[chosenone123]

hey vitimers

no matter what I try, I still get the following error

Code:

configure: error: libdb_cxx headers missing

I also googled the error and some of the solutions suggested there (for Bitcoin Core) don't work for Certurium. The disable-wallet option is not really an option because I want to be able to create and manage wallets...

You have an idea where I could be screwing up? On what Linux distribution/version are you running everything and is there maybe a security setting which needs to be changed in order for it to work?

[lm12345]

We need more nodes or this coin will die.

In case anyone is having issues building it, I've just built it in Ubuntu 21.10 without any issues with:

Code:

sudo apt-get install -qy  git make g++ autoconf libtool pkg-config bsdmainutils libboost-all-dev libssl-dev libevent-dev libdb++-dev
./autogen.sh
./configure --disable-shared --with-incompatible-bdb
make -j 4

Anyway, the simplest way to build it and run it on any distribution and without having to mess around with your libraries is to use docker. You'll need to make a couple of changes to the Dockerfile though:

- As 20.10 reached its end of life, change the ubuntu version to 20.04
- Prepend DEBIAN_FRONTEND=noninteractive to apt-get to prevent it from getting stuck waiting for user input installing some packages (for example, tzdata), as docker build is not interactive

Code:

FROM ubuntu:20.04

RUN apt-get update -q && \
    DEBIAN_FRONTEND=noninteractive apt-get install -qy  git make g++ autoconf libtool pkg-config bsdmainutils libboost-all-dev libssl-dev libevent-dev libdb++-dev && \
    rm -rf /var/lib/apt/lists/* && \
    apt-get autoremove -y && \
    apt-get clean
WORKDIR /certurium
VOLUME /root/.certurium/
ADD . /certurium
RUN ./autogen.sh && ./configure --with-gui=no --with-incompatible-bdb --enable-static --disable-shared && make -j4 && cp src/certurium* /usr/local/bin/ && make distclean
CMD ["certuriumd"]

Then build it with:

Code:

docker build -t certurium .

Run it with:

Code:

docker run --name certurium certurium

From another terminal, you can connect to the container with:

Code:

docker exec -it certurium bash

and from there you can use certurium-cli. For example, to shut down the server cleanly:

Code:

root@644cced990a2:/certurium# certurium-cli stop

To start the node again:

Code:

docker start certurium