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
There are a few issues in the saftey during implementation on HandleCallMessage in java and solidity.
In both cases the caller must always be the xCall Addresss.
On the java side the dapp must also verify that the _from is the NetworkAddress(previously BTP addresss in V1) of xCall on ICON
On the solidity contract apart from verifying the caller, the dapp must verify that the _from is the network address of the Java contract to prevent anyone from voting
The text was updated successfully, but these errors were encountered:
There are a few issues in the saftey during implementation on HandleCallMessage in java and solidity.
In both cases the caller must always be the xCall Addresss.
On the java side the dapp must also verify that the _from is the NetworkAddress(previously BTP addresss in V1) of xCall on ICON
On the solidity contract apart from verifying the caller, the dapp must verify that the _from is the network address of the Java contract to prevent anyone from voting
The text was updated successfully, but these errors were encountered: