From 810d8b3e79ca6ef8092b47e0f005c0c45a2c21c1 Mon Sep 17 00:00:00 2001 From: Ivan Ivanitskiy Date: Sun, 23 Jun 2019 16:01:44 +0300 Subject: [PATCH] indent fix --- README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 9878779..daef9b4 100644 --- a/README.md +++ b/README.md @@ -17,8 +17,9 @@ Here is the workflow: 1. The proof supplier uploads (data, proof) to the smart contract. 2. The user takes (data, proof) from the smart contract and sends it to the back end. 3. The back end checkes the proof. -4. a. If the proof is valid, it is stored by the back end with TRUE flag. Other users can see it in the front end and will not check this proof again. -4. b. If the proof is invalid, it is stored by the back end with FALSE flag. The user challenges this proof in the smart contract. In that case the user is sure that the proof is FALSE and thus the user will get the reward. +4. +- a. If the proof is valid, it is stored by the back end with TRUE flag. Other users can see it in the front end and will not check this proof again. +- b. If the proof is invalid, it is stored by the back end with FALSE flag. The user challenges this proof in the smart contract. In that case the user is sure that the proof is FALSE and thus the user will get the reward. To better understand the workflow, please review the scheme.