ChainProfit.com - 27+ BTC Paid | 140% Return | Running over four months now

[szycha]

When user enters Dashboard, you generate new, unique ID (you ensure uniqueness by using big numbers like 256-bit, or maintain a db of already used IDs - this could be as simple as two column table - ID + timestamp - upon generation you check if it has not been used within last 5-6 days).

at this point you have dashboard with new hidden unique-id field, that has never been used (submitted) before.

Note: you do not write the id to the table now.

When user submits his/her bet, first thing you do is to check whether it has already been used. If yes, proper message is thrown straight to the user face :-)
If no, bet is accepted and id is added to table.

old (stale) ids could be cleaned once per day via cron job, or per bet submission, or per unsuccessful bet submission <- my favorite option, means: random, but frequently enough.

If you stick to 5 days worth of IDs, you would end up with a table similar to active part of dashboard, which is as per now about 43 records.

Perhaps our friend used some broken browser (msie?) :-) that did not ask him / her about form re-submission; or is a victim of some malware?

Can I submit my CV for a position of project technical lead at CrazyPonzi.com? :-)

--
Best regards,
(-) Szycha.

[CrazyJoker]

When user enters Dashboard, you generate new, unique ID (you ensure uniqueness by using big numbers like 256-bit, or maintain a db of already used IDs - this could be as simple as two column table - ID + timestamp - upon generation you check if it has not been used within last 5-6 days).

at this point you have dashboard with new hidden unique-id field, that has never been used (submitted) before.

Note: you do not write the id to the table now.

When user submits his/her bet, first thing you do is to check whether it has already been used. If yes, proper message is thrown straight to the user face :-)
If no, bet is accepted and id is added to table.

old (stale) ids could be cleaned once per day via cron job, or per bet submission, or per unsuccessful bet submission <- my favorite option, means: random, but frequently enough.

If you stick to 5 days worth of IDs, you would end up with a table similar to active part of dashboard, which is as per now about 43 records.

I understand what you are saying, but I still fail to understand how this will solve the problem faced by SS2006 ? Because, user may want to submit two consecutive bets standing on the dashboard, which would have same effect of refreshing the page. If the first (desired action) is allowed, second (undesired action) will be automatically allowed. Rather, I can add an extra check box, which will be unchecked in each page load. Form will be submitted, only if this box is checked. But, this would probably create a bad user experience. So, I'm keeping it at hand as last resort.

Perhaps our friend used some broken browser (msie?) :-) that did not ask him / her about form re-submission; or is a victim of some malware?

I dont think it is malware, because in that case he would have faced this problem for all his bets. It might be an old browser. May be some mobile browser too. Unless he clarifies, we will never know.

Can I submit my CV for a position of project technical lead at CrazyPonzi.com? :-)

--
Best regards,
(-) Szycha.

LoLz... let this project grow.

[SS2006]

This is the best site. it's more of a gamblinb site, then a ponzi. Just like a roulette table.

[CrazyJoker]

This is the best site. it's more of a gamblinb site, then a ponzi. Just like a roulette table.

Nice to know that you liked the game. In fact, I am working on a rebranding - https://bitcointalk.org/index.php?topic=1065588.0

[szycha]

When user enters Dashboard, you generate new, unique ID (you ensure uniqueness by using big numbers like 256-bit, or maintain a db of already used IDs - this could be as simple as two column table - ID + timestamp - upon generation you check if it has not been used within last 5-6 days).

at this point you have dashboard with new hidden unique-id field, that has never been used (submitted) before.

Note: you do not write the id to the table now.

When user submits his/her bet, first thing you do is to check whether it has already been used. If yes, proper message is thrown straight to the user face :-)
If no, bet is accepted and id is added to table.

old (stale) ids could be cleaned once per day via cron job, or per bet submission, or per unsuccessful bet submission <- my favorite option, means: random, but frequently enough.

If you stick to 5 days worth of IDs, you would end up with a table similar to active part of dashboard, which is as per now about 43 records.

I understand what you are saying, but I still fail to understand how this will solve the problem faced by SS2006 ? Because, user may want to submit two consecutive bets standing on the dashboard, which would have same effect of refreshing the page. If the first (desired action) is allowed, second (undesired action) will be automatically allowed. Rather, I can add an extra check box, which will be unchecked in each page load. Form will be submitted, only if this box is checked. But, this would probably create a bad user experience. So, I'm keeping it at hand as last resort.

When hitting F5 or Ctrl+R (or ^R in short notation) browser resubmits the entire form (i.e. all key-value pairs that were submitted previously), even if new form is already displayed in browser window. But this time you have old ID in your table and you can politely refuse accepting new-old bet.

There is much simpler method: after receiving a POST from web form, use redirect (header("Location: /")) to move player one step further. Thus, when he/she will press F5 next time, new page (GET /) will be reloaded, not the old one.

Can I submit my CV for a position of project technical lead at CrazyPonzi.com? :-)

--
Best regards,
(-) Szycha.

LoLz... let this project grow.

You do not know my financial expectations yet. They will not kill the project - they will grow with it instead ;-)

--
Cheers,
(-) Szycha.

[tidus1097]

Ok I tried out your "game" with 0.01BTC. When I played your game I added 0.01 to the game. Luckily other players did deposit more btc. 1st time I got 0.014 which was the 40% stated in your game. Ok. Round 2. I played 0.01 again. More people played. I got paid 0.0126 not 0.014. Is that your fee? I thought it was 40% return+ your initial bet for a total of 140% By my calculations you the game owes me 0.0014. 0.0126+0.0014=0.014

