In the lead up to Christmas, and the much anticipated Nexus Tritium core release in January 2019, the Nexus development team is hard at work preparing for December’s public test nets and creating the module store. In late November, Colin Cantrell presented at the Cryptofinance conference in Oslo, and Nexus held its first European Developer Workshop in Warsaw.
The LISP mapping system is running on Tritium and is being tested. Crypto-EIDs which are IPv6 are also ready, and the team is moving forward with linking them to signature chains. Advanced Contracts are also in testing with new validation scripts which are being finished. The Logical and Interface layers are entering into their final phases of beta. A public Tritium testnet is aimed for the end of December, while the API and RPC are awaiting final core features to be completed.
The Nexus Tritium update will allow developers to integrate with the Nexus blockchain through an easy to use, feature-rich API set. APIs will create user-friendliness for developers who will be able to build in a wide range of languages, and interoperability for existing private systems to interact with the Nexus blockchain. Nexus has designed its software stack based on the Open System Interconnection (OSI) network reference model, with the fifth layer as the API layer.
Dino has added a new draft update to ‘LISP-Decent’ to describe a pull-based decentralized mechanism for the LISP mapping system, which can be read here. He has also been holding bi-weekly Zoom meetups of which the links to the recordings are below:
Zoom meetup 1 shows how packets flow, how Nexus peer connections are made, and how the containers are connected to the underlay.
Zoom meetup 2 shows how packets are encrypted and sent on the IPv6 overlay due to the Locator / ID Separation Protocol on the IP address network layer.
Zoom meetup 3 shows how crypto EIDs, the mapping system, transactions over the IPv6 overlay, and Nexus nodes will protect users against IP address spoofing.
Colin, Alex and Jules travelled to Oslo for the BitSpace CryptoFinance conference. At the conference Colin spoke on two occasions, as a keynote on how Nexus is designing a decentralized internet infrastructure through the use of cube satellites, and on a diverse and lively panel with Richard Hart. We would like to thank the Bitspace team for organizing such a great event, and we look forward to attending the next one. Recordings of Colin’s presentation and the panel discussion are available on the following links:
Long-time community members @Mirrax and @Lib, kindly showed the Nexus team some of the lands of Norway and held an interview with Colin in which he answered questions from the community. The interviews can be viewed on the following links:
Nexus hosted its first European Developer Workshop in Warsaw, Poland. Colin Cantrell presented the design of the proposed social organizational architecture. Alex El-Nemer presented on some of the Tritium use cases, with insights into the technology Nexus is building with partner SoundVault who specialize in music licensing. We would like to thank all the Polish community for their continued support and great hospitality. The workshop recording can be viewed here.
Sustainable Supply Chains
It is clear that organizations can only operate effectively with easy access to products and services. Likewise, no organization can continue to grow if late payments and poor procurement processes remain in place. This is where blockchain technology can play a crucial role, in both the modernisation and improvement of the logistics and operations which are vital to the performance of supply chain systems.
January 8th: Colin will speak at CES Las Vegas, on the topic of: “How blockchain is remaking the Media/Entertainment Business”
We would like to thank the following individuals from the community for their warm welcome in Norway, @Mirrax, @Lib and @Tjustt, and the many people who helped with the Warsaw Workshop, including @Kat @Zygmunt @Pawel @Kkbiznesowy and @Jakub.
The next Newsletter will follow January’s Tritium release. We would like to wish you all a lovely Christmas and New Year with your friends and family.
It is clear that organisations can only operate effectively with easy access to products and services. Likewise, no organisation can continue to grow if late payments and poor procurement processes remain in place. This is where blockchain technology can play a crucial role, in both the modernisation and improvement of the logistics and operations which are vital to the performance of supply chain systems.
With the release of the Tritium Mainnet, application developers will be able to interact with the functionalities of the Nexus blockchain through an easy to use, feature-rich API set. APIs will create user-friendliness for developers who will be able to build in a wide range of languages, and interoperability for existing private systems to interact with the Nexus blockchain. Nexus has designed its software stack based on the Open System Interconnection (OSI) network reference model, with the fifth layer as the API layer.
What is an API?
An API is an Application Programming Interface. While a user interacts with a system through a user interface, an API allows developers to interact through a programmatic interface. The way this works is that the API provides a list or set of simple commands that execute a series of operations, which would otherwise require specialist programming knowledge. This allows a developer to request or submit data to a system providing functionality to a higher-level application. For example, Facebook’s Graph API allows access to “Login with Facebook” and other features of their system.
The distributed validation method provided by a public blockchain or Distributed Ledger Technology (DLT) (on-chain) is very secure in comparison to that of a private blockchain (side-chain) or centralized database (off-chain), because it is validated by many nodes forming a global consensus. However, private blockchains which are serviced by their own nodes provide other benefits that are much easier to develop and scale. One such benefit is to record proofs of private, sensitive, or proprietary data that are generally stored in a private database. This provides the private database the ability to edit or delete this data, in order to comply with regulations such as General Data Protection Regulation (GDPR), while maintaining the positive qualities of immutable proofs from the private blockchain. An optimum balance between a Public Ledger, Private Ledgers, and Private Databases, will provide the performance and efficiency necessary for global adoption.
Nexus is developing the systems to enable private networks to utilize the public ledger, creating what is essentially a hybrid system, through an array of both private and public ‘template’ use case APIs. Public APIs will be provided by Nexus as open source technology, while Private APIs will be developed with businesses as their proprietary technology.
Nexus welcomes any interested parties to participate in our working groups to help shape the standardization process for the Nexus Software Stack, as we continue to develop the standardization body for DLT, similar to how the Internet Engineering Task Force (IETF) shapes the internet.
In addition to accessing the Public APIs, developers will be able to build their own Private APIs, providing the privacy of a permissioned system required to keep proprietary information and logic concealed, while harnessing the security of a public blockchain. This is possible through the use of state recording checkpoints between the private and public networks to ensure that agreements in the private network are also recorded in the public network, shown by the diagram below.
Given that only the aggregated state of the private ledger is recorded, sensitive or private data is not stored on the public ledger. Therefore, private APIs can secure proprietary contract logic, such as private supply chains, notaries, consumer verification services, etc., providing private services that the public layers are unable to. Since a private API functions as its own private network that synchronizes to the public network, one can expect the level of reliability and security of DLT. A private network can be operated under a software services license, or by the commissioner of a said API service. The final result, is a robust service that provides interoperability with existing private systems.
Nexus Private API Service for Enterprise range from hosting solutions to full private API buildout. Private APIs can be custom-built either by Nexus on behalf of a private client, or by any third party with or without consultation. Private testnets can also be provided during development to avoid loading the public and final private ledger with redundant data.
It is often claimed that the ratio of demand to supply for blockchain developers is 20:1, which has led to the high costs associated with blockchain development and low business adoption. Since most programmers are already comfortable interacting with an API, building on the Nexus API can be as simple as developing a web-app. Through improvements in accessibility, Nexus is set to significantly reduce the barriers to entry for blockchain technology.