Delegate.xyz primary sources — 2026-05-07

Project status in this pass

• No standalone Delegate.xyz whitepaper or litepaper surfaced.
• The clearest source of truth was the official documentation, the delegate-registry repository README, and the ERC-5639 draft standard.
• The sources consistently frame the project as a neutral delegation registry for scoped wallet-to-wallet authority, not as a custody product or simple NFT utility wrapper.

Primary-source snapshots

1) Official docs overview

• URL: https://docs.delegate.xyz/
• Key excerpt/signals:
  • The docs say delegate.xyz links cold wallets with hot wallets so the hot wallet can act on behalf of the cold wallet “like crypto power-of-attorney.”
  • They position the system for claims, governance, gaming, login, token-gated minting, and other access-control use cases.
  • They say users can delegate for everything, a specific contract, or a specific token.
  • They also claim 150+ onchain integrations and emphasize compatibility with smart-contract wallets because authentication relies on msg.sender rather than offchain signature workflows.
• Why it mattered:
  • This is the clearest product-level evidence that Delegate.xyz is really authority-routing infrastructure for safer hot-wallet use, not just an NFT claim helper.

2) Official docs feature framing

• URL: https://docs.delegate.xyz/
• Key excerpt/signals:
  • The docs emphasize five design properties: fully onchain, fully enumerable, fully independent, fully immutable, and fully verifiable.
  • They explicitly say there are zero admin powers and no governance control because governance is treated as an attack vector.
  • They highlight the same recognizable address across multiple EVM chains via vanity-address deployment.
• Why it mattered:
  • These design choices show the project is trying to be a neutral Schelling-point registry primitive whose trust model depends on immutability and chain-portable recognizability.

3) Repository README / deployment and design philosophy

• URL: https://raw.githubusercontent.com/delegatexyz/delegate-registry/main/README.md
• Key excerpt/signals:
  • The README points to the frontend at delegate.xyz and the docs at docs.delegate.xyz, then lists finalized deployments at the same address across many mainnets and testnets.
  • It says the registry is intended as “an immutable registry contract to be deployed as a standalone primitive.”
  • It argues for no admin powers, no external dependencies, fully onchain delegation, and clear method names that distinguish delegation from ownership.
• Why it mattered:
  • This is the strongest repository-level evidence that the project wants to become shared infrastructure rather than a proprietary app-specific standard.

4) ERC-5639 draft standard

• URL: https://eips.ethereum.org/EIPS/eip-5639
• Key excerpt/signals:
  • The abstract describes a Delegation Registry protocol and ABI that links delegate wallets to a vault wallet so the delegate can prove control and asset ownership of the vault.
  • The motivation frames this as a safer alternative to forcing cold wallets to sign into dapps directly.
  • The specification defines wallet-level, contract-level, and token-level delegation plus enumeration and check methods.
• Why it mattered:
  • This makes the standardization effort explicit and shows the mechanism is meant to outlive any single frontend.

5) Raw ERC-5639 markdown

• URL: https://raw.githubusercontent.com/ethereum/ERCs/master/ERCS/erc-5639.md
• Key excerpt/signals:
  • The raw text preserves the interface definitions and makes the intended primitive especially clear: delegateForAll, delegateForContract, delegateForToken, plus a family of check... and enumeration functions.
  • The proposal repeatedly frames the vault wallet as granting read-only or authentication-oriented access rather than transfer rights.
  • It also describes chained wallet authentication as a possible extension of the model.
• Why it mattered:
  • The raw spec clarifies that Delegate.xyz is really a reusable authority schema and registry ABI, not only a UI or integration brand.

Working conclusion

Delegate.xyz is best cataloged as delegation-registry infrastructure: a neutral, immutable control plane for publishing scoped hot-wallet authority so downstream apps can read delegated rights without taking custody or forcing repeated cold-wallet interaction.