After consideration, the @SEEDgov delegation decided to vote FOR on this proposal at the Tally Vote .
This is a no-brainer, the contracts have passed security requirements, and we still emphasize that we should remove barriers to provide a more streamlined process to the builders for them to migrate tokens to Arbitrum and use our native bridge.@Jose_StableLab :
Thank you @AbdullahUmar for raising awareness about the complexities around launching a custom gateway on Arbitrum.
As StableLab, we’ve been closely working with the Sky team throughout their custom gateway proposal process, and we’d like to share our perspective on the experience so far:
The Sky proposal is still in progress. While much of the technical and procedural work has been completed, there are still critical steps required before the proposal is ready for onchain submission.
All of the Sky-side code has been audited, as correctly noted in the proposal. The team has taken their due diligence seriously to ensure security and correctness.
Regarding Offchain Labs’ involvement, when approached, they provided the governance action contract and the required governance documentation necessary for executing it to achieve the Router update. However, they asked Sky to conduct their own review of the governance action contract and prepare and check the governance transaction payload themselves.
Because the governance execution itself must also be verified, the Sky team has independently engaged a separate security firm to audit and validate the governance actions. Importantly, they are covering these costs themselves.
We’ve also reached out to the $BORING team to support their efforts as well. However, due to the differing stages of their respective processes and some technical differences between both proposals, it’s likely that the two gateway proposals will proceed onchain separately. This is necessary to prevent delays in Sky’s timeline for launching USDS on Arbitrum.
Overall, we believe the current process for deploying custom gateways on Arbitrum, while secure, is highly resource-intensive and time-consuming. This creates a significant burden for projects looking to integrate with Arbitrum, particularly those without access to deep technical or auditing resources.
We think it’s worth opening a discussion on whether this process can be streamlined in the future, without compromising on security or decentralization, to reduce the overhead for teams launching in the Arbitrum ecosystem.
1 Like