01:13:22 whilst watching "next friday" 12:57:53 meeting in 2~ hours https://github.com/monero-project/meta/issues/864 13:05:18 "what's next up feature-wise?" <- For Feather I currently have my sight on: UR for offline tx signing, intergrating jberman's background sync (+ memory hardening), using dice as external entropy for seed generation, experiment with Flatpak extensions as an initial plugin system to ship "heavier" features like daemon integration, p2pool, maybe atomic swaps. More options for high/esoteric threat models. Plus lots of 13:05:18 misc. enhancements / UX improvements that I've collected from feedback. Not really a feature but also want to leverage containerization and Qt Test for automated regression testing (like ensuring no network requests are made before user grants permission / portable mode only writes in portable directory, etc). 13:36:19 "For Feather I currently have..." <- great, looks like background sync has finally got some eyes on it for a review 15:00:11 meeting time https://github.com/monero-project/meta/issues/864 15:00:30 Greetings 15:01:17 Hi 15:01:21 matrix is playing up for me but the IRC bridge is working thankfully 15:02:08 👋 15:02:58 Hello 15:03:07 lets share some community highlights while people come in 3. Community highlights 15:03:33 the new / final bulletproofs++ paper is here https://libera.monerologs.net/monero-research-lab/20230720#c268352. The first auditors, CypherStack, will provide an update some time in August (because the paper is now different / complete, i can only assume the scope of the audit may require changes / cost adjustments. The MRL team can discuss this 15:03:33 after CS provide feedback of the final paper). 15:05:25 Hello 15:05:32 https://libera.monerologs.net/monero-community/20230710#c267159 "Buy and sell information on the owner of any blockchain wallet address—anonymously, via smart contract." Lovera has tested it out for us. No support for Monero (transparent blockchains only) 15:06:11 I wonder if you could poison the system by selling fake info 🤔 15:06:19 Hi 15:06:32 after reaching out to several auditors/cryptography researchers for adding security proofs to the Seraphis paper(s), the initial feedback has been 'can we arrange a call' whereas for the bp++ audit, which the MRL was able to provide feedback on an actual scope of work, a quote for time / cost was easily obtaininable for comparison, i've recommended 15:06:32 the same to be done for the Seraphis papers to remove alot of friction from the process. jberman and koe will collaborate in creating a more detailed scope 15:08:11 blankpage[m]: a pretty graph goes a long way 15:08:26 Hello, sorry late. 15:08:51 hello 15:09:25 just sharing some highlights of the past 2 weeks if anyone wants to share something 15:10:10 To confirm, there are some funds raised and allocated for bp++++++ audit (but the eventual cost is unknown) whereas the audits for seraphis are essentially unknown and unfunded at this point? 15:10:32 [Revuo Monero](https://revuo-xmr.com/) - [The Monero Standard](https://localmonero.co/the-monero-standard) have been 2 active newsletters during this period and the author of revuo, rottenwheel has joined this channel 15:10:39 Does anyone know when escapethe3RA will be back to write the Monero observer? 15:11:12 blankpage yes - the bp++ audit funds where for an earlier version of the paper 15:11:16 s/observer/Observer/ 15:11:30 currently trying to obtain quotes for seraphis work 15:12:00 blankpage: BP++ now has security proofs. Those security proofs need to be checked to make sure there is no flaw in them. Seraphis is lacking security proofs. Those need to be written. Then those proofs need to be checked. 15:12:03 no updates from escape3RA about return date 15:12:53 The original BP++ paper had a vulnerability in it, too. (According to ACK-J) 15:14:02 Is there a post about that somewhere Rucknium? The vulnerability 15:14:53 in the papers changelog "Fixed soundness vulnerability in range proofs that required the introduction of new challenge 15:14:53 variable δ to the arithmetic circuit protocol." 15:15:10 i do not know what this means 15:15:54 blankpage: https://libera.monerologs.net/monero-research-lab/20230720#c268403 15:16:59 shall we move on to the CCS proposals? 15:17:32 Looks like 15:17:37 first impressions of the new bp++ paper from cypherstack coming in august* 15:18:14 4. [CCS updates](https://ccs.getmonero.org/) 15:18:24 a. [recanman bitejo rewrite and expansion proposal](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/395) 15:18:43 I thought about making a separate CCS for the jobs, but I am confident that I can finish it in one CCS. 15:19:10 I've already been working on it for fun (I am going to make it, but much slower if it doesn't get funded), and things have been going well. 15:19:59 proposal has not changed since 3 weeks. it will stay on the ideas page and rot away as it stands right now imo 15:20:11 I don't feel that any changes are necessary. 15:20:58 I will restate my opinion that I am not against such proposals but I would not donate because it requires network effects etc. to be successful rather than being a technical problem 15:21:46 Greetings #late 15:21:47 If you get something successful running, then maybe apply to CCS for maintenance/expansion 15:22:15 Since it would be a hobby project, it would take a year at minimum. 15:22:40 Most successful monero market website is a janky ugly mess but people will go wherever the people are 15:22:56 I'm planning to promote it with LocalMonero 15:23:18 has localmonero promoted bitejo? 15:23:35 No, they have not 15:24:00 I don't think the original creator of Bitejo ever contacted them. 15:24:51 I had suggested removing the jobs portion of the ccs (- name: Month 4 (Begin jobs service backend) (80 hours) funds: 15 XMR done: status: unfinished - name: Month 5 (Finish jobs service backend) (80 hours) funds: 10 XMR ) -25xmr 15:25:14 Could you remind me of the reasoning for that? 15:25:59 brings it to 30 xmr for work, 15 for maintenance and hosting etc 15:26:09 New ccs later for the jobs part 15:26:22 the proposal does not require changes according to recanman, which has received many suggestions during that time. if people would like more time to make a decision on merge/close (or willing to vote now) please say/do so 15:26:46 30xmr for current stuff 15:26:46 25 for jobs 15:26:46 15 for maintenance 15:26:46 cut the jobs stuff for now 15:28:58 I am about to make the changes 15:29:13 i would vote close on its current form, but do not want to deter recanman from coming back with something more appealing 15:29:46 discuss it again next meeting and move on? 15:29:57 ofrnxmr[m]: > <@ofrnxmr:monero.social> 30xmr for current stuff... (full message at ) 15:30:03 Total 45 XMR for four months of work 15:30:13 Close in current form, but since making changes, wait 2 weeks and revisit i think 15:31:16 recanman: thanks. we'llsee before the next meeting if anyone has anything else to suggest. 15:31:17 lets revisit next time and discuss more in the interim 15:31:46 By next meeting, I won't be able to commit the four months. 15:32:03 would anyone like to revisit any of the previous proposals that where voted for being closed 15:32:05 Thats ok 15:32:19 b. [Glitter Finance Cross-Chain Privacy Infrastructure with Monero](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/396) Close 15:32:19 c. [Serving Defcon 31 (2023)](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/397) Close 15:32:19 d. [XMR Business Wallet Development](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/398) Close 15:33:21 I say close them all 15:33:28 recanman[m]: You can begin work anytime and bill later. 15:33:28 should probably change your milestones description from "month1, 2 etc" to "as work is completed". 15:33:45 Nah close the three proposals 15:33:52 B. Close 15:33:52 C. Close 15:33:52 D. Close 15:34:24 Unless glittrr wants to sponsor us 15:35:34 thanks to everyone who is leaving feedback here and also on the gitlab 15:35:37 * sponsor us /s 15:36:29 moving on then.. 15:36:49 e. [Continued Feather Wallet development (3 months)](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/400) 15:37:19 tobtoht listed some items on the todo list today https://libera.monerologs.net/monero-community/20230722#c268628 15:37:21 I don't use Feather Wallet personally, but I've seen it and it is pretty great 15:37:22 +merge 15:38:01 Merge feather always 🪶 15:38:07 the background sync with view keys only pull request from jberman is also up for review. an update was provided here (with links to the associated bounty) https://github.com/monero-project/monero/pull/8619#issuecomment-1632951461 - its nice to see feather wants to integrate it asap 15:38:47 I like that feather wants to 15:39:38 But unless the fixes make it back upstream in less than a year 😅 TOBBY! Haha 15:39:51 (referring to proxy leak and dns leak, polyseed etc) 15:40:42 (Comment from a lurker: I am reviewing that background sync PR right now.) 15:40:50 That DNS leak happened to be an accidental fix, I wasn't aware of it. 15:41:29 rbrunner: I will review it too (not accepting the bounty) 15:42:00 tobtoht has been handling tech support / bug reports / sharing updates in #feather:monero.social 15:42:00 rbrunner: Could you explain background sync simply? What makes it different from the way sync happens now? 15:42:49 View keys 15:43:04 "Background" in this case means "While you don't have the wallet open in the app". 15:43:27 It's kept open in the background, in a pretty secure way, and collects info about incomming transactions. 15:43:44 also on IRC OFTC network #feather 15:43:45 If you "open" the wallet again in the app, it will be synced "officially" withing seconds. 15:44:13 So wallet can keep syncing in background without having spend keys in memory (?) 15:44:13 am i remembering wrong? 15:44:18 afaiu but injb (im not jberman) - the wallet will re-scan all the inputs received using the spend key to double check if they are realchange 15:44:36 that where found during background view key scanning 15:44:40 Yes, that's the "magic" that this PR implements - the spend secret key is NOT around 15:45:00 Does this use the change "heuristic" to recognize spent txs? 15:45:23 +merge for tobtoht. thanks for the #feather room nioc (i keep joining the empty #monero-feather lol 15:45:44 No, it just collects all rings where any of your outputs occur. Later, with the spend secret available again, it sorts things out 15:45:58 since the view key cannot directly recognize spent funds. 15:46:02 +1 Merge btw 15:46:48 +1 merge on Feather continued development 15:47:07 injb and i think no heuristics are needed because the spend key verifies if theyre change / real 15:47:17 after the fact 15:47:27 pls confirm 15:47:30 0xffc: joining us? 15:47:43 Yes, no heuristics are involved 15:47:44 (that was a ping) 15:48:22 Does it assume that the user doesn't have a second wallet that is spending funds? 15:49:04 No, that's no problem: If you collect *all* rings where any of your outputs occur, you catch such spendings 15:49:15 Does it check every tx that uses a given output to see if it's.... 15:49:36 I see. Check all rings that use the output. Makes sense 15:50:14 You check those rings with the spend key when your load it. Since there are only a few of those txs, it's a quick check. Right? 15:50:24 Exactly. 15:50:25 "[Revuo Monero](https://revuo-xmr..." <- Welcome? 😅 15:50:32 https://github.com/m2049r/xmrwallet/issues/785#issuecomment-1079569991 Rucknium: 15:50:32 Very nice :) 15:50:48 Some early discussion is here 15:51:23 I’m late but my vote merges for feather 🚀 15:51:23 hello! 15:52:11 B, C and D for me Close 15:52:31 " b. [Glitter Finance Cross-..." <- > <@plowsof:matrix.org> b. [Glitter Finance Cross-Chain Privacy Infrastructure with Monero](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/396) Close 15:52:31 > c. [Serving Defcon 31 (2023)](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/397) Close 15:52:31 > d. [XMR Business Wallet Development](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/398) Close 15:52:31 Here 15:53:00 positive / merge sentiment for feather 🪶 15:53:18 moving on... 15:53:20 Thanks all ♥️ 15:53:58 f. [j-berman full-time 3 months (part 5)](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/401) 15:54:02 +1 berman 15:54:48 I've raised doubts about whether it's a good idea to code a protocol that has no security proofs yet: https://libera.monerologs.net/monero-research-lab/20230705#c263993 15:55:07 If the community wants to go ahead with it, that's fine. 15:55:17 +1 15:55:24 It could be wasted effort 15:55:26 We need Dev work seraphis and all this stuff so +1 merge berman 15:55:37 +merge 15:56:53 perhaps adding in hours to collab with koe to create a detailed spec for auditors / cryptographers to obtain quotes from people easier could be added (i dont know how long this would take) 15:57:00 Rucknium: do you suggest we try to get proofs done asap? 15:57:11 ofrnxmr: Yes 15:57:12 isn't it a little early to work on including FCMP in the wallet lib? 15:57:32 hbs: IMHO, yes 15:58:34 It needs to be tested thouroughly, and I am not sure building tests around it would be much faster than plugging it into the library for testing ... 15:58:40 We don't know how we would get the security proofs for Curve Trees done. AFAIK, kayabaNerve is knocking on some doors to see who could work on it 15:58:40 ideally these things can be discussed in MRL/no wallet left behind meetings also 15:59:43 rbrunner: What's "it"? 15:59:59 The FCMP code 16:00:53 Im still +1 merge berman. Id rather not derail any momentum theyve created. Even if work doesnt pan out, maybe we'll find out before seraphis is even ready :P 16:02:32 so jberman merge / get feedback from MRL/no wallet left behind 16:03:21 Merge jberman 16:03:22 Sounds good to me 16:03:42 Also, merge jberman 16:04:01 i think merge before next meeting 16:04:02 If no negative feedback from mrl/NWLB/dev 16:04:35 AOB 16:05:36 Im assume kayabanerve: would say merge 16:05:41 msvb-lab shared in events that there will be a meeting in 1 hour 16:05:41 Anything else on the agenda? 16:05:50 no 16:06:48 monerokon is doing a lot of restructuring 16:07:35 #monero-translations:monero.social recently pushed a bunch of french translations to -site (yes, we still have passionate volunteers creating/reviewing translations 🙏) 16:07:47 So if involved with monerokon, or want tl be, pay attention to Monero Events because planning is already underway 16:09:19 "Finance Committee" to address concerns over reimbursement issue iirc , and other things.. creating a none profit to not have to rely on Digital Renegades for things / become independant 16:11:14 seems like we've came to an end, thank you all for joining and enjoy the rest of your weekend 👍️ 16:11:51 Good meeting and dankon everyone. 16:13:34 ah. One last note 16:14:12 Libera rooms will work differrnt with matrix soon. Youll need to join the matrix rooms 16:14:22 For example... (full message at ) 16:15:15 If you are joining from matrix and are in Libera.Chat #p2pool-log etc. I would recommend to move onto these (as they are plumbed and working already) before the cutoff date of portalled room https://libera.chat/news/matrix-deportalling 16:24:15 Thanks for mentioning, was going to do the same here but was waiting for meeting to be over :) 16:27:18 "But unless the fixes make it..." <- Yeah, I recently became aware that Monerujo is using a wallet_api extension for their pocketchange feature that I wrote for Feather eons ago and realized I could have saved them some time had that been available in core, so I think you're right to point this out and I will give upstreaming stuff higher priority going forward. 19:03:55 "0xffc: joining us?" <- Sorry, was sleep. Didn’t know it, otherwise would’ve woken up. Will ask you about details in pv 20:27:29 the 'built on Monero' game townforge has an upcoming version (including making blocks less blocky) demo video here (shared by Sysky in #townforge:libera.chat) https://www.yewtu.be/watch?v=zmRa-DV5R0I 21:30:23 Hey there, I'm new to the cryptospace and wanted to buy some Monero/BTC while avoiding KYC. I'll be visiting SFO/SJC area today if anyone is available and open to selling me some coins in person. 22:05:43 Better off using localmonero.co rather than posting randomly in a matrix room 22:15:04 Thanks for the tip! Sorry, I must have mistaken the intent of this room! 22:28:09 "the 'built on Monero' game..." <- Never actually saw Townforge 22:28:17 I don't play video games, but this is tempting