Prioritize Building out a Wormhole Integration

Thanks for the considered responses @preto and @Rigorous. I wanted to share a few thoughts, and I have a few questions.

Thoughts

My statement was brief, to expand a bit on my current position (happy to hear disagreements):

  1. Namada should not support assets or connect to things that are obvious scams (this doesn’t apply to any bridge we might reasonably consider here, but it would have applied e.g. to Terra/USDT, at least given the benefit of hindsight).
  2. Otherwise, Namada should be pretty liberal in connecting to chains and assets – not every user wants to use every asset or chain, but the more users using the MASP, the more privacy for everyone. At the protocol level, we should use IBC rate limits and/or similar circuit breakers (as is already done) to bound the risk should something go wrong.
  3. We should aim to help users understand what trust assumptions they’re making and what risks they’re exposed to. Typically, this would happen at the interface (e.g. Namadillo) level, with warnings, safety tips, “advanced mode”, links to external analyses, etc. The choices are ultimately always up to the user, but we should inform them as best we can (in a neutral fashion).

Would you generally be in agreement with that, or do you have a different take?

That’s fair, and I’m looking forward to seeing what you’ve been cooking up. Wormhole was mentioned before, and didn’t seem to generate any controversy then, but perhaps this was not very visible. On the other hand, from the Heliax side, we have development resources available (not everything can be used to speed up phase 4/5), and we’d like to get started on something – and I don’t think it’s in the community’s interest for us to spin our wheels idling either. Speed matters, especially in the current environment, whether we like it or not. However, I think that these goals should be able to be synthesized with thoughtfully designed process – perhaps a kind of signaling vote that is more specifically “exploratory”, for example – but I’ll hold off on brainstorming there until you share what you’ve been working on! Another process that I imagine would be helpful is a way to surface general community sentiment around immediate priorities (prior to signalling votes) that Heliax or other entities could use as a signal to inform how they focus their time.

I’m also excited about Union, and I think that we’ll definitely want to support different bridges in the future – ultimately, it’s up to what users want to use (and they, in turn, will care about which options are the safest, cheapest, and easiest, I expect).

Questions

Do you have a good data source for this? I looked quickly on DefiLlama but it wasn’t super clear.

Is Polaris a bridge? I thought it was a multichain DEX UI. Do you mean this Polaris, or another one?

3 Likes