Skip to content
Cadex - Reinventing Cryptocurrency
Branch: master
Clone or download
Pull request Compare This branch is 14 commits ahead, 467 commits behind dashpay: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.
.github
.tx
build-aux/m4
cadex-docs cadexpay Dec 9, 2018
contrib
depends
doc
docker
qa
share
src
.gitattributes
.gitignore
.travis.yml
CMakeLists.txt
CONTRIBUTING.md
COPYING
INSTALL.md
Makefile.am
README.md
autogen.sh
configure.ac
libcadexconsensus.pc.in

README.md

Cadex Core staging tree 1.0.0

master: Build Status develop: Build Status

http://cadex.xyz

What is Cadex?

Cadex is a total of dash fork an experimental digital currency that enables anonymous, instant payments to anyone, anywhere in the world. Cadex uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Cadex coin is the name of the open source software which enables the use of this currency. We are building a platform for business solutions

SPECIFICATIONS

Algorithm: x11

Block Reward: 25.16 CADEX, masternode gets 15.017 CADEX of block reward and the rest goes to Miners

RPCPORT: 28280

P2P PORT: 27270

MASTERNODE CONFIGURATIONS

  1. Using the control wallet, enter the debug console (Tools > Debug console) and type the following command:
masternode genkey (This will be the masternode’s privkey. We’ll use this later…)
  1. Using the control wallet still, enter the following command:
getaccountaddress chooseAnyNameForYourMasternode
  1. Still in the control wallet, send 100,000 CADEX to the address you generated in step 2 (Be 100% sure that you entered the address correctly. You can verify this when you paste the address into the “Pay To:” field, the label will autopopulate with the name you chose”, also make sure this is exactly 100,000 CADEX; No less, no more.)
  2. Still in the control wallet, enter the command into the console (This gets the proof of transaction of sending 100,000):
masternode outputs
  1. Still on the main computer, go into the cadex data directory, by default in Windows it’ll be
%Appdata%/CADEXCOIN

or Linux

cd ~/.CADEXCOIN

Find masternode.conf and add the following line to it:

# Format: alias IP:port masternodeprivkey collateral_output_txid collateral_output_index

or follow here

<Name of Masternode(Use the name you entered earlier for simplicity)> <Unique IP address>:51472 <The result of Step 1> <Result of Step 4> <The number after the long line in Step 4>

B. VPS Remote wallet install

  1. From your home directory, download the latest version from the CADEX GitHub repository:
wget https://github.com/cadexproject/cadex/releases/download/v1.0.0/ubuntu16-cli.tar.gz
  1. Unzip and extract:
tar -xvf ubuntu16-cli.tar.gz
  1. Go to your cadexcoin directory:
cd ubuntu16
  1. Note: If this is the first time running the wallet in the VPS, you’ll need to attempt to start the wallet
./cadexd
  1. stop cadexd with
CTRL+C
  1. Now on the masternodes, find the CADEX data directory here.(Linux: ~/.CADEXCOIN)
cd ~/.CADEXCOIN
  1. Open the cadex.conf by typing
vi cadex.conf or nano cadex.conf 
  1. Add the below code in the cadex.conf file
 rpcuser=long random username
 rpcpassword=longer random password
 rpcallowip=127.0.0.1
 rpcport=28280
 listen=1
 server=1
 daemon=1
 logtimestamps=1
 maxconnections=80
 masternode=1
 externalip=your vps ip address
 masternodeprivkey=Result of Step 1
  1. start your vps cadex daemon
./cadexd
  1. Start your masternode from your desktop wallet
masternode start-alias MN1

License

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

Development Process

The master branch is meant to be stable. Development is normally done in separate branches. Tags are created to indicate new official, stable release versions of Dash Core.

The contribution workflow is described in CONTRIBUTING.md.

Testing

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. Further details on running and extending unit tests can be found in /src/test/README.md.

There are also regression and integration tests of the RPC interface, written in Python, that are run automatically on the build server. These tests can be run (if the test dependencies are installed) with: qa/pull-tester/rpc-tests.py

The Travis CI system makes sure that every pull request is built for Windows, Linux, and OS X, and that unit/sanity tests are run automatically.

Manual Quality Assurance (QA) Testing

Changes should be tested by somebody other than the developer who wrote the code. This is especially important for large or high-risk changes. It is useful to add a test plan to the pull request description if testing the changes is not straightforward.

Translations

Changes to translations as well as new translations can be submitted to Dash Core's Transifex page.

Translations are periodically pulled from Transifex and merged into the git repository. See the translation process for details on how this works.

Important: We do not accept translation changes as GitHub pull requests because the next pull from Transifex would automatically overwrite them again.

You can’t perform that action at this time.