“Think your smart contract is safe? Double-check.”
In this edition of Coffee with Calyptus, we feature Manoj Patra, a Smart Contract Engineer at Kelp DAO, who has developed smart contracts managing over $2 billion in TVL. Manoj shares crucial insights on blockchain security, the importance of simplicity, and the challenges of DeFi development.
You've developed smart contracts, managing over $2 billion in TVL. What are the biggest lessons you’ve learned about security and reliability when working at this scale?
Security in blockchain development is paramount, and managing such high stakes has taught me invaluable lessons. I can summarize them in the below 5 points.
- Keep your code simple.
- Don't move ahead if you don't understand something.
- Double check even if it seems very obvious.
- Think as an auditor or blackhat when writing tests.
- Don't just try to increase code coverage. Rather try to break your own system and learn different tools to help you break it.
These principles have been instrumental in ensuring both security and reliability at scale.
What sparked your interest in blockchain and DeFi, and how has your perspective on the industry evolved as you’ve gained experience?
My journey into blockchain began when I started investing in cryptocurrencies after experimenting with various traditional finance tools. What struck me was the revolutionary potential of the technology, far beyond just its use as an investment vehicle. While casually watching short videos about the top 40-50 coins, I realized that blockchain is not just a fleeting trend—it’s a foundational innovation poised to reshape industries. This realization fueled my desire to be part of this transformation. Over time, I’ve come to appreciate the industry’s openness and low entry barriers, but I’ve also learned that true expertise in blockchain and DeFi requires dedication, consistent learning, and a willingness to tackle complex problems.
You have a strong background in data structures and algorithms. Has this foundation helped you in smart contract development and optimizing for gas efficiency?
During my undergraduate years, I was passionate about competitive programming, which sharpened my skills in data structures and algorithms. This training didn’t just improve my problem-solving abilities; it taught me to think critically and analyze problems deeply. When I transitioned to smart contract development, this foundation proved incredibly useful. It helped me quickly grasp the nuances of smart contract design, optimize for gas efficiency, and create more reliable solutions.
Working across smart contracts and backend systems, what do you see as the key differences and challenges between traditional backend engineering and blockchain development?
While traditional backend engineering involves a larger volume of code, the precision required in smart contract development makes the latter more demanding in certain ways. In blockchain development, the margin for error is virtually non-existent—one bug can compromise the entire protocol. Additionally, modifying or updating smart contracts is far more complex and less frequent than in traditional backend systems. These constraints require an exhaustive level of attention to detail and extensive testing, even for seemingly simple code. In contrast, backend systems often allow for quicker iterations and easier debugging. This makes blockchain development a unique challenge, emphasizing pre-deployment diligence over post-deployment fixes.
Having worked in both corporate and DAO settings, what’s one key insight you’ve gained about collaboration and adaptability in these different work environments?
Initially, I found the transition from a structured corporate environment to the dynamic and decentralized nature of DAOs challenging, often feeling burned out due to the lack of immediate support from colleagues working in different time zones and the absence of a fixed 9-to-5 schedule. Over time, I learned to embrace async work as I realized the importance of efficiency in communication and adaptability. I also realized the importance of flexibility—being truly available when needed, rather than forcing a rigid schedule. Small practices, like using smartphones for instant updates, also made a big difference. Ultimately, working in a DAO has been enriching, offering opportunities to connect with talented people from diverse cultural and professional backgrounds.
For those aiming to break into blockchain development or DeFi, what essential skills or knowledge areas should they focus on to build a strong foundation?
Breaking into blockchain development requires both foundational knowledge and proactive engagement. Start by watching videos from platforms like WhiteboardCrypto to understand DeFi from a user’s perspective. For smart contract development, Patrick Collins’ courses are a great resource. Simultaneously, build your personal brand by sharing your learning journey on platforms like Twitter. Don't wait to become an expert before contributing—start small, whether through internships, open-source contributions, or cold outreach via emails or DMs to potential mentors. Attending blockchain events is another excellent way to network and pitch yourself. If you're interested in blockchain security, try participating in public audits to gain hands-on experience. In the first 6-12 months, focus on learning rather than financial rewards. This space is filled with some of the brightest minds, and investing in knowledge will pay off immensely in the long run.
Solidity Challenge 🕵️♂️
What can go wrong in the following smart contract?
Jobs 💼
We have over 200 roles on our platform from companies like Aave, Aragon, Balancer, Gnosis, etc. Check out a select few below:
Head of Marketing - remote, NA/Europe, fulltime - $140-200k
Backend Web3 Developer - remote, Europe, fulltime - $70-90k
Senior Backend Engineer - remote, US, fulltime - $200-300k
Mobile Engineer (React Native or Flutter) - remote, global (3 month onsite to begin with), fulltime - $200-300k
Solidity Challenge Answer ✅
Answer:
- Unchecked return value for send so it can silently fail.
- Does not follow check effect interaction pattern.
