< elichai2>
sipa: https://github.com/bitcoin/bitcoin/issues/15621 requires a batch `secp256k1_ecdsa_recover` that recieves a list of signatures and returns a list of affine public keys, right?
< bitcoin-git>
bitcoin/master fa0119a MarcoFalke: doc: Refer in rpcbind doc to the manpage
< bitcoin-git>
bitcoin/master 91ed1b3 Wladimir J. van der Laan: Merge #16634: doc: Refer in rpcbind doc to the manpage
< coinmonks>
The 1 response I got (I won't name them),,tells that he is a freelancer, want to work on Bitcoin fulltime and currently use some economic help in that direction..
< coinmonks>
We can always help these folks and create a path for more people working fulltime on Bitcoin
< coinmonks>
I want to understand how BItcoin protocol development is getting funded now and are contributors in good economic condition
< coinmonks>
Also I have created a survey to understand Bitcoin protocol development.. So for only 1 person filled it.. I would like you pls take 2 minutes and check it ..
< bitcoin-git>
[bitcoin] kallewoof opened pull request #16653: script: add simple signature support (checker/creator) (master...2019-08-genpursigs) https://github.com/bitcoin/bitcoin/pull/16653
< bitcoin-git>
bitcoin/master c325f61 Andrew Chow: Return an error from descriptor Parse that gives more information about wh...
< bitcoin-git>
bitcoin/master 625534d Andrew Chow: Give more errors for specific failure conditions
< bitcoin-git>
bitcoin/master 6e1ae58 Andrew Chow: Check error messages in descriptor tests
< harding>
kakobrekla: that question (and any followups you have) may be better asked in #bitcoin. The answer is that P2WPKH uses a 20-byte hash RIPEMD(SHA256()) and P2WSH uses a 32-byte hash SHA256(). For details, see https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki#P2WSH
< bitcoin-git>
[bitcoin] GChuf opened pull request #16644: scripts: attempt to fix some translations in update-translations.py (master...patch-1) https://github.com/bitcoin/bitcoin/pull/16644
< bitcoin-git>
[bitcoin] hebasto opened pull request #16643: doc: Add ZMQ dependencies to the Fedora build instructions (master...20190818-doc-fedora-zmq) https://github.com/bitcoin/bitcoin/pull/16643
< hebasto>
fanquake: is Mine8801's activity in the bitcoin repo needed to be moderated?
< bitcoin-git>
[bitcoin] Sjors opened pull request #16639: [0.17] abort when attempting to fund a transaction above -maxtxfee (0.17...2019/08/backport_max_fee) https://github.com/bitcoin/bitcoin/pull/16639
< gribble>
https://github.com/bitcoin/bitcoin/issues/16341 | Introduce ScriptPubKeyMan interface and use it for key and script management (aka wallet boxes) by achow101 · Pull Request #16341 · bitcoin/bitcoin · GitHub
< bitcoin-git>
bitcoin/master dc7529a nicolas.dorier: [Fix] Allow connection of a noban banned peer
< bitcoin-git>
bitcoin/master d117f45 nicolas.dorier: Add test for setban
< bitcoin-git>
bitcoin/master b80cdfe MarcoFalke: Merge #16618: [Fix] Allow connection of a noban banned peer
< bitcoin-git>
[bitcoin] DrahtBot closed pull request #15150: gui: Show wallet selector on console window if there are wallets loaded (master...2019-01-consolewalletselector) https://github.com/bitcoin/bitcoin/pull/15150
< coinmonks>
hey guys, few days ago, I tried to understand the Bitcoin codebase using different metrics, for now i want to understand what is state of Bitcoin contributors and their economic well being..
< bitcoin-git>
[bitcoin] NicolasDorier opened pull request #16631: [Fix] The default whitelistrelay should be true (master...fix/default-whiterelay) https://github.com/bitcoin/bitcoin/pull/16631
< bitcoin-git>
[bitcoin] NicolasDorier opened pull request #16629: [Doc] Add documentation for the new whitelist permissions (master...doc/permissions) https://github.com/bitcoin/bitcoin/pull/16629
< roconnor>
Hi all. After building bitcoin-0.18.0 and bitcoin-0.18.1 when I run the test_bitcoin program it lists a large number of "Error: Specified -walletdir "wallets" is a relative path ... followed by "*** No errors detected". I didn't have this issue with bitcoin-0.17.1. Have I made some sort of configuration error here?
< bitcoin-git>
[bitcoin] ariard opened pull request #16624: wallet : encapsulate trransactions state (master...2019-08-encapsulate-tx-state) https://github.com/bitcoin/bitcoin/pull/16624
< gribble>
https://github.com/bitcoin/bitcoin/issues/16421 | Conservatively accept RBF bumps bumping one tx at the package limits by TheBlueMatt · Pull Request #16421 · bitcoin/bitcoin · GitHub
< wumpus>
also a lot of bitcoin core reviewers don't have much knowledge of the details of the cryptography and implementation
< wumpus>
#action move github-merge.py to bitcoin-maintainer-tools repo
< wumpus>
yes, if it affects use in bitcoin, or is even an issue that threatens bitcoin, that seems an exception
< sipa>
agree; though very serious issues that impact bitcoin could of course also be reported to bitcoin core
< wumpus>
instead of having it in the bitcoin core repository
< sipa>
i think that libsecp256k1 issues which don't directly affect bitcoin core can be kept inside the secp256k1 project (bitcoin core has no need for JNI... :p)
< real_or_random>
which raises the question who should be in there. secp256k1 maintainers or bitcoin-core maintainers?
< sipa>
we should probably add merge checks in CI just like in bitcoin core itself
< provoostenator>
Could reuse some of the Bitcoin Core tools over?
< bitcoin-git>
[bitcoin] MarcoFalke merged pull request #16561: tests: Use colors and dots in test_runner.py output only if standard output is a terminal (master...parsable) https://github.com/bitcoin/bitcoin/pull/16561
< bitcoin-git>
[bitcoin] fanquake merged pull request #16578: Do not pass in command line arguments to QApplication (master...no-qapp-args) https://github.com/bitcoin/bitcoin/pull/16578