BETA TEST — AEUC Marketplace and connected AEUC software are under active testing and may change. AEUC Empire LLC is the current legal entity identified for AEUC; other AEUC product and division names shown here are not represented as separate legal entities. Beta details

AEUC · Production key management

Keep signing authority out of public code.

This control records the current production boundary: browser wallets sign locally, Marketplace APIs receive public verification material, and protected AEUC credentials stay in server-side runtime configuration.

Browser signing boundary

PASS

Native wallet requests submit public keys and signatures; private keys are not sent to the Marketplace API.

Server-only chain credentials

PASS

AEUC Chain RPC/admin credentials are configured as server environment variables, not NEXT_PUBLIC variables.

Public environment scope

PASS

Public variables are limited to values intended for browsers, such as app URL and publishable/public keys.

Source exposure scan

PASS

Repository guard checks for embedded private-key PEM blocks, seed/mnemonic assignments, and secret-like NEXT_PUBLIC variables.

Production signing scope

PASS

Current protected managed-wallet operations remain server-side. No HSM/hardware-custody claim is made.

Permanent guard

Run npm run security:key-exposure after security-sensitive changes. A failure blocks the key-management claim until the exposure is removed.

Scope: PASS means the current AEUC deployment keeps production secrets out of client/public configuration and does not embed recoverable private-key material in tracked application source. It does not mean AEUC has an HSM, hardware wallet, multisig custody, or third-party key-management certification.