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

Switch from CID to pid (particle id) #577

Open
mastercyb opened this issue Jan 27, 2021 · 2 comments
Open

Switch from CID to pid (particle id) #577

mastercyb opened this issue Jan 27, 2021 · 2 comments

Comments

@mastercyb
Copy link
Member

Using CIDs in the knowledge graph leads to 3 problems:

  1. Content duplication and rank inflation as result. While IPFS itself strives to deduplicate content, CIDs creates a situation in which 1 unique piece of content can identify by infinite variants. This potentially could kill the idea of ranking.
  2. Inefficient memory usage. CIDS are 64 bytes. We can do 32 bytes. While 64 bytes max length is enforced the average length is around 40 bytes. In Cyber GPU memory is the most scarce resource. Switching to Keccak-256 (also used in Ethereum) we can reduce requirements twofold.
  3. Potential censorship for encodings. Currently, all additions to CIDs are prone to censorship. We can move out the information on how to interpret given CID to the knowledge graph itself hence making the approach ultimately flexible and resistant to censorship.

That is. I cannot see now how we can move the Great Web further with CIDs. They are clunky, authoritative, and inefficient for use in the knowledge graphs. I would switch content identification to Particles IDs (pids) - simple KECCAK-256 which is already being used in Ethereum. This decision simplifies so much and make cyberlinks even more powerful and universal construction.

@cyborgshead
Copy link
Member

cyborgshead commented Mar 12, 2021

Let's do this @cyb-master

@mastercyb
Copy link
Member Author

mastercyb commented Mar 14, 2021

Related all-stars discussion. Still tend to Keccak.

Sha-256 have one very serious advantage: written off bitcoin asics can be used for content migration

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

No branches or pull requests

2 participants