NextGenSoftware.OASIS.API.Providers.TRONOASIS
2.0.6
dotnet add package NextGenSoftware.OASIS.API.Providers.TRONOASIS --version 2.0.6
NuGet\Install-Package NextGenSoftware.OASIS.API.Providers.TRONOASIS -Version 2.0.6
<PackageReference Include="NextGenSoftware.OASIS.API.Providers.TRONOASIS" Version="2.0.6" />
<PackageVersion Include="NextGenSoftware.OASIS.API.Providers.TRONOASIS" Version="2.0.6" />
<PackageReference Include="NextGenSoftware.OASIS.API.Providers.TRONOASIS" />
paket add NextGenSoftware.OASIS.API.Providers.TRONOASIS --version 2.0.6
#r "nuget: NextGenSoftware.OASIS.API.Providers.TRONOASIS, 2.0.6"
#:package NextGenSoftware.OASIS.API.Providers.TRONOASIS@2.0.6
#addin nuget:?package=NextGenSoftware.OASIS.API.Providers.TRONOASIS&version=2.0.6
#tool nuget:?package=NextGenSoftware.OASIS.API.Providers.TRONOASIS&version=2.0.6
NextGen Software WEB4 OASIS API TRON OASIS Provider
WEB4 OASIS API TRON OASIS Provider is one of the many WEB2/WEB3 providers that plug in and integtate into the OASIS.
Native NFT identity and mint contract
TRON NFT descriptors expose NFTStandardType.TRC721 (serialized numeric value 6) and OnChainProvider.TRONOASIS through one shared descriptor factory. Existing standard values 0–5 are unchanged. This identifies the adapter's expected TRC721 ABI; it is not a complete contract-conformance audit or a claim that every indexed asset is discoverable.
For native minting, omit NFTStandardType or explicitly select TRC721; explicit Ethereum/Solana/Sui/Hedera/CosmWasm standards are rejected before wallet lookup. OnChainProvider may be omitted, Default, or TRONOASIS; contradictory explicit chains are rejected. Older clients that explicitly sent ERC721 must now select TRC721 or omit the optional setting. Update clients sharing the Core enum before consuming the new string value.
The existing explicit mint(address,uint256,string) collection extension still requires one token, a minter avatar, a metadata URI, and MetaData entries MintFunctionSignature, TokenAddress, and decimal TokenId. This change does not implement royalties, metadata freezing, cross-collection completeness, off-chain metadata fetching, or coordinator authorization. No implicit mint ABI or NFT identity is invented.
Mint recipients may be an explicit address or an avatar ID, username, email, or a consistent combination. Existing WalletManager lookups resolve only supplied selectors. All must resolve to the same exact canonical TRON wallet address; conflicting selectors, failed lookups and missing wallets stop before native signing, never silently mint to the minter. With no recipient selector, the existing minter-wallet default is retained. The shared NftMintRecipient coordinator is also used by Sui, which supplies its own address-equivalence comparison. Selection does not grant mint authority, fetch credentials, or authorize fees. Recipient lookups can incur storage-provider reads; hosted admission/accounting remains a separate verification gate.
Official TRC721 specification describes TRON's ERC721-compatible interface and TVM-specific behavior. Verification scope and unresolved native transaction/fee/release gates are recorded in Docs/WIP/HyperDrive-Providers/HYPERDRIVE_V2_CURRENT_RELEASE_GATES.md in the parent repository. Unit/gRPC fixture success is not full native or hosted provider certification.
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 | 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
- Grpc.Core (>= 2.46.6)
- Nethereum.ABI (>= 7.0.0)
- Nethereum.Signer (>= 7.0.0)
- NextGenSoftware.OASIS.API.Core (>= 2.0.7)
- NextGenSoftware.OASIS.Common (>= 2.0.1)
- NextGenSoftware.OASIS.Providers.Shared.KeyValueStorage (>= 2.0.2)
- TronNet (>= 0.2.0)
NuGet packages (1)
Showing the top 1 NuGet packages that depend on NextGenSoftware.OASIS.API.Providers.TRONOASIS:
| 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.
NextGenSoftware.OASIS.API.Providers.TRONOASIS v2.0.6
Connects the OASIS to TRON -- high-throughput blockchain optimised for entertainment and gaming with 2,000+ TPS, minimal fees, and TRC-20/TRC-721 support. Stores OASIS holons, avatars, and tokens. Part of the OASIS HOT-Swappable Provider Architecture. 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.TRONOASIS