BIP-54 is being pushed so much by Bitcoin Core for one simple reason: the "timewarp attack" is not an attack but, if coordinated correctly by miners, a potential scaling solution that Bitcoin Core is afraid of.
With enough miners on board (my calculations show that around a 90% supermajority is required), it's possible to "trick" Bitcoin's clock into ticking N times faster in a stable (!) way.
So, instead of blocks coming up every 10 minutes on average, they could come up, say, every 5 minutes, doubling the throughput and improving the user experience.
Yes, this may have the side effect of the block subsidy running out a bit faster, but considering that Bitcoin's already got a security budget issue, this would be a) a nice instant temporary remedy, and b) a long-term solution due to the possibility of collecting more fees thanks to the increased throughput.
The "timewarp attack" vector by itself is purely theoretical nonsense. It either requires a 51% majority that would orphan "non-participating" blocks or a 90% supermajority. It's visible on-chain and requires weeks to get activated. So, "remaining block subsidy could be mined in roughly 40 days" is a bogeyman. A quick reminder: Bitcoin requires at least 51% of its miners to be "honest". Otherwise, it simply doesn't work, and a "timewarp attack" would be the least of our concerns in case of a 51% attack.
Okay, back to scaling! Best thing about this approach? It doesn't require any kind of fork: neither hard nor soft. The possibility is already in the code. Considering that Bitcoin has huge issues with upgrades, it can be the last chance to actually scale Bitcoin.
Instead, Bitcoin Core wants to remove that possibility. Why? Because they still push for their defunct Lightning. Who are the authors of BIP-54? @darosior who works for Chaincode Labs and @TheBlueMatt who is a Blockstream co-founder. A clear conflict of interest to benefit Lightning.
@foundryservices, @AntPoolofficial, @f2pool, @ViaBTC, @SpiderPool_com, @MARA, @luxor, take notes!
Do I need to spin up an explainer website with details and charts? 🤔
@csuwildcat Well, try to remember how many of these lame Blockstream folks were saying "code is law" and supporting Ethereum Classic during the DAO hack back in 2016 and you'll get the irony.
Just for the record: I'm obviously not arguing that "stealing" L-BTC was a moral thing to do, but there's a huge but.
Blockstream blokes and their fans are the ones who've been preaching "code is law". It was them who were calling Ethereum a "centralized shitcoin" for reverting the DAO hack back in 2016 and supporting Ethereum Classic for "doing the right thing".
If you preach "code is law" (which is a valid thing to do, I'm not saying this is wrong!), you're taking the risk that the code you're using may be buggy, and you deem that risk lower than the risk of centralized actions such as rollbacks. It's a trade-off!
But saying that "reverting the DAO hack" was bad while at the same time saying "meh, L-BTC thing was a theft, not a bug, so return the coins or we call the FBI" is hypocrisy. https://t.co/DBGPySfSKB
I'm disgusted by many of the replies. People saying "code is law, so it's fair game to steal 600 bitcoin" are amoral weirdos. If their home had a lock w/ buggy firmware that allowed thieves to loot it, then the thieves returned some of their possessions after they begged, but kept a lot of their property, I bet your ass these goofballs wouldn't be like "Hurr derr, code is law, so it's my fault thugs used a code bug to get into my house and steal my stuff. They aren't criminals, they're 'whitehats' I must respect and thank for returning some of my things after I begged them". Get the f*ck out of here, you spineless, morally bankrupt goofballs. Thieves deserve to be hunted, beaten, and made an example of, not lauded as noble actors.
Had the funds been "stolen", though? What happened to the "code is law" mantra which Blockstream was in love with so much?
The "hacker" simply made a transaction which turned out to be a valid one under Liquid's own consensus rules: they created new L-BTC and then withdrew them. They didn't "steal" anyone's coins.
Many people, including me, have been warning that Blockstream developers are incompetent for years. They took the risk of using their product and got a haircut. Sounds fair to me 🤷♂️
To those responsible for the theft of bitcoin from the Liquid Network:
Blockstream will not pay a ransom for the return of stolen funds. Taking assets without authorization and withholding their return is a crime, not responsible disclosure. It is not white-hat activity. It is theft.
We have engaged in good faith in an effort to secure the return of stolen user funds and protect the broader Bitcoin community. That effort should not be mistaken for acceptance of the actions taken nor of the terms being demanded.
We will not be a party to the precedent that open-source software developed for the good of the Bitcoin community should subject its developers to paying a ransom that far exceeds their economic participation.
Bitcoin is hard money and can’t be minted without costs, Bitcoin doesn’t haircut users to pay a ransom.
To the Bitcoin community:
We are fighting for what we believe in, for the users whose funds were taken, and for the principles on which Bitcoin was built.
The community has demonstrated incredible resolve with teams of people dedicating their time in support of each other to identify and patch vulnerabilities in each other's products and systems. We are all driven by the mission that Bitcoin is the single best asset, for every person, company, and institution on the planet to invest, use, and build on. The world is a different place with the advancements of AI, and the Bitcoin community has responded with force to combat that threat.
Damage has been done, battles have been lost, but on the whole the Bitcoin community is gaining ground in the war with bad actors.
We want to thank the community for those efforts, for your support in hardening the network, helping users recover funds, and for your support in our assertion that crime does not deserve rewards.
To those holding the stolen bitcoin:
There is still an opportunity to resolve this responsibly. The bitcoin can be returned and we can revert to the standard of white-hat principals.
However, if the funds are not returned, we will pursue every lawful avenue available to us. We will work with law enforcement, exchanges, service providers, forensic specialists, and other relevant parties to trace and recover the assets and identify those responsible.
More importantly, Bitcoin is transparent by design and the community is made up of the most sophisticated engineers, cryptographers, and white-hat hackers globally. Transactions do not disappear, and neither does the evidence they leave behind.
We will not pay for the return of stolen property. We will not abandon our users. The Bitcoin community will not stop pursuing the funds.
Return the bitcoin.
Using cold wallets is meh. For an average user who doesn't want to bother with multisigs but has a non-trivial amount to store, I always recommend 1) using an air-gapped phone or laptop, 2) dice-generating the seed and/or using an additional xkcd-like passphrase.
@dbadol2000 Yet no one has found any bugs in Bitcoin itself, or, say, in the WBTC contract on Ethereum. They're incompetent.
The funny thing is that Liquid has never been decentralized, yet they needed that decentrazliation theatre to fool people, and that's exactly where they've failed.
We are aware of a security incident on @Liquid_BTC. Purported white-hat hackers have withdrawn ~4,000 BTC (~$320 million) from the Liquid Federation wallet. The @Blockstream team is working on contacting them on-chain with a signed message.
What we know so far is that the funds were withdrawn via the SideSwap PAK (Peg-out Authorization Key), but that key was not compromised, nor were any others.
Exchanges have been notified and have already paused (or will pause) LBTC deposits and withdrawals. Other Liquid assets such as USDT, DePix, and RWAs are unaffected by this security incident.
Bridge nodes have been temporarily disabled, so no new transactions can be submitted to the network. Effectively, the Liquid sidechain is paused until this issue is resolved.
Liquid wallets will be impacted, and we're sorry for any inconvenience. Federation members are actively working on resolving this so we can restore normal network activity.
You can monitor the situation via @mempool's https://t.co/M46Zhn8nlY site below:
https://t.co/B8j9u4j6i4
@korporacia48516 We're reading everything, but getting overloaded with slop reports, and unfortunately there's not enough hands to answer to all this.
For example, one of the "vulnerabilities" you've reported is that our own status page is an "operational status disclosure" 🤷♂️
BIP-54 is being pushed so much by Bitcoin Core for one simple reason: the "timewarp attack" is not an attack but, if coordinated correctly by miners, a potential scaling solution that Bitcoin Core is afraid of.
With enough miners on board (my calculations show that around a 90% supermajority is required), it's possible to "trick" Bitcoin's clock into ticking N times faster in a stable (!) way.
So, instead of blocks coming up every 10 minutes on average, they could come up, say, every 5 minutes, doubling the throughput and improving the user experience.
Yes, this may have the side effect of the block subsidy running out a bit faster, but considering that Bitcoin's already got a security budget issue, this would be a) a nice instant temporary remedy, and b) a long-term solution due to the possibility of collecting more fees thanks to the increased throughput.
The "timewarp attack" vector by itself is purely theoretical nonsense. It either requires a 51% majority that would orphan "non-participating" blocks or a 90% supermajority. It's visible on-chain and requires weeks to get activated. So, "remaining block subsidy could be mined in roughly 40 days" is a bogeyman. A quick reminder: Bitcoin requires at least 51% of its miners to be "honest". Otherwise, it simply doesn't work, and a "timewarp attack" would be the least of our concerns in case of a 51% attack.
Okay, back to scaling! Best thing about this approach? It doesn't require any kind of fork: neither hard nor soft. The possibility is already in the code. Considering that Bitcoin has huge issues with upgrades, it can be the last chance to actually scale Bitcoin.
Instead, Bitcoin Core wants to remove that possibility. Why? Because they still push for their defunct Lightning. Who are the authors of BIP-54? @darosior who works for Chaincode Labs and @TheBlueMatt who is a Blockstream co-founder. A clear conflict of interest to benefit Lightning.
@foundryservices, @AntPoolofficial, @f2pool, @ViaBTC, @SpiderPool_com, @MARA, @luxor, take notes!
Do I need to spin up an explainer website with details and charts? 🤔
��� URGENT: Critical vulnerability in Core Lightning
Blockstream developers urge users to shut down CLN Lightning nodes right NOW!
Please let everyone know!
A bitcoin miner just switched off every single one of its US bitcoin mines.
Keel, the company that used to be called Bitfarms, sold 1,085 bitcoin for $75 million. The buildings are becoming AI data centers now. Revenue fell 50%.
@anonpragmatic When Bitcoin was first published, it was supposed that fees would replace the subsidy. No one knew it back in 2009 that some guys would come and capture Bitcoin by not allowing it to scale to actually have these fees.
Yeah, thanks to Bitcoin Core, the security budget issue is already here, and Bitcoin will have to face a choice: either a block size increase (nope) or this… So, bye-bye, 21-million-coin cap 👇
@het_tk A bigger block size would attract more businesses to Bitcoin. Right now you can't build anything on Bitcoin that would require more than 1 tps.
What I've never understood about forking away (this applies to Bitcoin Cash in the same way as it does to Bitcoin Luke): yeah, you fix some surface issue (too little spam, too much spam, whatever), but you still end up inheriting the underlying issue, which is governance 🤔
My point here is that if you believe that the old chain has got "captured", how does creating a new PoW fork help? Yes, it will have the feature you wanted, but at some point in time, if your new chain becomes super popular, it will get "captured" once again 🤷♂️
Put simply, I believe Bitcoin has a chance switching algo to BLAKE2B. I don't believe the SHA256 chain has a future, primarily because it's becoming increasingly centralized.