[GIP-283] Authorize Securitize RWA contract domains

Summary

This proposal asks the DAO to approve a small setup step for the upcoming Securitize RWA product path.

The setup makes the required Securitize-related contract categories available in Gearbox’s Permissionless deployment system. This allows the launch contracts to be deployed and configured through the normal governance-controlled process.

Voting For does not launch a market, choose a curator, change risk parameters, move funds, or activate a user-facing product by itself. It only approves the setup batch listed below.

Context

Gearbox has been preparing the Securitize integration as a new product path for RWA-backed debt positions.

Securitize assets have controlled transfer and redemption flows. Because of that, Gearbox needs dedicated contract support for three parts of the product path:

1. Opening and managing Gearbox Credit Accounts that interact with Securitize assets.
2. Supporting the wrapped underlying asset used for market accounting and transfer controls.
3. Handling liquidation and redemption cases, including transition-stage assets and non-atomic settlement.

The Permissionless system and Bytecode Repository were introduced in GIP-235. In plain terms, before a new Gearbox contract type can be used through this system, its domain needs to be made public by governance approval.

This proposal makes the Securitize-related domains public so the launch setup can proceed through the existing multisig and governance process.

Proposed batch

The batch adds four public contract domains:

• RWA_FACTORY — supports the factory used for Securitize-compatible Gearbox Credit Account flows.
• RWA_UNDERLYING — supports the wrapped underlying asset used for market accounting and transfer-control logic.
• RWA_LIQUIDATOR — supports liquidation and redemption handling for Securitize-related positions, including transition-stage assets.
• ON_DEMAND_LP — reserves a future on-demand LP domain. This proposal does not launch on-demand LPs.

Batch hash:

0xc897795155ee0091dbe9986ef5f167c057e194de7bd3e27964448d5afeabc748

Execution request

To avoid launch delays, Technical Multisig signers may sign the Technical Multisig submission while this Snapshot vote is still open.

Cross-Chain Multisig signers must wait until the Snapshot vote is closed. They should sign the execution message only if the proposal reaches quorum and passes.

If the Snapshot vote fails or does not reach quorum, Cross-Chain Multisig signers should not sign the execution message. In that case, the Technical Multisig submission should not lead to execution and the batch will have no effect.

Transaction log

Txs log can be found here
Md5 checksums are 7c79b0ef5230835a6682effb38943be3, 83f70e0c44d1784348a5530011334384.