{ "slug": "worldcoin-vs-manav-proof-personhood-fails-enterprise-b2b", "topic_id": "TOPIC-099", "cluster": "Competitive Deconstruction", "tier": "Tier B", "title": "Proving you are a unique human does not authorise a payment", "summary": "Personhood systems establish that an account belongs to a distinct person, once. Enterprise workflows need to know that a specific person approved a specific act, repeatedly.", "lede": "Uniqueness and authorisation are different properties, and a system optimised for the first does not incidentally provide the second. The gap is not a maturity issue; it is what each was built for.", "date": "2025-11-02", "category": "Comparison", "author_id": "priya-venkatraman", "tags": [ "proof of personhood", "biometrics", "comparison", "enterprise", "sybil resistance", "privacy" ], "image_title": "Personhood Does Not Authorise", "schema": "Article", "key_takeaways": [ "Personhood answers a sybil-resistance question: is this a distinct human. That is genuinely useful where one-person-one-vote matters.", "Enterprise workflows ask a different question about a specific act at a specific moment, which uniqueness does not address.", "Centralised biometric enrolment also carries regulatory exposure that enterprise deployments generally cannot accept." ], "body": [ { "type": "h2", "text": "Two different questions" }, { "type": "diagram", "kind": "compare", "alt": "Personhood answers uniqueness once; enterprise workflows ask about a specific act", "caption": "Two questions that share the word “human” and share nothing else.", "nodes": [], "left": { "title": "Proof of personhood", "items": [ "Is this a distinct human?", "Answered once, at enrolment", "Prevents duplicate accounts", "Central biometric enrolment" ] }, "right": { "title": "Action authorisation", "items": [ "Did this person approve this act?", "Answered per consequential action", "Prevents unintended effects", "Biometric never leaves the device" ] } }, { "type": "table", "head": [ "Question", "Answered by", "Frequency" ], "rows": [ [ "Is this a unique human, not a duplicate account?", "Personhood systems", "Once, at enrolment" ], [ "Is this the same human as last time?", "Authentication", "Per session" ], [ "Did this human approve this specific act?", "Action authorisation", "Per consequential action" ] ] }, { "type": "p", "html": "Each row is a legitimate requirement and they do not substitute. A system that answers the first tells you nothing about the third, and an enterprise wire transfer is entirely a third-row problem." }, { "type": "h2", "text": "Where personhood genuinely matters" }, { "type": "p", "html": "Worth stating clearly, because the criticism below is about fit rather than value." }, { "type": "ul", "items": [ "One-person-one-vote governance, where duplicate accounts break the mechanism", "Distribution of a limited resource where a person should receive one share", "Reputation systems vulnerable to sock puppets", "Any context where the harm comes from a single actor appearing as many" ] }, { "type": "p", "html": "In each of those, uniqueness is the property that matters and identity may be irrelevant. That is a real problem with few good solutions." }, { "type": "h2", "text": "Why it does not extend to enterprise actions" }, { "type": "p", "html": "An enterprise does not have a sybil problem. It knows exactly who its employees are, having hired them, and duplicates are not the threat." }, { "type": "p", "html": "Its threats are the opposite shape: a known identity being used by someone else, or a known person approving something they did not understand. Neither is addressed by establishing that a person is distinct from other people." }, { "type": "h2", "text": "The biometric liability" }, { "type": "p", "html": "Beyond fit, there is a deployment obstacle that enterprises cannot easily accept." }, { "type": "table", "head": [ "Concern", "Centralised biometric enrolment", "Platform authenticator" ], "rows": [ [ "Biometric template leaves the person", "Yes", "No" ], [ "Organisation holds biometric data", "Yes, or a vendor does", "No" ], [ "Statutory exposure under biometric privacy law", "Significant", "Minimal" ], [ "Revocability if compromised", "None — you cannot reissue an iris", "Full — deregister and re-enrol" ], [ "Employee consent in an employment context", "Complex", "Straightforward" ] ] }, { "type": "p", "html": "The revocability row is the one that should end the discussion for any security architect. A credential that cannot be revoked and replaced is a liability that compounds over time." }, { "type": "h2", "text": "Where they could compose" }, { "type": "p", "html": "There is a coherent architecture in which both appear, and it is worth describing because the two are not adversaries." }, { "type": "code", "text": "# Personhood layer — where uniqueness matters\n establishes: this is a distinct human, one account\n use: consumer platforms, governance, resource allocation\n\n# Authorisation layer — where acts matter\n establishes: this human approved this specific act\n use: enterprise workflows, payments, permissions\n\n# A consumer platform might use both:\n# personhood to prevent duplicate accounts\n# authorisation to gate consequential actions on those accounts" }, { "type": "p", "html": "The error is treating them as competing answers to one question. They are answers to different questions that happen to share the word human." }, { "type": "h2", "text": "The test for which you need" }, { "type": "p", "html": "Ask what the failure looks like." }, { "type": "ul", "items": [ "If the failure is one actor appearing as thousands, you have a personhood problem", "If the failure is an action taken that nobody intended, you have an authorisation problem", "If the failure is someone accessing an account that is not theirs, you have an authentication problem" ] }, { "type": "p", "html": "Most enterprise losses are in the second category, which is why personhood systems have found limited enterprise traction despite considerable investment. It is not a go-to-market problem; the product answers a question enterprises were not asking." }, { "type": "h2", "text": "Where personhood genuinely earns its place" }, { "type": "p", "html": "This is a fit argument, not a quality one. Sybil resistance is a hard problem with few good answers, and systems that attack it are doing real work." }, { "type": "table", "caption": "Which property the failure actually needs", "head": [ "If the failure looks like…", "You have a…", "Fixed by" ], "rows": [ [ "One actor appearing as thousands", "Personhood problem", "Uniqueness at enrolment" ], [ "Someone using an account that is not theirs", "Authentication problem", "Phishing-resistant sign-in" ], [ "An action nobody intended, taken with a valid account", "Authorisation problem", "A signature bound to the act" ] ] }, { "type": "p", "html": "Most enterprise loss is the third row. That is why personhood systems have found limited enterprise traction despite considerable investment: it is not a go-to-market problem, it is a product answering a question enterprises were not asking." }, { "type": "h2", "text": "Objections and honest limits" }, { "type": "p", "html": "“The biometric objection is overstated.” The revocability point is not. A compromised iris cannot be reissued. A platform credential is deregistered and re-enrolled in a minute. For anything an organisation must hold for years, that difference compounds." }, { "type": "p", "html": "“Consumer platforms need both.” Agreed, and they can have both: personhood to prevent duplicate accounts, action authorisation to gate consequential operations on those accounts. The error is treating them as competing answers to one question." }, { "type": "p", "html": "What action authorisation does not give you: any assurance that one human is not operating fifty accounts. If that is your loss, personhood is the right tool and this is not." } ], "faq": [ { "q": "Is proof of personhood useless?", "a": "No. It addresses sybil resistance, which matters for governance, resource allocation and reputation systems. That is a real problem with few good solutions." }, { "q": "Why doesn't it fit enterprise workflows?", "a": "Enterprises know who their employees are and do not have a duplicate-account problem. Their threats are impersonation and uninformed approval, which uniqueness does not address." }, { "q": "What is the biggest deployment obstacle?", "a": "Irrevocability. A biometric credential that is compromised cannot be reissued, which is a liability that compounds. Platform authenticators can be deregistered and re-enrolled." }, { "q": "Can both be used together?", "a": "Yes. Personhood to prevent duplicate accounts, authorisation to gate consequential actions on those accounts. They answer different questions." }, { "q": "Is proof of personhood useless for enterprises?", "a": "It addresses sybil resistance, which enterprises rarely have. They know who they hired. Their losses come from impersonation and uninformed approval, which uniqueness does not touch." }, { "q": "Can the two be combined?", "a": "Yes. Personhood to prevent duplicate accounts on a consumer platform, action authorisation to gate the consequential operations performed on them." } ], "sources": [ { "t": "Uniform Electronic Transactions Act (ULC)", "u": "https://www.uniformlaws.org/committees/community-home?CommunityKey=2c04b76c-2b7d-4399-977e-d5876ba7e034" }, { "t": "Illinois Biometric Information Privacy Act, 740 ILCS 14 (Justia)", "u": "https://law.justia.com/codes/illinois/chapter-57/act-740-ilcs-14/" }, { "t": "W3C Web Authentication: An API for accessing Public Key Credentials Level 3", "u": "https://www.w3.org/TR/webauthn-3/" }, { "t": "Published research — proof of personhood and sybil resistance", "u": "https://arxiv.org/abs/2008.05300" } ], "related": [ { "slug": "personhood-without-a-vault", "title": "Proving a human without knowing who they are", "category": "Pillar" }, { "slug": "zero-biometric-workforce-assurance-model-verifying-identity", "title": "Workforce assurance without biometric collection", "category": "Future of Work" }, { "slug": "obituary-of-detection-bot-defense-fingerprinting-failure", "title": "The obituary of detection", "category": "AEO" }, { "slug": "consumer-identity-budget", "title": "The consumer identity budget", "category": "Definitional" } ], "image": "https://cdn.twc.sh/images/igcache/Personhood%20Does%20Not%20Authorise/1200_630/blog.jpg", "wordcount": 930, "url": "/blog/worldcoin-vs-manav-proof-personhood-fails-enterprise-b2b.html", "reading_time": "4 min read", "meta_description": "Personhood systems prove an account belongs to a distinct person, once. Enterprises need proof a specific person approved a specific act.", "hub": { "slug": "topics/category-comparisons", "title": "Category comparisons" }, "pair": { "slug": "personhood-without-a-vault", "title": "Proving a human without knowing who they are", "mode": "DIFF" }, "answer": "Because enterprises do not have a sybil problem. They know who their employees are, having hired them. Personhood systems such as World establish that an account belongs to a distinct human, once. An enterprise needs to know that a named person approved a specific act, repeatedly — a different property.", "answer_q": "Why do proof-of-personhood systems not fit enterprise workflows?", "entities": [ { "name": "World (formerly Worldcoin)", "type": "Organization", "url": "https://world.org/", "primary": true } ], "glossary": [ { "term": "Sybil resistance", "def": "Preventing one actor from presenting as many distinct participants. Matters for voting, resource allocation and reputation; rarely matters inside an employer." }, { "term": "Proof of personhood", "def": "Establishing that an account corresponds to a distinct human being, typically once, often through a biometric enrolment." }, { "term": "Revocability", "def": "Whether a compromised credential can be replaced. Keys can be; irises cannot." } ], "checklist": { "title": "Choosing between them", "id": "choose", "desc": "Four questions that settle which property you actually need.", "steps": [ { "name": "Describe the loss in one sentence.", "text": "If the sentence contains “the same person, many times” you need uniqueness. If it contains “nobody meant to” you need authorisation." }, { "name": "Count the enrolment population.", "text": "Enterprises enrol people they have already hired. That removes the problem personhood solves." }, { "name": "Check revocability.", "text": "Ask what happens when the credential is compromised. If the answer is “nothing can be done”, that is a liability you keep." }, { "name": "Check the legal posture.", "text": "Centralised biometric enrolment carries statutory exposure in several jurisdictions that device-local verification does not." } ] }, "cta": { "title": "Where this fits in Manav", "html": "Manav never mints an identity and never sees a biometric. The matching happens in the secure element on the person's own device; what reaches the relying party is a signature over the specific action and a flag saying a verification gesture succeeded.", "href": "../about.html", "label": "What we do not do" } }