...
Just let me know how you would like me to proceed! I'm ready to pay them back to the CAPTcoin main wallet!!
Yeah, I got 65 extra, I'd be willing to pay it back.
Tomorrow I'll create a return address for every affected address. In the meanwhile, you can keep claiming coins with the same address. It will be counted as returned, and only the exceeding amount will be sent. Thanks! Oh ok, then I have just paid it back because I claimed 100 more and got 35. Then the mix-up was not even a problem to the coin at all, if the ones who were affected have it taken from their claimed CAPT. Cool, so no return address for you  At the moment, the total amount still to be returned has been lowered to ⟳908.1916 (from the original ⟳2,402.3636) so everything seems to be going well. Only 31 addresses (out of 106) still need to return some amount. |
|
|
|
...
Just let me know how you would like me to proceed! I'm ready to pay them back to the CAPTcoin main wallet!!
Yeah, I got 65 extra, I'd be willing to pay it back.
Tomorrow I'll create a return address for every affected address. In the meanwhile, you can keep claiming coins with the same address. It will be counted as returned, and only the exceeding amount will be sent. Thanks! Wouldn't it just be easier to create one coin return address? That way any auditing could show what addresses sent their coins back to that one address, instead of making 106 different return addresses? The problem is the wallet automatically creates several addresses. If you've ever sent CAPTcoins, the wallet creates a new address to store the change. Therefore, if a single return address is used, the payment won't always come directly from the affected address, so there's no way to know for sure where it came from. It gets worst if the user already sent some coins to an exchange. With 106 different address, we can be sure whatever return-address A received came from its corresponding affected-address A. |
|
|
|
Hello, i have use my own referral link like this MyRef.CAPTcoin.com, but after i submit once then it back to get.captcoin.com , sorry for this noob question but do i have to go to My.Ref.CAPTcoin.com again or just submit next CAPT on get.captcoin.com. Thank you and wish CAPTcoin will be best  MyRef.CAPTcoin.com always redirects to get.CAPTcoin.com/?r=MyRef (provided MyRef is a valid referrer code) Then the referrer (MyRef) is stored in a cookie. So, no need to go every time to MyRef.CAPTcoin.com. |
|
|
|
...
Just let me know how you would like me to proceed! I'm ready to pay them back to the CAPTcoin main wallet!!
Yeah, I got 65 extra, I'd be willing to pay it back.
Tomorrow I'll create a return address for every affected address. In the meanwhile, you can keep claiming coins with the same address. It will be counted as returned, and only the exceeding amount will be sent. Thanks! |
|
|
|
Thank you for your donations! ⟳41 so far. It'd be great to reach ⟳100 to start the giveaway. But at least ⟳50 are required. Please donate to CcW6zuRaivuSYpDpyi792EyH7GuGFcimgx⟳50 have been donated for the Twitter giveaway. Thanks! Can we reach ⟳100? |
|
|
|
Hi everybody, Unfortunately, I made a mistake while manually processing the transactions automatically generated by the system: I executed 3 transactions twice. Affected transactions are: As a result, 106 unique addresses unfairly received a combined total of ⟳2,402.3636. The full list of affected addresses is: http://pastebin.com/hudGgqYV (sorted by received amount) However, several of these addresses are still completing captchas and claiming CAPTcoins, so the total amount has been now reduced to ⟳1,596.4739 (and lowering every second). I'm extremely sorry for this mistake! I must insist in the fact that the problem was in my manual execution of the transactions, and not in the automated system. What I propose to do:- Take measures so this will never happen again.
- Publish the pending amount in the form corresponding to each of these addresses. Ask people to continue completing captchas. Only the amount exceeding the already paid value will be sent.
- Create a unique receiving address for every of these addresses (a total of 106 unique receiving addresses). In the form, people will be asked to send the extra amount to the corresponding address.
This sent amount will be registered and forwarded to distribution address #20.
Please do not send the extra coins anywhere until this is set up.
(These steps have the objective of minimizing the impact of this mistake.) I know several addresses won't see the message, or won't return the extra amount even after seeing the message. To handle this, I propose: - At the end of the distribution, calculate the maximum percentage of extra coins received by every address.
For example, if an address earned ⟳1,000 but received ⟳1,100, it has an extra 10%. - Get the maximum percentage received by a single address.
For example, if address A received 10% and address B received 5%, get the maximum 10%. - From the distribution fund (totaling ⟳20,000,000), send every single address the same percentage of extra coins.
In this example, every single address would receive an extra 10%. - Of course, addresses who already received any extra coins would receive only the missing coins to reach the corresponding percentage.
For example, Address A would receive 0%, address B would receive the missing 5%, and unaffected addresses would receive the full 10%. - As planed, the rest of coins will be destroyed.
(These steps have the objective of converting my mistake into a fair one.) Again, I'm sorry for this mistake. Please post any comments regarding my suggested plan of actions. |
|
|
|
Stats corresponding to yesterday, July the 27th |
|
|
|
can you give a weibo giveaway? The site will soon be translated to Chinese. When it is, there can be a giveaway on Weibo. Could you organize it? (with funds donated by the community). When it is,tell me Thanks. I will. |
|
|
|
Dear dev, could you add to the captcha page, which captchas did not get solved ?
This information might make things easier for hackers, although not very probable. Opinions? |
|
|
|
Thank you for your donations! ⟳41 so far. It'd be great to reach ⟳100 to start the giveaway. But at least ⟳50 are required. Please donate to CcW6zuRaivuSYpDpyi792EyH7GuGFcimgx |
|
|
|
I see the first one as "Emprisk" instead of "Empnisk", but I'm not sure. That's Google's system, and I think it's somewhat permissive so maybe that one is OK. The third one should be: "19thG" (not "thG19"). Order is important there. |
|
|
|
Hey Dev I know it's related to my ip as sometimes I'm using vpn etc. So is it possible to solve it from ur side?
That's part of some basic security controls and unfortunately it'd be dangerous to remove. Please don't use a shared VPN to claim CAPTcoins. |
|
|
|
I answer this  With 9(7+2)= (63+18)= 81= fNR 81 But is wrong... as many other right attempts. I give up.  Dispose a FAQ telling how to solve these captchas, plz. THX Sorry about that. I'll create a detailed guide. In this case, "fNR81" is OK. Probably one of the other captchas were wrong. |
|
|
|
Hey Dev I wanna notify u about a problem I'm facing I don't know whether anyone is facing it or not. Not it's not about captchas, they are just childs play. But sometimes when I'm hitting submit button it's showing me "YOUR SESSION IS EXPIRED. PLEASE TRY AGAIN." instead of having around 40 - 50secs in my hand.
Please PM me your public IP address. |
|
|
|
|
Show Posts
Twitter giveaway
