Hmm, I need to check this later today when I am at home.

Yep, that should work. You can generate test xmpp messages on the support pages.

How embarassing  I DID click on the commit, skimmed the first few lines that showed removal of existing commands and went back to comment here. Please forgive my ignorance 

While I like the idea we have to make sure to stay backwardscompatible. So we can not just rename the commands and break all sorts of things that rely on the existing commands.
Better would be to add new commands and mark the old ones as "deprecated" and remove them only after some intermediate releases are done.

Doesn't this reversal make it even more suspicious? I mean that steep rise is equally unexpected like the steep loss before. What is the probability of these two events happening directly one after the other?

Currently the server is not reachable. I am checking with the datacenter whats going on...

Edit:
All up and running again!

New game mode: Singleplayer

Now you can get used to bitbattle.me by running single-player games.
The rules are the same, the only difference is that you have no opponent, so you don't risk having to share your win with your opponent. Of course this also means you miss the chance to increase your win by grabbing a share of your opponent's win!

So from pure game mechanics this singleplayer mode is very similar to the existing *dice games, but on technical level has some significant differences:

• The concept of a game with bet timeouts and game timeout
• The betting addresses are individual for each game
• Live update of game website with each placed bet
• Your win is payed only when the game is over, not after each bet
• There is no payout on lost bets

Especially the last two points might be interesting, as this prevents your wallet (and the blockchain) from being flooded with tiny transactions.

Having said that, i consider Singleplayer mode the "training mission" for the real thing. Get used to the game mechanics and the way risk score is calculated, then join the multiplayer games for the real fun 

FYI - Site has run out of diskspace sometime this morning  .
I could not react immediately on monitoring alert as I was not at home, so for some hours the service was not working.
Everything is back up and running since today afternoon ~15:00 german time. All missed blocks/transactions are processed in the meantime and the site is fully operational again.
Sorry for the inconvinience

Hmm - never really thought of it this way. You are right, I could try to join as much games as possible and always play a higher risk than the other player.

If you want to be sure that I do not trick you into a high risk game you can use the invitation game feature - I would have a hard time joining your invitation games without you noticing it.

How is this problem solved on other sites? I think the same scenario can be applied more or less to most online games where multiple anonymous players are involved. How can you make sure that all players are "real" and not just socket puppets from the bank?

Site update:

• Problem with joining abandoned/old games is solved
• The "Start playing" button on the main page now indicates if a player is currently waiting for an opponent (Button label will switch to "Join waiting player!")

Secret leaked?

Indeed this looks fishy. Given the amount of bets I am tempted to not accept this as pure coincidence/bad luck.

Fixed two issues today regarding timezones:

• Secret was revealed 2 hours too early :-)
• Bet creation date/time now includes timezone offset information.

I noticed that sometimes games waiting for opponent don't get closed properly when no one joins, resulting in the next player joining a game playing basically alone as the game starter abandoned the game already hours ago. I hope to get that fixed soon with some more improvements...

That's the exact reason I started  bitbattle.me. Same level of transparency/tracability as SatoshiDice, but much more action
Have a look at at and please provide feedback also in https://bitcointalk.org/index.php?topic=120497.0.

The first to click this invitatin link (within 5 minutes):

<invitation link removed>

Will bitbattle against me :-)

Edit: Removed the invitation link as it is no longer valid due to database reset!

bitbattle.me - Blockchain gambling improved

More than 250,000 bets placed with a total volume of 140,000 Bitcoin!

Jump straight into action without depositing and waiting for confirmations!
Don't want to wait hours until your bet gets eventually picked up?
Want to roll the dice without spamming the blockchain?
Fed up with your wallet being fragmented?
Want to track your bets in realtime on the website?
Pushing transactions without an opponent gets boring?

bitbattle.me is changing the game! It is inspired by the various dice games, but is adding some unique features:

• Have your own set of permanent bet addresses
• Track all your bets and sessions with personal statistics
• Optional incognito mode so only you can see your full stats and history
• Watch your and other people's bets and sessions live in the browser
• Multiplayer: Play against a (random) opponent
• Multiplayer: No luck? Still you can win by taking more risk than your opponent!
• Multiplayer: bitbattle your buddies with invitation games
• All kinds of statistics
• API & sample bot implementation

Most features are available without creating an account or registration! Simply create your player with attached set of Bet addresses - No email, no account, no password to remember! An account is mandatory to be able to start or join multiplayer sessions.

The basic bet system is similar to the various dice sites, but the available bets are spread more equal with win probability steps of ~5%. House edge for all bets is 1.9%.

Checkout the game rules, FAQ, available bets and API description.

---

Update 2013-06-02:

• Transaction fees reduced according to current bitcoin-qt client (0.0001 instead of 0.0005)
• Updated acceptance policy for incoming transactions:
•  If a transaction has fee >= 0.0005 0.0001, and all inputs are confirmed -> ALLOW
•  If a transaction has fee < 0.0005 0.0001, but all inputs are confirmed -> ALLOW
•  If a transaction has fee < 0.0005 0.0001, and at least one input is unconfirmed -> REJECT
•  If a transaction has at least one unconfirmed input but fee >= 0.0005 0.0001 -> ALLOW
•  If a transaction has at least one unconfirmed input and fee < 0.0005 0.0001 -> REJECT

Update 2013-05-02:
You can now opt to hide your stats and sessions from public. If you don't want the world to see how much you are betting you can go to your account settings and click on "Anonymize me in public stats".
Enabling this will anonymize or hide most of your personal information:

• Your dashboard will not be available for other users
• Your player name, sessions and transactionIDs will be replaced by '****' in all public statistics
• Your personal statistics will not be available for other users

Update 2013-03-19:

