Skip to content

Define and communicate goals and non-goals of this project #101

Description

@webmaster128

There are multiple alternative approaches to CosmWasm build systems that come with different priorities and trade-offs.

E.g.

In order to guide future development and be able to confidentially reject PRs that are not in line, we should define goals and non-goals here.

Activity

  1. dakom commented on Dec 28, 2022

    @dakom

    In line with that high-level discussion, may I suggest to rename this project something like "contract builder"?

    In other words, it seems to me that the goal of this project is really to have reproducible binaries, such that they can be confirmed by the on chain hash.

    It's not to actually optimize wasm code, that's the goal of wasm-opt (and cargo itself)

    Might seem a bit nitpicky, and naming things is hard, but it adds a bit of friction to discussions when I need to manually build for some reason, and it's unclear at first glance why I'm choosing to "not optimize" my contracts by skipping this tool (albeit while running cargo build and wasm-opt manually with the same exact settings as here).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions