* [staking] Sign staking transaction with standalone staking-iterate CLI
* [staking] golint
* [staking] Fix for build, move transaction under staking/types
* [staking] Send RLP signed staking transaction, receive in RPC
* [staking] Organize staking packages, send over specific staking message
* [staking] Satisfy jenkins build in temp CLI staking-iterate
* [staking] Adjust naming of types
* [staking] Fold separate package into types as initial creation by RJ
[cleanup] remove is_genesis flag
Signed-off-by: Leo Chen <leo@harmony.one>
[nodetype] add nodetype to replace is_explorer
Signed-off-by: Leo Chen <leo@harmony.one>
fix beacon sync channel blocking issue
use lastMileMux to protect lastMileBlock queue to avoid potential blocking; use sleep instead of ticker
Fix the beacon committee check
[release] add release action to go_executable_build.sh
Signed-off-by: Leo Chen <leo@harmony.one>
[node.sh] add -d option
-d download only
Signed-off-by: Leo Chen <leo@harmony.one>
[node.sh] add -T node_type option
-T node_type support node type (validator/explorer)
Signed-off-by: Leo Chen <leo@harmony.one>
[node.sh] backward compatible with older harmony binary
Signed-off-by: Leo Chen <leo@harmony.one>
[node.sh] support -i shard_id option
-i shard_id specify shard_id, this is applicable only to
explorer node
Signed-off-by: Leo Chen <leo@harmony.one>
Revisited api
Fix rpc integration
address some minor issues in comments and code
addressed comments on others' buckets
Add Global Access to OS Temp Directory Variable and Move DHT Files Into Temp Directory
Add flag to disable signers
Fix explorer handler
Fix explorer handler
fix explorer for loop
add shardID information in getTransactionByHash RPC CALL
Add CXReceipt RPC call; Add indexing for CXReceipt by TxHash
use only one index for CXEntryLookup; use shardID instead of fromShardID in RPC returned results
This is to allow for all 4 shards to roll into CrossTxEpoch and start
having cross-shard-transaction-related fields in block header/body
before the fields are actually used. Otherwise, if a shard A enters
CrossTxEpoch before shard B does and sends a cross-shard receipt to
shard B, it cannot be processed because chain B still lacks the incoming
receipts field.
This could occur as a result of database corruption or database update
race, where transaction → (blockHash, blockNum, txIndex) lookup succeeds
but the body for blockHash is not (yet) in the database.
Follow the same strategy for header versioning, except put everything
into the same "./core/types" package – for now. Adaptation of the
existing code outside the package to come next.
For now, follow header version (v0 or v1). Later header/block versions
should become independent: Blocks should have their own epoch-based
versioning schedule, and it should be possible to bump header version
without bump block version, and vice versa.
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.