From ebbc8a7266cf14f8fee8c8304db44c8402339e49 Mon Sep 17 00:00:00 2001 From: el00ruobuob Date: Fri, 15 Mar 2019 12:50:24 +0100 Subject: [PATCH] tini2p meeting logs from 2019-03-14 --- ...e-tini2p-dev-meeting-held-on-2019-03-14.md | 111 ++++++++++++++++++ 1 file changed, 111 insertions(+) create mode 100644 _posts/2019-03-14-logs-for-the-tini2p-dev-meeting-held-on-2019-03-14.md diff --git a/_posts/2019-03-14-logs-for-the-tini2p-dev-meeting-held-on-2019-03-14.md b/_posts/2019-03-14-logs-for-the-tini2p-dev-meeting-held-on-2019-03-14.md new file mode 100644 index 00000000..35884448 --- /dev/null +++ b/_posts/2019-03-14-logs-for-the-tini2p-dev-meeting-held-on-2019-03-14.md @@ -0,0 +1,111 @@ +--- +layout: post +title: Overview and Logs for the tini2p Dev Meeting Held on 2019-03-14 +summary: Current project status, Roadmap, I2P proposal implementation, and miscellaneous +tags: [dev diaries, i2p, crypto] +author: el00ruobuob / oneiric +--- + +# Logs + +**\** time to meet is almost here +**\** thanks to everyone for attending/lurking +**\** item 0: Greetings +**\** Hey-o! +**\** hiyo all +**\** welcome Corklander, looks like it may just be us today again +**\** item 1: Current project status / what's been done +**\** have spent the last few weeks refactoring and implementing generic wrappers for ecies +**\** went down a rabbit hole that took way longer thatn expected +**\** than\* +**\** in the middle of switching crypto++ for libsodium +**\** last remaining piece is the AES impl, which will be replaced with tiny-aes +**\** hi. lurking. +**\** reddsa took a backburner spot, and i will refocus on it after necessary refactors +**\** hi kinghat +**\** should be finished with refactors in next few days, and will MR the changes on gitlab +**\** will leave it up for ~1 week for review +**\** other than that, been working on other housekeeping refactors, and attending i2p dev meetings +**\** any questions/comments? +**\** there were i2p dev meetings? were they public? +**\** will this have an FFS/ICO ? +**\** whoops. not i2p xmr related dev meetings. +**\** yep, every week for #ls2 meetings discussing new leaseset2/netdb specs +**\** lol the greatest ICO crim- +**\** with all the premines +**\** wheres the old project? +**\** which old project? +**\** there was a bid FFS on kvri? +**\** is this replacing that? +**\** nop, not from me +**\** i'm still up in the air on an ffs +**\** okay, continue +**\** well, the last one run with the money +**\** or so I've heard +**\** people might be afraid for another FFS +**\** atleast me +**\** idk about all that. my last ffs got a little borked with overpromising/miscommunication, which has hopefully been resolved +**\** if you or anyone would like to discuss it, i'm open +**\** im just here for the tini2p 😄 +**\** Same. Other projects are for other meetings, IMO. +**\** its my understanding that i fairly addressed regarding milestone completion, maybe you think differently crim-? +**\** regardless, i want people to feel they can approach me openly about funding questions +**\** Ah. +1 +**\** not here to swindle anyone, and i think my track record proves that +**\** any other questions about item 1? +**\** my brain has already forgotten about the many different privacy network implementations that are in dev atm since the kovri mess. +**\** true, i2pd is still actively developed, along with java i2p, and i2p-zero packaging +**\** and there is ire of course :) the rust impl +**\** there may be more +**\** so onto item 2: Short-term road map +**\** so will continue with refactors + reddsa/encls2 this week +**\** hopefully should be ready to test within the next 1-2 weeks +**\** after that will shift focus back to ecies and i2np for router-to-router communication +**\** hopefully the generic wrappers i've written will be flexible enough for whatever crypto primitives are settled on +**\** leaseset2 and proposal 123 afaiu are still the main focus for i2p project, though focus maybe be shifting to 144 +**\** don't quote me on that +**\** hopefully should have router-to-router communication within the next month or so +**\** at least ready for local testnet / vms +**\** also need to work on some docs / other meta housekeeping, and separating impl into ipp files +**\** any questions/comments on short-term plans? +**\** For the testnet plans, do you have specific objectives? +**\** yeah, i'd like to build something people can spin up locally with no outside networking +**\** As in: 1) must complete 'hello world' round trip. 2) must have memory leaks below 100MB/day, etc? +**\** oh +**\** tbh, haven't thought that far into it. but can come up with some metrics for automated testnet runs +**\** CI is still on my todo, so thanks for the reminder +**\** I'm asking because I'm not sure where to separate unit and integration tests for a network-layer project. +**\** currently, i have separated the independently testable stuff into unit\_tests +**\** stuff that requires networking goes in net\_tests +**\** Ah, right. Well that makes sense to my brain now. :) +**\** so far, haven't seen the need for a separate integration\_test, but will if the need arises +**\** had a slow-test dir for a bit, but it was only for elgamal, and only when prime search was turned on +**\** now there's no elgamal at all so !!!!! ::) +**\** also zzz brought up that it wasn't obvious the library is header-only, so people may think nothing has been done +**\** all of the impl is currently in .h files +**\** i will be splitting impl into .ipp files, but the library is still intended to be header-only +**\** will write a reference router in .cc, but library user's are encouraged to just include the headers without needing a separate bin for the router +**\** users'\* +**\** users? +**\** anyway +**\** if no more on 2, item 3: I2P proposal implementation (123, 144) +**\** not much has changed, str4d added a more fleshed-out reddsa spec +**\** there is currently some discussion over exactly how to do aplha generation and key blinding +**\** there will be another meeting in #ls2 on i2prc this upcoming monday, iirc +**\** 144 is the ecies-x25519-ratchet proposal +**\** any questions on tini2p impl plans or questions in general re: the new spec proposals? +**\** cool deal, looks like we'll be ending early +**\** last item: Confirm next meeting time +**\** same time in two weeks? +**\** sure. gotta jet. see ya! +**\** Sure +**\** l8er kinghat, thanks for lurkin +**\** ok so 2019-03-28 at 18:00 UTC +**\** meeting over, thanks all +**\** Yea! +**\** thanks oneiric\_ +**\** thanks for the input Corklander +**\** Sure! +**\** np wowario +**\** Good work, btw +**\** thanks man