News

Read the latest XDAG related announcements.

    1. new hashrate counting system implemented; it is more precise than the existing one; touched to:
      • hashrate of whole network;
      • hashrate of the node;
      • hashrate of each miner;
    2. option ‘-a address’ added; this option allow the miner operate of this specific address instead of default one. This option is dedicated to miners who have several addresses.
      • For example, second address incidentally appears after update.
      • Another example: early solo miner with much of addresses. To use this option one need to know the address and have files wallet.dat, dnet_key.dat and the storage directory.
      • Then, run $ xdag -d -m N -a address pool:port
      • To know all addresses one need to run the program without -a option and type the command ‘account 1000’ or with larger number.
      • Then, one can see balances of these addresses in the balance viewer.
      • Note for early solo-miners: loading blocks could take a time, type the ‘state’ command periodically.
    3. small fixes:
      • transfer to incorrect address forbidded;
      • problem with rounding of smallest digit of amount fixed;
      • files netdb*.txt updated.

    This update recommended for pools on the next planned maintenance. Miners can update if it is necessary.

    new hashrate counting system implemented; it is more precise than the existing one; touched to: hashrate of whole network; hashrate of the node; hashrate of each miner; option ‘-a address’ added; this option allow the miner operate of this specific address instead of default one. This option is dedicated to miners who have several addresses. For example, second address incidentally appears after update. Another example: early solo miner with much of addresses. To use this option one need to know the address and have files wallet.dat, dnet_key.dat and the storage directory. Then, run $ xdag -d -m N -a address pool:port To know all addresses one need to run the program without -a option and type the command ‘account 1000’ or with larger number. Then, one can see balances of these addresses in the balance viewer. Note for early solo-miners: loading blocks could take a time, type the ‘state’ command periodically. small fixes: transfer to incorrect address forbidded; problem with rounding of smallest digit of amount fixed; files netdb*.txt updated.
    01-20
    2018
  • Pools owner! Update please your netdb-white.txt in the working folder.
    Here is current whitelist:
    • 52.5.32.68:13655
    • 199.16.31.96:3355
    • 109.90.229.170:35585
    • 45.63.58.16:13654
    • 52.232.109.201:13654
    • 54.37.158.221:13654
    • 172.105.216.53:3356
    • 47.93.223.203:13655
    • 213.168.251.23:13655

    The last is new my pool where I am migrating to.

    The address for miners will be 213.168.251.23:13654

    Pools owner! Update please your netdb-white.txt in the working folder.
    01-14
    2018
  • T13.816
    1. work with memory is rewritten. The data is now stored in a file that is mapped to memory. This will help if there is not much memory, and the necessary memory is constantly growing.
    2. the new version can be run in parallel with the old one, if you have a powerful server, so as not to interrupt the work of the miners
    3. fixed the error with the damage of about half of the hashes. Because of this, it seemed that the complexity of the network was growing. In fact, power was reduced by half because of this error;
    4. now the pools can xfer their fees to a wallet, not being afraid to steal money from the miners;
    5. you can add pools to the white list without rebooting your pool;
    6. you can donate a certain percentage to the community fund. In this case, the option for the pool will be -P ip:port:maxminers:poolfee:reward:direct:maxipminers:donation

    since the last update, some more pool can be added,as dev said,20 will be running for now to test. We will collect the ask for whitelisting all this day. As watched with dev you can send demand to me via PM, we will need the locations of our pool and at least some spec like bandwitch. Answer will be given as soon as we can give, please be patient.

    T13.816 work with memory is rewritten. The data is now stored in a file that is mapped to memory. This will help if there is not much memory, and the necessary memory is constantly growing. the new version can be run in parallel with the old one, if you have a powerful server, so as not to interrupt the work of the miners fixed the error with the damage of about half of the hashes. Because of this, it seemed that the complexity of the network was growing. In fact, power was reduced by half because of this error; now the pools can xfer their fees to a wallet, not being afraid to steal money from the miners; you can add pools to the white list without rebooting your pool; you can donate a certain percentage to the community fund. In this case, the option for the pool will be -P ip:port:maxminers:poolfee:reward:direct:maxipminers:donation
    01-13
    2018
  • Fixes:
    1. trouble with another address fixed (already!). If you run the program again you should obtain the same address.
    2. some rebranding done:
      • executable renamed to xdag, xdag.exe and xdagwallet.exe
      • prompt is xdag> now
      • currency token is XDAG
      • log file is xdag.log

    Recommended for miners.pool not concerned

    Fixes: trouble with another address fixed (already!). If you run the program again you should obtain the same address. some rebranding done: executable renamed to xdag, xdag.exe and xdagwallet.exe prompt is xdag> now currency token is XDAG log file is xdag.log
    01-11
    2018