I guess I need to take a break from working on Ant S5 How's that progressing? There's a lot of code to reverse engineer (although it's much better than trying to RE the binaries). From where are you getting the code? Interested in collaborating on it?  |
|
|
|
I guess I need to take a break from working on Ant S5 How's that progressing? There's a lot of code to reverse engineer (although it's much better than trying to RE the binaries). |
|
|
|
Any ideas when the Antminer U3 v2 will be supported? I am very curious to see if it will handle my U3's better than CG miner. I wish I was a coder and could help out. BFGMiner is a great piece of software  "Soon". I guess I need to take a break from working on Ant S5 & Avalon4 and just release 5.2 to get those out there... |
|
|
|
|
FWIW, I also checked CKPool, and (as expected) it is not affected either.
|
|
|
|
There is a vulnerability found in the majority of stratum mining protocol implementations. I've published the disclosure of this bug few weeks ago. Why did you make a public disclosure in Russian of a security bug in software written and maintained by people who probably don't understand Russian? The proper procedure for such things is to privately get in touch with the maintainers so they have an opportunity to fix it before public disclosure - especially for bugs easily exploited. Vulnerability is caused by incorrect algorithm of verification for uniqueness. Instead of checking raw solutions, most of the pools are doing this through checking the hex-encoded representation. This allows miner to create multiple versions of the same share through applying uppercase function to hex encoded solution.
This vulnerability seems as intentionally made i.e. backdoor. Simplest workaround is to use lower() method: While it's a pretty stupid bug, I don't think I'd automatically assume malice. As far I know, stratum-mining/eloipool/node-stratum-pool are vulnerable. Why do you say Eloipool is affected? It checks for duplicate submissions in binary. |
|
|
|
Guess that means well never See BFG support . I'll say it again I like both CG and BFG . why not give us that choice ? .  Now that things are open, BFGMiner support is planned as well (at least for the S5). There's a lot of code to go through, though, so it might be a few weeks still. P.S. Ignore the cgminer trolls' lies. |
|
|
|
Toby_Sterling
User account "Toby Sterling" is not registered.  |
|
|
|
I have forgotten about this, but there is the "rotate" function for bfgminer? and if yes, can i use it with non integer value, like 1/2?
example "rotate 1/2 minutes" or 30 secs if it is allowed
No, it only parses integers... is there a reason to not just use --balance or --load-balance for this? |
|
|
|
|
You left out the address and your username...
|
|
|
|
I am having issues installin BFGMiner 5.1 on my KNCMiner Jupiter
I followed the instructions in the README and everything works in the end. BFGminer 5.1 runs but if I restart the miner, ever goes back to the way before. And I have to follow all the instructions from scratch.
Any idea what I am doing wrong? Nothing, that's the expected outcome of those instructions. To effect a permanent change, you must overcome the RAM filesystem overlay. Generally, that means making a new firmware image and uploading it. |
|
|
|
question: Does --generate-to only accept Bitcoin & Litecoin addresses ?
I am trying to mine my local doged wallet but when i use --generate-to DOGEDADDR i get error Invalid Address
command i use:
bfgminer.exe --scrypt -o 127.0.0.1:20102 -u user -p pass -S zeusminer:\\.\COM4 --set zeusminer:clock=328 --set zeusminer:chips=128 --no-submit-stale --generate-to DOGEDADDR
I am still trying to figure out how to actually solomine a local wallet so maybe im missing something else but still curious about the error.
Only Bitcoin is supported, and GBT is strongly Bitcoin-specific. |
|
|
|
|
Well, when 5.10 exists it will work. Latest 5.1 does not support U3...
|
|
|
|
|
Right now, the wiki contains (I'm told) explicit links directly to malware and (without warning) scams.
A redirect from wiki.bitcoin.org would enable the criminals behind these to make their stuff look even more legit than they currently can ("it's at bitcoin.org, of course it's safe").
So I think I'd personally prefer more cleanup before this happens... but I don't have time to do it all myself.
If more people could volunteer to spend even a little time on it, it would help.
Edit: To be clear, I am not promising a redirect even if such cleanup occurs!
|
|
|
|
I'll try to document U3 stuff in README.ASIC before 5.2...
In the meantime, can you or someone else suggest a command line to use with 5.10 that will get BFG to recognize a U3? TIA. --set antminer:voltage=x800 --set antminer:clock=x1286 |
|
|
|
Hi, i am having troubles with my alcheminer scrypt miner when using bfgminer as a getwork to stratum proxy (also as a stratum to stratum proxy). My problem is that bfgminer send difficulty 0 to my miner.
Is there a way to fix it? Is the fault in my miner or is BFGminer sending difficulty in some strange way? Difficulty >0 would be extremely hard for scrypt. --set pxy:diff=1 should work, if you want to try it though. |
|
|
|
I have used it in the past and it verified and work correctly,jsut went and reverify and received the diff to low message  I think some of the Eligius servers serve out slightly less than 128 difficulty. Just skip the verification part and use it. M The problem is that the contract is marked as "dead" because of that. Maybe Eligius should round the difficulty setup to the nearest integer ? It's actually exactly 128, but stratum defines difficulty with a rounding error, so we have to adjust for that or else your miner might not submit some (tiny % of) valid shares. |
|
|
|
I have a question. If faster payouts were possible, then why we were waiting about a week for each payout before?
Backlog. No funds are ever kept online. The pool just coordinates miners to pay each other in normal operation. When the pool can't find someone for miners to pay, it sends the remaining funds to an offline wallet. When the pool has too many miners to pay, multiple people need to be available to pay the difference from that offline wallet. This security process is why Eligius has never lost any bitcoins to date, despite being the 3rd oldest pool. |
|
|
|
|
I'll try to document U3 stuff in README.ASIC before 5.2...
|
|
|
|
|
Show Posts
