The much touted website is up on a server and needed a few minor tweaks, but honestly, I was pretty much burnt out when lynos gave me a "rough draft" of how he would do it: http://lynortis.com/sxc-t1/ I don't know about you, but it blew my mind. May affect the wow factor, but less nipples on the frontpage, until you click an 18+ button would be better.
|
|
|
Go for the Haswell, it has the new AVX2 instructions that runs poolers cpuminer almost twice as fast as the "old" AVX intels, when mining other coins than XPM.
AMDs support for AVX is slow.
|
|
|
Simpsons?
""That fellow at Radio Shack said I was mad... well who's mad now?"* *TV Show
|
|
|
PXjsBxo1mfgF3L7S2SyBXHExC6QFRAeThN
Thanks!
|
|
|
C6swAvKQ67R5ntPy4Z2nfQEYECrh5esJUA 1. Registered 2. Registered and mining at http://cdc.coinmine.pl3. Voted Thanks! /EDIT, added pool name since I may have chosen the wrong pool for the giveaway, but it is active...
|
|
|
C73KTr86BUhPJfmfeupfiWNaPPHxU5KWtT
Thanks
|
|
|
I am at block 9332 with the 1.1.4 wallet. According to the previous post, block 9333 should be the valid one?
Trying to solomine, but I guess its pointless?
Using the *.conf file from the first page.
|
|
|
Just changed it, after re-reading the rules...
|
|
|
, Hoping that the country letters are included in the contest. Any bonus for being a smartass? /EDIT Changed to comma since it is considered a character according to the rules. 5XvKi2jwNfY9v81jFbboU67FkqAm6fJ3ba
|
|
|
ZShQ9kpQrEzQmRbGjuNP2cvzcpVKrMkUWc
|
|
|
JBv8NucRgtzQXe11jqFiVm3WP1eFSQXRHC
Thanx
|
|
|
JAZ9MHMNURoM8zt81UpFkNaeEWzqeauS14
Thanks.
|
|
|
Tried memory between 900-1450, no big difference. Running driver 13.8 since it also is a gaming rig and 13.8 is the best for Crossfire games.
Are the benchmarks made with N=6 or earlier? Hashrate halves at each N-change.
EDIT: Giving up on solo mining, after an hour I got 2 coins and 2 rejects, need a pool.
|
|
|
Getting about 1.4Mh/s on a 7970 running at a low 900Mhz. Getting no coins after a few minutes of testing though. Using: ybcminer --scrypt --thread-concurrency 8192 -I 13 -g 2 -w 256 --lookup-gap 2
"difficulty" : 1.04747063, "networkhashps" : 70542565, "Nfactor" : 6, "N" : 128, "powreward" : 1.00000000
EDIT, Just got 2 coins and a reject after 10 minutes on 3x7970.
|
|
|
Thanks for the pool! I hope that this will improve soon: "Pool Efficiency: 0.00%"
|
|
|
Watching the effects of the latest N change I noticed a few things A. - Even at a normalized hash rate (thanks canoe) - a lot of people bailed on mining YAC B. - Block time mean quintupled - we went from 55 seconds or so to over 250 - it could still be a few more days before we get back down to 1 minute. C. - Because of B, the transaction times crawled to a halt to fully validate D. - The difficulty is still plunging to catch up to the loss of hashpower (both from N change and folks stopping mining)
The following is suggested based on the possibility of a future where this coin is widely accepted and what the end user experience would be like trying to make a transaction shortly after an N increase. That person, would have to wait ~30+ minutes just to get the first 8 confirmations. This is not the type of experience an end user user would likely tolerate without a high level of frustration.
Based on this, I would like to propose a change that adjusts the difficulty downward at the same time as N increases in an effort to keep block times close to their target in the days that follow. In a no-loss scenario, an N increase halves the total hashpower, so I propose it also halves the difficulty at the same time.
Another big problem was that everybody was using a new GPU miner, that crashed at the N change. It took a couple of days to get a few updates to get it running at the new normal speed and it needed some tweking. I noticed that my miner crashed and the pool lost 95% of the hash rate at the same time. Hopefully this will not happen again...
|
|
|
1ACXu6obKbS1YFtWKHfiQBeVU24MBnTX8e
Thanks.
|
|
|
|