From 7c10715c1a7d47c161b70a470f5227f7b4a58400 Mon Sep 17 00:00:00 2001 From: hzysvilla Date: Tue, 20 Feb 2024 19:24:20 +0800 Subject: [PATCH] fix a syntax error. --- website/docs/devtools/net-design.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/devtools/net-design.md b/website/docs/devtools/net-design.md index 40f1524f4..348f1e62c 100644 --- a/website/docs/devtools/net-design.md +++ b/website/docs/devtools/net-design.md @@ -52,7 +52,7 @@ In SECIO, channel negotiation begins with a proposal phase, where we exchange i ## Current Status in Prysm -Currently in Prysm we do use SECIO for securing sessions, and a Peer’s identity is generated using the Secp256k1 curve. However we haven’t enforced that the ephemeral key generation curve, cipher for encryption and hash algorithm are the ones that are required for interoperability We would need to strictly define these when peers are making their initial proposal. If they do not adhere to them, we reject and disconnect from those peers. +Currently in Prysm we do use SECIO for securing sessions, and a Peer’s identity is generated using the Secp256k1 curve. However we haven’t enforced that the ephemeral key generation curve, cipher for encryption and hash algorithm are the ones that are required for interoperability. We would need to strictly define these when peers are making their initial proposal. If they do not adhere to them, we reject and disconnect from those peers. **Protocol Negotiation** We must use the multistream-select specification with id [/multistream/1.0.0](https://github.com/multiformats/multistream-select/)