There's already a Solana address tied to your Twitter handle. You didn't create it. You can't delete it.

Sounds like a stretch. It isn't. Here's the actual mechanism.

Every u/handle already has an address - Twitter, Telegram, doesn't matter

Solana lets you derive an address deterministically from any seed data:

address = derive(program_id, ["escrow", "twitter", "your_handle"])
address = derive(program_id, ["escrow", "telegram", "your_username"])

That address exists mathematically the second it's computable - no transaction, no signup, no action from you required. It's not created. It's discovered. Every Twitter handle, every Telegram username, has one of these sitting there right now, whether anyone's ever touched it or not.

The part that breaks people's intuition

Send SOL to that address and it just works. The System Program auto creates a bare account holding lamports the instant funds land. No init instruction, no prior setup, no cooperation needed from the address "owner" - because there is no owner yet. Just math.

So yes - literally right now, someone could know your u/handle or your Telegram u/username, derive that address, and send you SOL. It would sit there. You wouldn't know unless you checked. This is the primitive I built a payments system on top of.

Twitter and Telegram need very different proof mechanisms

The interesting part isn't just deriving the address - it's proving ownership later so the right person can claim what landed there.

• Telegram actually signs data natively. Their Mini App / Login Widget produces Ed25519-signed payloads, verifiable on-chain against Telegram's own published public key. No third party needed at all - Telegram IS the attestor. This turns out to be the more trustless path of the two.
• Twitter has no equivalent. There's no native signature you can check on-chain. So proving "I own this handle" without Twitter's cooperation needs a different trick: the user posts a public tweet, and we use Reclaim's zkFetch to generate a cryptographic proof that a specific public tweet really says what we claim - attestor-signed, verifiable on-chain. No login, no session, no credentials anywhere near the flow. It's just proving a public HTTP response is real, the same as proving any other public webpage's content.

Same underlying idea (prove handle ownership > unlock funds sitting at the derived address), completely different trust models depending on whether the platform signs things itself.

This only works because of how Solana is built

None of this is possible as a bolt-on - it's a direct consequence of Solana's account model. Addresses are cheap to derive, cheap to create, and the runtime itself handles the "does this account exist yet" problem for you on the SOL side. Combine that with sub-cent transaction costs and you get something that would be prohibitively expensive to run practically anywhere else: an address for every u/handle on the internet, sitting there, ready to receive value, costing nothing until someone actually uses it.

I've been building a protocol on top of this - letting you send crypto to literally any Twitter or Telegram handle, claimed later via proof of ownership, no wallet required upfront. Happy to go deeper on either verification path if people want it - the Telegram one especially is a neat trick most people don't realize is possible.