There are problems with the signature verification process

OS version : [MacOS BigSur 11.1.2]
XDAGJ version : [XDAGJ-0.4.2]
JDK version : [JDK15.0.2]

In the absence of the other party's private key, transactions belonging to the other party can be generated and verified using only the public key

The mining pool distributes revenue too frequently and generates a large number of blocks

The same blocks between Java and C versions are highly inconsistent

*Describe the new features you want to add
Describe in detail the interesting features you want to achieve.[eg. Hope that XDAGJ will join the virtual machine function so that we can customize our own smart contract]

Use cache to process synchronized blocks

1. Support generating mnemonic words to save the key
2. Support import mnemonic words to generate keys
3. Support the conversion of wallet.data and private key HEX
4. Support import private key HEX to wallet

provide dynamic libraries that can be used directly for linux and windows

The result of unpaid and hashrate calculation is too small

old wallet.dat from C node generate, use password and random params, If these two parameters are not included, an invalid wallet conversion will occur

1.Transfer issues: When there are input areas where the transfer amount needs to be greater than or equal to 6 as input blocks, it will cause the fields of a transaction block to not store information such as input and signature, resulting in an abnormal transaction block.
2. When transferring money, a transaction requires multiple transaction blocks to publish, but only one transaction block will be broadcast, resulting in only one transaction amount that is actually received.

Title
Apache Log4j Security Vulnerabilities

https://logging.apache.org/log4j/2.x/security.html

xdagj has an issue with licenses.
Please check the report.

https://app.fossa.com/projects/git%2Bgithub.com%2FXDagger%2Fxdagj/refs/branch/master/3007261dc34d401389aa5e139c07856039a145e5

Need to reconsider and adjust the accuracy of the amount calculation

Title
Briefly describe your problem

Software information (please complete the following information)

• OS version : [eg. MacOS BigSur 11.1.2]
• XDAGJ version : [eg. XDAGJ-0.4.1-Aplha]
• JDK version : [eg. JDK15.0.2]

Describe the bug
A clear and concise description of what the bug is.

Expected behavior
A clear and concise description of what you expected to happen.

Actual behavior
What actually happened

Log
Provide detailed logs so that we can troubleshoot problems.

Can Reproduce(option)
If can ,If you can, please tell us the detailed steps:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Additional context
Add any other context about the problem here.

can't run any commands

sh xdag.sh -d --account init

8月 05, 2022 11:16:43 下午 org.apache.commons.beanutils.FluentPropertyBeanIntrospector introspect
信息: Error when creating PropertyDescriptor for public final void org.apache.commons.configuration2.AbstractConfiguration.setProperty(java.lang.String,java.lang.Object)! Ignoring this property.
Exception in thread "main" java.lang.UnsatisfiedLinkError: 'int io.xdag.crypto.jni.Native.load_dnet_keys(byte[], int)'
	at io.xdag.crypto.jni.Native.load_dnet_keys(Native Method)
	at io.xdag.config.AbstractConfig.initKeys(AbstractConfig.java:197)
	at io.xdag.Launcher.buildConfig(Launcher.java:165)
	at io.xdag.cli.XdagCli.start(XdagCli.java:160)
	at io.xdag.cli.XdagCli.main(XdagCli.java:149)
	at io.xdag.cli.XdagCli.main(XdagCli.java:156)
	at io.xdag.Bootstrap.main(Bootstrap.java:32)

**Software information **

• OS version : MacOS 12.5 M1
• XDAGJ version : XDAGJ-0.4.9
• JDK version : JDK17.0.4
• Maven version : v3.8.6

Problem Description
With the increase of configuration options, the Config class carries too many miscellaneous configurations

Suggestion(option)
Refactoring configuration options:

1. Mainnet
2. Testnet
3. Devnet

Exception in thread "main" cn.hutool.core.io.resource.NoResourceException: Resource of path [xdag-testnet.config] not exist!

