Implement CIDv1

[whyrusleeping]

Once the content ID v1 specification is finalized, we need to begin the work of implementing and integrating it into go-ipfs.

This will contain roughly the following tasks:

• Implement go-multibase
• implement binary multicodec
• Implement 'go-cid' (or whatever we choose to call it)
• integrate into go-ipfs packages:
  • blocks package. NewBlock should use CID to 'hash' content, and the Key() method should return a CID
  • blocks/key should be able to understand multibase (and when to leave it off for legacy keys?)
  • exchange/bitswap will need to handle sending CIDs and legacy keys in wantlists
  • path:
    • resolver will need to understand CIDs (might not need to change anything here)
    • ParsePath needs to understand multibase
  • core/corehttp/commands/http will need to understand CIDs and multibase encodings
  • TODO: other integration points

Depends on:

• Bitswap cant currently handle other types of hashes #3055

Links:

• CIDv1 proposal: Experimental Proposal: CIDv1 -- IPLD, Multicodec-packed, and more specs#130

[jbenet]

There should be a separate package -- go-cid -- that implements all the
parsing/coding.
On Mon, Aug 8, 2016 at 11:02 Jeromy Johnson [email protected]
wrote:

Once the content ID v1 specification is finalized, we need to begin the
work of implementing and integrating it into go-ipfs.

This will contain roughly the following tasks:

• Implement go-multibase
• implement binary multicodec
• Implement 'go-cid' (or whatever we choose to call it)
• integrate into go-ipfs packages:
  • blocks package. NewBlock should use CID to 'hash' content, and
    the Key() method should return a CID
  • blocks/key should be able to understand multibase (and when to
    leave it off for legacy keys?)
  • exchange/bitswap will need to handle sending CIDs and legacy keys
    in wantlists
  • path:
    • resolver will need to understand CIDs (might not need to
      change anything here)
    • ParsePath needs to understand multibase
  • core/corehttp/commands/http will need to understand CIDs and
    multibase encodings
  • TODO: other integration points

Depends on:

• Bitswap cant currently handle other types of hashes #3055 Bitswap cant currently handle other types of hashes #3055

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#3059, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIcodw9xq-SS69BpzGDUMleWkD9DRV_ks5qd0T-gaJpZM4JfIqY
.

[ghost]

• find a name
  • multiname
  • multid (mul-thai-dee -- maybe too smart?)
  • multiqual (qualifier -- might sound too much like equal)
  • multisym (symbol, which is a synonym of identifier)

[whyrusleeping]

multilarsgierth

On Mon, Aug 22, 2016 at 4:00 PM Lars Gierth [email protected]
wrote:

• find a name
  • multiname
  • multid (mul-thai-dee -- maybe too smart?)
  • multiqual (qualifier -- might sound too much like equal)
  • multisym (symbol, which is a synonym of identifier)

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#3059 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABL4HM47iNADl5OXlPgfQE6Z4CQNlt6Eks5qiiohgaJpZM4JfIqY
.

[Kubuxu]

@lgierth for me it looks like it isn't really a part of multiformats suite, it is just bundle of them to be used as object identifiers in IPLD.

EDIT: s/IPFS/IPLD/

[jbenet]

I think it should be part of IPLD, it will be usable in other systems

[whyrusleeping]

This has been implemented