Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Canonical Content Registry on Blockstack #79

Closed
denisnazarov opened this issue Apr 9, 2015 · 5 comments
Closed

Canonical Content Registry on Blockstack #79

denisnazarov opened this issue Apr 9, 2015 · 5 comments

Comments

@denisnazarov
Copy link

denisnazarov commented Apr 9, 2015

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:

  1. Store unique CCID (canonical content identifier) in Blockstore
  2. Append file instance metadata to CCID (see examples in canonical-content-registry)
  3. Tag a CCID with a nametag
  4. Sign a statement stating a nametag belongs to an Openname profile
  5. Append arbitrary metadata to CCID (hashtags, related CCIDs, etc)
  6. 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

@shea256
Copy link
Member

shea256 commented Apr 15, 2015

This is awesome! Really like the detail you've added since you first showed us.

I'll dig into it deeper and provide some more in-depth feedback in a bit.

One quick thing I'm trying to figure out, though, is whether discussions like these should go under blockstore or under "specifications" for the protocol (the blockchain name protocol, formerly OpenName).

Check out the README.md:
https://github.com/openname/specifications

As you can see, we have specifications for users, but we can add specifications for content, according to your proposal.

Thoughts?

@denisnazarov
Copy link
Author

denisnazarov commented Apr 17, 2015

I think definitely a good idea to eventually add to the spec repo. Not sure if the preliminary discussion belongs here, because it is around the technical limitations/possibilities of blockstore.

Still thinking through #81, will try to respond with some thoughts this weekend.

@shea256
Copy link
Member

shea256 commented Apr 21, 2015

OK sounds good.

@muneeb-ali
Copy link
Member

muneeb-ali commented Apr 23, 2015

@denisnazarov Just read https://github.com/mine-code/canonical-content-registry -- great job at describing your system. Noticed you had Sybil attacks in the questions section. I'm writing about this and will share more details with you shortly. You might not have to worry about Sybil attacks :-)

@muneeb-ali muneeb-ali changed the title Canonical Content Registry on Blockstore Canonical Content Registry on Blockstack Feb 7, 2017
@jackzampolin
Copy link
Contributor

jackzampolin commented Jan 11, 2018

Closing as stale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants