freenode #monero-dev

1 Apr 2020

Official repo: github.com/monero-project/monero || Don’t ask to ask, just ask:) || Non-dev questions -> #monero, please || Next dev meeting is detailed on the Monero meeting issue on Github: github.com/monero-project/meta/issues

• 01:54
  selsta
  does anyone understand what this is? storage.googleapis.com/oss-fuzz-cov…yptofuzz/modules/monero/report.html
• 01:54
  selsta
  looks like oss-fuzz runs cryptofuzz which fuzzes some monero files :)
• 01:56
  moneromooo
  Interesting. Not super useful now though, since we're on randomx and this is Cryptonight bits.
• 01:57
  selsta
  maybe we can PR more here: github.com/guidovranken/cryptofuzz
• 07:58
  Inge-
  selsta: guidovranken.com/2019/05/14/differe…-fuzzing-of-cryptographic-libraries
• 11:56
  TrasherDK1
  Here's a first for me: wallet-name.unportable ??? After moving wallet files to another partition.
• 14:14
  squidbas1
  hi i'm trying to build the gui on freebsd getting linker errors at the end of the build
• 14:14
  squidbas1
  e.g. ld: error: unable to find library -lwallet_merged
• 14:15
  moneromooo
  Are you following the instructions from the README file ?
• 14:15
  squidbas1
  moneromoo: yes i am but there are no freebsd instructions
• 14:16
  moneromooo
  Then ask in #monero-gui.
• 14:16
  squidbas1
  ok will do thanks
• 16:31
  sarang
  Another small update made to PR 6338, which was squashed to the same commit
• 16:31
  sarang
  Takes care of domain separation used in subaddress generation (thanks to UkoeHB_ for noting this)
• 16:32
  sarang
  Passes CI
• 16:40
  sarang
  Weekly research meeting in #monero-research-lab begins at 17:00 UTC (about 20 minutes from now)
• 20:56
  sarang
  luigi1111: once the new commit on 6338 gets reviewed, it should be good to go
• 20:56
  sarang
  ^ luigi1111w
• 22:05
  selsta
  should we do an v0.15.0.6? (linux 32 bit fixes, gitian fixes, other bug fixes)
• 22:05
  selsta
  I would have time to organize it
• 22:17
  selsta
  Was thinking about branch equivalents of: #6197, #6381, #6384, #6397, #6398, #6405, #6403, #6408, #6414
• 23:20
  moneromooo
  6384 does not apply to the release branch fwiw. The buggy code is only in master.
• 23:23
  dEBRUYNE
  selsta: With the dandelion++ essentially being ready to get merged, why not go to 0.15.1.0 directly?
• 23:24
  selsta
  dEBRUYNE: Because I would prefer a last stable release before branching from master again
• 23:25
  selsta
  also doing v.15.0.6 would not take long, v0.15.1.0 will probably still take a bit of time
• 23:27
  selsta
  we can also do v0.15.1.0 I guess