Blockchain Unpacked: Real-World Insights, Pitfalls, and Possibilities

[0:00]Bhakti: Welcome back to the show, everyone! Today, we’re diving deep into blockchain—what it is, how it works, and why it matters far beyond just cryptocurrency. I’m thrilled to have Dr. Lena Oberoi with me. Lena, welcome!

[0:13]Dr. Lena Oberoi: Thanks so much! I’m really excited to get into the nuts and bolts of blockchain with you.

[0:25]Bhakti: You’ve been building distributed systems for a while. Can you tell listeners a bit about your background and what pulled you into blockchain?

[0:40]Dr. Lena Oberoi: Absolutely. I started as a backend engineer working on payment systems, so I was always fascinated by how data moves securely. When I first encountered blockchain through a supply chain pilot, the idea of a decentralized ledger really clicked. I realized it could solve problems that centralized databases just couldn’t.

[1:05]Bhakti: Do you remember your first blockchain project? Was it a success right away?

[1:17]Dr. Lena Oberoi: Oh, not at all! It was a bit of a wild ride. We tried to use blockchain to track shipments internationally, but ran into serious challenges with data entry and consensus. But even the failures taught us a lot about what blockchain is—and isn’t—good for.

[2:15]Bhakti: That’s a perfect segue. Let’s get everyone on the same page. In the simplest terms, what is blockchain?

[2:30]Dr. Lena Oberoi: Think of blockchain as a special type of database. Instead of one central server, copies are held by many participants. Data is grouped into blocks, each one chained to the last using cryptography. This makes it tamper-evident—if you change one block, everyone will know.

[2:55]Bhakti: So, it’s not just a bunch of servers? What’s the big deal about the ‘chain’ part?

[3:07]Dr. Lena Oberoi: Great question. The ‘chain’ means each set of transactions is linked together. If you try to change a record in the past, it would break the links and everyone would notice. That’s what gives blockchain its reputation for security and transparency.

[3:30]Bhakti: Let’s pause there and define ‘tamper-evident’. Does that mean it’s impossible to change data?

[3:45]Dr. Lena Oberoi: Not impossible, but extremely difficult. Tamper-evident means any attempt to alter data is obvious. In most public blockchains, you’d need to control a majority of the network to rewrite history. That’s expensive and impractical.

[4:40]Bhakti: How is that different from a regular database? Why not just use, say, a SQL server?

[4:55]Dr. Lena Oberoi: Traditional databases are controlled by one party. If you have admin access, you can change records and no one else might know. In blockchain, control is distributed, so trust is shared—not just placed in a single administrator.

[5:25]Bhakti: So, is blockchain always better than a regular database for transparency?

[5:40]Dr. Lena Oberoi: Not always. If you trust the central party and don’t need public verification, a database is simpler and faster. Blockchain shines when you have multiple organizations that don’t fully trust each other but need a shared source of truth.

[6:10]Bhakti: I like that distinction. Let’s talk about how blockchains actually keep everyone honest. What’s a consensus mechanism?

[6:25]Dr. Lena Oberoi: Consensus mechanisms are the rules for how everyone agrees on the state of the data. Think of it as a voting system. The two most common types are proof of work—where computers solve puzzles to add new blocks—and proof of stake, where participants put up value to validate transactions.

[7:00]Bhakti: Which one is better? Proof of work or proof of stake?

[7:15]Dr. Lena Oberoi: It depends! Proof of work is energy-intensive but very battle-tested. Proof of stake is more energy-efficient and faster, but it’s newer and has its own risks, like the ‘nothing at stake’ problem. The right choice depends on your priorities.

[7:45]Bhakti: Can you give an example of a consensus failure or issue you’ve seen?

[8:00]Dr. Lena Oberoi: Sure. In one enterprise project, we used a proof-of-authority model where only selected nodes could validate. It worked well until two nodes went offline for maintenance—suddenly, the chain stalled. We learned the hard way about redundancy and uptime.

[9:00]Bhakti: That’s a real-world lesson. I want to dig into decentralization. Why is it so important in blockchain?

