> For the complete documentation index, see [llms.txt](https://docs.governordao.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.governordao.org/products-and-services/proof-of-existence.md). # Proof of Existence (PoE) ### Introduction {% embed url="" %} Proof of Existence Overview {% endembed %} [Proof-of-Existence](https://onevoiceonevote.governordao.org) is a first-of-its-kind innovation in Sybil resistance, which addresses the decade-long dilemma of "how do I build decentralized systems designed for one account per user if I can't vet the accounts?" In other words, if you design your contract/emissions/token launch/consensus model around the notion that everyone gets one account, how do you stop people from using multiple accounts? The original answer, pioneered by Bitcoin and Proof-of-Work, is to make weight-based systems: the more hashrate you provide, the more BTC you earn. This model is permissible in some instances (yet rarely optimal). Uncapped, performance-based POW has resulted in an increasingly energy inefficient, expensive consensus model. In yield farms and governance voting, it means whales dominate the game and small accounts have virtually no say. In token sales and NFT mints, it means users are competing in gas wars against bots and multi-account participants. The only widely used defense today against multi-account and bot abuse is KYC, which has a separate set of baggage. Proof-of-Existence is the first easy-to-integrate, non-intrusive, 100% effective, universal defense against Sybil attacks. ### How it Works In partnership with leading biometrics firm Finnovant, Governor DAO has created a portal for biometric authentication of Ethereum wallets. Users enter the portal with a web3 connected wallet and input face + voice readings. Locally, the user device runs the input information through hundreds of algorithmic indicators to create an encrypted output hash representing the individual. No two individuals produce the same output hash, and Governor DAO receives the hash that corresponds with the input address. If the hash is unique from all others in the system, the address is tokenized as "provably unique". A non-transferrable ERC20 "Proof of Existence" token is attached to the user wallet, which enables any smart contract to easily check for that verifiable uniqueness with just one additional line of code. ![](/files/-Mi7AMYmMWVAi1PWdFMc) #### Security Notice: Governor DAO biometric signup is 100% anonymous and non-intrusive. Persons' biometric readings are hashed locally in the user device, and only the encrypted output is shared. No human ever sees face or voice readings. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.governordao.org/products-and-services/proof-of-existence.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.