David A. Harding

@Bosch-0 > The current favicon displays the 'Bitcoin' icon branding where it should show the 'Bitcoin Core' branding (which this PR fixes). Does Bitcoin Core have a branding policy? I've...

Thanks to @hebasto for poking me to put more resources on the website that educate users about the need for, and benefits of, economically using your own full nodes. Also...

Realized this was accidentally based on an old branch and was showing 0.21.0 as the latest release; rebased to master with no code changes and confirmed it now correctly shows...

I suggest that you close this issue and reopen it as a PR to the site (e.g. as a blog post). You don't have to have any intention of ever...

@minium that description looks accurate to me. Thanks!

Finding active and quality contributors to a public website is hard, but I think we had modest success on Bitcoin.org through the simple expediency of, 1. We asked for help...

After the merge of this PR, the spec no longer describes what `htlc_maximum_msat` is for. E.g. none of these is informative, ``` $ git grep htlc_maximum_msat 07-routing-gossip.md: * [`u64`:`htlc_maximum_msat`] 07-routing-gossip.md:...

> the “must have exactly 2 330-satoshi outputs” i can just add another HTLC p2wsh 330 sats and your template is broken. I believe @ariard is correct: anchor-style commitment transactions...

Hi @RequestPrivacy . It does indeed look like the first script should use `OP_EQUALVERIFY`. Good catch, thanks!

I saw this being mentioned on Twitter and I wanted to note that cross-input signature aggregation is not something I believe is being worked on by @sipa and others for...