Explore marking `dryCall()` as `view`

[sisyphusSmiling]

Problem Definition

The recent inclusion of CadenceOwnedAccount.dryCall enables view-only calls into EVM, but the Cadence interfacing method isn't itself designated as view. This prevents compatibility with certain interfaces that are marked as view where calls into EVM are required.

Proposed Solution

Designate EVM.drycall and CadenceOwnedAccount.dryCall as view.

Definition of Done

dryCall can be called from view context (pre/post conditions and other view method scope)

Actions Needed Before Submitting

Update ticket status using the following (remove this section once ticket created)

• What workstream does this ticket deal with? Find the appropriate 'S-' label and add that label.
• Is it a specific 'type' of ticket (ex: bug, documentation)? If yes, add that label as well.
• Is this ticket related to an overarching theme (ex: architecture, performance)? If yes, add that label as well.
• Add any/all descriptive characteristic labels needed (ex: Needs Estimation, Needs Test Cases).
• Now we should determine what release this ticket is associated with. If none, leave it blank. If it is associated with a specific release, please add it to the appropriate release.
• If this ticket is associated with a release, we want to assign it a level of importance within that release. These labels follow the standard MoSCoW method rules. We want to look at releases and then the importance of tickets within those specific releases. So the MoSCoW label is ONLY valid when it is taken in conjunction with its release.
• Assign this ticket a priority level (High, Medium, Low) via the appropriate label. These labels control the importance of the ticket within the sprint. For example, all P-High tickets should be worked on first, then P-Medium, then P-Low. This gives us an easy way to identify the order of priority for tickets within a specific sprint.

[m-Peter]

Nice catch @sisyphusSmiling , this shouldn't be difficult to change. However, it will require a EVM contract upgrade.

[bluesign]

nit: is EVM.drycall technically view though? see: revertibleRandom

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.