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
Copy file name to clipboardExpand all lines: README.md
+57Lines changed: 57 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,7 +47,64 @@ $ yarn add ethereum-multicall
47
47
```
48
48
49
49
## Usage
50
+
### Overloaded methods
51
+
As the [official docs mentions here](https://docs.ethers.io/v3/api-contract.html#prototype):
50
52
53
+
> Due to signature overloading, multiple functions can have the same name. The first function specifed in the ABI will be bound to its name. To access overloaded functions, use the full typed signature of the functions (e.g. contract["foobar(address,uint256)"]).
54
+
55
+
So, when creating the contract call context, under the calls array property we should have that in mind and use the method signature rather than the method name. E.g.
0 commit comments