xdagger / xdag

XDAG (Dagger Coin) Official Main Repository. XDAG is a novel DAG based cryptocurrency.

The Dagger (XDAG) cryptocurrency

• Community site: https://xdag.io
• The Main net was launched January 5, 2018 at 22:45 GMT

Principles:

• Directed acyclic graph (DAG), not blockchain
• Block = transaction = address
• Original idea and implementation
• Mineable, no premine, no ICO
• Mining new money every 64 seconds

HOW-TO:

• How to get a wallet
• How to getting started
• How to find pools
• How to contribute

Docs:

• Wiki
• Whitepaper 中文版
• Protocol 中文版
• License

Main chain idea:

Every block in DAG has up to 15 links to another blocks (inputs and outputs). Block B is referenced by another block A if we can reach B from A by following the links. Chain is a sequence of blocks each of which is referenced by the previous block. Chain is called distinct if every its block belongs to separate 64-seconds interval. Difficulty_of_block is 1/hash where hash is sha256(sha256(block)) regarded as little-endian number. Difficulty_of_chain is sum of difficulties of blocks. Main_chain is the distinct chain with maximum difficulty. Blocks in main chain are called main_blocks.

Daggers are mined in every main block. There are three periods of mining:

Stage 1	Stage 2	Stage 3
Block #1 to #1,017,322	Block #1,017,323 to #2,097,151	Each 2,097,152 blocks
1024 XDAG each block	128 XDAG each block	64 * (1/2)^n XDAG each block

The maximum XDAG supply is approximately 1.446294144 billion.

Each dagger is equal to power(2,32) cheatoshino. Transaction is valid if it is referenced by a main block. Valid transactions are strictly ordered depending on main chain and links order. Double spending is prohibited because only first concurrent transaction (by this order) is applied.

Structure of block:

The on-disk format will change in the future. Consider this the network protocol. Each block has a fixed size of 512 bytes. Block consists of 16 fields each of which has length 32 bytes. Field 0 is header, it consists of 4 quadwords:

• transport-layer header
• types of all 16 fields, 4 bits for one type
• timestamp of the block, in seconds from Unix era * 1024
• block fee in cheatoshi

Types of fields:

0. nonce
1. header
2. transaction input: 24 lower bytes of block hash and 8 bytes of input amount
3. transaction output, structure is the same as input
4. half of block signature; ECDSA number r or s; digest for signature is hash of (block concate public key)
5. half of output signature; only owner of this key can use this block as input
6. public key (x) with even y
7. public key with odd y
8. header of testnet
9. ... 15. are reserved for future usage.

Transport layer:

The dnet network is used as transport layer. A new transport layer will come in the future.

Maintainers:

Evgeniy ( XDAG: gKNRtSL1pUaTpzMuPMznKw49ILtP6qX3, BTC: 1Jonano4esJzZvqNtUY6NwfPme3EMpVs7n )
Frozen ( XDAG: +L5dzSh1QZv1We3wi8Of31M8eHwQJq4K )

Code Contributors:

• trueserve
• sgaragagghu
• Sofarlemineur
• Chen Zhen
• kbs1
• amwsffgu
• s2n-gribbly
• reymondtu
• sugaryen
• mojs78
• rubencm
• SantoMacias
• cnukaus
• mathsw
• ruben
• Dengfeng Liu
• BinaryOverflow
• Caleb Marshall
• NKU-Nikoni
• Elder Ryan
• hughchiu
• Mingege
• p2peer
• ZR

Full list of contributors including all contributors for XDAG sub-projects.

License

xdag's Issues

Add those RPC functions,thanks

XDAG RPC functions requirement:
base functions:
1.set rpc user and passwrod
2.set up rpc allow ip.
3.set rpc listen port
pool info
1.getpoolinfo(blcoks ,main blocks)
2.getpoolstate (pool state)
3.get peerinfo (net conn)
4.block notify (when a new block foud notfy some one)
5. rpc log (set some level )
exchange
1.get newaddress
2.get balance
3.getBalanceByAddress
4.list transactions N (list last transactions)
5.getblocks (block hash ,txid ,wallet address)
safty
1.import privkey /dump privkey
2. change password
3.walletLock,walletPassphrase

openxdagpool-scripts setup error: there is not cheatcoin folder and xdag_run.sh

