Why We Chose Privy
We built the Adina Labs Decentralized Job Marketplace around a simple onboarding goal. Anyone should be able to sign up, build a profile, and reach real matches without setting up a wallet first. Privy is the piece of infrastructure that makes that possible, and this is a short explanation of what it is and why it sits in our stack.
The onboarding problem it solves
For most non-technical users, the first real obstacle in Web3 is not the blockchain itself. It is the wallet. The conventional path asks a newcomer to install a browser extension, create a wallet, record a recovery phrase, and understand gas and networks before they can do anything useful. That sequence works for people who already manage their own keys, but for everyone else it adds friction at the exact moment a new user is deciding whether the product is worth their time. Privy exists to remove that friction while keeping self-custody intact.
What Privy is
Privy is embedded wallet infrastructure for applications. When a user signs in with an email address or a social login, Privy provisions a non-custodial wallet for them in the background, and that wallet only acts when the user personally approves an action. It is non-custodial by design. Privy splits the user's key material and reassembles it inside a secure environment only at the moment a transaction is approved, which means neither Privy nor Adina Labs can access or move funds on a user's behalf. Users can also export their key at any time and move to a self-hosted wallet.
The company has a strong track record behind it. In 2025 Privy was acquired by Stripe, one of the most established names in online payments, and it currently powers more than 75 million accounts across the applications built on it. For us, that scale and backing signal a wallet layer mature enough to run under a marketplace for years.
How it improves the experience
Privy lets people into the Decentralized Job Marketplace the way any modern application would, through a familiar login, with no extension to install and no seed phrase to memorize. Users who already hold a wallet can connect their own instead, and both paths follow the same rule underneath. Every action that moves value or writes a record on-chain requires a signature from a wallet the user controls.
The result is an experience that meets mainstream users where they are while preserving everything that makes Web3 worthwhile. People can participate first and encounter key management only when it genuinely matters, and the ownership of their wallet stays with them the entire time.