协议说明 - 版本历史

Simapple：/* Transaction Verification */

2011-05-30T11:45:58Z

Transaction Verification

←上一版本		2011年5月30日 (一) 11:45的版本
第53行：		第53行：
	Public keys (in scripts) are given as 04 <x> <y> where x and y are 32 byte strings representing the coordinates of a point on the curve. Signatures use [http://en.wikipedia.org/wiki/Distinguished_Encoding_Rules DER encoding] to pack the r and s components into a single byte stream (because this is what OpenSSL produces by default). -->		Public keys (in scripts) are given as 04 <x> <y> where x and y are 32 byte strings representing the coordinates of a point on the curve. Signatures use [http://en.wikipedia.org/wiki/Distinguished_Encoding_Rules DER encoding] to pack the r and s components into a single byte stream (because this is what OpenSSL produces by default). -->

	=== Transaction Verification ===		=== Transaction Verification (交易认证) ===
	{{See also\|OP_CHECKSIG}}		{{See also\|OP_CHECKSIG}}

	The first transaction of a block is usually the generating transaction, which do not include any "in" transaction, and generate bitcoins (from fees for example) usually received by whoever solved the block containing this transaction.		一个block的第一笔交易通常是生成比特币的交易，它不包含任何输入交易，而是生成比特币，这些比特币通常被完成这个block的人获得。这样的交易被称作“coinbase交易”。由于每个block只有一个coinbase交易，它无需执行脚本即被bitcoin客户端接受。
	Such transactions are called a "coinbase transaction" and are accepted by bitcoin clients without any need to execute scripts, provided there is only one per block.		<!-- The first transaction of a block is usually the generating transaction, which do not include any "in" transaction, and generate bitcoins (from fees for example) usually received by whoever solved the block containing this transaction.
			Such transactions are called a "coinbase transaction" and are accepted by bitcoin clients without any need to execute scripts, provided there is only one per block. -->

	If a transaction is not a coinbase, it references previous transaction hashes as input, and the index of the other transaction's output used as input for this transaction.		如果一笔交易不是coinbase交易，它会引用前一笔交易的散列和其他交易的输出作为这笔交易的输入，执行这笔交易输入部分的脚本。然后引用的交易输出部分的脚本会被执行。如果栈顶的元素为真则交易被认可。
			<!-- If a transaction is not a coinbase, it references previous transaction hashes as input, and the index of the other transaction's output used as input for this transaction.
	The script from the in part of this transaction is executed.		The script from the in part of this transaction is executed.
	Then the script from the out part of the referenced transaction is executed.		Then the script from the out part of the referenced transaction is executed.
	It is considered valid if the top element of the stack is true.		It is considered valid if the top element of the stack is true. -->

	=== Addresses (地址) ===		=== Addresses (地址) ===

2011年5月29日 (日) 10:58 Simapple

2011-05-29T10:58:15Z

显示更改

Simapple：/* block */

2011-05-29T10:54:46Z

block

←上一版本		2011年5月29日 (日) 10:54的版本
第622行：		第622行：
	\| 4 \|\| bits \|\| uint32_t \|\| 这一block的计算难度 <!-- The calculated difficulty target being used for this block -->		\| 4 \|\| bits \|\| uint32_t \|\| 这一block的计算难度 <!-- The calculated difficulty target being used for this block -->
	\|-		\|-
	\| 4 \|\| nonce \|\| uint32_t \|\| ~~用于生成这一block的临时量~~ <!-- The nonce used to generate this block… to allow variations of the header and compute different hashes -->		\| 4 \|\| nonce \|\| uint32_t \|\| 用于生成这一block的nonce值 <!-- The nonce used to generate this block… to allow variations of the header and compute different hashes -->
	\|-		\|-
	\| ? \|\| txn_count \|\| var_int \|\| 交易数量 <!-- Number of transaction entries -->		\| ? \|\| txn_count \|\| var_int \|\| 交易数量 <!-- Number of transaction entries -->
第629行：		第629行：
	\|}		\|}

			用于识别每个block的SHA256散列使用这个结构的前6个字段计算(version, prev_block, merkle_root, timestamp, bits, nonce, 后接标准 SHA256 填充, 共2个64字节块)而非整个block。计算散列是SHA256算法只需要处理2个块。由于nonce字段在第二个块里，在开采过程中，第一个块保持不变。因此只需要处理第二个块。但是bitcoin散列是二次散列，每个开采循环需要2轮SHA256计算。
	The SHA256 hash that identifies each block (and which must have a run of 0 bits) is calculated from the first 6 fields of this structure (version, prev_block, merkle_root, timestamp, bits, nonce, and standard SHA256 padding, making two 64-byte chunks in all) and ''not'' from the complete block. To calculate the hash, only two chunks need to be processed by the SHA256 algorithm. Since the ''nonce'' field is in the second chunk, the first chunk stays constant during mining and therefore only the second chunk needs to be processed. However, a Bitcoin hash is the hash of the hash, so two SHA256 rounds are needed for each mining iteration.		<!-- The SHA256 hash that identifies each block (and which must have a run of 0 bits) is calculated from the first 6 fields of this structure (version, prev_block, merkle_root, timestamp, bits, nonce, and standard SHA256 padding, making two 64-byte chunks in all) and ''not'' from the complete block. To calculate the hash, only two chunks need to be processed by the SHA256 algorithm. Since the ''nonce'' field is in the second chunk, the first chunk stays constant during mining and therefore only the second chunk needs to be processed. However, a Bitcoin hash is the hash of the hash, so two SHA256 rounds are needed for each mining iteration. -->

	=== headers ===		=== headers ===

