You open Zelcore, look for bStocks, and the banner that used to invite you to browse them is gone. No error, no warning, nothing labeled "restricted." The Add bStocks dialog just isn't there anymore. If you already hold a bStock, it's still sitting in your wallet with a live price — you just can't buy any more. That silence isn't a bug. It's the visible edge of a compliance system with three separate layers, and knowing which layer is doing what will save you from bad assumptions. This is Part 4 of our bStocks series.
Why a Permissionless-Looking Token Has a Passport Check
A bStock is a BEP-20 token on BNB Smart Chain. It moves like any other token: self-custodial, sendable to any address, no login required to hold it. That surface makes it easy to assume bStocks are as open as most crypto assets.
They aren't, because of what's on the other side of the token. bStocks are issued under an Approved Prospectus for each bStock, admitted to the FSRA Official List in the Abu Dhabi Global Market (ADGM), and those prospectuses don't extend coverage to other jurisdictions. The issuer's own FAQ states plainly that these tokenized securities are "not offered, sold, distributed, made available, or accessible in the United States or to, or for the account or benefit of, U.S. persons."
This isn't a crypto-specific rule — it's an ordinary securities-law constraint on what the token represents: a claim on a real, US-listed share. Wrapping a regulated security in a BEP-20 contract doesn't change its legal nature.
Three Different Layers of "Restricted" — Don't Conflate Them
It helps to separate "restricted" into the three places it actually gets enforced.
Layer 1 — the issuer's contract-level controls. The bStocks FAQ states transfers "may be restricted, rejected, delayed, frozen, paused, blacklisted, refused to be recognized, or otherwise blocked" if an address, user, transaction, jurisdiction, or activity may breach applicable law. The issuer reserves the right to add a wallet address to the token's smart-contract blacklist at its own discretion. This control lives in the contract and follows the address, not a session.
Layer 2 — the liquidity venue's geo-block. The dedicated bStocks swap route runs through Binance Web3, which checks the trading account's jurisdiction before executing a mint- or redeem-linked conversion or swap. This is an access control at the venue, separate from the token contract.
Layer 3 — the integrating wallet's own check. An app like Zelcore that lists bStocks and offers a swap decides independently whether to surface the product to a given user, because it isn't the issuer and doesn't control the token contract.
These layers can disagree. A contract blacklist is permanent and tied to an address. A venue geo-block is per-session and tied to a login. a wallet's own check is a UI decision on top of both. Passing one layer says nothing about the other two.
Exactly How Zelcore Handles It
On every login, Zelcore's servers check bStocks availability for the country associated with the user's connection, using the same restricted-country basis Binance applies. The check runs server-side.
Zelcore doesn't keep its own country list. Each BTech Holdings prospectus defines Restricted Jurisdictions as those "communicated on the Binance Platform", so Binance's current list is the reference, not any list copied into an article (checked 12 October 2026 against the NVIDIA bStocks prospectus published by ADGM).
The default is fail-closed: if the country can't be determined, bStocks are treated as unavailable rather than shown — a deliberate choice to err toward hiding the product rather than risk exposing it where it shouldn't be offered.
When a region comes back restricted, several things happen together: the one-time intro banner never shows, the Add bStocks dialog and Tokenized Stocks section inside Add Assets are hidden, the Swap action is disabled on any bStock coin card, and bStocks are removed from both sides of the swap pair picker.
Already-held bStocks are unaffected: balance, price, the chart, and the Tokenized US equity chip stay fully visible, and tokens can still be sent and received, since those are ordinary BSC transactions that don't touch Binance's swap backend. The restriction is specifically on the swap path, not on holding or moving the asset.
Zelcore does not show an explicit "unavailable in your region" message — the surfaces are simply absent. If you're looking for Add bStocks and can't find it, region restriction should be your first suspect. Availability is re-evaluated on every login, so travel changes what the UI shows, in both directions.
The VPN Trap
It's tempting to route around a geo-block with a VPN, but the layering above is exactly why that's risky rather than clever. A VPN can fool the venue-side check (Layer 2), waving a masked connection through in the moment. The contract-level blacklist power (Layer 1) doesn't depend on how the connection looked at swap time — it's a separate, permanent control.
The issuer's FAQ restricts addresses whose activity "may constitute a violation of applicable laws," adding them to the "smart contract blacklist at the issuer's discretion" — meaning the exposure is to the address itself, not just that session. A blacklisted address can be blocked from transacting with bStocks going forward, stranding a balance you still control but can no longer move. Independent of whether it even works, circumventing geo-restrictions with a VPN also violates the terms bStocks are offered under.
This isn't unique to bStocks: reporting on Robinhood's comparable tokenized-stock geo-blocking made the same point — "Front-end geo-blocking protects the issuer. It does much less to protect the user."
What Happens to Holdings If You Move to a Restricted Country
Nothing is confiscated or force-sold. If you bought bStocks while connected from an allowed country and later open Zelcore from a restricted one, the swap actions and add-asset surfaces disappear, but the tokens stay in the wallet exactly as they were, visible with a live price and chart, and still sendable and receivable as ordinary BEP-20 transfers.
Zelcore's restriction only touches the swap path, not the underlying blockchain balance; the blocked action is specifically buying more or selling, not holding or moving tokens between your own addresses.
Connect from an allowed region again and the swap surfaces return automatically, since availability is re-checked every login. Worth contrasting with the VPN scenario above: a geography-based UI restriction is reversible by moving, while a contract-level blacklist is not.
This distinction — what a contract controls versus what an interface layers on top — comes up across tokenized assets generally. We've covered the legal wrapper vs on-chain representation behind a tokenized asset, and separately, redemption, custody, and counterparty risk once you're holding one.
What to Check Before You Buy
- Confirm you're not a US person and not connecting from the United States — bStocks exclude both by the issuer's terms, regardless of what any app shows you.
- Don't assume the absence of an "unavailable" message means everything is fine. In Zelcore, unavailability shows up as missing surfaces, not a warning.
- Don't use a VPN to access bStocks from a restricted location — it risks a permanent contract-level blacklist on your address, not just a blocked swap.
- Remember holding is more durable than trading rights: your balance survives a move to a restricted region, but your ability to swap doesn't.
- Check the issuer's own FAQ and legal documentation for current eligibility rules before relying on a third-party summary, since restricted-jurisdiction lists change over time.
If you're newer to holding RWAs in self-custody, that piece covers approvals and transferability beyond bStocks specifically.
Risks to understand before you participate
The region-specific risks are the ones covered above: a contract-level blacklist is permanent and tied to your address, a missing swap option doesn't tell you why it's missing, and passing the venue's check says nothing about the issuer's own review. Zelcore's check follows the issuer's current basis rather than a policy Zelcore sets, and nothing here is legal advice. For issuer, custody and freeze risk in general, and how bStocks compare with xStocks, Dinari and Ondo, see bStocks risks compared with other tokenized stocks.
Key takeaways
- bStocks carry a securities-law restriction, not a crypto-native one: excluded from the United States and from US persons by the issuer's own ADGM prospectus.
- Three separate layers enforce this — the issuer's contract-level blacklist, the swap venue's geo-block, and Zelcore's own availability check — and they don't always move together.
- Zelcore checks availability on every login, fails closed when it can't determine your country, and hides bStocks surfaces without an explicit message.
- Already-held bStocks stay visible and remain sendable and receivable even in a restricted region; only the swap path is blocked.
- Using a VPN to bypass the check risks a permanent, address-level contract blacklist — a very different consequence than a session-based UI restriction.
