16 Commits (7736ec48e9591a1db10c1cb8ecff8dc5ebf0c080)

Author	SHA1	Message	Date
Konstantin	97eb8d972f	Go vet fixed.	3 years ago
Jong Hyuck Won	b9843abde5	RPC for staking txns and txns history queries (#2554) ... * staking txn. look up by hash fix on api backend rawdb storage * node explorer staking txn 'history' RPC layer support * fix unit test * add error log when explorer node db instance cannot be fetched * revert unwanted merge changes during rebase * use already encoded tx message fields for get staking txn rpc * update explorer node storage service for staking txns * use hex string for staking transaction data field * revert transaction pool apiv1 changes	5 years ago
Daniel Van Der Maden	eb8c9bb0f7	Add stressnet config ... * Add stressnet config to main.go * Add stressnet config internals	5 years ago
Daniel Van Der Maden	6d9a2e39a0	Add partner config ... * Add partner config to main.go * Add partner config internals * Refactor and add partner logic to genesis node	5 years ago
Eugene Kim	02ba0b309c	Fix cross-TX header introduction glitch ... Commit e79ba5fe88 introduced an off-by-one error which caused CX-enabled header to be introduced one epoch later than expected, i.e. at CrossTxEpoch + 1, where it should be CrossTxEpoch. This was caused by a vague, confusing naming of IsCrossTx(epoch) function of ChainConfig: The name did not clarify whether it meant introduction of CX-enabled header and processing of ingress receipts (which occurs at CrossTxEpoch) or acceptance of cross-shard transactions (which occurs at CrossTxEpoch+1). Introduce and use params.(*ChainConfig).HasCrossTxFields which handles the former case.	5 years ago
Rongjian Lan	e79ba5fe88	Make shard chain follow beacon chain's epoch after stakingEpoch	5 years ago
Rongjian Lan	33a452fa4e	Revert local change	5 years ago
Rongjian Lan	bad9c62922	Bug fixes	5 years ago
Rongjian Lan	bde9d38ed1	Add missing staking related core code; and add some basic rpcs	5 years ago
Rongjian Lan	77ff9d422d	test code	5 years ago
chao	0c020d8f6a	add staking transaction field in v2 body; add v3 header for future fork	5 years ago
Eugene Kim	d5a4f4e4ad	Wire Pangaea chain config	5 years ago
Eugene Kim	f7900cb908	Use v1 header for CrossTxEpoch	5 years ago
Eugene Kim	8ac042ad9f	Move v1.Header → v2.Header	5 years ago
Rongjian Lan	b00903279f	Fix NewHeader epoch setting	5 years ago
Eugene Kim	d35cba2d44	Move block.HeaderInterface → blockif.Header ... This is to make it possible to use the Header interface from implementations without causing cyclic imports.	5 years ago
Eugene Kim	bc711829b8	Fix goimports	5 years ago
Eugene Kim	8ac058bb2e	Version headers ... block.Header is now a lightweight wrapper around an embedded HeaderInterface value, which is implemented by both v0 and v1 headers. It inherits all methods from the wrapped HeaderInterface, except it overrides EncodeRLP, DecodeRLP, and Hash to handle tagged-RLP encoding/decoding. (block.HeaderRegistry is the tagged RLP registry for versioned headers.) A ripple effect is that header instance creation now requires knowledge of epoch. This logic is handled by blockfactory. blockfactory.Factory is the interface, implemented by blockfactory.factory type. It uses a chain config to pull in the right epoch for the right type. As a convenience, blockfactory.NewTestHeader creates a new test-purpose headers. Use this in contexts where the implied chain config is TestChainConfig or the chain config does not matter. Miscellaneous changes: - block.HeaderFieldSetter now lives in its own file. - The functionality of block.NewHeaderWith has been replaced by the (*block.Header).With method. The accompanying unit tests for (*block.Header).EncodeRLP and (*block.Header).DecodeRLP() are the cross-sectional unit tests for the functionality added by this. They make sure that v0 header is encoded/decoded without tagged RLP envelope (compatibility mode), and v1 header is encoded/decoded with one. See comments of the RLP byte sequence for differences.	5 years ago