Your cross-chain DeFi command center is here - save time and maximize revenue with one signature for complex cross-chain flows!

Joined July 2025
151 Photos and videos
Pinned Tweet
Feb 18
Ymax Early Access is LIVE πŸ”₯ Tired of juggling stablecoins across wallets, bridges, and protocols? Constant monitoring, clunky multi-step transactions, missed yields?? ↓
34
69
244
19,052
Jun 10
gmax, EthEconf πŸŒ… πŸ—½ See you on the floor!
Jun 10
Already the last day? Day 3 of ETHConf is here. β˜€οΈ Doors open at 8:30 AM. Grab breakfast, say hello to someone new, and enjoy every minute of the final day.
4
10
89
2,643
Ymax retweeted
That's a wrap for Day 2 at ETHConf. πŸ—½ The talks mattered. So did the moments between them. Packed stages, technical talks, hallway conversations… and yes, the doggos. 🐾 Watch the playback ↓
15
22
144
30,203
Ymax retweeted
One signature, multi-chain execution, DeFi yield without the complexity. Stop by the @Ymaxapp at ETHConf to learn more.
2
1
14
583
Jun 8
Wait did @DeanTribble just say AGENTIC YMAX??? πŸ‘€ πŸ‘€
6
12
83
5,066
Jun 8
Orchestration extends the mandate into a trust layer πŸ‘€
5
10
58
1,890
Jun 8
Smart contracts enforcing AI mandates on-chain πŸ‘‡
4
5
53
2,209
Jun 8
What can we do to make agents trustworthy for on-chain finance? "You can't watch your way to trust!" - @DeanTribble / @ethconf
5
12
71
5,071
Jun 8
Now on the breakout stage! @DeanTribble on agentic finance at @ethconf πŸ”₯
4
14
66
4,838
Jun 8
gm New York City! πŸ—½ Welcome to @ethconf! Come find us on the floor right next to the Barista Bar in Lounge 2. Grab a coffee and let's talk yield β˜•
7
6
59
5,495
Jun 4
ICYMI: New in Ymax: instrument status visibility. Pools now show their exact status β€” At Capacity, Paused, Deprecated, or Low Liquidity. Try it out: t2m.io/dxx0wie
5
3
73
5,104
Jun 4
Getting started with Ymax just got a lot simpler. New onboarding: curated portfolios, ready to go. Pick one, sign once, your capital is deployed. Nothing locked in β€” adjust, override, or build custom anytime. Read more: t2m.io/qucCM4F
4
9
82
5,607
Ymax retweeted
Jun 4
The Instagram hack was not just an AI chatbot story. It was a confinement failure. Attackers did not crack passwords or exploit a sophisticated zero-day. They convinced an AI support chatbot to add a new email address to high-profile Instagram accounts, then used that access to trigger password resets. That matters because AI agents are increasingly being connected to live systems with real authority: account controls, user data, financial workflows, customer support tools, enterprise software, and more. When an AI agent has broad standing authority, the agent itself becomes an attacker-accessible trust boundary. The lesson is not simply β€œmake the chatbot smarter.” The lesson is: don’t give the agent powers it should never have in the first place. This is the problem object-capability security and the @__Endojs__ framework are designed to address. Authority should be explicit, scoped, auditable, and revocable. An AI agent should only be able to act with the exact capabilities it has been given for the task at hand. No more ambient authority. No more assuming a helpful agent is a safe agent. Confinement is not an advanced feature for AI systems. It is the foundation. Read more about it in our latest blog post dcfoundation.io/the-instagra…
1
5
12
535
Jun 3
ICYMI β€” we'll be at EthConf NYC next week. Come find us if you want to talk cross-chain execution, onchain capital management, or why one signature beats fifteen. Drop a reply or DM if you'll be around. πŸ‘‡
4
6
91
6,353
Jun 2
More information on your positions is now available in the Ymax UI. Non-custodial doesn't just mean you own the assets, it means you have total visibility. Try ymax: t2m.io/PMu1Ex3
9
13
105
6,087
Ymax retweeted
Robinhood's AI agent trading launch is a real milestone. It's also highlights something the industry often gets wrong. The question isn't "should agents manage capital?" They should. It's "what authority model they operate under?" Giving an agent keys or broad wallet permissions is the wrong answer. You can only explain misbehavior rather than prevent it. What financial agents actually need: β†’ Constrained execution: an agent only act within an explicitly defined scope. Not "we trust it won't" but "it architecturally cannot" β†’ Revocation: the user can pull authority at any time, without needing the agent's cooperation β†’ Auditability: every action is visible and attributable before and after it happens, not reconstructed from logs after something goes wrong This must live at the authority layer, in the smart contract, not in a compliance dashboard on top of unconstrained execution. The agent might move your capital into a low-yield fund. That's fine, that's what you authorized. But it should be architecturally impossible for it to send funds to an unapproved address, bridge to an unapproved destination, or act outside the scope you set. Agents need contracts, not keys.
1
8
29
1,267
Jun 1
Manual cross-chain rebalancing: 15 transactions. 11 minutes. Multiple bridges, approvals, and signatures just to move capital where it needs to go. Ymax: 2 transactions. Under 2 minutes. Same outcome. One signature. That's what orchestration actually looks like. Episode 0 ↓ t2m.io/GQa1XPA
3
75
4,286
Jun 1
Our CEO @DeanTribble is speaking at @ethconf NYC next week! He'll be talking about enforceable guardrails for agentic finance. If you're building at the intersection of AI and onchain capital, you don't want to miss this one. πŸ“ NYC | [ Jun 8, 12:40 - 1:00 PM ]
🌟 NEW ETHConf speaker announced: @DeanTribble, CEO at @agoric Co-designed the first production smart contract at AMiX in the 1980s. Co-architect of Microsoft's Midori object-capability OS. Now runs Agoric, the JavaScript smart contract platform. June 8–10, NYC. πŸ—½
7
12
92
3,644