diff --git a/_alerts/2013-03-11-chain-fork.html b/_alerts/2013-03-11-chain-fork.html index 6ef3165340..d3ed74d9a4 100644 --- a/_alerts/2013-03-11-chain-fork.html +++ b/_alerts/2013-03-11-chain-fork.html @@ -10,14 +10,14 @@

What happened

with earlier versions of Bitcoin.

-The result was a block chain fork, with miners, merchants and users running the new version of bitcoin +The result was a blockchain fork, with miners, merchants and users running the new version of bitcoin accepting, and building on, that block, and miners, merchants and users running older versions of bitcoin -rejecting it and creating their own block chain. +rejecting it and creating their own blockchain.

What is being done

Large mining pools running version 0.8.0 were asked to switch back to version 0.7, to create a -single block chain compatible with all bitcoin software. +single blockchain compatible with all bitcoin software.

Questions & Answers

I'm not a miner or a merchant, what should I do?

diff --git a/_alerts/2013-03-15-upgrade-deadline.html b/_alerts/2013-03-15-upgrade-deadline.html index 06f98ff51d..33188af627 100644 --- a/_alerts/2013-03-15-upgrade-deadline.html +++ b/_alerts/2013-03-15-upgrade-deadline.html @@ -60,7 +60,7 @@

Miners/mining pool operators

Why this is necessary

