## Questions from SDao Q: How do we need to deploy the GO route optimizer? A: The go router compiles to webassembly, and is run client-side. There's a `make` command to do that (`make add-router`) in polymer-web, which is detailed in the readme. Just change the submodule directory to be wherever you're hosting it now in `.gitmodules`. You will also need to install `tinygo`, as this is what we used to compile it. --- Q: Do the contracts need to be deployed/instantiated in a particular order? A: The order is: - Deploy the vault - Deploy the staking contract (if you want to implement your own sDao contract that receives & distributes DEX fees, that's fine) - Link the staking contract to the vault - Deploy the distributors - Link the distributors to incentivized vault pools - Deploy the vesting schedule - Deploy the token with distributor/vesting addresses as initial holders - Do post-deploy config (set the token address in the staking & distributor contract, etc) --- Q: What’s the best way to make the contracts upgradeable? A: Like most Secret contracts, ours follow a MVC structure. You can make a handler callable only by the contract owner that lets you set a parameter in the contract config. --- Q: Any advice on moving contracts to cosmwasm 1.0? A: We were going to stay on the current version at launch. --- Q: Any other things that you were planning to do before launch? A: Not really. Just launch the DEX and token. --- Q: In the weighted pool section (https://polymer-docs.pages.dev/weighted_pools) it says both Bo and Bi are the amount of base currency that is being swapped, is that right or is Bo the amount of quote currency being swapped? A: Typo. That should say quote currency. O = out = quote currency --- Q: Can you detail the process you used to get the contracts up on testnet? A: We just ran the deploy scripts. We used [Polar](https://docs.arufaresearch.com/) for deployment and testing. Command is: ``` npx polar run /scripts/<script>.js ``` There are also scripts in `/scripts-interactions` that let you configure the contracts after deploy. They should be pretty readable, as they're just calling `secretcli`.