|
Please tell me you took pics.
|
|
|
|
1. Lots of threads on bitcoin discussion are being moved to unrelated boards that no one reads Hopefully this will get people to read those sections. 2. Having a newbie section is derogatory, people should be able to post where they like. Registering an account is inconvenient enough without having to satisfy some random admin. I've always really disliked the newbie restrictions. It significantly reduces the quality of the entire community IMO because there are no "drive-by contributors" who would otherwise make up a large percentage of the community. However, the moderation tools currently available aren't good enough to protect the community if there were no newbie restrictions. In particular, at least these features are needed: - A much better report system. (Currently, moderators just receive reports via email, which is terrible.) - Better CAPTCHAs for newbies. Many bots are able to defeat the current CAPTCHAs. - A way to require that newbies from certain IPs must have their posts approved by moderators. (Spam and proxy IPs would be given this treatment.) - A page like this that shows only posts by newbies, so moderators and other helpful people can patrol newbie posts. Whats stopping you from changing the forum software? |
|
|
|
Somebody else better post here before I eat more druhgs and gamble the coins away.
18zSd8Ra4bioqQAfSVMqr8J6MtaY58xA31 |
|
|
|
Im assuming satoshidice ran out of money hence the delays in payout's then they raised the min's to screw all the small time martingaler's and bring the pot back up i could be *completely* wrong but it would appear that way
either way im stopping playing till the min's go back down ..
SD has not "ran out of money." November was actually one of the best months yet for house returns. I'd be willing to be December will be as well... I'm curious, can you guys (or someone) pull statistics for each one of your "bet addresses" to see just how far off their actual win percentage is from their win odds? If possible... I would love to see what they are from November 1 to present. |
|
|
|
|
5000 BTC
Just to keep the good old tradition.
|
|
|
|
You might want to wrap the amounts in floatval(); Also you need to json_encode the array that is the issue you can't just pass the array.
floatval() wrapping is valuable advice, as I found.  But the issue is that the array is organized in such a way as to use each address for the identifier of the element in the array. You cannot use the same ID in the same array twice, thus eliminating the possibility of conducting a sendmany with multiple outputs to the same address with this particular PHP code. Exactly. Is there any other way to do this? |
|
|
|
Bitcoin classes doesn't have a sendtomany function, but if you want to do sendtomany with a jsonRPCClient then you just need an array that is setup like $array("address"=>amount); or $array['address']=amount;
Cause you it will have to be ran thru json_encode to get it to the correct format.
I didn't realize he's using "Bitcoin Classes". I'm using jsonRPCClient to connect with bitcoind. I'm doing this: $to=Array( "1address" => 1, "1address" => 2 ); sendmany("from", $to); It will only send one payment to "1address". The problem is that it has a duplicated key, so it's impossible to send multiple payments to the same address in the same transaction using this method. blockchain.info allows us to do this, but I don't know how they do it. |
|
|
|
"Running sessions" -> Once a session is closed, remove it from the list.
Well, it should already do that. Do you mean the running sessions on the front page or on the player dashboard? Both. Once the session has >100 bets it starts to get slow, and after 200 bets it really gets slow 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... 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. 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. Yep, some payments were with "pending" state for several minutes. Thank you for your feedback, and i hope you come back soon with a few thousand more bets (maybe with some higher stake?)  I had a really bad experience with SD when I started playing with a higher stake  |
|
|
|
Use the move method to transfer balances from one account to another. Moves from the default account to any other account always succeed; moves from any other account will fail if the account has insufficient funds. Moves are not broadcast to the network, and never incur transaction fees; they just adjust account balances in the wallet.
The command listtransactions also shows the movements. { "account" : "Dest", "category" : "move", "time" : 1355141623, "amount" : 1.00000000, "otheraccount" : "Orig", "comment" : "" } |
|
|
|
Gratulations! You put some stress to my system which is exactly what a wanted to see :-) Bounty has been paid (txID 78b276cac6b7f086dc25707d4e71269131a9b29329a87c0524ee6b287b44c1be). Thank you |
|
|
|
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/)
|
|
|
|
|
Show Posts
