From 12063cdc957c898e0d140d29a7da07a0cb3023b8 Mon Sep 17 00:00:00 2001
From: Vincent Texier <vit@free.fr>
Date: Thu, 22 Apr 2021 08:56:30 +0000
Subject: [PATCH] clarify DEWIF Format chapter and Base64 usage

---
 rfc/0013_Duniter_Encrypted_Wallet_Import_Format.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/rfc/0013_Duniter_Encrypted_Wallet_Import_Format.md b/rfc/0013_Duniter_Encrypted_Wallet_Import_Format.md
index 43bf10a..99d29d1 100644
--- a/rfc/0013_Duniter_Encrypted_Wallet_Import_Format.md
+++ b/rfc/0013_Duniter_Encrypted_Wallet_Import_Format.md
@@ -33,8 +33,9 @@ So currently a public key for DUBP is to be understood as an Ed25519 public key.
 
 DEWIF is an inter-operable and secure format for any DUBP wallet.
 
-DEWIF format is a base64 string.  
-This base64 string encodes a sequence of bytes whose structure is defined below.
+DEWIF format is a sequence of bytes whose structure is defined below. It can be used as raw binary data where suitable.  
+
+To use the binary data in a text context (email, ftp text transfer, json, html, etc) it is recommended to encode the binary data in a Base64 string. The Base64 string is used here to check the binary data validity. 
 
 ## Dewif bytes structure
 
-- 
GitLab