Chapter 2: A Borrowing Position – The Composable Crisis

The DeFi District was never truly empty. Even at 3:00 PM on a Tuesday, the virtual space buzzed with activity. Avatars drifted between protocol buildings, their movements smooth and purposeful. Chat bubbles popped up and faded away, carrying fragments of conversation—questions about yields, warnings about gas fees, excited announcements about new strategies.

Ravi’s avatar appeared at the entrance to Protocol A’s skyscraper, briefcase in hand, hoodie pulled up. He glanced at the time display in the corner of his vision: 2:58 PM. Two minutes early. He hated being early—it made him feel eager, desperate even. But he was also excited to show off his strategy.

Talia’s avatar materialized a moment later. Unlike Ravi’s casual hoodie, she wore a sleek analyst’s outfit—dark jacket, data pad in hand, a pair of smart glasses that reflected streams of information. Her posture was straight, professional, and slightly intimidating.

“You’re early,” Ravi said, trying to sound casual.

“I’m always early,” Talia replied. “It’s called being prepared.”

Ravi rolled his eyes—or at least, his avatar did. “Let’s not start with the lectures. You wanted to review my strategy, right?”

“I wanted to audit it,” Talia corrected. “There’s a difference. Review is just looking. Audit is finding problems.”

“Always so optimistic.”

“Realistic,” she said. “There’s a difference.”


They walked into Protocol A’s virtual lobby, and the environment shifted around them. The skyscraper’s interior was sleek and minimalist: polished floors, holographic displays showing current interest rates and collateral ratios, and a central information desk staffed by a helpful AI avatar.

Ravi led Talia to a private meeting room—a small, glass-walled space that overlooked the virtual city. They sat across from each other at a holographic table, and Ravi projected his dashboard onto the surface between them.

“Alright,” he said, unable to keep the pride from his voice. “Here it is. My composable strategy.”

The hologram displayed his positions in a series of interconnected boxes: Protocol A on the left, Protocol B on the right, with arrows showing the flow of assets. The numbers updated in real time, displaying current balances, borrowings, and earnings.

Talia leaned forward, her avatar’s expression focused. She expanded the Protocol A box, studying the collateral details. Then she expanded Protocol B, examining the yield farm’s parameters.

“Seventeen days active,” she murmured. “Ten thousand units deposited in Protocol A. Seven thousand five hundred borrowed. Deposited in Protocol B’s main farm. Effective APY… twenty percent.”

She looked up at Ravi. “That’s your base position?”

“Base position, yes,” Ravi said. “But I’m adding a new layer today. A leverage loop. That’s what I wanted you to see.”

“Show me.”

Ravi tapped the table, and the hologram shifted. New boxes appeared, new arrows connecting them. The diagram became more complex, a web of dependencies that would have been confusing to anyone who didn’t understand the protocols.

“This is the loop,” he explained, his enthusiasm building. “I deposit in Protocol A, borrow, deposit in Protocol B, earn rewards. Then I take my Protocol B position—which has grown—and use it as additional collateral in Protocol A. That lets me borrow more from Protocol A, which I deposit in Protocol B, which grows again, which lets me borrow more from Protocol A…”

He paused, catching his breath. “Each loop increases my effective leverage. After three loops, my exposure is three times my original capital. The APY goes from twenty percent to almost forty-five.”

Talia was silent for a long moment. Her avatar’s face was unreadable.

“Well?” Ravi prompted. “Impressive, right?”

“Ravi,” she said slowly, “may I run a simulation against your position?”

“Of course. That’s what you’re here for.”


Talia’s fingers moved across the holographic table, pulling up her own tools. She had a suite of risk assessment programs that she’d built herself—comprehensive simulations that stress-tested positions against dozens of scenarios.

The table flickered as her software interfaced with Ravi’s position data. A new window opened, displaying a series of charts and metrics.

“Your current position has a liquidation threshold of sixty-eight percent,” she said. “That means if the value of your collateral drops by more than thirty-two percent, Protocol A will start liquidating your assets.”

“Thirty-two percent is a lot,” Ravi said. “The asset is stable. It doesn’t move that much.”

“Stable until it’s not,” Talia replied. “That’s the first red flag.”

She tapped the table again, and a new graph appeared. It showed Ravi’s position under a hypothetical 10% drop in collateral value.

