Welcome to XDAGJ

中文版

Directory

• System environment
  • Installation and usage
  • Develop
    • XDAG Mars Project
  • Code
  • Contribution
  • Sponsorship
  • Other
  • License

System environment

JDK: v17
Maven: v3.9.1

JDK 17 Download

Eclipse Temurin™ 17 Latest Releases(https://adoptium.net/temurin/releases/)

Maven 3.9.1 Download

Apache Maven 3.9.x Latest Releases(https://maven.apache.org/download.cgi)

Installation and usage

The XDAGJ Testnet Tutorial can help you quickly access XDAGJ testnet by using wallets and mining functions. The Private Chain Building Tutorial helps you to build a private-chain for testing XDAGJ and finding bugs.

XDAGJ_TestNet_Tutorial

XDAGJ_Devnet_Tutorial

XDAGJ TestNet Explorer

Develop

XDAGJ has basic pool functions. Follow-up work will improve system stability and add new functions. The goal is to prepare XDAG for entry into the metaverse. It is important to adopt excellent blockchain technology.

XDAG Mars Project

Four stages:

Exploration phase: XDAGJ testnet is online (online, in beta)

• Deploy XDAGJ test network environment, open beta

• Implement the RandomX algorithm

• Implement the libp2p network protocol

• Testnet blockchain browser

• Test coin acquisition

Landing phase: XDAGJ mainnet is online

• Add test cases: write test cases for existing functions

• Add log functions: provide a relatively complete log service to facilitate troubleshooting

• Optimize synchronization protocol: ameliorate the existing synchronization protocol and improve synchronization efficiency

• Implement the snapshot function: reduce the cost of running a mining pool and boost the loading process

• Implement the RPC function: access Web3j, realize the standardization of the interface

• Introduce the Stratum protocol for miners

• Lightweight wallet application: join the browser wallet

• Standardize the format of public and private keys, follow the BIPXX specification, and add mnemonic words to generate public and private key pairs

Expansion phase: XDAGJ & XRC

• Improve the address block structure

• Increase the handling fee

• Optimize wallets to improve the user experience

• Support XRC standards

• Decrease the threshold of mining pool users

• Open the whitelist to achieve complete decentralization

Prosperity phase: XDAGJ & DeFi

• Implement cross-chain protocols, compatible with access to multiple blockchain systems, to achieve intercommunication between XDAG and other chain worlds

• Implement the oracle function

• Join a distributed exchange

Code

• Git

  We use the gitflow branch model

  • master is the main branch, which is also used to deploy the production environment. Cannot modify the code directly at any time.
  • develop is the development branch, always keep the latest code after completion and bug fixes.
  • feature is a new feature branch. When developing new features, use the develop branch as the basis, and create the corresponding feature/xxx branch according to the development characteristics.
  • release is the pre-launch branch. During the release test phase, the release branch code will be used as the benchmark test. When a set of features is developed, it will be merged into the develop branch first, and a release branch will be created when entering the test. If there is a bug that needs to be fixed during the testing process, it will be directly fixed and submitted by the developer in the release branch. When the test is completed, merge the release branch to the master and develop branches. At this time, the master is the latest code and is used to go online.
  • hotfix is the branch for repairing urgent problems on the line. Using the master branch as the baseline, create a hotfix/xxx branch. After the repair is completed, it needs to be merged into the master branch and the develop branch.

• Commit Message

  The submission message must begin with a short subject line, followed by an optional, more detailed explanatory text, which should be separated from the abstract by a blank line.

• Pull Request

  The pull request must be as clear and detailed as possible, including all related issues. If the pull request is to close an issue, please use the Github keyword convention close, fix, or resolve. If the pull request only completes part of the problem, use the connected keyword. This helps our tool to correctly link the issue to the pull request.

• Code Style

  Use the formatter_eclipse.xml or formatter_intellij.xml of the xdagj code style in the misc/code-style folder.

• Code Review

  We value the quality and accuracy of the code. Therefore, we will review all of the code that needs to be changed.

FAQ

• Time Synchronization Method with NTP XDAGJ_Time_Synchronization

• XDAGJ RPC Document XDAGJ_RPC

Contribution

• Security Question

  XDAGJ is still in the process of large-scale development, which means that there may be problems with existing codes or protocols, or errors that may exist in practice. If you find a security problem, we hope you can report it back as soon as possible.
  
  

  If you find a problem that may affect the security of the deployed system, we hope that you can send the problem privately to xdagj@xdag.io. Please do not discuss it publicly!

  If the problem is a weakness of the agreement or does not affect the online system, it can be discussed publicly and posted to issues.

• Features

  We are very happy to add more useful and interesting new features to XDAGJ. You can suggest any interesting new features that you think would be beneficial.

  If you are interested in the development of XDAGJ, we also welcome you to join the developer team and contribute your strength to XDAGJ. You can get in touch with us at xdagj@xdag.io.

Sponsorship

Since the launch of the Apollo Project, XDAGJ has made a significant breakthrough from 0 to 1. The development of XDAGJ has been on the right track. Your support can drive the successful implementation of XDAGJ technology. XDAG：BkcVG4i1BfxUJLdNPdctaCReBoyn4j32d

Other

XDAGJ New Address Structure

XDAGJ Libp2p Introduction

XDAG Wiki

XDAG Whitepaper

XDAG Protocol

License