Skip to main content
AVOID.NET
← Blockchain Capitalreviewed 2026-10-16 · 17 claims checked

Fact-check findings

What an automated fact-checker found when it re-read Blockchain Capital against the sources the page cites. Only the most recent review is shown.

Read this first

These findings are produced by an automated reviewer, and its results vary between runs: the same page, checked three times on the same day, came back with 15%, 20% and 34% of its claims disputed, mostly because each run extracted a different number of claims. Treat what follows as leads, not rulings.

“Disputed” means the reviewer could not reconcile the claim with the evidence it cited. It does not mean the claim is false. “Unverifiable” means no reachable source settled it either way.

Nothing here changes the page on its own. A proposed correction is applied only after a human moderator approves it; until then the page reads as it did when reviewed.

disputed 2partially supported 6confirmed 92 corrections pending · 0 applied

disputed

2 claims

The reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.

  1. #13[disputed][awaiting moderator]in section: Epstein/Coinbase Periphery
    “Epstein invested $3M in a 2014 Coinbase round alongside Blockchain Capital.”
    reviewerEpstein invested $3M in a 2014 Coinbase round alongside Blockchain Capital.Both cited sources, fetched directly, say Blockchain Capital planned a roughly $3.25M co-investment but that 'a fund investment was never consummated' and Epstein 'independently invested through his own entity, IGO Company LLC' (about $3M/$3,001,000). The page's phrasing that Epstein invested 'alongside Blockchain Capital' implies a joint investment that the cited sources explicitly say did not happen -- Blockchain Capital's only confirmed involvement was introducing/presenting the deal.
    Proposed correction (not yet applied)
    Epstein invested roughly $3M in a 2014 Coinbase round after Blockchain Capital presented him the opportunity; Blockchain Capital says its own planned co-investment in that round was never consummated and that Epstein invested independently through his entity, IGO Company LLC.
  2. #14[disputed][awaiting moderator]in the timeline
    “DOJ documents reveal Epstein $3M Coinbase investment alongside Blockchain Capital”
    reviewerDOJ documents reveal Epstein's $3M Coinbase investment occurred alongside Blockchain Capital.Same mischaracterization as the Epstein/Coinbase Periphery section: the cited CoinDesk article says Blockchain Capital's planned co-investment 'was never consummated' and Epstein invested independently, so 'alongside Blockchain Capital' overstates the firm's direct involvement in the 2014 purchase itself.
    Proposed correction (not yet applied)
    DOJ documents reveal Epstein's $3M Coinbase investment, which Blockchain Capital had introduced but says it did not itself make

partially supported

6 claims

