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.
1827 Commits
46 Branches
191 Tags
64 MiB
 
 
 
Tag: Branch: Tree: ea0578dedf
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'ea0578dedf'
${ noResults }
woop/internal/beaconchain
History
Eugene Kim 4a2e1e2110
Move Host interface into the top-level p2p package 		6 years ago
..
libs Move Host interface into the top-level p2p package 6 years ago
rpc use Info to replace nodeInfo in pingpong 6 years ago
README.md adding readme 6 years ago

README.md

The beaconchain package currently is a centralized service that allocates every potential new node (uses newnode package) a specific shard. If N is the number of shards, supplied as a parameter at bootup, then first N joining nodes are assigned to be the leaders of those N shards. The nodes that come after that are then assigned shards based on their order of entry. In the future, the generation of randomness would be decentralized. Such randomness would be provided to a new node once its PoS has been verified and then the node would be able to calculate its own shard automatically.