“Let’s say the asset drops ten percent,” she said. “Not a crash, just a normal market fluctuation. Protocol A recalculates your collateral-to-loan ratio. Your position is now closer to the liquidation threshold.”

The graph updated. Ravi’s effective leverage ratio had worsened.

“You’re still safe,” Talia continued. “But now you have less buffer. If the drop continues—fifteen percent, eighteen percent—you get a margin call. Protocol A starts selling your collateral at a discount to cover the loan.”

“Selling at a discount?” Ravi asked.

“Protocol A has to sell quickly to minimize bad debt. They’ll accept bids slightly below market price. That means your assets sell for less than they’re worth, which accelerates your loss.”

Ravi frowned. “Okay, but that’s a worst-case scenario. The asset has never dropped that much in a single day.”

“Worst-case scenarios are the only ones that matter,” Talia said. “But let’s keep going.”


She expanded the simulation, adding Protocol B to the equation.

“Now let’s look at your yield,” she said. “Protocol B’s APY is fifteen percent. That’s attractive, but it’s also volatile. It depends on user activity, token emissions, and market conditions. If Protocol B’s rewards drop—say, to ten percent, or eight—your effective APY plummets.”

Ravi shrugged. “I could just switch to another farm.”

“Could you? Let’s assume your Protocol B position has grown significantly. You’ve reinvested rewards, added leverage, built a substantial position. Now you’re locked into that farm because your entire strategy depends on it.”

A new graph appeared, showing Ravi’s earnings under declining reward rates.

“If Protocol B’s APY drops by just three percentage points,” Talia said, “your effective APY goes from forty-five to thirty-six. Still good. But the risk has increased because now your Protocol A position is using Protocol B as collateral. If Protocol B’s rewards drop, the value of your collateral in Protocol A drops. That’s a feedback loop.”

“I see where this is going,” Ravi said, his voice edged with impatience. “You’re going to say the risks multiply.”

“Yes,” Talia said simply. “The risks multiply. That’s the problem with composability. Each protocol has its own risks, and when you combine them, they don’t just add—they amplify. A one percent risk in Protocol A and a one percent risk in Protocol B doesn’t make a two percent risk. It makes something much larger.”

She pulled up a new visualization: a chain of dominoes, each one connected to the next.

“This is your strategy,” she said. “Every position is connected. A hiccup in Protocol A triggers a reaction in Protocol B. Protocol B’s reaction triggers a reaction in Protocol A. The whole thing becomes a house of cards.”

Ravi stared at the dominoes, his expression shifting from confidence to unease.

“That’s a worst-case scenario,” he said again.

“It’s the one I’m paid to analyze,” Talia replied. “And it’s the one that destroyed my sibling’s portfolio.”


The silence that followed was heavy.

Ravi knew the story—everyone in the community knew the story. Two years ago, Talia’s older sibling had built a composable strategy similar to Ravi’s. She’d been one of the first to use multiple protocols together, and she’d been celebrated as a pioneer. Her portfolio had grown to impressive size, and she’d been featured in community interviews and newsletters.

Then a protocol she’d used had suffered an oracle failure. A temporary glitch had mispriced the collateral, triggering a cascade of liquidations. The strategy collapsed in hours, taking her entire portfolio with it.

Talia had been auditing her sibling’s strategy at the time. She’d warned about the risks, but the warnings had been ignored.

“Your sibling’s position was more complex than mine,” Ravi said quietly.

“It was,” Talia agreed. “But the principle is the same. Composability is powerful, Ravi. It lets you build amazing things. But it’s also dangerous because it creates connections that aren’t always visible.”

She pulled up another visualization: a network diagram showing how different protocols in the ecosystem were connected. Lines crisscrossed between them, representing shared assets, shared oracles, shared dependencies.

“This is the bigger picture,” she said. “Your position isn’t just connected to Protocol A and Protocol B. It’s connected to everyone else who uses those protocols. If your position gets liquidated, it affects them. If their positions get liquidated, it affects you.”

Ravi studied the diagram. It was like a map of a city, but everything was interconnected—power lines, water mains, data cables, all tangled together.

“That’s the real risk,” Talia said. “Systemic risk. The failure of one part causing the failure of the whole.”


Ravi sat back in his virtual chair. His avatar’s face was thoughtful, the earlier enthusiasm tempered.

