The Arbitrage-Free Valuation Framework

Chapter 2 kicks off with arbitrage-free bond valuation — value additivity, dominance, and the binomial interest rate tree where volatility is the secret sauce!

Yaaaaa finally Chapter 2~~~~~~ Now we start picking up the new Level 2 stuff, bit by bit!!! This is gonna be fun!! haha Anyway, let’s gooooo~~

Chapter 2. The Arbitrage-Free Valuation Framework

When we compute the theoretical price of a bond, we’re going to study valuing it at a price where no arbitrage shows up (the law of one price). But here, unlike Level 1, we leave the door open: rates could go up, rates could go down… and we value bonds by modeling rates with a Binomial Model. heh heh heh heh

Hmm.. so in derivatives, through put-call parity,

Equation from the original notes

we already saw how, the moment that equality breaks, an arbitrage opportunity pops up.

But in the bond market — what kind of setup gives you an arbitrage opportunity?

There are two types of arbitrage opportunities:

➀ Value Additivity (the value of the whole differs from the sum of the values of the parts)

➁ Dominance (one asset trades at a lower price than another asset with identical characteristics)

Equation from the original notes

➁ Dominance: When somebody says “characteristics” about a financial product without specifying, it’s basically shorthand for the return–risk characteristics.

So — same return-risk profile but different price? → That’s when an arbitrage opportunity is sitting there.

(Put-call parity, by the way, was a Dominance-type arbitrage!)

Equation from the original notes

Equation from the original notes

Since the characteristics line up with the benchmark, we can just reuse the same numbers we used to discount the benchmark and value it that way.

Equation from the original notes

Binomial Interest Rate Tree Framework

If we just take the spot rates the market hands us and use them straight up — well, once you’re given the $s_i$’s, the ${}_{i}f_{j}$’s are all observed too,

Equation from the original notes

But in reality ${}_{1}f_{1}$ and $s_1'$ are going to be different, and honestly we can even predict ahead of time that they’ll be different, so when we compute present values now, we want to leave enough room for the possibility that things shift.

Equation from the original notes

That said — ${}_{1}f_{1} > s_1$ still holds, right? (assuming upward sloping) So be careful: don’t model the tree in a shape like

Equation from the original notes

If everyone’s expectation is that ${}_{1}f_{1}$ = 4%, then at the bare minimum the model has to give you a probability-weighted sum that equals 4%. In other words, drawing the tree properly:

Equation from the original notes

The tree itself ends up being an upward-sloping model — that’s what this means!

One more thing. If you’re modeling $s_1$ = 3%, ${}_{1}f_{1}$ = 4%, then actually,

Equation from the original notes

the number of trees that probability-weight back to 4% is not just one, right? In other words, the “angle,” the spread of the branches, is also a key parameter of the model.

And the number that captures it is volatility!

(Next chapter we look at embedded options, and that’s where this becomes super important!)

So — option-free bonds we can value with just a plain spot rate curve. But for bonds with embedded options, future rate changes are going to affect the probability of the option getting exercised, which in turn affects the future cash flows.

Bonds without embedded options? Spot curve, done. (So when you’re working problems, also know not to go through unnecessary suffering on option-free bonds! haha) But callable / putable bonds? The movement of interest rates is hugely tied to whether the option gets exercised, so these absolutely have to be valued through a model that has up-scenarios and down-scenarios baked in!

Anyway — the model we’re going to be working with from here on is the Binomial Interest Rate Tree, and it assumes that next period the interest rate has an equal probability of landing on one of two possible values. (50:50 probability!!! Notice — when we priced options on stocks, we computed and used a risk-neutral probability separately. That part is different here!!!)

OK, let’s actually get into the binomial model, one of the interest rate models.

Most basic question first: if we had to define “what is an interest rate?” in one phrase, what would we say?

Think about it ⇒ couldn’t we just call it “the time value of money”??? ok ok, interest rate model — let’s go!

So, first things first (the first button!): there are two things we’re going to understand about the Binomial Interest Rate Tree Model.

Equation from the original notes

Baseline assumption in finance: the distribution of (gross) returns is Lognormal.

What’s that, simply put?

Equation from the original notes

And in finance the convention is — it’s (log) returns, not stock prices, that get assumed normal. And here, interest rates can be thought of as returns, and apparently it’s better to assume these follow a Lognormal distribution too!

(I tacked on an appendix at the very back from “probability theory I studied,” covering the lognormal section.)

Equation from the original notes

Equation from the original notes

Equation from the original notes

And the use of this model also reflects the following:

Equation from the original notes

But… honestly, at this stage it’s hard to explain how it gets reflected nicely.. that’s content that’s going to click naturally later!!!

What we want to walk away with right here is that the framework we’re going to be using has two features:

➀ Higher volatility at higher rates ➁ Non-negative interest rate

Let’s just remember there are these two!


Heads-up. The figures here are the original notes, slips and all. A few things to watch for:

  • In the picture with the bell curve, the change that is about $\pm\sigma$ is the change in the exponent, $\ln X - \ln i_0$, not $X - i_0$: the rate moves to $X = i_0 e^{\pm\sigma}$.
  • In the picture of one step of the tree, the red relation should read $i_U = i_L\,e^{2\sigma}$; the picture has a dot where the equals sign belongs.

Comments

Discussion happens via GitHub Discussions. You'll need a GitHub account to comment.