for which compiler version a smart contract was developed for. It helps to avoid breaking changes.
B.
for which blockchain a smart contract was developed for. It helps to avoid confusion with beta-customers.
C.
for which blockchain node a smart contract was developed for. It helps to avoid mixing up different versions of go-ethereum.
Answer:
A
Question 13
Having a bug-bounty program early on:
Options:
A.
can help to engage the community in testing your smart contracts and therefore help to find bugs early.
B.
might be a burden as it is an administrative overhead mainly.
C.
is completely useless. Who wants to test beta-ware software? It’s better to start with the bug-bounty program after the contract is released on the main-net.
Answer:
A
Question 14
With the truffle config file you can manage:
Options:
A.
the amount of gas your contract deployment and transactions, against your contract, will need. This way you can essentially lower the gas costs over traditional web3.js dApps.
B.
different Networks to deploy your contracts to. This way you can easily deploy to a local blockchain, the main-net or the Ropsten/Rinkeby Test-Net with only one parameter.
C.
you can manage your secret API keys to the Ethereum Network. This way you can get access to several different Ethereum nodes at the same time without the need to switch your keyfiles.
Answer:
B
Question 15
Hashing Mining uses:
Options:
A.
Keccack256 while internally to hash values it's easy to use the Dagger-Hashimoto to create a meaningful hash.
B.
the Dagger-Hashimoto hashing while internally the EVM uses SHA256 which is an alias for Keccack256.
C.
the Dagger-Hashimoto hashing while internally the EVM uses Keccack256 which is almost similar to SHA256, but has a different padding so produces different hashes.
