For the DEX aspect of things you're correct. Theres about 5 transactions that need to happen per swap.
DLUX -> Hive:
CustomJson to list a swap 0a(lay tx)
Escrow Transaction to purchase a swap 0b(lay tx)
Escrow Approval 1&2(.agent and .to)
Escrow dispute 3(.to ->ensures no further action is required from either lay party)
Escrow release 4(.agent funds ->.to account)
Transfer 5(.to -> 0a's account)
The reverse looks about the same except the escrow transaction happens first, followed by approvals. Then the Custom Json happens to inform how to complete the chain.
I have it set up to even distribute an inflation pool of DLUX for completed txs as these require RCs. In effect you are mining for DLUX with RCs.
DLUX is meant to help decentralize content storage and serving for dlux.io (VR/AR/WebApps via IPFS) so theres a bunch of other things happening in my chain.
That's great. A huge potential.
OK, I won't bother you with silly questions any longer. At least not this week :)
Have a great weekend and good luck!