Developing on Nexus

Five benefits to using Nexus

Nexus is built to verify the authenticity of data, being a verification system, not a computation engine. The following five reasons are the most prominent factors why our seven layer software stack improves the developer experience over similar platforms such as Ethereum, EOS, and Waves: Security Model, Automated Key Management, Object Modeling, Restful API, and Scaling Model. Below we have included a comparison table between other similar platforms, to elucidate the unique qualities of our development environment.

Nexus comparison with other platforms

1. Security Model

Our security model combines together many different technologies that make Nexus resilient to the evolving threats coming from Quantum Computing, Blockchain, and Security in general. We follow best practices with professional security audits, open source code review, and utilizing modern standards in cryptography such as SHA3. We also provide the option to the end user or developer to use purely Quantum Resistant Cryptography (FALCON) rather than Classical Cryptography Standards (ECDSA).

2. Automated Key Management

Key management on Nexus is automated via a ‘decentralized authentication system’ we call ‘Signature Chains’. This not only gives the end user a better experience in managing their personal property, it also removes the burden of key management, which often requires third party plugins such as MetaMask. Signature Chains integrate into existing application frameworks that already rely on authorization systems through username and password combinations, and thereby provide DApp developers the ability to integrate blockchain functionality as an elevated layer into existing applications without much architectural modification.

3. Object Modeling

Our architecture is ‘object oriented’ meaning that immutable data objects can be modified via ‘operations’. Object modeling gives developers access to a toolkit of important functions for managing objects in an application that require some objects to maintain a history and native immutability. Specific fields in objects, however, can be configured as mutable or immutable. This is very useful for applications that rely on a dynamic state, such as the progression of ownership, location, and quantity etc. Immutability on the other hand guarantees that certain states remain unchanged, such as a serial number, even if grouped in an object with many dynamic states.

4. Restful API

Contrary to the designs of projects such as Ethereum, EOS, or Cardano, our DApp developer environment is API driven, meaning that as a developer you can integrate blockchain functionality into your apps without being inhibited by the many nuances of using an emerging programming language such as Solidity. This ensures a safer and higher quality production code, while reducing the overall cost of the software.

5. Scaling Model

Scaling is a requirement, not a feature. The architecture must be able to handle large volumes of contracts, while also maintaining the same, if not higher levels of security. We have partially achieved this through our TAO Framework (3DC), which is currently one-third complete. When fully implemented, it will provide full scalability, security, and decentralization through a globally sharded decentralized consensus network, necessary for the long term sustainability of Nexus.

Conclusion

We have spent over six years designing, developing, and deploying the current protocol. Our roadmap details our long term vision and continuous technological roll-out to support the growth of the Nexus ecosystem.

Roadmap

Tritium White Paper

What is Tritium?

API Documentation

Guides