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

Most upvoted comments

Got it, let me continue on there and sync back once something clicks.