Open geoknee opened 2 years ago
In my first attempt to fix this, I made a test which uses the native token for ledger channels and then goes again with an ERC20 token. But this caused the error a channel already exists with counterparty
. I think this means we will need to go deeper to get ourselves fully multi-asset compliant (i.e. we need to think about routing in multiple assets).
In the short term, I will probably just aim for supporting one token or the other (exclusive).
We suspect there a bug in this flow somewhere and we are not exercising the code enough to see it currently.