Bitcoin Forum

Introduction


Certurium is a fork of Bitcoin, and was conceived in 2013 as a rare commodity with the explicit goal of long term value apreciation. Today this purpose is being further refined for indefinite wealth storage – a digital asset engineered for the ages.

Certuriums parameters have been optimized to make it ideal for long term investments. It is important to understand that this is not an issued token but a decentrally mined cryptocurrency like Bitcoin. A purely peer-to-peer, decentralized digital store of value building upon Bitcoin, optimizing its paramaters and implementing technological components to leverage the blockchains advantages and cutting its disadvantages out.


The Perception of Bitcoin as a Transactional Currency

From its inception by Satoshi Nakamoto – whoever that might be – Bitcoin was intended to be (and was also positioned as) a transactional currency. Bitcoin was invented as a censorship free, trustless, decentralized peer to peer money. During all these years since the first Bitcoin transaction on January 3rd, 2009 the Bitcoin community fostered the image of Bitcoin as a new global currency.
However, as more and more people realize that Bitcoin might not be a great transactional currency, investors could also lose confidence in Bitcoin as an investment asset. Even though some observers have dubbed Bitcoin “Gold 2.0” one has to admit that Bitcoin is not ideally positioned as a pure investment coin.
Certurium was never positioned as a peer to peer money. From its beginnings it was designed purely as a digital asset.


Optimizations over Bitcoin

• Total number of coins is approximately 12'000'000
• Replacing the SHA256 hashing algorithm used in mining with the NeoScrypt algorithm
• Implementation of the T3 difficulty adjustment algorithm to prevent massive swings in difficulty

• Block adaptations
  
  • Initial block-reward of 0.001 new coin per block
  • On average, one block is mined per minute
  • Block halvings happen every 2'100'000 blocks, which is about every four years
  • Block maturation occurs after 100 confirmations

Difficulty adjustment algorithm

Bitcoin’s difficulty adjustment algorithm is executed only once every 2016 blocks. While this works sufficiently well for Bitcoin where the hashing power experiences only minor fluctuations relative to the total hashing power, this is a big issue for Altcoins where typically the total hashing power is low. A sudden increase in hashing power causes a high block rate leading to a much higher coin inflation than intended. A sudden drop in hashing power prolongs the time required to mine a new block by factors causing users to wait for transaction confirmations for an unexpected amount of time which lowers the user’s trust in such a system. Consequently, it’s crucial to select an algorithm that adjusts the mining difficulty with respect to the changing hashing power. The Certurium team implemented the T3 difficulty adjustment algorithm in C++ on top of Certurium Core to offer the solution to this problem.

Website

https://Certuriumcoin.com/


Community

• Telegram: https://t.me/Certurium
• Twitter: https://twitter.com/Certurium

Exchanges

• https://app.stex.com/en/trade/pair/BTC/CRT/1D
  
• https://p2pb2b.io/trade/CRT_AGNT

Chain Explorer

https://chainz.cryptoid.info/crt/


Github

• Source: https://github.com/certurium/certurium
• Recommended Miner: https://github.com/KlausT/ccminer
• Mining Pool: https://github.com/certurium/node-open-mining-portal
• Neoscrypt: https://github.com/ghostlander/NeoScrypt

Neoscrypt whitepaper

http://phoenixcoin.org/archive/neoscrypt_v1.pdf

UNIX BUILD NOTES

Some notes on how to build Argentum NT Core in Unix.

Heads-up: The build instructions are essentially the same as for bitcoin, so if you run into problems, make sure to google parallel bitcoin problems. Also, we haven't updated the usage(s) of variable name "bitcoin" in the code itself, because we had more pressing technological matters to attend to.

Note

Always use absolute paths to configure and compile Argentum NT Core and the dependencies.
For example, when specifying the path of the dependency:


Here BDB_PREFIX must be an absolute path - it is defined using $(pwd) which ensures
the usage of the absolute path.

To Build

This will build bitcoin-qt as well, if the dependencies are met.

Dependencies

These dependencies are required:

Library	Purpose	Description
libssl	Crypto	Random Number Generation, Elliptic Curve Cryptography
libboost	Utility	Library for threading, data structures, etc
libevent	Networking	OS independent asynchronous networking

Optional dependencies:

Library	Purpose	Description
miniupnpc	UPnP Support	Firewall-jumping support
libdb4.8	Berkeley DB	Wallet storage (only needed when wallet enabled)
qt	GUI	GUI toolkit (only needed when GUI enabled)
protobuf	Payments in GUI	Data interchange format used for payment protocol (only needed when GUI enabled)
libqrencode	QR codes in GUI	Optional for generating QR codes (only needed when GUI enabled)
univalue	Utility	JSON parsing and encoding (bundled version will be used unless --with-system-univalue passed to configure)
libzmq3	ZMQ notification	Optional, allows generating ZMQ notifications (requires ZMQ version >= 4.0.0)

Linux Distribution Specific Instructions

Ubuntu & Debian

Dependency Build Instructions

Build requirements:


Now, you can either build from self-compiled or install the required dependencies:


BerkeleyDB is required for the wallet.

Ubuntu and Debian have their own libdb-dev and libdb++-dev packages, but these will install
BerkeleyDB 5.1 or later. This will break binary wallet compatibility with the distributed executables, which
are based on BerkeleyDB 4.8. If you do not care about wallet compatibility,
pass to configure.


ZMQ dependencies (provides ZMQ API):


GUI dependencies:

If you want to build bitcoin-qt, make sure that the required packages for Qt development
are installed. Qt 5 is necessary to build the GUI.
To build without GUI pass .

To build with Qt 5 you need the following:


libqrencode (optional) can be installed with:


Once these are installed, they will be found by configure and a bitcoin-qt executable will be
built by default.

Notes

The release is built with GCC and then "strip bitcoind" to strip the debug
symbols, which reduces the executable size by about 90%.

miniupnpc

miniupnpc (http://miniupnp.free.fr/) may be used for UPnP port mapping. It can be downloaded from
http://miniupnp.tuxfamily.org/files/. UPnP support is compiled in and
turned off by default. See the configure options for upnp behavior desired:


Berkeley DB

It is recommended to use Berkeley DB 4.8. If you have to build it yourself,
you can use the installation script included in contrib/
like so:
from the root of the repository.

Note: You only need Berkeley DB if the wallet is enabled.

Boost

If you need to build Boost yourself:


Security

To help make your Argentum NT Core installation more secure by making certain attacks impossible to
exploit even if a vulnerability is found, binaries are hardened by default.
This can be disabled with:

Hardening Flags:


Hardening enables the following features:

Position Independent Executable: Build position independent code to take advantage of Address Space Layout Randomization
offered by some kernels. Attackers who can cause execution of code at an arbitrary memory
location are thwarted if they don't know where anything useful is located.
The stack and heap are randomly located by default, but this allows the code section to be
randomly located as well.

• Non-executable Stack: If the stack is executable then trivial stack-based buffer overflow exploits are possible if

vulnerable buffers are found. By default, Argentum NT Core should be built with a non-executable stack,
but if one of the libraries it uses asks for an executable stack or someone makes a mistake
and uses a compiler extension which requires an executable stack, it will silently build an
executable without the non-executable stack protection.

To verify that the stack is non-executable after compiling use:

The output should contain:
STK/REL/PTL
RW- R-- RW-

The STK RW- means that the stack is readable and writeable but not executable.

Additional Configure Flags

A list of additional configure flags can be displayed with:


ARM Cross-compilation

These steps can be performed on, for example, an Ubuntu VM. The depends system
will also work on other Linux distributions, however the commands for
installing the toolchain will be different.

Make sure you install the build requirements mentioned above.
Then, install the toolchain and curl:


To build executables for ARM:

Connect to node 194.182.179.84 when you have successfully built your Argentum NT Core node

Initial block-reward of 0.1 new coin per block

 ???

The very low block reward in argentum NT is a design feature, which allows the sell pressure to be radically minimized, as miners typically sell their coins to pay for the mining equipment they are running. As Argentum NT is positioned and built as a long term asset and not as a currency, it is an advantage for the mining reward to be so low. :)

hello AGNT!
I've come across your announcement today - whoa! Your philosophy and tech is looking great!
Tell me, how and where can I buy your coin, do I have to have BTC first? Which exchange? And how do I store it? Do you have wallets?
I really like the idea of digital silver - with digital shine factor :)

Hello fabz and welcome to the AGNT project :) We will be listing our coin fairly soon, when you will be able to purchase it with BTC. USD and other exchange options will come later. The exchange will be announced on this thread, on twitter and on the telegram chat, so you won't miss it!

For now, the only wallet we have is the full node that is published on github. You will need to build it yourself. We are working on lightweight wallets that will make it very easy to store and send AGNT in the future, with added functionality of locking your coins for a set amount of time. Stay tuned for that!


We're committed to making digital silver a reality! With all the pros that digitalisation brings   ;)

I came across your coin and the idea is really cool.

I have one question though, what insurance do I get on its longevity, since it is geared towards long term investments? Basically how can I expect my investment to not depreciate massively over time

This is achieved through various mechanisms. First of all, the mining reward is very low compared to bitcoin. That directly means a much weaker sell pressure that comes from miners having to sell their coins to pay for electricity. Secondly, we are working on various incentive mechanisms (like reward distribution to various long term holders) that will greatly reduce sell pressure even more. Thirdly, we are positioning ourselves as a long term asset and as such have an advantage over any crypto that positions themselves as a currency. Cryptos are much too volatile to be currencies, so any coin positioning themselves as one will ultimately hurt themselves in the long term. All of this ensures a higher trust in the asset and as such reinforces the idea of long term holding .

  is it a test mode now, or will a new network be launched when lightweight wallets is launched?


 p.s.  install Ubuntu and start the node... Yes, I then begin to feel like a hero))) maybe better to wait for the wallet....

The network that is now running is the mainnet :) The leightweight wallet will not be available soon, because we have other priorities!

i compiled and is a btc wallet that created a .bitcoinv folder in Home the question is for to add the node what is the conf file name ? ... "bitcoinv.conf" ?

