Skip to content

lzpap/tips

 
 

Repository files navigation

Tangle Improvement Proposal (TIP) Repository

TIPs are improvement proposals for bettering the IOTA technology stack.

Building the IOTA ecosystem is a community effort, therefore we welcome anyone to propose, discuss and debate ideas that will later become formalized TIPs.

Propose new ideas

Do you have an idea how to improve the IOTA technology stack?

  • Head over to the discussions page to browse already submitted ideas or share yours!
  • Once your idea is discussed, you can submit a draft TIP (template here) as a PR to the repository.
  • You will receive feedback from the TIP Editors and review from core devs.
  • Once accepted, your TIP is merged as Draft.
  • It is your responsibility to drive its implementation and to present a clear plan on how the new feature will be adopted by the network.
  • Once implementation is ready and testing yields satisfactory result, the TIP becomes Proposed.
  • Proposed TIPs that are supported by majority of the network become Active.

You may find more information about the TIP Process in TIP-1.

Pending TIPs

The following TIPs are currently being discussed and are awaiting further contribution:

# Title Description Type Layer Status
18 Multi-Asset Ledger and ISC Support Transform IOTA into a multi-asset ledger that supports running IOTA Smart Contracts Standards Core Draft
19 Dust Protection Based on Byte Costs Prevent bloating the ledger size with dust outputs Standards Core Draft
20 Transaction Payload with New Output Types UTXO-based transaction structure with TIP-18 Standards Core Draft
21 Serialization Primitives Introduce primitives to describe the binary serialization of objects Standards Core Draft
22 Protocol Parameters Describes the global protocol parameters for the IOTA protocol Standards Core Draft

Accepted TIPs (as of 2022-01-16)

# Title Description Type Layer Status
1 TIP Process Purpose and guidelines of the contribution framework Process - Active
2 White Flag Ordering Mitigate conflict spamming by ignoring conflicts Standards Core Active
3 Uniform Random Tip Selection Perform fast tip-selection to increase message throughput Standards Core Active
4 Milestone Merkle Validation Add Merkle tree hash to milestone for local ledger state verification Standards Core Active
5 Binary To Ternary Encoding Define the conversion between binary and ternary data Standards Core Active
6 Tangle Message Generalization of the Tangle transaction concept Standards Core Active
7 Transaction Payload UTXO-based transaction structure Standards Core Active
8 Milestone Payload Coordinator issued milestone structure with Ed25519 authentication Standards Core Active
9 Local Snapshot File Format File format to export/import ledger state Standards Interface Active
10 Mnemonic Ternary Seed Represent ternary seed as a mnemonic sentence Standards IRC Obsolete
11 Bech32 Address Format Extendable address format supporting various signature schemes and address types Standards Interface Active
12 Message PoW Define message proof-of-work as a means to rate-limit the network Standards Core Active
13 REST API Node REST API routes and objects in OpenAPI Specification Standards Interface Active
14 Ed25519 Validation Adopt ZIP-215 to explicitly define Ed25519 validation criteria Standards Core Active
15 Dust Protection Prevent bloating the ledger size with to dust outputs Standards Core Active
16 Event API Node event API definitions in AsyncAPI Specification Standards Interface Active
17 Wotsicide Define migration from legacy WOTS addresses to post-Chrysalis Phase 2 network Standards Core Active
18 Multi-Asset Ledger and ISC Support Transform IOTA into a multi-asset ledger that supports running IOTA Smart Contracts Standards Core Draft

Need help?

If you want to get involved in the community, need help getting started, have any issues related to the repository or just want to discuss blockchain, distributed ledgers, and IoT with other people, feel free to join our Discord.

About

RFCs (Requests for comments) for the IOTA protocol. RFCs can be accepted by individual node software implementations.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Shell 100.0%