Pages:
Author

Topic: Vertcoin - 1 | ASIC - 0 | Lyra2RE | Decentralised | GPU Mineable | Open Source - page 70. (Read 415451 times)

sr. member
Activity: 457
Merit: 273
To answer your question:
first I am the author of all those versions. metallicjames was rather a pre-release, and after that I decided to change the difficulty to 256, as it was allowing miners to get more shares. so apparently the other followed more the pre-release version that the "standard version".
also at that time, I was using verter, and this was the parameter which was giving good aggreement between the hashrate reported by the miner and the pool...

I can always change that setting for lyra2re (but technically it should have been 256) 

OK, please post here once you'll release a new version with 128 diff for the original lyra (and possibly add the aforementioned aliases for lyra2 algos - similarly as badman74 did in his version for the original lyra2).
legendary
Activity: 1120
Merit: 1000
sr. member
Activity: 2366
Merit: 305
Duelbits - $100k Bonus/week
Don't forget to delete or rename the .bin files after .dlls are placed.
newbie
Activity: 7
Merit: 0
Hello, guys
I have this kind of problem
My rig with 1x Radeon 7950 and 2x 5870 worked fine with previous algorithms of Vertcoin and other coins.

After the recent algorithm switch 7950 keeps working, giving ~3.4 Mh and ~12.5 of WU (intensity 19, worksizes 32 - 256 all work)
Both 5870 give just HW errors and around 1.7 Mh of false hashrate, doing nothing.
I tried changing the intensity, worksizes, clock and memory speeds - nothing helps. Also put the --no-extranonce flag.

Pool: give-me-coins, --diffuculty-multiplier is set to 2
ATI (AMD) Driver 13.12. Also tried above mentioned DLLs from 14.4 in the miner folder.
sgminer taken from official website

Did anybody get the 5870 running?
sr. member
Activity: 425
Merit: 250

750ti seems to be fine, now getting 11-13Mhash on verters.


You have 11-13 mh from one 750ti?
legendary
Activity: 1120
Merit: 1000
I think devs should communicate with craptsy, VTC locked there for several days.

It's working now.

cryptsy delayed update and dump delayed  Grin

But now – Yes, see Vertcoin, the wallet is update

https://www.cryptsy.com/pages/status

legendary
Activity: 2716
Merit: 1094
Black Belt Developer
I think devs should communicate with craptsy, VTC locked there for several days.

It's working now.
legendary
Activity: 1904
Merit: 1003
I think devs should communicate with craptsy, VTC locked there for several days.
hero member
Activity: 800
Merit: 1000
Rent and Lease your Lyra2REv2 Rigs at betarigs.com

https://www.betarigs.com/list?miner_type=21

Ahmed Bodi
Betarigs Admin
newbie
Activity: 1
Merit: 0
Private miners activated..  Undecided
legendary
Activity: 1400
Merit: 1050
Hey, djm34,

May I ask you why did you change the diff adjustment from 128 to 256 in your miner for the original Lyra2RE algorithm?

algorithm.c