• API extension: Now it is possible to obtain detailed information about player's bet addresses, win odds etc. in json-format. Just take player's dashboard url and append /json/ at the end. (Sample: http://bitbattle.me/player/herbert/json/)
  More details in section "Player information" in the API description.

Update 2013-03-16:

• Display improvements: All bitcoin amounts are now rounded to 4 digits instead of 3 digits and have a tooltip with the exact amount on mouse-over.
• Socket.io-based API available! Check out the documentation at http://bitbattle.me/api/
• Open-source sample bot written in Python, including simple martingale strategy, available on GitHub.

Update 2013-02-18:

• The "Get started" page now contains a section for optional account creation. (Note that for account creation no email confirmation is necessary, so you could register with fake email. However in this case there is no possibility to help you in case you forgot your password.)
• If you are logged in you have a dropdown menu on your username (top right of navbar) with shortlinks the the dashboard(s) of your player. (Yes, you can have multiple players connected with your account)
• If you are logged in, every player you create will automatically be linked to your account
• You can link your existing anonymous player to your account. Click on the "connect to account" button in the player's dashbord and follow the instructions (You will have to sign a message with your payout bitcoin address to prove ownership).
• It is no longer possible to close other player's sessions (You can only close sessions of your own player when you are logged in)
• It is no longer possible to start or join a multiplayer session with other players. (You can only do this with your own player when you are logged in)
• It is no longer possible to create multiple players with the same name. Existing duplicates have been renamed.

Update 2013-02-08:

• Player-related urls now using 'slug' based on playername instead of uuid (example: http://bitbattle.me/player/herbert/). Old bookmarks are still valid, they will redirect to the new urls.
• Running sessions table in dashboard and index page now show the remaining seconds until session timeout
• Fixed a rare racecondition while closing sessions that could lead to duplicate payment objects, resulting in no payment being made (Thanks to R33F for helping to track down this bug!)

Update 2013-02-01:

• Bet limits raised by 66%! Win up to 50 Bitcoin with a single bet!

Update 2013-02-01:

• Make the notification of waiting multiplayer game more prominent, including waiting opponents name.
• Make sure to close multiplayer sessions in time even when no bet was placed.
• Inform player about remaining seconds if he wants to close a session early.
• Added info on transaction acceptance policy to rules
• Show timestamp in payments history

Update 2013-01-28:
New statistics and various small UI fixes:

• Bet History
• Session History
• Payment History
• Slightly redesigned main page
• Limit the number of bets/sessions/payments displayed on the players dashboard (As info on past data is now available in the player's statistics)

Update 2013-01-12:

• Placing multiple bets of the same type within one transaction is now allowed
• Extended double-spend protection. Incoming transactions are now checked based on these rules (and some more  ):
•  If a transaction has fee >= 0.0005, and all inputs are confirmed -> ALLOW
•  If a transaction has fee < 0.0005, but all inputs are confirmed -> ALLOW
•  If a transaction has fee < 0.0005, and at least one input is unconfirmed -> REJECT
•  If a transaction has at least one unconfirmed input but fee (>= 0.0005) -> ALLOW
•  If a transaction has at least one unconfirmed input and fee < 0.0005 -> REJECT

Update 2013-01-05:

• Rework session close logic to prevent deadlocks
• Add some more crosslinks to blockchain.info for transactions and addresses
• Improve live connection for IE users (now using flashsocket)

Update 2012-12-29:

• Fix display bug when other player's bets show up in dashboard
• (hopefully) fix display bug when bets show up multiple times in dashboard
• Closing a session is now only allowed 30 seconds after the last bet has been placed
• Increase maximum bet stakes by 50%!

Update 2012-12-22:

• You can search for bets by transactionID (Button "Lookup Tx" on main page)
• Rejected bets now have tooltip on mouseover which states the reason for being rejected
• Refund payments now have a tooltip on mouseover which states the reason for the refund
• Some additional minor fixes

Update 2012-12-19:

• No more bet timeout for singleplayer sessions
• Increase session timeout to 10 minutes
• Added "close session" button to session details page
• Increase bet timeout in multiplayer sessions from 75 to 90 seconds
• Decrease bet limit to 50 bets/session

Update 2012-12-18:

• TxFee calculation now follows the same rules like the official bitcoin client. Payout transactions should get faster confirmations now.
• The issue of too little confirmed balance in the hot wallet ("Wallet depleted" error) should not occur (so often) anymore.
• Payments are now handled asynchronously. You will notice that all payment start in state "pending" and after a short time (usually <1 second) switch to status "paid"

Update 2012-12-14:

• The lucky number is now displayed in the session log
• The number of bets per session is now limited to prevent huge sessions like Carlos produced ;-).
• When a game is closed the reason for closing is displayed (bet limit reached, time limit reached etc.)
• Fix: Pending Payment issue caused by huge sessions
• Fix: Refunds in multiplayer sessions caused an internal error and were stuck
• Fix: After a bet is rejected due to insufficient wallet balance you had to open/close a multiplayer session in order to be able to bet again

Update 2012-12-11:

• Invitation links are back!
• The "Start Multiplayer" link will now change to "Join multiplayer" when another player started a multiplayer session. This should make it a bit easier to have a multiplayer session as you immediately see when one is started...

Das ganze gibt vielleicht den Ideen zu dezentralisierten Tauschbörsen wieder etwas mehr Interesse. Muss mir mal wieder den aktuellen Stand von OpenTransaction anschauen.
Jedenfalls vielen Dank an den OP für die scans!

Ahh, that makes sense. Thanks for clearing it up!

So this is for protecting against double-spend attacks? How does it help?

After skimming through this whole thread and not finding the answer:
I don't understand why you pay that small amount even when losing. What is the motivation?