The cited evidence supports part of the claim but not all of it.

  1. #7[partially supported][awaiting moderator]in section: Portfolio and Performance
    “NAV peaked at $23.83 in Q1 2021, fell to $14.72 by Q1 2023, reportedly recovered to ~$106 by early 2026.”
    reviewerNAV per BCAP token peaked at $23.83 in Q1 2021, fell to $14.72 by Q1 2023, and recovered to roughly $106 by early 2026.The specific NAV figures are independently accurate: Securities.io reported $23.83 as of March 31, 2021 and $14.72 as of March 31, 2023, and a live fetch of RWA.xyz/CoinGecko on review date showed NAV ~$106 ($105.74 on CoinGecko). However, the two sources actually cited for this section (CoinDesk's $580M-raise article and Bloomberg's $700M-raise article) do not contain any NAV history data -- the real support is uncited Securities.io quarterly reports and RWA.xyz, so the section's citations do not back its central numeric claims.
  2. #8[partially supported][awaiting moderator]in section: Entity Overview
    “BCAP represents 9.1M tokens on ZKsync Era, providing indirect economic interest in Fund III through a Cayman Islands/Singapore intermediary.”
    reviewerBCAP represents 9.1M tokens on ZKsync Era.A live fetch of RWA.xyz on the review date shows 8,980,603.37 tokens outstanding, about 1.4% below the page's 9.1M figure -- close enough to be a stale/rounded snapshot rather than a clear error, but not an exact match. RWA.xyz also describes Singapore as the issuer's domicile and Cayman Islands only as the 'Dispute Resolution Country', not a joint 'Cayman Islands/Singapore intermediary' structure as implied.
  3. #9[partially supported][awaiting moderator]in the summary
    “No SEC enforcement actions exist.”
    reviewerNo SEC enforcement actions exist against Blockchain Capital.No SEC litigation release, administrative proceeding or press release against Blockchain Capital surfaced in searches of SEC.gov and news coverage, consistent with the claim. However, this is a negative claim (absence of action) that is inherently hard to fully verify, and no source in the page's citation list is actually about SEC enforcement history -- the claim is asserted without a supporting citation.
  4. #10[partially supported][awaiting moderator]in section: SEC and Regulatory Status
    “No enforcement actions. BCAP was structured under Regulation D Rule 506(c) from day one.”
    reviewerNo enforcement actions exist against Blockchain Capital, and BCAP has compliant custody through Coinbase Custody and Anchorage.The 506(c) structuring claim is independently confirmed (multiple 2017 reports describe the BCAP ICO as a Rule 506(c)/Reg S offering capped at 99 accredited U.S. investors), but the section's only cited source is the 2018 Bloomberg Templum article, which addresses neither enforcement history nor the Reg D rule used. Same uncited-enforcement issue as the summary claim.
  5. #11[partially supported][awaiting moderator]in section: SEC and Regulatory Status
    “Compliant custody through Coinbase Custody and Anchorage.”
    reviewerBCAP custody is handled through Coinbase Custody and Anchorage.Independently confirmed via a live fetch of RWA.xyz, which lists Anchorage Digital Bank N.A. as 'Custodian' and Coinbase Custody as 'Crypto Custodian'. The claim is true but is not supported by the section's only cited source (the 2018 Bloomberg Templum article), which never mentions custody.
  6. #12[partially supported][awaiting moderator]in section: Firm Reputation
    “No regulatory actions and institutionally credible with active fundraising.”
    reviewerBlockchain Capital has no regulatory actions against it and is institutionally credible.The Block's article (fetched directly) confirms the ~$2B AUM and active $700M fundraise but says nothing about regulatory or enforcement history, so it does not support the 'no regulatory actions' assertion. Third occurrence of the same uncited-regulatory-status pattern seen in the summary and the SEC/Regulatory Status section.

confirmed

