Skip to content

Commit e94f0d3

Browse files
committed
Doc Drafts
Viat code Filesystem Utilities
1 parent d1b96f6 commit e94f0d3

29 files changed

+1946
-961
lines changed

docs/library/viat/neuromorphic.md

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
# VIAT NEUROMORPHIC CHARACTERISTICS
2+
3+
- The Trie structure mirrors the hierarchical branching of neurons and dendrites, where lookup paths resemble synaptic pathways leading to specific neurons. Neurons and their dendrites exhibit a hierarchical branching pattern, where the primary branch (the one closest to the cell body) gives rise to secondary branches, which in turn can give rise to tertiary branches, and so on, forming a tree-like structure. This hierarchical structure plays a crucial role in neuronal function, particularly in integrating information from multiple sources and in shaping the receptive field of the neuron
4+
- The multiple DAGs/Linear Blockchains behave like interconnected subnetworks in the brain, each responsible for different functional pathways (e.g., wallet DAG, transaction chain, receipt DAG).
5+
- Each DAG/Chain is self-contained yet contributes to the larger cognitive flow of the system — like specialized brain regions.
6+
7+
Parallelism and Asynchronous Processing
8+
Just like the brain, Viat supports massively parallel verification and processing.
9+
Nodes (verifiers/validators) act like neurons firing and validating inputs in parallel — no global synchronization is required, reflecting asynchronous neural signaling.
10+
11+
Spatially Addressable Memory (On-Disk Trie Folders)
12+
The physical file system structure mirrors spatial locality in the brain, where data is organized and located efficiently.
13+
The use of constant-time lookups via physical paths is like neural signals traveling along optimized, reinforced synaptic paths.
14+
15+
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.
16+
17+
A new block is essentially a new memory introduced to the neuronal state of Viat (The Superstructure). This memory is now part of Viat's short term memory which overtime can either be strengthened by the network and or effectively "forgotten". Strengthening a block "memory" is done overtime becoming more certain and effectively committed to long term memory what we can consider to be confirmed on traditional blockchain networks.
18+
19+
Neural State Machine
20+
Purkinje cell
21+
dendrites
22+
Neurons
23+
Sensory Neurons
24+
Motor Neurons
25+
Interneurons (Projection/Relay) & local
26+
27+
Viat filesystem
28+
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.
29+
30+
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.
31+
32+
The URI act as a pathway or memory index to a specific memory. As you travel down the pathway associated information can be accessed until the final location.
33+
34+
wallets(Sensory cortices)/Cq2v/uH3f/(walletFolder last 32 bytes of 64)/transactions/HA/hQ/(transactionFolder last 30 bytes of 32)
35+
Lines changed: 14 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
1-
# VIAT LIVING SUPER STRUCTURE
1+
# VIAT SUPERSTRUCTURE
22

3+
NOTES:
34
Viat has a Neuromorphic self-organizing layered multidimensional DAG-like super structure.
45
Wallets are stored in a folder trie with folder names based on wallet addresses.
56
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.
@@ -14,17 +15,15 @@ All wallets link back to a core root wallet block then the genesis block.
1415

1516
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 32 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.
1617

17-
# VIAT META STRUCTURE
18-
19-
genesisBlock = Second layer of DAG Super Structure {
20-
smartContractsRootBlock: smartContractsChain,
21-
walletRootBlock: {
22-
walletA: {
23-
transactionRootBlock: TransactionChain,
24-
receiptRootBlock: receiptDAG,
25-
accountStateBlock: accountStateChain,
26-
pendingTransactionsRootBlock: pendingTransactionsDAG,
27-
transactionVerificationRootBlock: transactionVerification,
28-
}
29-
}
30-
}
18+
## VIAT GRAPH SUPERSTRUCTURE
19+
20+
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.
21+
22+
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.
23+
24+
## Viat Physical File System
25+
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.
26+
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.
27+
28+
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.
29+

package.json

Lines changed: 15 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -21,20 +21,22 @@
2121
"@universalweb/acid": "^3.0.74",
2222
"cbor-x": "^1.6.0",
2323
"commander": "^13.1.0",
24+
"directory-tree": "^3.5.2",
2425
"electron": "latest",
26+
"fs-extra": "^11.3.0",
2527
"hash-wasm": "^4.12.0",
2628
"ip": "^2.0.1",
2729
"keychain": "^1.5.0",
2830
"libsodium-wrappers": "^0.7.15",
29-
"mongoose": "^8.14.1",
31+
"mongoose": "^8.14.2",
3032
"node-seal": "^5.1.5",
3133
"node-watch": "^0.7.4",
3234
"nodemon": "^3.1.10",
3335
"os-utils": "^0.0.14",
3436
"pqclean": "latest",
3537
"qrcode": "^1.5.4",
3638
"signale": "^1.4.0",
37-
"sodium-native": "^5.0.1"
39+
"sodium-native": "^5.0.2"
3840
},
3941
"description": "UW & VIAT modules: Client, Server, VIAT, DIS, Browser, Crypto, Wallets, Modules, & certificates.",
4042
"engines": {
@@ -115,19 +117,19 @@
115117
},
116118
"version": "3.0.7",
117119
"devDependencies": {
118-
"@babel/core": "^7.26.10",
119-
"@babel/eslint-parser": "^7.27.0",
120-
"@babel/preset-env": "^7.26.9",
120+
"@babel/core": "^7.27.1",
121+
"@babel/eslint-parser": "^7.27.1",
122+
"@babel/preset-env": "^7.27.2",
121123
"@stylistic/eslint-plugin": "^4.2.0",
122124
"auto-changelog": "^2.5.0",
123125
"axios": "^1.9.0",
124126
"benchmark": "^2.1.4",
125-
"daisyui": "^5.0.30",
126-
"eslint": "^9.25.1",
127-
"eslint-plugin-jsdoc": "^50.6.11",
128-
"globals": "^16.0.0",
129-
"tailwindcss": "^4.1.4",
130-
"textlint": "^14.6.0"
127+
"daisyui": "^5.0.35",
128+
"eslint": "^9.26.0",
129+
"eslint-plugin-jsdoc": "^50.6.14",
130+
"globals": "^16.1.0",
131+
"tailwindcss": "^4.1.6",
132+
"textlint": "^14.7.1"
131133
},
132134
"pnpm": {
133135
"overrides": {
@@ -144,7 +146,8 @@
144146
"pqclean",
145147
"os-utils",
146148
"os",
147-
"sodium-native"
149+
"sodium-native",
150+
"node-seal"
148151
]
149152
},
150153
"packageManager": "[email protected]"

0 commit comments

Comments
 (0)