This vote, if passed, will approve <ins>CP151: New simplified onboarding to build on Centrifuge</ins>.

The primary objective of this proposal is to simplify and streamline the Pool Onboarding Process (POP) for the Centrifuge Protocol. By making the process more permissionless and simplifying and aligning the protocol’s fee structure, we aim to lower the barriers to entry for issuers, making Centrifuge the de facto technology provider for self-service fund tokenization.

**Implications:**
- Simplify and automate the process of launching a pool on Centrifuge and lower the barriers to entry, making Centrifuge more accessible for potential issuers.
- Deprecate CP74
- Modify CP5, CP28
- Set a flat protocol fee of 50 bps for all types of pools

Link to the proposal on GitHub: https://github.com/centrifuge/cps/blob/main/cps/CP151.md
Link to the RFC on the forum: https://gov.centrifuge.io/t/cp151-new-simplified-onboarding-to-build-on-centrifuge/6832

Do you agree with this proposal?
Please vote **Yes**, **No** or **Abstain**.

CP151: New simplified onboarding to build on Centrifuge


This proposal, if passed, will approve the CP149: Migration of Centrifuge Governance Token (CFG) to EVM

This proposal seeks governance approval for migrating the Centrifuge governance token (CFG) to an EVM-compatible token standard. It builds upon CP 141, which introduced Centrifuge V3, a multi-chain, EVM-based protocol.
To align governance with Centrifuge V3, this proposal mandates k/factory to launch a new EVM CFG token and initiate the structured migration of existing CFG and WCFG tokens.
The current Centrifuge Chain CFG token will be deprecated along with WCFG and replaced by a new EVM-based CFG token, minimizing disruption for token holders through a transparent migration plan.

- Link to the proposal on GitHub: https://github.com/centrifuge/cps/blob/main/cps/CP149/CP149.md
- Link to the RFC on the forum: https://gov.centrifuge.io/t/cp149-migration-of-centrifuge-governance-token-cfg-to-evm/6810
Do you agree with this proposal?

Please vote **Yes**, **No** or **Abstain**.

CP149: Migration of Centrifuge Governance Token (CFG) to EVM


This proposal, if passed, will approve the CP141: Initiate the development of Centrifuge V3, a multi-chain, EVM based protocol

The proposal seeks governance approval to initiate the development of Centrifuge V3, an EVM-based protocol, to drive the next phase of growth for the RWA market. Built as a multi-chain system, this next-generation protocol will introduce features such as chain abstraction, modularity for diverse assets and investors, and enhanced composability with DeFi. The protocol will also migrate governance and CFG token support to an EVM chain, aligning with the ecosystem where the majority of Centrifuge’s activity already resides. This initiative positions Centrifuge to lead the rapidly growing RWA space and meet the evolving needs of institutions and DeFi participants.


- Link to the proposal on GitHub: https://github.com/centrifuge/cps/blob/main/cps/CP141/CP141.md
- Link to the RFC on the forum: https://gov.centrifuge.io/t/cp141-initiate-the-development-of-centrifuge-v3-a-multi-chain-evm-based-protocol/6734

Do you agree with this proposal?

Please vote **Yes**, **No** or **Abstain**.

CP141: Initiate the development of Centrifuge V3, a multi-chain, EVM based protocol

This snapshot vote, if passed, will approve CP128 and make amendments to our funding process for treasury proposals (CP2).

Implications:
* Introduce a milestone based funding process
* Make changes to the template used for funding requests

Link to the proposal on GitHub: https://github.com/centrifuge/cps/blob/main/cps/CP128/CP128.md
Link to the RFC on the forum: https://gov.centrifuge.io/t/cp128-amendments-to-cp2-component/6549/1

Do you agree with this proposal?

Please cast your vote by voting **Yes**, **No** or **Abstain**.

CP128: Amendments to CP2 component

This snapshot vote, if passed, will approve CP130 in order to reach an agreement in the Centrifuge DAO that the goal of resource allocation from the Centrifuge Treasury should always support the mission of Centrifuge and to this end, resources should be allocated to the proposals that can make the case for the highest return and highest impact for Centrifuge according to clear goals and themes.

Implications:
* All proposals should connect to the wider Centrifuge goals, and specify which goals your proposal meets and how
* Proposals must specialize in one or more of the Themes and list which Theme(s) are applicable

