Viat File organization

Updated crypto middleware
Viat code updates

Author: tomekmarchi

.cspell/custom-dictionary-workspace.txt

@@ -21,6 +21,7 @@ scalarmult
 schnorr
 scid
 secp
+sphincs
 SPHINCS
 streamid
 udsp

docs/library/viat/mining.md

@@ -9,6 +9,6 @@ There are two types of Viat miners - Auditors (validate) and Arbiters (verify).
 This design is reflective of the individual specific blocks for specific actions to strive for as high as possible linear TPS and extreme scalability.
 
 
-# MINING VITANIUM [VI]
+# MINING VITAINIUM [VI]
 
-Vitanium is the element which is mined and processed resulting in the final material VIAT.
+Vitainium is the element which is mined and processed resulting in the final material VIAT.

docs/library/viat/strategy.md

@@ -7,4 +7,4 @@ Scalability potential stems from the modularity of the Viat super structure. The
 
 ## RISC LIKE THINKING
 
-Viat favors small consistent predictable contained operations over larger dynamic stacked operations. Instead of multiple transactions/operations forced into blocks  Viat is in direct position of that perspective opting to instead keep it one transaction per-block. Simple concise consistent instructions are faster, easier, more efficient and more optimizable than something that is less predictable and has to be broken down first to be processed.
+Viat favors small consistent predictable contained operations over larger dynamic stacked operations. Instead of multiple transactions/operations forced into blocks Viat is in direct position of that perspective opting to instead keep it one transaction per-block. Simple concise consistent instructions are faster, easier, more efficient and more optimizable than something that is less predictable and has to be broken down first to be processed.

docs/library/viat/superStructure.md

@@ -22,8 +22,8 @@ The root layer is the genesis block and all things can directly trace back to it
 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
-Blocks are cryptographically linked allowing Viat to be displayed as a graph but the Super Structure itself consists of physical files and folders on disk.
-The VIAT Super Structure 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. 
+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. 
 
 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.
 

package.json

@@ -28,15 +28,15 @@
 		"ip": "^2.0.1",
 		"keychain": "^1.5.0",
 		"libsodium-wrappers": "^0.7.15",
-		"mongoose": "^8.14.2",
+		"mongoose": "^8.14.3",
 		"node-seal": "^5.1.5",
 		"node-watch": "^0.7.4",
 		"nodemon": "^3.1.10",
 		"os-utils": "^0.0.14",
 		"pqclean": "latest",
 		"qrcode": "^1.5.4",
 		"signale": "^1.4.0",
-		"sodium-native": "^5.0.2"
+		"sodium-native": "^5.0.3"
 	},
 	"description": "UW & VIAT modules: Client, Server, VIAT, DIS, Browser, Crypto, Wallets, Modules, & certificates.",
 	"engines": {
@@ -126,7 +126,7 @@
 		"benchmark": "^2.1.4",
 		"daisyui": "^5.0.35",
 		"eslint": "^9.26.0",
-		"eslint-plugin-jsdoc": "^50.6.14",
+		"eslint-plugin-jsdoc": "^50.6.17",
 		"globals": "^16.1.0",
 		"tailwindcss": "^4.1.6",
 		"textlint": "^14.7.1"