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
Yesterday, dhawkmoon in the Hyperledger Iroha community requested information on Iroha 1 smart contract support while working on a legacy Iroha 1 Burrow integration for smart contracts using Solidity.
dhawkmoon asked if there is a way to get the login of smart contract caller (foo@bar) inside a smart contract to check permissions based on the caller's role (to make a delegation call to the service contract).
There's an alternative question in case that does not work: is it possible to retrieve the caller's account using the msg.sender property?
@baziorek replied that Iroha 1 has an API that wraps Iroha commands and queries.
He said that when a programmer uses multiple commands wrapped that way, they will be unable to find out which command failed and why. He had also recommended this page to dhawkmoon.
If you have time to comment, please do, @iceseer. Thanks in advance for your comments on this request.
The text was updated successfully, but these errors were encountered:
Yesterday,
dhawkmoon
in the Hyperledger Iroha community requested information on Iroha 1 smart contract support while working on a legacy Iroha 1 Burrow integration for smart contracts using Solidity.dhawkmoon
asked if there is a way to get the login of smart contract caller (foo@bar
) inside a smart contract to check permissions based on the caller's role (to make a delegation call to the service contract).There's an alternative question in case that does not work: is it possible to retrieve the caller's account using the
msg.sender
property?@baziorek replied that Iroha 1 has an API that wraps Iroha commands and queries.
He said that when a programmer uses multiple commands wrapped that way, they will be unable to find out which command failed and why. He had also recommended this page to
dhawkmoon
.If you have time to comment, please do, @iceseer. Thanks in advance for your comments on this request.
The text was updated successfully, but these errors were encountered: