Detector: ZK verifier missing public-input / field-element range validation

[Gbangbolaoluwagbemiga]

Epic: Zero-Knowledge Verification

Summary

Flag on-chain proof verification that consumes public inputs without validating they are canonical field elements in range.

Background & Problem

A verifier that accepts out-of-range or non-canonical public inputs can be tricked; this is a classic ZK integration bug.

Impact / Why it matters

Prevents a whole class of critical verifier bypasses.

Proposed Approach

• Identify verification entry points + public-input params.
• Check for range/canonicality validation before the pairing check.

Acceptance Criteria

• Flags missing public-input validation.
• No FP when validation is present.

---

Filed as part of the mainnet-readiness & world-class roadmap. Scope is intentionally small enough for one focused PR; comment to claim.

[Alheriii]

Hi there 👋

I’d love to pick this one up.

For context: 200+ contributions shipped across the ecosystem, clean reviews, and I contributed to this project last wave with no dropped PRs or delays.

I’ll add comprehensive tests for DatasetRegistry, LicenseRouter, and RoyaltySplitter — covering happy paths, authorization, edge cases, expiry, revocation, and failures. Aiming for >85% coverage and cargo test --all green before PR.

Can I be assigned? Thanks!

[Gbangbolaoluwagbemiga]

@Alheriii, you are assigned, ensure all ci pipeline passes