Penn Blockchain Delegate Platform

Initialize Compound III (USDC on Ethereum)

We voted FOR: We’re excited for Compound v3 to come live and this was an easy no brainer. We want to congratulate the team for their hard work and also look forward to what this next version will bring!

1 Like

Compound Oracle Upgrade v3

We voted FOR: Crucial to update the protocol’s oracle contract to v3 as well, switching the anchor market from UNI v2 to v3.


cETH Risk Mitigation

We voted FOR: Our reasoning is very similar to our reasoning for Aave pausing ETH borrows. The extra revenue generated from a couple days of high ETH borrows we fee is not worth the inherent risks around the uncertainty of the initial post merge defi landscape.

Risk Parameter Changes for FEI

We voted FOR: Our hearts go out to eh FEI/Tribe team and hope they can peacefully wind down. There is no need for FEI on Compound anymore.

Initialize Compound III COMP Distribution

We voted FOR: As the emphasize revolves to Compound III, we believe this incentive shift is a good move in reaching that goal.

We have officially rebranded our Compound governance as FranklinDAO!

Everything will stay the same, just in the spirit of Web3, our outward facing name is now FranklinDAO!

PS: If a community admin can change our name to “FranklinDAO (UPenn) Delegate Platform” that would be very appreciated!:slight_smile:

Gauntlet <> Compound Renewal

We voted For: This was an overwhelming yes! We have seen the great work the team has done for Compound and think it should be continued for the following year. The analysis speaks for itself and after a nice talk with the team, we’re looking forward to their updated risk dashboard and new features in the future!

1 Like

Increase Compound III Supply Caps

We voted For: We think Compound III is ready to increase supply caps following the Gauntlet proposal. We look forward to the continuous growth of v3!

Risk Parameter Changes for FEI: Part 2

We voted For: In favor of the necessary steps needed to wind down FEI markets as the project unwinds.

1 Like

Adjust cCOMP and cUNI Parameters

We voted For: Pending the analysis put forward by Monet and forum post/discussion, we believe the adjusted parameters are sufficient and should be inplemented.

Pause Supply for Compound Assets

We voted YAE: Voting yes as a safety precaution in light of recent news regarding price manipulation possibilities. Will reassess to increase and adjust parameters in the future, but feel right now these more conservative estimates are safer.

1 Like

Liquidation Event Handling And Collateral Reserves

We voted FOR: Thanks for the team for catching this minor “error.” This update will make analytics and etherscan view for liquidations easier to manage and see!

1 Like

Risk Parameter Updates for 1 Collateral Asset

We voted FOR: Voting in line with our prior reasoning across Compound and Aave regarding adapting collateral factors to ensure safety and liquidation risks.

1 Like

CIP-1: Compound Improvement Proposal Adoption

We voted YES: We’re happy to see the adoption of CIPs! Having been Maker and Aave delegates for a while now, this "x"IP structure is great for access and clarity and we’re excited to see what proposals come to be!

Borrow Caps for Compound V2 Assets

We voted YES: After reviewing the discussions between Paul from Morpho and the Gauntlet team, we are glad to see only the most volatile assets in this formal proposal, and are in agreement that these borrow caps should be changed accordingly. When it comes to an eventual proposal for the stable assets with a lot more on chain liquidity, we think maybe a compromise between the two parties is appropriate, or a slight increase in the caps recommended on the forum post.

Note: Ethereum Transaction Hash (Txhash) Details | Etherscan
We submitted with about 2 minutes left, and high gas, but looks like on chain transaction failed. Might be a bug or UI issue where the voting technically ended before the UI showed it ended.

CGP 2.0 by Questbook

We voted YES: Looking forward to see the startup of the new grants program. We believe season 1.0 went pretty well and are excited to see the newly improved version. Also would love to get more involved and possible take on a research grant ourselves in the future!

Risk Parameter Updates for 1 Collateral Asset on the Comet USDC Market

We voted FOR: We are in favor of this Gauntlet proposal to increase the supply cap of COMP on the USDC market to increase to 900,000 as we trust their models’ judgements and think this is a reasonable change.

1 Like

CGP Hackathon Sponsorships in 2023

We voted YES: We think these hackathon sponsorships are appropriate and look forward to seeing what projects arise from the tracks!

1 Like

Initialize cUSDCv3 on Polygon

We voted FOR: We’re excited to see this first cross chain deployment of Compound III and look forward to seeing the eventual deployments across other chains as well! This deployment will bring millions and millions of more TVL and liquidity to Compound and we’re excited to see Compound go crosschain!


Compound V2 → V3 Migration Phase 1

We voted FOR: We’re looking forward to Compound V3 over the next few months and thank the team and all respective service providers for their hard work. :blush:

Risk Parameter Updates for V2 and V3 WETH Comet

We voted FOR: Voting to change the risk parameters for cWBTC and cbETH as specified in the proposal.

Announcement to the Compound community from the governance team at FranklinDAO.

As part of an effort to strengthen our internal organization and operational security, we’re migrating our delegate profile (franklindao.eth) to a hard wallet at 0xCc878369b26127BD4bC1B0B465bC8bE9b92a4c62.

Our old address (0x070341aA5Ed571f0FB2c4a5641409B1A46b4961b) will remain active in protocol governance for the next month until June 15, 2023, so as to give everyone ample time to re-delegate their tokens.

We appreciate all of the holders that have entrusted us with their voting power and look forward to meaningfully improving the projects we all use on your behalf.

We are always accessible via the forums or Twitter @franklin_dao for any questions!