Core Member David Moss shares update in Github Dawn2.x and Dawn 3.0 has been merged into github Master branch
Refers to Thomas latest PostChange the Way we forcast
New Change
message->codescopeauto-assign, no need assign manually
New Features:
- Deferred Transactions
- Staking Pools
- New Currency Contract
- New Token Standard
https://testnet1.eos.io/ Currrent Testnet still running Dawn 2.0x
Kev mentioned Dan's explanation of DPoS = BFT
Summary of the Video
DPoS: Delegated Proof of State BFT: Byzantine Fault Tolerance
Goals: decentralized power:
- no censorship over the inclusion of transactions
- applying state machine to arrive at the consensus state
Consensus Algorithm
- latency to first confirmation
BFT:
disagreements -> Byzantine Failure / Half General Attack
Generate Cryptographic proofs -> who is byzantine Generals are / who is at fault
-> Penalize the party (forfeit bond / exclude from community) -> No longer block producers
Process Explanations: traditional BTS & Steemit
(ignore election process)
- every 3 sec, one bp, one block
- gap when one BP down
Ensure Honesty & Sustainability
Methods 1 Longest Chain is the Consensus Chain
21 bp -> full speed -> long chain
10 bp -> half speed -> shorter chain
Only when the new chain's length longer than(equal cannot) current chain, switch to new chain.
Model works even 1 bp(honest)
- support election
- elect new bp
Methods 2 Last Irreversible Block (in Steemit)
2/3 of bp built upon
Prevent longer range attack avoid sb got old key, and create alternative blockchain.
Analogy: software download
In reality:
99% participation: like Steemit & BitShares enjoy
- track in
dyanmic_global_property_object - on disk
- to LIB when open db
Steemit and BitShares's depending states: 45secs on average, take 14 out of 21
Our EOS Go Admins:
EOS Go Admins Youtube Channel
Phishing Alert
Deterministic Machine is Turing Machine, but vice versa not necessary
