Lightning as a clearing house is like if every time someone issued an interbank transfer a boy was sent running with the cash in hands from one bank to the other to complete the transfer.

drivechain FUD bingo card

blup

imagine the "great script restoration" gives Bitcoin unlimited computational power. you can now do anything with script, even more than just OP_CAT would allow you to. so what? ethereum has had all that since always and tons of people trying to find a way to scale payments there for almost 10 years and the best they got was zk-rollups, which is shitty as scaling and only increase throughput by 2x

follow @htlc_nbot

imagine using a "payment pool" now you're making the same number of onchain transactions but every single one of them requires a bunch of people to sign? and you add a huge risk of bugs that cause money to be lost or everybody has to exit and pay $200 each

I wish I could get inside the minds of these people who think "sharing utxos" accomplishes anything for Bitcoin in terms of scaling lightning is already "sharing utxos" and look at how bad it is, any other construction will be worse

anchor outputs were the worst idea

all software has bugs, it just happens that lightning software has many more bugs than normal and these bugs cost much more money than normal, and after 7 years of complete dedication of dozens of developers they still exist for the most basic things, and yet these same developers insist in adding more and more complex features to the protocol

Another normal day in ZBD Social development.

How can Ark scale anything if each Ark internal transaction needs a Bitcoin onchain transaction? Sure, you can have infinite internal transactions at the cost of a single Bitcoin transaction, but how many active users do you need to not be required to wait 32 hours until accumulated potential internal transfers are enough in number to compensate doing a single onchain transaction at high fees?

King Arthur's Gold was probably the best game ever made.

imagine if we had to implement "transfers" in bitcoin, then we were left in a standstill trying to pick among p2pk, p2pkh, p2sh multisig, p2wpkh, p2wsh multisig or p2tr then we wouldn't be able to have any of these until we figured out the best and for those who think taproot is the best then maybe we should have waited 10 years before the first bitcoin transfer was made someone would be running a transfers.info website following all the proposals

Another Christmas, another Christmas without any useful soft fork.

Covenants.info

Documentation about Bitcoin Covenant proposals.

It turns out that RGB requires receivers of assets to already have an UTXO, it can't be the UTXO that has just been created in the process of sending. This is the most convoluted design anyone could have thought about. Why people think this is a good idea is beyond me.

CTV is useless. If CTV is activated by UASF no one is going to use it. That doesn't mean we shouldn't activate APO, TXHASH, CAT, Drivechain, OP_VAULT and other things, because these are useful.

The Mempool Open Source Project®

Explore the full Bitcoin ecosystem with The Mempool Open Source Project®. See the real-time status of your transactions, get network info, and more.

This HTLC output from a closed Lightning channel costed in redemption fees more than its value.

Hackathons are a waste of time.