 Show Posts
|
|
Pages: [1] 2 »
|
|
1
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: [Ultracoin] [Est. Feb 2014] ~ ASIC Resistant & Ultrafast 6 Second Transactions!
|
on: April 15, 2015, 04:50:08 PM
|
|
Time: 2014-01-23 06:32:32 UTC nFactor: 9
Time: 2014-02-16 13:05:04 UTC nFactor: 10
Time: 2014-02-28 16:21:20 UTC nFactor: 11
Time: 2014-04-06 02:10:08 UTC nFactor: 12
Time: 2014-05-24 15:15:12 UTC nFactor: 13
Time: 2014-07-12 04:20:16 UTC nFactor: 14
Time: 2015-01-22 08:40:32 UTC nFactor: 15
Time: 2015-04-29 10:50:40 UTC nFactor: 16
Time: 2016-02-14 17:21:04 UTC nFactor: 17
Time: 2017-03-09 02:01:36 UTC nFactor: 18
Time: 2018-04-01 10:42:08 UTC nFactor: 19
Time: 2021-06-09 12:43:44 UTC nFactor: 20
Time: 2022-07-02 21:24:16 UTC nFactor: 21
Time: 2031-01-03 18:48:32 UTC nFactor: 22
|
|
|
|
|
2
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: ULTRACOIN 2.0 NEW FORUM ~ Asic proof and and Ultrafast Transactions 6 seconds !
|
on: September 06, 2014, 09:45:25 AM
|
We urgently a good working node list!
I am trying to sync my wallet and I canīt. Usually crashed immediately as it tries to sync.
I have the same issue.. Took me two days and got stuck at the last 10000 blocks.. I closed my wallet and restarted it, and its taking ages to sync.. here is my current peer list, just put: addnode=37.187.53.116:44100 addnode=anotheraddress etc in ultracoin.conf which is normally located in C:\Users\YOURUSERNAME\AppData\Roaming\Ultracoin 05:34:47  getpeerinfo 05:34:47  [ { "addr" : "37.187.53.116:44100", "services" : "00000001", "lastsend" : 1409996085, "lastrecv" : 1409996066, "conntime" : 1409968487, "version" : 70054, "subver" : "/Ultracoin:0.7.2/", "inbound" : false, "releasetime" : 0, "startingheight" : 611769, "banscore" : 0 }, { "addr" : "86.190.68.228:44100", "services" : "00000001", "lastsend" : 1409996067, "lastrecv" : 1409996068, "conntime" : 1409968493, "version" : 70054, "subver" : "/Ultracoin:0.7.2/", "inbound" : false, "releasetime" : 0, "startingheight" : 611769, "banscore" : 0 }, { "addr" : "198.50.132.97:44100", "services" : "00000001", "lastsend" : 1409996087, "lastrecv" : 1409996041, "conntime" : 1409968533, "version" : 70054, "subver" : "/Ultracoin:0.7.2/", "inbound" : false, "releasetime" : 0, "startingheight" : 611770, "banscore" : 0 }, { "addr" : "83.183.206.27:44100", "services" : "00000001", "lastsend" : 1409996066, "lastrecv" : 1409996066, "conntime" : 1409968539, "version" : 70054, "subver" : "/Ultracoin:0.7.2/", "inbound" : false, "releasetime" : 0, "startingheight" : 611771, "banscore" : 0 }, { "addr" : "50.149.30.188:44100", "services" : "00000001", "lastsend" : 1409996042, "lastrecv" : 1409996066, "conntime" : 1409968705, "version" : 70054, "subver" : "/Ultracoin:0.7.2/", "inbound" : false, "releasetime" : 0, "startingheight" : 611773, "banscore" : 0 }, { "addr" : "86.5.138.107:44100", "services" : "00000001", "lastsend" : 1409996067, "lastrecv" : 1409996038, "conntime" : 1409969053, "version" : 70054, "subver" : "/Ultracoin:0.7.2/", "inbound" : false, "releasetime" : 0, "startingheight" : 611783, "banscore" : 0 }, { "addr" : "74.91.71.140:54791", "services" : "00000001", "lastsend" : 1409996069, "lastrecv" : 1409996069, "conntime" : 1409971242, "version" : 70052, "subver" : "/Ultracoin:0.7.2/", "inbound" : true, "releasetime" : 0, "startingheight" : 460123, "banscore" : 0 }, { "addr" : "95.24.74.134:49562", "services" : "00000001", "lastsend" : 1409996067, "lastrecv" : 1409996068, "conntime" : 1409971463, "version" : 70054, "subver" : "/Ultracoin:0.7.2/", "inbound" : true, "releasetime" : 0, "startingheight" : 605326, "banscore" : 0 }, { "addr" : "91.158.77.183:44100", "services" : "00000001", "lastsend" : 1409996068, "lastrecv" : 1409996068, "conntime" : 1409972854, "version" : 70054, "subver" : "/Ultracoin:0.7.2/", "inbound" : false, "releasetime" : 0, "startingheight" : 611915, "banscore" : 0 }, { "addr" : "176.12.62.100:1406", "services" : "00000001", "lastsend" : 1409996067, "lastrecv" : 1409996067, "conntime" : 1409975083, "version" : 70054, "subver" : "/Ultracoin:0.7.2/", "inbound" : true, "releasetime" : 0, "startingheight" : 611974, "banscore" : 0 }, { "addr" : "123.203.61.197:61187", "services" : "00000001", "lastsend" : 1409996067, "lastrecv" : 1409996084, "conntime" : 1409976625, "version" : 70054, "subver" : "/Ultracoin:0.7.2/", "inbound" : true, "releasetime" : 0, "startingheight" : 612027, "banscore" : 0 }, { "addr" : "31.220.0.11:44100", "services" : "00000001", "lastsend" : 1409996067, "lastrecv" : 1409996061, "conntime" : 1409978751, "version" : 70050, "subver" : "/Ultracoin:0.7.2/", "inbound" : false, "releasetime" : 0, "startingheight" : 286971, "banscore" : 0 }, { "addr" : "82.2.169.186:49314", "services" : "00000001", "lastsend" : 1409996067, "lastrecv" : 1409996068, "conntime" : 1409990131, "version" : 70054, "subver" : "/Ultracoin:0.7.2/", "inbound" : true, "releasetime" : 0, "startingheight" : 612481, "banscore" : 0 }, { "addr" : "113.253.135.99:62041", "services" : "00000001", "lastsend" : 1409996067, "lastrecv" : 1409996004, "conntime" : 1409991242, "version" : 70054, "subver" : "/Ultracoin:0.7.2/", "inbound" : true, "releasetime" : 0, "startingheight" : 594895, "banscore" : 0 }, { "addr" : "94.23.165.69:36589", "services" : "00000001", "lastsend" : 1409996067, "lastrecv" : 1409996067, "conntime" : 1409992520, "version" : 70054, "subver" : "/Ultracoin:0.7.2/", "inbound" : true, "releasetime" : 0, "startingheight" : 592164, "banscore" : 0 }, { "addr" : "169.234.250.22:61533", "services" : "00000001", "lastsend" : 1409996067, "lastrecv" : 1409996014, "conntime" : 1409995607, "version" : 70054, "subver" : "/Ultracoin:0.7.2/", "inbound" : true, "releasetime" : 0, "startingheight" : 612659, "banscore" : 0 } ] |
|
|
|
|
4
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN] [ASIC-RESISTANT] UltraCoin (UTC) - Ultrafast 6 second transactions!!
|
on: May 24, 2014, 05:47:45 AM
|
WALLET DEVELOPMENT UPDATE:
Okay, so our community chat session was wildly successful and we all agreed to implement the following: NFACTOR - 1 less from what it is now, effective for 12 months
POS - 7 day POS system at 5.2% per year, which equates to 0.1% per 7 days. Max time = 30 days
No change to # of coins or ratio for now The POS modifications are implemented and being tested. More news to follow on this. Expect an update shortly! NFACTOR is actually far more complex than originally thought. Turns out dialing back could have severe, potentially crippling, repercussions. We are investigating how to work through this, if at all possible. That being said: NFACTOR will change as scheduled this Saturday, May 24th, 2014 @ 03:15:12pm UTC. We cannot risk crippling the entire blockchain in an attempt to force this revision. When the NFACTOR changes, please use the config generator to update your miners! http://ultracoin.net/configgen_raw.htmlTo summarize, the wallet update will, for now, include only the POS modifications, NFACTOR changes are being discussed, and NFACTOR will shift this Saturday. We will keep you all posted otherwise. Thank you for your continued support! I'm not sure why the N-factor change has to be so complicated. I'm getting ready to go home for a long, long weekend but, if I remember correctly, there is just a convoluted function that has a bunch of arbitrary calculations that result in a block heights to change the N-factor at. The point is, I thought it just returned nFactor and all the other things that used that value derived it from that function. Why couldn't you just comment that all out and hardcode in the return value to be the N-factor you want it to be, aka 12? Obviously, this would be a mandatory wallet update. No ones wallet would work on the old N-factor so you'd have to set it at a date in the near future. well there is the factor of changing the wallet software, a mandatory update, and a forced date for transition. However there is also mining software, scrypt-jane/scrypt-chacha mining software also uses the same formula to determine the n-factor when mining. Custom revisions of each of the mining programs used will need to be ready for this change as well. Coordinating all of this is a nightmare in the crypto world, some people don't listen some don't understand and things just get complicated. That is what I said, I'll just copy it below and save myself the trouble of explaining it. // ultracoin: increasing Nfactor gradually
const unsigned char minNfactor = 4;
const unsigned char maxNfactor = 30;
unsigned char GetNfactor(int64 nTimestamp) {
int l = 0;
if (nTimestamp <= nChainStartTime || fTestNet)
return 4;
int64 s = nTimestamp - nChainStartTime;
while ((s >> 1) > 3) {
l += 1;
s >>= 1;
}
s &= 3;
int n = (l * 170 + s * 25 - 2320) / 100;
if (n < 0) n = 0;
if (n > 255)
printf( "GetNfactor(%lld) - something wrong(n == %d)\n", nTimestamp, n );
unsigned char N = (unsigned char) n;
//printf("GetNfactor: %d -> %d %d : %d / %d\n", nTimestamp - nChainStartTime, l, s, n, min(max(N, minNfactor), maxNfactor));
return min(max(N, minNfactor), maxNfactor);
} The wallet passes the Timestamp to the function, subtracts the start time to get the total length of time the coin has been producing blocks, does some funky arbitrary math, then returns the N factor, assuming it's between 4 and 30. If the value is outside that range ( 4> x >30), then it returns 4 or 30. That's it. Every call to get the N-factor in every other part of the wallet uses a call to GetNfactor. For a short term fix, you just comment out the entire block of code, and write "return 12". Then all the function calls remain the same and you are just forcing a set N factor until you decide on a proper schedule. I wouldn't imagine the mining software would care that it is hardcoded. I'd need thirtybird to go over that though, as I really don't know a ton about that side of it. I looked at his YACminer code and there are calls to getNFactor, but I got tired of tracking down where they were going to. He's much better at this stuff than me anyway so he can probably tell me whether there is something wrong with what I said above as well. The mining software uses basically the same function, at a minimum you would have to set nfmax 12 so the nfactor change is overridden. That still leaves coordination, and the fact that there are people that don't listen, don't understand, and a social mess. Changing the code itself is not a huge hurdle, setting the transition time, the mandatory update, and mining changes so people don't go into riot mode is complicated and not to be taken lightly. If the transition window, the timing and communication are not carefully considered and clearly stated in the right way a change of this type could kill a coin, or at least severely damage it. (yes much more than you may think the current problems are) Some simple changes are very complicated to actually implement. There is also the fact that some coins will have been mined at a higher nfactor, how that affects the blockchain when lowering it I do not know, but may require much more work on the wallet software to make sure the transition does not invalidate any coins during the change. |
|
|
|
|
5
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN] [ASIC-RESISTANT] UltraCoin (UTC) - Ultrafast 6 second transactions!!
|
on: May 23, 2014, 06:33:54 PM
|
WALLET DEVELOPMENT UPDATE:
Okay, so our community chat session was wildly successful and we all agreed to implement the following: NFACTOR - 1 less from what it is now, effective for 12 months
POS - 7 day POS system at 5.2% per year, which equates to 0.1% per 7 days. Max time = 30 days
No change to # of coins or ratio for now The POS modifications are implemented and being tested. More news to follow on this. Expect an update shortly! NFACTOR is actually far more complex than originally thought. Turns out dialing back could have severe, potentially crippling, repercussions. We are investigating how to work through this, if at all possible. That being said: NFACTOR will change as scheduled this Saturday, May 24th, 2014 @ 03:15:12pm UTC. We cannot risk crippling the entire blockchain in an attempt to force this revision. When the NFACTOR changes, please use the config generator to update your miners! http://ultracoin.net/configgen_raw.htmlTo summarize, the wallet update will, for now, include only the POS modifications, NFACTOR changes are being discussed, and NFACTOR will shift this Saturday. We will keep you all posted otherwise. Thank you for your continued support! I'm not sure why the N-factor change has to be so complicated. I'm getting ready to go home for a long, long weekend but, if I remember correctly, there is just a convoluted function that has a bunch of arbitrary calculations that result in a block heights to change the N-factor at. The point is, I thought it just returned nFactor and all the other things that used that value derived it from that function. Why couldn't you just comment that all out and hardcode in the return value to be the N-factor you want it to be, aka 12? Obviously, this would be a mandatory wallet update. No ones wallet would work on the old N-factor so you'd have to set it at a date in the near future. well there is the factor of changing the wallet software, a mandatory update, and a forced date for transition. However there is also mining software, scrypt-jane/scrypt-chacha mining software also uses the same formula to determine the n-factor when mining. Custom revisions of each of the mining programs used will need to be ready for this change as well. Coordinating all of this is a nightmare in the crypto world, some people don't listen some don't understand and things just get complicated. |
|
|
|
|
9
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN] [ASIC-RESISTANT] UltraCoin (UTC) - Newly Launched
|
on: March 10, 2014, 10:38:07 PM
|
--snip-- There are a few CPU miners. One is listed on the Ultracoin forum too. However, there is one specific miner that is best and most up to date. -Manual N parameters for multiple coins -X86 and 64bit formats -Stratum pool capable -Scrypt optimizations for Scrypt-Jane https://github.com/thirtybird/cpuminer/releases/This is the absolute best CPU miner out there currently. I believe it has all the needs being asked for. Even though I'm not actively posting here; I still hate to not help if I can.  Thanks Prot UftrEhcPx5hTY4YJvSziPi13dfZT9nXSqw good find, looks like they just recently added the min/max and starttime parameters. +1 internets to you sir |
|
|
|
|
10
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN] [ASIC-RESISTANT] UltraCoin (UTC) - Newly Launched
|
on: March 10, 2014, 04:37:21 PM
|
Bumface, is ziggy doing anything at all about the CPU mining problem?
what problem? We don't have an independent CPU miner that can be used for pools. Some of the patched CPU miners for a couple other scrypt-jane coins have a close enough start time that they will work while our n-factor overlaps with theirs. The main issue is getting one set up for ultracoin and having compiled versions available. |
|
|
|
|
11
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN] [ASIC-RESISTANT] UltraCoin (UTC) - Newly Launched
|
on: March 10, 2014, 02:16:05 PM
|
I would like to include the NFactor count down in block explorer. I remember someone post kind of JAVA code for generating NFactor check points before (not the mm/dd/yyyy format in official website but in unix time stamp) Searched for a while but can not find it. Could the author pls post again?  Some of the things that I think bumface/ziggy needs to do from my point of view:
1. Explain more about the N-factor. MANY people does not know about this.
We need to know the dates of when the N-factor changes for UTC and what that implies.
It's a BIG part of UTC so I don't understand how this is not explained on the OP from day 1.
bumface, you told me you'll speak to ziggy about this 3 days ago? What happened?
I'll post my N-factor timetable again, derived from the code in https://github.com/ziggy909/ultracoin/blob/master/src/main.cpp starting at line 994. I made a little javascript loop with the same calculations starting with Ultracoins sj-time. var sjtime = 1388361600;
var Ntime;
var l = 0;
var seconds = 0;
var s = 0;
var n = 0;
var N = 0;
var last = 8; // no output until N=9
while (seconds < 12884901888)
{
seconds += 1;
s = seconds;
l = 0;
n = 0;
N = 0;
while ((s >> 1) > 3)
{
l += 1;
s >>= 1;
}
s &= 3;
n = (l * 170 + s * 25 - 2320) / 100;
if (n < 0) n = 0;
N = Math.floor(n);
if (N > last)
{
last = N;
Ntime = new Date(sjtime*1000 + seconds*1000);
//print("N-Factor :" + N + " significant digits :" + l + " leftovers :" + s + " raw N :" + n + " Seconds from start :" + seconds);
print("N-Factor :" + N + " Date :" + Ntime.toUTCString());
}
} This is the output (i used a javascript console bookmarklet in firefox, it shut down the script before it got past N-factor 17) N-Factor :9 Date :Thu, 23 Jan 2014 06:32:32 GMT
N-Factor :10 Date :Sun, 16 Feb 2014 13:05:04 GMT
N-Factor :11 Date :Fri, 28 Feb 2014 16:21:20 GMT
N-Factor :12 Date :Sun, 06 Apr 2014 02:10:08 GMT
N-Factor :13 Date :Sat, 24 May 2014 15:15:12 GMT
N-Factor :14 Date :Sat, 12 Jul 2014 04:20:16 GMT
N-Factor :15 Date :Thu, 22 Jan 2015 08:40:32 GMT
N-Factor :16 Date :Wed, 29 Apr 2015 10:50:40 GMT
N-Factor :17 Date :Sun, 14 Feb 2016 17:21:04 GMT The next N-factor increase should be on the 28th of this month. there is this that i posted, however the javascript code will kill your browser and is not suitable for a web page, the best way to really do this would be to take the original chart and add 1388361600 to the first number in each range, to get javascript to display a unix timestamp as a date you need to multiply by 1000, javascript goes by miliseconds. i can probably put together something that just puts the numbers into an array and spits out the timestamp or date for the next n-factor if you would like. |
|
|
|
|
12
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN] [ASIC-RESISTANT] UltraCoin (UTC) - Newly Launched
|
on: March 09, 2014, 09:51:33 AM
|
is there anyway we can make our own way to purchase UTC with the USD?  ? first off I find it crazy that coinbase and localbitcoins are the 2 best ways to get introduced into cryptocurrency to begin with for people in USA. I know somebody said our own exchange, and that seems like a lot of work. I'm talking something simpler. Just quick easy way to purchase UTC with USD that we can market that to USA consumers. Jeez even a buy button in the wallet idk. any thoughts? usd/eur-utc Yes but you need to transfer BTC to that site first... I cant just deposit USD on that site freely. I would have to purchase on coinbase, transfer to crypto-trade, sell btc, than buy utc with usd. That is ridiculous. Why cant there be a way with my bank account to purchase this extremely fast UTC coin directly?? a coinbase for utc if you will maybe The main problem is US banks, and regulations for any kind of currency exchange. There's a reason there are not 100's of places where you can easily buy crypto, once you get into the financial sector the rules and regulations are complex and difficult to deal with. Probably similar with other nations as well, but it is a lot of bureaucracy and red tape to go through. |
|
|
|
|
14
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN] [ASIC-RESISTANT] UltraCoin (UTC) - Newly Launched
|
on: March 03, 2014, 07:41:28 AM
|
What CPU-Miner to use for UTC?I'm Using the CPU Miner which is used for Velocitycoin -> https://bitcointalk.org/index.php?topic=390767.0, depending on the age of your CPU u've to try out those different Exe's avx is the newst one. If this works for u, UTC donations are welcome: Ui1KS7wJjuUbq66fNTuUpeAkJ8k2YAbrkg :-) cheers M The velocitycoin cpu miner has a start time about 1 week ahead of ours, it will work "most" of the time for ultracoin just fine. around 1 week before our N-factor changes it may have some problems, but it will work right now, and you can see what hash rate you can get now, and at the next N-factor change as well. I'm sure someone can compile this for windows adjusting the start time hardcoded in scrypt-jane.c at some point. |
|
|
|
|
15
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN] [ASIC-RESISTANT] UltraCoin (UTC) - Newly Launched
|
on: March 01, 2014, 09:56:57 AM
|
Bumface, as I'm no longer sure you technically know your coin, please bring Ziggy to answer these questions:
1) What is the idea behind so quick changes of nfactor. We do not have asics yes, this makes only confusion. Is it possible to change it? Are you willing to do that?
2) If I understand PoS well, it will fire after year. Again, what is the reason? Wouldn't it be more attractive to have monthly PoS? Is it possible to change it? Are you willing to do that?
If anything from above is part of the strategy of this coin, I'm ok with it. But please confirm it. Btw I'm not troll, I'm mining from the beginning and I'm bagholder from 90, 70, 50 and 25.
I can help a bit with the N-Factor, it is the "standard" timing for scrypt-jane coins that have been made. It could be changed, however a custom miner and or custom patch for cgminer, cudaminer, and any cpu miner from other coins that happen to work because their start time is close enough to ours. As for how the original timing for scrypt-jane N-factor changes was done, nobody knows other than the person that did it. The following blog post describes this fairly well http://www.holynerdvana.com/2014/02/everything-you-wanted-to-know-about.html |
|
|
|
|
18
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN] [ASIC-RESISTANT] UltraCoin (UTC) - Newly Launched
|
on: February 26, 2014, 07:31:41 PM
|
New business idea: assurance against getting goxed. I'm sure we would have much customers now. What the hell is goin' on up here? Captain, the exchange is taking on lag. Then pump it out, mister. You're the bloody engineer. We can't get in. The server took a hit, and the network is wedged tight. Hiko's cuttin' it now. Jesus Christ, the crypto! We gotta cut that damn thing loose! That's not an option, Mr. Baker. Skipper, should I head for the breach? I need an answer now. I'm losin' her. Prices down 125%, Captain! Captain, take a look! That site goes down, we go down with it! Well, that's a chance I'll take. I'm cuttin' it loose. Stay away from that exchange, mister. I mean, what's so precious about your goddamn exchange, Captain? The exchange is mine. I've leveraged everything I own against it, and it's not insured. Christ, what's the matter with those people? |
|
|
|
|
19
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN] [ASIC-RESISTANT] UltraCoin (UTC) - Newly Launched
|
on: February 21, 2014, 08:45:54 PM
|
N-factor details added to the mainpost (source:nitropool)
Actually the credit goes to LHM for doing the hardwork, he has done a marvelous job. We copied his work and added some of our conclusions. ahh, thats wonderfull, LHM: your work is appreciated Glad to help out, the wallet source seems to call that function with the timestamp on the newest block so the timing may be off by a minute or so, but it should be pretty close. |
|
|
|
|
20
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN] [ASIC-RESISTANT] UltraCoin (UTC) - Newly Launched
|
on: February 21, 2014, 05:29:34 AM
|
good work thanks, I was starting to think about swapping coins, as my wattage vs coins generated are no longer paying off how ever I no longer have accurate way of knowing what power my current consumption is as its very hot weather and most GPU's idling under 500 mhz @ 70+ deg ) 71.0 c 100% 260 Kh/s 103263 / 2266 2.15% 290 Series 85% 654.47 Mhz 70.0 c 100% 200 Kh/s 80850 / 1626 1.97% 290 Series 85% 516.15 Mhz test rig on watt meter 460 kh/s 310 watts ( excluding PC power GPU's only ) full load is around 800 watts total , I need about 2 coins per kw watt to break even 78.0 c 100% 310 Kh/s 121402 / 5097 4.03% 290 Series 85% 840 Mhz 76.0 c 100% 270 Kh/s 105589 / 4792 4.34% 290 Series 85% 866.15 Mhz sample of average GPU's running under 80 deg / air temp 44 deg assuming around 290 watts +-10 watts per GPU at those speeds coins are really dropping off, I am hoping more big miners drop out on nxt NFactore change due to HW errors  ( more coin for me ) It is easier to adjust settings if you know when you need to. I'm mining with a couple laptop GPU's and my desktops crusty HD 5450, started at 55kh/s and i'm down to 35kh/s total now. I have mined 51 UTC so far, mining for fun more than profit. |
|
|
|
|
