Startup Diligence
Diligence report Enterprise Tech / blockchain infrastructure / zero-knowledge proof scaling Private unicorn / growth-stage blockchain infrastructure company with public token ecosystem exposure

StarkWare Industries Ltd.

StarkWare Startup Diligence Report

Proceed only to confirmatory diligence. A credible thesis depends on proving that StarkWare can convert STARK technical depth and Starknet/StarkEx adoption into durable, compliant company economics while reducing technical centralization, token/regulatory, bridge/security and competitive L2 risks.

Company profile

StarkWare Startup Diligence Report

StarkWare appears eligible for public-source diligence as an active private unicorn in zero-knowledge blockchain infrastructure. Public evidence supports active products, recognizable StarkEx customers, Starknet token/ecosystem activity, open-source R&D and a $8.0B valuation anchor, but the investment case cannot be underwritten from public data alone.

Website
starkware.co
Sector
Enterprise Tech / blockchain infrastructure / zero-knowledge proof scaling
Geography
Israel (CB Insights: Netanya) with global Ethereum, Starknet and Web3 ecosystem exposure
Stage
Private unicorn / growth-stage blockchain infrastructure company with public token ecosystem exposure
Known aliases
StarkWare, StarkWare Industries, Starknet, StarkEx, Cairo, SHARP, Stwo, STONE PROVER
Report version
1.0
Timezone
UTC

Executive summary

Strengths

  • StarkWare publicly documents Starknet, StarkEx, Cairo and STARK prover infrastructure.
  • Public customer testimonials name Immutable, Sorare, dYdX, rhino.fi and ApeX, and L2BEAT shows current Starknet operating metrics.
  • Open-source repositories and trademark records support public technical/IP activity.

Risks

  • Financial statements, ARR/revenue, gross margin, burn, cash, debt, backlog and runway are not public.
  • L2BEAT flags technical/centralization risks including no exit window for unwanted upgrades, permissioned roles and a 2026 outage.
  • STRK token economics, cross-chain token use, staking/governance and global user access create regulatory and compliance diligence needs.

Gaps

  • Audited financial statements, management accounts, ARR/revenue, gross margin, burn, cash, debt, backlog, tax positions and runway.
  • Capitalization, option/warrant/note schedules, investor rights, token treasury/allocation, foundation/company economics and current valuation bridge.
  • Customer revenue, top-account concentration, signed StarkEx/Starknet commercial agreements, churn, retention and customer references.
  • Security audits, incident history, key-management controls, bridge/prover/sequencer runbooks and decentralization milestones.
  • Counsel-reviewed legal schedule covering token, securities, sanctions/AML, IP, open-source, employment, privacy, litigation, insurance and material contracts.

Recommended next steps

  • Run finance/cap-table/token-treasury diligence before relying on the $8.0B valuation anchor.
  • Conduct independent technical/security review of Starknet, StarkEx, SHARP/Stwo, bridges, sequencer/prover operations and incident response.
  • Validate top customers, partner economics, revenue recognition, retention and commercial pipeline through contracts and reference calls.
  • Have counsel review token/regulatory, sanctions/AML, litigation, IP/open-source, data/privacy and cross-border operational exposure.

Risk register

high high likelihood

R-001: Financial opacity and valuation support gap

StarkWare is private and public sources do not disclose audited financials, revenue, margin, burn, cash, debt, tax or runway; the $8.0B valuation cannot be underwritten publicly.

Diligence request: Request audited financials, management accounts, bank/debt schedules, tax positions, ARR/revenue bridge, revenue recognition policies and valuation support.

high high likelihood

R-003: Customer/revenue concentration unknown

Public customer logos and L2 metrics do not disclose paying customer revenue, top-account concentration, churn, retention, pricing or contract renewals.

Diligence request: Request top-15 customer revenue, signed contracts, churn/cohort data, pipeline, reference calls and product-level gross margin.

high medium likelihood

R-002: Financing, token and preference-stack overhang

Public unicorn valuation coexists with undisclosed equity/token rights, investor protections, employee options and STRK/foundation economics.

Diligence request: Request cap table, option/warrant/note schedules, investor side letters, token allocation/treasury, foundation/company agreements and transfer restrictions.

high medium likelihood

R-004: Protocol security, bridge and centralization risk

Starknet/StarkEx rely on complex validity proofs, bridges, sequencers, provers and upgrades; L2BEAT flags no exit window, permissioned roles and an outage.

Diligence request: Run independent security/architecture review, audit remediation review, incident-history review and decentralization milestone testing.

high medium likelihood

R-005: Token, securities, sanctions/AML and cross-border regulatory exposure

STRK distribution, fees, governance, future staking and cross-chain token liquidity create regulatory ambiguity across jurisdictions.

Diligence request: Request legal memos on token status, sanctions/AML/geofencing, exchange listings, staking, governance, tax, consumer protection and foundation/company roles.

medium high likelihood

R-006: Competition and pricing pressure in Ethereum scaling

StarkWare competes with other ZK/optimistic rollups and app-chain/zkVM providers; differentiation may erode as tooling and proof systems mature.

Diligence request: Benchmark win/loss, cost, reliability, developer adoption, liquidity and enterprise economics against zkSync, Scroll, Polygon, Arbitrum, Optimism and emerging zkVM stacks.

medium medium likelihood

R-007: Key-person and R&D talent concentration

Technical moat appears tied to cryptography/prover expertise and public founder/researcher credibility; current management/org chart and retention are not public.

Diligence request: Request current org chart, management bios, retention plans, succession/key-person coverage, attrition and compensation/equity plans.

medium medium likelihood

R-008: IP, open-source and trademark chain-of-title risk

Open-source Cairo/Stwo assets and trademarks are public, but proprietary IP assignments, patent strategy, license compliance and dependency obligations are not public.

Diligence request: Request IP schedule, invention assignments, patent/trademark official records, OSS SBOM, license review and contributor assignment policy.

