(doc) more details for contract instrumentation

book/documentation/CONCEPT.html

@@ -225,7 +225,6 @@ <h3 id="coverage"><a class="header" href="#coverage">Coverage</a></h3>
 <h3 id="contract-selectors"><a class="header" href="#contract-selectors">Contract selectors</a></h3>
 <p><strong>ink! contract selectors</strong> are unique identifiers for functions within ink! smart contracts. Selectors are derived from
 function signatures and are used to call specific functions within a contract deployed on the blockchain.</p>
-<hr />
 
                     </main>
 

book/documentation/TECH.html

@@ -210,8 +210,7 @@ <h2 id="execution-and-validation"><a class="header" href="#execution-and-validat
 invariants hold across different message calls.</p>
 <h2 id="contract-instrumentation"><a class="header" href="#contract-instrumentation">Contract instrumentation</a></h2>
 <p>Phink instruments contracts using the <code>syn</code> crate, allowing for precise modification and analysis of the smart contract
-code. This instrumentation is pivotal for identifying potential vulnerabilities and safeguarding the integrity of the
-fuzz testing process.</p>
+code. For each high-level Rust instructions, a feedback is returned via the <code>debug_message</code> map to the fuzzing engine, mapping each instruction to a unique <code>u64</code> identifier. This map is then “expanded”, instrumented by AFL++ compiler, and ultimately updated the AFL++ shared map everytime a new edge is hit.</p>
 
                     </main>
 

book/documentation/print.html

@@ -853,7 +853,6 @@ <h3 id="coverage-1"><a class="header" href="#coverage-1">Coverage</a></h3>
 <h3 id="contract-selectors"><a class="header" href="#contract-selectors">Contract selectors</a></h3>
 <p><strong>ink! contract selectors</strong> are unique identifiers for functions within ink! smart contracts. Selectors are derived from
 function signatures and are used to call specific functions within a contract deployed on the blockchain.</p>
-<hr />
 <div style="break-before: page; page-break-before: always;"></div><h1 id="how-phink-works"><a class="header" href="#how-phink-works">How Phink works</a></h1>
 <p>Phink is built on top of AFL++, leveraging its capabilities to provide effective fuzz testing for ink! smart contracts.
 Here’s an overview of how the fuzzer operates.</p>
@@ -885,8 +884,7 @@ <h2 id="execution-and-validation"><a class="header" href="#execution-and-validat
 invariants hold across different message calls.</p>
 <h2 id="contract-instrumentation"><a class="header" href="#contract-instrumentation">Contract instrumentation</a></h2>
 <p>Phink instruments contracts using the <code>syn</code> crate, allowing for precise modification and analysis of the smart contract
-code. This instrumentation is pivotal for identifying potential vulnerabilities and safeguarding the integrity of the
-fuzz testing process.</p>
+code. For each high-level Rust instructions, a feedback is returned via the <code>debug_message</code> map to the fuzzing engine, mapping each instruction to a unique <code>u64</code> identifier. This map is then “expanded”, instrumented by AFL++ compiler, and ultimately updated the AFL++ shared map everytime a new edge is hit.</p>
 <div style="break-before: page; page-break-before: always;"></div><h1 id="troubleshooting"><a class="header" href="#troubleshooting">Troubleshooting</a></h1>
 <h2 id="debugging-phink"><a class="header" href="#debugging-phink">Debugging Phink</a></h2>
 <h3 id="afl-logs"><a class="header" href="#afl-logs">AFL++ logs</a></h3>

book/src/CONCEPT.md

@@ -68,6 +68,4 @@ good assessment of the contract's logic.
 ### Contract selectors
 
 **ink! contract selectors** are unique identifiers for functions within ink! smart contracts. Selectors are derived from
-function signatures and are used to call specific functions within a contract deployed on the blockchain.
-
----
+function signatures and are used to call specific functions within a contract deployed on the blockchain.

book/src/TECH.md

@@ -44,5 +44,4 @@ invariants hold across different message calls.
 ## Contract instrumentation
 
 Phink instruments contracts using the `syn` crate, allowing for precise modification and analysis of the smart contract
-code. This instrumentation is pivotal for identifying potential vulnerabilities and safeguarding the integrity of the
-fuzz testing process.
+code. For each high-level Rust instructions, a feedback is returned via the `debug_message` map to the fuzzing engine, mapping each instruction to a unique `u64` identifier. This map is then "expanded", instrumented by AFL++ compiler, and ultimately updated the AFL++ shared map everytime a new edge is hit.