fix to field in delegation quickstart

[alexandratran]

Description

Fix incorrect to field in the redeem delegation step in the delegation quickstart.

Issue(s) fixed

Fixes #2082

Preview

https://metamask-docs-me6d08aa4-consensys-ddffed67.vercel.app/delegation-toolkit/development/get-started/delegation-quickstart/#7-redeem-the-delegation

Checklist

Complete this checklist before merging your PR:

• If this PR contains a major change to the documentation content, I have added an entry to the top of the "What's new?" page.
• The proposed changes have been reviewed and approved by a member of the documentation team.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
metamask-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 18, 2025 10:11pm

[AyushBherwani1998]

I'm not actually sure if we should document delegatorSmartAccount. It assumes the delegatorSmartAccount will be present always which is not the case, if the delegations are stored, or if delegations are used in different environment to redeem like server, it won't stand true. Hence it was using delegateSmartAccount.address. Maybe we should change the documentation for redeemDelegation rather than quickstart. WDYT?

[alexandratran]

If we keep delegateSmartAccount here, what about the issue stated in #2082?

Using the delegate's address causes the UserOperation to fail, often with no clear error unless debugged deeply. The delegation signature isn't validated on the delegate’s account, which leads to invalid operations.

[AyushBherwani1998]

It should work fine, when redeemDelegations is called on Smart Account, it just works as a proxy for delegation manager. So all the calls are passed and processed by Delegation manager.

[cursor]

Bug: Delegation Redemption Redirects to Incorrect Account

The to address for delegation redemption was incorrectly changed from the delegate's smart account to the delegator's smart account. This forces the delegate to call the delegator's account, which is logically incorrect and assumes the delegator's account is always available. This breaks redemption functionality in environments where the delegator's account may not be present (e.g., servers), as the delegate should directly execute the DelegationManager call through their own account, as originally designed.

delegation-toolkit/get-started/delegation-quickstart.md#L148-L149

metamask-docs/delegation-toolkit/get-started/delegation-quickstart.md

Lines 148 to 149 in c42da6b

	{
	to: delegatorSmartAccount.address,

Fix in Cursor • Fix in Web

---

Was this report helpful? Give feedback by reacting with 👍 or 👎