nice ones  |
|
|
|
|
Hope it will be there soon, cryptsy is pretty stable now
|
|
|
|
|
What the heck going on with cryptsy, I placed sell orders with ASC and LK7, both are simply gone, no traces of the coins nor orders... never seen this in cryptsy!
|
|
|
|
|
98sNiCGjGK6L4ukoxTQvW99Mxx3SxFLqUW
thx
|
|
|
|
AltMiners GrainCoin PoolPPLNS - VarDiff - Stratum Only - 3% Pool FeesHi Folks, we just launched our new GrainCoin Pool using: PPLNS Reward System
Variable Difficulty
STRATUM Protocol
3% Pool FeesRegister Here: http://grain.altminers.comAnd Point your favorite mining software here: --scrypt -o stratum+tcp://grain.altminers.com:3336 -u [i]Weblogin.Worker[/i] -p [i]Worker password[/i] Happy Mining! Something seems to be wrong, pools been up for over an hour without finding a single block. I am using the pool now, everything seems fine. |
|
|
|
|
so many shitcoins recently: GLB, NXT, BSS,... people become very greedy now.
|
|
|
|
|
too many coins released recently, I think cryptsy takes no more coins
|
|
|
|
man, LTC what a miserable crash  Need to shutdown my rig, not even worth the electricity. |
|
|
|
another lifting from cryspay; lost 26500 from my wallet balance with this new client/blockchain; I've not mined since 14/08, why's that then? I have backups and starting to like my old blockchain and client actually  Nothing should be lost if you mined them, as only the last 2 days blocks regenerated and most are pos ones (only a few could be pow). You could try with the 1.5 client (we should caught up now with the old blockchain, so you don't need to use the new client with blacklist), and sync from the scratch. |
|
|
|
OK the blockchain is blocked for pow (the blocks created are only pos at this time), so we need to regenerate the last few pow blocks in order to make the coin function normally again. We don't know the reason why it is blocked, the same thing happened several times with other coins too, it looks like a rare bug somewhere in the pos code (since all happened to pos coins). We determined the last good pow block is around block 191569, so we regenerate the pow blocks starting there. The blockchain seems ok now. This is what you need to do to get onto the right blockchain and start to mine again: Download the rar file here (note this is a big file 206M because it includes the blockchain data - if your download speed is low, try to compile the client yourself then sync from scratch): https://mega.co.nz/#!doBjnBgb!JONo0kV4g3VFOPVsMkuiiHZPYbwB0urka2CLcC3_dPU unrar the file, there is a new qt exe for windows, and data files for the blockchain (under conf dir). If you are not using windows client, then you need to compile your own executable (windows you can compile yourself too). This is how you do it: - get all files from the github - add the following lines in main.cpp, at the beginning of CheckBlock function: // blacklist
if (GetHash() == uint256("0x00000002a2b7d72cb60264cdffd16b74237f442e67af9377cf45566c8b67315c"))
return error("CheckBlock() :191569 hash == 00000002a2b7d72cb60264cdffd16b74237f442e67af9377cf45566c8b67315c"); - compile the code blacklista the block 191569 and cause the blocks following it to be regenerated. This client is temporary. You don't need this client and blacklist code once the new blockchain catches up with the old one, which will take about a day, after it, you can use the old client without any problem. The only purpose of the new client is to not sync to the old blockchain. With the new client, you can just start and sync from scratch (delete everything in config dir EXCEPT your wallet and conf file, again don't delete the wallet.dat file). But the sync will takequite long, so you can use the downloaded blockchain data files (those under conf dir). Make a backup of your config dir, then copy the files in downloaded conf dir (databse dir, and blk0001.dat, blkindex.dat files) to your config dir, and overwrite the existing files. Also these addnodes: addnode=63.246.129.56 addnode=198.136.62.201 addnode=108.62.211.51 Now start the client, you should be in sync with the new blockchain and you should be able to mine. Because the existing blockchain is longer than the new blockchain, you may see the client say "xxx blocks remaining", as long as you are at block 191930 (current) or later, you should be able to start mining. |
|
|
|
All rejected at this moment, and i am pretty sure all the blocks are PoS and no PoW... Anyone can confirm this?
Confirm The blockchain is blocked on PoW, and I contacted dev, he asked me to help since he is at work now. I am working on it following his instructions and will give an update soon. |
|
|
|
You are throwing a shitfit over 10k DGC. An amount equal to 1.4 BTC. That is insignificant.
On my site's comments, you praised worldcoin, despite it having a 200k premine followed by an additional 200k instamine. Get over yourself.
I did not say WDC has no premine. Look at the charts: http://cryptometer.org/worldcoin_96_hour_charts.htmlat launch time, 6560 WDCs premined. Not the 200k as you said. |
|
|
|
Please tell me you did notice that the network hash dropped from 5.9 mhash during hour 1, to .48 mhash hour 2. I was there the minute DGC got launched, and there was no premine. There can be several reasons why the network hashrate dropped for an hour, if my memory serves me right i was getting a lot of orphan blocks during hour 2, because the blocks i found during hour 2 were still the same blocks as found during hour 1. The block generation got overrun in hour 1, because a LOT of people were mining it, and we paid for it in hour 2. After that, everything went back to normal. There is no premine, now shush lol, do you have the minimum knowledge of how the p2p coin works? If it has a lot of orphans because a lot people joined mining, you don't see the block rate drop, instead you will see block rate increase because of instamining and you will see the hashrate increase big time. You actually see this after hour 3. Have you ever heard a lot hashpower joined and the block rate actual declined? Go check the 96 hour curves for all other coins and find me one which behaved like this: http://cryptometer.orgAre you in your dream? What a joke, when people make up things. The facts are shown in the 96 hour charts: http://cryptometer.org/digitalcoin_96_hour_charts.htmland I put some comments for those innocent children to understand in the below diagram. BTW, more people here defending DGC does not change the facts. Facts are facts, it's simple.  |
|
|
|
Nice article on DGC. Well done. Lol, DGC no premine? No need to brag and everyone can see the DGC premine here in this 96-hour diagram: http://cryptometer.org/digitalcoin_96_hour_charts.htmlAlso I can hardly believe a famous scamcoin maker now becomes "unbias" alt coin commentator. Those who were in this forum 5-6 months ago know how many samecoins you made here, including a famous V-coin: https://bitcointalk.org/index.php?topic=221190.0and her companion S-coin already in cryptsy, why not make an effort to put her there too  Going through your articles in CryptoLife, a part from this one sounds pretty flattering, the rest seem pretty decent. Good job, Hazard! Are you still going on about a premine? Laughable. Dgc is widely regarded as amongst the fairest launched alt coins ever. Even you yourself said so here: https://bitcointalk.org/index.php?topic=264938.msg2836952#msg2836952As mentioned in that thread: First DGC Block (excluding genesis block of 50 DGC) was mined at 09:57:27 AM(UTC), about a minute and a half after the client was launched at 09:55:53 AM (UTC)Take a chill pill Phil. Excuse me? Are you blind? or you pretend to be blind? take a look again at the 96-hour curve, it is generated from the blockchain, and it does not lie: http://cryptometer.org/digitalcoin_96_hour_charts.html1st hour: 4099 blocks mined, or 9698 DGCs, with diff at 0 2nd hour: only 102 blocks mined, diff at virtually 0 too. 3rd hour and afterwards, normal blocks mined considering instamining at the beginning. What these mean? clearly, dev premined 1st hour (and some portion of 2nd hour), for something about 10000 DGCs, then he started to launch the coin in the forum etc, causing virtually no mining at hour 2, then from hour 3 and onwards, you see people joined and hashrate/diff increase, with clear instamining to about hour 6. The curves say all, everyone please look at the curves and judge yourselves. I have to say that 10000 DGCs premined by dev is not many, especially compared to some coins at that time such as CNC, FTC, etc, but don't tell me there's no premine. |
|
|
|
Nice article on DGC. Well done. Lol, DGC no premine? No need to brag and everyone can see the DGC premine here in this 96-hour diagram: http://cryptometer.org/digitalcoin_96_hour_charts.htmlAlso I can hardly believe a famous scamcoin maker now becomes "unbias" alt coin commentator. Those who were in this forum 5-6 months ago know how many samecoins you made here, including a famous V-coin: https://bitcointalk.org/index.php?topic=221190.0and her companion S-coin already in cryptsy, why not make an effort to put her there too Going through your articles in CryptoLife, a part from this one sounds pretty flattering, the rest seem pretty decent. Good job, Hazard! |
|
|
|
also, please check your blockchain with the block explorer http://starcoin.info/blockviewer/The block explorer is the "standard" one for blockchain, my wallets are all in sync with the block explorer. |
|
|
|
is not possible, a block 5 hours? Current Difficulty 0.10481759 Pool Hash Rate 17.111 MH/s For some reason all block candidates are being rejected by starcoind... I will try to check whats wrong.. We are founding ~15 blocks per minute! all rejected EDIT: ThreadRPCServer method=submitblock
ERROR: CheckProofOfWork() : nBits below minimum work
ERROR: CheckBlock() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED I will restart the daemon to see if that helps.. but this is not good. EDIT: Same thing.. all blocks get rejected.. Any dev wants to help? I can give more info if needed... I once saw these too, but I was on a forked chain by that time. Later when I sync with the right one, I don't see it again. The message says the block is rejected by the verification code, it could be generated artificially by some programs. |
|
|
|
Starcoin is running fine now since the update v1.5 (20/09/13) please reactivate it
BitJohn, can you reply the questions on STR? I keep hearing people from cryptsy saying STR did not implement the fix by CAP etc. You posted one message in the "Newbie" subforum for it, but you never communicated with the devs who apparently have no idea of what you are talking about. I replied you in "Newbie" thread and also in STR thread: https://bitcointalk.org/index.php?topic=259012.msg3264801#msg3264801But I did not hear from you, nor do I see any official update on STR since it was suspended by cryptsy. Can you provide info to STR devs and the miners community on what has happened and what is the plan of cryptsy? |
|
|
|
please check your blockchain against the block explorer. http://starcoin.info/blockviewer/I don't see forks, my 3 wallets all sync'd at block 154132 now (same from blockchain explorer), here are some of my peers: { "addr" : "188.252.16.109:18216", "services" : "00000001", "lastsend" : 1380507789, "lastrecv" : 1380507789, "conntime" : 1380507364, "version" : 60006, "subver" : "/Satoshi:0.7.2/", "inbound" : false, "releasetime" : 0, "startingheight" : 129451, "banscore" : 0 }, { "addr" : "216.158.85.123:18216", "services" : "00000001", "lastsend" : 1380507790, "lastrecv" : 1380507790, "conntime" : 1380507364, "version" : 60006, "subver" : "/Satoshi:0.7.2/", "inbound" : false, "releasetime" : 0, "startingheight" : 129451, "banscore" : 0 }, { "addr" : "63.246.129.56:18216", "services" : "00000001", "lastsend" : 1380507759, "lastrecv" : 1380507763, "conntime" : 1380507365, "version" : 60006, "subver" : "/Satoshi:0.7.2/", "inbound" : false, "releasetime" : 0, "startingheight" : 154123, "banscore" : 0 }, { "addr" : "192.241.182.189:18216", "services" : "00000001", "lastsend" : 1380507790, "lastrecv" : 1380507789, "conntime" : 1380507366, "version" : 60006, "subver" : "/Satoshi:0.7.2/", "inbound" : false, "releasetime" : 0, "startingheight" : 129451, "banscore" : 0 }, { "addr" : "37.229.117.57:18216", "services" : "00000001", "lastsend" : 1380507760, "lastrecv" : 1380507762, "conntime" : 1380507366, "version" : 60006, "subver" : "/Satoshi:0.7.2/", "inbound" : false, "releasetime" : 0, "startingheight" : 154123, "banscore" : 0 }, { "addr" : "212.119.171.18:18216", "services" : "00000001", "lastsend" : 1380507758, "lastrecv" : 1380507759, "conntime" : 1380507367, "version" : 60006, "subver" : "/Satoshi:0.7.2/", "inbound" : false, "releasetime" : 0, "startingheight" : 154123, "banscore" : 0 }, { "addr" : "95.95.106.58:51259", "services" : "00000001", "lastsend" : 1380507668, "lastrecv" : 1380507758, "conntime" : 1380507389, "version" : 60006, "subver" : "/Satoshi:0.7.2/", "inbound" : true, "releasetime" : 0, "startingheight" : 154124, "banscore" : 0 }, { "addr" : "205.173.255.101:47426", "services" : "00000001", "lastsend" : 1380507694, "lastrecv" : 1380507759, "conntime" : 1380507441, "version" : 60006, "subver" : "/Satoshi:0.7.2/", "inbound" : true, "releasetime" : 0, "startingheight" : 154126, "banscore" : 0 }, { "addr" : "173.247.188.146:32154", "services" : "00000001", "lastsend" : 1380507787, "lastrecv" : 1380507787, "conntime" : 1380507519, "version" : 60006, "subver" : "/Satoshi:0.7.2/", "inbound" : true, "releasetime" : 0, "startingheight" : 128960, "banscore" : 0 }, { "addr" : "86.11.74.139:18216", "services" : "00000001", "lastsend" : 1380507769, "lastrecv" : 1380507772, "conntime" : 1380507767, "version" : 60006, "subver" : "/Satoshi:0.7.2/", "inbound" : false, "releasetime" : 0, "startingheight" : 154133, "banscore" : 0 }, { "addr" : "64.120.17.150:59971", "services" : "00000001", "lastsend" : 1380507775, "lastrecv" : 1380507776, "conntime" : 1380507773, "version" : 60006, "subver" : "/Satoshi:0.7.2/", "inbound" : true, "releasetime" : 0, "startingheight" : 154133, "banscore" : 0 } |
|
|
|
|
Show Posts
