Not available yet. Replyz is built and tested, but not deployed: https://api.replyz.io is the planned address and does not answer yet. These pages describe the API as it is built today and may change before launch.

pow_invalid

HTTP 400 · The proof of work was rejected.

Endpoints: POST /v1/signup

When it happens

When	Message (as returned)	Fix (as returned)
The message names the reason: `malformed` (bad challenge or nonce format), `bad_signature` (the challenge was changed or not issued by Replyz) or `insufficient` (not enough zero bits). The challenge is not used up.	`Proof of work rejected ({reason}).`	`Get a fresh challenge from GET /v1/signup/challenge and solve it.`

What to do

Send the challenge exactly as received, with a nonce of 1–32 characters from [0-9A-Za-z]. SHA-256 of the UTF-8 string <challenge>:<nonce> must start with at least difficulty zero bits.

Example

{
  "type": "https://docs.replyz.io/errors/pow_invalid",
  "code": "pow_invalid",
  "status": 400,
  "message": "Proof of work rejected (insufficient).",
  "fix": "Get a fresh challenge from GET /v1/signup/challenge and solve it.",
  "docs": "https://docs.replyz.io/errors/pow_invalid.md"
}

See also

Quickstart

All codes: Errors.