BCAP is a venture fund wrapped in an ERC-20

BCAP is not “utility tokenomics” in the usual Web3 sense. It is a tokenized venture fund structure where an onchain token is explicitly used as a securities wrapper for an economic claim on a managed portfolio. For a contrast with more cash-like tokenized funds, see our USTBL tokenomics review.

Per the April 10, 2017 offering memorandum, BCAP is an Ethereum-based token representing an indirect, fractional, non-voting economic interest in the sole limited partnership interest in Blockchain Capital III Digital Liquid Venture Fund, LP (BC III DLVF) held by the issuer, Blockchain Capital TokenHub Pte. Ltd. (BCTH).

The same document is unusually direct about the compliance perimeter. The offering is described as being made (i) inside the US to up to 99 accredited investors and (ii) outside the US to non-US persons, relying on Regulation D and Regulation S constructs, with resale constraints designed to preserve those exemptions.

That framing matters because it dictates the token’s “product surface.” The token’s job is not governance, staking, or protocol fees. It is (a) a transferable record of a restricted security and (b) a mechanical rail for buybacks, redemptions, and (as of later updates) dividend-like distributions.

Supply: legally capped, technically elastic

The first tension in BCAP tokenomics is the gap between what the legal documents say the supply is supposed to be and what the token contract can do.

The smart contract design audited in 2017 implements a central bank model where a designated issuer account effectively controls circulating supply. The contract assigns a MAX_UINT256 balance to the central bank and defines total supply as MAX minus the central bank’s balance, which means circulating supply increases as tokens move out of the central bank.

OpenZeppelin’s audit summary calls this out plainly. The tokenIssuer address has “full control of the token supply,” and the same control plane can freeze and unfreeze transfers.

In other words, any hard cap is enforced by the offchain governance and legal covenants, not by immutable onchain constraints. That is a reasonable design choice for a regulated product. It is also a regulatory liability if the market ever treats “token supply” as a purely technical truth.

On the current token tracking side, CoinGecko lists BCAP on zkSync Era with contract 0x57fD71a86522Dc06D6255537521886057c1772A3 and shows 9,112,111 as circulating and total supply, and “∞” max supply as coded.

BCAP also historically existed on Ethereum mainnet. Etherscan labels an Ethereum contract for “Blockchain Capital Token” at 0x1f41e42d0a9e3c0dd3ba15b527342783b43200a9.

Allocations / distribution (as described in the offering docs)

Cashflow model: fees, NAV, and buyback-first “distributions”

BCAP’s economics read like traditional VC fund economics, then get translated into token-holder outcomes via secondary-market buybacks and issuer-controlled redemption pathways.

Fees are explicit. The base management fee is described as 0.625% quarterly, which corresponds to 2.5% annual of NAV, payable quarterly in advance.

Carried interest is described as 25% of realized capital gains, determined upon each realization on a cumulative basis, netting realized losses and specified unrealized losses, and net of previously paid carry.

NAV is central because the design leans on it as the “anchor” against which buybacks and redemption are framed. The memorandum describes NAV per BCAP as NAV divided by the number of outstanding BCAP tokens (defined as issued minus redeemed and/or purchased under buybacks).

That same section is also where tokenholders lose most of what crypto-native investors reflexively expect. Valuations assigned by the manager are stated to be “final and conclusive,” and tokenholders have no audit right over the valuations.

Returns to tokenholders (2017 design) are explicitly not dividends. The document states BCAP tokens have no distribution or dividend rights (other than on redemption), and that return of capital occurs through open market purchases under the buyback programs.

The buyback mechanics are spelled out in a way that matters for tokenomics modeling:

Realization buybacks: upon realizations, a minimum of 50% of proceeds should be reinvested (subject to a stated timing condition), and the remainder may be distributed to BCTH for use to repurchase BCAP on the open market. Tokens repurchased are described as being “immediately cancelled,” which increases the indirect fractional interest of remaining holders.

Liquidity buybacks: if market price (using a defined exchange-averaging approach) drops below 75% of NAV per token (based on the last quarterly NAV report), BC III DLVF and/or BCTH may purchase BCAP on the open market at its sole discretion.

Fixed price offers: after the first NAV report, BC III DLVF and/or BCTH may offer to repurchase tokens at a fixed price with at least 30 days notice published on TokenHub.

Redemption is issuer-driven, not holder-driven. The issuer states it may redeem after ten years for NAV and may redeem earlier upon regulatory concerns, while tokenholders do not have the right to compel redemption.

Governance and control surface

BCAP’s “governance” is mostly a set of manager and issuer discretions that would be familiar in private fund land, combined with a token contract that can be administratively constrained.

First, tokenholders have no voting rights, and the issuer states it does not intend to hold annual meetings.

Second, the smart contract has an explicit freeze/unfreeze feature controlled by an owner address, and transfer and transferFrom return false when transfers are frozen.

Third, issuance control is structural. The audited “central bank” model means supply management is inherently centralized at the token layer. The audit notes the tokenIssuer has full control of supply and recommends high security standards such as multisig for that key.

From a regulatory pragmatist angle, this is coherent. A fund token that cannot pause transfers or restrict flows is harder to keep inside securities-law constraints. The trade-off is obvious. The more the token behaves like an administratively controlled cap table, the less it behaves like credibly neutral money.

History and structural changes

BCAP’s core structure was publicly described in March 2017 as a parallel offering to a traditional fund, using Ethereum-based tokens representing fractional ownership in an evergreen fund vehicle.

The April 10, 2017 memorandum hard-coded the original “no dividends” posture and emphasized buybacks and issuer redemption as the capital return mechanisms.

On December 11, 2024, Blockchain Capital announced a payout of $0.25 per token in USDC to token holders, with payout expected on January 28, 2025, and that the fund would be migrating fully to ZKsync.

They also framed that $0.25 payout as 25% of the original $1 purchase price in the initial token offering in April 2017.

This is not a minor comms tweak. It changes how many holders will mentally underwrite the asset. Buyback-only tokens tend to trade like opaque closed-end funds with uncertain timing. Add explicit cash payouts and the token starts to look and feel like a yield instrument. For a crypto-native yield token comparison, see our YLDS tokenomics review. That can improve marketability while tightening the security-characterization story in jurisdictions that care about “expectation of profit” and issuer efforts.

Risk analysis

Dominant risk: BCAP’s tokenomics are inseparable from securities compliance, and the design choices that make the product legally survivable also make it hard to model and fragile under regulatory stress. For another example of a compliance-bounded cashflow token, compare against our SSTN tokenomics review.

The memorandum is explicit that transfers and resales are constrained by investor status and jurisdictional rules, including a framework intended to keep US persons under a 100-holder threshold relevant to Investment Company Act positioning.

Combine that with issuer-controlled redemption “upon regulatory concerns,” and you get a token whose economic lifecycle can be forced by compliance events rather than portfolio fundamentals.

Onchain, the contract layer reinforces that this is not a credibly neutral asset. The issuer control plane includes the ability to freeze transfers. Supply is also centrally managed via the “central bank” architecture, which the audit explicitly describes as giving the tokenIssuer full control of supply.

That is the trade. Token flexibility, administrative controls, and transfer management reduce legal exposure for an asset that is functionally a fund interest. They also increase dependence on offchain governance quality, operational security, and regulator interpretation. If those inputs degrade, the token’s “economic model” becomes less relevant than the control rights embedded in the docs and the issuer’s discretion to act.

In practice, this dominant risk shows up as parameter instability-these are token economy design components that dominate outcomes. Buybacks are discretionary. Redemptions are issuer-driven. Valuations are final and unauditable by holders. Even the shift from “no dividends” to announcing a USDC dividend illustrates how the payout profile can change over time in response to strategy and market constraints.

If you are trying to value BCAP as if it were a protocol token with stable rules, you will overfit. You have to value it like a managed vehicle operating inside a shifting compliance boundary-a theme we revisit in our research reports.

Top 3 risks

  1. Regulatory forcing functions. Trigger: a change in applicable securities or fund regulation, or a holder profile that creates “regulatory concerns.” Mechanism: issuer may redeem tokens early on regulatory grounds and resale restrictions can bind liquidity, while transfer management is reinforced by the ability to freeze transfers. Who bears it: tokenholders, primarily via forced exits, impaired liquidity, and basis risk versus NAV. Measurable indicators: changes to official issuer communications about eligibility, redemptions, and transfer limitations, and any onchain transfer halts consistent with a freeze.

  2. NAV opacity and discretion. Trigger: market stress, portfolio markdown cycles, or disputes about valuation methodology. Mechanism: NAV per token is defined by manager valuation inputs, which are stated to be final and conclusive, and tokenholder audit rights are disclaimed. Who bears it: tokenholders, through mispricing, delayed price discovery, and weakened confidence in the 75% of NAV buyback trigger as a “floor.” Measurable indicators: widening and persistent discounts to stated NAV, reduced exchange liquidity, and increased reliance on discretionary fixed-price offers instead of organic market clearing.

  3. Control-plane and key risk. Trigger: compromise or misuse of issuer-controlled roles. Mechanism: tokenIssuer has full control of supply in the “central bank” model and can freeze/unfreeze transfers via owner controls. Who bears it: tokenholders first, then the issuer via legal exposure and reputational damage. Measurable indicators: changes in privileged address behavior, unexpected supply shifts relative to policy, or any irregular transfer behavior that suggests administrative intervention at the contract level.

If you are building anything similar, treat the payout mechanics, redemption rights, and admin controls as first-class design objects. This is where token economy design stops being an academic exercise and becomes legal engineering. For teams that need external help pressure-testing these trade-offs, this is the narrow slice of tokenomics design services that is worth paying for.



This article is part of our Tokenomics Deep Dive series.