Web3 Leader Spotlight: Mario
This week, we had the pleasure of speaking with Mario, a seasoned Security Researcher who has lent his expertise to over 20 startups, aiding them in product development and scaling beyond the MVP stage.
Mario's expertise also extends to guiding several protocols in building robust smart contract architectures. He emphasises the importance of integrating both Web2 and Web3 components to establish resilient and future-proof architectural foundations. He is the creator of Soldeer, a first solidity-centric package manager built in Rust.
Follow Mario on X @m4rio_eth.
What motivated your transition from building in Web2 to Web3?
My experience in web2 was amazing, but I craved something new, so I delved into AI and Blockchain. I chose Blockchain to tackle the issue of centralization in various societal sectors, aiming for a decentralized, fairer future. This decision underscores my dedication to promoting inclusivity and resilience in our digital landscape.
With your experience helping startups to build and scale their products, what aspects of a product tends to draw the most attention from users during the initial stages of development and scaling?
Users value products that demonstrate an understanding of their needs, emphasizing the significance of prioritizing user satisfaction and conducting interviews during the initial stages of development. Relying solely on assumptions about user preferences significantly increases the risk of failure in product development. Building with the assumption that users will like it is a sure recipe for failure.
From your perspective as a Security Researcher, what shifts do you think are needed to encourage broader adoption of Web3 technology?
I believe there's a pressing need for more discourse on social engineering within the realm of Web3. While security researchers strive to counteract evolving threats, the unpredictable nature of human behavior presents an ongoing challenge that cannot be easily mitigated. It's imperative to recognize and address this human element for a safer space.
What common mistakes have you observed Web2 developers make when transitioning to Web3? Any advice to share to help with the transition?
A common hurdle faced by Web2 developers when transitioning to Web3 is the tendency to treat the blockchain as a conventional database. They sometimes try to store large volumes of data on-chain, which is fundamentally misguided.
Unlike a database, a blockchain isn't designed to efficiently manage extensive data storage. Another challenge arises from the contrasting nature of Web3 compared to Web2. While Web2 applications can scale by adding more machines, often leading to less optimized code initially, Web3 operates differently. Each operation in Web3 incurs a gas cost, directly impacting users in terms of dollar value.
This necessitates a focus on optimized code from the outset, a departure from the more relaxed approach often seen in Web2. It is important to take the time to thoroughly grasp the fundamental differences between Web2 and Web3 architectures. Building a solid understanding will enable you to navigate the unique challenges of Web3 more effectively and make informed design decisions.
