AULANI (@AC_616) header
AULANI (@AC_616) profile picture

#Bitcoin (only) focused | L🧡VE meeting & supporting Plebs | Creator of the Bitcoin themed @satosphere21 🌎 globe, which rotates by ambient light💡☀️

Joined August 2020
Photo by AULANI (@AC_616)Photo by AULANI (@AC_616)Photo by AULANI (@AC_616)Photo by AULANI (@AC_616)Photo by AULANI (@AC_616)Photo by AULANI (@AC_616)Photo by AULANI (@AC_616)Photo by AULANI (@AC_616)Photo by AULANI (@AC_616)Photo by AULANI (@AC_616)
My first ₿itcoin painting
This Post is from an account that no longer exists. Learn more
6
4
1
33
821
It’d be a million times easier to build a closed-source product that’s only accessible if you give up your identity, with zero consideration for privacy. But that’s not why we’re here. Bitcoin is a revolution, and revolutions are never easy.
6
32
2
373
13,668
It's easy to blame the system, to point fingers at external forces. But true change starts within. Your choices, including the money you use, reflect your values. Aligning with an honest protocol means aligning with integrity. The change is in your hands.
25
52
5
382
12,100
AULANI retweeted
This is the official and current incident report for the @Liquid_BTC hack. Summary: - A vulnerability in Elements' range proof caching was exploited on Sept 6, creating ~4,000 unbacked L-BTC. - The exploiter used SideSwap's peg-out authorization to convert the L-BTC to BTC, draining the reserve from ~4,205 BTC down to 197 BTC. - No keys were compromised. Functionaries operated as designed. The exploit was at the transaction validation level. - 3,400 BTC (~85%) has been returned. ~598.5 BTC still outstanding, discussions ongoing. - Emergency Elements release (v23.3.4) is in review, expected within ~48 hours. My comments: Regarding safe network restoration, Blockstream and Liquid Federation members are actively working on this. Estimates are looking like it could be 4-5 days, depending on various factors. We are all very much aware that many users still have funds in Liquid (L-BTC, USDT, DePix, etc) and are awaiting access, so again, safe network restoration is a priority. What the state of the network will be post restoration, given the shortfall in L-BTC, is also under discussion. Finally, securing the return of the remaining funds in control of the hacker is also a priority. Thanks again for your patience and understanding. There are multiple tracks being navigated here and none of them are simple and straightforward. 🙏
LIQUID NETWORK UPDATE: INCIDENT REPORT Status as of September 8, 2026, 19:10 UTC What Happened? On September 6, 2026 at 15:53:10 UTC (Liquid block 4,050,336), a vulnerability in the open-source Elements software related to how Liquid nodes cache range proof verifications was exploited, resulting in the creation of ~4,000 LBTC that were not backed by bitcoin held in reserve. The individual(s) responsible for the exploit then used the SideSwap service, a Liquid Federation member that holds a peg-out authorization (PAK) key, to convert the unbacked LBTC to BTC via Liquid’s standard peg-out mechanism. Because the validation failure occurred at the transaction level before the peg-out was initiated, both SideSwap’s node and the Liquid Network’s globally distributed functionary nodes accepted the LBTC as valid. The functionaries processed the peg-out as authorized, releasing approximately 4,000 BTC through SideSwap’s whitelisted bitcoin address, which SideSwap then forwarded to the address specified by the exploiters. Before the incident, the Liquid reserve held approximately 4,205 BTC. Following this peg-out and additional peg-outs processed before operations were halted, the reserve balance fell to 197 BTC. Key Clarifications No keys were compromised. The Liquid Federation functionaries were not hacked, and no private keys were compromised. The peg-out mechanism that authorizes withdrawals to whitelisted addresses operated as designed. Other Liquid-issued assets were not affected. USDT and other tokens issued on the Liquid Network were not impacted by the vulnerability, though they are temporarily unavailable while the network remains paused. Investigation is ongoing. As is common in complex critical-system failure investigations, this incident arose from the convergence of several individually low-probability factors that interacted in ways that ultimately defeated the system's built-in redundancies. More detail will be shared in forthcoming communications. What Steps Have Been Taken To Recover The Assets? The individual(s) responsible for the exploit left a public message on the bitcoin mainchain identifying themselves as white-hat security researchers and requesting contact to address the vulnerability. Patch deployed. Blockstream identified and deployed a patch to the Liquid Network’s bridge nodes, which was completed on September 7 at 01:09 UTC, ensuring the vulnerability is no longer exploitable. Partial fund recovery. On September 7 at 16:09:25 UTC (Liquid block 965,950), the exploiters returned 3,400 BTC to the Liquid Federation peg wallet. Approximately 598.5 BTC (15% of the total) remains outstanding. Discussions between Blockstream and the individuals responsible are ongoing to secure the return of the remaining funds. What Comes Next? Our immediate priorities are recovering the remaining funds and resuming normal network operations safely and as quickly as possible. Software update in progress. A fix for the exploited vulnerability has been developed and is undergoing multiple rounds of internal and external review. Blockstream is preparing an emergency release of Elements (v23.3.4), which is expected to be released as soon as possible, but within approximately 48 hours. Network restoration. Once the software update is finalized, Liquid Network functionary operators will perform additional adjustments to resume full functionality and restore the corrected network state, including rejection of the invalid peg-out. Ongoing updates. We will continue to provide detailed updates as the situation progresses. What You Should Know The Liquid Network remains offline at this time, while we work on reviewing the security fixes and network resumption code and coordinate with the white hat hacker towards timely resumption of the network with 1:1 backing for BTC. While the network is paused, users cannot transact on Liquid. If you operate a Liquid node, please watch for the emergency Elements release and follow the upgrade instructions when available. Users do not need to take any proactive steps to protect their funds at this time. The Liquid Federation and its members are committed to resolving this incident in coordination with Blockstream and to resuming normal operations as soon as it is safe to do so.
9
45
10
296
57,620
The Liquid Federation's top priority is resolving the security vulnerability and restoring secure, normal operations as quickly as possible. Your AQUA Wallet app and private keys remain completely uncompromised. Native on-chain Bitcoin transactions are unaffected and continue to function normally inside the app. As the Liquid sidechain is currently paused, Liquid transactions cannot be processed at this time. The white-hat party responsible for the exploit is communicating on-chain with Blockstream actively. We are monitoring the situation closely and will share further official updates as soon as network activity safely resumes.
20
16
162
12,318
If ColdCard is going to *try* to compare this to product liability cases, it would be the Ford Pinto case we all studied in law school The bigger issue for ColdCard is the product’s entire purpose failed for a large scale of users, serious financial harm was caused and there’s a lot more to it than just a faulty car part
20
17
141
7,114
It’s been 36 days since the Coldcard hack and the victims deserve more answers.
🚨 MOVE YOUR BITCOIN AS SOON AS POSSIBLE. Just had a friend lose $10,000 worth of Bitcoin. It was an COLDCARD Mk3. They did not use a passphrase. They did not use dice rolls.
9
7
66
4,590
AULANI retweeted
"Your node is not a vote." 🟠❌ @Excellion clears up a major misconception in the consensus debate. He explains why a node is a tool for personal financial sovereignty rather than a voting machine or a network governance tool.
8
11
1
44
5,721
HOW DO YOU EXPLAIN BITCOIN MINING?!? BOOKMARK this one for the next time your friends, family, colleagues, or classmates ask what Bitcoin mining actually is 😎 It always helps me to hear it again. Thanks @skwp for the framework!
36
95
13
539
44,166
IF you're not a part of the @clctibles art gallery at the Midwest Bitcoin Summit... well, DM me. We have reserved some wall space for some legit submissions. Stoked to see all this art IRL 👇
7
7
2
32
1,823
AULANI retweeted
There's been elevated interest in multi-vendor multisig since the Coldcard vulnerability disclosure a month ago. Multi-vendor multisig can reduce overall exposure to device vulnerabilities, but there are tradeoffs to consider as well.
9
21
79
7,372
I have added more passphrase wallets to the experiment. I created a new mk3 seed phrase - swept instantly, as expected. Will upload a video soon that explains the different passphrase strengths.
27
15
2
234
13,376
RT @Satosphere21: ⛔️ NOTE: Our payment server is temporarily down, so online ordering is paused for now. Thank you for your patience while…
1
6
The Yen is collapsing, Kevin Warsh is switching teams, And there's only one way out. It's today's MACROHARD MINUTE Let's get into it...
62
143
25
1,387
112,112
We're donating 0.21 BTC to @craigraw and 0.21 BTC to the Bitcoin Red Team for their responsible security disclosure of the recent critical vulnerability. In addition, friends and supporters of the BTCPay Server project have committed to funding a bounty to recover the stolen funds. The bounty will be 10% of the amount recovered, up to a maximum of 3 BTC for full recovery of the funds. These are modest contributions, but they are what we can offer as a FOSS project and a way to appreciate people doing critical security work, which helps the entire ecosystem. To anyone with actionable information that could lead to a recovery, including the attacker, please contact: [email protected]. Signal and other secure communication channels can be provided upon request. If multiple reports contribute to the recovery, the bounty will be split in coordination with the victims, based on the amount each victim lost, the funds recovered, how useful the information was to the recovery efforts, and other relevant factors.
20
118
16
514
48,671
Want to get bullish about Bitcoin again? Buy something with BTC and feel why they call it magic internet money.
8
2
1
24
1,912
AULANI retweeted
This is an ongoing attack on BTCPayserver users. Citadel21's lightning node was just swept. Fortunately there were not much funds there, due to cautionary steps before BIP-110 activation. Praying for all other affected users.
There is a critical vulnerability being actively exploited on BTCPay Server, which can result in the loss of funds. Please update your BTCPayServer to 2.4.2 by going to Admin Dashboard -> Server -> Maintenance -> Update & verify the 2.4.2 version string in the footer. If you are unable to update right away, turn off your BTCPay Server to prevent unauthorized access until you can update.
21
72
7
321
34,011
AULANI retweeted
Dice rolls? Entropy? Public keys??? If you’ve been left anxious & confused this week, this event will cover how multisig is protecting people right now, how to eliminate single points of failure, and how it all actually works. Tomorrow, 4PM CT. unchained.com/events/strengt…
6
15
51
4,353
AULANI retweeted
ZEUS infrastructure is temporarily offline following a cybersecurity incident. The attack has been mitigated. We are keeping services offline while we conduct a comprehensive audit of all systems before restoring operations. **Customer funds were neither lost or at risk.**
25
162
59
603
113,146
AULANI retweeted
Following the Coldcard vulnerability disclosure, we're already seeing an increase in phishing attempts. Stay alert for scams ⚠️ • Never share your wallet backup, aka recovery seed (12/20/24 words) • Only enter your wallet backup directly on your Trezor device during recovery • Trezor will never contact you asking for your wallet backup • Never follow wallet-migration instructions from unsolicited emails, messages or phone calls Trezor devices are not affected by the Coldcard incident.
69
209
24
1,533
92,825