Clarify and Document the Process for Static Calls in Casper

[devendran-m]

Problem Statement/Feedback (from Xord):

The process for performing static calls from contracts is also unclear. Suppose we have complex calculations, and we want clients to read results from a contract without initiating a transaction, as no state changes are involved. How can this be achieved in Casper? This is straightforward in EVM and Solana, yet the equivalent approach in Casper is not documented.

User Story:

As a developer building on the Casper Network,
I want a clear explanation and documentation of how to perform static calls from contracts,
so that I can enable clients to read results from a contract without initiating a transaction when no state changes are involved, similar to the straightforward approaches in EVM and Solana.

Acceptance Criteria:

• The documentation provides a dedicated section on performing static calls in Casper.
• A clear explanation is given on how to execute complex calculations within a contract and make the results accessible to clients without requiring a transaction.
• Practical examples and code snippets demonstrate the implementation of static calls in Casper.
• Comparisons with similar processes in EVM and Solana are included to help developers transitioning from those platforms understand the differences and adapt.
• Best practices for designing contracts with efficient static calls are outlined.
• Developers can implement and use static calls effectively after referencing the documentation without requiring additional clarification or support.