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

[phieudu0502]

Nice coinname, this makes me feel hilarious. This coin aim is to cheat someone, right?

[hisun]

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.

[olegklymko]

This looks very worth watching.

[sotisoti]

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?

[bspus]

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?

[Sofar]

Okay , good thing to give a delay !! 

Project is interessting and we maybe need some more time to start all this thing.
Everybody is now aware of what we doing here, just need some more code to work well.

Can we hope that you cheatoshin0 join us on the Discord channel ?
I think some of us can really help with test or with idea.

Therefore, thx for the following and for your involved in it.
See ya soon 

[fayrez]

Thanks dev, will we run into the same issue again? Will your nodes will be able to handle more than 20 connections each?

I think that now it is not good time to substantially rewrite the full node. It is necessary to make the functionality of the pool in it and write a miner that could be compiled and run on any hardware. In the pool, work with the miners will be arranged another way. There will be one thread that will consistently bypass the miners, their number may be more than 20. If any of the miners are forgotten, then this is not terrible for the network, just this miner will go to another pool.

But if there are more pools than 20, this is another case. It should be noted that each pool has an open ip, so they do not have to connect directly to each other, but may be through intermediaries. Therefore, I think the number of connections to other pools can be limited to 20.

maybe limit pool to have active connections to 16-20 another pool for reasonably small time period. after that period some part of active connection canceled and reconnect to other pools. some kind of slow/delayed syncro with all pools in reasonably big time period. but one pool does not have too many active connection if overall pool count is big ?

[Zellko]

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

Thanks cheatoshin0 for your hard work. I think it's fair to restart the system the 5th Jan.

I will be there to try to mine the first coin 

[fayrez]

maybe limit pool to have active connections to 16-20 another pool for reasonably small time period. after that period some part of active connection canceled and reconnect to other pools. some kind of slow/delayed syncro with all pools in reasonably big time period. but one pool does not have too many active connection if overall pool count is big ?

I think that's a good idea. Maybe we should once every few minutes to randomly tear one of the connections giving others the opportunity to connect. It is difficult to imagine how much we can have pools on restart. On the first launch there was only 4 open ip addresses. I recently revised the log file dnet.log. It turned out that my node received more than 1000 connections at the time the network was launched. Maybe it was an attack, but their addresses were different and it seems they using our protocol. Of course, it was impossible to work. I think if we had about 20 pools and about 50 miners in each, it would be the best option to start.

if we have small connection limits. it should be able to detect cpu threads (it was already done) also with network adapters. so if somebody have high-eng rig or server it can be easier to config the load for them. also some options to LAN connection priorities against public network should be added (it has similarity to p2p networks from my point of view)

[kurniawanj]

once again you need to rebranding this coin

we dont like cheating 

[Verethraghna]

once again you need to rebranding this coin

we dont like cheating 

no need to rebrand the name is already good as it is... meaning of words changes as time goes by... take 'gay' for example... in the past it means cheerful but now it has a different connotation 

[thienytcc88]

After there are Bitcoin Gold, silver, platinum... then we have cheatcoin. It is so hilarious.

[sotisoti]

once again you need to rebranding this coin

we dont like cheating 

I think that the question of the name should be decided by the vote of the miners after the launch of the main network and an automatic voting system using a hashrate.

How about making a poll in bitcointalk?

[TAGTRAUM]

Yea, we need a trainer coin here for full throttle 

[MAFTRADER]

How about making a poll in bitcointalk?

I think someone can start such a vote to find out the most popular names. But users of this forum are not the shareholders of the currency. Therefore, I think the final decision should be decided by the miners because they support the existence of the currency by mining.

i have to agree on this. will see how it goes !

HUH A !

from my side

DAMI Coin

[rehydrogenated]

How about making a poll in bitcointalk?

I think someone can start such a vote to find out the most popular names. But users of this forum are not the shareholders of the currency. Therefore, I think the final decision should be decided by the miners because they support the existence of the currency by mining.

i have to agree on this. will see how it goes !

HUH A !

from my side

DAMI Coin

Wow big price moves up today! Any good news coming down the pipes?

[ruleben]

Wow big price moves up today! Any good news coming down the pipes?

The pool and the miner will be available for testing until the new year. Other features such as a password on the purse will be after the new year. Restarting on January 5th.

wait for you dev,good luck

[MAFTRADER]

Wow big price moves up today! Any good news coming down the pipes?

Where do you get such information of price moves? OMG

[hankrules]

is there a way to gets stats from the miner?

Code:

cheatcoin> stats
Illegal command.

[aironeous]

When I follow your install instructions I get some warnings, these:

---------------
main.c: In function ‘main’:
main.c:427:4: warning: ignoring return value of ‘fgets’, declared with attribute warn_unused_result [-Wunused-result]
    fgets(cmd, CHEATCOIN_COMMAND_MAX, stdin);
    ^
main.c: In function ‘terminal’:
main.c:267:3: warning: ignoring return value of ‘fgets’, declared with attribute warn_unused_result [-Wunused-result]
   fgets(cmd, CHEATCOIN_COMMAND_MAX, stdin);
   ^
main.c:274:3: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result [-Wunused-result]
   write(fd, cmd, strlen(cmd) + 1);
   ^
pool.c: In function ‘pool_net_thread’:
pool.c:362:18: warning: unused variable ‘host’ [-Wunused-variable]
  struct hostent *host;
                  ^
storage.c: In function ‘cheatcoin_load_sums’:
storage.c:196:11: warning: ignoring return value of ‘fread’, declared with attribute warn_unused_result [-Wunused-result]
  if (f) { fread(buf, sizeof(struct cheatcoin_storage_sum), 256, f); fclose(f); }
           ^
wallet.c: In function ‘cheatcoin_wallet_init’:
wallet.c:79:3: warning: ignoring return value of ‘fread’, declared with attribute warn_unused_result [-Wunused-result]
   fread(priv, sizeof(cheatcoin_hash_t), 1, f);
   ^
../dnet/dnet_crypt.c: In function ‘dnet_crypt_init’:
../dnet/dnet_crypt.c:173:4: warning: ignoring return value of ‘fgets’, declared with attribute warn_unused_result [-Wunused-result]
    fgets(buf, 256, stdin);
    ^
../dnet/dnet_main.c: In function ‘daemonize’:
../dnet/dnet_main.c:46:36: warning: ignoring return value of ‘dup’, declared with attribute warn_unused_result [-Wunused-result]
     i = open("/dev/null", O_RDWR); dup(i); dup(i); /* handle standard I/O */
                                    ^
../dnet/dnet_main.c:46:44: warning: ignoring return value of ‘dup’, declared with attribute warn_unused_result [-Wunused-result]
     i = open("/dev/null", O_RDWR); dup(i); dup(i); /* handle standard I/O */
--------------------------

Could this be caused by not having some of the suggested packages installed
These were the suggested packages when I installed git

----------
Suggested packages:
  git-daemon-run | git-daemon-sysvinit git-doc git-el git-email git-gui gitk gitweb git-arch git-cvs git-mediawiki git-svn
----------
Or can these warnings be ignored.

Thanks