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

changed digital twin to 3bot

Browse Source
This commit is contained in:
mik-tf 2024-04-11 12:53:24 +00:00
parent 41932e2203
commit 7ce269b419
1 changed files with 88 additions and 88 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -1,88 +1,88 @@
# Quantum Safe Storage System for NFT
![](img/nft_architecture.jpg)
> 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:
- Http upload (everything possible on https://nft.storage/ is also possible on our system)
- Filesystem
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 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.
## The Benefits
#### Persistence = owned by the data user (as represented by digital twin)
![](img/nft_storage.jpg)
The system is not based on a shared-all architecture.
Whoever stores the data has full control over:
- Where data is stored (specific locations)
- The redundancy policy which is used
- How long the data is kept
- CDN policy (where the data is available and for how long)
#### Reliability
- Data cannot be corrupted
- Data cannot be lost
- 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)
- Data owner chooses the level of redundancy
#### Lookup
- Multi URL & storage network support (see more in the interfaces section)
- IPFS, HyperDrive URL schema
- Unique DNS schema (with long key which is globally unique)
#### CDN Support
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 from all these locations.
Caching happens at each endpoint.
#### Self Healing & Auto Correcting Storage Interface
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.
#### The Storage Algoritm Uses Quantum Safe Storage System As Its Base
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.
It uses forward looking error correcting codes inside.
#### Green
Storage uses upto 10x less energy compared to classic replicated system.
#### Multi Interface
The stored data is available over multiple interfaces at once.
| Interface | |
| -------------------------- | ----------------------- |
| IPFS | ![](img/ipfs.jpg) |
| Http(s) on top of Digital Twin | ![](img/http.jpg) |
| Syncthing | ![](img/syncthing.jpg) |
| Filesystem | ![](img/filesystem.jpg) |
This allows ultimate flexibility from the end user perspective.
The object (video, image etc.) can easily be embedded in any website or other representation which supports http.
# Quantum Safe Storage System for NFT
![](img/nft_architecture.jpg)
> 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:
- Http upload (everything possible on https://nft.storage/ is also possible on our system)
- Filesystem
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 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.
## The Benefits
#### Persistence = Owned by the data user, as represented by their associated 3bot
![](img/nft_storage.jpg)
The system is not based on a shared-all architecture.
Whoever stores the data has full control over:
- Where data is stored (specific locations)
- The redundancy policy which is used
- How long the data is kept
- CDN policy (where the data is available and for how long)
#### Reliability
- Data cannot be corrupted
- Data cannot be lost
- 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)
- Data owner chooses the level of redundancy
#### Lookup
- Multi URL & storage network support (see more in the interfaces section)
- IPFS, HyperDrive URL schema
- Unique DNS schema (with long key which is globally unique)
#### CDN Support
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 from all these locations.
Caching happens at each endpoint.
#### Self Healing & Auto Correcting Storage Interface
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.
#### The Storage Algoritm Uses Quantum Safe Storage System As Its Base
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.
It uses forward looking error correcting codes inside.
#### Green
Storage uses upto 10x less energy compared to classic replicated system.
#### Multi Interface
The stored data is available over multiple interfaces at once.
| Interface | |
| -------------------------- | ----------------------- |
| IPFS | ![](img/ipfs.jpg) |
| Http(s) on top of 3bot | ![](img/http.jpg) |
| Syncthing | ![](img/syncthing.jpg) |
| Filesystem | ![](img/filesystem.jpg) |
This allows ultimate flexibility from the end user perspective.
The object (video, image etc.) can easily be embedded in any website or other representation which supports http.