lambdaclass / lambdaclass/eth-agent
ABI tuple encoding not supported
Open
Nobody has claimed this yet.
enhancement
high-priority
- Dominant language
- TypeScript
- Stars
- 10
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Problem
Tuple types throw an error, limiting contract compatibility with many modern contracts.
Location
src/core/abi.ts:294-296
Current Code
if (type === 'tuple' || type.startsWith('(')) {
throw new Error('Tuple encoding requires component types');
}
Recommendation
- Implement tuple encoding with component types support
- Support nested tuples
- Support tuple arrays
Priority
High - Limits contract interoperability
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 at src/core/abi.ts:294-296 and trace how ABI types are parsed and encoded. Define the component-type handling needed for tuples, then verify support for nested tuples and tuple arrays. Done means tuple types no longer throw and the listed tuple forms encode successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100