Pages:
Author

Topic: [ANN] [SUP] Supcoin, PLUCK algorithm, Just Launched, Mine Now! - page 45. (Read 62226 times)

member
Activity: 81
Merit: 1002
It was only the wind.
unable to get accepted blocks with wolf-pluckminer-generic64-update1.exe in solomine. (shares are accepted with pool+statum)
Quote
2015-02-19 21:06:27   nActualTimespan = 36  before bounds
2015-02-19 21:06:27 GetNextWorkRequired DIGISHIELD RETARGET
2015-02-19 21:06:27 Params().TargetTimespan() = 300    nActualTimespan = 267
2015-02-19 21:06:27 Before: 1e114863  0000114863000000000000000000000000000000000000000000000000000000
2015-02-19 21:06:27 After:  1e0f61b4  00000f61b4451eb851eb851eb851eb851eb851eb851eb851eb851eb851eb851e
2015-02-19 21:06:27 ERROR: ContextualCheckBlock : block height mismatch in coinbase
2015-02-19 21:06:27 ERROR: ProcessNewBlock : AcceptBlock FAILED
2015-02-19 21:06:36   nActualTimespan = 36  before bounds
2015-02-19 21:06:36 GetNextWorkRequired DIGISHIELD RETARGET
2015-02-19 21:06:36 Params().TargetTimespan() = 300    nActualTimespan = 267
2015-02-19 21:06:36 Before: 1e114863  0000114863000000000000000000000000000000000000000000000000000000
2015-02-19 21:06:36 After:  1e0f61b4  00000f61b4451eb851eb851eb851eb851eb851eb851eb851eb851eb851eb851e
2015-02-19 21:06:50 GUI: flush: BitBlt failed (Descripteur non valide)
2015-02-19 21:06:50 GUI: flush: BitBlt failed (Descripteur non valide)
2015-02-19 21:07:36   nActualTimespan = 36  before bounds
2015-02-19 21:07:36 GetNextWorkRequired DIGISHIELD RETARGET
2015-02-19 21:07:36 Params().TargetTimespan() = 300    nActualTimespan = 267
2015-02-19 21:07:36 Before: 1e114863  0000114863000000000000000000000000000000000000000000000000000000
2015-02-19 21:07:36 After:  1e0f61b4  00000f61b4451eb851eb851eb851eb851eb851eb851eb851eb851eb851eb851e

You're not attempting to mine on mainnet, are you?
Quote
wolf-pluckminer-generic64-update1.exe -o http://127.0.0.1:14412 -O blabla:popolop --coinbase-addr=mrHSmcwqw9LAUe5ShPgUotfMWwMWqfg6Lx

port 14412 and supcoin-qt.exe -testnet
so i'm on the testnet i guess

isn't it supposed to be -testnet=1 ?
hero member
Activity: 868
Merit: 1000
this coin should be launched with cpu. if not will be raped as all coins.
legendary
Activity: 2688
Merit: 1240
Hashrate of the (CPU) Miners on Suprnova should match now, also the other stats like % of expected shares etc.

Trying to get the GPU miner to work now... (probably something with -f 256 or -l 256 etc.. not sure where the problem is atm)
legendary
Activity: 1512
Merit: 1000
quarkchain.io
Prefer amd miner not to be arranged at launch ...
full member
Activity: 212
Merit: 100
launch should be delayed till amd miner is release, if it dont once the count down finish.
sr. member
Activity: 439
Merit: 250
mmmmmm
Solo Miners!

If you are using CPU miner, please do not use the --coinbase-address flag. I'm investigating an issue where the miner doesn't properly construct blocks with the block height in the coinbase. Long story short, remove that flag to use "getwork" rather than "getblocktemplate". Getwork does not suffer from this problem and the CPU miner should work fine when using it.
member
Activity: 81
Merit: 1002
It was only the wind.
unable to get accepted blocks with wolf-pluckminer-generic64-update1.exe in solomine. (shares are accepted with pool+statum)
Quote
2015-02-19 21:06:27   nActualTimespan = 36  before bounds
2015-02-19 21:06:27 GetNextWorkRequired DIGISHIELD RETARGET
2015-02-19 21:06:27 Params().TargetTimespan() = 300    nActualTimespan = 267
2015-02-19 21:06:27 Before: 1e114863  0000114863000000000000000000000000000000000000000000000000000000
2015-02-19 21:06:27 After:  1e0f61b4  00000f61b4451eb851eb851eb851eb851eb851eb851eb851eb851eb851eb851e
2015-02-19 21:06:27 ERROR: ContextualCheckBlock : block height mismatch in coinbase
2015-02-19 21:06:27 ERROR: ProcessNewBlock : AcceptBlock FAILED
2015-02-19 21:06:36   nActualTimespan = 36  before bounds
2015-02-19 21:06:36 GetNextWorkRequired DIGISHIELD RETARGET
2015-02-19 21:06:36 Params().TargetTimespan() = 300    nActualTimespan = 267
2015-02-19 21:06:36 Before: 1e114863  0000114863000000000000000000000000000000000000000000000000000000
2015-02-19 21:06:36 After:  1e0f61b4  00000f61b4451eb851eb851eb851eb851eb851eb851eb851eb851eb851eb851e
2015-02-19 21:06:50 GUI: flush: BitBlt failed (Descripteur non valide)
2015-02-19 21:06:50 GUI: flush: BitBlt failed (Descripteur non valide)
2015-02-19 21:07:36   nActualTimespan = 36  before bounds
2015-02-19 21:07:36 GetNextWorkRequired DIGISHIELD RETARGET
2015-02-19 21:07:36 Params().TargetTimespan() = 300    nActualTimespan = 267
2015-02-19 21:07:36 Before: 1e114863  0000114863000000000000000000000000000000000000000000000000000000
2015-02-19 21:07:36 After:  1e0f61b4  00000f61b4451eb851eb851eb851eb851eb851eb851eb851eb851eb851eb851e

You're not attempting to mine on mainnet, are you?
legendary
Activity: 910
Merit: 1000
my core2 0.22khs, no point to run here
full member
Activity: 126
Merit: 100
hey djm34 will you release windows nvidia miner soon want to use it before sleep Smiley
sr. member
Activity: 439
Merit: 250
mmmmmm
wolfs amd miner got 67khs..

 no way im playing with my cpus any more, im out

1       Slut    67khs    25,467.58sup/day

dont try to tell its not u

If you're getting that from the pool, you should know the pool hashrate estimates are completely and wildly inaccurate.

CPU miners get around 1.6khash/s(average, for all cores), GPU miners get around 6khash/s(per GPU).

So, CPUs will definitely still be competitive at this point
My cpu - i5 2410m gets 0.24 khs tops.

http://i.imgur.com/tXBqApx.png

Looks like you compiled it yourself. Make sure to use `make CFLAGS="-O3 -march=native"` Otherwise you'll end up with an unoptimized miner. I thought this was obvious, but I'll add a note to the ANN for it
full member
Activity: 212
Merit: 100
wolfs amd miner got 67khs..

 no way im playing with my cpus any more, im out

1       Slut    67khs    25,467.58sup/day

dont try to tell its not u

If you're getting that from the pool, you should know the pool hashrate estimates are completely and wildly inaccurate.

CPU miners get around 1.6khash/s(average, for all cores), GPU miners get around 6khash/s(per GPU).

So, CPUs will definitely still be competitive at this point
My cpu - i5 2410m gets 0.24 khs tops.

http://i.imgur.com/tXBqApx.png

nividia gets 30x that... hmm a bit unfair for sure and all that unoptimized Sad
hero member
Activity: 574
Merit: 500
i5-3470
0.74 kh/s
member
Activity: 81
Merit: 1002
It was only the wind.
Why is the hashrate so big at pool site

Again, the hashrate display is not working yet.
legendary
Activity: 1274
Merit: 1000
★ BitClave ICO: 15/09/17 ★
wolfs amd miner got 67khs..

 no way im playing with my cpus any more, im out

1       Slut    67khs    25,467.58sup/day

dont try to tell its not u

If you're getting that from the pool, you should know the pool hashrate estimates are completely and wildly inaccurate.

CPU miners get around 1.6khash/s(average, for all cores), GPU miners get around 6khash/s(per GPU).

So, CPUs will definitely still be competitive at this point
My cpu - i5 2410m gets 0.24 khs tops.

http://i.imgur.com/tXBqApx.png
sr. member
Activity: 439
Merit: 250
mmmmmm
wolfs amd miner got 67khs..

 no way im playing with my cpus any more, im out

1       Slut    67khs    25,467.58sup/day

dont try to tell its not u

If you're getting that from the pool, you should know the pool hashrate estimates are completely and wildly inaccurate.

CPU miners get around 1.6khash/s(average, for all cores), GPU miners get around 6khash/s(per GPU).

So, CPUs will definitely still be competitive at this point
member
Activity: 81
Merit: 1002
It was only the wind.

It's common knowledge that because miners are used by malware, most AV software flags miners themselves as malware.

It's common knowledge among the more tech-savvy that AV programs are snake oil and almost completely useless.

Anyways, I signed it with my key - the same one I use for Bitcoin-OTC.
legendary
Activity: 910
Merit: 1000
wolfs amd miner got 67khs..

 no way im playing with my cpus any more, im out

1       Slut    67khs    25,467.58sup/day

dont try to tell its not u
hero member
Activity: 500
Merit: 500
@ocminer: port will be 7777 at launch too?


yep, about one hour before launch, i will wipe everything and start at launch with a fresh wallet etc. on the same port.

hashrate is now also almost correct, so it looks good

Good job ! Thanks Smiley

yes thanks a lot.
sr. member
Activity: 807
Merit: 251
@ocminer: port will be 7777 at launch too?


yep, about one hour before launch, i will wipe everything and start at launch with a fresh wallet etc. on the same port.

hashrate is now also almost correct, so it looks good

Good job ! Thanks Smiley
legendary
Activity: 2688
Merit: 1240
@ocminer: port will be 7777 at launch too?


yep, about one hour before launch, i will wipe everything and start at launch with a fresh wallet etc. on the same port.

hashrate is now also almost correct, so it looks good
Pages:
Jump to: