-
Notifications
You must be signed in to change notification settings - Fork 2
ValidateFirstRelease
Eric Passmore edited this page May 16, 2025
·
6 revisions
Review the MSIG that created the Vaulta System Contracts. Look for the setcode action.
https://eosauthority.com/transaction/5b2d6a4c50d00f86c1d76bb0cf88e4d712eb41137d90086992dffec8df990e2e?network=eos
- Get the checksum for the onchain code
Copy and past the setcode and pipe to
xxd -r -p | sha256sum -For example here is a truncated version
echo "0061736D0100000001FB012460000060037F7F7F0060027F7F0060017E0060047E7E7E7E017F60....41000B0408280000" | xxd -r -p | sha256sum -
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 contr
acts/system.wasm" | sha256sum --check
contracts/system.wasm: OK