You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We do have the ability right now to import contracts from mainnet or testnet into the sandbox and this is a great feature. An improvement would be adding the ability to copy contracts across networks or the same network.
The rationale is that this would enable a user to easily clone and deploy contracts from one account ID to another, and across networks, without having to build a WASM contract on their own or as some admin function if a project requires spinning up new contracts without the use of a factory contract.
The text was updated successfully, but these errors were encountered:
An improvement would be adding the ability to copy contracts across networks or the same network.
So to be clear, sandbox has special operations it can do that other networks cannot, like patching arbitrary contract data. A user wouldn't need to call into the constructor method for instance. In this case, if you're suggesting the ability to import contracts from say Mainnet to Testnet or Testnet to Testnet, then the only operations we're allowed here is just purely copying over the WASM bytes. We can actually already do this today with current state of workspaces-rs by utilizing the Worker::view_code and consequently calling into Account::deploy with the bytes.
The rationale is that this would enable a user to easily clone and deploy contracts from one account ID to another, and across networks, without having to build a WASM contract on their own or as some admin function if a project requires spinning up new contracts without the use of a factory contract.
If you need something like being able to import a contract into a different AccountId, then let me add an extra parameter where you can specify the designated AccountId.
We do have the ability right now to import contracts from mainnet or testnet into the sandbox and this is a great feature. An improvement would be adding the ability to copy contracts across networks or the same network.
The rationale is that this would enable a user to easily clone and deploy contracts from one account ID to another, and across networks, without having to build a WASM contract on their own or as some admin function if a project requires spinning up new contracts without the use of a factory contract.
The text was updated successfully, but these errors were encountered: