https://tests.bitcoin.it/w/api.php?action=feedcontributions&user=Luther&feedformat=atomBitcoin Wiki - User contributions [en]2024-03-29T10:22:11ZUser contributionsMediaWiki 1.30.0https://tests.bitcoin.it/w/index.php?title=CoinPal&diff=7541CoinPal2011-04-22T14:49:48Z<p>Luther: /* Weekly Limits */ Update limit table</p>
<hr />
<div>'''CoinPal''' is an exchange that accepts [[PayPal]] for relatively small order sizes and a weekly limit on purchases. The site was first publicly available on December 31, 2010<ref>[http://www.bitcoin.org/smf/index.php?topic=2555.0 CoinPal beta - Buying bitcoins with PayPal]</ref>. On January 14th, 2010 CoinPal introduced an API that allows merchants and others seeking payment to use the service to accept micro-payments<ref>[http://www.bitcoin.org/smf/index.php?topic=2555.msg38148#msg38148 Re: CoinPal beta - Buying bitcoins with PayPal]</ref>. The operator of the site also operates [[CoinCard]] for [[selling bitcoins]].<br />
<br />
==Weekly Limits==<br />
There is a limit on the number of bitcoins each customer can buy each week. This limit depends on the amount of time that has passed since the customer's first order.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Minimum days since customer's first order<br />
! Weekly limit<br />
|-<br />
| 0<br />
| 20<br />
|-<br />
| 3<br />
| 40<br />
|-<br />
| 7<br />
| 60<br />
|-<br />
| 14<br />
| 100<br />
|-<br />
| 45<br />
| 160<br />
|}<br />
<br />
Those trading on [[Bitcoin-otc|Bitcoin OTC]] can increase their weekly purchase limits by connecting CoinPal to the [[Bitcoin-otc|OTC web of trust]]<ref>[http://coinpal.ndrix.com/user/gpg Authenticate with a PGP Key]</ref>.<br />
<br />
==See Also==<br />
<br />
* [[Buying bitcoins]]<br />
* [[Selling bitcoins]]<br />
<br />
==External Links==<br />
<br />
* [http://coinpal.ndrix.com/bw CoinPal.ndrix.com] web site<br />
<br />
==References==<br />
<references /><br />
<br />
[[Category:Exchanges]]</div>Lutherhttps://tests.bitcoin.it/w/index.php?title=Help:FAQ&diff=6875Help:FAQ2011-04-07T03:03:06Z<p>Luther: /* How does the halving work when the number gets really small? */ Elaborate the halving calculation</p>
<hr />
<div>Here you will find answers to the most commonly asked questions.<br />
<br />
== General ==<br />
=== What are bitcoins? ===<br />
Bitcoins are the unit of currency of the Bitcoin system. A commonly used shorthand for this is “BTC” to refer to a price or amount (eg: “100 BTC”)<br />
A Bitcoin isn't actually a 'thing' you can point at. It is just a number associated with a [[Address|Bitcoin Address]]. See also an [[Introduction|easy intro]] to bitcoin.<br />
<br />
=== How are new Bitcoins created? ===<br />
<br />
[[File:total_bitcoins_over_time_graph.png|thumb|Number of bitcoins over time, assuming a perfect 10-minute interval.]]<br />
New coins are generated by a network node each time it finds the solution to a certain mathematical problem (i.e. creates a new [[block]]), which is difficult to perform and can demonstrate a [[proof of work]]. The reward for solving a block is [[controlled inflation|automatically adjusted]] so that in the first 4 years of the Bitcoin network, 10,500,000 BTC will be created. The amount is halved each 4 years, so it will be 5,250,000 over years 4-8, 2,625,000 over years 8-12 and so on. Thus the total number of coins will approach 21,000,000 BTC over time.<br />
<br />
In addition, built into the network is a system that attempts to allocate new coins in blocks about every 10 minutes, on average, somewhere on the network. As the number of people who attempt to generate these new coins changes, the difficulty of creating new coins changes. This happens in a manner that is agreed upon by the network as a whole, based upon the time taken to generate the previous 2016 blocks. The difficulty is therefore related to the average computing resources devoted to generate these new coins over the time it took to create these previous blocks. The likelihood of somebody "discovering" one of these blocks is based on the computer they are using compared to all of the computers also generating blocks on the network.<br />
<br />
=== What's the current total amount of Bitcoins in existence? ===<br />
<br />
[http://blockexplorer.com/q/totalbc Current count]<br />
<br />
The number of blocks times the coin value of a block is the number of coins in existence. The coin value of a block is 50 BTC for each of the first 210,000 blocks, 25 BTC for the next 210,000 blocks, then 12.5 BTC, 6.25 BTC and so on.<br />
<br />
=== How divisible are Bitcoins? ===<br />
<br />
Technically, a Bitcoin can be divided down to 8 decimals using existing data structures, so 0.00000001 BTC is the smallest amount currently possible. Discussions about and ideas for ways to provide for even smaller quantities of Bitcoins may be created in the future if the need for them ever arises. For convenience, the program currently accepts only 2 decimal places as quantities smaller than 0.01 BTC are considered of trivial value and are usually used only to attack the network.<br />
<br />
=== How does the halving work when the number gets really small? ===<br />
<br />
The reward will go from 0.00000001 BTC to 0. Then no more coins will likely be created. <br />
<br />
The calculation is done as a right bitwise shift of a 64-bit signed integer, which means it is divided by 2 and rounded down. The integer is equal to the value in BTC * 100,000,000. This is how all Bitcoin balances/values are stored internally.<br />
<br />
Keep in mind that using current rules this will take nearly 100 years before it becomes an issue and Bitcoins may change considerably before that happens.<br />
<br />
=== How long will it take to generate all the coins? ===<br />
<br />
The last block that will generate coins will be block #6,929,999. This should be generated around year 2140. Then the total number of coins in circulation will remain static at 20,999,999.9769 BTC.<br />
<br />
Even if the allowed precision is expanded from the current 8 decimals, the total BTC in circulation will always be slightly below 21 million (assuming everything else stays the same). For example, with 16 decimals of precision, the end total would be 20999999.999999999496 BTC.<br />
<br />
=== If no more coins are going to be generated, will more blocks be created? ===<br />
<br />
Absolutely! Even before the creation of coins ends, the use of [[transaction fee|transaction fees]] will likely make creating new blocks more valuable from the fees than the new coins being created. When coin generation ends, what will sustain the ability to use bitcoins will be these fees entirely. There will be blocks generated after block #6,929,999, assuming that people are still using Bitcoins at that time.<br />
<br />
==Economy==<br />
=== Where does the value of Bitcoin stem from? What backs up Bitcoin? ===<br />
Bitcoins have value because they are accepted as payment by many. See the [[Trade|list of Bitcoin-accepting sites]].<br />
<br />
When we say that a currency is backed up by gold, we mean that there's a promise in place that you can exchange the currency for gold. In a sense, you could say that Bitcoin is "backed up" by the price tags of merchants – a price tag is a promise to exchange goods for a specified amount of currency.<br />
<br />
It's a common misconception that Bitcoins gain their value from the cost of electricity required to generate them. Cost doesn't equal value – hiring 1,000 men to shovel a big hole in the ground may be costly, but not valuable. Also, even though scarcity is a critical requirement for a useful currency, it alone doesn't make anything valuable. For example, your fingerprints are scarce, but that doesn't mean they have any exchange value.<br />
<br />
=== What if someone bought up all the existing Bitcoins? ===<br />
What if somebody bought up all the gold in the world? Well, by attempting to buy it all, the buyer would just drive the prices up until he runs out of money.<br />
<br />
=== Bitcoin's monetary policy causes a deflationary spiral ===<br />
See the article [[Deflationary spiral]].<br />
<br />
==Networking==<br />
=== Do I need to configure my firewall to run bitcoin? ===<br />
<br />
Bitcoin will connect to other nodes, usually on tcp port 8333. You will need to allow outgoing TCP connections to port 8333 if you want to allow your bitcoin client to connect to many nodes. Bitcoin will also try to connect to IRC (tcp port 6667) to meet other nodes to connect to.<br />
<br />
If you want to restrict your firewall rules to a few ips and/or don't want to allow IRC connection, you can find stable nodes in the [[Fallback Nodes|fallback nodes list]]. If your provider blocks the common IRC ports, note that lfnet also listens on port 7777. Connecting to this alternate port currently requires either recompiling Bitcoin, or changing routing rules. For example, on Linux you can evade a port 6667 block by doing something like this:<br />
<br />
echo 173.246.103.92 irc.lfnet.org >> /etc/hosts<br />
iptables -t nat -A OUTPUT -p tcp --dest 173.246.103.92 --dport 6667 -j DNAT --to-destination :7777 -m comment --comment "bitcoind irc connection"<br />
<br />
<br />
=== How does the peer finding mechanism work? ===<br />
Bitcoin finds peers primarily by connecting to an IRC server (channel #bitcoin on irc.lfnet.org). If a connection to the IRC server cannot be established (like when connecting through TOR), an in-built node list will be used and the nodes will be queried for more node addresses.<br />
<br />
==Help==<br />
===I'd like to learn more. Where can I get help?===<br />
<br />
* Read the [[Introduction|introduction to bitcoin]] <br />
* See the videos, podcasts, and blog posts from the [[Press]]<br />
* Read and post on the [[Bitcoin:Community_portal#Bitcoin_Community_Forums|forums]]<br />
* Chat on one of the [[Bitcoin:Community_portal#IRC_Chat|Bitcoin IRC]] channels<br />
* Listen to [http://omegataupodcast.net/2011/03/59-bitcoin-a-digital-decentralized-currency/ this podcast], which goes into the details of how bitcoin works<br />
<br />
==See Also==<br />
<br />
* [[Man page]]<br />
<br />
[[zh-cn:FAQ]]<br />
[[fr:FAQ]]<br />
{{fromold|bitcoins}}<br />
<br />
[[Category:Technical]]<br />
[[Category:Vocabulary]]</div>Lutherhttps://tests.bitcoin.it/w/index.php?title=Secure_Trading&diff=6704Secure Trading2011-04-04T04:58:40Z<p>Luther: /* Best Practices with trading */ Grammar/spelling typos</p>
<hr />
<div>''Secure Trading Online''<br />
<br />
This topic is a guide in how to set up your online identity and best practices for trading with others in the Bitcoin community.<br />
<br />
==Introduction==<br />
Within the Bitcoin community, many are very careful with their security and identity. This is because of two main reasons:<br />
# There is no violent body to cover your back for you. Or more simply there is no courts to seek assistance from if your transaction sours.<br />
# One’s reputation is the most important thing that any user has; traders will take very little risk with new users who have not proven themselves. (as they could just be last week’s scammer with a new identity)<br />
The bitcoin community uses a few tools to help protect their privacy, and thus identity. The first and most important is a [[Securing Your Computer|Secure Computer]].<br /><br />
<br />
'''Before proceeding please make sure you have completed the [[Securing Your Computer]] guide, this guide assumes that your computer is secure both physically and in software.'''<br />
<br />
==Creating a secure Identity==<br />
The first step is to create a cryptographically secure public-private key-pair. This will be used as the basis of keeping both your wallet secure (see [[Securing your wallet]]), and your identity secure.<br />
<br />
===Creating your first PGP key-pair===<br />
A PGP key-pair does two very important functions.<br />
# Sign information with an unforgeable signature<br />
# Decrypt things that other people encrypt for you<br />
<br />
This allows you to both conduct business privately (encryption), and give out promises that you cannot deny making (signature).<br />
<br />
==== Microsoft Windows:====<br />
* Install GPG4Win: http://www.gpg4win.org/<br /><br />
<br />
This contains all the key management and generation tools for Microsoft Windows.<br />
<br />
====All:====<br />
# Install Thunderbird: https://www.mozillamessaging.com/en-GB/ <br />
# Setup your email account with Thunderbird.<br />
# Install the Enigmail plugin for Thunderbird: https://addons.mozilla.org/en-US/thunderbird/addon/enigmail/<br /><br />
<br />
Upon loading Enigmail, Thunderbird will ask you to make a new ‘identity,’ follow this wizard and you will have created your identity.<br /><br />
You should backup your private key in a secure place. Secondary, you should create a revocation certificate and store that in a different secure place (maybe print it out and store it in your fire safe).<br />
<br />
===Register with [#bitcoin-otc]===<br />
Follow the guide here: http://wiki.bitcoin-otc.com/wiki/Using_bitcoin-otc<br />
<br />
===Register the same username at the popular places:===<br />
* [[Bitcoin Forum]]<br />
* [[Bitcoin.it_Wiki|Bitcoin Wiki]]<br />
* [[Bitcoin:Community_portal#IRC_Chat|Freenode IRC]]<br />
Use a strong and different password for each of these places, keeping your passwords in a secure place. This will allow other people in the community to track you across the different Bitcoin related sites. Also making identity theft online more challenging.<br />
<br />
==Best Practices with trading==<br />
===Use Bitcoin-OTC===<br />
* Always require the user to become registered with #bitcoin-otc.<br />
* Require a signed message from the fingerprint quoted at: http://bitcoin-otc.com/viewgpg.php<br />
<br />
===Make sure both parties agree to the terms of the trade with signed messages.===<br />
* Get a PGP signed quote, and check the signature.<br />
* Send a PGP signed receipt.<br />
This allows either party to go public if the trade has become sour and stops your trading partner from claiming the details of the agreement were somehow different.<br /><br />
<br />
Search the Bitcoin Forum for the username of the person that you are trading with. Check if the user has provided constructive and useful advice to other parties. And, most importantly, check for any claims that the user has scammed.<br />
<br />
===Use an escrow===<br />
Trading might benefit from an escrow such that bitcoins are disbursed only after contract terms have been met.<br /><br />
<br />
A popular online escrow is [[ClearCoin]].<br />
<br />
Found in Bitcoin's community are trusted individuals willing to act as independent, third-party escrow brokers.</div>Lutherhttps://tests.bitcoin.it/w/index.php?title=CoinPal&diff=6616CoinPal2011-04-02T19:01:19Z<p>Luther: Moved weekly limits to a table in their own section</p>
<hr />
<div>'''CoinPal''' is an exchange that accepts [[PayPal]] for relatively small order sizes and a weekly limit on purchases. The site was first publicly available on December 31, 2010<ref>[http://www.bitcoin.org/smf/index.php?topic=2555.0 CoinPal beta - Buying bitcoins with PayPal]</ref>. On January 14th, 2010 CoinPal introduced an API that allows merchants and others seeking payment to use the service to accept micro-payments<ref>[http://www.bitcoin.org/smf/index.php?topic=2555.msg38148#msg38148 Re: CoinPal beta - Buying bitcoins with PayPal]</ref>. The operator of the site also operates [[CoinCard]] for [[selling bitcoins]].<br />
<br />
==Weekly Limits==<br />
There is a limit on the number of bitcoins each customer can buy each week. This limit depends on the amount of time that has passed since the customer's first order.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Minimum days since customer's first order<br />
! Weekly limit<br />
|-<br />
| 0<br />
| 20<br />
|-<br />
| 7<br />
| 40<br />
|-<br />
| 14<br />
| 60<br />
|-<br />
| 45<br />
| 80<br />
|}<br />
<br />
Those trading on [[Bitcoin-otc|Bitcoin OTC]] can increase their weekly purchase limits by connecting CoinPal to the [[Bitcoin-otc|OTC web of trust]]<ref>[http://coinpal.ndrix.com/user/gpg Authenticate with a PGP Key]</ref>.<br />
<br />
==See Also==<br />
<br />
* [[Buying bitcoins]]<br />
* [[Selling bitcoins]]<br />
<br />
==External Links==<br />
<br />
* [http://coinpal.ndrix.com/bw CoinPal.ndrix.com] web site<br />
<br />
==References==<br />
<references /><br />
<br />
[[Category:Exchanges]]</div>Lutherhttps://tests.bitcoin.it/w/index.php?title=User:Luther&diff=6118User:Luther2011-03-26T04:24:53Z<p>Luther: /* Donations */</p>
<hr />
<div>=About Me=<br />
I am a member of [http://www.oto.org Ordo Templi Orientis] and a user of [http://gnu.org free software] and the [http://lamar.colostate.edu/~hillger/ metric system]. I support Bitcoin because I believe it to be technically superior to government currencies and I hope that one day everyone will be able to migrate to Bitcoin as the basis for all money.<br />
<br />
=Donations=<br />
Direct donations: 18zBGmCZCmruA8ndVjVb1uv3oi4pczFvsf<br />
<br />
Contributors Award participant: 1PwAFcXskEDpYXg2HFonWZ8zeBPnynGQqW</div>Lutherhttps://tests.bitcoin.it/w/index.php?title=Changelog&diff=5927Changelog2011-03-23T23:08:04Z<p>Luther: Added changelogs for 0.3.19 to 0.3.20.2</p>
<hr />
<div>{{stub}}<br />
<br />
This page aggregates the changelogs that have been posted on the forum for the Bitcoin releases. <br />
<br />
=Changelogs=<br />
<br />
==0.3.20.2<ref>[http://www.bitcoin.org/smf/index.php?topic=4167.0 0.3.20.2 release announcement]</ref>==<br />
The maxsendbuffer bug (0.3.20.1 clients not being able to download the block chain from other 0.3.20.1 clients) was only going to get<br />
worse as people upgraded, so I cherry-picked the bug fix and created a minor release yesterday.<br />
<br />
The Amazon Machine Images I used to do the builds are available:<br />
<br />
ami-38a05251 Bitcoin-v0.3.20.2 Mingw (Windows; Administrator password 'bitcoin development')<br />
ami-30a05259 Bitcoin_0.3.20.2 Linux32<br />
ami-8abc4ee3 Bitcoin_0.3.20.2 Linux64<br />
<br />
(mac build will be done soon)<br />
<br />
If you have already downloaded version 0.3.20.1, please either add this to your bitcoin.conf file:<br />
<br />
maxsendbuffer=10000<br />
maxreceivebuffer=10000<br />
<br />
... or download the new version.<br />
<br />
==0.3.20.1==<br />
(No known forum post.)<br />
<br />
==0.3.20<ref>[http://www.bitcoin.org/smf/index.php?topic=2953.0 0.3.20 release announcement]</ref>==<br />
Please checkout the git integration branch from:<br />
<br />
https://github.com/bitcoin/bitcoin<br />
<br />
... and help test. The new features that need testing are:<br />
<br />
* -nolisten : https://github.com/bitcoin/bitcoin/pull/11<br />
* -rescan : scan block chain for missing wallet transactions<br />
* -printtoconsole : https://github.com/bitcoin/bitcoin/pull/37<br />
* RPC gettransaction details : https://github.com/bitcoin/bitcoin/pull/24<br />
* listtransactions new features : https://github.com/bitcoin/bitcoin/pull/10<br />
<br />
Bug fixes that also need testing:<br />
<br />
* -maxconnections= : https://github.com/bitcoin/bitcoin/pull/42<br />
* RPC listaccounts minconf : https://github.com/bitcoin/bitcoin/pull/27<br />
* RPC move, add time to output : https://github.com/bitcoin/bitcoin/pull/21<br />
* ...and several improvements to --help output.<br />
<br />
This needs more testing on Windows! Please drop me a quick private message, email, or IRC message if you are able to do some testing. If you find bugs, please open an issue at:<br />
<br />
https://github.com/bitcoin/bitcoin/issues<br />
<br />
==0.3.19<ref>[http://www.bitcoin.org/smf/index.php?topic=2228.0 0.3.19 release announcement]</ref>==<br />
There's more work to do on DoS, but I'm doing a quick build of what I have so far in case it's needed, before venturing into more complex ideas. The build for this is version 0.3.19.<br />
<br />
- Added some DoS controls<br />
As Gavin and I have said clearly before, the software is not at all resistant to DoS attack. This is one improvement, but there are still more ways to attack than I can count. <br />
<br />
I'm leaving the -limitfreerelay part as a switch for now and it's there if you need it.<br />
<br />
- Removed "safe mode" alerts<br />
"safe mode" alerts was a temporary measure after the 0.3.9 overflow bug. We can say all we want that users can just run with "-disablesafemode", but it's better just not to have it for the sake of appearances. It was never intended as a long term feature. Safe mode can still be triggered by seeing a longer (greater total PoW) invalid block chain.<br />
<br />
<br />
==0.3.18<ref>[http://www.bitcoin.org/smf/index.php?topic=2162.0 0.3.18 release announcement]</ref>==<br />
<br />
Changes:<br />
* Fixed a wallet.dat compatibility problem if you downgraded from 0.3.17 and then upgraded again<br />
* IsStandard() check to only include known transaction types in blocks<br />
* Jgarzik's optimisation to speed up the initial block download a little<br />
<br />
The main addition in this release is the Accounts-Based JSON-RPC commands that Gavin's been working on (more details at http://www.bitcoin.org/smf/index.php?topic=1886.0). <br />
* getaccountaddress<br />
* sendfrom<br />
* move<br />
* getbalance<br />
* listtransactions<br />
<br />
==0.3.17<ref>[http://www.bitcoin.org/smf/index.php?topic=1946.0 0.3.17 release announcement]</ref>==<br />
<br />
Version 0.3.17 is now available.<br />
<br />
Changes:<br />
* new getwork, thanks m0mchil<br />
* added transaction fee setting in UI options menu<br />
* free transaction limits<br />
* sendtoaddress returns transaction id instead of "sent"<br />
* getaccountaddress <account><br />
<br />
The UI transaction fee setting was easy since it was still there from 0.1.5 and all I had to do was re-enable it.<br />
<br />
The accounts-based commands: move, sendfrom and getbalance <account> will be in the next release. We still have some more changes to make first.<br />
<br />
==0.3.16==<br />
<br />
Never released.<br />
<br />
==0.3.15<ref>[http://www.bitcoin.org/smf/index.php?topic=1780.0 0.3.15 release announcement]</ref>==<br />
<br />
* paytxfee switch is now per KB, so it adds the correct fee for large transactions<br />
* sending avoids using coins with less than 6 confirmations if it can<br />
* BitcoinMiner processes transactions in priority order based on age of dependencies<br />
* make sure generation doesn't start before block 74000 downloaded<br />
* bugfixes by Dean Gores<br />
* testnet, keypoololdest and paytxfee added to getinfo<br />
<br />
==0.3.14<ref>[http://www.bitcoin.org/smf/index.php?topic=1528.0 0.3.14 release announcement]</ref>==<br />
<br />
Version 0.3.14 is now available<br />
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.14/<br />
<br />
Changes:<br />
* Key pool feature for safer wallet backup<br />
Gavin Andresen:<br />
* TEST network mode with switch -testnet<br />
* Option to use SSL for JSON-RPC connections on unix/osx<br />
* validateaddress RPC command<br />
eurekafag:<br />
* Russian translation<br />
<br />
==0.3.13<ref>[http://www.bitcoin.org/smf/index.php?topic=1327.0 0.3.13 release announcement]</ref>==<br />
<br />
Version 0.3.13 is now available. You should upgrade to prevent potential problems with 0/unconfirmed transactions. Note: 0.3.13 prevents problems if you haven't already spent a 0/unconfirmed transaction, but if that already happened, you need 0.3.13.2.<br />
<br />
Changes:<br />
* Don't count or spend payments until they have 1 confirmation.<br />
* Internal version number from 312 to 31300.<br />
* Only accept transactions sent by IP address if -allowreceivebyip is specified.<br />
* Dropped DB_PRIVATE Berkeley DB flag.<br />
* Fix problem sending the last cent with sub-cent fractional change.<br />
* Auto-detect whether to use 128-bit 4-way SSE2 on Linux.<br />
Gavin Andresen:<br />
* Option -rpcallowip= to accept json-rpc connections from another machine.<br />
* Clean shutdown on SIGTERM on Linux.<br />
<br />
Download:<br />
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.13/<br />
<br />
(Thanks Laszlo for the Mac OSX build!)<br />
<br />
Note:<br />
The SSE2 auto-detect in the Linux 64-bit version doesn't work with AMD in 64-bit mode. Please try this instead and let me know if it gets it right:<br />
http://www.bitcoin.org/download/bitcoin-0.3.13.1-specialbuild-linux64.tar.gz<br />
<br />
You can still control the SSE2 use manually with -4way and -4way=0.<br />
<br />
Version 0.3.13.2 (SVN rev 161) has improvements for the case where you already had 0/unconfirmed transactions that you might have already spent. Here's a Windows build of it:<br />
http://www.bitcoin.org/download/bitcoin-0.3.13.2-win32-setup.exe<br />
<br />
==0.3.12<ref>[http://www.bitcoin.org/smf/index.php?topic=999.0 0.3.12 release announcement]</ref>==<br />
<br />
Version 0.3.12 is now available.<br />
<br />
Features:<br />
* json-rpc errors return a more standard error object. (thanks to Gavin Andresen)<br />
* json-rpc command line returns exit codes.<br />
* json-rpc "backupwallet" command.<br />
* Recovers and continues if an exception is caused by a message you received. Other nodes shouldn't be able to cause an exception, and it hasn't happened before, but if a way is found to cause an exception, this would keep it from being used to stop network nodes.<br />
<br />
If you have json-rpc code that checks the contents of the error string, you need to change it to expect error objects of the form {"code":<number>,"message":<string>}, which is the standard. See this thread:<br />
http://www.bitcoin.org/smf/index.php?topic=969.0<br />
<br />
Download:<br />
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.12/<br />
<br />
=References=<br />
<references/></div>Lutherhttps://tests.bitcoin.it/w/index.php?title=PayPal&diff=5907PayPal2011-03-23T21:49:55Z<p>Luther: /* External Links */ Link to Wikipedia</p>
<hr />
<div>'''PayPal''' is an e-commerce business allowing payments and money transfers to be made through the Internet.<br />
A PayPal account can be funded with electronic debits from a bank account, from a payment card or by receiving a money transfer from another PayPal member. Funds in a PayPal account can be withdrawn to a bank account or by sending a money transfer to another PayPal member.<br />
<br />
==Fees==<br />
The fee for transferring money to another PayPal member can vary based on options. The typical transaction charge for PayPal is $0.30 per transaction plus 2.9% of the amount transferred. The transaction charge is deducted from the payment amount. A "personal, payments owed" transaction to another PayPal account where the recipient's account is not a business account will incur no transfer fee. International payments will incur an additional currency exchange fee of 1%, in many instances.<br />
<br />
PayPal operates in 190 markets worldwide.<br />
<br />
==See Also==<br />
<br />
* [[Buying bitcoins]]<br />
* [[Selling bitcoins]]<br />
* [[Dwolla]]<br />
<br />
==External Links==<br />
* [http://www.PayPal.com PayPal.com]<br />
* [http://en.wikipedia.org/wiki/Paypal PayPal's Wikipedia page]<br />
<br />
[[Category:Money transmitters]]</div>Lutherhttps://tests.bitcoin.it/w/index.php?title=CoinPal&diff=5905CoinPal2011-03-23T21:45:24Z<p>Luther: Add info about weekly limits</p>
<hr />
<div>'''CoinPal''' is an exchange that accepts [[PayPal]] for relatively small order sizes and a weekly limit on purchases. For new customers, the weekly limit is BTC 40. 14 days after a customer's first order, the weekly limit increases to BTC 60. 45 days after the first order, the limit becomes BTC 80.<br />
<br />
The site was first publicly available on December 31, 2010<ref>[http://www.bitcoin.org/smf/index.php?topic=2555.0 CoinPal beta - Buying bitcoins with PayPal]</ref>. On January 14th, 2010 CoinPal introduced an API that allows merchants and others seeking payment to use the service to accept micro-payments<ref>[http://www.bitcoin.org/smf/index.php?topic=2555.msg38148#msg38148 Re: CoinPal beta - Buying bitcoins with PayPal]</ref>.<br />
<br />
The operator of the site also operates [[CoinCard]] for [[selling bitcoins]].<br />
<br />
==See Also==<br />
<br />
* [[Buying bitcoins]]<br />
* [[Selling bitcoins]]<br />
<br />
==External Links==<br />
<br />
* [http://coinpal.ndrix.com/bw CoinPal.ndrix.com] web site<br />
<br />
==References==<br />
<references /><br />
<br />
[[Category:Exchanges]]</div>Lutherhttps://tests.bitcoin.it/w/index.php?title=Help:FAQ&diff=5852Help:FAQ2011-03-23T20:33:06Z<p>Luther: /* How long will it take to generate all the coins? */ Deleted a rouge Z</p>
<hr />
<div>Here you will find answers to the most commonly asked questions.<br />
<br />
== General ==<br />
=== What are bitcoins? ===<br />
Bitcoins are the unit of currency of the Bitcoin system. A commonly used shorthand for this is “BTC” to refer to a price or amount (eg: “100 BTC”)<br />
A Bitcoin isn't actually a 'thing' you can point at. It is just a number associated with a [[Address|Bitcoin Address]]. See also an [[Introduction|easy intro]] to bitcoin.<br />
<br />
=== How are new Bitcoins created? ===<br />
<br />
[[File:total_bitcoins_over_time_graph.png|thumb|Number of bitcoins over time, assuming a perfect 10-minute interval.]]<br />
New coins are generated by a network node each time it finds the solution to a certain mathematical problem (i.e. creates a new [[block]]), which is difficult to perform and can demonstrate a [[proof of work]]. The reward for solving a block is [[controlled inflation|automatically adjusted]] so that in the first 4 years of the Bitcoin network, 10,500,000 BTC will be created. The amount is halved each 4 years, so it will be 5,250,000 over years 4-8, 2,625,000 over years 8-12 and so on. Thus the total number of coins will approach 21,000,000 BTC over time.<br />
<br />
In addition, built into the network is a system that attempts to allocate new coins in blocks about every 10 minutes, on average, somewhere on the network. As the number of people who attempt to generate these new coins changes, the difficulty of creating new coins changes. This happens in a manner that is agreed upon by the network as a whole, based upon the time taken to generate the previous 2016 blocks. The difficulty is therefore related to the average computing resources devoted to generate these new coins over the time it took to create these previous blocks. The likelihood of somebody "discovering" one of these blocks is based on the computer they are using compared to all of the computers also generating blocks on the network.<br />
<br />
=== What's the current total amount of Bitcoins in existence? ===<br />
<br />
[http://blockexplorer.com/q/totalbc Current count]<br />
<br />
The number of blocks times the coin value of a block is the number of coins in existence. The coin value of a block is 50 BTC for each of the first 210,000 blocks, 25 BTC for the next 210,000 blocks, then 12.5 BTC, 6.25 BTC and so on.<br />
<br />
=== How divisible are Bitcoins? ===<br />
<br />
Technically, a Bitcoin can be divided down to 8 decimals using existing data structures, so 0.00000001 BTC is the smallest amount currently possible. Discussions about and ideas for ways to provide for even smaller quantities of Bitcoins may be created in the future if the need for them ever arises. For convenience, the program currently accepts only 2 decimal places as quantities smaller than 0.01 BTC are considered of trivial value and are usually used only to attack the network.<br />
<br />
=== How does the halving work when the number gets really small? ===<br />
<br />
The reward will go from 0.00000001 BTC to 0. Then no more coins will likely be created. <br />
<br />
The calculation is done as a right bitwise shift of a 64-bit signed integer. The integer is equal to the value in BTC * 100,000,000. This is how all Bitcoin balances/values are stored internally.<br />
<br />
Keep in mind that using current rules this will take nearly 100 years before it becomes an issue and Bitcoins may change considerably before that happens.<br />
<br />
=== How long will it take to generate all the coins? ===<br />
<br />
The last block that will generate coins will be block #6,929,999. This should be generated around year 2140. Then the total number of coins in circulation will remain static at 20,999,999.9769 BTC.<br />
<br />
Even if the allowed precision is expanded from the current 8 decimals, the total BTC in circulation will always be slightly below 21 million (assuming everything else stays the same). For example, with 16 decimals of precision, the end total would be 20999999.999999999496 BTC.<br />
<br />
=== If no more coins are going to be generated, will more blocks be created? ===<br />
<br />
Absolutely! Even before the creation of coins ends, the use of [[transaction fee|transaction fees]] will likely make creating new blocks more valuable from the fees than the new coins being created. When coin generation ends, what will sustain the ability to use bitcoins will be these fees entirely. There will be blocks generated after block #6,929,999, assuming that people are still using Bitcoins at that time.<br />
<br />
==Networking==<br />
=== Do I need to configure my firewall to run bitcoin? ===<br />
<br />
Bitcoin will connect to other nodes, usually on tcp port 8333. You will need to allow outgoing TCP connections to port 8333 if you want to allow your bitcoin client to connect to many nodes. Bitcoin will also try to connect to IRC (tcp port 6667) to meet other nodes to connect to.<br />
<br />
If you want to restrict your firewall rules to a few ips and/or don't want to allow IRC connection, you can find stable nodes in the [[Fallback Nodes|fallback nodes list]]. If your provider blocks the common IRC ports, note that lfnet also listens on port 7777. Connecting to this alternate port currently requires either recompiling Bitcoin, or changing routing rules. For example, on Linux you can evade a port 6667 block by doing something like this:<br />
<br />
echo 173.246.103.92 irc.lfnet.org >> /etc/hosts<br />
iptables -t nat -A OUTPUT -p tcp --dest 173.246.103.92 --dport 6667 -j DNAT --to-destination :7777 -m comment --comment "bitcoind irc connection"<br />
<br />
==Help==<br />
===I'd like to learn more. Where can I get help?===<br />
<br />
* Read the [[Introduction|introduction to bitcoin]] <br />
* See the videos, podcasts, and blog posts from the [[Press]]<br />
* Read and post on the [[Bitcoin:Community_portal#Bitcoin_Community_Forums|forums]]<br />
* Chat on one of the [[Bitcoin:Community_portal#IRC_Chat|Bitcoin IRC]] channels<br />
* Listen to [http://omegataupodcast.net/2011/03/59-bitcoin-a-digital-decentralized-currency/ this podcast], which goes into the details of how bitcoin works<br />
<br />
==See Also==<br />
<br />
* [[Man page]]<br />
<br />
[[zh-cn:FAQ]]<br />
[[fr:FAQ]]<br />
{{fromold|bitcoins}}<br />
<br />
[[Category:Technical]]<br />
[[Category:Vocabulary]]</div>Lutherhttps://tests.bitcoin.it/w/index.php?title=User:Luther&diff=5848User:Luther2011-03-23T20:03:05Z<p>Luther: New page</p>
<hr />
<div>=About Me=<br />
I am a member of [http://www.oto.org Ordo Templi Orientis] and a user of [http://gnu.org free software] and the [http://lamar.colostate.edu/~hillger/ metric system]. I support Bitcoin because I believe it to be technically superior to government currencies and I hope that one day everyone will be able to migrate to Bitcoin as the basis for all money.<br />
<br />
=Donations=<br />
Direct donations: 18zBGmCZCmruA8ndVjVb1uv3oi4pczFvsf<br />
<br />
Contributors Award participant: 18TFTUERaN6zqumcXXQ2Te2ZY3udtohvnk</div>Luther