Skip to content

Latest commit

 

History

History
22 lines (15 loc) · 819 Bytes

README.md

File metadata and controls

22 lines (15 loc) · 819 Bytes
Raw

README

Upgrade proposal verification

Assume you want to verify a new upgrade proposal with code commit <COMMIT> and binary hash <HASH>.

  1. Install Docker (only once).
  2. git clone https://github.com/TaggrNetwork/taggr.git (only once)
  3. cd taggr
  4. git fetch --all && git checkout <COMMIT>
  5. make release
  6. Verify that the printed hash matches the <HASH> value from the release page.

Release proposal

To propose a release, follow the steps above first. If they were successful, you'll find a binary taggr.wasm.gz in the release-artifacts directory. Use the printed code commit and the binary to submit a new release proposal.

Local development and contributions

Refer to the local development docs for instructions on how to work with Taggr locally.