From 3c11a4dc020a21c2cdbf8b667bcec2be717e08ba Mon Sep 17 00:00:00 2001 From: Hsiao-Wei Wang Date: Wed, 13 May 2020 12:56:50 +0800 Subject: [PATCH] Fix `AggregateVerify` param name: `message` -> `messages` Co-authored-by: Danny Ryan --- specs/phase0/beacon-chain.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/specs/phase0/beacon-chain.md b/specs/phase0/beacon-chain.md index 3d24ff043..1c88c2a4c 100644 --- a/specs/phase0/beacon-chain.md +++ b/specs/phase0/beacon-chain.md @@ -609,7 +609,7 @@ def bytes_to_int(data: bytes) -> uint64: - `def Verify(PK: BLSPubkey, message: Bytes, signature: BLSSignature) -> bool` - `def Aggregate(signatures: Sequence[BLSSignature]) -> BLSSignature` - `def FastAggregateVerify(PKs: Sequence[BLSPubkey], message: Bytes, signature: BLSSignature) -> bool` -- `def AggregateVerify(PKs: Sequence[BLSPubkey], message: Sequence[Bytes], signature: BLSSignature) -> bool` +- `def AggregateVerify(PKs: Sequence[BLSPubkey], messages: Sequence[Bytes], signature: BLSSignature) -> bool` Within these specifications, BLS signatures are treated as a module for notational clarity, thus to verify a signature `bls.Verify(...)` is used.