[9:15]Dr. Lena Oberoi: Decentralization removes single points of failure and control. It lets you build systems where no one entity can rewrite history or censor transactions. But it also makes coordination and upgrades much harder, so it’s a trade-off.

[9:45]Bhakti: Do you think most projects actually achieve meaningful decentralization?

[10:00]Dr. Lena Oberoi: Honestly, many private or ‘permissioned’ blockchains are only partly decentralized. Sometimes, decentralization is more of a marketing term than a technical reality. You have to look at who runs the nodes and how decisions are made.

[10:25]Bhakti: Let’s define ‘node’ quickly for the audience.

[10:35]Dr. Lena Oberoi: A node is just a computer that keeps a copy of the blockchain and helps validate and share data. The more independent nodes, the stronger the network usually is.

[11:10]Bhakti: Thanks for clearing that up. I want to move to smart contracts. People hear this term a lot. What are they, really?

[11:25]Dr. Lena Oberoi: A smart contract is a program that runs on the blockchain. It can automatically enforce rules—like transferring a digital asset if certain conditions are met—without needing a lawyer or middleman. But, like any code, it’s only as smart as its programmer.

[11:55]Bhakti: Can you walk us through a simple example of a smart contract in action?

[12:10]Dr. Lena Oberoi: Sure. Imagine buying concert tickets. You send money to a smart contract. If the ticket is available, the contract transfers the ticket to you. If not, it refunds you. No one can change the terms after the fact.

[12:35]Bhakti: Are smart contracts always the right solution? Or do they add complexity?

[12:50]Dr. Lena Oberoi: They add complexity, for sure. They’re great when you need automation and transparency among untrusted parties. But for simple logic, especially within one company, traditional scripts can be easier to audit and change.

[13:25]Bhakti: Let’s dig into a practical example. You mentioned supply chain earlier. Can you share a case study there?

[13:45]Dr. Lena Oberoi: Absolutely. We worked with a food importer to track shipments. Every step—from farm to warehouse to retailer—was logged on a blockchain. This let everyone verify the origin, reducing fraud and streamlining recalls. But we hit snags: data entry was often manual, and mistakes on-chain were permanent.

[14:25]Bhakti: That permanence sounds risky. What happens if someone enters the wrong data?

[14:40]Dr. Lena Oberoi: That’s a big issue. If bad data goes on the blockchain, it’s there forever. You can append corrections, but you can’t erase the mistake. That’s why data quality controls and incentives for honest input are so important.

[15:05]Bhakti: That’s a trade-off I hadn’t considered. How did the project handle scaling as shipments increased?

[15:20]Dr. Lena Oberoi: We quickly hit transaction limits. Public blockchains can only handle so many updates per second. To scale, we moved some data off-chain, storing only essential proofs on the blockchain. It was a balancing act between transparency and performance.

[15:55]Bhakti: Let’s pause and recap: Blockchain gives transparency and tamper-evidence, but scaling and data quality are real challenges. Is that fair?

[16:10]Dr. Lena Oberoi: Exactly. It’s not a silver bullet. You have to design systems that play to blockchain’s strengths and mitigate its weaknesses.

[16:30]Bhakti: What about digital identity? That’s another area people talk about. Can blockchain help there?

[16:45]Dr. Lena Oberoi: Definitely. With digital identity, individuals can control their credentials on a blockchain, sharing only what’s needed. One pilot we did let users prove their age to buy restricted goods—without revealing their full identity. But adoption was tricky; businesses and regulators had lots of questions.

[17:20]Bhakti: Can you share more about the challenges in that digital identity project?

[17:35]Dr. Lena Oberoi: Sure. We faced skepticism from businesses worried about compliance and from users nervous about privacy. Also, if a user lost their private key—the digital ‘password’—they lost access. Recovery mechanisms are a big open problem.

[18:10]Bhakti: Let’s talk about when blockchain is actually the wrong tool. Have you seen that happen?

[18:25]Dr. Lena Oberoi: Many times! Sometimes teams add blockchain because it sounds innovative, but really just need a database. For example, one logistics company built a blockchain pilot only to realize their partners didn’t want the overhead of running nodes. They scrapped it and went back to a shared API.

[19:00]Bhakti: What are some warning signs a project doesn’t need blockchain?

[19:15]Dr. Lena Oberoi: If all parties trust each other, or if performance and cost are top priorities, blockchain may not add value. Also, if your main goal is just to store or move data quickly, traditional tech is usually better.

[19:45]Bhakti: That’s helpful. Let’s talk about scalability. Blockchains are often said to be slow or expensive. Why is that?

[20:00]Dr. Lena Oberoi: Every transaction needs to be validated by many nodes, which takes time and resources. On public blockchains, transaction fees can spike during busy periods. Private chains are faster, but you trade off some of the openness and security.

[20:30]Bhakti: So, if I want instant and cheap transactions, blockchain isn’t ideal?

[20:45]Dr. Lena Oberoi: Correct. For high-speed, high-volume needs, blockchains struggle. There are scaling solutions like rollups and sidechains, but they add complexity and sometimes reduce decentralization.

[21:10]Bhakti: Let’s pause and define ‘rollup’ for listeners.

[21:20]Dr. Lena Oberoi: A rollup batches many transactions together and posts a summary to the blockchain. This reduces congestion but adds another layer of trust and engineering.

[21:45]Bhakti: So, every solution comes with a trade-off. That leads us to security. Blockchains are said to be secure by design. Is that always true?

[22:00]Dr. Lena Oberoi: They’re secure against certain types of tampering, but they’re not immune to bugs, poor key management, or social engineering. Smart contract bugs have led to major losses in recent years.

[22:25]Bhakti: Can you give an example of a smart contract failure?

[22:40]Dr. Lena Oberoi: Certainly. We saw a project where a missing validation in the code let attackers drain funds. Even though the blockchain itself was secure, the contract logic wasn’t. Auditing and thorough testing are essential.

[23:10]Bhakti: Is there ever a case where blockchain’s transparency is a problem?

[23:25]Dr. Lena Oberoi: Yes. For competitive industries, sharing too much data on a public blockchain can expose business secrets. That’s why many use private or permissioned chains, or keep sensitive data off-chain.

[24:00]Bhakti: Let’s do a quick recap: Blockchain brings transparency and tamper-evidence, but it’s not a fit for every problem. Scalability and privacy are real challenges. Anything else to add before we take a break?

[24:20]Dr. Lena Oberoi: Just that choosing blockchain is about understanding your requirements and constraints—not just following trends. We’ll dig into more pitfalls and trade-offs after the break.

[24:45]Bhakti: Perfect. Before we pause, one quick question: Is decentralization always worth the cost?

[25:00]Dr. Lena Oberoi: Not always. Sometimes, the cost and complexity outweigh the benefits—especially if your use case doesn’t require trustless collaboration. It’s important to be honest about that from the start.

[25:20]Bhakti: You mentioned earlier that marketing sometimes oversells decentralization. Can you share a time when that backfired?

[25:35]Dr. Lena Oberoi: Sure. One startup promoted their chain as ‘fully decentralized’ to attract funding, but in reality, only three companies controlled the nodes. When disagreements arose, it was clear the governance wasn’t as distributed as they claimed. Users lost trust quickly.

[26:10]Bhakti: That’s a reality check. Let’s wrap up this first half with a quick summary: Blockchain offers new ways to share data and enforce rules, but comes with trade-offs in performance, complexity, and governance. When we come back, we’ll dig into security, production failures, and where the industry is heading. Lena, ready for round two?

[26:35]Dr. Lena Oberoi: Absolutely. I’m looking forward to it!

[26:50]Bhakti: Alright, listeners, stay with us. We’ll be back in just a moment.

[27:10]Bhakti: And we’re back! Before we jump into security, Lena, any final thoughts on trade-offs you want to leave listeners with?

[27:20]Dr. Lena Oberoi: Just that every technology choice is about context. There’s no one-size-fits-all answer—and that’s especially true with blockchain.

[27:30]Bhakti: Alright, so we’ve talked through the basics and some of the core concepts of blockchain. Let’s pivot a bit. I want to dig deeper into how organizations are actually using blockchain in the real world. What are some compelling examples you’ve seen recently?

[27:55]Dr. Lena Oberoi: Absolutely. One area where blockchain is making waves is in supply chain management. I worked with a food distributor, and they wanted to improve traceability—from farm to table, every step logged transparently. They implemented a private blockchain, so every shipment, quality check, and transfer got recorded immutably. It meant that if there was a recall, they could pinpoint exactly where in the chain things went wrong.

[28:20]Bhakti: That’s fascinating. So, did they face any hurdles rolling that out?

[28:38]Dr. Lena Oberoi: Definitely. One major challenge was onboarding partners. Not every supplier was comfortable with the technology or keen on the transparency. There were a lot of workshops and even some resistance. But once they saw how it could reduce paperwork and speed up payments, adoption grew.

[29:00]Bhakti: That makes sense. I’ve heard of similar adoption stories in logistics. What about outside supply chains? Any other industry examples stand out to you?

[29:20]Dr. Lena Oberoi: Healthcare is another big one. I can’t name names due to confidentiality, but there’s a hospital network using blockchain to manage patient consent for data sharing. Patients control who accesses their records, and every consent or revocation is logged so there’s a clear audit trail.

[29:42]Bhakti: That brings up privacy. Blockchain is transparent, but healthcare data needs to stay confidential. How do they balance that?

[30:02]Dr. Lena Oberoi: Great question. They don’t store raw medical data on the blockchain. Instead, they store hashes—essentially fingerprints of the data. The actual records stay in encrypted databases. The blockchain just tracks permissions and accesses, so there’s a verifiable, tamper-proof log but no private info exposed.

[30:25]Bhakti: So, you get the auditability without the risk of leaks. Smart. Let’s zoom out a bit. What are some misconceptions people still have about blockchain, especially in enterprise contexts?

[30:48]Dr. Lena Oberoi: One big misconception is that blockchain is always public or that it’s all about cryptocurrency. In reality, most enterprise blockchains are private or permissioned. Another is that blockchains are magically secure or efficient—when in fact, they require careful design, especially around consensus and data storage.

[31:10]Bhakti: And speaking of consensus, can you break down the trade-offs between a few popular consensus mechanisms?

[31:32]Dr. Lena Oberoi: Sure. Proof of Work is robust but energy-intensive. Proof of Stake is more efficient, but relies on participants having a stake in the network—so there’s a different risk profile. For private blockchains, you often see Practical Byzantine Fault Tolerance or even simple voting mechanisms, which can be faster but require trust among participants.

[31:55]Bhakti: Have you seen projects choose the wrong consensus algorithm?

[32:10]Dr. Lena Oberoi: Yes, and it’s usually due to copying public blockchain models. For instance, a consortium of banks once used Proof of Work, thinking it was the gold standard, but it led to unnecessary complexity and cost. They eventually switched to a lighter-weight, permissioned consensus, and things improved dramatically.

[32:35]Bhakti: That leads to my next question: what are some common failure points when teams go from pilot to production with blockchain?

[32:54]Dr. Lena Oberoi: Scaling is a big one. It’s easy to get something working with a handful of nodes, but as you add more participants, latency and coordination issues pop up. Another is governance—who gets to update the rules? If you don’t define this early, disputes are inevitable.

[33:18]Bhakti: Can you share a quick story of a project that ran into those challenges?

[33:35]Dr. Lena Oberoi: Sure. A logistics network set up a blockchain pilot for invoice reconciliation. It worked great with three companies, but once they added two more, transaction times spiked. Turned out, their consensus algorithm couldn’t handle the extra load. They had to redesign that layer and add better node monitoring.

[33:58]Bhakti: So, planning for scale is crucial. What about smart contracts? Are there best practices or cautionary tales you can share?

[34:20]Dr. Lena Oberoi: Absolutely. Smart contracts are powerful, but they’re code—so bugs can be costly. I’ve seen teams launch contracts without thorough audits, only to find out later there was a loophole. Best practice: always do a security review, use established libraries, and keep contracts as simple as possible.

[34:45]Bhakti: Let’s do a mini case study. Can you walk us through a smart contract project that worked well, and why?

[35:05]Dr. Lena Oberoi: Sure. An energy trading platform set up a smart contract system where producers could automatically sell excess solar power to neighbors. They succeeded because they started small, used open-source templates, ran thorough audits, and involved users in testing. When an edge case popped up, they had a rollback plan ready.

[35:30]Bhakti: I love that they brought users into the process. It’s easy to forget that blockchain is still about people and trust. On that note—what are the human or organizational blockers to blockchain adoption?

[35:51]Dr. Lena Oberoi: Cultural resistance is a big one. Folks worry about transparency, losing control, or just the learning curve. Also, there’s often a lack of executive buy-in or a clear business case, so projects stall after the pilot phase.

[36:12]Bhakti: So, leadership matters. What about regulation? Do you see that as a blocker or an enabler?

[36:30]Dr. Lena Oberoi: It can be both. In some sectors, clear guidelines have actually accelerated adoption by reducing uncertainty. But in other cases, unclear or conflicting regulations have made organizations hesitant to take the plunge.

[36:50]Bhakti: Let’s shift gears. I want to do a rapid-fire round. I’ll throw out a word or phrase, and you give me your quick take. Ready?

[36:55]Dr. Lena Oberoi: Let’s go for it!

[37:00]Bhakti: First one: NFTs.

[37:03]Dr. Lena Oberoi: Interesting but overhyped. Real value in digital ownership, but lots of noise.

[37:07]Bhakti: Tokenization.

[37:10]Dr. Lena Oberoi: Powerful for real-world assets—think real estate or art—if you solve the legal complexities.

[37:14]Bhakti: Interoperability.

[37:16]Dr. Lena Oberoi: Critical and still a work in progress. Most blockchains can’t talk to each other easily yet.

[37:20]Bhakti: Zero-knowledge proofs.

[37:23]Dr. Lena Oberoi: Exciting tech for privacy. Still maturing but lots of promise in finance and identity.

[37:27]Bhakti: Immutable ledgers.

[37:29]Dr. Lena Oberoi: Blessing and curse—great for audit trails, tricky if you need to correct mistakes.

[37:33]Bhakti: Public vs. private chains.

[37:36]Dr. Lena Oberoi: Public chains: open and decentralized; private: faster, more control, but less trustless.

[37:40]Bhakti: Last one: Blockchain scalability.

[37:43]Dr. Lena Oberoi: Still the biggest challenge. Layer 2 solutions and sharding help, but not a silver bullet.

[37:48]Bhakti: Love those answers. Let’s go deeper on interoperability for a second. Are there any promising approaches you’ve seen to connect different blockchains?

[38:08]Dr. Lena Oberoi: There are some interesting cross-chain protocols and bridges. For example, atomic swaps let you trade assets across chains without relying on a central party. But these solutions are still evolving, and security is a big concern—bridges have been targeted by attackers.

[38:30]Bhakti: So, in production, would you recommend waiting or experimenting carefully?

[38:38]Dr. Lena Oberoi: Experiment, but with strong safeguards. Use testnets, limit what’s at risk, and monitor everything closely.

[38:50]Bhakti: Good advice. Let’s circle back to mistakes. What’s a classic mistake teams make when designing blockchain systems?

[39:05]Dr. Lena Oberoi: Trying to put everything on the blockchain. It’s tempting to log every detail, but blockchains have storage limits and performance costs. The best designs only store what’s necessary for audit or coordination, and keep heavy data off-chain.

[39:25]Bhakti: That’s a key point. Are there tools or frameworks you recommend for smart contract development?

[39:41]Dr. Lena Oberoi: Definitely. For Ethereum-based contracts, tools like Truffle and Hardhat are great for testing and deployment. OpenZeppelin has reusable, audited contract libraries. And don’t forget static analysis tools for finding bugs early.

[40:00]Bhakti: Let’s talk about monitoring. Once a blockchain app is live, how do teams keep tabs on it?

[40:15]Dr. Lena Oberoi: It’s similar to any distributed system—you need logging, transaction monitoring, and alerting. There are specialized blockchain explorers, but in private chains, you’ll want custom dashboards for performance and error tracking.

[40:35]Bhakti: Are there any unique production issues you’ve seen crop up?

[40:53]Dr. Lena Oberoi: One issue is node desynchronization. If a node falls behind, it can cause transaction delays or even forks. Regular backups and health checks are critical. Also, smart contract upgrades can be tricky—once deployed, code can’t easily change.

[41:15]Bhakti: That’s a good point. What’s your preferred approach for upgrading smart contracts?

[41:30]Dr. Lena Oberoi: Proxy patterns are popular—you deploy a new contract, but keep the same address by routing calls through a proxy. But this adds complexity and potential security risks, so it needs careful review.

[41:50]Bhakti: Let’s bring in our second mini case study. Can you describe a project where blockchain actually failed to deliver, and why?

[42:10]Dr. Lena Oberoi: Sure. A government agency tried to use blockchain to manage digital identities. The tech worked, but the project stalled because stakeholders couldn’t agree on governance. Who would control access? Who could update records? The lesson: technology can’t fix unclear roles or lack of trust.

[42:30]Bhakti: That’s such an important takeaway. Sometimes the blocker isn’t the tech at all.

[42:36]Dr. Lena Oberoi: Exactly. The hardest problems are often organizational, not technical.

[42:45]Bhakti: Let’s switch to future trends. What are you most excited about in blockchain right now?

[42:58]Dr. Lena Oberoi: I’m excited by privacy-preserving blockchains and decentralized identity. Also, new governance models—DAOs, for instance—are experimenting with collective ownership and decision-making.

[43:13]Bhakti: For listeners considering their first blockchain project, what’s your number one piece of advice?

[43:23]Dr. Lena Oberoi: Start small and solve a real problem. Don’t use blockchain for the sake of it. If you can’t explain the business benefit in a sentence, rethink the project.

[43:38]Bhakti: Great advice. As we head into our final segment, I’d like to walk through an implementation checklist. Can we break it down together, step by step?

[43:43]Dr. Lena Oberoi: Of course. Let’s do it.

[43:48]Bhakti: Alright, step one—define the business problem. What should teams focus on here?

[43:54]Dr. Lena Oberoi: Be crystal clear about what you’re solving, and why blockchain is uniquely suited to it—like trust, transparency, or automation.

[44:00]Bhakti: Step two—choose your blockchain type.

[44:05]Dr. Lena Oberoi: Pick between public, private, or consortium chains based on your trust and performance needs.

[44:10]Bhakti: Step three—plan your governance.

[44:15]Dr. Lena Oberoi: Decide who validates transactions, who can join, and how rules get updated. Governance makes or breaks projects.

[44:21]Bhakti: Step four—design your data model.

[44:26]Dr. Lena Oberoi: Only put what’s essential on-chain. Keep sensitive or bulky data off-chain, and use hashes for references.

[44:32]Bhakti: Step five—develop and audit smart contracts.

[44:38]Dr. Lena Oberoi: Write clean, tested code. Use established libraries and get independent security audits. Test on a testnet before going live.

[44:45]Bhakti: Step six—plan for scaling and monitoring.

[44:50]Dr. Lena Oberoi: Monitor node health and transaction throughput. Plan for growth—both in users and in transaction volume.

[44:56]Bhakti: Step seven—prepare your rollout and user onboarding.

[45:01]Dr. Lena Oberoi: Train your users. Offer clear documentation. Have a support plan ready for launch day.

[45:07]Bhakti: And finally—have an upgrade and recovery plan.

