Copyright (c) 2025 The Raqcoin developers
Raqcoin is an experimental new digital currency that enables instant payments to anyone, anywhere in the world. Raqcoin uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Raqcoin is also the name of the open source software which enables the use of this currency.
For more information, as well as an immediately useable, binary version of the RaqcoinCore client software, see www.Raqcoin.info
Before starting the application, you need to create a configuration file raqcoin.conf in the default data directory:
- Linux:
~/.abc/raqcoin.conf - macOS:
~/Library/Application Support/abc/raqcoin.conf - Windows:
%APPDATA%\abc\raqcoin.conf(typicallyC:\Users\YourUsername\AppData\Roaming\abc\raqcoin.conf)
You can find a configuration file example at contrib/debian/examples/raqcoin.conf.
Alternatively, you can specify a custom data directory using the -datadir parameter or a custom configuration file using the -conf parameter when starting the application.
RaqcoinCore is released under the terms of the GNU GPL v. 3 license. See https://www.gnu.org/licenses/gpl-3.0.en.html for more information.
THIRD PARTY SOFTWARE DISCLOSURE, ATTRIBUTIONS, COPYRIGHT NOTICES, AND LICENSES
Certain open source third-party software and data components are integrated and/or redistributed with RaqcoinCore. Such third-party components include terms and conditions, such as attribution and liability disclaimers (collectively "Third Party Disclosures") for which disclosure is required by their respective owners. This notice sets forth such Third Party Disclosures for RaqcoinCore.
RAQCOIN FOUNDATION MAKES NO REPRESENTATION, WARRANTY OR OTHER COMMITMENT REGARDING SUCH THIRD PARTY COMPONENTS. RAQCOINCORE, AND ALL THIRD PARTY COMPONENTS, ARE DISTRIBUTED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED, UNLESS PROHIBITED BY APPLICABLE LAW
-
Openssl • Copyright (c) 1998-2018 The OpenSSL Project, all rights reserved • Copyright (c) 1995-1998 Eric A. Young, Tim J. Hudson, all rights reserved • All rights reserved. • URL: https://www.openssl.org/ • Version: 1.1.0g • License 1: Original SSLeay License • License 2: Apache License 1.0 • License 3: Apache License 2.0
-
Berkeley DB
• Copyright (c) 1990, 1993, 1994, 1995 The Regents of the University of California, all rights reserved • Copyright (c) 1995, 1996 The President and Fellows of Harvard University, all rights reserved • URL: http://www.oracle.com/technetwork/database/database-technologies/berkeleydb/overview/index.html • Version: 5.1.29 • License: Affero General Public License v.3
-
Level db • Copyright (c) 2011 The LevelDB Authors. All rights reserved. • URL: http://leveldb.org/ • Version:1.1 • License: BSD License Clause 3
-
Boost • Copyright Beman Dawes, David Abrahams, 1998-2005. • Copyright Rene Rivera 2004-2005. • URL: https://www.boost.org/ • Version: 1.65.0 • License: Boost Software License
-
libpng • libpng versions 1.0.7, July 1, 2000 through 1.6.32, August 24, 2017 are Copyright (c) 2000-2002, 2004, 2006-2017 Glenn Randers-Pehrson, are derived from libpng-1.0.6, and are distributed according to the same disclaimer and license as libpng-1.0.6 with the following individuals added to the list of Contributing Authors:
o Simon-Pierre Cadieux o Eric S. Raymond o Mans Rullgard o Cosmin Truta o Gilles Vollant o James Yu o Mandar Sahastrabuddhe o Google Inc. o Vadim Barkov • URL: http://libpng.org/ • Version: 1.6.16 • License: libpng license
-
Protocol buffer • Copyright 2008 Google, Inc. • URL: https://developers.google.com/protocol-buffers/ • Version: 2.6.1 • License: BSD
-
qrencode • Copyright 2006-2017 Kentaro Fukuchi [email protected]. • URL: https://fukuchi.org/works/qrencode/manual/index.html • Version: 3.4.4 • License: GNU Lesser General Public License 2.1
-
Qt • Copyright Various Years, QT Company • URL: www.qt.io • Version: 5.6.3 • License GPL v. 2; GPL v. 3; : LGPL v. 3
-
Google Test • Copyright 2008, Google Inc., all rights reserved • URL: https://github.com/google/googletest/ • Version: • License BSD 3-Clause
-
MiniUPnP • Copyright (c) 2006-2017, Thomas BERNARD, all rights reserved • URL:http://miniupnp.free.fr/ • Version: 2.1 • License: MiniUPnP License
-
Bitcoin Core • Copyright (c) 2009-2018 The Bitcoin Core developers • URL:https://bitcoin.org/en/bitcoin-core/ • Version:0.8.6 • License: MIT License
-
libFES algorithm • URL: http://www.lifl.fr/~bouillag/fes/index.html • Version:0.2 • GPL V3
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 RaqcoinCore development team members simply pulls it.
If it is a more complicated or potentially controversial change, then the patch submitter will be asked to start a discussion (if they haven't already) on the mailing list.
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/coding.md) 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 Raqcoin.
Testing and code review is the bottleneck for development; we get more pull requests than we can review and test. Please be patient and help out, and remember this is a security-critical project where any mistake might cost people lots of money.
Developers are strongly encouraged to write unit tests for new code, and to
submit new unit tests for old code.
Unit tests for the core code are in src/test/. To compile and run them:
cd src; make -f makefile.unix test
Unit tests for the GUI code are in src/qt/test/. To compile and run them:
qmake RAQCOIN_QT_TEST=1 -o Makefile.test raqcoin-qt.pro
make -f Makefile.test
./raqcoin-qt_test
Every pull request is built for both Windows and Linux on a dedicated server,
and unit and sanity tests are automatically run. The binaries produced may be
used for manual QA testing — a link to them will appear in a comment on the
pull request posted by (https://github.com/RAQ-coin/). See https://github.com/RAQ-coin/Raqcoin-test
for the build/Raqcoin-test.
Large changes should have a test plan, and should be tested by somebody other than the developer who wrote the code.
See https://github.com/RAQ-coin/Raqcoin/QA/ for how to create a test plan.
A new program that can be used to do ABC mining on a GPU is recently release at http://polycephaly.org/projects/forcemq/data/MQForceGPU-20180724.tgz
To use it correctly, one may have to do some small adjustments.