Whitepaper - Ethereum Classic With Cover

More documents

Recommendations

Info

Ethereum Classic Documentation, Release 0.1 It is generally expected that the test implementer will read env, exec and pre then check their results against gas, logs, out, post and callcreates. If an exception is expected, then latter sections are absent in the test. Since the reverting of the state is not part of the VM tests. Basic structure { } "test name 1": { "env": { ... }, "pre": { ... }, "exec": { ... }, "gas": { ... }, "logs": { ... }, "out": { ... }, "post": { ... }, "callcreates": { ... } }, "test name 2": { "env": { ... }, "pre": { ... }, "exec": { ... }, "gas": { ... }, "logs": { ... }, "out": { ... }, "post": { ... }, "callcreates": { ... } }, ... Sections The env section: • currentCoinbase: The current block’s coinbase address, to be returned by the COINBASE instruction. • currentDifficulty: The current block’s difficulty, to be returned by the DIFFICULTY instruction. • currentGasLimit: The current block’s gas limit. • currentNumber: The current block’s number. • currentTimestamp: The current block’s timestamp. • previousHash: The previous block’s hash. The exec section: • address: The address of the account under which the code is executing, to be returned by the ADDRESS instruction. • origin: The address of the execution’s origin, to be returned by the ORIGIN instruction. • caller: The address of the execution’s caller, to be returned by the CALLER instruction. • value: The value of the call (or the endowment of the create), to be returned by the CALLVALUE instruction. • data: The input data passed to the execution, as used by the CALLDATA... instructions. Given as an array of byte values. See $DATA_ARRAY. • code: The actual code that should be executed on the VM (not the one stored in the state(address)) . See $DATA_ARRAY. • gasPrice: The price of gas for the transaction, as used by the GASPRICE instruction. 1.7. Contracts and Transactions 109
Ethereum Classic Documentation, Release 0.1 • gas: The total amount of gas available for the execution, as would be returned by the GAS instruction were it be executed first. The pre and post sections each have the same format of a mapping between addresses and accounts. Each account has the format: • balance: The balance of the account. • nonce: The nonce of the account. • code: The body code of the account, given as an array of byte values. See $DATA_ARRAY. • storage: The account’s storage, given as a mapping of keys to values. For key used notion of string as digital or hex number e.g: "1200" or "0x04B0" For values used $DATA_ARRAY. The callcreates section details each CALL or CREATE instruction that has been executed. It is an array of maps with keys: • data: An array of bytes specifying the data with which the CALL or CREATE operation was made. In the case of CREATE, this would be the (initialisation) code. See $DATA_ARRAY. • destination: The receipt address to which the CALL was made, or the null address ("0000...") if the corresponding operation was CREATE. • gasLimit: The amount of gas with which the operation was made. • value: The value or endowment with which the operation was made. The logs sections is a mapping between the blooms and their corresponding logentries. Each logentry has the format: • address: The address of the logentry. • data: The data of the logentry. • topics: The topics of the logentry, given as an array of values. Finally, there are two simple keys, gas and output: • gas: The amount of gas remaining after execution. • output: The data, given as an array of bytes, returned from the execution (using the RETURN instruction). See $DATA_ARRAY. $DATA_ARRAY - type that intended to contain raw byte data and for convenient of the users is populated with three types of numbers, all of them should be converted and concatenated to a byte array for VM execution. • The types are: 1. number - (unsigned 64bit) 2. “longnumber” - (any long number) 3. “0xhex_num” - (hex format number) e.g: ‘‘‘‘[1, 2, 10000, "0xabc345dFF", "199999999999999999999999999999999999999"]‘‘ 1.7.8 Web3 Base Layer Services In addition to the Ethereum blockchain, more components are being developed that decentralise other important aspects of web applications. 110 Chapter 1. Contents
Page 1 and 2:
ETHEREUM CLASSIC WHITEPAPER
Page 4 and 5:
Contents 1 Contents 3 1.1 Introduct
Page 6 and 7:
Using geth . . . . . . . . . . . .
Page 8 and 9:
Ethereum Classic Documentation, Rel
Page 10 and 11:
CHAPTER 1 Contents 1.1 Introduction
Page 12 and 13:
Page 14 and 15:
Page 16 and 17:
Page 18 and 19:
Page 20 and 21:
Page 22 and 23:
Page 24 and 25:
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Page 64 and 65:
Page 66 and 67: Ethereum Classic Documentation, Rel
Page 132 and 133: CHAPTER 2 Improve the Documentation
Page 134: Index A abiDefinition, 82 C code, 8
show all

Whitepaper - Ethereum Classic With Cover

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?