[ANN] [SUP] Supcoin, PLUCK algorithm, Just Launched, Mine Now! - page 45.

Wolf0

member

Activity: 81

Merit: 1002

It was only the wind.

Quote from: Arux on February 19, 2015, 04:20:53 PM

Quote from: Wolf0 on February 19, 2015, 04:16:16 PM

Quote from: Arux on February 19, 2015, 04:13:40 PM

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 ?

arloseb

hero member

Activity: 868

Merit: 1000

this coin should be launched with cpu. if not will be raped as all coins.

ocminer

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)

go6ooo1212

legendary

Activity: 1512

Merit: 1000

quarkchain.io

Prefer amd miner not to be arranged at launch ...

ray88

full member

Activity: 212

Merit: 100

launch should be delayed till amd miner is release, if it dont once the count down finish.

earlz

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.

Wolf0

member

Activity: 81

Merit: 1002

It was only the wind.

Quote from: Arux on February 19, 2015, 04:13:40 PM

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?

cisahasa

legendary

Activity: 910

Merit: 1000

my core2 0.22khs, no point to run here

temroa

full member

Activity: 126

Merit: 100

hey djm34 will you release windows nvidia miner soon want to use it before sleep

earlz

sr. member

Activity: 439

Merit: 250

mmmmmm

Quote from: cakir on February 19, 2015, 05:32:16 PM

Quote from: earlz on February 19, 2015, 05:28:45 PM

Quote from: cisahasa on February 19, 2015, 05:18:19 PM

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

ray88

full member

Activity: 212

Merit: 100

Quote from: cakir on February 19, 2015, 05:32:16 PM

Quote from: earlz on February 19, 2015, 05:28:45 PM

Quote from: cisahasa on February 19, 2015, 05:18:19 PM

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

Shadow_Runner

hero member

Activity: 574

Merit: 500

i5-3470
0.74 kh/s

Wolf0

member

Activity: 81

Merit: 1002

It was only the wind.

Quote from: temroa on February 19, 2015, 04:05:50 PM

Why is the hashrate so big at pool site

Again, the hashrate display is not working yet.

cakir

legendary

Activity: 1274

Merit: 1000

★ BitClave ICO: 15/09/17 ★

Quote from: earlz on February 19, 2015, 05:28:45 PM

Quote from: cisahasa on February 19, 2015, 05:18:19 PM

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

earlz

sr. member

Activity: 439

Merit: 250

mmmmmm

Quote from: cisahasa on February 19, 2015, 05:18:19 PM

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

Wolf0

member

Activity: 81

Merit: 1002

It was only the wind.

Quote from: YesOrNo on February 19, 2015, 03:58:11 PM

Quote from: e1ghtSpace on February 19, 2015, 03:51:35 PM

Quote from: YesOrNo on February 19, 2015, 03:47:37 PM

https://www.virustotal.com/pl/file/72f800749b59bfb63fe9e57ea4c5a6d959c82c5294cc4666912775b492c90e00/analysis/ Shocked

Does it really have to have so many red flags ?

Are you serious?

Yes I am

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.

cisahasa

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

Arux

hero member

Activity: 500

Merit: 500

Quote from: jamo4000 on February 19, 2015, 05:15:18 PM

Quote from: ocminer on February 19, 2015, 05:11:10 PM

Quote from: Arux on February 19, 2015, 05:09:17 PM

@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

yes thanks a lot.

jamo4000

sr. member

Activity: 807

Merit: 251

Quote from: ocminer on February 19, 2015, 05:11:10 PM

Quote from: Arux on February 19, 2015, 05:09:17 PM

@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

ocminer

legendary

Activity: 2688

Merit: 1240

Quote from: Arux on February 19, 2015, 05:09:17 PM

@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

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