The universal foundation layer every other layer of the OASIS Omniverse is built on — identity, karma, data, NFTs, tokens and providers, all unified under one API. One avatar, one karma score, one wallet — fully distributed, decentralised and fault-tolerant, interoperable across 40+ Web2 and Web3 providers and every connected world, forever.
Every blockchain, database and identity provider speaks its own language. WEB4 is the universal foundation layer underneath everything else in the OASIS Omniverse — identity, karma, data, NFTs, tokens and providers, all unified under one API, so every layer built on top never has to think about it again.
WEB4 is built on four uncompromising principles. Every avatar, every API call and every byte of data flows through these constraints.
WEB4 is the foundation every other OASIS layer is built on. These are the capabilities that emerge when identity, data and reputation are unified under one API.
The intelligent orchestration and interoperability layer abstracting over all of Web2 and Web3. HyperDrive connects everything to everything — routing, orchestrating and persisting data, applications and infrastructure across any network, provider, chain or technology, online or offline. No single point of failure. Impossible to shut down.
The next-generation, AI-native, decentralised Object-Relational Mapping engine that unifies data, intelligence and interoperability across every layer of the OASIS Omniverse. Map once. Query anywhere. Sync everything.
The power of COSMIC ORM is the same object model everywhere: Save(), Load(), Delete() and versioned audit trails across every provider. If you do not pass a provider, the ONODE uses its default provider from OASISDNA; HyperDrive handles replication, failover and load balancing underneath.
// Create a new object and persist it across the stack
// No provider is specified here, so OASIS uses the ONODE's default provider from OASISDNA.
var newHolon = new Holon();
newHolon.Name = "Test Data";
newHolon.Description = "Test Desc";
newHolon.HolonType = HolonType.Park;
var saveHolonResult = await STAR.OASISAPI.Data.SaveHolonAsync(newHolon, STAR.BeamedInAvatar.Id);
Console.WriteLine($"Saved with ID: {saveHolonResult.Result.Id}");
Console.WriteLine("Load-balanced across every provider.");
// Override the save provider for this one operation only.
// If you omit the provider, OASIS falls back to the ONODE's OASISDNA default provider.
var ethereumSaveResult = STAR.OASISAPI.Data.SaveHolon(
newHolon, STAR.BeamedInAvatar.Id, true, true, 0, true, false, ProviderType.EthereumOASIS);
Console.WriteLine($"Saved to Ethereum only: {ethereumSaveResult.Result.Id}");
Console.WriteLine("All later calls still use the configured default provider.");
// Use the ID returned by the save example above
// If you omit the provider here, OASIS uses the ONODE's default provider from OASISDNA.
var holonId = saveHolonResult.Result.Id;
var loadHolonResult = await STAR.OASISAPI.Data.LoadHolonAsync(
holonId, true, true, 0, true, false, HolonType.All, 0, ProviderType.IPFSOASIS);
Console.WriteLine($"Loaded from IPFS: {loadHolonResult.Result.Id}");
Console.WriteLine("The same object model, wherever it lives.");
// Delete through the API and keep the audit trail
// If you omit the provider here, OASIS uses the ONODE's default provider from OASISDNA.
var holonId = saveHolonResult.Result.Id;
var deleteHolonResult = await STAR.OASISAPI.Data.DeleteHolonAsync(
STAR.BeamedInAvatar.Id, holonId, true, ProviderType.EthereumOASIS);
Console.WriteLine($"Deleted with status: {deleteHolonResult.IsError}");
Console.WriteLine("Delete is audited and rollback-aware.");
// Switch the current provider context, then save using that new default.
await ProviderManager.Instance.SetAndActivateCurrentStorageProviderAsync(ProviderType.MongoDBOASIS, true);
var overrideSaveResult = await STAR.OASISAPI.Data.SaveHolonAsync(newHolon, STAR.BeamedInAvatar.Id);
Console.WriteLine($"Provider overridden, saved with ID: {overrideSaveResult.Result.Id}");
Console.WriteLine("Subsequent calls now use the new default provider.");
COSMIC ORM sits on top of a bespoke multi-parent cached fractal holonic graph chain built specifically for OASIS, with HyperDrive underneath for auto-replication, auto-failover, auto-load balancing and version-controlled auditability.
The OASIS DNA file is the ONODE's living JSON configuration layer. At C:\Source\BACKUP\DEV\OASIS_DNA.json, it defines the default provider behavior, HyperDrive policies, replication lists, failover order and load balancing rules that every Save, Load and Delete inherits when you do not explicitly override a provider.
This is where the ONODE learns how to behave. The list order matters: HyperDrive walks the configured failover providers in sequence, then moves on to the next provider if a call fails, giving you the resilience and automation that make OASIS feel effortless.
WEB4 abstracts away the entire Web2 + Web3 landscape so your app just calls one endpoint — everything else is handled, replicated and kept in sync automatically.
Native integrations with the chains, storage networks and databases your users already live on. This wall follows the same categories as the ProviderType enum, uses real logos where available, and falls back to branded initials where a provider does not have a clean official mark. Switch providers without changing a line of application code.
WEB4 is live today through the OASIS API — and growing into the universal foundation layer for every chain, provider and world.
Universal avatar identity, karma and reputation live today across every connected OASIS world, with real-time sync and automatic provider failover.
LIVENative support for Ethereum, Solana, Polygon, Holochain, IPFS, MongoDB, Neo4j, SOLID and 30+ more — all behind one unified REST API with live Swagger docs.
LIVEAutomatic provider selection, health-checking, replication and failover route every operation across the strongest available path — zero single points of failure.
LIVEA single dashboard view of every wallet, balance and NFT across every connected chain — manageable directly from OPORTAL without leaving the app.
COMING SOONNative biometric and passkey sign-in alongside wallet and social login — all normalised into the same WEB4 avatar identity behind the scenes.
COMING SOONExport your WEB4 karma and reputation score as a portable, verifiable credential that other platforms outside the OASIS Omniverse can read and trust.
COMING SOONA community-driven marketplace where developers can publish and monetise new provider integrations directly into the WEB4 abstraction layer via STARNET.
COMING SOONSocial-recovery and multi-device key recovery flows so losing a device never means losing your avatar, karma history or wallet access.
COMING SOONDeeper AI integration, smarter predictive routing, expanded provider coverage and faster auto-failover detection — the next major version of the orchestration engine powering every WEB4 operation.
COMING SOONA dedicated query language purpose-built for COSMIC ORM — natural-language-to-CQL translation, cross-provider joins in a single query, and a visual query builder for non-developers.
COMING SOONGeneral improvements to the OASIS Architecture and WEB4 API, which may include new APIs and improvements to existing ones — performance tuning, expanded controllers and documentation updates on a continuous, rolling basis.
COMING SOONThe list of native integrations grows continuously — every new chain, database and storage network the ecosystem needs gets added behind the same unchanging API.
COMING SOON