Security architecture

Trust comes from visible boundaries.

MoonKey is designed so an ordinary employee, dashboard, application, database service, or general backend cannot unilaterally spend a user's assets.

01
Application trust

Exact origins, redirects, bundle IDs and active status.

02
Authentication

Issuer, audience, nonce, proof and assurance.

03
Authorization

Tenant ancestry, app authority and current entitlement.

04
Transaction safety

Canonical decode, simulation, policy and risk.

05
Signing isolation

Minimal interface, replay defense and separated broadcast.

ISOLATED PLANENo general public ingress · constrained egress · separate release gates

Claims stay behind evidence.

MoonKey is pre-alpha. Production wallet safeguards and end-to-end technical acceptance are incomplete. Review and release are owner-operated.

Real-value release gate closedInternal technical acceptance pending
Security invariants

Properties the system must preserve.

These are testable boundaries, not marketing adjectives.

01

A revoked application cannot initiate new signatures.

02

An application cannot sign outside its effective policy.

03

An unrelated ecosystem cannot discover a wallet through email equality.

04

A base-tier organization cannot obtain ecosystem scope through lower-level APIs.

05

A subscription change cannot destroy, re-key, or orphan a wallet.

06

A dashboard administrator cannot obtain private key material.

Ownership beyond the platform

Recovery and portability are security features.

Hardened export, signer rotation, multi-factor recovery, explicit continuity access, and migration adapters keep ownership from becoming lock-in.

MoonKey signerUser-controlled ownerPortable account
The next chapter is yours

Build a world.
We’ll connect it.

Explore the foundation for your next ecosystem.