Block Storage System
Store blocks with a sha256 hash. We can then then request these blocks or seek them in the network by using their ID (the sha256). Storage blocks then make up a fundamental part of the network. Posts, images, videos, pages, and whatever else we need can be stored inside these blocks.
Types of blocks:
- UUK (Un-Updatable Key) - Static blocks. Can not be updated.
- USK (Updateable Site Key) - this is the sha256 of a key used to sign the release blocks. New versions can be released as needed.
From this we can then go on to create a WOT (Web of Trust) of other identities in the network. Posts and images can be inserted via UUK and addressed in a USK feed.
Blueprint information
- Status:
- Complete
- Approver:
- Vomun Developers
- Priority:
- Undefined
- Drafter:
- Vomun Developers
- Direction:
- Needs approval
- Assignee:
- aj00200
- Definition:
- Approved
- Series goal:
- Accepted for 0.0.0
- Implementation:
-
Implemented
- Milestone target:
-
build-6
- Started by
- aj00200
- Completed by
- aj00200
Whiteboard
Current block size limit would have to be 2048 bits because of the crypto limits in bug #892896. This can be changed later.
-------
The following comment was made by pharno but placed in the description rather than on the whiteboard:
maybe have a checksum integrated in the write and retrieve part. But looks good so far :) ~~pharno
-------------------
Are you suggesting that we hash the data to see if it matches the hash information given in the block ID for UUKS? For USKs, we can use signatures on the block to verify the data.
--Aj00200
-------------------
It has been implemented but it is not being used. We need appropriate API calls for it and we will probably need some protocol changes to mark packets as needing to be stored. We will see how this pans out over the next few days.
--Aj00200
Work Items
Dependency tree
* Blueprints in grey have been implemented.
