Whitepaper - Ethereum Classic With Cover
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>Ethereum</strong> <strong>Classic</strong> Documentation, Release 0.1<br />
base layer service Services such as SWARM and Whisper which are built into the <strong>Ethereum</strong> platform.<br />
js Javascript.<br />
syncing The process of downloading the entire blockchain.<br />
fast sync Instead of processing the entire block-chain one link at a time, and replay all transactions<br />
that ever happened in history, fast syncing downloads the transaction receipts along the blocks,<br />
and pulls an entire recent state database.<br />
ASIC Application-specific integrated circuit, in this case referring to an integrated circuit custom<br />
built for cryptocurrency mining.<br />
memory-hard Memory hard functions are processes that experience a drastic decrease in speed or<br />
feasibility when the amount of available memory even slightly decreases.<br />
keyfile Every account’s private key/address pair exists as a single keyfile. These are JSON text files<br />
which contains the encrypted private key of the account, which can only be decrypted with the<br />
password entered during account creation.<br />
ICAP format The format of the IBANs defined using the Inter-exchange Client Address Protocol.<br />
block(chain) explorer A website that allows easy searching and extraction of data from the<br />
blockchain.<br />
geth <strong>Ethereum</strong> client implemented in the Golang programming language, based on the protocol as<br />
defined in the <strong>Ethereum</strong> Yellow Paper.<br />
eth <strong>Ethereum</strong> client implemented in the C++ programming language, based on the protocol as defined<br />
in the <strong>Ethereum</strong> Yellow Paper.<br />
ethereumjs <strong>Ethereum</strong> client implemented in the Javascript/Node programming language, based on<br />
the protocol as defined in the <strong>Ethereum</strong> Yellow Paper.<br />
pyethereum <strong>Ethereum</strong> client implemented in the Python programming language, based on the protocol<br />
as defined in the <strong>Ethereum</strong> Yellow Paper.<br />
ethereumj <strong>Ethereum</strong> client implemented in the Java programming language, based on the protocol<br />
as defined in the <strong>Ethereum</strong> Yellow Paper.<br />
ethereumh <strong>Ethereum</strong> client implemented in the Haskell programming language, based on the protocol<br />
as defined in the <strong>Ethereum</strong> Yellow Paper.<br />
parity <strong>Ethereum</strong> client implemented in the Rust programming language, based on the protocol as<br />
defined in the <strong>Ethereum</strong> Yellow Paper.<br />
difficulty In very general terms, the amount of effort required to mine a new block. <strong>With</strong> the launch<br />
of Homestead, the difficulty adjustment algorithm will change.<br />
account Accounts are a central part of the <strong>Ethereum</strong> network and are an essential part of any transaction<br />
or contract. In <strong>Ethereum</strong>, there are two types of accounts: Externally Owned accounts<br />
(EOA) and Contract accounts.<br />
HLL (obsolete) Acronym for Higher Level Language, which is what Serpent and Solidity are. HLL<br />
is what early Ðapp developers called <strong>Ethereum</strong> programming languages that did not touch the<br />
low level elements. This phrase has been phased out.<br />
CLL (obsolete) Acronym for C Like Language, which Mutan was. This acronym has been phased<br />
out.<br />
ES1, ES2, and ES3 (obsolete) “<strong>Ethereum</strong> Script” versions 1,2 and 3. There were early versions of<br />
what would become the <strong>Ethereum</strong> Virtual Machine (EVM).<br />
log event Contracts are triggered by transactions executed as part of the block verification. If conceived<br />
of as a function call, contract execution is asynchronous, and therefore they have no return<br />
value. Instead contracts communicate to the outside world with log events. The log events are<br />
part of the transaction receipt which is produced when the transaction is executed. The receipts<br />
are stored in the receipt trie, the integrity of which is guaranteed by the fact that the current root<br />
122 Chapter 1. Contents