- Update dbis_core, cross-chain-pmm-lps, explorer-monorepo, metamask-integration, pr-workspace/chains - Omit embedded publish git dirs and empty placeholders from index Made-with: Cursor
2.2 KiB
2.2 KiB
Thirdweb Account Abstraction Support
Purpose: Define the repo's concrete Thirdweb execution policy for ERC-4337, EIP-7702, gas sponsorship, and x402 across the chains relevant to GRU and Chain 138.
Machine-readable source: ../../config/thirdweb-account-abstraction-support.json
Verifier: ../../scripts/verify/check-thirdweb-account-abstraction-support.sh
Bottom line
The repo now treats Thirdweb account abstraction as a dual-mode surface:
ERC-4337is the required compatibility baselineEIP-7702is the preferred execution mode where the chain and Thirdweb stack support itx402remains a7702-specific settlement rail, not a generic4337fallback
For Chain 138 specifically:
ERC-4337remains the current default execution mode in the policy matrixEIP-7702is tracked as supported target capabilityx402is enabled only through the GRU V2 USD payment tokens that exposeERC-2612andERC-3009
Chain 138 payment tokens
The Chain 138 x402-compatible payment tokens are:
cUSDT V2—0x9FBfab33882Efe0038DAa608185718b772EE5660cUSDC V2—0x219522c60e83dEe01FC5b0329d6fA8fD84b9D13d
These contracts are live and expose:
permit/ERC-2612transferWithAuthorizationreceiveWithAuthorizationERC-5267domain introspection through the V2 token base
See also:
Verify
Run:
bash scripts/verify/check-thirdweb-account-abstraction-support.sh
Optional JSON output:
bash scripts/verify/check-thirdweb-account-abstraction-support.sh --json
This verifies:
- dual-mode account abstraction is enabled in the matrix
- Chain 138 explicitly lists both
ERC-4337andEIP-7702 - Chain 138 keeps
ERC-4337as the current default until full7702confirmation - Chain 138 x402 stays pinned to
eip7702 - at least one Chain 138 payment token is listed as x402-compatible
- Ethereum Mainnet is also represented as dual-mode