# What is Profile.io?

**Lighthearted Disclaimer:** the team at Profile.io are heads down focused on v1 build so up to launch, this documentation / images / diagrams may not always be completely up to date. 

**TLDR:** Profile.io is your open source web3 profile and payments network where you (or your org) own the data via web3 smart contract accounts.

Profile.io is a programmable verifiable identity network and app/dapp marketplace enabling users and organisations to capitalise on web3 identity assets including soulbound nfts and Verifiable Credentials to verify their proof of personhood and experience and to use the associated encryption keys to unlock tailored experiences.

[Verified profiles ](/system-overview/profile-verification)have access to the profile [payment infrastructure](/system-overview/p2p-payments), while EOAs can use profile username DNS to pay to known profiles, replacing cumbersome wallet payments.

<img src="https://890329260-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8gAppT0BU7sZ0RTGqCSS%2Fuploads%2FkIJ8XOO1JwgcvQ0arAyF%2FCSS%20badge.png?alt=media&amp;token=57efebe3-e750-406d-8dd8-763a047c2027" alt="" data-size="line">Users/Orgs collect web3 [badges](/system-overview/profile.io-architecture/badges-vcs-sb-nfts) from others to build their public, private and ZK profiles.&#x20;

Capitalising on Account Abstraction, profile.io is user friendly but powered by latest layer2 technologies including ZK.

Profiles are open source to enable a creative developer ecosystem and UI on platform and integration across web2 and web3. If a user wants our standard profile layout that's cool - but if you want it some other way, that can be arranged within our composable (providing structure) open source framework - e-commerce / creator specific etc.&#x20;

The app/dapp marketplace and developer toolkit makes use of Badges' programmable encryption keys to offer value and experiences to badge holders and issuer organisations.  Out the box dapps include a Farcaster client with tickets, loyalty etc to follow.&#x20;

## UI Treatments

<figure><img src="https://890329260-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8gAppT0BU7sZ0RTGqCSS%2Fuploads%2FhmVLXYignsawfLm5WDYV%2Fprofile.io%20profile%20treatment.png?alt=media&amp;token=eb35f850-aa01-465d-bf91-b137193ba8f6" alt=""><figcaption><p>Profile creation towards proof of personhood</p></figcaption></figure>

<figure><img src="https://890329260-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8gAppT0BU7sZ0RTGqCSS%2Fuploads%2FViXVhXAPnPGBzVZvzN8j%2Fprofile%20Credentials%20public%3Aprivate.png?alt=media&amp;token=fead3186-aedb-4c04-8917-e2a0b942c79f" alt=""><figcaption><p>Profile Badges and Verification process treatment</p></figcaption></figure>

<figure><img src="https://890329260-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8gAppT0BU7sZ0RTGqCSS%2Fuploads%2F9E8Trh1HnR2nG2oiGPLw%2Fprofile%20A16Z%20Dapps.png?alt=media&amp;token=6916737d-8a08-427f-bc43-edad020e9904" alt="" width="375"><figcaption><p>Organisation dapps unlocked for badge holders</p></figcaption></figure>


# Profile Product Roadmap

MVP (Released 2024)0606

* assign smart contract account and smart contract wallet to new user with subsidy of gas fee
* Profile setup with[ Smart Sections ](/system-overview/profile.io-architecture/profile-structure)(+ small number pre-configured sections)
* user selects username (url) and displayname
* create first soulbound nft badge with subsidiy of gas fee.
* invite another user with soulbound nft badge
* complete CV style profile&#x20;
* Organisation DID (Decentralised Identifier)

In Development

* Skill badge endoresement (adds onchain property to NFT)
* Add socials to profile
* Farcaster login and social graph leverage
* Links Section for profile (visual link to external content)
* Explore page
  * view users
  * view organisations
  * view available badges (soulbound nfts)
* Privacy and Visilibty settings
  * for profile
  * for individual sections
  * for badges
  * includes fully public, avilable to connections, fully private
  * backend ZK for chain privacy
* User creates custom Profile Section
* Organisation Profile Creation
* Organisation Course Listings Section
* Organisation batch soulbound nft badge issuance
* Organisation Education Certificate Issuance (embedding Org DID with Soulbound NFT)
* Further Badge Details
* Profile connections

Later

