Author

Topic: [Closed] Wanted: PHP Script to collect data on addresses (Read 718 times)

donator
Activity: 2058
Merit: 1054
Greetings, Meni,

I am a web developer and have quite a bit of experience with implementing systems involving Bitcoin.

If you want to know what I've done in the past, check the portfolio on my site.

I also urge you to check out satoshicarnival.co, a fresh Bitcoin Casino where the front-end developer, and LastMail, my most recent hobby-project.

Sincerely,

~W-M
Thanks, PM sent.
W-M
full member
Activity: 210
Merit: 100
In Crypto we Trust.
Greetings, Meni,

I am a web developer and have quite a bit of experience with implementing systems involving Bitcoin.

If you want to know what I've done in the past, check the portfolio on my site.

I also urge you to check out satoshicarnival.co, a fresh Bitcoin Casino where the front-end developer, and LastMail, my most recent hobby-project.

Sincerely,

~W-M
donator
Activity: 2058
Merit: 1054
Crap, it's been a while since I traded on the forum and my scammer-sensor is uncalibrated...

The offer is open again.
donator
Activity: 2058
Merit: 1054
Hello,

I am myself php dev and more you can check my profile on freelancer.com


i would be happy to make this for you

contact me via pm so we may chat on skype?
Cool, sending PM.
donator
Activity: 2058
Merit: 1054
Hi, I'm offering 0.2 BTC for PHP code that does the following:

1. Accepts a list of Bitcoin addresses as a parameter.
2. Queries each address on blockchain.info or equivalent.
3. Outputs a tsv of all transactions involving one of the addresses in the list. For every such transaction there should be a row with the following fields:
* The address involved
* The balance change for the address in this transaction (total value of all outputs to this address, minus total value of all inputs from it)
* The date at which the transaction occured.
4. For addresses that do not appear in the blockchain at all, there should be a row with the address and 0 in the other fields.
5. The rows should be sorted by the address (in the original order the addresses were given), and then by the transaction date.

The code should be safe against injection attacks (if there is such a risk in the first place).
Jump to: