STAR ODK Runtime v3.3.3

This is the fourth release of the STAR ODK Runtime, which is automatically included in all generated OAPPs by STAR. There are 2 versions, one that is just the STAR ODK Runtime, the other also comes integrated with the OASIS Runtime (divided into a further 2 versions, one that includes HoloNET with the Holochain Conductors embedded and the other without).

This release has many improvements from the previous release such as:

• Overhauled everything!
• Re-built the STAR CLI Lib - now split out into modules which can be easily extended and now uses a new STARNETUIBase to add new modules.
• Brand new STAR API with over 20+ new APIs for managing OAPPS, Quests, Missions, NFTs, GeoNFTs, NFT Collections, GeoNFT Collections, Geohotspots, Inventory Items, Zomes, Holons, Celestial Bodies, CelestialSpaces, MetaData & more! It now also includes a new COSMIC API allowing people to create anything they like within their very own multiverse.
• Upgrades to STAR CLI & STARNET with new commands such as nft collections, geonft collections, clone & lots more! There are now over 548 commands!
• Also the backend in the new STAR API uses the generic STARNETManagerBase which can easily be extended to add new modules.
• ONODE / STAR ODK integrations.
• STAR CLI and STARNET improvements, templating and runtime embedding; STAR ODK upgrades to coordinate the above engine/interface changes.
• Rebuilt the No/Low Code Generator/Templating Engine with many improvements such as metatags and holon meta tags allowing custom data to be injected into OAPPs similar to CMS & beyond!
• Related to above each provider now implements its own custom low code generation allowing custom code to be generated for each provider.
• New COSMIC API for the STAR API allowing custom multiverses to be created for each avatar as well as The Great Simulation & The MagicVerse.
• New Plugin System allowing STARNET to be easily extended.
• New interop Library system allowing libs in any stack language to be used in your OAPP.
• Multiple bug fixes.
• Misc improvements.
• Layout improvements.
• Lots more! Too many changes to list here!

Full Changelog: STAR-ODK-Runtime-v2.2.0...STAR-ODK-Runtime-v3.3.3

The STAR ODK Runtime requires the OASIS Runtime to run so has a dependency on it. This version is dependent on OASIS Runtime v4.4.4.

The STAR ODK Runtime consists of:

NextGenSoftware.OASIS.STAR.dll - The main STAR Engine (used to generate OAPPs).
NextGenSoftware.OASIS.STAR.CLI.dll - The STAR CLI Engine (the CLI to the STAR Engine), this uses the STAR CLI Lib.
NextGenSoftware.OASIS.STAR.CLI.Lib.dll - The STAR CLI Lib (that can be used in generated OAPPs).
STAR.exe - The STAR CLI executable (entry point).

OASIS Runtime v4.4.4

This version is v4.4.4, however the the current LIVE OASIS API HTTP REST Service (also uses the same OASIS Runtime), is currently v4.0.0. A new release of this will also be made shortly...

https://oasisweb4.one/api

This release has many improvements from the previous release such as:

• Over 50+ providers for web2 and web3 now completed including Optimism, BNBChain, Bitcoin, Avalanche, Cardano, Bitcoin, Blockstack, Cosmos, Elrond, EOSIO, Ethereum, Fantom, Hashgrapth, Moralis, Near, Polygon, Rootstock, Solana, Telos, Sui, Tron, AWS, Azure, GoogleCloud, GO, Mapbox, WRLD3D, ActivityPub, SOLID, IPFS, Pinata, Scuttlebug, Threefold, ONION, Orion, SEEDS, Neo4j, SQLite, MongoDB & more!
• New OASIS HyperDrive v2 which now includes auto load balancing, AI Predictive Failover, Analytics, AI powered Smart Mode & more!
• New bespoke P2P ONET which merges all of web2, web3, OASIS HyperDrive, HoloNET (Holochain) and also networking protocols such as http, tcp, websockets, QUIC, gRPC & more into a fully unified API and network of networks, an abstraction layer over everything.
• Data API upgrade/overhaul.
• NFT API has been completely rewritten making it truly web4 now wrapping multiple web3 nfts that share the parent web4 nft and optionally overwriting any web4 Meta data meaning your nft appears across multiple chains sharing the same Meta data and allowing variants per chain. Very powerful system, truly web4 now, before it was more web3.5. It's now NFT API v2
• GeoNFT API upgraded.
• Added collections to the NFT API & the GeoNFT API.
• WEB4 NFT/GeoNFT's now wrap multiple WEB3 NFT's which share metadata with their parent WEB4 NFT/GeoNFT.
• NFT batching, improved error handling/retry logic etc.
• Cross-chain minting/sending & lots more!
• Added new API's such as video, bridging, chat, competition, eggs, files, gifts, health, HyperDrive v2.0, messaging, ONET, ONODE, settings, share, social, stats, subscription & video!
• Major Data API overhaul — more flexible, higher-performance data endpoints and richer request options per-call (auto-replication, auto-load-balance, auto-failover, provider lists, etc.).
• NFT & GeoNFT rewrites and feature additions — richer NFT model, collections support, cross-chain minting, batching, improved retry/error logic and new GeoNFT capabilities.
• Keys / Wallets API: new unified wallet model, provider wallets, wallet transactions, local encrypted storage (LocalFileOASIS), and improved key management (AES256 encryption, wallet IDs, new wallet manager/API).
• Provider APIs and interfaces modernized.
• Many provider interfaces gained async variants (ActivateProviderAsync, DeActivateProviderAsync, SendNFT/Mint changes, Search/Import/Export methods, etc.).
• Blockchain provider methods return richer TransactionRespone objects instead of simple bools.
• OASIS Runtime & Native endpoint upgrades.
• New OASIS Runtimes and a Native Integrated EndPoint package (embed OASIS runtime directly into apps, offline-capable).
• Setup projects for runtime installation (GAC) and runtime packaging improvements.
• Authentication / Avatar model changes:
• Username uniqueness introduced; Avatar / AvatarDetail restructuring; new auth behaviours, UMA JSON handling and improved JWT handling.
• Performance, stability, and cross-cutting improvements:
• Upgrades to .NET (moved up toward .NET 8), numerous bug fixes, refactors, and improved error handling/reporting across the stack.
• Various performance improvements.
• Numerous bug fixes.
• Misc improvements.
• Plus lots more! ;-)

Full Changelog: OASIS-Runtime-v3.3.1...OASIS-Runtime-v4.4.4

This runtime is designed to be used in OAPP's (OASIS Applications) that can work both online and offline and because they are using the OASIS API directly through the native integrated DLL's they are also faster than making calls to the HTTP REST Service.

NOTE - The packages below have not been updated yet to work with the latest runtime yet, they will be soon...

NuGet Packages:

The NextGenSoftware.OASIS.API.Native.Integrated.EndPoint NuGet package wraps around the OASIS Runtime providing an entry-point into the API. The OASIS Runtime is not designed to be used directly on its own but you can be if you wish. It is recommended you use either the OASIS API REST Service or the NextGenSoftware.OASIS.API.Native.Integrated.EndPoint NuGet package.

STAR ODK Runtime v2.2.0

This is the third release of the STAR ODK Runtime, which is automatically included in all generated OAPPs by STAR. There are 2 versions, one that is just the STAR ODK Runtime, the other also comes integrated with the OASIS Runtime (divided into a further 2 versions, one that includes HoloNET with the Holochain Conductors embedded and the other without).

This release has many improvements from the previous release such as:

• New OASIS OAPP API has been integrated into the STAR CLI (this allows STAR to now generate, publish, unpublish, install, launch, uninstall, list and search for OAPPs).
• Improved NFT Integration. (now supports ERC 721, ERC 1155 & MetaPlex standards as well as now being able to store the NFT metadata on the OASIS so it benefits from the OASIS Hyprdrive with the Auto-failover, Auto-load balancing & auto load-replication features. They can also choose to store on IPFS or Pinata).
• Improved GeoNFT Integration.
• Added Arbitrum, RootStock & Polygon support.
• Light Wizard improvements.
• Multiple bug fixes.
• Misc improvements.
• Layout improvements.
• Lots more!

Full Changelog: STAR-ODK-Runtime-2.1.0...STAR-ODK-Runtime-v2.2.0

The STAR ODK Runtime requires the OASIS Runtime to run so has a dependency on it. This version is dependent on OASIS Runtime v3.3.1.

The STAR ODK Runtime consists of:

NextGenSoftware.OASIS.STAR.dll - The main STAR Engine (used to generate OAPPs).
NextGenSoftware.OASIS.STAR.CLI.dll - The STAR CLI Engine (the CLI to the STAR Engine), this uses the STAR CLI Lib.
NextGenSoftware.OASIS.STAR.CLI.Lib.dll - The STAR CLI Lib (that can be used in generated OAPPs).
STAR.exe - The STAR CLI executable (entry point).

OASIS Runtime v3.3.1

This version is v3.3.1, however the the current LIVE OASIS API HTTP REST Service (also uses the same OASIS Runtime), is currently v3.0.0. A new release of this will also be made shortly...

https://api.oasisplatform.world.

This release has many improvements from the previous release such as:

• New OAPP API for loading, searching, creating, publishing, unpublising, installing, uninstalling & launching OAPP's.
• Improved NFT Integration. (now supports ERC 721, ERC 1155 & MetaPlex standards as well as now being able to store the NFT metadata on the OASIS so it benefits from the OASIS Hyprdrive with the Auto-failover, Auto-load balancing & auto load-replication features. They can also choose to store on IPFS or Pinata).
• Added Arbitrum, RootStock & Polygon support.
• Multiple bug fixes.
• Misc improvements.
• Lots more!

Full Changelog: OASIS-Runtime-v3.2.2...OASIS-Runtime-v3.3.1

This runtime is designed to be used in OAPP's (OASIS Applications) that can work both online and offline and because they are using the OASIS API directly through the native integrated DLL's they are also faster than making calls to the HTTP REST Service.

NOTE - The packages below have not been updated yet to work with the latest runtime yet, they will be soon...

NuGet Packages:

The NextGenSoftware.OASIS.API.Native.Integrated.EndPoint NuGet package wraps around the OASIS Runtime providing an entry-point into the API. The OASIS Runtime is not designed to be used directly on its own but you can be if you wish. It is recommended you use either the OASIS API REST Service or the NextGenSoftware.OASIS.API.Native.Integrated.EndPoint NuGet package.

STAR ODK Runtime v2.1.0

This is the second release of the STAR ODK Runtime, which is automatically included in all generated OAPPs by STAR. There are 2 versions, one that is just the STAR ODK Runtime, the other also comes integrated with the OASIS Runtime (divided into a further 2 versions, one that includes HoloNET with the Holochain Conductors embedded and the other without).

Changes:

This release has many improvements from the previous release such as:

• NFT Integration.
• GeoNFT Integration.
• Light Wizard improvements.
• Multiple bug fixes.
• Misc improvements.
• Layout improvements.
• STAR ODK Console Template improvements & fixes.
• Lots more!

Full Changelog: STAR-ODK-Runtime-2.0.1...STAR-ODK-Runtime-v2.1.0

The STAR ODK Runtime requires the OASIS Runtime to run so has a dependency on it. This version is dependent on OASIS Runtime v3.2.2.

The STAR ODK Runtime consists of:

• NextGenSoftware.OASIS.STAR.dll - The main STAR Engine (used to generate OAPPs).
• NextGenSoftware.OASIS.STAR.CLI.dll - The STAR CLI Engine (the CLI to the STAR Engine), this uses the STAR CLI Lib.
• NextGenSoftware.OASIS.STAR.CLI.Lib.dll - The STAR CLI Lib (that can be used in generated OAPPs).
• STAR.exe - The STAR CLI executable (entry point).

OASIS Runtime v3.2.2

This version is v3.2.2, however the the current LIVE OASIS API HTTP REST Service (also uses the same OASIS Runtime), is currently v3.0.0. A new release of this will also be made shortly...

https://api.oasisplatform.world.

Full Changelog: OASIS-Runtime-v3.2.1...OASIS-Runtime-v3.2.2

This runtime is designed to be used in OAPP's (OASIS Applications) that can work both online and offline and because they are using the OASIS API directly through the native integrated DLL's they are also faster than making calls to the HTTP REST Service.

NuGet Packages:

The NextGenSoftware.OASIS.API.Native.Integrated.EndPoint NuGet package wraps around the OASIS Runtime providing an entry-point into the API. The OASIS Runtime is not designed to be used directly on its own but you can be if you wish. It is recommended you use either the OASIS API REST Service or the NextGenSoftware.OASIS.API.Native.Integrated.EndPoint NuGet package.

STAR ODK Runtime v2.0.1

This is the first release of the STAR ODK Runtime, which is automatically included in all generated OAPPs by STAR. There are 2 versions, one that is just the STAR ODK Runtime, the other also comes integrated with the OASIS Runtime (divided into a further 2 versions, one that includes HoloNET with the Holochain Conductors embedded and the other without).

The STAR ODK Runtime requires the OASIS Runtime to run so has a dependency on it. This version is dependent on OASIS Runtime v3.2.1.

The STAR ODK Runtime consists of:

• NextGenSoftware.OASIS.STAR.dll - The main STAR Engine (used to generate OAPPs).
• NextGenSoftware.OASIS.STAR.CLI.dll - The STAR CLI Engine (the CLI to the STAR Engine), this uses the STAR CLI Lib.
• NextGenSoftware.OASIS.STAR.CLI.Lib.dll - The STAR CLI Lib (that can be used in generated OAPPs).
• STAR.exe - The STAR CLI executable (entry point).

OASIS Runtime v3.2.1

This version is v3.2.1, however the the current LIVE OASIS API HTTP REST Service (also uses the same OASIS Runtime), is currently v3.0.0. A new release of this will also be made shortly...

https://api.oasisplatform.world.

There are way too many fixes and improvements to list them all here! ;-) We intend to give more info on changes for upcoming versions...

Full Changelog: v3.2.0...v3.2.1

This runtime is designed to be used in OAPP's (OASIS Applications) that can work both online and offline and because they are using the OASIS API directly through the native integrated DLL's they are also faster than making calls to the HTTP REST Service.

NuGet Packages:

The NextGenSoftware.OASIS.API.Native.Integrated.EndPoint NuGet package wraps around the OASIS Runtime providing an entry-point into the API. The OASIS Runtime is not designed to be used directly on its own but you can be if you wish. It is recommended you use either the OASIS API REST Service or the NextGenSoftware.OASIS.API.Native.Integrated.EndPoint NuGet package.

Full Changelog: OASIS-Runtime-v3.2.0...OASIS-Runtime-v3.2.1

OASIS Runtime v3.2.0

This version is v3.2.0, however the the current LIVE OASIS API HTTP REST Service (also uses the same OASIS Runtime), is currently v3.0.0. A new release of this will also be made shortly...

https://api.oasisplatform.world.

There are way too many fixes and improvements to list them all here! ;-) We intend to give more info on changes for upcoming versions...

Full Changelog: v2.3.1...v3.2.0

This runtime is designed to be used in OAPP's (OASIS Applications) that can work both online and offline and because they are using the OASIS API directly through the native integrated DLL's they are also faster than making calls to the HTTP REST Service.

NuGet Packages:

The NextGenSoftware.OASIS.API.Native.Integrated.EndPoint NuGet package wraps around the OASIS Runtime providing an entry-point into the API. The OASIS Runtime is not designed to be used directly on its own but you can be if you wish. It is recommended you use either the OASIS API REST Service or the NextGenSoftware.OASIS.API.Native.Integrated.EndPoint NuGet package.

OASIS Runtime v2.3.1

This is the first release of the OASIS Runtime. The version is v2.3.1 so it stays in sync with the current LIVE OASIS API HTTP REST Service (also uses the same OASIS Runtime), which is currently at v2.3.1:

https://api.oasisplatform.world.

This runtime is designed to be used in OAPP's (OASIS Applications) that can work both online and offline and because they are using the OASIS API directly through the native integrated DLL's they are also faster than making calls to the HTTP REST Service.

The NextGenSoftware.OASIS.API.Native.Integrated.EndPoint NuGet package wraps around the OASIS Runtime providing an entry-point into the API. The OASIS Runtime is not designed to be used directly on its own but you can be if you wish. It is recommended you use either the OASIS API REST Service or the NextGenSoftware.OASIS.API.Native.Integrated.EndPoint NuGet package.