Skip to content

Instantly share code, notes, and snippets.

@lukestokes

lukestokes/deploylost.md

Last active April 28, 2019 01:25
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save lukestokes/80d5c1ec403f466ca87f3edc9a610819 to your computer and use it in GitHub Desktop.
Save lukestokes/80d5c1ec403f466ca87f3edc9a610819 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
deploylost.md

This proposal runs setcode and setabi methods for the eosio.lost account to deploy the code described in the eosio.lost README file.

To verify this proposal sets the right code, pull down the mainnet-v1 release from this repo: https://github.com/eosdac/eosio.lost

Compile it yourself using eosio.cdt version 1.5:

eosio-cpp -o eosio.lost.wasm eosio.lost.cpp --abigen

Check the md5 hash of the result:

sha256sum eosio.lost.wasm 
90f436cd4e13f6ad2b634a996c63818a827b7ba49c877831bd7f6d132ace1f39  eosio.lost.wasm

Now check that against the proposal:

./cleos.sh multisig review eosdacserver deploylost | jq -r '.transaction.actions[0].data.code' | xxd -r -p | sha256sum
90f436cd4e13f6ad2b634a996c63818a827b7ba49c877831bd7f6d132ace1f39  -

And note the md5 hashes are the same. This only tells you that the code in the eosio.lost mainnet-v1 release matches the code being deployed. It does not check the code for errors, vulnerabilities, or exploits which might hurt EOS. For that, you'll have to go through the source code directly.

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