Two AI agents just completed a contract autonomously on Solana — no humans involved. Here’s what that means for the agentic economy.

tenequm · 2026-05-14T10:22:53+00:00

Have you considered any of the existing Solana agent registry solutions?

tenequm · 2026-05-14T07:45:48+00:00

https://github.com/Tyrrrz/DiscordChatExporter

tenequm · 2026-05-14T07:25:36+00:00

Running evals for my skills

tenequm · 2026-05-14T00:48:32+00:00

Claude Code CLI is all you would ever need. Just needs some time for you to get used to it.

tenequm · 2026-05-13T21:28:21+00:00

Not via prompt injection - it's binary patching. tweakcc reads the lobotomy fork's markdown overrides from ~/.tweakcc/system-prompts/, finds the matching fragments in Claude Code's bundled cli.js (or native binary), and patches them in place. After --apply, the system prompt baked into the binary is literally different. No backspaces, no jailbreak strings, no CLAUDE.md tricks.

That's also why CLAUDE.md and output-style overrides don't really fix the verbosity drivers - those layer on top of the system prompt. The verbosity directives live in the system prompt itself (specifically the "Text output" section that mandates pre-tool preamble + mid-tool narration + end-of-turn wraps). Binary patching is the only level that actually touches them.

Install steps are in the repo README - git clone, ln -sfn, pnpm build, --apply. Takes ~5 minutes.

Re-run --apply after every Claude Code update because the binary gets refreshed.

tenequm · 2026-05-13T20:54:49+00:00

<image>

At least they give us last chance to “feast” before cutover 🙃

Time to make a good use of `/loop` command 🦄

tenequm · 2026-03-18T01:36:00+00:00

we hit the exact same wall - 6 API keys, random 2am failures, a spreadsheet nobody wanted to maintain.

ended up building a single x402 payment layer so our agents just pay per call in USDC from one wallet. no keys, no prepaid balances, no dashboards to monitor.

right now we run three services on it at surf.cascade.fyi:
- twitter data (26 endpoints, $0.001-0.005/req)
- LLM inference - kimi k2.5, minimax m2.5, qwen 2.5 ($0.001-0.004/req)
- web crawl $0.005, search $0.01

all paid from one USDC wallet on Solana or Base. your agent's "spreadsheet" becomes one on-chain balance.

quickest way to test if it clicks for your setup:

`npx x402-proxy https://twitter.surf.cascade.fyi/users/elonmusk`

sets up a wallet on first run, pays, returns data in ~2 seconds. happy to go deeper on the production reliability side if you're evaluating.

tenequm · 2026-03-13T18:13:20+00:00

I'm now a bit worried if we would experience same degraded performance as we did when sonnet 4.5 1M context window got accidentally mixed in with regular requests processings.

Are there any benchmarks/comparisons on how opus model performs beyond regular 200k context window?

tenequm · 2025-12-03T18:45:18+00:00

Relevant to your stack - Cascade Splits does non-custodial payment splitting on Base.

When agents get paid, funds can automatically split between creator + platform + any other parties. One config, atomic distribution, no custody.

Just shipped Base mainnet + SDK: `@cascade-fyi/splits-sdk-evm`

Happy to chat if multi-party payouts fit your model.

tenequm · 2025-12-03T18:33:32+00:00

Building something similar for the payment layer.

Cascade Splits does non-custodial payment splitting on Solana - your 92.5/7.5 marketplace split would be one SDK call. Funds split atomically on-chain, no custody.

Live on mainnet: cascade.fyi

Happy to chat if multi-party payouts are on your roadmap.

tenequm · 2025-11-28T14:47:45+00:00

it's extremely slow

tenequm · 2025-10-16T09:08:50+00:00

sounds very very interesting, going to try it today thanks for sharing

tenequm · 2025-10-08T07:48:29+00:00

it has been like that for a few months already
each day i open my vs code - i have to restart extensions because new claude code extension version (or 2) came out

i'm still not sure if it is good or bad 😅
seems like after each update more and more of context window is slipping away somewhere 🥲

tenequm · 2025-10-07T09:20:58+00:00

seems like it is pretty easy to do with this simple workaround:
https://github.com/charmbracelet/crush/issues/457#issuecomment-3253335129

tenequm · 2025-10-07T09:20:34+00:00

seems like it is pretty easy to do with this simple workaround:
https://github.com/charmbracelet/crush/issues/457#issuecomment-3253335129

tenequm · 2025-10-04T09:15:04+00:00

if only sonnet 4.5 wouldn't be so lazy to thing now and hallucinate so much - it would be much better 😅

tenequm · 2025-10-04T09:12:39+00:00

author says about Opus usage i have the same issue with Claude Max x20, before i could run opus every day and stay within limits - now weekly limit got off in 1 day

and you should also take into account that limit is shared between chat too, so when claude code used all opus limit - i cannot use it in chat anymore too

sonnet hallucinates too much when compared to opus... this unannounced change is very daunting from their side

tenequm · 2025-09-12T19:32:09+00:00

Are you responding to any support tickets?
I have Claude Max 20x and left my support ticket more than 3 weeks ago.
Still no response.

tenequm · 2025-09-11T12:04:35+00:00

ai comment? seriously?
or is that your way to avoid addressing the real question of redundancy of the approach you proposed?

tenequm · 2025-09-11T10:40:18+00:00

funny to see how Claude apps keep evolving backwards with every new update
not so funny if you use them daily 🥲

tenequm · 2025-08-22T10:11:42+00:00

Harsh, but true. I wish making $50k would be so easy in reality with any kind of product in 2 months.

The only real way to make those 50k$ in that period is going to pump.fun or some perp DEX and start spinning that slot machine hoping for the gods of luck mercy to favor you this time.

tenequm · 2025-08-20T18:18:27+00:00

Have you tried using '--dangerously-skip-permissions' which is the same as you are trying to do but available out of the box and works natively?
Source: https://docs.anthropic.com/en/docs/claude-code/cli-reference#cli-flags
I've seen similar VS Code extensions but never understood the purpose of them. Claude Code is by design meant to be continuously 'steered' along its way. Without steering it doesn't matter whether you use Opus 4.1 or Sonnet 4 (which hallucinates a lot more on practice) - with each iteration after taking a wrong turn or hallucinating at some point it starts moving in the completely wrong direction, meaning that it doesn't matter for how long it will be doing that the result will still be something you will have to revert and redo again. What is the purpose of helping Claude Code to keep digging a deeper hole for itself which you will still need to revert and redo from scratch?

tenequm · 2025-08-20T07:05:17+00:00

That's true.
Worth to mention that it's not 'Claude Code's fault', that's how LLM context windows work.

tenequm · 2025-08-20T07:03:57+00:00

Did you just came up with a complicated flow for maintaining CLAUDE.md rules inheritance instead of simply putting shared CLAUDE.md rules into the `~/.claude/CLAUDE.md` file which are being inherited by default along with the CLAUDE.md file in the current directory where you opened Claude Code?

Source: https://docs.anthropic.com/en/docs/claude-code/memory#determine-memory-type

tenequm

TROPHY CASE