From 6a6fefc352f010cb33850bad7007653ae6103f52 Mon Sep 17 00:00:00 2001 From: james-prysm Date: Wed, 5 Apr 2023 08:40:27 -0500 Subject: [PATCH 1/6] update page with corrected link --- ...-signature-aggregation-and-cryptography.md | Bin 2193 -> 2033 bytes 1 file changed, 0 insertions(+), 0 deletions(-) diff --git a/website/docs/how-prysm-works/bls-signature-aggregation-and-cryptography.md b/website/docs/how-prysm-works/bls-signature-aggregation-and-cryptography.md index 87c862884fb2010918cce4f941c0c28889de5a75..232cd5be93092e46f28df33f4cb73a925fef1014 100644 GIT binary patch delta 88 zcmbOz_>q6ZQdXamj8ui_q@3asg`CW!qQs)gSdEO5l7eC@ef{*zl8n+Mz2y8{{o>Ms nqQtz!lFaZ5QJd~$uaT`Dzs(Gn-f9+0U4o9FgvdGHuO9+(~GqcXW$HooU8c;3;_Xo zmA?OS{jvQ1TD&{tsSx)Gw~tTQOUTN=XwD?X=hbMI>rL04#Kx)L`4qZ5rovp(3%zx{ z)-{GyV53w>6ceW~R*N(gDqZCc59!P|mMxAGVF?@t@xtiC44 Date: Wed, 5 Apr 2023 22:03:01 -0500 Subject: [PATCH 2/6] updating to see if github shows correctly --- ...-signature-aggregation-and-cryptography.md | Bin 2033 -> 2028 bytes 1 file changed, 0 insertions(+), 0 deletions(-) diff --git a/website/docs/how-prysm-works/bls-signature-aggregation-and-cryptography.md b/website/docs/how-prysm-works/bls-signature-aggregation-and-cryptography.md index 232cd5be93092e46f28df33f4cb73a925fef1014..400720781fc7f02675b5fa46a7f6f736a8ea7868 100644 GIT binary patch delta 40 tcmey!|Av2q853jGWOJr)Alc89wfPs*a*)6xR(}?S#JrTvKUse;0st)#4(I>? delta 46 zcmaFE|B-)#853jiWOJr)Alc89#mKPvC)09}&_Y&!4m~cefTGIc+|6HDe=q_7ZN?AV From b6a63f6b3ff89f1f0a455469e4978b8f1571f783 Mon Sep 17 00:00:00 2001 From: james-prysm Date: Wed, 5 Apr 2023 22:06:44 -0500 Subject: [PATCH 3/6] removing interface code in favor of just going to the blst library url. --- .../bls-signature-aggregation-and-cryptography.md | 11 ++--------- 1 file changed, 2 insertions(+), 9 deletions(-) diff --git a/website/docs/how-prysm-works/bls-signature-aggregation-and-cryptography.md b/website/docs/how-prysm-works/bls-signature-aggregation-and-cryptography.md index 400720781..cc7d1b10d 100644 --- a/website/docs/how-prysm-works/bls-signature-aggregation-and-cryptography.md +++ b/website/docs/how-prysm-works/bls-signature-aggregation-and-cryptography.md @@ -4,7 +4,7 @@ title: BLS cryptography sidebar_label: BLS cryptography --- -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. +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 popularized within the tech community by the [Dfinity Project](https://dfinity.org/), whom utilized BLS to create a source of distributed randomness through a mechanism called “threshold relaying”. @@ -14,14 +14,7 @@ The BLS specification used by Ethereum can be found in the [official specificati 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 utilizes the [blst library](https://github.com/supranational/blst) for bls signatures and 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 -``` +Prysm utilizes the [blst library](https://github.com/supranational/blst) for bls signatures. import {RequestUpdateWidget} from '@site/src/components/RequestUpdateWidget.js'; From acfb041ca0e70feb5b7feb4b7ebc38609bf08028 Mon Sep 17 00:00:00 2001 From: james-prysm Date: Wed, 5 Apr 2023 22:11:10 -0500 Subject: [PATCH 4/6] adding header widget --- .../bls-signature-aggregation-and-cryptography.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/website/docs/how-prysm-works/bls-signature-aggregation-and-cryptography.md b/website/docs/how-prysm-works/bls-signature-aggregation-and-cryptography.md index cc7d1b10d..1e842ca03 100644 --- a/website/docs/how-prysm-works/bls-signature-aggregation-and-cryptography.md +++ b/website/docs/how-prysm-works/bls-signature-aggregation-and-cryptography.md @@ -3,6 +3,9 @@ id: bls-cryptography title: BLS cryptography sidebar_label: 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](../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. From bc6f0851855c2c5102e5cda8061dc886927127d2 Mon Sep 17 00:00:00 2001 From: james-prysm Date: Wed, 5 Apr 2023 22:31:03 -0500 Subject: [PATCH 5/6] test --- website/docs/how-prysm-works/keymanager-api.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/website/docs/how-prysm-works/keymanager-api.md b/website/docs/how-prysm-works/keymanager-api.md index 9c09200ff..1792b6de8 100644 --- a/website/docs/how-prysm-works/keymanager-api.md +++ b/website/docs/how-prysm-works/keymanager-api.md @@ -12,6 +12,8 @@ Prysm supports the official [Keymanager APIs](https://github.com/ethereum/keyman All Prysm Validator Client APIs require the use of the `--web` flag. +Quicktest + Please refer to the "local keystores APIs" to manage locally stored validator keys. Please refer to the "remote keystores APIs" to manage public key settings for Web3Signer; go to our Web3Signer docs page for more information. From 98651d499450bf65d51e7f7b0e6ef1ca8d271322 Mon Sep 17 00:00:00 2001 From: james-prysm Date: Wed, 5 Apr 2023 22:37:17 -0500 Subject: [PATCH 6/6] rolling back quick test --- website/docs/how-prysm-works/keymanager-api.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/website/docs/how-prysm-works/keymanager-api.md b/website/docs/how-prysm-works/keymanager-api.md index 1792b6de8..9c09200ff 100644 --- a/website/docs/how-prysm-works/keymanager-api.md +++ b/website/docs/how-prysm-works/keymanager-api.md @@ -12,8 +12,6 @@ Prysm supports the official [Keymanager APIs](https://github.com/ethereum/keyman All Prysm Validator Client APIs require the use of the `--web` flag. -Quicktest - Please refer to the "local keystores APIs" to manage locally stored validator keys. Please refer to the "remote keystores APIs" to manage public key settings for Web3Signer; go to our Web3Signer docs page for more information.