http://en.zaoniao.it/index.php?action=history&feed=atom&title=Lazy_API 2026-05-16T00:55:18Z Revision history for this page on the wiki MediaWiki 1.32.0 http://en.zaoniao.it/index.php?title=Lazy_API&diff=5629&oldid=prev 2019-06-08T13:50:08Z

<p>Created page with &quot;For the incredibly lazy and/or incompetent web developer, present is the lazy man&#039;s bitcoin API (copied from [https://bitcointalk.org/index.php?topic=4324.msg77187#msg77187 a...&quot;</p> <p><b>New page</b></p><div>For the incredibly lazy and/or incompetent web developer, present is the lazy man's bitcoin API (copied from [https://bitcointalk.org/index.php?topic=4324.msg77187#msg77187 a forum post]):<br /> <br /> ==Problem==<br /> <br /> Lazy web designer wants to use bitcoins without dealing with installing bitcoin on a server, installing a shopping cart interface, or using ugly merchant services with callbacks.<br /> <br /> ==Solution for receiving bitcoins==<br /> # Input a list of bitcoin receiving addresses to your database<br /> # Give a bitcoin address to a potential customer<br /> # Have the customer tell you when they have sent the coins and have at least 1 confirmation (you can choose a number higher than 1 if you are worried about double-spending)<br /> # Check blockexplorer to see if they sent the right amount<br /> # Give them what they paid for<br /> <br /> ==Risks==<br /> <br /> ===External Service===<br /> <br /> BlockExplorer is a service that is provided by a private party. There is no guarantee that the information provided by BlockExplorer matches the blockchain.<br /> <br /> There have not been any reports that BlockExplorer has reported transaction data incorrectly.<br /> <br /> ===Double Spending===<br /> <br /> A merchant is exposed to a [[double-spending]] attack when recognizing a payment before it has been [[confirmation|confirmed]] with a sufficient number of blocks.<br /> <br /> For an attacker to be successful with this double spend tactic a significant effort is required and thus the risk of this attack being made against the typical retail merchant is pretty minimal. It would not be advisable for a merchant with little to no recourse against an attacker to accept payment without a sufficient number of confirmations however.<br /> <br /> Note that this attack can be performed no matter which API or client is being used.<br /> <br /> <br /> ==Source==<br /> <br /> [http://bitcoin.it/ http://bitcoin.it/]<br /> <br /> ==See Also on BitcoinWiki==<br /> * [[SGAT]]<br /> * [[Trends Project]]<br /> * [[RAWG]]<br /> * [[SOFIN]]<br /> * [[BehaviourExchange]]<br /> <br /> [[Category:Manuals]]</div>

Admin