"进阶交易脚本实战：多签名、付至脚本哈希"

需积分: 0 151 浏览量更新于2024-03-21 收藏 161KB DOCX 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

资源详情

资源推荐

P2SH 地址隐藏了所有的复杂性，因此，付款人看不到这个脚本。

7.3.2 P2SH 的优点

The P2SH feature offers the following benefits compared to the direct use of complex scripts in locking

outputs:

相比直接在锁定输出中使用复杂脚本来说，P2SH 具有以下优点。

� Complex scripts are replaced by shorter fingerprints in the transaction output, making the

transaction smaller.

在交易输出中，用短指纹替代了复杂脚本，使得交易更短。

� Scripts can be coded as an address, so the sender and the sender’s wallet don’t need complex

engineering to implement P2SH.

脚本能被编码为地址，所以，付款人和付款人的钱包不需要复杂的工作就能实现 P2SH。

� P2SH shifts the burden of constructing the script to the recipient, not the sender.

P2SH 把构建脚本的负担转移至收款方，而不是付款方。

� P2SH shifts the burden in data storage for the long script from the output (which additionally to

being stored on the blockchain is in the UTXO set) to the input (only stored on the blockchain).

P2SH 将长脚本数据存储的负担从输出（存储在 UTXO 集，耗费内存）转移至输入（存储在区块链上）。

� P2SH shifts the burden in data storage for the long script from the present time (payment) to a

future time (when it is spent).

P2SH 将长脚本数据存储的负担从现在（付款时）转移至未来（花费时）。

� P2SH shifts the transaction fee cost of a long script from the sender to the recipient, who has to

include the long redeem script to spend it.

P2SH 将长脚本的交易费从付款方转移至收款方。

7.3.3 赎回脚本和验证

Prior to version 0.9.2 of the Bitcoin Core client, Pay-to-Script-Hash was limited to the standard types of

bitcoin transaction scripts, by the IsStandard() function. That means that the redeem script presented in

the spending transaction could only be one of the standard types: P2PK, P2PKH, or multisig.

在 Bitcoin Core 客户端 0.9.2 版本之前，P2SH 被限制为标准类型的比特币交易脚本，通过 IsStandard()

函数。

这意味着，花费交易中的赎回脚本只能是标准类型：P2PK、P2PKH、多签名。

As of version 0.9.2 of the Bitcoin Core client, P2SH transactions can contain any valid script, making the

P2SH standard much more flexible and allowing for experimentation with many novel and complex

types of transactions.

从 0.9.2 版本开始，P2SH 交易可以包含任意有效的脚本，这使得 P2SH 标准更加灵活，可以实现许多新颖

和复杂的交易类型。

You are not able to put a P2SH inside a P2SH redeem script, because the P2SH specification is not

recursive. Also, while it is technically possible to include RETURN (see Data Recording Output (RETURN))

in a redeem script, as nothing in the rules prevents you from doing so, it is of no practical use because

executing RETURN during validation will cause the transaction to be marked invalid.

不能在一个 P2SH 赎回脚本中放一个 P2SH，因为 P2SH 规范不能递归。

还有，虽然在技术上可以在赎回脚本中包含 RETURN（因为规则并不阻止这么做），但这样做并不实用，因

为验证期间执行 RETURN 将导致交易无效。

Note that because the redeem script is not presented to the network until you attempt to spend a P2SH

output, if you lock an output with the hash of an invalid redeem script it will be processed regardless.

The UTXO will be successfully locked. However, you will not be able to spend it because the spending

transaction, which includes the redeem script, will not be accepted because it is an invalid script. This

creates a risk, because you can lock bitcoin in a P2SH that cannot be spent later. The network will accept

the P2SH locking script even if it corresponds to an invalid redeem script, because the script hash gives

no indication of the script it represents.

注意，因为只有在花费 P2SH 输出时，才向网络提供赎回脚本，所以，如果你用一个无效的赎回脚本的哈

希来锁定输出，它还是会被处理。

这个 UTXO 会被成功地锁定，但是你再也不能花费这笔资金，因为你无法提供有效的赎回脚本。

这造成了一个风险，因为你可能把比特币锁定在一个以后不能花费的 P2SH 中。

网络会接受 P2SH 锁定脚本，即使它对应的是一个无效的赎回脚本，因为脚本哈希对脚本没有给出任何指

示。

Warning：P2SH locking scripts contain the hash of a redeem script, which gives no clues as to the

content of the redeem script itself. The P2SH transaction will be considered valid and accepted even if

the redeem script is invalid. You might accidentally lock bitcoin in such a way that it cannot later be

spent.

警告：P2SH 锁定脚本包含一个赎回脚本的哈希，这个哈希对赎回脚本的内容没有提供任何线索。

P2SH 交易会被认为是有效的，并被接受，即使赎回脚本是无效的。

你可能会偶然把锁定了比特币，但以后却不能花费。

7.4 用于数据记录的输出（RETURN）

Data Recording Output (RETURN)

Bitcoin’s distributed and timestamped ledger, the blockchain, has potential uses far beyond payments.

Many developers have tried to use the transaction scripting language to take advantage of the security

and resilience of the system for applications such as digital notary services, stock certificates, and smart

contracts. Early attempts to use bitcoin’s script language for these purposes involved creating

transaction outputs that recorded data on the blockchain; for example, to record a digital fingerprint of a

file in such a way that anyone could establish proof-of-existence of that file on a specific date by

reference to that transaction.

比特币的分布式和时间戳账本（即区块链）的潜在应用不只是支付。

许多开发者试图使用交易脚本语言，把这个系统的安全和弹性用于其它应用，例如：数字公证服务、股票

凭证、智能合约。

把比特币脚本语言用于这些目的早期尝试涉及创建交易输出，用输出把数据记录在区块链中。

例如，用这种方法记录一个文件的数字指纹，则任何人可以用那个交易证明某天那个文件已经存在。

The use of bitcoin’s blockchain to store data unrelated to bitcoin payments is a controversial subject.

Many developers consider such use abusive and want to discourage it. Others view it as a demonstration

of the powerful capabilities of blockchain technology and want to encourage such experimentation.

这是一个有争议的话题：使用比特币的区块链来存储与比特币支付不相关的数据。

许多开发者认为这是滥用，并试图予以阻止。

另一些开发者则将之看做区块链技术强大功能的一个证明，并予以鼓励。

Those who object to the inclusion of nonpayment data argue that it causes "blockchain bloat,"

burdening those running full bitcoin nodes with carrying the cost of disk storage for data that the

blockchain was not intended to carry. Moreover, such transactions create UTXO that cannot be spent,

using the destination bitcoin address as a freeform 20-byte field. Because the address is used for data, it

doesn’t correspond to a private key and the resulting UTXO can never be spent; it’s a fake payment.

These transactions that can never be spent are therefore never removed from the UTXO set and cause

the size of the UTXO database to forever increase, or "bloat."

反对的人认为这样做会引致“区块链膨胀”，使全节点要存储与交易无关的数据。

此外，这种交易创建的 UTXO 不能被花费，它将目的比特币地址用作一个随意写的 20 字节字段。

因为这个地址保存的是数据，没有对应的私钥，因此不会花费这个 UTXO，它是一个假的支付。

因此，这些交易永远不会被花费，也不会从 UTXO 集中删除，导致 UTXO 数据库只会“膨胀”。

In version 0.9 of the Bitcoin Core client, a compromise was reached with the introduction of the RETURN

operator. RETURN allows developers to add 80 bytes of nonpayment data to a transaction output.

However, unlike the use of "fake" UTXO, the RETURN operator creates an explicitly provably

unspendable output, which does not need to be stored in the UTXO set. RETURN outputs are recorded

on the blockchain, so they consume disk space and contribute to the increase in the blockchain’s size,

but they are not stored in the UTXO set and therefore do not bloat the UTXO memory pool and burden

full nodes with the cost of more expensive RAM.

在 Bitcoin Core 客户端 0.9 版本中，通过引入 Return 操作码达成了妥协。

剩余58页未读，继续阅读

李诗旸

粉丝: 30
资源: 329

"进阶交易脚本实战：多签名、付至脚本哈希"

高级分形 - MetaTrader 5脚本.zip

高级 ADX - MetaTrader 4脚本.zip

装备制作脚本_079脚本_冒险岛079NPC脚本_

mql4 macd高级

mql5语言编程手册中文

python从事行业

安全电子商务系统总体设计

python与财务学习

通达信 python

python的就业前景有哪些？

分析一下 聚宽 vs 米筐 vs BigQuant vs 迅投QMT

Python的应用领域

有什么难忘的银行测试业务的bug?比较有技术含量的高级测试范围

python股票新闻公告

AFL文件

同花顺龙虎榜数据爬虫

python 闲鱼私信机器人

wind 金融客户端 python

vscode调试MQL5

pkcs11测试工具

最新资源

分析一下聚宽 vs 米筐 vs BigQuant vs 迅投QMT