Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update TIP-20: Add network ID to essence #1

Merged
merged 1 commit into from
Jan 18, 2022
Merged

Update TIP-20: Add network ID to essence #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 8 additions & 0 deletions tips/TIP-0020/tip-0020.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -92,6 +92,13 @@ The following table describes the entirety of a _Transaction Payload_ in its ser
Set to <strong>value 0</strong> to denote a <i>Transaction Essence</i>.
</td>
</tr>
<tr>
<td>Network ID</td>
<td>uint64</td>
<td>
The unique value denoting whether the message was meant for mainnet, testnet, or a private networks. The <code>Network ID</code> should usually match the corresponding field of the encapsulating message, but this is not enforced.
</td>
</tr>
<tr>
<td>Inputs Count</td>
<td>uint16</td>
Expand Down Expand Up @@ -396,6 +403,7 @@ The following criteria defines whether a payload passes the syntactical validati

* Essence:
* `Transaction Type` value must denote a _Transaction Essence_.
* `Network ID` must match the value of the current network.
* Inputs:
* `Inputs Count` must be 0 < x ≤ `Max Inputs Count`.
* For each input the following must be true:
Expand Down