Once all is done, go to templates directory in this repository, and COPY all files to both xdag1/cheatcoin and xdag2/cheatcoin. Edit the xdag_run.sh file in both folders with your pool settings.
Re-execute xdag1 using ./xdag_run.sh in xdag1/cheatcoin folder without the -r option (script will ask). Wait for the pool to start up and load blocks from the storage.

in openxdagpool-scripts>readme file , there is not cheatcoin folder and xdag_run.sh 。

how to generate a new address ?

how to generate a new address ?

Loading of storage folder by pools take too much time

It takes about 17 hours now.

in help, still cheatcoin reference

$ xdag
xdag client/server, version 0.2.1.
Usage: xdag flags [pool_ip:port]
If pool_ip:port argument is given, then the node operates as a miner.
Flags:
-a address - specify your address to use in the miner
-c ip:port - address of another cheatcoin full node to connect
-d - run as daemon (default is interactive mode)
-h - print this help
-i - run as interactive terminal for daemon running in this folder
-l - output non zero balances of all accounts
-m N - use N CPU mining threads (default is 0)
-p ip:port - public address of this node
-P ip:port:CFG - run the pool, bind to ip:port, CFG is miners:fee:reward:direct:maxip:fund
miners - maximum allowed number of miners,
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,
maxip - maximum allowed number of miners connected from single ip,
fund - community fund fee in percent
-r - load local blocks and wait for 'run' command to continue
-s ip:port - address of this node to bind to
-t - connect to test net (default is main net)
-v N - set loglevel to N

make error

In file included from address.c:3:0:
/usr/lib/gcc/x86_64-alpine-linux-musl/6.4.0/include/stdint.h:9:26: error: no include path in which to search for stdint.h
 # include_next <stdint.h>
                          ^
address.c:4:20: fatal error: string.h: No such file or directory
 #include <string.h>
                    ^
compilation terminated.
block.c:3:20: fatal error: stdlib.h: No such file or directory
 #include <stdlib.h>
                    ^
compilation terminated.
crypt.c:3:20: fatal error: string.h: No such file or directory
 #include <string.h>
                    ^
compilation terminated.
hash.c:3:20: fatal error: string.h: No such file or directory
 #include <string.h>
                    ^
compilation terminated.
init.c:3:19: fatal error: stdio.h: No such file or directory
 #include <stdio.h>
                   ^
compilation terminated.
log.c:3:19: fatal error: stdio.h: No such file or directory
 #include <stdio.h>
                   ^
compilation terminated.
In file included from main.c:3:0:
init.h:6:18: fatal error: time.h: No such file or directory
 #include <time.h>
                  ^
compilation terminated.
memory.c:3:20: fatal error: stdlib.h: No such file or directory
 #include <stdlib.h>
                    ^
compilation terminated.
netdb.c:3:19: fatal error: stdio.h: No such file or directory
 #include <stdio.h>
                   ^
compilation terminated.
pool.c:3:19: fatal error: stdio.h: No such file or directory
 #include <stdio.h>
                   ^
compilation terminated.
sha256.c:16:20: fatal error: stdlib.h: No such file or directory
 #include <stdlib.h>
                    ^
compilation terminated.
storage.c:3:19: fatal error: stdio.h: No such file or directory
 #include <stdio.h>
                   ^
compilation terminated.
sync.c:3:20: fatal error: stdlib.h: No such file or directory
 #include <stdlib.h>
                    ^
compilation terminated.
transport.c:3:20: fatal error: stdlib.h: No such file or directory
 #include <stdlib.h>
                    ^
compilation terminated.
wallet.c:3:20: fatal error: stdlib.h: No such file or directory
 #include <stdlib.h>
                    ^
compilation terminated.
In file included from commands.c:1:0:
commands.h:4:18: fatal error: time.h: No such file or directory
 #include <time.h>
                  ^
compilation terminated.
terminal.c:2:20: fatal error: stdlib.h: No such file or directory
 #include <stdlib.h>
                    ^
compilation terminated.
../dnet/dnet_crypt.c:3:19: fatal error: stdio.h: No such file or directory
 #include <stdio.h>
                   ^
compilation terminated.
../dnet/dnet_database.c:3:20: fatal error: stdlib.h: No such file or directory
 #include <stdlib.h>
                    ^
