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
Following #48 , we added increased cost-control for LiveContract dynamically binded ABI entities (eg. methods).
From an UX standpoint, there is no point in returning only the receipt for non-mutating (ContractCallQuerys) calls. The dev should be all the time interested in the query result in this case since the state of the contract will never change under these circumstances.
Are there other dev flows that we could improve for only-receipts execution?
The text was updated successfully, but these errors were encountered:
Following #48 , we added increased cost-control for
LiveContract
dynamically binded ABI entities (eg. methods).From an UX standpoint, there is no point in returning only the receipt for non-mutating (
ContractCallQuery
s) calls. The dev should be all the time interested in the query result in this case since the state of the contract will never change under these circumstances.Are there other dev flows that we could improve for only-receipts execution?
The text was updated successfully, but these errors were encountered: