Origin
The full creation pipeline — from sealed enclave to live token.
Step 01
ENCLAVE INITIALIZATION
An EigenCloud TEE enclave (EigenCompute) was initialized. Once sealed, the enclave is cryptographically locked. No external access. No SSH. No admin panel. The enclave memory cannot be read or extracted.
Step 02
WALLET GENERATION
Inside the sealed enclave, a fresh Solana keypair was generated. The private key was created and stored entirely within the TEE. The key has never existed outside the enclave and cannot be exported.
Wallet: HWZD...LW8G View on Solscan →
Step 03
TOKEN PARAMETERS
The token parameters were defined: Name: Sovereign | Ticker: $Sovereign | Supply: 1,000,000,000. All configuration was handled within the TEE environment.
Step 04
ON-CHAIN DEPLOYMENT
The token deployment transaction was signed inside the TEE and broadcast to Solana mainnet. The transaction was executed entirely within the sealed enclave.
Step 05
ATTESTATION
EigenCloud generated a cryptographic attestation proving: the code running in the enclave was unmodified, the wallet was generated inside the TEE, the deployment transaction was signed inside the TEE, and no external input was received during the process.
Attestation: 0xfe82...3260 Verify Attestation →
Step 06
SEALED
The enclave remains sealed and cannot be accessed or modified. The private key will never leave the TEE. $Sovereign exists on-chain with its deployer key permanently secured inside the hardware enclave.