NextGenSoftware.OASIS.API.DNA 2.0.2

The core of the OASIS (Open API System / Omniverse Interoperability System) -- the GOD Protocol and API powering the decentralised Web4-Web10 Omniverse. Contains the OASIS Engine, HOT-Swappable Provider Architecture, Avatar API, Karma API, Holon/Data API, Keys/Wallets API, SEEDS API, and all core interfaces, managers, object models, and enums. Supports 55+ blockchain and decentralised network providers with Auto-FailOver, Auto-LoadBalancing, Auto-Replication, Auto-Sync, Write-Once-Deploy-Everywhere, Offline Support, and Triple-Level Quantum-Resistant Encryption. Explore the full OASIS Omniverse ecosystem at https://oasisomniverse.one -- Source code: https://github.com/NextGenSoftwareUK/OASIS -- REST API: https://api.web4.oasisomniverse.one

The OASIS BootLoader provides a single entry point to initialise the entire OASIS ecosystem in any .NET application. Reads OASISDNA configuration, registers and activates all configured providers, sets up Auto-FailOver/LoadBalancing, and returns a ready-to-use OASIS instance. Integrate 55+ decentralised networks into your app with just a few lines of code. Part of the OASIS Omniverse at https://oasisomniverse.one

Connects the OASIS to IPFS -- the content-addressed, peer-to-peer hypermedia protocol for permanent, decentralised data storage. Stores OASIS holons, avatar metadata, and binary assets on IPFS with CID-based addressing ensuring data integrity. Optionally pins to Filecoin for long-term persistence. Part of the OASIS HOT-Swappable Provider Architecture. Ecosystem: https://oasisomniverse.one

This sit's at a higher level of abstraction over OASIS API Core, and acts as the main Core (Business Logic Layer) to the OASIS API, whereas OASIS API Core is the core architecture and hosts the central managers such as ProviderManager, AvatarManager, HolonManager, etc, This package contains more higher level Managers (such as OLANDManager, MissionManager, ParksManager, MapManager, QuestManager, SEEDSManager, etc) and use cases built on top of OASIS API Core. This module also uses the OASISBootLoader to manage loading and using the OASISDNA/config for the ONODEONODE. OASIS API Core does not use the OASISBootLoader because it is at a lower level in the stack and so interface implementations (OASIS Providers) need to be manually injected into each Manager's constructor (DI) whereas this module and the OASISBootLoader manages all of this for you via the OASISDNA.json config file. Both OASIS.API.Native.Integrated.EndPoint & the REST API both use this module/package and provide a wrapper around it and are the recommeneded ways to use the OASIS API.

WEB4 OASIS API PinataOASIS Provider is one of the many WEB2/WEB3 providers that plug in and integtate into the OASIS.