I want to be more explicit here, because vague language doesn’t help anyone.
When I joined a little more than a year ago, TrueFi was beyond a lightly misaligned project. It was in outright distress.
Monthly spend was close to $450k, much of it tied to long-dated service contracts providing little value, fragmented process ownership, and legal exposure that could not simply be shut off without risking further damage. Unwinding those arrangements required care, negotiation, and time. During that period, execution was constrained whether it was visible or not.
On a practical level, progress was repeatedly slowed by things most people never see:
-
Chasing down long gone multisig signers just to move funds or approve changes
-
A legacy development shop that was unresponsive at critical moments, directly impacting front-end timelines
-
Partial access to infrastructure and repositories, making even simple updates harder than they should have been
-
Navigating uncomfortable but necessary conversations around prior governance decisions and serious legal matters of previous leadership
None of that shows up on a roadmap, but all of it materially affects velocity.
Strategy pivots were not cosmetic
At the time, the prevailing strategy was to build a heavily regulated, compliance-first marketplace. That path would have been extraordinarily expensive, slow, and very likely unsuccessful. A DAO is simply not well suited to securing certifications like SOC 2 Type II or operating like a traditional regulated financial institution. So, we had to shut that down, but as the new guys there’s some time needed to navigate the internal politics… even in a small organization.
Pivoting away from that direction was necessary. It was also disruptive. Some teams were understandably unhappy about moving away from work they had been contracted and compensated to do, and that friction further slowed execution.
The disappointing reskin many people point to was not a lack of effort. It was the result of trying to move forward while disentangling a structure we did not fully control.
Elara: a real setback, handled honestly
We believed Elara could be a winner. The idea was sound. The execution was not.
Leadership issues, missed commitments, and poor coordination let both the community and the broader team down. That was compounded by market conditions that made raising capital difficult and compressed yields to the point where the original launch assumptions no longer worked.
Importantly, this wasn’t ignored. Personnel and responsibility changes were made to reflect those failures, and the project was restructured accordingly. That process was uncomfortable, but necessary, and it materially changed how the work is now being executed.
Rather than abandon the effort or push something live that wouldn’t survive, we chose to retool it properly and leveraged our network to connect with more sustainable collateral sources.
What is moving forward
Despite the setbacks, progress has continued across multiple fronts:
-
Cyan has been a real bright spot. The upcoming marketing and growth push is on schedule relative to what was outlined in earlier forum posts.
-
A live lending vault with Accountable is coming online in days to weeks. Due diligence is complete, paperwork is signed, and we’re in final implementation.
-
Elara is close, and internally there is genuine excitement about finally bringing it live in a form that makes sense economically. Owning this treasury management asset and the tech to loop it means genuine profitability, which will be notable in the crypto ecosystem more broadly.
-
The portions of the rebrand that could be completed without breaching governance constraints are done, and we’re looking forward to sharing the full picture once approvals are in place.
Governance and transparency
Governance friction is real. It is not being ignored, and it is not slowing execution behind the scenes, but it does create visible bottlenecks at decision points. We are actively working through how to improve this without undermining the DAO’s role.
Wallet analysis, token sales, and intent
A number of the conclusions in the post rely on on-chain analysis that, while detailed, draws incorrect causal links.
Yes, tokens have been sold historically following funding approvals. That is not hidden, and it should not be surprising. Approved budgets still need to be converted into operating capital to pay vendors, contributors, and obligations that are largely denominated in fiat or stablecoins.
Where the analysis goes wrong is in assuming intent from timing.
Token sales were not executed to “prolong funding,” manipulate governance outcomes, or extract value. They were carried out under real operational constraints, including:
-
Limited liquidity windows
-
Fragmented legacy wallet structures
-
Execution dependency on legacy multisig signers
-
The need to honor previously approved commitments
In several cases, sales that appear discretionary were simply the first opportunity available to execute once access issues were resolved.
The important distinctions that were missed are:
-
Programmatic vs. opportunistic execution: sales were driven by operational necessity and access, not market timing
-
Use of proceeds: funds were applied to stated operating costs and obligations, not diverted elsewhere
-
Supply dynamics: these actions did not materially worsen long-term supply overhang and were part of stabilizing the project, not extracting from it
We may not have done a good enough job explaining how funded tokens are handled in practice, what execution constraints existed at the time, or why movements sometimes clustered in ways that look suspicious in hindsight. That opacity created space for speculation, even where the underlying activity was legitimate.
That said, our financial activity is detailed in DAO reports, and I stand by the rigor of that disclosure.
On-chain transparency is a feature, not a bug. But transparency without context can lead to confident conclusions that simply aren’t correct.
On transparency more broadly
I’ve spent over 20 years in equity markets, including public micro-caps. I can say with confidence that this community has far more visibility into operations, spending, and internal debate than equity holders typically do.
That doesn’t mean we can’t do better. We can. And we will.
I appreciate the candor in your comments here and in chat, Don. Your tone is professional, and you’re looking for clear answers. That’s fair, and it’s respected.
At the same time, it’s important to recognize that this is already a far more open book than most comparable structures, and that building entirely in the open is not always strategically viable.
Where we go from here
This has not been a straight line. There have been missteps, pivots, and lessons learned the hard way.
What matters now is that:
-
The cost structure is sane and continues to be reworked to align with economic reality
-
The product direction is grounded in reality
-
The pipeline is active
-
And the team is still here, still executing
We’re not giving up. We’re building through the mess, not pretending it didn’t exist.
The questions, pushback, and scrutiny are fair. We welcome them. All we ask is that they’re grounded in facts and paired with an understanding of where we started and where we’re actually headed.
More concrete updates are coming soon. The DAO report will provide additional granularity, and as governance progresses, we’ll be in a position to share the new branding with the community.