woop/node at 14e017defc18d712a854f70104e173e6eea9c058 - woop

The core protocol of WoopChain

blockchain consensus woopchain bls distributed-ledger-technology pbft proof-of-stake sharding

History

Leo Chen b560f88978 [libp2p/consensus] p2p spamming defense This is a big PR merged many small commits together. We add the message validation function in libp2p layer. In the validation function, we check the following conditions 1) the p2p message is a valid consensus message 2) the p2p message sender has a valid public key 3) the sender's public key is in the current committee 4) log the number of invalid/valid messages After the validation, the valid messages will be forward to the network, while the invalid messages will be filtered out. The messages intended for the validator will be handled in the consensus layer. Signed-off-by: Leo Chen <leo@harmony.one>		4 years ago
..
worker	cleanup and fixes during audit (#2931 )	5 years ago
README.md	Add readme for /node	6 years ago
double_signing.go	[staking][validation][protocol] (#2396 )	5 years ago
node.go	[libp2p/consensus] p2p spamming defense	4 years ago
node.md	[service][node] Project Tech debt clean up, remove wallet (#2664 )	5 years ago
node_cross_link.go	Refactor bls public key into a wrapper (#3203 )	4 years ago
node_cross_shard.go	cherrypick log level change	5 years ago
node_explorer.go	[libp2p/consensus] p2p spamming defense	4 years ago
node_genesis.go	Remove unused code and add benchmark for consensus msg check (#3211 )	4 years ago
node_handler.go	[libp2p/consensus] p2p spamming defense	4 years ago
node_handler_test.go	Bind public keys into private key wrapper (#3208 )	4 years ago
node_newblock.go	Remove unused code and add benchmark for consensus msg check (#3211 )	4 years ago
node_syncing.go	Remove unused code and add benchmark for consensus msg check (#3211 )	4 years ago
node_test.go	Move BLS related wrapper structure into a separate package (#3209 )	4 years ago
rpc.go	[rpc][p2p] Expose peer connectivity (#2962 )	5 years ago
service_setup.go	Remove unused code and add benchmark for consensus msg check (#3211 )	4 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.