Main Page: Difference between revisions

From Open Metaverse Wiki
Line 69: Line 69:
:**** [[Various Permissioned NFT 3d Assets]]
:**** [[Various Permissioned NFT 3d Assets]]
:**** [[Why Metaverse Governance Needs to Be Internal|Blockchain Based Community Governance]]
:**** [[Why Metaverse Governance Needs to Be Internal|Blockchain Based Community Governance]]
:**** [[Juried IP Dispute Resolution and Perceptual Hashes]]
:*** [[Modernized Versatile Avatar System]]
:*** [[Modernized Versatile Avatar System]]
:**** [[Improved Armature System]]
:**** [[Improved Armature System]]

Revision as of 05:50, 12 February 2023

Welcome to the Open Metaverse Wiki

About This Wiki

This wiki is presented by the Open Metaverse Research Group, a not-for-profit group of volunteers who are active in virtual worlds and deeply interested in supporting the development of an interoperable, scalable, non-proprietary metaverse based on existing and still to be developed "grids" or whatever succeeds the grid concept of metaverse elements.

About Us

Our group is called the Open Metaverse Research Group. See our About Us page for more details.

A Preliminary Outline

This mindmap is presented as a conversation-starter. It also has been suggested as an outline for this wiki. The following sections are based on this mindmap.

Concepts

  • Basic Precepts
    • OpenSource: The backbone of an open metaverse must be open source and built to enable many types of applications (VR/VW/AR/XR) to run on top of it, like HTML and to a lesser extent, VRML were intended.
    • Standards-based: Creating standards for an open sourced backbone, as well as for applications that run on it, are helpful to build trust in the code people are interacting with.
    • Interoperable: All operating systems must be able to access and use the backbone open metaverse service provided they have internet access by any means.
    • Protective of Privacy: The rights of the user to privacy, to be forgotten, to keeping their communications secure and encrypted without back doors, is sacrosanct.
  • Requirements
    • Decentralized Data: Data should not be controlled by any centralized system. This eliminates all centralized database systems from consideration, as well as proprietary ownership of the backbone.
    • Standards: Standards developed in a public way that is open to public comment ensures that the general public is fully informed to buy into the new system.
    • Non-proprietary: Making the backbone non-proprietary and distributed widely with many nodes handling transactions ensures continuity of the metaverse regardless of the fiscal or organizational health of any one group.
    • Data privacy: Using public key encryption of long key length to be resistant not only to botnet brute force attacks but against quantum computer attacks is essential to ensuring privacy of user data.
  • Structure
    • Interconnected independent grids: Proprietary grid/platform operators are all able to use the same backbone independently and fairly, building their own stake in the system and earning revenues from operating backbone nodes.
    • Geography-based: Users, and platforms built atop the backbone will obviously use the closest resources possible to ensure the lowest latency virtual experience, but the infrastructure of the network needs to be built in ways that help ensure latency is minimized for even the most remote users to encourage ease of access.

Mechanics

  • Web-based 2D
  • Web3
  • 3D Virtual Worlds
  • VR Head-Mounted Displays (HMDs)
  • Haptics
  • Implants
  • Named-data
  • non-TCP/IP
  • Identity verification
  • Blockchain

TimeLine

  • Present
    • Legacy versions
    • Fragmentation
    • Research
    • Planning

About the Metaverse

<youtube>https://www.youtube.com/watch?v=ZSgitLzAIis</youtube>

Links about the Metaverse

Articles

Other Organizations

Data Storage for the Open Metaverse