Next Earth OS

The Metaverse industry has a middleware problem. Developing for a unified digital space is clunky, problematic and expensive. The gap between Web3 and Web2 is too large for that. This is why we decided to build the Next Earth OS for developers to build their dApps.

Developers in our Developer Community are able to build their own applications using the Next Earth Operating System. This includes both read and write rights, the creation and manipulation of their own Layers, to make transactions of virtual land including land purchases, access UNIT generation, landowner data and dynamic properties of our NFTs through a simple API call. This means full Web3 compatibility for Web2 developers. In other words if you are a Web2 developer, you will be able to make use of our Web3 infrastructure and smart contracts while not knowing how to code in Solidity.

The Developer Portal is available on developer.nextearth.io where business and technical support will be provided to developers who wish to launch their dApps on the Next Earth App Store.

We also launched a Sandbox environment for developers to try out all our API calls without having to launch their app first and find the best technical solution to their needs. Our developers created a totally separated framework for the API from the Next Earth core system. This framework responsible for two things:the synchronization between Next Earth data and a proxy database which contains only the relevant data for the API (this means that the incoming data via the api can be checked and validated before it is written into the core database) running microservices that implements the endpoints

As a start, some obvious endpoints are created like Land NFTs data and landowner data. Thanks to the microservices architecture the new endpoints (or endpoint groups) can be developed separately for the coming use cases and as the needs grow from the Developer Community. The Next Earth API framework runs on AWS for the reliable performance and scalability. NEOS consists of multiple main building blocks:

Sandbox

Our Sandbox environment is powered by GraphQL, an open-source data query and manipulation language for APIs, and a runtime for fulfilling queries with existing data. Originally developed by Facebook in 2012, this playground allows you to check out all the capabilities of NEOS without having to deploy anything.

Object API

On NEOS, we differentiate between Organizations and Objects. On the Genesis Layer, the Organization is Next Earth, and the Objects are the Virtual Lands. Through our Object API, you can access all the data on the Genesis Layer as well as any further Layers you are authorized to access.

This is the fundamental building block to creating your own geotagged dNFT and dApps in the Next Earth Metaverse. When you create a Layer, you create your own Organization in the Metaverse and when you start minting dNFTs, you fill that Organization with your Objects.

Layer API

Building a dApp on NEOS starts with generating your own Layer. Defining the attributes of your Layer can be done via our Layer API that will serve as a connecting tissue between NEOS and your dApp. This is built on the foundations of our Nth Dimension Layer concept that allows us to scale the Next Earth Metaverse to millions of dApps, powered by NEOS.

Minting API

The Minting API allows you to mint dNFTs with your defined properties on specific geolocations, attached to your Layer. The Minting API enables you to build your own logic in a language agnostic way and when minted, you can read all the data via our Object API. The Minting API is a mission critical component of turning the Next Earth Metaverse into a true Web3 gateway as it enables all 20+ million developers to mint their own dNFTs without Web3 know-how.

Controller API

Developers need to ensure that users who interact with your dApp can safely store updates to the properties of their dNFTs on-chain. This is handled by the Controller API, which governs the dNFT property updates as defined by you.