Skip to content

Crawl another network #76

Open
Open

Description

@ameersohel45

The problem. A farmer on our network only finds what our own providers publish. If a neighbouring network carries mandi prices we do not, that farmer cannot see them. The two networks may already have agreed to share, and it still makes no difference.

Admitting a network records the agreement. Nothing acts on it. Nothing goes and fetches what that network offers.

What needs to be true

  • A farmer searching here finds catalogues from a network we admitted, next to our own.
  • We take only the capabilities we chose from that network, not everything it offers.
  • A copy is visible to us alone. It never travels on to a third network.
  • A copy is served only for as long as the owning network allows.
  • When that network stops sharing something, it stops appearing here.
  • A farmer searching does not wait on another network. Whatever is shown is already here.

Doc: Share, Notify (projection change).

Parent: #48

Activity

  1. added
    networkNetwork layer - discovery, registry, protocol, catalog (Sanketika)
    adapterAdapter codebase (beckn-onix). Additive - use alongside a layer label
    on Oct 8, 2026
  2. self-assigned this
    on Oct 8, 2026
  3. added theissue type on Oct 8, 2026
  4. ameersohel45 commented on Oct 13, 2026

    @ameersohel45
    CollaboratorAuthor

    Outbound crawl is ready for review. Networks periodically fetch catalogs from admitted peers, allowing farmers to discover their published content. Verified live across two OAN stacks.

    One thing is still in progress: when another network requests our catalogs, we don’t yet verify whether we’ve agreed to share them with that network.

    PR: #83

  5. ameersohel45 commented on Oct 13, 2026

    @ameersohel45
    CollaboratorAuthor

    Now done too: when another network asks us for catalogs, the registry refuses its key unless we agreed to share with them, so an unagreed caller fails signature validation. Verified live.

  6. 87 remaining items

  7. changed the title [-]Crawl an admitted network and store what it shares[/-] [+]Crawl another network[/+] on Oct 15, 2026
  8. ameersohel45 commented on Oct 15, 2026

    @ameersohel45
    CollaboratorAuthor

    PR #83 covers this.

    We ask every network we admitted for its catalogues, and publish them into our own discovery. A farmer here finds them next to ours.

    We take only the packs we picked. Each copy is visible to us alone, so it never travels further. Each one expires after the time that network allows. Anything they stop sharing drops out on its own.

    The crawler keeps nothing between passes, so it needs no database.

  9. ameersohel45 commented on Oct 19, 2026

    @ameersohel45
    CollaboratorAuthor

    Here is the PR , to crawl the admitted network : #83 .

    Status - Inreview.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

adapterAdapter codebase (beckn-onix). Additive - use alongside a layer labelnetworkNetwork layer - discovery, registry, protocol, catalog (Sanketika)

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions