I've been playing around with the Satoshidice APIs and have gotten stumped on placing a bet.  The string I'm sending is:

https://session.satoshidice.com/userapi/placebet.php?secret=f58fa54291a6f3fd5439513d35eeba5d#DoNotShareThisURL&betInSatoshis=100&id=52682211&serverHash=8e0ee37b2169ee39f950a92e24b254231db6a05ac5e0ba7419368a73c99a1b52&clientRoll=8237&belowRollToWin=32000

There are no coins at this address, if you were wondering.  The error that is being returned is :

[nextRound] => Array
        (
            [id] => 52682211
            [hash] => 8e0ee37b2169ee39f950a92e24b254231db6a05ac5e0ba7419368a73c99a1b52
            [welcomeMessage] =>
            [maxProfitInSatoshis] => 2491925551
        )

    [status] => fail
    [failcode] => 2
    [verbose] => Invalid belowRollToWin
    [processLog] => Array
        (
           

• => onlyAvailableIfDebugTrue

        )

I've tried everything I can think of to get past the "Invalid belowRollToWin" and I am making no progress.  I get the same error whether the account has coins or not, so that's not it.  You can paste that url in your browser and see if you get the same error.  If I can get to a "failcode = 19 Bet is bigger than balance" then I've made progress.

According to the "Stats" page, there has been 687.219 btc deposited from 1783 depositors.  That yields an average deposit of .385  Now if you want to include all the non-depositors, the actual average is .073

1BcVNszRAKbUgPPBBr83HYfAj29TXmKGQ9

As a follow-up, it's been a week since the problem mysteriously disappeared.  It is my guess that either my motherboard glitch worked itself out (unlikely) or that a Windows update last week replaced a corrupted file someplace (probably).  Thanks to everyone that made suggestions.

It's not consistent. It appears to be reading a time that is frozen on or about May 20th, but it sometimes only reads it for a couple of random minutes before it finds the correct time somewhere.  Even changing the BIOS way off and back doesn't make the problem go away.  Even when I find the right time on May 20th, within 5 minutes of setting the time, I'm back looking at the message as the world turns under my stuck in time computer.  The only thing that confuses me, is why the bitcoin client is the only program that is reading a bad date/time.  My BIOS is right, my Windows is right. I wrote a little c# program that loops around and displays DateTime.Now and never see anything but the correct time.  It's got to be a hardware issue, but not like anyone I've ever seen before.

Yes, I'm leaning toward motherboard issues also.  It looks like my wife is going to get a pretty robust (though slightly used) gaming machine.  Time for me to go shopping again.  I always get the new computer

You've added more detail, yet there is still a problem.  Even with auto-updates, not everyone will have the updates at the same time, and if the government has to wait weeks or months for everyone to get the malicious code, they risk getting caught by the source savvy power-users.  And, there are a lot of different clients out there now.  Granted, they mostly use similar code, but each has it's separate routes for updating.  A more plausible attack would be to discredit bitcoins as an evil invention of drug dealers, gamblers, and weapons dealers... oh wait, that is what they are doing! 

Simply deleting the wallet would not be enough.  Most of us figured out pretty quick how to copy or replace the wallet.dat someplace safe.  They can delete my whole hard drive, burn down my house, and lock me up for 20 years and I'm pretty sure I can at least get my wallet back. To really do any damage, the coins have to disappear.  To do that they'd have to get the wallet, decrypt my password, and send the coins to never, never land. Easy enough for a couple of thousand wallets, but to hurt the whole community, doing it millions of times before we caught on would be daunting even for a quantum computer.

I know what it means now, but...

