Yenten; cryptocurrency of the cpu, by the cpu, for the cpu
Branch: master
Clone or download
Pull request Compare This branch is 47 commits ahead, 15 commits behind conan-equal-newone:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.tx first commit Oct 28, 2017
contrib first commit Oct 28, 2017
doc third commit Feb 25, 2018
docs Update index.md Feb 11, 2019
qa
share
src update to yespower Feb 9, 2019
.gitattributes
.gitignore
COPYING first commit Oct 28, 2017
INSTALL first commit Oct 28, 2017
Makefile.am first commit Oct 28, 2017
README.md Fix README.md Dec 17, 2018
autogen.sh
configure.ac
pkg.m4 first commit Oct 28, 2017

README.md

Yenten Core integration/staging tree

http://yentencoin.info/

  • Copyright (c) 2017- Yenten Core Developers
  • Copyright (c) 2009-2017 Bitcoin Core Developers
  • Copyright (c) 2013-2017 Dash Developers (DarkGravityWave3)
  • Copyright (c) 2014-2017 Alexander Peslyak (Yescrypt Original)

License

Yenten Core is released under the terms of the MIT license. See COPYING for more information or see http://opensource.org/licenses/MIT.

Build yentend on Ubuntu 16.04

sudo apt-get install build-essential
sudo apt-get install libtool autotools-dev autoconf
sudo apt-get install libssl-dev
sudo apt-get install libboost-all-dev
sudo apt-get install pkg-config
sudo add-apt-repository ppa:bitcoin/bitcoin
sudo apt-get update
sudo apt-get install libdb4.8-dev
sudo apt-get install libdb4.8++-dev

git clone https://github.com/yentencoin/yenten.git
cd yenten
./autogen.sh
./configure --enable-upnp-default --without-gui --disable-tests
make

Development tips and tricks

compiling for debugging

Run configure with the --enable-debug option, then make. Or run configure with CXXFLAGS="-g -ggdb -O0" or whatever debug flags you need.

debug.log

If the code is behaving strangely, take a look in the debug.log file in the data directory; error and debugging message are written there.

The -debug=... command-line option controls debugging; running with just -debug will turn on all categories (and give you a very large debug.log file).

The Qt code routes qDebug() output to debug.log under category "qt": run with -debug=qt to see it.

testnet and regtest modes

Run with the -testnet option to run with "play bitcoins" on the test network, if you are testing multi-machine code that needs to operate across the internet.

If you are testing something that can run on one machine, run with the -regtest option. In regression test mode blocks can be created on-demand; see qa/rpc-tests/ for tests that run in -regest mode.

DEBUG_LOCKORDER

Bitcoin Core is a multithreaded application, and deadlocks or other multithreading bugs can be very difficult to track down. Compiling with -DDEBUG_LOCKORDER (configure CXXFLAGS="-DDEBUG_LOCKORDER -g") inserts run-time checks to keep track of what locks are held, and adds warning to the debug.log file if inconsistencies are detected.