-
Notifications
You must be signed in to change notification settings - Fork 141
Open
Labels
P2Medium: Good to have, but can wait until someone steps upMedium: Good to have, but can wait until someone steps upneed/analysisNeeds further analysis before proceedingNeeds further analysis before proceeding
Description
Environment
In our project we use IPNS-Over-Pubsub and maintain both kubo nodes and helia. We have rolled out a delegated http routers with support only for /providers since in kubo you don't need /ipns for IPNS provider query.
ipnsPubsubTopicRoutingCid = CID.createV1(0x55, sha256("floodsub:" + ipnsPubsubTopic))
Expected behavior
- When resolving an IPNS name using a delegated routing client (without
/ipnsendpoints), the resolver should query/routing/v1/providers/<ipnsPubsubTopicRoutingCid>to discover providers and dial them. - The resolver should connect to the announced provider, join the IPNS pubsub topic
Actual behavior
- IPNS resolve fails with
RecordNotFoundError. - No
/routing/v1/providers/*requests are made (provider query count stays 0). - The resolver never connects to the provider (
connections after resolve attempt: 0).
How to replicate
- Clone https://github.com/Rinse12/delegated-routing-ipns-provider-repro
npm installnpm run start- Observe the logs
Notes
- The repro spins up:
- A local delegated routing HTTP server that only serves
/routing/v1/providers/*.
- A local delegated routing HTTP server that only serves
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
P2Medium: Good to have, but can wait until someone steps upMedium: Good to have, but can wait until someone steps upneed/analysisNeeds further analysis before proceedingNeeds further analysis before proceeding