Summary

This proposal completes the transition of the ownerSafeDao Safe on Polygon to full DAO control by removing the remaining legacy individual signers and leaving the DAO Safe (newSigner) as the sole owner. It also authorises Panther DAO to enter into two agreements with the Panther Protocol Foundation, formally aligning the project's public website and dApp interface with DAO governance.

Together, these actions finalise Panther Protocol's governance structure ahead of the next phase of the protocol.

---

Motivation

Panther governance has progressively transitioned from early operational signers toward full DAO ownership. While most infrastructure is already DAO-controlled, ownerSafeDao still includes legacy signers from earlier phases of the protocol.

Removing these signers:

• Aligns control with DAO governance
• Reduces operational risk
• Simplifies key management
• Strengthens decentralisation
• Finalises governance structure before launch

At the same time, Panther's main public entry point and dApp interface should be formally aligned with DAO governance. The two proposed agreements achieve this while keeping the Foundation in a strictly non-operational role consistent with its grant framework.

---

What This Proposal Does

1. Safe Ownership Transition

Removes the following legacy signers from ownerSafeDao:

	Address
Signer 1	0xFee6D2Cb5816282D853fba79cB9C8b5EDB7908Cd
Signer 2	0xb83A3094272B6425f89BB5590b48928e2374eE11

After execution, the Safe ownership becomes:

Owner
newSigner Safe

2. Domain & Website Assignment and Trademark Licence Agreement

Transfers the Foundation's rights and interests in pantherprotocol.io and existing site content to the DAO, and grants a limited revocable licence to use Panther marks on the site. The DAO assumes full responsibility for the domain, DNS, routing, and content. The full agreement is attached for review.

3. Software Licence and Non-Operation Agreement (dApp Licence)

Grants the DAO a worldwide, perpetual, irrevocable, royalty-free licence to use, modify, deploy, and operate the Panther dApp as a non-custodial, open-source interface. The Foundation is explicitly non-operational under this agreement. The full agreement is attached for review.

---

Contract Addresses

Ethereum

Contract	Address
DAO Multisig	0x505796f5bc290269d2522cf19135ad7aa60dfd77
FxRoot	0xfe5e5D361b2ad62c541bAb87C45a0B9B018389a2

Polygon

Contract	Address
ownerSafeDao	0x026a024b13B4Ca23897ad578264C0ec543f904b9
newSigner (DAO Safe)	0x208Fb9169BBec5915722e0AfF8B0eeEdaBf8a6f0
MaticBridgeModule	0x4A4FC40d2475f493EcA3Ec436b924237AA1b0a76

---

Execution

Safe Ownership Transition

The proposal executes four cross-chain governance transactions via FxRoot from Ethereum to Polygon:

1. Approve hash for removing Signer 1
2. Execute removeOwner for Signer 1
3. Approve hash for removing Signer 2
4. Execute removeOwner for Signer 2

These calls are bundled into a governance execution batch.

Agreement Signing

If this proposal is approved, the DAO Multisig (0x505796f5Bc290269D2522cf19135aD7Aa60dfd77 on Ethereum) produces an off-chain cryptographic Safe message referencing the SHA-256 hash of each Foundation-signed PDF. That signature constitutes binding execution of each agreement on behalf of the DAO.

---

Licensing Resolutions

Resolution 1 — Domain & Website Assignment

Approve Panther DAO entering into the Domain and Website Assignment and Trademark Licence Agreement with effective date 1 February 2026, in the form signed by Panther Protocol Foundation and identified by SHA-256 hash 241b12494c6a1fcc45405841bac8dc88ca6bdd27a5b873c2c023d6c0e40f9e20, and authorise the Panther DAO Multisig at 0x505796f5Bc290269D2522cf19135aD7Aa60dfd77 on Ethereum to approve, execute, and implement that Agreement on behalf of the DAO, including by producing an off-chain cryptographic signature or Safe message referencing the above hash. Any action taken by that multisig in accordance with this authorisation shall constitute valid and binding execution of the Agreement by Panther DAO.

Resolution 2 — dApp Software Licence

Approve Panther DAO entering into the Software Licence and Non-Operation Agreement with effective date 1 February 2026, in the form signed by Panther Protocol Foundation and identified by SHA-256 hash d2e58581313f85be51b8433122a4c5e671963655385903c436d9f9d6cb23409f, and authorise the Panther DAO Multisig at 0x505796f5Bc290269D2522cf19135aD7Aa60dfd77 on Ethereum to approve, execute, and implement that Agreement on behalf of the DAO, including by producing an off-chain cryptographic signature or Safe message referencing the above hash. Any action taken by that multisig in accordance with this authorisation shall constitute valid and binding execution of the Agreement by Panther DAO.

---

Impact

After execution:

• DAO Safe becomes sole owner of ownerSafeDao
• Legacy signers are removed and governance structure is simplified
• pantherprotocol.io and its site content are formally under DAO control
• DAO holds a perpetual licence to operate the Panther dApp as a non-custodial interface
• Foundation remains strictly non-operational

No contract logic changes and no protocol funds are moved.

---

Why This Matters

Panther has spent years building privacy infrastructure and decentralised governance. This proposal completes the final ownership transition while formally aligning the protocol's public infrastructure and software rights with DAO governance. Once executed, Panther's core administrative and operational layer will be fully DAO-controlled ahead of the protocol's next phase.

---

Voting

For

• Execute the Safe ownership transition, approve both licensing resolutions, and finalise DAO control.

Against

• Do not execute the ownership change and do not approve the agreements.

Transactions Overview

Remove old signers (signer1, signer2) from ownerSafeDao and leave only newSigner Safe as owner via cross-chain governance

1. FxRoot@eth::sendMessageToChild(MaticBridgeModule, encodedData) // Approve hash for signer1 removal
2. FxRoot@eth::sendMessageToChild(MaticBridgeModule, encodedData) // Execute removeOwner for signer1
3. FxRoot@eth::sendMessageToChild(MaticBridgeModule, encodedData) // Approve hash for signer2 removal
4. FxRoot@eth::sendMessageToChild(MaticBridgeModule, encodedData) // Execute removeOwner for signer2