Summary

This proposal requests community approval to rebrand the TrueFi project and to mint the remaining TRU token supply to fund this transition and future growth.

Over the past year, the Board and Foundation have worked to clean up legacy issues, stabilize operations, and build new products. However, the TrueFi brand continues to carry reputational baggage from earlier eras that no longer reflect the team, the technology, or the direction of the project.

A rebrand allows the protocol to retain its technology (including Cyan, the TrueFi vault architecture, and the stablecoin/CDP system) while cleanly separating from the legacy identity that has become a significant headwind to growth and business development.

Background

TrueFi has gone through substantial internal transformation in the last 12 months. The current contributors have:

Streamlined governance and operations Consolidated technical assets Integrated Cyan Developed a stablecoin and CDP architecture Improved financial discipline Invested in modernizing the infrastructure

These improvements position the project for renewed growth. However, despite this progress, the brand itself remains one of the largest obstacles.

The Problem: The TrueFi Brand No Longer Represents the Project

The reputation TrueFi accumulated from 2020–2023 (governance disputes, misaligned incentives, unresolved forum discussions, contributor turnover, and loan disputes from teams long gone) continues to resurface despite the current team’s clean track record.

This manifests in several ways: BD conversations that begin with legacy concerns unrelated to today’s contributors Questions on socials about events that occurred years ago under prior teams Negative associations that overshadow new products and integrations Confusion about which groups or technologies are still part of the project Community members repeatedly asking why the protocol has not rebranded The brand has become a structural drag on credibility, growth, hiring, partnerships, and even basic communications.

The technology is strong. The team is aligned. The opportunity is real. The brand is a bottleneck. A clean slate solves this.

Rationale for Rebranding

The Community Has Actively Requested a Rebrand Multiple members of the Telegram community have raised the idea of rebranding, recognizing that the legacy issues are not going away and continue to distract from the work actually being built today. This proposal formalizes that discussion and acknowledges the community’s input.

The Brand Carries Reputational Baggage That No Longer Reflects Reality Despite the current team’s work to fix the past, nearly all external conversations still surface history that:

The current contributors did not create The current Board has already resolved or addressed The technology stack no longer reflects

This creates unnecessary friction for BD, partnerships, liquidity collaborators, and ecosystem conversations.

A Unified Brand Enables the Project to Present Its Technology as a Cohesive System We now operate: Cyan (NFT-backed lending) TrueFi vault infrastructure A stablecoin and CDP system Off-chain borrower evaluation and credit primitives

These should sit under one coherent brand, not fragmented legacy naming.

The Rebrand Allows Us to Move Forward Without Dragging the Past Along The rebrand is not about erasing history (the TrueFi forum will remain, but separately for legacy discussions) but about building a project that can grow without constantly answering for events unrelated to the present.

This creates: A clear identity A cleaner narrative A more credible BD posture A healthier environment for tokenholders A fresh foundation for everything we build next

The Rebrand Requires Resources: Treasury Recapitalization

Executing a proper rebrand and transition (including audits, documentation, business development, integrations, design work, communications, and ongoing operational continuity) requires adequate funding. Minting the remaining TRU supply does not change the maximum token supply, was always contemplated in the original token design, and provides the balance-sheet capital necessary to execute this transition responsibly. This recapitalization ensures that the project can move forward without compromise and with the resources needed to complete the rebrand effectively..

Scope of This Proposal

1. Approve a Full Rebrand of the Protocol This includes: Developing a new project name and identity Updating documentation, branding, and public interfaces Migrating active governance, engineering, and communications to the new brand Retaining the TrueFi forum for historical and claims-related matters

2. Mint the Remaining TRU Supply Into the Treasury Funds will support: Rebrand execution Operational continuity BD and liquidity partner engagement Engineering, audits, and integrations Communications and documentation updates Additional liquidity for Cyan, lending vaults, stablecoin, and CDP infrastructure

3. Establish the Operational Framework for the Brand Transition The transition will include coordinating contributors around a unified rebrand plan, updating all public documentation and technical materials to reflect the new identity, preparing communication packages for partners and ecosystem participants, and ensuring that Cyan, the vault architecture, and the stablecoin/CDP systems are properly represented under the new brand.

This framework also includes planning the sequence of interface updates, consolidating governance and communication channels, and managing the rollout of the new brand across all user- and developer-facing surfaces. This proposal focuses exclusively on the brand transition and does not authorize any token migration or reconstitution, which would require separate governance action if pursued.

4. Resume and Complete Critical Technical Workstreams As part of the brand transition and in preparation for renewed growth, several technical initiatives that were previously paused due to funding and prioritization constraints will be resumed and completed.

This includes restarting the external audit process for Elara V1, which had been paused during earlier stages of the project. Completing this audit is a prerequisite for deploying Elara as a production-grade system and for engaging with partners that require formally reviewed smart contract infrastructure. In parallel, the CDP architecture will undergo its own independent audit to ensure the security, correctness, and robustness of the system before broader usage.

In addition, work on KYC and AML integrations (which had also been paused) will be resumed. These integrations are necessary to support compliant counterparties, enable broader participation in the protocol’s products, and ensure the infrastructure can support institutional and regulated use cases as adoption increases.

Finally, additional capital will be allocated to support early-stage liquidity requirements across the protocol’s products. This includes ensuring sufficient liquidity is available to support initial usage, testing, and partner onboarding, without relying on ad hoc or reactive measures.

Together, these workstreams ensure that the protocol’s technical foundations, compliance capabilities, and liquidity posture are aligned with the expectations of a modern, growth-oriented on-chain financial platform.

Implementation Timeline (3–5 Weeks) Week 0–1: Mint remaining TRU into the treasury Begin final brand development, naming, and design Prepare updated documentation and transition plan

Week 2–3: Announce new brand identity Begin migration of public-facing interfaces, documentation, and communication channels

Week 3–5: Complete migration to new brand Provide transparency report on treasury usage and remaining runway Publish updated BD, partner, and technical documentation under new brand

Next Governance Steps

As this proposal does not fall under simplified governance exemptions, it must follow the full governance process:

Forum Posting (72 hours): Community discussion and feedback period.

Snapshot Vote (48 hours): Options: OK to vote on Tally Not OK to vote on Tally Abstain

A minimum of 5% of staked TRU is required for quorum.

Amendment Period (72 hours): If quorum is met but “Not OK to vote on Tally” receives the majority, the proposal enters a 72-hour amendment and discussion window before moving forward.

Tally Vote: If Snapshot passes (or the amendment period concludes), the proposal proceeds to Tally for a binding on-chain vote.

Conclusion

TFIP-37 initiates a straightforward but essential step: separating the future of the protocol from the legacy of the TrueFi brand.

This allows the community to focus on what has actually been built (modern credit primitives, NFT-backed lending, stablecoin/CDP infrastructure, and a unified technology stack) rather than continuously answering for a past that no longer reflects the team, the products, or the direction of the project.

The combination of a clean brand and a properly funded treasury gives the protocol the best possible foundation for growth.