-A bug caused a temporary block chain fork on 11 March, 2013. +A bug caused a temporary blockchain fork on 11 March, 2013. After investigating that bug, we determined that the bug can happen even if the entire network was still running old versions of Bitcoin-Qt/bitcoind. Therefore, the only option is to diff --git a/_data/glossary/en/block-chain.yaml b/_data/glossary/en/block-chain.yaml index 3396859ce6..352ffffa93 100644 --- a/_data/glossary/en/block-chain.yaml +++ b/_data/glossary/en/block-chain.yaml @@ -4,24 +4,24 @@ required: #-------------40 characters-------------# - title_max_40_characters_no_formatting: Block Chain + title_max_40_characters_no_formatting: Blockchain summary_max_255_characters_no_formatting: > A chain of blocks with each block referencing the block that preceded it. The most-difficult-to-recreate chain is - the best block chain. + the best blockchain. synonyms_shown_in_glossary_capitalize_first_letter: - - Block chain - - Best block chain ## this could be moved into its own entry + - Blockchain + - Best blockchain ## this could be moved into its own entry optional: synonyms_and_pluralizations_not_shown_in_glossary: + - block chain - block chains - blocks chain - block-chain - block-chains - - blockchain - blockchains - best block chain - best blockchain @@ -30,7 +30,7 @@ optional: - Header chain links_html_or_markdown_style_capitalize_first_letter: - - "[Block chain](/en/developer-guide#block-chain) --- Bitcoin.org Developer Guide" - - "[Block chain](https://en.bitcoin.it/wiki/Block_chain) --- Bitcoin Wiki" + - "[Blockchain](/en/developer-guide#block-chain) --- Bitcoin.org Developer Guide" + - "[Blockchain](https://en.bitcoin.it/wiki/Block_chain) --- Bitcoin Wiki" --- diff --git a/_data/glossary/en/block-height.yaml b/_data/glossary/en/block-height.yaml index 07212625a9..5b58222775 100644 --- a/_data/glossary/en/block-height.yaml +++ b/_data/glossary/en/block-height.yaml @@ -4,7 +4,7 @@ required: #-------------40 characters-------------# - title_max_40_characters_no_formatting: Block Chain Height, Block Height + title_max_40_characters_no_formatting: Blockchain Height, Block Height summary_max_255_characters_no_formatting: > The number of blocks preceding a particular block on a block @@ -19,8 +19,8 @@ optional: synonyms_and_pluralizations_not_shown_in_glossary: - heights - block heights - - block chain height - - block chain heights + - blockchain height + - blockchain heights not_to_be_confused_with_capitalize_first_letter: diff --git a/_data/glossary/en/block.yaml b/_data/glossary/en/block.yaml index 7e9c1d0c88..daaf0c5c9b 100644 --- a/_data/glossary/en/block.yaml +++ b/_data/glossary/en/block.yaml @@ -9,7 +9,7 @@ required: summary_max_255_characters_no_formatting: > One or more transactions prefaced by a block header and protected by proof of work. Blocks are the data stored on the - block chain. + blockchain. synonyms_shown_in_glossary_capitalize_first_letter: - Block diff --git a/_data/glossary/en/blocks-first-sync.yaml b/_data/glossary/en/blocks-first-sync.yaml index 722e3d6548..611db12bbd 100644 --- a/_data/glossary/en/blocks-first-sync.yaml +++ b/_data/glossary/en/blocks-first-sync.yaml @@ -7,7 +7,7 @@ required: title_max_40_characters_no_formatting: Blocks-First, Blocks-First Sync summary_max_255_characters_no_formatting: > - Synchronizing the block chain by downloading each block from a + Synchronizing the blockchain by downloading each block from a peer and then validating it. synonyms_shown_in_glossary_capitalize_first_letter: diff --git a/_data/glossary/en/confirmation-score.yaml b/_data/glossary/en/confirmation-score.yaml index a1cb063957..f4ef4d7be4 100644 --- a/_data/glossary/en/confirmation-score.yaml +++ b/_data/glossary/en/confirmation-score.yaml @@ -7,7 +7,7 @@ required: title_max_40_characters_no_formatting: Confirmation Score, Confirmed Transaction summary_max_255_characters_no_formatting: > - A score indicating the number of blocks on the best block chain + A score indicating the number of blocks on the best blockchain that would need to be modified to remove or modify a particular transaction. A confirmed transaction has a confirmation score of one or higher. diff --git a/_data/glossary/en/consensus-rules.yaml b/_data/glossary/en/consensus-rules.yaml index d900f922be..610f30dcd6 100644 --- a/_data/glossary/en/consensus-rules.yaml +++ b/_data/glossary/en/consensus-rules.yaml @@ -16,8 +16,8 @@ required: optional: synonyms_and_pluralizations_not_shown_in_glossary: - consensus rule - - block chain validation rule - - Block chain validation rules + - blockchain validation rule + - Blockchain validation rules - validation rule - validation rules diff --git a/_data/glossary/en/consensus.yaml b/_data/glossary/en/consensus.yaml index 888977d5b5..1db560d434 100644 --- a/_data/glossary/en/consensus.yaml +++ b/_data/glossary/en/consensus.yaml @@ -8,14 +8,14 @@ required: summary_max_255_characters_no_formatting: > When several nodes (usually most nodes on the network) all have - the same blocks in their locally-validated best block chain. + the same blocks in their locally-validated best blockchain. synonyms_shown_in_glossary_capitalize_first_letter: - Consensus optional: synonyms_and_pluralizations_not_shown_in_glossary: - - block chain consensus + - blockchain consensus not_to_be_confused_with_capitalize_first_letter: - Social consensus (often used in discussion among developers to indicate that most people agree with a particular plan) diff --git a/_data/glossary/en/fork.yaml b/_data/glossary/en/fork.yaml index be693e540c..f0cc587215 100644 --- a/_data/glossary/en/fork.yaml +++ b/_data/glossary/en/fork.yaml @@ -8,7 +8,7 @@ required: summary_max_255_characters_no_formatting: > When two or more blocks have the same block height, forking the - block chain. Typically occurs when two or more miners find + blockchain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack. @@ -28,6 +28,6 @@ optional: links_html_or_markdown_style_capitalize_first_letter: - "[Fork](/en/developer-guide#term-fork) --- Bitcoin.org Developer Guide" - - "[What is the longest block chain fork that has been made stale so far?](http://bitcoin.stackexchange.com/q/3343) --- Bitcoin StackExchange" + - "[What is the longest blockchain fork that has been made stale so far?](http://bitcoin.stackexchange.com/q/3343) --- Bitcoin StackExchange" --- diff --git a/_data/glossary/en/genesis-block.yaml b/_data/glossary/en/genesis-block.yaml index 518de6f4c8..83ff1cf4b6 100644 --- a/_data/glossary/en/genesis-block.yaml +++ b/_data/glossary/en/genesis-block.yaml @@ -7,7 +7,7 @@ required: title_max_40_characters_no_formatting: Genesis Block, Block 0 summary_max_255_characters_no_formatting: > - The first block in the Bitcoin block chain. + The first block in the Bitcoin blockchain. synonyms_shown_in_glossary_capitalize_first_letter: - Genesis block diff --git a/_data/glossary/en/hard-fork.yaml b/_data/glossary/en/hard-fork.yaml index 34ab032e01..9933481d48 100644 --- a/_data/glossary/en/hard-fork.yaml +++ b/_data/glossary/en/hard-fork.yaml @@ -7,7 +7,7 @@ required: title_max_40_characters_no_formatting: Hard Fork, Hard-Forking Change summary_max_255_characters_no_formatting: > - A permanent divergence in the the block chain, commonly occurs + A permanent divergence in the the blockchain, commonly occurs when non-upgraded nodes can't validate blocks created by upgraded nodes that follow newer consensus rules. @@ -22,7 +22,7 @@ optional: not_to_be_confused_with_capitalize_first_letter: - 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) - - Soft fork (a temporary divergence in the block chain caused by non-upgraded nodes not following new consensus rules) + - Soft fork (a temporary divergence in the blockchain 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 diff --git a/_data/glossary/en/header-chain.yaml b/_data/glossary/en/header-chain.yaml index d4d6a8377d..29853a5a8a 100644 --- a/_data/glossary/en/header-chain.yaml +++ b/_data/glossary/en/header-chain.yaml @@ -27,7 +27,7 @@ optional: - best headerchain not_to_be_confused_with_capitalize_first_letter: - - Block chain + - Blockchain links_html_or_markdown_style_capitalize_first_letter: - "[Header chain](/en/developer-guide#term-header-chain) --- Bitcoin.org Developer Guide" diff --git a/_data/glossary/en/headers-first-sync.yaml b/_data/glossary/en/headers-first-sync.yaml index 1fe9691f2c..76a1269bef 100644 --- a/_data/glossary/en/headers-first-sync.yaml +++ b/_data/glossary/en/headers-first-sync.yaml @@ -7,7 +7,7 @@ required: title_max_40_characters_no_formatting: Headers-First, Headers-First Sync summary_max_255_characters_no_formatting: > - Synchronizing the block chain by downloading block headers + Synchronizing the blockchain by downloading block headers before downloading the full blocks. synonyms_shown_in_glossary_capitalize_first_letter: diff --git a/_data/glossary/en/initial-block-download.yaml b/_data/glossary/en/initial-block-download.yaml index 5f9e16959f..df83f03e3a 100644 --- a/_data/glossary/en/initial-block-download.yaml +++ b/_data/glossary/en/initial-block-download.yaml @@ -9,7 +9,7 @@ required: summary_max_255_characters_no_formatting: > 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. + best blockchain. synonyms_shown_in_glossary_capitalize_first_letter: - Initial block download diff --git a/_data/glossary/en/locktime.yaml b/_data/glossary/en/locktime.yaml index 3f4fe6b2f8..3a4c83dacb 100644 --- a/_data/glossary/en/locktime.yaml +++ b/_data/glossary/en/locktime.yaml @@ -9,7 +9,7 @@ required: summary_max_255_characters_no_formatting: > Part of a transaction which indicates the earliest time or earliest block when that transaction may be added to the - block chain. + blockchain. synonyms_shown_in_glossary_capitalize_first_letter: - Locktime diff --git a/_data/glossary/en/null-data-transaction.yaml b/_data/glossary/en/null-data-transaction.yaml index 5933d18216..924a0d6e6a 100644 --- a/_data/glossary/en/null-data-transaction.yaml +++ b/_data/glossary/en/null-data-transaction.yaml @@ -8,7 +8,7 @@ required: summary_max_255_characters_no_formatting: > A standard transaction type which allows adding 40 bytes of - arbitrary data to the block chain up to once per transaction. + arbitrary data to the blockchain up to once per transaction. synonyms_shown_in_glossary_capitalize_first_letter: - Null data transaction diff --git a/_data/glossary/en/soft-fork.yaml b/_data/glossary/en/soft-fork.yaml index 65c6ab820d..d36948f038 100644 --- a/_data/glossary/en/soft-fork.yaml +++ b/_data/glossary/en/soft-fork.yaml @@ -7,7 +7,7 @@ required: title_max_40_characters_no_formatting: Soft Fork, Soft-Forking Change summary_max_255_characters_no_formatting: > - A temporary fork in the block chain which commonly occurs when + A temporary fork in the blockchain which commonly occurs when miners using non-upgraded nodes violate a new consensus rule their nodes don't know about. @@ -22,7 +22,7 @@ optional: not_to_be_confused_with_capitalize_first_letter: - 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) + - Hard fork (a permanent divergence in the blockchain 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 diff --git a/_data/glossary/en/stale-block.yaml b/_data/glossary/en/stale-block.yaml index bae21fd886..3e9727e39d 100644 --- a/_data/glossary/en/stale-block.yaml +++ b/_data/glossary/en/stale-block.yaml @@ -8,7 +8,7 @@ required: summary_max_255_characters_no_formatting: > Blocks which were successfully mined but which aren't included - on the current best block chain, likely because some other block + on the current best blockchain, likely because some other block at the same height had its chain extended first. synonyms_shown_in_glossary_capitalize_first_letter: diff --git a/_data/glossary/en/wallet.yaml b/_data/glossary/en/wallet.yaml index 0436bcd0d9..92bb1abd8c 100644 --- a/_data/glossary/en/wallet.yaml +++ b/_data/glossary/en/wallet.yaml @@ -7,7 +7,7 @@ required: title_max_40_characters_no_formatting: Wallet summary_max_255_characters_no_formatting: > - Software that stores private keys and monitors the block chain + Software that stores private keys and monitors the blockchain (sometimes as a client of a server that does the processing) to allow users to spend and receive satoshis. diff --git a/_includes/bitcoin-core/bitcoin-core-possible-problems.md b/_includes/bitcoin-core/bitcoin-core-possible-problems.md index 2fb02bf644..ba0fafe881 100644 --- a/_includes/bitcoin-core/bitcoin-core-possible-problems.md +++ b/_includes/bitcoin-core/bitcoin-core-possible-problems.md @@ -15,7 +15,7 @@ http://opensource.org/licenses/MIT. upload limit. - **Anti-virus:** Several people have placed parts of known computer - viruses in the Bitcoin block chain. This block chain data can't infect + viruses in the Bitcoin blockchain. This blockchain data can't infect your computer, but some anti-virus programs quarantine the data anyway, making it more difficult to run Bitcoin Core. This problem mostly affects computers running Windows. diff --git a/_includes/devdoc/bitcoin-core/rest/requests/get_block-notxdetails.md b/_includes/devdoc/bitcoin-core/rest/requests/get_block-notxdetails.md index 4e6fdec9ca..9c35f5a71c 100644 --- a/_includes/devdoc/bitcoin-core/rest/requests/get_block-notxdetails.md +++ b/_includes/devdoc/bitcoin-core/rest/requests/get_block-notxdetails.md @@ -55,7 +55,7 @@ GET /block/notxdetails/. - n: "→
`confirmations`" t: "number (int)" p: "Required
(exactly 1)" - d: "The number of confirmations the transactions in this block have, starting at 1 when this block is at the tip of the best block chain. This score will be -1 if the the block is not part of the best block chain" + d: "The number of confirmations the transactions in this block have, starting at 1 when this block is at the tip of the best blockchain. This score will be -1 if the the block is not part of the best blockchain" - n: "→
`size`" t: "number (int)" @@ -65,7 +65,7 @@ GET /block/notxdetails/. - n: "→
`height`" t: "number (int)" p: "Required
(exactly 1)" - d: "The height of this block on its block chain" + d: "The height of this block on its blockchain" - n: "→
`version`" t: "number (int)" @@ -95,7 +95,7 @@ GET /block/notxdetails/. - n: "→
`nonce`" t: "number (int)" p: "Required
(exactly 1)" - d: "The nonce which was successful at turning this particular block into one that could be added to the best block chain" + d: "The nonce which was successful at turning this particular block into one that could be added to the best blockchain" - n: "→
`bits`" t: "string (hex)" @@ -120,7 +120,7 @@ GET /block/notxdetails/. - n: "→
`nextblockhash`" t: "string (hex)" p: "Optional
(0 or 1)" - d: "The hash of the next block on the best block chain, if known, encoded as hex in RPC byte order" + d: "The hash of the next block on the best blockchain, if known, encoded as hex in RPC byte order" {% enditemplate %} diff --git a/_includes/devdoc/bitcoin-core/rest/requests/get_block.md b/_includes/devdoc/bitcoin-core/rest/requests/get_block.md index 1c24a8e5bb..4b4f50ff58 100644 --- a/_includes/devdoc/bitcoin-core/rest/requests/get_block.md +++ b/_includes/devdoc/bitcoin-core/rest/requests/get_block.md @@ -58,7 +58,7 @@ GET /block/. - n: "→
`confirmations`" t: "number (int)" p: "Required
(exactly 1)" - d: "The number of confirmations the transactions in this block have, starting at 1 when this block is at the tip of the best block chain. This score will be -1 if the the block is not part of the best block chain" + d: "The number of confirmations the transactions in this block have, starting at 1 when this block is at the tip of the best blockchain. This score will be -1 if the the block is not part of the best blockchain" - n: "→
`size`" t: "number (int)" @@ -68,7 +68,7 @@ GET /block/. - n: "→
`height`" t: "number (int)" p: "Required
(exactly 1)" - d: "The height of this block on its block chain" + d: "The height of this block on its blockchain" - n: "→
`version`" t: "number (int)" @@ -99,7 +99,7 @@ GET /block/. - n: "→
`nonce`" t: "number (int)" p: "Required
(exactly 1)" - d: "The nonce which was successful at turning this particular block into one that could be added to the best block chain" + d: "The nonce which was successful at turning this particular block into one that could be added to the best blockchain" - n: "→
`bits`" t: "string (hex)" @@ -124,7 +124,7 @@ GET /block/. - n: "→
`nextblockhash`" t: "string (hex)" p: "Optional
(0 or 1)" - d: "The hash of the next block on the best block chain, if known, encoded as hex in RPC byte order" + d: "The hash of the next block on the best blockchain, if known, encoded as hex in RPC byte order" {% enditemplate %} diff --git a/_includes/devdoc/bitcoin-core/rest/requests/get_tx.md b/_includes/devdoc/bitcoin-core/rest/requests/get_tx.md index bd1baa6ef1..411983feed 100644 --- a/_includes/devdoc/bitcoin-core/rest/requests/get_tx.md +++ b/_includes/devdoc/bitcoin-core/rest/requests/get_tx.md @@ -56,17 +56,17 @@ GET /tx/. - n: "→
`blockhash`" t: "string (hex)" p: "Optional
(0 or 1)" - d: "If the transaction has been included in a block on the local best block chain, this is the hash of that block encoded as hex in RPC byte order" + d: "If the transaction has been included in a block on the local best blockchain, this is the hash of that block encoded as hex in RPC byte order" - n: "→
`confirmations`" t: "number (int)" p: "Required
(exactly 1)" - d: "If the transaction has been included in a block on the local best block chain, this is how many confirmations it has. Otherwise, this is `0`" + d: "If the transaction has been included in a block on the local best blockchain, this is how many confirmations it has. Otherwise, this is `0`" - n: "→
`time`" t: "number (int)" p: "Optional
(0 or 1)" - d: "If the transaction has been included in a block on the local best block chain, this is the block header time of that block (may be in the future)" + d: "If the transaction has been included in a block on the local best blockchain, this is the block header time of that block (may be in the future)" - n: "→
`blocktime`" t: "number (int)" diff --git a/_includes/devdoc/bitcoin-core/rpcs/intro.md b/_includes/devdoc/bitcoin-core/rpcs/intro.md index a7f2d9158f..5f7bde5581 100644 --- a/_includes/devdoc/bitcoin-core/rpcs/intro.md +++ b/_includes/devdoc/bitcoin-core/rpcs/intro.md @@ -10,8 +10,8 @@ http://opensource.org/licenses/MIT. {% autocrossref %} Bitcoin Core provides a remote procedure call (RPC) interface for various -administrative tasks, wallet operations, and queries about network and block -chain data. +administrative tasks, wallet operations, and queries about network and +blockchain data. If you start Bitcoin Core using `bitcoin-qt`, the RPC interface is disabled by default. To enable it, set `server=1` in `bitcoin.conf` or supply the `-server` diff --git a/_includes/devdoc/bitcoin-core/rpcs/quick-ref.md b/_includes/devdoc/bitcoin-core/rpcs/quick-ref.md index 57aef82f89..585c855641 100644 --- a/_includes/devdoc/bitcoin-core/rpcs/quick-ref.md +++ b/_includes/devdoc/bitcoin-core/rpcs/quick-ref.md @@ -39,7 +39,7 @@ Use v0.n.n in abbreviation title to prevent autocrossrefing. _includes/rpc/getbestblockhash.md and run `make manual-update-summaries`. --> {% include helpers/summaries.md %} -#### Block Chain RPCs +#### Blockchain RPCs {:.no_toc} diff --git a/_includes/devdoc/bitcoin-core/rpcs/rpcs/getbestblockhash.md b/_includes/devdoc/bitcoin-core/rpcs/rpcs/getbestblockhash.md index 066884e33c..5df5606040 100644 --- a/_includes/devdoc/bitcoin-core/rpcs/rpcs/getbestblockhash.md +++ b/_includes/devdoc/bitcoin-core/rpcs/rpcs/getbestblockhash.md @@ -7,7 +7,7 @@ http://opensource.org/licenses/MIT. ##### GetBestBlockHash {% include helpers/subhead-links.md %} -{% assign summary_getBestBlockHash="returns the header hash of the most recent block on the best block chain." %} +{% assign summary_getBestBlockHash="returns the header hash of the most recent block on the best blockchain." %} {% autocrossref %} @@ -17,13 +17,13 @@ The `getbestblockhash` RPC {{summary_getBestBlockHash}} *Parameters: none* -*Result---hash of the tip from the best block chain* +*Result---hash of the tip from the best blockchain* {% itemplate ntpd1 %} - n: "`result`" t: "string (hex)" p: "Required
(exactly 1)" - d: "The hash of the block header from the most recent block on the best block chain, encoded as hex in RPC byte order" + d: "The hash of the block header from the most recent block on the best blockchain, encoded as hex in RPC byte order" {% enditemplate %} diff --git a/_includes/devdoc/bitcoin-core/rpcs/rpcs/getblock.md b/_includes/devdoc/bitcoin-core/rpcs/rpcs/getblock.md index e6d7c87e32..51594a473e 100644 --- a/_includes/devdoc/bitcoin-core/rpcs/rpcs/getblock.md +++ b/_includes/devdoc/bitcoin-core/rpcs/rpcs/getblock.md @@ -59,7 +59,7 @@ The `getblock` RPC {{summary_getBlock}} - n: "→
`confirmations`" t: "number (int)" p: "Required
(exactly 1)" - d: "The number of confirmations the transactions in this block have, starting at 1 when this block is at the tip of the best block chain. This score will be -1 if the the block is not part of the best block chain" + d: "The number of confirmations the transactions in this block have, starting at 1 when this block is at the tip of the best blockchain. This score will be -1 if the the block is not part of the best blockchain" - n: "→
`size`" t: "number (int)" @@ -69,7 +69,7 @@ The `getblock` RPC {{summary_getBlock}} - n: "→
`height`" t: "number (int)" p: "Required
(exactly 1)" - d: "The height of this block on its block chain" + d: "The height of this block on its blockchain" - n: "→
`version`" t: "number (int)" @@ -99,7 +99,7 @@ The `getblock` RPC {{summary_getBlock}} - n: "→
`nonce`" t: "number (int)" p: "Required
(exactly 1)" - d: "The nonce which was successful at turning this particular block into one that could be added to the best block chain" + d: "The nonce which was successful at turning this particular block into one that could be added to the best blockchain" - n: "→
`bits`" t: "string (hex)" @@ -124,7 +124,7 @@ The `getblock` RPC {{summary_getBlock}} - n: "→
`nextblockhash`" t: "string (hex)" p: "Optional
(0 or 1)" - d: "The hash of the next block on the best block chain, if known, encoded as hex in RPC byte order" + d: "The hash of the next block on the best blockchain, if known, encoded as hex in RPC byte order" {% enditemplate %} diff --git a/_includes/devdoc/bitcoin-core/rpcs/rpcs/getblockchaininfo.md b/_includes/devdoc/bitcoin-core/rpcs/rpcs/getblockchaininfo.md index aebac3085a..1bd87d7ad1 100644 --- a/_includes/devdoc/bitcoin-core/rpcs/rpcs/getblockchaininfo.md +++ b/_includes/devdoc/bitcoin-core/rpcs/rpcs/getblockchaininfo.md @@ -7,7 +7,7 @@ http://opensource.org/licenses/MIT. ##### GetBlockChainInfo {% include helpers/subhead-links.md %} -{% assign summary_getBlockChainInfo="provides information about the current state of the block chain." %} +{% assign summary_getBlockChainInfo="provides information about the current state of the blockchain." %} {% autocrossref %} @@ -17,23 +17,23 @@ The `getblockchaininfo` RPC {{summary_getBlockChainInfo}} *Parameters: none* -*Result---A JSON object providing information about the block chain* +*Result---A JSON object providing information about the blockchain* {% itemplate ntpd1 %} - n: "`result`" t: "object" p: "Required
(exactly 1)" - d: "Information about the current state of the local block chain" + d: "Information about the current state of the local blockchain" - n: "→
`chain`" t: "string" p: "Required
(exactly 1)" - d: "The name of the block chain. One of `main` for mainnet, `test` for testnet, or `regtest` for regtest" + d: "The name of the blockchain. One of `main` for mainnet, `test` for testnet, or `regtest` for regtest" - n: "→
`blocks`" t: "number (int)" p: "Required
(exactly 1)" - d: "The number of validated blocks in the local best block chain. For a new node with just the hardcoded genesis block, this will be 0" + d: "The number of validated blocks in the local best blockchain. For a new node with just the hardcoded genesis block, this will be 0" - n: "→
`headers`" t: "number (int)" @@ -43,17 +43,17 @@ The `getblockchaininfo` RPC {{summary_getBlockChainInfo}} - n: "→
`bestblockhash`" t: "string (hex)" p: "Required
(exactly 1)" - d: "The hash of the header of the highest validated block in the best block chain, encoded as hex in RPC byte order. This is identical to the string returned by the `getbestblockhash` RPC" + d: "The hash of the header of the highest validated block in the best blockchain, encoded as hex in RPC byte order. This is identical to the string returned by the `getbestblockhash` RPC" - n: "→
`difficulty`" t: "number (real)" p: "Required
(exactly 1)" - d: "The difficulty of the highest-height block in the best block chain" + d: "The difficulty of the highest-height block in the best blockchain" - n: "→
`verificationprogress`" t: "number (real)" p: "Required (exactly 1)" - d: "Estimate of what percentage of the block chain transactions have been verified so far, starting at 0.0 and increasing to 1.0 for fully verified. May slightly exceed 1.0 when fully synced to account for transactions in the memory pool which have been verified before being included in a block" + d: "Estimate of what percentage of the blockchain transactions have been verified so far, starting at 0.0 and increasing to 1.0 for fully verified. May slightly exceed 1.0 when fully synced to account for transactions in the memory pool which have been verified before being included in a block" - n: "→
`chainwork`" t: "string (hex)" diff --git a/_includes/devdoc/bitcoin-core/rpcs/rpcs/getblockcount.md b/_includes/devdoc/bitcoin-core/rpcs/rpcs/getblockcount.md index 586bbf08b8..a577fcfd2b 100644 --- a/_includes/devdoc/bitcoin-core/rpcs/rpcs/getblockcount.md +++ b/_includes/devdoc/bitcoin-core/rpcs/rpcs/getblockcount.md @@ -7,7 +7,7 @@ http://opensource.org/licenses/MIT. ##### GetBlockCount {% include helpers/subhead-links.md %} -{% assign summary_getBlockCount="returns the number of blocks in the local best block chain." %} +{% assign summary_getBlockCount="returns the number of blocks in the local best blockchain." %} {% autocrossref %} @@ -15,13 +15,13 @@ The `getblockcount` RPC {{summary_getBlockCount}} *Parameters: none* -*Result---the number of blocks in the local best block chain* +*Result---the number of blocks in the local best blockchain* {% itemplate ntpd1 %} - n: "`result`" t: "number (int)" p: "Required
(exactly 1)" - d: "The number of blocks in the local best block chain. For a new node with only the hardcoded genesis block, this number will be 0" + d: "The number of blocks in the local best blockchain. For a new node with only the hardcoded genesis block, this number will be 0" {% enditemplate %} diff --git a/_includes/devdoc/bitcoin-core/rpcs/rpcs/getblockhash.md b/_includes/devdoc/bitcoin-core/rpcs/rpcs/getblockhash.md index 344b0c99a3..d7f54a9ee0 100644 --- a/_includes/devdoc/bitcoin-core/rpcs/rpcs/getblockhash.md +++ b/_includes/devdoc/bitcoin-core/rpcs/rpcs/getblockhash.md @@ -7,7 +7,7 @@ http://opensource.org/licenses/MIT. ##### GetBlockHash {% include helpers/subhead-links.md %} -{% assign summary_getBlockHash="returns the header hash of a block at the given height in the local best block chain." %} +{% assign summary_getBlockHash="returns the header hash of a block at the given height in the local best blockchain." %} {% autocrossref %} diff --git a/_includes/devdoc/bitcoin-core/rpcs/rpcs/getchaintips.md b/_includes/devdoc/bitcoin-core/rpcs/rpcs/getchaintips.md index 365c1f5a58..800b3ec89d 100644 --- a/_includes/devdoc/bitcoin-core/rpcs/rpcs/getchaintips.md +++ b/_includes/devdoc/bitcoin-core/rpcs/rpcs/getchaintips.md @@ -7,7 +7,7 @@ http://opensource.org/licenses/MIT. ##### GetChainTips {% include helpers/subhead-links.md %} -{% assign summary_getChainTips="returns information about the highest-height block (tip) of each local block chain." %} +{% assign summary_getChainTips="returns information about the highest-height block (tip) of each local blockchain." %} {% autocrossref %} @@ -17,18 +17,18 @@ The `getchaintips` RPC {{summary_getChainTips}} *Parameters: none* -*Result---an array of block chain tips* +*Result---an array of blockchain tips* {% itemplate ntpd1 %} - n: "`result`" t: "array" p: "Required
(exactly 1)" - d: "An array of JSON objects, with each object describing a chain tip. At least one tip---the local best block chain---will always be present" + d: "An array of JSON objects, with each object describing a chain tip. At least one tip---the local best blockchain---will always be present" - n: "→
Tip" t: "object" p: "Required
(1 or more)" - d: "An object describing a particular chain tip. The first object will always describe the active chain (the local best block chain)" + d: "An object describing a particular chain tip. The first object will always describe the active chain (the local best blockchain)" - n: "→ →
`height`" t: "number (int)" @@ -43,12 +43,12 @@ The `getchaintips` RPC {{summary_getChainTips}} - n: "→ →
`branchlen`" t: "number (int)" p: "Required
(exactly 1)" - d: "The number of blocks that are on this chain but not on the main chain. For the local best block chain, this will be `0`; for all other chains, it will be at least `1`" + d: "The number of blocks that are on this chain but not on the main chain. For the local best blockchain, this will be `0`; for all other chains, it will be at least `1`" - n: "→ →
`status`" t: "string" p: "Required
(exactly 1)" - d: "The status of this chain. Valid values are:
• `active` for the local best block chain
• `invalid` for a chain that contains one or more invalid blocks
• `headers-only` for a chain with valid headers whose corresponding blocks both haven't been validated and aren't stored locally
• `valid-headers` for a chain with valid headers whose corresponding blocks are stored locally, but which haven't been fully validated
• `valid-fork` for a chain which is fully validated but which isn't part of the local best block chain (it was probably the local best block chain at some point)
• `unknown` for a chain whose reason for not being the active chain is unknown" + d: "The status of this chain. Valid values are:
• `active` for the local best blockchain
• `invalid` for a chain that contains one or more invalid blocks
• `headers-only` for a chain with valid headers whose corresponding blocks both haven't been validated and aren't stored locally
• `valid-headers` for a chain with valid headers whose corresponding blocks are stored locally, but which haven't been fully validated
• `valid-fork` for a chain which is fully validated but which isn't part of the local best blockchain (it was probably the local best blockchain at some point)
• `unknown` for a chain whose reason for not being the active chain is unknown" {% enditemplate %} diff --git a/_includes/devdoc/bitcoin-core/rpcs/rpcs/getdifficulty.md b/_includes/devdoc/bitcoin-core/rpcs/rpcs/getdifficulty.md index 5659b4d936..85f8832006 100644 --- a/_includes/devdoc/bitcoin-core/rpcs/rpcs/getdifficulty.md +++ b/_includes/devdoc/bitcoin-core/rpcs/rpcs/getdifficulty.md @@ -21,7 +21,7 @@ The `getdifficulty` RPC {{summary_getDifficulty}} - n: "`result`" t: "number (real)" p: "Required
(exactly 1)" - d: "The difficulty of creating a block with the same target threshold (nBits) as the highest-height block in the local best block chain. The number is a a multiple of the minimum difficulty" + d: "The difficulty of creating a block with the same target threshold (nBits) as the highest-height block in the local best blockchain. The number is a a multiple of the minimum difficulty" {% enditemplate %} diff --git a/_includes/devdoc/bitcoin-core/rpcs/rpcs/getinfo.md b/_includes/devdoc/bitcoin-core/rpcs/rpcs/getinfo.md index 7c29f6f6e5..c7054185ed 100644 --- a/_includes/devdoc/bitcoin-core/rpcs/rpcs/getinfo.md +++ b/_includes/devdoc/bitcoin-core/rpcs/rpcs/getinfo.md @@ -49,7 +49,7 @@ Core. Use the RPCs listed in the See Also subsection below instead. - n: "→
`blocks`" t: "number (int)" p: "Required
(exactly 1)" - d: "The number of blocks in the local best block chain. A new node with only the hardcoded genesis block will return `0`" + d: "The number of blocks in the local best blockchain. A new node with only the hardcoded genesis block will return `0`" - n: "→
`timeoffset`" t: "number (int)" @@ -69,7 +69,7 @@ Core. Use the RPCs listed in the See Also subsection below instead. - n: "→
`difficulty`" t: "number (real)" p: "Required
(exactly 1)" - d: "The difficulty of the highest-height block in the local best block chain" + d: "The difficulty of the highest-height block in the local best blockchain" - n: "→
`testnet`" t: "bool" diff --git a/_includes/devdoc/bitcoin-core/rpcs/rpcs/getmininginfo.md b/_includes/devdoc/bitcoin-core/rpcs/rpcs/getmininginfo.md index 8ca031bf19..809eeca51d 100644 --- a/_includes/devdoc/bitcoin-core/rpcs/rpcs/getmininginfo.md +++ b/_includes/devdoc/bitcoin-core/rpcs/rpcs/getmininginfo.md @@ -26,7 +26,7 @@ The `getmininginfo` RPC {{summary_getMiningInfo}} - n: "→
`blocks`" t: "number (int)" p: "Required
(exactly 1)" - d: "The height of the highest block on the local best block chain" + d: "The height of the highest block on the local best blockchain" - n: "→
`currentblocksize`" t: "number (int)" @@ -41,7 +41,7 @@ The `getmininginfo` RPC {{summary_getMiningInfo}} - n: "→
`difficulty`" t: "number (real)" p: "Required
(exactly 1)" - d: "If generation was enabled since the last time this node was restarted, this is the difficulty of the highest-height block in the local best block chain. Otherwise, this is the value `0`" + d: "If generation was enabled since the last time this node was restarted, this is the difficulty of the highest-height block in the local best blockchain. Otherwise, this is the value `0`" - n: "→
`errors`" t: "string" diff --git a/_includes/devdoc/bitcoin-core/rpcs/rpcs/getnetworkhashps.md b/_includes/devdoc/bitcoin-core/rpcs/rpcs/getnetworkhashps.md index 480e9f9941..daed82d3af 100644 --- a/_includes/devdoc/bitcoin-core/rpcs/rpcs/getnetworkhashps.md +++ b/_includes/devdoc/bitcoin-core/rpcs/rpcs/getnetworkhashps.md @@ -29,7 +29,7 @@ The `getnetworkhashps` RPC {{summary_getNetworkHashPS}} - n: "Height" t: "number (int)" p: "Optional
(0 or 1)" - d: "The height of the last block to use for calculating the average. Defaults to `-1` for the highest-height block on the local best block chain. If the specified height is higher than the highest block on the local best block chain, it will be interpreted the same as `-1`" + d: "The height of the last block to use for calculating the average. Defaults to `-1` for the highest-height block on the local best blockchain. If the specified height is higher than the highest block on the local best blockchain, it will be interpreted the same as `-1`" {% enditemplate %} diff --git a/_includes/devdoc/bitcoin-core/rpcs/rpcs/getpeerinfo.md b/_includes/devdoc/bitcoin-core/rpcs/rpcs/getpeerinfo.md index 3a248fe114..21764214c2 100644 --- a/_includes/devdoc/bitcoin-core/rpcs/rpcs/getpeerinfo.md +++ b/_includes/devdoc/bitcoin-core/rpcs/rpcs/getpeerinfo.md @@ -101,7 +101,7 @@ The `getpeerinfo` RPC {{summary_getPeerInfo}} - n: "→ →
`startingheight`" t: "number (int)" p: "Required
(exactly 1)" - d: "The height of the remote node's block chain when it connected to us as reported in its `version` message" + d: "The height of the remote node's blockchain when it connected to us as reported in its `version` message" - n: "→ →
`banscore`" t: "number (int)" diff --git a/_includes/devdoc/bitcoin-core/rpcs/rpcs/getrawtransaction.md b/_includes/devdoc/bitcoin-core/rpcs/rpcs/getrawtransaction.md index a19bc7ff4c..402c2141e8 100644 --- a/_includes/devdoc/bitcoin-core/rpcs/rpcs/getrawtransaction.md +++ b/_includes/devdoc/bitcoin-core/rpcs/rpcs/getrawtransaction.md @@ -41,7 +41,7 @@ The `getrawtransaction` RPC {{summary_getRawTransaction}} - n: "`result`" t: "null" p: "Required
(exactly 1)" - d: "If the transaction wasn't found, the result will be JSON `null`. This can occur because the transaction doesn't exist in the block chain or memory pool, or because it isn't part of the transaction index. See the Bitcoin Core `-help` entry for `-txindex`" + d: "If the transaction wasn't found, the result will be JSON `null`. This can occur because the transaction doesn't exist in the blockchain or memory pool, or because it isn't part of the transaction index. See the Bitcoin Core `-help` entry for `-txindex`" {% enditemplate %} @@ -67,17 +67,17 @@ The `getrawtransaction` RPC {{summary_getRawTransaction}} - n: "→
`blockhash`" t: "string (hex)" p: "Optional
(0 or 1)" - d: "If the transaction has been included in a block on the local best block chain, this is the hash of that block encoded as hex in RPC byte order" + d: "If the transaction has been included in a block on the local best blockchain, this is the hash of that block encoded as hex in RPC byte order" - n: "→
`confirmations`" t: "number (int)" p: "Required
(exactly 1)" - d: "If the transaction has been included in a block on the local best block chain, this is how many confirmations it has. Otherwise, this is `0`" + d: "If the transaction has been included in a block on the local best blockchain, this is how many confirmations it has. Otherwise, this is `0`" - n: "→
`time`" t: "number (int)" p: "Optional
(0 or 1)" - d: "If the transaction has been included in a block on the local best block chain, this is the block header time of that block (may be in the future)" + d: "If the transaction has been included in a block on the local best blockchain, this is the block header time of that block (may be in the future)" - n: "→
`blocktime`" t: "number (int)" diff --git a/_includes/devdoc/bitcoin-core/rpcs/rpcs/gettransaction.md b/_includes/devdoc/bitcoin-core/rpcs/rpcs/gettransaction.md index cca476fd2a..f46cd15afa 100644 --- a/_includes/devdoc/bitcoin-core/rpcs/rpcs/gettransaction.md +++ b/_includes/devdoc/bitcoin-core/rpcs/rpcs/gettransaction.md @@ -74,7 +74,7 @@ The `gettransaction` RPC {{summary_getTransaction}} - n: "→ →
`category`" t: "string" p: "Required
(exactly 1)" - d: "Set to one of the following values:
• `send` if sending payment
• `receive` if this wallet received payment in a regular transaction
• `generate` if a matured and spendable coinbase
• `immature` if a coinbase that is not spendable yet
• `orphan` if a coinbase from a block that's not in the local best block chain" + d: "Set to one of the following values:
• `send` if sending payment
• `receive` if this wallet received payment in a regular transaction
• `generate` if a matured and spendable coinbase
• `immature` if a coinbase that is not spendable yet
• `orphan` if a coinbase from a block that's not in the local best blockchain" - n: "→ →
`amount`" t: "number (bitcoins)" diff --git a/_includes/devdoc/bitcoin-core/rpcs/rpcs/gettxout.md b/_includes/devdoc/bitcoin-core/rpcs/rpcs/gettxout.md index ea921f27ab..d31182753a 100644 --- a/_includes/devdoc/bitcoin-core/rpcs/rpcs/gettxout.md +++ b/_includes/devdoc/bitcoin-core/rpcs/rpcs/gettxout.md @@ -55,7 +55,7 @@ The `gettxout` RPC {{summary_getTxOut}} - n: "→
`bestblock`" t: "string (hex)" p: "Required
(exactly 1)" - d: "The hash of the header of the block on the local best block chain which includes this transaction. The hash will encoded as hex in RPC byte order. If the transaction is not part of a block, the string will be empty" + d: "The hash of the header of the block on the local best blockchain which includes this transaction. The hash will encoded as hex in RPC byte order. If the transaction is not part of a block, the string will be empty" - n: "→
`confirmations`" t: "number (int)" diff --git a/_includes/devdoc/bitcoin-core/rpcs/rpcs/gettxoutsetinfo.md b/_includes/devdoc/bitcoin-core/rpcs/rpcs/gettxoutsetinfo.md index e3a98e816f..f76828eaa8 100644 --- a/_includes/devdoc/bitcoin-core/rpcs/rpcs/gettxoutsetinfo.md +++ b/_includes/devdoc/bitcoin-core/rpcs/rpcs/gettxoutsetinfo.md @@ -26,12 +26,12 @@ The `gettxoutsetinfo` RPC {{summary_getTxOutSetInfo}} - n: "→
`height`" t: "number (int)" p: "Required
(exactly 1)" - d: "The height of the local best block chain. A new node with only the hardcoded genesis block will have a height of 0" + d: "The height of the local best blockchain. A new node with only the hardcoded genesis block will have a height of 0" - n: "→
`bestblock`" t: "string (hex)" p: "Required
(exactly 1)" - d: "The hash of the header of the highest block on the local best block chain, encoded as hex in RPC byte order" + d: "The hash of the header of the highest block on the local best blockchain, encoded as hex in RPC byte order" - n: "→
`transactions`" t: "number (int)" diff --git a/_includes/devdoc/bitcoin-core/rpcs/rpcs/importaddress.md b/_includes/devdoc/bitcoin-core/rpcs/rpcs/importaddress.md index e76917cc2d..eb1168ef6b 100644 --- a/_includes/devdoc/bitcoin-core/rpcs/rpcs/importaddress.md +++ b/_includes/devdoc/bitcoin-core/rpcs/rpcs/importaddress.md @@ -35,7 +35,7 @@ The `importaddress` RPC {{summary_importAddress}} {% enditemplate %} -*Parameter #3---whether to rescan the block chain* +*Parameter #3---whether to rescan the blockchain* {% itemplate ntpd1 %} - n: "Rescan" diff --git a/_includes/devdoc/bitcoin-core/rpcs/rpcs/importprivkey.md b/_includes/devdoc/bitcoin-core/rpcs/rpcs/importprivkey.md index bcff61cadf..b282efc766 100644 --- a/_includes/devdoc/bitcoin-core/rpcs/rpcs/importprivkey.md +++ b/_includes/devdoc/bitcoin-core/rpcs/rpcs/importprivkey.md @@ -35,7 +35,7 @@ The `importprivkey` RPC {{summary_importPrivKey}} {% enditemplate %} -*Parameter #3---whether to rescan the block chain* +*Parameter #3---whether to rescan the blockchain* {% itemplate ntpd1 %} - n: "Rescan" @@ -59,7 +59,7 @@ The `importprivkey` RPC {{summary_importPrivKey}} Import the private key for the address mgnucj8nYqdrPFh2JfZSB1NmUThUGnmsqe, giving it a label and scanning the -entire block chain: +entire blockchain: {% highlight bash %} bitcoin-cli -testnet importprivkey \ diff --git a/_includes/devdoc/bitcoin-core/rpcs/rpcs/importwallet.md b/_includes/devdoc/bitcoin-core/rpcs/rpcs/importwallet.md index 0c2cf4507c..d5e5b87245 100644 --- a/_includes/devdoc/bitcoin-core/rpcs/rpcs/importwallet.md +++ b/_includes/devdoc/bitcoin-core/rpcs/rpcs/importwallet.md @@ -7,7 +7,7 @@ http://opensource.org/licenses/MIT. ##### ImportWallet {% include helpers/subhead-links.md %} -{% assign summary_importWallet="imports private keys from a file in wallet dump file format (see the `dumpwallet` RPC). These keys will be added to the keys currently in the wallet. This call may need to rescan all or parts of the block chain for transactions affecting the newly-added keys, which may take several minutes." %} +{% assign summary_importWallet="imports private keys from a file in wallet dump file format (see the `dumpwallet` RPC). These keys will be added to the keys currently in the wallet. This call may need to rescan all or parts of the blockchain for transactions affecting the newly-added keys, which may take several minutes." %} {% autocrossref %} diff --git a/_includes/devdoc/bitcoin-core/rpcs/rpcs/listsinceblock.md b/_includes/devdoc/bitcoin-core/rpcs/rpcs/listsinceblock.md index 891e64b5f9..7cfa0a8e90 100644 --- a/_includes/devdoc/bitcoin-core/rpcs/rpcs/listsinceblock.md +++ b/_includes/devdoc/bitcoin-core/rpcs/rpcs/listsinceblock.md @@ -31,7 +31,7 @@ The `listsinceblock` RPC {{summary_listSinceBlock}} - n: "Target Confirmations" t: "number (int)" p: "Optional
(0 or 1)" - d: "Sets the lastblock field of the results to the header hash of a block with this many confirmations. This does not affect which transactions are returned. Default is `1`, so the hash of the most recent block on the local best block chain is returned" + d: "Sets the lastblock field of the results to the header hash of a block with this many confirmations. This does not affect which transactions are returned. Default is `1`, so the hash of the most recent block on the local best blockchain is returned" {% enditemplate %} diff --git a/_includes/devdoc/bitcoin-core/rpcs/rpcs/listtransactions.md b/_includes/devdoc/bitcoin-core/rpcs/rpcs/listtransactions.md index 34b47b6632..c10d894c13 100644 --- a/_includes/devdoc/bitcoin-core/rpcs/rpcs/listtransactions.md +++ b/_includes/devdoc/bitcoin-core/rpcs/rpcs/listtransactions.md @@ -75,7 +75,8 @@ The `listtransactions` RPC {{summary_listTransactions}} - n: "→ →
`category`" t: "string" p: "Required
(exactly 1)" - d: "Set to one of the following values:
• `send` if sending payment
• `receive` if this wallet received payment in a regular transaction
• `generate` if a matured and spendable coinbase
• `immature` if a coinbase that is not spendable yet
• `orphan` if a coinbase from a block that's not in the local best block chain
• `move` if an off-block-chain move made with the `move` RPC" + d: "Set to one of the following values:
• `send` if sending payment
• `receive` if this wallet received payment in a regular transaction
• `generate` if a matured and spendable coinbase
• `immature` if a coinbase that is not spendable yet
• `orphan` if a coinbase from a block that's not in the local best +blockchain
• `move` if an off-blockchain move made with the `move` RPC" - n: "→ →
`amount`" t: "number (bitcoins)" @@ -105,17 +106,17 @@ The `listtransactions` RPC {{summary_listTransactions}} - n: "→ →
`blockhash`" t: "string (hex)" p: "Optional
(0 or 1)" - d: "Only returned for confirmed transactions. The hash of the block on the local best block chain which includes this transaction, encoded as hex in RPC byte order" + d: "Only returned for confirmed transactions. The hash of the block on the local best blockchain which includes this transaction, encoded as hex in RPC byte order" - n: "→ →
`blockindex`" t: "number (int)" p: "Optional
(0 or 1)" - d: "Only returned for confirmed transactions. The block height of the block on the local best block chain which includes this transaction" + d: "Only returned for confirmed transactions. The block height of the block on the local best blockchain which includes this transaction" - n: "→ →
`blocktime`" t: "number (int)" p: "Optional
(0 or 1)" - d: "Only returned for confirmed transactions. The block header time (Unix epoch time) of the block on the local best block chain which includes this transaction" + d: "Only returned for confirmed transactions. The block header time (Unix epoch time) of the block on the local best blockchain which includes this transaction" - n: "→ →
`txid`" t: "string (hex)" @@ -140,7 +141,7 @@ The `listtransactions` RPC {{summary_listTransactions}} - n: "→ →
`timereceived`" t: "number (int)" p: "Optional
(0 or 1)" - d: "A Unix epoch time when the transaction was detected by the local node, or the time of the block on the local best block chain that included the transaction. Not returned for *move* category payments" + d: "A Unix epoch time when the transaction was detected by the local node, or the time of the block on the local best blockchain that included the transaction. Not returned for *move* category payments" - n: "→ →
`comment`" t: "string" diff --git a/_includes/devdoc/bitcoin-core/rpcs/rpcs/move.md b/_includes/devdoc/bitcoin-core/rpcs/rpcs/move.md index 150d2ba2d8..32af924677 100644 --- a/_includes/devdoc/bitcoin-core/rpcs/rpcs/move.md +++ b/_includes/devdoc/bitcoin-core/rpcs/rpcs/move.md @@ -7,7 +7,7 @@ http://opensource.org/licenses/MIT. ##### Move {% include helpers/subhead-links.md %} -{% assign summary_move="moves a specified amount from one account in your wallet to another using an off-block-chain transaction." %} +{% assign summary_move="moves a specified amount from one account in your wallet to another using an off-blockchain transaction." %} {% autocrossref %} diff --git a/_includes/devdoc/bitcoin-core/rpcs/rpcs/prioritisetransaction.md b/_includes/devdoc/bitcoin-core/rpcs/rpcs/prioritisetransaction.md index 08aa53ea9e..0ead17c004 100644 --- a/_includes/devdoc/bitcoin-core/rpcs/rpcs/prioritisetransaction.md +++ b/_includes/devdoc/bitcoin-core/rpcs/rpcs/prioritisetransaction.md @@ -31,7 +31,7 @@ The `prioritisetransaction` RPC {{summary_prioritiseTransaction}} - n: "Priority" t: "number (real)" p: "Required
(exactly 1)" - d: "If positive, the priority to add to the transaction in addition to its computed priority; if negative, the priority to subtract from the transaction's computed priory. Computed priority is the age of each input in days since it was added to the block chain as an output (coinage) times the value of the input in satoshis (value) divided by the size of the serialized transaction (size), which is `coinage * value / size`" + d: "If positive, the priority to add to the transaction in addition to its computed priority; if negative, the priority to subtract from the transaction's computed priory. Computed priority is the age of each input in days since it was added to the blockchain as an output (coinage) times the value of the input in satoshis (value) divided by the size of the serialized transaction (size), which is `coinage * value / size`" {% enditemplate %} diff --git a/_includes/devdoc/bitcoin-core/rpcs/rpcs/submitblock.md b/_includes/devdoc/bitcoin-core/rpcs/rpcs/submitblock.md index 57fd1141c6..79cd1111b2 100644 --- a/_includes/devdoc/bitcoin-core/rpcs/rpcs/submitblock.md +++ b/_includes/devdoc/bitcoin-core/rpcs/rpcs/submitblock.md @@ -7,7 +7,7 @@ http://opensource.org/licenses/MIT. ##### SubmitBlock {% include helpers/subhead-links.md %} -{% assign summary_submitBlock="accepts a block, verifies it is a valid addition to the block chain, and broadcasts it to the network. Extra parameters are ignored by Bitcoin Core but may be used by mining pools or other programs." %} +{% assign summary_submitBlock="accepts a block, verifies it is a valid addition to the blockchain, and broadcasts it to the network. Extra parameters are ignored by Bitcoin Core but may be used by mining pools or other programs." %} {% autocrossref %} @@ -58,7 +58,7 @@ f0457bcb05865a94900ed11356d0b75228efb38c7785d6053ffff001d005d437\ '{ "workid": "test" }' {% endhighlight %} -Result (the block above was already on a local block chain): +Result (the block above was already on a local blockchain): {% highlight text %} duplicate diff --git a/_includes/devdoc/bitcoin-core/rpcs/rpcs/verifychain.md b/_includes/devdoc/bitcoin-core/rpcs/rpcs/verifychain.md index bc90446932..879e8bfb1c 100644 --- a/_includes/devdoc/bitcoin-core/rpcs/rpcs/verifychain.md +++ b/_includes/devdoc/bitcoin-core/rpcs/rpcs/verifychain.md @@ -7,7 +7,7 @@ http://opensource.org/licenses/MIT. ##### VerifyChain {% include helpers/subhead-links.md %} -{% assign summary_verifyChain="verifies each entry in the local block chain database." %} +{% assign summary_verifyChain="verifies each entry in the local blockchain database." %} {% autocrossref %} diff --git a/_includes/devdoc/bitcoin-core/rpcs/rpcs/verifytxoutproof.md b/_includes/devdoc/bitcoin-core/rpcs/rpcs/verifytxoutproof.md index 813694e71b..8602c7a15f 100644 --- a/_includes/devdoc/bitcoin-core/rpcs/rpcs/verifytxoutproof.md +++ b/_includes/devdoc/bitcoin-core/rpcs/rpcs/verifytxoutproof.md @@ -7,7 +7,7 @@ http://opensource.org/licenses/MIT. ##### VerifyTxOutProof {% include helpers/subhead-links.md %} -{% assign summary_verifyTxOutProof="verifies that a proof points to one or more transactions in a block, returning the transactions the proof commits to and throwing an RPC error if the block is not in our best block chain." %} +{% assign summary_verifyTxOutProof="verifies that a proof points to one or more transactions in a block, returning the transactions the proof commits to and throwing an RPC error if the block is not in our best blockchain." %} {% autocrossref %} diff --git a/_includes/devdoc/example_testing.md b/_includes/devdoc/example_testing.md index 5ac46587d8..b178f436ea 100644 --- a/_includes/devdoc/example_testing.md +++ b/_includes/devdoc/example_testing.md @@ -42,7 +42,7 @@ community, so please don't abuse it. For situations where interaction with random peers and blocks is unnecessary or unwanted, Bitcoin Core's regression test mode (regtest mode) lets you -instantly create a brand-new private block chain with the same basic +instantly create a brand-new private blockchain with the same basic rules as testnet---but one major difference: you choose when to create new blocks, so you have complete control over the environment. @@ -59,7 +59,7 @@ Bitcoin server starting {% autocrossref %} -Start `bitcoind` in regtest mode to create a private block chain. +Start `bitcoind` in regtest mode to create a private blockchain. {% endautocrossref %} @@ -75,7 +75,7 @@ bitcoin-cli -regtest generate 101 Generate 101 blocks using a special RPC which is only available in regtest mode. This takes about 30 seconds on -a generic PC. Because this is a new block chain using Bitcoin's default +a generic PC. Because this is a new blockchain using Bitcoin's default rules, the first blocks pay a block reward of 50 bitcoins. Unlike mainnet, in regtest mode only the first 150 blocks pay a reward of 50 bitcoins. However, a block must have 100 confirmations before that reward can be @@ -95,7 +95,7 @@ Verify that we now have 50 bitcoins available to spend. You can now use Bitcoin Core RPCs prefixed with `bitcoin-cli -regtest`. -Regtest wallets and block chain state (chainstate) are saved in the `regtest` +Regtest wallets and blockchain state (chainstate) are saved in the `regtest` subdirectory of the Bitcoin Core configuration directory. You can safely delete the `regtest` subdirectory and restart Bitcoin Core to start a new regtest. (See the [Developer Examples Introduction][devexamples] for default diff --git a/_includes/devdoc/example_transactions.md b/_includes/devdoc/example_transactions.md index b67fa9ce11..dc2fd166dc 100644 --- a/_includes/devdoc/example_transactions.md +++ b/_includes/devdoc/example_transactions.md @@ -583,7 +583,7 @@ Clean up the shell variables used. Unlike previous subsections, we're not going to send this transaction to the connected node with `sendrawtransaction`. This will allow us to illustrate in the Offline Signing subsection below how to spend a transaction which is not yet in -the block chain or memory pool. +the blockchain or memory pool. {% endautocrossref %} @@ -603,7 +603,7 @@ signing---which generally means signing a transaction without access to the current UTXO set. Offline signing is safe. However, in this example we will also be -spending an output which is not part of the block chain because the +spending an output which is not part of the blockchain because the transaction containing it has never been broadcast. That can be unsafe: ![Warning icon](/img/icons/icon_warning.svg) @@ -872,7 +872,7 @@ the UTXO. We have once again not generated an additional block, so the transactions -above have not yet become part of the regtest block chain. However, they +above have not yet become part of the regtest blockchain. However, they are part of the local node's memory pool. {% highlight bash %} diff --git a/_includes/devdoc/guide_block_chain.md b/_includes/devdoc/guide_block_chain.md index 451cf242d8..4365304993 100644 --- a/_includes/devdoc/guide_block_chain.md +++ b/_includes/devdoc/guide_block_chain.md @@ -4,18 +4,18 @@ http://opensource.org/licenses/MIT. {% endcomment %} {% assign filename="_includes/devdoc/guide_block_chain.md" %} -## Block Chain +## Blockchain {% include helpers/subhead-links.md %} {% autocrossref %} -The block chain provides Bitcoin's public ledger, an ordered and timestamped record +The blockchain provides Bitcoin's public ledger, an ordered and timestamped record of transactions. This system is used to protect against double spending and modification of previous transaction records. -Each full node in the Bitcoin network independently stores a block chain +Each full node in the Bitcoin network independently stores a blockchain containing only blocks validated by that node. When several nodes all -have the same blocks in their block chain, they are considered to be in +have the same blocks in their blockchain, they are considered to be in [consensus][/en/glossary/consensus]{:#term-consensus}{:.term}. The validation rules these nodes follow to maintain consensus are called [consensus rules][/en/glossary/consensus-rules]{:#term-consensus-rules}{:.term}. This section describes many of @@ -23,14 +23,14 @@ the consensus rules used by Bitcoin Core. {% endautocrossref %} -### Block Chain Overview +### Blockchain Overview {% include helpers/subhead-links.md %} {% autocrossref %} -![Block Chain Overview](/img/dev/en-blockchain-overview.svg) +![Blockchain Overview](/img/dev/en-blockchain-overview.svg) -The illustration above shows a simplified version of a block chain. +The illustration above shows a simplified version of a blockchain. A [block][/en/glossary/block]{:#term-block}{:.term} of one or more new transactions is collected into the transaction data part of a block. Copies of each transaction are hashed, and the hashes are then paired, @@ -54,14 +54,14 @@ previous transaction. A single transaction can create multiple outputs, as would be the case when sending to multiple addresses, but each output of a particular transaction can only be used as an input once in the -block chain. Any subsequent reference is a forbidden double +blockchain. Any subsequent reference is a forbidden double spend---an attempt to spend the same satoshis twice. Outputs are tied to [transaction identifiers (TXIDs)][/en/glossary/txid]{:#term-txid}{:.term}, which are the hashes of signed transactions. Because each output of a particular transaction can only be spent once, -the outputs of all transactions included in the block chain can be categorized as either +the outputs of all transactions included in the blockchain can be categorized as either [Unspent Transaction Outputs (UTXOs)][/en/glossary/unspent-transaction-output]{:#term-utxo}{:.term} or spent transaction outputs. For a payment to be valid, it must only use UTXOs as inputs. @@ -83,16 +83,16 @@ satoshi transaction fee. {% autocrossref %} -The block chain is collaboratively maintained by anonymous peers on the network, so +The blockchain is collaboratively maintained by anonymous peers on the network, so Bitcoin requires that each block prove a significant amount of work was invested in its creation to ensure that untrustworthy peers who want to modify past blocks have to work harder than honest peers who only want to add new blocks to the -block chain. +blockchain. Chaining blocks together makes it impossible to modify transactions included in any block without modifying all following blocks. As a result, the cost to modify a particular block increases with every new block -added to the block chain, magnifying the effect of the proof of work. +added to the blockchain, magnifying the effect of the proof of work. The [proof of work][/en/glossary/proof-of-work]{:#term-proof-of-work}{:.term} used in Bitcoin takes advantage of the apparently random nature of cryptographic hashes. @@ -114,7 +114,7 @@ that a given hash attempt will generate a number below the [target][/en/glossary threshold. Bitcoin assumes a linear probability that the lower it makes the target threshold, the more hash attempts (on average) will need to be tried. -New blocks will only be added to the block chain if their hash is at +New blocks will only be added to the blockchain if their hash is at least as challenging as a [difficulty][/en/glossary/difficulty]{:#term-difficulty}{:.term} value expected by the consensus protocol. Every 2,016 blocks, the network uses timestamps stored in each block header to calculate the number of seconds elapsed between generation @@ -159,21 +159,21 @@ the merkle tree. {% autocrossref %} Any Bitcoin miner who successfully hashes a block header to a value -below the target threshold can add the entire block to the block chain +below the target threshold can add the entire block to the blockchain (assuming the block is otherwise valid). These blocks are commonly addressed by their [block height][/en/glossary/block-height]{:#term-block-height}{:.term}---the number of blocks between them and the first Bitcoin block (block 0, most commonly known as the [genesis block][/en/glossary/genesis-block]{:#term-genesis-block}{:.term}). For example, block 2016 is where difficulty could have first been adjusted. -![Common And Uncommon Block Chain Forks](/img/dev/en-blockchain-fork.svg) +![Common And Uncommon Blockchain Forks](/img/dev/en-blockchain-fork.svg) Multiple blocks can all have the same block height, as is common when two or more miners each produce a block at roughly the same time. This -creates an apparent [fork][/en/glossary/fork]{:#term-fork}{:.term} in the block chain, as shown in the +creates an apparent [fork][/en/glossary/fork]{:#term-fork}{:.term} in the blockchain, as shown in the illustration above. -When miners produce simultaneous blocks at the end of the block chain, each +When miners produce simultaneous blocks at the end of the blockchain, each node individually chooses which block to accept. In the absence of other considerations, discussed below, nodes usually use the first block they see. @@ -188,11 +188,11 @@ to recreate and throw away [stale blocks][/en/glossary/stale-block]{:#term-stale those terms are also used for true orphan blocks without a known parent block.) Long-term forks are possible if different miners work at cross-purposes, -such as some miners diligently working to extend the block chain at the +such as some miners diligently working to extend the blockchain at the same time other miners are attempting a 51 percent attack to revise transaction history. -Since multiple blocks can have the same height during a block chain fork, block +Since multiple blocks can have the same height during a blockchain fork, block height should not be used as a globally unique identifier. Instead, blocks are usually referenced by the hash of their header (often with the byte order reversed, and in hexadecimal). @@ -210,7 +210,7 @@ spend the block reward (comprised of a block subsidy and any transaction fees pa The UTXO of a coinbase transaction has the special condition that it cannot be spent (used as an input) for at least 100 blocks. This temporarily prevents a miner from spending the transaction fees and block reward from a -block that may later be determined to be stale (and therefore the coinbase transaction destroyed) after a block chain fork. +block that may later be determined to be stale (and therefore the coinbase transaction destroyed) after a blockchain fork. Blocks are not required to include any non-coinbase transactions, but miners almost always do include additional transactions in order to @@ -293,7 +293,7 @@ creating two possible ways consensus can break: because it follows the old rules. In the first case, rejection by non-upgraded nodes, mining software -which gets block chain data from those non-upgraded nodes refuses to +which gets blockchain data from those non-upgraded nodes refuses to build on the same chain as mining software getting data from upgraded nodes. This creates permanently divergent chains---one for non-upgraded nodes and one for upgraded nodes---called a [hard @@ -302,19 +302,19 @@ fork][/en/glossary/hard-fork]{:#term-hard-fork}{:.term}. ![Hard Fork](/img/dev/en-hard-fork.svg) In the second case, rejection by upgraded nodes, it's possible to keep -the block chain from permanently diverging if upgraded nodes control a +the blockchain from permanently diverging if upgraded nodes control a majority of the hash rate. That's because, in this case, non-upgraded nodes will accept as valid all the same blocks as upgraded nodes, so the upgraded nodes can build a stronger chain that the non-upgraded nodes -will accept as the best valid block chain. This is called a [soft +will accept as the best valid blockchain. This is called a [soft fork][/en/glossary/soft-fork]{:#term-soft-fork}{:.term}. ![Soft Fork](/img/dev/en-soft-fork.svg) -Although a fork is an actual divergence in block chains, changes to the +Although a fork is an actual divergence in blockchains, changes to the consensus rules are often described by their potential to create either a hard or soft fork. For example, "increasing the block size above 1 MB -requires a hard fork." In this example, an actual block chain fork is +requires a hard fork." In this example, an actual blockchain fork is not required---but it is a possible outcome. **Resources:** [BIP16][], [BIP30][], and [BIP34][] were implemented as @@ -336,20 +336,20 @@ Non-upgraded nodes may use and distribute incorrect information during both types of forks, creating several situations which could lead to financial loss. In particular, non-upgraded nodes may relay and accept transactions that are considered invalid by upgraded nodes and so will -never become part of the universally-recognized best block chain. +never become part of the universally-recognized best blockchain. Non-upgraded nodes may also refuse to relay blocks or transactions which -have already been added to the best block chain, or soon will be, and so +have already been added to the best blockchain, or soon will be, and so provide incomplete information. Bitcoin Core includes code that detects a hard fork by looking at block -chain proof of work. If a non-upgraded node receives block chain headers +chain proof of work. If a non-upgraded node receives blockchain headers demonstrating at least six blocks more proof of work than the best chain it considers valid, the node reports an error in the `getinfo` RPC results and runs the `-alertnotify` command if set. This warns the operator that the non-upgraded node can't switch to what is likely the -best block chain. +best blockchain. Full nodes can also check block and transaction version numbers. If the block or transaction version numbers seen in several recent blocks are diff --git a/_includes/devdoc/guide_contracts.md b/_includes/devdoc/guide_contracts.md index c566305e64..f217ec82d3 100644 --- a/_includes/devdoc/guide_contracts.md +++ b/_includes/devdoc/guide_contracts.md @@ -73,7 +73,7 @@ keys provided). Bob gives the redeem script to Charlie, who checks to make sure his public key and Alice's public key are included. Then he hashes the redeem script to create a P2SH redeem script and pays the satoshis to it. Bob -sees the payment get added to the block chain and ships the merchandise. +sees the payment get added to the blockchain and ships the merchandise. Unfortunately, the merchandise gets slightly damaged in transit. Charlie wants a full refund, but Bob thinks a 10% refund is sufficient. They @@ -211,7 +211,7 @@ all under an Apache license. {% autocrossref %} Alice is concerned about her privacy. She knows every transaction gets -added to the public block chain, so when Bob and Charlie pay her, they +added to the public blockchain, so when Bob and Charlie pay her, they can each easily track those satoshis to learn what Bitcoin addresses she pays, how much she pays them, and possibly how many satoshis she has left. @@ -252,16 +252,16 @@ which output, so they can each spend their output with plausible deniability. Now when Bob or Charlie try to track Alice's transactions through the -block chain, they'll also see transactions made by Nemo and +blockchain, they'll also see transactions made by Nemo and Neminem. If Alice does a few more CoinJoins, Bob and Charlie might have to guess which transactions made by dozens or hundreds of people were actually made by Alice. -The complete history of Alice's satoshis is still in the block chain, +The complete history of Alice's satoshis is still in the blockchain, so a determined investigator could talk to the people AnonGirl CoinJoined with to find out the ultimate origin of her satoshis and possibly reveal AnonGirl as Alice. But against anyone casually browsing -block chain history, Alice gains plausible deniability. +blockchain history, Alice gains plausible deniability. The CoinJoin technique described above costs the participants a small amount of satoshis to pay the transaction fee. An alternative @@ -273,7 +273,7 @@ She announces her intention to spend satoshis and waits until someone else wants to make a purchase, likely from a different merchant. Then they combine their inputs the same way as before but set the outputs to the separate merchant addresses so nobody will be able to figure -out solely from block chain history which one of them bought what from +out solely from blockchain history which one of them bought what from the merchants. Since they would've had to pay a transaction fee to make their purchases diff --git a/_includes/devdoc/guide_mining.md b/_includes/devdoc/guide_mining.md index 47ba5395a7..205caf9893 100644 --- a/_includes/devdoc/guide_mining.md +++ b/_includes/devdoc/guide_mining.md @@ -9,7 +9,7 @@ http://opensource.org/licenses/MIT. {% autocrossref %} -Mining adds new blocks to the block chain, making transaction history +Mining adds new blocks to the blockchain, making transaction history hard to modify. Mining today takes on two forms: * Solo mining, where the miner attempts to generate new blocks on his @@ -53,7 +53,7 @@ On the other hand, if a hash is found below the target threshold, the mining hardware returns the block header with the successful nonce to the mining software. The mining software combines the header with the block and sends the completed block to `bitcoind` to be broadcast to the network for addition to the -block chain. +blockchain. {% endautocrossref %} @@ -74,7 +74,7 @@ construct block headers. In pooled mining, the mining pool sets the target threshold a few orders of magnitude higher (less difficult) than the network difficulty. This causes the mining hardware to return many block headers -which don't hash to a value eligible for inclusion on the block chain +which don't hash to a value eligible for inclusion on the blockchain but which do hash below the pool's target, proving (on average) that the miner checked a percentage of the possible hash values. @@ -87,7 +87,7 @@ transaction must pay the pool.) The information the miner sends to the pool is called a share because it proves the miner did a share of the work. By chance, some shares the pool receives will also be below the network target---the mining pool -sends these to the network to be added to the block chain. +sends these to the network to be added to the blockchain. The block reward and transaction fees that come from mining that block are paid to the mining pool. The mining pool pays out a portion of diff --git a/_includes/devdoc/guide_operating_modes.md b/_includes/devdoc/guide_operating_modes.md index 94519c1ca3..8d95ee25d7 100644 --- a/_includes/devdoc/guide_operating_modes.md +++ b/_includes/devdoc/guide_operating_modes.md @@ -9,7 +9,7 @@ http://opensource.org/licenses/MIT. {% autocrossref %} -Currently there are two primary methods of validating the block chain as a client: Full nodes and SPV clients. Other methods, such as server-trusting methods, are not discussed as they are not recommended. +Currently there are two primary methods of validating the blockchain as a client: Full nodes and SPV clients. Other methods, such as server-trusting methods, are not discussed as they are not recommended. {% endautocrossref %} @@ -18,9 +18,9 @@ Currently there are two primary methods of validating the block chain as a clien {% autocrossref %} -The first and most secure model is the one followed by Bitcoin Core, also known as a “thick” or “full chain” client. This security model assures the validity of the block chain by downloading and validating blocks from the genesis block all the way to the most recently discovered block. This is known as using the *height* of a particular block to verify the client’s view of the network. +The first and most secure model is the one followed by Bitcoin Core, also known as a “thick” or “full chain” client. This security model assures the validity of the blockchain by downloading and validating blocks from the genesis block all the way to the most recently discovered block. This is known as using the *height* of a particular block to verify the client’s view of the network. -For a client to be fooled, an adversary would need to give a complete alternative block chain history that is of greater difficulty than the current “true” chain, which is impossible due to the fact that the longest chain is by definition the true chain. After the suggested six confirmations, the ability to fool the client become intractable, as only a single honest network node is needed to have the complete state of the block chain. +For a client to be fooled, an adversary would need to give a complete alternative blockchain history that is of greater difficulty than the current “true” chain, which is impossible due to the fact that the longest chain is by definition the true chain. After the suggested six confirmations, the ability to fool the client become intractable, as only a single honest network node is needed to have the complete state of the blockchain. ![Block Height Compared To Block Depth](/img/dev/en-block-height-vs-depth.svg) @@ -31,11 +31,11 @@ For a client to be fooled, an adversary would need to give a complete alternativ {% autocrossref %} -An alternative approach detailed in the [original Bitcoin paper][bitcoinpdf] is a client that only downloads the headers of blocks during the initial syncing process and then requests transactions from full nodes as needed. This scales linearly with the height of the block chain at only 80 bytes per block header, or up to 4.2MB per year, regardless of total block size. +An alternative approach detailed in the [original Bitcoin paper][bitcoinpdf] is a client that only downloads the headers of blocks during the initial syncing process and then requests transactions from full nodes as needed. This scales linearly with the height of the blockchain at only 80 bytes per block header, or up to 4.2MB per year, regardless of total block size. -As described in the white paper, the merkle root in the block header along with a merkle branch can prove to the SPV client that the transaction in question is embedded in a block in the block chain. This does not guarantee validity of the transactions that are embedded. Instead it demonstrates the amount of work required to perform a double-spend attack. +As described in the white paper, the merkle root in the block header along with a merkle branch can prove to the SPV client that the transaction in question is embedded in a block in the blockchain. This does not guarantee validity of the transactions that are embedded. Instead it demonstrates the amount of work required to perform a double-spend attack. -The block's depth in the block chain corresponds to the cumulative difficulty that has been performed to build on top of that particular block. The SPV client knows the merkle root and associated transaction information, and requests the respective merkle branch from a full node. Once the merkle branch has been retrieved, proving the existence of the transaction in the block, the SPV client can then look to block *depth* as a proxy for transaction validity and security. The cost of an attack on a user by a malicious node who inserts an invalid transaction grows with the cumulative difficulty built on top of that block, since the malicious node alone will be mining this forged chain. +The block's depth in the blockchain corresponds to the cumulative difficulty that has been performed to build on top of that particular block. The SPV client knows the merkle root and associated transaction information, and requests the respective merkle branch from a full node. Once the merkle branch has been retrieved, proving the existence of the transaction in the block, the SPV client can then look to block *depth* as a proxy for transaction validity and security. The cost of an attack on a user by a malicious node who inserts an invalid transaction grows with the cumulative difficulty built on top of that block, since the malicious node alone will be mining this forged chain. {% endautocrossref %} @@ -96,7 +96,7 @@ Bloom filters were standardized for use via [BIP37](https://github.com/bitcoin/b {% autocrossref %} -There are future proposals such as Unspent Transaction Output (UTXO) commitments in the block chain to find a more satisfactory middle-ground for clients between needing a complete copy of the block chain, or trusting that a majority of your connected peers are not lying. UTXO commitments would enable a very secure client using a finite amount of storage using a data structure that is authenticated in the block chain. These type of proposals are, however, in very early stages, and will require soft forks in the network. +There are future proposals such as Unspent Transaction Output (UTXO) commitments in the blockchain to find a more satisfactory middle-ground for clients between needing a complete copy of the blockchain, or trusting that a majority of your connected peers are not lying. UTXO commitments would enable a very secure client using a finite amount of storage using a data structure that is authenticated in the blockchain. These type of proposals are, however, in very early stages, and will require soft forks in the network. Until these types of operating modes are implemented, modes should be chosen based on the likely threat model, computing and bandwidth constraints, and liability in bitcoin value. diff --git a/_includes/devdoc/guide_p2p_network.md b/_includes/devdoc/guide_p2p_network.md index 299afb9c44..7a01219e3a 100644 --- a/_includes/devdoc/guide_p2p_network.md +++ b/_includes/devdoc/guide_p2p_network.md @@ -148,7 +148,7 @@ In order to maintain a connection with a peer, nodes by default will send a mess Before a full node can validate unconfirmed transactions and recently-mined blocks, it must download and validate all blocks from block 1 (the block after the hardcoded genesis block) to the current tip -of the best block chain. This is the Initial Block Download (IBD) or +of the best blockchain. This is the Initial Block Download (IBD) or initial sync. Although the word "initial" implies this method is only used once, it @@ -158,10 +158,10 @@ for a long time. In this case, a node can use the IBD method to download all the blocks which were produced since the last time it was online. Bitcoin Core uses the IBD method any time the last block on its local -best block chain has a block header time more than 24 hours in the past. -Bitcoin Core 0.10.0 will also perform IBD if its local best block chain is +best blockchain has a block header time more than 24 hours in the past. +Bitcoin Core 0.10.0 will also perform IBD if its local best blockchain is more than 144 blocks lower than its local best header chain (that is, -the local block chain is more than about 24 hours in the past). +the local blockchain is more than about 24 hours in the past). {% endautocrossref %} @@ -172,12 +172,12 @@ the local block chain is more than about 24 hours in the past). Bitcoin Core (up until version [0.9.3][bitcoin core 0.9.3]) uses a simple initial block download (IBD) method we'll call *blocks-first*. -The goal is to download the blocks from the best block chain in sequence. +The goal is to download the blocks from the best blockchain in sequence. ![Overview Of Blocks-First Method](/img/dev/en-blocks-first-flowchart.svg) The first time a node is started, it only has a single block in its -local best block chain---the hardcoded genesis block (block 0). This +local best blockchain---the hardcoded genesis block (block 0). This node chooses a remote peer, called the sync node, and sends it the `getblocks` message illustrated below. @@ -189,7 +189,7 @@ sends the header hash of the only block it has, the genesis block to all zeroes to request a maximum-size response. Upon receipt of the `getblocks` message, the sync node takes the first -(and only) header hash and searches its local best block chain for a +(and only) header hash and searches its local best blockchain for a block with that header hash. It finds that block 0 matches, so it replies with 500 block inventories (the maximum response to a `getblocks` message) starting from block 1. It sends these inventories @@ -203,7 +203,7 @@ instance of the object. For blocks, the unique identifier is a hash of the block's header. The block inventories appear in the `inv` message in the same order they -appear in the block chain, so this first `inv` message contains +appear in the blockchain, so this first `inv` message contains inventories for blocks 1 through 501. (For example, the hash of block 1 is 4860...0000 as seen in the illustration above.) @@ -237,7 +237,7 @@ below: ![Second GetBlocks Message Sent During IBD](/img/dev/en-ibd-getblocks2.svg) Upon receipt of the second `getblocks` message, the sync node searches -its local best block chain for a block that matches one of the header +its local best blockchain for a block that matches one of the header hashes in the message, trying each hash in the order they were received. If it finds a matching hash, it replies with 500 block inventories starting with the next block from that point. But if there is no @@ -246,15 +246,15 @@ two nodes have in common is block 0 and so it sends an `inv` starting with block 1 (the same `inv` message seen several illustrations above). This repeated search allows the sync node to send useful inventories even if -the IBD node's local block chain forked from the sync node's local block +the IBD node's local blockchain forked from the sync node's local block chain. This fork detection becomes increasingly useful the closer the -IBD node gets to the tip of the block chain. +IBD node gets to the tip of the blockchain. When the IBD node receives the second `inv` message, it will request those blocks using `getdata` messages. The sync node will respond with `block` messages. Then the IBD node will request more inventories with another `getblocks` message---and the cycle will repeat until the IBD -node is synced to the tip of the block chain. At that point, the node +node is synced to the tip of the blockchain. At that point, the node will accept blocks sent through the regular block broadcasting described in a later subsection. @@ -277,17 +277,17 @@ of its downloading. This has several implications: download from a single sync node at a time. * **Download Restarts:** The sync node can send a non-best (but - otherwise valid) block chain to the IBD node. The IBD node won't be + otherwise valid) blockchain to the IBD node. The IBD node won't be able to identify it as non-best until the initial block download nears - completion, forcing the IBD node to restart its block chain download + completion, forcing the IBD node to restart its blockchain download over again from a different node. Bitcoin Core ships with several - block chain checkpoints at various block heights selected by + blockchain checkpoints at various block heights selected by developers to help an IBD node detect that it is being fed an - alternative block chain history---allowing the IBD node to restart + alternative blockchain history---allowing the IBD node to restart its download earlier in the process. * **Disk Fill Attacks:** Closely related to the download restarts, if - the sync node sends a non-best (but otherwise valid) block chain, the + the sync node sends a non-best (but otherwise valid) blockchain, the chain will be stored on disk, wasting space and possibly filling up the disk drive with useless data. @@ -324,7 +324,7 @@ solves several problems with the older blocks-first IBD method. ![Overview Of Headers-First Method](/img/dev/en-headers-first-flowchart.svg) The first time a node is started, it only has a single block in its -local best block chain---the hardcoded genesis block (block 0). The +local best blockchain---the hardcoded genesis block (block 0). The node chooses a remote peer, which we'll call the sync node, and sends it the `getheaders` message illustrated below. @@ -336,7 +336,7 @@ sends the header hash of the only block it has, the genesis block to all zeroes to request a maximum-size response. Upon receipt of the `getheaders` message, the sync node takes the first -(and only) header hash and searches its local best block chain for a +(and only) header hash and searches its local best blockchain for a block with that header hash. It finds that block 0 matches, so it replies with 2,000 header (the maximum response) starting from block 1. It sends these header hashes in the `headers` message @@ -402,7 +402,7 @@ stalling node and attempt to connect to another node. For example, in the illustration above, Node A will be disconnected if it doesn't send block 3 within at least two seconds. -Once the IBD node is synced to the tip of the block chain, it will +Once the IBD node is synced to the tip of the blockchain, it will accept blocks sent through the regular block broadcasting described in a later subsection. @@ -485,7 +485,7 @@ Blocks-first nodes may download orphan blocks---blocks whose previous block header hash field refers to a block header this node hasn't seen yet. In other words, orphan blocks have no known parent (unlike stale blocks, which have known parents but which aren't part of -the best block chain). +the best blockchain). ![Difference Between Orphan And Stale Blocks](/img/dev/en-orphan-stale-definition.svg) diff --git a/_includes/devdoc/guide_payment_processing.md b/_includes/devdoc/guide_payment_processing.md index 10ec3ca2db..38d2d0e244 100644 --- a/_includes/devdoc/guide_payment_processing.md +++ b/_includes/devdoc/guide_payment_processing.md @@ -94,7 +94,7 @@ payment requests: Using a separate address for each incoming payment makes it trivial to determine which customers have paid their payment requests. Your applications need only track the association between a particular payment -request and the address used in it, and then scan the block chain for +request and the address used in it, and then scan the blockchain for transactions matching that address. The next subsections will describe in detail the following four @@ -390,7 +390,7 @@ Charlie's wallet sees the PaymentACK and tells Charlie that the payment has been sent. The PaymentACK doesn't mean that Bob has verified Charlie's payment---see the Verifying Payment subsection below---but it does mean that Charlie can go do something else while the transaction gets confirmed. -After Bob's server verifies from the block chain that Charlie's +After Bob's server verifies from the blockchain that Charlie's transaction has been suitably confirmed, it authorizes shipping Charlie's order. @@ -402,7 +402,7 @@ otherwise-proven information. received an invoice to pay a specified pubkey script for a specified number of satoshis for goods specified in the memo field. -* The Bitcoin block chain can prove that the pubkey script specified by +* The Bitcoin blockchain can prove that the pubkey script specified by Bob was paid the specified number of satoshis. If a refund needs to be issued, Bob's server can safely pay the @@ -416,18 +416,18 @@ for more details. {% autocrossref %} -As explained in the [Transactions][] and [Block Chain][section block chain] sections, broadcasting +As explained in the [Transactions][] and [Blockchain][section blockchain] sections, broadcasting a transaction to the network doesn't ensure that the receiver gets paid. A malicious spender can create one transaction that pays the receiver and a second one that pays the same input back to himself. Only -one of these transactions will be added to the block chain, and nobody +one of these transactions will be added to the blockchain, and nobody can say for sure which one it will be. Two or more transactions spending the same input are commonly referred to as a [double spend][/en/glossary/double-spend]{:#term-double-spend}{:.term}. Once the transaction is included in a block, double spends are -impossible without modifying block chain history to replace the +impossible without modifying blockchain history to replace the transaction, which is quite difficult. Using this system, the Bitcoin protocol can give each of your transactions an updating confidence score based on the number of blocks which would need to be modified to replace @@ -495,7 +495,7 @@ estimate the amount of time until they're added to a block. Another example could be to detect a fork when multiple peers report differing block header hashes at the same block height. Your program can go into a safe mode if the fork extends for more than two blocks, indicating a possible problem with the -block chain. For more details, see the [Detecting Forks +blockchain. For more details, see the [Detecting Forks subsection][section detecting forks]. Another good source of double-spend protection can be human intelligence. For @@ -565,7 +565,7 @@ which outputs to spend first. There are a few different algorithms which can lead to different results. * A merge avoidance algorithm makes it harder for outsiders looking - at block chain data to figure out how many satoshis the receiver has + at blockchain data to figure out how many satoshis the receiver has earned, spent, and saved. * A last-in-first-out (LIFO) algorithm spends newly acquired satoshis diff --git a/_includes/devdoc/guide_transactions.md b/_includes/devdoc/guide_transactions.md index e028abdd44..17bed27c5e 100644 --- a/_includes/devdoc/guide_transactions.md +++ b/_includes/devdoc/guide_transactions.md @@ -28,7 +28,7 @@ To keep things simple, this section pretends coinbase transactions do not exist. Coinbase transactions can only be created by Bitcoin miners and they're an exception to many of the rules listed below. Instead of pointing out the coinbase exception to each rule, we invite you to read -about coinbase transactions in the block chain section of this guide. +about coinbase transactions in the blockchain section of this guide. ![The Parts Of A Transaction](/img/dev/en-tx-overview.svg) @@ -104,7 +104,7 @@ output if they can prove they control the private key corresponding to Bob's hashed public key. These instructions are called the [pubkey script][/en/glossary/pubkey-script]{:#term-pubkey-script}{:.term} or scriptPubKey. -Alice broadcasts the transaction and it is added to the block chain. +Alice broadcasts the transaction and it is added to the blockchain. The network categorizes it as an Unspent Transaction Output (UTXO), and Bob's wallet software displays it as a spendable balance. @@ -188,7 +188,7 @@ The script language is a [Forth-like](https://en.wikipedia.org/wiki/Forth_%28programming_language%29) stack-based language deliberately designed to be stateless and not Turing complete. Statelessness ensures that once a transaction is added -to the block chain, there is no condition which renders it permanently +to the blockchain, there is no condition which renders it permanently unspendable. Turing-incompleteness (specifically, a lack of loops or gotos) makes the script language less flexible and more predictable, greatly simplifying the security model. @@ -429,7 +429,7 @@ Signature script: [Null data][/en/glossary/null-data-transaction]{:#term-null-data}{:.term} pubkey scripts let you add a small amount of arbitrary data to the block chain in exchange for paying a transaction fee, but doing so is discouraged. (Null data is a standard pubkey script type only because some people were adding data -to the block chain in more harmful ways.) +to the blockchain in more harmful ways.) {% endautocrossref %} @@ -541,7 +541,7 @@ pay) flag, creating three new combined types: Because each input is signed, a transaction with multiple inputs can have multiple signature hash types signing different parts of the transaction. For example, a single-input transaction signed with `NONE` could have its -output changed by the miner who adds it to the block chain. On the other +output changed by the miner who adds it to the blockchain. On the other hand, if a two-input transaction has one input signed with `NONE` and one input signed with `ALL`, the `ALL` signer can choose where to spend the satoshis without consulting the `NONE` signer---but nobody else can @@ -564,7 +564,7 @@ hash types sign, including the procedure for inserting the subscript --> One thing all signature hash types sign is the transaction's [locktime][/en/glossary/locktime]{:#term-locktime}{:.term}. (Called nLockTime in the Bitcoin Core source code.) The locktime indicates the earliest time a transaction can be added to -the block chain. +the blockchain. Locktime allows signers to create time-locked transactions which will only become valid in the future, giving the signers a chance to change @@ -574,12 +574,12 @@ If any of the signers change their mind, they can create a new non-locktime transaction. The new transaction will use, as one of its inputs, one of the same outputs which was used as an input to the locktime transaction. This makes the locktime transaction -invalid if the new transaction is added to the block chain before +invalid if the new transaction is added to the blockchain before the time lock expires. Care must be taken near the expiry time of a time lock. The peer-to-peer network allows block time to be up to two hours ahead of -real time, so a locktime transaction can be added to the block chain up +real time, so a locktime transaction can be added to the blockchain up to two hours before its time lock officially expires. Also, blocks are not created at guaranteed intervals, so any attempt to cancel a valuable transaction should be made a few hours before the time lock expires. @@ -622,7 +622,7 @@ enable locktime. Transactions typically pay transaction fees based on the total byte size of the signed transaction. The transaction fee is given to the -Bitcoin miner, as explained in the [block chain section][section block chain], and so it is +Bitcoin miner, as explained in the [blockchain section][section blockchain], and so it is ultimately up to each miner to choose the minimum transaction fee they will accept. @@ -662,7 +662,7 @@ outputs be sent to a new P2PKH or P2SH address. In a transaction, the spender and receiver each reveal to each other all public keys or addresses used in the transaction. This allows either -person to use the public block chain to track past and future +person to use the public blockchain to track past and future transactions involving the other person's same public keys or addresses. If the same public key is reused often, as happens when people use @@ -678,7 +678,7 @@ Even better, using new public keys or [unique addresses][]{:#term-unique-address}{:.term} when accepting payments or creating change outputs can be combined with other techniques discussed later, such as CoinJoin or merge avoidance, to make it extremely difficult to -use the block chain by itself to reliably track how users receive and +use the blockchain by itself to reliably track how users receive and spend their satoshis. Avoiding key reuse can also provide security against attacks which might @@ -691,7 +691,7 @@ described below, with more general attacks hypothesized). first time satoshis sent to those addresses are spent, so attacks are effectively useless unless they can reconstruct private keys in less than the hour or two it takes for a transaction to be well - protected by the block chain. + protected by the blockchain. 2. Unique (non-reused) private keys protect against the second type of attack by only generating one signature per private key, so attackers @@ -730,14 +730,14 @@ identifier (txid), a modified transaction will not have the txid its creator expected. This isn't a problem for most Bitcoin transactions which are designed to -be added to the block chain immediately. But it does become a problem +be added to the blockchain immediately. But it does become a problem when the output from a transaction is spent before that transaction is -added to the block chain. +added to the blockchain. Bitcoin developers have been working to reduce transaction malleability among standard transaction types, but a complete fix is still only in the planning stages. At present, new transactions should not depend on -previous transactions which have not been added to the block chain yet, +previous transactions which have not been added to the blockchain yet, especially if large amounts of satoshis are at stake. Transaction malleability also affects payment tracking. Bitcoin Core's diff --git a/_includes/devdoc/guide_wallets.md b/_includes/devdoc/guide_wallets.md index 6518fd1a20..2934d79df1 100644 --- a/_includes/devdoc/guide_wallets.md +++ b/_includes/devdoc/guide_wallets.md @@ -33,7 +33,7 @@ program distributing public keys in order to receive satoshis and another program signing transactions spending those satoshis. Wallet programs also need to interact with the peer-to-peer network to -get information from the block chain and to broadcast new transactions. +get information from the blockchain and to broadcast new transactions. However, the programs which distribute public keys or sign transactions don't need to interact with the peer-to-peer network themselves. @@ -366,7 +366,7 @@ keys are described in official secp256k1 documentation and supported by default in the widely-used OpenSSL library. Because they're easy to use, and because they reduce almost by half -the block chain space used to store public keys for every spent output, +the blockchain space used to store public keys for every spent output, compressed public keys are the default in Bitcoin Core and are the recommended default for all Bitcoin software. diff --git a/_includes/devdoc/ref_block_chain.md b/_includes/devdoc/ref_block_chain.md index c1d41f37ab..30d0d7954b 100644 --- a/_includes/devdoc/ref_block_chain.md +++ b/_includes/devdoc/ref_block_chain.md @@ -4,7 +4,7 @@ http://opensource.org/licenses/MIT. {% endcomment %} {% assign filename="_includes/devdoc/ref_block_chain.md" %} -## Block Chain +## Blockchain {% include helpers/subhead-links.md %} The following subsections briefly document core block details. @@ -102,7 +102,7 @@ consensus rules: this block (assuming the spend is otherwise valid). However, the TXID corresponding to the output must be placed at some point before the TXID corresponding to the input. This ensures that any program parsing - block chain transactions linearly will encounter each output before it + blockchain transactions linearly will encounter each output before it is used as an input. If a block only has a coinbase transaction, the coinbase TXID is used as @@ -144,7 +144,7 @@ order when it's placed in the block header. The target threshold is a 256-bit unsigned integer which a header hash must be equal to or below in order for that header to be a valid part of -the block chain. +the blockchain. However, the header field *nBits* provides only 32 bits of space, so the target number uses a less precise format called "compact" which works like a base-256 version of scientific notation: diff --git a/_includes/devdoc/ref_p2p_networking.md b/_includes/devdoc/ref_p2p_networking.md index d8f04cb17e..f4e1e5dbef 100644 --- a/_includes/devdoc/ref_p2p_networking.md +++ b/_includes/devdoc/ref_p2p_networking.md @@ -172,12 +172,12 @@ different reasons: {% autocrossref %} The `getblocks` message requests an `inv` message that provides block -header hashes starting from a particular point in the block chain. It +header hashes starting from a particular point in the blockchain. It allows a peer which has been disconnected or started for the first time to get the data it needs to request the blocks it hasn't seen. Peers which have been disconnected may have stale blocks in their -locally-stored block chain, so the `getblocks` message allows the +locally-stored blockchain, so the `getblocks` message allows the requesting peer to provide the receiving peer with multiple header hashes at various heights on their local chain. This allows the receiving peer to find, within that list, the last header hash they had @@ -185,7 +185,7 @@ in common and reply with all subsequent header hashes. Note: the receiving peer itself may respond with an `inv` message containing header hashes of stale blocks. It is up to the requesting -peer to poll all of its peers to find the best block chain. +peer to poll all of its peers to find the best blockchain. If the receiving peer does not find a common header hash within the list, it will assume the last common block was the genesis block (block @@ -250,7 +250,7 @@ identical to the `inv` message; only the message header differs. *Added in protocol version 31800.* The `getheaders` message requests a `headers` message that provides block headers -starting from a particular point in the block chain. It allows a +starting from a particular point in the blockchain. It allows a peer which has been disconnected or started for the first time to get the headers it hasn’t seen yet. @@ -512,7 +512,7 @@ following checks (order doesn't matter): * Fail if the block header is invalid. Remember to ensure that the hash of the header is less than or equal to the target threshold encoded by the nBits header field. Your program should also, of course, attempt - to ensure the header belongs to the best block chain and that the user + to ensure the header belongs to the best blockchain and that the user knows how many confirmations this block has. For a detailed example of parsing a `merkleblock` message, please see @@ -1193,7 +1193,7 @@ ascending code number (primary) and alphabetic in reply to (secondary) --> | 0x40 | `tx` message | 32 | char[32] | The transaction will not be mined or relayed because the rejecting node considers it non-standard---a transaction type or version unknown by the server. Extra data is the rejected transaction's TXID. | 0x41 | `tx` message | 32 | char[32] | One or more output amounts are below the dust threshold. Extra data is the rejected transaction's TXID. | 0x42 | `tx` message | | char[32] | The transaction did not have a large enough fee or priority to be relayed or mined. Extra data is the rejected transaction's TXID. -| 0x43 | `block` message | 32 | char[32] | The block belongs to a block chain which is not the same block chain as provided by a compiled-in checkpoint. Extra data is the rejected block's header hash. +| 0x43 | `block` message | 32 | char[32] | The block belongs to a blockchain which is not the same blockchain as provided by a compiled-in checkpoint. Extra data is the rejected block's header hash. The annotated hexdump below shows a `reject` message. (The message header has been omitted.) @@ -1253,7 +1253,7 @@ before initializing its half of the connection by first sending a | 8 | nonce | uint64_t | A random nonce which can help a node detect a connection to itself. If the nonce is 0, the nonce field is ignored. If the nonce is anything else, a node should terminate the connection on receipt of a `version` message with a nonce it previously sent. | *Varies* | user_agent bytes | compactSize uint | Number of bytes in following user\_agent field. If 0x00, no user agent field is sent. | *Varies* | user_agent | string | *Renamed in protocol version 60000.*

