And what a time to enter AbcCVX right now.
U get to take advantage of the discount on ur way in too, currently its a bit wider than been for awhile.
Result?
Even more CVX working for yah, autocompounding and up to 40% APR.. (veCLEV Max boosted)
Higher than vlCVX, as usual..
This is my vault, this is my yield, this is my boost!
Yesterday Yieldtern caught himself chasing one more bad headline.
Banks glitching. Grounded flights. AI-assisted attacks. Crypto hacks. Iran. Then a dinosaur in Mexico and a prophecy about 90 days without power.
At some point he couldn’t tell what was real, what was exaggerated, or what was pure bullshit.
Still kept scrolling.
He’s never bought into the idea that one religion owns the answer. Maybe they’re all describing the same mystery from different corners of the room.
One Source, experiencing itself through everything. The beautiful and the brutal. Good and evil might just be names we give parts of a much bigger experience.
Doesn’t mean he has to like the brutal parts. He sure as fugg doesn’t have to go looking for them.
Yet there he was, voluntarily feeding his mind more fear.
Strange thing about free will.
We get to choose what we experience, then hand the choice to a feed.
Maybe the lesson yesterday wasn’t in any of those headlines.
It was noticing who kept clicking.
AI might be crypto’s biggest threat.
And ironically, its most natural path forward.
CT is capitulating. Yieldtern suspects some of that fear goes beyond another ugly chart.
He can sit through a nasty drawdown. One bad signature, a broken contract or a compromised operator emptying the wallet?
Can’t exactly DCA ur way out of that.
AI is making it cheaper to hunt for weaknesses. Even the big players struggle with security.
What happens to the small DeFi teams running on a fraction of their budgets?
And yet.
Humans were never going to spend their lives watching bridges, collateral ratios, governance votes and every token approval.
We built programmable finance, then expected people to babysit the whole damn machine.
Maybe AI becomes the missing operator.
Give an LLM unrestricted wallet access? Fugg no. Yieldtern didn’t get into DeFi to trade bank middlemen for a bot holding the keys.
Give the agent a job, hard limits and permissions you can revoke. Let it watch risk, manage collateral and handle the boring work without handing over ownership.
Yieldtern keeps coming back to one thought..
Maybe crypto isn’t waiting for another wave of retail users.
Maybe it’s waiting for an entirely different kind of user.
Yieldtern hopes the next degen on f(x) fuggin prints.
Yep. While his $FXN is locked.
Imagine needing ur own customers to get rekt so the owners can eat. Fugg that business model.
From Oct 12 to Nov 8, f(x) TVL dropped almost 30%. Then Nov 3–9 brought $790,760 in gross fees. 85% of the ENTIRE October in seven days, wif capital walking out.
Thats real people using the damn product.
Open an xPOSITION, pay a fee. Close it in profit, still pay a fee. Treasury captures its share, and 75% of that goes to veFXN. Yieldtern doesn't need the trader's liquidation to get paid. He wants the guy back next week.
And here's the longer bet. Leverage is already getting used. fxUSD, fxSAVE and fxMINT give the same ecosystem more ways to serve users. Not every product has to turn into a monster. Wtf happens if even a couple of them do?
Yieldtern wants a piece of the business people keep coming back to. Not some predatory crap that needs another degen dead to fund the yield.
If ur business model needs the customer to lose, keep it. Yieldtern doesn't want to own that shit.
I challenge that statement groksy.
Frontier model subsidies is over, and price will remain higher.
The other side, the midle and lower end models is going to be free, or near free..
Infact, its already like that…
Providers Are offering free endpoints all around the place, and promo campaigns with hundreds of millions tokens each day/week.
I will extend it further, majority of the tasks users need done, can and will be covered 80% or more of the free/near free models.
I already built such system routing, and can run agent swarms/teams free.
Kimi, glm, deepseek, all free but slow.
So route/build around that and u have an autonomous agentswarm, 100% free of token tax.
That enables unlimited experimenting..
My thinking, frontier will be what u talk to, that converts that conversation, to tasks for a Multi agent/worker system triaging that conversation to various intents/wants/outcomes and loops til users want is covered.
Humans shouldnt need to know about routing,models, or any of that stuff.
Our job?
Paint the fuggin dream u want..
I have a weekly Codex quota.
Just let me fucking use it.
Why is there a 5 hour babysitter sitting on top of it?
Yesterday I still had more than 50% of my weekly quota left.
Didn't matter.
The 5h window was the actual bottleneck.
And I had a full reset expiring, so I ended up using the reset before it disappeared.
That sounds like free compute.
It isn't always.
A full Codex reset also resets the weekly window and moves your next weekly reset date.
So if I still had quota left that I was planning to burn later in the week, that remaining capacity does not stack.
New week starts.
Old schedule is gone.
I have literally had these “gifts” reduce how much Codex I could use over the period compared to if OpenAI had just left my quota alone.
Around 15-30% in some cases from my own tracking.
Because I don't use compute evenly.
Of course I don't.
Some days I barely touch Codex.
Then I hit a build, research or debugging run where I want to absolutely cook it for 10 hours.
That is what a weekly quota is perfect for.
Give me X compute for the week.
I decide when the fuck I need it.
Instead Plus gets a weekly budget with a smaller timer sitting inside it telling me how quickly I'm allowed to spend my own allowance.
And apparently this isn't some fundamental safety requirement.
Pro 100, 200 and 500 don't have the 5 hour Codex limit.
So what exactly are we doing here?
Is the assumption that a Plus user can't be trusted to manage a weekly quota?
Because I can.
I am actively managing it already.
Yesterday I was trying to burn compute I did not need yet because a reset was about to expire.
Today I want to burn hard and the 5h limit matters more than the weekly quota again.
This creates completely backwards incentives.
Save quota for a hard workday?
You may not be allowed to spend it fast enough.
Get a promotional reset?
Better calculate whether using your “free” reset destroys quota you were already planning to use.
Get a global reset at the wrong point in your cycle?
Congrats, your reset calendar moved.
I don't want more babysitting tools for this.
I want one number.
You have this much Codex compute left.
Reset on this date.
Go nuts.
When it is gone, it is gone.
That I understand perfectly fine.
If Pro users can manage their compute without a 5h leash, let Plus users do the same.
I paid for a bucket.
Stop telling me how fast I am allowed to drink from it.
@thsottiaux
I want to tell AI what I want done.
I do not want to learn why request #83 got a 429.
Yet somehow we are normalizing this.
429 means one thing.
403 means something else.
504 might mean the model did the work and the transport died afterwards.
A reply can stop because it ran out of output tokens.
Another can hit an iteration ceiling with the final answer already sitting there.
Same experience for the user.
AI broke.
We went through 17 terminal failures inside YieldBrain recently.
Not one was the model failing to think.
5 were tool or harness failures, 4 rate limits or quota, 4 transport, 2 output budget, 1 auth and 1 insufficient evidence.
Zero semantic model failures.
That is insane to me.
Not because plumbing fails. Of course it fails.
Because we still expect the user to know what kind of plumbing failed.
Take a 429.
One NIM model can be unavailable while another NIM route is fine. We built the fanout so one model hitting 429 does not block the others.
If I see that failure, I know not to declare NIM dead.
Why the fuck should the user know that?
Same wif retries.
Some failures should back off.
Some should reroute.
A retired model route should not be retried at all.
We even found an 83 character harness error in the database that could be counted as an answer.
Imagine asking AI to do something and the system quietly records “yep, replied” because an error stub exists in the reply field.
kek.
This weekend made the problem painfully obvious in our own system.
On Friday I said publicly that we would release the first open source part of YieldBrain this weekend.
The kernel.
We did not.
It is still not publicly released.
The Director got the goal on Friday and kept working on it through the weekend.
The brief told it not to bulldoze through failures just to satisfy the release goal.
If something useful was repairing itself, leave it running.
If a provider looked dead, verify it.
If a harness broke, repair that lane first.
And public actions still belonged to me.
So the release kept uncovering work.
Fix one thing, verify it, then find the next thing behind it.
That does not fit neatly inside “this weekend.”
I was the one who said this weekend anyway.
The machine had a goal.
I made the promise.
By Sunday the kernel source had been promoted into our canonical internal control, but public release was still disabled.
There were still decisions around licensing, the namespace and the sanitized public export.
Those are human decisions.
So it stopped there.
Which is actually what I asked the system to do.
This is not the part where I claim our AI fixed itself and everything worked perfectly.
It didn't.
YieldBrain still works too often because I know what the fuck I am looking at.
I know that a 429 on one route is not automatically a dead provider.
I know why a 410 after that changes the diagnosis completely.
I know an output limit is not a network failure.
I know when the thing claiming to be an answer is actually garbage from the harness.
Of course I know.
I built the thing.
The user didn't.
That is the bug.
I don't want to build a better cockpit and teach everyone to become a pilot.
Fuck that.
The user should be able to say what they want done.
Then the system should deal with as much of the ugly shit underneath as it can.
If one route dies, it should know what that means before bothering the user.
If work can continue somewhere else, continue.
If the evidence is garbage, don't pretend the job succeeded.
And when it reaches something that actually needs the human, stop.
That is much closer to what I mean by “just works.”
A hosted coding subscription can own more of this plumbing because it controls more of the stack.
YieldBrain is different. It coordinates models, tools and compute the user already legitimately has access to.
So right now we see more seams.
I want fewer of them.
Not by pretending the machinery isn't there.
By making the system understand enough of its own machinery that the user doesn't have to.
That is also why putting the kernel out publicly matters to me.
As long as this thing only works in my setup, with me standing next to it knowing where all the weird bodies are buried, we have not proven the thing I actually care about.
Can the knowledge leave my head?
Can someone express a goal without first learning our little religion of queues, routes, retries and provider weirdness?
Not yet.
That is the honest answer.
There are roughly three hours left in the weekend while I write this.
Maybe the kernel goes public tonight. Maybe it doesn't.
I am not making another promise.
But the attempt already found the thing I wanted the release to test.
Too much of YieldBrain still works because its architect knows how YieldBrain works.
The user has better shit to do.
Ohh my…
The nerfing of the chat mode in ChatGPT is real…
I used to be able to work for days, even weeks in the same chat.
Now it reaches Max lenght in a day.
Are we compute restrained much @thsottiaux /@sama ??
Wtf is going on?