Xobak
Journal

Operating notes, including the bad weeks.

What the vaults did, what the guards blocked, and what the published research actually supports. No launch announcements dressed up as analysis.

Operations

The week the TWAP guard earned its keep

15 blocked actions are now in the ledger. Here is what each of them was refusing to do.

A price guard is a cost until the day it isn't. Ours fired repeatedly this week during a thin overnight window when the GME pool printed a spike that the 30-minute reference did not corroborate. Each time, the rebalance aborted rather than resetting the range around a price that reverted within minutes.

The forgone fees from those missed resets are real and small. The alternative — placing a fresh range around a spike and holding it as the pool snapped back — is how a managed position converts a temporary dislocation into a permanent loss. We would rather publish the refusals and explain them.

Every blocked action carries its deviation figure in the detail column, so the trade-off is auditable rather than asserted.

Strategy

Why GME runs a range nearly twice as wide as NVDA

Per-asset sizing, shown with the actual widths rather than described in the abstract.

Realized volatility on GME sits near 91% against 48% for NVDA. Running the same width on both would put the GME position out of range on ordinary days and leave the NVDA position earning far less than it could on quiet ones.

Wider is not free: it earns less per dollar deployed while in range. The exchange we accept is a lower headline rate for materially more time spent earning it — currently 92.2% of the trailing month for GME, against 98.2% for NVDA.

This is the whole argument for per-asset vaults compressed into two numbers. A generic manager cannot make that trade because it does not know which asset it is holding.

Launch

Third vault live, and why the deposit cap did not move

$2.00M per vault stays where it is until there is enough operating history to justify raising it.

The third market opened this week. The cap did not change, and will not change on the basis of demand — only on the basis of recorded behaviour through a volatility event the strategy has not yet seen.

Caps are unpopular because they turn away deposits. They are also the only honest mechanism a young strategy has for limiting how much capital is exposed to a model that has not been stress-tested. Raising one because the queue is long is how a strategy becomes a story about a strategy.

Research

Reading the LP profitability studies properly

51% unprofitable is the number everyone quotes. The more useful finding is the one nobody does.

The widely cited result is that a majority of Uniswap v3 liquidity providers lost money once impermanent loss was netted against fees, with $-260,100,000 of IL against $199,300,000 of fee income across the studied cohort.

The finding that actually shapes product design is quieter: an academic analysis found no statistical evidence that providers who repositioned more frequently performed better. If effort were the missing input, the most active wallets would separate from the pack. They did not.

That is why this protocol is not a dashboard with better tick controls. Better controls hand the same losing decision back to the user with a nicer interface around it.

Launch

First vault open on USDG

What we are starting with, what we are deliberately not doing, and how to check our work.

One market, capped deposits, and a public ledger of every action from the first block. No emissions, no points, no lock-up — the yield is swap fees or it is nothing.

USDG is the quote asset because it is the chain's settlement dollar and holds the large majority of stablecoin supply here; routing through anything else would fragment the liquidity we are trying to deepen.

Verification is the point of the transparency feed. Vault and zap addresses are listed in the registry, every action links to Blockscout, and the range readout shows in real time whether the position is earning or sitting idle in one asset.

Note

These entries describe the simulated operating history rendered elsewhere on this site. The research findings they reference are real and sourced in the protocol documentation.