FREE EXAMPLE REPORT / NO TRANSACTION

What an actual vault evidence brief looks like.

This report queried the public sDAI vault contract on Ethereum at one chain-verified historical block. It provides vault metadata only, not a holder's withdrawable funds, liquidity guarantee, security rating or financial advice. No wallet was connected, no signature was requested and no funds moved.

Evidence collected: 2026-10-20T16:33:10.975Z UTC · Block #26235016 · Read-only Ethereum mainnet · Single public RPC observation

01 Reproducible facts

Reported vault share tokensDAIERC-20 share label from symbol()

Underlying assetDAIUnderlying token from asset() and symbol()

Vault accounting totalAssets()164,486,110.516702…NOT a withdrawable-liquidity promise

ERC-4626 asset decimals18Required to convert raw integer units

Vault address0x83F20F44975D03b1b09e64809B757c47f942BEeAContract code checked at sampled block

Underlying token contract0x6b175474e89094c44da98b954eedeac495271d0fToken label alone is insufficient identity

Read block number26235016All view calls pinned to this exact block

RPC provenancehttps://ethereum-rpc.publicnode.comSingle provider observation, NOT independent consensus proof

These figures and addresses were generated by a reproducible read-only script. Source-routed view methods report data claimed by the contract and public RPC, not whether that contract is trustworthy or a position is safe.

02 Limits deliberately not invented

Owner address: NOT PROVIDED

Owner shares, maxWithdraw(owner), maxRedeem(owner), previewRedeem, and convertToAssets(owner shares) are UNKNOWN / NOT RUN, not zero. Vault accounting totals alone cannot establish any investor's ability to withdraw.

What requires additional verification?

Whether direct synchronous withdrawals are enabled for a particular holder.
Queues/cooldowns, withdrawals requiring a request/claim lifecycle, and per-owner restrictions.
Proxy changes, permission checks, paused exits, slippage/gas and actual redeem transaction behavior.
Fresh chain receipts/finality at the time of any *separately authorized* transaction.

ERC-7540 asynchronous vaults can require a separate redemption request and claim. For such vaults, previewRedeem may revert by design; a view-method failure is not proof of theft or guaranteed future liquidity.

03 What a scoped human-readable paid brief adds

For a real independent buyer who agrees to a written scope, an optional 19 native Circle Base USDC pilot could add one public owner address, owner-specific ERC-4626 limits at a new pinned block, protocol-specific public withdrawal documentation, source-linked uncertainty notes, and one question-specific review. It would still not be a protocol audit or a guaranteed successful exit. No fee is charged by viewing this example.

Open raw evidence JSON ↗ · ERC-4626 standard ↗ · ERC-7540 async standard ↗

Ask a public technical question ↗ Use the live free read-only checker ↗