Add paragraph about conclusive result validating base hypothesis

...regarding the usefulness of running pre-existing tests
by leveraging symbolic execution means offered by klee
in the context of smart contract quality assurance testing

docs/30-latest-mvp-for-safepkt-smart-contract-verifier.md

@@ -259,6 +259,16 @@ See this issue from project-oak/rvt about [`cargo veriy` being incompatible with
  - Port of the verifier as an extension for [Jetbrains products](https://plugins.jetbrains.com/docs/intellij/getting-started.html)  
  - Port of the verifier as a [Sonarqube plugin](https://docs.sonarqube.org/latest/extend/developing-plugin/)  
 
+### Conclusive results
+
+The default branch (`buggy-smart-contract`) available from SafePKT smart contract example,  
+offers a clear demonstration of how to leverage SafePKT verification tools,  
+in order to discover issues with a rust-based Smart Contract.
+
+The smart contract example here is based on [ERC20 technical standard](https://fr.wikipedia.org/wiki/ERC20), 
+and can be found in the following repository:  
+https://github.com/LedgerProject/safepkt_smart-contract-example
+
 ## System stability, maintainability
 
 ### Installation
@@ -280,7 +290,6 @@ A working strategy consists in ensuring that
  - `rvt` belongs to [`docker` group](https://docs.docker.com/engine/install/linux-postinstall/)
  - `www-data` is the user running the nginx instance
 
-
 ### Ballpark performance
 
 As of today, the verification process takes about 90s when executed from our dedicated server for a suite of about 30 tests without fuzzing.