More interesting is that in EU with 10 devices you can more or less legally block RX2 for all the devices around; bye-bye class C 
The demodulators aren’t as fixed in purpose as you seem to think. There are actually at least two stages with a rather fancy dynamic handoff assignment between. You can only receive 8 signals on the flexible paths, but with the right spreading factor combinations those 8 don’t have to all be on unique frequencies.
More interesting is that in EU with 10 devices you can more or less legally block RX2 for all the devices around; bye-bye class C
There are costs to LoRaWAN’s decision to forgo short-term, repairable state such as could permit synchronizing a hopping schedule for class C after a node does uplink. Ironically, where LoRaWAN does use shared state (to prevent join nonce or fcnt re-use) it tends to be all but impossible to restore once lost. It’s repairable short term state that is key to how many other sorts of modern multi-frequency networks work.
You’re pretty right. So what? Eight preamble sender will hit all the available demodulators, will not them?
8 boxes sending just preambles are obviously maliciously interfering. While this thread is about “guidelines” LoRaWAN is mostly used in places where there are “laws” prohibiting such behavior.
Please take a look at the very first post.
Isn’t this prohibited by law in most places? 
where no plaintiff there is no judge.
And even you have to find the node.
If some hackers will disturb the network they do it.
Those same hackers can get a cheap box to interfere with mobile phone signals and interrupt coverage at a location. That is the nature of wireless transmissions.
3 Likes