Skip to content

IPNS resolve does not query delegated HTTP routers #925

@Rinse12

Description

@Rinse12

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 /ipns endpoints), 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

  1. Clone https://github.com/Rinse12/delegated-routing-ipns-provider-repro
  2. npm install
  3. npm run start
  4. Observe the logs

Notes

  • The repro spins up:
    • A local delegated routing HTTP server that only serves /routing/v1/providers/*.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Medium: Good to have, but can wait until someone steps upneed/analysisNeeds further analysis before proceeding

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions