Topic: [CAPT] CAPTcoin - page 96. (Read 1059804 times)
Why you prefer using lazycoin?
requesting for CAPTcoin banners for promotion.
i wanna promote this on traffic exchanges i know but I can't really find banners for it
ok i made one from online banner makers @_@
i know it's simple and kinda lame, not really good at this lol
http://i.imgur.com/D6gbS7F.gif
i wanna promote this on traffic exchanges i know but I can't really find banners for it
ok i made one from online banner makers @_@
i know it's simple and kinda lame, not really good at this lol
http://i.imgur.com/D6gbS7F.gif
Alpha Tester Required!
(Read everything before applying)
(Read everything before applying)
I've just finished the first API service: Receive Payments API
It can be accessed here:
It works very similarly to Blockchain's API, with these basic differences:
- It works with CAPTcoin instead of Bitcoin (of course)
- It has an extra security for the merchant: A hash is sent with every callback. The actual key is sent only in the body of the SSL request when the address is generated. This is to make sure it's encrypt (unlike Blockchain, which asks the merchants to send a secret key via GET). So even if an attacker succeeds sniffing the traffic between the API and the merchant's server, he won't be able to simulate a callback. Learn more here (look for "salt_hash" and "security_hash").
- Transactions are forwarded to the merchant only after 6 confirmations. This is to prevent double-spend attacks (an extra security for the API).
- The code is 100% made from scratch.
This is the basic diagram explaining how it works:
This service is in alpha stage now
So I need testers:
Beware all generated addresses will be destroyed after this phase is over.
Do not use it on production yet.
To test, please go to: https://api.captcoin.com/
and read the full description and instructions.
Basically, you need to call this URL, either from your browser (to test) or from your server:
Code:
https://api.captcoin.com/receive?method=create&address=$receiving_address&callback=$callback_url
Where:
- $receiving_address: Your CAPTcoin address. Payments will be forwarded there
- $callback_url: The URL which will be called
Ideally, it'd be great if some of you can implement your own $callback_url for testing purposes.
The site contains instructions and basic examples on how to achieve that.
(I'm still working on a fork of https://github.com/blockchain/receive_payment_php_demo with a complete working example)
If you're not able to do that, you can use this Callbak URL:
Code:
https://api.captcoin.com/test.php
Whenever it is called, it will just log the event here:
https://api.captcoin.com/log.txt
so you can confirm it.
I made a simple tool to easily perform these tests:
https://api.captcoin.com/test/
Just follow these steps:
- Go to https://api.captcoin.com/test/
- Enter your CAPTcoin address and your callback URL, and click "Send"
- Verify the response
- Check the callback that will be sent, and confirm by clicking "Test the Callback URL"
- Verify the response is as expected
- If that works fine, go eject and send some amount between ⟳0.1 and ⟳1 to the generated address.
- Check the callbacks (for example https://api.captcoin.com/log.txt) every 3 minutes.
- Verify the coins are forwarded after 6 confirmations.
Please, help testing this to be 100% it's ready for production
Post any feedback.
I repeat the warning: All generated addresses will be destroyed after the alpha period is over. Do not use it on production yet.
That tool is great , it's a great step for any crypto !
I don't know api or something like that, just newbie programmer. So, I can't help you.. If i can about that, I want to be a tester..
If you're not a developer, you can help by going to:
https://api.captcoin.com/test/
And entering your address and this callback URL:
https://api.captcoin.com/test.php
As posted.
I do it. But show like called url, response, user instructions etc. What should I do?
You can do this:
- Go to https://api.captcoin.com/test/
- Enter your CAPTcoin address and your callback URL, and click "Send"
- Verify the response
- Check the callback that will be sent, and confirm by clicking "Test the Callback URL"
- Verify the response is as expected
- If that works fine, go eject and send some amount between ⟳0.1 and ⟳1 to the generated address.
Alpha Tester Required!
(Read everything before applying)
(Read everything before applying)
I've just finished the first API service: Receive Payments API
It can be accessed here:
It works very similarly to Blockchain's API, with these basic differences:
- It works with CAPTcoin instead of Bitcoin (of course)
- It has an extra security for the merchant: A hash is sent with every callback. The actual key is sent only in the body of the SSL request when the address is generated. This is to make sure it's encrypt (unlike Blockchain, which asks the merchants to send a secret key via GET). So even if an attacker succeeds sniffing the traffic between the API and the merchant's server, he won't be able to simulate a callback. Learn more here (look for "salt_hash" and "security_hash").
- Transactions are forwarded to the merchant only after 6 confirmations. This is to prevent double-spend attacks (an extra security for the API).
- The code is 100% made from scratch.
This is the basic diagram explaining how it works:
This service is in alpha stage now
So I need testers:
Beware all generated addresses will be destroyed after this phase is over.
Do not use it on production yet.
To test, please go to: https://api.captcoin.com/
and read the full description and instructions.
Basically, you need to call this URL, either from your browser (to test) or from your server:
Code:
https://api.captcoin.com/receive?method=create&address=$receiving_address&callback=$callback_url
Where:
- $receiving_address: Your CAPTcoin address. Payments will be forwarded there
- $callback_url: The URL which will be called
Ideally, it'd be great if some of you can implement your own $callback_url for testing purposes.
The site contains instructions and basic examples on how to achieve that.
(I'm still working on a fork of https://github.com/blockchain/receive_payment_php_demo with a complete working example)
If you're not able to do that, you can use this Callbak URL:
Code:
https://api.captcoin.com/test.php
Whenever it is called, it will just log the event here:
https://api.captcoin.com/log.txt
so you can confirm it.
I made a simple tool to easily perform these tests:
https://api.captcoin.com/test/
Just follow these steps:
- Go to https://api.captcoin.com/test/
- Enter your CAPTcoin address and your callback URL, and click "Send"
- Verify the response
- Check the callback that will be sent, and confirm by clicking "Test the Callback URL"
- Verify the response is as expected
- If that works fine, go eject and send some amount between ⟳0.1 and ⟳1 to the generated address.
- Check the callbacks (for example https://api.captcoin.com/log.txt) every 3 minutes.
- Verify the coins are forwarded after 6 confirmations.
Please, help testing this to be 100% it's ready for production
Post any feedback.
I repeat the warning: All generated addresses will be destroyed after the alpha period is over. Do not use it on production yet.
That tool is great , it's a great step for any crypto !
I don't know api or something like that, just newbie programmer. So, I can't help you.. If i can about that, I want to be a tester..
If you're not a developer, you can help by going to:
https://api.captcoin.com/test/
And entering your address and this callback URL:
https://api.captcoin.com/test.php
As posted.
I do it. But show like called url, response, user instructions etc. What should I do?
Alpha Tester Required!
(Read everything before applying)
(Read everything before applying)
I've just finished the first API service: Receive Payments API
It can be accessed here:
It works very similarly to Blockchain's API, with these basic differences:
- It works with CAPTcoin instead of Bitcoin (of course)
- It has an extra security for the merchant: A hash is sent with every callback. The actual key is sent only in the body of the SSL request when the address is generated. This is to make sure it's encrypt (unlike Blockchain, which asks the merchants to send a secret key via GET). So even if an attacker succeeds sniffing the traffic between the API and the merchant's server, he won't be able to simulate a callback. Learn more here (look for "salt_hash" and "security_hash").
- Transactions are forwarded to the merchant only after 6 confirmations. This is to prevent double-spend attacks (an extra security for the API).
- The code is 100% made from scratch.
This is the basic diagram explaining how it works:
This service is in alpha stage now
So I need testers:
Beware all generated addresses will be destroyed after this phase is over.
Do not use it on production yet.
To test, please go to: https://api.captcoin.com/
and read the full description and instructions.
Basically, you need to call this URL, either from your browser (to test) or from your server:
Code:
https://api.captcoin.com/receive?method=create&address=$receiving_address&callback=$callback_url
Where:
- $receiving_address: Your CAPTcoin address. Payments will be forwarded there
- $callback_url: The URL which will be called
Ideally, it'd be great if some of you can implement your own $callback_url for testing purposes.
The site contains instructions and basic examples on how to achieve that.
(I'm still working on a fork of https://github.com/blockchain/receive_payment_php_demo with a complete working example)
If you're not able to do that, you can use this Callbak URL:
Code:
https://api.captcoin.com/test.php
Whenever it is called, it will just log the event here:
https://api.captcoin.com/log.txt
so you can confirm it.
I made a simple tool to easily perform these tests:
https://api.captcoin.com/test/
Just follow these steps:
- Go to https://api.captcoin.com/test/
- Enter your CAPTcoin address and your callback URL, and click "Send"
- Verify the response
- Check the callback that will be sent, and confirm by clicking "Test the Callback URL"
- Verify the response is as expected
- If that works fine, go eject and send some amount between ⟳0.1 and ⟳1 to the generated address.
- Check the callbacks (for example https://api.captcoin.com/log.txt) every 3 minutes.
- Verify the coins are forwarded after 6 confirmations.
Please, help testing this to be 100% it's ready for production
Post any feedback.
I repeat the warning: All generated addresses will be destroyed after the alpha period is over. Do not use it on production yet.
That tool is great , it's a great step for any crypto !
I don't know api or something like that, just newbie programmer. So, I can't help you.. If i can about that, I want to be a tester..
If you're not a developer, you can help by going to:
https://api.captcoin.com/test/
And entering your address and this callback URL:
https://api.captcoin.com/test.php
As posted.
Alpha Tester Required!
(Read everything before applying)
(Read everything before applying)
I've just finished the first API service: Receive Payments API
It can be accessed here:
It works very similarly to Blockchain's API, with these basic differences:
- It works with CAPTcoin instead of Bitcoin (of course)
- It has an extra security for the merchant: A hash is sent with every callback. The actual key is sent only in the body of the SSL request when the address is generated. This is to make sure it's encrypt (unlike Blockchain, which asks the merchants to send a secret key via GET). So even if an attacker succeeds sniffing the traffic between the API and the merchant's server, he won't be able to simulate a callback. Learn more here (look for "salt_hash" and "security_hash").
- Transactions are forwarded to the merchant only after 6 confirmations. This is to prevent double-spend attacks (an extra security for the API).
- The code is 100% made from scratch.
This is the basic diagram explaining how it works:
This service is in alpha stage now
So I need testers:
Beware all generated addresses will be destroyed after this phase is over.
Do not use it on production yet.
To test, please go to: https://api.captcoin.com/
and read the full description and instructions.
Basically, you need to call this URL, either from your browser (to test) or from your server:
Code:
https://api.captcoin.com/receive?method=create&address=$receiving_address&callback=$callback_url
Where:
- $receiving_address: Your CAPTcoin address. Payments will be forwarded there
- $callback_url: The URL which will be called
Ideally, it'd be great if some of you can implement your own $callback_url for testing purposes.
The site contains instructions and basic examples on how to achieve that.
(I'm still working on a fork of https://github.com/blockchain/receive_payment_php_demo with a complete working example)
If you're not able to do that, you can use this Callbak URL:
Code:
https://api.captcoin.com/test.php
Whenever it is called, it will just log the event here:
https://api.captcoin.com/log.txt
so you can confirm it.
I made a simple tool to easily perform these tests:
https://api.captcoin.com/test/
Just follow these steps:
- Go to https://api.captcoin.com/test/
- Enter your CAPTcoin address and your callback URL, and click "Send"
- Verify the response
- Check the callback that will be sent, and confirm by clicking "Test the Callback URL"
- Verify the response is as expected
- If that works fine, go eject and send some amount between ⟳0.1 and ⟳1 to the generated address.
- Check the callbacks (for example https://api.captcoin.com/log.txt) every 3 minutes.
- Verify the coins are forwarded after 6 confirmations.
Please, help testing this to be 100% it's ready for production
Post any feedback.
I repeat the warning: All generated addresses will be destroyed after the alpha period is over. Do not use it on production yet.
That tool is great , it's a great step for any crypto !
I don't know api or something like that, just newbie programmer. So, I can't help you.. If i can about that, I want to be a tester..
i love this
Just added my vote on C-CEX, we are now 35th 
Thanks ! I edited my post
Just added my vote on C-CEX, we are now 35th
VOTE FOR CAPTCOIN
We've lost 1 rank on HitBTC, please don't forget to daily vote
- HitBTC / https://hitbtc.com/vote
Details : One vote/day per IP no need to register. If you are signed-in into your HitBTC account, your vote will be multiplied by 10 (but you can cast only one vote as a member).
Actual rank : 15th - Bleutrade / https://bleutrade.com/voting/CAPT
Details : unlimited votes but it's not free... Vote fee : 0.0001 BTC / Registration required.
Actual rank : 31st - SwapHole / https://www.swaphole.com/#!voting
Details : To vote for a certain coin click on the "Vote!" button of the row of the coin. You can also push votes by sending BTC to the stated BTC address of the coin of your choice. Please notice that each 0.00010000 BTC one vote will be added to the coin you support with your BTC transaction.
Actual rank : 43rd - C-CEX / https://c-cex.com/?id=vote
Details : You can vote for adding coin by depositing BTC to it's address.
Actual rank : 35th - Cryptofolio / http://cryptofolio.info/welcome/vote
Details : Accept free vote and paid vote (0.0005BTC/vote)
Actual rank : 12th
Well done !!
yea. i prefer using http://lazycoins.com than others 
I hope there will be a linux wallet soon.
I got it compiled on Zorin, maybe dev knows if I can just give you a copy or if it has to be compiled on each distro specifically. I did have to modify the .pro with these instructions to get it to compile. http://pw999.wordpress.com/2013/09/29/compiling-memecoin-qt-on-xubuntu/
I don't know if this is the right place, but does anyone want to trade 1400 capt for a 19$ amazon e-gift card?
Edit: nevermind
Edit: nevermind
got the hang of it now, i was doing times for that plus sign :/
why isnt the wallet syncing?
why isnt the wallet syncing?
actually you only get a certain amount of time,i am having problems with the wallet syncing tho
what happens if you change the % to 0 for bountyfund and the developer?
Total claimed: 0.4963 • Claims: 1
Ive done about 4 capchas so far, so why is does it say ive only done 1?
what happens if you change the % to 0 for bountyfund and the developer?
Total claimed: 0.4963 • Claims: 1
Ive done about 4 capchas so far, so why is does it say ive only done 1?
Most probably, some captcha was wrong the other 3 times. You get a message either confirming your claim or showing the error every time.
If you set the donation to 0, then you won't support the development. But of course you can do so.
Jump to: