# First steps with near-multicall >[TOC] In order to understand how to use near-multicall for super-charged DAO proposals, we first need to establish a rough understanding of how near-multicall works, it will be quick don't worry. ## The multicall instance Since SputnikDAO DAOs only allow to call one target address per proposal, we need a proxy contract that will handle all desired function calls. Multicall instances (MI) serve this purpose. Every DAO has their own private multicall instance to work with. ![](https://i.imgur.com/jUgiHru.png) The DAO will call its MI and pass instructions, the MI will then call the desired contracts one after another. :::info :bulb: The address of the MI is always derived from the DAO address. It's easy to explain it with an example: The MI to `marmaj.sputnik-dao.near` will be deployed to `marmaj.v1.multicall.near` ::: As a first time user, the DAO will first need to create their multicall instance. You can think of it as an installation step that only needs to happen once. ## Creating a multicall instance for my DAO To simplify the interaction, we offer a page on our UI that will assist you the creation process. Open https://multicall.app/#/dao and login with your wallet in the bottom left corner. Next, enter your DAOs address in the _Select DAO_ field below. You will be met with one of three scenarios: ![](https://i.imgur.com/zgEHJqQ.png) _Scenario A_. We successfully detected your DAO and by clicking on _Propose_, a DAO proposal will be created asking to create the multicall instance. After the Proposal passes, you are all set! _Scenario B_. Creating a multicall instance for this DAO was already proposed to the DAO, and its currently waiting for votes. Click _vote YES_ to vote _YES_ on the creation proposal. _Scenario C_. A multicall instance for this DAO already exists! :tada: The page will show a dashboard filled with data about your multicall instance. ## Making your first multicall [Our UI](https://multicall.app) offers a space to build your multicalls. Simply drag a _card_ from the side menu into the column in the middle of the page. This column represents your instructions given to the MI, it is executed in **sequence** from top to bottom. For advanced usage, you can add more columns by clicking the _+_ icon on top of the columns. The instructions in all columns will run in **parallel**. ![](https://i.imgur.com/UtFmnOt.gif) Let's talk a little about the cards. Cards serve as building blocks of the proposal. They hold information about what contract and function to call with what parameters. Click the pen icon in the top right corner of a card to open the card's editor where you specify the required parameter. To simplify the interaction, our team is working hard to create as many premade cards as possible. If none of the premade cards suit your need, the _Custom_ card will. :::info :bulb: Think we're missing a much needed card? Let us know in our [Discord](https://discord.gg/wc6T6bPvdr)! ::: Once you are happy with your creation click on the _Export_ tab in the side menu. You will be asked to put a proposal description that will be displayed on AstroDao. If everything is fine, i.e. you don't have any unresolved input errors and you have the rights to make proposals on the DAO, the propose button at the bottom of the menu will turn green. Click it to propose your multicall. **note:** The transaction cost is due to SputnikDAOs proposal bond, and will be reimbursed once your proposal is approved. The amount is set in the DAO configuration, near-multicall does not charge any fees. ## Dealing with funds As we have seen in _[The multicall instance](#The-multicall-instance)_ the MI serves as a proxy contract for the DAO. Since the DAO and MI are not the same contract, the MI cannot operate in the name of the DAO, meaning the MI cannot access funds on the DAO. This is a good thing when it comes to security, but a bad thing in terms of user experience. Any funds that are need for a multicall should be transferred to the MI prior to the execution of said multicall. We suggest to have some amount of spending money on the MI for quick access, while keeping the DAOs treasury on the DAO. The funds on the MI are only be accessible by the MI admins (per default, only the DAO). Legal statements where legal statements are due, we are a beta software and do not guarantee the safety of assets on the MI, please have a look at [our contract](https://github.com/near-multicall/contracts) yourself, use at your own risk. ![](https://i.imgur.com/myT7aaY.png) You can easily see the available funds on the MI via the _Funds_ tab on the [_DAO page_](https://multicall.app/#/dao). While creating a multicall keep in mind, that the action will be called from the MI. Say you want to interact with a Dapp, it will be the MI's Dapp account that is used, not the DAO's. **hint:** use our _Dapp login_ feature to view the Dapp as if logged in as the MI (or DAO!). _Pro tip._ Our UI also enables sending one whitelisted token as an attachment along with the instructions. ## Need assistance? If you have any questions or problems regarding near-multicall please don't hesitate to ask us on [Discord](https://discord.gg/wc6T6bPvdr). If you are curious about our other features and want to stay up to date with the project, follow us on [Twitter](https://twitter.com/near_multicall). We are 100% open source, read our code on [GitHub](https://github.com/near-multicall).