META-LAYER SOLUTION
LAYER SUBZERO | LAYER -1 | SUB-LAYER 0
UW/VIAT is a post quantum Meta-Layer solution that embraces a hybrid network architecture with post-quantum cryptography and designed for a multi-planetary future. It serves as the foundation for a next-generation Web (UW), Domain System (DIS), native cryptocurrency (VIAT), and cryptographic governance.
Unlike traditional Layer "0" solutions, which focus solely on blockchain interoperability and scalability, UW/VIAT encompasses a wide array of capabilities and technologies with implications beyond the blockchain space. UW/VIAT is a nexus of infrastructure for next-gen communications, applications, secure voting, digital ownership, real-time transactions, DeFi, IoT, cryptocurrency, governance, cryptographic identification, universal login, government intranets, smart contracts, domain name/information system, domain certificates, modern UTF-8 URLs, and beyond. UW/VIAT strives for balance; it contains both centralized and decentralized components that are natively integrated into a united system.
VIAT uses hybrid post quantum cryptography which combines classical and post quantum cryptography into a singular algorithm. There are two hybrid post quantum algorithms one is for Signatures and the other is for Key Exchanges. All primary VIAT cryptography used is listed below more are available for the UW.
SIGNATURE: DILITHIUM ◉ ED25519 ◉ SPHINCS+
KEY EXCHANGE: KYBER ◉ x25519
HASH: SHAKE256 (32 & 64 byte outputs)
WALLET ADDRESS: 64bytes SHAKE256 512bit expanded output
ENCRYPTION (AEAD): AEGIS-256 - XChaCha20Poly1305-IETF
SYMBOL: ⩝
These are all the cryptographic algorithms supported or play a role in the UW/VIAT. Hybrid post quantum algorithms are available for Key Exchanges and Signatures.
KEY EXCHANGE: [KYBER, x25519]
ENCRYPTION (AEAD): [AEGIS-256, XChaCha20Poly1305-IETF]
SIGNATURE: [DILITHIUM, ED25519, SPHINCS+, FALCON]
HASH: [SHAKE256, BLAKE3]
We call the UW/VIAT a nexus which is: a unified ecosystem where both Web-like, cryptocurrency, and governing elements are deeply interconnected yet functionally independent. Our version of the World Wide Web is the Universal Web and our cryptocurrency is VIAT; together they form what we call a nexus.
The Nexus has its own Domain System, Messaging System, Real-time events, design, data transport network protocol, language, browser, cryptocurrency, and many other unique components. It's a cohesive system rather than a bunch of independent technologies retrofitted to work with each other or layering one thing on top of the next similar to the Web today or what most call "Web3".
The objective of the Universal Web is to create a viable modern replacement for the Web today.
Depends on your definition.
If Web3 means ALL websites/apps are on a network like IPFS, users/services must use a smart contract to interact with sites, paying a TX fee just to post a social media update, using decentralized DNS with limited abilities (ex: ETH domains), then we have a very different definition. That version of the Web would be a major downgrade that removes key beneficial aspects of the Web while also not addressing any of the real issues. Any Web replacement must not introduce delays for any actions when a client is interacting with a server. If a user must use a smart contract to post on a site or make profile edits it adds significant delays and costs to otherwise trivial actions. If an action must first go through mining, verification, and propagation it's inherently slower than a modern cost free client-server API request. Regardless of optimization generally the typical client-server API request will require less time, data, and processing. Thinking about this logically we know the shortest distance is between two points therefore adding more points will always be slower. What this means is that we need to improve and include the World Wide Web's client-server model in the solution not disregard it.
Our standard for what we consider Web3 includes 2 major networks that are natively integrated: the first is a Web and a cryptocurrency with a new UDP based network protocol (UW://), a new domain name system (DIS). The Web part must include: a new next gen encrypted by default UDP based network protocol (UW://), native UTF-8 URLs with native emoji support, a new cryptographic certificate focused Domain name system (DIS), new types of domains, feature packed Domain Certificates, hybrid post quantum cryptography, and a historical public ledger of domain certificates.
The Universal Web's name was chosen because of its natural evolution of the name "The World Wide Web" and highlights the intent to build a Multi-planetary Web.
The Web is all the software bits that sits on-top of the Internet. The Universal Web at least for now is only concerned with software; no special hardware required. Users just need software to access the Universal Web and Servers just need software to setup a Universal Web server; the same goes for VIAT.
The World Wide Web has the Domain Name System, Web3 has Decentralized DNS, & the Universal Web has a similar component called the DIS(Domain Information System). Here's the critical difference DNS takes a hostname and spits out a DNS record (has things like an IP address) the DIS returns a cryptographic signed certificate. The returned certificate can have records akin to DNS records in it but is part of a cryptographically protected and verifiable certificate. The DIS plays a similar role to DNS but the DIS has greater functionality, has similar syntax, distributes only cryptographic certificates, and was designed with all other components in mind. Because the DIS provides a certificate instead of just a basic DNS record it makes connection establishment faster and more secure, specifically speeding up the connection synchronization (Handshake/Connection Establishment) process. When browsing the UW all domain lookups would go to the remote and or local DIS (cached). The entire DIS is a publicly verifiable blockchain but old certificates can be replaced which means Domain record changes are quick and easy with a 0TTL. The DIS doesn't share any domains or rules with the Web's Domain system meaning domain names don't carry over. The UW also permits emoji domains as well as single name domains. Reserved named domains are domains consisting of just a name to quickly access the site for example you just type "x" to go to "x.com".
Re-imagining the Web from the ground up may seem like a radical proposition, but it is entirely logical, rational, within our ability, & necessary. At its core, the Web is a collection of software solutions. Therefore, creating a system that can replace yet go beyond the Web doesn’t require reinventing the physical infrastructure; it simply demands innovative software designed to leverage current innovations while addressing the limitations of the old.
If we critically evaluate the challenges facing the current Web, from inefficiencies & vulnerabilities to its inability to fully embrace emerging technologies, it becomes self-evident that incremental updates aren't going to address fundamental design flaws. A foundational overhaul is not only viable but also more efficient and cost-effective. By building on 30 years of lessons, we can envision something that goes beyond what we call a Web, which integrates cutting-edge technologies and anticipates future advancements. This isn’t just an opportunity; it’s an imperative to build the future.
- UDSP MODULE (CONTAINS SERVER & CLIENT MODULE)
- SERVER MODULE (CHECK THE UDSP FOLDER & IMPORTS FOR FULL CODE)
- CLIENT MODULE (CHECK THE UDSP FOLDER & IMPORTS FOR FULL CODE)
- BROWSER (outdated)
- EXAMPLE APP (pnpm run server)
- BUILD DOMAIN & IDENTITY CERTIFICATES THAT ARE ALSO VIAT WALLETS (pnpm run certificates)
- SIMULATE CLIENT REQUEST (pnpm run simc) (ONLY RUN WHEN DEMO IN A STABLE COMMIT NOT LATEST UNLESS SPECIFIED)
- VARIOUS HELPER SCRIPTS
- PNPM start script builds/starts the Universal Web Browser
- Components must also be compiled for the front-end library
- Root is used to generate root certificates only
- Includes Identity Certificate generation examples
- EXAMPLE APPS
- UDSP
- UW URI (HIGHER ABSTRACTION PROTOCOL OVER UDSP)
- VARIOUS HELPER SCRIPTS
- PNPM is preferred for package management
Install NodeJS and PNPM
- UW UDP BASED NETWORK PROTOCOL
- SERVER MODULE
- CLIENT MODULE
- DIS (DOMAIN SYSTEM - NOT DNS)
- UW APPS
- Multi-OS Support
- Multi-Device Support
- UW BROWSER
- VIAT - NATIVE CRYPTOCURRENCY
- DECENTRALIZED GOVERNANCE
To help submit, write content, make art, write code, and or star this repo! All are welcome to the Nexus.
COPYRIGHT © 2025 UNIVERSAL WEB THE UNITED SYSTEMS of NEXUS MADE IN AMERICA
