solang: Cross contract passes wrong `AccountId` to `seal_call` on substrate
Please refer to this posting for further information: https://substrate.stackexchange.com/questions/202/calling-the-function-of-an-other-contract-in-solidity
I posted an answer there with the results of my debugging results: Solang somehow passes the wrong AccoundId
to seal_call
. I verified that by debugging output in the node.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 15 (14 by maintainers)
Commits related to this issue
- Add testcase for issue #666 Signed-off-by: Sean Young <sean@mess.org> — committed to seanyoung/solang by seanyoung 2 years ago
- Add testcase for issue #666 Signed-off-by: Sean Young <sean@mess.org> — committed to hyperledger/solang by seanyoung 2 years ago
- skip remaining failing tests related to metadata issue #666 so we can enable them again afterwards Signed-off-by: Cyrill Leutwiler <bigcyrill@hotmail.com> — committed to xermicus/solang by xermicus 2 years ago
- skip remaining failing tests related to metadata issue #666 so we can enable them again afterwards Signed-off-by: Cyrill Leutwiler <bigcyrill@hotmail.com> — committed to xermicus/solang by xermicus 2 years ago
Got it, let me continue on there and sync back once something clicks.