I think it is a good idea to spoil your users including myself, thank you for your information
Topic: BetterBets.io |V2 NXT betting + Shapeshift.io|🎲 DICE★PLINKO★PVP Game CORE - page 12. (Read 315714 times)
January 26, 2017, 03:30:41 AM
January 25, 2017, 07:18:33 PM
January 25, 2017, 05:34:23 PM
Welp...apparently the NXT desktop default passphrase isn't the actual passphrase for your account. Thanks for the 3400 NXT anyway guys 
Hi fiscorcle, Nxt client login and BetterBets.io login are 2 different animals.
Regards
I know, but the first account you setup on desktop NXT isn't the one that it logs into apparently *shrugs*
Email me [email protected] or PM me on Janus slack user bjorn_bb ( https://nxtchat.slack.com/messages/janusproject/details/ )and I will assist you with this 3400 NXT, these were intended to be a nice gesture from our team that I'd rather you not miss out on.
Sent you an email! Would appreciate any help you can provide
January 25, 2017, 02:48:13 PM
Welp...apparently the NXT desktop default passphrase isn't the actual passphrase for your account. Thanks for the 3400 NXT anyway guys
Hi fiscorcle, Nxt client login and BetterBets.io login are 2 different animals.
Regards
I know, but the first account you setup on desktop NXT isn't the one that it logs into apparently *shrugs*
Email me [email protected] or PM me on Janus slack user bjorn_bb ( https://nxtchat.slack.com/messages/janusproject/details/ )and I will assist you with this 3400 NXT, these were intended to be a nice gesture from our team that I'd rather you not miss out on.
January 25, 2017, 02:24:49 PM
Welp...apparently the NXT desktop default passphrase isn't the actual passphrase for your account. Thanks for the 3400 NXT anyway guys
Hi fiscorcle, Nxt client login and BetterBets.io login are 2 different animals.
Regards
I know, but the first account you setup on desktop NXT isn't the one that it logs into apparently *shrugs*
That issue never happened to me. Try to contact Nxt helpdesk on slack https://nxtchat.herokuapp.com
edit: check if is something related to a typo or caps.
January 25, 2017, 02:21:35 PM
Welp...apparently the NXT desktop default passphrase isn't the actual passphrase for your account. Thanks for the 3400 NXT anyway guys
Hi fiscorcle, Nxt client login and BetterBets.io login are 2 different animals.
Regards
I know, but the first account you setup on desktop NXT isn't the one that it logs into apparently *shrugs*
January 25, 2017, 11:10:46 AM
Welp...apparently the NXT desktop default passphrase isn't the actual passphrase for your account. Thanks for the 3400 NXT anyway guys
Hi fiscorcle, Nxt client login and BetterBets.io login are 2 different animals.
Regards
January 25, 2017, 10:59:21 AM
Welp...apparently the NXT desktop default passphrase isn't the actual passphrase for your account. Thanks for the 3400 NXT anyway guys
January 25, 2017, 09:25:41 AM
S O M E G O O D A C T I O N Y E S T E R D A Y!
January 25, 2017, 07:44:27 AM
Nice update. I am not sure if you updated the provably fair implementation now or already before, but I just had a proper look again. The implementation looks now very close to perfect I happily activated your site on my site again. There are still some smaller things that could be fixed:
1. Changing the client seed manually doesn't actually work (but "generate new" button does work.) So needs some change event listener that puts the new clientseed in the JS var and localstorage.
I happily activated your site on my site again. There are still some smaller things that could be fixed:1. Changing the client seed manually doesn't actually work (but "generate new" button does work.) So needs some change event listener that puts the new clientseed in the JS var and localstorage.
Thank you, will fix ...
2. Ideally the function verifyRoll() will also check the HASH which is the first part of verifying a result. So something like this:
Code:
if (activeCoin == 'btc') {
if (sha256(vSecret+'|'+vSalt) != vServerSeed) alert('Oh noes - serverseed hash changed! Contact site owner to see what happened or manually verify your bet.');
return (Math.floor((100 / Math.pow(2, 32) * ((vSecret + vClientSeed) % Math.pow(2, 32))) * 100) / 100).toFixed(2);
}
Obviously that alert should never happen though if (sha256(vSecret+'|'+vSalt) != vServerSeed) alert('Oh noes - serverseed hash changed! Contact site owner to see what happened or manually verify your bet.');
return (Math.floor((100 / Math.pow(2, 32) * ((vSecret + vClientSeed) % Math.pow(2, 32))) * 100) / 100).toFixed(2);
}
Will also add (thank you!)
3. If you use the above code, you would be checking the hash that you got after the bet. But you should check the hash that you saved before the bet (just for the theoretical situation where MP tries to cheat by changing the hash too.) You put this serverseed(=hash) already in the box with insertProvablyFairHtml() before the bet. So you can simply remove the following line from updateProvablyFairHtml() to ensure you verify the hash that you got before the bet:
Code:
// $('#newBetServerSeed').html(response['serverSeed']).hide().fadeIn(delay);
Will also fix ...
4. It says "Next Bet" in the second box, but that is actually the "Previous bet" 
Silly me :-)
Still I believe your provably fair implementation is now superior to almost all "per-roll implementations", so these are just smaller things that should be easy to fix
That is high praise coming from you, appreciate it. I'll fix the above issues sometime today; very much appreciate your feedback.
PS, I only tested Dice-BTC. Perhaps I can look at Plinko and NXT some other time if you want.
Plinko isn't implemented in the verifier yet because it uses a different algorithm to determine the final slot the ball falls into (it still uses the hash/seed and everything else, but it doesn't just compute it down to a single number using a single-calculation algorithm). I just didn't get around to implementing this.
NXT uses a different system to compute the roll result (taken from primedice) but now that you mention it, we could actually unify the logic for both coins, there's no real reason to have 2 algorithms in place. I will work on unifying the code so that both/all coins are treated identically.
Once again, thanks a lot for your feedback. I'll let you know when these changes are done.
January 25, 2017, 12:41:04 AM
Nice update. I am not sure if you updated the provably fair implementation now or already before, but I just had a proper look again. The implementation looks now very close to perfect I happily activated your site on my site again. There are still some smaller things that could be fixed:
1. Changing the client seed manually doesn't actually work (but "generate new" button does work.) So needs some change event listener that puts the new clientseed in the JS var and localstorage.
2. Ideally the function verifyRoll() will also check the HASH which is the first part of verifying a result. So something like this:
3. If you use the above code, you would be checking the hash that you got after the bet. But you should check the hash that you saved before the bet (just for the theoretical situation where MP tries to cheat by changing the hash too.) You put this serverseed(=hash) already in the box with insertProvablyFairHtml() before the bet. So you can simply remove the following line from updateProvablyFairHtml() to ensure you verify the hash that you got before the bet:
4. It says "Next Bet" in the second box, but that is actually the "Previous bet"
Still I believe your provably fair implementation is now superior to almost all "per-roll implementations", so these are just smaller things that should be easy to fix
PS, I only tested Dice-BTC. Perhaps I can look at Plinko and NXT some other time if you want.
I happily activated your site on my site again. There are still some smaller things that could be fixed:1. Changing the client seed manually doesn't actually work (but "generate new" button does work.) So needs some change event listener that puts the new clientseed in the JS var and localstorage.
2. Ideally the function verifyRoll() will also check the HASH which is the first part of verifying a result. So something like this:
Code:
if (activeCoin == 'btc') {
if (sha256(vSecret+'|'+vSalt) != vServerSeed) alert('Oh noes - serverseed hash changed! Contact site owner to see what happened or manually verify your bet.');
return (Math.floor((100 / Math.pow(2, 32) * ((vSecret + vClientSeed) % Math.pow(2, 32))) * 100) / 100).toFixed(2);
}
Obviously that alert should never happen though if (sha256(vSecret+'|'+vSalt) != vServerSeed) alert('Oh noes - serverseed hash changed! Contact site owner to see what happened or manually verify your bet.');
return (Math.floor((100 / Math.pow(2, 32) * ((vSecret + vClientSeed) % Math.pow(2, 32))) * 100) / 100).toFixed(2);
}
3. If you use the above code, you would be checking the hash that you got after the bet. But you should check the hash that you saved before the bet (just for the theoretical situation where MP tries to cheat by changing the hash too.) You put this serverseed(=hash) already in the box with insertProvablyFairHtml() before the bet. So you can simply remove the following line from updateProvablyFairHtml() to ensure you verify the hash that you got before the bet:
Code:
// $('#newBetServerSeed').html(response['serverSeed']).hide().fadeIn(delay);
4. It says "Next Bet" in the second box, but that is actually the "Previous bet"
Still I believe your provably fair implementation is now superior to almost all "per-roll implementations", so these are just smaller things that should be easy to fix
PS, I only tested Dice-BTC. Perhaps I can look at Plinko and NXT some other time if you want.
January 24, 2017, 07:49:08 PM
L I V E !!
Betterbets V2 (2017-01-22) #updates:
1- The entire old codebase was refactored into a properly modularized, namespaced and object-oriented codebase running on a proven micro-framework;
2- Every access point is now a proper route which is centrally access controlled; the application does not contain any hardcoded URLs anymore;
3- HTML output is produced through a modern, sandboxed template engine;
4- The original database design was properly normalized but almost all read operations still operate using a single query;
5- #4 means that new coins can be added without changing code;
6- The old database code was refactored to use a modern ORM layer;
7- Previously hacky remote call code was re-implemented using a modern RPC library;
8- The resulting codebase is E_ALL clean and much easier to understand, maintain and extend;
9- Support for luck-forging, raffle tickets and bet-mining was removed;
10- Several long-standing bugs and oddities were fixed both on the front- and back-end.
***We have extensively tested the site and believe that it's solid but as this is essentially a brand-new site/codebase, please let us know if something breaks. We will be monitoring things closely over the next few days, but we appreciate your understanding during this 'startup' phase.
Remember, Remember The 15th Of December:
All players who bet over 5 BTC volume should see an NXT credit of 3400 NXT.
All players who bet over 5 BTC volume should see an NXT credit of 3400 NXT.
Shapeshift is very simple as well to deposit NXT into your account, give it a try
January 24, 2017, 07:01:50 PM
January 24, 2017, 04:22:35 PM
January 24, 2017, 04:19:56 PM
You're all bitches
If you guys wanna have a good laugh have an entertaining read at this person's post history
https://bitcointalksearch.org/user/pokop-937810
January 24, 2017, 03:56:40 PM
You're all bitches
January 24, 2017, 08:47:08 AM
What happens to the Rbies that was in my bb wallet?
Hi B_UN1T, all RBIES balances/data is stored. The wallet will be open to deposit/withdrawal after Moneypot launch the new API version, which will allow R2B2 betting.
- The BetterBets staff
January 24, 2017, 08:34:35 AM
Very nice to see the site back online and glad you fixed everything for the punters. I really wish I could have a flutter but online gambling is not allowed in Southern Cyprus, which is quite weird lol because they have plenty of horse betting shops so that's a bit annoying.
January 24, 2017, 06:17:55 AM
What happens to the Rbies that was in my bb wallet?
January 24, 2017, 12:16:33 AM
Our apologies everyone, we discovered a Cloudflare issue that may have prevented some users from accessing the site, please try now if you had issues yesterday, thanks!
https://betterbets.io
https://betterbets.io
Jump to: