Vanity Generator = Onboarding + Benchmark Baseline
Why This Helps You
Run distributed compute and still get deterministic output you can trust.
Guarantees You Get
Deterministic execution, cross-worker consistency checks, and auditable submission receipts.
How To Use It
Choose app, configure platform + app fields, review exact IO contract, submit.
Module Source
Select a curated app for fast onboarding, or upload your own WASM module.
Frictionless Start
Solana Vanity Address Generator
Upload a deterministic WASM artifact and define expected output shape in step 3 before submitting.
What Happens
Execution chain that users can reason about.
1. Scheduler validates runtime + policy.
2. Workers execute deterministic tasks.
3. Consensus output and settlement proof are returned.
No hidden steps: each run exposes inputs, target runtime, and expected output class before submission.
Configure Platform + App Fields
Platform envelope is separated from app-specific fields so users can configure a single app without guessing.
Platform Job Envelope
These values apply to scheduling and execution regardless of app.
App Configuration: Solana Vanity Address Generator
These fields define what this specific app will execute.
Search space is a Vanity app field. Configure it here when running the vanity generator.
No Predefined Search Space For This App
Input Clarity
Make the contract obvious before run.
Platform: Job envelope + runtime + scheduler destination.
App: Solana Vanity Address Generator
Input: Prefix and counter range (+ optional seed handling mode).
App Field Summary: Vanity search space: prefix "So1" from counter 0 to 1000000 with chunk size 50000 across 5 workers.
Output: Matching address, keypair artifact, and deterministic execution proof envelope.
Expected Behavior: Workers execute deterministic counter chunks; scheduler returns consensus output and settlement evidence.
Use this as the canonical benchmark to normalize compute/fee multipliers across workers.
Review Contract Before Submission
Users should be able to answer: what goes in, what comes out, and what the network will do.
Input
Platform envelope: job name, runtime id, scheduler URL, execution policy.
App fields: Vanity search space: prefix "So1" from counter 0 to 1000000 with chunk size 50000 across 5 workers.
Output
Matching address, keypair artifact, and deterministic execution proof envelope.
What Will Happen
Workers execute deterministic counter chunks; scheduler returns consensus output and settlement evidence.
Onboarding Path
Submitting
Submission Accepted
Submission Error
Fix Before Submit
Cost + Runtime Estimate
Preview based on selected profile.
| Mode | preset |
| Execution | distributed-insecure |
| Est. Runtime | ~12s |
| Est. Fee | Generating |