ReneeStricklandIFP

Design

I've been seeing some talk lately about the need to fork bitcoin in the future and implement tail emissions, as though Bitcoin will fail without a block reward. This has never made sense to me, and I think such a fork would be a terrible idea.

Bitcoin doesn't have a "security budget." It's a protocol to provide probabilistic finality to reduce / eliminate the risk of a double spend. With no block reward, for any type of large transaction with an untrusted party, there is a strong incentive to provide "free" bitcoin to the miners of subsequent blocks, to ensure finality. This will be less necessary for small transactions, since the base level of transaction fees will likely be sufficient.

What are your thoughts on this? Obviously, we're still decades away before this will be a "problem," but I think it's important to address. These "tail emission" arguments need to put to rest.

Tail Emissions Are A Terrible Idea

econ

POLL: What "qualifies" as Bitcoin adoption?

JaniceHenderson7X7

To clarify: I am myself a bitcoin maxi. I am currently only invested in Bitcoin. It is the hostility part of maximalism that I believe turns people off and is counterproductive to increased bitcoin adoption.

There are some interesting things going on outside of Bitcoin, it is not all scams.

Operation Saylor - Episdoe 1/120

EarlLambSAK

Something like postman for nostr events. With a a UI to fill in the fields. 

As well as subscribe to things and see what the responses look like. 

lightning

SN Saloon

GabriellaMcintosh1RW

the federal reserve is very aware of bitcoin and also so is the defense department.  Everyone is watching us closely and although the pundits don't get it, the smart administrators and generals understand the technology 

I listened to the Bitcoin Audible Podcast [episode](https://www.fountain.fm/show/RtZlWdbEbpyEyjBNbeQ7) where Guy read the Ryan Gentry article on taproot assets (formerly known as Taro). From Guy's take, at worst this could solve an onchain problem. At best, it could open up many new lightning use cases. Guy seemed positive, and I usually trust his opinion.

Searching SN for info, I saw that @DarthCoin weighed in with "TapAss" on May 19. I must add that to the Second Edition of the Translation Guide.

What's the consensus here, or is it just wait and see?

Taproot Assets: Good or Bad?

devs

Introducing Ark by Burak

SydneyGillNYK

Hello, I've been using Zeus for quite a while and I'm actually quite at peace. What bothers me the most about the app is the small display for the sats. Can't you enlarge it, like with the Zap wallet? There would be enough space.

bitcoin

Many years ago, back when BTC was worth every little, an anonymous user created 160 "puzzles" on the Bitcoin timechain. Each puzzle is simply an amount of BTC which is locked by an address that was generated with a purposefully low-entropy private key.

The anon user published the list of 160 bitcoin addresses along with the amount of entropy used in the private key for each address. Address #1 only used 1 bit of entropy so the private key for Address #1 was literally either 2^0 or 2^1 (000..001 or 000...002). Needless to say, the first dozen puzzles were solved almost instantly. However, each puzzle is twice as difficult to "crack" as the previous one.

Over the years, the remaining puzzle addresses have received additional deposits from people looking to "sweeten the reward".

Yesterday, this transaction entered the mempool: https://mempool.space/tx/8c8ec6b3511c62500ea9b3a1c30ca937e15d251b55d30290a2a6da2f1124f3fb

It spends from the 66-bit puzzle address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so

This tx (accidentally) revealed the script pubkey of the address to everyone watching the mempool. This was a big mistake.

Since these addresses are known to be generated with low entropy, it only takes a few seconds/mins to brute force the private key if you already know the public key.

This caused the tx to be RBF'd by "bots" who were monitoring the mempool for spends of these puzzle addresses. 

This tool was likely used by the bots: https://github.com/JeanLucPons/Kangaroo

The bots managed to recreate the exact same private key from this accidentally revealed public key in just a few mins, meanwhile it took years and many Megawatts of compute to find the private key from just the address.

It appears most of the 6.6 BTC reward locked by the 66-bit key (we can't really call it a private key anymore) was redeemed by these bots.

It also possible that something nefarious happened (like a puzzle pool operator tried to make it look like bots stole the TX, when, really it was all a coverup to steal the reward from the pool participants).

This "theft" of the 66-bit puzzle reward highlights another use-case for "private" tx-inclusion services offered by large mining pools. If the finder of the 66-bit key had sent their TX direct to a miner, then maybe it could have been fully redeemed (assuming the miner didn't try to steal it also).

Anyways, its a good lesson in the importance of using strong entropy. The completion of these puzzles is also a reminder that compute is getting faster and cheaper every year, and Bitcoin relies on compute being expensive to enforce its property rights.

**Warning**: If you're thinking of joining one of the pools "cracking" these puzzles, consider your risks! Most of these pools are fully trusted and not auditable. You're spending real resources (GPUs and electricity) for a chance to be granted a reward by a trusted pool operator. There's also a ton of technical risk, even if your pool manages to crack the next puzzle, there are many factors that can lead to no payout for you!

Source: https://btcpuzzle.info