Skip to content
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
99 lines (66 sloc) 4.31 KB

DOMO Core integration/staging tree

What is DOMO?

DOMOcoin will be used as a 'ticket' to enter the community in the future (proof of ownership). We are developing the first prototype of a new kind of social network approach. Only people holding Domocoins in their wallet will be able to login to the network. This way mostly only 'crypto' and blockchain enthusiasts will join the community and create an environment Cryptotwitter is dreaming of. After reaching a decent amount of unique users within the prototype, we will do a official crowdfunding to develop a open source, decentralized, autonomous social network, which is not run by a single entity or centralized servers. This is your chance to join the team in early stages, earn a masternode for your effort and be hired to build a social network, which can´t be taken down by institutions and is maintained by the people actually using it.

The DOMO Community is essential part of Domocoin and will help to develop the project outside the boundarys of our initial goals. All future Blockchains and Projects will be carried out on the DOMO community, acting as testing, evaluating and developing entity in the Blockchain era.

For more information, as well as an immediately useable, binary version of the DOMO Core software, see


DOMO Core is released under the terms of the MIT license. See COPYING for more information or see

Development process

Developers work in their own trees, then submit pull requests when they think their feature or bug fix is ready.

If it is a simple/trivial/non-controversial change, then one of the DOMO development team members simply pulls it.

The patch will be accepted if there is broad consensus that it is a good thing. Developers should expect to rework and resubmit patches if the code doesn't match the project's coding conventions (see doc/ or are controversial.

The master branch is regularly built and tested, but is not guaranteed to be completely stable. Tags are created regularly to indicate new official, stable release versions of DOMO.


Testing and code review is the bottleneck for development; we get more pull requests than we can review and test on short notice. Please be patient and help out by testing other people's pull requests, and remember this is a security-critical project where any mistake might cost people lots of money.

Automated Testing

Developers are strongly encouraged to write unit tests for new code, and to submit new unit tests for old code. Unit tests can be compiled and run (assuming they weren't disabled in configure) with: make check

Manual Quality Assurance (QA) Testing

Large changes should have a test plan, and should be tested by somebody other than the developer who wrote the code.

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.


If the code is behaving strangely, take a look in the debug.log file in the data directory; error and debugging messages 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 DOMOs" 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 -regtest mode.


DOMO 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 which locks are held, and adds warnings to the debug.log file if inconsistencies are detected.

You can’t perform that action at this time.