NextGenSoftware.OASIS.API.Providers.PolygonOASIS 2.0.6

dotnet add package NextGenSoftware.OASIS.API.Providers.PolygonOASIS --version 2.0.6
                    
NuGet\Install-Package NextGenSoftware.OASIS.API.Providers.PolygonOASIS -Version 2.0.6
                    
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.API.Providers.PolygonOASIS" Version="2.0.6" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="NextGenSoftware.OASIS.API.Providers.PolygonOASIS" Version="2.0.6" />
                    
Directory.Packages.props
<PackageReference Include="NextGenSoftware.OASIS.API.Providers.PolygonOASIS" />
                    
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.API.Providers.PolygonOASIS --version 2.0.6
                    
#r "nuget: NextGenSoftware.OASIS.API.Providers.PolygonOASIS, 2.0.6"
                    
#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.API.Providers.PolygonOASIS@2.0.6
                    
#: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.API.Providers.PolygonOASIS&version=2.0.6
                    
Install as a Cake Addin
#tool nuget:?package=NextGenSoftware.OASIS.API.Providers.PolygonOASIS&version=2.0.6
                    
Install as a Cake Tool

NextGenSoftware.OASIS.API.Providers.PolygonOASIS

Connects the OASIS to Polygon -- Ethereum's leading L2 scaling solution offering EVM compatibility, dramatically lower fees, and near-instant finality. Stores OASIS holons, avatars, and NFTs on Polygon PoS or zkEVM with full Ethereum interoperability. Part of the OASIS HOT-Swappable Provider Architecture -- 55+ networks. Ecosystem: https://oasisomniverse.one

Installation

