omgnetwork/community-points

Publish contract ABI as artifect

Closed this issue · 1 comments

boolafish commented

Have been thinking about possible solutions:

  1. use ethPM as the package management. Not sure how to get the ABI out though. Supposedly do-able
  2. use npm as the package management. However, limited to npm to get the ABI out
  3. use a artifact branch in this repo, whenever there is a new release, we publish the ABI with the semver in a folder the branch there. eg. abi/v0.0.1/ and abi/v0.0.2/ ...
  4. Just manual put the ABI under contracts/ as Pong suggested.
0x234 commented

4 sounds the easiest here. It won't be changing often as v1 with 1.0.4 contracts will still be used so I don't think we need to version and support different ABIs.

  • 👍2