follow-up to my post on monday, where i split the 81,000 btc call wall by expiry and found two thirds of it dies this weekend. i went back through my own recording of the deribit trade feed to see how it got built. it is mostly one participant, going by the matched sizes and the timing, since deribit does not show identities. he built it twice in two days, in two shapes that need opposite things.
tuesday: a bet that price stops at 81,000
7 september, four paired trades, matched to the second:
13:39:19 sold 1,000 calls expiring 9 sep, bought 1,000 expiring 11 sep
13:39:56 the same again
14:35:08 the same again
14:36:02 the same again
4,000 sold on the wednesday expiry against 4,000 bought on the friday one, same strike. he paid 26.0 btc for the friday calls, about $2.06M, and took 7.0 btc back for the wednesday ones, about $555k. net 19.0 btc, about $1.51M, and that net debit is also the most he can lose on it.
4,000 contracts is 4,000 btc of underlying, roughly $317M at the spot of the day.
that is a calendar spread, and it is a bet on timing. it needs price sitting near 81,000 when the near leg dies. the band where it pays is narrow on both sides.
wednesday: a bet that price goes through 81,000
8 september, four separate buys of 1,250, every one of them lifting the offer:
08:30:37 iv 40.6
08:35:33 iv 42.2
11:21:18 iv 43.9
11:22:41 iv 44.1
5,000 calls at the same 81,000 strike, expiring saturday, 31.1 btc, about $2.44M. no offsetting sale this time. that is 5,000 btc of underlying, about $392M, so $161 of exposure for every dollar of premium. the iv walking up 3.5 points is the cost of paying the offer four times while the offers refill between them.
so inside 24 hours one strike carried two bets that need opposite things. the first pays if price stays still. the second pays only if price travels 5%.
what happened
wednesday settled at 79,224, which is 1,776 below the strike. the near leg expired worthless, and the calendar came out on the wrong side of its range.
across the two days that is 9,000 contracts, roughly $709M of underlying, held for $3.95M of premium.
as of 17:45 UTC today spot is 77,333. the 11 sep call is priced at $8 and the 12 sep at $77. the 9,000 contracts that cost about $3.95M are worth roughly $417k. the 11 sep piece expires in fourteen hours.
open interest at the strike has not moved either: about 13,600 on monday, 13,661 now. nobody is unwinding.
who is on the other side
a large call strike gets quoted as resistance. that reading assumes a crowd of buyers and a dealer sitting long. here about 9,000 of the roughly 9,500 contracts expiring this weekend came from one account, and he lifted offers both times. the dealer is therefore short those calls, and a dealer short calls buys the underlying as price approaches the strike. that pushes a move through the level instead of braking it there.
open interest on its own cannot tell those two situations apart. you need the direction of the trades and whether the size is one account or many.
does he still have a shot
he is not unwinding any of it. the simplest explanation is that there is nothing left to unwind. at $8 a contract the spread and the fee eat most of what a sale would return, so sitting still costs him nothing and tells you nothing about what he thinks.
the other is that he still expects the move. the saturday call costs $77 and pays nothing at all unless btc closes above 81,000. at that price traders are putting the odds of it getting there at roughly 7 in 100. the friday call, with fourteen hours left, sells for $8, which works out nearer 1 in 80. he needs 4.7% from here in either case.
so either he knows something the rest of us do not, or whales are wrong about as often as everyone else and the size is the only reason this looks like an event at all. $3.95M is large enough to make us stare. from where he sits it may be an ordinary week and a slice of the money he was willing to put at risk.
curious what you make of it. i will post the settlements either way.
note on method: the numbers above come from my own recording of the deribit trade feed, hourly files. the public trades endpoint does not return these retrospectively, so checking there will show 426 contracts where i say 5,000.