all other miners (official https://github.com/sgminer-dev/sgminer, badman74's https://github.com/badman74/sgminer, James Lovejoy https://github.com/metalicjames/sgminer-Lyra2RE, etc.):

Code:
{ "lyra2re", ALGO_LYRA2RE, "", 1, 128, 128, 0, 0, 0xFF, 0xFFFFULL, 0x0000ffffUL, 4, 2 * 8 * 4194304 , 0, lyra2re_regenhash, queue_lyra2RE_kernel, gen_hash, NULL},

your miner:

Code:
{ "Lyra2RE", ALGO_LYRA2RE, "", 1, 256, 256, 0, 0, 0xFF, 0xFFFFULL, 0x0000ffffUL, 4,2 * 8 * 4194304 , 0, lyra2reold_regenhash, queue_lyra2RE_kernel, gen_hash, NULL},

The issue is that obviously minority (or none) of the miners were using your sgminer version to mine the original Lyra2RE coins. Now since your version is popular, it won't work on existing Lyra2RE pools (without explicitly setting diff multiplier option, which is "deprecated" and hard to set if one is using configuration for multiple algorithms). Please correct your repo and set diff to 128 for the original Lyra2RE algo. It might also be wise for you to build new releases for the changes you recently added to your repo.

Another thing that would be good for you to add are aliases for algorithms (when using with -k or in config file) Lyra2RE == lyra2re, Lyre2REv2 = lyra2rev2 ...

Thanks and keep up the good work!

Kind regards,
kenshirothefist
To answer your question:
first I am the author of all those versions. metallicjames was rather a pre-release, and after that I decided to change the difficulty to 256, as it was allowing miners to get more shares. so apparently the other followed more the pre-release version that the "standard version".
also at that time, I was using verter, and this was the parameter which was giving good aggreement between the hashrate reported by the miner and the pool...

I can always change that setting for lyra2re (but technically it should have been 256) 
sr. member
Activity: 2366
Merit: 305
Duelbits - $100k Bonus/week
For anyone who wants an updated cpuminer since the last compiled version by the author does not support lyra2rev2 I compiled one yesterday.

https://mega.co.nz/#!eVZlgCDA!UiPBfUaeEEsKITPh2t2c_-4eBDNOB5noxgNNCYfD15Q

Virustotal 1/56 (bitcoin miner flag): https://www.virustotal.com/en/file/afc83ed72cc2a4b02424a91d41c0c8e170c345cd1d0513ef17a7d87adf3212cb/analysis/1439303005/

Lol I've just found a block on Aika pool with CPU Cheesy
sr. member
Activity: 457
Merit: 273
Hey, djm34,

May I ask you why did you change the diff adjustment from 128 to 256 in your miner for the original Lyra2RE algorithm?

algorithm.c

all other miners (official https://github.com/sgminer-dev/sgminer, badman74's https://github.com/badman74/sgminer, James Lovejoy https://github.com/metalicjames/sgminer-Lyra2RE, etc.):

Code:
{ "lyra2re", ALGO_LYRA2RE, "", 1, 128, 128, 0, 0, 0xFF, 0xFFFFULL, 0x0000ffffUL, 4, 2 * 8 * 4194304 , 0, lyra2re_regenhash, queue_lyra2RE_kernel, gen_hash, NULL},

your miner:

Code:
{ "Lyra2RE", ALGO_LYRA2RE, "", 1, 256, 256, 0, 0, 0xFF, 0xFFFFULL, 0x0000ffffUL, 4,2 * 8 * 4194304 , 0, lyra2reold_regenhash, queue_lyra2RE_kernel, gen_hash, NULL},

The issue is that obviously minority (or none) of the miners were using your sgminer version to mine the original Lyra2RE coins. Now since your version is popular, it won't work on existing Lyra2RE pools (without explicitly setting diff multiplier option, which is "deprecated" and hard to set if one is using configuration for multiple algorithms). Please correct your repo and set diff to 128 for the original Lyra2RE algo. It might also be wise for you to build new releases for the changes you recently added to your repo.

Another thing that would be good for you to add are aliases for algorithms (when using with -k or in config file) Lyra2RE == lyra2re, Lyre2REv2 = lyra2rev2 ...

Thanks and keep up the good work!

Kind regards,
kenshirothefist
legendary
Activity: 1400
Merit: 1050
Managed to run my 280x at 4,1 Mhash.

Pool reports way more than that though, between 6 and 8Mhash.
Anyone else got that too?

25MH/s overall in my test on Verters appears as 35MH/s with pretty high consistency.

Test hash of 31.5MH/s about, sent to Give-Me-Coins as a test (difficulty multiplier was, of course, adjusted) - they were dead on.

Yes, if you go back a few pages in this thread - you will see that I updated my pool to the presumably correct (based on hashrate) mask (7fff rather than ffff) - however people were then complaining of "invalid shares" - presumably the sgminer/ccminer's basic mask is below the default mask of the new algorithm and they need to be updated to avoid this issue.

Should be a single line edit in algorithm.c.
it is a single line to edit, just need that the main pool agree with each others (I don't change anything otherwise)
it was already a mess at the previous fork and the strange thing was that the miners in both case the miners were released before the pool  Grin
Last time I changed several time the difficulty there was always a problem with a pool or another... so this time I won't do anything unless there is a consensus

legendary
Activity: 938
Merit: 1001
Managed to run my 280x at 4,1 Mhash.

Pool reports way more than that though, between 6 and 8Mhash.
Anyone else got that too?

25MH/s overall in my test on Verters appears as 35MH/s with pretty high consistency.

Test hash of 31.5MH/s about, sent to Give-Me-Coins as a test (difficulty multiplier was, of course, adjusted) - they were dead on.

Yes, if you go back a few pages in this thread - you will see that I updated my pool to the presumably correct (based on hashrate) mask (7fff rather than ffff) - however people were then complaining of "invalid shares" - presumably the sgminer/ccminer's basic mask is below the default mask of the new algorithm and they need to be updated to avoid this issue.
legendary
Activity: 1120
Merit: 1000
legendary
Activity: 885
Merit: 1006
NiceHash.com
We're pleased to announce the immediate availability for buying and selling hashing power based on Lyra2REv2 algorithm on NiceHash.com: https://www.nicehash.com/index.jsp?p=news&id=27

Kind regards,
NiceHash.com
sr. member
Activity: 392
Merit: 250
Question about p2pools..

I've never successfully been able to connect to any p2pool listed on the p2pool site.  Yes, I connect to verters and coinotron with ease, but not p2pool.

I constantly get "no connection errors".  Yes, I've used my wallet and pass x for miner, but no luck.  I would rather bring my mining "power" over to the p2pool in order to help balance the coin.

Suggestions?

Try using the --no-extranonce flag with your miner.
newbie
Activity: 32
Merit: 0
Question about p2pools..

I've never successfully been able to connect to any p2pool listed on the p2pool site.  Yes, I connect to verters and coinotron with ease, but not p2pool.

I constantly get "no connection errors".  Yes, I've used my wallet and pass x for miner, but no luck.  I would rather bring my mining "power" over to the p2pool in order to help balance the coin.

Suggestions?
legendary
Activity: 938
Merit: 1001
Correct - and this is where profit comes into play. Lyra2REv2 is now less profitable than it was. Something like XMR is likely to STAY profitable for me. Now, were I him, that shit would be important to me, because there's pretty much no absolute certainty on bot command & control... it's actually likely there will always be a few at least trying to mine Lyra on old orders, never having got new ones. I obviously wanna minimize this shit, so parking my ass on XMR begins to look better than VTC, who just changed the algo to fuck up my day.

Agreed. Its like updating your own car's security - sure, it can probably be hacked if its worth it - however its now more secure and not that much more valuable (or less valuable) than half of the other cars in the same car park - so why would you try to steal it, when you can steal something that is far easier and more valuable?
Pages:
Jump to: