search

storacha-network / specs

🏅 Technical specifications for the w3up protocol stack
17 stars 0 forks source link

feat: propose `admin/upload/inspect` and `admin/store/inspect` capabilities #77

Closed travis closed 9 months ago

travis commented 10 months ago

At a high level, these are designed to enable administrators like @dchoi27 to figure out which space a given CID is associated with.

Problem CIDs come to us from a variety of sources - sometimes they are content CIDs that correspond to a particular upload/add invocation and sometimes they are "shard" CIDs that identify one of the CARs stored using store/add that make up the shards of a larger upload. admin/upload/inspect returns information about the upload and admin/store/inspect returns information about particular shards, so given an unknown CID administrators should check both.

alanshaw commented 10 months ago

Oh I should really read the PR description before reviewing the code 🤦‍♂️

I'd vote for 2 separate capabilities for querying upload/adds and store/adds!

travis commented 10 months ago

ok cool - I will rework this with two separate capabilities!

alanshaw commented 10 months ago

+1 I'm cool with trace/store/add and trace/upload/add as the capability names.

travis commented 9 months ago

ok great, works for me too! I'll get this in now!