Web3 Onboard is Blocknative’s answer to delivering the best experience for developers and end users as they connect and engage across blockchains. It is an open-source, framework-agnostic JavaScript library to onboard users to web3 apps. Launched in 2019, Web3 Onboard is the quickest and easiest way to add multi-wallet and multi-chain support to a project. With built-in modules for more than 80 unique hardware, software, and browser wallets, Web3 Onboard saves developers time and headaches related to the UI and logic of connecting wallets to dapps throughout the EVM.

With Web3 Onboard, dapp developers can seamlessly connect user's wallets to dapps and track the state of those wallets. Developers can also customize Web3 Onboard to match the look and feel of a specific dapp. Transaction preview, an integrated feature of Web3 Onboard, is a modular UI for previewing a single or set of unsigned Ethereum transactions, which can help with testing and debugging transactions committed on-chain.

Web3 Onboard has an active developer community with over 350 community PRs. Recently, Web3 Onboard released SSO support by working with the Particle Network team on a [collaborative PR](https://github.com/blocknative/web3-onboard/pull/1962). This allows any dapp using Web3 Onboard to now provide social login with a few clicks. Additionally, Web3 Onboard has full EIP-6963 support giving dapp developers a new tool to decide which wallet should be connected to their dapp. This benefits the ecosystem in a few ways:
* Developers can customize their wallet connection experience to tailor to their individual application’s needs.
* Wallet providers no longer have to worry about optimizing for an obscure race condition, but can instead focus on what matters most - building the best wallet experience for its users.

Additionally, the Blocknative team spends countless hours developing the best end user UX to give the highest quality experience to every user interacting with dapp <> wallet connection through Web3 Onboard so that dapp developers don't have to.

