< December 2023 >
Su Mo Tu We Th Fr Sa 123456789
10 11 12 13 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28 29 30
31
2021-12-18
<bitcoin-git>
[bitcoin] darosior opened pull request #23815: wallet: watchonly support for Miniscript descriptors (master...miniscript_wallet_watchonly) https://github.com/bitcoin/bitcoin/pull/23815
<bitcoin-git>
bitcoin/master 507c009 Hennadii Stepanov: test: Fix "echo" subtest in the system_tests for Windows
<bitcoin-git>
bitcoin/master 0aad33d Hennadii Stepanov: test: Fix "false" subtest in system_tests for Windows
<bitcoin-git>
bitcoin/master fb1b059 Hennadii Stepanov: test: Fix "non-zero exit code" subtest in system_tests for Windows
<bitcoin-git>
[bitcoin] hebasto opened pull request #23814: ci: Bump the macOS image to the latest Monterey (master...211218-monterey) https://github.com/bitcoin/bitcoin/pull/23814
<bitcoin-git>
[bitcoin] fjahr opened pull request #23813: Add test and docs for getblockfrompeer (master...2021-12-getblockfrompeer-follow-up) https://github.com/bitcoin/bitcoin/pull/23813
<bitcoin-git>
[bitcoin] mzumsande opened pull request #23812: test: fix intermittent failures in p2p_timeout.py (master...202112_p2p_timeout_fix) https://github.com/bitcoin/bitcoin/pull/23812
<bitcoin-git>
[bitcoin] fanquake opened pull request #23811: scripts: match on `EXE_FORMATS` rather than name string (master...sec_check_match_type) https://github.com/bitcoin/bitcoin/pull/23811
<laanwj>
PSA: as it was clear that fanquake has overwhelming support i've made him an admin of the bitcoin and bitcoin-core organizations
<bitcoin-git>
[bitcoin] PastaPastaPasta opened pull request #23810: refactor: destroy all C-style casts; use modern C++ casts, enforce via `-Wold-style-cast` (master...c-style-cast) https://github.com/bitcoin/bitcoin/pull/23810
<bitcoin-git>
bitcoin/master 97b2fc0 fanquake: Merge bitcoin/bitcoin#23803: ci: Disable s390x gui tests for now
<bitcoin-git>
[bitcoin] jb55 opened pull request #23809: tracing: reduce instructions generated by net:inbound_message tracepoint (master...conntype-enum-usdt) https://github.com/bitcoin/bitcoin/pull/23809
2021-12-17
<jb55>
btw satellite doesn't need to be a bitcoin fork right? couldn't it just be a block-from-space decoder + call submitblock? or is there more to it?
<sipa>
But Bitcoin Core works fine with tor itself, and tor itself also works with browsers.
<sipa>
Yes, he needs a way to communicate with Bitcoin Core. The altnet stuff goes in the direction of providing that functionality. As I said, I conceptually agree with that. I still don't see the point of node-tor, but if there is more functionality for interacting with separate networks, and someone makes it work with node-tor, sure...
<sipa>
That's all very reasonable, but I don't think that has much to do with Bitcoin Core.
<prayank>
sipa: Reason IIUC he doesn't like the way Tor project uses Tor protocol and its flaws etc. but wants to make a better to for different projects and bitcoin is one of them
<jb55>
so basically a way to feed network messages in and out as plaintext, turn bitcoin into a pure function?
<prayank>
sipa: what I understood based on his emails. he likes browsers, js and world around it. so webtorrents kind of things for bitcoin nodes. He is from france, he is good with his project but unable to express or get funding. IDK just wanted to share it here once so that people like you who know better would be able to see if it helps bitcoin at some point. Everything is moving to browsers tbh and this is not about altcoins. I work
<sipa>
But again, while I conceptually agree with making it easier to connect bitcoin nodes in more different ways with eachother, I don't understand the point of node-tor.
<sipa>
I don't think that's at all what he's talking about. He's saying that the communication between bitcoin core and node-tor (if it were to use node-tor rather than actual tor) would not use SOCKS.
<prayank>
hmm tbh I am not the best person to comment anything on this. I liked the idea and his follow up on mailing list. What I understand is: we do bitcoin nodes from browsers similar to one PoC by bcoin but its not safe for production. And this guy wants to make it interesting by using tor protocol for everything. I have issues with JS and WebRTC but if it can help bitcoin nodes usage I dont mind and maybe not full nodes or somethin
<sipa>
I conceptually like having more mechanisms for connecting bitcoin nodes though, so if there were a viable network like that to use as an additional one - sure why not.
<sipa>
I don't understanding anything about node-tor, or why you'd want to use a separate tor network for just bitcoin traffic. That completely defeats the purpose.
<bitcoin-git>
[gui] hebasto opened pull request #509: Respect dialog modality and fix a regression in wallet unlock (master...211217-unlock) https://github.com/bitcoin-core/gui/pull/509
<bitcoin-git>
[bitcoin] glozow opened pull request #23804: validation: followups for de-duplication of packages (master...2021-12-dedup-packages) https://github.com/bitcoin/bitcoin/pull/23804
<bitcoin-git>
[bitcoin] laanwj merged pull request #22704: fuzz: Differential fuzzing to compare Bitcoin Core's and D. J. Bernstein's implementation of ChaCha20 (master...diff-fuzz-chacha20) https://github.com/bitcoin/bitcoin/pull/22704
<bitcoin-git>
bitcoin/master 65ef932 stratospher: [fuzz] Add D. J. Bernstein's implementation of ChaCha20
<bitcoin-git>
bitcoin/master 4d0ac72 stratospher: [fuzz] Add fuzzing harness to compare both implementations of ChaCha20
<meshcollider>
Also, admin perms on bitcoin/bitcoin doesn't require admin on bitcoin/BIPs
<laanwj>
i mean in the end the github structure is contingent, it's not a representation of any formal power structure within bitcoin, if someone would really mess up the onus of development would simply move somewhere else
<laanwj>
glozow: no objections myself, but i do think it's important that people developing bitcoin core widely agree on it (which seems to be the case)
<bitcoin-git>
[bitcoin] shaavan opened pull request #23801: Refactor: Change time variable type from int64_t to std::chrono::seconds in net_processing.cpp (master...time_in_seconds_refactor) https://github.com/bitcoin/bitcoin/pull/23801
<laanwj>
i'm not sure what the fear here is, it seems to me the community around bitcoin dev is sufficiently diffuse and loosely organized that there's ton of ways for someone who is banned in error to have recourse
<bitcoin-git>
[bitcoin] sipa opened pull request #23799: Let test_runner.py start multiple jobs per timeslot (master...202112_multitesturn) https://github.com/bitcoin/bitcoin/pull/23799
<bitcoin-git>
[bitcoin] luke-jr opened pull request #23797: ci: Use Cirrus "greedy" flag to use idle CPU time when available (master...cirrus_greedy) https://github.com/bitcoin/bitcoin/pull/23797
<bitcoin-git>
[bitcoin] theStack opened pull request #23796: test: check that pruneblockchain RPC fails for future block or timestamp (master...202112-test-add_pruneblockchain_test_coverage) https://github.com/bitcoin/bitcoin/pull/23796
<bitcoin-git>
[bitcoin] MarcoFalke opened pull request #23795: refactor: Remove implicit-integer-sign-change suppressions in validation (master...2112-refValSup) https://github.com/bitcoin/bitcoin/pull/23795
<bitcoin-git>
bitcoin/master 62fa61f w0xlt: refactor: remove the wallet folder if the restore fails
<bitcoin-git>
[bitcoin] MarcoFalke merged pull request #23782: test: include two more interruptions points (master...2021-12-feature-init-test-interruptions) https://github.com/bitcoin/bitcoin/pull/23782
<bitcoin-git>
bitcoin/master 71115a5 seaona: test: include two more interruptions points
<bitcoin-git>
bitcoin/master 98c362a MarcoFalke: Merge bitcoin/bitcoin#23782: test: include two more interruptions points
<bitcoin-git>
[bitcoin] MarcoFalke closed pull request #15861: Restore warning for individual unknown version bits, as well as unknown version schemas (master...restore_vbits_warning) https://github.com/bitcoin/bitcoin/pull/15861
<chris23lngr>
hey everyone, i have some questions on bitcoin. Can anyone help?
<bitcoin-git>
[bitcoin] MarcoFalke closed pull request #13608: WIP: bitcoin-tx: Require that input amount is provided for witness transactions (master...bitcoin-tx-sign-amount) https://github.com/bitcoin/bitcoin/pull/13608
<bitcoin-git>
[bitcoin] theStack opened pull request #23784: bitcoin-tx: Require that input amount is provided for witness transactions (master...bitcoin-tx_check_witness_input_amount) https://github.com/bitcoin/bitcoin/pull/23784
<bitcoin-git>
[bitcoin] seaona opened pull request #23782: test: include two more interruptions points (master...2021-12-feature-init-test-interruptions) https://github.com/bitcoin/bitcoin/pull/23782
<bitcoin-git>
[bitcoin] MarcoFalke merged pull request #23758: net: Use type-safe mockable time for peer connection time (master...2112-timeMockp2p) https://github.com/bitcoin/bitcoin/pull/23758
<bitcoin-git>
bitcoin/master fa663a4 MarcoFalke: Use mockable time for peer connection time
<bitcoin-git>
bitcoin/master fad9438 MarcoFalke: scripted-diff: Rename touched member variables
<bitcoin-git>
bitcoin/master fad7ead MarcoFalke: refactor: Use type-safe std::chrono in net
<bitcoin-git>
[bitcoin] josibake opened pull request #23780: refactor, test: update `addrman_tests.cpp` to use output from `AddrMan::Good()` (master...josibake-addrman-test-refactors) https://github.com/bitcoin/bitcoin/pull/23780
<hebasto>
yeah, it is for bitcoin-core-gui in bitcoindesign.slack.com
<laanwj>
looks like it only has read access to bitcoin-core/gui (no more than any other user), but dunno what it's requesting
<laanwj>
why do we have slack integration enabled in the first place? i know there was a bitcoin core slack long ago, but i don't think it's a thing anymore?
<laanwj>
less happy with this ""You’re receiving this email because the GitHub App Slack, which is currently installed on your bitcoin-core organization, has updated its permissions and is requesting additional access. "
<Wes78>
sipa, yeah, it's a totally fictional take on it actually. A group of devs learn he didn't just create Bitcoin--but also created multi-dimensional travel. Think "Secret Life of Walter Mitty" meets crypto, ha. Totally fictional.
<Wes78>
Thank you. I'll head to #bitcoin to see what are some good steps. Trying to avoid Twitter for now to not be too public about it yet, ha. Thank you!
<michaelfolkson>
Wes78: You won't get the "team"'s blessing/endorsement as there is a large community of contributors working on it full time, part time, discontinued/occasional basis. Twitter/Mastodon or #bitcoin on IRC are probably best places to chat
<Wes78>
Hello! Trying to find a way to contact the primary Bitcoin Core dev team. I'm wanting to produce a series called "The Superb Search for Satoshi," a fictional take on the early years of Bitcoin and would love the Bitcoin current team's blessing/endorsement. What's the best way to reach someone?
<bitcoin-git>
bitcoin/master e9440ae fanquake: build: use __SIZEOF_INT128__ for checking __int128 availability
<bitcoin-git>
bitcoin/master 4279674 MarcoFalke: Merge bitcoin/bitcoin#23761: build: use __SIZEOF_INT128__ for checking __i...
<bitcoin-git>
[bitcoin] MarcoFalke merged pull request #23648: test: Use byte unit 'M' for -maxuploadtarget functional test (master...test-byteunit-maxuploadtarget) https://github.com/bitcoin/bitcoin/pull/23648
<bitcoin-git>
bitcoin/master 271252c Jon Atack: validation, log: extract FlushSnapshotToDisk() function
<bitcoin-git>
[bitcoin] MarcoFalke opened pull request #23762: wallet: Replace Assume with Assert where needed in coinselection (master...2112-refAssertCoinWallet) https://github.com/bitcoin/bitcoin/pull/23762
<bitcoin-git>
[bitcoin] fanquake opened pull request #23761: build: use __SIZEOF_INT128__ for checking __int128 availability (master...unify_int128_checking) https://github.com/bitcoin/bitcoin/pull/23761
<bitcoin-git>
[bitcoin] fanquake opened pull request #23760: util: move MapIntoRange() for reuse in fuzz tests (master...reuse_mapintorange) https://github.com/bitcoin/bitcoin/pull/23760
<bitcoin-git>
bitcoin/master 9600ea0 Martin Zumsande: test: Add edge case of pruning up to index height
<bitcoin-git>
bitcoin/master 698c524 Martin Zumsande: index: Fix backwards search for bestblock
<bitcoin-git>
[bitcoin] MarcoFalke opened pull request #23758: net: Use type-safe mockable time for peer connection time (master...2112-timeMockp2p) https://github.com/bitcoin/bitcoin/pull/23758
<bitcoin-git>
[bitcoin] klementtan closed pull request #22282: refactor: CheckFinalTx pass by reference instead of pointer (master...CheckFinalTx_ptr_to_ref) https://github.com/bitcoin/bitcoin/pull/22282
<bitcoin-git>
[bitcoin] hebasto opened pull request #23751: build, qt: No need to set inapplicable QPA backend for Android (master...211212-qpa) https://github.com/bitcoin/bitcoin/pull/23751
<bitcoin-git>
[bitcoin] darosior opened pull request #23750: rpcwallet: mention labels are disabled for ranged descriptors (master...no_label_range_descriptors) https://github.com/bitcoin/bitcoin/pull/23750
<Guest89>
Nobody wants to wait until 2142 for a "completed" currency. money shouldnt need to be "completed". Remove mining and use bitcoin as just that a digital value bought with real money with a cap of 21 million.
<Guest89>
Bitcoin devs right?
2021-12-11
<bitcoin-git>
[bitcoin] MarcoFalke merged pull request #23113: Add warnings to createmultisig and addmultisig if using uncompressed keys (master...202109_createmultisig_warnings) https://github.com/bitcoin/bitcoin/pull/23113
<bitcoin-git>
bitcoin/master e46fc93 Samuel Dobson: Add warnings field to addmultisigaddress to warn about uncompressed keys
<bitcoin-git>
bitcoin/master d1a9742 Samuel Dobson: Add warnings field to createmultisig to warn about uncompressed keys