User agent as defined by BIP14. Previously called subVer. -| 4 | start_height | int32_t | The height of the transmitting node's best block chain or, in the case of an SPV client, best block header chain. +| 4 | start_height | int32_t | The height of the transmitting node's best blockchain or, in the case of an SPV client, best block header chain. | 1 | relay | bool | *Added in protocol version 70001 as described by BIP37.*

Transaction relay flag. If 0x00, no `inv` messages or `tx` messages announcing new transactions should be sent to this client until it sends a `filterload` message or `filterclear` message. If 0x01, this node wants `inv` messages and `tx` messages announcing new transactions. The following service identifiers have been assigned. diff --git a/_includes/devdoc/ref_transactions.md b/_includes/devdoc/ref_transactions.md index 8018516142..254166af5d 100644 --- a/_includes/devdoc/ref_transactions.md +++ b/_includes/devdoc/ref_transactions.md @@ -211,7 +211,7 @@ Bitcoin Core and many other tools print and accept raw transactions encoded as hex. As of Bitcoin Core 0.9.3 (October 2014), all transactions use the -version 1 format described below. (Note: transactions in the block chain +version 1 format described below. (Note: transactions in the blockchain are allowed to list a higher version number to permit soft forks, but they are treated as version 1 transactions by current software.) diff --git a/_includes/helpers/summaries.md b/_includes/helpers/summaries.md index 48fca82317..60eb1fafdd 100644 --- a/_includes/helpers/summaries.md +++ b/_includes/helpers/summaries.md @@ -18,13 +18,13 @@ This file is licensed under the terms of its source texts{%endcomment%} {% assign summary_getAddedNodeInfo="returns information about the given added node, or all added nodes (except onetry nodes). Only nodes which have been manually added using the `addnode` RPC will have their information displayed." %} {% assign summary_getAddressesByAccount="returns a list of every address assigned to a particular account." %} {% assign summary_getBalance="gets the balance in decimal bitcoins across all accounts or for a particular account." %} -{% assign summary_getBestBlockHash="returns the header hash of the most recent block on the best block chain." %} +{% assign summary_getBestBlockHash="returns the header hash of the most recent block on the best blockchain." %} {% assign summary_getBlock="gets a block with a particular header hash from the local block database either as a JSON object or as a serialized block." %} -{% assign summary_getBlockChainInfo="provides information about the current state of the block chain." %} -{% assign summary_getBlockCount="returns the number of blocks in the local best block chain." %} -{% assign summary_getBlockHash="returns the header hash of a block at the given height in the local best block chain." %} +{% assign summary_getBlockChainInfo="provides information about the current state of the blockchain." %} +{% assign summary_getBlockCount="returns the number of blocks in the local best blockchain." %} +{% assign summary_getBlockHash="returns the header hash of a block at the given height in the local best blockchain." %} {% assign summary_getBlockTemplate="gets a block template or proposal for use with mining software." %} -{% assign summary_getChainTips="returns information about the highest-height block (tip) of each local block chain." %} +{% assign summary_getChainTips="returns information about the highest-height block (tip) of each local blockchain." %} {% assign summary_getConnectionCount="returns the number of connections to other nodes." %} {% assign summary_getDifficultly="returns the proof-of-work difficulty as a multiple of the minimum difficulty." %} {% assign summary_getGenerate="returns true if the node is set to generate blocks using its CPU." %} @@ -52,7 +52,7 @@ This file is licensed under the terms of its source texts{%endcomment%} {% assign summary_help="lists all available public RPC commands, or gets help for the specified RPC. Commands which are unavailable will not be listed, such as wallet RPCs if wallet support is disabled." %} {% assign summary_importAddress="adds an address or pubkey script to the wallet without the associated private key, allowing you to watch for transactions affecting that address or pubkey script without being able to spend any of its outputs." %} {% assign summary_importPrivKey="adds a private key to your wallet. The key should be formatted in the wallet import format created by the `dumpprivkey` RPC." %} -{% assign summary_importWallet="imports private keys from a file in wallet dump file format (see the `dumpwallet` RPC). These keys will be added to the keys currently in the wallet. This call may need to rescan all or parts of the block chain for transactions affecting the newly-added keys, which may take several minutes." %} +{% assign summary_importWallet="imports private keys from a file in wallet dump file format (see the `dumpwallet` RPC). These keys will be added to the keys currently in the wallet. This call may need to rescan all or parts of the blockchain for transactions affecting the newly-added keys, which may take several minutes." %} {% assign summary_keyPoolRefill="fills the cache of unused pre-generated keys (the keypool)." %} {% assign summary_listAccounts="lists accounts and their balances." %} {% assign summary_listAddressGroupings="lists groups of addresses that may have had their common ownership made public by common use as inputs in the same transaction or from being used as change from a previous transaction." %} @@ -79,11 +79,11 @@ This file is licensed under the terms of its source texts{%endcomment%} {% assign summary_signMessage="signs a message with the private key of an address." %} {% assign summary_signRawTransaction="signs a transaction in the serialized transaction format using private keys stored in the wallet or provided in the call." %} {% assign summary_stop="safely shuts down the Bitcoin Core server." %} -{% assign summary_submitBlock="accepts a block, verifies it is a valid addition to the block chain, and broadcasts it to the network. Extra parameters are ignored by Bitcoin Core but may be used by mining pools or other programs." %} +{% assign summary_submitBlock="accepts a block, verifies it is a valid addition to the blockchain, and broadcasts it to the network. Extra parameters are ignored by Bitcoin Core but may be used by mining pools or other programs." %} {% assign summary_validateAddress="returns information about the given Bitcoin address." %} -{% assign summary_verifyChain="verifies each entry in the local block chain database." %} +{% assign summary_verifyChain="verifies each entry in the local blockchain database." %} {% assign summary_verifyMessage="verifies a signed message." %} -{% assign summary_verifyTxOutProof="verifies that a proof points to one or more transactions in a block, returning the transactions the proof commits to and throwing an RPC error if the block is not in our best block chain." %} +{% assign summary_verifyTxOutProof="verifies that a proof points to one or more transactions in a block, returning the transactions the proof commits to and throwing an RPC error if the block is not in our best blockchain." %} {% assign summary_walletLock="removes the wallet encryption key from memory, locking the wallet. After calling this method, you will need to call `walletpassphrase` again before being able to call any methods which require the wallet to be unlocked." %} {% assign summary_walletPassphrase="stores the wallet decryption key in memory for the indicated number of seconds. Issuing the `walletpassphrase` command while the wallet is already unlocked will set a new unlock time that overrides the old one." %} {% assign summary_walletPassphraseChange="changes the wallet passphrase from 'old passphrase' to 'new passphrase'." %} diff --git a/_includes/helpers/vars.md b/_includes/helpers/vars.md index d6970dc370..c21819b14c 100644 --- a/_includes/helpers/vars.md +++ b/_includes/helpers/vars.md @@ -22,7 +22,7 @@ http://opensource.org/licenses/MIT. - n: "{{DEPTH}}
`category`" t: "string" p: "Required
(exactly 1)" - d: "Set to one of the following values:
• `send` if sending payment
• `receive` if this wallet received payment in a regular transaction
• `generate` if a matured and spendable coinbase
• `immature` if a coinbase that is not spendable yet
• `orphan` if a coinbase from a block that's not in the local best block chain" + d: "Set to one of the following values:
• `send` if sending payment
• `receive` if this wallet received payment in a regular transaction
• `generate` if a matured and spendable coinbase
• `immature` if a coinbase that is not spendable yet
• `orphan` if a coinbase from a block that's not in the local best blockchain" - n: "{{DEPTH}}
`amount`" t: "number (bitcoins)" @@ -56,17 +56,17 @@ http://opensource.org/licenses/MIT. - n: "{{DEPTH}}
`blockhash`" t: "string (hex)" p: "Optional
(0 or 1)" - d: "Only returned for confirmed transactions. The hash of the block on the local best block chain which includes this transaction, encoded as hex in RPC byte order" + d: "Only returned for confirmed transactions. The hash of the block on the local best blockchain which includes this transaction, encoded as hex in RPC byte order" - n: "{{DEPTH}}
`blockindex`" t: "number (int)" p: "Optional
(0 or 1)" - d: "Only returned for confirmed transactions. The block height of the block on the local best block chain which includes this transaction" + d: "Only returned for confirmed transactions. The block height of the block on the local best blockchain which includes this transaction" - n: "{{DEPTH}}
`blocktime`" t: "number (int)" p: "Optional
(0 or 1)" - d: "Only returned for confirmed transactions. The block header time (Unix epoch time) of the block on the local best block chain which includes this transaction" + d: "Only returned for confirmed transactions. The block header time (Unix epoch time) of the block on the local best blockchain which includes this transaction" - n: "{{DEPTH}}
`txid`" t: "string (hex)" @@ -91,7 +91,7 @@ http://opensource.org/licenses/MIT. - n: "{{DEPTH}}
`timerecived`" t: "number (int)" p: "Required
(exactly 1)" - d: "A Unix epoch time when the transaction was detected by the local node, or the time of the block on the local best block chain that included the transaction" + d: "A Unix epoch time when the transaction was detected by the local node, or the time of the block on the local best blockchain that included the transaction" - n: "{{DEPTH}}
`comment`" t: "string" @@ -262,4 +262,4 @@ bitcoins even if this parameter is set to `1` or higher.{% endcapture %} {% assign WARNING="![Warning icon](/img/icons/icon_warning.svg) **Warning:**" %} -{% assign reindexNote="Note: if you begin using `txindex=1` after downloading the block chain, you must rebuild your indexes by starting Bitcoin Core with the option `-reindex`. This may take several hours to complete, during which time your node will not process new blocks or transactions. This reindex only needs to be done once." %} +{% assign reindexNote="Note: if you begin using `txindex=1` after downloading the blockchain, you must rebuild your indexes by starting Bitcoin Core with the option `-reindex`. This may take several hours to complete, during which time your node will not process new blocks or transactions. This reindex only needs to be done once." %} diff --git a/_includes/references.md b/_includes/references.md index fe6a2e60f2..2a0177556e 100644 --- a/_includes/references.md +++ b/_includes/references.md @@ -243,7 +243,7 @@ http://opensource.org/licenses/MIT. [REST]: /en/developer-reference#http-rest [RPC]: /en/developer-reference#remote-procedure-calls-rpcs [RPCs]: /en/developer-reference#remote-procedure-calls-rpcs -[section block chain]: /en/developer-guide#block-chain +[section blockchain]: /en/developer-guide#block-chain [section block header]: /en/developer-reference#block-headers [section block versions]: /en/developer-reference#block-versions [section creating a bloom filter]: /en/developer-examples#creating-a-bloom-filter diff --git a/_plugins/autocrossref.rb b/_plugins/autocrossref.rb index 07e231369e..a593f0e33e 100644 --- a/_plugins/autocrossref.rb +++ b/_plugins/autocrossref.rb @@ -65,7 +65,7 @@ def render(context) ## Sort terms by reverse length, so longest matches get linked - ## first (e.g. "block chain" before "block"). Otherwise short + ## first (e.g. "blockchain" before "block"). Otherwise short ## terms would get linked first and there'd be nothing for long ## terms to link to. site['crossref'].sort_by { |k, v| -k.length }.each { |term| diff --git a/_releases/0.10.0.md b/_releases/0.10.0.md index 39be7f173f..b42e5796d7 100644 --- a/_releases/0.10.0.md +++ b/_releases/0.10.0.md @@ -100,7 +100,7 @@ the number of validated blocks. common with each peer. While synchronizing, the heights of the blocks that we have requested from peers (but haven't received yet) are also listed as 'inflight'. -- A new RPC `getchaintips` lists all known branches of the block chain, +- A new RPC `getchaintips` lists all known branches of the blockchain, including those we only have headers for. Transaction fee changes @@ -250,7 +250,7 @@ RPC documentation for those methods for more information. Compared to using `getrawtransaction`, this mechanism does not require `-txindex`, scales better, integrates better with the wallet, and is compatible -with future block chain pruning functionality. It does mean that all relevant +with future blockchain pruning functionality. It does mean that all relevant addresses need to added to the wallet before the payment, though. Consensus library diff --git a/_releases/0.10.1.md b/_releases/0.10.1.md index 493b230090..871fb98efe 100644 --- a/_releases/0.10.1.md +++ b/_releases/0.10.1.md @@ -97,7 +97,7 @@ Block (database) and transaction handling: - `1d2cdd2` Fix InvalidateBlock to add chainActive.Tip to setBlockIndexCandidates - `c91c660` fix InvalidateBlock to repopulate setBlockIndexCandidates - `002c8a2` fix possible block db breakage during re-index -- `a1f425b` Add (optional) consistency check for the block chain data structures +- `a1f425b` Add (optional) consistency check for the blockchain data structures - `1c62e84` Keep mempool consistent during block-reorgs - `57d1f46` Fix CheckBlockIndex for reindex - `bac6fca` Set nSequenceId when a block is fully linked diff --git a/_releases/0.11.0.md b/_releases/0.11.0.md index b9f5462526..fea7845b6b 100644 --- a/_releases/0.11.0.md +++ b/_releases/0.11.0.md @@ -275,7 +275,7 @@ git merge commit are mentioned. ### Configuration and command-line options - #5636 `a353ad4` Add option `-allowselfsignedrootcertificate` to allow self signed root certs (for testing payment requests) -- #5900 `3e8a1f2` Add a consistency check `-checkblockindex` for the block chain data structures +- #5900 `3e8a1f2` Add a consistency check `-checkblockindex` for the blockchain data structures - #5951 `7efc9cf` Make it possible to disable wallet transaction broadcast (using `-walletbroadcast=0`) - #5911 `b6ea3bc` privacy: Stream isolation for Tor (on by default, use `-proxyrandomize=0` to disable) - #5863 `c271304` Add autoprune functionality (`-prune=`) diff --git a/_releases/0.3.24.md b/_releases/0.3.24.md index 0701fe9d35..9c0bea7837 100644 --- a/_releases/0.3.24.md +++ b/_releases/0.3.24.md @@ -18,7 +18,7 @@ This is another bug fix release. We had hoped to have wallet encryption ready f Notable fixes in v0.3.24, and the main reasons for this release: -* Block downloads were failing or taking unreasonable amounts of time to complete, because the increased size of the block chain was bumping up against some earlier buffer-size DoS limits. +* Block downloads were failing or taking unreasonable amounts of time to complete, because the increased size of the blockchain was bumping up against some earlier buffer-size DoS limits. * Fix crash caused by loss/lack of network connection. Notable changes in v0.3.24: diff --git a/_releases/0.5.0.md b/_releases/0.5.0.md index c9a13d9228..ca0bfc6aed 100644 --- a/_releases/0.5.0.md +++ b/_releases/0.5.0.md @@ -81,7 +81,7 @@ MAJOR GUI CHANGES * "Splash" graphics at startup that show address/wallet/blockchain loading progress. -* "Synchronizing with network" progress bar to show block-chain download +* "Synchronizing with network" progress bar to show blockchain download progress. * Icons at the bottom of the window that show how well connected you are diff --git a/_releases/0.5.3.md b/_releases/0.5.3.md index 0e3e498848..1eade5503b 100644 --- a/_releases/0.5.3.md +++ b/_releases/0.5.3.md @@ -22,7 +22,7 @@ PROTOCOL UPDATES ---------------- * BIP 30: Introduce a new network rule: "a block is not valid if it contains -a transaction whose hash already exists in the block chain, unless all that +a transaction whose hash already exists in the blockchain, unless all that transaction's outputs were already spent before said block" beginning on March 15, 2012, 00:00 UTC. diff --git a/_releases/0.6.3.md b/_releases/0.6.3.md index 666b1c87bd..b808002582 100644 --- a/_releases/0.6.3.md +++ b/_releases/0.6.3.md @@ -26,7 +26,7 @@ speed up processing of new block messages and make propagating blocks across the network faster. Fixed an obscure bug that could cause the bitcoin process to get -stuck on an invalid block-chain, if the invalid chain was +stuck on an invalid blockchain, if the invalid chain was hundreds of blocks long. Bitcoin-Qt no longer automatically selects the first address diff --git a/_releases/0.8.0.md b/_releases/0.8.0.md index d8c80dbe2a..085e24d512 100644 --- a/_releases/0.8.0.md +++ b/_releases/0.8.0.md @@ -36,7 +36,7 @@ Incompatible Changes This release no longer maintains a full index of historical transaction ids by default, so looking up an arbitrary transaction using the getrawtransaction RPC call will not work. If you need that functionality, you must run once -with -txindex=1 -reindex=1 to rebuild block-chain indices (see below for more +with -txindex=1 -reindex=1 to rebuild blockchain indices (see below for more details). Improvements diff --git a/_releases/0.8.1.md b/_releases/0.8.1.md index ca6cd3dce7..731ac806d1 100644 --- a/_releases/0.8.1.md +++ b/_releases/0.8.1.md @@ -54,7 +54,7 @@ Incompatible Changes This release no longer maintains a full index of historical transaction ids by default, so looking up an arbitrary transaction using the getrawtransaction RPC call will not work. If you need that functionality, you must run once -with -txindex=1 -reindex=1 to rebuild block-chain indices (see below for more +with -txindex=1 -reindex=1 to rebuild blockchain indices (see below for more details). Improvements diff --git a/_releases/0.8.6.md b/_releases/0.8.6.md index 5ce19ddd25..2b2089d86f 100644 --- a/_releases/0.8.6.md +++ b/_releases/0.8.6.md @@ -44,7 +44,7 @@ your machine. - Lower maximum size for free transaction creation (see ) -- OSX block chain database corruption fixes +- OSX blockchain database corruption fixes - Update leveldb to 1.13 - Use fcntl with `F_FULLSYNC` instead of fsync on OSX - Use native Darwin memory barriers diff --git a/_releases/0.9.0.md b/_releases/0.9.0.md index 86a1d26b71..a5e6602c4a 100644 --- a/_releases/0.9.0.md +++ b/_releases/0.9.0.md @@ -78,7 +78,7 @@ To reduce confusion between Bitcoin-the-network and Bitcoin-the-software we have renamed the reference client to Bitcoin Core. -OP_RETURN and data in the block chain +OP_RETURN and data in the blockchain ------------------------------------- On OP_RETURN: There was been some confusion and misunderstanding in the community, regarding the OP_RETURN feature in 0.9 and data in the @@ -217,7 +217,7 @@ Command-line options: - Remove `-logtodebugger` - Allow `-noserver` with bitcoind -Block-chain handling and storage: +Blockchain handling and storage: - Update leveldb to 1.15 - Check for correct genesis (prevent cases where a datadir from the wrong diff --git a/_releases/0.9.2.1.md b/_releases/0.9.2.1.md index 867b706139..0c39c861b4 100644 --- a/_releases/0.9.2.1.md +++ b/_releases/0.9.2.1.md @@ -92,7 +92,7 @@ Command-line options: - Fix `-printblocktree` output - Show error message if ReadConfigFile fails -Block-chain handling and storage: +Blockchain handling and storage: - Fix for GetBlockValue() after block 13,440,000 (BIP42) - Upgrade leveldb to 1.17 diff --git a/_releases/0.9.2.md b/_releases/0.9.2.md index 1d47879771..d02bef332b 100644 --- a/_releases/0.9.2.md +++ b/_releases/0.9.2.md @@ -92,7 +92,7 @@ Command-line options: - Fix `-printblocktree` output - Show error message if ReadConfigFile fails -Block-chain handling and storage: +Blockchain handling and storage: - Fix for GetBlockValue() after block 13,440,000 (BIP42) - Upgrade leveldb to 1.17 diff --git a/_translations/ar.yml b/_translations/ar.yml index 13c6a9ac47..3cb1871b56 100644 --- a/_translations/ar.yml +++ b/_translations/ar.yml @@ -253,7 +253,7 @@ ar: whocontrolstxt1: "لا أحد يملك شبكة البت كوين تماماً كما لا يوجد أحد يمتلك التكنولوجيا المحركة للبريد الإلكتروني. البت كوين يتم التحكم بها من قبل جميع مستخدمي البت كوين من جميع أنحاء العالم. بينما يقوم المطورين بتحسين البرنامج، لا يمكنهم فرض تغيير قي بروتوكول البت كوين لإن جميع المستخدمين لديهم مطلق الحرية لإختيار أي برنامج وإصدار يمكنهم استخدامه. من أجل البقاء على توافق مع بعضهم البعض، يحتاج جميع المستخدمين لإستخدام برامج تتماشى مع نفس القواعد. البت كوين يمكن أن تعمل بشكل جيد فقط عندما يكون هناك إجماع وتكامل بين جميع المستخدمين. ولهذا، جميع المستخدمين والمطورين لديهم القدرة والحافز على تبني وحماية هذا الإجماع." howitworks: "كيف يعمل البت كوين؟" howitworkstxt1: "من وجهة نظر المستخدم، فالبت كوين لا شئ أكثر من كونه برنامج جوال أو برنامج كمبيوتر يقوم بتوفير محفظة بت كوين شخصية ويسمح للمستخدم بإرسال وإستقبال عملات البت كوين بإستخدامه. هكذا تعمل البت كوين لأغلب المستخدمين." - howitworkstxt2: "خلف الستار، تتشارك شبكة البت كوين جسر عام يسمى الـ \"block chain\" أو سلسلة البلوكات. الجسر يحتوي على كل معاملة تم إرسالها يوماً ما، مما يسمح للكمبيوتر الخاص بأي مستخدم من التأكد من صلاحية كل معاملة. صحة كل معاملة محمية بواسطة توقيع إلكتروني يتوافق مع العنوان الراسل، مما يسمح لجميع المستخدمين بالتحكم الكامل في إرسال عملات البت كوين من خلال محافظ البت كوين الخاصة بهم. بالإضافة لذلك، يمكن لأي أحد إتمام المعاملات بإستخدام قوة الحوسبة الخاصة بإجهزة متخصصة والحصول على جوائز بالبت كوين مقابل خدماتهم. وهذا ما يسمى بالـ \"mining\" أو التنقيب. لتعلم المزيد حول البت كوين، يمكنك الإطلاع على كيفية عمل البت كوين و ورقة عمل البت كوين الأساسية." + howitworkstxt2: "خلف الستار، تتشارك شبكة البت كوين جسر عام يسمى الـ \"blockchain\" أو سلسلة البلوكات. الجسر يحتوي على كل معاملة تم إرسالها يوماً ما، مما يسمح للكمبيوتر الخاص بأي مستخدم من التأكد من صلاحية كل معاملة. صحة كل معاملة محمية بواسطة توقيع إلكتروني يتوافق مع العنوان الراسل، مما يسمح لجميع المستخدمين بالتحكم الكامل في إرسال عملات البت كوين من خلال محافظ البت كوين الخاصة بهم. بالإضافة لذلك، يمكن لأي أحد إتمام المعاملات بإستخدام قوة الحوسبة الخاصة بإجهزة متخصصة والحصول على جوائز بالبت كوين مقابل خدماتهم. وهذا ما يسمى بالـ \"mining\" أو التنقيب. لتعلم المزيد حول البت كوين، يمكنك الإطلاع على كيفية عمل البت كوين و ورقة عمل البت كوين الأساسية." used: "هل البت كوين مستعملة حقاً من قبل الناس؟" usedtxt1: "نعم، هنالك عدد متزايد من الأعمال والأشخاص الذين يقومون بإستخدام البت كوين. هذا يتضمن أعمال كثيرة ومتنوعة كالمطاعم، العقارات، المؤسسات القانونية، وخدمات إنترنت شهيرة كـ Namecheap، WordPress، Reddit و Flattr. بينما لا يزال البت كوين ظاهرة جديدة نسبياً، فهو ينمو بسرعة. في نهاية أغسطس 2013، إجمالي قيمة المتوفر من عملات البت كوين للتداول تجاوز 1.5 مليار دولار مع ما قيمته ملايين من عملات البت كوين يتم تداوله يومياً." acquire: "كيف يحصل الفرد على عملات البت كوين؟" @@ -412,7 +412,7 @@ ar: basics: "الأساسيات للمستخدم الجديد" basicstxt1: "كمستخدم جديد، يمكنك البدء بإستخدام البت كوين بدون معرفة المعلومات التقنية. بمجرد أن قمت بتثبيت محفظة بت كوين على جهاز الكمبيوتر أو الهاتف الجوال الخاص بك، ستقوم بإنشاء أول عنوان بت كوين خاص بك ويمكنك إنشاء المزيد عند الحاجة. يمكنك الكشف عن عناوينك لأصدقائك حتى يمكنهم أن يدفعوا لك أو العكس. في الواقع، إن هذا مشابه جداً لكيفية عمل البريد الإلكتروني، الفارق الوحيد أن عناوين البت كوين يجب إستخدامها مرة واحدة فقط." balances: "الأرصدة - سلسلة البلوكات" - balancestxt: "سلسلة البلوكات أو كما تسمى بالإنجليزية \"block chain\" هي عبارة عن جسر مٌشارك مع العامة تعتمد عليه شبكة البت كوين كلها. جميع المعاملات المؤكدة مضمنة داخل سلسلة البلوكات. وبهذه الطريقة، محافظ البت كوين يمكنها حساب رصيدها الممكن التحكم به والتي يٌسمح لحامليها بالتصرف بها وإنفاقها وكذلك المعاملات الجديدة يمكن تأكيدها بنفس الطريقة. سلامة سلسلة البلوكات والترتيب الزمني الصحيح لها خاضع لـ التشفير حرفياً." + balancestxt: "سلسلة البلوكات أو كما تسمى بالإنجليزية \"blockchain\" هي عبارة عن جسر مٌشارك مع العامة تعتمد عليه شبكة البت كوين كلها. جميع المعاملات المؤكدة مضمنة داخل سلسلة البلوكات. وبهذه الطريقة، محافظ البت كوين يمكنها حساب رصيدها الممكن التحكم به والتي يٌسمح لحامليها بالتصرف بها وإنفاقها وكذلك المعاملات الجديدة يمكن تأكيدها بنفس الطريقة. سلامة سلسلة البلوكات والترتيب الزمني الصحيح لها خاضع لـ التشفير حرفياً." transactions: "المعاملات - المفاتيح الخاصة" transactionstxt: "المعاملة أو كما تسمى بالإنجليزية \"transaction\" هي تحويل قيمة ما بين محافظ البت كوين يتم تضمينها في سلسلة البلوكات. محافظ البت كوين تحتفظ بجزء سري من البيانات يسمى المفتاح الخاص أو الأساس، والذي يتم إستخدامه لتوقيع المعاملات، توفير البرهان الرياضي على أن المعاملة نفذت من مالك المحفظة. التوقيع أيضاً يحفظ المعاملة من أن يتم تعديلها أو التلاعب بها من قبل أي أحد بعد إصدارها. جميع المعاملات يتم نشرها وتوزيعها بين المستخدمين وغالباً ما يبدأ تأكيدها بواسطة الشبكة في الـ 10 دقائق التالية، من خلال عملية تسمى التنقيب." processing: "معالجة - التنقيب" @@ -580,7 +580,7 @@ ar: bitcoin: "البت كوين" bitcointxt: "Bitcoin - يتم إستخدامها بحروف كبيرة لتوصيف مبدأ البت كوين نفسه، أو شبكة البت كوين نفسها. على سبيل المثال: \"كنت أتعلم اليوم عن بروتوكول الـ Bitcoin\".
bitcoin - بدون حروف كبيرة، يتم إستخدامها لتوصيف البت كوين كوحدة محاسبية. على سبيل المثال: \"قمت اليوم بإرسال 10 bitcoins\" وغالباً ما يتم إختصارها أيضاً لـ BTC أو XBT" blockchain: "سلسلة البلوكات" - blockchaintxt: "سلسلة البلوكات أو كما تسمى بالإنجليزية \"block chain\" هي سجل عام لجميع معاملات البت كوين مرتبة زمنياً. سلسلة البلوكات يتم مشاركتها بين جميع مستخدمي البت كوين. يتم إستخدام السلسلة من أجل التأكد من إستمرارية معاملات البت كوين ولكي تمنع الإنفاق المزدوج." + blockchaintxt: "سلسلة البلوكات أو كما تسمى بالإنجليزية \"blockchain\" هي سجل عام لجميع معاملات البت كوين مرتبة زمنياً. سلسلة البلوكات يتم مشاركتها بين جميع مستخدمي البت كوين. يتم إستخدام السلسلة من أجل التأكد من إستمرارية معاملات البت كوين ولكي تمنع الإنفاق المزدوج." block: "البلوك" blocktxt: "البلوك أو المجموعة أو كما يسمى بالإنجليزية \"block\" هو سجل في سلسلة البلوكات يحتوي على العديد من المعاملات قيد التنفيذ يقوم بتأكيدها. في المتوسط، كل 10 دقائق تقريباً، بلوك جديد يحتوي مجموعة من المعاملات يتم إضافته إلى سلسلة البلوكات من خلال التنقيب." btc: "BTC" @@ -673,7 +673,7 @@ ar: vocabulary: address: address bitcoin: bitcoin - blockchain: block-chain + blockchain: blockchain block: block btc: btc confirmation: confirmation diff --git a/_translations/bg.yml b/_translations/bg.yml index b4989a5a2c..feb046d088 100644 --- a/_translations/bg.yml +++ b/_translations/bg.yml @@ -230,7 +230,7 @@ bg: sourcecode: "Вземи отворения код" versionhistory: "Покажи история на версиите" notelicense: "Bitcoin Core е свободен софтуерен проект, създаден от група хора, който е разпространен под лиценза на Масачузетския технологичен институт." - notesync: "Първоначалната синхронизация на Bitcoin Core може да отнеме много време. Проверете дали имате достатъчно дисково пространство и достатъчно бърза интернет връзка за целия block chain (над 20GB). Ако знаете как да изтеглите торент файл, може да ускорите процеса като съхраните bootstrap.dat (по-старо копие на block chain) в data директорията на Bitcoin Core преди стартирането на софтуера." + notesync: "Първоначалната синхронизация на Bitcoin Core може да отнеме много време. Проверете дали имате достатъчно дисково пространство и достатъчно бърза интернет връзка за целия blockchain (над 20GB). Ако знаете как да изтеглите торент файл, може да ускорите процеса като съхраните bootstrap.dat (по-старо копие на blockchain) в data директорията на Bitcoin Core преди стартирането на софтуера." patient: "Трябва да бъдете търпеливи" events: title: "Конференции и събития - Биткойн" @@ -582,7 +582,7 @@ bg: bittxt: "Милибиткойнът е обща единица, използвана за обозначаване на под-единица на биткойн - 1 000 000 бита се равнява на 1 биткойн (BTC или B⃦). Тази единица е обикновено по-удобна за ценообразуване на стоки и услуги." bitcoin: "Биткойн" bitcointxt: "Биткойн, написано с главна буква, се използва, когато се говори за концепцията Биткойн или за цялата мрежа, като например \"Аз четох за Биткойн протокола днес.\"
биткойн с малка буква се използва, за да опише биткойните като разчетна единица, като например \"Изпратих 10 биткойна днес.\" Често използвано в практиката съкращение за биткойн е BTC или XBT." - blockchain: "Block Chain" + blockchain: "Blockchain" blockchaintxt: "Блок-веригата представлява публичен регистър на всички Биткойн транзакции в хронологичен ред. Тя се споделя между всички Биткойн потребители. Използва се, за да потвърди биткойн транзакциите и да предотврати дублиране на разходите (използването на биткойни, които са били изхарчени вече в предишна транзакция)." block: "Block" blocktxt: "Блокът е запис в блок-веригата, който съдържа и потвърждава много, чакащи транзакции. Приблизително на всеки 10 минути, нов блок, съдържащ транзакции, се прилага към блок-веригата чрез добив." @@ -680,7 +680,7 @@ bg: address: address bit: bit bitcoin: bitcoin - blockchain: block-chain + blockchain: blockchain block: block btc: btc confirmation: confirmation diff --git a/_translations/da.yml b/_translations/da.yml index 0ae099c6a2..b4078e9b0d 100644 --- a/_translations/da.yml +++ b/_translations/da.yml @@ -621,7 +621,7 @@ da: bittxt: "Bit er en udbredt enhed, der bruges til at angive en underenhed af en bitcoin – 1.000.000 bit er lig med 1 bitcoin (BTC eller B⃦). Denne enhed er for det meste mere belejlig til angivelse af drikkepenge og pricer på varer og services." bitcoin: "Bitcoin" bitcointxt: "Bitcoin – skrevet med stort begyndelsesbogstav – bruges når begrebet Bitcoin eller selve netværket beskrives. Fx: \"Jeg lærte noget om Bitcoin-protokollen i dag.\"
bitcoin – skrevet med småt – bruges til at beskrive bitcoin som enhed eller konto. Fx: \"Jeg sendte to bitcoin i dag.\" Det forkortes ofte BTC eller XBT." - blockchain: "Blokkæde (block chain)" + blockchain: "Blokkæde (blockchain)" blockchaintxt: "Blokkæden er en offentlig optegnelse over Bitcoin-transaktioner i kronologisk rækkefølge. Blokkæden deles mellem alle Bitcoin-brugere. Den bruges til at verificere bestandigheden af Bitcoin-transaktioner og til at forhindre dobbeltspendering." block: "Blok (block)" blocktxt: "En blok er en fortegnelse i blokkæden, som indeholder og bekræfter mange ventende transaktioner. Omtrent hvert 10. minut gennemsnitligt bliver en ny blok, der indeholder transaktioner, føjet til blokkæden ved hjælp af mining." diff --git a/_translations/el.yml b/_translations/el.yml index 5a7038c1e6..ce124d6298 100644 --- a/_translations/el.yml +++ b/_translations/el.yml @@ -259,7 +259,7 @@ el: whocontrolstxt1: "Κανείς δεν είναι ιδιοκτήτης του δικτύου Bitcoin όπως ακριβώς και κανένας δεν είναι ιδιοκτήτης της τεχνολογίας πίσω από το email. Το Bitcoin ελέγχεται από όλους τους χρήστες Bitcoin σε όλο τον κόσμο. Ενώ οι προγραμματιστές βελτιώνουν το λογισμικό, δεν μπορούν να εξαναγκάσουν καμία αλλαγή στο πρωτόκολλο Bitcoin, διότι όλοι οι χρήστες είναι ελεύθεροι να επιλέξουν την έκδοση του λογισμικού που χρησιμοποιούν. Για να διατηρηθεί η συμβατότητα, όλοι οι χρήστες πρέπει να χρησιμοποιούν το λογισμικό που υπακούει στους ίδιους κανόνες. Το Bitcoin μπορεί να λειτουργήσει σωστά μόνο με την πλήρη συναίνεση μεταξύ όλων των χρηστών. Ως εκ τούτου, όλοι οι χρήστες και οι προγραμματιστές έχουν ισχυρό κίνητρο να προστατεύουν αυτήν την γενική συναίνεση." howitworks: "Πώς λειτουργεί το Bitcoin;" howitworkstxt1: "Από τη μεριά του χρήστη, το Bitcoin δεν είναι τίποτα περισσότερο από μια εφαρμογή κινητού τηλεφώνου ή υπολογιστή η οποία παρέχει ένα προσωπικό πορτοφόλι Bitcoin και επιτρέπει στο χρήστη να στέλνει και να λαμβάνει bitcoins μέσω αυτού . Έτσι λειτουργεί το Bitcoin για τους περισσότερους χρήστες." - howitworkstxt2: "Στο παρασκήνιο, το δίκτυο Bitcoin μοιράζεται ένα δημόσιο λογιστικό βιβλίο (ledger) που ονομάζεται \"block chain\" (αλυσίδα των μπλοκ). Αυτό το βιβλίο περιέχει κάθε συναλλαγή που έχει ποτέ επεξεργαστεί από το δίκτυο, επιτρέποντας στον υπολογιστή του χρήστη να εξακριβώνει την εγκυρότητα της κάθε συναλλαγής. Η αυθεντικότητα της κάθε συναλλαγής προστατεύεται από ψηφιακές υπογραφές που αντιστοιχούν στις διευθύνσεις αποστολής, επιτρέποντας σε όλους τους χρήστες να έχουν πλήρη έλεγχο κατά την αποστολή bitcoins από τις δικές τους διευθύνσεις Bitcoin. Επιπλέον, ο καθένας μπορεί να επεξεργαστεί συναλλαγές που χρησιμοποιούν την υπολογιστική ισχύ εξειδικευμένου υλισμικού (hardware) και να κερδίσει μια ανταμοιβή σε bitcoins για την υπηρεσία αυτή. Αυτό συχνά ονομάζεται εξόρυξη (mining). Για να μάθετε περισσότερα για το Bitcoin, μπορείτε να συμβουλευτείτε την ειδική ιστοσελίδα και το πρωτότυπο έγγραφο." + howitworkstxt2: "Στο παρασκήνιο, το δίκτυο Bitcoin μοιράζεται ένα δημόσιο λογιστικό βιβλίο (ledger) που ονομάζεται \"blockchain\" (αλυσίδα των μπλοκ). Αυτό το βιβλίο περιέχει κάθε συναλλαγή που έχει ποτέ επεξεργαστεί από το δίκτυο, επιτρέποντας στον υπολογιστή του χρήστη να εξακριβώνει την εγκυρότητα της κάθε συναλλαγής. Η αυθεντικότητα της κάθε συναλλαγής προστατεύεται από ψηφιακές υπογραφές που αντιστοιχούν στις διευθύνσεις αποστολής, επιτρέποντας σε όλους τους χρήστες να έχουν πλήρη έλεγχο κατά την αποστολή bitcoins από τις δικές τους διευθύνσεις Bitcoin. Επιπλέον, ο καθένας μπορεί να επεξεργαστεί συναλλαγές που χρησιμοποιούν την υπολογιστική ισχύ εξειδικευμένου υλισμικού (hardware) και να κερδίσει μια ανταμοιβή σε bitcoins για την υπηρεσία αυτή. Αυτό συχνά ονομάζεται εξόρυξη (mining). Για να μάθετε περισσότερα για το Bitcoin, μπορείτε να συμβουλευτείτε την ειδική ιστοσελίδα και το πρωτότυπο έγγραφο." used: "Χρησιμοποιείται στ'αλήθεια το Bitcoin από τους ανθρώπους;" usedtxt1: "Ναι. Υπάρει ένας αυξανόμενος αριθμός επιχειρήσεων και ιδιωτών που χρησιμοποιούν το Bitcoin. Περιλαμβάνονται επιχειρήσεις όπως εστιατόρια, ξενοδοχεία, δικηγορικά γραφεία, καθώς και δημοφιλείς online υπηρεσίες όπως οι Namecheap, WordPress, Reddit και Flattr. Ενώ το Bitcoin παραμένει ένα σχετικά νέο φαινόμενο, αναπτύσσεται γρήγορα. Στο τέλος Αυγούστου του 2013, η αξία όλων των bitcoins σε κυκλοφορία ξεπέρασε το 1.5 δις δολάρια με bitcoins αξίας εκατομμύριων δολαριών να ανταλλάζονται καθημερινά." acquire: "Πώς αποκτά κάποιος bitcoins;" @@ -275,7 +275,7 @@ el: advantagesli2: "Πολύ χαμηλά τέλη - Προς το παρόν, οι πληρωμές με Bitcoin γίνονται είτε με μηδενικά είτε με εξαιρετικά χαμηλά τέλη. Οι χρήστες μπορεί να συμπεριλάβουν τέλη στις συναλλαγές τους προκειμένου να έχουν προτεραιότητα στην διεκπεραίωση, κάτι που έχει ως αποτελέσματα την γρηγορότερη επικύρωση των συναλλαγών από το δίκτυο. Επιπροσθέτως, οι επεξεργαστές για εμπόρους υπάρχουν για να τους βοηθήσουν στην επεξεργασία πληρωμών, μετατρέποντας τα bitcoins σε πιστωτικό χρήμα και καταθέτοντας τα κεφάλαια απευθείας στον τραπεζικό λογαριασμό των εμπόρων καθημερινά. Καθώς αυτές οι υπηρεσίες βασίζονται στο Bitcoin, μπορούν να προσφέρονται με πολύ χαμηλότερα τέλη σε σχέση με την PayPal ή δίκτυα πιστωτικών καρτών." advantagesli3: "Λιγότεροι κίνδυνοι για τους εμπόρους - Οι συναλλαγές με Bitcoin είναι ασφαλείς, μη αναστρέψιμες και δεν περιέχουν προσωπικές πληροφορίες ή ευαίσθητα προσωπικά δεδομένα των πελατών. Αυτό προστατεύει τους εμπόρους από ζημίες που προκαλούνται από απάτες ή δόλιους αντιλογισμούς χρέωσης (chargebacks) και δεν υπάρχει ανάγκη για συμβατότητα με PCI. Οι έμποροι μπορούν εύκολα να επεκταθούν σε νέες αγορές όπου είτε οι πιστωτικές κάρτες δεν είναι διαθέσιμες, είτε τα ποσοστά απάτης είναι απαράδεκτα υψηλά. Το αποτελέσματα σε καθαρό κέρδος είναι χαμηλότερα τέλη, μεγαλύτερες αγορές και λιγότερα διοικητικά κόστη. " advantagesli4: "Ασφάλεια και έλεγχος - Οι χρήστες του Bitcoin έχουν πλήρη έλεγχο των συναλλαγών τους. Είναι ανέφικτο για τους εμπόρους να επιβάλλουν ανεπιθύμητες ή απαρατήρητες χρεώσεις όπως μπορεί να συμβεί με άλλες μεθόδους πληρωμής. Οι πληρωμές με Bitcoin μπορούν να διεξαχθούν χωρίς να συνδέονται προσωπικές πληροφορίες με την συναλλαγή. Αυτό προσφέρει ισχυρή προστασία κατά της κλοπής ταυτότητας. Οι χρήστες του Bitcoin μπορούν επίσης να προστατέψουν τα χρήματά τους με αντίγραφα ασφαλείας και κρυπτογράφηση." - advantagesli5: "Διαφανής και ουδέτερος - Όλες οι πληροφορίες που αφορούν τον εφοδιασμό του Bitcoin με χρήματα είναι άμεσα διαθέσιμες στην αλυσίδα των μπλοκ (block chain) για τον οποιονδήποτε να τις επιβεβαιώσει και να τις χρησιμοποιήσει σε πραγματικό χρόνο. Κανένα άτομο ή οργανισμός δεν μπορεί να ελέγξει ή να πλαστογραφήσει το πρωτόκολλο του Bitcoin διότι είναι κρυπτογραφικά ασφαλές. Αυτό επιτρέπει στον πυρήνα του Bitcoin να είναι αξιόπιστος αφού είναι απόλυτα ουδέτερος, διαφανής και προβλέψιμος." + advantagesli5: "Διαφανής και ουδέτερος - Όλες οι πληροφορίες που αφορούν τον εφοδιασμό του Bitcoin με χρήματα είναι άμεσα διαθέσιμες στην αλυσίδα των μπλοκ (blockchain) για τον οποιονδήποτε να τις επιβεβαιώσει και να τις χρησιμοποιήσει σε πραγματικό χρόνο. Κανένα άτομο ή οργανισμός δεν μπορεί να ελέγξει ή να πλαστογραφήσει το πρωτόκολλο του Bitcoin διότι είναι κρυπτογραφικά ασφαλές. Αυτό επιτρέπει στον πυρήνα του Bitcoin να είναι αξιόπιστος αφού είναι απόλυτα ουδέτερος, διαφανής και προβλέψιμος." disadvantages: "Ποια είναι τα μειονεκτήματα του Bitcoin;" disadvantagesli1: "Βαθμός αποδοχής - Πολλοί άνθρωποι δεν είναι ακόμα ενήμεροι για το Bitcoin. Καθημερινά, περισσότερες επιχειρήσεις δέχονται τα bitcoins γιατί θέλουν τα πλεονεκτήματα κάνοντας χρήση του αλλά η λίστα παραμένει μικρή και ακόμα χρειάζεται να μεγαλώσει έτσι ώστε να επωφεληθούμε από τα αποτελέσματα δικτύου." disadvantagesli2: "Αστάθεια - Η συνολική αξία των bitcoins σε κυκλοφορία και ο αριθμός των επιχειρήσεων που χρησιμοποιούν το Bitcoin είναι ακόμα πολύ μικρός σε σύγκριση με αυτό που θα μπορούσε να είναι. Συνεπώς, σχετικά μικρά γεγονότα, συναλλαγές, ή επιχειρηματικές δραστηριότητες μπορούν να επηρεάσουν σημαντικά την τιμή. Θεωρητικά, η αστάθεια αυτή θα μειωθεί καθώς οι αγορές Bitcoin και η τεχνολογία ωριμάζoυν. Ποτέ στο παρελθόν δεν έχει δει ο κόσμος ένα νεοσύστατο νόμισμα, οπότε είναι πραγματικά δύσκολο (και συναρπαστικό να φανταστούμε το πώς θα εξελιχθεί." @@ -291,7 +291,7 @@ el: anonymoustxt1: "To Bitcoin είναι σχεδιασμένο ώστε να επιτρέπει στους χρήστες του να στέλνουν και να λαμβάνουν πληρωμές με ένα αποδεκτό επίπεδο προστασίας προσωπικών δεδομένων όπως επίσης και σε οποιαδήποτε άλλη μορφή χρημάτων. Ωστόσο, το Bitcoin δεν είναι ανώνυμο και δεν μπορεί να προσφέρει το ίδιο επίπεδο προστασίας προσωπικών δεδομένων όπως με τα μετρητά. Η χρήση του Bitcoin αφήνει εκτεταμένα δημόσια αρχεία. Διάφοροι μηχανισμοί υπάρχουν για να προστατέψουν τα προσωπικά δεδομένα των χρηστών και ακόμα περισσότεροι είναι υπό εξέλιξη. Ωστόσο, υπάρχει ακόμα δουλειά που πρέπει να γίνει πριν οι λειτουργίες αυτές χρησιμοποιούνται σωστά από τους περισσότερους χρήστες του Bitcoin." anonymoustxt2: "Έχουν διατυπωθεί κάποιες ανησυχίες ότι οι ιδιωτικές συναλλαγές με Bitcoin θα μπορούσαν να χρησιμοποιηθούν για παράνομους σκοπούς. Ωστόσο, αξίζει να σημειωθεί ότι το Bitcoin θα υπόκειται αναμφίβολα σε παρόμοιους κανονισμούς με αυτούς που ήδη εφαρμόζονται στα υπάρχοντα χρηματοοικονομικά συστήματα. Το Bitcoin δεν μπορεί να είναι πιο ανώνυμο από τα μετρητά και δεν είναι πιθανό να εμποδίζει τις εγκληματολογικές έρευνες από το να διεξάγονται. Επιπροσθέτως, το Bitcoin είναι σχεδιασμένο επίσης για να αποτρέπει ένα μεγάλο φάσμα οικονομικών εγκλημάτων." lost: "Τι συμβαίνει όταν τα bitcoins χαθούν;" - losttxt1: "Όταν ένας χρήστης χάσει το πορτοφόλι του, έχει ως αποτέλεσμα τα χρήματα να βγαίνουν εκτός κυκλοφορίας. Τα χαμένα bitcoins παραμένουν ακόμα στην αλυσίδα των μπλοκ (block chain) ακριβώς όπως και όλα τα άλλα bitcoins. Ωστόσο, τα χαμένα bitcoins παραμένουν ανενεργά για πάντα διότι δεν υπάρχει τρόπος για κανέναν να βρει το(α) ιδιωτικό(ά) κλειδί(ά) τα οποία θα τους επιτρέψουν να ξοδευτούν ξανά. Εξαιτίας του νόμου προσφοράς και ζήτησης, όταν υπάρχουν λιγότερα bitcoins διαθέσιμα, τα εναπομείναντα θα έχουν μεγαλύτερη ζήτηση και αυξάνεται η αξία τους για αντιστάθμισμα." + losttxt1: "Όταν ένας χρήστης χάσει το πορτοφόλι του, έχει ως αποτέλεσμα τα χρήματα να βγαίνουν εκτός κυκλοφορίας. Τα χαμένα bitcoins παραμένουν ακόμα στην αλυσίδα των μπλοκ (blockchain) ακριβώς όπως και όλα τα άλλα bitcoins. Ωστόσο, τα χαμένα bitcoins παραμένουν ανενεργά για πάντα διότι δεν υπάρχει τρόπος για κανέναν να βρει το(α) ιδιωτικό(ά) κλειδί(ά) τα οποία θα τους επιτρέψουν να ξοδευτούν ξανά. Εξαιτίας του νόμου προσφοράς και ζήτησης, όταν υπάρχουν λιγότερα bitcoins διαθέσιμα, τα εναπομείναντα θα έχουν μεγαλύτερη ζήτηση και αυξάνεται η αξία τους για αντιστάθμισμα." scale: "Μπορεί το Bitcoin να γίνει ένα σημαντικό δίκτυο πληρωμών;" scaletxt1: "Το δίκτυο Bitcoin μπορεί ήδη να επεξεργαστεί ένα πολύ υψηλότερο αριθμό συναλλαγών το δευτερόλεπτο από ότι κάνει σήμερα. Ωστόσο, δεν είναι εντελώς έτοιμο να σκαρφαλώσει στο επίπεδο των μεγαλύτερων δικτύων πιστωτικών καρτών. Εργασίες είναι σε εξέλιξη προκειμένου να αρθούν οι τωρινοί περιορισμοί και οι μελλοντικές ανάγκες είναι καλά γνωστές. Από την αρχή, κάθε πτυχή του δικτύου Bitcoin είναι σε διαρκή διαδικασία ωρίμανσης, βελτιστοποίησης και εξειδίκευσης και θα πρέπει να αναμένεται να παραμείνει έτσι για τα μερικά επόμενα χρόνια. Καθώς αυξάνεται η κίνηση, περισσότεροι χρήστες Bitcoin χρησιμοποιούν ελαφρούς πελάτες και οι πλήρεις κόμβους δικτύου μπορούν να γίνουν μια πιο εξειδικευμένη υπηρεσία. Για περισσότερες πληροφορίες, δείτε την Κλιμάκωση σελίδα Bitcoin Wiki." legal: "Νομικά" @@ -351,20 +351,20 @@ el: poweredoff: "Τι γίνεται αν λάβω ένα bitcoin όταν ο υπολογιστής μου είναι απενεργοποιημένος;" poweredofftxt1: "Αυτό λειτουργεί καλά. Τα bitcoins θα εμφανιστούν την επόμενη φορά που ξεκινάτε το πορτοφόλι σας. Τα bitcoins δεν λαμβάνονται στην πραγματικότητα από το λειτουργικό στον υπολογιστή σας, επισυνάπτονται σε ένα κοινόχρηστο λογιστικό βιβλίο (ledger) το οποίο διαμοιράζεται ανάμεσα σε όλες τις συσκευές του δικτύου. Αν σας αποσταλλούν bitcoins όταν το προγράμμα πορτοφολιού πελάτη δεν τρέχει και το ενεργοποιήσετε αργότερα, θα μεταφορτώσει τα μπλοκ (blocks) και θα έρθει στο ίδιο επίπεδο για οποιεσδήποτε συναλλαγές δεν γνώριζε ήδη και τα bitcoins εν τέλει θα εμφανιστούν σαν να είχαν μόλις ληφθεί σε πραγματικό χρόνο. Το πορτοφόλι σας χρειάζεται μόνο όταν επιθυμείτε να ξοδέψετε bitcoins." sync: "Τι σημαίνει \"συγχρονισμός\" και γιατί αργεί τόσο;" - synctxt1: "Μεγάλος χρόνος συγχρονισμού απαιτείται μόνο με πελάτες πλήρους κόμβου (full node) όπως το Bitcoin Core. Από τεχνικής άποψης, συγχρονισμός είναι η διαδικασία της μεταφόρτωσης και επαλήθευσης όλων των προηγούμενων συναλλαγών Bitcoin στο δίκτυο. Για να υπολογίσουν κάποιοι πελάτες Bitcoin το διαθέσιμο υπόλοιπο από το Bitcoin πορτοφόλι σας και να κάνουν νέες συναλλαγές, χρειάζεται να είναι ενήμεροι για όλες τις προηγούμενες συναλλαγές. Αυτό το βήμα μπορεί να είναι εντατικής χρήσης πόρων και απαιτεί επάρκεια σε εύρος ζώνης (bandwidth) και χώρο αποθήκευσης για να χωράει το πλήρες μέγεθος της αλυσίδας των μπλοκ (block chain). Για να παραμείνει το Bitcoin ασφαλές, αρκετοί άνθρωποι θα πρέπει να συνεχίσουν να χρησιμοποιούν πελάτες πλήρους κόμβου (full node) διότι εκτελούν το έργο της επικύρωσης και μετάδοσης των συναλλαγών." + synctxt1: "Μεγάλος χρόνος συγχρονισμού απαιτείται μόνο με πελάτες πλήρους κόμβου (full node) όπως το Bitcoin Core. Από τεχνικής άποψης, συγχρονισμός είναι η διαδικασία της μεταφόρτωσης και επαλήθευσης όλων των προηγούμενων συναλλαγών Bitcoin στο δίκτυο. Για να υπολογίσουν κάποιοι πελάτες Bitcoin το διαθέσιμο υπόλοιπο από το Bitcoin πορτοφόλι σας και να κάνουν νέες συναλλαγές, χρειάζεται να είναι ενήμεροι για όλες τις προηγούμενες συναλλαγές. Αυτό το βήμα μπορεί να είναι εντατικής χρήσης πόρων και απαιτεί επάρκεια σε εύρος ζώνης (bandwidth) και χώρο αποθήκευσης για να χωράει το πλήρες μέγεθος της αλυσίδας των μπλοκ (blockchain). Για να παραμείνει το Bitcoin ασφαλές, αρκετοί άνθρωποι θα πρέπει να συνεχίσουν να χρησιμοποιούν πελάτες πλήρους κόμβου (full node) διότι εκτελούν το έργο της επικύρωσης και μετάδοσης των συναλλαγών." mining: "Εξόρυξη" whatismining: "Τι είναι η εξόρυξη του Bitcoin;" whatisminingtxt1: "Εξόρυξη (mining) είναι η διαδικασία δαπάνης υπολογιστικής ισχύος για να επεξεργαστούν οι συναλλαγές, να ασφαλιστεί το δίκτυο και για να παραμείνουν όλοι στο σύστημα συγχρονισμένοι μαζί. Μπορεί να εκληφθεί ως το κέντρο δεδομένων του Bitcoin με την εξαίρεση ότι έχει σχεδιαστεί για να είναι πλήρως αποκεντρωμένο με εξορύκτες που λειτουργούν σε όλες τις χώρες και κανένα άτομο δεν ασκεί έλεγχο πάνω στο δίκτυο. Αυτή η μέθοδος αναφέρεται ως εξόρυξη (mining) αναλογικά όπως η εξόρυξη χρυσού διότι είναι επίσης ένας προσωρινός μηχανισμός που χρησιμοποιείται στην έκδοση νέων bitcoins. Ωστόσο, σε αντίθεση με την εξόρυξη χρυσού, η εξόρυξη Bitcoin παρέχει μια ανταμοιβή σε αντάλλαγμα των χρήσιμων υπηρεσιών που απαιτούνται για να λειτουργήσει ένα ασφαλές δίκτυο πληρωμών. Η εξόρυξη θα απαιτείται ακόμα και μετά την έκδοση του τελευταίου bitcoin. " howminingworks: "Πώς δουλεύει η εξόρυξη του Bitcoin;" howminingworkstxt1: "Ο καθένας μπορεί να γίνει εξορύκτης Bitcoin (miner) τρέχοντας το λογισμικό με εξειδικευμένο υλισμικό (hardware). Το λογισμικό εξόρυξης αφουγκράζεται τις μεταδόσεις συναλλαγών μέσω του δικτύου μεταξύ ομότιμων (peer-to-peer) και εκτελεί τις κατάλληλες εργασίες για να επεξεργαστεί και να επιβεβαιώσει τις συναλλαγές αυτές. Οι εξορύκτες Bitcoin εκτελούν αυτή την εργασία διότι μπορούν να κερδίσουν τέλη συναλλαγής που πληρώνονται από τους χρήστες για ταχύτερη επεξεργασία μιας συναλλαγής και πρόσφατα δημιουργηθέντα bitcoins που έλαβαν σάρκα και οστά σύμφωνα με μια σύνθετη φόρμουλα. " - howminingworkstxt2: "Για να επιβεβαιωθούν οι νέες συναλλαγές, αυτές πρέπει να συμπεριληφθούν σε ένα μπλοκ (block) μαζί με μια μαθηματική απόδειξη εργασίας. Τέτοιες αποδείξεις είναι πολύ δύσκολο να παραχθούν διότι δεν υπάρχει κανένας τρόπος δημιουργίας τους παρά μόνο δοκιμάζοντας δισεκατομμύρια υπολογισμούς το δευτερόλεπτο. Αυτό απαιτεί οι εξορύκτες να εκτελούν αυτούς τους υπολογισμούς πριν τα μπλοκ (blocks) γίνουν αποδεκτά από το δίκτυο και πριν αυτοί λάβουν μια αμοιβή. Καθώς περισσότεροι άνθρωποι ξεκινάνε εξόρυξη, η δυσκολία εξεύρεσης έγκυρων μπλοκ αυξάνεται αυτόματα από το δίκτυο για να διασφαλίσει ότι ο μέσος χρόνος για να βρεθεί ένα μπλοκ παραμένει ίσος με 10 λεπτά. Κατά συνέπεια, η εξόρυξη είναι μια πολύ ανταγωνιστική επιχείρηση όπου κανένας ιδιώτης εξορύκτης δεν μπορεί να ελέγξει τι περιλαμβάνεται εντός της αλυσίδας των μπλοκ (block chain)." - howminingworkstxt3: "Η απόδειξη εργασίας είναι επίσης σχεδιασμένη να εξαρτάται από το προηγούμενο μπλοκ (block) για να επιβάλλει μια χρονολογική σειρά στην αλυσίδα των μπλοκ (block chain). Αυτό καθιστά εκθετικά δύσκολη την αντιστροφή των προηγούμενων συναλλαγών διότι απαιτεί επαναυπολογισμό των αποδείξεων εργασίας όλων των ακόλουθων μπλοκ (block). Όταν δύο μπλοκ βρίσκονται ταυτόχρονα, οι εξορύκτες εργάζονται πάνω στο πρώτο μπλοκ που λαμβάνουν και αλλάζουν σε μεγαλύτερες αλυσίδες των μπλοκ μόλις βρεθεί το επόμενο μπλοκ. Αυτό επιτρέπει η εξόρυξη να είναι ασφαλής και διατηρεί μια παγκόσμια γενική συναίνεση που βασίζεται στην επεξεργαστική ισχύ." + howminingworkstxt2: "Για να επιβεβαιωθούν οι νέες συναλλαγές, αυτές πρέπει να συμπεριληφθούν σε ένα μπλοκ (block) μαζί με μια μαθηματική απόδειξη εργασίας. Τέτοιες αποδείξεις είναι πολύ δύσκολο να παραχθούν διότι δεν υπάρχει κανένας τρόπος δημιουργίας τους παρά μόνο δοκιμάζοντας δισεκατομμύρια υπολογισμούς το δευτερόλεπτο. Αυτό απαιτεί οι εξορύκτες να εκτελούν αυτούς τους υπολογισμούς πριν τα μπλοκ (blocks) γίνουν αποδεκτά από το δίκτυο και πριν αυτοί λάβουν μια αμοιβή. Καθώς περισσότεροι άνθρωποι ξεκινάνε εξόρυξη, η δυσκολία εξεύρεσης έγκυρων μπλοκ αυξάνεται αυτόματα από το δίκτυο για να διασφαλίσει ότι ο μέσος χρόνος για να βρεθεί ένα μπλοκ παραμένει ίσος με 10 λεπτά. Κατά συνέπεια, η εξόρυξη είναι μια πολύ ανταγωνιστική επιχείρηση όπου κανένας ιδιώτης εξορύκτης δεν μπορεί να ελέγξει τι περιλαμβάνεται εντός της αλυσίδας των μπλοκ (blockchain)." + howminingworkstxt3: "Η απόδειξη εργασίας είναι επίσης σχεδιασμένη να εξαρτάται από το προηγούμενο μπλοκ (block) για να επιβάλλει μια χρονολογική σειρά στην αλυσίδα των μπλοκ (blockchain). Αυτό καθιστά εκθετικά δύσκολη την αντιστροφή των προηγούμενων συναλλαγών διότι απαιτεί επαναυπολογισμό των αποδείξεων εργασίας όλων των ακόλουθων μπλοκ (block). Όταν δύο μπλοκ βρίσκονται ταυτόχρονα, οι εξορύκτες εργάζονται πάνω στο πρώτο μπλοκ που λαμβάνουν και αλλάζουν σε μεγαλύτερες αλυσίδες των μπλοκ μόλις βρεθεί το επόμενο μπλοκ. Αυτό επιτρέπει η εξόρυξη να είναι ασφαλής και διατηρεί μια παγκόσμια γενική συναίνεση που βασίζεται στην επεξεργαστική ισχύ." howminingworkstxt4: "Οι εξορύκτες Bitcoin δεν είναι μπορούν ούτε να εξαπατήσουν αυξάνοντας την δική τους ανταμοιβή, ούτε να επεξεργαστούν δόλιες συναλλαγές οι οποίες θα μπορούσαν να αλλοιώσουν το δίκτυο του Bitcoin διότι όλοι οι κόμβοι Bitcoin θα απέρριπταν οποιοδήποτε μπλοκ (block) περιέχει άκυρα δεδομένα σύμφωνα με τους κανόνες του πρωτόκολλου του Bitcoin. Συνεπώς, το δίκτυο παραμένει ασφαλές ακόμα και αν όλοι οι εξορύκτες Bitcoin δεν είναι έμπιστοι." miningwaste: "H εξόρυξη του Bitcoin δεν είναι σπατάλη ενέργειας;" miningwastetxt1: "Η δαπάνη ενέργειας για να ασφαλιστεί και να λειτουργήσει ένα δίκτυο πληρωμής ούτε που είναι σπατάλη. Όπως και κάθε άλλη υπηρεσία πληρωμής, η χρήση του Bitcoin συνεπάγεται κόστη επεξεργασίας. Οι υπηρεσίες που είναι αναγκαίες για την λειτουργία των ευρύτατα διαδεδομένων τρεχόντων νομισματικών οικονομικών συστημάτων, όπως είναι οι τράπεζες, οι πιστωτικές κάρτες και τα θωρακισμένα οχήματα επίσης καταναλώνουν πολλή ενέργεια. Παρόλο που σε αντίθεση με το Bitcoin, η συνολική ενεργειακή τους κατανάλωση δεν είναι διαφανής και δεν μπορεί να μετρηθεί τόσο εύκολα." miningwastetxt2: "Η εξόρυξη Bitcoin (mining) έχει σχεδιαστεί για να τελειοποιηθεί περισσότερο με την πάροδο του χρόνο με χρήση εξειδικευμένου υλισμικού (hardware) που καταναλώνει λιγότερη ενέργεια και τα λειτουργικά κόστη εξόρυξης θα πρέπει να συνεχίσουν να είναι αναλογικά με την ζήτηση. Όταν η εξόρυξη Bitcoin γίνει πολύ αναγωνιστική και λιγότερο επικερδής, μερικοί εξορύκτες επιλέγουν να τερματίσουν τις δραστηριότητές τους. Επιπροσθέτως, όλη η ενέργεια που δαπανάται για την εξόρυξη, τελικά μετασχηματίζεται σε θερμότητα και οι πιο κερδοφόροι εξορύκτες θα είναι εκείνοι που αξιοποιούν αυτή τη θερμότητα για καλή χρήση. Ένα βέλτιστα αποδοτικό δίκτυο εξόρυξης είναι αυτό που δεν καταναλώνει στην πραγματικότητα επιπλέον ενέργεια. Ενώ αυτό είναι το ιδανικό, τα οικονομικά της εξόρυξης είναι τέτοια που οι εξορύκτες σε ατομικό επίπεδο υπερβάλλουν εαυτόν προς αυτή την κατεύθυνση," miningsecure: "Πώς η εξόρυξη βοηθάει στην ασφάλεια του Bitcoin;" - miningsecuretxt1: "Η εξόρυξη (mining) δημιουργεί το ισοδύναμο μιας ανταγωνιστικής λοταρίας η οποία καθιστά δύσκολο για τον καθένα να προσθέτει διαδοχικά νέα μπλοκ σε μια αλυσίδα των μπλοκ (block chain). Αυτό προστατεύει την ουδετερότητα του δικτύου αποτρέποντας οποιοδήποτε άτομο από το να αποκτήσει εξουσία για να μπλοκάρει συγκεκριμένες συναλλαγές. Αυτό επίσης αποτρέπει οποιοδήποτε άτομο από το να αντικαταστήσει τμήματα της αλυσίδας των μπλοκ (block chain) ώστε να μειώσουν τις δικές τους δαπάνες πράγμα το οποίο θα μπορούσε να χρησιμοποιηθεί στην εξαπάτηση άλλων χρηστών. Η εξόρυξη καθιστά εκθετικά πιο δύσκολο να αντιστραφεί μια προηγούμενη συναλλαγή αφού απαιτείται η επαναγραφή όλων των μπλοκ (blocks) που ακολουθούν την συναλλαγή αυτή." + miningsecuretxt1: "Η εξόρυξη (mining) δημιουργεί το ισοδύναμο μιας ανταγωνιστικής λοταρίας η οποία καθιστά δύσκολο για τον καθένα να προσθέτει διαδοχικά νέα μπλοκ σε μια αλυσίδα των μπλοκ (blockchain). Αυτό προστατεύει την ουδετερότητα του δικτύου αποτρέποντας οποιοδήποτε άτομο από το να αποκτήσει εξουσία για να μπλοκάρει συγκεκριμένες συναλλαγές. Αυτό επίσης αποτρέπει οποιοδήποτε άτομο από το να αντικαταστήσει τμήματα της αλυσίδας των μπλοκ (blockchain) ώστε να μειώσουν τις δικές τους δαπάνες πράγμα το οποίο θα μπορούσε να χρησιμοποιηθεί στην εξαπάτηση άλλων χρηστών. Η εξόρυξη καθιστά εκθετικά πιο δύσκολο να αντιστραφεί μια προηγούμενη συναλλαγή αφού απαιτείται η επαναγραφή όλων των μπλοκ (blocks) που ακολουθούν την συναλλαγή αυτή." miningstart: "Τι χρειάζομαι για να ξεκινήσω την εξόρυξη;" miningstarttxt1: "Κατά τις πρώτες ημέρες του Bitcoin, ο καθένας μπορούσε να βρει ένα καινούριο μπλοκ (block) χρησιμοποιώντας την κεντρική μονάδα επεξεργασίας (CPU) του υπολογιστή τους. Καθώς όλο και περισσότεροι άνθρωποι ξεκίνησαν εξόρυξη, η δυσκολία εξεύρεσης νέων μπλοκ αυξήθηκε κατά πολύ στο σημείο που η μόνη αποδοτική από πλευράς κόστους μέθοδος σήμερα είναι η χρήση εξειδικευμένου υλισμικού (hardware). Μπορείτε να επισκεφθείτε το BitcoinMining.com για περισσότερες πληροφορίες." security: "Ασφάλεια" @@ -374,7 +374,7 @@ el: hackedtxt1: "Οι κανόνες του πρωτόκολλου και η κρυπτογραφία που χρησιμοποιείται για το Bitcoin λειτουργούν για χρόνια μετά το ξεκίνημά τους γεγονός που αποτελεί καλή ένδειξη ότι η ιδέα είναι καλά σχεδιασμένη. Ωστόσο, κενά ασφαλείας έχουν βρεθεί και επιδιορθωθεί κατά καιρούς σε διάφορες εφαρμογές λογισμικού. Όπως και σε κάθε άλλη μορφή λογισμικού, η ασφάλεια του λογισμικού Bitcoin εξαρτάται από την ταχύτητα με την οποία τα προβλήματα βρίσκονται και επιδιορθώνονται. Όσο περισσότερα τέτοια ζητήματα ανακαλύπτονται, τόσο περισσότερη ωριμότητα κερδίζει το Bitcoin. " hackedtxt2: "Υπάρχουν συχνά παρανοήσεις σχετικά με κλοπές και διαρροές ασφαλείας που συνέβησαν σε ποικίλες ανταλλαγές και επιχειρήσεις. Παρόλο που τα γεγονότα αυτά είναι ατυχή, κανένα από αυτά δεν σχετίζεται με απόκτηση παράνομης πρόσβασης (hacking) στο ίδιο το Bitcoin, ούτε και υπαινίσσεται έμφυτα ελαττώματα στο Bitcoin. Όπως ακριβώς μια ληστεία τράπεζας δεν σημαίνει ότι το δολάριο είναι εκτεθειμένο σε κίνδυνο. Ωστόσο, είναι ακριβές να ειπωθεί ότι το πλήρες σύνολο σωστών πρακτικών και ευκολονόητων λύσεων προστασίας είναι αναγκαίες για να δοθεί στους χρήστες καλύτερη προστασία στα χρήματά τους και να μειωθεί ο γενικός κίνδυνος κλοπής και απώλειας. Κατά τη διάρκεια των τελευταίων χρόνων, έχουν αναπτυχθεί τέτοιες δυνατότητες ασφαλείας, όπως η κρυπτογράφηση πορτοφολιού, πορτοφόλια εκτός σύνδεσης, πορτοφόλια υλισμικού και συναλλαγές πολλαπλών υπογραφών." collude: "Θα μπορούσαν οι χρήστες να συνωμοτήσουν εναντίον του Bitcoin;" - colludetxt1: "Δεν είναι εφικτό να αλλάξει το πρωτόκολλο του Bitcoin τόσο εύκολα. Οποιοσδήποτε πελάτης του Bitcoin δεν συμμορφώνεται με τους ίδιους κανόνες, δεν μπορεί να επιβάλλει τους δικούς του κανόνες στους άλλους χρήστες. Σύμφωνα με τις τρέχουσες προδιαγραφές, η διπλή δαπάνη δεν είναι εφικτή στην ίδια αλυσίδα των μπλοκ (block chain) και ούτε και η δαπάνη bitcoins χωρίς μια έγκυρη υπογραφή. Συνεπώς, δεν είναι εφικτό να δημιουργήσουμε ανεξέλεγκτα πoσά από bitcoins ως δια μαγείας, να ξοδέψουμε τα κεφάλαια των άλλων χρηστών, να αλλοιώσουμε το δίκτυο ή οτιδήποτε παρόμοιο με τα παραπάνω." + colludetxt1: "Δεν είναι εφικτό να αλλάξει το πρωτόκολλο του Bitcoin τόσο εύκολα. Οποιοσδήποτε πελάτης του Bitcoin δεν συμμορφώνεται με τους ίδιους κανόνες, δεν μπορεί να επιβάλλει τους δικούς του κανόνες στους άλλους χρήστες. Σύμφωνα με τις τρέχουσες προδιαγραφές, η διπλή δαπάνη δεν είναι εφικτή στην ίδια αλυσίδα των μπλοκ (blockchain) και ούτε και η δαπάνη bitcoins χωρίς μια έγκυρη υπογραφή. Συνεπώς, δεν είναι εφικτό να δημιουργήσουμε ανεξέλεγκτα πoσά από bitcoins ως δια μαγείας, να ξοδέψουμε τα κεφάλαια των άλλων χρηστών, να αλλοιώσουμε το δίκτυο ή οτιδήποτε παρόμοιο με τα παραπάνω." colludetxt2: "Ωστόσο, η πλειοψηφία των εξορυκτών (miners) θα μπορούσαν αυθαίρετα να εμποδίσουν ή να αντιστρέψουν πρόσφατες συναλλαγές. Η πλειοψηφία των χρηστών μπορεί επίσης να ασκήσει πίεση ώστε να υιοθετηθούν κάποιες αλλαγές. Λόγω του ότι το Bitcoin λειτουργεί σωστά μόνο με τη γενική συνέναιση ανάμεσα στους χρήστες, η αλλαγή στο πρωτόκολλο μπορεί να είναι πολύ δύσκολη και απαιτεί η συντριπτική πλειοψηφία των χρηστών να υιοθετήσει τις αλλαγές κατά τέτοιο τρόπο ώστε οι υπόλοιποι χρήστες να μην έχουν σχεδόν καμιά επιλογή παρά να ακολουθήσουν. Κατά γενικό κανόνα, είναι δύσκολο να φανταστούμε τον λόγο για τον οποίο οποιοσδήποτε χρήστης Bitcoin θα επέλεγε να υιοθετήσει οποιαδήποτε αλλαγή η οποία θα μπορούσε να θέσει σε κίνδυνο τα ίδια του τα χρήματα." quantum: "Είναι το Bitcoin ευάλωτο στην κβαντική πληροφορική;" quantumtxt1: "Ναι, τα περισσότερα από τα συστήματα που βασίζονται στην κρυπτογραφία γενικά είναι, συμπεριλαμβανομένων και των παραδοσιακών τραπεζικών συστημάτων. Ωστόσο, οι κβαντικοί υπολογιστές δεν υπάρχουν ακόμα και πιθανώς να μην υπάρξουν για αρκετό καιρό ακόμα. Στην περίπτωση που η κβαντική πληροφορική θα μπορούσε να είναι επικείμενη απειλή για το Bitcoin, το πρωτόκολλο θα μπορούσε να αναβαθμιστεί για να χρησιμοποιεί μετα-κβαντικούς αλγόριθμους. Δεδομένης της σπουδαιότητας που θα είχε αυτή η ενημέρωση, μπορεί να αναμένεται με ασφάλεια ότι θα ελέγχονταν σε μεγάλο βαθμό από τους προγραμματιστές και θα υιοθετούνταν από όλους τους χρήστες του Bitcoin." @@ -417,12 +417,12 @@ el: intro: "Αυτή είναι μια ερώτηση που συχνά προκαλεί σύγχυση. Ορίστε μια γρήγορη εξήγηση!" basics: "Τα βασικά για ένα νέο χρήστη" basicstxt1: "Ως νέος χρήστης, μπορείτε να ξεκινήσετε με το Bitcoin χωρίς να καταλαβαίνετε τις τεχνικές λεπτομέρειες. Αφότου έχετε εγκαταστήσει το Bitcoin πορτοφόλι στον υπολογιστή ή στο κινητό σας τηλέφωνο, θα δημιουργήσει την πρώτη Bitcoin διεύθυνση και μπορείτε να δημιουργήσετε περισσότερες οποτεδήποτε χρειαστείτε. Μπορείτε να αποκαλύψετε τις διευθύνσεις στους φίλους σας έτσι ώστε να μπορούν να σας πληρώσουν ή το αντίστροφο. Στην πραγματικότητα, αυτό είναι αρκετά παρόμοιο με την λειτουργία του ηλεκτρονικού ταχυδρομείου, με την εξαίρεση ότι οι διευθύνσεις Bitcoin θα πρέπει να χρησιμοποιούνται μόνο για μια φορά." - balances: "Υπόλοιπα Λογαριασμού - αλυσίδα των μπλοκ (block chain)" - balancestxt: "Η αλυσίδα των μπλοκ (block chain) είναι ένα κοινόχρηστο δημόσιο λογιστικό βιβλίο πάνω το οποίο βασίζεται ολόκληρο το δίκτυο Bitcoin. Όλες οι επιβεβαιωμένες συναλλαγές συμπεριλαμβάνονται στην αλυσίδα των μπλοκ. Με αυτό τον τρόπο, τα πορτοφόλια Bitcoin μπορούν να υπολογίζουν το διαθέσιμο υπόλοιπο και οι νέες συναλλαγές μπορούν να επαληθεύονται ότι δαπανώνται bitcoins τα οποία στην πραγματικότητα κατέχονται από αυτόν που τα δαπανά. Η ακεραιότητα και η χρονολογική σειρά της αλυσίδας των μπλοκ εφαρμόζονται με την κρυπτογραφία." + balances: "Υπόλοιπα Λογαριασμού - αλυσίδα των μπλοκ (blockchain)" + balancestxt: "Η αλυσίδα των μπλοκ (blockchain) είναι ένα κοινόχρηστο δημόσιο λογιστικό βιβλίο πάνω το οποίο βασίζεται ολόκληρο το δίκτυο Bitcoin. Όλες οι επιβεβαιωμένες συναλλαγές συμπεριλαμβάνονται στην αλυσίδα των μπλοκ. Με αυτό τον τρόπο, τα πορτοφόλια Bitcoin μπορούν να υπολογίζουν το διαθέσιμο υπόλοιπο και οι νέες συναλλαγές μπορούν να επαληθεύονται ότι δαπανώνται bitcoins τα οποία στην πραγματικότητα κατέχονται από αυτόν που τα δαπανά. Η ακεραιότητα και η χρονολογική σειρά της αλυσίδας των μπλοκ εφαρμόζονται με την κρυπτογραφία." transactions: "Συναλλαγές - ιδιωτικά κλειδιά" - transactionstxt: "Μια συναλλαγή είναι μια μεταφορά αξίας μεταξύ πορτοφολιών Bitcoin η οποία συμπεριλαμβάνεται στην αλυσίδα των μπλοκ (block chain). Τα πορτοφόλια Bitcoin κρατάνε ένα μυστικό κομμάτι δεδομένων που ονομάζεται ιδιωτικό κλειδί ή φύτρο (seed), το οποίο χρησιμοποιείται για να υπογράψει συναλλαγές παρέχοντας μια μαθηματική απόδειξη η οποία έχει προέλθει από το πορτοφόλι του ιδιοκτήτη. Η υπογραφή επίσης εμποδίζει τη συναλλαγή από το να τροποποιηθεί από τον οποιονδήποτε μόλις αυτή έχει εκδοθεί. Όλες οι συναλλαγές μεταδίδονται μεταξύ των χρηστών και συνήθως ξεκινάνε να επιβεβαιώνονται από το δίκτυα στα επόμενα 10 λεπτά μέσω μια διαδικασίας που ονομάζεται εξόρυξη." + transactionstxt: "Μια συναλλαγή είναι μια μεταφορά αξίας μεταξύ πορτοφολιών Bitcoin η οποία συμπεριλαμβάνεται στην αλυσίδα των μπλοκ (blockchain). Τα πορτοφόλια Bitcoin κρατάνε ένα μυστικό κομμάτι δεδομένων που ονομάζεται ιδιωτικό κλειδί ή φύτρο (seed), το οποίο χρησιμοποιείται για να υπογράψει συναλλαγές παρέχοντας μια μαθηματική απόδειξη η οποία έχει προέλθει από το πορτοφόλι του ιδιοκτήτη. Η υπογραφή επίσης εμποδίζει τη συναλλαγή από το να τροποποιηθεί από τον οποιονδήποτε μόλις αυτή έχει εκδοθεί. Όλες οι συναλλαγές μεταδίδονται μεταξύ των χρηστών και συνήθως ξεκινάνε να επιβεβαιώνονται από το δίκτυα στα επόμενα 10 λεπτά μέσω μια διαδικασίας που ονομάζεται εξόρυξη." processing: "Επεξεργασία - εξόρυξη" - processingtxt: "Η εξόρυξη είναι ένα κατανεμημένο συναινετικό σύστημα που χρησιμοποιείται για την επιβεβαίωση συναλλαγών σε αναμονή συμπεριλαμβάνοντας αυτές στην αλυσίδα των μπλοκ (block chain). Επιβάλλει μια χρονολογική σειρά στην αλυσίδα των μπλοκ, προστατεύει την ουδετερότητα του δικτύου και επιτρέπει σε διαφορετικούς υπολογιστές να συμφωνήσουν σχετικά με την κατάσταση του συστήματος. Για να επιβεβαιωθούν, οι συναλλαγές πρέπει να εντάσσονται σε ένα μπλοκ (block) που υπακούει σε πολύ αυστηρούς κανόνες κρυπτογραφίας που θα επαληθευτούν από το δίκτυο. Οι κανόνες αυτοί εμποδίζουν τα προηγούμενα μπλοκ (blocks) από το να τροποποιηθούν, διότι κάτι τέτοιο θα ακύρωνε όλα τα ακόλουθα μπλοκ. Η εξόρυξη δημιουργεί επίσης το ισοδύναμο μιας ανταγωνιστικής λοταρίας, η οποία εμποδίζει κάθε άτομο από το να προσθέσει εύκολα νέα διαδοχικά μπλοκ (blocks) στην αλυσίδα των μπλοκ (block chain). Με αυτόν τον τρόπο, κανένα άτομο δεν μπορεί να ελέγξει τι περιλαμβάνεται στην αλυσίδα των μπλοκ ή να αντικαταστήσει τμήματα της αλυσίδας αυτής για να ακυρώσει τις δικές του δαπάνες." + processingtxt: "Η εξόρυξη είναι ένα κατανεμημένο συναινετικό σύστημα που χρησιμοποιείται για την επιβεβαίωση συναλλαγών σε αναμονή συμπεριλαμβάνοντας αυτές στην αλυσίδα των μπλοκ (blockchain). Επιβάλλει μια χρονολογική σειρά στην αλυσίδα των μπλοκ, προστατεύει την ουδετερότητα του δικτύου και επιτρέπει σε διαφορετικούς υπολογιστές να συμφωνήσουν σχετικά με την κατάσταση του συστήματος. Για να επιβεβαιωθούν, οι συναλλαγές πρέπει να εντάσσονται σε ένα μπλοκ (block) που υπακούει σε πολύ αυστηρούς κανόνες κρυπτογραφίας που θα επαληθευτούν από το δίκτυο. Οι κανόνες αυτοί εμποδίζουν τα προηγούμενα μπλοκ (blocks) από το να τροποποιηθούν, διότι κάτι τέτοιο θα ακύρωνε όλα τα ακόλουθα μπλοκ. Η εξόρυξη δημιουργεί επίσης το ισοδύναμο μιας ανταγωνιστικής λοταρίας, η οποία εμποδίζει κάθε άτομο από το να προσθέσει εύκολα νέα διαδοχικά μπλοκ (blocks) στην αλυσίδα των μπλοκ (blockchain). Με αυτόν τον τρόπο, κανένα άτομο δεν μπορεί να ελέγξει τι περιλαμβάνεται στην αλυσίδα των μπλοκ ή να αντικαταστήσει τμήματα της αλυσίδας αυτής για να ακυρώσει τις δικές του δαπάνες." readmore: "Εξερευνώντας έναν νέο κόσμο" readmoretxt: "Αυτή είναι μια πολύ σύντομη και περιεκτική περίληψη του συστήματος. Αν θέλετε να υπεισέλθετε σε λεπτομέρειες, μπορείτε να διαβάσετε το πρωτότυπο άρθρο το οποίο περιγράφει τον σχεδιασμό του συστήματος, διαβάστε την τεκμηρίωση προγραμματιστή, και εξερευνήστε το Bitcoin wiki." index: @@ -614,10 +614,10 @@ el: bittxt: "Το Μπιτ (bit) είναι μια συνηθισμένη μονάδα που χρησιμοποιείται για να προσδιορίσει μια υπομονάδα ενός bitcoin. 1,000,000 bits ισούνται με 1 bitcoin (BTC or B⃦). Η μονάδα αυτή είναι συνήθως περισσότερο πρακτική για τιμολόγηση φιλοδωρημάτων, αγαθών και υπηρεσιών." bitcoin: "Bitcoin" bitcointxt: "Το Bitcoin - με κεφαλαίο, χρησιμοποιείται όταν περιγράφουμε την έννοια του Bitcoin, ή ολόκληρο το ίδιο το δίκτυο. π.χ \"Μάθαινα για το πρωτόκολλο Bitcoin σήμερα.\"
Το bitcoin - χωρίς κεφαλαίο, χρησιμοποιείται για να περιγράψει τα bitcoins ως μονάδα ενός λογαριασμού. e.g. \"Έστειλα δέκα bitcoins σήμερα.\" Συχνά χρησιμοποιείται η συντομογραφία BTC ή XBT." - blockchain: "Αλυσίδα των Μπλοκ (Block Chain)" - blockchaintxt: "Η αλυσίδα των μπλοκ (block chain) είναι ένα δημόσιο αρχείο συναλλαγών Bitcoin με χρονολογική σειρά. Η αλυσίδα των μπλοκ διαμοιράζεται μεταξύ όλων των χρηστών Bitcoin. Χρησιμοποιείται για να επαληθεύσει την μονιμότητα των συναλλαγών Bitcoin και για να αποτρέψει διπλές δαπάνες (double spending)." + blockchain: "Αλυσίδα των Μπλοκ (Blockchain)" + blockchaintxt: "Η αλυσίδα των μπλοκ (blockchain) είναι ένα δημόσιο αρχείο συναλλαγών Bitcoin με χρονολογική σειρά. Η αλυσίδα των μπλοκ διαμοιράζεται μεταξύ όλων των χρηστών Bitcoin. Χρησιμοποιείται για να επαληθεύσει την μονιμότητα των συναλλαγών Bitcoin και για να αποτρέψει διπλές δαπάνες (double spending)." block: "Μπλοκ (Βlock)" - blocktxt: "Ένα μπλοκ είναι ένα αρχείο στην αλυσίδα των μπλοκ (block chain) το οποίο περιέχει και επικυρώνει πολλές συναλλαγές σε αναμονή. Περίπου κάθε 10 λεπτά, κατά μέσο όρο, ένα νέο μπλοκ που συμπεριλαμβάνει συναλλαγές επισυνάπτεται στο αλυσίδα των μπλοκ μέσω εξόρυξη." + blocktxt: "Ένα μπλοκ είναι ένα αρχείο στην αλυσίδα των μπλοκ (blockchain) το οποίο περιέχει και επικυρώνει πολλές συναλλαγές σε αναμονή. Περίπου κάθε 10 λεπτά, κατά μέσο όρο, ένα νέο μπλοκ που συμπεριλαμβάνει συναλλαγές επισυνάπτεται στο αλυσίδα των μπλοκ μέσω εξόρυξη." btc: "BTC" btctxt: "Το BTC είναι μια συνηθισμένη μονάδα που χρησιμοποιείται για να προσδιορίσει ένα bitcoin (B⃦)." confirmation: "Επιβεβαίωση" @@ -637,7 +637,7 @@ el: signature: "Υπογραφή" signaturetxt: "Μια κρυπτογραφική υπογραφή είναι ένας μαθηματικός μηχανισμός που επιτρέπει σε κάποιον να αποδείξει την κυριότητα. Στην περίπτωση του Bitcoin, ένα Bitcoin πορτοφόλι και τα δικά του ιδιωτικό(ά) κλειδί(ά) συνδέονται με κάποια μαθηματική μαγεία. Όταν το λογισμικό σας Bitcoin υπογράψει μια συναλλαγή με το κατάλληλο ιδιωτικό κλειδί, όλο το δίκτυο μπορεί να δει ότι η υπογραφή συμπίπτει με τα bitcoins που ξοδεύονται. Ωστόσο, δεν υπάρχει τρόπος, που να χαλάσει ο κόσμος, κάποιος να μαντέψει το ιδιωτικό κλειδί σας για να κλέψει τα κερδισμένα με κόπο bitcoins σας." wallet: "Πορτοφόλι" - wallettxt: "Ένα Bitcoin πορτοφόλι είναι γενικώς το ισοδύναμο ενός φυσικού πορτοφολιού στο δίκτυο Bitcoin. Στην πραγματικότητα, το πορτοφόλι περιέχει τα δικά σας ιδιωτικό(ά) κλειδί(ά) τα οποία σας επιτρέπουν να ξοδεύετε τα bitcoins που κατενέμονται σε αυτή την αλυσίδα των μπλοκ (block chain). Το κάθε Bitcoin πορτοφόλι μπορεί να σας δείξει το συνολικό υπόλοιπο όλων των bitcoins που ελέγχει και σας αφήνει να πληρώσετε ένα συγκεκριμένο ποσό σε ένα συγκεκριμένο άτομο, όπως συμβαίνει και με ένα αληθινό πορτοφόλι. Αυτό διαφέρει από τις πιστωτικές κάρτες όπου χρεώνεστε από τον έμπορο." + wallettxt: "Ένα Bitcoin πορτοφόλι είναι γενικώς το ισοδύναμο ενός φυσικού πορτοφολιού στο δίκτυο Bitcoin. Στην πραγματικότητα, το πορτοφόλι περιέχει τα δικά σας ιδιωτικό(ά) κλειδί(ά) τα οποία σας επιτρέπουν να ξοδεύετε τα bitcoins που κατενέμονται σε αυτή την αλυσίδα των μπλοκ (blockchain). Το κάθε Bitcoin πορτοφόλι μπορεί να σας δείξει το συνολικό υπόλοιπο όλων των bitcoins που ελέγχει και σας αφήνει να πληρώσετε ένα συγκεκριμένο ποσό σε ένα συγκεκριμένο άτομο, όπως συμβαίνει και με ένα αληθινό πορτοφόλι. Αυτό διαφέρει από τις πιστωτικές κάρτες όπου χρεώνεστε από τον έμπορο." you-need-to-know: title: "Μερικά πράγματα που πρέπει να γνωρίζετε - Bitcoin" pagetitle: "Μερικά πράγματα που πρέπει να γνωρίζετε " @@ -712,7 +712,7 @@ el: address: address bit: bit bitcoin: bitcoin - blockchain: block-chain + blockchain: blockchain block: block btc: btc confirmation: confirmation diff --git a/_translations/en.yml b/_translations/en.yml index 2fd0e024b0..3a0a536822 100644 --- a/_translations/en.yml +++ b/_translations/en.yml @@ -306,7 +306,7 @@ en: source: "Source code" versionhistory: "Show version history" notelicense: "Bitcoin Core is a community-driven free software project, released under the MIT license." - notesync: "Bitcoin Core initial synchronization will take time and download a lot of data. You should make sure that you have enough bandwidth and storage for the full block chain size (over 20GB). If you have a good Internet connection, you can help strengthen the network by keeping your PC running with Bitcoin Core and port 8333 open." + notesync: "Bitcoin Core initial synchronization will take time and download a lot of data. You should make sure that you have enough bandwidth and storage for the full blockchain size (over 20GB). If you have a good Internet connection, you can help strengthen the network by keeping your PC running with Bitcoin Core and port 8333 open." full_node_guide: "Read the full node guide for details." patient: "Check your bandwidth and space" releasekeys: "Bitcoin Core Release Signing Keys" @@ -334,7 +334,7 @@ en: whocontrolstxt1: "Nobody owns the Bitcoin network much like no one owns the technology behind email. Bitcoin is controlled by all Bitcoin users around the world. While developers are improving the software, they can't force a change in the Bitcoin protocol because all users are free to choose what software and version they use. In order to stay compatible with each other, all users need to use software complying with the same rules. Bitcoin can only work correctly with a complete consensus among all users. Therefore, all users and developers have a strong incentive to protect this consensus." howitworks: "How does Bitcoin work?" howitworkstxt1: "From a user perspective, Bitcoin is nothing more than a mobile app or computer program that provides a personal Bitcoin wallet and allows a user to send and receive bitcoins with them. This is how Bitcoin works for most users." - howitworkstxt2: "Behind the scenes, the Bitcoin network is sharing a public ledger called the \"block chain\". This ledger contains every transaction ever processed, allowing a user's computer to verify the validity of each transaction. The authenticity of each transaction is protected by digital signatures corresponding to the sending addresses, allowing all users to have full control over sending bitcoins from their own Bitcoin addresses. In addition, anyone can process transactions using the computing power of specialized hardware and earn a reward in bitcoins for this service. This is often called \"mining\". To learn more about Bitcoin, you can consult the dedicated page and the original paper." + howitworkstxt2: "Behind the scenes, the Bitcoin network is sharing a public ledger called the \"blockchain\". This ledger contains every transaction ever processed, allowing a user's computer to verify the validity of each transaction. The authenticity of each transaction is protected by digital signatures corresponding to the sending addresses, allowing all users to have full control over sending bitcoins from their own Bitcoin addresses. In addition, anyone can process transactions using the computing power of specialized hardware and earn a reward in bitcoins for this service. This is often called \"mining\". To learn more about Bitcoin, you can consult the dedicated page and the original paper." used: "Is Bitcoin really used by people?" usedtxt1: "Yes. There is a growing number of businesses and individuals using Bitcoin. This includes brick and mortar businesses like restaurants, apartments, law firms, and popular online services such as Namecheap, WordPress, and Reddit. While Bitcoin remains a relatively new phenomenon, it is growing fast. At the end of August 2013, the value of all bitcoins in circulation exceeded US$ 1.5 billion with millions of dollars worth of bitcoins exchanged daily." acquire: "How does one acquire bitcoins?" @@ -368,7 +368,7 @@ en: advantagesli3: "Fewer risks for merchants - Bitcoin transactions are secure, irreversible, and do not contain customers’ sensitive or personal information. This protects merchants from losses caused by fraud or fraudulent chargebacks, and there is no need for PCI compliance. Merchants can easily expand to new markets where either credit cards are not available or fraud rates are unacceptably high. The net results are lower fees, larger markets, and fewer administrative costs." advantagesli4: "Security and control - Bitcoin users are in full control of their transactions; it is impossible for merchants to force unwanted or unnoticed charges as can happen with other payment methods. Bitcoin payments can be made without personal information tied to the transaction. This offers strong protection against identity theft. Bitcoin users can also protect their money with backup and encryption." - advantagesli5: "Transparent and neutral - All information concerning the Bitcoin money supply itself is readily available on the block chain for anybody to verify and use in real-time. No individual or organization can control or manipulate the Bitcoin protocol because it is cryptographically secure. This allows the core of Bitcoin to be trusted for being completely neutral, transparent and predictable." + advantagesli5: "Transparent and neutral - All information concerning the Bitcoin money supply itself is readily available on the blockchain for anybody to verify and use in real-time. No individual or organization can control or manipulate the Bitcoin protocol because it is cryptographically secure. This allows the core of Bitcoin to be trusted for being completely neutral, transparent and predictable." disadvantages: "What are the disadvantages of Bitcoin?" disadvantagesli1: "Degree of acceptance - Many people are still unaware of Bitcoin. Every day, more businesses accept bitcoins because they want the advantages of doing so, but the list remains small and still needs to grow in order to benefit from network effects." disadvantagesli2: "Volatility - The total value of bitcoins in circulation and the number of businesses using Bitcoin are still very small compared to what they could be. Therefore, relatively small events, trades, or business activities can significantly affect the price. In theory, this volatility will decrease as Bitcoin markets and the technology matures. Never before has the world seen a start-up currency, so it is truly difficult (and exciting) to imagine how it will play out." @@ -384,7 +384,7 @@ en: anonymoustxt1: "Bitcoin is designed to allow its users to send and receive payments with an acceptable level of privacy as well as any other form of money. However, Bitcoin is not anonymous and cannot offer the same level of privacy as cash. The use of Bitcoin leaves extensive public records. Various mechanisms exist to protect users' privacy, and more are in development. However, there is still work to be done before these features are used correctly by most Bitcoin users." anonymoustxt2: "Some concerns have been raised that private transactions could be used for illegal purposes with Bitcoin. However, it is worth noting that Bitcoin will undoubtedly be subjected to similar regulations that are already in place inside existing financial systems. Bitcoin cannot be more anonymous than cash and it is not likely to prevent criminal investigations from being conducted. Additionally, Bitcoin is also designed to prevent a large range of financial crimes." lost: "What happens when bitcoins are lost?" - losttxt1: "When a user loses his wallet, it has the effect of removing money out of circulation. Lost bitcoins still remain in the block chain just like any other bitcoins. However, lost bitcoins remain dormant forever because there is no way for anybody to find the private key(s) that would allow them to be spent again. Because of the law of supply and demand, when fewer bitcoins are available, the ones that are left will be in higher demand and increase in value to compensate." + losttxt1: "When a user loses his wallet, it has the effect of removing money out of circulation. Lost bitcoins still remain in the blockchain just like any other bitcoins. However, lost bitcoins remain dormant forever because there is no way for anybody to find the private key(s) that would allow them to be spent again. Because of the law of supply and demand, when fewer bitcoins are available, the ones that are left will be in higher demand and increase in value to compensate." scale: "Can Bitcoin scale to become a major payment network?" scaletxt1: "The Bitcoin network can already process a much higher number of transactions per second than it does today. It is, however, not entirely ready to scale to the level of major credit card networks. Work is underway to lift current limitations, and future requirements are well known. Since inception, every aspect of the Bitcoin network has been in a continuous process of maturation, optimization, and specialization, and it should be expected to remain that way for some years to come. As traffic grows, more Bitcoin users may use lightweight clients, and full network nodes may become a more specialized service. For more details, see the Scalability page on the Wiki." legal: "Legal" @@ -483,20 +483,20 @@ en: poweredoff: "What if I receive a bitcoin when my computer is powered off?" poweredofftxt1: "This works fine. The bitcoins will appear next time you start your wallet application. Bitcoins are not actually received by the software on your computer, they are appended to a public ledger that is shared between all the devices on the network. If you are sent bitcoins when your wallet client program is not running and you later launch it, it will download blocks and catch up with any transactions it did not already know about, and the bitcoins will eventually appear as if they were just received in real time. Your wallet is only needed when you wish to spend bitcoins." sync: "What does \"synchronizing\" mean and why does it take so long?" - synctxt1: "Long synchronization time is only required with full node clients like Bitcoin Core. Technically speaking, synchronizing is the process of downloading and verifying all previous Bitcoin transactions on the network. For some Bitcoin clients to calculate the spendable balance of your Bitcoin wallet and make new transactions, it needs to be aware of all previous transactions. This step can be resource intensive and requires sufficient bandwidth and storage to accommodate the full size of the block chain. For Bitcoin to remain secure, enough people should keep using full node clients because they perform the task of validating and relaying transactions." + synctxt1: "Long synchronization time is only required with full node clients like Bitcoin Core. Technically speaking, synchronizing is the process of downloading and verifying all previous Bitcoin transactions on the network. For some Bitcoin clients to calculate the spendable balance of your Bitcoin wallet and make new transactions, it needs to be aware of all previous transactions. This step can be resource intensive and requires sufficient bandwidth and storage to accommodate the full size of the blockchain. For Bitcoin to remain secure, enough people should keep using full node clients because they perform the task of validating and relaying transactions." mining: "Mining" whatismining: "What is Bitcoin mining?" whatisminingtxt1: "Mining is the process of spending computing power to process transactions, secure the network, and keep everyone in the system synchronized together. It can be perceived like the Bitcoin data center except that it has been designed to be fully decentralized with miners operating in all countries and no individual having control over the network. This process is referred to as \"mining\" as an analogy to gold mining because it is also a temporary mechanism used to issue new bitcoins. Unlike gold mining, however, Bitcoin mining provides a reward in exchange for useful services required to operate a secure payment network. Mining will still be required after the last bitcoin is issued." howminingworks: "How does Bitcoin mining work?" howminingworkstxt1: "Anybody can become a Bitcoin miner by running software with specialized hardware. Mining software listens for transactions broadcast through the peer-to-peer network and performs appropriate tasks to process and confirm these transactions. Bitcoin miners perform this work because they can earn transaction fees paid by users for faster transaction processing, and newly created bitcoins issued into existence according to a fixed formula." - howminingworkstxt2: "For new transactions to be confirmed, they need to be included in a block along with a mathematical proof of work. Such proofs are very hard to generate because there is no way to create them other than by trying billions of calculations per second. This requires miners to perform these calculations before their blocks are accepted by the network and before they are rewarded. As more people start to mine, the difficulty of finding valid blocks is automatically increased by the network to ensure that the average time to find a block remains equal to 10 minutes. As a result, mining is a very competitive business where no individual miner can control what is included in the block chain." - howminingworkstxt3: "The proof of work is also designed to depend on the previous block to force a chronological order in the block chain. This makes it exponentially difficult to reverse previous transactions because this requires the recalculation of the proofs of work of all the subsequent blocks. When two blocks are found at the same time, miners work on the first block they receive and switch to the longest chain of blocks as soon as the next block is found. This allows mining to secure and maintain a global consensus based on processing power." + howminingworkstxt2: "For new transactions to be confirmed, they need to be included in a block along with a mathematical proof of work. Such proofs are very hard to generate because there is no way to create them other than by trying billions of calculations per second. This requires miners to perform these calculations before their blocks are accepted by the network and before they are rewarded. As more people start to mine, the difficulty of finding valid blocks is automatically increased by the network to ensure that the average time to find a block remains equal to 10 minutes. As a result, mining is a very competitive business where no individual miner can control what is included in the blockchain." + howminingworkstxt3: "The proof of work is also designed to depend on the previous block to force a chronological order in the blockchain. This makes it exponentially difficult to reverse previous transactions because this requires the recalculation of the proofs of work of all the subsequent blocks. When two blocks are found at the same time, miners work on the first block they receive and switch to the longest chain of blocks as soon as the next block is found. This allows mining to secure and maintain a global consensus based on processing power." howminingworkstxt4: "Bitcoin miners are neither able to cheat by increasing their own reward nor process fraudulent transactions that could corrupt the Bitcoin network because all Bitcoin nodes would reject any block that contains invalid data as per the rules of the Bitcoin protocol. Consequently, the network remains secure even if not all Bitcoin miners can be trusted." miningwaste: "Isn't Bitcoin mining a waste of energy?" miningwastetxt1: "Spending energy to secure and operate a payment system is hardly a waste. Like any other payment service, the use of Bitcoin entails processing costs. Services necessary for the operation of currently widespread monetary systems, such as banks, credit cards, and armored vehicles, also use a lot of energy. Although unlike Bitcoin, their total energy consumption is not transparent and cannot be as easily measured." miningwastetxt2: "Bitcoin mining has been designed to become more optimized over time with specialized hardware consuming less energy, and the operating costs of mining should continue to be proportional to demand. When Bitcoin mining becomes too competitive and less profitable, some miners choose to stop their activities. Furthermore, all energy expended mining is eventually transformed into heat, and the most profitable miners will be those who have put this heat to good use. An optimally efficient mining network is one that isn't actually consuming any extra energy. While this is an ideal, the economics of mining are such that miners individually strive toward it." miningsecure: "How does mining help secure Bitcoin?" - miningsecuretxt1: "Mining creates the equivalent of a competitive lottery that makes it very difficult for anyone to consecutively add new blocks of transactions into the block chain. This protects the neutrality of the network by preventing any individual from gaining the power to block certain transactions. This also prevents any individual from replacing parts of the block chain to roll back their own spends, which could be used to defraud other users. Mining makes it exponentially more difficult to reverse a past transaction by requiring the rewriting of all blocks following this transaction." + miningsecuretxt1: "Mining creates the equivalent of a competitive lottery that makes it very difficult for anyone to consecutively add new blocks of transactions into the blockchain. This protects the neutrality of the network by preventing any individual from gaining the power to block certain transactions. This also prevents any individual from replacing parts of the blockchain to roll back their own spends, which could be used to defraud other users. Mining makes it exponentially more difficult to reverse a past transaction by requiring the rewriting of all blocks following this transaction." miningstart: "What do I need to start mining?" miningstarttxt1: "In the early days of Bitcoin, anyone could find a new block using their computer's CPU. As more and more people started mining, the difficulty of finding new blocks increased greatly to the point where the only cost-effective method of mining today is using specialized hardware. You can visit BitcoinMining.com for more information." security: "Security" @@ -506,7 +506,7 @@ en: hackedtxt1: "The rules of the protocol and the cryptography used for Bitcoin are still working years after its inception, which is a good indication that the concept is well designed. However, security flaws have been found and fixed over time in various software implementations. Like any other form of software, the security of Bitcoin software depends on the speed with which problems are found and fixed. The more such issues are discovered, the more Bitcoin is gaining maturity." hackedtxt2: "There are often misconceptions about thefts and security breaches that happened on diverse exchanges and businesses. Although these events are unfortunate, none of them involve Bitcoin itself being hacked, nor imply inherent flaws in Bitcoin; just like a bank robbery doesn't mean that the dollar is compromised. However, it is accurate to say that a complete set of good practices and intuitive security solutions is needed to give users better protection of their money, and to reduce the general risk of theft and loss. Over the course of the last few years, such security features have quickly developed, such as wallet encryption, offline wallets, hardware wallets, and multi-signature transactions." collude: "Could users collude against Bitcoin?" - colludetxt1: "It is not possible to change the Bitcoin protocol that easily. Any Bitcoin client that doesn't comply with the same rules cannot enforce their own rules on other users. As per the current specification, double spending is not possible on the same block chain, and neither is spending bitcoins without a valid signature. Therefore, It is not possible to generate uncontrolled amounts of bitcoins out of thin air, spend other users' funds, corrupt the network, or anything similar." + colludetxt1: "It is not possible to change the Bitcoin protocol that easily. Any Bitcoin client that doesn't comply with the same rules cannot enforce their own rules on other users. As per the current specification, double spending is not possible on the same blockchain, and neither is spending bitcoins without a valid signature. Therefore, It is not possible to generate uncontrolled amounts of bitcoins out of thin air, spend other users' funds, corrupt the network, or anything similar." colludetxt2: "However, powerful miners could arbitrarily choose to block or reverse recent transactions. A majority of users can also put pressure for some changes to be adopted. Because Bitcoin only works correctly with a complete consensus between all users, changing the protocol can be very difficult and requires an overwhelming majority of users to adopt the changes in such a way that remaining users have nearly no choice but to follow. As a general rule, it is hard to imagine why any Bitcoin user would choose to adopt any change that could compromise their own money." quantum: "Is Bitcoin vulnerable to quantum computing?" quantumtxt1: "Yes, most systems relying on cryptography in general are, including traditional banking systems. However, quantum computers don't yet exist and probably won't for a while. In the event that quantum computing could be an imminent threat to Bitcoin, the protocol could be upgraded to use post-quantum algorithms. Given the importance that this update would have, it can be safely expected that it would be highly reviewed by developers and adopted by all Bitcoin users." @@ -549,12 +549,12 @@ en: intro: "This is a question that often causes confusion. Here's a quick explanation!" basics: "The basics for a new user" basicstxt1: "As a new user, you can get started with Bitcoin without understanding the technical details. Once you have installed a Bitcoin wallet on your computer or mobile phone, it will generate your first Bitcoin address and you can create more whenever you need one. You can disclose your addresses to your friends so that they can pay you or vice versa. In fact, this is pretty similar to how email works, except that Bitcoin addresses should only be used once." - balances: "Balances - block chain" - balancestxt: "The block chain is a shared public ledger on which the entire Bitcoin network relies. All confirmed transactions are included in the block chain. This way, Bitcoin wallets can calculate their spendable balance and new transactions can be verified to be spending bitcoins that are actually owned by the spender. The integrity and the chronological order of the block chain are enforced with cryptography." + balances: "Balances - blockchain" + balancestxt: "The blockchain is a shared public ledger on which the entire Bitcoin network relies. All confirmed transactions are included in the blockchain. This way, Bitcoin wallets can calculate their spendable balance and new transactions can be verified to be spending bitcoins that are actually owned by the spender. The integrity and the chronological order of the blockchain are enforced with cryptography." transactions: "Transactions - private keys" - transactionstxt: "A transaction is a transfer of value between Bitcoin wallets that gets included in the block chain. Bitcoin wallets keep a secret piece of data called a private key or seed, which is used to sign transactions, providing a mathematical proof that they have come from the owner of the wallet. The signature also prevents the transaction from being altered by anybody once it has been issued. All transactions are broadcast between users and usually begin to be confirmed by the network in the following 10 minutes, through a process called mining." + transactionstxt: "A transaction is a transfer of value between Bitcoin wallets that gets included in the blockchain. Bitcoin wallets keep a secret piece of data called a private key or seed, which is used to sign transactions, providing a mathematical proof that they have come from the owner of the wallet. The signature also prevents the transaction from being altered by anybody once it has been issued. All transactions are broadcast between users and usually begin to be confirmed by the network in the following 10 minutes, through a process called mining." processing: "Processing - mining" - processingtxt: "Mining is a distributed consensus system that is used to confirm waiting transactions by including them in the block chain. It enforces a chronological order in the block chain, protects the neutrality of the network, and allows different computers to agree on the state of the system. To be confirmed, transactions must be packed in a block that fits very strict cryptographic rules that will be verified by the network. These rules prevent previous blocks from being modified because doing so would invalidate all following blocks. Mining also creates the equivalent of a competitive lottery that prevents any individual from easily adding new blocks consecutively in the block chain. This way, no individuals can control what is included in the block chain or replace parts of the block chain to roll back their own spends." + processingtxt: "Mining is a distributed consensus system that is used to confirm waiting transactions by including them in the blockchain. It enforces a chronological order in the blockchain, protects the neutrality of the network, and allows different computers to agree on the state of the system. To be confirmed, transactions must be packed in a block that fits very strict cryptographic rules that will be verified by the network. These rules prevent previous blocks from being modified because doing so would invalidate all following blocks. Mining also creates the equivalent of a competitive lottery that prevents any individual from easily adding new blocks consecutively in the blockchain. This way, no individuals can control what is included in the blockchain or replace parts of the blockchain to roll back their own spends." readmore: "Going down the rabbit hole" readmoretxt: "This is only a very short and concise summary of the system. If you want to get into the details, you can read the original paper that describes the system's design, read the developer documentation, and explore the Bitcoin wiki." index: @@ -755,18 +755,18 @@ en: bittxt: "Bit is a common unit used to designate a sub-unit of a bitcoin - 1,000,000 bits is equal to 1 bitcoin (BTC or B⃦). This unit is usually more convenient for pricing tips, goods and services." bitcoin: "Bitcoin" bitcointxt: "Bitcoin - with capitalization, is used when describing the concept of Bitcoin, or the entire network itself. e.g. \"I was learning about the Bitcoin protocol today.\"
bitcoin - without capitalization, is used to describe bitcoins as a unit of account. e.g. \"I sent ten bitcoins today.\"; it is also often abbreviated BTC or XBT." - blockchain: "Block Chain" - blockchaintxt: "The block chain is a public record of Bitcoin transactions in chronological order. The block chain is shared between all Bitcoin users. It is used to verify the permanence of Bitcoin transactions and to prevent double spending." + blockchain: "Blockchain" + blockchaintxt: "The blockchain is a public record of Bitcoin transactions in chronological order. The blockchain is shared between all Bitcoin users. It is used to verify the permanence of Bitcoin transactions and to prevent double spending." block: "Block" - blocktxt: "A block is a record in the block chain that contains and confirms many waiting transactions. Roughly every 10 minutes, on average, a new block including transactions is appended to the block chain through mining." + blocktxt: "A block is a record in the blockchain that contains and confirms many waiting transactions. Roughly every 10 minutes, on average, a new block including transactions is appended to the blockchain through mining." btc: "BTC" btctxt: "BTC is a common unit used to designate one bitcoin (B⃦)." confirmation: "Confirmation" confirmationtxt: "Confirmation means that a transaction has been processed by the network and is highly unlikely to be reversed. Transactions receive a confirmation when they are included in a block and for each subsequent block. Even a single confirmation can be considered secure for low value transactions, although for larger amounts like 1000 US$, it makes sense to wait for 6 confirmations or more. Each confirmation exponentially decreases the risk of a reversed transaction." cryptography: "Cryptography" - cryptographytxt: "Cryptography is the branch of mathematics that lets us create mathematical proofs that provide high levels of security. Online commerce and banking already uses cryptography. In the case of Bitcoin, cryptography is used to make it impossible for anybody to spend funds from another user's wallet or to corrupt the block chain. It can also be used to encrypt a wallet, so that it cannot be used without a password." + cryptographytxt: "Cryptography is the branch of mathematics that lets us create mathematical proofs that provide high levels of security. Online commerce and banking already uses cryptography. In the case of Bitcoin, cryptography is used to make it impossible for anybody to spend funds from another user's wallet or to corrupt the blockchain. It can also be used to encrypt a wallet, so that it cannot be used without a password." doublespend: "Double Spend" - doublespendtxt: "If a malicious user tries to spend their bitcoins to two different recipients at the same time, this is double spending. Bitcoin mining and the block chain are there to create a consensus on the network about which of the two transactions will confirm and be considered valid." + doublespendtxt: "If a malicious user tries to spend their bitcoins to two different recipients at the same time, this is double spending. Bitcoin mining and the blockchain are there to create a consensus on the network about which of the two transactions will confirm and be considered valid." hashrate: "Hash Rate" hashratetxt: "The hash rate is the measuring unit of the processing power of the Bitcoin network. The Bitcoin network must make intensive mathematical operations for security purposes. When the network reached a hash rate of 10 Th/s, it meant it could make 10 trillion calculations per second." mining: "Mining" @@ -778,7 +778,7 @@ en: signature: "Signature" signaturetxt: "A cryptographic signature is a mathematical mechanism that allows someone to prove ownership. In the case of Bitcoin, a Bitcoin wallet and its private key(s) are linked by some mathematical magic. When your Bitcoin software signs a transaction with the appropriate private key, the whole network can see that the signature matches the bitcoins being spent. However, there is no way for the world to guess your private key to steal your hard-earned bitcoins." wallet: "Wallet" - wallettxt: "A Bitcoin wallet is loosely the equivalent of a physical wallet on the Bitcoin network. The wallet actually contains your private key(s) which allow you to spend the bitcoins allocated to it in the block chain. Each Bitcoin wallet can show you the total balance of all bitcoins it controls and lets you pay a specific amount to a specific person, just like a real wallet. This is different to credit cards where you are charged by the merchant." + wallettxt: "A Bitcoin wallet is loosely the equivalent of a physical wallet on the Bitcoin network. The wallet actually contains your private key(s) which allow you to spend the bitcoins allocated to it in the blockchain. Each Bitcoin wallet can show you the total balance of all bitcoins it controls and lets you pay a specific amount to a specific person, just like a real wallet. This is different to credit cards where you are charged by the merchant." you-need-to-know: title: "Some things you need to know - Bitcoin" pagetitle: "Some things you need to know" @@ -863,7 +863,7 @@ en: address: address bit: bit bitcoin: bitcoin - blockchain: block-chain + blockchain: blockchain block: block btc: btc confirmation: confirmation diff --git a/_translations/es.yml b/_translations/es.yml index e284e6d972..581fb07e3f 100644 --- a/_translations/es.yml +++ b/_translations/es.yml @@ -261,7 +261,7 @@ es: whocontrolstxt1: "De la misma manera que nadie controla la tecnología detrás del correo electrónico, Bitcoin tampoco tiene propietarios. Bitcoin lo controlan todos los usuarios de Bitcoin del mundo. Aunque los programadores mejoran el software, no pueden forzar un cambio en el protocolo de Bitcoin porque todos los demás usuarios son libres de elegir el software y la versión que quieran. Para que sigan siendo compatibles entre sí, todos los usuarios necesitan utilizar software que cumpla con las mismas reglas. Bitcoin sólo puede funcionar correctamente si hay consenso entre todos los usuarios. Por lo tanto, todos los usuarios y programadores tienen un gran aliciente en proteger dicho consenso." howitworks: "¿Cómo funciona Bitcoin?" howitworkstxt1: "Desde la perspectiva del usuario, Bitcoin no es más que una aplicación móvil o de escritorio que provee un monedero Bitcoin personal y permite al usuario enviar y recibir bitcoins con el. Así es como funciona Bitcoin para la mayoría de los usuarios." - howitworkstxt2: "Detrás de las cámaras, la red Bitcoin comparte una contabilidad pública llamada \"block chain\". Esta contabilidad contiene cada transacción procesada, permitiendo verificar la validez de cada transacción. La autenticidad de cada transacción esta protegida por firmas digitales correspondientes a las direcciones de envío, permitiendo a todos los usuarios tener control total al enviar Bitcoins desde sus direcciones Bitcoin. Además, cualquiera puede procesar una transacción usando el poder computacional de hardware especializado y conseguir una recompensa en Bitcoins por este servicio. Esto es comúnmente llamado \"mining\" o minería. Para aprender más sobre Bitcoin, puedes consultar la página dedicada y el documento original." + howitworkstxt2: "Detrás de las cámaras, la red Bitcoin comparte una contabilidad pública llamada \"blockchain\". Esta contabilidad contiene cada transacción procesada, permitiendo verificar la validez de cada transacción. La autenticidad de cada transacción esta protegida por firmas digitales correspondientes a las direcciones de envío, permitiendo a todos los usuarios tener control total al enviar Bitcoins desde sus direcciones Bitcoin. Además, cualquiera puede procesar una transacción usando el poder computacional de hardware especializado y conseguir una recompensa en Bitcoins por este servicio. Esto es comúnmente llamado \"mining\" o minería. Para aprender más sobre Bitcoin, puedes consultar la página dedicada y el documento original." used: "¿Lo utiliza realmente la gente?" usedtxt1: "Sí. Existe un número creciente de negocios e individuos usando Bitcoin. Esto incluye negocios tradicionales como restaurantes, casas, bufetes de abogados y servicios de Internet populares como Namecheap, Wordpress, Reddit y Flattr. Aunque Bitcoin sigue siendo un fenómeno relativamente nuevo, esta creciendo rápido. A finales de Agosto de 2013, el valor de todos los bitcoins en circulación superaba los 1.5 billones de dólares y cada día se intercambiaban el equivalente a millones de dólares en bitcoins." acquire: "¿Cómo se adquieren bitcoins?" @@ -420,7 +420,7 @@ es: basics: "Lo esencial para un usuario nuevo" basicstxt1: "Como usuario nuevo, usted puede empezar con Bitcoin sin entender los detalles técnicos. Una vez usted tenga instalado un monedero en su ordenador o dispositivo móvil, se generará su primera dirección Bitcoin y podrá crear más cuando lo necesite. Puede dar su dirección a sus amigos para que le paguen o viceversa. De hecho, es similar a como funciona el correo electrónico, excepto que las direcciones Bitcoin solamente deberían ser usadas una única vez." balances: "Balances - cadena de bloques" - balancestxt: "La cadena de bloques o \"block chain\" es una contabilidad pública compartida en la que se basa toda la red Bitcoin. Todas las transacciones confirmadas se incluyen en la cadena de bloques. De esta manera los monederos Bitcoin pueden calcular su saldo gastable y las nuevas transacciones pueden ser verificadas, asegurando que el cobro se esta haciendo al que realiza el pago. La integridad y el orden cronológico de la cadena de bloques se hacen cumplir con criptografía." + balancestxt: "La cadena de bloques o \"blockchain\" es una contabilidad pública compartida en la que se basa toda la red Bitcoin. Todas las transacciones confirmadas se incluyen en la cadena de bloques. De esta manera los monederos Bitcoin pueden calcular su saldo gastable y las nuevas transacciones pueden ser verificadas, asegurando que el cobro se esta haciendo al que realiza el pago. La integridad y el orden cronológico de la cadena de bloques se hacen cumplir con criptografía." transactions: "Transacciones - llaves privadas" transactionstxt: "Una transacción es una transferencia de valores entre monederos Bitcoin que será incluida en la cadena de bloques. Los monederos Bitcoin disponen de un fragmento secreto llamado clave privada, utilizada para firmar las operaciones, proporcionando una prueba matemática de que la transacción está hecha por el propietario del monedero. La firma también evita que la transacción no sea alterada por alguien una vez ésta ha sido emitida. Todas las transacciones son difundidas entre los usuarios y por lo general empiezan a ser confirmadas por la red en los 10 minutos siguientes a través de un proceso llamado minería." processing: "Procesamiento - minería" diff --git a/_translations/fa.yml b/_translations/fa.yml index aceccca8c0..4c675cba1d 100644 --- a/_translations/fa.yml +++ b/_translations/fa.yml @@ -681,7 +681,7 @@ fa: address: address bit: bit bitcoin: bitcoin - blockchain: block-chain + blockchain: blockchain block: block btc: btc confirmation: confirmation diff --git a/_translations/hi.yml b/_translations/hi.yml index ba9509e4a1..0217ceaaaa 100644 --- a/_translations/hi.yml +++ b/_translations/hi.yml @@ -233,7 +233,7 @@ hi: sourcecode: "स्रोत कोड प्राप्त करें" versionhistory: "संस्करण इतिहास दिखाएं" notelicense: "Bitcoin कोर समुदाय संचालित है मुफ्त सॉफ्टवेयर परियोजना MIT लाइसेंस के तरत जारी है। " - notesync: "Bitcoin कोर प्रारंभिक सिंक पर लंबा समय लग सकता है। पूरे block chain size (over 20GB) के लिए क्या आपके पास पर्याप्त बैंडविड्थ और भंडारण है यह सुनिश्चित करें। यदि आपको टॉरेंट फ़ाइल डाउनलोड करना आता है तो, सॉफ्टवेयर शुरू करने से पहले bootstrap.dat (ब्लॉक श्रृंखला के पिछली नकल) को Bitcoin कोर डेटा निर्देशिका में डाल कर आप इस प्रतिक्रिया को तेज़ कर सकते हैं" + notesync: "Bitcoin कोर प्रारंभिक सिंक पर लंबा समय लग सकता है। पूरे blockchain size (over 20GB) के लिए क्या आपके पास पर्याप्त बैंडविड्थ और भंडारण है यह सुनिश्चित करें। यदि आपको टॉरेंट फ़ाइल डाउनलोड करना आता है तो, सॉफ्टवेयर शुरू करने से पहले bootstrap.dat (ब्लॉक श्रृंखला के पिछली नकल) को Bitcoin कोर डेटा निर्देशिका में डाल कर आप इस प्रतिक्रिया को तेज़ कर सकते हैं" patient: "आपको धैर्य रखना होगा" events: title: "सम्मेलन और घटनाए - Bitcoin" @@ -712,7 +712,7 @@ hi: address: address bit: bit bitcoin: bitcoin - blockchain: block-chain + blockchain: blockchain block: block btc: btc confirmation: confirmation diff --git a/_translations/it.yml b/_translations/it.yml index 315baa85d6..84040b7be1 100644 --- a/_translations/it.yml +++ b/_translations/it.yml @@ -238,7 +238,7 @@ it: source: "Codice sorgente" versionhistory: "Mostra la cronologia delle versioni" notelicense: "Bitcoin Core è un progetto libero e open-source portato avanti dalla comunità e rilasciato sotto la licenza MIT." - notesync: "La sincronizzazione iniziale di Bitcoin Core richiede tempo e il download di molti dati. Dovresti essere sicuro di avere una linea abbastanza veloce e spazio sufficiente per scaricare la block chain completa (oltre 20GB). Se hai un buona linea internet, puoi aiutare a rafforzare la rete tenendo avviato il programma Bitcoin Core sul tuo PC e aprendo la porta 8333 del tuo modem." + notesync: "La sincronizzazione iniziale di Bitcoin Core richiede tempo e il download di molti dati. Dovresti essere sicuro di avere una linea abbastanza veloce e spazio sufficiente per scaricare la blockchain completa (oltre 20GB). Se hai un buona linea internet, puoi aiutare a rafforzare la rete tenendo avviato il programma Bitcoin Core sul tuo PC e aprendo la porta 8333 del tuo modem." full_node_guide: "Leggere la guida full node per i dettagli." patient: "Controlla il tuo spazio e la banda" events: @@ -265,7 +265,7 @@ it: whocontrolstxt1: "Nessuno possiede la rete Bitcoin, così come nessuno possiede la tecnologia che sta dietro le e-mail. Bitcoin è controllata da tutti gli utenti Bitcoin in giro per il mondo. Mentre gli sviluppatori stanno migliorando il software, loro non possono forzare un cambiamento nel protocollo Bitcoin, perché tutti gli utenti sono liberi di scegliere quale software e versione usare. Per restare compatibili con gli altri, tutti gli utenti devono usare software conformi alle stesse regole. Bitcoin può lavorare correttamente solo con un consenso completo tra tutti gli utenti. Quindi, tutti gli utenti e gli sviluppatori hanno un forte incentivo a proteggere questo consenso." howitworks: "Come funziona Bitcoin?" howitworkstxt1: "Dal punto di vista dell'utente, Bitcoin non è altro che un'applicazione per cellulare/tablet o un programma per computer che fornisce un portafoglio personale per accedere ai bitcoin, e consente ad un utente di inviare e ricevere bitcoin con loro. E' così che Bitcoin funziona per la maggioranza degli utenti. " - howitworkstxt2: "Dietro le scene, la rete Bitcoin sta condividendo un libro mastro pubblico chiamato \"block chain\". Questo libro mastro contiene tutte le transazioni che sono state elaborate, permettendo al computer degli utenti di verificare la validità di ogni transazione. L'autenticità di ogni transazione è protetta da firme digitali che corrispondono all'indirizzo del mittente, permettendo a tutti gli utenti di avere pieno controllo sui bitcoin inviati dai loro indirizzi Bitcoin personali. In più, chiunque può processare transazioni usando la potenza computazionale dell'hardware specializzato ed ottenere un premio in bitcoin per questo servizio. Questo viene spesso chiamato \"mining\". Per sapere di più su Bitcoin, puoi consultare la pagina dedicata e il foglio originale." + howitworkstxt2: "Dietro le scene, la rete Bitcoin sta condividendo un libro mastro pubblico chiamato \"blockchain\". Questo libro mastro contiene tutte le transazioni che sono state elaborate, permettendo al computer degli utenti di verificare la validità di ogni transazione. L'autenticità di ogni transazione è protetta da firme digitali che corrispondono all'indirizzo del mittente, permettendo a tutti gli utenti di avere pieno controllo sui bitcoin inviati dai loro indirizzi Bitcoin personali. In più, chiunque può processare transazioni usando la potenza computazionale dell'hardware specializzato ed ottenere un premio in bitcoin per questo servizio. Questo viene spesso chiamato \"mining\". Per sapere di più su Bitcoin, puoi consultare la pagina dedicata e il foglio originale." used: "Bitcoin è realmente usato dalle persone?" usedtxt1: "Sì. C'è un numero crescente di aziende e privati che utilizza Bitcoin. Questo include imprese di mattoni e malta come ristoranti, appartamenti, studi legali e servizi online popolari come Namecheap, WordPress e Reddit. Anche se Bitcoin rimane un fenomeno relativamente nuovo, sta crescendo velocemente. Alla fine dell'Agosto 2013, il valore di tutti i bitcoin in circolazione superava 1.5 miliardi di $ americani con milioni di dollari in forma di bitcoin scambiati quotidianamente." acquire: "Come acquisire i bitcoin?" @@ -281,7 +281,7 @@ it: advantagesli2: "Costi molto bassi - I pagamenti Bitcoin sono correntemente processati senza costi oppure con addebiti estremamente bassi. Gli utenti possono accettare di sostenere dei costi, quando effettuano una transazione, per ricevere priorità di elaborazione, che si traduce in conferme più veloci della transazione. Inoltre, esistono dei programmi commerciali, ideati per assistere i commercianti nell'elaborazione delle transazioni, convertendo bitcoin in moneta e depositando fondi direttamente nei conti bancari dei commercianti quotidianamente. Poiché questi servizi sono basati su Bitcoin, possono essere offerti a costi molto più bassi di quelli offerti con PayPal o dalle carte di credito." advantagesli3: "Meno rischi per i commercianti - Le transazioni Bitcoin sono sicure, irreversibili e non contengono dati sensibili o informazioni personali del cliente. Ciò protegge i commercianti da perdite causate da frodi o da chargeback fraudolenti e non c'è bisogno della conformità PCI. I commercianti si possono facilmente espandere verso nuovi mercati dove carte di credito non sono disponibili o il tasso di frodi è inaccettabilmente alto. I risultati della rete sono costi più bassi, mercati più ampi e costi amministrativi più bassi. " advantagesli4: "Sicurezza e controllo - Gli utenti di Bitcoin controllano totalmente le proprie transazioni; i commercianti non possono forzare cambiamenti indesiderati o inosservati, così come avviene con gli altri metodi di pagamento. I pagamenti di Bitcoin possono effettuarsi senza alcuna informazione personale connessa alla transazione. Questo offre una grande protezione contro il furto d'identità. Gli utenti Bitcoin possono anche proteggere il proprio denaro facendo ricorso al backup o criptando i dati." - advantagesli5: "Trasparente e neutrale - Tutte le informazioni riguardanti il magazzino di denaro Bitcoin sono prontamente disponibili sulla block chain a chiunque, per verifica ed utilizzo in tempo reale. Nessun privato o organizzazione può controllare o manipolare il protocollo Bitcoin perché è sicuro dal punto di vista crittografico. Questo permette al nucleo di Bitcoin di essere considerato sicuro per essere completamente neutrale, trasparente e prevedibile." + advantagesli5: "Trasparente e neutrale - Tutte le informazioni riguardanti il magazzino di denaro Bitcoin sono prontamente disponibili sulla blockchain a chiunque, per verifica ed utilizzo in tempo reale. Nessun privato o organizzazione può controllare o manipolare il protocollo Bitcoin perché è sicuro dal punto di vista crittografico. Questo permette al nucleo di Bitcoin di essere considerato sicuro per essere completamente neutrale, trasparente e prevedibile." disadvantages: "Quali sono gli svantaggi di Bitcoin?" disadvantagesli1: "Grado di accettazione - Molte persone sono ancora inconsapevoli dell'esistenza di Bitcoin. Ogni giorno, sempre più aziende accettano i bitcoin, in quanto vogliono trarne dei vantaggi, ma la lista resta piccola e ha ancora bisogno di crescere, per poter beneficiare degli effetti della rete." disadvantagesli2: "Volatilità - Il valore totale dei bitcoin in circolazione e il numero di aziende che usano Bitcoin sono molto piccoli rispetto a quelli che potrebbero essere. Pertanto, piccoli eventi, scambi o attività speculative potrebbero variarne significativamente il prezzo. In teoria, questa volatilità diminuirà quando il mercato di Bitcoin e le tecnologie saranno mature. Prima d'ora, il mondo non ha mai assistito al lancio di una nuova valuta, quindi è veramente difficile (ed interessante) immaginare che cosa succederà." @@ -297,7 +297,7 @@ it: anonymoustxt1: "Bitcoin è programmato per consentire ai propri utenti di inviare e ricevere pagamenti ad un livello accettabile di privacy, così come ogni altra forma di denaro. Tuttavia, Bitcoin non è anonimo e non può offrire lo stesso livello di privacy, del denaro liquido. L'utilizzo di Bitcoin lascia tracce pubbliche consistenti. Vari meccanismi sono destinati a proteggere la privacy degli utenti, e molti altri sono in fase di sviluppo. Tuttavia, c'è ancora del lavoro da svolgere prima che tali elementi possano essere usati correttamente dalla maggioranza degli utenti Bitcoin. " anonymoustxt2: "Alcune preoccupazioni sono sorte in merito alle transazioni private con Bitcoin che potrebbero essere utilizzate per scopi illegali. Tuttavia, vale la pena notare che Bitcoin sarà indubbiamente soggetto a simili regolamentazioni attualmente in vigore all'interno degli esistenti sistemi finanziari. Bitcoin non può essere del denaro contante, e non è tale da impedire indagini criminali. inoltre, Bitcoin è progettato per prevenire un ampio raggio di crimini finanziari." lost: "Che cosa succede se vengono persi dei bitcoin?" - losttxt1: "Quando un utente perde il suo portafoglio, questo comporta rimuovere il denaro dalla circolazione. I bitcoin persi restano nella block chain proprio come qualsiasi altro bitcoin. Tuttavia, i bitcoin persi restano giacenti per sempre, perché non c'è alcun modo di trovare la chiave(i) privata, che consentirebbe loro di tornare ad essere spesi. A causa della legge della domanda e offerta, quando ancor meno bitcoin risultano disponibili, quelli che restano avranno una maggiore richiesta e il loro valore aumenterà." + losttxt1: "Quando un utente perde il suo portafoglio, questo comporta rimuovere il denaro dalla circolazione. I bitcoin persi restano nella blockchain proprio come qualsiasi altro bitcoin. Tuttavia, i bitcoin persi restano giacenti per sempre, perché non c'è alcun modo di trovare la chiave(i) privata, che consentirebbe loro di tornare ad essere spesi. A causa della legge della domanda e offerta, quando ancor meno bitcoin risultano disponibili, quelli che restano avranno una maggiore richiesta e il loro valore aumenterà." scale: "Bitcoin potrà arrivare ad essere uno dei maggiori sistemi di pagamento?" scaletxt1: "La rete Bitcoin potrebbe già elaborare un maggiore numero di transazioni al secondo, rispetto a quanto riesce a fare oggi. Tuttavia, non è del tutto pronta per salire al livello superiore offerto dalle maggiori reti delle carte di credito. Stiamo lavorando per diminuire le attuali limitazioni, ed i futuri requisiti sono ben conosciuti. Fin dall'inizio, ogni aspetto della rete Bitcoin è in continua fase di maturazione, ottimizzazione e specializzazione, e dovrebbe restare così per alcuni anni a venire. Con la crescita del traffico, sempre più utenti Bitcoin dovrebbero utilizzare dei client leggeri, e i nodi di rete dovrebbero diventare un servizio più specializzato. Per ulteriori informazioni, vedi lapagina dedicata alla Scalability su Wiki." legal: "Legale" @@ -357,20 +357,20 @@ it: poweredoff: "Che cosa succede se ricevo un bitcoin quando il computer è spento ?" poweredofftxt1: "Questo funziona bene. I bitcoin appariranno la prossima volta che cominci l'applicazione del tuo portafoglio. In realtà, i bitcoin non vengono ricevuti dal software sul tuo computer, sono allegati ad un registro pubblico, che viene condiviso da tutti i dispositivi sulla rete. Se vi inviano dei bitcoin quando il programma client del tuo portafoglio non è in funzione, e poi lo lanci in seguito, caricherà dei blocchi e raccoglierà qualsiasi transazione di cui non era consapevole, ed i bitcoin finiranno con apparire proprio nel modo in cui sono stati ricevuti in tempo reale. Il tuo portafoglio è necessario solo quando desideri spendere i bitcoin. " sync: "Che cosa significa \"sincronizzando\" e perchè impiega così tanto tempo" - synctxt1: "Lungo tempo di sincronizzazione viene richiesto solo con i client full node come Bitcoin Core. Tecnicamente parlando, la sincronizzazione è il processo di download e verifica di tutte le precedenti transazioni Bitcoin sulla rete. Per alcuni client di Bitcoin, per calcolare il bilancio spendibile del tuo portafoglio Bitcoin ed eseguire nuove transazioni, occorre essere consapevoli di tutte le precedenti transazioni. Questa fase può essere una grande risorsa e richiede sufficiente larghezza di banda e capienza per ospitare la grandezza della block chain. Per far sì che Bitcoin resti sicuro, sufficienti utenti dovrebbero continuare ad utilizzare i client full node, perchè hanno la funzionalità di convalidare e trasmettere le transazioni. " + synctxt1: "Lungo tempo di sincronizzazione viene richiesto solo con i client full node come Bitcoin Core. Tecnicamente parlando, la sincronizzazione è il processo di download e verifica di tutte le precedenti transazioni Bitcoin sulla rete. Per alcuni client di Bitcoin, per calcolare il bilancio spendibile del tuo portafoglio Bitcoin ed eseguire nuove transazioni, occorre essere consapevoli di tutte le precedenti transazioni. Questa fase può essere una grande risorsa e richiede sufficiente larghezza di banda e capienza per ospitare la grandezza della blockchain. Per far sì che Bitcoin resti sicuro, sufficienti utenti dovrebbero continuare ad utilizzare i client full node, perchè hanno la funzionalità di convalidare e trasmettere le transazioni. " mining: "Minare-mining" whatismining: "Che cosa è il mining di Bitcoin?" whatisminingtxt1: "Il mining è il processo che utilizza la potenza di calcolo per elaborare le transazioni, rendere sicura la rete e mantenere tutti insieme sincronizzati nel sistema. Si può considerare come il centro dati dei Bitcoin ad eccezione del fatto che è stato progettato per essere totalmente decentralizzato, con minatori che operano in tutte le nazioni senza che nessun individuo abbia il controllo della rete. Questo processo si chiama \"mining\" per un'analogia con l'estrazione dell'oro perchè è un meccanismo temporaneo per l'emissione di nuovi bitcoin. A differenza dell'estrazione dell'oro, però, la produzione di Bitcoin dà un premio in cambio di servizi utili al funzionamento di una rete di pagamenti sicuri. Il mining sarà comunque necessario anche dopo che l'ultimo bitcoin sarà stato estratto." howminingworks: "Come funziona il mining di Bitcoin ?" howminingworkstxt1: "Chiunque può diventare un minatore di Bitcoin utilizzando un software con hardware dedicato. Il software \"ascolta\" le transazioni in corso su una rete peer-to-peer ed esegue una serie di attività al fine di elaborare e confermare queste transazioni. I minatori di Bitcoin svolgono questa attività poiché possono guadagnare le commissioni pagate dagli utenti per ottenere una elaborazione più veloce delle proprie transazioni o anche guadagnare bitcoin appena coniati tramite un algoritmo già noto." - howminingworkstxt2: "Per ottenere la conferma delle nuove transazioni, occorre che vengano incluse in un blocco con una prova di lavoro matematica. Tali prove sono molto difficili da generare, perché non vi è alcun modo se non quello di provare miliardi di calcoli al secondo. Questo richiede che gli estrattori di dati eseguano questi calcoli, prima che i loro blocchi vengano accettati dalla rete e prima che siano assegnati. Quante più persone iniziano a estrarre, tanto più aumenta in modo automatico la difficoltà di trovare blocchi validi da parte della rete, per assicurare che il tempo medio per trovare il blocco resti uguale a 10 minuti. Di conseguenza, l'estrazione è molto competitiva, dove nessun estrattore singolo possa controllare ciò che contiene la block chain. " - howminingworkstxt3: "La prova di lavoro è anche programmata per dipendere dai blocchi precedenti per imporre un ordine cronologico nella block chain. Questo rende esponenzialmente difficile invertire le transazioni precedenti, perché richiede il calcolo delle prove di lavoro di tutti i blocchi successivi. Quando si trovano due blocchi allo stesso tempo, i minatori lavorano sul primo blocco che ricevono, e passano alla più grande block chain, fino a quando non si trova il prossimo blocco. Ciò consente al mining di assicurare e mantenere un consenso globale sulla capacità di elaborazione. " + howminingworkstxt2: "Per ottenere la conferma delle nuove transazioni, occorre che vengano incluse in un blocco con una prova di lavoro matematica. Tali prove sono molto difficili da generare, perché non vi è alcun modo se non quello di provare miliardi di calcoli al secondo. Questo richiede che gli estrattori di dati eseguano questi calcoli, prima che i loro blocchi vengano accettati dalla rete e prima che siano assegnati. Quante più persone iniziano a estrarre, tanto più aumenta in modo automatico la difficoltà di trovare blocchi validi da parte della rete, per assicurare che il tempo medio per trovare il blocco resti uguale a 10 minuti. Di conseguenza, l'estrazione è molto competitiva, dove nessun estrattore singolo possa controllare ciò che contiene la blockchain. " + howminingworkstxt3: "La prova di lavoro è anche programmata per dipendere dai blocchi precedenti per imporre un ordine cronologico nella blockchain. Questo rende esponenzialmente difficile invertire le transazioni precedenti, perché richiede il calcolo delle prove di lavoro di tutti i blocchi successivi. Quando si trovano due blocchi allo stesso tempo, i minatori lavorano sul primo blocco che ricevono, e passano alla più grande blockchain, fino a quando non si trova il prossimo blocco. Ciò consente al mining di assicurare e mantenere un consenso globale sulla capacità di elaborazione. " howminingworkstxt4: "I minatori di Bitcoin non hanno la possibilità di barare aumentando la loro ricompensa, né validare transazioni fraudolente che possano corrompere la rete Bitcoin, perché tutti i nodi Bitcoin respingerebbero ogni blocco contenente dati che non siano validi secondo le regole del protocollo Bitcoin. Perciò la rete resta sicura anche se non tutti i \"minatori\" Bitcoin sono affidabili." miningwaste: "Il mining di Bitcoin non è uno spreco di energia ?" miningwastetxt1: "Spendere energia per assicurare ed operare un sistema di pagamento si rivela difficilmente uno spreco. Come ogni altro sistema di pagamento, l'utilizzo di Bitcoin implica i costi delle operazioni. Anche i servizi necessari per l'operazione degli attuali sistemi monetari, come banche, carte di credito e auto blindate, utilizzano molta energia. Ma a differenza di Bitcoin, il loro consumo totale di energia non è trasparente e non può essere facilmente quantificato. " miningwastetxt2: "Il mining di Bitcoin è stato programmato per ottenere una maggiore ottimizzazione sul tempo, con l'hardware specializzato nel consumare meno energia, e i costi operativi del mining dovrebbero continuare ad essere proporzionati alla domanda. Quando il mining di Bitcoin diventa troppo competitivo e meno propizio, alcuni minatori scelgono di cessare le loro attività. Inoltre, tutta l'energia spesa durante l'operazione di mining, alla fine viene trasformata in calore, e i minatori che trarranno maggiori profitti saranno coloro che faranno buon uso del calore. Un'ottimale rete efficiente del mining è quella che in effetti, non consuma energia extra. Se da un lato si tratta di una situazione ideale, l'economia relativa al mining è quella che i minatori combattono individualmente. " miningsecure: "Come aiuta il mining a tenere sicura la rete Bitcoin ?" - miningsecuretxt1: "La fase di mining crea l'equivalente di una lotteria competitiva, che rende difficile per chiunque aggiungere di conseguenza nuovi blocchi di transazioni all'interno di una block chain. Questo protegge la neutralità della rete, prevenendo che chiunque possa acquisire la capacità di bloccare determinate transazioni. Questo impedisce anche che si sostituiscano parti della block chain per ridurre le proprie spese, il che potrebbe essere utilizzato per defraudare gli altri utenti. Il mining rende esponenzialmente più difficile invertire una transazione passata, richiedendo di riscrivere tutti i block in seguito alla transazione. " + miningsecuretxt1: "La fase di mining crea l'equivalente di una lotteria competitiva, che rende difficile per chiunque aggiungere di conseguenza nuovi blocchi di transazioni all'interno di una blockchain. Questo protegge la neutralità della rete, prevenendo che chiunque possa acquisire la capacità di bloccare determinate transazioni. Questo impedisce anche che si sostituiscano parti della blockchain per ridurre le proprie spese, il che potrebbe essere utilizzato per defraudare gli altri utenti. Il mining rende esponenzialmente più difficile invertire una transazione passata, richiedendo di riscrivere tutti i block in seguito alla transazione. " miningstart: " Che cosa mi occorre per iniziare il mining?" miningstarttxt1: "Nei primi giorni di Bitcoin, chiunque poteva trovare un nuovo blocco, attraverso il proprio CPU del computer. Man mano che sempre più persone iniziarono l'operazione del mining, la difficoltà di trovare nuovi blocchi aumentava enormemente, fino al punto in cui l'unico metodo vantaggioso del mining oggi utilizza un hardware specializzato. Puoi visitare BitcoinMining.com per maggiori informazioni." security: "Sicurezza" @@ -380,7 +380,7 @@ it: hackedtxt1: "Le regole del protocollo e la crittografia utilizzata per Bitcoin sono ancora in funzione anni dopo la sua nascita, il che è una buona indicazione del fatto che il concetto è ben progettato. Tuttavia, delle imperfezioni sulla sicurezza sono state trovate e sistemate nel tempo, in vari software. Come ogni altra forma di software, la sicurezza del software di Bitocoin dipende dalla velocità con cui i problemi vengono scoperti e risolti. Più problematiche vengono scoperte, più Bitcoin acquista maturità. " hackedtxt2: "Spesso ci sono pregiudizi in merito a furti e violazioni di sicurezza, che sono avvenuti in diversi scambi e affari. Sebbene tali eventi siano sfortunati, nessuno di essi ha coinvolto Bitcoin; proprio come una rapina in banca, non significa che il dollaro è compromesso. Tuttavia, è accurato dire che una serie completa di accorgimenti e soluzioni intuitive per migliorare la sicurezza è necessaria per garantire una maggiore protezione del denaro degli utenti, e riduce il rischio generale di furto e perdita. Nel corso degli ultimi anni, tali sistemi di sicurezza si sono rapidamente sviluppati, come il criptaggio del portafoglio, i portafogli offline, i portafogli hardware e le transazioni con varie firme. " collude: "Gli utenti possono colludere contro Bitcoin ?" - colludetxt1: "Non è possibile cambiare il protocollo Bitcoin così facilmente. Ogni client Bitcoin che non è conforme alle stesse regole degli altri non può forzare l'utilizzo delle sue regole rispetto quelle degli altri. Le specifiche correnti non permettono il \"double spending\" (doppia spesa) nella stessa block chain, e nemmeno che i bitcoin siano spesi in mancanza di una firma valida. Pertanto non è possibile generare dal nulla un importo non controllato di bitcoins, non è possibile spendere i fondi di qualcun'altro, e nemmeno corrompere il network in nessun modo." + colludetxt1: "Non è possibile cambiare il protocollo Bitcoin così facilmente. Ogni client Bitcoin che non è conforme alle stesse regole degli altri non può forzare l'utilizzo delle sue regole rispetto quelle degli altri. Le specifiche correnti non permettono il \"double spending\" (doppia spesa) nella stessa blockchain, e nemmeno che i bitcoin siano spesi in mancanza di una firma valida. Pertanto non è possibile generare dal nulla un importo non controllato di bitcoins, non è possibile spendere i fondi di qualcun'altro, e nemmeno corrompere il network in nessun modo." colludetxt2: "Comunque, una maggioranza di minatori potrebbe scegliere arbitrariamente di bloccare o invertire transazioni recenti. Una maggioranza di utenti può inoltre fare pressione per l'adozione di alcuni cambiamenti. Dato che Bitcoin lavora correttamente solo con un completo consenso di tutti gli utenti, cambiare il protocollo potrebbe essere molto difficile e richiederebbe che una larghissima maggioranza di utenti adottasse i cambiamenti, in modo tale che non resti alcuna scelta agli utenti rimanenti, che non potrebbero fare altro che seguire la maggioranza. In linea generale, è difficile immaginare che un qualsiasi utente Bitcoin possa scegliere di adottare qualche cambiamento che potrebbe mettere a rischio il suo stesso denaro." quantum: "Bitcoin è vulnerabile ai computer quantistici?" quantumtxt1: "Si, la maggior parte dei sistemi si affidano alla crittografia, inclusi i sistemi bancari. Tuttavia, i computer quantici non esistono ancora e non esisteranno per un po'. Nell'evenienza che le computazioni quantiche costituiscano una minaccia immediata per Bitcoin, il protocollo sarà aggiornato per l'uso di algoritmi post-quantici. Data l'importanza che avrà questo aggiornamento, ci si può ragionevolmente aspettare che sarà altamente revisionato dagli sviluppatori ed adottato da tutti gli utenti Bitcoin" @@ -426,9 +426,9 @@ it: balances: "Bilanci - catena di blocchi" balancestxt: "La blockchain è un registro publico e condiviso sul quale si basa l'intera rete Bitcoin. Tutte le transazioni confermate sono incluse nella blockchain. In questo modo, i portafogli Bitcoin possono calcolare il loro bilancio spendibile e nuove transazioni possono essere verificate, per poter spendere Bitcoin che sono effettivamente nelle mani di chi li spende. L'integrità e l'ordine cronologico della blockchain sono protetti attraverso crittografia." transactions: "Transazioni - chiavi private" - transactionstxt: "Una transazione è un trasferimento di valori tra portafogli Bitcoin che viene incluso nel block chain. I portafogli di Bitcoin contengono un insieme segreto di dati chiamati a chiave privata o seme, che viene utilizzato per firmare le transazioni fornendo una prova matematica che provengono dal proprietario del portafoglio. La firma impedisce anche che la transazione venga alterata da chiunque, una volta che viene eseguita. Tutte le transazioni avvengono tra utenti e in genere iniziano ad essere confermate dalla rete nei 10 minuti successivi, attraverso un processo chiamato estrazione dei dati." + transactionstxt: "Una transazione è un trasferimento di valori tra portafogli Bitcoin che viene incluso nel blockchain. I portafogli di Bitcoin contengono un insieme segreto di dati chiamati a chiave privata o seme, che viene utilizzato per firmare le transazioni fornendo una prova matematica che provengono dal proprietario del portafoglio. La firma impedisce anche che la transazione venga alterata da chiunque, una volta che viene eseguita. Tutte le transazioni avvengono tra utenti e in genere iniziano ad essere confermate dalla rete nei 10 minuti successivi, attraverso un processo chiamato estrazione dei dati." processing: "Elaborazioni - estrazione" - processingtxt: "Il mining (letteralmente: processo minerario) è un sistema di consenso distribuito utilizzato per confermare le transazioni in attesa includendole nella block chain. Questo mantiene un ordine cronologico nella block chain, protegge la neutralità della rete e consente a diversi computer di concordare sullo stato del sistema. Per essere confermate, le transazioni devono essere impacchettate in un blocco che rispetti regole crittografiche molto rigide, che verranno verificate dalla rete. Queste regole impediscono che qualunque blocco precedente venga modificato, perché ciò invaliderebbe tutti i blocchi successivi. Il mining crea inoltre l'equivalente di una lotteria competitiva che impedisce a chiunque di aggiungere facilmente nuovi blocchi consecutivamente nella block chain. In questo modo nessuno può controllare cosa è incluso nella blockchain o sostituire parti della block chain in modo da riottenere quanto speso." + processingtxt: "Il mining (letteralmente: processo minerario) è un sistema di consenso distribuito utilizzato per confermare le transazioni in attesa includendole nella blockchain. Questo mantiene un ordine cronologico nella blockchain, protegge la neutralità della rete e consente a diversi computer di concordare sullo stato del sistema. Per essere confermate, le transazioni devono essere impacchettate in un blocco che rispetti regole crittografiche molto rigide, che verranno verificate dalla rete. Queste regole impediscono che qualunque blocco precedente venga modificato, perché ciò invaliderebbe tutti i blocchi successivi. Il mining crea inoltre l'equivalente di una lotteria competitiva che impedisce a chiunque di aggiungere facilmente nuovi blocchi consecutivamente nella blockchain. In questo modo nessuno può controllare cosa è incluso nella blockchain o sostituire parti della blockchain in modo da riottenere quanto speso." readmore: "Scendendo nella tana del coniglio" readmoretxt: "Questo è solo un sommario breve e conciso. Se vuoi entrare nei dettagli, puoi leggere il documento originale che descrive il design del sistema, leggere la documentazione dello sviluppatore, ed esplorare la wiki di Bitcoin." index: @@ -621,8 +621,8 @@ it: bittxt: "Il bit è un'unità comune utilizzata per indicare una sotto-unità del bitcoin - 1,000,000 di bit equivalgono a 1 bitcoin (BTC o B⃦). Questa unità è solitamente più appropriata per dare un valore a una mancia o un prezzo a beni e servizi." bitcoin: "Bitcoin" bitcointxt: "Bitcoin - con la maiuscola, è usata quando si descrive il concetto di Bitcoin, o l'intero network stesso. Per esempio \" Oggi stavo studiando il protocollo di Bitcoin.\"
bitcoin - senza maiuscola, è usata per descrivere i bitcoin come un'unità di conto. Per esempio \"Ti ho mandato dieci bitcoin oggi.\"; inoltre, è spesso abbreviato in BTC o XBT." - blockchain: "Block Chain" - blockchaintxt: "La block chain è un registro pubblico delle transazioni Bitcoin in ordine cronologico. La block chain è condivisa tra tutti gli utenti Bitcoin. È utilizzata per verificare la permanenza delle transazioni Bitcoin e per prevenire double spending." + blockchain: "Blockchain" + blockchaintxt: "La blockchain è un registro pubblico delle transazioni Bitcoin in ordine cronologico. La blockchain è condivisa tra tutti gli utenti Bitcoin. È utilizzata per verificare la permanenza delle transazioni Bitcoin e per prevenire double spending." block: "Blocco" blocktxt: "Un blocco è una parte della blockchain che contiene e conferma molte transazioni in attesa. In media circa ogni 10 minuti un nuovo blocco, che include delle transazioni, viene aggiunto alla blockchain attraverso il processo di mining." btc: "BTC" @@ -630,9 +630,9 @@ it: confirmation: "Conferma" confirmationtxt: "La conferma indica che una transazione è stata processata dalla rete ed è altamente improbabile che sia respinta. La transazioni ricevono una conferma, quando sono incluse in un blocco e per ogni blocco successivo. Anche una singola conferma può essere considerata sicura per le transazioni di basso valore, sebbene per cifre maggiori come 1000 US$, è consigliabile attendere ben 6 conferme o di più. Ogni conferma esponenzialmente diminuisce il rischio di una transazione respinta. " cryptography: "Crittografia" - cryptographytxt: "La crittografia è quella branca della matematica che ci consente di creare prove matematiche che forniscono elevati livelli di sicurezza. Il commercio e le operazioni bancarie online impiegano già la crittografia. Nel caso di Bitcoin la crittografia è impiegata per rendere impossibile a chiunque di spendere del denaro dal portafoglio di un altro utente o alterare la block chain. Può essere anche utilizzata per criptare un portafoglio, in modo che non possa essere usato senza una passowrd." + cryptographytxt: "La crittografia è quella branca della matematica che ci consente di creare prove matematiche che forniscono elevati livelli di sicurezza. Il commercio e le operazioni bancarie online impiegano già la crittografia. Nel caso di Bitcoin la crittografia è impiegata per rendere impossibile a chiunque di spendere del denaro dal portafoglio di un altro utente o alterare la blockchain. Può essere anche utilizzata per criptare un portafoglio, in modo che non possa essere usato senza una passowrd." doublespend: "Double Spend" - doublespendtxt: "Se un utente malintenzionato prova a spendere i propri bitcoin verso due diversi riceventi contemporaneamente, si tratta di doppia spesa. Il mining di Bitcoin ed il block chain esistono per creare un consenso sulla rete, per decidere quale delle due transazioni sia considerata valida." + doublespendtxt: "Se un utente malintenzionato prova a spendere i propri bitcoin verso due diversi riceventi contemporaneamente, si tratta di doppia spesa. Il mining di Bitcoin ed il blockchain esistono per creare un consenso sulla rete, per decidere quale delle due transazioni sia considerata valida." hashrate: "Hash Rate" hashratetxt: "Per hash rate si intende l'unità di misura della potenza di elaborazione della rete Bitcoin. Per fini di sicurezza la rete Bitcoin deve eseguire delle operazioni matematiche intensive. Quando la rete raggiunge un hash rate di 10 Th/s, significa che può realizzare un trilione di calcoli al secondo." mining: "Mining" @@ -644,7 +644,7 @@ it: signature: "Firma" signaturetxt: "La firma criptografica è un meccanismo matematico che consente di provare la proprietà. Nel caso di Bitcoin, un portafoglio Bitcoin e la sua chiave privata(e) sono collegati per mezzo di un vincolo matematico magico. Quando il tuo software Bitcoin segna una transazione con la chiave privata appropriata, l'intera rete può vedere che la firma combacia con i bitcoin spesi. Tuttavia, non c'è alcun modo per il mondo d'indovinare la tua chiave privata, per derubarti dei tuoi bitcoin, ottenuti col sudore della fronte. " wallet: "Portafoglio" - wallettxt: "Un portafoglio di Bitcoin è circa l'equivalente di un portafoglio materiale sul network di Bitcoin. In realtà il tuo portafoglio contiene le chiavi private che ti permettono di usare i bitcoin allocati nella block chain. Ogni portafoglio Bitcoin può mostrarti il bilancio totale di tutti i bitcoin che controlla e ti permette di pagare cifre precise ad una persona specifica, come un vero portafoglio. Questo è diverso dalla carte di credito dove ti sono addebitate le spese dal commerciante." + wallettxt: "Un portafoglio di Bitcoin è circa l'equivalente di un portafoglio materiale sul network di Bitcoin. In realtà il tuo portafoglio contiene le chiavi private che ti permettono di usare i bitcoin allocati nella blockchain. Ogni portafoglio Bitcoin può mostrarti il bilancio totale di tutti i bitcoin che controlla e ti permette di pagare cifre precise ad una persona specifica, come un vero portafoglio. Questo è diverso dalla carte di credito dove ti sono addebitate le spese dal commerciante." you-need-to-know: title: "Alcune cose da sapere - Bitcoin" pagetitle: "Alcune cose da sapere" diff --git a/_translations/ja.yml b/_translations/ja.yml index c564bccdb9..015b8d4391 100644 --- a/_translations/ja.yml +++ b/_translations/ja.yml @@ -712,7 +712,7 @@ ja: address: address bit: bit bitcoin: bitcoin - blockchain: block-chain + blockchain: blockchain block: block btc: btc confirmation: confirmation diff --git a/_translations/ko.yml b/_translations/ko.yml index d8470be39a..f16d67d4ee 100644 --- a/_translations/ko.yml +++ b/_translations/ko.yml @@ -712,7 +712,7 @@ ko: address: address bit: bit bitcoin: bitcoin - blockchain: block-chain + blockchain: blockchain block: block btc: btc confirmation: confirmation diff --git a/_translations/pt_BR.yml b/_translations/pt_BR.yml index 132f14a280..12b132da6e 100644 --- a/_translations/pt_BR.yml +++ b/_translations/pt_BR.yml @@ -234,7 +234,7 @@ pt_BR: sourcecode: "Obtenha o código fonte" versionhistory: "Mostrar histórico da versão" notelicense: "Bitcoin Core é um projeto livre e de código aberto, lançado sob a licença MIT." - notesync: "A sincronização inicial com Bitcoin Core pode levar bastante tempo. Você deve assegurar-se de ter largura de banda e memória suficiente para o tamanho inteiro do block chain (mais de 20GB). Se você souber como fazer o download de um arquivo torrente, você pode acelerar esse processo colocando bootstrap.dat (uma cópia prévia do block chain) no diretório de dados do Bitcoin Core antes de iniciar o programa." + notesync: "A sincronização inicial com Bitcoin Core pode levar bastante tempo. Você deve assegurar-se de ter largura de banda e memória suficiente para o tamanho inteiro do blockchain (mais de 20GB). Se você souber como fazer o download de um arquivo torrente, você pode acelerar esse processo colocando bootstrap.dat (uma cópia prévia do blockchain) no diretório de dados do Bitcoin Core antes de iniciar o programa." patient: "Você precisará ter paciência" events: title: "Conferências e eventos - Bitcoin" @@ -260,7 +260,7 @@ pt_BR: whocontrolstxt1: "Ninguém é dono da rede Bitcoin muito como ninguém possui a tecnologia por trás do e-mail. Bitcoin é controlada por todos os usuários do Bitcoin ao redor do mundo. Enquanto os desenvolvedores estão melhorando o software, eles não podem forçar uma mudança no protocolo do Bitcoin, porque todos os usuários são livres para escolher o software e versão que eles usam. A fim de permanecer compatíveis uns com os outros, todos os usuários precisam usar o software em conformidade com as mesmas regras. Bitcoin só pode funcionar corretamente com um consenso total entre todos os usuários. Portanto, todos os usuários e desenvolvedores têm um forte incentivo para proteger este consenso." howitworks: "Como o Bitcoin funciona?" howitworkstxt1: "Da perspectiva do usuário, Bitcoin não é nada mais do que um programa aplicativo ou computador móvel que ofersece uma carteira Bitcoin pessoal e permite que o usuário envie e receba bitcoins com ele. Assim é como Bitcoin funciona para a maioria dos usuários." - howitworkstxt2: "Nos bastidores, a rede Bitcoin compartilha um registro público chamado de \"cadeia de bloco\" ou \"block chain\". Este registro contém todas as transações já processadas​​, permitindo que o computador do usuário verifique a validade de cada transação. A autenticidade de cada transação é protegida por assinaturas digitais correspondentes aos endereços enviados, permitindo que todos os usuários tenham controle total sobre o envio de bitcoins de seus próprios endereços Bitcoin. Além disso, qualquer um pode processar transações, usando o poder de computação de hardware especializado e ganhar uma recompensa em bitcoins por este serviço. Isso é muitas vezes chamado de \"mineração\". Para saber mais sobre Bitcoin, pode consultar a página dedicada e o documento original." + howitworkstxt2: "Nos bastidores, a rede Bitcoin compartilha um registro público chamado de \"cadeia de bloco\" ou \"blockchain\". Este registro contém todas as transações já processadas​​, permitindo que o computador do usuário verifique a validade de cada transação. A autenticidade de cada transação é protegida por assinaturas digitais correspondentes aos endereços enviados, permitindo que todos os usuários tenham controle total sobre o envio de bitcoins de seus próprios endereços Bitcoin. Além disso, qualquer um pode processar transações, usando o poder de computação de hardware especializado e ganhar uma recompensa em bitcoins por este serviço. Isso é muitas vezes chamado de \"mineração\". Para saber mais sobre Bitcoin, pode consultar a página dedicada e o documento original." used: "Bitcoin é realmente usado por pessoas?" usedtxt1: "Sim, Existe um número crescente de empresas e indivíduos usando Bitcoin. Incluindo estabelecimentos tradicionais como restaurantes, apartamentos, escritórios de advocacia e serviços populares on-line como Namecheap, WordPress, Reddit e Flattr. Enquanto Bitcoin continua a ser um fenômeno relativamente novo, ele está crescendo rapidamente. No final de agosto de 2013, o valor de todos os bitcoins em circulação excediam 1.5 bilhões de dólares americanos, sendo que 1.5 milhões de dólares em bitcoins são usados diariamente." acquire: "Como uma pessoa pode adquirir bitcoins?" @@ -276,7 +276,7 @@ pt_BR: advantagesli2: "Taxas muito baixas - pagamentos com Bitcoin são atualmente processados tanto sem taxas ou com taxas extremamente pequenas. Os usuários podem incluir taxas de transações para receber tratamento prioritário, o que resulta em uma confirmação das transações mais rápida pela rede. Além disso, existem processadores comerciais para auxiliar comerciantes em operações de processamento, convertendo bitcoins em uma moeda fiduciária e depositando fundos diretamente para contas bancárias dos comerciantes diariamente. Como estes serviços são baseados em Bitcoin, eles podem ser oferecidos com taxas muito mais baixas do que com PayPal ou redes de cartão de crédito." advantagesli3: " Menos riscos para os comerciantes - As transações de Bitcoin são seguras, irreversível, e não contêm informações confidenciais ou pessoais dos clientes. Isso protege os comerciantes de perdas causadas por fraude ou estornos fraudulentos, e não há necessidade de conformidade com o PCI. Os comerciantes podem facilmente expandir para novos mercados, onde os cartões de crédito não estão disponíveis ou taxas de fraude são inaceitavelmente elevadas. Os resultados líquidos são taxas mais baixas, os mercados maiores, e menos custos administrativos." advantagesli4: "Segurança e controle - Usuários do Bitcoin tem controle total de suas transações; é impossível que os comerciantes forcem cobranças indesejadas ou não notificadas como poderia ocorrer com outras formas de pagamento. Os pagamentos com Bitcoin podem ser realizados sem vincular informações pessoais à transação. Isto oferece forte proteção contra furto de identidade. Os usuários do Bitcoin também podem proteger seu dinheiro com cópias de segurança e criptografia." - advantagesli5: "Transparente e neutro - Toda informação em relação a própria moeda Bitcoin está facilmente disponível na block chain para qualquer um verificar e usar em tempo real. Nenhum indivíduo ou organização pode controlar ou manipular o protocolo Bitcoin, porque este é criptograficamente seguro. Isso permite que o núcleo do Bitcoin seja confiável por ser completamente neutro, transparente e previsível." + advantagesli5: "Transparente e neutro - Toda informação em relação a própria moeda Bitcoin está facilmente disponível na blockchain para qualquer um verificar e usar em tempo real. Nenhum indivíduo ou organização pode controlar ou manipular o protocolo Bitcoin, porque este é criptograficamente seguro. Isso permite que o núcleo do Bitcoin seja confiável por ser completamente neutro, transparente e previsível." disadvantages: "Quais são as desvantagens do Bitcoin?" disadvantagesli1: "Grau de aceitação - Muitas pessoas ainda não têm conhecimento de Bitcoin. A cada dia, mais empresas aceitam bitcoins, porque eles querem as vantagens ao fazê-lo, mas a lista continua pequena e ainda precisa crescer, a fim de beneficiar-se dos efeitos de rede." disadvantagesli2: "Volatilidade - O valor total do número de bitcoins em circulação e o número de transações que utilizam Bitcoin ainda é muito menor comparado ao que poderia ser. Portanto, eventos relativamente pequenos, trocas, ou atividades negociais podem afetar significativamente o seu preço. Em teoria, esta volatilidade irá diminuir a medida que o mercado da Bitcoin e a tecnologia amadurecerem. Nunca antes o mundo havia presenciado a criação de uma moeda, então é realmente difícil (e excitante) imaginar como isto irá funcionar." @@ -292,7 +292,7 @@ pt_BR: anonymoustxt1: "A Bitcoin é designada para permitir aos usuários enviar e receber pagamentos com um grande nível de privacidade, assim como qualquer outra forma de pagamento. Entretanto, Bitcoin não é anônima e não pode oferecer o mesmo nível de privacidade que o papel moeda. O usuário da Bitcoin deixa uma extensiva lista de dados públicos. Vários mecanismo existem para proteger a privacidade dos usuários, e mais outros estão em desenvolvimento. Porém, ainda existe trabalho a ser feito antes que esses mecanismos sejam utilizados corretamente pela maioria dos usuários da Bitcoin." anonymoustxt2: "Algumas preocupações foram levantadas de que as transações privadas poderiam ser usadas para fins ilegais com Bitcoin. No entanto, é interessante notar que o Bitcoin, sem dúvida, será submetido a regulamentos semelhantes que já estão em vigor dentro de sistemas financeiros existentes. Bitcoin não pode ser mais anônimo do que o dinheiro e não é susceptível de impedir investigações criminais de serem conduzidas. Além disso, o Bitcoin também é projetado para evitar uma grande variedade de crimes financeiros." lost: "O que acontece quando bitcoins são perdidos?" - losttxt1: "Quando um usuário perde a carteira, seu dinheiro é retirado de circulação. Os Bitcoins perdidos ainda permanecem na block chain, assim como quaisquer outros bitcoins. No entanto, perder bitcoins é mantê-los perdidos para sempre, porque não há nenhuma maneira de alguém encontrar a chave privada que lhes permitiria serem gastos novamente. Por causa da lei da oferta e da procura, quanto menos bitcoins estão disponíveis, aqueles que estão à esquerda estarão em maior demanda e haverá um aumento no valor para compensar." + losttxt1: "Quando um usuário perde a carteira, seu dinheiro é retirado de circulação. Os Bitcoins perdidos ainda permanecem na blockchain, assim como quaisquer outros bitcoins. No entanto, perder bitcoins é mantê-los perdidos para sempre, porque não há nenhuma maneira de alguém encontrar a chave privada que lhes permitiria serem gastos novamente. Por causa da lei da oferta e da procura, quanto menos bitcoins estão disponíveis, aqueles que estão à esquerda estarão em maior demanda e haverá um aumento no valor para compensar." scale: "Bitcoin pode tornar-se uma grande rede de pagamento?" scaletxt1: "A rede Bitcoin já pode processar um número muito maior de transações por segundo do que já processa hoje. No entanto, não é totalmente preparada para ser dimensionada para o nível das grandes redes de cartão de crédito. Os trabalhos estão em curso para levantar as limitações atuais, e as futuras exigências já são bem conhecidas. Desde o início, todos os aspectos da rede Bitcoin tem sido um processo contínuo de maturação, otimização e especialização e, isso deve-se esperar que permaneça assim durante alguns anos. Como o tráfego cresce, mais usuários Bitcoin podem utilizar clientes leves e os nós de toda a rede podem se tornar um serviço mais especializado. Para mais detalhes, consulte página Scalability no Wiki." legal: "Legal" @@ -352,14 +352,14 @@ pt_BR: poweredoff: "E se eu receber um bitcoin quando o meu computador estiver desligado?" poweredofftxt1: "Tudo bem. Os bitcoins aparecerão na próxima vez que você iniciar o aplicativo da carteira. Bitcoins não são realmente recebidos pelo software no seu computador, eles são anexados a um registro público que é compartilhado entre todos os dispositivos na rede. Se lhe forem enviados bitcoins quando o programa cliente da carteira não está em execução e mais tarde você iniciá-lo, ele irá baixar blocos e obter as transações que não conhece, e os bitcoins eventualmente aparecerão como se estivesse acabado de receber em tempo tempo real. Sua carteira só é necessária quando você deseja gastar bitcoins." sync: "O que é que \"sincronizando\" quer dizer e por que demora tanto?" - synctxt1: "Um longo período de sincronização só é necessário quando se utiliza clientes de nó completo como o Bitcoin Core. Técnicamente falando, sincronização é o processo de download e verificação de todas as transações que já passaram pela rede. Para alguns clientes de Bitcoin, calcular o saldo da sua carteira de Bitcoin e realizar novas transações é necessário que se saiba de todas as transações anteriores. Este passo utiliza intensivamente recursos e exige uma banda e armazenamento suficientes para acomodar o tamanho total da block chain. Para que o Bitcoin continue seguro, um número suficiente de pessoas tem que manter um cliente de nó completo para que executem a tarefa de validação e afinação das transações." + synctxt1: "Um longo período de sincronização só é necessário quando se utiliza clientes de nó completo como o Bitcoin Core. Técnicamente falando, sincronização é o processo de download e verificação de todas as transações que já passaram pela rede. Para alguns clientes de Bitcoin, calcular o saldo da sua carteira de Bitcoin e realizar novas transações é necessário que se saiba de todas as transações anteriores. Este passo utiliza intensivamente recursos e exige uma banda e armazenamento suficientes para acomodar o tamanho total da blockchain. Para que o Bitcoin continue seguro, um número suficiente de pessoas tem que manter um cliente de nó completo para que executem a tarefa de validação e afinação das transações." mining: "Mineração" whatismining: "O que é mineração de Bitcoin?" whatisminingtxt1: "Mineração é o processo de usar capacidade de processamento para processar transações, garantir a segurança da rede, e manter todos participantes do sistema sincronizados. Pode ser considerado como o datacenter do Bitcoin exceto que foi projetado para ser totalmente descentralizado, com mineradores em todos os países e nenhum em particular tendo controle sobre a rede. Este processo é chamado de \"mineração\" em uma analogia à mineração de ouro porque é um mecanismo temporário utilizado na emissão de novos bitcoins. Porém diferentemente da mineração de ouro, a mineração de Bitcoin provê uma recompensa em troca dos serviços essenciais para operar uma rede segura de pagamentos. Mineração ainda será necessária depois que o último Bitcoin for emitido." howminingworks: "Como é que a mineração de bitcoin funciona?" howminingworkstxt1: "Qualquer um pode se tornar um mineiro de Bitcoin executando software com hardware especializado. Software de Mineração ouve transações transmitidas através da rede ponto a ponto e executa tarefas apropriadas para processar e confirmar essas transações. Mineiros de Bitcoin realizam esse trabalho, porque eles podem ganhar comissões de transação pagas pelos usuários para o processamento mais rápido das transações, e bitcoins novos são emitidos de acordo com uma fórmula fixa existente internamente." - howminingworkstxt2: "Para novas transações serem confirmadas, elas precisam ser incluídas em um bloco juntamente com uma prova matemática de trabalho. Tais provas são muito difíceis de serem geradas porque não há um jeito de se criá-las a não ser através da tentativa de realizar bilhões de cálculos por segundo. Isso requer que mineradores realizem tais cálculos antes que seus blocos sejam aceitos pela rede e antes de serem recompensados. À medida que mais pessoas começam a minerar, a dificuldade de encontrar novos blocos válidos é automaticamente aumentada, para garantir que a média de tempo para encontrar um bloco permaneça igual a 10 minutos. Como resultado, a mineração é um negócio altamente competitivo onde nenhum indivíduo minerador pode controlar o que é incluído na block chain." - howminingworkstxt3: "A prova de trabalho também é projetada para depender do bloco anterior para forçar uma ordem cronológica na block chain. Isso torna exponencialmente difícil de reverter operações anteriores, pois isso exige o recálculo das provas de trabalho de todos os blocos subsequentes. Quando dois blocos se encontram ao mesmo tempo, os mineiros trabalham sobre o primeiro bloco que receber e exibem a cadeia mais longa de blocos logo que o bloco seguinte é encontrado. Isso permite que a mineração garanta e mantenha um consenso global com base no poder de processamento." + howminingworkstxt2: "Para novas transações serem confirmadas, elas precisam ser incluídas em um bloco juntamente com uma prova matemática de trabalho. Tais provas são muito difíceis de serem geradas porque não há um jeito de se criá-las a não ser através da tentativa de realizar bilhões de cálculos por segundo. Isso requer que mineradores realizem tais cálculos antes que seus blocos sejam aceitos pela rede e antes de serem recompensados. À medida que mais pessoas começam a minerar, a dificuldade de encontrar novos blocos válidos é automaticamente aumentada, para garantir que a média de tempo para encontrar um bloco permaneça igual a 10 minutos. Como resultado, a mineração é um negócio altamente competitivo onde nenhum indivíduo minerador pode controlar o que é incluído na blockchain." + howminingworkstxt3: "A prova de trabalho também é projetada para depender do bloco anterior para forçar uma ordem cronológica na blockchain. Isso torna exponencialmente difícil de reverter operações anteriores, pois isso exige o recálculo das provas de trabalho de todos os blocos subsequentes. Quando dois blocos se encontram ao mesmo tempo, os mineiros trabalham sobre o primeiro bloco que receber e exibem a cadeia mais longa de blocos logo que o bloco seguinte é encontrado. Isso permite que a mineração garanta e mantenha um consenso global com base no poder de processamento." howminingworkstxt4: "Mineiros de Bitcoin não são capazes de enganar, aumentando a sua própria recompensa, nem processar transações fraudulentas que poderiam corromper a rede Bitcoin, porque todos os nós Bitcoin rejeitariam qualquer bloco que contenham dados inválidos de acordo com as regras do protocolo Bitcoin. Consequentemente, a rede continua a ser segura, mesmo que nem todos os mineiros de Bitcoin possam ser confiáveis." miningwaste: "Minerar Bitcoin não é um desperdício de energia?" miningwastetxt1: "Gastar energia para proteger e operar um sistema de pagamento é dificilmente um desperdício. Como qualquer outro serviço de pagamento, o uso de Bitcoin implica custos de processamento. Serviços necessários para o funcionamento dos sistemas monetários atualmente generalizados, tais como bancos, cartões de crédito e veículos blindados, também usam muita energia. Embora ao contrário Bitcoin, o seu consumo total de energia não é transparente e não pode ser tão facilmente medido." @@ -421,9 +421,9 @@ pt_BR: balances: "Saldos - cadeia de blocos" balancestxt: "A cadeia de blocos é um livro de registro de contabilidade público compartilhado no qual toda a rede Bitcoin confia. Todas transações confirmadas são incluídas na cadeia de blocos. Desta forma, as carteiras de Bitcoin podem calcular seu saldo disponível e novas transações podem ser verificadas para que se possa usar bitcoins que são realmente de propriedade de quem está gastando. A integridade e ordem cronológica da cadeia de blocos são protegidas por criptografia." transactions: "Transações - chaves privadas" - transactionstxt: "Uma transação é uma transferência de valor entre carteiras Bitcoin que é incluída na block chain. Carteiras Bitcoin mantém uma informação secreta chamada chave privada ou semente, que é usada para assinar transações, fornecendo uma prova matemática provando que elas vieram do dono da carteira. A assinatura também previne que a transação seja alterada por qualquer um depois de emitida. Todas as transações são divulgadas entre os usuários e normalmente começam a ser confirmadas pela rede nos próximos 10 minutos, através de um processo chamado mineração." + transactionstxt: "Uma transação é uma transferência de valor entre carteiras Bitcoin que é incluída na blockchain. Carteiras Bitcoin mantém uma informação secreta chamada chave privada ou semente, que é usada para assinar transações, fornecendo uma prova matemática provando que elas vieram do dono da carteira. A assinatura também previne que a transação seja alterada por qualquer um depois de emitida. Todas as transações são divulgadas entre os usuários e normalmente começam a ser confirmadas pela rede nos próximos 10 minutos, através de um processo chamado mineração." processing: "Processando - minerando" - processingtxt: "A mineração é um sistema que funciona através de consenso serve para confirmar as transações e incluí-las no block chain. Protege a neutralidade da rede, e permite que diferentes computadores estejam harmonicamente sincronizados com o sistema. Para serem confirmadas, as transações devem ser incluídas em um bloco e verificadas pela rede através de regras criptográficas. Essa regras previnem que blocos antigos sejam modificados, o que provocaria a invalidação dos blocos posteriores. A mineração também cria um jogo equivalente à loteria, que dificulta a criação de novos blocos pelas mesmas pessoas. Isto evita que pessoas possam decidir o que incluir no block chain ou mudar partes do block chain e assim conseguir reverter suas próprias transações." + processingtxt: "A mineração é um sistema que funciona através de consenso serve para confirmar as transações e incluí-las no blockchain. Protege a neutralidade da rede, e permite que diferentes computadores estejam harmonicamente sincronizados com o sistema. Para serem confirmadas, as transações devem ser incluídas em um bloco e verificadas pela rede através de regras criptográficas. Essa regras previnem que blocos antigos sejam modificados, o que provocaria a invalidação dos blocos posteriores. A mineração também cria um jogo equivalente à loteria, que dificulta a criação de novos blocos pelas mesmas pessoas. Isto evita que pessoas possam decidir o que incluir no blockchain ou mudar partes do blockchain e assim conseguir reverter suas próprias transações." readmore: "Até onde você está disposto a descobrir?" readmoretxt: "Este é somente um resumo muito breve e conciso do sistema. Caso queira saber mais a fundo, você pode ler o artigo original que descreve o projeto do sistema, ler a documentação para programadores, e explorar a Wiki de Bitcoin." index: @@ -615,16 +615,16 @@ pt_BR: bittxt: "Bit é uma unidade comum para designar uma sub-unidade de bitcoin — 1.000.000 de bits é igual à 1 bitcoin (BTC or B). Esta unidade é geralmente mais conveniente para colocar preços em gorjetas, produtos e serviços." bitcoin: "Bitcoin" bitcointxt: "Bitcoin - quando começar em letra maiúscula, é usado para descrever o conceito do bitcoin, ou a própria rede por completa. Por exemplo \"Eu estava aprendendo sobre o protocolo do Bitcoin hoje.\"
bitcoin - em letra minúscula é usado para descrever a unidade de bitcoins na conta. Por exemplo \"Eu enviei dez bitcoins hoje.\" Existem também as abreviações BTC ou XBT." - blockchain: "Block Chain" - blockchaintxt: "A block chain é um registro público de transações Bitcoin em ordem cronológica. A block chain é compartilhada entre todos os usuários do Bitcoin. Ele é usado para verificar a permanência de transações Bitcoin e impedir duplo gastos ." + blockchain: "Blockchain" + blockchaintxt: "A blockchain é um registro público de transações Bitcoin em ordem cronológica. A blockchain é compartilhada entre todos os usuários do Bitcoin. Ele é usado para verificar a permanência de transações Bitcoin e impedir duplo gastos ." block: "Bloco" - blocktxt: "Um block é um registro dentro do block chain que contém e confirma várias transações em espera. Aproximadamente a cada 10 minutos, em média, um novo bloco com transações é anexado a block chainatravés da mineração." + blocktxt: "Um block é um registro dentro do blockchain que contém e confirma várias transações em espera. Aproximadamente a cada 10 minutos, em média, um novo bloco com transações é anexado a blockchainatravés da mineração." btc: "BTC" btctxt: "BTC é uma unidade comum usada para designar um bitcoin (B)." confirmation: "Confirmação" confirmationtxt: "Confirmação significa que uma transação foi processada pela rede e é altamente improvável ser revertida. Transações recebem uma confirmação quando são incluídas em um bloco e a cada bloco subsequente. Mesmo uma única confirmação pode ser considerada segura para transações de baixos valores, apesar de valores maiores como 1.000 US$, faz sentido esperar por 6 confirmações ou mais. Cada confirmação reduz exponencialmenteo risco de uma transação ser revertida." cryptography: "Criptografia" - cryptographytxt: "A criptografia é o ramo da matemática que nos deixa criar provas matemáticas que fornecem um alto nível de segurança. Já sendo utilizada em comércio online e bancos. No caso do Bitcoin, a criptografia é utilizada para fazer com que seja impossível para qualquer um gastar fundos da carteira de outro usuário ou corromper a block chain. Também pode ser utilizada para encriptar uma carteira, de modo que ela não pode ser utilizada sem uma senha." + cryptographytxt: "A criptografia é o ramo da matemática que nos deixa criar provas matemáticas que fornecem um alto nível de segurança. Já sendo utilizada em comércio online e bancos. No caso do Bitcoin, a criptografia é utilizada para fazer com que seja impossível para qualquer um gastar fundos da carteira de outro usuário ou corromper a blockchain. Também pode ser utilizada para encriptar uma carteira, de modo que ela não pode ser utilizada sem uma senha." doublespend: "Gasto Duplo" doublespendtxt: "Se um usuário malicioso tentar gastar os seus bitcoins em dois recipientes ao mesmo tempo, isto é gasto duplo. Bitcoin mineração e a corrente de bloqueio estão ali para criar um consenso na network sobre qual das duas transações será confirmada e pode ser considerada válida." hashrate: "Taxa de Hash" diff --git a/_translations/ru.yml b/_translations/ru.yml index 2a1380059a..3323576a27 100644 --- a/_translations/ru.yml +++ b/_translations/ru.yml @@ -718,7 +718,7 @@ ru: address: address bit: bit bitcoin: bitcoin - blockchain: block-chain + blockchain: blockchain block: block btc: btc confirmation: confirmation diff --git a/_translations/uk.yml b/_translations/uk.yml index 002dfa1d52..5e54ca7581 100644 --- a/_translations/uk.yml +++ b/_translations/uk.yml @@ -712,7 +712,7 @@ uk: address: address bit: bit bitcoin: bitcoin - blockchain: block-chain + blockchain: blockchain block: block btc: btc confirmation: confirmation diff --git a/_translations/zh_CN.yml b/_translations/zh_CN.yml index 3f255555a6..dcaf852f30 100644 --- a/_translations/zh_CN.yml +++ b/_translations/zh_CN.yml @@ -712,7 +712,7 @@ zh_CN: address: address bit: bit bitcoin: bitcoin - blockchain: block-chain + blockchain: blockchain block: block btc: btc confirmation: confirmation diff --git a/en/bitcoin-core/features/privacy.md b/en/bitcoin-core/features/privacy.md index caf8e7c4d5..03050c92bf 100644 --- a/en/bitcoin-core/features/privacy.md +++ b/en/bitcoin-core/features/privacy.md @@ -104,7 +104,7 @@ third_party_privacy: > details were published to your Twitter or Facebook feed for all your > friends to see? You probably wouldn't want to use cash any more. -Every confirmed Bitcoin transaction is published to the block chain +Every confirmed Bitcoin transaction is published to the blockchain where anyone can see it. So **why do people still use Bitcoin?** And why do many of them believe that Bitcoin is a private way of sending money? @@ -314,7 +314,7 @@ against eavesdroppers for received transactions. ## Strong Privacy for Sent Transactions -To put a transaction on the block chain, you must send it publicly---but +To put a transaction on the blockchain, you must send it publicly---but how you send it can make a big difference. ![Sending privacy](/img/bitcoin-core/sending-privacy.svg) @@ -427,7 +427,7 @@ Isn't that worth occasionally starting up a few seconds slower? Some lightweight wallets don't connect to the Bitcoin peer-to-peer (P2P) network. Instead, they make a (usually secure) connection to a single - server that provides block chain data. + server that provides blockchain data. The wallet tells the server all of its addresses, and the server replies with all of the transactions that belong to the wallet. This explicitly diff --git a/en/bitcoin-core/features/user-interface.md b/en/bitcoin-core/features/user-interface.md index ab8b1b2ec0..737b94fc37 100644 --- a/en/bitcoin-core/features/user-interface.md +++ b/en/bitcoin-core/features/user-interface.md @@ -182,8 +182,8 @@ the Bitcoin network. {% translate walletmsigna choose-your-wallet %} **No configuration necessary:** just install Bitcoin Core on the same -computer you plan to use mSigna, wait for Bitcoin Core to sync the block -chain, and then start mSigna---it will automatically connect to your +computer you plan to use mSigna, wait for Bitcoin Core to sync the +blockchain, and then start mSigna---it will automatically connect to your Bitcoin Core full node. {:.right-hanger} diff --git a/en/bitcoin-core/features/validation.md b/en/bitcoin-core/features/validation.md index fe30ef3c0e..94e02b1171 100644 --- a/en/bitcoin-core/features/validation.md +++ b/en/bitcoin-core/features/validation.md @@ -33,7 +33,7 @@ blocks that violate the 21 million bitcoin limit or which break other important rules. Users of other wallets don't get this level of security, so miners can -trick them into accepting fabricated transactions or hijacked block chains. +trick them into accepting fabricated transactions or hijacked blockchains. Why take that risk if you don't have to? Bitcoin Core provides the **best possible security against dishonest miners** along @@ -205,13 +205,13 @@ safety][] > Alice believes that there should never be more than 21 million > bitcoins---but one day she's tricked into buying "bitcoins" that -> are only valid on a block chain with permanent 10% inflation. +> are only valid on a blockchain with permanent 10% inflation. -- **Bitcoin bank**{:.fgred} users have to use whatever block chain the +- **Bitcoin bank**{:.fgred} users have to use whatever blockchain the bank uses. Banks can even profit from switching their users to a new chain and selling their users' bitcoins from the old chain. -- **Lightweight (SPV) wallet**{:.fgred} users accept the block chain +- **Lightweight (SPV) wallet**{:.fgred} users accept the blockchain they know about with the most proof of work. This lets the hash rate majority of miners force SPV wallet users off of Bitcoin. @@ -227,7 +227,7 @@ The alternative is to allow miners to do whatever they want. ### Real Example In July 2015, several large Bitcoin miners accidentally produced an -invalid block chain several blocks longer than the correct block chain. +invalid blockchain several blocks longer than the correct blockchain. Some bank wallets and many SPV wallets accepted this longer chain, putting their users' bitcoins at risk. @@ -274,7 +274,7 @@ mining income.

Unless you use Bitcoin Core, you can never be sure that your bitcoin balance -is correct according to the block chain. +is correct according to the blockchain.
### Real Example @@ -304,7 +304,7 @@ users stopped receiving notification of new transactions. This attack applies to **all Bitcoin wallets.**{:.fgred} The attack works because powerful miners have the ability to rewrite the -block chain and replace their own transactions, allowing them to take +blockchain and replace their own transactions, allowing them to take back previous payments. The cost of this attack depends on the percentage of total network hash @@ -461,7 +461,7 @@ If you have any questions, please ask on the [forums][bcc forums] or
**Simplified Payment Verification (SPV)** wallets are lightweight wallets that can verify whether or not a transaction is part of a block - without downloading the {{site.text.chain_gb}} GB block chain. However, + without downloading the {{site.text.chain_gb}} GB blockchain. However, they cannot verify whether or not the transaction is actually valid. (Only full validation nodes like Bitcoin Core can do that.) diff --git a/en/bitcoin-core/index.md b/en/bitcoin-core/index.md index 82c41671d6..fde2856369 100644 --- a/en/bitcoin-core/index.md +++ b/en/bitcoin-core/index.md @@ -24,9 +24,9 @@ breadcrumbs:
- Bitcoin Core is programmed to decide which block chain contains + Bitcoin Core is programmed to decide which blockchain contains valid transactions. The users of Bitcoin Core only accept - transactions for that block chain, making it the Bitcoin block + transactions for that blockchain, making it the Bitcoin block chain that everyone else wants to use
@@ -34,12 +34,12 @@ breadcrumbs: It is these users who keep Bitcoin decentralized. They individually run their own Bitcoin Core full nodes, and each of those full nodes separately follows the exact same rules to decide - which block chain is valid. + which blockchain is valid. There's no voting or other corruptible process involved: there's just individual software following identical rules—"math"—to evaluate identical blocks and coming to identical conclusions - about which block chain is valid. + about which blockchain is valid. This shared agreement (called consensus) allows people like you to only accept valid bitcoins, enforcing Bitcoin's rules against diff --git a/en/developer-documentation.md b/en/developer-documentation.md index 1fce957327..af3c15f198 100644 --- a/en/developer-documentation.md +++ b/en/developer-documentation.md @@ -31,9 +31,9 @@ end_of_page: |
-

Block Chain

-

Block Chain Guide

-

Block Chain Reference

+

Blockchain

+

Blockchain Guide

+

Blockchain Reference

Transactions

Transactions Guide

diff --git a/en/developer-reference.md b/en/developer-reference.md index d8acf56485..03fe7b5590 100644 --- a/en/developer-reference.md +++ b/en/developer-reference.md @@ -59,13 +59,13 @@ end_of_page: | #### RPCs -{{WARNING}} the block chain and memory pool can include arbitrary data +{{WARNING}} the blockchain and memory pool can include arbitrary data which several of the commands below will return in hex format. If you convert this data to another format in an executable context, it could be used in an exploit. For example, displaying a pubkey script as ASCII text in a webpage could add arbitrary Javascript to that page and create a cross-site scripting (XSS) exploit. To avoid problems, please -treat block chain and memory pool data as an arbitrary input from an +treat blockchain and memory pool data as an arbitrary input from an untrusted source. {% include devdoc/bitcoin-core/rpcs/rpcs/addmultisigaddress.md %} @@ -243,13 +243,13 @@ untrusted source. #### Requests -{{WARNING}} the block chain and memory pool can include arbitrary data +{{WARNING}} the blockchain and memory pool can include arbitrary data which several of the commands below will return in hex format. If you convert this data to another format in an executable context, it could be used in an exploit. For example, displaying a pubkey script as ASCII text in a webpage could add arbitrary Javascript to that page and create a cross-site scripting (XSS) exploit. To avoid problems, please -treat block chain and memory pool data as an arbitrary input from an +treat blockchain and memory pool data as an arbitrary input from an untrusted source. {% include devdoc/bitcoin-core/rest/requests/get_block.md %} diff --git a/en/full-node.md b/en/full-node.md index eab455e8cd..e6201d9c8c 100644 --- a/en/full-node.md +++ b/en/full-node.md @@ -77,7 +77,7 @@ A complete list of commands is available in the [Bitcoin.org developer reference](/en/developer-reference#rpc-quick-reference). When Bitcoin Core daemon first starts, it will begin to download the -block chain. This step will take at least several hours, and it may +blockchain. This step will take at least several hours, and it may take a day or more on a slow Internet connection or with a slow computer. During the download, Bitcoin Core will use a significant part of your connection bandwidth. You can stop Bitcoin Core at any time using @@ -285,7 +285,7 @@ you want to use, click Ok to use the default. ![Bitcoin-Qt Welcome](/img/full-node/en-bitcoin-qt-welcome.png) -Bitcoin Core GUI will begin to download the block chain. This +Bitcoin Core GUI will begin to download the blockchain. This step will take at least several hours, and it may take a day or more on a slow Internet connection or with a slow computer. During the download, Bitcoin Core will use a significant part of your connection @@ -500,7 +500,7 @@ you want to use, click *Ok* to use the default. ![Bitcoin-Qt Welcome](/img/full-node/en-bitcoin-qt-welcome.png) -Bitcoin Core GUI will begin to download the block chain. This +Bitcoin Core GUI will begin to download the blockchain. This step will take at least several hours, and it may take a day or more on a slow Internet connection or with a slow computer. During the download, Bitcoin Core will use a significant part of your connection @@ -696,7 +696,7 @@ still need to configure inbound connections as described later in the ![Opening outgoing firewall for Bitcoin Core](/img/full-node/en-win7-bitcoin-core-outgoing-firewall.png) -Bitcoin Core GUI will begin to download the block chain. This +Bitcoin Core GUI will begin to download the blockchain. This step will take at least several hours, and it may take a day or more on a slow Internet connection or with a slow computer. During the download, Bitcoin Core will use a significant part of your connection @@ -894,7 +894,7 @@ still need to configure inbound connections as described later in the ![Opening outgoing firewall for Bitcoin Core](/img/full-node/en-win7-bitcoin-core-outgoing-firewall.png) -Bitcoin Core GUI will begin to download the block chain. This +Bitcoin Core GUI will begin to download the blockchain. This step will take at least several hours, and it may take a day or more on a slow Internet connection or with a slow computer. During the download, Bitcoin Core will use a significant part of your connection @@ -989,7 +989,7 @@ For example, to safely stop your node, run the following command: {{complete_list_of_commands_and_ibd}} -When Bitcoin Core daemon first starts, it will begin to download the block chain. This step will take at least several hours, and it may take a day or more on a slow Internet connection or with a slow computer. During the download, Bitcoin Core will use a significant part of your connection bandwidth. You can stop Bitcoin Core at any time using the stop command; it will resume from the point where it stopped the next time you start it. +When Bitcoin Core daemon first starts, it will begin to download the blockchain. This step will take at least several hours, and it may take a day or more on a slow Internet connection or with a slow computer. During the download, Bitcoin Core will use a significant part of your connection bandwidth. You can stop Bitcoin Core at any time using the stop command; it will resume from the point where it stopped the next time you start it.
*Optional: Start Your Node At Boot* @@ -1056,7 +1056,7 @@ you want to use, click Ok to use the default. ![Bitcoin Core Welcome](/img/full-node/en-osx-welcome-to-bitcoin-core.png) -Bitcoin Core GUI will begin to download the block chain. This +Bitcoin Core GUI will begin to download the blockchain. This step will take at least several hours, and it may take a day or more on a slow Internet connection or with a slow computer. During the download, Bitcoin Core will use a significant part of your connection diff --git a/img/dev/en-blockchain-overview.dot b/img/dev/en-blockchain-overview.dot index 10a28983fa..afa56ed104 100644 --- a/img/dev/en-blockchain-overview.dot +++ b/img/dev/en-blockchain-overview.dot @@ -56,5 +56,5 @@ _transactions0 -> _transactions1 -> _transactions2 [ style = "invis", minlen = 2 invis1 -> _transactions0 [ style = "invis", minlen = 1 ]; -label = "\nSimplified Bitcoin Block Chain"; +label = "\nSimplified Bitcoin Blockchain"; } diff --git a/img/dev/en-blockchain-overview.svg b/img/dev/en-blockchain-overview.svg index fea05ed6b6..a1c9ea5a3c 100644 --- a/img/dev/en-blockchain-overview.svg +++ b/img/dev/en-blockchain-overview.svg @@ -9,7 +9,7 @@ blockchain -Simplified Bitcoin Block Chain +Simplified Bitcoin Blockchain cluster_block0header Block 1 diff --git a/img/dev/en-blocks-first-flowchart.dot b/img/dev/en-blocks-first-flowchart.dot index 02e1fabd0f..8c98bd532b 100644 --- a/img/dev/en-blocks-first-flowchart.dot +++ b/img/dev/en-blocks-first-flowchart.dot @@ -12,7 +12,7 @@ edge [ penwidth = 1.75, fontname="Sans" ] node [ penwidth = 1.75, shape = "none", fontname="Sans"] graph [ penwidth = 1.75, fontname="Sans" ] -fsbc [ label = "Fully-Synced Block Chain?", style = "filled" ]; +fsbc [ label = "Fully-Synced Blockchain?", style = "filled" ]; listen [ label = "Listen For New Blocks (Inv)" ]; request_blocks [ label = "Request Blocks (GetData)" ]; request_invs [ label = "Request Inventories (GetBlocks)" ]; diff --git a/img/dev/en-blocks-first-flowchart.svg b/img/dev/en-blocks-first-flowchart.svg index 5b3192ff51..26c453e29f 100644 --- a/img/dev/en-blocks-first-flowchart.svg +++ b/img/dev/en-blocks-first-flowchart.svg @@ -14,7 +14,7 @@ fsbc -Fully-Synced Block Chain? +Fully-Synced Blockchain? listen diff --git a/img/dev/en-headers-first-flowchart.dot b/img/dev/en-headers-first-flowchart.dot index bed9abcac4..10750ad924 100644 --- a/img/dev/en-headers-first-flowchart.dot +++ b/img/dev/en-headers-first-flowchart.dot @@ -12,7 +12,7 @@ edge [ penwidth = 1.75, fontname="Sans" ] node [ penwidth = 1.75, shape = "none", fontname="Sans"] graph [ penwidth = 1.75, fontname="Sans" ] -fsbc [ label = "Fully-Synced Block Chain?", style = "filled" ]; +fsbc [ label = "Fully-Synced Blockchain?", style = "filled" ]; fshc [ label = "Fully-Synced Header Chain?", style = "filled" ]; more_headers_than_blocks [ label = "More Headers Than Blocks?", style = "filled" ]; listen_for_new_blocks [ label = "Listen For New Blocks (Inv)" ]; diff --git a/img/dev/en-headers-first-flowchart.svg b/img/dev/en-headers-first-flowchart.svg index f087ab6011..c56000e440 100644 --- a/img/dev/en-headers-first-flowchart.svg +++ b/img/dev/en-headers-first-flowchart.svg @@ -14,7 +14,7 @@ fsbc -Fully-Synced Block Chain? +Fully-Synced Blockchain? fshc diff --git a/img/dev/en-orphan-stale-definition.dot b/img/dev/en-orphan-stale-definition.dot index 6de8537c33..4b19235b31 100644 --- a/img/dev/en-orphan-stale-definition.dot +++ b/img/dev/en-orphan-stale-definition.dot @@ -38,6 +38,6 @@ subgraph cluster_toplabel { label = "Orphan blocks have no known parent, so they can't be validated" } -label = " \nStale blocks are valid but not part of the best block chain" +label = " \nStale blocks are valid but not part of the best blockchain" } diff --git a/img/dev/en-orphan-stale-definition.svg b/img/dev/en-orphan-stale-definition.svg index dab784ff53..1bd0c95fdf 100644 --- a/img/dev/en-orphan-stale-definition.svg +++ b/img/dev/en-orphan-stale-definition.svg @@ -10,7 +10,7 @@ _anonymous_0 -Stale blocks are valid but not part of the best block chain +Stale blocks are valid but not part of the best blockchain cluster_mainchain cluster_toplabel