Topic: bitbattle.me - no deposit, instant bets, ZERO waiting! 0-conf accepted! - page 10. (Read 16421 times)

The play today was a lot smoother. I emailed you about the only issue I noticed today which was, session would not close by timeout until you actually opened the session. This probably won't be an issue for most because I imagine they stay in session while playing. However, I like to stay on my dashboard while playing so, for people like me, this will happen. It doesn't necessarily make much of a difference to keep the session open as far as I'm concerned but, wanted to alert you.

To everyone else... This game is really great. If you used to be a fan of SD but hate the lag, lost bets, and spam getting in the way, this is the perfect place. You are in a session all by your lonesome and it is EXTREMELY fast.

Launched some updates today:

• 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

Slim was playing cat and mouse with my hot wallet the last 2 days, repeatedly causing the site to go into "Wallet depleted" mode. I need to rework the strategy here a bit while still making sure not to accept any bet that could not be paid from the hot wallet...

The rescan seems to have helped. To be sure all is fine I did a more or less complete exchange of the hot wallet - Transferred all funds to my local wallet and back again to the hot wallet - Went through without a problem.

The pending payments also have catched up already - So you can roll again :-)

Somehow the wallet got corrupted, resulting in most part of the balance being unspendable 
Right now restarting bitcoind with -rescan option - let's see if all comes back again...

Hah, you managed to screw the stats also: http://bitbattle.me/statistics/lucky_numbers/
As you always placed multiple bets in one transaction and for the graph i take the lucky numbers of the last 1000 bets there are a lot of bets with the same lucky number, resulting in a graph that seems to contain much less dots than before :-)

Both.

Yes, the bet processing gets really slow when the sessions has more than 200-300 bets. Maybe the limit should be 200 or 150 bets per session.

Yep, some payments were with "pending" state for several minutes.

I had a really bad experience with SD when I started playing with a higher stake  

I'll get back to you with the advertising 

Well, it should already do that. Do you mean the running sessions on the front page or on the player dashboard?
Yep, sounds good!
What exactly got slow? The website updates or the processing of the incoming transactions? I could limit the number of bets that can be placed within one session - When the limit is reached the session gets closed and paid out. As you proofed a script/bot can easily create hundres of bets per session which is not really considered in the UI...
Also good idea!
Yeah, betting API is on my TODO-List, but somewhere with lower priority. I think it could be fun to have bots bitbattle each other in multiplayer mode  But this will take a lot of thinking and also improvemnt of the multiplayer sessions...
This is only a display problem - closing, payout and last bet all happened in the same second, and the sorting of session events is done via timestamp which has a resolution of only one second. Definitely also have to change this :-)

Also the payment engine had some trouble, you probably noticed that some payments were in state "pending" for several minutes. I also will have a look there what was the problem.

Thank you for your feedback, and i hope you come back soon with a few thousand more bets (maybe with some higher stake?) 

Thank you   

Gratulations! You put some stress to my system which is exactly what a wanted to see :-) Bounty has been paid (txID 78b276cac6b7f086dc25707d4e71269131a9b29329a87c0524ee6b287b44c1be).

It was really fun to see my bets going through and my balance going up and down.

I'm sure your site will have great success  

Some things you may want to change/improve:

• "Running sessions" -> Once a session is closed, remove it from the list.
• Show the lucky number in the list (main page and user page)
• Once the session has >100 bets it starts to get slow, and after 200 bets it really gets slow
• Show the total bets and payout in the user page, so we can see the net profit
• API for betting bots, in SatoshiDice the bots can see if the user won the bet or not with the returning txid, it would be nice for you to have something similar with using API, or create an option to send a callback for a given page once the lucky number is calculated.
• Some bets did it after the session had closed (Eg. http://bitbattle.me/game/38435746aa2d4c79b2f1afaebe3ea2cd/)

I won!

http://bitbattle.me/bet/5000/

Create an account at https://coinad.com and I'll offer you free advertising for life

Whoever want to see my awesome stats: http://bitbattle.me/player/9bea43bff985482bbffa1302bc1de65a/

Invitation sessions are back!

On your player's dashboard you will find a new button "Start Invite Session". Click it to start an invitation multiplayer session. The new session will start in waiting mode and display an invitation link to share - Whoever gets to click this link will join your session!

Another small change is also live:
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...

PS:
Bet count is still low at around 1600, so still some more to go to claim the bounty!

BOUNTY RUN - Get 10 BTC to place bet #5000!
Right now (2012-12-08) there are 1477 bets placed. If you place Bet number 5000 you will get a bounty of 10 BTC - no strings attached!
Only condition: The bet must be valid (i.e. not a refund). In case Bet 5000 is a refunded one due to any reason, the next valid bet will get the bounty!
The bounty will be paid to the payout address of the player placing the bet. The bet number is the first number in the Bet log. Both single- and multiplayer bets can win. Note that the bounty will not be paid automatically, so please allow for some hours until you get your bounty in case i sleep, am offline etc. 

Update launched today:

• New "Get started!" page that should be more user-friendly
• "Find Player" on the frontpage to directly locate your player dashboard
• You can now start/join multiplayer sessions with your player
• Your bet addresses are now shown in a dedicated popup-window, so you can always keep them around
• whole bunch of UI design/layout improvements and cleanups

Unfortunately one nice feature did not make the change: Right now you can not create invitation sessions anymore. But this feature will come back soon 

And did I mention that win payouts of bitbattle.me do not directly rely on the outpoints of incoming bets? So even if some double-spends would come through this will have no effect on people's win payouts. 

Btw:
This is not as easy as it sounded in the beginning Since the whole site works without authentication there is no easy way to prevent anybody from closing your running session if I just add an according link. So this feature is not (yet) in.

Good point about being able to stop a singleplayer session. I will definitely add this

Had a bit of a play under the name Rocket.

Nice that you get the results so quick. Though it would be great if there was a button on the player dashboard to instantly end a session and get paid out (without having to leave the page)

I used a wallet with a small balance when testing and had to forever navigate away from the page when the wallet was out of cash, to then get my winnings paid out, navigate back to the page and keep going.

Other than that.. I like it!

Did not venture onto the multiplayer part yet though as things seemed very quiet.

Player srmagic was the lucky guy to make bitbattle.me reach a significant first milestone: 1000th bet!, placed today at 17:28:41+0100 (unfortunately lost once again  )

I did not expect to hit this number of bets so fast, so I take this as a sign of both trust and really having fun - Thank you to everyone who used the site so far!

There are already a lot of improvements planned, especially I want to focus on the multiplayer part. Right now there are just too few players so it is very unlikely that you get an opponent when starting a multiplayer session. Naturally, this can only be changed by you :-) While the active player base is reaching critical mass for multiplayer I am working on making it a smoother experience. First thing on the list is to make it possible to join multiplayer game with your existing player, instead of always needing to handle temporary bet addresses.

So stay tuned and keep rolling 

In case you did not realize it - The player stats were totally wonky . This is fixed now (together with better validation of Bitcoin Address when creating a new player)!
Right now jammm is by far the most active player with 348 bets.

Thanks for your feedback steamgames!
I noticed that someone created a player with an invalid payout address and actually won 0.35302. Naturally the transaction is still in "pending" state. So, if you read this please contact me so we can sort this out - In the meantime I'm back to coding to improve validation of payout addresses :-)

Edit:
Another thing, some user probably by mistake created a new player for each session. This is not necessary, the idea is that you just create a player once and then keep using it for as many sessions as you like. Whenever you place a bet by sending some coins to one of your bet addresses a new session is automatically started. Or, in other words: If you created a player the bet addresses are permanent, they will NOT expire when your session ends.