compilation terminated.
../dnet/dnet_main.c:3:19: fatal error: stdio.h: No such file or directory
 #include <stdio.h>
                   ^
compilation terminated.
../dnet/dnet_threads.c:3:20: fatal error: stdlib.h: No such file or directory
 #include <stdlib.h>
                    ^
compilation terminated.
../dnet/dnet_connection.c:3:20: fatal error: stdlib.h: No such file or directory
 #include <stdlib.h>
                    ^
compilation terminated.
../dnet/dnet_stream.c:5:20: fatal error: stdlib.h: No such file or directory
 #include <stdlib.h>
                    ^
compilation terminated.
../dnet/dnet_packet.c:3:20: fatal error: stdlib.h: No such file or directory
  include <stdlib.h>
▽                   ^
compilation terminated.
../dnet/dnet_command.c:3:20: fatal error: stdlib.h: No such file or directory
 #include <stdlib.h>
                    ^
compilation terminated.
../dnet/dnet_log.c:3:20: fatal error: stdlib.h: No such file or directory
 #include <stdlib.h>
                    ^
compilation terminated.
../dnet/dnet_files.c:3:19: fatal error: stdio.h: No such file or directory
 #include <stdio.h>
                   ^
compilation terminated.
../dnet/dnet_tap.c:30:19: fatal error: stdio.h: No such file or directory
 #include <stdio.h>
                   ^
compilation terminated.
../dus/programs/dfstools/source/dfslib/dfslib_random.c:3:20: fatal error: stdlib.h: No such file or directory
 #include <stdlib.h>
                    ^
compilation terminated.
../dus/programs/dfstools/source/lib/dfsrsa.c:3:19: fatal error: stdio.h: No such file or directory
 #include <stdio.h>
                   ^
compilation terminated.
../dus/programs/dar/source/lib/crc_c.c:17:33: fatal error: stdlib.h: No such file or directory
 #include <stdlib.h> /* T5.245 */
                                 ^
compilation terminated.
In file included from ../utils/utils.c:9:0:
../utils/utils.h:12:19: fatal error: stdio.h: No such file or directory
 #include <stdio.h>
                   ^
compilation terminated.
make: *** [Makefile:97: xdag] Error 1

pls help me

Help, a problem with a wallet.

Hello. How to restore a wallet. After restart of a wallet, it hangs on initialization?

crash with terminate command

2018-06-03 02:18:16.652 [7000004ef000:FATA] Signal 11 delivered
2018-06-03 02:18:16.653 [7000004ef000:FATA] RIP=100f6fb38, EFL=10202, ERR=4, CR2=10c7e9070,
2018-06-03 02:18:16.653 [7000004ef000:FATA] RAX=10c7e8f10, RBX=7000004ef000, RCX=5ef000005f000, RDX=5f0000005f000, RSI=5ef00, RDI=1011837b0, RBP=7000004eedb0, RSP=7000004eed90,
2018-06-03 02:18:16.654 [7000004ef000:FATA] R8=1011837d0, R9=ffffffff00000000, R10=1011837c8, R11=1011837d0, R12=100f6dd30, R13=0, R14=7000004ef000, R15=0,
2018-06-03 02:18:16.654 [7000004ef000:FATA] 0 xdag 0x0000000100fa169d sigCatch + 2589
2018-06-03 02:18:16.655 [7000004ef000:FATA] 1 libsystem_platform.dylib 0x00007fff66b85f5a _sigtramp + 26
2018-06-03 02:18:16.655 [7000004ef000:FATA] 2 libsystem_c.dylib 0x00007fff9eb58268 usual_extra + 8
2018-06-03 02:18:16.655 [7000004ef000:FATA] 3 xdag 0x0000000100f6e501 work_thread + 2001
2018-06-03 02:18:16.656 [7000004ef000:FATA] 4 libsystem_pthread.dylib 0x00007fff66b8f661 _pthread_body + 340
2018-06-03 02:18:16.656 [7000004ef000:FATA] 5 libsystem_pthread.dylib 0x00007fff66b8f50d _pthread_body + 0
2018-06-03 02:18:16.656 [7000004ef000:FATA] 6 libsystem_pthread.dylib 0x00007fff66b8ebf9 thread_start + 13
2018-06-03 02:18:26.788 [7fff9eb76380:MESS] Initializing log system...
2018-06-03 02:18:26.789 [7fff9eb76380:MESS] Reading hosts database...
2018-06-03 02:18:26.790 [7fff9eb76380:MESS] Initializing cryptography...

