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

Document how to call magic contracts directly with a web3 library #1676

Open
Dr-Electron opened this issue Aug 30, 2024 · 3 comments
Open

Document how to call magic contracts directly with a web3 library #1676

Dr-Electron opened this issue Aug 30, 2024 · 3 comments
Labels

Comments

@Dr-Electron
Copy link
Collaborator

Is your feature request related to a problem? Please describe.

Some functions like the once related to allowance need to be called by the user directly so we should mention how to do this with libs like ethers and web3 (one should be enough)

Describe the solution you'd like

Ideally this is just another Tab beside Solidity | Web3 | Testing | WASP CLI

@HighGecko
Copy link
Contributor

Both alvaragar and I used Remix when starting out. I personally find it much more intuitive compared to Hardhat, and simplier than also needing to build a frontend to use Web3/Ethers/Viem.

Documentation could provide simple instructions to:

  1. Sign in to Remix,
  2. Copy & Paste Magic Contracts or link github repo into File Explorer.
  3. Compile ISCSandbox.sol under Solidity Complier
  4. Under Deploy & Run Transactions, select "Injected Provider - Metamask" under Environment.
  5. Type 0x1074000000000000000000000000000000000000 as the input for At Address and click the button.
  6. Potentially provide example inputs for using Allow, getAllowance and send

@HighGecko
Copy link
Contributor

iscsandbox

@Dr-Electron
Copy link
Collaborator Author

Remix uses ethers or web3 in the backend anyway. For the how-tos we will not use a Remix IDE. As that is already a layer above. Remix, Metamask and so one are way better described in other tutorials imo. But this is an iterative process and we will find the best way to solve this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Product Backlog
Development

No branches or pull requests

2 participants