Plume opened trading for nBND on October 5, a token that gives investors blockchain-based exposure to Fidelity's roughly $28 billion Total Bond ETF. The underlying fund — FBND — was not tokenized, and its assets did not move onchain.
NBND is what's known as a receipt token. It represents a claim on a Nest vault that holds actual FBND shares. Hours after launch, something happened. The details aren't fully clear from what's been released so far, but the timing is worth noting.
What nBND actually is
The structure here matters, because it's easy to misread the headline. Fidelity didn't tokenize anything. The $28 billion in FBND stayed exactly where it was — in the traditional fund wrapper.
What Plume did was create a token that tracks exposure to those shares through a vault. Nest is the vault provider. Investors who hold nBND are holding a receipt, not the ETF itself. That's a meaningful distinction. It means the token's value depends on two things working: the vault's ability to hold and manage FBND shares, and the token's ability to accurately reflect that claim.
This isn't the first time a crypto platform has wrapped a traditional asset this way. It is, however, one of the larger traditional funds to get this treatment. A $28 billion bond ETF isn't a niche product. It's the kind of fund that pension committees and conservative allocators use.
The launch timeline
October 5 was the go-live date. Plume announced the opening, and trading began. By all appearances, it was a standard launch — the kind of thing that's become more common as tokenization efforts expand beyond crypto-native assets.
Then, within hours, an unspecified event occurred. The available information cuts off there. No timeline for when more details might emerge, no indication of what specifically happened, and no statement from Plume, Nest, or Fidelity about the nature of the incident.
What's clear is that the launch didn't proceed quietly. That alone is unusual for a product tied to a fund this size.
Why the timing is awkward
Tokenized traditional assets have been a growing theme this year. The pitch is straightforward: bring the transparency and accessibility of blockchain rails to conventional funds that have historically been gated behind brokers and settlement windows.
But the model has a structural tension. The token can trade 24/7. The underlying fund doesn't. FBND shares settle on traditional market hours, through traditional custodians. If the vault needs to buy or sell shares to meet redemption demand, it's operating on a different clock than the token.
That mismatch isn't necessarily fatal. It's just the part that gets tested when markets move fast or when something breaks.
Fidelity's involvement here is indirect. The company didn't issue nBND, didn't announce it, and as of now hasn't commented. Its fund is simply the reference asset. Plume and Nest are the ones running the show.
What comes next
The immediate question is what actually happened in those first hours. Until Plume or Nest provides an account, the market is left guessing. That's not a comfortable place for a product holding exposure to a $28 billion bond fund.
The second question is whether this affects the vault's operations. If nBND holders can't redeem, or if the vault's FBND position is somehow impaired, the consequences would ripple well beyond Plume's user base. So far, there's no indication either way.
For now, the launch is live. The incident, whatever it was, has happened. And the next concrete update — from Plume, from Nest, or from whoever is holding the keys to that vault — is what everyone's waiting on.
