修改： 固化需要的19个不同sr包括区块生产者#278
Merged
Benson0224 merged 2 commits intotronprotocol:masterfrom Feb 5, 2026
Merged
Conversation
vivian1912
reviewed
Dec 24, 2025
| 此处对未确认状态区块的“认可”方式是：其他超级代表在该区块之后生产后续区块。例如，如图 d 所示，当超级代表 C 生产了第 103 块后，超级代表 E 在第 103 块的基础上生产了第 104' 块，超级代表 G、A、B 分别生产了第 105'、106'、107' 块，这些实质上都是第 103 块的后续区块，因此也是对 C 生产的第 103 块的认可。 | ||
|
|
||
| 由此可知，当高度为 121 的区块被生产出来时，第 103 块就成为了固化块，因为它此时已经有了 19 个后续区块。需要强调的是：生产这 19 个区块的超级代表必须**互不相同**，并且与生产第 103 个区块的超级代表也**不同**。 | ||
| 由此可知，当高度为 121 的区块被生产出来时，第 103 块就成为了固化块，因为它此时已经有了 18 个后续区块。需要强调的是：生产这 18 个区块的超级代表必须**互不相同**，并且与生产第 103 个区块的超级代表也**不同**，这样就保证这个区块获得了19个不同的SR的确认，19个SR包括区块的生产者。 |
Contributor
There was a problem hiding this comment.
是的，确实是这样，对于一个区块，如果有其他18个不同的SR基于它生产了后续区块，那么这个区块就被确认了。但是基于上面的图例来看的话，后续的某些区块存在相同SR产块的情况，那么这段话描述的可能就会有歧义。
是否可以不使用图例中的区块号，而是使用n这样的表述？或者再修改/增加一下图例？
kuny0707
approved these changes
Feb 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.