Tasit 🤐 (tasit.eth) retweeted
🎉 Apollo Client 3 is finally here!
apollographql.com/blog/annou…
Tasit 🤐 (tasit.eth) retweeted
Check out this simple demo native mobile dapp I made that generates an in-dapp Ethereum account for the user and then creates a contract-based account (@gnosisSafe) via CREATE2 with that account as the owner.
expo.io/@tasit/account-recov…
Powered by @TasitProject
Our contracts package is a lot leaner and meaner after the switch to Buidler + Buidler EVM by @NomicLabs, Waffle by @ethworks, TypeChain by @ethereum_ts, ethers by @ethersproject, and solhint by @ProtoFire_io.
github.com/tasitlabs/tasit-s…
Working on a new @tasit/hooks package in the Tasit SDK repo.
More info on custom hooks: reactjs.org/docs/hooks-custo…
Tasit 🤐 (tasit.eth) retweeted
reading through the @TasitProject docs and i can't vibe harder with their methodology. lets jam
Tasit 🤐 (tasit.eth) retweeted
Take a look at what ESP funded in the first quarter of 2020: blog.ethereum.org/2020/05/07…
Tasit 🤐 (tasit.eth) retweeted
Watch the “Native Mobile Ethereum dApps: Why, How & What to Do About Censorship” 🤐 🛠️⚙️ workshop from #ETHDenver with @paulcowgill of @TasitProject 📽️👉youtube.com/watch?v=LLm9ZQjS… #imapegabufficorn
Agree? Disagree? Hop in our Discord and let's talk about it.
discordapp.com/invite/bRp4QK…
You always can wire any of these accounts up with a "parent" contract-based account for shared account recovery settings.
And you always can link your accounts off-chain—ENS names make this easy—so this doesn't mean missing out on a global view of the state of your accounts.
Does this mean losing out on the convenience of single sign-on? Nope!
You still can use one of those identities across apps if and only if it makes sense for those apps to "know" about each other.
The Tasit project is working towards a future where people have 50 accounts, not just 1—some upgraded into contract-based accounts, some not.
A different use case warrants a different account/handle:
investment, savings, gaming, work, hobbies, side projects, social media, etc.
First it's counterfactually deployed, and then it's actually deployed.
Woah, both of those words have "actually" in them. 🤯
The burner account can be upgraded into a contract-based account as soon as the user needs features like account recovery, batched transactions, etc.
The user gets to pick their handle for that specific app (using an ENS subdomain under the hood).
Plus, automatically creating a new account is better for (A) OPSEC and (B) accounting reasons.
And it maps better to what people expect from web 2, where you sign up for each app separately.
The chorus cries, "Another new wallet?!?"
For new users, they don't have a preexisting account anyway, and this could evolve into their main account.
And it's not exactly a "wallet" if it's just a feature in an app that does one job well for the user.
