I think it would be easier to generate trace splines from a particle emitted from node 76 (or at least node 76’s null).
The traces can be associated with sweeps or lofts so that they in turn generate geometry. You can also use plugins to render just the splines themselves. (white lights is one of my favorites). The traces grow (as would the sweep) as the particles move about.
I’m not sure about the simultaneity. The issue (as I see it) is going to be distance. Each node will be a different distance away from the others so the distance will have to be traversed at different speeds for them all to arrive at receivers all over the place. You could measure the distance between the pair of nodes that are picked in the random sort and then do the math for how much velocity should be imparted so each particle arrives at the given time, the farther away the more initial oomph needed to send the trace on its way. I think you can achieve all of this with expresso.
Or you could use a really big velocity everywhere and then have the sweeps grow over time along all the traces (the traces would span the distances almost instantly).
But there’s a problem here. You want randomness, but only the first volly is random. After that its always the receiver that sends out a new beam to a new random node, but can it be one of the ones that has either already received or already fired?
Instead of using the random function in the link list, you might have to make an array the number of objects available and when picking a new “random” value make sure its not one that’s been used before. So the array would get bigger or smaller each iteration either adding to the list of ones not to use or removing ones that have been used. Then use that array to pick choose the index of the node in the link list to fire next.
Keep in mind there is no “memory” in expresso for whats come before so either have to calculate the whole thing for every frame right back to the beginning of time, or make a change for each node that is tested on each frame. So if node 1 has been used, it gets slightly bigger lets say. When you choose a new value to fire you check to see if its already gotten bigger, and if so pick the next index in the array and test that one (and so one). Coffee would work well for this as would python. Having the array grow or shrink might look after this.