Anton Dosta retweeted
Anton Dosta retweeted
Crypto vendors hide fees in creative ways. Let's break down how these flows actually work.
First, to be clear, Polymarket has:
1. The lowest fees.
2. The fastest settlement.
3. The highest limits.
Here's how.
First, how do most crypto orchestrators work today?
A user attempts a trade. The orchestrator scans the market for the "best rate," picks a route on the user's behalf, and executes.
Sounds great. So what's the problem?
Issue 1) Markets are dynamic, and pricing can be poor
If you rely on orchestration alone, you will give users bad pricing at some point - markets aren't always efficient.
USDT to USDC trades at a floating market price, not a fixed one. As of writing, depositing USDT on Hyperliquid carries an 8.7bp markup & Relay costs 15.5bp. The same transaction on Polymarket costs 5.5bp.
The bigger the transaction, the worse pricing gets. A $10M USDT deposit through an orchestrator means brutal slippage, slow settlement, or no quote at all - funds stuck.
And it is worst exactly when it matters most. Markets dislocate hardest during high volatility, so users get their worst pricing during a big airdrop, election, IPO, or sports game.
To give users a good experience, someone has to eat the cost when markets aren't efficient.
Apps will say "we have zero fees" - but when markets dislocate, retail gets their face ripped off.
Btw – it is not possible to offer 1:1 USDT to USDC for deposits & withdrawals in any size without be arbitraged.
Issue 2) Most bridges can't guarantee SLAs
Say a user is depositing $10M into Polymarket. Try any leading router rn and you'll struggle to find a quote for a $10M USDT transaction. Should those transactions just get stuck?
What happens during the Super Bowl, when everyone bridges at once? We've seen liquidity on major bridges drop below $50k. Should users just not be able to deposit?
What happens when rebalancing goes down on a major chain? It happened to BNB recently - funds couldn't get off the chain. Should every BNB user eat 1h+ delays?
Every cross-application bridge (i.e., ALL bridges today) is exposed to these failures.
To give users a good experience, you need an app-specific bridge with real capital behind it - in Polymarket's case, >$10M dedicated to instant transactions for its users alone.
Apps will say "we can bridge from any chain" - then fall over when markets dislocate.
How does Fun + Polymarket solve this?
Fun + Polymarket routing combines three capabilities:
1. An OTC desk.
2. A world-class aggregator.
3. An app-specific bridge.
The result:
1. Best pricing from Relay, Across, LayerZero, CCTP, and others - at all times. Thanks to our relationships with Polymarket, Aave, Lighter & others Fun is one of the largest transaction originators in crypto. This size enables highly preferential pricing.
2. Fun steps in and takes the loss if routers can't deliver SLA-level pricing.
3. Fun holds $10M to fill the transaction if routers can't deliver the size.
This thread doesn't even mentioned the other infra to make crypto tx's great: transaction retries, gas retries, slippage monitoring, broad token & chain support, fast pickup times, RPC fallbacks, streaming fallbacks, and more.
@Polymarket and @Fun have iterated on this tech for two years. I'm proud of the work, and grateful for the partners we've built alongside.
I admire what the Kalshi team has built - this isn't a hit piece, and John is well-intentioned. But it is simply inaccurate to imply Polymarket has inferior crypto rails.
Polymarket supports larger orders, faster, with tighter settlement and greater uptime than any other crypto platform today.
Anton Dosta retweeted
if you're not happy single, you won't be happy in a relationship.
true happiness comes from building dashboards that give executives deeper insight into critical business functions
Today, we announce our $72 million Series A, co-led by @multicoin and @SignalFire.
fun.xyz/news/series-a
feels like a New Year's Eve!
Exchange upgrades starting now. The platform is under maintenance for ~1 hour. Trading is paused and the orderbooks are being cleared. Funds and positions are safe.
$1M in liquidity rewards go live when trading resumes. Updates in this thread.
Anton Dosta retweeted
We're excited to announce 'The Situation Room' by Polymarket is coming to Washington, D.C.
The world's first bar dedicated to monitoring the situation. 🧵
Anton Dosta retweeted
1/ 🎉 Introducing Ethereum House: a builders studio in downtown SF accelerating Ethereum’s next generation of hackers, researchers, and founders. Taking over a full floor @frontiertower, led by @ergokhaner & @_mia_56_
Anton Dosta retweeted
The Ethereum House - the key node in the @ethereumfndn Schelling Point in Silicon Valley has found its home at Frontier Tower’s 12th floor - welcome!
Check the full thread below to learn more and find out how to join us.
Replying to @ethereumfndn
1/ Ethereum House will plant roots at @frontiertower on the 12th floor, now entirely dedicated to Ethereum.
The space includes room for meetups, coworking, and even a station to build your own validator.
Other floors in the House focus on d/acc, longevity, AI, and robotics.
Anton Dosta retweeted
0/ Say hello to @ethereumhouseSF
A local hub for Ethereum builders, researchers, founders and investors in San Francisco’s @frontiertower. We’re excited to be supporting the Ethereum House with grant funding and collaboration from EF team members.
Anton Dosta retweeted
Some thoughts on Radix, component libraries, and shadcn/ui.
We’re at that point in the web dev cycle where we’re talking about component libraries again. That’s okay. With Radix receiving fewer updates, it’s a conversation worth having.
Let me start with this and I’ll bold it: The worst thing you can do right now for your production app is switch component libraries.
Don’t do it. That’s not where your time or resources should go. Whatever bug you’re seeing with Radix in your app, you’ll likely run into more, including new ones, with something else. (No shade to anyone. That’s just how code works.)
Yes, Radix is getting fewer updates. But Radix is still a mature, well-designed library, battle-tested and used in millions of production apps. Code doesn’t stop working just because maintainers move on. That’s the strength of open source. And what Radix does, it still does extremely well.
Here’s what I’d suggest:
- Already using Radix in prod? Stick with it.
- Starting a new project? Consider Radix, React Aria, or Ariakit. All great choices.
- Using Radix and thinking what's next? Keep an eye on Base UI (we are). It’s built by the same smart team that created Radix. They’ve done it once. Now they get to do it again and it’s looking really good (currently in beta).
- Hit a bug with Radix and can’t find a fix or patch? Try testing the equivalent from Base UI. The APIs are very similar.
- shadcn is built for this. Code you own. Code you can improve, rewrite or replaced.
The most important thing: Use something that works for you and that you understand. Your component library should be stable. This isn’t where you want to take risks in your tech stack.
Every new project (not just component libraries) goes through growing pains: bugs, API changes, missing features, incomplete docs. It’s okay to wait it out, especially for production apps.
Now, where does shadcn/ui fit into all of this?
shadcn (unfortunately named 😅) is not a component library. It’s an idea. It’s a combination of a few things: an open abstraction, great defaults, and a distribution system.
- An open abstraction built on top of several component libraries. Radix being one of them. It’s code you’d write yourself, structured in a way that’s easier to work with. Loved by LLMs.
- Carefully chosen defaults that handle the smaller things like focus states, animation styles, variants, and components that naturally fit with one another. Just enough to be a great starting point, and just enough to get out of the way when you’re ready to build your own design system.
- A distribution system that makes it easy to build, generate, and share code. Built for AI.
The component library is just one layer of shadcn. And if it ever comes to it, a swappable one.


























