Skip to content

4eku/Taggr

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

1,758 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

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.

Backups

Make sure you have installed cargo.

To create a backup of the Taggr state, run:

make backup DIR=/path/to/backup

Local development and contributions

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

About

Decentralized social network and publishing platform.

Resources

License

Stars

0 stars

Watchers

0 watching

Forks

Packages

 
 
 

Contributors

Languages

  • TypeScript 84.1%
  • Rust 11.2%
  • CSS 2.4%
  • JavaScript 0.9%
  • HTML 0.7%
  • Shell 0.3%
  • Other 0.4%