ASPERN · due-diligence report
Concrete · CTQIROUSD1
Concrete · ethereum · concrete-ctqirousd1-655567
Generated 2026-10-29 10:22:18 UTC. Every figure below carries the moment it was read, because a report is read later than it is made. Nothing here is a recommendation to invest. The live page carries the same readings and moves with them.
What it holds
How you get out
The contract imposes NO notice period: a redeem settles in the transaction that asks for it. That is not a promise of an instant exit — it is still subject to the vault having the money, which is the liquidity reading and a separate question — but there is no queue, no request step and no lock-up in the contract.
No share of this vault has been destroyed in the window we scanned, which is what a holder leaving looks like here. That is a reading of the chain and not of our flow register, and it means nobody left rather than that we did not look.
Six risks, read separately
This is the 66th different vault read from here today, and the allowance at this level is 50. Past that a caller is not checking a vault any more, they are reading the population, and the population is the product: the risk screen covers every vault at once, filtered and sorted and compared. Nothing is slowed down and nothing else on this answer is withheld. Vaults already read today stay open whatever the count, because coming back to a vault you are considering is exactly what this allowance is for.
What it advertised and what it returned
The published ratio divides the realised rate by the rate this vault quotes TODAY. Over 40 of the 74 days the return covers we hold its own quotes, it advertised between 0.00% and 1522.42%, averaging 38.06%, and today's quote is near the BOTTOM of that range, so the published ratio flatters the delivery. We hold no quote for the rest of the window, so this says what the venue was advertising while we watched and not across the whole return.
This vault deploys into one contract on ethereum, 0xf2c5d20b4e7d3f3f5fa91e833042661d8f252c7b. This contract does not derive what it is worth from what it holds: a multisig at 0x796c0fe8f8487a8c6b37ba58aae6e10ab0e89fec POSTS the figure, with the last posting on 2026-10-28. one posting may move it by at most 50 of the contract’s own units, and a posting goes stale after 7 days. Those are limits on the POSTING and not checks on the number: nothing in this contract sets it against anything the chain can confirm. So a flat unit price upstream is not evidence that nothing was earned, and a moving one would not be evidence that anything was. It is the reported book value of a strategy whose holdings we cannot see, and whoever holds that key decides it. The last posting is still inside that period.
Who controls it, and whether that has changed
We have watched who controls this vault since 2026-09-13 and nothing we record has moved in that window. That is not the same as a vault that has never changed hands: anything before 2026-09-13 predates this platform holding control state at all, and we do not reconstruct it from history.
What we cannot see
- · A single step on 2026-10-19 accounts for 95% of the movement behind this figure, so it is not a rate that repeats.
- · The realised return is not comparable with the advertised one (venue-quotes-nothing), so the ratio is not a verdict on the venue's figure.
- · The risk band rests on 76% of its components; the rest could not be measured for this vault.
- · Whether it still takes deposits is not something we could establish.
- · Whether a timelock exists elsewhere: we read the controller and it is not one, and we do not separately search for a timelock behind it.