From 61861fc9e60f4a13adb60fd23e30936147300199 Mon Sep 17 00:00:00 2001 From: dEBRUYNE-1 Date: Tue, 21 Nov 2017 20:35:08 +0100 Subject: [PATCH] Overview and Logs for the Dev Meeting Held on 2017-11-19 --- ...-for-the-dev-meeting-held-on-2017-11-19.md | 265 ++++++++++++++++++ 1 file changed, 265 insertions(+) create mode 100644 _posts/2017-11-19-overview-and-logs-for-the-dev-meeting-held-on-2017-11-19.md diff --git a/_posts/2017-11-19-overview-and-logs-for-the-dev-meeting-held-on-2017-11-19.md b/_posts/2017-11-19-overview-and-logs-for-the-dev-meeting-held-on-2017-11-19.md new file mode 100644 index 00000000..3f79d793 --- /dev/null +++ b/_posts/2017-11-19-overview-and-logs-for-the-dev-meeting-held-on-2017-11-19.md @@ -0,0 +1,265 @@ +--- +layout: post +title: Overview and Logs for the Dev Meeting Held on 2017-11-19 +summary: Discussion of open PRs and issues, Bulletproofs, Monero Research Lab, Monero integrations, dedicated Monero hardware wallet, multisig, and miscellaneous +tags: [dev diaries, core, crypto] +author: dEBRUYNE / fluffypony +--- + +# Overview + +An overview can be found on [MoneroBase](https://monerobase.com/wiki/DevMeeting_2017-11-19). + +# Logs + +**\** Hey everyone! I don't know if fluffypony will be here today, but let's see about getting this thing started. +**\** Hello to everyone idling in the peanut gallery +**\** Hello. +**\** 2. Brief review of what's been completed since the previous meeting +**\** Can we get a mini-update from dev, gui, hardware, and mrl? +**\** I can speak for MRL +**\** We've been thoroughly investigated bulletproofs, a new form of CT range proofs +**\** is moneromooo here? +**\** Yes +**\** have one thing to bring up +**\** when there's time +**\** They should function as essentially a drop-in replacement that is 10% the size of the original proofs (for one output; even smaller for multiple outputs) +**\** with about the same verification time; possibly a teensy bit faster +**\** Kudos to andytoshi for a lot of great help on those, and others +**\** it's like a TARDIS! the bigger the input the smaller the output! /s +**\** So it's looking really promising that it'd be good for us? +**\** yes +**\** We'll start translating the Java test code over to C/C++ for more detailed work +**\** it's a win-win: smaller-spaced range-proofs, with the same verification time +**\** There were some doubts about ver time, but we literally just had a convo over in MRL that pointed out a simple caching that helps us +**\** MRL, folks. Let's give 'em a hand. +**\** It was pointed out, though, that there's very little randomness hanging around, which could affect storing stuff "in the randomness" +**\** That may be a deepe discussion for later +**\** yeah, using these range proofs makes encrypting messages with range proofs far less do-able +**\** \*deeper +**\** eh who cares +**\** MRL is excellent, nice. +**\** andytoshi is really the one who nailed it, btw +**\** aye +**\** aaaaand all his co-authors +**\** Can we send them a fruit basket? +**\** +1 +**\** which has included, for a second time, Jonathan Bootle +**\** rehrar set up an FFS for it +**\** 0.2 XMR +**\** and for the N^th time, greg maxwell +**\** 100 XMR requested +**\** biggest fruit basket ever +**\** Anyhoo, that's the big news from MRL right now, I suppose +**\** awesome. Thanks so much. +**\** multisig is looking like i will be ready to hand it off to sarang by the end of the month, as hoped. +**\** and thats it for now +**\** Anyone else have an update since the last meeting two weeks ago? +**\** This is huge from a scaling perspective +**\** absolutely +**\** dev has done a tone of PR merges latelt +**\** lately +**\** can you summarize them? +**\** there's still been build issues with readline dependencies but I think they're pretty much sorted by now +**\** we've isolated readline from GUI dependencies, etc. +**\** mooo can probably summarize better +**\** vtnerd says "oh good" +**\** "woo" +**\** Hmm. I can go look at github: +**\** (mostly small things anyway) +**\** FP confirmed he can't make it today. He sends his apologies. +**\** disguising password length in prompt I guess is still a small thing, but user visible +**\** less unnecessary locking in some DB readers, which should speed up some RPC +**\** Fixes for BSD build +**\** The wallet does not fetch unneeded hashes anymore (ie, starts direct from 1.4e6) +**\** CORS (for those who know what it is) +**\** A fix for show\_transfers missing more than one incoming input in a tx +**\** And I think the rest is either prior to last meeting, or small/internal stuff. +**\** yeah but it comprises a couple dozen PRs between then and now +**\** Alright, awesome. Thanks moneromooo. +**\** hardware, I know you give updates in community, but I think most of us that know are excited about the rapid progress you're making +**\** care to share something small about what's been going down? +**\** Hardware; we've settled our initial workflows and have built a twenty strong team. Journals are taking notice (see press) and the project is moving along. +**\** https://taiga.getmonero.org/project/michael-rfc-hwallet-1-implementation/wiki/press/ +**\** I'll mark our forum proposal milestone 1 as concluded today probably. +**\** We now have an open call to any interested in a hardware wallet, become part of the project and possibly test a prototype. See: +**\** https://taiga.getmonero.org/project/michael-rfc-hwallet-1-implementation/wiki/preview/ +**\** I'll demonstrate our two current working protoypes at this week's first ever Monero Munich meeting. +**\** That's all, any questions? +**\** What do you expect those who receive the prototypes to test? +**\** Very weak expectations, hopefully each finds their own way to contribute and strengthen the project. +**\** There's a test plan page, where people can make comments while testing. +**\** But that is just one of many choices, each individual can make on their own. +**\** Pretty lame answer no? +**\** Alright, thanks msvb-lab! +**\** Thanks for the opportunity. +**\** Sounds like pretty nice stuff is going on there, congrats :) +**\** (I counted 72 PRs merged since last dev meeting) +**\** hyc: Who make most of the merges, fluffy? +**\** So, we've got Code + ticket discussion / Q & A time available for the devs to discuss dev-y things. But all the mergy stuff may have to wait because of FP absence, but if there's other business to take care of, devs you have the floor +**\** yes he does all the merges +**\** we didn't get a report from GUI +**\** oh, right! so sorry. +**\** Anybody working on GUI have stuff to talk about. +**\** ping Jaquee ? +**\** so i've been chatting with mooo, Jaquee, and vtnerd recently about integrating MyMonero with the native mainline libwallet +**\** sorry. i'm on the run +**\** signs point to integrating with wallet\_api +**\** I may end up tackling a small portion of factoring wallet2 +**\** ok, no worries Jaquee. +**\** As long as not too many gratuitous changes ^\_^ +**\** 100% mooo +**\** all variable and class names being filtered thru pig-latin +**\** dsc, in here :) +**\** :) +**\** Is our GUI crew considered only monero-gui, or are mymonero.com and Moneruj (Android) included as well? +**\** has it started? +**\** lol hyc +**\** I think GUI crew is people who work on the monero-gui repo +**\** mymonero and Monerujo are their own thing +**\** dsc has what started? +**\** the meeting :D +**\** oh, yeah. We're about half hour in. :) +**\** oh - that's worth mentioning too - the repo is now properly named monero-gui, no longer monero-core +**\** rehrar: So Monerujo communicate on a different channel, right? +**\** That rename is a milestone :) +**\** Monerujo utilizes the Mattermost where they have a private channel for the devs and core team, and a public channel for questions. They've also got a Taiga to track progress. +**\** aight, so I'm working on a black theme for `monero-gui` (qt5) .. learning QML in the process. Trying to get some more UX developers involved and generally just trying to document things as I go +**\** I can rep Monerujo though, as I'm heavily involved with them +**\** they've got some exciting stuff coming +**\** yes, can you link your thread dsc? +**\** sure +**\** The one you made a few days ago. +**\** https://www.reddit.com/r/Monero/comments/7dvwq0/contributing_to_monero_as_an_ux_developer_short/ +**\** in the comments there are the various proposals for redesigning the GUI. Are there any thoughts on any of those? +**\** well, first dsc you wanted to say something, go ahead. :) +**\** No I was finished :P +**\** but to answer your question: There are 3 UI proposals of which I picked the one that was most trivial to implement +**\** seeing as I'm just one guy with zero QML experience, hehe. +**\** rehrar: Basically we're first kind of going for the dark theme, which will have a light mode as well +**\** Because it's most trivial to implement +**\** (only requires minor changes to the current design) +**\** https://github.com/monero-project/monero-core/issues/419 +**\** https://github.com/monero-project/monero-core/issues/869 +**\** https://github.com/monero-project/monero-core/issues/949 +**\** Some screenshots -> https://i.imgur.com/89YFUj7.png +**\** for those interested +**\** Ok. Cool deal! +**\** To clarify, the dark theme is #949 +**\** cool +**\** dsc also made a PR which should make the GUI more responsive +**\** cant make any predictions as to when I have some tangible, taking quite some time...! +**\** s/some/something/ +**\** Also, we're aiming to include subaddresses and multisig somewhere in the future^tm +**\** And, once there is a core appstore account, we'll start testing the ios port of the GUI +**\** There'll be an android port as well, fwiw +**\** dEBRUYNE: Is Qt5 easy to port to mobile? +**\** Is there a new android APK to test? I last saw one months ago +**\** sgp: Buildbot produces APKs iirc +**\** Let me check +**\** No that isn't setup now +**\** msvb-lab: Jaquee did it, so better to ask him :P +**\** I can't promise next week even, very busy +**\** rehrar: To give you an idea, right now I have this: https://i.imgur.com/iLwupdB.png +**\** or to give anyone an idea for that matter :) +**\** Hello +**\** looks pretty chill imo :D +**\** aye aye +**\** WIP ofc :) +**\** I personally think there needs to be a bit of a restructuring of some info, but this is a good meantime +**\** agreed +**\** good stuff +**\** would be nice to get a more recent android build up for people to test +**\** Alright. That's it from GUI? No other opinions on dEBRUYNE and dsc stuff either? +**\** looks like we can move on to ticket Q/A +**\** ok Code + ticket discussion / Q & A +**\** hyc moneromooo can you two take the lead for this? +**\** Well, if anyone has questions about them, please ask. +**\** I'd leave it to mooo. I'm not aware of any open questions +**\** ^^ +**\** ticket Q/A \!= discussing open PR's, right? +**\** sure +**\** ask away +**\** low hanging fruit PRs (that can probably be merged): #919, #954, #963 on monero-gui +**\** not so much a question ^\_^ +**\** probably ask luigi to merge them if fluffy is unavailable +**\** luigi merges GUI PRs anyway :) +**\** alright +**\** I think luigi is out for a few days, so be patient. (: +**\** Alrighty, shall we move on? +**\** FFS Formalization: https://github.com/monero-project/meta/pull/87 +**\** Is there meeting? +**\** serhack started 40 minutes ago +**\** we probably don't have time for a large discussion (if at all), but I just wanted to encourage the devs to take a look at the PR +**\** Oh +**\** I forgot it +**\** The idea of having a set of formalized guidelines for FFS proposals going forward has been thrown around a lot. It'd be good to get some opinions on how this is laid out and any concerns that may arise from it. +**\** I didn't understand well: is the project funded by ffs an Official project? +**\** Does the current system work? +**\** There's been hiccups ArticMine. fireice and guzzi come to mind. +**\** those seem like complete outliers :P +**\** not exactly legit claims to issues imo +**\** Largely based on de facto expectations that are not actually formalized. +**\** How do we learn about the hickups mentioned (in order to understand context?) +**\** but proposals could stand to be more concrete, specific, detailed, +**\** rehrar: formalization can be a bit of a rabbit hole as well +**\** sometimes humans need to be involved +**\** ppl need to recognize the situation before a formal plan can be applied +**\** indeed. current US political situation reflects this - institutions are designed assuming good faith in all participants +**\** but if the situation is not able to be recognized by ppl then how can it be applied for the desired result? +**\** nobody can take all the time needed to identify every possible abusable loophole +**\** What we have currently is a Core Team centered way of resolving disputes that, to my knowledge, hasn't really been utilized since I've been here +**\** since we've got that right now, maybe we stick with it? +**\** but identifying loopholes and plugging them is not a bad thing +**\** it's just that they need to be done by humans imo +**\** We may need some tweaking to deal with the hiccups; but as afar as I can see at a fundamental level the system is working +**\** don't know where else the graphic is, so I'll just link it here: https://getkovri.org/contributing.html +**\** bottom of the page +**\** This has not been formally replaced, so it is currently active. We can discuss that at a later time though. Let's move on. +**\** 5. Any additional meeting items +**\** If anyone has anything, speak up. :) +**\** If anyone wants to test multisig, feel free. PR 2134. +**\** is there a set date for the next code freeze? +**\** A little update by me about Monero Integrations +**\** go for it serhack +**\** So we (I and cryptochangements) are going to release Magento Plugin, In the past few weeks, we worked on a new cool payment box for Monero Integrations. +**\** +**\** I am currently working on OpenCart too so I think we can release Magento payment box the next week.. +**\** +**\** I have talked to OpenBazaar too and they have told me that Monero + Openbazaar would be nice.. it will be a difficult task but I think I can do it +**\** you can go on, rehrar +**\** Everytime I read OpenBazaar, it makes me want to punch that scammer from a few years back... +**\** alright, thanks man :) +**\** atrides? +**\** That's the one. +**\** doesn't he still run Dwarfpool? +**\** yeah, and ppl still mine on it +**\** We should encourage them not to +**\** Either way: 6. Confirm next meeting date/time +**\** December 3rd? Same time? +**\** so no freeze date, eh? +**\** Should we move time because daylight savings? +**\** About mid december +**\** word. +**\** Please do not move the time +**\** Or january. Unclear. +**\** ok, time not moved +**\** FP would have a better answer? +**\** isn't a release due in January? +**\** and we're supposed to freeze a month before +**\** March +**\** well dec or jan gives us 3 months +**\** ok +**\** There's a new freeze/release schedule isn't there? +**\** mebbe someone can open a meta issue and set some dates into it +**\** i thought we had 3 months of freeze for more testing / fixing than before .... +**\** 3 months of freeze is gonna make me punch someone else :P +**\** It's branch, then release from the brnch aftrer 2-3 months. +**\** It's already painful when stuff doens't get merged after a month. +**\** The big one is the bullet proofs +**\** right. i thought branch is a freeze... i.e., feature freeze.... i.e., freeze on adding wacky new stuff that requires bandaloots and warples +**\** That's not likely to be ready by then. +**\** but yeah... perhaps that should be documented somewhere +**\** (Not to interrupt, but meeting is over for those who need to go, discussion can of course continue) +**\** Alright. You guys are the best! thanks for being a part of this community, and developing the software we all know and love as Morono +**\** rehrar: Thanks, good flow of topics, great moderation. \ No newline at end of file