Skip to content

Incorrect retrieval protocol listed for CIDs with many providers #13

@masih

Description

@masih

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions