初创公司尽调
尽调报告 Cybersecurity / Decentralized Identity / Blockchain Series A / token-network private company 2026-08-07

Humanity Protocol

具备真实品类延展空间的生物识别身份网络,但黑客事件后的信任折价很大,经济模型仍不透明。

Humanity Protocol 具备真实身份市场的期权价值和当前 token 市场相关性,但 2026 年攻击事件和缺失的财务披露,让结论只能停在继续研究;当前低于 $1B 的 FDV 只有在条件成立时才算合理。

封面要素

最近融资 / 融资基准 01
Series A $20M at $1.1B FDV [CO012, CV001]
公开披露融资额 04
50 USD M+ [CO013, CI011]
创始人 / CEO 05
Terence Kwok [CO007]
公开身份转化漏斗 06
7M+ Human IDs / ~10M wallets [CO019]

公司概况

Humanity Protocol 是一家总部位于香港的生物识别身份网络,公开由创始人兼 CEO Terence Kwok 领导。它的产品叙事覆盖 基于掌纹的真人证明验证、可复用凭证、面向开发者的身份基础设施,以及在教育、活动、机构加密工作流和反欺诈场景中的 伙伴分发。公开证据支持其融资动能和漏斗顶部采用具备实质规模,但经营业务的财务披露仍不足,2026 年 6 月攻击事件也 损伤了治理信心。

官网
www.humanityprotocol.com
创始人
Terence Kwok
总部
Hong Kong
产品
Humanity 销售一套真人证明栈,围绕掌纹生物识别、去中心化标识符、可验证凭证、开发者 API 和 SDK,以及支持验证者和 生态参与的代币化网络构建。
客户
创建 Human ID 的终端用户、集成身份检查的开发者、教育和活动生态,以及机构或金融分发伙伴,而不是一组已披露的直接 企业付费客户。
商业模式
公开材料暗示其模式混合了代币激励、验证者经济、开发者和生态活动,以及未来企业凭证或验证服务,但确切收费模式仍未披露。
阶段
Series A / token-network private company
融资情况
Humanity 披露 2024 年一轮 $30M 融资,估值 $1B;2025 年 1 月又披露 $20M Series A,完全稀释估值 $1.1B;公开融资额至少约 $50M。
[CO003, CO004, CO007, CO008, CO012, CO013, CO019, CI001]

执行摘要

主要优势

  • Humanity 所在的身份、反机器人和凭证验证赛道真实且在增长,欺诈和 AI 滥用让需求更急。
  • 产品不只是单一 token:它覆盖掌纹生物识别唯一性、可复用凭证、开发者工具和面向机构的业务通道。
  • 公开证据显示,公司在教育、活动、钱包、资金库工作流和开放金融愿景上有多个具名合作伙伴和分发通道。
  • 活跃 token 市场价格让投资者看到当前估值发现,而不只是过期的私募轮标记。

主要风险

  • 2026 年 6 月的特权密钥攻击留下持续的信任和治理折价,任何未来估值都必须消化。
  • 公开财务披露薄弱:没有可靠收入、利润率、留存、资金库或现金跑道视图。
  • 客户质量仍未被充分证明,因为最强公开证据大多由合作伙伴牵引,而不是直接合同收入证明。
  • Token 估值对稀释、供应治理和修复叙事高度敏感,而不是由可观察现金流基本面支撑。
  • 生物识别数据处理和跨境隐私义务带来的法律与声誉风险,高于一般 crypto token 项目。

未决问题

  • 当前收入、毛利率,以及企业或机构工作流是否产生有意义的经常性现金收入。
  • 资金库构成、解锁政策、token 销售治理,以及仍与 2026 年 6 月修复相关的任何储备或负债。
  • 黑客事件后的控制重构,包括密钥管理、签名人政策和特权访问加固的独立证据。
  • 具名合作伙伴和集成公告背后的直接客户转化、留存和合同深度。
  • 2026 年可靠员工数、组织架构图,以及公司和基金会实体之间的治理权利图谱。

目录

Chapter 01

01公司概览

1.1 身份、产品范围,以及 Humanity 为何存在

Humanity Protocol 更像是在把自己包装成一层信任基础设施,而不是单一应用。其当前主页称,网络能让机构、 品牌、开发者和用户在不存储敏感用户数据的前提下验证声明;协议和文档页面则把 Humanity 定义为一个可扩展的、 基于 EVM 的真人证明系统,核心是生物识别身份和零知识证明。产品定位覆盖市场两侧:企业和品牌获得保护隐私的 KYC、忠诚度、访问和欺诈工具,开发者获得抗女巫身份层,用户获得可携带的 Human ID。技术差异点在掌纹路线。 官方和高管材料反复强调,掌纹和掌静脉信号比虹膜方案侵入性更低、也更容易规模化,尤其是在结合智能手机采集、 扫描硬件和自我主权身份设计时。落到尽调语言,Humanity 想靠比 Worldcoin 更低的摩擦,同时声称比中心化 KYC 栈更强的隐私,拿下真人证明品类。[CO001, CO002, CO003, CO004, CO005, CO006]

KPI 快照表
指标数值 / 状态日期置信度缺口 / 备注
总部 / 运营基地根基在香港;发布和融资材料提到香港、迪拜和纽约2024-2026公开材料最能支持香港是最清晰的基地,但运营足迹比单一城市创业公司更广。
公开亮相2024 年走出隐身模式2024保留的公开来源清楚记录 2024 年发布 / 走出隐身;它们不能明确证明 2022 年正式成立日期。
最新披露估值11002025-01以百万美元计的完全稀释估值来自 2025 年 1 月融资;后续代币市场信号在估值章节讨论。
已披露融资额502025-012024 年 5 月至少 $30M,加上 2025 年 1 月 $20M;公开来源不能证明这些轮次之外还有额外股权融资。
Human ID 里程碑~7,000,0002025官方 testnet beta 文章报告接近 7M 个 Human ID;后来的掌纹扫描文章称预约超过 8M,这与已验证真人不是同一口径。
钱包地址~10,000,0002025官方 testnet beta 文章报告接近 10M 个钱包地址。
主网状态已上线,支持 zkTLS 凭证证明2025-2026上线报道确认主网可用,以及早期旅行和酒店集成。
员工人数null2026保留的公开记录没有可靠的当前员工人数,因此团队规模仍是尽调缺口,而不是可报告 KPI。

货币数值以百万美元显示。员工人数为空值表示公开数据缺口未解决,不代表员工为零。

[CO008, CO009, CO012, CO013, CO019, CO020]
FO002: 公司快照逻辑

Humanity 的逻辑栈把身份注册、更强的生物识别验证、zk 凭证证明、开发者与企业应用,以及代币化验证者 / 社区激励连接起来。

这是产品栈的架构抽象,不是来自源代码的精确数据流图。

[CO003, CO004, CO005, CO021, CO022, CO029]

1.2 领导层、融资历史,以及谁在经济上重要

公司的公开领导叙事高度集中在创始人兼 CEO Terence Kwok 身上。纳入资料中的访谈和发布材料一贯把他定位为 Humanity 隐私与生物识别论点的创始人、公开战略制定者和首席解释者;最早的发布公告还突出 Yat Siu 和 Sandeep Nailwal,把他们作为有影响力的 founding-human 和生态支持者,而不是运营高管。资本形成速度很快, 且高度加密原生。Humanity 2024 年 5 月种子轮由 Kingsway Capital 领投,Animoca Brands、Blockchain.com、 Hashed、Shima Capital 等参投,融资 $30 million、估值 $1 billion;2025 年 1 月又完成由 Pantera Capital 和 Jump Crypto 领投的 $20 million 融资,完全稀释估值 $1.1 billion。仅这两轮就确认了至少 $50 million 的 公开披露资本。它们也说明,投资人押注的是 Humanity 的协议野心和网络效应,而不是已披露收入。因此,标准利益 相关方地图与其说围绕董事会治理,不如说围绕创始人中心性、战略 Web3 支持者、验证者 / 社区一致性,以及 Humanity Foundation 和代币基础设施周围仍不透明的控制权。[CO007, CO008, CO010, CO011, CO012, CO013]

领导层和创始人表
人物角色背景创始人-市场匹配 / 职能覆盖关键人依赖
Terence Kwok创始人兼 CEO科技创业者,也是 Humanity Protocol 隐私优先身份主张的公开架构师把赛道叙事、融资可信度、生物识别定位和协议路线图掌控在自己手里
Yat SiuFounding Human / 战略支持者Animoca Brands 联合创始人兼董事长,发布材料将其列为关键生态支持者增加 Web3 分发、代币经济可信度和战略投资者入口,而不是日常运营控制
Sandeep NailwalFounding Human / 战略支持者Polygon 联合创始人,发布材料称其是协议早期指导者增强链设计和生态可信度,尤其是 Polygon CDK 以及向 Web3 应用拓展的部分

这张表只捕捉公开来源中可见的个人领导层;不是完整董事会、管理层或基金会治理名单。

[CO007, CO008, CO030, CO031]
利益相关方 / 投资者地图
利益相关方角色控制或经济重要性尽调问题
Terence Kwok / 创始团队战略和产品控制核心创始人叙事、路线图权力和公众信任高度集中在 Kwok 及小型创始核心周围索取创始人归属安排、控制权和继任计划。
Kingsway Capital2024 年 5 月种子轮领投方锚定首个披露的 $1B 估值,并在公开 testnet 扩张前帮助验证协议索取 cap table 持股、按比例跟投权,以及种子轮任何治理契约。
Pantera Capital 和 Jump Crypto2025 年 1 月轮次领投方确定最后披露的 $1.1B 完全稀释估值,并强化协议的 crypto 原生机构背书索取购买的具体证券、代币 / 股权组合、解锁条款和 side-letter 权利。
Animoca Brands 和 Polygon 生态战略支持者和分发验证方提供生态触达、可信度,以及接触开发者、游戏和更广 Web3 集成界面的入口索取商业义务、验证者角色,以及任何优先代币准入。
Humanity 社区 / 验证者 / $H 持有人网络参与基础代币发布和 fairdrop 结构使社区激励成为增长和安全主张的核心索取质押集中度、验证者分布和 fairdrop 留存行为。
Humanity Foundation / 发行方基础设施运营和控制层黑客事件后的讨论显示,基金会层面的密钥管理和桥控制对风险具有实质经济影响索取法律实体地图、托管政策和特权密钥治理。

这张地图强调从公开证据看具有经济或结构重要性的各方;不能替代实际 cap table、基金会文件或代币分配时间表。

[CO010, CO011, CO012, CO013, CO019, CO021]
FO003: 快照 KPI

公开证据最扎实的指标集中在融资和身份增长漏斗前端,员工规模仍未解开。

身份与钱包数据来自官方社区更新,不应等同于付费客户或已验证生物识别注册。

[CO012, CO013, CO019, CO020, CO031, CO032]

1.3 推出节奏、牵引力,以及后续章节应复用的里程碑序列

Humanity 最强的公开证据不是财务披露,而是网络拉新的速度。2024 年 5 月融资公告称,项目出隐身模式后一个月内 已收集超过 50 万个候补名单注册。到 2024 年末,Humanity 称 2024 年 9 月测试网已达到 100 万个 Human ID; 后续官方更新又把这一数字推到超过 500 万个 Human ID,再到接近 700 万个 Human ID、近 1000 万个钱包地址, 以及超过 500 万名 RWT 持有人。第二阶段掌纹扫描推出后,又声称在生物识别验证从预约进入真实真人认证之前, 已预留超过 800 万个 Human ID。并行地,协议在 2025 年 6 月发行 $H,用 fairdrop 概念包装抗机器人代币分发, 随后在 zkTLS 支持的凭证证明下上线主网。这个顺序重要,因为它展示了 Humanity 的运营模型:先捕获身份,其次 加深验证,再叠加代币、证明和现实世界集成。后续章节应把这里的里程碑表作为唯一事实年表。[CO015, CO016, CO017, CO018, CO019, CO020]

里程碑表
日期事件类型金额 / 估值 / 状态参与方含义
2024-Q1在 Polygon CDK 上走出隐身并公开亮相创立协议发布Human Institute 与 Animoca Brands、Polygon Labs确立项目的公开身份,以及基于掌纹的真人证明定位。
2024-05-15宣布种子轮融资融资$30M,估值 $1BKingsway Capital 与 Animoca Brands、Blockchain.com、Hashed、Shima Capital在 testnet 前为招聘和产品开发提供资金,也证明早期投资者有需求。
2024-09Testnet 上线产品Human ID 预约阶段开始Humanity Protocol 社区启动网络增长引擎第一阶段。
2024-12testnet 上达到 100 万个 Human ID规模1M Human IDsHumanity Protocol 用户显示早期身份需求漏斗顶部已有动能。
2025-01-28宣布 Series A / 战略融资融资$20M,FDV $1.1BPantera Capital;Jump Crypto完成最后一轮公开披露融资,并为协议扩张提供资金。
2025-Q1官方路线图更新提及超过 5M 个 Human ID规模5M+ Human IDsHumanity Protocol 用户表明增长已越过最初 testnet 上线里程碑并继续加速。
2025-Q2Testnet beta 更新发布产品~7M Human IDs;~10M 钱包;5M+ RWT 持有人Humanity Protocol 用户形成主网上线前最强的一组公开使用指标。
2025-06-25$H fairdrop 和代币发布产品$H 在交易所上线Humanity Protocol 社区和验证者引入网络激励、治理和质押经济。
2025-2026主网上线,支持 zkTLS 凭证证明产品主网上线Humanity Protocol;旅行和酒店合作伙伴协议从 waitlist / testnet 叙事转向实际凭证使用。
2026掌纹扫描 app 开始推出产品第二阶段生物识别验证Humanity Protocol 用户系统从 ID 预约进入实际生物识别真人证明。
2026-06-09安全事件和代币暴跌负面报告称代币回撤约 86%Humanity Foundation;代币持有人给后续所有尽调章节带来重大的信任和治理悬顶。

日期混用了精确日期、季度标记和仅年份引用,因为保留的公开记录有些只能指方向,不能给精确日期。这是本报告的标准时间线。

[CO009, CO010, CO012, CO015, CO016, CO017]
FO001: 公司里程碑时间线

Humanity 从隐秘发布进入融资、测试网规模、代币化、主网上线、掌纹扫描铺开,随后在公开可见约两年内遭遇重大安全挫折。

采用季度标记,因为留存公开记录更偏里程碑,而不是精确日历日期。

[CO009, CO012, CO017, CO021, CO035, CO037]

1.4 治理、负面信号,以及仍未实质验证的事项

在投资人最需要承销证据的地方,公开记录明显更薄。Humanity 官方沟通在社区增长、身份预约和生态愿景上很丰富, 但对当前员工数、法律实体图谱、董事会构成、客户集中度,以及从庞大漏斗顶部 ID 基础转化出的收入披露很少。 2026 年 6 月,信任叙事也急剧走弱:一份被广泛引用的攻击报告描述了 $H 在 Ethereum 和 BNB Chain 上被 未授权铸造和出售、代币约 86% 暴跌,以及公众指控内部人控制或特权密钥管理过度集中。即便公司更愿意把事件 描述为外部密钥泄露,而非协议设计失败,事件仍削弱了 Humanity 叙事中最干净的那一版:一个隐私优先的身份网络 理应在结构上比现有替代方案更安全。因此,概览结论应保持平衡。Humanity 建立了有吸引力的品类叙事,展现出 罕见的拉新动能,并吸引了顶级加密投资人,但它尚未给出足够公开证据,把 Human ID 增长视为持久变现或成熟治理 的证明。[CO027, CO031, CO034, CO035, CO036, CO037]

1.5 图表

Chapter 02

02市场分析

2.1 市场边界:Humanity 卖的是证明与凭证层,不是整套身份栈

界定 Humanity 市场最清晰的方式,是把它放在身份验证、真人证明、生物识别保障和可复用数字凭证的交叉处。 Humanity 官方材料没有描述一个狭窄的纯加密细分市场。它们讨论 KYC、忠诚度、访问控制、欺诈降低、凭证可携带性 和抗女巫应用设计。这意味着纳入的支出不只是区块链身份钱包,也包括活体检测和生物识别验证、凭证发行与复用,以及在 证明唯一真人很重要的场景中选定的反机器人或反欺诈工作流。被排除的支出同样重要。Humanity 并未覆盖整套 IAM 栈、密码管理、通用安全运营或所有外包 KYC 工作流。现状仍然碎片化:中心化 KYC 供应商、社交登录、人工 证件审核、CAPTCHA,以及 World ID 等相邻真人证明系统,都在解决同一任务的不同切片。这个边界逻辑重要,因为 它能防止投资人把整个生物识别市场或整个身份验证市场当成 Humanity 的现实可服务市场。真正的问题是:这类支出中 哪个子集足够重视保护隐私、可复用的人类唯一性,愿意采用一个新的网络化协议,而不是更便宜的现有点解决方案。[CM001, CM002, CM003, CM004, CM019, CM028]

市场定义表
细分 / 类别纳入支出排除支出买方 / 付费方相关性
身份验证平台证件核验、活体检测、生物识别、欺诈编排、可复用凭证更广义 IAM、终端安全、通用网络安全工具合规、欺诈、风险和平台团队Humanity 企业侧最接近的宽口径公开市场代理。
生物识别保证掌纹、人脸、指纹、虹膜、硬件扫描仪、匹配引擎没有身份工作流或凭证层的通用传感器政府、企业、门禁运营商关键使能层,但比 Humanity 的实际协议切入口宽得多。
去中心化数字身份 / 可验证凭证钱包、凭证发行、发行方注册表、隐私保护证明纯代币投机或非凭证型消费者钱包政府、生态、凭证发行方、平台运营商最接近 Humanity 可复用身份主张的架构同类。
真人证明 / 反女巫抗 bot、fairdrop 门控、治理完整性、社区验证没有持久身份的通用 CAPTCHA 式垃圾信息控制协议基金会、增长团队、信任与安全团队短期 Web3 切入口,Humanity 在这里差异化最直接。
旅行 / 忠诚度 / 凭证复用可携带忠诚度、账户关联、教育和职业证明不需要可复用信任凭证的传统 CRM 系统合作、产品和运营负责人代表从 crypto 原生身份走向消费者实用性的现实桥梁。
现状替代方案中心化 KYC 供应商、社交登录、人工审核、CAPTCHA、政府 ID身份工作流中的既有预算负责人这些替代方案限制定价权,也拖慢协议迁移。

这张表按 job-to-be-done 定义 Humanity 的市场。纳入和排除支出是基于保留来源集作出的分析判断,不是管理层指引。

[CM001, CM002, CM003, CM004, CM028, CM030]
FM001: 市场规模视角

Humanity 的合理市场落在几个更宽的相邻市场之内;真人证明和可复用凭证构成更窄的可服务切口。

上层使用已报告的市场总量;下层刻意保持定性,因为留存来源无法支持 Humanity 精确切口的清晰公开 SOM。

[CM001, CM005, CM006, CM018, CM028, CM034]

2.2 规模测算视角:广义相邻市场很大,可用切入点窄得多

公开市场规模只能支持分层看法。Mordor Intelligence 估计,2026 年身份验证市场为 $15.78 billion,到 2031 年增至 $26.8 billion,CAGR 约 11.2%;更广义的生物识别市场更大,2026 年为 $67.86 billion,预计 2031 年达到 $136.86 billion,CAGR 约 15.1%。这些数字说明,买家已经在身份核验和生物识别保障上投入真金白银, 但它们不能证明 Humanity 能覆盖全部支出。Humanity 更近的切口更小,因为许多生物识别部署是物理访问或国家运营 系统,不需要去中心化凭证;许多以证件为中心的 KYC 流程也不需要持续的真人证明。地理位置也重要。Mordor 显示 北美当前支出领先,而亚太在身份验证和生物识别两个市场中增速最快。这对 Humanity 在方向上有利,因为公司的公开 足迹与亚洲相关,早期增长叙事也更偏互联网原生,而非网点银行原生。尽管如此,最强的可服务市场视角不是单一自上 而下的 TAM 数字;而是一组由身份验证、生物识别和数字凭证复用锚定的相邻市场,其中真人证明层是更窄但演化更快 的子板块。[CM005, CM006, CM007, CM008, CM009, CM010]

TAM / SAM / SOM 或规模测算视角表
发布方年份地域数值CAGR / 增长方法论视角置信度局限
Mordor Intelligence – 身份验证市场2026全球2026 年 15.78 USD B;2031 年 26.8 USD B2026-2031 年 CAGR 11.18%宽口径身份验证软件和服务市场自上而下市场有用,但比 Humanity 更窄的真人证明切入口宽得多。
Mordor Intelligence – 生物识别市场2026全球2026 年 67.86 USD B;2031 年 136.86 USD B2026-2031 年 CAGR 15.07%覆盖硬件、软件和公共部门用例的宽口径生物识别市场口径太宽,不能直接当成 Humanity 可服务市场,因为大量支出在去中心化凭证之外。
World Economic Forum – 数字 ID 包容性视角2026 年语境下引用 2023 年全球850M 人没有法定 ID不是收入 CAGR 来源数字身份和包容性的未满足需求视角人口需求不等于可变现的企业支出。
FATF 数字 ID 指引2020 年官方指引,2026 年仍有效全球 / 受监管金融未引用市场规模数字交易估计年增长 12.7%;到 2022 年,60% GDP 已数字化客户尽职调查的监管需求视角指引是监管和定性材料,不是公司市场收入预测。
Entrust / LexisNexis / ID.me 欺诈报告2025-2026全球威胁量视角,不是市场规模深度伪造、合成身份和 bot 均大幅上升证明与验证需求侧紧迫性视角显示痛点强度,不直接等于买方会在 Humanity 类解决方案上花多少钱。

本章刻意使用多个规模测算视角,而不是一个膨胀的 TAM。Humanity 真正可服务市场是嵌在这些更宽类别中的一个子细分。

[CM005, CM006, CM014, CM015, CM018, CM022]
FM002: 市场估算区间

当前到预测区间显示,相邻身份市场在增长;但也显示 Humanity 窄切口与更广义生物识别宇宙之间差距多大。

低值是 2026 年市场规模估算,高值是同一发布方的 2031 年预测;这是时间跨度区间,不是牛 / 基准 / 熊情景。

[CM005, CM006, CM034]

2.3 买家、用户、付费方和采用路径因细分市场而异

Humanity 的买家地图很杂。在 Web3,近期买家通常是协议基金会、增长团队或生态运营方,目标是阻止女巫刷量、 改善公平代币分发,或提升治理和社区激励中的信任。在受监管准入流程中,买家更常是风险、合规、欺诈或 平台安全团队,关心更低误报、更好活体检测和更少合成身份损失。在旅行、酒店、教育和职业凭证场景里,用户可能是 消费者,但付费方更可能是平台、发行方或合作负责人,他们要降低准入摩擦并获得可携带的信任信号。 Humanity 自己围绕旅行忠诚度、金融凭证、教育或职业证明的主网定位符合这个模型。因此,采用路径是多步骤的: 用户必须注册,更强验证必须完成,发行方和平台必须认可凭证,开发者必须集成工具,监管者或企业风险团队必须接受 这套保障模型。这让网络效应成为可能,但不会自动发生。随着更多发行方和应用认可单一 Human ID,Humanity 这样的 协议会更有价值;但如果可携带凭证的标准化不足,或用户没有从低摩擦预约走向更高保障验证,它也可能停滞。[CM015, CM016, CM017, CM028, CM029, CM030]

细分 / 买方地图
细分买方用户付费方工作流预算负责人采用触发因素
Web3 协议 / 生态基金会、增长、社区、治理团队钱包持有人或社区参与者基金会 / 协议 treasuryfairdrop、治理、抗女巫增长 / 生态 / 基金会运营bot 滥用、羊毛党套利和治理完整性压力。
Crypto 交易所 / 钱包风险、信任与安全、平台安全交易者、存款人或账户持有人风险 / 平台 / 合规预算开户注册、账户恢复、滥用预防风险 / 信任与安全合成身份、虚假账户或奖励滥用损失。
Fintech / neobank / 受监管开户注册合规、欺诈或身份负责人接受 KYC 的客户合规 / 欺诈 / 开户预算开户、持续验证、欺诈审查风险 / 合规 / 运营深度伪造、活体伪造和 KYC 成本上升。
旅行 / 酒店 / 忠诚度产品合作或忠诚度运营方旅行者 / 忠诚度会员产品 / 合作 / 运营预算关联并复用可信凭证忠诚度 / 产品 / 运营希望减少重复开户,并增加已验证权益或门控访问。
教育 / 就业凭证机构或凭证发行方学生、工作者或申请人发行方 / 平台 / 机构预算学位、角色或资格的可携带证明数字化转型 / 注册办公室 / HR tech需要可携带、用户控制的证明,同时不暴露完整记录。
政府 / 公共部门身份服务机构或数字身份项目办公室公民或居民公共部门数字服务预算高保证身份、认证、联合身份政府 IT / 身份项目政策强制要求、降低欺诈与普惠目标。

不同细分市场里,买方、用户和付款方并不一致。Humanity 的 Web3 根基没有排除相邻的企业或公共部门需求,但对应的销售动作和保障要求会不同。

[CM007, CM008, CM015, CM017, CM029, CM030]
FM003: 买方 / 分群摩擦图

不同分群对保障强度、凭证可携带性和增长导向的消费者激活有不同组合需求,因此销售动作和市场成熟度也不同。

单元格是有证据支撑的序数判断,说明每个分群哪里最有紧迫性或价值;不是实测市场份额统计。

[CM028, CM030, CM032, CM036, CM038]
FM004: 采用漏斗或价值链图

这个品类的采用会从对数字身份的广泛好奇,压缩到小得多的一批用户和发行方:他们愿意完成更高保障验证,并复用由此得到的凭证。

数值是序数型采用步骤权重,用来说明漏斗压缩,而不是实测转化率。

[CM029, CM030, CM032, CM036, CM038]

2.4 增长驱动很明显;监管和信任约束同样真实

Humanity 所在品类的需求驱动异常清晰。Entrust、LexisNexis 和 ID.me 都描述了一个身份欺诈环境:深度伪造、 注入攻击、合成身份,以及越来越像真人的自动化流量,正在以传统验证控制难以承受的速度扩张。在这种环境里,真人 证明和可复用信任信号的经济价值会上升。监管背景也支持更强基础设施的需求。FATF 称,稳健的数字 ID 可以降低成本、 改善尽调并扩大包容性;NIST 2025 年对 SP 800-63-4 的更新强化了证明、认证和联邦化的重要性;欧洲委员会的 数字身份计划也显示,可携带凭证正在成为政策目标,而不只是加密实验。但同一环境也带来约束。生物识别系统面临 隐私、同意和公平性审查;World Economic Forum 材料强调,去中心化数字 ID 仍需要适配用途的政策、标准和治理, 才能避免复制新的监控或滥用形态。对 Humanity 来说,市场增长的理由是对的,但采用会奖励那些把低摩擦与可信保障、 互操作性和事件后信任结合起来的供应商,而不是只展示快速获客的供应商。[CM015, CM016, CM017, CM018, CM020, CM021]

增长驱动因素与约束表
驱动因素 / 约束方向时点含义尽调问题
深度伪造与注入攻击驱动当前促使客户在静态证件和密码之外,更急迫地部署更强的真人验证层Humanity 的保障模型能否在规模化场景下顶住深度伪造和注入绕过?
合成身份增长驱动当前让持续验证和更高保障的入门验证更有价值在合成身份问题上,Humanity 哪些环节强于只做证件验证的供应商?
代理式机器人流量与类人自动化驱动当前支撑社区、游戏和账号创建流程对真人证明的需求Humanity 目前的业务牵引有多少来自抗机器人需求,多少来自投机性代币需求?
欧盟数字身份与可复用凭证政策驱动中期让可携带凭证和跨平台信任更有政策依据Humanity 能否与企业和监管钱包标准互通?
FATF / NIST 保障要求驱动中期利好能把身份核验、认证和治理讲清楚的供应商Humanity 的模型能否清晰映射到主流保障框架?
隐私与生物识别同意法规约束当前抬高生物识别身份系统的法律和声誉成本Humanity 在哪些司法辖区无需大改设计或增加本地存储控制就能进入?
标准碎片化 / 签发方接受度约束中期凭证若不能被签发方和依赖方广泛接受,网络效应就跑不起来哪些外部签发方或机构已经接受 Humanity 凭证?
安全事件后的信任受损约束当前让买方更谨慎看待密钥或代币控制集中的协议管理层能向企业买方展示哪些事故后的具体控制措施?

本表对增长与阻力同等处理。同一波 AI 欺诈一边创造需求,一边抬高保障要求,也会惩罚治理弱点。

[CM015, CM016, CM017, CM021, CM022, CM023]

2.5 图表

Chapter 03

03竞争格局

3.1 直接真人证明对手按硬件、社交图谱、担保和聚合路线分化

最接近的直接对手,是其他用于证明唯一真人、而不只是验证政府证件的系统。World ID 是最明显的可比对象:它营销 通用真人证明、消费者登录场景,以及围绕深度伪造防御、凭证和奖励扩展的工具包,但仍依赖基于 Orb 的验证,并 背负虹膜扫描争议留下的包袱。BrightID 和 Proof of Humanity 位于设计光谱另一端。BrightID 是一个公共品、 开源的社交身份网络,避免个人身份信息并依靠社交图谱分析;Proof of Humanity 则用资料、押金、担保和挑战流程 维护一份抗女巫真人列表。Human Passport 是最强的非生物识别聚合型竞争者:它为空投、治理、防垃圾信息和 在线社区打包真人证明、ZK KYC 和数据服务。面对这组对手,Humanity 的核心押注是,掌纹生物识别加可复用凭证, 可以在不继承 World 的 Orb 系统同等硬件摩擦的情况下,比社交或担保模型提供更低摩擦。换句话说,直接竞争者 对“真人性”的事实来源并不一致:World 信任专用硬件,BrightID 信任社交连接,Proof of Humanity 信任社区担保 和挑战激励,Human Passport 信任可组合信号聚合。Humanity 要求市场信任生物识别加可复用凭证。[CP001, CP002, CP003, CP004, CP005, CP006]

竞争对手画像表
竞争对手类别规模 / 融资目标细分市场差异化局限
World ID / World生物识别真人证明网络消费级网络野心;留存资料中未确定当前已验证用户数消费者应用、奖励、社交、游戏、现场活动Orb 验证的唯一真人证明、凭证、奖励、深度伪造工具依赖硬件,围绕虹膜验证的隐私和监管包袱更重
BrightID社交图谱唯一性证明社区主导的公共品;网站可见团队名册Web3 社区、投票、公平访问非侵入式、开源、无 PII、社交恢复社交图谱入门验证可能更慢,也不够企业友好
Proof of Humanity 真人证明担保与挑战注册表开放的人类注册表模型;留存资料中未披露企业规模治理、空投、社交、认证押金、担保和挑战机制强调抗 Sybil摩擦更高,注册速度慢于移动优先系统
Human Passport聚合器 / 抗 Sybil 数据层2M+ Passport、120+ 合作伙伴、43M+ 凭证、已保护 $512M+ 空投空投、治理、社区、垃圾信息防控可组合印章、哈希化信号、强 Web3 分发生物识别唯一性的差异化较弱,因为它转而聚合多种信号
Persona企业身份验证平台公开强调主流客户名单以及 2026 Gartner / 2025 Forrester 认可金融科技、市场平台、加密、政府、教育、劳动力IDV、KYB、KYA、复验和风险的工作流覆盖面广不是专门为去中心化真人证明打造的网络
Humanity Protocol手掌生物识别凭证网络$50M+ 已披露资本,Human ID 增长强劲,但企业规模尚未公开证明Web3 身份、抗 Sybil、凭证复用、选定现实世界集成掌纹加掌静脉策略试图平衡可及性、隐私和唯一性必须相较更成熟对手证明信任、签发方接受度和收入转化

规模字段混合直接披露指标和明确标注的未知项;许多竞争对手不发布可直接比较的用户、收入或合同数量。

[CP001, CP004, CP006, CP008, CP009, CP011]
功能 / 能力矩阵
采购标准HumanityWorld IDBrightIDProof of Humanity 真人证明Human PassportPersona
生物识别唯一性证明
无 PII / 隐私优先叙事
低摩擦消费者自助入门验证
企业 KYC / 合规适配度
空投 / 治理 / 抗 Sybil 适配度
可复用凭证 / 跨应用野心

单元格是基于公开产品定位得出的有证据支持的序数判断,不是基准性能测试结果。

[CP001, CP002, CP004, CP006, CP008, CP010]
FP001: 竞争定位图

直接竞争格局聚成四个角:消费者生物识别、隐私 / 社区、聚合器 / 分发,以及企业合规。

坐标轴是有证据支撑的序数评分,概括隐私舒适度相对于保障强度 / 企业就绪度;不是实测基准输出。

[CP019, CP021, CP022, CP023, CP024, CP025]

3.2 相邻企业既有厂商可能比部分 Web3 同行更重要

当买家是受监管企业,而不是代币驱动社区,竞争故事就会改变。Persona 的公开网站说明了原因:它现在把自己营销为 一种灵活、安全的线上真人和企业验证方式,展示蓝筹客户标识,并突出 Gartner 和 Forrester 认可。其产品足迹覆盖 政府 ID、文档 AI、自拍识别、数字 ID、KYB、KYA、重新验证和风险报告,远宽于 Humanity 当前的公开产品证明。 Onfido 和 Jumio 仍是重要替代品,尽管本轮检索访问其公开页面受限,因为它们代表主流既有 KYC 和活体检测供应商, 许多买家会首先选择这类方案。Civic 的启示来自另一个角度:其公开网站如今围绕 AI 代理集成、GTM 工作流和 认证工具,意味着一个曾经更知名的身份品牌已经把战略重心移出这条赛道。Fractal ID 更难评估,因为检索期间 网站不可用,但这种可见度缺失本身就是竞争信号。因此,最大的替代方案可能是一套混合栈:用既有 KYC 供应商处理 受监管保障,再叠加 Human Passport、BrightID 或内部启发式规则等单独反女巫层。[CP011, CP012, CP013, CP014, CP015, CP016]

定价 / 套餐比较
竞争对手价格 / 单位 / 合同模式包含能力折扣或未知项含义
Humanity Protocol留存资料中没有公开标价;经济性与协议采用、代币化参与绑定Human ID、掌纹验证推广、凭证、Fairdrop / 质押生态企业买方的商业套餐条款仍未披露买方还难以把 TCO 与企业既有供应商做基准比较。
World ID留存资料中没有公开自助式企业价格真人证明、深度人脸、人脸认证、凭证、奖励商业条款不公开;硬件铺设影响很大World 可能靠生态 / 网络效应变现,而不是简单 SaaS。
BrightID社区 / 公共品模式;留存资料中没有标准企业定价社交图谱唯一性、社交恢复、公平访问证明变现方式似乎没有 SaaS IDV 标准化对重视隐私的社区吸引力高于由采购主导的买方。
Proof of Humanity 真人证明注册表 / 挑战 / 担保机制;留存资料中没有清晰 SaaS 定价已验证人类注册表、空投、治理、认证经济模型并非按传统企业软件定位适合治理场景,但更难做财务基准比较。
Human PassportAPI / 数据服务式定位;留存资料中没有透明公开费率表实时 Sybil 检查、数据服务、ZK KYC、合作伙伴集成可能取决于套餐和用量竞争点更多在 Web3 分发和可组合性,而不是标价透明度。
Persona / 企业既有供应商演示驱动的企业合同,不是简单公开定价IDV、KYB、KYA、风险报告、复验、案例管理公开标价仍有限或定制企业买方可能仍偏好既有供应商,因为不透明定价在合规软件中很常见。

市场定价极度不透明。未知项明确列出,而不是猜测。

[CP022, CP028, CP029]
FP002: 功能广度 / 能力图

企业既有厂商和 web3 原生竞争者覆盖身份任务的不同切片,因此更可能出现混合栈,而不是单一赢家。

单元格是按工作流判断产品适配度的序数判断,意在展示可堆叠性,而不是原始功能数量。

[CP022, CP026, CP027, CP029, CP035, CP036]

3.3 护城河耐久度取决于认可和信任,而不只取决于注册数

这个市场里没有竞争者能在所有维度获胜。World 有更强消费者认知和专用硬件护城河,但监管和隐私敏感度也更高。 BrightID 和 Proof of Humanity 吸引重视隐私和治理的社区,但在主流准入流程上可能显得更慢或更难规模化。 Human Passport 已经拥有可衡量的 Web3 分发和可组合多印章模型,因此在不想使用生物识别的空投、治理和 社区完整性场景中,是强替代品。Persona 和企业既有厂商在受监管准入流程中更难被替换,因为它们已经嵌入 合规工作流,并有可见客户背书。Humanity 因此处在一个有吸引力但不稳定的中间地带。如果掌纹验证真的比 Orb 硬件 更容易规模化、比重担保系统更好用,同时又支持可复用凭证,Humanity 可以切出一个独特位置。否则,买家可以多归属、 混用供应商,或默认选择最适合其具体工作流的成熟层。关键护城河变量因此是发行方认可、开发者集成、事件后信任, 以及 Human ID 是否成为其他应用真正认可的凭证。这也意味着,竞争分析不能停在产品主张。它必须追问哪些系统被 发行方接受,哪些被监管者容忍,哪些能在真实安全或治理压力下不失去买家信心。[CP019, CP021, CP022, CP023, CP024, CP025]

