Skip to main content
Version: 3.2.0

Proof download waits while certificates are missing

Overview​

A certificate that is not on OVH yet must not fail the Tower job.

How it works​

neo answers 202 certificates_not_ready from the proof zip while no Bitcoin proof is complete. Tower throws ProofNotReadyError, the job returns to Waiting, and the hourly cron retries it with no age limit. An older neo answers 409 in the same case, which is handled the same way. HTTP 422 still fails the job.

Key files​

  • src/protocol/bcyip/api.ts - Accept 202, 409 and 422 from the zip
  • src/app.service.ts - Map a missing certificate to Waiting
  • src/protocol/bcyip/download-proof.spec.ts - Zip statuses

Known issues​

  • None recorded in the 3.2.0 fragment.

Next steps​

  • None from this release.