[45:12]Dr. Lena Oberoi: Exactly. Plan for bugs or exploits. Decide how you’ll handle smart contract upgrades and what you’ll do if something goes wrong.

[45:20]Bhakti: That’s a fantastic checklist. I want to take a couple of listener questions before we wrap up. Here’s one: How do you convince skeptical executives to invest in a blockchain project?

[45:30]Dr. Lena Oberoi: Focus on ROI and risk reduction. Show concrete examples—like faster settlements or reduced disputes. Execs care about outcomes, not tech jargon.

[45:40]Bhakti: Another question: What skills should a team have to succeed with blockchain?

[45:50]Dr. Lena Oberoi: You need strong software engineers, ideally with distributed systems experience. But also legal, compliance, and business experts. And don’t underestimate the value of a good change manager.

[46:02]Bhakti: That’s a well-rounded team. Let’s do one more: If someone wants to learn more or get started, where should they begin?

[46:14]Dr. Lena Oberoi: Start with open tutorials and sandboxes—many blockchains have great dev portals. Join community forums, read whitepapers, and try building a simple dApp. Learning by doing is key.

[46:25]Bhakti: Thanks for those tips. As we approach the end, any parting thoughts on the future of blockchain or how teams can stay ahead?

[46:38]Dr. Lena Oberoi: Stay curious and open-minded. Blockchain is evolving fast, and today’s best practices may change. Keep an eye on new governance models, privacy tech, and real-world adoption stories. And always question if blockchain is the right tool for the job.

[46:55]Bhakti: That’s such a good note to end on. Before we wrap, let’s recap today’s top takeaways for our listeners. I’ll start: Number one—blockchain isn’t just for crypto. It’s powering real-world solutions in supply chain, healthcare, and beyond.

[47:08]Dr. Lena Oberoi: Number two—smart governance and scaling plans are critical for production success.

[47:15]Bhakti: Number three—don’t store everything on-chain. Use the blockchain for what it’s best at: transparency, auditability, and automation.

[47:22]Dr. Lena Oberoi: Number four—never skip security audits for smart contracts. Prevention is cheaper than fixing.

[47:28]Bhakti: Number five—focus on people and process, not just technology.

[47:33]Dr. Lena Oberoi: And finally—keep learning, because the landscape is still changing.

[47:41]Bhakti: Perfect. We’re almost out of time, but I want to thank you for such a practical and deep conversation. Before we say goodbye, any resources or places where listeners can connect with you or learn more?

[47:52]Dr. Lena Oberoi: I’m active on professional networks, and I occasionally share case studies and guides on my blog. Happy to connect and answer questions—just mention this podcast!

[48:00]Bhakti: Fantastic. Well, thank you again for joining us and sharing your insights.

[48:06]Dr. Lena Oberoi: Thank you for having me. This was a great discussion.

[48:13]Bhakti: To our listeners: We hope you found today’s episode on blockchain valuable. If you enjoyed it, please subscribe to Softaims and leave us a review. It really helps others discover the show.

[48:22]Dr. Lena Oberoi: And if you have questions or topics you want us to cover next, send them in! We love hearing from you.

[48:30]Bhakti: One last checklist before we go. If you’re considering blockchain for your team, remember: clarify your business case, pick the right type of chain, plan your governance, design your data model wisely, audit your code, monitor your production, onboard your users, and always have a backup plan.

[48:48]Dr. Lena Oberoi: Couldn’t have said it better myself.

[48:54]Bhakti: That’s it for today’s episode of Softaims. Thanks for listening, and we’ll catch you next time.

[48:59]Dr. Lena Oberoi: Take care, everyone!

[49:05]Bhakti: And with that, we’re signing off. Stay curious, keep building, and see you soon.

[49:12]Bhakti: This was Softaims, your go-to for real-world tech conversations. Goodbye!

[49:16]Dr. Lena Oberoi: Goodbye!

[49:20]Bhakti: And that wraps up our episode. Thanks again for tuning in—until next time!

[55:00]Bhakti: Softaims out.