launchonkeys.com
“Keys: launch coins, earn with letter keys”
Tech check
What the site says about itself, next to what its public page actually loads. Facts only, no verdict: you decide.
What it is
- The site describes itself as: “Hold a letter key, earn from every coin with that letter in its ticker. Launch on Keys.”E2
- It's built with React (common tools for building web apps).E20
- In your browser it can copy text to your clipboard and saves small bits of data in your browser.E23E24
- It has sections such as /launches, /discover, /keys, /race, /docs and /create.E37
- While loading, it called 6 endpoints on its own servers, such as /__l5e/trackevents, /engine/config, /config and 3 more.E25E26E27E28
Where your data goes
Crypto & walletsConnect wallets, read blockchains or fetch token prices. 2
| auth.privy.io | Privy: embedded wallets and wallet login | 3×E12 |
| explorer-api.walletconnect.com | WalletConnect / Reown: connects mobile and browser wallets | 1×E11 |
Error & performance monitoringReport crashes and speed to the developers. 1
| csp-report.browser-intake-datadoghq.com | Datadog: error and performance monitoring | 1×E13 |
Crypto and wallets
How key features work
Connecting your wallet
It connects to crypto wallets using Privy (wallet login) and WalletConnect / Reown. Connecting shows the site your wallet address; it doesn't move funds by itself.E21E22E12E11
Privy (wallet login)WalletConnect / ReownCookies and storage
Names only. We never store the values.
| Cookie | Set for | Kept | Whose |
|---|---|---|---|
| __dplE14 | launchonkeys.com | about 1 days | the site |
| __cf_bmE15 | launchonkeys.com | about 0 days | the site |
| __cf_bmE16 | privy.io | about 0 days | other company |
| _cfuvidE17 | privy.io | until you close the browser | other company |
localStorageE18: privy:caid, base-acc-sdk.store, privy:sent:cmupbrm2z015w0cl6rpmvo403:5030197799141770
IndexedDBE19: base-acc-sdk
Pages and API calls
Pages it links to
//launches/discover/keys/race/docs/create/coin/portfolioEndpoints
Called while loading (seen) or named in the code (code).
| launchonkeys.com/__l5e/trackevents | seenE25 |
| api.launchonkeys.com/engine/config | seenE26 |
| api.launchonkeys.com/config | seenE27 |
| api.launchonkeys.com/collect | seenE28 |
| api.launchonkeys.com/stats | seenE29 |
| api.launchonkeys.com/launches/ticker | seenE30 |
| /api/v1/token_price | codeE31 |
| /api/v1/farcaster/signer/status | codeE32 |
| /engine/config | codeE33 |
| /engine/image | codeE34 |
| /engine/launches/prepare | codeE35 |
| /engine/trades/prepare | codeE36 |
Evidence
Every sentence above points to one of these. Code references show the file, line:column and the short identifier that matched, never the site's code itself.
Limits
- We only see what your browser sees: code and requests on a first visit, without logging in or accepting cookie banners. What the servers do with data is invisible from outside.
- Site code is usually minified (compressed), so names are partly lost and some code may be only partly analysed.
- Some trackers only load after you accept cookies or log in, so the real list can be longer.
- We visited from a server in the United States. Sites load different trackers and cookie banners in different countries (visitors in the EU usually get a consent banner first).
- The tech check compares the site's own words with what its public page loads. Work done on servers, in private code or in separate apps isn't visible here, so 'nothing found' means not visible on the public page, not that it doesn't exist.
- This text was written from fixed templates because no AI writer was available. It uses exactly the same evidence.
- The code reader hit its size budget on parts of 51 large bundle file(s); those parts weren't fully analysed.
Facts, not judgements: this page describes what the code and traffic show, not anyone's intent. Not financial advice. Case id 15PI8DyO.