Can you update the github with the new code? Thanks! The great thing about virtual currencies is we can always change the code back if it is not working. View it as a test run. Our large shareholders have been claiming that miners are dumping nonstop to keep the price down and lock in quick profits so we are going to test what happens after the fork. Can you upload the source properly? It just a ZIP file. and not only that, it DOES NOT COMPILE. Can you at least address that? |
|
|
|
right guys, we almost out of 0.01 just like i told you all for the past week. Multipool drk dumps will happen for next two days. We are going into 0.009 or lower, please do not panic this is only temporary but will happen, until code is reviewed which will be sometime next week.  Or counter the other multipool dumps by mining with the DRK multipool, we'll buy up the dumpers, but need more mining support! www.xpool.caCheers! |
|
|
|
BitcoinDark by xpool - The Official BTCD Multipool PROP reward system BTCD Payouts Scrypt & SHA256 & X11 Algo's DDoS Protected High Performance Backend Simple setup and usage 1% Fee To mine: How does it work?
xpool offers 3 different sets of coins to mine. SHA256, Scrypt and X11. Each algorithm runs on a shift (see below). The confirmed coins are traded throughout the duration of the shift automatically to maximize the profits from exchanging them into BTCD. Once the shift ends, the shift is moved into "Confirming" status while all the coins are confirmed as successfully traded and exchanged, the BTCD payments are sent.
Current shifts run 24 hours, Monday - Friday and end at 7PM Eastern each day except Saturday & Sunday. The weekend shift ends on the Monday. Payments are then finialized and typically complete 2-3 hours after a shift ends.
The advantage of the pool is that you can utilize your any GPU, CPU and older ASIC equipment to earn you the more desired BitcoinDark. Cheers and Happy Hashing!
Donations welcome or tip me, crackers, on IRC!
Any issues, please report them here or feel free to PM me, as I can't always see every post.
|
|
|
|
Can you update the github with the new code? Thanks! The great thing about virtual currencies is we can always change the code back if it is not working. View it as a test run. Our large shareholders have been claiming that miners are dumping nonstop to keep the price down and lock in quick profits so we are going to test what happens after the fork. Can you upload the source properly? It just a ZIP file. |
|
|
|
BitcoinDark by xpool - The Official BTCD Multipool PROP reward system BTCD Payouts Scrypt & SHA256 & X11 Algo's DDoS Protected High Performance Backend Simple setup and usage 1% Fee To mine: How does it work?
xpool offers 3 different sets of coins to mine. SHA256, Scrypt and X11. Each algorithm runs on a shift (see below). The confirmed coins are traded throughout the duration of the shift automatically to maximize the profits from exchanging them into BTCD. Once the shift ends, the shift is moved into "Confirming" status while all the coins are confirmed as successfully traded and exchanged, the BTCD payments are sent.
Current shifts run 24 hours, Monday - Friday and end at 7PM Eastern each day except Saturday & Sunday. The weekend shift ends on the Monday. Payments are then finialized and typically complete 2-3 hours after a shift ends.
The advantage of the pool is that you can utilize your any GPU, CPU and older ASIC equipment to earn you the more desired BitcoinDark. Cheers and Happy Hashing!
Donations welcome or tip me, crackers, on IRC!
Any issues, please report them here or feel free to PM me, as I can't always see every post.
Today's shift payments have finished. Over 299 BTCD sent out to miners on all 3 algos! Cheers! |
|
|
|
LOOKS LIKE BITCOINDARK MULTIPOOL IS NOW btcd.xpool.ca
Both addresses will work. Just changed it to be btcd centric and not "dark". Cheers! Awesome. Hey some people have been wondering about the payouts? It seems they haven't been getting them. They have been. They are just impatient.  |
|
|
|
LOOKS LIKE BITCOINDARK MULTIPOOL IS NOW btcd.xpool.ca
Both addresses will work. Just changed it to be btcd centric and not "dark". Cheers! |
|
|
|
This rise in price is no normal growth, it's doomed to be dumped again.
So we have basically no new supply. Less than 1.2 million, not sure we will even get past that by year end. We have multipools that are buying and I would say they buy a bit more than 200 BTCD So if you are familiar with supply/demand economics, this creates an upward pressure to the prices. has been buying 300-400 a day and I expect that to continue to grow. Cheers! |
|
|
|
ahh ok... here is where my windows client is stuck:
{
"blocks" : 854308,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 0.00686077,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 1560466,
"pooledtx" : 0,
"testnet" : false
}
Is that with the new code or your original wallet? You might try this: The clients (most) have two 'ways' to connect - one is addnode=, the other is connect= . The windows client "might" benefit from using connect= in your xencoin.conf and triptech's IP for now -- that tells the client to connect directly to another node and ignore peers and seeds -- maybe it will help you get up to speed on connections - once the chain is down, you should be able to remove it and restart - I would think it would stay synced then. The issue is the lack of checkpoints in the chain on the old clients -- so they continually get stuck... EDIT: My xenseed only shows two other clients besides mine running on port 4334 (default) for XNC - there should be a few more with the exchanges but they are not showing up - and I'm willing to bet that the three are you, me, and tt. That was just the orig windows QT. My linux binary, just crashed: xencoind: /usr/include/boost/thread/pthread/recursive_mutex.hpp:92: boost::recursive_mutex::~recursive_mutex(): Assertion `!pthread_mutex_destroy(&m)' failed. |
|
|
|
BitcoinDark by xpool - The Official BTCD Multipool PROP reward system BTCD Payouts Scrypt & SHA256 & X11 Algo's DDoS Protected High Performance Backend Simple setup and usage 1% Fee To mine: How does it work?
xpool offers 3 different sets of coins to mine. SHA256, Scrypt and X11. Each algorithm runs on a shift (see below). The confirmed coins are traded throughout the duration of the shift automatically to maximize the profits from exchanging them into BTCD. Once the shift ends, the shift is moved into "Confirming" status while all the coins are confirmed as successfully traded and exchanged, the BTCD payments are sent.
Current shifts run 24 hours, Monday - Friday and end at 7PM Eastern each day except Saturday & Sunday. The weekend shift ends on the Monday. Payments are then finialized and typically complete 2-3 hours after a shift ends.
The advantage of the pool is that you can utilize your any GPU, CPU and older ASIC equipment to earn you the more desired BitcoinDark. Cheers and Happy Hashing!
Donations welcome or tip me, crackers, on IRC!
Any issues, please report them here or feel free to PM me, as I can't always see every post.
|
|
|
|
Xencoin Community Fork - Repo updated - checkpoints added - version data changed - https://github.com/thecarnie/xencoin (TESTING - UNSTABLE) xencoin-seeder - Repo updated - initial seed changed for now - version data changed - https://github.com/thecarnie/xencoin-seederThe XNC repo has my temporary xenseed node coded in - it should start downloading a blockchain right away without help from nodes in the xencoin.conf file... Be sure to remove them and delete your peers.dat file to test if it is connecting and finding nodes as expected. Still monitoring for a 10k orphan block exception during re-download. The chain is probably about 1/2 orphans mixed in from the bad diff algo and multi-pools. Will know more in the morning -- Building now. I'll add the coin to www.hasher.ca again for people to test with. Finished, deleted blk* peers database etc... however, not connecting up: 2014-07-21 12:32:39 send version message: version 70002, blocks=0, us=192.99.35.133:1542, them=98.93.92.131:4334, peer=98.93.92.131:4334 2014-07-21 12:32:39 socket recv error 104 2014-07-21 12:32:39 disconnecting node 98.93.92.131:4334 2014-07-21 12:32:42 trying connection 98.93.92.131:4334 lastseen=73.3hrs 2014-07-21 12:32:42 connected 98.93.92.131:4334 2014-07-21 12:32:42 send version message: version 70002, blocks=0, us=192.99.35.133:1542, them=98.93.92.131:4334, peer=98.93.92.131:4334 2014-07-21 12:32:42 socket closed 2014-07-21 12:32:42 disconnecting node 98.93.92.131:4334 2014-07-21 12:32:44 trying connection 98.93.92.131:4334 lastseen=73.3hrs $ xencoind getinfo { "version" : 80703, "protocolversion" : 70002, "walletversion" : 60000, "balance" : 0.00000000, "blocks" : 0, "timeoffset" : 0, "connections" : 0, "proxy" : "", "difficulty" : 0.00024414, "testnet" : false, "keypoololdest" : 1405451347, "keypoolsize" : 101, "paytxfee" : 0.00000000, "mininput" : 0.00001000, "errors" : "" } THANKS! That test alone shows several changes have worked. That IP you're seeing is my DDNS to my node working via the xenseed daemon running on my DL140 over here. Basically, the source last night has xenseed updated to host our own primary seeder, and I DDNSed my dev servers for now to keep the seeder going because I don't have any linux VMs facing the public at the moment. The multiple connects to that IP basically show that I'm not down re-downloading the blockchain yet, so I'm not sharing blocks it seems. I'm currently at about 675k since restarting last night. The checkpoints seem to have resolved the orphan mapping exhaustion issue I had yesterday, so progress. You might just shut the daemon down for a little bit on that one -- I'll ping a message up when I have the whole chain down and we can re-test to see if you start syncing up - Thanks again man! Ok great. What block should we actually be on, for the correct chain? I started up my windows wallet and it sync'd up to 830k+ We're up to just under 900k blocks (I'm showing two nodes with 899k (mine which is still pulling) and triptech's. I'm currently at 700k blocks so I think within the next hour or so it will be servicing other nodes ahh ok... here is where my windows client is stuck: { "blocks" : 854308, "currentblocksize" : 0, "currentblocktx" : 0, "difficulty" : 0.00686077, "errors" : "", "generate" : false, "genproclimit" : -1, "hashespersec" : 0, "networkhashps" : 1560466, "pooledtx" : 0, "testnet" : false } |
|
|
|
Less than 48 hours with a miner hosted on zenminer, and I haven't been able to log in for the last seven hours. Just great.  cloud hosting? |
|
|
|
Come get your DRS!  http://www.hasher.caPROP reward system Worker Stats DDoS Protected High Performance Backend Simple setup and usage To mine: Username: your DRS wallet address Password: anything DRS (vardiff): stratum+tcp://stratum.hasher.ca:3554 DRS go straight to your wallet once the block is confirmed. We don't hold your DRS! Cheers and Happy Hashing! |
|
|
|
Is it possible to transfer the old posts to here?
We are considering that. We may take a look at the old thread and bring the most relevant and helpful posts back. Just link back to the old thread. |
|
|
|
Xencoin Community Fork - Repo updated - checkpoints added - version data changed - https://github.com/thecarnie/xencoin (TESTING - UNSTABLE) xencoin-seeder - Repo updated - initial seed changed for now - version data changed - https://github.com/thecarnie/xencoin-seederThe XNC repo has my temporary xenseed node coded in - it should start downloading a blockchain right away without help from nodes in the xencoin.conf file... Be sure to remove them and delete your peers.dat file to test if it is connecting and finding nodes as expected. Still monitoring for a 10k orphan block exception during re-download. The chain is probably about 1/2 orphans mixed in from the bad diff algo and multi-pools. Will know more in the morning -- Building now. I'll add the coin to www.hasher.ca again for people to test with. Finished, deleted blk* peers database etc... however, not connecting up: 2014-07-21 12:32:39 send version message: version 70002, blocks=0, us=192.99.35.133:1542, them=98.93.92.131:4334, peer=98.93.92.131:4334 2014-07-21 12:32:39 socket recv error 104 2014-07-21 12:32:39 disconnecting node 98.93.92.131:4334 2014-07-21 12:32:42 trying connection 98.93.92.131:4334 lastseen=73.3hrs 2014-07-21 12:32:42 connected 98.93.92.131:4334 2014-07-21 12:32:42 send version message: version 70002, blocks=0, us=192.99.35.133:1542, them=98.93.92.131:4334, peer=98.93.92.131:4334 2014-07-21 12:32:42 socket closed 2014-07-21 12:32:42 disconnecting node 98.93.92.131:4334 2014-07-21 12:32:44 trying connection 98.93.92.131:4334 lastseen=73.3hrs $ xencoind getinfo { "version" : 80703, "protocolversion" : 70002, "walletversion" : 60000, "balance" : 0.00000000, "blocks" : 0, "timeoffset" : 0, "connections" : 0, "proxy" : "", "difficulty" : 0.00024414, "testnet" : false, "keypoololdest" : 1405451347, "keypoolsize" : 101, "paytxfee" : 0.00000000, "mininput" : 0.00001000, "errors" : "" } THANKS! That test alone shows several changes have worked. That IP you're seeing is my DDNS to my node working via the xenseed daemon running on my DL140 over here. Basically, the source last night has xenseed updated to host our own primary seeder, and I DDNSed my dev servers for now to keep the seeder going because I don't have any linux VMs facing the public at the moment. The multiple connects to that IP basically show that I'm not down re-downloading the blockchain yet, so I'm not sharing blocks it seems. I'm currently at about 675k since restarting last night. The checkpoints seem to have resolved the orphan mapping exhaustion issue I had yesterday, so progress. You might just shut the daemon down for a little bit on that one -- I'll ping a message up when I have the whole chain down and we can re-test to see if you start syncing up - Thanks again man! Ok great. What block should we actually be on, for the correct chain? I started up my windows wallet and it sync'd up to 830k+ |
|
|
|
|
We've updated the stratum VARDIFF calculations to stick with x2 adjustments. Some of you have expressed that your miners behave a little weird with the more specific adjustments. So now you will notice your diff will be 2,4,8,16,32,64,128,256 etc....
Thanks!
|
|
|
|
Xencoin Community Fork - Repo updated - checkpoints added - version data changed - https://github.com/thecarnie/xencoin (TESTING - UNSTABLE) xencoin-seeder - Repo updated - initial seed changed for now - version data changed - https://github.com/thecarnie/xencoin-seederThe XNC repo has my temporary xenseed node coded in - it should start downloading a blockchain right away without help from nodes in the xencoin.conf file... Be sure to remove them and delete your peers.dat file to test if it is connecting and finding nodes as expected. Still monitoring for a 10k orphan block exception during re-download. The chain is probably about 1/2 orphans mixed in from the bad diff algo and multi-pools. Will know more in the morning -- Building now. I'll add the coin to www.hasher.ca again for people to test with. Finished, deleted blk* peers database etc... however, not connecting up: 2014-07-21 12:32:39 send version message: version 70002, blocks=0, us=192.99.35.133:1542, them=98.93.92.131:4334, peer=98.93.92.131:4334 2014-07-21 12:32:39 socket recv error 104 2014-07-21 12:32:39 disconnecting node 98.93.92.131:4334 2014-07-21 12:32:42 trying connection 98.93.92.131:4334 lastseen=73.3hrs 2014-07-21 12:32:42 connected 98.93.92.131:4334 2014-07-21 12:32:42 send version message: version 70002, blocks=0, us=192.99.35.133:1542, them=98.93.92.131:4334, peer=98.93.92.131:4334 2014-07-21 12:32:42 socket closed 2014-07-21 12:32:42 disconnecting node 98.93.92.131:4334 2014-07-21 12:32:44 trying connection 98.93.92.131:4334 lastseen=73.3hrs $ xencoind getinfo { "version" : 80703, "protocolversion" : 70002, "walletversion" : 60000, "balance" : 0.00000000, "blocks" : 0, "timeoffset" : 0, "connections" : 0, "proxy" : "", "difficulty" : 0.00024414, "testnet" : false, "keypoololdest" : 1405451347, "keypoolsize" : 101, "paytxfee" : 0.00000000, "mininput" : 0.00001000, "errors" : "" } |
|
|
|
Xencoin Community Fork - Repo updated - checkpoints added - version data changed - https://github.com/thecarnie/xencoin (TESTING - UNSTABLE) xencoin-seeder - Repo updated - initial seed changed for now - version data changed - https://github.com/thecarnie/xencoin-seederThe XNC repo has my temporary xenseed node coded in - it should start downloading a blockchain right away without help from nodes in the xencoin.conf file... Be sure to remove them and delete your peers.dat file to test if it is connecting and finding nodes as expected. Still monitoring for a 10k orphan block exception during re-download. The chain is probably about 1/2 orphans mixed in from the bad diff algo and multi-pools. Will know more in the morning -- Building now. I'll add the coin to www.hasher.ca again for people to test with. |
|
|
|
Block reward goes down to 100 coins block time to 60 seconds and re target time of 3 hours instead of 1000 coins, 30 seconds, 4 hours compiling bombs out for me... obj/txdb.o: In function `void CLevelDBBatch::Write<std::pair<char, uint256>, CCoins>(std::pair<char, uint256> const&, CCoins const&)': /home/crackers/src/FuelCoinCode/src/leveldb.h:42: undefined reference to `leveldb::WriteBatch::Put(leveldb::Slice const&, leveldb::Slice const&)' obj/txdb.o: In function `void CLevelDBBatch::Write<std::pair<char, int>, CBlockFileInfo>(std::pair<char, int> const&, CBlockFileInfo const&)': /home/crackers/src/FuelCoinCode/src/leveldb.h:42: undefined reference to `leveldb::WriteBatch::Put(leveldb::Slice const&, leveldb::Slice const&)' obj/txdb.o: In function `CLevelDBBatch': /home/crackers/src/FuelCoinCode/src/leveldb.h:23: undefined reference to `leveldb::WriteBatch::WriteBatch()' obj/txdb.o: In function `~CLevelDBBatch': /home/crackers/src/FuelCoinCode/src/leveldb.h:23: undefined reference to `leveldb::WriteBatch::~WriteBatch()' collect2: error: ld returned 1 exit status make: *** [FuelCoind] Error 1 |
|
|
|
|
Show Posts
