Skip to content
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

Closed
dusterbloom opened this issue Jul 3, 2024 · 8 comments
Closed

Neutron deployment #75

dusterbloom opened this issue Jul 3, 2024 · 8 comments
Assignees
Milestone

Comments

@dusterbloom
Copy link
Contributor

dusterbloom commented Jul 3, 2024

  • be able to run on Neutron
  • runs transfers demo on Neutron

Depends on #124 on #144

@dusterbloom dusterbloom self-assigned this Jul 3, 2024
@dusterbloom
Copy link
Contributor Author

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"

@dusterbloom
Copy link
Contributor Author

All contracts are currently building proper wasm files compatible with the above neutron-testnet versioning standard

@thanethomson
Copy link
Contributor

thanethomson commented Aug 13, 2024

Mostly addressed by #119.

Still outstanding:

  • Adapt the Quartz CLI to be able to deploy to Neutron (see below)

@davekaj
Copy link
Contributor

davekaj commented Aug 20, 2024

Requirements taken from #154 , and closing 154

Summary

Our current (WIP) impl for the quartz CLI only works with wasmd, but we should get it to work with neutrond as well.

Acceptance Criteria (tentative)

  • Either replace all wasmd usages with neutrond.
  • Or add support for a --chain-bin CLI arg that allows users to specify which chain binary to use. (This means we probably also need to get all chain related config params from the user e.g. address prefix, coin denom, etc.)

@davekaj davekaj mentioned this issue Aug 20, 2024
2 tasks
@davekaj
Copy link
Contributor

davekaj commented Aug 20, 2024

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

@davekaj
Copy link
Contributor

davekaj commented Sep 3, 2024

Making the cli configurable with a binary (wasmd, neutrond, osmosisd, etc.)

@davekaj
Copy link
Contributor

davekaj commented Sep 17, 2024

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

@dusterbloom dusterbloom linked a pull request Sep 27, 2024 that will close this issue
@davekaj
Copy link
Contributor

davekaj commented Oct 23, 2024

We can deploy to neutron testnet and a single validator neturon testnet with v0.1, so closing now

@davekaj davekaj closed this as completed Oct 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants