It should be fixed now, will test again.
Topic: [CLOSED] BitPing.Net - A bitcoin notify service - page 2. (Read 6972 times)
Hmm, found a bug in the monitor code, that caused some addresses to not be detected
It should be fixed now, will test again.
It should be fixed now, will test again.
I am monitoring this address: http://blockexplorer.com/address/1J9fuhVWEBT1ZuRRk66eFo6s9pc4wJ4ozg
But I have not received notification.
Also there is no notification in history...
Did you create the order after the payment was sent (but before it reached 4 confirmations) ?But I have not received notification.
Also there is no notification in history...
I am currently running a test to check if theres anything wrong with the system.
Which informations are you looking for in history ?
I am monitoring this address: http://blockexplorer.com/address/1J9fuhVWEBT1ZuRRk66eFo6s9pc4wJ4ozg
But I have not received notification.
Also there is no notification in history...
But I have not received notification.
Also there is no notification in history...
Any chance to see more detailed history about what happened to each notification ?
Awesome! Very useful service and source..
Notify
Fixed a bug in 0-confirmation signature calculation recently, so you can now validate the message correctly! 
Added a price conversion tool.
https://bitping.net/tools/price.php?amount=100¤cy=USD returns how many BTC equals USD
https://bitping.net/tools/price.php?amount=100¤cy=USD&type=js returns it as a javascript document.write, so it can be used in clientside only websites to build a simple "shop".
More info : http://bitping.net/tools.php
Added a price conversion tool.
https://bitping.net/tools/price.php?amount=100¤cy=USD returns how many BTC equals USD
https://bitping.net/tools/price.php?amount=100¤cy=USD&type=js returns it as a javascript document.write, so it can be used in clientside only websites to build a simple "shop".
More info : http://bitping.net/tools.php
Awesome - thanks a lot!
This is a great idea - would it be possible to also support an option for a plain text minimal output?
e.g. http://bitping.net/exchange_rates.php?rates=AUDBTC&format=rate_only
e.g. http://bitping.net/exchange_rates.php?rates=AUDBTC&format=rate_only
Done, with a small twist just to be safe
http://bitping.net/exchange_rates.php?rates=AUDBTC&format=rate_only&disclaimer=accepted
This is a great idea - would it be possible to also support an option for a plain text minimal output?
e.g. http://bitping.net/exchange_rates.php?rates=AUDBTC&format=rate_only
that would output
5.23623852
(handy for use with curl)
Cheers,
Ian.
e.g. http://bitping.net/exchange_rates.php?rates=AUDBTC&format=rate_only
that would output
5.23623852
(handy for use with curl)
Cheers,
Ian.
Added exchange rates
http://bitping.net/exchange_rates.php for all pairs.
http://bitping.net/exchange_rates.php?rates=DKKBTC,DKKUSD for just those rates.
Data is updated every 15minutes.
The USDBTC is from mt. gox.
All other BTC are calculated based on this, ie. EURBTC is NOT the eur exchange, but simply EURUSD * USDBTC.
See license and other notes in the feed.
Small example (note that we can only use 0 here, because I only asked for 1rate, and you should ofcause do some error checking...
http://bitping.net/exchange_rates.php for all pairs.
http://bitping.net/exchange_rates.php?rates=DKKBTC,DKKUSD for just those rates.
Data is updated every 15minutes.
The USDBTC is from mt. gox.
All other BTC are calculated based on this, ie. EURBTC is NOT the eur exchange, but simply EURUSD * USDBTC.
See license and other notes in the feed.
Small example (note that we can only use 0 here, because I only asked for 1rate, and you should ofcause do some error checking...
Code:
$json = json_decode(file_get_contents("http://bitping.net/exchange_rates.php?rates=DKKBTC"), true);
echo "DKKBTC IS ".$json["rates"][0]["rate"]." last updated at ".$json["rates"][0]["updated"]."
";
$btc = 1000 / $json["rates"][0]["rate"];
echo "Please pay $btc BTC to 1xyz
";
echo "DKKBTC IS ".$json["rates"][0]["rate"]." last updated at ".$json["rates"][0]["updated"]."
";
$btc = 1000 / $json["rates"][0]["rate"];
echo "Please pay $btc BTC to 1xyz
";
Very nice and simple service, thanks!
Basic API for address handling added.
You can now add and remove addresses from the orders using a API.
This is useful if you for whatever reason cannot or will not give out all address upfront, you can then call BPN when you assign a address to a user, or in the morning with the list of addresses for the day, etc.
More info under "Orders", its a GET/POST with your secret used in a sha1 hash for security.
Adding an address that already exists, will not result in a error.
Removing an address that don't exists, will not result in a error.
You can now add and remove addresses from the orders using a API.
This is useful if you for whatever reason cannot or will not give out all address upfront, you can then call BPN when you assign a address to a user, or in the morning with the list of addresses for the day, etc.
More info under "Orders", its a GET/POST with your secret used in a sha1 hash for security.
Adding an address that already exists, will not result in a error.
Removing an address that don't exists, will not result in a error.
If someone is willing to host a copy of the service, please let me know and I will help with the setup if needed.
Optimally there should be 3+ identical services, so websites can register for all 3, and require 2 independent events before taking it for good.
For the same reason, a mirror/copy should not be hosted by me, since it could then go down at the same time.
The service requires 512mb ram, 15gb disc space, virtually no cpu and low disc io (after the initial import)
You can of cause change the donation link on your version, but you should not expect to make a profit out of it.
Optimally there should be 3+ identical services, so websites can register for all 3, and require 2 independent events before taking it for good.
For the same reason, a mirror/copy should not be hosted by me, since it could then go down at the same time.
The service requires 512mb ram, 15gb disc space, virtually no cpu and low disc io (after the initial import)
You can of cause change the donation link on your version, but you should not expect to make a profit out of it.
Latest changes have been comitted to github, along with a small example app that uses jQuery and BPN to show live payment received to "customer"
Regular events 1-n are now attempted every 2 minutes for 24hours.
Thank you!
With the help of stcupp we can now supply unconfirmed notifications
For now this only works with regular orders, ie. not one-shot API.
You simply select 0 from the dropdown...
Unconfirmed events are attempted for delivery every 10seconds for 5 minutes, after that no more attempts are made.
Regular events 1-n are now attempted every 2 minutes for 24hours.
So you may wish to register for unconfirmed events to show "Payment received" to customer, and then 1-6confirmations before shipping the items/downloads/keys/etc.
This is ofcause beta, please report any bugs, missed events, etc.
For HTTP POST API confirmations is set to 0 for unconfirmed, and block to -1.
In other news : A bug with block number has been fixed, previously we were sending blockID, not the blockHeight.
For now this only works with regular orders, ie. not one-shot API.
You simply select 0 from the dropdown...
Unconfirmed events are attempted for delivery every 10seconds for 5 minutes, after that no more attempts are made.
Regular events 1-n are now attempted every 2 minutes for 24hours.
So you may wish to register for unconfirmed events to show "Payment received" to customer, and then 1-6confirmations before shipping the items/downloads/keys/etc.
This is ofcause beta, please report any bugs, missed events, etc.
For HTTP POST API confirmations is set to 0 for unconfirmed, and block to -1.
In other news : A bug with block number has been fixed, previously we were sending blockID, not the blockHeight.
Just 10K blocks togo ...
Missed notifications will begin to be sent out in a few hours.
[UPDATE] 2000blocks remaining, processing at about 20 each minute ~1½hour till notifications start again
[UPDATE] Back in action as of 16:30 UTC
Missed notifications will begin to be sent out in a few hours.
[UPDATE] 2000blocks remaining, processing at about 20 each minute ~1½hour till notifications start again
[UPDATE] Back in action as of 16:30 UTC
It is now downloading blockchain again from beginning ?
I tried to restore a good chunk of the block file to speed it up and it failed, so yes, it is going to have to slave its way trough the entire block chain.How about incising that retry to at least few days? It can try frequently for the first hour and then it can try like once pen hour.
Well if your server is down several days, you should be confirming the payments manually anyway.Could maybe increase the delay to a few hours.
Also is there option that BitPing requires specific reply from my server? Something like 'OK' ?
No, any 200 resp will do.I plan to use it for exchange and I think those are options that I need to make it reliable.
Then you should probaly run a local service, instead of depending on an external service.
It is now downloading blockchain again from beginning ?
How about incising that retry to at least few days? It can try frequently for the first hour and then it can try like once pen hour.
Also is there option that BitPing requires specific reply from my server? Something like 'OK' ?
I plan to use it for exchange and I think those are options that I need to make it reliable.
How about incising that retry to at least few days? It can try frequently for the first hour and then it can try like once pen hour.
Also is there option that BitPing requires specific reply from my server? Something like 'OK' ?
I plan to use it for exchange and I think those are options that I need to make it reliable.
Jump to: