Skip to content

Update tips.md#600

Open
GordonLtron wants to merge 2 commits into
tronprotocol:masterfrom
GordonLtron:TIP-Specification-and-Guidelines
Open

Update tips.md#600
GordonLtron wants to merge 2 commits into
tronprotocol:masterfrom
GordonLtron:TIP-Specification-and-Guidelines

Conversation

@GordonLtron
Copy link
Copy Markdown
Contributor

Review of TIP Specification and Guidelines

This PR contains several inconsistencies between the defined rules and the provided header templates, as well as minor typographical errors that need immediate correction before merging.

Standardize Naming Conventions:

  • Standard vs. Standards: You use Standard Track in the text but Standards Track in the TIP Header template. Standardize this to Standards Track globally.
  • TVM vs. VM: You list TVM under Standard Track categories, but the TIP Header template specifies VM. Standardize to TVM to be precise (TRON Virtual Machine).

Fix the Incomplete Status List in the TIP Header:
The status field in the TIP Header section is missing half of the valid statuses you defined earlier in the document.

  • Current: status: <Draft | Last Call | Accepted | Final | Deferred>
  • Change to: status: <Draft | Last Call | Accepted | Final(non-core) | Final(core) | Active | Abandoned | Rejected | Deferred>

Wording improvements for clarity:

  • Change building consensus for the TIP to building consensus around the TIP.
  • Under the Implementation section, change the sentence to: This section is optional before a TIP reaches Accepted status, but mandatory before it transitions to Final status.

Please resolve these discrepancies so developers have a single, unified source of truth for the TIP template.

Comment thread docs/developers/tips.md Outdated

TIPs are primarily categorized into two types: `Standard Tracks` and `Informational`.

* **`Standard Tracks`**: These TIPs describe changes that affect how TRON is implemented, such as modifications to block or transaction validity rules, proposed application standards, or any changes that affect the interoperability of TRON applications. `Standard Tracks` TIPs can be further subdivided into the following categories:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggest to use Standards Track (not Standard Tracks) to stay consistent with the EIP

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants