-
Notifications
You must be signed in to change notification settings - Fork 2
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
Neutron deployment #75
Comments
In order for this to work, update PR #76 needs to be completed (and it is but not yet merged). Here below the list of crates version we are aiming to upgrade to: [workspace.dependencies]
cosmwasm-std = "2.0.4"
cw2 = "2.0.0"
schemars = "0.8.15"
serde = { version = "1.0.188", default-features = false }
serde-json-wasm = "1.0.0"
cw-storage-plus = "2.0.0"
cosmwasm-schema = { version = "2.0.4", default-features = false }
base64 = "0.21.7"
prost = "0.12.3"
prost-types = "0.12.1"
cosmos-sdk-proto = { version = "0.20.0", default-features = false }
bech32 = "0.9.1"
thiserror = "1.0.49"
protobuf = "~3.3.0"
hex = "0.4.3"
serde_json = { version = "1.0.87" }
tendermint-proto = "0.34.1"
speedate = "0.13.0" |
All contracts are currently building proper |
Mostly addressed by #119. Still outstanding:
|
Requirements taken from #154 , and closing 154 SummaryOur current (WIP) impl for the quartz CLI only works with Acceptance Criteria (tentative)
|
Dan and I were having a discussion to close out #159 by adding in support for neutrond. We can do that, or create a new PR that does that. Need to decide in the next pelaton |
Making the cli configurable with a binary (wasmd, neutrond, osmosisd, etc.) |
We had a discussion in peloton today, that we will launch quartz with just neutron, and in the future we will add the ability to attach to any binary, since quartz will work with any cosmos chain (so we shouldn't limit ourselves to wasmd and neutrond). However for v0.1, just neutron is fine |
We can deploy to neutron testnet and a single validator neturon testnet with v0.1, so closing now |
Depends on #124 on #144
The text was updated successfully, but these errors were encountered: