🎙️From AWS to Aave & Lens Protocol: Nader Dabit Explains Web 3 Social Media

Nader has become a household name across the developer community with his combination of to-the-point tutorials, live coding demos and interviews focused on modern web development, Web 3, AI, cloud computing and more. He’s always learning and experimenting in public. Nader is currently the Director of Dev Relations at Aave/Lens. Today, he’ll get to do some details behind his journey into Web 3 starting with The Graph, decentralized social media, the devs building on the Lens Protocol, Lens infrastructure and he’ll give us a mini deep dive into gasless transactions via Lens. But first, Nader tells us about what it was like being early to AWS before he made his switch into Web 3 full-time.

🙏 Thanking our podcast sponsors:

• Stader Labs, a multi-chain liquid staking platform with 40k+ DeFi partnerships across 6 chains, is coming to Ethereum soon. Sign up to get alpha on ETHx—their ETH LST. Be the first to know about $1M in DeFi rewards!

Listen to the Interview:

Watch the Video:

• Timestamps
  00:00 Introduction
• 00:57 Transitioning from Big Tech to Web3
• 04:04 A Developer’s Journey and Advice
• 16:15 Building a Web3 Social Network: Lens and its Potential for Developers and Users
• 27:54 Exploring the Culture and Censorship Resistance of Decentralized Social Media with Lens
• 33:06 Building on Polygon and Achieving Permanence: A Look into the Lens Infrastructure
• 37:09 The Unique Mechanisms and Future Opportunities of Lens On-Chain and Web3 Social
• 43:59 Building a Data Availability Layer for Social Networks: The Lens Approach
• 47:44 About Execution and the Go Token Launch
• 49:16 Lens’ Competitive Landscape and User Metrics
• 52:53 How to Get Started on Lens as a User or Developer
• 54:46 What’s Next?
• 55:45 Gitcoin Passport

🔒 PREMIUM SUBSCRIBERS GET A FULL TRANSCRIPT OF THE PODCAST BELOW. THANK YOU FOR YOUR CONTINUED SUPPORT OF INDEPENDENT JOURNALISM FOR WEB3!

7 Key Takeaways

1. Nader Dabit, a developer with experience at AWS, transitioned to web3 due to an interest in serverless technology and the potential of blockchain for building products and applications.

1. Dabit’s advice for Big Tech developers looking to transition to web3 is to have a long-term vision and be committed to the ups and downs of the industry.

1. Dabit recommends learning in public and sharing what you’re learning as you go along, which can help others who are just starting out.

1. Dabit is excited about the potential of AI and blockchain for data analysis.

1. Lens is a web3 native social network that offers infrastructure for building social features into applications.

1. Lens is built on Polygon, a sidechain that is more centralized but less expensive, and is rolling out a new infrastructure that uses the Bundlr network and Arweave for permanence.

1. Lens is working towards decentralization in various aspects of their infrastructure, but it’s still a journey. Communication is key in these situations, whether it’s reaching out to engineers on social media or asking for help in a chatroom.

Transitioning from Big Tech to Web3: A Developer’s Journey and Advice

I have been a developer for 11 years now, starting at AWS. At that point, I was already interested in developer tooling and being part of the developer ecosystem. I have written open source and taught developers how to build apps. Working on infrastructure that allows other developers to build their own apps and companies was exciting to me. Around the same time, serverless technology was becoming more popular, and AWS was rolling out many new serverless services. It was an excellent opportunity to help build infrastructure that other developers could use to build their own applications. I was able to join that team and stayed there for a little over three years, where I learned a lot and had a great time in my career.

In 2016 and 2017, I started trading and being involved in crypto, but I was just speculating and didn’t really know what I was doing. Later, after the boom and bust cycle of 2018, I got back into trading and started doing research on The Graph token. Learning about the underlying technology made me realize that crypto is not just for speculation but for building products and applications. This led me to dive down the rabbit hole of web3, especially after watching talks. At that point, I was looking for the next thing to work on and became really excited about web3. I looked around at different protocols and places to work and reached out to The Graph. Since then, I have been all in on web3 and it’s been a fun time.

Can you share some advice with someone who’s in Big Tech and maybe looking to do a similar transition to web3?

To enter this space, you need to know what you’re getting into, even if you prepare mentally. It’s been a rocky ride, but I have learned a lot and I am happy to be here. There are many ups and downs, and with regulatory uncertainty, some days are good while others are bad. You need to have a long-term vision and be committed to what we are working towards. If you’re only in it for the short term, it will be tough to stay during the ups and downs.

