Search projects, hackathons, sponsors and tech

    ← All projects

    Tare-Vault

    Tare traces DeFi vault positions, checks evidence, and explains what remains unverified.

    Demo

    About

    NOTE: The demo works when https://tare.visk404.dev/ is pasted directly into the browser’s address bar, but clicking an external link can trigger the origin error. What is behind my vault balance, how can I check it, and what should I investigate next? Tare is an evidence-first DeFi investigation tool for depositors, treasury reviewers and AI agents. A vault balance can hide several layers of allocations and shared lending dependencies. An accounting quote can also look reassuring without establishing custody, liquidity or full backing. Starting with a public wallet address, Tare discovers supported positions across Ethereum, Base and Arbitrum. Explorer examines one wallet–vault position, showing observed shares, contract conversion quotes, supported market exposure and eligible source checks. Investigate adds bounded multi-position analysis, shared-market relationships, comparisons between two observations, and historical share/accounting verification for Steakhouse USDC on Ethereum. The Graph supplies indexed observations for comparison with direct blockchain reads. Chainlink provides reference prices for eligible assets. An optional Bazantic Recipe explains the displayed evidence with fact citations, while the original report and limitations remain available. Tare separates observations, calculations, reference prices and unverified claims. Missing evidence stays missing; accounting agreement never becomes a universal safety score. Reports and captures can be downloaded, and compatible captures can be replayed without pretending they are fresh evidence. The public investigation flow is read-only and requires no wallet signing. A separate Chainlink CRE experiment demonstrates confidential policy evaluation and bounded execution on a dedicated Base Sepolia test control. Evidence before assumptions.

    How it's made

    Tare is built primarily in TypeScript, with a React/Vite interface, protected HTTP API, CLI and local stdio MCP server. Shared modules separate source acquisition, protocol adapters, integer calculations, verification and report formatting. Live acquisition and saved-capture replay reuse the same comparison logic. Discovery combines Morpho, enabled Euler supply discovery and configured ERC-4626 registry entries. RPC-backed adapters support Morpho V1 market exposure, bounded Ethereum USDC V2-to-V1 traversal and generic ERC-4626 accounting. Other supported V2 candidates receive an explicitly narrower accounting-only check rather than invented strategy coverage. Our AssemblyScript subgraph indexes Steakhouse USDC share transfers and vault/market accounting. A separate accounting-only deployment supports recent comparisons. The Graph Token API contributes wallet share-balance observations; Tare compares eligible data against block-pinned RPC, checking deployment identity, indexing errors and exact values. Historical verification joins share-ledger and accounting comparisons at one covered block. Chainlink valuation uses reviewed USDC/WETH feed mappings on Ethereum, Base and Arbitrum, with round, freshness and L2 sequencer checks. Separately, a CRE confidential handler processes authenticated Tare evidence and private policy thresholds. A retained hosted run delivered a bounded exit through Chainlink’s forwarder and our one-use Base Sepolia receiver; the latest retained configuration is paused. Bazantic exposes seven Tare gateway tools and reusable Recipes. The in-page assistant retrieves a consented, ten-minute report snapshot and returns a cited explanation. Tare checks response structure, citation IDs and complete context retrieval, without claiming these checks guarantee factual correctness. A separate Graph-to-Tare Recipe composes indexed acquisition with RPC comparison. No direct LLM provider dependency was added. Key engineering challenges were preserving exact units, handling indexing lag and block differences, distinguishing authorization from evidence, and retaining useful partial results without overstating verification.