← Vivek Kumar Sen and Zamyang Sherpareviewed 2026-10-27 · 11 claims checked
Fact-check findings
What an automated fact-checker found when it re-read Vivek Kumar Sen and Zamyang Sherpa 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.
unverifiable
4 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #2[unverifiable][awaiting moderator]in section: Lawsuit and Legal Status
“with Lewis Silkin LLP representing the plaintiffs”
reviewerLewis Silkin LLP represents the plaintiffsNone of the cited pages I read name Lewis Silkin. The same claim recurs in the legal strategy section, along with a characterisation of the firm. - #3[unverifiable][awaiting moderator]in section: Defendants: Background and Prior Activity
“Both Vivek Kumar Sen and Zamyang Sherpa are identified in the court filing as residents of Preston, Lancashire, United Kingdom.”
reviewerBoth defendants are identified in the filing as residents of Preston, LancashireA specific town for named individuals is not supported by any cited source I read. This is sensitive personal location data for living persons; recommend removal unless a source is found. - #8[unverifiable][awaiting moderator]in the timeline
“2023-08-01”
reviewerTimeline: earliest enrollment on 2023-08-01 and last enrollment on 2026-02-28The sources give month-level precision only. The day-level dates 2023-08-01 and 2026-02-28 appear to be synthesised placeholders. Also, the page elsewhere presents the Feb 2026 end of the range as the end of payouts, not the last enrollment. - #10[unverifiable][awaiting moderator]in section: X's Legal Strategy and Broader Context
“The lawsuit represents a precedent-testing move in which a major social platform pursues civil fraud recovery against alleged engagement-manipulation actors in a named UK High Court proceeding.”
reviewerLewis Silkin is described as a UK law firm with experience in media and technology litigation; case is precedent-testing and no comparable prior X case was identifiedThis is editorial characterisation not in any source I read.
partially supported
2 claimsThe cited evidence supports part of the claim but not all of it.
- #4[partially supported][awaiting moderator]in section: Defendants: Background and Prior Activity
“He also hosted a podcast called The Vivek Podcast and served as an EU news reporter for Bitcoin Magazine.”
reviewerSen hosted The Vivek Podcast and served as an EU news reporter for Bitcoin MagazineOther biographical details check out against the author page. The podcast and title are not on the cited page and may come from an uncited source. - #9[partially supported][awaiting moderator]in the timeline
“X launched Original Content Rewards to replace the Creator Revenue Sharing Program, with stated filters against artificial impressions.”
reviewerX suspended the six accounts on Aug 18, 2026; Aug 7 enrollment stop; Sept 7 program end; Sept 8 Original Content Rewards launchDates are consistent across outlets within a day. The Sept 8 date is supported by crypto.news but not by the cited Cryptopolitan page, which says about Sept 7.
confirmed
5 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in section: Lawsuit and Legal Status
“On September 17, 2026, X Internet Unlimited Company and X Corp. filed a civil claim (BL-2026-001161) in the Business and Property Courts of England and Wales against Vivek Kumar Sen, Zamyang Sherpa, and unnamed additional account operators.”
reviewerClaim BL-2026-001161 was filed Sept 17, 2026 in the Business and Property Courts by X Internet Unlimited Company and X Corp against Sen, Sherpa and persons unknownCorroborated by crypto.news and a search summary of other outlets. - #5[confirmed][no action needed]in section: Defendants: Background and Prior Activity
“His Bitcoin Magazine author page credits him with 285 published articles on that platform, where he wrote under the byline 'Vivek.'”
reviewerBitcoin Magazine author page credits 285 articles; Sen discovered Bitcoin in 2016; ran Bitgrow Lab; previously worked at Lightning VenturesThe byline detail was not separately checked. - #6[confirmed][no action needed]in section: Financial Breakdown of Alleged Fraudulent Payouts
“@Vivek4real_ (linked to Sen) received £74,332.44; @Bitcoin_Teddy (linked to Sen, via a Stripe account in the name Stefan Mann) received approximately £50,065 in aggregate across multiple currency tranches including euros and Paraguayan guarani; @saylordocs (linked to Sen) received £49,441.91; @TrendingBitcoin (linked to Sherpa) received £22,938.35; @PolyBackTest (linked to Sherpa) received £6,705.25; @Kalshibacktest (linked to Sherpa) received £3,490.71.”
reviewerAlleged payouts total at least £207,384 with a per-account breakdownFigures match two outlets and sum to roughly £207,384 with the small guarani tranche. RuntimeWire, also cited, does not give the breakdown. - #7[confirmed][no action needed]in section: Lawsuit and Legal Status
“interest under Section 35A of the Senior Courts Act 1981”
reviewerX seeks at least ~£75,000 in costs and interest under s.35A Senior Courts Act 1981The cause-of-action list also matches a search summary, except that 'knowing receipt' was not seen in sources I read. - #11[confirmed][no action needed]in section: Defendant Response
“The allegations remain untested and unproven in court.”
reviewerNo defense filing or statement located; right-of-reply requests unansweredMy own search found no later defense or ruling.
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.