So a strategy for devices stuck with unconfirmed transactions would be to send another blank transaction referencing the original unapproved transaction. Since this network will be used primarily by non-humans, such a behavior would need to be coded into the IOT device itself right? For example: If transaction does not confirm withing x time, then resend a blank transaction with reference to first one.
How would this work out in a larger simulation where many devices would use such a strategy? Could this cause a spam of blank transactions in the network where many devices are trying to promote their own transactions for faster confirmation times? Or is this a non-issue?
If a device paid to a merchant then the marchant himself can confirm all pending transactions sent to him by organizing these transactions into few subtrees and confirming the roots.
"Dumb" reconfirmation increases amplitude of cosine pulses making some devices to generate 2-3 extra blank transactions which increases security of the system.