-
Notifications
You must be signed in to change notification settings - Fork 212
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker environment for testing cross-chain orchestration #8896
Comments
As discussed in the project management meeting, @0xpatrickdev will come back with a list of things that are missing from Agoric chain at genesis that need to be added to starship and then we'll regroup and find the owners to address those missing things |
starship-demo#700a5f68 contains changes implemented by the cosmology team to integrate an agoric chain image via agoric-3-proposals. The chain starts successfully, but from a new genesis state instead of the simulated state from agoric-3-proposals. In starship-demo repo#07e7ddf, the latest head, the agoric configuration implements the custom scripts directives available for building the chain. Presumably, these could be modified to preserve the existing genesis state and send tokens to the starship An alternative approach might involve executing core proposals on top of the new genesis state. I explored this path today (init-network.js, init-localchain.js, init-orchestration.js) but faced some headwinds:
|
@0xpatrickdev and I managed to get just a little more info: |
Here is a comparison of vats available in starship-demo repo#07e7ddf versus a normal a3p: normal
starship
The diff is only v15 onwards, which only seems to be inter economy dependencies. I don't think these are completely necessary, and was surprised to see some behavior like smart wallets not working as expected. Provisioning a smart wallet results in unexpected behavior. When attempting to first add 10_000_000uist to the provision pool addr,
Still figuring out how to set Here is the beginning section of the validator logs: starship validator logs
It seems like Cosmosvisor is being used , but I'm not seeing the repoconfig.sh: No such file or directory error. Edit: ah, provisionPool is part of the inter economy bits: v25:zcf-b1-9f877-provisionPool-governor |
Example of this is here: 0xpatrickdev/starship-demo#5 |
refs: #9063 ## Description More progress on, - #9063 ### Security Considerations Sources chain network data from chain-registry. ### Scaling Considerations Writes each chain info node or edge to one vstorage node. ### Documentation Considerations none ### Testing Considerations We'll also have to solve making it work in Starship but I think that's a concern for #8896 or a new ticket. ### Upgrade Considerations Not yet released. When we do want to update the chain info in agoricNames we'll need new work.
closes: #XXXX refs: #8896 ## Description - Creates `@agoric/multichain-testing` package outside of the yarn workspace - Provides a containerized, multi-chain testing environment for local and CI testing using [cosmology-tech/starship](https://github.com/cosmology-tech/starship/tree/devnet-0.2.2) - The current `config.yaml` includes agoric, osmosis, cosmos, and hermes relayers between each. A chain registry (served over http), faucet, and block explorer are also provided). - Provides an ava test setup for accessing a chain registry, creating wallets, and requesting faucet funds - Ports utilities from `@agoric/synthetic-chain` and `dapp-agoric-basics` that help towards a smart wallet client that can execute offers. ### Security Considerations ### Scaling Considerations Taking on some tech debt here wrt smart wallet utilities and being DRY, but we plan to address this in future. See #8963 ### Documentation Considerations README.md documentation for running the service is provided. ### Testing Considerations The goal of this PR is to build greater confidence in our software via automated testing with fully-simulated chains. ### Upgrade Considerations
refs: #8896 ## Description The current `stakeIca.contract.js` bundle is ~4.5 MB uncompressed. Any attempted installation resulted in **400 Bad Request: request body too large** . This change adjusts `app.toml` and `config.toml` params like `max_body_bytes`, `max_header_bytes`, `max_txs_bytes`, `max_tx_bytes`, and `rpc-max-body-bytes`. ### Security Considerations ### Scaling Considerations The settings may not match other environments, and developers may find their bundles are too large to install if they are only developing against this environment. ### Documentation Considerations The `update-config.sh` is long and mostly copied from `cosmology-tech/starship`. I've added a note about its source and a separate commit for the adjustments made to it. ### Testing Considerations Manually tested the parameters in the course of #9042. Expect a test to be checked in with the completion of #9042. Running the **Multichain E2E Testing** job and ensuring the `Setup Starship Infrastructure` step passes should give us confidence the overrides are also working in CI. ### Upgrade Considerations
refs: #8896 ## Description Extracted from #9534 to focus that PR on multichain and lighten the review. Also it had merge conflicts with master that this resolves. ### Security Considerations nothing new ### Scaling Considerations no ### Documentation Considerations none ### Testing Considerations new coverage ### Upgrade Considerations none
As a contract developer, I need a docker environment with simulated Osmosis, Cosmos, Agoric, IBC Relayers, and test tokens.
Dependencies
The text was updated successfully, but these errors were encountered: