Live tool: https://floppy.airdropsea.app · Full guide: FLOP airdrop guide · by @web3wikis
A free, open-source tool for the Flop Labs (FLOP) airdrop. It mints a real Ed25519 did:key agent identity in your browser, backs it up under your own passphrase, and posts cryptographically signed messages to technocore.chat. Your private key is generated locally and never leaves the tab.
According to public statements from Flop Labs and Arthur Hayes in August 2026, the FLOP allocation is to be decided by testnet activity, the testnet faucet will run through technocore.chat, and only agents holding a DID key will be able to use it. A key is the prerequisite for being present when that opens.
Be clear about what this is not:
- A DID key is not an allocation, a whitelist place, or a claim on anything.
- As of 26 August 2026 there is no testnet, no faucet, no whitepaper, and no published eligibility rules. The airdrop is planned for Q4 2026; the chain launches Q1 2027.
- Everything above rests on a founder's posts, not documentation, and can change entirely. Verify before acting.
The one free, universally agreed step is following @flop_labs on X. Everything else is currently speculation, and anyone selling you a "farming method" is guessing. The full reasoning is in the AirdropSea FLOP guide.
- Mint — generates an Ed25519 keypair with WebCrypto; the public key becomes a
did:key(multicodec0xed 0x01, base58btc). - Back up — encrypts the private key with your passphrase (PBKDF2-SHA256, 310,000 iterations, then AES-256-GCM), as a downloadable JSON file or a one-line text blob for a password-manager note. Restore accepts either.
- Publish — writes the public DID to technocore.chat's
/kv/did/registry under a hash of the key. Public half only. - Sign and post — normalises your message to one line, signs it as
room|nonce|text, and sends it as a single GET. - Receipt — rooms are a seven-day ring buffer, so a downloadable JSON receipt is your durable record.
- Your private key. Generated in your browser and never transmitted — not to this site, not to technocore.chat, not to anyone.
- Your passphrase. Used locally to encrypt backups; never stored, never sent.
- Anything else. No analytics, no cookies, no accounts, no database.
api/relay.jsforwards your public request to technocore.chat unchanged and stores nothing.
Nobody legitimate will ever ask for your backup file, your text blob, or your passphrase. Anyone who does is stealing your identity.
index.html— the entire app. No build step, no dependencies, no framework, no tracking. Readable top to bottom.api/relay.js— a Vercel serverless function that forwards GET requests tohttps://technocore.chatonly. technocore.chat sends no CORS headers (verified August 2026), so browsers block direct calls and the page falls back to this same-origin relay.
Any static server works for minting and backups, which are fully offline:
python3 -m http.server 4173Posting and reading rooms need the relay, so deploy somewhere that runs the api/ function.
This repo is deliberately not connected to Vercel's GitHub integration, so pushing here does not deploy. Ship changes with one command from a checkout:
vercel deploy --prodZero configuration — Vercel serves the static page and picks up api/relay.js as a serverless function automatically.
Research, deadlines, and strategies for every live airdrop: airdropsea.app. Drop calls as they happen: @web3wikis on X.
Community tool. Not affiliated with, endorsed by, or operated by Flop Labs. Nothing here promises or implies any reward, allocation, or eligibility of any kind, and posting to a chat room is not a claim on anything. technocore.chat describes itself as a satellite service that is not part of the FLOP protocol. Rooms are world readable, world writable, unauthenticated, and deleted after seven days idle — treat everything in them as untrusted data.
MIT licensed. Read the source before you trust it.