As you can see here, I'm dedicated: http://www.crowdspring.com/logo-design/project/2379339_btc-cake-tasty-logo/

Who should I pick to win though?

And there, I have now started to add sending email! Currently you can enable to get an email for a cake result, but more to come! Nice to have that in place finally. Will make it easier to add "reset password" functionality.

There, I fixed so now you can reclaim your account if something with the cookie went wrong. There is a cookie created as soon as you access the site which just keeps track of your unique address. This one will live for about 68 years (limit of int32 size). If this cookie was deleted, or you use another browser or computer, a new one will be created. Then, you just use your unique url and login (if password is set) and click on "reclaim" button there.

And I've also tested so that you can't login to one account and then access someone else's without logging in! (this provided that the account has a password set on it).

I actually have an explainer video planned, but will take a while before that is ready. I'm pretty sure I will have one eventually though.

In short it's input to the end result generation. Every user can provide whatever they want here, and it is used to generate the end result. One small change of the salt change the end result completely. Basically this randomizes the result in a way no one knows how, but it enables a fair random result value where no one will have the control of what it will be.

Look under the Results -> Calculation in a cake where time is up for a more detailed way how it's done.

I can also mention that the slow response now is mainly because of the database. I'm pretty sure I've indexed proper keys, but I will look into this more deeply as well. I'm using a cloud based one, not locally, but still. It's taking a bit too long for the queries... Especially Dashboard is slow. Rest is better now. Still need to investigate why it's slow when I get the time...

Oh, haha, ok. Well, I will try. If someone that gets it can help me out that would be even better because I'm kinda blind to it being the one that have worked on this for so long.

Gordoh did help me write this: http://www.btccake.com/gettingstarted but maybe still too detailed...

Basically how it worked was that in the background the web browser made a connection to the btccake.com for about a minute. If something happened, a message would have been send through that connection. If not, the connection would timeout, and the web browser would reconnect again. And this would go on forever, just so if there were something happening at btccake.com, you would have been notified about it without having to reload the page. However, a misstake at btccake.com kept this connection open (or really didn't release it), even though you had disconnected.

Now, there is a limit on how many of these that can be open, so, as you can imagine, if a new connection was made from you every minute, it adds up. Especially because this is exactly the same for every new users too. And thus, when these open connections are too many, btccake.com (the server) can't handle any more and thus you can't access the site.

Makes more sense now?

Again, I'm sorry about that.

As I mention in my note on the dashboard, I disabled what I think was causing the problem. Live feedback and realtime chat won't work now, but that is also in the works using socket.io instead.

Alright! It's back up again!

Nah, it's only me atm actually. All done by me. From scratch even. But expanding will be fun. When/If this site is big enough with enough volume, I'm sure I will hire some that can help me out. The volume isn't large enough yet though. Which is good in a way, because I can deal with issues like this without too many angry people.

Yea, I'm really sorry about it guys. I wish I didn't have to be at this day job, and I could have fixed it by now... I will be back in about 3-4 hours so it should be back up then! Don't worry about your bitcoins or cakes though. It's there. It's just the server having too many connections open, and can't accept more. Some stupid bug somewhere...

Yea, I will! As soon as I get home!

I can enable SSH or whatever, but in a way I like it so closed down because that also means hackers will also have it difficult...

Also, you might get a page there and notice it's kinda old. It's because it's a cached page from cloudflare. So, basically just ignore that.

Meh, site is experiencing some issues, and I can't do anything about it for a few hours... I think there might be a bug with not closing connections properly, which is why when enough connect it adds up and it doesn't have more "file handles" left. I'm working on replacing the long-poll I have now with socket.io. Hopefully will this get rid of the bug AND make chatting a great reliable experience!

Sorry about that guys!

Yet another update.

I updated the result information:



Note the "Times of initial bet". I might rephrase that later, but anyway. It shows how many times your bet you get if you win.

Also note that this value is the same for everybody on the same wedge. Why? Because this is how fair this game is.

You can now also create private cakes. More on that later...

Alright, yet some more minor updates done. I added http://www.btccake.com/security that explains some precautions and security measures I do. Feel free to give me feedback on it.

Also, this one is funny: http://www.btccake.com/cake/192dbc8d5103c86fbdd29fc39dfa8df507a409520aaf51dac672f0b9e39fd6c7 and shows how things can change and how fair it is. One bet was made on wedge 1 at 0.00000643. Then I did a bet on wedge 2 at 0.00100000 which gave me 99% chance of winning. Then, gordoh comes in and puts a bet on wedge 1 at 0.00100000 giving wedge 1 the lead. Now, what is fun here is that this bet basically helps the user that had basically very low chance of winning now a larger chance of winning. gordoh will take the most, but it will be shared equally:

Currently wedge 1 has a 50.2% chance of winning. Wedge 2 49.8%. And, if wedge 1 wins it will be a fair split:


Cool huh?

Edit: Maybe I should post these updates on twitter instead... although this is more than 140 characters...

Since I'm back at my regular day job, development will be slowing down somewhat during the weekdays. Don't worry though, its quite robust as is so far, and I continue work on this whenever I can. I just wanted to notify you guys. This is something I really want to take off and be something I can work on more but I'm not there yet where this supports me.

Alright, I just put the account lockdown live!

If you have set a password for your account, and go to your profile you will be greeted by this now:




I love it because this really locks down your account even further. And, when time is up for that cookie you set there, you have to login again. Even if you happen to have that profile page open and try to do stuff, if time is up, I've put checks in place on server side, so you can't do anything before you login again!

(Note that "Forgot Password" doesn't work at the moment, so if you do have problems, message me and I can help you out. For this to work later on though, you would need an email set too)

Yet another cake that went well: http://www.btccake.com/cake/09a7ff8b77934d05dccabf972f175472233285882ba918e6e2095003402948b7

The amount in the tables there doesn't take into account that if the total to give to winners is less than 0.001, no fee is taken! In this case the total ended up to 0.00029000. I might increase that to 0.01 or so later actually. But anyway, that is why the winners got it all and the amount in the tables under the Wedges and "All bets" tabs are a bit less than what you actually got.

Alright, gotta love linux. Automatic backups are now in place! Both for the wallet and database! And, I've setup so it automatically sends the backup to my email. This way, I also have a backup "in the cloud".

Also, not only is the wallet encrypted, the zipped backup is also locked with a password. Hey, can't be paranoid enough eh?

And yes, I've tested to unpack it, and it works.

Backups are done and are send to my email every day! This is how serious I am about this. I sure as hell don't want to loose anyone’s data. And, because zipped data is password protected, it will not be easy to access even if someone got the backups.