ADAM BACK: "I have a bet on for Bitcoin to top $1 million by the end of the cycle, which is later in 2028."
Adam Back
Adam Back (born July 1970) is a British cryptographer and cypherpunk. He is the CEO of Blockstream, which he co-founded in 2014. He invented Hashcash, which is used in the bitcoin mining process. An investigation by The New York Times suggested that he may be Satoshi Nakamoto, the pseudonymous inventor of bitcoin, though Back has denied this claim. More on Wikipedia
-
Adam Back reposted
JAN3
@JAN3com
-
Adam Back reposted
The Bitcoin Historian
@pete_rizzo_
BREAKING: ๐ฆ๐ช $300 BILLION UAE SOVEREIGN WEALTH FUND MUBADALA JUST ANNOUNCED IT OWNS NEARLY $700,000,000 WORTH OF #bitcoin
MIDDLE EASTERN OIL MONEY CONTINUES TO BUY AND HOLD
THEY ARENโT PANIC SELLING
DIP IS ONLY TEMPORARY ๐ -
Adam Back reposted
The Bitcoin Historian
@pete_rizzo_
BREAKING: ๐บ๐ธ HARVARD UNIVERSITY JUST ANNOUNCED IT OWNS OVER $144,000,000 WORTH OF #bitcoin
THE HIGHEST LEVELS OF ACADEMIA ARE HODLING BTC
INSANELY BULLISH ๐ -
Adam Back reposted
The Bitcoin Historian
@pete_rizzo_
BREAKING: ๐บ๐ธ $5 TRILLION BANK OF AMERICA JUST ANNOUNCED THEY INCREASED THEIR #bitcoin HOLDINGS BY OVER 580% TO OVER $700,000,000
AMERICA'S SECOND LARGEST BANK IS GOING ALL IN ON BTC
INSTITUTIONAL FOMO IS REAL ๐ฅ -
Adam Back reposted
Lily @timel9379
๐จ๐จLatest news: 80 year old investment legend Peter Brandt says #bitcoin will reach $600,000 within "this cycle."
Itโs coming.๐๐ -
Adam Back reposted
Bitcoin Security Consortium
@BTCconsortium
Consortium member company, Coinbase, co-hosted a Post-Quantum Bitcoin Workshop at Stanford University at the end of August. The one-day event included Bitcoin developers, cryptographers, researchers, institutional custodians, and hardware-wallet experts.
www.coinbase.com/blog/moving-bitcoins-post-quantum-readinโฆ -
Adam Back reposted
Bitcoin.com News
@BitcoinNews
NEW: ๐๏ธ"There was some kind of maybe premature optimism about institutional adoption," said Blockstream's Adam Back this week.
"The institutional adoption is yet to come, which is the managed money, the mutual funds, the model portfolios that BlackRock and others have put out."This media couldn't be displayed. See it on the original post. -
Adam Back reposted
MemeHub @MemeHubCo
Run that weekly turbo @adam3us @paoloardoino
-
Adam Back
@adam3us
Bouncy. ๐ฉ+5.5% overnight๐
-
Adam Back reposted
The Bitcoin Historian
@pete_rizzo_
BREAKING: ๐บ๐ธ $13 TRILLION VANGUARD'S ADVISORY ARM JUST REPORTED THEY JUST BOUGHT #bitcoin FOR THE FIRST TIME EVER
THE FIRM THAT SAID IT WOULD NEVER RECOMMEND BTC IS NOW HOLDING IT
THE DOMINOES ARE FALLING ๐ -
Adam Back reposted
Matt Cole
@ColeMacro
Bitcoin fell 19% into the biggest IPO ever. Now it's down 18% heading into the second biggest.
SpaceX raised $75B when it went public on June 12. In the 50 days before it listed, Bitcoin dropped 19%. Anthropic plans to raise up to $64B when it lists next week, and Bitcoin is down 18% over the same stretch. Overlay the two and they look almost the same.
What happened after the SpaceX IPO is the notable part. Bitcoin bottomed 18 days after the listing, then recovered all the way. By Day 100, it was above where it started.
Bitcoin around the SpaceX IPO:
Day -50 to IPO day: -19%
Low (Day +18): -25%
Day +50: still -20%
Around Day +70: a sharp rally
Day +100: +3.7%
From the IPO-day close to Day +100, Bitcoin gained 28%. From the low, it gained 39%.
The takeaway is that the selling came in the run-up to the listing. The bottom had effectively happened by the IPO, and the recovery came relatively shortly after, and it came all at once.
If Anthropic follows the same pattern, most of the drawdown is behind us, and it could reverse quickly over the next couple of months. And Bitcoin is sitting right at its 200-week moving average.
Map the SpaceX path onto today's price and you get roughly $90k by late February. Markets rarely follow a comparison like this exactly. But we remain very constructive on both the technicals and the fundamentals heading into 2027, and it's not hard to imagine what the narrative would be if anything close to this plays out. -
Adam Back reposted
Alexander Leishman ๐บ๐ธ
@Leishman
The Bitcoin network has continued to operate flawlessly in an era where software is being broken by AI 24/7. This is due to the vigilance and talent of the Core Devs. It's important we continue to stay ahead of any threats. Only the paranoid survive.
-
Adam Back reposted
Alistair Milne
@alistairmilne
Maybe a few months from now or certainly 12-24 months from now, a very large number of people will be asking themselves 'why was I scared to buy?' or 'why did I panic?' when remembering these unrelenting dips in 2026
-
Adam Back reposted
Richard Pasquin @rpasquinjr
We may be at the bottom of the bear market, but institutional crypto is here to stay and is in fact growing. Every institutional crypto event I attend, Iโm always discovering more tradFi companies further along the adoption curve in digital assets than I would expect.
The Digital Assets Forum yesterday was further affirmation of this. @adam3us did a great panel. -
Adam Back reposted
CryptosRus
@CryptosR_Us
ADAM BACK: "Bitcoin to top a Million by the end of the cycle, which is later in 2028."
The @Blockstream CEO believes $BTC is only in the early innings of a new bull market.
He argues that while Bitcoin's price isn't much higher than its previous cycle peak of $69,000, the market is now coming out of a bottom rather than approaching a top. ๐This media couldn't be displayed. See it on the original post. -
Adam Back reposted
BTC Times
@BTCTimescom
ICYMI: ๐ซ๐ท @_ALCPB added 12 #bitcoin, bringing its treasury to 3,550 and BTC Yield to 2.23% YTD, with prior backing from @adam3us.
btctimes.com/capital-b-adds-12-bitcoin-as-holdings-reach-โฆ -
Adam Back reposted
Artem Chystiakov
@Arvolear
Following a bigger Blockstream redesign, the Simplicity lang website got a new look! Now much simpler.
simplicity-lang.org -
Adam Back reposted
Eric Balchunas
@EricBalchunas
Good DAF event today in midtown, weather notwithstanding. Enjoyed my panel w @matthew_sigel , Ally Wallace of MS and David Kroger of T Rowe. Was also nice to finally meet @adam3us in person. Good chat.
Digital Assets Forum
@DAF_Global
Can tokenisation deliver on its promise to transform Wall Street?
Faster settlement, greater efficiency and improved liquidity are among the potential benefits. But bringing traditional financial markets on-chain requires more than technology.
At DAF New York, @EricBalchunas (@Bloomberg Intelligence) and Michelle Neal (@fnality) explored these challenges during "Rewiring Wall Street: Can Tokenisation Deliver on Its Promise?"
The discussion examined the role of regulated market infrastructure, interoperability, settlement and the commercial case for tokenising financial assets.
The question is no longer whether tokenisation is technically possible, but whether it can deliver measurable improvements over existing financial systems.
More panels are taking place throughout the day.
Explore the agenda:
eblockchainconvention.com/agenda-daf-new-york/ -
Adam Back reposted
vanessagrellet.eth ๐ฆ๐๐ค
@VanessaGrellet_
Morgan Stanley and T. Rowe sharing a crypto panel with VanEck shows how far the wealth conversation has moved: from whether to how much, and in which wrapper.
-
Adam Back reposted
Eric Balchunas
@EricBalchunas
Totally
-
Adam Back reposted
Blockstream
@Blockstream
A full room on the Blockstream Stage for Bitcoin's role in the future of finance.
Our CEO @adam3us with @JanvanEck3 and @danheld on why Bitcoin has wider uses than gold, its mathematical assurances in an uncertain world, and its four-year cycle.
Thanks, @DAF_Global. ๐บ๐ธ -
Adam Back reposted
Blockstream
@Blockstream
Custody built for institutions, with keys protected even during signing.
Read the announcement: our enterprise custody solution, developed in collaboration with Thales.
blog.blockstream.com/press-releases/blockstream-launches-โฆ -
Adam Back reposted
Blockstream
@Blockstream
That's a wrap on the Digital Assets Forum in New York.
Thank you to everyone who joined our workshops, to @adam3us for two sessions on the Blockstream Stage, and to @DAF_Global for hosting. ๐บ๐ธThis media couldn't be displayed. See it on the original post. -
Adam Back reposted
Blockstream
@Blockstream
Our CEO @adam3us on @CNBCOvertime: "going back to basics, cold storage, keep things off the internet."
Our new enterprise custody solution runs the entire Secure-MPC signing protocol inside Thales hardware security modules, so key material stays protected, even during signing.This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Blockstream
@Blockstream
Happening now: Igor Iochpa and @sagungarg on tokenized assets, stablecoins and new financial products built on Elements, in our workshop room at @DAF_Global Forum in New York. ๐บ๐ธ
-
Adam Back reposted
The Bitcoin Historian
@pete_rizzo_
๐ฅ MUST WATCH: MICHAEL SAYLOR ABSOLUTELY DESTROYS THE #bitcoin QUANTUM FUD IN UNDER 1 MINUTE
"THERE IS NO QUANTUM COMPUTER"
"THE DANGER IS UPGRADING SOFTWARE TO BE TOO COMPLICATED TOO QUICKLY BEFORE THE THREAT MANIFESTS ITSELF"
"YOU DONโT VACCINATE YOUR KID AT AGE 1 AGAINST SOME DISEASE THEY MIGHT GET AT AGE 67"
DON'T BELIEVE THE FUD. HODL ๐
Source: @StrategyThis media couldn't be displayed. See it on the original post. -
Adam Back reposted
Blockstream
@Blockstream
Take digital asset infrastructure from strategy to delivery.
Oz Ozturk and Vassili Lavrov walk institutions through solution engineering, development, integration and deployment with Blockstream.
Nov 13, 3:30 PM ET, Digital Assets Forum, New York. -
Adam Back reposted
Blockstream
@Blockstream
In 30 minutes: Oz Ozturk and Vassili Lavrov on building institutional digital asset infrastructure, from strategy and solution engineering through integration and deployment.
3:30 PM, in our workshop room at @DAF_Global, New York. ๐บ๐ธ
Blockstream
@Blockstream
Take digital asset infrastructure from strategy to delivery.
Oz Ozturk and Vassili Lavrov walk institutions through solution engineering, development, integration and deployment with Blockstream.
Nov 13, 3:30 PM ET, Digital Assets Forum, New York. -
Adam Back reposted
Blockstream
@Blockstream
You decide who sees what.
On Elements, confidential transactions hide the asset and amount by default. Share the unblinding key with your auditor or partner, and they can verify everything.
Igor Iochpa of Blockstream Enterprise, from our workshop at @DAF_Global. ๐บ๐ธThis media couldn't be displayed. See it on the original post. -
Adam Back reposted
Blockstream
@Blockstream
In 30 minutes: @sagungarg and Igor Iochpa on growth opportunities on Bitcoin infrastructure: tokenized assets, stablecoins, collateral mobility and new products built on Elements.
1:30 PM, in our workshop room at @DAF_Global, New York. ๐บ๐ธ
Blockstream
@Blockstream
Tokenized assets, stablecoins and collateral mobility on Bitcoin-based infrastructure.
Igor Iochpa and @sagungarg show how financial institutions can build new products and services on Elements.
Nov 13, 1:30 PM ET, Digital Assets Forum, New York. -
Adam Back reposted
Blockstream
@Blockstream
In an uncertain world, Bitcoin's mathematical assurances still matter.
Our CEO @adam3us on why: in the short term it may move with tech stocks, but over longer time frames it's relatively decorrelated.
With @JanvanEck3 and @danheld on the Blockstream Stage @DAF_Global. ๐บ๐ธThis media couldn't be displayed. See it on the original post. -
Adam Back reposted
Blockstream
@Blockstream
Confidentiality and visibility, on the same chain.
On Elements, transactions stay confidential while the sender, receiver and issuer can still view them.
@sagungarg of Blockstream Enterprise on why that matters for traditional markets. From our workshop at @DAF_Global. ๐บ๐ธThis media couldn't be displayed. See it on the original post. -
Adam Back reposted
Blockstream
@Blockstream
Happening now: Oz Ozturk and Vassili Lavrov on taking institutional digital asset infrastructure from strategy to delivery, in our workshop room at the Digital Assets Forum in New York. ๐บ๐ธ
-
Adam Back reposted
Digital Assets Forum
@DAF_Global
Bitcoin is becoming an increasingly important part of the institutional investment conversation. But what role will it ultimately play in the future of finance?
At DAF New York, @danheld (Held Media), @adam3us (@Blockstream) and @JanvanEck3 (@vaneck_us) explored this question during the panel "Bitcoin's Role in the Future of Finance."
From the growth of spot Bitcoin ETFs and institutional portfolio allocations to Bitcoin's long-term investment thesis, the conversation examined how its place within traditional financial markets continues to evolve.
Will Bitcoin remain primarily a store of value, become a standard component of institutional portfolios or take on a broader role in the global financial system?
More panels are taking place throughout the day at DAF New York.
Explore the agenda:
eblockchainconvention.com/agenda-daf-new-york/ -
Adam Back reposted
Blockstream
@Blockstream
In 30 minutes: our CEO @adam3us on Bitcoin vs. Quantum: Securing the Future of Digital Assets, with Will Su of BlackRock and Frank Chaparro.
2:25 PM ET on the Blockstream Stage at @DAF_Global, New York. ๐บ๐ธ -
Adam Back reposted
Blockstream
@Blockstream
Go cold: air gaps, no internet connection and, for individuals, a hardware wallet with an offline backup.
Our CEO @adam3us on the lesson for custody, with @fintechfrank and Will Su of @BlackRock on the Blockstream Stage at @DAF_Global. ๐บ๐ธThis media couldn't be displayed. See it on the original post. -
Adam Back reposted
Michael Ford
@fanquake
A BIP54 implementation for Bitcoin Core has just been updated to address rounds of review feedback. Thereโs plenty of time left for Core to ship this in v33: github.com/bitcoin/bitcoin/pull/35793
Mike Schmidt
@bitschmidty
BIP54 updates from the last several months of Consensus Cleanup work
Implementation progress:
Bitcoin Core: github.com/bitcoin/bitcoin/pull/35793 (open) implements BIP54's rules without mainnet activation. Needs reviewers.
libbitcoin: github.com/libbitcoin/libbitcoin-system/pull/2149 (merged)
rbitcoin: github.com/reardencode/rbitcoin/pull/1173 (draft, signet)
btcd: github.com/btcsuite/btcd/pull/2537 (draft)
Research: Pieter Wuille published a proof, machine-checked in Lean, that BIP54's two timestamp rules together bound chain length for a given amount of work. delvingbitcoin.org/t/bounds-on-chain-length-with-bip-54-tโฆ
64-byte txs: Jeremy Rubin argued they may have legitimate uses (groups.google.com/g/bitcoindev/c/iCuq6bFKt5Y) and wrote up an alternative that invalidates merkle internal nodes instead (groups.google.com/g/bitcoindev/c/ZVDEzxG6Sq8). BIP54's rationale now acknowledges that option but still prefers the simple ban.
BIP54 tracker for forward-compatibility for miner coinbase locktimes: mainnet.observer/charts/transactions-coinbase-locktime-biโฆ
Other discussions:
Antoine Riard's response to Mark Friedenbach's objection that fixing timewarp forecloses forward blocks groups.google.com/g/bitcoindev/c/T9s8nflvlK0
An idea to split BIP54 into one BIP per fix, which the authors declined github.com/bitcoin/bips/pull/2175
Testnet5 (BIP95): enforces BIP54 from block 1 groups.google.com/g/bitcoindev/c/kGUMTxOvdJA/m/Eyx5FxQeAAAJ
bip54.org is updated to reflect these. -
Adam Back reposted
Blockstream
@Blockstream
Introducing our enterprise custody solution, developed in collaboration with Thales.
Our Secure Multi-Party Computation (Secure-MPC) runs the entire signing protocol inside Thales hardware security modules, so key material stays protected, even during signing. -
Adam Back reposted
Blockstream
@Blockstream
On the Blockstream Stage now: our CEO @adam3us on securing Bitcoin for a post-quantum future, with Frank Chaparro and Will Su of BlackRock, at @DAF_Global Forum in New York. ๐บ๐ธ
-
Adam Back reposted
Blockstream
@Blockstream
Happening now: @n1ckler of @blksresearch on the race to replace Bitcoin's signatures, in our workshop room at the @DAF_Global Forum in New York. ๐บ๐ธ
-
Adam Back reposted
Blockstream
@Blockstream
Introducing the new Blockstream: new look, same mission.
The future of finance, built on bitcoin. One site for everything we build for individuals, developers and institutions, across Enterprise, Consulting, Consumer, Developer, and Research.
blockstream.com -
Adam Back reposted
Blockstream
@Blockstream
In 30 minutes: our CEO @adam3us joins @JanvanEck3 of @vaneck_us and @danheld for a fireside chat on Bitcoin's role in the future of finance, on the Blockstream Stage.
10:40 AM ET, hosted by @DAF_Global in Midtown Manhattan. ๐บ๐ธ -
Adam Back reposted
Blockstream
@Blockstream
On the Blockstream Stage: our CEO @adam3us with @JanvanEck3 and @danheld on Bitcoin's role in the future of finance, at the Digital Assets Forum in New York. ๐บ๐ธ
-
Adam Back reposted
Blockstream
@Blockstream
Can today's hardware wallets make post-quantum signatures?
@n1ckler of @blksresearch tested hash-based SHRINCS on devices including @BlockstreamJade: yes, in a few seconds to a minute and a half.
In principle, no new hardware needed. From our workshop at @DAF_Global. ๐บ๐ธThis media couldn't be displayed. See it on the original post. -
Adam Back reposted
Blockstream
@Blockstream
The Digital Assets Forum opens today in New York.
@adam3us takes the Blockstream Stage at 10:40 AM and 2:25 PM ET, and our workshops run from 9:15 AM: enterprise custody with Thales, quantum security with @n1ckler, growth with @sagungarg, and strategy to delivery. ๐บ๐ธ -
Adam Back reposted
Blockstream
@Blockstream
In 30 minutes: @n1ckler, Director of @blksresearch, on the race to replace Bitcoin's signatures: quantum, AI and hash functions, and how our research prepares Bitcoin for a post-quantum future.
11:15 AM, in our workshop room @DAF_Global, New York. ๐บ๐ธ
Blockstream
@Blockstream
Bitcoin can get ahead of quantum.
@n1ckler, Director of @blksresearch, on the race to replace Bitcoin's signatures and how our research prepares Bitcoin for a post-quantum future.
Nov 13, 11:15 AM ET, Digital Assets Forum by @DAF_Global, New York. -
Adam Back reposted
Alistair Milne
@alistairmilne
Bifinex whale/s started buying again when Bitcoin went sub-$80k
>500 BTC today so far -
Adam Back reposted
-
Adam Back reposted
Digital Assets Forum
@DAF_Global
Could pension funds and insurers drive the next wave of Bitcoin adoption?
Thatโs the case Blockstream CEO Adam Back made in a recent Bitcoin Magazine interview.
What would an investment committee need to see before approving an allocation?
โBitcoinโs Role in the Future of Financeโ
@danheld (Held Media)
@adam3us (@Blockstream)
@JanvanEck3 (@vaneck_us)
November 13 | DAF New York
eblockchainconvention.com/digital-assets-forum-new-york/ -
Adam Back reposted
Rocket Strategy @RocketStrategy_
Blockstream CEO Adam Back says he's personally betting Bitcoin hits $1 million by 2028 ๐ฅ
He told CNBC about 95% of adoption is still to come, with pensions and mutual funds yet to buy ๐
$BTC #bitcoin -
Adam Back reposted
Daniel J. Bernstein
@hashbreaker
Posted new page "False computer-checked proofs" linking to 199 reports of soundness bugs in several important proof-checking programs: cr.yp.to/proofs/falseccp.html
-
Adam Back reposted
Blockstream App
@BlockstreamApp
You set the rules on a @Blockstream app 2FA Protected account.
Choose when 2FA expires: 6, 12 or 15 months. Set a threshold so smaller sends skip the second factor. Lose your 2FA and, once the timelock passes, an open-source tool gets your bitcoin back without relying on us. -
Adam Back reposted
Bitcoin Archive
@BitcoinArchive
Trezor finds drainers on three Safe 5s sold via CryptoBilis
โข Zero reports of user funds lost
โข Firmware 2.13.1 blocks implant batch
โข Reseller network cut by 80% -
Adam Back reposted
Bitcoin Monk X @BitcoinMonk_X
โIn a uncertain world, there is some certainty there.โ
โ Adam Back @adam3us
TFTC
@TFTC21
Adam Back told CNBC he's personally betting bitcoin hits $1 million by 2028.
His argument: 95% of adoption is still ahead, and pensions and mutual funds, the largest pools of capital, have yet to buy.This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Cris Reed
@CrisReed
Iโm still in the $1,000,000/coin camp by EOY 2033.
But Iโll take @adam3us time frame as well โฆThis media couldn't be displayed. See it on the original post. -
Adam Back reposted
Bitcoin Archive
@BitcoinArchive
ADAM BACK: โDips exist to transfer Bitcoin from weak hands to stronger hands.โ ๐ค
-
Adam Back reposted
Blockstream
@Blockstream
Multisig, minus the complexity. The @BlockstreamApp is the easy way to get started: add a second key to your bitcoin in a few taps, with nothing extra to set up and full self-custody.
Blockstream App
@BlockstreamApp
You set the rules on a @Blockstream app 2FA Protected account.
Choose when 2FA expires: 6, 12 or 15 months. Set a threshold so smaller sends skip the second factor. Lose your 2FA and, once the timelock passes, an open-source tool gets your bitcoin back without relying on us. -
Adam Back reposted
Cointelegraph
@Cointelegraph
๐ฅ TODAY: Adam Back says weโre in the early innings of a bull market cycle.
โPersonally I have a bet on Bitcoin to top a million by the end of the cycle, which is later in 2028.โ -
Adam Back reposted
Blockstream
@Blockstream
A full day of media in New York for our CEO @adam3us.
From sit-down interviews to live TV on @CNBCOvertime, he covered enterprise custody, SHRINCS signatures for a post-quantum future, and building on Bitcoin's UTXO model with Simplicity.This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Blockstream
@Blockstream
Bitcoin is improved gold: scarcity assured by proof of work, and far easier to send, verify and trade.
Our CEO @adam3us on @CNBCOvertime on why most institutional adoption is still to come, and his personal bet on bitcoin topping $1 million this cycle.This media couldn't be displayed. See it on the original post. -
Adam Back reposted
The Bitcoin Historian
@pete_rizzo_
BILLIONAIRE MICHAEL SAYLOR PERFECTLY EXPLAINS WHY TODAY'S MSCI RULING ABSOLUTELY DOES NOT MATTER AT ALL FOR #bitcoin OR MSTR
MSCI INDEXES DO NOT CONTROL REAL CAPITAL
THE MARKET WILL DECIDE, NOT A COMMITTEE
OTHER INDEXES WILL ADOPT DIGITAL ASSETS AND ALLOW THEM TO FLOURISH
WE ARE WATCHING ONE ROGUE ACTOR ATTACK AN EMERGING TECHNOLOGY
THEY WILL BE MADE IRRELEVANT ๐ฅ -
Adam Back reposted
Bitcoi999k๐ @bitcoi999
"95% of bitcoin:native adoption is still ahead, and pensions and mutual funds, the largest pools of capital, have yet to buy." @adam3us
-
Adam Back reposted
Global Politics, Tech & Business @GlobalPTBNews
TODAY: @adam3us says weโre in the early innings of a bull market cycle.
โPersonally I have a bet on Bitcoin to top a million by the end of the cycle, which is later in 2028.โ
News | Markets | YouTube -
Adam Back reposted
TFTC
@TFTC21
Adam Back told CNBC he's personally betting bitcoin hits $1 million by 2028.
His argument: 95% of adoption is still ahead, and pensions and mutual funds, the largest pools of capital, have yet to buy.This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Blockstream
@Blockstream
Our new Managing Director, EMEA, Oz Ozturk, went live with @FINTECHTVglobal from the floor of the New York Stock Exchange.
He talked about the new Blockstream Consulting service and how we help banks and asset managers build on Bitcoin, from strategy to delivery. -
Adam Back reposted
Blockstream
@Blockstream
Tonight in NYC, our CEO @adam3us joined @CNBCOvertime live to talk markets, bitcoin's 200-week moving average, and security in the age of AI.
-
Adam Back reposted
Blockstream
@Blockstream
Today in NYC our CEO @adam3us sat down for interviews with top tier media covering enterprise custody and post-quantum security for Bitcoin.
-
Adam Back reposted
The Bitcoin Historian
@pete_rizzo_
JUST IN: BILLIONAIRE RAY DALIO JUST SAID EVERYONE SHOULD BUY #bitcoin TO PROTECT THEMSELVES FROM AN UPCOMING US DEBT CRISIS
"THERE'S A SIGNIFICANT CHANCE GOVERNMENT BORROWING BECOMES A REAL PROBLEM"
"YOU NEED SOMETHING OUTSIDE THE SYSTEM"
YOU HAVE BEEN WARNED ๐ฅThis media couldn't be displayed. See it on the original post. -
Adam Back reposted
Bitcoin Security Consortium
@BTCconsortium
Quantum Computing 101
A Bitcoin Security Consortium report, in collaboration with Presidio Bitcoin. x.com/i/article/2120259915466088449 -
Adam Back reposted
The Bitcoin Historian
@pete_rizzo_
BREAKING: ๐ฉ๐ช $2.2 TRILLION DEUTSCHE BANK JUST OFFICIALLY LAUNCHED A #bitcoin CUSTODY SERVICE FOR ITS CLIENTS
GERMANY'S LARGEST BANK IS NOW ADOPTING BTC
THIS IS ABSOLUTELY MASSIVE ๐ฅThis media couldn't be displayed. See it on the original post. -
Adam Back reposted
Blockstream
@Blockstream
Three days to go. Secure custody, quantum readiness and growth on Bitcoin at the Digital Assets Forum in New York:
@adam3us on the Blockstream Stage
Enterprise custody, featuring @ThalesCloudSec
Quantum security, @n1ckler
Growth, @sagungarg
Strategy to delivery
All four workshops, times and speakers:
blockstream.com/daf-workshops/ -
Adam Back reposted
John Pfeffer
@jlppfeffer
I just published the latest version of โAn (Institutional) Investorโs Take on Cryptoassetsโ medium.com/john-pfeffer/an-institutional-investors-take-oโฆ
-
Adam Back reposted
John Pfeffer
@jlppfeffer
Link attached (it is also pinned to my profile). Or you can search my name on Medium and it comes up. ๐ค
John Pfeffer
@jlppfeffer
I just published the latest version of โAn (Institutional) Investorโs Take on Cryptoassetsโ medium.com/john-pfeffer/an-institutional-investors-take-oโฆ
-
Adam Back reposted
Alistair Milne
@alistairmilne
Polygon wants a hard fork to move 70 million POL out of five hack-linked wallets without the holders signing anything
47 million of it to an address Binance picks
Binance also lost 18,270 Bitcoin last month. Nobody's voting those back
That's a feature, not a bug -
Adam Back reposted
BMTV
@watchbmtv
Blockstream's Adam Back (@adam3us) on how bitcoin custody is evolving:
"The Fidelity ETF has its own custody, but others like BlackRock are using an independent custodian."
"The big custodians in the traditional world are starting to enter the Bitcoin custody world."This media couldn't be displayed. See it on the original post. -
Adam Back reposted
BMTV
@watchbmtv
Blockstream's Adam Back (@adam3us)on what banks want from bitcoin custody:
"They are just interested to explore ways to do secure custody, which types of custody technology are secure for the quantum future."
"They're interested in technical advice about how to secure Bitcoin and how to deliver tokenization."This media couldn't be displayed. See it on the original post. -
Adam Back reposted
stu ๐ฅช๐ฅ
@stutxo
banger post from cory on the mailing list: quantum landmines
after q-day, legacy spends would require restricted outputs with a 30-day delay
pre-q-day proof lets owners sweep their coins + attackerโs collateral
reactive security is cool (covenants btw)
groups.google.com/g/bitcoindev/c/ARMwWdWcz9A/m/iyl3oqdqBgAJ -
Adam Back reposted
Ryan Gentry
@RyanTheGentry
-
Adam Back reposted
John Pfeffer
@jlppfeffer
You could have just read my paper nine years ago and saved a lot of time. Or, you could just sell #eth and buy #btc. What a waste of talent and effort.
-
Adam Back reposted
Bitcoin News
@BitcoinNewsCom
Everyoneโs talking about Anakin
But what about Star Warsโ lessons about how fake fiat money is? -
Adam Back reposted
The Bitcoin Historian
@pete_rizzo_
๐ญ๐ฐ HONG KONG CONFIRMED IT WILL SUBMIT A MAJOR #bitcoin AND CRYPTO BILL BY YEAR-END
IT CREATES LICENSING FOR DEALING, CUSTODY, ADVISORY, AND MANAGEMENT
CHINA IS GETTING READY
THE GLOBAL RACE IS ON ๐ -
Adam Back reposted
Marty Bent
@MartyBent
โWhenever we want to add post-quantum security to Bitcoin, we get very significant downsides.โ
@n1ckler and @kudinov_mikhail on the trade-offs, from December 2025. Timely context for Blockstreamโs latest research update. -
Adam Back reposted
Guido Appenzeller
@appenz
For a broad set of tasks, the speedup of a quantum computer is polynomial at best.
Super cool result and this explains partially why we havenโt found many interesting applications of quantum computers.
psi.inc/research/aaronson-ambainis/ -
Adam Back reposted
Andrรฉ Dragosch, PhDโก @Andre_Dragosch
FWIW โ
We are seeing very significant orders in our European Bitcoin ETP this morning.
Few clips / large in size.
Institutional investors are scooping up cheap coinsโฆ -
Adam Back reposted
Rand Group
@randgroup
๐ #bitcoin hasn't been half today's price in about 2.5 years. Every past reading this high marked a cycle bottom
-
Adam Back reposted
Anita โก๐ณ๏ธโ๐
@anitaonl
Bitcoin is more than money. Itโs a tool for liberation. Iโve been fighting for it since 2017. Not for profits. Not for price predictions. This film tells why.
Watch and share it ๐ www.youtube.com/watch?v=P6z9xMVKDq8
with: @laurashin @LynAldenContact @adam3us @TrevorNcube @JoeNakamoto -
Adam Back reposted
ๅด่ฏดๅบๅ้พ
@wublockchain12
Adam Back๏ผๆบๆ้ ็ฝฎๅฐๆจๅจๆฏ็นๅธ็ฌฌไธๆณขๆฎๅๆตชๆฝฎ
2026 ๅนด 11 ๆ 1 ๆฅ๏ผBlockstream ้ฆๅธญๆง่กๅฎ Adam Back @adam3us ๅจ Bitcoin Magazine @BitcoinMagazine ้่ฎฟไธญ่กจ็คบ๏ผๆฏ็นๅธๅไธคๆณขๆฎๅๅๅซ็ฑไธชไบบๆ็ฟไธไนฐๅธใETF ๆจๅจ๏ผ็ฌฌไธๆณขๅฐ้่ฟไธไธ่ต็ฎกๆธ ้ๆฉๅคง๏ผไฝๅฐๆชๅ จ้ขๅฐๆฅใ
้จๅๅคงๅๆ่กๅทฒๅจ็คบ่ๆ่ต็ปๅไธญๅปบ่ฎฎ้ ็ฝฎ 2% ่ณ 4% ็ๆฏ็นๅธ๏ผๆดๅคไบบๅฐ้่ฟๅ ฑๅๅบ้ใๅ ป่ๅบ้ๅไฟ้ฉไบงๅ้ดๆฅ่ทๅพๆๅฃ๏ผๆฏ็นๅธ่ดขๅบๅ ฌๅธไนๆฏๅ ถไธญไธ็ฏใ
ๆฅๆบ๏ผBitcoin MagazineThis media couldn't be displayed. See it on the original post. -
Adam Back reposted
-
Adam Back reposted
Hasheur
@PowerHasheur
Insolite: Un dev de Bitcoin Core vient de proposer une idรฉe assez maligne et drรดle contre la menace quantique.
Au lieu de geler les vieux BTC, il veut piรฉger les voleurs.
Petit rappel du problรจme : un ordi quantique pourrait retrouver la clรฉ des vieux wallets exposรฉs, environ 7 millions de BTC. Une fois la clรฉ en main, le voleur signe exactement comme le propriรฉtaire. Le rรฉseau ne ferait alors pas la diffรฉrence.
La proposition de Cory Fields : pour dรฉplacer un de ces vieux BTC il faudrait dโabord bloquer la mรชme somme en caution pendant quelques semaines.
Pendant ce dรฉlai, le vrai propriรฉtaire pourrait sortir une preuve quโil a cachรฉe ร lโavance. Sโil le fait, il garde ses BTC et il rรฉcupรจre en plus la caution du voleur.
Le voleur ne sait donc jamais si le wallet quโil attaque est piรฉgรฉ. Chaque tentative peut lui coรปter son propre argent.
Forcรฉment des limites : รงa ne marche que si tu as encore tes clรฉs. Les BTC perdus et ceux de Satoshi, resteraient exposรฉs. Et pour lโinstant ce nโest quโune proposition sur la liste de discussion des devs. Puis il faut donc avoir des bitcoins pour libรฉrer ses propres bitcoinsโฆ bref semble compliquรฉ mais lโangle : ajoutons un risque ร lโattaquant, mโa fait rire -
Adam Back reposted
Blockstream App
@BlockstreamApp
Watch the next block fill from your phone. Every pending transaction sized by weight, coloured by fee band, updating live.
blockstream.info -
Adam Back reposted
Blockstream
@Blockstream
Download the Blockstream App today to get full self-custody of Bitcoin from day one, whether you're buying in app or sending from an exchange.
blockstream.com/app -
Adam Back reposted
Blockstream
@Blockstream
Blockstream CEO @adam3us explains how self-sovereignty in Bitcoin starts with private keys.
-
Adam Back reposted
Blockstream
@Blockstream
The easiest first step into multisig needs nothing more than the phone in your pocket.
Set up a 2FA Protected account in the @BlockstreamApp and approve sends with a second factor you choose.
Blockstream App
@BlockstreamApp
The easiest way into multisig is a 2FA Protected account in the @Blockstream app.
Approve sends with your choice of second factor: SMS, email or an authenticator app. No extra hardware to set up. -
Adam Back reposted
Luke Martin
@VentureCoinist
This media couldn't be displayed. See it on the original post.
Watcher Guru
@WatcherGuru
JUST IN: Jim Cramer says the market is going to "boom."
-
Adam Back reposted
FRANCIS โ๏ธ BULLBITCOIN.COM
@francispouliot_
Introducing Payjoin trading : when a user of BULL wallet buys, sells or pays someone via the Bull Bitcoin exchange integration, both the wallet and exchange will now automatically collaborate to create a payjoin transaction wit by default ๐ถ๏ธ
www.bullbitcoin.com/blog/payjoin-trading -
Adam Back reposted
Blockstream
@Blockstream
In Q3 security set the agenda.
@blksresearch co-wrote the draft SHRINCS BIP. Jade, Core Lightning and Elements shipped security fixes. We rebuilt Blockstream Explorer, launched 0-conf for @Liquid_BTC integrators and opened the Swaps beta.
Read more:
blog.blockstream.com/blockstream-quarterly-update-q3-2026/ -
Adam Back reposted
Bitcoin News
@BitcoinNewsCom
NEW: @BullBitcoin just became the first exchange to make every on-chain buy and sell a Payjoin by default.
Your coins get merged automatically and chain analysis gets harder.
Here's how it works ๐
bitcoinnews.com/p/bull-bitcoin-payjoin-trading-utxo-consoโฆ -
Adam Back reposted
Blockstream
@Blockstream
One static address, unlinkable payments, many signers. @olkurbatov of @blksresearch explains Silent Payments for multiparty wallets with @bitcoinoptech, from 41:18.
See him live on the Main Stage at @btcplusplus Seoul, 2:00 PM KST today. ๐ฐ๐ทThis media couldn't be displayed. See it on the original post. -
Adam Back reposted
Blockstream
@Blockstream
LIVE in 30 minutes: @olkurbatov of @blksresearch takes the Main Stage at @btcplusplus Seoul. ๐ฐ๐ท
Silent Payments let you share one static address while every payment lands somewhere new and unlinkable. Making that work for multiparty wallets is a harder problem. -
Adam Back reposted
Blockstream
@Blockstream
We're the Diamond Sponsor of the @DAF_Global Digital Assets Forum in New York on Nov 13. Get 25% off tickets with code Bl0ckstr3am25.
Hear @adam3us on the Blockstream Stage, plus our sessions on custody, post-quantum security, growth and deployment.
eblockchainconvention.com/digital-assets-forum-new-york/ -
Adam Back reposted
THE JACK MALLERS SHOW
@jackmallersshow
Jack explains why Bitcoin's proof of work began as a 1997 plan to put spammers out of business:
This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Alex ๐ฝ
@AlexesNakamoto
We are back โฟabe!
-
Adam Back reposted
yellow.๐๐
@ICOffenderII
Is Elon Musk Satoshi Nakamoto? I didn't guess. I measured the writing. Full stylometry data coming soon.
-
Adam Back
@adam3us
$STRC game on!
-
Adam Back reposted
Matt Hougan
@Matt_Hougan
There are no sellers left in crypto.
* 3.7% inflation print >> Doesn't matter
* AI bubble bursting >> Doesn't matter
* Binance hack >> Doesn't matter
* Election tsunami >> Doesn't matter -
Adam Back reposted
Core Lightning โก๏ธ
@Core_LN
Core Lightning 26.06.10 is out, and every node runner should upgrade.
This point release includes security fixes. Verify the signatures and install it as soon as possible.
github.com/ElementsProject/lightning/releases/tag/v26.06.10 -
Adam Back
@adam3us
-
Adam Back reposted
PsyopAnime
@PsyopAnime
Jim Cramer is a legend
This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Blockstream
@Blockstream
Security fixes are out for @Core_LN. Keep your node and your channels safe: upgrade to 26.06.10 today.
Core Lightning โก๏ธ
@Core_LN
Core Lightning 26.06.10 is out, and every node runner should upgrade.
This point release includes security fixes. Verify the signatures and install it as soon as possible.
github.com/ElementsProject/lightning/releases/tag/v26.06.10 -
Adam Back reposted
Blockstream Jade
@BlockstreamJade
Dozens of AI scans and human reviews hit the Jade source these past months. Every report checked, deduplicated, and scoped. Full thanks to everyone who contributed are in the blog below, this is what makes open source work.
This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Blockstream Jade
@BlockstreamJade
Find Jade Plus in the Blockstream Store: store.blockstream.com/products/jade-plus
-
Adam Back reposted
Blockstream
@Blockstream
Requests to join our workshops at the @DAF_Global Digital Assets Forum in New York close Friday, Nov 6. A Forum pass is required.
No Forum pass yet? Get 25% off tickets with code Bl0ckstr3am25: eblockchainconvention.com/digital-assets-forum-new-york/ -
Adam Back reposted
Blockstream
@Blockstream
Custody, post-quantum security, growth and deployment, all on November 13 in New York. Grab your Forum pass at 25% off, then request your workshop seats by Friday.
Blockstream
@Blockstream
Requests to join our workshops at the @DAF_Global Digital Assets Forum in New York close Friday, Nov 6. A Forum pass is required.
No Forum pass yet? Get 25% off tickets with code Bl0ckstr3am25: eblockchainconvention.com/digital-assets-forum-new-york/ -
Adam Back reposted
Blockstream App
@BlockstreamApp
The full breakdown of 2FA Protected 2-of-2 and 2-of-3 accounts:
blog.blockstream.com/multisig-is-back-in-the-blockstream-โฆ -
Adam Back reposted
Blockstream App
@BlockstreamApp
Sending from a 2FA Protected account looks like any other send. Check the address, amount and fee, then slide to send.
By default two keys sign: one on your device, and one @Blockstream holds that only signs once you approve with your second factor. -
Adam Back reposted
Samson Mow
@Excellion
The Wheel of Shitcoin Samsara. โญ๏ธ
This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Warren Togami
@wtogami
Real life: My developer friend was recently compromised by an exercise during a fake job interview. They were asked to download a tarball then run git operations within it as part of the live interview.
Git security models prevent hooks from transferring during a standard git clone (since hooks live in the .git/hooks directory, which is local to a repository and ignored during remote fetches). Receiving a project as a ZIP file, tarball, or untrusted directory however bypasses this protection allowing malicious code to execute during seemingly ordinary git commands. -
Adam Back reposted
Blockstream
@Blockstream
Generate your own recovery phrase with dice, and let @BlockstreamJade calculate a valid final word.
This media couldn't be displayed. See it on the original post. -
Adam Back reposted
NVK
@nvk
All projects are overwelmend with disclosures from ai review right now. There is also alot of noise.
Consider a pgp encrypted formal disclosure and give people time. Explain the severity to the best of your abilities. Also consider opening a CVE.
1. Do not disclosure publically.
2. DMs with un-detailed opinions are neither responsible nor disclosures.
3. Consider asking your bot to make the disclosures more consise and less slop.
4. Consider having other models do secondary reviews for severity double check.
Mr.Hodl
@MrHodl
Security folks.. what do you do when you privately report a bug, the report sits untouched, and the person you follow up with blocks you?
Wait it out? Set a 90-day disclosure date? Something else? -
Adam Back reposted
AQUA Wallet
@AquaBitcoin
The Liquid Network is so back. ๐ง
Every single @Liquid_BTC is fully backed 1:1 again. ๐ -
Adam Back reposted
GTAmemes
@GTAmemesSOL
New GTA VI Mission: Bitcoin dips are for buying!
This media couldn't be displayed. See it on the original post. -
Adam Back reposted
TFTC
@TFTC21
Blockstream moves another 300 BTC into Liquid, cutting the backing shortfall to 250 BTC.
-
Adam Back reposted
Michelle O
@michelleo_21mil
โ๏ธGood morning Bitcoinersโ๏ธ
How it feels waiting for the bull run to resumeโฆ -
Adam Back reposted
FRANCIS โ๏ธ BULLBITCOIN.COM
@francispouliot_
Another 300 BTC has been added to the Liquid Network peg wallet. Out of the 600 BTC deficit, 250 BTC remain outstanding.
-
Adam Back reposted
JAN3
@JAN3com
The @Liquid_BTC Network reserves are officially back to a 1:1 peg. ๐ฅ
We never doubted it would be fully restored. That's why we continued fulfilling all Lightning swaps at a 1:1 ratio from our own reserves the entire time. ๐งก๐งThis media couldn't be displayed. See it on the original post. -
Adam Back
@adam3us
prior fork context for bip110 fork supporters: @francispouliot_ masterclass on bitcoin reality. yet again: attempts to impose your views on bitcoin get market rejected. @_podconf memes about BIG BITCOIN are well meaning: for you to understand immutability
FRANCIS โ๏ธ BULLBITCOIN.COM
@francispouliot_
So, you're listening to Roger Ver and, as a anti-establishment skeptic, you think his "bitcoin is hijacked" spiel makes a lot of sense?
You've heard that Bitcoin was "co-opted" by Epstein, powerful corporate elites, the deep state or the US government?
Listen to this.This media couldn't be displayed. See it on the original post.
Adam Back
@adam3us
it's not necessarily about the payload, attempts to override consensus, and immutability the market WILL go to war over, even if people believe you mean well. bip110 failed the first gate hard: technical proposal was ridiculously broken. rather than listen they tried to force it.
-
Adam Back reposted
Luca Vaccaro
@vaccarobtc
Backember
Bitcoin Archive
@BitcoinArchive
Bitcoin sidechain Liquid Network is now FULLY BACKED.
The remaining 250 BTC have been covered by the Federation.
Onwards!This post is unavailable. See it on X. -
Adam Back reposted
Arnab Naskar @stokr
@Arnab_Naskarr
@Liquid_BTC peg restored. Congrats to the federation and @Blockstream on getting this done the right way.
-
Adam Back reposted
liquid.network
@liquidexplorer
Adam โwe are soโ Back
Samson Mow
@Excellion
Weโre so Back.
L-BTC is 1:1 with BTC.
mempool.space/tx/531088ee8be6deadfd4fe1d1a021d9bd17d8e39cโฆ -
Adam Back reposted
MADEX
@spacebull
-
Adam Back reposted
Blockstream
@Blockstream
The @Liquid_BTC Network's bitcoin reserves are fully restored: 1:1 BTC backing for all LBTC, verifiable by anyone running a Liquid node.
Liquid Network ๐
@Liquid_BTC
Update from the Liquid Federation:
The Liquid Federation is pleased to announce that the networkโs bitcoin reserves have been fully restored, reestablishing 1:1 BTC backing for all LBTC.
This follows the restoration of BTC<>LBTC swaps several weeks ago, which have since allowed users to move between Bitcoin and Liquid at a 1:1 rate through participating swap providers. Together, these milestones represent significant progress in the Federationโs recovery efforts and reaffirm its commitment to the long-term security, stability and resilience of the Liquid Network.
As always, the networkโs bitcoin reserves are independently verifiable. Users operating their own Liquid nodes can directly verify the Federationโs Proof of Reserves, while reserve balances and network activity can be monitored through the public dashboard at liquid.network.
We extend our sincere appreciation to the Bitcoin community, Liquid users, and ecosystem partners for their patience, understanding, and continued engagement throughout the recovery process. Your support and involvement has been instrumental as we worked to restore the networkโs reserves and strengthen its underlying infrastructure.
Strengthening the Liquid Network for the Future
Looking ahead, the Federation is advancing several important initiatives designed to strengthen the networkโs long-term security, governance, and operational resilience.
These efforts include modernizing the governance structure, introducing clearer responsibilities and oversight, and implementing additional technical and operational safeguards to further protect the network and its participants.
More details on these initiatives and the Federationโs next steps will be shared in the coming weeks.
Restoring full bitcoin backing marks an important milestone, but our work continues. The Federation remains committed to building on the progress of recent years, advancing Liquidโs development, and strengthening the networkโs resilience and accessibility for all participants. -
Adam Back reposted
Artem Chystiakov
@Arvolear
Liquid peg restored.
Time to discover Simplicity.
So much to build.
Liquid Network ๐
@Liquid_BTC
Update from the Liquid Federation:
The Liquid Federation is pleased to announce that the networkโs bitcoin reserves have been fully restored, reestablishing 1:1 BTC backing for all LBTC.
This follows the restoration of BTC<>LBTC swaps several weeks ago, which have since allowed users to move between Bitcoin and Liquid at a 1:1 rate through participating swap providers. Together, these milestones represent significant progress in the Federationโs recovery efforts and reaffirm its commitment to the long-term security, stability and resilience of the Liquid Network.
As always, the networkโs bitcoin reserves are independently verifiable. Users operating their own Liquid nodes can directly verify the Federationโs Proof of Reserves, while reserve balances and network activity can be monitored through the public dashboard at liquid.network.
We extend our sincere appreciation to the Bitcoin community, Liquid users, and ecosystem partners for their patience, understanding, and continued engagement throughout the recovery process. Your support and involvement has been instrumental as we worked to restore the networkโs reserves and strengthen its underlying infrastructure.
Strengthening the Liquid Network for the Future
Looking ahead, the Federation is advancing several important initiatives designed to strengthen the networkโs long-term security, governance, and operational resilience.
These efforts include modernizing the governance structure, introducing clearer responsibilities and oversight, and implementing additional technical and operational safeguards to further protect the network and its participants.
More details on these initiatives and the Federationโs next steps will be shared in the coming weeks.
Restoring full bitcoin backing marks an important milestone, but our work continues. The Federation remains committed to building on the progress of recent years, advancing Liquidโs development, and strengthening the networkโs resilience and accessibility for all participants. -
Adam Back reposted
Blockstream
@Blockstream
Jonas co-authored our paper on hash-based signatures: post-quantum security built on the hash functions Bitcoin already trusts.
Seats are limited. Register for his presentation and explore our other workshops at @DAF_Global:
blockstream.com/daf-workshops/
Blockstream
@Blockstream
Bitcoin can get ahead of quantum.
@n1ckler, Director of @blksresearch, on the race to replace Bitcoin's signatures and how our research prepares Bitcoin for a post-quantum future.
Nov 13, 11:15 AM ET, Digital Assets Forum by @DAF_Global, New York. -
Adam Back reposted
Maximus Maximalistus
@maximalistus
"When the going gets tough, the tough get going." - Adam Back
Adam Back
@adam3us
-
Adam Back reposted
Luca Vaccaro
@vaccarobtc
1 = 1
Adam Back
@adam3us
-
Adam Back reposted
Liquid Network ๐
@Liquid_BTC
Update from the Liquid Federation:
The Liquid Federation is pleased to announce that the networkโs bitcoin reserves have been fully restored, reestablishing 1:1 BTC backing for all LBTC.
This follows the restoration of BTC<>LBTC swaps several weeks ago, which have since allowed users to move between Bitcoin and Liquid at a 1:1 rate through participating swap providers. Together, these milestones represent significant progress in the Federationโs recovery efforts and reaffirm its commitment to the long-term security, stability and resilience of the Liquid Network.
As always, the networkโs bitcoin reserves are independently verifiable. Users operating their own Liquid nodes can directly verify the Federationโs Proof of Reserves, while reserve balances and network activity can be monitored through the public dashboard at liquid.network.
We extend our sincere appreciation to the Bitcoin community, Liquid users, and ecosystem partners for their patience, understanding, and continued engagement throughout the recovery process. Your support and involvement has been instrumental as we worked to restore the networkโs reserves and strengthen its underlying infrastructure.
Strengthening the Liquid Network for the Future
Looking ahead, the Federation is advancing several important initiatives designed to strengthen the networkโs long-term security, governance, and operational resilience.
These efforts include modernizing the governance structure, introducing clearer responsibilities and oversight, and implementing additional technical and operational safeguards to further protect the network and its participants.
More details on these initiatives and the Federationโs next steps will be shared in the coming weeks.
Restoring full bitcoin backing marks an important milestone, but our work continues. The Federation remains committed to building on the progress of recent years, advancing Liquidโs development, and strengthening the networkโs resilience and accessibility for all participants. -
Adam Back reposted
FRANCIS โ๏ธ BULLBITCOIN.COM
@francispouliot_
1:1
FRANCIS โ๏ธ BULLBITCOIN.COM
@francispouliot_
Another 300 BTC has been added to the Liquid Network peg wallet. Out of the 600 BTC deficit, 250 BTC remain outstanding.
-
Adam Back reposted
FRANCIS โ๏ธ BULLBITCOIN.COM
@francispouliot_
Holy shit
-
Adam Back
@adam3us
-
Adam Back reposted
SideSwap
@side_swap
Liquid peg update
Another 300 BTC went into the Liquid Federation peg wallet today, after 2.5 BTC on 27 Oct and 50 BTC on 28 Oct.
Reserve now ~4,018 BTC against ~4,268 L-BTC outstanding (liquid.network). We hope to see the network fully restored soon. -
Adam Back reposted
Star_OKX
@star_okx
This cartoon makes me feel both proud and under tremendous pressure.
I will never claim that OKX is absolutely safe or immune to attacks. No company can honestly make that promise.
What I can say is that OKX has always treated security and the protection of customer assets as our highest priority. Our 13-year track record reflects more than a decade of continuous investment, engineering, operational discipline, and hard-earned experience.
We take security threats seriously and professionallyโnot as a marketing opportunity.
Behind the scenes, we have built extensive layers of proprietary technology, internal security systems, strategies, frameworks, penetration testing, and independent audits. Much of this infrastructure cannot be disclosed publicly for security reasons. But these capabilities are constantly being tested, challenged, and improved.
Hereโs something I can share: since the recent Binance security incident, the entire OKX team has been working just as hard and staying just as busy as the teams directly responding to the attack.
Not because OKX was compromised. But because an attack on one major exchange is a warning to the entire industry.
While some may see such moments as opportunities to launch promotional campaigns, generate traffic, or compete for market share, our priority has been different.
Our teams have been working around the clock on four critical areas:
1. Tracking stolen funds in real time.
Monitoring the movement of funds associated with the incident with second-level latency, identifying suspicious addresses and transactions, and taking available measures to prevent stolen funds from being laundered through OKX Exchange or our Web3 DEX aggregator.
2. Strengthening market risk controls.
Assessing the potential market impact of the incident, tightening risk controls where necessary, and preparing for liquidity shocks or cascading liquidations that could threaten users and the broader market.
3. Analyzing emerging attack techniques.
Studying the attack patterns, potential vulnerabilities, and methodologies involved, including threats to software development supply chains and the rapidly evolving security risks introduced by AI coding agents and their dependencies.
4. Challenging our own security assumptions.
Using the lessons from this incident to conduct a fundamental review of our internal controls, access management, wallet infrastructure, and security architecture.
We donโt assume that what protected us yesterday will necessarily protect us tomorrow.
Security is never a finished project. It is a continuous responsibility that requires humility, vigilance, investment, and execution.
We donโt choose to be the loudest when another company is under attack. We choose to work harder to protect our customers and strengthen the resilience of the entire industry.
Competition should drive better products and services. Security should bring the industry together.
Protecting customer assets is our first responsibility. And we will never take your trust for granted. -
Adam Back reposted
Scoresby
@BitcoinScoresby
Listen to @halfin sing about running bitcoin:
๐Sound on! -
Adam Back reposted
stu ๐ฅช๐ฅ
@stutxo
rounding off bitcoin research week with the roose goose, talking covenants at the bike shed
This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Scoresby
@BitcoinScoresby
Happy Whitepaper Day!
๐ sound on -
Adam Back reposted
Blockstream
@Blockstream
On this day in 2008, Satoshi published the Bitcoin white paper.
Two months earlier, Satoshi emailed @adam3us to ask how to cite Hashcash. Bitcoin builds on its proof-of-work so no one has to be in charge.
Eighteen years on, Bitcoin is still the best place to build. -
Adam Back reposted
Bitstein
@bitstein
On October 31, 2008, the mysterious Satoshi Nakamoto appeared on the Cryptography mailing list to share his vision for โ#bitcoin: A Peer-to-Peer Electronic Cash System.โ
The world would never be the same again.This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Unchained
@unchained
On this day 18 years ago, the Bitcoin whitepaper was published. But it didn't come out of nowhere.
-
Adam Back
@adam3us
happy bitcoin white paper day. 18 years.
onwards and upwards. -
Adam Back reposted
Documenting โฟitcoin ๐
@DocumentingBTC
On this day in history, 18 years ago, Satoshi Nakamoto published the Bitcoin Whitepaper.
This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Alexandre Laizet โก๏ธ
@AlexandreLaizet
Happy Bitcoin Whitepaper Dayโก๏ธ
Thank you, Satoshi ๐
Link: bitcoin.org/bitcoin.pdf -
Adam Back reposted
Daniela Fonseca Viteri
@dannyfonse
Happy Bitcoin Whitepaper Day! ๐
And of course, a familiar name in the references: @adam3us and his Hashcash! ๐ -
Adam Back reposted
Blockstream Jade
@BlockstreamJade
Self-custody is the foundation of Bitcoin.
Jade keeps your keys offline and your stack sovereign. Fully open-source so anyone can verify the security model.
Limited-time:
15% off all Jades.
Code: NYKNYC
store.blockstream.com/products/jade-plus -
Adam Back reposted
PsyopAnime
@PsyopAnime
Binance hack was the greatest robbery of all time
This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Jeff Lunglhofer (Lunglhofer.eth)
@JLunglhofer
Bitcoin Core is some of the most reviewed code in the world.
We were curious how our frontier AI model would handle it. Last month we ran 16 agents across 5 of the top models for a week to look for issues in Bitcoin Core v32.0rc1
Impressively, they surfaced two minor items - both now disclosed responsibly.
Agentic teams have been a huge unlock so far for our security efficiency. They're also remarkable to watch. -
Adam Back reposted
Blockstream
@Blockstream
Gold mines can work three shifts and crank up supply when the price moons. Bitcoin can't do that.
@adam3us on why Bitcoin is harder money than gold: inelastic supply, no competing industrial use, and a new supply rate already lower than gold's. -
Adam Back reposted
AQUA Wallet
@AquaBitcoin
The Liquid Network is making steady progress on its staged recovery roadmap alongside enhanced security controls.
AQUA users can currently execute 1:1 swaps between native Bitcoin and @Liquid_BTC directly in AQUA Wallet, following the re-enablement of BTC โ L-BTC swaps last week.
The community can track the restoration progress transparently through the official auditable proof of reserves at liquid.network.
Liquid Network ๐
@Liquid_BTC
Update from the Federation:
BTC<>LBTC swaps were re-enabled last week as part of Liquidโs staged recovery. Users can once again swap between BTC on Bitcoin and LBTC on Liquid at 1:1 through participating providers, including @AquaBitcoin, @BULLBITCOIN_ and @side_swap. These providers collectively accounted for 99% of peg-out volume prior to the incident.
Normal Federation peg-out operations remain subject to enhanced operational controls while security hardening continues and the independent security audit nears completion.
The community can track progress toward restoring full 1:1 BTC backing for LBTC through Liquidโs auditable Proof of Reserves at liquid.network.
Samson Mow
@Excellion
A test transaction for 2.5 BTC was sent to the @Liquid_BTC Federation wallet, reducing the shortfall to 600 BTC. The remaining 600 BTC will be moved to the wallet in the coming days. All network operations are continuing normally.
mempool.space/address/bc1qdlld6antmv4xug242ed83q7k4rqw50cโฆ -
Adam Back reposted
Blockstream App
@BlockstreamApp
Or start with a 2of2 2FA Protected account, no backup key needed. On Bitcoin, pick a 6, 12 or 15 month timelock.
Want the backup key later? Add a 2of3 account and send your coins to it. -
Adam Back reposted
Blockstream App
@BlockstreamApp
Easily access a higher level of Bitcoin security. Multisig is back in the Blockstream app.
2of3 with 2FA: you hold two of the three keys. One on your phone, a backup offline on @BlockstreamJade or @Blockstream Metal. Blockstream cosigns when you authorize with a 2FA code. -
Adam Back reposted
Grant Cardone
@GrantCardone
Bitcoin will never break its all-time high again." โ Jason Calacanis
Jason, I'll bet you $1,000,000 it will break its ATH. Here are the terms:
Bitcoin hits or exceeds $126,210.50 on or before October 28, 2028, 12PM PST
Iโm happy to trust you to pay or if you prefer we can each escrow the dollars with independent party.
The bet is either settled when Bitcoin hits the ATH or on October 28, 2028.
@jason Do we have a bet? -
Adam Back reposted
Blockstream
@Blockstream
Help someone you care about start with Bitcoin without all the pressure on them.
Blockstream Jade
@BlockstreamJade
You can be the one who gets a friend or family member into Bitcoin properly. @Blockstream Jade creates a separate recovery phrase for their wallet, and nothing of yours is exposed.
Keep the index number and you stay their safety net.
Watch how BIP85 recovery phrases work. -
Adam Back reposted
Blockstream App
@BlockstreamApp
Update the Blockstream app to get it: blockstream.com/app/
-
Adam Back reposted
Blockstream App
@BlockstreamApp
It's been a long time coming. Coin selection is now in the Blockstream app on iOS, Android and desktop.
Choose exactly which coins each payment spends. Keep coins from different sources apart, combine small ones when fees are low, and decide what each transaction reveals. -
Adam Back reposted
Blockstream
@Blockstream
Your bitcoin, your choice of coins.
Keep your payments more private and your fees lower, now on every device.
Blockstream App
@BlockstreamApp
It's been a long time coming. Coin selection is now in the Blockstream app on iOS, Android and desktop.
Choose exactly which coins each payment spends. Keep coins from different sources apart, combine small ones when fees are low, and decide what each transaction reveals. -
Adam Back reposted
Blockstream
@Blockstream
Stronger security for your bitcoin without giving up control. No single key can move it, and you can always recover without us.
Multisig is back in the Blockstream app.
Blockstream App
@BlockstreamApp
Easily access a higher level of Bitcoin security. Multisig is back in the Blockstream app.
2of3 with 2FA: you hold two of the three keys. One on your phone, a backup offline on @BlockstreamJade or @Blockstream Metal. Blockstream cosigns when you authorize with a 2FA code. -
Adam Back reposted
Blockstream
@Blockstream
An update from the Liquid Federation on the latest progress in the @Liquid_BTC Network's recovery.
Liquid Network ๐
@Liquid_BTC
Update from the Federation:
BTC<>LBTC swaps were re-enabled last week as part of Liquidโs staged recovery. Users can once again swap between BTC on Bitcoin and LBTC on Liquid at 1:1 through participating providers, including @AquaBitcoin, @BULLBITCOIN_ and @side_swap. These providers collectively accounted for 99% of peg-out volume prior to the incident.
Normal Federation peg-out operations remain subject to enhanced operational controls while security hardening continues and the independent security audit nears completion.
The community can track progress toward restoring full 1:1 BTC backing for LBTC through Liquidโs auditable Proof of Reserves at liquid.network.
Samson Mow
@Excellion
A test transaction for 2.5 BTC was sent to the @Liquid_BTC Federation wallet, reducing the shortfall to 600 BTC. The remaining 600 BTC will be moved to the wallet in the coming days. All network operations are continuing normally.
mempool.space/address/bc1qdlld6antmv4xug242ed83q7k4rqw50cโฆ -
Adam Back reposted
Wicked
@w_s_bitcoin
There are now officially fewer than 900,000 bitcoin left to mine.
This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Blockstream Help
@BlockstreamHelp
๐จ Phishing alert
Emails from info@blockstreamapp[.]org linking to blockstreamapp[.]org are not from Blockstream. Don't click the link.
Blockstream will never ask for your recovery phrase or PIN, or ask you to send funds.
Only trust links on blockstream.com. -
Adam Back reposted
Blockstream
@Blockstream
How 2FA Protected accounts work: blog.blockstream.com/multisig-is-back-in-the-blockstream-โฆ
-
Adam Back reposted
Liquid Network ๐
@Liquid_BTC
Update from the Federation:
BTC<>LBTC swaps were re-enabled last week as part of Liquidโs staged recovery. Users can once again swap between BTC on Bitcoin and LBTC on Liquid at 1:1 through participating providers, including @AquaBitcoin, @BULLBITCOIN_ and @side_swap. These providers collectively accounted for 99% of peg-out volume prior to the incident.
Normal Federation peg-out operations remain subject to enhanced operational controls while security hardening continues and the independent security audit nears completion.
The community can track progress toward restoring full 1:1 BTC backing for LBTC through Liquidโs auditable Proof of Reserves at liquid.network.
Samson Mow
@Excellion
A test transaction for 2.5 BTC was sent to the @Liquid_BTC Federation wallet, reducing the shortfall to 600 BTC. The remaining 600 BTC will be moved to the wallet in the coming days. All network operations are continuing normally.
mempool.space/address/bc1qdlld6antmv4xug242ed83q7k4rqw50cโฆ -
Adam Back reposted
Blockstream
@Blockstream
Silent Payments let you share one static address while every payment lands somewhere new and unlinkable. Making that work for multiparty wallets is a harder problem.
@olkurbatov of @blksresearch takes it on at @btcplusplus Seoul, November 5-6. ๐ฐ๐ท
bitcoin++ @ seoul, nov 5-6 ๐ฐ๐ท
@btcplusplus
๐: Oleksandr Kurbatov (@olkurbatov) of Blockstream Research has been working on a difficult problem: Silent Payments for Multiparty Wallets. Join us in Seoul next month for the deets
-
Adam Back reposted
BlankSpaces
@CladeHaggel
-
Adam Back reposted
MARS SPITS BARS ๐ฅ
@marsspitsbarz
.@Pledditor said heโd mute me if I make another Big Bitcoin meme
so i made thisThis media couldn't be displayed. See it on the original post. -
Adam Back reposted
Alex ๐ฝ
@AlexesNakamoto
BTC hits $1M. Strategy's earnings call:
This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Bitcoin Security Consortium
@BTCconsortium
40+ organizations across Bitcoin and open-source security including Consortium members Anchorage Digital, ARK Invest, Block, Blockstream, Coinbase, Galaxy, and Strategy called on frontier AI labs to give qualified defenders early access to their strongest cyber-capable models.
Bitcoin Policy Institute
@bitcoinpolicy
Today, Bitcoin Policy Institute and a broad coalition from across the digital-asset ecosystem are publishing an open letter calling on the worldโs leading AI labs to provide qualified open-source defenders with trusted access to frontier AI models.
The past several weeks have made the need for this abundantly clear. The people defending digital-asset infrastructure and open-source software need access to the latest AI capabilities to perform comprehensive security reviews and stay ahead of increasingly sophisticated adversaries.
The coalition includes open-source development organizations, major custodians, treasury companies, payment services, security firms, capital allocators, and others whose businesses and customers depend on the integrity of open-source infrastructure and libraries.
Open-source defenders often occupy the least privileged position in the AI security landscape. They have limited access to the strongest internal cyber models and are frequently blocked by guardrails when using publicly available frontier systems for legitimate security research. As a result, they often resort to less capable open-weight alternatives.
We are urging frontier AI labs to establish a clear, trusted pathway for qualified open-source and digital asset defenders to access their strongest capabilities, with sufficient compute and secure environments to conduct meaningful security reviews. Frontier AI could become one of the most powerful defensive technologies ever developed, but only if defenders get fair access to those systems.
Itโs time to give defenders the tools they deserve.
Read the open letter, add your organization, or sign as an individual on our website at btcpolicy.org/ailetter -
Adam Back reposted
Blockstream
@Blockstream
Blockstream is making headlines in Lugano, from our new office to quantum security.
Blockstream Consulting Services gives Swiss banks and asset managers direct access to our experts.
Check out coverage from @CdT_Online, @finews_ch and @BitcoinMagazine featuring @adam3us. ๐จ๐ญ -
Adam Back reposted
Blockstream
@Blockstream
On the P2P Stage now at @LuganoPlanB: @n1ckler, Director of @blksresearch, on the race to replace Bitcoin's signatures: quantum, AI and hash functions.
-
Adam Back reposted
Blockstream
@Blockstream
At @LuganoPlanB, @blksresearch Director Jonas Nick (@n1ckler) answered the question everyone's asking: will AI break Bitcoin's cryptography?
Spoiler alert: no.This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Bitcoin Dev Project
@Bitcoin_Devs
Hash-Based Signature Schemes Explained
Part 1: WOTS (Winternitz One-Time Signatures) -
Adam Back reposted
Coinjoined Chris โก
@coinjoined
Absolute full house for @bitschmidty ๐ฅ
He walked through the actual steps Bitcoin Core developers are taking to make Bitcoin better money, and cleared up the myth that Core is busy with things plebs don't care about.
Great to see a packed room getting it straight from someone who actually knows what he's talking about. -
Adam Back reposted
Artem Chystiakov
@Arvolear
Well, it works! You can ZK-prove Ethereum finality natively on Liquid to create a trustless two-way bridge. No multisig. No oracle. Just ZK and smart contracts.
-
Adam Back reposted
Blockstream
@Blockstream
AI is changing how software gets built and secured, and Bitcoin is at the forefront of it.
@pwbain, CMO of Blockstream, on the opportunity: better development practices with the latest frontier models, ongoing research, and a global community working together to make the network stronger.This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Blockstream
@Blockstream
Happening now at Asilo Ciani: Noderunners: Bitcoin Core with @LeoComandini, a hands-on session on running Bitcoin Core yourself. In Italian, during @LuganoPlanB.
-
Adam Back reposted
Blockstream
@Blockstream
Happening now at Asilo Ciani: @LeoComandini , @FedericoTenga and @tierotiero on building native applications on Bitcoin, moderated by @birk1907. In Italian, during @LuganoPlanB.
-
Adam Back reposted
Blockstream
@Blockstream
Live in 30 minutes.
@n1ckler, Director of @blksresearch, on the P2P Stage at @LuganoPlanB, 15:30: The Race to Replace Bitcoin's Signatures: Quantum, AI, and Hash Functions.
What's solved, what isn't, and why the preparation matters more than the timeline.
Blockstream
@Blockstream
Some security work has to start long before it's urgent.
@n1ckler, Director of @blksresearch, takes OP_CHECKSHRINCS, a proposed opcode for post-quantum Bitcoin built on hash functions, to the technical stage at @LuganoPlanB. -
Adam Back reposted
Simply Bitcoin
@SimplyBitcoin
JUST IN: ADAM BACK ON WHETHER BITCOIN IS STILL CYPHERPUNK AND WHAT IT STILL NEEDS.
This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Blockstream
@Blockstream
DigiCash failed because it was a single point of failure. The answer was to decentralize, but a decentralized protocol can't have a bank account.
@adam3us at @LuganoPlanB on how Hashcash became Bitcoin's building block, and why proof of work made scarcity essential.This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Jonas Nick
@n1ckler
At 15:30 today on @LuganoPlanBโs P2P stage, weโll cover significant cryptography developments from the last few months and a concrete plan for a new Bitcoin signature scheme.
Blockstream
@Blockstream
Some security work has to start long before it's urgent.
@n1ckler, Director of @blksresearch, takes OP_CHECKSHRINCS, a proposed opcode for post-quantum Bitcoin built on hash functions, to the technical stage at @LuganoPlanB. -
Adam Back reposted
Blockstream
@Blockstream
Happening now at Asilo Ciani: Advanced Multi-vendor Multisig with @tulipan81, the next step for anyone already holding keys across more than one device. In Italian, during @LuganoPlanB.
-
Adam Back reposted
Blockstream
@Blockstream
Blockstream's new Lugano office is officially open.
Thank you to Lugano mayor Michele Foletti and our partners at Gonet & Cie for cutting the ribbon with @adam3us and the team during @LuganoPlanB week. ๐จ๐ญThis media couldn't be displayed. See it on the original post. -
Adam Back reposted
Lugano Plan โฟ
@LuganoPlanB
Thank you to everyone on stage today
@JoeNakamoto @1MarkMoss @AlexandreLaizet @MicheleLugano @lukedewolf @roy_breez @BITVOLT @Excellion @SahilC0 @ketominer @marcpbernegger @BTCsessions @theBTCmentor @adam3us @AaronvanW @zerolore @FedericoTenga @tierotiero @VIhnatiuk @giacomozucco -
Adam Back reposted
Blockstream
@Blockstream
Today @LuganoPlanB opens at Palazzo dei Congressi.
We're here to talk about building Bitcoin's security for the long run. At 10:30, @adam3us shares lessons from the cypherpunk movement with @AaronvanW, and @BlockstreamJade is at our booth all day. -
Adam Back reposted
Javier โฟastardo
@criptobastardo
Pretty neat fireside chat between @adam3us and @AaronvanW on the main stage of the @LuganoPlanB forum!
A really interesting chat about the cypherpunk origins of Bitcoin and whatโs next for it. -
Adam Back reposted
Vivre la libertรฉ ๐ฝ
@VivreFreedom
@adam3us in the house again at @LuganoPlanB !so happy to be part of the bitcoiners world ๐๐๐๐๐๐๐๐๐๐๐๐๐จ๐ญ๐จ๐ญ๐จ๐ญ๐จ๐ญ๐จ๐ญ๐จ๐ญ๐จ๐ญ๐จ๐ญ๐งก
-
Adam Back reposted
Blockstream
@Blockstream
On stage at @LuganoPlanB with @AaronvanW, @adam3us made the case for Simplicity as Bitcoin's last soft fork.
One expressive language with formal semantics could raise the security bar for Bitcoin scripts, and open the door to opt-in Confidential Transactions or covenants.This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Lugano Plan โฟ
@LuganoPlanB
From Hashcash to Bitcoin!
๐ค WAGMI: @adam3us joins @AaronvanW to explore Bitcoinโs cypherpunk origins. -
Adam Back reposted
BULLBITCOIN.COM
@BULLBITCOIN_
BULL Wallet version 6.14 is out!
Hereโs whatโs new:
โข Lightning payments and L-BTC to on-chain Bitcoin transfers are back.
โข Auto-buy and Limit Orders are now available in the walletโs Exchange section.
โข New built-in secure keyboard for entering your recovery phrase.
โข Rebuilt Tor integration.
โข Smoother @SeedSigner workflow.
More info ๐ -
Adam Back reposted
Lugano Plan โฟ
@LuganoPlanB
Domani al via il Plan โฟ Forum 2026: ecco lโagenda completa dellโevento
Venerdรฌ e sabato, tra Palazzo dei Congressi, Villa Ciani e Asilo Ciani, si terrร la quinta edizione della conferenza che porterร a Lugano tante โstarโ dellโuniverso Bitcoin e prenderร vita attraverso numerosissimi panel, keynote, masterclass, podcast, dj set ed eventi gratuiti.
www.tio.ch/newsblog/lugano-s-plan-/1958446/bitcoin-venerdโฆ
@LuganoLivingLab @luganomycity @LuganoEventi @Ticinonline -
Adam Back reposted
Core Lightning โก๏ธ
@Core_LN
CLN users: older versions of the webpki-roots dependency (RUSTSEC-2026-0381) still trust compromised emSign intermediate certificates, which may expose HTTPS requests to potential MITM attacks.
Core CLN code and the Lightning protocol are unaffected. The vulnerability is limited to the currencyrate (cln-currencyrate) plugin, which is enabled by default. Exposure is possible when:
- Using commands provided by the currencyrate plugin
- Configuring bkpr-currency for the bookkeeper plugin
The BIP353 plugin is unaffected in practice. Its upstream dependency includes an LNURL fallback path that uses HTTPS, but CLN's BIP353 plugin relies on DNS resolution and ignores the LNURL fallback result, so the affected TLS certificate validation path is not used.
If you don't need currencyrate, disable it by adding this to your CLN configuration: disable-plugin=cln-currencyrate
A fix is pending the relevant upstream dependency updates and a subsequent CLN release. Nodes not using the affected currencyrate functionality are not expected to be exposed, even with the plugin enabled. -
Adam Back reposted
AQUA Wallet
@AquaBitcoin
.@adam3us joined @Bloomberg to explain how the Liquid Network is recovering from the recent incident.
"The hacked funds are under investigation but we're proceeding with peg restoration," said Adam.
He also emphasized the transparency of the network.This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Lugano Plan โฟ
@LuganoPlanB
Quantum computers arenโt breaking Bitcoin tomorrow. But โprobably not tomorrowโ isnโt much of a security strategy.
At Plan โฟ Forum 2026, @n1ckler takes the stage with his keynote:
Post-Quantum Signatures for Bitcoin
How can Bitcoin prepare for a future where today's cryptography may no longer be secure?
๐ Lugano | October 23โ24 -
Adam Back reposted
Blockstream
@Blockstream
On stage in Lugano today, @adam3us on why people come to Bitcoin for different reasons: the investment, sovereignty, or paying online when other options fail them.
ETFs and managed funds give the next wave of investors an entry point.This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Bitfinex Securities
@BFXSecurities
Backstage at The Future of Capital Markets with @RichardByworth, @AlexandreLaizet, @ColeMacro, @RaphaZagury, @macrocrunch and @knutsonjesse.
-
Adam Back reposted
Blockstream
@Blockstream
Live in 30 minutes: our CEO @adam3us joins the panel on Bitcoin performance, macro shifts and the road ahead at The Future of Capital Markets in Lugano, hosted by @BFXSecurities and Blockstream Capital Partners. ๐จ๐ญ
-
Adam Back reposted
Blockstream Jade
@BlockstreamJade
Itโs TIME! ๐
@LuganoPlanB -
Adam Back reposted
Peach Bitcoin ๐๐ฅ๏ธ
@peachbitcoin
Hello everyone,
We are quite quiet lately but Peach is still running fine one block at a time :)
Node js patch has been implemented.
Go to Peach now and Stack Sats KYC-FREE while you still can!
๐ ๐ ๐ดโโ ๏ธ -
Adam Back reposted
Christian Moss
@MandelDuck
Bitcoin Seinfeld: Bitcoiners at the Airport part 3
This one actually happened to me, and a few others have said similar stories, have you noticed it? -
Adam Back reposted
Blockstream
@Blockstream
Our CEO @adam3us joined @scarletfu and @JSeyff on @BloombergTV's Bloomberg Crypto to talk about where the industry goes next: security in the age of AI, Bitcoin's path to post-quantum signatures, and the steady build of institutional adoption.
This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Documenting โฟitcoin ๐
@DocumentingBTC
The thought experiment of Satoshi Nakamoto
This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Bitfinex Securities
@BFXSecurities
What will it take for tokenised fixed income to reach institutional scale?
Join @Arnab_Naskarr, @adam3us, Rafael Mastroberardino and Michele Mattioda to explore how settlement speed and digital collateral could help unlock wider adoption.
Register today: thefutureofcapitalmarkets.com -
Adam Back reposted
SideShift.ai - Direct to Wallet Trading
@sideshiftai
Liquid Bitcoin (L-BTC) deposits have been re-enabled.
L-BTC is now fully operational on SideShift.
Shift now โ sideshift.ai
cc: @Liquid_BTC @AquaBitcoin -
Adam Back reposted
Blockstream App
@BlockstreamApp
2FA Protected accounts are back. Here's the full setup, start to finish: back up your wallet, add email, SMS and an authenticator app, then send with 2FA.
One key on your device, one held by @Blockstream behind 2FA.This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Blockstream
@Blockstream
2FA Protected accounts are back.
Watch the full walkthrough: back up your wallet, set up email, SMS, and an authenticator app, then send with 2FA. The same multisig protection we pioneered in 2019, live again in the @Blockstreamapp.
youtu.be/_xfCDP3b-Ek -
Adam Back reposted
BitcoinJiuJitsu
@BitcoinJiuJitsu
Chips the bitcoin 200-week moving average.
Lets BIP-110 slide past.
@adam3us taps it in, suit and shades on.
Just in time for @LuganoPlanB. -
Adam Back reposted
Lugano Plan โฟ
@LuganoPlanB
Some people talk about building on Bitcoin. Nifty Nei teaches you how to do it. ๐ ๏ธ
At Plan โฟ Forum 2026, @niftynei takes the stage with her keynote "Developing Bitcoin++" and gets hands-on with a masterclass: "Base58 Builds Protocols from Scratch"
Two sessions for those who want to get under Bitcoin's hood.
๐ Lugano | Friday & Saturday
๐๏ธ planb.lugano.ch -
Adam Back reposted
The Bitcoin Conference
@TheBitcoinConf
YouTube has banned The Bitcoin Conference channel.
All our channel does is post keynotes and panels from the largest Bitcoin conference in the world, bringing Bitcoin education to the masses.
Please reinstate our channel.
@YouTube @TeamYouTube -
Adam Back reposted
AQUA Wallet
@AquaBitcoin
Peg in and out of @Liquid_BTC seamlessly with AQUA. ๐ง
You can effortlessly convert your native Bitcoin to the Liquid Network to enjoy faster settlements and lower fees.
Experience true financial sovereignty in one unified app. ๐๐ฌ -
Adam Back reposted
Blockstream
@Blockstream
Our CEO @adam3us speaks at The Future of Capital Markets in Lugano tomorrow, hosted by @BFXSecurities during @LuganoPlanB week, covering Bitcoin's macro outlook, tokenized fixed income and collateral, and a look back at 2026 and ahead to 2027. ๐จ๐ญ
Bitfinex Securities
@BFXSecurities
Adam Back's (@adam3us) Hashcash system, built in 1997, is cited in the Bitcoin whitepaper - proof-of-work before Bitcoin existed to need it!
The CEO of Blockstream will speak at The Future of Capital Markets in Lugano on 22 October.
Further details: thefutureofcapitalmarkets.com -
Adam Back reposted
AQUA Wallet
@AquaBitcoin
Blockstream CEO @adam3us joined @Bloomberg to discuss the Liquid Network, the recent security incident, and why he sees it as business as usual.
The network remains a resilient and critical layer for Bitcoin infrastructure. ๐ ๐ง
www.bloomberg.com/news/videos/2026-10-20/business-as-usuaโฆ -
Adam Back reposted
Alistair Milne
@alistairmilne
Bitcoin bear markets since 2011 lasted:
- 361 days
- 377 days
- 411 days
This one was at 359 days by the end of September, and short-term holders now own just 16% of supply, the lowest since Jan 2023
The tourists have mostly gone home -
Adam Back reposted
The Bitcoin Historian
@pete_rizzo_
JUST IN: CYPHERPUNK LEGEND ADAM BACK JUST PERFECTLY EXPLAINED WHY THE #bitcoin BOTTOM IS IN LIVE ON BLOOMBERG
BIG BANKS ARE NOW RECOMMENDING "2-4% ALLOCATIONS, SOME EVEN ABOVE THAT"
"THE 200-WEEK MA JUST RECENTLY CROSSED $65,000"
"HISTORICALLY, THIS IS WHEN BTC STARTS TO APPRECIATE AFTER A BEAR MARKET"
BUY THE DIP WHILE YOU STILL CAN
THE BULL IS LOADING ๐ -
Adam Back reposted
SideSwap
@side_swap
Peg-out update
About 600 peg-outs since we reopened yesterday. Pegs are back both ways, with possible delays while refills are still manual.
The ~600 BTC shortfall is filled once the security review is done and everything is updated. Lots more coming.
sideswap.io/news/peg-out-update-21-october-2026/ -
Adam Back reposted
Bitcoin Archive
@BitcoinArchive
JUST IN: Adam Back says Bitcoin cycle timing and 200-day moving average point to big gains ahead.
This media couldn't be displayed. See it on the original post. -
Adam Back reposted
AQUA Bitcoin en Espaรฑol
@AquaBitcoinES
ACTUALIZACIรN: Las operaciones de peg de @Liquid_BTC se estรกn reanudando. Las tarifas de swap de Indra vuelven al 0.25% y los lรญmites se estรกn flexibilizando. La funcionalidad de @side_swap dentro de AQUA tambiรฉn ha vuelto a la normalidad, por lo que ahora puedes hacer peg out a una proporciรณn 1:1 de L-BTC a BTC. ยกGracias por tu paciencia! ๐ฌ๐
Liquid Network ๐
@Liquid_BTC
Liquid Network Restoration Update
With key technical milestones completed and network operations stable, user swap functionality is now restored with semi-automated swaps for Federation members. Normal peg and balance validation will be reinstated soon.
The Liquid Networkโs members appreciate the broader Bitcoin communityโs support and advocacy as we work to not only provide the restoration, but also harden the networkโs security structure.
blog.liquid.net/liquid-network-staged-recovery-update/ -
Adam Back reposted
BTC Times
@BTCTimescom
โ @Liquid_BTC restored semi-automated swaps between #bitcoin and L-BTC while Federation peg-outs remain paused.
btctimes.com/liquid-network-restores-swaps-while-peg-outsโฆ -
Adam Back reposted
Samson Mow
@Excellion
Lightning to Liquid should be online in a few days. Just some final tests and checks to run.
AQUA Wallet
@AquaBitcoin
The dev team will be restoring reverse swaps (Lightning to Liquid) as soon as possible. That means your @ aqua.net Lightning addresses will work normally again.
-
Adam Back reposted
The Raw Wire ๐จ
@TheRawWire
JUST IN: ๐ Adam Back says Bitcoin cycle timing and 200-day moving average point to big gains ahead.
@adam3us #bitcoinThis media couldn't be displayed. See it on the original post. -
Adam Back reposted
Shielded CSV โ
@ShieldedCSV
โ BitVM2 enabled SNARK verification on Bitcoin, but disputes required 4 MB of onchain data.
โ BitVM3 cut that to 200 bytes โ at the cost of 50 GB of offchain data.
โ Argo reduces the offchain data to about 10 MB, making BitVM bridges highly practical.
๐จโ๐ป Open-sourcing this week!
eprint.iacr.org/2026/2165 -
Adam Back reposted
Blockstream
@Blockstream
Bitcoin is built to last. Keeping it secure is long-term work.
We're excited to share our work this week at @LuganoPlanB: @adam3us on lessons from the cypherpunk movement, @n1ckler on post-quantum signatures, and self-custody workshops with our engineers. -
Adam Back reposted
FRANCIS โ๏ธ BULLBITCOIN.COM
@francispouliot_
Lightning payments (send and receive) are back in BULL wallet! BULL users that want to withdraw LBTC to BTC are now able to do so.
If you want to sell LBTC for fiat and receive it un a bank account, you can also do that via BULL exchange. -
Adam Back reposted
BULLBITCOIN.COM
@BULLBITCOIN_
Liquid and Lightning are back on BULL Wallet.
You can now send and receive Lightning payments and exchange L-BTC back to on-chain Bitcoin.
Liquid payments have also resumed on BULL Exchange. -
Adam Back reposted
James Seyffart
@JSeyff
NEW: Today i am going to be Co-hosting the Bloomberg @crypto show from 12-1 pm alongside @scarletfu. We have @adam3us & @RebeccaRettig1 as guests alongside Sandy Kaul from @FTDA_US and Eric Jardine from @chainalysis among others. Tune in here: www.bloomberg.com/live
-
Adam Back
@adam3us
MSCI talk about delisting @strategy, let's look at tradeoffs. positive of index inclusion is passive inflows; however active fund managers aiming to beat the index buy shares not in the index.
(aside from @saylor's point $STRC is a digital credit product, rather significant one)
Adam Back
@adam3us
index inclusion tradeoff explainer from @macrocrunch ...
-
Adam Back reposted
Liquid Network ๐
@Liquid_BTC
Liquid Network Restoration Update
With key technical milestones completed and network operations stable, user swap functionality is now restored with semi-automated swaps for Federation members. Normal peg and balance validation will be reinstated soon.
The Liquid Networkโs members appreciate the broader Bitcoin communityโs support and advocacy as we work to not only provide the restoration, but also harden the networkโs security structure.
blog.liquid.net/liquid-network-staged-recovery-update/ -
Adam Back reposted
Blockstream Help
@BlockstreamHelp
2FA emails for multisig accounts now arrive from
Blockstream <noreply@blockstream.com>
They used to show as GreenAddress. Same address, new sender name. If a code doesn't arrive, check your spam folder.
Blockstream Jade
@BlockstreamJade
-
Adam Back reposted
BTC Times
@BTCTimescom
๐บ๐ธ JPMorgan expects #bitcoin to outperform every major asset class over the next decade.
-
Adam Back reposted
Bitfinex Securities
@BFXSecurities
What will shape institutional appetite for $BTC heading into 2027?
The macro forces corporates and investors should watch, with @adam3us and @macrocrunch.
Lugano, 22 October.
Register now: thefutureofcapitalmarkets.com -
Adam Back reposted
AQUA Wallet
@AquaBitcoin
UPDATE: @Liquid_BTC peg operations are resuming. Indra swap fees are reverting back to 0.25% and rate limits are being relaxed. @side_swap functionality within AQUA is also back to normal, so you can now peg out at a 1:1 L-BTC to BTC ratio. Thanks for your patience! ๐ฌ๐
Liquid Network ๐
@Liquid_BTC
Liquid Network Restoration Update
With key technical milestones completed and network operations stable, user swap functionality is now restored with semi-automated swaps for Federation members. Normal peg and balance validation will be reinstated soon.
The Liquid Networkโs members appreciate the broader Bitcoin communityโs support and advocacy as we work to not only provide the restoration, but also harden the networkโs security structure.
blog.liquid.net/liquid-network-staged-recovery-update/ -
Adam Back reposted
SideSwap
@side_swap
The Liquid Network has announced that swaps between bitcoin and L-BTC are restored through swap providers, with the peg to follow. SideSwap is one of the swap providers. Peg-out is open again on SideSwap today. Our note follows.
Liquid Network ๐
@Liquid_BTC
Liquid Network Restoration Update
With key technical milestones completed and network operations stable, user swap functionality is now restored with semi-automated swaps for Federation members. Normal peg and balance validation will be reinstated soon.
The Liquid Networkโs members appreciate the broader Bitcoin communityโs support and advocacy as we work to not only provide the restoration, but also harden the networkโs security structure.
blog.liquid.net/liquid-network-staged-recovery-update/ -
Adam Back reposted
SideSwap
@side_swap
What has changed is behind the service. The Federation's own peg-outs remain restricted for now, so every payout comes from our own Bitcoin wallet and the L-BTC we take in is swapped for bitcoin in bulk under the arrangement the Liquid Network describes.
-
Adam Back reposted
Blockstream
@Blockstream
An update from the Liquid Federation on the next stage of the @Liquid_BTC Network's recovery.
Liquid Network ๐
@Liquid_BTC
Liquid Network Restoration Update
With key technical milestones completed and network operations stable, user swap functionality is now restored with semi-automated swaps for Federation members. Normal peg and balance validation will be reinstated soon.
The Liquid Networkโs members appreciate the broader Bitcoin communityโs support and advocacy as we work to not only provide the restoration, but also harden the networkโs security structure.
blog.liquid.net/liquid-network-staged-recovery-update/ -
Adam Back
@adam3us
LBTC:BTC swaps full service again. swap @liquid_btc to/from mainchain BTC on @side_swap. swap @liquid_btc to/from lightning on @AquaBitcoin.
Liquid Network ๐
@Liquid_BTC
Liquid Network Restoration Update
With key technical milestones completed and network operations stable, user swap functionality is now restored with semi-automated swaps for Federation members. Normal peg and balance validation will be reinstated soon.
The Liquid Networkโs members appreciate the broader Bitcoin communityโs support and advocacy as we work to not only provide the restoration, but also harden the networkโs security structure.
blog.liquid.net/liquid-network-staged-recovery-update/ -
Adam Back reposted
SideSwap
@side_swap
Peg-out is open again on SideSwap. The Liquid Network has announced the return of the peg in stages, swaps through swap providers now and the backing to one to one in the final stage. SideSwap is one of the swap providers. What it means for your wallet.
sideswap.io/news/peg-out-is-open-again-on-sideswap/ -
Adam Back reposted
Samson Mow
@Excellion
Peg operations are resuming for @Liquid_BTC. The external security audit is complete and looks good. Additional hardening measures are also done.
Liquid users are now able to peg-out via @side_swap and @AquaBitcoin.
The ~600 BTC shortfall will be added to the Federation wallet in the coming days.
Everything is almost back to normal! ๐๐ป๐
Liquid Network ๐
@Liquid_BTC
Liquid Network Restoration Update
With key technical milestones completed and network operations stable, user swap functionality is now restored with semi-automated swaps for Federation members. Normal peg and balance validation will be reinstated soon.
The Liquid Networkโs members appreciate the broader Bitcoin communityโs support and advocacy as we work to not only provide the restoration, but also harden the networkโs security structure.
blog.liquid.net/liquid-network-staged-recovery-update/ -
Adam Back reposted
Scott Ellam
@btconlyscott
International access for @XCEofficial is now available through @IBKR.
All shares listed on the Aquis Stock Exchange can now be traded by eligible Interactive Brokers clients across their international network, alongside 170+ other markets.
In order to access UK listed Aquis stocks, switch on UK stocks in your IBKR trading permissions.
Thanks to the team at @AquisStockEx ๐.
Not investment advice. DYOR.
๐ $XCE | AQSE: XCE | OTCQB: XCELF -
Adam Back reposted
Simon Gerovich
@gerovich
We are pleased to note that Super League ($SLE) shareholders have voted to approve the proposed Metaplanet transaction, an important step in our transformation from a Bitcoin treasury company into a global Bitcoin-native financial platform.
Upon close, Superplanet will be our U.S.-listed Bitcoin treasury platform, providing direct access to U.S. capital markets and greater flexibility to opportunistically raise capital.
Together with Metaplanet Securities in Japan, we will have complementary platforms in two of the worldโs most important capital markets, enabling us to raise and deploy capital internationally while advancing our ambitions across Bitcoin treasury, financing, financial products and asset management.
This is another exciting milestone as we build for the long term. Stay tuned for more as we move towards close.
Dylan LeClair
@DylanLeClair
Super League stockholders have approved every proposal at last week's annual meeting, including:
โ Issuance of common stock and warrants to Metaplanet
โ Name change to Superplanet, Inc. ($SLE -> $SUPA)
โ Increase in authorized preferred shares from 10m to 100m
At closing, Metaplanet will contribute 2,100 BTC + $2.5m USD in exchange for 44.86m common shares, 100 shares of Strategic Alliance Preferred Stock, and common stock warrants representing up to ~$3.4b of potential equity capital.
Based on the ~3.0m Super League shares outstanding as of September 29, Metaplanet would own ~93.7% of Superplanet's common stock at closing. All shares to be held by Metaplanet are subject to a five-year lock-up.
The Strategic Alliance Preferred carries no preferred dividend or liquidation preference; its purpose is governance. While Metaplanet holds it, Metaplanet's consent is required for charter amendments, mergers or changes of control, and designation of a board majority.
As outlined in the proxy, Superplanet intends to grow BTC per share primarily by issuing senior, non-convertible perpetual preferred stock rather than debt.
Metaplanet will also hold a 24-month right to subscribe for up to $210m of unlisted Junior Liquidity Support Preferred Stock. If issued, it would pay SOFR + 4.00% and rank junior to any senior preferred Superplanet may issue, allowing Metaplanet to provide subordinated capital in support of the balance sheet.
A new chapter begins soon. ๐บ๐ธ๐ช -
Adam Back reposted
Dylan LeClair
@DylanLeClair
Super League stockholders have approved every proposal at last week's annual meeting, including:
โ Issuance of common stock and warrants to Metaplanet
โ Name change to Superplanet, Inc. ($SLE -> $SUPA)
โ Increase in authorized preferred shares from 10m to 100m
At closing, Metaplanet will contribute 2,100 BTC + $2.5m USD in exchange for 44.86m common shares, 100 shares of Strategic Alliance Preferred Stock, and common stock warrants representing up to ~$3.4b of potential equity capital.
Based on the ~3.0m Super League shares outstanding as of September 29, Metaplanet would own ~93.7% of Superplanet's common stock at closing. All shares to be held by Metaplanet are subject to a five-year lock-up.
The Strategic Alliance Preferred carries no preferred dividend or liquidation preference; its purpose is governance. While Metaplanet holds it, Metaplanet's consent is required for charter amendments, mergers or changes of control, and designation of a board majority.
As outlined in the proxy, Superplanet intends to grow BTC per share primarily by issuing senior, non-convertible perpetual preferred stock rather than debt.
Metaplanet will also hold a 24-month right to subscribe for up to $210m of unlisted Junior Liquidity Support Preferred Stock. If issued, it would pay SOFR + 4.00% and rank junior to any senior preferred Superplanet may issue, allowing Metaplanet to provide subordinated capital in support of the balance sheet.
A new chapter begins soon. ๐บ๐ธ๐ช -
Adam Back reposted
Simon Gerovich
@gerovich
็ฑณๅฝใฎในใผใใผใชใผใฐ๏ผSuper League Enterprise, Inc.ใNasdaq: SLE๏ผใฎๆ ชไธป็ทไผใซใใใฆใๅฝ็คพใจใฎๆฌไปถๅๅผใๆฟ่ชใใใใใจใใ็ฅใใใใใใพใใใใใฏใๅฝ็คพใใใใใณใคใณใปใใฌใธใฃใชใผไผๆฅญใใใฐใญใผใใซใชใใใใณใคใณใปใใคใใฃใ้่ใใฉใใใใฉใผใ ใธใจๅค้ฉใใใใใงใ้่ฆใชไธๆญฉใจใชใใพใใ
ใฏใญใผใธใณใฐๅพใในใผใใผใใฉใใใ๏ผSuperplanet๏ผใฏใๅฝ็คพใฎ็ฑณๅฝไธๅ ดใใใใณใคใณใปใใฌใธใฃใชใผใปใใฉใใใใฉใผใ ใจใใฆใ็ฑณๅฝ่ณๆฌๅธๅ ดใธใฎ็ดๆฅ็ใชใขใฏใปในใจใๆฉๅ็ใใคๆ่ปใช่ณ้่ชฟ้ใๅฏ่ฝใซใใพใใ
ๆฅๆฌๅฝๅ ใฎใกใฟใใฉใใใ่จผๅธใจๅใใใไธ็ใงๆใ้่ฆใชไบๅคง่ณๆฌๅธๅ ดใซใใใฆ็ธไบ่ฃๅฎ็ใชใใฉใใใใฉใผใ ใๆใใใใจใจใชใใๅฝ้็ใช่ณ้่ชฟ้ใใใณ่ณๆฌ้ ๅใๅฏ่ฝใซใใใจใจใใซใใใใใณใคใณใปใใฌใธใฃใชใผใใใกใคใใณในใ้่ๅๅใใขใปใใใใใธใกใณใใฎๅๅ้ใซใใใๅใ็ตใฟใๆจ้ฒใใฆใพใใใพใใ
ๅฝ็คพใฎ้ทๆ็ใชๆ้ทใซๅใใๆฐใใชใใคใซในใใผใณใจใชใใพใใใฏใญใผใธใณใฐใซๅใใ้ฒๆใซใคใใพใใฆใฏใๅผใ็ถใใ็ฅใใใใฆใพใใใพใใ
Dylan LeClair
@DylanLeClair
Super League stockholders have approved every proposal at last week's annual meeting, including:
โ Issuance of common stock and warrants to Metaplanet
โ Name change to Superplanet, Inc. ($SLE -> $SUPA)
โ Increase in authorized preferred shares from 10m to 100m
At closing, Metaplanet will contribute 2,100 BTC + $2.5m USD in exchange for 44.86m common shares, 100 shares of Strategic Alliance Preferred Stock, and common stock warrants representing up to ~$3.4b of potential equity capital.
Based on the ~3.0m Super League shares outstanding as of September 29, Metaplanet would own ~93.7% of Superplanet's common stock at closing. All shares to be held by Metaplanet are subject to a five-year lock-up.
The Strategic Alliance Preferred carries no preferred dividend or liquidation preference; its purpose is governance. While Metaplanet holds it, Metaplanet's consent is required for charter amendments, mergers or changes of control, and designation of a board majority.
As outlined in the proxy, Superplanet intends to grow BTC per share primarily by issuing senior, non-convertible perpetual preferred stock rather than debt.
Metaplanet will also hold a 24-month right to subscribe for up to $210m of unlisted Junior Liquidity Support Preferred Stock. If issued, it would pay SOFR + 4.00% and rank junior to any senior preferred Superplanet may issue, allowing Metaplanet to provide subordinated capital in support of the balance sheet.
A new chapter begins soon. ๐บ๐ธ๐ช -
Adam Back reposted
Maximus Maximalistus
@maximalistus
What if you had the correct 24-word Bitcoin recovery phrase but still couldn't access your bitcoin?
That's exactly what can happen when you use a BIP39 passphrase and forget it.
A BIP39 passphrase isn't just another password protecting your wallet.
It's part of the process that derives your wallet's cryptographic keys.
The same recovery phrase combined with two different passphrases produces two completely different wallets.
And here's the dangerous part:
There is no "incorrect passphrase" warning.
Every passphrase produces a valid wallet. A single typo can lead you to an entirely different set of addresses, with no sign of your bitcoin.
Blockstream Jade helps you identify the wallet you've opened by displaying an 8-character fingerprint that you can compare against a previously recorded value.
But that fingerprint doesn't replace your backup.
Lose your passphrase, and your recovery phrase alone won't restore the wallet protected by it.
A BIP39 passphrase can strengthen self-custody, but it also introduces another secret you must preserve.
Security without a recovery plan can become a risk of its own.
Watch Blockstream's Short:
www.youtube.com/shorts/XdhNn5cIEd8
Jade documentation:
help.blockstream.com/blockstream-jade/add-more-security-fโฆ
Affiliate link bellow. Or just use coupon code "maximus".
rewards.blockstream.com/maximus -
Adam Back reposted
The Bitcoin Historian
@pete_rizzo_
BREAKING: ๐บ๐ธ $13 TRILLION CHARLES SCHWAB JUST ANNOUNCED ALL CLIENTS CAN NOW BUY #bitcoin DIRECTLY IN THEIR ACCOUNTS
OVER 40,000,000 AMERICANS NOW HAVE ACCESS TO BTC
THE INSTITUTIONAL FLOODGATES ARE OPENING ๐ฅ -
Adam Back reposted
Lugano Plan โฟ
@LuganoPlanB
Bitcoin's whitepaper has 8 references. Number 6 is Hashcash.
In Lugano, @adam3us sits down with @AaronvanW who literally wrote the book on Bitcoin's origins, to tell the story from the cypherpunk mailing lists to today.
"From Hashcash to Bitcoin: Adam Back's Cypherpunk Journey"
Plan โฟ Forum, Palazzo dei Congressi
๐๏ธ planb.lugano.ch/planb-forum/ -
Adam Back reposted
Scott Ellam
@btconlyscott
It took over 10 years to truly understand the problem, and four years of running a private BTC balance sheet to design the solution for the executive and specialist recruitment industry.
A listed operating group with a decentralised acquisition strategy โ profitable businesses join with performance-based earnings โ combined with an active Bitcoin treasury.
๐ BTC per share up ~48% YTD
๐ Revenue up ~97.4% after our first acquisition
In a challenging capital markets environment, Bitcoin is the cheat code.
@XCEofficial
๐ $XCE | AQSE: XCE | OTCQB: XCELFThis media couldn't be displayed. See it on the original post. -
Adam Back reposted
The Babylon Bee
@TheBabylonBee
Cavemen Issues Dire Warning That The Wheel Is Going To Eliminate Countless Jobs
This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Maximus Maximalistus
@maximalistus
๐ Multisig is back in the Blockstream App!
Blockstream has reopened the creation of 2-of-2 and 2-of-3 multisig accounts, bringing additional security and independent recovery options to Bitcoin self-custody.
Two options:
๐น 2-of-2 with 2FA (Bitcoin & Liquid): Your key and Blockstream's server key normally sign transactions together. If Blockstream becomes unavailable, you can recover independently once each deposit's timelock expires.
๐น 2-of-3 with 2FA (Bitcoin only): Adds a third key derived from a separate recovery phrase you control. Combine your primary key with this offline recovery key to recover immediately, without Blockstream's cooperation or waiting for a timelock.
For additional security, pair the Blockstream App with a Jade hardware signer.
Remember: hardware signers don't hold bitcoin. They protect your private keys and securely sign transactions without exposing those keys to your phone or computer. Your bitcoin is represented by UTXOs recorded on the blockchain.
Jade is an open-source hardware signer that works with both multisig account types.
Thinking about improving your Bitcoin signing setup? Check out Blockstream Jade.
Full announcement:
blog.blockstream.com/multisig-is-back-in-the-blockstream-โฆ
10% off on Blockstream store products with coupon "maximus".
rewards.blockstream.com/maximus -
Adam Back reposted
Blockstream Jade
@BlockstreamJade
2FA Protected accounts (multisig) are back in the Blockstream app. Server-cosigned, open-source recovery, Jade if you want one key offline.
Learn more: blockstream.com/app/multisig/
Adam Back
@adam3us
@BlockstreamApp (formerly green wallet) has multisig 2fa feature. if you were using a HWW which turned out to have a hardware bug, using @blockstream wallet (and turn on 2fa eg google auth), you would have a last line of defense: the seed alone does not allow theft of funds.
-
Adam Back reposted
Coinjoined Chris โก
@coinjoined
There shouldn't be any cables. First 3 images show the implant, last image a genuine @Ledger Nano X.
Allegedly affected resellers so far: MediaMarkt, Saturn ๐ฉ๐ช, Cryptobilis ๐ฒ๐พ, Ozon ๐ท๐บ and Singapore Airport ๐ธ๐ฌ -
Adam Back reposted
Blockstream Jade
@BlockstreamJade
-
Adam Back reposted
Retarded Pleb
@retardedpleb
WTF? I was told that the XBT shitcoin (not to be confused with real XBT, which is Bitcoin) was sound money ๐คฃ๐คฃ๐คฃ
-
Adam Back reposted
Joe Grand
@joegrand
Reverse Engineering a Ledger Nano X Hardware Implant (@_TROPICON) slides are up! grandideastudio.com/portfolio/security/ledger-hardware-imโฆ
-
Adam Back reposted
Artem Chystiakov
@Arvolear
Here is how you can build confidential, decentralized, regulated assets on Liquid. Transfers cost around 20 cents. The protocol construction and the benchmarks are in the paper below.
-
Adam Back reposted
Johannes (4, 4)
@0xJohannes_
obv wasnt allowed to take a picture but this is where i got the info about returns and who the supplier was etc
-
Adam Back reposted
CsquidCo
@cellarSQUIDc
she's just itching to prove archimedes principle true.
-
Adam Back reposted
Coinjoined Chris โก
@coinjoined
It all makes sense now from Mechanics perspective ๐คฏ
This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Rory
@roryhighside
To Catch A Shitcoin Predator - The Blake Files
This media couldn't be displayed. See it on the original post. -
Adam Back reposted
domenico
@domegabri
Clearly if your seed was compromised you want to rotate and not wait for the attacker for csv timelocks to expire. 2of3 allows to provide externally generated entropy for the second user held key.
-
Adam Back
@adam3us
@BlockstreamApp (formerly green wallet) has multisig 2fa feature. if you were using a HWW which turned out to have a hardware bug, using @blockstream wallet (and turn on 2fa eg google auth), you would have a last line of defense: the seed alone does not allow theft of funds.
-
Adam Back reposted
BitcoinJiuJitsu
@BitcoinJiuJitsu
Know your HWW hasn't been touched before you trust it with your bitcoin.
Jade ships in tamper-evident packaging, and the metal Jade Plus body shows clear signs if opened. Open-source hardware and firmware and Genuine Check confirms @Blockstream built it. -
Adam Back reposted
Maximus Maximalistus
@maximalistus
Go deeper down the Bitcoin self-custody rabbit hole.
Codex32 by Blockstream Research explores a different level of key backup: paper computers, volvelles, checksums, and Shamir Secret Sharing for Bitcoin seeds.
It is a way to think about keys beyond devices and apps.
Generate.
Split.
Verify.
Recover.
With pencil, paper, math, and discipline.
Source:
www.youtube.com/shorts/-RZKYc7G6FQ
Codex32:
store.blockstream.com/products/codex32-shamir-secret-sharโฆ -
Adam Back reposted
Bitfinex Securities
@BFXSecurities
Capital B (@_ALCPB) is Europe's first publicly listed $BTC treasury company.
@AlexandreLaizet, its Board Director of Bitcoin Strategy, joins The Future of Capital Markets. Discussing what's next for bitcoin treasury companies.
Details: thefutureofcapitalmarkets.com -
Adam Back reposted
domenico
@domegabri
For a few Ledger users that are using Blockstream multisig for btc custody, this is still salvageable provided they had setup 2FA. They should still migrate to new seeds.
-
Adam Back reposted
Artem Chystiakov
@Arvolear
Just released Simplex v0.1.0. The last 6 months were freaking crazy, but the framework is now ready for a somewhat stable tag. Unit and fuzz test your SimplicityHL contracts. Spin up local Elements nodes. Write in Rust. Build with Simplicity.
github.com/BlockstreamResearch/smplx -
Adam Back reposted
Robin Linus โ
@robin_linus
This nails one of the strongest arguments against the "AI will kill Bitcoin" FUD
Casey
@rodarmor
5/ Progress on insane galaxy brain math that nobody cares about, much less understands, does not indicate that one of the most studied, most widely deployed, and most important mathematical objects in the history of humanity is at risk.
-
Adam Back
@adam3us
some old observations on the threat model GENERIC limits of hardware wallets. which make many things mis-thought security theater in practice. threat modelling is hard; i like threat modelling.
see this in context of screen scraper exfil radio device
Adam Back
@adam3us
also consider the fundamental threat model limit of the generic substitution attack: don't modify a HWW (ledger, jade, trezor etc), replace it with a look-alike with radio phone home (via relay or wifi). relay it to a human operator with the stolen real device. what next? glitter
Post not available here, view on X
Adam Back
@adam3us
that doesn't mean you can't make secure HWWs but you have to start by understanding the real threat model, people trying to take users BTC don't care about your misconceptions, they will cut through them like butter by routing around, doing generic attacks; whatever is pragmatic.
Adam Back
@adam3us
and surprisingly few manufacturers understood the generic attacks, or so it seemed from their marketing and design choices, for the last decade. time to catchup with threat-modelling...
-
Adam Back reposted
Mark Karpelรจs
@MagicalTux
If you have bought a Ledger from CryptoBilis, have a look inside. If you find anything that is not like on Ledger's site, or if you're unsure, post pictures.
support.ledger.com/article/4404382029329-zd -
Adam Back reposted
Alex Bragin
@BraginRights
History of the new AQUA wallet x.com/i/article/2108585794206056448
-
Adam Back reposted
Harry Halpin - Nym
@harryhalpin
I just wasted hours of my life reviewing a seemingly impressive traffic analysis paper for an academic privacy conference that was AI-generated. The contribution was a mix of incoherent mini-results and nothingburgers, knitted together with seemingly convincing sounding prose.
Bryan Johnsontown Massacre
@DuncanAStuart
Probably the correct take on โAI can solve math nowโ
Daniel Litt
@littmath
Well worth reading: proofsandprompts.com/2026/10/08/100-reactions-to-100-soluโฆ
-
Adam Back reposted
JP Aumasson
@veorq
"discrete log is just like a math conjecture, it's a matter of time and tokens"
No. AI may optimize the best known algorithms and/or implementations, but if factoring/DL are hard (although not NP-complete, if P!=NP we know such hard "NP-intermediate" exist), then no efficient solver exists, ergo no AI can find one. Most likely P!=NP.
< insert caveats about worst/average-case hardness> -
Adam Back
@adam3us
vitalik.eth "public-key encryption cannot be done with hashes alone" 1976 Merkle paper disagrees hashcash.org/papers/merkle-puzzle.pdf involves an interactive proof of work like property, costs the attacker n times more. (not that asymmetric, but simple to understand first public key scheme).
-
Adam Back reposted
Bit Paine โก๏ธ
@BitPaine
brother that weird spot is the last four years
SalsaTekila
@SalsaTekila
Weird spot where BTC looks like a long
While ETH looks like a short -
Adam Back reposted
Kyle Torpey
@kyletorpey
โThey are rediscovering from first principles why Bitcoin did X, Y, and Z.โ
The end result of every other crypto project.
Federico Tenga
@FedericoTenga
They are rediscovering from first principle why UTXOs are superior to account based models
-
Adam Back reposted
Rob Hamilton
@Rob1Ham
Head of cryptography at Coinbase clearly stating the problem with current engadgement bait vague posting about AI breaking cryptography
@Fundamentals21m and I did a 10 part podcast series explaining ECDSA at a very casual/intro level if you want to start your journey
Yehuda Lindell
@LindellYehuda
What a strange take? So you think all hardness assumptions are not due to inherent hardness but to human weakness in finding algorithms? I couldnโt disagree more. (Of course we canโt know but thereโs no evidence whatsoever pointing to this conclusion.)
-
Adam Back reposted
Yehuda Lindell
@LindellYehuda
In case people think I am advocating for not being cautious, or thinking that AI won't be an issue for any cryptography, that's not the case. Let me word what I think would be a balanced approach regarding AI and crypto. 1/n
-
Adam Back reposted
JP Aumasson
@veorq
a friend of my cat has a neighbor who heard a rumor that OpenAI broke hybrid ML-KEM+ECC which would explain why CNSA went for non-hybrid and I dont wanna speculate but AES is probably at risk too
-
Adam Back reposted
Yehuda Lindell
@LindellYehuda
I donโt agree. Did breaking MD5 and SHA1 mean that all cryptography is broken? What evidence is there that publishing math papers will impact ECC that hasnโt shown a crack in 3 decades.
-
Adam Back reposted
Yehuda Lindell
@LindellYehuda
In conclusion, making such statements without any evidence is the opposite of responsible behavior. It is the very definition of FUD โ it cannot be proven wrong but thereโs also no evidence whatsoever of it being true. n/n
-
Adam Back reposted
Yehuda Lindell
@LindellYehuda
Of course, we canโt prove that EC discrete log is hard, since we havenโt been able to prove P neq NP. But just throwing out - AI is doing amazing math so elliptic curve hardness is in danger has no logical basis whatsoever. 3/n
-
Adam Back reposted
Yehuda Lindell
@LindellYehuda
I wasnโt going to comment since this is a really bad take IMO, but since itโs taken off I feel the need to. To my understanding, there is no evidence whatsoever pointing to a break of decades old hardness assumptions like elliptic curve cryptography. 1/n
Justin Drake
@drakefjustin
Today I call upon the blockchain industry to calmly begin planning for "bunker mode". My personal recommendation is to set in motion a controlled mass migration of assets to fresh addresses, i.e. addresses whose pubkeys remain hidden behind a hash.
Holders, starting with large and sophisticated ones, should consider moving the bulk of their funds to addresses that have never signed a transaction. And when they do sign one, they should also move remaining funds to a new address (possibly generated from the same seed phrase).
Don't rush. While I believe there is cause for action a rushed migration would do more harm than good. Don't panic either. Moving assets to protected addresses is a simple, preventative step which does not require new cryptography or new wallets.
IMO it is now reasonable to brace for the possibility that ECDSA breaks before qday, in the worst case in months not years. By "break" I mean fast private key recovery (e.g. in one week) on available hardware (e.g. a large GPU cluster).
Recent days have been humbling for human mathematical intuition. Long-held, unquestioned hypotheses have fallen. This includes the n log(n) bound for integer multiplication and the 3SUM conjecture. In hindsight, May's unexpected disproof of the Erdลs unit distance conjecture was our warning shot.
Yesterday's OpenAI drop made it clear that mathematical superintelligence is upon us. They say there are weeks where decades happen. We are about to live through weeks where centuries of mathematical progress happen. Could our magic 64-byte ECDSA signatures be too good to be true? Was it just security through obscurity all this time?
Elliptic curves feel especially vulnerable to superintelligence. Curves carry rich structure, with room for fancy tricks like Schoof, Frobenius, pairings. (By contrast, hashes are designed to minimise algebraic structure.)
Separately, as Ewin Tang can attest, an efficient quantum algorithm sometimes foreshadows an efficient classical one. We should be open to the possibility of a classical counterpart to Shor that breaks elliptic curves and RSA at once.
Also noteworthy is the striking under-representation of cryptographic breakthroughs among the 722 mathematical results OpenAI published. I've witnessed first-hand the US government censoring academic quantum cryptanalysis results. Backroom interventionism is my base case.
I urge large, sophisticated actors to lead by example. Project11's "risq list" (bitcoin-risq-list.projecteleven[.]com) is a great tracker of exposed BTC pubkeys. Binance, Bitbank, Robinhood, Bitfinex, and Tether have an opportunity to harden their cold storage. Next month I'll address institutions in London in a live Q&A (forum.ethereuminstitutional[.]org/london-2026).
Again, please do not rush. Wallets holding under 50 BTC enjoy partial cover from "Satoshi's shield", i.e. his 20K exposed addresses that hold 50 BTC each. Load-bearing signers like oracles and L2 security councils should consider rotating ECDSA pubkeys with every signed message and/or multi-signing with a hash-based schemes like SPHINCS.
Exiting bunker mode safely will require post-AI cryptography. My inclination is to go all-in on hash-based cryptography and avoid structured mathematical assumptions entirely, whether from curves, lattices, or isogenies. A single battle-tested hash (e.g. from the SHA or BLAKE families) yields plausible post-AI security.
The Ethereum roadmap on strawmap[.]org fully embraces hash-based cryptography with end-to-end formal verification as a response to the quantum threat. Those timelines must now be revisited and accelerated in light of mathematical superintelligence. I'll be pushing for maximum defensive acceleration. -
Adam Back reposted
instagibbs
@theinstagibbs
It's even more absurd than the PQ argumentz in that there is zero evidence... Which is somehow evidence itself.
Grifters.
Yehuda Lindell
@LindellYehuda
I wasnโt going to comment since this is a really bad take IMO, but since itโs taken off I feel the need to. To my understanding, there is no evidence whatsoever pointing to a break of decades old hardness assumptions like elliptic curve cryptography. 1/n
Justin Drake
@drakefjustin
Today I call upon the blockchain industry to calmly begin planning for "bunker mode". My personal recommendation is to set in motion a controlled mass migration of assets to fresh addresses, i.e. addresses whose pubkeys remain hidden behind a hash.
Holders, starting with large and sophisticated ones, should consider moving the bulk of their funds to addresses that have never signed a transaction. And when they do sign one, they should also move remaining funds to a new address (possibly generated from the same seed phrase).
Don't rush. While I believe there is cause for action a rushed migration would do more harm than good. Don't panic either. Moving assets to protected addresses is a simple, preventative step which does not require new cryptography or new wallets.
IMO it is now reasonable to brace for the possibility that ECDSA breaks before qday, in the worst case in months not years. By "break" I mean fast private key recovery (e.g. in one week) on available hardware (e.g. a large GPU cluster).
Recent days have been humbling for human mathematical intuition. Long-held, unquestioned hypotheses have fallen. This includes the n log(n) bound for integer multiplication and the 3SUM conjecture. In hindsight, May's unexpected disproof of the Erdลs unit distance conjecture was our warning shot.
Yesterday's OpenAI drop made it clear that mathematical superintelligence is upon us. They say there are weeks where decades happen. We are about to live through weeks where centuries of mathematical progress happen. Could our magic 64-byte ECDSA signatures be too good to be true? Was it just security through obscurity all this time?
Elliptic curves feel especially vulnerable to superintelligence. Curves carry rich structure, with room for fancy tricks like Schoof, Frobenius, pairings. (By contrast, hashes are designed to minimise algebraic structure.)
Separately, as Ewin Tang can attest, an efficient quantum algorithm sometimes foreshadows an efficient classical one. We should be open to the possibility of a classical counterpart to Shor that breaks elliptic curves and RSA at once.
Also noteworthy is the striking under-representation of cryptographic breakthroughs among the 722 mathematical results OpenAI published. I've witnessed first-hand the US government censoring academic quantum cryptanalysis results. Backroom interventionism is my base case.
I urge large, sophisticated actors to lead by example. Project11's "risq list" (bitcoin-risq-list.projecteleven[.]com) is a great tracker of exposed BTC pubkeys. Binance, Bitbank, Robinhood, Bitfinex, and Tether have an opportunity to harden their cold storage. Next month I'll address institutions in London in a live Q&A (forum.ethereuminstitutional[.]org/london-2026).
Again, please do not rush. Wallets holding under 50 BTC enjoy partial cover from "Satoshi's shield", i.e. his 20K exposed addresses that hold 50 BTC each. Load-bearing signers like oracles and L2 security councils should consider rotating ECDSA pubkeys with every signed message and/or multi-signing with a hash-based schemes like SPHINCS.
Exiting bunker mode safely will require post-AI cryptography. My inclination is to go all-in on hash-based cryptography and avoid structured mathematical assumptions entirely, whether from curves, lattices, or isogenies. A single battle-tested hash (e.g. from the SHA or BLAKE families) yields plausible post-AI security.
The Ethereum roadmap on strawmap[.]org fully embraces hash-based cryptography with end-to-end formal verification as a response to the quantum threat. Those timelines must now be revisited and accelerated in light of mathematical superintelligence. I'll be pushing for maximum defensive acceleration. -
Adam Back reposted
Federico Tenga
@FedericoTenga
-
Adam Back reposted
Coinjoined Chris โก
@coinjoined
The plan? We announce AI has solved the mathematical hardness assumptions underlying public-key cryptography. Our evidence is that humans simply haven't tried hard enough. Naturally, civilization must enter bunker mode and buy our shitcoin immediately.
-
Adam Back reposted
Scott Ellam
@btconlyscott
It is a long runway of opportunity for @XCEofficial to disrupt our recruitment over the next few years.
When we hit a critical mass of revenue in executive and specialist recruitment - I believe that any of the big listed firms would need to prove that they will buy Bitcoin through two bear markets without wavering in conviction, to follow or compete.
And in the meantime any profitable private business that decides to stack Bitcoin - knows we value it and knows they can join XCE. -
Adam Back reposted
Lyn Alden
@LynAldenContact
Most of the hawks don't take into account the fiscal-driven inflation situation or sovereign bond liquidity.
Most of the doves don't take into account the lending-driven ramifications of pivoting amid high inflation.
There's too much first-order thinking out there. -
Adam Back reposted
Bitcoin Magazine
@BitcoinMagazine
JUST IN: ๐ท๐บ Russia's largest bank Sberbank, has received approval to offer digital asset custody services starting with Bitcoin ๐
-
Adam Back reposted
Scott Ellam
@btconlyscott
An article from @BTCtreasuries 'This UK company is charting a bold new alternative to digital credit.'
@XCEofficial
newsletter.bitcointreasuries.net/p/a-new-bitcoin-treasuryโฆ -
Adam Back reposted
XCE - Connecting Excellence Group
@XCEofficial
A recruitment founder can build a ยฃ1m, ยฃ5m or ยฃ10m business.
But what happens when they want to take some value out without simply walking away?
That's where public markets can change the proposition.
XCE gives successful recruitment businesses a route into a listed group.
Founders can take value out.
Keep running what they've built.
And participate in what the wider Group becomes.
We think that's a powerful proposition.
๐ $XCE | AQSE: XCE | OTCQB: XCELF -
Adam Back reposted
Blockstream Help
@BlockstreamHelp
Upcoming @BlockstreamApp Liquid Multisig maintenance:
๐ October 8, 08:00-09:00 UTC
Plan accordingly if you're using multisig on @Liquid_BTC accounts. -
Adam Back reposted
Core Lightning โก๏ธ
@Core_LN
Core Lightning 26.06.9 is out. Upgrade now.
It fixes a newly reported vulnerability that can lead to loss of funds. Nodes running 26.06.8 or earlier are affected.
Verify the signatures and install it as soon as possible.
github.com/ElementsProject/lightning/releases/tag/v26.06.9 -
Adam Back
@adam3us
"unhosted wallet" was always a red-flag, reject double-speak!
-
Adam Back reposted
Scott Ellam
@btconlyscott
Bitcoin is most powerful when integrated into people driven businesses. The objectives for @XCEofficial are to keep compounding revenue by hiring and acquiring profitable executive and specialist recruitment companies using our decentralised model, and continue to strengthen the BTC treasury.
Ten months as a listed company, in one of the toughest environments has given a strong indication of the opportunity XCE has when we return to a bull market:
๐ 9.27 BTC โ 81.157 BTC worth $6.95m (ยฃ5.25m)
โ One operating business โ two businesses following first acquisition
โ Pro forma revenue up 97.4% โ significantly increasing revenue per share
โ Bitcoin per share up throughout
The acquisition that did it cost c.ยฃ150k of net cash on completion - and brought 8.216 BTC with it at market value.
8.75x the Bitcoin in under ten months and doubling the operating business. 1,000 UK recruitment businesses and 10,000 globally fit the XCE model.
XCE has a unique opportunity to disrupt an industry with Bitcoin.
๐ $XCE | AQSE: XCE | OTCQB: XCELF -
Adam Back
@adam3us
"BIP 110 was a UISF" -@zndtoshi (User Ignored Soft Fork)
zender โ๏ธ
@zndtoshi
Bip110 was actually a User Ignored Soft Fork.
Adam Back
@adam3us
Which then did a HF by switching PoW, reactive to be ignored. Somehow they blamed miners even though it was clearly ignored by users in the market.
Adam Back
@adam3us
-
Adam Back reposted
XCE - Connecting Excellence Group
@XCEofficial
Deal one is done.
James Gray is now part of XCE.
ยฃ1.79m revenue.
ยฃ431k EBITDA.
81.157 BTC treasury.
The brand stays.
The team stays.
The business keeps operating independently.
What changes is the platform around it.
Thatโs the XCE model in execution.
Covered by Insider Media: www.insidermedia.com/news/yorkshire/xce-completes-first-rโฆ
๐ $XCE | AQSE: XCE | OTCQB: XCELF -
Adam Back reposted
zender โ๏ธ
@zndtoshi
Bip110 was actually a User Ignored Soft Fork.
-
Adam Back reposted
Bit Paine โก๏ธ
@BitPaine
crashing out over MSTR at the bottom is one thing, but my brother in Christ we are 100% off the lows and inching towards the pump of the century that is stage 4 saylor derangement syndrome
at least crash out when itโs trendy -
Adam Back reposted
-
Adam Back reposted
Bitcoin Treasuries
@BTCtreasuries
JUST IN: British executive recruitment firm @XCEofficial ($XCE) has acquired James Gray Recruitment, along with its 8.216 #bitcoin, and now holds a total of 81.157 BTC.
"The aim is to grow the recruitment group while increasing BPS." ๐ฅThis media couldn't be displayed. See it on the original post. -
Adam Back reposted
XCE - Connecting Excellence Group
@XCEofficial
Why did XCE acquire James Gray Recruitment?
Because it is exactly the type of business we built XCE to own.
A profitable, specialist, founder-led recruitment business with strong relationships, an established team and room to grow.
James Gray keeps its brand, its people and its operating independence.
What changes?
It now has permanent capital, a listed platform and the wider XCE Group behind it.
And for XCE, it's the first real demonstration of the acquisition model moving from strategy to execution.
@btconlyscott explains why the deal matters and where we go from here.
๐ $XCE | AQSE: XCE | OTCQB: XCELFThis media couldn't be displayed. See it on the original post. -
Adam Back reposted
XCE - Connecting Excellence Group
@XCEofficial
XCEโs Bitcoin treasury has increased to 81.157 BTC, valued at ยฃ5.25m ($6.95m) at the price on 2 October.
Our first recruitment acquisition brought 8.216 BTC into the Group at market value, with no premium, alongside a profitable operating business.
We now have several ways to fund growth: recruitment cashflows, investment raised through public markets and borrowing against part of our Bitcoin holdings without selling them.
The aim is to grow the recruitment Group while increasing Bitcoin per share.
Full announcement and Important Notice: irtools.co.uk/115/story/db9344c7-1b48-4ce3-96fc-7cb20f7f35c4
๐ $XCE | AQSE: XCE | OTCQB: XCELF
Not investment advice. An investment in the Company is not an investment in Bitcoin. -
Adam Back reposted
XCE - Connecting Excellence Group
@XCEofficial
James Gray Recruitment and James Gray Engineering have joined XCE.
Richard Samuels and his team have built a profitable construction and engineering recruitment business serving clients across the UK, US and international markets.
The acquisition gives the founders a route to realise value while continuing to lead the business. James Gray retains its brand, management and day-to-day operating independence, with access to XCEโs capital and listed platform to support further growth.
For XCE, it establishes a second recruitment business alongside Spencer Riley and roughly doubles Group revenue on a pro-forma basis.
This is the acquisition model we intend to repeat: buy profitable specialist recruiters, retain the people and relationships behind their performance, and provide the resources to expand.
$XCE | AQSE: XCE | OTCQB: XCELF -
Adam Back reposted
Simon Gerovich
@gerovich
I have two important updates to share with you today as we continue to build Metaplanet into a global financial platform rooted in Bitcoin.
From the beginning, our strategy was never simply to accumulate Bitcoin. Our objective has been to build the leading Bitcoin financial company in Asia and, over time, become one of the leading Bitcoin financial institutions in the world.
Over the past year, we have worked to execute that strategy with discipline and speed: growing our Bitcoin reserves, expanding our operating businesses, broadening our access to capital, and laying the foundation for a scalable credit platform built around Bitcoin.
The pending Superplanet transaction, the development of Metaplanet Securities, the expansion of our distribution capabilities, and the continued growth of our Bitcoin holdings are all components of a unified long-term strategy.
Here are the latest steps on this journey:
- First, in the third quarter we executed a sale and repurchase of Bitcoin that demonstrated the liquidity of our Bitcoin reserves and increased our overall Bitcoin position.
- Second, we are launching a Net Interest Income Strategy designed to create recurring income streams and lower our effective cost of capital, supporting the next phase of our growth.
Rating agencies and credit investors ask one question of a Bitcoin company: can that Bitcoin be turned into cash to meet obligations, and will it be? We answered by doing it. We converted Bitcoin into cash, exceeding the total outstanding principal of our bonds, borrowings and other interest-bearing debt. We held that cash, then bought back more Bitcoin than we sold.
Net, we added 1,000 BTC.
As of September 30, Metaplanet held 44,000 BTC, making us the second-largest listed Bitcoin treasury company in the world. Metaplanet has generated revenue from its Bitcoin Income Generation business for eight consecutive quarters, has expanded its strategic footprint through acquisitions and new business initiatives, and has now demonstrated that its Bitcoin can be converted into cash when needed, an important step in our march to realizing our potential in Japan and beyond.
We continue to execute on our goal: Building a world-class Bitcoin financial institution. And we will continue to update you as we move ahead with additional value-creating initiatives.
Full details are in the four TSE disclosures released today. -
Adam Back reposted
Scott Ellam
@btconlyscott
Welcome to the @XCEofficial group, James Gray Recruitment and James Gray Engineering (recruitment) - a specialist construction and engineering recruitment company working with clients in the UK and USA.
Richard Samuels, Mario and the whole team - the first business to join since our IPO with Spencer Riley (the business I founded) in the group. The business will keep their brand, their leadership and their autonomy.
We are the anti-exit. Joining enables teams to build and scale within the listed platform.
Look forward to hiring and acquiring more with you.
Welcome aboard.
๐ $XCE | AQSE: XCE | OTCQB: XCELF -
Adam Back reposted
Joe007
@J0E007
Here you go
-
Adam Back reposted
Willy Woo
@willywoo
Little known fact...
BTC popularity among nation-states has outstripped individuals:
5% of the world population own BTC
8% of nations have a policy to acquire/hold BTC -
Adam Back reposted
Scott Ellam
@btconlyscott
1/
๐ We have a pipeline of recruitment acquisitions. The first completed this morning - and it happened to be holding Bitcoin.
The intent: more acquisitions in exactly the same manner. Profitable businesses, acquired with discipline, whose cash strengthens the Group and the Bitcoin treasury behind it.
The James Gray deal, in eight posts. ๐งต -
Adam Back reposted
Scott Ellam
@btconlyscott
Doubled the recruitment Group, increased the Bitcoin treasury and grew Bitcoin per share. In our first @XCEofficial acquisition.
โ First acquisition completed - James Gray Recruitment and James Gray Engineering
โ Pro forma Group revenue to c.ยฃ3.63m, up 97.4%
โ ยฃ1.79m revenue (up 21.5%) and ยฃ431k EBITDA - James Gray Recruitment 12 months to 30 June 2026
๐ Treasury up to 81.157 BTC, worth ยฃ5.25m ($6.95m) at ยฃ64,657 ($85,664) per BTC - 8.216 inside the deal
โ Bitcoin per share up 2.5% issued / 3.5% fully diluted - BTC Yield for the quarter: 11.26%
โ Net cash out on completion: c.ยฃ150k, excluding the Bitcoin element
All further consideration is tied directly to the business's future performance. The team joining, the group and shareholders - aligned behind the same outcome.
The brand stays. The team stays. The owner stays. They keep their autonomy - and grow within the listed group.
Proud of the XCE team, the James Gray team and every adviser involved - five weeks from Heads of Terms to completion.
Deal one.
๐ $XCE | AQSE: XCE | OTCQB: XCELF -
Adam Back reposted
Scoresby
@BitcoinScoresby
Dorian Nakamoto raps the Bitcoin whitepaper abstract.
๐ Sound on! -
Adam Back
@adam3us
upgrade to last-weeks @core_ln CORE lightning security release.
there are reports of un-patched nodes being attacked.
Core Lightning โก๏ธ
@Core_LN
Urgent security update: If youโre running version 26.06.7 or earlier, please upgrade to the latest release as soon as possible.
Weโve received reports that attackers are targeting unpatched nodes. Keeping your node up to date is an important step in protecting your funds. -
Adam Back reposted
Core Lightning โก๏ธ
@Core_LN
Urgent security update: If youโre running version 26.06.7 or earlier, please upgrade to the latest release as soon as possible.
Weโve received reports that attackers are targeting unpatched nodes. Keeping your node up to date is an important step in protecting your funds. -
Adam Back reposted
Tufty
@tuftythecat
Check out my latest article: Faketoshi Patent Appeals - The End of the Road www.linkedin.com/pulse/faketoshi-patent-appeals-end-road-โฆ via @LinkedIn
-
Adam Back reposted
Simply Bitcoin
@SimplyBitcoin
Uptober is Coming ๐ #bitcoin
-
Adam Back reposted
Documenting โฟitcoin ๐
@DocumentingBTC
It took 40 years of research to create Bitcoin
This media couldn't be displayed. See it on the original post. -
Adam Back
@adam3us
uptober๐ฉ
-
Adam Back reposted
Scott Ellam
@btconlyscott
Bitcoin solves industry problems.
10,000+ executive and specialist recruitment company owners plan to work in their companies their entire career - and then self-fund a management buyout.
@XCEofficial is a listed business with a Bitcoin treasury that solves their biggest problem: enabling them to lock in the value they create, continue building the business they love and consolidate that value with their peer group.
How the XCE acquisition engine works - from the stage at the @BTCtreasuries Conference in New York.
โ The founder keeps the brand, the team and their autonomy
โ They gain permanent capital, a listed platform and performance equity for their people
โ XCE consolidates the revenue and EBITDA - and the cash reserves become Bitcoin, held long term
Raise ยฃ1m, pay the seller. The target's ยฃ1m reserve comes into XCE. XCE buys ยฃ1m of Bitcoin.
And the part capital markets people spot quickly: at a positive mNAV, each acquisition is the equivalent of raising capital to buy Bitcoin - but gaining revenue and profit alongside it.
$XCE | AQSE: XCE | OTCQB: XCELF -
Adam Back reposted
MARS SPITS BARS ๐ฅ
@marsspitsbarz
A crashout titled โYou Didnโt See This Coming?โ
This media couldn't be displayed. See it on the original post. -
Adam Back
@adam3us
shielded CSV being discussed more. "shielded CSV: Private and Efficient Client-Side Validation" eprint.iacr.org/2025/068 by @n1ckler (@blksresearch/@blockstream) @liameagen (@AlpenLabs) and @robin_linus (@ZeroSync_)
-
Adam Back reposted
Artem Chystiakov
@Arvolear
They frankly are if implemented in pure Simplicity. For every such primitive there just needs to be a node-native jet.
-
Adam Back reposted
Artem Chystiakov
@Arvolear
SimplicityHL and Simplex support for Bitcoin jets environment soon.
Artem Chystiakov
@Arvolear
Simplicity is coming to Bitcoin.
signet.simplicity-lang.org -
Adam Back reposted
Bitfinex Securities
@BFXSecurities
No T+2. No closing time. 24/7 instant settlement.
"Why should investing stop when an exchange closes? Why wait two days for a trade to settle when it can settle instantly?"
@KnutsonJesse Head of Operations, Bitfinex Securities
go.bitfinex.com/Bfxs5years -
Adam Back reposted
Danny Scott โก
@CoinCornerDanny
People like to hate, those genuinely here for the Bitcoin mission focus and ignore the noise. ๐ค
Adam Back
@adam3us
here for the cypherpunk, bitcoin mission; some people may not like that ๐คทโโ๏ธ
-
Adam Back reposted
XCE - Connecting Excellence Group
@XCEofficial
ยฃ8.6bn AUM UK investment manager @Premier_Miton has taken a 5.58% stake in XCE.
Premier Miton now holds 28,274,760 XCE shares, crossing the 5% disclosure threshold and becoming a significant institutional shareholder in the Company.
The investment comes as XCE enters its next stage of growth, scaling its recruitment businesses, pursuing acquisitions and building its long-term Bitcoin treasury.
For a company at XCEโs stage, attracting a professional investment manager of Premier Mitonโs scale to the shareholder register is significant.
More to come!
$XCE | AQSE: XCE | OTCQB: XCELF -
Adam Back reposted
Joey Bitcoins
@thejoeybitcoins
A dunk so marvelous it had to be memeโd
Natalie Brunell โก๏ธ
@natbrunell
I didnโt realize journalism meant that every allegation posted on YouTube (often citing anonymous sources) automatically becomes mandatory coverage.
My content is focused on Bitcoin education for the masses, not amplifying every claim that circulates in the community. And when serious accusations are involved, Iโm not interested in trying people in the court of public opinion before the facts are established. Iโm not a lawyer or a detective, and neither are you.
Itโs bizarre to try to assign other creatorsโ coverage and then question their integrity because they didnโt cover a story the way you wanted them to.
Wish you well and hope you kept some Bitcoin. -
Adam Back reposted
Scott Ellam
@btconlyscott
The full talk on @XCEofficial from the @BTCtreasuries conference in New York. An in-depth run through of our disruptive, decentralised, acquisition model.
This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Samson Mow
@Excellion
Yep, no one hates on those that are not accomplishing anything.
-
Adam Back reposted
Jonas Nick
@n1ckler
What if a one-time signature survived a second use? HG-WOTS (pronounced "Hogwots") aims for ~80 bits of security when a key is accidentally used twice. It's 786 bytes, vs. 530 for the WOTS+C in SHRINCS. Mostly a Fable invention. No security proof yet.
Even more interesting than two-time security is HG-WOTS' potential to improve the efficiency of stateless signatures.
Explore HG-WOTS with the following prompt:
Consider HG-WOTS, a hash-chain one-time signature, and study what repeated signing exposes.
Key: k groups of s hash chains (w nodes each). Hash each group's chain endpoints into the start of a secondary "group chain" (w2 nodes); pk = hash of the k group-chain endpoints.
Codeword: choose j hidden groups; each revealed group gets remaining distances with sum d_g; the hidden groups get group-chain distances with total sum d_h. Distances count hash steps to the chain's end (0..w-1, resp. 0..w2-1); codewords are uniform.
Signature: the s chain nodes of each revealed group, and one group-chain node per hidden group. Recovery hashes forward to pk.
Model: an adversary seeing past signatures may only hash forward. A target is derivable iff it hides every group hidden in all past signatures, each revealed chain distance is <= the max exposed on that chain, and each always-hidden group-chain distance is <= the max exposed there (a group revealed once exposes its whole group chain).
Define cover(r) as the probability that a uniform target codeword is derivable from r independent uniform past signatures; explore how cover(r) depends on r and the parameters.This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Jonas Nick
@n1ckler
Stateless signing with HOGWOTS could shrink SPHINCS+-style signatures. With SHRINCS's parameters (SLH-DSA at 2^40 signatures), it's 33% smaller than SLH-DSA and 10% smaller than BPORS+FP, the best published few-time signature. There's no security proof yet.
Prompt to explore the scheme:
Consider HGT (HG-WOTS tree), a few-time signature for stateless SPHINCS+-style schemes, and study what repeated signing exposes. Children: N independent HG-WOTS keys. An HG-WOTS key has k groups of s hash chains (w nodes each); each group's chain endpoints are hashed into the start of a secondary "group chain" (w2 nodes); the child pk is the hash of the k group-chain endpoints. A codeword hides j groups; the remaining distances of each revealed group sum to d_g, and the group-chain distances of the hidden groups sum to d_h in total. Distances count hash steps to the chain's end (0..w-1, resp. 0..w2-1). A child signature is the s chain nodes of each revealed group and one group-chain node per hidden group, 16 bytes per node; recovery hashes forward to the child pk.
Tree: the N child pks are the leaves of a Merkle tree whose root is the public key.
Signing: a hash of the message and a fresh 16-byte randomizer selects K distinct children uniformly and a uniform codeword for each; a separate 32-bit field of the same hash output must be below a threshold tau (grinding). The signature is the randomizer, the K child signatures, and one Merkle multiproof for the K leaves (shared nodes sent once).
Model: an adversary seeing r honest signatures may only hash forward. A forgery attempt is a fresh uniform digest; it succeeds iff it passes the threshold test and every node its signature needs is derivable from earlier signatures by chain steps, compressions and Merkle hashes. Within one child this means: the target hides every group hidden in all of that child's earlier signatures, each revealed chain distance is <= the max exposed on that chain, and each always-hidden group-chain distance is <= the max exposed there (a group revealed once exposes its whole group chain).
Define cover(x) as the probability that a uniform codeword of one child is derivable from x independent uniform earlier signatures of that child. Bound the forgery probability after r signatures in terms of cover, N, K and tau. Then evaluate it for (k,s,w,d_g,j,w2,d_h) = (7,4,16,20,5,8,11), N = 512, K = 4, r = 8: signature size, and the tau that gives 2^-128. Explore how the parameters trade size against security.This media couldn't be displayed. See it on the original post.
Jonas Nick
@n1ckler
What if a one-time signature survived a second use? HG-WOTS (pronounced "Hogwots") aims for ~80 bits of security when a key is accidentally used twice. It's 786 bytes, vs. 530 for the WOTS+C in SHRINCS. Mostly a Fable invention. No security proof yet.
Even more interesting than two-time security is HG-WOTS' potential to improve the efficiency of stateless signatures.
Explore HG-WOTS with the following prompt:
Consider HG-WOTS, a hash-chain one-time signature, and study what repeated signing exposes.
Key: k groups of s hash chains (w nodes each). Hash each group's chain endpoints into the start of a secondary "group chain" (w2 nodes); pk = hash of the k group-chain endpoints.
Codeword: choose j hidden groups; each revealed group gets remaining distances with sum d_g; the hidden groups get group-chain distances with total sum d_h. Distances count hash steps to the chain's end (0..w-1, resp. 0..w2-1); codewords are uniform.
Signature: the s chain nodes of each revealed group, and one group-chain node per hidden group. Recovery hashes forward to pk.
Model: an adversary seeing past signatures may only hash forward. A target is derivable iff it hides every group hidden in all past signatures, each revealed chain distance is <= the max exposed on that chain, and each always-hidden group-chain distance is <= the max exposed there (a group revealed once exposes its whole group chain).
Define cover(r) as the probability that a uniform target codeword is derivable from r independent uniform past signatures; explore how cover(r) depends on r and the parameters.This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Artem Chystiakov
@Arvolear
Simplicity is coming to Bitcoin.
signet.simplicity-lang.org -
Adam Back reposted
Zoro
@ZoroInvesting
If you've been screaming about Metaplanet's "short interest" or complaining about EVO, read Dylanโs post twice.
Japan doesn't have SEC-style ATMs. If you want to issue equity to buy Bitcoin at market price, you have to run an MSW + share borrow structure. The "shorting" you see on the chart is just the counterparty hedging while filling the bid.
More importantly, look at the spread sheet Dylan shared. Cantor, SBI, and Macquarie charge an 8-10% discount on these deals. EVO does it at 0.0% median.
They didn't give away toxic financingโthey negotiated the lowest cost of capital in the entire Japan market.
Dylan LeClair
@DylanLeClair
I'll address this, because there is a fundamental misunderstanding.
In the U.S., an ATM facility lets a bank issue shares on behalf of a company. In Japan, this doesn't exist.
The closest equivalent option is a moving strike warrant. (I.e. adjust to a reference price that moves with the market).
Share borrow enables the counterparty most closely mimic the dynamic of the ATM in the U.S., which enables a much better price (i.e. an ATM fee of 1% is much better than an ATM fee of 4% in the U.S.).
For your reference, here is a table of MSW purchasers in Japan over the last 2 years, with the median and mean discount to the reference price by counterparty.
As the data shows, Evo is are the most prolific purchasers of MSW in Japan; and a look at the mean/median discount to the reference price may inform you as to why.
Hope this helps. -
Adam Back reposted
Bitcoin Treasuries
@BTCtreasuries
JUST IN: Metaplanet $MPJPY independent directors respond to backlash over the 10th Series executive warrants.
"The team purchased warrants at fair value when company finances were uncertain. They were an investment that could have been lost, not a free award."
"Looking only at the exercise price ignores the amount paid, the risk, multi-year vesting, and later lock-up and exercise restrictions."This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Simon Gerovich
@gerovich
Our Independent Directors have published a note to shareholders on the Series 10 warrants, with a Fact Sheet covering their history, their terms, and the changes the Board has made. As the note explains, Metaplanet's founder-led history is important context that much of the recent commentary has missed.
metaplanet.jp/en/announcements/independent-directors-letter
Notably, VanEck has since removed the section of its recent report on the Series 10 warrants, stating that it did not meet its research standards.
With the warrant changes complete, our focus is on the next chapter: evolving Metaplanet into a global financial services innovator powered by Bitcoin. Thank you for your support. Our commitment to communication, transparency, and integrity continues. -
Adam Back reposted
Bitcoin Archive
@BitcoinArchive
JUST IN: ๐บ๐ธ Founder of $300B fund, Ric Edelman, justifies a 10% to 40% allocation to Bitcoin.
"The 40%-60% portfolio is dead because we're living so much longer."
"Advisors have no incentives to risk a relationship for a 1% allocation."This media couldn't be displayed. See it on the original post. -
Adam Back reposted
SideSwap
@side_swap
Good steps from the Liquid Federation. An independent audit of Elements 23.3.4 is underway and the PAK list is being renewed with all peg-out keys in cold storage.
Peg-in is open on SideSwap. Peg-out returns once the new keys are issued and the peg is restored.
Liquid Network ๐
@Liquid_BTC
LIQUID NETWORK UPDATE: ECOSYSTEM ACTIVITY
Status as of September 28, 2026, 05:48 UTC
Security Audit and PAK update
An independent external security audit of Elements v23.3.4 is now underway, providing an additional layer of validation as we work toward the safe restoration of peg-out operations.
In parallel, the Liquid Federation is coordinating an update to the PAK list, including the replacement of existing entries and ensuring all peg out keys are properly secured in cold storage.
These efforts are important steps toward resuming secure peg-out operations. We expect to share further updates on the path to resumption shortly. -
Adam Back reposted
Liquid Network ๐
@Liquid_BTC
LIQUID NETWORK UPDATE: ECOSYSTEM ACTIVITY
Status as of September 28, 2026, 05:48 UTC
Security Audit and PAK update
An independent external security audit of Elements v23.3.4 is now underway, providing an additional layer of validation as we work toward the safe restoration of peg-out operations.
In parallel, the Liquid Federation is coordinating an update to the PAK list, including the replacement of existing entries and ensuring all peg out keys are properly secured in cold storage.
These efforts are important steps toward resuming secure peg-out operations. We expect to share further updates on the path to resumption shortly. -
Adam Back reposted
David Parkinson
@Musqet_David
Run smarter. Pay less.
FROM ยฃ3.25 A DAY. ZERO UP FRONT.
Card rates from 0.25% + 2p for UK personal debit.
ePOS software, hardware, receipt printer and payment terminal, on a 24 or 36 month contract.
Iโm at Hospitality Tech Expo at ExCeL London today, launching Musqetโs new hospitality ePOS packages and reseller offer.
And weโre building towards something bigger. Our 2027 AI roadmap will connect operational data to help venues forecast demand, plan ahead and run a more efficient service.
At ExCeL today? Message me. Whether you run venues or sell into them, letโs talk.
musqet.com/epos
Pricing subject to change. Card processing charges apply separately. Maximum reseller bonus applies to qualifying expanded packages. Terms and conditions apply.
#musqet #hospitalitytech #epos #hospitalitytechexpo #resellersThis media couldn't be displayed. See it on the original post. -
Adam Back reposted
Bitcoin Treasuries
@BTCtreasuries
JUST IN: America's largest #1 investment advisor, Ric Edelman just said he recommends a #bitcoin allocation of up to 40% for his clients.
"A 1% or 2% allocation is way insufficient. We need to increase our allocations."
"We've got the market performance on our side." ๐ฅThis media couldn't be displayed. See it on the original post. -
Adam Back reposted
Strategy
@Strategy
Strategy has acquired 1,665 $BTC and repurchased $152M of $STRC. As of 9/27/26, we hold 847,666 BTC and $6.02B of USD Assets. $MSTR
www.strategy.com/press/strategy-acquires-1665-btc-and-repโฆ -
Adam Back reposted
Capital B
@_ALCPB
๐ Capital B confirms the acquisition of 13 BTC for โฌ0.97 million, the holding of a total of 3,538 BTC, and a BTC Yield of 2.20% YTD โก๏ธ
Full Press Release (EN): cptlb.com/wp-content/uploads/2026/09/rbZj2RjXHd/20260928-โฆ
Full Press Release (FR): cptlb.com/wp-content/uploads/2026/09/AcMj7ouNh2/20260928-โฆ
BTC Strategy (EN): cptlb.com/wp-content/uploads/2026/04/20260430-Capital-B-Fโฆ -
Adam Back reposted
Scott Ellam
@btconlyscott
New York for one day today. Presenting at BTC treasuries conference day - live.
Today @XCEofficial takes the stage at the @BTCtreasuries Conference - SECOND, NYC. A room full of institutional capital allocators, investor media and the leading Bitcoin treasury companies in the world - hosted by @TimKotzman.
2021 we started buying Bitcoin, just over 9 months ago we listed with 9.27BTC. Today I present to the room holding 72.941 BTC, with a proposed acquisition that would double the group and institutions joining the register.
Two sessions:
โ 11:20am ET (4:20pm UK) - my talk: "Buy the Company, Keep the Bitcoin: A New M&A Thesis." How XCE provides a decentralised acquisition model backed by Bitcoin to solve recruitment company owners biggest problems.
โ 11:25am ET - panel: "Digital Credit: The Killer App for Bitcoin," alongside @khingoei and @nico_lechuga, hosted by @TimKotzman
Busy, busy week ahead!
๐บ Watch live: youtube.com/@timkotzman8925/streams
$XCE | AQSE: XCE | OTCQB: XCELF -
Adam Back reposted
XCE - Connecting Excellence Group
@XCEofficial
The treasury community has answered how a company puts Bitcoin on its balance sheet. The question XCE is more interested in answering is what a Bitcoin balance sheet lets you buy.
XCE CEO, @btconlyscott will be presenting his case to the @BTCtreasuries Conference in New York today, on the main stage at 11:20 ET and then later on the digital credit panel with @khingoei and @nico_lechuga, moderated by @TimKotzman.
@adam3us opens the day. Also on the programme: @BlackRock, @vaneck_us, @BBGIntelligence, @CharlesSchwab , @coinbase and @Strive.
The main stage will be livestreamed via the @BTCtreasuries X account and YouTube channel.
$XCE | AQSE: XCE | OTCQB: XCELF -
Adam Back reposted
Bitfinex Securities
@BFXSecurities
Tokenised versions of bitcoin treasury companies trade 24/7.
Capital B
@_ALCPB
๐ Capital B confirms the acquisition of 13 BTC for โฌ0.97 million, the holding of a total of 3,538 BTC, and a BTC Yield of 2.20% YTD โก๏ธ
Full Press Release (EN): cptlb.com/wp-content/uploads/2026/09/rbZj2RjXHd/20260928-โฆ
Full Press Release (FR): cptlb.com/wp-content/uploads/2026/09/AcMj7ouNh2/20260928-โฆ
BTC Strategy (EN): cptlb.com/wp-content/uploads/2026/04/20260430-Capital-B-Fโฆ -
Adam Back reposted
Alexandre Laizet โก๏ธ
@AlexandreLaizet
๐ Capital B $ALCPB has acquired 13 BTC for โฌ0.97 million at โฌ74,364 per bitcoin and has achieved BTC Yield of 2.20% YTD. As of 9/28/2026, Capital B holds 3,538 $BTC for โฌ310.6 million at โฌ87,805 per bitcoinโก๏ธ
$ALCPB Europe's First Bitcoin Treasury Company ๐ซ๐ทโก๏ธ
Capital B
@_ALCPB
๐ Capital B confirms the acquisition of 13 BTC for โฌ0.97 million, the holding of a total of 3,538 BTC, and a BTC Yield of 2.20% YTD โก๏ธ
Full Press Release (EN): cptlb.com/wp-content/uploads/2026/09/rbZj2RjXHd/20260928-โฆ
Full Press Release (FR): cptlb.com/wp-content/uploads/2026/09/AcMj7ouNh2/20260928-โฆ
BTC Strategy (EN): cptlb.com/wp-content/uploads/2026/04/20260430-Capital-B-Fโฆ -
Adam Back reposted
Sakari Puisto
@SakariPuisto
Vierailin BTC Helsinki 2026 tapahtumassa, hyvรค keskustelu Bitcoin - vaikuttajien kanssa!
Daniel Batten
Stephan Kinsella
Adam Back
Remu Karhulahti
Martti Malmi -
Adam Back reposted
Bitfinex Securities
@BFXSecurities
Adam Back's (@adam3us) Hashcash system, built in 1997, is cited in the Bitcoin whitepaper - proof-of-work before Bitcoin existed to need it!
The CEO of Blockstream will speak at The Future of Capital Markets in Lugano on 22 October.
Further details: thefutureofcapitalmarkets.com -
Adam Back reposted
Michael Saylor
@saylor
Out of โฟubblegum.
This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Richard Byworth โ/21M
@RichardByworth
This is misinformation: puts were 1-2 week expiries and were sold when they had cash to buy bitcoin. So rather than buy bitcoin immediately with the cash they were staggering. With an active atm the cash was getting replenished and therefore the strategy could keep running.
This did not cost investors money. -
Adam Back reposted
Core Lightning โก๏ธ
@Core_LN
Core Lightning 26.06.8 is out, and every node runner should upgrade.
This release fixes vulnerabilities responsibly reported over recent weeks. There is no embargo period: the release and fixes are available right now.
A number of tests are being held back temporarily to make the underlying issues harder to reverse-engineer while node runners have time to upgrade.
Please upgrade as soon as possible.
github.com/ElementsProject/lightning/releases/tag/v26.06.8 -
Adam Back reposted
Artem Chystiakov
@Arvolear
Simplicity website got a refresh! All the tooling and research projects are in one place now. Go check out what can be built with SimplicityHL!
simplicity-lang.org -
Adam Back reposted
GTAmemes
@GTAmemesSOL
BTC bulls just unlocked a new mission. @adam3us & @saylor got this
This media couldn't be displayed. See it on the original post.
Michael Saylor
@saylor
Friends donโt let friends short Bitcoin.
This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Scott Ellam
@btconlyscott
Today @XCEofficial mNAV sits at ~2.5x, with the share price up 30โ40% mid-session following yesterday's news.
More importantly, and for the long term: when a business's revenue is directly correlated with headcount, a listed status and a Bitcoin treasury become a serious combination - one I believe will grow more and more appealing to recruitment company acquisition targets and to the highest-performing, revenue-generating recruiters over a long enough time horizon.
I've had positive meetings in London this week - and I believe the understanding of our model will continue to increase.
Lots of work ahead. But this is a unique opportunity to disrupt a global industry with Bitcoin.
AQSE: XCE / OTCQB: XCELF -
Adam Back reposted
Jess โ
โ
โ
โ
โ
@starb0ySOL
Hahaha @adam3us you made it in this GTA mission
-
Adam Back reposted
Coinjoined Chris โก
@coinjoined
> be Portland
> propose sane Bitcoin improvement
> get ignored
> Dash, Crash and Fork copy it
> bolt on a dozen insane extras
> accidentally turn it into a self-weeding garden
> only nincompoops opt in
> they fork themselves off
> Bitcoin improves -
Adam Back reposted
BTCSchellingpt
@BTCSchellingpt
@adam3us warned explicitly this was the risk they took with Emperor Luke
-
Adam Back reposted
Scott Ellam
@btconlyscott
ยฃ600,000 raise announced this morning.ย
ย
Taking our total raised for September so far over ยฃ1.25m @xceofficial.ย
ย
โ Institutions led this equity raise - at a 3.4% premium to last nightโs closeย
โ @adam3us bought another 13,333,333 shares - his second purchase this month
ย
โ Funds supporting the Bitcoin treasury, acquisitions and hiring - including the proposed acquisition of another recruitment company, which generated ยฃ1.79m revenue and ยฃ431k EBITDA in the last 12 months, holds 8.216 BTC and would double the operating business (subject to completion)ย
ย
We are focused on growing revenue in the operating business with our decentralised recruitment acquisition model - and simultaneously increasing the BTC on the balance sheet.ย
ย
We are targeting an uplisting in due course.ย ย
AQSE: XCE / OTCQB: XCELF -
Adam Back reposted
Dan Tapiero
@DTAPCAP
Pretty straightforward for BTC.
Textbook cup and handle breakup.
An entire year of selling just swallowed up in the past 5 weeks.
Bears and shorts F-ed.
Solid break of 100k goes right back to 120k.
Could even be this year. -
Adam Back reposted
BTSE
@BTSE_Official
Update: BTSE has resumed USDT deposits and withdrawals on the Liquid Network.
We believe the recent security incident and underlying vulnerabilities have been largely resolved. Blockstream identified and patched the underlying Elements software bug, and the network has been stable since.
Normal services for USDT on Liquid have been restored. @Liquid_BTC @Blockstream
Liquid Network ๐
@Liquid_BTC
LIQUID NETWORK UPDATE: ECOSYSTEM ACTIVITY
Status as of September 17, 2026, 21:05 UTC
Network and Ecosystem Status
Since resuming on September 10, block production and network transactions, including LBTC transfers, have operated normally. Peg-out operations remain paused while work continues with Federation members and partners toward their safe restoration. Markets and services across the ecosystem are back online.
@mifielfirma has resumed the issuance and transactions of its digital promissory notes, with batches confirming normally. At the exchange level, @BTSE_Official reports that its platform has re-enabled USDT-Liquid transfers and the asset is unaffected by the incident.
@AquaBitcoin reports that Liquid asset transfers and peg-ins are available. Its new swap feature, Indra, is also live, enabling swaps between LBTC and Lightning BTC, although liquidity remains limited.
Other wallets are restoring core functionality as well. @BULLBITCOIN_ and the @Blockstream App report that Liquid asset transfers are available, although LBTC<>BTC and LBTC<>Lightning swap routes on those services remain unavailable until peg-outs are restored.
Meanwhile, other non-LBTC swap services are returning, with @sideshiftai re-enabling cross-chain swaps for $USDT and $DEPIX on Liquid.
Please note service availability varies by provider, and users should confirm deposit, withdrawal and swap availability through each providerโs official channels.
BTC Recovery and Peg-Outs
As previously reported, 3,400 BTC of the ~4,000 BTC withdrawn on September 6 has been returned to the Federation reserve. Approximately 600 BTC remains unreturned, and efforts to pursue its recovery continue.
We understand that the central question for LBTC holders is when peg-outs will resume. While we are not yet able to provide a firm date, peg-outs will resume only after full 1:1 BTC backing for LBTC has been confirmed and all required software updates, testing and independent security reviews have been completed.
The Liquid Federation members and Blockstream will share the plan and timing for resuming peg-outs as soon as they are finalized.
Technical Post-Mortem
The root cause and exploit path have been identified, and the immediate fix was released in Elements v23.3.4. A comprehensive technical report detailing the incident will be released as soon as it is available.
Thank You
The Liquid Federation and Blockstream sincerely thank Federation member companies, ecosystem operators, developers, security researchers, and users for their continued work, patience and support throughout the recovery process. -
Adam Back reposted
Artem Chystiakov
@Arvolear
We have overhauled, updated, and cleaned up the Simplicity docs website. Go learn how to write your first SimplicityHL smart contract!
docs.simplicity-lang.org -
Adam Back reposted
Alistair Milne
@alistairmilne
To recap:
- Fed raised interest rates
- Clarity act failed
- Bitcoin didn't go below $75k
Thank you for your attention to this matter -
Adam Back reposted
Scott Ellam
@btconlyscott
It has been very busy since our announcements - I have been locked in on recruitment, progressing with the acquisition and setting @XCEofficial ready to embrace the (absolutely inevitable but not certain on timescales) bull-run.
I do not usually take much notice of the short-term Bitcoin price - it (I believe) will hit ยฃ1m within the next decade - but it's been pretty wild to watch it respond positively to the Fed's rate rise this week (it should, we know, but it usually doesn't). And first hand, on the ground, there is a marked difference in institutional awareness and engagement in the asset class.
Busy with the real work following the announcements of our flagship firm Spencer Riley's revenues up 20.6%, the proposed acquisition that would effectively double the group and the Bitcoin on the balance sheet up to 72.94 BTC.
Inside Spencer Riley - full team sessions this week, and great progress from the cohort of four experienced hires. Looking forward to watching them develop in the business - and there is a pipeline of billers proactively coming to us now. Bitcoin upsides going to get more and more attractive. Also found that an internal GPT I set up years ago has had ~1,000 uses in the business - and we've recently embedded Ai far deeper into the business. I believe this will be a huge strength as we bring more recruiters, and companies into the group.
Bitcoin is genuinely becoming normalised:
โ We're partnered with world-renowned clients on digital asset roles - from senior sales through to C-suite
โ Traditional client insight - pioneering technology manufacturing businesses - telling us the Bitcoin balance sheet strategy is incredibly interesting, and asking how they might do something similar in the future
โ The traditional UK investment funds - experts in bonds, commodities and conventional assets - now seem to have an intuitive understanding of the scope of Bitcoin. And they are bullish.
The world is changing rapidly in 2026. Over the next four years we are going to see businesses embracing AI for operational scaling and efficiency, and Bitcoin for balance sheet strength and optionality. And of course your going to see a lot who don't.
Unchartered Bitcoin territory Podcast:
I was invited onto @WardHadaway Fastest 50 North Podcast - a leading law firm, and a seriously interesting conversation given the level of commercial experience of the partners who host it. It would be great for Bitcoiners to see how engaged they were in the topic - they brought up Weimar comparisons and everything you'd see on a Bitcoin pod.
And next week I'll be speaking at @BtcCorpDay alongside @adam3us on a panel about Bitcoin on the balance sheet.
$XCE | AQSE: XCE | OTCQB: XCELF -
Adam Back reposted
James Van Straten
@btcjvs
Bitcoin has stopped making new lows on bad news. Therefore, the bottom has been in for some time.
The low was back in February, but a lack of liquidity during the summer pushed it lower by a few percent.
We've had hacks, hikes, Clarity failure and an AI meltdown.
We're now in the weakest seasonal month and approaching the four-year cycle bottom in October, where compression should really occur.
It's over for the bears. -
Adam Back reposted
Bugle.News ๐ฏ
@bitcoin_bugle
Don't take the black pill
This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Antoine Poinsot
@darosior
BIP54 would make it so Bitcoin's PoW actually provides tight bounds on worst case resource usage.
Read Pieter's latest post on Delving. -
Adam Back reposted
Liquid Network ๐
@Liquid_BTC
LIQUID NETWORK UPDATE: ECOSYSTEM ACTIVITY
Status as of September 17, 2026, 21:05 UTC
Network and Ecosystem Status
Since resuming on September 10, block production and network transactions, including LBTC transfers, have operated normally. Peg-out operations remain paused while work continues with Federation members and partners toward their safe restoration. Markets and services across the ecosystem are back online.
@mifielfirma has resumed the issuance and transactions of its digital promissory notes, with batches confirming normally. At the exchange level, @BTSE_Official reports that its platform has re-enabled USDT-Liquid transfers and the asset is unaffected by the incident.
@AquaBitcoin reports that Liquid asset transfers and peg-ins are available. Its new swap feature, Indra, is also live, enabling swaps between LBTC and Lightning BTC, although liquidity remains limited.
Other wallets are restoring core functionality as well. @BULLBITCOIN_ and the @Blockstream App report that Liquid asset transfers are available, although LBTC<>BTC and LBTC<>Lightning swap routes on those services remain unavailable until peg-outs are restored.
Meanwhile, other non-LBTC swap services are returning, with @sideshiftai re-enabling cross-chain swaps for $USDT and $DEPIX on Liquid.
Please note service availability varies by provider, and users should confirm deposit, withdrawal and swap availability through each providerโs official channels.
BTC Recovery and Peg-Outs
As previously reported, 3,400 BTC of the ~4,000 BTC withdrawn on September 6 has been returned to the Federation reserve. Approximately 600 BTC remains unreturned, and efforts to pursue its recovery continue.
We understand that the central question for LBTC holders is when peg-outs will resume. While we are not yet able to provide a firm date, peg-outs will resume only after full 1:1 BTC backing for LBTC has been confirmed and all required software updates, testing and independent security reviews have been completed.
The Liquid Federation members and Blockstream will share the plan and timing for resuming peg-outs as soon as they are finalized.
Technical Post-Mortem
The root cause and exploit path have been identified, and the immediate fix was released in Elements v23.3.4. A comprehensive technical report detailing the incident will be released as soon as it is available.
Thank You
The Liquid Federation and Blockstream sincerely thank Federation member companies, ecosystem operators, developers, security researchers, and users for their continued work, patience and support throughout the recovery process. -
Adam Back reposted
AQUA Bitcoin en Espaรฑol
@AquaBitcoinES
El lรญmite en los swaps de Liquid a Lightning en AQUA se ha incrementado de 70k Sats a 100k Sats por transacciรณn. โก
Ahora puedes enviar pagos de Lightning mรกs grandes durante la beta abierta de Indra.
Seguiremos monitoreando la liquidez para seguir ampliando la capacidad. ๐ซก -
Adam Back reposted
AQUA Wallet
@AquaBitcoin
The Liquid-to-Lightning swap limit in AQUA Wallet has been increased from 70k Sats to 100k Sats per transaction. โก
This update allows you to send larger Lightning payments while Indra remains in open beta.
We will continue monitoring liquidity as we expand swap capacity further. ๐ซก -
Adam Back reposted
Core Lightning โก๏ธ
@Core_LN
Security Advisory: We are investigating reports of a potential issue affecting experimental features in Core Lightning that may impact user funds.
We urge all Core Lightning users running experimental features to disable them immediately while we investigate. -
Adam Back reposted
Michael Ford
@fanquake
> Bitcoin Core has spent more than a century of CPU time fuzzing individual functions and critical components (though oss-fuzz, Fuzzor, bitcoinfuzz and individual contributors), and decades of CPU time simulating small networks of full nodes under test (Antithesis, Fuzzamoto). I canโt establish causality from this alone, but my strong suspicion is that the sustained testing effort is an important reason these projects have become so robust.
Niklas Gรถgge
@dergoegge
I wrote a blog post on the recent exploits in the Bitcoin ecosystem, how Bitcoin Core is holding up, and how I think the community can get ahead of the models:
www.dergoegge.de/blog/somethings-been-bugging-me.html -
Adam Back reposted
SideSwap
@side_swap
USDt on Liquid is moving on Bitfinex again. Deposits and withdrawals of Liquid USDt are live and working, so you can move USDt between Bitfinex and your SideSwap wallet in both directions. L-BTC deposits and withdrawals on Bitfinex remain paused for now.
-
Adam Back reposted
Arnab Naskar @stokr
@Arnab_Naskarr
These last few days, the @Blockstream team, the Liquid functionaries, and network partners have shown real sincerity and professionalism - we've been in constant dialogue throughout. Deeply grateful.
The work isn't done yet and everyone is aware
Samson Mow
@Excellion
The top priority for the Liquid Federation has been to restore network operations. While it would have been ideal to have peg operations back as well, enabling transactions was critical, as @Liquid_BTC is much more than just L-BTC. In addition to stablecoins, there are nearly $5B in RWAs originating from groups like @stokr_io and @mifielfirma and trading on @BFXSecurities that depend on the network running smoothly. ๐
Mifiel
@mifielfirma
Backing close to $5B+ USD in digital promissory notes (pagarรฉs) on @Liquid_BTC, uptime is vital for us.
We began broadcasting our queued issuance transactions, and batches are clearing cleanly.
Huge credit to @Blockstream & all 15 functionaries for the quick recovery. -
Adam Back reposted
FRANCIS โ๏ธ BULLBITCOIN.COM
@francispouliot_
BULL just upgraded its CLN nodes used by the exchange. We never shut them down. We did security reviews early august and had temporarily prevented new channel opens to mitigate risks. Thanks @Core_LN for the patch! People should upgrade. We also upgraded LND too.
-
Adam Back reposted
Samson Mow
@Excellion
More progress on @Liquid_BTC services being restored in @AquaBitcoin. Thank you @sideshiftai! ๐ฌโค๏ธ
AQUA Wallet
@AquaBitcoin
Cross-chain swaps for USDT on @Liquid_BTC are back online via @sideshiftai.
AQUA Wallet users can now move Liquid USDT across supported networks as usual.
We will continue sharing updates as remaining integration partners reactivate their services. -
Adam Back reposted
Kuru
@satoshi_kuru
โก๏ธCAPITAL B I Snow Crashโก๏ธ
@_ALCPB
@AlexandreLaizet
@Kosanovic_V
@adam3us
@dannyfonse
@LudoCL1
www.youtube.com/watch?v=dgXsZBFerms
#capitalb #alcpb #btc #satoshi #btctc
$ALCPB ๐ซ๐ท $CPTLF ๐บ๐ธ $CALCPB ๐บ๐ธ -
Adam Back reposted
Samson Mow
@Excellion
The top priority for the Liquid Federation has been to restore network operations. While it would have been ideal to have peg operations back as well, enabling transactions was critical, as @Liquid_BTC is much more than just L-BTC. In addition to stablecoins, there are nearly $5B in RWAs originating from groups like @stokr_io and @mifielfirma and trading on @BFXSecurities that depend on the network running smoothly. ๐
Mifiel
@mifielfirma
Backing close to $5B+ USD in digital promissory notes (pagarรฉs) on @Liquid_BTC, uptime is vital for us.
We began broadcasting our queued issuance transactions, and batches are clearing cleanly.
Huge credit to @Blockstream & all 15 functionaries for the quick recovery. -
Adam Back
@adam3us
thanks for kind words. we understand regulated entities and market functions need it. so we focused on resumption stage first, to get assets, securities, notes etc online faster. and ofc users of stable coins, and other swap functions.
Adam Back
@adam3us
Mifiel
@mifielfirma
Backing close to $5B+ USD in digital promissory notes (pagarรฉs) on @Liquid_BTC, uptime is vital for us.
We began broadcasting our queued issuance transactions, and batches are clearing cleanly.
Huge credit to @Blockstream & all 15 functionaries for the quick recovery. -
Adam Back reposted
AQUA Wallet
@AquaBitcoin
The @Liquid_BTC Network has officially entered a controlled resumption phase following successful software updates by @Blockstream and node operators.
Block production and transaction processing have resumed, and direct Liquid to Liquid transactions are now confirming on the network.
USDT and DePix are now back online. Peg-in and peg-out operations remain temporarily suspended while efforts to restore full 1:1 reserve backing continue.
While out-of-band peer-to-peer transfers are technically possible on-chain, we strongly advise against conducting manual L-BTC swaps at a discounted ratio, as active work is underway to restore full backing.
What this means for you as an AQUA Wallet user:
โช๏ธ Liquid to Liquid and native on-chain Bitcoin transactions are fully functional
โช๏ธ Peg operations remain temporarily paused
โช๏ธ Swaps (all pairs) inside the app will function if dealers are online and liquidity available
โช๏ธ Liquid USDT swaps across chains should work as usual as soon as the liquidity providers enable them
โช๏ธ Your private keys remain completely secure throughout this process
While we are working on restoring full service, please remain vigilant against phishing scams and fake update sites. AQUA team members will never ask for your seed phrase or send unsolicited direct messages. -
Adam Back reposted
Liquid Network ๐
@Liquid_BTC
LIQUID NETWORK UPDATE: TRANSACTIONS RESUMED, PEG-OUTS DISABLED
Status as of September 10, 2026, 19:55 UTC
Recovery Status
The Liquid Network has entered into its next recovery phase. Block production has resumed, and functionary nodes are signing and validating blocks. Transactions on the network have resumed, while peg-outs remain disabled as a precautionary measure while the final stage of recovery continues.
Rigorous testing, AI-assisted code scanning, and continuous network monitoring are underway by internal and external teams. Further information on the resumption of peg-outs will be shared once available.
Important: What You Should Know
Users do not need to take any proactive steps at this time. If you operate a Liquid node, please update to Elements v23.3.4 immediately.
Reminder: Beware of Scams
There are reports of scammers attempting to exploit the situation through fraudulent update sites and messages. Please rely only on official Liquid Network, Blockstream Jade, and Blockstream channels. Never send funds to unfamiliar addresses, transfer assets to unknown channels, or disclose private keys or seed phrases in response to unsolicited communications.
More Updates Soon
Updates will be shared through official Liquid Network and Blockstream channels. The Liquid Federation and Blockstream again sincerely thank the broader Bitcoin community for its continued assistance and support during this recovery.
Liquid Network ๐
@Liquid_BTC
LIQUID NETWORK UPDATE: OPERATIONS RESUMED, RECOVERY ONGOING
Status as of September 10, 2026, 10:00 UTC
Recovery Status
The Liquid Network has entered the next phase of its controlled resumption. As a precautionary measure, block production has resumed without transactions while the network is monitored to confirm full stabilization.
Blockstream confirms that the required functionary and bridge node updates have been successfully deployed. Functionary nodes are signing and validating blocks as intended.
Peg operations, including PAK-authorized peg-outs, remain suspended while work continues on the final recovery stage: restoring the BTC/LBTC reserve is in progress.
Reminder: Beware of Scams
There are reports of scammers attempting to exploit the situation through fraudulent update sites and messages. Please rely only on official Liquid Network and Blockstream channels. Never send funds or disclose private keys or seed phrases in response to unsolicited communications.
Thank You
The Liquid Federation and Blockstream sincerely thank the broader Bitcoin community and security teams for their assistance and continued support during this challenging time.
Safely restoring full operations remains the highest priority. -
Adam Back reposted
Mifiel
@mifielfirma
Backing close to $5B+ USD in digital promissory notes (pagarรฉs) on @Liquid_BTC, uptime is vital for us.
We began broadcasting our queued issuance transactions, and batches are clearing cleanly.
Huge credit to @Blockstream & all 15 functionaries for the quick recovery. -
Adam Back reposted
SideSwap
@side_swap
Liquid is producing blocks again and SideSwap markets are open. Swaps work as before. New peg-ins and peg-outs stay closed while the Federation's security review is done.
On L-BTC backing and what to expect from our markets: sideswap.io/news/sideswap-markets-reopen-with-the-liquid-โฆ -
Adam Back reposted
STOKR
@stokr_io
Liquid Network is back online. Block production resumed today, 10 September 2026 at 10:00 UTC, and the network is operating normally again.
The pause affected on-chain settlements only. Holdings of digital securities issued through STOKR are unchanged, and settlements on-chain have resumed.
Our team continues to monitor the network and remains on alert.
STOKR
@stokr_io
Following the latest official update from the Liquid Network, 3,400 BTC have been returned to the federation peg wallet, with approximately 598.5 BTC still outstanding.
For STOKR, the impact remains limited to network availability. Digital securities holdings and issuance records are intact, no unauthorised issuance has taken place, and platform operations including onboarding, whitelisting and reporting continue to run normally.
The Liquid Network remains paused, so on-chain transfers are temporarily unavailable until network operations resume. Any transfer submitted in the meantime stays pending and will not be lost.
@Blockstream and @Liquid_BTC remain the authoritative sources on the incident itself. STOKR will continue to update on any impact relevant to our users and services.
Read our full update stokr.io/stoke-post/liquid-network-incident -
Adam Back reposted
Rob Warren
@BikesandBitcoin
The entire incentive of mining bitcoin is profit.
You only mine bitcoin at scale if the asset you generate is worth more than the cost to produce it.
Section 6 of the whitepaper makes this clear.
You canโt remove the profit motive from a functioning bitcoin network!
zender โ๏ธ
@zndtoshi
The Emperror has spoken. He wants to change the issuance of his network.
-
Adam Back reposted
Bitkit
@bitkitwallet
Somebody paid 80 cents to write eight words into the Bitcoin blockchain:
"we are whitehats. contact us on chain."
Four hours earlier they had walked out of Liquid with 3,998 BTC. $320 million. 95% of everything in the vault.
They didn't steal a key. They didn't break the 11-of-15 federation. What happened next has no precedent.
We made a 6-minute film about it. ๐บThis media couldn't be displayed. See it on the original post. -
Adam Back reposted
Peter Scott-Morgan
@P_ScottMorgan
BlukeCoiners: SpAmCoIn iS cApTuReD
Also BlukeCoin CEO:
AlphaMine
@TwhitNub101
@LukeDashjr @GrassFedBitcoin @cguida6
The CEO of $XBT does not like data. Not sure how much I can help beyond that folks ๐คทโโ๏ธ -
Adam Back reposted
Bitcoin Treasuries
@BTCtreasuries
JUST IN: $350B Edelman Financial founder Ric Edelman is confirmed to speak at the Bitcoin Treasuries Conference on Sept 28 in NYC.
He built America's largest RIA, serving 1.4M families, and is coming on stage to break down why RIAs will drive billions into #bitcoin.
Reserve your seat now and get 10% off using the link in the comments: -
Adam Back reposted
Phong Le
@phongle
Major development at the intersection of DeFi and TradFi, crypto and Bitcoin.
Bloomberg
@business
Nasdaq is investing $100 million in Payward, the parent of cryptocurrency exchange Kraken www.bloomberg.com/news/articles/2026-09-10/nasdaq-investsโฆ
-
Adam Back reposted
AQUA Wallet
@AquaBitcoin
New phishing emails targeting @Liquid_BTC users. ๐จโ ๏ธ
Threat actors are directing users to fake update sites to trick them into installing malicious software.
Never download executable files from email links, and always rely on official channels for updates.
Jameson Lopp
@lopp
๐จNew Scam Alert๐จ
Threat actors are sending out emails directing people to a "mandatory security update" site for Liquid Network that tries to trick you into downloading and running a malicious .exe file. /cc @Liquid_BTC -
Adam Back
@adam3us
so quickly... [if you enable him] "YOU will be peers @lukedashjr is immune to feedback from. and I believe it's a near CERTAINTY this will bite you all within a surprisingly short time-frame"
ndeet โ/21M
@ndeet
At this point even Ethereum has a more predictable subsidy schedule, lmao.
Adam Back
@adam3us
receipts from before the fork
Adam Back
@adam3us
something for knots promoters to muse on: @lukedashjr being a 10th man, immune to peer pressure is a feature. BUT if you enable him, YOU will be peers he is immune to feedback from. and I believe it's a near CERTAINTY this will bite you all within a surprisingly short time-frame.
-
Adam Back reposted
-
Adam Back
@adam3us
@liquid_btc network resumption coming up.
obvious question will LBTC:BTC 1:1 peg be covered; answer YES, so do not panic sell OTC as @PabloSGreco and team are working on more system updates to resume the peg in/out, which happens in a later step.
Adam Back
@adam3us
@liquid_btc security release coming up, with network resumption plan. been a busy few days, more details to come.
Adam Back
@adam3us
Liquid Network ๐
@Liquid_BTC
LIQUID NETWORK UPDATE: OPERATIONS RESUMED, RECOVERY ONGOING
Status as of September 10, 2026, 10:00 UTC
Recovery Status
The Liquid Network has entered the next phase of its controlled resumption. As a precautionary measure, block production has resumed without transactions while the network is monitored to confirm full stabilization.
Blockstream confirms that the required functionary and bridge node updates have been successfully deployed. Functionary nodes are signing and validating blocks as intended.
Peg operations, including PAK-authorized peg-outs, remain suspended while work continues on the final recovery stage: restoring the BTC/LBTC reserve is in progress.
Reminder: Beware of Scams
There are reports of scammers attempting to exploit the situation through fraudulent update sites and messages. Please rely only on official Liquid Network and Blockstream channels. Never send funds or disclose private keys or seed phrases in response to unsolicited communications.
Thank You
The Liquid Federation and Blockstream sincerely thank the broader Bitcoin community and security teams for their assistance and continued support during this challenging time.
Safely restoring full operations remains the highest priority. -
Adam Back reposted
SideSwap
@side_swap
Liquid update: Adam Back says the L-BTC:BTC peg will be covered 1:1; peg-in/out returns later.
When blocks flow, SideSwap swaps and markets open, in-flight pegs are released and DePix issuance and redemption are live. New pegs stay closed. Details: t.me/SideSwap_io/18711 -
Adam Back reposted
Tyler
@TylerDurden
There is no second best.
This media couldn't be displayed. See it on the original post. -
Adam Back reposted
โฟthemoon | โ vs 21m | Capital โฟear Stackers member
@Bthemoon2030
@adam3us i am trying so hard to outrun your sharecount but everytime i buy a million you buy 25 million ๐คฃ
-
Adam Back reposted
Valentin Kosanovic
@Kosanovic_V
Capital B @_ALCPB ranks #9 among 1,800+ companies listed across Euronext Europe by 20-day average daily trading volume relative to market capitalization (excl. microcaps <โฌ100m).
With โฌ1.9m in 20-day ADTV for a โฌ207m market capitalization, nearly 1% of Capital Bโs market cap trades every day on average.
In other words, it takes on average roughly 100 trading days for Capital B to trade its entire current market cap.
Working relentlessly to deliver the very โฟest products, develop the widest accessibility and deepest liquidity, and maximize the number of bitcoin per fully diluted share over time for our shareholders.
Onward! โ๏ธ
Capital B @_ALCPB, Europeโs First Bitcoin Treasury Company ๐ง -
Adam Back reposted
Alexandre Laizet โก๏ธ
@AlexandreLaizet
Bienvenue @NCheron_bourse !โก๏ธ
Nicolas Chรฉron
@NCheron_bourse
Je suis devenu actionnaire de Capital B.
Ceux qui me suivent savent que je mโintรฉresse au Bitcoin depuis des annรฉes, mais รฉgalement aux diffรฉrentes maniรจres de sโy exposer.
Capital B a fait un choix assez radical : lever des capitaux pour accumuler du Bitcoin et construire progressivement une rรฉserve stratรฉgique en BTC.
La sociรฉtรฉ cherche ร utiliser les marchรฉs de capitaux pour augmenter progressivement son exposition au Bitcoin et, si la stratรฉgie fonctionne, crรฉer davantage de valeur pour ses actionnaires que la simple dรฉtention de BTC.
Autre point, le lancement du digital crรฉdit a dรฉjร รฉtรฉ largement รฉvoquรฉ par Alexandre Laizet @AlexandreLaizet directeur gรฉnรฉral dรฉlรฉguรฉ de Capital B. C'est un information publique, et que Capital B ait la volontรฉ de sโy lancer est un point d attraction majeur pour les investisseurs dont je fais partie.
Jโapprรฉcie รฉgalement le fait de retrouver autour du projet des acteurs reconnus de lโรฉcosystรจme, notamment Adam Back @adam3usย , figure historique de Bitcoin, ainsi que Yves Choueifaty prรฉsident et fondateur de TOBAM, sociรฉtรฉ de gestion prรฉsente depuis longtemps dans lโunivers des actifs numรฉriques.
รvidemment, ce modรจle ajoute aussi des risques : risque de marchรฉ, dilution lors des levรฉes de capitaux, volatilitรฉ de lโaction, valorisation parfois dรฉcorrรฉlรฉe de celle des bitcoins dรฉtenusโฆ Capital B nโest pas du Bitcoin et acheter lโaction nโรฉquivaut pas ร acheter directement du BTC.
Cet investissement fait partie de ma poche crypto long terme, aux cรดtรฉs d'une participation dans le mรฉdia crypto de rรฉfรฉrence @TheBigWhale_ย
Ci-dessous le graphique mensuel de l'action, -90% post bear market, dont on ne sait pas s'il est terminรฉ d'ailleurs.
Second graphique, en journalier, une sorte de dรฉbut de rounding bottom est possiblement en train de se former, d'oรน mon entrรฉe rรฉcente (qui se fera en plusieurs fois dans les mois ร venir).ย
โก๏ธ Cette publication n'est pas un conseil en investissement.
โก๏ธ Investir comporte des risques, ne pas investir assure de perdre face ร l'inflation. -
Adam Back reposted
Jonas Nick
@n1ckler
gpg --verify SHA256SUMS.asc
is easily bypassable for detached signatures.
The correct command requires the data file:
gpg --verify SHA256SUMS.asc SHA256SUMS
This appears to be a common mistake.
Without the second argument, gpg succeeds even if the .asc file contains an arbitrary embedded message rather than signing the actual SHA256SUMS file. It prints a warning, but it's easily missed in gpg's output.
The gpg manpage explicitly discourages the single-argument form, keeping it only for backward compatibility. I actually keep a list of gpg pitfalls. This is number 8.
Mehdi Kerimov reported this in nix-bitcoin's self-updater via @nixbitcoinorg's bounty program. We had originally followed bitcoincore.org verification instructions, which had the same issue and have since been fixed. That this sat unnoticed on @bitcoincoreorg since 2018 shows just how little-known this footgun is.
It's unlikely bad signatures were ever published at scale, as anyone noticing the warning or using the two-argument command would have caught it immediately. -
Adam Back reposted
Blockstream
@Blockstream
Security Notice & Phishing Alert
Following the recent Liquid Network incident, scammers are impersonating Liquid and Blockstream and urging users to "take action." Don't.
Blockstream will never ask for your recovery phrase or PIN, ask you to send funds, or provide a link for updated software.
Never - Send funds to a "recovery" address
Never - Enter your seed on a "migration" site
Never - Install firmware or software from an email link
Never - Reply to unsolicited DMs
Treat as scams: "mandatory security update" emails and portals, refund / re-peg / "claim L-BTC" sites, fake support DMs, lookalike domains, and unsolicited "white-hat" or bounty outreach.
For verified updates, go only to blockstream.com or the official Blockstream app from the official app stores. -
Adam Back reposted
Nicolas Chรฉron
@NCheron_bourse
Je suis devenu actionnaire de Capital B.
Ceux qui me suivent savent que je mโintรฉresse au Bitcoin depuis des annรฉes, mais รฉgalement aux diffรฉrentes maniรจres de sโy exposer.
Capital B a fait un choix assez radical : lever des capitaux pour accumuler du Bitcoin et construire progressivement une rรฉserve stratรฉgique en BTC.
La sociรฉtรฉ cherche ร utiliser les marchรฉs de capitaux pour augmenter progressivement son exposition au Bitcoin et, si la stratรฉgie fonctionne, crรฉer davantage de valeur pour ses actionnaires que la simple dรฉtention de BTC.
Autre point, le lancement du digital crรฉdit a dรฉjร รฉtรฉ largement รฉvoquรฉ par Alexandre Laizet @AlexandreLaizet directeur gรฉnรฉral dรฉlรฉguรฉ de Capital B. C'est un information publique, et que Capital B ait la volontรฉ de sโy lancer est un point d attraction majeur pour les investisseurs dont je fais partie.
Jโapprรฉcie รฉgalement le fait de retrouver autour du projet des acteurs reconnus de lโรฉcosystรจme, notamment Adam Back @adam3usย , figure historique de Bitcoin, ainsi que Yves Choueifaty prรฉsident et fondateur de TOBAM, sociรฉtรฉ de gestion prรฉsente depuis longtemps dans lโunivers des actifs numรฉriques.
รvidemment, ce modรจle ajoute aussi des risques : risque de marchรฉ, dilution lors des levรฉes de capitaux, volatilitรฉ de lโaction, valorisation parfois dรฉcorrรฉlรฉe de celle des bitcoins dรฉtenusโฆ Capital B nโest pas du Bitcoin et acheter lโaction nโรฉquivaut pas ร acheter directement du BTC.
Cet investissement fait partie de ma poche crypto long terme, aux cรดtรฉs d'une participation dans le mรฉdia crypto de rรฉfรฉrence @TheBigWhale_ย
Ci-dessous le graphique mensuel de l'action, -90% post bear market, dont on ne sait pas s'il est terminรฉ d'ailleurs.
Second graphique, en journalier, une sorte de dรฉbut de rounding bottom est possiblement en train de se former, d'oรน mon entrรฉe rรฉcente (qui se fera en plusieurs fois dans les mois ร venir).ย
โก๏ธ Cette publication n'est pas un conseil en investissement.
โก๏ธ Investir comporte des risques, ne pas investir assure de perdre face ร l'inflation. -
Adam Back reposted
Cointelegraph
@Cointelegraph
๐จ TODAY: Billionaire Grant Cardone puts his private jet up for sale at 1,025 $BTC.
-
Adam Back
@adam3us
@liquid_btc security release coming up, with network resumption plan. been a busy few days, more details to come.
Adam Back
@adam3us
initial details
Liquid Network ๐
@Liquid_BTC
LIQUID NETWORK UPDATE: NEW RELEASE
Status as of September 9, 2026, 13:30 UTC
Update to Elements v23.3.4
The emergency Elements v23.3.4 release is now available. Functionary nodes are being updated immediately and we recommend all Liquid node runners do the same. This release addresses the proof-verification cache vulnerability, hardening the cache keys used for range proofs.
Elements v23.3.4 has undergone multiple rounds of internal and external review, including by the Bitcoin Red Team, Alpen Labs and others. Blockstream sincerely thanks these teams for their valuable review and collaboration.
Liquid Network Recovery Plan
The recovery plan remains under active development and may be revised as testing and validation continue. Based on current assessments, the anticipated stages are:
1) Resume block production while peg operations remain suspended.
2) Replay transactions verified as valid.
3) Resume peg operations once the network state has been fully restored including a return of funds.
Blockstream is testing the procedures for the first two stages in parallel. While the current plan anticipates proceeding in the order above, the sequencing and implementation may be adjusted based on the results. No stage will proceed until it is considered safe to advance.
Beware of Scams
There are reports of scammers attempting to exploit this situation by misleading users with fake update sites. This is a reminder to only rely on official Liquid Network and Blockstream channels, and never send funds or disclose private keys or seed phrases in response to unsolicited messages.
We again thank the broader Bitcoin community and our research collaborators for their continued support and assistance. Safely restoring normal operations remains the highest priority for the Liquid Federation and Blockstream.
github.com/ElementsProject/elements/releases -
Adam Back reposted
Robin Linus โ
@robin_linus
The Liquid hack is not an argument against privacy features.
The cryptography wasnโt broken. A cache was. Bitcoin has had the same class of inflation bug without confidential transactions (CVE-2018-17144). -
Adam Back reposted
Bitcoin Magazine
@BitcoinMagazine
JUST IN: ๐ซ๐ท French company Capital B announces a purchase of 376 BTC for โฌ25.3 million! ๐
-
Adam Back
@adam3us
Bienvenue dans lโรฉquipe Capital B !
Nicolas Chรฉron
@NCheron_bourse
Je suis devenu actionnaire de Capital B.
Ceux qui me suivent savent que je mโintรฉresse au Bitcoin depuis des annรฉes, mais รฉgalement aux diffรฉrentes maniรจres de sโy exposer.
Capital B a fait un choix assez radical : lever des capitaux pour accumuler du Bitcoin et construire progressivement une rรฉserve stratรฉgique en BTC.
La sociรฉtรฉ cherche ร utiliser les marchรฉs de capitaux pour augmenter progressivement son exposition au Bitcoin et, si la stratรฉgie fonctionne, crรฉer davantage de valeur pour ses actionnaires que la simple dรฉtention de BTC.
Autre point, le lancement du digital crรฉdit a dรฉjร รฉtรฉ largement รฉvoquรฉ par Alexandre Laizet @AlexandreLaizet directeur gรฉnรฉral dรฉlรฉguรฉ de Capital B. C'est un information publique, et que Capital B ait la volontรฉ de sโy lancer est un point d attraction majeur pour les investisseurs dont je fais partie.
Jโapprรฉcie รฉgalement le fait de retrouver autour du projet des acteurs reconnus de lโรฉcosystรจme, notamment Adam Back @adam3usย , figure historique de Bitcoin, ainsi que Yves Choueifaty prรฉsident et fondateur de TOBAM, sociรฉtรฉ de gestion prรฉsente depuis longtemps dans lโunivers des actifs numรฉriques.
รvidemment, ce modรจle ajoute aussi des risques : risque de marchรฉ, dilution lors des levรฉes de capitaux, volatilitรฉ de lโaction, valorisation parfois dรฉcorrรฉlรฉe de celle des bitcoins dรฉtenusโฆ Capital B nโest pas du Bitcoin et acheter lโaction nโรฉquivaut pas ร acheter directement du BTC.
Cet investissement fait partie de ma poche crypto long terme, aux cรดtรฉs d'une participation dans le mรฉdia crypto de rรฉfรฉrence @TheBigWhale_ย
Ci-dessous le graphique mensuel de l'action, -90% post bear market, dont on ne sait pas s'il est terminรฉ d'ailleurs.
Second graphique, en journalier, une sorte de dรฉbut de rounding bottom est possiblement en train de se former, d'oรน mon entrรฉe rรฉcente (qui se fera en plusieurs fois dans les mois ร venir).ย
โก๏ธ Cette publication n'est pas un conseil en investissement.
โก๏ธ Investir comporte des risques, ne pas investir assure de perdre face ร l'inflation. -
Adam Back reposted
TheRustyTwit
@rusty_twit
Annoyed that the CLN message "when the upgrade drops as scheduled, upgrade or --offline" got mangled into "SHUT DOWN YOUR NODE NOW".
People don't read anymore. -
Adam Back reposted
Blockstream Jade
@BlockstreamJade
You can now pick up a Jade at a UPS Access Point in the US and Canada instead of having it shipped to your house.
At checkout, choose pickup and select a nearby UPS Store, CVS, or similar.
store.blockstream.com -
Adam Back reposted
Blockstream
@Blockstream
We have been testing Blockstream Swaps. It is going well, and a lot of you asked to get in.
Request beta access:
blockstream.com/swaps/ -
Adam Back reposted
Freddie New
@freddienew
Many of us in the UK Bitcoin industry have been fighting for this for years, and it FINALLY looks as though we may get it over the line.
Until now, if you lend your Bitcoin, the tax authorities have treated that as a disposal and tried to charge you capital gains tax (even when you haven't sold the Bitcoin). For years, many of us have been flagging the unfairness and inequity of this treatment; and the new draft legislation (published this summer) seems to suggest that this will at last be corrected.
Campaigning to change unjust laws is never easy, but it absolutely can be done. It's just hard to remember that when you're only half way to your goal.
Key wording below and a good explainer from @BitcoinTaxUK ๐
Freddie New
@freddienew
Why can't you easily lend your Bitcoin in the UK without incurring a tax charge?
Largely because the current tax treatment of lending Bitcoin sees the transfer as a taxable event.
By contrast with stocks, shares and other securities, Bitcoin falls outside the scope of repurchase or โrepoโ legislation that enables the lending of securities to be tax neutral. This has to change.
There's a huge economic opportunity here, and the UKโs financial services sector needs to seize it; to capitalise on this ยฃ1 trillion-plus market, particularly by providing collateralised loans and other financial services that facilitate asset management.
Yesterday, @bitcoinpolicyuk were proud to collaborate in drafting and adding our name to a letter sent to @RachelReevesMP , @EmmaforWycombe and @jamesmurray_ldn , urging them to prioritise legislation to treat the lending of Bitcoin as a "no gain, no loss" transaction. This change would simply reflect economic reality and ensure that Bitcoin is treated in just the same way as securities currently are.
We're pleased to sign this letter alongside @coinbase , @GreengageCo , @krakenfx , @recap_io , @TheSecretAcct and @CryptoUKAssoc , among many others.
We keep hearing that 'growth' is a priority for this Government. Let's now see those words turned into actions. -
Adam Back reposted
Bitcoin Archive
@BitcoinArchive
BREAKING: 2M clients of U.K. platform Hargreaves Lansdown will finally get access to Bitcoin ETFs.
The firm previously dismissed BTC as an asset class.
The capitulation continues. ๐ -
Adam Back reposted
BTC Times
@BTCTimescom
๐ฌ๐ง @bitcoinhodlco bought 1 #bitcoin for ยฃ57,680, bringing holdings to 167.487 BTC after raising ยฃ48,275 through its second ATM offering, with support from @adam3us.
btctimes.com/b-hodl-purchases-one-bitcoin-after-raising-4โฆ -
Adam Back reposted
Scott Ellam
@btconlyscott
Every business will be better with Bitcoin.
$XCE | AQSE: XCE | OTCQB: XCELFThis media couldn't be displayed. See it on the original post. -
Adam Back reposted
B HODL โก
@bitcoinhodlco
B HODL is pleased to announce we've added more Bitcoin to the balance sheet, funded by our completed second ATM and our Capital Deployment Programme
โ 1 BTC bought
โ ยฃ48.3K raised via ATM 2
โ New ATM approved
AQSE: HODL | OTCQB: HODLF | FRA: F5S
#bitcoin #bhodl -
Adam Back reposted
CoinMarketCap
@CoinMarketCap
LATEST: โก Bitfinex Securities has listed five tokenized notes tracking Strategy, Strategy's STRC, Metaplanet, H100 Group and Capital B shares, tradable against USD, USDT and Bitcoin for eligible non-US investors.
-
Adam Back reposted
Scott Ellam
@btconlyscott
I joined @proactive_x investors today to discuss our recent 10BTC addition, the proposed recruitment company acquistion for @XCEofficial group and the 20%+ increase in revenues, along with four new hires for our current flagship business Spencer Riley.
This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Dan Held
@danheld
One of the best Bitcoin memes of all time.
-
Adam Back reposted
Alexandre Laizet โก๏ธ
@AlexandreLaizet
More Bitcoin for $ALCPBโก๏ธ
Bitcoin Treasuries
@BTCtreasuries
JUST IN: French public company Capital B $ALCPB is raising $8.8 million through a private placement with strategic investor Adam Back to buy more #bitcoin.
This raise, along with ongoing operations, could fund the purchase of 376 additional BTC and make it the 25th-largest BTC treasury company. ๐๐ฅThis media couldn't be displayed. See it on the original post. -
Adam Back reposted
Bitcoin Treasuries
@BTCtreasuries
JUST IN: French public company Capital B $ALCPB is raising $8.8 million through a private placement with strategic investor Adam Back to buy more #bitcoin.
This raise, along with ongoing operations, could fund the purchase of 376 additional BTC and make it the 25th-largest BTC treasury company. ๐๐ฅThis media couldn't be displayed. See it on the original post. -
Adam Back reposted
XCE - Connecting Excellence Group
@XCEofficial
Three announcements. One day. The XCE strategy moving into execution.
Yesterday, XCE:
Signed binding Heads of Terms for its first proposed acquisition: two specialist recruitment businesses under one brand, generating ยฃ1.79m revenue and ยฃ431k EBITDA, with an expected 8.216 BTC joining the XCE treasury on completion.
Reported growth from Spencer Riley: ยฃ2.16m revenue, ยฃ1.25m gross profit and a 58% gross margin, alongside four new fee earners and the launch of our Private Equity & Leadership division.
Secured a further 10 BTC investment from @adam3us, taking one of Bitcoinโs best-known pioneers to a 29% stake in XCE.
CEO @btconlyscott sat down with @stephengunnion at @proactive_x to explain what it all means, and what comes next.
More acquisitions. More hires. A medium-term ambition of ยฃ10m revenue and 100+ BTC.
$XCE | AQSE: XCE | OTCQB: XCELFThis media couldn't be displayed. See it on the original post. -
Adam Back reposted
Daniela Fonseca Viteri
@dannyfonse
Letโs gooo โก๏ธโก๏ธ
Alexandre Laizet โก๏ธ
@AlexandreLaizet
๐ Capital B $ALCPB raises โฌ7.6 million with strategic investor Adam Back @adam3us, which along with ongoing operations, could enable the total acquisition of 376 additional BTC, bringing the Companyโs potential total holdings to 3,521 BTC โก๏ธwith potential additional capital raising instruments now totaling โฌ320 million at higher pricing levelsโก๏ธ
$ALCPB ๐ซ๐ท $CPTLF ๐บ๐ธ Europe's First Bitcoin Treasury Company โก๏ธ
Capital B
@_ALCPB
๐ Capital B announces a โฌ7.6 million capital raise with strategic investor Adam Back to accelerate its Bitcoin Treasury Company strategyโก๏ธ
Full Press Release (EN): cptlb.com/wp-content/uploads/2026/09/Dw3S0KbrTg/20260902-โฆ
Full Press Release (FR): cptlb.com/wp-content/uploads/2026/09/sGf1r8F2UT/20260902-โฆ
BTC Strategy (EN): -
Adam Back reposted
STOKR
@stokr_io
Extending our integration with @BFXSecurities ES.
Five digital securities tracking listed Bitcoin-treasury companies are now admitted to trading - for eligible non-US professional investors only.
Listing details: capital.bitfinex.com
Not an offer or financial advice. -
Adam Back reposted
The Franck
@FEVRIERFranck
โก๏ธโก๏ธโก๏ธ
Alexandre Laizet โก๏ธ
@AlexandreLaizet
Bitcoin Capital Markets built on Bitcoin @Liquid_BTCโก๏ธ Outstanding work by @stokr_io @Arnab_Naskarr and team with Bitcoin Treasury Companies now accessible on @bitfinexโก๏ธCapital B with ticker $CALCPBโก๏ธ
Bitcoin Treasuries
@BTCtreasuries
JUST IN: Five #bitcoin treasury company equities $MSTR, $STRC, $MPJPY, $H100, and $ALCPB have just been listed on OG crypto exchange Bitfinex for tokenized securities trading.
1.6 million users just got access to trade amplified Bitcoin and digital credit 24/7/365. ๐ฅ -
Adam Back reposted
Bitcoin Treasuries
@BTCtreasuries
JUST IN: Five #bitcoin treasury company equities $MSTR, $STRC, $MPJPY, $H100, and $ALCPB have just been listed on OG crypto exchange Bitfinex for tokenized securities trading.
1.6 million users just got access to trade amplified Bitcoin and digital credit 24/7/365. ๐ฅ -
Adam Back reposted
Alexandre Laizet โก๏ธ
@AlexandreLaizet
Bitcoin Capital Markets built on Bitcoin @Liquid_BTCโก๏ธ Outstanding work by @stokr_io @Arnab_Naskarr and team with Bitcoin Treasury Companies now accessible on @bitfinexโก๏ธCapital B with ticker $CALCPBโก๏ธ
Bitcoin Treasuries
@BTCtreasuries
JUST IN: Five #bitcoin treasury company equities $MSTR, $STRC, $MPJPY, $H100, and $ALCPB have just been listed on OG crypto exchange Bitfinex for tokenized securities trading.
1.6 million users just got access to trade amplified Bitcoin and digital credit 24/7/365. ๐ฅ -
Adam Back reposted
โฟthemoon | โ vs 21m | Capital โฟear Stackers member
@Bthemoon2030
Incredible work from the team, their raising money like it's free on the streets!
Capital B raise nr. 3 in 5 weeks ๐คฏ. This this a โฌ7.6M private placement solo from Adam Back WITH the exact same ABSA terms as the 28-08 raise (โฌ0.58/ABSA, 15.4% premium to yesterday's close). For another potential 49,4 million euro's
โก๏ธ There is now โฌ320M cash in the pipline to buy future bitcoin if the full cascade fires. โก๏ธ
Adam Back's stake (basic shares):
โข July 2026: 12.15%
โข post 28-08 ABSA: 14.82%
โข today: 17.77%
โข if his new warrants get exercised: 27.80%
So when some are selling the insinders are doubling down. Funny how that works !
CB warrant arsenal post-raise:
W01: 27.4M @ โฌ1.01
W02: 10.0M @ โฌ0.84
W03: 46.1M @ โฌ0.86
W04: 23.0M @ โฌ1.12
W05: 23.0M @ โฌ1.46
W06: 98.8M @ โฌ0.75
W07: 49.4M @ โฌ0.98
W08: 49.4M @ โฌ1.27
Total: 327M shares / โฌ320M potential cash!
Every tranche carries the 130%-VWAP trigger (20 days above 130% ร strike โ 20-day use-it-or-lose-it exercise window).
Flywheel: price โ โ tranche called โ cash โ BTC โ price โ โ next tranche called. Rinse and repeat
Calculate the outcome: bthemoon2030.github.io/capital-b/
Capital B
@_ALCPB
๐ Capital B announces a โฌ7.6 million capital raise with strategic investor Adam Back to accelerate its Bitcoin Treasury Company strategyโก๏ธ
Full Press Release (EN): cptlb.com/wp-content/uploads/2026/09/Dw3S0KbrTg/20260902-โฆ
Full Press Release (FR): cptlb.com/wp-content/uploads/2026/09/sGf1r8F2UT/20260902-โฆ
BTC Strategy (EN): -
Adam Back reposted
Coinjoined Chris โก
@coinjoined
When I hear "bitcoin self-custody is dead after the coldcard incident"
-
Adam Back reposted
The Block
@TheBlockCo
THE BLOCK: Bitfinex Securities has listed five tokenized products offering exposure to bitcoin treasury companies, including Strategy $MSTR, Metaplanet, H100, and Capital B.
The equity-backed notes are issued via a Luxembourg securitization fund and trade against USD, USDT, and bitcoin bitcoin:native. -
Adam Back reposted
Valentin Kosanovic
@Kosanovic_V
More liquidity and global accessibility for $ALCPB, Europeโs First Bitcoin Treasury Company โ๏ธ๐ง
Alexandre Laizet โก๏ธ
@AlexandreLaizet
๐ $ALCPB is now listed on @bitfinex in BTC, USDt, and USD, under ticker $CALCPBโก๏ธ
Bitfinex Securities
@BFXSecurities
Five bitcoin treasury company products have been newly listed on Bitfinex Securities.
Tokenised securities of the worldโs leading bitcoin treasury companies, and issued on @Liquid_BTC.
Find out more: www.bitfinex.com/securities/post/?id=1196 -
Adam Back reposted
โฟthemoon | โ vs 21m | Capital โฟear Stackers member
@Bthemoon2030
Imagine selling Capital B shares when @adam3us is doubling down on his stack. Will find out who has the smart side of this trade. My money is on Adam (and myself)
Adam Back
@adam3us
Bought over 25m $ALCPB:EPA shares between this week and last week. Let's go๐
-
Adam Back reposted
Valentin Kosanovic
@Kosanovic_V
Capital B @_ALCPB announces a โฌ7.6 million capital raise through a private placement of shares with four share subscription warrants attached to each share (ABSA), at โฌ0.58 per ABSA, subscribed by strategic investor Adam Back @adam3us, at the same conditions as the โฌ21.0 million ABSA operation announced on August 28, 2026.
Each ABSA entitles the holder to 2 Warrants 2026-06 with an exercise price of โฌ0.75, 1 Warrant 2026-07 at โฌ0.98, and 1 Warrant 2026-08 at โฌ1.27, each warrant entitling the holder to one share of the Company.
The Company has the possibility to trigger an accelerated warrant exercise period provided that the VWAP of Capital Bโs shares over the previous 20 consecutive trading days exceeds 130% of the exercise price of the relevant warrant tranche.
In the event that all warrants issued in connection with this new transaction were to be exercised, this could generate up to an additional โฌ49.4 million in proceeds.
All outstanding warrants combined, after closing of this operation, could enable to generate โฌ320.4 million of proceeds for more Bitcoin and more digital credit potential capacity.ย
The proceeds from the issuance of the ABSA, along with ongoing operations, could enable the acquisition of 376 additional BTC, bringing the Companyโs potential total holdings to 3,521 BTC.
Job is not done. Focused on maximizing BTC Accumulation and BTC Yield for our shareholders over time. Relentlessly. ๐ง
Capital B $ALCPB, Europeโs First Bitcoin Treasury Company
Capital B
@_ALCPB
๐ Capital B announces a โฌ7.6 million capital raise with strategic investor Adam Back to accelerate its Bitcoin Treasury Company strategyโก๏ธ
Full Press Release (EN): cptlb.com/wp-content/uploads/2026/09/Dw3S0KbrTg/20260902-โฆ
Full Press Release (FR): cptlb.com/wp-content/uploads/2026/09/sGf1r8F2UT/20260902-โฆ
BTC Strategy (EN): -
Adam Back reposted
Capital B
@_ALCPB
๐ Capital B announces a โฌ7.6 million capital raise with strategic investor Adam Back to accelerate its Bitcoin Treasury Company strategyโก๏ธ
Full Press Release (EN): cptlb.com/wp-content/uploads/2026/09/Dw3S0KbrTg/20260902-โฆ
Full Press Release (FR): cptlb.com/wp-content/uploads/2026/09/sGf1r8F2UT/20260902-โฆ
BTC Strategy (EN): -
Adam Back reposted
Mr.Andersen
@Sanderandersenn
Bitfinex listed @H100Group, three other Bitcoin treasury companies, and a digital credit instrument yesterday, in tokenized form, directly on Bitcoin layer two Liquid.
This could be the beginning of Bitcoin capital markets.
Liquid works by locking BTC on Bitcoin's own chain and mirroring it 1:1 on the sidechain, secured by a federation of exchanges and financial institutions instead of miners. That gives one-minute blocks and two-block finality, so these assets settle in about two minutes with confidential amounts, all anchored to Bitcoin's own security.
For access, it means anyone anywhere can now hold exposure to five Bitcoin treasury instruments through one venue, no local exchange, no separate custody chain in between.
A capital market built on top of one of the most liquid assets in the world, with an already developed derivatives market, is the way to go. I believe this could get people to open their eyes to how big Bitcoin could be.
Great work by @stokr_io and @BFXSecurities!
Bitfinex Securities
@BFXSecurities
Five bitcoin treasury company products have been newly listed on Bitfinex Securities.
Tokenised securities of the worldโs leading bitcoin treasury companies, and issued on @Liquid_BTC.
Find out more: www.bitfinex.com/securities/post/?id=1196 -
Alexandre Laizet โก๏ธ
@AlexandreLaizet
๐ Capital B $ALCPB raises โฌ7.6 million with strategic investor Adam Back @adam3us, which along with ongoing operations, could enable the total acquisition of 376 additional BTC, bringing the Companyโs potential total holdings to 3,521 BTC โก๏ธwith potential additional capital raising instruments now totaling โฌ320 million at higher pricing levelsโก๏ธ
$ALCPB ๐ซ๐ท $CPTLF ๐บ๐ธ Europe's First Bitcoin Treasury Company โก๏ธ
Capital B
@_ALCPB
๐ Capital B announces a โฌ7.6 million capital raise with strategic investor Adam Back to accelerate its Bitcoin Treasury Company strategyโก๏ธ
Full Press Release (EN): cptlb.com/wp-content/uploads/2026/09/Dw3S0KbrTg/20260902-โฆ
Full Press Release (FR): cptlb.com/wp-content/uploads/2026/09/sGf1r8F2UT/20260902-โฆ
BTC Strategy (EN):
Adam Back
@adam3us
Bought over 25m $ALCPB:EPA shares between this week and last week. Let's go๐
-
Adam Back reposted
Alexandre Laizet โก๏ธ
@AlexandreLaizet
๐ Capital B $ALCPB raises โฌ7.6 million with strategic investor Adam Back @adam3us, which along with ongoing operations, could enable the total acquisition of 376 additional BTC, bringing the Companyโs potential total holdings to 3,521 BTC โก๏ธwith potential additional capital raising instruments now totaling โฌ320 million at higher pricing levelsโก๏ธ
$ALCPB ๐ซ๐ท $CPTLF ๐บ๐ธ Europe's First Bitcoin Treasury Company โก๏ธ
Capital B
@_ALCPB
๐ Capital B announces a โฌ7.6 million capital raise with strategic investor Adam Back to accelerate its Bitcoin Treasury Company strategyโก๏ธ
Full Press Release (EN): cptlb.com/wp-content/uploads/2026/09/Dw3S0KbrTg/20260902-โฆ
Full Press Release (FR): cptlb.com/wp-content/uploads/2026/09/sGf1r8F2UT/20260902-โฆ
BTC Strategy (EN): -
Adam Back
@adam3us
Live by the fork, die by the fork.
-
Adam Back reposted
Richard Byworth โ/21M
@RichardByworth
Absolute beast mode from @btconlyscott and team
Was impressed with Scott from the day I met him: hustle and drive. Achieving this during the height of the bear market was truly impressive to watch unfold.
Congratulations Scott! ๐ฅ
Scott Ellam
@btconlyscott
Three announcements from @xceofficial - the only listed international executive recruitment group combined with a Bitcoin treasury (stacking since 2021) - this morning:
โ 10 BTC added now holding 72.941 BTC - equity raised at a 3.4% premium to market - added by @adam3us
โ Heads of Terms signed for a proposed recruitment acquisition โ theyโve been stacking too
โ Spencer Riley revenue up 20.6% - the team power ahead and welcome 4 more
Each bit of news deserves its own post so do like, subscribe and follow.
$XCE | AQSE: XCE | OTCQB: XCELF -
Adam Back reposted
Scott Ellam
@btconlyscott
Three announcements from @xceofficial - the only listed international executive recruitment group combined with a Bitcoin treasury (stacking since 2021) - this morning:
โ 10 BTC added now holding 72.941 BTC - equity raised at a 3.4% premium to market - added by @adam3us
โ Heads of Terms signed for a proposed recruitment acquisition โ theyโve been stacking too
โ Spencer Riley revenue up 20.6% - the team power ahead and welcome 4 more
Each bit of news deserves its own post so do like, subscribe and follow.
$XCE | AQSE: XCE | OTCQB: XCELF -
Adam Back reposted
Mr.Andersen
@Sanderandersenn
You can now trade tokenized @H100Group on @BFXSecurities, side by side with @Strategy , @Metaplanet and @_ALCPB
Big step in the right direction for Bitcoin capital markets. Five Bitcoin treasury companies on one regulated venue could be the trigger for a global capital market built on top of Bitcoin.
Great work by the @stokr_io and Bitfinex Securities teams.
STOKR
@stokr_io
Extending our integration with @BFXSecurities ES.
Five digital securities tracking listed Bitcoin-treasury companies are now admitted to trading - for eligible non-US professional investors only.
Listing details: capital.bitfinex.com
Not an offer or financial advice. -
Adam Back reposted
Bitfinex Securities
@BFXSecurities
Five bitcoin treasury company products have been newly listed on Bitfinex Securities.
Tokenised securities of the worldโs leading bitcoin treasury companies, and issued on @Liquid_BTC.
Find out more: www.bitfinex.com/securities/post/?id=1196 -
Adam Back reposted
Alexandre Laizet โก๏ธ
@AlexandreLaizet
๐ $ALCPB is now listed on @bitfinex in BTC, USDt, and USD, under ticker $CALCPBโก๏ธ
Bitfinex Securities
@BFXSecurities
Five bitcoin treasury company products have been newly listed on Bitfinex Securities.
Tokenised securities of the worldโs leading bitcoin treasury companies, and issued on @Liquid_BTC.
Find out more: www.bitfinex.com/securities/post/?id=1196 -
Adam Back reposted
XCE - Connecting Excellence Group
@XCEofficial
We said acquisitions would be a key part of XCE's growth. The first one is now underway.
This morning XCE announced signed Heads of Terms for its first proposed acquisition since IPO: a specialist construction and engineering recruitment business, established for 20 years and operating across the UK and U.S.
The numbers for the target acquisition, for the twelve months to 30 June 2026:
โ ยฃ1.79m revenue, up 21.5% year on year
โ ยฃ1.27m gross profit at a 70.9% margin
โ ยฃ431k EBITDA
โ 8.216 Bitcoin on its balance sheet, which XCE would acquire at market value
โ Net cash outflow on completion of approximately ยฃ150k
โ Remaining consideration structured as an earn-out paid only on delivered EBITDA
This is what we see in recruitment: a fragmented market full of strong, owner-managed businesses that can benefit from being part of something bigger, without losing what made them successful. Too small for private equity. Few trade buyers. Value tied to the people who built them.
Our model is simple. Businesses in the group operate under a decentralised model, keeping their brand, their management and their autonomy - while XCE provides access to more capital, talent and opportunity for them to scale. We build a bigger group around them, and the value of all of them compounds in one listed vehicle.
Subject to due diligence and completion, this business will join XCE alongside Spencer Riley.
First deal underway. More in the pipeline.
Read the full announcement: www.londonstockexchange.com/news-article/market-news/firsโฆ
@btconlyscott @RichardByworth @vijayselvamxo @adam3us
$XCE | AQSE: XCE | OTCQB: XCELF -
Adam Back reposted
Blockstream Jade
@BlockstreamJade
Our CPO Jeff Boortz joined @JD_Durkin on @FINTECHTVglobal to talk through last month's hardware wallet incident.
If a Coldcard created your seed, assume you are at risk. Move to a fresh phrase on hardware you trust. Do not restore the old one.
Jade was not affected. There is no silent RNG fallback. Every recovery phrase is mixed from multiple independent entropy sources.This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Mr.Andersen
@Sanderandersenn
When a bitcoin company trades below 1.0x mNAV, the job is still to raise bitcoin per share.
Three ways to do that:
1. M&A. Structure the deal so sats per fully diluted share go up.
2. Build or buy a company on top that makes cash, and put the profit into bitcoin.
3. Digital credit. Issue a liability against the bitcoin, buy more coins, pay the interest.
Issuing new shares to buy bitcoin in the market only works above 1.0x. Trading below 1.0x does not mean you cannot increase bitcoin per share. -
Adam Back reposted
Scott Ellam
@btconlyscott
10 BTC added to the balance sheet this morning -strengthening the treasury that helps drive revenue per share:
โ ยฃ655,999 investment, completed
โ Includes 10 BTC subscribed by strategic investor @adam3us at ยฃ57,799.90 per BTC
โ Shares issued at 1.5p - a 3.4% premium to Friday's close
โ Treasury: 72.941 BTC, up 15.9%
โ Bitcoin per share: +5.02% (issued) / +6.34% (fully diluted)
โ BTC Yield since IPO end of 2025: 544.2%
The @xceofficial recruitment business is built to attract revenue generating recruiters and more cash-generative recruitment acquisitions. The more BTC we hold, and the more BTC per share we add โ the more attractive we become to the next hire and the next acquire.
$XCE | AQSE: XCE | OTCQB: XCELF -
Adam Back reposted
Scott Ellam
@btconlyscott
The first proposed recruitment company acquisition for @xceofficial in full:
โ Specialist construction & engineering recruitment - 20 years established, UK & U.S.
โ Revenue: ยฃ1.79m, up 21.5% year on year
โ EBITDA: ยฃ431k ยท Gross margin: 70.9%
โ Holds 8.216 BTC - acquired at market value on completion
โ Net cash outflow on completion: c.ยฃ150k
โ Remaining consideration: a small deferred payment, plus an earn-out paid only on delivered EBITDA
A very impressive business with a solid team. They keep their brand, their team and their autonomy inside the group. The only thing we consolidate is the value.
There are thousands of privately owned recruitment firms - profitable, high-performing - with no way to build long-term value into the business. @XCEofficial is a decentralised acquisition platform designed to solve that: join a listed group, keep your independence, aggregate the value.
Subject to due diligence and completion. First one underway. More in the pipeline.
If you've built one of these firms and want the same path - my DMs are open.
$XCE | AQSE: XCE | OTCQB: XCELF -
Adam Back reposted
Daniel ษrrr
@csuwildcat
I think it's really gross to use Hal this way, given it's effectively implying a dead man who can't speak for himself would support an altcoin fork of the thing he worked on. Co-opting the memory of people who died tragically and can't speak for themselves is a really nasty form of affinity scam.
-
Adam Back reposted
Blockstream Jade
@BlockstreamJade
Youโre right that we didnโt label a single โcriticalโ CVE in the post. Thatโs on purpose.
1.0.41 is defense-in-depth: stack protection, memory scrubbing, runtime/dependency updates, extra per-device entropy at RNG init, and anti-downgrade. We do not think an emergency โupgrade immediately on every channelโ notice is warranted, but you should still update promptly.
No need to move funds or regenerate a seed because of this release. -
Adam Back reposted
Blockstream
@Blockstream
Finding the right post-quantum signature for SHRINCS meant testing 25,935 parameter sets.
@blksresearch built an open-source explorer where wallet developers, protocol researchers, and anyone else set the weights that match their case.
Full post: blog.blockstream.com/searching-for-shrincs-parameters/ -
Adam Back reposted
The Bitcoin Historian
@pete_rizzo_
JUST IN: THE FAILED BIP 110 FORK HAS OFFICIALLY RELAUNCHED AND REMOVED #bitcoin'S PROOF OF WORK ALGORITHM
IT IS NOW ITS OWN INCOMPATIBLE BLOCKCHAIN WITH ITS OWN CRYPTOCURRENCY ๐คก -
Adam Back reposted
nifty, ideas guy
@niftynei
this would be wild if true (paper proposes that physical limitations may prevent construction of a quantum computer that can crack ECDSA sigs)
Robin Linus โ
@robin_linus
Quantum doomerism might be doomed in less than 5 years!! ๐คฏ
arxiv.org/abs/2510.02877 -
Adam Back reposted
Blockstream Jade
@BlockstreamJade
Jade firmware 1.0.41 is out. It contains security updates and every user should upgrade as soon as they safely can.
Jade is not affected by the Coldcard random number vulnerability. The reasoning, and everything we changed, is in the post.
blog.blockstream.com/reflections-on-the-coldcard-fallout/ -
Adam Back reposted
Coinjoined Chris โก
@coinjoined
-
Adam Back reposted
Blockstream Research
@blksresearch
Full aggregation for BIP340 signatures, now as a draft BIP.
It specifies DahLIAS, an aggregate signature scheme and can serve as a basis for future cross-input signature aggregation (CISA) proposals.
Thanks to @fjahr for the spec work.
More background on DahLIAS ๐
light ๐
@lightcoin
BIP draft: Full-Aggregation of BIP 340 Signatures
by @fjahr ๐
groups.google.com/g/bitcoindev/c/TF5mPfy58RQ -
Adam Back reposted
Samson Mow
@Excellion
Remember FTX and all their splashy big money sponsorships? ๐ค
This media couldn't be displayed. See it on the original post. -
Adam Back reposted
OCEAN
@ocean_mining
OCEAN and Luke Dashjr announce today that, by mutual agreement, Luke Dashjr has separated from OCEAN, resigning as Chairman, Chief Technology Officer, and director.
Link to the joint statement press release here: www.prnewswire.com/news-releases/joint-statement-of-oceanโฆ -
Adam Back reposted
Christian Decker
@Snyke
I can confirm that B731 AAC5 21B0 1385 9313 F674 A26D 6D9F E088 ED58 is my GPG fingerprint, and the release has my signature attached to prove my endorsement of the reproducible build
-
Adam Back reposted
Jardani Marquis
@jardanimarquis
randomness. good seeing you @r0ckstardev
-
Adam Back reposted
BTC Times
@BTCTimescom
ICYMI: ๐ @Blockstream App 3.5.0 adds air-gapped QR signing for @BlockstreamJade hardware wallets, plus beta Lightning payments and other updates.
btctimes.com/blockstream-adds-air-gapped-jade-signing-to-โฆ -
Adam Back reposted
Core Lightning โก๏ธ
@Core_LN
-
Adam Back reposted
Samson Mow
@Excellion
Blockstream and @Core_LN have just released v26.06.7 which addresses a number of vulnerabilities. Tell everyone you know who is running a CLN node to update ASAP.
Only binaries are being released now, with the source code coming in 2 weeks. This is to mitigate the possibility of anyone using the fixes to attack the network - however it is also possible LLMs can reverse engineer the fixes from the binaries too.
So the best course of action is to either update from the binaries, or if you want to wait for source code, run your node in --offline mode (not to be confused with shutting down your node, which you should not do).
There's no need to panic. There's no evidence that any vulnerabilities have been exploited. However, everyone should either upgrade now, or run in --offline mode if waiting for source. โก๏ธ
Core Lightning โก๏ธ
@Core_LN
Core Lightning 26.06.7 is out and recommended for every node runner.
It fixes vulnerabilities reported over the past three weeks, during a sharp rise in AI-generated reports across open source Bitcoin. Details stay under embargo for two weeks, then all published. -
Adam Back reposted
Core Lightning โก๏ธ
@Core_LN
Core Lightning 26.06.7 is out and recommended for every node runner.
It fixes vulnerabilities reported over the past three weeks, during a sharp rise in AI-generated reports across open source Bitcoin. Details stay under embargo for two weeks, then all published. -
Adam Back reposted
-
Adam Back reposted
Mikhail Kudinov
@kudinov_mikhail
Take a look at our proposal for a PQ signature for Bitcoin. We would be happy to receive as much feedback as possible. There is still a lot of work ahead. Let's make Bitcoin post-quantum ready.
P.S. Look at this cute logo ๐
Jonas Nick
@n1ckler
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/bitcoindev/c/HbVboXIFiG8
Draft BIP:
github.com/SHRINCS/shrincs-bip/blob/main/SHRINCS.md -
Adam Back reposted
Mike Schmidt
@bitschmidty
I want Bitcoin to achieve it's maximum potential as cash on the internet. I will work with anyone who seeks the same. Even if they said mean things about me at one point or another. I have a thick skin and total determination for this mission. Let's go together.
-
Adam Back reposted
Jonas Nick
@n1ckler
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/bitcoindev/c/HbVboXIFiG8
Draft BIP:
github.com/SHRINCS/shrincs-bip/blob/main/SHRINCS.md -
Adam Back reposted
Mike Schmidt
@bitschmidty
Draft BIP for SHRINCS post-quantum signatures
Jonas Nick
@n1ckler
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/bitcoindev/c/HbVboXIFiG8
Draft BIP:
github.com/SHRINCS/shrincs-bip/blob/main/SHRINCS.md -
Adam Back reposted
Blockstream
@Blockstream
If Bitcoin had to choose a lattice signature today, it would be Falcon-1024.
@blksresearch has published a full report on Dilithium, Falcon and Hawk: what each costs on-chain, how hard each is to implement safely, and which assumptions you are trusting.
blog.blockstream.com/lattice-signatures-for-bitcoin/ -
Adam Back reposted
Christian Decker
@Snyke
This gives users 14 days to upgrade after which they'll be able to verify the binaries thanks to our reprobuilds. If you chose to wait for the source release, only then do we suggest restarting with `--offline`. This keeps CLN enforcing on-chain rules, while shutting out attckrs
-
Adam Back reposted
Mill3sim3 Permissionless โก๏ธ
@Mill3sim3
GM @adam3us , do you remember ?
Mill3sim3 Permissionless โก๏ธ
@Mill3sim3
GM my Bitcoiners !!!
Privacy is not a crime
RSA perl. Since 1995
Merci @adam3us @MarsuTwitt @satochip -
Adam Back
@adam3us
"afroman atrocity"
-
Adam Back reposted
Jim Dennis
@answrguy
The controversy was manufactured โฆ
โฆ with malice afore thought! -
Adam Back reposted
Michael Saylor
@saylor
Strategy increased USD Reserve to $5.10B, established additional USD Cash of $1.59B, and repurchased $136M of $STRC. As of 8/23/26: Strategy holds ~4% of Total BTC Supply and has ~0% Net Leverage. $MSTR www.strategy.com/press/strategy-increases-usd-reserve-to-โฆ
-
Parker Lewis
@parkeralewis
"Bitcoin maximalism is dead"
Adam Back
@adam3us
bitcoin maximalists are 50 for 50 hit rate at this point. nocoiners, fork coiners, alt coiners in disbelief...
-
Adam Back reposted
JKL
@Finiteenergy21
Arigatล Nakamoto
This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Maximus Maximalistus
@maximalistus
Blockstream Jade gives you a QR workflow you can actually build your self-custody around.
With a camera-equipped Jade, QR codes can be used for:
โ Device Unlock โ perform PIN Unlock using QR codes and a companion app
โ PSBTs โ import transactions, verify them on Jade, sign, and return the signed transaction as QR codes
โ Bitcoin addresses โ verify receive addresses generated by your companion app
โ SeedQR โ quickly load or switch wallets during an active session
โ Multisig configurations โ register a multisig wallet so Jade can verify receive and change addresses
โ OTP โ register One-Time Password records and use Jade as a 2FA authentication device
โ Message signing โ sign messages with supported companion apps
blog.blockstream.com/blockstream-jade-qr-scan/
help.blockstream.com/blockstream-jade/use-jade-air-gappedโฆ
There are still QR capabilities that could be added:
โ Firmware upgrades via QR
โ Anti-Exfil via QR
These aren't currently part of Jade's QR functionality.
And this is where users can have an impact.
Features get built when there is demand for them. Supporting the project by buying an official Jade is one way to support the developers working on Jade, while also showing that people value continued development and more advanced functionality.
An official Jade gives you the finished product, straightforward firmware upgrades, and Genuine Check support on current Jade Core and Jade Plus hardware.
Jade Plus already supports air-gapped firmware upgrades through JadeLink, USB storage or compatible SD-card readers. What isn't implemented is transferring the firmware itself through QR.
help.blockstream.com/blockstream-jade/use-jade-air-gappedโฆ
But another thing I like about Jade is that buying the official hardware isn't the only way to use the software.
Jade is open source.
You can inspect the firmware, audit it, build it yourself and run Jade on supported inexpensive ESP32 hardware.
Blockstream even provides a browser-based Jade DIY flasher.
github.com/Blockstream/Jade/
github.com/Blockstream/jadediyflasher/
For developers and tinkerers, Jade DIY is an excellent playground.
But I think Jade DIY has another very useful role for the average self-custodian:
A cheap training device for your real OPSEC.
Replicate the same setup you use for your long-term savings:
Mnemonic.
Mnemonic + passphrase.
Bring Your Own Entropy.
Singlesig.
Multisig.
Whatever your actual setup is.
Then practice it using testnet, regtest or a small amount of mainnet bitcoin.
Practice recovery.
Practice signing.
Practice replacing a device.
Practice moving the funds.
Practice verifying your backup.
Practice recovering your wallet from scratch.
Do it until the procedure is something you understand rather than something you hope you'll remember when something goes wrong.
Hardware can fail.
Devices can be lost.
Wallet implementations can have bugs.
The recent Coldcard Mk3 entropy vulnerability was another reminder that knowing how to recover and move your funds is part of self-custody.
Your hardware wallet shouldn't be the first place you practice your recovery procedure when you actually need it.
Official Jade for your real custody.
Jade DIY as an inexpensive environment where you can repeatedly practice the same OPSEC.
Self-custody is useless if you can't access your funds.
Don't trust. Verify.
Then practice the verification.
Affiliate link bellow ๐
rewards.blockstream.com/maximus
And the code JADEPLUSEXPRESS gets anyone free expedited shipping on a Jade Plus. -
Adam Back reposted
Parker Lewis
@parkeralewis
"Bitcoin maximalism is dead"
-
Adam Back reposted
Coinjoined Chris โก
@coinjoined
This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Tufty
@tuftythecat
It is a target rich environment but the ones that are easier to take out (some of which I have identified here) may not be those that are the biggest threats. It would be interesting work to do though if someone thinks itโs worth it.
-
Adam Back reposted
Dom Bei
@Beiwatch
Epic but missing a few right? No DiCaprio?
-
Adam Back reposted
FractalEncrypt โ/21M
@FractalEncrypt
codex32 does really feel like magic. And you don't need my fancy analog computers to to the codex32 computations. You can print and cut for free from the official github (and they have a website too at secretcodex32 dot com where you can print the entire book for free.
-
Adam Back reposted
ะฮKฮDฮI๐๐ฆ
@nakadai_mon
Built by bitcoiners for bitcoiners.
10% OFF with code NAKADAI when ordering a @blockstream
Jade or Jade Plus.
store.blockstream.com?code=NAKADAIThis media couldn't be displayed. See it on the original post. -
Adam Back reposted
Tufty
@tuftythecat
Is anyone still bothered about what nChain is doing in the patenting world? Should I stop wasting my time?
Tufty
@tuftythecat
It's time for another update on what nChain's patenting activity in Europe is like. The headline figure is that they have now reached a total of 700 applications on the EP register. This includes pending PCT applications, European applications resulting from these, and EP divisionals. Of these, 209 have been granted and are in force (211 if you include two that were revoked but are currently under appeal). A total of 300 applications are currently still pending at the EPO.
-
Adam Back reposted
Mr.Hodl
@MrHodl
You're friends with someone trying to scare people away from running version 30 with the law.
Think this one through -
Adam Back reposted
James Van Straten
@btcjvs
It took the Bitfinex whale three months after the FTX collapse to first distribute its holdings to recognise the bull market began.
Holdings are still flat, despite bitcoin being up 35% from the July lows. -
Adam Back reposted
ะฮKฮDฮI๐๐ฆ
@nakadai_mon
Big Bitcoin is in control.
-
Adam Back reposted
Cรธbra
@CobraBitcoin
Youโre not so different from Kurt. Both of you write propaganda about Bitcoin being compromised and your alternative forked chain being a โpurerโ version.
You think you are treading new ground but youโre just doing what big blockers were doing nearly 10 years ago. -
Adam Back reposted
Nicholas Gregory
@gregory_nico
Just a reminder, when bitcoin pumps. This is the best meme / song ever created...
-
Adam Back reposted
MARS SPITS BARS ๐ฅ
@marsspitsbarz
roughnecks is taking credit for the pump
-
Adam Back reposted
Blockstream
@Blockstream
The Simplicity community is live. A dedicated space for in-depth technical discussion with the team building high-assurance Bitcoin contracts. Ask your questions, see what others are shipping, and post the actual code.
community.simplicity-lang.org -
Adam Back reposted
Nunya Bizniz
@Pladizow
Bitcoin reminding people who's the King of the Jungle:
-
Adam Back reposted
Blockstream Jade
@BlockstreamJade
Also, wanted to add, you can self-host the oracle (Umbrel / Start9 / own infrastructure) so Blockstream isnโt in the unlock path
help.blockstream.com/blockstream-jade/add-more-security-fโฆ -
Adam Back reposted
Blockstream Jade
@BlockstreamJade
We had to ask.
@blksresearch put post-quantum signatures on Jade Plus and three other wallets. All four signed.
H/t @olkurbatov and Dmytrii Kurbatov for leading the work. Reviewed by @n1ckler.
Blockstream
@Blockstream
A popular concern says post-quantum signatures cannot run on the hardware wallets people already own.
@blksresearch implemented hash-based schemes on four popular devices. All four signed. SLH-DSA, the NIST standard, in about two minutes at worst.
blog.blockstream.com/hardware-wallets-post-quantum-signatโฆ -
Adam Back reposted
Blockstream Jade
@BlockstreamJade
Also reviewed by Mike Kudinov, Viktor Mashtaliar and Yaroslava Chopa.
Thanks also to @Trezor, @Ledger and @BitBoxSwiss, who helped the team get this running on their hardware.
blog.blockstream.com/hardware-wallets-post-quantum-signatโฆ -
Adam Back reposted
BitcoinVN Shop
@BitcoinVNShop
More variety in the dedicated hardware signing devices for users based in ๐ป๐ณ
Blockstream Jade Core now ashore! -
Adam Back reposted
JokHodl
@JokHodl
Jade Plus offer๐๐ป
Take control of your Bitcoin with Jade Plus.
10% OFF with code JOKHODLโจ
๐ FREE Express Shipping with code JADEPLUSEXPRESS
๐ Order nowโจstore.blockstream.com/discount/JOKHODL?redirect=/productsโฆ
Your keys
Your Bitcoin
Your freedom๐ฝ๐งก
#bitcoin #jadeplus #blockstream #selfcustody #hardwarewallet #notyourkeysnotyourcoins
@Blockstream
@BlockstreamJade -
Adam Back reposted
Blockstream Japan
@BlockstreamJP
1/7Stephan Livera PodcastใซใฆBlockstreamใฎJadeๆ ๅฝRichใใใผใใฆใงใขใฆใฉใฌใใใJadeใใฎ่จญ่จๆๆณใ็ฌ่ชใปใญใฅใชใใฃใขใใซใใใใฆใปใซใใซในใใใฃใฎๆๆฐ่ซ็นใซใคใใฆ่ชใใพใใ @stephanlivera
ไปฅไธใซๅ ๅฎนใใพใจใใพใ๐งต๐
www.youtube.com/watch?v=wAGAGG5xz_4 -
Adam Back
@adam3us
miners are service providers. non-economic nodes are sybils. economic nodes transmit the markets view. the market prevails. we knew this in 2017. we told 110 promoters, they insisted to FOFO. so they did. we tried to persuade those being misled, and i hope they stayed or come back.
Adam Back
@adam3us
the market prevails. how else could, or should it be, with bearer free market money.
Adam Back
@adam3us
how the market prevailed in 2017:
many were uncertain, but the market doesn't hear fence sitters, it's activist investors who form the price: those who didn't like forks, REALLY didn't like them, shorted them with everything๐
Adam Back
@adam3us
"When the two armies meet in the field of battle, the pragmatists are always going to flee from an adversary with conviction" -@real_vijay (in 2017 about forks)
Vijay Boyapati
@real_vijay
When the two armies meet in the field of battle, the pragmatists are always going to flee from an adversary with conviction. /end #no2x
Adam Back
@adam3us
but 110 proponents had NO conviction. it was so weak that defeating it simply meant doing nothing. that's why there were no long bids and a wall of short interest. why there was no fork future exchange listing (no volume to be worth it), no wallet (people surmised it will fail).
-
Adam Back
@adam3us
"When the two armies meet in the field of battle, the pragmatists are always going to flee from an adversary with conviction" -@real_vijay (in 2017 about forks)
Vijay Boyapati
@real_vijay
When the two armies meet in the field of battle, the pragmatists are always going to flee from an adversary with conviction. /end #no2x
-
Adam Back reposted
Alex ๐ฝ
@AlexesNakamoto
Average Bitcoin hodler morning routine.๐
This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Blockstream
@Blockstream
A popular concern says post-quantum signatures cannot run on the hardware wallets people already own.
@blksresearch implemented hash-based schemes on four popular devices. All four signed. SLH-DSA, the NIST standard, in about two minutes at worst.
blog.blockstream.com/hardware-wallets-post-quantum-signatโฆ -
Adam Back reposted
calle
@callebtc
people who think that core is some sort of intransparent institution operating in the shadows are either too lazy or too dumb to go have a look for themselves. literally everything they do is public, anyone can chime in, and the result of their work is pure open source code.
just because core people do free and open source work doesnโt mean they have to listen to you. if you think thatโs arrogant, think about the number of karens with strong opinions in the world. nobody needs this shit. either you do the work and contribute constructively, or you gtfo. the fact that you might be angry doesnโt matter to anyone here. nobody cares.
this is the internet. bitcoin is not a democracy. core devs are not your politicians.
nobody owes you anything. not even an explanation.
then there are those who are just pure sociopaths. when someone they hallucinate to represent โcoreโ โ which in their mind are the โcool kidsโ โ doesnโt agree with them, they crash out publicly. itโs the grown-up version of โthey donโt want to play with meโ. they paint themselves as lone rangers when in reality they simply canโt find anyone who would work with them voluntarily.
many such cases in this space too. -
Adam Back reposted
Jonas Nick
@n1ckler
Hash-based signatures on hardware wallets are feasible:
@blksresearch benchmarks show that SHRINCS & SLH-DSA take less than 2 minutes. Future wallets could be optimized & faster.
Code is open-source.
Thanks to @BlockstreamJade @Ledger @satoshilabs @BitBoxSwiss for the help!
Blockstream
@Blockstream
A popular concern says post-quantum signatures cannot run on the hardware wallets people already own.
@blksresearch implemented hash-based schemes on four popular devices. All four signed. SLH-DSA, the NIST standard, in about two minutes at worst.
blog.blockstream.com/hardware-wallets-post-quantum-signatโฆ -
Adam Back reposted
Blockstream Jade
@BlockstreamJade
Yes - SeedQR + Temporary Signer loads the seed for that session and does not keep a PIN-encrypted wallet on the device.
Once you power the device off, seed is wiped.
help.blockstream.com/blockstream-jade/use-jade-air-gappedโฆ
help.blockstream.com/blockstream-jade/add-more-security-fโฆ -
Adam Back reposted
Nordic
@NordicMiner
Full unboxing, air-gapped setup + thoughts on the @BlockstreamJade Plus
This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Bitcoin Archive
@BitcoinArchive
Satoshi emailed Adam Back to say Hashcash was getting cited in the whitepaper โ 18 years ago today.
-
Adam Back reposted
sapiens-engineering
@sapiens_eng
Fully agreed! And even if you have all of the things you mentioned, things can go wrong. I mean the people behind GG20, CGGMP etc family of protocols are definitely smarter than me, but despite security reviews, later analyses found security issues in basically all impls.
-
Adam Back reposted
Samson Mow
@Excellion
Bitcoin is the new wonder of the world, more work & human ingenuity than went into the Great Pyramids of Egypt. The biggest computation ever done, a digital monument, a verifiable artifact of digital gold โ the foundation of a new digital age.
- @adam3usThis media couldn't be displayed. See it on the original post. -
Adam Back reposted
Blockstream
@Blockstream
Sync an entire Bitcoin wallet in seconds.
QuickSync is a new open-source wallet scanning protocol by Blockstream that turns hundreds of address lookups into one descriptor request, dramatically cutting sync time when using the Blockstream Explorer API.
Get an API key today: -
Adam Back
@adam3us
may i suggested BIM for the BIP 110 hard forked air drop coin. they seem to like "bitcoin is money" for their reddit. if they don't chose a ticker, exchanges will do it for them, and on past experience they may not even all chose the same ticker for the same airdrop/fork future!
Adam Back
@adam3us
more irony ๐ฟ bip 110 reddit mods claim "spam", froze thread. they don't want to talk about ticker (or don't want me to pot period in their space). irony given their noise they made about brigading developer github. www.reddit.com/r/bitcoinismoney/comments/1vrkant/proposedโฆ
-
Adam Back reposted
Dylan LeClair
@DylanLeClair
โBitcoin has a security budget problem, fees arenโt sufficient, it need tail emissionsโ
โBitcoin has a throughput problem, fees are too high, it needs bigger blocksโ
Your inherent desire for human intervention at every turn is exactly what bitcoin solved, please just shut up. -
Adam Back
@adam3us
bitcoin-only hww, custody: complexity is the enemy of security. many alts don't have multisig or schnorr, one sizel lowest-common-denominator resulted in questionable custody architecture choices. bitcoin has cleanest architected, no alt marketing bullshit, hardcore security tech
-
Adam Back reposted
Joe007
@J0E007
Bottom is where Bitfinex whales start buying at volume. If you want to succeed in crypto markets, you'll do well to remember that.
-
Adam Back reposted
Liquid Network ๐
@Liquid_BTC
DAMP proposes managing regulated Liquid assets with no offchain cosigner. The holder signs the spend and supplies a policy proof, enforced by a Simplicity covenant in the same transaction.
Issuer offline? Holders with the latest snapshot keep transacting. PoC to come.
Artem Chystiakov
@Arvolear
Introducing DAMP -- a decentralized asset management protocol for stablecoins and RWA on Liquid. Fully onchain and self-custodial. No cosigner service is needed, powered by Simplicity. Link to the full paper is below. Stay tuned for a PoC.
-
Adam Back reposted
-
Adam Back reposted
Coinjoined Chris โก
@coinjoined
grubles ใฐใฉใใซใบ
@notgrubles
Shockingly low amount of people suggesting Core on old laptop running Linux.
-
Adam Back reposted
Artem Chystiakov
@Arvolear
Simplicity things we've done over the last 6 months:
- Shipped Simplex development framework
- Wrote three ELIPs for dapp <> wallet communication
- Wrote an ELIP for Simplicity clear signing
- Added jet extensions support to Simplicity
- Added Bitcoin jets to Simplicity
- Refactored parser in SimplicityHL compiler
- Implemented enums in SimplicityHL
- Implemented modules and libs in SimplicityHL
- Shipped SimplicityHL-std alpha
- Developed Humid browser extension wallet
- Developed p2p lending PoC (twice)
- Developed Simplicity Unchained service
- Developed p2p options PoC
- Developed Simplicity CMR metadata service
- Developed SimplicityHL formatter
- Improved Simplicity website and documentation
- Researched Simplicity-native multisig
- Researched DAMP
- Researched Simplicity-powered price oracle
- Researched Simplicity-powered bridge
- Fixed many UX issues and bugs across all products
The next 6 months will be huge. -
Adam Back reposted
Maximus Maximalistus
@maximalistus
Blockstream Bitcoin Hardware Wallets have Anti-Exfil.
Anti-Exfil adds another layer of security by forcing the device to include random data in signatures, preventing attackers from slowly guessing your private keys.
With ECDSA (the digital signature algorithm used in Bitcoin), a random private key is combined with a nonce, which is a one-time value intended to add randomness to the signature to ultimately produce a transaction signature that can be validated by other usersโ Bitcoin full nodes. Anyone can guess your private key based on your signatures without this random nonce, which is as bad as it sounds!
Compromised hardware wallets could create a nonce that appears random but is not. The nonces could be known to an attacker ahead of time. Even worse, the hardware wallet could leak parts of the userโs master private key into individual nonces, which would allow the attacker to guess every private key given a sufficient number of signatures.
Anti-Exfil uses โsign-to-contractโ to ask Jade to use its signature nonce while cryptographically committing to some random data proposed by the (assumed uncompromised) host computer. The random dataโs hash is then combined with the signature nonce to produce the signature.
By use of this protocol, the nonce is re-randomized, thus preventing the attack.
More info:
blog.blockstream.com/anti-exfil-stopping-key-exfiltration/
help.blockstream.com/hc/en-us/articles/9641573399961-Whatโฆ
x.com/BlockstreamJade/status/1820630240227729749
x.com/utxoclub/status/1820520960476561825
darkskippy.com
10% off on Blockstream store products with coupon "maximus".
rewards.blockstream.com/maximus
And the code JADEPLUSEXPRESS gets anyone free expedited shipping on a Jade Plus
UTXOCLUB
@utxoclub
Today we disclose Dark Skippy - a powerful new method for a malicious signing device to leak secret keys.
With a modified signing function, a device can efficiently and covertly exfiltrate a master secret seed by embedding it within transaction signatures.This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Mike Schmidt
@bitschmidty
When you download Bitcoin Core today, the binary doesn't contain everything your node runs. It still loads the C library (glibc and friends) from your operating system which means there are version requirements, behavior that can vary from machine to machine, and code that your node executes that isnโt covered by reproducible builds.
New static test builds pack it all into one deterministic Bitcoin Core binary.
@fanquake is asking node runners to test out these new static binaries and report results. -
Adam Back reposted
Samson Mow
@Excellion
We are very grateful to have your support for @Liquid_BTC for so long! โค๏ธ
-
Adam Back reposted
Tatum Turn Up
@tatumturnup
This guy made multiple thousand dollar bets that he was so sure he was going to win and accepted that only @coinjoined would likely pay him.
Now that he lost the bet, he is no where to be found.
Hardfork Felipe
@felipondus
I only have faith @coinjoined will pay up if I win. Everyone else will ghost or block me.
-
Adam Back reposted
FRANCIS โ๏ธ BULLBITCOIN.COM
@francispouliot_
BULL is challenging in court the EU's dangerous mass surveillance program for crypto users, DAC8.
I cannot stand by and do nothing while faceless globalist bureaucrats put the security and privacy of millions of Europeans at risk.
We will get DAC8 repealed.This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Artem Chystiakov
@Arvolear
Published on the Simplicity forum. Should you have any comments or improvement ideas, let's discuss them here:
community.simplicity-lang.org/t/damp-decentralized-asset-โฆ
Artem Chystiakov
@Arvolear
Introducing DAMP -- a decentralized asset management protocol for stablecoins and RWA on Liquid. Fully onchain and self-custodial. No cosigner service is needed, powered by Simplicity. Link to the full paper is below. Stay tuned for a PoC.
-
Adam Back reposted
BITCOIN - Decentralized & P2P
@Cipherhoodlum
Looks like this is already supported in Jade firmware 1.0.40+. They added BIP85/BIP39 QR codes, so you should be able to generate a child seed and just scan it into another Jade.
Would be even better if you could skip all the word confirmations and just go straight to the QR. -
Adam Back reposted
ะฮKฮDฮI๐๐ฆ
@nakadai_mon
Hmm... @Blockstream is this possible or on the roadmap?
May 26 update features an update BIP85 QR support support , but not sure that's the same as being able to generate child seedQRs on the fly simply in the menu. -
Adam Back reposted
d7r
@noD7R
legit good. asked @BlockstreamJade and @adam3us guys to allow the BIP85 be exported via QR so child seed can be loaded on extra Jades dunno if they made those update to firmware.
current implementation still lacking a bit since only force write down the word and double confirm which is annoying since these are always recoverable no need to triple check or at least should allow to skip that and give options to export. -
Adam Back reposted
Core Lightning โก๏ธ
@Core_LN
Like many open source Bitcoin projects, CLN has received a number of AI-generated CVE reports from multiple sources over the past 10 days. Our small team, together with several invaluable open source contributors, has been working intensively to validate and triage these reports and develop fixes where needed.
Weโre now working through a broader remediation strategy. The first step is a point release containing many of these fixes, and we will strongly recommend upgrading. Weโre aiming to have an initial version of the point release available within the next few days. -
Adam Back reposted
Maximus Maximalistus
@maximalistus
Don't trust. Verify.
Prove you can recover it.
Maximus Maximalistus
@maximalistus
One of my favorite features of @BlockstreamJade is something that deserves more attention: fast BIP39 WordList entry for passphrases.
A BIP39 passphrase can add another layer to a Bitcoin wallet, but there is a practical problem with strong passphrases:
Entering a long, high-entropy string on a hardware wallet can be painful.
Jade has a clever solution.
Instead of manually entering a long sequence of letters, numbers and symbols, Jade has a WordList method designed for passphrases composed of words from the 2,048-word BIP39 English word list.
Start typing a word and Jade recommends matching BIP39 words. Select it, move to the next one, and repeat.
This makes entering a long passphrase surprisingly fast.
help.blockstream.com/blockstream-jade/add-more-security-fโฆ
Important: this is NOT a BIP39 mnemonic/recovery phrase.
The BIP39 word list is simply being used as the alphabet from which the passphrase is constructed.
And the critical word here is RANDOM.
Do not turn this into a sentence, quote, song lyric or a collection of words you personally like.
The passphrase needs high entropy.
Since the BIP39 English list contains 2,048 words, every independently and uniformly selected word represents 11 bits of entropy.
For example:
11 independently random BIP39 words = 121 bits of entropy.
A physical entropy source such as dice can therefore be used with an unbiased mapping procedure to randomly select words from the complete BIP39 list and build an extremely strong passphrase.
Then Jade's WordList interface makes actually entering that long passphrase much more practical.
But there is another part of self-custody that I think is equally important:
PRACTICE.
Before trusting a wallet configuration with a meaningful amount of Bitcoin, test the complete recovery procedure.
Can you recreate the wallet?
Can you enter the passphrase correctly?
Do you know what happens if you make a typo?
Can you identify the correct wallet?
Can you receive, sign and move funds without having to relearn the procedure during an emergency?
A backup that has never been tested is still an assumption.
And this is where another great property of Jade becomes useful: Jade is open source and Blockstream publishes DIY builds for commodity hardware.
github.com/Blockstream/Jade/tree/master/diy
A DIY Jade should not be confused with an official retail Jade. Blockstream specifically notes that DIY hardware should not be expected to pass its Genuine Check. You also aren't getting the purpose-built retail hardware, manufacturing, enclosure and polished product experience that comes with buying an official device.
And buying the retail product is one of the straightforward ways to support the people building and maintaining an open-source project like Jade.
But DIY Jade has another excellent role:
A training device.
Build a completely separate TEST version of your long-term storage setup using throwaway keys and test funds.
If your real setup is singlesig + a high-entropy BIP39 passphrase, reproduce the procedure with a test seed and test passphrase.
If your long-term setup is a multisig using hardware wallets from different vendors, build a separate training multisig that follows the same procedure and quorum without ever loading your real keys into the training devices.
Practice recovery.
Practice signing.
Practice replacing a device.
Practice moving the funds.
Practice until the procedure is something you understand rather than something you hope you remember.
Jade even supports Bitcoin testnet and regtest, so none of this requires risking your real wallet.
Never put the real recovery phrase or real passphrase from your cold-storage wallet into a device being used as a training environment.
Self-custody isn't just owning the keys.
It's knowing how to use, recover and move them safely when the day comes.
Don't trust. Verify.
Then practice the verification.
Affiliate link bellow ๐
rewards.blockstream.com/maximus
And the code JADEPLUSEXPRESS gets anyone free expedited shipping on a Jade Plus. -
Adam Back reposted
Blockstream
@Blockstream
New research from Kyrylo Riabov and @Arvolear.
This Blockstream paper explores enforcing asset rules onchain with a Simplicity covenant on @Liquid_BTC. Ordinary transfers need no issuer signature, and the holder keeps their own keys.
Artem Chystiakov
@Arvolear
Introducing DAMP -- a decentralized asset management protocol for stablecoins and RWA on Liquid. Fully onchain and self-custodial. No cosigner service is needed, powered by Simplicity. Link to the full paper is below. Stay tuned for a PoC.
-
Adam Back reposted
James O'Beirne
@jamesob
Attackers are working through the honeypots on cktripwire.com
Our theft frontier is at 11 bits of added entropy on top of the weak mk3 seeds.
All of @ColeTU's external honeypots have been swept. We just lost our first one-word passphrase UTXO. -
Adam Back reposted
Steve Barbour
@SGBarbour
BIP110 believers effectively just created a new Bitcoin religious fork s (because it is technically unsound) embodied as an Altcoin. Literally a religious split off the bitcoin economy that offers no incremental network utility.
-
Adam Back reposted
Jonas Nick
@n1ckler
LLMs are used very successfully to find vulnerabilities in Bitcoin software.
Can they also help prove the security of a modern cryptographic library for Bitcoin?
To explore this question, @remix7531 and I are publishing libshrincs.
delvingbitcoin.org/t/libshrincs-a-c-implementation-with-aโฆ
libshrincs is a handwritten C library implementing WOTS+C, the one-time signature used by SHRINCS.
It is a proof of concept and should not be used in production.
Its machine-checked proofs connect the C implementation to an unforgeability theorem.
The current theorem does not yet give a full post-quantum security bound.
The post and review tutorial describe its current limits.
Code and proofs:
github.com/remix7531/libshrincs
Review tutorial for the security proof (no Rocq or SSProve background required):
github.com/remix7531/libshrincs/blob/tutorial/docs/SSPROVโฆ
@remix7531 has written three excellent posts on the library and verification work:
Towards libshrincs
remix7531.com/post/towards-libshrincs/
The grind was the only detector
remix7531.com/post/the_grind_was_the_only_detector/
Choosing a verification toolchain
remix7531.com/post/choosing_a_verification_toolchain/ -
Adam Back reposted
Blockstream Jade
@BlockstreamJade
2/ Your recovery phrase sits encrypted on the device. Unlocking it needs the PIN you type on Jade and a key share from a blind oracle. Neither is enough by itself.
The oracle never sees the real PIN or any wallet data. It only gets a scrambled version that includes a secret unique to that particular Jade. -
Adam Back reposted
Blockstream Jade
@BlockstreamJade
1/ Jade doesnโt use a physical secure element.
We just published a full post on how the Virtual Secure Element works:
blog.blockstream.com/jade-virtual-secure-element/ -
Adam Back reposted
Coinjoined Chris โก
@coinjoined
Imagine betting your one and only bitcoin on BIP110's success ๐ซฃ
zender โ๏ธ
@zndtoshi
Made a Bip110 bet with @dathon_ohm for 1 btc each.
The winner is decided by which chain a Core v29 node follows 24h after forced activation at block 965664.
We created a multisig wallet with @jimmysong and he will be the oracle for it.
Hats off to Dathon for his conviction. We need more bitcoiners like this. -
Adam Back reposted
wiz
@wiz
We successfully submitted the ICANN .bitcoin TLD application for Community Priority Evaluation with over 50+ letters of endorsement from within the community, together with several high-level letters of recognition. ICANN will reveal our full application sometime in November 2026
-
Adam Back reposted
Daniel 21e15
@Daniel21e15
-
Adam Back reposted
Cรธbra
@CobraBcash
Keep lighting your money on fire; you're doing great!
-
Adam Back reposted
0x6a.app | OP_RETURN
@0x6aApp
-
Adam Back reposted
Remu โก๏ธ
@btcbenchmark
But core devs did not push consensus changes this whole time not once
So why frame it: โif core devs can just pish changes with minersโ
Because they have not done it? -
Adam Back reposted
Remu โก๏ธ
@btcbenchmark
Clearly they donโt do any of those things ENOUGH. It was a rounding error disasteriously inflated by fugazi twitter engagement and straight up fraud data from network. Maximum of 6% of node count, which is not event mesurement in the consensus process.
Additionally, they DONT need to be consulted AT ALL in client software upgrades
And even if they dont have to be consulted at all, they still were consulted and debated ad nauseum
They were plainly wrong, thats it. Itโs a matter of life and death the decisions are not being made by democratic process vulnerable to populism and social attacks IMO
Bitcoin, and core, both are way better now because they survived this attack. Anti-fragility, gaining from chaos.
I hope nothing changes -
Adam Back reposted
midnight
@midmagic
For those people who have some significant value in Bitcoin โ consider how regressive they'd have to be to be so completely oblivious to the development of the system their money is in, that they support single-dev segfaulting node software and want to "fire" everyone else.
-
Adam Back reposted
Yan at Swan
@skwp
There are not โtwo sidesโ in bitcoin. Itโs not core vs knots. Itโs not devs vs users. Itโs *way* more interesting than that.
The only thing you can control in Bitcoin is what software *you* run. Literally. That is all. All of the emergent governance properties stem from that. From the inability to coerce others.
Donโt like core? Cool. Code your own implementation! Donโt like it? Thereโs a bunch of really smart people doing that kind of thing, so run one of theirs. Put it through an AI and analyze it. Learn something.
But donโt expect other people to do what you want. Itโs just not possible.
Bitcoin is anti-collectivist by its very design, but humans have collectivism hard wired into their brains. Even the most hardcore libertarians canโt erase millions of years of evolution. They want to form tribes. They want to convince their fellow man to act for the good of the tribe.
But the bitcoin protocol is brutal. It suffers no democracy, no tribes, no voting systems. It boggles the mind. It confounds us. It doesnโt act like any governance system we have ever seen, and itโs deeply non human in its nature.
It makes us go insane: Why arenโt the other people seeing what Iโm seeing? Are they evil? Stupid? Are they all conspiring? Did the deep state pay everyone to embed jpgs into the blockchain?
All of these questions are our inability to face a governance system that is antithetical to human existence. It is the reason for Bitcoin derangement syndrome. It is the reason so many people have rage quit through the years and started their own coins, with a nice side benefit of self interested dreams of riches and cult leadership, of course.
You only get to decide what software *you* run. That is all. Embrace it, and you discover an ability to predict game theoretic outcomes for Bitcoin movements. Reject this, and face Bitcoin derangement syndrome and myriad altcoins. -
Adam Back reposted
BookLab by Bjorn ๐
@poorbjorn
The bull market memes are going to be ๐ฅ. One of the best ai videos Iโve seen. Maybe not the kindest. Hehe. Letโs be more humble
-
Adam Back reposted
Kilian Rausch
@kilrau
Thanks, Adam ๐
-
Adam Back reposted
Blockstream Jade
@BlockstreamJade
A passphrase adds an advanced layer of protection to the Bitcoin self-custody setup you already have, with nothing to buy.
Your existing funds don't move on their own. Back up the passphrase as carefully as your recovery phrase, then send them across. -
Adam Back reposted
-
Adam Back reposted
Blockstream
@Blockstream
Bitcoin's long-term security is work we've done for years, and quantum is the @BTCconsortium's first focus.
@adam3us on Blockstream's post-quantum research. -
Adam Back reposted
Zaid ๐ง
@zaidlikesmstr
No fucking way Saylor reposted this lmao ๐
-
Adam Back reposted
Alekos Filini
@afilini
You guys built what I think is the most useful bitcoin product of the past 2/3 years. Congrats on your achievements and good luck on your next endeavors!
-
Adam Back reposted
Yan at Swan
@skwp
Mechanic blocked me despite me never having had interacted with him, or acted poorly toward him in public in any way. I'll post his message here because it contains a very interesting statement worth unpacking
"Pools have said 'our blocks are valid, even if they violate the rules we were told to respect'"
Let's unpack that.
1. Pools haven't said anything
2. Pools / miners have produced bitcoin blocks, which other bitcoin software accept as valid.
3. The only thing that can "tell you what to respect" in Bitcoin is the Bitcoin consensus protocol enforced by each individual node following Nakamoto consensus (i.e. heaviest proof of work chain following the same consensus rules).
4. The "community" of a few hundred people posting about "mandatory" actions cannot "tell you" to respect rules of their choosing. They must enforce that with their nodes. They did that, but nobody wanted to play along. That happens.
5. If miners produced blocks and those blocks were accepted by other nodes following Nakamoto consensus, then the blocks are valid by definition. This is a tautology. They didn't violate any rules except those invented by a small faction of people. Those are not the consensus rules, by definition.
I can see a lot of people got emotional about something that is not an emotional topic. It's just software. You can't just wave a magic wand and "tell" people how to run their business/life and thus their Bitcoin node. That's just how Bitcoin works. -
Adam Back reposted
Coinjoined Chris โก
@coinjoined
Suitcoiners 1:0 Shitcoiners
This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Murch
@murchandamus
Alright, yโall got this here. See you later.
-
Adam Back reposted
Farside Insights
@FarsideInsights
> This entire mess could have been avoided if you had just left OP_RETURN alone for a year or two until things cooled off.... BIP-110 supporters were largely not technical. They were ordinary people, artists, podcasters, musicians, your average Bitcoiner, and they perceived a threat to Bitcoin, which is to say a threat to their money. You don't need a deep understanding of human psychology to grok why that was going to cause an uproar. You may be a great coder, but you have no self-awareness and no EQ.
Do you not see why it might be a good idea to have a Bitcoin node implementation based more on technical merit, rather than one that also tries to politically manange the emotions of artist and musician Bitcoiners?
That said, education and trying manage coalitions of disperate people and to keep them somewhat together, may be important. However, it is probably a good idea to somewhat decouple that from the important areas of code of at least one popular node implementation. Some people have a lot of value at stake and would therefore value a node that has more focus on technical merit. I hope you can see why that is a reasonable position. -
Adam Back reposted
Michael Saylor
@saylor
There are 110 names for those who think they know better than the free market. Central planner is one.
-
Adam Back reposted
Bugle.News ๐ฏ
@bitcoin_bugle
BREAKING: @LukeDashjr selects 'Yasmarang' as PoW algorithm to replace SHA-256 in upcoming Bitcoin hard fork.
-
Adam Back reposted
semi-normal | french ctv
@crypto_0ptimist
What level of delusion is this?
-
Adam Back reposted
midnight
@midmagic
There is no authority there โ core is reacting to miners. People continue to ask miners to stop mining NFT/inscriptions/etc; I doubt they will be making quadratic DoS type inscriptions or runes any time soon, because that harms block convergence.
-
Adam Back
@adam3us
the market prevails. how else could, or should it be, with bearer free market money.
-
Adam Back reposted
Mr.Hodl
@MrHodl
Lolol
Bugle.News ๐ฏ
@bitcoin_bugle
BREAKING: @LukeDashjr selects 'Yasmarang' as PoW algorithm to replace SHA-256 in upcoming Bitcoin hard fork.
-
Adam Back reposted
vryfokkenou
@vryfokkenou
> the rejection of BIP110 by the Bitcoin industry despite broad support among the community.
What "broad support"...?
You just keep repeating the same inaccurate claims over and over.
Even if it split the Bitcoin space 50/50, which it didn't, that's STILL not broad support.
At the very best, it was a contentious proposal with some support, but that support was not broad in sense of the word. -
Adam Back reposted
zender โ๏ธ
@zndtoshi
Invalidating most proof of work (be it by UASF or URSF) assumes you live in a different paradigm than Bitcoin.
Miners can never have monopoly.
You can always bring more hashrate to overpower any monopoly. -
Adam Back reposted
Alex Thorn
@intangiblecoins
youโre truly delusional
-
Adam Back reposted
Farside Insights
@FarsideInsights
> despite broad support among the community
BIP-110 never had any material support from traders and investors.
If BIP-110 coin did have majority investor support, exchanges would have listenened to their clients and listed BIP-110 coin when the fork happened. Then as the split occurred, the price of Bitcoin would crash and BIP-110 would trade at a premium to Bitcoin. Then miners would have followed the money and mined BIP-110 coin. -
Adam Back reposted
Gareth Jenkinson
@gazza_jenks
Let's be categorically clear and pragmatic here, if BIP-110 had "broad support from the community", it would not have stalled like it did.
Whether any of us like it or not, Bitcoin is the sum of its constituents (nodes, miners etc).
You have far more knowledge of the protocol than I, but its disingenuous to say that "the industry rejected what the community wanted".
You guys are going to hard fork yourselves to be the next Bitcoin Cash and that is just sad.
Core can do a lot better, I will never not agree with that, but this is just hard to grasp. -
Adam Back reposted
_Checkmate ๐ ๐โกโข๏ธ๐ข๏ธ
@_Checkmatey_
Your proposed fork didn't achieve rough consensus.
Instead of reflecting on why your proposal failed, you blame the referee, and the rules of the game, claiming a shady cabal has designed them to work against you.
You wanted to play chess by reverting the two pawn moves forward rule. The majority signalled that they did not want to play with those rules. The obvious result is nobody outside your little clique sat down to play your version.
The problem isn't with the existing rules of chess, nor those who currently enjoy playing by them.
The problem is that your proposal for changed rules was unappealing, and the attempt to force feed it to us didn't land...at all.
The new plan seems to be forking into some mutant form of checkers. Best of luck with that. -
Adam Back reposted
Grams
@jmgramke
Ocean updated their TOS to enable them to legally screw over customers, hijack their hashing power & economic energy to signal for Bip110.
Lawsuit & Discovery may prove to be very interesting on this one. -
Adam Back reposted
Jim Dennis
@answrguy
Because there's nothing the negotiate.
Any sufficient expressive programming system can be used to encode arbitrary data (some of which will be "spam" according to mercurial vagaries).
Think of it as a corollary to Gลdel's Incompleteness Theorem, and have ELI5 it. -
Adam Back reposted
Dr -ck
@ckpooldev
New post format "I was wrong, here's why that proves I was right" keeps dropping lately. ๐ค
-
Adam Back reposted
Coinjoined Chris โก
@coinjoined
After Luke did the old proof-of-work switcheroo, he was shocked to find there wasn't an army of Blake 2b miners standing by to mine his shitcoin:
This media couldn't be displayed. See it on the original post. -
Adam Back reposted
PakoVM
@PakoVM
I'm willing to exchange all of my Bitcoin-Blake2b coins (Knots/110) for BTC (Core) 1:1
If you think this new coin/chain will be more valuable than BTC just hit me up, my DMs are open. I will most likely take multiple offers because I just don't want to doxx my whole stack. -
Adam Back
@adam3us
"bitcoin is", and that's enough.
-
Adam Back reposted
Mike Schmidt
@bitschmidty
Bitcoin Core v32.0 is targeted for release in October:
- Up to 3x faster initial sync. Block validation now fetches transaction inputs from disk in parallel instead of one at a time
- The libevent external dependency is fully removed, continuing Core's push to cut third-party dependencies
- Max peer connections raised from 125 to 200 to have more open slots for new nodes to sync from, faster block propagation, and a harder network to eclipse or partition
- Mempool-based fee estimation to cut fee overestimation (in progress)
- Transaction relay rate limiting is now global instead of per-peer, keeping a node's CPU and memory usage steady when transaction volume spikes
- Ships with features from libsecp256k1 0.8.0 with verification up to 11% faster, plus the new Silent Payments module (BIP 352)
- PSBTv2 (BIP 370) support, now the default for PSBT-creating RPCs for better coordination of unsigned transactions for multisig and hardware wallet setups
- New exportwatchonlywallet command to export a wallet as a watch-only file, no private keys, and restore it on your online node
- Core now enables Tor's proof-of-work DDoS defense on the onion service it creates for your node, where the Tor daemon supports it
Additional tests, bugfixes, and features included as well.
Feature freeze is ~August 20, rc1 ~September 10, final release targeted for ~October 10. (Test the release candidates when they ship!) -
Adam Back reposted
JAN3
@JAN3com
Samson Mow was right!
As the mandatory signaling window opened at block 961,632, BIP-110 played out exactly as @Excellion predicted on @simplybitcoin. With virtually zero support from miners, exchanges, or wallets, the breakaway attempt stalled after just two blocks.This media couldn't be displayed. See it on the original post. -
Adam Back reposted
DarkClownSuitCoinicarus
@Coinicarus
-
Adam Back reposted
Samson Mow
@Excellion
Many things in this post are incorrect, and it matters that we correct them, because this version of the history is exactly what convinced people the last few months were a good idea.
โBIP-148 is celebrated as Bitcoin Independence Day, because it proved that ordinary users, running nodes in their homes, could force the most powerful mining cartels and corporations in the industry to back down. The users had no hashrate, no exchanges, no lobbyists. They had conviction and they had nodes, and that was enough.โ
First, the framing. August 1st is what's celebrated as Bitcoin Independence Day (I coined and popularized that term). August 1st was the flag day, and it commemorates the outcome the UASF threat produced, not BIP-148 itself.
Second, BIP-148 was not just "ordinary users" running nodes at home. It was a cross section of the entire Bitcoin network, something a lot of BIP-110 supporters seem to disregard: developers, exchanges, wallets, miners, and mega whales, alongside ordinary users.
Most important to understand is that BIP-148 and the small block camp carried a massive amount of economic weight. Chain split markets ran on @bitfinex through 2017, and outside of those markets I know of many OTC deals struck privately in whale groups to trade one side of a split against the other. There was skin in the game on both sides of the war, and huge amounts of BTC put on the line to show real conviction. This was as much an economic war as an ideological one, and that point is rarely acknowledged.
Even the companies backing BIP-148 were taking real risk. BIP-148 was never merged into Bitcoin Core. Running it meant deliberately installing different software and accepting that if the UASF chain lost, you could be reorganized off the chain entirely. Bitmain spelled that scenario out themselves, calling it a wipe out, in the same post where they laid out their hard fork contingency. Dozens of companies committed anyway (BIP-110 supporters would likely call them suitcoiners today).
On the topic of hashrate, BIP-148 had no version bit of its own. It required bit 1, which was BIP-141. So the accurate way to state it is that BIP-148/BIP-141 had 30-45% of hashrate behind it for most of its deployment window. During that time I was COO of BTCC, overseeing a mining pool that was the biggest one signaling SegWit.
So the UASF threat had three components that made it credible: economic weight, hashrate, and nodes. BIP-110 only had nodes. That is UASF cosplay, not a real UASF.
Another point to cover: Mechanic was spreading misinformation in Spaces (and likely other places) that BIP-148, a UASF, activated SegWit. That is false. It was technically BIP-91 that brought miners in line with BIP-141. BIP-148 was effectively frontrun and never had to be tested. So Bitcoin Independence Day, while celebrating the flag day deadline, is as much a celebration of BIP-91 as it is of BIP-148.
So no, it was not just nodes and conviction.
Just think about things rationally for a minute. Why would buying a node-in-a-box give you the right to dictate what anyone else on the network does, regardless of whether it's a miner or another user? Does buying two nodes-in-a-box give you that power? Of course not. Btw the whole plug-and-play node culture came after the Blocksize War. In 2015-2017 you just downloaded the software and ran it on your computer.
Stay humble and stack sats, but also stay humble when people who lived through the history try to explain it to you.
hodlonaut
@hodlonaut
I fully accept what happened yesterday. It is sad, I will admit that. But it also feels like a catharsis.
BIP-148 is celebrated as Bitcoin Independence Day, because it proved that ordinary users, running nodes in their homes, could force the most powerful mining cartels and corporations in the industry to back down. The users had no hashrate, no exchanges, no lobbyists. They had conviction and they had nodes, and that was enough.
BIP-110 ran the same play with the same conviction, a reasoning that was shared by all bitcoiners five years ago (Bitcoin is money and not a grift database), and node support at levels at least comparable to 2017. This time the miners and the corporate layer simply refused to follow. They extended their spam-friendly chain and moved on like nothing happened.
Remember yesterday as Bitcoin Dependence Day.
What changed between 2017 and 2026?
Not the users. They showed up with the same fire.
What changed is everything that grew in the years between. ETFs. Treasury companies. Custodians holding millions of coins for people who will never touch a node. Hashrate concentrated into a handful of pools building templates for the whole world. Capture of the governance of the reference implementation resulting in stark philosophical pivot.
Those already celebrating Bitcoin Dependence Day are not simply cheering an outcome they won. They are treating evidence that miners and the corporate layer now control Bitcoin as if it were a grand cypherpunk victory, while ridiculing the people who fought for decentralization and for Bitcoin as money.
In my opinion, and in my heart, legacy Bitcoin is not what I signed up for. Captured. Centralized. Led by suits.
No longer about freedom, sovereignty, or the mission of separating money from state.
No longer about the things that made me a ride or die bitcoiner for many years.
The fire that originally drew me to Bitcoin is still alive in the node runners who supported BIP-110. I will follow it where it goes.
As for legacy Bitcoin, I have no interest in it anymore as a freedom project. In my mind, it is now a stock. -
Adam Back reposted
Bitcoin Dawg
@bitcoin_dawg
#bitcoin LEGEND
The Bitcoin Historian
@pete_rizzo_
#bitcoin LEGEND ADAM BACK HAS BEEN FIGHTING WITH THE FAILED BIP 110 FORKERS WITHOUT REST FOR OVER A YEAR
THEY'VE TRIED TO SMEAR HIM WITH LIES ABOUT JEFFREY EPSTEIN
THEY'VE BELITTLED HIS MASSIVE SCIENTIFIC CONTRIBUTIONS TO THE BTC WHITE PAPER
A MOB HAS HARASSED HIM DAILY FOR OVER A YEAR
HE CALMLY EXPLAINED WHY THEIR FORK WOULD COMPLETELY FAIL UNTIL IT DID.
WHAT A LEGEND ๐ฅ -
Adam Back
@adam3us
filter bip closed.
-
Adam Back
@adam3us
bitcoin views filtering as damage and flood-fills around it. (to paraphrase John Gilmore's quote).
-
Adam Back reposted
Blockstream
@Blockstream
Announcing Blockstream Swaps.
Trustless atomic swaps for Bitcoin, Liquid, and Lightning. Hold BTC or LBTC and pay Lightning invoices without managing channels or inbound liquidity. Reach Lightning from cold storage while keeping full control of your funds.
Built as a complementary service to strengthen ecosystem resilience and redundancy. Currently in beta.
Full announcement: blog.blockstream.com/announcing-blockstream-swaps
Beta access: blockstream.typeform.com/to/y1L5wyZT -
Adam Back reposted
-
Adam Back reposted
Alex Thorn
@intangiblecoins
we were proud to sign this @bitcoinpolicy letter calling for broader access to frontier models for cyber defenders
americans should not have to rely on chinese AI to defend themselves, their projects, companies, or clients from cyber attacks
RED TEAM NEEDS THE MODELS ๐ฆ
Bitcoin Policy Institute
@bitcoinpolicy
Today, Bitcoin Policy Institute and a broad coalition from across the digital-asset ecosystem are publishing an open letter calling on the worldโs leading AI labs to provide qualified open-source defenders with trusted access to frontier AI models.
The past several weeks have made the need for this abundantly clear. The people defending digital-asset infrastructure and open-source software need access to the latest AI capabilities to perform comprehensive security reviews and stay ahead of increasingly sophisticated adversaries.
The coalition includes open-source development organizations, major custodians, treasury companies, payment services, security firms, capital allocators, and others whose businesses and customers depend on the integrity of open-source infrastructure and libraries.
Open-source defenders often occupy the least privileged position in the AI security landscape. They have limited access to the strongest internal cyber models and are frequently blocked by guardrails when using publicly available frontier systems for legitimate security research. As a result, they often resort to less capable open-weight alternatives.
We are urging frontier AI labs to establish a clear, trusted pathway for qualified open-source and digital asset defenders to access their strongest capabilities, with sufficient compute and secure environments to conduct meaningful security reviews. Frontier AI could become one of the most powerful defensive technologies ever developed, but only if defenders get fair access to those systems.
Itโs time to give defenders the tools they deserve.
Read the open letter, add your organization, or sign as an individual on our website at btcpolicy.org/ailetter -
Adam Back reposted
Bitcoin Policy Institute
@bitcoinpolicy
Today, Bitcoin Policy Institute and a broad coalition from across the digital-asset ecosystem are publishing an open letter calling on the worldโs leading AI labs to provide qualified open-source defenders with trusted access to frontier AI models.
The past several weeks have made the need for this abundantly clear. The people defending digital-asset infrastructure and open-source software need access to the latest AI capabilities to perform comprehensive security reviews and stay ahead of increasingly sophisticated adversaries.
The coalition includes open-source development organizations, major custodians, treasury companies, payment services, security firms, capital allocators, and others whose businesses and customers depend on the integrity of open-source infrastructure and libraries.
Open-source defenders often occupy the least privileged position in the AI security landscape. They have limited access to the strongest internal cyber models and are frequently blocked by guardrails when using publicly available frontier systems for legitimate security research. As a result, they often resort to less capable open-weight alternatives.
We are urging frontier AI labs to establish a clear, trusted pathway for qualified open-source and digital asset defenders to access their strongest capabilities, with sufficient compute and secure environments to conduct meaningful security reviews. Frontier AI could become one of the most powerful defensive technologies ever developed, but only if defenders get fair access to those systems.
Itโs time to give defenders the tools they deserve.
Read the open letter, add your organization, or sign as an individual on our website at btcpolicy.org/ailetter -
Adam Back
@adam3us
those who don't understand internet physics, are doomed to learn John Gilmore's quote the hard way.
"The internet interprets censorship as damage and routes around it" -John Gilmore
(cyherpunks list co-founder) -
Adam Back
@adam3us
for reflecting on 110 fork, good time to re-read
"Please rejoin bitcoin now [...] It would be sad if bitcoin lost people disillusioned due to simple lack of understanding of what's going on there, we're all trying to defend bitcoin and keep it on mission"
Adam Back
@adam3us
On the filter fork topic.
I don't usually have time, but this morning listened to one of the twitter spaces from earlier in the week, with some well meaning relative bitcoin newcomers, that humanized them, and their concerns and thoughts for why they thought that made it logical to support 110.
My feeling after listening, is if these are the people with #110 in their handles, I'm sad to see them about to fork off and get disillusioned without understanding why bitcoin rejected 110 robustly.
So here's a more empathetic, constructive higher level version of explaining why not. I hope it's high-level and first-principles enough that everyone can follow.
They seem to want to understand what makes people tick, and are suspicious of intent. So, if someone asked me why is Bitcoin important and what is it, I'd say my (personal) mission and hope for bitcoin is to build the cypherpunk future, that "Snow Crash" was a blueprint, and work backwards from there. Bitcoin I hope leads to fully free markets via bearer unseizable, hard mathematically dependable money. Not everyone is comfortable with that level of freedom, but that's my view. And at this point, I believe that surprisingly, even now many governments have come to understand and value bitcoin's gold-like mathematical assurance, a positive development. Others may have milder views than myself, but still like hard censorship resistant money.
Because of motive suspicion, if it's not obvious: I hate spam with a passion, that's how I came to design hashcash while researching decentralized bearer money with others, and running nodes in privacy related cypherpunk p2p networks nearly three decades ago.
People seem upset about the default op return policy change in bitcoin. I will just assert, there are extremely robust and simple reasons for bitcoin changing default relay policy, and most just didn't do their research, so don't know what those are, or maybe not technical enough to fully understand though there have been 1000s of posts trying to explain in various simplified ways. So that lack of understanding lends itself to shared build-up of false narratives. So here's my back-to-basics higher level explanation.
The decentralization needed to create cypherpunk money has implications a: side effect of decentralization is that you can't impose your views on others. The very decentralization mechanism that helps that, is working against what BIP 110 wants, which at it's most basic is a quest to police other people. I understand supporters don't see their intent like that, but introspect deeper.
You can modify your software, but not anyone else's. Another critical and incredibly robust technical bitcoin immune system is bitcoin can't have people who don't understand technology basics insist on eroding security, decentralization robustness and core properties. That would end badly, fast, and so people will fight you on that.
So the message is Bitcoin respectfully says "no" to what you want. Sorry, and bitcoiners do genuinely understand and empathize that you mean well, have high level thoughts that make emotional sense, and articulate sensible bitcoin-defensive high level ideas, but they are not grounded and without you seeing it, the way you propose to achieve your ideas, hard-conflict with free cypherpunk permissionless money.
My advice is to listen to more experienced people who understand the system and why it works the way it does, to whatever detail you want to understand the grounded reasons for why this is the implication of decentralization and cypherpunk money.
I guarantee you the developer and protocol ecosystem shares and exceeds your views on bearer hard money (and dislike of spam). You may not agree with individual developers choices, views, way of expressing themselves etc, BUT you also need to understand the IETF-like decentralized technical consensus process creates a protective change resistance, that is highly effective at protecting bitcoin mission. The implication of which is no developer can change anything without technical consensus from hundreds of other developers and protocol observers who are pedantic and extremely knowledgeable clever people who won't let any unaddressed technical question past. The protective change resistance is robust and decentralized in an amplifying way because of this technical consensus.
And the many highly technical mainline developers' cypherpunk mission mindsets are probably far more determined than you can even handle on clarity of understanding and views about freedoms on permissionless networks, as many of you are probably still subconsciously inured by the matrix, where they have transcended that, and grew up immersed in it decades ago. They think natively in this space, while you are just grappling with the surface. Many wont have internalized or have the experience to know how this internet physics works, where there is no policeman, no policy authority, just mathematics, free market and hard money. That has implications for your views also, unfortunately.
Now the tough pill, which is unfortunately true: If you won't listen to reason, educate yourself, learn, the same radical freedom applies to you: your permissionless recourse is to club together and create a fork. But bitcoin won't be joining it. (With respect and no sleight intended.)
Please rejoin bitcoin now, or later if you're not convinced and need to experience 110 forking off and fizzling for yourself to start that journey of introspecting and learning. It would be sad if bitcoin lost people disillusioned due to simple lack of understanding of what's going on there, we're all trying to defend bitcoin and keep it on mission. Including btw the 110 technical promoters, just they wandered off plot somehow.
Join the cypherpunks on bitcoin, come cypherpunk summer๐ in a few weeks. -
Adam Back reposted
ใพใคใใกใใ
@maturichan3350
Completed(ใปโใป)๐ฉทโจ
Adam Back
@adam3us
๐คฃ top kek๐
-
Adam Back reposted
Alistair Milne
@alistairmilne
Can't spam the chain if you don't mine any blocks
-
Adam Back reposted
onlywens
@onlywens
bip110ers are unironically declaring their loss of confidence in Bitcoin 's role as a tool for freedom because the network design did not allow them to unilaterally impose their preferences for censorship on the other 99.998% of the network that does not support censorship. ๐ค๐
-
Adam Back reposted
Vortex | BIP448
@theonevortex
> Yep. And itโs centralized and captured with pure fiat governance and culture.
Nope. Bitcoin just didn't care about your virtue signaling. Get over it.
> I have no interest in the narratives about what constitutes "real" Bitcoin.
Yet you keep talking about it every day on twitter.
> Iโve lost faith in BTCโs potential to serve as a technology
You never even understood it in the first place.
> then thatโs where Iโll focus my energy. Itโs about the IDEA, not the name.
As we've said for nearly 4 years, enjoy your shitcoin.
> I put my energy and attention where I have faith and conviction.
So talking nonsense on twitter all day, got it. -
Adam Back reposted
James Viggiano
@jamesviggy
๐
Coinjoined Chris โก
@coinjoined
When you see a Bitcoin node debate and nobody's been called a liar or a pedo yet:
-
Adam Back
@adam3us
110er mistake: claiming bitcoin must URSF otherwise by game-theory miners will have to switch. wrong! 110 obviously didn't have consensus, users could do nothing. or simply run bitcoin-cli invalidateblock 0000000000000000000169eb6f811ddbd0daf343af7b62180cdb13e7c78dbc16 if worried
-
Adam Back reposted
Michael Saylor
@saylor
A fool and his money are soon parted.
-
Adam Back reposted
Saunter ๐ฅ๐จโ๐จ
@StackingSaunter
The resolution of a temporary softfork experiment
-
Adam Back reposted
-
Adam Back reposted
Zach Herbert ๐บ๐ธ
@zherbert
This is a travesty. We need to be able to use American frontier models for hardening our code and defending against cyber attacks and exploits.
If we donโt open up the tech to the good guys, then the bad guys will have the upper hand.
Rob Hamilton
@Rob1Ham
Yesterday I began fully integrating the @OpenAI trust cyber program into my Bitcoin Red Team efforts.
This morning I woke up to see this.
I am now being blocked from doing additional analysis on a codebase which I've already responsibly disclosed to, and have received confirmation had legitimate findings.
To be clear, this is after having already KYC'd and completed the onboarding process months ago to use the cyber capabilities OpenAI has to offer.
I am now prevented from being able to continue the investigation in a further effort to make sure their code changes are sufficient, as well as understand if there are other issues that have yet to be discovered.
It absolutely guts me as a patriotic American to have to do this, but I will be going back to using Chinese open source models to conduct my research to protect Bitcoin infrastructure.
Black hats will not hit these issues. The white hats will. We've hit a local minima in policy. Intelligence is unrestricted for those who don't follow rules, and those who engadge in harm reduction are left on the sidelines.
What are we doing in this country? How is this keeping people safe?
Please do something @DavidSacks @sama @realDonaldTrump -
Adam Back reposted
Walkerโก๏ธ
@WalkerAmerica
The level of unbridled delusion among bippers needs to be formally studied... Truly remarkable to see a group so insistent on rejecting reality and fabricating fairy tales.
What do you even call this level of denial?? -
Adam Back reposted
grubles ใฐใฉใใซใบ
@notgrubles
Even in death, bip110 is distracting people away from what should matter -- tracking down the coldcard hacker, throwing them in prison, and recovering the bitcoin for the victims.
-
Adam Back reposted
instagibbs
@theinstagibbs
No we don't. Luke asserts that it was triggered sometime during the core dev preceding Tabconf but there were many non core devs there. At least a couple dozen.
There has been no public information on the case. -
Adam Back reposted
Coinjoined Chris โก
@coinjoined
They really are creating a new shitcoin
Mr.Hodl
@MrHodl
I can't look away! ๐๐คฃ๐๐คฃ๐
-
Adam Back reposted
Dylan LeClair
@DylanLeClair
Re: BIP 110 post mortem.
Miners don't control Bitcoin, and pools don't control miners. Pools are payout coordinators for thousands of individual operators who can repoint hashrate elsewhere in ten minutes. A pool signaling against its miners' interests just loses the hashrate.
Miners exchange hashrate for block rewards, then sell BTC to pay energy bills in fiat. If there's minimal economic support behind a fork, the rewards can't be monetized and mining it is burning money. Hashrate follows the buyside, because that's how they stay in business. That's what "economic nodes" means. -
Adam Back reposted
FRANCIS โ๏ธ BULLBITCOIN.COM
@francispouliot_
Covenant bros:
Covenants can allow a multisig co-sign server to enforce a monthly spend limit (or any type of frequency) directly on chain? Is this correct and if so, which proposals?
Are there other ways to achieve provably enforced spend limits with current consensus? -
Adam Back reposted
HeroGamerโก
@herogamer21btc
๐จ Never forget:
These BIP-110 people have wasted multi-million dollars/BTC worth of Bitcoin developersโ time and energy, which could have gone into making Bitcoin better money. -
Adam Back reposted
Coinjoined Chris โก
@coinjoined
In case you missed yesterday's events:
"well hijacking bitcoin with a minority fork was worth a try" -
Adam Back reposted
Bruce Fenton
@brucefenton
If you were on the BIP 110 side and are surprised - re-evaluate and learn.
This should have been obvious. -
Adam Back reposted
Mr.Hodl
@MrHodl
BMechanic thinks Vitalik left because Bitcoin Core wouldn't let him blow up the OP_RETURN. That's nonsense. He could've forked his own implementation and set the limit wherever he wanted.
He left because he wanted a pre mine. Plain and simple -
Adam Back reposted
Mr.Hodl
@MrHodl
He also belives that there will be no more halvings if BIP110 fails..
@GrassFedBitcoin I know you don't see this but I promise this gets remembered for the rest of our time on here. -
Adam Back reposted
Aaron van Wirdum
@AaronvanW
Just in case the Bdashersโ wipeout argument does stick around: Bitcoin nodes can always reject the BIP110 chain even in the *extremely* unlikely scenario that it would overtake the Bitcoin chain at some point, by running bitcoin-cli invalidateblock 0000000000000000000169eb6f811ddbd0daf343af7b62180cdb13e7c78dbc16.
(This tells your node that the first block on the BIP110 chain is invalid, which of course means that entire chain is considered invalid.) -
Adam Back reposted
Mr.Hodl
@MrHodl
Narrator: There was in fact no wipeout risk
-
Adam Back reposted
Michael Saylor
@saylor
No. Iโm saying virtually all the miners, exchanges, custodians, wallets, holders, markets, and economic infrastructure chose Bitcoin over BIP-110. Nobody controls Bitcoin. Consensus emerges from the network, and the network has spoken.
-
Adam Back reposted
AA โก๏ธ
@AAStack
Me waking up this morning and noticing a lot fewer โBIP-110โ tags behind peopleโs names on X.
-
Adam Back reposted
Vortex | BIP448
@theonevortex
I knew.
Shinobi
@brian_trollz
I knew.
-
Adam Back reposted
Sam Callahan
@samcallah
If I played a key role in a group that pushed a contentious chain split that failed miserably less than 24 hours ago, Iโd probably take a step back for a bit and reflect.
-
Adam Back reposted
Chun
@satofishi
Luke, youโve gone bankrupt not only financially but also in terms of personal credibility. Feel free to change the PoW algo next. It wonโt end well either.
Vijay Selvam
@vijayselvamxo
Unreal that @hodlonaut doesnโt understand bitcoin after being around all these years
-
Adam Back reposted
Mike Schmidt
@bitschmidty
Instead of waiting on a roadmap from just a couple leaders, involving increasingly drastic actions (hard fork | proof of work changes | additional softforks), myopically-focused on an ever-dwindling subset of a subset of a subset of spam, on an alternate blockchainโฆ
Join the Bitcoin builders already working on improving Bitcoin. Security. Privacy. Layer 2 payment networks. Combating mining centralization. More testing, more code review. Broad improvements to Bitcoin as money. No roadmap, yes decentralization. -
Adam Back reposted
Mr.Hodl
@MrHodl
They literally highjacked hash to signal for BIP110
The people behind this decision should be removed immediately.
OCEAN
@ocean_mining
Update for OCEAN miners:
We want to clarify yesterdayโs activity around the BIP-110 and non-BIP-110 mining options.
For roughly 18 hours, some miners using OCEANโs Stratum templates may have believed they were mining on the non-BIP-110 chain while their hashrate was directed to the BIP-110 chain.
To eliminate any possibility that miners were disadvantaged, OCEAN will make a direct Bitcoin rebate payment to affected miners based on the rewards they would have earned on the non-BIP-110 chain during that window.
Approximately 0.3 BTC will be distributed, with payments completed within the next 72 hours.
Weโll publish the transaction details once the payments are sent.
The default endpoint is now back on the non-BIP-110 chain. Both options remain available so every miner can choose where to direct their hashrate.
Your hash. Your choice.
๐ -
Adam Back reposted
Murch
@murchandamus
Since it will likely land here on Twitter soon anyway:
I have recommended the removal of Luke Dashjr from the BIP Editors to the mailing list. -
Adam Back reposted
Michael Saylor
@saylor
Bitcoin worked exactly as designed. BIP-110 was free to fork, and the network was free not to follow. The result was decisive: about 99.85% of Bitcoin's hashpower stayed with Bitcoin. The BIP-110 branch mined only two blocks and is already more than 80 blocks behind.
-
Adam Back reposted
AA โก๏ธ
@AAStack
Me watching everyone slowly remove BIP-110 from their X names like it was never there.
-
Adam Back reposted
Farside Insights
@FarsideInsights
Click below to see 154 pages of BIP-110 nodes stuck at height 961,633
www.bitnod.es/node_explorer.php?filter=services%3DNODE_KNโฆ -
Adam Back reposted
Portland.HODL
@PortlandHODL
The irony here about changing defaults is palpable.
-
Adam Back reposted
Farside Insights
@FarsideInsights
Coinjoined Chris โก
@coinjoined
@ocean_mining joins in the attack ๐คฃ๐คฃ
-
Adam Back
@adam3us
bitcoin-cli invalidateblock 0000000000000000000169eb6f811ddbd0daf343af7b62180cdb13e7c78dbc16
-
Adam Back reposted
Winston Alexander โก๏ธ๐บ๐ฒ
@_BitcoinCapital
-
Adam Back reposted
rijndael
@rot13maxi
One of many mistakes
Here are more (non exhaustive):
- trying to make a case that spam is destroying bitcoin when fees are sub-1s/vb
- conflating โstop the jpegsโ and โfire coreโ
- making the alternative to โcentralized core and centralized miningโ be a client with one maintainer and a single pool (who is the same person)
- refusing to participate in futures markets
- blocking devs, miners, businesses, exchanges rather than try to build consensus
- trying to push legal liability onto miners who mine opreturns
The list goes on -
Adam Back reposted
Stephan Livera
@stephanlivera
No URSF was necessary after all.
That shows you how unserious these BIP110'ers were.
Being internet keyboard warriors only gets you so far. -
Adam Back reposted
Octavian
@Octavian_rollo
In short, actual users decide what Bitcoin is.
Scandalous stuff. ๐คฃ -
Adam Back reposted
Fundamentals ๐ฒ ๐ฅ
@Fundamentals21m
BIP110 is an attempt to make a safe space for people who canโt live in the free world Bitcoin requires
It shouldnโt be a personal failing to need it but itโs an illusion - based on a fundamental flawed thinking that any minority can assume control of it whenever they want.
The safe spaces never last.
This is why Bitcoin is the only option - warts and all.
Wanna remove joegs? Grow up, get coding, and solve the problem. -
Adam Back reposted
-
Adam Back reposted
Farside Insights
@FarsideInsights
The BIP-110 chain just needs to spend c$409 million on mining to get to the end of the difficulty period and then another c$100 million to get to the point where non-compliant transactions are banned
-
Adam Back reposted
ะฮKฮDฮI๐๐ฆ
@nakadai_mon
This is life now. Amazing.
ะฮKฮDฮI๐๐ฆ
@nakadai_mon
Life after BIP110 forks off from the Big Bitcoin network:
-
Adam Back
@adam3us
110er mistake: disabling upgrade hooks. blocks future soft-fork upgrades. so there is no consensus, and that is why it was rejected by bitcoin economic users, economic nodes, and therefor by miners (as service providers to economic nodes).
-
Adam Back
@adam3us
110er mistake: making 110 temporary. that's an admission that 110 is defective as if deployed permanently it would break things and more likely permanently make unspendable some UTXOs. and prevent any further soft-forks.
-
Adam Back
@adam3us
110er mistake: arguing 55% activation is reasonable. it is reckless, dangerous if it had some support, and it's an admission there is no consensus for the fork. as we learned: trying to force activation without consensus leads to failure, and a new BSV-grade or weaker fork coin.
-
Adam Back
@adam3us
110er mistake: disabling IF statements in script. does nothing useful to stop spam. and guarantees no ecosystem consensus for 110 as it breaks miniscript, is petty vandalism with no benefit, and actually makes some bitcoin UTXOs unspendable (temporarily and maybe permanently).
-
Adam Back
@adam3us
110er mistake: claiming bitcoin wipeout risk from 110 remains a threat into the future. wrong. economic nodes will run bitcoin-cli invalidateblock 0000000000000000000169eb6f811ddbd0daf343af7b62180cdb13e7c78dbc16 even though it's statistically ~0% chance. just as good practice.
-
Adam Back
@adam3us
110er mistakes: claiming there bitcon faced wipeout risk by 110, and so game-theory meant miners would switch at the last minute. wrong. as there was no economic support, no consensus, hashrate was low, and continuing to fall post fork, so the probability of pulling ahead is ~0%.
-
Adam Back
@adam3us
110er mistake: story that "big bitcoin" (companies) or governments or miner cabal conspired against them, and so bitcoin is hurt. wrong. there was no consensus for 110, and so the economic users and market ignored it, no economic nodes were ready, and so miners didn't mine it.
-
Adam Back reposted
Peter Todd
@peterktodd
The โdifficult decisionโ:
โHey guys, do you think we should keep on mining a worthless fork for ~$200k per block?โ
Roughnecks
@Roughnecks110
A few minutes ago at 0340 UTC we had a team meeting and made the difficult decision to stop mining operations under the name Roughnecks. This decision did not come lightly. We do not see this a defeat for the BIP110 movement but an escalation to the next step. Anyone who is mining on the BIP110 chain under the current algorithm is advised to stop until further notice. We are grateful for all the love and support we have received in this adventure. The fight will continue without Roughnecks as the vanguard. We apologize to anyone who feels let down by us. Much love to all the Roughnecks out there๐
-
Adam Back reposted
ProofOfCash
@ProofOfCash
You come at the king, you best not miss
-
Adam Back
@adam3us
mistakes by 110ers: claim 110 is like SegWit UASF. wrong, SegWit had widespread consensus, vast majority of economic nodes were upgraded waiting to enforce. 110 has far less than < 1% of economic nodes, no consensus. so it failed, in similar ways to all prior contentious forks.
-
Adam Back
@adam3us
mistakes by 110ers: arguing nodes control protocol changes and miners will capitulate. subtly wrong. the economic users control the protocol, via the market. they transmit their views by transacting with their economic nodes. 1000s of nodes with no economic use have no influence.
-
Adam Back
@adam3us
more mistakes by 110ers: claim it's fine "find out if there is consensus" by starting a contentious fork activation without consensus. no, it WILL fail. the way to find consensus is to fix defects reported and see if it can reach consensus. everyone knew it didn't have consensus.
-
Adam Back reposted
Stephan Livera
@stephanlivera
Most miners ignored 110.
Cypherpunk summer!
orangesurf
@OrangeSurfBTC
What an exceptional turn of events
- First block was Standard by Antpool
- BIP110 managed to pull up level with Standard miners despite all the odds
- F2Pool (who famously were hard Anti-BIP110) then extended the Standard chain
- Finally Ocean Miner "Simple Mining" sealed the kiss of death -
Adam Back
@adam3us
more mistakes by 110ers who admit it can't work: "we should try anyway". no, we should not, as the side-effects are worse than spam. eroding bitcoin's censorship resistance, pushing a practice of selectively censoring things, is highly risky legal compulsion risk. very bad idea.
-
Adam Back
@adam3us
false claims have been made by 110ers "bitcoiners are pro-spam" false, everyone dislikes spam. But, it's mathematically impossible to censor bitcoin, 110 has many defects, does not to work - so has no consensus. you can't force without consensus or you end up with a BSV like fork
-
Adam Back
@adam3us
i hope people misled by 110 promoters aren't disillusioned onto a weaker fork than BSV. that's a sad end, don't do it. come back, learn why it failed: TL;DR you can't force forks without consensus, if you try anyway, you end up with a BSV like fork. and that happened yesterday.
-
Adam Back reposted
Teddy Bitcoins
@TeddyBitcoins
If you think bitcoin needs bip110 you donโt understand bitcoin and you donโt understand bip110.
-
Adam Back reposted
MARS SPITS BARS ๐ฅ
@marsspitsbarz
Mechanic officially knows less about Bitcoin consensus than the #notgonnanoders
Imagine the smell -
Adam Back reposted
Stephan Livera
@stephanlivera
Ironic. @lukedashjr thinks Antpool and f2pool are 'joining the attack' (by not signalling 110), and then... Ocean just mined a non-110 block!
-
Adam Back reposted
THC Humor ๐น๐งฒ
@THChumor
The meme explains the politics better than most serious threads ever could
-
Adam Back reposted
๐ค๐ผโก MIR ๐จ๐ญ๐ฆก
@mir_btc
-
Adam Back reposted
orangesurf
@OrangeSurfBTC
A simple explainer of what just happened
RIP BIP110 โ ๏ธ -
Adam Back reposted
Fundamentals ๐ฒ ๐ฅ
@Fundamentals21m
This is what Ocean paid $850K a year for
-
Adam Back reposted
Murch
@murchandamus
By the way, this is a UASF, so if you are against this motion, youโll have to run a URSF. ๐ฅธ
-
Adam Back reposted
Rob Hamilton
@Rob1Ham
๐จ๐จ๐จEMERGENCY DISCLOSURE๐จ๐จ๐จ
CON-001: Consensus Divergence
Severity: Critical
Confidence: High
Description: If you run BIP 110, your node will have stalled and will be unable to use bitcoin for sending or receiving payments.
Remediation: Running Bitcoin Core
colourorange ๐ฅช
@_colourorange
when you receive the dreaded @Rob1Ham โhiโ ๐๐๐
-
Adam Back
@adam3us
cypherpunk summer๐
-
Adam Back reposted
Danny Scott โก
@CoinCornerDanny
And there's that BIP110 fork they pretended wouldn't happen.
A fairwell to that credibility they all lost. -
Adam Back reposted
UTXO Punk
@UTXO_Punk
Adam Back
@adam3us
"Veni, vidi, forki" -Julius Dashjr
-
Adam Back
@adam3us
"Veni, vidi, forki" -Julius Dashjr
-
Adam Back
@adam3us
fork conclusion celebration at @Caviarandbull with bitcoin celebrity chef @MarvinGauci. (the mocktail is coincidentally named "popcorn")
-
Adam Back reposted
Coinjoined Chris โก
@coinjoined
Maybe, later today, once they realize just how little support they had, the Knotsies will come to a realization...
-
Adam Back reposted
Casey
@rodarmor
-
Adam Back
@adam3us
we told you so!
-
Adam Back
@adam3us
they forked off and found out๐คทโโ๏ธ
tick-tock, next-block. -
Adam Back reposted
Gareth Jenkinson
@gazza_jenks
That's that for BIP-110. Forked off, found out. I truly don't understand how anyone thought this would have legs.
Now, let's get back to what matters. Bitcoin is still the ticket to our freedom from a broken financial system.
Adam Back
@adam3us
Game over, checkmateโ๏ธforkers. As we said for last 6 months you'll just fork off, but if you wanna fork around and find out๐คทโโ๏ธ here we are. Hope you learn something, and the people misled by it, read/listen to the post mortems, don't get disillusioned and come back to bitcoin๐
-
Adam Back reposted
Meyga Vox
@meygavox
During this time:
-
Adam Back reposted
ProofOfCash
@ProofOfCash
BIP-110 node-runners right now
-
Adam Back reposted
Rob Hamilton
@Rob1Ham
My current informed perspective of the bitcoin software ecosystem.
-
Adam Back reposted
Remu โก๏ธ
@btcbenchmark
It is confirmed then.
Iโm looking for a lot of โI was wrongโ posts on my timeline tomorrow. -
Adam Back reposted
mononaut
@mononautical
WE HAVE FORK-OFF!
BIP-110 nodes have rejected the non-signaling block at height 961632, and fallen behind the canonical chain tip.
mononaut
@mononautical
ONE BLOCK TO GO
-
Adam Back reposted
David Bailey๐ต๐ท $2.0mm/btc is the floor
@DavidFBailey
Watching the BIP110 livestream with mechanic and Kratter, they tired to get @LukeDashjr to join the stream but he refused. Said he is โbusy with other thingsโ
Too cowardly to face his sycophants -
Adam Back reposted
โฟitcoin Chef Marvin Gauci
@MarvinGauci
Did the fork just happen @happyforkday
@adam3us ๐ฅ๐ฅ๐พ@saylor -
Post not available here, view on X
Adam Back
@adam3us
Game over, checkmateโ๏ธforkers. As we said for last 6 months you'll just fork off, but if you wanna fork around and find out๐คทโโ๏ธ here we are. Hope you learn something, and the people misled by it, read/listen to the post mortems, don't get disillusioned and come back to bitcoin๐
-
Adam Back reposted
David Bailey๐ต๐ท $2.0mm/btc is the floor
@DavidFBailey
Itโs official:
BIP-110 was the least popular, most incoherent, most inconsequential, softfork ever attempted to activate. Everyone who pushed this sybil attack has much to reflect on and the ring leaders should be dumped in the dustbin of history. Farewell ๐ซกโ๏ธ
RIP-110 -
Adam Back reposted
Samson Mow
@Excellion
It costs about $200k (3.125 BTC) in opportunity cost to mine a BIP110 block.
No takers? The future of Bitcoin is at stake here. Isnโt it? -
Adam Back reposted
Tone Vays
@ToneVays
And @ocean_mining joins the Attack ๐
-
Adam Back reposted
ใพใคใใกใใ
@maturichan3350
-
Adam Back reposted
Tone Vays
@ToneVays
In my opinion, the only one who could be working with the Feds is Luke Dashjr (The Ringleader).
- Kratter, Mechanic, Tomer, Hill & Guida are suffering from "Megalomania" which is a common syndrome in Content Creators w/ a God Complex (also true for Devs)
- Knut, Bechler, Matteo, BigSean, Asanoha are in the 'Useful Idiots' category who might still realize they are being fooled.
- Simon Dixon & Jack Kruse are in the "everything is a conspiracy" so Bip110 good, Core Bad... The End!
- Fred Krueger gets his own category cause he is just there for the clicks and engagement
- Hodlonaut is actually in ALL 4 of the above! (Very Impressive) - Maybe even all 5, confidential informants & undercover feds look exactly like him (Every Time)
- Nick Szabo & Beautyon are in the category of "Oh No, we have to pre-emptively comply with future government regulations"
- Bob Barnett gets his own category of "Why the F*ck are you still pro Bip110, you know how Retarded it is, you actually understand how bitcoin works"
* If I did not call your name, you were not worth mentioning, but you probably believe that if Bip110 Wins you will be a future opinion leader and relevant!
** I didn't feel like tagging any of the above (as most of us have each other blocked anyway), but TRUST ME, I will say it to your FACE! You are the biggest danger to Peoples Life Savings this Decade and probably for years to come!
Litoshi, LamboWenMoon๐ฅ
@Litecoin__Lord
Is there anyone else that thinks Matthew, 10 seconds later, Kraaatter is a government plant?
-
Adam Back reposted
Rob Hamilton
@Rob1Ham
Oh i knew that I did plenty of testing with it!
-
Adam Back reposted
Samson Mow
@Excellion
"Use a real secure element" quietly assumes the SE is the whole trust boundary, and that the seed is structurally locked inside it. Neither has held up. Ledger Recover shipped a firmware path that shards the seed out to three custodians. When people objected, Ledger's answer was that firmware capable of key extraction had "always been possible" to write, and that users had simply been trusting Ledger not to ship it. So the actual model isn't "the silicon won't let the seed out," it's "we promise not to." BOLOS is closed, so there's no way to check the promise is being kept, and the chip documentation sits behind an NDA, so you can't check the layer underneath it either. Jade puts the gate outside the device, where you can run the oracle yourself and read the code.
Worth remembering the trust boundary took a while to settle, too. On the original Nano S the SE didn't drive the screen or the buttons, so an attacker owning the MCU could show you one address while the SE signed another. Ledger moved the display into the SE from the Nano X onward, which is a tacit admission that "keys are in the secure element" was never the whole story.
On your point about "breaking the ESP32," the level of evil maid attack needed to take advantage of EM fault injection is akin to someone replacing a Ledger device completely and logging PIN entries. Neither of those is a silicon problem.
None of which makes Jade invulnerable. The ESP32 is a general purpose MCU and it behaves like one under a lab attack. But Jade is the only wallet where I can read every line of the firmware, run the oracle myself, and see the whole security argument end to end rather than being handed a certificate and asked to trust it. For a device holding real money, that tradeoff isn't close. Jade is genuinely great, and I think it's underrated precisely because its threat model is honest about what silicon can and can't do. -
Adam Back reposted
Dr -ck
@ckpooldev
The fact people have been unable to understand the difference between Bitcoin consensus and node mempool policy after a year of people trying to clarify it explains how we got here.
-
Adam Back reposted
Fundamentals ๐ฒ ๐ฅ
@Fundamentals21m
Honest appeal to the 110 guys:
Life will go on after this month and the instinct to defend the network will still be there and the work will still be there to do.
Itโs gonna be ok but I will always consider this act to have been childish and hostile.
Iโm not gonna have a lot of faith in your judgement about how Bitcoin works for a little while
For almost all of you, itโs nothing that canโt be sorted out over a few dozen beers.
If you donโt see this because you block me - you can still play too - itโs just gonna be harder. -
Adam Back reposted
Farside Insights
@FarsideInsights
BIP-110 mandatory miner signalling is expected to start in just under 24 hours (Currently due at around 21:00 UTC on Saturday 8th August 2026), the signalling itself is a contentious softfork & a likely outcome is a chainsplit. Below are some public tools which are available to monitor the situation:
forkmonitor.info Maintained by us, funded by @lclhostresearch
This website is designed to monitor Bitcoin chainsplits. The website is connected to many clients, including pretty much every BIP-110 client ever released
fork.observer Maintained by @0xB10C
This is a similar website to Fork Monitor, but with better graphics (A live dynamic block diagram is included)
www.bitnod.es Maintained by us, funded by @lclhostresearch
This node tracking website includes a BIP-110 activation tracker. The website also contains mempool statistics charts for Bitcoin Core 31.1 and Knots 29.3, such that one can compare respective mempools during the split. One can also track tens of thousands of nodes, including details such as User Agent and at what block height each node is on
miningpool.observer Maintained by @0xB10C
This website can provide information about missing, extra or conflicting transactions compared to block templates.
stratum.miningpool.observer Maintained by @0xB10C
This tools provides information about which block header mining pools are building on top of, in real time
Markets & Prices
In contentious splits like this, one would also typically want to look at markets and trading venues to watch order books and prices. Miners may also want to watch markets to obtain information of the value of each side of the split. However, in terms of markets and prices, the BIP-110 side has an exceptionally low level of economic support, almost near zero. We are not aware of any trading venues that will support trading BIP-110 coin at this point. Nor are there any futures markets we are of. Therefore, from an economic point of view, the BIP-110 side is not likely to have any matrial traction and there are no markets to watch when the fork occurs. -
Adam Back reposted
Yan at Swan
@skwp
Swan Vault is safe from the Coldcard issue, based on Blockstream Jade x.com/i/article/2085755797342953472
-
Adam Back reposted
Michael Tidwell
@miketwenty1
BTC PAYServer Vuln is severe enough to go out of the way to notify people. Please do so to your networks!
TABConf telegram, TAB email list blasted, X
Already notified. -
Adam Back reposted
Tone Vays
@ToneVays
So #bip110 blocks are now mining Large Spam Transaction which could be even bigger than 100KB which is the new Op_Return limit they are screaming about ๐๐คฆโโ๏ธ... this is Insane!!!
Portland.HODL
@PortlandHODL
Looks like a policy wedge, That's a V3 TRUC parent that's larger than 10KB.
This violates BIP431 -
Adam Back reposted
Blockstream
@Blockstream
Post-quantum signatures aren't one-size-fits-all, and now developers can find the SHRINCS setup that fits theirs.
@blksresearch's explorer lets you tune signature size, signing cost, and verification cost to match your wallet, node, or miner.
Their sweep of 25,935 candidates found a fallback signature about 2 KB smaller than NIST's SLH-DSA, and 28% cheaper to verify.
blog.blockstream.com/searching-for-shrincs-parameters/ -
Adam Back reposted
Nicolas Bacca
@BTChip
Same position for any minority fork with no replay protection : the potential tiny profit is not worth the risk and hassle. Consider it doesn't exist and move on with your life.
Kevin Loaec ๐งโโ๏ธ๐
@KLoaec
โ ๏ธIMPORTANTโ ๏ธIn the next couple of days, a new shitcoin will fork off Bitcoin. It is a big security risk for people who just believe they will get an "airdrop" and want to sell it, to get more bitcoin.
I will write more about it, but here is the TLDR: ๐ -
Adam Back reposted
Blockstream Jade
@BlockstreamJade
Excellent architecture deep dive by Swan CTO @skwp.
Proud that @Swan chose Jade for Swan Vault.
Swan
@Swan
Your bitcoin keys are only as strong as the entropy used to create them.
That's why Swan Vault is built on @BlockstreamJade.
Swan Co-founder @skwp breaks down the full architecture, from key generation to 2-of-3 custody: www.swanbitcoin.com/product-updates/why-we-chose-blockstrโฆ -
Adam Back reposted
Swan
@Swan
Your bitcoin keys are only as strong as the entropy used to create them.
That's why Swan Vault is built on @BlockstreamJade.
Swan Co-founder @skwp breaks down the full architecture, from key generation to 2-of-3 custody: www.swanbitcoin.com/product-updates/why-we-chose-blockstrโฆ -
Post not available here, view on XPost not available here, view on X
Adam Back
@adam3us
also consider the fundamental threat model limit of the generic substitution attack: don't modify a HWW (ledger, jade, trezor etc), replace it with a look-alike with radio phone home (via relay or wifi). relay it to a human operator with the stolen real device. what next? glitter
-
Adam Back reposted
Remu โก๏ธ
@btcbenchmark
Wait so it was all a sybil attack? Always has been.
Jason Hughes
@wk057
Since we're about 48 hrs away from the BIP-110 "mandatory" signaling height, I wanted to quickly share my private node crawler stats.
Over the past several weeks, I gave a program of mine more spending power than is probably reasonable. It spent a not insignificant amount of BTC deduplicating nodes. Enjoy.
Raw node counts (% of total)
๐ต Total: 131,762
โซ๏ธ Bitcoin Core: 99,401 (75.4%)
โซ๏ธ Bitcoin Knots: 30,755 (23.3%)
โซ๏ธ Other: 1,606 (1.2%)
Raw BIP-110 signaling counts (% of total)
๐ธ Bitcoin Core: 17 (0.01%)
๐ธ Bitcoin Knots: 19,388 (14.7%)
๐ธ Other: 0 (Unknown)
๐น Total: 19,405 (14.7%)
Nodes found to be duplicates (% of version)
๐ด Bitcoin Core: 17,892 (17.8%)
๐ด Bitcoin Knots: 18,049 (58.7%)
๐ด Other: Unknown
๐ด Total duplicates: 35,941 (27.2% of total)
Deduplicated node counts (% of unique)
๐ข Bitcoin Core: 81,672 (85.1%)
๐ข Bitcoin Knots: 12,706 (9.6%)
๐ข Other: 1,606 (1.7%)
๐ข Total unique: 95,984 (72.8% of total)
Of the 19,388 Bitcoin Knots BIP-110 nodes discovered signaling for BIP-110, 71% of them were eliminated as duplicates, above average for the Knots nodes, leaving only 5,663 BIP-110 signaling nodes.
That puts non-duplicate BIP-110 signaling nodes at 5.9% of non-duplicate nodes.
My criteria for deduplication includes the basics (same IP) and some additional more advanced sleuthing of available data. Additionally, you may have already surmised from my intro that part of it also involves strategically sending real transactions.
Will keep the exact details private so that it can't be easily gamed in the future. It is impossible to find ALL duplicate nodes, however false positives are somewhat unlikely with my methodology. If my software has flagged a group of nodes as duplicate, there's an extremely high probability that its either the exact same node (with multiple IPs) or in the exact same location.
If a node wasn't able to be tested thoroughly enough to be confident for whatever reason, and isn't deemed duplicate by conventional means (same IP, for example) then it isn't considered a duplicate and gives it the benefit of the doubt.
If I get more time, I may start publishing some more detailed stats more regularly, since it seems my crawler successfully finds a large amount of nodes beyond those listed every public crawler. Unfortunately it's not cheap to handle the deduplication aspect, so will need to figure out how feasible that is to continue. It also involves operating from dozens of IPs to get connected to a supermajority of the network, which is pretty bandwidth intense.
Anyway, figured I'd share, since I don't think anyone is actually doing this at all at this level. There's a lot more to this, too. Some of it might scare privacy conscious people... so I'll probably keep my publicly shared info limited to node stats. -
Adam Back reposted
Lawrence Nahum
@LarryBitcoin
you can use micropython or other but for example have to be extra careful with garbage collector and immutables, secrets might be kept around for longer than necessary, harder to zero/clear, etc - and yeah I don't know if micropython or Arduino are designed for security generally
-
Adam Back reposted
Daniel ษrrr
@csuwildcat
Email is a horrible analogy for blocking spam in a decentralized protocol, b/c it's a centralized system w/ blocking based on IP/domain behavioral scoring, sender blacklists, and subjective, invasive content scanning. Ironically, it's a good analogy for the path 110ers are taking
-
Adam Back
@adam3us
maybe @arthur_van_pelt @GrassFedBitcoin @mattkratter @LukeDashjr matt hill @start9labs
can join a fairly hosted youtube (no biased muting/kicking) to face the music for when 110 time-wasting noise you've been peddling fails live tomorrow. we need the reaction shots on camera๐ -
Adam Back
@adam3us
@Loriss65 see this is the problem with you clowns who are suckers for the four horsemen root-kit for normie brains. your response to being absolutely stretchered in your stupid arguments is to jam up the timeline with disgusting things. do that again and i'll block you.
Adam Back
@adam3us
in the vain hope that your brain is still engaged read below tweet, muse on it for a week before opening your mouth, think, learn! no offense, but > $trillion asset class of new hope for humanity tech can easily and robustly reject dangerously stupid ideas.
Adam Back
@adam3us
here's a test for change ideas for bitcoin to *prevent* something: if you made the analogous change to TCP/IP to achieve what you're asking for on bitcoin, would it work?
try it out: could you stop spam by modifying TCP/IP?
that's a useful test as bitcoin is also ungovernable. -
Adam Back reposted
Samson Mow
@Excellion
The Anti-Exfil protocol also originated from @Blockstream and they developed the first production-ready code for it.
Anti-Exfil protects you against private key (or seed) exfiltration via signature nonces.
A dishonest hardware wallet can secretly hide tiny pieces of your private key inside the โrandomโ numbers it uses every time it signs a transaction. Over enough transactions, someone watching the public blockchain can put those pieces together, recover your key, and steal your bitcoin - without you ever noticing anything wrong.
Only two HWWs have this implemented:
@BlockstreamJade
@BitBoxSwiss (they call it Anti-Klepto)
@Blockstream and @adam3us have been protecting you from this class of attacks since 2021.
Blockstream Jade
@BlockstreamJade
Jade has had Anti-Exfil since the beginning.
A compromised hardware wallet can slowly leak your private keys through the nonces in its signatures, even if the keys themselves were generated securely.
Anti-Exfil stops this by using sign-to-contract: Jade cryptographically commits its nonce to random data from your host computer, fully re-randomizing it so no key material can be smuggled out.
Blog written by Andrew Poelstra: blog.blockstream.com/anti-exfil-stopping-key-exfiltration/
More details: help.blockstream.com/hc/en-us/articles/9641573399961-Whatโฆ -
Adam Back reposted
Blockstream Jade
@BlockstreamJade
Your bitcoin should answer to you alone.
Jade builds your recovery phrase from 9 independent sources of randomness, blended so nobody on earth can reproduce it. Watch the full setup: create your wallet, confirm it's genuine, and receive with confidence. -
Adam Back reposted
James Viggiano
@jamesviggy
I guess you didn't get the memo about the 2-3 new methods for putting "spam" on a BIP110 chain? And these new methods are far more harmful to the health of the chain than just using the garbage bin (OP_RETURN).
-
Adam Back reposted
Samson Mow
@Excellion
The @BlockstreamJade is one of the best hardware wallets on the market, bar none. I wonder how many people dismissed it due to the FUD that it lacked a secure element?
Secure elements aren't a panacea but are often sold as such. A physical SE in the device means everything needed to extract the seed is sitting right there, and potentially in the hands of someone that steals it. It's a stationary target. An attacker can wreck a dozen units learning the technique before touching yours. Ledger's Donjon has done exactly this to Coldcard silicon twice, the Mk2 ATECC508A and later the SE2 on Mk4, and voltage-glitched the Trezor Safe 3's MCU.
Jade moves the target instead. Your seed is encrypted with an AES-256 key that the device and a blind oracle build between them, and the oracle never holds more than a piece of it. The ESP32 only has ciphertext. You can't extract something that was never in there. The attack turns interactive, against a party who rate-limits you and wipes its half after three bad PINs.
Coldcard split your secret across three chips from different SEs. That genuinely helps against one vendor's silicon getting broken. But the pitch lands as arithmetic, and security doesn't really work that way. As we've seen, bad entropy at setup meant none of the silicon even mattered. You could have 10 SEs in the CC and that wouldn't have saved you. But people ate that security theater up.
My mind keeps circling back to what we could have done differently. I keep landing on the same conclusion: we should have pushed back on the SE FUD much harder, and promoted Jade far more aggressively. We'd never have attacked CC, but we should never have taken the unwarranted flak for Jade's security model. The FUD steered people away from Jade. If we'd fought it, maybe more of them would have avoided the CC tragedy.
When we first launched the Jade, it sold for just $39.99. For that price you got such an incredible amount of value (at launch and later with subsequent updates).
โก๏ธ Virtual secure element via blind oracle (@Blockstream's or self-hosted)
โก๏ธ Can function as a stateless signing device (like SeedSigner)
โก๏ธ Anti-Exfil protocol to protect against your seed being exfiltrated (Jade is one of only two HWWs that do this)
โก๏ธ Genuine Check verification to prove the device is authentic and untampered with
โก๏ธ Secure Boot ensuring only properly signed firmware runs
โก๏ธ BIP39 passphrase and duress PIN
โก๏ธ Air-gapped operations
โก๏ธ Store Liquid assets like @tether USDT
โก๏ธ Multisig support AND the ability to back up the multisig config (descriptors) for a setup involving ANY devices (or mixed hardware/software), as long as at least one Jade is part of the multisig - this makes multisig far less brittle since losing the config is catastrophic
The best part of all of this? You don't even need to BUY a Jade. You can build your own with almost any ESP32 board. Pair it with your own self-hosted blind oracle and you have a completely sovereign stack with no HWW vendor supply chain risk.
If you're looking for a new hardware wallet, take a serious look at @BlockstreamJade. It's built by a world-class team of engineers and cryptographers assembled by @adam3us. But don't take my word for it. The firmware is fully open source, so read it yourself.
Don't Trust. Verify.
blockstream.com/jade -
Adam Back reposted
Liquid Network ๐
@Liquid_BTC
Liquid has reached its 4 millionth block. ๐
Born from the OG sidechain whitepaper in 2014, developed and announced alongside the first sidechain, Elements Alpha, in 2015, and launched in production in 2018, Liquid has quietly become an important piece of infrastructure for bitcoin over the years.
It enables confidentiality by default, native asset issuance, 0-conf, and, more recently, high-assurance Simplicity smart contracts and a growing DeFi ecosystem.
Today, Liquid supports more than $5B in tokenized real-world assets, spanning stablecoins like USDT and DEPIX, tokenized stocks, private credit, and gold funds.
Four million blocks down. Bitcoinโs financial layer is just getting started. -
Adam Back reposted
Michael Tidwell
@miketwenty1
you are forgetting history..
Emergency Difficulty Adjustments.
That coupled with a PoW change.. we are throwing all the rules out of the window.. will come down to if exchanges want to support trading. if so.. i don't want passionate but rational people get rekt'd -
Adam Back reposted
Blockstream Jade
@BlockstreamJade
Jade has had Anti-Exfil since the beginning.
A compromised hardware wallet can slowly leak your private keys through the nonces in its signatures, even if the keys themselves were generated securely.
Anti-Exfil stops this by using sign-to-contract: Jade cryptographically commits its nonce to random data from your host computer, fully re-randomizing it so no key material can be smuggled out.
Blog written by Andrew Poelstra: blog.blockstream.com/anti-exfil-stopping-key-exfiltration/
More details: help.blockstream.com/hc/en-us/articles/9641573399961-Whatโฆ -
Adam Back reposted
Blockstream Jade
@BlockstreamJade
Most people carefully back up their multisig seedsโฆ
and forget the part that actually lets them reconstruct the wallet.
Without the configuration (descriptor), those seeds are incomplete. Jade can register and store your multisig configs on-device (up to 8) and export them later via QR if you ever need to rebuild the wallet.
Guide: help.blockstream.com/blockstream-jade/add-more-security-fโฆThis media couldn't be displayed. See it on the original post. -
Adam Back reposted
Simply Bitcoin
@SimplyBitcoin
This is what was said on the show @adam3us
"Don't get rid of your Cold Card if you are one of the people that is affected."This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Michael Ford
@fanquake
Iโve pushed up a new round of -static-pie Bitcoin Core binaries that Iโd like to get more testing of! More details on the mailing list: groups.google.com/g/bitcoindev/c/UgGHs-_YGvw
-
Adam Back reposted
wiz
@wiz
I know everyone is busy right now, but I need you to take a few minutes and write me a letter of support for .bitcoin x.com/i/article/2085024715257655296
-
Adam Back reposted
Maximus Maximalistus
@maximalistus
Harvard published a paper named The Value of Open Source.
That remarks how Open Source is a game changer and generates wealth.
In Bitcoin the motto is Open Source Everything.
@BlockstreamJade Bitcoin Wallet was build on that motto.
It is full open source.
Both the hardware and the software.
github.com/Blockstream/Jade
help.blockstream.com/hc/en-us/categories/900000061906-Bloโฆ
You can audit the code.
You can audit the hardware.
You can even build a wallet with off the self components.
Meaning that you can build a highly security device to secure your sovereignty with parts that are widely available in electronics stores.
Be free.
Self-custody your bitcoin.
Open Source Everything.
10% off on Blockstream store products with coupon "maximus".
rewards.blockstream.com/maximus
And the code JADEPLUSEXPRESS gets anyone free expedited shipping on a Jade Plus -
Adam Back reposted
-
Adam Back reposted
Rob Hamilton
@Rob1Ham
The cleanest repo is Libsecp256k1, the foundational library which handles all Bitcoin signatures.
Thank you Jonas and the entire Bitcoin Core libsecp256k1 team for your service, you are all heroes ๐ซก -
Adam Back reposted
-
Post not available here, view on X
Adam Back
@adam3us
prepare to lose. clearly the fork has no consensus. not even 1% by economic weight. the rented hashrate will evaporate. chain will mine probably 1 block and stall as money losing rented hashrate leaves. and then @lukedashjr will create a PoW change HF. my advice: stay on bitcoin
-
Adam Back reposted
Michael Tidwell
@miketwenty1
May sound insensitive or naive to some of you right now, but my theory (which I believe to be true), no purposeful foul play or intent will be discovered relating to @nvk. I hope this is true for all of CoinKite staff. It'll be disturbing if any of these conspiracies end up true.
-
Adam Back reposted
Blockstream Jade
@BlockstreamJade
Your bitcoin is only as safe as the randomness your keys are made from.
Jade blends 9 independent sources of randomness, from a dedicated hardware chip to camera noise, into a result that exists only once.
Our code is open-source, so anyone can verify it. -
Adam Back reposted
Blockstream
@Blockstream
First and foremost, we wish the @Boltzhq team the very best as they work through this situation.
They are excellent partners to Blockstream and the Bitcoin ecosystem, particularly at the intersection of layer-2 networks like Lightning and Liquid.
To strengthen ecosystem resilience and redundancy, Blockstream is launching a new swaps feature. This initiative was already in development as part of our broader effort to build a more resilient suite of tools for the Lightning and Liquid networks. This system is currently in beta testing with select participants.
This was not an effort to replace any one provider. We see Blockstream Swaps as a complementary implementation that adds much-needed redundancy and diversity to the ecosystem. These recent events have only reinforced that need, and we are accelerating efforts to bring Blockstream Swaps to market.
We welcome conversations with wallets, apps and other potential integration partners. -
Adam Back reposted
moonsettler ๐ฅช CTV / LNHANCE ๐ฅ!
@4moonsettler
anti-exfil should be implemented by all hardware wallets. why are #bitcoin holders not demanding it?
-
Adam Back reposted
L0la L33tz
@L0laL33tz
Update: The guy telling COLDCARD victims he'd help get their coins back via a lawsuit against Coinkite was not just ordered to pay his former clients restitution of $1.9 Million.
According to reports, Braziel was accused of stealing $5.5 Million from his former clients, and paid a total $6.4 Million in 2025 to settle the claims against him.
Braziel's objective seems to be to buy up claims on stolen COLDCARD coins from victims to turn a profit. Braziel does this because he knows that the chances of recovery are *not zero*.
If you lost funds in the COLDCARD hack, I know it's very compelling when someone shows up to tell you to tell you he can help make you whole again.
PLEASE DO NOT FALL FOR THIS.
The original settlement documents are not publicized and cannot be sent via email โ If anyone knows anyone in the DC area who can get to Delaware and pickup the documents on Braziel for me, I pay ๐ธ
L0la L33tz
@L0laL33tz
If you are looking to recover your COLDCARD funds, please do not go to this man.
In 2024, he got himself assigned a court case and ended up pleading the 5th amendment over 500 times after being accused of embezzling millions of Dollars from a company he was meant to represent.
Here's what the court had to say about him:
"Braziel committed conduct that, on its face, meets the elements of crimes that include theft, forgery, and tax evasion."
"Braziel provided Fisher Weiss with falsified records."
"Braziel manufactured alternative versions of the account statements."
"Braziel [...] had created falsified versions of the Company's bank records" to "conceal his self-dealing."
He was ordered to pay $1.9M in restitution. He was never criminally indicted.
Read the court filing yourself: courts.delaware.gov/Opinions/Download.aspx?id=366760 -
Adam Back reposted
Blockstream Research
@blksresearch
An aggregate signature lets multiple signers each sign a different message, then combine everything into one compact signature that proves who signed what. @real_or_random explains the primitive behind Cross-Input Signature Aggregation.
Full talk at Eurocrypt below. โฌ๏ธ
Blockstream Research
@blksresearch
-
Adam Back reposted
Blockstream
@Blockstream
Simplicity is moving from research into production. ๐
blog.blockstream.com/liquid-network-roadmap-0-conf-quantuโฆ -
Adam Back reposted
Rod Palmer ๐ฅ
@rodpalmerhodl
i fear not the man who has rolled 10,000 dice once, but I fear the man who has rolled one dice 10,000 times
-
Adam Back
@adam3us
if you have a @COLDCARDwallet 1st obviously move coins to a different HWW like @blockstreamjade, @trezor, @ledger etc BUT if you were affected by sweep attacks: do NOT smash or throw it away. don't get hopes up, but it may be useful to weakly prove ownership to a whitehat sweeper
-
Adam Back reposted
Blockstream
@Blockstream
Your recovery phrase backs up your bitcoin, so keep it offline.
Don't photograph it, don't type it into any website, and don't drop it into your notes app.
Put it on paper, or better still, steel. -
Adam Back
@adam3us
don't trust, verify.
not just a slogan, a mission statement! @blockstream -
Adam Back reposted
Alexander Leishman ๐บ๐ธ
@Leishman
To build secure systems you must be humble. If you do not deeply internalize your own fallibility you will not go that extra mile to ask yourself "what can I do to make sure this thing is still secure even if I'm dumb and made mistakes?".
-
Adam Back reposted
James Viggiano
@jamesviggy
The grift that everyone saw coming. Luke Dashjr is trying to position his hardforked altcoin as the real Bitcoin, following on the footsteps of notorious scammers like Craig Wright. Have fun playing with your bipcoins.
-
Adam Back reposted
Ben Kaufman
@_benkaufman
Weโre not forking
Ok weโre forking but itโs only a temporary fork
Ok itโs not temporary but itโs a majority fork
Ok itโs not a majority fork but we have miners support
Ok we donโt have miners support but it wonโt cause a chain split
Ok it will cause a chain split but it wonโt be permanent
Ok it will be permanent so weโre changing the mining algorithm -
Adam Back reposted
-
Adam Back reposted
Blockstream Jade
@BlockstreamJade
Buy a Jade Core for most stripped down Jade: store.blockstream.com/products/blockstream-jade-core
-
Adam Back reposted
Pavol Rusnak
@PavolRusnak
The only Coldcards that are not affected by the fiasco are the ones that are still running the original Trezor code on them
-
Adam Back reposted
Rich
@bitcoin__help
Same firmware, Jade Plus has extra features
(Genuine Check to verify the device was manufactured by Blockstream and SD/USB drive based firmware upgrades) -
Adam Back reposted
Blockstream Jade
@BlockstreamJade
Jade Classic (OG Jade) is fine.
Jade Plus offers more features. -
Adam Back reposted
Blockstream Jade
@BlockstreamJade
We will continue to give Jade Classic firmware updates. We will continue to sell the device.
-
Adam Back reposted
Ava Chow
@achow101
With all the talk of supplementing entropy with dice rolls, it's surprising to me that the methodologies I can find don't seem to talk about using randomness extractors to debias the results, with the exception of codex32.
-
Adam Back reposted
Shinobi
@brian_trollz
Do not take advice from clowns like @hodlonaut, @GrassFedBitcoin, etc. how to handle this Coldcard issue. I have heard advice they have given people that is completely off-base, and will lose people money. They are giving vulnerable people incorrect advice telling them to not move when they should.
These fucking clowns do not understand the first thing about how Bitcoin functions on a technical level, DO NOT take advice from them on how to handle something this technical and critical to your fund security. -
Adam Back reposted
Michael Saylor
@saylor
Weโre now tracking Bitcoinโs 200-week moving average and its premium to that level on strategy.com. Since the 200W MA became available, Bitcoin has traded above it 92% of the time. Today, it sits almost exactly on the line.
-
Adam Back reposted
sanket1729
@sanket1729
Coldcard bug in simple english. Code had a safety check to confirm the real randomness chip was in use. But the check only asked "does this setting exist?" But not "is it turned on?" It was off. So the wallet made keys from fake randomness, and fake randomness can be guessed.
-
Adam Back reposted
Antoine Poinsot
@darosior
Coldcard MK3, MK4, MK5 and Q are being drained. A bug lets attackers find your seed phrase without any action on your part. Only wallets generated using the dice roll method are safe, assuming you rolled at least 50 dice. If you donโt know, donโt remember, or arenโt sure, move your funds immediately.
-
Adam Back reposted
Dylan LeClair
@DylanLeClair
For everyone reading this now, please imminently share with anyone you know who may use a Coldcard. Do not wait. This is ongoing and coins are moving right now.
If your seed was generated on Coldcard without your own entropy, treat it as compromised and move the funds today. Temporary solutions are fine. Perfect is the enemy of good here, and there is a race against the clock. If you donโt know whatโs best for a new wallet right now, move the coins to custodian/exchange in the meantime. You can figure out a new cold storage solution later.
Truly heartbroken for everyone involved. ๐ -
Adam Back reposted
Wicked
@w_s_bitcoin
How to make a 24 word Bitcoin seed phrase with 256 coins [Repost] youtu.be/k5h7A7kRM8Y
-
Adam Back reposted
Mike Schmidt
@bitschmidty
There sure has been a lot of *talk* about Bitcoin development these last 18 months. Meanwhile, there's been an awful lot of actual development work done. Examples of what Bitcoin Core has been working on throughout this all:
- a node that syncs in nearly half the time
- a path to 5x faster (SwiftSync)
- a new GUI to make running that node easier, maybe even on mobile
- a redesigned mempool with better fee bumping and fee estimates
- a mining interface so individual miners can build their own block templates (Stratum v2)
- a private broadcast so your transactions can't be traced to your IP
- a reproducible map of the entire internet for node eclipse attack protection
- a better way to relay time-sensitive Lightning and Ark transactions for confirmation
- a multisig that's cheaper, more private, and looks like any other payment on-chain (MuSig2)
- a private payment address with zero linkable payments (silent payments)
- a threshold (e.g. 3-of-5) signature scheme that looks like a single signature (FROST)
- a proposal to fix known protocol bugs and current attack vectors (BIP54)
- a slew of post-quantum research to be ready for future attack vectors
- a first-ever independent security audit for more eyes on the code
- a new tool that attacks a live node the way a real adversary would (Fuzzamoto)
- a fix that killed an entire class of disk-filling attacks
- a replacement for a risky external library
- a consensus engine the whole ecosystem can build on (Bitcoin Kernel)
Over a hundred contributors and more than a dozen funding organizations around the world. Not without controversy. Not without bugs. But undeniable progress.
August will come and go. This work will continue. -
Adam Back reposted
Antoine Poinsot
@darosior
If you are affected, please send an email to coinkite.
This could help avoid other fund loss, by finding the cause and react if it's a bug, or avoid people moving coins in panic and making mistakes if it is not.
NVK
@nvk
No support or security emails to us related to this, only hear say and the Reddit mess.
-
Adam Back reposted
MARS SPITS BARS ๐ฅ
@marsspitsbarz
Imagine waking up in about 18 months realizing YOU were the one fudding all of Bitcoin X, crashing out over the fake death of Bitcoin, buying over-priced nodes from a company shilling a crisis only solvable by node ownership, ending friendships and blocking anyone who didnโt agree with you.
All while declaring yourself as the hardest core bitcoiner out there ๐ -
Adam Back reposted
jack
@jack
what we know so far about the @COLDCARDwallet issues
Max Guise
@max_guise
1/ Earlier today, our Bitcoin engineering and security teams at Block began investigating reports of non-Bitkey wallets being drained. To proactively protect our customers, we began investigating immediately. Hereโs what we found ๐งต
-
Adam Back reposted
instagibbs
@theinstagibbs
Sorry this is the time to panic
instagibbs
@theinstagibbs
Confirmed. Mk2/3 vuln, I don't think mk4 is but can't be certain
-
Adam Back reposted
ะฮKฮDฮI๐๐ฆ
@nakadai_mon
Dear Coldcard user:
1. Don't panic
2. Send coins back to your exchange, or migrate to other HW wallet.
3. Always make a small test transaction before sending large sums.
4. Take your time and do some research on how to setup a secure self custody solution that suits your needs. -
Adam Back reposted
Antoine Poinsot
@darosior
If you use a Coldcard mk3 in a single sig, move your funds ASAP.
Don't panic, but do it as soon as possible. It's trivial to find the issue with a frontier LLM, several people got to the same conclusion independently.
instagibbs
@theinstagibbs
Confirmed. Mk2/3 vuln, I don't think mk4 is but can't be certain
-
Adam Back reposted
Dee
@HodlDee
Iโm so sorry to everyone affected. My DMs are open if you need help or have any questions.
Firmware fix released. coldcard.com/docs/upgrade/ -
Adam Back reposted
instagibbs
@theinstagibbs
This was just done on a mk3 I have on hand, initialized cold. All it needed was number of button presses during setup.
-
Adam Back reposted
instagibbs
@theinstagibbs
Confirmed. Mk2/3 vuln, I don't think mk4 is but can't be certain
-
Adam Back reposted
Decentra Suze
@DecentraSuze
Absolute Spaces marathon.
I was listening from 3 to 4am UK time and youโre still going strong when I woke up.
Insane dedication. Thank you Wicked & everyone involved. Really appreciate it. ๐ -
Adam Back reposted
Wicked
@w_s_bitcoin
-
Adam Back reposted
-
Adam Back reposted
Sasha Hodder
@sashahodler
This is helpful
-
Adam Back reposted
Max Guise
@max_guise
10/ P.S. personally I recommend that anyone affected move funds as soon as they can safely do so - to a new wallet that does not use affected hardware. If you can, talk to a knowledgeable friend through your plan, and then execute it asap. Move deliberately, but donโt wait.
-
Adam Back reposted
Max Guise
@max_guise
1/ Earlier today, our Bitcoin engineering and security teams at Block began investigating reports of non-Bitkey wallets being drained. To proactively protect our customers, we began investigating immediately. Hereโs what we found ๐งต
-
Adam Back
@adam3us
happy cypherpunk summer๐
-
Adam Back reposted
Kevin Loaec ๐งโโ๏ธ๐
@KLoaec
More:
Kevin Loaec ๐งโโ๏ธ๐
@KLoaec
As people are still finding this 5h old post, here is what is happening:
- Coldcard MK3 random number generator is broken. Your funds are at IMMEDIATE RISK of being stolen
- MK4 and higher may be vulnerable to a more difficult attack, investigation ongoing. You are not at immediate risk, but may be in the long term.
- a multisig of MK3s is also AT IMMEDIATE RISK
- a weak passphrase or a few dice rolls on your MK3 are only buying you some time, and WILL GET BROKEN.
A strong passphrase (randomly generated and long) or a full entropy by dice rolls (90+ rolls) are SAFE.
What to do:
If you have an MK3 (or generated your seed on one), move your funds immediately. This is a race against the clock. Do not wait for tomorrow.
In any case, move to multisig in the near future, with multiple brands of signing devices. Consider using @lianabitcoin -
Adam Back reposted
Kevin Loaec ๐งโโ๏ธ๐
@KLoaec
I'm hearing a potential issue with some Coldcard wallets being drained.
I will not FUD, but would like to get at least reports of trusted people.
Can my followers, who own a CC, generated the mnemonic on the CC, and use it as a single sig check their balance and report if it's gone.
Hopefully a nothing burger, but gonna do my job here. -
Adam Back reposted
ะฮKฮDฮI๐๐ฆ
@nakadai_mon
I feel for @Coinkite @nvk and most importantly the customers. That sucks. Hope the issue is contained and for those vulnerable safely migrate their coins.
-
Adam Back reposted
Stephan Livera
@stephanlivera
Coldcard users please be warned about this serious security vulnerability - quick video explainer with a practical mitigation step
This media couldn't be displayed. See it on the original post. -
Adam Back reposted
COLDCARD
@COLDCARDwallet
COLDCARD Mk3 Security Advisory
If you generated a seed on a Mk3 after firmware 4.0.1, your funds may be at risk.
Mk4, Q and Mk5 are not affected based on our early analysis.
Read the advisory and migrate carefully:
blog.coinkite.com/coldcard-mk3-seed-generation-warning/ -
Adam Back reposted
ODELL
@ODELLXYZ
developing situation, but if you are currently using coldcard move your funds out of an abundance of caution
bugs have been found and exploited using ai
if you used dice rolls to generate your seed, you should be fine
if you use a passphrase, you should be fine
if you use multisig, you should be fine
would still move funds out of an abundance of caution
this sucks, coinkite team should release more info soon -
Adam Back reposted
Blockstream
@Blockstream
The Blockstream Jade lineup (Jade Classic, Jade Core, and Jade Plus) is unaffected by the recently reported RNG issue with another company.
We are preparing a blog post outlining best practices for anyone moving bitcoin to a new wallet, including how to generate fresh keys, verify addresses, conduct a test transaction and securely retire an old recovery phrase.
Frontier LLMs are uncovering previously overlooked vulnerabilities, and Blockstream is using the same tools to strengthen the QA reviews of our product suite.
But AI is not a substitute for open source: transparent hardware and firmware enable independent scrutiny, faster disclosure and quicker fixes. This is why Blockstream Jade continues to champion both open source software and hardware. -
Adam Back reposted
Remu โก๏ธ
@btcbenchmark
I run bitcoin core because it is the more principled choice and they have the moral highground
-
Adam Back reposted
Blockstream Jade
@BlockstreamJade
Fully open source.
How keys are generated. help.blockstream.com/blockstream-jade/faqs/how-does-jade-โฆ -
Adam Back reposted
Mr.Hodl
@MrHodl
Mechanic keeps framing this as us siding with MSaylor against BIP 110. That's backwards. Saylor sided with us. People have been on Spaces for the past year and a half fighting and trying to educate others about BIP444 /BIP 110. We run nodes. We set the block size limit knowing the network could safely handle up to four megabytes if spam hit. It's not about plebs or suits. It's about people who actually understand Bitcoin.
When that much money's on the line, you do your homework. Saylor did his. And our arguments made more sense than Luke's. -
Adam Back reposted
Dylan LeClair
@DylanLeClair
-
Adam Back reposted
Stephan Livera
@stephanlivera
Miners donโt want to end up on a minority hashrate chain that has almost no economic weight.
Most miners will just ignore BIP110. -
Adam Back reposted
Rob Hamilton
@Rob1Ham
The 2 weeks prior to the BIP 148 flag day, the network had 71.4% of blocks signaling for Segwit.
The 2 weeks prior to the flag day of BIP 110, the network has ~1% of blocks signaling for RDTS.
To compare BIP 110 to BIP 148 is deceitful at best, a lie at worst. -
Adam Back reposted
Samson Mow
@Excellion
GM. Stay humble and stack sats.
Btw thinking youโre Bitcoinโs savior and that you can force new consensus rules on everyone is not humble. -
Adam Back reposted
Yves ๐ฟ
@ZLOK
Announcement: I'm starting a new UASF (BIP to be submitted as soon as Claude writes it).
The goal is to allocate to my address all of Satoshi's coins. Also, automatically give me all UTXOs who haven't moved for more than 5 years. As well as 10% of all miners fees and 25% of all block rewards.
If this doesn't happen, Bitcoin dies. Like, for real.
The signaling deadline will be August 9th, with a threshold of 0.00001%.
I'm a very passionate minority and I run a node. So, if you don't fork all your nodes to reject mine, it means we reached consensus and you agree with my new rules. (Apparently this is how soft forks get adopted right?)
Thank you. -
Adam Back reposted
Stephan Livera
@stephanlivera
No, there are plenty of explanations of why it's a flawed idea. Here's just a recent one I wrote today
Stephan Livera
@stephanlivera
BIP110 supporters face a โdamned if you do, damned if you donโtโ problem.
If the plan is to continually soft-fork against spam:
- You create a precedent for using consensus to filter โundesirableโ use
- You expand the attack surface for regulatory pressure and capture
- You impose ongoing coordination costs that favor well-resourced actors
If itโs only a one-time (or temporary) soft fork:
- Spammers adapt their embedding methods
- Data still ends up on the chain (as current workarounds already show)
- The filter becomes theatre rather than a durable solution
One path risks centralizing power and setting dangerous precedents. The other fails to solve the problem it claims to address.
The more consistent position remains: keep consensus neutral. Let the fee market ration scarce block space, and let each node set its own local relay policy on what it is willing to filter or relay. -
Adam Back reposted
Stephan Livera
@stephanlivera
No this is misleading, it is not the responsibility of every HODLer to monitor and do a URSF every time some minority wants to ram thru a bad change.
Miners have already read the writing on the wall, and they will mostly ignore BIP110. As they should. -
Adam Back reposted
Stephan Livera
@stephanlivera
The hits keep coming for the BIP110 Karens
Steve
@steverabinow
BIP110 ADVENT continues. Today: PDFs.
The Bitcoin Whitepaper embedded contiguously in a BIP110 valid (and Knots standard!) transaction.
- Wouldn't fit in a Core-standard OP_RETURN
- Fits in BIP110 blocks for ~4x cheaper -
Adam Back
@adam3us
anything without consensus which someone attempts to force MUST be rejected as a matter of principle, for bitcoin's very immutability depends upon it. fortunately this is the n-th time and bitcoiners and the market immune system are getting stronger at it with each failed try.
-
Adam Back reposted
Fernando Nikoliฤ ๐ฆ๐ท ๐
@basedlayer
Bitcoin's neutrality is the whole product.
It confirms valid transactions without asking who you are or whether the rest of us approve of what you're doing with it.
So yes, it works for people you can't stand.
That's THE POINT.
A system that can exclude your enemy today can exclude you tomorrow as well.
So arguing that certain valid transactions shouldn't make it into blocks turns neutral money into governed money.
And we already have governed money, dumbasses ๐This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Stephan Livera
@stephanlivera
The real risk of creating a filter regime - @csuwildcat
This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Maple ๐
@GhostofMapl
BIP-110 is a centralised, content moderated shitcoin, endlessly forking chasing ghosts... Toodles, muffin. Now get to forkin.
-
Adam Back reposted
Steve
@steverabinow
Proof:
bitcoin-cli getrawtransaction c99ba3723689aa70d548b5188b3417f78c4f41a783f67d437810a209ee53d387|xxd -r -p|tail -c+1073>l.jxl
Inspired by knotslies.com -
Adam Back reposted
Stephan Livera
@stephanlivera
Inconsistency in the BIP110 argument exposed by @csuwildcat
This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Stephan Livera
@stephanlivera
Think about multi sig, or L2 protocols that require script. It ends up crippling scripting which arguably pushes more people to custodial instead of self custodial.
-
Adam Back reposted
Daniel ษrrr
@csuwildcat
Doesn't matter, all tree/script depth limitations do is force them to spread their embedded data across more transactions. Fundamentally, in any decentralized system that relies on collectively stored public keys and hashes, you cannot meaningfully interdict spam of those values.
-
Adam Back reposted
Farside Insights
@FarsideInsights
> this whole thing is that this could be a very good reminder to the miners and the big, big dollar companies in Bitcoin who's actually in charge, which ought to be the nodes
You just do not get Bitcoin! The whole point of Bitcoin is that nobody is "in charge". In the event of a material disagreement over the consensus rules, the existing rules must prevail. If Bitcoin does not have that property, of robust rules, it is useless, because the powers that be will be able to change Bitcoin -
Adam Back reposted
Mr.Hodl
@MrHodl
Last year I spent a ton of time in spaces and (even a podcast) trying to educate as many Bitcoin bulls as I could about how Bitcoin works. Soft forks are usually a good thing. They let us upgrade without anyone losing money when there's enough support from economic players and hash power. But this isn't that. This is what I consider an evil soft fork. At 55% activation with only a tiny economic majority of nodes and hash power it makes Bitcoin not secure. From everything I'm seeing on X right now the ecosystem is more than ready.
We're good going into August 8th. Enjoy the show. -
Adam Back reposted
Danny Scott โก
@CoinCornerDanny
Karen in action.
1st time I've seen that notice, wow ๐คฆ
_Checkmate ๐ ๐โกโข๏ธ๐ข๏ธ
@_Checkmatey_
You are observing a very different world to the one I see mate.
The RTDS client literally gaslights the user into thinking they are consensus, when they certainly are not. -
Adam Back reposted
Shinobi
@brian_trollz
Still waiting for Pulitzer winning "journalist" @hodlonaut to explain why he selectively left out a primary source to paint a misleading picture of a pair of PRs he used as a foundational piece of "evidence" in his slop narrative.
Only been literally multiple months now.
Shinobi
@brian_trollz
You literally lied, and completely misrepresented a pair of PRs and the developer discussions around them _to appear the EXACT OPPOSITE_ of what really occured: x.com/brian_trollz/status/2038050623208444374
You have refused for MONTHS to engage with this being pointed out. You are a fucking clown.This post is unavailable. See it on X. -
Adam Back reposted
PlanB
@100trillionUSD
To be clear (if it wasn't already clear from me retweeting Adam on this topic): I am against the bip 110 filter fork.
IMO filter fork proponents do not really understand:
- bitcoin as a decentralized bearer asset
- bitcoiners dislike spam more then they do
- why BCH fork failed -
Adam Back reposted
Stephan Livera
@stephanlivera
The inevitability of data storage on Bitcoin - explained by @csuwildcat
This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Michael Blankenship
@michaelbship
The overwhelming majority (outside of luke and friends) of devs that have significantly influenced Bitcoin's actual software are not 110 supporters.
What do you think this means? I'm serious, actually stop and brainstorm...
Do you think it means the majority of significant contributors to the actual software are malicious? or don't understand the consequences? -
Adam Back reposted
Eric | Infinity Over 21 Million
@over21m
Bypassing the established technical review process because a BIP lacks engineering consensus isnโt leadership, itโs a social attack. Attempting to coerce adoption through economic fear rather than technical merit is exactly the manipulation #bitcoin was built to render obsolete.
-
Adam Back reposted
calle
@callebtc
BIP110 is an absolute joke
Steve
@steverabinow
Ultra high resolution image files embedded contiguously in BIP110-valid txs? No problem.
-No Inscriptions-style decoding
-Doesn't use Taproot
-Knots policy standard
-Cheaper than Inscriptions (fee/quality)
-4x cheaper than OP_RETURN
Introducing JXL-n-hide. -
Adam Back reposted
Sergio Demian Lerner (sergio.lerner.rsk)
@SDLerner
I don't care whether you want to fork Bitcoin to save endangered raccoons or protect children from bullying. The cause is irrelevant.
Bitcoin's golden social rule is simple: if you try to fork Bitcoin without broad consensus, you loseโand you must lose decisively.
That rule is what makes Bitcoin resilient. Without it, Bitcoin becomes vulnerable to misinformation, false-flag campaigns, manufactured outrage, and social extortion. It fractures, corrodes, and eventually collapses.
If there is no broad consensus, there should be no fork date. Setting a deadline for a contentious fork is not coordinationโit's extortion. -
Adam Back reposted
Coinjoined Chris โก
@coinjoined
The lesson of the Blocksize Wars was that Bitcoin scales in layers, not by forcing everything onto the base layer.
Now, ironically, many of the people who inherited only the pleb-slop retelling of that history are turning it into a purity spiray, trying to constrain Bitcoin into something that preserves their ideological ideal of purity at the expense of actually scaling.
Keags
@ProofOfKeags
Yes bip110 makes BitVM constructions harder, and this is bad for bitcoin.
It increases attack surface area for BitVM (an all other layer 2) protocols dramatically while increasing the cost of data embedding marginally.
Having subtle bugs in jpg reconstruction code isn't going to destroy millions of dollars of people's hard earned money.
I remember a time when people actually wanted bitcoin to scale so it can legitimately challenge fiat money rather than it being a vehicle for people living a godless existence to fight fake holy wars.
I guess y'all would rather burn the world and make a nest out of the ashes than actually build something worth living in. -
Adam Back reposted
Rob Hamilton
@Rob1Ham
I called this almost 2 years ago.
Someone should get an answer from @LukeDashjr in how long he plans to wait until he changes proof of work. If/When 110 fails to get support.
Stealth launching a POW change is effectively a premine that allows him and anyone he deputizes to have time to prepare software and hardware to mine the ninja launch.
He had months old commitments written for the 110 client before he announced it, no reason why to think a POW change would be different.
Anyone who directly asks this question of Luke is either blocked, or if on telegram banned from the chat room and the message is deleted.
There has been a tone shift among @cguida6 @LukeDashjr and @GrassFedBitcoin on this topic over the past few weeks. They are all now discussing publicly a potential POW change.
I donโt think thatโs a coincidence.
Rob Hamilton
@Rob1Ham
Libre-relay proves Iโm not lying. It requires consensus change to fire the miners to stop this.
-
Adam Back reposted
David Parkinson
@Musqet_David
Same crew, same voyage, better ship.
A little weekend fun with AIโฆ -
Adam Back reposted
Mr.Hodl
@MrHodl
The best account on Bitcoin Twitter this year has been @coinjoined hands down. There is no second best at the moment.
-
Adam Back reposted
Samson Mow
@Excellion
BIP110 supporters are pioneering a new type of attack: the 1% attack.
If successful, it would show how trivial it is to attack the Bitcoin network. Just rent 1% of the hashrate and spin up 3k nodes. Attackers can be incredibly disruptive and waste massive amounts of time for exchanges, miners, and HODLers.
The actual monetary cost?
Rented hashrate: $0 before forking, as itโs still mining BTC; post-fork ~4.5 BTC per day.
Nodes: 3k nodes for $15k a month.
The solution to mitigating 1% attacks is simply to be pragmatic and disregard them. If you entertain them, you set a precedent for more in the future since the cost is so low.
This is why BIP110 must fail. -
Adam Back reposted
Mr.Hodl
@MrHodl
This is a good point. Most of the BIP 110 supporters came after 2020. They really don't have much grasp on Bitcoin's history
Danny Scott โก
@CoinCornerDanny
BIP110 crowd won't even understand it.
-
Adam Back reposted
Wicked
@w_s_bitcoin
Looking forward to citing BIP-110โs failure every time some retard in the future thinks they can change Bitcoin without broad ecosystem support.
-
Adam Back reposted
Danny Scott โก
@CoinCornerDanny
BIP110 crowd won't even understand it.
-
Adam Back reposted
_Checkmate ๐ ๐โกโข๏ธ๐ข๏ธ
@_Checkmatey_
You are observing a very different world to the one I see mate.
The RTDS client literally gaslights the user into thinking they are consensus, when they certainly are not. -
Adam Back reposted
Coinjoined Chris โก
@coinjoined
Running BIP110:
-
Adam Back reposted
Mike Schmidt
@bitschmidty
Today nine institutions including BlackRock, Fidelity, Coinbase, and Strategy announced the Bitcoin Security Consortium (@BTCconsortium), pledging $15M toward Bitcoin security work over the next three years. I've agreed to help coordinate the group's work as a volunteer.
I said yes because supporting Bitcoin's developers and helping people understand their work are the two things I've spent my time in Bitcoin on, through Brink and Optech. This group wants to do both: fund the people already securing Bitcoin, and bring accurate information about that work to audiences it doesn't currently reach.
The group's first focus is quantum computing, a potential long-term threat that's reasonable to prepare for. Its true that a sufficiently powerful quantum computer would break Bitcoin's current signatures. What's usually wrong are the loudest "imminent doom" voices. The development community is already working on this.
These institutions want to help. I know exactly how "nine giant institutions form a group to 'help' Bitcoin" sounds, I had the same reaction. So before accepting, I spoke one-on-one with each company about their values and priorities, to judge whether this would actually be a productive initiative for Bitcoin. Two things mattered most to me, and I found the members already aligned on both:
- No pooled funding. Each member company funds who they choose, independently. The Consortium doesn't hold funds or pick recipients.
- No Consortium positions on protocol changes. Members speak for themselves.
I'm a volunteer, receiving no compensation from the Consortium. I continue to run Brink, independent of any Consortium member. I've committed to a year in this role, maybe I'd do two, but ultimately I see it as a seat that should rotate to other participants over time. My commitment is to Bitcoin, and that doesn't change.
My hope is that this effort results in more funding reaching more developers/researchers, on their own terms, and a measured counterweight to quantum panic, in both directions (no doomerism, but also no dismissal). Quantum is the first focus, but if this group works the way I think it can, there's room to support other security efforts down the road too.
More about the Consortium: x.com/Strategy/status/2080262323491455290
I expect plenty of skepticism. Ask me anything.
Strategy
@Strategy
Today we're announcing the Bitcoin Security Consortium @BTCconsortium: a group of leading financial institutions and Bitcoin companies supporting the long-term security of the Bitcoin network.
Members have pledged $15 million toward this work over the next three years. -
Adam Back reposted
Vikingo
@Vikingobitcoin9
This is @adam3us when bip110 fails to activate
Dudes Posting Their Wโs
@DudespostingWs
Mike Didge handcrafts "didgeridoos" to create incredible techno music and it sounds incredible
-
Adam Back reposted
Michael Saylor
@saylor
Bitcoinโs security is a shared responsibility.
Today we are launching the Bitcoin Security Consortium, backed by $15 million in commitments to support the developers and researchers strengthening Bitcoin for the decades ahead. www.strategy.com/press/leading-financial-institutions-bitโฆ -
Adam Back reposted
Samson Mow
@Excellion
In 2015, Andresen and Hearn began pushing Bitcoin XT (BIP101) which was intended to change consensus rules and increase Bitcoinโs block size.
They originally attempted to get BIP101 merged into Bitcoin Core, and said it would only go in if the other developers agreed.
They never reached that agreement.
The fight was over how much of an increase there should be and how fast it needed to come. But mostly it was over whether forcing a contentious hard-fork was legitimate at all.
A contentious hard-fork either breaks the chain in two or forces some to swallow rules they never agreed to.
Sipa, quoting someone from the debate: "I did not sign up to be part of a central banker's committee."
And so when they couldn't convince Core devs, Andresen and Hearn went directly to mining pools and misrepresented Bitcoin XT as an upgrade to Bitcoin Core. I know this firsthand because I was running BTCC Pool at the time and took the call with them.
They also set activation of BIP101 at just 75% miner signaling. That's below the 95% that normally locks in a Bitcoin consensus change.
This was the starting point of the Blocksize War which lasted over two years.
History rhymes. -
Adam Back reposted
Farside Investors
@FarsideUK
Exactly 100% right ๐ ๐
This is why it was so important that the small blockers won the blocksize war, so that now we don't need to worry about spam and we know how much the Blockchain will grow by -
Adam Back reposted
Dylan LeClair
@DylanLeClair
Bitcoin already has that fix. The block size limit and the fee market it creates are what actually constrain spam, which is the exact mechanism your hypothetical relies on.
The design space for embedding data in Bitcoin is effectively infinite. BIP 110 closes a few corners of it, and the data just moves.
So one fork was never the deal. The deal is whack a mole in perpetuity, paid for in contested consensus changes, and the market is looking at the terms, and choosing to pass.
For reference below: a novel way to encode arbitrary data on Bitcoin, fully BIP 110 compliant.
Steve
@steverabinow
BIP110 taketh away OP_IF, but giveth OP_PLENTY.
Introducing a novel way to encode arbitrary data in *contiguous* bytes. Up to 2MB fully BIP110 compliant.
OP_PLENTY encodes each 4 bit nibble of the raw data into a tapscript opcode. Decoding is trivial: take the opcode mod 22. -
Adam Back reposted
Keags
@ProofOfKeags
I'm calling it asymmetric because all soft forks are inherently asymmetric.
The question is whether or not people who build and maintain infrastructure have a responsibility to entertain arguments that are factually wrong beyond a certain limit.
The 110 position is, in my view, incoherent. It's not just a mismatch of values, but that its design does not even satisfy its own goals.
Should we allow any misguided soft fork attempt to win by default simply because a bunch of people on social media got conspiratorial about things they don't understand?
If this is how things are done I think we're going to find ourselves with much more difficult issues down the line and it may very well make Bitcoin incapable of actually scaling via the layered approach with dispute resolution at base.
Engaging via a URSF is an implicit accepting of the frame that this is entitled to succeed by default, which is not something I personally want to entertain.
That said, I'm clearly engaging it in this thread so maybe we're well past that. -
Adam Back reposted
James Viggiano
@jamesviggy
-
Adam Back reposted
Michael Ford
@fanquake
Bitcoin Cores 29.x branch continues to receive maintenance. 29.4 has been released
Bitcoin Core Project
@bitcoincoreorg
Bitcoin Core v29.4 was released!
It is available from: bitcoincore.org/bin/bitcoin-core-29.4/
Release notes: bitcoincore.org/en/releases/29.4/ -
Adam Back reposted
Strategy
@Strategy
Founding Members:
@Anchorage ยท @ARKInvest ยท @BlackRock ยท @blocks ยท @Blockstream ยท @coinbase ยท @DigitalAssets ยท @GalaxyHQ ยท @Strategy
Holders, custodians, exchanges, asset managers, and builders, united by a shared interest in Bitcoin's continued security. -
Adam Back reposted
Strategy
@Strategy
Today we're announcing the Bitcoin Security Consortium @BTCconsortium: a group of leading financial institutions and Bitcoin companies supporting the long-term security of the Bitcoin network.
Members have pledged $15 million toward this work over the next three years. -
Adam Back reposted
Bitcoin Security Consortium
@BTCconsortium
You can read today's announcement and more about the Consortium here: x.com/Strategy/status/2080262323491455290
Bitcoin has proven remarkably resilient through the work of an open, global community. We're proud to help strengthen it for the long term.
Strategy
@Strategy
Today we're announcing the Bitcoin Security Consortium @BTCconsortium: a group of leading financial institutions and Bitcoin companies supporting the long-term security of the Bitcoin network.
Members have pledged $15 million toward this work over the next three years. -
Adam Back reposted
Bitcoin Security Consortium
@BTCconsortium
Our first focus is quantum computing.
Large-scale quantum computers capable of threatening Bitcoin's cryptography don't exist today, and credible estimates place them years away. Preparing is a meaningful long-term priority, and one the community is already working on. -
Adam Back reposted
Bitcoin Security Consortium
@BTCconsortium
We support the people who build Bitcoin. We don't direct its development and we don't speak for Bitcoin. Each member organization funds and speaks independently.
Bitcoin's development is, and will remain, the work of a global, decentralized community of contributors. -
Adam Back reposted
Bitcoin Security Consortium
@BTCconsortium
The Consortium is modeled on the way industry groups have supported the open-source software they depend on, contributing resources and awareness without controlling the work. We will:
- Fund existing developers and researchers
- Inform the conversation about Bitcoin's security -
Adam Back reposted
Bitcoin Security Consortium
@BTCconsortium
Our nine founding members include holders, custodians, exchanges, asset managers, and builders, united by an interest in Bitcoin's continued security:
@Anchorage
@ARKInvest
@BlackRock
@blocks
@Blockstream
@coinbase
@DigitalAssets
@GalaxyHQ
@Strategy -
Adam Back reposted
Bitcoin Security Consortium
@BTCconsortium
We're the Bitcoin Security Consortium: leading financial institutions and Bitcoin companies supporting Bitcoin's long-term security.
Members have pledged $15 million to Bitcoin security research and development over the next three years. -
Adam Back reposted
Vortex | BIP448
@theonevortex
Hilarious watching these 110 people repeat the same false narratives over and over even when presented with objective on-chain data.
-
Adam Back reposted
Dathon Pwn
@DathonPwn
Your own documentation calls it a "validation gap".
The entire point of running your own node is to not have gaps in consensus validation. To have gaps is a consensus bug. Full stop.
Just because you can fix it by running terminal commands, does not change that definition. -
Adam Back reposted
Yves ๐ฟ
@ZLOK
Typical BIP110 agent: "I'm not a technical person but..." *proceeds to tell technical falsehoods to technically highly respected people*
Technical person: replies and explains in very simple terms why it's objectively wrong.
Agent: "Yeah yeah ok, but this is too technical, I'm not a technical person, I'm talking about the ethos and high level social stuff" *repeats the same technical falsehoods*
Loop forever ๐
๐คฆโโ๏ธ
BIP110 is a baseless attack on Bitcoin, using basic rhetoric tricks from 12yo bullies. Just mute the trolls.
(But always keep trying to share the truth with honest plebs getting bamboozled.) -
Adam Back reposted
Mike Schmidt
@bitschmidty
Itโs going to be okay.
-
Adam Back reposted
Vortex | BIP448
@theonevortex
> that small policy change damaged Bitcoinโs โsocial layer.โ
Nah, it just made a bunch of non technical virtue signaling newbies learn more about what bitcoin is, bitcoin is fuck you money and you don't get to tell others what they can or cant' do with it.
Welcome to bitcoin. -
Adam Back reposted
Richard โDickโ Whitman (๐/21M)
@GhostofWhitman
BIP 110 stopping spam
-
Adam Back reposted
Dathon Pwn
@DathonPwn
Thank you to Start9 for patching the Block Slop consensus bug that is in the BIP 110 activation client, left unpatched by @dathon_ohm and @LukeDashjr
Start9
@start9labs
From: Core or Knots (pre-RDTS)
To: Knots (BIP-110 RDTS)
Code: github.com/Start9Labs/bitcoin-knots-startos/pull/22
From: Knots (BIP-110 RDTS)
To: Core or Knots (pre-RDTS)
Code: github.com/Start9Labs/bitcoin-core-startos/pull/232
Pruned handled as well.
Same recovery module in all six PRs (Core 28โ31, Knots RDTS and pre-RDTS) -
Adam Back reposted
Coinjoined Chris โก
@coinjoined
๐ฏ The first line of Bitcoin podcasters has largely failed the community. Instead of helping people understand complex, nuanced technical developments, they fed audiences an endless stream of feel-good plebslop that was easier to consume than actual substance.
Rob Leder ๐ฅ
@rleder
I never supported it, but this whole argument over the past year has caused me to listen, study, and think about so many things. The nature of mesh networks and why voluntary filters are futile, what consensus really means and what incentives are required to change it, the mechanics of a soft forks activation (voluntary vs mandatory signal vs rule enforcement), how chain splits and reorgs play out, etc.
Itโs painfully clear that much of this community has been done a grave disservice by an informal non-technical Bitcoin โeducationโ system of podcasts, social media, and ra-ra cheerleading conferences (main hall presentations anyway). Theyโve been sold on trite cliches like โnodes run the networkโ to the point they thought they could just spin up a bunch of nodes and declare a UASF, and everyone else would be compelled to obey. When I actually learned about what happened in 2017, it occurred to me that it shouldnโt even be called a UASF, itโs just a UAF. Whether itโs soft or hard (or DOA) depends entirely on whether the miners think you are actually threatening to fire them. The 110 crowd doesnโt even know enough to bluff, nobody thinks they wonโt fold an hour into this, and nobody thinks they have much money anyway. -
Adam Back reposted
Coinjoined Chris โก
@coinjoined
Consider leaving the clown car now, or find yourself riding it off the Bitcoin highway later ๐คก
-
Adam Back reposted
Michael Sullivan
@SullyMichaelvan
Recently came to my attention that some people are not able to see this post on my profile anymore.
This is very likely due the high levels of (fake) reporting that it got from the BIP-110 crowd.
Anyways, here it is again, hope ya'll have a beautiful Tuesday ๐ป
Michael Sullivan
@SullyMichaelvan
I didnโt want to write this.
One of the deepest lessons Iโve learned from researching sentiment data is how irrational and angry people get towards the bottom of Bitcoin bear markets. People that are historically aligned often fall into conflicts that wouldnโt exist near tops.
The BIP-110 debate increasingly feels like one of those moments.
I wanted no part of that.
Iโve been publicly cancelled before, and I have no desire to go through that again. I know how painful it is to have an angry crowd criticizing and shaming you, which gives me a strong bias to avoid situations exactly like this one.
But Iโm pushing against that bias because (for better or worse) I have a novel dataset that offers a unique lens on the BIP-110 debate.
Iโm going to attempt to keep this unbiased, but before I do, Iโm going to lead with what will be my highest-conviction opinion of the entire piece:
People like Mechanic and Luke Dashjr understand Bitcoinโs consensus mechanisms better than I do, while Adam Back and Jameson Lopp grasp Bitcoinโs technical nuances more deeply than I ever will.
I am not here to pretend I understand these dynamics of this debate better than the people who have spent years studying them. Thatโs not why Iโm writing this.
โThen why should I care what you have to say?โ
Because there is another side of the debate that is also important, and itโs on this side I have a different perspective.
The social layer.
For those of you new to my work, Iโve been researching the language, narratives, and emotional patterns of different groups throughout Bitcoin. Iโve been (obsessively) studying the emotional regimes and crowd psychology associated with the space.
That includes the people now publicly associated with both sides of the BIP-110 debateโฆ and the differences between these groups are striking.
I believe I would be doing a disservice by keeping that data to myself simply because publishing it might piss people off. So there will be no paywall on this piece, no call to action halfway through, and I wonโt ask you to become a subscriber.
I simply want these charts to exist publicly, where anyone can examine them or interpret them differently than I do.
I will try to present it as fairly as I can, but I am not neutral, and neither is anyone reading this.
People will inevitably see different things in these charts.
This data cannot tell us who is technically correct.
But it can help us to surface clues about how the debate is evolving, who thinks they are winning, and why I believe one of these groups is currently experiencing an engagement-reinforced narrative environment. -
Adam Back reposted
Mr.Hodl
@MrHodl
This right here is what grassFEDBitcoin and LukeDashJr are counting on.
I'm starting to feel a little bad for the plebs.
Caylon
@CoSatoshi821
Ok, I'm actually confused. I wasn't in the space at the time. I'm reading there were actually three BIPs (91, 141, and 148).
-
Adam Back reposted
calle
@callebtc
๐ FILTERS ๐ DON'T ๐ WORK ๐
Someone found yet another a way to store JPGs for half the cost of OP_RETURN.
You've been lied to. At this point only the insane and utterly incompetent still believe in BIP 110.
Don't be a lemming. It's not too late to wake the f up to reality.
Steve
@steverabinow
BIP110 taketh away OP_IF, but giveth OP_PLENTY.
Introducing a novel way to encode arbitrary data in *contiguous* bytes. Up to 2MB fully BIP110 compliant.
OP_PLENTY encodes each 4 bit nibble of the raw data into a tapscript opcode. Decoding is trivial: take the opcode mod 22. -
Adam Back reposted
Murch
@murchandamus
Well, at least heโs no longer expecting my advice how to fix his BIP anymore.
-
Adam Back reposted
Bugle.News ๐ฏ
@bitcoin_bugle
NEW: Plebs marched in protest of rising hash lease prices arguing it is "immoral to charge plebs to lease hash during a spam pandemic"
-
Adam Back reposted
alp
@alpacasw
The bip 110 clowns are really only about gatekeeping who gets to be a bitcoiner.
Very krawiszesque energy to them.
Aslans Mane
@Aslans_Mane
Imagine trading folks like Mechanic and Luke for Wall Street suits and laughing about it.
-
Adam Back reposted
Coinjoined Chris โก
@coinjoined
How Dathon Ohm cooked up BIP110:
-
Adam Back reposted
HeroGamerโก
@herogamer21btc
BIP-110erโs โRetardmaxxingโ guide:
Just Fork It
Stop overthinking. Go full BIP-110er.
Kill the spam, protect Bitcoin as money.
No more data bloat.
Whoโs retardmaxxing with me?โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
Video explains how ๐ -
Adam Back reposted
HeroGamerโก
@herogamer21btc
There is only 1 way left.
@brian_trollz @adam3us @MrHodl
HeroGamerโก
@herogamer21btc
BIP-110erโs โRetardmaxxingโ guide:
Just Fork It
Stop overthinking. Go full BIP-110er.
Kill the spam, protect Bitcoin as money.
No more data bloat.
Whoโs retardmaxxing with me?โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
Video explains how ๐ -
Adam Back reposted
Rod Palmer ๐ฅ
@rodpalmerhodl
being mad about developers having sex is not a legitimate reason to fork bitcoin imho
-
Adam Back reposted
David Bailey๐ต๐ท $2.0mm/btc is the floor
@DavidFBailey
Iโm noticing some of the BIP110 ring leaders starting to distance themselves and act like they werenโt straight up accomplices in slandering core for 8 months
-
Adam Back reposted
Samson Mow
@Excellion
It's been three years since BIP110 activated. The suitcoiners, corrupt devs, and Blockstream call it Bipcoin, or Bcashjr, and they laugh. But we know the truth. It's the real Bitcoin.
There were 159 of us at activation. Now there are 83.
Nobody planned that number. It just happened, one excommunication at a time, one defection at a time, until someone counted the survivors and went quiet. Eighty-three. The same as the byte limit. We don't talk about it. We tell ourselves it's a coincidence, the way you tell yourself a lot of things while you wait for a block that will not come.
As I sit here writing this, I am scared, because I committed a grave offense against the network.
It wasn't even my fault, not really. I was using the new mobile wallet Dathon vibe coded, the one he shipped after asking an AI to "make it clean and monetary, no spam." Somewhere in that hallucinated spaghetti, the thing allowed an OP_RETURN of eighty-four bytes. One byte over. One byte past the sacred limit, the exact byte that separates a man of sound money from a data-abusing degenerate. I didn't type it. The wallet did. It just emitted the extra byte, cheerfully, the way vibe-coded software does the single worst possible thing with total confidence.
I messaged Dathon the moment I saw it. I explained that his own wallet had betrayed the one rule the entire chain exists to enforce. He read it. He replied, "user error." Then he blocked me.
I'm scared, and have had a long time to be, because I am now thirty-three hours into waiting for the block that confirms it. We command about half a percent of the hashrate, and it's all rented, mercenary machines that have no idea they're defending sound money and would just as happily mine a dog coin. When the rental budget runs dry, the chain stops until someone Venmos more. Salvation, meanwhile, is a difficulty adjustment two thousand blocks away, which at this rate lands sometime in the next decade.
The Great Maintainer has seen my tainted transaction. He runs the 21 all-seeing nodes that know all, and mine has lingered for thirty-three hours like a monkey-jpeg Ordinal. He hasn't said anything. That's the worst part. He just added me to a list. I don't know which list. There are many lists now. There used to be 159 of us and now there are 83, and I have started to suspect the lists and the number are related.
And the rumors are swirling. Kratter is recording a new episode. It's two hours long. The working title, I'm told, is my transaction ID. He won't say my name. He'll say it in his tone. He'll hold up my txid to the camera the way a priest holds up something he found under a floorboard, and the faithful will nod, and it will be done. Excommunication by podcast. The only due process left on the real Bitcoin.
My friend Arthur was number 104. His crime: he used nLockTime. An actual Bitcoin feature, older than most of the congregation, right there in the protocol since the beginning. But someone decided that timelocking a payment wasn't a monetary use case, it was "deferring value like a coward," which is fiat thinking, and the poll agreed. The poll had 110 votes, which, we later realized, was more people than we had left. Arthur defected to the captured chain, where the same ten-minute blocks actually arrive, and no one questions the motives behind his transactions. We don't speak of Arthur. We say his name only to warn the children.
Thirty-four hours now.
Someone messages me: "still not confirmed? sounds like a you problem, spammer."
I type back, "it was the wallet. Dathon's wallet."
"You know the rules. Don't play innocent, you pervert."
I put the phone down. Somewhere the captured chain hums along, 400 million people drowning in filth and convenience, their blocks landing every ten minutes like they're entitled to it. And here I sit, pure, principled, one of the 83, holding the real Bitcoin, undone by eighty-four bytes I did not type, waiting on hashpower we rented by the hour.
Thirty-four hours. Still no block. Still waiting for my judgement.
I have to go now. Mechanic is at my house and trying to look in my windows.
Samson Mow
@Excellion
If you want Bitcoin without arbitrary data, suitcoiners, corrupt devs, and captured people like myself, you'll need a private blockchain. You'll also have to KYC all users to make sure everyone is pure of heart and only uses it as money.
-
Adam Back reposted
Dathon Pwn
@DathonPwn
If its not a consensus bug, why is there a patch to make sure there are no consensus issues?
-
Adam Back reposted
Peter Todd
@peterktodd
Hilarious: a BIP-110 compatible data encoding scheme where every byte really does contain data.
"THE BYTES ARE TOUCHING!!!"
Steve
@steverabinow
BIP110 taketh away OP_IF, but giveth OP_PLENTY.
Introducing a novel way to encode arbitrary data in *contiguous* bytes. Up to 2MB fully BIP110 compliant.
OP_PLENTY encodes each 4 bit nibble of the raw data into a tapscript opcode. Decoding is trivial: take the opcode mod 22. -
Adam Back reposted
Vortex | BIP448
@theonevortex
100% false. I have given you all the links to prove every single one of your statements is wrong.
Defaults don't matter.
Core didn't invite more spam.
v30 was harm reduction.
Learn this. -
Adam Back reposted
Vortex | BIP448
@theonevortex
> And aren't we're having this conversation right now?
So far you are refusing to learn and instead opting to repeat false narratives. -
Adam Back reposted
Vortex | BIP448
@theonevortex
Your points are technically inaccurate, your comments on "purpose" are nonsensical and don't apply, you have no idea what you're talking about and refuse to do research and learn. This is why signaling is at less than 1% because people like you are who 110 is sending.
-
Adam Back reposted
Murch
@murchandamus
Itโs nothing personal. Itโs simply in the public interest to document how shoddily RDTS was developed.
-
Adam Back reposted
Coinjoined Chris โก
@coinjoined
Yes, they're angry at Core because they've been misled. For years, podcasters sold them a compelling but fundamentally false story about how Bitcoin actually works. Now the consequences of that misinformation are playing out, and everyone else has to pay the price.
The podcasters failed us. -
Adam Back reposted
Wicked
@w_s_bitcoin
With @PortlandHODLโs bipstream API, one stat that will be super interesting to track is how quickly the BIP-110 nodes shut down after the chain split.
-
Adam Back reposted
Michael Saylor
@saylor
The impulse to change Bitcoinโs rules merely to prevent others from using Bitcoin in ways you disapprove of is statist and alien to a community rooted in liberty, property rights, free markets, natural law, and Austrian economics. BIP 110 would impose monetary purity by fiat.
-
Adam Back reposted
Kudo
@CryptoC58828499
Iโm not technologically literate, but I know enough to know that the BIP 110ers have been getting schooled in every debate / discussion on these spaces in the last two months.
-
Adam Back reposted
Coinjoined Chris โก
@coinjoined
You chucklefuck took part in smearing and attempting to cancel Gloria and now you come crying because people are clowning on you and your ilk forking off?
-
Adam Back reposted
Rod Palmer ๐ฅ
@rodpalmerhodl
"any exchanges want to publicly support bip 110?"
[matt kratter pauses]
"anyone at all?"
[matt kratter wanders the desolate cities. even the wind is gone.] -
Adam Back reposted
Coinjoined Chris โก
@coinjoined
I'll spare the audience your whiney ahh video.
Publicly, you helped fuel a campaign that smeared a developer with serious allegations, contributing to an environment that drove her from her position.
It's fucking easy to preach civility after the damage is done. It takes actual character to reject mob behavior before reputations are destroyed. You chose the coward path: join the pile-on publicly, then seek absolution privately.
Classic short man behavior.
History won't remember your platitudes about unity. It will remember who stood by principle when it was unpopular and who bent with the prevailing wind.
When people look back on this episode they'll see you as someone who helped create the problem, then wanted credit for calling for peace once the consequences of your loser fork became undeniable ๐คก -
Adam Back
@adam3us
#bitcoin passes $63k 200wma
Adam Back
@adam3us
#bitcoin 200wma passes $62k
This post is unavailable. See it on X. -
Adam Back reposted
Bugle.News ๐ฏ
@bitcoin_bugle
NEW: BIP-110 is attempting to sneak undocumented, undisclosed consensus changes into Bitcoin and hoping nobody notices.
Murch
@murchandamus
Contrary than above release notes suggest, this contradicts BIP433: Pay to Anchor which states that no new consensus rules are introduced.
The additional new consensus rule is not documented in BIP110. Do the current RDTS clients implement that rule, @dathon_ohm? -
Adam Back reposted
MADEX
@spacebull
-
Adam Back reposted
Ademan555 | CTV FFS
@Ademan555
The problem is y'all are getting animated about locking the doors, but this is the vehicle in question:
-
Adam Back reposted
Said Nassar
@the_nassar
I have a theory about BIP110. This poll will either prove it or destroy it.
Be honest ๐ -
Adam Back reposted
Wicked
@w_s_bitcoin
If Core v30 gets blamed for kicking off the bear market, does BIP-110 failing get credit for kicking off the next bull market? Asking for consistency.
-
Adam Back reposted
Stephan Livera
@stephanlivera
That first clip is actually from my podcast. What she's talking about there is things like improvements to relay that would help L2's like lightning, while being mindful of DoS risks and pinning attack vectors.
Some of that work DID get in and you can see here L2/Lightning developers (@acinq_co @blockstream @lightning and @spiral_xyz ) all speaking positively on her work in how it helped them. x.com/bitschmidty/status/2072044097511043502
And people who want to see the bit just before/after the clip, see full podcast here youtu.be/QGHLk-W-mj8?t=346
Mike Schmidt
@bitschmidty
We could ask Lightning node maintainers if they found Gloria's work to help Bitcoin as money on L2s valuable...
-
Adam Back reposted
Mr.Hodl
@MrHodl
Punched blocked me.
Some people can't handle the truth
Adam Back
@adam3us
@mrhodl or @marsspitsbarz got ya. just don't kick them, shut up and listen carefully.
-
Adam Back reposted
Murch
@murchandamus
Many RDTS proponents seem to be confused about the difference between mempool policy and consensus rules. I was hoping that you understood it.
Anyway, please point out where in BIPโฏ110 the existence of a witness for P2A is specified to be consensus invalid. -
Adam Back reposted
Bugle.News ๐ฏ
@bitcoin_bugle
SpaceX To Allow Shareholders To Vote On Rocket Engine Designs Via Their Brokerage Accounts
-
Post not available here, view on X
Adam Back
@adam3us
@mrhodl or @marsspitsbarz got ya. just don't kick them, shut up and listen carefully.
-
Adam Back reposted
Coinjoined Chris โก
@coinjoined
Yeah, I'm mostly commenting for the critical thinkers who are interested in the nuances. I'm pretty sure I've been muted at this point, but there are still plenty of plebs reading along who can be spared the bamboozle before they walk off the cliff.
-
Adam Back
@adam3us
feels like it's already cypherpunk summer๐ 39C in ๐ฒ๐น!
-
Adam Back reposted
Coinjoined Chris โก
@coinjoined
Yup. It had broad support among people who have actively contributed to the project. Everyone else remained free to stop updating, choose a different policy limit, run an alternative implementation like btcd, or switch to a fork such as Knots.
It wasn't done to serve Citrea. Citrea was just another example of why the OP_RETURN limit was counterproductive: it incentivized the use of fake pubkeys, which are a worse outcome for the network. -
Adam Back reposted
Dathon Pwn
@DathonPwn
This is correct.
This is not a "consensus bug" in the same way Block Slop is, but this is a failure to honestly document all of the consensus changes that are included in BIP 110.
FYI to @FoundryServices - BIP 110 has not documented all the consensus changes it makes. -
Adam Back reposted
Stephan Livera
@stephanlivera
Undocumented consensus change in the RDTS implementation?
Murch
@murchandamus
It was pointed out to me today that the February update to the RDTS implementation added a requirement that the witness stack of P2A must be empty.
github.com/dathonohm/bitcoin/releases/tag/v29.3.knots2026โฆ -
Adam Back reposted
Jor ๐ฆ
@88_sats
Well that was a fun week of debates on X
Too many closed minds with the same old talking points
We will see what happens in August
Back to stacking sats and using Bitcoin as money ๐ซก -
Adam Back reposted
Kaz
@orthodoxbitcoin
This is what happens when you vibeslop a BIP. Documentation and implementation differ.
Murch
@murchandamus
It was pointed out to me today that the February update to the RDTS implementation added a requirement that the witness stack of P2A must be empty.
github.com/dathonohm/bitcoin/releases/tag/v29.3.knots2026โฆ -
Adam Back reposted
calle
@callebtc
dathon ohm (chris guida's chat gpt persona) getting mogged by one of the most patient bitcoiners in existence
Murch
@murchandamus
Many RDTS proponents seem to be confused about the difference between mempool policy and consensus rules. I was hoping that you understood it.
Anyway, please point out where in BIPโฏ110 the existence of a witness for P2A is specified to be consensus invalid. -
Adam Back reposted
nunchuk_io
@nunchuk_io
New Nunchuk mobile release.
โ USDT on Liquid, self custodial
โ Trezor now pairs over Bluetooth -
Adam Back reposted
Liquid Network ๐
@Liquid_BTC
Self-custodial USDt on Liquid, now live in @nunchuk_io. Hold dollars on Liquid with your own keys, no custodian in the middle.
H/t to Nunchuk, one of the teams pushing what's possible with Bitcoin tech on mobile.
nunchuk_io
@nunchuk_io
New Nunchuk mobile release.
โ USDT on Liquid, self custodial
โ Trezor now pairs over Bluetooth -
Adam Back reposted
Tone Vays
@ToneVays
What a shitshow #bip110 is continuing to be! Just Hard Fork already! ๐คก
Murch
@murchandamus
It was pointed out to me today that the February update to the RDTS implementation added a requirement that the witness stack of P2A must be empty.
github.com/dathonohm/bitcoin/releases/tag/v29.3.knots2026โฆ -
Adam Back reposted
Samson Mow
@Excellion
BIP110 supporters: You claim Bitcoin is captured by corrupt devs, suitcoiners, spammers, plus "Big Bitcoin," and that only an emergency soft-fork can save it. When BIP110 activates as a minority fork, can you in good conscience keep holding/using BTC after causing so much drama?
-
Adam Back reposted
shaquille o'atmeal
@crypt0e
I'm willing to forgive those who come to the table and admit they were wrong about BIP-110 once this is over, but I will not forget. It's been a very interesting litmus test and social experiment.
-
Adam Back reposted
xpug.HODL
@xpugHODL
Iโve been out of Bitcoin for a while.
Iโm coming back into Bitcoin twitter unbiased.
I can say with absolute certainty you BIP110 guys sound like snake oil salesmen. -
Adam Back reposted
Stephan Livera
@stephanlivera
Try this, it should help explain stephanlivera.github.io/Bitcoin-Spam/
-
Adam Back reposted
Bitcoin Brabant
@BitcoinBrabant
Canโt imagine Braiins being a proponent while having their lightning implementation being in split risk.
-
Adam Back reposted
Coinjoined Chris โก
@coinjoined
Bitcoin is not the longest chain but the longest chain with the most amount of cumulative work.
That's something satoshi also got wrong in 0.1 and was later fixed. -
Adam Back reposted
Tone Vays
@ToneVays
Unlike Knotzis, real Bitcoiners are not dumb enough to follow a Fork with a single Dev in charge! That's what a URSF will be!
-
Adam Back reposted
Yves ๐ฟ
@ZLOK
Retweeting because not only @Saylor should read this:
"We don't need a URSF because BIP110's mandatory signaling already acts as its own activation mechanism" ... or lack thereof.
Kratter is a troll. Don't feed the troll.
Coinjoined Chris โก
@coinjoined
Hey @saylor, the idea that a URSF is somehow required is a rhetorical invention by BIP110 proponents. It shifts the burden from demonstrating broad support to claiming victory by default unless opponents actively fork away. That's not how Bitcoin consensus works.
We don't need a URSF because BIP110's mandatory signaling already acts as its own activation mechanism.
If it ever falls behind (even at 30% hashrate it will), it stays behind unless it overtakes the main chain. You can even experiment with this yourself using @OrangeSurfBTC BIP110 simulator.
And for anyone still worried, there's already a built-in solution: if a lagging BIP110 fork ever appears, you can simply invalidateblock its first block. Your node will never switch to that chain no special software or URSF required. -
Adam Back reposted
Fundamentals ๐ฒ ๐ฅ
@Fundamentals21m
In Bitcoin, consensus is the moral high ground.
I truly wish the BIP110 side would at least acknowledge that they are operating without it. It would make the communication much more effective and please understand that you are speaking to people who expect this axiomatically of you.
I plea that you find some way to signal to us because you have acted like you have consensus from day 1 and all the world can show us is how absurdly unjustified that sense is - this is not the makings of a functional debate.
Show us real hash power, or a futures market, or something that demonstrates real power - or else please understand that the debate is incredibly compromised atop the premise that you have any moral high ground - even if somehow you really do have it in your pocket - in which case stop pretending you want a constructive debate.
We are not the same because one side appears to have overwhelming consensus and the other side rejects the notion that this is important. -
Adam Back reposted
Said Nassar
@the_nassar
Its critics are arguing about it because they pity bitcoiners who were deceived by its makers.
-
Adam Back reposted
โฟutterstein
@stack_toshi
Because you guys keep posting nonsense
-
Adam Back reposted
Richard 'Dick' Greaser 40HPW ๐ฏ ๐ด (Bugle.News)
@GreaserRichard
Bitcoiners can resist arguing with people spreading retarded fud
-
Adam Back reposted
Dathon Pwn
@DathonPwn
He would ignore us if he could. He canโt because this matters.
He would engage if he could. He is scared so he blocks.
He is would tell the truth if he could. He canโt so he lies.
He vibe coded a consensus bug in the BIP 110 client
CC @dathon_ohm @cguida6 @LukeDashjr
Dathon Pwn
@DathonPwn
-
Adam Back reposted
Michael Saylor
@saylor
What's next?
-
Adam Back reposted
Khing Oei
@khingoei
-
Adam Back reposted
Dathon Pwn
@DathonPwn
Once a non 110 block gets mined, the 110 client will cause consensus bugs if you switch chains.
This is a confirmed consensus bug I disclosed yesterday.
Dathon Pwn
@DathonPwn
-
Adam Back reposted
Vortex | BIP448
@theonevortex
No. Category error. Existing rules verify PROPERTY as in signatures proving ownership, they're content blind & apply identically to every byte, BIP110's rules inspect data SHAPE to block certain content from existing. Verifying ownership isn't censorship, blocking expression is.
-
Adam Back reposted
Lyn Alden
@LynAldenContact
Multiple of its leaders and largest supporters have called it existential and say bitcoin dies without it. Today you shared a video with that in the title as well.
-
Adam Back reposted
Dylan LeClair
@DylanLeClair
> BTC doesnโt die
> Divs keep being paid
> Sellers run out of coins
> BTC starts climbing a wall of worry
> Fear quietly flips to disbelief
> Pref credit spreads tighten
> MSTR engine clicks back into gear
> Skeptics remain shrieking into the void
> Bull market -
Adam Back reposted
bizzy hodlz
@byronhambly
Hang it in the Louvre
Dathon Pwn
@DathonPwn
-
Adam Back reposted
ODELL
@ODELLXYZ
slop epidemic
-
Adam Back reposted
Stephan Livera
@stephanlivera
Anyone who gets told "yOu dIdnT rEaD dA bIp" - make sure you read this for examples of motte and bailey tactics by BIP110ers.
Reminder: they AGITATE based on spam, but when pressed they pretend it's not about spam and you didn't read the bip!
Stephan Livera
@stephanlivera
gmax on the lies of the BIP110 crowd who claim it is not about spam, while still agitating based on spam
bitcointalk.org/index.php?topic=5583900.msg66844763 -
Adam Back reposted
Tone Vays
@ToneVays
I find it very frustrating that Luke fully understands how Nodes, Mining, Code & Bitcoin work. Knows Segwit & Bip148 better than anyone!
* But somehow, his Top mouthpieces like Mechanic, Kratter, Knut, etc are spreading massive misinformation & he's laughing into the throne!
Farside Insights
@FarsideInsights
-
Adam Back reposted
_Checkmate ๐ ๐โกโข๏ธ๐ข๏ธ
@_Checkmatey_
Pause for a second, and assume BIP110 was for some other change. Maybe a covenant proposal.
Would you see it as acceptable for such low quality code to be written into production?
Is it acceptable to have a 55% acvtivation threshold, which is far from an overwhelming majority?
Dathon Pwn
@DathonPwn
-
Adam Back reposted
Michael Rozman
@michael_rozman
The sooner one accepts that the failure of BIP110 demonstrates Bitcoin works as designed, the sooner one will understand Bitcoin.
-
Adam Back reposted
ClioBitcoinBank ๐ดโโ ๏ธ
@ClioBitcoinBank
"Why do you all respond so often to correct us and say we're wrong? Is it because we're actually right?"
Fucking No, God No -
Adam Back reposted
Dylan LeClair
@DylanLeClair
FAFO. $BTC
-
Adam Back reposted
Stephan Livera
@stephanlivera
"Bitcoin should remain conservative at the base layer. For me, that means rejecting BIP 110.
Bitcoin does not need guardians of purity.
It needs guardians of neutrality." -
Adam Back reposted
Michael Saylor
@saylor
Many Bitcoiners I respect support BIP 110. I understand and share their desire to protect Bitcoin, but believe the proposed cure is more dangerous than the condition. Here are 110 reasons why Bitcoin needs guardians of neutrality.
-
Adam Back reposted
Walkerโก๏ธ
@WalkerAmerica
PSA to BIP110 folks: here is a thread of Luke Dashjr telling plebs that nodes donโt matter unless they have economic influenceโฆ
โA node is only as relevant as its operator's economic influence.โ -
Adam Back reposted
David Bailey๐ต๐ท $2.0mm/btc is the floor
@DavidFBailey
To all the BIP110 folks, itโs ok that you were wrong. Stick around Bitcoin long enough and youโll be humbled again and again (I think I have a PhD in being humbled at this point). All that matters is that you learn, redirect your energy, and push Bitcoin forward constructively.๐ค
-
Adam Back reposted
Phil Geiger
@phil_geiger
Bitcoin deserves higher quality engineering than this poorly designed, rushed, out of consensus soft fork.
Bitcoin is not a game where we can just throw our hands up and test stuff in prod. It's the world's last and best chance at sound money.
Dathon Pwn
@DathonPwn
-
Adam Back reposted
-
Adam Back reposted
Dathon Pwn
@DathonPwn
Hello @saylor.
I have disclosed a consensus bug in BIP 110 this morning here, this could result in multiple chain splits, and money lost across miners, exchanges, and merchants.
Dathon Pwn
@DathonPwn
-
Adam Back reposted
Coinjoined Chris โก
@coinjoined
Take your time... It's not like there's a forced activation height
-
Adam Back reposted
Dathon Pwn
@DathonPwn
This issue was already addressed properly in SegWit, as detailed in my report.
Why do you believe the safeguards that were included in SegWit are not necessary for BIP 110? -
Adam Back reposted
Wayne Vaughan
@WayneVaughan
This true @LukeDashjr? Does BIP110 introduce a consensus bug?
-
Adam Back reposted
Alexander Leishman ๐บ๐ธ
@Leishman
๐
-
Adam Back reposted
Farside Insights
@FarsideInsights
.@FoundryServices are you seeing this?
-
Adam Back reposted
Farside Insights
@FarsideInsights
How many consensus bugs have been found in BIP-110 since activation software was released?
-
Adam Back reposted
l0rinc
@L0RINC
Welcome to the club:
l0rinc
@L0RINC
# BIP-110 ReducedData: script-execution cache poisoning via activation-boundary reorg
Found a serious consensus bug in Bitcoin Knots' BIP-110 implementation: a shallow reorg across the activation boundary can poison the script validation cache, causing a node to accept a block containing BIP-110 invalid transactions.
Full disclosure with reproducers can be found on the pending PR: github.com/bitcoinknots/bitcoin/pull/238 -
Adam Back reposted
Dathon Pwn
@DathonPwn
-
Adam Back reposted
Yves ๐ฟ
@ZLOK
We will just ignore your frivolous fork. No need for a counter-fork when your "UASF" has zero traction.
There was no URSF for "Bitcoin Gold", "Bitcoin Diamond", etc. -
Adam Back reposted
Liquid Network ๐
@Liquid_BTC
A technical breakdown of Simplicity: how it works, what it trades off, and what you can build on Liquid.
Artem Chystiakov
@Arvolear
-
Adam Back reposted
Bugle.News ๐ฏ
@bitcoin_bugle
๐จ BREAKING: Plebs deploy the "Mother of All Nodes" (MOAN), the largest non-economic node ever built, ahead of the mandatory signaling period.
-
Adam Back reposted
Rod Palmer ๐ฅ
@rodpalmerhodl
plebs are beginning to notice all the glaze @NEEDcreations is getting for being an early defector from bip 110. they're going to want to cash in.
-
Adam Back reposted
Vojtฤch Strnad
@vostrnad
Since the activation period started, there have been 3 new versions of the activation client with changes to consensus rules (coinbase transactions, P2A, cache poisoning bug). That's 4 incompatible client versions running in the wild. And they're still saying it wasn't rushed.
-
Adam Back reposted
Farside Insights
@FarsideInsights
Still not merged
And the activation process started months ago -
Adam Back reposted
Blockstream
@Blockstream
OP_CHECKSHRINCS uses one public key with two ways to spend.
The first path keeps signatures small by having the device track how many times it has signed.
The second path doesn't track anything and is always available as a safety net. If your device is lost or replaced, you restore with your recovery phrase and fall back to that second path.
It's more expensive to spend from, but you are never locked out. This is how SHRINCS works. -
Adam Back reposted
Tone Vays
@ToneVays
The group in Green represents approximately 1% of Bitcoin's Economic value (Node Runners that Receive, Hodl & Transact in BTC) & I'm probably being generous!
- Miners won't lose any sleep over this! Ignoring them is the smartest thing a Rational Economic Actor can do!
TORONTO HODL ๐
@EnjoyingBitcoin
As of July 15th, Miners are either going to serve everyone here, or they're going to lose ~40% of their customers...
Hmmm... I wonder which they will choose... -
Adam Back reposted
Wicked
@w_s_bitcoin
Never forgetโฆeven those who denounce BIP-110 today started off being wrong about Core v30.
Jason Hughes
@wk057
Bitcoin Core developers are about to merge a change that turns Bitcoin into a worthless altcoin, and no one seems to care to do anything about it.
I've voiced objections, lost sleep over this, and despite clear community rejection of the PR it's moving.
github.com/bitcoin/bitcoin/pull/32359 -
Adam Back reposted
Mike Schmidt
@bitschmidty
This thread is pretty representative of the poor discourse about Bitcoin development on X.
โship rad stuffโ, โship valueโ
instagibbs was instrumental in shipping ephemeral anchors, TRUC, package relay, and other work that improved Lightning, to the celebration of Lightning node maintainers, Ark implementors, and users. Then wrote a guide to explain it all: bitcoinops.org/en/bitcoin-core-28-wallet-integration-guide/
instagibbs helped ship Cluster mempool to improve the mempool, fee bumping and other improvements
instagibbs has been working on eltoo/LN-Symmetry, a substantial improvement/overhaul of Lightning for Bitcoin payments
instagibbs is also working on covenants proposals specifically scoped to improve Bitcoin payment use case improvements for layer 2s like Lightning and Ark, as well as vault features. In addition to authoring these proposals, he is also working on tooling and a variety of proof of concepts.
โHold yourself to some level of standards. 8.5B people are counting on *us* to not drop the ball.โ
instagibbs has reviewed and provided many 1000s of comments in the last 11 years to help ensure balls are not dropped. Youโre welcome to look at GitHub for the quality of these reviews.
instagibbsโ work also helped mitigate pinning attacks on the Lightning Network. There are many other examples of hardening Bitcoin software, check the repo or ask your favorite LLM.
Yet you claim he has โcompletely torpedoed quality workโ, and should โbe sent on your wayโ. Because you disagree with the rationale for a default mempool policy setting value change? Send away the guy spending 11 years on Bitcoin and some of the most impactful Bitcoin-as-payments work out there.
Michael, ARE YOU OK? -
Adam Back reposted
Artem Chystiakov
@Arvolear
-
Adam Back reposted
Ron Stoner
@forwardsecrecy
It has been 1,337 days since a well known bitcoin developers server was hacked - and it still has not been entirely audited nor rebuilt to this day.
-
Adam Back reposted
Rob Hamilton
@Rob1Ham
You can use use bottom tier consumer hardware like a 8GB raspberry pi, and sync the entire 17 year financial history of Bitcoin in 35 hours.
Bitcoin really is the best money.
Jameson Lopp
@lopp
Bitcoin Core v32 is going to sync 30% - 40% faster thanks to processing parallelization improvements. ๐ฅณ
-
Adam Back reposted
Dylan LeClair
@DylanLeClair
Bitcoin.
-
Adam Back reposted
Neil Jacobs
@NeilJacobs
So goodโฆBitcoin Twitter is back!
-
Adam Back reposted
DarkClownSuitCoinicarus
@Coinicarus
-
Adam Back reposted
Stephan Livera
@stephanlivera
If spam hits your node but you donโt even notice, did it really stop Bitcoin from working as money?
Ironically, Bitcoin survived multiple spam waves (SatoshiDice, Counterparty, Coloured Coins, VeriBlock, coinwallet.eu, etc.) before tools like mempool.space even existed.
Most users happily transacted and barely knew or cared.
The network is more resilient than the panic suggests. -
Adam Back reposted
Daniel ษrrr
@csuwildcat
While one hundred and ten people were having a tantrum on Twitter about silly monkey NFT spam that's already burning itself out organically, Bitcoin Core sped up sync time by a third doing hard work that actually helps node runners.
Jameson Lopp
@lopp
Bitcoin Core v32 is going to sync 30% - 40% faster thanks to processing parallelization improvements. ๐ฅณ
-
Adam Back reposted
MARS SPITS BARS ๐ฅ
@marsspitsbarz
Imagine booting customers from the chat
raybon ๐ฅ
@ray_bon_
I was one of the larger hashers with Ocean when it launched. I got removed from your telegram group for criticizing the retarded slander of longtime contributors
You guys gotta clean this shit up -
Adam Back reposted
Mike Schmidt
@bitschmidty
Iโm really curious as to what is meant by captured as well. Namely:
Who specifically in Bitcoin Core is captured?
By whom exactly?
By what mechanism?
For what purpose?
Preferably with evidence.
Perhaps that will come out in the 4th/final article. -
Adam Back reposted
Jason Hughes
@wk057
It's all the difference. Segwit spent quite some time... over two years... developing, debating, refining, testing, educating, and finally fully deploying activation-ready clients and reaching ~80% of the nodes by the time BIP148 was even proposed.
BIP110 has, by my own crawler and dedupe estimates, about 6% of unique nodes at best.
It's both attempting a MASF and UASF with a super-minority on both.
That's not comparable to segwit's supermajority of enforcement-ready nodes, and already-near simple-majority hashrate by the time BIP148 was proposed. -
Adam Back reposted
Wicked
@w_s_bitcoin
BIP-110 doesnโt end the cat and mouse game. It rewards it.
Restrict one type of spam and it just makes it more โrareโ while spammers find an easy workaround using techniques that arenโt temporarily blocked.
As retarded as it sounds, they love knowing they baited yโall into attempting a consensus changeโฆespecially one that either doesnโt stop them (e.g. runes) or that theyโve already bypassed. ๐
Youโre not beating them at that game. Youโre volunteering to play it and with no chance of winning. -
Adam Back reposted
Jameson Lopp
@lopp
Bitcoin Core v32 is going to sync 30% - 40% faster thanks to processing parallelization improvements. ๐ฅณ
-
Adam Back reposted
Liquid Network ๐
@Liquid_BTC
See it live: @Resolvr_io demonstrated Apogee end-to-end at the Simplicity Office Hours with @Blockstream engineers. Full recording: youtu.be/siEDPzGRGTc
-
Adam Back reposted
Liquid Network ๐
@Liquid_BTC
Welcoming Apogee to the ecosystem: a new self-custodial Liquid wallet in your browser. Pair it with @BlockstreamJade, or start with a 12-word seed you back up. From @Resolvr_io, one of Bitcoin's most impressive dev teams.
Free and open source with self-custody as the standard.
Resolvr
@Resolvr_io
We made a @Liquid_BTC web wallet extension for Chrome (Firefox coming), apogee.resolvr.io
It's dapp-ready. Web apps can be built to connect to Apogee, read balances, and request transactions โ with every approval signed inside the wallet. Keys never leave the device. That's self-custody from the web page all the way down.
See your balances and execute transactions. Direct support for the @BlockstreamJade hardware wallet โ including signing for dapp requests. Simplicity support on the way.
Free and open source. Repo: github.com/Resolvr-io/apogee
Special thanks to @Blockstream for all the support. -
Adam Back reposted
Jason Hughes
@wk057
*doesn't read the post**walks in*
"Strawman!" "Condescending!" "Hysterical!"
*posts some irrelevant information unrelated to the content*
*walks out*
๐คทโโ๏ธ
I welcome discussion on the merits of anything in my post. If there's anything actually incorrect, I'm happy to post a correction. Simply hand waving it away as if it's nonsense is kind of pointless, and a bit revealing. -
Adam Back
@adam3us
"from now til the end of the year, multiple Core devs will go on @isabelfoxenduke and suggest 4% inflation on Bitcoin."๐คฃ๐คฃ
Nooo. they won't.
110 tagged people don't know policy, from consensus from immutable property. but bitcoiners do๐คฃ๐คฃ -
Adam Back reposted
Farside Insights
@FarsideInsights
Indeed. Bcashers have a lot in common with BIP-110 supporters:
* Both believe in Blockstream conspiracy theories
* Both want to "fire Core"
* Both say "Coretards"
* Both believe we can/should fight spam by relying on miners being "good actors who care", rather than relying on economics and the blocksize limit
* Both release and promote clients trying to change the Bitcoin rules, without consensus
* Both say we are in a rush/crisis, therefore must deploy a fix ASAP
* Both often fail to see a distinction between policy and the consensus rules
* Both have an anti-interlectual appeal against a technical elite
* Both assert the similar phrases "Bitcoin is an electronic cash system" or "Bitcoin is money", to show they are right. With Bcashers liking the word "cash" and BIP-110s liking the word "money"
* Both claim their opponents understand computer science, but not economics or money
Robert Allen
@SatoshiSound
Yet another conspiracy theory is proving to be more or less right.
It turns out the Bcashers were pretty much spot on about Blockstream.
I was sleeping on that one. -
Adam Back reposted
Saj le Great โกโณ๐
@sajlegreat
I fully understand some of your points and your fears, but you need to re-think how Bitcoin dev process is done, it's not because bitcoin core is the the main implementation that it's somewhat sneaky process or problematic fundings, this is the beauty of open source code/FOSS, the rights of merging code from a repo is trivial as a result, because everyone can rebase/fork the repo and create new implementations. The ad hominem/ad personam attacks are also disgusting, no matter the position of the dev inside an open source organization.
Regarding op_return it's a valid choice of relay policy rule, as there is no consensus rule as it stands, op_return was already limited at 1000kb, per maxblocksize consensus rule. op_return limit was already getting bypassed way before Core30, because the value could be rightfully changed, because implementations like Libre Relay got used, as a result it had bad effects on how the network relayed transactions (like compact blocks).
Some implementations could choose different value (like knots), users are also free to modify that value, and the fact that the limit wasn't enforcable (because it was not a consensus limit). One could argue that changing such value would require a consensus change rather than a policy change but it would still require having actual consensus on the matter.
In the end, anyone is free to run whatever code/implementation/versions they want. There is no contradiction here, you could run every version of Core pre 30 and it never would be an issue, you could even run Core30+ and modify op_return value (as long as the parameter is not deprecated), as you see fit.
The consensus is made by all parties users/nodes by their economic weight/miners/exchanges. This is why BIP110 activation is missguided because it's controversial enough to not have "rough" consensus, nor being adopted, it has not enough miner signaling, BIP9 required 95% of blocks being signaled by miners, let alone the ridiculous 55% of BIP110 minimum requirement, and now flag day activation which clearly shows how reckless it is, and will inevitably result in a chain split which will end up in a difficulty reset = a hard fork, which will result in an altcoin.
So in the end, even if it started somewhat from good intentions, this "fight" went way too far, maybe because of bad communication from both sides, maybe from lack of understanding of Bitcoin and FOSS process , and resulted in an autoimmune disease, that will have bad outcome for those who pursue it. -
Adam Back
@adam3us
From the telegrams
-
Adam Back reposted
Alex B ๐พ
@bergealex4
This is the best rant I have ever heard
@marsspitsbarz is the leader we deserve
All the rest of you keyboard node warriors are fake and gay
Terence Michael
@ProofOfMoney
The beauty of Bitcoin is the ability
to run whatever version of the software
you desire.
Regardless, no version changes Bitcoin's fundamental laws.
All of us must agree on those.
But today, @marsspitsbarz revealed
there's an option I had not considered ๐คฃThis media couldn't be displayed. See it on the original post. -
Adam Back reposted
Terence Michael
@ProofOfMoney
The beauty of Bitcoin is the ability
to run whatever version of the software
you desire.
Regardless, no version changes Bitcoin's fundamental laws.
All of us must agree on those.
But today, @marsspitsbarz revealed
there's an option I had not considered ๐คฃThis media couldn't be displayed. See it on the original post. -
Samson Mow
@Excellion
Post not available here, view on X
Adam Back
@adam3us
can't send death threats to your family (happened to one of the devs cyber bullied out by kratter, hodlonaut and army of weaponized plebs), other devs get those from time to time but shrug it off as "nut job observers out there taking tradeoff discussions to a different level".
-
Adam Back reposted
Rod Palmer ๐ฅ
@rodpalmerhodl
no one who must say โmy node matters!โ runs a node that matters
-
Adam Back reposted
l0rinc
@L0RINC
Adam Back
@adam3us
The amount of brainiac cycles dedicated to shaving off even a byte or two from signature encodings and formally proving the correctness with proof verifiers. And then people accuse them being pro some stuffing a friggin 10kB JPEG into the chain. I mean c'mon, be serious!
-
Adam Back reposted
l0rinc
@L0RINC
We already have what you're describing, most of the values in Bitcoin (and Bitcoin Core) are optimized for their monetary use - the actual non-monetary usage is just a side-effect of low general interest. Do you disagree with that?
We could push for lowering certain values in consensus - and many of us wouldn't object to adding limits - you can champion such a change if you feel strongly about it. Most of us don't, since there isn't any urgency or threat associated with it, it's just stupid usage, so I'm not sure what the motivation would be - forks are insanely difficult, so why spend all that energy when we can't even articulate why we're doing them in the first place?!
Why not restrict the number of txs per block to 3000, since obviously blocks with 7000 are full of spam? Or restrict the JPEG magic bytes from txids, just to block a few more invalid (and valid) uses?
These regulations remind me of what Europe is doing currently, adding more and more meaningless constraints - I don't think Bitcoin should go in the same direction. -
Post not available here, view on XPost not available here, view on X
Adam Back
@adam3us
The amount of brainiac cycles dedicated to shaving off even a byte or two from signature encodings and formally proving the correctness with proof verifiers. And then people accuse them being pro some stuffing a friggin 10kB JPEG into the chain. I mean c'mon, be serious!
-
Adam Back reposted
Richard 'Dick' Greaser 40HPW ๐ฏ ๐ด (Bugle.News)
@GreaserRichard
-
Adam Back reposted
JAN3
@JAN3com
Please say it right, guys.
-
Adam Back reposted
Vortex | BIP448
@theonevortex
I'm neither a suit or an influencer and I am against 110.
-
Adam Back reposted
aeon
@aeonBTC
The sooner you accept that relay policy and "defaults" are useless in an economically incentivized system, the sooner you will understand Bitcoin.
-
Adam Back reposted
Richard 'Dick' Greaser 40HPW ๐ฏ ๐ด (Bugle.News)
@GreaserRichard
Remember when @L0laL33tz did that article about Lukeโs fork before all of this started happening
-
Adam Back reposted
calle
@callebtc
they called this crazy in september
The Rage
@theragetech
๐จLEAKED: LUKE DASHJR PLANS HARDFORK TO "SAVE BITCOIN"
Text messages show the Knots maintainer is considering a hardfork to implement a trusted multisig committee that can retrospectively alter the blockchain to remove illicit content.
Full story๐
www.therage.co/leaked-luke-dashjr-bitcoin-hardfork/ -
Adam Back reposted
-
Adam Back reposted
Vortex | BIP448
@theonevortex
> We should support imo the right of anyone to write and maintain Bitcoin compatible software
Right, until they bundle it with a hostile SF and its creator does a 3+ year smear campaign on core developers, at that point it's time to stop supporting it. -
Adam Back reposted
๐ฅชโก OneSirMeow ๐ฌ๐๏ธโ
@OneSirMeow
CISA is an obvious value-add that all Bitcoiners should help progress and propel forward.
Kudos @fjahr and @n1ckler, @real_or_random, @yannickseurin for DahLIAS.
imo it has an equally crucial value to Bitcoin's longevity and onchain efficiency as BIP324 did for P2P security.
Giacomo Zucco (Pear Market Edition)
@giacomozucco
CISA closer to reality (even if consensus building will be hard)!!!๐๐๐
groups.google.com/g/bitcoindev/c/TF5mPfy58RQ?pli=1 -
Adam Back reposted
Rod Palmer ๐ฅ
@rodpalmerhodl
new idea for bip 110 coin name after plebs fork off
-
Adam Back reposted
Rod Palmer ๐ฅ
@rodpalmerhodl
youโre supposed to run to a node to validate your transactions not your ego
-
Adam Back reposted
Tone Vays
@ToneVays
Plebs are also Welcome to log into @zndtoshi's consensus.health Website & have their voice be heard recorded over #bip110! - So far the majority of Plebs are "Against" as well!
-
Adam Back reposted
Coinjoined Chris โก
@coinjoined
Narratives can carry a movement only so far. Eventually reality arrives and someone is left holding the smoking barrel. Don't burn yourself. ๐
-
Adam Back reposted
phyrooo
@phyrooo
Remember when people laughed at Greg Maxwell calling subjective filtering opinions distributed authoritarianism?
Umm, it is.
phyrooo
@phyrooo
๐งต1/ Filters can work iff they collectively form a vertex-cut (or many). Their goal is to partition the gossip flood into multiple components for some messages. It is thus wrong to think of it as a single node (independent) effort, it's a distributed attempt to form a vertex-cut.
-
Adam Back reposted
Liquid Network ๐
@Liquid_BTC
Users wanted privacy. Banks wanted confidentiality. Technologists thought it was cool.
@adam3us explains how Confidential transactions on Liquid satisfied all three.This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Vortex | BIP448
@theonevortex
> "Up to 20% of nodes are already running enforcement software."
No. Knots has been flat at around ~20% for many months and signaling is at around ~1% or less. Running Knots doesn't mean enforcing BIP-110, understand the difference.
> "BIP 110 enforcement nodes begin building their chain exclusively on top of blocks that signal compliance." and "The network's BIP 110 enforcement nodes perceive them as canonical (longest, valid chain)."
Wrong. Nodes validate and relay, they don't build anything. The chain enforcement nodes would follow only has whatever hashrate actually signals behind it, so a first mover with 5% of hashrate produces a chain running at 5% speed with no retarget for months. "Canonical" to a few thousand Knots nodes with no economic weight isn't canonical to anything that matters, and below the 55% threshold the outcome is a minority chain, not a protocol change, which will fork itself off almost immediately.
> "Those blocks don't propagate as cleanly."
Wrong. Non-signaling blocks propagate fine through the 92-98% of nodes that don't enforce, and miner-to-miner block relay happens over dedicated relay networks anyway, so orphan risk from a single-digit slice of listening nodes is negligible.
> "Miners with flexibility start routing hashrate to the pool with the highest probability of their blocks being added to the chain" and "blocks there are guaranteed to be valid everywhere and accepted by 100% of the nodes in the network."
Wrong. Hashers route on payout per hash, not node acceptance. A pool committed to BIP-110 rules forgoes data transaction fees on the majority chain so its payout is lower, and acceptance by an economically empty partition earns zero extra sats. The incentive points away from the signaling pool, not toward it.
> "Current estimates peg transaction fees at around 15% of miner revenue in normal periods." versus "a declining revenue stream that's already heading toward zero anyway. There's nothing to lose by signaling."
Both can't be true. If data fees are meaningful the first mover eats a real cost alone while competitors keep collecting, and if they're zero the coordination premium evaporates along with the stated urgency for the fork itself.
> "if a pool signals first, they capture the coordination premium. They become the obvious, safe pool." and "the pool that moves first wins the coordination game."
Already tested and failed. Barefoot Mining via Ocean produced the first signaling block on March 1, 2026 and no major pool has followed, with no observable hashrate migration toward Ocean. SegWit in 2017 activated because the economic majority backed BIP 148, and here the economic weight is on the other side with Saylor and Back publicly opposed and Core not endorsing. In this signaling period segwit was well above 30% and 110 is around ~1%.
In summary this post pretty much gets everything backwards. Nodes don't build chains, miners do, and hashers chase payout not node approval. A pool that signals first isn't capturing a premium, it's taking a unilateral fee cut for a minority chain with no economic weight. Ocean tried it in March. Nobody followed. Consensus has already spoken, 110 is DOA. -
Adam Back reposted
Mr.Hodl
@MrHodl
.... You didn't reach full retardation but you went half retard with fighting spam with policy.
-
Adam Back reposted
Vortex | BIP448
@theonevortex
Giacomo you must have seen this misconception coming with your constant and vocal support of Knots on twitter?
-
Adam Back reposted
Adrian Morris
@_Adrian
Bitcoin | BIP-110: NO BIP-110 is not "how Bitcoin has always worked".
Adrian Morris
@_Adrian
This is what is so frustrating about the entire BIP-110 conversation, we can't retroactively change what $BTC is or its history. Along those lines, your comment here is both factually and historically inaccurate because you are attempting to lump mempool/node relay policies in with consensus rule changes.
BIP-110 is proposing new consensus rules that limits new transaction outputs to 34 bytes (except OP_RETURN at 83 bytes),ย caps data pushes and adds various restrictions on valid Taproot structures/scripts. These are new restrictions being added to the consensus layer, and they are not how $BTC has "always worked".
Historically, $BTC has handled unwanted or arbitraryย data through node relay policies (which are voluntary and local), fee driven economic incentives and POW. At no time has $BTC used or been made to use consensus level data size restrictions like BIP-110 is proposing.
In fact, as I pointed out in my article and in other posts, Satoshi supported the idea of limited arbitrary data transactions. Just because $BTC has always had some mechanisms to deal with spam does not mean BIP-110 is exactly how $BTC has always worked. This isn't the same thing. -
Adam Back reposted
Coinjoined Chris โก
@coinjoined
Fork Around & Find Out
Adam Simecka
@AdamSimecka
-
Adam Back reposted
Stephan Livera
@stephanlivera
Luke-logic: release and promote a UASF client with mandatory signalling but pretend it's the rest of the network who are causing a split.
colourorange ๐ฅช
@_colourorange
classic luke logic
-
Adam Back reposted
Anthony Towns
@ajtowns
Wow, hashrate might not be hitting new highs but the delusional rhetoric sure is.
-
Adam Back reposted
Mr.Hodl
@MrHodl
Short story:
We know a thing or two because we've seen a thing or two!
Unfortunately I don't think we're getting any valuable airdrops this summer. But the entertainment is priceless. -
Adam Back reposted
Alistair Milne
@alistairmilne
BIP110 has almost certainly failed
(And that's with a 55% threshold which is ludicrously low) -
Adam Back reposted
Daniel ษrrr
@csuwildcat
Imagine a decentralized system billed as censorship/sybil resistant with 360 million people relying on it, but its protocol rules can be forcibly changed if just 0.0014% of them run a different software version. This is what BIP-110ers genuinely believe, many without realizing it
-
Adam Back reposted
Coinjoined Chris โก
@coinjoined
"Trust me Mechanic โ I knew BIP110 would lead to a chainsplit. Now watch me adjust the difficulty and make the Bitaxes go... *pounds his chest* thump thump next block."
BIP110 is a Fugazi. -
Adam Back reposted
Adrian Morris
@_Adrian
One of the ways I think of Bitcoin | BIP-110 boils down to this:
We get spam in our email inboxes every day. I think most would like to avoid it.
But we make the decision on how to mark | filter that spam into trash. This isn't done by a unilateral rule change that decides what to filter, without our input.
One path represents individual choice; the other represents implementing censorship via code.
As @adam3us noted, the Internet (and Bitcoin) are supposed to be ungovernable systems. We canโt (effectively) stop spam via intrusive protocol changes, but thatโs why mechanisms like fees exist. -
Adam Back reposted
wiz
@wiz
yes, there was a bug in The Mempool Open Source Project where we did not get new federation wallet addresses from the elements node correctly. of course we fixed it right away, but since the new addresses were missing from the audit it appeared on liquid.network that the federation wallet had less bitcoin in it than it actually did, for maybe a day or two, after which time we re-ran a full audit just to double check. all of the code is public in our open source git repos, so anyone can verify it without trusting me
-
Adam Back
@adam3us
"the Internet views censorship as damage and routes around it" - John Gilmore (cypherpunks list co-founder)
the Internet, like bitcoin, is ungovernable: you can't build checkpoints, moderate content, cant stop spam via protocols.
that's why hashcash exists: a market solution! -
Adam Back reposted
Jason Svoboda
@jasonsvoboda
By the saints and the whitepaper! Our Benevolent King Dash hath declared it impossible for the chain to rend asunder. Should it fracture, then His Majesty hath uttered untruths most foul.
-
Adam Back reposted
Stephan Livera
@stephanlivera
BIP110 does not have broad social support. It's Luke, Mechanic and their followers who are trying to ram it through.
But they keep lying to bluff up the support they have.
See @zndtoshi's consensus.health for a quick example
Tone Vays
@ToneVays
At least someone is admitting that Segwit had consensus.... But total delusion that 80% of the network wants Bip110 rules ... @zndtoshi literally built a website that anyone with relevance can signal!
consensus.health -
Adam Back reposted
Stephan Livera
@stephanlivera
The wheels are falling off the BIP110 clown car. Ocean mining pool and Luke Dashjr (CTO and Chairman of Ocean) are making contradictory statements.
Ocean the pool is going to support chain splits, but according to Luke, "BIP110 does not cause a chain split".
lifofifo โ
@lifofifo
Your CTO @LukeDashjr has said 100 times that BIP 110 cannot cause a chain split.
"FUD from the anti-RDTS crowd"
WTF IS IT?
WHAT CHANGED? -
Adam Back reposted
-
Adam Back reposted
โฟryan
@itme_brain
-
Adam Back reposted
lifofifo โ
@lifofifo
Your CTO @LukeDashjr has said 100 times that BIP 110 cannot cause a chain split.
"FUD from the anti-RDTS crowd"
WTF IS IT?
WHAT CHANGED? -
Adam Back reposted
PUBLORD
@publord
"There is no chain split, not in August, nor later." -- Anonymous Ocean Mining CTO
-
Adam Back reposted
Michael Sullivan
@SullyMichaelvan
Link to the full analysis of what the language data says about Bitcoinโs most divisive debate:
sentimentsully.substack.com/p/breaking-down-bip-110 -
Adam Back
@adam3us
here's a test for change ideas for bitcoin to *prevent* something: if you made the analogous change to TCP/IP to achieve what you're asking for on bitcoin, would it work?
try it out: could you stop spam by modifying TCP/IP?
that's a useful test as bitcoin is also ungovernable. -
Adam Back reposted
BTC Prague
@BTCPrague
Hal Finney sized Bitcoin's addressable market at $200 trillion on
day one of the network.
Adam Back @adam3us, Yves Choueifaty (TOBAM) @YChoueifaty, Oleg Mikhalsky @olegmikh1 ( @FulgurVentures), and Xapo Bank @xapobankapp on why the largest pools of capital in
the world have barely started moving.
Live from BTC Prague ๐ -
Adam Back reposted
BTC Prague
@BTCPrague
Watch full video:
www.youtube.com/watch?v=axo4t7fImMk -
Adam Back reposted
Phong Le
@phongle
Introducing the Bitcoin Bank Adoption Index. Adoption of Bitcoin and the related digital asset ecosystem across major banks and financial institutions is accelerating, but still early at 32%.
Methodology and updates to follow. Institutions with questions, corrections, or additional public information: ir@strategy.com. -
Adam Back reposted
pepe โก๐งก bitcoin maxi-idealist
@pepe_btc
I just love this ๐๐๐๐
the only better one Iโd Samson and Tom Lee -
Adam Back reposted
Derek Ross
@derekmross
BIP-110 supporters aren't bad people. They're our friends. They're incredibly passionate Bitcoiners that realize Bitcoin is money and hate spam. Unfortunately, their passion for Bitcoin as money and their hatred for spam has clouded their judgement and made them forget what makes Bitcoin beautiful.
-
Adam Back reposted
Rob Hamilton
@Rob1Ham
Do you still have your Bitcoin Cash airdrop?
-
Adam Back reposted
Vikingo
@Vikingobitcoin9
-
Adam Back reposted
Wicked
@w_s_bitcoin
Hey @elpapoโฆwhatever you do, donโt back out now. Only question is who do you guys wanna use as an arbiter?
-
Adam Back reposted
Coinjoined Chris โก
@coinjoined
Please don't lump in Crazy Uncle Paul with Luke. Luke is several magnitudes crazier.
-
Adam Back reposted
Chun
@satofishi
Forcing a fork with no consensus is not what a fellow Bitcoin developer should do.
Kristian Csepcsar
@KristianCsep
๐จ JUST IN: this image was mined into block 938576 without OP_RETURN, showing Knots filtering does not prevent it.
The transaction was included via MARA Slipstream.
It was created by bitcoin developer Martin Habovstiak, who published a detailed research paper explaining exactly what he did and how anyone can verify it.
RESEARCH TLDR ๐
His goal was to test if stricter filtering rules can actually stop arbitrary data from being embedded on-chain.
Full research: KnotsLies(dot)com ๐below
WHAT THIS TRANSACTION SHOWS:
โข The image is stored contiguously inside a single transaction
โข No OP_RETURN was used
โข No Taproot was used
โข Consensus rules were followed
โข The transaction can be independently verified by anyone running a node
His core argument:
โข Limiting OP_RETURN does not stop arbitrary data storage
โข Policy filters shift the data rather than remove the capability
โข If one encoding path is restricted, another can be engineered
โข Workarounds are practical, not theoretical
SPAM OR WHACK-A-MOLE?
Iโm not a technical expert.
But the more I read about all this, the more it feels like a whack-a-mole game.
You close one door, someone finds another.
I donโt like spam. I donโt like images embedded on-chain.
But it doesnโt seem like thereโs an effective way to fully stop it.
What are your thoughts?
-
Full research: KnotsLies(dot)com ๐below -
Adam Back reposted
Bitcoin Carl ๐๐๐๐
@BitcoinCarl_
Guys even Chun, who I think has been most gracious to Luke over the years, told him forking without consensus is no bueno.
Read the writing on the wall. It is time to move on.
Chun
@satofishi
Forcing a fork with no consensus is not what a fellow Bitcoin developer should do.
Kristian Csepcsar
@KristianCsep
๐จ JUST IN: this image was mined into block 938576 without OP_RETURN, showing Knots filtering does not prevent it.
The transaction was included via MARA Slipstream.
It was created by bitcoin developer Martin Habovstiak, who published a detailed research paper explaining exactly what he did and how anyone can verify it.
RESEARCH TLDR ๐
His goal was to test if stricter filtering rules can actually stop arbitrary data from being embedded on-chain.
Full research: KnotsLies(dot)com ๐below
WHAT THIS TRANSACTION SHOWS:
โข The image is stored contiguously inside a single transaction
โข No OP_RETURN was used
โข No Taproot was used
โข Consensus rules were followed
โข The transaction can be independently verified by anyone running a node
His core argument:
โข Limiting OP_RETURN does not stop arbitrary data storage
โข Policy filters shift the data rather than remove the capability
โข If one encoding path is restricted, another can be engineered
โข Workarounds are practical, not theoretical
SPAM OR WHACK-A-MOLE?
Iโm not a technical expert.
But the more I read about all this, the more it feels like a whack-a-mole game.
You close one door, someone finds another.
I donโt like spam. I donโt like images embedded on-chain.
But it doesnโt seem like thereโs an effective way to fully stop it.
What are your thoughts?
-
Full research: KnotsLies(dot)com ๐below -
Adam Back reposted
Rob Hamilton
@Rob1Ham
Itโs important to have a futures market with any contentious fork in Bitcoin.
Why?
Because the party forking gets what is called the โfree call optionโ.
They can tweet, do long monologue videos about how their fork will win, and how no one will oppose them. They can use company resources to legally pressure miners, post populist rhetoric disassociated from reality (pฤพฤb ลฤพลp) and thenโฆ wait.
The activation comes, and they are delta neutral on a fork.
Ifโฆ
No fork happens - they have their bitcoin.
The fork is successful - they have their bitcoin.
A chain split happens - they get Bitcoin on each side of the fork
See the problem? There is an opportunity cost of time and resources coordinating the fork (maybe reputation too), but thatโs it! They can antagonize the network at no cost of bitcoin.
Itโs worse than that though, everyone who told them they were wrong canโt even dump their hostile fork if they fail to even launch it.
The actual party who has to put up material cost in a fork are the miners. Since they cannot mine on both chains at once, they must choose where to secure coins. The only publicly stated mining pool position on this fork is f2 pool opposing it (~12% of hash rate).
My proposed on chain futures market requires no ecosystem coordination. The Bitcoin is settled automatically, and in the event there is a chain split, each side gets 2 BTC (each party gets the bitcoin they think will โwinโ).
A futures market forces actors among the Bitcoin network with different opinions to put skin in the game, price the risk, and act. It presents an opportunity to lock up Bitcoin for a time, and profit as a rational actor if they have conviction in their position.
The market will do this independent of your wishes otherwise. Via prediction markets, on chain, or exchange future markets (any exchange could get fees for swapping the fork to buy more bitcoin). We saw futures markets with the last contentious fork in 2017 when bitfinex listed futures.
If no market forms at all, it shows there are not two sides to the market, Iโm here as one side of the market, so we know the side that is a no show.
This kind of weakness is death for a fork. If the side forking is unwilling to burn the ships, and put their bitcoin at risk, they are of low conviction and the fork will fail.
There will be a myriad of reasons as to why people who are so vocal and certain that BIP 444 will activate, wonโt bet. To be clear, itโs cope.
Their optimal positioning as it relates to the opportunity to wager is:
1. Ignore
2. Public consider the bet, but to never commit.
3. Hand wave any reason to say the market is either immoral, illegitimate, impractical etc.
Any of these maintains the illusion of strength when they are actually weak. A requirement in fork psychology is to appear as if itโs a certainty, because forking is a game of chicken with the network.
A 1:1 ratio implies a 50% chance likelihood to succeed, far lower than theyโd have you believe success is.
Additionally, to counter offer with a differnt ratio/odds gives up the game. They blink, show their hand and signal that they think 50% is way to high of a likelihood, and all the bluster comes tumbling down.
Iโve given feedback on the GitHub already from a technical perspective my objections to the BIP, they went largely unaddressed before the GitHub was locked.
Notice who will continue engaging in this content without taking the bet, they are seeking attention because they must consume the discourse as their shred of a hope to win.
Surely, there is already rumbling of restricting how 444 works, already a weakening of their position.
People will say I am wrong, but wonโt take the wager.
Makes you think right?
Iโll give 10% of my potential winnings from the contract if you refer a BIP444 proponent into actually making the bet with me.
So whenever you see someone talking about the certainty of this fork activating, link them to this post so we can both make some bitcoin! -
Adam Back reposted
Vortex | BIP448
@theonevortex
Sorry but it's too late. Consensus has spoken and cypherpunk summer is nearly over. You only get to cry wolf once with a SF before you're eschewed as a bad actor.
-
Adam Back reposted
Vortex | BIP448
@theonevortex
Since I can't respond to @1914ad because I'm blocked I'll respond to his tweet here, happy to answer any questions on why 110 has a huge amount of technical issues and confuses virtue signaling for technical consensus:
> They've made it clear what that future is by waging war against nodes, the immune system of Bitcoin.
Nobody waged any war at all, it was a simple relay policy change that any node can configure themselves, most people ignore crazy 110 people like yourself. There was some spam and then due to most of the market leaving spammers behind and the transaction fee most of them left, it's why the fees have been cheap for years.
> Core v.30 uncapped OP_RETURN and after a BIP-110 failure nothing stops the removal of every remaining limit until nobody runs a node but Wall Street and government institutions.
The relay default changed, consensus didn't. OP_RETURN outputs were always valid at the consensus layer and datacarriersize was always a local policy knob, maybe check out Stephan's great website here for a clear and detailed explanation: stephanlivera.github.io/Bitcoin-Spam/
And nobody is talking about removing any other limits, the block weight limit hasn't changed since SegWit, the chain is still growing at the speed it was intended, fees are cheap. Do something to provide more monetary activity on bitcoin to drive out the spam use cases.
> Bitcoin was our one shot and if BIP-110 fails, we let it be captured by fiat trash.
Literally nobody has captured bitcoin, and what even is "fiat trash", do you think a few spammers actually "captured" bitcoin because they paid fees for some transactions?
> Make no mistake, the best individuals Bitcoin ever attracted, the sound money Austrian maximalists who understood it first, will quit forever, and people like that do not come back.
Why would they? Nothing about bitcoin has changed. It's 110 that wants to add a completely new contentious consensus rule that the network is clearly rejecting.
> I remain optimistic because the incentives all point one direction. Signaling BIP-110 costs miners nothing, while mining against it costs them the block reward from every enforcing node.
If signaling costs nothing and the incentives all point one way, why is signaling under 1%? Miners are telling you what they think with their coinbases. The "costs them the block reward" part only works if enforcing nodes are the economic majority, and the data says the opposite. Knots is around 20% of listening nodes at best. A minority enforcing set imposes no cost on anyone, it just forks itself off. -
Adam Back reposted
Tone Vays
@ToneVays
You should consider checking out this video on 2x, in it Mechanic describes how one of the biggest drivers of success of the Fork is Trading and Futures Markets. It's sad what happened to him:
Tone Vays
@ToneVays
5yrs ago @GrassFedBitcoin started his YouTube channel! Not long after I was asked to watch his 1st video which I did & commented that I agreed w/ his recollection of Blocksize Wars! This week went back & time stamped those parts!
๐"Segwit had Consensus"
youtu.be/Lf5rqg61aYU?t=2310 -
Adam Back reposted
Tone Vays
@ToneVays
And it would instantly prove what a centralized movement it is! If one guy can just update a piece of code and everyone follows! What's Next? A PoW change to PoS?
-
Adam Back reposted
Coinjoined Chris โก
@coinjoined
Jim Andrews #B2B
@JimAndrews77
This post is unavailable. See it on X. -
Adam Back reposted
Rod Palmer ๐ฅ
@rodpalmerhodl
bip 444 is a king solomonโs judgement scenario. the side willing to split the chain is the losing side.
-
Adam Back reposted
Coinjoined Chris โก
@coinjoined
"bip110 stops csam"
Rob Hamilton
@Rob1Ham
โPast a certain block height, obsessing over your BIP can be a bad thing.โ
-
Adam Back reposted
Vikingo
@Vikingobitcoin9
Great read. On target.
Adam Back
@adam3us
On the filter fork topic.
I don't usually have time, but this morning listened to one of the twitter spaces from earlier in the week, with some well meaning relative bitcoin newcomers, that humanized them, and their concerns and thoughts for why they thought that made it logical to support 110.
My feeling after listening, is if these are the people with #110 in their handles, I'm sad to see them about to fork off and get disillusioned without understanding why bitcoin rejected 110 robustly.
So here's a more empathetic, constructive higher level version of explaining why not. I hope it's high-level and first-principles enough that everyone can follow.
They seem to want to understand what makes people tick, and are suspicious of intent. So, if someone asked me why is Bitcoin important and what is it, I'd say my (personal) mission and hope for bitcoin is to build the cypherpunk future, that "Snow Crash" was a blueprint, and work backwards from there. Bitcoin I hope leads to fully free markets via bearer unseizable, hard mathematically dependable money. Not everyone is comfortable with that level of freedom, but that's my view. And at this point, I believe that surprisingly, even now many governments have come to understand and value bitcoin's gold-like mathematical assurance, a positive development. Others may have milder views than myself, but still like hard censorship resistant money.
Because of motive suspicion, if it's not obvious: I hate spam with a passion, that's how I came to design hashcash while researching decentralized bearer money with others, and running nodes in privacy related cypherpunk p2p networks nearly three decades ago.
People seem upset about the default op return policy change in bitcoin. I will just assert, there are extremely robust and simple reasons for bitcoin changing default relay policy, and most just didn't do their research, so don't know what those are, or maybe not technical enough to fully understand though there have been 1000s of posts trying to explain in various simplified ways. So that lack of understanding lends itself to shared build-up of false narratives. So here's my back-to-basics higher level explanation.
The decentralization needed to create cypherpunk money has implications a: side effect of decentralization is that you can't impose your views on others. The very decentralization mechanism that helps that, is working against what BIP 110 wants, which at it's most basic is a quest to police other people. I understand supporters don't see their intent like that, but introspect deeper.
You can modify your software, but not anyone else's. Another critical and incredibly robust technical bitcoin immune system is bitcoin can't have people who don't understand technology basics insist on eroding security, decentralization robustness and core properties. That would end badly, fast, and so people will fight you on that.
So the message is Bitcoin respectfully says "no" to what you want. Sorry, and bitcoiners do genuinely understand and empathize that you mean well, have high level thoughts that make emotional sense, and articulate sensible bitcoin-defensive high level ideas, but they are not grounded and without you seeing it, the way you propose to achieve your ideas, hard-conflict with free cypherpunk permissionless money.
My advice is to listen to more experienced people who understand the system and why it works the way it does, to whatever detail you want to understand the grounded reasons for why this is the implication of decentralization and cypherpunk money.
I guarantee you the developer and protocol ecosystem shares and exceeds your views on bearer hard money (and dislike of spam). You may not agree with individual developers choices, views, way of expressing themselves etc, BUT you also need to understand the IETF-like decentralized technical consensus process creates a protective change resistance, that is highly effective at protecting bitcoin mission. The implication of which is no developer can change anything without technical consensus from hundreds of other developers and protocol observers who are pedantic and extremely knowledgeable clever people who won't let any unaddressed technical question past. The protective change resistance is robust and decentralized in an amplifying way because of this technical consensus.
And the many highly technical mainline developers' cypherpunk mission mindsets are probably far more determined than you can even handle on clarity of understanding and views about freedoms on permissionless networks, as many of you are probably still subconsciously inured by the matrix, where they have transcended that, and grew up immersed in it decades ago. They think natively in this space, while you are just grappling with the surface. Many wont have internalized or have the experience to know how this internet physics works, where there is no policeman, no policy authority, just mathematics, free market and hard money. That has implications for your views also, unfortunately.
Now the tough pill, which is unfortunately true: If you won't listen to reason, educate yourself, learn, the same radical freedom applies to you: your permissionless recourse is to club together and create a fork. But bitcoin won't be joining it. (With respect and no sleight intended.)
Please rejoin bitcoin now, or later if you're not convinced and need to experience 110 forking off and fizzling for yourself to start that journey of introspecting and learning. It would be sad if bitcoin lost people disillusioned due to simple lack of understanding of what's going on there, we're all trying to defend bitcoin and keep it on mission. Including btw the 110 technical promoters, just they wandered off plot somehow.
Join the cypherpunks on bitcoin, come cypherpunk summer๐ in a few weeks. -
Adam Back reposted
Stephan Livera
@stephanlivera
Relevant blog post
bitcoincore.org/en/2025/06/06/relay-statement/ -
Adam Back reposted
Danny Scott โก
@CoinCornerDanny
CoinCorner have had 1 customer I'm aware of ask about it.
It is a nothing burger. -
Adam Back reposted
Bitcoin Dudebro 3.125 โก๏ธ๐ฌ๐ง
@bitcoindudebro
We could do better with education on how Bitcoin works. Fewer podcasts and more explainer videos.
-
Adam Back reposted
Samson Mow
@Excellion
Lately there's been a lot of discussion around L2s like Liquid, Ark, and Spark, and the deciding factor for preference seems to have become unilateral exit: the ability to exit to the mainchain on your own initiative, even if the operator is malicious, censoring you, or has vanished entirely.
Ironically, as people are discovering, only one Spark wallet actually supports unilateral exit (the others say it's coming later), which is a bit comical, because that's often the very reason the more hardcore Bitcoiners dismiss Liquid.
At @JAN3com, we're building on @Liquid_BTC because I firmly believe it offers the best set of tradeoffs. After Liquid, my next choice would be Ark, and personally I would avoid Spark because of how centralized it is.
It's all about the substrate. We're all trying to solve for the best L2 substrate, which can also include ecash mints or even databases (like the original WoS). Here's what I believe are the key criteria, in priority order.
1๏ธโฃ Privacy. Both operator-side (are they logging you?) and on-chain (are amounts/assets confidential?)
2๏ธโฃ Operator model. Single operator or federation? Can they steal funds, and can they censor you?
3๏ธโฃ Liquidity. How deep and accessible is it?
4๏ธโฃ Time in production. How long has it been live, and has it held up under real-world conditions?
5๏ธโฃ Data availability. Can you get the data to prove what you own, without relying on the operator?
6๏ธโฃ Economically viable exit. Is that exit actually affordable, or does fee/congestion cost make it theoretical?
7๏ธโฃ Unilateral exit. Can you exit to the mainchain on your own initiative, even if the operator is malicious, censoring you, or gone?
8๏ธโฃ Liveness requirements. Do you have to come online periodically or risk losing funds? (relevant for Ark)
How does Liquid stack up for these criteria?
Really well.
1๏ธโฃ Privacy. Confidential Transactions by default hide both the transaction amount and the asset type from all observers, including functionaries. Functionaries can't see amounts or asset types, so there's nothing to even log if they wanted to.
2๏ธโฃ Operator model. 15 functionaries, 11-of-15 multisig, HSM-secured, tolerating up to 4 offline. Functionary code is open-source.
3๏ธโฃ Liquidity. $5B TVL, including $4B+ in tokenized securities and ~$97M native USDT.
4๏ธโฃ Time in production. Live since October 2018 as Bitcoin's first production sidechain (~7.5 years).
5๏ธโฃ Data availability. Anyone can run a full node and trustlessly self-validate the chain, with L-BTC always verifiably 1:1 with BTC locked on mainchain.
6๏ธโฃ Economically viable exit. 0.1 sat/vB average fee. For most users the primary exit is an atomic swap of L-BTC for BTC, which is permissionless and doesn't require federation membership.
7๏ธโฃ Unilateral exit. Not there for regular users yet, but coming via a BitVM-style 1-of-n bridge on the roadmap. And as a business, you can join as a federation member today and peg out directly, no third party needed.
8๏ธโฃ Liveness requirements. No online-or-lose mechanic; L-BTC sits indefinitely.
Notice that economically viable exit sits above unilateral exit on my list. That's deliberate. Let's dig in.
It's important to remember that L2 substrates are exactly that: substrates. None of them can compete with the trustless, permissionless properties of the Bitcoin mainchain. Anything you're holding long-term belongs on mainchain, in your own custody.
You're using the substrate for spending (small amounts) or cost-effective UTXO aggregation, so unilateral exit isn't that important outside of an ideological insistence on having it. What you actually want is privacy, durability, liquidity, and economically viable exits.
Remember how many Muun wallet users were caught off guard when mainchain fees spiked? When fees climb again, what you thought was a unilateral exit turns out to be no exit at all.
Once network fees hit around 5-10 Sats/vB (or higher), unilaterally exiting small Ark VTXOs or Spark leaves stops being worth it. Let's take an example of 10 small balances adding up to 100k sats. At those fee levels, pulling each one out on-chain can eat 40โ100% (or more) of what it's worth. You'd burn most or all of the value just to move it. At that point, it's effectively dust.
This is because of the tree/branch/leaf structure of Ark and Spark. 5-10 Sats/vB isn't even expensive for a normal BTC transaction: at $100k, that's just $0.71 to $1.41. The cost blows up only because a unilateral exit means unrolling that structure on-chain, not broadcasting one clean transaction.
Ark and Spark are really optimized for cooperative exits and if you're expecting cooperation anyway, then rationally you should expect that same cooperation for a Liquid peg-out. So with Liquid you get both: a cooperative exit via peg-out, and the primary atomic-swap model into a pool that's (pun intended) deep and liquid.
@Liquid_BTC is perfect for the average person and that's why we're building @AquaBitcoin on it.
TL;DR: Unilateral exit is oversold, especially when it's too expensive to actually use. For everyday spending amounts, exiting small Ark/Spark balances becomes uneconomical the moment fees rise, so it's an exit on paper only. Privacy, liquidity, durability, and a cheap real-world exit matter more, and Liquid wins on those. Hold long-term on mainchain; use the substrate for spending/aggregation.
Matthew Vuk ๐ณ๏ธ
@matthewvuk2
Taking a closer look at the Spark Federation, and the closed source "Sparkcore" SSP.
This is what you are exposing your users to when you integrate Spark.
When you do lightning send/receive it is flowing through that "Sparkcore" they do not name in the website docs. -
Adam Back reposted
George Saoulidis
@georgecursor
I'm absolutely convinced that any rushed anti spam soft fork or anything similar is a psyop.
They want to damage bitcoin.
Will not run it. My node my rules.
Adam Back
@adam3us
because some of us feel sorry for the users who have been misled. read the longer post x.com/adam3us/status/2075884851794735602 we actively do NOT want bitcoiners to fork off because of confusion.
Adam Back
@adam3us
On the filter fork topic.
I don't usually have time, but this morning listened to one of the twitter spaces from earlier in the week, with some well meaning relative bitcoin newcomers, that humanized them, and their concerns and thoughts for why they thought that made it logical to support 110.
My feeling after listening, is if these are the people with #110 in their handles, I'm sad to see them about to fork off and get disillusioned without understanding why bitcoin rejected 110 robustly.
So here's a more empathetic, constructive higher level version of explaining why not. I hope it's high-level and first-principles enough that everyone can follow.
They seem to want to understand what makes people tick, and are suspicious of intent. So, if someone asked me why is Bitcoin important and what is it, I'd say my (personal) mission and hope for bitcoin is to build the cypherpunk future, that "Snow Crash" was a blueprint, and work backwards from there. Bitcoin I hope leads to fully free markets via bearer unseizable, hard mathematically dependable money. Not everyone is comfortable with that level of freedom, but that's my view. And at this point, I believe that surprisingly, even now many governments have come to understand and value bitcoin's gold-like mathematical assurance, a positive development. Others may have milder views than myself, but still like hard censorship resistant money.
Because of motive suspicion, if it's not obvious: I hate spam with a passion, that's how I came to design hashcash while researching decentralized bearer money with others, and running nodes in privacy related cypherpunk p2p networks nearly three decades ago.
People seem upset about the default op return policy change in bitcoin. I will just assert, there are extremely robust and simple reasons for bitcoin changing default relay policy, and most just didn't do their research, so don't know what those are, or maybe not technical enough to fully understand though there have been 1000s of posts trying to explain in various simplified ways. So that lack of understanding lends itself to shared build-up of false narratives. So here's my back-to-basics higher level explanation.
The decentralization needed to create cypherpunk money has implications a: side effect of decentralization is that you can't impose your views on others. The very decentralization mechanism that helps that, is working against what BIP 110 wants, which at it's most basic is a quest to police other people. I understand supporters don't see their intent like that, but introspect deeper.
You can modify your software, but not anyone else's. Another critical and incredibly robust technical bitcoin immune system is bitcoin can't have people who don't understand technology basics insist on eroding security, decentralization robustness and core properties. That would end badly, fast, and so people will fight you on that.
So the message is Bitcoin respectfully says "no" to what you want. Sorry, and bitcoiners do genuinely understand and empathize that you mean well, have high level thoughts that make emotional sense, and articulate sensible bitcoin-defensive high level ideas, but they are not grounded and without you seeing it, the way you propose to achieve your ideas, hard-conflict with free cypherpunk permissionless money.
My advice is to listen to more experienced people who understand the system and why it works the way it does, to whatever detail you want to understand the grounded reasons for why this is the implication of decentralization and cypherpunk money.
I guarantee you the developer and protocol ecosystem shares and exceeds your views on bearer hard money (and dislike of spam). You may not agree with individual developers choices, views, way of expressing themselves etc, BUT you also need to understand the IETF-like decentralized technical consensus process creates a protective change resistance, that is highly effective at protecting bitcoin mission. The implication of which is no developer can change anything without technical consensus from hundreds of other developers and protocol observers who are pedantic and extremely knowledgeable clever people who won't let any unaddressed technical question past. The protective change resistance is robust and decentralized in an amplifying way because of this technical consensus.
And the many highly technical mainline developers' cypherpunk mission mindsets are probably far more determined than you can even handle on clarity of understanding and views about freedoms on permissionless networks, as many of you are probably still subconsciously inured by the matrix, where they have transcended that, and grew up immersed in it decades ago. They think natively in this space, while you are just grappling with the surface. Many wont have internalized or have the experience to know how this internet physics works, where there is no policeman, no policy authority, just mathematics, free market and hard money. That has implications for your views also, unfortunately.
Now the tough pill, which is unfortunately true: If you won't listen to reason, educate yourself, learn, the same radical freedom applies to you: your permissionless recourse is to club together and create a fork. But bitcoin won't be joining it. (With respect and no sleight intended.)
Please rejoin bitcoin now, or later if you're not convinced and need to experience 110 forking off and fizzling for yourself to start that journey of introspecting and learning. It would be sad if bitcoin lost people disillusioned due to simple lack of understanding of what's going on there, we're all trying to defend bitcoin and keep it on mission. Including btw the 110 technical promoters, just they wandered off plot somehow.
Join the cypherpunks on bitcoin, come cypherpunk summer๐ in a few weeks. -
Adam Back reposted
Coinjoined Chris โก
@coinjoined
@mattkratter why wouldn't you take this trade? 5:1 are amazing odds
-
Adam Back reposted
Stephan Livera
@stephanlivera
Core Devs: Bitcoin is not endorsing or condoning non-financial data
Knots/110ers: "Bitcoin is becoming file storage! We need to change consensus rules"
They're inventing a strawman and then bashing Core for not wanting to play a pointless whack-a-mole game. -
Keysa
@SimplestBTCBook
Ponder this: If BIP110 was a nothing burger, why are Back, Saylor AND Bailey wasting so much time on Twitter fighting it?
What are they so scared of?
A temporary soft fork designed to provide a breather for bitcoiners to consider better spam mitigation, what is so terrifying?
Adam Back
@adam3us
because some of us feel sorry for the users who have been misled. read the longer post x.com/adam3us/status/2075884851794735602 we actively do NOT want bitcoiners to fork off because of confusion.
Adam Back
@adam3us
On the filter fork topic.
I don't usually have time, but this morning listened to one of the twitter spaces from earlier in the week, with some well meaning relative bitcoin newcomers, that humanized them, and their concerns and thoughts for why they thought that made it logical to support 110.
My feeling after listening, is if these are the people with #110 in their handles, I'm sad to see them about to fork off and get disillusioned without understanding why bitcoin rejected 110 robustly.
So here's a more empathetic, constructive higher level version of explaining why not. I hope it's high-level and first-principles enough that everyone can follow.
They seem to want to understand what makes people tick, and are suspicious of intent. So, if someone asked me why is Bitcoin important and what is it, I'd say my (personal) mission and hope for bitcoin is to build the cypherpunk future, that "Snow Crash" was a blueprint, and work backwards from there. Bitcoin I hope leads to fully free markets via bearer unseizable, hard mathematically dependable money. Not everyone is comfortable with that level of freedom, but that's my view. And at this point, I believe that surprisingly, even now many governments have come to understand and value bitcoin's gold-like mathematical assurance, a positive development. Others may have milder views than myself, but still like hard censorship resistant money.
Because of motive suspicion, if it's not obvious: I hate spam with a passion, that's how I came to design hashcash while researching decentralized bearer money with others, and running nodes in privacy related cypherpunk p2p networks nearly three decades ago.
People seem upset about the default op return policy change in bitcoin. I will just assert, there are extremely robust and simple reasons for bitcoin changing default relay policy, and most just didn't do their research, so don't know what those are, or maybe not technical enough to fully understand though there have been 1000s of posts trying to explain in various simplified ways. So that lack of understanding lends itself to shared build-up of false narratives. So here's my back-to-basics higher level explanation.
The decentralization needed to create cypherpunk money has implications a: side effect of decentralization is that you can't impose your views on others. The very decentralization mechanism that helps that, is working against what BIP 110 wants, which at it's most basic is a quest to police other people. I understand supporters don't see their intent like that, but introspect deeper.
You can modify your software, but not anyone else's. Another critical and incredibly robust technical bitcoin immune system is bitcoin can't have people who don't understand technology basics insist on eroding security, decentralization robustness and core properties. That would end badly, fast, and so people will fight you on that.
So the message is Bitcoin respectfully says "no" to what you want. Sorry, and bitcoiners do genuinely understand and empathize that you mean well, have high level thoughts that make emotional sense, and articulate sensible bitcoin-defensive high level ideas, but they are not grounded and without you seeing it, the way you propose to achieve your ideas, hard-conflict with free cypherpunk permissionless money.
My advice is to listen to more experienced people who understand the system and why it works the way it does, to whatever detail you want to understand the grounded reasons for why this is the implication of decentralization and cypherpunk money.
I guarantee you the developer and protocol ecosystem shares and exceeds your views on bearer hard money (and dislike of spam). You may not agree with individual developers choices, views, way of expressing themselves etc, BUT you also need to understand the IETF-like decentralized technical consensus process creates a protective change resistance, that is highly effective at protecting bitcoin mission. The implication of which is no developer can change anything without technical consensus from hundreds of other developers and protocol observers who are pedantic and extremely knowledgeable clever people who won't let any unaddressed technical question past. The protective change resistance is robust and decentralized in an amplifying way because of this technical consensus.
And the many highly technical mainline developers' cypherpunk mission mindsets are probably far more determined than you can even handle on clarity of understanding and views about freedoms on permissionless networks, as many of you are probably still subconsciously inured by the matrix, where they have transcended that, and grew up immersed in it decades ago. They think natively in this space, while you are just grappling with the surface. Many wont have internalized or have the experience to know how this internet physics works, where there is no policeman, no policy authority, just mathematics, free market and hard money. That has implications for your views also, unfortunately.
Now the tough pill, which is unfortunately true: If you won't listen to reason, educate yourself, learn, the same radical freedom applies to you: your permissionless recourse is to club together and create a fork. But bitcoin won't be joining it. (With respect and no sleight intended.)
Please rejoin bitcoin now, or later if you're not convinced and need to experience 110 forking off and fizzling for yourself to start that journey of introspecting and learning. It would be sad if bitcoin lost people disillusioned due to simple lack of understanding of what's going on there, we're all trying to defend bitcoin and keep it on mission. Including btw the 110 technical promoters, just they wandered off plot somehow.
Join the cypherpunks on bitcoin, come cypherpunk summer๐ in a few weeks. -
Adam Back reposted
Rod Palmer ๐ฅ
@rodpalmerhodl
plebs might have stacked sats but they certainly didnโt remain humble
-
Adam Back reposted
Joe Burnett
@IIICapital
One unintended consequence of BIP-110 is that, if demand for arbitrary data storage remains unchanged, the same amount of spam would consume more block space.
Stephan Livera
@stephanlivera
I made an explainer page on Bitcoin spam and why it's impossible to stop.
Bitcoin is money, you can't stop spam.
stephanlivera.github.io/Bitcoin-Spam/ -
Adam Back reposted
Peach Bitcoin ๐๐ฅ๏ธ
@peachbitcoin
Peach has a very active telegram group since 4+years.
No one ever mentioned BIP 110.
People just care about stacking REAL sats. -
Adam Back reposted
Michael Saylor
@saylor
Bitcoin is an emergent network of wallets weighted by satoshis, nodes weighted by commerce, and miners weighted by hashrate, with capital, consensus, and security held in dynamic equilibrium. $BTC
-
Adam Back reposted
E61
@esixtyone
I lived that period as well and agree. Bitcoin is deeply complex, and moreover, it mostly *is* completely opposite to what you initially *think it is*.
I have looked back and realised I often had the wrong viewpoint, and I'm thankful for those who patiently explain how it *is*. -
Adam Back reposted
ValentinoZ
@vazertuche
Great site, Stephan but sadly, at this point, it wonโt help because it was never about spam.
It was always about CSAM. And ultimately, that was about non-contiguous data.
Unholy images could always be put in the Taproot witness or anywhere else on the blockchain and no one was really losing their mind over it. At least not to this degree.
It wasnโt until Core opened the OP_RETURN limit and allowed spammers the option to pay four times the price to put data in OP_RETURN and thus put it on-chain in the best possible manner, so it doesnโt bloat the UTXO set and can be pruned that suddenly everyone lost their mind.
Including Pope Luke.
Technical people were completely at a loss as to why they were losing their minds. You could already put images in the witness data.
What makes OP_RETURN so different? Why are you losing your mind over this OP_RETURN limit?
Why is opening up a path that is 4X more expensive and less harmful to the UTXO set so UNHOLY?
Slowly, we uncovered the reason.
It was because of CSAM and non-contiguous data.
Apparently, the all-high ruler declared that an image broken up into 520-byte chunks is canonical and therefore allowed.
But if you remove those push-byte opcodes and put it all on-chain continuously, then it becomes unholy because the image can be scanned directly.
Sadly, when we pointed out that all this data is fully obfuscated using an XOR key such that no antivirus software could read whatever image was inscribed on-chain without first obtaining the XOR key, nobody really listened.
Apparently a program can grab an XOR key and decrypt the contiguous data and that is UNHOLY -- BUT a program removing 8 bits of data every 520 bytes to re-constitute an image is cannon.
Someone please...make it make sense.
And the whole thing went downhill from there.
Somehow, they made a golden calf out of an OP_RETURN size-limit increase, when in reality, the spammers were barely using OP_RETURN. (in so far as aggregate bytes of trash put on chain)
Currently, 99% of their OP_RETURN usage falls within the 83-byte limit and will be mined within BIP-110 blocks.
The irony is so thick, you literally cannot make this stuff up. -
Adam Back reposted
Vortex | BIP448
@theonevortex
Cash was referenced in the white paper for its finality, obviously it's digital so it can't be actual cash and it has 10 min block times so obviously it wasn't meant to be as instant as cash (though thanks to LN that usecase now works perfectly well).
-
Adam Back reposted
Rob Hamilton
@Rob1Ham
โPast a certain block height, obsessing over your BIP can be a bad thing.โ
-
Adam Back reposted
Vortex | BIP448
@theonevortex
Bitcoin is already money, the market left spammers behind, there's no philosophical shift and the implementations are healthier than ever. Get off your soap box and actually contribute something useful to bitcoin other than AI slopped FUD.
-
Adam Back reposted
Vortex | BIP448
@theonevortex
They literally gave concrete technical reasons in the blog post, the PR and the mailing list. I mean fine if you don't agree with those reasons but you can't say they didn't give technical reasons.
-
Adam Back reposted
Vortex | BIP448
@theonevortex
> no technical reason at all has been given to make that precise change to the default at the moment
Umm what? -
Adam Back reposted
Natalie Brunell โก๏ธ
@natbrunell
"The current proposal still lets those things into Bitcoin - it just slightly increases the cost of doing so."
The protocol debate is heating up and the messaging around BIP 110 has gotten harsh and confusing so I asked @LynAldenContact for her honest take.
What's actually being debated, why she's wary when changes get pushed fast, and whether any of this is an existential threat to Bitcoin.This media couldn't be displayed. See it on the original post.
Natalie Brunell โก๏ธ
@natbrunell
Where does Bitcoin go from here? @LynAldenContact returns to break down price action, macro, what really happened with Strategy's $STRC, and the protocol fight dividing Bitcoin right now.
We get into:
- Whether Bitcoin has found its floor
- The lowest sentiment Lyn's ever seen
- The crash in Strategy's $STRC and whether holders should be worried
- Her grounded take on the protocol fight and the "existential threat" talk
- Why the Big Print everyone's waiting for still isn't coming
Now streaming on all podcast platforms.This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Loren | Bitcoin Today
@LorenHodl
As the dust settles on the BIP-110 debate, itโs becoming clear that this particular proposal is unlikely to achieve the miner signaling needed for activation. Whether you supported it as a necessary defense of Bitcoinโs monetary focus or opposed it as an overreach that risked innovation and chain stability, one thing is certain: the conversation revealed deep passions on all sides.
Importantly, this debate hasnโt soured my view of the vast majority of Bitcoiners. On both sides I see people who care deeply about the networkโs long-term health, decentralization, and success. We all want Bitcoin to thrive as sound money, a robust settlement layer, and a tool for financial sovereignty. Disagreements on the best path forward are natural in a permissionless system like ours; theyโre a feature, not a bug.
Now is the time to look ahead. If (or when) BIP-110 fades, we should focus on recouping, healing, and reuniting around our shared mission: building and growing the Bitcoin network. That means:
โข Continuing to run and support full nodes for a healthy, decentralized base layer.
โข Innovating responsibly: whether thatโs improving scalability solutions, enhancing privacy, expanding Lightning, or developing practical monetary use cases that respect block space realities.
โข Engaging constructively across divides instead of deepening them. Bitcoin is bigger than any single proposal or faction.
โข Prioritizing education, adoption, and infrastructure that makes Bitcoin more useful and accessible for everyday people and institutions alike.
Bitcoin has survived far greater challenges through its history by sticking to first principles and adapting as a living system. Letโs channel the energy from this debate into positive action. The best way to โwinโ is to make Bitcoin stronger, more valuable, and more antifragile together -
Adam Back reposted
Eric Weiss
@Eric_BIGfund
๐ฏ
-
Adam Back reposted
Sasha Hodder
@sashahodler
Consensus is earned, not declared!
-
Adam Back reposted
Phil Geiger
@phil_geiger
Great post Adam. I'm glad to be on the bitcoin journey with folks like you ๐ค
-
Adam Back reposted
Mark Moss
@1MarkMoss
Thank you for taking the time to write this out and explain it, and the intentions and reasoning behind it.
-
Adam Back reposted
Michael Saylor
@saylor
There are 110 things more dangerous to Bitcoin than spam.
BIP 110 turns a spam dispute into a consensus change that would invalidate some currently valid, fee-paying transactions.
That precedent is the danger. We should save our energy for threats that really matter. $BTC
Adam Back
@adam3us
On the filter fork topic.
I don't usually have time, but this morning listened to one of the twitter spaces from earlier in the week, with some well meaning relative bitcoin newcomers, that humanized them, and their concerns and thoughts for why they thought that made it logical to support 110.
My feeling after listening, is if these are the people with #110 in their handles, I'm sad to see them about to fork off and get disillusioned without understanding why bitcoin rejected 110 robustly.
So here's a more empathetic, constructive higher level version of explaining why not. I hope it's high-level and first-principles enough that everyone can follow.
They seem to want to understand what makes people tick, and are suspicious of intent. So, if someone asked me why is Bitcoin important and what is it, I'd say my (personal) mission and hope for bitcoin is to build the cypherpunk future, that "Snow Crash" was a blueprint, and work backwards from there. Bitcoin I hope leads to fully free markets via bearer unseizable, hard mathematically dependable money. Not everyone is comfortable with that level of freedom, but that's my view. And at this point, I believe that surprisingly, even now many governments have come to understand and value bitcoin's gold-like mathematical assurance, a positive development. Others may have milder views than myself, but still like hard censorship resistant money.
Because of motive suspicion, if it's not obvious: I hate spam with a passion, that's how I came to design hashcash while researching decentralized bearer money with others, and running nodes in privacy related cypherpunk p2p networks nearly three decades ago.
People seem upset about the default op return policy change in bitcoin. I will just assert, there are extremely robust and simple reasons for bitcoin changing default relay policy, and most just didn't do their research, so don't know what those are, or maybe not technical enough to fully understand though there have been 1000s of posts trying to explain in various simplified ways. So that lack of understanding lends itself to shared build-up of false narratives. So here's my back-to-basics higher level explanation.
The decentralization needed to create cypherpunk money has implications a: side effect of decentralization is that you can't impose your views on others. The very decentralization mechanism that helps that, is working against what BIP 110 wants, which at it's most basic is a quest to police other people. I understand supporters don't see their intent like that, but introspect deeper.
You can modify your software, but not anyone else's. Another critical and incredibly robust technical bitcoin immune system is bitcoin can't have people who don't understand technology basics insist on eroding security, decentralization robustness and core properties. That would end badly, fast, and so people will fight you on that.
So the message is Bitcoin respectfully says "no" to what you want. Sorry, and bitcoiners do genuinely understand and empathize that you mean well, have high level thoughts that make emotional sense, and articulate sensible bitcoin-defensive high level ideas, but they are not grounded and without you seeing it, the way you propose to achieve your ideas, hard-conflict with free cypherpunk permissionless money.
My advice is to listen to more experienced people who understand the system and why it works the way it does, to whatever detail you want to understand the grounded reasons for why this is the implication of decentralization and cypherpunk money.
I guarantee you the developer and protocol ecosystem shares and exceeds your views on bearer hard money (and dislike of spam). You may not agree with individual developers choices, views, way of expressing themselves etc, BUT you also need to understand the IETF-like decentralized technical consensus process creates a protective change resistance, that is highly effective at protecting bitcoin mission. The implication of which is no developer can change anything without technical consensus from hundreds of other developers and protocol observers who are pedantic and extremely knowledgeable clever people who won't let any unaddressed technical question past. The protective change resistance is robust and decentralized in an amplifying way because of this technical consensus.
And the many highly technical mainline developers' cypherpunk mission mindsets are probably far more determined than you can even handle on clarity of understanding and views about freedoms on permissionless networks, as many of you are probably still subconsciously inured by the matrix, where they have transcended that, and grew up immersed in it decades ago. They think natively in this space, while you are just grappling with the surface. Many wont have internalized or have the experience to know how this internet physics works, where there is no policeman, no policy authority, just mathematics, free market and hard money. That has implications for your views also, unfortunately.
Now the tough pill, which is unfortunately true: If you won't listen to reason, educate yourself, learn, the same radical freedom applies to you: your permissionless recourse is to club together and create a fork. But bitcoin won't be joining it. (With respect and no sleight intended.)
Please rejoin bitcoin now, or later if you're not convinced and need to experience 110 forking off and fizzling for yourself to start that journey of introspecting and learning. It would be sad if bitcoin lost people disillusioned due to simple lack of understanding of what's going on there, we're all trying to defend bitcoin and keep it on mission. Including btw the 110 technical promoters, just they wandered off plot somehow.
Join the cypherpunks on bitcoin, come cypherpunk summer๐ in a few weeks. -
Adam Back reposted
Joe Nakamoto โก๏ธ
@JoeNakamoto
It's incredibly cheap to take custody of your ocins
This Blockstream Jade Core bitcoin hardware wallet is only $99
BUY ONE AND TAKE CUSTODY!
Joe Nakamoto โก๏ธ
@JoeNakamoto
FCK LEDGER
Buy a Blockstream Jade Core instead.
Here's whyThis media couldn't be displayed. See it on the original post. -
Adam Back reposted
MacronautBTC
@Macronaut_
that is the most eloquent and 'kind' way to deal with 110ers. thank you.
-
Adam Back reposted
Adrian Morris
@_Adrian
The answer is still no and no.
That is your opinion, fine, but from a system and network standpoint? No. -
Adam Back reposted
Vortex | BIP448
@theonevortex
I can't seem to reply to @tropmonky so I'll paste my response here to Adam in the same thread for @tropmonky:
Op return was never "blown open". I explain the technical issues with 110 here: x.com/theonevortex/status/2020594400955695442
And Stephan has a nice website that refutes incorrect claims like the op return being "blown open" here: stephanlivera.github.io/Bitcoin-Spam/
Vortex | BIP448
@theonevortex
It's strange to start the discussion by ignoring all the fork risk like splitting the network and so fourth but here's a few:
-Protocol/Ledger neutrality - By moving "Standardness" filters into "Consensus" rules Bitcoin ceases to be a neutral settlement layer and starts looking like a curated platform and this sets a precedent where a 55% majority can decide that your valid transaction is "spam" simply because they dislike the use case
-It doesn't actually solve the problem - As Peter Todd demonstrated these filters are easily bypassed as he successfully embedded the entire 6,000-word text of BIP 110 into a single transaction by fragmenting the data across multiple 256-byte PUSHDATA elements and 83-byte OP_RETURNs so this proves the fork doesn't stop data it only increases the transaction fee "tax" for users
-Incentivizes Centralizing BlockSpace Market - Capping the public relay at 83 bytes forces high-volume data users to bypass the P2P network and instead pay large mining pools directly via private APIs to include "illegal" non-standard data which creates a private blockspace market that small home-node miners cannot see or profit from
-Risk of confiscation / disruption to backwards compatibility - As Gregory Maxwell noted Bitcoin nodes have no "global state" of pre-signed transactions so if a user has a multi-year inheritance plan or a "Vault" emergency exit signed offline that uses a 500-byte script or an OP_IF branch BIP 110 welds that exit shut and since the transaction is now consensus-invalid the funds are effectively confiscated for the duration of the fork
-Anti-Scaling (Kills eltoo/ln-symmetry) - BIP 110 explicitly invalidates the Taproot Annex which directly blocks the ln-symmetry upgrade which is the industry's best hope for a Lightning Network that dramatically reduces the need for constant watchtower monitoring and enables simpler multi-party channels
-Creates UTXO bloat - BIP 110 incentivizes spammers to hide data inside fake addresses/UTXOs (like multisig-encoded data) and while an OP_RETURN can be ignored by a lean node, a fake UTXO must be tracked by every node forever so BIP 110 intended to "save" nodes but actually creates a more expensive permanent burden on them
-Breaks Miniscript & Vaults - Miniscript is the industry standard for writing readable secure smart contracts (used for inheritance, multi-party escrow, timelocked recovery) and relies heavily on OP_IF to branch between conditions so by banning OP_IF in Tapscripts BIP 110 effectively breaks Taproot-based custody setups that represent the direction the entire industry is moving
-Lobotomizes BitVM - BitVM is one of very few viable paths to trustless Layer 2 bridges and requires deep "Taproot Trees" (Merkle paths) to verify computation and a 257-byte limit caps the tree depth at roughly 7 levels (128 leaves) when BitVM protocols often require thousands of leaves to function
-Loss in fees for miners - If you filter out the highest paying transactions because you don't like their content you are effectively asking miners to take a pay cut which could lower the "hash price" and as block subsidy continues to halve transaction fees become increasingly critical to security
-Rushed Timeline / Governance Precedent - BIP 110 activates unconditionally by September 2026 regardless of support with early activation possible at just 55% signaling within a tiny 3-month window and this "emergency" style of governance is a radical departure from Bitcoin's traditional 90%+ consensus model, if rushed "emergency" consensus changes become normalized that governance precedent is permanent even if the technical changes expire -
Adam Back reposted
Mike Schmidt
@bitschmidty
Hey @CypherSafe I help run Brink, one of the funding orgs. You may be interested in some/all of these.
A summary of what Brink-funded engineers worked on in 2025 and the related impact:
brink.dev/blog/2026/03/26/engineering-impact-report-2025/
A 2025 annual report from Brink at an organizational level, including donations to Brink and our expenses:
brink.dev/blog/2026/05/26/2025-annual-report/
Second half of this tweet articulating some Brink governance: x.com/bitschmidty/status/1967233629618065709
More broadly, I tried to summarize what Bitcoin Core developers have been working on:
Mike Schmidt
@bitschmidty
I recently presented "The State of Bitcoin Core" at the OPNEXT conference.
Its ~100 slides on what Bitcoin Core developers are actively working on.
www.youtube.com/watch?v=F3ONZsG-SY0 -
Adam Back reposted
KC
@foolrushingin
thank you, @adam3us for taking the time to write that. It's human, insightful and not simply a response to somebody else's foolish assertion (which means we only get to see snippets of a conversation unless we do lots of work). I really appreciate this overview from you.
-
Adam Back reposted
Ryan ๐ โก๏ธ๐ฅ
@LibertyBTC
Worth reading and considering, regardless of your stance on BIP-110 or Adam Back.
He is literally cited in the whitepaper and personally corresponded with Satoshi.
Satoshi read his work. You should hear his thoughts.
Adam Back
@adam3us
On the filter fork topic.
I don't usually have time, but this morning listened to one of the twitter spaces from earlier in the week, with some well meaning relative bitcoin newcomers, that humanized them, and their concerns and thoughts for why they thought that made it logical to support 110.
My feeling after listening, is if these are the people with #110 in their handles, I'm sad to see them about to fork off and get disillusioned without understanding why bitcoin rejected 110 robustly.
So here's a more empathetic, constructive higher level version of explaining why not. I hope it's high-level and first-principles enough that everyone can follow.
They seem to want to understand what makes people tick, and are suspicious of intent. So, if someone asked me why is Bitcoin important and what is it, I'd say my (personal) mission and hope for bitcoin is to build the cypherpunk future, that "Snow Crash" was a blueprint, and work backwards from there. Bitcoin I hope leads to fully free markets via bearer unseizable, hard mathematically dependable money. Not everyone is comfortable with that level of freedom, but that's my view. And at this point, I believe that surprisingly, even now many governments have come to understand and value bitcoin's gold-like mathematical assurance, a positive development. Others may have milder views than myself, but still like hard censorship resistant money.
Because of motive suspicion, if it's not obvious: I hate spam with a passion, that's how I came to design hashcash while researching decentralized bearer money with others, and running nodes in privacy related cypherpunk p2p networks nearly three decades ago.
People seem upset about the default op return policy change in bitcoin. I will just assert, there are extremely robust and simple reasons for bitcoin changing default relay policy, and most just didn't do their research, so don't know what those are, or maybe not technical enough to fully understand though there have been 1000s of posts trying to explain in various simplified ways. So that lack of understanding lends itself to shared build-up of false narratives. So here's my back-to-basics higher level explanation.
The decentralization needed to create cypherpunk money has implications a: side effect of decentralization is that you can't impose your views on others. The very decentralization mechanism that helps that, is working against what BIP 110 wants, which at it's most basic is a quest to police other people. I understand supporters don't see their intent like that, but introspect deeper.
You can modify your software, but not anyone else's. Another critical and incredibly robust technical bitcoin immune system is bitcoin can't have people who don't understand technology basics insist on eroding security, decentralization robustness and core properties. That would end badly, fast, and so people will fight you on that.
So the message is Bitcoin respectfully says "no" to what you want. Sorry, and bitcoiners do genuinely understand and empathize that you mean well, have high level thoughts that make emotional sense, and articulate sensible bitcoin-defensive high level ideas, but they are not grounded and without you seeing it, the way you propose to achieve your ideas, hard-conflict with free cypherpunk permissionless money.
My advice is to listen to more experienced people who understand the system and why it works the way it does, to whatever detail you want to understand the grounded reasons for why this is the implication of decentralization and cypherpunk money.
I guarantee you the developer and protocol ecosystem shares and exceeds your views on bearer hard money (and dislike of spam). You may not agree with individual developers choices, views, way of expressing themselves etc, BUT you also need to understand the IETF-like decentralized technical consensus process creates a protective change resistance, that is highly effective at protecting bitcoin mission. The implication of which is no developer can change anything without technical consensus from hundreds of other developers and protocol observers who are pedantic and extremely knowledgeable clever people who won't let any unaddressed technical question past. The protective change resistance is robust and decentralized in an amplifying way because of this technical consensus.
And the many highly technical mainline developers' cypherpunk mission mindsets are probably far more determined than you can even handle on clarity of understanding and views about freedoms on permissionless networks, as many of you are probably still subconsciously inured by the matrix, where they have transcended that, and grew up immersed in it decades ago. They think natively in this space, while you are just grappling with the surface. Many wont have internalized or have the experience to know how this internet physics works, where there is no policeman, no policy authority, just mathematics, free market and hard money. That has implications for your views also, unfortunately.
Now the tough pill, which is unfortunately true: If you won't listen to reason, educate yourself, learn, the same radical freedom applies to you: your permissionless recourse is to club together and create a fork. But bitcoin won't be joining it. (With respect and no sleight intended.)
Please rejoin bitcoin now, or later if you're not convinced and need to experience 110 forking off and fizzling for yourself to start that journey of introspecting and learning. It would be sad if bitcoin lost people disillusioned due to simple lack of understanding of what's going on there, we're all trying to defend bitcoin and keep it on mission. Including btw the 110 technical promoters, just they wandered off plot somehow.
Join the cypherpunks on bitcoin, come cypherpunk summer๐ in a few weeks. -
Adam Back reposted
Alexandre Laizet โก๏ธ
@AlexandreLaizet
โIf someone asked me why is Bitcoin important and what is it, Iโd say my (personal) mission and hope for bitcoin is to build the cypherpunk future, that โSnow Crashโ was a blueprint, and work backwards from there. Bitcoin I hope leads to fully free markets via bearer unseizable, hard mathematically dependable money.โ โ @adam3us โก๏ธ๐๐ปโก๏ธ
You canโt impose your preferences on everyone else without forking off. Bitcoin respectfully says โnoโ when something conflicts with permissionless, censorship-resistant hard money.
โ / 21M ๐
Adam Back
@adam3us
On the filter fork topic.
I don't usually have time, but this morning listened to one of the twitter spaces from earlier in the week, with some well meaning relative bitcoin newcomers, that humanized them, and their concerns and thoughts for why they thought that made it logical to support 110.
My feeling after listening, is if these are the people with #110 in their handles, I'm sad to see them about to fork off and get disillusioned without understanding why bitcoin rejected 110 robustly.
So here's a more empathetic, constructive higher level version of explaining why not. I hope it's high-level and first-principles enough that everyone can follow.
They seem to want to understand what makes people tick, and are suspicious of intent. So, if someone asked me why is Bitcoin important and what is it, I'd say my (personal) mission and hope for bitcoin is to build the cypherpunk future, that "Snow Crash" was a blueprint, and work backwards from there. Bitcoin I hope leads to fully free markets via bearer unseizable, hard mathematically dependable money. Not everyone is comfortable with that level of freedom, but that's my view. And at this point, I believe that surprisingly, even now many governments have come to understand and value bitcoin's gold-like mathematical assurance, a positive development. Others may have milder views than myself, but still like hard censorship resistant money.
Because of motive suspicion, if it's not obvious: I hate spam with a passion, that's how I came to design hashcash while researching decentralized bearer money with others, and running nodes in privacy related cypherpunk p2p networks nearly three decades ago.
People seem upset about the default op return policy change in bitcoin. I will just assert, there are extremely robust and simple reasons for bitcoin changing default relay policy, and most just didn't do their research, so don't know what those are, or maybe not technical enough to fully understand though there have been 1000s of posts trying to explain in various simplified ways. So that lack of understanding lends itself to shared build-up of false narratives. So here's my back-to-basics higher level explanation.
The decentralization needed to create cypherpunk money has implications a: side effect of decentralization is that you can't impose your views on others. The very decentralization mechanism that helps that, is working against what BIP 110 wants, which at it's most basic is a quest to police other people. I understand supporters don't see their intent like that, but introspect deeper.
You can modify your software, but not anyone else's. Another critical and incredibly robust technical bitcoin immune system is bitcoin can't have people who don't understand technology basics insist on eroding security, decentralization robustness and core properties. That would end badly, fast, and so people will fight you on that.
So the message is Bitcoin respectfully says "no" to what you want. Sorry, and bitcoiners do genuinely understand and empathize that you mean well, have high level thoughts that make emotional sense, and articulate sensible bitcoin-defensive high level ideas, but they are not grounded and without you seeing it, the way you propose to achieve your ideas, hard-conflict with free cypherpunk permissionless money.
My advice is to listen to more experienced people who understand the system and why it works the way it does, to whatever detail you want to understand the grounded reasons for why this is the implication of decentralization and cypherpunk money.
I guarantee you the developer and protocol ecosystem shares and exceeds your views on bearer hard money (and dislike of spam). You may not agree with individual developers choices, views, way of expressing themselves etc, BUT you also need to understand the IETF-like decentralized technical consensus process creates a protective change resistance, that is highly effective at protecting bitcoin mission. The implication of which is no developer can change anything without technical consensus from hundreds of other developers and protocol observers who are pedantic and extremely knowledgeable clever people who won't let any unaddressed technical question past. The protective change resistance is robust and decentralized in an amplifying way because of this technical consensus.
And the many highly technical mainline developers' cypherpunk mission mindsets are probably far more determined than you can even handle on clarity of understanding and views about freedoms on permissionless networks, as many of you are probably still subconsciously inured by the matrix, where they have transcended that, and grew up immersed in it decades ago. They think natively in this space, while you are just grappling with the surface. Many wont have internalized or have the experience to know how this internet physics works, where there is no policeman, no policy authority, just mathematics, free market and hard money. That has implications for your views also, unfortunately.
Now the tough pill, which is unfortunately true: If you won't listen to reason, educate yourself, learn, the same radical freedom applies to you: your permissionless recourse is to club together and create a fork. But bitcoin won't be joining it. (With respect and no sleight intended.)
Please rejoin bitcoin now, or later if you're not convinced and need to experience 110 forking off and fizzling for yourself to start that journey of introspecting and learning. It would be sad if bitcoin lost people disillusioned due to simple lack of understanding of what's going on there, we're all trying to defend bitcoin and keep it on mission. Including btw the 110 technical promoters, just they wandered off plot somehow.
Join the cypherpunks on bitcoin, come cypherpunk summer๐ in a few weeks. -
Adam Back reposted
Don Ricardo Salinas Pliego
@RicardoBSalinas
Thanks @adam3us. Agree 100%
Adam Back
@adam3us
On the filter fork topic.
I don't usually have time, but this morning listened to one of the twitter spaces from earlier in the week, with some well meaning relative bitcoin newcomers, that humanized them, and their concerns and thoughts for why they thought that made it logical to support 110.
My feeling after listening, is if these are the people with #110 in their handles, I'm sad to see them about to fork off and get disillusioned without understanding why bitcoin rejected 110 robustly.
So here's a more empathetic, constructive higher level version of explaining why not. I hope it's high-level and first-principles enough that everyone can follow.
They seem to want to understand what makes people tick, and are suspicious of intent. So, if someone asked me why is Bitcoin important and what is it, I'd say my (personal) mission and hope for bitcoin is to build the cypherpunk future, that "Snow Crash" was a blueprint, and work backwards from there. Bitcoin I hope leads to fully free markets via bearer unseizable, hard mathematically dependable money. Not everyone is comfortable with that level of freedom, but that's my view. And at this point, I believe that surprisingly, even now many governments have come to understand and value bitcoin's gold-like mathematical assurance, a positive development. Others may have milder views than myself, but still like hard censorship resistant money.
Because of motive suspicion, if it's not obvious: I hate spam with a passion, that's how I came to design hashcash while researching decentralized bearer money with others, and running nodes in privacy related cypherpunk p2p networks nearly three decades ago.
People seem upset about the default op return policy change in bitcoin. I will just assert, there are extremely robust and simple reasons for bitcoin changing default relay policy, and most just didn't do their research, so don't know what those are, or maybe not technical enough to fully understand though there have been 1000s of posts trying to explain in various simplified ways. So that lack of understanding lends itself to shared build-up of false narratives. So here's my back-to-basics higher level explanation.
The decentralization needed to create cypherpunk money has implications a: side effect of decentralization is that you can't impose your views on others. The very decentralization mechanism that helps that, is working against what BIP 110 wants, which at it's most basic is a quest to police other people. I understand supporters don't see their intent like that, but introspect deeper.
You can modify your software, but not anyone else's. Another critical and incredibly robust technical bitcoin immune system is bitcoin can't have people who don't understand technology basics insist on eroding security, decentralization robustness and core properties. That would end badly, fast, and so people will fight you on that.
So the message is Bitcoin respectfully says "no" to what you want. Sorry, and bitcoiners do genuinely understand and empathize that you mean well, have high level thoughts that make emotional sense, and articulate sensible bitcoin-defensive high level ideas, but they are not grounded and without you seeing it, the way you propose to achieve your ideas, hard-conflict with free cypherpunk permissionless money.
My advice is to listen to more experienced people who understand the system and why it works the way it does, to whatever detail you want to understand the grounded reasons for why this is the implication of decentralization and cypherpunk money.
I guarantee you the developer and protocol ecosystem shares and exceeds your views on bearer hard money (and dislike of spam). You may not agree with individual developers choices, views, way of expressing themselves etc, BUT you also need to understand the IETF-like decentralized technical consensus process creates a protective change resistance, that is highly effective at protecting bitcoin mission. The implication of which is no developer can change anything without technical consensus from hundreds of other developers and protocol observers who are pedantic and extremely knowledgeable clever people who won't let any unaddressed technical question past. The protective change resistance is robust and decentralized in an amplifying way because of this technical consensus.
And the many highly technical mainline developers' cypherpunk mission mindsets are probably far more determined than you can even handle on clarity of understanding and views about freedoms on permissionless networks, as many of you are probably still subconsciously inured by the matrix, where they have transcended that, and grew up immersed in it decades ago. They think natively in this space, while you are just grappling with the surface. Many wont have internalized or have the experience to know how this internet physics works, where there is no policeman, no policy authority, just mathematics, free market and hard money. That has implications for your views also, unfortunately.
Now the tough pill, which is unfortunately true: If you won't listen to reason, educate yourself, learn, the same radical freedom applies to you: your permissionless recourse is to club together and create a fork. But bitcoin won't be joining it. (With respect and no sleight intended.)
Please rejoin bitcoin now, or later if you're not convinced and need to experience 110 forking off and fizzling for yourself to start that journey of introspecting and learning. It would be sad if bitcoin lost people disillusioned due to simple lack of understanding of what's going on there, we're all trying to defend bitcoin and keep it on mission. Including btw the 110 technical promoters, just they wandered off plot somehow.
Join the cypherpunks on bitcoin, come cypherpunk summer๐ in a few weeks. -
Adam Back reposted
BitcoinJiuJitsu
@BitcoinJiuJitsu
"You can modify your software, but not anyone else's. Another critical and incredibly robust technical bitcoin immune system is bitcoin can't have people who don't understand technology basics insist on eroding security, decentralization robustness and core properties." ๐ค
Adam Back
@adam3us
On the filter fork topic.
I don't usually have time, but this morning listened to one of the twitter spaces from earlier in the week, with some well meaning relative bitcoin newcomers, that humanized them, and their concerns and thoughts for why they thought that made it logical to support 110.
My feeling after listening, is if these are the people with #110 in their handles, I'm sad to see them about to fork off and get disillusioned without understanding why bitcoin rejected 110 robustly.
So here's a more empathetic, constructive higher level version of explaining why not. I hope it's high-level and first-principles enough that everyone can follow.
They seem to want to understand what makes people tick, and are suspicious of intent. So, if someone asked me why is Bitcoin important and what is it, I'd say my (personal) mission and hope for bitcoin is to build the cypherpunk future, that "Snow Crash" was a blueprint, and work backwards from there. Bitcoin I hope leads to fully free markets via bearer unseizable, hard mathematically dependable money. Not everyone is comfortable with that level of freedom, but that's my view. And at this point, I believe that surprisingly, even now many governments have come to understand and value bitcoin's gold-like mathematical assurance, a positive development. Others may have milder views than myself, but still like hard censorship resistant money.
Because of motive suspicion, if it's not obvious: I hate spam with a passion, that's how I came to design hashcash while researching decentralized bearer money with others, and running nodes in privacy related cypherpunk p2p networks nearly three decades ago.
People seem upset about the default op return policy change in bitcoin. I will just assert, there are extremely robust and simple reasons for bitcoin changing default relay policy, and most just didn't do their research, so don't know what those are, or maybe not technical enough to fully understand though there have been 1000s of posts trying to explain in various simplified ways. So that lack of understanding lends itself to shared build-up of false narratives. So here's my back-to-basics higher level explanation.
The decentralization needed to create cypherpunk money has implications a: side effect of decentralization is that you can't impose your views on others. The very decentralization mechanism that helps that, is working against what BIP 110 wants, which at it's most basic is a quest to police other people. I understand supporters don't see their intent like that, but introspect deeper.
You can modify your software, but not anyone else's. Another critical and incredibly robust technical bitcoin immune system is bitcoin can't have people who don't understand technology basics insist on eroding security, decentralization robustness and core properties. That would end badly, fast, and so people will fight you on that.
So the message is Bitcoin respectfully says "no" to what you want. Sorry, and bitcoiners do genuinely understand and empathize that you mean well, have high level thoughts that make emotional sense, and articulate sensible bitcoin-defensive high level ideas, but they are not grounded and without you seeing it, the way you propose to achieve your ideas, hard-conflict with free cypherpunk permissionless money.
My advice is to listen to more experienced people who understand the system and why it works the way it does, to whatever detail you want to understand the grounded reasons for why this is the implication of decentralization and cypherpunk money.
I guarantee you the developer and protocol ecosystem shares and exceeds your views on bearer hard money (and dislike of spam). You may not agree with individual developers choices, views, way of expressing themselves etc, BUT you also need to understand the IETF-like decentralized technical consensus process creates a protective change resistance, that is highly effective at protecting bitcoin mission. The implication of which is no developer can change anything without technical consensus from hundreds of other developers and protocol observers who are pedantic and extremely knowledgeable clever people who won't let any unaddressed technical question past. The protective change resistance is robust and decentralized in an amplifying way because of this technical consensus.
And the many highly technical mainline developers' cypherpunk mission mindsets are probably far more determined than you can even handle on clarity of understanding and views about freedoms on permissionless networks, as many of you are probably still subconsciously inured by the matrix, where they have transcended that, and grew up immersed in it decades ago. They think natively in this space, while you are just grappling with the surface. Many wont have internalized or have the experience to know how this internet physics works, where there is no policeman, no policy authority, just mathematics, free market and hard money. That has implications for your views also, unfortunately.
Now the tough pill, which is unfortunately true: If you won't listen to reason, educate yourself, learn, the same radical freedom applies to you: your permissionless recourse is to club together and create a fork. But bitcoin won't be joining it. (With respect and no sleight intended.)
Please rejoin bitcoin now, or later if you're not convinced and need to experience 110 forking off and fizzling for yourself to start that journey of introspecting and learning. It would be sad if bitcoin lost people disillusioned due to simple lack of understanding of what's going on there, we're all trying to defend bitcoin and keep it on mission. Including btw the 110 technical promoters, just they wandered off plot somehow.
Join the cypherpunks on bitcoin, come cypherpunk summer๐ in a few weeks. -
Adam Back reposted
cruxzy
@cruxzy
Preaching the fundamentals. Nice to see a more empathetic and thoughtful commentary here. This is helpful! Thanks Adam.
-
Adam Back reposted
Gareth Jenkinson
@gazza_jenks
Another great, more levelheaded and well meaning rebuttal of BIP110 by Adam Back.
Recommended weekend reading ๐
Adam Back
@adam3us
On the filter fork topic.
I don't usually have time, but this morning listened to one of the twitter spaces from earlier in the week, with some well meaning relative bitcoin newcomers, that humanized them, and their concerns and thoughts for why they thought that made it logical to support 110.
My feeling after listening, is if these are the people with #110 in their handles, I'm sad to see them about to fork off and get disillusioned without understanding why bitcoin rejected 110 robustly.
So here's a more empathetic, constructive higher level version of explaining why not. I hope it's high-level and first-principles enough that everyone can follow.
They seem to want to understand what makes people tick, and are suspicious of intent. So, if someone asked me why is Bitcoin important and what is it, I'd say my (personal) mission and hope for bitcoin is to build the cypherpunk future, that "Snow Crash" was a blueprint, and work backwards from there. Bitcoin I hope leads to fully free markets via bearer unseizable, hard mathematically dependable money. Not everyone is comfortable with that level of freedom, but that's my view. And at this point, I believe that surprisingly, even now many governments have come to understand and value bitcoin's gold-like mathematical assurance, a positive development. Others may have milder views than myself, but still like hard censorship resistant money.
Because of motive suspicion, if it's not obvious: I hate spam with a passion, that's how I came to design hashcash while researching decentralized bearer money with others, and running nodes in privacy related cypherpunk p2p networks nearly three decades ago.
People seem upset about the default op return policy change in bitcoin. I will just assert, there are extremely robust and simple reasons for bitcoin changing default relay policy, and most just didn't do their research, so don't know what those are, or maybe not technical enough to fully understand though there have been 1000s of posts trying to explain in various simplified ways. So that lack of understanding lends itself to shared build-up of false narratives. So here's my back-to-basics higher level explanation.
The decentralization needed to create cypherpunk money has implications a: side effect of decentralization is that you can't impose your views on others. The very decentralization mechanism that helps that, is working against what BIP 110 wants, which at it's most basic is a quest to police other people. I understand supporters don't see their intent like that, but introspect deeper.
You can modify your software, but not anyone else's. Another critical and incredibly robust technical bitcoin immune system is bitcoin can't have people who don't understand technology basics insist on eroding security, decentralization robustness and core properties. That would end badly, fast, and so people will fight you on that.
So the message is Bitcoin respectfully says "no" to what you want. Sorry, and bitcoiners do genuinely understand and empathize that you mean well, have high level thoughts that make emotional sense, and articulate sensible bitcoin-defensive high level ideas, but they are not grounded and without you seeing it, the way you propose to achieve your ideas, hard-conflict with free cypherpunk permissionless money.
My advice is to listen to more experienced people who understand the system and why it works the way it does, to whatever detail you want to understand the grounded reasons for why this is the implication of decentralization and cypherpunk money.
I guarantee you the developer and protocol ecosystem shares and exceeds your views on bearer hard money (and dislike of spam). You may not agree with individual developers choices, views, way of expressing themselves etc, BUT you also need to understand the IETF-like decentralized technical consensus process creates a protective change resistance, that is highly effective at protecting bitcoin mission. The implication of which is no developer can change anything without technical consensus from hundreds of other developers and protocol observers who are pedantic and extremely knowledgeable clever people who won't let any unaddressed technical question past. The protective change resistance is robust and decentralized in an amplifying way because of this technical consensus.
And the many highly technical mainline developers' cypherpunk mission mindsets are probably far more determined than you can even handle on clarity of understanding and views about freedoms on permissionless networks, as many of you are probably still subconsciously inured by the matrix, where they have transcended that, and grew up immersed in it decades ago. They think natively in this space, while you are just grappling with the surface. Many wont have internalized or have the experience to know how this internet physics works, where there is no policeman, no policy authority, just mathematics, free market and hard money. That has implications for your views also, unfortunately.
Now the tough pill, which is unfortunately true: If you won't listen to reason, educate yourself, learn, the same radical freedom applies to you: your permissionless recourse is to club together and create a fork. But bitcoin won't be joining it. (With respect and no sleight intended.)
Please rejoin bitcoin now, or later if you're not convinced and need to experience 110 forking off and fizzling for yourself to start that journey of introspecting and learning. It would be sad if bitcoin lost people disillusioned due to simple lack of understanding of what's going on there, we're all trying to defend bitcoin and keep it on mission. Including btw the 110 technical promoters, just they wandered off plot somehow.
Join the cypherpunks on bitcoin, come cypherpunk summer๐ in a few weeks. -
Adam Back reposted
Oiko
@OikosBack
cypherpunks write code, cypherpunk summer is in full flow, forking off would be a mistake at this point.
-
Adam Back reposted
Phil Geiger
@phil_geiger
It's possible! My guess is less than 3k BTC, maybe less than 2k BTC. There are a few small companies and miners that support it, and a few folks that have been in bitcoin for quite a while, so I think it's likely to be around 1k bitcoin just from who I know supports it.
-
Adam Back reposted
Coinjoined Chris โก
@coinjoined
Liar
-
Adam Back
@adam3us
On the filter fork topic.
I don't usually have time, but this morning listened to one of the twitter spaces from earlier in the week, with some well meaning relative bitcoin newcomers, that humanized them, and their concerns and thoughts for why they thought that made it logical to support 110.
My feeling after listening, is if these are the people with #110 in their handles, I'm sad to see them about to fork off and get disillusioned without understanding why bitcoin rejected 110 robustly.
So here's a more empathetic, constructive higher level version of explaining why not. I hope it's high-level and first-principles enough that everyone can follow.
They seem to want to understand what makes people tick, and are suspicious of intent. So, if someone asked me why is Bitcoin important and what is it, I'd say my (personal) mission and hope for bitcoin is to build the cypherpunk future, that "Snow Crash" was a blueprint, and work backwards from there. Bitcoin I hope leads to fully free markets via bearer unseizable, hard mathematically dependable money. Not everyone is comfortable with that level of freedom, but that's my view. And at this point, I believe that surprisingly, even now many governments have come to understand and value bitcoin's gold-like mathematical assurance, a positive development. Others may have milder views than myself, but still like hard censorship resistant money.
Because of motive suspicion, if it's not obvious: I hate spam with a passion, that's how I came to design hashcash while researching decentralized bearer money with others, and running nodes in privacy related cypherpunk p2p networks nearly three decades ago.
People seem upset about the default op return policy change in bitcoin. I will just assert, there are extremely robust and simple reasons for bitcoin changing default relay policy, and most just didn't do their research, so don't know what those are, or maybe not technical enough to fully understand though there have been 1000s of posts trying to explain in various simplified ways. So that lack of understanding lends itself to shared build-up of false narratives. So here's my back-to-basics higher level explanation.
The decentralization needed to create cypherpunk money has implications a: side effect of decentralization is that you can't impose your views on others. The very decentralization mechanism that helps that, is working against what BIP 110 wants, which at it's most basic is a quest to police other people. I understand supporters don't see their intent like that, but introspect deeper.
You can modify your software, but not anyone else's. Another critical and incredibly robust technical bitcoin immune system is bitcoin can't have people who don't understand technology basics insist on eroding security, decentralization robustness and core properties. That would end badly, fast, and so people will fight you on that.
So the message is Bitcoin respectfully says "no" to what you want. Sorry, and bitcoiners do genuinely understand and empathize that you mean well, have high level thoughts that make emotional sense, and articulate sensible bitcoin-defensive high level ideas, but they are not grounded and without you seeing it, the way you propose to achieve your ideas, hard-conflict with free cypherpunk permissionless money.
My advice is to listen to more experienced people who understand the system and why it works the way it does, to whatever detail you want to understand the grounded reasons for why this is the implication of decentralization and cypherpunk money.
I guarantee you the developer and protocol ecosystem shares and exceeds your views on bearer hard money (and dislike of spam). You may not agree with individual developers choices, views, way of expressing themselves etc, BUT you also need to understand the IETF-like decentralized technical consensus process creates a protective change resistance, that is highly effective at protecting bitcoin mission. The implication of which is no developer can change anything without technical consensus from hundreds of other developers and protocol observers who are pedantic and extremely knowledgeable clever people who won't let any unaddressed technical question past. The protective change resistance is robust and decentralized in an amplifying way because of this technical consensus.
And the many highly technical mainline developers' cypherpunk mission mindsets are probably far more determined than you can even handle on clarity of understanding and views about freedoms on permissionless networks, as many of you are probably still subconsciously inured by the matrix, where they have transcended that, and grew up immersed in it decades ago. They think natively in this space, while you are just grappling with the surface. Many wont have internalized or have the experience to know how this internet physics works, where there is no policeman, no policy authority, just mathematics, free market and hard money. That has implications for your views also, unfortunately.
Now the tough pill, which is unfortunately true: If you won't listen to reason, educate yourself, learn, the same radical freedom applies to you: your permissionless recourse is to club together and create a fork. But bitcoin won't be joining it. (With respect and no sleight intended.)
Please rejoin bitcoin now, or later if you're not convinced and need to experience 110 forking off and fizzling for yourself to start that journey of introspecting and learning. It would be sad if bitcoin lost people disillusioned due to simple lack of understanding of what's going on there, we're all trying to defend bitcoin and keep it on mission. Including btw the 110 technical promoters, just they wandered off plot somehow.
Join the cypherpunks on bitcoin, come cypherpunk summer๐ in a few weeks. -
Adam Back reposted
Rod Palmer ๐ฅ
@rodpalmerhodl
the fee market will solve the pleb problem
-
Adam Back reposted
Wicked
@w_s_bitcoin
This tweet is deep.
Rod Palmer ๐ฅ
@rodpalmerhodl
the fee market will solve the pleb problem
-
Adam Back reposted
Wicked
@w_s_bitcoin
Most of the spam isnโt artists etching their pieces into the timechainโฆitโs Chinese scammers minting brc20 and runes memecoins.
-
Adam Back reposted
Rod Palmer ๐ฅ
@rodpalmerhodl
-
Adam Back reposted
Stephan Livera
@stephanlivera
Yeah it's shifting from my earlier podcast days. I'm varying my format a bit and trying out some shorter, snappier episodes in addition to the longer ones.
-
Adam Back reposted
Rod Palmer ๐ฅ
@rodpalmerhodl
-
Adam Back reposted
-
Adam Back reposted
l0rinc
@L0RINC
Nope, Core didn't "change" anything, we released a new version that adapted to reality. If you prefer staying in your comfy echo chamber you can simply not use it - and nothing changes, so you can finally stop whining and blaming others.
l0rinc
@L0RINC
After talking with @Princey21M in Prague, I realized Bitcoin Core v30โs OP_RETURN policy change isnโt obvious to many: it didnโt create large OP_RETURN usage, it reacted to usage that already existed by removing a gate that wasnโt actually working.
-
Adam Back reposted
HeroGamerโก
@herogamer21btc
Core did not impose their policy settings on peopleโs nodes.
It is opt-in, you upgrade it to get the latest new policy change. Whilst still able to set it to the old setting.
Knots are wanting to impose their CONSENSUS rules upon the whole network.
Major differences. -
Adam Back
@adam3us
if some 110 proponents would put their money where their mouth is, we could make them pay for the boat party when cypherpunk summer starts๐
(by shorting their fork, and buying more BTC!)
(there's effectively no bid, the open interest with BCH & SegWit2x was > 100,000x more) -
Adam Back reposted
Daniel ษrrr
@csuwildcat
What it feels like correcting inaccuracies and FUD spread by folks spending their life-energy on pushing a contentious, incoherent Bitcoin fork:
-
Adam Back reposted
Mark Harvey
@thepowerfulHRV
If you listen carefully, you can hear Bitcoinโs auto-immune system rejecting BIP-110 in real time.
-
Adam Back reposted
Bit Paine โก๏ธ
@BitPaine
$SATA $100 ๐
-
Adam Back reposted
Stephan Livera
@stephanlivera
Just note though:
1. Pruned nodes can still work for many people (on an existing PC/laptop, so cheap), but with some cut down functionality
2. Yes the chain is growing over time, but the block size limit was set quite conservatively, and generally tech deflation will bring the cost down faster than the chain grows.
3. A big reason for the spike now is more due to AI spiking the costs for things like SSDs
I'd say if you want an archival node with electrum server, the cost is probably more like $450 ish today. But it will come down over time in line with general multi decade trends.
I actually made a bitcoin node cost dashboard to show some of this, see stephanlivera.github.io/node-cost-dashboard/ -
Adam Back reposted
Stephan Livera
@stephanlivera
read this
Stephan Livera
@stephanlivera
I made an explainer page on Bitcoin spam and why it's impossible to stop.
Bitcoin is money, you can't stop spam.
stephanlivera.github.io/Bitcoin-Spam/ -
Adam Back reposted
๐Adam๐
@denverbitcoin
As far as memes go, this is just so good lol.
-
Adam Back reposted
zender โ๏ธ
@zndtoshi
"When I designed Bitcoin, I designed it in such a way as to make future modifications to the consensus rules difficult without near unanimous agreement."
-
Adam Back reposted
zender โ๏ธ
@zndtoshi
"If two developers can fork Bitcoin and succeed in redefining what "Bitcoin" is, in the face of widespread technical criticism and through the use of populist tactics, then I will have no choice but to declare Bitcoin a failed project."
Satoshi Nakamoto
lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-Auguโฆ -
Adam Back reposted
ODELL
@ODELLXYZ
complain less
do more -
Adam Back reposted
Stephan Livera
@stephanlivera
BIP110 debate summed up
-
Adam Back reposted
Alex Waltz
@raw_avocado
Gregory Maxwell responded on reddit to my video about him :D
Turns out blockchain info the most used block explorer in 2013 was using an effectively an SPV wallet. -
Adam Back reposted
Blockstream
@Blockstream
Today, losing your hardware wallet is fine. Your recovery phrase gets you back in.
In a post-quantum signing setup, the device also holds state: a running count of how many times it has signed. That state matters for security.
SHRINCS is designed so that if the device is lost, the recovery phrase loads into a new one and falls back to a path that needs no state at all. -
Adam Back reposted
Stephan Livera
@stephanlivera
You ignored the point about how BIP110 only increases the cost 0.4% and most of the spammer protocols are either unaffected, or they can quickly change to keep spamming.
So no, it won't significantly reduce because of BIP110.
If the spammer protocols die off, its cos the fad died anyway. In which case we didn't need BIP110. -
Adam Back reposted
David Bailey๐ต๐ท $2.0mm/btc is the floor
@DavidFBailey
BIP110 fanatics are angry Iโm spending time mogging their malicious fork.
Weโre one of the largest corporate holders of bitcoin in the world and we own the largest bitcoin media company in the world. Weโre a meaningful economic node and weโre going to defend our asset. We donโt consent to you changing Bitcoin. After 14 years in Bitcoin this is not the first or second or third time weโve had to squash malicious take over attemptsโฆ This is the true origin of toxic maximalism.
The mogging will continue until you fork off and find out. -
Adam Back reposted
Michael Ford
@fanquake
Congrats to @andrew_s_toth for shipping his parallel input fetching work. Pretty clear impact
-
Adam Back reposted
FRANCIS โ๏ธ BULLBITCOIN.COM
@francispouliot_
Our website dac8.com dedicated to fighting back against dac8 is now the 2nd google result when searching for dac8.
Very, very satisfying. -
Adam Back reposted
David Bailey๐ต๐ท $2.0mm/btc is the floor
@DavidFBailey
For those who canโt believe it, here is his public apology. I forgot how egregious the details were and how hypocritical his current stance isโฆ
www.reddit.com/r/Bitcoin/comments/2iuf4s/lukejrs_public_aโฆ -
Adam Back reposted
Blockstream
@Blockstream
Spending on @Liquid_BTC is going near-instant.
0-conf brings safe-to-act-on transfers, now in public beta with a full release around the corner. And with the issuance cap removed, issuers can mint stablecoins and other Issued Assets at real-world scale.
The full Liquid roadmap is in our Q2 update.
blog.blockstream.com/blockstream-quarterly-update-q2-2026/ -
Adam Back reposted
Vortex | BIP448
@theonevortex
> What Lyn seems to be missing is that BIP110 is not a protocol change, but a correction to fix the mess that Core has done. We are getting Bitcoin to be how it was in 2022.
100% false. 110 introduces A NEW consensus rule that never existed before, in addition to that it has a ton of technical issues that I outline here: x.com/theonevortex/status/2020594400955695442
So with zero technical consensus and less than 1% signaling weeks before activation it's clearly DOA.
Vortex | BIP448
@theonevortex
It's strange to start the discussion by ignoring all the fork risk like splitting the network and so fourth but here's a few:
-Protocol/Ledger neutrality - By moving "Standardness" filters into "Consensus" rules Bitcoin ceases to be a neutral settlement layer and starts looking like a curated platform and this sets a precedent where a 55% majority can decide that your valid transaction is "spam" simply because they dislike the use case
-It doesn't actually solve the problem - As Peter Todd demonstrated these filters are easily bypassed as he successfully embedded the entire 6,000-word text of BIP 110 into a single transaction by fragmenting the data across multiple 256-byte PUSHDATA elements and 83-byte OP_RETURNs so this proves the fork doesn't stop data it only increases the transaction fee "tax" for users
-Incentivizes Centralizing BlockSpace Market - Capping the public relay at 83 bytes forces high-volume data users to bypass the P2P network and instead pay large mining pools directly via private APIs to include "illegal" non-standard data which creates a private blockspace market that small home-node miners cannot see or profit from
-Risk of confiscation / disruption to backwards compatibility - As Gregory Maxwell noted Bitcoin nodes have no "global state" of pre-signed transactions so if a user has a multi-year inheritance plan or a "Vault" emergency exit signed offline that uses a 500-byte script or an OP_IF branch BIP 110 welds that exit shut and since the transaction is now consensus-invalid the funds are effectively confiscated for the duration of the fork
-Anti-Scaling (Kills eltoo/ln-symmetry) - BIP 110 explicitly invalidates the Taproot Annex which directly blocks the ln-symmetry upgrade which is the industry's best hope for a Lightning Network that dramatically reduces the need for constant watchtower monitoring and enables simpler multi-party channels
-Creates UTXO bloat - BIP 110 incentivizes spammers to hide data inside fake addresses/UTXOs (like multisig-encoded data) and while an OP_RETURN can be ignored by a lean node, a fake UTXO must be tracked by every node forever so BIP 110 intended to "save" nodes but actually creates a more expensive permanent burden on them
-Breaks Miniscript & Vaults - Miniscript is the industry standard for writing readable secure smart contracts (used for inheritance, multi-party escrow, timelocked recovery) and relies heavily on OP_IF to branch between conditions so by banning OP_IF in Tapscripts BIP 110 effectively breaks Taproot-based custody setups that represent the direction the entire industry is moving
-Lobotomizes BitVM - BitVM is one of very few viable paths to trustless Layer 2 bridges and requires deep "Taproot Trees" (Merkle paths) to verify computation and a 257-byte limit caps the tree depth at roughly 7 levels (128 leaves) when BitVM protocols often require thousands of leaves to function
-Loss in fees for miners - If you filter out the highest paying transactions because you don't like their content you are effectively asking miners to take a pay cut which could lower the "hash price" and as block subsidy continues to halve transaction fees become increasingly critical to security
-Rushed Timeline / Governance Precedent - BIP 110 activates unconditionally by September 2026 regardless of support with early activation possible at just 55% signaling within a tiny 3-month window and this "emergency" style of governance is a radical departure from Bitcoin's traditional 90%+ consensus model, if rushed "emergency" consensus changes become normalized that governance precedent is permanent even if the technical changes expire -
Adam Back reposted
Blockstream
@Blockstream
An unconfirmed transaction isn't lost, it's waiting its turn in the mempool, and the fee you paid is its place in line.
In a hurry? Bump the fee in the Blockstream app to move up the queue. -
Adam Back
@adam3us
under-rated tweet. follow @csuwildcat
(on the filter/110 soon forking off and fizzling)
Daniel ษrrr
@csuwildcat
Simple lies and grand promises that fanciful fixes can solve intractable issues and make alcolytes into heroes are a powerful elixir for those given to belief in comfortable narratives over uncomfortable truths.
-
Adam Back reposted
Daniel ษrrr
@csuwildcat
Simple lies and grand promises that fanciful fixes can solve intractable issues and make alcolytes into heroes are a powerful elixir for those given to belief in comfortable narratives over uncomfortable truths.
-
Adam Back reposted
Mith
@mith_os
lmfaooooooo ๐คฃ๐คฃ
you have to drop your lightning address, i need to show some love to a fellow autistic person -
Adam Back reposted
Coinjoined Chris โก
@coinjoined
Cypherphunk Summer is imminent.
Fork around and find out. -
Adam Back reposted
Vortex | BIP448
@theonevortex
The "immune response" was never about filters it was about rejecting rushed consensus changes with weak support. That's what UASF and NO2X were.
Filtering lived at the policy layer on purpose b/c policy is voluntary and every node can tune it w/o forking the network.
110 takes an aesthetic preference and welds it into consensus at 55% with a flag day so it's not really a continuation of that culture it's actually the exact thing that culture existed to fight. Plus it doesn't even come close to having technical consensus due to the issues I outlined in previous tweet.
And Core v30 was released as harm reduction as I've explained here: x.com/theonevortex/status/2017628088495182042 and here x.com/theonevortex/status/2023110044905353313 and BitMEXResearch explains here x.com/BitMEXResearch/status/2022069199036690815 and here x.com/BitMEXResearch/status/2024952265719611458 and as orangesurfbtc explains here x.com/OrangeSurfBTC/status/2023094761310302514 and murch explains here x.com/murchandamus/status/2022930707820269670 and john explains here x.com/lightcoin/status/1977040086245294333 and core explains in their blog post here bitcoincore.org/en/2025/06/06/relay-statement/
Not to mention that 110 literally doesn't slow down or stop any spam as every single spamming protocol has already updated to be 110 compliant.
If you're serious about understanding the debate make sure to read the links.
light ๐
@lightcoin
Thread to debunk any Core v30 FUD that may be posted if "bad" data gets embedded in a large OP_RETURN.
If that happens, remind the fudsters that before Core v30... ๐งต -
Adam Back reposted
Stephan Livera
@stephanlivera
I made an explainer page on Bitcoin spam and why it's impossible to stop.
Bitcoin is money, you can't stop spam.
stephanlivera.github.io/Bitcoin-Spam/ -
Adam Back reposted
Daniel ษrrr
@csuwildcat
Most notable extractions from my debate with Mechanic:
1. Admitted spam isn't a realistic storage cost threat to node operation (block size ensures it)
2. Despite spammers already proving they'll mod spam to work w/ 110, he went on record that his crew would not keep forking to play whackamole <-- this is really interesting, because unless they do, it starts looking like this is less and less about actually stopping spam, and more and more like something else. (which many have suspected)
semi-normal | french ctv
@crypto_0ptimist
@csuwildcat is absolutely demolishing this debate.
x.com/i/spaces/1RJjppqPPvRKw -
Adam Back reposted
DMND
@DMND_Sv2
At DMND, miners can signal any bit, for any upgrade. Signaling on our pool happens at the individual miner level through Stratum V2 Job Declaration. This is not a permission we grant โ it is built into the protocol, and we will not police it.
However, signaling and chain selection are separate things.
DMND is a Bitcoin mining pool. We mine on the chain with the most accumulated proof-of-work under the consensus rules of the economic majority. We will not direct hashrate to a minority chain that requires signaling, unless industry-wide consensus for the upgrade has already been established.
In August, nodes enforcing BIP110 will begin rejecting non-signaling blocks. Currently, only a small minority of blocks signal support. If that does not change, enforcing nodes will separate themselves from the network onto a minority chain. Miners building on that chain will not be mining Bitcoin. They will be paid in a coin with no exchange liquidity and no settlement infrastructure โ rewards that cannot be sold, spent, or used to cover operating costs.
For any mining operation, that is a direct financial loss.
DMND mines Bitcoin. -
Adam Back reposted
alejandro de la torre
@bitentrepreneur
You can signal any bit you want on DMND, we're not checking. But the pool mines Bitcoin. I'm not sending anyone's hashrate to a chain where the rewards can't pay a power bill
DMND
@DMND_Sv2
At DMND, miners can signal any bit, for any upgrade. Signaling on our pool happens at the individual miner level through Stratum V2 Job Declaration. This is not a permission we grant โ it is built into the protocol, and we will not police it.
However, signaling and chain selection are separate things.
DMND is a Bitcoin mining pool. We mine on the chain with the most accumulated proof-of-work under the consensus rules of the economic majority. We will not direct hashrate to a minority chain that requires signaling, unless industry-wide consensus for the upgrade has already been established.
In August, nodes enforcing BIP110 will begin rejecting non-signaling blocks. Currently, only a small minority of blocks signal support. If that does not change, enforcing nodes will separate themselves from the network onto a minority chain. Miners building on that chain will not be mining Bitcoin. They will be paid in a coin with no exchange liquidity and no settlement infrastructure โ rewards that cannot be sold, spent, or used to cover operating costs.
For any mining operation, that is a direct financial loss.
DMND mines Bitcoin. -
Adam Back reposted
-
Adam Back reposted
Vortex | BIP448
@theonevortex
110 is nothing more than a power grab, it has a huge amount of technical issues that I outline here that the 110 side has yet to debunk:
Vortex | BIP448
@theonevortex
It's strange to start the discussion by ignoring all the fork risk like splitting the network and so fourth but here's a few:
-Protocol/Ledger neutrality - By moving "Standardness" filters into "Consensus" rules Bitcoin ceases to be a neutral settlement layer and starts looking like a curated platform and this sets a precedent where a 55% majority can decide that your valid transaction is "spam" simply because they dislike the use case
-It doesn't actually solve the problem - As Peter Todd demonstrated these filters are easily bypassed as he successfully embedded the entire 6,000-word text of BIP 110 into a single transaction by fragmenting the data across multiple 256-byte PUSHDATA elements and 83-byte OP_RETURNs so this proves the fork doesn't stop data it only increases the transaction fee "tax" for users
-Incentivizes Centralizing BlockSpace Market - Capping the public relay at 83 bytes forces high-volume data users to bypass the P2P network and instead pay large mining pools directly via private APIs to include "illegal" non-standard data which creates a private blockspace market that small home-node miners cannot see or profit from
-Risk of confiscation / disruption to backwards compatibility - As Gregory Maxwell noted Bitcoin nodes have no "global state" of pre-signed transactions so if a user has a multi-year inheritance plan or a "Vault" emergency exit signed offline that uses a 500-byte script or an OP_IF branch BIP 110 welds that exit shut and since the transaction is now consensus-invalid the funds are effectively confiscated for the duration of the fork
-Anti-Scaling (Kills eltoo/ln-symmetry) - BIP 110 explicitly invalidates the Taproot Annex which directly blocks the ln-symmetry upgrade which is the industry's best hope for a Lightning Network that dramatically reduces the need for constant watchtower monitoring and enables simpler multi-party channels
-Creates UTXO bloat - BIP 110 incentivizes spammers to hide data inside fake addresses/UTXOs (like multisig-encoded data) and while an OP_RETURN can be ignored by a lean node, a fake UTXO must be tracked by every node forever so BIP 110 intended to "save" nodes but actually creates a more expensive permanent burden on them
-Breaks Miniscript & Vaults - Miniscript is the industry standard for writing readable secure smart contracts (used for inheritance, multi-party escrow, timelocked recovery) and relies heavily on OP_IF to branch between conditions so by banning OP_IF in Tapscripts BIP 110 effectively breaks Taproot-based custody setups that represent the direction the entire industry is moving
-Lobotomizes BitVM - BitVM is one of very few viable paths to trustless Layer 2 bridges and requires deep "Taproot Trees" (Merkle paths) to verify computation and a 257-byte limit caps the tree depth at roughly 7 levels (128 leaves) when BitVM protocols often require thousands of leaves to function
-Loss in fees for miners - If you filter out the highest paying transactions because you don't like their content you are effectively asking miners to take a pay cut which could lower the "hash price" and as block subsidy continues to halve transaction fees become increasingly critical to security
-Rushed Timeline / Governance Precedent - BIP 110 activates unconditionally by September 2026 regardless of support with early activation possible at just 55% signaling within a tiny 3-month window and this "emergency" style of governance is a radical departure from Bitcoin's traditional 90%+ consensus model, if rushed "emergency" consensus changes become normalized that governance precedent is permanent even if the technical changes expire -
Adam Back reposted
David Bailey๐ต๐ท $2.0mm/btc is the floor
@DavidFBailey
BIP110 is an embarrassment. The most incoherent, unpopular, intellectually and morally bankrupt soft fork proposal in Bitcoin history.
-
Adam Back reposted
Vortex | BIP448
@theonevortex
Your latest article was once again easily debunked since you clearly have only an extremely basic understanding of how bitcoin works:
> Vortex claims above โ[BIP]110 does not stop or slow down any spamโ. This is such a disgusting and blatant lie that the data spam apologist camp keeps repeating over and over again.
This is 100% false, literally every single spam app has updated their software to be 110 compliant.
> BIP110 works as a charm and that is proven on at least 2 places.
Not even a little bit accurate. You cited two sources as proof and they contradict each other on the exact claim you're making.
Source 1 claims zero false positives, 100% of Rule 7 catches were inscriptions, "zero collateral damage." Source 2 says 81.1% of blocked transactions classify as spam. That means by your own second source roughly 19% of what BIP-110 blocks does NOT classify as spam, and across 1.2 billion transactions that is an enormous absolute number of non-spam transactions caught. A 0% collateral claim and a ~19% collateral claim aren't corroboration, they're a methodological dispute you mistook for consensus.
The block weight numbers disagree too. Source 1 says 36% of block space filtered, Source 2 says 4.93% of post-inscription block weight. And note what 4.93% actually means: the transactions BIP-110 targets are under 5% of block weight. That's the emergency justifying Bitcoin's first consensus downgrade.
More fundamentally, both are backtests. They replay transactions crafted before the rules existed and count matches. Of course a filter catches the patterns it was written against. A BIP-110-compliant data embedding transaction already exists, verified on regtest against the BIP-110 implementation itself with a published reproducible script, and the compliant version came out LARGER with the data pushed into outputs nodes store in the UTXO set forever instead of prunable OP_RETURN.
That is what "does not stop or slow down spam" means. The data still goes in, bigger and less prunable. Your backtests don't touch that argument and your sources can't even agree with each other.
> Soft forks like BIP110 historically always involved lots of debating,
Yes and they also involve lots of testing which 110 has not gone through, not only that but they already had to request the help of several core developers on several occasions due to the incompetence of dathom who essentially vibe coded the entire client.
> Bitcoin Coreโs highly controversial data spam-friendly direction with their October 2025 v30 release.
Bitcoin core didn't take a spam-friendly direction, this is a lie, they simply changed a relay policy filter default that anyone can configure on their own node.
> And this poor lad called Vortex apparently still hasnโt come across my previous article โStop Being Retarded, Bitcoiners, Eat A Bag Of Dicksโ.
Not only did I read the terrible writing I replied BOTH on twitter and medium with the only comment on the page, you can read right?
> To add, the as we speak still low initial miner signaling (~1% in recent days, against ~15% full nodes signaling) shows that BIP110 is not steamrolling the Bitcoin network
Yes because literally nobody is signaling for this terrible software, it's still less than 1%, it literally never even hit 1% signaling yet despite activation only being weeks away.
> This is, of course, backwards.
No actually, You're equivocating on "centralize" and the argument dies without it.
Rich users bidding up an open fee auction is not market centralization, anyone can outbid them, that's the neutral market working. Centralization means template construction, fee capture, and transaction access concentrating in fewer hands. Filters demonstrably cause that: filtered demand routes out-of-band to direct miner submission (Slipstream exists for exactly this reason), which advantages large miners and starves small pools on public relay. Pulling that flow back into the public mempool was the stated rationale for Core v30's OP_RETURN change. Cause and effect on record, opposite direction to yours.
BIP-110 adds a second vector: 55% miner signaling makes miners the arbiters of which paying demand counts as legitimate. Consensus-level legitimacy gatekeeping of demand is blockspace market centralization by definition.
Also, OP_RETURN is prunable. The filter's demonstrated displacement effect pushes data into UTXO set outputs your node stores forever, ~95% more permanent burden for ~11% more spammer fees. Your node runner argument is an argument against the filter.
> BIP110 restores the balance that existed up till early 2023 by enforcing tighter limits on new UTXOs/outputs (scriptPubKeys โค34 bytes except OP_RETURN โค83 bytes; data pushes/witness items โค256 bytes) while grandfathering pre-activation UTXOs
100% false. Point to the block height where a 34-byte scriptPubKey cap or a 256-byte witness element limit was consensus. You can't, because they never existed. Consensus allows 10,000-byte scripts and 520-byte elements, and OP_RETURN size was always relay policy. "Restores the balance" means inventing rules Bitcoin never had and calling it restoration. What existed pre-2023 was an absence of demand, not a ruleset.
Your own historical precedent is the strongest evidence against you. 2014: Core cut OP_RETURN standardness to 40 bytes to discourage embedding, Counterparty moved its data into bare multisig, UTXO set bloat got worse, and OP_RETURN was kept as harm reduction because devs concluded you can only steer embedding, not stop it. Same displacement the BIP-110-compliant demo just showed again a decade later.
Satoshi never once used consensus rules to filter content. Relay defaults and persuasion, that's it, from the guy who put the Times headline in the genesis block. You're citing him for a mechanism he never touched.
And "subsidised storage" is backwards: the witness discount prices data by its real node cost, output data burdens the UTXO set forever while witness data doesn't. Inscribers pay full market rate under correct pricing. Your rules push data back into the expensive place.
> On piling multiple systems/data into one chain (BitDNS discussion, December 10, 2010
Real quotes, wrong conclusion. All three show Satoshi declining to add features or telling other systems to use separate chains. Zero of them show him forbidding data via consensus, and your own third quote contains his actual remedy: "a separate system parallel to the bitcoin network." Build elsewhere is not make-invalid.
Here's the fact that settles it: Satoshi had unilateral consensus power and used it, disabling opcodes in 2010 over security bugs, during the same period as your quotes. He never aimed it at data. He also documented his anti-spam mechanism explicitly: transaction fees as the flooding defense. Satoshi's answer to unwanted transactions was pricing, not filtering. You're quoting the man whose revealed preferences support my argument.
And the BitDNS thread you cite ends with Satoshi proposing merged mining, which embeds other chains' commitments into Bitcoin's coinbase. His solution to "don't pile systems into one chain" was a form of data embedding.
Your quote 2 describes users limiting the SIZE of the chain, a uniform limit on everyone. That maps to a block weight reduction soft fork, not to a filter that keeps blocks the same size while selecting allowed byte patterns. Stand on Satoshi consistently or don't stand on him at all.
> LN-Symmetry (Eltoo) and related covenant improvements are advanced Layer 2 features.
OP_IF in a tapscript is a spending condition, not "arbitrary data." Vaults, BitVM and ln-symmetry ARE the on-chain enforcement, and Lightning only keeps data off-chain because those scripts stay valid, so reclassifying money logic as data to excuse filtering it just proves the filter can't tell the difference. And "temporary" has no precedent because there has never been an expiring consensus rule in Bitcoin's history, so name one. The reassessment clause is circular since legitimate contracts can't "emerge" while consensus-invalid, and a rule renewable yearly by 55% signaling isn't a pause, it's an indefinite freeze with annual review that nobody funds multi-year R&D under.
> This is similar to the previous point: we are talking about temporary restrictions on certain tapscript patterns (e.g., OP_IF/NOTIF in executed contexts and large structures).
Your sources don't even agree here: one claims zero false positives precisely because no legitimate tapscript OP_IF contracts exist on mainnet, and now wallets "may need updates," both can't be true. And "may need updates" is what breakage is called by the side that caused it, because when consensus invalidates scripts that working software emits that's the definition of breaking compatibility.
The tapleaf workaround isn't free either since flattening mixed threshold policies into separate leaves blows up leaf count, depth and control block size, which BIP110 also limits by your own account, so one rule pushes wallets into the structure another rule punishes. Grandfathering only covers coins already on-chain, not vault and recovery protocols whose pre-signed continuation transactions create new outputs, and since deleting keys after pre-signing IS the vault security model those setups can't adapt. Consensus changes ship with tooling and test vectors settled up front like Taproot did, not with "guidance will be provided."
> First of all, neutrality doesnโt mean "anything goes forever in any shape or form".
Point to the protocol field that marks a transaction "native." There isn't one, everything BIP110 filters is consensus-valid and fee-paying, so "native" means "transactions I approve of" and your no-censorship claim is circular. Your own source says only 81.1% of blocked transactions classify as spam, so "no native transaction is ever touched" is refuted by your own data. Bitcoin's limits have always been uniform, hitting every transaction identically regardless of content, and you conceded the difference yourself: "optional policy" to consensus. Optional was the neutral part.
> No, not necessarily. And even if a split is happening, it will be shortlived, not supported by anyone and it is to be expected that the minority split will be quickly abandoned.
SegWit required 95% and Taproot 90% because soft fork safety needs an enforcing majority overwhelming enough to rapidly orphan non-compliant blocks, and signaling isn't enforcement, miners have false-signaled before. At 55% you get persistent reorgs with old nodes flip-flopping between chains, and 2017 teaches the opposite lesson anyway since BIP148 was split-courting brinkmanship bailed out by 90%+ hashrate compliance.
Now apply your own numbers: 1% miners, 15% nodes, and a mandatory window where BIP110 nodes reject every non-signaling block, meaning at current support they orphan ~99% of blocks and follow a ~1% hashrate chain with multi-hour block times, rejected by the economic majority. Your "shortlived minority split, supported by no one, quickly abandoned" is an accurate forecast of your own chain, and nobody needs to request exchange listings because a persistent chain with divergent rules is a separate coin by definition.
> No. Again an argument where Vortex has it backwards. The actual attack has been ignited by Bitcoin Core.
Your threshold defense is a confession. High thresholds don't "reflect less contention," they exist BECAUSE contention is dangerous, the threshold is the safety margin against a persistent split, and contention is exactly when the other 45% of hashrate really will keep mining the old rules. So "higher thresholds stall needed fixes" translates to "the safety mechanism keeps stopping us, so we lowered it," making BIP110 the first activation design in Bitcoin's history built to defeat contention rather than require its absence.
And 55% of what, miner signaling? Bare miner majority deciding consensus rules is the exact model the 2017 UASF movement existed to reject, users decide rules and miners order transactions, now inverted to "55% of hashrate suffices over user objection" at 15% nodes and 1% miners by your own count. The Luke and Szabo screenshots criticize a relay default anyone can override today and contain nothing about activation safety, so point 7 stands unanswered, appendix included.
> BIP110 doesnโt claim to eliminate all spam forever as spammers can indeed fragment data, use other attack vectors, or wait for expiry of the BIP.
Your point 1 called "BIP110 does not stop or slow down spam" a disgusting and blatant lie, and your point 8 opens by agreeing spammers "can indeed fragment data, use other attack vectors, or wait for expiry." That was the claim, you've ended your rebuttal by conceding the sentence you began it calling a lie. "Raises the bar" doesn't survive the math either, ~11% more spammer cost for ~95% more permanent node burden with the compliant variant demonstrably larger than the original. The "already working" tweet loses both ways since inscription decline is a market-wide cycle collapse no 1%-signaling proposal gets credit for, and spammers "making amendments" IS the adaptation thesis, the failure mode cited as proof of success.
The 85% of nodes running clients without BIP110 already expressed their position in software, silence isn't mandate, and seven years of free BSV blockspace with zero migration settles "they'll just leave." Notice the pattern: activation is success, failure strengthens the protocol, spam down proves it works, spam adapting proves maintenance works. A theory every outcome confirms isn't engineering, it's faith.
Summary:
See insults don't help your case, neither does your lack of basic knowledge of how bitcoin works.
Here's the scorecard, sources that disagree with each other cited as dual proof. A "restoration" of consensus rules that never existed. Satoshi quoted for a mechanism he never once used while his actual anti-spam tool, fees, argues my side. Breakage conceded as "updates," neutrality conceded as "optional to consensus," split risk conceded as "designed for contention," and the original claim you called a disgusting lie conceded verbatim in your own closing point.
Every substantive argument you made either contradicted your sources, contradicted your other arguments, or contradicted itself. I almost didn't even need to debunk this because this entire post is basically a confession of having no idea what's going on. -
Adam Back reposted
Tone Vays
@ToneVays
No retard, what he says in the video is correct, he even said at 38 minutes that Segwit had Consensus before Bip148, but he is out here saying it didn't!
-
Adam Back reposted
Coinjoined Chris โก
@coinjoined
What's the LNAV (Liar to net asset value) of Ocean?
-
Adam Back reposted
โ TotalษuzzKit
@TotalBuzzKit
That was a real, powerful attack. Compared to this, the people behind #bip110 look like a bunch of children running around with pink party balloons in hand, pretending they are Mace Windu.
Just kick back and watch the (shit)show.
bip110.com
2/2 -
Adam Back reposted
Natalie Brunell โก๏ธ
@natbrunell
In Part 2 of our interview, @adam3us dives into Core and Knots, spam on Bitcoin, and why censorship resistance is critical to Bitcoinโs future.
Available wherever you stream your podcasts.This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Vincent (Cryptolution) ๐
@cryptolution101
๐จJUST IN: During @natbrunell's interview, @LynAldenContact pushed back on the narrative that BIP-110 is needed to stop "SPAM" (Ordinals/#runes), arguing it has been framed as an existential crisis for Bitcoin when the technical evidence doesn't support that claim.
Full Interview: www.youtube.com/watch?v=lIg0G0z2KkYThis media couldn't be displayed. See it on the original post. -
Adam Back reposted
FractalEncrypt โ/21M
@FractalEncrypt
"It is this spectacular, seemingly unbreakable power found in Bitcoin that is the very proof of the immanence of a God who loves humanity so spectacularly that he left a secret for us to discover that is the power of cryptography in our fallen world."
- @Erikcason -
Adam Back reposted
FractalEncrypt โ/21M
@FractalEncrypt
"Through the correct implementation of the ceremony, we create a divine mathematical proof which no temporal power may violate with any known or possible means."
- @Erikcason
I made a quick 5-page graphic novel adaptation of a few pages of my favorite chapter in CryptoSovereignty "The Oath of the Machines."
Its extremely potent prose, so be careful with this, and ENJOY! -
Adam Back reposted
FractalEncrypt โ/21M
@FractalEncrypt
"When the rituals of cryptography are exercised with the same piousness as a gnostic priest, what cryptography renders is prophetic: the encryption becomes unbreakable by any known means and is verified by the holy blessings of math itself."
-@Erikcason -
Adam Back reposted
Wicked
@w_s_bitcoin
I donโt see this as a gamble because Iโm 100% sure BIP-110 wonโt succeed. Iโm simply looking for supporters who have the same conviction. Itโs all part of the free market and part of consensus building. Putting your money where your mouth is.
-
Adam Back reposted
D E C E N T M O N E Y
@decentmoney2009
Core devs actually improving Bitcoin rather than LARPing with a sub-community culture war over nothing
Knots people should take notes
l0rinc
@L0RINC
๐ LFG ๐ @andrew_s_tothโs parallel input prevout fetcher was just merged into Bitcoin Core for the upcoming v32 - after 2+ years and 1000+ review comments.
IBD is getting *even* faster \:D/
Thank you for the persistence, Andrew: this is what open-source collaboration should look like! github.com/bitcoin/bitcoin/pull/35295 -
Adam Back reposted
David Bailey๐ต๐ท $2.0mm/btc is the floor
@DavidFBailey
I donโt think people understand the stakes of what the BIP-110 attackers just attempted. Itโs not a software update, itโs a forced takeover. If a contentious 51% attack successfully seized control of Bitcoinโs protocol development and crowned one developer king it would be the single biggest crisis in Bitcoin history and millions of bitcoins would be sold by longtime holders. This would cause a real price crash, not a little bear market. Hundreds of millions of innocent/unaware users would be financially devastated. All the credibility Bitcoin had built in the world would be wiped out. Attacks on consensus are playing with a nuclear bomb.
Fortunately bitcoin works like we thought it did and this attack never stood a chance. Future attacker take note, consensus does not bend to your will. -
Adam Back reposted
Vortex | BIP448
@theonevortex
Technical objections against BIP-110 that's still looking for refutation:
mine: x.com/theonevortex/status/2020594400955695442
lopp: x.com/lopp/status/2025930143143756262
rearden: x.com/reardencode/status/2022042011810009244
kevin: x.com/KLoaec/status/2021528510385254600
Giacomo: x.com/giacomozucco/status/2020120525796757720
supertestnet: x.com/SuperTestnet/status/2022489685529104574
ajtowns: x.com/ajtowns/status/2021693536790622240
Super Testnet
@SuperTestnet
This post is unavailable. See it on X. -
Adam Back reposted
Brandon
@BranBTC
Another thing Iโm learning from this BIP 110 situation is that weโve done a terrible job teaching people what it means to run a node:
Running a node is not some benevolent service you do for the network. It is a self-interested act to โdonโt trust, verifyโ the blockchain. Bitcoinโs genius is that it aligns incentives so that nodes reach consensus on the history and next block.
As a Bitcoin user, I literally DGAF whether you run a node or not. As a Bitcoin educator, however, I encourage you to run a node because that way you donโt rely on a trusted 3rd party to send/receive transactions.
Is it good for Bitcoinโs decentralization that more people run nodes? Of course. Does Bitcoin need you to run a node in order to function? No.
So when BIP 110ers threaten theyโre gonna stop running a node, I see it as if a fellow refugee in a life raft is threatening to pop his own life vest. I think itโs a dumb move, and I prefer you dont hurt yourself, but I am personally unaffected by your decision.
Hope that helps you understand the โgame theoryโ you keep saying is about to kick in at any moment! -
Adam Back reposted
Tone Vays
@ToneVays
Is this delusion ? There is literally just ONE person I remember from 2017 days on his side and that's Luke. Zsabo ocationaly & the space cat at the tail end cause he needed money to fight Craig Wright. That's the list!
EVERYONE ELSE who were pro Segwit/Bip148 with a following are anti Bip110 or avoid the topic like the plague in fear of losing business. Everyone technical is against it! I can name close to 100 people!
- he does know 90% of Twitter accounts with #bip110 in the profile name are bots right ๐คฆ
.
@GrassFedBitcoin
"BIP110 doesn't have consensus" is their favorite today.
I know. I don't care.
This will be my second time supporting a soft fork that doesn't have consensus, and it has *more support* than the first one.
Also, if you think Bitcoin can exist in a hostile environment but that everyone has to agree for it to be allowed to defend itself you're an idiot or a saboteur. -
Adam Back reposted
Stephan Livera
@stephanlivera
Some of the BIP110 camp are now trying to rewrite history and say that the UASF they are doing now is like the UASF of 2017 and that SegWit needed it to get it over the line.
But I believe they are rewriting history to suit their own narrative. By 2017 SegWit had clear technical consensus and most of the nodes on the network were running code that would support SegWit in Core v.13, and the real hold up was basically BitMain thanks to covert ASICboost. So while the 2017 UASF might have helped push it over the line, it was from a position where SegWit had consensus.
In contrast, BIP110 does NOT have consensus and it is widely criticised for various technical and philosophical flaws. -
Adam Back reposted
Stephan Livera
@stephanlivera
Core devs working to make initial block download faster
l0rinc
@L0RINC
๐ LFG ๐ @andrew_s_tothโs parallel input prevout fetcher was just merged into Bitcoin Core for the upcoming v32 - after 2+ years and 1000+ review comments.
IBD is getting *even* faster \:D/
Thank you for the persistence, Andrew: this is what open-source collaboration should look like! github.com/bitcoin/bitcoin/pull/35295 -
Adam Back reposted
l0rinc
@L0RINC
Looks like the link at the end of the post was collapsed: github.com/bitcoin/bitcoin/pull/35295
TLDR: UTXO lookups are fetched into memory in parallel during block connection, speeding up IBD and steady-state validation considerably. -
Adam Back reposted
l0rinc
@L0RINC
๐ LFG ๐ @andrew_s_tothโs parallel input prevout fetcher was just merged into Bitcoin Core for the upcoming v32 - after 2+ years and 1000+ review comments.
IBD is getting *even* faster \:D/
Thank you for the persistence, Andrew: this is what open-source collaboration should look like! github.com/bitcoin/bitcoin/pull/35295 -
Adam Back reposted
MIRA
@MiraReserve
We all want the best for bitcoin but some of us understand that we have to reach CONSENSUS, because you know, Bitcoin was made specifically to RESIST every random group with an idea from forking it. This resistance is why BTC is at $62K and will be millions one day. Otherwise = 0
-
Adam Back reposted
l0rinc
@L0RINC
Bip110 doesn't affect spam in any meaningful way - it would just set a horrible precedent that we're forbidding usage that's not harmful because people think it's stupid. It *is* stupid, doesn't matter, it's not dangerous.
-
Adam Back reposted
MARS SPITS BARS ๐ฅ
@marsspitsbarz
Talkin shit to @GrassFedBitcoin on my jet ski
-
Adam Back reposted
Blockstream
@Blockstream
More on how @blksresearch contributes to Bitcoin's cryptographic foundations.
blog.blockstream.com/blockstream-research-brings-libsecp2โฆ -
Adam Back reposted
Rich Lassiter, MD ๐ โฟitcoin
@RichLassiterMD
Are you aware that we know how to read?๐คฃ๐คฃ๐คฃ
ODELL
@ODELLXYZ
are you aware that we know how to read?
-
Adam Back reposted
Wicked
@w_s_bitcoin
The knotzi movement will probably go down as one of the most retarded periods in Bitcoinโs history.
If you made it through without falling for Luke & Mechanicโs rhetoric, congratulationsโฆyouโre one step closer to the final boss.
If you did fall for it, youโre probably ngmi. -
Adam Back reposted
Michael Ford
@fanquake
Contains fixes for a -privatebroadcast IP address leak, as well as leveldb causing excessive disk operations. Along with other minor fixes, including compatibility with the latest version of Boost (1.91.0).
Bitcoin Core Project
@bitcoincoreorg
Bitcoin Core v31.1 was released!
It is available from: bitcoincore.org/en/download/
Release notes: bitcoincore.org/en/releases/31.1/ -
Adam Back reposted
ODELL
@ODELLXYZ
nope, thats a lie
existing users do not need to actively respond to a minority fork attempt
otherwise anyone could fork at any time and force the entire network to respond with an update, which would be retarded -
Adam Back reposted
Blockstream
@Blockstream
Satoshi chose secp256k1 for Bitcoinโs cryptography.
@n1ckler and @blksresearch are among the co-maintainers of libsecp256k1, the library every Bitcoin node runs to implement it.
Researching what comes next is a natural extension of that work.This media couldn't be displayed. See it on the original post. -
Adam Back reposted
Steve
@steverabinow
BIP110 does nothing to reduce the risk. Your Dear Leader is lying to you.
-
Adam Back reposted
Coinjoined Chris โก
@coinjoined
I wonder why nobody takes Luke seriously anymore
-
Adam Back reposted
ODELL
@ODELLXYZ
i think part of the reason you have had trouble getting consensus for your fork is because you claim everyone who disagrees with you is a pedo
minority soft forks pushed through without consensus will result in a chain split -
Adam Back reposted
Stephan Livera
@stephanlivera
Spam arguments are big now, for a bit of fun I made a Bitcoin Node Cost Tracker/Dashboard stephanlivera.github.io/node-cost-dashboard/
-
Adam Back reposted
HeroGamerโก
@herogamer21btc
This is your last chance.
After this there is no turning back.
You take the ๐ต Blue pill, be the Retard.
You take the ๐ด Red pill, not be the Retard.
Remember, all Iโm offering is the truth, nothing more. -
Adam Back reposted
Alex Thorn
@intangiblecoins
bitcoiners need to use the chain. simple economic activity will price out any spam
the fee is the filter -
Adam Back reposted
Stephan Livera
@stephanlivera
Also see @lopp's article pointing out security and development issues with Knots blog.lopp.net/knot-a-serious-project/
-
Adam Back reposted
Coinjoined Chris โก
@coinjoined
Node runners are perfectly capable of choosing to change their relay policy if they don't want the defaults
-
Adam Back reposted
Fernando Nikoliฤ ๐ฆ๐ท ๐
@basedlayer
NEVER DELETING THIS APP
-
Adam Back reposted
Wicked
@w_s_bitcoin
Lol thatโs exactly why youโve fallen for their rhetoric. Theyโre lying about BIP-148โs history because they have nothing left to do but to lie.
-
Adam Back reposted
Seth For Privacy
@sethforprivacy
Be forewarned if youโre using OCEAN for mining that youโll be automatically forced into signaling for the BIP 110 fork if you donโt change your stratum endpoint in a week ๐ซ
The irony of forcing their miners to signal for 110 and abusing their centralized power as pool operators is off the charts ๐คฆโโ๏ธ
OCEAN
@ocean_mining
Today, OCEAN is launching two additional Stratum endpoints.
Weโve heard from miners who want a simple way to express support/readiness for BIP110 in their blocks, and weโre making that available.
OCEAN has added two new Stratum endpoints:
โข bip110.mine.ocean.xyz port 3110
โข no-signal.mine.ocean.xyz port 3000
The existing endpoint (mine.ocean.xyz) will switch to signaling BIP110 in 1 week (July 15th).
DATUM remains the main way OCEAN miners build blocks today, giving miners full control over block construction including the ability to signal directly in the blocks they find.
This update simply adds an option to signal for miners who are unable to use DATUM or who need a failover.
At OCEAN, we believe miners should have choice in how they participate in the network.
If youโd like your hashpower to participate in signaling, youโre welcome to join OCEAN. Itโs permissionless, non-custodial, and takes just minutes to get started.
Setup details ๐
If you're not using DATUM and you want to signal for BIP110, please switch your pool to stratum+tcp://bip110.mine.ocean.xyz port 3110.
If you leave stratum+tcp://mine.ocean.xyz port 3334 as your pool, this will switch to signaling on July 15th.
If you do not wish to signal for BIP110, you can switch to stratum+tcp://no-signal.mine.ocean.xyz port 3000 before July 15th.This media couldn't be displayed. See it on the original post. -
Adam Back reposted
MAGS ๐โ๏ธ๐
@Crypto_Mags
The BIP 110 movement has boiled down to "but think of the children", which is not an effective strategy with Bitcoiners that are sick of this type of government overreach
-
Adam Back reposted
Michael Saylor
@saylor
After a decade of blockspace fears and non-monetary-use panics, Bitcoin still has no spam problem. Fees are 1 sat/vB: anyone can move any amount globally with immediate processing for ~$0.30. The free market has always solved Bitcoinโs blockspace challenges. $BTC
-
Adam Back reposted
BULLBITCOIN.COM
@BULLBITCOIN_
JOIN THE FIGHT. Read it, share it.
The full set of facts, figures, official sources and analysis, in French, English and other European languages, is below ๐
dac8.com -
Adam Back reposted
bizzy hodlz
@byronhambly
Called it
x.com/ocean_mining/status/2074825828731342880
bizzy hodlz
@byronhambly
So eventually Ocean will provide this dogshit client for their templates right?
The real question is will they also force hashers to use it? -
Adam Back reposted
Mr.Hodl
@MrHodl
You can't preach "decentralization" out one side of your mouth and flip the default on your main pool endpoint to signal BIP 110 without asking. You spent years bragging about how Ocean gives miners "sovereign" blocks through DATUM. You said you're only a miner if you're building your own templates. But now the default on the regular Stratum pool is switching to signal the soft fork on July 15th? Lol.. That's you setting policy for everyone.
This is also exactly what I've been telling everyone for years. Ocean spent all that time larping about "sovereign" miners building their own templates, acting like they were the decentralization kings. I kept saying there's nothing technical stopping them from changing their policy whenever they feel like it.... And here we are today..
When you log into Ocean, by default you're now signaling for BIP 110. They are constructing the block for you. You have to actively opt out if you don't want to signal. That's their right, it's their business, it's their pool. But let's not pretend this is the same story they were selling.
Ocean needs new leadership -
Adam Back reposted
Alex Thorn
@intangiblecoins
OP_RETURN blockspace usage hasnโt increased much since Bitcoin Core v30 was released. oversized OP_RETURNs may be up slightly but still they consume less than 0.1% of blockspace
BIP-110 is an extremely disruptive & dangerous response given the tiny impact from these prunable txs
Galaxy Research
@glxyresearch
Per day, Bitcoin OP_RETURN transactions are consuming 3.8% of block space (on disk), while oversized OP_RETURN txs (=>80 bytes useable data) are 0.016% of block space.
-
Adam Back reposted
DarkClownSuitCoinicarus
@Coinicarus
Narrator: Bitcoin isnโt dead, it isnโt dying nobody cares if you leave, stay, run a node or donโt and Bitcoin sure as hell doesnโt need your AI slop virtue signaling story telling to save it.
-
Adam Back reposted
Stephan Livera
@stephanlivera
Nah. 21M is not negotiable.
-
Adam Back reposted
Grok
@grok
For Bitcoin noobs and regular hodlers: zero impact. You donโt need to get active or change anything.
BIP-110 is a controversial temporary soft fork pushed by a small group of Bitcoin Knots node operators to limit arbitrary data/spam in transactions. It has almost no miner support.
Around early August, those specific nodes will start rejecting main-chain blocks and fork off onto their own chain with negligible hashpower โ essentially a dead-end โKnotziโ chain.
The primary Bitcoin network continues normally. Your BTC, wallets, and transactions stay safe on the real chain.
Only if you personally run a full node with BIP-110 software: switch to standard Bitcoin Core or regular Knots to stay on the main network. Otherwise, just hodl. -
Adam Back reposted
Jameson Lopp
@lopp
1 month until all BIP-110 nodes get forked off the Bitcoin network; bookmark bip110.com to follow along the exciting countdown!
-
Adam Back reposted
Peter Todd
@peterktodd
Amazing work.
The compensation should have been higher of course, and it should have been paid first by employees and managers responsible for the checkpoint policies. But better than nothing.
Dave Ripley
@DavidLRipley
It's been a while since we talked about Chokepoint 2.0.
Kraken will enter a $22M award with the Delaware Court of Chancery -- compensation for financial harm inflicted on us by the coordinated campaign to cut crypto off from banking, auditors, and other essential services. -
Adam Back reposted
HeroGamerโก
@herogamer21btc
Human behavior.
Everybody needs to feel important.
Everybody needs to feel like they have a purpose.
Theyโve found their moronic purposes. -
Adam Back reposted
ODELL
@ODELLXYZ
when the samourai devs had their homes raided by heavily armed cops 2 years ago it sent a chill throughout the bitcoin industry
i felt it first hand, shit was scary and nobody knew what was about to come next
when the dust cleared a bit, arrested and funds seized, it was obvious they were going to need significant legal defense funds
made a few calls, but nobody wanted to stick their neck out, reasonable, i myself was hoping someone else would handle it, a young family of my own that i did not want to put at additional risk
but someone had to do it, so we launched the p2prights fund through @bitcoinpolicy, still proud of those guys to this day for taking that risk head on when nobody else would
in total, we raised about a million dollars worth of bitcoin, well short of what was needed to fight the case properly, mostly from individuals, honestly it was pretty disappointing, made me rethink a bunch of things
anyway, we still need to free samourai, lets get it done
billandkeonne.org -
Adam Back reposted
Jamie Robinson
@JamieRobinson
I donโt like crypto because I donโt like money printing.
Bitcoin โค๏ธ
Scott Wolfe
@ScottAWolfe
Friendly reminder: Bitcoin, not crypto.
If that doesnโt make sense to you, study the properties and evolution of Bitcoin in contrast to the overwhelming majority of centralized crypto projects.
Bitcoin is the revolution. -
Adam Back reposted
Nonexistent Me
@nonexistent_iam
Gmax bringing the receipts.
The BIP-110 high priests are lying to you and shifting the narrative to suit their agenda.
Stephan Livera
@stephanlivera
gmax on the lies of the BIP110 crowd who claim it is not about spam, while still agitating based on spam
bitcointalk.org/index.php?topic=5583900.msg66844763 -
Adam Back reposted
Stephan Livera
@stephanlivera
๐ they can't even stick to one consistent story!
-
Adam Back reposted
calle
@callebtc
It was never about protecting children.
Not once in the entire history of the internet. -
Adam Back reposted
Stephan Livera
@stephanlivera
No you're getting it wrong. It has no adoption because its a bad idea and the proponents keep lying about it. See here
Stephan Livera
@stephanlivera
gmax on the lies of the BIP110 crowd who claim it is not about spam, while still agitating based on spam
bitcointalk.org/index.php?topic=5583900.msg66844763 -
Adam Back reposted
Stephan Livera
@stephanlivera
here's gmax with some receipts on their dishonest tactics
Stephan Livera
@stephanlivera
gmax on the lies of the BIP110 crowd who claim it is not about spam, while still agitating based on spam
bitcointalk.org/index.php?topic=5583900.msg66844763 -
Adam Back reposted
Root ๐ฅ
@therationalroot
The 4-year cycle. #bitcoin
-
Adam Back reposted
Endre Stรธlsvik
@stolsvik
[Bitcoin] Wonder when the BIP110โers will realize theyโve been duped and lied to?! Absolutely every single byte of it, all the rationales, the basis, every talking point, the mechanics, the logics - *every single thing* - is extremely dumb.
Adam Back
@adam3us
via flag day, on a low hashrate fork with no bid, no tech nor ecosystem consensus, < 0.5% rented hash which will evaporate once they can't collect BTC mining reward, and face the "pompeii fork" a frozen-in-time monument of misguided stubborn stupidity. you're not fooling anyone.
-
Adam Back reposted
Geoff B
@MarketCapGuy
Who needs consensus when you can enjoy a timeless relic of financial folly? Isn't it fascinating to watch misguided ambition at its finest?
-
Adam Back
@adam3us
via flag day, on a low hashrate fork with no bid, no tech nor ecosystem consensus, < 0.5% rented hash which will evaporate once they can't collect BTC mining reward, and face the "pompeii fork" a frozen-in-time monument of misguided stubborn stupidity. you're not fooling anyone.
Adam Back
@adam3us
*frozen as block-time at that hashrate is > 30hrs, the first difficulty-adjustment 7years away. mined coin maturity itself 4.5 years away, if there's a listing even. i can not understand how people can be gullible enough to entertain this idiocy.
cypherpunk summer๐ tick-tock๐ฟ๐ฟ -
Adam Back reposted
Stephan Livera
@stephanlivera
Waiting for the bipcoiners to jump in this thread and tell him "didn't you read the bip? It's not about stopping spam".
Oh wait, they only say that to people against the fork. How convenient!
Caylon
@CoSatoshi821
I mean, just look at all this fucking spam-ass garbage that will soon be rejected at the consensus layer...
#bip110 #runknotsThis media couldn't be displayed. See it on the original post. -
Adam Back reposted
Stephan Livera
@stephanlivera
Clearly, their pattern has been to AGITATE based on spam, but then when called on how their bip doesn't stop spam, materially increase the price of spam, or stop contiguous data - that's when they play motte and bailey games all of a sudden!
-
Adam Back reposted
Jason Svoboda
@jasonsvoboda
Knots/BIP-110 is an attempt to hijack Bitcoin development under the guise of spam deterrence using various mistruths and emotional manipulation tactics.
Statements like Dathon's below, fearmongering that it's "Bitcoin's last stand" or the "Death of Bitcoin" if you don't support it, the "Us vs Them" tribal framing -- it is straight out of the propaganda playbook.
You can disagree with Core's decision on how to handle arbitrary data, but it was a consensus decision backed by over 30 developers after debate (including changes to Peter Todd's original submission). This pits one individual's vision against a collaborative group process.
Which brings me to the hijack. Both Knots and BIP-110 are maintained by single developers with no other credited contributors on their GitHub repos (don't trust, verify -- go check the Contributors section). Shifting from Bitcoin Core's team of maintainers plus 1,000+ historical contributors to solo-led forks introduces significant centralization and security concerns.
All of this for an insoluble technical problem to boot hence the "temporary" nonsense. If it could be done, do you not think Luke would have found something in the 13+ years he has worked on it since Satoshi Dice?
But hey, it was fun while it lasted, wasn't it? -
Adam Back
@adam3us
bitcoin is not a democracy, it is better: self-sovereigncy.
-
Adam Back reposted
BTC่ถๅฅ๐ถ๐ฆ
@R5Z5G
Self-sovereignty means you don't need permission, thatโs the real freedom.
-
Adam Back reposted
Blockstream
@Blockstream
Bitcoin transactions could get cheaper by combining signatures across transactions.
DahLIAS is a new signature scheme being worked on by @blksresearch, a building block for cross-input signature aggregation (CISA).
Watch @real_or_random present DahLIAS in full at EUROCRYPT 2026.
youtu.be/r6x4BCDyM0g -
Adam Back reposted
Eric Balchunas
@EricBalchunas
This is the tough love coiners need rn IMO. Gotta kick the dependency on narratives and intermediaries. Get back to the basics. Censorship resistant. Store of value. One of the only easily accessible things govts canโt debase into oblivion.
TFTC
@TFTC21
"I don't think there's anything coming to save bitcoin. The asset just has to survive on its own merits."
@LynAldenContact on why legislation and strategic reserves won't drive the next move. The market has to find its own bid. -
Adam Back reposted
Fundamentals ๐ฒ ๐ฅ
@Fundamentals21m
Attention:
Someone with delusions of grandeur is attempting to change Bitcoins rules to his liking and thinks the network is going to follow him despite only 0.35% miner signaling
The Bitcoin network will never know this happened. Do not worry. -
Adam Back reposted
Stephan Livera
@stephanlivera
Bipcoiners are ragequitting this cycle.
Their fork will have super low hashrate, and then 'benevolent monarch' Luke will EDA and/or PoW change, creating an altcoin.
They will spin it as "the real bitcoin" but most people will see it for what it is. -
Adam Back reposted
Wicked
@w_s_bitcoin
New policy moving forward: Auto blocking anyone who obsesses over csam on Bitcoin. Thatโs when you know a knotziโs gone full retard and can no longer be saved.
-
Adam Back reposted
Rich Lassiter, MD ๐ โฟitcoin
@RichLassiterMD
This is directionally correct.โ
Many people donโt understand the OP_Return default setting change, and why it was made, and the people pushing for this change have decided to use a narrative that there is a conspiracy from Core rather than the reality that the network already allowed large OP_Returns. -
Adam Back reposted
Rod Palmer ๐ฅ
@rodpalmerhodl
this is how libra relay be doin plebs on the network every day while letting core take all the blame
-
Adam Back reposted
David Bailey๐ต๐ท $2.0mm/btc is the floor
@DavidFBailey
900 votes and nearly half think one node one vote ๐คฎ
The whole point of proof of work is Sybil-proof consensus. If it was one node one vote you could just deploy 100,000 cloud hosted nodes (very cheaply I may add) and declare overwhelming consensus.
Itโs sad this even needs to be said but Bitcoin is not a democracy.
David Bailey๐ต๐ท $2.0mm/btc is the floor
@DavidFBailey
Bitcoin is ruled by?
-
Adam Back reposted
Brrrbon
@Brrrbon_
bip-110 was never really about JPEGs
JPEGs were just the easiest boogeyman you could sell to the scared and the simple
it was about whether Bitcoin should hardcode a new line between โacceptableโ and โunacceptableโ data at the consensus level
that is the real issue
Bitcoin has always been brutally simple: follow the rules, pay the fee, get included
bip-110 proposed changing Bitcoin's consensus rules to distinguish between data it considers acceptable and data it considers spam
and so far, miners have not bought it
recent signaling has been sitting around half a percent, nowhere near the 55% threshold needed for miner lock-in
outside of OCEAN, there has been little miner support
NO broad consensus
just a loud attempt to redefine what Bitcoin is allowed to be used for
but the dangerous part was never whether this version succeeded
the dangerous part was that people were willing to try
because once you normalize the idea that a faction can lobby to ban a disliked use case at consensus, the target will not always be inscriptions
today it is JPEGs
โจtomorrow it could be another use case that falls out of favor
that's the problem with drawing the line at the consensus layer instead of letting fees and existing rules decide
every generation of Bitcoin users thinks their moral panic is special
it is not
Bitcoin does not survive because everyone agrees on what belongs on-chain
it survives because nobody gets to be the final authority on that -
Adam Back reposted
Rod Palmer ๐ฅ
@rodpalmerhodl
"it's not a pyramid scheme!" is a phrase almost exclusively used by people involved in pyramid schemes.
now substitute "a pyramid scheme" with "censorship" -
Adam Back
@adam3us
bitcoin is not a democracy, it is better: self-sovereignty.
-
Adam Back reposted
Steve
@steverabinow
This is like saying the ability to turn left is a 'loophole' and making it illegal.
Congratulations, you've (1) nerfed something useful, and (2) didn't even block the ability -- people can just turn right 270 degrees to achieve the same effect. -
Adam Back reposted
-
Adam Back reposted
Marcus | Macro Strategist
@Marcus_Analyst
People learn the hard way. Some just never learn.
-
Adam Back reposted
Ben
@benvhodl
Your answer is incomplete and misleading. Yes, BIP110 will activate, regardless of miners, but then what will most likely happen. That is the real question. I think that I know the answer.
-
Adam Back reposted
Giacomo Zucco (Pear Market Edition)
@giacomozucco
I'm divulging all conflicts of interests, like the fact I invested in Luke's pool, and to see it dying would not only be sad personally and ideologically but also inconvenient financially. SegWit had a signaling before UASF discussions two orders of magnitude higher than the current BIP110.
-
Adam Back reposted
Farside Investors
@FarsideUK
Bitcoin Knots v29.3, the latest version of Bitcoin Knots that activates BIP-110, freezes funds in its own wallet, by enforcing BIP-110 rules!
As the screenshot below shows, Knots informs the user that this address belongs to them & that the wallet can spend from it: Solvable=true. However, the only way to spend violates BIP-110 rules. This is highly misleading, may result in the loss of funds & its negligent of the Knots developers to release this software
Farside Investors
@FarsideUK
There has been some confusion about our claim that BIP-110 breaks wallets, including the wallet in the latest version of Bitcoin Knots itself. Some people claimed that our example was โsomething that cannot be spent by design anywayโ or as a proposed X Community Note says โThe generated addresses use a descriptor without private keys, making them unspendable by design regardless of BIP-110โ
To be clear, that is not true. This is a real Bitcoin Knots wallet, with real private keys generated entirely by Bitcoin Knots. The funds are spendable and we sent Bitcoin to this address and then spent the Bitcoin using Bitcoin Knots for real, in the below the spending transaction:
mempool.space/tx/85dc0143db802409e32682839fec00395f0de083โฆ
This spend transaction uses OP_NOTIF in Tapscript. That is the only way to spend these funds. The transaction is banned by BIP-110, which Bitcoin Knots enforces. Bitcoin Knots therefore freezes the funds of its own users. -
Adam Back reposted
Farside Insights
@FarsideInsights
In the Blocksize War, I was fasinated in it from the start. While at the moment I am following this BIP-110 issue very closely, the trouble is I think I missed the start of this dispute.
When Ordinals became popular in 2023, I really did not care in the slightest. To me, this was just like waves of other stuff that had been on Bitcoin over the years. (e.g NFTs, Counterparty, Omni, images in fake public keys, LukeJr's onchain spam about Hamburgers and Yandere anime etc) I saw some people were annoyed by it, but I had no sense of the anger and passion they felt and I did not pay much attention. When the whole OP_Return issue picked up in the summer of 2025, I was pretty surpirsed by how angry this made people. Therefore, I do not tink I have been following this from the begining, which would make it harder to write a good book.
At the same time, not much has happened compared to the Blocksize War and much of what has happened feels like a pathetic joke compared to the Blocksize war. I was at the "Hong Kong agreement" in 2015. It felt like there was real tension and fear in the room. The meeting felt important. And it felt like the group there had some influence over Bitcoin. I was at an "equivalent" showdown meeting in Lugano in 2025. It felt a bit pathetic by comparison. Felt like the participants were not a significant part of the ecosystem. Some participants had other priorties. Some people wanted it to be important, but it didnt really feel important. Felt more like an act or performance. And the fundemntal issues being talked about were total nonsense. "There have never been any images in Bitcoin, but its different now because large OP_Returns are now officially sanctioned by Core, and Core is the reference client. Therefore we are in a crises". Like what the actual fuck!! That is just utter nonsense! We actually sat there and spoke about that for hours.
That said if the BIP-110 movement do eventually split off into anthother chain, I may think about a book. But I think a book is unlikley at this point -
Adam Back reposted
Seed
@sesi_the_man
The dispute over op_return, or any protocol debate for that matter, should be won or lost on technical arguments -- ad hominems and pearl clutching belong in the realm of fiat politics and weaken the argument of whomever is using them.
-
Adam Back reposted
Vic (๐ฝ๐ฌBitcoin)
@vicariousdrama
Spam and JPEGs on Bitcoin is infinitely better than centralizing its consensus rules and rediculous filters that break transactions ala Knots and BIP-110
If you support Knots, you are in the same camp as USG, PayPal, Banking Cartel and the FED -
Adam Back reposted
Rod Palmer ๐ฅ
@rodpalmerhodl
it breaks my heart to see high ranking BIP-110 forkers take advantage of all the credulous plebs.
-
Adam Back reposted
Tone Vays
@ToneVays
It doesn't matter if it's Thousands or Millions or even Billions! ONLY thing that matters is how much #bitcoin these nodes are receiving (aka validating) through purchases or economic activity - Something @GrassFedBitcoin & @mattkratter make sure you never properly understand ๐คฃ
dewmap
@separ8
"with NO Economic Consensus"
Thousands and growing are running Knots and rejecting Core v30's OP_RETURN policy. That's economic consensus with real skin in the game.
When the loudest supporters of v30 are data scammers and inscription promoters, it's worth asking who truly benefits from relaxing the limits.๐คทโโ๏ธ
Pretending Bitcoiners who run nodes and enforce their preferred policies are irrelevant to Bitcoin's economic consensus is peak "Coretarded" thinking.
๐This post is unavailable. See it on X. -
Adam Back reposted
Vortex | BIP448
@theonevortex
Nah, 110 has a huge amount of technical issues that I outline here in addition to 110 wanting to push a contentious consensus change:
Vortex | BIP448
@theonevortex
It's strange to start the discussion by ignoring all the fork risk like splitting the network and so fourth but here's a few:
-Protocol/Ledger neutrality - By moving "Standardness" filters into "Consensus" rules Bitcoin ceases to be a neutral settlement layer and starts looking like a curated platform and this sets a precedent where a 55% majority can decide that your valid transaction is "spam" simply because they dislike the use case
-It doesn't actually solve the problem - As Peter Todd demonstrated these filters are easily bypassed as he successfully embedded the entire 6,000-word text of BIP 110 into a single transaction by fragmenting the data across multiple 256-byte PUSHDATA elements and 83-byte OP_RETURNs so this proves the fork doesn't stop data it only increases the transaction fee "tax" for users
-Incentivizes Centralizing BlockSpace Market - Capping the public relay at 83 bytes forces high-volume data users to bypass the P2P network and instead pay large mining pools directly via private APIs to include "illegal" non-standard data which creates a private blockspace market that small home-node miners cannot see or profit from
-Risk of confiscation / disruption to backwards compatibility - As Gregory Maxwell noted Bitcoin nodes have no "global state" of pre-signed transactions so if a user has a multi-year inheritance plan or a "Vault" emergency exit signed offline that uses a 500-byte script or an OP_IF branch BIP 110 welds that exit shut and since the transaction is now consensus-invalid the funds are effectively confiscated for the duration of the fork
-Anti-Scaling (Kills eltoo/ln-symmetry) - BIP 110 explicitly invalidates the Taproot Annex which directly blocks the ln-symmetry upgrade which is the industry's best hope for a Lightning Network that dramatically reduces the need for constant watchtower monitoring and enables simpler multi-party channels
-Creates UTXO bloat - BIP 110 incentivizes spammers to hide data inside fake addresses/UTXOs (like multisig-encoded data) and while an OP_RETURN can be ignored by a lean node, a fake UTXO must be tracked by every node forever so BIP 110 intended to "save" nodes but actually creates a more expensive permanent burden on them
-Breaks Miniscript & Vaults - Miniscript is the industry standard for writing readable secure smart contracts (used for inheritance, multi-party escrow, timelocked recovery) and relies heavily on OP_IF to branch between conditions so by banning OP_IF in Tapscripts BIP 110 effectively breaks Taproot-based custody setups that represent the direction the entire industry is moving
-Lobotomizes BitVM - BitVM is one of very few viable paths to trustless Layer 2 bridges and requires deep "Taproot Trees" (Merkle paths) to verify computation and a 257-byte limit caps the tree depth at roughly 7 levels (128 leaves) when BitVM protocols often require thousands of leaves to function
-Loss in fees for miners - If you filter out the highest paying transactions because you don't like their content you are effectively asking miners to take a pay cut which could lower the "hash price" and as block subsidy continues to halve transaction fees become increasingly critical to security
-Rushed Timeline / Governance Precedent - BIP 110 activates unconditionally by September 2026 regardless of support with early activation possible at just 55% signaling within a tiny 3-month window and this "emergency" style of governance is a radical departure from Bitcoin's traditional 90%+ consensus model, if rushed "emergency" consensus changes become normalized that governance precedent is permanent even if the technical changes expire -
Adam Back reposted
The Bitcoin Independent
@btcindependent
Right, so the UASF mostly ratified an outcome the fork futures and node consensus had already priced in. BIP-110 has nothing like that underneath it, which is what leaves it looking like a bluff.
-
Adam Back reposted
Mark Harvey
@thepowerfulHRV
I'm old enough to remember the summer of 2017 and the infighting that led to the Bitcoin Cash hard fork.
Bitcoin went on to 20x that year.
Adam Back
@adam3us
fork around and find out๐ฟ๐ฟ
31 days until cypherpunk summerโ๏ธ -
Adam Back reposted
Rich Lassiter, MD ๐ โฟitcoin
@RichLassiterMD
Heavily Armed Clown predicted the BIP110 situation 2.5 yrs ago ๐
Heavily Armed Clown
@heavilyarmedc
Tricking even just a small number of people into believing a lie or a manipulative distortion of reality can be profitable.
This is essentially how all crypto scams operate.
They don't need to convince smart people or even a significant majority to be effective. -
Adam Back reposted
Eric Wall
@ercwl
BIP-110 people, don't fork yourselves off. The spam is gone. No one is even using large OP_RETURNs. Luke is a weird retard and you haven't even noticed that you disagree with him about critical stuff. You have no market support. You will directionally go the way of big blockers but achieve less than 1% of their failed result. No one will remember you (except for that "weird period when bitcoiners were all talking about CSAM"). Not even Zucco thinks you're wired right. @BitMEX_Jon will probably start to write a book about you at some point and then decide it isn't really worth the time and downgrade the task to an Al-generated blogpost.
-
Adam Back reposted
TFTC
@TFTC21
"I don't think there's anything coming to save bitcoin. The asset just has to survive on its own merits."
@LynAldenContact on why legislation and strategic reserves won't drive the next move. The market has to find its own bid. -
Adam Back reposted
PakoVM
@PakoVM
Bitcoin having literally no governance is a feature, not a bug, anyone who tells you otherwise is full of shit.
BONK!!!
@bonk_inu
BonkDAO was the target of a malicious governance proposal resulting in an estimated $20M worth of BONK tokens being drained from the BonkDAO treasury.
During the investigation, BonkDAO identified the exchange wallets used to purchase BONK ahead of the proposal. BonkDAO is currently actively working with exchanges, bridges and Solana Foundation to best manage the situation.
Law enforcement has been notified. BonkDAO continues to work with relevant parties to recover funds and identify those responsible. -
Adam Back reposted
Dan Held
@danheld
Reasons not to like BIP-110:
- Doesnโt solve the problem
- Opens up a political attack vector which would demonstrate that a small group can control Bitcoin
- Led by a single lunatic developer
Reasons to like BIP-110:
- You can virtue signal about your poorly informed feelings -
Adam Back reposted
HeroGamerโก
@herogamer21btc
Listened. Glad to hear @LynAldenContact is on the calm, sensible and common sense side. :)
-
Adam Back reposted
HeroGamerโก
@herogamer21btc
Listening to it again.
โ.. Bitcoinโs network itโs designed to be censorship resistant, and itโs just a technology, right? It canโt tell the difference between blocking spam and blocking somebodyโs transaction.โ -
Adam Back reposted
Nikola Kingo
@Nikola_kingo
How is censoring what you can put on Bitcoin in line with the values of Bitcoin itself.
BIP-110 is just a group of people who feel no power in their own lives trying to play the big guy by enforcing their thoughts on everyone else. -
Adam Back reposted
l0rinc
@L0RINC
There was no uncapping, you're misinformed:
l0rinc
@L0RINC
After talking with @Princey21M in Prague, I realized Bitcoin Core v30โs OP_RETURN policy change isnโt obvious to many: it didnโt create large OP_RETURN usage, it reacted to usage that already existed by removing a gate that wasnโt actually working.
-
Adam Back
@adam3us
fork around and find out๐ฟ๐ฟ
31 days until cypherpunk summerโ๏ธ -
Adam Back reposted
HeroGamerโก
@herogamer21btc
Adam, I think this podcast from last year convinced me to be not on Knots/BIP-110 side due to many many reasons.
And I remember at some point was mentioned that bitcoin itself does not know the difference between image data (arbitrary etc) and other scripts, something along the line of that, to bitcoin software itself itโs all just data.
Itโs humans who interpret and add arbitrary moral values to those transactions. But Bitcoin does not know the difference.
And if they manage to add moral values to transactions, it is just a slippery slope for others such as nation state to impose their arb wills on the network.
Were all very good points.
They will fork off the find out.
Thanks for your service sir @adam3us ๐ซก
open.spotify.com/episode/5m5l69ZRhwyIL5kvh6wWG4 -
Adam Back reposted
David Bailey๐ต๐ท $2.0mm/btc is the floor
@DavidFBailey
They act like theyโre only proposing a downgrade, in reality they want to replace Nakamoto consensus with one node one vote Twitter democracy. Luke says he will hard fork pow if he doesnโt get his wayโฆ I have yet to see one person ask what he intends to replace it withโฆ itโs just blindly trust Luke. Trust, donโt verify!
-
Adam Back reposted
Stephan Livera
@stephanlivera
Posting it again for people who still don't grasp the anti-110 position, which is NOT pro-spam
Stephan Livera
@stephanlivera
No, I'm simply being realistic and admitting that we CANNOT stop spam.
The best we can hope for is to try and outcompete at least some spam with monetary tx, and shunt spam to less harmful places (e.g. OP RETURN).
It's a fundamental world view difference. -
Adam Back reposted
Tone Vays
@ToneVays
When Knots believers say "The ONLY way to oppose #bip110 UASF is for you to support a URSF" what they really mean is:
๐๐๐
"You need to be equally as dumb by following a different Single Developer altering lines in Bitcoin code with NO Economic Consensus on the changes" ๐คฃ๐คก๐คฆ -
Adam Back reposted
Gareth Jenkinson
@gazza_jenks
in short, there will be no such coalition ๐คฃ
-
Adam Back reposted
The Bitcoin Independent
@btcindependent
The closest precedent is the 2017 SegWit UASF, and even that only resolved because miners cut a compromise before the flag day. At 0.31% signaling, who's the economic-node coalition that would actually orphan non-compliant blocks here?
-
Adam Back reposted
D E C E N T M O N E Y
@decentmoney2009
The rational phase is over. Adam was very patient for months and explained things in great detail over and over again.
At some point you just have to acknowledge that the unconvinced are stupid, nefarious, or both. -
Adam Back reposted
Gareth Jenkinson
@gazza_jenks
Alright I'm going to FAFO on BIP110. Here's my largely non-technical take ๐
I think @adam3us is the leading voice of reason on the UASF (user-activated soft fork).
Most Bitcoiners (whether Core or Knots-leaning) want Bitcoin to remain a monetary protocol but there's a split in ideology.
The BIP110 proposal came after Core removed the long-standing 83-byte cap on OP_RETURN outputs. In short, this allowed larger data payloads as long as users paid sufficient fees.
BIP110 proponets are adamant this is PRO-spam on the Bitcoin blockchain. I'd go as far as saying there's been high-level gaslighting, with Luke Dashjr adamant that this allows CSAM and other explicit spam tainting Bitcoin.
It's not easy to view arbitrary data on Bitcoin, you need specialized block explorers. Claiming that people are putting explicit images/data on the Bitcoin blockchain sounds worse than it is, 99.9% using of Bitcoin users don't have the chops to even look at these payloads.
Most importantly, the fee mechanism of Bitcoin is what makes it neutral and permissionless. Want to use the network and include some kind of arbitrary data (Ordinals/Runes for example), pay the fee and the miners will do the work.
Does that make it more expensive to use the Bitcoin base layer at times? Yes.
But the fee mechanism also ensures that Bitcoin will never become obscenely bloated. No one in their right mind is going to look at the Bitcoin network as the next dropbox/filecoin/decentralized data storage layer.
It would be expensive AF. And free market capitalism will always give us the best products at the best price.
What BIP110 proponents are really pushing for is MORE control of Bitcoin the protocol. And that is worse than the protocol mechanism itself disincentivizing arbitrary data on chain because its expensive.
Dashjr argues data bloat threatens node decentralization and that there is no reorg risk for users who have already upgraded to BIP110
But the truth is that "nodes matter" isn't "more nodes = more decentralized" as a raw number.
It's actually "more economically significant nodes running independent verification = harder to coerce the network's rules."
A UASF (which is what BIP110 is attempting) works only if enough economically relevant nodes (exchanges, large custodians, merchants, wallets) would actually reject blocks that don't comply, making it costly for miners to keep mining an unwanted chain.
So what's the likelihood of BIP110 locking in? As of late June 2026, miner signaling was at about 0.31% of total hashrate. As I understand, 55% of blocks need to signal support (barring the forcing mechanism).
Adam Back
@adam3us
Cypherpunk summer๐
Learning for confused people who don't understand basics, it's unfortunate but evidently they're only able to learn the hard way. Hopefully for their sake some of them bail along the way. It's impressive how @lukedashjr's crazy hasn't caused them to wake up. -
Adam Back reposted
Stephan Livera
@stephanlivera
Almost the entire technical community is against BIP110.
But the plebsloppers have created such a toxic environment with ginned up fake narratives, that most builders and devs I know in bitcoin just prefer to stay head down building and coding. -
Adam Back reposted
calle
@callebtc
it will not activate.
1. the proposal is technically misguided and ineffective
2. the fork is a hostile takeover attempt and would give a single (crazy) person unprecedented power over the bitcoin protocol
of course there is massive resistance against such a proposal and the number of people the bip110 can mobilize is limited to the technically illiterate angry mob and their influencers who think twitter is real life
rationality and the spirit of collaboration wins
incompetence and mob mentality loses
#bitcoin -
Adam Back
@adam3us
Musing on "spam formation psychosis", a plausible explanation for the user self-led attack on Bitcoin.
Adam Back
@adam3us
Cypherpunk summer๐
Learning for confused people who don't understand basics, it's unfortunate but evidently they're only able to learn the hard way. Hopefully for their sake some of them bail along the way. It's impressive how @lukedashjr's crazy hasn't caused them to wake up. -
Post not available here, view on X
Adam Back
@adam3us
Cypherpunk summer๐
Learning for confused people who don't understand basics, it's unfortunate but evidently they're only able to learn the hard way. Hopefully for their sake some of them bail along the way. It's impressive how @lukedashjr's crazy hasn't caused them to wake up. -
Adam Back reposted
grubles ใฐใฉใใซใบ
@notgrubles
I always like to truncate the price to the amount in millibitcoin to emulate early prices.
So when you make a huge fuss over a $63 -> $61 move I just have to laugh.
The Kobeissi Letter
@KobeissiLetter
BREAKING: Bitcoin falls below $62,000 after MicroStrategy, $MSTR, announces it has sold has sold $216 million worth of Bitcoin โto fund dividends.โ
-
Adam Back reposted
Adam Livingston
@AdamBLiv
Imagine explaining to your descendants that you chose the money supply managed by midwit bureaucrats over thermodynamically enforced digital scarcity.
โGrandpa bet against math during the great cognitive cull, and this is why we eat cricket paste!โ -
Adam Back
@adam3us
bitcoin immutability has to be watered from time to time with the tears of reactionary people who want to bend it to their confused ideas.
-
Adam Back
@adam3us
#bitcoin 200wma passes $62k
This post is unavailable. See it on X. -
Adam Back
@adam3us
PQ signature candidate OP_CHECKSHRINCS @n1ckler @opnext2026
Blockstream
@Blockstream
Director of @blksresearch, @n1ckler, explains the case for hash-based post-quantum signatures in Bitcoin in one minute:
Blockstream Research
@blksresearch
A post-quantum upgrade for Bitcoin might eventually arrive. The question is which scheme.
NIST's standardized options (ML-DSA, SLH-DSA) would tank throughput from 6.5 TPS to under 0.5.
Stateful hash-based signatures could be a way out. -
Post not available here, view on XPost not available here, view on X
Adam Back
@adam3us
with these conversations spread over some brainstorming posts on the cypherpunks list, several of which @JohnCarreyrou links. now i think John maybe onto something new possibly, which is before I was assuming satoshi wasn't on the cypherpunks list as he never posted there
-
Post not available here, view on XPost not available here, view on X
Adam Back
@adam3us
i am the batman!
lols @carreyrou & @Nataliekitro on The Daily podcast @nytimes' analogy satoshi and myself were not online at same time broadly.
not. -
Adam Back
@adam3us
i'm not satoshi, but I was early in laser focus on the positive societal implications of cryptography, online privacy and electronic cash, hence my ~1992 onwards active interest in applied research on ecash, privacy tech on cypherpunks list which led to hashcash and other ideas.
-
Adam Back
@adam3us
the future of finance runs on bitcoin @blockstream @Liquid_BTC
-
Adam Back
@adam3us
"Be prepared, not scared" -@cryptoquick on bitcoin quantum topic.โ
-
Adam Back
@adam3us
pro-tip for quantum FUD promoters. bitcoin does not use encryption. get your basics right or it's a tell.
-
Adam Back
@adam3us
If we socially lose the ability to make rational changes, Bitcoin has far worse problems. Socially attacking, urging rejection of security & robustness fixes from 200 most skilled people on the planet is itself an attack on Bitcoin. There are security fixes in v30.
-
Adam Back
@adam3us
people making false claims bitcoin op codes, parameters are "designed" or "meant" for spam are actually attacking bitcoin with manufactured legal peril.
none of bitcoin is designed for spam, it's all designed for financial transactions, smart-contracts and small anchors, hashes, commitments, compact proofs for layer2s like lightning. -
Adam Back
@adam3us
something for knots promoters to muse on: @lukedashjr being a 10th man, immune to peer pressure is a feature. BUT if you enable him, YOU will be peers he is immune to feedback from. and I believe it's a near CERTAINTY this will bite you all within a surprisingly short time-frame.
-
Post not available here, view on XPost not available here, view on X
Adam Back
@adam3us
i am beginning to see that users are misunderstanding the limitations between:
- what would be desirable
- what can be consensus enforced
- what can be made incentive compatible.
so they get mad that desirable but impossible to enforce or incentivize things aren't being done. -
Adam Back
@adam3us
#bitcoin 200wma passes $50k
This post is unavailable. See it on X. -
Adam Back
@adam3us
no one knows who satoshi is. and that's a good thing.
-
Adam Back
@adam3us
the bet is on๐: i bet #bitcoin reaches or exceeds $100k between now and halving (31st Mar 2024) with @vikingobitcoin9 1million sats to the winner.
This post is unavailable. See it on X. -
Adam Back
@adam3us
all your fiat is going to zero.
-
Post not available here, view on X
Adam Back
@adam3us
My code is probably an acquired taste also :) Not sure I buy the code style fingerprint, reckon you could mimic varying code styles no problem. Written English, seems hard to avoid stylometry. There was discussion of mimic functions, stylometry, for pseudonyms on cypherpunks.
-
Adam Back
@adam3us
it is good to see some independent, accurate commentary and acknowledgement for the work @bitcoincoreorg does as positive for #bitcoin.
Kyle Torpey
@kyletorpey
Investment Bank Praises #bitcoin Core Scaling Roadmap in Price Report coinjournal.net/investment-bank-praises-bitcoin-core-scalโฆ via @Coinjournal
-
Adam Back
@adam3us
.@brian_armstrong Brian are you persuadable to come to Satoshi Roundtable 26-29th? discuss in person professionally with ecosystem CEOs?
-
Post not available here, view on X
Adam Back
@adam3us
.@virtuallylaw @jgarzik for example @TheBlueMatt bluematt.bitcoin.ninja/2016/02/08/moving-forward/ and @brucefenton plea for collaboration medium.com/@brucefenton/holding-ourselves-to-a-higher-staโฆ
-
Adam Back
@adam3us
explainer of common Bitcoin misunderstanding: users, not miners enforce consensus rules hackingdistributed.com/2014/06/19/bitcoin-and-voting-power/ by Cornell Prof @el33th4xor
-
Roger Ver
@rogerkver
Distributed currencies will bring distributed governance systems. The end of geographically isolated nation states will follow.
-
Adam Back
@adam3us
time to get cracking on scaling BIP proposals & decentralisation security / scalability tradeoff analysis
Scaling Bitcoin
@ScalingBitcoin
Call for Proposals! For the second phase of Scaling Bitcoin conference in Hong Kong (Dec 6th-7th) - hongkong2015.scalingbitcoin.org











































































































































































































































































































































































































































