Core proposition 🌀 help web3 users discover each other, transact, and collaborate through their identities in a trust-minimised way

• ✨ create a flow abstracted from your identity wallet
• 🫂 discover crypto users by ens, farcaster, lens, or address
• 💸 send, receive, request crypto, and more coming

Who is it for?

👥 someone who wants to:

• discover crypto users by their socials and transact without extra hassle
• minimise their main wallet activity
• have extra payment use cases beyond the conventional crypto wallet

59 seconds demo: https://www.loom.com/share/3279eb04f84d4d90bf69fcf876edd719

Payflow has four main concepts:

• flows
• signers
• identities
• payments

Flows

Flow is an abstraction over your identity wallet, the one connected to web3 socials, and the one you want to minimise making frequent signings. Each flow consists of a set of AA wallets across multiple chains (L2s), you can have as many flows as you like, but by default there is one pre-created on the sign up.

Signing

Signer (EOA/passkey) is used for login and signing all flow’s related transactions.

Identities

Identities (ens, farcaster, lens, or address) are used for linking your social graph to your flows so that you can be discovered by other payflow users. Also, potentially, identities can be used for flow’s recovery process, messaging, and other use cases.

Payments

You can attach different payment functionalities to a flow: send, receive, request, tipping, create a crypto jar for collecting crypto for any purpose, or create a community jar, co-owned by multiple payflow users. Ideally, identity is not involved in the flow signing process, although people can opt to use the same wallet as the signer and identity.

Proof & Attest

You need to prove identity ownership, so that the payflow system can recognise it’s linked to your profile, and your peers can discover your profile through it. While all wallets are non-custodial, if the server is compromised, a malicious user can manipulate flow and identity information. This is where EAS comes into the picture for attesting flow information ownership by identity.

P.S. You can try it out here (10 codes available): https://app.stg.payflow.me/connect?code=ensgrants