A key part of this: what makes it harder than if the tokens were flowing the other way? What can you do about that?
Conversation
If you are using HTLCs this would be a simpler process, if you can get something like this on the Solana side, it could be argued overall development complexity would be lowered in either direction.
1
1
Replying to
We're using something kinda similar; I think it's faster and cleaner, but fundamentally resting on the same mechanism.
1
2
Interesting when you say cleaner, is the process more streamlined, better generation/verification, or something different?
1
1
Replying to
Faster -- you don't need much of a timelock, and you can do it all in 1 step in ~99% of all cases, so it only takes a few block times beyond a same-chain swap.
Also cheaper, because you generally don't need to go through that process (by being optimistic)
1
2
That sounds awesome, are confirmation times heavily impacted by any of the cross-chain interactions? Like in the case of your example with ETH, is the minimum confirmation set needed to avoid being uncle'd or impacted by natural forks a matter of concern?
1
1
Replying to
It depends on what you're trying to do but you almost always have to wait at least as long as it takes the slower chain to be safely confirmed. The big difference between approaches is whether you have to wait for 1 round or 3.
Most of the extra compute can be on the fast chain.
1
2
Ah, that makes sense! I'm excited to see something like that in action, might be something cool to integrate into one of my projects (or clients haha) :)
1
2