driver 14.6 only HW 
Which card and settings?
Topic: Vertcoin - First Scrypt N | First Stealth Address - Privacy without mixer - page 45. (Read 1232701 times)
December 06, 2014, 12:49:50 PM
December 06, 2014, 12:35:45 PM
driver 14.6 only HW
December 06, 2014, 12:13:30 PM
read here
expect more clarification from the Vertcoin developers
Vertcoin has always been and will continue to be the leader in decentralization of cryptocurrency. Lyra2 is a natural successor of Scrypt providing an improvement on the same fundamental purpose – scaling hardware difficulty. The decision to move to this algorithm comes as a preemptive strike against ASICs and a move against Multipools. As many of you know, we have several concepts in the hopper to remain in step with the Vertcoin charter – Vertcoin’s [algorithm] is designed to resist the development of custom mining hardware and multipool mining, ensuring that transactions are validated by a widely distributed network and avoiding the selling pressure when large mining pools indiscriminately flood the market with freshly mined coins.
Would someone explain in detail how Vertcoin will be a Multipool resistant ..... what has changed in the algorithms for Multipool resistant
expect more clarification from the Vertcoin developers
December 06, 2014, 12:12:52 PM
December 06, 2014, 12:12:05 PM
Carry on this discussion while Forum **Shilling**, Marinecoin Rewards Forum Content creators and people who reply to forum posts. Fully automatic rewards.
FTFY. Spamming and scamming all day, e'eryday. Please keep your 98% premined shitcoin on your own thread, or better yet, just let your scam peter out and make the world a better place
December 06, 2014, 12:09:33 PM
Well, finally:
node-stratum-pool fork: https://github.com/sammy007/node-stratum-pool/tree/lyra2re
node-multi-hashing fork: https://github.com/sammy007/node-multi-hashing/tree/lyra2re
Tested, it works, shares accepted. Resulting hashes are equal to lyra2re-hash-python output.
Note: sph-blake.c from original zone's repo overwritten with blake.c from VTC repo, because it's blake2b. So please only use this fork for Lyra2RE hashing, other algos using blake simply broken in my fork.
If you want stratum, check out original README.md. Config:
var myCoin = {
"name": "Vertcoin",
"symbol": "VTC",
"algorithm": "lyra2re",
"txMessages": false
};
Hire a hooker for me: VxyRQWAzxWPWhvqYhEUCTSBVJQ2GtDJza8
Thanks for this, will add to the list of projects.
December 06, 2014, 12:05:03 PM
Well, finally:
node-stratum-pool fork: https://github.com/sammy007/node-stratum-pool/tree/lyra2re
node-multi-hashing fork: https://github.com/sammy007/node-multi-hashing/tree/lyra2re
Tested, it works, shares accepted. Resulting hashes are equal to lyra2re-hash-python output.
Note: sph-blake.c from original zone's repo overwritten with blake.c from VTC repo, because it's blake2b. So please only use this fork for Lyra2RE hashing, other algos using blake simply broken in my fork.
If you want stratum, check out original README.md. Config:
var myCoin = {
"name": "Vertcoin",
"symbol": "VTC",
"algorithm": "lyra2re",
"txMessages": false
};
Hire a hooker for me: VxyRQWAzxWPWhvqYhEUCTSBVJQ2GtDJza8
December 06, 2014, 11:54:26 AM
whis sgminer-v5-Lyra2RE-RC1-WIN32
[17:37:34] Probing for an alive pool
[17:37:34] bla-bla-bla.com difficulty changed to 64
[17:37:35] Startup GPU initialization... Using settings from pool bla-bla-bla.com.
[17:37:35] Startup Pool No = 0
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
what I'm doing wrong? or the new lyra sgminer don't work whis pools now? 0_o ps. r280x and 7850
use -g2, I experienced crash at -g4[17:37:34] Probing for an alive pool
[17:37:34] bla-bla-bla.com difficulty changed to 64
[17:37:35] Startup GPU initialization... Using settings from pool bla-bla-bla.com.
[17:37:35] Startup Pool No = 0
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
what I'm doing wrong? or the new lyra sgminer don't work whis pools now? 0_o ps. r280x and 7850
"gpu-threads" : "2",
but now I connect to test pool 92.27.201.170:9174 .... and miner is work!!!
so ... we need wait upgrade other pool?
This pool is just for testing - VTC has not switched to Lyra2 yet.
EDIT: Ugh, this miner doesn't have the worksize bug patched...
December 06, 2014, 11:48:18 AM
whis sgminer-v5-Lyra2RE-RC1-WIN32
[17:37:34] Probing for an alive pool
[17:37:34] bla-bla-bla.com difficulty changed to 64
[17:37:35] Startup GPU initialization... Using settings from pool bla-bla-bla.com.
[17:37:35] Startup Pool No = 0
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
what I'm doing wrong? or the new lyra sgminer don't work whis pools now? 0_o ps. r280x and 7850
use -g2, I experienced crash at -g4[17:37:34] Probing for an alive pool
[17:37:34] bla-bla-bla.com difficulty changed to 64
[17:37:35] Startup GPU initialization... Using settings from pool bla-bla-bla.com.
[17:37:35] Startup Pool No = 0
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
what I'm doing wrong? or the new lyra sgminer don't work whis pools now? 0_o ps. r280x and 7850
"gpu-threads" : "2",
but now I connect to test pool 92.27.201.170:9174 .... and miner is work!!!
so ... we need wait upgrade other pool?
This pool is just for testing - VTC has not switched to Lyra2 yet.
EDIT: Ugh, this miner doesn't have the worksize bug patched...
Worksize bug?
December 06, 2014, 11:20:00 AM
whis sgminer-v5-Lyra2RE-RC1-WIN32
[17:37:34] Probing for an alive pool
[17:37:34] bla-bla-bla.com difficulty changed to 64
[17:37:35] Startup GPU initialization... Using settings from pool bla-bla-bla.com.
[17:37:35] Startup Pool No = 0
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
what I'm doing wrong? or the new lyra sgminer don't work whis pools now? 0_o ps. r280x and 7850
use -g2, I experienced crash at -g4[17:37:34] Probing for an alive pool
[17:37:34] bla-bla-bla.com difficulty changed to 64
[17:37:35] Startup GPU initialization... Using settings from pool bla-bla-bla.com.
[17:37:35] Startup Pool No = 0
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
what I'm doing wrong? or the new lyra sgminer don't work whis pools now? 0_o ps. r280x and 7850
"gpu-threads" : "2",
but now I connect to test pool 92.27.201.170:9174 .... and miner is work!!!
so ... we need wait upgrade other pool?
December 06, 2014, 11:07:44 AM
scrypt-jane is a crypto library and not the name of a hashing function and thats it...
Wolf0 is right...what they call scrypt-jane as a hashing algo is simply cacha and keccak in combination.
Wolf0 is right...what they call scrypt-jane as a hashing algo is simply cacha and keccak in combination.
December 06, 2014, 11:03:06 AM
Actually the new algo is a downgrade on Scrypt Jane which was released 2 years ago. As you are all aware Scrypt Jane has 7 hashing functions Sha256, Sha512, Blake256, Blake512, Skein512, Keccak256 and Keccak512 will your miracle new function has 5 and took months to complete.
Scrypt Jane is still ASIC resistant. Not sure what exactly your trying to sell here but it quite obviously is a downgrade on 2 year old code. Shame really, try something a little more unique next time maybe.
Scrypt Jane is still ASIC resistant. Not sure what exactly your trying to sell here but it quite obviously is a downgrade on 2 year old code. Shame really, try something a little more unique next time maybe.
lol wut. Scrypt-Jane, also known as scrypt-chacha, has Keccak-512 and chacha. That's all.
https://github.com/floodyberry/scrypt-jane
Supported Hash Functions
SHA256/512
BLAKE256/512
Skein512
Keccak256/512 (SHA-3)
Hash function implementations, unlike mix functions, are not optimized. The PBKDF2 computations are relatively minor in the scrypt algorithm, so including CPU specific versions, or vastly unrolling loops, would serve little purpose while bloating the code, both source and binary, and making it more confusing to implement correctly.
https://github.com/yacoin/yacoin/tree/master/src/scrypt-jane/code
December 06, 2014, 11:02:13 AM
Actually the new algo is a downgrade on Scrypt Jane which was released 2 years ago. As you are all aware Scrypt Jane has 7 hashing functions Sha256, Sha512, Blake256, Blake512, Skein512, Keccak256 and Keccak512 will your miracle new function has 5 and took months to complete.
Scrypt Jane is still ASIC resistant. Not sure what exactly your trying to sell here but it quite obviously is a downgrade on 2 year old code. Shame really, try something a little more unique next time maybe.
Scrypt Jane is still ASIC resistant. Not sure what exactly your trying to sell here but it quite obviously is a downgrade on 2 year old code. Shame really, try something a little more unique next time maybe.
lol wut. Scrypt-Jane, also known as scrypt-chacha, has Keccak-512 and chacha. That's all.
I'm running it now, but my rigs all have 4GB or more - I don't think it's gonna be much, though, not like scrypt-N. Probably needs as much SYSTEM memory as X11, but significantly more GPU RAM.
December 06, 2014, 10:55:32 AM
whis sgminer-v5-Lyra2RE-RC1-WIN32
[17:37:34] Probing for an alive pool
[17:37:34] bla-bla-bla.com difficulty changed to 64
[17:37:35] Startup GPU initialization... Using settings from pool bla-bla-bla.com.
[17:37:35] Startup Pool No = 0
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
what I'm doing wrong? or the new lyra sgminer don't work whis pools now? 0_o ps. r280x and 7850
use -g2, I experienced crash at -g4 [17:37:34] Probing for an alive pool
[17:37:34] bla-bla-bla.com difficulty changed to 64
[17:37:35] Startup GPU initialization... Using settings from pool bla-bla-bla.com.
[17:37:35] Startup Pool No = 0
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
what I'm doing wrong? or the new lyra sgminer don't work whis pools now? 0_o ps. r280x and 7850
December 06, 2014, 10:53:38 AM
Actually the new algo is a downgrade on Scrypt Jane which was released 2 years ago. As you are all aware Scrypt Jane has 7 hashing functions Sha256, Sha512, Blake256, Blake512, Skein512, Keccak256 and Keccak512 will your miracle new function has 5 and took months to complete.
Scrypt Jane is still ASIC resistant. Not sure what exactly your trying to sell here but it quite obviously is a downgrade on 2 year old code. Shame really, try something a little more unique next time maybe.
Scrypt Jane is still ASIC resistant. Not sure what exactly your trying to sell here but it quite obviously is a downgrade on 2 year old code. Shame really, try something a little more unique next time maybe.
lol wut. Scrypt-Jane, also known as scrypt-chacha, has Keccak-512 and chacha. That's all.
https://github.com/floodyberry/scrypt-jane
Supported Hash Functions
SHA256/512
BLAKE256/512
Skein512
Keccak256/512 (SHA-3)
Hash function implementations, unlike mix functions, are not optimized. The PBKDF2 computations are relatively minor in the scrypt algorithm, so including CPU specific versions, or vastly unrolling loops, would serve little purpose while bloating the code, both source and binary, and making it more confusing to implement correctly.
https://github.com/yacoin/yacoin/tree/master/src/scrypt-jane/code
December 06, 2014, 10:53:21 AM
Actually the new algo is a downgrade on Scrypt Jane which was released 2 years ago. As you are all aware Scrypt Jane has 7 hashing functions Sha256, Sha512, Blake256, Blake512, Skein512, Keccak256 and Keccak512 will your miracle new function has 5 and took months to complete.
Scrypt Jane is still ASIC resistant. Not sure what exactly your trying to sell here but it quite obviously is a downgrade on 2 year old code. Shame really, try something a little more unique next time maybe.
Scrypt Jane is still ASIC resistant. Not sure what exactly your trying to sell here but it quite obviously is a downgrade on 2 year old code. Shame really, try something a little more unique next time maybe.
That was taken from the vertcoin Reddit. So you Fudding yourself? Quick make up a lie!!
https://www.reddit.com/r/vertcoin/comments/20qlkn/whats_the_difference_between_scryptn_and_scrypt/
December 06, 2014, 10:49:57 AM
whis sgminer-v5-Lyra2RE-RC1-WIN32
[17:37:34] Probing for an alive pool
[17:37:34] bla-bla-bla.com difficulty changed to 64
[17:37:35] Startup GPU initialization... Using settings from pool bla-bla-bla.com.
[17:37:35] Startup Pool No = 0
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
what I'm doing wrong? or the new lyra sgminer don't work whis pools now? 0_o ps. r280x and 7850
[17:37:34] Probing for an alive pool
[17:37:34] bla-bla-bla.com difficulty changed to 64
[17:37:35] Startup GPU initialization... Using settings from pool bla-bla-bla.com.
[17:37:35] Startup Pool No = 0
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[17:37:35] Initialising kernel Lyra2RE.cl with bitalign, unpatched BFI, nfactor 10, n 1024
what I'm doing wrong? or the new lyra sgminer don't work whis pools now? 0_o ps. r280x and 7850
December 06, 2014, 10:47:49 AM
Actually the new algo is a downgrade on Scrypt Jane which was released 2 years ago. As you are all aware Scrypt Jane has 7 hashing functions Sha256, Sha512, Blake256, Blake512, Skein512, Keccak256 and Keccak512 will your miracle new function has 5 and took months to complete.
Scrypt Jane is still ASIC resistant. Not sure what exactly your trying to sell here but it quite obviously is a downgrade on 2 year old code. Shame really, try something a little more unique next time maybe.
Scrypt Jane is still ASIC resistant. Not sure what exactly your trying to sell here but it quite obviously is a downgrade on 2 year old code. Shame really, try something a little more unique next time maybe.
That was taken from the vertcoin Reddit. So you Fudding yourself? Quick make up a lie!!
https://www.reddit.com/r/vertcoin/comments/20qlkn/whats_the_difference_between_scryptn_and_scrypt/
December 06, 2014, 10:45:31 AM
You can now mine on testnet! Just pull and build the latest code: https://github.com/vertcoin/vertcoin. Testnet forks at block 100.
December 06, 2014, 10:44:33 AM
Actually the new algo is a downgrade on Scrypt Jane which was released 2 years ago. As you are all aware Scrypt Jane has 7 hashing functions Sha256, Sha512, Blake256, Blake512, Skein512, Keccak256 and Keccak512 will your miracle new function has 5 and took months to complete.
Scrypt Jane is still ASIC resistant. Not sure what exactly your trying to sell here but it quite obviously is a downgrade on 2 year old code. Shame really, try something a little more unique next time maybe.
Scrypt Jane is still ASIC resistant. Not sure what exactly your trying to sell here but it quite obviously is a downgrade on 2 year old code. Shame really, try something a little more unique next time maybe.
lol wut. Scrypt-Jane, also known as scrypt-chacha, has Keccak-512 and chacha. That's all.
also the only reason why scrypt-jane is asic resistant is because there is no profitable coin to mine... and everybody runs away when the nfactor becomes too high...
(scrypt-jane as all scrypt derivative are high temp algo... at least lyra2RE is low temp/ low power algo... bensam will be happy
) Jump to: