Summary: Delegate.xyz is delegation-routing infrastructure. The important point is that it publishes reusable wallet-to-wallet authority relationships onchain without turning the registry itself into an execution layer.
What it does:
Lets a vault wallet delegate rights to a hotter wallet at whole-wallet, contract, or token granularity
Publishes those delegations onchain through an immutable registry that dapps and contracts can query directly
Exposes enumeration methods so integrators can read delegations without reconstructing state only from events
Uses the same recognizable deployment address across many EVM chains via CREATE2-style deployment patterns
Supports use cases like governance participation, token-gated access, claims, minting, gaming, and wallet-auth flows while explicitly not transferring custody
Positions the registry as a shared neutral primitive so new projects can inherit existing cold-wallet → hot-wallet delegation relationships
Key claims:
The docs describe delegate.xyz as a way to link cold wallets with hot wallets so the hot wallet can act on behalf of the cold wallet “like crypto power-of-attorney,” which is the clearest sign this belongs in the corpus as authority-routing infrastructure rather than a single consumer app
The docs say the granular permission model supports delegating for everything, a specific contract, or a specific token, showing that the project is really a scoped delegation registry instead of a blanket wallet proxy
The official README says the registry is intended as “an immutable registry contract to be deployed as a standalone primitive,” which is a strong indicator that the project is aiming for neutral shared infrastructure status
The README and docs both emphasize fully onchain operation, no hidden relay of offchain signatures, and compatibility with smart-contract wallets because authentication is based on msg.sender, not private-key signature conventions
The docs say the registry is fully enumerable, meaning integrators can retrieve complete delegation sets onchain rather than relying only on event parsing, which lowers integration friction and makes the registry more useful as a common coordination layer
The docs and README repeatedly stress zero admin powers, no governance control, and immutability, explicitly treating governance as an attack surface rather than a feature
The README highlights deployment at the same vanity address across many chains, which matters because recognizability and repeatability make the registry easier for users and integrators to treat as a Schelling-point primitive
ERC-5639 frames the same interface as a standard for granting wallet-, contract-, or token-level permissions to delegate wallets, reinforcing that Delegate.xyz is not only a product surface but also a live standardization effort around reusable delegation semantics
Whitepaper: No standalone Delegate.xyz whitepaper or litepaper surfaced in this pass. The clearest current source of truth was the official docs, the delegate-registry repository README, and the ERC-5639 draft standard collected in ../whitepapers/delegate-xyz-primary-sources-2026-05-07.md.