<laanwj>
from a more holistic point of view about "bitcoin privacy" i don't think something like onlynet contributes much
<prayank>
michaelfolkson: Agree that privacy wiki has lot of interesting things. I respect Chris Belcher for his contributions in improving Bitcoin Privacy. The docs I was talky about were only for Bitcoin Core. Mainly Tor, i2p, wallet etc. This privacy wiki also needs some updates: Dandelion should be removed, i2p needs to be added, lot of things related to Tor (you can write few pages on just `onlynet`). Anyways it's just a suggestion.
<bitcoin-git>
[bitcoin] theStack opened pull request #22805: refactor: use CWallet const shared pointers in dump{privkey,wallet} (master...202108-refactor-const_correctness_for_further_dump_methods) https://github.com/bitcoin/bitcoin/pull/22805
<prayank>
Problem with Stackexchange and other places is you can write with more freedom and sometimes wrong things may not get noticed which in few years become a practice. Example: second paragraph in this comment by Greg Maxwell https://github.com/bitcoin/bitcoin/issues/17491#issuecomment-705485718
<laanwj>
(of course there are different perspectives, some people mean 'privacy' as in 'hiding that you're running a bitcoin node in the first place' which is... very difficult if impossible with overlay networks)
<michaelfolkson>
jonatack: Oh yeah :facepalm: I completely forgot about belcher's awesome privacy wiki. https://en.bitcoin.it/wiki/Privacy
<laanwj>
general privacy advice about using bitcoin spans much further than just using an overlay network, the most privacy-relevant in that regard is what you use to broadcast transactions
<jonatack>
that's true, the wiki is being used for repo project management. an article on your personal blog or website or (good point) on BitcoinStackExchange seems good, or https://en.bitcoin.it (still maintained?)
<bitcoin-git>
bitcoin/22.x c1c79f4 W. J. van der Laan: doc: Stop nixing `-` in manual pages
<bitcoin-git>
bitcoin/22.x 86de567 W. J. van der Laan: doc: Manual pages update for rc3
<bitcoin-git>
[gui] hebasto merged pull request #403: refactor: Make paths to update Encryption and HD wallet statuses simpler (master...210811-hd) https://github.com/bitcoin-core/gui/pull/403
<jonatack>
fanquake: i'm doing what i can to help them. that's the only reason for the docs. there are maybe ~30 users who have set up I2P with bitcoin, but i've heard from many of them.
<gribble>
https://github.com/bitcoin/bitcoin/issues/22647 | If both options "onion" and "proxy" are unset, no outbound Onion connections should be made · Issue #22647 · bitcoin/bitcoin · GitHub
<wired>
so you're a Bitcoin developer?
<bitcoin-git>
[bitcoin] klementtan opened pull request #22804: validation: GuessVerificationProgress returns 0 when no blocks downloaded (master...verification_progress_fix) https://github.com/bitcoin/bitcoin/pull/22804
<laanwj>
this is the development channel not bitcoin 101 channels
<kalle>
midnight: I don't think there was a bips channel, and I feel like a non-core-focused dev channel would be nice to have, at least. Whoever the genie is, I propose we try restoring #bitcoin-dev. :)
<Yihen>
The script system is the engine of Bitcoin transactions, and I am very interested in miniscript.
<Yihen>
does it need to compile to bitcoin OP_CODE script?
<Yihen>
is it a new script for bitcoin?
<midnight>
I think the idea was that #bitcoin-dev was killed thanks to rando jgarzik, so I guess they assumed it was toxic-- so they just put +f #bitcoin on it.
<kalle>
Is it possible to set up #bitcoin-dev channel somehow? Would like to discuss BIP process and that channel would've probably been ideal, as it's not a core thing and #bitcoin is not focused on development.
<bitcoin-git>
[bitcoin] aitorjs opened pull request #22797: docs: tx_orphan_no_fee and tx_orphan_invalid dont exist as transactions in p2p_invalid_tx.py (master...master) https://github.com/bitcoin/bitcoin/pull/22797
<bitcoin-git>
[bitcoin] glozow opened pull request #22796: RBF move (1/n): extract BIP125 Rule 5 into policy/rbf (master...2021-08-rbf-1) https://github.com/bitcoin/bitcoin/pull/22796
<michaelfolkson>
sipa: Yeah it won't let me do bitcoin-cli stop on my signet, testnet nodes :)
<sipa>
michaelfolkson: if you change the passphrase without restarting, bitcoin-cli will read the new one, but bitcoind will still be using the old one, so it'll likely stop working until you restart
<michaelfolkson>
Does a bitcoin.conf in the testnet3/signet directory work if there is no bitcoin.conf in .bitcoin? I'll have to try
<michaelfolkson>
Didn't know you had to stop mainnet, testnet and signet node (assuming running them in parallel) to change the bitcoin.conf
<michaelfolkson>
bitcoin.conf in .bitcoin controls mainnet, testnet, signet nodes etc. Would it not make more sense to have a bitcoin.conf in the testnet3/signet directory controlling the testnet/signet node?
<laanwj>
(i've, for example, redirected c-lightning's and bitcoin RPC over ssh verious times to get remote access to them)
<bitcoin-git>
[bitcoin] meshcollider merged pull request #22781: wallet: fix the behavior of IsHDEnabled, return false in case of a blank hd wallet. (master...fix_ishdenabled) https://github.com/bitcoin/bitcoin/pull/22781
<bitcoin-git>
bitcoin/master 8733a8e Saibato: the result of CWallet::IsHDEnabled() was initialized with true.
<bitcoin-git>
bitcoin/master 3755dea Samuel Dobson: Merge bitcoin/bitcoin#22781: wallet: fix the behavior of IsHDEnabled, retu...
<Bullit>
recall listtransactions as a command from japan and return 8.533fractal bitcoin to 3KWmEuAXy8HauiZRhUJLVdn4eFKvoGCtap split Recall Protocol Controller invalid adress
<bitcoin-git>
[bitcoin] lsilva01 opened pull request #22794: test: Split rpc_invalid_address_message test into two (master...split_invalid_address_message_test) https://github.com/bitcoin/bitcoin/pull/22794
<S3RK>
but in bitcoin-core CLI is just a thin proxy. Which begs the question whether it's a serious user-facing interface or not
<gribble>
https://github.com/bitcoin/bitcoin/issues/22775 | rpc: Add option to list transactions from oldest to newest in `listtransactions` RPC command by ben-kaufman · Pull Request #22775 · bitcoin/bitcoin · GitHub
<bitcoin-git>
[bitcoin] achow101 opened pull request #22793: Simplify BaseSignatureChecker virtual functions and GenericTransactionSignatureChecker constructors (master...refactor-sig-checker) https://github.com/bitcoin/bitcoin/pull/22793
<bitcoin-git>
[bitcoin] Zero-1729 opened pull request #22790: test: add aarch64-apple-darwin platform entry to get_previous_releases (master...add-aarch64-apple-darwin-get-prev-releases) https://github.com/bitcoin/bitcoin/pull/22790
<bitcoin-git>
[bitcoin] theStack opened pull request #22789: external_signer: improve fingerprint matching logic (stop on first match) (master...202108-external_signer-improve_fingerprint_matching) https://github.com/bitcoin/bitcoin/pull/22789
<bitcoin-git>
[bitcoin] MarcoFalke opened pull request #22788: scripted-diff: Use generate* from TestFramework (master...2108-testGenDiff) https://github.com/bitcoin/bitcoin/pull/22788
<bitcoin-git>
bitcoin/master 1bbe289 W. J. van der Laan: Merge bitcoin/bitcoin#22565: [script] signet's getcoins.py improvements
<bitcoin-git>
[bitcoin] Saibato opened pull request #22781: wallet: fix the behavior of IsHDEnabled, return false in case of a blank hd wallet. (master...fix_ishdenabled) https://github.com/bitcoin/bitcoin/pull/22781
<laanwj>
sipa: yeah, true, it's just that we now have squashed most of the usability issues in bitcoin-cli (after the libevent switch), that would basically start over
<sipa>
iirc, my suggestion at the time was just dropping libevent for bitcoin-cli, as bitcoind-compatible-httpd should be very simple to implement by hand :)
<bitcoin-git>
[bitcoin] darosior opened pull request #22779: policy: correct (lower) the dust threshold for Taproot outputs (master...taproot_dust_limit) https://github.com/bitcoin/bitcoin/pull/22779
<laanwj>
if you don't care about bitcoin-cli (e.g. use it from python) server-side might be enough thogh
<laanwj>
so we basically cannot do it, at least in bitcoin-cli, without some really ugly hacks around libevent
<Randolf>
videre_e: This is the development channel. For mining questions, please ask in the #bitcoin-mining channel instead: /join #bitcoin-mining
<bitcoin-git>
bitcoin/master 6bb5470 nthumann: util: Check if specified config file cannot be opened
<bitcoin-git>
[bitcoin] glozow closed pull request #22252: policy: Trim Packages when transaction with same txid exists in mempool (master...2021-06-mempool-matches) https://github.com/bitcoin/bitcoin/pull/22252
<bitcoin-git>
[bitcoin] jnewbery opened pull request #22777: net processing: don't request tx relay on feeler connections (master...2021-08-feeler-no-frelay) https://github.com/bitcoin/bitcoin/pull/22777
<bitcoin-git>
[bitcoin] fanquake merged pull request #22275: A few follow-ups for taproot signing (master...202106_taproot_sign_followup) https://github.com/bitcoin/bitcoin/pull/22275
<bitcoin-git>
[bitcoin] ben-kaufman opened pull request #22775: rpc: Add option to list transactions from oldest to newest in `listtransactions` RPC command (master...listtransactions-set-order) https://github.com/bitcoin/bitcoin/pull/22775
2021-08-22
<laanwj>
but lets move GUI discussion to #bitcoin-core-gui
<laanwj>
i think what projects like umbrel do right is to treat core as a component, not as something that should absorb or include all the other functionality, they make it more user friendly by offering things like web guis and a way to install and manage everything bitcoin related as a suite
<bitcoin-git>
[bitcoin] mzumsande opened pull request #22772: refactor: hasher cleanup (follow-up to 19935) (master...202108_hasher_cleanup) https://github.com/bitcoin/bitcoin/pull/22772
<prayank>
laanwj: Are these ever discussed before? 1. Bitcoin Core web console like i2p has a webpage at 127.0.0.1:7070. We could add lot of thing in it that are normally rejected for qt. Example: Mempool charts and other charts (basics) 2. Plugins for qt like Electrum
<bitroach>
I can add Github integration to the Bitcoin Forum pretty easily, lets see how you guys will like the forum first ;)
<bitcoin-git>
[bitcoin] MarcoFalke opened pull request #22769: fuzz: Use LIMITED_WHILE instead of limit_max_ops (master...2108-fuzzRefactor) https://github.com/bitcoin/bitcoin/pull/22769
<bitroach>
I open the forum soon as I published the Bitcoin paper in markdown (I did just had some issue with the database what I fixed) also by default all users has end-to-end encrypted PMs enabled which based on BIP-39, PMs can't be scanned by the AI as you imagine because of the strong encryption
<bitroach>
the current Bitcoin environment like r/Bitcoin the IRC channels like this one as well the GitHub repo and the theymos and cobrabitcoin run Bitcoin sites are brutally censored and extremely centralized in the hands of a few, I'm the person who going to change that and nobody can do absolutely nothing to stop what is coming
<bitroach>
Artifical Intelligence also deployed on the Bitcoin Forum so trolls has no chance, they post will be hidden by the AI soon as they click the submit button
<bitroach>
both Bitcoin Core discussions and Bitcoin Cash discussions are welcome to the Bitcoin Forum, I'm only going to censor those who in any way advocate for Blockstream
<bitroach>
Bitcoin Cash is still Bitcoin, possibly even more than the current Bitcoin Core
<bitroach>
Just to make it clear, I allow Bitcoin Cash to be on the Bitcoin Forum, why would I censor Roger Ver and Kim DotCom?
<bitroach>
funny isn't? I offering thousands of dollars + working on a Bitcoin Forum and I get attacked, banned and censored on IRC
<bitroach>
I even offered over 20% donation to Bitcoin Core from all the forum related income, I talked with luke-jr and I would only pay to him nobody else, we didn't agree in the terms yet I just offered a cut
<bitroach>
I'm open for helping Bitcoin Core Developers by allowing them to join the Bitcoin Forum, Bitcoin Core Developers have exclusive right to post and moderate the Development category on the forum. At one point I considered to approve all signups with @bitcoincore.org emails and grant them developer badges, but after that my domain is censored on IRC I changed my mind pretty quickly. currently the only person I respect is luke-jr,
<bitcoin-git>
[bitcoin] n-thumann opened pull request #22768: script: Add commits signed with sipas expired key to allow-revsig-commits (master...add_sipa_expired_key_signed_commits) https://github.com/bitcoin/bitcoin/pull/22768
<bitroach>
I'm not theymos bud, I don't hide and certainly not scamming and stealing 11,000 Bitcoin
<bitroach>
I'm definitely going to call Bitcoiners to abandon all Bitcoin related IRC channels because run by fucktards who censor it
<bitroach>
well, turned out that Zoltan controls the Bitcoin Forum, keep bullshitting and each of you will be doxed in a nice topic
<bitroach>
you can clearly see that by linking my Bitcoin Forum
<bitroach>
American anti-chinese anti-russian motherfuckers pushing for propaganda even on Bitcoin related IRC channels
<bitroach>
if any ops trolling the forum I will publish a topic and will call Bitcoin Core developers terrorists
<bitroach>
let me absolutely clear, none of you welcome on the Bitcoin Forum and I find any of you (talking about the ops on these channels) will be immediately kicked banned from the Bitcoin Forum
<bitroach>
you can't link a bitcoin forum without approval from the motherfuckers who think they own Bitcoin
<bitroach>
I getting kicked from these channels because I own the bitcoin.forum domain if you link https://bitcoin.forum you will be immediately kicked from these channels
<michaelfolkson>
bitroach: If you get kicked from #bitcoin you can move to another channel or set up your own channel. But this definitely isn't the right channel for general ranting.
<bitroach>
I just compiled Bitcoin Core on another server I own with --disable-wallet and --without-gui yet when I go to the .bitcoin folder there is a folder called wallets
<bitroach>
Gavin Andresen's access to the GitHub repository revoked and all kinds of shit merged to Bitcoin Core without any vote whatsoever
<bitroach>
they not forked the repository, they paid out millions of dollars to merge they crap to Bitcoin core
<bitroach>
why segwit or taproot can't be a fork outside of Bitcoin Core?
<bitroach>
little bit of money here and there and all developers agree to merge crap and destroy Bitcoin
<bitroach>
they trolled Bitcoin Core
<bitroach>
basically with segwit and now with taproot blockstream totally taken over the Bitcoin core repository on GitHub
<bitroach>
I have all right to be outraged about this blockstream crap and the propaganda on the Bitcoin repository on GitHub
<bitroach>
#bitcoin is censored, in fact all bitcoin related channel, forums even github is censored
<bitroach>
segwit and taproot is merged to Bitcoin core because devs working for blockstream inc
<meshcollider>
bitroach: you should move to #bitcoin, but most of the devs aren't employed by blockstream, no. There's a big variety in developer funding (volunteers, grants, sponsorship, patreon, employment, etc.)
<bitroach>
I believe that Bitcoin is in danger, number 1, it is controlled by a very few people when there are way better engineers in the world, number 2, these so called "developers" working for various corporations not only to Blockstream Inc, example Amazon and Google
<bitroach>
isn't Bitcoin supposed to be independent from corporations and governments?
<bitroach>
Blockstream Inc's payees merged segwit and now they merging taproot too into the Bitcoin core software
<bitroach>
does Bitcoin core developers get paid by Blockstream inc?
<bitroach>
I have some questions regarding Bitcoin development
<bitcoin-git>
[bitcoin] ryanofsky opened pull request #22766: refactor: Clarify and disable unused ArgsManager flags (master...pr/argscripts) https://github.com/bitcoin/bitcoin/pull/22766
<bitcoin-git>
[bitcoin] hebasto opened pull request #22764: build: Include qt sources for parsing with extract_strings.py (master...210821-translation) https://github.com/bitcoin/bitcoin/pull/22764
<bitcoin-git>
[bitcoin] prakash1512 opened pull request #22763: fuzz: execute each file in dir without fuzz engine (master...issue-21461-execute-file-without-fuzz-engine) https://github.com/bitcoin/bitcoin/pull/22763
<bitcoin-git>
[bitcoin] MarcoFalke opened pull request #22762: Raise InitError when peers.dat is invalid or corrupted (master...2108-InitErrorAddrmanCorrupt) https://github.com/bitcoin/bitcoin/pull/22762
<robertspigler>
prayank: If you're trying to build a private tx broadcasting scheme into bitcoin, we need to come up with something more complete. Like Dandelion with DoS issues figured out
<prayank>
No. Because I am trying to improve privacy of Bitcoin Core (ipv4) nodes and not create another privacy project for broadcasting transactions.
<bitcoin-git>
[bitcoin] MarcoFalke opened pull request #22757: test: Use boost::unit_test::enable_if<RUN_RAII_EVENT_TESTS> (master...2108-testEnableIf) https://github.com/bitcoin/bitcoin/pull/22757
<bitcoin-git>
[bitcoin] MarcoFalke merged pull request #22707: test: refactor use of getrawmempool in functional tests for efficiency (master...test_improve_mempool_updatefromblock_efficiency) https://github.com/bitcoin/bitcoin/pull/22707
<bitcoin-git>
bitcoin/master 86dbd54 Michael Dietz: test: improve mempool_updatefrom efficiency by using getmempoolentry for s...