Chapter 01

01Financial Information

Public sources support unicorn/valuation anchors and token/network signals, but company financial statements, revenue, runway, cap table, debt, tax, customer economics and projections are private.

I.A Annual and quarterly financial information for the past three years

not publicly verifiable confidence: high

No audited or management financial statements were public. Only network/protocol metrics and product descriptions provide indirect signals.

Evidence gaps

  • Audited income statements, balance sheets, cash flows, footnotes, management reports, revenue breakdowns, backlog and AR aging.

Hidden risks

  • Protocol activity could mask weak company monetization or high support/prover costs.

Follow-up questions

  • Provide audited and management financial statements for 2023-2026 YTD plus revenue by product, customer, channel and geography.
Public financial, revenue and unit-economic signals
signalpublic evidenceverification statusunderwriting gap
Company revenue/ARR/gross marginNo audited financials or revenue by product/customer located in reviewed public sources.not_publicly_verifiableAudited financial statements, revenue recognition policy and product/customer revenue bridge.
Network activity proxyL2BEAT reported 646.20K past-day Starknet operations and $0.000101 average L1 cost per L2 UOP.verifiedTranslate network operations into StarkWare revenue, fees, token economics and margin.
StarkEx enterprise/SaaS pricingStarkEx product page describes SaaS/features but no price card or customer economics.not_publicly_verifiableSigned contracts, minimums, usage fees, renewal terms and gross margin.
Runway/cash/debt/taxNot disclosed in reviewed public sources.not_publicly_verifiableBank statements, debt schedules, tax filings, cash forecast and board-approved plan.

Network metrics are not company financials.

I.B Financial Projections

not publicly verifiable confidence: high

No public projections were found. Public growth drivers are Starknet/StarkEx adoption, STRK ecosystem and STARK R&D, but predictability and financing assumptions are private.

Evidence gaps

  • Three-year quarterly plan, scenario sensitivities, token/equity economics, foreign exchange and regulatory assumptions.

Hidden risks

  • Crypto-cycle volatility, token incentives and protocol fees could make forecasts less predictable than product activity suggests.

Follow-up questions

  • Provide board-approved model with downside/base/upside cases and reconciliation to protocol metrics.

I.C Capital Structure

partially verified confidence: medium

Investor names and valuation anchors are public, but share count, option/warrant/note schedules, preference stack, debt and token allocations are not public.

Evidence gaps

  • Cap table, option plan, token allocation, investor rights, debt/off-balance sheet liabilities.

Hidden risks

  • Equity/token/foundation economics could create hidden dilution, tax or control issues.

Follow-up questions

  • Provide fully diluted cap table, token treasury/allocation/unlocks and all financing/debt instruments.
Capital structure and ownership snapshot
stakeholder or instrumentpublic positionverification statusdiligence caveat
Named venture investorsCB extract lists Sequoia Capital, Paradigm and Pantera Capital.partially_verifiedOwnership percentages, preferences, board rights and side letters are private.
Founders / early teamWikipedia row lists Eli Ben-Sasson, Michael Riabzev, Uri Kolodny and Alessandro Chiesa.partially_verifiedCurrent holdings, roles, vesting and assignment agreements require company records.
STRK / Starknet Foundation economicsFoundation announced STRK distribution and uses; company/foundation economic relationship not public.partially_verifiedRequest token treasury, allocation, unlocks, governance, service agreements and tax/legal opinions.
Debt, warrants, options, SAFEs/notesNo complete public schedule found.not_publicly_verifiableRequest capitalization waterfall and all dilutive instruments.

I.D Other financial information

partially verified confidence: medium

Public valuation anchors exist, but tax positions, accounting policies and full financing history require private records.

Evidence gaps

  • Tax positions, revenue recognition, financing history with ownership percentages and current basis by round.

Hidden risks

  • Stale valuation could obscure down-round, secondary, token or preference-stack risks.

Follow-up questions

  • Provide complete financing history, valuation reports, 409A/tax records and accounting policy memos.
Public funding and valuation anchors
dateeventamount or valuationparticipants or sourceverification statusdiligence caveat
2021-11-17CB Insights unicorn-club entry/current valuation anchor$8.0B valuation; round amount not provided in promptCB Insights extract; investors listed as Sequoia Capital, Paradigm, Pantera Capitalpartially_verifiedRequest financing documents and current valuation bridge.
2022-05Wikipedia unicorn table valuation row$8B valuationWikipedia row citing Forbes; founders listed in rowpartially_verifiedSecondary source; verify against company board/investor records.
Prior roundsSeed/Series funding history before unicorn valuationNot fully reconstructed from accessible public sources in this runNot publicly verified in reviewed sourcesnot_publicly_verifiableRequest complete equity, SAFE/note, warrant and token financing history.

Only public anchors are shown; no cap-table math should be inferred.

StarkWare public valuation and activity timeline Timeline of public valuation/status anchors and selected post-valuation activity signals.
Public valuation trajectory and missing financing data Chart of public valuation anchors with null markers for undisclosed prior/current valuations.
Chapter 02

02Products

StarkWare publicly offers Starknet, StarkEx, Cairo and STARK prover technology. The product claims are well documented, but pricing, SLAs, security assurance, customer economics and decentralization milestones require deeper review.

II.A Description of each product

partially verified confidence: high

Starknet and StarkEx are clearly described public products, supported by Cairo and Stwo/SHARP. Product economics and independent performance/security validation remain open.

Evidence gaps

  • Product-level revenue/margin, roadmap timing/cost, security audits, incident history, SLAs and customer support obligations.

Hidden risks

  • Bridge/prover/sequencer bugs, upgrade controls, data-availability assumptions and enterprise SLAs could create high-severity exposure.

Follow-up questions

  • Provide product P&L, roadmap, audit reports, penetration tests, incident log, SLA obligations and customer deployment matrix.
Product and SKU matrix
productaudiencekey featuresverification statusdiligence gap
StarknetDevelopers, dApps, validators/users in Ethereum ecosystemPermissionless decentralized validity rollup; smart contracts; scale for dApps.verifiedIndependent performance, uptime, decentralization and revenue conversion.
StarkExApp-specific exchanges, NFT, payments and DeFi operatorsStandalone validity-rollup SaaS with rollup/validium data availability, high throughput, low gas, self-custody.verifiedCustomer contracts, deployment list, SLAs, pricing and support obligations.
CairoDevelopers building provable programs and Starknet contractsTuring-complete language for provable programs; powers Starknet/StarkEx per homepage.verifiedDeveloper adoption, support burden and language/compiler risk.
SHARP / Stwo / Stone ProverStarkWare proof infrastructure and downstream STARK systemsProduction-grade Circle STARK prover/verifier; powers SHARP and Starknet according to README.verifiedProduction deployment scope, audit status, cost curves and migration risk.
Pricing and economic model comparison
offeringpublic pricing signalcomparison pointverification status
Starknet network usageL2BEAT reported average L1 cost per L2 UOP of $0.000101 over its displayed window.Protocol/network cost proxy, not company price.verified network metric; revenue not_publicly_verifiable
StarkEx SaaSNo public price card found on product page.Enterprise app-specific rollup pricing likely contract-specific.not_publicly_verifiable
Competitor L2s / rollup ecosystemsPublic fee dashboards exist at protocol level but company economics vary.Compare total cost, proof cost, liquidity, developer tooling and enterprise support.partially_verified; requires benchmark
StarkWare product architecture and dependency map High-level public architecture derived from StarkWare product pages and L2BEAT.
Chapter 03

03Customer Information

Public customer evidence is limited to testimonials/logos, Starknet network metrics and ecosystem relationships. Top-customer revenue, concentration and severed relationships are not public.

III.A Top customers by application

partially verified confidence: medium

Five StarkEx testimonial/logo signals were observed, but top-15 customer revenue and purchase timing are private.

Evidence gaps

  • Top-15 customers by year, product/application, contract values, renewal status and ownership/timing of purchases.

Hidden risks

  • Public logos may be stale or non-revenue; one or two large deployments could dominate revenue.

Follow-up questions

  • Provide top-customer schedule and allow reference calls with current production customers.
Publicly known customers and ecosystem use cases
customer or logouse casesource quote or signalverification statusrevenue gap
ImmutableNFT trading and minting scalingImmutable testimonial says it needed to scale NFT trading and minting.partially_verifiedContract value, renewal and current production status not public.
SorareStarkEx customer testimonial/logoListed on customer testimonials page.partially_verifiedRevenue and active use not public.
dYdXStarkEx customer testimonial/logoListed on customer testimonials page.partially_verifiedCurrent economics after dYdX product migrations require confirmation.
rhino.fiStarkEx customer testimonial/logoListed on customer testimonials page.partially_verifiedRevenue and active use not public.
ApeX (Davion Labs)StarkEx customer testimonial/logoListed on customer testimonials page.partially_verifiedRevenue and active use not public.
Starknet users/dAppsNetwork activityL2BEAT reported 646.20K past-day operations.verified network metricUser operations do not equal StarkWare customer revenue.

III.B Strategic relationships

partially verified confidence: medium

Public relationships include Starknet Foundation/token activity, Ethereum settlement, NEAR/Solana token interoperability and research collaboration signals.

Evidence gaps

  • Revenue contribution, marketing agreements, foundation/company services, liquidity-provider terms and partner contracts.

Hidden risks

  • Foundation/company economics and partner agreements may contain hidden obligations or compliance duties.

Follow-up questions

  • Provide all strategic partnership, foundation, token-liquidity, research and ecosystem grant agreements.
Strategic relationships and partnerships
relationshipnaturepublic evidencediligence gap
Starknet FoundationToken distribution, governance and ecosystem roleFoundation announced STRK distribution and use for fees/governance/future staking.Company/foundation agreements, economics, governance authority and liabilities.
NEAR Intents / Solana / Meteora / JupiterSTRK token interoperability/liquiditySTRK page describes native Solana availability via NEAR Intents and mentions Meteora/Jupiter.Commercial terms, compliance controls, liquidity quality and custody/bridge risk.
EthereumSettlement/data availability/verifier layer for Starknet/StarkEx systemsL2BEAT says ZK proofs are verified on Ethereum and data is published on-chain.Ethereum fee sensitivity, outage/upgrade dependencies and emergency procedures.
Polygon Labs / Circle STARK researchResearch collaboration signalHomepage references Circle STARKs collaboration between StarkWare and Polygon labs.IP ownership, publication rights and commercialization.

III.C Revenue by customer

not publicly verifiable confidence: high

No customer revenue or concentration data is public. L2BEAT network activity is not a substitute for company revenue.

Evidence gaps

  • Revenue by customer/product, customers above 5% revenue, churn/retention, backlog and cohort expansion.

Hidden risks

  • Underwriting could overvalue protocol usage that does not accrue to StarkWare.

Follow-up questions

  • Provide revenue concentration schedule and customer-by-customer ARR/NRR/churn bridge.
Public customer and partner signal count Bar chart uses public-evidence counts, not revenue weights, because revenue concentration is private.

III.D Significant relationships severed within the last two years

not publicly verifiable confidence: high

No public schedule of severed customer/partner/supplier relationships was found.

Evidence gaps

  • Terminated customers, lost partners, supplier disputes and reasons for churn.

Hidden risks

  • Lost flagship customers or migrations could materially impair revenue despite stale testimonials.

Follow-up questions

  • Provide churn/lost-logo schedule and list any significant severed relationships since 2024.

III.E Top suppliers

partially verified confidence: medium

Public dependencies include Ethereum, sequencer/prover/operator stack, GitHub and undisclosed cloud/security vendors.

Evidence gaps

  • Top suppliers by spend, SLAs, cloud architecture, security vendors, contingency plans and bridge/operator runbooks.

Hidden risks

  • Single points of failure in proving, sequencing, bridges, cloud or security vendors could disrupt service.

Follow-up questions

  • Provide supplier spend schedule, vendor contracts, SOC reports, incident runbooks and DR plans.
Supplier and infrastructure dependency map
dependencyrolepublic evidenceconcentration risk
Ethereum L1Settlement, verifier and data availability layerL2BEAT says proofs verified on Ethereum and data published on-chain.High dependency on Ethereum fees, finality and contract upgrades.
Sequencer/prover/operator stackTransaction ordering, proof generation, state updatesStarkEx page and L2BEAT describe operator/prover/whitelisted proposer roles.Operational outage, censorship or frozen withdrawals if permissioned roles fail.
GitHub/open-source infrastructurePublic code hosting and developer channelstarkware-libs repositories are public and active.Repository governance, supply-chain security and contributor controls.
Cloud/hosting/security vendorsCorporate and production infrastructureSpecific vendor spend and contracts not publicly disclosed.Request vendor list, SOC reports, SLAs, DR and key-management controls.
Chapter 04

04Competition

StarkWare has credible public technical differentiation in STARK/Cairo/Stwo, but competition in Ethereum scaling and ZK infrastructure is intense and economic differentiation is not publicly proven.

IV.A Competitive landscape by market segment

partially verified confidence: medium

Competition centers on proof model, EVM compatibility, liquidity/network effects, security/decentralization, developer tooling and enterprise economics.

Evidence gaps

  • Win/loss data, pricing benchmarks, developer cohort metrics, market share, customer references and competitor cost curves.

Hidden risks

  • EVM-compatible competitors may win developers/liquidity despite StarkWare proof technology; token incentives can distort apparent adoption.

Follow-up questions

  • Provide competitive win/loss, benchmark analysis and product-market fit metrics by developer/customer segment.
Competitor comparison matrix
competitorproduct overlaptarget differentiatorsource or basisdiligence question
Matter Labs / zkSyncZK Ethereum scaling network and developer ecosystemStarknet/Cairo/STARK proof stack and StarkEx app-specific historyAnalyst market map using L2BEAT category and public product sourcesCompare fees, TVL, users, developer tooling, security and decentralization.
ScrollEthereum zkEVM rollupStarknet uses Cairo/STARK architecture rather than EVM-equivalent positioningAnalyst market map using public L2 competitor contextDoes Cairo differentiation help or hurt developer adoption versus EVM compatibility?
Polygon zkEVM / AggLayer / Polygon CDKZK scaling, proof systems, app-chain infrastructureCircle STARK research signal and Starknet/StarkEx installed baseStarkWare homepage notes Circle STARKs collaboration with Polygon labsClarify collaboration vs competition and IP/commercial boundaries.
Arbitrum / Optimism / BaseEthereum L2 scaling and liquidity ecosystemsValidity proofs vs optimistic rollup architectureL2Beat classifies Starknet as ZK Rollup; broader L2 market contextCan StarkWare overcome liquidity/network effects of larger optimistic rollups?
RISC Zero, Succinct, zkVM/prover stacksProof generation and verifiable computation infrastructureProduction STARK rollup/prover deployments and Cairo ecosystemStwo README and GitHub open-source evidenceBenchmark proof cost, developer adoption and enterprise/commercial model.
Basis of competition scoring
axisstarkware public positiontop competitor positionevidence strengthfollow up
Proof technology depthStrong public STARK/Cairo/Stwo evidenceOther ZK teams also investing heavilymedium-highBenchmark proof cost and audit posture.
Developer compatibilityCairo-specific architectureEVM-equivalent/EVM-compatible rollups reduce switching costsmediumMeasure developer acquisition, conversion and retention.
Security/decentralizationValidity proofs and on-chain data, but Stage 1/no exit window/permissioned rolesVaries by L2; mature rollups compete on decentralization milestoneshighReview roadmap to permissionless sequencing/proving and exit guarantees.
Commercial monetizationStarkEx SaaS and Starknet ecosystem but pricing/revenue not publicToken ecosystems and infrastructure providers compete on fees and grantslowRequest company financials and contract-level economics.
Ethereum scaling competitive map Qualitative market map for public competitors and adjacent proof infrastructure.
Chapter 05

05Marketing, Sales, and Distribution

Public GTM signals are strongest in developer/community, customer testimonials and token ecosystem distribution. Sales productivity, pipeline and marketing ROI are private.

V.A Strategy and implementation

partially verified confidence: medium

StarkWare uses developer docs/GitHub, StarkEx enterprise positioning, testimonials, token/community programs and research thought leadership.

Evidence gaps

  • Marketing budgets, channel ROI, sales pipeline, regional distribution plans and compliance controls.

Hidden risks

  • Developer activity and token distribution can be high while paid pipeline or retention is weak.

Follow-up questions

  • Provide GTM plan, marketing budget/ROI, channel metrics and compliance review for token/community campaigns.
Distribution channels and GTM motions
channelmotionpublic evidencemetric gap
Developer ecosystemDocs, GitHub, Cairo/Starknet toolingDocs repository says official documentation hub; GitHub repos are active.Developer signups, activation, retention and support cost.
Enterprise/app-specific salesStarkEx SaaS for exchanges/NFT/DeFi operatorsStarkEx product and testimonials list use cases/customers.Pipeline, sales cycle, pricing, quota productivity and renewal rates.
Foundation/token communitySTRK distribution, governance, staking narrativeProvisions Program distributes STRK and describes governance/fees/staking.Company attribution, CAC, compliance controls and durable usage.
Thought leadership/events/researchBlogs, STARK research, Bitcoin/Ethereum scaling narrativeHomepage highlights Stwo, Circle STARKs and Bitcoin scaling posts.Lead generation, conversion and brand ROI.
Public marketing-signal summary
signalobserved valueverification statusinterpretation
Customer testimonialsFive named StarkEx testimonial/logos observedpartially_verifiedHelpful credibility, but current paid status and revenue unknown.
Open-source starscairo repository showed 1,890 stars; stwo showed 494 stars in GitHub search results.verified point-in-timeDeveloper awareness signal, not revenue.
Docs channelStarknet docs repo describes official hub and automatic docs deployment.verifiedSupports self-serve developer distribution.
Token/community distributionProvisions Program distributed >700M STRK to nearly 1.3M addresses.verifiedLarge reach, but may create token/regulatory and incentive-quality risks.

V.B Major Customers

not publicly verifiable confidence: high

Major customer status and pipeline are not public beyond testimonials/logos.

Evidence gaps

  • Pipeline by stage, customer health, expansion/renewal plans and reference calls.

Hidden risks

  • Stale logos may inflate perceived traction.

Follow-up questions

  • Provide customer pipeline, health scores, renewal calendar and NRR/GRR.

V.C Principal avenues for generating new business

partially verified confidence: medium

Principal public avenues are developer self-serve docs/open source, StarkEx enterprise sales, token/community programs and research events/content.

Evidence gaps

  • CAC, conversion, developer funnels, enterprise pipeline, grant spend and payback.

Hidden risks

  • Open-source/community channels may not convert into durable company economics.

Follow-up questions

  • Provide funnel metrics from developer awareness through paid deployment/customer revenue.
Public GTM signal mix Bar chart of observable GTM signals from public sources.

V.D Sales force productivity model

not publicly verifiable confidence: high

No sales compensation, quota, sales cycle or new-hire productivity model is public.

Evidence gaps

  • Sales org, quotas, compensation, pipeline, conversion, sales cycle and implementation capacity.

Hidden risks

  • Complex enterprise deployments may create long sales cycles and implementation risk.

Follow-up questions

  • Provide sales-force roster, quota attainment, pipeline conversion and implementation backlog.

V.E Ability to implement marketing plan with current and projected budgets

not publicly verifiable confidence: high

Marketing budget sufficiency cannot be assessed publicly.

Evidence gaps

  • Budget, headcount, agency/vendor contracts and campaign ROI.

Hidden risks

  • Underfunded GTM could limit commercialization despite technical credibility.

Follow-up questions

  • Provide current and projected GTM budget with ROI and hiring assumptions.
Chapter 06

06Research and Development

Public R&D evidence is a relative strength: Cairo/Stwo repositories, STARK research, prover roadmap and Starknet/StarkEx architecture. The main diligence gaps are R&D cost, security audits, IP ownership and roadmap execution risk.

VI.A Description of R&D organization

partially verified confidence: medium

Public sources show founder/researcher context, GitHub activity and limited engineering leadership signals, but not budget or full org structure.

Evidence gaps

  • R&D headcount, budget, roadmap staffing, key-person dependencies and contractor/vendor mix.

Hidden risks

  • R&D concentration in a small number of cryptography experts could create key-person and recruiting risk.

Follow-up questions

  • Provide R&D org chart, roadmap, budget, hiring plan, attrition and key-person retention strategy.
Public R&D personnel and leadership signals
name or rolepublic role signalsourceverification statusdiligence caveat
Eli Ben-SassonListed by Wikipedia row as a StarkWare Industries founderWikipedia unicorn list rowpartially_verifiedCurrent title, employment agreement, ownership and time allocation require company confirmation.
Michael RiabzevListed by Wikipedia row as a founderWikipedia unicorn list rowpartially_verifiedCurrent role and IP assignments require confirmation.
Uri KolodnyListed by Wikipedia row as a founderWikipedia unicorn list rowpartially_verifiedCurrent role and departure/transition status require confirmation.
Alessandro ChiesaListed by Wikipedia row as a founderWikipedia unicorn list rowpartially_verifiedCurrent role, advisor/employment relationship and IP assignment require confirmation.
Gideon KaempferCareers page identifies VP EngineeringStarkWare careerspartially_verifiedConfirm current role, reporting line and retention.

VI.B New Product Pipeline

partially verified confidence: medium

Public pipeline themes include Stwo, Circle STARKs, Bitcoin/Ethereum settlement narrative and sequencer/staking decentralization; costs and timing are not public.

Evidence gaps

  • Product roadmap, R&D cost, launch criteria, security audit/remediation, benchmarks and decentralization milestones.

Hidden risks

  • Research breakthroughs may not translate to low-cost, secure, decentralized production systems on schedule.

Follow-up questions

  • Provide product pipeline, milestones, budget, technical risk register, audits, incident response and performance benchmarks.
Public R&D and product pipeline
projectpublic statusexpected impactverification statusfollow up
Stwo proverREADME says production and powering SHARP/Starknet; homepage calls it next-gen scaling.Lower proof cost and core technical differentiation.partially_verifiedAudit reports, benchmarks, deployment logs and migration plan.
Circle STARKsHomepage references collaboration with Polygon labs and paper.Faster/cheaper STARK proofs; research moat.partially_verifiedIP rights, implementation roadmap and third-party validation.
Bitcoin/Ethereum settlement visionHomepage says Starknet can become a single layer settling on both Bitcoin and Ethereum.Expanded market narrative and technical complexity.unverified roadmap claimMilestones, technical dependencies, regulatory and security review.
Decentralized sequencing/stakingProvisions Program states future staking in a PoS model to choose decentralized sequencers.Decentralization improvement and token utility.partially_verifiedTimeline, security model, slashing, governance and compliance opinions.
R&D portfolio and proof-stack map Map public R&D assets to product outcomes and technical diligence needs.
Chapter 07

07Management and Personnel

Public management/personnel evidence is incomplete. Founder and limited engineering signals are visible, but full org chart, headcount, compensation, equity plans, turnover and employee-relations records require private diligence.

VII.A Organization Chart

not publicly verifiable confidence: medium

Only a partial public org placeholder can be built from founder and limited careers-page signals.

Evidence gaps

  • Current org chart, reporting lines, board/advisor list, key vacancies and succession plans.

Hidden risks

  • Hidden gaps in leadership depth, succession and accountability may exist.

Follow-up questions

  • Provide current org chart and leadership roster with reporting lines.
Public management/org-chart placeholder Org chart built only from public founder and limited careers-page signals; reporting lines are not verified.

VII.B Historical and projected headcount by function and location

not publicly verifiable confidence: medium

Careers page supports activity but does not disclose headcount or hiring plan.

Evidence gaps

  • Historical/projected headcount by function/location, hiring plan, attrition and contractor mix.

Hidden risks

  • Talent shortfalls could delay R&D, security, compliance or enterprise sales commitments.

Follow-up questions

  • Provide HRIS exports, recruiting pipeline and hiring budget.
Headcount and hiring signals
function or regionpublic signalverification statushr gap
Israel / remote hiringCareers page shows Open Positions context and Israel Remote text.partially_verifiedCurrent requisition list, headcount by function/location, hiring plan and attrition.
Engineering/R&DCareers page names VP Engineering and software team leads; GitHub repos show active public engineering.partially_verifiedEngineering headcount, contractor mix, key-person dependencies and retention.
Sales/marketing/customer successNo public sales-force roster or productivity model identified.not_publicly_verifiableSales org chart, quota, compensation, pipeline and customer-success coverage.
Legal/compliance/securityNo public staffing plan or compliance team roster identified.not_publicly_verifiableCompliance/security org chart, counsel relationships and regulatory coverage.
Headcount and hiring public anchor chart Chart shows absence of public headcount trend data and one hiring/activity anchor from careers/GitHub.

VII.C Senior management biographies

partially verified confidence: medium

Founders are listed in a secondary public unicorn row and limited engineering leaders appear on careers page; current bios/tenure are incomplete.

Evidence gaps

  • Management biographies, employment history, tenure, current titles, board roles and key-person arrangements.

Hidden risks

  • Outdated public founder/role data could obscure current leadership transitions.

Follow-up questions

  • Provide current management bios and employment agreements.
Senior management and public role roster
person or grouppublic role or signalsourcecurrent statusfollow up
Eli Ben-SassonFounder listed in public unicorn row; appears in StarkWare/Starknet public thought leadership snippets.Wikipedia row; homepage news snippet references Eli Ben-Sassonpartially_verifiedConfirm current title, authority, board role and compensation.
Michael RiabzevFounder listed in public unicorn rowWikipedia rowpartially_verifiedConfirm current role, IP assignment and retention.
Uri KolodnyFounder listed in public unicorn rowWikipedia rowpartially_verifiedConfirm current role/transition status and equity/consulting arrangements.
Alessandro ChiesaFounder listed in public unicorn rowWikipedia rowpartially_verifiedConfirm advisor/employment status and IP arrangements.
Engineering leadershipCareers page names Gideon Kaempfer as VP Engineering and two software team leadsCareers pagepartially_verifiedRequest current org chart and management biographies.

VII.D Compensation arrangements

not publicly verifiable confidence: high

Compensation and benefits arrangements are not public.

Evidence gaps

  • Employment agreements, executive compensation, benefits, severance, retention and bonus plans.

Hidden risks

  • Retention or severance obligations may be material.

Follow-up questions

  • Provide compensation and benefits schedules, employment agreements and severance/retention obligations.

VII.E Incentive stock plans

not publicly verifiable confidence: high

Incentive equity/token plans are not public.

Evidence gaps

  • Equity incentive plans, grant schedules, token grants, strike prices and vesting.

Hidden risks

  • Unseen token/equity incentives may dilute investors or create retention cliffs.

Follow-up questions

  • Provide fully diluted equity and token incentive schedules.

VII.F Significant employee relations problems, past or present

not publicly verifiable confidence: high

No public employee-relations schedule was available.

Evidence gaps

  • Complaints, settlements, investigations, labor law matters and policy compliance.

Hidden risks

  • Undisclosed HR disputes or compliance issues could affect retention and liabilities.

Follow-up questions

  • Provide employee-relations legal/HR schedule and policy attestations.

VII.G Personnel Turnover

not publicly verifiable confidence: high

Turnover metrics were not public.

Evidence gaps

  • Turnover by function/location, regretted attrition, exit themes and retention plans.

Hidden risks

  • R&D or leadership churn could impair roadmap delivery.

Follow-up questions

  • Provide attrition analysis and retention plan.
Public turnover and employee-relations signals
itempublic evidenceverification statusfollow up
Founder/leadership transitionsReviewed sources did not provide a complete current management/transition history.not_publicly_verifiableRequest leadership transition memos, current roster and board minutes.
Employee turnover last two yearsNo public turnover statistics found.not_publicly_verifiableRequest attrition by function/location, regretted attrition, offer acceptance and employee engagement results.
Employee relations problemsNo public employee-relations matter schedule found in reviewed sources.not_publicly_verifiableRequest HR/legal schedule, complaints, settlements and works council/labor issues if any.
Chapter 08

08Legal and Related Matters

Public legal diligence found trademark/open-source signals, STRK/token regulatory exposure, L2 protocol risk and CourtListener docket mentions. No counsel-certified litigation, insurance, regulatory, material-contract or IP schedule is public.

VIII.A Pending lawsuits against the Company

inconclusive confidence: medium

CourtListener search produced StarkWare mentions but did not verify a schedule of pending lawsuits against StarkWare.

Evidence gaps

  • Counsel-certified litigation schedule, official docket searches, claims/indemnity schedule and bankruptcy counterparty exposure.

Hidden risks

  • Third-party bankruptcy/investor proceedings could involve StarkWare shares/tokens or transfer restrictions.

Follow-up questions

  • Have counsel run docket searches in relevant jurisdictions and provide litigation/claims schedule.
Pending lawsuits against the company - public search summary
matter or search resultpublic signalcompany roleverification status
CourtListener StarkWare search13 cases and 119 docket entries matched StarkWareMostly snippet mentions; direct defendant status not verifiedinconclusive; counsel search required
Three Arrows Capital bankruptcy snippetsSnippets refer to Starkware tokens/investmentsInvestment/counterparty reference, not lawsuit against StarkWare from snippetinconclusive; review claims/transfer restrictions
Genesis/FTX/Maclaurin snippetsSnippets reference StarkWare shares/tokens or schedulesThird-party asset/collateral referencesinconclusive; request legal schedule and investor records
Company-provided litigation scheduleNot publicUnknownnot_publicly_verifiable; request counsel letter
Legal, token and IP timeline Timeline of public legal/IP/token events and search findings.

VIII.B Pending lawsuits initiated by Company

not publicly verifiable confidence: medium

No public plaintiff-side litigation schedule was found.

Evidence gaps

  • Plaintiff claims, arbitrations, IP oppositions and settlement agreements.

Hidden risks

  • Unseen disputes may affect IP, customers or suppliers.

Follow-up questions

  • Provide litigation and dispute schedule for company-initiated matters.
Pending lawsuits initiated by the company - public search summary
categorypublic evidenceverification status
StarkWare as plaintiff/claimantNo verified public schedule of lawsuits initiated by StarkWare was located from reviewed search snippets.not_publicly_verifiable; run counsel-led docket search
IP enforcement/oppositionsTrademark aggregator shows marks but no enforcement schedule.not_publicly_verifiable; request IP litigation/opposition docket
Contract disputes/arbitrationsNo public arbitration or contract-dispute schedule found.not_publicly_verifiable; request material disputes schedule

VIII.C Environmental and employee safety issues and liabilities

not publicly verifiable confidence: low

No environmental or workplace safety records were public for a software/blockchain infrastructure company.

Evidence gaps

  • Workplace safety policies, facilities leases, insurance and local compliance records.

Hidden risks

  • Office/facility and employee safety compliance can still create local liabilities.

Follow-up questions

  • Provide EHS/safety policies and any claims or inspections.

VIII.D Material patents, copyrights, licenses, and trademarks

partially verified confidence: medium

Public IP evidence includes live/dead trademark aggregator records and Apache-licensed open-source repositories; official IP ownership and license compliance require counsel.

Evidence gaps

  • Official USPTO/WIPO trademark records, patent schedule, invention assignments, OSS SBOM/license review and copyright registrations.

Hidden risks

  • IP assignment gaps, OSS license conflicts or unfiled patents could weaken defensibility.

Follow-up questions

  • Provide complete IP schedule, official trademark/patent records and OSS compliance memo.
Material IP, trademarks, copyrights and licenses
assetjurisdiction or repositorystatussourcediligence request
STONE PROVERU.S. trademark aggregatorLIVE serial 79398152 per TrademarkEliteTrademarkEliteVerify official USPTO/WIPO status and ownership.
STARKGATEU.S. trademark aggregatorLIVE serial 79375465 per TrademarkEliteTrademarkEliteVerify official records and assignment chain.
STARKEX / CAIRO / STARKWAREU.S. trademark aggregatorLive entries reported; one dead STARKWARE entry also reportedTrademarkEliteObtain global trademark schedule and prosecution history.
Cairo repositoryGitHubApache 2.0 public repository; Cairo language for provable programsGitHub README/searchOSS license/SBOM, contributor assignments, dependency review.
Stwo repositoryGitHubApache 2.0 public repository; production-grade Circle STARK prover/verifierGitHub READMEAudit reports, security policy, commercialization/IP boundary.

VIII.E Insurance coverage and material exposures

not publicly verifiable confidence: high

Insurance policies are not public.

Evidence gaps

  • Insurance policies, limits, exclusions, claims history and broker letters.

Hidden risks

  • Coverage exclusions for digital assets, sanctions, bridges or protocol failures could be material.

Follow-up questions

  • Provide insurance schedule and claims history.

VIII.F Material contracts

not publicly verifiable confidence: high

Customer, supplier, investor, foundation, token, liquidity-provider and employment contracts are not public.

Evidence gaps

  • Material contract list, customer/supplier/foundation/investor/token agreements and obligations summary.

Hidden risks

  • Hidden exclusivity, indemnity, termination, MFN, change-of-control or regulatory covenants may exist.

Follow-up questions

  • Provide material contracts and obligation matrix.

VIII.G Regulatory agency problems

partially verified confidence: medium

No specific regulatory enforcement action against StarkWare was verified publicly, but STRK token, global users, cross-chain liquidity and L2 bridge/governance design create regulatory and operational risk.

Evidence gaps

  • Regulatory correspondence, legal opinions, sanctions/AML policies, geofencing, token/staking memos and consumer-risk disclosures.

Hidden risks

  • Absence of public enforcement is not proof of clean regulatory status; token-related obligations may be jurisdiction-specific.

Follow-up questions

  • Have counsel review token, AML/sanctions, securities, tax, privacy and consumer-protection posture.
Regulatory, insurance, material-contract and operational exposure summary
exposurepublic signalriskverification status
Token/regulatorySTRK distribution, fees/governance/future staking and cross-chain Solana availability.Securities, commodities, sanctions/AML, tax and consumer-protection questions.partially_verified; request counsel memos
Protocol governance/upgradesL2BEAT flags permissioned roles, no exit window and emergency upgrade/bridge controls.User funds, liability and reputational risk if incidents occur.verified public risk; request controls/audits
InsuranceNo public insurance schedule found.Cyber, D&O, E&O, crime, token/bridge and litigation coverage unknown.not_publicly_verifiable; request policies
Material contractsCustomer, foundation, supplier, investor and token agreements are not public.Revenue recognition, exclusivity, indemnities, change-of-control and termination exposure.not_publicly_verifiable; request contract list
Risk heatmap for public-source diligence Heatmap of the top cross-functional risks identified in the report.

Evidence

Evidence claims
IDClaimStatusSources
EC-001 CB Insights extract identifies StarkWare as a private unicorn with $8.0B valuation, date joined 2021-11-17, Israel/Netanya location, Enterprise Tech industry and investors Sequoia Capital, Paradigm and Pantera Capital. partially verified medium SRC-001
EC-002 Wikipedia unicorn table lists StarkWare Industries at $8B in May 2022 in blockchain, Israel, with founders Eli Ben-Sasson, Michael Riabzev, Uri Kolodny and Alessandro Chiesa. partially verified medium SRC-002
EC-003 StarkWare publicly positions itself as a STARK proof pioneer with Starknet and StarkEx products. verified high SRC-003
EC-004 StarkEx publicly claims rollup/validium data availability, high throughput, low gas fees, Ethereum-level security, self-custody and an operator-to-StarkEx-prover/verifier workflow. verified medium SRC-004
EC-005 StarkWare customer testimonials publicly identify Immutable, Sorare, dYdX, rhino.fi and ApeX as testimonial/customer-logo signals. partially verified medium SRC-005
EC-006 StarkWare careers page describes the company as a well-funded Israeli deep-tech blockchain startup and shows active hiring context. partially verified medium SRC-006
EC-007 Starknet Foundation announced the STRK Provisions Program, distributing more than 700M STRK to nearly 1.3M addresses, with STRK intended for fees, governance and future staking. verified high SRC-007
EC-008 Starknet/STRK materials show cross-chain token expansion to Solana via NEAR Intents and include a no-investment/legal-advice disclaimer. verified medium SRC-008
EC-009 L2BEAT reports current Starknet operating metrics including 646.20K past-day operations, $51.34K annual L1 cost window and 100% normal uptime in the past 30 days, and classifies Starknet as Stage 1 ZK Rollup. verified high SRC-009
EC-010 L2BEAT flags centralization and operational risks for Starknet, including a 2026 outage, no exit window for unwanted upgrades and permissioned proposer/operator roles. verified high SRC-009
EC-011 starkware-libs/cairo is an active public repository for Cairo, described as the first Turing-complete language for creating provable programs; GitHub metadata showed 1,890 stars and update on 2026-06-13. verified high SRC-010SRC-011
EC-012 starkware-libs/stwo is public, Apache-licensed, described as production-grade Circle STARK prover/verifier and production technology powering SHARP/Starknet. verified high SRC-012
EC-013 TrademarkElite lists six U.S. trademarks filed by StarkWare Industries Ltd., including live STONE PROVER, STARKGATE, STARKEX, CAIRO and STARKWARE entries and one dead STARKWARE entry. partially verified medium SRC-013
EC-014 CourtListener search results for StarkWare show 13 cases and 119 docket entries, mostly third-party references such as Three Arrows, Genesis, FTX and other matters, not a verified schedule of lawsuits against StarkWare. inconclusive medium SRC-014
EC-015 StarkWare About Us and careers pages provide limited public team/advisor signals, but a full organization chart, current management roles, compensation and turnover data are not public. partially verified medium SRC-015SRC-006
EC-016 CB Insights maintains a StarkWare profile page titled products, competitors, financials, employees and headquarters locations, but detailed fields were not fully accessible in this run. inconclusive low SRC-016
EC-017 StarkWare homepage highlights ongoing R&D/news themes including Stwo Prover, Circle STARKs and a vision for Starknet settlement on Bitcoin and Ethereum. partially verified medium SRC-003
EC-018 The Starknet Docs repository describes itself as the official documentation hub for Starknet developers, validators and users, with automatic deployment to docs.starknet.io. verified medium SRC-017
EC-019 Public sources reviewed do not disclose audited financial statements, ARR/revenue, gross margin, backlog, customer concentration, cap table, debt, insurance, tax, HRIS or material contract schedules. not publicly verifiable high SRC-001SRC-003SRC-004SRC-005SRC-006SRC-009SRC-014
EC-020 L2BEAT reports Starknet publishes data needed to reconstruct state on-chain and verifies ZK proofs on Ethereum, but notes historical concerns about unverified bootloader programs and governance/upgrades. verified high SRC-009
Sources
IDPublisherTitleAccessed
SRC-001 CB Insights / workflow user-provided material User-provided CB Insights Global Unicorn Club extract for StarkWare 2026-06-14
SRC-002 Wikipedia Wikipedia: List of unicorn startup companies 2026-06-14
SRC-003 StarkWare StarkWare homepage 2026-06-14
SRC-004 StarkWare StarkEx product page 2026-06-14
SRC-005 StarkWare StarkWare customer testimonials 2026-06-14
SRC-006 StarkWare StarkWare careers page 2026-06-14
SRC-007 Starknet Foundation Starknet Provisions Program 2026-06-14
SRC-008 Starknet STRK is now natively accessible on Solana via NEAR Intents 2026-06-14
SRC-009 L2BEAT L2BEAT Starknet project profile 2026-06-14
SRC-010 GitHub GitHub search results for starkware-libs repositories 2026-06-14
SRC-011 GitHub / starkware-libs starkware-libs/cairo README 2026-06-14
SRC-012 GitHub / starkware-libs starkware-libs/stwo README 2026-06-14
SRC-013 TrademarkElite TrademarkElite StarkWare Industries Ltd. trademark owner profile 2026-06-14
SRC-014 CourtListener / Free Law Project CourtListener search results for StarkWare 2026-06-14
SRC-015 StarkWare StarkWare About Us page 2026-06-14
SRC-016 CB Insights CB Insights StarkWare company profile 2026-06-14
SRC-017 GitHub / starkware-libs starkware-libs/starknet-docs README 2026-06-14

Disclaimer

This report is a public-evidence diligence snapshot, not investment advice. Important financial, legal, technical, and contractual facts remain non-public and should be verified directly with management and primary documents before any investment decision.