feat: integrate dagger contracts
Integrate dagger contracts from `nim-dagger-contracts` repo.
Add `dagger-contracts`, `nim-web3`, and all of `nim-web3`’s transitive deps as submodule deps to `nim-dagger`. Note: `nim-web3` and its transitive deps may no longer be needed when we switch to `nim-ethers`.
Add a `testContracts` nimble task to test all of the contracts functionality. Namely, this spins up an ethereum simulator, deploys the contracts (in `dagger-contracts`), runs the contract tests, and finally, regardless of success/error, kills the ethereum sim processes. The nimble task can be run with `./env.sh nimble testContracts`.
We also tested `nim-dagger-contracts` as a submodule dep of `nim-dagger`, and while the tests run as expected, the preference is to merge `nim-dagger-contracts` inside of `nim-dagger` for ease of parallel development. There’s also a high probability that `nim-dagger-contracts` is not being used as a dep by other projects. Are there any strong objections to this?
Co-authored-by: Michael Bradley <michaelsbradleyjr@gmail.com>
2022-01-25 00:22:58 +00:00
|
|
|
import std/json
|
|
|
|
|
import pkg/ethers
|
|
|
|
|
import pkg/questionable
|
|
|
|
|
|
|
|
|
|
type Deployment* = object
|
|
|
|
|
json: JsonNode
|
|
|
|
|
|
2022-03-15 16:19:21 +00:00
|
|
|
const defaultFile = "vendor/dagger-contracts/deployment-localhost.json"
|
feat: integrate dagger contracts
Integrate dagger contracts from `nim-dagger-contracts` repo.
Add `dagger-contracts`, `nim-web3`, and all of `nim-web3`’s transitive deps as submodule deps to `nim-dagger`. Note: `nim-web3` and its transitive deps may no longer be needed when we switch to `nim-ethers`.
Add a `testContracts` nimble task to test all of the contracts functionality. Namely, this spins up an ethereum simulator, deploys the contracts (in `dagger-contracts`), runs the contract tests, and finally, regardless of success/error, kills the ethereum sim processes. The nimble task can be run with `./env.sh nimble testContracts`.
We also tested `nim-dagger-contracts` as a submodule dep of `nim-dagger`, and while the tests run as expected, the preference is to merge `nim-dagger-contracts` inside of `nim-dagger` for ease of parallel development. There’s also a high probability that `nim-dagger-contracts` is not being used as a dep by other projects. Are there any strong objections to this?
Co-authored-by: Michael Bradley <michaelsbradleyjr@gmail.com>
2022-01-25 00:22:58 +00:00
|
|
|
|
|
|
|
|
## Reads deployment information from a json file. It expects a file that has
|
|
|
|
|
## been exported with Hardhat deploy.
|
|
|
|
|
## See also:
|
|
|
|
|
## https://github.com/wighawag/hardhat-deploy/tree/master#6-hardhat-export
|
|
|
|
|
proc deployment*(file = defaultFile): Deployment =
|
|
|
|
|
Deployment(json: parseFile(file))
|
|
|
|
|
|
|
|
|
|
proc address*(deployment: Deployment, Contract: typedesc): ?Address =
|
|
|
|
|
let address = deployment.json["contracts"][$Contract]["address"].getStr()
|
|
|
|
|
Address.init(address)
|
