Whitepaper - Ethereum Classic With Cover

More documents

Recommendations

Info

Ethereum Classic Documentation, Release 0.1 TEST_SUITE = BlockTests TEST_CASES = blValidBlockTest blInvalidTransactionRLP blTransactionTest blInvalidHeaderTest userDefinedFile TEST_SUITE = TransactionTests TEST_CASES = ttTransactionTest ttWrongRLPTransaction tt10mbDataField userDefinedFile TEST_SUITE = StateTests TEST_CASES = stExample stSystemOperationsTest stPreCompiledContracts stLogTests stRecursiveCreate stTransactionTest stInitCodeTest stSpecialTest stRefundTest stBlockHashTest stQuadraticComplexityTest stSolidityTest stMemoryTest stCreateTest userDefinedFileState TEST_SUITE = VMTests TEST_CASES = vm_tests vmArithmeticTest vmBitwiseLogicOperationTest vmSha3Test vmEnvironmentalInfoTest vmBlockInfoTest vmIOandFlowOperationsTest vmPushDupSwapTest vmLogTest vmSystemOperationsTest vmPerformanceTest vmInputLimitsTest1 vmInputLimitsTest2 vmRandom userDefinedFile Blockchain Tests Found in /BlockTests, the blockchain tests aim is to test the basic verification of a blockchain. /BlockTests - general blockchain tests. All blocks are built on network: Frontier /BlockTests/Homestead - homestead blockchain tests. All blocks are built on network: Homestead /BlockTests/TestNetwork - transition blockchain tests. All blocks before 5th are built on network: Frontier, then each block should correspond to Homestead rules. It is based around the notion of executing a list of single blocks, described by the blocks portion of the test. The first block is the modified genesis block as described by the genesisBlockHeader portion of the test. A set of pre-existing accounts are detailed in the pre portion and form the world state of the genesis block. It is generally expected that the test implementer will read genesisBlockHeader and pre and build the corresponding blockchain in the client. Then the new blocks, described by its RLP found in the rlp object of the blocks (RLP of a complete block, not the block header only), is read. If the client concludes that the block is valid, it should execute the block and verify the parameters given in blockHeader (block header of the new block), transactions (transaction list) and uncleHeaders (list of uncle headers). If the client concludes that the block is invalid, it should verify that no blockHeader, transactions or uncleHeaders object is present in the test. The client is expected to iterate through the list of blocks and ignore invalid blocks. Basic structure { "ValidBlocks": { "genesisBlockHeader": { ... }, "pre": { ... }, "blocks" : [ { "chainname" : "A", "blocknumber" : "1", "rlp": { ... }, "blockHeader": { ... }, "transactions": { ... }, "uncleHeaders": { ... } }, { "chainname" : "A", "blocknumber" : "2", "rlp": { ... }, "blockHeader": { ... }, "transactions": { ... }, "uncleHeaders": { ... } } ] }, 1.7. Contracts and Transactions 101
Ethereum Classic Documentation, Release 0.1 } "SomeInvalidBlocks": { "genesisBlockHeader": { ... }, "pre": { ... }, "blocks" : [ { "chainname" : "B", "blocknumber" : "3", "chainnetwork" : "Frontier", "rlp": { ... }, }, { "blocknumber" : "1", "rlp": { ... }, "blockHeader": { ... }, "transactions": { ... }, "uncleHeaders": { ... } }, { "blocknumber" : "1", "chainnetwork" : "Homestead", "rlp": { ... }, }, { "blocknumber" : "2", "rlp": { ... }, "blockHeader": { ... }, "transactions": { ... }, "uncleHeaders": { ... } } ] }, ... Sections • The genesisBlockHeader section coinbase: The 160-bit address to which all fees collected from the successful mining of this block be transferred, as returned by the COINBASE instruction. difficulty: A scalar value corresponding to the difficulty level of this block. This can be alculated from the previous block’s difficulty level and the timestamp, as returned by the DIFFICULTY instruction. gasLimit: A scalar value equal to the current limit of gas expenditure per block, as returned by the GASLIMIT instruction. number: A scalar value equal to the number of ancestor blocks. The genesis block has a number of zero. timestamp: A scalar value equal to the reasonable output of Unix’s time() at this block’s inception, as returned by the TIMESTAMP instruction. parentHash: The Keccak 256-bit hash of the parent block’s header, in its entirety bloom: The Bloom filter composed from indexable information (logger address and log topics) contained in each log entry from the receipt of each transaction in the transactions list. extraData: An arbitrary byte array containing data relevant to this block. This must be 1024 bytes or fewer. gasUsed: A scalar value equal to the total gas used in transactions in this block. nonce: A 256-bit hash which proves that a sufficient amount of computation has been carried out on this block. receiptTrie: The Keccak 256-bit hash of the root node of the trie structure populated with the receipts of each transaction in the transactions list portion of the block. 102 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: 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

Create successful ePaper yourself

Delete template?

Save as template?