X (Twitter)

The X (formerly Twitter) Legacy Identity Provider (LIDP) integrates one of the web's largest public social graphs into the open Nostr and Lightning ecosystem.

Identifier Format

The canonical identifier for X is the user's handle (username), stripped of the @ symbol and lowercased.

• Raw Format: handle (e.g., jack)
• Resolved URI: x:jack

Privacy Model: Public

Like Discord, X is treated as a Public identity.

In the user's Identity Connection event, the profile content will typically publish the raw handle in plaintext to enable global search and discovery across Zapf clients. The connection key maintains protocol compliance as a hash of the identifier.

Verification Flow (OAuth)

Zap Settlement Providers verify X ownership using OAuth 1.0a or OAuth 2.0.

1. Scope: tweet.read, users.read
2. Endpoint: https://api.twitter.com/2/users/me
3. Evidence: Yes. Modern X OAuth 2.0 produces standard bearer tokens that can be shared across ZSPs.

Expected Profile Resolution

When a client resolves an X identity, the Zap Settlement Provider fetches standard metadata (such as the username, display name, and profile picture). This enriches the native Nostr client UI, allowing users to verify they are zapping the correct X personality.

Evidence Sharing Support

Because X supports OAuth 2.0, it produces standard bearer tokens. The ZSP encrypts this token into a portable evidence payload using secure encryption ↗.

This allows the user to securely execute Evidence Sharing with other ZSPs in the ecosystem without ever needing to re-authenticate with X.