[TigerMart]

Ok I tried out your "game" with 0.01BTC. When I played your game I added 0.01 to the game. Luckily other players did deposit more btc. 1st time I got 0.014 which was the 40% stated in your game. Ok. Round 2. I played 0.01 again. More people played. I got paid 0.0126 not 0.014. Is that your fee? I thought it was 40% return+ your initial bet for a total of 140% By my calculations you the game owes me 0.0014. 0.0126+0.0014=0.014

I think, your calculation was wrong at the first time. It was indeed correct for the second time. The actual return to a palyer against a bet of 0.01 BTC is always 0.0126 BTC not 0.014 BTC. When signed in, if you click on your Bet ID, it shows you the actual return of the bet. 10% is the site commission, out of which 5% goes to the owner and 5% goes to your referrer (or to the owner again if you have no referrer). It is clearly stated in their FAQ as well...

2. How to play this game ?

A: If you have bitcoin, then it is very easy. Simply sign up and deposit the amount of bitcoin you want to play with. Now, mention the amount you want to invest in a round in the dashboard and click play. When there will be enough bitcoin deposited by other investors after you to return 140% of your investment, it will automatically be returned to you after deducting 10% commission.

Off topic - @tidus1097 Is there any avatar campaign going on for bitcoin knives ? Then I'd like to join

[tidus1097]

Ok I tried out your "game" with 0.01BTC. When I played your game I added 0.01 to the game. Luckily other players did deposit more btc. 1st time I got 0.014 which was the 40% stated in your game. Ok. Round 2. I played 0.01 again. More people played. I got paid 0.0126 not 0.014. Is that your fee? I thought it was 40% return+ your initial bet for a total of 140% By my calculations you the game owes me 0.0014. 0.0126+0.0014=0.014

I think, your calculation was wrong at the first time. It was indeed correct for the second time. The actual return to a palyer against a bet of 0.01 BTC is always 0.0126 BTC not 0.014 BTC. When signed in, if you click on your Bet ID, it shows you the actual return of the bet. 10% is the site commission, out of which 5% goes to the owner and 5% goes to your referrer (or to the owner again if you have no referrer). It is clearly stated in their FAQ as well...

2. How to play this game ?

A: If you have bitcoin, then it is very easy. Simply sign up and deposit the amount of bitcoin you want to play with. Now, mention the amount you want to invest in a round in the dashboard and click play. When there will be enough bitcoin deposited by other investors after you to return 140% of your investment, it will automatically be returned to you after deducting 10% commission.

Off topic - @tidus1097 Is there any avatar campaign going on for bitcoin knives ? Then I'd like to join

Ah, thank you for the clarification. That does make sense now. As for the bitcoin-knives, no unfortunately a major of order of mine was misdirected and lost by the PO. I'm in the process now of claims with them :/ Once I do get my shipment, I can resume updating the site with more knives. Unfortunately I cannot purchase no more til I get this resolved with the PO. So right now it would not be buisness wise to invest in advertising since I don't have much I can sell right now 

[szycha]

Tactical wait... OK
@SS2006: are you loosing this time?

--
Cheers,
(-) Szycha.

[szycha]

Or maybe a new, big investor will save us? Anyone willing to loose his/her money? metwuerst? thedreamer? :-)

[SS2006]

I won't lose I have a calculated plan

[CrazyJoker]

Probably, all of you have noticed that I have added some functionalities in the table. Hopefully, all of you like it...

It is amazing to see that the game kept rolling even when BitcoinTalk was down. Withdrawals happened everyday as usual. Details: www.crazyponzi.com/proof.php

Here is today's withdrawal: https://blockchain.info/tx/0f899ce0b86f94da34dea9a2a5dc0bfd327c0b3eab514a7dcdca6c4469fae084

Keep playing...

[andolini82]

This investing still running? Or many of u only give share personal experience when using this investing site??

[dannyprats]

This investing still running? Or many of u only give share personal experience when using this investing site??

Same here.. still paying..??

[TigerMart]

This investing still running? Or many of u only give share personal experience when using this investing site??

Not only it is still runnning, but also it is paying to rebrand itself to continue in a bigger and better way - https://bitcointalk.org/index.php?topic=1065588.0

[RocketSingh]

This investing still running? Or many of u only give share personal experience when using this investing site??

Same here.. still paying..??

Tx ID of the payment was posted just one post above yours. So, I guess, it is not difficult to nderstand that it is still paying. In fact, for those who understand the game, it is no secret that the game will keep on paying for its own good as it makes more money from commission than it could by running away with the fund.

[CrazyJoker]

Daily withdrawal has been made for today...

https://blockchain.info/tx/ecf21a0667094d84d997bb56417f182d0480455a5a350ead5a1d7af043b9658d

[SS2006]

Don't get this game
hephaestus 0.05 and teffcz 0.01 expired, that is 0.06

so why is the bank roll only: 0.00186224

[SpanishSoldier]

Don't get this game
hephaestus 0.05 and teffcz 0.01 expired, that is 0.06

so why is the bank roll only: 0.00186224

What I understand is expiration does not increase the bankroll. Investment does. Expiry only makes sure that the bankroll will be compared to the next pending.

[clipman77]

This game is a dead yet, there is not enough players.