--- layout: post title: Overview and Logs for the Dev Meeting Held on 2017-05-21 summary: Sub / disposable addresses, new website, CLI/GUI lightwallet integration tags: [dev diaries, core, crypto] author: dEBRUYNE / fluffypony --- *May 21th, 2017* # Overview An overview [can be found on MoneroBase](https://monerobase.com/wiki/DevMeeting_2017-05-21). # Logs **\** we have to do the dev meeting really quietly so the pony can get some sleep **\** 1. Greetings **\** 2. Brief review of what's been completed since the previous meeting **\** 3. Code + ticket discussion / Q & A **\** 4. Any additional meeting items **\** 5. Confirm next meeting date/time **\** (no relay bot btw) **\** So, since last time, I'm not sure what's been merged. Not much I think ? There was the key image flaw made public too. **\** I'm working on abstracting network addresses. Mostly works, but serialization is being a massive pain. **\** Anyone else want to say anything about what they're working on ? **\** eventually I hope to have the amd64-51-30k speedups in wallet2.cpp (assuming fluffy approves) **\** and improve the hex -> bin performance would be nice too (not nearly ready for a merge though) **\** What is that short for ? **\** oh sorry, the ASM for wallet scanning **\** What are the 51 and 30k short for ? **\** its already written so that it can be removed by cmake, and does not touch the consensus code _at all_ **\** 51-bit limbs and 30k tables **\** 30k table singular, sorry **\** Anyone else doing something nice ? hyc, LMDB wallet code maybe ? :) **\** Nobody else ? tewinget ? **\** everyone is out spending bytecoins **\** Alright. Ticket discussion. The only thing I know is people reporting sync stopping. Some of them are user error, some are corrupt db, but I think there may be something else. I'd need to see good logs for both sides though. **\** Anyone wants to say anything about pending bugs ? **\** Testing related... your 1982 works nicely, with no apparent issues after several days. That on a daemon with none to very light load, fwiw. **\** Cool, thanks. **\** About pending bugs: we're still waiting for finalization of the disposable address theory, IIRC RandomRun and knacc were discussing a change recently. **\** knaccc: any comment about this ? **\** I'm syncing on Windows right now, albeit with non-default settings. Will report if it gets wedged. **\** change to which portion, disposable addresses or sub-addresses? **\** or I guess you specifically said disposable address **\** I don't remember. It's 1753. **\** I did, but not on purpose :) **\** I have a feeling it'll be a fast meeting. **\** luigi1112: anything new about smaller range proofs ? **\** he's out spending bytecoin too **\** happened to me today (sync); it just hanged; killed the process and restarted monerod; continued seamlessly **\** can re-sync with different loglvl to see if it happens again **\** Next time, don't kill it before you've looked at the thread stack traces. **\** Anything else someone wants to say in the meeting ? **\** Kovri test site? :D Not super dev-y, but nobody else says anything. **\** Kovri meeting is in 48 minutes. **\** there is no kovri meeting today **\** aw... then feel free. **\** anonimal: around ? **\** moneromooo sorry no. will update soooooon **\** ty **\** Hmm. **\** next meeting will be exciting :-) **\** Well, no test site either then. **\** oh baby i know what that means **\** i think **\** Next meeting: in two weeks, same time. **\** Done. The only good meetings are short meetings. **\** am I doing this right **\** ann of ann **\** mooo, how to use stacktrace? **\** Oh he's back now :) **\** jollymort: gdb /path/to/monerod `pidof monerod` **\** thread apply all bt **\** so i can do it while it's running **\** Yes. **\** no need to start it in some special way? **\** ok **\** i'll set loglvl to max also **\** and start sync from 0 **\** I wouldn't. **\** ok, so just restart and wait for it to hang? **\** 3 and 4 are toop spammy for being much use in general usage. **\** Yes. **\** rehrar: free free if you have something to say/show. **\** Anyways, Monero test site here: http://45.32.161.183/ mobile responsive now and a brand new mobile navigation. **\** Kovri test site: http://45.32.171.42/ completely integrated into the Jekyll. The custom CSS framework was ported without issue. This bodes well for my further work on getmonero.org. **\** Looks clean. **\** hi. a bit late to meeting. i'm working on lightwallet integration in cli and gui **\** or wallet2 mostly **\** You mean mymonero ? **\** We scrubbed it down. **\** yeah. and openmonero **\** should work with both backends **\** and should be switchable from full wallet to light wallet. vtnerd. would you consider implementing input/output import in mymonero api? **\** https://github.com/moneroexamples/openmonero/issues/21 **\** would make it possible to switch from full wallet to light wallet without a rescan **\** not clear how the mobile experience would go **\** just an initial impression **\** ? **\** experience of what? **\** as in how user gets wallet file on their mobile and how they pick it **\** I don't know what you mean Jacquee **\** you want to import an existing wallet quickly from a local DB to a mymonero backend ? **\** and also the other direction ? **\** that would be cool. maybe :-) **\** yeah. if i have a full wallet on my desktop and want to use the same wallet on my mobile. I could convert my full wallet to lightwallet by sending my inputs/outputs to mymonero/openmonero backend. And then login as usual on my phone **\** with seed **\** without paying the 1 xmr rescan fee **\** that was my idea **\** so the magic happens in desktop wallet. **\** on mobile you only login as usual **\** yeah, but its doable but I would have to think about it a bit **\** the backend would still want to verify correctness, so its not stomping on someone elses coins, etc **\** but it would be doing much less work **\** ok. yeah backend could verify with view key **\** that's probably best **\** yes. but it would only be looking at the set of outputs specified in the RPC call which will be much faster **\** exactly **\** Jaquee: ic **\** yeah so the import out will be much easier, and you can almost do it with unspent_outs call **\** *export I think is what normal people say **\** yeah. i'm almost done with that **\** i'm trying to make wallet2 fully compatible so i can switch between light wallet and using a normal node **\** well I meant but the export from the backend side, but ok interesting that you've already started the wallet side **\** yup, understood **\** how monero is configured to only cpu/gpu mining? **\** so, to summarize. if i create the mymonero wallet first i can already switch between full and light wallet mode. This import call i'm suggesting also makes it possible to switch from an old full wallet never initialized on mymonero. **\** ok