https://en.bitcoin.it/w/api.php?action=feedcontributions&feedformat=atom&user=DacoinminsterBitcoin Wiki - User contributions [en]2026-04-06T23:03:34ZUser contributionsMediaWiki 1.43.8https://en.bitcoin.it/w/index.php?title=User:Dacoinminster&diff=35317User:Dacoinminster2013-01-18T21:55:14Z<p>Dacoinminster: Created page with "I wrote: * The [http://bitcoinmedia.com/the-second-bitcoin-whitepaper/ The Second Bitcoin Whitepaper] * The Lazy API for accepting bitcoins."</p>
<hr />
<div>I wrote:<br />
<br />
* The [http://bitcoinmedia.com/the-second-bitcoin-whitepaper/ The Second Bitcoin Whitepaper]<br />
* The [[Lazy API]] for accepting bitcoins.</div>Dacoinminsterhttps://en.bitcoin.it/w/index.php?title=Talk:Lazy_API&diff=35316Talk:Lazy API2013-01-18T21:50:34Z<p>Dacoinminster: </p>
<hr />
<div>Is the title descriptive of the article's contents? Are the articles contents suitable / necessary where an article should exist? Wouldn't this be something that, if valuable enough, is added to the [[Merchant Howto]] and/or the [[How to accept Bitcoin, for small businesses]]? [[User:Sgornick|Sgornick]] 02:26, 2 April 2011 (GMT)<br />
<br />
Done! I'm particularly fond of this method of accepting bitcoins, since I paid a 20BTC bounty to Theymos to help make it happen. I'd hate for this info to get lost. [[User:dacoinminster|dacoinminster]] 13:50, 18 January 2013 (PST)</div>Dacoinminsterhttps://en.bitcoin.it/w/index.php?title=Talk:Lazy_API&diff=35315Talk:Lazy API2013-01-18T21:49:22Z<p>Dacoinminster: </p>
<hr />
<div>Is the title descriptive of the article's contents? Are the articles contents suitable / necessary where an article should exist? Wouldn't this be something that, if valuable enough, is added to the [[Merchant Howto]] and/or the [[How to accept Bitcoin, for small businesses]]? [[User:Sgornick|Sgornick]] 02:26, 2 April 2011 (GMT)<br />
<br />
Done! I'm particularly fond of this method of accepting bitcoins, since I paid a 20BTC bounty to Theymos to help make it happen. I'd hate for it to get lost.</div>Dacoinminsterhttps://en.bitcoin.it/w/index.php?title=How_to_accept_Bitcoin,_for_small_businesses&diff=35314How to accept Bitcoin, for small businesses2013-01-18T21:47:43Z<p>Dacoinminster: Added link to Lazy API</p>
<hr />
<div>{{merge|Merchant Howto}}<br />
<br />
This guide is intended for small business owners who wish to help promote Bitcoin by accepting it as payment for goods and services. It's written with the assumption that you operate a regular business that sells goods or services for regular national currency such as dollars, and that you wish to accept Bitcoin as another legal way to pay, and that you intend to pay taxes on your Bitcoin income just like any other income.<br />
<br />
With Bitcoin being touted as a way to conduct anonymous transactions and as way to compete with government currency, many small business owners wonder what's the right way to accept and account Bitcoin, or if it's legal or ethical, or whether and how they should pay taxes on income received through Bitcoin.<br />
<br />
As far as we know, Bitcoin isn't yet formally recognized by governments and authorities as a "currency". But in practice, Bitcoin is likely no different than accepting payment in other forms, such as cash, or gold, or scrip, or gift cards or foreign currency. We think that it is pretty much the same as the local businesses of Great Barrington, Massachusetts choosing to accept their locally-printed [http://www.reuters.com/article/2007/06/19/us-usa-economy-berkshares-idUSN0530157720070619 "Berkshire Bucks"] to support their local economy.<br />
<br />
==Starting to accept Bitcoin for transactions==<br />
Accepting Bitcoin at a small business is best started in whichever manner keeps the accounting simple for you. This will vary by the type of business you are operating.<br />
<br />
===Start with a sign===<br />
[[{{ns:file}}:WeAcceptBitcoin.png]]<br />
<br />
If you expect that the number of people interested in using Bitcoin is small, you might simply start by posting a sign or a note: "We Accept Bitcoin", and ask people to contact you directly in order to make a payment. Even if hardly anybody uses Bitcoin as a payment method, you're helping Bitcoin in two ways: one, by increasing awareness, and two, by making your customers more willing to accept Bitcoin as payment from others in the future, because now they know somewhere they can spend it.<br />
<br />
===Utilize a merchant solution===<br />
If you sell things on your website (goods or services), you'll want to use a [[#Merchant Services|Bitcoin merchant solution]] to accept the Bitcoins (you can usually opt to have them converted to USD or other currencies automatically). If you sell things in a brick and mortar shop, customers can pay using their mobile phone app (for example [http://www.paytunia.com Paytunia], [http://www.blockchain.info/wallet Blockchain.info's app] or [https://walletbit.com/mobile/ WalletBit Mobile]), so it's best if you can place a QR code near your register to which the customers can scan with their phone and pay (use http://ma.eatgold.com/accept to make a QR code sign).<br />
<br />
===Accounting===<br />
When a customer makes a payment, you might simply issue a credit to their account. Ideally, you want to enter it in a way that suggests you received a payment. You could consider entering it as a "discount", but you may want to consider whether this inappropriately disguises the nature of the transaction. If on the other hand, you're giving "discounts" for Bitcoins, but then you are selling the Bitcoins for currency and then counting that as income, then chances are good that your calculation of income is making up for it. Ask your accountant.<br />
<br />
===Businesses that offer gift cards===<br />
If your business sells gift cards or gift certificates, you may find that the easiest way to accept Bitcoin is to accept it only for the purchase of gift cards, and then require the gift cards to be used for actual purchases of goods or services. This way, the accounting practices you already have in place for processing gift cards can be put to use. The accounting for Bitcoins would then be minimized to tracking sales of a single SKU.<br />
<br />
This method is also ideal for retail food establishments and convenience stores, where the payment of Bitcoins through a mobile phone for a small daily food purchase might be cumbersome or disruptive, especially in front of a line of other customers. Bitcoins in this case would be best used to reload prepaid cards that can then be swiped at point-of-sale.<br />
<br />
If you don't accept gift cards, but you already accept credit cards through a swipe terminal, consider the possibility that you could add a retail gift card system through the swipe terminal you already own. Many point-of-sale terminals, including ones from VeriFone&reg;, are designed around the ability to support multiple applications on the same terminal. Gift cards are also highly profitable because of "breakage", or in other words, the fact that a significant percentage of them never get redeemed.<br />
<br />
You could consider adding a private label gift card program from a provider who specializes in this, not just as a jumpstart to accepting Bitcoins, but as an extra boost to income. A private label gift card service provider necessarily have to handle your funds - they can simply provide a solution that keeps track of the balance on the cards on your behalf, including features that allow users to check their balances by phone or by web. Such a solution, of course, is also what makes the cards swipeable through the card reader.<br />
<br />
===Businesses that mail invoices===<br />
Does your business send out invoices to customers? Adding one line may make a huge impact for the Bitcoin economy. Perhaps you list it as a payment option just after Visa, MasterCard, and American Express, even if that means your customer must call or e-mail to make a payment.<br />
<br />
If you have access to the programming expertise such that you can generate Bitcoin addresses programmatically, consider generating a brand new Bitcoin address for each invoice, and print it on the invoice. When a Bitcoin payment arrives, you'll automatically know where it should arrive.<br />
<br />
Customers might wonder how much BTC they should pay in order to satisfy an invoice in full. Your invoice might suggest an amount. For example, if your invoice is for $100 and BTC's are currently worth $1.24 each, your invoice might suggest that it can be paid in full ''"with a payment of 80.65 BTC if paid by (date)"''.<br />
<br />
You might be able to anticipate the possibility that even though a Bitcoin address can be printed on an invoice or payment stub, that they are very cumbersome for most people to type, especially being a mix of uppercase and lowercase letters. However, you should probably still do it anyway. The customer is probably going to want some paper trail for his payment. Giving him a pre-printed payment stub with a pre-printed address will satisfy that, because the customer can independently and publicly prove through [[Block Explorer]] that the payment took place.<br />
<br />
Does your business have a website? On your invoice, consider allowing them to go to a special URL to get the address to make a Bitcoin payment just by typing in their invoice number. For example, ''ht<nowiki>tps://ww</nowiki>w.yoursite.com/paybtc'' with a form they can enter their invoice number, or just ''ht<nowiki>tps://ww</nowiki>w.yoursite.com/paybtc/60365'' for paying invoice #60365. This way, they can see the Bitcoin address, copy and paste it directly into their Bitcoin client.<br />
<br />
Use a brand new address for each invoice whenever possible, and use it only once. This benefits the customer as it removes any ambiguity as to which customer is making which payment and for which invoice.<br />
<br />
===Avoiding fraud===<br />
<br />
You should also consider the possible risk that fraudsters could send counterfeit invoices to your customers, and entice them to make a payment to a Bitcoin address they control, instead of you. While that isn't likely in general - it depends on how well a fraudster could find out who your customers are in the first place - it would certainly be an unpleasant situation if it ever happened. One way you could control that is, whenever possible, never let people try to type Bitcoin addresses off payment stubs - instead, force people to get the full Bitcoin address from your website via secure SSL. But, still print ''most'' of the address on the payment stub (perhaps with four or five characters starred out), so that the customer's need for a paper trail can be satisfied, so they can prove they paid if there is ever a dispute.<br />
<br />
==Setting Prices==<br />
<br />
When a business accepts bitcoins for payment, there generally is the need to convert them to the currencies used for paying suppliers, employees and shareholders. Some merchants set prices based on the current market rate at the time the price quote is presented to the customer (merchant services like [http://www.bit-pay.com Bit-pay], [https://coinbase.com Coinbase], [http://paysius.com Paysius] or [https://walletbit.com WalletBit] do this automatically). <br />
<br />
[[Bitcoin Prices]] lists the exchange rate for many currencies on multiple exchanges.<br />
<br />
When prices are determined using an automated process, the current market rate can be based on either a current price or on a weighted average basis. [[Bitcoin Charts]] provides a [http://bitcoincharts.com/about/markets-api data feed that provides weighted prices].<br />
<br />
When bitcoin funds for purchases are received, some merchants instantly exchange those proceeds into the preferred currency used (again done automatically by [http://www.bit-pay.com Bit-pay], [https://coinbase.com Coinbase], [http://paysius.com Paysius] or [https://walletbit.com WalletBit]). Hedging for each transaction can nearly entirely eliminate exchange rate risk that the business is exposed to when accepting bitcoins for payment.<br />
<br />
==Contract==<br />
<br />
A sales contract might be used to ensure that specific terms are met to lessen the chances of a misunderstanding. For instance, the party sending payment is responsible for paying any [[transaction fee]] that might be necessary. A contract might specify that a transaction fee must be paid and what amount, so as to prevent the situation where the transaction is considered a low priority transaction and thus isn't confirmed quickly.<br />
<br />
Other items that might be addressed in a contract:<br />
<br />
* Requirement and handling of escrow through an [[:Category:Escrow_services|escrow service]].<br />
* Jurisdiction for disputes.<br />
* Refund policy (particularly with the exchange rate being volatile)<br />
<br />
==Paying taxes on Bitcoin income==<br />
[[Tax compliance]] is a topic of concern for small businesses. We aren't accountants or lawyers, and can't give legal or accounting advice.<br />
<br />
But in many respects, Bitcoin transactions work very much like cash. Just like Bitcoin, cash is anonymous and doesn't leave a paper trail, yet is widely used in commerce every day.<br />
<br />
Ask yourself how you would handle a cash transaction. Do you accept cash transactions? Do you normally pay taxes on cash transactions? The answer for Bitcoin should probably be the same.<br />
<br />
As for how to decide what a Bitcoin transaction is worth... the IRS, as far as we know, has never issued a guide mentioning how to value Bitcoin transactions. But they probably have rules and guidelines on how to value transactions made in foreign currency or "cash equivalents". We imagine the accounting would be similar.<br />
<br />
With Bitcoins, there's likely to be some difference between the value of BTC when you received them as payment, versus when you go to exchange them for another currency like USD, should you decide to do so. This scenario, likewise, would be no different if you accepted foreign currency or gold as payment. Under some scenarios, it might make sense to book the dollar value of BTC income as it is received, and then to book any difference incurred when it is exchanged for fiat currency. Under others, it might make sense to book the whole thing at the time of exchange.<br />
<br />
Perhaps you might talk to your accountant. You don't need to get into a discussion with your accountant about block chains and private keys or the philosophy behind a decentralized currency. By comparing the fundamentals of Bitcoins to accounting concepts already well understood by the public, you can probably get all the answers you need. What would you ask your accountant if you decided that you wanted to accept ''Berkshire Bucks'' or 1-ounce gold coins as payment?<br />
<br />
== Merchant Services ==<br />
* [https://www.bitpay.com BitPay] Bitcoin payment processor with mobile checkout solution<br />
* [https://merchant.bitutils.com BitUtils] Provides HTML buttons to start accepting bitcoins instantly. No server side setup required.<br />
* [https://coinbase.com/docs/merchant_tools/payment_buttons Coinbase] Offers payment buttons, checkout pages, shopping cart integration, and daily cash out to USD.<br />
* [https://mtgox.com/merchant MTGOX] Bitcoin payment processing<br />
* [https://paysius.com Paysius] Allows merchants to easily and securely accept Bitcoin on their website and track payments<br />
* [https://walletbit.com WalletBit] Bitcoin payment processor with mobile checkout solution<br />
* [http://fasterco.in Fasterco.in] Bitcoin payment processing for merchants and day-traders<br />
<br />
== Help this article ==<br />
<br />
This article is a stub, please add to it!<br />
<br />
==See Also==<br />
<br />
* [[Merchant Howto]]<br />
* [[In-store Transactions]]<br />
* [[Tax compliance]]<br />
* [[Securing online services]]<br />
* [[BitCoins Mobile]] provides accurate up to date pricing from multiple exchanges from your Apple iPad, iPhone, or iPod Touch.<br />
* [[Bitcoin PayFlow]] automates the process for accepting bitcoins<br />
* [[Lazy API]] The lazy (and possibly easiest?) way to accept bitcoin payments on your website<br />
<br />
[[Category:ECommerce]]<br />
[[Category:Local]]<br />
<br />
[[de:Bitcoin_als_Geschäft_akzeptieren]]</div>Dacoinminsterhttps://en.bitcoin.it/w/index.php?title=Merchant_Howto&diff=35313Merchant Howto2013-01-18T21:46:11Z<p>Dacoinminster: Added link to Lazy API</p>
<hr />
<div>{{merge|How to accept Bitcoin, for small businesses}}<br />
<br />
Accepting Bitcoins is easy, and there are several ways to do it.<br />
<br />
==Manually==<br />
# Download a bitcoin client<br />
# When a customer wants to buy something, send them a Bitcoin address where their payment should be sent.<br />
#* You can do this by clicking "New.." next to your address in the Bitcoin client and sending that address to the customer.<br />
# When payment comes in to that address, send the goods to your customer. Depending on the value of what you're selling, you may wish to wait until the payment shows Confirmed.<br />
# To issue a refund, obtain from the customer the [[Address|bitcoin address]] where the refund payment should be sent. The refund address will likely be different from the address used when the customer sent payment, especially if an [[EWallet]] was used by the customer.<br />
<br />
==Automated==<br />
===Pre-generating Bitcoin addresses===<br />
You can accept Bitcoins on your website without needing to use Bitcoin APIs or third party services if you pre-generate a large number of receiving Bitcoin addresses and store them in a database on your web server, and dispense them one-by-one to customers when they are ready to pay. This way, your web server never actually handles the bitcoins - it simply gives out addresses belonging to a wallet you maintain elsewhere. By using a unique address per order, you will always know which payment belongs to which order. [https://www.casascius.com Example of website using this method]<br />
<br />
To pre-generate addresses, use a tool such as [[Pywallet]] (which can generate a wallet.dat file) or [[Bitcoin Address Utility]] (which can generate a CSV file). In both cases, you will be generating a list of [[Address|Bitcoin address]]es along with their corresponding [[private key]]s. Only the Bitcoin addresses (not the private keys) should be loaded on the web server.<br />
<br />
If you are shipping goods manually, you can use the Bitcoin software to check for incoming payments, or alternately consider using [[Block Explorer]] or [[Abe]] to verify payment when you're about to ship. To make this easy, make your website provide you a full hyperlink that includes the proper receiving address: ht<nowiki>tp://www</nowiki>.blockexplorer.com/address/ADDRESSGOESHERE.<br />
<br />
If you are delivering digital goods or services and want to be able to deliver instantly upon payment and/or confirmation, you can use a third-party service such as [[Bitcoin Notify]] to tell your website when a payment has been received. This sort of service requires no significant API implementation - they will simply make a POST to your website or send you an e-mail when a payment has been received on one of your addresses.<br />
<br />
If you keep Bitcoins off your web server, this ensures your wallet cannot be stolen if your web server experiences a security intrusion. Your risk becomes limited to the possibility that a successful intruder could add his own addresses to your address pool and steal funds from a few incoming orders until you detect the problem, however, this is a relatively controllable risk.<br />
<br />
===Using a third-party plugin===<br />
You can use an existing [[:Category:Shopping Cart Interfaces|shopping cart interface]] from a 3rd party to automatically handle all Bitcoin payments on your website. If you want to develop the system yourself, you can utilize the Bitcoin client's [[API tutorial (JSON-RPC)|JSON-RPC API]] to automatically accept payments.<br />
<br />
Things to note if you build it yourself:<br />
# When a customer orders something on your website it records:<br />
#* Bitcoin address that payment should be sent to<br />
#* Order details (delivery address etc.)<br />
#* Customer's refund address (optional - if you wish you can ask for this later, only in cases a refund is required)<br />
#* Payment amount<br />
# When payment arrives, checks that they have paid the correct amount or not, and informs you<br />
#* You dispatch the goods to the customer and mark the order as fulfilled<br />
#* If you cannot dispatch the goods you mark the order as denied and ask the customer for a refund address (unless you already have it from earlier) to send a refund.<br />
# Forwards the funds to bitcoin address of your choice<br />
<br />
==Common Errors==<br />
It has been observed on occasion that a business funnels all its orders through the same Bitcoin address, and asks people to send some BTC, then send email describing the timing and the amount of the transaction to 'claim' it. This is '''not''' secure, since anyone can see the transaction details using a tool such as [[Block Explorer]], and then try to claim someone else's transaction as theirs.<br />
<br />
Do not do this. Give each customer a unique Bitcoin address.<br />
<br />
==Listing your business on the Bitcoin Trade page==<br />
<br />
Anyone can add and update a listing on the [[Trade|trade]] page. Just register if you haven't and add to the appropriate category. If you'ld like assistance, perhaps someone in the [http://webchat.freenode.net/?channels=#bitcoin-marketing #bitcoin-marketing] IRC channel would be willing to assist.<br />
<br />
==See Also==<br />
* [[In-store Transactions]]<br />
* [[:Category:Shopping Cart Interfaces|Shopping Cart Interfaces]]<br />
* [[Securing online services]]<br />
* [[Bitcoin Evolution]] handles sales tracking and order forms; requires Bitcoin client for actual payment<br />
* [[Bitcoin PayFlow]] automates the process for accepting bitcoins<br />
* [[Bitcoin API Services]] an easy solution for securely accepting Bitcoins and updating BTC prices<br />
* [[BitcoinNotify]] merchants solution for accepting Bitcoins and updating BTC prices<br />
* [[Coinbase]] Offers payment buttons, checkout pages, shopping cart integration, and daily cash out to USD.<br />
* [[Converter|Bitcoin Javascript Converter]] displays a price in BTCs after converting from USDs.<br />
* [[How to accept Bitcoin, for small businesses]]<br />
* [[:Category:Marketing|Marketing]]<br />
* [[URI Scheme]]<br />
* [[Promotional graphics]], buttons and logos<br />
* [[BitPay]] Merchant solutions for Bitcoin<br />
* [http://paysius.com Paysius] Allows merchants to easily and securely accept Bitcoin payments on their website<br />
* [http://merchant.bitutils.com BitUtils Merchant] Provides html buttons for accepting bitcoins<br />
* [[WalletBit]] Bitcoin gateway and Merchant solutions<br />
* [[Fasterco.in]] Bitcoin payment processing for merchants and day-traders<br />
* [[Lazy API]] The lazy (and possibly easiest?) way to accept bitcoin payments on your website<br />
[[Category:ECommerce]]</div>Dacoinminsterhttps://en.bitcoin.it/w/index.php?title=Lazy_API&diff=35312Lazy API2013-01-18T21:42:23Z<p>Dacoinminster: Fixed broken link</p>
<hr />
<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 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 />
[[de:API_für_Faule]]<br />
<br />
[[Category:Developer]]</div>Dacoinminsterhttps://en.bitcoin.it/w/index.php?title=Meetups&diff=10113Meetups2011-06-08T20:14:56Z<p>Dacoinminster: </p>
<hr />
<div>Don't add everyone who's going the the "Who?" column, just prominent bitcoin members and organizers. Also see [http://bitcoin.meetup.com bitcoin.meetup.com]<br />
<br />
{| class="wikitable"<br />
|-<br />
! Group<br />
! When?<br />
! Where?<br />
! Who?<br />
! Other Notes<br />
|-<br />
|<br />
| 7:00 PM, June 16<br />
| <br />
| Boston, MA<br />
| <br />
|-<br />
| [http://www.meetup.com/bitcoin New York Bitcoin Users]<br />
| 7:00 PM, 2nd Saturday of every month ([http://www.meetup.com/bitcoin/events/past past meetings])<br />
| OnlyOneTV Studios - 290 Fifth Ave New York, NY<br />
| Bruce Wagner (Organizer) and others<br />
| <br />
|-<br />
| [http://www.meetup.com/BitcoinDC Washington, DC Bitcoin Users]<br />
| 7:00 PM, 1st Monday of every month ([http://www.meetup.com/BitcoinDC/#past past meetings])<br />
| Northside Social, 3211 Wilson Blvd Arlington, VA<br />
| [[User:Dduane|Darrell Duane]] (Organizer) and others<br />
|<br />
|-<br />
| [http://www.meetup.com/Silicon-Valley-Bitcoin-Users Silicon Valley Bitcoin Users]<br />
| 7:00 PM, Tuesday, June 14, 2011 ([http://www.meetup.com/Silicon-Valley-Bitcoin-Users/events/past past meetings])<br />
| 140B S Whisman Road Mountain View, CA <br />
| Brian Mcqueen and others<br />
|<br />
|-<br />
| [http://www.meetup.com/BitcoinChicago Chicago]<br />
| No regular schedule yet ([http://www.meetup.com/BitcoinChicago/events/past past meetings])<br />
| Sunnyvale Art Gallery Cafe, 251 W El Camino Real Sunnyvale, CA<br />
| Igor<br />
|<br />
|-<br />
| [http://www.meetup.com/denver-bitcoin Denver]<br />
| First meeting June 4th, 2011 ([http://www.meetup.com/denver-bitcoin/events/past past meetings])<br />
| Gypsy House Cafe - 1279 Marion St Denver, CO<br />
| bearbones<br />
|<br />
|-<br />
| [http://www.meetup.com/bitcoinSF Bitcoin SF]<br />
| Saturday, June 4, 2011 ([http://www.meetup.com/bitcoinSF past meetings])<br />
| SFSU - 1600 Holloway Ave. San Francisco, CA<br />
| Brian Mcqueen and others<br />
|<br />
|-<br />
| [http://www.meetup.com/Los-Angeles-Digital-Currency-Innovators-Group Los Angeles Digital Currency Innovators]<br />
| Thursday July 7th, 2011, 7 PM<br />
| (mt)/Media Temple, Culver City, CA<br />
| [[User:sgornick|Stephen Gornick]] (Interim organizer) and others<br />
| Seeking meetup coordinator<br />
|-<br />
| [http://www.meetup.com/Las-Vegas-Bitcoin-Users Las Vegas Bitcoin Users]<br />
| Thursday, June 9, 2011, 7:00 PM ([http://www.meetup.com/Las-Vegas-Bitcoin-Users#past past meetings])<br />
| Putters, 6945 South Rainbow Boulevard, Las Vegas, NV<br />
| Mark Russell<br />
|<br />
|-<br />
| [http://www.meetup.com/Bitcoin-Twin-Cities-Users-Meetup Bitcoin Twin Cities Users]<br />
| Friday, June 10, 2011, 6:30 PM<br />
| Joule - 1200 Washington Ave S Minneapolis, MN<br />
| Mac Manson<br />
|<br />
|-<br />
| [http://www.hive13.org/?p=310 Hive13 Hackerspace]<br />
| Bitcoin Exchange, Every Tuesday, 7:30 PM<br />
| Hive13 - 2929 Spring Grove Avenue, Cincinnati, OH<br />
| <br />
|<br />
|-<br />
| [[Melbourne Bitcoin Community]]<br />
| Forming<br />
| Suggest a location, and a date and time<br />
| @da2ce7 on Freenode Channel: #bitcoin-aus<br />
|<br />
|-<br />
| [[Bitcoin:Tokyo meetup|Tokyo]]<br />
| <br />
| <br />
| [[User:MagicalTux|Magical Tux]] (Organizer) and others<br />
|<br />
|-<br />
| [http://meetup.com/Bitcoin-Canada Vancouver Canada]<br />
| ([http://www.meetup.com/Bitcoin-Canada/#past past meetings])<br />
| The Brickhouse - 730 Main St.<br />
| humble (and others)<br />
|<br />
|-<br />
| [http://www.bitcoin.org/smf/index.php?topic=6725.0 Zurich Switzerland]<br />
| Semi-regular, about once a month<br />
| Oliver Twist Pub<br />
| Stefan Thomas (weusecoins), Mike Hearn (bitcoinj), bitdragon, Luzius (Wuala), more ... <br />
|<br />
|-<br />
| [[Seattle Bitcoin Meetup]]<br />
| Anybody interested?<br />
| Suggest a location, and a date and time<br />
| dacoinminster<br />
|<br />
|-<br />
|}<br />
<br />
[[Category:Local]]<br />
<br />
[[de:Treffen]]</div>Dacoinminsterhttps://en.bitcoin.it/w/index.php?title=Lazy_API&diff=6738Lazy API2011-04-04T16:14:52Z<p>Dacoinminster: </p>
<hr />
<div>For the incredibly lazy and/or incompetent web developer, I present 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 (me) 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 if one of the wallet services someday lets you get a new address via API call, but this will work for now.<br />
<br />
'''Bad idea:'''<br />
<br />
Selling bars of gold this way (owner of blockexplorer.com could rip you off)<br />
<br />
'''Good(?) idea:'''<br />
<br />
Selling naked pictures of your grandma this way (owner of blockexplorer.com won't bother)<br />
<br />
'''Shameless begging:'''<br />
<br />
If this info is useful to you, please consider a donation: 19hMEAaRMbEhfSkeU4GT8mgSuyR4t4M6TH<br />
<br />
Thanks to theymos for making changes to blockexplorer.com to make it even easier to do this. You can support blockexplorer.com by donating to 1Cvvr8AsCfbbVQ2xoWiFD1Gb2VRbGsEf28<br />
<br />
[[Category:Developer]]</div>Dacoinminsterhttps://en.bitcoin.it/w/index.php?title=Lazy_API&diff=6737Lazy API2011-04-04T16:04:33Z<p>Dacoinminster: </p>
<hr />
<div>For the incredibly lazy and/or incompetent web developer, I present 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 (me) wants to use bitcoins without dealing with installing bitcoin on a server, installing a shopping card 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 if one of the wallet services someday lets you get a new address via API call, but this will work for now.<br />
<br />
'''Bad idea:'''<br />
<br />
Selling bars of gold this way (owner of blockexplorer.com could rip you off)<br />
<br />
'''Good(?) idea:'''<br />
<br />
Selling naked pictures of your grandma this way (owner of blockexplorer.com won't bother)<br />
<br />
'''Shameless begging:'''<br />
<br />
If this info is useful to you, please consider a donation: 19hMEAaRMbEhfSkeU4GT8mgSuyR4t4M6TH<br />
<br />
Thanks to theymos for making changes to blockexplorer.com to make it even easier to do this. You can support blockexplorer.com by donating to 1Cvvr8AsCfbbVQ2xoWiFD1Gb2VRbGsEf28<br />
<br />
[[Category:Developer]]</div>Dacoinminsterhttps://en.bitcoin.it/w/index.php?title=Lazy_API&diff=6736Lazy API2011-04-04T16:02:34Z<p>Dacoinminster: </p>
<hr />
<div>For the incredibly lazy and/or incompetent web developer, I present 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 (me) wants to use bitcoins without dealing with installing bitcoin on a server, installing a shopping card 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 if one of the wallet services someday lets you get a new address via API call, but this will work for now.<br />
<br />
'''Bad idea:'''<br />
<br />
Selling bars of gold this way (owner of blockexplorer.com could rip you off)<br />
<br />
'''Good(?) idea:'''<br />
<br />
Selling naked pictures of your grandma this way (owner of blockexplorer.com won't bother)<br />
<br />
'''Shameless begging:'''<br />
<br />
If this info is useful to you, please consider a donation: 19hMEAaRMbEhfSkeU4GT8mgSuyR4t4M6TH<br />
<br />
Thanks to theymos for making changes to blockexplorer.com to make it even easier to do this. You can support his blockexplorer.com by donating to 1Cvvr8AsCfbbVQ2xoWiFD1Gb2VRbGsEf28<br />
<br />
[[Category:Developer]]</div>Dacoinminsterhttps://en.bitcoin.it/w/index.php?title=Lazy_API&diff=6735Lazy API2011-04-04T16:00:50Z<p>Dacoinminster: </p>
<hr />
<div>For the incredibly lazy and/or incompetent web developer, I present 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 (me) wants to use bitcoins without dealing with installing bitcoin on a server, installing a shopping card 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 if one of the wallet services someday lets you get a new address via API call, but this will work for now.<br />
<br />
'''Bad idea:'''<br />
<br />
Selling bars of gold this way (owner of blockexplorer.com could rip you off)<br />
<br />
'''Good(?) idea:'''<br />
<br />
Selling naked pictures of your grandma this way (owner of blockexplorer.com won't bother)<br />
<br />
'''Shameless begging:'''<br />
<br />
If this info is useful to you, please consider a donation: 19hMEAaRMbEhfSkeU4GT8mgSuyR4t4M6TH<br />
<br />
[[Category:Developer]]</div>Dacoinminsterhttps://en.bitcoin.it/w/index.php?title=Lazy_API&diff=6734Lazy API2011-04-04T16:00:22Z<p>Dacoinminster: </p>
<hr />
<div>For the incredibly lazy and/or incompetent web developer, I present 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 (me) wants to use bitcoins without dealing with installing bitcoin on a server, installing a shopping card 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 if one of the wallet services someday lets you get a new address via API call, but this will work for now.<br />
<br />
'''Bad idea:'''<br />
<br />
Selling bars of gold this way (owner of blockexplorer.com could rip you off)<br />
<br />
'''Good(?) idea:'''<br />
<br />
Selling naked pictures of your grandma this way (owner of blockexplorer.com won't bother)<br />
<br />
'''Shameless begging:'''<br />
<br />
If this info is useful to you, please consider a donation: 19hMEAaRMbEhfSkeU4GT8mgSuyR4t4M6TH<br />
<br />
[[Category:Developer]]</div>Dacoinminsterhttps://en.bitcoin.it/w/index.php?title=Lazy_API&diff=6520Lazy API2011-04-01T16:43:50Z<p>Dacoinminster: </p>
<hr />
<div>For the incredibly lazy and/or incompetent web developer, I present 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 (me) wants to use bitcoins without dealing with installing bitcoin on a server, installing a shopping card 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<br />
# Check blockexplorer to see if they sent the right amount (i.e. http://blockexplorer.com/address/19hMEAaRMbEhfSkeU4GT8mgSuyR4t4M6TH)<br />
# Wait for more blocks (confirmations) if paranoid (look for the latest block number to go up here: http://blockexplorer.com/)<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 if one of the wallet services someday lets you get a new address via API call, but this will work for now.<br />
<br />
'''Bad idea:'''<br />
<br />
Selling bars of gold this way (owner of blockexplorer.com could rip you off)<br />
<br />
'''Good(?) idea:'''<br />
<br />
Selling naked pictures of your grandma this way (owner of blockexplorer.com won't bother)<br />
<br />
'''Shameless begging:'''<br />
<br />
If this info is useful to you, please consider a donation: 19hMEAaRMbEhfSkeU4GT8mgSuyR4t4M6TH<br />
<br />
[[Category:Developer]]</div>Dacoinminsterhttps://en.bitcoin.it/w/index.php?title=Lazy_API&diff=6519Lazy API2011-04-01T16:38:13Z<p>Dacoinminster: </p>
<hr />
<div>For the incredibly lazy and/or incompetent web developer, I present 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 (me) wants to use bitcoins without dealing with installing bitcoin on a server, installing a shopping card 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<br />
# Check blockexplorer to see if they sent the right amount (i.e. http://blockexplorer.com/address/19hMEAaRMbEhfSkeU4GT8mgSuyR4t4M6TH)<br />
# Wait for more blocks (confirmations) if paranoid<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 if one of the wallet services someday lets you get a new address via API call, but this will work for now.<br />
<br />
'''Bad idea:'''<br />
<br />
Selling bars of gold this way (owner of blockexplorer.com could rip you off)<br />
<br />
'''Good(?) idea:'''<br />
<br />
Selling naked pictures of your grandma this way (owner of blockexplorer.com won't bother)<br />
<br />
'''Shameless begging:'''<br />
<br />
If this info is useful to you, please consider a donation: 19hMEAaRMbEhfSkeU4GT8mgSuyR4t4M6TH<br />
<br />
[[Category:Developer]]</div>Dacoinminsterhttps://en.bitcoin.it/w/index.php?title=Lazy_API&diff=6518Lazy API2011-04-01T16:37:56Z<p>Dacoinminster: </p>
<hr />
<div>For the incredibly lazy and/or incompetent web developer, I present 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 (me) wants to use bitcoins without dealing with installing bitcoin on a server, installing a shopping card 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<br />
# Check blockexplorer to see if they sent the right amount (i.e. http://blockexplorer.com/address/19hMEAaRMbEhfSkeU4GT8mgSuyR4t4M6TH)<br />
# Wait for more blocks (confirmations) if paranoid<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 if one of the wallet services someday lets you get a new address via API call, but this will work for now.<br />
<br />
'''Bad idea:'''<br />
<br />
Selling bars of gold this way (owner of blockexplorer.com could rip you off)<br />
<br />
'''Good(?) idea:'''<br />
<br />
Selling naked pictures of your grandma this way (owner of blockexplorer.com won't bother)<br />
<br />
'''Shameless begging:'''<br />
If this info is useful to you, please consider a donation: 19hMEAaRMbEhfSkeU4GT8mgSuyR4t4M6TH<br />
<br />
[[Category:Developer]]</div>Dacoinminsterhttps://en.bitcoin.it/w/index.php?title=PHP_developer_intro&diff=6517PHP developer intro2011-04-01T16:30:35Z<p>Dacoinminster: </p>
<hr />
<div>'''L'''inux '''A'''pache '''M'''ySQL '''P'''HP + Bitcoin tutorial.<br />
<br />
For the sake of this tutorial we assume an Ubuntu server running with PHP. The use case here is integrating a shopping system to accept Bitcoins. We assume some knowledge of Bitcoin and experience in PHP.<br />
<br />
You can substitute any other language here for PHP. See the associated [[API reference (JSON-RPC)|API reference]] pages for info on other languages.<br />
<br />
You will run Bitcoin in daemon mode. The way PHP communicates is through localhost HTTP requests. You use a library called [http://jsonrpcphp.org/ JSON-RPC] to call the various functions. It will respond back with a [http://en.wikipedia.org/wiki/Json JSON object].<br />
<br />
== Setting up Bitcoin ==<br />
<br />
You need the bitcoind command-line daemon. You can either compile it from source or download a binary from the bitcoin.org homepage.<br />
<br />
See [[Running Bitcoin]] for details on configuring bitcoin.<br />
<br />
Before running bitcoind you will need to create a file in the bitcoin data directory (~/.bitcoin/.bitcoin.conf on Linux):<br />
<source lang="bash"><br />
rpcuser=user<br />
rpcpassword={you MUST pick a unique password to be secure}<br />
</source><br />
<br />
Now run bitcoind:<br />
<source lang="bash"><br />
$ ./bitcoind<br />
# wait a few seconds for it to start up<br />
$ ./bitcoind getinfo<br />
# various info shown<br />
$ ./bitcoind help<br />
# help on commands<br />
</source><br />
<br />
Bitcoin is now initialising and you must wait until "blocks" is at the [http://bitcoinwatch.com/ current count].<br />
<br />
== First steps ==<br />
<br />
Assuming Bitcoin has finished the initialisation process; download the file jsonRPCClient.php from [http://jsonrpcphp.org/ JSON-RPC PHP]. The other files can be safely discarded.<br />
<br />
<source lang="php"><br />
require_once 'jsonRPCClient.php';<br />
<br />
$bitcoin = new jsonRPCClient('http://user:password@127.0.0.1:8332/');<br />
<br />
echo "<pre>\n";<br />
print_r($bitcoin->getinfo());<br />
echo "</pre>";<br />
</source><br />
<br />
== Precision ==<br />
<br />
Bitcoin amounts can range from 0.00000001 to 21,000,000. To avoid rounding errors, you must make sure your PHP implementation supports the full range of bitcoin values without losing precision. Most PHP implementations use IEEE 64-bit double-precision floating point numbers, which have 53 bits of precision, which is enough to correctly represent the full range of bitcoin values.<br />
<br />
See [[Proper Money Handling (JSON-RPC)]] for more information.<br />
<br />
If your PHP implementation does not support 64-bit numbers, you must use a version of bitcoind that sends values as strings (genjix maintains a fork at http://github.com/genjix/bitcoin) and use the [http://php.net/manual/en/ref.gmp.php GMP] and [http://php.net/manual/en/ref.bc.php BC Math] libraries for all calculations involving bitcoin amounts.<br />
<br />
== Accounts ==<br />
<br />
In Bitcoin, money is sent to addresses. Your balance is the total of all the money in all the address in your wallet.<br />
<br />
Bitcoin goes another step. You can have accounts. Each account holds multiple addresses and adds like a mini-Bitcoin.<br />
<br />
<source lang="bash"><br />
$ ./bitcoind listaccounts<br />
# show list of accounts and various info for each one<br />
$ ./bitcoind getaccountaddress user889<br />
# get an address to receive money to that is unique for the account user889<br />
$ ./bitcoind getbalance user889<br />
# get the sum of all the money in the addresses owned by the account user889<br />
</source><br />
<br />
In your shopping system, each user should have a unique username. You then query bitcoin for a unique address using $bitcoin->getaccountaddress("user889"); [gets the first address for user889] or $bitcoin->getnewaddress("user889"); [creates a new address for user889].<br />
<br />
The customer then deposits to this address.<br />
<br />
You can check the funds for that customer by doing $bitcoin->getbalance("user889", 4);. The 4 indicates the minimum number of confirmations we will accept before assuming this payment is valid.<br />
<br />
=== getnewaddress vs getaccountaddress ===<br />
<br />
Using getnewaddress helps increase the anonymity of your customers by making it hard to track their payments from the POV of a malicious agent. However running it too often will cause your wallet to become filled with many empty addresses.<br />
<br />
I recommend that you run do something like:<br />
<source lang="php"><br />
<?php<br />
require_once('jsonRPCClient.php');<br />
$bitcoin = new jsonRPCClient('http://root:root@127.0.0.1:8332/'); <br />
# now check for appropriate funds in user account<br />
try {<br />
$username = ...<br />
if(isset($_SESSION['sendaddress']))<br />
$sendaddress = $_SESSION['sendaddress'];<br />
else {<br />
$sendaddress = $bitcoin->getnewaddress($username);<br />
$_SESSION['sendaddress'] = $sendaddress;<br />
}<br />
$balance = $bitcoin->getbalance($username);<br />
}<br />
catch (Exception $e) {<br />
die("<p>Server error! Please contact the admin.</p>");<br />
}<br />
?><br />
</source><br />
<br />
This creates a new address at the beginning of every new session, and stores it in the session variable.<br />
<br />
<br />
==See Also==<br />
<br />
* [[API reference (JSON-RPC)]]<br />
* [[Lazy_API]]<br />
<br />
[[Category:Developer]]</div>Dacoinminsterhttps://en.bitcoin.it/w/index.php?title=Original_Bitcoin_client/API_calls_list&diff=6516Original Bitcoin client/API calls list2011-04-01T16:29:10Z<p>Dacoinminster: /* See Also */</p>
<hr />
<div>Bitcoin API call list (as of version 0.3.19)<br />
<br />
== Common operations ==<br />
<br />
=== Listing my bitcoin addresses ===<br />
<br />
Listing the bitcoin addresses in your wallet is easily done via ''listreceivedbyaddress''. It normally lists only addresses which already have received transactions, however you can list all the addresses by setting the first argument to 0, and the second one to true<br />
<br />
== Full list ==<br />
<br />
Required arguments are denoted inside &lt; and &gt; Optional arguments are inside [ and ].<br />
<br />
{|class="wikitable"<br />
! Command !! Parameters !! Description<br />
|-<br />
| backupwallet || <destination> || Safely copies wallet.dat to destination, which can be a directory or a path with filename.<br />
|-<br />
| getaccount || <bitcoinaddress> || Returns the account associated with the given address.<br />
|-<br />
| getaccountaddress || <account> || Returns the current bitcoin address for receiving payments to this account.<br />
|-<br />
| getaddressesbyaccount || <account> || Returns the list of addresses for the given account.<br />
|-<br />
| getbalance || [account] [minconf=1] || If [account] is not specified, returns the server's total available balance.<br/>If [account] is specified, returns the balance in the account.<br />
|-<br />
| getblockbycount || height || Dumps the block existing at specified height. '''Note: this is not available in the official release'''<br />
|-<br />
| getblockcount || || Returns the number of blocks in the longest block chain.<br />
|-<br />
| getblocknumber || || Returns the block number of the latest block in the longest block chain.<br />
|-<br />
| getconnectioncount || || Returns the number of connections to other nodes.<br />
|-<br />
| getdifficulty || || Returns the proof-of-work difficulty as a multiple of the minimum difficulty.<br />
|-<br />
| getgenerate || || Returns true or false whether bitcoind is currently generating hashes<br />
|-<br />
| gethashespersec || || Returns a recent hashes per second performance measurement while generating.<br />
|-<br />
| getinfo || || Returns an object containing various state info.<br />
|-<br />
| getnewaddress || [account] || Returns a new bitcoin address for receiving payments. If [account] is specified (recommended), it is added to the address book so payments received with the address will be credited to [account].<br />
|-<br />
| getreceivedbyaccount || <account> [minconf=1] [includeempty=false] || Returns the total amount received by addresses with <account> in transactions with at least [minconf] confirmations.<br />
|-<br />
| getreceivedbyaddress || <bitcoinaddress> [minconf=1] [includeempty=false] || Returns the total amount received by <bitcoinaddress> in transactions with at least [minconf] confirmations.<br />
|-<br />
| gettransaction || <txid> || Get detailed information about <txid><br />
|-<br />
| [[getwork]] || [data] || If [data] is not specified, returns formatted hash data to work on:<br />
* "midstate" : precomputed hash state after hashing the first half of the data<br />
* "data" : block data<br />
* "hash1" : formatted hash buffer for second hash<br />
* "target" : little endian hash target<br />
If [data] is specified, tries to solve the block and returns true if it was successful.<br />
|-<br />
| help || [command] || List commands, or get help for a command.<br />
|-<br />
| listreceivedbyaccount || [minconf=1] [includeempty=false] || Returns an array of objects containing:<br />
* "account" : the account of the receiving addresses<br />
* "amount" : total amount received by addresses with this account<br />
* "confirmations" : number of confirmations of the most recent transaction included<br />
|-<br />
| listreceivedbyaddress || [minconf=1] [includeempty=false] || Returns an array of objects containing:<br />
* "address" : receiving address<br />
* "account" : the account of the receiving address<br />
* "amount" : total amount received by the address<br />
* "confirmations" : number of confirmations of the most recent transaction included<br />
To get a list of accounts on the system, execute bitcoind listreceivedbyaddress 0 true<br />
|-<br />
| listtransactions || <account> [count=10] || Returns up to [count] most recent transactions for account <account>.<br />
|-<br />
| move || <fromaccount> <toaccount> <amount> [minconf=1] [comment] || Move from one account in your wallet to another.<br />
|-<br />
| sendfrom || <fromaccount> <tobitcoinaddress> <amount> [minconf=1] [comment] [comment-to] || <amount> is a real and is rounded to the nearest 0.01<br />
|-<br />
| sendtoaddress || <bitcoinaddress> <amount> [comment] [comment-to] || <amount> is a real and is rounded to the nearest 0.01<br />
|-<br />
| setaccount || <bitcoinaddress> <account> || Sets the account associated with the given address.<br />
|-<br />
| setgenerate || <generate> [genproclimit] || <generate> is true or false to turn generation on or off.<br/>Generation is limited to [genproclimit] processors, -1 is unlimited.<br />
|-<br />
| stop || || Stop bitcoin server.<br />
|-<br />
| validateaddress || <bitcoinaddress> || Return information about <bitcoinaddress>.<br />
|}<br />
<br />
==See Also==<br />
<br />
* [[Original Bitcoin client]]<br />
* [[API reference (JSON-RPC)]]<br />
* [[Lazy_API]]<br />
<br />
[[Category:Technical]]<br />
[[Category:Developer]]</div>Dacoinminsterhttps://en.bitcoin.it/w/index.php?title=API_reference_(JSON-RPC)&diff=6515API reference (JSON-RPC)2011-04-01T16:28:07Z<p>Dacoinminster: /* See Also */</p>
<hr />
<div>== Controlling Bitcoin ==<br />
<br />
Run ''bitcoind'' or ''bitcoin -server''. You can control it via the command-line or by HTTP-JSON-RPC commands.<br />
<br />
You must create a bitcoin.conf configuration file setting an rpcuser and rpcpassword; see [[Running Bitcoin]] for details.<br />
<br />
Now run:<br />
$ ./bitcoind<br />
bitcoin server starting<br />
$ ./bitcoind help<br />
# shows the help text<br />
<br />
A [[Original Bitcoin client/API Calls list|list of RPC calls]] will be shown.<br />
<br />
$ ./bitcoind getbalance<br />
2000.00000<br />
<br />
== JSON-RPC ==<br />
<br />
Running Bitcoin with the -server argument (or running bitcoind) tells it to function as a [http://json-rpc.org/wiki/specification|HTTP JSON-RPC] server, but <br />
[http://en.wikipedia.org/wiki/Basic_access_authentication|HTTP Basic access authentication] must be used when communicating with it, and, for security, by default, the server only accepts connections from other processes on the same machine. If your HTTP or JSON library requires you to specify which 'realm' is authenticated, use 'jsonrpc'.<br />
<br />
Bitcoin supports SSL (https) JSON-RPC connections beginning with version 0.3.14. See the [[Enabling SSL on original client daemon|rpcssl wiki page]] for setup instructions and a list of all bitcoin.conf configuration options.<br />
<br />
To access the server you should find a [http://json-rpc.org/wiki/implementations|suitable library] for your language.<br />
<br />
== Proper money handling ==<br />
<br />
See the [[Proper Money Handling (JSON-RPC)|proper money handling page]] for notes on avoiding rounding errors when handling bitcoin values.<br />
<br />
== Python ==<br />
<br />
Save the following file as jsonrpc.py.<br />
<br />
<source lang="python"><br />
import urllib<br />
import decimal<br />
import json<br />
<br />
class JSONRPCException(Exception):<br />
def __init__(self, rpcError):<br />
Exception.__init__(self)<br />
self.error = rpcError<br />
<br />
class ServiceProxy(object):<br />
def __init__(self, serviceURL, serviceName=None):<br />
self.__serviceURL = serviceURL<br />
self.__serviceName = serviceName<br />
<br />
def __getattr__(self, name):<br />
if self.__serviceName != None:<br />
name = "%s.%s" % (self.__serviceName, name)<br />
return ServiceProxy(self.__serviceURL, name)<br />
<br />
def __call__(self, *args):<br />
postdata = json.dumps({"method": self.__serviceName, 'params': args, 'id':'jsonrpc'})<br />
respdata = urllib.urlopen(self.__serviceURL, postdata).read()<br />
resp = json.loads(respdata, parse_float=decimal.Decimal)<br />
if resp['error'] != None:<br />
raise JSONRPCException(resp['error'])<br />
else:<br />
return resp['result'] <br />
</source><br />
<br />
Python-jsonrpc automatically generates Python methods corresponding to the functions above.<br />
<br />
<source lang="python"><br />
from jsonrpc import ServiceProxy<br />
<br />
access = ServiceProxy("http://user:password@127.0.0.1:8332")<br />
access.getinfo()<br />
access.listreceivedbyaddress(6)<br />
#access.sendtoaddress("11yEmxiMso2RsFVfBcCa616npBvGgxiBX", 10)<br />
</source><br />
<br />
== Ruby ==<br />
<br />
<source lang="ruby"><br />
=begin<br />
Make sure to do:<br />
gem install rest-client<br />
<br />
Usage:<br />
h = ServiceProxy.new('http://user:password@127.0.0.1:8332')<br />
puts h.getinfo.call<br />
puts h.getbalance.call '0'<br />
=end<br />
require 'json'<br />
require 'rest_client'<br />
<br />
class JSONRPCException < RuntimeError<br />
def initialize()<br />
super()<br />
end<br />
end<br />
<br />
class ServiceProxy<br />
def initialize(service_url, service_name=nil)<br />
@service_url = service_url<br />
@service_name = service_name<br />
end<br />
<br />
def method_missing(name, *args, &block)<br />
if @service_name != nil<br />
name = "%s.%s" % [@service_name, name]<br />
end<br />
return ServiceProxy.new(@service_url, name)<br />
end<br />
<br />
def respond_to?(sym)<br />
end<br />
<br />
def call(*args)<br />
postdata = {"method" => @service_name, "params" => args, "id" => "jsonrpc"}.to_json<br />
respdata = RestClient.post @service_url, postdata<br />
resp = JSON.parse respdata<br />
if resp["error"] != nil<br />
raise JSONRPCException.new, resp['error']<br />
end<br />
return resp['result']<br />
end<br />
end<br />
</source><br />
<br />
== PHP ==<br />
<br />
The [http://jsonrpcphp.org/ JSON-RPC PHP] library also makes it very easy to connect to Bitcoin. For example:<br />
<br />
<source lang="php"><br />
require_once 'jsonRPCClient.php';<br />
<br />
$bitcoin = new jsonRPCClient('http://user:password@127.0.0.1:8332/');<br />
<br />
echo "<pre>\n";<br />
print_r($bitcoin->getinfo()); echo "\n";<br />
echo "Received: ".$bitcoin->getreceivedbylabel("Your Address")."\n";<br />
echo "</pre>";<br />
</source><br />
<br />
=== Precision ===<br />
<br />
Because PHP has no option to JSON decode to accurate decimal class, you should internally use GMP. Treat each number like a large int with 8 decimal places (this can be trimmed for display).<br />
<br />
You will need to get a [https://github.com/genjix/bitcoin/tree/strrpc saner branch] and compile it. This treats every monetary value int64 8 decimal strings. So 1 BTC will be "100000000". Use PHP's GMP functions to manipulate these values accurately.<br />
<br />
For converting between internal GMP numbers and display/user input, you can use these functions:<br />
<source lang="php"><br />
# converts a user supplied number to our internal representation<br />
# 3.14 => "314000000"<br />
# accepts strings, floats and ints as input<br />
function numstr_to_internal($numstr)<br />
{<br />
return bcmul($numstr, pow(10, 8), 0);<br />
}<br />
# converts an internal number to an end user number for display as defined by precision<br />
# 314100000 => "3.14"<br />
# accepts GMP numbers, ints and strings as input<br />
function internal_to_numstr($num, $precision=2)<br />
{<br />
$repr = gmp_strval($num);<br />
$repr = bcdiv($repr, pow(10, 8), $precision);<br />
# now tidy output...<br />
# trim trailing 0s<br />
$repr = rtrim($repr, '0');<br />
# and a trailing . if it exists<br />
$repr = rtrim($repr, '.');<br />
return $repr;<br />
}<br />
<br />
$num_internal = numstr_to_internal("3.141");<br />
echo "<p>".$num_internal."</p>";<br />
$num_display = internal_to_numstr($num_internal);<br />
echo "<p>".$num_display."</p>";<br />
</source><br />
<br />
If you need to do a decimal division in GMP, then GMP only supports integer division + a remainder ([http://php.net/manual/en/function.gmp-div-qr.php gmp_div_qr]). The work-around for this, is to use the bcmath module:<br />
<source lang="php"><br />
$a = gmp_init("100");<br />
$b = gmp_init("3");<br />
echo "<p>".bcdiv(gmp_strval($a), gmp_strval($b), 3)."</p>";<br />
</source><br />
<br />
Note that bcdiv uses strings.<br />
<br />
See also: [http://php.net/manual/en/ref.gmp.php GMP] and [http://php.net/manual/en/ref.bc.php BC Math] manuals.<br />
<br />
== Java ==<br />
<br />
The easiest way to tell Java to use HTTP Basic authentication is to set a default Authenticator:<br />
<br />
<source lang="java"><br />
final String rpcuser ="...";<br />
final String rpcpassword ="...";<br />
<br />
Authenticator.setDefault(new Authenticator() {<br />
protected PasswordAuthentication getPasswordAuthentication() {<br />
return new PasswordAuthentication (rpcuser, rpcpassword.toCharArray());<br />
}<br />
});<br />
</source><br />
<br />
Once that is done, any JSON-RPC library for Java (or ordinary URL POSTs) may be used to communicate with the Bitcoin server.<br />
<br />
== Perl ==<br />
<br />
The JSON::RPC package from CPAN can be used to communicate with Bitcoin. You must set the client's credentials; for example:<br />
<br />
<source lang="perl"><br />
use JSON::RPC::Client;<br />
use Data::Dumper;<br />
<br />
my $client = new JSON::RPC::Client;<br />
<br />
$client->ua->credentials(<br />
'localhost:8332', 'jsonrpc', 'user' => 'password' # REPLACE WITH YOUR bitcoin.conf rpcuser/rpcpassword<br />
);<br />
<br />
my $uri = 'http://localhost:8332/';<br />
my $obj = {<br />
method => 'getinfo',<br />
params => [],<br />
};<br />
<br />
my $res = $client->call( $uri, $obj );<br />
<br />
if ($res){<br />
if ($res->is_error) { print "Error : ", $res->error_message; }<br />
else { print Dumper($res->result); }<br />
} else {<br />
print $client->status_line;<br />
}<br />
</source><br />
<br />
== .NET (C#) ==<br />
The communication with rpc service can be achieved using the standard httprequest/response objects.<br />
A library for serialising and deserialising Json will make your life a lot easier:<br />
<br />
* JayRock for .NET 4.0<br />
* Json.Net for .NET 2.0 and above <br />
<br />
The following example uses Json.Net:<br />
<br />
<source lang="csharp"><br />
HttpWebRequest webRequest = (HttpWebRequest)WebRequest.Create("http://localhost.:8332");<br />
webRequest.Credentials = new NetworkCredential("user", "pwd");<br />
/// important, otherwise the service can't desirialse your request properly<br />
webRequest.ContentType = "application/json-rpc";<br />
webRequest.Method = "POST";<br />
<br />
JObject joe = new JObject();<br />
joe.Add(new JProperty("jsonrpc", "1.0"));<br />
joe.Add(new JProperty("id", "1"));<br />
joe.Add(new JProperty("method", Method));<br />
// params is a collection values which the method requires..<br />
if (Params.Keys.Count == 0)<br />
{<br />
joe.Add(new JProperty("params", new JArray()));<br />
}<br />
else<br />
{<br />
JArray props = new JArray();<br />
// add the props in the reverse order!<br />
for (int i = Params.Keys.Count - 1; i >= 0; i--)<br />
{<br />
.... // add the params<br />
}<br />
joe.Add(new JProperty("params", props));<br />
}<br />
<br />
// serialize json for the request<br />
string s = JsonConvert.SerializeObject(joe);<br />
byte[] byteArray = Encoding.UTF8.GetBytes(s);<br />
webRequest.ContentLength = byteArray.Length;<br />
Stream dataStream = webRequest.GetRequestStream();<br />
dataStream.Write(byteArray, 0, byteArray.Length);<br />
dataStream.Close();<br />
<br />
<br />
WebResponse webResponse = webRequest.GetResponse();<br />
<br />
... // deserialze the response<br />
</source><br />
<br />
== Command line (cURL) ==<br />
<br />
You can also send commands and see results using [http://curl.haxx.se/ cURL] or some other command-line HTTP-fetching utility; for example:<br />
<br />
<source lang="bash"><br />
curl --user user --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getinfo", "params": [] }' <br />
-H 'content-type: text/plain;' http://127.0.0.1:8332/<br />
</source><br />
<br />
You will be prompted for your rpcpassword, and then will see something like:<br />
<br />
<source lang="javascript"><br />
{"result":{"balance":0.000000000000000,"blocks":59952,"connections":48,"proxy":"","generate":false,<br />
"genproclimit":-1,"difficulty":16.61907875185736,"error":null,"id":"curltest"}<br />
</source><br />
<br />
== See Also==<br />
<br />
* [[Original_Bitcoin_client/API_Calls_list|API calls list]]<br />
* [[Running Bitcoin]]<br />
* [[Lazy_API]]<br />
<br />
[[Category:Articles using content from the old wiki]]<br />
[[Category:Technical]]<br />
[[Category:Developer]]</div>Dacoinminsterhttps://en.bitcoin.it/w/index.php?title=Lazy_API&diff=6514Lazy API2011-04-01T16:27:02Z<p>Dacoinminster: </p>
<hr />
<div>For the incredibly lazy and/or incompetent web developer, I present 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 (me) wants to use bitcoins without dealing with installing bitcoin on a server, installing a shopping card 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<br />
# Check blockexplorer to see if they sent the right amount (i.e. http://blockexplorer.com/address/19hMEAaRMbEhfSkeU4GT8mgSuyR4t4M6TH)<br />
# Wait for more blocks (confirmations) if paranoid<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 if one of the wallet services someday lets you get a new address via API call, but this will work for now.<br />
<br />
'''Bad idea:'''<br />
<br />
Selling bars of gold this way (owner of blockexplorer.com could rip you off)<br />
<br />
'''Good(?) idea:'''<br />
<br />
Selling naked pictures of your grandma this way (owner of blockexplorer.com won't bother)<br />
<br />
[[Category:Developer]]</div>Dacoinminsterhttps://en.bitcoin.it/w/index.php?title=Lazy_API&diff=6513Lazy API2011-04-01T16:26:25Z<p>Dacoinminster: </p>
<hr />
<div>For the incredibly lazy and/or incompetent web developer, I present 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 (me) wants to use bitcoins without dealing with installing bitcoin on a server, installing a shopping card 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<br />
# Check blockexplorer to see if they sent the right amount (i.e. http://blockexplorer.com/address/19hMEAaRMbEhfSkeU4GT8mgSuyR4t4M6TH)<br />
# Wait for more blocks (confirmations) if paranoid<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 if one of the wallet services someday lets you get a new address via API call, but this will work for now.<br />
<br />
Bad idea: <br />
<br />
Selling bars of gold this way (owner of blockexplorer.com could rip you off)<br />
<br />
Good(?) idea: <br />
<br />
Selling naked pictures of your grandma this way (owner of blockexplorer.com won't bother)<br />
<br />
[[Category:Developer]]</div>Dacoinminsterhttps://en.bitcoin.it/w/index.php?title=Lazy_API&diff=6512Lazy API2011-04-01T16:21:38Z<p>Dacoinminster: </p>
<hr />
<div>For the incredibly lazy and/or incompetent web developer, I present 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 (me) wants to use bitcoins without dealing with installing bitcoin on a server, installing a shopping card 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<br />
# Check blockexplorer to see if they sent the right amount (i.e. http://blockexplorer.com/address/19hMEAaRMbEhfSkeU4GT8mgSuyR4t4M6TH)<br />
# Wait for more blocks (confirmations) if paranoid<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 if one of the wallet services someday lets you get a new address via API call, but this will work for now.<br />
<br />
Bad idea: Selling bars of gold this way (owner of blockexplorer.com could rip you off)<br />
<br />
Good(?) idea: Selling naked pictures of your grandma this way (owner of blockexplorer.com won't bother)</div>Dacoinminsterhttps://en.bitcoin.it/w/index.php?title=Lazy_API&diff=6511Lazy API2011-04-01T16:19:29Z<p>Dacoinminster: </p>
<hr />
<div>For the incredibly lazy and/or incompetent web developer, I present 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:''' Lazy web designer (me) wants to use bitcoins without dealing with installing bitcoin on a server, installing a shopping card 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<br />
# Check blockexplorer to see if they sent the right amount (i.e. http://blockexplorer.com/address/19hMEAaRMbEhfSkeU4GT8mgSuyR4t4M6TH)<br />
# Wait for more blocks (confirmations) if paranoid<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 if one of the wallet services someday lets you get a new address via API call, but this will work for now.<br />
<br />
Bad idea: Selling bars of gold this way (owner of blockexplorer.com could rip you off)<br />
<br />
Good(?) idea: Selling naked pictures of your grandma this way (owner of blockexplorer.com won't bother)</div>Dacoinminsterhttps://en.bitcoin.it/w/index.php?title=Lazy_API&diff=6510Lazy API2011-04-01T16:18:52Z<p>Dacoinminster: </p>
<hr />
<div>For the incredibly lazy and/or incompetent web developer, I present 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:''' Lazy web designer (me) wants to use bitcoins without dealing with installing bitcoin on a server, installing a shopping card interface, or using ugly merchant services with callbacks.<br />
<br />
'''Solution for sending bitcoins:'''<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<br />
# Check blockexplorer to see if they sent the right amount (i.e. http://blockexplorer.com/address/19hMEAaRMbEhfSkeU4GT8mgSuyR4t4M6TH)<br />
# Wait for more blocks (confirmations) if paranoid<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 if one of the wallet services someday lets you get a new address via API call, but this will work for now.<br />
<br />
Bad idea: Selling bars of gold this way (owner of blockexplorer.com could rip you off)<br />
Good(?) idea: Selling naked pictures of your grandma this way (owner of blockexplorer.com won't bother)</div>Dacoinminsterhttps://en.bitcoin.it/w/index.php?title=Lazy_API&diff=6509Lazy API2011-04-01T16:18:02Z<p>Dacoinminster: </p>
<hr />
<div>For the incredibly lazy and/or incompetent web developer, I present 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:''' Lazy web designer (me) wants to use bitcoins without dealing with installing bitcoin on a server, installing a shopping card interface, or using ugly merchant services with callbacks.<br />
<br />
'''Solution for sending bitcoins:'''<br />
Use the [https://mtgox.com/support/tradeAPI MtGox API]<br />
<br />
'''Solution for receiving bitcoins:'''<br />
# 1) Input a list of bitcoin receiving addresses to your database<br />
2) Give a bitcoin address to a potential customer<br />
3) Have the customer tell you when they have sent the coins and have at least 1 confirmation<br />
4) Check blockexplorer to see if they sent the right amount (i.e. http://blockexplorer.com/address/19hMEAaRMbEhfSkeU4GT8mgSuyR4t4M6TH)<br />
5) Wait for more blocks (confirmations) if paranoid<br />
6) Give them what they paid for<br />
7) 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 if one of the wallet services someday lets you get a new address via API call, but this will work for now.<br />
<br />
Bad idea: Selling bars of gold this way (owner of blockexplorer.com could rip you off)<br />
Good(?) idea: Selling naked pictures of your grandma this way (owner of blockexplorer.com won't bother)</div>Dacoinminsterhttps://en.bitcoin.it/w/index.php?title=Lazy_API&diff=6508Lazy API2011-04-01T16:13:58Z<p>Dacoinminster: Created page with "For the incredibly lazy and/or incompetent web developer, I present the lazy man's bitcoin API (copied from [http://www.bitcoin.org/smf/index.php?topic=4324.msg77187#msg77187 a f..."</p>
<hr />
<div>For the incredibly lazy and/or incompetent web developer, I present 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: Lazy web designer (me) wants to use bitcoins without dealing with installing bitcoin on a server, installing a shopping card interface, or using ugly merchant services with callbacks.<br />
<br />
Solution for sending bitcoins:<br />
Use the MtGox API (https://mtgox.com/support/tradeAPI)<br />
<br />
Solution for receiving bitcoins:<br />
1) Input a list of bitcoin receiving addresses to your database<br />
2) Give a bitcoin address to a potential customer<br />
3) Have the customer tell you when they have sent the coins and have at least 1 confirmation<br />
4) Check blockexplorer to see if they sent the right amount (i.e. http://blockexplorer.com/address/19hMEAaRMbEhfSkeU4GT8mgSuyR4t4M6TH)<br />
5) Wait for more blocks (confirmations) if paranoid<br />
6) Give them what they paid for<br />
7) 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 if one of the wallet services someday lets you get a new address via API call, but this will work for now.<br />
<br />
Bad idea: Selling bars of gold this way (owner of blockexplorer.com could rip you off)<br />
Good(?) idea: Selling naked pictures of your grandma this way (owner of blockexplorer.com won't bother)</div>Dacoinminster