Adding additional step to what is next in progress report 3

progress_reports/progress_report_3.md

@@ -155,6 +155,8 @@ Continuing Phase III: Integrate the results of Phase I and Phase II into the BLA
     - This node can then be added to BLAST as another model that is available to the users
     - So far I have been exploring ways to create lightweight implementation-specific nodes that are still very accurate representations of the full implementation. I created an LND node that is just a little more efficient, but is still essentially a full LND node. A more effective strategy might be to create generic simulation nodes that simply help make up a test network and then use full implementations for the nodes of interest that the user is trying test. These "generic simulation nodes" would not be very realistic, but that does not really matter because you are not interested in how these nodes operate, they are just there to help facilitate the simulation. For example, if you are trying to test out some simulated attack on LND nodes, you could have a few full LND nodes running but you need several different routes to and from these nodes. You could start up these "generic simulation nodes" and open channels to them to create a network around the LND nodes. These nodes do not have to be explicitly defined in SimLN because they won't initiate any payments, they will just forward payments between the real LND nodes. This could increase the size of the test network that is possible.
     - This type of node can be developed and then added to BLAST as another "model" through the model interface that is already built.
+3. Create CLN model for BLAST
+    - Create a model that adheres to the BLAST RPC interface that controls a given number of full CLN nodes.
 
 ## What was the OpenSats funding used for?
 The grant money was used as part of my income in order to pay for living expenses.