Vertcoin - 1 | ASIC - 0 | Lyra2RE | Decentralised | GPU Mineable | Open Source

[TheCoinFinder]

stratum+tcp://pool.verters.com:3333 dedicated pre-fork lyra2re2 port

All shares submitted will be attributed to user accounts. This port will be joined by port 4444 after the fork. But if you want to test your setup, port 3333 is now setup for the lyra2rev2 algo.

seems to be working, but diff stays too low and a ton of shares are generated.
is vardiff enabled on that port?

Hi yes. What is your hashing speed at the moment and what difficulty is it showing?

[pallas]

stratum+tcp://pool.verters.com:3333 dedicated pre-fork lyra2re2 port

All shares submitted will be attributed to user accounts. This port will be joined by port 4444 after the fork. But if you want to test your setup, port 3333 is now setup for the lyra2rev2 algo.

seems to be working, but diff stays too low and a ton of shares are generated.
is vardiff enabled on that port?

Hi yes. What is your hashing speed at the moment and what difficulty is it showing?

36 Mh/s and diff is 1.6
also the pool stats page shows my user only (on the "contributor shares" table)

[TheCoinFinder]

stratum+tcp://pool.verters.com:3333 dedicated pre-fork lyra2re2 port

All shares submitted will be attributed to user accounts. This port will be joined by port 4444 after the fork. But if you want to test your setup, port 3333 is now setup for the lyra2rev2 algo.

seems to be working, but diff stays too low and a ton of shares are generated.
is vardiff enabled on that port?

Hi yes. What is your hashing speed at the moment and what difficulty is it showing?

36 Mh/s and diff is 1.6
also the pool stats page shows my user only (on the "contributor shares" table)

