NextGenSoftware.OASIS.OASISBootLoader 2.0.0

.NET 10.0 This package targets .NET 10.0. The package is compatible with this framework or higher. 
dotnet add package NextGenSoftware.OASIS.OASISBootLoader --version 2.0.0
                    


                    

                
NuGet\Install-Package NextGenSoftware.OASIS.OASISBootLoader -Version 2.0.0
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="NextGenSoftware.OASIS.OASISBootLoader" Version="2.0.0" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="NextGenSoftware.OASIS.OASISBootLoader" Version="2.0.0" />
                    


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="NextGenSoftware.OASIS.OASISBootLoader" />
                    


                            Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package. 
paket add NextGenSoftware.OASIS.OASISBootLoader --version 2.0.0
                    


                    

                
#r "nuget: NextGenSoftware.OASIS.OASISBootLoader, 2.0.0"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
#:package NextGenSoftware.OASIS.OASISBootLoader@2.0.0
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package. 
#addin nuget:?package=NextGenSoftware.OASIS.OASISBootLoader&version=2.0.0
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=NextGenSoftware.OASIS.OASISBootLoader&version=2.0.0
                    


                            Install as a Cake Tool

NextGen Software WEB4 OASIS API BootLoader

Responsible for Booting The OASIS & managing the various OASIS Providers. Used by various OASIS Packages such as OASIS.API.Integrated.Native.EndPoint, STAR & others.

Initial Release targeting OASIS API v2.3.1 (Current LIVE REST version):
https://api.oasisweb4.one

Full documentation and source code can be found here:
https://github.com/NextGenSoftwareUK/Our-World-OASIS-API-HoloNET-HoloUnity-And-.NET-HDK

Make sure you check out the Overview and Benefits Of Building On The WEB 4 OASIS API sections above! 😃 Thank you!

Product Compatible and additional computed target framework versions.
.NET net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (10)

Showing the top 5 NuGet packages that depend on NextGenSoftware.OASIS.OASISBootLoader:

Package Downloads
NextGenSoftware.OASIS.API.ONODE.BLL

This sit's at a higher level of abstraction over OASIS API Core, and acts as the main BLL (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 ONODE. OASIS API Core does not use the OASISBootLoader because it is at a lower level in the stack and so interface implementions (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.Core.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.
NextGenSoftware.OASIS.API.Native.Integrated.EndPoint

The OASIS API Native Integrated EndPoint. To be used to integrate the OASIS API directly into target applications (including Unity) instead of using the existing REST API. Can be used for offline/poor connection use cases, etc. This version will also of course be faster than the REST API. This version also contains some functionality not currently implemented in the REST API.
NextGenSoftware.OASIS.STAR

STAR (Spatial Transmutation And Reality) ODK — the Omniverse Technology Abstraction Runtime for building OAPPs, holonic quests, NFT items, and multiplayer experiences on the OASIS API.
NextGenSoftware.OASIS.Web6.Core

The Core (Business Logic Layer) for WEB6 - the AI abstraction layer of the OASIS Omniverse. Provides a unified interface across AI providers (OpenAI, Anthropic, Ollama and more), hosts the OASIS MCP Server integration, and enables AI-augmented avatar interactions, quest generation and holonic reasoning.
NextGenSoftware.OASIS.Web7.Core

The Core (Business Logic Layer) for WEB7 - the non-invasive human/AI symbiosis layer of the OASIS Omniverse. Hosts the BioSignalProcessingManager (EEG, HRV, GSR), IntentionEngine, SymbiosisSessionManager (Borg-Free pledge enforced) and CollectiveConsciousnessManager for multi-participant shared intention fields.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
2.0.0 0 7/12/2026
1.0.5 1,672 2/3/2023
1.0.4 1,099 1/19/2023
1.0.3 484 1/4/2023
1.0.2 1,709 9/1/2022
1.0.1 1,343 8/30/2022
1.0.0 1,300 8/25/2022

- OASIS Omniverse Reboot and Rebrand: major ecosystem relaunch under oasisomniverse.one after ~3 years of deep development.
- Added WEB6 (The AI Layer) with full LLM routing via FAHRN — supports OpenAI, Anthropic Claude, Cohere, HuggingFace, and Azure OpenAI.
- Added WEB7 (The Spatial/AR Layer), WEB8 (The Holographic Layer), WEB9 (The Neural Layer), and WEB10 (The Omniversal Layer) decentralised API tiers.
- Added ONET P2P network with FAHRN (Federated Adaptive Holonic Routing Network) and HolonicBraid mesh routing.
- Added OASIS HyperDrive v2 with DHT-based distributed storage and replication.
- Added OASIS MCP Server for seamless WEB4-WEB10 tool integration.
- Full implementation of all remaining provider interface stubs across all ~55 OASIS Providers.
- Security overhaul: CORS hardening (open/pluggable API policy), JWT validation fixes, NuGet vulnerability remediation across all projects.
- Fixed GetKarmaAsync returning 0: now falls back to AvatarDetail.Karma when in-memory cache is empty.
- Auto-creates AvatarDetail on first karma award if it does not exist yet.
- Fixed MongoDB holon save always inserting instead of updating for REST clients.
- Fixed circular reference serialisation causing truncated JSON in loadHolon responses.
- Fixed null max_tokens causing 400 errors across OpenAI, Cohere, AzureOpenAI, and HuggingFace providers.
- JWT middleware now skips silently on invalid tokens; AuthorizeAttribute handles the decision.
- PreferOpenServ, EnableFAHRN, EnableHolonicBraid, and ApiKeys added to OASIS_DNA.json.
- Added optional returnUrl parameter to forgot-password endpoint.
- Made OldPassword optional in ResetPassword (not required when using a reset token).
- Changed license to GNU Affero General Public License v3 (AGPL3).
- Numerous bug fixes, stability improvements, and performance enhancements.
- Upgraded all projects to .NET 10 — the latest LTS runtime with improved performance, lower memory footprint, and new language features.
- Miscellaneous stability improvements and internal refactoring across all layers.
- Improved async/await patterns and cancellation token propagation throughout.
- Better null safety and nullable reference type annotations.
- Refined logging output for easier diagnostics.
- Various minor bug fixes identified during the WEB6-10 integration testing phase.
- Many misc improvements.
- Multiple bug fixes.