< bitcoin-git>
[bitcoin] laanwj closed pull request #10372: Add perf counter data to GetStrongRandBytes state in scheduler (master...2017-05-scheduler-rng) https://github.com/bitcoin/bitcoin/pull/10372
< bitcoin-git>
bitcoin/master 15254e9 Wladimir J. van der Laan: Merge #10372: Add perf counter data to GetStrongRandBytes state in scheduler...
< bitcoin-git>
bitcoin/master 888cce5 Matt Corallo: Add perf counter data to GetStrongRandBytes state in scheduler
< bitcoin-git>
bitcoin/master 399fb8f Matt Corallo: Add internal method to add new random data to our internal RNG state
< da2ce7>
One of the critical security properties of bitcoin is a well-distributed set of miners. AsicBoost dramatically breaks this assumtion.
< wumpus>
"I think there is a dramatic under estimation the damage of asicboost to Bitcoin" in what way? because they overrepresent themselves, resulting in more mining centralization than would otherwise be the case?
< da2ce7>
wumpus, I agree: BIP148 may be, even then, too rushed (but I personally believe BIP148 is the safest option available, as I think there is a dramatic under estimation the damage of asicboost to Bitcoin). However, I haven't seen this considered in any of the significant anti-BIP148 responses to the mailing list. Centrally not an analysis of the tradeoffs available.
< jtimon>
BlueMatt: I can't remember which of your PRs contained something somilar to https://github.com/bitcoin/bitcoin/pull/10427 but it's basically what you wanted with my 2 smaller but more important for me nits
< bitcoin-git>
[bitcoin] laanwj closed pull request #10415: [tests] Speed up fuzzing by ~200x when using afl-fuzz (master...fast-afl-fuzzing) https://github.com/bitcoin/bitcoin/pull/10415
< bitcoin-git>
bitcoin/master 217b416 Wladimir J. van der Laan: Merge #10415: [tests] Speed up fuzzing by ~200x when using afl-fuzz...
< bitcoin-git>
bitcoin/master 693247b practicalswift: [test] Speed up fuzzing by ~200x when using afl-fuzz...
< bitcoin-git>
[bitcoin] paveljanik opened pull request #10431: Prevent shadowing the global dustRelayFee (master...20170519_policy_shadowing) https://github.com/bitcoin/bitcoin/pull/10431
< bitcoin-git>
[bitcoin] jnewbery opened pull request #10423: [tests] skipped tests should clean up after themselves (master...cleanup_skipped) https://github.com/bitcoin/bitcoin/pull/10423
< bitcoin-git>
[bitcoin] laanwj closed pull request #10408: Net: Improvements to Tor control port parser (master...torcontrol-parser-patches) https://github.com/bitcoin/bitcoin/pull/10408
< bitcoin-git>
bitcoin/master d63677b Jack Grigg: torcontrol: Fix ParseTorReplyMapping...
< bitcoin-git>
bitcoin/master d8e03c0 Jack Grigg: torcontrol: Improve comments
< bitcoin-git>
bitcoin/master 29f3c20 Jack Grigg: torcontrol: Add unit tests for Tor reply parsers
< bitcoin-git>
[bitcoin] fanquake closed pull request #9427: Use compact blocks for blocks that have equal work to our active tip (master...UseCmpctBlockForCompetingBlocks) https://github.com/bitcoin/bitcoin/pull/9427
< bitcoin-git>
bitcoin/master 9f7341b Gregory Sanders: Add witness data output to TxInError messages
2017-05-17
< Anduck>
not only in bitcoin scene, that is
< lichtamberg_>
And you are also removing the possibility to switch to the correct chain, if BIP148 really gets much traction at the end. With the toggle option, people can switch more or less easily.. without => you are forcing the users to unofficial versions.. most people dont compile bitcoin themself
< lichtamberg_>
On one side you are asking for more community participation, and on the other side you are dismissing one of the biggest community movements which bitcoin ever had..
< Anduck>
anyway, even while bip148 may be stupidly risky, there's no point in trying to slow it down. it happens if it happens. running bitcoin node will increasingly require more knowledge of what actual rules does the code follow. there's no point in trying to oppose this from realising
< Anduck>
bgp is not comparable to bitcoin because there's no competitor. nobody gains anything if they get bgp replaced by something else
< BlueMatt>
bitcoin even is
< BlueMatt>
i assume you can picture the "how to install bitcoin core" guides where someone tells you to use that flag and then they'll tell you you've been paid
< BlueMatt>
sdf_0010: maybe a better comparison is a flag to run bitcoin core on testnet but have everything pretend to be mainnet
< BlueMatt>
if they're, otoh, expecting "Core" to decide consensus rules for the bitcoin ecosystem, then they can also clearly fuck off
< BlueMatt>
well then they're expecting us to do the job of figuring out what the community's consensus on bitcoin's consensus rules is, and it is clearly not bip 148
< BlueMatt>
on top of people doing physical outreach and talking to various groups at meetups, plus discussions with long-time bitcoin holders and investors
< BlueMatt>
it is not bitcoin core's job to merge something *until* that exists, irrespective of whether individual contributors are pushing for it
< BlueMatt>
businesses are also users of the system, especially the many that do not expose bitcoin to their users, and there is clearly not vast, broad support for bip 148 in that community even *if* core merges it
< BlueMatt>
luke-jr: this is absurd, do you seriously believe the vast, vast majority of bitcoin users (incl businesses) support bip 148?
< SopaXorzTaker>
banned from #bitcoin for spreading bullsh*t
< wumpus>
again, #bitcoin, this is not the place to discuss the protocol in general
< wumpus>
please, #bitcoin
< bitcoin-git>
[bitcoin] practicalswift opened pull request #10415: [fuzz] Speed up fuzzing by ~200x when using afl-fuzz (master...fast-afl-fuzzing) https://github.com/bitcoin/bitcoin/pull/10415
< bitcoin-git>
[bitcoin] fanquake closed pull request #9325: Allow first cmpctblock/blocktxn received to be processed (rather than first requested) (master...ProcessFirstCmpct) https://github.com/bitcoin/bitcoin/pull/9325
< bitcoin-git>
[bitcoin] laanwj closed pull request #10388: Output line to debug.log when IsInitialBlockDownload latches to false (master...printIBD) https://github.com/bitcoin/bitcoin/pull/10388
< bitcoin-git>
bitcoin/master 526e839 Wladimir J. van der Laan: Merge #10388: Output line to debug.log when IsInitialBlockDownload latches to false...
< bitcoin-git>
bitcoin/master 65d484a Alex Morcos: Output line to debug.log when IsInitialBlockDownload latches to false
< gribble>
https://github.com/bitcoin/bitcoin/issues/10388 | Output line to debug.log when IsInitialBlockDownload latches to false by morcos · Pull Request #10388 · bitcoin/bitcoin · GitHub
< gribble>
https://github.com/bitcoin/bitcoin/issues/7522 | Bugfix: Only use git for build info if the repository is actually the right one by luke-jr · Pull Request #7522 · bitcoin/bitcoin · GitHub
< bitcoin-git>
[bitcoin] fanquake closed pull request #9091: Optimize sending of getheaders when pindexLast is an ancestor of pindexBestHeader (master...OptimizeMoreGetheaders) https://github.com/bitcoin/bitcoin/pull/9091
< bitcoin-git>
[bitcoin] laanwj closed pull request #10405: tests: Correct testcase in script_tests.json for large number OP_EQUAL (master...2017_05_scriptnum_test) https://github.com/bitcoin/bitcoin/pull/10405
< bitcoin-git>
bitcoin/master 2f84cf6 Wladimir J. van der Laan: tests: Correct testcase in script_tests.json for large number OP_EQUAL...
< bitcoin-git>
bitcoin/master 0542978 Wladimir J. van der Laan: Merge #10405: tests: Correct testcase in script_tests.json for large number OP_EQUAL...
< bitcoin-git>
[bitcoin] laanwj closed pull request #10374: qa: Warn when specified test is not found (master...Mf1705-qaWarnTestNotFound) https://github.com/bitcoin/bitcoin/pull/10374
< bitcoin-git>
bitcoin/master 5411997 Wladimir J. van der Laan: Merge #10374: qa: Warn when specified test is not found...
< bitcoin-git>
bitcoin/master fac79e4 MarcoFalke: qa: Warn when specified test is not found
< Chris_Stewart_5>
If I have a transaction that spends a raw witness spk and the input is already signed on the spending tx, and then I'm trying to call fundrawtransaction to add a fee. Is this currently unsupported in bitcoin core? Do I need to use P2SH(P2WSH)?
< bitcoin-git>
[bitcoin] str4d opened pull request #10408: Net: Improvements to Tor control port parser (master...torcontrol-parser-patches) https://github.com/bitcoin/bitcoin/pull/10408
< sipa>
this channel is about implementation and development of the bitcoin core software
< dermoth>
#bitcoin-dev would be more appropriate?
< sipa>
well this channel is about the developement of bitcoin core
< dermoth>
sipa, yes possibly OT - hoe many bitcoin "dev" channels there is?? :)
< gmaxwell>
sipa: well you can filter the inputs that were spent, there was a point on bitcoin-dev about this a year ago.
< sipa>
perhaps this is more for #bitcoin-wizards then
< dermoth>
Hey there... I was thinking about the issue of block size vs. propagation time... If I'm not mistaken Bitcoin already sends header only first so miners can start mining quickly on tip, but they cannot validate/include any transaction until they get the full block...
< bitcoin-git>
bitcoin/master c99ab3c Luke Dashjr: RPC: Allow multiple names for parameters
< bitcoin-git>
bitcoin/master e3c9f2d Andrew Chow: Use a verbosity instead of two verbose parameters...
< bitcoin-git>
[bitcoin] laanwj opened pull request #10405: tests: Correct testcase in script_tests.json for large number OP_EQUAL (master...2017_05_scriptnum_test) https://github.com/bitcoin/bitcoin/pull/10405
< bitcoin-git>
[bitcoin] rvelhote opened pull request #10400: [RPC] Add an uptime command that displays the amount of time (in seconds) bitcoind has been running (master...rpc-uptime) https://github.com/bitcoin/bitcoin/pull/10400
< bitcoin-git>
[bitcoin] sipa opened pull request #10396: Report LevelDB estimate for chainstate size in gettxoutsetinfo (master...diskdbsize) https://github.com/bitcoin/bitcoin/pull/10396
2017-05-13
< sipa>
if that seems like an arbitrary distinction, please realize that many people here are not interested in the political drama surrounding bitcoin and just want to develop software
< sipa>
this channel is not about discussing proposed changes to the bitcoin consensus rules
< bitcoin-git>
[bitcoin] practicalswift opened pull request #10395: Replace boost::function with std::function (C++11) (master...replace-boost-function) https://github.com/bitcoin/bitcoin/pull/10395
< bitcoin-git>
[bitcoin] practicalswift closed pull request #10378: Rename TxConfirmStats to CTxConfirmStats to achieve class naming consistency (master...TxConfirmStats) https://github.com/bitcoin/bitcoin/pull/10378
2017-05-12
< sipa>
ok, so in the rpc signing code and in bitcoin-tx, there used to be a Modifier that was both used check whether an output already existed, and then add it
< kanzure>
i added a comment here explaining that perhaps a better design would be to let user specify the final transaction size (if the user knows it) or allowing feeRate=0 if the user plans to delete an output later https://github.com/bitcoin/bitcoin/pull/10202#issuecomment-301134038