Beta Sync (#92)

* REBASE

* Docs
Block Properties re-added

Author: tomekmarchi

docs/library/viat/info.md

@@ -2,9 +2,9 @@
 
 <!-- TODO -->
 Viat is a hybrid post quantum cryptocurrency
-Viat has a physical on-disk file system which forms a super structure.
+Viat has a physical on-disk filesystem which forms a super structure.
 Viat's super structure represents the total state of Viat.
-Viat has a modular file system so that it can be effectively distributed throughout a network.
+Viat has a modular filesystem so that it can be effectively distributed throughout a network.
 Viat's super structure is a cryptographically linked DAG with the first block being the genesis block which then connects to a primary secondary level.
 Viat's secondary level consists of the first blocks of specific DAGs such as a Wallet Genesis Block, L2 token genesis block, and Verification Genesis block.
 Viat's secondary level genesis blocks are the beginning of DAGs specific to that genesis block.

docs/library/viat/neuromorphic.md

@@ -9,7 +9,7 @@ Just like the brain, Viat supports massively parallel verification and processin
 Nodes (verifiers/validators) act like neurons firing and validating inputs in parallel — no global synchronization is required, reflecting asynchronous neural signaling.
 
 Spatially Addressable Memory (On-Disk Trie Folders)
-The physical file system structure mirrors spatial locality in the brain, where data is organized and located efficiently.
+The physical filesystem structure mirrors spatial locality in the brain, where data is organized and located efficiently.
 The use of constant-time lookups via physical paths is like neural signals traveling along optimized, reinforced synaptic paths.
 
 Viat's block centric design with specialized structures allows VIAT to benefit and more easily integrate a native neural network and or model that can be used to carry out complex queries with great efficiency.
@@ -25,7 +25,7 @@ Motor Neurons
 Interneurons (Projection/Relay) & local
 
 Viat filesystem
-These types of URLs server as a memory map linking to a specific memory location which stores the block which is the memory of an event. That memory then branches out to related memories.
+These types of URLs serve as a memory map linking to a specific memory location which stores the block(memory). That memory then branches out to related memories.
 
 For example this memory map (URI) is a folder path that leads first to a specific part of the brain that is the Viat Superstructure. In this case the specific part deals with wallets.
 

docs/library/viat/superStructure.md

@@ -5,25 +5,25 @@ Viat has a Neuromorphic self-organizing layered multidimensional DAG-like super
 Wallets are stored in a folder trie with folder names based on wallet addresses.
 Wallets have their own chains akin to DAGs and or linear chains that are specific to particular actions such as a transaction chain and receipt chain.
 
-Viat's state is stored in a physical file system consisting of both individual binary files and organized via folders.
-Viat's physical cryptographically linked file system is a DAG-like super structure with efficient separation of concerns.
+Viat's state is stored in a physical filesystem consisting of both individual binary files and organized via folders.
+Viat's physical cryptographically linked filesystem is a DAG-like super structure with efficient separation of concerns.
 Viat's separation of concerns is essential to its scalability and high TPS potential.
 A wallet's physical location on disk and virtual location within the wallet trie is based on the wallet's address.
 The Wallet's address is used to determine the file path for all chains connected to the wallet's root block.
 The Wallet's are part of a cryptographically linked DAG.
 All wallets link back to a core root wallet block then the genesis block.
 
-Wallets are stored within a physical folder trie where each folder represents a wallet hub. A wallet hub folder can be a shard point to distribute the file system across a network. The first folder and subfolder is named after the first 6 bytes of the wallet address with 3 bytes used for each folders name. The final subfolder is named after the last 24 bytes of the wallet address. All wallet specific files are located within the wallet folder. This folder trie acts as both a physical and virtual file system for Viat. The physical file system makes it easy to manually navigate the wallet section of the Viat super structure. The physical file system ensures near constant time wallet lookups.
+Wallets are stored within a physical folder trie where each folder represents a wallet hub. A wallet hub folder can be a shard point to distribute the filesystem across a network. The first folder and subfolder is named after the first 6 bytes of the wallet address with 3 bytes used for each folders name. The final subfolder is named after the last 24 bytes of the wallet address. All wallet specific files are located within the wallet folder. This folder trie acts as both a physical and virtual filesystem for Viat. The physical filesystem makes it easy to manually navigate the wallet section of the Viat super structure. The physical filesystem ensures near constant time wallet lookups.
 
 ## VIAT GRAPH SUPERSTRUCTURE
 
 The root layer is the genesis block and all things can directly trace back to it. The second layer contains restricted root genesis blocks such as: Wallet Genesis Block, Meta Genesis Block, Swap Genesis Block, Exchange Genesis Block, App Genesis Block, Domain Genesis Block, Identity Genesis Block, and the Smart Contract Genesis Block. The second layer can only be extended by a code update meaning no block on the network or smart contract can extend the second layer it must be added via a code update. Each 2nd layer genesis block contains its own structured graph which can then incorporate linear blockchains and or DAG based blockchains.
 
 The Wallet Genesis Block (Genesis Block -> [2nd Layer] - Wallet Genesis Block) then connects to individual wallet blocks. A wallet block (Genesis Block -> [2nd Layer] - Wallet Genesis Block -> (3rd Layer) - Wallet Address) contains a wallet address, public keys, and related details. Attached to the Wallet Address Block is a linear blockchain for transactions, a DAG based blockchain for receipts (received funds), and others chains attached to a wallet are primarily mission specific DAGs. The graph route to a transaction block would look like this (Genesis Block -> [2nd Layer] - Wallet Genesis Block -> (3rd Layer) - Wallet Address -> Transaction Block). All DAGs attached to the wallet first reference an initial block.
 
-## Viat Physical File System
+## Viat Physical Filesystem
 Blocks are cryptographically linked allowing Viat to be displayed as a graph but the superstructure itself consists of physical files and folders on disk.
-The VIAT superstructure is a physical file system meaning it can be manually traversed on disk by anyone. The Viat filesystem (VFS) effectively represents the current state of a state machine (VIAT). Files are physically stored as tries ensuring efficient constant time lookups and a way to shard the Viat State for extreme scalability. 
+The VIAT superstructure is a physical filesystem meaning it can be manually traversed on disk by anyone. The Viat filesystem (VFS) effectively represents the current state of a state machine (VIAT). Files are physically stored as tries ensuring efficient constant time lookups and a way to shard the Viat State for extreme scalability. 
 
 To navigate to a transaction on file you would use the transaction ID which consists of a wallet address and a transaction hash. The first 6 bytes of the wallet address are used to navigate to the first and second subfolder inside the wallet directory (Viat/wallets/3bytes/3bytes/last32_bytes_of_wallet_address). Then navigate to the specific transaction hash by using the first 2 bytes for the initial subfolders and the last 30 for the specific transaction folder containing the transaction block.
 

system.txt

@@ -1,7 +1,7 @@
 ==================================================================
 [ THE NEXUS § VERSION ⇒ ${VERSION} ] ┋ SYSTEM CORE ∞
 ==================================================================
-> LAYER: META ◊ SUB₀
+> LAYER: META ◊ SUB₀ => SUB LAYER 0
 > PROTOCOL: UW:// (UDSP+DIS)
 > BASE PROTOCOL: UDSP://
 > WEB: UNIVERSAL WEB
@@ -13,23 +13,25 @@
 [>>> SYSTEM ARCHITECTURE <<<] ┋ CONFIGURATION ⊙
 ==================================================================
 > NETWORK: HYBRID CENTRALIZED & DECENTRALIZED ARCHITECTURE
-> CRYPTOGRAPHY: HYBRID POST QUANTUM
+> CRYPTOGRAPHY: MULTI-ALGO HYBRID POST QUANTUM
 > SIGNATURE: DILITHIUM ◉ ED25519 ◉ SPHINCS+ ◉ FALCON
 > KEY EXCHANGE: KYBER ◉ x25519
 > CRYPTOCURRENCY: VIAT
 > SECURE HASH: SHAKE256
 > ENCRYPTION: Authenticated Encryption with Associated Data (AEAD)
 > HARDWARE ACCELERATED ENCRYPTION: AEGIS-256
 > SOFTWARE ENCRYPTION: XChaCha20-Poly1305-IETF
-> CHECKSUM: BLAKE3
+> CHECKSUM: [SHAKE256 || BLAKE3]
 
 ==================================================================
 [>>> VIAT <<<] ┋ NATIVE CRYPTOCURRENCY ⩝
 ==================================================================
-> SIGNATURE: DILITHIUM ◉ ED25519 ◉ SPHINCS+
+> SIGNATURE: [DILITHIUM ◉ ED25519 ◉ SPHINCS+]
 > HASH: SHAKE256
 > BLOCKCHAIN: Hierarchical Block-Trie SUPERSTRUCTURE (DRAFT)
+> FILESYSTEM: DAG ◉ Linear Blockchain
 > BLOCKCHAIN TYPES: DAG ◉ Linear Blockchain
+> HASH SIZE: 64 BYTES
 > SYMBOL: ⩝
 
 ==================================================================
@@ -55,7 +57,7 @@
 ---------------------------------------------------------------
 > MISSION: POST QUANTUM CRYPTOGRAPHIC NEXUS
 ---------------------------------------------------------------
-> END OBJECTIVE: **INTERGALACTIC FEDERATED SYSTEM**
+> END OBJECTIVE: **UNIVERSAL FEDERATED SYSTEM**
 ---------------------------------------------------------------
 ==================================================================
 [>>> MADE IN AMERICA <<<] ┋ THE UNITED STATES OF AMERICA 🇺🇸

viat/blocks/receipt/block.js

@@ -1,3 +1,4 @@
+//  BETA
 import {
 	blockMethods,
 	getReceiptFromBlock,
@@ -18,13 +19,7 @@ import { assignToClass } from '@universalweb/acid';
 import blockDefaults from '../defaults.js';
 import { readStructured } from '#utilities/file';
 import viatCipherSuite from '#crypto/cipherSuite/viat.js';
-// Means receipt can be made independently of the block
-// Then include the block's hash as part of the TX Block Hashlink
-// Both are signed meaning they are all linked and contents can be trusted even based on the hash link alone
 // Block Hash (TX DATA || Receipt NONCE || Receipt Meta?) Creates cryptographic link to the original transaction block
-// Physical link is created by the path of the original TX hash
-// Block is stored using the receiver address plus the original transaction hash
-// Block's path mirrors the transaction block's path making it easy to find both
 // Both together create a physical link between the two blocks
 export class ReceiptBlock extends Block {
 	constructor(data, config) {
@@ -46,10 +41,15 @@ export async function receiptBlock(data, config) {
 	return block;
 }
 export default receiptBlock;
-const exampleBlock = await receiptBlock({
-	sender: viatCipherSuite.createBlockNonce(64),
-	transaction: viatCipherSuite.createBlockNonce(64),
-});
+// const exampleBlock = await receiptBlock({
+// 	sender: viatCipherSuite.createBlockNonce(64),
+// 	transaction: viatCipherSuite.createBlockNonce(64),
+// 	receiver: viatCipherSuite.createBlockNonce(64),
+// 	mana: 1000,
+// 	amount: 1000,
+// 	//  Reference a prior confirmed receipt from the receiver's address.
+// 	priorReceipt: viatCipherSuite.createBlockNonce(64)
+// });
 // console.log('Transaction Block', exampleBlock);
 // exampleBlock.setDefaults();
 // await exampleBlock.setHash();

viat/blocks/transaction/block.js

@@ -6,14 +6,7 @@ import {
 	getTransactionPathURLFromBlock,
 	getTransactionURLFromBlock
 } from './uri.js';
-// Include a Block Link ID - uses to quickly share a transaction and then can be efficiently found by other parties.
-// This is a unique ID that is generated for each transaction. It can be used to quickly find the transaction in the block chain.
-// Reference block, link block, Anchor block, receipt block -> Links to received viat from another wallets send block
-// TX Queue Block - This is a block that is used to queue transactions and alert validators of needed work. It can be used to quickly find none validated transactions in the block chain that aren't yet indexed.
-// Bloom Filter for confirmed transactions updated by the sender?
-// One for verifiers to check if a transaction is confirmed
-// The last for confirmed transactions that have been fully audited and verified
-// Use Merkle Trees with bloom filters - use merkle tree to confirm bloom filter then
+// Consider Multi-part transaction block -> reduce size and cost of each transaction
 import { toBase64Url, toHex } from '#crypto/utils.js';
 import { Block } from '../block.js';
 import blockDefaults from '../defaults.js';

viat/superStructure/package.js

@@ -0,0 +1 @@
+//  PACKAGE the superstructure into a unified folder of files for delivery of large sections or the entire superstructure