NEWS

The announcements of XDAG.

  • We are pleased to announce that XDAG v0.2.2 is released.

    1. XDag v0.2.2 release
    2. Github

    Change list:

    • 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 to 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 the purpose to protect pool againnst DDOS and cheating with shares.
      • If you use several connections with the same address you can no longer 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 at the moment.
    • Some log messages are disabled during the loading process of the storage. It can help to decrease count of disk I/O operations and speed up the loading of storage folder.
    • DAG takes too much space in memory. Pools use temporary files for swapping in order to decrease memory usage. A new configuration “-z” was added:
      • -z - 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 a transfer, you will see this 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/ksk5SsT5PqLhAwCUhqtBFNPB6WizsDk0

    Currently you can use field “Flags” to find out the 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 the following 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.

    For pool owners: The configuration for pool was updated. A new parameter “maxconn - maximum allowed number of miners with the same address” was added. Also parameters were reordered.

    -P ip:port:CFG - run the pool, bind to ip:port, 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 percent
    

    Example of command line for starting pool (for test net):

    xdag -t -p 213.21.5.18:3366 -P 213.21.5.18:454:1000:100:60:1:1:1:1
    

    Output of miners command was changed. Example:

    xdag> miners
    List of miners:
     NN  Address for payment to            Status   IP and port            in/out bytes      nopaid shares
    ------------------------------------------------------------------------------------------------------
     -1. EacdO89D9vDursfUP4dsPHvHu1mnKdHP  fee      -                      -                 0.000000
      0. XUSGrE0EHNLZ1OMZqv7pvbBa4YRA+zKp  active   -                      -                 34.238053
     C1. -                                 -        127.0.0.1:50013        9568/4800         34.238053
     C2. -                                 -        127.0.0.1:50634        576/96            0.135454
      1. CtuR8NizlQHSb09T8fV3bURYCEmQ/jcN  active   -                      -                 31.848017
     C1. -                                 -        127.0.0.1:50024        10944/4640        31.848017
      2. qJ4ytVsbjyiuDP57XaLo1ia323XeHFS8  archive  -                      -                 13.180378
    ------------------------------------------------------------------------------------------------------
    Total 2 active miners.
    

    Now all connections with the same address are grouped. Disconnected miners are marked with “archived” state. Archive miners are removed from the list when all shares are paid. In order to see the list in the old format, you can use command “miners conn.”

    xdag> miners conn
    List of miners:
     NN  Address for payment to            Status   IP and port            in/out bytes      nopaid shares
    ------------------------------------------------------------------------------------------------------
      0. XUSGrE0EHNLZ1OMZqv7pvbBa4YRA+zKp  active   127.0.0.1:50013        9600/4800         34.238053
      1. CtuR8NizlQHSb09T8fV3bURYCEmQ/jcN  active   127.0.0.1:50024        10976/4640        31.848017
      2. XUSGrE0EHNLZ1OMZqv7pvbBa4YRA+zKp  active   127.0.0.1:50634        576/96            0.135454
    ------------------------------------------------------------------------------------------------------
    Total 3 active miners.
    

    This list shows only active connections. The new version no longer has “archive connections”.

    We are pleased to announce that XDAG v0.2.2 is released.
    05-18
    2018
  • Due to the recent events the following recommendations and decisions have been made by the community and developer team.

    Only use pools listed in the whitelist. Even though it’s very restraining in its current state, using only approved pools is vital for the health of the network. For now, every submission regarding whitelist addition will be audited. This will continue until the network is fully stable. The following requirements have to be fulfilled in order to apply for a pool:

    • No private pools
    • A public frontend would be appreciated. If you don’t want to add one, please provide at least:
      • Pool status must be exposed in real time (maximum interval time: one minute) by HTTP
      • Pool net conn must be exposed in real time (maximum interval time: one minute) by HTTP
    • Server time zone must be set to UTC time zone
    • Must use ntpdate to synchronize time
    • Must use root or unlimited user (max open files limit set to more then 4096) to start pool process
    • Do not try to change the hardcode of max miners
    • Server configuration with 8-core CPU, 32G RAM, SSD raid0/raid10 and above
    • 1Gbit/s Internet Speed and above

    The contact person of a pool must be added to the Discord poolowner group.

    Regarding whitelist additions, please send your requests to: pool@xdag.io. No other ways will be accepted for now.

    In your email request, please include this list and fill out everything.

    1. 1 Pool IP:
    2. 2 Pool Configuration:
      • 2.1 Pool config:
      • 2.2 NTP config:
      • 2.3 Timezone config:
    3. 3 Pool hardware configuration:
      • 3.1 CPU:
      • 3.2 RAM:
      • 3.3 Disk:
      • 3.4 Internet bandwidth:
    4. 4 Pool frontend:
      • 4.1 Stats through HTTP:
      • 4.2 Net conn through HTTP:
      • 4.3 Pool frontend link (optional):
    5. 5 Pool Owner:
    Due to the recent events the following recommendations and decisions have been made by the community and developer team.
    05-12
    2018
  • Pools are open for mining again as of 15:45 UTC. Per agreement between all the pool owners there are no fees (0%).

    100% of the block reward goes to the miners.

    Pools are open for mining again as of 15:45 UTC. Per agreement between all the pool owners there are no fees (0%).
    05-10
    2018
  • The current status of the network is progressing well. We are going to wait for the few left blocks to finish and verify the integrity of the network.

    We have decided not to rollback.

    More information will be announced later.

    The current status of the network is progressing well. We are going to wait for the few left blocks to finish and verify the integrity of the network.
    05-10
    2018
  • Recently there have been some issues regarding the mainnet desynchronization. Last night, several pool owners reported a DDoS attack. The pools in mainland China generated a lot of traffic to the rest of the international pools. Sadly, the Great Firewall of China controls traffic to and from mainland China, and the bandwidth is heavily restricted which resulted in desynchronization issues between mainland Chinese pools and international pools. The issues with slow synchronization of blocks further increased the problems.

    Temporarily, it has been negotiated with some Chinese pool owners to move their pools outside of mainland China due to firewall restrictions. Pools with mainland Chinese IP addresses have temporarily been removed from the whitelist.

    In the future, we are going to investigate and give recommendations of hardware configurations to make sure that pools run optimally. The whitelisted pools will also be audited so that the configuration does not interfere with the network. To do this, we would like all pool owners to keep in contact with the developers and the rest of the community to ensure that everything works smoothly.

    In the meanwhile, the development team will start to work on optimizing the network layer to avoid desynchronization issues.

    The plan for returning to a stable network is as follows:

    1. Pools which are in a non-fork status will synchronize for 24 hours.
    2. If the pools are in normal operation within 24 hours, the network will slowly expand to allow more pools.
    3. If the pools are not synchronized within 24 hours, there is a need for an emergency rollback to a previous state.

    Pool owners who can be trusted by the community miners and volunteer to do this rollback are advised to contact the development team. There are already several pools that volunteer to do this.

    In the case of a rollback, if you are affected by a loss of coins, please contact communitymanager@xdag.io. If you lost coins due to a trade, first contact the person you performed the trade with. If you lost coins due to an exchange trade, please contact the specific exchange.

    Recently there have been some issues regarding the mainnet desynchronization. Last night, several pool owners reported a DDoS attack. The pools in mainland China generated a lot of traffic to the rest of the international pools. Sadly, the Great Firewall of China controls traffic to and from mainland China, and the bandwidth is heavily restricted which resulted in desynchronization issues between mainland Chinese pools and international pools. The issues with slow synchronization of blocks further increased the problems.
    05-09
    2018