|
|
|
|
|
|
by undefined0
4017 days ago
|
|
|
I know you're not seriously looking for an answer but meh... I've actually created a service (B2B) which requires bitcoin as I need atomicity, which bitcoin delivers perfectly (as long as I wait for N confirmations, it's pretty certain that I now _own_ the bitcoins). This is where PayPal fails, people can get refunds, chargebacks from credit card providers & PayPal can limit/suspend your account without notice (which they are famous for doing). I'm not a pro/anti bitcoin evangalist but I'm just throwing out there an example of what "programmable money" actually means. Bank transfers work well for non-refundable payments as well but most banks don't offer an API so bitcoins is the best alternative for my use case. Other advantages over PayPal are the OP codes and multisig which are a powerful thing for programmers to use. Bitcoin is great for merchants/developers but it has many disadvantages for customers. |
|
|
Atomicity is not a distributed database feature unique to Bitcoin, or even to PoW-based schemes in general.
Though if Bitcoin happens to work for your use case then by all means, don't reinvent the wheel.
> (as long as I wait for N confirmations, it's pretty certain that I now _own_ the bitcoins)
That's assuming your transaction makes it into a mined block. There have been backlogs of multiple blocks worth of transactions waiting to make it into a mined block, and there's been a huge blocksize debate going on partially because of that (which brings the potential for a fork of the blockchain into competing camps no less!)
Even after getting your transaction into a mined block, it's not unheard of to have orphaned blocks https://blockchain.info/charts/n-orphaned-blocks so you need to determine what level of atomicity you need. If it's actually 100% instead of 99.99% then even Bitcoin is not safe for your use case.