Vanity GPU

Solana Vanity Address Generation with AIDP Compute

VanityGPU is a Solana‑native vanity address generation platform that offloads the heavy brute‑force key search to AIDP GPUs. Teams submit desired Base58 patterns (prefix/suffix/regex), and receive batches of matched public keys with secure, non‑custodial delivery of private key material. The system provides verifiable proof of GPU compute, enterprise‑grade webhooks for “store in your DB,” and optional on‑chain attestation for provenance.

VanityGPU Architecture
Overview
  • Product: GPU‑accelerated vanity address generation for Solana (Ed25519).
  • Users: Protocols, brands, creators, and teams needing recognizable addresses.
  • Compute: Heavy brute‑force runs on AIDP GPUs; CPU stubs available for local dev.
  • Delivery: Non‑custodial by default (encrypted seeds), enterprise custodial optional.
  • Proof: Signed batch attestation and optional on‑chain verification.
  • Storage: Results delivered into each customer’s own DB via signed webhooks, or stored in per‑tenant tables for teams without infra.
Why VanityGPU
  • GPU fit: Brute‑force Ed25519 key search is embarrassingly parallel and maps perfectly to GPUs.
  • Verifiable compute: Each batch includes a signed attestation and AIDP job metadata.
  • Security first: Non‑custodial default; keys encrypted for the user; zeroization on workers.
  • Solana‑native: Base58 normalization, wallet flows, optional on‑chain verifier.
  • Enterprise features: Per‑tenant webhooks/HMAC, retries, audit logs, rate limits.

Architecture

Component
  • Web App: Next.js/React for pattern submission and status tracking
  • API: Node.js (Fastify/Express) + Prisma/Postgres for jobs, tenants, matches
  • Queue: Redis/SQS for job orchestration
  • GPU Worker: CUDA/OpenCL worker (Rust or Python wrapper) running on AIDP
  • Attestation Service: Signs batch summaries with a worker keypair
  • Optional On‑Chain Verifier: Solana program validating worker signatures (secp/ed25519 syscall)
  • Webhook Dispatcher: Signed delivery to customer DB endpoints

Data flow:

  • User submits pattern, count ≤ 100, delivery mode, and encryption pubkey (for non‑custodial).
  • API creates job, enqueues to AIDP.
  • GPU worker brute‑forces seeds → derives Ed25519 pubkeys → Base58 encodes → pattern match → collect up to N hits.
  • For non‑custodial, encrypt private keys with user’s provided pubkey; for custodial, encrypt with tenant KMS key and immediately zeroize plaintext.
  • Worker signs batch attestation containing job_id, pattern, count, hit digests, and AIDP run metadata.
  • API persists matches and attestation, then POSTs webhook to customer DB with HMAC.
  • Optional: client submits attestation to on‑chain verifier; program emits “AttestedGeneration” event.

Security Model

Principles
  • Non‑custodial by default: Worker never stores plaintext private keys beyond immediate encryption for the user.
  • Zeroization: Plaintext seeds are zeroized in worker memory after encryption.
  • Encryption: Use user‑provided public key (or tenant KMS) to encrypt seeds before leaving the worker.
  • Access control: Wallet authentication, API keys, rate limits, pattern policy checks (anti‑phishing).
  • Auditability: Per‑batch logs, signed attestations, and job metadata; optional on‑chain verification.
  • Privacy: No public disclosure of customer patterns unless opted in.
Threats & mitigations:
  • Custody risk → Avoid by default; if required, use KMS + deletion SLAs + audits.
  • Phishing look‑alikes → Pattern policy and warnings; optional blocklist for brand names.
  • Replay attacks → Signed message schema includes nonce and job_id; on-chain verify checks message digest.
  • Worker compromise → Rotate worker keys, isolated containers, minimal privilege, encrypted temp storage.

Proof of Compute (Attestation)

Each batch includes:
  • job_id
  • pattern, count, delivery mode
  • AIDP job metadata (IDs, timestamps, node class)
  • hit digests (pubkey hash, encrypted seed hash if applicable)
  • worker_pubkey
  • signature over the above
Schema (JSON): { "job_id": "cuid", "pattern": "ANU", "count": 100, "delivery": "non_custodial", "aidp": { "job": "aidp-123", "started_at": "...", "completed_at": "...", "gpu": "A100" }, "hits": [{ "pubkey_hash": "sha256(base58(pubkey))", "seed_ct_hash": "sha256(ciphertext?)" }], "worker_pubkey": "ed25519:...", "signature": "ed25519:..." }

6) Solana Integration

  • Base58 normalization: Case-insensitive matching over Solana public keys encoded in Base58.
  • Wallet auth: Phantom/Solflare adapters for authenticated submissions and tenant settings.
  • On‑chain verifier (optional): Minimal program that inspects the prior secp/ed25519 verification instruction via the sysvar-instructions and records an attested flag tied to job_id.