It's easy enough. I'm kind of busy atm but I'll be glad to help you when I'm free. Shoot me a PM if you have any questions. For now, don't worry about the payments and the API. First make the HTML forms and have them submit to a PHP script.
Then, sanitize the data (GET/POST params).
Then, call the API.
Topic: Help a beginner create an inputs.io faucet from scratch (Read 1541 times)
I've just built mine on x10Hosting.com with success.
It takes some hours to clear the redirect, but after that, it worked quite fine!
http://stetchino.elementfx.com/
I've signed up, uploaded the files, created the database and changed config.php accordingly.
It takes some hours to clear the redirect, but after that, it worked quite fine!
http://stetchino.elementfx.com/
I've signed up, uploaded the files, created the database and changed config.php accordingly.
I'm talking about creating one from scratch WITHOUT the myfaucet script
I've just built mine on x10Hosting.com with success.
It takes some hours to clear the redirect, but after that, it worked quite fine!
http://stetchino.elementfx.com/
I've signed up, uploaded the files, created the database and changed config.php accordingly.
It takes some hours to clear the redirect, but after that, it worked quite fine!
http://stetchino.elementfx.com/
I've signed up, uploaded the files, created the database and changed config.php accordingly.
This could probably be solved with google, but how do you make api calls in php?
The page I linked describes it for inputs.io.
This could probably be solved with google, but how do you make api calls in php?
The page I linked describes it for inputs.io.
This could probably be solved with google, but how do you make api calls in php?
I'll give you some idea of how I think the application should be composed (although I've not made one myself, I make that clear).
You need a way to handle the transactions (inputs.io)
https://inputs.io/api
Here's the API to use^
Then you need to program some business logic, that is the glue and requests through the web language of your choice (PHP, Python, Ruby etc.).
You could make the web language frontend request a backend-service, written in another language, or the same language for handling the occassional processing (of scheduled payouts).
I know I keep saying this, but Golang is great for backend services (It's easy multi-threading and the nice minimalistic keyword set is perfect), although I think you should just get your proof of concept code working, and you'll make thoughts about your complete design in the process.
And hey; good idea to get someone to security audit it. You can ask some people kindly, but there is also http://codereview.stackexchange.com/ it's in beta, you might wanna try it.
There's also automated scanners like
http://wapiti.sourceforge.net/
(I think it's still a good one, but others might have come in to the game, this is the one I used last time).
glhf
Heading off now, but if i'm correct, backend services require a VPS, so since I only have shared web hosting i've been looking around. I've found koding (http://koding.com) and was wondering if that was good or bad. I also have absolutely no idea how I would even use anything other than PHP to output HTML or to do backend jobs.You need a way to handle the transactions (inputs.io)
https://inputs.io/api
Here's the API to use^
Then you need to program some business logic, that is the glue and requests through the web language of your choice (PHP, Python, Ruby etc.).
You could make the web language frontend request a backend-service, written in another language, or the same language for handling the occassional processing (of scheduled payouts).
I know I keep saying this, but Golang is great for backend services (It's easy multi-threading and the nice minimalistic keyword set is perfect), although I think you should just get your proof of concept code working, and you'll make thoughts about your complete design in the process.
And hey; good idea to get someone to security audit it. You can ask some people kindly, but there is also http://codereview.stackexchange.com/ it's in beta, you might wanna try it.
There's also automated scanners like
http://wapiti.sourceforge.net/
(I think it's still a good one, but others might have come in to the game, this is the one I used last time).
glhfOh I remember you said that, well - The first thing is just getting to learn the inputs.io API, and practise till you feel confident in it. You can try the simple examples on the API page and try modding them.
PHP is fine, just take things one step at a time.
I'll give you some idea of how I think the application should be composed (although I've not made one myself, I make that clear).
You need a way to handle the transactions (inputs.io)
https://inputs.io/api
Here's the API to use^
Then you need to program some business logic, that is the glue and requests through the web language of your choice (PHP, Python, Ruby etc.).
You could make the web language frontend request a backend-service, written in another language, or the same language for handling the occassional processing (of scheduled payouts).
I know I keep saying this, but Golang is great for backend services (It's easy multi-threading and the nice minimalistic keyword set is perfect), although I think you should just get your proof of concept code working, and you'll make thoughts about your complete design in the process.
And hey; good idea to get someone to security audit it. You can ask some people kindly, but there is also http://codereview.stackexchange.com/ it's in beta, you might wanna try it.
There's also automated scanners like
http://wapiti.sourceforge.net/
(I think it's still a good one, but others might have come in to the game, this is the one I used last time).
glhf
Heading off now, but if i'm correct, backend services require a VPS, so since I only have shared web hosting i've been looking around. I've found koding (http://koding.com) and was wondering if that was good or bad. I also have absolutely no idea how I would even use anything other than PHP to output HTML or to do backend jobs. You need a way to handle the transactions (inputs.io)
https://inputs.io/api
Here's the API to use^
Then you need to program some business logic, that is the glue and requests through the web language of your choice (PHP, Python, Ruby etc.).
You could make the web language frontend request a backend-service, written in another language, or the same language for handling the occassional processing (of scheduled payouts).
I know I keep saying this, but Golang is great for backend services (It's easy multi-threading and the nice minimalistic keyword set is perfect), although I think you should just get your proof of concept code working, and you'll make thoughts about your complete design in the process.
And hey; good idea to get someone to security audit it. You can ask some people kindly, but there is also http://codereview.stackexchange.com/ it's in beta, you might wanna try it.
There's also automated scanners like
http://wapiti.sourceforge.net/
(I think it's still a good one, but others might have come in to the game, this is the one I used last time).
glhf
I'll give you some idea of how I think the application should be composed (although I've not made one myself, I make that clear).
You need a way to handle the transactions (inputs.io)
https://inputs.io/api
Here's the API to use^
Then you need to program some business logic, that is the glue and requests through the web language of your choice (PHP, Python, Ruby etc.).
You could make the web language frontend request a backend-service, written in another language, or the same language for handling the occassional processing (of scheduled payouts).
I know I keep saying this, but Golang is great for backend services (It's easy multi-threading and the nice minimalistic keyword set is perfect), although I think you should just get your proof of concept code working, and you'll make thoughts about your complete design in the process.
And hey; good idea to get someone to security audit it. You can ask some people kindly, but there is also http://codereview.stackexchange.com/ it's in beta, you might wanna try it.
There's also automated scanners like
http://wapiti.sourceforge.net/
(I think it's still a good one, but others might have come in to the game, this is the one I used last time).
glhf
You need a way to handle the transactions (inputs.io)
https://inputs.io/api
Here's the API to use^
Then you need to program some business logic, that is the glue and requests through the web language of your choice (PHP, Python, Ruby etc.).
You could make the web language frontend request a backend-service, written in another language, or the same language for handling the occassional processing (of scheduled payouts).
I know I keep saying this, but Golang is great for backend services (It's easy multi-threading and the nice minimalistic keyword set is perfect), although I think you should just get your proof of concept code working, and you'll make thoughts about your complete design in the process.
And hey; good idea to get someone to security audit it. You can ask some people kindly, but there is also http://codereview.stackexchange.com/ it's in beta, you might wanna try it.
There's also automated scanners like
http://wapiti.sourceforge.net/
(I think it's still a good one, but others might have come in to the game, this is the one I used last time).
glhf
Hello guys, I want to expand my learning, so i'm asking for your help. I want to create a bitcoin faucet to add to http://bitcoinmaniac.com , but I don't want to go the easy route and use the precreated myfaucet script. I want to create quality code and be proud of it. I'm a beginner with PHP and i've never even touched mysql, and I don't know where to start. I'd like to see a few things in my faucet:
Loads things from a config file that can be easily edited to change most aspects of the faucet. (API key, payout, etc)
Doesn't allow payouts to the same address or IP for a time set in the config file
Pretty basic things. Please help me, I don't want you to do the work for me, I want you to direct me where I can learn the neccessary skills to build such a thing. I appreciate any help or constructive feedback you might have.
Loads things from a config file that can be easily edited to change most aspects of the faucet. (API key, payout, etc)
Doesn't allow payouts to the same address or IP for a time set in the config file
Pretty basic things. Please help me, I don't want you to do the work for me, I want you to direct me where I can learn the neccessary skills to build such a thing. I appreciate any help or constructive feedback you might have.
Jump to: