the final tab for @solana yield
- Tweets 280
- Following 11
- Followers 8,085
- Likes 128
Pinned Tweet
Big one: everything that powers Yieldbay is now a public API.
app.yieldbay.fi/developers
Wallet portfolios, live yields, personalized recommendations, and protocol health, the exact same engine behind our dashboard, now available for anyone to build on.
Currently live in Beta.
8
15
50
2,766
Yieldbay Yield Report #5 🌊
SOL reclaimed $120 for the first time since January. Capital is rotating out of DEX speculation and into yield. Liquid staking TVL up double digits this week.
Where that yield actually is, and what's safe underneath it 🧵
7
17
45
2,537
Health, 6 protocols:
→ Perena USD*: still 2 open critical alerts, collateralization at 0%. Five weeks running.
→ Kamino kVaults: sharp inflow +299% on wYLDS Allocator. Two supply mismatches, both recovered.
→ Jupiter Earn: balance drop warnings.
38 events tracked. The biggest hack of the year (Bitget, $351M) also landed this week. Not on Solana.
Still the reminder.
1
1
30
The market did the risk-pricing for you this week. The critical protocol's yield fell. The healthy one's rose. They met at the same number.
That gap closing is what you should be watching, not the top of the leaderboard.
app.yieldbay.fi
24
Yieldbay Yield Report #4 🌊
The Fed just hiked for the first time since 2023. SOL reclaimed $105 as the strongest major. Galaxy launched new vaults on Kamino.
When the risk-free rate moves, it's worth re-checking what your on-chain yield is actually paying you for.
Here's where things stand 🧵
7
13
49
565
Health check, 6 protocols monitored:
→ Perena USD*: 2 open critical alerts. Collateralization at 0% on two entities. This has been critical since our last report four weeks ago.
→ Kamino kVaults: balance drop of -23.89% on Neutral Trade USDC Max Yield, still open. Two supply mismatches this week, both recovered.
→ Jupiter Earn: balance drop warnings.
35 important events tracked.
1
2
116
This is the report in one line: the highest stablecoin yield on Solana right now is also the one flashing critical.
Rates are rising. That raises the bar for every DeFi yield to justify its risk. Chasing the top number without checking what's behind it is exactly how people get caught.
Connect your wallet, see every position ranked by return and by safety.
app.yieldbay.fi
2
123
Solana just went from 1,232 → 4,096 bytes per transaction.
Not the sexiest upgrade to tweet about, but probably one of the more important ones.
Complex DeFi routing, ZK proofs and multi-approver flows just became a lot easier to build.
Curious to see what people do with the extra room.
10
15
43
5,543
Big one: everything that powers Yieldbay is now a public API.
app.yieldbay.fi/developers
Wallet portfolios, live yields, personalized recommendations, and protocol health, the exact same engine behind our dashboard, now available for anyone to build on.
Currently live in Beta.
8
15
50
2,766
No email signup. API keys are owned and controlled by a connected Solana wallet, created, rotated, and revoked with a signed message. Fully non-custodial, even for key management.
Built for agents too: LLM-friendly docs at api.yieldbay.fi/docs.md and a discovery file at /llms.txt.
(Tested against three different LLMs, including a genuinely bad one, all three parsed it correctly first try.)
1
29
This is a limited free beta preview right now. A paid tier with significantly higher limits is coming soon for teams building production integrations.
Already have a health-only key? You'll need to rotate it to unlock the new endpoints.
Docs: api.yieldbay.fi/docs
Get a key: app.yieldbay.fi/developers
23
We've shipped quite a bit around Protocol Health lately.
But Health is only one piece of what we're building with Yieldbay.
The bigger goal is simple: one place to understand what your capital is doing on Solana, what could be doing better, and what actually deserves your attention.
Positions. Yield. Opportunities. Risk. Eventually execution.
All in one place.
6
15
89
1,266
A Solana neobank got hit for $500K last week. Here's what actually happened, and why it's a good case study, not a hit piece.
6
22
94
11,180
The real lesson: a vulnerability sat live in production until someone exploited it. A one-time audit doesn't catch a contract that becomes dangerous after the fact.
That's the entire case for continuous monitoring instead of a point-in-time check. Watching what's live, not just what was reviewed once.
1
1
83
This is exactly why we built Protocol Health the way we did: real-time on-chain state, every 5 minutes, watching for the kind of anomalies that don't show up in an audit that happened months ago.
app.yieldbay.fi/health
1
41