runesleo

Once Bitcoin layer assets become more complex,
the first problem ordinary users encounter is:
Who is the actual balance based on?
I've come across this issue on Alkanes these days.
For the same address,
the balances and statuses seen on Subfrost, ESPO, UniSat, and idclub
may all be different.
Some look like they have been spent.
Some look like they have been reverted.
Some balances update very late.
I broke down a transaction on Alkanes
by txid / block / outpoint,
and realized that fundamentally, it's the same set of UTXOs
interpreted differently by different systems.

The quota display for Codex is a bit interesting.
It shows that this week's quota is already at 0%,
but the current conversation can still continue to work.
Let's not jump to conclusions; it could be several mechanisms stacking together:
The short-term window quota is still active,
the current session has a grace period,
local tool calls don't fully consume the same pool,
UI percentage may be rounded or delayed,
the remote host status is still maintained.
These kinds of details are quite similar to the real complexity of an Agent product:
Users see a chat box,
but behind

Since I started remotely connecting to my Mac with the Codex App on my phone recently, the user experience has been getting better and better.
As a result, whether I'm working lying in bed or coding outdoors while out and about, my phone battery drains rapidly.

Many people get stuck when working with AI, not because they write prompts poorly.
It's because the same conversation gets more and more bloated over time, eventually turning into a garbage dump of context.
I’ve now added an "auto shell change reminder" to my Codex workspace.
I have 10 pinned workspaces every day:
Content, research, strategy, product, daily wrap-up...
/morning, /next, session-end tasks are all stored there.
The problem is, after using it for a while, each thread's historical baggage gets heavier and heavier.
Tokens keep piling up,
Old tasks, new tasks, wrap-up

I manually created a shell change reminder for the Codex pinned thread.
I use threads like Daily Rhythm every day:
/morning, /next, session-end, today-end all get filled in there.
As a result, the tokens keep accumulating and growing thicker.
Today, I let automation directly monitor tokens_used:
If it exceeds 50M
→ Automatically scan pinned threads
→ Daily Rhythm rolls over itself
→ Create a new clean pinned thread
→ Write back registry / state / backup / latest
Other threads only report candidates.
For example, strategy, portfolio, product, I still want to make the call

The new X salary has been credited, $96.17.
Compared to the previous pay period:
Last period $105.64
This period $96.17
Less by $9.47, approximately -9%
Breaking it down:
Impressions: 461k → 445k (-3.4%)
CPM: $2.29 per 10,000 → $2.16 per 10,000 (-5.8%)
For everyone's reference

"The State Council's Regulations on Outbound Investment" is trending today.
I think the biggest reminder for ordinary people is:
Asset allocation should consider both the target and the channel.
Are you buying US stocks, AI beta, overseas assets, or just a channel that depends on brokers, deposits and withdrawals, identity, and policy windows?
Part of BTC's long-term value comes from here.
It is both a price asset and a hedge against channel risks.

I hope OpenAI doesn't overlook me.
I just applied for Codex for Open Source.
This program is pretty intense:
Providing key open source maintainers
6 months of ChatGPT Pro + Codex,
Plus API quotas and conditional access to Codex Security.
What I like most is:
OpenAI finally treats "maintaining open source"
as a real form of labor.
Reviewing PRs.
Splitting issues.
Fixing security problems.
Releasing versions.
Updating documentation.
Writing automation.
Handling a bunch of corner cases no one wants to touch.
These tasks are usually the easiest to get free labor for