okay - so it is like the following:
@DavidMc0 stores his favorite cat picture to the network
- cat picture gets split into 3 chunks + 1 public chunk because he wants to share it with his grandma
- payment is needed but gladly we have a native token → we store an additional TX on the network as native Token Type that just needs a very small native fee to be paid to the nodes storing this TX (in contrast to the nodes storing the cat picture)
- the very small fee just needs another TX to be stored so we have a TX#2 to pay for storing TX#1 on the network
- then we need TX#3 to pay for TX#2 storage
…
so without changing the initial payment system to include an additional payment output(s) for the additionally needed payment TX for a native token we are trapped in an infinite loop of required payments ![]()
and that’s just the first obvious needed change for nodes … we’ve not even started to investigate consequences …