1
Deploying contract is done by two actions, eosio::setcode for wasm, and eosio::setabi for abi. setcode costs 10x the size of wasm file, but setabi costs the exact size of abi file.
1
a few things to consider:
it is not advisable to compile on your servers. you need tbe full blown dev environment to be set up correctly (all dependencies) in order to compile successfuly; when eosio-ccp was reported as hanging in the past it was because there was some dependencies missing or not version aligned (clang, submodules, etc). if you try to ...
1
this was answered by the comments provided.
in short you can not trust fully the contract as long as the keys controlling the account to which the contract is deployed are still in the hands of a person.
the solution can do several things, two of them are mentioned below:
You can multi sig the contract to trusted members of the community.
You can resign the ...
Only top voted, non community-wiki answers of a minimum length are eligible
