Topic: ClamBaker.Club (Read 1653 times)
Thanks, my uncooked clams are refunded. All is good.
We post this with heavy hearts:
Clambaker.Club version one is going to be shut down until a re-written version can be finished and tested.
We've encountered some terrible troubles trying to get version one going and its best for the site and community to cease deposits.
At this time we ask anyone who deposited but wasn't paid out yet to PM us a TXID of your investment.
Refunds (of your principal) will be done over the next few days, with those sending TXID of unpaid baked clams being paid first.
We apologize to the CLAM community and forums for rushing into this project without proper testing.|
Stay tuned to this thread, We will be keeping this thread updated as the new clambaker.club is created.
Clambaker.Club version one is going to be shut down until a re-written version can be finished and tested.
We've encountered some terrible troubles trying to get version one going and its best for the site and community to cease deposits.
At this time we ask anyone who deposited but wasn't paid out yet to PM us a TXID of your investment.
Refunds (of your principal) will be done over the next few days, with those sending TXID of unpaid baked clams being paid first.
We apologize to the CLAM community and forums for rushing into this project without proper testing.|
Stay tuned to this thread, We will be keeping this thread updated as the new clambaker.club is created.
But it's a mistake to take random code from github and use it without understanding it or checking that it works as intended.
Fortunately for the site I've noticed that you have applied a few fixes in github.
Thank you for helping us correct the errors this site first went online with.
Deposits and withdrawls are currently paused but staking is still online.
Once dooglus gives us the go ahead to launch again we will be back up.
I did end up forking the repository myself and contributing a fix for the "return address" bug, but I'm in no way affiliated with this project, and fear it will all end in tears.
The PHP code you started with was dreadful, and it isn't a whole lot better now. I've fixed a few significant bugs, but there are probably many remaining.
Please refrain from associating my name with this project in an attempt to give it feelings of legitimacy. I'm talking about things like:
Quote
<@KLYE> The code is doog blessed.
<@dooglus> hardly
<@dooglus> I said it was shit
<@KLYE> Then you dinked around in it
<@KLYE>
<@dooglus> and now it's ever so slightly less shit
<@KLYE> Yes. Yes it is.
<@KLYE> Its still shit.
<@KLYE> But dooglus lubed.
<@dooglus> hardly
<@dooglus> I said it was shit
<@KLYE> Then you dinked around in it
<@KLYE>
<@dooglus> and now it's ever so slightly less shit
<@KLYE> Yes. Yes it is.
<@KLYE> Its still shit.
<@KLYE> But dooglus lubed.
to be honest you should just request a return address from the depositor instead of reusing an old address, it would allow people to send coins from one wallet and receive with another plus you wouldn't have to do something as gross as determining the return address from the outputs.
It seems he's wanting to have the Ponzi run entirely on the blockchain, so the users don't have to make an account on the website.
But it's a mistake to take random code from github and use it without understanding it or checking that it works as intended.
Fortunately for the site I've noticed that you have applied a few fixes in github.
Thank you for helping us correct the errors this site first went online with.
Deposits and withdrawls are currently paused but staking is still online.
Currently performing maintenance and will hopefully be back up shortly!
I was fortunate enough to have Just-Dice.com owner dooglus give me a hand in auditing and bug fixing on the site!
Everything should be functioning as normal again. We had to rebuild the database as well as fix a few scripts.
Everything should be functioning as normal again. We had to rebuild the database as well as fix a few scripts.
I did help out. The scripts being used were really pretty bad. I fixed a few of the most obvious bugs but not all of them. I personally wouldn't be using these scripts on a live site. They feel like an accident waiting to happen.
One bug that I didn't fix is in the way the script determines which address to pay out to. It looks at the first input of the deposit transaction, finds which transaction created that output, and the uses the address of either the 1st or 2nd output of that transaction as the address to repay. There's no comment to explain why such a strange strategy is used, but it will often result in the wrong person being paid out.
See https://i.imgur.com/A0BvC0h.png and http://clamsight.com/tx/c38a5be7810f6ef6ac74c08d263198d100a779ddc5d963a56ddb28bda78c5815 for a couple of examples.
Why isn't he just sending back to the first input (Labeled output in your image). The xDkh address in your image. That is still going to have problems if sent from JD but
he does have a mess of warnings... Also you should control all of the address your sending from...
Since I don't know what he's actually going to use to send back, I just had to make some assumptions... Not sure if I even understand it correctly.
to be honest you should just request a return address from the depositor instead of reusing an old address, it would allow people to send coins from one wallet and receive with another plus you wouldn't have to do something as gross as determining the return address from the outputs.
It seems he's wanting to have the Ponzi run entirely on the blockchain, so the users don't have to make an account on the website.
But it's a mistake to take random code from github and use it without understanding it or checking that it works as intended.
to be honest you should just request a return address from the depositor instead of reusing an old address, it would allow people to send coins from one wallet and receive with another plus you wouldn't have to do something as gross as determining the return address from the outputs.
You are 100% correct about the payouts looking for the 1st or 2nd transaction to send back. This is why we ask you not play from JD or exchanges.
I don't think you understand the point I am trying to make.
Check the 2 examples I linked to. Check in your database to see which address they are set to pay out to. It isn't the 1st or 2nd "input address".
Edit: I posted a github issue for the bug too, though the repository there hasn't been touched for 18 months, so I guess it has been abandoned.
Thanks for pointing out it's set to 6 confirms. We'd done this to match JD after you posed the security risk of 1 block transactions!
As for the script, I know both yourself and the Clam developers have both audited the code and made tweaks.
As for the original bugs, I believe that they have been patched and have faith in the new script.
You are 100% correct about the payouts looking for the 1st or 2nd transaction to send back. This is why we ask you not play from JD or exchanges.
As for the script, I know both yourself and the Clam developers have both audited the code and made tweaks.
As for the original bugs, I believe that they have been patched and have faith in the new script.
You are 100% correct about the payouts looking for the 1st or 2nd transaction to send back. This is why we ask you not play from JD or exchanges.
I was fortunate enough to have Just-Dice.com owner dooglus give me a hand in auditing and bug fixing on the site!
Everything should be functioning as normal again. We had to rebuild the database as well as fix a few scripts.
Everything should be functioning as normal again. We had to rebuild the database as well as fix a few scripts.
I did help out. The scripts being used were really pretty bad. I fixed a few of the most obvious bugs but not all of them. I personally wouldn't be using these scripts on a live site. They feel like an accident waiting to happen.
One bug that I didn't fix is in the way the script determines which address to pay out to. It looks at the first input of the deposit transaction, finds which transaction created that output, and the uses the address of either the 1st or 2nd output of that transaction as the address to repay. There's no comment to explain why such a strange strategy is used, but it will often result in the wrong person being paid out.
See https://i.imgur.com/A0BvC0h.png and http://clamsight.com/tx/c38a5be7810f6ef6ac74c08d263198d100a779ddc5d963a56ddb28bda78c5815 for a couple of examples.
ClamBaker.club has also moved from 1 confirm to 5 for added security. (Takes around 5 minutes to show on site)
It says 6 on the site:
"Note: Transactions are added above after 6 confirmations."
Pleased to announce we have fixed the Database issues and deposits have been re-enabled over on the site.
Site is back up but we have disabled deposits for the time being until we can sort out the DB glitch encountered.
The CLAM are safe, We currently hold 12.44206925 CLAM onsite and are stake-n-baking them. Withdrawals online will be auto processed.
Hopefully have deposits online and the site working 100% by later tonight or tomorrow.
The CLAM are safe, We currently hold 12.44206925 CLAM onsite and are stake-n-baking them. Withdrawals online will be auto processed.
Hopefully have deposits online and the site working 100% by later tonight or tomorrow.
I'm giving it a try. But can you explain a little more about this?
On your main screen I see
Collecting 20.31954135 / 15.00000000 for 0ebd6cb0871aa7ed737b33c5522f4012...
a) Why are you collecting more then your paying out?
b) Where are you collecting this from?
c) how can I look at that transaction?
Down in the latest transactions there are a couple of paid transaction in the middle of baking ones. Shouldn't the transaction get paid back in the same order they were received?
Just a note: The amount in the latest transactions is the amount being paid back and not the amount deposited.
Good luck with this, I hope it works out well.
Good day chilly2K. We are having a bit of a bug at the moment (as you can see).
We had a minor database glitch develop shortly after launch which was fixed but is currently throwing a few numbers wrong.
Site is currently down and we have one of the CLAM lead developers actually looking into it as I type this.
Funds are still safe (and staking!) and we hope to have the site fixed and back online some time later this evening.
Site appears down.
Beautiful fucking idea.
Beautiful fucking idea.
Indeed the site is down at the moment. Read the reply above for a bit further details.
Quote from: ClamBaker.Club link=topic=1216193.msg12746416#msg12746416 date=14454
[size=24pt
[size=24pt
This isn't clickable in the OP
Site appears down.
Beautiful fucking idea.
Beautiful fucking idea.
I'm giving it a try. But can you explain a little more about this?
On your main screen I see
Collecting 20.31954135 / 15.00000000 for 0ebd6cb0871aa7ed737b33c5522f4012...
a) Why are you collecting more then your paying out?
b) Where are you collecting this from?
c) how can I look at that transaction?
Down in the latest transactions there are a couple of paid transaction in the middle of baking ones. Shouldn't the transaction get paid back in the same order they were received?
Just a note: The amount in the latest transactions is the amount being paid back and not the amount deposited.
Good luck with this, I hope it works out well.
We are back online.
I was fortunate enough to have Just-Dice.com owner dooglus give me a hand in auditing and bug fixing on the site!
Everything should be functioning as normal again. We had to rebuild the database as well as fix a few scripts.
ClamBaker.club has also moved from 1 confirm to 6 for added security. (Takes around 5 minutes to show on site)
I was fortunate enough to have Just-Dice.com owner dooglus give me a hand in auditing and bug fixing on the site!
Everything should be functioning as normal again. We had to rebuild the database as well as fix a few scripts.
ClamBaker.club has also moved from 1 confirm to 6 for added security. (Takes around 5 minutes to show on site)
Nearly 150 CLAM have been baked-n-staked and return to their owners!
Glad to hear you had a delicious CLAM bake!
Made a spend and got CLAM returned to me. Worked out great. Spending again.
Jump to: