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
Libraries with public / external functions are deployed as a separate contract. If deploying a contract that depends on such a library, the contract needs to be linked with the library. This is done by replacing a placeholder (e.g. __$7e77f802c8a093aee7d19a899432839085$__) in the bytecode of the contract with the address of the library.
Ideally, we should support two cases:
deploy both the library and the contract in a single step (deploy call does everything for you)
deploy library in a separate step and provide an address to deployed library when deploying the contract
Module
ABI
📝 Description
Libraries with
public
/external
functions are deployed as a separate contract. If deploying a contract that depends on such a library, the contract needs to be linked with the library. This is done by replacing a placeholder (e.g.__$7e77f802c8a093aee7d19a899432839085$__
) in the bytecode of the contract with the address of the library.Ideally, we should support two cases:
See for reference:
The text was updated successfully, but these errors were encountered: