From 851772ea1ed3894d173144264706064a697deb9f Mon Sep 17 00:00:00 2001
From: Logan oos Even <46396513+Logan007@users.noreply.github.com>
Date: Wed, 29 Jul 2020 15:13:27 +0545
Subject: [PATCH] updated CRYPTO.md

revision
---
 doc/CRYPTO.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/CRYPTO.md b/doc/CRYPTO.md
index 9e9dd67..3aebd1d 100644
--- a/doc/CRYPTO.md
+++ b/doc/CRYPTO.md
@@ -125,7 +125,7 @@ In case of a PACKET-type, it is succeeded by the fields depicted below:
 ```
 ### Encryption
 
-If enabled (`-H`), all fields but the payload (which is handled seperately as outlined above) get encrypted using SPECK in CTR mode. As packet headers need to be decryptable by the supernode and we do not want to add another key (to keep it a simple interface), the community name serves as key (keep it secret!) because it is already known to the supernode.
+If enabled (`-H`), all fields but the payload (which is handled seperately as outlined above) get encrypted using SPECK in CTR mode. As packet headers need to be decryptable by the supernode and we do not want to add another key (to keep it a simple interface), the community name serves as key (keep it secret!) because it is already known to the supernode. The community name consists of up to 16 characters (well, 15 + `0x00`), so key size of 128 bit is a reasonable choice here.
 
 The scheme applied tries to maintain compatibility with current packet format and works as follows: