BitcoinCash/nakamoto-archive
1
Fork 0
Code Issues Pull Requests Releases Activity

Add files via upload

Browse Source
This commit is contained in:
wakgill
2021-01-01 22:34:42 -06:00
committed by GitHub
parent 770d4fa260
commit 6b856c4ac7
12 changed files with 990 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/web/bitcoin-org/20090131/Satoshi_Nakamoto.asc
+13
View File
@@ -0,0 +1,13 @@
<!DOCTYPE html>
<html>
<head>
</head>
<body style="overflow:hidden;">
<iframe id="playback" src="https://web.archive.org/web/20110228054007if_/http://www.bitcoin.org:80/Satoshi_Nakamoto.asc" frameborder="0" style="position:absolute;top:65px;left:0;width:100%;">
</iframe>
</body>
</html>
docs/web/bitcoin-org/20090131/byzantine.html
+29
View File
@@ -0,0 +1,29 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>The Byzantine Generals' Problem</title>
</head>
<body>
<style type="text/css">
body {
margin-top:0 !important;
padding-top:0 !important;
/*min-width:800px !important;*/
}
</style>
<font size="+1">The Byzantine Generals' Problem</font><br>
<br>
A number of Byzantine Generals each have a computer and want to attack the King's wi-fi by brute forcing the password, which they've learned is a certain number of characters in length. Once they stimulate the network to generate a packet, they must crack the password within a limited time to break in and erase the logs, lest they be discovered. They only have enough CPU power to crack it fast enough if a majority of them attack at the same time.<br>
<br>
They don't particularly care when the attack will be, just that they agree. It has been decided that anyone who feels like it will announce an attack time, which we'll call the "plan", and whatever plan is heard first will be the official plan. The problem is that the network is not instantaneous, and if two generals announce different plans at close to the same time, some may hear one first and others hear the other first.<br>
<br>
They use a proof-of-work chain to solve the problem. Once each general receives whatever plan he hears first, he sets his computer to solve a difficult hash-based proof-of-work problem that includes the plan in its hash. The proof-of-work is difficult enough that with all of them working at once, it's expected to take 10 minutes before one of them finds a solution and broadcasts it to the network. Once received, everyone adjusts the hash in their proof-of-work computation to include the first solution, so that when they find the next proof-of-work, it chains after the first one. If anyone was working on a different plan, they switch to this one, because its proof-of-work chain is now longer.<br>
<br>
After about two hours, the plan should be hashed by a chain of 12 proofs-of-work. Every general, just by verifying the difficulty of the proof-of-work chain, can estimate how much parallel CPU power per hour was expended on it and see that it must have required the majority of the computers to produce in the allotted time. At the least, most of them had to have seen the plan, since the proof-of-work is proof that they worked on it. If the CPU power exhibited by the proof-of-work is sufficient to crack the password, they can safely attack at the agreed time.<br>
<br>
<a href="https://web.archive.org/web/20090309175840/http://www.bitcoin.org/">Home</a><br>
<br>
</body>
</html>
docs/web/bitcoin-org/20090131/index.html
+75
View File
@@ -0,0 +1,75 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Bitcoin.org - Research Paper on Peer-to-Peer Electronic Cash</title>
</head>
<body>
<font size="5"><b>Bitcoin.org</b></font>
<hr>
Bitcoin v0.1 Alpha Release<br>
<br>
Announcing the first release of Bitcoin, a new electronic cash system that uses a peer-to-peer network to prevent double-spending. It's completely decentralized with no server or trusted parties.<br>
<br>
<img src="/web/20090131115053im_/http://bitcoin.org/screen1.png" width="683" height="343" border="0"><br>
<br>
<img src="/web/20090131115053im_/http://bitcoin.org/screen2.png" width="636" height="327" border="0"><br>
<br>
It's currently Windows only for now. Open source C++ code is included.<br>
<br>
Download link: <a href="https://web.archive.org/web/20090131115053/http://sourceforge.net/project/showfiles.php?group_id=244765&amp;package_id=298441">bitcoin-0.1.3.rar</a><br>
<br>
- Unpack the files into a directory<br>
- Run BITCOIN.EXE<br>
- It automatically connects to other nodes<br>
<br>
If you can keep a node running that accepts incoming connections, you'll really be helping the network a lot. Port 8333 on your firewall needs to be open to receive incoming connections.<br>
<br>
The software is still alpha and experimental. There's no guarantee the system's state won't have to be restarted at some point if it becomes necessary, although I've done everything I can to build in extensibility and versioning.<br>
<br>
You can get coins by getting someone to send you some, or turn on Options-&gt;Generate Coins to run a node and generate blocks. I made the proof-of-work difficulty ridiculously easy to start with, so for a little while in the beginning a typical PC will be able to generate coins in just a few hours. It'll get a lot harder when competition makes the automatic adjustment drive up the difficulty. Generated coins must wait 120 blocks to mature before they can be spent.<br>
<br>
There are two ways to send money. If the recipient is online, you can enter their IP address and it will connect, get a new public key and send the transaction with comments. If the recipient is not online, it is possible to send to their Bitcoin address, which is a hash of their public key that they give you. They'll receive the transaction the next time they connect and get the block it's in. This method has the disadvantage that no comment information is sent, and a bit of privacy may be lost if the address is used multiple times, but it is a useful alternative if both users can't be online at the same time or the recipient can't receive incoming connections.<br>
<br>
Total circulation will be 21,000,000 coins. It'll be distributed to network nodes when they make blocks, with the amount cut in half every 4 years.<br>
<br>
first 4 years: 10,500,000 coins<br>
next 4 years: 5,250,000 coins<br>
next 4 years: 2,625,000 coins<br>
next 4 years: 1,312,500 coins<br>
etc...<br>
<br>
When that runs out, the system can support transaction fees if needed. It's based on open market competition, and there will probably always be nodes willing to process transactions for free.<br>
<br>
<br>
<br>
<br>
01 Nov 2008<br>
<br>
Bitcoin is a new design for a fully peer-to-peer electronic cash system. A C++ implementation is under development for release as an open source project.<br>
<br>
Main properties:<br>
&nbsp; - Double-spending is prevented with a peer-to-peer network.<br>
&nbsp; - No mint or other trusted parties.<br>
&nbsp; - Participants can be anonymous.<br>
<br>
The network works in parallel to generate a chain of
<a href="https://web.archive.org/web/20090131115053/http://www.hashcash.org/">Hashcash</a> style proof-of-work.
The proof-of-work chain is the key to
<a href="byzantine.html">solving the Byzantine Generals' Problem</a>
of synchronising the global view and generating computational proof
of the majority consensus without having to trust anyone.<br>
<br>
Paper: <a href="https://web.archive.org/web/20090131115053/http://www.bitcoin.org/bitcoin.pdf"><b>Bitcoin: A Peer-to-Peer Electronic Cash System</b></a><br>
<br>
<b>Abstract.</b> A purely peer-to-peer version of electronic cash would allow online payments to be sent directly from one party to another without the burdens of going through financial institutions. Digital signatures provide part of the solution, but the main benefits are lost if a trusted party is still required to prevent double-spending. We propose a solution to the double-spending problem using a peer-to-peer network. The network timestamps transactions by hashing them into an ongoing chain of hash-based proof-of-work, forming a record that cannot be changed without redoing the proof-of-work. The longest chain not only serves as proof of the sequence of events witnessed, but proof that it came from the largest pool of CPU power. As long as honest nodes control the most CPU power on the network, they can generate the longest chain and outpace any attackers. The network itself requires minimal structure. Messages are broadcasted on a best effort basis, and nodes can leave and rejoin the network at will, accepting the longest proof-of-work chain as proof of what happened while they were gone.<br>
<br>
<br>
<br>
<br>
Satoshi Nakamoto<br>
<img src="https://web.archive.org/web/20090131115053im_/http://bitcoin.org/something.png" width="120" height="19" border="0"><br>
<a href="Satoshi_Nakamoto.asc">PGP key</a><br>
<br>
</body>
</html>
docs/web/bitcoin-org/20090303/byzantine.html
+29
View File
@@ -0,0 +1,29 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>The Byzantine Generals' Problem</title>
</head>
<body>
<style type="text/css">
body {
margin-top:0 !important;
padding-top:0 !important;
/*min-width:800px !important;*/
}
</style>
<font size="+1">The Byzantine Generals' Problem</font><br>
<br>
A number of Byzantine Generals each have a computer and want to attack the King's wi-fi by brute forcing the password, which they've learned is a certain number of characters in length. Once they stimulate the network to generate a packet, they must crack the password within a limited time to break in and erase the logs, lest they be discovered. They only have enough CPU power to crack it fast enough if a majority of them attack at the same time.<br>
<br>
They don't particularly care when the attack will be, just that they agree. It has been decided that anyone who feels like it will announce an attack time, which we'll call the "plan", and whatever plan is heard first will be the official plan. The problem is that the network is not instantaneous, and if two generals announce different plans at close to the same time, some may hear one first and others hear the other first.<br>
<br>
They use a proof-of-work chain to solve the problem. Once each general receives whatever plan he hears first, he sets his computer to solve a difficult hash-based proof-of-work problem that includes the plan in its hash. The proof-of-work is difficult enough that with all of them working at once, it's expected to take 10 minutes before one of them finds a solution and broadcasts it to the network. Once received, everyone adjusts the hash in their proof-of-work computation to include the first solution, so that when they find the next proof-of-work, it chains after the first one. If anyone was working on a different plan, they switch to this one, because its proof-of-work chain is now longer.<br>
<br>
After about two hours, the plan should be hashed by a chain of 12 proofs-of-work. Every general, just by verifying the difficulty of the proof-of-work chain, can estimate how much parallel CPU power per hour was expended on it and see that it must have required the majority of the computers to produce in the allotted time. At the least, most of them had to have seen the plan, since the proof-of-work is proof that they worked on it. If the CPU power exhibited by the proof-of-work is sufficient to crack the password, they can safely attack at the agreed time.<br>
<br>
<a href="https://web.archive.org/web/20090309175840/http://www.bitcoin.org/">Home</a><br>
<br>
</body>
</html>
docs/web/bitcoin-org/20090303/index.html
+79
View File
@@ -0,0 +1,79 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Bitcoin.org - Open Source P2P Electronic Cash</title>
</head>
<body>
<font size="5"><b>Bitcoin.org</b></font>
<hr>
Bitcoin v0.1 Alpha Release<br>
<br>
Announcing the first release of Bitcoin, a new open source peer-to-peer electronic cash system that's completely decentralized, with no central server or trusted parties. Users hold the crypto keys to their own money and transact directly with each other, with the help of the network to check for double-spending.<br>
<br>
<img src="https://web.archive.org/web/20090303195936im_/http://bitcoin.org/screen3.png" width="640" height="300" border="0"><br>
<br>
<img src="https://web.archive.org/web/20090303195936im_/http://bitcoin.org/screen4.png" width="625" height="286" border="0"><br>
<br>
Windows NT/2000/XP/Vista. Open source C++ code is included.<br>
<br>
Download link: <a href="https://web.archive.org/web/20090303195936/http://sourceforge.net/project/showfiles.php?group_id=244765&amp;package_id=298441">bitcoin-0.1.5.rar</a><br>
<br>
- Unpack the files into a directory<br>
- Run BITCOIN.EXE<br>
- It automatically connects to other nodes<br>
<br>
If you can keep a node running that accepts incoming connections, you'll really be helping the network a lot. Port 8333 on your firewall needs to be open to receive incoming connections.<br>
<br>
The software is still alpha and experimental. There's no guarantee the system's state won't have to be restarted at some point if it becomes necessary, although I've done everything I can to build in extensibility and versioning.<br>
<br>
You can get coins by getting someone to send you some, or turn on Options-&gt;Generate Coins to run a node and generate blocks. I made the proof-of-work difficulty ridiculously easy to start with, so for a little while in the beginning a typical PC will be able to generate coins in just a few hours. It'll get a lot harder when competition makes the automatic adjustment drive up the difficulty. Generated coins must wait 120 blocks to mature before they can be spent.<br>
<br>
There are two ways to send money. If the recipient is online, you can enter their IP address and it will connect, get a new public key and send the transaction with comments. If the recipient is not online, it is possible to send to their Bitcoin address, which is a hash of their public key that they give you. They'll receive the transaction the next time they connect and get the block it's in. This method has the disadvantage that no comment information is sent, and a bit of privacy may be lost if the address is used multiple times, but it is a useful alternative if both users can't be online at the same time or the recipient can't receive incoming connections.<br>
<br>
Total circulation will be 21,000,000 coins. It'll be distributed to network nodes when they make blocks, with the amount cut in half every 4 years.<br>
<br>
first 4 years: 10,500,000 coins<br>
next 4 years: 5,250,000 coins<br>
next 4 years: 2,625,000 coins<br>
next 4 years: 1,312,500 coins<br>
etc...<br>
<br>
When that runs out, the system can support transaction fees if needed. It's based on open market competition, and there will probably always be nodes willing to process transactions for free.<br>
<br>
<br>
<br>
<i>01 Nov 2008</i><br>
<br>
Bitcoin is a new design for a fully peer-to-peer electronic cash system. A C++ implementation is under development for release as an open source project.<br>
<br>
Main properties:<br>
&nbsp; - Double-spending is prevented with a peer-to-peer network.<br>
&nbsp; - No mint or other trusted parties.<br>
&nbsp; - Participants can be anonymous.<br>
<br>
The network works in parallel to generate a chain of
<a href="https://web.archive.org/web/20090303195936/http://www.hashcash.org/">Hashcash</a> style proof-of-work.
The proof-of-work chain is the key to
<a href="/web/bitcoinorg/20090303/byzantine.html">solving the Byzantine Generals' Problem</a>
of synchronising the global view and generating computational proof
of the majority consensus without having to trust anyone.<br>
<br>
Paper: <a href="https://web.archive.org/web/20090303195936/http://www.bitcoin.org/bitcoin.pdf"><b>Bitcoin: A Peer-to-Peer Electronic Cash System</b></a><br>
<br>
<b>Abstract.</b> A purely peer-to-peer version of electronic cash would allow online payments to be sent directly from one party to another without going through a financial institution. Digital signatures provide part of the solution, but the main benefits are lost if a trusted third party is still required to prevent double-spending. We propose a solution to the double-spending problem using a peer-to-peer network. The network timestamps transactions by hashing them into an ongoing chain of hash-based proof-of-work, forming a record that cannot be changed without redoing the proof-of-work. The longest chain not only serves as proof of the sequence of events witnessed, but proof that it came from the largest pool of CPU power. As long as a majority of CPU power is controlled by nodes that are not cooperating to attack the network, they'll generate the longest chain and outpace attackers. The network itself requires minimal structure. Messages are broadcast on a best effort basis, and nodes can leave and rejoin the network at will, accepting the longest proof-of-work chain as proof of what happened while they were gone.<br>
<br>
<br>
<br>
Related Links<br>
<a href="https://web.archive.org/web/20090303195936/http://www.weidai.com/bmoney.txt">Wei Dai's b-money</a><br>
<a href="https://web.archive.org/web/20090303195936/http://unenumerated.blogspot.com/2005/12/bit-gold.html">Nick Szabo's bit gold</a><br>
<a href="https://web.archive.org/web/20090303195936/http://testgrid.allmydata.org:3567/uri/URI:DIR2-RO:j74uhg25nwdpjpacl6rkat2yhm:kav7ijeft5h7r7rxdp5bgtlt3viv32yabqajkrdykozia5544jqa/wiki.html#%5B%5BDecentralized%20Money%5D%5D">Zooko's blog</a><br>
<br>
<br>
<br>
Satoshi Nakamoto<br>
<img src="https://web.archive.org/web/20090303195936im_/http://bitcoin.org/something.png" width="120" height="19" border="0"><br>
<a href="Satoshi_Nakamoto.asc">PGP key</a><br>
<br>
</body>
</html>
docs/web/bitcoin-org/20090722/byzantine.html
+29
View File
@@ -0,0 +1,29 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>The Byzantine Generals' Problem</title>
</head>
<body>
<style type="text/css">
body {
margin-top:0 !important;
padding-top:0 !important;
/*min-width:800px !important;*/
}
</style>
<font size="+1">The Byzantine Generals' Problem</font><br>
<br>
A number of Byzantine Generals each have a computer and want to attack the King's wi-fi by brute forcing the password, which they've learned is a certain number of characters in length. Once they stimulate the network to generate a packet, they must crack the password within a limited time to break in and erase the logs, lest they be discovered. They only have enough CPU power to crack it fast enough if a majority of them attack at the same time.<br>
<br>
They don't particularly care when the attack will be, just that they agree. It has been decided that anyone who feels like it will announce an attack time, which we'll call the "plan", and whatever plan is heard first will be the official plan. The problem is that the network is not instantaneous, and if two generals announce different plans at close to the same time, some may hear one first and others hear the other first.<br>
<br>
They use a proof-of-work chain to solve the problem. Once each general receives whatever plan he hears first, he sets his computer to solve a difficult hash-based proof-of-work problem that includes the plan in its hash. The proof-of-work is difficult enough that with all of them working at once, it's expected to take 10 minutes before one of them finds a solution and broadcasts it to the network. Once received, everyone adjusts the hash in their proof-of-work computation to include the first solution, so that when they find the next proof-of-work, it chains after the first one. If anyone was working on a different plan, they switch to this one, because its proof-of-work chain is now longer.<br>
<br>
After about two hours, the plan should be hashed by a chain of 12 proofs-of-work. Every general, just by verifying the difficulty of the proof-of-work chain, can estimate how much parallel CPU power per hour was expended on it and see that it must have required the majority of the computers to produce in the allotted time. At the least, most of them had to have seen the plan, since the proof-of-work is proof that they worked on it. If the CPU power exhibited by the proof-of-work is sufficient to crack the password, they can safely attack at the agreed time.<br>
<br>
<a href="https://web.archive.org/web/20090309175840/http://www.bitcoin.org/">Home</a><br>
<br>
</body>
</html>
docs/web/bitcoin-org/20090722/index.html
+85
View File
@@ -0,0 +1,85 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Bitcoin.org - Open Source P2P Electronic Cash</title>
</head>
<body>
<font style="font-size: 26px"><b>Bitcoin.org</b></font>
<font style="font-size: 13px" face="helv, arial">
<hr>
Bitcoin is a free open source peer-to-peer electronic cash system that is completely decentralized, without the need for a central server or trusted parties. Users hold the crypto keys to their own money and transact directly with each other, with the help of the P2P network to check for double-spending.<br>
<br>
<img src="https://web.archive.org/web/20090722011820im_/http://www.bitcoin.org/screen3.png" width="640" height="300" border="0"><br>
<br>
<img src="https://web.archive.org/web/20090722011820im_/http://www.bitcoin.org/screen4.png" width="625" height="286" border="0"><br>
<br>
Windows NT/2000/XP/Vista. Open source C++ code is included.<br>
<br>
Download link: <a href="https://web.archive.org/web/20090722011820/http://sourceforge.net/project/showfiles.php?group_id=244765&amp;package_id=298441">bitcoin-0.1.5.rar</a><br>
<br>
- Unpack the files into a directory<br>
- Run BITCOIN.EXE<br>
- It automatically connects to other nodes<br>
<br>
If you can keep a node running that accepts incoming connections, you'll really be helping the network a lot. Port 8333 on your firewall needs to be open to receive incoming connections.<br>
<br>
The software is still alpha and experimental. There's no guarantee the system's state won't have to be restarted at some point if it becomes necessary, although I've done everything I can to build in extensibility and versioning.<br>
<br>
You can get coins by getting someone to send you some, or turn on Options-&gt;Generate Coins to run a node and generate blocks. I made the proof-of-work difficulty ridiculously easy to start with, so for a little while in the beginning a typical PC will be able to generate coins in just a few hours. It'll get a lot harder when competition makes the automatic adjustment drive up the difficulty. Generated coins must wait 120 blocks to mature before they can be spent.<br>
<br>
There are two ways to send money. If the recipient is online, you can enter their IP address and it will connect, get a new public key and send the transaction with comments. If the recipient is not online, it is possible to send to their Bitcoin address, which is a hash of their public key that they give you. They'll receive the transaction the next time they connect and get the block it's in. This method has the disadvantage that no comment information is sent, and a bit of privacy may be lost if the address is used multiple times, but it is a useful alternative if both users can't be online at the same time or the recipient can't receive incoming connections.<br>
<br>
Total circulation will be 21,000,000 coins. It'll be distributed to network nodes when they make blocks, with the amount cut in half every 4 years.<br>
<br>
first 4 years: 10,500,000 coins<br>
next 4 years: 5,250,000 coins<br>
next 4 years: 2,625,000 coins<br>
next 4 years: 1,312,500 coins<br>
etc...<br>
<br>
When that runs out, the system can support transaction fees if needed. It's based on open market competition, and there will probably always be nodes willing to process transactions for free.<br>
<br>
<br>
<br>
<i>01 Nov 2008</i><br>
<br>
Bitcoin is a new design for a fully peer-to-peer electronic cash system. A C++ implementation is under development for release as an open source project.<br>
<br>
Main properties:<br>
&nbsp; - Double-spending is prevented with a peer-to-peer network.<br>
&nbsp; - No mint or other trusted parties.<br>
&nbsp; - Participants can be anonymous.<br>
<br>
The network works in parallel to generate a chain of
<a href="https://web.archive.org/web/20090722011820/http://www.hashcash.org/">Hashcash</a> style proof-of-work.
The proof-of-work chain is the key to
<a href="byzantine.html">solving the Byzantine Generals' Problem</a>
of synchronising the global view and generating computational proof
of the majority consensus without having to trust anyone.<br>
<br>
Paper: <a href="https://web.archive.org/web/20090722011820/http://www.bitcoin.org/bitcoin.pdf"><b>Bitcoin: A Peer-to-Peer Electronic Cash System</b></a><br>
<br>
<b>Abstract.</b> A purely peer-to-peer version of electronic cash would allow online payments to be sent directly from one party to another without going through a financial institution. Digital signatures provide part of the solution, but the main benefits are lost if a trusted third party is still required to prevent double-spending. We propose a solution to the double-spending problem using a peer-to-peer network. The network timestamps transactions by hashing them into an ongoing chain of hash-based proof-of-work, forming a record that cannot be changed without redoing the proof-of-work. The longest chain not only serves as proof of the sequence of events witnessed, but proof that it came from the largest pool of CPU power. As long as a majority of CPU power is controlled by nodes that are not cooperating to attack the network, they'll generate the longest chain and outpace attackers. The network itself requires minimal structure. Messages are broadcast on a best effort basis, and nodes can leave and rejoin the network at will, accepting the longest proof-of-work chain as proof of what happened while they were gone.<br>
<br>
<br>
<br>
Related Links<br>
<a href="https://web.archive.org/web/20090722011820/http://www.weidai.com/bmoney.txt">Wei Dai's b-money</a><br>
<a href="https://web.archive.org/web/20090722011820/http://unenumerated.blogspot.com/2005/12/bit-gold.html">Nick Szabo's bit gold</a><br>
<a href="https://web.archive.org/web/20090722011820/http://testgrid.allmydata.org:3567/uri/URI:DIR2-RO:j74uhg25nwdpjpacl6rkat2yhm:kav7ijeft5h7r7rxdp5bgtlt3viv32yabqajkrdykozia5544jqa/wiki.html#%5B%5BDecentralized%20Money%5D%5D">Zooko's blog</a><br>
<br>
<br>
I'll announce new version updates on the mailing list:<br>
bitcoin-list@lists.sourceforge.net<br>
<a href="https://web.archive.org/web/20090722011820/http://lists.sourceforge.net/mailman/listinfo/bitcoin-list">Subscribe/Unsubscribe</a><br>
<a href="https://web.archive.org/web/20090722011820/http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-list">Archives</a><br>
<br>
<br>
Satoshi Nakamoto<br>
<img src="https://web.archive.org/web/20090722011820im_/http://www.bitcoin.org/something.png" width="120" height="19" border="0"><br>
<a href="Satoshi_Nakamoto.asc">PGP key</a><br>
<br>
</font>
</body>
</html>
docs/web/bitcoin-org/20090822/byzantine.html
+31
View File
@@ -0,0 +1,31 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>The Byzantine Generals' Problem</title>
</head>
<body>
<style type="text/css">
body {
margin-top:0 !important;
padding-top:0 !important;
/*min-width:800px !important;*/
}
</style>
<small>This page was archived one time on 09 March 2009. It is provided here for continuity but should not necessarily be taken as an exact copy of the page that existed at this date.</small>
<hr>
<font size="+1">The Byzantine Generals' Problem</font><br>
<br>
A number of Byzantine Generals each have a computer and want to attack the King's wi-fi by brute forcing the password, which they've learned is a certain number of characters in length. Once they stimulate the network to generate a packet, they must crack the password within a limited time to break in and erase the logs, lest they be discovered. They only have enough CPU power to crack it fast enough if a majority of them attack at the same time.<br>
<br>
They don't particularly care when the attack will be, just that they agree. It has been decided that anyone who feels like it will announce an attack time, which we'll call the "plan", and whatever plan is heard first will be the official plan. The problem is that the network is not instantaneous, and if two generals announce different plans at close to the same time, some may hear one first and others hear the other first.<br>
<br>
They use a proof-of-work chain to solve the problem. Once each general receives whatever plan he hears first, he sets his computer to solve a difficult hash-based proof-of-work problem that includes the plan in its hash. The proof-of-work is difficult enough that with all of them working at once, it's expected to take 10 minutes before one of them finds a solution and broadcasts it to the network. Once received, everyone adjusts the hash in their proof-of-work computation to include the first solution, so that when they find the next proof-of-work, it chains after the first one. If anyone was working on a different plan, they switch to this one, because its proof-of-work chain is now longer.<br>
<br>
After about two hours, the plan should be hashed by a chain of 12 proofs-of-work. Every general, just by verifying the difficulty of the proof-of-work chain, can estimate how much parallel CPU power per hour was expended on it and see that it must have required the majority of the computers to produce in the allotted time. At the least, most of them had to have seen the plan, since the proof-of-work is proof that they worked on it. If the CPU power exhibited by the proof-of-work is sufficient to crack the password, they can safely attack at the agreed time.<br>
<br>
<a href="https://web.archive.org/web/20090309175840/http://www.bitcoin.org/">Home</a><br>
<br>
</body>
</html>
docs/web/bitcoin-org/20090822/index.html
+86
View File
@@ -0,0 +1,86 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Bitcoin.org - Open Source P2P Electronic Cash</title>
</head>
<body>
<font style="font-size: 26px"><b>Bitcoin.org</b></font>
<font style="font-size: 13px" face="helv, arial">
<hr>
Bitcoin is a free open source peer-to-peer electronic cash system that is completely decentralized, without the need for a central server or trusted parties. Users hold the crypto keys to their own money and transact directly with each other, with the help of the P2P network to check for double-spending.<br>
<br>
<img src="https://web.archive.org/web/20090822060833im_/http://www.bitcoin.org/screen3.png" width="640" height="300" border="0"><br>
<br>
<img src="https://web.archive.org/web/20090822060833im_/http://www.bitcoin.org/screen4.png" width="625" height="286" border="0"><br>
<br>
Windows NT/2000/XP/Vista. Open source C++ code is included.<br>
<br>
Download link: <a href="https://web.archive.org/web/20090822060833/http://sourceforge.net/project/showfiles.php?group_id=244765&amp;package_id=298441">bitcoin-0.1.5.rar</a><br>
<br>
- Unpack the files into a directory<br>
- Run BITCOIN.EXE<br>
- It automatically connects to other nodes<br>
<br>
If you can keep a node running that accepts incoming connections, you'll really be helping the network a lot. Port 8333 on your firewall needs to be open to receive incoming connections.<br>
<br>
The software is still alpha and experimental. There's no guarantee the system's state won't have to be restarted at some point if it becomes necessary, although I've done everything I can to build in extensibility and versioning.<br>
<br>
You can get coins by getting someone to send you some, or turn on Options-&gt;Generate Coins to run a node and generate blocks. I made the proof-of-work difficulty ridiculously easy to start with, so for a little while in the beginning a typical PC will be able to generate coins in just a few hours. It'll get a lot harder when competition makes the automatic adjustment drive up the difficulty. Generated coins must wait 120 blocks to mature before they can be spent.<br>
<br>
There are two ways to send money. If the recipient is online, you can enter their IP address and it will connect, get a new public key and send the transaction with comments. If the recipient is not online, it is possible to send to their Bitcoin address, which is a hash of their public key that they give you. They'll receive the transaction the next time they connect and get the block it's in. This method has the disadvantage that no comment information is sent, and a bit of privacy may be lost if the address is used multiple times, but it is a useful alternative if both users can't be online at the same time or the recipient can't receive incoming connections.<br>
<br>
Total circulation will be 21,000,000 coins. It'll be distributed to network nodes when they make blocks, with the amount cut in half every 4 years.<br>
<br>
first 4 years: 10,500,000 coins<br>
next 4 years: 5,250,000 coins<br>
next 4 years: 2,625,000 coins<br>
next 4 years: 1,312,500 coins<br>
etc...<br>
<br>
When that runs out, the system can support transaction fees if needed. It's based on open market competition, and there will probably always be nodes willing to process transactions for free.<br>
<br>
<br>
<br>
<i>01 Nov 2008</i><br>
<br>
Bitcoin is a new design for a fully peer-to-peer electronic cash system. A C++ implementation is under development for release as an open source project.<br>
<br>
Main properties:<br>
&nbsp; - Double-spending is prevented with a peer-to-peer network.<br>
&nbsp; - No mint or other trusted parties.<br>
&nbsp; - Participants can be anonymous.<br>
<br>
The network works in parallel to generate a chain of
<a href="https://web.archive.org/web/20090822060833/http://www.hashcash.org/">Hashcash</a> style proof-of-work.
The proof-of-work chain is the key to
<a href="byzantine.html">solving the Byzantine Generals' Problem</a>
of synchronising the global view and generating computational proof
of the majority consensus without having to trust anyone.<br>
<br>
Paper: <a href="https://web.archive.org/web/20090822060833/http://www.bitcoin.org/bitcoin.pdf"><b>Bitcoin: A Peer-to-Peer Electronic Cash System</b></a><br>
<br>
<b>Abstract.</b> A purely peer-to-peer version of electronic cash would allow online payments to be sent directly from one party to another without going through a financial institution. Digital signatures provide part of the solution, but the main benefits are lost if a trusted third party is still required to prevent double-spending. We propose a solution to the double-spending problem using a peer-to-peer network. The network timestamps transactions by hashing them into an ongoing chain of hash-based proof-of-work, forming a record that cannot be changed without redoing the proof-of-work. The longest chain not only serves as proof of the sequence of events witnessed, but proof that it came from the largest pool of CPU power. As long as a majority of CPU power is controlled by nodes that are not cooperating to attack the network, they'll generate the longest chain and outpace attackers. The network itself requires minimal structure. Messages are broadcast on a best effort basis, and nodes can leave and rejoin the network at will, accepting the longest proof-of-work chain as proof of what happened while they were gone.<br>
<br>
<br>
<br>
Related Links<br>
<a href="https://web.archive.org/web/20090822060833/http://www.weidai.com/bmoney.txt">Wei Dai's b-money</a><br>
<a href="https://web.archive.org/web/20090822060833/http://unenumerated.blogspot.com/2005/12/bit-gold.html">Nick Szabo's bit gold</a><br>
<a href="https://web.archive.org/web/20090822060833/http://testgrid.allmydata.org:3567/uri/URI:DIR2-RO:j74uhg25nwdpjpacl6rkat2yhm:kav7ijeft5h7r7rxdp5bgtlt3viv32yabqajkrdykozia5544jqa/wiki.html#%5B%5BDecentralized%20Money%5D%5D">Zooko's blog</a><br>
<br>
<br>
I'll announce new version updates on the mailing list:<br>
bitcoin-list@lists.sourceforge.net<br>
<a href="https://web.archive.org/web/20090822060833/http://lists.sourceforge.net/mailman/listinfo/bitcoin-list">Subscribe/Unsubscribe</a><br>
<a href="https://web.archive.org/web/20090822060833/http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-list">Archives</a><br>
<br>
<br>
Satoshi Nakamoto<br>
<img src="https://web.archive.org/web/20090822060833im_/http://www.bitcoin.org/something.png" width="120" height="19" border="0"><br>
<a href="Satoshi_Nakamoto.asc">PGP key</a><br>
<br>
</font>
</body>
</html>
docs/web/bitcoin-org/20100106/index.html
+162
View File
@@ -0,0 +1,162 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en" dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
<title>Bitcoin P2P Cryptocurrency | Bitcoin</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/web/20100106082749cs_/http://www.bitcoin.org/modules/aggregator/aggregator.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/web/20100106082749cs_/http://www.bitcoin.org/modules/node/node.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/web/20100106082749cs_/http://www.bitcoin.org/modules/system/defaults.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/web/20100106082749cs_/http://www.bitcoin.org/modules/system/system.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/web/20100106082749cs_/http://www.bitcoin.org/modules/system/system-menus.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/web/20100106082749cs_/http://www.bitcoin.org/modules/tableofcontents/tableofcontents.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/web/20100106082749cs_/http://www.bitcoin.org/modules/user/user.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/web/20100106082749cs_/http://www.bitcoin.org/sites/all/themes/custom3/html-elements.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/web/20100106082749cs_/http://www.bitcoin.org/sites/all/themes/zen/zen/tabs.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/web/20100106082749cs_/http://www.bitcoin.org/sites/all/themes/zen/zen/messages.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/web/20100106082749cs_/http://www.bitcoin.org/sites/all/themes/zen/zen/block-editing.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/web/20100106082749cs_/http://www.bitcoin.org/sites/all/themes/zen/zen/wireframes.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/web/20100106082749cs_/http://www.bitcoin.org/sites/all/themes/custom3/layout.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/web/20100106082749cs_/http://www.bitcoin.org/sites/all/themes/custom3/custom3.css?h"/>
<link type="text/css" rel="stylesheet" media="print" href="https://web.archive.org/web/web/20100106082749cs_/http://www.bitcoin.org/sites/all/themes/custom3/print.css?h"/>
<!--[if IE]>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/sites/all/themes/zen/zen/ie.css?h" />
<![endif]-->
<script type="text/javascript" src="https://web.archive.org/web/web/20100106082749js_/http://www.bitcoin.org/misc/jquery.js?h"></script>
<script type="text/javascript" src="https://web.archive.org/web/web/20100106082749js_/http://www.bitcoin.org/misc/drupal.js?h"></script>
<script type="text/javascript" src="https://web.archive.org/web/web/20100106082749js_/http://www.bitcoin.org/modules/tableofcontents/jquery.scrollTo-min.js?h"></script>
<script type="text/javascript" src="https://web.archive.org/web/web/20100106082749js_/http://www.bitcoin.org/modules/tableofcontents/jquery.localscroll-min.js?h"></script>
<script type="text/javascript" src="https://web.archive.org/web/web/20100106082749js_/http://www.bitcoin.org/modules/tableofcontents/tableofcontents.js?h"></script>
<script type="text/javascript">
<!--//--><![CDATA[//><!--
jQuery.extend(Drupal.settings, { "basePath": "/" });
//--><!]]>
</script>
</head>
<body class="front not-logged-in node-type-page one-sidebar sidebar-right">
<div id="page"><div id="page-inner">
<a name="navigation-top" id="navigation-top"></a>
<div id="header"><div id="header-inner" class="clear-block">
<div id="logo-title">
<div id="logo"><a href="https://web.archive.org/web/web/20100106082749/http://www.bitcoin.org/" title="Home" rel="home"><img src="https://web.archive.org/web/20100106082749im_/http://www.bitcoin.org/sites/all/themes/custom3/logo.png" alt="Home" id="logo-image"/></a></div>
</div> <!-- /#logo-title -->
</div></div> <!-- /#header-inner, /#header -->
<div id="main"><div id="main-inner" class="clear-block">
<div id="content"><div id="content-inner">
<div id="content-header">
<h1 class="title">Bitcoin P2P Cryptocurrency</h1>
</div> <!-- /#content-header -->
<div id="content-area">
<div id="node-3" class="node node-type-page"><div class="node-inner">
<div class="content">
<h2 class="homepage-title page-title">Bitcoin P2P Cryptocurrency</h2>
<p>Bitcoin is a peer-to-peer network based anonymous digital currency. Peer-to-peer (P2P) means that there is no central authority to issue new money or keep track of transactions. Instead, these tasks are managed collectively by the nodes of the network. Anonymity means that the real world identity of the parties of a transaction can be kept hidden from the public or even from the parties themselves. Advantages:</p>
<ul>
<li>Transfer money easily through the internet, without having to trust third parties.</li>
<li>Third parties can’t prevent or control your transactions.</li>
<li>Be safe from the unstability caused by fractional reserve banking and bad policies of central banks. The limited inflation of the Bitcoin system’s money supply is distributed evenly (by CPU power) throughout the network, not monopolized by the banks.</li>
</ul>
<p>Bitcoin is an open source project created by Satoshi Nakamoto, and is currently in beta development stage. Get the latest version of Bitcoin at the <a href="https://web.archive.org/web/20100106082749/http://sourceforge.net/projects/bitcoin/">Sourceforge project page</a>.</p>
<p>Screenshots:</p>
<p><a href="https://web.archive.org/web/web/20100106082749/http://www.bitcoin.org/sites/default/files/screen3.png"><img src="https://web.archive.org/web/20100106082749im_/http://www.bitcoin.org/sites/default/files/screen3_thumb.png" alt="Main window screenshot"/></a></p>
<p><a href="https://web.archive.org/web/web/20100106082749/http://www.bitcoin.org/sites/default/files/screen4.png"><img src="https://web.archive.org/web/20100106082749im_/http://www.bitcoin.org/sites/default/files/screen4_thumb.png" alt="Sending dialog screenshot"/></a></p>
<p>Using Bitcoin:</p>
<p>Turn on Options-&gt;Generate Coins to get a few coins by helping to run the network. Bitcoin runs in the background when your computer is idle and should not slow down other programs. It may take days to successfully generate a coin, so be patient. The timing varies and depends on how much idle CPU time you contribute. </p>
<p>The total eventual circulation of Bitcoins will be 21,000,000 coins. There will never be more coins than that. The coins are entering circulation gradually, at a steady pace over many years, to nodes supporting the network in proportion to the CPU time they contribute.</p>
<p>To receive incoming connections, you need to set your firewall to forward port 8333 (TCP) to your computer. This increases the number of nodes you can connect with.</p>
<p><a style="font-size: 1.2em; font-weight: 600;" href="https://web.archive.org/web/20100106082749/http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.2.0-win32-setup.exe/download">Download Bitcoin 0.2 for Windows (exe)</a> <span style="font-size: 0.9em; line-height: 0.9em;">(3.1MB)</span><br/>
<a style="font-size: 1.2em; font-weight: 600;" href="https://web.archive.org/web/20100106082749/http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.2.0-win32.zip/download">Download Bitcoin 0.2 for Windows (zip)</a> <span style="font-size: 0.9em; line-height: 0.9em;">(3.1MB)</span><br/>
<a style="font-size: 1.2em; font-weight: 600;" href="https://web.archive.org/web/20100106082749/http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.2.0-linux.tar.gz/download">Download Bitcoin 0.2 for Linux</a> <span style="font-size: 0.9em; line-height: 0.9em;">(2.4MB)</span></p>
<p>Note: If you have 64-bit Linux, the package ia32-libs needs to be installed.</p>
<p><span style="font-size: 0.8em; line-height: 0.8em;">SHA1 b8acb0008c5ce8a3c30f67491d7a85d1a7f73174 bitcoin-0.2.0-win32-setup.exe<br/>
SHA1 9efbdd7ba31989f477d3006b3b867942579c4695 bitcoin-0.2.0-win32.zip<br/>
SHA1 6ff749851e66801f2c82a199eec595d853c9fa8d bitcoin-0.2.0-linux.tar.gz<br/>
</span></p>
</div>
</div></div> <!-- /node-inner, /node -->
</div>
</div></div> <!-- /#content-inner, /#content -->
<div id="sidebar-right"><div id="sidebar-right-inner" class="region region-right">
<div id="block-menu-primary-links" class="block block-menu region-odd odd region-count-1 count-1"><div class="block-inner">
<h2 class="title">Primary links</h2>
<div class="content">
<ul class="menu"><li class="leaf first active-trail"><a href="https://web.archive.org/web/web/20100106082749/http://www.bitcoin.org/" title="" class="active">Home</a></li>
<li class="leaf"><a href="node/1.html" title="FAQ">FAQ</a></li>
<li class="leaf"><a href="https://web.archive.org/web/20100106082749/http://www.bitcoin.org/smf/" title="">Forum</a></li>
<li class="leaf last"><a href="node/2.html" title="Contact">Contact</a></li>
</ul> </div>
</div></div> <!-- /block-inner, /block -->
<div id="block-block-1" class="block block-block region-even even region-count-2 count-2"><div class="block-inner">
<h2 class="title">Download Bitcoin</h2>
<div class="content">
<p style="margin-bottom: -0.4em;"><img src="https://web.archive.org/web/20100106082749im_/http://www.bitcoin.org/sites/default/files/images/download_arrow.png" width="21" height="22" style="float: left; margin-right: 0.45em; margin-top: 0.56em;"/>Download<br/>Bitcoin 0.2</p>
<p><a href="https://web.archive.org/web/20100106082749/http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.2.0-win32-setup.exe/download">Windows (exe)</a> 3.1MB<br/>
<a href="https://web.archive.org/web/20100106082749/http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.2.0-win32.zip/download">Windows (zip)</a> 3.1MB<br/>
<a href="https://web.archive.org/web/20100106082749/http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.2.0-linux.tar.gz/download">Linux</a> (32-bit) 2.4MB</p>
</div>
</div></div> <!-- /block-inner, /block -->
</div></div> <!-- /#sidebar-right-inner, /#sidebar-right -->
</div></div> <!-- /#main-inner, /#main -->
<div id="footer"><div id="footer-inner" class="region region-footer">
<div id="block-block-3" class="block block-block region-odd odd region-count-1 count-3"><div class="block-inner">
<div class="content">
<p><center><span class="footer"><a class="sflogo" href="https://web.archive.org/web/20100106082749/http://sourceforge.net/projects/bitcoin"><img src="https://web.archive.org/web/20100106082749im_/http://www.bitcoin.org/sites/all/themes/custom2/sflogo.gif" width="80" height="15" alt="Get Bitcoin at SourceForge.net. Fast, secure and Free Open Source software downloads"/></a>&nbsp;&nbsp;</span></center></p>
</div>
</div></div> <!-- /block-inner, /block -->
</div></div> <!-- /#footer-inner, /#footer -->
</div></div> <!-- /#page-inner, /#page -->
</body>
</html>
docs/web/bitcoin-org/20100106/node/1.html
+227
View File
@@ -0,0 +1,227 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en" dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
<title>FAQ | Bitcoin</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/20091214210829cs_/http://www.bitcoin.org/modules/aggregator/aggregator.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/20091214210829cs_/http://www.bitcoin.org/modules/node/node.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/20091214210829cs_/http://www.bitcoin.org/modules/system/defaults.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/20091214210829cs_/http://www.bitcoin.org/modules/system/system.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/20091214210829cs_/http://www.bitcoin.org/modules/system/system-menus.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/20091214210829cs_/http://www.bitcoin.org/modules/tableofcontents/tableofcontents.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/20091214210829cs_/http://www.bitcoin.org/modules/user/user.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/20091214210829cs_/http://www.bitcoin.org/sites/all/themes/custom3/html-elements.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/20091214210829cs_/http://www.bitcoin.org/sites/all/themes/zen/zen/tabs.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/20091214210829cs_/http://www.bitcoin.org/sites/all/themes/zen/zen/messages.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/20091214210829cs_/http://www.bitcoin.org/sites/all/themes/zen/zen/block-editing.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/20091214210829cs_/http://www.bitcoin.org/sites/all/themes/zen/zen/wireframes.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/20091214210829cs_/http://www.bitcoin.org/sites/all/themes/custom3/layout.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/20091214210829cs_/http://www.bitcoin.org/sites/all/themes/custom3/custom3.css?h"/>
<link type="text/css" rel="stylesheet" media="print" href="https://web.archive.org/web/20091214210829cs_/http://www.bitcoin.org/sites/all/themes/custom3/print.css?h"/>
<!--[if IE]>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/sites/all/themes/zen/zen/ie.css?h" />
<![endif]-->
<script type="text/javascript" src="https://web.archive.org/web/20091214210829js_/http://www.bitcoin.org/misc/jquery.js?h"></script>
<script type="text/javascript" src="https://web.archive.org/web/20091214210829js_/http://www.bitcoin.org/misc/drupal.js?h"></script>
<script type="text/javascript" src="https://web.archive.org/web/20091214210829js_/http://www.bitcoin.org/modules/tableofcontents/jquery.scrollTo-min.js?h"></script>
<script type="text/javascript" src="https://web.archive.org/web/20091214210829js_/http://www.bitcoin.org/modules/tableofcontents/jquery.localscroll-min.js?h"></script>
<script type="text/javascript" src="https://web.archive.org/web/20091214210829js_/http://www.bitcoin.org/modules/tableofcontents/tableofcontents.js?h"></script>
<script type="text/javascript">
<!--//--><![CDATA[//><!--
jQuery.extend(Drupal.settings, { "basePath": "/" });
//--><!]]>
</script>
</head>
<body class="not-front not-logged-in node-type-page one-sidebar sidebar-right page-node-1 section-node">
<div id="page"><div id="page-inner">
<a name="navigation-top" id="navigation-top"></a>
<div id="header"><div id="header-inner" class="clear-block">
<div id="logo-title">
<div id="logo"><a href="/web/20091214210829/http://www.bitcoin.org/" title="Home" rel="home"><img src="https://web.archive.org/web/20091214210829im_/http://www.bitcoin.org/sites/all/themes/custom3/logo.png" alt="Home" id="logo-image"/></a></div>
</div> <!-- /#logo-title -->
</div></div> <!-- /#header-inner, /#header -->
<div id="main"><div id="main-inner" class="clear-block">
<div id="content"><div id="content-inner">
<div id="content-header">
<h1 class="title">FAQ</h1>
</div> <!-- /#content-header -->
<div id="content-area">
<div id="node-1" class="node node-type-page"><div class="node-inner">
<div class="content">
<p class="page-title" style="margin-bottom: 0.5em">FAQ</p>
<script type="text/javascript">toc_collapse=0;</script><div id="toc" class="toc">
<div class="toc-title">Table of contents<span class="toc-toggle-message"> </span></div>
<div class="toc-list">
<ol>
<li class="toc-level-1"><a href="#General_Questions">General Questions</a>
<ol>
<li class="toc-level-2"><a href="#What_is_Bitcoin">What is Bitcoin?</a></li>
<li class="toc-level-2"><a href="#How_does_Bitcoin_work">How does Bitcoin work?</a></li>
<li class="toc-level-2"><a href="#What_is_Bitcoins_value_backed_by">What is Bitcoin’s value backed by?</a></li>
<li class="toc-level-2"><a href="#How_are_new_Bitcoins_created">How are new Bitcoins created?</a></li>
<li class="toc-level-2"><a href="#What-s_the_current_total_amount_of_Bitcoins_in_existence">What's the current total amount of Bitcoins in existence?</a></li>
<li class="toc-level-2"><a href="#What_is_a_block">What is a "block"?</a></li>
<li class="toc-level-2"><a href="#So_your_wealth_is_determined_by_the_amount_of_CPU_power_you_have">So your wealth is determined by the amount of CPU power you have?</a></li>
<li class="toc-level-2"><a href="#Is_Bitcoin_safe">Is Bitcoin safe?</a></li>
<li class="toc-level-2"><a href="#Why_should_I_use_Bitcoin">Why should I use Bitcoin?</a></li>
<li class="toc-level-2"><a href="#Where_can_I_get_Bitcoins">Where can I get Bitcoins?</a></li>
</ol>
<li class="toc-level-1"><a href="#Using_Bitcoin">Using Bitcoin</a>
<ol>
<li class="toc-level-2"><a href="#How_do_I_make_a_transaction">How do I make a transaction?</a></li>
<li class="toc-level-2"><a href="#How_do_I_generate_coins">How do I generate coins?</a></li>
<li class="toc-level-2"><a href="#How_long_does_it_take_to_generate_a_coin">How long does it take to generate a coin?</a></li>
<li class="toc-level-2"><a href="#My_Bitcoin_client_shows_0_connections_wheres_the_problem">My Bitcoin client shows 0 connections, where’s the problem?</a></li>
<li class="toc-level-2"><a href="#How_do_I_open_port_8333">How do I open port 8333?</a></li>
<li class="toc-level-2"><a href="#How_do_I_backup_my_wallet">How do I backup my wallet?</a></li>
<li class="toc-level-2"><a href="#What_does_Generated_not_accepted_in_the_description_bar_mean">What does "Generated (not accepted)" in the description bar mean?</a></li>
</ol>
</li>
</ol>
</div>
</div>
<h2 id="General_Questions">General Questions</h2>
<h3 id="What_is_Bitcoin">What is Bitcoin?</h3>
<p>Bitcoin is a peer-to-peer network based anonymous digital currency. ''Peer-to-peer'' (P2P) means that there is no central authority to issue new money or to keep track of the transactions. Instead, those tasks are managed collectively by the nodes of the network. ''Anonymity'' means that the real world identity of the parties of a transaction can be kept hidden from the public or even from the parties themselves.</p>
<h3 id="How_does_Bitcoin_work">How does Bitcoin work?</h3>
<p>Bitcoin utilizes public/private key cryptography. When a coin is transfered from user A to user B, A adds B’s public key to the coin and signs it with his own private key. Now B owns the coin and can transfer it further. To prevent A from transferring the already used coin to another user C, a public (but anonymous) list of all the previous transactions is collectively maintained by the network of Bitcoin nodes, and before each transaction the coin’s unusedness will be checked.</p>
<p>For details, see the technical paper: <a href="/web/20091214210829/http://www.bitcoin.org/sites/default/files/bitcoin.pdf">Bitcoin: A Peer-to-Peer Electronic Cash System</a>.</p>
<h3 id="What_is_Bitcoins_value_backed_by">What is Bitcoin’s value backed by?</h3>
<p>Bitcoin is valued for the things it can be exchanged to, just like all the traditional paper currencies are.</p>
<p>When the first user publicly announces that he will make a pizza for anyone who gives him enough Bitcoins, then he can use Bitcoins as payment to some extent - as much as people want pizza and trust his announcement. A pizza-eating hairdresser who trusts him as a friend might then announce that she starts accepting Bitcoins as payment for fancy haircuts, and the value of the Bitcoin would be higher - now it would be backed by pizzas ''and'' haircuts. When Bitcoins have become accepted widely enough, he could retire from his pizza business and still be able to use his Bitcoin-savings.</p>
<p>Currently, Bitcoin is in beta development stage, and some new features need to be implemented before the system is well suited for real use. The system already works on the basic level, though, and you can trade with it if you want to.</p>
<p>You can buy and sell Bitcoins with PayPal at <a href="https://web.archive.org/web/20091214210829/http://newlibertystandard.wetpaint.com/">NewLibertyStandard's Exchange Service</a>.</p>
<h3 id="How_are_new_Bitcoins_created">How are new Bitcoins created?</h3>
<p>New coins are generated by a network node each time it finds the solution to a certain calculational problem (i.e. creates a new <a href="#What_is_a_block">block</a>), for which an average solution time can be calculated. The difficulty of the problem is adjusted so that in the first 4 years of the Bitcoin network, 10,500,000 coins will be created. The amount is halved each 4 years, so it will be 5,250,000 in years 4-8, 2,625,000 in years 8-12 and so on. Thus the total number of coins will approach 21,000,000 over time.</p>
<h3 id="What-s_the_current_total_amount_of_Bitcoins_in_existence">What's the current total amount of Bitcoins in existence?</h3>
<p>The number of blocks times the coin value of a block. The coin value is 50 bc per block for the first 210,000 blocks, 25 bc for the next 210,000 blocks, then 12.5 bc, 7.25 bc and so on.</p>
<p>As of October 30th 2009, there are about 26,000 blocks in the block chain, which means 26,000 * 50 bc = 1,300,000 bitcoins in existence. You can see the up-to-date number of blocks in the status bar of the Bitcoin main window.</p>
<h3 id="What_is_a_block">What is a "block"?</h3>
<p>A block is a unit which contains the information of the transactions made after the previous block, plus a transaction which assigns a new coin to the creator of the block. Blocks form a chain from the first block to the latest block. To create a new block you need to spend CPU time, which acts as an unbribable timestamp for the previous transactions. The average rate of block creation in the whole system is 6 / hour. For details, see the technical paper: <a href="/web/20091214210829/http://www.bitcoin.org/sites/default/files/bitcoin.pdf">Bitcoin: A Peer-to-Peer Electronic Cash System</a>.</p>
<p>The block chain length is shown in the status bar of the Bitcoin main window. The number increases rapidly while your Bitcoin client is downloading the block chain from other nodes. After the downloading is finished, your node can start generating new blocks.</p>
<h3 id="So_your_wealth_is_determined_by_the_amount_of_CPU_power_you_have">So your wealth is determined by the amount of CPU power you have?</h3>
<p>No. There's a constant average rate of new Bitcoins created, and that amount is divided among the nodes by the CPU power they use. When Bitcoins start having real exchange value, the competition for coin creation will drive the price of electricity needed for generating a coin close to the value of the coin, so the profit margin won't be that huge. The easier way to gain a lot of wealth would be trading goods.</p>
<p>At the moment, though, you can generate new coins quite profitably, if you expect them to have real value in the future. If you choose to, be aware that Bitcoin is still experimental software.</p>
<h3 id="Is_Bitcoin_safe">Is Bitcoin safe?</h3>
<p>Yes, as long as you make backups of your Bitcoin wallet, protect it with a strong password and keep keyloggers away from your computer.</p>
<p>If you lose your wallet or if some unknown attacker gets it and manages to break your password, there’s no way to get your coins back. On the other hand, that is usually also the case if you lose your physical wallet.</p>
<h3 id="Why_should_I_use_Bitcoin">Why should I use Bitcoin?</h3>
<ul>
<li>Transfer money easily through the internet, without having to trust third parties.</li>
<li>Third parties can’t prevent or control your transactions.</li>
<li>Be safe from the instability caused by fractional reserve banking and bad policies of the central banks. The limited inflation of the Bitcoin system’s money supply is distributed evenly (by CPU power) throughout the network, not monopolized to the banks.</li>
</ul>
<h3 id="Where_can_I_get_Bitcoins">Where can I get Bitcoins?</h3>
<p>Find a Bitcoin owner and sell her something - MMORPG equipment, IT support, lawn mowing, dollars or whatever you can trade with her. You can also generate new Bitcoins for yourself by running a Bitcoin network node.</p>
<p>You can buy and sell Bitcoins with PayPal at <a href="https://web.archive.org/web/20091214210829/http://newlibertystandard.wetpaint.com/">NewLibertyStandard's Exchange Service</a>.</p>
<h2 id="Using_Bitcoin">Using Bitcoin</h2>
<h3 id="How_do_I_make_a_transaction">How do I make a transaction?</h3>
<p>When you want to send coins, click the ''Send Coins'' button up in the main window. You can send coins to the recipient's IP address if he's running the Bitcoin client, or to his Bitcoin address even if he's not online or doesn't want to reveal his IP. A comment can be included when sending to an IP.</p>
<p>If you're receiving a valuable amount of coins from a sender whom you can't be sure to trust, before accepting the transaction you may want to wait until it's verified by a few blocks. The more blocks you wait, the closer to zero is the sender's chance to successfully double-spend the coins sent to you. The amount of blocks after the transaction is shown in the ''Status'' column of the transaction list in the main window.</p>
<h3 id="How_do_I_generate_coins">How do I generate coins?</h3>
<p>Turn on ''Options -&gt; Generate Coins'' to run a node and generate new coins. Be sure to have port 8333 open for incoming connections (<a href="#How_do_I_open_port_8333">instructions</a>).</p>
<h3 id="How_long_does_it_take_to_generate_a_coin">How long does it take to generate a coin?</h3>
<p>Initially your Bitcoin client will have to download and verify the Bitcoin block chain, which is indicated by the number of blocks (shown in the status bar) increasing rapidly. On a modern PC that might take a few hours, after which it will start generating coins.</p>
<p>Your average coin creation rate will be (6 * 50 coins / hour) * (your CPU speed / the total CPU speed in the system). At the moment (October 2009) it might be something like 500 coins / day, for example.</p>
<h3 id="My_Bitcoin_client_shows_0_connections_wheres_the_problem">My Bitcoin client shows 0 connections, where’s the problem?</h3>
<p>That could happen if port 8333 is not open for incoming connections (<a href="#How_do_I_open_port_8333">instructions</a>).</p>
<h3 id="How_do_I_open_port_8333">How do I open port 8333?</h3>
<p>If you’re behind a firewall, it will usually ask if you want to allow incoming connections to an application when running it for the first time. If you’re also behind NAT, see <a href="https://web.archive.org/web/20091214210829/http://www.portforward.com/">www.portforward.com</a> for instructions how to forward the port correctly. Select your router from the list and see its Default Guide.</p>
<p>Use <a href="https://web.archive.org/web/20091214210829/http://www.canyouseeme.org/">www.canyouseeme.org</a> to check if the port is accepting incoming connections.</p>
<h3 id="How_do_I_backup_my_wallet">How do I backup my wallet?</h3>
<p>Your data is stored in the directory ''%appdata%\Bitcoin'', which is typically:</p>
<p>&nbsp;Windows XP:<br/>
&nbsp;&nbsp;&nbsp;C:\Documents and Settings\<i>username</i>\Application Data\Bitcoin<br/>
&nbsp;Windows Vista:<br/>
&nbsp;&nbsp;&nbsp;C:\Users\<i>username</i>\AppData\Roaming\Bitcoin</p>
<p>It’s recommended that you stop Bitcoin before backing it up to make sure the backup will be correct.</p>
<p>If you want to encrypt your backup, you can use some program like <a href="https://web.archive.org/web/20091214210829/http://www.truecrypt.org/">TrueCrypt</a>. An in-built tool for encrypting your wallet will be included in Bitcoin later on.</p>
<h3 id="What_does_Generated_not_accepted_in_the_description_bar_mean">What does "Generated (not accepted)" in the description bar mean?</h3>
<p>It implies that your computer and another node created a new block at close to the same time, and your block was rejected for being broadcast later than the one from the other node. It's normal and unavoidable.</p>
</div>
</div></div> <!-- /node-inner, /node -->
</div>
</div></div> <!-- /#content-inner, /#content -->
<div id="sidebar-right"><div id="sidebar-right-inner" class="region region-right">
<div id="block-menu-primary-links" class="block block-menu region-odd odd region-count-1 count-1"><div class="block-inner">
<h2 class="title">Primary links</h2>
<div class="content">
<ul class="menu"><li class="leaf first"><a href="https://web.archive.org/web/20091214210829/http://www.bitcoin.org/" title="">Home</a></li>
<li class="leaf active-trail"><a href="node/1" title="FAQ" class="active">FAQ</a></li>
<li class="leaf"><a href="https://web.archive.org/web/20091214210829/http://www.bitcoin.org/smf/" title="">Forum</a></li>
<li class="leaf last"><a href="node/2" title="Contact">Contact</a></li>
</ul> </div>
</div></div> <!-- /block-inner, /block -->
<div id="block-block-1" class="block block-block region-even even region-count-2 count-2"><div class="block-inner">
<div class="content">
<p><a href="https://web.archive.org/web/20091214210829/http://sourceforge.net/project/downloading.php?group_id=244765&amp;filename=bitcoin-0.1.5.rar"><img src="https://web.archive.org/web/20091214210829im_/http://www.bitcoin.org/sites/default/files/images/download_arrow.png" width="21" height="22" style="float: left; margin-right: 0.45em; margin-top: 0.56em;"/> Download<br/>Bitcoin 0.1.5</a><br/>
For Windows <span style="font-weight: normal;">(2.1MB)</span></p>
</div>
</div></div> <!-- /block-inner, /block -->
</div></div> <!-- /#sidebar-right-inner, /#sidebar-right -->
</div></div> <!-- /#main-inner, /#main -->
<div id="footer"><div id="footer-inner" class="region region-footer">
<div id="block-block-3" class="block block-block region-odd odd region-count-1 count-3"><div class="block-inner">
<div class="content">
<p><center><span class="footer"><a class="sflogo" href="https://web.archive.org/web/20091214210829/http://sourceforge.net/projects/bitcoin"><img src="https://web.archive.org/web/20091214210829im_/http://www.bitcoin.org/sites/all/themes/custom2/sflogo.gif" width="80" height="15" alt="Get Bitcoin at SourceForge.net. Fast, secure and Free Open Source software downloads"/></a>&nbsp;&nbsp;</span></center></p>
</div>
</div></div> <!-- /block-inner, /block -->
</div></div> <!-- /#footer-inner, /#footer -->
</div></div> <!-- /#page-inner, /#page -->
</body>
</html>
docs/web/bitcoin-org/20100106/node/2.html
+145
View File
@@ -0,0 +1,145 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en" dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
<title>Contact | Bitcoin</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/20091219013554cs_/http://www.bitcoin.org/modules/aggregator/aggregator.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/20091219013554cs_/http://www.bitcoin.org/modules/node/node.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/20091219013554cs_/http://www.bitcoin.org/modules/system/defaults.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="v/web/20091219013554cs_/http://www.bitcoin.org/modules/system/system.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/20091219013554cs_/http://www.bitcoin.org/modules/system/system-menus.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/20091219013554cs_/http://www.bitcoin.org/modules/tableofcontents/tableofcontents.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/20091219013554cs_/http://www.bitcoin.org/modules/user/user.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/20091219013554cs_/http://www.bitcoin.org/sites/all/themes/custom3/html-elements.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/20091219013554cs_/http://www.bitcoin.org/sites/all/themes/zen/zen/tabs.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/20091219013554cs_/http://www.bitcoin.org/sites/all/themes/zen/zen/messages.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/20091219013554cs_/http://www.bitcoin.org/sites/all/themes/zen/zen/block-editing.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/20091219013554cs_/http://www.bitcoin.org/sites/all/themes/zen/zen/wireframes.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/20091219013554cs_/http://www.bitcoin.org/sites/all/themes/custom3/layout.css?h"/>
<link type="text/css" rel="stylesheet" media="all" href="https://web.archive.org/web/20091219013554cs_/http://www.bitcoin.org/sites/all/themes/custom3/custom3.css?h"/>
<link type="text/css" rel="stylesheet" media="print" href="https://web.archive.org/web/20091219013554cs_/http://www.bitcoin.org/sites/all/themes/custom3/print.css?h"/>
<!--[if IE]>
<link type="text/css" rel="stylesheet" media="all" href="/sites/all/themes/zen/zen/ie.css?h" />
<![endif]-->
<script type="text/javascript" src="https://web.archive.org/web/20091219013554js_/http://www.bitcoin.org/misc/jquery.js?h"></script>
<script type="text/javascript" src="https://web.archive.org/web/20091219013554js_/http://www.bitcoin.org/misc/drupal.js?h"></script>
<script type="text/javascript" src="https://web.archive.org/web/20091219013554js_/http://www.bitcoin.org/modules/tableofcontents/jquery.scrollTo-min.js?h"></script>
<script type="text/javascript" src="https://web.archive.org/web/20091219013554js_/http://www.bitcoin.org/modules/tableofcontents/jquery.localscroll-min.js?h"></script>
<script type="text/javascript" src="https://web.archive.org/web/20091219013554js_/http://www.bitcoin.org/modules/tableofcontents/tableofcontents.js?h"></script>
<script type="text/javascript">
<!--//--><![CDATA[//><!--
jQuery.extend(Drupal.settings, { "basePath": "/" });
//--><!]]>
</script>
</head>
<body class="not-front not-logged-in node-type-page one-sidebar sidebar-right page-node-2 section-node">
<div id="page"><div id="page-inner">
<a name="navigation-top" id="navigation-top"></a>
<div id="header"><div id="header-inner" class="clear-block">
<div id="logo-title">
<div id="logo"><a href="https://web.archive.org/web/20091219013554/http://www.bitcoin.org/" title="Home" rel="home"><img src="/web/20091219013554im_/http://www.bitcoin.org/sites/all/themes/custom3/logo.png" alt="Home" id="logo-image"/></a></div>
</div> <!-- /#logo-title -->
</div></div> <!-- /#header-inner, /#header -->
<div id="main"><div id="main-inner" class="clear-block">
<div id="content"><div id="content-inner">
<div id="content-header">
<h1 class="title">Contact</h1>
</div> <!-- /#content-header -->
<div id="content-area">
<div id="node-2" class="node node-type-page"><div class="node-inner">
<div class="content">
<h2 class="page-title">Contact</h2>
<ul>
<li>Post on the <a href="https://web.archive.org/web/20091219013554/http://www.bitcoin.org/smf">Forum</a></li>
<li>Join #bitcoin-dev on the <a href="https://web.archive.org/web/20091219013554/http://freenode.net/">FreeNode</a> IRC network</li>
<li>E-mail the project manager at <img src="/web/20091219013554im_/http://www.bitcoin.org/sites/default/files/medium.png" style="vertical-align: middle; margin-left: 1px; margin-top: -2px;"/></li>
</ul>
</div>
</div></div> <!-- /node-inner, /node -->
</div>
</div></div> <!-- /#content-inner, /#content -->
<div id="sidebar-right"><div id="sidebar-right-inner" class="region region-right">
<div id="block-menu-primary-links" class="block block-menu region-odd odd region-count-1 count-1"><div class="block-inner">
<h2 class="title">Primary links</h2>
<div class="content">
<ul class="menu"><li class="leaf first"><a href="https://web.archive.org/web/20091219013554/http://www.bitcoin.org/" title="">Home</a></li>
<li class="leaf"><a href="https://web.archive.org/web/20091219013554/http://www.bitcoin.org/node/1" title="FAQ">FAQ</a></li>
<li class="leaf"><a href="https://web.archive.org/web/20091219013554/http://www.bitcoin.org/smf/" title="">Forum</a></li>
<li class="leaf last active-trail"><a href="https://web.archive.org/web/20091219013554/http://www.bitcoin.org/node/2" title="Contact" class="active">Contact</a></li>
</ul> </div>
</div></div> <!-- /block-inner, /block -->
<div id="block-block-1" class="block block-block region-even even region-count-2 count-2"><div class="block-inner">
<h2 class="title">Download Bitcoin</h2>
<div class="content">
<p><img src="https://web.archive.org/web/20091219013554im_/http://www.bitcoin.org/sites/default/files/images/download_arrow.png" width="21" height="22" style="float: left; margin-right: 0.45em; margin-top: 0.56em;"/>Download<br/>Bitcoin 0.2</p>
<p><a href="https://web.archive.org/web/20091219013554/http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.2.0-win32-setup.exe/download">Windows (exe)</a> 3.1MB<br/>
<a href="https://web.archive.org/web/20091219013554/http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.2.0-win32.zip/download">Windows (zip)</a> 3.1MB<br/>
<a href="https://web.archive.org/web/20091219013554/http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.2.0-linux.tar.gz/download">Linux</a> 2.4MB</p>
</div>
</div></div> <!-- /block-inner, /block -->
</div></div> <!-- /#sidebar-right-inner, /#sidebar-right -->
</div></div> <!-- /#main-inner, /#main -->
<div id="footer"><div id="footer-inner" class="region region-footer">
<div id="block-block-3" class="block block-block region-odd odd region-count-1 count-3"><div class="block-inner">
<div class="content">
<p><center><span class="footer"><a class="sflogo" href="https://web.archive.org/web/20091219013554/http://sourceforge.net/projects/bitcoin"><img src="/web/20091219013554im_/http://www.bitcoin.org/sites/all/themes/custom2/sflogo.gif" width="80" height="15" alt="Get Bitcoin at SourceForge.net. Fast, secure and Free Open Source software downloads"/></a>&nbsp;&nbsp;</span></center></p>
</div>
</div></div> <!-- /block-inner, /block -->
</div></div> <!-- /#footer-inner, /#footer -->
</div></div> <!-- /#page-inner, /#page -->
</body>
</html>