Service status

We do not publish a status badge, because we do not yet have the uptime history to back one up and a green dot nobody measures is worth nothing. What we have instead is a live health endpoint you can call yourself, at any time, without an account or a key:

GET https://nemequene.ink/health

What it tells you

• ok — 1 when the API is answering. If you cannot reach the endpoint at all, that is your answer.
• mode — which chain this instance settles on: mainnet for the real thing, signet or regtest for test instances.
• custody — always none. It is stated in the health check because it is the one property that must never quietly change.
• own_validation.height — the block height our own validator has reached, and own_validation.oracle_tip the height it is comparing against.
• own_validation.lag — how many blocks behind we are. Zero is normal. A number that keeps growing means confirmations will be late.
• own_validation.fresh — 1 when our chain view is current. If this is 0, treat confirmation times as unreliable until it recovers.

What we promise, and what we do not

• No SLA on the free sandbox plan. It is for evaluation and it may be restarted at any time.
• Deploys cause a brief restart. In-flight requests can fail for roughly a second. Every state-changing call is idempotent for exactly this reason: retry it with the same idempotency key and you will not double-charge anyone.
• Your money is not affected by our downtime. Payments go from your customer to an address derived from your own key. If we are down, the transaction still confirms on the bitcoin network — we just have not noticed it yet, and we will when we come back.

Telling us something is wrong

Sign in and use the message box on the Contact tab. If you cannot sign in, that is itself worth telling us however you can reach us.