Vetro (VUSD)

Vetro receives an adverse research assessment. Vetro issues VUSD and vetBTC against reserves of approved assets and pays yield through separate staked wrappers. Two facts decide the judgment. A Keeper can pause deposits and withdrawals for a specific asset, so the exit depends on a switch held by an operator rather than on the contract itself. The public documentation available on 2026-09-15 also did not disclose the reserve composition, the identity of the Owner and Keeper keys, or the redemption timing. At that date, the protocol was eighteen days old with roughly $508k on-chain, so it had no operating record to make up for the missing disclosure. Size is not the reason, and we do not treat it as one. An undisclosed reserve behind a pegged dollar whose withdrawals an operator can switch off would fail at any size.

Review triggers: events that reopen the verdict
• Vetro publishes the VUSD reserve composition with independent attestation, and names the Owner and Keeper key holders and signing thresholds
• The per-asset deposit and withdrawal pause is removed, timelocked, or placed behind a disclosed governance process with a published redemption service time
• A Keeper pauses withdrawals on a live asset, or VUSD sustains a material deviation from one dollar

Watched nightly: a warning on its venues or files, or a cited document that changes, reopens the memo. The first confirmation is due 2026-12-15.

The research file

The mechanism

Vetro issues pegged assets against reserves held in what the documentation calls isolated Treasury Vaults. VUSD is presented as a settlement-grade dollar targeting one-to-one redemption and described as fully reserved by design, with on-chain proof of reserves. vetBTC and vetETH are settlement-grade representations of BTC and ETH: users swap in approved denominated assets and receive the vet token. Yield is deliberately separated from the settlement asset and delivered through opt-in wrappers, sVUSD and VUSDx for the dollar and svetBTC for bitcoin, so a holder of plain VUSD is not the one earning the return.

Who controls it

The contracts use an Owner and Keeper model. The Owner whitelists new assets, sets fees and appoints Keepers. Keepers move funds between the Treasury and yield vaults and can pause deposits and withdrawals for specific assets. That last power is the decisive control fact: a holder relying on one-to-one redemption depends on a Keeper key not exercising a pause it is documented to hold. Each new asset vertical additionally requires a veVETRO governance vote before activation, so admission is a token-holder decision. The documentation reachable on 2026-09-15 did not name who holds the Owner or Keeper keys, did not state whether the contracts are upgradeable, and did not publish the reserve composition behind VUSD.

The record

DefiLlama listed Vetro on 2026-08-28 and reported approximately $508k on an Ethereum-only perimeter on 2026-09-15, of which about $67k sat in pools carrying a published yield. That is eighteen days of public operating history. An audit dated February 2026 is published in the protocol audit repository, reported with 287 tests and 96.08 percent line coverage. No incident is disclosed and none was found in the search performed on 2026-09-15 across the protocol documentation, the contracts wiki and general web sources, which at eighteen days establishes nothing about behaviour under stress.

The exit

The stated exit is one-to-one redemption of VUSD against the reserve, and swap-out from the Treasury Vaults for the vet assets. Both run through vaults whose swap-out toggle a Keeper controls per asset, and neither the servicing timing nor any queue was documented. The secondary exit is selling into market depth, and at roughly $508k of protocol assets across a token that also advertises a target of more than a hundred networks, usable depth on any single venue should be assumed very thin. A holder cannot currently demonstrate either exit path to a client.

The comparison

A client who wants a redeemable dollar can hold a researched cash instrument where the obligor is named and the reserve is attested, which is the status quo this record is measured against. Within the pegged-asset family, the registry already rejects better-disclosed issuers on control and eligibility grounds, and Vetro discloses less than those while adding an operator-held withdrawal pause. The separation of settlement from yield is a sound design choice and is recorded as such, but it does not answer who holds the reserve or who can stop a redemption.

Open questions

What exactly backs VUSD and in what proportions; who holds the Owner and Keeper keys and under what signing threshold; whether the core contracts are upgradeable and by whom; what the redemption servicing time is and whether any queue exists; which oracles feed the redundant oracle mapping and who can change them; and whether the February 2026 audit scope covered the pause and treasury-transfer powers. None were answerable from public documentation on 2026-09-15.

Sources

The claims above trace to these. Where a number could not be independently verified, the thesis says so.

• Vetro — protocol documentation · primary · accessed 2026-09-15
  Supports: VUSD settlement asset, sVUSD and VUSDx yield layers, separation of settlement and yield, multi-network target
• Vetro — vetBTC and vetETH · primary · accessed 2026-09-15
  Supports: swap in approved assets, isolated Treasury Vaults, swap-in and swap-out toggles, veVETRO vote before activation, redundant oracle mapping
• Vetro contracts — Owner and Keeper model · secondary · accessed 2026-09-15
  Supports: Owner whitelists assets and sets fees, Owner appoints Keepers, Keepers move treasury funds, Keepers pause deposits and withdrawals
• Vetro — VUSD audit report · primary · accessed 2026-09-15
  Supports: February 2026 audit, test count, line coverage
• DefiLlama — Vetro record · secondary · accessed 2026-09-15
  Supports: current TVL, Ethereum perimeter, CDP category, listing date 2026-08-28

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.