Web3bridge Students (Cohort XI) Share What They’ve Learned: Interface, Interaction & Mainnet forking

this video is proudly brought to you by wwbd with links our official sponsors for cohort 11 hi everyone I'm Sunday Solomon welcome to yet another weekly updates um today we'll be talking about interfaces interfaces are very similar to AR contracts where you just like after contracts can be inherited interface can also be inherited your interface can be inside of a contract and outside of a contract still but mostly for modularization and to best reduce gas fee gas fees we make them outside the contract so basically instead of another file your interfaces can can be inherited they can also be imported so your interfaces when creating an interface is just like a contract is also declared where you have your keyword contract and then the contract name and the rest of the code logic that goes into the contract the same way your interface work except that for interfaces you have no Constructors for interfaces you also have no States variables and then interfaces you don't have the logic inside of the interface so what that the interface does is it extends it's like an extension of the actual logic so what it does is it gives you um the parameters needed to run the function instead of its original or inide of its parent representation so your your interface is basically can also act like a standard just like we have the IRC 20 IRC 721 they also act like um a guideline for say for interaction so if you if you to interact with that interface you have to follow that interface structure mind you they can still be overwritten interfaces can be overwritten where you declare the the actual interface and then inside of the interface you now declare how you want the parameters or the function to be used and returned so they can be overwritten directions are a way to um re uh interact remotely with an already deployed contract so yes let's say you have a contract that is already deployed that you would like to interact with or communicate with um what you do is to get the contract address of the already deployed contracts and have that handy and then get the interface as well now when I say the interface I mean the functions that are readily available inside of the contract now you get the functions that you need and you declare them as an interface now that interface is going to um be able to provide those functions that you need to call from the already deployed contract now when you have that and you have your interface and you have your contract uh from your code you can call the functions that are inside of that contract and interact with the deployed contract on chain now this is useful for when you um do not want to you want to communicate with that contract from your code or you do not want to communicate from the front end that is available another use case is cuz our tutor gave us a scenario that happened say there's this scenario where someone um uh provided liquidity to a pool but isn't able to pull it out pull it out then the way he went about that was getting the interface and then interacting with it from his code and calling the function that is in that contract and that is a very handy tool for people who want to interact remotely with an already deployed contract so M working is it allows us to um simulate reward because um of course while we are developing our smash contract we can use test net to test our apps and see how they works but still we seem to simulate some there are some transactions that some um some applications that this with forance def or this Dex so this things we need to to simulate real world scenario so we need to do what we call minute for so we can simulate how this we work in um we work with reward data set and States M networking is all about interacting with an already deployed um contract on chain that is basically you're trying to interact with that um smart contract on your local machine which is your laptop when you are doing this you are not changing the data of the already deploy contract you are just impersonating that contract on your local machine and we made use of the Unis swab V2 router the address to do this m net foring you can passate different contracts on your local machine first of all why do you want to do main networking main networking helps um as a smart contract developer helps you to you know test a function that is already deployed in another contract maybe you are trying to work on a um a contract and you want to interact with that contract but that contract has already been deployed on chain so how do you do that you do that using that main networking and for you to do that um how that provide that um package a helper which you use to impersonate um a user a reuser in sense like the user already has that token so in that way because for you not to um interact with it on your local machine you have to act as if you're a re owner of that uh um coin on that contract [Music]