* @[email protected]

Interesting:

"A 100% libre RISC-V + 3D GPU chip for mobile devices"

"The application for funding from NLnet and the Next Generation Internet initiative from the European Commission, from back in November of last year, has been approved. It means that we have EUR 50,000 to pay for full-time engineering work to be carried out over the next year, and to pay for bounty-style tasks. For the right people, with the right skills, there is money now available."

https://www.crowdsupply.com/libre-risc-v/m-class/updates/first-nlnet-grant-approved-to-fund-development

cc @orionwl

4 years in operation, still doing like 5-10 coinjoins a day just from my bot (I think there are about 60 active, typically), hundreds of millions (not exaggeration) of dollars worth of btc made more fungible, more than one academic paper analysing it ... but still everyone talks like Joinmarket either doesn't exist or is a dead project.

🤷‍♂️

A beautiful illustration of why relying on things like e2e encryption as solving privacy problems is a big mistake.
I believe two additional things are *both* necessary: partitioned identities and steganography.

https://www.privacyinternational.org/case-study/2997/betrayed-app-she-had-never-heard-how-truecaller-endangering-journalists

I've succcessfully figured out how to make manual coin control transactions with the lnd wallet over grpc (in Python, but I'll probably rewrite in golang). Will prob drop it on github shortly. Will require a PR on lnd though, although it's minor.

Longer term goal has been to do something like this: build a kind of 'sidecar daemon' that runs against lnd and passively coinjoins using 'SNICKER' (see it on my joinmarket.me blog). I've also done some PSBT code that may be useful in btcsuite/btcuti.

It's a good discussion about Jeremy Rubin's BIP proposal for a new opcode, CHECKOUTPUTSHASHVERIFY, aka COSHV, to be activated for Tapscript version 0. Goal is a minimum viable form of covenants.

https://github.com/JeremyRubin/bips/blob/op-checkoutputshashverify/bip-coshv.mediawiki

It's been rewarding to follow the ongoing review of the latest Bitcoin Optech newletter, kudos to @harding and everyone involved.

https://github.com/bitcoinops/bitcoinops.github.io/pull/149

To give a motivating example: you could create a macaroon that only allows the owner to spend up to 0.1btc and not more; and you could delegate that to a less secure server, or something.

Currently they don't have something as complicated as that, but they do have a macaroon specifically for generating invoices only (and not diddling with the wallet otherwise).

When Jonas says this, best to listen:

https://twitter.com/n1ckler/status/1133671925299982337

Working with and studying lnd a bit recently, I'm finding the topic of macaroons increasingly interesting. Here's an easily digestible overview of how lnd uses them:

https://github.com/lightningnetwork/lnd/blob/dadf13e2a32118cc7416e297142fdd0d0c94a6a5/docs/macaroons.md

Here's a simple crypto quiz question coming out of that: how is an HMAC different from a digital signature with the HMAC secret as private key? (note: 'simple'; there's nothing advanced here, and it's not a trick question!)

How to thrive with the return of higher fees. New video of Mike Schmidt of Blockstream and Bitcoin OpTech during Blockchain Week NYC earlier this month giving a 30 min overview on the Bitcoin fee market and how to mitigate higher fees:

https://www.youtube.com/watch?v=ihUQ4C42KUk

Great to see continually-improving RISC-V platform support in the latest release of Steel Bank Common Lisp (SBCL) http://www.sbcl.org/all-news.html?1.5.3#1.5.3

please don't use medium

maybe should have said mempool

ok bitcoin twitter everyone out of the pool less arguing more building