|
A ddos attack snuck under the radar for a minute before they got filtered. Apologies for the bumpy ride just now. Mining service looks healthy again now.
|
|
|
|
|
Issue resolved. Pool should be running as normal.
Apologies for the downtime.
I'm looking into the details to ensure it won't happen again.
|
|
|
|
Yes I have confirmed all 3 of my bitfury miners work, however it is almost impossible to get all three to connect to bitminter. They all switch off failing.
Is there a fix to this?
What exactly happens? In bfgminer they work fine, but in Bitminter client you have problems detecting all 3? Only 1 or 2 get detected? Or they all 3 get detected but fail after mining for a while? |
|
|
|
My shifts start out good and stay that way for a day or two then they start to drop off and become erratic. Should I be restarting the client or PC every so often? I did notice you have options to automate certain things in the Bitminter client, is that something I should be using?
A couple users have reported increased memory usage as days go by and eventually sluggish response from Bitminter client. I run it for weeks/months at a time and have been unable to reproduce this issue. If you are having this issue, a java heapdump would be greatly appreciated. You'll need JDK (java development kit) installed for this. http://stackoverflow.com/questions/407612/how-to-get-a-thread-and-heap-dump-of-a-java-process-on-windows-thats-not-runnin |
|
|
|
Actually...275399 IS a BitMinter block. Coinbase signature is included.
Err... no? Coinbase: �3SOCK\ �C�4/SockThing/HHTT |
|
|
|
How does blockchain determine which pool solves the block?
It doesn't. It doesn't even try to. blockchain.info doesn't actually show who created or solved a block. It shows who they observed relaying the block first. What does this mean? Absolutely nothing. In a peer-to-peer network everyone are relaying blocks and transactions all the time. It doesn't mean anything. I saw a person threaten another person because the second person's bitcoin node had relayed a transaction stealing coins from the first person. Does it mean that the second person was the thief? No. Bitcoin nodes relay blocks and transactions indiscriminately all the time. One can hope that blockchain.info will stop showing worthless information that is constantly being misinterpreted and could in some cases have dangerous consequences. But I'm not holding my breath. This site actually tries to identify who created the block: http://blockorigin.pfoe.be/index.php
TL;DR: blockchain.info BAD, blockorigin.pfoe.be GOOD.
|
|
|
|
I have a bitfury miner that will not connect anymore. Bitminter client is giving me a times out error.
Is the miner dead?
Did you test it with bfgminer? Do you have any plans in the future to expand your merged mining support to other alt coins?
Not currently. devcoin (centralized coin with a central dude giving most of the coins to his friends) and ixcoin (an old pre-mine scam that just won't die completely) seem pretty much worthless. Maybe in the future if there is something supporting merged mining that is of value and/or that is actually useful. So i recently set up my account on bitminter.com and started using the Bitminter miner and I can see that its getting proof of work accepted by server and all of that stuff but my balance on the website is not changing, only the unconfirmed for NMC and the future for both BTC and NMC are changing. I have my account info set up on the miner as well. Thoughts?
You get paid when blocks are found. Right now we're on an unlucky round. This evens out with lucky rounds in the long term. More info on payouts here: https://bitcointalk.org/index.php?topic=27062.msg2769824#msg2769824 |
|
|
|
I have one client machine that runs constantly between 125-135ghs and another machine that runs between 4-5ghs yet I never see anything above 125ghs combined through the web site. I usually see 110-115 and sometimes in the 90s. Is there any explanation for this or am I missing something?
Look at your average hashrates per shift. Those are more accurate since they are estimated for a whole shift, not just a couple minutes of mining. https://bitminter.com/shiftsThese hashrate estimates you see on the website only count accepted work. If you have a lot of rejected work and/or hardware errors (miscalculations) then that will affect the results. |
|
|
|
I have not been able to connect to mint.bitminter.com since sometime this morning, directly with cgminer or with a stratum proxy. Trying even to telnet directly to mint.bitminter.com on 3333, 8332, 80, or 5050 results in a connection timeout. I have reloaded the page at https://bitminter.com many times without any problems, although the live stats popup (on the "me" tab) shows no gauge image. Is there a problem? The site seems to be indicating other people are submitting work... *note this is all on a setup that has been functioning for months now Contact me at operator@bitminter.com and let me know which IP you are having trouble connecting from. |
|
|
|
I have .004 in my BTC balance, and 0 in NMC. How can I request a manual payout of the balance as I don't see myself using bitminter in the foreseeable future right now.
Manual cash is out coming soon. |
|
|
|
Is it me or is Bitminter getting more stale blocks than other pools?
It's because other pools don't show stale blocks, only orphaned blocks. Would you consider adding a decimal point and the comma number_format() ?
So as of now WTFATF has a rate of 22762... what I'm asking is to change the display so it might look like this: 22,762.8
Yeah, or maybe display TH/s or GH/s depending on your speed, like with Bitminter client. |
|
|
|
Could someone explain why I'm seeing around 1.24% rejected proofs of work on the live stats page? What causes this and what can I do to reduce this number?
The reject ratio is always high just after we find a block. It starts at 100% rejects the instant after the block is found, but quickly drops after that. |
|
|
|
can you please help me: I use Bitminter 1.1.2 because of my firewall. For mining I use a AMD 7770 but I have the problem that I get many miscalculations (for example 100accepted and 92 miscalculated). What can I do or is this normal?
That's one of the bugs in 1.1.2. It reports hardware errors that don't exist. It wasn't really prepared for var diff, but it works just with this cosmetic side effect. Depending on your OS there are some programs that can force another program to communicate through a proxy. You might be able to use the latest version that way. is this only a cosmetic effekt that the performance iof mining don't reduce? No tunneling works behind our firewall  I think most of it is cosmetic. But it would be better to run a newer version. Maybe you can use something like this: http://superuser.com/questions/18417/force-programs-that-do-not-specify-proxy-settings-to-use-a-proxy-ie-steam |
|
|
|
I updated to the latest drivers , but now i lost Opencl support i get this:
"Lacking OpenCL support. If you want to use GPUs, please install the latest drivers from your graphics card manufacturer."
Maybe my card does not supoort opencl.
Maybe nvidia removed opencl support for windows xp in their latest drivers? AMD did this and if you use win xp the latest catalyst version you can use I think is 12.3. Yes, from march 2012. Later AMD drivers work on XP for graphics, but not OpenCL. Anyone know if nvidia has done the same? |
|
|
|
|
Try reboot and/or reinstall nvidia drivers to fix "compilation error".
If you have to sudo to run on ASICs it's probably because your normal user lacks access to serial ports. For Ubuntu: "sudo usermod -a -G dialout USERNAME" then log out and back in.
|
|
|
|
I have 4 blades, the server sets each to 8, when I have them all on a separate worker. If I point them all to the same worker, the server assigns 32. Granted this seems like it is fine, but if it is expecting one blade to handle a diff of 32 then it seems overkill.
Whether you are mining with one 40 GH ASIC or four 10 GH ASICs doesn't matter. They do the same amount of work and find the same amounts of proofs of work. The four 10 GH ASICs will not do worse than the single 40 GH ASIC running at diff 32. The results are the same. To an outside observer everything is exactly the same. That observer can't even see if the results are produced by one or four physical devices. Guess I'm gettin to ya, sorry ;-/
Not at all. I'm just trying to get some points through to everyone. I see a lot of misunderstandings lately about worker difficulty. There is a belief that difficulty is a useful tweak you can do to improve your hashrate. This is wrong. It's a trade-off between variance and bandwidth usage (and for mining pool servers, the amount of proofs of work they have to process). Your hashrate is the same, regardless of difficulty. Increasing the minimum difficulty is useful to those with high hashpower to prevent the burst of proofs of work when you start out at low difficulty and the mining server in a panic trying to ramp up your difficulty quickly enough. I think the work submits per minute with a default setting of 20 is good for most people. If you have a very slow internet connection you may want to decrease that. If you are very worried about variance you can use the Easy Mode perk to be allowed to increase it above 20. But for most people 20 is good. It gives you fairly low variance, fairly low bandwidth usage and (kind of) fairly accurate live hashrate on the website. |
|
|
|
So if the server corrects with ideal diffs, then I could just ignore seting a minimum and let it settle in to that sweet spot on it's own after time, since for me when my hardware gets here will be 6 workers @ 100gh each. So I can either use one worker for the 6 identical workers at 71 or just forget setting a minimum and let them settle in on their own, assuming I didn't misunderstand what you just said.
Basically everyone can forget setting anything at all. The server will make things work. But if you have a high hashrate like 600 GH then you may want to set a minimum difficulty, maybe 512, to make the ride smoother right after you connect to start mining. This avoids the server having to ramp up your difficulty quickly from 4. Instead you get a good difficulty right away. |
|
|
|
|
Show Posts
