Hi all!
XDag v0.2.2 is released.
https://github.com/XDagger/xdag/releases/tag/0.2.2Github:
https://github.com/XDagger/xdagList of changes:
- transaction address is shown in the console version, you can track the status of your transaction in the block explorer
- new field "State" was added to the output of the "block" command. See description below
- a bug in DNET which could break synchronization between pools is fixed
- a bug in block validation logic which could lead to divergence of balances between pools is fixed
- large changes in the mining:
- unpaid shares are paid even if miner is disconnected
- miners who use several rigs with one wallet address recieve only one total payment, not several payments corresponding to the number of connections. It should help to decrease network load
- restriction on count of connections with the same address was added. This count can be configured, see description below
- count of shares per task from one connection was restricted to 20, if count of shares exceeds 20 (during one minute) miner is disconnected. It was made with purpose to protect pool againg DDOS and cheating with shares.
- if you use several connections with the same address you no longer can send the same shares. All shares must be unique
- output of the miners command was changed. See description below
- max count of connections was increased to 8192
- small update in the GUI wallet
- draft version of JSON-RPC. Not ready for exchanges now
- some log messages are disabled during loading the storage. It can help to decrease count of disc I/O operations and speed up the loading of storage folder
- DAG takes too much space in the memory. Pools use temporary files for swapping in order to decrease memory usage. A new configuration "-z" was added:
- -z <path> - you can set path to temp-file folder
- -z RAM - use RAM instead of temp-files. It can speed up loading of storage and make the pool faster, but demands large amout of free memory
Transaction address:
After you transfer message you will see message "Transaction address is xxxxxxxxxxxxxx, it will take several minutes to complete the transaction.". Example:
xdag> xfer 5 EnTkFVTGB+J4oKHHTQIay3Q3Zc1a8s0u
Password:
Xfer: transferred 5.000000000 XDAG to the address EnTkFVTGB+J4oKHHTQIay3Q3Zc1a8s0u.
Transaction address is ksk5SsT5PqLhAwCUhqtBFNPB6WizsDk0, it will take several minutes to complete the transaction.
You can use that address to track your transaction, for example:
https://explorer.xdag.io/block/ksk5SsT5PqLhAwCUhqtBFNPB6WizsDk0Currently you can use field "Flags" to find out state of the transaction (block):
0 - block is just recieved
10 - block is in processing
1c - block is accepted
1F - it is main block
18 - block is rejected. It can be caused by insufficient balance or synchronization problems
New version has a new field "state" with values:
- Pending
- Accepted
- Rejected
- Main
Example:
xdag> block gkileoNyIQ+24I82gBKXcsm1wZSKHIVd
time: 2018-05-18 01:59:27.916
timestamp: 16bf8253fab
flags: 0
state: Pending
file pos: 200
hash: 0c93950ebed441c95d851c8a94c1b5c972971280368fe0b60f2172837aa54882
difficulty: 00000001c7a2f05a0
balance: gkileoNyIQ+24I82gBKXcsm1wZSKHIVd 0.000000000
-------------------------------------------------------------------------------------------
block as transaction: details
direction address amount
-------------------------------------------------------------------------------------------
fee: NjVnGThQVNPsMnMwgRPTJQWvmsBNSCTB 0.000000000
output: CtuR8NizlQHSb09T8fV3bURYCEmQ/jcN 0.000000000
input: CtuR8NizlQHSb09T8fV3bURYCEmQ/jcN 50000.000000000
output: XUSGrE0EHNLZ1OMZqv7pvbBa4YRA+zKp 50000.000000000
-------------------------------------------------------------------------------------------
block as address: details
direction transaction amount time
-------------------------------------------------------------------------------------------
Existing block explorers can use this field to show the block state.
Poll
