Solana Smart Contract

This module is responsible for loading and managing the OASISDNA.json config file. This is where all of the settings for the ONODE are kept such as settings for each OASIS Provider configured for that ONODE, which ones to use for auto-replication, auto-loadbalance, auto-failover, email, authentication, security, error handling, encryption, logging settings etc.

This is the heart of the OASIS and contains the core OASIS Engine, architecture, managers, interfaces, helpers, holons/objects, object model, enums, etc. It can be used directly in projects/apps if needed (you can use any of the Managers) but it is highly recommended you use the OASIS.API.Native.Integrated.EndPoint or REST API instead.

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.

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

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.