tfgrid/info_tfgrid
30
3
Fork 0
Code Issues Pull Requests 1 Packages Projects Releases Activity

Merge branch 'main_commsteam' of https://git.ourworld.tf/tfgrid/info_tfgrid into main_commsteam

Browse Source
This commit is contained in:
samtaggart 2024-04-04 12:29:10 +02:00
commit 606884068b
1 changed files with 31 additions and 31 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

62
collections/tech/qsss/nft_storage.md
View File

@ -4,53 +4,53 @@
> TODO: need to upgrade image, also digital twin needs to be named '3bot' > TODO: need to upgrade image, also digital twin needs to be named '3bot'
The owner of the NFT can upload the data using one of our supported interfaces The owner of the NFT can upload the data using one of our supported interfaces:
- http upload (everything possible on https://nft.storage/ is also possible on our system) - Http upload (everything possible on https://nft.storage/ is also possible on our system)
- filesystem - Filesystem
Every person in the world can retrieve the NFT (if allowed) and the data will be verified when doing so. The data is available everywhere in the world using multiple interfaces again (IPFS, HTTP(S), ...). Caching happens on global level. No special software or account on threefold is needed to do this. Anyone in the world can retrieve the NFT (if allowed) and the data will be verified when doing so. The data is available anywhere in the world using multiple interfaces again (IPFS, HTTP(S) etc.). Caching happens on a global level. No special software or account on ThreeFold is needed to do this.
The NFT system uses a super reliable storage system underneath which is sustainable for the planet (green) and ultra secure and private. The NFT owner also owns the data. The NFT system operates on top of a very reliable storage system which is sustainable for the planet and ultra secure and private. The NFT owner also owns the data.
## Benefits ## The Benefits
#### Persistence = owned by the data user (as represented by digital twin) #### Persistence = owned by the data user (as represented by digital twin)
![](img/nft_storage.jpg) ![](img/nft_storage.jpg)
Is not based on a shared-all architecture. The system is not based on a shared-all architecture.
Whoever stores the data has full control over Whoever stores the data has full control over:
- where data is stored (specific locations) - Where data is stored (specific locations)
- redundancy policy used - The redundancy policy which is used
- how long should the data be kept - How long the data is kept
- CDN policy (where should data be available and how long) - CDN policy (where the data is available and for how long)
#### Reliability #### Reliability
- data cannot be corrupted - Data cannot be corrupted
- data cannot be lost - Data cannot be lost
- each time data is fetched back hash (fingerprint) is checked, if issues autorecovery happens - Each time data is fetched back the hash (fingerprint) is checked. If there are any issues then autorecovery occurs
- all data is encrypted and compressed (unique per storage owner) - All data is encrypted and compressed (unique per storage owner)
- data owner chooses the level of redundancy - Data owner chooses the level of redundancy
#### Lookup #### Lookup
- multi URL & storage network support (see further the interfaces section) - Multi URL & storage network support (see more in the interfaces section)
- IPFS, HyperDrive URL schema - IPFS, HyperDrive URL schema
- unique DNS schema (with long key which is globally unique) - Unique DNS schema (with long key which is globally unique)
#### CDN support (with caching) #### CDN Support
Each file (movie, image) stored is available on many places worldwide. Each file (movie, image etc.) stored is available in many locations worldwide.
Each file gets a unique url pointing to the data which can be retrieved on all locations. Each file gets a unique url pointing to the data which can be retrieved from all these locations.
Caching happens on each endpoint. Caching happens at each endpoint.
#### Self Healing & Auto Correcting Storage Interface #### Self Healing & Auto Correcting Storage Interface
@ -58,9 +58,9 @@ Any corruption e.g. bitrot gets automatically detected and corrected.
In case of a HD crash or storage node crash the data will automatically be expanded again to fit the chosen redundancy policy. In case of a HD crash or storage node crash the data will automatically be expanded again to fit the chosen redundancy policy.
#### Storage Algoritm = Uses Quantum Safe Storage System as base #### The Storage Algoritm Uses Quantum Safe Storage System As Its Base
Not even a quantum computer can hack data as stored on our QSSS. Not even a quantum computer can hack data stored on our QSSS.
The QSSS is a super innovative storage system which works on planetary scale and has many benefits compared to shared and/or replicated storage systems. The QSSS is a super innovative storage system which works on planetary scale and has many benefits compared to shared and/or replicated storage systems.
@ -74,15 +74,15 @@ Storage uses upto 10x less energy compared to classic replicated system.
The stored data is available over multiple interfaces at once. The stored data is available over multiple interfaces at once.
| interface | | | Interface | |
| -------------------------- | ----------------------- | | -------------------------- | ----------------------- |
| IPFS | ![](img/ipfs.jpg) | | IPFS | ![](img/ipfs.jpg) |
| http(s) on top of Digital Twin | ![](img/http.jpg) | | Http(s) on top of Digital Twin | ![](img/http.jpg) |
| syncthing | ![](img/syncthing.jpg) | | Syncthing | ![](img/syncthing.jpg) |
| filesystem | ![](img/filesystem.jpg) | | Filesystem | ![](img/filesystem.jpg) |
This allows ultimate flexibility from enduser perspective. This allows ultimate flexibility from the end user perspective.
The object (video,image) can easily be embedded in any website or other representation which supports http. The object (video, image etc.) can easily be embedded in any website or other representation which supports http.