ok, done.! i find the way.  ;D

great :) If you need help with anything else, just let us know!

It is quite funny seeing in the github as various coin variables and even executive names are being changed from platinum and bitcoin to argentum 2 weeks after launch. Shouldn’t it done before?

We were focusing on technical changes and wanted to get the fork out. At first, cosmetic changes - which have no effect on functionality - were supposed to be left alone so that we could quickly incorporate new BIPs ontop of our own technically differing system. We now changed some cosmetics to facilitate integration for block explorers and exchange listing :)

RPCPORT ??????

What happened to the coins on cryptsy? The receiver gave some coins back to the devs if he couldn't sell them. Did he give the cryptsy Argentum back to a dev?

Please google bitcoin.conf :)

Maybe he gave coins to one of the earlier devs, but I wouldn't know

+1

Most of that information could be copied from the old thread. A few modifications to get it up to date is all that is needed.

https://bitcointalk.org/index.php?topic=1432608.0

Thanks for the input :) I updated block reward, mining time and halving points under the tab Optimizations over Bitcoin.
Also, you can now see the blockchain explorer all the way at the bottom

It's still on these exchanges that you could add to the OP.

https://www.coinexchange.io/market/ARG/BTC

https://novaexchange.com/market/BTC_ARG/

Why ? ThaT's Argentum-NT, not bitcoin.

RPCPORT of Bitcoin is already used ..... by BITCOIN ! ....

The markets that you are referring to are not trading Argentum NT but Argentum. Agnt is a fork of Argentum :)

The listing has finally happened and you can find the market on NovaExchange at https://novaexchange.com/market/BTC_AGNT/  :D

The file name is the same, you can set it up like so:  ~/.argentumntcoin/bitcoin.conf

Sorry, I thought it was a rebranding, not a fork.

Is this a new ARG (Argentum) / SWAP or not?

Hi,

Can anyone compile a windows wallet please?

or help me compile on Ubuntu 16.04... i am a complete linux novice, and cannot get it to compile, it says something like recompile with -fPIC, and thet us/bin/ld erros
No idea

This a Argentum hard fork. The old chain is still live and tradeable

Common mistake with ubuntu compilation is that one forgets to pass --disable-shared to ./configure. Let me know if that works and else you can send me details to your problem via dm

Dev, why are you modestly silent about the size of the premine? Say no shy. Well, how much is 2-5 million or more? ;D
Maybe then we will believe in the value of your coin. And we will understand why the reward to miners is only 0.1AGNT

22'222'222 coins were generated in the AGNT genesis block
https://chainz.cryptoid.info/agnt/block.dws?0.htm (https://chainz.cryptoid.info/agnt/block.dws?0.htm)
Every ARG was then credited in a 1:1 ratio on the new blockchain. The rest is to be given to a foundation to ensure the long term development and support of the coin.
If you've got any other question, just let me know  :)

So you basically premined more than 10 000 000 coin, which is close to 50% of total supply on a 6 years old coin.......
And you even added staking on top of that............................
Total scam

Every coin that has been premined will go into development and support of Argentum NT. The foundation that I have mentioned will be completely transparent about any movement in funds. Regarding staking, I don't know why you would assume that we've added any staking functionality. The blockchain consensus is reached by proof of work

Dude stop bs 50% haha.

There is already enough cryptocurrencies.

I agree.
In fact there are too many cryptocurrencies, many of them abandoned projects.
We are planning ahead and setting aside enough funds to develop our vision. These funds - that belong to the foundation, not to the developers - will benefit every holder of Argentum NT. Anybody who realizes how much of a difference a strong development backbone makes, is not going to mind a high premine.

All the exchanges that are listed are closing ..Is there going to be anther listed i can run 1 th/s on this coin ?

http://zergpool.com/yaamp/ui/css/zergpool_small.png 
 You can mine ArgentumNT at autoexchange mining pool Zergpool.com (http://Zergpool.com) at 0.5% fee. Please use following commands for different mining options
 
 Option 1 Auto coin switch by profitability within algorithm with autoexchange to specified coin wallet(BTC in example below)
 Option 2 Direct coin mining with payout to coin wallet
 Option 3 Direct coin mining with autoexchange to specified coin wallet(BTC in example below)
 Please note mc stands for mining coin symbol, c stand for payout coin symbol
 
 Autoexchange to BTC, LTC, DASH, BCH, DOGE or any other currency we mine
 Happy mining,
  cheers pinpin

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 (https://github.com/Certurium/certurium/releases/tag/v0.18.0.5)
You will be able to find the website at Certuriumcoin.com (http://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.

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 :)

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

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

On Kubuntu:


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 :o

Thanks :)

EDIT: just tried it with



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

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


and


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


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 (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.


If you did everything right, you can finally run certurium by typing 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:

(may not work for all distros)

and then you have to specify

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.

Hey,
the problem lies in the last line:

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 ;)

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

But then I get this error again:

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.

hey vitimers

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


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?

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:


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


Then build it with:


Run it with:


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


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


To start the node again: