Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update bls page #759
base: master
Are you sure you want to change the base?
Update bls page #759
Changes from all commits
6a6fefc80adcdb2a4ae64b6a63f6acfb041bc6f08598651d407121ecFile filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
A major obstacle for Ethereum in the effort to move into a [Proof-of -Stake](../terminology.md#proof-of-stake-pos) model was verifying cryptographic signatures efficiently enough to reach scalability expectations; for this task, **Boneh-Lynn-Shacham signatures \(BLS\)** were chosen. BLS allows for efficient signature aggregation and verification at scale using [Elliptic Curve cryptography](https://en.wikipedia.org/wiki/Elliptic-curve_cryptography). It was originally popularised within the tech community by the [Dfinity Project](https://dfinity.org/), whom utilised BLS to create a source of distributed randomness through a mechanism called “threshold relaying”. The BLS specification used by Ethereum can be found in the [official specifications repository.](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/beacon-chain.md#bls-signatures) ## How does it work? As mentioned, Ethereum uses the BLS signature scheme to facilitate secure cryptography within the protocol. This method allows [validators](../terminology.md#validator) to sign messages, and these resulting signatures are then aggregated and verified at scale. This enables a full [Proof-of-Stake](../terminology.md#proof-of-stake-pos) system with a massive number of [validators](../terminology.md#validator) to function efficiently in production. Prysm utilises a pure Go BLS [implementation](https://github.com/phoreproject/bls) for this initial testnet release. However, due to efficiency concerns, it will be replaced by a more performant implementation in the upcoming release \(likely in C++\). Prysm contains the following public BLS API which can be used across the project: ```go func (s *Signature) Verify(msg []byte, pub *PublicKey, domain uint64) bool func (s *SecretKey) Sign(msg []byte, domain uint64) *Signature func (s *Signature) VerifyAggregate(pubKeys []*PublicKey, msg []byte, domain uint64) bool func AggregateSignatures(sigs []*Signature) *Signature ``` import {RequestUpdateWidget} from '@site/src/components/RequestUpdateWidget.js'; <RequestUpdateWidget docTitle="BLS cryptography"/>import {HeaderBadgesWidget} from '@site/src/components/HeaderBadgesWidget.js';
A major obstacle for Ethereum in the effort to move into a Proof-of -Stake model was verifying cryptographic signatures efficiently enough to reach scalability expectations; for this task, Boneh-Lynn-Shacham signatures (BLS) were chosen.
BLS allows for efficient signature aggregation and verification at scale using Elliptic Curve cryptography. It was originally popularized within the tech community by the Dfinity Project, whom utilized BLS to create a source of distributed randomness through a mechanism called “threshold relaying”.
The BLS specification used by Ethereum can be found in the official specifications repository.
How does it work?
As mentioned, Ethereum uses the BLS signature scheme to facilitate secure cryptography within the protocol. This method allows validators to sign messages, and these resulting signatures are then aggregated and verified at scale. This enables a full Proof-of-Stake system with a massive number of validators to function efficiently in production.
Prysm utilizes the blst library for bls signatures.
import {RequestUpdateWidget} from '@site/src/components/RequestUpdateWidget.js';