Figure 2
At the top, rectangular text box 1 is labeled “Start: Problem Identification.” A downward arrow leads to a rectangular text box 2 labeled “Review Literature and Identify Gaps.” A downward arrow from rectangular text box 2 leads to rectangular text box 3 labeled “Framework and Functional Requirements Design.” A right-pointing arrow leads to a rectangular text box 4 labeled “Define Stakeholders.” The right-pointing downward arrow leads to a rectangular text box 5 labeled “Design System Architecture.” A downward arrow from rectangular text box 3 leads to rectangular text box 6 labeled “Select Technology (Ethereum, Solidity).” A downward arrow from this rectangular text box 6 leads to a rectangular text box 7 labeled “Smart Contract Development.” A downward arrow from rectangular text box 5 leads to rectangular text box 8 labeled “Develop Algorithms.” A left-pointing arrow from this rectangular text box 8 leads to rectangular text box 7. From these two downward-slanting arrows emerge from the bottom of rectangular text box 7. On the left, the downward-slanting arrow leads to rectangular text box 9 labeled “Security and Cost Analysis,” and the right downward-slanting arrow leads to rectangular text box 10 labeled “Testing and Validation.” A downward arrow from rectangular text box 9 and rectangular text box 10 leads to rectangular text box 11 labeled “End: Optimize slash Generalize slash Deploy Framework.”Methodology flowchart diagram. Source: Authors' own creation/work