Introduction
Let’s stop wasting time and get back to work.
We’re burning valuable time as Cicada has been extremely motivated to keep getting pools live and we want to support and enable them.
We’re proposing a 3-month stopgap proposal so that we can continue to push with Cicada, help Adapt3r when needed, and maintain the momentum we’ve been building over prior months.
We propose extending the pricing of our last engagement so that this decision does not have to be as “controversial” and this gives alternative teams a serious amount of time to both get ramped up (alongside us) and come up with real new and novel ideas.
Timeline for Alternative Teams
An ideal 3-month timeline for new service providers that should happen in tandem with our work would include:
- 1 month of an RFP period where new service providers can make proposals without feeling rushed
- 1 month of review, debate, and selection
- 1 month of time for the new service provider to ramp up their work alongside us so that there is ample time for handoff and knowledge sharing
Next Quarter Work
Below is the list of tasks we had outlined to work on with Cicada:
- Distributing token incentives on Arbitrum
- We have hit the first two milestones for the lender incentive grant on Arbitrum and we need to begin distributing these. TrueFi will need to decide how to best distribute these ARB rewards to LPs, whether through farming contracts or periodic airdrops. You can track the early growth of the Arbitrum vaults here https://dune.com/truefi/truefi-alocs-on-arbitrum
- Partner Integrations for distribution
- We are currently speaking with two new stablecoin issuers and one large regional CEX (which is issuing a stablecoin) who are interested in partnering with Cicada to underwrite market maker loans on TrueFi and with two of the issuers looking to seed the pools. These would bring TrueFi new borrowers, new sources of liquidity, new assets to support, and interestingly, an opportunity to host one of the first non-USD stablecoins on a credit protocol. Besides normal pool deployment, additional non-standard development work might be needed before one of the stablecoins is to be adopted on the TrueFi platform.
- Wallet / Interface Integrations
- Somewhat related to the above, but unique – we are in conversations with a CeFi-like application and a web3 wallet that are interested in offering Cicada’s higher yielding pool opportunities to their users.
- Additional L2 deployments
- Wallfacer and Cicada are in advanced discussions with an additional Layer 2 network to deploy additional lines of credit with them. These pools would also be lender incentivized with the L2s native token as a part of an upcoming DeFi incentive program the L2 is running. Development work is needed to modify TrueFi contracts for this L2 network and to deploy on this L2.
Below is the list of tasks we had outlined to work on with Adapt3r:
- Adapt3r is in the final negotiations of becoming the collateral asset for “decentralized RWA stablecoin” and will need support in getting this live and may consider transitioning from “asset vaults” to “index vaults” for this integration.
This is on top of our existing and ongoing responsibilities that we do not normally break out, but include everything mentioned in the prior post
See specifically:
Additionally, we will support the board on getting up to speed on the current (healthy) state of the treasury. If no one else steps up, we can also consider putting forth a treasury diversification proposal.
There are some tasks from “Chapter 3” that we’ve deprioritized and we’ve refocused on more product, engineering, and business work that is more go-to-market driven.
Hand Off Tasks
There are additional “hand off” items that we also need to complete. We will (obviously) do these regardless of whether a new agreement is approved, but just flagging some other items as well.
- Wallfacer team members leave Truefi-protocol Github org
- TrueFi · GitHub - Currently this Github has owners from Archblock and Wallfacer. Archblock currently pays for this. To transfer ownership to the Foundation, the Foundation will need Github account(s) and a way to pay for it.
- Pass engineering / technical accounts to Foundation
- Netlify: Hosting service for truefi.io, truefi app, truefi documentation
- Foundation will need a way to pay for hetzner account, cloud hosting software used for testing
- Pass social platform accounts to Foundation.
-
For most of these, there will be no issue, but for some like forums and Twitter, the Foundation will need a way to pay. Additionally, the Foundation should have some kind of password manager we can use to securely pass login access for these accounts.
- Forum
- Discord
- Medium
- Substack
- TrueFi.io Google & Slack
- Dune Analytics
- Hetzner
- docs.truefi.io (gitbook)
Budget and duration:
3-months at a rate of 3,666,666 TRU per month with 20% upfront
Masa previously said,
We have strong preference for 3-months given the timeline outlined above, but if the sole motivated “NO” voter feels so strongly towards 2-months, we can do our best to accommodate. A hard extension of the prior engagement is 3,666,666 TRU/month. We’ll leave some time for discussion, but request an expedited timeline here as the normal period of 3 weeks would be a terrible loss for the momentum we have going.