Discover and read the best of Twitter Threads about #clightning
Most recents (8)
1/ #LAYER2ROUNDUP: Welcome to the latest thread of our monthly series on Lightning and Liquid. What you missed:
⚡️ LN capacity at all-time highs, up 200% yoy
🌇 #LightningHackdayIST
🔖 New research from @vulpemventures
⛏️ BMN on @BFXSecurities
and much more👇🧐
⚡️ LN capacity at all-time highs, up 200% yoy
🌇 #LightningHackdayIST
🔖 New research from @vulpemventures
⛏️ BMN on @BFXSecurities
and much more👇🧐
2/ #Bitcoin capacity for both the @Liquid_BTC and #LightningNetwork continues to steadily rise with year-over-year growth LQ ~25% / LN ~200%, respectively. 🌊⚡️
3/ With an estimated limit of 500 TPS per channel, the #LightningNetwork has a throughput of more than 40 million TPS based on the number of channels today (the equivalent of 14.4 TB size blocks), enabling it to become the global payment layer of the #Bitcoin circular economy.
1/ #LAYER2ROUNDUP: In Jan, both protocols had a slew of big announcements:
🌋 #BitcoinBond update
🥕 #Taproot on @Liquid_BTC
🏛 New #LiquidFederation members
🇦🇷 @ln_strike launches in Argentina
⚡️ Anniversary of the #LightningNetwork whitepaper
Let's review and more👇🧐
🌋 #BitcoinBond update
🥕 #Taproot on @Liquid_BTC
🏛 New #LiquidFederation members
🇦🇷 @ln_strike launches in Argentina
⚡️ Anniversary of the #LightningNetwork whitepaper
Let's review and more👇🧐
2/ Network capacity for both the @Liquid_BTC and #LightningNetwork continued to expand, LQ (3,528) / LN (3,399), reaching new highs for a combined capacity of 6,927 #Bitcoin.
Year-over-year, network capacity has grown LQ 25% / LN 290%, respectively. 🌊⚡️
Year-over-year, network capacity has grown LQ 25% / LN 290%, respectively. 🌊⚡️
3/ On the eve of the #LightningNetwork whitepaper's sixth anniversary, @jackmallers announced the Lightning-powered app @ln_strike was to begin rolling out in Argentina, one of many Latin American nations battling inflation and economic uncertainty.
btctimes.com/news/bitcoin-l…
btctimes.com/news/bitcoin-l…
1/ #LAYER2ROUNDUP: Last month, Lightning implementations #clightning and #LND rolled out major updates, and @Liquid_BTC took centerstage at @AdoptingBTC for the #BitcoinBond announcement.
Combined #L2 capacity also reached a new high of 6,661 BTC (~$377M).
Combined #L2 capacity also reached a new high of 6,661 BTC (~$377M).
2/ We begin at the @TABConf in Atlanta with a #LightningNetwork panel - @alexbosworth, @gkrizek, @niftynei, and @TheBlueMatt - who discussed off-chain scaling, privacy on Lightning, and liquidity ads.
3/ #Liquidityads are a spec proposal that allows Lightning nodes to source inbound capital via the gossip protocol.
I used #clightning's new multifundchannel with every one of the 1837 nodes on testnet. Most are dead, many timed out, some already had channels, and two didn't respond to open_channel, but 106 made it! Here's the open tx:
blockstream.info/testnet/tx/cde…
blockstream.info/testnet/tx/cde…
Thanks to @niftynei for the freshly mined testnet coins, @ZmnSCPxj for the new multifundchannel plugin. We've been able to do this in theory for over a year, but now it's trivial! Though I had to use python: bash told me "Argument list too long".
I had to manually kill the two non-responsive open_channels, since we don't time out. Issue opened for next release (too minor for rc2 imho): github.com/ElementsProjec…
lnprototest is vital for lightning development. It's a simple place to rapidly implement new features for testing: very hackable! It also lets us test things that real implementations don't do. It's an easy on-ramp for interoperability testing.
github.com/rustyrussell/l…
github.com/rustyrussell/l…
For example, I accidentally broke #clightning accepting unknown odd packets. Nothing broke! But this is vital for future upgrades, where we want to rely on this "you will ignore this, not barf" behaviour. lnprototest's predecessor found this.
Testing all the paths of opening a channel lead me to find the CVE-2019-12998. And now we're working on dual-funding channels, it's vital we thoroughly test opening negotiation.
#TLC2019 was over too fast! Everyone I spoke with was trying something exciting, but I feel I barely scratched the surface. Got to fanboy @JackMallers far too briefly (hey, you still in town?). Main things on my to-do list below:
1/ Offers. Well received, great feedback and ideas, main q was "when?". Going to take at least 6 months, but I'm going to start now. Watch mailing list for proposal.
2/ Privacy. "D+. Must try harder". Lots we can fix, like github.com/lightningnetwo… and github.com/ElementsProjec…. Will restore amount fuzzing I accidentally lost. More metrics needed on route fuzzing. Segwit v1 needed too. Nym mixnet yay! But some is v hard...
Note that if you upgrade to #clightning rc, Sparkwallet breaks. @shesek is on it, but meanwhile you can restore the old `listpayments` command with a trivial plugin (since API hasn't *yet* changed):
@shesek #!/usr/bin/env python3
from lightning import Plugin
plugin = Plugin()
@plugin.method("listpayments")
def listpayments(plugin, bolt11=None):
"""Emulate the deprecated listpayments command"""
return plugin.rpc.listsendpays(bolt11)
plugin.run()
from lightning import Plugin
plugin = Plugin()
@plugin.method("listpayments")
def listpayments(plugin, bolt11=None):
"""Emulate the deprecated listpayments command"""
return plugin.rpc.listsendpays(bolt11)
plugin.run()
To collect #boltathon payments, needed more incoming capacity. @bitrefill worked from #eclair but instructions were lnd. Trivially transformed for #clightning, but really need to write a lnurl plugin.
Every time I try to use #LightningNetwork for something real, I see how much more there is to do...
FWIW, here was what I did to redeem channel: lightning-cli connect 030c3f19d742ca294a55c00376b3b355c3c90d61c6b6b39554dbc7ac19b141c14f && lightning-cli -H getinfo | sed -n 's/^id=//p' | tr -d '\n' | curl -G --data-urlencode remoteid@- "api.bitrefill.com/v1/thor?k1=b35…"