Hi. Yeah, the contributor shares table seems to have an issue (it only shows yourself in that table mostly, haven't got around to debugging it yet).

I can check for the timings for the vardiff update - but how many shares are you submitting at that difficulty?

[pallas]

seems to be working, but diff stays too low and a ton of shares are generated.
is vardiff enabled on that port?

Hi yes. What is your hashing speed at the moment and what difficulty is it showing?

36 Mh/s and diff is 1.6
also the pool stats page shows my user only (on the "contributor shares" table)

Hi. Yeah, the contributor shares table seems to have an issue (it only shows yourself in that table mostly, haven't got around to debugging it yet).

I can check for the timings for the vardiff update - but how many shares are you submitting at that difficulty?

maybe 2 or 3 a second....

[TheCoinFinder]

Hi. Yeah, the contributor shares table seems to have an issue (it only shows yourself in that table mostly, haven't got around to debugging it yet).

I can check for the timings for the vardiff update - but how many shares are you submitting at that difficulty?

maybe 2 or 3 a second....

Is that from a single worker or multiple workers aggregated?

[pallas]

stratum+tcp://pool.verters.com:3333 dedicated pre-fork lyra2re2 port

All shares submitted will be attributed to user accounts. This port will be joined by port 4444 after the fork. But if you want to test your setup, port 3333 is now setup for the lyra2rev2 algo.

Not sure I understand how that merged ports is working.
If my lyra2rev2 shares are counted for my account, does that mean I'll get the coins when a block is found?
If that's the case, users still mining on the old algo will get less coins, but my shares will not help finding blocks...
That's a disaster if many people start using the new algo.

[pallas]

Hi. Yeah, the contributor shares table seems to have an issue (it only shows yourself in that table mostly, haven't got around to debugging it yet).

I can check for the timings for the vardiff update - but how many shares are you submitting at that difficulty?

maybe 2 or 3 a second....

Is that from a single worker or multiple workers aggregated?

single worker. single rig.

[TheCoinFinder]

stratum+tcp://pool.verters.com:3333 dedicated pre-fork lyra2re2 port

All shares submitted will be attributed to user accounts. This port will be joined by port 4444 after the fork. But if you want to test your setup, port 3333 is now setup for the lyra2rev2 algo.

Not sure I understand how that merged ports is working.
If my lyra2rev2 shares are counted for my account, does that mean I'll get the coins when a block is found?
If that's the case, users still mining on the old algo will get less coins, but my shares will not help finding blocks...
That's a disaster if many people start using the new algo.

Well, the switch over is quite close anyway (a couple of days). And I'm monitoring it to see the uptake - obviously, if more people are using the new algo, then we will find less and less coins until the hardfork - however, by doing this, it should mean that we are one of the first pools to be properly going on / after the hard-fork and hopefully should profit early as the hashrate should alter as the botnet gets mitigated.

[DonCoreRA]

stratum+tcp://pool.verters.com:3333 dedicated pre-fork lyra2re2 port

All shares submitted will be attributed to user accounts. This port will be joined by port 4444 after the fork. But if you want to test your setup, port 3333 is now setup for the lyra2rev2 algo.

Nice!
Work!
Naaaa let`s Test a bit


EDIT:
I have found a BUG in the new sgminer whit Lyra2REv2 Support for AMD Cards, whit Catalyst 14.9 or higher, i have only HW`errors when i start mining...can confirm that someone?!?
Whit 14.4 or lower no Prob.

[TheCoinFinder]

Ok, as a compromise (for now) - any shares submitted will be counted (so the mining is better than just testnet) - but the share difficulty recorded will be half of that whichi t actually is. This is so to penalise the new mining method as it won't find new blocks currently. This penalty will be removed a few hours before the live fork.

[silencesilence]

Why all selling, I have a feeling that comes Mega Dump after 10-08-2015

[AikaPool]

https://aikapool.com/vtc - updated to v0.10.0.0

Welcome!

[upgradeadvice]

node-multihashing w/ Lyra2REv2 working
https://github.com/upgradeadvice/node-multi-hashing

[djm34]

stratum+tcp://pool.verters.com:3333 dedicated pre-fork lyra2re2 port

All shares submitted will be attributed to user accounts. This port will be joined by port 4444 after the fork. But if you want to test your setup, port 3333 is now setup for the lyra2rev2 algo.

Nice!
Work!
Naaaa let`s Test a bit


EDIT:
I have found a BUG in the new sgminer whit Lyra2REv2 Support for AMD Cards, whit Catalyst 14.9 or higher, i have only HW`errors when i start mining...can confirm that someone?!?
Whit 14.4 or lower no Prob.

which cards ?  
I will have a look

edit: just upgraded my driver to 15.7, my 290x is still working fine, getting around 7.5MH/s
(I will make a second algo based on the old matrix as used in lyra2re, see if the cards which have problem still have problem... but obviously it isn't something I can really test on my computer...) however this code is expected to be a little slower...

[glukolog]

EDIT:
I have found a BUG in the new sgminer whit Lyra2REv2 Support for AMD Cards, whit Catalyst 14.9 or higher, i have only HW`errors when i start mining...can confirm that someone?!?
Whit 14.4 or lower no Prob.

which cards ?  
I will have a look

AMD 5970 with catalyst 13.111 have only HW errors

[djm34]

EDIT:
I have found a BUG in the new sgminer whit Lyra2REv2 Support for AMD Cards, whit Catalyst 14.9 or higher, i have only HW`errors when i start mining...can confirm that someone?!?
Whit 14.4 or lower no Prob.

which cards ?  
I will have a look

AMD 5970 with catalyst 13.111 have only HW errors

can you check that the old lyra (Lyra2RE) is working within that version ?
 you should get boo instead of hw error

[glukolog]

EDIT:
I have found a BUG in the new sgminer whit Lyra2REv2 Support for AMD Cards, whit Catalyst 14.9 or higher, i have only HW`errors when i start mining...can confirm that someone?!?
Whit 14.4 or lower no Prob.

which cards ?  
I will have a look

AMD 5970 with catalyst 13.111 have only HW errors

can you check that the old lyra (Lyra2RE) is working within that version ?
 you should get boo instead of hw error

Yes, 5970 is working on that version sgminer with "-k Lyra2RE"

[djm34]

can someone try this new kernel: http://ge.tt/6zmgnrL2?c
with --kernel Lyra2REv2

however don't push too high the intensity, it needs some fix in the code... (I just need to know if it is working...)
it is based on the old lyra kernel and the performance are terrible...

this is just in case the problem doesn't get solved

[never]

can someone try this new kernel: http://ge.tt/6zmgnrL2?c
with --kernel Lyra2REv2

however don't push too high the intensity, it needs some fix in the code... (I just need to know if it is working...)
it is based on the old lyra kernel and the performance are terrible...

this is just in case the problem doesn't get solved

This is what I get on 7970 GPUs.

[16:19:51] Started sgminer 5.1.0
"./kernel/skein256.cl", line 85: warning: white space betw
          newline in line splice ignored
            p0 += h[((R)+0) % 9];  \
                                    ^

"./kernel/skein256.cl", line 97: warning: white space betw
          newline in line splice ignored
                p0 += h[((R)+1) % 9];   \
                          [16:19:52] Failed to init GPU th
ce 0
[16:19:52] Restarting the GPU from the menu will not fix t
[16:19:52] Re-check your configuration and try restarting.

[djm34]

can someone try this new kernel: http://ge.tt/6zmgnrL2?c
with --kernel Lyra2REv2

however don't push too high the intensity, it needs some fix in the code... (I just need to know if it is working...)
it is based on the old lyra kernel and the performance are terrible...

this is just in case the problem doesn't get solved

This is what I get on 7970 GPUs.

[16:19:51] Started sgminer 5.1.0
"./kernel/skein256.cl", line 85: warning: white space betw
          newline in line splice ignored
            p0 += h[((R)+0) % 9];  \
                                    ^

"./kernel/skein256.cl", line 97: warning: white space betw
          newline in line splice ignored
                p0 += h[((R)+1) % 9];   \
                          [16:19:52] Failed to init GPU th
ce 0
[16:19:52] Restarting the GPU from the menu will not fix t
[16:19:52] Re-check your configuration and try restarting.

for which one ? (these are warning they are non lethal)