51 percent attackThe ability of someone controlling a majority of network hash rate to revise transaction history and prevent new transactions from confirming.
#
The ability of someone controlling a majority of network hash rate to revise transaction history and prevent new transactions from confirming.
Majority attackThe ability of someone controlling a majority of network hash rate to revise transaction history and prevent new transactions from confirming.
#
The ability of someone controlling a majority of network hash rate to revise transaction history and prevent new transactions from confirming.
The ability of someone controlling a majority of network hash rate to revise transaction history and prevent new transactions from confirming.
AddressA 20-byte hash formatted using base58check to produce either a P2PKH or P2SH Bitcoin address. Currently the most common way users exchange payment information.
Not to be confused with: IP address
#
A 20-byte hash formatted using base58check to produce either a P2PKH or P2SH Bitcoin address. Currently the most common way users exchange payment information.
Not to be confused with: IP address
A 20-byte hash formatted using Base58check The method used in Bitcoin for converting 160-bit hashes into P2PKH and P2SH addresses. Also used in other parts of Bitcoin, such as encoding private keys for backup in WIP format. Not the same as other base58 implementations. Not to be confused with: P2PKH address, P2SH address, IP address
A 20-byte hash formatted using base58check to produce either a P2PKH or P2SH Bitcoin address. Currently the most common way users exchange payment information.
Not to be confused with: IP address
Not to be confused with: IP Address A 20-byte hash formatted using base58check to produce either a P2PKH or P2SH Bitcoin address. Currently the most common way users exchange payment information. Not to be confused with: IP address
Base58checkThe method used in Bitcoin for converting 160-bit hashes into P2PKH and P2SH addresses. Also used in other parts of Bitcoin, such as encoding private keys for backup in WIP format. Not the same as other base58 implementations.
Not to be confused with: P2PKH address, P2SH address, IP address
#
The method used in Bitcoin for converting 160-bit hashes into P2PKH and P2SH addresses. Also used in other parts of Bitcoin, such as encoding private keys for backup in WIP format. Not the same as other base58 implementations.
Not to be confused with: P2PKH address, P2SH address, IP address
The method used in Bitcoin for converting 160-bit hashes into P2PKH and P2SH addresses. Also used in other parts of Bitcoin, such as encoding private keys for backup in WIP format. Not the same as other base58 implementations.
Not to be confused with: P2PKH Address A 20-byte hash formatted using base58check to produce either a P2PKH or P2SH Bitcoin address. Currently the most common way users exchange payment information. Not to be confused with: IP address
A 20-byte hash formatted using base58check to produce either a P2PKH or P2SH Bitcoin address. Currently the most common way users exchange payment information.
Not to be confused with: IP address
A 20-byte hash formatted using base58check to produce either a P2PKH or P2SH Bitcoin address. Currently the most common way users exchange payment information.
Not to be confused with: IP address
BlockOne or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
#
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
One or more transactions prefaced by a Block One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
An 80-byte header belonging to a single block which is hashed repeatedly to create proof of work.
A hash below a target value which can only be obtained, on average, by performing a certain amount of brute force work—therefore demonstrating proof of work.
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
BlockOne or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
chain #
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
Best block chainA chain of blocks with each block referencing the block that preceded it. The most-difficult-to-recreate chain is the best block chain.
Not to be confused with: Header chain
#
A chain of blocks with each block referencing the block that preceded it. The most-difficult-to-recreate chain is the best block chain.
Not to be confused with: Header chain
A chain of blocks with each Block One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
A chain of blocks with each block referencing the block that preceded it. The most-difficult-to-recreate chain is the best block chain.
Not to be confused with: Header chain
Not to be confused with: Header An 80-byte header belonging to a single block which is hashed repeatedly to create proof of work.
BlockOne or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
HeaderAn 80-byte header belonging to a single block which is hashed repeatedly to create proof of work.
#
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
An 80-byte header belonging to a single block which is hashed repeatedly to create proof of work.
HeaderAn 80-byte header belonging to a single block which is hashed repeatedly to create proof of work.
#
An 80-byte header belonging to a single block which is hashed repeatedly to create proof of work.
An 80-byte Header An 80-byte header belonging to a single block which is hashed repeatedly to create proof of work.
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
A hash below a target value which can only be obtained, on average, by performing a certain amount of brute force work—therefore demonstrating proof of work.
HeightThe number of blocks preceding a particular block on a block chain. For example, the genesis block has a height of zero because zero block preceded it.
#
The number of blocks preceding a particular block on a block chain. For example, the genesis block has a height of zero because zero block preceded it.
BlockOne or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
HeightThe number of blocks preceding a particular block on a block chain. For example, the genesis block has a height of zero because zero block preceded it.
#
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
The number of blocks preceding a particular block on a block chain. For example, the genesis block has a height of zero because zero block preceded it.
The number of blocks preceding a particular Block One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
The number of blocks preceding a particular block on a block chain. For example, the genesis block has a height of zero because zero block preceded it.
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
BlockOne or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
reward #
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
The amount that miners may claim as a reward for creating a Block One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
Denominations of Bitcoin value, usually measured in fractions of a bitcoin but sometimes measured in multiples of a satoshi. One bitcoin equals 100,000,000 satoshis.
Not to be confused with: Binary bits, a unit of data with two possible values
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
Not to be confused with: Block One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
Maximum BlockOne or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
Size #
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
The maximum size of a Block One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
When several nodes (usually most nodes on the network) all have the same blocks in their locally-validated best block chain.
Not to be confused with: Social consensus (often used in discussion among developers to indicate that most people agree with a particular plan), Consensus rules (the rules that allow nodes to maintain consensus)
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
Not to be confused with: Block One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
Blocks-first syncSynchronizing the block chain by downloading each block from a peer and then validating it.
Not to be confused with: Headers-first sync
#
Synchronizing the block chain by downloading each block from a peer and then validating it.
Not to be confused with: Headers-first sync
Synchronizing the Block One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
A computer that connects to the Bitcoin network.
Not to be confused with: Lightweight node, SPV node
Not to be confused with: Headers-first sync Synchronizing the block chain by downloading block headers before downloading the full blocks. Not to be confused with: Blocks-first sync (Downloading entire blocks immediately without first getting their headers)
Bloom filterA filter used primarily by SPV clients to request only matching transactions and merkle blocks from full nodes.
Not to be confused with: Bloom filter (general computer science term, of which Bitcoin’s bloom filters are a specific implementation)
#
A filter used primarily by SPV clients to request only matching transactions and merkle blocks from full nodes.
Not to be confused with: Bloom filter (general computer science term, of which Bitcoin’s bloom filters are a specific implementation)
A filter used primarily by SPV A method for verifying if particular transactions are included in a block without downloading the entire block. The method is used by some lightweight Bitcoin clients.
Not to be confused with: Bloom filter A filter used primarily by SPV clients to request only matching transactions and merkle blocks from full nodes. Not to be confused with: Bloom filter (general computer science term, of which Bitcoin’s bloom filters are a specific implementation)
Chain codeIn HD wallets, 256 bits of entropy added to the public and private keys to help them generate secure child keys; the master chain code is usually derived from a seed along with the master private key
#
In HD wallets, 256 bits of entropy added to the public and private keys to help them generate secure child keys; the master chain code is usually derived from a seed along with the master private key
In HD wallets, 256 bits of entropy added to the public and private keys to help them generate secure child keys; the master Chain code In HD wallets, 256 bits of entropy added to the public and private keys to help them generate secure child keys; the master chain code is usually derived from a seed along with the master private key
In HD wallets, the master chain code and master private key are the two pieces of data derived from the root seed.
Change AddressA 20-byte hash formatted using base58check to produce either a P2PKH or P2SH Bitcoin address. Currently the most common way users exchange payment information.
Not to be confused with: IP address
#
A 20-byte hash formatted using base58check to produce either a P2PKH or P2SH Bitcoin address. Currently the most common way users exchange payment information.
Not to be confused with: IP address
Change outputAn output in a transaction which returns satoshis to the spender, thus preventing too much of the input value from going to transaction fees.
Not to be confused with: Address reuse
#
An output in a transaction which returns satoshis to the spender, thus preventing too much of the input value from going to transaction fees.
Not to be confused with: Address reuse
An Output An output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent. Not to be confused with: Outpoint (a reference to a particular output)
Denominations of Bitcoin value, usually measured in fractions of a bitcoin but sometimes measured in multiples of a satoshi. One bitcoin equals 100,000,000 satoshis.
Not to be confused with: Binary bits, a unit of data with two possible values
An input in a transaction which contains three fields: an outpoint, a signature script, and a sequence number. The outpoint references a previous output and the signature script allows spending it.
Not to be confused with: Address A 20-byte hash formatted using base58check to produce either a P2PKH or P2SH Bitcoin address. Currently the most common way users exchange payment information. Not to be confused with: IP address
Child keyIn HD wallets, a key derived from a parent key. The key can be either a private key or a public key, and the key derivation may also require a chain code.
Not to be confused with: Public key (derived from a private key, not a parent key)
#
In HD wallets, a key derived from a parent key. The key can be either a private key or a public key, and the key derivation may also require a chain code.
Not to be confused with: Public key (derived from a private key, not a parent key)
Child public keyIn HD wallets, a key derived from a parent key. The key can be either a private key or a public key, and the key derivation may also require a chain code.
Not to be confused with: Public key (derived from a private key, not a parent key)
#
In HD wallets, a key derived from a parent key. The key can be either a private key or a public key, and the key derivation may also require a chain code.
Not to be confused with: Public key (derived from a private key, not a parent key)
Child private keyIn HD wallets, a key derived from a parent key. The key can be either a private key or a public key, and the key derivation may also require a chain code.
Not to be confused with: Public key (derived from a private key, not a parent key)
#
In HD wallets, a key derived from a parent key. The key can be either a private key or a public key, and the key derivation may also require a chain code.
Not to be confused with: Public key (derived from a private key, not a parent key)
In HD wallets, a key derived from a Parent key In HD wallets, a key used to derive child keys. The key can be either a private key or a public key, and the key derivation may also require a chain code. Not to be confused with: Public key (derived from a private key, not a parent key)
The private portion of a keypair which can create signatures that other people can verify using the public key.
Not to be confused with: Public key (data derived from the private key), Parent key (a key used to create child keys, not necessarily a private key)
The public portion of a keypair which can be used to verify signatures made with the private portion of the keypair.
Not to be confused with: Private key (data from which the public key is derived), Parent key (a key used to create child keys, not necessarily a public key)
In HD wallets, 256 bits of entropy added to the public and private keys to help them generate secure child keys; the master chain code is usually derived from a seed along with the master private key
Not to be confused with: Public key The public portion of a keypair which can be used to verify signatures made with the private portion of the keypair. Not to be confused with: Private key (data from which the public key is derived), Parent key (a key used to create child keys, not necessarily a public key)
The private portion of a keypair which can create signatures that other people can verify using the public key.
Not to be confused with: Public key (data derived from the private key), Parent key (a key used to create child keys, not necessarily a private key)
In HD wallets, a key used to derive child keys. The key can be either a private key or a public key, and the key derivation may also require a chain code.
Not to be confused with: Public key (derived from a private key, not a parent key)
CoinbaseA special field used as the sole input for coinbase transactions. The coinbase allows claiming the block reward and provides up to 100 bytes for arbitrary data.
Not to be confused with: Coinbase transaction, Coinbase.com
#
A special field used as the sole input for coinbase transactions. The coinbase allows claiming the block reward and provides up to 100 bytes for arbitrary data.
Not to be confused with: Coinbase transaction, Coinbase.com
A special field used as the sole Input An input in a transaction which contains three fields: an outpoint, a signature script, and a sequence number. The outpoint references a previous output and the signature script allows spending it.
A special field used as the sole input for coinbase transactions. The coinbase allows claiming the block reward and provides up to 100 bytes for arbitrary data.
Not to be confused with: Coinbase transaction, Coinbase.com
A special field used as the sole input for coinbase transactions. The coinbase allows claiming the block reward and provides up to 100 bytes for arbitrary data.
Not to be confused with: Coinbase transaction, Coinbase.com
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
Not to be confused with: Coinbase A special field used as the sole input for coinbase transactions. The coinbase allows claiming the block reward and provides up to 100 bytes for arbitrary data. Not to be confused with: Coinbase transaction, Coinbase.com
A special field used as the sole input for coinbase transactions. The coinbase allows claiming the block reward and provides up to 100 bytes for arbitrary data.
Not to be confused with: Coinbase transaction, Coinbase.com
CoinbaseA special field used as the sole input for coinbase transactions. The coinbase allows claiming the block reward and provides up to 100 bytes for arbitrary data.
Not to be confused with: Coinbase transaction, Coinbase.com
transaction #
A special field used as the sole input for coinbase transactions. The coinbase allows claiming the block reward and provides up to 100 bytes for arbitrary data.
Not to be confused with: Coinbase transaction, Coinbase.com
Generation transactionThe first transaction in a block. Always created by a miner, it includes a single coinbase.
Not to be confused with: Coinbase (the unique part of a coinbase transaction)
#
The first transaction in a block. Always created by a miner, it includes a single coinbase.
Not to be confused with: Coinbase (the unique part of a coinbase transaction)
The first transaction in a Block One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
Mining is the act of creating valid Bitcoin blocks, which requires demonstrating proof of work, and miners are devices that mine or people who own those devices.
A special field used as the sole input for coinbase transactions. The coinbase allows claiming the block reward and provides up to 100 bytes for arbitrary data.
Not to be confused with: Coinbase transaction, Coinbase.com
Not to be confused with: Coinbase A special field used as the sole input for coinbase transactions. The coinbase allows claiming the block reward and provides up to 100 bytes for arbitrary data. Not to be confused with: Coinbase transaction, Coinbase.com
A special field used as the sole input for coinbase transactions. The coinbase allows claiming the block reward and provides up to 100 bytes for arbitrary data.
Not to be confused with: Coinbase transaction, Coinbase.com
CompactSizeA type of variable-length integer commonly used in the Bitcoin P2P protocol and Bitcoin serialized data structures.
Not to be confused with: VarInt (a data type Bitcoin Core uses for local data storage), Compact (the data type used for nBits in the block header)
#
A type of variable-length integer commonly used in the Bitcoin P2P protocol and Bitcoin serialized data structures.
Not to be confused with: VarInt (a data type Bitcoin Core uses for local data storage), Compact (the data type used for nBits in the block header)
A type of variable-length integer commonly used in the Bitcoin P2P protocol and Bitcoin serialized data structures.
Not to be confused with: VarInt (a data type Bitcoin Core uses for local data storage), Compact (the data type used for nBits The target is the threshold below which a block header hash must be in order for the block to be valid, and nBits is the encoded form of the target threshold as it appears in the block header. Not to be confused with: Difficulty (a number measuring the difficulty of finding a header hash relative to the difficulty of finding a header hash with the easiest target)
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
An 80-byte header belonging to a single block which is hashed repeatedly to create proof of work.
Compressed public keyAn ECDSA public key that is 33 bytes long rather than the 65 bytes of an uncompressed public key.
#
An ECDSA public key that is 33 bytes long rather than the 65 bytes of an uncompressed public key.
An ECDSA Public key The public portion of a keypair which can be used to verify signatures made with the private portion of the keypair. Not to be confused with: Private key (data from which the public key is derived), Parent key (a key used to create child keys, not necessarily a public key)
The public portion of a keypair which can be used to verify signatures made with the private portion of the keypair.
Not to be confused with: Private key (data from which the public key is derived), Parent key (a key used to create child keys, not necessarily a public key)
Confirmation scoreA score indicating the number of blocks on the best block chain that would need to be modified to remove or modify a particular transaction. A confirmed transaction has a confirmation score of one or higher.
#
A score indicating the number of blocks on the best block chain that would need to be modified to remove or modify a particular transaction. A confirmed transaction has a confirmation score of one or higher.
ConfirmationsA score indicating the number of blocks on the best block chain that would need to be modified to remove or modify a particular transaction. A confirmed transaction has a confirmation score of one or higher.
#
A score indicating the number of blocks on the best block chain that would need to be modified to remove or modify a particular transaction. A confirmed transaction has a confirmation score of one or higher.
Confirmed transactionA score indicating the number of blocks on the best block chain that would need to be modified to remove or modify a particular transaction. A confirmed transaction has a confirmation score of one or higher.
#
A score indicating the number of blocks on the best block chain that would need to be modified to remove or modify a particular transaction. A confirmed transaction has a confirmation score of one or higher.
Unconfirmed transactionA score indicating the number of blocks on the best block chain that would need to be modified to remove or modify a particular transaction. A confirmed transaction has a confirmation score of one or higher.
#
A score indicating the number of blocks on the best block chain that would need to be modified to remove or modify a particular transaction. A confirmed transaction has a confirmation score of one or higher.
A score indicating the number of blocks on the Best block chain A chain of blocks with each block referencing the block that preceded it. The most-difficult-to-recreate chain is the best block chain. Not to be confused with: Header chain
A score indicating the number of blocks on the best block chain that would need to be modified to remove or modify a particular transaction. A confirmed transaction has a confirmation score of one or higher.
A score indicating the number of blocks on the best block chain that would need to be modified to remove or modify a particular transaction. A confirmed transaction has a confirmation score of one or higher.
ConsensusWhen several nodes (usually most nodes on the network) all have the same blocks in their locally-validated best block chain.
Not to be confused with: Social consensus (often used in discussion among developers to indicate that most people agree with a particular plan), Consensus rules (the rules that allow nodes to maintain consensus)
#
When several nodes (usually most nodes on the network) all have the same blocks in their locally-validated best block chain.
Not to be confused with: Social consensus (often used in discussion among developers to indicate that most people agree with a particular plan), Consensus rules (the rules that allow nodes to maintain consensus)
When several nodes (usually most nodes on the network) all have the same blocks in their locally-validated Best block chain A chain of blocks with each block referencing the block that preceded it. The most-difficult-to-recreate chain is the best block chain. Not to be confused with: Header chain
Not to be confused with: Social Consensus When several nodes (usually most nodes on the network) all have the same blocks in their locally-validated best block chain. Not to be confused with: Social consensus (often used in discussion among developers to indicate that most people agree with a particular plan), Consensus rules (the rules that allow nodes to maintain consensus)
When several nodes (usually most nodes on the network) all have the same blocks in their locally-validated best block chain.
Not to be confused with: Social consensus (often used in discussion among developers to indicate that most people agree with a particular plan), Consensus rules (the rules that allow nodes to maintain consensus)
When several nodes (usually most nodes on the network) all have the same blocks in their locally-validated best block chain.
Not to be confused with: Social consensus (often used in discussion among developers to indicate that most people agree with a particular plan), Consensus rules (the rules that allow nodes to maintain consensus)
ConsensusWhen several nodes (usually most nodes on the network) all have the same blocks in their locally-validated best block chain.
Not to be confused with: Social consensus (often used in discussion among developers to indicate that most people agree with a particular plan), Consensus rules (the rules that allow nodes to maintain consensus)
rules #
When several nodes (usually most nodes on the network) all have the same blocks in their locally-validated best block chain.
Not to be confused with: Social consensus (often used in discussion among developers to indicate that most people agree with a particular plan), Consensus rules (the rules that allow nodes to maintain consensus)
The Block One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
When several nodes (usually most nodes on the network) all have the same blocks in their locally-validated best block chain.
Not to be confused with: Social consensus (often used in discussion among developers to indicate that most people agree with a particular plan), Consensus rules (the rules that allow nodes to maintain consensus)
Not to be confused with: Consensus When several nodes (usually most nodes on the network) all have the same blocks in their locally-validated best block chain. Not to be confused with: Social consensus (often used in discussion among developers to indicate that most people agree with a particular plan), Consensus rules (the rules that allow nodes to maintain consensus)
When several nodes (usually most nodes on the network) all have the same blocks in their locally-validated best block chain.
Not to be confused with: Social consensus (often used in discussion among developers to indicate that most people agree with a particular plan), Consensus rules (the rules that allow nodes to maintain consensus)
Child pays for parentSelecting transactions for mining not just based on their fees but also based on the fees of their ancestors (parents) and descendants (children).
Not to be confused with: Replace by Fee, RBF
#
Selecting transactions for mining not just based on their fees but also based on the fees of their ancestors (parents) and descendants (children).
Not to be confused with: Replace by Fee, RBF
CPFPSelecting transactions for mining not just based on their fees but also based on the fees of their ancestors (parents) and descendants (children).
Not to be confused with: Replace by Fee, RBF
#
Selecting transactions for mining not just based on their fees but also based on the fees of their ancestors (parents) and descendants (children).
Not to be confused with: Replace by Fee, RBF
Ancestor miningSelecting transactions for mining not just based on their fees but also based on the fees of their ancestors (parents) and descendants (children).
Not to be confused with: Replace by Fee, RBF
#
Selecting transactions for mining not just based on their fees but also based on the fees of their ancestors (parents) and descendants (children).
Not to be confused with: Replace by Fee, RBF
Selecting transactions for Mining Mining is the act of creating valid Bitcoin blocks, which requires demonstrating proof of work, and miners are devices that mine or people who own those devices.
Not to be confused with: Replace by fee Replacing one version of an unconfirmed transaction with a different version of the transaction that pays a higher transaction fee. May use BIP125 signaling. Not to be confused with: Child pays for parent, CPFP
Replacing one version of an unconfirmed transaction with a different version of the transaction that pays a higher transaction fee. May use BIP125 signaling.
Not to be confused with: Child pays for parent, CPFP
DenominationDenominations of Bitcoin value, usually measured in fractions of a bitcoin but sometimes measured in multiples of a satoshi. One bitcoin equals 100,000,000 satoshis.
Not to be confused with: Binary bits, a unit of data with two possible values
#
Denominations of Bitcoin value, usually measured in fractions of a bitcoin but sometimes measured in multiples of a satoshi. One bitcoin equals 100,000,000 satoshis.
Not to be confused with: Binary bits, a unit of data with two possible values
BitcoinsDenominations of Bitcoin value, usually measured in fractions of a bitcoin but sometimes measured in multiples of a satoshi. One bitcoin equals 100,000,000 satoshis.
Not to be confused with: Binary bits, a unit of data with two possible values
#
Denominations of Bitcoin value, usually measured in fractions of a bitcoin but sometimes measured in multiples of a satoshi. One bitcoin equals 100,000,000 satoshis.
Not to be confused with: Binary bits, a unit of data with two possible values
SatoshisDenominations of Bitcoin value, usually measured in fractions of a bitcoin but sometimes measured in multiples of a satoshi. One bitcoin equals 100,000,000 satoshis.
Not to be confused with: Binary bits, a unit of data with two possible values
#
Denominations of Bitcoin value, usually measured in fractions of a bitcoin but sometimes measured in multiples of a satoshi. One bitcoin equals 100,000,000 satoshis.
Not to be confused with: Binary bits, a unit of data with two possible values
Denominations of Bitcoin value, usually measured in fractions of a bitcoin but sometimes measured in multiples of a satoshi. One bitcoin equals 100,000,000 Satoshis Denominations of Bitcoin value, usually measured in fractions of a bitcoin but sometimes measured in multiples of a satoshi. One bitcoin equals 100,000,000 satoshis. Not to be confused with: Binary bits, a unit of data with two possible values
Not to be confused with: Binary bits, a unit of data with two possible values
DifficultyHow difficult it is to find a block relative to the difficulty of finding the easiest possible block. The easiest possible block has a proof-of-work difficulty of 1.
Not to be confused with: Target threshold (the value from which difficulty is calculated)
#
How difficult it is to find a block relative to the difficulty of finding the easiest possible block. The easiest possible block has a proof-of-work difficulty of 1.
Not to be confused with: Target threshold (the value from which difficulty is calculated)
Network DifficultyHow difficult it is to find a block relative to the difficulty of finding the easiest possible block. The easiest possible block has a proof-of-work difficulty of 1.
Not to be confused with: Target threshold (the value from which difficulty is calculated)
#
How difficult it is to find a block relative to the difficulty of finding the easiest possible block. The easiest possible block has a proof-of-work difficulty of 1.
Not to be confused with: Target threshold (the value from which difficulty is calculated)
How difficult it is to find a Block One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
How difficult it is to find a block relative to the difficulty of finding the easiest possible block. The easiest possible block has a proof-of-work difficulty of 1.
Not to be confused with: Target threshold (the value from which difficulty is calculated)
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
How difficult it is to find a block relative to the difficulty of finding the easiest possible block. The easiest possible block has a proof-of-work difficulty of 1.
Not to be confused with: Target threshold (the value from which difficulty is calculated)
Not to be confused with: Target The target is the threshold below which a block header hash must be in order for the block to be valid, and nBits is the encoded form of the target threshold as it appears in the block header. Not to be confused with: Difficulty (a number measuring the difficulty of finding a header hash relative to the difficulty of finding a header hash with the easiest target)
How difficult it is to find a block relative to the difficulty of finding the easiest possible block. The easiest possible block has a proof-of-work difficulty of 1.
Not to be confused with: Target threshold (the value from which difficulty is calculated)
DNS seedA DNS server which returns IP addresses of full nodes on the Bitcoin network to assist in peer discovery.
Not to be confused with: HD wallet seeds
#
A DNS server which returns IP addresses of full nodes on the Bitcoin network to assist in peer discovery.
Not to be confused with: HD wallet seeds
A DNS server which returns IP addresses of full nodes on the Bitcoin network to assist in Peer A computer that connects to the Bitcoin network. Not to be confused with: Lightweight node, SPV node
Not to be confused with: HD wallet The Hierarchical Deterministic (HD) key creation and transfer protocol (BIP32), which allows creating child keys from parent keys in a hierarchy. Wallets using the HD protocol are called HD wallets.
Double spendA transaction that uses the same input as an already broadcast transaction. The attempt of duplication, deceit, or conversion, will be adjudicated when only one of the transactions is recorded in the blockchain.
#
A transaction that uses the same input as an already broadcast transaction. The attempt of duplication, deceit, or conversion, will be adjudicated when only one of the transactions is recorded in the blockchain.
A transaction that uses the same Input An input in a transaction which contains three fields: an outpoint, a signature script, and a sequence number. The outpoint references a previous output and the signature script allows spending it.
Escrow contractA transaction in which a spender and receiver place funds in a 2-of-2 (or other m-of-n) multisig output so that neither can spend the funds until they’re both satisfied with some external outcome.
#
A transaction in which a spender and receiver place funds in a 2-of-2 (or other m-of-n) multisig output so that neither can spend the funds until they’re both satisfied with some external outcome.
A transaction in which a spender and receiver place funds in a 2-of-2 (or other m-of-n) Multisig A pubkey script that provides n number of pubkeys and requires the corresponding signature script provide m minimum number signatures corresponding to the provided pubkeys. Not to be confused with: P2SH multisig (a multisig script contained inside P2SH), Advanced scripts that require multiple signatures without using OP_CHECKMULTISIG or OP_CHECKMULTISIGVERIFY
An output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent.
Not to be confused with: Outpoint (a reference to a particular output)
Extended keyIn the context of HD wallets, a public key or private key extended with the chain code to allow them to derive child keys.
#
In the context of HD wallets, a public key or private key extended with the chain code to allow them to derive child keys.
Public Extended keyIn the context of HD wallets, a public key or private key extended with the chain code to allow them to derive child keys.
#
In the context of HD wallets, a public key or private key extended with the chain code to allow them to derive child keys.
Private Extended keyIn the context of HD wallets, a public key or private key extended with the chain code to allow them to derive child keys.
#
In the context of HD wallets, a public key or private key extended with the chain code to allow them to derive child keys.
In the context of HD wallets, a Public key The public portion of a keypair which can be used to verify signatures made with the private portion of the keypair. Not to be confused with: Private key (data from which the public key is derived), Parent key (a key used to create child keys, not necessarily a public key)
The private portion of a keypair which can create signatures that other people can verify using the public key.
Not to be confused with: Public key (data derived from the private key), Parent key (a key used to create child keys, not necessarily a private key)
In HD wallets, 256 bits of entropy added to the public and private keys to help them generate secure child keys; the master chain code is usually derived from a seed along with the master private key
ForkWhen two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
#
When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
When two or more blocks have the same Block One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
The number of blocks preceding a particular block on a block chain. For example, the genesis block has a height of zero because zero block preceded it.
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
Not to be confused with: Hard Fork When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack. Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
When several nodes (usually most nodes on the network) all have the same blocks in their locally-validated best block chain.
Not to be confused with: Social consensus (often used in discussion among developers to indicate that most people agree with a particular plan), Consensus rules (the rules that allow nodes to maintain consensus)
When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
When several nodes (usually most nodes on the network) all have the same blocks in their locally-validated best block chain.
Not to be confused with: Social consensus (often used in discussion among developers to indicate that most people agree with a particular plan), Consensus rules (the rules that allow nodes to maintain consensus)
When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
Genesis BlockOne or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
#
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
BlockOne or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
0 #
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
The first Block One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
Not to be confused with: Generation transaction The first transaction in a block. Always created by a miner, it includes a single coinbase. Not to be confused with: Coinbase (the unique part of a coinbase transaction)
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
Hard ForkWhen two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
#
When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
A permanent divergence in the Block One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
When several nodes (usually most nodes on the network) all have the same blocks in their locally-validated best block chain.
Not to be confused with: Social consensus (often used in discussion among developers to indicate that most people agree with a particular plan), Consensus rules (the rules that allow nodes to maintain consensus)
Not to be confused with: Fork When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack. Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
When several nodes (usually most nodes on the network) all have the same blocks in their locally-validated best block chain.
Not to be confused with: Social consensus (often used in discussion among developers to indicate that most people agree with a particular plan), Consensus rules (the rules that allow nodes to maintain consensus)
When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
A hash below a target value which can only be obtained, on average, by performing a certain amount of brute force work—therefore demonstrating proof of work.
When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
When several nodes (usually most nodes on the network) all have the same blocks in their locally-validated best block chain.
Not to be confused with: Social consensus (often used in discussion among developers to indicate that most people agree with a particular plan), Consensus rules (the rules that allow nodes to maintain consensus)
When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
Hardened Extended keyIn the context of HD wallets, a public key or private key extended with the chain code to allow them to derive child keys.
#
In the context of HD wallets, a public key or private key extended with the chain code to allow them to derive child keys.
A variation on HD wallet The Hierarchical Deterministic (HD) key creation and transfer protocol (BIP32), which allows creating child keys from parent keys in a hierarchy. Wallets using the HD protocol are called HD wallets.
The private portion of a keypair which can create signatures that other people can verify using the public key.
Not to be confused with: Public key (data derived from the private key), Parent key (a key used to create child keys, not necessarily a private key)
In HD wallets, 256 bits of entropy added to the public and private keys to help them generate secure child keys; the master chain code is usually derived from a seed along with the master private key
The private portion of a keypair which can create signatures that other people can verify using the public key.
Not to be confused with: Public key (data derived from the private key), Parent key (a key used to create child keys, not necessarily a private key)
Software that stores private keys and monitors the block chain (sometimes as a client of a server that does the processing) to allow users to spend and receive satoshis.
Not to be confused with: HD wallet (a protocol that allows all of a wallet’s keys to be created from a single seed)
HD protocolThe Hierarchical Deterministic (HD) key creation and transfer protocol (BIP32), which allows creating child keys from parent keys in a hierarchy. Wallets using the HD protocol are called HD wallets.
#
The Hierarchical Deterministic (HD) key creation and transfer protocol (BIP32), which allows creating child keys from parent keys in a hierarchy. Wallets using the HD protocol are called HD wallets.
HD walletThe Hierarchical Deterministic (HD) key creation and transfer protocol (BIP32), which allows creating child keys from parent keys in a hierarchy. Wallets using the HD protocol are called HD wallets.
#
The Hierarchical Deterministic (HD) key creation and transfer protocol (BIP32), which allows creating child keys from parent keys in a hierarchy. Wallets using the HD protocol are called HD wallets.
The Hierarchical Deterministic (HD) key creation and transfer protocol (BIP32), which allows creating child keys from parent keys in a hierarchy. Wallets using the HD protocol The Hierarchical Deterministic (HD) key creation and transfer protocol (BIP32), which allows creating child keys from parent keys in a hierarchy. Wallets using the HD protocol are called HD wallets.
HD walletThe Hierarchical Deterministic (HD) key creation and transfer protocol (BIP32), which allows creating child keys from parent keys in a hierarchy. Wallets using the HD protocol are called HD wallets.
seed #
The Hierarchical Deterministic (HD) key creation and transfer protocol (BIP32), which allows creating child keys from parent keys in a hierarchy. Wallets using the HD protocol are called HD wallets.
Root seedA potentially-short value used as a seed to generate the master private key and master chain code for an HD wallet.
Not to be confused with: Mnemonic code / mnemonic seed (a binary root seed formatted as words to make it easier for humans to transcribe and possibly remember)
#
A potentially-short value used as a seed to generate the master private key and master chain code for an HD wallet.
Not to be confused with: Mnemonic code / mnemonic seed (a binary root seed formatted as words to make it easier for humans to transcribe and possibly remember)
A potentially-short value used as a seed to generate the Master private key In HD wallets, the master chain code and master private key are the two pieces of data derived from the root seed.
In HD wallets, 256 bits of entropy added to the public and private keys to help them generate secure child keys; the master chain code is usually derived from a seed along with the master private key
The Hierarchical Deterministic (HD) key creation and transfer protocol (BIP32), which allows creating child keys from parent keys in a hierarchy. Wallets using the HD protocol are called HD wallets.
Not to be confused with: Mnemonic code / mnemonic seed (a binary Root seed A potentially-short value used as a seed to generate the master private key and master chain code for an HD wallet. Not to be confused with: Mnemonic code / mnemonic seed (a binary root seed formatted as words to make it easier for humans to transcribe and possibly remember)
HeaderAn 80-byte header belonging to a single block which is hashed repeatedly to create proof of work.
chain #
An 80-byte header belonging to a single block which is hashed repeatedly to create proof of work.
Best header chainA chain of block headers with each header linking to the header that preceded it; the most-difficult-to-recreate chain is the best header chain
Not to be confused with: Block chain
#
A chain of block headers with each header linking to the header that preceded it; the most-difficult-to-recreate chain is the best header chain
Not to be confused with: Block chain
A chain of Block One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
An 80-byte header belonging to a single block which is hashed repeatedly to create proof of work.
An 80-byte header belonging to a single block which is hashed repeatedly to create proof of work.
A chain of block headers with each header linking to the header that preceded it; the most-difficult-to-recreate chain is the best header chain
Not to be confused with: Block chain
Not to be confused with: Block One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
Headers-first syncSynchronizing the block chain by downloading block headers before downloading the full blocks.
Not to be confused with: Blocks-first sync (Downloading entire blocks immediately without first getting their headers)
#
Synchronizing the block chain by downloading block headers before downloading the full blocks.
Not to be confused with: Blocks-first sync (Downloading entire blocks immediately without first getting their headers)
Synchronizing the Block One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
Not to be confused with: Blocks-first sync Synchronizing the block chain by downloading each block from a peer and then validating it. Not to be confused with: Headers-first sync
High-priority transactionTransactions that don’t have to pay a transaction fee because their inputs have been idle long enough to accumulated large amounts of priority. Note: miners choose whether to accept free transactions.
#
Transactions that don’t have to pay a transaction fee because their inputs have been idle long enough to accumulated large amounts of priority. Note: miners choose whether to accept free transactions.
Free transactionTransactions that don’t have to pay a transaction fee because their inputs have been idle long enough to accumulated large amounts of priority. Note: miners choose whether to accept free transactions.
#
Transactions that don’t have to pay a transaction fee because their inputs have been idle long enough to accumulated large amounts of priority. Note: miners choose whether to accept free transactions.
Transactions that don’t have to pay a Transaction fee The amount remaining when the value of all outputs in a transaction are subtracted from all inputs in a transaction; the fee is paid to the miner who includes that transaction in a block. Not to be confused with: Minimum relay fee (the lowest fee a transaction must pay to be accepted into the memory pool and relayed by Bitcoin Core nodes)
Initial BlockOne or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
download #
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
IBDThe process used by a new node (or long-offline node) to download a large number of blocks to catch up to the tip of the best block chain.
Not to be confused with: Blocks-first sync (syncing includes getting any amount of blocks; IBD is only used for large numbers of blocks)
#
The process used by a new node (or long-offline node) to download a large number of blocks to catch up to the tip of the best block chain.
Not to be confused with: Blocks-first sync (syncing includes getting any amount of blocks; IBD is only used for large numbers of blocks)
The process used by a new Node A computer that connects to the Bitcoin network. Not to be confused with: Lightweight node, SPV node
A computer that connects to the Bitcoin network.
Not to be confused with: Lightweight node, SPV node
A chain of blocks with each block referencing the block that preceded it. The most-difficult-to-recreate chain is the best block chain.
Not to be confused with: Header chain
Not to be confused with: Blocks-first sync Synchronizing the block chain by downloading each block from a peer and then validating it. Not to be confused with: Headers-first sync
The process used by a new node (or long-offline node) to download a large number of blocks to catch up to the tip of the best block chain.
Not to be confused with: Blocks-first sync (syncing includes getting any amount of blocks; IBD is only used for large numbers of blocks)
InputAn input in a transaction which contains three fields: an outpoint, a signature script, and a sequence number. The outpoint references a previous output and the signature script allows spending it.
#
An input in a transaction which contains three fields: an outpoint, a signature script, and a sequence number. The outpoint references a previous output and the signature script allows spending it.
TxInAn input in a transaction which contains three fields: an outpoint, a signature script, and a sequence number. The outpoint references a previous output and the signature script allows spending it.
#
An input in a transaction which contains three fields: an outpoint, a signature script, and a sequence number. The outpoint references a previous output and the signature script allows spending it.
An Input An input in a transaction which contains three fields: an outpoint, a signature script, and a sequence number. The outpoint references a previous output and the signature script allows spending it.
The data structure used to refer to a particular transaction output, consisting of a 32-byte TXID and a 4-byte output index number (vout).
Not to be confused with: Output (an entire output from a transaction), TxOut (same as output)
A value related to a public key which could only have reasonably been created by someone who has the private key that created that public key. Used in Bitcoin to authorize spending satoshis previously sent to a public key.
Part of all transactions. A number intended to allow unconfirmed time-locked transactions to be updated before being finalized; not currently used except to disable locktime in a transaction
Not to be confused with: Output index number / vout (this is the 0-indexed number of an output within a transaction used by a later transaction to refer to that specific output)
The data structure used to refer to a particular transaction output, consisting of a 32-byte TXID and a 4-byte output index number (vout).
Not to be confused with: Output (an entire output from a transaction), TxOut (same as output)
An output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent.
Not to be confused with: Outpoint (a reference to a particular output)
A value related to a public key which could only have reasonably been created by someone who has the private key that created that public key. Used in Bitcoin to authorize spending satoshis previously sent to a public key.
Internal byte orderThe standard order in which hash digests are displayed as strings—the same format used in serialized blocks and transactions.
Not to be confused with: RPC byte order (where the byte order is reversed)
#
The standard order in which hash digests are displayed as strings—the same format used in serialized blocks and transactions.
Not to be confused with: RPC byte order (where the byte order is reversed)
The standard order in which hash digests are displayed as strings—the same format used in serialized blocks and transactions.
Not to be confused with: RPC byte order A hash digest displayed with the byte order reversed; used in Bitcoin Core RPCs, many block explorers, and other software. Not to be confused with: Internal byte order (hash digests displayed in their typical order; used in serialized blocks and serialized transactions)
InventoryA data type identifier and a hash; used to identify transactions and blocks available for download through the Bitcoin P2P network.
Not to be confused with: Inv message (one of the P2P messages that transmits inventories)
#
A data type identifier and a hash; used to identify transactions and blocks available for download through the Bitcoin P2P network.
Not to be confused with: Inv message (one of the P2P messages that transmits inventories)
A data type identifier and a hash; used to identify transactions and blocks available for download through the Bitcoin P2P network.
Not to be confused with: Inv Message A parameter of bitcoin: URIs which allows the receiver to optionally specify a message to the spender.
LocktimePart of a transaction which indicates the earliest time or earliest block when that transaction may be added to the block chain.
#
Part of a transaction which indicates the earliest time or earliest block when that transaction may be added to the block chain.
nLockTimePart of a transaction which indicates the earliest time or earliest block when that transaction may be added to the block chain.
#
Part of a transaction which indicates the earliest time or earliest block when that transaction may be added to the block chain.
Part of a transaction which indicates the earliest time or earliest Block One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
MainnetThe original and main network for Bitcoin transactions, where satoshis have real economic value.
Not to be confused with: Testnet (an open network very similar to mainnet where satoshis have no value), Regtest (a private testing node similar to testnet)
#
The original and main network for Bitcoin transactions, where satoshis have real economic value.
Not to be confused with: Testnet (an open network very similar to mainnet where satoshis have no value), Regtest (a private testing node similar to testnet)
The original and main network for Bitcoin transactions, where Satoshis Denominations of Bitcoin value, usually measured in fractions of a bitcoin but sometimes measured in multiples of a satoshi. One bitcoin equals 100,000,000 satoshis. Not to be confused with: Binary bits, a unit of data with two possible values
Not to be confused with: Testnet A global testing environment in which developers can obtain and spend satoshis that have no real-world value on a network that is very similar to the Bitcoin mainnet. Not to be confused with: Regtest (a local testing environment where developers can control block generation)
The original and main network for Bitcoin transactions, where satoshis have real economic value.
Not to be confused with: Testnet (an open network very similar to mainnet where satoshis have no value), Regtest (a private testing node similar to testnet)
Denominations of Bitcoin value, usually measured in fractions of a bitcoin but sometimes measured in multiples of a satoshi. One bitcoin equals 100,000,000 satoshis.
Not to be confused with: Binary bits, a unit of data with two possible values
A local testing environment in which developers can almost instantly generate blocks on demand for testing events, and can create private satoshis with no real-world value.
Not to be confused with: Testnet (a global testing environment which mostly mimics mainnet)
A computer that connects to the Bitcoin network.
Not to be confused with: Lightweight node, SPV node
A global testing environment in which developers can obtain and spend satoshis that have no real-world value on a network that is very similar to the Bitcoin mainnet.
Not to be confused with: Regtest (a local testing environment where developers can control block generation)
Transaction malleabilityThe ability of someone to change (mutate) unconfirmed transactions without making them invalid, which changes the transaction’s txid, making child transactions invalid.
Not to be confused with: BIP62 (a proposal for an optional new transaction version that reduces the set of known mutations for common transactions)
#
The ability of someone to change (mutate) unconfirmed transactions without making them invalid, which changes the transaction’s txid, making child transactions invalid.
Not to be confused with: BIP62 (a proposal for an optional new transaction version that reduces the set of known mutations for common transactions)
Transaction mutabilityThe ability of someone to change (mutate) unconfirmed transactions without making them invalid, which changes the transaction’s txid, making child transactions invalid.
Not to be confused with: BIP62 (a proposal for an optional new transaction version that reduces the set of known mutations for common transactions)
#
The ability of someone to change (mutate) unconfirmed transactions without making them invalid, which changes the transaction’s txid, making child transactions invalid.
Not to be confused with: BIP62 (a proposal for an optional new transaction version that reduces the set of known mutations for common transactions)
The ability of someone to change (mutate) unconfirmed transactions without making them invalid, which changes the transaction’s Txid An identifier used to uniquely identify a particular transaction; specifically, the sha256d hash of the transaction. Not to be confused with: Outpoint (the combination of a txid with a vout used to identify a specific output)
Not to be confused with: BIP62 (a proposal for an optional new transaction version that reduces the set of known mutations for common transactions)
MinerMining is the act of creating valid Bitcoin blocks, which requires demonstrating proof of work, and miners are devices that mine or people who own those devices.
-activated soft ForkWhen two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
#
Mining is the act of creating valid Bitcoin blocks, which requires demonstrating proof of work, and miners are devices that mine or people who own those devices.
When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
MASFA Soft Fork activated by through miner signalling.
Not to be confused with: User Activated Soft Fork (a soft fork activated by flag day or node enforcement instead of miner signalling.), Fork (a regular fork where all nodes follow the same consensus rules, so the fork is resolved once one chain has more proof of work than another), Hard fork (a permanent divergence in the block chain caused by non-upgraded nodes not following new consensus rules), Soft fork (a temporary divergence in the block chain caused by non-upgraded nodes not following new consensus rules), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers
#
A Soft Fork activated by through miner signalling.
Not to be confused with: User Activated Soft Fork (a soft fork activated by flag day or node enforcement instead of miner signalling.), Fork (a regular fork where all nodes follow the same consensus rules, so the fork is resolved once one chain has more proof of work than another), Hard fork (a permanent divergence in the block chain caused by non-upgraded nodes not following new consensus rules), Soft fork (a temporary divergence in the block chain caused by non-upgraded nodes not following new consensus rules), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers
A Soft Fork When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack. Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
Mining is the act of creating valid Bitcoin blocks, which requires demonstrating proof of work, and miners are devices that mine or people who own those devices.
Not to be confused with: User Activated Soft Fork When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack. Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
A computer that connects to the Bitcoin network.
Not to be confused with: Lightweight node, SPV node
Mining is the act of creating valid Bitcoin blocks, which requires demonstrating proof of work, and miners are devices that mine or people who own those devices.
When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
When several nodes (usually most nodes on the network) all have the same blocks in their locally-validated best block chain.
Not to be confused with: Social consensus (often used in discussion among developers to indicate that most people agree with a particular plan), Consensus rules (the rules that allow nodes to maintain consensus)
When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
A hash below a target value which can only be obtained, on average, by performing a certain amount of brute force work—therefore demonstrating proof of work.
When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
When several nodes (usually most nodes on the network) all have the same blocks in their locally-validated best block chain.
Not to be confused with: Social consensus (often used in discussion among developers to indicate that most people agree with a particular plan), Consensus rules (the rules that allow nodes to maintain consensus)
When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
When several nodes (usually most nodes on the network) all have the same blocks in their locally-validated best block chain.
Not to be confused with: Social consensus (often used in discussion among developers to indicate that most people agree with a particular plan), Consensus rules (the rules that allow nodes to maintain consensus)
When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
Master Chain codeIn HD wallets, 256 bits of entropy added to the public and private keys to help them generate secure child keys; the master chain code is usually derived from a seed along with the master private key
#
In HD wallets, 256 bits of entropy added to the public and private keys to help them generate secure child keys; the master chain code is usually derived from a seed along with the master private key
Master private keyIn HD wallets, the master chain code and master private key are the two pieces of data derived from the root seed.
#
In HD wallets, the master chain code and master private key are the two pieces of data derived from the root seed.
In HD wallets, the master Chain code In HD wallets, 256 bits of entropy added to the public and private keys to help them generate secure child keys; the master chain code is usually derived from a seed along with the master private key
In HD wallets, the master chain code and master private key are the two pieces of data derived from the root seed.
A potentially-short value used as a seed to generate the master private key and master chain code for an HD wallet.
Not to be confused with: Mnemonic code / mnemonic seed (a binary root seed formatted as words to make it easier for humans to transcribe and possibly remember)
Merkle BlockOne or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
#
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
A partial Merkle tree A tree constructed by hashing paired data (the leaves), then pairing and hashing the results until a single hash remains, the merkle root. In Bitcoin, the leaves are almost always transactions from a single block. Not to be confused with: Partial merkle branch (a branch connecting one or more leaves to the root), Merkle block (a partial merkle branch connecting one or more transactions from a single block to the block merkle root)
A filter used primarily by SPV clients to request only matching transactions and merkle blocks from full nodes.
Not to be confused with: Bloom filter (general computer science term, of which Bitcoin’s bloom filters are a specific implementation)
The root node of a merkle tree, a descendant of all the hashed pairs in the tree. Block headers must include a valid merkle root descended from all transactions in that block.
Not to be confused with: Merkle tree (the tree of which the merkle root is the root node), Merkle block (a partial merkle branch connecting the root to one or more leaves [transactions])
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
Not to be confused with: MerkleBlock Message A parameter of bitcoin: URIs which allows the receiver to optionally specify a message to the spender.
A parameter of bitcoin: URIs which allows the receiver to optionally specify a message to the spender.
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
Merkle rootThe root node of a merkle tree, a descendant of all the hashed pairs in the tree. Block headers must include a valid merkle root descended from all transactions in that block.
Not to be confused with: Merkle tree (the tree of which the merkle root is the root node), Merkle block (a partial merkle branch connecting the root to one or more leaves [transactions])
#
The root node of a merkle tree, a descendant of all the hashed pairs in the tree. Block headers must include a valid merkle root descended from all transactions in that block.
Not to be confused with: Merkle tree (the tree of which the merkle root is the root node), Merkle block (a partial merkle branch connecting the root to one or more leaves [transactions])
The root Node A computer that connects to the Bitcoin network. Not to be confused with: Lightweight node, SPV node
A tree constructed by hashing paired data (the leaves), then pairing and hashing the results until a single hash remains, the merkle root. In Bitcoin, the leaves are almost always transactions from a single block.
Not to be confused with: Partial merkle branch (a branch connecting one or more leaves to the root), Merkle block (a partial merkle branch connecting one or more transactions from a single block to the block merkle root)
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
The root node of a merkle tree, a descendant of all the hashed pairs in the tree. Block headers must include a valid merkle root descended from all transactions in that block.
Not to be confused with: Merkle tree (the tree of which the merkle root is the root node), Merkle block (a partial merkle branch connecting the root to one or more leaves [transactions])
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
Not to be confused with: Merkle tree A tree constructed by hashing paired data (the leaves), then pairing and hashing the results until a single hash remains, the merkle root. In Bitcoin, the leaves are almost always transactions from a single block. Not to be confused with: Partial merkle branch (a branch connecting one or more leaves to the root), Merkle block (a partial merkle branch connecting one or more transactions from a single block to the block merkle root)
The root node of a merkle tree, a descendant of all the hashed pairs in the tree. Block headers must include a valid merkle root descended from all transactions in that block.
Not to be confused with: Merkle tree (the tree of which the merkle root is the root node), Merkle block (a partial merkle branch connecting the root to one or more leaves [transactions])
A computer that connects to the Bitcoin network.
Not to be confused with: Lightweight node, SPV node
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
Merkle treeA tree constructed by hashing paired data (the leaves), then pairing and hashing the results until a single hash remains, the merkle root. In Bitcoin, the leaves are almost always transactions from a single block.
Not to be confused with: Partial merkle branch (a branch connecting one or more leaves to the root), Merkle block (a partial merkle branch connecting one or more transactions from a single block to the block merkle root)
#
A tree constructed by hashing paired data (the leaves), then pairing and hashing the results until a single hash remains, the merkle root. In Bitcoin, the leaves are almost always transactions from a single block.
Not to be confused with: Partial merkle branch (a branch connecting one or more leaves to the root), Merkle block (a partial merkle branch connecting one or more transactions from a single block to the block merkle root)
A tree constructed by hashing paired data (the leaves), then pairing and hashing the results until a single hash remains, the Merkle root The root node of a merkle tree, a descendant of all the hashed pairs in the tree. Block headers must include a valid merkle root descended from all transactions in that block. Not to be confused with: Merkle tree (the tree of which the merkle root is the root node), Merkle block (a partial merkle branch connecting the root to one or more leaves [transactions])
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
Not to be confused with: Partial merkle branch (a branch connecting one or more leaves to the root), Merkle Block One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
The root node of a merkle tree, a descendant of all the hashed pairs in the tree. Block headers must include a valid merkle root descended from all transactions in that block.
Not to be confused with: Merkle tree (the tree of which the merkle root is the root node), Merkle block (a partial merkle branch connecting the root to one or more leaves [transactions])
MessageA parameter of bitcoin: URIs which allows the receiver to optionally specify a message to the spender.
HeaderAn 80-byte header belonging to a single block which is hashed repeatedly to create proof of work.
#
A parameter of bitcoin: URIs which allows the receiver to optionally specify a message to the spender.
An 80-byte header belonging to a single block which is hashed repeatedly to create proof of work.
The four Header An 80-byte header belonging to a single block which is hashed repeatedly to create proof of work.
Minimum relay feeThe minimum transaction fee a transaction must pay (if it isn’t a high-priority transaction) for a full node to relay that transaction to other nodes. There is no one minimum relay fee—each node chooses its own policy.
Not to be confused with: Transaction fee (the minimum relay fee is a policy setting that filters out transactions with too-low transaction fees)
#
The minimum transaction fee a transaction must pay (if it isn’t a high-priority transaction) for a full node to relay that transaction to other nodes. There is no one minimum relay fee—each node chooses its own policy.
Not to be confused with: Transaction fee (the minimum relay fee is a policy setting that filters out transactions with too-low transaction fees)
Relay feeThe minimum transaction fee a transaction must pay (if it isn’t a high-priority transaction) for a full node to relay that transaction to other nodes. There is no one minimum relay fee—each node chooses its own policy.
Not to be confused with: Transaction fee (the minimum relay fee is a policy setting that filters out transactions with too-low transaction fees)
#
The minimum transaction fee a transaction must pay (if it isn’t a high-priority transaction) for a full node to relay that transaction to other nodes. There is no one minimum relay fee—each node chooses its own policy.
Not to be confused with: Transaction fee (the minimum relay fee is a policy setting that filters out transactions with too-low transaction fees)
The minimum Transaction fee The amount remaining when the value of all outputs in a transaction are subtracted from all inputs in a transaction; the fee is paid to the miner who includes that transaction in a block. Not to be confused with: Minimum relay fee (the lowest fee a transaction must pay to be accepted into the memory pool and relayed by Bitcoin Core nodes)
Transactions that don’t have to pay a transaction fee because their inputs have been idle long enough to accumulated large amounts of priority. Note: miners choose whether to accept free transactions.
A computer that connects to the Bitcoin network.
Not to be confused with: Lightweight node, SPV node
The minimum transaction fee a transaction must pay (if it isn’t a high-priority transaction) for a full node to relay that transaction to other nodes. There is no one minimum relay fee—each node chooses its own policy.
Not to be confused with: Transaction fee (the minimum relay fee is a policy setting that filters out transactions with too-low transaction fees)
A computer that connects to the Bitcoin network.
Not to be confused with: Lightweight node, SPV node
Not to be confused with: Transaction fee The amount remaining when the value of all outputs in a transaction are subtracted from all inputs in a transaction; the fee is paid to the miner who includes that transaction in a block. Not to be confused with: Minimum relay fee (the lowest fee a transaction must pay to be accepted into the memory pool and relayed by Bitcoin Core nodes)
The minimum transaction fee a transaction must pay (if it isn’t a high-priority transaction) for a full node to relay that transaction to other nodes. There is no one minimum relay fee—each node chooses its own policy.
Not to be confused with: Transaction fee (the minimum relay fee is a policy setting that filters out transactions with too-low transaction fees)
MiningMining is the act of creating valid Bitcoin blocks, which requires demonstrating proof of work, and miners are devices that mine or people who own those devices.
#
Mining is the act of creating valid Bitcoin blocks, which requires demonstrating proof of work, and miners are devices that mine or people who own those devices.
MinerMining is the act of creating valid Bitcoin blocks, which requires demonstrating proof of work, and miners are devices that mine or people who own those devices.
#
Mining is the act of creating valid Bitcoin blocks, which requires demonstrating proof of work, and miners are devices that mine or people who own those devices.
Mining Mining is the act of creating valid Bitcoin blocks, which requires demonstrating proof of work, and miners are devices that mine or people who own those devices.
A hash below a target value which can only be obtained, on average, by performing a certain amount of brute force work—therefore demonstrating proof of work.
MultisigA pubkey script that provides n number of pubkeys and requires the corresponding signature script provide m minimum number signatures corresponding to the provided pubkeys.
Not to be confused with: P2SH multisig (a multisig script contained inside P2SH), Advanced scripts that require multiple signatures without using OP_CHECKMULTISIG or OP_CHECKMULTISIGVERIFY
#
A pubkey script that provides n number of pubkeys and requires the corresponding signature script provide m minimum number signatures corresponding to the provided pubkeys.
Not to be confused with: P2SH multisig (a multisig script contained inside P2SH), Advanced scripts that require multiple signatures without using OP_CHECKMULTISIG or OP_CHECKMULTISIGVERIFY
Bare multisigA pubkey script that provides n number of pubkeys and requires the corresponding signature script provide m minimum number signatures corresponding to the provided pubkeys.
Not to be confused with: P2SH multisig (a multisig script contained inside P2SH), Advanced scripts that require multiple signatures without using OP_CHECKMULTISIG or OP_CHECKMULTISIGVERIFY
#
A pubkey script that provides n number of pubkeys and requires the corresponding signature script provide m minimum number signatures corresponding to the provided pubkeys.
Not to be confused with: P2SH multisig (a multisig script contained inside P2SH), Advanced scripts that require multiple signatures without using OP_CHECKMULTISIG or OP_CHECKMULTISIGVERIFY
A Pubkey script A script included in outputs which sets the conditions that must be fulfilled for those satoshis to be spent. Data for fulfilling the conditions can be provided in a signature script. Pubkey Scripts are called a scriptPubKey in code. Not to be confused with: Pubkey (a public key, which can be used as part of a pubkey script but don’t provide a programmable authentication mechanism), Signature script (a script that provides data to the pubkey script)
A value related to a public key which could only have reasonably been created by someone who has the private key that created that public key. Used in Bitcoin to authorize spending satoshis previously sent to a public key.
Not to be confused with: P2SH Multisig A pubkey script that provides n number of pubkeys and requires the corresponding signature script provide m minimum number signatures corresponding to the provided pubkeys. Not to be confused with: P2SH multisig (a multisig script contained inside P2SH), Advanced scripts that require multiple signatures without using OP_CHECKMULTISIG or OP_CHECKMULTISIGVERIFY
A pubkey script that provides n number of pubkeys and requires the corresponding signature script provide m minimum number signatures corresponding to the provided pubkeys.
Not to be confused with: P2SH multisig (a multisig script contained inside P2SH), Advanced scripts that require multiple signatures without using OP_CHECKMULTISIG or OP_CHECKMULTISIGVERIFY
nBitsThe target is the threshold below which a block header hash must be in order for the block to be valid, and nBits is the encoded form of the target threshold as it appears in the block header.
Not to be confused with: Difficulty (a number measuring the difficulty of finding a header hash relative to the difficulty of finding a header hash with the easiest target)
#
The target is the threshold below which a block header hash must be in order for the block to be valid, and nBits is the encoded form of the target threshold as it appears in the block header.
Not to be confused with: Difficulty (a number measuring the difficulty of finding a header hash relative to the difficulty of finding a header hash with the easiest target)
TargetThe target is the threshold below which a block header hash must be in order for the block to be valid, and nBits is the encoded form of the target threshold as it appears in the block header.
Not to be confused with: Difficulty (a number measuring the difficulty of finding a header hash relative to the difficulty of finding a header hash with the easiest target)
#
The target is the threshold below which a block header hash must be in order for the block to be valid, and nBits is the encoded form of the target threshold as it appears in the block header.
Not to be confused with: Difficulty (a number measuring the difficulty of finding a header hash relative to the difficulty of finding a header hash with the easiest target)
The Target The target is the threshold below which a block header hash must be in order for the block to be valid, and nBits is the encoded form of the target threshold as it appears in the block header. Not to be confused with: Difficulty (a number measuring the difficulty of finding a header hash relative to the difficulty of finding a header hash with the easiest target)
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
An 80-byte header belonging to a single block which is hashed repeatedly to create proof of work.
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
The target is the threshold below which a block header hash must be in order for the block to be valid, and nBits is the encoded form of the target threshold as it appears in the block header.
Not to be confused with: Difficulty (a number measuring the difficulty of finding a header hash relative to the difficulty of finding a header hash with the easiest target)
The target is the threshold below which a block header hash must be in order for the block to be valid, and nBits is the encoded form of the target threshold as it appears in the block header.
Not to be confused with: Difficulty (a number measuring the difficulty of finding a header hash relative to the difficulty of finding a header hash with the easiest target)
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
An 80-byte header belonging to a single block which is hashed repeatedly to create proof of work.
Not to be confused with: Difficulty How difficult it is to find a block relative to the difficulty of finding the easiest possible block. The easiest possible block has a proof-of-work difficulty of 1. Not to be confused with: Target threshold (the value from which difficulty is calculated)
How difficult it is to find a block relative to the difficulty of finding the easiest possible block. The easiest possible block has a proof-of-work difficulty of 1.
Not to be confused with: Target threshold (the value from which difficulty is calculated)
An 80-byte header belonging to a single block which is hashed repeatedly to create proof of work.
How difficult it is to find a block relative to the difficulty of finding the easiest possible block. The easiest possible block has a proof-of-work difficulty of 1.
Not to be confused with: Target threshold (the value from which difficulty is calculated)
An 80-byte header belonging to a single block which is hashed repeatedly to create proof of work.
The target is the threshold below which a block header hash must be in order for the block to be valid, and nBits is the encoded form of the target threshold as it appears in the block header.
Not to be confused with: Difficulty (a number measuring the difficulty of finding a header hash relative to the difficulty of finding a header hash with the easiest target)
NodeA computer that connects to the Bitcoin network.
Not to be confused with: Lightweight node, SPV node
#
A computer that connects to the Bitcoin network.
Not to be confused with: Lightweight node, SPV node
Full nodeA computer that connects to the Bitcoin network.
Not to be confused with: Lightweight node, SPV node
#
A computer that connects to the Bitcoin network.
Not to be confused with: Lightweight node, SPV node
Archival nodeA computer that connects to the Bitcoin network.
Not to be confused with: Lightweight node, SPV node
#
A computer that connects to the Bitcoin network.
Not to be confused with: Lightweight node, SPV node
Pruned NodeA computer that connects to the Bitcoin network.
Not to be confused with: Lightweight node, SPV node
#
A computer that connects to the Bitcoin network.
Not to be confused with: Lightweight node, SPV node
PeerA computer that connects to the Bitcoin network.
Not to be confused with: Lightweight node, SPV node
#
A computer that connects to the Bitcoin network.
Not to be confused with: Lightweight node, SPV node
A computer that connects to the Bitcoin network.
Not to be confused with: Lightweight Node A computer that connects to the Bitcoin network. Not to be confused with: Lightweight node, SPV node
A method for verifying if particular transactions are included in a block without downloading the entire block. The method is used by some lightweight Bitcoin clients.
A computer that connects to the Bitcoin network.
Not to be confused with: Lightweight node, SPV node
Null data transactionA transaction type relayed and mined by default in Bitcoin Core 0.9.0 and later that adds arbitrary data to a provably unspendable pubkey script that full nodes don’t have to store in their UTXO database.
Not to be confused with: OP_RETURN (an opcode used in one of the outputs in an OP_RETURN transaction)
#
A transaction type relayed and mined by default in Bitcoin Core 0.9.0 and later that adds arbitrary data to a provably unspendable pubkey script that full nodes don’t have to store in their UTXO database.
Not to be confused with: OP_RETURN (an opcode used in one of the outputs in an OP_RETURN transaction)
OP_RETURN transactionA transaction type relayed and mined by default in Bitcoin Core 0.9.0 and later that adds arbitrary data to a provably unspendable pubkey script that full nodes don’t have to store in their UTXO database.
Not to be confused with: OP_RETURN (an opcode used in one of the outputs in an OP_RETURN transaction)
#
A transaction type relayed and mined by default in Bitcoin Core 0.9.0 and later that adds arbitrary data to a provably unspendable pubkey script that full nodes don’t have to store in their UTXO database.
Not to be confused with: OP_RETURN (an opcode used in one of the outputs in an OP_RETURN transaction)
Data carrier transactionA transaction type relayed and mined by default in Bitcoin Core 0.9.0 and later that adds arbitrary data to a provably unspendable pubkey script that full nodes don’t have to store in their UTXO database.
Not to be confused with: OP_RETURN (an opcode used in one of the outputs in an OP_RETURN transaction)
#
A transaction type relayed and mined by default in Bitcoin Core 0.9.0 and later that adds arbitrary data to a provably unspendable pubkey script that full nodes don’t have to store in their UTXO database.
Not to be confused with: OP_RETURN (an opcode used in one of the outputs in an OP_RETURN transaction)
A transaction type relayed and mined by default in Bitcoin Core 0.9.0 and later that adds arbitrary data to a provably unspendable Pubkey script A script included in outputs which sets the conditions that must be fulfilled for those satoshis to be spent. Data for fulfilling the conditions can be provided in a signature script. Pubkey Scripts are called a scriptPubKey in code. Not to be confused with: Pubkey (a public key, which can be used as part of a pubkey script but don’t provide a programmable authentication mechanism), Signature script (a script that provides data to the pubkey script)
An Unspent Transaction Output (UTXO) that can be spent as an input in a new transaction.
Not to be confused with: Output (any output, whether spent or not. Outputs are a superset of UTXOs)
Not to be confused with: OP_RETURN (an Opcode Operation codes from the Bitcoin Script language which push data or perform functions within a pubkey script or signature script.
A transaction type relayed and mined by default in Bitcoin Core 0.9.0 and later that adds arbitrary data to a provably unspendable pubkey script that full nodes don’t have to store in their UTXO database.
Not to be confused with: OP_RETURN (an opcode used in one of the outputs in an OP_RETURN transaction)
OpcodeOperation codes from the Bitcoin Script language which push data or perform functions within a pubkey script or signature script.
#
Operation codes from the Bitcoin Script language which push data or perform functions within a pubkey script or signature script.
Data-pushing opcodeOperation codes from the Bitcoin Script language which push data or perform functions within a pubkey script or signature script.
#
Operation codes from the Bitcoin Script language which push data or perform functions within a pubkey script or signature script.
Non-Data-pushing opcodeOperation codes from the Bitcoin Script language which push data or perform functions within a pubkey script or signature script.
#
Operation codes from the Bitcoin Script language which push data or perform functions within a pubkey script or signature script.
Operation codes from the Bitcoin Script language which push data or perform functions within a Pubkey script A script included in outputs which sets the conditions that must be fulfilled for those satoshis to be spent. Data for fulfilling the conditions can be provided in a signature script. Pubkey Scripts are called a scriptPubKey in code. Not to be confused with: Pubkey (a public key, which can be used as part of a pubkey script but don’t provide a programmable authentication mechanism), Signature script (a script that provides data to the pubkey script)
A value related to a public key which could only have reasonably been created by someone who has the private key that created that public key. Used in Bitcoin to authorize spending satoshis previously sent to a public key.
Orphan BlockOne or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
#
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
Blocks whose parent Block One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
A computer that connects to the Bitcoin network.
Not to be confused with: Lightweight node, SPV node
Not to be confused with: Stale Block One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
OutpointThe data structure used to refer to a particular transaction output, consisting of a 32-byte TXID and a 4-byte output index number (vout).
Not to be confused with: Output (an entire output from a transaction), TxOut (same as output)
#
The data structure used to refer to a particular transaction output, consisting of a 32-byte TXID and a 4-byte output index number (vout).
Not to be confused with: Output (an entire output from a transaction), TxOut (same as output)
The data structure used to refer to a particular transaction Output An output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent. Not to be confused with: Outpoint (a reference to a particular output)
An identifier used to uniquely identify a particular transaction; specifically, the sha256d hash of the transaction.
Not to be confused with: Outpoint (the combination of a txid with a vout used to identify a specific output)
An output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent.
Not to be confused with: Outpoint (a reference to a particular output)
Not to be confused with: Output An output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent. Not to be confused with: Outpoint (a reference to a particular output)
An output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent.
Not to be confused with: Outpoint (a reference to a particular output)
An output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent.
Not to be confused with: Outpoint (a reference to a particular output)
An output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent.
Not to be confused with: Outpoint (a reference to a particular output)
OutputAn output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent.
Not to be confused with: Outpoint (a reference to a particular output)
#
An output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent.
Not to be confused with: Outpoint (a reference to a particular output)
TxOutAn output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent.
Not to be confused with: Outpoint (a reference to a particular output)
#
An output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent.
Not to be confused with: Outpoint (a reference to a particular output)
An Output An output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent. Not to be confused with: Outpoint (a reference to a particular output)
Denominations of Bitcoin value, usually measured in fractions of a bitcoin but sometimes measured in multiples of a satoshi. One bitcoin equals 100,000,000 satoshis.
Not to be confused with: Binary bits, a unit of data with two possible values
A script included in outputs which sets the conditions that must be fulfilled for those satoshis to be spent. Data for fulfilling the conditions can be provided in a signature script. Pubkey Scripts are called a scriptPubKey in code.
Not to be confused with: Pubkey (a public key, which can be used as part of a pubkey script but don’t provide a programmable authentication mechanism), Signature script (a script that provides data to the pubkey script)
Denominations of Bitcoin value, usually measured in fractions of a bitcoin but sometimes measured in multiples of a satoshi. One bitcoin equals 100,000,000 satoshis.
Not to be confused with: Binary bits, a unit of data with two possible values
Not to be confused with: Outpoint The data structure used to refer to a particular transaction output, consisting of a 32-byte TXID and a 4-byte output index number (vout). Not to be confused with: Output (an entire output from a transaction), TxOut (same as output)
An output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent.
Not to be confused with: Outpoint (a reference to a particular output)
P2PKH AddressA 20-byte hash formatted using base58check to produce either a P2PKH or P2SH Bitcoin address. Currently the most common way users exchange payment information.
Not to be confused with: IP address
#
A 20-byte hash formatted using base58check to produce either a P2PKH or P2SH Bitcoin address. Currently the most common way users exchange payment information.
Not to be confused with: IP address
P2PKH OutputAn output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent.
Not to be confused with: Outpoint (a reference to a particular output)
#
An output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent.
Not to be confused with: Outpoint (a reference to a particular output)
A Bitcoin payment Address A 20-byte hash formatted using base58check to produce either a P2PKH or P2SH Bitcoin address. Currently the most common way users exchange payment information. Not to be confused with: IP address
The public portion of a keypair which can be used to verify signatures made with the private portion of the keypair.
Not to be confused with: Private key (data from which the public key is derived), Parent key (a key used to create child keys, not necessarily a public key)
A script included in outputs which sets the conditions that must be fulfilled for those satoshis to be spent. Data for fulfilling the conditions can be provided in a signature script. Pubkey Scripts are called a scriptPubKey in code.
Not to be confused with: Pubkey (a public key, which can be used as part of a pubkey script but don’t provide a programmable authentication mechanism), Signature script (a script that provides data to the pubkey script)
Not to be confused with: P2PK Output An output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent. Not to be confused with: Outpoint (a reference to a particular output)
An output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent.
Not to be confused with: Outpoint (a reference to a particular output)
The public portion of a keypair which can be used to verify signatures made with the private portion of the keypair.
Not to be confused with: Private key (data from which the public key is derived), Parent key (a key used to create child keys, not necessarily a public key)
A 20-byte hash formatted using base58check to produce either a P2PKH or P2SH Bitcoin address. Currently the most common way users exchange payment information.
Not to be confused with: IP address
An output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent.
Not to be confused with: Outpoint (a reference to a particular output)
A 20-byte hash formatted using base58check to produce either a P2PKH or P2SH Bitcoin address. Currently the most common way users exchange payment information.
Not to be confused with: IP address
An output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent.
Not to be confused with: Outpoint (a reference to a particular output)
P2SH AddressA 20-byte hash formatted using base58check to produce either a P2PKH or P2SH Bitcoin address. Currently the most common way users exchange payment information.
Not to be confused with: IP address
#
A 20-byte hash formatted using base58check to produce either a P2PKH or P2SH Bitcoin address. Currently the most common way users exchange payment information.
Not to be confused with: IP address
P2SH OutputAn output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent.
Not to be confused with: Outpoint (a reference to a particular output)
#
An output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent.
Not to be confused with: Outpoint (a reference to a particular output)
A Bitcoin payment Address A 20-byte hash formatted using base58check to produce either a P2PKH or P2SH Bitcoin address. Currently the most common way users exchange payment information. Not to be confused with: IP address
A script included in outputs which sets the conditions that must be fulfilled for those satoshis to be spent. Data for fulfilling the conditions can be provided in a signature script. Pubkey Scripts are called a scriptPubKey in code.
Not to be confused with: Pubkey (a public key, which can be used as part of a pubkey script but don’t provide a programmable authentication mechanism), Signature script (a script that provides data to the pubkey script)
A script included in outputs which sets the conditions that must be fulfilled for those satoshis to be spent. Data for fulfilling the conditions can be provided in a signature script. Pubkey Scripts are called a scriptPubKey in code.
Not to be confused with: Pubkey (a public key, which can be used as part of a pubkey script but don’t provide a programmable authentication mechanism), Signature script (a script that provides data to the pubkey script)
Not to be confused with: P2PK Output An output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent. Not to be confused with: Outpoint (a reference to a particular output)
An output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent.
Not to be confused with: Outpoint (a reference to a particular output)
The public portion of a keypair which can be used to verify signatures made with the private portion of the keypair.
Not to be confused with: Private key (data from which the public key is derived), Parent key (a key used to create child keys, not necessarily a public key)
A 20-byte hash formatted using base58check to produce either a P2PKH or P2SH Bitcoin address. Currently the most common way users exchange payment information.
Not to be confused with: IP address
An output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent.
Not to be confused with: Outpoint (a reference to a particular output)
A 20-byte hash formatted using base58check to produce either a P2PKH or P2SH Bitcoin address. Currently the most common way users exchange payment information.
Not to be confused with: IP address
An output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent.
Not to be confused with: Outpoint (a reference to a particular output)
A pubkey script that provides n number of pubkeys and requires the corresponding signature script provide m minimum number signatures corresponding to the provided pubkeys.
Not to be confused with: P2SH multisig (a multisig script contained inside P2SH), Advanced scripts that require multiple signatures without using OP_CHECKMULTISIG or OP_CHECKMULTISIGVERIFY
A pubkey script that provides n number of pubkeys and requires the corresponding signature script provide m minimum number signatures corresponding to the provided pubkeys.
Not to be confused with: P2SH multisig (a multisig script contained inside P2SH), Advanced scripts that require multiple signatures without using OP_CHECKMULTISIG or OP_CHECKMULTISIGVERIFY
Operation codes from the Bitcoin Script language which push data or perform functions within a pubkey script or signature script.
P2SH MultisigA pubkey script that provides n number of pubkeys and requires the corresponding signature script provide m minimum number signatures corresponding to the provided pubkeys.
Not to be confused with: P2SH multisig (a multisig script contained inside P2SH), Advanced scripts that require multiple signatures without using OP_CHECKMULTISIG or OP_CHECKMULTISIGVERIFY
#
A pubkey script that provides n number of pubkeys and requires the corresponding signature script provide m minimum number signatures corresponding to the provided pubkeys.
Not to be confused with: P2SH multisig (a multisig script contained inside P2SH), Advanced scripts that require multiple signatures without using OP_CHECKMULTISIG or OP_CHECKMULTISIGVERIFY
A P2SH Output An output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent. Not to be confused with: Outpoint (a reference to a particular output)
A script similar in function to a pubkey script. One copy of it is hashed to create a P2SH address (used in an actual pubkey script) and another copy is placed in the spending signature script to enforce its conditions.
Not to be confused with: Signature script (a script that provides data to the pubkey script, which includes the redeem script in a P2SH input)
A pubkey script that provides n number of pubkeys and requires the corresponding signature script provide m minimum number signatures corresponding to the provided pubkeys.
Not to be confused with: P2SH multisig (a multisig script contained inside P2SH), Advanced scripts that require multiple signatures without using OP_CHECKMULTISIG or OP_CHECKMULTISIGVERIFY
A pubkey script that provides n number of pubkeys and requires the corresponding signature script provide m minimum number signatures corresponding to the provided pubkeys.
Not to be confused with: P2SH multisig (a multisig script contained inside P2SH), Advanced scripts that require multiple signatures without using OP_CHECKMULTISIG or OP_CHECKMULTISIGVERIFY
Not to be confused with: Multisig A pubkey script that provides n number of pubkeys and requires the corresponding signature script provide m minimum number signatures corresponding to the provided pubkeys. Not to be confused with: P2SH multisig (a multisig script contained inside P2SH), Advanced scripts that require multiple signatures without using OP_CHECKMULTISIG or OP_CHECKMULTISIGVERIFY
A pubkey script that provides n number of pubkeys and requires the corresponding signature script provide m minimum number signatures corresponding to the provided pubkeys.
Not to be confused with: P2SH multisig (a multisig script contained inside P2SH), Advanced scripts that require multiple signatures without using OP_CHECKMULTISIG or OP_CHECKMULTISIGVERIFY
A pubkey script that provides n number of pubkeys and requires the corresponding signature script provide m minimum number signatures corresponding to the provided pubkeys.
Not to be confused with: P2SH multisig (a multisig script contained inside P2SH), Advanced scripts that require multiple signatures without using OP_CHECKMULTISIG or OP_CHECKMULTISIGVERIFY
A pubkey script that provides n number of pubkeys and requires the corresponding signature script provide m minimum number signatures corresponding to the provided pubkeys.
Not to be confused with: P2SH multisig (a multisig script contained inside P2SH), Advanced scripts that require multiple signatures without using OP_CHECKMULTISIG or OP_CHECKMULTISIGVERIFY
Parent keyIn HD wallets, a key used to derive child keys. The key can be either a private key or a public key, and the key derivation may also require a chain code.
Not to be confused with: Public key (derived from a private key, not a parent key)
#
In HD wallets, a key used to derive child keys. The key can be either a private key or a public key, and the key derivation may also require a chain code.
Not to be confused with: Public key (derived from a private key, not a parent key)
Parent public keyIn HD wallets, a key used to derive child keys. The key can be either a private key or a public key, and the key derivation may also require a chain code.
Not to be confused with: Public key (derived from a private key, not a parent key)
#
In HD wallets, a key used to derive child keys. The key can be either a private key or a public key, and the key derivation may also require a chain code.
Not to be confused with: Public key (derived from a private key, not a parent key)
Parent private keyIn HD wallets, a key used to derive child keys. The key can be either a private key or a public key, and the key derivation may also require a chain code.
Not to be confused with: Public key (derived from a private key, not a parent key)
#
In HD wallets, a key used to derive child keys. The key can be either a private key or a public key, and the key derivation may also require a chain code.
Not to be confused with: Public key (derived from a private key, not a parent key)
In HD wallets, a key used to derive child keys. The key can be either a Private key The private portion of a keypair which can create signatures that other people can verify using the public key. Not to be confused with: Public key (data derived from the private key), Parent key (a key used to create child keys, not necessarily a private key)
The public portion of a keypair which can be used to verify signatures made with the private portion of the keypair.
Not to be confused with: Private key (data from which the public key is derived), Parent key (a key used to create child keys, not necessarily a public key)
In HD wallets, 256 bits of entropy added to the public and private keys to help them generate secure child keys; the master chain code is usually derived from a seed along with the master private key
Not to be confused with: Public key The public portion of a keypair which can be used to verify signatures made with the private portion of the keypair. Not to be confused with: Private key (data from which the public key is derived), Parent key (a key used to create child keys, not necessarily a public key)
The private portion of a keypair which can create signatures that other people can verify using the public key.
Not to be confused with: Public key (data derived from the private key), Parent key (a key used to create child keys, not necessarily a private key)
In HD wallets, a key used to derive child keys. The key can be either a private key or a public key, and the key derivation may also require a chain code.
Not to be confused with: Public key (derived from a private key, not a parent key)
Payment protocolThe deprecated protocol defined in BIP70 (and other BIPs) which lets spenders get signed payment details from receivers.
Not to be confused with: IP-to-IP payment protocol (an insecure, discontinued protocol included in early versions of Bitcoin)
#
The deprecated protocol defined in BIP70 (and other BIPs) which lets spenders get signed payment details from receivers.
Not to be confused with: IP-to-IP payment protocol (an insecure, discontinued protocol included in early versions of Bitcoin)
Payment requestThe deprecated protocol defined in BIP70 (and other BIPs) which lets spenders get signed payment details from receivers.
Not to be confused with: IP-to-IP payment protocol (an insecure, discontinued protocol included in early versions of Bitcoin)
#
The deprecated protocol defined in BIP70 (and other BIPs) which lets spenders get signed payment details from receivers.
Not to be confused with: IP-to-IP payment protocol (an insecure, discontinued protocol included in early versions of Bitcoin)
The deprecated protocol defined in BIP70 (and other BIPs) which lets spenders get signed payment details from receivers.
Not to be confused with: IP-to-IP Payment protocol The deprecated protocol defined in BIP70 (and other BIPs) which lets spenders get signed payment details from receivers. Not to be confused with: IP-to-IP payment protocol (an insecure, discontinued protocol included in early versions of Bitcoin)
Private keyThe private portion of a keypair which can create signatures that other people can verify using the public key.
Not to be confused with: Public key (data derived from the private key), Parent key (a key used to create child keys, not necessarily a private key)
#
The private portion of a keypair which can create signatures that other people can verify using the public key.
Not to be confused with: Public key (data derived from the private key), Parent key (a key used to create child keys, not necessarily a private key)
The private portion of a keypair which can create signatures that other people can verify using the Public key The public portion of a keypair which can be used to verify signatures made with the private portion of the keypair. Not to be confused with: Private key (data from which the public key is derived), Parent key (a key used to create child keys, not necessarily a public key)
Not to be confused with: Public key The public portion of a keypair which can be used to verify signatures made with the private portion of the keypair. Not to be confused with: Private key (data from which the public key is derived), Parent key (a key used to create child keys, not necessarily a public key)
The private portion of a keypair which can create signatures that other people can verify using the public key.
Not to be confused with: Public key (data derived from the private key), Parent key (a key used to create child keys, not necessarily a private key)
In HD wallets, a key used to derive child keys. The key can be either a private key or a public key, and the key derivation may also require a chain code.
Not to be confused with: Public key (derived from a private key, not a parent key)
The private portion of a keypair which can create signatures that other people can verify using the public key.
Not to be confused with: Public key (data derived from the private key), Parent key (a key used to create child keys, not necessarily a private key)
Proof of workA hash below a target value which can only be obtained, on average, by performing a certain amount of brute force work—therefore demonstrating proof of work.
#
A hash below a target value which can only be obtained, on average, by performing a certain amount of brute force work—therefore demonstrating proof of work.
POWA hash below a target value which can only be obtained, on average, by performing a certain amount of brute force work—therefore demonstrating proof of work.
#
A hash below a target value which can only be obtained, on average, by performing a certain amount of brute force work—therefore demonstrating proof of work.
A hash below a Target The target is the threshold below which a block header hash must be in order for the block to be valid, and nBits is the encoded form of the target threshold as it appears in the block header. Not to be confused with: Difficulty (a number measuring the difficulty of finding a header hash relative to the difficulty of finding a header hash with the easiest target)
A hash below a target value which can only be obtained, on average, by performing a certain amount of brute force work—therefore demonstrating proof of work.
Pubkey scriptA script included in outputs which sets the conditions that must be fulfilled for those satoshis to be spent. Data for fulfilling the conditions can be provided in a signature script. Pubkey Scripts are called a scriptPubKey in code.
Not to be confused with: Pubkey (a public key, which can be used as part of a pubkey script but don’t provide a programmable authentication mechanism), Signature script (a script that provides data to the pubkey script)
#
A script included in outputs which sets the conditions that must be fulfilled for those satoshis to be spent. Data for fulfilling the conditions can be provided in a signature script. Pubkey Scripts are called a scriptPubKey in code.
Not to be confused with: Pubkey (a public key, which can be used as part of a pubkey script but don’t provide a programmable authentication mechanism), Signature script (a script that provides data to the pubkey script)
ScriptPubKeyA script included in outputs which sets the conditions that must be fulfilled for those satoshis to be spent. Data for fulfilling the conditions can be provided in a signature script. Pubkey Scripts are called a scriptPubKey in code.
Not to be confused with: Pubkey (a public key, which can be used as part of a pubkey script but don’t provide a programmable authentication mechanism), Signature script (a script that provides data to the pubkey script)
#
A script included in outputs which sets the conditions that must be fulfilled for those satoshis to be spent. Data for fulfilling the conditions can be provided in a signature script. Pubkey Scripts are called a scriptPubKey in code.
Not to be confused with: Pubkey (a public key, which can be used as part of a pubkey script but don’t provide a programmable authentication mechanism), Signature script (a script that provides data to the pubkey script)
A script included in outputs which sets the conditions that must be fulfilled for those Satoshis Denominations of Bitcoin value, usually measured in fractions of a bitcoin but sometimes measured in multiples of a satoshi. One bitcoin equals 100,000,000 satoshis. Not to be confused with: Binary bits, a unit of data with two possible values
A value related to a public key which could only have reasonably been created by someone who has the private key that created that public key. Used in Bitcoin to authorize spending satoshis previously sent to a public key.
A script included in outputs which sets the conditions that must be fulfilled for those satoshis to be spent. Data for fulfilling the conditions can be provided in a signature script. Pubkey Scripts are called a scriptPubKey in code.
Not to be confused with: Pubkey (a public key, which can be used as part of a pubkey script but don’t provide a programmable authentication mechanism), Signature script (a script that provides data to the pubkey script)
Not to be confused with: Pubkey (a Public key The public portion of a keypair which can be used to verify signatures made with the private portion of the keypair. Not to be confused with: Private key (data from which the public key is derived), Parent key (a key used to create child keys, not necessarily a public key)
A script included in outputs which sets the conditions that must be fulfilled for those satoshis to be spent. Data for fulfilling the conditions can be provided in a signature script. Pubkey Scripts are called a scriptPubKey in code.
Not to be confused with: Pubkey (a public key, which can be used as part of a pubkey script but don’t provide a programmable authentication mechanism), Signature script (a script that provides data to the pubkey script)
A value related to a public key which could only have reasonably been created by someone who has the private key that created that public key. Used in Bitcoin to authorize spending satoshis previously sent to a public key.
A script included in outputs which sets the conditions that must be fulfilled for those satoshis to be spent. Data for fulfilling the conditions can be provided in a signature script. Pubkey Scripts are called a scriptPubKey in code.
Not to be confused with: Pubkey (a public key, which can be used as part of a pubkey script but don’t provide a programmable authentication mechanism), Signature script (a script that provides data to the pubkey script)
Public keyThe public portion of a keypair which can be used to verify signatures made with the private portion of the keypair.
Not to be confused with: Private key (data from which the public key is derived), Parent key (a key used to create child keys, not necessarily a public key)
#
The public portion of a keypair which can be used to verify signatures made with the private portion of the keypair.
Not to be confused with: Private key (data from which the public key is derived), Parent key (a key used to create child keys, not necessarily a public key)
The public portion of a keypair which can be used to verify signatures made with the private portion of the keypair.
Not to be confused with: Private key The private portion of a keypair which can create signatures that other people can verify using the public key. Not to be confused with: Public key (data derived from the private key), Parent key (a key used to create child keys, not necessarily a private key)
The public portion of a keypair which can be used to verify signatures made with the private portion of the keypair.
Not to be confused with: Private key (data from which the public key is derived), Parent key (a key used to create child keys, not necessarily a public key)
In HD wallets, a key used to derive child keys. The key can be either a private key or a public key, and the key derivation may also require a chain code.
Not to be confused with: Public key (derived from a private key, not a parent key)
The public portion of a keypair which can be used to verify signatures made with the private portion of the keypair.
Not to be confused with: Private key (data from which the public key is derived), Parent key (a key used to create child keys, not necessarily a public key)
Replace by feeReplacing one version of an unconfirmed transaction with a different version of the transaction that pays a higher transaction fee. May use BIP125 signaling.
Not to be confused with: Child pays for parent, CPFP
#
Replacing one version of an unconfirmed transaction with a different version of the transaction that pays a higher transaction fee. May use BIP125 signaling.
Not to be confused with: Child pays for parent, CPFP
RBFReplacing one version of an unconfirmed transaction with a different version of the transaction that pays a higher transaction fee. May use BIP125 signaling.
Not to be confused with: Child pays for parent, CPFP
#
Replacing one version of an unconfirmed transaction with a different version of the transaction that pays a higher transaction fee. May use BIP125 signaling.
Not to be confused with: Child pays for parent, CPFP
Opt-in replace by feeReplacing one version of an unconfirmed transaction with a different version of the transaction that pays a higher transaction fee. May use BIP125 signaling.
Not to be confused with: Child pays for parent, CPFP
#
Replacing one version of an unconfirmed transaction with a different version of the transaction that pays a higher transaction fee. May use BIP125 signaling.
Not to be confused with: Child pays for parent, CPFP
Replacing one version of an Unconfirmed transaction A score indicating the number of blocks on the best block chain that would need to be modified to remove or modify a particular transaction. A confirmed transaction has a confirmation score of one or higher.
The amount remaining when the value of all outputs in a transaction are subtracted from all inputs in a transaction; the fee is paid to the miner who includes that transaction in a block.
Not to be confused with: Minimum relay fee (the lowest fee a transaction must pay to be accepted into the memory pool and relayed by Bitcoin Core nodes)
Not to be confused with: Child pays for parent Selecting transactions for mining not just based on their fees but also based on the fees of their ancestors (parents) and descendants (children). Not to be confused with: Replace by Fee, RBF
Selecting transactions for mining not just based on their fees but also based on the fees of their ancestors (parents) and descendants (children).
Not to be confused with: Replace by Fee, RBF
Redeem scriptA script similar in function to a pubkey script. One copy of it is hashed to create a P2SH address (used in an actual pubkey script) and another copy is placed in the spending signature script to enforce its conditions.
Not to be confused with: Signature script (a script that provides data to the pubkey script, which includes the redeem script in a P2SH input)
#
A script similar in function to a pubkey script. One copy of it is hashed to create a P2SH address (used in an actual pubkey script) and another copy is placed in the spending signature script to enforce its conditions.
Not to be confused with: Signature script (a script that provides data to the pubkey script, which includes the redeem script in a P2SH input)
RedeemScriptA script similar in function to a pubkey script. One copy of it is hashed to create a P2SH address (used in an actual pubkey script) and another copy is placed in the spending signature script to enforce its conditions.
Not to be confused with: Signature script (a script that provides data to the pubkey script, which includes the redeem script in a P2SH input)
#
A script similar in function to a pubkey script. One copy of it is hashed to create a P2SH address (used in an actual pubkey script) and another copy is placed in the spending signature script to enforce its conditions.
Not to be confused with: Signature script (a script that provides data to the pubkey script, which includes the redeem script in a P2SH input)
A script similar in function to a Pubkey script A script included in outputs which sets the conditions that must be fulfilled for those satoshis to be spent. Data for fulfilling the conditions can be provided in a signature script. Pubkey Scripts are called a scriptPubKey in code. Not to be confused with: Pubkey (a public key, which can be used as part of a pubkey script but don’t provide a programmable authentication mechanism), Signature script (a script that provides data to the pubkey script)
A 20-byte hash formatted using base58check to produce either a P2PKH or P2SH Bitcoin address. Currently the most common way users exchange payment information.
Not to be confused with: IP address
A script included in outputs which sets the conditions that must be fulfilled for those satoshis to be spent. Data for fulfilling the conditions can be provided in a signature script. Pubkey Scripts are called a scriptPubKey in code.
Not to be confused with: Pubkey (a public key, which can be used as part of a pubkey script but don’t provide a programmable authentication mechanism), Signature script (a script that provides data to the pubkey script)
A value related to a public key which could only have reasonably been created by someone who has the private key that created that public key. Used in Bitcoin to authorize spending satoshis previously sent to a public key.
Not to be confused with: Signature A value related to a public key which could only have reasonably been created by someone who has the private key that created that public key. Used in Bitcoin to authorize spending satoshis previously sent to a public key.
A script included in outputs which sets the conditions that must be fulfilled for those satoshis to be spent. Data for fulfilling the conditions can be provided in a signature script. Pubkey Scripts are called a scriptPubKey in code.
Not to be confused with: Pubkey (a public key, which can be used as part of a pubkey script but don’t provide a programmable authentication mechanism), Signature script (a script that provides data to the pubkey script)
A script similar in function to a pubkey script. One copy of it is hashed to create a P2SH address (used in an actual pubkey script) and another copy is placed in the spending signature script to enforce its conditions.
Not to be confused with: Signature script (a script that provides data to the pubkey script, which includes the redeem script in a P2SH input)
An input in a transaction which contains three fields: an outpoint, a signature script, and a sequence number. The outpoint references a previous output and the signature script allows spending it.
RegtestA local testing environment in which developers can almost instantly generate blocks on demand for testing events, and can create private satoshis with no real-world value.
Not to be confused with: Testnet (a global testing environment which mostly mimics mainnet)
#
A local testing environment in which developers can almost instantly generate blocks on demand for testing events, and can create private satoshis with no real-world value.
Not to be confused with: Testnet (a global testing environment which mostly mimics mainnet)
Regression test modeA local testing environment in which developers can almost instantly generate blocks on demand for testing events, and can create private satoshis with no real-world value.
Not to be confused with: Testnet (a global testing environment which mostly mimics mainnet)
#
A local testing environment in which developers can almost instantly generate blocks on demand for testing events, and can create private satoshis with no real-world value.
Not to be confused with: Testnet (a global testing environment which mostly mimics mainnet)
A local testing environment in which developers can almost instantly generate blocks on demand for testing events, and can create private Satoshis Denominations of Bitcoin value, usually measured in fractions of a bitcoin but sometimes measured in multiples of a satoshi. One bitcoin equals 100,000,000 satoshis. Not to be confused with: Binary bits, a unit of data with two possible values
Not to be confused with: Testnet A global testing environment in which developers can obtain and spend satoshis that have no real-world value on a network that is very similar to the Bitcoin mainnet. Not to be confused with: Regtest (a local testing environment where developers can control block generation)
The original and main network for Bitcoin transactions, where satoshis have real economic value.
Not to be confused with: Testnet (an open network very similar to mainnet where satoshis have no value), Regtest (a private testing node similar to testnet)
RPC byte orderA hash digest displayed with the byte order reversed; used in Bitcoin Core RPCs, many block explorers, and other software.
Not to be confused with: Internal byte order (hash digests displayed in their typical order; used in serialized blocks and serialized transactions)
#
A hash digest displayed with the byte order reversed; used in Bitcoin Core RPCs, many block explorers, and other software.
Not to be confused with: Internal byte order (hash digests displayed in their typical order; used in serialized blocks and serialized transactions)
A hash digest displayed with the byte order reversed; used in Bitcoin Core RPCs, many Block One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
Not to be confused with: Internal byte order The standard order in which hash digests are displayed as strings—the same format used in serialized blocks and transactions. Not to be confused with: RPC byte order (where the byte order is reversed)
Sequence numberPart of all transactions. A number intended to allow unconfirmed time-locked transactions to be updated before being finalized; not currently used except to disable locktime in a transaction
Not to be confused with: Output index number / vout (this is the 0-indexed number of an output within a transaction used by a later transaction to refer to that specific output)
#
Part of all transactions. A number intended to allow unconfirmed time-locked transactions to be updated before being finalized; not currently used except to disable locktime in a transaction
Not to be confused with: Output index number / vout (this is the 0-indexed number of an output within a transaction used by a later transaction to refer to that specific output)
Part of all transactions. A number intended to allow unconfirmed time-locked transactions to be updated before being finalized; not currently used except to disable Locktime Part of a transaction which indicates the earliest time or earliest block when that transaction may be added to the block chain.
Not to be confused with: Output An output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent. Not to be confused with: Outpoint (a reference to a particular output)
An output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent.
Not to be confused with: Outpoint (a reference to a particular output)
An output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent.
Not to be confused with: Outpoint (a reference to a particular output)
Serialized BlockOne or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
#
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
A complete Block One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
Serialized transactionComplete transactions in their binary format; often represented using hexadecimal. Sometimes called raw format because of the various Bitcoin Core commands with “raw” in their names.
#
Complete transactions in their binary format; often represented using hexadecimal. Sometimes called raw format because of the various Bitcoin Core commands with “raw” in their names.
Raw transactionComplete transactions in their binary format; often represented using hexadecimal. Sometimes called raw format because of the various Bitcoin Core commands with “raw” in their names.
#
Complete transactions in their binary format; often represented using hexadecimal. Sometimes called raw format because of the various Bitcoin Core commands with “raw” in their names.
Complete transactions in their binary format; often represented using hexadecimal. Sometimes called raw format because of the various Bitcoin Core commands with “raw” in their names.
SIGHASH_ALLDefault signature hash type which signs the entire transaction except any signature scripts, preventing modification of the signed parts.
#
Default signature hash type which signs the entire transaction except any signature scripts, preventing modification of the signed parts.
Default Signature A value related to a public key which could only have reasonably been created by someone who has the private key that created that public key. Used in Bitcoin to authorize spending satoshis previously sent to a public key.
A value related to a public key which could only have reasonably been created by someone who has the private key that created that public key. Used in Bitcoin to authorize spending satoshis previously sent to a public key.
SIGHASH_ANYONECANPAYA signature hash type which signs only the current input.
Not to be confused with: SIGHASH_SINGLE (which signs this input, its corresponding output, and other inputs partially)
#
A signature hash type which signs only the current input.
Not to be confused with: SIGHASH_SINGLE (which signs this input, its corresponding output, and other inputs partially)
A Signature A value related to a public key which could only have reasonably been created by someone who has the private key that created that public key. Used in Bitcoin to authorize spending satoshis previously sent to a public key.
An input in a transaction which contains three fields: an outpoint, a signature script, and a sequence number. The outpoint references a previous output and the signature script allows spending it.
Not to be confused with: SIGHASH_SINGLE Signature hash type that signs the output corresponding to this input (the one with the same index value), this input, and any other inputs partially. Allows modification of other outputs and the sequence number of other inputs. Not to be confused with: SIGHASH_ANYONECANPAY (a flag to signature hash types that only signs this single input)
An input in a transaction which contains three fields: an outpoint, a signature script, and a sequence number. The outpoint references a previous output and the signature script allows spending it.
An output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent.
Not to be confused with: Outpoint (a reference to a particular output)
SIGHASH_NONESignature hash type which only signs the inputs, allowing anyone to change the outputs however they’d like.
#
Signature hash type which only signs the inputs, allowing anyone to change the outputs however they’d like.
Signature A value related to a public key which could only have reasonably been created by someone who has the private key that created that public key. Used in Bitcoin to authorize spending satoshis previously sent to a public key.
SIGHASH_SINGLESignature hash type that signs the output corresponding to this input (the one with the same index value), this input, and any other inputs partially. Allows modification of other outputs and the sequence number of other inputs.
Not to be confused with: SIGHASH_ANYONECANPAY (a flag to signature hash types that only signs this single input)
#
Signature hash type that signs the output corresponding to this input (the one with the same index value), this input, and any other inputs partially. Allows modification of other outputs and the sequence number of other inputs.
Not to be confused with: SIGHASH_ANYONECANPAY (a flag to signature hash types that only signs this single input)
Signature A value related to a public key which could only have reasonably been created by someone who has the private key that created that public key. Used in Bitcoin to authorize spending satoshis previously sent to a public key.
An output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent.
Not to be confused with: Outpoint (a reference to a particular output)
An input in a transaction which contains three fields: an outpoint, a signature script, and a sequence number. The outpoint references a previous output and the signature script allows spending it.
An input in a transaction which contains three fields: an outpoint, a signature script, and a sequence number. The outpoint references a previous output and the signature script allows spending it.
Part of all transactions. A number intended to allow unconfirmed time-locked transactions to be updated before being finalized; not currently used except to disable locktime in a transaction
Not to be confused with: Output index number / vout (this is the 0-indexed number of an output within a transaction used by a later transaction to refer to that specific output)
Not to be confused with: SIGHASH_ANYONECANPAY A signature hash type which signs only the current input. Not to be confused with: SIGHASH_SINGLE (which signs this input, its corresponding output, and other inputs partially)
A value related to a public key which could only have reasonably been created by someone who has the private key that created that public key. Used in Bitcoin to authorize spending satoshis previously sent to a public key.
An input in a transaction which contains three fields: an outpoint, a signature script, and a sequence number. The outpoint references a previous output and the signature script allows spending it.
SignatureA value related to a public key which could only have reasonably been created by someone who has the private key that created that public key. Used in Bitcoin to authorize spending satoshis previously sent to a public key.
#
A value related to a public key which could only have reasonably been created by someone who has the private key that created that public key. Used in Bitcoin to authorize spending satoshis previously sent to a public key.
A value related to a Public key The public portion of a keypair which can be used to verify signatures made with the private portion of the keypair. Not to be confused with: Private key (data from which the public key is derived), Parent key (a key used to create child keys, not necessarily a public key)
The private portion of a keypair which can create signatures that other people can verify using the public key.
Not to be confused with: Public key (data derived from the private key), Parent key (a key used to create child keys, not necessarily a private key)
The public portion of a keypair which can be used to verify signatures made with the private portion of the keypair.
Not to be confused with: Private key (data from which the public key is derived), Parent key (a key used to create child keys, not necessarily a public key)
Denominations of Bitcoin value, usually measured in fractions of a bitcoin but sometimes measured in multiples of a satoshi. One bitcoin equals 100,000,000 satoshis.
Not to be confused with: Binary bits, a unit of data with two possible values
The public portion of a keypair which can be used to verify signatures made with the private portion of the keypair.
Not to be confused with: Private key (data from which the public key is derived), Parent key (a key used to create child keys, not necessarily a public key)
SignatureA value related to a public key which could only have reasonably been created by someone who has the private key that created that public key. Used in Bitcoin to authorize spending satoshis previously sent to a public key.
hash #
A value related to a public key which could only have reasonably been created by someone who has the private key that created that public key. Used in Bitcoin to authorize spending satoshis previously sent to a public key.
SighashA flag to Bitcoin signatures that indicates what parts of the transaction the signature signs. (The default is SIGHASH_ALL.) The unsigned parts of the transaction may be modified.
Not to be confused with: Signed hash (a hash of the data to be signed), Transaction malleability / transaction mutability (although non-default sighash flags do allow optional malleability, malleability comprises any way a transaction may be mutated)
#
A flag to Bitcoin signatures that indicates what parts of the transaction the signature signs. (The default is SIGHASH_ALL.) The unsigned parts of the transaction may be modified.
Not to be confused with: Signed hash (a hash of the data to be signed), Transaction malleability / transaction mutability (although non-default sighash flags do allow optional malleability, malleability comprises any way a transaction may be mutated)
A flag to Bitcoin signatures that indicates what parts of the transaction the Signature A value related to a public key which could only have reasonably been created by someone who has the private key that created that public key. Used in Bitcoin to authorize spending satoshis previously sent to a public key.
Default signature hash type which signs the entire transaction except any signature scripts, preventing modification of the signed parts.
Not to be confused with: Signed hash (a hash of the data to be signed), Transaction malleability The ability of someone to change (mutate) unconfirmed transactions without making them invalid, which changes the transaction’s txid, making child transactions invalid. Not to be confused with: BIP62 (a proposal for an optional new transaction version that reduces the set of known mutations for common transactions)
The ability of someone to change (mutate) unconfirmed transactions without making them invalid, which changes the transaction’s txid, making child transactions invalid.
Not to be confused with: BIP62 (a proposal for an optional new transaction version that reduces the set of known mutations for common transactions)
A flag to Bitcoin signatures that indicates what parts of the transaction the signature signs. (The default is SIGHASH_ALL.) The unsigned parts of the transaction may be modified.
Not to be confused with: Signed hash (a hash of the data to be signed), Transaction malleability / transaction mutability (although non-default sighash flags do allow optional malleability, malleability comprises any way a transaction may be mutated)
SignatureA value related to a public key which could only have reasonably been created by someone who has the private key that created that public key. Used in Bitcoin to authorize spending satoshis previously sent to a public key.
script #
A value related to a public key which could only have reasonably been created by someone who has the private key that created that public key. Used in Bitcoin to authorize spending satoshis previously sent to a public key.
ScriptSigData generated by a spender which is almost always used as variables to satisfy a pubkey script. Signature Scripts are called scriptSig in code.
Not to be confused with: ECDSA signature (a signature, which can be used as part of a pubkey script in addition to other data)
#
Data generated by a spender which is almost always used as variables to satisfy a pubkey script. Signature Scripts are called scriptSig in code.
Not to be confused with: ECDSA signature (a signature, which can be used as part of a pubkey script in addition to other data)
Data generated by a spender which is almost always used as variables to satisfy a Pubkey script A script included in outputs which sets the conditions that must be fulfilled for those satoshis to be spent. Data for fulfilling the conditions can be provided in a signature script. Pubkey Scripts are called a scriptPubKey in code. Not to be confused with: Pubkey (a public key, which can be used as part of a pubkey script but don’t provide a programmable authentication mechanism), Signature script (a script that provides data to the pubkey script)
A value related to a public key which could only have reasonably been created by someone who has the private key that created that public key. Used in Bitcoin to authorize spending satoshis previously sent to a public key.
Data generated by a spender which is almost always used as variables to satisfy a pubkey script. Signature Scripts are called scriptSig in code.
Not to be confused with: ECDSA signature (a signature, which can be used as part of a pubkey script in addition to other data)
Not to be confused with: ECDSA Signature A value related to a public key which could only have reasonably been created by someone who has the private key that created that public key. Used in Bitcoin to authorize spending satoshis previously sent to a public key.
A value related to a public key which could only have reasonably been created by someone who has the private key that created that public key. Used in Bitcoin to authorize spending satoshis previously sent to a public key.
A script included in outputs which sets the conditions that must be fulfilled for those satoshis to be spent. Data for fulfilling the conditions can be provided in a signature script. Pubkey Scripts are called a scriptPubKey in code.
Not to be confused with: Pubkey (a public key, which can be used as part of a pubkey script but don’t provide a programmable authentication mechanism), Signature script (a script that provides data to the pubkey script)
SPVA method for verifying if particular transactions are included in a block without downloading the entire block. The method is used by some lightweight Bitcoin clients.
#
A method for verifying if particular transactions are included in a block without downloading the entire block. The method is used by some lightweight Bitcoin clients.
Simplified Payment VerificationA method for verifying if particular transactions are included in a block without downloading the entire block. The method is used by some lightweight Bitcoin clients.
#
A method for verifying if particular transactions are included in a block without downloading the entire block. The method is used by some lightweight Bitcoin clients.
Lightweight clientA method for verifying if particular transactions are included in a block without downloading the entire block. The method is used by some lightweight Bitcoin clients.
#
A method for verifying if particular transactions are included in a block without downloading the entire block. The method is used by some lightweight Bitcoin clients.
Thin clientA method for verifying if particular transactions are included in a block without downloading the entire block. The method is used by some lightweight Bitcoin clients.
#
A method for verifying if particular transactions are included in a block without downloading the entire block. The method is used by some lightweight Bitcoin clients.
A method for verifying if particular transactions are included in a Block One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
Soft ForkWhen two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
#
When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
A softfork is a change to the bitcoin protocol wherein only previously valid blocks/transactions are made invalid. Since old nodes will recognise the new blocks as valid, a softfork is backward-compatible.
Not to be confused with: Fork When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack. Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
When several nodes (usually most nodes on the network) all have the same blocks in their locally-validated best block chain.
Not to be confused with: Social consensus (often used in discussion among developers to indicate that most people agree with a particular plan), Consensus rules (the rules that allow nodes to maintain consensus)
When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
A hash below a target value which can only be obtained, on average, by performing a certain amount of brute force work—therefore demonstrating proof of work.
When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
When several nodes (usually most nodes on the network) all have the same blocks in their locally-validated best block chain.
Not to be confused with: Social consensus (often used in discussion among developers to indicate that most people agree with a particular plan), Consensus rules (the rules that allow nodes to maintain consensus)
When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
Stale BlockOne or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
#
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
Blocks which were successfully mined but which aren’t included on the current Best block chain A chain of blocks with each block referencing the block that preceded it. The most-difficult-to-recreate chain is the best block chain. Not to be confused with: Header chain
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
The number of blocks preceding a particular block on a block chain. For example, the genesis block has a height of zero because zero block preceded it.
Not to be confused with: Orphan Block One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
Standard TransactionA transaction that passes Bitcoin Core’s IsStandard() and IsStandardTx() tests. Only standard transactions are mined or broadcast by peers running the default Bitcoin Core software.
#
A transaction that passes Bitcoin Core’s IsStandard() and IsStandardTx() tests. Only standard transactions are mined or broadcast by peers running the default Bitcoin Core software.
A transaction that passes Bitcoin Core’s IsStandard() and IsStandardTx() tests. Only standard transactions are mined or broadcast by peers running the default Bitcoin Core software.
Start stringFour defined bytes which start every message in the Bitcoin P2P protocol to allow seeking to the next message.
#
Four defined bytes which start every message in the Bitcoin P2P protocol to allow seeking to the next message.
Network magicFour defined bytes which start every message in the Bitcoin P2P protocol to allow seeking to the next message.
#
Four defined bytes which start every message in the Bitcoin P2P protocol to allow seeking to the next message.
Four defined bytes which start every Message A parameter of bitcoin: URIs which allows the receiver to optionally specify a message to the spender.
A parameter of bitcoin: URIs which allows the receiver to optionally specify a message to the spender.
TestnetA global testing environment in which developers can obtain and spend satoshis that have no real-world value on a network that is very similar to the Bitcoin mainnet.
Not to be confused with: Regtest (a local testing environment where developers can control block generation)
#
A global testing environment in which developers can obtain and spend satoshis that have no real-world value on a network that is very similar to the Bitcoin mainnet.
Not to be confused with: Regtest (a local testing environment where developers can control block generation)
A global testing environment in which developers can obtain and spend Satoshis Denominations of Bitcoin value, usually measured in fractions of a bitcoin but sometimes measured in multiples of a satoshi. One bitcoin equals 100,000,000 satoshis. Not to be confused with: Binary bits, a unit of data with two possible values
The original and main network for Bitcoin transactions, where satoshis have real economic value.
Not to be confused with: Testnet (an open network very similar to mainnet where satoshis have no value), Regtest (a private testing node similar to testnet)
Not to be confused with: Regtest A local testing environment in which developers can almost instantly generate blocks on demand for testing events, and can create private satoshis with no real-world value. Not to be confused with: Testnet (a global testing environment which mostly mimics mainnet)
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
TokenA token is a programmable digital asset with its own codebase that resides on an already existing block chain. Tokens are used to help facilitate the creation of decentralized applications.
Not to be confused with: Bitcoins, Satoshis, Security token, Denominations
#
A token is a programmable digital asset with its own codebase that resides on an already existing block chain. Tokens are used to help facilitate the creation of decentralized applications.
Not to be confused with: Bitcoins, Satoshis, Security token, Denominations
A Token A token is a programmable digital asset with its own codebase that resides on an already existing block chain. Tokens are used to help facilitate the creation of decentralized applications. Not to be confused with: Bitcoins, Satoshis, Security token, Denominations
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
Not to be confused with: Bitcoins Denominations of Bitcoin value, usually measured in fractions of a bitcoin but sometimes measured in multiples of a satoshi. One bitcoin equals 100,000,000 satoshis. Not to be confused with: Binary bits, a unit of data with two possible values
Denominations of Bitcoin value, usually measured in fractions of a bitcoin but sometimes measured in multiples of a satoshi. One bitcoin equals 100,000,000 satoshis.
Not to be confused with: Binary bits, a unit of data with two possible values
A token is a programmable digital asset with its own codebase that resides on an already existing block chain. Tokens are used to help facilitate the creation of decentralized applications.
Not to be confused with: Bitcoins, Satoshis, Security token, Denominations
Transaction feeThe amount remaining when the value of all outputs in a transaction are subtracted from all inputs in a transaction; the fee is paid to the miner who includes that transaction in a block.
Not to be confused with: Minimum relay fee (the lowest fee a transaction must pay to be accepted into the memory pool and relayed by Bitcoin Core nodes)
#
The amount remaining when the value of all outputs in a transaction are subtracted from all inputs in a transaction; the fee is paid to the miner who includes that transaction in a block.
Not to be confused with: Minimum relay fee (the lowest fee a transaction must pay to be accepted into the memory pool and relayed by Bitcoin Core nodes)
Miners feeThe amount remaining when the value of all outputs in a transaction are subtracted from all inputs in a transaction; the fee is paid to the miner who includes that transaction in a block.
Not to be confused with: Minimum relay fee (the lowest fee a transaction must pay to be accepted into the memory pool and relayed by Bitcoin Core nodes)
#
The amount remaining when the value of all outputs in a transaction are subtracted from all inputs in a transaction; the fee is paid to the miner who includes that transaction in a block.
Not to be confused with: Minimum relay fee (the lowest fee a transaction must pay to be accepted into the memory pool and relayed by Bitcoin Core nodes)
The amount remaining when the value of all outputs in a transaction are subtracted from all inputs in a transaction; the fee is paid to the Miner Mining is the act of creating valid Bitcoin blocks, which requires demonstrating proof of work, and miners are devices that mine or people who own those devices.
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
Not to be confused with: Minimum relay fee The minimum transaction fee a transaction must pay (if it isn’t a high-priority transaction) for a full node to relay that transaction to other nodes. There is no one minimum relay fee—each node chooses its own policy. Not to be confused with: Transaction fee (the minimum relay fee is a policy setting that filters out transactions with too-low transaction fees)
TxidAn identifier used to uniquely identify a particular transaction; specifically, the sha256d hash of the transaction.
Not to be confused with: Outpoint (the combination of a txid with a vout used to identify a specific output)
#
An identifier used to uniquely identify a particular transaction; specifically, the sha256d hash of the transaction.
Not to be confused with: Outpoint (the combination of a txid with a vout used to identify a specific output)
An identifier used to uniquely identify a particular transaction; specifically, the sha256d hash of the transaction.
Not to be confused with: Outpoint The data structure used to refer to a particular transaction output, consisting of a 32-byte TXID and a 4-byte output index number (vout). Not to be confused with: Output (an entire output from a transaction), TxOut (same as output)
An identifier used to uniquely identify a particular transaction; specifically, the sha256d hash of the transaction.
Not to be confused with: Outpoint (the combination of a txid with a vout used to identify a specific output)
An output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent.
Not to be confused with: Outpoint (a reference to a particular output)
User-activated soft ForkWhen two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
#
When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
UASFA Soft Fork activated by flag day or node enforcement instead of miner signalling.
Not to be confused with: Miner Activated Soft Fork (a soft fork activated through miner signalling), Fork (a regular fork where all nodes follow the same consensus rules, so the fork is resolved once one chain has more proof of work than another), Hard fork (a permanent divergence in the block chain caused by non-upgraded nodes not following new consensus rules), Soft fork (a temporary divergence in the block chain caused by non-upgraded nodes not following new consensus rules), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers
#
A Soft Fork activated by flag day or node enforcement instead of miner signalling.
Not to be confused with: Miner Activated Soft Fork (a soft fork activated through miner signalling), Fork (a regular fork where all nodes follow the same consensus rules, so the fork is resolved once one chain has more proof of work than another), Hard fork (a permanent divergence in the block chain caused by non-upgraded nodes not following new consensus rules), Soft fork (a temporary divergence in the block chain caused by non-upgraded nodes not following new consensus rules), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers
A Soft Fork When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack. Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
A computer that connects to the Bitcoin network.
Not to be confused with: Lightweight node, SPV node
Mining is the act of creating valid Bitcoin blocks, which requires demonstrating proof of work, and miners are devices that mine or people who own those devices.
Not to be confused with: Miner Mining is the act of creating valid Bitcoin blocks, which requires demonstrating proof of work, and miners are devices that mine or people who own those devices.
When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
Mining is the act of creating valid Bitcoin blocks, which requires demonstrating proof of work, and miners are devices that mine or people who own those devices.
When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
When several nodes (usually most nodes on the network) all have the same blocks in their locally-validated best block chain.
Not to be confused with: Social consensus (often used in discussion among developers to indicate that most people agree with a particular plan), Consensus rules (the rules that allow nodes to maintain consensus)
When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
A hash below a target value which can only be obtained, on average, by performing a certain amount of brute force work—therefore demonstrating proof of work.
When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
When several nodes (usually most nodes on the network) all have the same blocks in their locally-validated best block chain.
Not to be confused with: Social consensus (often used in discussion among developers to indicate that most people agree with a particular plan), Consensus rules (the rules that allow nodes to maintain consensus)
When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
When several nodes (usually most nodes on the network) all have the same blocks in their locally-validated best block chain.
Not to be confused with: Social consensus (often used in discussion among developers to indicate that most people agree with a particular plan), Consensus rules (the rules that allow nodes to maintain consensus)
When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
When two or more blocks have the same block height, forking the block chain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
Not to be confused with: Hard fork (a change in consensus rules that breaks security for nodes that don’t upgrade), Soft fork (a change in consensus rules that weakens security for nodes that don’t upgrade), Software fork (when one or more developers permanently develops a codebase separately from other developers), Git fork (when one or more developers temporarily develops a codebase separately from other developers)
UTXOAn Unspent Transaction Output (UTXO) that can be spent as an input in a new transaction.
Not to be confused with: Output (any output, whether spent or not. Outputs are a superset of UTXOs)
#
An Unspent Transaction Output (UTXO) that can be spent as an input in a new transaction.
Not to be confused with: Output (any output, whether spent or not. Outputs are a superset of UTXOs)
An Unspent Transaction Output An output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent. Not to be confused with: Outpoint (a reference to a particular output)
An Unspent Transaction Output (UTXO) that can be spent as an input in a new transaction.
Not to be confused with: Output (any output, whether spent or not. Outputs are a superset of UTXOs)
An input in a transaction which contains three fields: an outpoint, a signature script, and a sequence number. The outpoint references a previous output and the signature script allows spending it.
Not to be confused with: Output An output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent. Not to be confused with: Outpoint (a reference to a particular output)
An output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent.
Not to be confused with: Outpoint (a reference to a particular output)
WalletSoftware that stores private keys and monitors the block chain (sometimes as a client of a server that does the processing) to allow users to spend and receive satoshis.
Not to be confused with: HD wallet (a protocol that allows all of a wallet’s keys to be created from a single seed)
#
Software that stores private keys and monitors the block chain (sometimes as a client of a server that does the processing) to allow users to spend and receive satoshis.
Not to be confused with: HD wallet (a protocol that allows all of a wallet’s keys to be created from a single seed)
Software that stores private keys and monitors the Block One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
Denominations of Bitcoin value, usually measured in fractions of a bitcoin but sometimes measured in multiples of a satoshi. One bitcoin equals 100,000,000 satoshis.
Not to be confused with: Binary bits, a unit of data with two possible values
Not to be confused with: HD wallet The Hierarchical Deterministic (HD) key creation and transfer protocol (BIP32), which allows creating child keys from parent keys in a hierarchy. Wallets using the HD protocol are called HD wallets.
Software that stores private keys and monitors the block chain (sometimes as a client of a server that does the processing) to allow users to spend and receive satoshis.
Not to be confused with: HD wallet (a protocol that allows all of a wallet’s keys to be created from a single seed)
WIFA data interchange format designed to allow exporting and importing a single private key with a flag indicating whether or not it uses a compressed public key.
Not to be confused with: Extended private keys (which allow importing a hierarchy of private keys)
#
A data interchange format designed to allow exporting and importing a single private key with a flag indicating whether or not it uses a compressed public key.
Not to be confused with: Extended private keys (which allow importing a hierarchy of private keys)
WalletSoftware that stores private keys and monitors the block chain (sometimes as a client of a server that does the processing) to allow users to spend and receive satoshis.
Not to be confused with: HD wallet (a protocol that allows all of a wallet’s keys to be created from a single seed)
Import Format #
Software that stores private keys and monitors the block chain (sometimes as a client of a server that does the processing) to allow users to spend and receive satoshis.
Not to be confused with: HD wallet (a protocol that allows all of a wallet’s keys to be created from a single seed)
A data interchange format designed to allow exporting and importing a single Private key The private portion of a keypair which can create signatures that other people can verify using the public key. Not to be confused with: Public key (data derived from the private key), Parent key (a key used to create child keys, not necessarily a private key)
An ECDSA public key that is 33 bytes long rather than the 65 bytes of an uncompressed public key.
Not to be confused with: Extended private keys (which allow importing a hierarchy of private keys)
Watch-only AddressA 20-byte hash formatted using base58check to produce either a P2PKH or P2SH Bitcoin address. Currently the most common way users exchange payment information.
Not to be confused with: IP address
#
A 20-byte hash formatted using base58check to produce either a P2PKH or P2SH Bitcoin address. Currently the most common way users exchange payment information.
Not to be confused with: IP address
An Address A 20-byte hash formatted using base58check to produce either a P2PKH or P2SH Bitcoin address. Currently the most common way users exchange payment information. Not to be confused with: IP address
A script included in outputs which sets the conditions that must be fulfilled for those satoshis to be spent. Data for fulfilling the conditions can be provided in a signature script. Pubkey Scripts are called a scriptPubKey in code.
Not to be confused with: Pubkey (a public key, which can be used as part of a pubkey script but don’t provide a programmable authentication mechanism), Signature script (a script that provides data to the pubkey script)
Software that stores private keys and monitors the block chain (sometimes as a client of a server that does the processing) to allow users to spend and receive satoshis.
Not to be confused with: HD wallet (a protocol that allows all of a wallet’s keys to be created from a single seed)
The private portion of a keypair which can create signatures that other people can verify using the public key.
Not to be confused with: Public key (data derived from the private key), Parent key (a key used to create child keys, not necessarily a private key)
Software that stores private keys and monitors the block chain (sometimes as a client of a server that does the processing) to allow users to spend and receive satoshis.
Not to be confused with: HD wallet (a protocol that allows all of a wallet’s keys to be created from a single seed)
Bitcoin URIA URI which allows receivers to encode payment details so spenders don’t have to manually enter addresses and other details.
#
A URI which allows receivers to encode payment details so spenders don’t have to manually enter addresses and other details.
A URI which allows receivers to encode payment details so spenders don’t have to manually enter addresses and other details.
Certificate chainA chain of certificates connecting a individual’s leaf certificate to the certificate authority’s root certificate.
#
A chain of certificates connecting a individual’s leaf certificate to the certificate authority’s root certificate.
A chain of certificates connecting a individual’s Leaf certificate The end-node in a certificate chain; in the payment protocol, it is the certificate belonging to the receiver of satoshis.
A certificate belonging to a certificate authority (CA).
CoinbaseA special field used as the sole input for coinbase transactions. The coinbase allows claiming the block reward and provides up to 100 bytes for arbitrary data.
Not to be confused with: Coinbase transaction, Coinbase.com
BlockOne or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
HeightThe number of blocks preceding a particular block on a block chain. For example, the genesis block has a height of zero because zero block preceded it.
#
A special field used as the sole input for coinbase transactions. The coinbase allows claiming the block reward and provides up to 100 bytes for arbitrary data.
Not to be confused with: Coinbase transaction, Coinbase.com
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
The number of blocks preceding a particular block on a block chain. For example, the genesis block has a height of zero because zero block preceded it.
The current Block One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
The number of blocks preceding a particular block on a block chain. For example, the genesis block has a height of zero because zero block preceded it.
A special field used as the sole input for coinbase transactions. The coinbase allows claiming the block reward and provides up to 100 bytes for arbitrary data.
Not to be confused with: Coinbase transaction, Coinbase.com
FiatNational currencies such as the dollar or euro.
#
National currencies such as the dollar or euro.
National currencies such as the dollar or euro.
Intermediate certificateA intermediate certificate authority certificate which helps connect a leaf (receiver) certificate to a root certificate authority.
#
A intermediate certificate authority certificate which helps connect a leaf (receiver) certificate to a root certificate authority.
A Intermediate certificate A intermediate certificate authority certificate which helps connect a leaf (receiver) certificate to a root certificate authority.
A certificate belonging to a certificate authority (CA).
Key indexAn index number used in the HD wallet formula to generate child keys from a parent key.
#
An index number used in the HD wallet formula to generate child keys from a parent key.
An index number used in the HD wallet The Hierarchical Deterministic (HD) key creation and transfer protocol (BIP32), which allows creating child keys from parent keys in a hierarchy. Wallets using the HD protocol are called HD wallets.
In HD wallets, a key used to derive child keys. The key can be either a private key or a public key, and the key derivation may also require a chain code.
Not to be confused with: Public key (derived from a private key, not a parent key)
Key pairA private key and its derived public key.
#
A private key and its derived public key.
A Private key The private portion of a keypair which can create signatures that other people can verify using the public key. Not to be confused with: Public key (data derived from the private key), Parent key (a key used to create child keys, not necessarily a private key)
The public portion of a keypair which can be used to verify signatures made with the private portion of the keypair.
Not to be confused with: Private key (data from which the public key is derived), Parent key (a key used to create child keys, not necessarily a public key)
LabelThe label parameter of a bitcoin: URI which provides the spender with the receiver’s name (unauthenticated).
#
The label parameter of a bitcoin: URI which provides the spender with the receiver’s name (unauthenticated).
The Label The label parameter of a bitcoin: URI which provides the spender with the receiver’s name (unauthenticated).
Leaf certificateThe end-node in a certificate chain; in the payment protocol, it is the certificate belonging to the receiver of satoshis.
#
The end-node in a certificate chain; in the payment protocol, it is the certificate belonging to the receiver of satoshis.
The end-Node A computer that connects to the Bitcoin network. Not to be confused with: Lightweight node, SPV node
A chain of certificates connecting a individual’s leaf certificate to the certificate authority’s root certificate.
The deprecated protocol defined in BIP70 (and other BIPs) which lets spenders get signed payment details from receivers.
Not to be confused with: IP-to-IP payment protocol (an insecure, discontinued protocol included in early versions of Bitcoin)
Denominations of Bitcoin value, usually measured in fractions of a bitcoin but sometimes measured in multiples of a satoshi. One bitcoin equals 100,000,000 satoshis.
Not to be confused with: Binary bits, a unit of data with two possible values
MergeSpending, in the same transaction, multiple outputs which can be traced back to different previous spenders, leaking information about how many satoshis you control.
#
Spending, in the same transaction, multiple outputs which can be traced back to different previous spenders, leaking information about how many satoshis you control.
Spending, in the same transaction, multiple outputs which can be traced back to different previous spenders, leaking information about how many Satoshis Denominations of Bitcoin value, usually measured in fractions of a bitcoin but sometimes measured in multiples of a satoshi. One bitcoin equals 100,000,000 satoshis. Not to be confused with: Binary bits, a unit of data with two possible values
MergeSpending, in the same transaction, multiple outputs which can be traced back to different previous spenders, leaking information about how many satoshis you control.
avoidance #
Spending, in the same transaction, multiple outputs which can be traced back to different previous spenders, leaking information about how many satoshis you control.
A strategy for selecting which outputs to spend that avoids merging outputs with different histories that could leak private information.
MessageA parameter of bitcoin: URIs which allows the receiver to optionally specify a message to the spender.
#
A parameter of bitcoin: URIs which allows the receiver to optionally specify a message to the spender.
A parameter of bitcoin: URIs which allows the receiver to optionally specify a Message A parameter of bitcoin: URIs which allows the receiver to optionally specify a message to the spender.
Micropayment channelterm-micropayment-channel (contracts-guide) (original target)
#
term-micropayment-channel (contracts-guide) (original target)
term-micropayment-channel (contracts-guide) (original target)
OP CHECKMULTISIGOpcode which returns true if one or more provided signatures (m) sign the correct parts of a transaction and match one or more provided public keys (n).
#
Opcode which returns true if one or more provided signatures (m) sign the correct parts of a transaction and match one or more provided public keys (n).
Opcode Operation codes from the Bitcoin Script language which push data or perform functions within a pubkey script or signature script.
OutputAn output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent.
Not to be confused with: Outpoint (a reference to a particular output)
index #
An output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent.
Not to be confused with: Outpoint (a reference to a particular output)
The sequentially-numbered index of outputs in a single transaction starting from 0.
PKIPublic Key Infrastructure; usually meant to indicate the X.509 certificate system used for HTTP Secure (https).
#
Public Key Infrastructure; usually meant to indicate the X.509 certificate system used for HTTP Secure (https).
Public key The public portion of a keypair which can be used to verify signatures made with the private portion of the keypair. Not to be confused with: Private key (data from which the public key is derived), Parent key (a key used to create child keys, not necessarily a public key)
Point functionThe ECDSA function used to create a public key from a private key.
#
The ECDSA function used to create a public key from a private key.
The ECDSA function used to create a Public key The public portion of a keypair which can be used to verify signatures made with the private portion of the keypair. Not to be confused with: Private key (data from which the public key is derived), Parent key (a key used to create child keys, not necessarily a public key)
The private portion of a keypair which can create signatures that other people can verify using the public key.
Not to be confused with: Public key (data derived from the private key), Parent key (a key used to create child keys, not necessarily a private key)
PP amountPart of the Output part of the PaymentDetails part of a payment protocol where receivers can specify the amount of satoshis they want paid to a particular pubkey script.
#
Part of the Output part of the PaymentDetails part of a payment protocol where receivers can specify the amount of satoshis they want paid to a particular pubkey script.
Part of the Output An output in a transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent. Not to be confused with: Outpoint (a reference to a particular output)
The deprecated protocol defined in BIP70 (and other BIPs) which lets spenders get signed payment details from receivers.
Not to be confused with: IP-to-IP payment protocol (an insecure, discontinued protocol included in early versions of Bitcoin)
Denominations of Bitcoin value, usually measured in fractions of a bitcoin but sometimes measured in multiples of a satoshi. One bitcoin equals 100,000,000 satoshis.
Not to be confused with: Binary bits, a unit of data with two possible values
A script included in outputs which sets the conditions that must be fulfilled for those satoshis to be spent. Data for fulfilling the conditions can be provided in a signature script. Pubkey Scripts are called a scriptPubKey in code.
Not to be confused with: Pubkey (a public key, which can be used as part of a pubkey script but don’t provide a programmable authentication mechanism), Signature script (a script that provides data to the pubkey script)
PP expiresThe expires field of a PaymentDetails where the receiver tells the spender when the PaymentDetails expires.
#
The expires field of a PaymentDetails where the receiver tells the spender when the PaymentDetails expires.
The expires field of a PaymentDetails where the receiver tells the spender when the PaymentDetails expires.
PP memoThe memo fields of PaymentDetails, Payment, and PaymentACK which allow spenders and receivers to send each other memos.
#
The memo fields of PaymentDetails, Payment, and PaymentACK which allow spenders and receivers to send each other memos.
The memo fields of PaymentDetails, Payment, and PaymentACK which allow spenders and receivers to send each other memos.
PP merchant dataThe merchant_data part of PaymentDetails and Payment which allows the receiver to send arbitrary data to the spender in PaymentDetails and receive it back in Payments.
#
The merchant_data part of PaymentDetails and Payment which allows the receiver to send arbitrary data to the spender in PaymentDetails and receive it back in Payments.
The merchant_data part of PaymentDetails and Payment which allows the receiver to send arbitrary data to the spender in PaymentDetails and receive it back in Payments.
PP PKIPublic Key Infrastructure; usually meant to indicate the X.509 certificate system used for HTTP Secure (https).
data #
Public Key Infrastructure; usually meant to indicate the X.509 certificate system used for HTTP Secure (https).
The pki_data field of a PaymentRequest which provides details such as certificates necessary to validate the request.
PP PKIPublic Key Infrastructure; usually meant to indicate the X.509 certificate system used for HTTP Secure (https).
type #
Public Key Infrastructure; usually meant to indicate the X.509 certificate system used for HTTP Secure (https).
The PKI Public Key Infrastructure; usually meant to indicate the X.509 certificate system used for HTTP Secure (https).
PP scriptThe script field of a PaymentDetails where the receiver tells the spender what pubkey scripts to pay.
#
The script field of a PaymentDetails where the receiver tells the spender what pubkey scripts to pay.
The script field of a PaymentDetails where the receiver tells the spender what pubkey scripts to pay.
Previous BlockOne or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
HeaderAn 80-byte header belonging to a single block which is hashed repeatedly to create proof of work.
hash #
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
An 80-byte header belonging to a single block which is hashed repeatedly to create proof of work.
A field in the Block One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
An 80-byte header belonging to a single block which is hashed repeatedly to create proof of work.
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
An 80-byte header belonging to a single block which is hashed repeatedly to create proof of work.
R parameterThe payment request parameter in a bitcoin: URI.
#
The payment request parameter in a bitcoin: URI.
The Payment request The deprecated protocol defined in BIP70 (and other BIPs) which lets spenders get signed payment details from receivers. Not to be confused with: IP-to-IP payment protocol (an insecure, discontinued protocol included in early versions of Bitcoin)
ReceiptA cryptographically-verifiable receipt created using parts of a payment request and a confirmed transaction.
#
A cryptographically-verifiable receipt created using parts of a payment request and a confirmed transaction.
A cryptographically-verifiable Receipt A cryptographically-verifiable receipt created using parts of a payment request and a confirmed transaction.
The deprecated protocol defined in BIP70 (and other BIPs) which lets spenders get signed payment details from receivers.
Not to be confused with: IP-to-IP payment protocol (an insecure, discontinued protocol included in early versions of Bitcoin)
A score indicating the number of blocks on the best block chain that would need to be modified to remove or modify a particular transaction. A confirmed transaction has a confirmation score of one or higher.
Root certificateA certificate belonging to a certificate authority (CA).
#
A certificate belonging to a certificate authority (CA).
A certificate belonging to a certificate authority (CA).
SSL SignatureA value related to a public key which could only have reasonably been created by someone who has the private key that created that public key. Used in Bitcoin to authorize spending satoshis previously sent to a public key.
#
A value related to a public key which could only have reasonably been created by someone who has the private key that created that public key. Used in Bitcoin to authorize spending satoshis previously sent to a public key.
Signatures created and recognized by major SSL implementations such as OpenSSL.
Stanndard BlockOne or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
relay #
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
The regular Block One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
A parameter of bitcoin: URIs which allows the receiver to optionally specify a message to the spender.
Transaction version numberA version number prefixed to transactions to allow upgrading.
#
A version number prefixed to transactions to allow upgrading.
A version number prefixed to transactions to allow upgrading.
Unique AddressA 20-byte hash formatted using base58check to produce either a P2PKH or P2SH Bitcoin address. Currently the most common way users exchange payment information.
Not to be confused with: IP address
#
A 20-byte hash formatted using base58check to produce either a P2PKH or P2SH Bitcoin address. Currently the most common way users exchange payment information.
Not to be confused with: IP address
Address A 20-byte hash formatted using base58check to produce either a P2PKH or P2SH Bitcoin address. Currently the most common way users exchange payment information. Not to be confused with: IP address
Unsolicited BlockOne or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
push #
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
When a Miner Mining is the act of creating valid Bitcoin blocks, which requires demonstrating proof of work, and miners are devices that mine or people who own those devices.
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
A parameter of bitcoin: URIs which allows the receiver to optionally specify a message to the spender.
A parameter of bitcoin: URIs which allows the receiver to optionally specify a message to the spender.
URI qr codeA QR code containing a bitcoin: URI.
#
A QR code containing a bitcoin: URI.
A QR code containing a bitcoin: URI.
V2 BlockOne or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
#
One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the block chain.
The current version of Bitcoin blocks.
Leave a Reply
Want to join the discussion?Feel free to contribute!