[bitcoin] dongcarl opened pull request #24332: [kernel 2/n] Decouple from `netaddress`+`asmap`, parts of `timedata`+`init/common` (master...2022-02-libbitcoinkernel-p2-minimal) https://github.com/bitcoin/bitcoin/pull/24332
bitcoin/master 5f7f2f7 fanquake: Merge bitcoin/bitcoin#24241: doc: cleanup doc on need of Developer Account...
prayank: the bitcoin-dev list has greylisting active. messages from new emails will be in a moderation queue and need to be manually approved before being sent to the list. messages that are not approved will appear here: https://lists.ozlabs.org/pipermail/bitcoin-dev-moderation/ I don't see the email in question there, so it's probably just still in the queue waiting for someone to get to it
belcher: I am not sure why merchange and customer is used in this example it can be any peer1 and peer2 or alice-bob. If bitcoin was used for merchant and customer thing today maybe this thing was already solved.
indeed the very first payjoin BIP was written by the operator of a bitcoin casino whos customers kept getting banned because they transferred coins straight from a kyc exchange to the casino
much more useful would be to ask places like bitcoin casinos, p2p exchanges and individual web stores to adopt payjoin
Kaizen_Kintsugi_: Perhaps #bitcoin-core-pr-reviews is better channel for these types of general questions. But with Schnorr we can do key aggregation schemes (e.g. MuSig2) but not signature aggregation across say inputs
provoostenator: E.g. ./src/bitcoin-chainstate ./test-datadir (This is a draft PR please don’t use it on your actual datadir).
provoostenator: bitcoin-chainstate does do something! It will print out information about a datadir and wait for new blocks (encoded in hex) to process on stdin. I found it pretty cool to start it and start feeding it block 1, 2, 3, and see it work :-)
Right, I think in practice libbitcoinkernel will probably be a subset of bitcoin-node (is that the right binary?), as in bitcoin-node can link against libbitcoinkernel (not proposing that we do this yet)
michaelfolkson: It was sarcasm for some privacy wallets writing non sense that affect privacy of Bitcoin in general but nobody wants to talk about it. I understand your point and no disagreement.
laanwj: In my mind, bitcoin-chainstate is more of a demo executable, one which makes sure that we're linking in everything we need and surfaces our dependency tree. I think it'll be nice to have a few of these demo executables as guiding "north stars" so we can see how ergonomic (or rather, un-ergonomic) libbitcoinkernel is right now, and how it
Basically bitcoin-chainstate is a binary that, upon invocation with a datadir path as the first argument, will load the datadir, print out information about it, then wait for blocks (encoded in hex) on stdin to call ProcessNewBlock on. THE PROBLEM is that when I start with an empty datadir, and feed it block 1 and block 2, then exit, the next time
Coin Control is important and should always remain part of bitcoin wallets that care about privacy. If UX needs to be improved there can be a checkbox in settings to disable it. Or if wallet has no coin control but cluster control, removing it will not reduce errors it will change nature of errors and create new issues.
Sorry if this looks offtopic because of link but concept is ontopic. After working on several privacy related PRs in Core and then WW2 I realized core is not that bad with no marketing and coinjoin. Privacy is expressing yourself selectively. Everything is public on Bitcoin but if user wants to share links of transactions with less people that is privacy.