Whitepaper - Ethereum Classic With Cover

More documents

Recommendations

Info

Ethereum Classic Documentation, Release 0.1 The address of the account under which the code is executing, to be returned by the ADDRESS instruction. secretKey The secret key as can be derived by the v,r,s values if the transaction. to The address of the transaction’s recipient, to be returned by the ORIGIN instruction. value The value of the transaction (or the endowment of the create), to be returned by the CALLVALUE‘ instruction (if executed first, before any CALL). • 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 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 is one simple key output output The data, given as an array of bytes, returned from the execution (using the RETURN instruction). See $DATA_ARRAY. In order to avoid big data files, there is one exception. If the output data is prefixed with #, the following number represents the size of the output, and not the output directly. $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) 1.7. Contracts and Transactions 105
Ethereum Classic Documentation, Release 0.1 e.g: ‘‘‘‘[1, 2, 10000, "0xabc345dFF", "199999999999999999999999999999999999999"]‘‘‘‘ RLP Tests Describes an RLP (https://github.com/ethereum/wiki/wiki/RLP) encoding using the .json file. The client should read the rlp byte stream, decode and check whether the contents match it’s json representation. Then it should try do it reverse - encode json rlp representation into rlp byte stream and check whether it matches the given rlp byte stream. If it is an invalid RLP byte stream in the test, then ‘in’ field would contain string ‘INVALID’ Some RLP byte streams are expected to be generated by fuzz test suite. For those examples ‘in’ field would contain string ‘VALID’ as it means that rlp should be easily decoded. RLP tests are located in in /RLPTests Note that RLP tests are testing a single RLP object encoding. Not a stream of RLP objects in one array. Basic structure { "rlpTest": { "in": "dog", "out": "83646f67" }, "multilist": { "in": [ "zw", [ 4 ], 1 ], "out": "c6827a77c10401" }, "validRLP": { "in": "VALID", "out": "c7c0c1c0c3c0c1c0" }, } "invalidRLP": { "in": "INVALID", "out": "bf0f000000000000021111" }, ... Sections • in - json object (array, int, string) representation of the rlp byte stream (*except values ‘VALID’ and ‘INVALID’) • out - string of rlp bytes stream Difficulty Tests Found in \Basic Tests\difficulty*.json files. This tests are designed to just check the difficulty formula of a block. difficulty = DIFFICULTY(currentBlockNumber, currentTimestamp, parentTimestamp, parentDifficulty) described at [EIP2](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-2.mediawiki) point 4 with homestead changes. 106 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: 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?