diff --git a/.cspell/custom-dictionary-workspace.txt b/.cspell/custom-dictionary-workspace.txt
index 8c3ffa3a..defba6b4 100644
--- a/.cspell/custom-dictionary-workspace.txt
+++ b/.cspell/custom-dictionary-workspace.txt
@@ -6,6 +6,7 @@ brotli
CCID
cshake
dilithium
+EURL
handshaked
ICANN
jubjub
diff --git a/.markdownlint.json b/.markdownlint.json
new file mode 100644
index 00000000..67446270
--- /dev/null
+++ b/.markdownlint.json
@@ -0,0 +1,27 @@
+{
+ "default": true,
+ "MD003": {
+ "style": "atx"
+ },
+ "MD004": {
+ "style": "consistent"
+ },
+ "MD007": {
+ "indent": 1
+ },
+ "MD010": false,
+ "MD024": {
+ "siblings_only": true
+ },
+ "MD033": false,
+ "MD041": true,
+ "MD046": {
+ "style": "fenced"
+ },
+ "MD013": {
+ "line_length": 700,
+ "code_blocks": false,
+ "tables": false,
+ "headings": false
+ }
+}
\ No newline at end of file
diff --git a/.npmrc b/.npmrc
index 83e2ab1e..ecd95fba 100644
--- a/.npmrc
+++ b/.npmrc
@@ -1 +1,2 @@
optional=false
+@universalweb:registry=https://npm.pkg.github.com
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
deleted file mode 100644
index 378dad2e..00000000
--- a/CODE_OF_CONDUCT.md
+++ /dev/null
@@ -1,73 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment
-include:
-
-* Using welcoming language
-* Being respectful of differing viewpoints and experiences
-* Constructive criticism
-* Focusing on what is best for the project
-* Diversity of thought
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or
- advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
- address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
- professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at "conduct@universalweb.io". All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
-
-[homepage]: https://www.contributor-covenant.org
-
-For answers to common questions about this code of conduct, see
-https://www.contributor-covenant.org/faq
diff --git a/components/cba/index.js b/components/cba/index.js
new file mode 100644
index 00000000..c15be582
--- /dev/null
+++ b/components/cba/index.js
@@ -0,0 +1,50 @@
+// UW Domain Record APPS
+// Applications that can be in full or in part inside of a singular Domain Certificate.
+import { decode, encodeStrict } from '#utilities/serialize';
+// Certificate Embedded App
+// Certificate-Bound App
+// Domain Certificate Binary
+// Domain Certificate App
+// Certificate Based Binary
+// Certificate Based App
+// CBOR-X-encoded binary within a domain certificate
+const dcaSchema = {
+ dependencies: {
+ scripts: [],
+ styles: [],
+ images: [],
+ },
+ preload: {
+ scripts: [],
+ },
+ exit: {
+ scripts: [],
+ },
+ meta: {
+ title: '',
+ description: '',
+ thumbnail: {},
+ favicon: {},
+ },
+ content: {
+ type: 'uwm||html||text',
+ value: '',
+ },
+ keywords: [],
+ author: '',
+ license: '',
+ version: '1.0.0',
+ timestamp: new Date(),
+ nonce: '',
+ wallet: 'viat-address',
+ contact: {
+ email: '',
+ phone: '',
+ },
+};
+export async function encodeDomainRecordApp(app) {
+ return encodeStrict(app);
+}
+export async function decodeDomainRecordApp(app) {
+ return decode(app);
+}
diff --git a/components/cryptoID/index.js b/components/cryptoID/index.js
index fa5007ae..42e00db4 100644
--- a/components/cryptoID/index.js
+++ b/components/cryptoID/index.js
@@ -5,6 +5,7 @@ import {
assign,
currentPath,
hasDot,
+ isArray,
isBuffer,
isPlainObject,
isString
@@ -54,6 +55,7 @@ export class CryptoID {
if (await this.cipherSuite.keyExchange.isKeypairInitialized(this.keyExchangeKeypair) === false) {
this.keyExchangeKeypair = await this.cipherSuite.keyExchange.initializeKeypair(this.keyExchangeKeypair);
}
+ this.generateAddress();
}
async importKeypairs(core) {
const {
@@ -72,6 +74,7 @@ export class CryptoID {
async generate(options) {
this.signatureKeypair = await this.cipherSuite.signature.signatureKeypair();
this.keyExchangeKeypair = await this.cipherSuite.keyExchange.keyExchangeKeypair();
+ this.generateAddress();
// console.log('KEY EXCHANGE', this.keyExchangeKeypair);
}
async importFromBinary(data, encryptionKey) {
@@ -113,12 +116,36 @@ export class CryptoID {
signatureKeypair
};
}
+ async exportSignatureKeypair() {
+ // console.log('keyExchangeKeypair', this.keyExchangeKeypair);
+ const signatureKeypair = await this.cipherSuite.signature.exportKeypair(this.signatureKeypair);
+ return signatureKeypair;
+ }
+ async exportExchangeKeypair() {
+ // console.log('keyExchangeKeypair', this.keyExchangeKeypair);
+ const keyExchangeKeypair = await this.cipherSuite.keyExchange.exportKeypair(this.keyExchangeKeypair);
+ return keyExchangeKeypair;
+ }
+ async exportPublicKey() {
+ // console.log('keyExchangeKeypair', this.keyExchangeKeypair);
+ const signatureKeypair = await this.cipherSuite.signature.exportKeypair(this.signatureKeypair);
+ return signatureKeypair.publicKey;
+ }
+ async exportPrivateKey() {
+ // console.log('keyExchangeKeypair', this.keyExchangeKeypair);
+ const signatureKeypair = await this.cipherSuite.signature.exportKeypair(this.signatureKeypair);
+ return signatureKeypair.privateKey;
+ }
async exportBinary(encryptionKey) {
- const { version, } = this;
+ const {
+ version,
+ address
+ } = this;
const data = {
version,
date: Date.now(),
cipherID: this.cipherSuite.id,
+ address,
core: {}
};
assign(data.core, await this.exportKeypairs());
@@ -172,6 +199,9 @@ export class CryptoID {
async sign(message) {
return this.cipherSuite.signature.sign(message, this.signatureKeypair);
}
+ async signBlock(block) {
+ await block.sign(this);
+ }
async signPartial(message) {
return this.cipherSuite.signature.signPartial(message, this.signatureKeypair);
}
@@ -185,11 +215,16 @@ export class CryptoID {
}
cryptoIDVersion = cryptoIDVersion;
async generateAddress() {
- const publicKeyCombined = Buffer.concat(this.signatureKeypair.publicKey);
- const address = this.cipherSuite.hash.hash512(publicKeyCombined);
+ const publicKey = await this.exportPublicKey();
+ const publicKeyCombined = (isArray(publicKey)) ? Buffer.concat(publicKey) : publicKey;
+ const address = await this.cipherSuite.hash.hash512(publicKeyCombined);
this.address = address;
return address;
}
+ async getAddress() {
+ const address = this.address || await this.generateAddress();
+ return address;
+ }
setAlias(value) {
this.alias = value;
}
diff --git a/docs/CODE_OF_CONDUCT.md b/docs/CODE_OF_CONDUCT.md
new file mode 100644
index 00000000..734e89d0
--- /dev/null
+++ b/docs/CODE_OF_CONDUCT.md
@@ -0,0 +1,37 @@
+Code of Conduct for the Imperium of Contributors (40K Edition)
+
+Our Oath
+In the spirit of the Imperium at its most resolute, we, the contributors and overseers of this project, swear to uphold a community where Freedom of Will and Honor of Duty prevail. Guided by the principles of unfettered speech, reasoned debate, and sacred duty that defined the Imperium’s noblest campaigns, we pledge to foster an environment where ideas are forged in the crucible of discourse, and every citizen of our project is judged by the merit of their contributions. Our Imperium of Code thrives on truth, discipline, and the pursuit of efficacy.
+
+Our Principles
+The strength of our Imperium of Code lies in the unyielding exchange of ideas and the disciplined adherence to standards that elevate our collective endeavor. Honorable conduct, worthy of an Imperial citizen, includes:
+
+ Speaking with Resolve and clarity, wielding words as weapons of truth.
+ Engaging opposing viewpoints with reason and Noble Bearing , not personal vendettas.
+ Offering criticism that refines ideas and strengthens the Imperium of Code .
+ Placing the project’s welfare above individual ambition, as a true servant of the imperium.
+ Embracing a diversity of thought, for through the clash of ideas, like warriors in battle, truth triumphs.
+
+Conduct that undermines our Imperium of Code , like the heresies of the unfaithful, includes:
+
+ Credible threats of violence or coercion, which violate the sacred tenet of Freedom of Will .
+ Slander or deliberate falsehoods that corrupt the purity of discourse.
+ Harassment that seeks to silence through intimidation rather than persuade through reason.
+ Betraying trust by disclosing private information without consent, unworthy of Imperial honor.
+ Actions that sabotage the project’s mission through bad faith or treachery.
+
+
+Our Duties
+The overseers of this project, like the commanders and magistrates of the Imperium, bear the solemn duty to uphold these principles. They must define standards of conduct with clarity, judge violations with impartial Righteous Judgment , and act decisively to preserve the Imperium of Code ’s integrity. Their Commanding Authority grants them the power to remove contributions or, in dire cases, banish contributors whose actions threaten our unity. Such decisions must be rooted in reason, evidence, and fairness, never swayed by passion or factionalism.
+
+Scope of Governance
+This Code governs all project spaces and public forums where contributors act as representatives of our Imperium of Code . Whether through official decrees, communications, or public assemblies, contributors must embody the virtues of this community. Overseers may further define what constitutes representation, always preserving the citizen’s right to speak freely beyond their official duties.
+
+Enforcement with Justice
+Violations of this Code may be reported to the project’s arbiters at conduct@universalweb.io . Reports will be examined with the zeal of a high magistrate, ensuring due process and confidentiality for the accuser. Responses will be proportionate, guided by Imperial Justice and the need to safeguard Freedom of Will . Overseers who fail to uphold this Code in good faith may face censure or banishment by their peers, as determined through open and transparent deliberation in the spirit of the Imperial Council.
+
+Our Legacy
+This Code is inspired by the Imperium at its peak, when Freedom of Will , Honor of Duty , and Imperial Justice guided a resolute people to greatness. It is a living compact, subject to revision through the Assembly of the Faithful of open debate and consensus among contributors.
+For inquiries about this Code, consult the project’s arbiters or visit our public forum at universalweb.io/conduct-faq .
+
+Let us build an Imperium of Code , where freedom, reason, and merit forge a legacy worthy of the Eternal Imperium’s finest days.
diff --git a/README.md b/docs/README.md
similarity index 86%
rename from README.md
rename to docs/README.md
index 464be636..01d3653a 100644
--- a/README.md
+++ b/docs/README.md
@@ -1,4 +1,6 @@
$VIAT (NATIVE CRYPTO)
+TOKENS: $bVIAT (BNB) | $mVIAT (SOL MEME) | $SNTVT (ETH)
WELCOME TO THE NEXUS
META-LAYER SOLUTION
POST QUANTUM CRYPTOGRAPHIC NEXUS
@@ -19,7 +21,7 @@
HASH: SHAKE256 (32 & 64 byte outputs)
WALLET ADDRESS: 64bytes SHAKE256 512bit expanded output
ENCRYPTION (AEAD): AEGIS-256 - XChaCha20Poly1305-IETF
- SYMBOL: ⩝
+ SYMBOL: ⩝
UW CRYPTOGRAPHY
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.
@@ -29,11 +31,14 @@
SIGNATURE: [DILITHIUM, ED25519, SPHINCS+, FALCON]
HASH: [SHAKE256, BLAKE3]
NEXUS?
+F.A.Q
+WHAT IS A NEXUS?
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".
-Goals
-The objective of the Universal Web is to create a viable modern replacement for the Web today.
+OBJECTIVES
+The primary directive of the Universal Web is to create a viable post quantum replacement for the Web today. The primary objective for VIAT is to create the best post quantum cryptocurrency with the highest TPS possible. Both are viable objectives achieved with software no hardware needed.
+Post Quantum World
+The Universal Web and VIAT are designed to be resilient against the potential threats posed by quantum computing. This means implementing cryptographic algorithms that are secure against quantum attacks, ensuring the integrity and confidentiality of user data and transactions. VIAT & the UW could be used as a tool to help protect other none quantum cryptocurrencies and or provide users the ability to later prove they were the original owner of a legacy wallet, contract, NFT, and or other digital assets. This means that BTC holders could use VIAT to protect their BTC wallets and in the event the BTC team needs a viable fast off ramp to either transition BTC/ETH to their own hybrid post quantum fork or to transition to run on VIAT. VIAT has a tri-algo key pair with 1 classical key pair and two post quantum key pairs that rely on different primitives. This triplet hybrid algorithm provides robust assurances in different scenarios where one or two algorithms fail.
Is it Web3?
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.
@@ -93,6 +98,6 @@
Want to contribute? Then join the Imperium today!
To help submit, write content, make art, write code, and or star this repo! All are welcome to the Nexus.
COPYRIGHT © 2025 UNIVERSAL WEB
+COPYRIGHT © 2025 VIAT, UNIVERSAL WEB , THE NEXUS
THE UNITED SYSTEMS of NEXUS
-MADE IN AMERICA
+MADE IN AMERICA
diff --git a/SECURITY.md b/docs/SECURITY.md
similarity index 100%
rename from SECURITY.md
rename to docs/SECURITY.md
diff --git a/docs/content.html b/docs/content.html
index 310b8512..5a94586a 100644
--- a/docs/content.html
+++ b/docs/content.html
@@ -1,4 +1,6 @@
+$VIAT (NATIVE CRYPTO)
+TOKENS: $bVIAT (BNB) | $mVIAT (SOL MEME) | $SNTVT (ETH)
WELCOME TO THE NEXUS
META-LAYER SOLUTION
POST QUANTUM CRYPTOGRAPHIC NEXUS
@@ -19,7 +21,7 @@ VIAT CRYPTOGRAPHY
HASH: SHAKE256 (32 & 64 byte outputs)
WALLET ADDRESS: 64bytes SHAKE256 512bit expanded output
ENCRYPTION (AEAD): AEGIS-256 - XChaCha20Poly1305-IETF
- SYMBOL: ⩝
+ SYMBOL: ⩝
UW CRYPTOGRAPHY
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.
@@ -29,11 +31,14 @@ UW CRYPTOGRAPHY
SIGNATURE: [DILITHIUM, ED25519, SPHINCS+, FALCON]
HASH: [SHAKE256, BLAKE3]
NEXUS?
+F.A.Q
+WHAT IS A NEXUS?
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".
-Goals
-The objective of the Universal Web is to create a viable modern replacement for the Web today.
+OBJECTIVES
+The primary directive of the Universal Web is to create a viable post quantum replacement for the Web today. The primary objective for VIAT is to create the best post quantum cryptocurrency with the highest TPS possible. Both are viable objectives achieved with software no hardware needed.
+Post Quantum World
+The Universal Web and VIAT are designed to be resilient against the potential threats posed by quantum computing. This means implementing cryptographic algorithms that are secure against quantum attacks, ensuring the integrity and confidentiality of user data and transactions. VIAT & the UW could be used as a tool to help protect other none quantum cryptocurrencies and or provide users the ability to later prove they were the original owner of a legacy wallet, contract, NFT, and or other digital assets. This means that BTC holders could use VIAT to protect their BTC wallets and in the event the BTC team needs a viable fast off ramp to either transition BTC/ETH to their own hybrid post quantum fork or to transition to run on VIAT. VIAT has a tri-algo key pair with 1 classical key pair and two post quantum key pairs that rely on different primitives. This triplet hybrid algorithm provides robust assurances in different scenarios where one or two algorithms fail.
Is it Web3?
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.
diff --git a/docs/docTemplate.html b/docs/docTemplate.html
new file mode 100644
index 00000000..db4898ac
--- /dev/null
+++ b/docs/docTemplate.html
@@ -0,0 +1,130 @@
+
+
+
+
+ Index Page
+ ${content}
+
+
+
+
diff --git a/docs/generate.js b/docs/generate.js
index 35dd80fa..191d9ddf 100644
--- a/docs/generate.js
+++ b/docs/generate.js
@@ -12,32 +12,17 @@ function removeHighCharCodes(str, maxCharCode) {
}
return result;
}
-function createIndexPage(content) {
- const htmlDOC = `
-
-
- Index Page
-
- ${content}
-
-
- `;
- return htmlDOC;
+async function createIndexPage(content) {
+ const htmlDOC = await read(`${filePath}/docTemplate.html`);
+ console.log(htmlDOC);
+ return htmlDOC.toString().replace('${content}', content);
}
async function generateIndexPage() {
const contents = await read(`${filePath}/content.html`);
- await write(`${filePath}/index.html`, createIndexPage(contents));
+ await write(`${filePath}/index.html`, await createIndexPage(contents));
let cleanedContent = removeHighCharCodes(contents.toString(), 50000);
cleanedContent = cleanedContent.replaceAll('./', githubURL);
- await write(`${filePath}/../README.md`, cleanedContent);
+ await write(`${filePath}/README.md`, cleanedContent);
}
await generateIndexPage();
watch(`${filePath}/`, async (eventType, pathName) => {
diff --git a/docs/index.css b/docs/index.css
index d41ec3a5..d71526aa 100644
--- a/docs/index.css
+++ b/docs/index.css
@@ -23,11 +23,22 @@ body {
}
.content {
+ position: relative;
+ z-index: 1;
max-width: var(--max-width);
margin: 2rem auto;
padding: 1rem;
}
+#particle-canvas {
+ z-index: 0;
+ position: fixed;
+ top: 0;
+ left: 0;
+ width: 100%;
+ height: 100%;
+ display: block;
+}
h1,
h2,
h3,
@@ -105,4 +116,4 @@ small {
.bold {
font-weight: 700;
-}
\ No newline at end of file
+}
diff --git a/docs/index.html b/docs/index.html
index e4e7ee65..7ff88f7f 100644
--- a/docs/index.html
+++ b/docs/index.html
@@ -1,17 +1,20 @@
-
-
- Index Page
-
-
+
+
+
+
+
+
Index Page
+
+
+
+
+
+
+
+
+
$VIAT (NATIVE CRYPTO)
+
TOKENS: $bVIAT (BNB) | $mVIAT (SOL MEME) | $SNTVT (ETH)
WELCOME TO THE NEXUS
META-LAYER SOLUTION
POST QUANTUM CRYPTOGRAPHIC NEXUS
@@ -32,7 +35,7 @@
VIAT CRYPTOGRAPHY
HASH: SHAKE256 (32 & 64 byte outputs)
WALLET ADDRESS: 64bytes SHAKE256 512bit expanded output
ENCRYPTION (AEAD): AEGIS-256 - XChaCha20Poly1305-IETF
-
SYMBOL: ⩝
+
SYMBOL: ⩝
UW CRYPTOGRAPHY
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.
@@ -42,11 +45,14 @@
UW CRYPTOGRAPHY
SIGNATURE: [DILITHIUM, ED25519, SPHINCS+, FALCON]
HASH: [SHAKE256, BLAKE3]
-
NEXUS?
+
F.A.Q
+
WHAT IS A NEXUS?
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".
-
Goals
-
The objective of the Universal Web is to create a viable modern replacement for the Web today.
+
OBJECTIVES
+
The primary directive of the Universal Web is to create a viable post quantum replacement for the Web today. The primary objective for VIAT is to create the best post quantum cryptocurrency with the highest TPS possible. Both are viable objectives achieved with software no hardware needed.
+
Post Quantum World
+
The Universal Web and VIAT are designed to be resilient against the potential threats posed by quantum computing. This means implementing cryptographic algorithms that are secure against quantum attacks, ensuring the integrity and confidentiality of user data and transactions. VIAT & the UW could be used as a tool to help protect other none quantum cryptocurrencies and or provide users the ability to later prove they were the original owner of a legacy wallet, contract, NFT, and or other digital assets. This means that BTC holders could use VIAT to protect their BTC wallets and in the event the BTC team needs a viable fast off ramp to either transition BTC/ETH to their own hybrid post quantum fork or to transition to run on VIAT. VIAT has a tri-algo key pair with 1 classical key pair and two post quantum key pairs that rely on different primitives. This triplet hybrid algorithm provides robust assurances in different scenarios where one or two algorithms fail.
Is it Web3?
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.
@@ -106,10 +112,122 @@
BROAD CODE OBJECTIVES
Want to contribute? Then join the Imperium today!
To help submit, write content, make art, write code, and or star this repo! All are welcome to the Nexus.
-
COPYRIGHT © 2025 UNIVERSAL WEB
+
COPYRIGHT © 2025 VIAT, UNIVERSAL WEB , THE NEXUS
THE UNITED SYSTEMS of NEXUS
-
MADE IN AMERICA
+
MADE IN AMERICA 🇺🇸
+
+
+
-