Picket: Token Gate Anything
Picket allows you authenticate users based on their wallet and authorize users based on token ownership. It's OAuth 2.0 compatible, so it can be used securely on web or mobile.
Let me know if you are interested in trying it out and I can get you off the waitlist!
Trending on Indie Hackers
Had a similar idea after I made my own metamask signature login system. I'm curious on what the strategy to monetize this is?
That's exactly what motivated me to build this as well. Few ideas for monetization, depending on traction:
What are your thoughts?
I'm not sure about this. Users might be inclined to create new accounts and delete underperforming projects to stay on the free tier.
Need more details here, what does "Teams" functionality entail in the context of an authentication provider?
Most likely your best bet, make sure your login flow has branding so your free tier can drive organic growth. When I took notes on this idea I couldn't think of any better pricing model so I just wrote "Copy auth0 pricing" (https://auth0.com/pricing)
Another thing to consider is that most experienced Web3 teams are just going to make this in house; Especially when user wallets are already connected to their site. Maybe a possible feature improvement is the option to feed a Metamask/Wallet provider object to the SDK so the user doesn't have to connect to another site.
Lastly, you could do a free beta and maybe gather some analytics on average users per project and use that to help adjust your pricing cutoff.
Let me know if you wanna hop on a call and spitball some ideas.
We use Picket to power Picket, so an account is tied to a wallet-address. If you want to collaborate on a project with other team members, they cannot sign in because they don't have access to your private key. There are ways around this (sharing a wallet address) but at a certain point it's nice to collaborate w/o hacks.
This is already a feature : )
This is what were are doing now, Let me know if you or anyone who would be interested in getting access!
Will do!
You want to target beginner web3 devs for the barebones auth functionality because most big teams can (and already have ) made this in-house.
Some avenues I see that could lead to explosive growth among larger projects/communities
"Only if the user has staked tokens in this contract for x amount of time."
"Greater than X amount of money in crypto" (This is one DeBank API Call away)
Venturing into those areas will open up new ways to monetize and make it worthwhile for more experienced teams to overhaul their in-house web3 login.
I agree that it helps a beginner dev kickstart a project, which is a good starting audience; however, as a team/company grows I could see them wanting them to delegate auth security to a provider like Picket.
Couldn't agree more on these ideas. These are all on the roadmap. I think a key differentiator for Web3 Auth is that you can have these more unique and interoperable authorization methods like you are describing.
This comment was deleted 3 months ago.