Topic: Peerbet.org - Play without house edge! - page 15. (Read 106648 times)
The bug causing empty string in the chat PMs that was sent via API have been fixed!
Now you can send chat message to the concrete user, for example:
Bot owners, please update your scripts to make chat more readable for real users.
Code:
%user name, Hello, this is private message!
(comma is the delimiter, username can contain spaces)
Bot owners, please update your scripts to make chat more readable for real users.
We are happy to announce bonuses for the Peerbet website and Android app translation. You can earn 0.01-0.1 BTC depending from the localization value to the Peerbet (i.e. popular languages will be rewarded higher). You need to translate website's locale files and Android app's strings.xml.
If you are interested in, write what languages do you know.
I could do Polish translation. From the second one it's this /Peerbet_src/res/values/strings.xml file only?If you are interested in, write what languages do you know.
We are happy to announce bonuses for the Peerbet website and Android app translation. You can earn 0.01-0.1 BTC depending from the localization value to the Peerbet (i.e. popular languages will be rewarded higher). You need to translate website's locale files and Android app's strings.xml.
If you are interested in, write what languages do you know.
I could do Polish translation. From the second one it's this /Peerbet_src/res/values/strings.xml file only? If you are interested in, write what languages do you know.
You can remove users from chat mute list with "/unignore username" command.
I like it. I blogged recently about a bias I noticed will small (i.e. 50) sets of (contiguous) hashes showing drastic skew, although with much larger sets (i.e. 1,000,000) this was eliminated entirely. I will retry with this new algorithm and see if small sets show improved probability. Thanks!
Winning ticket determination algorithm have changed to increase produced random number quality. The bias described above was completely eliminated.
Previous version (use for verification of the raffles completed before March 26, 2013, 03:15 UTC):
Code:
function getWinningTicket($nonce, $blockHash, $ticketsTotal)
{
$randMax = 268435455;
$remainder = $randMax % $ticketsTotal;
$output = -1;
do {
$hash = hash('sha256', $nonce . $blockHash);
$randHex = substr($hash, strlen($hash) - 7, 7);
$x = base_convert($randHex, 16, 10);
$output = $x % $ticketsTotal;
$nonce .= '0';
}
while($x >= ($randMax - $remainder));
return $output + 1;
}
Previous version (use for verification of the raffles completed before March 26, 2013, 03:15 UTC):
Code:
function getWinningTicket($nonce, $blockHash, $ticketsTotal)
{
$hash = hash('sha256', $nonce . $blockHash);
$randHex = substr($hash, strlen($hash) - 7, 7);
$randDec = base_convert($randHex, 16, 10);
return ($randDec % $ticketsTotal) + 1;
}
I can translate from English to Italian and from Spanish to Italian aswell,
i'm a native italian/spanish speaker.(Parents from both sides, i've lived in italy and spanish country aswell for years, right now i'm in Italy)
if you need me contact me to see how much work is it
Someone already took Italian translation, but said that he is very busy in near time. You can start working on Italian locale. i'm a native italian/spanish speaker.(Parents from both sides, i've lived in italy and spanish country aswell for years, right now i'm in Italy)
if you need me contact me to see how much work is it
I can translate from English to Italian and from Spanish to Italian aswell,
i'm a native italian/spanish speaker.(Parents from both sides, i've lived in italy and spanish country aswell for years, right now i'm in Italy)
if you need me contact me to see how much work is it
i'm a native italian/spanish speaker.(Parents from both sides, i've lived in italy and spanish country aswell for years, right now i'm in Italy)
if you need me contact me to see how much work is it
I just thought: because you wrote about this flaw, you could also suggest how to correct it.
You know, I did suggest the stackexchange post, which has what I think is the correct algorithm.
Quote
I have implemented new random algorithm that solves bias flaw. Please ensure that it is correct.
With the caveat that I'm not a PHP programmer at all, it looks right to me.
I have implemented new random algorithm that solves bias flaw. Please ensure that it is correct.
Code:
function getWinningTicket($nonce, $blockHash, $ticketsTotal)
{
$randMax = 268435455;
$remainder = $randMax % $ticketsTotal;
$output = -1;
do {
$hash = hash('sha256', $nonce . $blockHash);
$randHex = substr($hash, strlen($hash) - 7, 7);
$x = base_convert($randHex, 16, 10);
$output = $x % $ticketsTotal;
$nonce .= '0';
}
while($x >= ($randMax - $remainder));
return $output + 1;
}
If you don't want to do it, don't do it. I was just giving feedback based the incorrect algorithm you posted on the forum.
I never said that I don't want to change the algorithm. I just thought: because you wrote about this flaw, you could also suggest how to correct it. Hi, I made a few security tests on your site. I didn't find any SQL injection vulnerability, but I found out a way to do XSS attack. Is there any bounty for that? 
I can add some credits to play on your Peerbet account.
Hi, I made a few security tests on your site. I didn't find any SQL injection vulnerability, but I found out a way to do XSS attack. Is there any bounty for that?
But anyway, another algorithm would be to increment the nonce and generate a new hash. Again, you do this deterministically only when the first hash falls in the bad range.
Suggest working PHP version of the algorithm with nonce increment and I will update Peerbet scripts.I'm not a PHP coder.
If you don't want to do it, don't do it. I was just giving feedback based the incorrect algorithm you posted on the forum.
But anyway, another algorithm would be to increment the nonce and generate a new hash. Again, you do this deterministically only when the first hash falls in the bad range.
Suggest working PHP version of the algorithm with nonce increment and I will update Peerbet scripts. You are right, but some users may incorrectly understand why some blocks being rejected and just stop playing. Suggest another algorithm without this disadvantage.
BTW, I still don't understand why change of algorithm is necessary when skewness does not (statistically significant) affect fairness of the game?
Your statements are contradictory here. If the bias is very small (which it is), then blocks won't be skipped very often and users won't have anything to be upset about. It's not going to happen very often, if ever. But as things stand now you can't (honestly) say that your game is "fair." You can say that the bias is "small" and users might be okay with that, or they might not. BTW, I still don't understand why change of algorithm is necessary when skewness does not (statistically significant) affect fairness of the game?
But anyway, another algorithm would be to increment the nonce and generate a new hash. Again, you do this deterministically only when the first hash falls in the bad range.
You misunderstand. The discarding is entirely deterministic based on the formula. There is no way for the administrator to exploit that. i.e. still provably fair.
You are right, but some users may incorrectly understand why some blocks being rejected and just stop playing. Suggest another algorithm without this disadvantage.BTW, I still don't understand why change of algorithm is necessary when skewness does not (statistically significant) affect fairness of the game?
Discarding blocks can let users to think that Peerbet operator tries to play against its users
You misunderstand. The discarding is entirely deterministic based on the formula. There is no way for the administrator to exploit that. i.e. still provably fair.
my username: samurajj
Jump to: