Content pfp
Content
@
https://warpcast.com/~/channel/zora-devs
0 reply
0 recast
0 reaction
@isthispalash pfp
@isthispalash
@theprimefibber
Semicolon Fingers weekly update! First things first, it seems I may have underestimated the amount of work required, oops haha.. people will definitely be able to post their stories by next week 💪🏽 The past week I worked on contracts, the auth layer, and the writing side of the app.. The two biggest issues I faced / am facing, 1. User authentication using wallets 2. Managing three domains with consistent auth More below 👇🏽
1 reply
1 recast
3 reactions
@isthispalash pfp
@isthispalash
@theprimefibber
Using wallet sign ons — The main issue here is that this limits the number and the kind of users that can participate on the app.. Ideally, anyone should be able to publish stories, but having a wallet restriction forces users to first become crypto aware (if not native), and that is not the objective.. I even tried to move authentication later in the user flow (ie, after writing and just before publishing), and use Coinbase Smart Wallet, but that has a bunch of downstream issues, primarily the inability to write custom code around the Smart Wallet.. On the reader side of the app, the wallet login also becomes an issue since ideally the UX is being presented with a story from the get go and not bothering with web3 at all.. As a result, the move is now to do a username / password type authentication, akin to web2 platforms.. no need to reinvent the wheel just yet.. especially when trying to bring new people into crypto!
1 reply
0 recast
1 reaction
@isthispalash pfp
@isthispalash
@theprimefibber
With a traditional authentication, the issue is now managing it across three domains, ie, the main profile domain, the writer domain, and the reader domain.. As a result, a new repo manages auth and all domains ping the api of this [deployed] repo.. The auth service is written, now integration to the main app remains..
1 reply
0 recast
1 reaction
@isthispalash pfp
@isthispalash
@theprimefibber
In terms of contract development, one of the biggest challenges is managing gas.. The idea is to employ both testnet and mainnet where in all activity is stored temporarily on testnet and when the reader activity is finally Coined (read: committed), their activity is made "real" and put on mainnet.. CREATE2 is great here, since as the reading activity goes on mainnet, new app tokens are minted to target addresses which correspond to User Smart Wallets.. The app will not need to pick up the cost of deploying these Wallets (on register), as the users can deploy their Wallets when first withdrawing! More info can be found here (in a bit) ~ https://github.com/sliver-labs/semicolon-fingers/blob/master/docs/architecture.md#contracts
1 reply
0 recast
1 reaction