The more I work with computers (and I've been working with them for 32 years), the more I'm amazed at how intricate and complicated the simplest problems can become.  I was baffled why other clients (litecoin, feathercoin) didn't have the problem with the time. I was confused that my virtual machines didn't have an issue even when set to use the host date/time.  But, after studying the util.cpp till I knew what to look for (thanks for all the suggestions), I was completely blown away when this showed up in the debug.log


This was from a fresh debug.log and all the entries occurred within about 1 minutes of each other.  I've stripped out all the extraneous IP connection and addressing lines.  Note that as it connected to peers, the time difference was quite consistent (aprox. 28 days) until all of a sudden after 9 connections, the difference went to zero, all while consistently showing me the correct date/time on my desktop.  It is consistent that every time I start the bitcoin-qt, the time is off about that much, but whether or not the difference goes away is inconsistent.  

If it was the bios that had the wrong time, it would not straighten itself out randomly without a reboot, and certainly not mess itself up simply by closing the bitcoin client and re-opening it. I have completely uninstalled the client and deleted the %appdata%\bitcoin directory and started over new, yet am right back where I started with only the mystery and few answers.  Something happened or got written someplace around May 20 that the client keeps reading.  What it is, I have no clue.

"Added time data, samples 11, offset +5 (+0 minutes)
nTimeOffset = +0  (+0 minutes)"

...but what does this mean?

Land of the free... not in my lifetime, not yet anyway!  When Americans finally get fed up with this crushing tyranny, the rest of world will probably breath a sigh of relief.  There has never been a more horrendous misapplication of power than what I have seen spewed from the corrupt power hungry pulpit posers that run our government right now.     

I really like the way you have blocked access to the site and technically, no 'gambling' occurs on the site.  If there ever is a trial over this, I really hope it's televised.  First, I want to see if they can find twelve jurors that can understand the bitcoin network, and second, how they think they can stop the transmission of bitcoins between any two people.

I can't agree with you more here, except for one change.  Programs cannot be stupid.  They will always simply be a reflection of the programmer(s).  That, however, will have to be discussion for a different thread.

I currently have 20 connections. I did the -debug=1 switch and looked in the logs and though I didn't understand everything in them, I did not see anything that would indicated a different time than local.  Your thoughts about a router or server up line from my computer having a wrong time is plausible if this problem occurred on other computer within my LAN or within the VMs on the same computer.  My Litecoin wallet on the same computer doesn't have a problem with the time, and from what I know, the two wallets have almost identical code. 

Later today, I'm going to backup my wallet.dat and then blow the whole bitcoin data directory away and uninstall.  I'll let y'all know the outcome when I get it all running again.

I've tried everything to correct the date/time on my machine and I don't think this has anything to do with the problem.  This morning I tried changing my CMOS and Windows date/time back a couple of weeks, rebooted to make sure everything was saved, changed the settings back to the correct date/time and still have the warning.  Then I remembered I had a couple of VMware OS's installed for testing, so I cranked them up.  Now, these VM boxes should be reading the same system date/time as my main wallet, but the VMs on the same computer don't give the date/time warning.  Weird!

So far it seems harmless but I hate mysteries. Especially when money is involved.

All good guesses.  Checked the timezone is set correctly for Utah and it sync'd just fine to the server.  Still have the message. 

I have a file synchronizer program I wrote a few years ago and if there was anything wrong with my systems date/time it would be barfing up 10 thousand files, but it is working fine.  Maybe it's time I pulled in the bitcoin source and started becoming a power-user myself.

Yes, I did check the year.  And I think it started the day after the power went out last Sunday.  I've double checked the date and times on both my local DHCP router and my Internet modem.  It doesn't appear to be stopping the program, but it is a mystery.

I've checked that both my CMOS and Windows 7 date and time are correct, yet I have this warning plastered across my client.  Any Ideas?

The purpose of the pyramid is the same as any pyramid scheme.  It's touted as an "investment" but in reality it is gambling.  You are betting that you are not the last person to invest in the pyramid.  If you deposit money to your deposit address, that money gets passed up the pyramid to others that have also deposited.  The more people below you in the pyramid and the more you deposit, the more your possible return.  No deposit, no return!  

So if you just join and think that's all that you have to do to get something then you're not understanding the rules.  Learn to work your referral link so that you actually have a pyramid below you and deposit some btc.  I have 423 people that have joined below me, and more joining below them.  You have to "work" the pyramid.  It's not a free ride.

http://bitcoinpyramid.com/r/2463

Marriage is a big enough gamble without including bets on bitcoin prices.  As someone that has been married multiple times let me just say your plan sounds... perfect!

This is why when I wrote my own program equivalent to KeePass, it automatically saves previously used passwords when I generate new ones.  I've had websites restore backups and forget my new password.  Remembering old passwords comes in handy.

The only ripoff at Satoshidice is the Law of Averages!  Lady Luck can be a bitch