Through @Plaid's Wallet Onboard, @FranklinPayroll now supports more than 300 wallet clients! Employers and workers across wallets like @Ledger, @rainbowdotme , and @TrustWallet can now benefit from non-custodial payroll. Instant settlement. No more waiting 'til payday to get paid
@abishek@jaibhavnani we do this today! within our Investments API https://t.co/exvEdcD8bp
we added exchanges last year https://t.co/8g9bJGRIv8 and quietly added Ethereum self-custody wallets recently
still more data we want to add but getting there :)
Big news: weโve launched our first crypto-native developer product - Wallet Onboard. With a single integration, developers now have access to 300+ wallets.
It's been a fun ride building this over the last few months. Wanted to share some thoughts I've learned along the way ๐งต
Attention crypto devsโ๏ธWeโre so excited to introduce Wallet Onboard๐ช
โ๏ธ Connect your app to 300+ crypto wallets with one integration
๐ Simple, dynamic wallet selection for consumers
๐ Built with a privacy-first principle in mind
Get started now ๐ https://t.co/rnb4oNfIL5
All in all - this is just the beginning for us. We have an ambitious roadmap and Iโm excited about all the crypto-native things weโll be building going forward.
In the meantime, feel free to let me know what you think we should build next - always here for ideas!
Embedded crypto and โsufficient decentralizationโ (@farcaster_xyz) are my bets for the next wave.
Data will be on-chain where it actually makes sense (usernames, in-game items, etc), but it might be invisible to most consumers and powered by a traditional web2 stack in front.
@htormey use deep links/redirects as a way to pass data instead of a websocket relay (as well as replacing the current behavior of taking you into the CB wallet browser too)