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
Leo Chen 96d3363d27 use sync.Map to avoid concurrent map read/write error 6 years ago
..
worker Break tie of core-consensus-core import cycle; add pRnd channel for consensus 6 years ago
README.md Add readme for /node 6 years ago
contract.go fix private key constant 6 years ago
node.go use sync.Map to avoid concurrent map read/write error 6 years ago
node.md fix format in node.md 6 years ago
node_genesis.go add constants 6 years ago
node_handler.go use sync.Map to avoid concurrent map read/write error 6 years ago
node_handler_test.go Say goodbye to Schnorr sig and kyber package and mark BLS done 6 years ago
node_newblock.go increase consensus timeout 6 years ago
node_syncing.go add beaconchain node state syncing (#502) 6 years ago
node_test.go Merge pull request #498 from LeoHChen/drg 6 years ago
p2p.go Move Host interface into the top-level p2p package 6 years ago
service_setup.go add beaconchain node state syncing (#502) 6 years ago
staking.go More constants to staking.go 6 years ago
staking_test.go Also move tests for staking_test.go 6 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.