Deployments · Securitize · platform by Securitize

VanEck Treasury Fund (VBILL)Updated 28 Oct 2026

VanEck's first tokenised fund, a US Treasury fund built with Securitize and launched on Avalanche, BNB Chain, Ethereum and Solana at once, with Wormhole for cross-chain transfers. Minimums are $100,000 on most chains and $1 million on Ethereum. Supply is split fairly evenly across Ethereum, BNB Chain and Solana.

AnnouncedProof of conceptPilotLive (limited)Live (scaled)

Live (limited) since 13 May 2025[5] — Qualified investors only; about $60 million on chain in October 2026. · Reviewed 13d ago

Assets
Fund interest[5]
Fund shares issued as tokens; the fund holds US Treasuries
Networks
Ethereum Public, permissionless[5]
Avalanche Public, permissionless[5]
BNB Chain Public, permissionless[5]
Solana Public, permissionless[5]
Use cases
Primary issuance[4]Fund subscription and redemption[4]
Jurisdictions
United States

Participants

Likely relevant regulation

Assets

Data feeds

  • Fund NAVChainlink LabsNAVLink (SmartData)Ethereum[3][2]VBILL NAV feed, issuer VanEck, data via Securitize; Chainlink says it supports VBILL on Aave Horizon (LlamaGuard NAV variant listed).
  • Fund NAVRedStoneRedStone NAV feed (push and pull)Ethereum, BNB Chain, Solana, Avalanche[1]RedStone prices VBILL daily for the Euler KPK vault.
  • Interest ratesRedStoneRedStone interest accrual feedEthereum, BNB Chain, Solana, Avalanche[1]

Moves across networks

Metrics

  • $59.82mAssets under management · as of 11 Oct 2026[4]
    On-chain via rwa.xyz.
  • $22.93mAssets on Ethereum · as of 11 Oct 2026 · on Ethereum[4]
    On-chain token supply via rwa.xyz; NAV $1.
  • $21.61mAssets on BNB Chain · as of 11 Oct 2026 · on BNB Chain[4]
    On-chain token supply via rwa.xyz; NAV $1.
  • $14.57mAssets on Solana · as of 11 Oct 2026 · on Solana[4]
    On-chain token supply via rwa.xyz; NAV $1.
  • $706,365Assets on Avalanche · as of 11 Oct 2026 · on Avalanche[4]
    On-chain token supply via rwa.xyz; NAV $1.
  • 26 holdersToken holders · as of 11 Oct 2026[4]
    On-chain via rwa.xyz.
  • $167.64mFund interests sold since launch · as of 29 May 2026[7]
    Form D 'total amount sold' since the first sale on 2025-06-01: cumulative subscriptions into the fund, whose interests are issued as tokens; 15 investors had invested. Gross of redemptions, so it is not a balance.
  • 15 investorsInvestors in the offering · as of 29 May 2026[7]
    Form D count of investors who have already invested.

Timeline

  1. Happened 13 May 2025 · Launch · recorded 11 Oct 2026
    VanEck and Securitize launch VBILL on four chains.[5]

Sources

  1. [1]Tokenize the World: RedStone's Role in the Securitize Ecosystem — RedStone, 6 Jul 2026. Accessed 16 Oct 2026. Provider self-report: RedStone is Securitize's primary oracle partner and lists the feeds and networks per product..B
  2. [2]Chainlink's Work With Major Tokenized Asset Platforms and Stablecoin Issuers — Chainlink. Accessed 16 Oct 2026. Chainlink's own round-up of client announcements (provider self-report); undated page..B
  3. [3]Chainlink data feeds directory: Ethereum mainnet (machine-readable feed list behind data.chain.link) — Chainlink. Accessed 16 Oct 2026. Provider's own feed directory; JSON with no page headline, so the title is descriptive. Each entry names the feed, its proxy contract and, for SmartData feeds, the issuer and data source..B
  4. [4]VBILL asset page — RWA.xyz. Accessed 11 Oct 2026.A
  5. [5]VanEck, Securitize launch tokenized US Treasury fund across four blockchains — The Block, 13 May 2025. Accessed 11 Oct 2026.C
  6. [6]Securitize announces Wormhole as official interoperability provider for VanEck's first tokenized fund, VBILL — Wormhole, 13 May 2025. Accessed 13 Oct 2026.B
  7. [7]VanEck Treasury Fund, Ltd.: Form D notice of exempt offering (amendment) signed 2026-05-29 — VanEck Treasury Fund, Ltd. (SEC Form D/A), 29 May 2026. Accessed 26 Oct 2026.A
  8. [8]VanEck Launches its First Tokenized Fund on Securitize — Markets Media, 14 May 2025. Accessed 28 Oct 2026.C

Spotted something out of date or missing? Suggest a correction, ideally with a source.