One thing I'll add. I am pretty sure I saw that the chips would sell for roughly $30 each. That would put the parts cost for this in at least the $70-80 range (wild guess on my part). Maybe j4bberwock got a better price, but I don't think anybody should expect this to be cheap.
Final retail price will be close to $150. You are right on the price of the chips, you can't get them really cheaper. Then, you add the PCB, the other components, and the cost of the assembly. To be transparent, they will cost me at least $125 including import taxes and VAT. And we are speaking of a bulk order of over 1000 boards. J4bberwock, which software will support these miners? Will cgminer or bfgminer devs add support for these devices, or is ancient minerd (the one that is also used for SFARDS official miner) the only one that is going to be supported? |
|
|
|
Pfool, currently your proxy aggregates all incoming connections (workers) into single outgoing connection (worker). It would be very good if you could add a parameter to specify the number of workers per one outgoing connection. For example, if one would set this "num-of-workers-per-outbound-connection" to 10 and would have 100 inbound workers connected (100 miners) this would create 10 outbound connection to the end-point pool. Could you do this?
what would the point of that be kenshirothefist? ... it seems to me that it would just create more work to aggregate the workers into 'sub connections' that would then have to be sent off as larger workers ... Yes, exactly. Several benefits: - no need to run several proxy instances, use only one for several workers; - many end-point pools (including nicehash.com) do not prefer very big aggregated workers (for example like 1 PH SHA256 workers in big proxy configurations) due to issues with setting difficulties, rejects, etc. ... with such option users of this proxy would simply configure proper sub-aggregation setting (like 10 workers per one outgoing worker) and would get better efficiency without struggling by running several proxy instances; - this would bring additional options like you already mentioned such as the possibility to direct different (sub-agreggated) outgoing workers to different pools; - probably some other stuff that I can't remember now  ... sure all this requires quite some coding effort ... but I think it could be some cool stuff if properly implemented. |
|
|
|
|
Pfool, currently your proxy aggregates all incoming connections (workers) into single outgoing connection (worker). It would be very good if you could add a parameter to specify the number of workers per one outgoing connection. For example, if one would set this "num-of-workers-per-outbound-connection" to 10 and would have 100 inbound workers connected (100 miners) this would create 10 outbound connection to the end-point pool. Could you do this?
|
|
|
|
A small but annoying bug regarding diff was found in cgminer, could somebody please check out if sgminer is affected as well? See this cgminer pull request: https://github.com/ckolivas/cgminer/pull/679? This is a small but annoying bug, causing small loss of performance (in terms of accounted shares on pool) when changing difficulty - especially when using vardiff or often diff changing (when switching from low to high diff miner immediately sends high diff while is should/could still send low diff and pool might wrongly account for shares). If sgminer is also affected, please push this patch to https://github.com/sgminer-dev/sgminer as well. Thanks! This has now been merged into sgminer-dev. I suggest all of you using custom sgminer forks to also include this patch since it will yield in a few percent better performance/payouts (on any pool). https://github.com/sgminer-dev/sgminer/commit/8bf1c1807cca1ca0ec0f87b452e3d1cb395f0b1b |
|
|
|
A small but annoying bug regarding diff was found in cgminer, could somebody please check out if sgminer is affected as well? See this cgminer pull request: https://github.com/ckolivas/cgminer/pull/679? This is a small but annoying bug, causing small loss of performance (in terms of accounted shares on pool) when changing difficulty - especially when using vardiff or often diff changing (when switching from low to high diff miner immediately sends high diff while is should/could still send low diff and pool might wrongly account for shares). If sgminer is also affected, please push this patch to https://github.com/sgminer-dev/sgminer as well. Thanks! |
|
|
|
ckolivas, could you please pull this pull request: https://github.com/ckolivas/cgminer/pull/679? This is a small but annoying bug, causing small loss of performance (in terms of accounted shares on pool) when changing difficulty - especially when using vardiff or often diff changing (when switching from low to high diff miner immediately sends high diff while is should/could still send low diff and pool might wrongly account for shares). Thanks! |
|
|
|
|
Are these SF100 meant to be fully standalone miners (plug into Ethernet) or like USB devices, connected to external controllers (similar to Avalons)?
|
|
|
|
Stopping it at six. 1 btc each = 6 btc
3btc at nicehash 50th
3btc at westhash 50th
I Will do the rentals manual rate adjustments (saves money I have time)
3btc with 50th is close to 6 days if we average 0.0099 with manual adjustments we could be as low as 00.91 when we are lucky and as high as 0.0102
over 0.0102 just sit and wait it out.
Hey, Phil, it's good to see you're enjoining clicking on NiceHash, but you can also automate this with NiceHashBot and just set&forget ... NiceHashBot will do exactly what you're trying to achieve: - get the app on https://github.com/nicehash/NiceHashBot/releases- submit new order and set upper limit - bot will automatically adjust price to the lowest possible and rise it up to your upper limit if other bidders are bidding higher and there is not enough low-price hash power (and the again lower it if possible, etc. etc.) This way your hash for solo mining will be automatically adjusted to lowest possible price. So you'll have more time to spend on bitcointalk |
|
|
|
|
How about undeclocking C1 miner? Is it possible to underclock/undevolt it to get better efficiency? Has anybody tried it? What kind of hash rate is it possible to get if you undeclock/undevolt to max 800W power consumption?
|
|
|
|
Ok, I did a multi-algo version myself, source available from HERE.This is based on badman74's latest version, so includes Lyra2E, Pluck and WhirlpoolX algos. Don't ask for windows builds, sorry. Are you sure this is based on latest badman74's version from here: https://github.com/badman74/sgminer? Because I've noticed two issues: "--difficulty-multiplier 2" issue is not resolved in your source (but is in badman74's git version) and Lyra2RE algo only works with "Lyra2RE" algorithm acronym, but not with "lyra2re". |
|
|
|
|
You should be very careful when using this software!!! There are no references to sources, no explanation who made those builds, etc.
This is most probably malware! I'd keep away from this software, it might even be some Bitcoin-stealing malware inside or at least some hidden pool mining inside.
|
|
|
|
Here is my working room heater I have a wooden custom build case under my desk with big ATX chassis in it, and one undeclocked Avalon4 connected to my Linux workstation which is always powered on anyway   Avalon4 is connected directly to my PC's power supply   My PC is an good old Intel quad-core, custom water cooled with water cooled GPU (an old AMD, doesn't even support OpenCL, so I can't mine with it )  But my undeclocked Avalon4 at only 30% fan speed is almost totally silent and at 45C it makes a great foot heater for cold days  That makes a nice heater that actually makes Bitcoins ... the miner itself draws about 380W which makes lesst hen 0.55 W/GH at wall ... considering the heating effect the electricity is basically free. |
|
|
|
What would be the right grammar to add both, "stratum+tcp://stratum.nicehash.com/#xnsub#skipcbcheck"?
Luke-Jr, it would be very useful if you would include a section in README explaining all #xxx pool parameters and the correct usage of them (syntax). Currently these options/features are only mentioned in NEWS... |
|
|
|
@Wolf0, @badman74, @djm34, etc. guys, guys, guys ... as I said many times before you are all great programmers (and I sent tips to all of you for your great public work) but you really lack one skill that is crucial for open source development, and that is team work. It is OK for each of you to optimize some kernels and not share it publicly to get maximum profit out of your own work. But as far as core development and binary distribution it should be done at one central place. People on this thread get lost when looking for binaries, trying various builds, many times hits an older build, build with bugs, etc. Linus Torvalds designed and developed Git with powerful branching in mind with this purpose - you can keep your branches, but should also maintain a master branch and not make thousands of forks even for smallest and marginal changes. https://github.com/sgminer-dev/sgminer is a good central place and binaries could be placed at the Releases section https://github.com/sgminer-dev/sgminer/releases ... So, can you put your self together and work as a team? You should all take a look at this talk: https://www.youtube.com/watch?v=5pOxlazS3zs (especially from minute 2 to minute 5, but preferably whole video). Anyway, keep up the good work |
|
|
|
a new version based on the latest sgminer5 version is coming, these problems should be fixed (can't test it though, I have only one amd card)
djm34, could you please work with Slix (ystarnaud) to include Lyra2RE into https://github.com/sgminer-dev/sgminer once is stable? |
|
|
|
Guys, why are you keeping this thread alive? All the excellent work that has been done by the OP author - lasybear and other developers has already been included in the "official" sgminer release (it's a community work, therefore I guess it can be called in any way, if you don't like "official" then it can be the "sgminer-dev" version). Information gets lost if it is kept in several separate threads, therefore I welcome you to discuss topics regarding sgminer and related stuff in this thread: https://bitcointalk.org/index.php?topic=632503.0If you agree, we could consider this thread closed and continue the debate here: https://bitcointalk.org/index.php?topic=632503.new#new |
|
|
|
|
Show Posts
