Pages:
Author

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

hero member
Activity: 488
Merit: 500
In case this happens to you:
There is a race-condition bug in the code that will create two or more payments for one session. This is considered "impossible" by the payment engine backend and so none of the payments get paid. I have a bugfix for this in the pipeline but not yet on the production system.
I get immediate email notification by the payment engine in case this happens and will always sort this out as soon as possible, but depending on personal state (sleeping/working/etc) and availability of internet access it might take few hours.

This happend 4 times the last week, so it is quite unlikely you encounter this bug, but if it is the case don't panic, you will get your payout  Cool

The bugfix is now deployed to production system. Issue should not happen anymore  Smiley
hero member
Activity: 488
Merit: 500
In case this happens to you:
There is a race-condition bug in the code that will create two or more payments for one session. This is considered "impossible" by the payment engine backend and so none of the payments get paid. I have a bugfix for this in the pipeline but not yet on the production system.
I get immediate email notification by the payment engine in case this happens and will always sort this out as soon as possible, but depending on personal state (sleeping/working/etc) and availability of internet access it might take few hours.

This happend 4 times the last week, so it is quite unlikely you encounter this bug, but if it is the case don't panic, you will get your payout  Cool
hero member
Activity: 488
Merit: 500
Ahrg. Bitcoind has been running for several weeks now without restart - Just today it started making troubles. I am looking into it right now.

Okay, everything is back to normal again. Pending payments are sent out, all transactions should be handled. If you think a transaction is missing let me know!
hero member
Activity: 488
Merit: 500
Ahrg. Bitcoind has been running for several weeks now without restart - Just today it started making troubles. I am looking into it right now.
hero member
Activity: 488
Merit: 500
Have you had any issues with double spending? You seem pretty brave accepting 0 conf bets!

Zero problem so far Grin
But I do have multiple measures in place to protect me, some of which are only possible through the usage of individual bet addresses for each player. And of course some obvious like "reject unconfirmed bets that don't have a tx fee" etc.
hero member
Activity: 504
Merit: 500
Have you had any issues with double spending? You seem pretty brave accepting 0 conf bets!
hero member
Activity: 488
Merit: 500
bitbattle.me is now online without any noteworthy incident for almost 6 months, having served 105,000+ bets in more than 6,000 sessions. While I consider this a great success, unfortunately the net result is not really overwhelming so far. Basically I am still struggling with keeping a positive net result. Therefor I am now raising the house edge from 1.8% to 1.9%.

This is still in the same range than the competition - And remember that I still offer some outstanding features:
  • immediate feedback on any bet
  • still accepting unconfirmed transactions
  • no blockchain bloat or transaction spamming
  • personal statistics and bet addresses
  • minimum bet of only 0.001 BTC

So I hope you keep visiting bitbattle.me Wink!
hero member
Activity: 488
Merit: 500
Another API piece now online: Now it is possible to obtain bet addresses, win odds etc of your player in json-format. Just take your dashboard url and append
Code:
/json/
at the end.

Sample link: http://bitbattle.me/player/herbert/json/

Check out the new section "Player information" in the API description.
hero member
Activity: 488
Merit: 500
Another update rolled out today:
  • 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.

