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
We have really nice hooks (on top of wagmi's) for interacting with contracts deployed from SE-2 (leveraging on the hardhat_contracts.ts file).
Let's find the best way to do something similar with external contracts. E.g. You want your dApp to interact with the DAI contract. SE1 use a external_contracts.js file.
Ideally, as a builder, I'd like to use it the same way we use our custom hooks (same autocomplete / types magic).
I guess we could do that right now if we make the builder paste (in the right format) the contract info in hardhats_contracts.ts. But that's not very friendly.
So maybe a external_contracts.ts with a more clear format? Using wagmi's cli?
We have really nice hooks (on top of wagmi's) for interacting with contracts deployed from SE-2 (leveraging on the
hardhat_contracts.ts
file).Let's find the best way to do something similar with external contracts. E.g. You want your dApp to interact with the DAI contract. SE1 use a
external_contracts.js
file.Ideally, as a builder, I'd like to use it the same way we use our custom hooks (same autocomplete / types magic).
I guess we could do that right now if we make the builder paste (in the right format) the contract info in
hardhats_contracts.ts
. But that's not very friendly.So maybe a
external_contracts.ts
with a more clear format? Using wagmi's cli?Check out this comment from @technophile-04 #200 (comment).
The text was updated successfully, but these errors were encountered: