Roadmap
This section outlines NIN.Earth’s current development status, roadmap, and future plans. You can follow ongoing progress, upcoming updates, and long-term goals that define the evolution of NIN.Earth.
Spherical globe for 1:1 scale Earth.
Publishing Domain Space, the fundamental elements of the NIN Metaverse, as digital assets - the Web3 way.
Back-end architecture for the expansive NIN Metaverse.
True Web3 geo-locational Metaverse for everyone & everything.
(Under consideration. It will be disclosed once a decision is made.)
Establishing a governance structure for community decision-making. Opening Domain Space information to other Metaverse projects.
Key Information
NIN.Earth utilizes the Solana blockchain. Domain Space NFT is minted on the Solana blockchain.
Total number of tiles: 237,279,209,162 [ea]
Average area of a tile: 2,149.643 [m2]
Average edge length of a tile: 28.663897 [m]
Maximum number of tiles that can be selected at one time: 35 [ea]
Creator address of Domain Space NFT :
6qm3yCWBbKGoqdMLGbeZHSBMP6pomtMHxkbK2MbhG7SA
Collection NFT of Domain Space NFT :
Phase I
The Spherical Earth
1:1 scale digital Earth for AR should be based on a spherical 3D map with hexagonal tiles.
Mercator vs Spherical projection It is impossible to create a 1:1 scale digital Earth using a Mercator projection. Why? Check out this TED-Ed : Why every world map is wrong
Square vs Hexagon tile Square tiles obviously cannot cover the spherical shape of the Earth, but hexagons can. Hexagons are the Bestagons
AR on a Mercator projection with square tiles? It’s just nonsense. The Mercator projection distorts the size of landmasses as latitude increases from the equator to the poles. Consequently, the scale is not uniform across the map, which also affects the size of 3D objects in augmented reality (AR). Aligned square tiles on top of that? No way!
The Fundamental Assets
Domain Space is the fundamental asset of the NIN Metaverse. To ensure ownership, each Domain Space is minted on the blockchain as an NFT — a digital asset in a decentralized Web3 environment without central control. The NFT serves as the sole and definitive proof of ownership of a Domain Space and must be securely stored. It also acts as the key to managing the Domain Space.
Detail information of Domain Space Double-click a Domain Space tile on the map. This will retrieve detailed information about the Domain Space. The Mint, Creator, and Collection NFT addresses provided in the information can be used to verify whether an NFT is a genuine Domain Space NFT or a fake one.
Availability of Domain Space To prevent permanent dead spots in the NIN Metaverse due to lost NFTs, each Domain Space must be renewed every 10 years. Renewal is free, except for the cost to replace the NFT with a new one. The renewal process will be announced several years before the end of the initial 10-year period. Tiles of Domain Space that fail to renew will be released for purchase by other users.
Domain Space for Domain Name The Domain Name(URL) for the current web service will continue to be used in the NIN metaverse. Users can assign their Domain Name to their Domain Space in the NIN metaverse, allowing people to visit their land directly, just like accessing their website.
Tile rules for Domain Space - All selected tiles must be connected, with no isolated tiles. - A maximum of 35 tiles can be selected at one time. - The tiles of Domain Space generate NIN points, which will be used in the NIN ecosystem later.
Account, ID/PW
Does blockchain require an account and ID/PW? No. Instead, it relies solely on a private key and a public key. The private key is your secret, granting access to your assets and identity, while the public key acts as your unique identifier, like an address.
We believe the Web3 Metaverse should follow the same principle. In the NIN Metaverse, users shouldn't need to create accounts, remember PW, or verify their identity through centralized services. Instead, your public key, which contains your NFTs, represents you and serves as both your identity and your access point across the Metaverse.
This approach enables greater user control, privacy, and interoperability, allowing you to be part of the Metaverse and navigate it seamlessly without sacrificing ownership or security. That's the essence of Web3: true digital self-sovereignty.
Phase II
The Architecture
It will be disclosed in Phase II
Vast expanse How to manage the vast expanse of the metaverse on a 1:1 scale digital Earth.
Large population How to service the vast metaverse for a large population on Earth.
Countless 3D objects How to manage the countless 3D objects in the metaverse.
Web3 Metaverse The structure to achieve decentralized ownership and governance.
Not 3D Graphics, but Structure is Key
When a metaverse project claims to be a geo-locational Metaverse representing a 1:1 scale Digital Earth, they should understand the implications.
There are approximately 1,200 million websites globally, with 16~17% of them active — equivalent to 200 million web servers.
(https://siteefy.com/how-many-websites-are-there)
In a geo-locational Metaverse that mirrors Earth on a 1:1 scale, each tile is akin to a site in Web 2.
The NIN Metaverse contains 237,279,209,162 tiles, and other projects likely have similar numbers. Moreover, the workload difference between a web server and a 3D Metaverse server is immense:
Real-Time Rendering and Interaction - Metaverse Server: Manages complex 3D environments with real-time rendering, physics simulations, and frequent synchronization, demanding significant computational power. - Web Server: Handles HTTP requests and serves content, with minimal real-time processing; graphical tasks are client-side.
State Synchronization - Metaverse Server: Synchronizes states across multiple users in real time, including avatar positions and shared actions. - Web Server: Mostly stateless, relying on discrete API requests, which are computationally lighter.
Network Traffic - Metaverse Server: Requires high bandwidth and low latency to manage constant updates and interactions. - Web Server: Handles lower-frequency, request-response traffic, with less stringent latency requirements.
Persistent Virtual Environments - Metaverse Server: Maintains a persistent virtual world, requiring ongoing simulations even without active users. - Web Server: Operates on-demand, serving resources only when requested.
Complex User Interactions - Metaverse Server: Handles spatial data, collision detection, and real-time user interactions among multiple users, requiring complex orchestration. - Web Server: Manages simpler interactions, such as forms and link clicks, which are less computationally demanding.
Graphics and Physics Processing - Metaverse Server: Computes graphics, physics, and collisions server-side for consistency, adding significant computational load. - Web Server: Does not handle 3D rendering or physics, as these are client-side tasks.
Storage Requirements - Metaverse Server: Manages large volumes of user-generated content and 3D assets, requiring substantial storage. - Web Server: Primarily handles text-based content and media, with lower storage needs.
Overall, a Metaverse server's workload can be 10-100 times greater in terms of computation, network requirements, and complexity compared to a traditional web server, requiring a robust infrastructure to manage real-time interactions, 3D environments, and many concurrent users.
This huge level of workload should be handled globally on a 1:1 scale Digital Earth. Imagine 10-100 times the workload of 193,890,945 web servers.
If a geo-locational Metaverse project lacks a detailed plan to handle this massive workload, it indicates a lack of understanding of the complexities involved, focusing primarily on graphics rather than the full scope of infrastructure requirements.
Phase III
Web3 geo-locational Metaverse
It will be disclosed in Phase III
Flexibility Users will be able to construct their lands as they wish.
Visibility Users will see in AR what they build on their lands in the metaverse, at the corresponding location on Earth.
Serviceability Users will be able to offer services related to their lands as they have planned.
Profitability Users will be able to engage in economic activities on their lands without any fees, taxes, or charges—at least not from the NIN Meraverse.
Controlability Users will have ownership and control over their lands without relying on centralized authorities.
Responsibility Users will have greater responsibilities as they gain more autonomy in managing and developing their lands.
Phase III-1
It will be disclosed in Phase III
Phase IV
Openverse
It will be disclosed in Phase IV
IV)
Open Community Decision-making and management processes will be collectively controlled and guided by the community, rather than by a centralized authority.
Open Source The source code of the NIN Metaverse will be freely available for anyone to review, contribute to, and improve. It will be maintained by the community.
Open Data As there are many services built on OpenStreetMap (OSM)—such as Leaflet, Mapbox, Uber, and Amazon—there is a wide range of possibilities for Metaverse applications based on the Domain Space information of NIN.Earth. This information will be openly available to everyone, enabling anyone to create their own Metaverse using this open data. The NIN Metaverse is just one example demonstrating how Domain Space information can be utilized.
Last updated