--- layout: post title: Overview and Logs for the tini2p Dev Meeting Held on 2019-09-19 summary: Current project status, Roadmap, Meta issues, and miscellaneous tags: [dev diaries, i2p, crypto] author: el00ruobuob / oneiric --- # Logs **\** time of the meet **\** 0: Greetings **\** h **\** 1: What's been done **\** A lot **\** Finished tunnels impl, and merged into master **\** (with helpful review from @DavidBurkett) **\** I'm still used to being the only person working on the project, so have to habituate myself to a workflow that includes other people **\** started work on the router context (what ties all the pieces together) **\** Don't change anything because of me. I'm slow and unreliable **\** I'll catch up eventually, just keep doing what you're doing :) **\** in the process, came across some impl bugs in NTCP2 (fixed), updated NTCP2 to include a testnet v. mainnet netID, and started working on ECIES updates **\** no worries, I just meant that you're the first other than me to review my code :) **\** Haha, got it **\** for the ECIES updates: there has been a lot of them **\** zzz pushed updates to move us to something much closer to standard Noise, and I love the changes **\** it's a bit of work to change my impl, but all the changes are for the better **\** the code is looking much cleaner now **\** the cryptographic guarantees are stronger and more clear as well, which is the bigger win imo **\** :rocket: Do you have a link to zzz's updates? **\** you can follow my work in my context branch: https://gitlab.com/tini2p/tini2p/tree/context **\** Ah perfect **\** yeah, zzz's updates are pushed to the main 144 proposal: https://geti2p.net/spec/proposals/144-ecies-x25519-aead-ratchet **\** we're still working out some kinks in the handshake, and will need to update the ratchet KDFs afterwards **\** we are getting \*\*much\*\* closer to finalizing the spec though, which is awesome **\** so, my impl may deviate from the spec a bit until we get everything figured out **\** we're trying to get as close to standard Noise as possible, while maintaining the necessary properties for ECIES-X25519 stated goals **\** That's great news **\** definitely **\** :smile\_cat: **\** the downside to all that is I've spent a good amount of time refactoring, so don't have code that is ready for a release candidate **\** long-term it's for the best, in the short-term it's a slog to get to alpha release **\** which leads to the next item **\** 2: What's next **\** continue the refactors for ECIES-X25519 **\** get something working for end-to-end crypto sessions, and work with zzz on fixing spec bugs (if/when they come up) **\** finish the context impl **\** create the docker testnet for local integration testing **\** idk how long the docker testnet will take, but I'm hoping something minimal will be fairly easy to setup **\** if it takes more than a day or two, I'll push an alpha release candidate without the testnet **\** the biggest hurdle I see for the testnet is populating the NetDB of the routers with the RouterInfos of the other routers in the testnet **\** I don't have reseed impled, so I'll have to do something manual **\** you may find this useful: http://zzz.i2p/topics/2756-testnet-with-lxc-instructions **\** really hoping this is the last time I'll have to say this: pushing the alpha release date back another two weeks **\** awesome! thank you @zlatinb :) **\** also talk to "obscuratus" on Irc2P, he has a mixed i2pd/java i2p testnet, also with lxc **\** right on, I'm hoping to do it with docker for eventual windows support **\** right now, tini2p only builds on linux. will be working on cross-platform builds post-alpha **\** there's probably a lot of crossover in approach to lxc, so I appreciate the resources. will definitely be reaching out to obscuratus **\** Builds on mac also **\** But of course, that's based on linux **\** I nearly had it building on windows, but I got frustrated and quit :) **\** haha wow, thanks for build testing **\** yeah, I imagine the windows experience is pretty hellish atm **\** np, wasn't intentional. I'm the 0.1% of devs who prefers windows **\** So I tried there first **\** It wasn't quite as bad as you might think, but 1 of the dependencies was pissing me off lol **\** noise-c? **\** Yes, that's the one **\** yup **\** that's a bear **\** I'll be moving all the noise stuff into the project proper, and remove the noise-c lib **\** it's a great reference, but making it cross-platform is such a pain **\** Excellent. Let me know when you want me to try building again **\** will do, I appreciate the offer **\** :thumbsup: **\** long-term I hope to contribute a CMake build system to noise-c **\** atm that's low priority though **\** that will be extremely time-consuming, but I want to give something back to the project **\** rweather did a lot to help me understand Noise :) **\** so, that's more-or-less what I'll be working on: router context, ECIES updates, some NetDB stuff, docker testnet **\** 3: Questions/comments **\** alright, so that's the meeting **\** will do my best to get a release candidate out by next Thursday, and alpha release the following week **\** Looking forward to it **\** :+1: **\** 4: Next meeting **\** 2019-10-03 18:00 UTC **\** holy shit, we're already almost in October **\** thanks all for attending **\** @tini2p\_gitlab twirls the gavel