<bitcoin-git>
[bitcoin] hebasto opened pull request #23463: ci: Increase --timeout-factor in the native Windows CI task (master...211107-timeout) https://github.com/bitcoin/bitcoin/pull/23463
<dougefish>
Is here any reason why we don't volume mount the qa-assets directory from the host into the running container? (https://github.com/bitcoin/bitcoin/blob/master/ci/test/04_install.sh#L42). If one is doing fuzz testing with CI scripts and you stop the container you have to re-download this huge repo again.
<satoshi>
Also don't forget what happened to Gavin Andresen just before Blockstream Inc started enforcing protocol changes! Bitcoin is dead for more than 4 years already. Thank you very much!
<satoshi>
hiring some indian women from Google to work on Bitcoin core doesn't makes Bitcoin Core less white-supremacist, they only hired those women to able to say "look we are not that white at all".
<satoshi>
it is very unfortunate to see in less than a decade Bitcoin turned into a white-supremacist tool developed by real neo-nazis who residing in NATO memberstates only
<satoshi>
Is not that there are isn't any C++ programmer in China, Russia or elsewhere outside of NATO-member states... it is solely about that the Bitcoin repository is run by Blockstream Inc and white supremacist motherfuckers who loves NATO bombings in Afghanistan, Iraq and many other countries. All of them are whiter than snow. Bitcoin Core has ZERO tolerance against the best C++ programmers from China. They hate Chinese and any other
<satoshi>
White-supremacist motherfucker neo-nazis running the Bitcoin repository on GitHub
<satoshi>
Show me any "Bitcoin core developer" who is from China, Russia, Japan, Korea, Vietnam... The reason why you can't is because ONLY residents of NATO member-states or they allied countries can ever gain access to the bitcoin repository on GitHub.
<satoshi>
the bitcoin repository on github run by American, Asutralian and NATO sympathizer neo-nazi terrorists
<satoshi>
fanquake is an annoying person who shouldn't have access to the GitHub repository, he is using the "bitcoin" account first and only after his own, trying to suggest he owns Bitcoin.
<bitcoin-git>
[bitcoin] fanquake opened pull request #23450: doc: update SECURITY.md inline with recent changes to bitcoincore.org (master...update_sec_md) https://github.com/bitcoin/bitcoin/pull/23450
<bitcoin-git>
[bitcoin] RandyMcMillan opened pull request #23449: contrib/install_db4.sh: check if tar exists (master...install-db4-check) https://github.com/bitcoin/bitcoin/pull/23449
2021-11-05
<bitcoin-git>
[bitcoin] lsilva01 opened pull request #23448: refactor, consensus: remove calls to global `Params()` in validation layer (master...remove_call_params) https://github.com/bitcoin/bitcoin/pull/23448
<bitcoin-git>
[bitcoin] laanwj opened pull request #23446: doc: Mention that BerkeleyDB is for legacy wallet in build-unix (master...2021-11-unix-build-doc-legacy) https://github.com/bitcoin/bitcoin/pull/23446
<bitcoin-git>
[bitcoin] martinus opened pull request #23439: Open streams_test_tmp file in temporary folder (master...2021-11-allow-concurrent-streams_buffered_file_rand) https://github.com/bitcoin/bitcoin/pull/23439
<satoshi>
Would correct myself, the current version number should be Bitcoin 0.22.0. Reaching 0.99 is not that far in future, Reaching 1.0.0 would have the CLIENT_VERSION 1 million. It makes more sense to me, than reaching 99.0 in 15 years. This is not a rush for highest CLIENT_VERSION.
<bodom>
Hi there! I am trying to understand an hex scriptpubkey: "6a04665678a0" bitcoin core API decodes it into ASM as "OP_RETURN -544757350" but, to my understanding, it should be "OP_RETURN -1602726298". Where i am wrong? This is driving me crazy.
<TallTim>
hmm, ran fsck on a linux box that bitcoin core was getting "database read error" on but its clean. Blew out the chainstate/blocks directories, forced full resync, chokes around 7yrs in. Odd.
<bitcoin-git>
[bitcoin] hebasto opened pull request #23403: test: Fix segfault in the psbt_wallet_tests/psbt_updater_test (master...210331-psbt) https://github.com/bitcoin/bitcoin/pull/23403
<bitcoin-git>
bitcoin/master 7efc628 fanquake: Merge bitcoin/bitcoin#23385: refactor: get wallet path relative to wallet_...
<bitcoin-git>
[bitcoin] brunoerg opened pull request #23392: test: move check_node_connections to util (master...2021-10-check-node-connections) https://github.com/bitcoin/bitcoin/pull/23392
2021-10-29
<bitcoin-git>
[bitcoin] greenaddress opened pull request #23387: WIP: add support to save fee estimates without having to shut down the node (master...dump_fee_estimates) https://github.com/bitcoin/bitcoin/pull/23387
<bitcoin-git>
[bitcoin] mjdietzx opened pull request #23385: refactor: get wallet path relative to wallet_dir (master...refactor-get-relative-wallet-path) https://github.com/bitcoin/bitcoin/pull/23385
<bitcoin-git>
[bitcoin] Sjors closed pull request #22260: Make bech32m the default for RPC, opt-in for GUI (master...2021/06/bech32_gui) https://github.com/bitcoin/bitcoin/pull/22260
<bitcoin-git>
[bitcoin] vasild closed pull request #23382: addrman: bump peers.dat format version number (master...addrman_format_bump_multiaddr) https://github.com/bitcoin/bitcoin/pull/23382
<bitcoin-git>
[bitcoin] vasild opened pull request #23382: addrman: bump peers.dat format version number (master...addrman_format_bump_multiaddr) https://github.com/bitcoin/bitcoin/pull/23382
<bitcoin-git>
[bitcoin] glozow opened pull request #23381: validation/refactor: refactoring for package submission (master...2021-10-validation-refactors) https://github.com/bitcoin/bitcoin/pull/23381
<bitcoin-git>
[bitcoin] jnewbery opened pull request #23380: addrman: Fix AddrMan::Add() return semantics and logging (master...2021-10-addrman-add-logging) https://github.com/bitcoin/bitcoin/pull/23380
<laanwj>
luke-jr: so your win32 cross-compile of bitcoin core using the standard mingw-w64 compiler of ubuntu focal, crashes?
<bitcoin-git>
[bitcoin] theStack opened pull request #23375: test: MiniWallet: more deterministic coin selection for coinbase UTXOs (oldest first) (master...202110-test-MiniWallet-deterministic_coin_selection_oldest_first) https://github.com/bitcoin/bitcoin/pull/23375
<bitcoin-git>
[bitcoin] vasild opened pull request #23373: Parse command line arguments from unit and fuzz tests, make addrman consistency check ratio easier to change (master...checkaddrman_in_tests) https://github.com/bitcoin/bitcoin/pull/23373
<bitcoin-git>
[bitcoin] MarcoFalke merged pull request #23305: test: refactor: add `script_util` helper for creating bare multisig scripts (master...202110-test-add_helper_for_bare_multisig_scripts) https://github.com/bitcoin/bitcoin/pull/23305
<bitcoin-git>
[bitcoin] theStack opened pull request #23371: test: MiniWallet: add P2TR support and use it per default (master...202110-test-MiniWallet-change_P2WSH_to_P2TR) https://github.com/bitcoin/bitcoin/pull/23371
<MarcoFalke>
sipa: 2021-10-25T15:04:09Z Error: Invalid or corrupt peers.dat (Corrupt data. Consistency check failed with code -5: iostream error). If you believe this is a bug, please report it to https://github.com/bitcoin/bitcoin/issues. As a workaround, you can move the file ("/tmp/regtest/peers.dat") out of the way (rename, move, or delete) to have a new one created on the next start.
<bitcoin-git>
[bitcoin] MarcoFalke merged pull request #23306: Make AddrMan support multiple ports per IP (master...202110_addrmanmultiport) https://github.com/bitcoin/bitcoin/pull/23306
<sipa>
that implies bitcoin core would not consider that address as its own
2021-10-24
<bitcoin-git>
[bitcoin] hebasto opened pull request #23349: util: Use FEATURE_LATEST for wallets created with bitcoin-wallet (master...211024-bw-version) https://github.com/bitcoin/bitcoin/pull/23349
<bitcoin-git>
[bitcoin] hebasto opened pull request #23348: rpc, wallet: Do not return "keypoololdest" for blank descriptor wallets (master...211024-rpc-gwi) https://github.com/bitcoin/bitcoin/pull/23348
<prayank>
But I smiled on energy question instead of reacting in a weird way. Said I will cover this in my presentation later and I can assure Bitcoin has no energy issues.
<prayank>
I might sound negative at times while reading things however intentions were always to imrove Bitcoin.
<bitcoin-git>
[bitcoin] hebasto opened pull request #23346: util, refactor: Improve headers for bitcoin-wallet tool (master...211024-bw-headers) https://github.com/bitcoin/bitcoin/pull/23346
<bitcoin-git>
[bitcoin] hebasto opened pull request #23345: build: Drop unneeded dependencies for bitcoin-wallet tool (master...211024-bw-deps) https://github.com/bitcoin/bitcoin/pull/23345
<hebasto>
guest3456: provided data are not enough to give you a 100% working solution, but generally it is more reliable to move into an external drive a blocks dir only; it is easy to achieve by placing `blocksdir="path-to-external-drive/new-blocks-dir` into your `bitcoin.conf`