What's happening to XDAG from 7/5/2018？

XDAG is in great discussion these days, but no one could explain exactly what happened.
We are eager to know what caused this accident.
XDAG community, tell something, please.

How auto transfer XDAG

Transfers XDAG to other wallet address，./xdag -i then xfer S A，
that's the only to do it.？Is it possible to not enter xdag>?

adjust pool % fee/reward in command line

Shall we built it into xdag command so instead of kill process and restart daemon to adjust pool parameters, it can be changed within xdag -i

Always use executable directory, not current directory

xdag wallet uses current directory when tries to open wallet.dat, dnet_key.dat and storage folder. It can confuse users if xdag wallet is started not from current directory.

See example:

In the first case wallet is started from current directory and in the second case wallet is started not from current directory. As you can see in that case wallet offers to create a new account.

[MacOSX] wallet doesn't work after first start

wallet works fine the first time it is initialized.
after you close it and reopen, it doesn't work anymore.

https://cdn.discordapp.com/attachments/440844768763838465/440911808245661717/Screen_Shot_2018-05-02_at_12.25.48_AM.png
https://cdn.discordapp.com/attachments/440844768763838465/440899678842781716/Screen_Shot_2018-05-01_at_11.37.24_PM.png

it keep to tell "Type command, help for example." every 12secs
and it seems that doesn't connect.

"Wait sync blocks" value more than 0

Several pool owners stated that "wait sync blocks" value is more than zero, but pool is sychronized.

help！need more pool

More pool adding nodes are needed to achieve faster synchronization efficiency. I want to build more pool nodes in Asia, and how to join the white list.

some time a lot of miners disconnect from the pool , because of socket hangup

some time a lot of miners disconnect from the pool , because of socket hangup
and they can not reconnect in a short time. when restart daggerGPUminer it cant not connect too.

hanging with account command

With test pool, when try to connect to testnet type account command, it will hangup there.

mac connection to website fails

Mac connection to website https fail, httpse OK

cann't pass compile /xdag/client

to compile client in Ubuntu 4.13 gcc 4.8.5

