NextGenSoftware.OASIS.Providers.Shared.KeyValueStorage
1.0.0
See the version list below for details.
dotnet add package NextGenSoftware.OASIS.Providers.Shared.KeyValueStorage --version 1.0.0
NuGet\Install-Package NextGenSoftware.OASIS.Providers.Shared.KeyValueStorage -Version 1.0.0
<PackageReference Include="NextGenSoftware.OASIS.Providers.Shared.KeyValueStorage" Version="1.0.0" />
<PackageVersion Include="NextGenSoftware.OASIS.Providers.Shared.KeyValueStorage" Version="1.0.0" />
<PackageReference Include="NextGenSoftware.OASIS.Providers.Shared.KeyValueStorage" />
paket add NextGenSoftware.OASIS.Providers.Shared.KeyValueStorage --version 1.0.0
#r "nuget: NextGenSoftware.OASIS.Providers.Shared.KeyValueStorage, 1.0.0"
#:package NextGenSoftware.OASIS.Providers.Shared.KeyValueStorage@1.0.0
#addin nuget:?package=NextGenSoftware.OASIS.Providers.Shared.KeyValueStorage&version=1.0.0
#tool nuget:?package=NextGenSoftware.OASIS.Providers.Shared.KeyValueStorage&version=1.0.0
NextGenSoftware.OASIS.Providers.Shared.KeyValueStorage
Complete OASIS storage provider implementation (avatars, avatar details, holons, parent/child links, search, import/export) over any key-value or blob service. Used by the edge KV and blob storage providers. https://oasisomniverse.one
Installation
dotnet add package NextGenSoftware.OASIS.Providers.Shared.KeyValueStorage
NuGet versions · Source project
Choose a published version compatible with the other OASIS packages in your application. This guide describes current source; older packages may not contain the same functionality.
Frameworks and dependencies
Declared target frameworks: net10.0.
Direct external package references:
NextGenSoftware.OASIS.API.Core
Project references and conditional dependency versions are recorded in the source project. NuGet restore resolves packaged dependencies; do not mix arbitrary DLLs from different release graphs.
Integration and configuration
Use this package for the responsibility described above, alongside its owning OASIS runtime/provider integration. Inspect the source project's public APIs and owning component documentation for construction and configuration; this package installation command does not start an API server, authenticate an avatar or provision an external service.
Provider adapters require their respective service configuration and credentials. Runtime libraries require the host application's lifecycle and persistent paths where applicable. Supply only the settings actually required by the owning component; do not copy production DNA into a client or public release.
Errors and security
For APIs returning OASISResult<T>, check IsError, ErrorCode and Message; do not treat a failed result as success. Preserve useful diagnostics without logging access tokens, passwords or private keys. Keep secrets in the host's appropriate protected configuration or platform storage.
Platform requirements
Target-framework compatibility is not proof that every native dependency or external service works on every operating system. Check the selected version's platform assets and native/service requirements before deployment. Unity/mobile integrations require their supported platform layer and packaging workflow; a managed NuGet archive alone does not establish Android/iOS, IL2CPP or two-device convergence acceptance.
Troubleshooting
- Restore/assembly mismatch: pin a coherent set of package versions and inspect the dependency graph.
- Configuration or authentication error: inspect the owning component's result diagnostics and service requirements without exposing secrets.
- Native loading failure: verify OS/architecture and required native artifacts rather than suppressing the error.
- Missing functionality in an older version: compare the immutable released source and release notes, not only the moving Development branch.
Releases and further documentation
Verified release matrix · Documentation audit
Published NuGet versions are immutable. Updated documentation ships with a new unpublished package version after checked promotion and publication. This metadata-backed guide does not replace product-specific API examples or claim unverified platform tests.
| Product | Versions 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. |
-
net10.0
- NextGenSoftware.OASIS.API.Core (>= 2.0.5)
NuGet packages (114)
Showing the top 5 NuGet packages that depend on NextGenSoftware.OASIS.Providers.Shared.KeyValueStorage:
| Package | Downloads |
|---|---|
|
NextGenSoftware.OASIS.API.Providers.SOLANAOASIS
Connects the OASIS to Solana -- capable of 65,000+ transactions per second with sub-second finality and sub-cent fees. Stores OASIS holons, avatars, NFTs, and token data on Solana programs. Ideal for high-frequency OASIS data workloads. Part of the OASIS HOT-Swappable Provider Architecture -- switch providers at runtime, zero code changes. Ecosystem: https://oasisomniverse.one |
|
|
NextGenSoftware.OASIS.API.Providers.EthereumOASIS
Connects the OASIS to Ethereum -- the world's leading smart contract platform. Stores OASIS holons, avatars, and NFTs on-chain, interacts with EVM-compatible contracts, and participates in the Ethereum DeFi ecosystem. Fully integrated with the OASIS HOT-Swappable Provider Architecture -- switch to or from Ethereum at runtime with zero code changes. Write-Once-Deploy-Everywhere across 55+ providers. REST API: https://api.web4.oasisomniverse.one | Ecosystem: https://oasisomniverse.one |
|
|
NextGenSoftware.OASIS.API.Providers.ChainLinkOASIS
Connects the OASIS to Chainlink -- the industry-standard decentralised oracle network providing tamper-proof data feeds, verifiable randomness (VRF), and Cross-Chain Interoperability Protocol (CCIP). Enables OASIS holons and contracts to consume real-world data and communicate cross-chain. Part of the OASIS HOT-Swappable Provider Architecture. Ecosystem: https://oasisomniverse.one |
|
|
NextGenSoftware.OASIS.API.Providers.IPFSOASIS
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 |
|
|
NextGenSoftware.OASIS.API.Providers.EOSIOOASIS
Connects the OASIS to EOSIO -- the delegated proof-of-stake blockchain with feeless transactions (resource model), 4,000+ TPS, and WASM smart contracts. Stores OASIS holons, avatars, and tokens on EOS mainnet or sidechains. Part of the OASIS HOT-Swappable Provider Architecture. Ecosystem: https://oasisomniverse.one |
GitHub repositories
This package is not used by any popular GitHub repositories.
NextGenSoftware.OASIS.Providers.Shared.KeyValueStorage v1.0.0
Complete OASIS storage provider implementation (avatars, avatar details, holons, parent/child links, search, import/export) over any key-value or blob service. Used by the edge KV and blob storage providers. https://oasisomniverse.one/
What's new for this initial public release
- chore: preserve pending workspace changes (76823ca)
- docs(packages): add missing NuGet guides and release setup sections (77c65ea)
- feat(providers): add shared key-value storage provider base with tests (8a176bf)
- fix(packaging): explicitly include newly documented package readmes (5be30be)
Full changelog
https://github.com/NextGenSoftwareUK/OASIS/commits/master/Providers/Shared/NextGenSoftware.OASIS.Providers.Shared.KeyValueStorage