[Announce] bitcoinmonitor.net - Free professional notification/payment service - page 3.

Herbert

hero member

Activity: 488

Merit: 500

Two updates on the documentation:

As some user pointed out, the parameters in the callback are NOT in alphabetical order. (http://www.bitcoinmonitor.net/help/)
Your agent ID is now displayed in the dashboard after the agent's name. Also the API docs have been update with the info where to get the agent ID

And someone added bitcoinmonitor.net to ProgrammableWeb: http://www.programmableweb.com/api/bitcoinmonitor - Thank you Grin

Herbert

hero member

Activity: 488

Merit: 500

Just noticed that this thread started exactly 20 months ago! This feels like ages in the bitcoin world.
Just look at the exchange rate at that time - around 5 USD Grin

Herbert

hero member

Activity: 488

Merit: 500

The server hosting bitcoind backend went down yesterday evening, resulting in no notifications being sent. Got it running again this morning - system has caught up in the meantime and all missed notifications should be sent out. Sorry for the downtime :-/

Swapster

member

Activity: 131

Merit: 10

I am checking this out.

See how it goes...

Herbert

hero member

Activity: 488

Merit: 500

Hi,

today I finally made the transition to the new machine. The frontend is remaining on the old system, while bitcoind and backend is on the new system. All went smooth without noticable downtime. From the logs all seems fine, but please let me know if you experience any troubles.

No need to change anything on user-side - IP and hostname for website and API access stay the same.

I am quite confident that this will finally fix the downtimes experienced in the last weeks Wink

Herbert

hero member

Activity: 488

Merit: 500

Quote from: TheButterZone on April 01, 2013, 09:09:20 PM

Are you getting enough donations to cover costs? Blockchain.info now has the same notification facility (with even more options like SMS), even for Watch Only addresses. It's good to have redundancy but please don't go into the red!

Well, you can't say I'm swamped with dontations so far Wink

: https://blockchain.info/address/12AxBpvmqzYbSHmvZML6Xv9TPncJgdnikm

But that's okay for me. I use bitcoinmonitor.net also for myself / some of my own projects, and I also see it as a kind of contribution to the bitcoin project as a whole.

TheButterZone

legendary

Activity: 3038

Merit: 1032

RIP Mommy

Are you getting enough donations to cover costs? Blockchain.info now has the same notification facility (with even more options like SMS), even for Watch Only addresses. It's good to have redundancy but please don't go into the red!

Herbert

hero member

Activity: 488

Merit: 500

The last weeks there were some incidents resulting in notifications for confirmed transactions being delayed by several hours. The root cause is that the current hardware is not really up for the job anymore. I started this site more than a year ago and requirements drastically changed since then. With the current rate of transactions going on and the increase of blocksize I need to move to bigger hardware (Main issues are RAM and disk IO at the moment).
I have a better machine available already - Just need to find the time to move to it. Will keep you posted...

Herbert

hero member

Activity: 488

Merit: 500

You may have noticed delays in notifications for confirmed payments today. Bitcoind was running fine and all, except for the rpcthread to handle the jsonrpc commands. So monitoring did not complain, and all 0-conf notifications went through. But notifications for confirmations > 0 were stuck since block 221370.
I restarted bitcoind and the system is now catching up on the missed notifications.
Sorry for any trouble :-(

mrvision

sr. member

Activity: 527

Merit: 250

Quote from: Herbert on January 21, 2013, 06:53:46 PM

Unfortunately it turned out I introduced a nasty bug with the last changes regarding transactions with locktime set Undecided

. This bug could lead to delayed notification and even sometimes in completely missing notifications. I reverted the problematic changes so that notifications now work again as expected.

Thank you, i noticed there was a delay in the notifications that's why i asked.

Herbert

hero member

Activity: 488

Merit: 500

Unfortunately it turned out I introduced a nasty bug with the last changes regarding transactions with locktime set Undecided

. This bug could lead to delayed notification and even sometimes in completely missing notifications. I reverted the problematic changes so that notifications now work again as expected.

Herbert

hero member

Activity: 488

Merit: 500

Quote from: mrvision on January 20, 2013, 08:33:01 PM

Quote from: Herbert on January 14, 2013, 03:29:36 PM

Functionality/Security update:
Starting immediately bitcoinmonitor.net agents will NOT trigger 0-confirmation notifications on transactions which have a locktime set. Notifications for transactions with locktime will only trigger when the transaction gets a first confirmation.
The change is fully backwards-compatible: If you have an agent setup to notify on 0 confirmations you will get 2 notifications as soon as the transaction gets a confirmation: First for status "unconfirmed", followed by "one confirmation".

What's that? I need 0 confirmation notifications!!! Even when i know that i'm not serving the product until i have SIX notifications, i need 0 confirmation notification in order to make ajax continue.

No worries, you still get the 0 confirmations on all standard transactions. Only when a transaction comes which has a locktime set I don't trigger the 0-confirmation. This locktime feature is not used by any client at the moment (and also there is no real usecase for it in general as it is only halfway implemented). But it can be abused for trying double-spend attacks. So this change is a security feature to protect you, but will not affect any normal user of bitcoin.

mrvision

sr. member

Activity: 527

Merit: 250

Quote from: Herbert on January 14, 2013, 03:29:36 PM

Functionality/Security update:
Starting immediately bitcoinmonitor.net agents will NOT trigger 0-confirmation notifications on transactions which have a locktime set. Notifications for transactions with locktime will only trigger when the transaction gets a first confirmation.
The change is fully backwards-compatible: If you have an agent setup to notify on 0 confirmations you will get 2 notifications as soon as the transaction gets a confirmation: First for status "unconfirmed", followed by "one confirmation".

What's that? I need 0 confirmation notifications!!! Even when i know that i'm not serving the product until i have SIX notifications, i need 0 confirmation notification in order to make ajax continue.

Herbert

hero member

Activity: 488

Merit: 500

Functionality/Security update:
Starting immediately bitcoinmonitor.net agents will NOT trigger 0-confirmation notifications on transactions which have a locktime set. Notifications for transactions with locktime will only trigger when the transaction gets a first confirmation.
The change is fully backwards-compatible: If you have an agent setup to notify on 0 confirmations you will get 2 notifications as soon as the transaction gets a confirmation: First for status "unconfirmed", followed by "one confirmation".

mrvision

sr. member

Activity: 527

Merit: 250

Quote from: Herbert on December 21, 2012, 09:49:36 AM

System is up and running again, currently catching up missed transactions.
But, guys, please stop monitoring of 1dice... Addresses! This creates such a high number of notification events that the current hardware is at its limits. And at the moment I have no ressources (time and money) to scale up and move to bigger hardware.
So for now i removed all Satoshidice addresses from the system. I hope I don't need to implement a bitcoin address blacklist Grin

Thank you Herbert for your site. Its great! As soon as my service starts generating profit i'll send you a donation. I need bitcoinmonitor always up!!

BTW, i think you should have a 'premium account' (a cheap one) so you don't run out of money.

TheButterZone

legendary

Activity: 3038

Merit: 1032

RIP Mommy

How many of those are actively in use?

Raoul Duke

legendary

Activity: 1358

Merit: 1002

Quote from: TheButterZone on December 21, 2012, 03:55:11 PM

How easy is it to blacklist 1dice*?

That will also blacklist non-satoshidice addresses who start with that same pattern

TheButterZone

legendary

Activity: 3038

Merit: 1032

RIP Mommy

How easy is it to blacklist 1dice*?

Herbert

hero member

Activity: 488

Merit: 500

System is up and running again, currently catching up missed transactions.
But, guys, please stop monitoring of 1dice... Addresses! This creates such a high number of notification events that the current hardware is at its limits. And at the moment I have no ressources (time and money) to scale up and move to bigger hardware.
So for now i removed all Satoshidice addresses from the system. I hope I don't need to implement a bitcoin address blacklist Grin

Herbert

hero member

Activity: 488

Merit: 500

Site is having some serious troubles at the moment. Had to do a hard restart and waiting for it to come up again...

Topic: [Announce] bitcoinmonitor.net - Free professional notification/payment service - page 3. (Read 19527 times)