护城河耐久性 / 竞争风险登记表
护城河主张威胁严重性缓解 / 尽调问题
手掌生物识别比 Orb 硬件摩擦更低World 仍可凭消费者认知和专用硬件护城河获胜要求按模态和地域提供实证转化率、流失率和准确率数据。
Human ID 可成为可复用凭证层买方可能多供应商并用,同时使用独立 KYC 与抗 Sybil 技术栈要求提供真实签发方名单、重复使用数据和跨应用凭证复用率。
隐私优先的生物识别胜过社交或担保模型重视隐私的社区可能仍偏好 BrightID、PoH 或 Human Passport 这类非生物识别系统证明其能进入目前拒绝较重生物识别采集的社区。
Human ID 快速增长带来分发优势如果注册没有转化为可信集成或付费工作流,增长可能商品化要求提供激活、验证完成率和变现队列数据。
Web3 根基在空投和治理场景形成防御性Human Passport 在这些具体工作流里分发已经很深说明掌纹唯一性为什么能在欺诈、UX 或留存上胜过多印章聚合。
Humanity 能打通 Web3 与企业身份Persona 和其他既有供应商已经掌握企业信任和客户背书要求提供企业案例研究、合规控制和可供背书的生产环境客户。

本风险登记表关注持久竞争威胁,而不只是功能缺口。

[CP021, CP022, CP025, CP026, CP027, CP028]
FP003: 护城河 / 就绪度 KPI

眼下就绪度最强的是 Human Passport 的 web3 分发、Persona 的企业可信度,以及 World 的消费者生物识别品牌认知;Humanity 仍是那条「需要证明」的中间路线。

KPI 是从留存来源片段提取的类别标记,不是归一化评分模型。

[CP009, CP012, CP021, CP023, CP028, CP032]

3.4 图表

Chapter 04

04财务

4.1 公开经济模型以代币为先,现金收入机制大多仍不透明

Humanity 没有展示传统软件价目表。最清晰的公开经济载体是 H 代币页面,它描述了一种固定供应的 ERC-20 资产, 用于奖励验证者、驱动开发者并协调协议参与。Fairdrop 和质押材料强化了同一图景:激励和生态增长位于模型中心。 这很重要,因为它改变了“财务”的含义。最可见的价值驱动是代币发行、供应解锁、凭证采用,以及资金库或生态杠杆, 而不是已披露 ARR 或按席位订阅。公开材料确实暗示多条潜在变现路径——企业身份服务、凭证验证、开发者工具、 资金库升值,以及通过 Moongate 提供活动或忠诚度基础设施——但纳入来源没有披露合同定价、实际抽成率或按业务线 确认的收入。结果是,一个真实经济系统存在,但现金转化路径不清楚。换一种说法,Humanity 公布了其网络的供给侧逻辑, 却没有公布其业务的利润表逻辑。投资人能看到代币如何分配、部分桶何时解锁,以及社区为什么应该在意。但他们仍看不到 由此产生的需求有多少会转化为费用、服务收入,或由发行方捕获的资金库价值,而不是流向验证者、用户或市场交易者。[CI001, CI002, CI003, CI004, CI005, CI006]

收入流表
收入流机制单位当前公开状态质量尽调问题
代币价值 / 金库敞口H 代币生态和相关金库定位带来价值增值代币价格、FDV、解锁路径可通过公开代币经济学和市场数据看到,但签发方经济性未披露战略相关性中等,会计可见度低披露金库持仓、代币出售政策、已实现收益 / 亏损以及金库钱包治理
验证者 / 质押经济质押与验证奖励把参与和验证工作对齐代币奖励 / 质押参与作为产品功能公开可见,但不是签发方收入生态信号好,收入可见度弱提供质押量、验证者数量、收益率公式和金库捕获率
开发者 / 应用活动开发者使用协议身份和凭证构建应用API 使用量、凭证检查、集成合同官方定位有所暗示,但没有披露公开定价可能可扩展,但尚未证明能形成现金流披露付费开发者计划、免费到付费转化和合同规模
企业身份 / 凭证服务组织可能为可复用身份以及金融或教育凭证工作流付费按部署 / 合同 / 验证量用例公开,变现条款不公开战略重要,但公开资料尚未证明展示可背书合同、试点与生产环境划分、定价和续约条款
Moongate 活动与忠诚度基础设施通过收购平台提供票务、访问控制、忠诚度和现实世界用户引导营销活动 / 现场活动 / 准入工作流收购扩大产品覆盖面,但没有公开贡献数字有趣的邻近业务,暂无财务证明披露 Moongate 收入、利润率、客户数,以及与 Human ID 增长的挂钩
Fairdrop / 社区增长代币排放驱动获客和生态参与代币分配 / 活动产出清晰可见,但更应视为激励支出而非赚取收入有用的增长杠杆,但收入质量不足量化 CAC 等价成本、欺诈节省,以及 Fairdrop 用户向留存用户的转化

各行区分可能的价值捕获路径和已披露会计收入;Humanity 尚未发布分部收入。

[CI001, CI002, CI006, CI007, CI010, CI024]
定价 / 变现表
产品 / 服务价格 / 单位 / 合同标价与实现价格折扣 / 未知项来源说明
Human ID / 凭证未见公开标价Unknown企业合同如有,仍未披露官方页面讨论产品范围,不提供费率表
$H 代币市场交易代币价格,而不是供应商标价公开现货价格,发行方实际变现未知价格波动,不等同于收入CoinGecko 和 CoinMarketCap 仅提供市场参考
质押收益率作为生态激励存在,不是已披露公司价格Unknown奖励公式和金库捕获仍不清楚质押门户确认功能存在,但不说明经济性
Fairdrop 活动代币分配,而不是直接现金定价N/A每名留存用户的有效获客成本未披露Fairdrop 定位为分发机制
Moongate 现实世界激活未见公开定价Unknown收购可能涉及定制活动或合作伙伴条款Moongate 公告扩大产品覆盖面,不提高价格透明度

Humanity 目前未在留存公开记录中披露标准化商业定价。

[CI007, CI008, CI009, CI019, CI024, CI025]
FI001: 收入模型桥

Humanity 公开的收入逻辑,是从身份增长进入代币激励、集成,最后才可能走向现金变现。

这座桥基于公开定位和代币经济学重构,不来自已披露的管理会计。

[CI001, CI006, CI010, CI015, CI025, CI033]
FI002: 单位经济性桥

公开故事缺失的一环,是身份验证和代币激励如何转成可持续毛利。

每一步都作为公开叙事可见,但转化率和成本项没有披露。

[CI007, CI015, CI017, CI019, CI024, CI035]

4.2 融资和代币市场信号足以证明相关性,但不足以证明持久经营质量

最强的公开数字是融资和代币市场数据。多个来源支持其在 2024 年融资和 2025 年 1 月 Series A 中合计披露融资约 $50 million;后者被描述为 $1.1 billion 完全稀释估值,而不是传统经审计企业价值。2026 年 8 月的代币市场页面 显示,网络现货市值约 $170 million、完全稀释价值约 $852 million,仍然很大,但低于此前融资标题。漏斗顶部使用 指标也看起来亮眼:Humanity 报告过 100 万个 Human ID,随后约 700 万个 ID 和 1000 万个钱包。但这些是采用指标, 不是付费需求证明。它们说明网络和代币在市场想象中达到有意义的规模;它们没有揭示系统实际产生多少收入、利润率或 净现金。这个区别在这里比传统创业公司更重要,因为代币网络在纸面上可以显得很大,却仍为运营方产生有限当前现金。 买家因此必须对估值标题打折,直到管理层打开叙事背后的账本。[CI011, CI012, CI013, CI014, CI015, CI016]

资本充足性表
项目公开证据当前值 / 状态解读尽调需索取
已披露融资额2024 年融资加 2025 年 1 月轮次公开口径合计约 $50M足以支持有意义的建设,但不能推断当前现金提供股权结构表、各轮募集资金和当前现金
最新融资基准2025 年 1 月 Series A 轮FDV 约 $1.1B这是代币网络基准,不是经审计的运营 EV提供轮次文件以及优先权 / 代币权利
当前代币市场价值CoinGecko 2026 年 8 月快照市值约 $170M / FDV 约 $852M公开市场给网络的定价低于融资基准提供金库按市值计价敞口和代币销售历史
资金续航期未披露Unknown无法判断融资紧迫性提供月度现金消耗和 12 个月现金计划
债务 / 信贷义务留存证据中没有项目融资或债务披露未知 / 公开未确认留存资料显示资本结构主要由股权和代币驱动提供债务明细表、认股权证和表外义务

轮次时间线仅按评估未来资本充足性所需范围概述。

[CI011, CI012, CI014, CI021, CI022, CI023]
FI003: 财务估算区间

目前最清楚的公开区间不是收入,而是估值:已披露融资基准与当前代币市场价值的对照。

上述标记有来源支撑,不是收入预测,也不是 DCF 结果。

[CI012, CI013, CI021, CI022, CI023]

4.3 资本形成看起来可信,但现金续航和单位经济仍藏在公司控制的披露背后

从尽调角度看,Humanity 可以融资,但还不能被充分承销。它确实已经融资、发行代币激励、扩展到主网,并用恢复与 透明度界面回应了一次严重攻击。但这些都不能替代判断现金续航或利润率质量所需的私有指标。公开记录仍未披露收入、 毛利率、现金消耗、账面现金、留存、客户集中度、CAC、回本周期或单用户验证成本。攻击事件又增加了一层不确定性,因为 恢复义务、运营整改和信任修复都可能消耗资源,而不创造持久收入。相比一家上市身份软件公司,Humanity 的披露集 极其单薄。因此,正确财务结论应保持谨慎:公司有足够资本、产品动能和代币基础设施,值得被认真对待;但投资人仍需要 资料室,才能有信心为收入质量、资本充足性或事件后韧性定价。本章因此把未知项视为真实尽调阻塞点,而不是用 软件式经验法则把它们抹平。如果 Humanity 最终展示经常性收入、有吸引力的贡献利润率,并控制事件后资金库暴露, 投资判断可以很快改善。但仅凭纳入的公开记录,正确立场仍是受证据约束,而不是乐观。[CI017, CI018, CI019, CI020, CI027, CI028]

单位经济性表
指标数值 / 状态置信度重要性尽调问题
收入 / ARR未公开披露投资判断的核心规模指标提供月度收入、ARR 和按业务线拆分的收入
毛利率未公开披露决定其收入质量更接近软件还是服务提供按分部划分的 GAAP 或管理口径毛利率
获客成本未公开披露检验 Fairdrop 拉动的增长是否高效按渠道提供 CAC,包括代币激励支出
回本周期未公开披露显示企业 / 客户获客效率按客户群组提供回本周期
净收入留存未公开披露说明增长能否越过漏斗顶部身份数量,沉淀为持久关系按细分提供 NRR/GRR 和流失率
每活跃用户验证成本未公开披露决定生物识别扩张的单位经济性提供每次掌纹验证的单位成本,以及持续更新凭证的成本
验证者奖励效率未公开披露显示价值捕获前漏掉了多少网络支出提供验证者奖励公式和总派发比率

空值是刻意保留的;公开记录不足以支撑编造单位经济指标。

[CI017, CI019, CI031, CI035]
公开财务缺口表
缺失的私有指标对投资判断的影响具体尽调路径
各产品线收入无法把代币叙事和现金业务拆开索取董事会材料或管理层 P&L 拆分
毛利率及托管 / 验证成本无法判断协议使用是否盈利索取毛利桥和基础设施 / 生物识别成本拆分
现金余额和月度现金消耗无法评估下一轮时点索取最新资产负债表和 12 个月经营计划
留存和付费客户群组无法判断集成是否转化为可持续收入索取企业 / 开发者客户的群组表
金库与解锁治理无法定价稀释和抛压风险索取金库钱包映射、解锁时间表和代币委员会政策
漏洞利用事件补救成本无法估算 2026 年 6 月事件的经济损失索取事件成本台账、法律准备金和补偿计划

这些是产出投资级财务模型前最低限度必须补齐的数据点。

[CI017, CI028, CI029, CI030, CI032, CI036]
FI004: 资本强度 / 现金流图

公开证据指向工程、生态激励和信任修复三大成本桶;传统营运资本压力还看不出来。

单元格是有来源支撑的等级判断,用来排序可见成本压力,不编造具体费用金额。

[CI020, CI028, CI029, CI034, CI036]

4.4 图表

Chapter 05

05产品与技术

5.1 产品如今横跨真人证明、可携带凭证和身份感知应用

自早期“Worldcoin 竞争者”定位以来,Humanity 对外展示的产品范围已经明显扩展。主页、协议页面和文档如今呈现的是更广的 信任层:用户预留 Human ID,完成更强掌纹验证,持有钱包原生凭证,然后在需要真人证明、资格或声誉的应用中复用 凭证。主网和可验证凭证文章让产品野心更清晰。Humanity 不再只销售唯一性证明。它试图成为一张身份图谱,让教育、 旅行、就业、社交和金融事实可以被选择性证明,而不用交出原始个人数据。这创造了比一次性注册更大的机会, 但也让产品执行更难,因为公司要解决的不只是生物识别,还有可携带性、开发者体验、发行、撤销,以及在许多应用语境 中被接受。广度在战略上有吸引力,因为它给 Humanity 提供了多个切入市场的楔子:消费者身份、开发者工具、凭证编排 和伙伴中介分发。它也抬高了执行门槛。一家公司可以早早做出吸引人的注册体验,却要很久以后才能证明凭证发行、撤销、 可携带性和多应用认可可以在规模上可靠运行。因此,最重要的尽调问题不是产品地图是否雄心勃勃;而是那张地图背后的 运营细节是否足够快地追上来。[CE001, CE002, CE003, CE004, CE005, CE007]

产品模块 / 资产矩阵
模块 / 资产主要用户状态 / 成熟度差异化尽调缺口
Human ID消费者和生态用户身份预约和账户层已上线跨应用可移植的身份锚点公开记录未量化活跃 ID 与沉睡 ID
掌纹验证需要更强唯一性证明的消费者2026 年已公开上线使用掌纹生物识别,而不是 Orb 硬件或社交背书模型无公开准确率或失败率基准
可验证凭证用户、社区和合作伙伴已上线,并随主网扩展钱包持有、选择性共享的证明无公开签发方 / 撤销性能指标
SDK / APIWeb2 开发者和应用团队公共文档和 GitHub 仓库已上线类 OAuth 集成和预设验证无公开速率限制、SLA 或生产客户深度
Walrus 存储层开发者和协议运营方已宣布上线集成用于声明、证明和回执的去中心化存储留存资料中没有第三方审计
Fireblocks 支持机构金库和托管团队已宣布上线支持让机构通过既有托管流程操作 H相比终端用户身份 UX,更直接支持资产和金库操作

各行区分可观测模块和缺失的基准证明。

[CE003, CE006, CE010, CE012, CE019, CE022]
工作流 / 用例表
用户任务当前工作流Humanity 方案可衡量收益限制
在线证明唯一真人预约 ID、完成验证、出示证明Human ID 加掌纹验证无需交出中心化身份即可抵抗 Sybil无公开完成率基准
证明可复用属性连接凭证来源并出示选择性证明钱包持有的可验证凭证跨应用和生态的可移植性签发方覆盖和撤销 SLA 不清晰
为 Web 应用加入真人感知登录实现类 OAuth 认证流程和预设检查SDK/API 集成开发者接入比从零自建更快无公开企业 SLA
私密证明 Web 原生事实从可信网站数据生成 zkTLS 证明主网加基于 Reclaim 的 zkTLS无需披露原始页面内容即可证明技术仍早期,独立验证有限
启用多链 / 应用验证跨应用锚定并验证凭证数据Walrus 支撑的存储和 API更广的互操作性和去中心化控制架构由厂商描述,未经独立审计
支持机构金库操作在既有流程中托管并操作 HFireblocks 对 Humanity Mainnet 的支持降低机构操作摩擦金库支持本身不能证明企业采用身份产品

收益是产品层面的方向性判断,未经 KPI 审计。

[CE003, CE008, CE010, CE012, CE019, CE022]
FE002: 客户工作流 / 运营流程

典型产品流程从身份注册开始,叠加强证明和凭证,再把这些证明开放给应用或合作伙伴。

该流程是产品级通用描述,不是字面意义上的协议时序图。

[CE003, CE006, CE010, CE011, CE025]

5.2 最强公开技术证明来自文档和 SDK 接口层,而不是第三方基准

最能说明 Humanity 不只是故事的证据,来自其开发者接口层。SDK/API 文档明确把集成模型描述为类似 OAuth。公开的 TypeScript 和 React SDK 仓库展示了认证 URL、令牌交换、预设验证、凭证轮询、钩子和测试 mock 等具体流程,比许多私有加密身份项目发布的内容具体得多。GitHub 组织也显示出数十个仓库和 2026 年 8 月仍有更新 活动,暗示工程节奏仍在运行。架构侧的公开图景是分层的:主网加 zkTLS 用于证明 Web 原生事实,可由钱包持有并 选择性分享的凭证,以及可接入应用的 API 或智能合约接口。Walrus 通过描述去中心化节点、静态加密的凭证数据和 验证回执,补充了更明确的存储与验证架构。即便如此,可获得的证明大多仍是自我描述。公开记录显示了这套栈应该如何 工作;它并未独立验证这套栈能达到企业级表现。这在尽调中是一个有意义的优势,因为仓库和文档创造了可观察的实现细节。 它们揭示命名约定、开发者假设、支持的预设,以及团队期待第三方构建的应用类型。同时,如果没有生产参考客户、 性能遥测或正式保障证据匹配,它们也可能夸大成熟度。[CE008, CE012, CE013, CE014, CE015, CE016]

技术 / 运营架构表
层 / 组件作用依赖风险
掌纹生物识别层支撑更强的真人唯一性证明用户设备采集加生物识别流程准确率、反欺骗和隐私控制未经过独立基准测试
Human ID / DID 层锚定用户身份并连接凭证协议账户模型和钱包端界面沉睡 ID 或低质量注册可能稀释实用性
凭证签发 / 存储私密存储和出示证明钱包、凭证格式和 Walrus 支撑的数据平面撤销和可移植性性能未公开量化
zkTLS / Reclaim 层将 Web 原生账户事实转为密码学证明Reclaim 式证明生成和可信网站兼容性仍处早期,依赖合作伙伴 / 生态支持
SDK / API 层让应用发起认证请求并检查凭证开发者文档、托管 API、GitHub 包速率限制、运行时间和 API 经济性均未公开
机构运营层让机构在主网上持有并操作 HFireblocks 及相关托管基础设施金库准备度可能快于终端用户的生产采用

架构根据文档、SDK 和官方帖子重建,而不是来自正式参考架构文档。

[CE008, CE012, CE014, CE019, CE020, CE022]
路线图 / 发布 / 开发阶段表
日期 / 阶段功能 / 里程碑状态含义来源
2024 测试网Human ID 预约和早期生态增长已完成在更强生物识别上线前搭起身份漏斗官方测试网帖子
2025-06 代币发行Fairdrop 和 staking 经济机制已完成围绕身份增长加入激励层官方 Fairdrop 和 big-moves 帖子
2025-2026 主网主网、zkTLS 和更丰富的凭证用例已完成 / 已上线产品从预约叙事转向活跃凭证工作流官方主网帖子和第三方报道
2026 掌纹上线掌纹扫描启动已完成 / 推出中成熟度高于仅候补的身份账户官方掌纹扫描帖子
2026 Walrus 集成去中心化存储和多链凭证管线已完成 / 已上线改善面向开发者和互操作性的架构叙事官方 Walrus 帖子
2026 Fireblocks 支持机构托管和金库操作已完成 / 已上线提升持有 H 的机构可操作性官方 Fireblocks 帖子

状态标签反映截至 2026-08-07 的留存公开证据,不代表内部路线图确定性。

[CE006, CE007, CE008, CE019, CE022, CE023]
FE001: 产品架构图

公开可见架构从用户验证向上延伸到凭证、开发者 API 和合作伙伴基础设施。

技术栈综合自文档、博客和 SDK README,并非公司发布的工程蓝图。

[CE002, CE003, CE008, CE012, CE019, CE022]

5.3 产品成熟度真实存在,但信任、可靠性和依赖尽调仍未完成

Humanity 值得肯定的是,它发布了一条相当可读的信任叙事。保护隐私的验证、钱包持有凭证、zkTLS、Walrus 上静态 加密的数据,以及事件响应界面,都说明团队理解身份产品的生死取决于敏感信息控制。Fireblocks 支持也显示出它愿意 接入更严肃的运营环境,而不是停留在纯投机代币应用。但公开记录的边界仍很明显。纳入来源不能证明 SOC 2、ISO 27001、 正常运行时间历史、误报率、活体测试质量或独立生物识别准确性研究。事件界面有用,但也提醒投资人:特权访问和运营 安全失误可以伤害整套栈。当前最佳判断是,Humanity 在生态广度、开发者工具和伙伴集成上的成熟速度,快于外部验证 保障。这对采用是好信号,但不足以关闭完整企业尽调。实践中,Humanity 应被当作基础设施产品,而不只是品牌项目来 判断。基础设施买家关心降级行为、事件响应、权限边界、撤销设计和伙伴依赖图谱。公开材料触及这些主题,但还 没有用风险敏感企业会期待的测试结果或审计材料把问题闭合。[CE022, CE023, CE026, CE027, CE028, CE029]

信任 / 质量 / 合规表
控制 / 信号状态范围缺口
保护隐私的验证叙事已有公开文档首页、协议、文档、博客叙事强于独立验证
钱包持有凭证模型已有公开文档可验证凭证和 SDK 流程未留存公开生产规模审计
静态加密的 Walrus 架构已有公开文档去中心化存储上的凭证数据和回执未留存第三方安全审查
事件恢复和透明度入口公开可见索赔门户和受损地址追踪器显示响应能力,也暴露运营风险
常规企业认证留存资料未见证据N/A需要 SOC 2 / ISO 或同等证明
正常运行时间 / 性能指标留存资料未见证据N/A需要延迟、吞吐量、失败率和可用性报告

本表区分真实公开控制和缺失的企业级保障证明。

[CE005, CE020, CE026, CE027, CE028, CE030]
FE003: 关键依赖图

Humanity 的公开技术栈依赖少数外部技术和运营伙伴。

DAG 突出已披露依赖,不覆盖所有内部基础设施组件。

[CE008, CE019, CE021, CE022, CE029]
FE004: 产品成熟度 / 能力图

公开证据显示,文档、集成和产品宽度更成熟;第三方验证和企业级保障仍弱。

单元格是由保留证据支撑的等级判断,不是基准测试分数。

[CE012, CE017, CE022, CE026, CE027, CE028]

5.4 图表

Chapter 06

06客户

6.1 客户故事横跨用户、开发者、机构和伙伴,但直接付费方披露仍偏轻

Humanity 的公开记录已不再支持对客户基础的狭义解读。最明显的用户是创建 Human ID、随后完成更强验证的终端消费者。 但纳入集合还显示至少四类额外细分:在身份基础设施上构建的开发者,使用 Open Campus 的教育或凭证发行方,通过 Moongate 触达的活动或忠诚度运营方,以及通过 Fireblocks 和 Mastercard 式集成触达的机构或金融分发方。这种广度 很重要,因为它说明 Humanity 可以讲一个多边平台故事,而不是单一应用故事。它也制造了一个反复出现的尽调问题。 公开材料很少区分买家、用户和付费方。学生、参会者、钱包持有人、机构或开发者都可能使用系统,但来源并不稳定披露 谁签了合同、合同是否进入生产,或任何披露标识是否代表有意义的经常性支出。对 Humanity 来说,这种模糊尤其重要, 因为一些最强公开证明由伙伴驱动。在普通 SaaS 公司里,标识列表或许仍暗示计费关系。在这里,一个被点名的对手方 可能只是分发盟友、生态集成方、钱包界面或用例展示方。因此,客户章节必须严格区分每项证明实际成立的内容。[CU001, CU002, CU013, CU014, CU020, CU021]

客户细分表
细分买方 / 用户 / 付款方主要用例规模 / 战略价值缺口
终端用户 / Human ID 持有人用户可见;付款方不清晰预约身份、证明真人、持有凭证留存资料中最大的漏斗顶部基础用户数不等于收入数
开发者 / dApps开发者集成;付款方不清晰加入真人感知认证或凭证检查对生态增长至关重要付费方案和留存未披露
教育生态通过 Open Campus 触达学生、教育者和机构签发并验证教育凭证显示向非加密原生场景扩张的路径未披露机构合同数量
活动 / 忠诚度生态通过 Moongate 触达活动运营方、社区和参会者票务、门禁、奖励、身份绑定参与最强的现实世界部署证明收入贡献未披露
机构 / 托管 / 金库通过 Fireblocks 触达机构在主网上托管并操作 H提升可操作性和触达本身不能证明 Human ID 使用
金融服务 / 开放金融Mastercard thesis 指向的用户和贷款方 / 服务提供商可复用的金融资格和身份凭证进入现实金融的潜在桥梁仍停留在公告级证明

各细分把可见用户、合作伙伴渠道和未披露的直接付款方分开。

[CU001, CU004, CU006, CU008, CU012, CU020]
客户增长 / 采用轨迹表
指标日期来源置信度含义缺失分母
Human ID 数1M+2024-12/2025官方增长帖子显示早期用户采用活跃 ID 与沉睡 ID 未知
Human ID 数量~7M2025-Q2官方测试版更新显示漏斗大幅增长已验证与未验证的拆分不明
钱包~10M2025-Q2官方测试版更新指向较大的账户关联覆盖面付费用户占比不明
Moongate 门票300,000+2026Moongate 收购公告显示线下活动分发基础不等同于 Humanity 原生付费客户
可通过 Fireblocks 触达的机构2,400+2026Fireblocks 集成公告显示广泛的机构渠道触达触达不等于活跃使用
通过 Fireblocks 支持的区块链网络130+2026Fireblocks 集成公告表明已进入现有运营栈的分发路径不衡量实际客户采用

这些是采用或触达指标,不是收入 KPI。

[CU003, CU007, CU009, CU021, CU028]
FU001: 客户旅程图

Humanity 的客户采用常从用户或合作伙伴问题切入,再沿身份、凭证和生态集成扩展。

旅程图概括多个细分市场的可见客户逻辑,并非每类买家的字面漏斗。

[CU001, CU002, CU020, CU025]
FU002: 采用 / 部署漏斗

公开证据在漏斗顶部最强;问题转向变现和留存后,证据变薄。

数值是证据权重等级,不是实际客户数。

[CU003, CU007, CU009, CU017, CU018, CU028]

6.2 具名证明最强的地方,是 Humanity 接入既有生态的地方

纳入集合中最好的客户证据,是具名且针对具体用例的。Open Campus 给 Humanity 提供了围绕可互操作学习者凭证和 面向机构采用的具体教育叙事。Moongate 提供了最清晰的现实世界访问案例,覆盖票务、访问控制,以及收购前已披露的 30 多万张链上门票足迹。Fireblocks 提供的是机构可运营性,而不是终端客户身份证明,但它仍重要,因为它降低了已经 活跃于数字资产的机构的工作流摩擦。Walrus 展示 Sui 相邻基础设施上的开发者如何消费身份信号;韩国 hackathon 文章则显示生态建设者在实践中使用这些接口。Mastercard 叠加了围绕开放金融驱动 Human ID 的金融服务 野心层。合在一起,这些具名证明展示出跨多个垂直领域可信的先落地再扩张逻辑。它们还没有展示的是 ACV、合同 期限或续约质量的直接透明度。额外的钱包、移动应用和机构分发文章加深了这幅图景。D’CENT 和 Hex Trust 把故事延伸到 钱包和机构支持入口;移动应用发布则暗示 Humanity 正试图把生态认知转化为更可重复的消费者入口。这些都是有用证明点, 但仍更接近赋能和渠道扩张,而不是已披露合同收入。[CU004, CU005, CU006, CU007, CU008, CU009]

具名客户证明表
客户 / 合作伙伴细分领域部署 / 用例生产还是试点结果局限
Open Campus教育凭证将 Open Campus ID 和成就接入 Humanity 凭证战略集成 / 可能仍是早期部署保留样本中最强的教育领域证明未公开合同规模或机构数量
Moongate活动 / 准入 / 忠诚度票务、准入控制、忠诚度和身份绑定参与既有平台叠加收购后集成300,000+ 张链上门票提供了少见的具体分发证明仍未披露收入或 Human ID 绑定率
Fireblocks机构托管 / 资金管理在现有机构运营中支持 Humanity Mainnet 和 H合作伙伴平台已生产支持显示已打通大型机构渠道的运营入口资金管理支持不能证明身份客户直接采用
Mastercard金融身份 / 开放金融将 Human ID 接入可复用的金融验证流程战略集成 / 早期动作显示切入信贷准入的野心未披露收入、上线规模和客户量

具名证明按部署证据的具体程度排序,而不只看传播声量。

[CU004, CU006, CU007, CU008, CU009, CU012]
FU003: 客户证明矩阵

具名证明在部署具体度和经济可见度上差异明显。

单元格是基于保留来源细节的等级判断,不是合同披露。

[CU004, CU006, CU008, CU010, CU012, CU032]

6.3 耐久性、集中度和变现仍是私有信息

一旦问题从存在性证明转向耐久性证明,客户章节就会转为谨慎。公开记录没有披露付费客户数、留存、净收入留存、毛留存、 流失、满意度或按收入计的客户集中度。它也高度依赖生态对手方;这对扩张有用,但如果伙伴没有转化为直接客户经济, 风险也高。漏斗顶部用户和钱包指标同样容易被过度解读。它们证明采用兴趣,不证明合同质量。负面证据在这里也重要。 2026 年 6 月攻击及随后的治理争论,会压低信任敏感买家的意愿,尤其是当身份产品要求用户和伙伴依赖长期凭证时。 因此,正确承销立场是混合的:Humanity 比许多早期身份协议有更强具名证明,但公开集合在续约、ACV 和集中度上仍太薄, 不能称客户账本耐久。这个缺口重要,因为许多早期加密公司可以展示生态热情,却无法证明一套耐久业务。除非 Humanity 披露重复使用、合同经济,以及多少具名伙伴已完全投入生产,投资人应把客户故事视为有希望,但仍由合作叙事中介。[CU003, CU017, CU018, CU019, CU022, CU023]

留存 / 重复使用 / 满意度表
指标数值 / null客群置信度尽调追问
NRR全部付费客户索取按客户细分和合作伙伴导入批次拆分的 NRR
GRR全部付费客户索取 GRR 和客户流失率
合同期限企业 / 合作伙伴渠道索取标准合同期限和续约机制
重复使用率终端用户 / 凭证持有人索取 MAU 与凭证使用的比率
客户满意度 / 评价全部细分索取客户访谈、NPS 或外部评价证据

这些 null 是有意保留,因为保留的公开记录未披露耐久性指标。

[CU017, CU018, CU031]
扩张与集中度风险表
扩张驱动集中度风险影响尽调路径
教育凭证可能停留在单一旗舰合作限制机构端可复制性的证明索取 Open Campus 推广进度和机构数量
活动与忠诚度可能过度依赖收购来的 Moongate 渠道扩张更像合作伙伴带动,而非原生增长索取 Moongate 客户名单和绑定率
通过 Fireblocks 进入机构运营触达可能无法转化为活跃身份工作流可能夸大企业端牵引力索取使用 Humanity Mainnet 的活跃机构账户数
通过 Mastercard 切入金融身份高曝光可能掩盖生产规模偏低可能停留在愿景,而非收入驱动索取上线地区、合作伙伴漏斗和活跃用户指标
代币激励增长闭环Fairdrop 带来的获客未必等于留存可能抬高漏斗指标,却没有耐久客户索取激励获客批次与自然获客批次的留存对比

可见最大风险是证明和规模仍依赖中介型合作伙伴。

[CU022, CU023, CU024, CU025, CU026, CU027]
FU004: 客户证明流与耐久性缺口

公开证明从合作伙伴公告到可见用例这段很顺;一问到续约、ACV 和集中度,证据就转弱。

该流程显示,保留客户集中的证据在哪里变薄。

[CU014, CU017, CU019, CU023, CU034, CU035]

6.4 图表

Chapter 07

07风险

7.1 生物识别身份带来密集的隐私、制裁和跨境法律暴露

Humanity 不只是另一个加密代币项目。其条款和隐私政策清楚显示,掌纹验证、生物识别处理、制裁控制和对司法辖区敏感 的访问限制,都是核心服务模型的一部分。这立刻把公司置于比典型消费者应用更严苛的法律环境。香港隐私规则强调合法、 公平收集、留存纪律和安全。GDPR 对生物识别数据的处理更严格,因为特殊类别数据不能被随意处理。如果 Humanity 的 可复用凭证触达金融或消费者语境,美国隐私和安全预期也重要。公司自己的文件又增加一层:它们考虑供应商存储、在适用 法律下披露生物识别数据,以及 BVI 管辖条款下的广泛暂停权。换句话说,风险不只是“监管也许有一天会到来”。敏感数据、 跨境、制裁和治理暴露已经写进运营设计。对投资人来说,关键含义是 Humanity 不能躲在“去中心化身份”这个说法后面。 去中心化可以降低部分中心化数据库风险,但公司自己的法律文件显示,链下治理、处理方、执法请求、制裁逻辑和生物识别 数据处理,都是现实世界运营模型的一部分。产品主张与这些运营现实之间只要出现错配,就可能很快变成法律和声誉问题。[CR001, CR002, CR003, CR004, CR005, CR006]

监管 / 法律风险登记表
风险证据触发因素司法辖区 / 场所可能性严重性缓释成熟度剩余敞口尽调路径
生物识别数据处理限制GDPR 第 9 条和隐私政策披露EU / 跨境低到中索取法律依据、DPIA 和跨境数据流图
香港隐私合规PDPO 要求公平收集、留存和安全保护香港中到高低到中索取香港合规备忘录和处理方控制
制裁 / 禁止司法辖区敞口条款内嵌制裁和禁止司法辖区限制BVI / 全球中到高索取制裁控制、筛查供应商和申诉流程
隐私承诺执法风险FTC 式预期:隐私声明要与实际做法一致美国 / 消费者保护中到高低到中中到高对比隐私声明与实际存储、披露和供应商做法

这些行按保留公开来源中证据最强的法律与监管敞口排序。

[CR001, CR002, CR004, CR006, CR007, CR008]
FR001: 风险热力图

生物识别、特权访问和合作伙伴驱动采用交汇处,残余风险最高。

热力图用基于保留证据的等级排序,不使用合成概率。

[CR007, CR008, CR014, CR023, CR025, CR037]

7.2 2026 年 6 月攻击证明,运营安全是论点级风险

事件记录异常重要,因为它揭示了失败在实践中如何发生。Quantstamp 总结、第三方报道和恢复界面都指向同一方向: Humanity 2026 年 6 月事件由钓鱼、恶意软件和被盗特权密钥驱动,而不是传统智能合约 bug。这个区分有实质意义。 它意味着公司的真实攻击面包括人员操作、密钥备份、桥管理和钱包卫生,而不只是链上代码。事件规模同样重要。报告指向 未授权铸造、大规模代币盗窃,以及被流动性池、金库、智能合约仓位和快照后购买者复杂化的恢复流程。公司用事件总结、 透明度工具、迁移机制和补偿流程回应,这是建设性的。但同一组动作也展示出,一个核心承诺是信任的产品背后,如今有 多复杂的运营系统。因此,事件应被解读为控制系统失效,而不只是糟糕标题。智能合约审计无法阻止被钓鱼的操作员、被盗 签名密钥或被攻破的桥管理。投资人因此需要证明,公司在攻击后改变了人员、流程和基础设施控制,而不是只替换代币后继续前进。[CR013, CR014, CR015, CR016, CR017, CR018]

运营 / 质量 / 安全风险登记表
失效模式证据触发因素可能性严重性缓释成熟度剩余敞口未解决缺口
特权密钥泄露 / 钓鱼Quantstamp 摘要和第三方黑客事件报道严重需要事后密钥管理重设计证明
复杂恢复边界情况索赔门户和赔偿机制中到高需要索赔解决统计和剩余责任
合作方重启 / 迁移执行需要协调交易所、桥和合作伙伴中到高中到高需要迁移完成指标和合作伙伴确认
缺少公开保障指标无公开正常运行时间、认证或生物识别基准需要审计材料、SLA 数据和独立测试

运营行聚焦 2026 年事件及周边披露中证据最直接的风险。

[CR013, CR014, CR015, CR018, CR019, CR020]
FR002: 风险传导图

Humanity 的主要风险沿信任、合规和合作伙伴渠道传导,影响客户增长、财库灵活性和估值。

展示因果方向,不量化损失概率。

[CR010, CR021, CR023, CR028, CR035, CR040]

7.3 伙伴依赖、竞争压力和缺失的运营证明,让剩余暴露仍然很高

即便隐私和事件风险都被完美控制,Humanity 仍会面临严肃执行挑战。最强的公开采用证明很多都穿过对手方:Walrus、 Fireblocks、Open Campus、Moongate、Mastercard 和其他生态伙伴。这些关系有价值,但也意味着 Humanity 的公开 牵引力部分借自它无法完全控制的外部基础设施。竞争又增加一层。反机器人和真人证明问题在增长,这有利于品类需求; 但对手路线仍然可用,未来任何安全或隐私争议都可能把伙伴或用户推向替代方案。与此同时,投资人仍缺少认证、正常运行 时间、直接付费客户留存,或多少伙伴公告已转化为耐久商业部署的强公开证据。结果是,风险画像被可见缓释措施改善, 但仍高度暴露于复发、合规摩擦,以及从生态兴趣转化为可信运营结果时的失望。伙伴故事放大了这个担忧。如果采用仍主要 由伙伴驱动,那么每增加一次集成,公司必须处理的外部信任、运营协调和失效面管理都会增加。在这些条件下,增长仍可能 有吸引力,但前提是底层控制环境变得明显强于 2026 年 6 月时的样子。[CR022, CR023, CR024, CR025, CR026, CR027]

合作伙伴 / 依赖风险登记表
依赖交易对手 / 渠道角色集中度线索失效场景严重性缓释措施剩余敞口
去中心化存储与开发者访问Walrus / Sui 相邻生态凭证存储与验证路径公开架构依赖具名合作伙伴集成合作伙伴宕机或战略变化会扰动数据层记录备用架构和可移植性
机构可操作性Fireblocks托管和资金管理分发通道机构叙事依赖合作伙伴触达说法支持若落地不及预期,机构入口叙事会走弱分散托管和集成路径中到高
教育凭证Open Campus垂直领域凭证渠道单一旗舰证明可能夸大更广泛的教育牵引力教育采用停留在象征层面中到高展示更多发行方和上线机构中到高
活动与忠诚度Moongate线下准入与活动采用通道最强线下证明来自收购渠道绑定和变现低于预期披露绑定率和收购后增长中到高
金融身份Mastercard / 开放金融路径通向现实金融服务的桥仍是公告层面的证明金融服务动作未能越过公关层面完成转化披露上线指标和交易对手

依赖风险升高,因为由合作伙伴中介的证明仍多于直接付费客户披露。

[CR022, CR023, CR024, CR028, CR039]
人员 / 执行风险登记表
角色 / 职能依赖或缺口可能性严重性缓释措施尽调路径
特权操作员 / 董事事件显示,单个设备被攻破可能级联成协议危机中到高严重事件后加固和密钥隔离索取组织架构图、签名人政策和设备控制变更
安全领导 / IR 流程需要可复用的事件响应,而不只是一次紧急处置固化 IR 手册并引入外部取证索取 IR 桌面演练和审计排期
合规 / 隐私运营跨境生物识别和制裁义务密集专门的隐私与制裁治理索取 DPO / 合规权责图
合作伙伴管理 / GTM采用逻辑分散在多个交易对手身上结构化合作伙伴治理和成功指标索取合作伙伴评分卡和续约 / 使用指标

人员风险升高,因为公开记录已显示一条以操作员为中心的失效路径。

[CR004, CR014, CR034, CR035, CR039]
缓释与叫停标准表
风险可监测触发因素阈值 / 事件行动含义
特权密钥事故复发出现涉及签名人、管理员或桥密钥的新事件迁移后运营稳定前出现任何复发升级为投资逻辑破裂,并冻结投资测算
隐私 / 监管升级正式监管行动、重大投诉或被迫改变数据流程EU、香港或关键市场出现任何重大动作重新测算增长和法律准备金假设
合作伙伴集中,但缺少直接客户证明具名合作增加,但仍没有收入 / 留存披露再过 2-3 个季度仍只有证明、没有客户经济性细节下调客户转化假设
保障缺口仍未补齐仍无公开认证、正常运行时间数据或独立生物识别测试到下一轮重大融资或企业端推进前维持高剩余风险折价
恢复执行受挫赔偿延迟、索赔争议或迁移混乱持续存在未解决索赔人积压仍有实质规模上调信任和诉讼风险假设

叫停标准强调可衡量事件;这些事件会很快推翻以信任为核心的身份投资逻辑。

[CR018, CR019, CR025, CR036, CR037, CR038]
FR003: 依赖图

关键外部依赖集中在存储、托管、分发和监管合法性。

依赖图只覆盖保留证据集中最显眼的外部具名依赖。

[CR022, CR023, CR024, CR035, CR039]

7.4 图表

Chapter 08

08估值

8.1 市场把 Humanity 重新定价到低于融资头条,但还谈不上明显便宜

最容易犯的估值错误,是盯住单一数字。只看 2025 年 1 月 11 亿美元完全稀释估值,Humanity 仍像一只受伤后等着恢复的独角兽;只看今天约 1.7 亿美元的流通市值,又像已经彻底坏掉。两种读法都不够。更克制的做法,是把三个公开标尺放在一起:上一轮融资 FDV、实时代币 FDV、实时流通市值。这个框架能看出黑客事件后的真实重置,但不是网络意义归零。它也解释了为什么这家公司仍难承销:价格跑得远快于披露质量。投资者仍看不到公开的收入、利润率、留存或资金库明细。也就是说,市场发现的是一个代币价格,不是站得住脚的内在价值。在代币化系统里,这个区别更关键:供给机制可以撑住很大的名义 FDV,而当前持有人能兑现的市场价值小得多。忽视这个价差,投资者会把稀缺误判成便宜;忽视剩余战略价值,又会反过来把资产按网络完全没有未来期权来定价。[CV001, CV002, CV003, CV004, CV005, CV006]

FV002: 估值敏感性

最能支撑的公开估值标记,是上一轮融资、当前实时 FDV 和当前流通市值。

柱状图比较不同语境下的公开标记;它们不是同口径企业价值。

[CV001, CV002, CV004, CV006, CV008]

8.2 上行来自战略期权,下行来自未解的信任和披露风险

没有理由把 Humanity 一笔抹掉。它产品线有宽度,有具名伙伴,也踩在 bot、欺诈和可复用凭证这些正在 crypto 和 AI 工作流里变大的问题上。Fireblocks、Moongate、涉及 Mastercard 的报道和其他集成表明,只要执行改善,身份图谱可以接入多条变现路径。但看空理由同样成立。2026 年 6 月的攻击永久改写了叙事。安全修复、治理可信度和代币供给治理,如今已经和估值绑在一起。企业 AI 转向未来可能拓宽机会,但按现有证据,它在带来更多现金流之前,主要先增加执行不确定性。投资者因此一边被要求为期权和修复买单,一边还缺少给企业定价所需的常规经营数字。[CV010, CV011, CV012, CV013, CV014, CV015]

投资论点 / 反论点表
论点证据什么会改变判断
多头论点:身份赛道需求真实,Humanity 有可信的选择权具名合作伙伴路径、较大的用户漏斗,以及覆盖凭证和信任工作流的产品宽度需要证明选择权能转成付费客户经济性
多头论点:市场已经重估了大量坏消息当前公开 FDV 低于此前 $1.1B 融资基准需要证明实时代币价格稳定,而不只是叙事反弹
反方论点:黑客事件造成持久治理折价漏洞利用、恢复机制和转向叙事仍主导市场故事需要持续证据证明控制更强、信任在恢复
反方论点:缺少收入披露,所有估值判断都很脆弱没有公开收入、利润率、留存或金库数据需要运营指标和金库治理披露

每条论点都对应一项会提升或下调判断的尽调事项。

[CV010, CV011, CV012, CV013, CV014, CV024]
FV001: 建议逻辑

建议从战略相关性出发,经过风险和披露约束,落到对价格敏感的继续研究立场。

建议逻辑是因果链,不是量化模型。

[CV010, CV012, CV013, CV026, CV029, CV040]
FV003: 估值 / 回报区间

公开证据支持很宽的区间,因为估值更取决于信任修复和运营证明质量,而不是单一干净 KPI。

区间来自公开标记和叙事风险推导的情景输出,不是折现现金流。

[CV032, CV033, CV034]

8.3 公开可比公司更多说明披露折价,而不是给出干净倍数

可比分析只有保持谦逊才有用。Okta、Coinbase 和 Palantir 规模大得多,透明度也远高于 Humanity。它们的市值展示了身份软件、上市 crypto 基础设施和高溢价数据平台叙事的上限,但对尽调最大的价值是披露对照。上市公司文件会把收入、利润率、流动性、风险和治理说清楚,Humanity 做不到。这不等于 Humanity 没有价值;这意味着投资者在借用任何上市公司光环之前,先要打上很重的披露和治理折价。因此,本章可比表是框架工具,不是把 Humanity 硬塞进一个公开记录无法支持的伪收入倍数。公开可比仍能用来校验野心:当身份与信任业务把赛道位置、可验证经济性和可信控制环境配在一起时,可以长得很大。Humanity 已经站在赛道上;缺的是一层证据,让外部人知道这种位置是否正在复利成持久企业价值。[CV016, CV017, CV018, CV019, CV020, CV021]

牛 / 基准 / 熊情景表
情景核心假设估值区间概率信号
信任拖累延续,未披露有意义的变现,代币价值被压回现货市值逻辑$0.3B-$0.5B FDV如果修复叙事转弱或又出现控制问题,概率上升
基准没有新事故,伙伴选择权仍在,但经济性披露不足$0.7B-$0.9B FDV按当前公开证据最可能
伙伴路径转成可信的企业或金融工作流,信任重建经得住时间$1.1B-$1.4B FDV需要硬运营证据和信用修复

情景区间是基于公开市场标记和叙事风险的分析输出,不是管理层指引。

[CV032, CV033, CV034]
可比估值表
可比对象指标 / 日期估值或倍数状态相关性局限
Humanity 2025 年融资2025 年 1 月轮融资$1.1B FDV历史私募基准市场预期最好的历史锚FDV 不等同于经审计企业价值
Humanity 2026 年实时交易2026 年 8 月公开代币指标~$170M 现货市值 / ~$852M FDV当前市场信号当前最好的公开定价指标受代币交易和供应假设驱动
Okta2026 年 8 月市值~$26.0B公开身份软件可比公司显示披露充分的身份软件规模化后可交易到什么水平商业模式不同,且公开披露完整
Coinbase2026 年 8 月市值~$39.5B公开加密基础设施可比公司给上市加密原生基础设施的规模定位交易所模式差异很大
Palantir2026 年 8 月市值~$404.8B公开数据平台天花板可作为「叙事 + 披露」上限可比规模大得多,经济性不可比

可比集合刻意保持小而示意性,不追求穷尽。

[CV001, CV004, CV018, CV019, CV036]
FV004: 投资 KPI

实时市场给出的信号足以评估价格和风险,但不足以有把握地评估业务质量。

KPI 混合数字和类别标记,因为公开证据在市场定价上比运营更强。

[CV001, CV004, CV005, CV026, CV028, CV040]

8.4 在收入和控制证据改善前,最站得住脚的结论是继续研究

最终建议会故意让动量投资者不够满意。按公开证据,Humanity 还没有便宜到可以轻松买入,也没有坏到可以完全放弃。在当前附近的代币市场水平,这个故事只对能承受高风险、经营证据不完整,并且接受重大事故后重建信任这一前提的投资者有吸引力。转向买入,需要收入、留存、资金库治理和黑客事件后安全控制的硬证据。转向回避,则可以由又一次控制失败,或持续无法把生态关系转成持久经济性来证明。剩下的正确结论就是继续研究:中等信心、高风险;按实时价格看估值公平到偏投机,按旧融资头条看则偏贵。[CV026, CV029, CV030, CV031, CV032, CV033]

投资建议摘要表
视角当前判断证据基础决策含义
投资建议继续研究代币二级市场价格可见,但业务经济性仍不公开。只有在尽调更深、价格更克制时才继续跟进。
信心价格和融资历史可见,收入与金库数据不可见。用区间和条件假设,不给单一目标。
风险评级黑客事件后的信任修复、供应抛压和伙伴转化仍未解决。先按下行情景承销。
估值立场现价附近介于合理与投机之间;接近 $1.1B FDV 时偏贵当前定价低于上一轮融资口径,但披露质量仍弱。不要只锚定历史融资。

摘要表刻意让结论随价格和证据变化。

[CV026, CV027, CV028, CV029, CV040]
论点破坏与否决触发表
触发项阈值对论点的传导行动含义
重复安全失误任何新的特权密钥或恢复控制事故摧毁信任重建论点从「继续研究」转为「回避」
运营披露没有进展到下一次主要融资周期仍没有收入 / 留存 / 金库披露估值仍纯靠叙事驱动维持大幅折价,或直接放弃
伙伴证明仍停留在象征层面合作数量增加,但直接经济性仍缺位多头情景无法转成业务质量下调上行假设
代币供应治理恶化解锁或金库行为削弱市场信心基于 FDV 的多头逻辑明显削弱重估到更低情景区间

否决触发项聚焦那些会迅速推翻代币驱动修复论点的事件。

[CV030, CV031, CV035, CV038]
最终尽调问题表
主题缺失证据重要性负责人或尽调路径
收入与毛利率没有公开收入或利润率数据需要它把代币叙事转成业务价值管理层 / 资料室
留存与客户经济性没有 NRR、GRR、ACV 或队列披露需要它检验伙伴驱动故事是否持久管理层 / 客户队列材料
金库与供应治理没有详细金库构成或出售政策需要它判断稀释和抛压风险基金会 / 金库委员会
黑客事件后的控制变更没有独立证据证明密钥管理或运营控制已重新设计需要它承销复发风险安全审计 / 外部评估方
伙伴转化关键集成没有量化收入或生产落地深度需要它给选择权理性定价伙伴评分卡和已签客户证据

这些是给出高确信度投资建议前必须完成的最低限度工作流。

[CV030, CV035, CV038, CV040]

8.5 图表

免责声明

本报告基于截至 2026-08-07 的公开信息,不构成投资建议。Humanity Protocol 是一家未上市的代币网络企业,财务披露有限,因此估值、客户质量和治理结论仍部分基于推断。

证据索引

结论
编号陈述可信度来源
CO001 Humanity’s homepage presents the protocol as an internet trust layer that verifies claims without requiring parties to store user data. SO001
CO002 Humanity says zero-knowledge proofs can verify attributes such as age, income, or identity without revealing the underlying personal data. SO001
CO003 The official positioning spans enterprise verification use cases, consumer Human IDs, and developer-facing sybil-resistant applications rather than a single narrow workflow. SO001, SO002
CO004 Humanity’s docs define the protocol as a scalable decentralized EVM-based proof-of-humanity solution built around biometric data. SO024, SO002
CO005 Humanity’s documentation says its mobile app captures palm prints while dedicated scanners use infrared vein mapping, with both paths protected by zero-knowledge proofs. SO025, SO011
CO006 Official and executive materials frame palm recognition as a less invasive, more scalable alternative to iris-based proof-of-personhood systems. SO004, SO010, SO011
CO007 Terence Kwok is the publicly visible founder and CEO of Humanity Protocol across retained launch and interview materials. SO004, SO008, SO009
CO008 Public materials place Humanity’s operating identity across Hong Kong, Dubai, and New York, with later interviews most clearly describing the company as Hong Kong based. SO003, SO004, SO008
CO009 The strongest retained public evidence supports a 2024 public emergence from stealth, while a precise earlier formal founding date is not clearly documented in open sources. SO003, SO004, SO016
CO010 Humanity announced a $30 million seed round in May 2024 led by Kingsway Capital at a $1 billion valuation. SO003, SO016
CO011 The May 2024 round included Animoca Brands, Blockchain.com, Hashed, Shima Capital, and other crypto-native investors. SO003
CO012 Humanity raised $20 million in January 2025 from Pantera Capital and Jump Crypto at a $1.1 billion fully diluted valuation. SO005, SO006, SO007
CO013 The two disclosed 2024-2025 fundraisings establish at least $50 million of public capital raised. SO003, SO005, SO006
CO014 Management and coverage linked the January 2025 round to Human ID expansion, proof-of-humanity development, ecosystem integrations, and mainnet or token rollout. SO005, SO007, SO008
CO015 Humanity said it collected more than 500,000 waitlist signups within one month of emerging from stealth. SO003
CO016 Humanity’s public testnet began in September 2024 as the first phase of a three-phase rollout centered on reserving a unique Human ID. SO013, SO016
CO017 By late 2024 Humanity reported that the testnet had reached one million Human IDs roughly three months after launch. SO016
CO018 An official 2025 roadmap post said the earlier testnet launch had already brought in over five million Human IDs. SO014
CO019 Humanity’s testnet-beta post later reported close to seven million Human IDs, nearly ten million wallet addresses, and over five million RWT holders. SO013
CO020 The palm-scan app rollout began after Humanity said more than eight million users had already reserved Human IDs. SO017
CO021 Humanity’s first fairdrop launched $H on major exchanges on 25 June 2025 and presented the token as the basis for rewards, staking, governance, and validator incentives. SO015
CO022 Official copy frames Human ID as a reusable passport across Web3 and other settings rather than as a one-off login credential. SO001, SO015
CO023 Mainnet launch coverage said Humanity went live with zkTLS so users could prove claims from familiar web2 credentials without exposing the underlying page or account data. SO018, SO019
CO024 At mainnet launch, reported integrations included travel and hospitality loyalty programs from Delta, Emirates, Singapore Airlines, Marriott, and Hilton. SO019
CO025 Launch reporting also positioned Humanity as supporting financial, educational, and professional credentials in addition to travel-linked identity proofs. SO019
CO026 Management said Humanity planned palm-scan rollout milestones across select cities in Asia and Europe during 2025. SO010
CO027 Independent coverage consistently treats Humanity as a direct Worldcoin alternative because it uses palm biometrics where Worldcoin uses iris scans. SO010, SO021, SO022
CO028 Management claims raw biometric information is not kept in centralized stores and is instead shielded through zero-knowledge or segmented credential design. SO010, SO011
CO029 Humanity’s public posture now spans consumer onboarding, developer tooling, validator incentives, and enterprise credential use cases at the same time. SO001, SO015, SO019
CO030 The official blog index shows the roadmap extending beyond core identity into Open Campus, Moongate, and Mastercard-linked credential initiatives. SO012
CO031 The retained open record does not provide a reliable current employee count, executive-bench disclosure, or full foundation-governance map for 2026. SO003, SO012, SO026
CO032 Humanity’s strongest public traction indicators are Human IDs, wallet addresses, referrals, and points holders rather than disclosed paying customers or revenue. SO013, SO014, SO015
CO033 The phase-two palm-scan rollout moved Humanity from identity reservation toward actual biometric verification and future attestations. SO017, SO013
CO034 BanklessTimes framed Humanity’s spring 2026 token surge largely as flow captured from Worldcoin’s credibility collapse rather than as proof of independent business fundamentals. SO022
CO035 A June 2026 Crypto Times report said Humanity suffered a roughly $30-32 million exploit involving unauthorized minting and sales of $H across Ethereum and BNB Chain, after which the token fell by about 86%. SO023
CO036 The same adverse report said critics questioned whether privileged-key management, insider controls, or market-making practices were too concentrated around Humanity’s token infrastructure. SO023
CO037 By mid-2026 Humanity’s public story had become a mix of strong onboarding momentum and materially higher trust, governance, and security scrutiny. SO013, SO017, SO023
CO038 Later chapters should treat valuation, customer monetization, and mature governance quality as less verified than identity-growth metrics and protocol ambition. SO013, SO014, SO022, SO023
CM001 Humanity’s market is best framed as a privacy-preserving identity and proof layer rather than as a pure crypto-token product. SM001, SM002, SM003
CM002 The included spend relevant to Humanity covers biometric proofing, proof-of-personhood, credential issuance and reuse, and selected KYC, loyalty, and anti-fraud workflows. SM001, SM002, SM007, SM025
CM003 Humanity does not address the full IAM, password-management, or generic security-operations markets, so those budgets should be excluded from its realistic market boundary. SM001, SM002, SM014
CM004 Status-quo alternatives to Humanity include centralized KYC vendors, social-login identity providers, manual review, CAPTCHAs, and adjacent proof-of-personhood systems such as World ID. SM013, SM020, SM021
CM005 Mordor Intelligence estimates the identity-verification market will grow from $15.78 billion in 2026 to $26.8 billion in 2031 at 11.18% CAGR. SM008
CM006 Mordor Intelligence estimates the biometrics market will grow from $67.86 billion in 2026 to $136.86 billion in 2031 at 15.07% CAGR. SM009
CM007 Financial services accounted for 30.72% of identity-verification market share in 2025, making regulated onboarding the largest current spend pool in the retained source set. SM008
CM008 Gaming and gambling is one of the fastest-growing identity-verification segments in Mordor’s market view, growing at 11.24% CAGR. SM008
CM009 Biometric verification led the identity-verification market by solution type in 2025 with 35.84% revenue share. SM008
CM010 Cloud platforms held 65.12% of identity-verification market share in 2025, showing that buyers increasingly expect software-delivered orchestration rather than only appliance-based systems. SM008
CM011 Within biometrics, hardware still leads current revenue while software is forecast to grow fastest at 16.35% CAGR through 2031. SM009
CM012 Contactless biometric systems are growing faster than contact-based ones, which is directionally supportive for smartphone- or scanner-based palm capture models. SM009
CM013 Government and law enforcement represented 38.10% of the biometrics market in 2025, underscoring how much biometric spend sits outside Humanity’s immediate Web3 wedge. SM009
CM014 North America leads current identity-verification and biometrics spending, while Asia-Pacific is the fastest-growing geography in both market lenses. SM008, SM009
CM015 FATF says reliable digital ID can make customer due diligence easier, cheaper, and more secure while also supporting transaction monitoring and financial inclusion. SM010
CM016 NIST SP 800-63-4, finalized in July 2025, sets updated digital-identity guidance spanning identity proofing, authentication, and federation. SM011
CM017 The European Commission’s digital identity program is designed to let people prove identity electronically and use wallet-linked trust services across borders. SM012
CM018 The World Economic Forum notes that roughly 850 million people still lack legal ID and many more lack privacy and control over how their data is shared. SM013, SM014
CM019 WEF’s privacy-preserving digital ID analysis argues that decentralized credentials can reduce the panopticon problem of centralized identity providers that observe every identity transaction. SM013
CM020 WEF’s Reimagining Digital ID report says decentralized ID could help expand access and user control but still needs fit-for-purpose policy, regulation, and technology to deliver social benefit at scale. SM014
CM021 WEF’s ethics article says future digital identity systems raise serious questions about consent, dignity, authenticity, and misuse as AI-generated replicas become easier to create. SM015
CM022 Entrust says identity fraud has become industrialized and that deepfakes now represent one in five biometric fraud attempts. SM016
CM023 Entrust reports that injection attacks rose 40% year over year and deepfaked selfie attempts increased 58% in one year. SM016
CM024 LexisNexis says synthetic identities now account for 11% of fraud and have increased eight-fold globally year over year. SM017, SM019
CM025 LexisNexis says agentic traffic grew 450% between January and December 2025 while malicious bot attacks rose 59% over the year. SM017
CM026 ID.me says generative AI removes historical bottlenecks in synthetic identity creation and that attackers now target liveness systems with injection-based deepfakes. SM018
CM027 ID.me argues that identity verification can no longer be treated as a one-time checkpoint because fraud now exploits the entire workflow continuously. SM018
CM028 Humanity’s realistic market wedge is the subset of identity demand where buyers care about proving a unique human and reusing that proof across applications. SM001, SM003, SM006, SM007
CM029 Web3 protocols are likely the earliest paying segment because Humanity’s fairdrop and anti-sybil story directly targets farmer resistance, validator incentives, and governance integrity. SM006, SM020, SM021
CM030 Travel, hospitality, fintech, education, and professional credentials are adjacent buyers where reusable trust signals can lower repeated onboarding friction. SM007, SM001, SM025
CM031 The buyer-user-payer split varies by segment, with compliance teams paying in regulated onboarding while product, partnership, or foundation budgets pay in web3 and loyalty-oriented use cases. SM007, SM010, SM025
CM032 Adoption depends on a chain of steps from enrollment to stronger verification to issuer acceptance and cross-platform reuse, so network effects are possible but not automatic. SM023, SM024, SM007, SM017
CM033 Standards fragmentation, privacy law, and cross-border assurance requirements are likely to slow deployment even if raw demand for digital identity rises. SM010, SM011, SM012, SM014
CM034 Broad biometrics or identity-verification TAMs overstate Humanity’s opportunity because large portions of those markets do not require decentralized credentials or proof-of-personhood. SM008, SM009, SM014
CM035 The strongest present demand driver for Humanity-like products is the rise in AI fraud, synthetic identity, and bots rather than a purely ideological move toward self-sovereign identity. SM016, SM017, SM018
CM036 Humanity’s Human ID and wallet metrics demonstrate strong crypto-native onboarding demand, but they do not by themselves prove paid enterprise market capture or revenue quality. SM023, SM024, SM005, SM006
CM037 Biometric decentralized identity faces meaningful adoption constraints around privacy, consent, and trust that cannot be solved by growth alone. SM015, SM016, SM018
CM038 The market is likely to split between high-assurance regulated identity verification and lower-friction community proof-of-personhood layers, with long-term value accruing to systems that bridge both credibly. SM010, SM011, SM012, SM007
CP001 Humanity and World are both competing to provide a human-only identity or access layer, but World requires Orb-based verification while Humanity emphasizes palm-based onboarding. SP003, SP018, SP019, SP024
CP002 World ID markets itself as universal proof of human for dating, live events, gaming, social media, and related consumer use cases. SP003
CP003 World publicly highlights deep face, face auth, credentials, and rewards on top of its core proof-of-human layer. SP003
CP004 BrightID describes itself as a public-good, nonintrusive, decentralized, open-source social identity network. SP005, SP006
CP005 BrightID says it solves unique identity through social-graph analysis without recording personally identifying information. SP005
CP006 Proof of Humanity positions itself as a decentralized, sybil-resistant list of humans. SP007
CP007 Proof of Humanity’s workflow relies on a profile with name, photo, and video, plus deposit, vouching, and challenge steps. SP007
CP008 Human Passport markets proof-of-personhood tools and data services for both onchain and offchain use cases. SP008
CP009 Human Passport publicly reports 2M+ passports, 120+ ecosystem partners, 43M+ credentials, and more than $512M in airdrops secured against sybils. SP008
CP010 Human Passport says it does not store names, emails, IPs, or personal identifiers and instead uses hashed or reduced signals. SP008
CP011 Persona markets itself as a flexible and secure way to verify real people and real businesses online. SP009
CP012 Persona’s site shows a broad mainstream customer roster and highlights 2026 Gartner and 2025 Forrester recognition in identity verification. SP009
CP013 Persona’s public product taxonomy spans government ID, document AI, selfie recognition, digital ID, KYB, KYA, reverification, and risk reports. SP009, SP010
CP014 Civic’s public website now centers signal-based GTM, Bryn, Auth, and MCP for AI-powered workflows rather than a core human-identity-verification product line. SP011, SP012
CP015 Civic’s public pivot implies that at least one adjacent identity brand has found better monetization outside Humanity’s exact category. SP011, SP012
CP016 Fractal ID’s site was unavailable during this run, limiting public visibility into its current competitive positioning. SP013
CP017 Onfido’s public product page was blocked by security verification during this run, which limited direct comparison of its current product packaging. SP014, SP015
CP018 Jumio’s retrieved public pages were too minimal to extract a detailed current feature or pricing comparison in this run. SP016, SP017
CP019 Humanity differentiates from World by arguing that palm biometrics can deliver lower friction and less invasive capture than Orb-centered iris verification. SP018, SP019, SP024
CP020 Humanity differs from BrightID and Proof of Humanity because it uses biometrics instead of social-graph or vouch-and-challenge proofs. SP005, SP007, SP024
CP021 Human Passport is Humanity’s most direct non-biometric web3 rival because it targets the same anti-sybil, governance, airdrop, and community-integrity workflows. SP008, SP021
CP022 Persona and incumbent KYC vendors are more dangerous in regulated onboarding because they already fit compliance workflows and show broader enterprise proof. SP009, SP010, SP017
CP023 World appears stronger on consumer-network ambition and brand awareness than Humanity, but also carries heavier privacy and regulatory baggage. SP003, SP018, SP023
CP024 BrightID and Proof of Humanity likely offer a more privacy-purist posture than Humanity, but with slower or higher-friction onboarding for mainstream users. SP005, SP007, SP019
CP025 Human Passport benefits from composability and partner-network effects because it aggregates many proof signals rather than insisting on one biometric modality. SP008
CP026 Humanity’s moat depends on whether mobile-accessible palm verification and reusable credentials can outperform both hardware biometrics and non-biometric aggregators. SP003, SP008, SP024, SP025
CP027 Multi-homing is plausible because many buyers can combine a KYC incumbent with a separate anti-sybil or proof-of-personhood layer. SP008, SP009, SP017, SP021
CP028 Pricing and packaging are generally opaque across this field, with enterprise demos, ecosystem incentives, or community models more common than transparent rate cards. SP008, SP009, SP017
CP029 A major substitute for Humanity is internal build around a mainstream KYC vendor plus CAPTCHAs, manual review, and separate anti-abuse heuristics. SP009, SP017, SP021
CP030 Regulatory and trust posture is a buying criterion, so biometric rivals with more controversy or weaker controls can lose despite stronger distribution. SP018, SP019, SP023
CP031 Persona’s visible customer logos provide stronger public proof of mainstream enterprise adoption than Humanity currently discloses. SP009, SP020
CP032 Human Passport’s published passport, partner, and credential counts imply stronger current web3 distribution than Humanity’s named partner set alone. SP008, SP020
CP033 Proof of Humanity’s challenge mechanism may be especially durable in governance contexts even if it is slower for mass onboarding. SP007
CP034 Civic’s reduced focus on this category narrows its direct rivalry today but also illustrates monetization risk inside decentralized identity. SP011, SP012
CP035 Humanity occupies a potentially unstable middle ground between enterprise KYC incumbents and privacy-first community proof systems. SP009, SP019, SP024
CP036 Long-term competitive durability is more likely to come from issuer acceptance, developer integrations, and trust after incidents than from raw sign-up counts alone. SP020, SP021, SP022, SP025
CI001 Humanity’s public token materials frame $H as the economic incentive layer for validators, developers, and protocol participation rather than as a simple equity proxy. SI001, SI002
CI002 The $H page says the token is meant to reward validators who uphold identity integrity and to fuel developers building applications on the network. SI001
CI003 Humanity publicly states that $H has a fixed supply of 10 billion ERC-20 tokens. SI001, SI003
CI004 The published allocation table reserves 19% for early contributors and 10% for investors. SI001
CI005 The same allocation page shows sizable pools for community incentives, ecosystem funding, identity-verification rewards, and foundation operations, reinforcing a tokenized network-economics model. SI001
CI006 Humanity’s official fairdrop materials present token distribution as a sybil-resistant user-acquisition and ecosystem-bootstrap mechanism, not a disclosed software pricing plan. SI005, SI001
CI007 Public materials describe staking and validation incentives, but they do not disclose a clean fee schedule showing how much protocol activity converts into revenue retained by the company or foundation. SI001, SI002, SI005
CI008 No retained official source exposes list pricing, contract minimums, enterprise subscription bands, or standardized onboarding fees for customers. SI026, SI021, SI022
CI009 That absence of public price disclosure makes Humanity’s monetization model materially less transparent than a typical SaaS identity vendor. SI026, SI025
CI010 Official positioning consistently emphasizes programmable trust, credentials, and token incentives, implying the economic design is closer to protocol adoption plus treasury appreciation than to conventional seat-based SaaS. SI001, SI021, SI022
CI011 Multiple sources support about $50 million of publicly disclosed capital raised across Humanity’s 2024 round and January 2025 round. SI007, SI008, SI009, SI010
CI012 The January 2025 round was widely described as $20M at a $1.1B fully diluted valuation led by Pantera Capital and Jump Crypto. SI008, SI009, SI010
CI013 The 2024 raise was explicitly framed as a $30M round at a $1B valuation, giving Humanity headline financing momentum before token launch. SI007
CI014 Because the $1.1B marker is described as fully diluted valuation, it should be interpreted as token-network valuation context rather than as audited operating equity value. SI008, SI010, SI001
CI015 Official milestone posts disclose strong top-of-funnel growth — 1M Human IDs, then 7M+ Human IDs and roughly 10M wallets — but those metrics are not equivalent to paying customers or recognized revenue. SI011, SI012, SI006
CI016 The best public traction metrics are identity reservations, wallet counts, token participation, and ecosystem integrations, not revenue, ARR, or gross margin. SI011, SI012, SI015, SI016
CI017 No retained source discloses revenue, ARR, gross margin, burn, cash balance, CAC, payback, NRR, or runway. SI026, SI001, SI021
CI018 That makes Humanity financially real in capital formation terms but still not publicly modelable in operating-performance terms. SI011, SI017, SI003
CI019 The staking portal confirms an active staking surface, but the retained output is too thin to prove staking volume, yield structure, or treasury capture. SI002
CI020 The fairdrop and staking materials suggest user incentives were central to growth strategy around token launch. SI005, SI006, SI002
CI021 CoinGecko’s 2026 market page shows roughly 2 billion tokens circulating against a 10 billion maximum supply, highlighting the difference between spot market cap and fully diluted valuation. SI003, SI001
CI022 On 2026-08-07 CoinGecko listed Humanity at roughly $170M market cap and about $852M FDV, materially below the prior $1.1B financing headline. SI003
CI023 That gap implies public market trading was discounting the token network below the January 2025 fully diluted financing benchmark. SI003, SI012
CI024 The public token page explicitly links real-human verification to fairdrop eligibility, suggesting growth spending partly took the form of token emissions rather than cash-only marketing. SI001, SI005
CI025 Moongate expands Humanity’s possible revenue surface beyond pure identity verification into event ticketing, access control, loyalty, and real-world activations. SI014
CI026 Even so, the Moongate announcement does not disclose acquisition price, revenue contribution, gross margin, or payback period. SI014
CI027 The mainnet coverage broadens the product story toward credentials and Web2/Web3 reputation, but the public record still stops short of proving recurring enterprise monetization. SI015, SI016
CI028 The June 2026 exploit added a direct economic overhang because token price damage, recovery obligations, and governance scrutiny can all reduce treasury flexibility and customer trust. SI017, SI018, SI019, SI020
CI029 Humanity’s recovery portal shows multiple holder categories requiring manual review, indicating the incident likely created nontrivial operational and compensation complexity. SI019, SI020
CI030 The transparency tracker shows the team treated the incident as an on-chain recovery and disclosure problem, but it does not disclose the total balance-sheet cost borne by the issuer or foundation. SI020, SI019
CI031 Official docs and homepage messaging focus on identity, privacy, and protocol design rather than on revenue recognition or customer billing, reinforcing that financial diligence is still constrained by company-controlled disclosure. SI021, SI022, SI026
CI032 Compared with a public identity platform such as Okta, Humanity offers far less standardized financial disclosure, making comparability on gross margin, R&D intensity, and sales efficiency impossible from public sources. SI025, SI026
CI033 The public record supports a plausible future mix of token appreciation, protocol incentives, developer activity, and enterprise credential services, but it does not yet reveal what share of value accrues as current cash revenue. SI001, SI021, SI014
CI034 Nothing in the retained sources proves meaningful working-capital burdens such as inventory, receivables finance, or project-finance debt; the main capital need appears to be ecosystem building, engineering, and go-to-market execution. SI007, SI014, SI021
CI035 Nothing in the retained sources proves positive unit economics on customer acquisition, identity verification cost per user, or validator payout efficiency. SI001, SI002, SI026
CI036 The most supportable public financial verdict is that Humanity has raised enough capital and built enough token-market infrastructure to matter, but not enough disclosure exists to underwrite revenue quality, margin path, or runway with confidence. SI011, SI012, SI017, SI003
CE001 Humanity’s official positioning spans proof-of-humanity, reusable credentials, and a broader “trust layer” rather than a single KYC workflow. SE001, SE002, SE003
CE002 The public docs describe the protocol as an EVM-based proof-of-humanity solution built around decentralized identifiers and verifiable credentials. SE002, SE003
CE003 Humanity distinguishes Human ID reservation, stronger biometric verification, and reusable credentials as separate layers of the user journey. SE003, SE004, SE008, SE007
CE004 The biometric docs say Humanity uses palm biometrics as the core uniqueness primitive for proof-of-humanity. SE004, SE008
CE005 Official materials emphasize privacy-preserving verification and user ownership rather than centralized storage of raw identity data. SE001, SE003, SE004
CE006 Palm scanning moved from theory into a public rollout phase in 2026, which is stronger evidence of maturity than the earlier waitlist-only Human ID period. SE008, SE021, SE022
CE007 Mainnet is publicly live, and official coverage describes it as the point where Humanity started bridging Web2 and Web3 credentials. SE007, SE016, SE017
CE008 The mainnet launch post says zkTLS developed with Reclaim is live inside the dashboard. SE007, SE005
CE009 The same post expands the product from simple proof-of-personhood into broader proof-of-reputation use cases such as employment, education, and memberships. SE007, SE006
CE010 Humanity’s verifiable-credentials post frames credentials as wallet-held, selectively shared, and portable across ecosystems. SE006, SE003
CE011 Official examples include humanity proof, membership proof, travel or loyalty credentials, and other attestations rather than only government-ID-style checks. SE006, SE007
CE012 The public SDK/API docs position Humanity as an OAuth-2.0-like integration surface for web applications. SE009, SE012, SE013
CE013 The TypeScript SDK README shows presets for isHuman, age checks, and accredited-investor-style verification flows. SE012
CE014 The connect SDK exposes state, nonce, token exchange, refresh, revoke, and credential-update polling primitives, which is materially more than a thin marketing placeholder. SE012
CE015 The React SDK claims ready-made components can reduce integration time from multiple days to roughly 30 minutes. SE013
CE016 The React SDK also includes typed providers, verification hooks, credential-update hooks, and testing helpers, indicating a maturing front-end integration surface. SE013
CE017 The GitHub organization page showed 31 repositories with multiple recent updates in late July and early August 2026, which is a real developer-activity signal even if stars alone do not prove adoption. SE011
CE018 The docs resources page exposes chain IDs, explorer, faucet, bridge, dashboard, and developer portal links, showing that the public stack includes chain operations in addition to identity UX. SE010
CE019 The Walrus integration says Humanity migrated major credential components, including claims data, proofs, issuance metadata, revocation logs, and verification receipts, onto decentralized nodes. SE014
CE020 That Walrus post also says credential data is encrypted at rest with user-delegated keys and accessed through API abstraction plus cross-chain communication. SE014
CE021 Official Walrus materials imply that Sui developers and smart contracts can request verification results through a simplified API path. SE014
CE022 The Fireblocks integration is an operational rather than purely marketing signal because it places Humanity Mainnet inside institutional custody and treasury workflows already used for other digital assets. SE015
CE023 Humanity says Fireblocks serves more than 2,400 institutions and 130+ blockchains, which, if accurate, broadens the reachable operating environment for H and the mainnet. SE015
CE024 Public third-party coverage consistently describes Humanity as privacy-first and aimed at bridging Web2 and Web3 identity rather than replacing every existing identity system. SE016, SE017, SE018, SE019
CE025 The public product story is therefore broader than a single mobile biometric app: it includes identity reservation, palm verification, credentials, APIs, smart-contract access, and treasury/custody rails. SE001, SE007, SE009, SE014, SE015
CE026 The docs and blogs provide qualitative architecture detail, but they do not disclose false-positive rates, throughput, latency, liveness benchmarks, or independent biometric accuracy tests. SE004, SE005, SE007
CE027 No retained source proves SOC 2, ISO 27001, or similar conventional enterprise assurance certifications for the product surface. SE001, SE009, SE010
CE028 Likewise, the retained set does not provide a public uptime history or formal status-page evidence for the identity, API, or mainnet surfaces. SE009, SE010, SE011
CE029 Visible dependencies include Reclaim for zkTLS, Walrus and Sui-adjacent infrastructure for decentralized storage, Fireblocks for institutional custody, and GitHub-hosted SDK distribution for developers. SE005, SE014, SE015, SE011, SE012, SE013
CE030 The incident response surfaces show the team can publish recovery and transparency tooling quickly, but they also reveal that privileged-access and operational security are real technical diligence items. SE023, SE024
CE031 The connect SDK explicitly supports mock providers and testing helpers, which is a stronger developer-maturity signal than a docs-only API narrative. SE012, SE013
CE032 Humanity’s public use-case map now spans financial reputation, education, travel, event access, governance, and bot resistance. SE006, SE007, SE014, SE025
CE033 The Mastercard coverage, while third-party, supports the view that Humanity is trying to turn Human ID into reusable financial-eligibility infrastructure rather than a one-time login credential. SE025
CE034 The product is more mature on integration surfaces and narrative breadth than on independently benchmarked performance or compliance proof. SE009, SE010, SE014, SE015
CE035 The best public verdict is that Humanity has a real multi-layer identity stack with meaningful developer activity and expanding partner integrations, but it still asks investors to trust a lot of architecture and reliability claims without third-party validation. SE007, SE011, SE014, SE015, SE009
CU001 Humanity’s public record now points to at least five visible customer or partner segment clusters: end users, developers, education ecosystems, event/access ecosystems, and institutional or financial rails. SU001, SU002, SU005, SU006, SU007, SU008
CU002 The official product story still centers on end users creating Human IDs and proving humanity, but the public go-to-market has broadened well beyond consumer onboarding alone. SU001, SU017, SU024
CU003 The testnet and growth posts show user-scale signals — 1M Human IDs, then roughly 7M IDs and 10M wallets — that establish demand but not customer monetization. SU003, SU004
CU004 Open Campus is the clearest education-sector proof in the retained set because the announcement specifies credentialing, learner identities, and institutional engagement goals. SU006
CU005 The Open Campus partnership positions Humanity as the proof-of-humanity and verifiable-credential layer inside education use cases rather than as a generic marketing partner. SU006
CU006 Moongate is the clearest real-world access and event-distribution proof because Humanity acquired infrastructure already used for ticketing, credentialing, and access control. SU005
CU007 The Moongate post says that platform had already powered more than 300,000 on-chain tickets globally, which is one of the strongest quantified deployment indicators in the retained customer set. SU005
CU008 Fireblocks is the clearest institutional-operability proof because it places Humanity Mainnet into an existing custody and treasury environment used by thousands of institutions. SU007
CU009 Humanity says Fireblocks supports more than 2,400 institutions and over 130 blockchain networks, which, if accurate, materially expands the reachable distribution environment for H and related workflows. SU007
CU010 Walrus is better read as ecosystem and developer adoption proof than as traditional customer proof, because the announcement emphasizes Sui developers and app builders using identity signals. SU008
CU011 The Korea hackathon post adds lightweight but useful practitioner proof that third parties were building real-world applications on top of Humanity’s surfaces. SU009
CU012 The Mastercard integration points to a financial-services distribution thesis around reusable Human ID and open-finance credentials, but the retained proof is still partner-announcement level rather than contracted-revenue proof. SU010, SU011
CU013 Taken together, Open Campus, Moongate, Fireblocks, Walrus, and Mastercard show a multi-vertical expansion thesis rather than a single-customer concentration around one dApp. SU005, SU006, SU007, SU008, SU010
CU014 The public customer story is stronger on strategic partner breadth than on direct proof of paying enterprise accounts. SU005, SU006, SU007, SU010, SU014
CU015 Identity Week and FinanceFeeds both frame Humanity’s mainnet as a bridge between Web2 and Web3, supporting a cross-vertical customer thesis around privacy-first identity. SU012, SU013
CU016 The verifiable-credentials materials explicitly broaden the user-value proposition into travel, education, and gated-access workflows, which is relevant for expansion even without direct revenue proof. SU025, SU024
CU017 The public record does not disclose paying-customer counts, ACV, NRR, GRR, renewal rates, or logo churn. SU001, SU023, SU017
CU018 No retained source proves recurring enterprise revenue customers at scale. SU001, SU006, SU007, SU010
CU019 That means the strongest “customers” evidence is deployment or partnership proof, not software-book transparency. SU005, SU006, SU007, SU008, SU010
CU020 The buyer-user-payer mix is still blurry: end users enroll, developers integrate, partners distribute, and an undisclosed party may ultimately pay for enterprise or institutional workflows. SU001, SU002, SU024
CU021 User and wallet counts should not be treated as customer counts, because the public record does not tie those top-of-funnel figures to contracts or revenue cohorts. SU003, SU004, SU024
CU022 Token incentives appear to help customer acquisition and ecosystem engagement, especially around fairdrop and staking, but they also make it harder to judge organic retention. SU004, SU021, SU003
CU023 One visible concentration risk is partner dependence: much of the strongest proof sits in counterparties such as Moongate, Open Campus, Fireblocks, Walrus, and Mastercard rather than in a large disclosed base of direct paying customers. SU005, SU006, SU007, SU008, SU010
CU024 Another concentration risk is that many public use cases remain web3-native or crypto-adjacent, which leaves the story exposed to ecosystem cycles even when the identity concept is broader. SU013, SU014, SU015
CU025 Open Campus, Moongate, and Mastercard each suggest credible land-and-expand logic because they connect Humanity to larger issuance, access, or financial networks beyond one-off signups. SU005, SU006, SU010, SU011
CU026 Fireblocks suggests expansion into institutions that already operate multiple chains, but it does not itself prove those institutions are using Human ID for end-customer identity workflows. SU007
CU027 Walrus suggests expansion into Sui developers and apps, but it is still ecosystem infrastructure proof rather than proof of large paying developer cohorts. SU008
CU028 The strongest quantified outcome signals in the retained set are 300,000+ on-chain tickets at Moongate and 2,400+ institutions reachable through Fireblocks, plus the Human ID and wallet counts from official growth posts. SU005, SU007, SU003, SU004
CU029 Public geography proof is broad but soft: Humanity is clearly operating in global web3 ecosystems, while named proofs touch education, events, and institutional rails across multiple regions without disclosing region-level revenue. SU005, SU006, SU007, SU013
CU030 The exploit and adverse commentary complicate the customer story because trust-sensitive buyers may hesitate until incident response and governance credibility improve. SU022, SU016
CU031 The public set also lacks direct user-satisfaction or review-platform evidence, so quality of experience cannot be inferred from partner announcements alone. SU023, SU017
CU032 The named proofs strongest enough for an IC memo are Moongate for real-world events, Open Campus for education credentials, Fireblocks for institutional operability, and Mastercard for financial-identity ambition. SU005, SU006, SU007, SU010, SU011
CU033 Hackathon and developer-facing evidence is useful, but weaker than named production or distribution partnerships when underwriting customer durability. SU008, SU009
CU034 Humanity’s customer chapter therefore reads stronger on expansion surface and ecosystem fit than on renewals, contract economics, or direct enterprise penetration. SU013, SU017, SU023
CU035 The best public verdict is that Humanity has real adoption vectors and credible named proof across several verticals, but the market still cannot see which of those vectors convert into durable paying customers. SU005, SU006, SU007, SU010, SU017
CR001 Humanity’s terms explicitly contemplate identity verification through palm print and vein image recognition, confirming that biometric processing sits near the center of the service design. SR002
CR002 Humanity’s privacy policy says it may collect, process, store with providers, and disclose biometric data in connection with the service and applicable laws. SR001
CR003 The privacy policy also states users may have deletion and other privacy rights, but those rights are constrained by applicable law and operational obligations. SR001
CR004 Humanity’s terms define Personal Data by reference to the BVI Data Protection Act 2021 and other applicable BVI laws, anchoring the legal framework partly outside Hong Kong or the EU. SR002
CR005 The same terms say disputes are governed by British Virgin Islands law and allow the company to suspend, restrict, or terminate access in multiple circumstances. SR002
CR006 The terms also include prohibited-jurisdiction and sanctions language, meaning compliance exposure is embedded directly into account access and platform usage. SR002
CR007 Hong Kong PDPO guidance requires lawful and fair collection, accuracy controls, retention discipline, and security protection for personal data, which are directly relevant to biometric identity products. SR003
CR008 GDPR Article 9 treats biometric data used to uniquely identify a natural person as special-category data whose processing is generally prohibited unless a permitted condition applies. SR004
CR009 The FTC’s privacy and security guidance reinforces that companies must honor their privacy promises and maintain security appropriate to the sensitivity of the data they possess. SR005
CR010 Because Humanity wants reusable credentials that can touch financial or eligibility contexts, cross-border privacy compliance is a first-order risk rather than a back-office detail. SR001, SR004, SR005
CR011 FATF, NIST, and EU digital-identity materials all support the idea that digital identity systems sit inside a tightening compliance environment where assurance, minimization, and governance matter. SR018, SR019, SR020
CR012 Humanity’s own policy language about provider storage and disclosure means its privacy burden extends beyond just on-chain design into off-chain processors and data handling. SR001, SR003
CR013 Quantstamp’s incident summary says the June 2026 attack involved unauthorized minting and selling of H on Ethereum and BSC after attacker-controlled keys were used. SR006
CR014 The same summary says the attacker phished a director, installed malware, and stole keys, making the exploit primarily an operational-security failure rather than a code bug. SR006, SR010, SR011
CR015 BSCN explicitly says the incident was not caused by a smart-contract vulnerability but by compromised private keys and operational-security failures. SR011, SR012
CR016 The incident summary says roughly 150 operational H wallets and related gas-funding wallets were also drained, showing a wider privileged-surface problem than one admin key alone. SR006
CR017 BSCN reports about 447 million H tokens were stolen or unauthorizedly minted across the attack, which made the financial and governance impact too large for a simple patch response. SR011, SR012
CR018 The claim portal shows that liquidity-pool, vault, smart-contract, and post-snapshot purchasers require manual review, which adds operational, legal, and customer-support complexity to recovery. SR007, SR011, SR012
CR019 CoinAlert explicitly notes that some claimants may face KYC or AML screening after forensic analysis, which creates privacy and UX risk for holders who expected a frictionless crypto recovery. SR012
CR020 The transparency tracker is a mitigating control because it exposes attacker-linked addresses and movements, but it also publicly evidences how much trust now depends on incident communications. SR008, SR006
CR021 The exploit therefore creates three simultaneous risks: treasury damage, user-trust damage, and proof that privileged-key management is a core technical attack surface. SR006, SR009, SR010, SR011
CR022 Humanity’s customer and product stories remain partner-mediated, so failures in partners or integrations can hit both adoption and perceived safety. SR025, SR026, SR027, SR028, SR029, SR030
CR023 Visible dependencies include Walrus for decentralized storage, Fireblocks for institutional operability, Open Campus for education proof, Moongate for events, and Mastercard for financial-identity distribution. SR025, SR026, SR028, SR029, SR030
CR024 Those dependencies are strategically helpful, but they also mean Humanity’s public traction is partly downstream of counterparties it does not fully control. SR023, SR025, SR026, SR028, SR029, SR030
CR025 The public record still does not prove SOC 2, ISO 27001, formal uptime reporting, or independent biometric-accuracy benchmarks, leaving assurance risk open. SR001, SR002, SR024
CR026 AI-driven fraud and bot growth are genuine market tailwinds for Humanity’s category, but they also raise the bar for failure because customers buy identity products to reduce trust risk, not add more. SR021, SR022, SR024
CR027 Competitive pressure from World and non-biometric identity alternatives means Humanity may face reputational damage faster if security or privacy claims underperform. SR013, SR014, SR015
CR028 The public customer record remains light on direct paying-customer disclosures, which itself is a risk because partner announcements can mask concentration or weak retention. SR028, SR029, SR030
CR029 Market research and identity-fraud reports support a large addressable need, but they do not remove the execution risk of turning interest into safe, compliant deployment. SR016, SR017, SR021, SR022, SR023
CR030 Humanity’s terms reserve broad rights to restrict access, and that can be useful for sanctions compliance but risky for user trust if enforcement or appeals processes are opaque. SR002
CR031 The privacy policy’s broad disclosure and provider language means an investor should not assume the system is purely self-custodial or purely on-chain from a data-governance perspective. SR001, SR025
CR032 BSCN says Humanity planned to relaunch mainnet in the weeks after the recovery and coordinate with exchanges, bridges, and liquidity partners, which highlights complex execution dependencies during crisis response. SR011
CR033 The recovery design includes a compensation fund and a one-to-one airdrop, which are visible mitigations but also admissions that the edge-case burden is material. SR007, SR011, SR012
CR034 The official incident summary naming a director’s compromised machine and key backups indicates people and process controls are at least as important as smart-contract audits for Humanity. SR006, SR010
CR035 Because biometric and credential systems involve sensitive personal data, any future privacy controversy could transmit quickly into customer adoption, regulatory scrutiny, and partner caution. SR001, SR004, SR005, SR013
CR036 The strongest public mitigations today are transparency tooling, a formal incident summary, token migration, compensation mechanisms, and more explicit anti-fraud product positioning. SR006, SR007, SR008, SR011, SR024
CR037 What is still missing are independent proofs that key-management controls, processor controls, biometric safeguards, and uptime controls have been materially strengthened after the incident. SR001, SR006, SR010, SR024
CR038 A practical kill criterion would be any repeat privileged-key incident or major privacy controversy before the company demonstrates stable credential and partner growth. SR006, SR001, SR013
CR039 Another kill criterion would be evidence that named partners remain symbolic while direct paying-customer disclosures never materialize. SR028, SR029, SR030
CR040 The overall risk verdict is high: Humanity sits in an attractive market, but the combination of biometric sensitivity, operational-security failure, partner dependence, and disclosure gaps keeps residual exposure elevated. SR004, SR006, SR022, SR023, SR025, SR030
CV001 Humanity’s January 2025 headline funding benchmark was a $20M round priced at a $1.1B fully diluted valuation. SV007, SV008, SV009
CV002 Humanity’s May 2024 financing was publicly framed around $30M raised at roughly a $1B valuation. SV006
CV003 Those financing references are best read as token-network FDV markers rather than as audited operating-enterprise values. SV001, SV006, SV007
CV004 CoinGecko’s August 2026 page places Humanity near $170M spot market cap and about $852M fully diluted valuation. SV002
CV005 CoinMarketCap’s H/USDT page shows H near $0.0859 on 2026-08-07, consistent with a sub-$1B fully diluted token value. SV003, SV004
CV006 Current public token-market markers therefore sit materially below the January 2025 $1.1B funding headline. SV002, SV004, SV007
CV007 That reset is meaningful, but it does not by itself make Humanity obviously cheap. SV002, SV007, SV018
CV008 The gap between about $170M spot cap and about $852M FDV means circulating value and fully diluted value tell very different stories. SV001, SV002, SV004
CV009 Investors are therefore underwriting future token distribution and unlock governance, not just today’s float. SV001, SV002
CV010 Humanity’s strongest bullish valuation input is strategic optionality across identity, anti-fraud, developer, and institution-facing workflows. SV010, SV012, SV023, SV024, SV029, SV030
CV011 A second bullish input is that some hack damage has already been repriced because live FDV sits below the old financing headline. SV002, SV004, SV007, SV014
CV012 The strongest bearish input is the lack of public revenue, margin, retention, and treasury disclosure. SV001, SV018, SV019
CV013 The June 2026 exploit created a lasting governance and trust discount in any valuation model. SV013, SV014, SV015, SV016, SV017
CV014 Current public narrative still revolves around the hack, recovery, and pivot more than around operating metrics. SV005, SV015
CV015 The enterprise-AI pivot may widen optionality, but on public evidence it adds execution risk before it adds proven monetization. SV005, SV015
CV016 Humanity cannot be valued like a mature identity software company on disclosed revenue multiples. SV018, SV019, SV020
CV017 Okta, Coinbase, and Palantir are useful only as boundary markers because they are economically proven and publicly disclosed in ways Humanity is not. SV018, SV019, SV020, SV021, SV022
CV018 CompaniesMarketCap places Okta near $26.0B, Coinbase near $39.5B, and Palantir above $400B as of August 2026. SV020, SV021, SV022
CV019 Those public comps are dangerous to overread because their values rest on audited financials and governance, not on token unlock paths. SV018, SV019, SV020, SV021, SV022
CV020 Palantir’s 10-K and Okta’s annual report show exactly the disclosure depth Humanity lacks on revenue quality, liquidity, and risks. SV018, SV019
CV021 That disclosure gap alone justifies a substantial discount relative to public software and infrastructure comparables. SV018, SV019, SV020
CV022 Recent CoinMarketCap history shows H remained volatile in early August 2026. SV003, SV004
CV023 The hack changed valuation by shifting the main underwriting question from adoption scale to trust recovery. SV013, SV014, SV015
CV024 Partner optionality from Fireblocks, Moongate, Open Campus, and Mastercard deserves some value because it shows multiple adoption lanes. SV023, SV024, SV029, SV030
CV025 That optionality still cannot be capitalized aggressively without direct revenue or production-depth proof. SV023, SV024, SV029, SV030
CV026 The most supportable public recommendation is research-more rather than buy or avoid. SV002, SV013, SV018, SV019
CV027 Confidence should remain medium at best because price history is observable while operating economics are mostly private. SV002, SV003, SV018, SV019
CV028 Risk rating should remain high because the thesis depends on security recovery, supply governance, partner conversion, and future monetization. SV013, SV015, SV023
CV029 At today’s public markers, Humanity looks more defensible near live levels than at the old $1.1B funding headline. SV002, SV004, SV007
CV030 A move from research-more to buy would require hard evidence on revenue, retention, treasury governance, and post-hack controls. SV013, SV018, SV019
CV031 A thesis break would include another privileged-key incident, unresolved compensation liabilities, or failure to convert partnerships into direct economics. SV013, SV016, SV017, SV029, SV030
CV032 A public bear case centers on valuation compressing closer to spot-cap logic if trust recovery weakens. SV002, SV014, SV015
CV033 A base case centers on stable recovery and public FDV holding in the high-hundreds-of-millions range while monetization stays unproven. SV002, SV004, SV015
CV034 A bull case requires partner lanes converting into credible enterprise or financial workflows plus restored trust. SV007, SV023, SV024, SV029, SV030
CV035 The absence of direct customer and revenue data means any single-number target would be false precision. SV018, SV019, SV023
CV036 Comparables still help directionally: Okta frames identity-software disclosure, Coinbase frames listed crypto infrastructure, and Palantir frames narrative-plus-data-platform scale. SV018, SV019, SV020, SV021, SV022
CV037 Humanity’s live public pricing is best interpreted as a narrative-adjusted token-market mark, not as a clean measure of enterprise intrinsic value. SV002, SV003, SV004, SV005
CV038 The minimum final diligence asks are revenue proof, retention proof, treasury governance, and post-hack control evidence. SV013, SV018, SV019, SV023
CV039 Until those asks are answered, the right stance is price-sensitive curiosity rather than conviction. SV025, SV026, SV028
CV040 The overall valuation verdict is that Humanity is strategically interesting, financially under-disclosed, and only conditionally attractive near current token-market levels for high-risk investors. SV002, SV013, SV018, SV019, SV023
来源
编号出版方标题引文
SO001 Humanity Verify anything, store nothing
SO002 Humanity Protocol
SO003 Humanity Humanity Protocol Raises $30M at a $1 Billion Valuation to Build a Zero-Knowledge Worldcoin Competitor The team at Humanity Protocol plans to use the funds to accelerate hiring and product development ahead of their public testnet launch in the second half of 2024.
SO004 Animoca Brands Humanity Protocol Emerges from Stealth
SO005 Coinspeaker Humanity Protocol Secures $20M Funding, Hits $1.1B Valuation
SO006 The Block Pantera Capital and Jump Crypto lead $20 million funding round for Humanity Protocol
SO007 Verdict Humanity Protocol raises $20m at $1.1bn valuation
SO008 Securities.io Terence Kwok, CEO and Founder of Humanity Protocol – Interview Series
SO009 Pulse 2.0 Humanity Protocol: An Interview With Founder and CEO Terence Kwok
SO010 Cryptonews Can Humanity Protocol Avoid Worldcoin’s Pitfalls?
SO011 Crypto Briefing Humanity Protocol Leverages ZK-Proofs to Protect Personal Identity Data
SO012 Humanity Humanity Blog
SO013 Humanity The Testnet Beta Is Live
SO014 Humanity Humanity Protocol Gears Up for Big Moves
SO015 Humanity $H is Here: Introducing the First-Ever Fairdrop
SO016 Humanity Humanity Protocol Hits 1 Million Human IDs on Testnet
SO017 Humanity Palm Scanning Begins on Humanity Protocol
SO018 FinanceFeeds Humanity Launches $1.1B Mainnet in Bid to Challenge Worldcoin
SO019 Identity Week Humanity Protocol Mainnet Goes Live, Bridging Web2 and Web3 for Privacy-First Digital Identity
SO020 IQ.wiki Humanity Protocol – Milestones
SO021 KuCoin What Is the Difference Between Worldcoin and Humanity Protocol?
SO022 BanklessTimes Humanity Protocol Surges 65% Amid Worldcoin’s Credibility Problem
SO023 The Crypto Times ZachXBT Calls $32M Humanity Protocol Hack “Possibly Staged,” $H Crashes 86% Humanity Protocol ... suffered a $30-32 million exploit ... and crashed its $H token by 80-93% within hours.
SO024 Humanity Docs What Is Humanity
SO025 Humanity Docs How Biometric Proof-of-Humanity Works
SO026 Built In Humanity Protocol Careers, Perks + Culture
SM001 Humanity Verify anything, store nothing
SM002 Humanity Protocol
SM003 Humanity Docs What Is Humanity
SM004 Humanity Docs How Biometric Proof-of-Humanity Works
SM005 Humanity Humanity Protocol Raises $30M at a $1 Billion Valuation to Build a Zero-Knowledge Worldcoin Competitor
SM006 Humanity $H is Here: Introducing the First-Ever Fairdrop
SM007 Identity Week Humanity Protocol Mainnet Goes Live, Bridging Web2 and Web3 for Privacy-First Digital Identity
SM008 Mordor Intelligence Identity Verification Market Size and Share
SM009 Mordor Intelligence Biometrics Market Analysis
SM010 FATF Guidance on Digital Identity
SM011 NIST NIST Special Publication 800-63-4 Digital Identity Guidelines
SM012 European Commission European Digital Identity
SM013 World Economic Forum Blockchain can help create privacy-preserving digital ID
SM014 World Economic Forum Reimagining Digital ID
SM015 World Economic Forum Ethical dilemmas posed by the future of digital identity
SM016 Entrust Identity Fraud Report
SM017 LexisNexis Risk Solutions Synthetic Identities and Agentic Bots Posing as Human Contribute to 8% Rise in Global Fraud
SM018 ID.me The 2026 Identity Fraud Landscape Report
SM019 Insurance Journal LexisNexis: Synthetic Identity Fraud Rises Significantly in 2025
SM020 Cryptonews Can Humanity Protocol Avoid Worldcoin’s Pitfalls?
SM021 KuCoin What Is the Difference Between Worldcoin and Humanity Protocol?
SM022 BanklessTimes Humanity Protocol Surges 65% Amid Worldcoin’s Credibility Problem
SM023 Humanity The Testnet Beta Is Live
SM024 Humanity Palm Scanning Begins on Humanity Protocol
SM025 Securities.io Terence Kwok, CEO and Founder of Humanity Protocol – Interview Series
SM026 Pulse 2.0 Humanity Protocol: An Interview With Founder and CEO Terence Kwok
SP001 Humanity Verify anything, store nothing
SP002 Humanity Protocol
SP003 World World ID
SP004 World World Home
SP005 BrightID What is BrightID?
SP006 BrightID BrightID
SP007 Proof of Humanity The Internet of Humans
SP008 Human Passport Sybil Protection Suite
SP009 Persona Secure Identity Verification Solutions
SP010 Persona Persona identity-verification page not found but product taxonomy visible
SP011 Civic Civic home
SP012 Civic Civic products page with revoked access / current footer positioning
SP013 Fractal ID Fractal ID service unavailable
SP014 Onfido Onfido home security verification page
SP015 Onfido Onfido identity verification page blocked by security verification
SP016 Jumio Jumio home minimal output
SP017 Jumio Jumio KYC page minimal output
SP018 KuCoin What Is the Difference Between Worldcoin and Humanity Protocol?
SP019 Cryptonews Can Humanity Protocol Avoid Worldcoin’s Pitfalls?
SP020 Identity Week Humanity Protocol Mainnet Goes Live, Bridging Web2 and Web3 for Privacy-First Digital Identity
SP021 Humanity $H is Here: Introducing the First-Ever Fairdrop
SP022 Humanity Palm Scanning Begins on Humanity Protocol
SP023 BanklessTimes Humanity Protocol Surges 65% Amid Worldcoin’s Credibility Problem
SP024 Humanity Docs How Biometric Proof-of-Humanity Works
SP025 Humanity Docs What Is Humanity
SP026 Humanity Humanity Protocol Raises $30M at a $1 Billion Valuation to Build a Zero-Knowledge Worldcoin Competitor
SP027 Humanity The Testnet Beta Is Live
SP028 Humanity Verify anything, store nothing
SP029 World World ID
SI001 Humanity $H Token | Humanity
SI002 Humanity Humanity Protocol - Staking Platform
SI003 CoinGecko Humanity Price: H/USD Live Price Chart, Market Cap & News Today
SI004 CoinMarketCap Humanity price today, H to USD live price, marketcap and chart
SI005 Humanity $H is Here: Introducing the First-Ever Fairdrop
SI006 Humanity Humanity Protocol Gears Up for Big Moves
SI007 Humanity Humanity Protocol Raises $30M at a $1 Billion Valuation to Build a Zero-Knowledge Worldcoin Competitor
SI008 Coinspeaker Humanity Protocol Secures $20M Funding, Hits $1.1B Valuation
SI009 The Block Pantera Capital and Jump Crypto lead $20 million funding round for Humanity Protocol
SI010 Verdict Humanity Protocol raises $20m at $1.1bn valuation
SI011 Humanity The Testnet Beta Is Live
SI012 Humanity Humanity Protocol Hits 1 Million Human IDs on Testnet
SI013 Humanity Palm Scanning Begins on Humanity Protocol
SI014 Humanity Humanity Protocol Acquires Moongate to Accelerate Real-World Adoption of Decentralized Identity
SI015 Identity Week Humanity Protocol Mainnet Goes Live, Bridging Web2 and Web3 for Privacy-First Digital Identity
SI016 FinanceFeeds Humanity Launches $1.1B Mainnet in Bid to Challenge Worldcoin
SI017 The Crypto Times ZachXBT Calls $32M Humanity Protocol Hack “Possibly Staged,” $H Crashes 86% Humanity Protocol ... suffered a $30-32 million exploit ... and crashed its $H token by 80-93% within hours.
SI018 The Crypto Times Humanity Protocol Unveils H Token Recovery and Airdrop Plan Post $36M Hack
SI019 Humanity H Token Recovery Program · Humanity Protocol
SI020 Humanity H Compromised Address Tracker
SI021 Humanity Docs What Is Humanity
SI022 Humanity Docs How Biometric Proof-of-Humanity Works
SI023 KuCoin What Is the Difference Between Worldcoin and Humanity Protocol?
SI024 BanklessTimes Humanity Protocol Surges 65% Amid Worldcoin’s Credibility Problem
SI025 SEC Okta Annual Report on Form 10-K
SI026 Humanity Verify anything, store nothing
SE001 Humanity Verify anything, store nothing
SE002 Humanity Protocol
SE003 Humanity Docs What Is Humanity
SE004 Humanity Docs How Biometric Proof-of-Humanity Works
SE005 Humanity What is zkTLS and How Does It Work?
SE006 Humanity What Are Verifiable Credentials and How Do I Use Them?
SE007 Humanity Humanity Protocol Mainnet Live, Bridging Web2 and Web3
SE008 Humanity Palm Scanning Begins on Humanity Protocol
SE009 Humanity Build with the SDK / API
SE010 Humanity Resources | API Reference | Humanity Docs
SE011 GitHub Humanity
SE012 GitHub GitHub - humanity-developers/connect-sdk
SE013 GitHub GitHub - humanity-developers/react-sdk: Humanity Protocol React SDK
SE014 Humanity Decentralized IDs are here: Humanity integrates with Walrus
SE015 Humanity Humanity Mainnet Integrates with Fireblocks, Expanding Institutional Treasury Access
SE016 Identity Week Humanity Protocol Mainnet Goes Live, Bridging Web2 and Web3 for Privacy-First Digital Identity
SE017 FinanceFeeds Humanity Launches $1.1B Mainnet in Bid to Challenge Worldcoin
SE018 Crypto Briefing Humanity Protocol Leverages ZK-Proofs to Protect Personal Identity Data
SE019 Cryptonews Can Humanity Protocol Avoid Worldcoin’s Pitfalls?
SE020 BanklessTimes Humanity Protocol Surges 65% Amid Worldcoin’s Credibility Problem
SE021 Humanity The Testnet Beta Is Live
SE022 Humanity Humanity Protocol Gears Up for Big Moves
SE023 Humanity H Token Recovery Program · Humanity Protocol
SE024 Humanity H Compromised Address Tracker
SE025 Metaverse Post Humanity Protocol Partners With Mastercard To Integrate Open Finance And Enhance Identity Verification
SE026 KuCoin What Is the Difference Between Worldcoin and Humanity Protocol?
SE027 Crypto Economy Humanity Protocol’s Mastercard Integration Expands Access to Global Finance
SU001 Humanity Verify anything, store nothing
SU002 Humanity Protocol
SU003 Humanity The Testnet Beta Is Live
SU004 Humanity Humanity Protocol Gears Up for Big Moves
SU005 Humanity Humanity Protocol Acquires Moongate to Accelerate Real-World Adoption of Decentralized Identity
SU006 Humanity Humanity Protocol Partners with Open Campus, Bringing Digital Identity and Credentialing to the Education Sector
SU007 Humanity Humanity Mainnet Integrates with Fireblocks, Expanding Institutional Treasury Access
SU008 Humanity Decentralized IDs are here: Humanity integrates with Walrus
SU009 Humanity Korea Hackathon Highlights: Real-World Use Cases Powered by Humanity Protocol
SU010 Metaverse Post Humanity Protocol Partners With Mastercard To Integrate Open Finance And Enhance Identity Verification
SU011 Crypto Economy Humanity Protocol’s Mastercard Integration Expands Access to Global Finance
SU012 Identity Week Humanity Protocol Mainnet Goes Live, Bridging Web2 and Web3 for Privacy-First Digital Identity
SU013 FinanceFeeds Humanity Launches $1.1B Mainnet in Bid to Challenge Worldcoin
SU014 Cryptonews Can Humanity Protocol Avoid Worldcoin’s Pitfalls?
SU015 KuCoin What Is the Difference Between Worldcoin and Humanity Protocol?
SU016 BanklessTimes Humanity Protocol Surges 65% Amid Worldcoin’s Credibility Problem
SU017 Humanity Docs What Is Humanity
SU018 Humanity Docs How Biometric Proof-of-Humanity Works
SU019 Securities.io Terence Kwok, CEO and Founder of Humanity Protocol – Interview Series
SU020 Pulse 2.0 Humanity Protocol: An Interview With Founder and CEO Terence Kwok
SU021 Humanity Palm Scanning Begins on Humanity Protocol
SU022 The Crypto Times ZachXBT Calls $32M Humanity Protocol Hack “Possibly Staged,” $H Crashes 86% Humanity Protocol ... suffered a $30-32 million exploit ... and crashed its $H token by 80-93% within hours.
SU023 Humanity Humanity Blog
SU024 Humanity Humanity Protocol Mainnet Live, Bridging Web2 and Web3
SU025 Humanity What Are Verifiable Credentials and How Do I Use Them?
SU026 Humanity Humanity and Moongate Make a Splash at TOKEN2049 Singapore
SU027 Humanity $H Now Supported on D’CENT Wallet: Security Meets Humanity
SU028 Humanity Hex Trust Secures Strategic Position in Humanity Protocol
SU029 Humanity Humanity Unveils Proof of Trust to Tackle AI Fraud
SU030 Humanity Humanity App Is Now Live on iOS and Android: Step Into the Future of Verified Identity
SU031 Humanity Can You Still Spot a Real Human Online?
SR001 Humanity Privacy Policy | Humanity
SR002 Humanity Terms and Conditions | Humanity
SR003 PCPD The Personal Data (Privacy) Ordinance
SR004 GDPR-Info Art. 9 GDPR – Processing of special categories of personal data
SR005 FTC Privacy and Security
SR006 Humanity $H Incident Summary | Humanity
SR007 Humanity H Token Recovery Program · Humanity Protocol
SR008 Humanity H Compromised Address Tracker
SR009 The Crypto Times ZachXBT Calls $32M Humanity Protocol Hack “Possibly Staged,” $H Crashes 86% Humanity Protocol ... suffered a $30-32 million exploit ... and crashed its $H token by 80-93% within hours.
SR010 Halborn Explained: The Humanity Protocol Hack (June 2026)
SR011 BSCN Humanity Protocol Launches Recovery Airdrop After $36M Hack
SR012 CoinAlert News Humanity Protocol to Airdrop New H Tokens After $36 Million Hack
SR013 BanklessTimes Humanity Protocol Surges 65% Amid Worldcoin’s Credibility Problem
SR014 KuCoin What Is the Difference Between Worldcoin and Humanity Protocol?
SR015 World World ID
SR016 Mordor Intelligence Identity Verification Market Size and Share
SR017 Mordor Intelligence Biometrics Market Analysis
SR018 FATF Guidance on Digital Identity
SR019 NIST NIST Special Publication 800-63-4 Digital Identity Guidelines
SR020 European Commission European Digital Identity
SR021 Entrust Identity Fraud Report
SR022 LexisNexis Risk Solutions Synthetic Identities and Agentic Bots Posing as Human Contribute to 8% Rise in Global Fraud
SR023 ID.me The 2026 Identity Fraud Landscape Report
SR024 Humanity Humanity Unveils Proof of Trust to Tackle AI Fraud
SR025 Humanity Decentralized IDs are here: Humanity integrates with Walrus
SR026 Humanity Humanity Mainnet Integrates with Fireblocks, Expanding Institutional Treasury Access
SR027 Humanity Humanity Protocol Mainnet Live, Bridging Web2 and Web3
SR028 Humanity Humanity Protocol Acquires Moongate to Accelerate Real-World Adoption of Decentralized Identity
SR029 Humanity Humanity Protocol Partners with Open Campus, Bringing Digital Identity and Credentialing to the Education Sector
SR030 Metaverse Post Humanity Protocol Partners With Mastercard To Integrate Open Finance And Enhance Identity Verification
SV001 Humanity Protocol H Token
SV002 CoinGecko Humanity price, market cap, FDV
SV003 CoinMarketCap Humanity Price History and Historical Data
SV004 CoinMarketCap Calculate Humanity to Tether USDT Live Today (H-USDT)
SV005 CoinMarketCap Latest Humanity News - (H) Future Outlook, Trends & Market Insights
SV006 Humanity Protocol Humanity Protocol raises $30M at a $1 billion valuation
SV007 CoinSpeaker Humanity Protocol secures $20M funding, hits $1.1B valuation
SV008 The Block Pantera and Jump lead Humanity funding round
SV009 Verdict Humanity Protocol raises $20m
SV010 Humanity Protocol The testnet beta is live
SV011 Humanity Protocol Humanity Protocol hits 1 million Human IDs on testnet
SV012 Humanity Protocol Humanity Protocol mainnet live
SV013 Humanity Protocol Humanity incident update
SV014 The Crypto Times ZachXBT calls Humanity hack possibly staged; H crashes Humanity Protocol ... suffered a $30-32 million exploit ... and crashed its $H token by 80-93% within hours.
SV015 Crypto Briefing Humanity Protocol pivots to enterprise AI after $36M hack
SV016 BSC News Humanity Protocol unveils recovery airdrop after hack
SV017 CoinAlert Humanity Protocol H token airdrop
SV018 SEC Palantir annual report on Form 10-K
SV019 SEC Okta annual report
SV020 CompaniesMarketCap Okta (OKTA) - Market capitalization
SV021 CompaniesMarketCap Palantir (PLTR) - Market capitalization
SV022 CompaniesMarketCap Coinbase (COIN) - Market capitalization
SV023 Metaverse Post Humanity Protocol partners with Mastercard
SV024 Crypto Economy Humanity Protocol Mastercard integration expands access
SV025 FinanceFeeds Humanity launches $1.1B mainnet
SV026 Identity Week Humanity Protocol mainnet goes live
SV027 KuCoin Difference between Worldcoin and Humanity Protocol
SV028 BanklessTimes Humanity Protocol surges amid Worldcoin credibility problem
SV029 Humanity Protocol Humanity mainnet integrates with Fireblocks
SV030 Humanity Protocol Humanity acquires Moongate