Make each process be able to have at least two threads. One for connecting to the Illuminati and one for connecting to other processes.

Make the server be able to handle in async - use Tokio for that.

In order to keep track of active users, I want to keep track of who sent its information to the server.

Currently I only know how to send over the TCPStream Strings and Integers but now I want to modify it to the extent that I can send serialised User objects

Create new offers for memory storage

This way it will be more organised, less spaghetti code, and easier to write additional things aka multiple requests sent over to the server side.

Should I make each process follow like a class-like structure?

Instead of sending back the echo of whatever was sent, maybe send back an HTTP code.

https://developer.mozilla.org/en-US/docs/Web/HTTP/Status

When I tried to modify my handles() method to be able to modify the global variable I had to pass in the new argument - the borrow of the global variable. However, this triggered some weird "variable can be outlived by the borrow" error and this is how it was explained.

Not sure if the 'move' is a good fix as I am doing it for the first time.

Make a thread that takes an offer and removes it at a certain time.

Do users need to ask the iluminati server what their funds status is or can they check internally?

Learn how to use a Merkle Tree for communicating between two processes.

Create a system where clients send requests to the server.

1. POST their information
2. GET the information -> here a search system will need to be implemented
3. Error handling where if not sufficient funds etc. ... => this is for the future

So, before I send over an object via the TCPStream, I must make sure that the object is serialised!

Implement the search method on all the offers when a GET request is sent in. First, just return with simple filter based on the given user and then sort the offers.