[ANN] [XDAG] Community Driven - First Mineable DAG | CPU Mining

[DakotaFred]

cheatcoin> stats
Statistics for ours and maximum known parameters:
            hosts: 103 of 191
           blocks: 327 of 323956
      main blocks: 96 of 24039
    orphan blocks: 1
 wait sync blocks: 113
 chain difficulty: 242494abb20ad1b06e of 205715e03d7a51b2eac7
cheatcoins supply: 98304.000000000 of 24615936.000000000
hour hashrate MHs: 35.83 of 40.36


Is this normal or not?

My node is 138.68.84.85

Not. Numbers like 323956 arr not valid. They come from testnet. One node just connected from testnet to mainnet. These number were fixed.

Dev please post the output of your 'stats', 'net hosts', and 'net conn' output so we can all compare.

[MAFTRADER]

cheatcoin> stats
Statistics for ours and maximum known parameters:
            hosts: 103 of 191
           blocks: 327 of 323956
      main blocks: 96 of 24039
    orphan blocks: 1
 wait sync blocks: 113
 chain difficulty: 242494abb20ad1b06e of 205715e03d7a51b2eac7
cheatcoins supply: 98304.000000000 of 24615936.000000000
hour hashrate MHs: 35.83 of 40.36


Is this normal or not?

My node is 138.68.84.85

Not. Numbers like 323956 arr not valid. They come from testnet. One node just connected from testnet to mainnet. These number were fixed.

do i need to delete all dat file wait for your next update? or keep it ?

[progmax]

Node1:

cheatcoin> stats
Statistics for ours and maximum known parameters:
            hosts: 61 of 61
           blocks: 2681 of 2681
      main blocks: 39 of 39
    orphan blocks: 1
 wait sync blocks: 0
 chain difficulty: 1d92a2bcfd6f2391dc of 1d92a2bcfd6f2391dc
cheatcoins supply: 39936.000000000 of 39936.000000000
hour hashrate MHs: 3.98 of 13.97

Node 2:

cheatcoin> stats
Statistics for ours and maximum known parameters:
            hosts: 4 of 4
           blocks: 2687 of 2687
      main blocks: 45 of 45
    orphan blocks: 1
 wait sync blocks: 0
 chain difficulty: 1da041b4781e584333 of 1da041b4781e584333
cheatcoins supply: 46080.000000000 of 46080.000000000
hour hashrate MHs: 4.04 of 7.03
cheatcoin> net conn
Current connections:
  0. 52.5.32.68:13654          44 sec, 0/1024 in/out bytes, 0/0 packets, 0/0 dropped
cheatcoin> net hosts
Active hosts:
  0. 8084A685                   0 sec, T13.764, local     trust  127.0.0.1:0
cheatcoin>



Dev, what do you say? )

[marilouadrie]

What I fail to understand is why you called it Cheatcoin if it is protected by sha256

[xibeijan]

do i need to delete all dat file wait for your next update? or keep it ?

keep, we will come back.)

What is going on?  Was the launch a failure and you will try again later?  Or will it just continue?

[hisun]

The client can not start normally, the launch failed?

[sotisoti]

Will the difficulty increase over time?

[frankkkkkkk]

- Directed acyclic graph, not blockchain
- Block = transaction = address
- Mineable, no premine, no ICO

These look very exciting!

[frankkkkkkk]

- Directed acyclic graph, not blockchain
- Block = transaction = address
- Mineable, no premine, no ICO

These look very exciting!

How to mine it?I cant find any information on the website.

[Verethraghna]

I ran the daemon but it seems it can't connect to the main net? Is it online yet? 

[jonano]

Maybe you are only connected to yourself.
Try net connect 202.97.251.229:13655

I don't know. I didn't change anything, but in the morning I see more correct values:
cheatcoin> stats
Statistics for ours and maximum known parameters:
            hosts: 185 of 185
           blocks: 2850 of 2850
      main blocks: 421 of 421
    orphan blocks: 4
 wait sync blocks: 0
 chain difficulty: 7ba844795bddf77e4b of 7ba844795bddf77e4b
cheatcoins supply: 431104.000000000 of 24615936.000000000
hour hashrate MHs: 11.45 of 11.45

[sotisoti]

Code:

2017-12-25 04:19:57  dnet.2: starting connection with 202.97.251.229:13655.
2017-12-25 04:19:57  dnet.3: starting connection with 52.5.32.68:13654.
2017-12-25 04:19:57  dnet.4: starting connection with 199.16.31.96:3355.
2017-12-25 04:19:58  dnet.2: connection error (12), Connection reset by peer
2017-12-25 04:20:46  dnet.3: connection error (-6), Connection reset by peer
2017-12-25 04:21:04  dnet.6: starting connection with 199.16.31.96:3355.
2017-12-25 04:21:04  dnet.7: starting connection with 52.5.32.68:13654.
2017-12-25 04:21:04  dnet.5: starting connection with 202.97.251.229:13655.
2017-12-25 04:21:05  dnet.5: connection error (12), Connection reset by peer
2017-12-25 04:21:50  dnet.7: connection error (-6), Success
2017-12-25 04:22:08  dnet.4: cannot connect (-1), Connection timed out
2017-12-25 04:22:11  dnet.9: starting connection with 202.97.251.229:13655.
2017-12-25 04:22:11  dnet.10: starting connection with 199.16.31.96:3355.
2017-12-25 04:22:11  dnet.8: starting connection with 52.5.32.68:13654.
2017-12-25 04:22:12  dnet.9: connection error (12), Connection reset by peer

Code:

cheatcoin full node client/server, version T13.654-T13.764.
cheatcoin> stats
Statistics for ours and maximum known parameters:
            hosts: 3 of 3
           blocks: 96 of 96
      main blocks: 22 of 22
    orphan blocks: 4
 wait sync blocks: 0
 chain difficulty: 0ef25b39c5f7fc2d2 of 0ef25b39c5f7fc2d2
cheatcoins supply: 22528.000000000 of 22528.000000000
hour hashrate MHs: 1.16 of 1.16
cheatcoin> 

Any idea what's happening? I can telnet to the machine just fine

[sotisoti]

What is going on?  Was the launch a failure and you will try again later?  Or will it just continue?

We continue, but can't synchronize the whole main net because software supports now 20 connections per node as well. Software need to be rewritten in on-thread-for-all-connections manner and then try again to synchronize.

Ah, is that (max 20 connections) the reason why I can't connect to the node? What will happen to the coins that have been mined already?

[macsai]

Obviously，there is premine,  only 20 connections.

[xxnwxf]

What IP's are official dev ?  After doing a git pull and re-compiling the daemon I now have a cluttered up netdb.txt.  Please don't leave us hanging.

These are real ip's as I see.
52.5.32.68:13654
199.16.31.96:3355
202.97.251.229:13655
100.65.173.194:13659

I publish one more fix to git repo and mark these ip addresses as white. Limit of 20 connections do not applied to white addresses. This is emergency fix for first time. More fixes will be tomorrow.

I try to use the terminal in the windows system to ping these addresses, are unable to connect. How can I fix it?

[ruleben]

Ah, is that (max 20 connections) the reason why I can't connect to the node? What will happen to the coins that have been mined already?

The hard limit of 20 connections is set because my host is slow and can't support more thread simultaneously. And there are only few hosts with public ip. That's why almost no one can't connect to another. Already mined coins may be recalculated be the algorithm after the synchronization.

hi,dev 24096  main block there?

[xxnwxf]

It seems to be a fail start. I turned off my node.

My propositions:

1) write pool and miner
2) connections will be allowed only between public ip nodes
3) every public ip node can run a pool
4) every non public ip node can run a miner and connect to a pool
5) restart the system in January with zeroing all balances

I can not believe it, I lost something. But thank you for your positive attitude

[strayapple]

It seems to be a fail start. I turned off my node.

My propositions:

1) write pool and miner
2) connections will be allowed only between public ip nodes
3) every public ip node can run a pool
4) every non public ip node can run a miner and connect to a pool
5) restart the system in January with zeroing all balances

we will always support you

[dominguero]

It seems to be a fail start. I turned off my node.

My propositions:

1) write pool and miner
2) connections will be allowed only between public ip nodes
3) every public ip node can run a pool
4) every non public ip node can run a miner and connect to a pool
5) restart the system in January with zeroing all balances

Great, these decisions  have a lot of sense.

[Trademaxx]

so please tell us how he have to setup the portforwarding ip & Port to run a pool. What happens when Public ip changes? Maybe dyndns could help the ones with nonstatic ip.

Maybe write a more detailed instruction how to correctly set it up that.