Error INFO As Below:
pool.c:929:21: error: dereferencing pointer to incomplete type ‘struct hostent’
if (!host || !host->h_addr_list[0]) {
^
pool.c:933:10: error: ‘h_errno’ undeclared (first use in this function)
res = h_errno;
^
pool.c:933:10: note: each undeclared identifier is reported only once for each function it appears in
sha256.c: In function ‘sha256_final’:
sha256.c:140:3: warning: implicit declaration of function ‘memset’ [-Wimplicit-function-declaration]
memset(cdata, 0, 56);
^
sha256.c:140:3: warning: incompatible implicit declaration of built-in function ‘memset’
sha256.c:140:3: note: include ‘<string.h>’ or provide a declaration of ‘memset’
../dnet/dnet_threads.c: In function ‘dnet_thread_work’:
../dnet/dnet_threads.c:77:10: warning: implicit declaration of function ‘gethostbyname’ [-Wimplicit-function-declaration]
host = gethostbyname(str);
^
../dnet/dnet_threads.c:77:8: warning: assignment makes pointer from integer without a cast [-Wint-conversion]
host = gethostbyname(str);
^
../dnet/dnet_threads.c:78:21: error: dereferencing pointer to incomplete type ‘struct hostent’
if (!host || !host->h_addr_list[0]) {
^
../dnet/dnet_threads.c:79:54: error: ‘h_errno’ undeclared (first use in this function)
mess = "cannot resolve host ", mess1 = str; res = h_errno;
^
../dnet/dnet_threads.c:79:54: note: each undeclared identifier is reported only once for each function it appears in
Makefile:97: recipe for target 'xdag' failed
make: *** [xdag] Error 1

base58 address

Mission:
Use base58 address instead of base64 address for new generated wallet and transactions.

Description:
Currently the wallet and block address use base64 which is not friendly to users and web browsers, while base58 is much more friendly.

If you would like to take this task, please reply with your proposal and ask dev team to review.

Connect to a node automatically

To connect with the wallet, the user shouldn't need to enter a pool manually to connect.
I think the program should check all the available pools/nodes and connect to the one available with less ping or something.

Cannot connect the main network.

Hi, I want to start my own pool.

When I followed the tutorial of the https://github.com/XDagger/openxdagpool-scripts, it can not connect the main network.

Here is the start command:
pool@ip-172-31-34-249:~/xdag1/client$ TZ=GMT ./xdag -d -p 54.164.118.71:16775 -P 54.164.118.71:13654:20000:2000:450:1:1:1:1

Here is the state prompt:

xdag> state
Trying to connect to the main network.

Here is the stats prompt:

xdag> stats
Statistics for ours and maximum known parameters:
            hosts: 34 of 34
           blocks: 7 of 7
      main blocks: 5 of 5
    orphan blocks: 1
 wait sync blocks: 0
 chain difficulty: 000000057d75e6383 of 000000057d75e6383
      XDAG supply: 5120.000000000 of 5120.000000000
4 hr hashrate MHs: 0.00 of 0.00

Connection state:

xdag> net conn
Current connections:
xdag> net hosts
Active hosts:
  0. 6274700E                   0 sec, T13.714, local     trust  127.0.0.1:0
xdag> net host
6274700E                   0 sec, T13.714, trust

Could you tell me is there any configuration problem for my code?

Thanks for your time.

Potential buffer overflows in dnet_command()

dnet/dnet_command.c

int dnet_command(const char *in, struct dnet_output *out) {
    char *cmd, *lasts, inbuf[DNET_COMMAND_MAX]; // 0x1000 = 4096
    struct dnet_host *host;
	FILE *f;
	int len;
	strcpy(inbuf, in); // here
	cmd = inbuf;
begin:
	while (*cmd && isspace(*cmd)) ++cmd; // here

It looks like there are two places where a command > 4096 bytes could overflow in two different places, causing memory corruption and trivially exploiting the code.

The length of the command needs to be explicitly checked before operating on the data in any way. 'len' appears to be checked after the copies and increment the pointer, when it should be checked beforehand.

These types of vulnerabilities could affect the security of the system which is running the code.

tx fees to mining rewards

please add 0.01 tx fees to transactions, to be given to mining rewards. this will stabalise the network hugely.

Pool availability/actual payout monitoring - openxdagpool

New features proposed for openxdagpool:

add a round robin query (on whitelist) to find out which pools are available, and list on website.

And performance of actual mining result, to accompany the proclaimed arguments

full audit of the discord moderation group

As pool support for https://xdag.signal2noi.se

why have i been removed from the chat??
I would advise a full audit of the discord moderation group.

thank you for your time.

Rus

Remove mining from wallet

Is not necessary anymore, since we already have a cpu/gpu miner.

xdag-cli last command

Hi,

it would be convenient if we could bring last commands on arrow up, same like in bash:

xdag> account
[address]          0.000000000  key 0
xdag> ^[[A
Illegal command.

using xdag on OSX. Thank you

linux build issues

GPU's show correct hash-rate in terminal, but pools only seeing a small percentage of hash-rate and rewards not paying correctly, tested on multiple pools over the course of many hours (8 hrs overnight)

Potential stack-based buffer overflow in XDagCore

I didn't see a place to create issues at https://github.com/xrdavies/DaggerGpuMiner, so I hope this is ok place to track them until that is fixed.

XDagCore/XNetwork.cpp

bool XNetwork::ValidateAddress(const char *address, sockaddr_in &peerAddr)
{
    char *lasts;
    char buf[0x100]; // 256

    // Fill in the address of server
    memset(&peerAddr, 0, sizeof(peerAddr));
    peerAddr.sin_family = AF_INET;

    // Resolve the server address (convert from symbolic name to IP number)
    strcpy(buf, address); // here

address is copied into buf without checking if the server address is < 256 bytes and there were no other limits seen on a server address's size.

This can be easily fixed by just checking if address < buf before doing the copy.

Also, in CLminer.cpp there is an issue:

void AddDefinition(std::string& source, char const* id, unsigned value)
{
     char buf[256];
     sprintf(buf, "#define %s %uu\n", id, value);
     source.insert(source.begin(), buf, buf + strlen(buf));
}

If id is not guaranteed to be < 256 bytes, a buffer overflow will occur.

You can fix this by using snprintf() instead of sprintf() and specifying the max size to be sizeof(buf).

These vulnerabilities could allow someone to compromise the process and affect the security of the user running the app.

miner tag

Add tag for miners to display them in pool miner-list

Deadlock while sending several transactions

Deadlock:
block.c, function xdag_set_balance, line:
pthread_mutex_lock(&block_mutex);

block.c, function work_thread, line:
pthread_mutex_lock(&block_mutex);

xdag can't run on centos

➜ client git:(develop) ✗ ./xdag -m 2 -d 172.105.216.53:3355
xdag client/server, version 0.2.0.Transport module: dnet T11.231-T13.714, running as daemon.
Password:
➜ client git:(develop) ✗ ./xdag -i
xdag client/server, version 0.2.0.
xdag> help
Can't connect to unix domain socket errno:2
xdag>

long parameter support

Add long parameter support.

json-rpc

json-rpc

Xdagwallet86 is not valid on win32 error

Xdagwallet86 is not valid on win32 error

xdag was MIT licensed, is now GPL licensed; action needed

Commit 1a88c7c has merged in support for Readline.

This project is MIT licensed. However, Readline is GPL. Binaries built with this software, and distribution of this software in source or binary form, must comply with the GPL license. This is more restrictive than the MIT license. Because of these restrictoins, this commit should be immediately reverted.

Any unrelated fixes should be recommited per task without being merged into a single commit.

An alternate method for command history or completion should be devised.

xdag> Trying to connect to the main network.

Followed instructions to open the pool, but:

root@vultr:/var/www/pool# cat state.txt 
xdag client/server, version 0.2.1.
xdag> Trying to connect to the main network.

root@vultr:/var/www/pool# ps aux | grep xdag
pool     13236  0.0  0.0  23552   860 ?        Ss   09:52   0:00 ./xdag -d -p 45.77.39.193:16775 -P 45.77.39.193:13654:20000:0.5:1:1:200:0.5
pool     13238  7.6  0.9 31539672 9140 ?       Sl   09:52   1:16 ./xdag -d -p 45.77.39.193:16775 -P 45.77.39.193:13654:20000:0.5:1:1:200:0.5

Any hint? or how to debug? Other txt logs are all correct, can sync transactions.

how do my pool IP update to whitelist?

I'm start xdag daemon:
./xdag -d -r -p 47.75.1.95:16775 -P 47.75.1.95:12315:2048:0.5:1:1:200:1
thanks!

The balance in wallet is cleared to 0.010631004 XDAG when my PC is powered off accidentally and powered it back

My question: How can I repair my wallet? Thanks.

pool configuration has no effect.

Reported from pools guy, the pool cannot change the configuration

potential issues on Mac OSX

dnet fork
==11195==ThreadSanitizer: starting new threads after multi-threaded fork is not supported. Dying (set die_after_fork=0 to override)

Reduce invalid transactions caused by network asynchrony.

At present, when the network is out of sync, each mineral pool will produce a block in 64 seconds, and each mining pool will distribute thousands of trading dividends separately, which will seriously affect the synchronization of the network.Add a maturity, only when the main block is recognized 1000 main blocks, can transfer the dividend.

Can not connect to the main network.

ubuntu 16.04.
run ./xdag with -d -p and -P parameters.
It always "Trying to connect to the main network".

Mac wallet re-generate address

here's what happened... step by step.. hopng @Frozen might have a look at this

1. i had mac wallet open and mining for a day or so.
2. i had been sending coins to mac wallet from windows GUI
3. mac wallet received coins ok
4. i did a test send from mac to windows gui
5. windows gui received coins ok from mac wallet
6. tonight. tried to send a freind some XDAG
7. wallet stuck
8. restarted wallet
9. wallet had old password (good) but new address (bad)
10. account 5 - only one address showed
11. raskul tears hair out
12. restart mac
13. restatrt mac wallet
14. account 5
    15.mac wallet has 2 addresses (!)
15. the old wallet recovers
16. plus some random new wallet address witj 0XDAG
17. sent coins to windows gui
    http://explorer.xdag.io/block/WbgINR6V4fLmSQxkixfkLY57NcreYlm4?addr_page=3
    coins safe
    still. panicked

How can I update whitelist, if I want to add a xdag miner pool?

dnet create failed cause restart

dnet create failed cause restart

2018-06-03 02:00:33.442 [70000b4d0000:INFO] MAIN : 64cc1b93cb918f0761b189094c35f24f84667f7f3fc1ecc3993cf54807d063a5 t=16c4b6bffff pos=200
2018-06-03 02:00:34.191 [70000b5d6000:INFO] Mining: start from beginning because of pre-top block changed
2018-06-03 02:00:34.192 [70000b5d6000:INFO] Mintop: 6ce6444e52b614630fee829f33dc327520345afae8818e2391737d1631b6dab2 t=16c4b6cffff pos=200
2018-06-03 02:00:40.549 [7fff9eb76380:FATA] Signal 11 delivered
2018-06-03 02:00:40.550 [7fff9eb76380:FATA] RIP=7fff66b90126, EFL=10202, ERR=0, CR2=0,
2018-06-03 02:00:40.550 [7fff9eb76380:FATA] RAX=2e2f67756265442f, RBX=70000b96b000, RCX=203, RDX=1, RSI=7ff520819200, RDI=70000b96b000, RBP=7ffee834fa20, RSP=7ffee834fa00,
2018-06-03 02:00:40.551 [7fff9eb76380:FATA] R8=80008ff, R9=107adc230, R10=0, R11=246, R12=0, R13=0, R14=3, R15=7fff9eb76358,
2018-06-03 02:00:40.553 [7fff9eb76380:FATA] 0 xdag 0x00000001078e369d sigCatch + 2589
2018-06-03 02:00:40.554 [7fff9eb76380:FATA] 1 libsystem_platform.dylib 0x00007fff66b85f5a _sigtramp + 26
2018-06-03 02:00:40.554 [7fff9eb76380:FATA] 2 ??? 0x0000000000000000 0x0 + 0
2018-06-03 02:00:40.554 [7fff9eb76380:FATA] 3 xdag 0x00000001078bfbcf dnet_thread_create + 415
2018-06-03 02:00:40.555 [7fff9eb76380:FATA] 4 xdag 0x00000001078c5b9b dnet_command + 939
2018-06-03 02:00:40.555 [7fff9eb76380:FATA] 5 xdag 0x00000001078c6311 dnet_execute_command + 65
2018-06-03 02:00:40.556 [7fff9eb76380:FATA] 6 xdag 0x00000001078d92dd xdag_net_command + 29
2018-06-03 02:00:40.556 [7fff9eb76380:FATA] 7 xdag 0x00000001078e0326 processNetCommand + 182
2018-06-03 02:00:40.557 [7fff9eb76380:FATA] 8 xdag 0x00000001078df9cd xdag_com_net + 29
2018-06-03 02:00:40.557 [7fff9eb76380:FATA] 9 xdag 0x00000001078e0cf9 xdag_command + 313
2018-06-03 02:00:40.557 [7fff9eb76380:FATA] 10 xdag 0x00000001078e0a3f startCommandProcessing + 175
2018-06-03 02:00:40.558 [7fff9eb76380:FATA] 11 xdag 0x00000001078ca3b9 xdag_init + 5849
2018-06-03 02:00:40.558 [7fff9eb76380:FATA] 12 xdag 0x00000001078e22c4 main + 36
2018-06-03 02:00:40.559 [7fff9eb76380:FATA] 13 libdyld.dylib 0x00007fff66877015 start + 1
2018-06-03 02:00:40.559 [7fff9eb76380:FATA] 14 ??? 0x000000000000000a 0x0 + 10
2018-06-03 02:00:50.565 [7fff9eb76380:MESS] Initializing log system...
2018-06-03 02:00:50.566 [7fff9eb76380:MESS] Reading hosts database...

Mac OS ：Can't connect to unix domain socket errno:2

share verification

share verification

Dagger info paper

Hi guys,

I am preparing XDAG info paper, so I can spread this information. Please peer review it, let me know what should be changed/added/deleted. After we can put it here as WIKI page and post it to community, so all useful info will be on one place.

Thanks

https://docs.google.com/document/d/1b8OmK4RPGtMkh4qQyaLYVQM-Lfym1gKqR1Hq3Rrf7oM/edit?usp=sharing