Trustless Bridge Review

As I’m sure all of you are aware, @sumamu and his team recently posted the bridge code for the community to review.

@sol_sanctum and I are working with him to setup the testnet so we can try out the code. I’m sure everyone is busy working on SYRIUS, HTLC, PTLC, and Atomic Swaps.

Once everyone burns through their current work, I’m curious how we plan to review this code.

  1. Should he submit a PR while the community audits it?
  2. Should we audit it and then submit a PR?
  3. Should we have a discussion about the architecture before doing anything?
  4. Do we think this needs a ZIP?

I hope we can give @sumamu some feedback on general expectations. If we need a ZIP I’m happy to help with that process. Here is the repo.

My hope is we can avoid a situation where sumamu submits the PR, it gets approved, and the Pillars are not ready to adopt it. Which is why I’m posting now to try and avoid that.


I think we should follow this order of operations:

  1. Community-wide architectural review + confirming the code works
  2. Code review
  3. Code audit
  4. ZIP
  5. PR

I really want to avoid a “trust me bro, it works” situation.
Any mistake in this project can be devastating for Zenon.
We need to be especially careful with the bridge.


I already started to contribute and setup the Github Actions cicd pipeline

orchestrator releases here: Release v0.0.1-testnet · alienc0der/orchestrator · GitHub

1 Like

@sumamu wanted to share some community feedback on the bridge