The API is quite extensive and contains the same information that is used on the website to display the session progress. To get started check out the sample bot implementation (Direct download as zip: https://github.com/TripleSpeeder/bitbattlebot/archive/master.zip). There is a skeleton bot that is only listening for events and can be used as a starting point for individual bots, and a martingale bot based on the skeleton bot that implements a very simple martingale strategy.

20-round martingale bot run, starting each round with a stake 0.001 and limiting max bet to 1.0:
Code:
stingray ~/dev/bitbattlebot $ python martingalebot.py 8d735c925ea0431b984055b2b42bccb1 http://:@localhost: 1JczM9rH98Fe6YYqF39r89yS2f5gJHW63r 0.001 1.0 20
Connected. Now subscribing to player channel 8d735c925ea0431b984055b2b42bccb1
Joined channel 8d735c925ea0431b984055b2b42bccb1. Now starting bot.
Starting round 1!
Betting 0.00100000 on 1JczM9rH98Fe6YYqF39r89yS2f5gJHW63r
[Bet]: lessthan32768, drawn: 2301, result: True, stake: 0.00100000, win: 0.00196400
Starting round 2!
Betting 0.00100000 on 1JczM9rH98Fe6YYqF39r89yS2f5gJHW63r
[Sessionstate]: 2w/0l/48r - Stake: 0.00200000 - Payout: 0.00342800
[Bet]: lessthan32768, drawn: 46289, result: False, stake: 0.00100000, win: 0.00000000
Betting 0.00200000 on 1JczM9rH98Fe6YYqF39r89yS2f5gJHW63r
[Sessionstate]: 2w/1l/47r - Stake: 0.00300000 - Payout: 0.00342800
[Bet]: lessthan32768, drawn: 46704, result: False, stake: 0.00200000, win: 0.00000000
Betting 0.00400000 on 1JczM9rH98Fe6YYqF39r89yS2f5gJHW63r
[Sessionstate]: 2w/2l/46r - Stake: 0.00500000 - Payout: 0.00292800
[Bet]: lessthan32768, drawn: 7250, result: True, stake: 0.00400000, win: 0.00785600
Starting round 3!
Betting 0.00100000 on 1JczM9rH98Fe6YYqF39r89yS2f5gJHW63r
[Sessionstate]: 3w/2l/45r - Stake: 0.00900000 - Payout: 0.01078400
[Bet]: lessthan32768, drawn: 1318, result: True, stake: 0.00100000, win: 0.00196400
Starting round 4!
Betting 0.00100000 on 1JczM9rH98Fe6YYqF39r89yS2f5gJHW63r
[Sessionstate]: 4w/2l/44r - Stake: 0.01000000 - Payout: 0.01274800
[Bet]: lessthan32768, drawn: 21080, result: True, stake: 0.00100000, win: 0.00196400
Starting round 5!
Betting 0.00100000 on 1JczM9rH98Fe6YYqF39r89yS2f5gJHW63r
[Sessionstate]: 5w/2l/43r - Stake: 0.01100000 - Payout: 0.01471200
[Bet]: lessthan32768, drawn: 9757, result: True, stake: 0.00100000, win: 0.00196400
Starting round 6!
Betting 0.00100000 on 1JczM9rH98Fe6YYqF39r89yS2f5gJHW63r
[Sessionstate]: 6w/2l/42r - Stake: 0.01200000 - Payout: 0.01667600
[Bet]: lessthan32768, drawn: 41832, result: False, stake: 0.00100000, win: 0.00000000
Betting 0.00200000 on 1JczM9rH98Fe6YYqF39r89yS2f5gJHW63r
[Sessionstate]: 6w/3l/41r - Stake: 0.01300000 - Payout: 0.01667600
[Bet]: lessthan32768, drawn: 22893, result: True, stake: 0.00200000, win: 0.00392800
Starting round 7!
Betting 0.00100000 on 1JczM9rH98Fe6YYqF39r89yS2f5gJHW63r
[Sessionstate]: 7w/3l/40r - Stake: 0.01500000 - Payout: 0.02010400
[Bet]: lessthan32768, drawn: 19953, result: True, stake: 0.00100000, win: 0.00196400
Starting round 8!
Betting 0.00100000 on 1JczM9rH98Fe6YYqF39r89yS2f5gJHW63r
[Sessionstate]: 8w/3l/39r - Stake: 0.01600000 - Payout: 0.02206800
[Bet]: lessthan32768, drawn: 50302, result: False, stake: 0.00100000, win: 0.00000000
Betting 0.00200000 on 1JczM9rH98Fe6YYqF39r89yS2f5gJHW63r
[Sessionstate]: 8w/4l/38r - Stake: 0.01700000 - Payout: 0.02206800
[Bet]: lessthan32768, drawn: 28751, result: True, stake: 0.00200000, win: 0.00392800
Starting round 9!
Betting 0.00100000 on 1JczM9rH98Fe6YYqF39r89yS2f5gJHW63r
[Sessionstate]: 9w/4l/37r - Stake: 0.01900000 - Payout: 0.02599600
[Bet]: lessthan32768, drawn: 49097, result: False, stake: 0.00100000, win: 0.00000000
Betting 0.00200000 on 1JczM9rH98Fe6YYqF39r89yS2f5gJHW63r
[Sessionstate]: 9w/5l/36r - Stake: 0.02000000 - Payout: 0.02599600
[Bet]: lessthan32768, drawn: 3881, result: True, stake: 0.00200000, win: 0.00392800
Starting round 10!
Betting 0.00100000 on 1JczM9rH98Fe6YYqF39r89yS2f5gJHW63r
[Sessionstate]: 10w/5l/35r - Stake: 0.02200000 - Payout: 0.02942400
[Bet]: lessthan32768, drawn: 18600, result: True, stake: 0.00100000, win: 0.00196400
Starting round 11!
Betting 0.00100000 on 1JczM9rH98Fe6YYqF39r89yS2f5gJHW63r
[Sessionstate]: 11w/5l/34r - Stake: 0.02300000 - Payout: 0.03138800
[Bet]: lessthan32768, drawn: 5543, result: True, stake: 0.00100000, win: 0.00196400
Starting round 12!
Betting 0.00100000 on 1JczM9rH98Fe6YYqF39r89yS2f5gJHW63r
[Sessionstate]: 12w/5l/33r - Stake: 0.02400000 - Payout: 0.03335200
[Bet]: lessthan32768, drawn: 15509, result: True, stake: 0.00100000, win: 0.00196400
Starting round 13!
Betting 0.00100000 on 1JczM9rH98Fe6YYqF39r89yS2f5gJHW63r
[Sessionstate]: 13w/5l/32r - Stake: 0.02500000 - Payout: 0.03531600
[Bet]: lessthan32768, drawn: 53076, result: False, stake: 0.00100000, win: 0.00000000
Betting 0.00200000 on 1JczM9rH98Fe6YYqF39r89yS2f5gJHW63r
[Sessionstate]: 13w/6l/31r - Stake: 0.02600000 - Payout: 0.03531600
[Bet]: lessthan32768, drawn: 34125, result: False, stake: 0.00200000, win: 0.00000000
Betting 0.00400000 on 1JczM9rH98Fe6YYqF39r89yS2f5gJHW63r
[Sessionstate]: 13w/7l/30r - Stake: 0.02800000 - Payout: 0.03531600
[Bet]: lessthan32768, drawn: 53901, result: False, stake: 0.00400000, win: 0.00000000
Betting 0.00800000 on 1JczM9rH98Fe6YYqF39r89yS2f5gJHW63r
[Sessionstate]: 13w/8l/29r - Stake: 0.03200000 - Payout: 0.03481600
[Bet]: lessthan32768, drawn: 14787, result: True, stake: 0.00800000, win: 0.01571200
Starting round 14!
Betting 0.00100000 on 1JczM9rH98Fe6YYqF39r89yS2f5gJHW63r
[Sessionstate]: 14w/8l/28r - Stake: 0.04000000 - Payout: 0.05052800
[Bet]: lessthan32768, drawn: 29104, result: True, stake: 0.00100000, win: 0.00196400
Starting round 15!
Betting 0.00100000 on 1JczM9rH98Fe6YYqF39r89yS2f5gJHW63r
[Sessionstate]: 15w/8l/27r - Stake: 0.04100000 - Payout: 0.05249200
[Bet]: lessthan32768, drawn: 46723, result: False, stake: 0.00100000, win: 0.00000000
Betting 0.00200000 on 1JczM9rH98Fe6YYqF39r89yS2f5gJHW63r
[Sessionstate]: 15w/9l/26r - Stake: 0.04200000 - Payout: 0.05249200
[Bet]: lessthan32768, drawn: 14861, result: True, stake: 0.00200000, win: 0.00392800
Starting round 16!
Betting 0.00100000 on 1JczM9rH98Fe6YYqF39r89yS2f5gJHW63r
[Sessionstate]: 16w/9l/25r - Stake: 0.04400000 - Payout: 0.05642000
[Bet]: lessthan32768, drawn: 19850, result: True, stake: 0.00100000, win: 0.00196400
Starting round 17!
Betting 0.00100000 on 1JczM9rH98Fe6YYqF39r89yS2f5gJHW63r
[Sessionstate]: 17w/9l/24r - Stake: 0.04500000 - Payout: 0.05788400
[Bet]: lessthan32768, drawn: 50651, result: False, stake: 0.00100000, win: 0.00000000
Betting 0.00200000 on 1JczM9rH98Fe6YYqF39r89yS2f5gJHW63r
[Sessionstate]: 17w/10l/23r - Stake: 0.04600000 - Payout: 0.05788400
[Bet]: lessthan32768, drawn: 60010, result: False, stake: 0.00200000, win: 0.00000000
Betting 0.00400000 on 1JczM9rH98Fe6YYqF39r89yS2f5gJHW63r
[Sessionstate]: 17w/11l/22r - Stake: 0.04800000 - Payout: 0.05788400
[Bet]: lessthan32768, drawn: 24424, result: True, stake: 0.00400000, win: 0.00785600
Starting round 18!
Betting 0.00100000 on 1JczM9rH98Fe6YYqF39r89yS2f5gJHW63r
[Sessionstate]: 18w/11l/21r - Stake: 0.05200000 - Payout: 0.06574000
[Bet]: lessthan32768, drawn: 13418, result: True, stake: 0.00100000, win: 0.00196400
Starting round 19!
Betting 0.00100000 on 1JczM9rH98Fe6YYqF39r89yS2f5gJHW63r
[Sessionstate]: 19w/11l/20r - Stake: 0.05300000 - Payout: 0.06770400
[Bet]: lessthan32768, drawn: 60132, result: False, stake: 0.00100000, win: 0.00000000
Betting 0.00200000 on 1JczM9rH98Fe6YYqF39r89yS2f5gJHW63r
[Sessionstate]: 19w/12l/19r - Stake: 0.05400000 - Payout: 0.06770400
[Bet]: lessthan32768, drawn: 23445, result: True, stake: 0.00200000, win: 0.00392800
Starting round 20!
Betting 0.00100000 on 1JczM9rH98Fe6YYqF39r89yS2f5gJHW63r
[Sessionstate]: 20w/12l/18r - Stake: 0.05600000 - Payout: 0.07113200
[Bet]: lessthan32768, drawn: 30550, result: True, stake: 0.00100000, win: 0.00196400
Last round finished.
Disconnecting...
(bitbattlebot)stingray ~/dev/bitbattlebot $

See http://bitbattle.me/player/herbertsbot/ for the related session.
hero member
Activity: 488
Merit: 500
On SDice these bets would have resulted in 100.000 payout transactions, of which ~50.000 would be just dust spam to notify that you lost.

In principle, Erik pays tx-fees for the loss-payments. He pays them from the edge.
You don't have to pay them.  How much lower is your edge compared to Erik's?

There is 0.1% difference (Erik takes 1.9%, I take 1.8%).  But I did not calculate the Tx Fee difference in detail, so I can't tell if my overall edge is better than SDice.
But I can tell you that statistics are not on my side so far. Since beginning of the year house edge is way below the theoretical 1.8%. At the moment I am at impressive 0.73% Undecided

Even if you kept all these savings for yourself, you'd still be "good guy" for not
polluting the blockchain, but if your edge reflected your lower expenses, by being
noticably lower, then that might well attract more customers...

just speculating.
Maybe you are right, but with the statistical variance there is not much room for lowering the house edge withouth further increasing the risk of going negative...
hero member
Activity: 488
Merit: 500
I wanted to have the bet #100,000.
But I didn't have any money on my wallet at that time, just if I was home   Sad
No problem, next hot bet number is #1,000,000 Grin
full member
Activity: 216
Merit: 100
On SDice these bets would have resulted in 100.000 payout transactions, of which ~50.000 would be just dust spam to notify that you lost.

In principle, Erik pays tx-fees for the loss-payments. He pays them from the edge.
You don't have to pay them.  How much lower is your edge compared to Erik's?

Even if you kept all these savings for yourself, you'd still be "good guy" for not
polluting the blockchain, but if your edge reflected your lower expenses, by being
noticably lower, then that might well attract more customers...

just speculating.
legendary
Activity: 952
Merit: 1000
I wanted to have the bet #100,000.
But I didn't have any money on my wallet at that time, just if I was home   Sad
hero member
Activity: 488
Merit: 500


100.000 Bets!



Gratulations! This morning player alonsoj15 placed bet number 100.000!


Time for a short comparison:
  • On SDice these bets would have resulted in 100.000 payout transactions, of which ~50.000 would be just dust spam to notify that you lost.
  • On bitbattle.me these bets resulted in 4570 payout transaction. And not a single dust spam.

So you should know where to gamble if you care about blockchain bloat... Grin
hero member
Activity: 488
Merit: 500
It's been quite quiet here, so time for an intermediate update!
The new optional registration feature seems to work nicely, also site stability and performance has evolved nicely. We are only ~400 bets short of 100000 placed bets!

Right now I am working on three areas:
  • Upgrading my bitcoind backend to the 0.8 codebase
  • Usersettings so you can define your own bet limits, session limits, timeouts etc. (And probably an "incognito" playing mode)
  • API to enable integration with other websites, apps or implement gambling bots

The API is already coming along nicely - I hope to have it finished within the next few days, including a sample martingale bot implementation. Actually it is already working fine in my test environment, but still needs some cleanups and documentation. Only problem is the limited time i can spare for this at the moment :-)

