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

[bathrobehero]

Yeah but GPUs are different, you've seen here how difficult it can be to get them mining smoothly on the array of different configurations. Imagine trying to write some malware which does that. Second, most people who own expensive enough GPUs for mining will probably notice that their computer is infected since they'll be unable to play games.

That argument flies out of the window once you earn 15 BTC per day for weeks if not months. You can easily deploy a small army of pretty decent coders for that kind of money to overcome any of the difficulties you have mentioned.

[1714043803]

1714043803

[1714043803]

1714043803

[1714043803]

1714043803

[1714043803]

1714043803

[djm34]

Yeah but GPUs are different, you've seen here how difficult it can be to get them mining smoothly on the array of different configurations. Imagine trying to write some malware which does that. Second, most people who own expensive enough GPUs for mining will probably notice that their computer is infected since they'll be unable to play games.

That argument flies out of the window once you earn 15 BTC per day for weeks if not months. You can easily deploy a small army of pretty decent coders for that kind of money to overcome any of the difficulties you have mentioned.

Yeah but GPUs are different, you've seen here how difficult it can be to get them mining smoothly on the array of different configurations. Imagine trying to write some malware which does that. Second, most people who own expensive enough GPUs for mining will probably notice that their computer is infected since they'll be unable to play games.

That argument flies out of the window once you earn 15 BTC per day for weeks if not months. You can easily deploy a small army of pretty decent coders for that kind of money to overcome any of the difficulties you have mentioned.

botnet are still illegal (with jail time if convicted I think) and a small army of coder keeping it quite for long... this will never happen.
Also it is highly unpractical to set up a malware for a large variety of software, gpu's etc...
 
targetting cpu is a lot easier, most of them belongs to non IT personal who won't even notice they are mining.
High end gpu, becomes noisy are owned by people more experience with computer and they will notice something wrong and will probably reinstall everything getting rid of the malware. It isn't a good solution in itself.
botnet are targetting your grandparents computers not ours... for a good reason... not limited to the password in 4 letters 

[bathrobehero]

Yeah but GPUs are different, you've seen here how difficult it can be to get them mining smoothly on the array of different configurations. Imagine trying to write some malware which does that. Second, most people who own expensive enough GPUs for mining will probably notice that their computer is infected since they'll be unable to play games.

That argument flies out of the window once you earn 15 BTC per day for weeks if not months. You can easily deploy a small army of pretty decent coders for that kind of money to overcome any of the difficulties you have mentioned.

Yeah but GPUs are different, you've seen here how difficult it can be to get them mining smoothly on the array of different configurations. Imagine trying to write some malware which does that. Second, most people who own expensive enough GPUs for mining will probably notice that their computer is infected since they'll be unable to play games.

That argument flies out of the window once you earn 15 BTC per day for weeks if not months. You can easily deploy a small army of pretty decent coders for that kind of money to overcome any of the difficulties you have mentioned.

botnet are still illegal (with jail time if convicted I think) and a small army of coder keeping it quite for long... this will never happen.
Also it is highly unpractical to set up a malware for a large variety of software, gpu's etc...
 
targetting cpu is a lot easier, most of them belongs to non IT personal who won't even notice they are mining.
High end gpu, becomes noisy are owned by people more experience with computer and they will notice something wrong and will probably reinstall everything getting rid of the malware. It isn't a good solution in itself.
botnet are targetting your grandparents computers not ours... for a good reason... not limited to the password in 4 letters  

That's beside the point I feel. Illegality I feel is irrelevant because I'd imagine botnet masters would have the common sense of hiding behind proxies. Also, obviously we won't get infected but plenty of corporate computers and personal computers belonging to computer-illiterates (grandmas) will. Obviously the number of infected computers decreases over time as more and more people realize there's something wrong and reinstall the whole thing or delete it with an antivir - if it's finding it that is.

I see your point but I think that huge botnets can control so many CPUs that they can effectively compete with GPUs when it comes to the net hashrate of a coin because at the end of the day botnet CPU mining cost nothing.

[bathrobehero]

It's got a cost - and the cost is higher the less skilled the bot herder is... which it's common for them to be idiots. Executables need developing, then crypting on every change, either the zombie systems must be bought, or an exploit must be found and automated to create/expand the botnet... Also, even if you turn the miner's CPU usage down when someone's on the system, it's possible for them to notice lag. Happy bots stay bots - if the user's experience is harmed too much, then they will reinstall or get the help of someone who can. Another reason GPU mining on bots isn't wisely done... not if you want to continue having a botnet, that is.

I get that and I don't pretend to know much about botnets, but if someone is (was) earning 15 BTC per day I'd imagine they weren't exactly incompetent. 

[TheCoinFinder]

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?

[zenrith]

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?

[jamesl22]

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.

[nicehash]

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

[silencesilence]

Vertcoin Difficulty Chart    UP UP -> 148
http://www.coinwarz.com/cryptocurrency/coins/vertcoin

UP UP -> diff 192

UP UP -> Vertcoin Difficulty 248
UP UP -> Network Hashrate 7.88

[TheCoinFinder]

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.

[djm34]

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  
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

[kenshirothefist]

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

[ReiMomo]

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

[djm34]

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) 

[hopefulsleuth]

Private miners activated.. 

[mrbodz]

Rent and Lease your Lyra2REv2 Rigs at betarigs.com

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

Ahmed Bodi
Betarigs Admin

[sammy007]

I think devs should communicate with craptsy, VTC locked there for several days.

[pallas]

I think devs should communicate with craptsy, VTC locked there for several days.

It's working now.

[silencesilence]

I think devs should communicate with craptsy, VTC locked there for several days.

It's working now.

cryptsy delayed update and dump delayed 

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

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

[trid]

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

You have 11-13 mh from one 750ti?