Add the mostreadable &accessible
user‑identifiers.

Two things happen, and they are separate. Linking. A person proves they control a social account and connects the wallet they already use. From then on the handle points at that wallet's address. Nothing about the wallet changes and nothing leaves it — the proof and the connection both happen inside the user's own wallet popup. [ How linking works → ] Sending. An application looks up the address by handle and sends to it the way it would send to any address. Resolution runs on LibID, the open protocol underneath handles.link — handles.link is one bridge built on it, not the protocol itself. [ How resolution works → ] The full spec is public: [ Read the spec → ]

X, Google and Github out of the box. Any other OAuth/OIDC iDP (identity provider) can be added through libID’s extensible library. You can add and contribute support to any new one in a few prompts.

Out of the box Ethereum, Base, Polygon, MegaETH, and Eden with any EVM-compatible wallet. Support for non-EVM networks is planned, and the established architecture was meticulously designed around that.

No. handles.link is an identity bridge, not a wallet. A handle points to the linked wallet the user already controls, and everything that touches that wallet happens in the user's own popup. There is no path through our system that reaches key material or funds.