Does it only bind to localhost or is there anything stopping me from running this on one system and pointing all of my rigs at it?

(read: I don't want to deal with the dependencies eight times)

An average hard drive uses 7 to 10 watts running full out - which in a mining rig, it shouldn't be doing. It uses much less when idle.

Worst case monthly cost for your hard disk at your cited energy costs is $1.44 per month.

A single 5830, on the other hand, would cost about $15.55 and one of my 400W rigs would eat up $57.6 per month. I've got six of those rigs and energy here in NV costs 11.28 cents per kW/H. My bill, including air conditioning, went up almost $300 per month. I envy your paltry $200 

Finally found the blockchain file but mine is at 400K, right where app details says it is, and it doesn't grow when I let the app sit and run.

This.

Especially considering that their pool structure is basically zero fee, Mr Sam wouldn't have been making much off of, say 50 GH/s of power. Even if he kept the 1% rather than redistributing it that's less than 10 BTC per month at current difficulty. Ignoring the variance problem completely, we should have solved between 3 and 4 blocks in this amount of time with our amount of power. that's 150 to 200 BTC worth of incentive - 15 to 20 months worth of profit at no real cost whatsoever.

It's a cool idea, but the incentive to cheat is too high and the pool owner's rep is too low. Maybe I'm overreacting, maybe Mr Sam is an honest guy and we're just having a really terrible round, but I'll be back over at Eligius for now, if for no other reason because at least I know Luke-Jr's rep better than Mr Sam's.

BTW, "Bitcoin Wallet" works just fine on the exact same phone. Granted, testnet's blockchain is MUCH smaller but still, that was a 5 second delay and this has run for hours...

Left it running for 9 hours last night. 4KB data footprint...

Yeah we really really need a block status indicator to help those of us who have been spinning for several hours troubleshoot.

Yeah, while other pools, solo mining etc have certainly taught me that long blocks happen, we're rapidly approaching the 95% point for this pool's hash rating and it seems more likely by the minute that block #3 will never hit and that our hashing power has been stolen. Too much longer and even if it's not technically proven it'll be statistically proven

I'd still like to know what Diablo's evidence is. I'm packing up and heading back to Eligius regardless, but I would still like to know what evidence is backing his claims.

Is there any actual proof of this or just trust in one forum moderator?

A hair under right now, I've got one node down from a dead power supply and one that's short a video card (technically short a VGA dummy plug but the effect is the same) but yeah, about 3GH/s or so.

I just wish I could get people to sign up on my referral link without being all spammy with giant images and such. No offense 

I'm pretty happy pointing my ~3GH/s at this pool regardless though, it's much more responsive so I lose fewer hashes to overhead. It's a pretty noticeable difference.

Yeah, I thought that was odd too, but what they're exposing to me has two boolean outs and if i leave either of them off it tells me that no override for that function has that number of parameters. Also its return type is void so no "bool whatever = function()"

I'm so confused at this point. They really should publish sample code

And yes, I realize that Dwolla's forums would be a more appropriate place to ask these questions, but their draconian registration process requires hand-approval which apparently no one is there to do right now, been waiting on approval for something like 7 hours now

I don't have the code for client.SendMoneyAssumeCosts, client is an Api object, and Api is the class I'm pulling in from the https://www.dwolla.com/api/API.svc?wsdl web reference. SendMoneyAssumeCosts is Dwolla's code which I do not have.

As for the decimal conversion, there was much more code before and it's gone through many iterations. That didn't used to be a static value and I simply didn't change the code around it when I changed it to a static value for testing.

Oh and for the record, I'm using their SOAP API but if someone has sample code for REST I'll happily switch to that one instead.

Hi Zagitta,

I wasn't looking for generic SOAP or REST instructions, I was looking for specific documentation of Dwolla's API as used in C#. Neither SOAP nor REST are that complicated, the problem is that I'm getting unexpected results from Dwolla and can't figure out why and there is no code that I can find floating around to tell me how wrong I've done this.

I'm quite sure it's something simple and stupid, I'm not even out of the initial testing phase, tapping out a few lines of untrapped code just to see what does and doesn't work. Perhaps I've just been staring at the problem too long and it needs fresh eyes.

I've got a web reference to https://www.dwolla.com/api/API.svc?wsdl set up in my project, as per their documentation. Here is the code I'm trying to make work, with API keys and account numbers redacted. Despite its brevity I'm sure it's a hot mess, considering what I've been up to these last few hours, but hopefully you can spot the problem?

protected void Page_Load(object sender, EventArgs e)
        {
            Api client = new Api();
           
            bool bResult;
            bool bResultSpec;
            decimal amt = System.Convert.ToDecimal(1.00);
           
            client.SendMoneyAssumeCosts("apikey_redacted", "apicode_redacted", amt, true, "test", "acct_num_redacted", out bResult, out bResultSpec);
            Label1.Text = bResult.ToString();

            client.Dispose();
        }

on the client.SendMoneyAssumecosts() line I get "The request failed with an empty response." and can't figure out why.

For clarification, I've added the web reference to https://www.dwolla.com/api/API.svc?wsdl and added the appropriate references, etc.

I create a new instance of their Api object called "client" and throw my various values into variables, then execute this:

client.SendMoneyAssumeCosts("myapikeyhere", "mysecrethere", amt, true, "test", "account-number-here", out bResult, out bResultSpec);

This code fails and throws the error: "The request failed with an empty response."

Any ideas?

So my google-fu is failing me. Does anyone have (or can find better than I can) a simple C# example of sending and requesting/receiving money with the Dwolla API (SOAP or REST, I don't really care at this point).

I've found example code in every other language, but for some reason it looks NOTHING like what's exposed to me via the exact same web reference...

80 hours... are you freaking kidding me? This is just too painful to watch.