when I compile xdagj and use
nohup java -jar --enable-preview xdagj-0.4.0-shaded.jar > xdagj.log 2>&1 &
run the test net or main net ,It crashes.

Exception in thread "main" cn.hutool.core.io.resource.NoResourceException: Resource of path [xdag-testnet.config] not exist!
at cn.hutool.core.io.resource.ClassPathResource.initUrl(ClassPathResource.java:122)
at cn.hutool.core.io.resource.ClassPathResource.(ClassPathResource.java:74)
at cn.hutool.core.io.resource.ClassPathResource.(ClassPathResource.java:34)
at cn.hutool.core.io.resource.ResourceUtil.getResourceObj(ResourceUtil.java:199)
at cn.hutool.setting.Setting.(Setting.java:128)
at cn.hutool.setting.Setting.(Setting.java:116)
at cn.hutool.setting.Setting.(Setting.java:106)
at io.xdag.config.AbstractConfig.getSetting(AbstractConfig.java:207)
at io.xdag.config.AbstractConfig.(AbstractConfig.java:153)
at io.xdag.config.TestnetConfig.(TestnetConfig.java:32)
at io.xdag.Launcher.buildConfig(Launcher.java:102)
at io.xdag.cli.XdagCli.start(XdagCli.java:126)
at io.xdag.cli.XdagCli.main(XdagCli.java:59)
at io.xdag.cli.XdagCli.main(XdagCli.java:66)
at io.xdag.Bootstrap.main(Bootstrap.java:36)

How can i fix this problem?
I follow this tutorial step by step:
https://github.com/XDagger/xdagj/blob/master/docs/XDAGJ_Private_Chain_Tutorial_eng.md
Can anyone help me ?

Add a verification step to the TERMINATE command line
Once the terminate command is accidentally entered, the system will stop running, adding verification steps can effectively prevent misoperations.
For example, password verification can be performed when using the terminate command, and the program can be terminated only if the verification is passed

Describe the new features you want to add
Add the stratum protocol to the mining pool to provide a better mining experience and support more types of miners

Synchronization problem

• OS version : MacOS BigSur 11.1.2
• XDAGJ version : XDAGJ-0.4.2
• JDK version : JDK15.0.2

Pool synchronization is mainly divided into two scheme, one is obtained in batches based on checksum, which belongs to the synchronization from the starting block to the latest block, and the other is to request from the latest block. The second scheme is abnormal.

Pool will distribute rewards to each miner, and a large number of transaction blocks will be generated for each epoch.
The idea of ​​the solution is as follows:
1)The reward amount less than 10^-9 will not be paid;
2)Each miner reward reaches 1 XDAG before paying；
3)The miner's offline time is greater than the specified time, the reward will be cleared.

Add block backref to record the transaction history

I have some time to do some contribute, but there is no develepment roapmap in this repo, can communities offer a roadmap so that other develeper like me can join the xdagj more easily？

The seed received by the miner is inconsistent with the seed of the mining pool verification difficulty, resulting in a small difficulty of the main block.

The pseudo-block sent by the miner has no input signature, and he can be packaged into the blockchain, and this pseudo-block can accept transfers from other addresses as an address, but he cannot spend the xdag of this address.

C version and java version have a synchronization bug problem, positive and negative synchronization in some specific cases will appear inconsistent.

//|--epoch 1-----|-----epoch 2-----|-----epoch 3-----|
//------A <-------- B <-------- C
//-------------------------|
//-------------------------|------------- D

It will be blocked when switching the main chain, causing synchronization failure.

New wallet password generated when importing old wallet is empty

Title
stop wallet to mine xdag

Software information (please complete the following information)

• OS version : [eg. MacOS BigSur 11.1.2]
• XDAGJ version : [eg. XDAGJ-0.4.1-Aplha]
• JDK version : [eg. JDK15.0.2]

