GSoC-2021.md

@@ -111,7 +111,7 @@ B[Fetch url using Non-Tor client] -->M[Remove GDPR]
 C--NO--->D{check whether <br> tor returns 4xx or 5xx <br>error codes}--YES----->F(Tor Block Error)
 E4--No---->E[/Additional Tests <br> DOM checks/]
 E-->E1[DOM Checks <br> Percentage of differnce in DOM nodes]
-E-.->E2[Consensus Module]
+E-.->E2[Consensus Module (Lite)]
 E------>E3[Captcha Check] %% This will use the fact of the request path containing captcha in the url itself
 E4{If the <br> Redirected website <br>returns error}--yes------->F
 E1-->G{if <br> score >0}
@@ -142,3 +142,9 @@ style NT stroke-width:3px,fill:#FFFF00
 
 For more details one you could look into the [Experimental code](https://raw.githubusercontent.com/Hackhard/Fetcher/main/status%20code/test_run4/tr.py) and it's [output](https://raw.githubusercontent.com/Hackhard/Fetcher/main/status%20code/test_run4/tr_bash_output) to gain an even more insight.
 
+
+### Consensus Module (Lite):
+
+![image](uploads/21de2095ef9a6ca6cce11c69930619d8/image.png)
+
+This is the tabular form of the logic for the current version of `Consensus Module` that I would follow, that would be called lite because it's using proxies + non-tor Dom values to check with the tor values, providing a better statistical result when the tor isn't blocked fully (status code error) and also will be using `proxies` rather than `Vpn`, as they are easier to integrate and a simple Google search can give us a list of many proxies according to different regions which are updated too.