Content
@
https://warpcast.com/~/channel/bring
0 reply
0 recast
0 reaction
Mikhail
@zkbringer.eth
dev update pt2: Front-end: > @spacehzxmayhem is working day and night on the front-end, rewriting existing parts of the code to NextJS for Server side rendering and all-in-one platform experience - users will be able to launch new drops, see a list of created drops by other users and claim a drop, all within a single app. > We will use Privy for wallet authentication. Familiar for crypto native users and have an option to sign up with email for newbies (creating a Coinbase Smart Wallet under the hood)
1 reply
0 recast
4 reactions
Mikhail
@zkbringer.eth
Back-end: > As we rely on zkTLS to authenticate users and smart contracts to verify the proofs, we actually can deliver the service without intoducing a back-end logic. Which means that all logic will be onchain. Which means it will be easy to integrate zkBring in other apps and wallets without any vendor lockin. > Instead of a back-end we will deploy a zkBring indexer and use smart contract events as a data source. > To automatically index events we will create zkBring subgraph and use Goldsky Mirror to sync indexer with the onchain data > Here's the first version of the drop contract - https://github.com/zkBring/drop-contracts Very simple but good enough for the MVP. > We're targetting to have a testnet version of the platfrom by end of next week.
1 reply
0 recast
3 reactions