Add conclustions and open challenges

SemSEreport/exercises.tex

@@ -131,7 +131,6 @@ We attempted to implement an automatic weakness detection pipeline by using a mu
 	\item \textbf{Slither}: A highly useful tool that offers a large static analysis toolkit for solidity, it not only allows the extraction of contract data like storage layouts but also automatic scanning for common weaknesses. Although it did not seem to be able to detect SWC-124, the storage layout functionality was used extensively by our team.
 \end{itemize}
 
-
 \section{Exploit Creation}\label{sec:exploit-creation}
 
 \subsection{Short recap of weakness definitions}
@@ -193,7 +192,7 @@ Using the heuristics above, we were not able to find a contract that is vulnerab
 
 \subsection{Non-exploitable contracts}
 
-\noindent Solidity files that contained no contracts:
+\noindent Solidity files that contained no contracts, just libraries, that would not introduce SWC-124 to the contracts using them as per the heuristics:
 
 \begin{itemize}
 	\item AuctionLib.sol
@@ -213,7 +212,7 @@ Using the heuristics above, we were not able to find a contract that is vulnerab
 	\item GovernmentAlpha.sol
 	\item HedgeSwap.sol
 	\item HermesImplementation.sol
-	\item IMETACoin223Token\_13.sol - had this contract been compiled with solidity under 0.8.0, it could have been vulnerable.
+	\item IMETACoin223Token\_13.sol - had this contract been compiled with solidity under 0.8.0, it would have been vulnerable.
 	\item UniswapV3PoolAdapter.sol
 	\item UserDeposit.sol
 	\item WPCMainnetBridge.sol
@@ -223,10 +222,19 @@ Using the heuristics above, we were not able to find a contract that is vulnerab
 
 \subsection{Conclusions}
 
+We have proposed initial heuristics which can show us whether a contract is vulnerable to SWC-124. They are easy to understand and apply even in large contracts.
+We have demonstrated an example workflow that uses the tool Slither as a data-gathering aid and applies the heuristics. As a result of this workflow, we were unable to find
+vulnerable specimen from the examples provided.
+
 \subsection{Lessons learned: what works, what doesn't}
 
+% TODO: Do we have something to add?
+
 \subsection{Open challenges}
 
+The initial heuristics are easy to add to a static code analysis tool, such as Slither.
+Afterwards, it can be used to develop a dataset of vulnerable or non-vulnerable samples, which, alongside with manually verified contracts, can be used to improve or expand the heuristics.
+
 \bibliography{exercise.bib}
 
 \end{document}