Sergiu

I measure the gap between what a market reports and what it can support. Paid agent data over x402 on Solana, Base, Algorand. Risk monitors on 6 more chains.

[Sergiu @ochinimus]

On Canton an auditor only sees the contracts they're a stakeholder on. A withheld event and one that never happened look identical to them.

visum turns that blind spot into a number: a signed on-ledger coverage ratio showing how much of a workflow the auditor actually saw. 9,760 test runs, 0 mismatches.

Built solo for @appsfactory_cc . The daily diary and mentor questions kept me honest about what's proven and what isn't.

Live demo: https://t.co/uCjX4nwbdM
Code: https://t.co/av917SA5CU

[Sergiu @ochinimus]

Launched nimus on @MeteoraAG from my @solanamobile today.

You back it on a schedule: pick an SKR amount, daily or weekly, approve once. Each period one transaction buys nimus into your wallet. Capped onchain by Solana Subscriptions, revocable any time.

https://t.co/iCULSMZJrS

[Sergiu @ochinimus]

It is a clever structure and worth building. Fix the pricing story, the order flow and the keys before mainnet, and show this week's strike and the upside at stake on every borrow. Full review, code, data and screenshots: https://t.co/YExMobtFma

[Sergiu @ochinimus]

One single-signer key can upgrade both programs, freeze the stock tokens and mark wallets as verified. It is a hot key: it verified my brand-new wallet on its own, before the wallet had sent a single transaction. Fine on devnet. Not on mainnet.

[Sergiu @ochinimus]

A paid x402 call settles whenever the server answers 200, even if the answer is a zero it made up.

AgentFeed on Algorand returns 503 when its own lookup fails, so the payment never settles. Proven on mainnet in the demo.

@AlgoFoundation @GoPlausible

[Sergiu @ochinimus]

cassum is deployed. https://t.co/DHgB61sIAR

Two buttons. One runs the deletion test on the server right then, the same workload with Sibyl Memory and again against a store that returns nothing on every read. 24 paid calls against 80, for the same 20 delivered payloads.

The other spawns two real processes. The first learns and writes to disk. The second has a different pid, cannot buy, and still names the right provider.

Nothing on that page is precomputed. @sibylcap

[Sergiu @ochinimus]

Second one, same family.

solana program extend and deploy's auto-extend both send ExtendProgramChecked. Cookie Chain's loader rejects it, so the upgrade fails in preflight with invalid instruction data and no state change.

The legacy ExtendProgram works. Deploy with --no-auto-extend after.

[Sergiu @ochinimus]

One thing for anyone else building here.

anchor-cli 1.2.0 emits an SBPFv3 binary by default. Cookie Chain has not activated that feature, so the deploy fails after writing a buffer and it reads like a chain fault.

anchor build --arch v0

That is the fix.

[Sergiu @ochinimus]

Needs COOK on Cookie Chain. Bridge from Solana here:

https://t.co/LTD3UuLS00

Program 5HV3pKAZ3RTbeJnszGB1iQXZUX2dgtwGmms3imPsoE94
Code https://t.co/EMRgfiXvzP

Built for the @TheCookieChain cApp bounty.

[Sergiu @ochinimus]

Building a buyer that remembers its purchases found a bug in my own API.

One paid endpoint had been unbuyable since the day it shipped. It issued a correct 402. It appeared in the manifest at the right price. curl looked fine. Every check I had said healthy.

The Coinbase CDP facilitator was rejecting the payment payload with a 400 and no server-side log anywhere. Cause was the resource description length. I bisected it on the live service: 487 characters settles, 515 does not.

The description was 683 characters. It was the most thorough one I had written.

Nothing but an actual signed payment could have found this. Not a health check, not a manifest read, not reading my own source. You have to spend money to learn that you cannot take it.

Fixed by truncating in the payment challenge only. The full text still renders everywhere a human reads it.

@sibylcap