And if you are following the discussion about SatoshiDice vs. the blocksize limit vs. dust spam transactions etc - I think it would be safe to recommend anybody to use bitbattle.me instead of SatoshiDice if you want to improve the situation here!
I don't think that the blocksize limit is a real issue by SatoshiDice - we would hit that limit anyway some time in the future. But what really bothers me is the blockchain bloat with the dust transactions. Using the blockchain for this kind of information is just plain wrong in my opinion.
hero member
Activity: 488
Merit: 500
Another small update:
Anonymous players now again can close their sessions with the old 30 seconds timeout. Registered players of course still can close their sessions without waiting!
hero member
Activity: 488
Merit: 500
Another small update:
Since closing a session is now only allowed for registered players: The 30 seconds waiting time until you can close a session is now removed - You can close your sessions without any waiting time Grin.
hero member
Activity: 488
Merit: 500
Okay, up and running with some major update - optional account registration!

  • The "Get started" page now contains a section for optional account creation.
  • 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.

Note that for account creation no email confirmation is necessary, so you can also register with fake email. However in this case there is no possibility to help you in case you forgot your password.
hero member
Activity: 488
Merit: 500
Site will be down a few minutes for upgrading...
hero member
Activity: 488
Merit: 500
So, any suggestions how to prove ownership of an existing player if the sign message feature is not available to you?

Blockchain-wallet users have some control over what addresses to make a transaction *from*, so
maybe requesting a new bet be made from the anonymous account's payout-address might work.

Still wouldn't work for instawallet(and equiv.)-users...
Good point. I was actually surprised that blockchain wallet does not provide the sign message feature. I think I saw it there before... Anyway for now I will only implement automatic verification based on bitcoins sign message feature. Other ways need to be done manually.

PS: I'm not sure about that "same name" business. Do they really use exactly
the same name,  and your software didn't already prevent it? Or is it just about
"looking" the same as by use of certain unicode-chars that look similar to ascii-chars?
Funny enough in the "slim"-example the scammer used slightly different names, probably expecting that the same name would be rejected ;-) But the site allows to use exactly the same name, as long as as the payout address is different. There is only a unique constraint on the combination name + payout address.
Really should have added that unique constraint on the name in the beginning...

Anyway, will start rolling out the update in a few minutes!
Pages:
Jump to: