Mars
Mars copied to clipboard
Mars is an infrastructure-as-code tool for Ethereum
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically....
**Is your feature request related to a problem? Please describe.** A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] **Describe the solution you'd...
It would take long `getEthPriceUsd` when I'd like to deploy to my local network (and for every single transaction). Is it possible 1. disable getEthPriceUsd via config 2. cache the...
Mars already handles verification of contracts on Etherscan family of block explorers. It would be cool to add support for [Sourcify](https://sourcify.dev/) verification as well.
Currently we output in deployments.json `multisig: false` for non-multisig deployments. That adds unnecessary clutter. multisig: true should only be added for multisig related scenarios
Running `mars` on a contract with a fixed-size array function parameter (e.g. `address[2]`) generates the following error: ``` Unknown type address[2] ``` Related code: https://github.com/TrueFiEng/Mars/blob/master/packages/mars/src/generate/generator.ts#L82-L107
When network is provided to mars in format `http...` then in deployments.json entries are saved under 'unknown' node. Allow for network naming overrides.
While #15 I've stumbled upon a problem with hardhat generated `*.json` files stored in nested directories.
I want to store frequently used mars configuration in a file. Especially when there's a need for complex structure for some extension feature (e.g. multisig) ```json { "multisig": { "gnosis":...
There is implicit limitation that the multisig batch tx cannot exceed gas limit, otherwise it reverts. Improve the situation. Idea - try to simulate (dry-run) the batch tx execution and...