Sky proposes custom USDS gateway registration in Arbitrum's router

What happened

Arbitrum DAO opened a constitutional Snapshot proposal to register custom USDS and sUSDS gateways in the canonical router used by the official bridge UI.

What changed

A concrete governance path opened for routing two Sky assets through token-specific custom gateways instead of default gateway handling in the official UI.

What did not change

The March proposal did not change router state or authorize execution. The custom bridge contracts were already live, while official UI routing remained disabled pending governance.

Confirmed

• The proposal identified the Ethereum and Arbitrum custom gateway contracts and USDS and sUSDS token addresses.
• The proposal stated that the router configuration still used default gateways and that official bridge UI access was disabled for these tokens.
• The March Snapshot record opened a governance vote before later execution stages.

Still open

• Governance approval, payload verification, and execution were not completed during March.
• Independent verification of the final governance payload and router state remained outstanding.
• Registration would not itself establish the suitability or solvency of USDS or sUSDS.

What it means for an advisor

• Track the proposal because it would add a token-specific custody and upgrade path to the official Arbitrum bridge interface.
• Keep Sky-asset diligence separate from the Arbitrum bridge memo; router registration does not approve either asset.
• Require executed router state and verified gateway controls before treating the UI path as operative.