Oli (@guggero) header
Oli (@guggero) profile picture

Struck by Lightning ⚡️ PGP F4FC70F07310028424EFC20A8E4256593F177720 (also https://teapawt.org/t.co/9SEa4Fb5rv)

Berne, Switzerland
Joined September 2008
Photo by Oli (@guggero)Photo by Oli (@guggero)Photo by Oli (@guggero)Photo by Oli (@guggero)Photo by Oli (@guggero)Photo by Oli (@guggero)Photo by Oli (@guggero)Photo by Oli (@guggero)Photo by Oli (@guggero)Photo by Oli (@guggero)
This is our Self Order Point in action. Scan a QR code, pay it with your #LightningNetwork enabled wallet and get a random generated order name that you can mention to pick up your order at the coffee bar inside. @EnergyKitchen @puzzleitc @lightning
9
92
26
301
Replying to @guggero
"The hash re-uses the sha_sequences and sha_outputs digests we already pre-compute for BIP 341." Nice.
1
1
3
102
I finally found the time to dig into the different covenant soft fork proposals out there and make up my mind. I think #BIP448 is what we should go with (+ #BIP54 of course, that's a no-brainer). With just three opcodes (OP_TEMPLATEHASH, OP_CHECKSIGFROMSTACK, OP_INTERNALKEY) we
4
13
64
2,571
me understand things. Demo of different scenarios #BIP448 allows (not all of them useful, just educational): guggero.github.io/cryptograp… If you want to learn more about OP_TEMPLATEHASH, see guggero.github.io/cryptograp… Its implementation in Go is roughly 40 lines of hashing logic:
1
4
23
876
For those that have long running nodes, the Bitcoin data community would REALLY appreciate if you could check your node for stale block data: github.com/bitcoin-data/stal…
2
9
2
28
2,954
Just finished sending out another batch of emails/DMs with matches from node-recovery.com (LN zombie recovery service). Hopefully another 20 zombie channels that can be rescued.
3
1
5
516
Today, we're publishing BIP SHRINCS, the first concrete proposal for a post-quantum signature scheme designed specifically for Bitcoin. The BIP draft turns what began as a rough idea into exact algorithms with an executable reference implementation. This is an important milestone: the discussion can now focus on analyzing, criticizing, and improving a concrete proposal. The BIP makes choices ranging from major design questions, such as whether to support flexible XMSS and how to balance signature size against verification time, to the many smaller decisions involved in saving a byte here or there. All of these choices are up for debate. Big thanks to Mike Casey, @conduition, @Ethan_Heilman, @kudinov_mikhail, @olkurbatov, Boris Nagaev, and @remix7531 for their contributions to the BIP. A lot more work lies ahead: - The draft BIP specifies only the cryptography. Using SHRINCS in Bitcoin Script will require a separate BIP. - We are working on a security proof for the exact construction and parameters. - Wallet integration and user experience, for example around backups and recovery after state loss, are still at an early stage. The design space remains wide open. SHRINCS is not intended to be Bitcoin's "final" signature scheme, and it is not optimal along every axis. I do think it is a very good trade-off among the options we have now. bitcoin-dev post: groups.google.com/g/bitcoind… Draft BIP: github.com/SHRINCS/shrincs-b…
40
145
34
553
129,765
Ark Protocol Explainers ⚓️🚢 I'll be stepping away from the Bitcoin space for a bit, but before I do I wanted to leave one last thing behind: a three part series on how the Ark protocol actually works. VTXOs, Connectors, Checkpoint Txs, OOR and more! See thread for links 🧵
9
31
4
122
12,988
Dashboard tracking LN channel closures over the last few days. It assumes that 2-of-2 multisig spends are likely LN channels. The recent attacks on BTCPay would likely manifest in cooperative channel closures. closes.ellemouton.com/
1
6
1
17
1,087
Thanks to the Bitcoin Red Team (follow @Rob1Ham @craigraw @callebtc @evankaloudis) for the responsible security disclosure and for providing details to address the vulnerability. To stay safe, make sure that even after the update, you: - Completely refresh macaroons and macaroons.db - Completely refresh auth strings for other LN backends - If you generated a hot on-chain wallet in BTCPay, you want to move those funds and recreate the wallet
17
105
25
632
98,671
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.
215
1,343
520
2,540
1,619,784
Is it just me or is working with clankers much more mentally taxing than coding yourself? Things move much faster, so more context switching between parallel-running tasks, more decisions to make…
5
19
688
Wow, Kimi K3 is indeed crazy good at finding bugs (as @callebtc and @Rob1Ham have shown in their recent red teaming effort as well). You should definitely sweep all your projects and open PRs with Kimi, write the findings to files, then let your "cheaper" clanker fix them.
2
1
23
2,093
I just made a Lightning payment from @arkade_os into @lightning Lab's wavelength (and back) on signet. Pretty slick UX 〰️⚡️ Integration was pretty easy too 🚀
4
9
1
38
2,827
Going to set up some LN infrastructure on Signet and need a couple of sats more than what the faucets can give me. Who can make me Signet rich? tb1pf2m22cvykzj7p092dapra9ckjl4j9mq6enppjkmltjqgg7g24yxsy4zfte Thanks!
4
1
6
1,240
Wow, that was fast, already got more than enough, thank you @emzy!!! teapawt.org/emzy/status/2080641161…
2
137
Announcing Wavelength, the easiest way to integrate bitcoin for agents and humans. 〰️⚡ With a simple non-custodial API, anyone can integrate Lightning into their app and get instant, high volume, low fee transactions. Machines can pay machines. Humans can pay humans. Anywhere. The future of agentic money is ours to build. Learn more: lightning.engineering/posts/… Start building it: wavelength.lightning.enginee…
57
161
57
662
167,388
announcing Wavelength, our solution to make self-custodial Bitcoin payments easy for humans and agents alike! Wavelength serves as a standalone daemon (and library!) that makes it easy to instantly send+recv Bitcoin payments 😎 λ it seamlessly operates on/off-chain, w/ off-chain payments using a normal BOLT 11 invoice we all know and love! github.com/lightninglabs/wav…
Announcing Wavelength, the easiest way to integrate bitcoin for agents and humans. 〰️⚡ With a simple non-custodial API, anyone can integrate Lightning into their app and get instant, high volume, low fee transactions. Machines can pay machines. Humans can pay humans. Anywhere. The future of agentic money is ours to build. Learn more: lightning.engineering/posts/… Start building it: wavelength.lightning.enginee…
10
43
5
167
15,203