Liquity V2 Trove Explorer

Back to Blog

Introducing Rails: DeFi Self-Service Support

Rails tracks interactions with DeFi protocols, helping you understand activity from real events

Introducing Rails: DeFi Self-Service Support

Before you interact with any DeFi protocol, wouldn't you want to see how it actually works? Not just read the docs but see how real users are managing real positions?

Rails is a transparency layer for DeFi protocols. Instead of reading documentation and hoping you understand, you can browse real positions, see real transactions, and watch how experienced users manage risk. Every redemption, every interest rate adjustment, every liquidation—all visible and explained in context. When you open a position yourself, Rails tracks your complete timeline. Every action you take, every event that affects your position, presented chronologically with clear explanations of what happened and why it matters.

A redemption example

Let's look at a real event: a redemption that cleared 27,802 BOLD of debt.

On Rails, you see this transaction with an orange "REDEMPTION" badge. The position's debt dropped from 96,131 BOLD to 68,329 BOLD. Collateral went from 61.28 wstETH to 55.7 wstETH. The collateral ratio actually improved from 301% to 385%.

Walkthrough showing how to view and understand a redemption event in Rails
Viewing a redemption event in Rails: Click to expand transaction details and see the underlying mechanics

Click to expand the details and you learn the underlying mechanics: A BOLD holder exchanged their BOLD for collateral at face value. This happens when BOLD trades below $1, making redemptions profitable for arbitrageurs.

This is the beauty of Liquity V2's design—redemptions are essential for keeping BOLD pegged to $1. When BOLD dips below a dollar, arbitrageurs profit by buying cheap BOLD and redeeming it for $1 worth of collateral. This buying pressure pushes BOLD back toward its peg. It's an elegant, automated mechanism that requires no governance or intervention.

The position got hit because it had a 4.2% interest rate—one of the lowest in the wstETH branch. Now you understand something crucial about how the protocol works: interest rate determines redemption risk. Low rate = low cost borrowing, but higher chance of redemption when the peg weakens. High rate = more expensive, but protection from redemptions.

After the redemption the borrower immediately increased their interest rate from 4.2% to 4.7%.

See the patterns

Look at the Trove list view. Notice interest rates with labels like "Summerstone" or "ARM"? That's a batch manager—a service that actively manages interest rates for you. Being able to judge the performance of these delegates will help you decide if you should manage rates yourself or delegate to a service.

See the closed Trove with 1.46 million BOLD debt? Check its timeline. You can view its entire history—when it borrowed, how it adjusted rates, when it got redeemed, how it was closed. Every mechanic of the protocol visible in one position's lifecycle.

This is how you really understand a protocol: watching the underlying mechanics operate through real positions.

Beyond raw data

Traditional block explorers show you event logs and hex data. Rails shows you what those events actually mean.

The timeline view displays every action chronologically with visual icons. Borrows, interest rate adjustments, transfers, redemptions—all in sequence showing cause and effect. You see the mechanics in motion.

Rails also provides educational context. When viewing a redemption, there's a "How Redemptions Work" section explaining the mechanism. Links to common questions like "What happens if my Trove gets redeemed?" and "How can I stay protected?"

Why this matters

DeFi protocols are powerful but complex. Traditional approaches give you documentation and tutorials. Rails shows you something different: the actual mechanics operating in real positions.

See how the largest borrowers manage risk. Notice what interest rates actually protect from redemptions. Watch how positions respond when BOLD loses its peg. Understand the protocol through observed behavior, not theoretical examples.

What you can do now

Currently in beta, Rails currently supports Liquity V2 across all collateral types (WETH, wstETH, rETH). You can:

  • Browse active Troves to see protocol mechanics in action
  • View any position's complete timeline by address or ENS name
  • Explore redemption patterns and borrowing strategies
  • Understand how the protocol actually works before risking capital

Start with the Trove list. Filter by collateral type. Sort by interest rate or debt size. Click into positions and explore their timelines. See the mechanics operate through hundreds of real transactions.

Then decide if the protocol is right for you.

Try it: rails.finance