Describe the bug
When a wallet connects a pool, the pool will give little XDAGs to the wallet and generate transactions every minute.

Expected behavior
The pool should not give XDAGs to the wallet as a reward. The pool should close the TCP immediately after the wallet checks the balance, sends the transaction, and confirms the transaction.

Actual behavior
When a wallet connects a pool, the pool will give little XDAGs to the wallet and generate transactions every minute.

Log
Provide detailed logs so that we can troubleshoot problems.

Can Reproduce(option)
If can ,If you can, please tell us the detailed steps:

1. Go to 'www.xdag.io'
2. Download a windows version wallet
3. Connects to the pool
4. See error

Additional context
Add any other context about the problem here.

What is XFS?

The XDAG Funding System is a tool that automates the process of rewards. A contributor should be able to create a proposal, upload and edit a proposal. The proposal should consist of the following:

1. General task description.
2. Milestones with detailed tasks to be finished.
3. Timeline which details an estimated amount of time spent on each
   task.
4. Start and end date for the proposal, and each milestone.
5. Amount of funds required.

Each proposal will be split into a minimum of 2 milestones.
Milestones and proposals must have a status:

1. work-in-progress, 2. in-progress, 3.finished, 4. requires-review, 5. requires-revision.

The definition of these statuses are fairly easy to understand. Payment should only be made once a milestone has been finished with two or more favourable reviews. The community should be able to review proposals, and ask for revisions to current in-progress or under review proposals. Once a proposal has been finished, the remaining funds should be rewarded.

Features include:

1. Easy overview of proposals and their status.
2. Each proposal has its own page with an interface showing relevant information.
3. WYSIWYG text editor which supports Markdown formatting.
4. Funds should be held in escrow. Automatic payment per milestone upon finished review.
5. A review system where each user has the ability to comment, rate, and ask for revisions. The user should also have some form of trust factor.
   A higher rank of trust weighs more than a low rank trust. Trust factorneed not be shown to the end user.
   A clear and concise description of what you want to happen.

Prerequisites & implementation

In this section, I will try to detail what is needed before XFS can be implemented on XDAG.io.

3.1 Prerequisites

1. XDAG RPC.

3.2 Implementation
In this section, I will detail an outline of the preferred implementation.

1. Develop XFS using an object-oriented programming language, such as Python, C++, or Java. The XFS should also have a frontend.
2. The XFS code must be made publicly available as open source.
3. XFS should call the XDAG RPC for payments and balance refreshing.
4. The wallet should be kept in cold storage and not accessed by third parties for payouts.
5. XFS should be hosted separately from the XDAG node.
6. XFS should have a simple UI similar to the block explorer.
7. Automated wallet and address creation. Suggested methods:
   (a) A new wallet with a new address for each proposal.
   (b) The same wallet, but with a new address for each proposal.
   (c) The same wallet with the same address for each proposal, with a different Tx remark for each proposal.

link to the original file from Mathsw : https://drive.google.com/file/d/1gQysWuuZ3WiT28vAvwFVDxyLMzZa7eq2/view?usp=sharing

Add randomX algorithm for the java version of XDAG

The biggest source of Ethereum on the chain and the success of smart contracts, we see that the key to the success of the Ethereum ecosystem is the creation of an EVM virtual machine. At present, the realization of a virtual machine is very important for XDAG. The reasons are as follows:

1. The throughput of Ethereum L1 15 tps/s causes high handling fees (>10$), which greatly limits the development of DAPP
2. Ethereum 2.0 POS has not yet determined the specific launch date, which has a great degree of delay risk and security risk (the topic of POW vs POS is a cliché, not to argue here, but we believe that POW is more secure)
3. XDAG has a natural high TPS design, and POW safety design, and has a good foundation for the development of higher performance DAPP

EVM Illustrated

EVM INSTRUCTIONS

The EVM executes as a stack machine with a depth of 1024 items. Each item is a 256-bit word, which was chosen for the ease of use with 256-bit cryptography (such as Keccak-256 hashes or secp256k1 signatures).

