[TX Builder] Loading transaction batch from other tx/txs
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- blockchain, frontend
Research direction
Start by locating the TX Builder entry point and its existing transaction-loading and batching flow; the issue names no specific files or tests. Trace how a safeTxHash could load executed or pending transactions, including from other Safes, and define done as editable single loads, additive batching, and flattened MultiSend calls without nested batches.
Written by the indexing model from the issue text.
Description
Overview
We would like users to be able to replay txs, so tx builder can load transactions using the safeTxHash. Also for advanced users loading multiple executed or pending transactions and batching them together in a single transaction will be very useful.
Goals
- Enable users to load a single tx into the tx builder (executed or pending, or even txs from other Safes).
- Enable users to batch together multiple txs into the builder (executed or pending, or even txs from other Safes).
Requirements
- Add a new button to load data from a tx (for a first version just copying and pasting the
safeTxHashwould be enough). - Tx data is loaded into the builder and can be modified, or a new transaction can be loaded and it will be added to the batching.
- If trying to batch multiple transactions that are already batched, don't do nested calls to Multisend, just refactor the calls to do a single call to MultiSend with all the data.
Screens
Links
- 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 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
safe-global/safe-react-apps#835 ·
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 ·