dotnet add package NextGenSoftware.OASIS.API.Providers.PolygonOASIS

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](https://github.com/NextGenSoftwareUK/OASIS/blob/Development/Docs/WIP/Release and Status/OASIS_RELEASE_STATUS.md) · [Documentation audit](https://github.com/NextGenSoftwareUK/OASIS/blob/Development/Docs/WIP/Release and Status/RELEASE_DOCUMENTATION_AUDIT.md)

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.

Explicit public Polygon PoS balance CQL profile

PolygonPublicAccountMetadataSource is a separate anonymous read representation. It queries configured mainnet addresses; it does not use a wallet, submit a transaction, scan accounts or write owned records. Canonical PolygonOASIS signed storage remains separate. The common Web3Core EvmPublicAccountMetadataSource owns RPC parsing, bounds, native selection and mapping; each provider supplies its fixed chain/genesis/metadata descriptor.

This profile requires chain0x89and the pinned Polygon genesis. It resolves one RPC-reported finalized block and reads every selected balance with its canonical block hash. There is no latest-block/other-endpoint fallback. Metadata includes PolygonAccountAddress, PolygonChainId, PolygonBlockHash, PolygonBlockNumber, PolygonCommitment and PolygonBalanceWei. Balance values are exact decimal strings in the chain's smallest native unit; they are not ETH-denominated values.

Configuration has exactly schema1, rpcUrl, chainId0x89, addresses and sourceOwner. Use the retained nonsecret catalogue in LocalState/COSMIC/HostedPolygonPublicSourceCurrent. One to eight lowercase20-byte addresses, anonymous root HTTPS,8KiB/depth4JSON and 256KiB/depth16RPC bounds apply. Signer fields/credential paths/auth headers and unknown/duplicate properties are rejected. Keep the mapping owner stable.

// Compose the exact bounded native address selection. No account scan occurs.
var query = CosmicQuery<Holon>
    .Create(CosmicQueryScope.Named(ProviderType.PolygonOASIS).Result)
    .WithReadAccess(CosmicQueryReadAccess.OwnerOrPublic(avatarId).Result)
    .Where(row => selectedAddresses.Contains(
        CosmicQueryMetadata.Value<string>(row, "PolygonAccountAddress")));

if (query.IsError)
    throw new InvalidOperationException(query.Message);

var plan = CosmicQueryPlanner.Plan(
    query.Result,
    ProviderType.PolygonOASIS,
    new[] { new CosmicQueryTarget(ProviderType.PolygonOASIS, source.QueryCapabilities) });

if (plan.IsError)
    throw new InvalidOperationException(plan.Message);

var rows = await source.ExecuteCosmicQueryAsync(
    plan.Result, cancellationToken: cancellationToken);

if (rows.IsError)
    throw new InvalidOperationException(rows.Message, rows.Exception);

Supply source from PolygonPublicAccountMetadataSource.FromJson and await its ActivateQuerySourceAsync before executing, checking IsError. Content/name/description filters, sorting, continuation and arbitrary chain queries are unsupported. Public address-state rows do not prove that COSMIC holons were persisted on-chain or cryptographically verify an RPC-reported finalized state.

Native3/2CQL passes;18controlled Polygon cases plus18affected Ethereum cases pass. Ethereum native3/2and its published C# sample also pass after the shared-reader extraction. Tests reuse the existing EthereumOASIS.CqlTests target with a Polygon reference; no separate runtime/node/environment is required.

WEB4 query-only admission, HTTP discovery/presets, Mongo federation/isolation, replication and hosted/browser acceptance remain next. No hosted Polygon enrollment or complete ORM parity is claimed. The retained local signed-record demo is a different profile. Protocol readiness probe.

WEB4 task integration now registers CQL_POLYGON_PUBLIC_SOURCE_JSON through the isolated query-only profile registry. Explicit read permission/tariff remain separate from signed Polygon storage. Native HTTP acceptance passes3/2and Mongo pairing5/4with foreign-private0/public-pair3; controlled bearer/usage infrastructure is not production login/billing/replication/browser proof.

Use the existing fixture-aware runner -PolygonMongoHttp after a leased bounded build. It retains original intents/ACKs and removes only the owner-checked Mongo fixture on success. Do not replay uncertain writes or replace a retained cohort.

Four Polygon presets can be staged individually with Publish-HostedPolygonPublicConfiguration.py. For the joint Google/Ethereum/Polygon release, prepare Publish-HostedGoogleEthereumConfiguration.py with-polygon. That explicit option composes all3strict validators into5changed values/12presets, preserving wallet DNA and each independent permission/free tariff. No live change occurs during preparation. Use only the matching tested application/Core revision for the scheduled rollout; apply-with-polygon is the explicit journalled mutation. Encrypted snapshots require an explicit PolygonAccountAddress queryable-key grant; the publisher refuses missing policy rather than changing global reserved keys.

Runnable console and HTTP walkthrough: public Polygon CQL guide. The --polygon-public console mode passes native3/2through HolonManager/LINQ, with a native test compiling the actual published sample files.

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 (1)

Showing the top 1 NuGet packages that depend on NextGenSoftware.OASIS.API.Providers.PolygonOASIS:

Package Downloads
NextGenSoftware.OASIS.OASISBootLoader

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

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
2.0.6 151 11/14/2026
2.0.5 147 11/14/2026
2.0.4 346 10/13/2026
2.0.3 210 9/28/2026
2.0.2 168 9/28/2026
2.0.0 352 7/12/2026

NextGenSoftware.OASIS.API.Providers.PolygonOASIS v2.0.6

Connects the OASIS to Polygon -- Ethereum's leading L2 scaling solution offering EVM compatibility, dramatically lower fees, and near-instant finality. Stores OASIS holons, avatars, and NFTs on Polygon PoS or zkEVM with full Ethereum interoperability. Part of the OASIS HOT-Swappable Provider Architecture -- 55+ networks. Ecosystem: https://oasisomniverse.one/

What's new since v2.0.5
- Initial validated package contents and metadata for this release line.

Full changelog
https://github.com/NextGenSoftwareUK/OASIS/commits/master/Providers/Blockchain/NextGenSoftware.OASIS.API.Providers.PolygonOASIS