https://en.bitcoin.it/w/api.php?action=feedcontributions&feedformat=atom&user=Vladorz 2026-05-15T20:35:04Z User contributions MediaWiki 1.43.8 https://en.bitcoin.it/w/index.php?title=Lazy_API&diff=32155 2012-10-28T18:32:11Z

<p>Vladorz: /* Solution for receiving bitcoins */</p> <hr /> <div>For the incredibly lazy and/or incompetent web developer, present is the lazy man's bitcoin API (copied from [http://www.bitcoin.org/smf/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 sending bitcoins==<br /> <br /> Use the [https://mtgox.com/support/tradeAPI MtGox API]<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 (i.e. http://blockexplorer.com/q/getreceivedbyaddress/19hMEAaRMbEhfSkeU4GT8mgSuyR4t4M6TH/1) - the /1 is the number of confirmations you require<br /> # Give them what they paid for<br /> # After a reasonable amount of time has passed, you can re-use the address for another customer<br /> <br /> You could avoid having a list of addresses and reusing them by getting a new address via API call from one of the wallet services that support this feature (e.g. https://instawallet.org/static/api).<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 /> ==See Also==<br /> <br /> * [[BitAddress]] Generate address and private key pairs for an offline wallet<br /> * [[BitcoinNotify]] Register addresses and receive email or SMS alerts when a payment to that address occurs<br /> <br /> [[Category:Developer]]</div>

Vladorz https://en.bitcoin.it/w/index.php?title=Lazy_API&diff=32154 2012-10-28T13:47:45Z

<p>Vladorz: /* Solution for receiving bitcoins */</p> <hr /> <div>For the incredibly lazy and/or incompetent web developer, present is the lazy man's bitcoin API (copied from [http://www.bitcoin.org/smf/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 sending bitcoins==<br /> <br /> Use the [https://mtgox.com/support/tradeAPI MtGox API]<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 (i.e. http://blockexplorer.com/q/getreceivedbyaddress/19hMEAaRMbEhfSkeU4GT8mgSuyR4t4M6TH/1) - the /1 is the number of confirmations you require<br /> # Give them what they paid for<br /> # After a reasonable amount of time has passed, you can re-use the address for another customer<br /> <br /> You could avoid having a list of addresses and reusing them by getting a new address via API call from one of the wallet services that support this feature (i.e. https://instawallet.org/static/api).<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 /> ==See Also==<br /> <br /> * [[BitAddress]] Generate address and private key pairs for an offline wallet<br /> * [[BitcoinNotify]] Register addresses and receive email or SMS alerts when a payment to that address occurs<br /> <br /> [[Category:Developer]]</div>

Vladorz