XDAGJ is a Java implementation of XDAG. It is rebuilt on the basis of C Version XDAG. For more information, please check XDagger .
Alpha version is being improved.
XDAG：+89Zijf2XsXqbdVK7rdfR4F8+RkHkAPh
JDK : v1.8
Maven : 3.6.3Make sure the above environment is installed before you build this project.
XDAGJ_Networking_Specification
The generated files are stored in MainNet/TestNet during runtime. It depends on whether you access main network or the test network.
* dnet_key.dat : Used to verify your password
* wallet_*.dat : Store your accounts' private key
* Rocksdb : Storage blocks
* sumsStoreDir : Blocks sums storage path
* storeDir : Block information storage path (include block, account and orphan) Download the source code from the master branch.
Configure a new library file for it.
> cd src/c
> make_so.bat ## for Windows
> ### or for Mac OS or Linux
> make_so.sh> git clone https://github.com/XDagger/xdagj.git
> cd xdagj
> mvn clean package In XDAGJ，resource/conf.setting is a global configuration file. If specified configuration parameters are not configured，the default parameters will be used.Refer hutool
To avoid stack overflow, increase the STACK value of the JVM to at least 4096k when loading the test network data.
The startup method based on the default configuration file :
> java -jar xdagj.jar
> run ##start the program
> terminate ##trun offStartup method with the appointed configuration file:
> java -jar xdagj.jar -f [file storage path] -t -p [ip：port] -P [CFG]For more commands:
> java -jar xdagj.jar -hRefer How to build a test environment
start para:
-t [Use testnet]
-f yourpath [Change the file storage path to yourpath ]
-p ip:port [Bind ip:port as whitelist address]
-P (CFG)
[set pool config; CFG is miners:maxip:maxconn:fee:reward:direct:fund
miners - maximum allowed number of miners
maxip - maximum allowed number of miners connected from single ip
maxconn - maximum allowed number of miners with the same address
fee - pool fee in percent
reward - reward to miner who got a block in percent
direct - reward to miners participated in earned block in percent
fund - community fund fee in percentExecution parameters :
xdag> run [Run,start working]
xdag> account N [Check your accounrs ,N is optional ]
xdag> state [Check your pool state if you are connected to other pool]
xdag> stats [Check network status]
xdag> balance [Check you balance]
xdag> block A [Check the block info use hash or address]
xdag> mainblocks N [Print list of N (20 by default) main blocks]
xdag> minedblocks N [Print list of N (20 by default) main blocks mined by current pool]
xdag> keygen [Generate new private/public key pair and set it by default]
xdag> net conn [List connections]
xdag> net connect ip:port [connect a new pool]
xdag> miners [Printf list of activite miners in our pool]
xdag> xfer N A [Transfer N XDAG to the address A]
xdag> disconnect all|ip:port [all : disconnect all miners / ip:port disconnect the specified miner]
xdag> exit [Terminate xdag process]
xdag> terminate [Terminate xdag process]This is an Open Source Project and we welcome all sorts of contributions, including reporting issues, contributing code, and helping us improve our community. Here are the instructions to get you started.
Whether you find any errors, bugs or inconsistencies in the code or documents of the XDAGJ project, or have any other problems or suggestions, please let us know on the Issue section.
The main Issues for bug reporting are as follows:
When considering design proposals for implementations, we are looking for:
- A description of the problem this design proposal solves
- Discussion of the tradeoffs involved
- Discussion of the proposed solution
We use a simple git branching model:
mastermust always workdevelopis the branch for development- create feature-branches to merge into
develop - all commits must pass testing so that git bisect is easy to run
Just stay current with develop (rebase).
Commit messages must start with a short subject line, followed by an optional, more detailed explanatory text which is separated from the summary by an empty line.
Write clean code. Universally formatted code promotes ease of writing, reading, and maintenance.
Update documentation when creating or modifying features. Test your documentation changes for clarity, concision, and correctness, as well as a clean documentation build.
The pull request must be as clear as possible and as detailed as possible, including all related issues. If the pull request is meant to close an issue please use the Github keyword conventions of closes, fixes, or resolves. If the pull request only completes part of an issue use the connects keywords. This helps our tools properly link issues to pull requests.
use xdagj code style formatter_eclipse.xml or formatter_intellij.xml at misc/code-style folder import to your IDE for format code.
We value the quality and accuracy of the code. Therefor, we will review all the codes that need to be changed.
We use Thank you for your efforts. in comments on the code review to indicate acceptance. A change requires Thank you for your efforts. from the maintainers of each component affected. If you know whom it may be, ping them.
