Just tried them on a Mac Mini with Snow Leopard and a single Block Erupter USB, give the USB timeout errors: [2013-09-17 14:00:28] AMU0: TIMEOUT GetResults took 1999ms but was 100ms
[2013-09-17 14:00:30] AMU0: TIMEOUT GetResults took 1999ms but was 100ms
[2013-09-17 14:00:32] AMU0: TIMEOUT GetResults took 1999ms but was 100ms
[2013-09-17 14:00:34] AMU0: TIMEOUT GetResults took 1999ms but was 100ms
[2013-09-17 14:00:36] AMU0: TIMEOUT GetResults took 1999ms but was 100ms
[2013-09-17 14:00:37] Stratum from pool 0 detected new block
[2013-09-17 14:00:38] AMU0: TIMEOUT GetResults took 1998ms but was 100ms Hardware is ok with bfgminer compiled from github. |
|
|
|
|
I don't really know the answer, at a guess I think a lot of people have bought LTC hoping that it will rise in value when Gox eventually launches it. This has caused a drop in LTC trade volume as people hang on to it, also a liquidity crises for all coins as people are in hold mode rather than trade mode. Like I say, just a guess, I might be totally wrong.
|
|
|
|
- return GetNetworkHashPS(params.size() > 0 ? params[0].get_int() : 576);
+ return GetNetworkHashPS(params.size() > 0 ? params[0].get_int() : 48); It's a worthwhile change, if it had been done earlier you wouldn't have had the other mandatory updates. Better late than never. Amazing, it's not like I didn't predict this would happen or anything. ~BCX~ That's not the actual diff calc code, just the approximation for stats, but you obviously get the point, by only going back something like 48 blocks instead of 576 it makes the 12 block re-targets far more relevant than 576 block history, which could be several hours or days old depending on how the hash rate is. My gut feeling is that 48 block history is about right for GME, because the base hash rate is virtually unknown, it becomes more of an art than a science. As the coin matures and finds a core of miners some fine tuning can be done later. |
|
|
|
No, I am just completely fed up of the utter lack of support for the coin. It really doesn't matter how I tweak it, if there is no real miner support it'll make very little difference to the overall result.
You need to STOP tweaking immediately. a new nark fork every other week is murder to a coin's support. If there is lack of support for the coin, it is not the fault of the people that refuse to support it, you need to give them a reason to. Right now, GME is looking wavery as all hell because ther is a new mandatory update every couple of weeks. Every time one of those needs to be released, you're essentially announcing to everyone that the system was flawed before. It's difficult to gather support for a coin when you're essentially giving the message that it's got all kinds of problems that need to be constantly addressed. To create support for the coin we need infrast5ructure that accepts this coin. More effort needs to be put form on that than tweaking the coin, because even a perfect coin is going to have no support if no one will take it as money. That being said, I'll be opening up a Minecraft server that will accept GME/LTC/ and possibly BTC as payment for server access and in-game resources. This will eventually include a web-based marketplace where players can offer up their resources for sale. We may also offer up Minecraft Game Codes for crypto as well if there's interest. - return GetNetworkHashPS(params.size() > 0 ? params[0].get_int() : 576);
+ return GetNetworkHashPS(params.size() > 0 ? params[0].get_int() : 48); It's a worthwhile change, if it had been done earlier you wouldn't have had the other mandatory updates. Better late than never. |
|
|
|
How flooding the market with $100 ASICs suppose to save the mining community?
Because it Lets the free market work its magic. If they can't match the price they fold. |
|
|
|
Very interesting and I am interested to support the effort if the details all line up.
My biggest general concern is "are we too late" when it comes to keeping up with folks who are basically at 28nm now, and moving to smaller soon...
Lol, not much smaller than 28nm atm. The ROI on anything smaller will be terrible, way to bleeding edge. |
|
|
|
Ah, the socialist solution to ASIC!
I'm in, if this isn't just a pipe dream. But what's to stop unknown groups from buying huge chunks of this proposed new hashing power? Wouldn't this just be another opportunity for the well-funded profiteers to make even more money?
Make a finite batch and have a lottery for each one, make it random distribution for fairness. One persons money then becomes as good as anothers. |
|
|
|
|
Is there an ASIC on the market which I could order today, that would return as much or more BTC as I would have to pay for it in say under 6mths of mining? I am not sure that there is anymore.
The margins are too high, there is nothing worth buying atm. The ASIC land rush is over until the manufactures start delivering on time, and charging sensible prices.
BTC network just hit 1PH/s and no 28nm gear yet. Wait till that hits, it will be 2,3,..4PH/s in no time.
|
|
|
|
oo go buy a couple thousand of dollars from BFL. They say they will ship.
There is nothing in the BFL range that will earn back the BTC you pay for it. |
|
|
|
It's not a theory it's fact. If you don't understand the maths behind it then you really shouldn't continue trying to argue against it.
Oh I understand the theory alright, I have looked though your code, and I also understand what the block chain timestamps are telling me. Block 66792 timestamp 1379244162 Block 67368 timestamp 1379250767 That's 576 blocks in 6,605sec or 11.47sec per block, an easy 576,000 coins. Good luck with your roller coaster I am out of here. |
|
|
|
You clearly don't understand the way it works. The average block time is calculated over the last 576 blocks which under perfect circumstances would be 24 hours worth of blocks. Let me give you an example:
I'll start with block 67,000 as it's a nice round number and the difficulty was still falling at this point. The timestamp of this block was 1379249098 (Sun, 15 Sep 2013 12:44:58 GMT). The block 576 blocks behind this (66424) had a timestamp of 1379003057 (Thu, 12 Sep 2013 16:24:17 GMT). now already you must be able to clearly see that this is well over 24 hours. It's actually 4 hours shy of 3 days.
The target block time in GME is 2.5 minutes (150 seconds) so lets see what the average is between these 2 points:
1379249098 - 1379003057 = 246041
OK so there were 576 blocks so lets divide it by that number.
246041 / 576 = 427.15~
So there you have it. The average block time over the span of those 576 blocks was 427.15~ seconds per block which is over 2.84 times what it should be hence the difficulty continues to fall until this number is under 150 at which point it reverses.
If there were more than a few people consistently mining it instead of jumping ship the moment the difficulty went too high then the coin would find a sweet spot but all anyone cares about is what coinchoose says is the most profitable coin to mine at that specific moment.
How does that theory explain why the difficulty was well below 1 for several thousand blocks of high hash rate when it's only supposed to be a 576 block average? GME roller coaster just fed millions of coins to some UNKNOWN address in minutes. I would call that an exploit. You don't just suddenly drive at 100mph down the motorway because you spent an hour stuck in crawling traffic. The function of the diff adjustments is to keep the block time as close to 2.5min as possible, not to appease some 24hour average by having wild swings between seconds and almost an hour per block which is what the last few blocks have been. 67781 2013-09-15 21:20:40 67780 2013-09-15 20:25:40 67779 2013-09-15 19:31:04 |
|
|
|
Maybe I missed it or not.. did your batch 1 ship yet?
No it's not November. |
|
|
|
GameCoin is not under attack, it just went to the top of coinchoose in a big way. When I first looked at the page the profitability was over 4000%.
People can't be bothered mining GameCoin when the difficulty is higher so the average time per block (calculated over 576 blocks) is much longer than 2.5 minutes so the difficulty will keep falling until the tipping point is reached at which point it reverses. Now the opposite is true. The difficulty will just keep going up until the average over the last 576 blocks is 2.5 minutes.
If people don't care enough to continue mine it so that it can find a sweet spot, this pattern will just keep repeating. if you want it to stabilize, stop coinchoose watching and continue to mine it.
You must be joking, I sat there for about half an hour watching the hash rate go up, and the difficulty go down. Explain that? There records are all there in the block explorer for the world to see. The reason it suddenly leaped up on Coinchoose was because of the crazy falling difficulty. |
|
|
|
Stop running you mouth then!
Give up with the attitude welcome to the ignore list. Meanwhile I would say GME has just been attacked again with low diff injections, most likely someone solo so the destination shows as UNKNOWN on http://gme.p2pool.nl/chain/Gamecoins I notice that p2pool blocks also come up as UNKNOWN there. Normal pool blocks fill in the address. The diff stopped falling about block 67258 where the chain looks a bit messy. 3 forks? |
|
|
|
I really hate you hoppers and jumpers and multi pool type miners! Come in here with your fucking opinions and shit about the coin, yet don't mine it when it needs you the most!
Be loyal to the coin or just STFU!!!!
I refuse to miner GME anymore, it's always under attack. (Or way off block time) |
|
|
|
|
We seem to have runway low diff again.
0.07584385 and falling. I suspect a time warp attack from a solo miner, and fork.
|
|
|
|
it may be any more than tompool can do, But it does not do GME ANY favours. so it should stay off
You are nothing but a troll aren't you, you have no idea when tompool was even last on GME, you just want to promote your own pool by trying to discredit the pools that actually helped when the coin was relaunched. Welcome to my ignore list. |
|
|
|
i agree with bcx for once. another thing which needs to be done is tompool needs to keep off GME. a stable low hash is far better than a 2 min spike in the hash
You realize that tompool is only like 26Mh/s which is tiny. There are people with 10 times that jumping on the coin. There is no way tompool could get the coin up to 3.1 diff that it is at currently. Work it out first before you are critical. actually YOU need to work it out before being critical. tompool themselvs have said on their website that the multipool will occasionally switch to GME aside from the static GME mining,The mulipool should not switch to gme period! its a chain reaction which will only affect gme not benefit it FFS It's pretty obvious that you open your mouth before looking up how many MH/s you need to have before getting to a particular difficulty figure tompool is not capable of achieving more than about 30MH/s On average it takes (difficulty * 2^32 hashes) to solve each block, so to get to 3.1 diff it means there were 3.1* 2^32 hashes in a 2.5min period, which is many times more than tompool can do. |
|
|
|
According to Localbitcoin.com:
I can sell my BTC for cash locally for (best price) $117.xx
I can sell my BTC online for (best price) $124.xx
I can buy BTC locally for cash $145.xx
I can buy BTC online for (best price) $135.xx
the going rate according to 50BTC is US$125.76
so you can see that we have to pay about $11 / BTC in fees (about 7.3%).
Acquiring $1740 in BTC to buy 4 boards and a back plane will cost me over $150 in BTC fees.
I'd much rather pay Paypal fees and feel comfortable about the transaction.
I see the excessive fee gouging as one of the things holding back on more use of BTC. (used to be the same problem for gold bullion most places).
Why are you carrying on like a nutter? Has somebody actually said there will be no Paypal ordering on future board purchases? |
|
|
|
|
My confirmation emails for withdrawal are not arriving, I did a resend half a dozen times nothing, opened a support ticked and the confirmation for that arrived in about 5 seconds. I have been watching the mail logs and there are no connection attempts to my mail server each time a click resend on Cryptsy. I have recevied dozens of withdrawal confirmations in the past.
|
|
|
|
|
Show Posts
