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
Eugene Kim 75a92d7b10 Add field names to StakeInfo field init 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 [sc] enable faucet for all shards 6 years ago
contract_test.go [cleanup] remove peers variable from consensus New function 6 years ago
demo_contract.go [lint] fix ineffassign #708 6 years ago
node.go Merge pull request #724 from chaosma/chao-wip 6 years ago
node.md Some adhoc cleanup 6 years ago
node_genesis.go [lint] fix misspell #708 6 years ago
node_handler.go Merge pull request #724 from chaosma/chao-wip 6 years ago
node_handler_test.go [cleanup] remove peers variable from consensus New function 6 years ago
node_newblock.go [log] disable huge debug log in leader 6 years ago
node_syncing.go debug beacon sync not stable issue 6 years ago
node_test.go [cleanup] remove peers variable from consensus New function 6 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
service_setup.go Merge pull request #688 from harmony-one/ricl-peers 6 years ago
staking.go Add field names to StakeInfo field init 6 years ago
staking_test.go [cleanup] remove peers variable from consensus New function 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.