Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stop using the relayer #131

Draft
wants to merge 6 commits into
base: main
Choose a base branch
from
Draft

Stop using the relayer #131

wants to merge 6 commits into from

Conversation

llunaCreixent
Copy link
Member

@llunaCreixent llunaCreixent commented Jul 25, 2022

We are looking at which parts of the code call the relayer and for what. Later we can design different solutions (without relayer) for those same tasks, and reimplement the functions.

Here there are the function we need to reimplement:

  • safe.js > predictAddress()
  • safe.js > getSafeStatus()
  • safe.js > prepareDeploy() -> probably not needed
  • safe.js > isFunded()
  • safe.js > deploy()
  • safe.js > deployForOrganization()
  • utils.js > requestRelayer() -> not needed anymore
  • utils.js > estimateTransactionCosts()
  • utils.js > waitForPendingTransactions()
  • utils.js > requestNonce()
  • utils.js > executeTokenSafeTx() -> we don't need this
  • utils.js > executeSafeTx()

If we stop using the relayer's database we will have to adjust our resources (rpc endpoints) to be able to deal with more eth_calls.

Reference for executing tx without a relayer:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants