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
Those abstract contract types, define interfaces with a list of methods callable on the contract. Some are internal, but others are external, view, pure, and payable, meaning that they can be triggered by transactions coming from the outer world.
We want our client to expose all of those.
I added some of them in #3. There is more to be added, just follow the way I did it: one abstract contract -> one file -> one abigen macro -> one trait -> one impl for AsRef<MyInterfaceType> -> one field in the client -> one imp of AsRef<MyInterfaceType> for MyClientType.
So go into each abstract contract, find the public method by hitting crtl+F, copy paste their signature in the abigen and then go with the flow
The text was updated successfully, but these errors were encountered:
Starknet core contract is a contract deployed on Ethereum.
It is made of multiple abstract contracts, the list is defined here:
zaun/lib/starknet/Starknet.sol
Line 33 in 895b35f
Those abstract contract types, define interfaces with a list of methods callable on the contract. Some are internal, but others are
external
,view
,pure
, andpayable
, meaning that they can be triggered by transactions coming from the outer world.We want our client to expose all of those.
I added some of them in #3. There is more to be added, just follow the way I did it: one abstract contract -> one file -> one
abigen
macro -> one trait -> one impl forAsRef<MyInterfaceType>
-> one field in the client -> one imp ofAsRef<MyInterfaceType> for MyClientType
.So go into each abstract contract, find the public method by hitting crtl+F, copy paste their signature in the
abigen
and then go with the flowThe text was updated successfully, but these errors were encountered: