WEB4 · THE FOUNDATION LAYER

OASIS WEB4

ONE AVATAR. ONE KARMA. EVERY WORLD.

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.

EXPLORE WEB4 → SWAGGER DOCS → ORIGINAL WEB4 SITE →
UNIFIED WEB4 OASIS API ETHEREUM CHAIN SOLANA CHAIN IPFS STORAGE MONGODB DATA SQLITE DATA HOLOCHAIN P2P POLYGON CHAIN NEO4J GRAPH SOLID POD AWS CLOUD KARMA REPUTATION NFTs / GeoNFTs TOKENS UTILITY WALLET UNIVERSAL AVATAR FOUNDATION SOCIAL APIS
THE CONCEPT

WHAT IS WEB4?

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.

WEB6 / WEB7 / WEB8+  —  AI, symbiosis, galactic network and beyond
ABOVE
WEB5 / STAR ODK  —  holons, OAPPs, the decentralised app store
WEB5+
↓ EVERYTHING ABOVE BUILDS ON THIS
WEB4 · FOUNDATION LAYER  —  identity, karma, data, NFTs, tokens & providers
THIS LAYER
↓ WEB4 UNIFIES EVERYTHING BELOW
WEB3 / WEB2 / WEB1  —  blockchains, cloud APIs, the open internet
BELOW
FOUNDING PRINCIPLES

UNIFIED BY DESIGN

WEB4 is built on four uncompromising principles. Every avatar, every API call and every byte of data flows through these constraints.

👤
UNIVERSAL
One avatar identity, recognised instantly across every connected world. No account juggling, no fresh starts, no fragmented reputation.
🔑
SOVEREIGN
You hold your own keys. Private keys stay local and auto-sync across your own devices — never custodied, never locked into a single provider.
🔗
INTEROPERABLE
40+ Web2 and Web3 providers behind one unified API. Switch chains, databases or storage networks without rewriting a single line of application code.
♾️
PERSISTENT
Karma, reputation and history are never lost. Auto-replicated across every available provider with automatic failover if any one of them goes down.
CAPABILITIES

THE FOUNDATION LAYER IN ACTION

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.

👤
AVATAR SSO
One OASIS avatar identity across every integrated world. Name, reputation, karma, level history, achievements and NFT cosmetics all follow you — one login, infinite worlds.
🧘
KARMA & REPUTATION ENGINE
Real-world and in-game positive actions earn karma that flows through every connected world, raising stats, unlocking superpowers and building a portable, provider-agnostic reputation.
💰
UNIVERSAL WALLET
Private keys stay local and auto-backup across your own devices. Public keys and wallets auto-replicate across providers — a decentralised, aggregated wallet for every connected chain.
🖼️
CROSS-CHAIN NFTs
Mint once, recognise everywhere. NFTs minted through WEB4 are queryable and tradeable across every connected chain and marketplace, without bridging or wrapping.
📍
GEONFTS & LOCATION DATA
Real-world GPS coordinates anchored directly to on-chain NFTs and GeoHotSpots. Mint, discover and trade digital assets tied to physical locations — the backbone of every location-based OASIS world.
🗺️
QUEST & SOCIAL SYSTEMS
Quests, clans, messaging and social graphs all live in the same identity layer as your avatar — so progress, friends and reputation travel with you instead of resetting per world.
🔐
PROVIDER-AGNOSTIC AUTH
Sign in with wallets, social logins, biometrics or classic email — WEB4 normalises every auth method into one identity, so apps never need to care which one a user chose.
📡
REAL-TIME DATA SYNC
Changes to avatar, karma or inventory propagate to every connected world and provider in real time — no polling, no stale state, no manual reconciliation.
📖
FULLY DOCUMENTED API
A complete REST API with live Swagger sandbox endpoints. Query any data, manage any asset, control any identity — through one unified interface instead of dozens of incompatible ones.
THE ORCHESTRATION ENGINE

OASIS HYPERDRIVE

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.

HYPERDRIVE CLOUD AWS · AZURE · GCP DATABASES MONGO · SQL BLOCKCHAINS ETH · SOL · POLY IPFS FILECOIN LOCAL SQLITE P2P / DLT HOLOCHAIN EDGE NODES LOW LATENCY APIS MICROSERVICES IOT DEVICES AI/ML SYSTEMS
Works online or offline
Impossible to shut down
No single point of failure
Self-healing & auto-recover
Provider, chain & network agnostic
Future-proof infrastructure
🧭
INTELLIGENT ROUTING
Automatically finds the best path for performance, cost and reliability across every connected provider.
🛡️
AUTO FAILOVER
If a node, network or provider fails, HyperDrive instantly reroutes — no downtime, no manual intervention.
⚖️
AUTO LOAD BALANCING
Distributes workloads across the optimal nodes for maximum efficiency, automatically and continuously.
💾
PERSISTENT BY DESIGN
Data is safely stored across multiple destinations simultaneously — never resting on a single provider.
🔄
REAL-TIME SYNC
Everything stays in sync across all devices, nodes and environments, online or off.
🧠
AI-DRIVEN OPTIMIZATION
Continuously learns and adapts to changing conditions — latency, cost, reliability — for the best possible performance.
ROUTING SWITCHBOARD
HYPERDRIVE CLOUD / DB CHAIN / IPFS API / EDGE IOT / AI
CONNECTS TO EVERYTHING: cloud providers, databases, APIs & microservices, blockchains & layer 1/2s, IPFS & decentralised storage, edge networks, devices & IoT, traditional web apps, AI & ML systems, identity systems, payment & commerce, game servers & worlds — and more.
INTELLIGENT. ADAPTIVE. AUTONOMOUS. — ONE LAYER. ALL INFRASTRUCTURE. NO LIMITS. NO DOWNTIME.
THE UNIVERSAL DATA LAYER

