本文介绍了公证变更交易从验证到非验证公证的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在进行从验证公证人到一组新的非验证公证人的公证变更交易时,新的一组非验证公证人如何了解以前的交易?。

while doing a notary change transaction from validating notaries to a new set of non validating notaries, how does the new set of non-validating notaries learn about the previous transactions?.

它们是否仅获得先前交易的哈希或整个交易依赖关系图?

Do they get only the hashes of previous transactions or the entire transaction dependency graph?

推荐答案

新公证人不会学习

相反,我们有以下过程:

Instead, we have the following process:


  • 具有哈希值 2772BE 和公证人 NotaryA 的交易被提交到分类账

  • 有人希望将此交易的第一个输出状态(表示为< 2772BE,0> )转移到 NotaryB

  • 它们使用单​​个输入< 2772BE,0> 组成公证更改交易。假设此公证更改交易的哈希值为 35D0A5

  • NotaryA 符号此交易,将其输入< 2772BE,0> 标记为已使用

  • 但是,此交易还会创建一个输出状态< 35D0A5,0> ,指向 NotaryB

  • NotaryA 的>< 2772BE,0> 。但是指向 NotaryB < 35D0A5,0> 未使用

  • A transaction with hash 2772BE and notary NotaryA is committed to the ledger
  • Someone wants to transfer the first output state of this transaction (denoted <2772BE, 0>) to NotaryB
  • They form a notary change transaction with a single input, <2772BE, 0>. Let's say the hash of this notary change transaction is 35D0A5
  • NotaryA signs this transaction, marking its input <2772BE, 0> as spent
  • However, this transaction also creates one output state, <35D0A5, 0>, pointing to NotaryB
  • <2772BE, 0>, which pointed to NotaryA, is now spent. But <35D0A5, 0>, which points to NotaryB, is unspent

通过这种方式,我们已将州转移到新的公证处,以防止重复支出。

In this way, we have transferred the state to a new notary in a way that prevents double-spends.

这篇关于公证变更交易从验证到非验证公证的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

06-21 06:01