You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the LID web UI, the SP can look up a cid in the search box.
It will look up the cid as a payload cid by searching
in the LID payload cid -> piece cid index
in the boostd sqlite database by root payload cid (deal data root cid).
In practice it is confusing to lookup the cid by root payload cid (the deal's Label field) in the boostd sqlite database. It can give the SP the impression that the deal label field corresponds to a payload cid, when that may not actually be the case.
If the user wants to search by the deal's Label field they can already do this using the search box on the Storage Deals list page.
We should remove the code that looks up the cid by root payload cid in the web UI, including removing it from the graphql endpoint (resolver).
The text was updated successfully, but these errors were encountered:
In the LID web UI, the SP can look up a cid in the search box.
It will look up the cid as a payload cid by searching
In practice it is confusing to lookup the cid by root payload cid (the deal's Label field) in the boostd sqlite database. It can give the SP the impression that the deal label field corresponds to a payload cid, when that may not actually be the case.
If the user wants to search by the deal's Label field they can already do this using the search box on the Storage Deals list page.
We should remove the code that looks up the cid by root payload cid in the web UI, including removing it from the graphql endpoint (resolver).
The text was updated successfully, but these errors were encountered: