Product

Consumer crypto is no longer limited by infrastructure.

Just good enough ideas and great execution.

well I would disagree

there are def a bunch of infra problems, eg replicating embedded wallets without vendor lockin. For me this is a problem, for u it might not be bc u can scale the team more easily

well I would disagree

there are def a bunch of infra problems, eg replicating embedded wallets without vendor lockin. For me this is a problem, for u it might not be bc u can scale the team more easily

https://ethereum-magicians.org/t/open-source-alternatives-to-privy-web3auth-and-dynamic/20209?u=timdaub

Founder /kiwi-news, a decentralized Hacker News

How do you solve vendor lock in at all in any intermediated system. Simple model: if you have api keys, there is lock in risk (same goes for AA or anything else). 

Escape hatches matter. But if we weren’t willing to deal with some lock in we’d all still be writing assembly.

Data privacy on the web. Keeper of the fabric @privy.

Fmr Protocol Labs consensus work. Before that YC S14 🇫🇷🌐🍊

It could be done, I'd just worry about security tbh

IMO it can only be dealt with by the app running the servers, so I‘d host my own version of privy on prem or smth like this, but I understand it is a considerable worse monetization model for you then and there doesn‘t seem to be defense either

Building dynamic.xyz | @dynamic | Craft magical onchain sign up experiences  - embedded wallets, login, user mgnt, authz and more | Demo: demo.dynamic.xyz

You use oidc for the login. This results in a JWT which is signed. So you can do a ZKP of it.

At scale you can make it cheaper to bring proofs onchain. You use zkJWT to add a key to the smart contract wallet that can be generated on the client.


The only security issue is sourcing the signing keys

https://warpcast.com/eulerlagrange.eth/0x06e4f6e8