Today is the day! @farsideapp officially launches its live trading bots on @HyperliquidX and @dYdX Thank you to everyone involved, everyone who tested the beta and everyone who has been so interested in what we are doing. So much more exciting ideas to come, this is only the beginning.

Back on Spaces with @farsideapp now! xitter.cf/i/spaces/1yxBePbvkwkJN

Live on spaces now @farsideapp xitter.cf/i/spaces/1qxvvemOlzWxB

Live on spaces tomorrow with @ChimpxAI and @Sonar_Trade

First spaces for @farsideapp happening tomorrow!

I've been in crypto long enough to know what content I respect and what makes me close the app. What I respect: - Accounts that focus on process, not outcome - Builders who explain how their systems actually work - Threads that break down market structure and positioning What makes me cringe: - "100x gem" culture - Buzzwords with zero mechanics behind them - AI products that overpromise and underdeliver Crypto has a content problem. Too many projects sound the same because they're all copying each other. That's why I built @farsideapp the way I did. Sharp. Systematic. We tell you exactly what the AI does and what it doesn't. If that's boring to you, we're probably not for you. If that's refreshing, you're exactly who we built this for.

Looking forward to attending @Hashlock_’s web3 event this week! I’ll also be doing a short pitch for @farsideapp at the event so make sure you tune in! luma.com/POC-July?tk=r4NON3

I did not expect legal and regulatory thinking to shape @farsideapp as much as it did. When you're building in crypto, compliance conversations feel like something you have later. After the product exists, after you have users, after things are moving. That was roughly my assumption going in. What actually happened was the opposite. The moment we got serious about what Farside could and could not do from a regulatory standpoint, it forced decisions that went all the way down to how the system was architected. Non-custodial was not just a philosophical choice. It became a structural requirement. Non-discretionary execution was not just a feature, but a constraint we had to design the entire permissions model around. At first that felt limiting. There were things we wanted to build that we had to pull back from because they would have crossed a line we were not willing to cross. But the longer we lived with those constraints, the more I realized they were making the product better. Every time we hit a wall, we found a cleaner solution on the other side of it. The non-custodial requirement pushed us toward a user-controlled execution model that I now think is genuinely stronger than what we would have built without it. Constraints have a way of doing that. They remove the lazy options and force you toward the ones that actually hold up. I am not sure I would have believed that at the start of this process. I believe it now.

One of the earliest decisions we had to make at @farsideapp was whether to build around centralized exchanges or decentralized ones. CEXs would have been the easier path. → The infrastructure is mature. → Onboarding is simpler. → The user base is larger. Every practical argument pointed in that direction. We spent real time considering it. I'm not going to pretend it was an obvious call. But every time we got close to committing to CEXs, we kept running into the same problem. To make a CEX integration work the way we wanted: automated execution, strategy management, real control, users would have to give us API keys. Which means giving us meaningful access to their funds. That's a form of custody. Maybe not technically, but functionally. And I couldn't get comfortable with it. Not because of regulation, not because of legal risk... but because it contradicted the whole reason I wanted to build this in the first place. If the system requires users to hand over control to work, then the system isn't actually giving them control. It's just moving who holds it. So we chose DEXs. → Non-custodial by design. → Users keep their keys, their assets, their execution authority. → Farside operates within the permissions they grant, nothing more. It made the development significantly harder. DEX infrastructure is less standardized, onboarding is more complex, the user base is smaller. We chose the harder path deliberately. What I learned from that decision is that the non-custodial constraint isn't just a feature. It's a forcing function. Every design choice we make has to work within it. And that discipline has made the product more coherent, not less. The easier technical path and the right product path are rarely the same thing. When they diverge, you have to decide early which one you're building for.

Going to be an exciting chat with @leagueoftraders on X spaces.

Looking forward to representing @farsideapp on this Space hosted by @vs1_finance tomorrow. See you there 🫡

Some World Cup predictions and hot takes 👇 🇺🇸 USA fail to make it out of their group. 🇵🇹 Portugal finally evolve beyond being built around Ronaldo. His role changes, the team opens up, and we see some of their best football in years. 🇧🇷 Brazil are going to surprise everyone. The only question is whether that surprise is a deep run to the final or a complete collapse. 🇨🇦 Canada make it out of their group and continue the progress we’ve seen over the last few years. 🏴󠁧󠁢󠁥󠁮󠁧󠁿 England once again fall short of the final. The pressure ramps up and Tuchel moves on after the tournament. 🇲🇦 Morocco prove their last World Cup wasn’t a fluke and make another impressive run. 🇳🇴 Haaland scores fewer than 5 goals. 🇰🇷 South Korea are the surprise package of the tournament. 🇦🇷 Argentina get a favourable side of the bracket and find themselves in another final. 🇪🇸 Yamal wins Player of the Tournament. 🇫🇷 France are knocked out much earlier than expected, either the Round of 16 or Quarter Finals. 🇪🇬 Salah arrives with a point to prove and scores more than 5 goals. What are your hottest World Cup takes? 👀 #WorldCup2026 #FIFAWorldCup #Football #Soccer