TheCoinFinder
Legendary
Offline
Activity: 938
Merit: 1001
|
|
August 19, 2014, 09:31:07 PM |
|
ocminer / anyone what is the issue with: sph_luffa512_context ctx_luffa1; sph_cubehash512_context ctx_cubehash1; sph_echo512_context ctx_echo1;
uint32_t hashA[16], hashB[16];
sph_luffa512_init (&ctx_luffa1); sph_luffa512 (&ctx_luffa1, input, 80); sph_luffa512_close (&ctx_luffa1, hashA);
sph_cubehash512_init (&ctx_cubehash1); sph_cubehash512 (&ctx_cubehash1, hashA, 64); sph_cubehash512_close(&ctx_cubehash1, hashB);
sph_echo512_init (&ctx_echo1); sph_echo512 (&ctx_echo1, hashB, 64); sph_echo512_close(&ctx_echo1, hashA);
memcpy(output, hashA, 32);
?
|
|
|
|
Bumberchute
|
|
August 19, 2014, 09:42:47 PM |
|
You updated your wallet prior to the fork?
Also, I think the Block Explorer needs to update their client. I have no deposits showing beyond the fork and there were 2.
I'm not sure exactly how to make the block explorer support both algos... I know I'll need some python module which should be called deep_hash, but I don't know how to write this module myself. But if I get that module and plug it into ABE, I'm not sure if the block explorer will still work with the part from before the fork... If anyone could help me out with these problems I'll happily update the block explorer, but if not you guys may need to find someone more experienced to make a new explorer. PM me your email and I'll send you the hash module I don't know why you will need the python module though? The wallet will work fine. As far as I know, the DeepChain.py file I'll have to make for ABE will need to import the deep_hash module and call its deep_hash.getPoWHash(header) function. For example see the X11Chain.py file here: https://github.com/bitcoin-abe/bitcoin-abe/blob/master/Abe/Chain/X11Chain.py#L26I'll need to make one similar to that for Deepcoin that presumably needs to use both the qubit_hash and deep_hash modules.
|
|
|
|
ocminer
Legendary
Offline
Activity: 2688
Merit: 1240
|
|
August 19, 2014, 09:43:16 PM |
|
ocminer / anyone what is the issue with: sph_luffa512_context ctx_luffa1; sph_cubehash512_context ctx_cubehash1; sph_echo512_context ctx_echo1;
uint32_t hashA[16], hashB[16];
sph_luffa512_init (&ctx_luffa1); sph_luffa512 (&ctx_luffa1, input, 80); sph_luffa512_close (&ctx_luffa1, hashA);
sph_cubehash512_init (&ctx_cubehash1); sph_cubehash512 (&ctx_cubehash1, hashA, 64); sph_cubehash512_close(&ctx_cubehash1, hashB);
sph_echo512_init (&ctx_echo1); sph_echo512 (&ctx_echo1, hashB, 64); sph_echo512_close(&ctx_echo1, hashA);
memcpy(output, hashA, 32);
? look in your inbox
|
suprnova pools - reliable mining pools - #suprnova on freenet https://www.suprnova.cc - FOLLOW us @ Twitter ! twitter.com/SuprnovaPools
|
|
|
TheCoinFinder
Legendary
Offline
Activity: 938
Merit: 1001
|
|
August 19, 2014, 10:43:35 PM Last edit: August 19, 2014, 10:53:49 PM by TheCoinFinder |
|
look in your inbox
Thanks for that. I just looked and your code seems identical to mine. Ok, so I need some miners mining the new algo to test this. I dont have a GPU to test, and there seems to be no cpu miner for this? We have changed the port to 9673 so people stop mining with the wrong algorithm.
|
|
|
|
tylerderden
Copper Member
Legendary
Offline
Activity: 1162
Merit: 1025
|
|
August 19, 2014, 11:13:20 PM Last edit: August 19, 2014, 11:29:08 PM by tylerderden |
|
ok so what's up with deepcoin? i mined it before, now when i try to mine on suprnova i get all rejects if i use port 3223 and if i use 3222 i get gpu's on idle waiting for work. which algo are we using now? why am i getting all rejects?
this is my bat file:
sgminer -k deepcoin -o stratum+tcp://deep.suprnova.cc:3223 -u user -p pw -I 13 -g 4 -w 128
i'm getting share below target
|
|
|
|
xtrembash
|
|
August 20, 2014, 12:00:17 AM |
|
i deleted blockchain and redwl blockchain and now my wallet sync it's ok
|
|
|
|
TheCoinFinder
Legendary
Offline
Activity: 938
Merit: 1001
|
|
August 20, 2014, 12:38:48 AM |
|
ok so what's up with deepcoin? i mined it before, now when i try to mine on suprnova i get all rejects if i use port 3223 and if i use 3222 i get gpu's on idle waiting for work. which algo are we using now? why am i getting all rejects?
this is my bat file:
sgminer -k deepcoin -o stratum+tcp://deep.suprnova.cc:3223 -u user -p pw -I 13 -g 4 -w 128
i'm getting share below target
We are using the new deephash algorithm - same as suprnova. Try using that one with us and let us know
|
|
|
|
tylerderden
Copper Member
Legendary
Offline
Activity: 1162
Merit: 1025
|
|
August 20, 2014, 01:54:13 AM |
|
tried your pool hashharder, i got waiting for work from pools...
using bat
sgminer -k deepcoin -o stratum+tcp://www.hashharder.com:9673 -u deepaddress -p x -I 13 -g 4 -w 128
not sure why i'm having so many issues, any guidance would be appreciated.
the messed up thing is i got mostly rejects with supr's pool but a few shares accepted so i dont know what the deal is
|
|
|
|
xwebnetwork
|
|
August 20, 2014, 02:13:24 AM |
|
Tyler, try the following for your config. I had the same issue with the rejects but this cleared it right up. -k deepcoin -o stratum+tcp://deep.suprnova.cc:3223 -u USER -p PASS -w 128 --difficulty-multiplier 256 -g 1 -I 21 Also, on a side note, I think the website is ready to go. Can you guys give it a once over and let me know if you find any bugs/issues? I'd still like to get an "Our Team" page up eventually. http://xwebhosting.org/deepcoin/
|
|
|
|
Goldshredder
|
|
August 20, 2014, 02:21:44 AM Last edit: August 20, 2014, 02:39:37 AM by Goldshredder |
|
Tyler, try the following for your config. I had the same issue with the rejects but this cleared it right up. -k deepcoin -o stratum+tcp://deep.suprnova.cc:3223 -u USER -p PASS -w 128 --difficulty-multiplier 256 -g 1 -I 21 Also, on a side note, I think the website is ready to go. Can you guys give it a once over and let me know if you find any bugs/issues? I'd still like to get an "Our Team" page up eventually. http://xwebhosting.org/deepcoin/As I said earlier: Small grammar change required - "mining DCN yields a much higher hash rate"
|
|
|
|
xwebnetwork
|
|
August 20, 2014, 02:22:49 AM |
|
Whoops! Missed that. Thanks!
|
|
|
|
penambang
|
|
August 20, 2014, 02:48:58 AM |
|
I'm stuck at block 77182 { "version" : 80701, "protocolversion" : 72001, "walletversion" : 60000, "balance" : xxx, "blocks" : 77182, "timeoffset" : 601, "connections" : 3, "proxy" : "", "difficulty" : 14.70271559, "testnet" : false, "keypoololdest" : 1404489751, "keypoolsize" : 101, "paytxfee" : 0.00000000, "mininput" : 0.00001000, "errors" : "" }
|
|
|
|
a.i.a
Newbie
Offline
Activity: 58
Merit: 0
|
|
August 20, 2014, 03:20:52 AM |
|
I'm stuck at block 77182 { "version" : 80701, "protocolversion" : 72001, "walletversion" : 60000, "balance" : xxx, "blocks" : 77182, "timeoffset" : 601, "connections" : 3, "proxy" : "", "difficulty" : 14.70271559, "testnet" : false, "keypoololdest" : 1404489751, "keypoolsize" : 101, "paytxfee" : 0.00000000, "mininput" : 0.00001000, "errors" : "" } seems working { "version" : 80701, "protocolversion" : 72001, "walletversion" : 60000, "balance" : , "blocks" : 77352, "timeoffset" : 50, "connections" : 8, "proxy" : "", "difficulty" : 19.86031337, "testnet" : false, "keypoololdest" : 1408339397, "keypoolsize" : 101, "paytxfee" : 0.00000000, "mininput" : 0.00001000, "errors" : "" }
|
|
|
|
penambang
|
|
August 20, 2014, 03:27:07 AM |
|
some logs: 2014-08-20 03:16:23 trying connection 193.24.210.50:22871 lastseen=-0.1hrs 2014-08-20 03:16:24 connected 193.24.210.50:22871 2014-08-20 03:16:24 send version message: version 72001, blocks=77356, us=36.69.51.208:22871, them=193.24.210.50:22871, peer=193.24.210.50:22871 2014-08-20 03:16:24 trying connection 83.149.8.59:22871 lastseen=84.4hrs 2014-08-20 03:16:25 Added time data, samples 2, offset +600 (+10 minutes) 2014-08-20 03:16:25 receive version message: /Satoshi:0.8.7.1/: version 72001, blocks=77360, us=36.69.51.208:15807, them=193.24.210.50:22871, peer=193.24.210.50:22871 2014-08-20 03:16:25 accepted alert 1, AppliesToMe()=0 2014-08-20 03:16:25 accepted alert 1, AppliesToMe()=0 2014-08-20 03:16:26 received block ad11b5d78ee9cfd6c01714b69f93301bbc4dc492e697077e0c1f1e09014fe65a 2014-08-20 03:16:26 ERROR: AcceptBlock() : incorrect proof of work 2014-08-20 03:16:26 ERROR: ProcessBlock() : AcceptBlock FAILED 2014-08-20 03:16:26 Misbehaving: 193.24.210.50:22871 (0 -> 100) DISCONNECTING 2014-08-20 03:16:26 disconnecting node 193.24.210.50:22871
|
|
|
|
marada
|
|
August 20, 2014, 05:35:49 AM |
|
Me too, block #77018 :/
|
|
|
|
fnordian
Member
Offline
Activity: 60
Merit: 10
|
|
August 20, 2014, 07:19:24 AM |
|
Yep, wallet stuck at 76814...
|
|
|
|
peterw1234
|
|
August 20, 2014, 08:37:13 AM |
|
The new wallet works fine for me though EDIT: Nevermind, turns out I am stuck at block #77625
|
|
|
|
sung
Member
Offline
Activity: 70
Merit: 10
|
|
August 20, 2014, 08:52:10 AM |
|
ye!!!My wallet stuck at #77674
|
|
|
|
kozmos
|
|
August 20, 2014, 09:06:48 AM |
|
Deleted the blockchain, and synced the wallet again.
The wallet sync to the current block at the time of sync, but it does not sync. further more.
Example: Current block = X
The wallet will sync to block X (Current block at the time of the intial synching, after deleting the blockchain from the wallet's folder), but will not sync after that to X+1 .... X+n
I guess we need more nodes.
|
|
|
|
xtrembash
|
|
August 20, 2014, 09:50:09 AM |
|
yea need to delete the blockchain all the time in order to sync ....
|
|
|
|
|