Migrate Stargate Protocol Contracts to OneSig

Summary This proposal recommends migrating all protocol-related Stargate smart contracts to OneSig, an open-source multi-chain execution framework developed by LayerZero. OneSig significantly reduces operational overhead and enhances security by enabling secure, single-signature execution of transactions across any number of chains. Treasury funds will remain in the Gnosis Safe for the time being.

Background Managing and executing multi-chain transactions is one of the most resource-intensive and error-prone aspects of operating a protocol like Stargate. Stargate’s current reliance on multisig coordination across various chains introduces operational friction, delayed deployments, and potential security vulnerabilities—as seen in recent front-end and multisig-related exploits across the ecosystem.

OneSig provides a unified execution environment that allows for:

Proposal of transaction batches across chains

Merkelization and signature of a single Merkle root

Threshold-based validation and execution of each transaction independently

This results in lower overhead, faster execution, and verifiability without relying on centralized services or complex coordination.

OneSig has undergone seven independent audits, and all audit reports are publicly available here: https://github.com/LayerZero-Labs/onesig/tree/main/packages/onesig-evm/audits

There is a deep dive on OneSig available here.

Proposal Stargate DAO will:

Approve the migration of all protocol-related smart contracts to the OneSig, away from Gnosis Safe.

Retain the current Gnosis Safe setup for treasury custody, for the time being.

The signer threshold on OneSig will remain at 3/6, and the signers on OneSig will remain as the same signers that have been used on Stargate’s Gnosis Safes.

Execution Upon DAO approval:

Stargate Foundation will very carefully migrate Stargate V2 & V1 protocol contracts over to newly deployed OneSig contracts with 3/6 threshold.

An internal testing and validation phase will occur over 3–4 weeks to simulate and verify all workflows.

A final readiness review will be conducted before switching contract management and execution to OneSig.

Treasury funds and Safe configurations will remain unchanged.