Skip to content
This repository was archived by the owner on Nov 13, 2024. It is now read-only.

Fix in-page links #1369

Merged
merged 3 commits into from
Sep 26, 2022
Merged

Fix in-page links #1369

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ae5c619
Signature Scope & WitnessRule
Hecate2 Sep 21, 2022
9c43291
fix in-page links
Hecate2 Sep 21, 2022
ea56cb6
Merge branch 'master' into jump
Hecate2 Sep 21, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/en-us/basic/concept/transaction.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ The version allows the transaction structure to be updated to make it backward c

The first field is the script hash of the transaction sender account. Since UTXO model has been deprecated in Neo N3 and the native assets NEO and GAS turned into NEP-17 assets, the input and outputs fields are no longer recorded in the transaction structure, instead, the `sender` is used to track the sender of the transaction.

The rest fields are used to define the effective scope of signature. When checkwitness is used for transaction verification, cosigners except the transaction sender need to define the scope of their signature. See [Signature Scope](#Signature Scope) for details.
The rest fields are used to define the effective scope of signature. When checkwitness is used for transaction verification, cosigners except the transaction sender need to define the scope of their signature. See [Signature Scope](#signature-scope) for details.

| Field | Description | Type |
| ------------------ | ------------------------------------------------------------ | ---------------- |
Expand Down Expand Up @@ -164,7 +164,7 @@ When constructing a transaction, you need to specify the field `scopes` in `sign
| 0x10 | `CustomContracts` | The signature is only effective to the specified contract script. It can be used in conjunction with CalledByEntry. |
| 0x20 | `CustomGroups` | The signature is effective to contracts in the group. It can be used in conjunction with CalledByEntry. |
| 0x80 | `Global` | The signature is globally effective. The risk is extremely high because the contract may transfer all assets in the address. Only choose it when the contract is extremely trusted. |
| 0x40 | `WitnessRules` | You need to specify the rule and scope. See [WitnessRule](#WitnessRule) |
| 0x40 | `WitnessRules` | You need to specify the rule and scope. See [WitnessRule](#witnessrule) |

For better understanding, suppose there is a contract invocation chain: **[entry]->[Contract A]->[Contract B]->[Contract C]...->[Target]**

Expand Down
2 changes: 1 addition & 1 deletion docs/zh-cn/basic/concept/transaction.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ version属性允许对交易结构进行更新，使其具有向后兼容性。
### signers
signers中的第一个字段为交易发起账户的地址哈希。由于Neo N3弃用了UTXO模型，仅保留有账户余额模型，原生资产NEO和GAS的转账交易统一为NEP-17资产操作方式，因此交易结构中不再记录inputs和outputs字段，通过signers字段来跟踪交易的发送方。

signers中余下的字段定义了签名的作用范围。当 checkwitness 用于交易验证时，除交易发送者 sender 外，其他的 signers 都需要定义其签名的作用范围。详情请参见 [签名作用域](#签名作用域)。
signers中余下的字段定义了签名的作用范围。当 checkwitness 用于交易验证时，除交易发送者 sender 外，其他的 signers 都需要定义其签名的作用范围。详情请参见[签名作用域](#签名作用域)。

| 字段 | 说明| 类型|
|--------------|------------------| --|
Expand Down
2 changes: 1 addition & 1 deletion docs/zh-cn/gettingstarted/develop.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ dotnet new -i Neo3.SmartContract.Templates

![](assets\extension.png)

4. 打开 `Nep17` 目录中的 Nep17 模板文件，参考前文 [编写 NEP17 代码](#编写-nep17-代码)。
4. 打开 `Nep17` 目录中的 Nep17 模板文件，参考前文 [编写 NEP17 代码](#编写-nep17代码)。

相对于 Neo Legacy 来说， Neo N3 的 NEP17 合约模板有以下改动：

Expand Down