FeedProjects
Developers
Settings
๐ŸŽ‰ A new chapter begins: Boardroom has joined Agora
Learn more
protocol logo
Explore / Projects
TrueFi

Proposals

Discussions

Members

Information

Create Proposal

TrueFi

ProposalsDiscussionsMembersInformation
Proposal
Back to Proposals
closedEnded 4 years ago ยท Snapshot (Offchain)

TFIP-1: Claim Proxy Ownership of Lending Pools

By 0xf6E2...0Ea521

Author: @hal

TFIP-1: Claim Proxy Ownership of Lending Pools

Abstract

This proposal intends for the TrueFi DAO to claim ownership of tfLP liquidity pools in the TrueFi protocol. The goal of this proposal is to extend the decentralization of the protocol.

By claiming proxy ownership, the DAO will fully control upgrades for these smart contracts. Therefore, the only way to modify the code or logic for these contracts would be through a governance vote on-chain.

Motivation

The TrueFi protocol includes 4 permissionless pools: tfTUSD, tfUSDC, tfUSDT, tfBUSD. The liquidity in these pools has been controlled by stkTRU votes, but the actual ownership of the smart contracts has been managed by a multisig. In order for these pools to be truly decentralized, control of upgrades to these contracts must be controlled by the TrueFi DAO. Claiming ownership of these contracts allows the DAO to fully own and operate its own liquidity pools.

Summary

TrueFi uses a smart contract proxy pattern - each contract consists of a proxy (public facing address) and an implementation (actual code). Code from the implementation is loaded into the proxy contract every time someone wants to interact with the smart contract. The proxy owner has the ability to change the implementation contract in order to add new functionality or logic.

In order to control the smart contract proxies, a function call needs to be made to each liquidity pool proxy address. Before the claimProxyOwnership() function can be called, the previous owner multisig will call the transferProxyOwenrship() function.

Actions

  1. Call claimProxyOwnership() on 0x97cE06c3e3D027715b2d6C22e67D5096000072E5
  2. Call claimProxyOwnership() on 0x6002b1dcB26E7B1AA797A17551C6F487923299d7
  3. Call claimProxyOwnership() on 0xA991356d261fbaF194463aF6DF8f0464F8f1c742
  4. Call claimProxyOwnership() on 0x1ed460d149d48fa7d91703bf4890f97220c09437
Continue Reading
Connect Wallet to Add Note
0
Votes 5
VoterCast PowerVote & Rationale
0xCAD8...f4f4D3
4.372M

YES

0x7d96...576D34
2.771M

YES

0x0562...961516
750,000

YES

0x46dF...33c428
74,625

YES

0x0773...97DdD0
1,435

YES

VOTE POWER
0
Connect Wallet
Proposal Status
  • Fri May 20 2022, 02:31 pmVoting Period Starts
  • Mon May 23 2022, 02:30 pmEnd Voting Period
Current Results

1-YES

7.97M

DocumentationBrandingContact Us
Home
This Project is Currently Disabled

If you would like to enable it, please checkout below.

Boardroom Subscription

Sign up for an individual subscription (access all projects on the platform)

Subscribe
Enable Project

Enable the entire project for every user

Enable Project
Contact Us