What is Tritium?


"The blockchain is a verification system, not a computation engine"

The design of Tritium is based on information gathered from many discussions with Fortune 10 to Fortune 500 companies, developers, and community volunteers over the past two years. Through our research we’ve found that most projects built on Ethereum do not use the Ethereum Virtual Machine (EVM) for its turing completeness, i.e. its ability to do universal computation. What businesses require from blockchain technology are contracts that function more like real world actions between people, with the addition of an immutable data layer capable of managing rights and ownership.

Therefore, we have developed an easily accessible and versatile Software Stack where data can be operated on, its ownership transferred between users, and whereby conditions define the behavior of actions. Our design not only provides numerous ready-made contract functionalities through elegant design, it is also able to scale with the growing demand of smart contracts.

Register Based Contract Engine

A register is the fastest storage medium inside your computer’s CPU (Central Processing Unit), that the processor uses to cache data in between calculations. This has become a more desirable architecture for computer design as an improvement to a much older architecture called a ‘stack’.

Our contract engine follows this architecture as an improvement to other blockchain-powered virtual machines such as the EVM (Ethereum Virtual Machine) that still use the older stack architecture. The improved efficiency gained through the use of registers makes developing on Nexus not only easier, but also much more efficient and scalable.

Application Programming Interface

Our Application Programming Interface (API) is for developers to build Decentralized Applications (DApps) and Hybrid Networks. The API can be used for the recording of Supply Chains, Digital Asset Licensing, Financial Assets, Records, Licenses, Certificates, and Securitized Token Offerings (STOs).

To add flexibility, a developer can make non-standard API calls with custom conditions to provide additional functionality to the DApp that is unavailable through the standard API. This can be further augmented with Domain-Specific Languages on the lower API layer.

Conditional Contracts

A basic Nexus contract is comprised of three layers: data (Registers), programmable actions (Operations), and accounts (Signature Chains). Together, these layers verify the information of a system or Decentralized Application (DApp), following logic that closely relates to agreements and contracts between people.

We have followed this approach for the primary reason that smart contracts cannot be realized with existing language designs, they require a new architecture. This is in direct contrast to EOS’ use of Web Assembly (WASM), which was designed for web development rather than building secure financial applications.

Conditional Contracts allow a user to set requirements in order for a contract to be fulfilled, such as contract time expiration, the decentralized exchange of an asset, or a non-custodial escrow services.

Decentralized Login System

A major benefit of using cryptocurrencies is the security gained through the use of public key cryptography. Though this is a vast improvement to centralized login systems, this benefit comes with the drawback of key management. In order to manage these keys, most cryptocurrencies use a database storage file called a ‘wallet.dat’ that keeps a record of all the keys that have been / will be used to access funds.

We believe that the adoption of blockchain technology will always be limited if relying on such a model, due to the inconvenience of having to make regular wallet backups, loss or theft of hard drives, and the risk of sending funds to unspendable addresses. These systems are susceptible to human error, boding for the need for complex hardware designed specifically to store private keys securely. Though these devices are a step towards user friendliness, they are still at risk of being lost or stolen, and therefore are not a reliable replacement for authorization systems.

Therefore, we developed a decentralized login system: Signature Chains. This technology still uses public key cryptography, but rather than maintaining the keys on disk or the cloud, they are stored in ‘mathematical hyperspace’. Signature Chains support the Nexus Wallet, making it accessible from any computer simply by logging in with your credentials (username, password and pin).

Signature Chains can be integrated with various security measures such as biometrics and hardware password managers. We view this approach as being fundamental to the adoption of blockchain by the general public, while it also improves current security standards.

Signature Chains are also available for DApp developers to build with, furthering our mission of making blockchain technology more accessible. Signature Chains are comparable to a personal blockchain, and provide the foundation for features such as Managing Assets, whilst maintaining pseudo-anonymity for privacy. In our opinion, they are a very important step for mainstream adoption across all blockchain use cases.

Decentralized Exchange

Assets and tokens hosted on Tritium fulfill the requirement of managing and storing ownership rights, and also provide another unique utility: decentralized exchange. Through the intelligent use of conditional contracts, without custodian services, anyone is able to transact between different tokens and assets. 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.

Asset Management