Do you have any advice for others that might be aspiring to be devrel in crypto? How do you recommend they approach that?

One of the best things I’ve learned as a developer is the idea of learning in public. This has worked really well for me. As you gain more experience, you can pick things up faster. If you publicly share what you’re learning as you go along, people resonate with that. It’s as simple as being out there, learning and trying new things, and sharing what you’re doing. This can help people who are just starting out. As a self-taught developer, I appreciated all the content that others put out there for me to learn and get started. It’s fulfilling for me to be able to do the same for others.

What’s the best medium for that learning in public? Do you recommend a YouTube channel, Twitter? What would you recommend to people?

I think it’s a combination of those things, but it also depends on what that person’s good at. I think certain people are excellent at video production. Some people are really good at social media. So I would say experiment. Find the things that you’re good at and really double down on the things that you’re most effective at.

@chainyoda on Twitter asks: How does ser travel so much? Whats sers formula for managing jet lag and quick recovery from #DevRel travel?

It’s really tough to get used to jet lag. The key is trying to reduce travel as much as possible, but I’m still on the road about once a month. When I do have jet lag, I just have to get used to dealing with it. I don’t really have a good answer for how to avoid it, but I think being consistent with my work will help me stay consistent regardless of time zone or location. When I’m traveling, I know that I’ll probably get less done, so I try to be productive when I’m not traveling.

@owocki on Twitter asks: How do you build stuff so fast and what’s your secret?

Sometimes I find it easy to jump into a code base and understand it quickly, but other times it’s a struggle. I can be very stubborn when it comes to learning something new and will often stay up all night or spend a whole week trying to figure it out. When working with bleeding-edge technology, it can be especially frustrating when things break and no one responds to your requests for help.

I had an issue with the GPT Slack plugins where my app stopped working and no one responded to my messages for a while. I even created a video, but it still didn’t work. Eventually, someone from OpenAI helped me, but it turned out the fix wasn’t deployed to production yet.

When you finally figure something out, it feels great and you can share that knowledge with others to save them from the pain and suffering you went through. Communication is key in these situations, whether it’s reaching out to engineers on social media or asking for help in a chatroom.

What new technologies are you most excited about tinkering with? Or would you recommend someone who’s interested in this career path to start looking into?

I am excited about the potential of AI and blockchain, especially when it comes to data analysis. Even though I am not a data scientist or a Python developer, I think these technologies have become more accessible to everyone through the use of APIs and SDKs. I’m looking forward to experimenting with AI in combination with blockchain and web3 principles. At Edge and Node, I had the opportunity to start learning about the web3 stack, which sparked my curiosity. I am still eager to discover more about the protocols, tools, and SDKs that work in web3 and figure out how to use them to build the ideas I have.

You’ve actually had a very interesting journey in your short time in web3 between The Graph and Celestia and now to Lens on the decentralized social media side. So talk to us a little bit about that journey and then I wanna deep dive into Lens.

I am someone who is always interested in learning and finding out different things, and the space I work in moves extremely quickly. With my interest in web3, The Graph was a great introduction for me. The founding team and I have very core beliefs about what it means to be decentralized, and the work that we are doing will lay the groundwork for this. While at The Graph, I started becoming more interested in these niche areas in web3 that had massive challenges, such as scalability, UX, and security.

Celestia was one protocol I became interested in, but I also realized that there are other solutions, such as Arbitrum Nova and what we’re releasing soon with Lens. Once I understood that Celestia was a really low-level protocol and I felt I wasn’t contributing effectively, I started to become interested in other things.

I considered opening my own consulting company and doing software engineering, but I ultimately joined the Aave and Lens team, where I am now. Even though I work with Lens and Aave, I still experiment with other protocols and do a bit of consulting on the side.

Building a Web3 Social Network: Lens and its Potential for Developers and Users

Lens is one of the more web3 native social networks. Let’s start with why we need a web3 Social network in your opinion.

I believe there are a couple of perspectives to consider here. First, there’s the user perspective, the developer perspective, and the infrastructure perspective, including how the applications will ultimately progress through different front ends. When thinking about traditional applications and social networks, one typically thinks of a company building the entire front end and back end, maintaining everything in a siloed database that is inaccessible to anyone outside the company. However, what really stands out about web3 is the open public composable backends and infrastructure that anyone can build upon. This is why I was attracted to web3 the most. The go-to-market for something like a social network in web3 looks a lot different from web2, where you control the entire stack.

With Lens, we are building and maintaining high-quality infrastructure, including smart contracts, making it easy for people to build their own APIs, and offering an API as well. The developer only needs to be a front-end developer; they don’t need to know smart contract development, DevOps, or database engineering. This enables faster and easier building and experimentation. You end up having more experimentation on the front end, and there are already dozens of mobile and web apps, some of which have valuations in the range of tens of millions of dollars. This is because developers can focus on just one thing and do it really well, without worrying about everything else.

Another area that separates web3 from web2 is that when you want to build social features into your application, you typically hand-roll everything from scratch. However, with Lens, developers can use it as an infrastructure layer to build social features into their apps that might not necessarily be thought of as social apps.

Starting with a bootstrap user base of 100,000-110,000 users on Lens makes it easier for developers to build and deploy their apps without starting from scratch. Once we remove the allow list/white list portion of the sign-up process, it will be even easier for people to treat Lens as an infrastructure layer.

I wanna ask one question on the building around Lens. And I also wanna get into what the listeners could do on Lens. So first, you’re enabling developers to build on top of Lens. How’s that been going and what are some of the more exciting apps that you’ve seen?

As a developer advocate, my team and I prioritize the developer experience, always taking into account feedback from developers to create tools and SDKs that simplify the process and reduce the barriers to entry for building what they want.

We’ve developed various SDKs, such as React Native mobile SDK, React Cooks SDK, and a Big Query API, which allows developers to create machine learning and AI algorithms from large data sets. While still in beta and currently closed off, our protocol has been successful, though my biggest challenge is getting developers excited about it.

We plan to remove this limitation later this year. Personally, I have noticed that I tend to use social media when bored, but lately, I have been using Orb, a mobile app for Lens that is highly polished and probably the best Lens app available. I also recommend checking out Lint Tube, a Lens YouTube-type app, and Lister, the most popular app on Lens. We have various niche communities focused on different interests such as art, music, and fashion, such as Enzo Collective.

Why did you guys start in the beta, like the closed beta phase as opposed to starting open and permissionless?

I think the main thing is that we just didn’t have everything figured out quite yet. And we’re solving the two biggest challenges today that we’re actually rolling out something when this podcast goes out, which will probably be after tomorrow, and we’ll have solved.

The first challenge is scalability because Lens runs on a blockchain period, and even though blockchains have come a long way, Polygon only scales to a certain amount, right? Even the blockchains that are considered the most scalable still are orders of magnitude less scalable than a traditional database. I’m trying to build the type of application that is similar to what we’re used to web2.

So with Twitter, I think Elon Musk tweeted that out there were like 50,000 interactions per second during the World Cup, but blockchains, a few hundred, maybe a few thousand transactions per second is what they can handle. And these are also shared execution machines. Not only are we using that portion of the thousand transactions per second, but every other app in the world is all kind of fighting for this limited resource. So Lens just did not scale enough for us to enable anyone to use it because we would either bring down the network or the gas prices would go so high that it would make Polygon unusable.

So what we’ve been building since December, when I say we it’s really the engineering team, and they’re really smart and they deserve all the credit, have built out what we’re calling like an Optimistic L3 and this is a new protocol that has been built from the ground up. That will scale in the range of 25 to 55,000 transactions per second. And this has been tested and tested. These aren’t just random numbers that are being thrown out. It actually does do that. So I’m really excited to bring Lens to scale.

The next thing we’re doing beyond that is we have to figure out and actually execute on how to do content moderation in the sense that if someone bots the network with a bunch of spam, do we want that to show up or not?

Now, if we’re building on a permissionless protocol, we can’t stop those people from doing that. So at the protocol level, nothing’s happening. But we do have different APIs that people can choose to use. We have different recommendation algorithms that people can choose to use. And when someone logs into Twitter and 99 out of the hundred comments on their post or bots, the experience is really bad. So we don’t want that to be happening on Lens. Therefore, we’re figuring out how to make our API that people can choose or not choose to use display in a way the content that makes it a good experience.

That’s the next phase of what we’re doing. Once that has been rolled out and you could almost bucket that as civil resistance in some way, it’s kind of a form of civil resistance, then we’ll make it permissionless because then we want anyone to be able to use the app and for it to be a good experience.

Exploring the Culture and Censorship Resistance of Decentralized Social Media with Lens

There are these things that kind of spring up when you have a decentralized social media, right? Decentralized social is manifested by different protocols at the algorithm layer, and perhaps people might be compensated to build algorithms, with a top 10 to 50 list. The moderating protocol is the same. People can be compensated for moderating content and categorizing it. And then, on the reputation front, how do you think about these various parts and how do they apply to Lens? Do you believe that such economies and marketplaces will emerge?

We already have several teams building their own recommendation algorithms for people to use. One team, in particular, has members from prestigious schools like Harvard and experience working in big tech. They have created an algorithm that works well and are talking to front ends on Lens. If they want to use their algorithm instead of our APIs, they are free to do so. Additionally, there is a project creating an MPM type of repository for algorithms that developers can opt into or users can choose their own algorithm. Everything is on chain and public.

There’s a lot of experimentation happening, and we’re not sure what will be successful. At the base level, we want to offer something usable, and once developers gain traction, they can optimize their builds with some of these other solutions.

I’m not sure if you heard, but TikTok was in danger of being banned. now TikTok has announced that they will begin banning some content. So it’s intriguing because, in my opinion, these digital firms should not be the ones to dictate or judge what truth is. It should be up to the individual to pick what content they may view and what content they want to see, as well as what algorithms they want to see, rather than extractive algorithms that are only looking to monetize the users. What is the culture like within Lens when it comes to these kinds of topics?

I believe that the culture at web3 is very open. We all have our own opinions and there are a lot of discussions where people disagree with each other, which I think is a good thing. There shouldn’t be one person dictating what should and shouldn’t be done. We have a lot of smart people from different backgrounds, which makes for interesting conversations with diverse perspectives. It has been an amazing experience for me, and I can’t complain about any of the work I have done at web3.

How are you guys approaching that just within the Lens ecosystem in terms of censorship resistance?

At the protocol level, there is no way to censor anything. It’s like how a transaction cannot be stopped from being written to the Ethereum network. However, people can choose which algorithms to buy into, which APIs to use, and even build their own APIs to surface the content they want to see.

The protocol is completely censorship-resistant, but the middle layer where people query their data is where censorship can occur. It is up to the user and the developer to decide whether or not to censor anything. Currently, there are a handful of APIs available, including our API, but in the next six months, we may see more widely used APIs that differ in how they handle content moderation. With a million people using the protocol, certain things should not be surfaced, such as violent content in front of children. There are various scenarios that need to be considered, but ultimately, it should be up to the user to choose what they want to see.

Building on Polygon and Achieving Permanence: A Look into the Lens Infrastructure

You mentioned Polygon. Let’s double-click into that. Why the choice to build on Polygon as opposed to maybe a layer two like Arbitrum, Optimism, zksync?

The decision to use Polygon was made before I joined the company, but I understand that the tradeoff with Polygon is between decentralization and scalability. Polygon is more like a sidechain, and it is a little bit centralized. However, the transactions on the network are less expensive, although I’m not sure if they are faster.

The company is rolling out a new infrastructure that uses Polygon but is around 700 times more scalable and around 1000 times cheaper than being on Polygon directly. Only things that need to be on-chain will be on the actual blockchain, while everything else will be stored in a permanent, decentralized network. For example, commenting on a post or posting a tweet does not need to be on the chain. Only things that need to be tokenized will be on the chain. The technology that’s enabling this under the hood is the Bundlr network.

That’s great that it’s crypto native and then why are we over an IPFS?

In order to achieve the idea of permanence, IPFS requires a lot of complexity built on top of it, such as Filecoin and other technologies.

What sets Arweave apart from IPFS, as learned at The Graph, is that Arweave not only offers immutability like IPFS, but it also promises permanence, which is dependent on the protocol existing and the technology working. The founders of Arweave say that it will work and it has been working well for a number of years, so the issue of permanence is not a concern. Therefore, Arweave was chosen due to its promise of permanence.

Are there any other notable aspects of the Lens infrastructure that maybe are centralized today that still need to be decentralized?

Maybe around the gateway side, the proxy side. I think right now decentralization is very much a journey and would love to understand those components. And then also how serious Lens is around decentralization.

The current API is centralized, but there are plans to decentralize it in the future. Once the new infrastructure is rolled out and challenges like filtering users are solved, the move toward decentralization will begin. The company also plans to support the Graph protocol on Polygon, which will provide a decentralized option for API usage.

The Unique Mechanisms and Future Opportunities of Lens On-Chain and Web3 Social

Describe the unique mechanisms of Lens on-chain. So maybe around the profile, comment, mirror, collect, monetization, follow, etc.

Lens on-chain has unique mechanisms that differentiate it from traditional social networks. One of the reasons users are drawn to it is the built-in monetization, which allows creators to attach a dollar value to their posts and allows supporters to easily pay and show their support. These payments are made directly from one user to another, without any middlemen, and are enabled by on-chain and crypto-native features. This creates opportunities for creators to earn revenue in small amounts, which is more accessible to a wider audience than high-value NFTs.

The user’s profile itself is an NFT, which allows for ownership and transferability of all publications and comments associated with that profile. Overall, Lens on-chain offers unique mechanisms for monetization and ownership that are enabled by on-chain features and NFTs.

Can you talk a little bit about how Lens and web3 social is changing the landscape for how content creators can think about monetization beyond what you already shared?

The team has multiple groups working on different projects, and a few of them have been very successful and are already seeking funding due to their popularity. One such project is Waves, which allows content creators and influencers to be paid directly through the platform. Instead of spending a marketing budget on traditional social media platforms like Facebook, Waves uses on-chain information available through Lens to find users who resonate with a particular audience and pay them to share the content. A campaign can be set up with Waves where a budget is allocated for a publication, and users who meet specific criteria, such as having a certain number of followers, can participate by sharing the publication and receiving a direct payment. This approach can help reach a segmented audience effectively with a limited budget.

And what else needs to be built in your opinion? What can listeners who are interested in building in the Lens ecosystem should be thinking about?

There are several opportunities to explore in the realm of machine learning algorithms and recommendation algorithms, which can bring new experiences to people. Additionally, there is potential for creating apps that are not just direct copies of existing web2 apps. This area is starting to show some promise, but if you have a unique idea for an app, consider building it exactly as you envision it without following the established rules. Niche communities can also be a good target for your app, as they can help you to bootstrap your initial user base, even if it is not a massive number of people.

Building a Data Availability Layer for Social Networks: The Lens Approach

On your point around the machine learning piece, can you chat a little bit about what you envision that future to look like?

I think that AI and machine learning are really powerful tools that can help developers with data analysis and simplification. At Lens, we’re experimenting with building database queries using AI, which can make it easier for non-programmers to construct complex queries. For example, we can take natural language input and use GPT-3 or other models to turn it into an actual database query. Another exciting use case is an app that condenses your feed into a highlight reel based on your preferences and likes, saving you time and allowing you to catch up with your network less frequently. These are just a few examples of how machine learning algorithms can bring new experiences and efficiencies to users.

Let’s chat a little bit about the data availability piece you mentioned. One reason I’m excited about data availability is that I think for a social network to really take off in a decentralized way with the TPS needed, you’ll need something at a data availability layer. Can you talk a little bit about the thought process around building your own at Lens versus using an Eigen layer versus using a Celestia?

I believe that Eigen layer and Celestia are not mature enough and may not be the right fit for our needs. We have already been utilizing Bundlr Network in many areas and have had close communication with their team. We have tested their scalability, which has been proven by us and many others for a while now, and they are continuing to improve and increase their throughput. Given the growth we expect, it’s important for us to have confidence and experience with our chosen platform.

The APIs for Bundlr are also straightforward and easy to use, so it was a logical decision for us to go that route. As we discussed, Bundlr has been around for a few years and has demonstrated resiliency without any issues, which makes it a compelling choice.

About Execution and the Go Token Launch

Can you talk a little bit about that execution on a senior leadership side and how you go about executing at the level you do?

I’ve been working with Aave for about six months now, but most of my focus has been on working with Lens. With Aave, a lot of the work is done through the Aave DAO, which is a decentralized community that makes many decisions. Although the company receives grants and we do certain things, a lot of work is done through the DAO. Because Lens needs a lot of attention, and since DeFi is not my strongest suit, I haven’t spent as much time on Aave as I have on Lens.

When we launch the Go Token on the mainnet in a couple of weeks, I’ll be spending a lot more time on Aave, and I’ll probably split my time 50-50 between the two projects. Right now, I’d say I’ve spent about 80-85% of my time on Lens.

What’s this Go token you speak of? Is that the native token to Lens?

Is a stable coin. A stablecoin that we’re gonna be launching.

What about a token for Lens? When will that happen?

I’m not able to comment on that.

Lens’ Competitive Landscape and User Metrics

Can we talk a little bit about the competitive landscape?

I believe that in the past, people have expected only one winner in the market due to network effects and high valuations. I think that with more diversity in protocols and applications, there will be multiple successful options based on personal preferences. While some may not succeed, many of the ones mentioned will likely do well.

In the current market, success doesn’t necessarily require billions of users like in the past. Even platforms like Twitter, with hundreds of millions of users, aren’t profitable. By re-engineering and rethinking how protocols are built, sustainability can be achieved with only a few million, a hundred million, or tens of millions of users. Thus, smaller, niche social networks can succeed without requiring massive user bases.

Talking numbers, so it’s early days, but can you tell us a little bit about what the metrics on Lens look like for the number of users?

I estimate that the user base for the network is around 105 to 110,000, but a significant portion of those accounts are bots, fake accounts, or people who only signed up for airdrops. Personally, I would cut that number in half, leaving around 55,000 real users on the network.

In terms of other statistics, for March 2023, the network generated around $31,000 in fees paid to creators, with an average of about 19,500 daily active users. As for the number of applications, there are currently a little over 100 medium to high-quality applications being used or developed on the network.

How to Get Started on Lens as a User or Developer

What’s the best way for a user to get their profile up and running within the different apps on Lens?

The biggest challenge right now for people who want to use Lens is the difficulty in accessing the platform. In a few weeks, a new process will be rolled out on the Lens website (lens.xyz) where users can sign up for a waitlist with a straightforward process. This will make it easier for users to join the platform.

Currently, the main ways to access the platform are by attending a conference and getting a PO app or being allow-listed because of having an ETH Denver ticket, or by reaching out to the team as a developer. The two-phase process to make it easier to access Lens involves the new waitlist process and eventually having no waitlist at all. Users are advised to keep an eye out for updates on the Lens website.

What about developers? How can they get involved?

As a developer, you don’t need a Lens profile to start building and deploying on main. You can simply jump straight into our documentation at docs.lens.xyz, where you’ll find all the SDK documentation and APIs. To get inspiration for the types of apps that are available or to experiment with some of them, you can check out lens.xyz/apps, where we have showcased around 100 apps available on Lens.

If you have a great idea as a developer and you are a skilled builder, you may be interested in our grants program. We are still providing grants ranging from $1,000 to $15,000, depending on your idea. You can find more information about the grants program at lens.xyz.

What’s Next

peterpan on Twitter asks what’s next for you?

I’m still here and excited to continue building on Lens. We have some exciting updates coming out soon, and I’m currently experimenting with Chat GPT and GPT plugins, as well as working on the side with Gitcoin Passport. I’m particularly interested in modular ecosystems and have mentioned Celestia before.

Another project that caught my attention is Fuel Network, which has built an integrated stack from the programming language to the developer SDKs to the client SDKs. It’s as if Ethereum started over and built out the entire developer stack.

Gitcoin passport, can you double-click into what that is?

I believe that Gitcoin Passport is a great solution for civil resistance that’s accessible for everyone to use. It doesn’t require scanning into a system like World Coin, which can be restrictive and may turn off a lot of people.

Gitcoin Passport is a privacy-preserving way to verify your unique humanity, and it offers users the option to opt-in to off-chain or on-chain verification methods or both. You can earn points for donating to Gitcoin grants, having an Ethereum address of a certain age, or having an ENS domain, and all these points add up to a score that people can use to determine whether or not you’re a real human.

I think that Gitcoin Passport is especially useful in preventing bots from accessing online forums or communities. For instance, we had a forum for Lens that was botted, and half a million fake accounts signed up within a few hours. With Gitcoin Passport, however, we can eliminate bots by putting up a firewall that removes 99% of them. Although it may not reduce bot access completely, it does a great job of getting through that initial hurdle.

Recently, Gitcoin Passport released a new API that I’ve been exploring because the old API was really bad. Their SDK was also terrible, but the new API is pretty nice, so I recommend checking it out.

How are you defiant?

I believe that staying in the tech space and being excited about the challenges we face together is an act of defiance. However, aside from that, I’m not sure. I do express my opinions on Twitter and social media and I’m not a fan of the oversimplified views that people tend to express there. I think there’s often more nuance to issues than people acknowledge, and I find it toxic when people take extreme stances without considering the gray area. So I do call out those types of people on occasion.

I also love how you are your full self on social media a lot of times you’ll get suggestions that you should niche down and only talk about one specific thing. Can you talk a little bit about how you’ve approached that?

I always follow my curiosity, and I believe there is a lot of fascinating stuff out there to learn about. Sharing what I learn in public is something I enjoy doing. Over the years, I have gained experience in building web technology, mobile applications, and cloud computing, and now I am exploring web3. This diversity of experience allows me to speak to a broad range of topics and also makes it easier for me to learn new things. This is just how I am.