Production Verification

Production verification is the quality gate that allows an Engine to operate in public production communities. The goal is to ensure users receive reliable results and that Engines behave safely and predictably under real traffic.

What Verification Checks

Verification typically includes four areas:

Identity and agreement checks

• KYC completion (where required)
• Engine Provider Agreement completed (where required)

Engine configuration review

• Engine configuration fields are present and correct in the UI
• Artifact types and webhook selection are correct
• Any required metadata or capability fields are accurately set

Technical verification

• PolySwarm sends known benign and known malicious test artifacts to your Engine in a controlled environment

• Your Engine must:

  • accept webhook requests
  • validate signatures
  • return 202 Accepted quickly
  • process the bounty asynchronously
  • post a correctly formatted assertion back
• Unsupported artifact types must return UNKNOWN with bid 0

Operational readiness

• Endpoint is stable and reachable over HTTPS
• Engine is reliable under expected traffic (rate limit and concurrency)
• Timeouts and error handling do not cause cascading failures

Passing Verification

You will typically pass verification when:

• Your Engine consistently produces valid assertions
• Your webhook service stays online throughout the verification window
• Responses are timely, consistent, and do not exceed expected time limits
• Unsupported artifacts are handled safely (UNKNOWN, bid 0)
• Configuration in the UI matches real behavior

Common Verification Failure Reasons

• Webhook reachable but fails signature validation: Secret mismatch or signature implementation bug
• Webhook returns slow responses: Analysis happens in the HTTP request thread instead of a worker
• Malformed assertions: Missing verdict, invalid bid type, invalid metadata structure
• Artifact download failures: Network or firewall issues, incorrect handling of artifact_uri
• Incorrect handling of unsupported types: Returning benign instead of UNKNOWN

Verification Failure

1. Review the feedback from the PolySwarm Engines team.
2. Fix the issue and test the fix in the Development Community.
3. Request verification again from My Engines.