Hello, we are specifying a protocol for a canonical content registry. You can read a detailed proposal here: https://github.com/mine-code/canonical-content-registry. We are interested in building it on top of Blockstore to do the following:
- Store unique CCID (canonical content identifier) in Blockstore
- Append file instance metadata to CCID (see examples in canonical-content-registry)
- Tag a CCID with a nametag
- Sign a statement stating a nametag belongs to an Openname profile
- Append arbitrary metadata to CCID (hashtags, related CCIDs, etc)
- Ability to easily interpret the above by a new node in the DHT
I wanted to open this issue to start a discussion about extending Blockstore to support writing metadata in the format above. What are the systems current limitations and what could be possible steps to extend blockstore?
Reading the README should provide some context. Let me know if I can clarify any of the ideas, and feel free to open CCR related issues on that repo.
@muneeb-ali @shea256 @jessewalden @moudy
Hello, we are specifying a protocol for a canonical content registry. You can read a detailed proposal here: https://github.com/mine-code/canonical-content-registry. We are interested in building it on top of Blockstore to do the following:
I wanted to open this issue to start a discussion about extending Blockstore to support writing metadata in the format above. What are the systems current limitations and what could be possible steps to extend blockstore?
Reading the README should provide some context. Let me know if I can clarify any of the ideas, and feel free to open CCR related issues on that repo.
@muneeb-ali @shea256 @jessewalden @moudy