Dax

So I am going to keep building and releasing what is needed to protect the community and keep it alive until someone actually wants to sit down and talk.

I’ve stayed in Slack and with counsel, trying to find a fair, written resolution because I believe in the team and wanted to keep this out of a public dogpile. When legal threats were made, I moved everything to the lawyers and have stayed at that table, ready to clarify IP and economics properly. I’m not going to argue contracts on X, but I remain willing to resolve this through proper legal and accounting channels and to make sure the community and team are taken care of. But I have been waiting for someone to actually come to the table with me and so far only two people have actually come forward to talk.

@ShannonBeing Free will man, but dude we did it. We built a working privacy platform. The core model works and supports the token in real ways. I am proud of everyone who has come along for the ride and we can continue to build.

@dev_skill_issue I think it's an appropriate message. Don't know what others are expecting, but one things certain... They sold.

my outcome goals are to protect the project, create pace and balance that is good for my health to contribute and remove myself from day to day business management to write code only and be compensated as the OG w a small licensing or royatly fee from revenue. I have even been willing to do a single day transition with the whales to decentralize and protect the project or put it under a business leader who can take it farther than I can. As for writing code I will still show up everyday and continue to build as my health allows. @ZeraLabs

Yes, I had exploratory conversations with Perkins about a potential acquisition of ZeraLabs. These were early-stage, non-binding discussions... no offer was in place, and no transaction was imminent. Nor did I expect that doing so would mean I would just drop everything. I did this bc they are honest and well meaning group. Bc of that, I made the decision to keep the conversations limited rather than broadly sharing something that might never materialize. In hindsight, I understand why that decision is being questioned, and I take that feedback seriously. To be clear: there was no finalized deal, no signed terms, and no change in ownership or control of the company at any point. On the metrics and valuation: early-stage crypto projects are often valued on forward-looking potential, not just current fee generation. That said, I understand that different parties reached different conclusions during diligence. That is what back and forth is for. As well as my health conditions which have developed. Healthcare in the US is not cheap. I also want to acknowledge the concerns being raised around contributor expectations and ownership. Those are important, and I’m taking steps to review and clarify them directly with the people involved, I have been sitting at that table for weeks and the other side has not showed up. Instead trying this in the court of public opinion. I’m committed to protecting this project and protocol. Esp as we move to open source and fully decentralize it.

On May 20, 2026, @dev_skill_issue approached me regarding a potential acquisition of @ZeraLabs. He presented the business as generating income at around $10k MRR and discussed valuations substantially higher than what I would conclude after reviewing the materials provided. After receiving the pitch deck and reviewing the metrics, I found that the protocol itself had generated less than $1 in protocol fees over roughly 77 days, with lifetime deposits below $10k and limited usage compared to the valuation being discussed. I shopped the opportunity to several VC parties. The feedback I kept receiving was that the protocol faced significant operational, compliance, and legal hurdles that made it practically impossible to justify the valuation that was provided. While these discussions were happening, I was unaware that contributors and team members were not informed that acquisition discussions were taking place. After speaking with multiple insiders, I learned that several people involved with the project claim they had no knowledge of these conversations. They didn't even know it was on the table. When screenshots later publicly surfaced, I was expecting a transparent explanation from leadership. Instead public reassurances were spouted that did not address the underlying concerns being raised by large scale VC funds. Attached is the acquisition conversations, valuation discussions, and acquisition materials so the community can review them and draw its own conclusions. A concern that emerged during my due diligence was contributor ownership and intellectual property concerns. Contributors have publicly claimed substantial authorship of the codebase, while also alleging promised ownership interests. I have not verified those claims, but they were significant enough that they should be brought up. The screenshots, pitch materials, and conversations are attached below.

@42_onsol @PerkinsFund Oh that, yea while in maintenance mode I can find ur deposits and return funds but we dont have a drain method on the pools just a freeze method if something breaks.

@dev_skill_issue @PerkinsFund So that's why @PerkinsFund didn't want to expose you. He is part of all this.

I am still here and so are the whales we are still working and building releases... you all saw me build and deploy new stuff and the dectralization plan for the relayer earlier this week. Nothing is going anywhere. And yes we have internal disagreements and I am sick but still showing up so we are gonna keep on going and Monday whales and the chat and the socials will clarify exactly who is doing what.

Thanks everyone for the help w the bug reports and the new pools! @ZeraLabs

merkle tree indexer bugs are up there with cache invalidation as the hardest class of bugs the chain is the source of truth, your indexed view is "eventually" consistent, and the gap between them is invisible until a user can't withdraw their own funds so its not an easy to catch error...

@42_onsol @kayitardio @dev_skill_issue He’s enjoying pride month

Coming back to this, the issues with $Zera are still unresolved, and there is no new information as the price keeps dropping. @dev_skill_issue ,you need to start being more responsible with users funds and actively communicate the progress.

Wow telegram be slow today... thanks for pointing out more bugs everyone! Its def a squashing kinda week.

So we wanna get rid of the whole relayer thing in privacy protocols... I made a demo and proof of concept we can roll into @ZeraLabs feepool-demo.zeralabs.org/zera

I wrote about this kind of exploit 2 years ago even published demos for research blog.skill-issue.dev/blog/rusty_pip…

Its pride month. I may be proud to show something off this weekend. @ZeraLabs

@solana_devs Real Privacy @ZeraLabs

Video react to this tweet with what you're building on Solana We'll RT the best ones

Should be fixed try sending some of the new ZEC ! @ZeraLabs

Deploying another pool! Fixing bugs... @ZeraLabs x.com/i/broadcasts/1…

Ooops turns out I broke something lol. Speed run deploy this afternoon after lunch and meeting.

Surprise it was a short VC... ran out of time but we just dropped USDT support @ZeraLabs

Who is excited for the group VC on Monday?