docs: document EIP-2612 permit and Permit2 in ERC20Vault - #29
Open
ggonzalez94 wants to merge 1 commit into
Open
Conversation
Proposal0023 (taiko-mono#22083) upgraded the L1 and L2 ERC20 vaults with the permit entrypoints added in taiko-mono#22093, so ERC-20 bridging can now be done in a single signed transaction instead of `approve` + `sendToken`. This adds: - A new "Approval-free ERC-20 sends" subsection in the bridging page covering `sendTokenWithPermit` (EIP-2612) and `sendTokenWithPermit2` (Permit2 at `0x000000000022D473030F116dDEE9F6B43aC78BA3`), including when to reach for each. - SKILL.md now lists all three ERC-20 send paths in the "Bridge tokens (programmatic)" recipe so agents don't default to `approve` + `sendToken` when a permit path fits. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0167RsqRvufRULhpZBMoQkRx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Proposal0023 (taiko-mono#22083) upgraded the L1 and L2
ERC20Vaultproxies to the implementations that add EIP-2612permitand Permit2 support (taiko-mono#22093). This means ERC-20 bridging can now be done in a single signed transaction instead ofapprove+sendToken, and the docs did not mention it — including the SKILL.md recipe agents follow to bridge programmatically.Changes
docs/pages/protocol/bridging.mdx: new subsection Approval-free ERC-20 sends:sendTokenWithPermitandsendTokenWithPermit2under Token Bridging. Explains when to reach for each entrypoint, notes that the message shape, quota accounting and refund path matchsendToken, gives the canonical Permit2 address (0x000000000022D473030F116dDEE9F6B43aC78BA3), and flags theVAULT_PERMIT_NO_ALLOWANCEfailure a griefed EIP-2612 permit will surface.docs/public/SKILL.md: the Bridge tokens (programmatic) recipe now lists all three send paths (sendToken,sendTokenWithPermit,sendTokenWithPermit2) with a one-line guide for each, and both mainnet contract-address tables now include the Permit2 address. This keeps agents from defaulting toapprove+sendTokenwhen the token supports permit or when the user already has a Permit2 allowance.Notes
_SEND_ETHER_GAS_LIMITfrom 35,000 → 135,000. That constant is not documented anywhere in the docs today, so I did not add it here.bridge.taiko.xyzcan pick up the new copy naturally without changes here.🤖 Generated with Claude Code
https://claude.ai/code/session_0167RsqRvufRULhpZBMoQkRx
Generated by Claude Code