Latest Posts
Update of methodology part
This update post out the methodology part of the final project
• Straggler protocol
This straggler protocol is introduced to handle the situation when the verification module takes too long to verify, i.e., to access external databases. The protocol first introduces priority level into verification results (Accept:1, Pending: 2, Reject:3, from low to high respectively) to make the final verification decision. Pending message is sent when the time spent in verification exceeds the time constraint as {RESULT, s, h, Pending, ni}
When final result is pending, all other nodes send back their verification with signature and ask client to re-submit the transaction with all the verifications, since those verifications will be skipped in the next run. Intuitively, Consensus leader under such circumstances will not add the pending transactions into the block...
Update of intro part
The Cross-enterprise trading systems hold a stringent requirement for its infrastructure to tackle an enormous amount of transactions among mutually untrusted parties. Such requirements include, but are not limited to, a throughput high enough to handle all the transactions, an almost instant time for ledger-recording and, the robustness against various kinds of system faults.
A Blockchain is a distributed database where the nodes are communicating using a p2p network. Blocks, each containing a batch of transaction records, are added tail-to-tail into the chain. As shown in Fig. 1, every block also includes a cryptographic hash of the previous block, and the entire chain is therefore protected from tampering its content.