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
The running of the execute_operation in the Linera smart contract is returning a typed response Self::Response. Then this answer is serialized as a Vec<u8>.
That Vec<u8> is then dropped in runtime.rs at the following line:
It is easy to avoid the dropping of this result. But the question is how to access it. In Ethereum, when a transaction is submitted with eth_sendRawTransaction, the user receives a transaction_hash. That transaction hash can then access to the result of the operation by doing eth_getTransactionReceipt. In Ethereum, if one is interested in getting the result without the result being committed then we can use more directly eth_call.
But Linera is not like Ethereum. What we could do is to redirect the result of operation to events.
The text was updated successfully, but these errors were encountered:
The running of the
execute_operation
in the Linera smart contract is returning a typed responseSelf::Response
. Then this answer is serialized as aVec<u8>
.That
Vec<u8>
is then dropped inruntime.rs
at the following line:It is easy to avoid the dropping of this result. But the question is how to access it. In Ethereum, when a transaction is submitted with
eth_sendRawTransaction
, the user receives atransaction_hash
. That transaction hash can then access to the result of the operation by doingeth_getTransactionReceipt
. In Ethereum, if one is interested in getting the result without the result being committed then we can use more directlyeth_call
.But Linera is not like Ethereum. What we could do is to redirect the result of operation to events.
The text was updated successfully, but these errors were encountered: