Sw/.tch

• **traditional **professional networks are not user-friendly for engineers. we want to control the data, see real connections and less messaging noisy.
• people create and host their profiles in the form of a standardized JSON on IPFS. benefit: data control, anyone can build an easily searchable database (scrape and fill Postgress, for example), where a recruiter has full flexibility of creating queries forgoing the limitations of custodial professional networks
• when 2 users worked together or know each other well, they can **stake **FIL (or other payment tokens) into their connection. think of it as a twitter blue mark but for connections instead of profiles
• referral fee if one user wants an introduction to a friend of a friend in the network, they pay a fee.

Motivation & impact -- professional networks' search interface is worse than SQL queries!! -- users should get paid for incoming messages, not the professional networked company -- users should control their data and not the professional company -- interface optimized for builders and hackers, not for hr/sales/bd. we want to see each other's source code

fevm CID control, graph of erc20vote tokens, and referral logic we wrap wFIL token used as a payment and stake it into the connections between friends

• people create and host their profiles in the form of a standardized JSON
• JSON has fields for skills, education, experiences, projects, hackathons
• people host themselves, so they have control over the data and can delete it whenever they want to
• the host URL goes into a file. the file is either shared publicly on IPFS or BitTorrent
• an opensource tool to scrape the self-hosted JSON resumes into a Postgres or an opensource search engine
• matching for projects open-source AI tool
• zk recommendations and social proof Bonus
• recipient gets paid for reading a message (from a recruiter, for example)
• friends
• posting things
• the UI has to be intuitive for coders first and only then others Motivation & impact -- professional networks' search interface is worse than SQL queries!! -- users should get paid for incoming messages, not the professional networked company -- users should control their data and not the professional company -- interface optimized for builders and hackers, not for hr/sales/bd. we want to see each other's source code