The core protocol of WoopChain
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
woop/node
chao 39214def83 improve cross tx receipts verification to avoid beacon sync dependency 5 years ago
..
worker Merge conflicts 5 years ago
README.md Add readme for /node 6 years ago
contract.go Migrate go-ethereum params into harmony/internal/params 5 years ago
errors.go add puzzle contract 6 years ago
node.go Merge branch 'master' of github.com:harmony-one/harmony into signing-fix 5 years ago
node.md Some adhoc cleanup 6 years ago
node_cross_shard.go improve cross tx receipts verification to avoid beacon sync dependency 5 years ago
node_error.go fix incomingReceipts storage; cherry pick from RJ's branch 5 years ago
node_explorer.go [log] set proper level for debug messages 5 years ago
node_genesis.go Merge header change 5 years ago
node_handler.go improve cross tx receipts verification to avoid beacon sync dependency 5 years ago
node_handler_test.go Add CrossLink, EIP155, and S3 fork 5 years ago
node_metrics.go NodeBalanceCounter -> NodeBalanceGauge, remove unnecessary stuff in metrics service 5 years ago
node_newblock.go Merge conflicts 5 years ago
node_syncing.go Merge cross-shard into master 5 years ago
node_test.go [pingpong] remove pong messages from discovery service 5 years ago
node_utils.go replace consensus blsAddr with new syncID for state syncing 6 years ago
p2p.go [cleanup] remove libp2p unicast support 6 years ago
rpc.go add current to the sharding structure for sdk 5 years ago
service_setup.go Merge branch 'master' of github.com:harmony-one/harmony into signing-fix 5 years ago
staking.go Move ShardState et al from ./core/types to ./shard 5 years ago
staking_test.go fix conflict 5 years ago

README.md

Node struct is the core entity that represents a network node participating in the Harmony protocol.

A node is the main message handler to all kinds of protocol messages such as consensus message, block sync, transactions etc. A node contains all the necessary references to other objects (e.g. blockchain object and consensus object) to handle the incoming messages.