Additionally because there are a number of them, the size is actually over 1KB. Thus we have a small input value and a (relatively) large byte size for the transaction.
This is the most important part related to this transaction. Over 1 KB size = 0.0002 fee required to be treated as standard transaction. If this was issued via one of the wallets, the wallet creator needs to adjust to take transaction size into consideration asap. Delayed transactions due to insufficient fees can be a game breaker, if MSC are bought via DEX and the time window closes before the transaction confirms.
+1
and thanks Zathras for the explanation
what should be the process for this? someone going to file an issue? i guess technically its not a master protocol thing, but it would need to be at least discussed in a special considerations area of the spec?