PoS_EVM
/
woop
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
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.
6335 Commits
46 Branches
191 Tags
64 MiB
 
 
 
Tag: Branch: Tree: 6741f07de3
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '6741f07de3'
${ noResults }
woop/node
History
Leo Chen 54912716ce
[validation] move newview validation to p2p layer 		4 years ago
..
worker cleanup and fixes during audit (#2931) 5 years ago
README.md Add readme for /node 6 years ago
api.go [viewchange] encapsulate both viewID and viewChangeID 4 years ago
double_signing.go [staking][validation][protocol] (#2396) 5 years ago
node.go [validation] move newview validation to p2p layer 4 years ago
node.md [service][node] Project Tech debt clean up, remove wallet (#2664) 5 years ago
node_cross_link.go Remove all wrong usage of singlr flight; also fix voting power cache key (#3229) 4 years ago
node_cross_shard.go cherrypick log level change 5 years ago
node_explorer.go Add back multi-sig support and fix the multi-sig check for harmony nodes (#3337) 4 years ago
node_genesis.go Rosetta Implementation - pt2 (Stage 3.2 of Node API Overhaul) (#3312) 4 years ago
node_handler.go Increase crosslink catching rate, expect to have equillibrium at 5 block delay (#3333) 4 years ago
node_handler_test.go Bind public keys into private key wrapper (#3208) 4 years ago
node_newblock.go [viewchange] encapsulate both viewID and viewChangeID 4 years ago
node_syncing.go Rosetta Implementation - pt2 (Stage 3.2 of Node API Overhaul) (#3312) 4 years ago
node_test.go Move BLS related wrapper structure into a separate package (#3209) 4 years ago
service_setup.go [Explorer] Add explorer node in sync check (#3215) 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.