Skip to content

Your wallets stay yours. Your records stay traceable.

Zetra reads public wallet activity and stores the business record around it. Funds move directly between your customers and your wallets. Private keys and signing authority remain with you.

Non-custodial by design

  • Customers pay your wallet directly; funds never pass through Zetra.
  • Zetra needs only public addresses. It never asks for private keys, seed phrases or signing permissions.
  • Payments are direct NEP-141 transfers to merchant-controlled NEAR accounts. Zetra never holds customer funds or signing keys.

Wallet monitoring

  • Tokens are identified by NEAR network and NEP-141 contract account, never by symbol.
  • Payments are booked only after the network's settlement policy is met. Before that, they show as detected and change nothing.
  • If monitoring falls behind or a provider fails, Zetra pauses and says so. It doesn't fill gaps with guesses.

API security

  • API keys are 256-bit random secrets, shown once and stored only as SHA-256 hashes.
  • Test and live keys are separated; read-only scopes available; revocation is immediate.
  • Rate limits, request IDs, strict input validation and idempotency keys on every create.

Webhook verification

  • Every delivery is signed with HMAC-SHA256 over the timestamp and raw body.
  • Receivers reject stale timestamps to prevent replay; secrets rotate without downtime.
  • Delivery status reflects real HTTP attempts, and every request and response is kept.

Evidence and audit history

  • Blockchain observations, match decisions, financial events, allocations and resolutions are append-only, enforced by the database.
  • Manual resolutions record who, when, why, and the state before and after.
  • A chain reorganization or reversal adds a correcting entry. History is never rewritten.

Data isolation

  • Every query is scoped to your organization, and PostgreSQL row-level security enforces it again underneath.
  • The application connects as a non-superuser role, so isolation cannot be bypassed by a missing filter.
  • Session cookies are HttpOnly and SameSite; state-changing requests from other origins are refused.

Zetra's smart contract has an automated test suite with fuzz and invariant tests, but it has not been audited by a third party. We'll publish audit reports here when they exist. Report vulnerabilities to security@zetra.dev.