Cristóbal Medina López

Could be an issue generated in the fragmentation process?

Great! Thanks. Let us take a look before merging.

We finally commented the catching part (see simulator.py from line 347 to 363), because we force to sleep for 2 seconds before starting to draw.

What if you try to run it separately, for example: Simulate it first: ``` python3 simulator.py run --number-of-monitors 1 --number-of-peers 4 --number-of-rounds 100 --set-of-rules dbs --drawing-log test.draw ``` And then...

It sounds really interesting. We could try it. Do you know whether it offers the possibility to draw networks?

>A quick solution would be to put NODE OUT line in drawing file whenever a peer receives good bye message from the splitter. You mean it removes itself, isn't it?...

>No, i was talking in reference to other peers who will receive GOODBYE message from removed peers. It could work with honest peers.

I think it's not an important issue that removed peers appear like a ghost if finally they are completely removed from the graph. What do you think @vicente-gonzalez-ruiz? Any other...

No, I think it would be enough checking the forwarding list of itself (where it is the origin).