|
Maybe you can firm up your offer of paying for a rig they send you prior to you making payment and you can confirm that to us. I am assuming here you'll be happy to meet their asking price and associated costs, since you initiated the "invitation to treat".
|
|
|
|
|
Who is real and who is not? That they respond to posts, the same way you do, is enough proof they are real (in the confines of this forum). In any case, they must have a reason to refuse escrow (if indeed they've refused it), and though that may be a warning sign, it may just as well be an innocent oversight or indeed a business decision on their part, but that does not make them a scam (though they could be).
|
|
|
|
|
Stop giving the guy a hard time. He is NOT a manufacturer but clearly a reseller. If anyone thinks they are a scam, simply do not buy from them, period. I am sure their prices will put off a lot of people, as the very same rigs can be got from the manufacturers cheaper (albeit subject to taxes).
But honestly, would any "respected" member of this forum asking for a rig to be sent before paying actually pay for it if it were sent (at their prices)? The answer will be a convoluted one, arguing price point, shipping et al and ending with NO. So why do you ask if you know you can not (and will not) pay for it? Cut the guy some slack.
|
|
|
|
|
Talk about signature campaign spam and necro posting ....
If any rig is twice as fast as another, not only that, but uses half the energy to deliver that hash rate compared to the other, then it is as clear as daylight that it has to be, arguably, twice as expensive, if not more.
EDIT: And no, I refuse to feed the troll.
|
|
|
|
|
Now here is the proof, if any was needed, that bitmain do NOT care about the bitcoin eco-system, let alone the home miner (and not that they have / need to).
Without any question, the S:Next-one is already in production and being deployed in their own mining operation. And the suggestion by some that bitmain's strategy includes playing their part to limit network diff growth through limiting rig's sales to the home miner for the benefit of us all is all but wishful thinking. They are in it for themselves (and I don't blame them for that), but price gouging home miners is a despicable act on their part. Current USD rate is over $288 yet they have their's set at $278, and that for overpriced, used equipement ... well, they are the only game in town so why not?
An absolute disgrace!
|
|
|
|
It's not extremely bad at all. The CDF values for different Diff% are: 0.86466471676339 200.00%
0.95021293163214 300.00%
0.98168436111127 400.00%
0.99326205300091 500.00%
0.99752124782333 600.00%
0.99908811803445 700.00%
0.9996645373721 800.00%
0.99987659019591 900.00%
Simple statistics. So for example, it is expected on average for 1 in just under 1,001 blocks to be more than 700% i.e. some time in the near or distant future, it is not at all unexpected to get a block over 700% The wonders of statistics .... can achieve and fail to deliver granularity in the same breath. Should have been called guessitics. But also note the even more important fact regarding that - sample vs population.
If you only have a small sample of blocks you can't even expect those numbers to be close.
Remember that the bitcoin network itself uses 2016 blocks to determine, inaccurately, the current network performance, so you need a lot of blocks before you can make any reasonable statistical judgements.
I actually believed the minimum sample size required to have at least 95% confidence in the result is 2000. (Off my fading memory, doubling that sample size to 4000 would NOT get you into 96% confidence irrespective of the population size....). |
|
|
|
^^^Your line: {"api-listen":true,"api-allow":"W:127.0.0.1","pools":Should be: {"api-listen":true,"api-allow":"W:127.0.0.1,R:192.168.0.194","pools":to allow read access, or prepend a W instead of an R to the IP to set write access (i.e restarts, pool changes etc) OT: I enjoy he threads where you overclocked your S3 and S3+. Huge help for me when I started mining and I have used that knowledge for both over and underclocking. Underclocking is the Bitcoin miner's overclocking these days. I wish there was more information about the pencil mod, or a mod you could do with a rheostat which simply dialed the vcore and frequency up and down. I need to load Kanos firmware because I am still running the October 24, 2014 FW I found in the Ocing thread you made. and Thank you very much for pointing out the missing R. After I read your post then Kanos I jumped to the cgminer text he linked and there it is, hello to me haha. I should probably do more googling on the topic. I have been playing with JSON to Excel for kicks and starting importing data, but then I realize the hard work is done in so many open source projects like this one. I do however like the ability to apply a % reduction to the miner speed reported by the SP20 in M's miner to see if I can find the magic number. You are welcome ... never done any harm doing it your own way, so keep at the JSON to excel thing, I am sure you'll end up with a custom report that can beat any code off the web! I personally have no SP20, so not in the best postion to give advice on how to reduce the miner speed. Via the SSH or through a script, it should be straight foward, i.e simply change frequency settings (in conf file) then restart cgminer (which re-reads the conf file). Where is the best thread or site to find things like can I pass through the command line parameters for cgminer through the password field. I'm not averse to reading long threads and googling, but man I haven't tripped across a for sure on that except password and a mem command. I'll go through the cgminer thread again and read the readme.
If by commad line you mean SSH, then all cgminer API commands can be run via SSH, and since you'll be looking to change settings for cgminer, I'd say the best repository would the very same cgminer API- README file. |
|
|
|
That is what happened when they made that change. Pointless, and a waste of other people's effort.
Anyone who had a program to monitor the API was of course looking for fields named "MHS ..." then Bitmain put different fields in the Ants, so all of those monitoring programs now had to look for both "MHS ..." and "GHS ..."
Yes there have been other monitoring programs around for a long time.
I suppose there are a number of ways to skin a cat. The way I implemented the parsing of json (BTW I've never used M's monitor simply because I wrote my own) meant that I took care of the MHs nuasance when I first saw it, because I thought "what happens when it's THs ... so I had it covered to PHs ! The issue that cropped up (I think I mentioned this in another thread), was the additional nesting of the json result ... but all good now. |
|
|
|
The solution for monitoring tools may well be to support those broken APIs also, but ignoring the consistent and backward compatible cgminer API I've written is a mistake.
That's a bit harsh. My app is coded around the API output coming from the supported miners at the time it was written. How/why would support be added for data that isn't available and can't be tested with? M I agree there was nothing much to be done about the "mother" cgminer API output, simply because there was no demand for it and the assumption that bitmain actually properly implemented the API. Saying that, the fix is quite simple, basically, the json output from kano's API is nested inside another array (if you deserialize using the native javascriptdeserializer in .NET), and there are extra values added (hopefully that will be consistent in the S5 release too). |
|
|
|
To me it looks more like remote access to miners produced by them. You can register dual miner on that website and then you can remotly check and maintain miners in your location.
I actually agree with you here that it may just double up as a miner hosting (as well as a cloud mining) option for their gear. They may be taking a leaf from the bitmain book of tricks, but (it has been said before and) I believe that is the way the home mining market is headed. |
|
|
|
I post with logic and provide a thought-out response; you posts bullshit and call people names. Hmm.... You also can't seem to figure out how to quote more than one post in a single response. You're funny.  You post nonsense for the simple and selfish persuits of your signature campaign. On a good day I'd call that signature campaign trolling, but I'd be feeding the troll in you to troll even more. I call you what I perceive you to be from your posts, and you are a pathetic troll (and so what if I can't quote more than one post, if at all ... it's a troll's toolkit). |
|
|
|
Ever since you started your recent line of witch hunt questioning we haven't solved a block. Seems this is no ordinary coincidence?!
I know ck and kano walk on hallowed ground in more ways than one, but asking a simple question a couple of times (mostly because some trolls who do not have a clue as to the answer keep doing their best to answer it or signature campaign posting), can not be construed to be a witch hunt .... surely not. Well, unless of course you are so thick you can not see the simplicity of the question for the love of trolling. |
|
|
|
I didn't think my response left any ambiguity about what effect those changes had on luck: Wow guys - that's some blocktastic green run you've got going on there, well done!
Do you think it's because of your modifications -ck mentioned earlier?:
No That the changes to bitcoind were "announced" coincidentally during the latter end of good luck streak coupled with the assertion that (and I vaguely quote here) "those changes were to give pools an advantage" when asked whether they'd be shared, may have led me (and anyone else bold enough to admit) to believe that they were responsible for the "improved luck". I am sure even the trolls, with the benefit of this hindsight would appreciate there's nothing out of the ordinary in that. But again I failed to get the answer (to draw parallels) to the secondary question: has the bad luck streak also afflicted the solo pool? (or maybe I should do my research ...) |
|
|
|
are those code changes actually affecting our luck? As you should obviously know, you can not answer that question.
I can answer, and the answer is a resounding "NO". What is the use of repeating something thats been answered by the person it was asked in the first place aside from the pleasure in trolling? You signature campaign troll. |
|
|
|
hmm interesting, some things there i didn't know. I run them at stock freqs btw. Im going to put them on the dells just to be safe. Thanks.
Just remember to un-plug and re-plug the 6 pin PCI-E cables every blue moon ..... or whenever you do your power reboots. |
|
|
|
|
If you do not OC (in fact I'd say you need to underclock a bit) then you can run 2 S3's on one of these.
With regard to cables, I'd go for 16AWG.
|
|
|
|
The answer is no
I do apologize because I misunderstood you.
I am sorry I was thinking that you claim or assume that latest changes brought bad luck
I am REALY sorry
...
Apology accepted. You are still an idiot anyhow (and I won't be offering any apologies for that). |
|
|
|
Pekatete,
Please answer yes no please
Do you claim or assume that Latest code changes are causing bad luck to both solo and kano pool
If the answer is yes you are a total idiot. PERIOD
If answer is no please do take my SINCERE excuse because my English is not native and I misunderstood your post
Anyway do not feel obliged to answer me
Thanks
OK now you have proved your lack of ANY worth. The question you are asking me is the very same question I was asking (well, that was until the trolls jumped in attempting to answer what they couldn't). Now how daft can you get? |
|
|
|
Do not assume just check github and stop spreading nonce
if you do not have a clue how to check github and read and understand c code just shut up please
Thanks
You may be revered around here, but that counts for nought in my book. So I think YOU should shut your gob and find someone else to take the edge off your issues with whoever that is you have an issue with (everyone really!). REALY? Do you have issues with github and c code? I have no issues with this and with you also. I just can not be so polite like others when I read a total bullshit from incompetent people who think that math is like philosophy or literature but math is a math and 1+1=2 Peace Now you sound like a total idiot. I have not taken the trouble to look through your last posts, but I receive a few alerts to several threads on this forum (mainly in the hardware sub-forum of bitcoin), and you have been posting to a few of those, needless to say, all you have been posting is diatribe and ranting, nothing of value whatsoever. If you do not want to be polite, I am sure you are well accustomed to people not being polite to you either, (so here you go) you accomplished twat! |
|
|
|
|
Show Posts
