Last block mined has 0 TX in. Something might be wrong.
Just some miners still on ancient cgminer versions. Those blocks are already rare and will be rarer as more people upgrade their miners. I send a message to upgrade whenever those miners get a reject, but I guess most miners aren't watching their logs that much. |
|
|
|
|
Before I allow miners to modify the transactions I hope bitcoind will get a JSON-RPC method that allows you to send it a block (or just prevblockhash + list of transactions) and get back whether this would be a valid or invalid block. I would like to not have to duplicate all those checks that bitcoind does.
If that happens, I'd be willing to support GBT transaction mutations in my pool.
Even without that, miners could implement checking for double-spend attempts across multiple pools. But the only reaction available would be to stop mining in all pools with conflicting transactions. Not a very good solution.
Either way, it would be interesting to know how many miners are interested in this. It makes more sense to spend time on this if miners actually care. Anyone want to set up a survey?
|
|
|
|
any plans on making fastest user list longer?
There are no plans for that. And I think top 50 is as much as makes sense to display at one time. But perhaps it could have multiple pages, like the block list. |
|
|
|
Have you considered something like CloudFlare to help protect the front end? It won't do anything for the mining ports, but it might help defend the website.
In this instance it was a pool server bug undetected in testing that made the getwork miners go nuts. But yeah, I have considered CloudFlare. I may go for that in the future with more servers. |
|
|
|
Quick question, am I able to log multiple computers into one worker id? Would this affect performance? Thanks
Yes, you can. You won't be able to tell the computers apart in statistics but otherwise it would be fine. |
|
|
|
Not sure what's going on, but I'm getting paid a lot less than normal this last week. I've been getting .05-.06 btc every block but now I'm lucky to get .02 or even .01 every block. Normally I get around .7-1 btc in a day and I'm not even getting .3 on most days. Has something changed that I missed?
The reward halfing at height 210 000? |
|
|
|
Looks like bfgminer now is working onstratum. I see less shares acceptedon my console but the hashrate on bitminter looks right. Is this the way its supposed to work.
Yeah, that's because of variable difficulty. When it says "Accepted f7564e7c Diff 16/4 GPU 0" that means this proof of work would be good enough when mining even at difficulty 16, but you are currently mining at difficulty 4. On the server this will count the same as 4 difficulty 1 proofs of work. So you will see the accepted count on the server go up by 4. |
|
|
|
I'd say just drop the connection since that would mandate they try to reauthorise.
Yeah, will do that. Didn't see this until now: https://en.bitcoin.it/wiki/StratumAre all those RPC methods documented somewhere? |
|
|
|
|
Issue with bfgminer fixed as well.
|
|
|
|
Apologies for the bumpy ride. Technical mumblings: There was an issue with longpoll (both getwork and gbt) because of a race condition. Seems it never triggered before I switched to a different java virtual machine. And of course it never triggered during testing, even with that JVM. Have to love those bugs that only occur in production. I believe that issue should now be resolved. Bad news is, I didn't know bfgminer requires mining.get_transactions to be implemented. Edit: it doesn't, actually. So bfgminer is still acting up. But any miners running getwork or gbt should be fine again. Working on the bfgminer issue. Is merged mining still occurring with stratum?
Yes, merged mining happens whether you use stratum, gbt or getwork. |
|
|
|
|
Seems a change on the server is causing miners to sometimes run crazy. Working on it.
|
|
|
|
Sorry for the web server barely being able to move. There's a DDoS attack in progress.  |
|
|
|
All the new changes are now live on the regular ports. Testport has shut down for now. Variable difficulty ("var diff") settings: minimum 1, maximum 16, and default at 2 when your hashrate is unknown. The maximum will be increased when ASICs come out. The server will adjust your difficulty aiming for 20 submitted proofs of work per minute. Port 8332 has getwork with difficulty 1 for now. This means you can still use leases from hashpower.com - var diff will be activated for getwork once hashpower supports var diff. Port 8332 also has GBT with var diff. Port 3333 and 5050 has Stratum with var diff. New work pushed at 30 second intervals. If you want to use GBT or Stratum you may want to update your miner config and/or restart bfgminer/cgminer/poclbm to get it running with a new protocol. BitMinter client will get support for other protocols later. It runs getwork with rollntime now and will use var diff once activated on the server. Let me know if you have any questions or experience any problems. Congrats on the upgrade Doc!
Thanks! That was a lot of work and many changes that just went live. Good to finally finish all that and see it running smoothly (knock on wood). |
|
|
|
Running good here. One thing I'm seeing is the server can't seem to decide what difficulty to give. Largest miner is ~2.6GH/s. At startup, it's on difficulty 2. Then it switches to 1. Then it switches back to 2. Right now it's on one.
It's changing between 2 and 4 for me. Reject rate is ~1.5% ~1.9%. Yes, some users will be on the boundary between two difficulties. This currently gives a lot of rejects in cgminer. But they do no harm and they will disappear in a later cgminer version when it starts using the new stratum way of handling difficulty. Stratum was recently changed to better handle changing difficulty. We'll have to expect it can take some time before everyone have changed their implementations. Rewards page isn't working correctly anymore, it seems to assume a 50 BTC block reward for the expected average.
Oops, will look into this. Please add stratum to the main port. I miss the statistics. Coming right up. |
|
|
|
|
BitMinter client tries to run the GPU as fast as possible at all times. The red light flashes when the needle reaches the red section. It simply means you are above what is considered normal speed for your GPU. Probably because you are overclocking. If you overclock a bit more it will probably stay in the red all the time.
|
|
|
|
|
What would be recommended server behavior in the case that, after authentication, a worker's credentials are no longer valid. For instance due to the password changing, the worker being deleted, the user being banned or the user account deleted.
And does it make sense to implement more commands than the ones in the docs at bitcoin.cz?
|
|
|
|
|
Thanks for testing, guys! Just restarted with some tweaks to var diff and logging, and fixed the stats issue.
Testing continues. Let me know if you have any issues at all on the test port. So far things are running very well and I'm considering setting this up on the main port very soon.
I forgot to mention the new version also has some decent reduction in CPU usage. It will be interesting to see the effect all these changes will have on CPU usage and reject rates.
|
|
|
|
I have my miners pointing at stratum now. I miss the stats. I assume this is production testing, so I still get paid for my work?  Yeah, this is a case of that ugly thing called "testing in production".  So yes, you get paid, and work done on the test port shows in most statistics but not current hashrate (worker page, top50 list, etc). But if you refresh the workers page after 10-15 seconds you can see the number of accepted proofs of work go up. 36 Stratum connections at the moment. Everything running smoothly. I do see the test port reporting statistics wrong, not always counting Stratum users for the current number of users and workers in the pool. I'm working on fixing that. You can't see the wrong numbers now, but I need to fix it before this goes live on the regular port. |
|
|
|
BitMinter is currently testing some goodness for ASICs: - Stratum with variable difficulty
- GBT (getblocktemplate) with variable difficulty
- getwork with rollntime and variable difficulty
That's all the three viable options for ASIC mining. Join the test and help make sure everything is ready before your ASIC arrives. See https://bitcointalk.org/index.php?topic=27062.msg1372864#msg1372864 for info. |
|
|
|
|
Show Posts
