ValidateFirstRelease

Get the code

There are two methods documented here.

From MSIG

First you can review the executed MSIG and copy and past the data from the setcode action. Review the MSIG that created the Vaulta System Contracts. Look for the setcode action. https://eosauthority.com/transaction/5b2d6a4c50d00f86c1d76bb0cf88e4d712eb41137d90086992dffec8df990e2e?network=eos

From System

cleos -u https://eos.api.eosnation.io get code -c /tmp/core.vaulta.wasm core.vaulta

code hash: 718b4773953cae5a21803b7b585d0e17d988b4d3d5d0cabcc57a143ec99a31a6
saving wasm to /tmp/core.vaulta.wasm

Get the checksum for the onchain code

For example if the code is in a file named /tmp/core.vaulta.wasm Run this command sha256sum /tmp/core.vaulta.wasm

The resulting checksum should be 718b4773953cae5a21803b7b585d0e17d988b4d3d5d0cabcc57a143ec99a31a6

Build the Contracts from source

You must already have installed and built CDT-4.1.

git clone https://github.com/VaultaFoundation/vaulta-system-contract.git
cd vaulta-system-contract
mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTS=OFF ..

Validate

Take the checksum you generated in step 1 and use it to verify the contract.

echo  "718b4773953cae5a21803b7b585d0e17d988b4d3d5d0cabcc57a143ec99a31a6 contracts/system.wasm"  | sha256sum  --check

contracts/system.wasm: OK