Topic: [ANN][YAC] yacoin: yet another altcoin. START is now. - page 173. (Read 346684 times)
Nice! Why didn't I think of this for GRC coin, change the algorithm so only I have the ability to GPU mine at release, brilliant, I tip my hat to you sir
HOHO
+1 for digicoin
Also, what time in UTC does this monster get released?
Also, what time in UTC does this monster get released?
About 8 seconds per hash attempt with 512 megabytes, so it'd take 18 days to verify the initial download of a blockchain with 200,000 blocks. lol so how much space on hd can it take?
no more than usual, it's just the algorithm that is being altered.
About 8 seconds per hash attempt with 512 megabytes, so it'd take 18 days to verify the initial download of a blockchain with 200,000 blocks. lol so how much space on hd can it take?
RilCoin,
MemCoin,
SilverCoin,
IronCoin
I personally prefer IronCoin, sound like come from GOT
MemCoin,
SilverCoin,
IronCoin
I personally prefer IronCoin, sound like come from GOT
QuadCoreCoin?!?!
digicoin ?
CPUCoin
Corecoin?
CPUCoin
Really someone just needs to implement it with high r values and see what kind of hash rates they get. I don't think an r leading to 512 MB of RAM required will be that catastrophic.
Here you go:
Quote
[test]$ time ./scrypt-ref 1024 1 1
0.007u 0.000s 0:00.00 0.0% 0+0k 0+0io 0pf+0w
[test]$ time ./scrypt-ref 1024 4096 1
31.282u 0.235s 0:31.55 99.8% 0+0k 0+0io 0pf+0w
[test]$ time ./scrypt-sse 1024 4096 1
9.725u 0.225s 0:09.95 99.8% 0+0k 0+0io 0pf+0w
[test]$ time ./scrypt-nosse 1024 4096 1
7.535u 0.210s 0:07.75 99.8% 0+0k 0+0io 0pf+0w
[test]$ cat /proc/cpuinfo | grep name
model name : Intel(R) Xeon(R) CPU E5540 @ 2.53GHz
model name : Intel(R) Xeon(R) CPU E5540 @ 2.53GHz
model name : Intel(R) Xeon(R) CPU E5540 @ 2.53GHz
model name : Intel(R) Xeon(R) CPU E5540 @ 2.53GHz
[test]$ uname -a
Linux cs 2.6.18-308.16.1.el5 #1 SMP Tue Sep 18 07:21:07 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux
0.007u 0.000s 0:00.00 0.0% 0+0k 0+0io 0pf+0w
[test]$ time ./scrypt-ref 1024 4096 1
31.282u 0.235s 0:31.55 99.8% 0+0k 0+0io 0pf+0w
[test]$ time ./scrypt-sse 1024 4096 1
9.725u 0.225s 0:09.95 99.8% 0+0k 0+0io 0pf+0w
[test]$ time ./scrypt-nosse 1024 4096 1
7.535u 0.210s 0:07.75 99.8% 0+0k 0+0io 0pf+0w
[test]$ cat /proc/cpuinfo | grep name
model name : Intel(R) Xeon(R) CPU E5540 @ 2.53GHz
model name : Intel(R) Xeon(R) CPU E5540 @ 2.53GHz
model name : Intel(R) Xeon(R) CPU E5540 @ 2.53GHz
model name : Intel(R) Xeon(R) CPU E5540 @ 2.53GHz
[test]$ uname -a
Linux cs 2.6.18-308.16.1.el5 #1 SMP Tue Sep 18 07:21:07 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux
About 8 seconds per hash attempt with 512 megabytes, so it'd take 18 days to verify the initial download of a blockchain with 200,000 blocks.
ouch.
Basically everyone would have to run it through an electrum server of some sort.
I vote the name of the coin to be ElectrumCoin.
Electrum has already been used. Cool name though
Really someone just needs to implement it with high r values and see what kind of hash rates they get. I don't think an r leading to 512 MB of RAM required will be that catastrophic.
Here you go:
Quote
[test]$ time ./scrypt-ref 1024 1 1
0.007u 0.000s 0:00.00 0.0% 0+0k 0+0io 0pf+0w
[test]$ time ./scrypt-ref 1024 4096 1
31.282u 0.235s 0:31.55 99.8% 0+0k 0+0io 0pf+0w
[test]$ time ./scrypt-sse 1024 4096 1
9.725u 0.225s 0:09.95 99.8% 0+0k 0+0io 0pf+0w
[test]$ time ./scrypt-nosse 1024 4096 1
7.535u 0.210s 0:07.75 99.8% 0+0k 0+0io 0pf+0w
[test]$ cat /proc/cpuinfo | grep name
model name : Intel(R) Xeon(R) CPU E5540 @ 2.53GHz
model name : Intel(R) Xeon(R) CPU E5540 @ 2.53GHz
model name : Intel(R) Xeon(R) CPU E5540 @ 2.53GHz
model name : Intel(R) Xeon(R) CPU E5540 @ 2.53GHz
[test]$ uname -a
Linux cs 2.6.18-308.16.1.el5 #1 SMP Tue Sep 18 07:21:07 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux
0.007u 0.000s 0:00.00 0.0% 0+0k 0+0io 0pf+0w
[test]$ time ./scrypt-ref 1024 4096 1
31.282u 0.235s 0:31.55 99.8% 0+0k 0+0io 0pf+0w
[test]$ time ./scrypt-sse 1024 4096 1
9.725u 0.225s 0:09.95 99.8% 0+0k 0+0io 0pf+0w
[test]$ time ./scrypt-nosse 1024 4096 1
7.535u 0.210s 0:07.75 99.8% 0+0k 0+0io 0pf+0w
[test]$ cat /proc/cpuinfo | grep name
model name : Intel(R) Xeon(R) CPU E5540 @ 2.53GHz
model name : Intel(R) Xeon(R) CPU E5540 @ 2.53GHz
model name : Intel(R) Xeon(R) CPU E5540 @ 2.53GHz
model name : Intel(R) Xeon(R) CPU E5540 @ 2.53GHz
[test]$ uname -a
Linux cs 2.6.18-308.16.1.el5 #1 SMP Tue Sep 18 07:21:07 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux
About 8 seconds per hash attempt with 512 megabytes, so it'd take 18 days to verify the initial download of a blockchain with 200,000 blocks.
ouch.
Basically everyone would have to run it through an electrum server of some sort.
I vote the name of the coin to be ElectrumCoin.
Hell the biggest reasons I don't believe feathercoin and chinacoin don't have a future is that who the hell is going to use something called a feathercoin, or a chinacoin? It sounds childish
dumb name, not appealing. Will fail.
As much as I hate to agree with you, He's right. Can you possibly consider changing the name to something more...professional? This could have some potential, but if the name is silly, it will die before the new year :\
Quick question, is there a CPU-mining program that can handle variable Scrypt rounds?
Edit: aside from the built-in miner, which is significantly slower.
Edit: aside from the built-in miner, which is significantly slower.
if everyone is using the same software ot mine, the fact that it is slower will be irrelevant, as noone will have the advantage.
Not if someone modifies the scrypt routines in cgminer to work similar to how it works in the built in yacoin miner. No contest.
I give it a day at most before that happens with this coin.
Quick question, is there a CPU-mining program that can handle variable Scrypt rounds?
Edit: aside from the built-in miner, which is significantly slower.
Edit: aside from the built-in miner, which is significantly slower.
if everyone is using the same software ot mine, the fact that it is slower will be irrelevant, as noone will have the advantage.
dumb name, not appealing. Will fail.
Interesting coin, let's see how its works
Watching
So you're going through with this ? Will it be a test that you kill later or will it stay ? I'm not going to stop my rig just "for the lulz" you know.
Jump to: