Your account. Your history. Your say.
in development
A personal account for carrying your identity, learning and contributions across the system, with recovery and control over what you share.
This page shows the founding version. Community decisions will appear when the shared commons is connected. View collaboration status
View foundation versions, community decisions and original credits →Changing a phone, an application or a wallet should not mean starting your life in the system again. Umahn is the account and participation foundation we are building to carry your access, private context and useful history between services. Wallets on supported blockchains connect to that account, alongside the records and permissions you choose to use.
The account design connects devices, sign-in methods, email or social accounts and trusted recovery contacts under permissions you can inspect. It should let you recover access and change providers while keeping your records. Biometric checks normally unlock credentials on your device. Linking a service does not automatically give it control of your account or money.
You should be able to show a qualification, authorize a task or prove eligibility without exposing your whole life. Umahn’s planned private storage and separate identities for different contexts support that choice. Applications and agents receive defined permissions, with limits, expiry and revocation. Usage and attention may inform optional personal context; they do not silently become permission to act for you.
Proof of personhood is one part of Umahn: establishing distinct human participation while limiting disclosure. Alongside it, education and contribution modules connect learning, skills, teaching, work, care and creative activity to records you can carry forward. Bloom and other issuers assess learning; SideGigs and participating projects record reviewed contributions. Owning an account does not itself prove that someone is a unique person.
Umahn is intended to carry scoped reputation, work-impact assessments and governance eligibility or weight. Each needs its source, evidence, rules and a route to correction or appeal. SOS and participating communities decide how those records inform shared decisions. Payment, reputation, impact and governance weight remain distinct; a person’s dignity and basic voice do not depend on a score.
The naming and capsule experiment begins on SOS Systems, with Umahn as its intended home when the account foundation is ready. The future connection should preserve the source of claims and their history. Linking or migrating existing records needs a tested ownership and recovery process. Today’s Arc Testnet claims and early-claim points do not establish personhood, verified reputation or governance weight.
Umahn connects a person to their chosen services and participation history. Otto uses delegated authority; Bloom connects learning; SideGigs and other projects supply contribution evidence. SOS defines governance protections and rules. Each service should receive only the information and authority it needs.
Help test account recovery, connect a contribution or learning record, or design a fair way to challenge an assessment.
Propose, contribute & decide →