Mikhail

@zkbringer.eth

157 Following

188 Followers

Mikhail pfp

Some of the key learnings: - crypto power users hesitant to install a 3rd party extension. Updating the design to add more info about why the extension is required for the zkTLS verification and why zkPass can be trusted (500k+ installs, audited & open-source code, backed by legit VCs, etc) - less savvy users don't care that much about this issue (they mainly want to claim tokens) - since we launched the testnet version Reddit has retired the API endpoint we were validating and the zkTLS verificatiion schema no longer works. To mitigate this issue in the future: a. we're adding a way to update the schema for existing drops. b. we will limit timeframe of the drop (e.g. 2 weeks) to lower the chance of API changes within this timeframe

0 reply

0 recast

2 reactions

Mikhail pfp

zkBring demo: verify Uber account (at least one trip) and claim tokens. airdrops for real humans, not bots: > zkTLS verification via zkPass > instant gasless onboarding with Coinbase Wallet > token incentives to get onchain launching on Base soon. DM to test!

1 reply

1 recast

10 reactions

Mikhail pfp

0 reply

0 recast

1 reaction

Mikhail pfp

0 reply

0 recast

1 reaction

Mikhail pfp

With zkTLS, any data from any website can become airdrop criteria. The screenshot shows our current airdrops live on Base Sepolia. For Mainnet launch and our first zkTLS airdrop, we're designing criteria that: - are difficult to Sybil - are relevant to most users (at least one per person) - showcase zkTLS's full potential

1 reply

1 recast

6 reactions

Mikhail pfp

0 reply

0 recast

1 reaction

Mikhail pfp

0 reply

0 recast

0 reaction

Mikhail pfp

Thanks! DM'ed the link

0 reply

0 recast

0 reaction

Mikhail pfp

thanks for the comment. respectfully, disagree. instead of abstracting the tech away, we've intentionally decided to highlight it and educate our users about the tech. we think It's important: - for our users to see that verification is completely private (that's why they need to install the verification extension) - for crypto projects to get that we can target by absolutely any data on any website. we're also targeting crypto curious folks at launch (that's why the name is zkbring btw!)

0 reply

0 recast

1 reaction

Mikhail pfp

Launching next week. Anyone wants to test an early version on Base Sepolia and give us your feedback?

8 replies

1 recast

24 reactions

Mikhail pfp

Platform polished and ready. Launching soon. Currently finishing the docs and working on our first campaign drops.

0 reply

2 recasts

12 reactions

Mikhail pfp

How to disable multiple smart contracts to claim the same webproof and allow user to choose an address to claim after proof generation: 1. Create an ephemeral signer 2. XOR drop contract and ephemeral signer addresses 3. Generate webproof attached to the XORed address 4. Let the user create a new wallet and sign the fresh new address with ephemeral signer 5. At claim drop contract computes XOR address, verifies that it's attached to the webproof and verifies that claimer address was signed by ephemeral key initially I came up with hashing two addresses instead of XORing, but @cxrtisxl suggested XORing them instead of hashing and I liked it better.

0 reply

1 recast

3 reactions

Mikhail pfp

🤫 https://x.com/binji_x/status/1904378622992904314

0 reply

0 recast

4 reactions

Mikhail pfp

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

2 reactions

Mikhail pfp

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

3 reactions

Mikhail pfp

dev update: > as shared before, we decided to launch with zkPass and desktop-only version. The reason is that we found that a browser extension is the best UX for zkTLS proof generation: - you don’t have to enter sensitive credentials into a random app. - proof generation is both reliable and fast with zkPass > last couple weeks @noisebody0x and I spent a lot of time iterating on the drop page. We realized that we're one of the first teams working on a zkTLS user-facing product and we don't have a visual language to showcase the privacy benefits of zkTLS (similar to the private tab icon / HTTPS lock icon in browsers). So, we used a simple familiar structure for the functional part of the page (do something and get tokens) and intentionally decided to confuse users with unknown technical concepts like "Verify via zkTLS" and "Generate webproof" to educate them about the new tech. TBH i like what we got in the end. What do you think?

0 reply

1 recast

7 reactions

Mikhail pfp

dev update: > been quiet for the last couple weeks as we're busy working on the platform > decided to go fully desktop for the launch as we've discovered that the zkTLS xp is much nicer on desktop (check out zkpass) > launcher is ready, working on the platform now > expect couple more quiet weeks as the team full-mode building > really excited about the upcoming launch 😎

2 replies

5 recasts

10 reactions

Mikhail pfp

Yes, happy to hop on the call and share what we're building 😎

0 reply

0 recast

1 reaction

Mikhail pfp

re: onchain reputation: We will add SBT support to Bring. Generate zkTLS webproof of any internet data (e.g. that you've played N hours on Steam) and claim a corresponding SBT. Now you have a way to target Steam players onchain. https://x.com/JayLovesPotato/status/1894726519077138872

0 reply

0 recast

5 reactions

Mikhail pfp

some stats for our campaigns for far: It ain't much, but it's honest work.

1 reply

1 recast

3 reactions