Recently, the developer team at Sigma Prime also known as SigP took to Twitter to announce an update on the recently launched open source Ethereum 2.0 client called ‘Lighthouse’. The team discussed the progress in the project and laid out the roadmap for future work.
In the official blog post, the team stated that the post covers the progress in the Lighthouse project carried out in the past two weeks. The team has successfully implemented the pre-processing of the Block. Lighthouse update 1 includes a Boneh–Lynn–Shacham [BLS] aggregate signature. However, the team stated that the BLS signatures are still unsafe.
A simpleSerialize [SSZ] has been implemented. A draft specification of the SSZ produced by SigP has been merged into the Ethereum 2.o specification repository.
Furthermore, they explained the block pre-processing implementation. SigP stated that it has been the most significant achievement implementing and benchmarking it.
The block pre-processing involves the process of accepting a serialized block from an untrusted source and “deeming” it valid. According to the team, the pre-processing stage is required to reduce the impact of malicious blocks on the system. The processing will be quick and inexpensive.
They further explained that the pre-processing stage involves many steps like validating the attestations, processing the attestations concurrently, de-serialization of records before validation to fail in cases of “bad attestations”. They added:
“A single invalid attestation invalidates the entire block so we avoid de-serializing them all up-front.”
The team also stated that they have performed pre-processing benchmarks. With the implementation of the BLS aggregate signatures, the team was able to use real signature verification and provide the pre-processing benchmarks.
According to the team, there has been some confusion in the Ethereum community regarding the exact BLS aggregation scheme used in the Ethereum 2.0 specification. SigP stated:
“Ethereum 2.0 uses the ‘old’ scheme described in BGLS03. The new scheme mitigates the “rouge-key attack” and allows signatures across distinct messages but is slower. Eth 2.0 protects against the rouge-key attack by requiring a bls_proof_of_possession on validator registration and naturally requires all signed messages to be identical (non-distinct).”
They added that the old scheme was faster and they did not require the features of the ‘new’ scheme.
Over the coming weeks, the team stated that they will be working on fuzzing framework, libp2p daemon, state transition logic. They will also be working on an implementation of the Friendly Finality Gadget [FFG] fork choice rule.
Subscribe to AMBCrypto’s Newsletter
Monero [XMR] transaction fees plummet to 2 cents post the ‘Bulletproof’ hardfork
Ethereum [ETH] only accounted for 4% of Genesis trading loan book by end of September 2018
TAP releases new alpha version of their app
Cardano [ADA] continues its developmental roll; prices reflect the same
Tron [TRX] Technical Analysis: Bull pushing strong to power down bear in the short-term
Ripple partner Santander to adopt SWIFT GPI: What does it mean for XRP-powered xRapid?
XRP can now be used as collateral for $2 million instant loans
Ripple partner Santander goes live with SWIFT’s Global Payments Innovation
Bitcoin [BTC] is not going to disappear, but Ethereum [ETH], XRP and others are “going bust”, says Roubini
Tron [TRX/USD] Technical Analysis: The bulls have charged attack on the bear
Ripple and XRP rise in tandem; banking sector lays down the path for the cryptocurrency’s developments
XRP is not a security and the SEC will recognize it, says Ripple’s Chief Market Strategist
Exosis [EXO] to emerge as a rising star as one-stop solution for the cryptocurrency ecosystem
XRP sentiment gets bullish push as Ripple’s market strategist teases worldwide adoption of xRapid