lambdaclass / lambdaclass/eth-agent
Add EIP-712 typed data signing
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 10
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Problem
Only raw message signing appears supported. Many dApps and protocols require EIP-712 typed signatures for:
- Permit (gasless approvals)
- Meta-transactions
- Off-chain signatures
Recommendation
- Implement
signTypedData(domain, types, value)on Account - Expose in AgentWallet
- Add safety checks for signing requests
Use Cases
- ERC-2612 Permit for gasless approvals
- OpenSea/NFT marketplace signatures
- DAO governance votes
Priority
Feature request
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating Account's existing raw message-signing implementation and the AgentWallet interface. Define how signTypedData should accept the domain, types, and value, expose it through AgentWallet, and determine the safety checks required for signing requests; done means typed-data signing supports the listed use cases and its behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100