From f69b3823e98701af0f5e8bf3f6e07aa3d26ac0f8 Mon Sep 17 00:00:00 2001
From: librelois <c@elo.tf>
Date: Sat, 22 May 2021 18:39:14 +0200
Subject: [PATCH] [RFC17] comment encoding must be in base64 without padding

---
 rfc/0017_transaction_comment_encryption.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/rfc/0017_transaction_comment_encryption.md b/rfc/0017_transaction_comment_encryption.md
index 6b7868a..574e923 100644
--- a/rfc/0017_transaction_comment_encryption.md
+++ b/rfc/0017_transaction_comment_encryption.md
@@ -104,7 +104,7 @@ It is recommended to randomly generate a random number of extra bytes to obscure
 
 ## Encoding in transaction document
 
-Encrypted message in encoded in base 64 in transaction comment directly (DUBP protocol already accept all base 64 characters).
+Encrypted message in encoded in base 64 (without padding) in transaction comment directly (DUBP protocol already accept all base 64 characters).
 
 ## Maximum message length
 
-- 
GitLab