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

Feature: Accounts in Devnet should not need to deploy a contract before they can interact with it. #168

Open
Nonnyjoe opened this issue Oct 20, 2023 · 1 comment

Comments

@Nonnyjoe
Copy link

Feature Request Summary

Once a contract is declared and deployed by a single devnet account, other accounts should be able to interact with that deployed account.

Detailed Description

At the moment once a contract has been declared and deployed by one of the accounts made available on devnet, on switching to a different account the interact section displays a message that the contract had not been deployed yet, thereby prompting the new address to deploy a new instance of the compiled contract. This is an issues especially during contract testing where its required for multiple account to interact with the contract in order to execute certain functionalities (eg, contract ownership transfer) as at this moment when using Plugin version: v0.2.3 only the single account that deployed the contract has access to interact with the contract.

UI Update's

  1. All contracts deployed by a unique user should be visible regardless of the account used for deployment.
  2. The Interact section should list all deployed contract and buttons to interact with them similar to the way transaction section displays individual transactions.

Desired Behavior

  1. Users should be able to utilize multiple devnet accounts to interact with a contract deployed by single devnet account.

Examples from Other Projects

  1. Remix Deploy & Run plugin [https://remix-ide.readthedocs.io/en/latest/udapp.html]
    • Screenshot/GIF: [https://i.ibb.co/YQzWPqK/issue.png]
@JorikSchellekens
Copy link
Contributor

Yes! This would be an excellent feature. We may need to update the planned UI changes to incorporate a clean way to manage "deployed assets". @PaulUXD can you think about this when you have some time?

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

No branches or pull requests

2 participants