OASIS COSMIC ORM

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.

COSMIC ORM RELATIONAL SQL GRAPH RELATIONS DOCUMENT NOSQL VECTOR AI / ML TIME-SERIES EVENTS DAPPS OAPPS AI AGENTS AUTONOMOUS SMART CONTRACTS ON-CHAIN IOT DEVICES EXTERNAL APIS
🧱
UNIVERSAL DATA ABSTRACTION
Maps any data structure, object, relationship or state across any system, app or chain — one standard object model for everything.
🧠
AI-NATIVE INTELLIGENCE
Understands context, relationships and intent to optimize queries, generate schemas and detect anomalies automatically.
🌐
CROSS-WORLD INTEROPERABILITY
One data layer that connects every world, app, chain, device and identity in the OASIS Omniverse.
🔒
DECENTRALISED BY DESIGN
No central server, no single point of failure. Built on HyperDrive with auto-replication, auto-failover and auto-load balancing from the ground up.
♾️
INFINITE SCALE & FLEXIBILITY
From tiny objects to cosmic datasets — from local apps to planetary scale — without re-architecting a thing.
🔗
SMART RELATIONSHIPS
Auto-joins, intelligent relationship mapping and natural-language-to-structured-query translation, all built in.
RELATIONAL DOCUMENT GRAPH KEY-VALUE TIME-SERIES VECTOR / AI BINARY / FILES STREAMING

REAL CODE EXAMPLES

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.

C#Save a Holon
// 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.");
C#Save to a 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.");
C#Load from a 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.");
C#Delete a Holon
// 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.");
C#Override the Provider
// 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.");
HOLON LIFECYCLE
SAVE() ONE OBJECT MODEL LOAD() FROM ANY PROVIDER DELETE() AUDITED & ROLLBACK-READY AUDIT VERSION CONTROLLED HOLON

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.

ONE DATA LAYER. INFINITE WORLDS. LIMITLESS POSSIBILITIES.
THE CONFIG BRAIN

OASISDNA

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.

WHAT IT CONTAINS

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.

Storage Providers

  • AutoFailOverEnabled - turn failover on or off
  • AutoReplicationEnabled - mirror data across providers
  • AutoLoadBalanceEnabled - spread reads and writes
  • AutoFailOverProviders - ordered failover path
  • AutoReplicationProviders - providers that stay in sync
  • AutoLoadBalanceProviders - providers used for balancing

HyperDrive

  • IsEnabled - global HyperDrive switch
  • DefaultStrategy - strategy mode for routing
  • MaxRetryAttempts / RequestTimeoutMs
  • HealthCheckIntervalMs and live provider checks
  • EnabledProviders - providers allowed into the mesh
  • LoadBalancingProviders - providers participating in balancing

Provider Configs

  • ProviderConfigs - per-provider settings and thresholds
  • ProviderCosts - cost and preference signals
  • ProviderPermissions - access and routing rules
  • OASISProviderPrivateKeys - provider key material
  • OASISProviderBootType - warm or cold boot behavior
If you do not specify a provider, OASIS uses the configured ONODE default from OASISDNA. If that provider fails, HyperDrive follows the failover list in order and keeps the operation moving.
UNDER THE HOOD

40+ PROVIDERS. ONE API.

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 PROVIDER INTEGRATIONS

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.

THE ROAD AHEAD

BUILDING THE FOUNDATION

WEB4 is live today through the OASIS API — and growing into the universal foundation layer for every chain, provider and world.

SHIPPING NOW
Avatar SSO & Karma Engine

Universal avatar identity, karma and reputation live today across every connected OASIS world, with real-time sync and automatic provider failover.

LIVE
SHIPPING NOW
40+ Provider Integrations

Native support for Ethereum, Solana, Polygon, Holochain, IPFS, MongoDB, Neo4j, SOLID and 30+ more — all behind one unified REST API with live Swagger docs.

LIVE
SHIPPING NOW
HyperDrive Auto-Failover

Automatic provider selection, health-checking, replication and failover route every operation across the strongest available path — zero single points of failure.

LIVE
NEXT
Universal Wallet Aggregation UI

A single dashboard view of every wallet, balance and NFT across every connected chain — manageable directly from OPORTAL without leaving the app.

COMING SOON
NEXT
Biometric & Passkey Auth

Native biometric and passkey sign-in alongside wallet and social login — all normalised into the same WEB4 avatar identity behind the scenes.

COMING SOON
NEXT
Cross-Chain Reputation Export

Export your WEB4 karma and reputation score as a portable, verifiable credential that other platforms outside the OASIS Omniverse can read and trust.

COMING SOON
ON THE HORIZON
Provider Marketplace

A community-driven marketplace where developers can publish and monetise new provider integrations directly into the WEB4 abstraction layer via STARNET.

COMING SOON
ON THE HORIZON
Decentralised Identity Recovery

Social-recovery and multi-device key recovery flows so losing a device never means losing your avatar, karma history or wallet access.

COMING SOON
ON THE HORIZON
HyperDrive v3

Deeper 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 SOON
ON THE HORIZON
COSMIC Query Language (CQL)

A 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 SOON
ON THE HORIZON
Architecture & API Enhancements

General 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 SOON
ALWAYS EVOLVING
More Providers to Come

The 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