Link to the proposal on GitHub: https://github.com/centrifuge/cps/blob/main/cps/CP130.md
Link to the RFC on the forum: https://gov.centrifuge.io/t/cp130-goals-and-themes-for-resource-allocation-for-the-centrifuge-treasury/6564

Do you agree with this proposal?

Please cast your vote by voting **Yes**, **No** or **Abstain**.

CP130: Goals and Themes for Resource Allocation for Centrifuge DAO Treasury

This proposal, if passed, will approve the CP103: Launch an RWA Lending Market

Proposal to create an RWA-focused lending market to give users the ability to lend and borrow against eligible pool tokens.

- Link to the proposal on GitHub: https://github.com/centrifuge/cps/blob/main/cps/CP103/CP103.md
- Link to the RFC on the forum: https://gov.centrifuge.io/t/cp103-launch-an-rwa-lending-market/6346

Do you agree with this proposal?
Please vote **Yes**, **No** or **Abstain**.


CP103: Launch an RWA Lending Market


This proposal, if passed, will approve the CP105: Data Protocol (Technical Proposal) 
Proposal to introduce the Data Protocol, a further development of the Private Offchain Data (POD) within the Centrifuge network, enabling secure data storage, collaboration, and sharing functionalities.

- Link to the proposal on GitHub: https://github.com/centrifuge/cps/blob/main/cps/CP105/CP105.md
- Link to the RFC on the forum: https://gov.centrifuge.io/t/cp105-data-protocol-technical-proposal/6344

Do you agree with this proposal?
Please vote **Yes**, **No** or **Abstain**.

CP105: Data Protocol (Technical Proposal) 

This proposal, if passed, will approve the agreements for how to manage the funds in the Centrifuge Treasury. This is an update to the existing agreement that passed with CP58.

- Link to the proposal on GitHub: https://github.com/centrifuge/cps/blob/main/cps/CP107.md
- Link to the RFC on the forum: https://gov.centrifuge.io/t/rfc-updated-treasury-spending-agreement/6290/1

Do you agree with this proposal?

Please vote **Yes**, **No** or **Abstain**.

CP107: Updated Treasury Spending Agreement

This proposal, if passed, will approve our migration to OpenGov with the suggested tracks and parameters. Some changes will also be made to our governance process as a result of an accepted migration. 

- Link to the proposal on GitHub: https://github.com/centrifuge/cps/blob/main/cps/CP108/CP108.md
- Link to the RFC on the forum: https://gov.centrifuge.io/t/rfc-centrifuge-migration-to-opengov/5984

Do you agree with this proposal?

Please vote **Yes**, **No** or **Abstain**.

CP108: Centrifuge Migration to OpenGov

This proposal, if passed, will approve the CP104: Financial Reporting.
Proposal to build standardised real-time financial reporting for Centrifuge pools based on the data made available in the subquery.

- Link to the proposal on GitHub: https://github.com/centrifuge/cps/blob/main/cps/CP104.md
- Link to the RFC on the forum: https://gov.centrifuge.io/t/cp104-financial-reporting/6351

Do you agree with this proposal?
Please vote **Yes**, **No** or **Abstain**.

CP104: Financial Reporting

This OpenSquare snapshot is to get a **temperature check** of what the sentiment is around the Treasury Proposal from Tangem Wallet to integrate Centrifuge and Altair into their wallet.

