New answers tagged

0

msg.sender is either the account that signed the transaction or the contract that called your contract and it's created automatically. msg.sender cannot be faked and you can rely on it, otherwise Ethereum network won't be secure


1

If the MAIN contract inherits from RandomNumberConsumer making editDna internal should be enough. // Declare contract as abstract abstract contract RandomNumberConsumer is VRFConsumerBase { // Forward declaration function editDna(uint randomN, uint carId, bytes32 requestId) internal virtual; constructor() VRFConsumerBase(..) public { .. ...


0

It's not much of a feature or achievement to create basic transactions using some esoteric MyEtherWallet "offline GUI" (which needs to be connected to the internet and thus is very much an "online GUI" despite the deceptive name). Etherscan was providing this functionality ages before MEW. What WOULD BE impressive would be to be able to ...


1

Calls through view members of interfaces are done through STATICCALL opcode. As my experiment confirmed Solidity 0.6.0 does use STATICCALL in this case. https://github.com/ethereum/EIPs/blob/master/EIPS/eip-214.md To increase smart contract security, this proposal adds a new opcode that can be used to call another contract (or itself) while disallowing any ...


Top 50 recent answers are included