19:00:26 <wumpus> #startmeeting 19:00:26 <core-meetingbot> Meeting started Thu May 6 19:00:26 2021 UTC. The chair is wumpus. Information about MeetBot at https://bitcoin.jonasschnelli.ch/ircmeetings. 19:00:26 <core-meetingbot> Available commands: action commands idea info link nick 19:00:34 <wumpus> #bitcoin -core-dev Meeting: achow101 aj amiti ariard bluematt cfields Chris_Stewart_5 digi_james dongcarl elichai2 emilengler fanquake fjahr gleb glozow gmaxwell gwillen hebasto instagibbs jamesob jb55 jeremyrubin jl2012 jnewbery jonasschnelli jonatack jtimon kallewoof kanzure kvaciral lightlike luke-jr maaku marcofalke meshcollider michagogo moneyball morcos nehan NicolasDorier paveljanik 19:00:35 <wumpus> petertodd phantomcircuit promag provoostenator ryanofsky sdaftuar sipa vasild wumpus 19:00:47 <meshcollider> hi 19:00:51 <jonatack> hi 19:00:52 <murch> hi 19:00:54 <jb55> hi 19:00:56 <jnewbery> hi 19:00:58 <michaelfolkson> hi 19:00:59 <fjahr> hi 19:01:28 <ariard> hi 19:01:54 <wumpus> welcome to the weekly bitcoin-core-dev meeting, there is one proposed meeting topic from http://gnusha.org/bitcoin-core-dev/proposedmeetingtopics.txt: Plan for future Core fuzzing using OSS-Fuzz (michaelfolkson) 19:01:56 <sipa> hi 19:02:05 <wumpus> any last minute topic proposals? 19:02:53 <wumpus> #topic High priority for review 19:02:54 <core-meetingbot> topic: High priority for review 19:03:21 <wumpus> 10 current blockers on review in https://github.com/bitcoin/bitcoin/projects/8 19:03:39 <wumpus> anything to add/remove or this is ready for merge? 19:04:23 <achow101> hi 19:04:43 <murch> #17331 has five concept ACKs and one tACK 19:04:48 <gribble> https://github.com/bitcoin/bitcoin/issues/17331 | Use effective values throughout coin selection by achow101 ÷ Pull Request #17331 ÷ bitcoin/bitcoin ÷ GitHub 19:05:00 <murch> Might be good if a couple more people took a look 19:05:09 <sipa> i will 19:05:18 <wumpus> right, needs more code review ACKs i guess 19:06:01 <gleb> hi 19:06:24 <wumpus> nothing else? 19:06:31 <achow101> I will be making a few changes to #17331, so it is not rtm 19:06:34 <gribble> https://github.com/bitcoin/bitcoin/issues/17331 | Use effective values throughout coin selection by achow101 ÷ Pull Request #17331 ÷ bitcoin/bitcoin ÷ GitHub 19:06:59 <wumpus> achow101: thanks for letting us know 19:08:14 <wumpus> no other discussion of high prio PRs? moving to next topic 19:08:32 <wumpus> #topic Plan for future Core fuzzing using OSS-Fuzz (michaelfolkson) 19:08:33 <core-meetingbot> topic: Plan for future Core fuzzing using OSS-Fuzz (michaelfolkson) 19:09:16 <michaelfolkson> Ok cool, so I don't know if the regular fuzzers are here but Core has signed up to use Google's OSS-Fuzz from what I understand 19:09:43 <murch> https://github.com/google/oss-fuzz/pull/5699 19:09:44 <michaelfolkson> I heard about it through this https://github.com/bitcoin/bitcoin/pull/21856 19:10:32 <michaelfolkson> In the past there were some discussions on whether it would be wise to sign up to it. The biggest concern being the 90 day disclosure. 19:11:15 <michaelfolkson> But it sounds like these concerns were resolved and there was some misunderstanding that there could always be some exceptions (for Core or any other project) 19:11:27 <luke-jr> presumably by the time it gets to Google, 90 day disclosure is better than not knowing at all? 19:12:07 <michaelfolkson> luke-jr: I think this more if Google finds out about it they plan to release details of it after 90 days 19:12:23 <michaelfolkson> luke-jr: If there is no exception 19:12:54 <luke-jr> michaelfolkson: right, but if we had already know, Google wouldn't have found out anyway 19:13:04 <sipa> we have an exception 19:13:29 <michaelfolkson> sipa: Ok I wasn't clear on the details of that. But that's good 19:14:05 <michaelfolkson> So assuming there are no problems with the disclosure part (which it sounds like there isn't) I wondered what the plan was to take advantage of using OSS-Fuzz 19:14:25 <michaelfolkson> Or have we not thought this far ahead yet? 19:14:37 <michaelfolkson> It looks like this was signed up for the last week 19:15:13 <sipa> michaelfolkson: MarcoFalke knows more details 19:15:41 <michaelfolkson> The main benefit it appears to give is access to vast amount of CPU cores but I wondered what particular fuzzing would be done on those cores and whether that would be managed by an individual, the fuzzing team etc 19:15:51 <sipa> but i don't think there is that much to say; it's up and running our fuzzers fron what i understand, in a number of configurations 19:16:29 <michaelfolkson> So no plan to allocate certain fuzzing exercises, targeted fuzzing to those particular cores? 19:17:09 <sipa> not sure what the advantage of that would be 19:17:28 <sipa> if we think our fuzzers are good, more cpu power running them is good 19:17:39 <sipa> if we don't think they're useful, they should be removed 19:17:56 <michaelfolkson> Ok so just running existing fuzzers but with more CPU power 19:18:26 <michaelfolkson> Do we get anything else from signing up to OSS-Fuzz other than CPU cores? Do you know? 19:18:43 <sipa> in what sense? 19:19:01 <michaelfolkson> I'm not sure. Just clarifying if that is the only benefit 19:19:13 <sipa> i mean... that's what fuzzing is 19:19:18 <sipa> they help us eun our fuzzers 19:19:22 <sipa> for free 19:19:28 <michaelfolkson> They have a few fuzzing experts over at Google. Maybe they will engage with it 19:19:31 <michaelfolkson> shrugs 19:19:38 <wumpus> tbh, i'm not sure this is a meeting discussion topic or simply some questions that could be handled outside the meeting, but i guess it's okay as we have no other topics for today 19:20:09 <michaelfolkson> Ok that's all. Just interested in what had happened and what the plan was 19:20:24 <wumpus> okay 19:20:25 <michaelfolkson> I hadn't seen it discussed anywhere on IRC until that PR popped up 19:20:35 <wumpus> #endmeeting