AshleyYatesV1R

Music

How to Attach Your self-hosted LNbits wallet to SEND/RECEIVE sats to/from SN

AnaCaseyZ03

IMO stuff that's offline. Not everything needs to connect to an app or a remote server. I mean both physical gadgets but also a lot of apps that could just work offline.

Bitkit Wallet AMA - John Carvalho, CEO of Synonym

FrederickDavilaOKN

> Personally, I’ll stop engaging or contributing on Delving Bitcoin [...]

the same way you stopped engaging and contributing to LN? lol

/s

bitcoin

Managing LN wallets liquidity

JenniferRussell7H1

The post is kind of begging... Bitcoin is all about proof of work. So next time show us some proof of work first.

But let's push this even further. I am a beer drinker too.
I know I am risking to be scammed with a new anon SN account.

I don't want to know who you really are, I don't care too much.
I care more for bitcoin adoption.

So...  let's make an experiment - push it forward. (@sn maybe this could be another cool daily post)
- find a bar that accept Bitcoin, near you - see btcmap.org
- ask to pay over LN for a beer
- take a screenshot of the QR invoice, or share it here
- record a video or at least some pictures of the whole process and share them here
- we will pay for your beer.

I did this with a lady from, UK, paying her coffee in a bar. And this was how she was onboarded into Bitcoin!
I said to the coffee shop owner: I will pay in sats the coffee for the first customer that enter and doesn't have sats to pay it. And I did it!
Then this lady created a nice webpage about this idea
https://www.kindnesscontagion.co.uk

bitdevs

[Daily puzzle] Probability of ending at 1

AliciaPeckOSU

> What do you hope it's like? 

More gradual building out of lightning services and adoption from merchants. Slow is smooth and smooth is fast.

> What do you fear its like?

Rapid adoption, because that probably means the dollar collapsed or totalitarian CBDC's got pushed through. Many people aren't even remotely ready for a switch to Bitcoin and we would see lots of lost wealth from mishandling.

> What products do you think we'll see?

I expect more and more alternatives to Big Tech platforms, especially as censorship season ramps up in America.

> Where are the loud voices in Bitcoin wrong?

Carnivore diet, but that's pretty tangential to all the important things they're getting right.

Ask the River team anything you want to know about Lightning, Bitcoin, or seed oils. 

River AMA 

**Introduction** 
By now, the story of Mt. Gox is coming to a close. Once the lawsuits are settled, it seems this chapter of Bitcoin History will be finished. Many people know Mt. Gox and what happened (they used an insecure password, got hacked and lost thousands of Bitcoin).

But did you know Mt. Gox had made some oopsies in the past too? They were one of the first victims of the transaction malleability attack (https://en.bitcoin.it/wiki/Transaction_Malleability). From what I can tell, some attackers withdrew Bitcoin from Mt. Gox, then malleated the transaction such that the transaction ID would change. At this point Mt. Gox would see that the withdrawal never went through (the tx ID they had in their system is no longer in the mempool or in any block), and so they would start another withdrawal.

I think one of the most interesting displays of Mt. Gox's incompetence is when they destroyed around 2000 Bitcoin in a single block due to one mistake. The infamous block 150,951 has losses totalling over 2600 Bitcoin that can't ever be recovered.

**Inside one of the transactions**
By far the biggest loss was in the transaction [aa62bdd690de061a6fbbd88420f7a7aa574ba86da4fe82edc27e2263f8743988](https://mempool.space/tx/aa62bdd690de061a6fbbd88420f7a7aa574ba86da4fe82edc27e2263f8743988), which destroyed 367.758 BTC
![](https://i.imgur.com/WLQTAow.png)

Notice anything strange? Lets inspect the UNKNOWN output further:
![](https://i.imgur.com/cyGIn6b.png)

If you're familiar with Bitcoin Script, you might have spotted the issue already. For those not in the know, let me briefly explain what happened. A normal P2PKH output's locking script looks like this:

-  Compute the hash of the public key that was put on the stack
- If the public key hash matches, then check that there is a valid signature on the stack for that public key
- If these conditions are met, you can spend the output!

But.. that's not what this output does. Instead of pushing a public key hash to the stack, it simply pushes a 0. So what this output is saying is: If you can provide a public key that hashes to **0**, and you have a valid signature for that public key, you can spend it.

But there is no public key that hashes to 0! Even if we were to start finding it, it'd take us far longer than the heat death of the universe to find such a special key. Thus this output is *unspendable*. Infact it gets even worse; as far as I can tell OP_0 pushes a single byte to the stack. A RIPEMD-160 hash is 20 bytes. So this script is just not valid at all, because OP_EQUALVERIFY would always be false (comparing a 20 byte value to a 1 byte value). 

Thus this, and all other similarly malformed transactions in this block are unspendable. Here's a list (thanks bitcoin-supply.com):

![](https://i.imgur.com/zDYDuhE.png)

