— Generate identities for N clients.

— Define a message of your choice. The message can be modeled in JSON or any format of your choice. The message schema is known to both the clients and the node.

— Each client generates a message, signs it, and sends the signed message to the node. Each client is configured to generate and send a message every second, for 1 minute.

— The node validates the message received as follows:
1: The message schema is valid.
2: The message is signed.
3: The signature is valid and the message indeed came from the client who sent it.

— If the validation succeeds, the node persists the message in the order the message was received.

— When the number of messages received reaches 100, the node processes the messages as follows.
1: Plucks the 100 messages from its queue.
2: Creates a hash of those messages.
3: Signs the hash.
4: Persists the signed hash, hash, and the 100 messages in a separate list. The order of the entry (block) in the list is the order in which the group of 100 messages arrived at the node. To keep the test simple, there is no blockchain created, but a simple list of blocks.

— The node exposes the following APIs, which can be called by the clients. Depending on the implementation, this can be just methods to call on the node, HTTP endpoints, etc. So, define the API format as required.
1: Get the number of completed blocks.
2: Get the block identified by index in the list.

Please identify the test cases, describe them, and demonstrate that the implementation passes the test cases.

A subset of the above functionality can be implemented, if the effort goes beyond a typical weekend’s worth of work. Please spell out what is excluded when submitting the work.