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

Incorrect retrieval protocol listed for CIDs with many providers #13

Open
masih opened this issue May 30, 2023 · 0 comments
Open

Incorrect retrieval protocol listed for CIDs with many providers #13

masih opened this issue May 30, 2023 · 0 comments

Comments

@masih
Copy link
Member

masih commented May 30, 2023

Example:
bafy2bzacebc3bt6cedhoyw34drrmjvazhu4oj25er2ebk4u445pzycvq4ta4a

From the cid.contact website I get this which seems to indicate dag-house is running graphsync, which last I checked wasn't the case.
image

curling the routing/v1 endpoint shows only Bitswap from /dns4/elastic.dag.house/tcp/443/wss
curling the /cid endpoint seems to also only show bitswap (although it shows the many IPNI internal duplicate records)

I don’t see garaphsync metadata listed in json response under daghouse :
$ curl https://cid.contact/cid/bafy2bzacebc3bt6cedhoyw34drrmjvazhu4oj25er2ebk4u445pzycvq4ta4a | jq -c '.MultihashResults[].ProviderResults[] | select(.Metadata | length > 4) | select(.Provider.Addrs[] | contains("dag"))'
There are, however, providers for that CID over graphsync it seems:
$ curl https://cid.contact/cid/bafy2bzacebc3bt6cedhoyw34drrmjvazhu4oj25er2ebk4u445pzycvq4ta4a | jq -c '.MultihashResults[].ProviderResults[] | select(.Metadata | length > 4).Provider.Addrs | unique'
If I have not missed anything this looks like a bug in cid.contact web UI.

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

1 participant