修改： 拼接r s v值获取完整签名值时的拼接顺序错误及补充拼接时对v值的特殊说明 #282
Conversation
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
vivian1912
reviewed
Jan 8, 2026
docs/mechanism-algorithm/account.md
Outdated
| * **计算 `v` 值**：`v` 值是恢复标志符，由于 `r` 值有取模运算以及椭圆曲线的对称性，如果只有 `r` 值，一个 `r` 最多可以恢复出四个 `K`。`v` 值的取值范围是 `0、1、2、3` 四个整数，历史上为了和以太坊保持一致，最后的 `v` 值会在 `0、1、2、3` 的基础上再加 `27`，即最后 `v` 值的取值范围是 `27、28、29、30`。有了确定的 `v`，就可以恢复出唯一的 `K`。`v` 为 1 个字节。 | ||
|
|
||
| 4. 将签名结果 `r`，`s`，`v` 拼接后添加到交易中，拼接顺序为 `v || r || s`。 | ||
| 4. 将 `r`，`s`，`v` 值拼接后得到完整的签名值添加到交易中，拼接顺序为 `r || s || v`。需要注意的是拼接时不对`v`值作加`27`处理，使用标准的`0、1、2、3` |
Contributor
There was a problem hiding this comment.
新加部分是不是可以去掉？因为TRON 签名的 v 可以为0、1 或 27、28 两种。是否可以改一下第3步中的 计算v值 那里？
There was a problem hiding this comment.
签名如果以r s v结构出现的话 也就是sig.v值是标准值加27 如果签名以拼接形式出现也就是在交易里看到的那种 是以标准值作为拼接元素。一般代码里看到的v都是加了27的，标准值的时候一般叫recID。不过这个建议很好，拼接的描述用recID更好，而不是v值不作加27处理的描述，然后v值的计算那儿先写就算recId，再对recid作加27处理得到v值。
vivian1912
approved these changes
Jan 9, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.