During execution, the EVM maintains a transient memory (as a word-addressed byte array), which does not persist between transactions.

Contracts, however, do contain a Merkle Patricia storage trie (as a word-addressable word array), associated with the account in question and part of the global state.

Compiled smart contract bytecode executes as a number of EVM opcodes, which perform standard stack operations like XOR, AND, ADD, SUB, etc. The EVM also implements a number of blockchain-specific stack operations, such as ADDRESS, BALANCE, KECCAK256, BLOCKHASH, etc.

*Describe the new features you want to add
Describe in detail the interesting features you want to achieve.[eg. Hope that XDAGJ will join the virtual machine function so that we can customize our own smart contract]

Excuse me, does the java version of xdag support windows?

Add global hashrate calculation function

Title
Briefly describe your problem

Software information (please complete the following information)

• OS version : [eg. MacOS BigSur 11.1.2]
• XDAGJ version : [eg. XDAGJ-0.4.1-Aplha]
• JDK version : [eg. JDK15.0.2]

Describe the bug
A clear and concise description of what the bug is.

Expected behavior
A clear and concise description of what you expected to happen.

Actual behavior
What actually happened

Log
Provide detailed logs so that we can troubleshoot problems.

Can Reproduce(option)
If can ,If you can, please tell us the detailed steps:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Additional context
Add any other context about the problem here.

Problem Description
There are many places to manipulate byte arrays in the code, and many third-party tools are used, which makes developers extremely prone to errors when operating. It is recommended to use a unified bytecode manipulation tool to facilitate large-scale use in the future.

Suggestion(option)
Apache tuweni toolkit structured many blockchain byte manipulation toolkits, such as hash using 32 bytes, Bytes32, MutableBytes32 and other very useful tools. It is recommended to use this tool to refactor the code.

The reward is not normal

Libp2p network will connect itself, resulting in abnormal synchronization.
Constantly asking for blocks that are not available to yourself, resulting in synchronization failure

Title
Briefly describe your problem

Software information (please complete the following information)

• OS version : [eg. MacOS BigSur 11.1.2]
• XDAGJ version : [eg. XDAGJ-0.4.1-Aplha]
• JDK version : [eg. JDK15.0.2]

Describe the bug
A clear and concise description of what the bug is.

Expected behavior
A clear and concise description of what you expected to happen.

Actual behavior
What actually happened

Log
Provide detailed logs so that we can troubleshoot problems.

Can Reproduce(option)
If can ,If you can, please tell us the detailed steps:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Additional context
Add any other context about the problem here.

*Describe the new features you want to add
Describe in detail the interesting features you want to achieve.[eg. Hope that XDAGJ will join the virtual machine function so that we can customize our own smart contract]

There are problems with the signature verification process

• OS version : [MacOS BigSur 11.1.2]
• XDAGJ version : [XDAGJ-0.4.2]
• JDK version : [JDK15.0.2]

In the absence of the other party's private key, transactions belonging to the other party can be generated and verified using only the public key

Improve the synchronization speed, modify the synchronization protocol

Add rpc for the java version of XDAG

Synchronization problem

OS version : [MacOS BigSur 11.1.2]
XDAGJ version : [XDAGJ-0.4.2]
JDK version : [JDK15.0.2]

There may be a problem that a certain height block is missing. When the block is not referenced by the main block and the main block, it may be missing.

The existing whitelist mechanism can only restrict active connections to nodes in the whitelist, but cannot avoid the access of non-whitelist nodes

The total number of global variable blocks namin will not decrease when switching the main chain, it will show the total number of blocks before

Exception in thread "main" java.lang.UnsatisfiedLinkError: 'void io.xdag.crypto.jni.Native.dfslib_random_init()'
at mac when run a pool.

After switching to the randomX algorithm, the difficulty is inconsistent after a certain main block