Skip to content
This repository was archived by the owner on Dec 8, 2025. It is now read-only.

Commit 5526691

Browse files
authored
Merge pull request #104 from InjectiveLabs/docs/faq-multicall3-tachida2k
docs: add FAQ about multicall3
2 parents 43aa861 + 9cc17c4 commit 5526691

File tree

1 file changed

+13
-1
lines changed

1 file changed

+13
-1
lines changed

.gitbook/faq.md

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,9 +22,21 @@ which is 1 to 1, and bidirectional.
2222
## Infrastructure
2323

2424
Q: When maintaining a private node:
25-
- should we store 2.5 Ti archival data (event provider)?
25+
26+
- Should we store 2.5 Ti archival data (event provider)?
2627
- Can we skip that part and make indexer work?
2728

2829
A: Event provider can be pruned. One can use the public event provider endpoint for the initial sync. Then resort to local deployment, but only from the latest height. Therefore, yes can be skipped.
2930

3031
----
32+
33+
## EVM
34+
35+
Q: Does Injective have a deployment of the [`multicall3`](https://www.multicall3.com/) smart contract? <!-- tachida2k -->
36+
37+
A: Yes.
38+
39+
- Injective Mainnet `multicall3`: [`0xcA11bde05977b3631167028862bE2a173976CA11`](https://blockscout.injective.network/address/0xcA11bde05977b3631167028862bE2a173976CA11?tab=contract)
40+
- Injective Testnet `multicall3`: [`0xcA11bde05977b3631167028862bE2a173976CA11`](https://testnet.blockscout.injective.network/address/0xcA11bde05977b3631167028862bE2a173976CA11?tab=contract)
41+
42+
----

0 commit comments

Comments
 (0)