If I always use the same random words to generate keys, on whatever machine will I always get the same addresses?
Will we need to have port forwarding to open a port on our node in order to mine? This was not the case in testnet, so why should it be on the mainnet?
Topic: [ANN] [XDAG] New Community-based Cryptocurrency - First Mineable DAG ! - page 124. (Read 75448 times)
December 25, 2017, 05:20:00 AM
December 25, 2017, 05:13:29 AM
Proposed time for restart is
Fri, 05 Jan 2018 22:45:20 GMT (Unix time 0x5A500000)
Thanks dev, will we run into the same issue again? Will your nodes will be able to handle more than 20 connections each? Fri, 05 Jan 2018 22:45:20 GMT (Unix time 0x5A500000)
December 25, 2017, 05:07:27 AM
This looks very worth watching.
December 25, 2017, 04:57:22 AM
Proposed time for restart is
Fri, 05 Jan 2018 22:45:20 GMT (Unix time 0x5A500000)
Yes, we will always support you and look forward to it. Fri, 05 Jan 2018 22:45:20 GMT (Unix time 0x5A500000)
December 25, 2017, 04:45:51 AM
Nice coinname, this makes me feel hilarious. This coin aim is to cheat someone, right?
December 25, 2017, 04:34:32 AM
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.
Maybe write a more detailed instruction how to correctly set it up that.
December 25, 2017, 02:50:01 AM
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
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.
December 25, 2017, 02:40:37 AM
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
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
December 25, 2017, 02:10:38 AM
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 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
December 25, 2017, 01:17:44 AM
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.
December 25, 2017, 12:58:05 AM
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.
December 25, 2017, 12:56:28 AM
Obviously，there is premine, only 20 connections.
December 25, 2017, 12:45:21 AM
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.
December 25, 2017, 12:23:03 AM
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>
December 25, 2017, 12:21:05 AM
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:Try net connect 202.97.251.229:13655
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
December 24, 2017, 11:46:42 PM
I ran the daemon but it seems it can't connect to the main net? Is it online yet? 
December 24, 2017, 10:33:03 PM
- 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. - Block = transaction = address
- Mineable, no premine, no ICO
These look very exciting!
December 24, 2017, 10:29:31 PM
- Directed acyclic graph, not blockchain
- Block = transaction = address
- Mineable, no premine, no ICO
These look very exciting!
- Block = transaction = address
- Mineable, no premine, no ICO
These look very exciting!
December 24, 2017, 09:41:14 PM
Will the difficulty increase over time?
December 24, 2017, 09:36:09 PM
The client can not start normally, the launch failed?
Jump to: