How the catalogue and memo demo fit together
In brief
MintLab is an offline Solana vanity-address catalogue with a controlled memo demonstration. Search for a prefix or suffix, select an address, and send a sponsored memo signed by that address. The keys stay with the demo backend.
The released generation is 20260916-rtx3080-one-hour-plus-short-cpu-v1: an RTX 3080 (sm86) GPU run of one hour (3,600.151 seconds, starting 2026-09-16 18:31:34.979 UTC) plus bounded CPU work for short targets.
What was actually generated
- 570 deduplicated dictionary targets: 500 English entries plus crypto terms.
- 41 short targets were handled by CPU; 529 targets by GPU.
- The importer verified retained public keys and signatures, checking 911 input rows and retaining 885 literal records: 400 prefix and 485 suffix records, with 885 unique addresses.
- 26 records were excluded by the literal-match filter. These figures describe this run, not exhaustive coverage or a mining-speed guarantee.
The English source is the top-english-wordlists project, attributed under CC BY 3.0 Unported. Crypto terms and source hashes are recorded in the dictionary manifest.
Generation and import
CPU and CUDA workers generate Ed25519 keypairs and test literal Base58 prefix/suffix variants. The worker records target position and case policy; it does not substitute lookalike characters. An encrypted private vault holds the raw scalars. The public catalogue contains addresses and provenance only.
Import verifies each address against its retained scalar and verifies the a test-message signature before a record can be selected. This is an integrity gate for the catalogue, not a cryptographic audit of the miner or the resulting key.
Memo and sweep flow
The backend controls the fee payer and required vanity signer. A visitor wallet does not sign or fund the operation. Funding is a separate confirmed transaction. After funding, the vanity signer submits one transaction containing the Memo program instruction and a sweep of the remaining lamports to the approved recovery destination. Prepared bytes and signatures are persisted before broadcast so a lost response can be recovered by operation ID.
Network fees are not refunded. Funding and memo/sweep fees are accounted for by the backend’s cumulative lamport cap; failed or ambiguous sends remain recoverable rather than being silently retried with new keys.
A verified example is the mainnet memo-and-sweep transaction. Its memo says “MintLab portfolio demo: this vanity address signs the memo.”
Operational boundaries
The demo is backend-controlled and disabled unless its encrypted vault, sponsor signer, pinned mainnet configuration, fee cap, RPC, confirmation, and recovery checks are present. It does not expose private keys, accept arbitrary visitor destinations, or promise a particular target length. A catalogue match is a generated record, not a recommendation to use the address for funds.