Makina
Makina is an execution engine on Ethereum that operators use to run on-chain yield strategies. The DefiLlama API read on 2026-08-15 showed about $44.2M TVL, below the size floor. We do not open the individual review until it clears that floor, and we reject it on size. One practice advising 100 households moves $1M to $8M into a venue based on the same research, and at that size the book becomes the exit crush, whatever the protocol’s quality.
- TVL sustained above the retired TVL threshold for 30 days
Watched nightly: a warning on its venues or files, or a cited document that changes, reopens the memo. The first confirmation is due 2026-11-15.
The research file
Mechanism applicability
Makina strategies issue Machine shares while an Operator allocates capital through Hub and optional cross-chain Spoke Calibers. Positions can include lending supplies, DEX LPs, yield vaults, and debt. The Operator may open, resize, close, harvest, or bridge them through pre-approved instructions. This shows that Makina is a live, actively managed vault venue covered by the below-materiality dossier. It does not amount to an individual endorsement of any Machine.
Current observation and evidence boundary
The DefiLlama protocol API read on 2026-08-15 reported approximately $44.2M of tracked Makina TVL on Ethereum, below the v1 dossier’s size floor. We do not open the individual review until the protocol clears that floor. Makina documents separate roles for governance, the Security Council, the Operator, the Risk Manager, and guardians, as well as a ChainSecurity assessment. This review does not match every deployed Machine, role address, instruction root, audit finding, incident, or underlying venue. We have not yet reviewed those items.
Accounting and exit applicability
Makina calculates share value from idle assets, Hub and Spoke positions, and bridges in progress, with settings that limit data age and rates of change. It does not promise an immediate withdrawal. A user may enter a FIFO redemption queue while the Operator closes positions and returns liquidity to the Hub. Third-party liquidity, bridge timing, stale valuations, and operator action can therefore delay settlement. In recovery mode, the Security Council gains powers to unwind positions.
Why the shared dossier decides
The v1 below-materiality dossier rejects Makina before we review an individual Machine because a client allocation could make up a material share of the current venue or a smaller strategy. Reopen only after the same survey perimeter shows at least the size floor for 30 straight days. The reopened review must cover each Machine’s mandate, live positions and debt, roles, instruction limits, accounting, audits and incidents, reachable chains, security-module coverage, and exits from the queue under stress. Clearing the floor would not mean approval.
Research status
This is a capacity-unproven record for Makina, not a quality rejection or approval. Reported TVL says how big the venue is, not what the client owns, who can change the rules, or how a position exits at a proposed size. The individual review opens when the protocol clears the size floor.
Sources
The claims above trace to these. Where a number could not be independently verified, the thesis says so.
- Makina Docs — asset lifecycle · primary · accessed 2026-08-15
Supports: Machine shares, operator allocation, Hub and Spokes, withdrawal buffer, FIFO redemptions, recovery mode - Makina Docs — trust model and roles · primary · accessed 2026-08-15
Supports: governance multisig, Operator limits, Risk Manager, Security Council, accounting agents - Makina Docs — share price and AUM · primary · accessed 2026-08-15
Supports: AUM composition, cross-chain accounting, staleness controls, share-price guard - ChainSecurity — Makina Core assessment · secondary · accessed 2026-08-15
Supports: core assessment, redemption delay, operator dependency, third-party liquidity, accounting risk - DefiLlama — Makina survey record, read 2026-08-15 · secondary · accessed 2026-08-15
Supports: current TVL, Ethereum, allocator category, survey perimeter
Inherited controls
The research above describes the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The layer with the most administrative power sets the position’s effective control; that describes control, not quality or suitability.
| Chain | Verdict | Control | Control constraint |
|---|---|---|---|
| Ethereum | Approved | No freeze key | No sequencer, no upgrade key, no operator who can be compelled. Rule changes require social consensus. |