as far as i know
in short: device shows you the hashrate including hardware errors
pool shows only matching hashrate.
thats the discrepancy
Yes, but when I switch off the Turbomode and let it run at nominal 800 GHs, then eligius shows only about 650 GHs... so not sure what's happening here... it's like I have to let the devices run in Turbomode so that I reach the nominal 800 GHs at all. What's your ping time to Eligius? If it's high you could be losing shares. If it is due to high response times and not just your internet pipe then I'd try a local P2Pool public server - http://p2pools.org/btc - Although P2Pool can take up to 72hrs to show your correct hashrate. hm, eligius.st doesn't let me ping it, I get 100% packetloss when I do a ping on a computer that is in the same network like my two miners. but doesn't that have to do with the fact that they are being DDOS allthetime lately? |
|
|
|
did they paid for your shipping fee returning the miner to them?
I've email them and no replies yet.
No, they haven't yet. I will ask them again... but at the moment I am just trying to figure out how to setup the machines the best way so they hash with optimum. |
|
|
|
hm, the turbomode of the second 800GHs coindesk seems to work much better....
that means ? do you know the color of the modules ? green or red ? which work better ? I will make fotos soon, please wait... |
|
|
|
|
hm, the turbomode of the second 800GHs coindesk seems to work much better.... but I am not sure, I need to run them for a day to get better averages.
|
|
|
|
as far as i know
in short: device shows you the hashrate including hardware errors
pool shows only matching hashrate.
thats the discrepancy
Yes, but when I switch off the Turbomode and let it run at nominal 800 GHs, then eligius shows only about 650 GHs... so not sure what's happening here... it's like I have to let the devices run in Turbomode so that I reach the nominal 800 GHs at all. |
|
|
|
UPDATE: today I already recieved a replacement for the damaged device. UPS was very fast. Took them not even 24 hours. Thanks to bitmine for resolving this problem fast. New device is happily hashing away together with its 800 GHs twin: http://eligius.st/~wizkid057/newstats/userstats.php/16bWt62xq5rmQuGscq7L7GuZfYmZkkvN5xWhat I don't get is why eligius shows the devices hashing with 800 GH/s each, when in fact I am letting them run in turbomode of about 950 GHs? Can anyone explain the discrepancy here? Thanks. |
|
|
|
- Up to date news concerning our products, firmware releases, and many other bitmine and bitcoin-related news and new ways to interact with us and give us your feedback.
Thanks giorgiomassa. So are you currently working on a new firmware to increase the rather weak turbomode of the coindesks? I mean it doesn't really deserve to be called turbomode like it is now. I am asking since you are still advertizing the turbomode as a 50% increase on your online shop. Wouldn't it be fair to call it "up to 15%" until better firmware really delivers what is promised? Is a firmware update even going to help here, or is this completely hardware dependend? Would be glad if you could give us your estimation. |
|
|
|
|
Addition: I got a followup email by antonio, this time they will use UPS to send the device, since last time with FedEx the device was damaged.
Neat!
|
|
|
|
Update about my damaged device.
Yesterday I called bitmine, and they said they couldn't yet review the damaged device, so they can't give me an update about how they will proceed.
Today I tried to call them and waited for 30 min on the line. Then I hung up. An email I wrote afterwards has not yet recieved any answer.
It's embarassing.
So, today they answered my email: Dear Mr. XXXXXX,
We are sending you a replacemente device today. Sorry for your trouble, this one hopefully will work nicely.
Best regards,
Bitmine AG, Bitmine.ch This is great, bitmine. Thanks. |
|
|
|
|
Update about my damaged device.
Yesterday I called bitmine, and they said they couldn't yet review the damaged device, so they can't give me an update about how they will proceed.
Today I tried to call them and waited for 30 min on the line. Then I hung up. An email I wrote afterwards has not yet recieved any answer.
It's embarassing.
|
|
|
|
Make sure you have at least Sexcoin Wallet / Client Version 0.6.4.4!
Check. ....the project finally got some traction and 2014 is the Do or Die year for Sexcoin.
Not just Sexcoin... 2014 is the Do or Die year for ALL altcoins. (except maybe the ones who are silently being merge mined with Bitcoin) |
|
|
|
I've read somewhere that Mazacoin is theoretically merge-mineable.
Mazacoin states on their main website that it is merge mineable, but I have not found any mining pool that provides merge mining BTC with MZC. |
|
|
|
how deep will DVC fall?
What do you guys think?
I think the focus is on what bitcoins are going to do at the moment, so I suspect there is going to be the continual downwards pressure on dvc until bitcoins break back above $600 on good volume. If btc break down below $380, then there's a good chance the dvc price will crash as more people convert to btc and panic sell. I just wish I had more btc to lay some thick buy offers on vircurex (apart from the recent frozen funds, it still seems business as usual there). I'm quite surprised it's kind of holding steady at 27-28 satoshi for the past week or so. Maybe a psychological bottom. My sentiment exactly. I think the bitcoin/namecoin/devcoin trio makes so much sense. They have more than necessary hashing power to secure each others systems, and that's the most important thing going forward. Who cares about price fluctuations... |
|
|
|
It looks like NMC merged mining stopped to work. Last payment I received was from 2014-03-08. BTC mining and payments still work as expected. Anyone has similar issue?
Really?... just yesterday I signed for the NMC merge mining... and some people claim it doesn't even work? That would be so sad! |
|
|
|
The way I work it out (very roughly) is that Eligius generally solves 20+ blocks per day, so 13 will likely take around half a day.
The other way of looking at it is to follow the link to the payment queue, find your address therein, check the "Age" column.
Say, for example, your Age is 1 day 22 hours.
Then look at the top of the queue and at the bottom of the first block. Don't look at the actual top of the first block as that may worry you.
There should be a lot of entries there with a similar age (say for example 2 days 10 hours).
Subtract your Age from that Age and the difference (12 hours) is (roughly) how long it will take you to work your way to the top of the queue.
The actual real amount of time is how long the pool actually takes to solve those 13 blocks that will get you to the top, plus the variance of any more people joining the queue ahead of you as their thresholds are passed and they turn out to have been waiting longer than you for a payout.
Hope that helps, but now I write it down it does sound a little tricky and it took me a while to figure it out myself. YMMV.
Thanks, I will take your advice and try to get a feeling about how I am supposed to approximate those values. |
|
|
|
I emailed them and they should have a return label for me, so i can ship it back to them since it's insured.
Aah, I see you are located far far away... so you will ofcourse use FedEx to return it (same way you recieved it) Since my device didn't have to cross borders I used swisspost which is muchcheaper AND insured. |
|
|
|
this pool doesn't seem to payout the way it explains itself.. been watching it like a hawk the past week and seems payouts has a mind of its own
a detail on the mechanics (not the theory) would be useful since it doesn't seem to behave in practice as it is intended... basically it seems all accumulated work gets held ransom regardless of current block luck cycles which in theory should be paying out portions past your pay threshold but in practice it just sits there and says you are going further and further behind as if all your current work is old work that has to wait for super luck to include you .. and that doesn't even seem to trigger it either
it is broken
Just your understanding of how things work is broken. The pool is operating as it should. What some people do not understand is that the payout queue and the rewards from CPPSRB are completely independent things. The payout queue is a way to get actual coins to miners in transactions on the network. The CPPSRB rewards are the way miner's balances at the pool are increased. You never are further behind or anything. The payout queue is generally actual coins that will be paid to your address. The rewards are separate from that. For me as a noob this sounds like chinese. So when it says 13 block delay here at my address http://eligius.st/~wizkid057/newstats/userstats.php/16bWt62xq5rmQuGscq7L7GuZfYmZkkvN5xhow can I get an estimated value about how long it will take before the BTC arrives in my wallet? Thank you for your service to mother bitcoin. |
|
|
|
|
how deep will DVC fall?
What do you guys think?
|
|
|
|
how? There are no bids. No one is buying this. Let's see if someone buys that. I think it's insanely overprized. |
|
|
|
I received my order but no CPP came with it and worst thing is my order date was mid september and I just got it on Friday and also one of my module is broken.
It is interesting that you also recieved your device on friday, and that your device was damaged too. It's probably no coincidence that we both recieved damaged devices.I wonder what the hell happened. Can you tell me where you are located mo_mo? |
|
|
|
|
Show Posts
