Function calls in the Ethereum Virtual Machine are specified by the first four bytes of data sent with a transaction. These 4-byte signatures are defined as the first four bytes of the Keccak hash (SHA3) of the canonical representation of the function signature. Since this is a one-way operation, it is not possible to derive the human readable representation of the function from the 4-byte signature. This database is meant to allow mapping those 4-byte signatures back to their human readable versions.

RT @ethchris: Feature freeze for #Solidity 0.5.0! Please try our prerelease: We are still working on improving the documentation.

an Ethereum EVM binary analysis framework

💰🕰️📋[EIP 1337 POC] Recurring subscriptions on the Ethereum blockchain powered by meta transactions. - austintgriffith/token-subscription

provides a clean separation between the communication aspect of smart contracts on a blockchain, allowing for the rich interaction patterns, and a programming component, which enjoys principled semantics and is amenable to formal verification. Scilla is not meant to be a high-level programming language, and we are going to use it as a translation target for high-level languages, such as Solidity, for performing program analysis and verification, before further compilation to an executable bytecode.

#Solidity 0.5.0 breaking release preliminary changelog #ethereum