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.
50 Commits
46 Branches
191 Tags
64 MiB
 
 
 
Tag: Branch: Tree: 212c86a784
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '212c86a784'
${ noResults }
Minh Doan 212c86a784
add transaction, utils, utils_test. 		7 years ago
aws-code fixing typo 7 years ago
aws-scripts WIP for amazon codedeploy 7 years ago
aws-setup app spec 7 years ago
consensus Refactor consensus code into leader part and validator part 7 years ago
p2p Add more comments, fix type and styling 7 years ago
.gitignore Add .gitignore file 7 years ago
AppSpec.yml app spec 7 years ago
README.md addressing RJ comments 7 years ago
benchmark_node.go Fix send_tnx to only send START_CONCENSUS to leader; Add consensus signature threshold counting 7 years ago
block.go add data structure for blockchain 7 years ago
blockchain.go add data structure for blockchain 7 years ago
deploy.sh remove mode argument as that is derived 7 years ago
ipList.txt working code to initialize consensus 7 years ago
kill_node.sh more files 7 years ago
node.go Add more comments, fix type and styling 7 years ago
send_tnx.sh Fix send_tnx to only send START_CONCENSUS to leader; Add consensus signature threshold counting 7 years ago
transaction.go add transaction, utils, utils_test. 7 years ago
utils.go add transaction, utils, utils_test. 7 years ago
utils_test.go add transaction, utils, utils_test. 7 years ago

README.md

Harmony Benchmark

Usage

./deploy.sh ipList.txt ./send_txn.sh

References

https://github.com/lightningnetwork/lnd

New Plan:

Done

TODO

  • implement block of transactions, instead of individual generators
  • instead of consume used leader.send function
  • understand when the program terminates and why we don't end up writing all the txns
  • simplify code, if it might be a overkill
  • Read go concurrency to setup transaction channel and pour those txns (randomString) into a queue from where the leader node can read it in chunks.

Readings