|
|
| (One intermediate revision by the same user not shown) |
| Line 1: |
Line 1: |
| ;'''Bitcoin'''
| | #redirect [[Vocabulary]] |
| : The name of a decentralized p2p crypto-currency application.
| |
| ;'''[[Bitcoins]]'''
| |
| : The currency used and generated within the Bitcoin system.
| |
| ;'''[[Block]]'''
| |
| : Blocks are links in a chain of transaction verifications. Outstanding transactions get bundled into a block and are verified roughly every ten minutes on average. Each subsequent block strengthens the verification of previous blocks. Each block contains one or more transactions.
| |
| ;'''[[Block Chain]]'''
| |
| : Each block includes the difficult-to-produce verification hash of the previous block. This allows each subsequent block to be linked to all previous blocks. These blocks which are linked together for the purpose of verifying transactions within blocks is called the block chain.
| |
| ;'''Branching Point'''
| |
| : The block at which the block chain diverges into multiple chain branches
| |
| ;'''BTC'''
| |
| : The common decimal [[Units|unit]] of Bitcoins, equal to 100,000,000 satoshis.
| |
| ;'''Chain Branching'''
| |
| ;'''Checkpoint Lockin'''
| |
| : Every once in a while, a recent block hash is hardcoded into Bitcoin. This prevents pretty much any possible attack from affecting transactions made up to this point. No matter what happens (except perhaps if SHA-256 is broken), these transactions will survive. Satoshi announced the feature [http://www.bitcoin.org/smf/index.php?topic=437 here](broken link) and it was discussed to death [http://www.bitcoin.org/smf/index.php?topic=1647 here] (broken link).
| |
| ;'''Coinbase'''
| |
| : "Coinbase" is another name for a generation transaction. The input of such a transaction contains some arbitrary data where the scriptSig would go in normal transactions -- this data is sometimes called the "coinbase", as well.
| |
| ;'''[[Confirmation]]'''
| |
| : To protect against double spending, a transaction should not be considered as "confirmed" until a certain number of blocks in the block chain confirm, or verify that the transaction. The classic bitcoin client will show a transaction as "n/unconfirmed" until 6 blocks confirm the transaction.
| |
| ;'''[[Difficulty]]'''
| |
| : Every 2016 blocks, Bitcoin adjusts the difficulty of verifying blocks based on the time it took to verify the previous 2016 blocks. The difficulty is adjusted so that given the average estimated computing power of the whole bitcoin network, only one block will verified on average every ten minutes for the next 2016 blocks. The difficulty is usually expressed as a number, optionally accurate to many decimal places (eg. in [http://blockexplorer.com/b/100000 block 100,000] it was 14,484.162361. The difficulty is inversely proportional to the hash target, which is expressed as a hex number with around 50 digits, and is the number under which a block's generated hash must be to qualify as an officially verified block. The hash target is equal to ((65535 << 208) / difficulty). Difficulty is also often called block difficulty, hash difficulty, verification difficulty or the difficulty of generating bitcoins.
| |
| ;'''Double Spending'''
| |
| : Attempting to spend coins that have already been spent in another transaction
| |
| ;'''Generate Bitcoins'''
| |
| : When a Bitcoin miner finds a block, it receives newly minted bitcoins and the transaction fees which may or may not be included in the block. The amount of bitcoins awarded for verifying a block is 50 BTC for the first 210,000 blocks and half the previous amount of bitcoins for each subsequent 210,000 blocks. On average, 210,000 blocks take about 4 years to verify. The total amount of bitcoins that will ever be minted is roughly 21,000,000 BTC.
| |
| ;'''[[Hash]]'''
| |
| : A computer algorithm which produces an identification key that can be used to easily verify that data has not been altered. If you change any single bit of the original data and run the hash algorithm, the hash will completely change. Because the hash is seemingly random, it is prohibitively difficult to try to produce a specific hash by changing the data which is being hashed.
| |
| ;'''Low Priority'''
| |
| : See Priority.
| |
| ;'''Memory pool'''
| |
| : Generators store [[transactions]] waiting to get into a block in their memory pool after receiving them. Received transactions are stored even if they are invalid to prevent nodes from constantly requesting transactions that they've already seen. The memory pool is cleared when Bitcoin is shut down, causing the [[network]] to gradually forget about transactions that haven't been included in a [[block]].
| |
| ;'''Merkle root'''
| |
| : Every [[transactions|transaction]] has a [[hash]] associated with it. In a [[block]], all of the transaction hashes in the block are themselves hashed (sometimes several times -- the exact process is complex), and the result is the Merkle root. In other words, the Merkle root is the hash of all the hashes of all the transactions in the block. The Merkle root is included in the [[block hashing algorithm|block header]]. With this scheme, it is possible to securely verify that a transaction has been accepted by the network (and get the number of confirmations) by downloading just the tiny block headers and [[Wikipedia:Merkle tree|Merkle tree]] -- downloading the entire block chain is unnecessary. This feature is currently not used in Bitcoin, but it will be in the future.
| |
| ;''' Miner'''
| |
| : Computer software which is designed to repeatedly calculate hashes with the intention to create a successful block and earn coins from transaction fees and new coins created with the block itself. The term references an analogy of gold miners who dig gold out of the ground and thus "discover" new gold that can be used to create new coins with a similar kind of discovery occurring with a successful hash to create new Bitcoins.
| |
| ;'''Node'''
| |
| : Each Bitcoin client currently running within the network is referred to as a Node of the system.
| |
| ;'''Nonce'''
| |
| : A nonce is an otherwise meaningless number which is used to alter the outcome of a hash. Each time Bitcoin hashes a block, it increments a nonce within the block which it is trying verify. If the numeric value of the effectively random hash is below a certain amount determined by the block generation difficulty, then the block is accepted by other clients and gets added to the chain.
| |
| ;'''Orphan block'''
| |
| : An orphan block is a block that is not in the currently-longest [[block chain]].
| |
| ;'''Priority'''
| |
| : A scoring mechanism to help ensure that expensive data storage isn't consumed by lower quality and spam. Low priority transactions will not get included by a miner if the limited space is already filled by higher priority transactions. A [[Transaction Fee|transaction fee]] will affect priority.
| |
| ;'''[[Proof of work]]'''
| |
| : A result that can only be obtained through the use of computational resources. Changing the data in the proof of work requires redoing the work.
| |
| ;'''Reorganize'''
| |
| : A block chain reorganize (or '''reorg''') happens when one chain becomes longer than the one you are currently working on. All of the blocks in the old chain that are not in the new one become orphan blocks, and their generations are invalidated. Transactions that use the newly-invalid generated coins also become invalid, though this is only possible in large chain splits because generations can't be spent for 100 blocks. The number of confirmations for transactions may change after a reorg, and transactions that are not in the new chain will become "0/unconfirmed" again. If a transaction in the old chain conflicts with one in the new chain (as a result of double-spending), the old one becomes invalid.
| |
| ;'''Satoshi'''
| |
| : The base unit of Bitcoin (0.00000001 BTC) is sometimes called a Satoshi, after Bitcoin's creator Satoshi Nakamoto.
| |
| ;'''Seed Nodes'''
| |
| : Nodes whose IP addresses are included in the [[Original Bitcoin client|Bitcoin client]] for use during a new installation when the normal bootstrapping process through IRC wasn't possible.
| |
| ;'''Subsidy'''
| |
| : The block subsidy is the BTC created for generating a block. The subsidy is halved every four years.
| |
| ;'''Super Nodes'''
| |
| : A participant in a p2p network which connects to as many other nodes as possible.
| |
| ;'''[[Transaction Fee]]'''
| |
| : A voluntary fee which can be added to a transaction which is used as an incentive to add the bitcoin transaction to a block. The fee determines the likelihood of inclusion in any given block, where a high fee included with a transaction has a priority over transactions with a lower fee included or no fee at all.
| |
| ;'''Virgin bitcoin'''
| |
| : The reward for generating a [[Block|block]] that has not yet been spent, a state which might increase the ability to transact [[anonymity|anonymously]].
| |
| | |
| [[Category:Technical]]
| |
| [[Category:Vocabulary| ]]
| |