Custom tx: Fetch implementation abi when contract is proxy

Open
#818 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
frontend

Research direction

Start at the custom transaction builder and its contract ABI-fetching flow. Trace how proxy contracts are detected and how implementation ABI functions are parsed; done means proxy contracts use the implementation ABI and the builder shows that detection and fetching occurred.

Written by the indexing model from the issue text.

Description

What is the feature about

When using the custom tx builder and attempting to interact with a proxied contract the Abi is fetched for the proxy contract.

Rather we should detect that the contract is a proxy and additionally fetch the abi for the proxy's implementation.

The list of requirements

  • detect that input contract is a proxy via interface
  • fetch implementation abi
  • Parse functions from the implementation abi

Designs/sketches

Should largely happen behind the scenes. Show a message that we've detected a proxy and fetched the implementation abi.

This would greatly enhance usability for proxy contracts via the custom transaction builder.

Dominant language
TypeScript
Stars
116
Forks
84
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from safe-global/safe-react-apps

All issues in safe-global/safe-react-apps

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.