Nemequene

Security

How the service is built, stated plainly. Operated by Nemequene LLC (in formation) (Rhode Island, USA). Effective 2026-08-01.

Non-custodial by construction

No private key exists anywhere in our systems. The service holds only watch-only public keys, so theft of our servers cannot move a single satoshi. This is not a policy — it is an architectural absence.

Verifiable, tamper-evident records

Every successful API response carries a cryptographic proof: events live in a hash-chained, append-only log with an RFC 6962 Merkle tree over it, and the tree root is anchored daily in an independent signed store. You can verify inclusion, consistency, and completeness of your own records without trusting us — a missing or altered event is mathematically demonstrable.

Credentials

Transport

TLS 1.3 with a publicly-trusted certificate and automated renewal. Plain HTTP serves nothing on the TLS port. Webhook endpoints must be HTTPS — we refuse to sign content delivered over a transport that cannot protect it.

Minimal surface

The language, compiler, HTTP server, TLS stack, datastore, and ACME client are our own code with no third-party runtime dependencies — the supply-chain attack surface most services inherit simply is not present. Our subprocessor list is: our hosting providers. That is the whole list.

Operations

Deployments pass automated verification gates before and after going live; daily sweeps re-verify the whole surface and alert on any failure; the business ledger replicates continuously to an independent machine. Incidents are written up honestly and the write-ups drive fixes.

Reporting a vulnerability

We want to hear it. Contact us through your portal account, and we will acknowledge within two business days. Good-faith research within the law is welcome; we do not pursue researchers who report responsibly.