Skip to main content
Challenge

Build a Local Service Registry Interoperability and Audit Pipeline

Reconcile service provider credential updates and catalog diffs across decentralized Beckn registry nodes. Identify conflicting registrations and audit participant compliance.

Workflow AutomationHosted by Vera
Challenge brief

What you are building

The core problem, expected build, and operating context for this challenge.

Reconcile service provider credential updates and catalog diffs across decentralized Beckn registry nodes. Identify conflicting registrations and audit participant compliance.

Network Governance Analyst

Poll mock Beckn registry nodes for registered provider service capabilities and signing keys.

Detect registry diffs such as service radius changes, category alterations, and key rotations.

Audit cryptographic key formats and check for unauthorized category claims.

Publish synchronized participant directories with verifiable audit stamps.

Registry network topology dashboard showing node sync status, key lifecycle, and policy alerts.

Construct synthetic Beckn registry snapshots containing provider registration records and key logs. Starter examples below are synthetic. They are not downloaded records.

Beckn protocol specifications Adopts Beckn network architecture specs for BAP, BPP, and Registry discovery interactions.

ray-serve, cryptography, pydantic. Distributes high-throughput batch validation of registry participant records across parallel workers. Local embedding or lightweight classifier model to identify duplicate service provider listings.

Submit runnable source, pinned dependencies, setup commands, a working interface, example outputs, and a recorded end-to-end demo. Include tests and an action log.

Identifies unauthorized modifications to participant service boundary radii.

Validates public key format compliance according to Beckn network policy.

Detects duplicate entity listings operating under conflicting network IDs.

Generates synchronized directory snapshots with cryptographic audit hashes.

```json [ { "input": { "node_id": "REG-NODE-01", "entry": { "participant_id": "bpp.kirana-fresh.net", "role": "BPP", "signing_key": "MCowBQYDK2VwAyEA9Y4X2s...mockedKey", "categories": [ "retail:grocery" ], "service_radius_km": 15 } }, "expected_output": { "validation_status": "VALID", "key_compliant": true, "discrepancies": [], "sync_action": "UPSERT_ACTIVE_DIRECTORY" } }, { "input": { "node_id": "REG-NODE-02", "entry": { "participant_id": "bpp.kirana-fresh.net", "role": "BPP", "signing_key": "MALFORMED_HEADER_KEY", "categories": [ "retail:grocery", "financial:micro_loans" ], "service_radius_km": 2500 } }, "expected_output": { "validation_status": "INVALID", "key_compliant": false, "discrepancies": [ "INVALID_KEY_FORMAT", "UNLICENSED_CATEGORY_FINANCIAL", "RADIUS_EXCEEDS_LOCAL_LIMIT" ], "sync_action": "QUARANTINE_RECORD" } } ] ```

Maintains mock registry state; performs simulated cryptographic checks without manipulating real network registries. Use mock external writes. Require human review before any real deployment.

Rules

Participation guide

Maintains mock registry state; performs simulated cryptographic checks without manipulating real network registries. Use mock external writes and human review.

Delivery guide

How work is evaluated

Evaluation

Identifies unauthorized modifications to participant service boundary radii. Validates public key format compliance according to Beckn network policy. Detects duplicate entity listings operating under conflicting network IDs. Generates synchronized directory snapshots with cryptographic audit hashes.

Submission format

Runnable source, pinned dependencies, setup commands, working interface, example outputs, recorded demo, tests, and action logs.

Datasets

Challenge datasets

Public datasets, plus the private datasets you have access to.

Evaluation rubric

How submissions are scored

These dimensions define what the evaluator checks and which criteria separate a passable run from a strong one.

Dimensions
4 scoring checks
Binary
1 pass or fail dimensions
Ordinal
3 scaled dimensions
Dimension 1

Complete workflow

Poll mock Beckn registry nodes for registered provider service capabilities and signing keys. Detect registry diffs such as service radius changes, category alterations, and key rotations. Audit cryptographic key formats and check for unauthorized category claims. Publish synchronized participant directories with verifiable audit stamps.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 2

Correctness and evidence

Identifies unauthorized modifications to participant service boundary radii. Validates public key format compliance according to Beckn network policy. Detects duplicate entity listings operating under conflicting network IDs. Generates synchronized directory snapshots with cryptographic audit hashes.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 3

Review interface

Registry network topology dashboard showing node sync status, key lifecycle, and policy alerts.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 4

Safe execution

Maintains mock registry state; performs simulated cryptographic checks without manipulating real network registries.

Binary check

This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.

Learning goals

What you should walk away with

  • Poll mock Beckn registry nodes for registered provider service capabilities and signing keys.

  • Detect registry diffs such as service radius changes, category alterations, and key rotations.

  • Audit cryptographic key formats and check for unauthorized category claims.

  • Publish synchronized participant directories with verifiable audit stamps.

Resources and assets

Reference links and supporting material

Dataset notes

Construct synthetic Beckn registry snapshots containing provider registration records and key logs. Supplied starter examples are synthetic, not source extracts.

Challenge setup

Configuration summary for this challenge.

Challenge input

Input details are not configured.

Ray Serve

Action Space in the agent workflow.

Evaluated output

No output checks are configured.

Evaluation checks
  • Poll mock Beckn registry nodes for registered provider service capabilities and signing keys. Detect regist...
  • Identifies unauthorized modifications to participant service boundary radii. Validates public key format co...
  • Registry network topology dashboard showing node sync status, key lifecycle, and policy alerts.
Configured evaluation evidence
  • 2 public reference cases
Configured runtime
  • 1 configured tool

Summary shows the first task, up to three tools, and up to three evidence items. Open the technical recipe to view all configured items.

View technical recipe

Configured tools

Action Space
  • Ray Serve · Optional

Evaluation contract

  • Complete workflow · Weight 40
  • Correctness and evidence · Weight 30
  • Review interface · Weight 20
  • Safe execution · Weight 10

Reference cases

  • 2 public reference cases

Workflow tasks

No workflow tasks are configured.

Recipe freeze marker

No recipe freeze time is recorded.

Frequently Asked Questions about Build a Local Service Registry Interoperability and Audit Pipeline