* Profile Themes (enable no-code customisation)
* Verify socials
* Wallet top up
* Connect third party EOA wallet
* Add profile smart contract wallet address to WalletConnect for nft issuance from third party platforms and aggregation of user soulbound nfts, poaps etc to Profile.io
* Profile verification using likeness check (web2) - verify real name profile or anon profile
* Profile verification using ZK likeness check (web3) - verify real name profile or anon profile
* Profile verification using profile algorithm (ie combination of nfts and social creates reputation score and proof of personhood likelihood)
* Profile DNS - use your profile.io/handle as your crypto wallet address
* Section Integrations - eg paragraph.xys; Farcaster recent posts; Frames etc
* Fully open sourcing profile sections for development
* Wallet and crypto functionality - to include staking

Considering

* Token value to profile ecosystem
* Appchain (L1, L2 or L3?) for soulbound nfts and DIDs at lower gas fee.
* DID for every user (current cost per user limitations) - own appchain may resolve.


# Design Direction

request access to figma.

<figure><img src="https://890329260-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8gAppT0BU7sZ0RTGqCSS%2Fuploads%2FuQhsW0omey2HQhex8XFK%2FSign%20UP.jpg?alt=media&amp;token=4041d908-36ff-443b-8ac3-d0bd3e4a974f" alt=""><figcaption><p>Sign Up</p></figcaption></figure>

<figure><img src="https://890329260-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8gAppT0BU7sZ0RTGqCSS%2Fuploads%2FAdKrOul610JYLtSgG2Aq%2FFull%20profile.jpg?alt=media&amp;token=8c3281e7-b89a-49ce-837c-40cce1aa327e" alt=""><figcaption><p>Full Profile (Design Direction) Next version is enhancing payment prominence and further profile configuration by user.</p></figcaption></figure>

<figure><img src="https://890329260-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8gAppT0BU7sZ0RTGqCSS%2Fuploads%2FywXg6vsDxSDELngj2JgM%2Fbadge%20view.jpg?alt=media&amp;token=2a185fc6-0a99-44bf-8864-b218e8e1f98f" alt=""><figcaption><p>Badge view</p></figcaption></figure>

<figure><img src="https://890329260-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8gAppT0BU7sZ0RTGqCSS%2Fuploads%2F5s9RdfmNl0zFpFeJlK3j%2FExplore.jpg?alt=media&amp;token=ad7a95ad-5156-41a1-bff2-19a7db6ec85e" alt=""><figcaption><p>Explore</p></figcaption></figure>

{% @figma/embed fileId="vRfd7nyiLAgeINsFoQhv0B" nodeId="3972:11204" url="<https://www.figma.com/file/vRfd7nyiLAgeINsFoQhv0B/Profile.io-Design?mode=design&node-id=3972-11204&t=ktsyvSQZD85NSyUB-4&type=design>" %}


# Motivation & Values

In no particular order:

* Web3 services and in particular wallets remain hard to use and inaccessible. Signing up to profile.io uses [account abstraction](/system-overview/account-abstraction) and alongside [unique IDno. ](/system-overview/profile.io-architecture/user-profile-id-data)and username setup, automates creation of smart contract accounts (initially Polygon and Solana) for holding identity assets and for payments, limited gas subsidy for skill badge issuance, web3 DNS record and if possible also automates [soulbound nft staking](broken://pages/uc0skcnHQV55tNomzBx6) - as again, staking is complex for the non-initiated.
* The internet is not at 'end game' in terms of architecture and sovereignty and an open source privacy preserving data architecture is required to avoid stasis and reach potential.
* User and Organisational data is not available across the internet or to the data owners and creators themselves.
* Current dominant platforms do not have a mechanism to enable both trusted and trustless interactions.
* Web3 identity is at its infancy and lacks useability and value propositions. Where digital ID is not government mandated, private companies are taking up the mantle but require careful design and incentivisation.  Profile.io seems obvious and needed but no-one else has done it.
* Proof of Personhood and proof of experience can take many forms and build towards an effective identity algorithm.  Identity is not an overt part of the brand.  Profile is about user experience, user reward and value and is technology agnostic provided that the technology can integrate and unlock wider blockchain based / decentralised use cases - so DID/VC / Ethereum Attestion Service / Soul-bound NFTs are all fair game and user experience will encompass these different technologies - as most users simply do not care about a DID or POP.
* No current plans to issue a token but remains under review if can serve a genuine purpose.  Others attempting this so far have largely fallen into traps of lack of usability or becoming only web3 native rather than looking to non-web3 users first.  Incentivisation is though key and other incentivisation mechanics (borrowed from web2 'golden' era) will be used - eg gamification and open app/dapp frameworks).

**Values**

* Sovereignty of data
* OpenSource and abstracted where possible
* Decentralised where possible

<br>


# SSI Basics & Concepts

Self-Sovereign Identity (SSI) is a user-centric approach to digital identity that gives people and organisations full control over their data. SSI enables anyone to easily share their data and reliably prove their identity without sacrificing security or privacy.

In other words, SSI enables you to manage and own your identity, which can span across a wealth of data points: from core identifiers such as your name, age and address, to your qualifications and health and insurance data, to social clubs and attendance proofs.

A key concept are Decentralised Identifiers (DIDs) which enable trusted issuance and also decentralisation.  DIDs are blockchain based so if an organisation wishes to leave Profile.io they can still access their DID.

SSI has an onboarding problem and lacks incentive structures which provides an opportunity for profile.io.

## How does SSI work?

SSI allows us to model digital identity in a similar manner to how we are accustomed to in the non-digital world through paper documents and cards.&#x20;

Trust Registries ensure that the overall system can be relied on and a decentralised trust registry of issuers is the goal of profile.io.

For example, instead of presenting a physical identity document, such as a drivers license or membership card, you present a digital credential that is securely stored in your Profile mobile app. These digital credentials can be reliably verified by anyone that you choose to share them with,  and even preserve sensitive information whilst proving that a statement is true, such as proving you are over 21 without disclosing your true age.

In doing so, SSI enables decentralised ecosystems to interact in cryptographically trusted ways. These ecosystems look like three-sided marketplaces, whereby every actor can take on three roles:

* **Issuers** - Parties who issue identity-related data to people or organisations in the form of digital credentials. These are the originators of data sources. *For example, a university that issues digital certifications to graduates.*
* **Holders** - Individuals or organisations who receive digital credentials that contain data about themselves. By aggregating and storing credentials in a unified Profile, Holders can build holistic digital identities that are under their control and can easily be shared with third parties.
* **Verifiers** - Parties who rely on data to provide products and services, who can reliably verify and process data presented to them by Holders. *For example, a supermarket that provides discounts to qualified health practitioners.*


# Profile.io Architecture

Profile.io connects web2 scalability and web3 decentralisation and privacy preserving technologies.  Inititial web3 networks that we are building on are the Polygon PoS network and Solana networks. Both provide vibrant developer communities and Polygon provides a suite of tools well placed for shipping an identity-focused application, while Solana offers fast NFT infrastructure.

[Polygon ID](https://polygon.technology/polygon-id) provides a toolkit for building SSI solutions that are natively integrated into the Polygon PoS network. This includes an SDK for creating featureful "identity wallets", and advanced technologies such as zero-knowledge proofs for data privacy and security.

As an open platform, the platform will support other DID methods, coming from other chains and technical providers and for example TDD and Cheqd DID and VC integrations are in development.

<figure><img src="https://890329260-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8gAppT0BU7sZ0RTGqCSS%2Fuploads%2FgfswyYzGpBFmAWypEtIT%2FProfile%20Concept-Page-2.drawio%20(3).png?alt=media&amp;token=bfc781a3-26ae-420f-aa8d-49318668435f" alt=""><figcaption></figcaption></figure>


# User Profile ID Data

A Profile ID comprises the following:

* The address(es) of the generated smart contract accounts (initially Polygon and Solana).
* An email associated with the Profile ID - this is useful for organisations issuing credentials who maintain a database of the recipients' emails, such as a University.
* A URL linked to their Profile ID (<https://www.profile.io/{Profile> ID}).
* A Decentralised Identifier (DID). This is a key component of SSI and is used to cryptographically pair a Verifiable Credential to an identity.
* Web3 DNS Address - either subdomain or standard url.
* Once verified, a verified member badge.
* Algorithmic proof of personhood score for trust mechisms.
* A linked EOA address, such as a MetaMask account (subject to certain rules) or;
* A linked ENS account (such as profile.eth). Only one linked account is permitted per Profile ID.

DIDs are constructed in accordance with [W3C standards](https://www.w3.org/TR/did-core/). A sample of a DID issued on Ethereum appears as follows:

```
{
  '@context': [
    'https://www.w3.org/ns/did/v1',
    'https://w3id.org/security/suites/secp256k1recovery-2020/v2'
  ],
  id: 'did:ethr:0xb9c5714089478a327f09197987f16f9e5d936e8a',
  verificationMethod: [
    {
      id: 'did:ethr:0xb9c5714089478a327f09197987f16f9e5d936e8a#controller',
      type: 'EcdsaSecp256k1RecoveryMethod2020',
      controller: 'did:ethr:0xb9c5714089478a327f09197987f16f9e5d936e8a',
      blockchainAccountId: 'eip155:1:0xb9c5714089478a327f09197987f16f9e5d936e8a'
    }
  ],
  assertionMethod: [
    'did:ethr:0xb9c5714089478a327f09197987f16f9e5d936e8a#controller'
  ],
  authentication: [
    'did:ethr:0xb9c5714089478a327f09197987f16f9e5d936e8a#controller'
  ]
}
```


# Profile Structure

In broad terms profiles are broken into:

* Header
* Sections, comprising:
  * Section Title
  * [Badge](/system-overview/profile.io-architecture/badges-vcs-sb-nfts) holding and associated text
  * Fields to include, dates / text / images (for experience purposes
  * API endpoints (to backend/enable other apps and integrations)
* Associated [Theme](/system-overview/profile.io-architecture/themes)

Sections are open source such that the community can adopt/adapt and create new Section types.

Out the box sections:

Socials

Claimed and Verified Skill badges (issued by self and from other users - initially programming language logos and assocated VC)

Work Experience

Academic Experience


# Themes

Like Wordpress users can integrate themes to customise their [profiles](/system-overview/profile.io-architecture/profile-structure).

This includes out the box themes, to grow into a marketplace in later versions; and

OpenSource framework to enable the addition of themes to marketplace and custom themes.


# Issuer (Organisation) ID

Each organisation has unique ID to be allocated via the [distributed issuer registry](broken://pages/7jgCIMo7rWbuGXr9X6WR).

hashes stored onchain

Onboarding of Issuers

* initial non-scaleable process of KYB
* long term issuer registry to be decentralised while maintaining unique ID approach
* API to integrate issuer

Admins are individual User Profile IDs. Can have more than 1 admin.

Admins can then issue VCs from the organisation to user profiles to hold in their account.


# Badges (VCs SB NFTs)

Badges denote a users verified credentials and can have various underlying verifiable technologies such as SSI VCs, soulbound nfts and others as they emerge. Programability provides dapp/app use cases beyond verification

Badges are initially issued by other users and orgs.

In future, a play to earn marketplace may be introduced with training / certification partners.

**Badge Example, Profile embedding and associated org Farcaster app/dapp**

<div align="left"><figure><img src="https://890329260-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8gAppT0BU7sZ0RTGqCSS%2Fuploads%2FUCQKIqqurFTzrutXwskV%2FCSS%20badge.png?alt=media&amp;token=e28b6c83-e2e2-4f47-be1c-bcfe3d8c5568" alt="" width="241"><figcaption><p>Badge treatment</p></figcaption></figure> <figure><img src="https://890329260-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8gAppT0BU7sZ0RTGqCSS%2Fuploads%2FE9tOXExoZXeymu1V38Z4%2Fprofile%20A16Z%20Badge.png?alt=media&amp;token=01ef7966-22bf-49c4-8a16-434dc0187454" alt="" width="375"><figcaption><p>Badge treatment in Profile</p></figcaption></figure> <figure><img src="https://890329260-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8gAppT0BU7sZ0RTGqCSS%2Fuploads%2F1D2HyPM1eAgtQLu3WCmS%2Fprofile%20A16Z%20Dapps.png?alt=media&amp;token=0a303462-dec2-4a89-84cb-31db8117c7d7" alt="" width="375"><figcaption><p>Organisation apps/dapps unlocked for badge holder</p></figcaption></figure> <figure><img src="https://890329260-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8gAppT0BU7sZ0RTGqCSS%2Fuploads%2FBdJicexYmGRYZf6cHi4T%2FIMG_EAD88FABF8C9-1.jpeg?alt=media&amp;token=f7a6fa44-545d-4998-999b-82d7876796e5" alt="" width="188"><figcaption><p>Gated Farcaster Alumni Community from out the box app/daps</p></figcaption></figure></div>

<figure><img src="https://890329260-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8gAppT0BU7sZ0RTGqCSS%2Fuploads%2FViXVhXAPnPGBzVZvzN8j%2Fprofile%20Credentials%20public%3Aprivate.png?alt=media&amp;token=fead3186-aedb-4c04-8917-e2a0b942c79f" alt=""><figcaption><p>Public / Private Badges -- Pending Verification / Verified Credential Treatments</p></figcaption></figure>

**Badge Thesis**

Profile.io initial central design will focus on real world user achievements such as academic and skill credentials, club membership and work/career.   In general badges are bound to a user and non-transferable other than from issuer to user.  While third party badges may enter the ecosystem, user to user transferability may be an issue to overcome given transfer can break down the trust framework (eg POAPs have genuine utility in our ecosystem but are technically transferable so may not reflect a user's actual achievement/credential). The focus is not on amassing NFT art in your profile or various crypto tokens. However,  as[ user profiles](/system-overview/profile.io-architecture/user-profile-id-data) are open source, the developer community may choose to give users the option for this in third party apps/dapps or potentially even a parallel core profile network.

Badges are verifiable and programmable.

Standardised [Schema](https://profile-1.gitbook.io/profile.io-technical-docs/system-components/badges) for different badge types is under development and will be subject to policy with ability for issuers to influence policy. Schema will assist programatic interface of [dapp/app](/system-overview/app-dapp-marketplace) developer for the [marketplace](/system-overview/app-dapp-marketplace).

Badges are Verifiable Credentials that are attached to a user's Profile ID, that are issued to them by Issuers (Organisations). The details contained within the Badge are stored privately off-chain, and it is entirely at the user's discretion whether they want to make it public.

Badges are ZK enabled - particularly relevant to [App/Dapp marketplace](/system-overview/app-dapp-marketplace) for ZK app access authentication.

All users to receive onboarding badges as progress towards [proof of personhood](/system-overview/proof-of-personhood-pop-algorithm) - unlocking incentives such as access to verified user P2P payment dapp.


# Data Registries


# Schema Registry

Registry of schema for VCs, to include:

* Name
* Fields
* Creation Dates.
* Versioning and permissions (ie for duplication and modification)
* Creator
* Owner.


# Trusted Registry

To include trusted Issuers; verifiers.

Initially centralised with roadmap to decentralisation and permissionless or delegated accreditation structure.

**Phase 1**&#x20;

Manual and non-scalable where necessary to ensure integrity (ie we manually accredit and check issuer organisations and associated admin users)

Make use of verified public ledgers such as stock market indices and regulated approved registries such as the FCA register.&#x20;

Do not rely on unverified public registers which may have the appearance of verification and trust. Classic example is UK Companies House company register which does not contain verfied data and can be too easily used for money laundering.

**Phase 2**

Building in collaboration with other SSI issuer platforms a permissionless and/or accredited issuance system.

Key traits:

* Avoid issuer duplication - 1 organisation per issuer (note this is a simplication as issuers may have sub-issuers and various badge types with levels of admin authorisation internally).
* Decentralised issuer trust registry on chain - system can reference issuer data - ie current assumed approach is that each issuer is public (while [users](/system-overview/profile.io-architecture/user-profile-id-data) and [badge ](/system-overview/profile.io-architecture/badges-vcs-sb-nfts)holder identity can be private behind ZK if the user wishes).
* To research and explore:
  * Accreditation of issuers:
    * is this the right thing to do?
    * process and rules
    * scalable mechanism - onboarding and offboarding issuers
  * Permissionless issuer trust registry and protocol
    * how can this not rely on a central authority?
    * what does the 'org chart' look like.
    * onboarding and offboarding issuers


# DID Registry

The Profile.io DID Registry is a core service that provides capabilities such as registering, managing, and resolving DIDs. Consumers can interact with the DID Registry to:

* Insert a DID document.
* Update a DID document.
* Revoke a DID (or the controlling keys).
* Resolve a DID (and obtain a DID document).

The Profile.io DID Registry will integrate with the DID Registry that is maintained by European Blockchain Services Infrastructure (EBSI) via an API connection.

Furthermore, Polygon ID provides a native DID Registry live on Polygon PoS network. The Profile.io DID registry will integrate with this also to pair with pre-existing Polygon DIDs.


# Profile Verification

Profiles are verified as follows:

1. for non-wallet owners via onramp verification.
2. for those connecting wallets, via initial kyc and wallet sanctions check
3. For those not following either formal verification process, [gradual proof of personhood algorithm](/system-overview/proof-of-personhood-pop-algorithm).

1 and 2 incorporate both basic verification memberships and premium memberships. cost is discussed (for simple comparison) to be c.$3 p.a. for basic members (ie cover kyc cost etc) and up to $100 p.a. for premium membership - with a growth hack discount for premium (eg first 1000 premium members costs $10; 2nd 2000 members costs $20 etc - to find price point.

Premium verification membership enables more minting of soulbound NFTs to your network and reduced payment transaction fees (see below).

Verification mints a soulbound NFT including DID information held against your [Profile ID](/system-overview/profile.io-architecture/user-profile-id-data).

Verification opens access to our [payment network](/system-overview/p2p-payments) (and other benefits as they are introduced) - enabliing verified users to pay each other.  Currently under review if profile DNS service from other EOAs can be enabled if user has not yet verified their profile.

Note - differentiate profile verification here - and account activation (by email or other 2FA).


# P2P Payments

Following profile verification, users can request and initiate payments to other profiles. &#x20;

Inbuilt wallet into platform, uses smart contract account - non-custodial wallet.

Attach own EOA to import crypto etc.

Currently under review if non-verified users can receive payment - but likelihood is yes.


# App/Dapp Marketplace

Consisting of open marketplace and pre-configured out-the-box solutions.

Platform to include programatic interface to enable dapp / app developers (including [organisations](/system-overview/profile.io-architecture/issuer-organisation-id)) to enable dapps to link to badge holders.

Following out-the-box solutions under consideration:

* P2P2B payments (fiat/cypto)
* Farcaster hub social network spinup for organisations to port social graphs via badge gating from profile.io badges.
* Towns spinup - gated by badges
* loyalty and other value transfer from organisations to badge holders - including potential for checkout integration. eg. Dapper Labs sports membership / season ticket holders badge gated discount store or game apps.
* Badge Holder Votes.
* \[Jobs - an obvious use case which may be a core app functionality (see [content](/system-overview/social-content-growth-vectors)) rather than app/dapp marketplace - under review]


# Account Abstraction

Profile.io smart contract accounts are developed in accordance with the [Safe{Core} AA SDK](https://docs.safe.global/safe-core-aa-sdk/safe-core-sdk). Safe is an industry-leading provider of smart contract infrastructure tools which secure over $46B of assets.&#x20;

Whilst Externally Owned Accounts (EOAs) have paved the way for user-owned wallets to interface with dApps and provide a non-custodial means to safeguard assets, certain barriers such as the need to pre-fund with Ether to submit transactions and the need to manage private keys deem EOAs unfit for mainstream consumer applications.

[EIP-4337 Account Abstraction](https://ethereum.org/en/roadmap/account-abstraction/) - smart contract accounts - is a standard that addresses a multitude of pain points implicating management of EOAs today. Such features include:

* Account recovery in the event that keys are lost or compromised.
* The possibility for dApp providers to subsidise users' transaction fees.
* Greater programmability that enables dApp and wallet providers to innovate on user experiences.


# Social / Content Growth Vectors

User interactions for growth

Profile adopts some social network vectors for growth and profile enhancement but keeps this curated in order to create high value experience and avoid replicating or trying to compete with other incumbent networks who have captured other social interaction types - including:

**Connections:**&#x20;

* References.  Vouch / Support / Endorse to help proof of personhood.
* Followers (of public profile)
* Connections (may experiment with close connection upper limit and may then get access to private profile)

\
[**Badge**](/system-overview/profile.io-architecture/badges-vcs-sb-nfts) **nudges . Badge claims**

**Content**&#x20;

Share what you know / share what you love / all content is linked to content types to bulid semantic knowledge base to improve efficiency of social content access. Content serves for knowledge and demonstrate profile value, while trying to avoid linkedin humblebrags and time-wasting.

* Article
* Event
* News
* Jobs
* Books

\
Feed - showing connections new public badges. New apps. Content.

Likes/Emojis/Comments + Tip for content (Fiat/BC/Eth)

1/1 Messaging

Group chat.

Most social interactions would take place through [app/dapp marketplace](/system-overview/app-dapp-marketplace) - ie farcaster etc.


# Decentralisation, OpenSource Overview and Compatability

Overview of approach rather than execution. Links to Values

**Decentralisation**

The platform will be decentralised where efficient solutions can be found but not at the expense of user experience or overall objective of building a universal profile.

Areas where decentralisation is likely:

* Trust Registries (issuers ie trusted orgs) - DIDs are onchain (in time will support multiple DID methods (if beneficial) so any user or org can leave profile with their DID intact.
* Badges (soulbound nfts and vcs) are on chain and so users are not bound to profile.io.

**OpenSource Approach**

Ensure composable elements of user profiles are opensource to ensure compatibility across web frameworks and apps.

Issuer components can also be open sourced.

To consider each element of the infrastructure in terms of suitability for open source.

Core platform updates will be determined by central team unless a point is reached where an alternative approach is required.

**Compatibility**

Credential Issuance and verification is open to multiple technical approaches, networks (and offchain credentials) and providers, with profile.io as a selected destination for credentials. We will engage wider developer community to achieve this compatibility.

App/Dapp integration requires standardised approach to integration.

Profile composable elements and ZK authorisation to be compatible across tech stacks via open source approach.


# Proof of Personhood (POP) Algorithm

**Approach**

POP scoring for each user and organisation based on multiple touchpoints.

**Assumptions**

* Users and organisations will not all want to use the same method of POP
* there may be one, many or a combination of proof of personhood methods that are valid
* some proof of personhood methods are valid contributors to POP score but imperfect as a sole point of reliance.
* Institutional registries (eg public Company registries) are assumed not to have third party verification until approved as part of algorithm
* Users and organisations will claim false credentials until

**Algorithm Components**

* Biometrics
  * worldcoin
* Approved National/International/Institutional credentials
  * ID cards / driving licence / BankID (Sweden) & other national ids
  * Stock market indices (ie reliance upon public company verification)
    * note that LEI (Legal Entity Identifier) & National Company Registries are unlikely to offer a valid POP component and each will need approval case by case
  * OpenBanking / Bank Statements / AML Credentials (eg from Coinbase if can partner)- digital integration
  * KYC / AML on platform (subject to budget constraints)
* Social-graph
  * Connections on Profile.io including:
    * endorsements from other trusted users and organsations
    * badges from issuer organisations


# Current live platform status

Status: Basic landing page live

Last update date: 16 September 2023

* [profile.io](https://profile.io) holding (and ugly) landing page published but not marketed / listed
* capturing incidental user sign ups.
* Docs published and under iterative development.


# User Flows

Access to figma may be requested.

{% @figma/embed fileId="NSh1LymyYIBQf7sb1eyA84" nodeId="5606:17209" url="<https://www.figma.com/file/NSh1LymyYIBQf7sb1eyA84/Tabled-Legal-Path-UX-%2F-UI?type=design&node-id=5606-17209&mode=design&t=jaPx1MYpSg2lLqQ1-4>" %}


# Use Cases

Commercial / not for profit Company:

* current employee badge
* former employee badge
* partner / customer badge
* supply-chain
* Pension credentials

Academic

* current class students
  * whole University
  * department
* former students / degree certificates
* schools
* Professional Accreditation
* Microcredits / online moocs

Professional Qualification

* Lawyer/Accountant
* professional creds - eg test engineer
* Distributed credential authorisation
* Medic/health

Non-professional Qualification

* eg Scuba

Clubs / Memberships / Association / Standards Bodies

* Current Membership badge - verified (eg Manchester United Supporters Club - with gated app).
* Former Membership badge
* Political parties

National ID / POP

* ID Card
* Passport
* Drivers Licence
* Proof of Age
* Proof of Address (historic)

Not focus for profile:

* your nft art collection
* your crypto collection (other than through native P2P payments dapp)


# About / Contact

Profile.io is a product being developed by tabled technologies - tabled.io

for all enquiries - paul \[at] tabled.io


# External Resources