Assets are used to create a record of a digital or physical asset on the blockchain, in order to track ownership and facilitate peer-to-peer exchange. The registration of assets can be facilitated by DApps to create many decentralized and automated services. Some examples of assets that can be registered on the Nexus Blockchain include:

Digital Assets and Media:

Music, Audio Books, E-books, Graphics & Photography Film, TV shows, Games, Software and Apps.

Supply Chain Certificates (Standards, Authenticity, Quality Assurance, Customs, Titles):

Agricultural Produce & Fish, Minerals, Timber, Livestock, Electricity, Pharmaceuticals, Electrical Goods and Components, Luxury Goods, Antiques, Art, Branded goods, Customs Records, Cars, Motor Cycles, Boats.

Financial Assets:

Company Registrations and Securitized Tokens, Land Titles.

Personal Records, Licenses and Certificates:

Birth Certificates, Digital Identification, Medical Records, Educational and Professional Certificates, References (Landlord and Employment), Education, Insurance Records, Marriage Certificates, Driving & other Licenses.

Intellectual Property:

Patents, Trademarks, Internet Domains (DNS, TNS).

Gaming Assets:

In Game Tokens, Virtual Assets.


Loyalty Points, Airmiles.

Token Protocols

Some believe that our future societies will use tokenization for many purposes. This is a novel idea, considering that the current use of tokens has been limited to speculative assets, such as Initial Coin Offerings (ICOs). Conversely, Nexus fungible tokens can facilitate the transparent and automatic payment of Royalties and Dividend payouts.

Tokens can represent partial ownership or rights to an underlying digital or physical asset. The token allocation determines how the revenue is distributed, and the revenue is paid out to the holders in a direct peer-to-peer manner. This is in direct contrast to current manual systems that are used to facilitate these types of payments, which are often slow and costly to operate.

The diagram above shows the flow of an automatic payment of a shared revenue stream. In this example, the token (called TKN) distribution is 50-25-25. The process follows these steps:

1. User pays a license fee (here it is 1000NXS) for use of an asset.
2. The token holders are notified to claim their percentage of the payment (DEBIT), which is represented by their total token balance divided by the total token supply.
3. Each token holder credits their account by proving their right to this payment with their TKN balance.

STOsDigital Rights Management

TAO Name System

The TAO Name System (TNS) is similar to Domain Name System (DNS), allowing users to create and exchange names with one another that point to different objects, without having to use large hexadecimal addresses. These names can resolve to register addresses such as assets and tokens, or become aliases for user identification.

TNS reduces the complexity of sending transactions, as a user only requires a username and account name to send funds to another user (eg. send to paul:savings). Similarly, TNS also simplifies the user experience of managing digital assets. Entries can also point to IP addresses for remote services wishing to explore blockchain based DNS functionality.

Lower Level Library

The Lower Level Library (LLL) is a high-performance ‘Template Library’ designed to power emerging-web technologies. Most web technology today is clunky, centralized, and over-engineered as a result of decades of development. The LLL is simple, powerful, and lightweight. It contains three main components: Cryptography (LLC), Database (LLD), and Protocol (LLP).

The Cryptography component contains Quantum Resistant cryptography, the Database component out performs Google’s LevelDB by orders of magnitude, and the Protocol component handles well over 450k requests per second. The LLL is the foundation to the TAO framework, while being able to support other web technologies with high reliability, performance, and extensibility.

Hybrid Networks

The demand for privacy has created a growing divide between public systems like Bitcoin, and private systems like Hyper Ledger or Quorum. The combination of these two architectures is what we term ‘Hybrid’, whereby the public network generates security and decentralization, and the private network provides autonomy, privacy, and isolation.

A Hybrid Network is an ideal choice for any individual, company, or large enterprise wishing to manage their own private network, without the added complexity of worrying about system or network security and protection of critical user data.


Tritium runs on the Locator Identifier Separation Protocol (LISP) overlay, developed by team member Dino Farinacci who was the first Fellow (the most senior rank or title one can achieve in engineering) of Cisco.

LISP increases the reliability and security of communication between nodes, and is responsible for network scaling through multicast, identification through a static EID (Endpoint Identifiers), and authentication by using these identifiers.

Through IPv6 addressing LISP provides ample capacity for the emerging IoT industry. It will be used in a critical capacity with the release of Amine, which uses the Network (IP) layer to shard data and assign identifiers to data segments for management of the distributed database, without the loss of security or privacy.