Issue #671: Bitcoin leverage flush, Landfall wallet, Second's Ark exploit

1
00:00:00,000 --> 00:00:08,600
Greetings, Bitcoiner. This is Bitcoin Breakdown, your daily Bitcoin briefing on this Thursday,
2
00:00:08,800 --> 00:00:14,320
8th of October. Three stories in under five minutes. Sharp analysis, zero noise. Let's
3
00:00:14,320 --> 00:00:22,620
get into it. First, the price. Bitcoin traded at $83,062 on Wednesday morning, the 7th of
4
00:00:22,620 --> 00:00:33,340
October 2026 in New York. That was down nearly 4% over 24 hours. It dipped as low as $82,823.
5
00:00:34,060 --> 00:00:40,540
Over the past 24 hours, nearly $178 million of Bitcoin long positions were closed,
6
00:00:40,540 --> 00:00:46,820
according to CoinGlass. That figure covers Bitcoin longs only. So do not stack it against
7
00:00:46,820 --> 00:00:51,520
the bigger or crypto liquidation totals you may have seen. Those cover different windows
8
00:00:51,520 --> 00:01:00,960
and a wider market. An earlier report counted $555.6 million of crypto liquidations. $487.2
9
00:01:00,960 --> 00:01:08,280
million of that was longs. Another put long liquidations at $550 million. Gold, silver,
10
00:01:08,480 --> 00:01:21,296
and equities also fell that morning Here is our view We think this was likely a deleveraging event Overenthusiastic leveraged positions got liquidated Gold silver and equities also fell So we think the short
11
00:01:21,296 --> 00:01:27,696
downturn was not Bitcoin-specific. Those closed long positions were leveraged bets that went the
12
00:01:27,696 --> 00:01:32,536
wrong way. Overextended traders paid for the move and the market kept moving without them. Second,
13
00:01:32,796 --> 00:01:37,916
a new wallet for miners. Vincenzo Palazzo released Landfall. It is a showcase wallet,
14
00:01:37,916 --> 00:01:43,556
not a production one. It is built for ocean lightning payouts. One 24 word recovery phrase
15
00:01:43,556 --> 00:01:51,496
does all the work. That phrase derives your BIP 84 payout address locally. So the key that signs
16
00:01:51,496 --> 00:01:57,216
is provably the key that owns the address. The same phrase also seeds a Lexi lightning node.
17
00:01:57,576 --> 00:02:02,196
Lexi runs the node and handles the liquidity. You keep the keys. That node runs in a secure
18
00:02:02,196 --> 00:02:09,116
Enclave. It creates the payable BOLT12 offer. Then you paste in the verification message Ocean
19
00:02:09,116 --> 00:02:17,376
gives you. Landfall signs it verbatim with BIP322. It shows you exactly what was signed and by which
20
00:02:17,376 --> 00:02:35,553
address The author gives plain guidance Use it to receive your Ocean payouts and spend them Do not park a large balance in it Do not restore the recovery phrase of a wallet you care about A showcase gets no security audit no release schedule and no support The project is main
21
00:02:35,553 --> 00:02:40,913
net only, and it also keeps the recovery phrase in a plain text file on the machine running it.
22
00:02:41,433 --> 00:02:45,293
The Enclave design has no independent audit in the sources. If you want a real product,
23
00:02:45,533 --> 00:02:52,653
say so. Open an issue, tip, or tell Ocean. Third, an exploit on the ARC side. Second,
24
00:02:52,653 --> 00:02:58,393
says that on Monday the 5th of October an attacker exploited a bug in its ARK server's boarding flow.
25
00:02:58,633 --> 00:03:07,053
The attacker took 0.75 Bitcoin of Second's own liquidity. Second says the bug let the attacker
26
00:03:07,053 --> 00:03:13,073
register boards with only his own signatures. Second says he then exited those boards back to
27
00:03:13,073 --> 00:03:18,933
his own wallet. At the same time he spent the same VTXOs out of Second's node through Lightning.
28
00:03:18,933 --> 00:03:21,933
Second says no user funds were affected.
29
00:03:21,933 --> 00:03:28,933
A news report relaying Second's statement valued the loss at $62,322 at the time.
30
00:03:28,933 --> 00:03:34,933
User VTXOs sit on pre-signed exit paths the server cannot spend.
31
00:03:34,933 --> 00:03:49,749
So the only Bitcoin exposed was Second own Second also says it mitigated a denial of service attack on its ARK server on Tuesday It ties that attack to the attacker continued probing which delayed Lightning receives on
32
00:03:49,749 --> 00:03:55,409
Bark-based wallets. Every incident fact here comes from Second's own thread. We have not seen
33
00:03:55,409 --> 00:04:00,869
an on-chain trace, an audit, or an independent post-mortem. Treat the numbers as Second's account.
34
00:04:01,129 --> 00:04:06,449
Here is our view. We think the ARK server is not a custodian in any meaningful sense.
35
00:04:06,449 --> 00:04:10,329
It cannot unilaterally move user value, even when compromised.
36
00:04:10,869 --> 00:04:16,089
We think this incident, with only the operator's own liquidity lost, shows that design working.
37
00:04:16,769 --> 00:04:22,589
Second itself says the design did its job, even if it would rather have demonstrated it another way.
38
00:04:23,009 --> 00:04:27,509
Second's chief executive, Stephen Ruse, wrote that this is how money should work.
39
00:04:27,789 --> 00:04:31,289
That is an interested party's opinion, not independent confirmation.
40
00:04:31,809 --> 00:04:34,809
Losing only your own sats is how that design is supposed to fail.
41
00:04:34,809 --> 00:04:39,649
that's your bitcoin breakdown top stories for today you can find the full edition of the
42
00:04:39,649 --> 00:04:44,969
newsletter in the episode's description with much more content including the latest bitcoin insights
43
00:04:44,969 --> 00:04:50,709
and analysis pieces and the latest freedom tech tools and project launches stay humble
44
00:04:50,709 --> 00:04:53,129
and keep on stacking those sats