9 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in section: SIM-Swap Attack on Co-Founder
    “$6.3M in personal crypto was stolen from co-founder Bart Stephens in May 2023 via SIM-swap attack. Lawsuit filed August 2023 against anonymous perpetrators. Not a fund breach but a significant personal security incident.”
    reviewerBart Stephens, co-founder of Blockchain Capital, lost $6.3M in a SIM-swap attack in May 2023 and sued anonymous perpetrators in August 2023.Corroborated independently by Forbes Australia, ForkLog and Blockworks search coverage: $6.3M stolen May 12-14, 2023 via SIM-swap impersonating Stephens' brother; complaint filed Aug 16, 2023 in N.D. Cal. against 'Jane Doe'. Both cited URLs returned HTTP 403 on direct fetch (likely anti-bot, not confirmed dead), but content is corroborated by independent outlets.
  2. #2[confirmed][no action needed]in section: X Account Hijacking
    “In August 2023, Blockchain Capital's Twitter/X account was hijacked to promote a fake BCAP airdrop phishing scam. The account was recovered with no fund assets affected.”
    reviewerIn August 2023, Blockchain Capital's X/Twitter account was hijacked to promote a fake BCAP airdrop phishing scam, and was recovered with no fund assets affected.Confirmed via search: account compromised August 9, 2023, used to promote a fake BCAP token claim with a lookalike phishing domain; account was later recovered. Matches page's month-level date.
  3. #3[confirmed][no action needed]in section: Brock Pierce Founding Controversy
    “The firm's 2019 attempt to scrub Pierce from founding history is documented and contradicted by contemporaneous sources.”
    reviewerBrock Pierce co-founded the firm and Blockchain Capital's 2019 attempt to distance itself from him as a founder is documented and contradicted by contemporaneous sources.Fetched directly; Decrypt article published May 3, 2019 (updated July 30, 2019), confirming a Blockchain Capital spokeswoman disputed Pierce's founder status while the firm's own Wikipedia page, CoinDesk and CNBC called him a founder.
  4. #4[confirmed][no action needed]in section: Portfolio and Performance
    “$580M raised in 2023; $700M raise underway as of April 2026.”
    reviewerBlockchain Capital raised $580M for two new funds, announced September 18, 2023.Confirmed via Bloomberg, The Block, Fortune and Decrypt coverage: $580M closed Sept 18, 2023 across a sixth early-stage fund and first opportunity fund; $700M raise (seventh early-stage + second growth fund) reported by Bloomberg April 22, 2026.
  5. #5[confirmed][no action needed]in section: Investor Rights and Token Structure
    “First dividend paid in January 2025 ($0.25/token USDC after 8 years).”
    reviewerBCAP's first dividend was $0.25/token paid in USDC in January 2025, roughly 8 years after the April 2017 token issuance.PR Newswire release confirms $0.25/token USDC dividend with expected payout date January 28, 2025, and migration to ZKsync; 2017-to-2025 is 8 years as stated.
  6. #6[confirmed][no action needed]in section: SEC and Regulatory Status
    “First claimed SEC-compliant secondary trade occurred in January 2018 via Templum.”
    reviewerThe first claimed SEC-compliant secondary trade of BCAP tokens occurred via Templum in January 2018.Bloomberg (Jan 22, 2018) reported Templum CEO Chris Pallotta's claim that a BCAP trade was the first fully compliant security-token trade on its platform; page correctly frames this as a 'claimed' first. Direct WebFetch of the Bloomberg URL returned 403 (paywall), but the article's content is independently corroborated by search-indexed coverage.
  7. #15[confirmed][no action needed]in section: Epstein/Coinbase Periphery
    “Blockchain Capital later purchased roughly half of Epstein's Coinbase stake in 2018 for ~$14.7M.”
    reviewerBlockchain Capital purchased roughly half of Epstein's Coinbase stake in 2018 for approximately $14.7M.Both sources, fetched directly, confirm Blockchain Capital agreed in 2018 to buy half of Epstein's Coinbase position for $14,666,667 (~$14.7M), implying a gain of over $11M on the portion sold.
  8. #16[confirmed][no action needed]in section: Secondary Market Liquidity
    “Effectively zero on-chain secondary trading exists. Regulated transfer restrictions mean BCAP is for all practical purposes an illiquid private fund interest despite the token wrapper.”
    reviewerEffectively zero on-chain secondary trading exists for BCAP; it is for all practical purposes illiquid.Both cited URLs were fetched directly and loaded without issue. STOMarket shows mostly $0.00 daily volume with only sporadic small trades (largest $94,554). CoinGecko explicitly states BCAP tokens 'have stopped trading' on all its listed exchanges and 24h volume is $0.00.
  9. #17[confirmed][no action needed]in the summary
    “The firm manages $2B+ AUM with portfolio companies including Coinbase, Kraken, and Circle.”
    reviewerBlockchain Capital manages $2B+ AUM.Confirmed by multiple independent sources (Bloomberg Sept. 2023, The Block April 2026) citing ~$2B in (fee-bearing) assets under management; portfolio companies Coinbase, Kraken and Circle are independently corroborated by multiple VC-tracking sites.
How this fits together. The reviewer reads the published page and its cited sources and records one finding per claim. A human moderator decides whether each proposed correction is applied; those decisions, and the score changes they cause, appear in the audit log. Earlier review runs are not shown here; only the latest reflects the page as it stands.