TAO Roadmap: Difference between revisions

From Nexus Wiki
Jump to navigation Jump to search
← Older edit
No edit summary
update roadmap
 
Line 1: Line 1:
= Tritium =
= TAO Roadmap =


== Trust System ==
Our roadmap shows the progress made in each of the core stages of the TAO Framework which include the deployment of the Three-Dimensional Chain (3DC). Each letter represents one of the three consensus upgrades that correspond to the addition of a lock level on the 3DC.


This milestone marks the introduction of the new trust key decay rate, with trust decreasing 3 times faster than it accrues. Replacing the hard 24-hour time limit in September 2018, the new decay rate gives staking wallets greater ability to retain trust and more accurately reflects the effort invested in securing the blockchain.
== The roadmap to success ==


Released 2018-09-16
=== What are our major goals? ===


== LISP ==
==== Mobile and Web Dapps ====


The Locator/ID Separation Protocol is an important network protocol that allows one to control their IP addressing, without relying on ISPs for allocation.
* Mobile Wallet Official Release
* Mobile P2P Quantum Resistant Encrypted Chat App with Programmable chat rooms and user authentication
* Mobile Wallet additions to allow Remote Sessions for using Mobile Wallet and/or Desktop Wallet as a 2FA source
* Decentralized Search Engine (https://nexus.io/search) for censorship free search and personalized results based on local data. No tracking, no ads, no censorship. Reputation and results ordering maintained on-chain
* LLD and LLP Service Layer for use in Web-Apps and also accessible through the LLL-TAO API System
* Mobile P2P and decentralized Uber dapp with 0% fees, on-chain reputation, and collateralized delivery functionality
* Mobile P2P DEX Interface for trading tokens on Nexus or Hybrid/Sister chains in a mobile Dapp
* Mobile P2P decentralized Geo-Spacial markets where you can buy and sell locally any legal product(s). This combines with the P2P decentralized delivery system so that goods can be transported as another additional revenue for drivers
* Mobile Filesystem Backup to use LLL-TAO File System to backup files on your device and allow access with the Nexus Dapp Suite
* LX-OS Microkernel with Linux Compatibility Layer to run certain flavors of Android OS such as Graphene and allow hardware compatibility and security beyond the Google Pixel


Released 2019-01-31
== Tritium++ ==


== Legacy Mode ==
=== 5.1.x ===


Full update to Nexus Core software supporting Legacy blockchain operation. This mode features fast sync times, instant loading, and a small memory and disk footprint.
==== Mobile Wallet ====


Released 2019-06-26
* Final Bugfixes to get Mobile wallet released


== Interface / Wallet ==
=== 5.2 ===


The Nexus interface supports full wallet function. Modular functionality allows custom themes and addon modules such as Binance trading, multi-coin storage, a block explorer, Tritium features, and anything module developers might dream up.
* SQL Language Updates: Upgrades to the SQL language in the API to add additional functionality and operators
* Removal of OpenSSL: Complete Removal of OpenSSL using our own embedded TLS and Cryptography in the LLC
* Integration of O(!) LLD Service: Integrate O(!) LLD Service completely into the complete Network
* New APIs: P2P Messenger API, Crypto API


Released 2019-06-26
=== 5.3 ===


== API / SDK ==
* Remote Login System and API, Sigchain Ledger VM to create programmable access patterns to your sigchain with multiple sets of credentials


Our API gives developers access to a wide set of features available through a simple HTTP interface. This provides easy access to smart contracts that can be embedded directly into web applications and existing login systems.
=== 6.0 ===


Released 2019-11-05
* Hard Fork for Difficulty Adjustments, Security Updates, Initial Filesystem Hosting, and Initial Augmented Contracts


= Tritium++ =
=== 6.1 ===


== Hybrid Mode ==
* Post hard fork maintenance, DSL for Initial Augmented Contracts, Signature Chaining Space Reduction Complete


An important feature, hybrid mode is capable of forming an individual network out of the box, making it a highly useful tool for businesses that wish to utilize our blockchain technology, while retaining high levels of privacy.
=== 7.0 ===


Release 2021-09-07
* Hard Fork for Security Updates, Pooled Staking, Incentivized Hybrid Mode, Final Incentivized Filesystem, and Final Augmented Contracts


== Contract Domain Specific Languages ==
=== 7.1 ===


Contract-specific programming languages will be provided that will include internal safety mechanisms such as catching overflows to allow more complex contract development, while remaining less prone to error.
* Post hard fork maintenance, Final DSL for Augmented Contracts


== P2P Market API ==
=== 8.0 ===


The Decentralized Exchange will sit mainly in the Logical / Interface layers, with the exchange itself being facilitated by a conditional contract on the Operations layer. The DEX will be able to be used to trade tokens and assets listed on Nexus, promoting the development of decentralized marketplaces where any type of asset can be traded in a truly free, peer to peer manner without a need for a custodian service. There is no authority that designates the process of listing, and there are no other parties involved in the exchange other than the buyer and the seller.
* Hard Fork for implementation of Starfish Funding Model as an on-chain enforced protocol, currently allocation is voted via trust keys on-chain but is not enforced by the ledger


Released 2023-04-26
== Amine ==


== Mobile Wallet ==
=== 9.0 ===


Our official mobile wallet will be developed using most of the software that runs the desktop wallet, with changes to the interface to be more mobile friendly, and daemon packages that incrementally will be improved over time to enable more contract functionality and staking. The Mobile Wallet will still have the modular design of the Nexus Wallet, so that developers can extend it with their DApps by simply deploying new modules to the Wallet.
* Hard Fork to add additional hash reference ID for an Amine Shard(s)
* Initially 4 shards will be created using pBFT and nPoW + Trust that reference the main chain
* A user will be required to opt-in to a shard to process within in it, or can opt-out and process transactions using the Tritium Protocol
* This will be ongoing throughout Amine if any adjustments need to be made
* Hard Fork to deprecate UTxO, retain support for it in processing but not allow new UTxO transactions to be made


== Pooled Staking ==
=== 9.1.x ===


As more people continue to join the staking process, the network becomes more secure through the increase in the Trust channel difficulty. Though this provides benefits to the network as a whole, it constantly drives up the required amount of coins to maintain a Trust key. Pooled Staking solves this by giving smaller balances the ability to collaborate with peers, ultimately resulting in increased staking access to the regular user, and higher network security. This approach does not require a central service, since it will work as a sub network inside Nexus, that itself comes to consensus on the Trust keys to be included. This is a pure, decentralized, staking protocol that will benefit the entire network as a whole.
* Post Hard-Fork Maintenance while releasing TAO only mode where we can truncate the chain at the first Tritium Block, and keep headers of the Legacy chain to save disk space
* Processing of Legacy transactions will be stopped and their history locked
* Any coins not in a sigchain at this point will be considered lost, and we can update our coin-supply


== Object Modeling ==
=== 10.0 ===


Object Modeling is a new feature that will extend the API layer allowing developers to model their Object Registers in languages such as XML (Extensible Markup Language). This will also contain modeling languages that will make it possible for advanced developers to work with lower level object operations. These could include using specific data types and specifiers, developing more complex object behavior through Augmented Contracts, or creating extra conditions that regulate the object’s overall behavior.
* Add Trust System to Mining Nodes to weight their proof of work with trust along with the actual work completed
* Add Trust System to Hybrid Network Sigchains to develop an algorithm of consistent contributions to the network in the form of NXS payments for use with the hybrid systems
* Add Trust System to Ambassador Network Sigchains to develop the algorithm of voting allocated funded between Embassies and as our final voting group


== Augmented Contracts ==
=== 10.1.x ===


Augmented Contracts are the second type of contracts that will be available in the Tritium Protocol. These types of contracts extend the Conditional VM (Virtual Machine that processes Conditional Statements) to provide additional benefits including, but not limited to, methods, functions, operation overloading, and encapsulation. Augmented contracts add a layer of complexity and processing, so will carry a higher fee to execute. This will require more on-chain processing, but overall makes our Contract Engine much more powerful.
* Post Hard-Fork maintenance, add global network data sharding using the LLD so that your node only has to retain part of the chain dataset, while keeping the main chain as a list of block headers for reference
* This is a stair stepped process that will eventually lead to full data and process sharding


== Protected Assets ==
== Obsidian ==


Protected Assets are a type of asset with the addition that a ‘Master’ owner retains the right to revoke access to the asset. This essentially allows the asset creator to have permanent access to an asset, which is necessary for securities, collateralized loans (DeFi), non-transferable assets (Tickets, Educational/Professional Awards and Certificates, Certificates of Insurance, Licenses etc.). They are also useful for protecting the asset from being transferred to unqualified parties, or in other words, parties that do not fulfill the requirements set out by asset creator.
=== 11.0 ===


== LLD Global File System ==
* Hard Fork to link all the voting groups into global systems maintenance such as fee management, and fund management to each DAO (Embassy) that's been allocated


The LLD global file system will support secondary files that record assets to be stored and retrieved through network operations, providing a seamless interface for managing assets and data.
=== 11.1.x ===


= Amine =
* Post Hard Fork Maintenance updates


== pBFT + Reputation Channels (L1) ==
=== 12.0 ===


This new architectural component will process transactions in parallel, using reputation as an additional weight to provide higher security. The transaction speed of L1 channels will vary based on the risk that a merchant wishes to assume, ranging from sub-second speeds to 5 seconds. For higher value transactions, it will be recommended that they receive additional weight from validation on the next consensus layer: L2, reducing transaction speed to 15 seconds plus.
* Hard Fork to develop a mining share system, where initial merkle proofs of all miners shares can be submitted over a Tritium Block and the reward distributed among the submitters of the given share
* This also weights the block based on the total proof of work, and the total trust that generated it
* Every miner can then contribute to each individual block, but must agree on the same merkleRoot to hash together


== pBFT + PoS Trust Network (L2) ==
=== 12.1.x ===


As an extension to the existing Proof of Stake system, L2 will form the second layer of consensus above the L1. The L2 layer ensures safety and liveness, cross-shard communication, and resolves conflicts from the L1 layer. It represents the horizontal chaining of the L1 channels, and is a major step towards a truly decentralized and scalable ledger.
* Post Hard Fork Maintenance updates


== Network Data Sharding ==
=== 13.0 ===


Data sharding is an essential facet of our ledger design in order to achieve long-term scalability. Amine will provide the opportunity for nodes to run in “shard” mode, which will lower their disk and memory usage, even when the network is under high load.
* Hard Fork to develop nPoS shards and cross links between L1 State channels along with full Data Sharding of transaction and register states


== LISP Multicast Links for (L1) and (L2) ==
=== 13.1.x ===


Using LISP, the L1 and L2 layers will have their own Multicast links, therefore packets and transactions will route in constant time no matter how many nodes are part of the system.
* Post Hard Fork Maintenance updates


== Application Store ==
=== 14.0 ===


Here applications and modules will be able to be shared and sold in a decentralized marketplace. Modules will provide developers the building blocks to create applications.
* Hard Fork to deprecate the main chain from the first 3D block, weave the L1, L2, and L3 layers together, still retaining only 4 L1 state channels


= Obsidian =
=== 14.1.x ===


== Extended Network Data Sharding ==
* Post Hard Fork Maintenance updates


Data sharding in Obsidian will extend to critical network functions, resulting in nodes being required to store only a portion of the overall chain. Note, this is data sharding, not computational sharding, which means once data has been processed, it can be partitioned and stored between nodes. The result will be an increase of data storage as more nodes join the network.
=== 15.0 ===


== Decentralized Mining & Merkle Share Pool (L3) ==
* Hard Fork to add the mitosis process for splitting of L1 state channels and L2 nPoS shards to increase capacity, or merging them to decrease capacity


This component will use Proof of Work based mining shares computed from the work performed by the nodes of L2. Consensus will be determined by the largest value of shares + trust, in order to reach the final agreement on the most valid 3D block.
=== 15.1.x ===


== DAO: L1 Voting Group (Implement) ==
* Post Hard Fork Maintenance updates


The L1 voting group will provide voting rights to validators who are new to the network, and therefore do not have enough resources to participate in the L2 consensus. Voting weight is based on reputation.
=== 16.x.x ===


== DAO: L2 Voting Group (Extend) ==
* Hard Fork and maintenance updates to adjust consensus parameters as final upgrade to the core protocol
 
* This could include modifying certain values for security, and touching up on any updates that need to be done to the 3DC
The L2 voting group will extend Tritium’s “Ambassador DAO” and provide voting rights to validators who have reached a reputation threshold. Voting weight is based on reputation multiplied by stake.
 
== DAO: L3 Voting Group ==
 
The L3 voting group will provide voting rights to miners. Voting weight is based on mining power (average weight of mined shares over time) multiplied by reputation.
 
== LISP Multicast Links for L3  ==
 
Shares on L3 will use LISP Multicast links allowing the efficient broadcasting of mined shares, and the acceptance of L2 hashes for computation by L3 nodes.

Latest revision as of 15:04, 2 February 2025

TAO Roadmap

Our roadmap shows the progress made in each of the core stages of the TAO Framework which include the deployment of the Three-Dimensional Chain (3DC). Each letter represents one of the three consensus upgrades that correspond to the addition of a lock level on the 3DC.

The roadmap to success

What are our major goals?

Mobile and Web Dapps

  • Mobile Wallet Official Release
  • Mobile P2P Quantum Resistant Encrypted Chat App with Programmable chat rooms and user authentication
  • Mobile Wallet additions to allow Remote Sessions for using Mobile Wallet and/or Desktop Wallet as a 2FA source
  • Decentralized Search Engine (https://nexus.io/search) for censorship free search and personalized results based on local data. No tracking, no ads, no censorship. Reputation and results ordering maintained on-chain
  • LLD and LLP Service Layer for use in Web-Apps and also accessible through the LLL-TAO API System
  • Mobile P2P and decentralized Uber dapp with 0% fees, on-chain reputation, and collateralized delivery functionality
  • Mobile P2P DEX Interface for trading tokens on Nexus or Hybrid/Sister chains in a mobile Dapp
  • Mobile P2P decentralized Geo-Spacial markets where you can buy and sell locally any legal product(s). This combines with the P2P decentralized delivery system so that goods can be transported as another additional revenue for drivers
  • Mobile Filesystem Backup to use LLL-TAO File System to backup files on your device and allow access with the Nexus Dapp Suite
  • LX-OS Microkernel with Linux Compatibility Layer to run certain flavors of Android OS such as Graphene and allow hardware compatibility and security beyond the Google Pixel

Tritium++

5.1.x

Mobile Wallet

  • Final Bugfixes to get Mobile wallet released

5.2

  • SQL Language Updates: Upgrades to the SQL language in the API to add additional functionality and operators
  • Removal of OpenSSL: Complete Removal of OpenSSL using our own embedded TLS and Cryptography in the LLC
  • Integration of O(!) LLD Service: Integrate O(!) LLD Service completely into the complete Network
  • New APIs: P2P Messenger API, Crypto API

5.3

  • Remote Login System and API, Sigchain Ledger VM to create programmable access patterns to your sigchain with multiple sets of credentials

6.0

  • Hard Fork for Difficulty Adjustments, Security Updates, Initial Filesystem Hosting, and Initial Augmented Contracts

6.1

  • Post hard fork maintenance, DSL for Initial Augmented Contracts, Signature Chaining Space Reduction Complete

7.0

  • Hard Fork for Security Updates, Pooled Staking, Incentivized Hybrid Mode, Final Incentivized Filesystem, and Final Augmented Contracts

7.1

  • Post hard fork maintenance, Final DSL for Augmented Contracts

8.0

  • Hard Fork for implementation of Starfish Funding Model as an on-chain enforced protocol, currently allocation is voted via trust keys on-chain but is not enforced by the ledger

Amine

9.0

  • Hard Fork to add additional hash reference ID for an Amine Shard(s)
  • Initially 4 shards will be created using pBFT and nPoW + Trust that reference the main chain
  • A user will be required to opt-in to a shard to process within in it, or can opt-out and process transactions using the Tritium Protocol
  • This will be ongoing throughout Amine if any adjustments need to be made
  • Hard Fork to deprecate UTxO, retain support for it in processing but not allow new UTxO transactions to be made

9.1.x

  • Post Hard-Fork Maintenance while releasing TAO only mode where we can truncate the chain at the first Tritium Block, and keep headers of the Legacy chain to save disk space
  • Processing of Legacy transactions will be stopped and their history locked
  • Any coins not in a sigchain at this point will be considered lost, and we can update our coin-supply

10.0

  • Add Trust System to Mining Nodes to weight their proof of work with trust along with the actual work completed
  • Add Trust System to Hybrid Network Sigchains to develop an algorithm of consistent contributions to the network in the form of NXS payments for use with the hybrid systems
  • Add Trust System to Ambassador Network Sigchains to develop the algorithm of voting allocated funded between Embassies and as our final voting group

10.1.x

  • Post Hard-Fork maintenance, add global network data sharding using the LLD so that your node only has to retain part of the chain dataset, while keeping the main chain as a list of block headers for reference
  • This is a stair stepped process that will eventually lead to full data and process sharding

Obsidian

11.0

  • Hard Fork to link all the voting groups into global systems maintenance such as fee management, and fund management to each DAO (Embassy) that's been allocated

11.1.x

  • Post Hard Fork Maintenance updates

12.0

  • Hard Fork to develop a mining share system, where initial merkle proofs of all miners shares can be submitted over a Tritium Block and the reward distributed among the submitters of the given share
  • This also weights the block based on the total proof of work, and the total trust that generated it
  • Every miner can then contribute to each individual block, but must agree on the same merkleRoot to hash together

12.1.x

  • Post Hard Fork Maintenance updates

13.0

  • Hard Fork to develop nPoS shards and cross links between L1 State channels along with full Data Sharding of transaction and register states

13.1.x

  • Post Hard Fork Maintenance updates

14.0

  • Hard Fork to deprecate the main chain from the first 3D block, weave the L1, L2, and L3 layers together, still retaining only 4 L1 state channels

14.1.x

  • Post Hard Fork Maintenance updates

15.0

  • Hard Fork to add the mitosis process for splitting of L1 state channels and L2 nPoS shards to increase capacity, or merging them to decrease capacity

15.1.x

  • Post Hard Fork Maintenance updates

16.x.x

  • Hard Fork and maintenance updates to adjust consensus parameters as final upgrade to the core protocol
  • This could include modifying certain values for security, and touching up on any updates that need to be done to the 3DC
Retrieved from "https://nexus-wiki.org/index.php?title=TAO_Roadmap&oldid=201"