The initial proposal mentions 500 branded wallets (2-card set) + integration of CFG/AIR + delivery for a total cost of $16,470. Based on the input in the forum post and [Governance Call 26](https://www.youtube.com/watch?v=GvRNtiwHSFY) from the DAO, more options are provided (including the total cost).

Read the full proposal and discussion [here](https://gov.centrifuge.io/t/rfc-integration-of-the-network-into-tangem-and-production-of-500-branded-centrifuge-wallets-2-card-sets/6332).

Option 2 includes customised boxes instead of branded wallets.

Note, that **this vote does not determine the outcome** of this proposal - an onchain proposal is still required in order for it to pass.

Please vote on **one** of the three options below.

Proposal to integrate CFG + AIR into Tangem

This proposal, if passed, will approve the Roadmap Proposal 1  proposed by PEG.

- Link to the proposal on GitHub: https://github.com/centrifuge/cps/blob/main/cps/CP87.md
- Link to the RFC on the forum: https://gov.centrifuge.io/t/cp87-roadmap-proposal-1/6077

Do you agree with this proposal?
Please vote **Yes**,  **No** or **Abstain**.

CP87: Roadmap Proposal 1

This proposal, if passed, will give a mandate to the OpenGov Technical Committee.

The initial members will be seeded in the same runtime upgrade that implements OpenGov on both Centrifuge and Altair, respectively.

Link to the proposal on GitHub: https://github.com/centrifuge/cps/blob/main/cps/CP86.md

Link to the RFC on the forum: https://gov.centrifuge.io/t/rfc-opengov-technical-committee-mandate-request/6085

Do you agree with this proposal?
Please vote **Yes**, **No** or **Abstain**.

CP86: OpenGov Technical Committee Mandate Request

This proposal, if passed, will introduce and add different pool fees for different types of pools.

- Link to the proposal on Github: https://github.com/centrifuge/cps/blob/main/cps/CP83.md
- Link to RFC on Gov forum: https://gov.centrifuge.io/t/cp83-updating-cp28-centrifuge-protocol-fees/6022

Do you agree with this proposal?
Please vote **Yes**, **No **or **Abstain**.

CP83: Updating CP28 Centrifuge Protocol Fees

If passed, this proposal will discontinue Centrifuge Crowdloan rewards claiming 60 days after the date this proposal passes (if passed).

- Link to the proposal on Github: https://github.com/centrifuge/cps/blob/main/cps/CP84.md
- Link to RFC on Gov forum: https://gov.centrifuge.io/t/cp84-unclaimed-polkadot-rewards/6035

Do you agree with this proposal?

CP84: Unclaimed Polkadot Rewards

If passed, this proposal will discontinue rewards claiming on Tinlake 30 days after the date this proposal passes (if passed) and transfer any remaining tokens from the Tinlake wallet to the Centrifuge DAO Treasury wallet.

Link to the proposal on Github: https://github.com/centrifuge/cps/blob/main/cps/CP81.md
Link to RFC on Gov forum: https://gov.centrifuge.io/t/rfc-unclaimed-tinlake-rewards/5885

- Do you agree with this proposal?

Please vote **Yes**, **No **or **Abstain**.

CP81: Unclaimed Tinlake Rewards

This proposal, if passed, would introduces an additional component to the transaction fee that will be transferred to the treasury for each transaction in addition to the standard weight-based fee system that is part of any Substrate based chain.

Link to proposal on github: https://github.com/centrifuge/cps/blob/main/cps/CP74.md
Link to RFC on Gov forum: https://gov.centrifuge.io/t/rfc-updating-transaction-fees-for-pools/5773/

- Do you agree with this proposal?

Please vote **Yes**, **No** or **Abstain**.

CP74: Updating Transaction Fees for Pools

This proposal, if passed, would amend the current POP V2 process to the new POP v3 process which would simplify the Pool Onboarding Process (POP) by making it more similar to other Centrifuge Governance processes, which use the formula of Request for Comment (RFC) followed by discussion (during this discussion period the Centrifuge Credit Group can choose to put forward an assessment) and then a vote. It would also make it a faster, simpler, and clearer process.

- Link to proposal on github: https://github.com/centrifuge/cps/blob/main/cps/CP68/CP68.md
- Link to RFC on Gov forum: https://gov.centrifuge.io/t/rfc-update-the-pool-onboarding-proposal-for-open-pools-pop-version-3/5698

Do you agree with this proposal?
Please vote Yes, No or Abstain.

CP68: Update the Pool Onboarding Proposal for Open Pools (POP) – Version 3

This proposal, if passed, will introduce three different types of pools on Centrifuge and define them:

- Open Pools
- Closed Pools
- Portfolio Pools

**Do you agree with this proposal?**

Please vote **Yes**, **No** or **Abstain**.

See the full proposal on GitHub: https://github.com/centrifuge/cps/blob/main/cps/CP63.md
See the discussion in the RFC: https://gov.centrifuge.io/t/rfc-definitions-of-pool-types-categories/5688

CP63: Definitions of Pool Types & Categories

This proposal will
- extend the versatility of the Centrifuge protocol

Linked Pools are an extension of functionality for on-chain pools beyond the existing asset-financing logic. This feature will allow so-called “linked” pools to be funded directly by another pool where the system was previously limited to fund only assets.

**Do you agree with this proposal?**

Please vote **Yes** or **No**.

See the full proposal: https://github.com/centrifuge/cps/blob/main/cps/CP59.md
See the discussion in the RFC: https://gov.centrifuge.io/t/rfc-linked-pools-technical-proposal/5569