2011年5月29日 (日) 10:26 Simapple

2011-05-29T10:26:34Z

←上一版本		2011年5月29日 (日) 10:26的版本
第167行：		第167行：
	\|}		\|}

	~~一个网络地址结构的十六进制转储示例~~		一个网络地址结构示例
	<!-- Hexdump example of Network address structure -->		<!-- Hexdump example of Network address structure -->

第280行：		第280行：
	\|}		\|}

	~~一个version消息的十六进制转储示例~~(请注意version消息头没有校验和)		一个version消息示例(请注意version消息头没有校验和)
	<!-- Hexdump example of version message (note the message header for this version message does not have a checksum): -->		<!-- Hexdump example of version message (note the message header for this version message does not have a checksum): -->

第328行：		第328行：
	<!-- The ''verack'' message is sent in reply to ''version'' for clients >= 209. This message consists of only a [[#Message structure (消息结构)\|message header]] with the command string "verack". -->		<!-- The ''verack'' message is sent in reply to ''version'' for clients >= 209. This message consists of only a [[#Message structure (消息结构)\|message header]] with the command string "verack". -->

	~~verack消息的十六进制转储：~~		verack消息示例：
	<!-- Hexdump of the verack message: -->		<!-- Hexdump of the verack message: -->

第359行：		第359行：
	<!-- '''Note''': Starting version 31402, addresses are prefixed with a timestamp. If no timestamp is present, the addresses should not be relayed to other peers, unless it is indeed confirmed they are up. -->		<!-- '''Note''': Starting version 31402, addresses are prefixed with a timestamp. If no timestamp is present, the addresses should not be relayed to other peers, unless it is indeed confirmed they are up. -->

	~~addr消息的十六进制转储示例~~		addr消息示例
	<!-- Hexdump example of ''addr'' message: -->		<!-- Hexdump example of ''addr'' message: -->
	<pre>		<pre>

Simapple：/* verack */

2011-05-29T10:23:25Z

verack

←上一版本		2011年5月29日 (日) 10:23的版本
第325行：		第325行：
	=== verack ===		=== verack ===

	版本不低于209的客户端在应答version消息时发送verack消息。这个消息仅包含一个command为"verack"的[[#Message \|消息头]]		版本不低于209的客户端在应答version消息时发送verack消息。这个消息仅包含一个command为"verack"的[[#Message (消息)\|消息头]]
	<!-- The ''verack'' message is sent in reply to ''version'' for clients >= 209. This message consists of only a [[#Message structure (消息结构)\|message header]] with the command string "verack". -->		<!-- The ''verack'' message is sent in reply to ''version'' for clients >= 209. This message consists of only a [[#Message structure (消息结构)\|message header]] with the command string "verack". -->

Simapple：/* verack */

2011-05-29T10:22:47Z

verack

←上一版本		2011年5月29日 (日) 10:22的版本
第325行：		第325行：
	=== verack ===		=== verack ===

	版本不低于209的客户端在应答version消息时发送verack消息。这个消息仅包含一个command为"verack"的[[#Message ~~structure~~\|消息头]]		版本不低于209的客户端在应答version消息时发送verack消息。这个消息仅包含一个command为"verack"的[[#Message \|消息头]]
	<!-- The ''verack'' message is sent in reply to ''version'' for clients >= 209. This message consists of only a [[#Message structure (消息结构)\|message header]] with the command string "verack". -->		<!-- The ''verack'' message is sent in reply to ''version'' for clients >= 209. This message consists of only a [[#Message structure (消息结构)\|message header]] with the command string "verack". -->

Simapple：/* 常用标准 */

2011-05-29T10:21:50Z

常用标准

←上一版本		2011年5月29日 (日) 10:21的版本
第6行：		第6行：
	本文档中用到的类名称来自C99标准		本文档中用到的类名称来自C99标准

	==~~常用标准~~==		==共用标准==

	=== Hashs (散列) ===		=== Hashs (散列) ===

Simapple：/* Message structure (消息结构) */

2011-05-29T10:21:21Z

Message structure (消息结构)

←上一版本		2011年5月29日 (日) 10:21的版本
第87行：		第87行：
	<!-- Almost all integers are encoded in little endian. Only IP or port number are encoded big endian. -->		<!-- Almost all integers are encoded in little endian. Only IP or port number are encoded big endian. -->

	=== Message ~~structure~~ (~~消息结构~~) ===		=== Message (消息) ===

	{\|class="wikitable"		{\|class="wikitable"

Simapple：/* Network address (网络地址) */

2011-05-29T10:18:01Z

Network address (网络地址)

←上一版本		2011年5月29日 (日) 10:18的版本
第157行：		第157行：
	! 字段尺寸 !! 描述 !! 数据类型 !! 说明		! 字段尺寸 !! 描述 !! 数据类型 !! 说明
	\|-		\|-
	\| 8 \|\| services \|\| uint64_t \|\| 与[[#version\|version 消息]中的service(s)相同 <!-- same service(s) listed in [[#version\|version]]? -->		\| 8 \|\| services \|\| uint64_t \|\| 与[[#version \|version 消息]]中的service(s)相同 <!-- same service(s) listed in [[#version\|version]]? -->
	\|-		\|-
	\| 16 \|\| IPv6/4 \|\| char[16] \|\| Ipv6地址，以网络字节顺序存储。官方客户端仅支持IPv4，仅读取最后4个字节以获取IPv4地址。IPv4地址以16字节的[http://en.wikipedia.org/wiki/IPv6#IPv4-mapped_IPv6_addresses IPv4映射位址]格式写入结构。(12字节 ''00 00 00 00 00 00 00 00 00 00 FF FF'', 后跟4 字节IPv4地址)		\| 16 \|\| IPv6/4 \|\| char[16] \|\| Ipv6地址，以网络字节顺序存储。官方客户端仅支持IPv4，仅读取最后4个字节以获取IPv4地址。IPv4地址以16字节的[http://en.wikipedia.org/wiki/IPv6#IPv4-mapped_IPv6_addresses IPv4映射位址]格式写入结构。(12字节 ''00 00 00 00 00 00 00 00 00 00 FF FF'', 后跟4 字节IPv4地址)

Simapple：/* Network address (网络地址) */

2011-05-29T10:17:41Z

Network address (网络地址)

←上一版本		2011年5月29日 (日) 10:17的版本
第157行：		第157行：
	! 字段尺寸 !! 描述 !! 数据类型 !! 说明		! 字段尺寸 !! 描述 !! 数据类型 !! 说明
	\|-		\|-
	\| 8 \|\| services \|\| uint64_t \|\| 与[[#version 消息\|version]]中的service(s)相同 <!-- same service(s) listed in [[#version\|version]]? -->		\| 8 \|\| services \|\| uint64_t \|\| 与[[#version\|version 消息]中的service(s)相同 <!-- same service(s) listed in [[#version\|version]]? -->
	\|-		\|-
	\| 16 \|\| IPv6/4 \|\| char[16] \|\| Ipv6地址，以网络字节顺序存储。官方客户端仅支持IPv4，仅读取最后4个字节以获取IPv4地址。IPv4地址以16字节的[http://en.wikipedia.org/wiki/IPv6#IPv4-mapped_IPv6_addresses IPv4映射位址]格式写入结构。(12字节 ''00 00 00 00 00 00 00 00 00 00 FF FF'', 后跟4 字节IPv4地址)		\| 16 \|\| IPv6/4 \|\| char[16] \|\| Ipv6地址，以网络字节顺序存储。官方客户端仅支持IPv4，仅读取最后4个字节以获取IPv4地址。IPv4地址以16字节的[http://en.wikipedia.org/wiki/IPv6#IPv4-mapped_IPv6_addresses IPv4映射位址]格式写入结构。(12字节 ''00 00 00 00 00 00 00 00 00 00 FF FF'', 后跟4 字节IPv4地址)

协议说明 - 版本历史

Simapple：​/* Transaction Verification */

2011年5月29日 (日) 10:58 Simapple

Simapple：​/* block */

2011年5月29日 (日) 10:26 Simapple

Simapple：​/* verack */

Simapple：​/* verack */

Simapple：​/* 常用标准 */

Simapple：​/* Message structure (消息结构) */

Simapple：​/* Network address (网络地址) */

Simapple：​/* Network address (网络地址) */

Simapple：/* Transaction Verification */

Simapple：/* block */

Simapple：/* verack */

Simapple：/* verack */

Simapple：/* 常用标准 */

Simapple：/* Message structure (消息结构) */

Simapple：/* Network address (网络地址) */

Simapple：/* Network address (网络地址) */