Transaction Builder tuple issues
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- blockchain, frontend
Research direction
Start in the Safe Transaction Builder by importing the attached Transactions Batch.json and editing its second transaction, reproducing the failure with array inputs and complex parameters. Trace the encoding path used for batch transactions and compare it with custom data mode. Done means the parameters are accepted, encoded correctly, and the transaction is added to the batch without requiring pre-encoded data.
Written by the indexing model from the issue text.
Description
Bug description
The Transaction Builder fails to encode complex parameter specifically when trying to process array of inputs
Environment
- Browser: Chrome
- Safe Web App: Transaction Builder
- Contract Method: applyChainUpdates, seems unrelated to any particular method
Steps to reproduce
- Go to Safe Transaction Builder
- Create a new transaction and import the attached json
- Go to edit the second transaction
Expected result
- The transaction should be properly encoded and added to the batch
- The interface should accept and properly format parameters
Screenshots
Additional Information
- Current workaround is to use custom data mode with pre-encoded transaction data, Chainlink need the functionality to transparently share transactions and data
https://5afe.slack.com/archives/C06R53VAT18/p1738615187477089
- Dominant language
- TypeScript
- Stars
- 116
- Forks
- 84
- PR merge metrics
- No merged PRs in 30d
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.
More from safe-global/safe-react-apps
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
safe-global/safe-react-apps#863 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
safe-global/safe-react-apps#854 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
safe-global/safe-react-apps#852 · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
safe-global/safe-react-apps#839 · 2 comments ·
-
safe-global/safe-react-apps#834 · 2 comments · 1 assignee ·
All issues in safe-global/safe-react-apps
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·