BitPay's merchant processing during the alert/fork last night

marcus_of_augustus

legendary

Activity: 3920

Merit: 2349

Eadem mutata resurgo

Quote from: BitPay Business Solutions on March 12, 2013, 02:39:56 PM

Quote from: marcus_of_augustus on March 12, 2013, 02:35:48 PM

Good to see BitPay is taking care of concerns.

Are your systems using version 0.7 or 0.8 bitcoind backends?

we were on 0.7 bitcoind (and still are)

Thanks Tony ... you and your team should probably know about this if using 0.7

Quote

https://bitcointalk.org/index.php?topic=152208.msg1616926;topicseen#new

Melbustus

legendary

Activity: 1722

Merit: 1004

Thanks for the update.

And...

Quote

Kudos to the dev team, miners and pools operators for their quick diagnosis and correction of the problem. It is actually a great demonstration of how Bitcoin is more than just the software and the protocol it implements. It's also the network of users, miners, developers and service providers that can quickly react to situations such as this to preserve the integrity of the system.

^ Well said.

BitPay Business Solutions

hero member

Activity: 742

Merit: 500

Quote from: marcus_of_augustus on March 12, 2013, 02:35:48 PM

Good to see BitPay is taking care of concerns.

Are your systems using version 0.7 or 0.8 bitcoind backends?

we were on 0.7 bitcoind (and still are)

the good thing about the client going into "safe mode" is that it alerts you to a potential fork so you can quickly reach consensus with the other players to determine which one you need to follow.

This is an excellent example of how mining is critical to bitcoin, and the lack of mining in other systems like Ripple would have a much tougher time dealing with forks.

marcus_of_augustus

legendary

Activity: 3920

Merit: 2349

Eadem mutata resurgo

Good to see BitPay is taking care of concerns.

Are your systems using version 0.7 or 0.8 bitcoind backends?

BitPay Business Solutions

hero member

Activity: 742

Merit: 500

posted on our blog here:

http://blog.bitpay.com/2013/03/bugs-and-forks.html

Quote

Customers that placed orders during the time of the network issues may have noticed that their transactions were not immediately recognized. These transactions will eventually get credited to those invoices and confirmed by the network.
If you're a merchant, you may have received warnings about unconfirmed invoices, those invoices will eventually be confirmed and credited to your account.
We've checked all payments into BitPay and at this point there are no instances where a transaction has failed to confirm due to this incident.

One of the benefits for merchants using Bitpay is that we worry about these issues so they don't have to.

Topic: BitPay's merchant processing during the alert/fork last night (Read 974 times)