“You’re saying I shouldn’t do this,” he said. “The leverage loop.”

“I’m saying you should understand what you’re doing,” Talia replied. “The risks aren’t theoretical, Ravi. They’re real. And they’re not just your risks—they’re everyone’s risks.”

“But the returns…”

“I know,” Talia said. “Twenty percent, forty-five percent. It’s tempting. But let me show you something else.”

She pulled up a graph showing Ravi’s position under a series of stress tests: a 15% price drop, a 20% drop, a 30% drop. Each scenario showed his portfolio shrinking faster than he’d expect, the leverage amplifying the losses.

“This is what happens in a crash,” she said. “Your losses aren’t just your initial capital—they’re your initial capital times your leverage. If you’re three times leveraged, a 20% drop costs you 60% of your capital. If you’re five times leveraged, it costs you everything.”

Ravi stared at the graph. The lines were terrifying.

“I’m not expecting a crash,” he said weakly.

“Nobody expects a crash,” Talia said. “That’s why they’re so destructive.”


The meeting room was quiet for a long moment. Outside the glass walls, avatars drifted past, oblivious to the conversation inside.

Ravi looked at his dashboard, at the numbers ticking upward. His position had grown another few units since the meeting began. It felt like progress. It felt like validation.

“Your sibling,” he said finally. “She lost everything?”

“Everything,” Talia confirmed. “She was leveraging five-to-one. A 15% drop wiped her out.”

“What did she do after?”

Talia’s avatar looked away. “She left the community. She’s still in the ecosystem, but she doesn’t build strategies anymore. She just… holds.”

Ravi processed that. He couldn’t imagine leaving. Building strategies was what he loved. It was his purpose, his passion.

“Are you trying to scare me?” he asked.

“I’m trying to warn you,” Talia said. “There’s a difference. I don’t want you to stop building. I want you to build carefully. With eyes open.”

She pushed a file across the holographic table. It was a risk assessment report, detailed and comprehensive.

“This is a breakdown of your current strategy,” she said. “Every risk factor, every connection, every hidden vulnerability. Read it. Think about it. Then decide whether to add the leverage loop.”

Ravi accepted the file, his avatar nodding slowly.

“Thank you,” he said. “I’ll read it.”


Talia stood, her avatar smoothing the front of her jacket.

“I should go,” she said. “I have another audit scheduled in fifteen minutes.”

“Another strategy?” Ravi asked.

“Another warning,” Talia said. “There are a lot of people building similar strategies right now. The community is in a fever pitch about composability. Everyone wants to be the next yield genius.”

“And you’re trying to slow them down?”

“I’m trying to keep them from going bankrupt,” she said. “There’s a difference.”

Ravi nodded. “Same thing.”

“No,” Talia said, her voice softening slightly. “Slowing people down is about controlling them. Protecting them from themselves. That’s not what I’m doing. I’m giving them information. What they do with it is up to them.”

She paused at the door.

“Ravi,” she said. “You’re one of the smartest builders I know. But smart people make the worst mistakes because they think they can outthink the system. The system doesn’t care about intelligence. It just follows its rules, and sometimes the rules are brutal.”

“I understand,” Ravi said.

“Do you?”

He didn’t answer.


After Talia left, Ravi sat alone in the meeting room, staring at the risk assessment report. It was dense, packed with graphs and formulas and worst-case scenarios.

He opened the first page and began reading. Talia had identified a dozen risk factors he hadn’t considered: the volatility of Protocol B’s rewards, the correlation between Protocol A and Protocol B’s assets, the potential for a temporary oracle failure.

She’d also included a simulation of a “domino effect”—a chain reaction that started with a small price drop and ended with a cascade of liquidations.

Ravi read through it all. Part of him appreciated Talia’s thoroughness. But another part—a louder part—was already dismissing the warnings.

She’s too cautious. She’s still traumatized by what happened to her sibling.

He thought about the leverage loop. Forty-five percent APY. His earnings would grow faster than he’d ever imagined. He could hit his goals in months instead of years.

Talia doesn’t understand. I’m not like other builders. I’m careful. I’ve done the math.

He closed the report and reopened his dashboard. The numbers were still green. His position was still growing. Everything was fine.

But Talia’s warnings lingered in the back of his mind, like a splinter he couldn’t quite remove.


Later that evening, Ravi sat at his desk in the real world. The sun had set outside his window, and the city lights were beginning to flicker on. His room was dark except for the glow of his monitors.

He’d re-read Talia’s report twice. The arguments were compelling, but he couldn’t shake the feeling that she was being overly pessimistic. The risks were real, yes. But they were manageable. He could protect himself with stop-losses, diversify his collateral, monitor the oracles more carefully.

He opened his strategy planner and began sketching out the leverage loop again. His fingers moved quickly, entering formulas and parameters.

One loop: 25% effective APY. Two loops: 35%. Three loops: 45%.

He stopped, his hand hovering over the keyboard.

Talia’s voice echoed in his mind: “The risks multiply. A one percent risk in Protocol A and a one percent risk in Protocol B doesn’t make a two percent risk. It makes something much larger.”

Ravi clenched his jaw. She was right about the math, but she was wrong about the practical implications. The risks were small. The probabilities were tiny. He was willing to accept them for the returns.

She’s not the one taking the risk. I am.

He entered the final parameters and saved the strategy.

“Tomorrow,” he murmured. “Tomorrow I’ll implement it.”

He minimized the window and opened his community dashboard. In the DeFi District, the lights were still on. Avatars moved between buildings, building their strategies, chasing their yields.

Ravi saw Talia’s avatar in the distance, standing outside Protocol C’s headquarters, probably delivering another warning to another builder.

She cares too much, he thought. But that’s not a bad thing. Someone has to be the voice of caution.

He just didn’t want that someone to be him.


His phone buzzed on the desk. A message from Talia.

“Did you read the report?”

Ravi smiled. She was persistent, he’d give her that.

“Reading it now,” he lied.

“And?”

“I’ll think about it. Thanks.”

“Promise me you’ll think about it. Really think about it.”

Ravi hesitated. Then he typed: “I promise.”

Talia’s reply came a moment later: “Good. That’s all I ask.”

Ravi set the phone down and returned to his dashboard. The numbers were still ticking upward, but somehow they didn’t feel as satisfying as they had before.

He pushed the feeling aside and started planning the next phase of his strategy.


At 11:47 PM, Ravi was still awake, his eyes fixed on his screens. He’d been tinkering with his leverage loop for hours, running simulations, optimizing parameters.

The results were compelling: 45% APY, steady growth, manageable risk (according to his calculations). He was confident he could execute the strategy without issue.

But Talia’s warnings kept creeping back into his thoughts. He’d seen the domino chain visualization, the stress test results, the network diagram. He understood the risks intellectually.

Understanding isn’t the same as accepting, he thought.

He opened Talia’s report one more time, scrolling to the section on oracle mismatches. The concept was simple but powerful: different protocols used different oracles to value assets. If those oracles disagreed—even by a small amount—it could trigger liquidations and create arbitrage opportunities.

Protocol A uses one oracle. Protocol B uses another. If there’s a divergence…

He shook his head. It was too far-fetched. The oracles were reliable. They’d been stable for years.

But stable until they’re not.

He closed the report. Then he opened his strategy planner and added a few extra safety measures: a smaller initial position, a lower leverage ratio, and a tighter stop-loss trigger.

There. That should make Talia happy.

He saved the updated strategy and closed his laptop. It was almost midnight. He needed to sleep.


As Ravi lay in bed, staring at the ceiling, he thought about the future. His strategy would be successful. He’d prove that composability could be managed safely. He’d show Talia that the risks could be controlled.

But even as he thought it, a small voice whispered in the back of his mind:

What if you’re wrong?

He pushed the voice away and closed his eyes.

Tomorrow, he would implement the leverage loop. Tomorrow, his earnings would multiply. Tomorrow, everything would change.

He fell asleep with a smile on his face, dreaming of bricks and towers and money machines.

He didn’t dream about dominoes.

Table of contents:
Introduction
Chapter 1: The Bricks of Finance
Chapter 2: A Borrowing Position
Chapter 3: The Yield Farm <<<<<< NEXT
Chapter 4: The Leverage Loop
Chapter 5: The Oracle Mismatch
Chapter 6: The Domino Collapse
Chapter 7: The Cascading Liquidation
Chapter 8: The Circuit Breaker
Chapter 9: The Decoupled Protocols
Chapter 10: Interconnected, Not Fragile

Loading



Dear reader, love our creation? Support us moving forward