BetKing.io - 20% Rakeback Christmas Bonus - Most trusted Bitcoin Dice site

[Frosxh]

i would like to see the old software, however if its possible, adding more games is way much better. so i guess i would choose the old software + invest option but hopefully you can add some games as time goes

[erpbridge]

Old software seemed to be fine to me as well. Won't mind seeing it again. However only staying with dice might be a better appeal this time. It seemed that the site lost focus when I saw roulette and other games on there.

[lite]

A new software will be good, just take your time to develop it heh. will the new software include investment option?

[Jungian]

Looks like most people want it back now, which is quite understandable. We loves the site and we don't want to wait.

Why not reopen it now, and add some features along the way later?

[BTCevo]

if you are going to be back for real. You really need to get more players to play on your site back. Dont know if there will be many big whale to play back on your site or not since your site becoming ico. And may be what i really want to see is some new game with good amount of jackpot though. And of course with huge bankroll jackpot will be huge for sure. This will attract many people to come too

[seuntjie]

Would new software have a decent API?

[BetKing.io]

Would new software have a decent API?

Yes.

The whole point of new software is to be able to go back with a fresh start and do things right building on the 4 years of experience I now have.

Dice is very simple but the tech behind it would include:
Proper REST API
Easier maintenance and deployment.
Easier to add new features, games or bug fixes
Better scalability and performance
Better auditing and security
3rd party app support

I've already started that for the new version. Dice game is done (including API).
Considering the response I think it might be best to launch dice after the new framework is in place and then add games/features as they are done (no rushing them this time).

I wanted to come back with a huge release and ad campaign but if say dice, casino and sports were all ready to go it probably isn't worth it from a business point to wait x months until poker was ready for example.

[seuntjie]

Would new software have a decent API?

Yes.

The whole point of new software is to be able to go back with a fresh start and do things right building on the 4 years of experience I now have.

Dice is very simple but the tech behind it would include:
Proper REST API
Easier maintenance and deployment.
Easier to add new features, games or bug fixes
Better scalability and performance
Better auditing and security
3rd party app support

I've already started that for the new version. Dice game is done (including API).
Considering the response I think it might be best to launch dice after the new framework is in place and then add games/features as they are done (no rushing them this time).

I wanted to come back with a huge release and ad campaign but if say dice, casino and sports were all ready to go it probably isn't worth it from a business point to wait x months until poker was ready for example.

Cool. I support this decision.

Will you send me an email when you're testing the site or about a week before you launch so I can have DiceBot ready for the launch please?

[LoyceV]

Do you want BetKing to open back up?
- Yes - Now with same software + invest option
- Yes - New software (open around august-october)
- No -

I've had a month and a half break and looked at other projects and nothing really jumps out as things I want to do for next 3+ years.

I'm leaning towards the middle answer, create new software in own time and get it perfect and exactly how I wanted it then launch, stress free.

Launching the same product now would mean new software would take even longer to finish due to supoprt and running the site and it doesn't provide anything new just putting the site back on.

Why don't you hire someone to do support and run the site? In my opinion it's clear you wanted your time off, but the site was profitable enough to keep running without you personally having to worry about it. Closing the site seemed like capital destruction, but if you don't mind about that, good for you!

What do you think?

You asked for it Do whatever you want Just think about the reason why you closed it in the first place. If that didn't change, why would you open it again?

[kpcian]

I think you should re-open the site with old software + invest option. And you can work for the new software, when the work is done, you can just release the new software with more platforms.

The point to re-open is you won't lose your old players and maybe some people decided to gave up bitcoin after they heard betking.io is closed !

Would be really nice if you open betking again.

[BetKing.io]

Would new software have a decent API?

Yes.

The whole point of new software is to be able to go back with a fresh start and do things right building on the 4 years of experience I now have.

Dice is very simple but the tech behind it would include:
Proper REST API
Easier maintenance and deployment.
Easier to add new features, games or bug fixes
Better scalability and performance
Better auditing and security
3rd party app support

I've already started that for the new version. Dice game is done (including API).
Considering the response I think it might be best to launch dice after the new framework is in place and then add games/features as they are done (no rushing them this time).

I wanted to come back with a huge release and ad campaign but if say dice, casino and sports were all ready to go it probably isn't worth it from a business point to wait x months until poker was ready for example.

Cool. I support this decision.

Will you send me an email when you're testing the site or about a week before you launch so I can have DiceBot ready for the launch please?

Will do. Thanks.

I'm actually in two minds wether to open source it or not so others can contribute.
Two things putting me off that decision are:
1) Someone finds an exploit and doesn't report it but uses it
2) If in 2-3 years some big company wishes to buy BetKing, would they knowing the software is out there for free?

I'm not worried about anyone taking it and starting own site because they would still need bankroll and trust to attract players.

[game-protect]

Will do. Thanks.

I'm actually in two minds wether to open source it or not so others can contribute.
Two things putting me off that decision are:
1) Someone finds an exploit and doesn't report it but uses it
2) If in 2-3 years some big company wishes to buy BetKing, would they knowing the software is out there for free?

I'm not worried about anyone taking it and starting own site because they would still need bankroll and trust to attract players.

1) For security reasons, I don't recommend to open source your code

2) If they google for it, likely yes.

The most value of BetKing.io is the trust you have built, with sending investor balances back. I will be gladly add you to the Game Protect website.

[BetKing.io]

I'm actually in two minds wether to open source it or not so others can contribute.
Two things putting me off that decision are:
1) Someone finds an exploit and doesn't report it but uses it
2) If in 2-3 years some big company wishes to buy BetKing, would they knowing the software is out there for free?

Yeah, 1) is concerning. Not only does open source make it easier to find attack vectors, it makes it easier to abuse them. Of course, it's never a good idea to rely on obscurity -- but it makes a good defensive layer.

2) I don't think I'd worry about. I think as long as the license allows you to relicense it, I'm not sure it'd be a big deal. Big companies buy companies for the player base and brand, not the code itself.


I guess the middle ground is to open source the front end, but not the back end. It largely avoids all the security risk stuff, but unless it's easy for people to run their own dev copy it might be hard to get contributors

100% agree there.
I'll open source the front end but not back. The front is more useful anyway as it allows players to mod things if they like.

[seuntjie]

I'm actually in two minds wether to open source it or not so others can contribute.
Two things putting me off that decision are:
1) Someone finds an exploit and doesn't report it but uses it
2) If in 2-3 years some big company wishes to buy BetKing, would they knowing the software is out there for free?

Yeah, 1) is concerning. Not only does open source make it easier to find attack vectors, it makes it easier to abuse them. Of course, it's never a good idea to rely on obscurity -- but it makes a good defensive layer.

2) I don't think I'd worry about. I think as long as the license allows you to relicense it, I'm not sure it'd be a big deal. Big companies buy companies for the player base and brand, not the code itself.


I guess the middle ground is to open source the front end, but not the back end. It largely avoids all the security risk stuff, but unless it's easy for people to run their own dev copy it might be hard to get contributors

100% agree there.
I'll open source the front end but not back. The front is more useful anyway as it allows players to mod things if they like.

In my bed-time life contemplations I've considered writing and opening an almost open source casino a few times. My conclusion every time was to write a separate library that handles all of the game logic (like RNG, hit registering, win/lose, returns etc) and open source that, but keep the datalayer and other business layers closed

[jamyr]

I'm actually in two minds wether to open source it or not so others can contribute.
Two things putting me off that decision are:
1) Someone finds an exploit and doesn't report it but uses it
2) If in 2-3 years some big company wishes to buy BetKing, would they knowing the software is out there for free?

Yeah, 1) is concerning. Not only does open source make it easier to find attack vectors, it makes it easier to abuse them. Of course, it's never a good idea to rely on obscurity -- but it makes a good defensive layer.

2) I don't think I'd worry about. I think as long as the license allows you to relicense it, I'm not sure it'd be a big deal. Big companies buy companies for the player base and brand, not the code itself.


I guess the middle ground is to open source the front end, but not the back end. It largely avoids all the security risk stuff, but unless it's easy for people to run their own dev copy it might be hard to get contributors

100% agree there.
I'll open source the front end but not back. The front is more useful anyway as it allows players to mod things if they like.

its official then?

[rubiprojects]

I'm actually in two minds wether to open source it or not so others can contribute.
Two things putting me off that decision are:
1) Someone finds an exploit and doesn't report it but uses it
2) If in 2-3 years some big company wishes to buy BetKing, would they knowing the software is out there for free?

Yeah, 1) is concerning. Not only does open source make it easier to find attack vectors, it makes it easier to abuse them. Of course, it's never a good idea to rely on obscurity -- but it makes a good defensive layer.

2) I don't think I'd worry about. I think as long as the license allows you to relicense it, I'm not sure it'd be a big deal. Big companies buy companies for the player base and brand, not the code itself.


I guess the middle ground is to open source the front end, but not the back end. It largely avoids all the security risk stuff, but unless it's easy for people to run their own dev copy it might be hard to get contributors

100% agree there.
I'll open source the front end but not back. The front is more useful anyway as it allows players to mod things if they like.

Dean, you are best and very selfless. Other sites will refer your codes, that is for sure. And keep the back end in close source to avoid more copycats. You enjoy your good life. 

[LoyceV]

An Open Source front end would allow a scam-site to easily copy it. You may want to consider this before publishing sources.

[BetKing.io]

Been playing with some design for new front end.
Here's the phone version. What do you think?
The dropdown button next to balance is so you can change currency.

[Dice-Bet]

Been playing with some design for new front end.
Here's the phone version. What do you think?
The dropdown button next to balance is so you can change currency.

For me the old bold colors you had in the background were better.

[joksim299]

Been playing with some design for new front end.
Here's the phone version. What do you think?
The dropdown button next to balance is so you can change currency.

Hire designer.