diff --git a/_posts/2017-07-02-logs-for-the-Community-meeting-held-on-2017-07-02.md b/_posts/2017-07-02-logs-for-the-Community-meeting-held-on-2017-07-02.md index 5c7d5e33..41c12944 100644 --- a/_posts/2017-07-02-logs-for-the-Community-meeting-held-on-2017-07-02.md +++ b/_posts/2017-07-02-logs-for-the-Community-meeting-held-on-2017-07-02.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2017-07-02 summary: Official website, marketing / social media, slogan, Kovri, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: dEBRUYNE / fluffypony --- diff --git a/_posts/2017-07-16-logs-for-the-Community-meeting-held-on-2017-07-16.md b/_posts/2017-07-16-logs-for-the-Community-meeting-held-on-2017-07-16.md index c91296d4..b5915a98 100644 --- a/_posts/2017-07-16-logs-for-the-Community-meeting-held-on-2017-07-16.md +++ b/_posts/2017-07-16-logs-for-the-Community-meeting-held-on-2017-07-16.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2017-07-16 summary: Work groups and IRC channel reorganization, meeting structure, slogan, user guides, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: dEBRUYNE / fluffypony --- diff --git a/_posts/2017-07-30-logs-for-the-Community-meeting-held-on-2017-07-30.md b/_posts/2017-07-30-logs-for-the-Community-meeting-held-on-2017-07-30.md index 32cae8ef..20ab8bae 100644 --- a/_posts/2017-07-30-logs-for-the-Community-meeting-held-on-2017-07-30.md +++ b/_posts/2017-07-30-logs-for-the-Community-meeting-held-on-2017-07-30.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2017-07-30 summary: Monero Meetups, Case studies – communities in other cryptocurrencies, Twitter / Facebook background, helping out with testing, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: dEBRUYNE / fluffypony --- diff --git a/_posts/2017-10-09-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-10-09.md b/_posts/2017-10-09-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-10-09.md index 39f28138..e456fd31 100644 --- a/_posts/2017-10-09-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-10-09.md +++ b/_posts/2017-10-09-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-10-09.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2017-10-09 summary: Announcements, Round table discussion of projects, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / surae --- diff --git a/_posts/2017-10-30-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-10-30.md b/_posts/2017-10-30-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-10-30.md index 0161f5de..613cdf5b 100644 --- a/_posts/2017-10-30-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-10-30.md +++ b/_posts/2017-10-30-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-10-30.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2017-10-30 summary: Multisig, hash-based accumulators, blockchain protocols, quantum-hard shuffle PRNG, educational outreach, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: dEBRUYNE / fluffypony --- diff --git a/_posts/2017-11-13-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-11-13.md b/_posts/2017-11-13-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-11-13.md index ad915dce..1966883a 100644 --- a/_posts/2017-11-13-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-11-13.md +++ b/_posts/2017-11-13-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-11-13.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2017-11-13 summary: Educational outreach, multisig, Bulletproofs (range proofs), RuffCT, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: dEBRUYNE / fluffypony --- diff --git a/_posts/2017-11-27-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-11-27.md b/_posts/2017-11-27-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-11-27.md index 91b254fd..67dda494 100644 --- a/_posts/2017-11-27-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-11-27.md +++ b/_posts/2017-11-27-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-11-27.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2017-11-27 summary: SPECTRE, multisig, Bulletproofs (range proofs), ZKStarks, ASIC resistance, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: dEBRUYNE / fluffypony --- diff --git a/_posts/2017-12-09-logs-for-the-Community-meeting-held-on-2017-12-09.md b/_posts/2017-12-09-logs-for-the-Community-meeting-held-on-2017-12-09.md index 38122164..0c555d18 100644 --- a/_posts/2017-12-09-logs-for-the-Community-meeting-held-on-2017-12-09.md +++ b/_posts/2017-12-09-logs-for-the-Community-meeting-held-on-2017-12-09.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2017-12-09 summary: Community highlights, Forum Funding System updates, RFC-HWALLET-1, Monero video series, Malware Response Workgroup, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: dEBRUYNE / fluffypony --- diff --git a/_posts/2017-12-11-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-12-11.md b/_posts/2017-12-11-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-12-11.md index e86e2e16..d5f01781 100644 --- a/_posts/2017-12-11-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-12-11.md +++ b/_posts/2017-12-11-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-12-11.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2017-12-11 summary: Bulletproofs (range proofs), ASIC resistance, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: dEBRUYNE / fluffypony --- diff --git a/_posts/2017-12-18-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-12-18.md b/_posts/2017-12-18-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-12-18.md index 0121fb0f..21c4dec7 100644 --- a/_posts/2017-12-18-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-12-18.md +++ b/_posts/2017-12-18-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-12-18.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2017-12-18 summary: MRL work, MRL 2018 forecast, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / surae --- diff --git a/_posts/2017-12-23-logs-for-the-Community-meeting-held-on-2017-12-23.md b/_posts/2017-12-23-logs-for-the-Community-meeting-held-on-2017-12-23.md index 9cc0df30..ad35446e 100644 --- a/_posts/2017-12-23-logs-for-the-Community-meeting-held-on-2017-12-23.md +++ b/_posts/2017-12-23-logs-for-the-Community-meeting-held-on-2017-12-23.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2017-12-23 summary: Community highlights, Forum Funding System updates, RFC-HWALLET-1, Malware Response Workgroup, Forum Funding System donor flairs, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: dEBRUYNE / fluffypony --- diff --git a/_posts/2018-01-05-logs-for-the-Hardware-meeting-held-on-2018-01-05.md b/_posts/2018-01-05-logs-for-the-Hardware-meeting-held-on-2018-01-05.md index 3ec23556..11e33572 100644 --- a/_posts/2018-01-05-logs-for-the-Hardware-meeting-held-on-2018-01-05.md +++ b/_posts/2018-01-05-logs-for-the-Hardware-meeting-held-on-2018-01-05.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Hardware Meeting Held on 2018-01-05 summary: Poll conducted, Reddit summaries, status report(s), conclusion of name search, highlights of 34C3 in Leipzig, etherpads for groups, test plan discussion, recent firmware & FPGA research, mechanical engineering, recent logo contributions, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: dEBRUYNE / fluffypony --- diff --git a/_posts/2018-01-06-logs-for-the-Community-meeting-held-on-2018-01-06.md b/_posts/2018-01-06-logs-for-the-Community-meeting-held-on-2018-01-06.md index bb7362ee..f121a9f6 100644 --- a/_posts/2018-01-06-logs-for-the-Community-meeting-held-on-2018-01-06.md +++ b/_posts/2018-01-06-logs-for-the-Community-meeting-held-on-2018-01-06.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2018-01-06 summary: Community highlights, Forum Funding System updates, RFC-HWALLET-1, Rehrar's Kovri proposal, Serhack's integrations, Fondajo, community materials, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: dEBRUYNE / fluffypony --- diff --git a/_posts/2018-01-12-logs-for-the-Hardware-firmware-meeting-held-on-2018-01-12.md b/_posts/2018-01-12-logs-for-the-Hardware-firmware-meeting-held-on-2018-01-12.md index 7cda4aff..66f4ae59 100644 --- a/_posts/2018-01-12-logs-for-the-Hardware-firmware-meeting-held-on-2018-01-12.md +++ b/_posts/2018-01-12-logs-for-the-Hardware-firmware-meeting-held-on-2018-01-12.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Hardware Firmware Meeting Held on 2018-01-12 summary: Discussion of the firmware for the dedicated hardware wallet and a discussion of Ledger's approach -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: dEBRUYNE / fluffypony --- diff --git a/_posts/2018-01-20-logs-for-the-Community-meeting-held-on-2018-01-20.md b/_posts/2018-01-20-logs-for-the-Community-meeting-held-on-2018-01-20.md index 3a9bd660..55f733f4 100644 --- a/_posts/2018-01-20-logs-for-the-Community-meeting-held-on-2018-01-20.md +++ b/_posts/2018-01-20-logs-for-the-Community-meeting-held-on-2018-01-20.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2018-01-20 summary: Community highlights, Forum Funding System updates, RFC-HWALLET-1, Kasisto, open ideas, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: dEBRUYNE / fluffypony --- diff --git a/_posts/2018-01-29-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-01-29.md b/_posts/2018-01-29-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-01-29.md index 6b49f794..5cf7821a 100644 --- a/_posts/2018-01-29-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-01-29.md +++ b/_posts/2018-01-29-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-01-29.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-01-29 summary: MRL direction, ideas for research, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: dEBRUYNE / fluffypony --- diff --git a/_posts/2018-02-03-logs-for-the-Community-meeting-held-on-2018-02-03.md b/_posts/2018-02-03-logs-for-the-Community-meeting-held-on-2018-02-03.md index 63b1e21f..9611e7c2 100644 --- a/_posts/2018-02-03-logs-for-the-Community-meeting-held-on-2018-02-03.md +++ b/_posts/2018-02-03-logs-for-the-Community-meeting-held-on-2018-02-03.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2018-02-03 summary: Community highlights, Monero Integrations, Monero outreach initiative, Forum Funding System updates, RFC-HWALLET-1, Localization workgroup, open ideas, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: dEBRUYNE / fluffypony --- diff --git a/_posts/2018-02-05-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-02-05.md b/_posts/2018-02-05-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-02-05.md index 6ae534d8..15e43a9e 100644 --- a/_posts/2018-02-05-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-02-05.md +++ b/_posts/2018-02-05-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-02-05.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-02-05 summary: Bulletproofs, dedicated Monero conference, increasing minimum ring size, making ring size static, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: dEBRUYNE / fluffypony --- diff --git a/_posts/2018-02-12-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-02-12.md b/_posts/2018-02-12-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-02-12.md index 49bc1839..6e97c00c 100644 --- a/_posts/2018-02-12-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-02-12.md +++ b/_posts/2018-02-12-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-02-12.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-02-12 summary: Bulletproofs, auditing Bulletproofs, dedicated Monero conference, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: dEBRUYNE / fluffypony --- diff --git a/_posts/2018-02-17-logs-for-the-Community-meeting-held-on-2018-02-17.md b/_posts/2018-02-17-logs-for-the-Community-meeting-held-on-2018-02-17.md index 728d6a09..b3ab49c6 100644 --- a/_posts/2018-02-17-logs-for-the-Community-meeting-held-on-2018-02-17.md +++ b/_posts/2018-02-17-logs-for-the-Community-meeting-held-on-2018-02-17.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2018-02-17 summary: Community highlights, Forum Funding System updates, RFC-HWALLET-1, Localization workgroup, March HF, chain split discussion (e.g. MoneroV), and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: dEBRUYNE / fluffypony --- diff --git a/_posts/2018-02-19-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-02-19.md b/_posts/2018-02-19-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-02-19.md index 7ad6f0fc..44ec65cf 100644 --- a/_posts/2018-02-19-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-02-19.md +++ b/_posts/2018-02-19-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-02-19.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-02-19 summary: Multisig (paper), chain split (e.g. MoneroV), anonymity set, auditing options, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: dEBRUYNE / fluffypony --- diff --git a/_posts/2018-02-26-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-02-26.md b/_posts/2018-02-26-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-02-26.md index 2c34f7e5..0b897fd8 100644 --- a/_posts/2018-02-26-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-02-26.md +++ b/_posts/2018-02-26-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-02-26.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-02-26 summary: Sarang work, Surae work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / surae --- diff --git a/_posts/2018-03-03-logs-for-the-Community-meeting-held-on-2018-03-03.md b/_posts/2018-03-03-logs-for-the-Community-meeting-held-on-2018-03-03.md index 5714eee4..bd9dcb68 100644 --- a/_posts/2018-03-03-logs-for-the-Community-meeting-held-on-2018-03-03.md +++ b/_posts/2018-03-03-logs-for-the-Community-meeting-held-on-2018-03-03.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2018-03-03 summary: Community highlights, Forum Funding System updates, RFC-HWALLET-1, Localization workgroup, Bulletproof audit discussion, MoneroV discussion, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: el00ruobuob / SamsungGalaxyPlayer --- diff --git a/_posts/2018-03-05-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-03-05.md b/_posts/2018-03-05-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-03-05.md index 36ef15cb..46732fe9 100644 --- a/_posts/2018-03-05-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-03-05.md +++ b/_posts/2018-03-05-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-03-05.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-03-05 summary: Sarang work, Surae work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / surae --- diff --git a/_posts/2018-03-12-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-03-12.md b/_posts/2018-03-12-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-03-12.md index 857bcb9b..fbd67f89 100644 --- a/_posts/2018-03-12-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-03-12.md +++ b/_posts/2018-03-12-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-03-12.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-03-12 summary: BP audit, Sarang work, Surae work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / surae --- diff --git a/_posts/2018-03-19-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-03-19.md b/_posts/2018-03-19-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-03-19.md index 5b7131a9..29abbf05 100644 --- a/_posts/2018-03-19-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-03-19.md +++ b/_posts/2018-03-19-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-03-19.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-03-19 summary: MRL work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / surae --- diff --git a/_posts/2018-03-26-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-03-26.md b/_posts/2018-03-26-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-03-26.md index 6e98473f..60db793c 100644 --- a/_posts/2018-03-26-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-03-26.md +++ b/_posts/2018-03-26-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-03-26.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-03-26 summary: MRL work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / surae --- diff --git a/_posts/2018-03-31-logs-for-the-Community-meeting-held-on-2018-03-31.md b/_posts/2018-03-31-logs-for-the-Community-meeting-held-on-2018-03-31.md index 3a3a0589..e26f93fe 100644 --- a/_posts/2018-03-31-logs-for-the-Community-meeting-held-on-2018-03-31.md +++ b/_posts/2018-03-31-logs-for-the-Community-meeting-held-on-2018-03-31.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2018-03-31 summary: Community highlights, Forum Funding System updates, RFC-HWALLET-1, Localization workgroup, RIAT Monero workgroup, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: el00ruobuob / SamsungGalaxyPlayer --- diff --git a/_posts/2018-04-02-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-04-02.md b/_posts/2018-04-02-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-04-02.md index 01814a1e..32f8cf9a 100644 --- a/_posts/2018-04-02-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-04-02.md +++ b/_posts/2018-04-02-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-04-02.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-04-02 summary: Sarang work, Surae work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / surae --- diff --git a/_posts/2018-04-09-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-04-09.md b/_posts/2018-04-09-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-04-09.md index 34bf5eae..51eb5e29 100644 --- a/_posts/2018-04-09-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-04-09.md +++ b/_posts/2018-04-09-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-04-09.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-04-09 summary: Sarang work, Surae work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / surae --- diff --git a/_posts/2018-04-14-logs-for-the-Community-meeting-held-on-2018-04-14.md b/_posts/2018-04-14-logs-for-the-Community-meeting-held-on-2018-04-14.md index c2c7a584..44d95742 100644 --- a/_posts/2018-04-14-logs-for-the-Community-meeting-held-on-2018-04-14.md +++ b/_posts/2018-04-14-logs-for-the-Community-meeting-held-on-2018-04-14.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2018-04-14 summary: Community highlights, Forum Funding System updates, Localization workgroup, Important update for the community workgroup, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: el00ruobuob / SamsungGalaxyPlayer --- diff --git a/_posts/2018-04-16-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-04-16.md b/_posts/2018-04-16-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-04-16.md index 9240bd99..588d2962 100644 --- a/_posts/2018-04-16-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-04-16.md +++ b/_posts/2018-04-16-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-04-16.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-04-16 summary: Sarang work, Surae work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / surae --- diff --git a/_posts/2018-04-28-logs-for-the-Community-meeting-held-on-2018-04-28.md b/_posts/2018-04-28-logs-for-the-Community-meeting-held-on-2018-04-28.md index f0bed121..e5bea085 100644 --- a/_posts/2018-04-28-logs-for-the-Community-meeting-held-on-2018-04-28.md +++ b/_posts/2018-04-28-logs-for-the-Community-meeting-held-on-2018-04-28.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2018-04-28 summary: Community highlights, Forum Funding System updates, Localization workgroup Q&A, Monero Integrations, Monero QR GUI discussion, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: el00ruobuob / SamsungGalaxyPlayer --- diff --git a/_posts/2018-04-30-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-04-30.md b/_posts/2018-04-30-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-04-30.md index 885ed79b..d7e62942 100644 --- a/_posts/2018-04-30-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-04-30.md +++ b/_posts/2018-04-30-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-04-30.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-04-30 summary: Sarang work, Surae work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / surae --- diff --git a/_posts/2018-05-07-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-05-07.md b/_posts/2018-05-07-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-05-07.md index f8695ac4..5a2a4fcc 100644 --- a/_posts/2018-05-07-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-05-07.md +++ b/_posts/2018-05-07-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-05-07.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-05-07 summary: Sarang work, Surae work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / surae --- diff --git a/_posts/2018-05-12-logs-for-the-Community-meeting-held-on-2018-05-12.md b/_posts/2018-05-12-logs-for-the-Community-meeting-held-on-2018-05-12.md index 82677132..34c73eb5 100644 --- a/_posts/2018-05-12-logs-for-the-Community-meeting-held-on-2018-05-12.md +++ b/_posts/2018-05-12-logs-for-the-Community-meeting-held-on-2018-05-12.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2018-05-12 summary: Community highlights, Forum Funding System updates, Localization workgroup Q&A, open ideas, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: el00ruobuob / SamsungGalaxyPlayer --- diff --git a/_posts/2018-05-14-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-05-14.md b/_posts/2018-05-14-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-05-14.md index 4c9741aa..a2383761 100644 --- a/_posts/2018-05-14-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-05-14.md +++ b/_posts/2018-05-14-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-05-14.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-05-14 summary: MRL work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / sarang --- diff --git a/_posts/2018-05-21-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-05-21.md b/_posts/2018-05-21-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-05-21.md index 90368b75..81d23aa4 100644 --- a/_posts/2018-05-21-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-05-21.md +++ b/_posts/2018-05-21-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-05-21.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-05-21 summary: Sarang work, Surae work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / surae --- diff --git a/_posts/2018-05-26-logs-for-the-Community-meeting-held-on-2018-05-26.md b/_posts/2018-05-26-logs-for-the-Community-meeting-held-on-2018-05-26.md index 8818d1a0..bed66d51 100644 --- a/_posts/2018-05-26-logs-for-the-Community-meeting-held-on-2018-05-26.md +++ b/_posts/2018-05-26-logs-for-the-Community-meeting-held-on-2018-05-26.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2018-05-26 summary: Community highlights, Forum Funding System updates, Localization workgroup Q&A, Core Team FFS funds reallocation discussion, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: el00ruobuob / rehrar --- diff --git a/_posts/2018-05-28-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-05-28.md b/_posts/2018-05-28-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-05-28.md index a91061fc..ad3d8139 100644 --- a/_posts/2018-05-28-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-05-28.md +++ b/_posts/2018-05-28-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-05-28.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-05-28 summary: Sarang work, Surae work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / surae --- diff --git a/_posts/2018-06-04-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-06-04.md b/_posts/2018-06-04-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-06-04.md index 07977a64..a00a2cd7 100644 --- a/_posts/2018-06-04-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-06-04.md +++ b/_posts/2018-06-04-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-06-04.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-06-04 summary: Sarang work, Surae work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / surae --- diff --git a/_posts/2018-06-09-logs-for-the-Community-meeting-held-on-2018-06-09.md b/_posts/2018-06-09-logs-for-the-Community-meeting-held-on-2018-06-09.md index 4d61b594..9fbf183e 100644 --- a/_posts/2018-06-09-logs-for-the-Community-meeting-held-on-2018-06-09.md +++ b/_posts/2018-06-09-logs-for-the-Community-meeting-held-on-2018-06-09.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2018-06-09 summary: Community workgroup and meeting purpose, Community highlights, Forum Funding System updates, New community meeting/event calendar, Localization workgroup report, PR, O&E workgroup report, Malware response workgroup report, Meeting date/time discussion, open ideas, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: el00ruobuob / SamsungGalaxyPlayer --- diff --git a/_posts/2018-06-11-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-06-11.md b/_posts/2018-06-11-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-06-11.md index 6cc0ad3c..b322480e 100644 --- a/_posts/2018-06-11-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-06-11.md +++ b/_posts/2018-06-11-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-06-11.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-06-11 summary: MRL work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / surae --- diff --git a/_posts/2018-06-18-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-06-18.md b/_posts/2018-06-18-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-06-18.md index 068fc50c..ce797d65 100644 --- a/_posts/2018-06-18-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-06-18.md +++ b/_posts/2018-06-18-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-06-18.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-06-18 summary: MRL work, DefCon plans, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / surae --- diff --git a/_posts/2018-06-23-logs-for-the-Community-meeting-held-on-2018-06-23.md b/_posts/2018-06-23-logs-for-the-Community-meeting-held-on-2018-06-23.md index 3db14e2d..bacec3ab 100644 --- a/_posts/2018-06-23-logs-for-the-Community-meeting-held-on-2018-06-23.md +++ b/_posts/2018-06-23-logs-for-the-Community-meeting-held-on-2018-06-23.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2018-06-23 summary: Community highlights, Community workgroup developments, Forum Funding System updates, Localization workgroup report, Outreach workgroup report, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: el00ruobuob / SamsungGalaxyPlayer --- diff --git a/_posts/2018-06-25-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-06-25.md b/_posts/2018-06-25-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-06-25.md index 026b9fec..bf94b485 100644 --- a/_posts/2018-06-25-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-06-25.md +++ b/_posts/2018-06-25-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-06-25.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-06-25 summary: MRL work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / surae --- diff --git a/_posts/2018-07-02-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-07-02.md b/_posts/2018-07-02-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-07-02.md index 20fe5428..8da0d393 100644 --- a/_posts/2018-07-02-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-07-02.md +++ b/_posts/2018-07-02-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-07-02.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-07-02 summary: Sarang work, Surae work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / sarang --- diff --git a/_posts/2018-07-07-logs-for-the-Community-meeting-held-on-2018-07-07.md b/_posts/2018-07-07-logs-for-the-Community-meeting-held-on-2018-07-07.md index 094f2448..1efd7351 100644 --- a/_posts/2018-07-07-logs-for-the-Community-meeting-held-on-2018-07-07.md +++ b/_posts/2018-07-07-logs-for-the-Community-meeting-held-on-2018-07-07.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2018-07-07 summary: Community highlights, Forum Funding System updates, Dutch translations discussion, Monero Outreach discussion, Outreach workgroup report, Monero Marketing workgorup (including r/MoneroMarketing potential transfer) report, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: el00ruobuob / SamsungGalaxyPlayer --- diff --git a/_posts/2018-07-09-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-07-09.md b/_posts/2018-07-09-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-07-09.md index 8e347b3b..a52d38e0 100644 --- a/_posts/2018-07-09-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-07-09.md +++ b/_posts/2018-07-09-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-07-09.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-07-09 summary: MRL work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / sarang --- diff --git a/_posts/2018-07-16-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-07-16.md b/_posts/2018-07-16-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-07-16.md index 89d6fd29..c047e97a 100644 --- a/_posts/2018-07-16-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-07-16.md +++ b/_posts/2018-07-16-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-07-16.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-07-16 summary: Sarang work, Surae work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / sarang --- diff --git a/_posts/2018-07-21-logs-for-the-Community-meeting-held-on-2018-07-21.md b/_posts/2018-07-21-logs-for-the-Community-meeting-held-on-2018-07-21.md index 284c835d..d37c1948 100644 --- a/_posts/2018-07-21-logs-for-the-Community-meeting-held-on-2018-07-21.md +++ b/_posts/2018-07-21-logs-for-the-Community-meeting-held-on-2018-07-21.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2018-07-21 summary: Community highlights, Forum Funding System updates, Workgroup report, Tracking challenge discussion, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: el00ruobuob / SamsungGalaxyPlayer --- diff --git a/_posts/2018-07-23-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-07-23.md b/_posts/2018-07-23-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-07-23.md index 3da09e0c..c31ac437 100644 --- a/_posts/2018-07-23-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-07-23.md +++ b/_posts/2018-07-23-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-07-23.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-07-23 summary: Sarang work, Surae work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / surae --- diff --git a/_posts/2018-07-30-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-07-30.md b/_posts/2018-07-30-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-07-30.md index 5269d53c..e1565581 100644 --- a/_posts/2018-07-30-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-07-30.md +++ b/_posts/2018-07-30-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-07-30.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-07-30 summary: Sarang work, others work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / sarang --- diff --git a/_posts/2018-08-20-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-08-20.md b/_posts/2018-08-20-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-08-20.md index f2ec50e9..6131c964 100644 --- a/_posts/2018-08-20-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-08-20.md +++ b/_posts/2018-08-20-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-08-20.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-08-20 summary: Sarang work, Surae work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / surae --- diff --git a/_posts/2018-08-27-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-08-27.md b/_posts/2018-08-27-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-08-27.md index c0d59e67..640d474c 100644 --- a/_posts/2018-08-27-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-08-27.md +++ b/_posts/2018-08-27-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-08-27.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-08-27 summary: Sarang work, Surae work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / surae --- diff --git a/_posts/2018-09-01-logs-for-the-Community-meeting-held-on-2018-09-01.md b/_posts/2018-09-01-logs-for-the-Community-meeting-held-on-2018-09-01.md index 1fe2d62b..4808dbe9 100644 --- a/_posts/2018-09-01-logs-for-the-Community-meeting-held-on-2018-09-01.md +++ b/_posts/2018-09-01-logs-for-the-Community-meeting-held-on-2018-09-01.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2018-09-01 summary: Community highlights, Forum Funding System updates, Workgroup report, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: el00ruobuob / SamsungGalaxyPlayer / rehrar --- diff --git a/_posts/2018-09-15-logs-for-the-Community-meeting-held-on-2018-09-15.md b/_posts/2018-09-15-logs-for-the-Community-meeting-held-on-2018-09-15.md index 7f455277..462f1a0c 100644 --- a/_posts/2018-09-15-logs-for-the-Community-meeting-held-on-2018-09-15.md +++ b/_posts/2018-09-15-logs-for-the-Community-meeting-held-on-2018-09-15.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2018-09-15 summary: Community highlights, Forum Funding System updates, Workgroup report, Changelly r/Monero discussion, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: el00ruobuob / SamsungGalaxyPlayer --- diff --git a/_posts/2018-09-17-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-09-17.md b/_posts/2018-09-17-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-09-17.md index f284f4cb..f409ae37 100644 --- a/_posts/2018-09-17-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-09-17.md +++ b/_posts/2018-09-17-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-09-17.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-09-17 summary: Sarang work, Surae work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / surae --- diff --git a/_posts/2018-09-24-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-09-24.md b/_posts/2018-09-24-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-09-24.md index 51cd49a4..72a7f952 100644 --- a/_posts/2018-09-24-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-09-24.md +++ b/_posts/2018-09-24-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-09-24.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-09-24 summary: Sarang work, Surae work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / surae --- diff --git a/_posts/2018-09-29-logs-for-the-Community-meeting-held-on-2018-09-29.md b/_posts/2018-09-29-logs-for-the-Community-meeting-held-on-2018-09-29.md index e961a92a..5681ee2c 100644 --- a/_posts/2018-09-29-logs-for-the-Community-meeting-held-on-2018-09-29.md +++ b/_posts/2018-09-29-logs-for-the-Community-meeting-held-on-2018-09-29.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2018-09-29 summary: Community highlights, Forum Funding System updates, Workgroup report, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: el00ruobuob / SamsungGalaxyPlayer --- diff --git a/_posts/2018-10-01-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-10-01.md b/_posts/2018-10-01-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-10-01.md index 629b3152..264da388 100644 --- a/_posts/2018-10-01-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-10-01.md +++ b/_posts/2018-10-01-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-10-01.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-10-01 summary: Surae work, Sarang work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / sarang --- diff --git a/_posts/2018-10-08-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-10-08.md b/_posts/2018-10-08-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-10-08.md index e4b0cd02..e775c403 100644 --- a/_posts/2018-10-08-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-10-08.md +++ b/_posts/2018-10-08-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-10-08.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-10-08 summary: Surae work, Sarang work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / sarang --- diff --git a/_posts/2018-10-13-logs-for-the-Community-meeting-held-on-2018-10-13.md b/_posts/2018-10-13-logs-for-the-Community-meeting-held-on-2018-10-13.md index 11f7e27a..a092b9fe 100644 --- a/_posts/2018-10-13-logs-for-the-Community-meeting-held-on-2018-10-13.md +++ b/_posts/2018-10-13-logs-for-the-Community-meeting-held-on-2018-10-13.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2018-10-13 summary: Community highlights, Forum Funding System updates, Workgroup report, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: rehrar / SamsungGalaxyPlayer --- diff --git a/_posts/2018-10-15-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-10-15.md b/_posts/2018-10-15-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-10-15.md index 56c7fa09..a348641f 100644 --- a/_posts/2018-10-15-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-10-15.md +++ b/_posts/2018-10-15-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-10-15.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-10-15 summary: Surae work, Sarang work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / sarang --- diff --git a/_posts/2018-10-22-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-10-22.md b/_posts/2018-10-22-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-10-22.md index 4f0ea500..39d0e00a 100644 --- a/_posts/2018-10-22-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-10-22.md +++ b/_posts/2018-10-22-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-10-22.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-10-22 summary: Surae work, Sarang work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / sarang --- diff --git a/_posts/2018-10-27-logs-for-the-Community-meeting-held-on-2018-10-27.md b/_posts/2018-10-27-logs-for-the-Community-meeting-held-on-2018-10-27.md index 4212c44e..98f4df8e 100644 --- a/_posts/2018-10-27-logs-for-the-Community-meeting-held-on-2018-10-27.md +++ b/_posts/2018-10-27-logs-for-the-Community-meeting-held-on-2018-10-27.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2018-10-27 summary: Community highlights, Forum Funding System updates, Workgroup report, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: el00ruobuob / rehrar --- diff --git a/_posts/2018-10-29-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-10-29.md b/_posts/2018-10-29-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-10-29.md index b783f306..a9ac1e96 100644 --- a/_posts/2018-10-29-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-10-29.md +++ b/_posts/2018-10-29-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-10-29.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-10-29 summary: Surae work, Sarang work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / sarang --- diff --git a/_posts/2018-11-05-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-11-05.md b/_posts/2018-11-05-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-11-05.md index 1295bc36..a13b47f8 100644 --- a/_posts/2018-11-05-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-11-05.md +++ b/_posts/2018-11-05-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-11-05.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-11-05 summary: Sarang work, Surae work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / sarang --- diff --git a/_posts/2018-11-10-logs-for-the-Community-meeting-held-on-2018-11-10.md b/_posts/2018-11-10-logs-for-the-Community-meeting-held-on-2018-11-10.md index 1d819b95..faa2a1c0 100644 --- a/_posts/2018-11-10-logs-for-the-Community-meeting-held-on-2018-11-10.md +++ b/_posts/2018-11-10-logs-for-the-Community-meeting-held-on-2018-11-10.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2018-11-10 summary: Community highlights, Forum Funding System updates, Workgroup report, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: el00ruobuob / SamsungGalaxyPlayer --- diff --git a/_posts/2018-11-12-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-11-12.md b/_posts/2018-11-12-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-11-12.md index 851dcb92..32f6b197 100644 --- a/_posts/2018-11-12-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-11-12.md +++ b/_posts/2018-11-12-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-11-12.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-11-12 summary: Sarang work, Surae work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / surae --- diff --git a/_posts/2018-11-19-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-11-19.md b/_posts/2018-11-19-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-11-19.md index 8288083f..92c71742 100644 --- a/_posts/2018-11-19-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-11-19.md +++ b/_posts/2018-11-19-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-11-19.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-11-19 summary: Surae work, Sarang work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / surae --- diff --git a/_posts/2018-11-26-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-11-26.md b/_posts/2018-11-26-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-11-26.md index fe116560..e64e88a5 100644 --- a/_posts/2018-11-26-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-11-26.md +++ b/_posts/2018-11-26-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-11-26.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-11-26 summary: Sarang work, Surae work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / surae --- diff --git a/_posts/2018-12-03-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-12-03.md b/_posts/2018-12-03-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-12-03.md index 0e0dd0e9..450e6323 100644 --- a/_posts/2018-12-03-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-12-03.md +++ b/_posts/2018-12-03-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-12-03.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-12-03 summary: Surae work, Sarang work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / sarang --- diff --git a/_posts/2018-12-08-logs-for-the-Community-meeting-held-on-2018-12-08.md b/_posts/2018-12-08-logs-for-the-Community-meeting-held-on-2018-12-08.md index e6dc24fa..bb8854b9 100644 --- a/_posts/2018-12-08-logs-for-the-Community-meeting-held-on-2018-12-08.md +++ b/_posts/2018-12-08-logs-for-the-Community-meeting-held-on-2018-12-08.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2018-12-08 summary: Community highlights, Forum Funding System updates, Workgroup report, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: el00ruobuob / SamsungGalaxyPlayer --- diff --git a/_posts/2018-12-10-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-12-10.md b/_posts/2018-12-10-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-12-10.md index 889f0407..10f75dbb 100644 --- a/_posts/2018-12-10-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-12-10.md +++ b/_posts/2018-12-10-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-12-10.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-12-10 summary: Sarang work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / sarang --- diff --git a/_posts/2018-12-17-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-12-17.md b/_posts/2018-12-17-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-12-17.md index f72a85d9..bd0c1505 100644 --- a/_posts/2018-12-17-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-12-17.md +++ b/_posts/2018-12-17-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-12-17.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-12-17 summary: Sarang work, Surae work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / surae --- diff --git a/_posts/2018-12-31-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-12-31.md b/_posts/2018-12-31-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-12-31.md index 9ee6330b..95f3892d 100644 --- a/_posts/2018-12-31-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-12-31.md +++ b/_posts/2018-12-31-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-12-31.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2018-12-31 summary: Sarang work, Surae work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / surae --- diff --git a/_posts/2019-01-05-logs-for-the-Community-meeting-held-on-2019-01-05.md b/_posts/2019-01-05-logs-for-the-Community-meeting-held-on-2019-01-05.md index eceb5aa1..6ad3b7d3 100644 --- a/_posts/2019-01-05-logs-for-the-Community-meeting-held-on-2019-01-05.md +++ b/_posts/2019-01-05-logs-for-the-Community-meeting-held-on-2019-01-05.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2019-01-05 summary: Community highlights, Forum Funding System updates, Workgroup report, Kovri discussion, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: el00ruobuob / SamsungGalaxyPlayer --- diff --git a/_posts/2019-01-07-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-01-07.md b/_posts/2019-01-07-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-01-07.md index 1b72cd49..063aa6b8 100644 --- a/_posts/2019-01-07-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-01-07.md +++ b/_posts/2019-01-07-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-01-07.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2019-01-07 summary: Sarang work, Surae work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / surae --- diff --git a/_posts/2019-01-14-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-01-14.md b/_posts/2019-01-14-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-01-14.md index 1f4bc8db..130cb27c 100644 --- a/_posts/2019-01-14-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-01-14.md +++ b/_posts/2019-01-14-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-01-14.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2019-01-14 summary: Upgrade items, Research, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / sarang --- diff --git a/_posts/2019-01-19-logs-for-the-Community-meeting-held-on-2019-01-19.md b/_posts/2019-01-19-logs-for-the-Community-meeting-held-on-2019-01-19.md index f78727e0..ad613dc7 100644 --- a/_posts/2019-01-19-logs-for-the-Community-meeting-held-on-2019-01-19.md +++ b/_posts/2019-01-19-logs-for-the-Community-meeting-held-on-2019-01-19.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2019-01-19 summary: Community highlights, Forum Funding System updates, Event topics, Hardware topics, Surveys, Workgroup report, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: el00ruobuob / SamsungGalaxyPlayer --- diff --git a/_posts/2019-01-21-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-01-21.md b/_posts/2019-01-21-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-01-21.md index 09ec3c9e..dc0b1655 100644 --- a/_posts/2019-01-21-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-01-21.md +++ b/_posts/2019-01-21-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-01-21.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2019-01-21 summary: Ongoing work, New work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / surae --- diff --git a/_posts/2019-01-28-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-01-28.md b/_posts/2019-01-28-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-01-28.md index c6603613..7fb3cd0e 100644 --- a/_posts/2019-01-28-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-01-28.md +++ b/_posts/2019-01-28-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-01-28.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2019-01-28 summary: Ongoing work, MRL going to SBC, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / surae --- diff --git a/_posts/2019-02-02-logs-for-the-Community-meeting-held-on-2019-02-02.md b/_posts/2019-02-02-logs-for-the-Community-meeting-held-on-2019-02-02.md index 06eace86..0f145b61 100644 --- a/_posts/2019-02-02-logs-for-the-Community-meeting-held-on-2019-02-02.md +++ b/_posts/2019-02-02-logs-for-the-Community-meeting-held-on-2019-02-02.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2019-02-02 summary: Community highlights, Forum Funding System updates, Workgroup report, and Code of Conduct discussion -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: el00ruobuob / rehrar --- diff --git a/_posts/2019-02-04-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-02-04.md b/_posts/2019-02-04-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-02-04.md index acf251e7..840028dc 100644 --- a/_posts/2019-02-04-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-02-04.md +++ b/_posts/2019-02-04-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-02-04.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2019-02-04 summary: Network upgrade, MRL work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / sarang --- diff --git a/_posts/2019-02-11-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-02-11.md b/_posts/2019-02-11-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-02-11.md index 6482fb20..3430bfe3 100644 --- a/_posts/2019-02-11-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-02-11.md +++ b/_posts/2019-02-11-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-02-11.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2019-02-11 summary: Network upgrade, MRL work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / sarang --- diff --git a/_posts/2019-02-16-logs-for-the-Community-meeting-held-on-2019-02-16.md b/_posts/2019-02-16-logs-for-the-Community-meeting-held-on-2019-02-16.md index d852be17..c8e72ff4 100644 --- a/_posts/2019-02-16-logs-for-the-Community-meeting-held-on-2019-02-16.md +++ b/_posts/2019-02-16-logs-for-the-Community-meeting-held-on-2019-02-16.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2019-02-16 summary: Community highlights, Forum Funding System updates, Workgroup report, Network Upgrade, and RamdomX PoW discussion -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: el00ruobuob / SamsungGalaxyPlayer --- diff --git a/_posts/2019-02-25-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-02-25.md b/_posts/2019-02-25-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-02-25.md index c74e8294..04238241 100644 --- a/_posts/2019-02-25-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-02-25.md +++ b/_posts/2019-02-25-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-02-25.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2019-02-25 summary: Output Selection, MRL work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / sarang --- diff --git a/_posts/2019-03-02-logs-for-the-Community-meeting-held-on-2019-03-02.md b/_posts/2019-03-02-logs-for-the-Community-meeting-held-on-2019-03-02.md index 107981f1..758f70ac 100644 --- a/_posts/2019-03-02-logs-for-the-Community-meeting-held-on-2019-03-02.md +++ b/_posts/2019-03-02-logs-for-the-Community-meeting-held-on-2019-03-02.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2019-03-02 summary: Community highlights, CCS / FFS updates, Workgroup report, Network Upgrade, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: el00ruobuob / SamsungGalaxyPlayer --- diff --git a/_posts/2019-03-04-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-03-04.md b/_posts/2019-03-04-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-03-04.md index 02f5624b..3e6bb4d3 100644 --- a/_posts/2019-03-04-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-03-04.md +++ b/_posts/2019-03-04-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-03-04.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2019-03-04 summary: Sarang work, Surae work, SamsungGalaxyPlayer proposal and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / sarang --- diff --git a/_posts/2019-03-11-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-03-11.md b/_posts/2019-03-11-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-03-11.md index 8c619d0e..9844248a 100644 --- a/_posts/2019-03-11-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-03-11.md +++ b/_posts/2019-03-11-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-03-11.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2019-03-11 summary: Network upgrade, Point release discussions, MRL work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / sarang --- diff --git a/_posts/2019-03-16-logs-for-the-Community-meeting-held-on-2019-03-16.md b/_posts/2019-03-16-logs-for-the-Community-meeting-held-on-2019-03-16.md index b508b74a..ba333642 100644 --- a/_posts/2019-03-16-logs-for-the-Community-meeting-held-on-2019-03-16.md +++ b/_posts/2019-03-16-logs-for-the-Community-meeting-held-on-2019-03-16.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2019-03-16 summary: Community highlights, CCS / FFS updates, Workgroup report, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: el00ruobuob / SamsungGalaxyPlayer --- diff --git a/_posts/2019-03-18-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-03-18.md b/_posts/2019-03-18-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-03-18.md index e0f00a16..9afcf6a3 100644 --- a/_posts/2019-03-18-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-03-18.md +++ b/_posts/2019-03-18-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-03-18.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2019-03-18 summary: Sarang work, Surae work, Output distribution and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / sarang --- diff --git a/_posts/2019-03-25-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-03-25.md b/_posts/2019-03-25-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-03-25.md index 8e77a925..259a726e 100644 --- a/_posts/2019-03-25-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-03-25.md +++ b/_posts/2019-03-25-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-03-25.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2019-03-25 summary: Surae work, Sarang work, Output distribution and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / sarang --- diff --git a/_posts/2019-03-30-logs-for-the-Community-meeting-held-on-2019-03-30.md b/_posts/2019-03-30-logs-for-the-Community-meeting-held-on-2019-03-30.md index 71e17501..d11ec370 100644 --- a/_posts/2019-03-30-logs-for-the-Community-meeting-held-on-2019-03-30.md +++ b/_posts/2019-03-30-logs-for-the-Community-meeting-held-on-2019-03-30.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2019-03-30 summary: Community highlights, CCS updates, Workgroup report, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: el00ruobuob / SamsungGalaxyPlayer --- diff --git a/_posts/2019-04-01-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-04-01.md b/_posts/2019-04-01-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-04-01.md index 3defba09..19158679 100644 --- a/_posts/2019-04-01-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-04-01.md +++ b/_posts/2019-04-01-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-04-01.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2019-04-01 summary: Sarang work, Surae work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / sarang --- diff --git a/_posts/2019-04-08-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-04-08.md b/_posts/2019-04-08-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-04-08.md index 6889dca3..53cfa7b2 100644 --- a/_posts/2019-04-08-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-04-08.md +++ b/_posts/2019-04-08-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-04-08.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2019-04-08 summary: Sarang work, Surae work, Output distribution and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / sarang --- diff --git a/_posts/2019-04-13-logs-for-the-Community-meeting-held-on-2019-04-13.md b/_posts/2019-04-13-logs-for-the-Community-meeting-held-on-2019-04-13.md index de50daa6..5d9e0b84 100644 --- a/_posts/2019-04-13-logs-for-the-Community-meeting-held-on-2019-04-13.md +++ b/_posts/2019-04-13-logs-for-the-Community-meeting-held-on-2019-04-13.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2019-04-13 summary: Community highlights, CCS / FFS updates, Workgroup report, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: el00ruobuob / SamsungGalaxyPlayer --- diff --git a/_posts/2019-04-15-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-04-15.md b/_posts/2019-04-15-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-04-15.md index c0a8ebf9..d5248244 100644 --- a/_posts/2019-04-15-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-04-15.md +++ b/_posts/2019-04-15-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-04-15.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2019-04-15 summary: Surae work, Sarang work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / sarang --- diff --git a/_posts/2019-04-22-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-04-22.md b/_posts/2019-04-22-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-04-22.md index b2c01636..84f38b41 100644 --- a/_posts/2019-04-22-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-04-22.md +++ b/_posts/2019-04-22-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-04-22.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2019-04-22 summary: Sarang work, Surae work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / sarang --- diff --git a/_posts/2019-04-27-logs-for-the-Community-meeting-held-on-2019-04-27.md b/_posts/2019-04-27-logs-for-the-Community-meeting-held-on-2019-04-27.md index f8dbea37..959e4aef 100644 --- a/_posts/2019-04-27-logs-for-the-Community-meeting-held-on-2019-04-27.md +++ b/_posts/2019-04-27-logs-for-the-Community-meeting-held-on-2019-04-27.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2019-04-27 summary: Community highlights, CCS / FFS updates, Workgroup report, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: el00ruobuob / SamsungGalaxyPlayer --- diff --git a/_posts/2019-04-29-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-04-29.md b/_posts/2019-04-29-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-04-29.md index 884431c7..bd4e9d36 100644 --- a/_posts/2019-04-29-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-04-29.md +++ b/_posts/2019-04-29-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-04-29.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2019-04-29 summary: Sarang work, Surae work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / sarang --- diff --git a/_posts/2019-05-04-logs-for-the-localization-workgroup-meeting-held-on-2019-05-03.md b/_posts/2019-05-04-logs-for-the-localization-workgroup-meeting-held-on-2019-05-03.md index 36b30d14..d7f58e1e 100644 --- a/_posts/2019-05-04-logs-for-the-localization-workgroup-meeting-held-on-2019-05-03.md +++ b/_posts/2019-05-04-logs-for-the-localization-workgroup-meeting-held-on-2019-05-03.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Localization Workgroup meeting held on 2018-05-03 summary: Translation's workflow improvements and future of Pootle -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: erciccione --- diff --git a/_posts/2019-05-06-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-05-06.md b/_posts/2019-05-06-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-05-06.md index c1358744..23fb3414 100644 --- a/_posts/2019-05-06-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-05-06.md +++ b/_posts/2019-05-06-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-05-06.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2019-05-06 summary: Sarang work, Surae work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / sarang --- diff --git a/_posts/2019-05-11-logs-for-the-Community-meeting-held-on-2019-05-11.md b/_posts/2019-05-11-logs-for-the-Community-meeting-held-on-2019-05-11.md index c714ef17..a1b6bd3e 100644 --- a/_posts/2019-05-11-logs-for-the-Community-meeting-held-on-2019-05-11.md +++ b/_posts/2019-05-11-logs-for-the-Community-meeting-held-on-2019-05-11.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2019-05-11 summary: Community highlights, CCS updates, Workgroup report, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: el00ruobuob / SamsungGalaxyPlayer --- diff --git a/_posts/2019-05-14-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-05-14.md b/_posts/2019-05-14-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-05-14.md index d61da55d..c5657abf 100644 --- a/_posts/2019-05-14-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-05-14.md +++ b/_posts/2019-05-14-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-05-14.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2019-05-14 summary: Surae work, Sarang work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / sarang --- diff --git a/_posts/2019-05-20-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-05-20.md b/_posts/2019-05-20-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-05-20.md index 3a61efcd..b0178528 100644 --- a/_posts/2019-05-20-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-05-20.md +++ b/_posts/2019-05-20-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-05-20.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2019-05-20 summary: Sarang work, Surae work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / suraeNoether --- diff --git a/_posts/2019-05-25-logs-for-the-Community-meeting-held-on-2019-05-25.md b/_posts/2019-05-25-logs-for-the-Community-meeting-held-on-2019-05-25.md index 3f898aac..9bb39e6a 100644 --- a/_posts/2019-05-25-logs-for-the-Community-meeting-held-on-2019-05-25.md +++ b/_posts/2019-05-25-logs-for-the-Community-meeting-held-on-2019-05-25.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2019-05-25 summary: Community highlights, CCS updates, Workgroup report, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: el00ruobuob / rehrar --- diff --git a/_posts/2019-05-27-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-05-27.md b/_posts/2019-05-27-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-05-27.md index 8b599522..f30aa5d3 100644 --- a/_posts/2019-05-27-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-05-27.md +++ b/_posts/2019-05-27-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-05-27.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2019-05-27 summary: Surae work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / suraeNoether --- diff --git a/_posts/2019-06-03-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-06-03.md b/_posts/2019-06-03-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-06-03.md index efd5a04f..c0f61c1d 100644 --- a/_posts/2019-06-03-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-06-03.md +++ b/_posts/2019-06-03-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-06-03.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2019-06-03 summary: Sarang work, Surae work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / sarang --- diff --git a/_posts/2019-06-08-logs-for-the-Community-meeting-held-on-2019-06-08.md b/_posts/2019-06-08-logs-for-the-Community-meeting-held-on-2019-06-08.md index b2c2b847..13cba49a 100644 --- a/_posts/2019-06-08-logs-for-the-Community-meeting-held-on-2019-06-08.md +++ b/_posts/2019-06-08-logs-for-the-Community-meeting-held-on-2019-06-08.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2019-06-08 summary: CCS updates, Workgroup report, RandomX fund leftover, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: el00ruobuob / rehrar --- diff --git a/_posts/2019-06-10-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-06-10.md b/_posts/2019-06-10-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-06-10.md index 74e3bc58..35fcb68c 100644 --- a/_posts/2019-06-10-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-06-10.md +++ b/_posts/2019-06-10-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-06-10.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2019-06-10 summary: Surae work, Sarang work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / sarang --- diff --git a/_posts/2019-06-17-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-06-17.md b/_posts/2019-06-17-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-06-17.md index d6791b3d..36603bcd 100644 --- a/_posts/2019-06-17-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-06-17.md +++ b/_posts/2019-06-17-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-06-17.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2019-06-17 summary: Surae work, Sarang work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / sarang --- diff --git a/_posts/2019-07-01-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-07-01.md b/_posts/2019-07-01-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-07-01.md index b1f883f4..3d290453 100644 --- a/_posts/2019-07-01-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-07-01.md +++ b/_posts/2019-07-01-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-07-01.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2019-07-01 summary: Surae work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / suraeNoether --- diff --git a/_posts/2019-07-06-logs-for-the-Community-meeting-held-on-2019-07-06.md b/_posts/2019-07-06-logs-for-the-Community-meeting-held-on-2019-07-06.md index 100a7a53..b853ed55 100644 --- a/_posts/2019-07-06-logs-for-the-Community-meeting-held-on-2019-07-06.md +++ b/_posts/2019-07-06-logs-for-the-Community-meeting-held-on-2019-07-06.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2019-07-06 summary: Community highlights, CCS updates, Monero Konferenco recap, Workgroup report, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: el00ruobuob / rehrar --- diff --git a/_posts/2019-07-08-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-07-08.md b/_posts/2019-07-08-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-07-08.md index d77e3a99..4301a890 100644 --- a/_posts/2019-07-08-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-07-08.md +++ b/_posts/2019-07-08-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-07-08.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2019-07-08 summary: Surae work, Sarang work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / sarang --- diff --git a/_posts/2019-07-15-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-07-15.md b/_posts/2019-07-15-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-07-15.md index 4fcfa6ef..10ee2428 100644 --- a/_posts/2019-07-15-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-07-15.md +++ b/_posts/2019-07-15-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-07-15.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2019-07-15 summary: Surae work, Sarang work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / sarang --- diff --git a/_posts/2019-07-20-logs-for-the-Community-meeting-held-on-2019-07-20.md b/_posts/2019-07-20-logs-for-the-Community-meeting-held-on-2019-07-20.md index 2b289a46..8054decc 100644 --- a/_posts/2019-07-20-logs-for-the-Community-meeting-held-on-2019-07-20.md +++ b/_posts/2019-07-20-logs-for-the-Community-meeting-held-on-2019-07-20.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2019-07-20 summary: Community highlights, CCS updates, Workgroup report, and miscellaneous -tags: [community, crypto] +tags: [dev diaries, community, crypto] author: el00ruobuob / rehrar --- diff --git a/_posts/2019-07-22-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-07-22.md b/_posts/2019-07-22-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-07-22.md index ec412279..4c810b7c 100644 --- a/_posts/2019-07-22-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-07-22.md +++ b/_posts/2019-07-22-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-07-22.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2019-07-22 summary: Surae work, Sarang work, and miscellaneous -tags: [community, crypto, research] +tags: [dev diaries, community, crypto, research] author: el00ruobuob / sarang --- diff --git a/_posts/2019-07-29-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-07-29.md b/_posts/2019-07-29-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-07-29.md new file mode 100644 index 00000000..46c08909 --- /dev/null +++ b/_posts/2019-07-29-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-07-29.md @@ -0,0 +1,142 @@ +--- +layout: post +title: Logs for the Monero Research Lab Meeting Held on 2019-07-29 +summary: Sarang work, Surae work, and miscellaneous +tags: [dev diaries, community, crypto, research] +author: el00ruobuob / sarang +--- + +# Logs + +**\** OK, let's begin +**\** Hello all +**\** Logs of this meeting will be posted to the GitHub agenda issue afterward +**\** GREETINGS +**\** greetings! +**\** hey +**\** Whoops, here is the current agenda: https://github.com/monero-project/meta/issues/377 +**\** Let's go ahead with ROUNDTABLE +**\** I've been working hard on an RCT3 implementation, integrating some nice optimizations and seeing if it's possible to get key images working as expected +**\** This also led to a bunch of other library updates that the code relies on +**\** So generally just a lot of coding +**\** I also gave a fun lecture on the Enigma cipher machine and the math behind it, which is always fun ;) +**\** nice, what was that for? a meetup or something? +**\** A friend teaches at a university and thought it would be good for an undergrad crypto class +**\** Since the Enigma break is all about permutation groups +**\** nice +**\** I should be able to finish up an integration of the BP inner product verifier optimization into RCT3 shortly +**\** Then, of course, DEF CON approaches! +**\** neat +**\** i have a very dirty branch on my computer with my matching simulations and experiments being worked upon +**\** How are those going? +**\** defcon - anyone got grasshopper repellent? +**\** -\_\_\_\_- +**\** i've proven all the theorems necessary to prove that the algorithm in graphtheory.py does what i claim it does, and i'm currently testing that my simulated ledgers are doing what i expect. +**\** noice +**\** Will be very neat to see the results, and to see if/how they can work with the analysis that Isthmus et al. are doing on Monero and Zcash +**\** in addition to that, i have a bunch of MAGIC stuff I need to get done, and my discussions with isthmus' digital forensics work are leaning in that direction +**\** i'm thinking the content of this project may take up more than two papers :\\ +**\** Cool! +**\** Also worth noting that the CLSAG paper has been updated on IACR, thanks mainly to kenshamir[m]'s comments and questions +**\** kenshamir[m] has also been working on a Rust implementation of CLSAG/MLSAG using the dalek library +**\** hyc: i hear grasshoppers are delicious, i wonder if any of those fancy vegas michelin star restaurants are capitalizing on the swarm +**\** Anything you'd like to share on that, kenshamir[m] ? +**\** Hi, the library is finished, not interopable with monero because it uses a different curve though. The numbers are quite impressive and I believe it is due to the way cLSAG was created +**\** aw shucks +**\** Will be great to see your MLSAG vs CLSAG numbers at different ring sizes +**\** i believe there was a question re: ristretto and multi-exp like pippenger right before the meeting that would be relevant here? +**\** I brought it up a while back because we handle different linear combination sizes \_very\_ differently in the codebase +**\** is that rust code in a public repo? +**\** We use no fewer than 4 methods +**\** The numbers above were for different ring sizes, I may have mis-typed key sizes by accident +**\** 256 and 512 were for the decoy sizes; if I was not clear +**\** A big part of the reason CLSAG verification is faster than MLSAG is because of the introduction of a new linear combination evaluation algorithm +**\** kenshamir[m]: can you link them again for the logs? +**\** (if comfortable having them public) +**\** \ Not the cLSAG code, once I add documentation and sanitise it I can post it in here +**\** ty +**\** \ Yep sure +**\** :) +**\** What does "without Pippenger/Straus" mean? Simple iterative evaluation of linear combinations? +**\** Yep exactly +**\** Impressive numbers +**\** Of course, it's a different hash function +**\** I just did scalarbase mult in a for loop +**\** haha yeah that too +**\** hmmmmm +**\** But if the hash function is the same across both of your CLSAG/MLSAG, then the relative numbers are good +**\** something that is both faster and smaller and with equivalent security is a no-brainer for implementation (pending audits) +**\** Speaking of this, still in contact with potential auditors, who are moving very slowly +**\** Nothing to report on that front :/ +**\** the improved space allows for a logarithmic increase in verification time without actually slowing down the network (at least when it comes to new nodes downloading the network). judging by these numbers, a ring size of 16 or 32 is no longer like pouring molasses or concrete onto the network +**\** OK, any other interesting research to report? +**\** re: audits, or roll-out in general. Is this the kind of thing that could be rolled-out in parallel with existing? i.e., have an overlap, where the network uses the existing as the primary / default, but can optionally use the new thing, and then once new thuing is vetted, just prune the old? +**\** ^ slow auditors - a lot of people are on summer holiday now +**\** or, switch to the new and no longer have to relay / verify the old style during the overlap? +**\** sarang: am i wrong in saying that gingeropolous is correct that clsag could be implemented in parallel before mlsag is deprecated? +**\** we had a 24hr overlap in the last hardfork for this sort of thing +**\** this would be kinda different. +**\** I suppose it could be overlapping, provided the fee model supports it properly +**\** I don't really see why this would be useful +**\** i dunno. i'm just opening the conversation regarding the model that all new things need to be audited +**\** i mean, obvi auditing is great +**\** yes +**\** but its not perfect +**\** hyc: Yeah in general, summer constitutes low activity +**\** It's good for inspiring confidence, as well as the obvious benefits of catching any errors +**\** Can Monero benefit from using bulletproofs for arithmetic circuits? +**\** gingeropolous: Didn't we discuss that kind of model for Bulletproofs or RingCT too? +**\** Likely not, with our current tx model +**\** yeah dEBRUYNE +**\** The scaling isn't great +**\** I think it was shot down for good reasons, but I cannot remember them exactly :-P +**\** i think that was post audit though +**\** and we have hash functions, which screw things up +**\** Zooko had a slide in some presentation where his team estimated the verification time for a circuit with the complexity of Sapling (Sprout? don't recall) +**\** and BP verification was O(1 s) +**\** Compared to our current verification time which is probably 1/50th of that +**\** maybe 1/100th +**\** yikes +**\** kenshamir: if we designed an arithmetic circuit to describe a ring confidential transaction language, then yes, but that's sort of what RCT3 and omniring and lelantus try to do... sarang, i think zooko was showing "what it would look like for a Sapling transaction language to be proven in the bulletproof setting" not ring confidential transactions, so it's not clear to me whether it'd be slower. +**\** in our setting +**\** with the exception of our non-AC-compatible hash function +**\** sarang: That's verification time for fully shielded transactions? +**\** dEBRUYNE yeah, iirc +**\** Yikes +**\** Yeah, that timing was just to give an example of what a production-size tx circuit might look like +**\** Especially given that, as far as I know, you have to run a full node in order to properly perform fully shielded transactions +**\** Anyway, I digress :-P +**\** Anyway, suraeNoether is right in that RCT3 and Omniring try to bring the BP benefits to specific languages used to prove RingCT-type statements +**\** which is why we're interested in them +**\** yeah, bulletproofs for use in SNARK-style languages is like... uhm... putting a large-diameter turbofan engine into a Mini Cooper. It's not going to do what you think it's going to do. +**\** BPs can be much more efficient for languages built for it +**\** which is why range proofs are so efficient +**\** haha +**\** indeed +**\** moving along +**\** heh +**\** ok, other research? +**\** Or QUESTIONS, from the agenda? +**\** OK then! To ACTION ITEMS +**\** I'll be finalizing some things for my DEF CON talk, workshop, and panel; and finalizing some RCT3 integration optimizations +**\** suraeNoether: ? +**\** oh gosh sorry +**\** i was computing a number sorry about that. :P +**\** it's 7 +**\** my action items are: work on sims and the experimenter, and work with isthmus to formalize statistical hypotheses for testing all this +**\** Having data from Isthmus's group will be extremely valuable for this kind of analysis +**\** actually the number is O(153.58\*N), which is the number of bits used to describe the number of possible spend histories at ring size 32 with N outputs. +**\** which is nutters +**\** This is all assuming no external information? +**\** Or other graph-based information on chain reactions and provably-spent outputs? +**\** merely the total number of self-consistent spend histories +**\** Ah ok, so for a hypothetical graph +**\** yeah +**\** got it +**\** O(153.58\*N) ... great. now your math is talking in math +**\** well it means that for, say, 1000 transactions at ring size 32, there are 2^(153,580) possible spend histories. +**\** anyway +**\** (N has to be a lot bigger than the ring size for the above formula to hold btw) +**\** which is... quite reasonable +**\** Any other final thoughts or questions before we adjourn? +**\** OK then! Thanks to everyone for participating. We are adjourned diff --git a/_posts/2019-08-03-logs-for-the-Community-meeting-held-on-2019-08-03.md b/_posts/2019-08-03-logs-for-the-Community-meeting-held-on-2019-08-03.md new file mode 100644 index 00000000..4f14b73a --- /dev/null +++ b/_posts/2019-08-03-logs-for-the-Community-meeting-held-on-2019-08-03.md @@ -0,0 +1,236 @@ +--- +layout: post +title: Logs for the Community Meeting Held on 2019-08-03 +summary: Community highlights, CCS updates, Workgroup report, and miscellaneous +tags: [dev diaries, community, crypto] +author: el00ruobuob / SamsungGalaxyPlayer +--- + +# Logs + + +**\** meeting time +**\** 0. Introduction +**\** We would like to welcome everyone to this Monero Community Workgroup Meeting! +**\** Hi! +**\** Hello people +**\** Link to agenda on GitHub: https://github.com/monero-project/meta/issues/380 +**\** Monero Community meetings are a discussion place for anything going on in the Monero Community, including other Monero workgroups. We use meetings to encourage the community to share ideas and provide support. +**\** 1. Greetings +**\** Hello +**\** Hi :) +**\** Hello everyone +**\** Hey everyone +**\** welcome everyone +**\** ahoy +**\** Ahoy hoy +**\** |o/ +**\** I'm reporting live from a world-famous beach in Wisconsin. Just kidding, it's not world-famous. But I am at a beach +**\** Thanks +**\** 2. Community highlights +**\** See Monero weekly highlights at https://revuo-monero.com/ +**\** o\_0 +**\** There was a Coffee Chat led by rehrar last week: https://www.youtube.com/watch?v=1S5UotVgku8 +**\** [ Monero Coffee Chat - 2019.07.27 - YouTube ] - www.youtube.com +**\** Ecosystem related: I’m hosting a Zcash community conversation on the future of the block reward Sunday (tomorrow): https://forum.zcashcommunity.com/t/livestream-discussion-future-of-zcash-block-reward/34247 +**\** Does anyone else have community (non-workgroup) updates to share? +**\** I was impressed by XMR.RU's report +**\** Kinda, what are the sections again? +**\** yes, they do a lot of great work +**\** I want to talk in the right place +**\** needmonero90: https://github.com/monero-project/meta/issues/380 +**\** if you're unsure, we should have plenty of time in open ideas +**\** Ah this works actually. +**\** We have a problem. +**\** Konferenco funding. +**\** There was a shortfall, and one of our beloved PhD researchers (sarang) is now footing the $30-40k bill. +**\** Taking it extremely well, might I add +**\** I don't think that this is an appropriate state for things to be in, and I would like to propose a second CCS be created for the community to cover the shortfall +**\** I will of course be putting my money where my mouth is and contributing a chunk, it sets a really bad standard if the organizer is on the hook for overages in costs at the event. +**\** What caused this? +**\** I imagine that would be a massive sticking point to attracting talent to the position in the future, it's a huge risk +**\** Price fluctuations and unforseen konferenco costs (which admittedly sarang was not entirely unresponsible for) +**\** OsrsNeedsF2P: the market tanked after the funds were raised +**\** and before they were converted to $ +**\** I told sarang that I was appalled that he expected to be on the hook for the costs, and that I would bring it up at the next community meeting +**\** So here I am +**\** that's a chunk of change +**\** Yes. +**\** needmonero90: sarang or surae? +**\** One of them +**\** Whoever organized +**\** May have been surae +**\** I believe it is surae +**\** Lemme check +**\** needmonero90: did you read the full funding report? Probably good to talk to scooby about the accounting specifics too +**\** My bad it was suraeNoether +**\** I didn't yet, I just thought it would be appropriate to broach the subject here +**\** Because $40k is significant +**\ \** It should be noted that he would only be like 4k on the hole if the market had shifted so drastically. +**\** needmonero90: if you want to champion this, I recommend talking to scooby so you have a full picture of the finances +**\ \** Market shift accounts for literally like 85% of his loss. So not "bad planning" or anything. +**\** I can do that, sure. +**\** Thanks for bringing it up, I wasn't quite sure the best way to mention it. I've been thinking of some possible fundraising ideas though. I'm willing to volunteer for the effort. +**\** apart from trying to recover the funds, is this something that can be avoided in the future? 1) Allow for dynamic/moving CSS targets 2) release funds ASAP +**\** we can also consider other options, including some allocation for the next Konferenco CCS that will inevitably happen. There are a few possible reimbursement options +**\** You can't force a conference to be funded if people aren't interested in it. +**\** dsc\_: yes, immediate release needs to happen for trusted entities in the future +**\** Ayeoo +**\** The conference should appeal to the needs of the fundees after all. +**\** needmonero90: is there anything you specially wanted to have answered, or are you feeling for support? +**\** I just wanted to make this a topic of discussion and explain where I think things stand +**\** I'm minorly advocating a new CCS for the shortfall, but I'm not too particular about where we go with it +**\** Just wanted the subject up for discussion +**\ \** If we're being real, that conference will be the highlight of Monero's year, just in quality. Talks freely available on YouTube as a resource for years to come. +**\** All right, please keep going with the initiative and let us know how it goes. Might be best to open a Reddit discussion too +**\** yes, the recordings are very valuable +**\** I will keep going with the meeting, but we can cover this topic again during open ideas if people have other comments +**\** thanks for introducing the idea needmonero90 +**\** Any other non-workgroup updates to share? +**\** Maybe a focus on those types of deliverables should be emphasised? +**\** 3. CCS updates +**\** CCS proposals in ideas to be discussed: +**\** I suggest to ciber this shortfall with a CCS for it, but start on planning and funding earlier for future events (konferenco, defcon, etc.) Be better prepared for this type of things. Have a bigger budget. +**\** “Telegram bot for Monero-Jobs group” (3 XMR) https://repo.getmonero.org/monero-project/ccs-proposals/merge\_requests/91 +**\** Ciber \*cover +**\** Does anyone have comments on this proposal? +**\** looks good to me +**\** Generally speaking I'm strict with proposals I support, but this definitely has mine +**\** 3 XMR looks reasonable +**\** 3 XMR is too reasonable +**\** lol +**\** Yeah +**\** +**\** me too +**\** It's like, ramen budget living at your parent's house low +**\** ENDOGEN was not able to make it. I'm part of the Monero jobs chat room. Alteady gave my comments, would like to hear from the community. +**\** I wish more proposals were like this. He's really outlined the benefits of this +**\** It's a very good deal, if the code works as advertised. +**\** Any final comments on this proposal? People seem comfortable with it +**\** >Something like "What would you like to do?" and then there would be three buttons that the user could press: "Request Work", "Offer Work" and "Create Proposal" +**\** We need this for IRC and Reddit too. I know the outreach team wanted to do something like this +**\** This is super useful +**\** “A Monero Tip Bot for Telegram” (13 XMR) https://repo.getmonero.org/monero-project/ccs-proposals/merge\_requests/86 +**\** The 3XMR was what he estimated for his work. He's actually really enthusiastic about it. We will have to see how he delivers of course. +**\** We discussed this similar proposal last week, but I wanted a last call for comments +**\** \*last meeting +**\** I honestly feel kind of bad for that 3XMR maybe we should advise him to double it +**\** OsrsNeedsF2P the bot will be open source so I guess we all would benefit :). +**\** I'd be happy to fund that extra 3.. +**\** I provided my insights on that thread, but I still think the Telegram tip bot is asking for too much +**\** It's definitely a good initiative though. +**\** OsrsNeedsF2P: what # or range would you feel comfortable with? +**\** Well here's the thing; it's a custodial service that really will just be running one wallet and a very simple file tracking everyone's balance. +**\** That feels like something that should be done open source and maintained by core +**\** Like, the servers +**\** That's the intention ^ +**\** luigi specified in the thread that he would feel comfortable moving it with an agreed-upon host +**\** Luigi said he's willing to move it forward if a suitable host is found +**\** Let's review his funding points +**\** Like idk, I'm not sure we need to pay for this one? I think repurposing osrs's bot would work fine +**\** We could maybe talk to endogen +**\** My bot is non-custodial, finding a host is much more difficult +**\** I like the tip bot. That sure will also help. +**\** Keeping wallet synced is a b\*\* +**\** I like the tip bot as well. I think getting it out no Telegram is worth it. But his funding points directly: +**\** >>Collect Feature Requests and Prototype the Telegram bot: 1 XMR +**\** Thoughts? +**\** tbf it's \<$100 +**\** Prototyping is an essential part of any project +**\ \** I think the hope was the core team would indeed host it. +**\ \** I can ask them what their thoughts are for doing that. +**\** Endogen suggested once he worked the monerojobs.bot and be.working he wil add a multisig wallet for it. +**\** If there's an integratable telegram tip bot though, that would be much easier +**\** Yep +**\** >Implement Features: 5 XMR +**\** OsrsNeedsF2P: you reminded me +**\** There is +**\** Briar patch has a SPICE token tipbot +**\** For spicy comments +**\** I can see if it's open source or whether they can share the code +**\** If we get the code, it cuts the work significantly. +**\** Honestly, you guys overestimate how hard it is to make a tip bot +**\** All the APIs already exist +**\** The only reason the Reddit Tip Bot took so long to perfect the UX was soley because I was keeping everyone's wallets separate. Knowing as little as I did (no RPC, hardly Python), that would have still been a 1 day job +**\ \** #makeitthenlol +**\** What would be a reasonable price OsrsNeedsF2P? Just give your thoughts. +**\** I think 5 XMR to implement it is reasonable. I don't think any of his other requests are; +**\** >>Intensive Testing of Bot on Stagenet Within one or more Monero Telegram groups / Bug Fixing: 4 XMR +**\** >>Maintenance and Support: 3 XMR (one time fee) +**\** The prototype is certainly worth 1 XMR if there is really a solid prototype goal he's following, but unlike Endogen's request for instance, it's not nearly as clear or laid out +**\** What does everyone else think? I'm no coder so for me is quite hard to know more. +**\** But if OsrsNeedsF2P says it is because he knows. Those are my thoughts. +**\** The only thing I can't really comment on is the bot would likely be written in Javascript, and I'm very poor at estimating the difficulties in that +**\** But that is within the Implement Features category +**\** I think OsrsNeedsF2P should be head of Python Monero robots +**\** as such I trust his authority on the matter +**\** I've heard javascript is terrible so I wouldn't like something written in javascript. But again, I'm no coder so is like...mmm +**\** To summarize, OsrsNeedsF2P feels the cost is about twice as much as it should be, and hosting still needs to be resolved. Overall, the benefits are generally understood as valuable +**\** Very valuable I might add; also, the condition Luigi set was already on the hosting. +**\** We could tell him that the community supports a 5XMR proposal and wait and see his response. +**\** Perhaps the course of action should be first to figure out hosting, and then try to negotiate slightly better rates. But in the absence of others willing to code, we may not have other rate options +**\** I would even donate if it was only 5 XMR. 5/6/7, depending on what he offers. +**\** OsrsNeedsF2P: please add your comments again after this meeting in the thread, along with anyone else who has an opinion +**\** Will do. +**\** Any final comments on this matter? +**\** Another reminder to Luigi/rehrar: please move the v1docq47 proposal, which was discussed in detail and received favorable feedback last meeting +**\** Final chance for CCS comments +**\** 4. Workgroup report +**\** a. Daemon/CLI workgroup +**\** moneromooo is taking a much-needed vacation +**\** progress is continuing with various networking features and tests +**\** rehrar: want to summarize the dev meeting from last week? +**\** I have to get off my train. Cannot provide GUI update other than: pony is building bins, I'm working on I2P-Zero still. +**\** thanks dsc +**\** I know I’m coming into this late. Talking bout hosting. What about using Tari .org +**\** Are we talking container deployments? +**\ \** Sorry. Got busy for a bit. +**\** now is a good time to ask if there are localization workgroup updates too, or else we can skip that section +**\** Do we have a pirate localization workgroup yet +**\ \** We talked about Gitlab/GitHub stuff and people have opinions. +**\** I will give a small summary from outreach +**\** needmonero90: there was for one old version at least iirc +**\ \** Did anything else of interest pop up? +**\** sure lh1008[m], we can do that for e) +**\ \** Not to my mind. But I may just be forgetting something +**\** rehrar thanks +**\** I can give an update for d) Defcon workgroup +**\** Please check https://monerovillage.org for the livestream links (will be posted soon) and schedule (posted now). We will unfortunately only learn around 9:30am MT on Friday whether the events will be livestreamed. It's dependent on Defcon staff, but we'll keep you updated +**\** e) Outreach workgroup +**\** sent a long message: \< https://matrix.org/\_matrix/media/v1/download/matrix.org/RRYzFHFhqHanRLjmjzmyNPQV > +**\** Copy of link contents: +**\** About transcriptions: +**\** - All Breaking Monero transcriptions done. +**\** - MoneroKon from 26/12 already finished. 7 merged and 5 in review process. +**\** https://github.com/monero-ecosystem/outreach-docs/tree/master/monero-outreach-docs/en/transcriptions +**\** https://taiga.getmonero.org/project/xmrhaelan-monero-public-relations/epic/198 +**\** thanks lh1008[m], anything else? we look forward to your help for Defcon +**\** Thank you sgp\_ +**\** 5. Open ideas time +**\** It’s open ideas time! Feel free to propose your ideas to this discussion group, and feel free to comment on others’ ideas. If you disagree with the idea, please reply with constructive criticism. Thank you! +**\** We have a good 8 minutes, don't be shy! +**\** That would be all. The rest of MoneroKon are in production. Every talk has a volunteer. +**\** Yes of course count with us +**\** So, I want to talk about skepticism Sunday. Specifically, people posting the same stuff repeatedly with no intention of following up or responding to replies +**\** ah, the "uncensored version of this thread" person +**\** To be more direct, yes +**\** That's not skepticism +**\** I have one. We should be better prepared for events and shortfalls. +**\** imo remove, easy decision for me +**\** Any objections? I can just blacklist the link from that thread specifically. +**\** Scalpel +**\** Have never been on sundays skepticism. I guess I will also participate on them. +**\** lh1008[m]: indeed, that has been an ongoing effort. MRL takes payment before working the three months to reduce volatility +**\** Yep I've seen those efforts too. +**\** Something else. We should support more those artisitc initiatives. Just take this into your pillow discussion >:). +**\** we also need official Monero Village and Monero Party hashtags +**\** #MoneroVillage #defcon27? #Monero #Defcon27? +**\** Thank you everyone. Have to finish reviews. Love you all. +**\** #MoneroVillage +**\** We're running out of time, but think about hashtags and comment here if you have good ideas. Of course this channel is always open for discussions after the meeting +**\** 6. Confirm next meeting date/time +**\** The next community meeting will be in 2 weeks on 17 August at 17:00 UTC. The next Coffee Chat will be on 24 August at 16 UTC. Thanks rehrar for handling the last one. +**\ \** Ye +**\** 7. Conclusion +**\ \** Question on those. +**\** That’s all! Thanks for attending this Monero Community meeting, and we hope to see you on r/MoneroCommunity and #monero-community. Take care, and know that change starts with YOU. diff --git a/_posts/2019-08-05-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-08-05.md b/_posts/2019-08-05-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-08-05.md new file mode 100644 index 00000000..e605695f --- /dev/null +++ b/_posts/2019-08-05-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-08-05.md @@ -0,0 +1,55 @@ +--- +layout: post +title: Logs for the Monero Research Lab Meeting Held on 2019-08-05 +summary: Sarang work, and miscellaneous +tags: [dev diaries, community, crypto, research] +author: el00ruobuob / sarang +--- + +# Logs + +**\** Let's go ahead and get started +**\** suraeNoether says he is unavailable at this time due to an appointment +**\** Agenda is here, where logs will be posted: https://github.com/monero-project/meta/issues/381 +**\** GREETINGS +**\** hello +**\** Seeing as it's a quiet day, I'll move right along to ROUNDTABLE +**\** I finished work on an efficient RCT3 verifier that takes advantage of Bulletproof-style inner product scaling +**\** and also added fee support, which the original paper didn't natively support +**\** As well as many other assorted code library updates that I'd been meaning to get to over time +**\** Finally, I've been preparing for my DEF CON talk and workshop, and also made a simple CTF puzzle +**\** What have other folks been working on? +**\** nothing of particular note here, though I'm curious what the latest on the different ring signature schemes is +**\** Aha, that'll be the topic of my talk! +**\** its been on my mind :D +**\** Why's that? +**\** transaction efficiency (both time and space) is one of the obstacles we need to overcome +**\** Agreed +**\** randomX seems fairly solid now +**\** Of course, these proposals aren't really long-term scaling solutions +**\** but they would provide welcome improvements +**\** Is this meeting slow because of defcon? I assume so +**\** There are still some questions on an RCT3 proof that are being investigated +**\** and on the possibility of Omniring efficiency improvements +**\** so the status of different tx protocols may change over time +**\** On that note, an ACTION ITEM for me is to return to Omniring analysis +**\** it's a more complex approach (computationally) than RCT3 +**\** and one of those things where the usual efficiency analysis sweeps some types of simple operations under the rug +**\** but those operations can add up fast! +**\** This weekend's village is of course another big action item :) +**\** Slow day today :/ +**\** Well, in the interest of respecting everyone's time, are there any questions or other research of interest to share? +**\** (crickets) +**\** hey I happen to be here +**\** hello +**\** I was going to ask if there has been any helpful stuff from Lelantus? +**\** The authors have been working on a modified prover that offloads some of the proving complexity to the verifier (and pays a bit in size) +**\** and the goal is still to remove the tracing that's present (and necessitates self-spend operations) +**\** But AFAIK there have been no solutions as of yet +**\** Ah okay, cool. +**\** I suspect that removing that problem would require big architectural changes to the whole construction :/ +**\** but I hope that I am proven wrong :) +**\** Well, since it's a quiet day I suppose we can adjourn the meeting quite early +**\** Hopefully livestreaming will be happening at the DEF CON village so everyone can see the talks +**\** I'll post my slides to github after my talk, since they have (IMO) some nice and simple information comparing tx protocols +**\** Thanks to everyone for attending today! diff --git a/_posts/2019-08-08-logs-for-the-tini2p-dev-meeting-held-on-2019-08-08.md b/_posts/2019-08-08-logs-for-the-tini2p-dev-meeting-held-on-2019-08-08.md new file mode 100644 index 00000000..4b2a7457 --- /dev/null +++ b/_posts/2019-08-08-logs-for-the-tini2p-dev-meeting-held-on-2019-08-08.md @@ -0,0 +1,51 @@ +--- +layout: post +title: Overview and Logs for the tini2p Dev Meeting Held on 2019-08-08 +summary: Current project status, Roadmap, Meta issues, and miscellaneous +tags: [dev diaries, i2p, crypto] +author: el00ruobuob / oneiric +--- + +# Logs + +**\** 0: Greetings +**\** hi +**\** 1: What's been done +**\** Reworked a BuildRequestRecord, BuildReplyRecord, and TunnelBuildMessage to be templated based on symmetric crypto used (AES/ChaCha20) +**\** reorged the commits, because the changes were verbose, and most (if not all) were for code added in the `tunnels` branch +**\** Added `Hop`and `OutboundGateway` classes for tunnel message processing +**\** `OutboundGateway` is still WIP, and will hopefully be finishing up today +**\** didn't get nearly as much done as I had hoped, so scaling back my expectations a bit +**\** going to push back alpha release two weeks +**\** 2: What's next +**\** will be finishing `OutboundGateway`, and implementing `OutboundEndpoint`, `InboundGateway`, and `InboundEndpoint` +**\** those are the last of the message processing classes +**\** dev is somewhat slow because I'm implementing AES + ChaCha tunnels simultaneously (which adds some headache), but it should be worth it in the long-term +**\** ultimately, I think it is faster to do both simultaneously +**\** after the processing classes, I'll start implementing tunnel pools and management classes +**\** given the experience of the past couple weeks, pools + management could take a week each, so alpha may actually be a month away +**\** hopefully not, and I'll do my best to complete them correctly as fast as possible. correctness takes priority over speed, though +**\** 3: ECIES Status +**\** development and discussion on 144 continues +**\** there has been progress over the last couple meetings, and hopefully we're getting closer to consensus on what 144 goals + spec should be +**\** zzz is insistent on unlimited 0-RTT messages, and reusing ephemeral key data for cached DH results +**\** I think both are bad ideas +**\** unlimited 0-RTT messages opens an attack vector for never completing the handshake, where a mitm on the reply tunnel drops Bob's New Session Reply messages +**\** or allows the reply messages through, but blocks Alice's Existing Session messages +**\** reusing ephemeral key data could lead to the same symmetric key being used to encrypt the New Session and New Session Reply payload sections +**\** in a version of the spec that sends multiple New Session (Reply) messages, encrypting different payload sections with the same key material breaks ChaCha20-Poly1305 +**\** it's a fragile scheme, that requires a lot of analysis and care to get right +**\** I'm proposing that instead of sending unlimited New Session and New Session Reply messages, we send one each, including up to the maximum data for one payload section (~60KB) +**\** until the New Session Reply is received by Alice, she will drop any other messages from the client destined for Bob +**\** somewhat outside the protocol, I'm suggesting Alice's router send a "please resend in X seconds/minutes" as a reply to the client until the session is established +**\** similarly, if Bob's initial reply is too large to fit in one Payload section, Bob will send a "please resend after session established" message to Alice +**\** Alice can then send a "reply was too large for initial message, please retry the request" +**\** ^ can send that to the client +**\** alternatively, Alice and Bob could queue messages until session establishment, but that could lead to resource exhaustion. less desirable and less secure +**\** latest I2P LS2 meeting log: https://gitlab.com/tini2p/meta/issues/26 +**\** I'll likely be implementing the drop-until-secure, single New Session (Reply) scheme until we come to consensus on what to do +**\** 4: Next meeting +**\** 2019-08-22 18:00 UTC +**\** @tini2p\_gitlab juggles baffer like a hacky sack +**\** thinking further about the "resend request" message Bob sends when the reply is too large for a single payload section, Bob could include the original request in the message +**\** Alice could then extract the request, and resend in the first Existing Session message diff --git a/_posts/2019-08-11-logs-for-the-dev-meeting-held-on-2019-08-11.md b/_posts/2019-08-11-logs-for-the-dev-meeting-held-on-2019-08-11.md new file mode 100644 index 00000000..796be23f --- /dev/null +++ b/_posts/2019-08-11-logs-for-the-dev-meeting-held-on-2019-08-11.md @@ -0,0 +1,181 @@ +--- +layout: post +title: Overview and Logs for the Dev Meeting Held on 2019-08-11 +summary: Development status, Code & ticket discussion, and miscellaneous +tags: [dev diaries, core, crypto] +author: el00ruobuob / dEBRUYNE +--- + +# Logs + +**\** so dev meeting? :P +**\** hi! +**\** Who's here? hyc, vtnerd, sarang, suraeNoether, moneromooo, jtgrassie, luigi1111, fluffypony +**\** Certainly! +**\** Probably forgetting a lot of people +**\** Guess it's vacation time for a lot of people :-P +**\** here more or less +**\** So what should we discuss? +**\** o/ +**\** testnet->rx ? +**\** as in when can we fork testnet to RandomX +**\** Maybe that would be good with moneromooo back from "frolocking amoung cows" or so +**\** Here, live from def con +**\** Def con party then? :) +**\** Very good attendance at the def con village this weekend, for sure +**\** even being off the beaten path? +**\** Anyway, concerning RandomX: The reviews are all through, right? +**\** Yes, for sure +**\** Having free badges was a huge help +**\** ... present (too busy too lock at clock) ... +**\** https://ostif.org/four-audits-of-randomx-for-monero-and-arweave-have-been-completed-results/ +**\** I think what is left is to merge the RandomX PR from hyc and set a testnet fork date +**\** hey sorry, was afk. but yes +**\** Yes, nice to see all those "fixed" and "solved" +**\** As a side note, thoughts on releasing 0.15 binaries in early september already? +**\** Or would that be too short +**\** would probably need mooo's opinion there +**\** what's our outstanding PR count look like anyway? +**\** I am thinking that we have freedom to release early as we do not have any last minute consensus changes +**\** Quite a lot, but I am working with luigi to get the queue down :P +**\** luigi & mooo\* +**\** cool +**\** a mid-Sept release date sounds plausible. basically 1 month from now? +**\** Sounds like a decent target +**\** It also gives services, users etc. a larger time frame to prepare +**\** The forks with binaries 1 week in advance were admittedly quite hectic :-P +**\** so we would expect testnet to switch to randomx on that mid-Sept date +**\** on or around... +**\** it would be nice to have testnet fork a little earlier to randomx imo +**\** There was some issue with another project's switch to RandomX, right? +**\** Was that an issue with a miner implementation? +**\** Loki. xmrig bug +**\** there are no issues with the monerod integration +**\** What was the effect of the bug? +**\** (in the miner that is) +**\** jtgrassie: so, switch over testnet earlier, but on self-compiled binaries maybe? +**\** dEBRUYNE: the miner didn't reinitialize the dataset when seed epoch changed +**\** yes +**\** all blocks mined after that point were invalid, rejected by daemons +**\** restarting the miner would get it working until the next epoch +**\** but it was patched pretty quickly +**\** Ah I see, so part of the network hashrate basically disappeared because they were mining invalid blocks +**\** yes +**\** So will those mid-September binaries now be the ones that do not support \*long\* payment id's anymore? I lost a little the overview +**\** no idea, haven't followed payment ID discussion +**\** needmonero90: did Binance provide you with a timeline? +**\** https://usercontent.irccloud-cdn.com/file/IA4ai9LF/Screenshot\_20190811-102559\_Telegram.jpg +**\** https://usercontent.irccloud-cdn.com/file/eo22z2BE/Screenshot\_20190811-102608\_Telegram.jpg +**\** https://usercontent.irccloud-cdn.com/file/YcXsymNo/Screenshot\_20190811-102612\_Telegram.jpg +**\** There was the latest. +**\** I can upload the full convo to pastebin if you want it +**\** neat +**\** Yeah, sounds good +**\** moneromooo: are there any infos on which exchanges would be able to receive/send to subaddresses after the mid September fork? +**\** sorry i meant needmonero90 +**\** Anyone got contacts at bittrex or bitfinex? I tried reaching out to them on reddit, but did not get a response +**\** Bittrex can be contacted over their slack iirc +**\** At least a year and a half ago that was the case. +**\** Well, they also could contact \*us\*, at least in theory :) +**\** would be good to create a list, i guess some exchanges will be concerned if removing the ability to use payment ids cribles them to get transactions from other exchanges +**\** Tat: I just took up the discussion with binance because someone had to do it, I don't have the list of other exchanges. +**\** needmonero90: thx +**\** I will happily talk to whoever if we get a contact +**\** Just ping me their details +**\** Kraken important +**\** Kraken will be fine +**\** oh, great :) +**\** Least of our concerns on the exchange front +**\** i think if at least 3-5 big exchanges would move to subaddresses, that would put some pressure on the rest and they probably follow within a reasonable timeframe +**\** Well, "reasonable timeframe" is almost over, with hardfork in mid-October, wouldn't you say? +**\** Maybe they are pretty quiet because they don't want let people look into their cards ... +**\** rbrunner: we are talking of not using long payment id's anymore, integrated addresses would still work i guess, so most of the exchanges will still be able to work with that as is +**\** Ah, ok, right, misunderstood you +**\** The most important thing is to get them off long payment IDs imo +**\** Certainly, if we don't support them anymore in 2 months +**\** so these exchanges aren't supporting integrated addrs yet? +**\** hyc: it depends, i think poloniex uses integrated addresses, bitfinex uses 64 char payent id's +**\** yes, polo uses integrated +**\** dEBRUYNE: do you think receiving of transactions with long payment id's will be still supported by the wallet +**\** Who would send those, and how? +**\** i mean in theory you need to be able to resync, so to prevent that, the wallet would have to ignore all long payment id's from block height X +**\** Yes, the code is full of such switches "Starting from height x stop to do X and start do to Y" +**\** Daily business, so to say +**\** rbrunner: is there really only one source for code of the monero wallet, is there any wallet implementation that isn't using monero c++ wallet core? +**\** I would guess that starting with the fork height the long payment just does not get decoded / delivered to the wallet anymore +**\** tat: Not sure about MyMonero's code +**\** I'm happy with testnet switching to randomx as soon as a patch is made fwiw. +**\** Otherwise I think it's pretty much a monoculture +**\** Pony's the one to get on board since seed nodes and his mining node will need to be updated then. +**\** i mean if there is any wallet that will still send with long payment id's, it wont be too bad, since funds will still arrive but if you rely on that id to track incoming setlements you are screwed +**\** The wallet will ignore the payment id IIRC. It'll still get the money of course. +**\** hyc: The big ones are binance, bittrex, bitfinex +**\** needmonero90 is currently working with binance, I will try to get ahold of the other two somehow +**\** moneromooo: all that's needed before merging the existing randomX integration patch, then, is setting the block height for the testnet fork +**\** IIRC I put a command line switch somehwere to enable something there. +**\** (about payment id decoding) +**\** i would say if an exchange is still using long payment id's and he switches within one month, and he is not able to process long payment id's anymore he will have two years of still receiving to those long payment'id since not all users get that change immediately +**\** they should've switched to integrated addrs 2 years ago ... +**\** i think a command line switch would be pretty fair, with the emphasis on this feature will be deprecated, that would send the right signal +**\** What do you mean with "not all users get that change immediately"? Your software will stop to work after the hardfork, no? +**\** and it's their own obligation to notify their users if deposit addresses change +**\** Maybe I misunderstand, but this is not Bitcoin where the move to SegWit takes 5 years or so ... +**\** The wallet has been warning it's deprecated for a while. +**\** hyc: so you are full positive that sending out with long payment ids will be impossible after the next hard fork +**\** It will likely be still possible. +**\** fwiw, we have been stating long payment ids are deprcated for ages now. they are a problem for privacy and IMO removed asap. +**\** But if several large exchanges still use long payment ids close to the fork, I might be convinced to consensus ban them. +**\** "Close to the fork" ... being ... about today :) +**\** Oh. +**\** To elaborate, using them has required going to advanced settings and toggling a box saying "don't do this" before you could send for ages. +**\** Is there fork soon ? I missed the talk. +**\** mid-OCtober presumably +**\** We're liky july, no ? +**\** No, I mean, as far as big projects are concerned, 2 months pass in a blink of an eye +**\** August. Close enough. +**\** OK, true. +**\** I did give binance until October, so it would be nice not to go faster than that +**\** So "binance, bittrex, bitfinex" sounds like a lot indeed. +**\** Or I'll have to backpedal and apologize and politick +**\** i totally support that point, but for the poor souls that use still long payment ids and continue to receive payments, after the fork with long payment ids, since some users/exchanges will still do so it will be case for customer suport every single time +**\** "Possible" does not mean "easy to do". Maybe would need your own doctored self-compiled software +**\** exchanges and users won't ever stop using payment ids while they are still possible. +**\** Which would work because \*consensus\* would still allow the long id's +**\** to the above: mymonero is indeed not using the monero core wallet - it simply cannot actually +**\** the light wallet server and openmonero implementations are using parts but not the whole as well for the same reason +**\** but the payment id stuff is client side which has already moved away from long ids +**\** i think making it impossible to send long payment ids, but have a switch that still allows to decode them would be a good move, possible fading that switch out over time +**\** yeah our pure fns for long payment ids were actually deleted in mymonero core iirc +**\** fwiw monero core can adopt that code +**\** I think long payment id's still floating around after the work is much less probable than some poor exchange not being able to receive payments at all +**\** s/work/fork +**\** rbrunner: could be true, there is only a few wallets, if they all disallow that, and there is no hand woven code that push transactions to the network +**\** we have certainly seen oddball txns on the network before, which probably came from custom wallet code +**\** but I don't see that as our problem to manage +**\** except it potentially weakens other users privacy +**\** (e.g. if those odd tx outputs get used as decoys) +**\** which is why i favor banning long payent ids at protocol level +**\** I'm a bit reluctant to do that since we still are keeping extradata itself +**\** Banning in october seems a bit optimistic imo +**\** but if the official wallets have already disabled generating them by default, seems OK to me +**\** You do mean the long payment id's? Well, backing down now could set a bad precedent +**\** FWIW, to see what I've done: https://github.com/moneromooo-monero/bitmonero/commits/crash +**\** yes +**\** I don't remember exactly so can't give a tl;dr :) +**\** (grep for "payment" in the commit title) +**\** this? https://github.com/moneromooo-monero/bitmonero/commit/0951c3a9ad0c8376b8abd8908603166d7ffc174d +**\** that one looks good to me +**\** Yes. There's at least another one a few commits earlier. +**\** I also see ignoring receivedo nes https://github.com/moneromooo-monero/bitmonero/commit/6aad370708c0c06c1091912fcc97dceaa09d5b75 +**\** So standalone \*short\* id's are gone also, at least over RPC, if I read that code correctly. +**\** Only integrated over RPC +**\** yeah that all looks good to me +**\** Yes. They were never supposed to be supported. I added them because I'm an idiot. luigi was right. +**\** Now we just wait what bittrex, bitfinex say :) +**\** I still count on them not being stupid, just not noisy - working on it for quite some time already +**\** back to randomx - any suggestions for testnet fork date? 1 week from today? sooner? later? +**\** Whenever pony can be certain to have his nodes updated. +**\** So... mid november ? +**\** sigh... +**\** 2 weeks, for the next meeting? +**\** Oh. I did have some minor stuff I wanted to add for v12. diff --git a/_posts/2019-08-17-logs-for-the-Community-meeting-held-on-2019-08-17.md b/_posts/2019-08-17-logs-for-the-Community-meeting-held-on-2019-08-17.md new file mode 100644 index 00000000..c7d65385 --- /dev/null +++ b/_posts/2019-08-17-logs-for-the-Community-meeting-held-on-2019-08-17.md @@ -0,0 +1,194 @@ +--- +layout: post +title: Logs for the Community Meeting Held on 2019-08-17 +summary: Community highlights, CCS updates, Workgroup report, and miscellaneous +tags: [dev diaries, community, crypto] +author: el00ruobuob / SamsungGalaxyPlayer +--- + +# Logs + + +**\** Hello everyone, welcome back to the typical meeting schedule +**\** 0. Introduction +**\** We would like to welcome everyone to this Monero Community Workgroup Meeting! +**\** Link to agenda on GitHub: https://github.com/monero-project/meta/issues/382 +**\** Monero Community meetings are a discussion place for anything going on in the Monero Community, including other Monero workgroups. We use meetings to encourage the community to share ideas and provide support. +**\** 1. Greetings +**\** Hello +**\** hi +**\** hi +**\** hello everyone, welcome +**\** Hello +**\** 2. Community highlights +**\** Monero just concluded its Defcon village. More details on that later. +**\** I need a Blockfolio banner. What should it be? I need an announcement and a link. +**\** At the moment, it points to monerovillage.org. not great +**\ \** Hi +**\** Point to getmonero.org? +**\** Sure, but with what text? +**\** Maybe something about the upgrade to let people know too? +**\** Check out the official website? +**\** Yeah that would work +**\** Did you upgrade to 0.14.1 yet? +**\** we're supposed to be their test bunny for conversions, so think of some announcements we can make over the next few weeks +**\** PM me if you think of any +**\** I can use it for the coffee chat to see if it gets more traction than normal I suppose +**\** waves as he shuffles in late +**\** Does anyone else have community (non-workgroup) updates to share? +**\** welcome midipoet +**\** thanks for the heads up... +**\** Monero News telegram channel was born this week +**\** very nice lh1008[m] +**\** which one is that? +**\** Oh, and Monero Telegram channel too. +**\** \ @MoneroNews247 +**\** any other questions/updates? +**\** 3. CCS updates +**\** There have been no updates on the CCS proposals in ideas since last meeting. Are there any other comments? +**\<\_hahsun\_>** hi guys +**\** hello +**\** I'll take that as none +**\** please comment on gitlab and reopen the discussions if you are interested in making these proposals come to fruition +**\** Ideas in funding required: +**\** v1docq47: video creation / translations into russian (august - january) (1.33/37.8 XMR) https://ccs.getmonero.org/proposals/v1docq47-video-creation-translations-into-russian-(august-january).html +**\** Continued funding for Surae for another quarter, Aug Sep Nov 2019 (252.42/357 XMR) https://ccs.getmonero.org/proposals/surae-mrl-research-q3-2019.html +**\** World Crypto Con for rehrar and Sarang (28.73/30 XMR) https://ccs.getmonero.org/proposals/rehrar-sarang-2019-wcc.html +**\** Does anyone else have a CCS update, or comments about any of these CCS proposals? +**\** there is one that is not showing on the website +**\** due to being incorrectly formatted +**\** the one about Monero GIGS +**\** \*GIFS +**\** link? +**\** grabbing, sec +**\** https://repo.getmonero.org/monero-project/ccs-proposals/merge\_requests/88 +**\** any comments on this one? looks a little expensive to me, but they have a history of making them and interest +**\** deadline is 2019-09-01 +**\** I don't really think it's necessary, but that's just me +**\** $800 for 25 gifs seems a bit steep +**\** rehrar: are you in touch with Jack? Maybe have him solicit opinions in r/moonero +**\** ok, I'll have him do that. +**\** if people from r/moonero are happy with the rates, then I don't want to be the reason it's not moved +**\** maybe it's something that sub-community is interested in funding +**\** any final CCS comments? +**\<\_hahsun\_>** yes a question. +**\** sure hahsun +**\<\_hahsun\_>** what happens when I did work on a proposal? but it is still open? +**\** Don't really like the CCS for .gif meme creation. +**\<\_hahsun\_>** I have reached some milestones that is +**\** hahsun: that happens sometimes, and usually they are retroactive if approved and funded +**\<\_hahsun\_>** ok. and do I have to update it on the open proposal? +**\** I would probably comment or something, yes +**\<\_hahsun\_>** alright will do +**\ \** Btw, didn't we approve the telegram tipbot already? +**\** el00ruobuob: I think custody was/is still an open question +**\ \** Ah ok. +**\<\_hahsun\_>** yes. I am awaiting a response from fluffy. will update as soon as I get it +**\ \** Great. +**\ \** I still approve it, as a few weeks ago. +**\<\_hahsun\_>** I got a great response from the communit,.thats why I made a plan B if custody is not taken care by the monero team +**\<\_hahsun\_>** I see an increase of users by average of 25 users per day. amazing feedback from people with feature requests. I am happy. +**\** I'm glad this is proceeding even as you wait for a response +**\** 4. Workgroup report +**\** moneromooo is still on vacation, but development continues +**\** \<\_hahsun\_ "I got a great response from the "> Decentralize the responsibility. Just saying. +**\** vtnerd make some i2p and lightweight server upgrades +**\** \<\_hahsun\_ "I see an increase of users by av"> Awesome +**\** there are some other node updates +**\** 2 output minimum will now be enforced on consensus layer (hooray, thanks Isthmus) +**\<\_hahsun\_>** I will lh1008. I try. thanks +**\** those are the main things that stuck out to me looking at the github commits. Am I missing something? +**\** looks like there is still activity with the tini2p according to the gitter dev channel +**\** interesting. we will have to see how that comes about +**\** we met some i2p folks at defcon +**\** they also posted a defcon report on their forum +**\** https://i2pforum.net/viewtopic.php?f=18&t=875&sid=088751cca1b2e6560a01a2e960671eb7 +**\** \ Nice! +**\** any localization updates? chime in or I'll proceed to the gui updates +**\** I think we're largely still waiting for WebLate to be enabled +**\** no GUI updates from me +**\** GUI has a few other design updates. It's nice to have a group of people consistently participating and politely discussing different options +**\** dsc\_ has been slacking indeed +**\** totally not focused on the ctf or anything +**\** hehe +**\** which transitions us nicely to.... +**\** d. Defcon workgroup +**\** also i2p-zero and I traveled to meet certain GUI contributors +**\** there is more happening that you dont see ;p +**\** Monero^TM +**\** Defcon is over! What an event! Livestreams had some issues but are up: +**\** Friday: https://www.youtube.com/watch?v=wNnjO1XSEdg +**\** [ Monero Defcon27 Village - Friday Livestream - YouTube ] - www.youtube.com +**\** Saturday: https://www.youtube.com/watch?v=J\_9ssXDErqY +**\** [ Monero Defcon27 Village - Saturday Livestream - YouTube ] - www.youtube.com +**\** Sunday: https://www.youtube.com/watch?v=un7-pwkZRDc +**\** [ Monero Defcon27 Village - Sunday Livestream - YouTube ] - www.youtube.com +**\** The hotel AV staff recorded all the talks, but they will probably take months to be uploaded. I’ll keep trying to grab copies in the meantime. +**\** Read rehrar’s report: https://www.reddit.com/r/Monero/comments/cqegma/monero\_village\_defcon\_2019\_report/ +**\** [REDDIT] Monero Village - Defcon 2019 report (self.Monero) | 78 points (96.0%) | 19 comments | Posted by Rehrar | Created at 2019-08-14 - 19:20:38 +**\** I will be sending photos that I took to the relevant people so that they can share as they choose. Here are what I’m calling “atmosphere photos” of the room and non-people. PM me for original versions of the ones you like: https://imgur.com/a/fu9vmDQ +**\** Monero Talk uploaded 10 videos from the event: https://www.youtube.com/channel/UC3Hx81QYLoEQkm3vyl4N4eQ/videos +**\** [ Monero Talk - YouTube ] - www.youtube.com +**\** There are many areas for improvement, but I think it was overall an improvement compared to last year. We still need more people to sit at the front tables and answer the "what is Monero" question 10,000 times +**\** rehrar's report was great! +**\ \** Where could we find the moneropoly? I need one. +**\** el00ruobuob: these were limited first-edition releases. None left. However, CypherMarket will have the second version at some point +**\ \** \\o/ +**\** Which will be arguably better as they will have custom house/hotel pieces +**\** btw rehrar alleges the typical Moneropoly game takes 30 minutes..... more like 3+ hours +**\** 30-40 if played quickly and by correct rules +**\** no way +**\** anyway +**\** that's all from me for Defcon. we can finally talk about other stuff happening in the community +**\** 5. Open ideas time +**\** It’s open ideas time! Feel free to propose your ideas to this discussion group, and feel free to comment on others’ ideas. If you disagree with the idea, please reply with constructive criticism. Thank you! +**\** I'd like to discuss the possibility of marketing through an (video) advert - how that could look like +**\** sure, what do you have in mind +**\** I had nothing particular in mind, but something in the spirit of Apples "privacy" commercial +**\** I love the way that ad gets the point across +**\** It's a very good ad indeed. +**\** https://www.youtube.com/watch?v=A\_6uV9A12ok +**\** [ Privacy on iPhone — Private Side - YouTube ] - www.youtube.com +**\** \ Yes +**\** Monero has barely no marketing - I don't mind that much usually.. but I'm the position to use proffesional equipment to create something. +**\** \<== also filmmaker +**\** person of many talents +**\** Adverts are tricky though. Just wondering what the community thinks. +**\** Nice! I'd be down to throw in some money to the CCS or whatever +**\** \ Nice idea +**\** I haven't thought of a video series, but I will tell of one ad campaign we are slowly working on for Mastering Monero +**\** We are going to be advertising "Using Bitcoin isn't safe", "using x isn't safe" with links to pages outlining why the privacy protections are terrible, then recommending Monero +**\** If anyone has an idea for a 1 minute commercial feel free to send it my way. I shoot on super 16mm (Aaton XTR). +**\** dsc\_: do you have anything in mind at the moment? +**\** sgp\_: absolutely no idea +**\** who is the target audience? +**\** It could be something that represents our community and values +**\** Which then could be used on the website or .. I don't know. +**\** "open source is better" +**\** "Monero: we've got your back" +**\** "Monero: no surprises" +**\** Yeah. Ill make sure it doesn't get cheesy I can provide some stills from a thing I shot recently. +**\** Anyway, just wanted to present the idea. +**\** Out of curiosity on the note of advertising, are there any billboard designs people have already? +**\** A ~$2K billboard in PHX (roughly 5 mil people) nets roughly 3mil impressions over a month, allegedly +**\** Regardless of this video idea I think Monero could currently use some proffesional marketing. Our software is currently stable enough for the masses, good ecosystem all-around (better than during 2017 bubble). +**\** Mastering Monero info from Amazon: https://usercontent.irccloud-cdn.com/file/tq2doUtJ/amazon%20advertising +**\** But I can also understand if we don't do any marketing since we're a grassroots community. So it's fine eitherway +**\** If we do marketing maybe it would be a good idea to target areas with privacy conscious people/culture. Not sure how to determine that though... +**\** dsc\_: if you advertise Mastering Monero, we may be able to pay for a budget +**\** Interesting. +**\** I think the video would be worthwhile. While organic word of mouth growth is great, if we want to accelerate adoption the word needs to get out to more people +**\** Yes, I think marketing is fine +**\** as long as it isn't predatory +**\** any final comments before we wrap up? thanks dsc\_ for introducing the topic and offering your skills +**\** Any MRL questions? +**\** when auto churn? +**\** We should probably have a semi-formal postmortem for DEFCON in the next month or so after folk have had a chance to rest, but before people forget too much +**\** kidding +**\** I'm on mobile but can type slowly +**\** xmrscott[m]: indeed, would be good +**\** I'll post the info here after polling folk for a good time in -defcon +**\** 6. Confirm next meeting date/time +**\** The next community meeting will be in 2 weeks on 7 September at 17:00 UTC. The next Coffee Chat will be on 24 August at 16 UTC. +**\** 7. Conclusion +**\** That’s all! Thanks for attending this Monero Community meeting, and we hope to see you on r/MoneroCommunity and #monero-community. Take care, and know that change starts with YOU. diff --git a/_posts/2019-08-20-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-08-20.md b/_posts/2019-08-20-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-08-20.md new file mode 100644 index 00000000..a93d7eca --- /dev/null +++ b/_posts/2019-08-20-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-08-20.md @@ -0,0 +1,114 @@ +--- +layout: post +title: Logs for the Monero Research Lab Meeting Held on 2019-08-20 +summary: Sarang work, Surae work, and miscellaneous +tags: [dev diaries, community, crypto, research] +author: el00ruobuob / sarang +--- + +# Logs + +**\** OK, let's get started with our meeting +**\** Agenda here: https://github.com/monero-project/meta/issues/383 +**\** Logs posted there afterward +**\** GREETINGS +**\** hello +**\** howdy +**\** heya +**\** It's been two weeks since the last meeting... plenty to discuss! +**\** In the spirit of fairness and teamwork, I'll go first :D +**\** The DEF CON village, despite having a poor location, was well attended +**\** I did a talk, a workshop, a CTF, and a panel discussion +**\** how did the attendance compare to last year? +**\** I would estimate higher +**\** nice! +**\** I've written up a brief spacetime analysis of Omniring in its current form: https://github.com/SarangNoether/skunkworks/blob/sublinear/omniring.md +**\** It does not presently support batching, but the authors have a couple of ideas on how to do so safely that are forthcoming +**\** I'll be discussing with them this week +**\** On a related note, the RCT3 construction has a flaw that would be exploitable in practice +**\** The authors of that paper, I'm told, also have a fix forthcoming that may relate to the Omniring batching enhancement +**\** Made a quick PR to fix a bias in Schnorr signatures: https://github.com/monero-project/monero/pull/5807 +**\** o/ +**\** Cleaned up an MLSAG improvement PR: https://github.com/monero-project/monero/pull/5707 +**\** Made some updates to Zero to Monero (see topic branches): https://github.com/SarangNoether/zero-to-monero/ +**\** And I'm working on getting CLSAG and thring sigs submitted to conference proceedings (a tiresome and lengthy process) +**\** That's my two cents +**\** damn, son +**\** yeah, that was a damn mic drop brother +**\** Anything to share with the class, suraeNoether ? +**\** as for me, I've been on vacation and just got back. I'm still going to be only half-on today because I have some personal business I have to attend. it was an eventful vacation. for one thing, I was able to prove a few theorems for my graph matching paper that are necessary for publication. based on a conversation I had with sgp\_ right before I left, I spent a lot of time thinking about experimental +**\** design, and I'm starting to discuss this with sarang. +**\** in addition to that, I was contacted by Astral, the team working on bullet-proof monero-mining drones, re: an unfortunately urgent funding matter. +**\** sarang what happened to reusing existing functions or adding it as a function instead of inline? +**\** not that it matters that much I guess +**\** There were some silly issues with includes and having access to the right underlying functions +**\** It seemed simpler to do it as is +**\** i would urge folks in the audience to watch OhGodAGirl\_\_'s talk from teh Konferenco here (https://www.youtube.com/watch?v=jDSKIr5EPiU ) or Leah's interview wiht monerotalk https://www.youtube.com/watch?v=jl1w6VDEWq4 to refresh themselves on the project +**\** meaning they need funding? +**\** if anyone is interested in assisting Astral in composing a CCS, I've been pinging some ideas back and forth with Leah +**\** yes, and some of the funding needs are rather urgent; I spoke with OhGodAGirl\_\_ and OpenSourceress about this in person at the Konferenco and we have been kicking some ideas around +**\** i anticipate a vigorous discussion on the matter, because the community funding sources, in my mind, should be a source of funding of last resort +**\** the folks who contribute to the monero community are people who care about privacy and they want to see the project advance in a healthy direction, and without them, all of this falls apart +**\** Probably a good discussion for -community? +**\** Unless there's a technical/research component to it? +**\** well, it's a nascent funding request for a hardware project with a timeliness component that recently presented at our conference, but going into further detail during the meeting is certainly unnecessary +**\** got it +**\** and full disclosure: i am not yet in any way financially linked with Astral, although that may eventually change +**\** i.e. this isn't for me +**\** Anyone else wish to share research work of interest? +**\** I'm excited to take a look at the current state of the matching simulations suraeNoether +**\** that's all I have for the round table this week, but I'll also be playing catch-up on the lelantus vs. omni vs. rct3 cage match that's been going on these past few weeks +**\** may eventually change? hamster.gif +**\** OK, so after the brief ROUNDTABLE is GENERAL QUESTIONS... anyone? +**\** I have a general question +**\** i have one, too +**\** The proceedings/journals under consideration for CLSAG (thanks also to some outside advice) are Financial Cryptography, PETS, ACM TOPS, and ANCS +**\** Any other suggestions that I may have missed, that could be in scope? +**\** It's tough in the CLSAG case since it's an improvement over earlier work, but not earth-shattering +**\** and that always seems to be a tricky place to be in the publishing world +**\** I plan to highlight the improvements and generalize it a bit for submission +**\** are you strictly considering conference proceedings or are you open to journal-only suggestions? +**\** Journals are fine too (ACM TOPS, e.g.) +**\** But since submissions are typically one-at-a-time, there's no real rush to add to the list +**\** But obviously prioritizing is useful to avoid submitting for delayed rejections +**\** fair enough. I thought ACM TOPS was a conference, silly me. :P +**\** Anyway, that's my question +**\** suraeNoether: yours? +**\** some of the biggest improvements that have come out of MRL this year have involved efficiency improvements, ranging from bulletproofs optimizations to compressed signature schemes. Only some of these improvements will carry on to the "next version" of monero, especially if we end up having to migrate our transaction model to something like one of the Big Three... +**\** suraeNoether: Don't they have other options than to tend to the CSS? +**\** I genuinely think this is not appropriate for it +**\** so my question is: what sort of improvements would you like to see from the Monero Research Lab in the next year, keeping in mind that we will want to migrate to a different scheme sooner or later? +**\** dEBRUYNE: i'll start a conversation about this over in -community +**\** I would definitely like some research into ring sig alternatives. +**\** That's very much in progress rehrar +**\** do you mean ring confidential transactions? +**\** from the ground plebs, we're never quite sure how much progress and when and why and stuff +**\** because lelantus, omni, and rct3 are each replacements for ring sigs +**\** in a certain sense +**\** but they are still ring confidential transaction schemes +**\** Yeah, my analyses try to give a reasonable spacetime estimate for those protocols +**\** I wonder if a bimonthly MRL bulletin would be helpful to the masses +**\** or a monthly one +**\** I can assist in getting it out +**\** suraeNoether: OK +**\** Any other general questions? +**\** sarang, do you have an answer to my question? +**\** rehrar answered and this was something i was happy to see +**\** usually it's the noethers talking at everyone else during these meetings :D +**\** but i am curious +**\** I think determining the real viability of newer transaction protocols is a priority for my research +**\** okay. my personal white whale has always been to replace linearly-sized RCT with something sublinear but sufficiently fast to not drag down the network, so i'm happy to have such an embarassment of schemes to work through +**\** anywya, no other questions from me +**\** Yeah, once the RCT3 fix and Omniring batch issues are solved, there will be a much clearer view of what's reasonable IMO +**\** Anyway, on to ACTION ITEMS +**\** I'll be discussing protocol details with some other researchers this week, to gain some better information on these changes +**\** Getting the preprints sorted out for edits and submission +**\** If any of you feels like leaving a brief comment here btw -> https://www.reddit.com/r/Monero/comments/ct29nx/spectre\_protocol\_update/ +**\** and catching up on a backlog of other preprints that have come out +**\** suraeNoether: ? +**\** working with you on matching code and experimental design, and backlog reading on the work Sarang has done over the past 2 months comparing these three sublinear protocols +**\** neat +**\** OK, any final questions or comments before adjourning? +**\** going once +**\** going twice +**\** Adjourned! Logs will be posted shortly diff --git a/_posts/2019-08-22-logs-for-the-tini2p-dev-meeting-held-on-2019-08-22.md b/_posts/2019-08-22-logs-for-the-tini2p-dev-meeting-held-on-2019-08-22.md new file mode 100644 index 00000000..92eb527b --- /dev/null +++ b/_posts/2019-08-22-logs-for-the-tini2p-dev-meeting-held-on-2019-08-22.md @@ -0,0 +1,78 @@ +--- +layout: post +title: Overview and Logs for the tini2p Dev Meeting Held on 2019-08-22 +summary: Current project status, Roadmap, Meta issues, and miscellaneous +tags: [dev diaries, i2p, crypto] +author: el00ruobuob / oneiric +--- + +# Logs + +**\** 0: Greetings +**\** hi +**\** 1: What's been done +**\** A lot +**\** I've more-or-less finished the tunnel message processing classes (Hop, InboundEndpoint, InboundGateway, OutboundEndpoint, OutboundGateway) +**\** still making changes as I impl tunnel management classes (InboundTunnel, OutboundTunnel, TransitTunnel, Pool, PoolManager), but the changes are fairly minor +**\** had a few big, time-consuming refactors for the processing classes, but most of those are finished now (hopefully) +**\** I am almost done with the TransitTunnel class (used for participating in Tunnels created by remote routers) +**\** :wave: +**\** hi @DavidBurkett, how are you? +**\** Great! And yourself? +**\** doing well, thanks :) +**\** welcome +**\** to the meeting +**\** Happy to be here. Will observe and try not to interrupt :) +**\** right on, feel free to ask or comment at will +**\** happy to have you, as always +**\** so Tunnels are almost done, and have been what I've spent all of my time on over the last two weeks +**\** 2: What's next +**\** so, the last few I2P LS2 meetings have been a bit hairy +**\** we've been discussing, mainly, changes to 144 (ECIES-X25519 end-to-end sessions) +**\** admittedly, I could have handled things much better than I did +**\** thankfully, things seem to be moving forward again, and we've concluded that reuse of ephemeral keys is a bad idea +**\** it will require some changes to my ECIES-X25519 impl, which I will do after finishing tunnels +**\** whether to follow the drop-until-secure or send-NewSession-until-secure is still to be determined +**\** drop-until-secure is what I prefer, and means routers with drop end-to-end messages, until a secure channel to the Destination is established +**\** only requires one round-trip, and support sending one 0-RTT payload in the initial NewSession and NewSessionReply messages +**\** zzz is of the opinion that drop-until-secure will not work for performance and client-related reasons +**\** I haven't begun to implement client stuff, so maybe zzz is right +**\** NewSession-until-secure basically sends NewSession messages to the Destination until the first NewSessionReply is received +**\** Is that discussion in the PR for 144 or something? +**\** Or was that in IRC? +**\** was on Irc2P, the meeting logs are here: tini2p/meta#29 +**\** Thanks :) +**\** and here: tini2p/meta#28 +**\** guess it might be a bit much to rehash the discussion here, just trying to summarize +**\** I'll read through and understand +**\** YOu have good TL;DR's +**\** NewSession-until-secure also has its problems, but should be workable +**\** thanks :) +**\** anyway, I'll be implementing the drop-until-secure until we come to consensus on what actually becomes spec +**\** it's simpler, more secure, and more efficient +**\** though latency/performance may be a killer for it +**\** after the changes for ECIES-X25519, I'll be gluing everything together with a RouterContext class +**\** with RouterContext, I'll be able to have the NTCP2 transport talk to the Tunnels and NetDB classes +**\** I'll create some basic unit tests, if they make sense. the majority of the tests for RouterContext will be net-tests (integration/functional tests) +**\** with RouterContext finished, tini2p library users will be able to build their own router +**\** that will likely be alpha-release time +**\** I'm shooting for a one-week impl time on RouterContext, but may run into bugs/refactor work that pushes that timescale back a week or two +**\** it's really just gluing stuff together though, so I'm hoping it goes quickly +**\** I also need to make a small update to NTCP2 for the testnet-separation update to specs from 147 +**\** basically it's a netID check that ensures no cross-talk between mainnet and testnet routers +**\** it's important for I2P network health, so I am happy to impl +**\** That's awesome! I'll watch for updates on that RouterContext. I'll try setting one up once you're finished +**\** for sure :) +**\** will likely be adding a docker setup, so you can run a full testnet entirely locally +**\** Nice! +**\** definitely! also allows spinning up 10+ routers on different /16 pretty easily, so it may be a good way to do integration tests with I2P Java and i2pd once I add ElGamal tunnel building +**\** ElGamal tunnel building is post-alpha though +**\** :) +**\** so that's about it for stuff until alpha release +**\** 3: Questions/Comments +**\** Nothing from me. :thumbsup: +**\** for sure +**\** 4: Next meeting +**\** staying on normal schedule, two weeks from today: 2019-09-05 18:00 UTC +**\** that's all, thanks all for the meeting +**\<@tini2p\_gitlab>** gaffer banger diff --git a/_posts/2019-08-25-logs-for-the-dev-meeting-held-on-2019-08-25.md b/_posts/2019-08-25-logs-for-the-dev-meeting-held-on-2019-08-25.md new file mode 100644 index 00000000..2c92b332 --- /dev/null +++ b/_posts/2019-08-25-logs-for-the-dev-meeting-held-on-2019-08-25.md @@ -0,0 +1,220 @@ +--- +layout: post +title: Overview and Logs for the Dev Meeting Held on 2019-08-25 +summary: Development status, Code & ticket discussion, 0.15 release discussion, and miscellaneous +tags: [dev diaries, core, crypto] +author: el00ruobuob / rehrar +--- + +# Logs + +**\** Meeting time, but it seems Rehrar has problems getting through to here from Mattermost ... +**\** rehrar can't join IRC directly? +**\** ok, let's do this then +**\** So you all don't see him either, right? +**\** I'm on the move atm, unfortunately. +**\** Nope +**\** Technology, pfft +**\** In fact, I may be called away in about twenty minute's time. +**\** I can lead until then, but maybe dEBRUYNE or moneromooo can afterwards? +**\** normal stuff today. +**\** Sure +**\** 1. Greetings, 2. What's done since last meeting? 3. Code/ticket discussion 4. Other meeting items 5. next meeting time +**\** pings luigi1111 sarang fluffypony moneromooo vtnerd suraeNoether\_\_\_ hyc jtgrassie selsta xiphon +**\** 1. Greetings +**\** say hi +**\** hi +**\** Hi +**\** dsc\_ medusa\_ also +**\** hi +**\** \ hi +**\** 2. What's been completed since last meeting? +**\** Hi +**\** Did you guys have a meeting a couple weeks ago? I was at defcon, so didn't attend. +**\** hi +**\** Yes, there was a meeting two weeks ago +**\** there was a meeting 2 weeks ago, not much happened +**\** cool, so completed since then then +**\** been a slow past couple of weeks? +**\** I've worked with luigi and mooo to get some stuff merged +**\** We're at about 60 open PRs now (quite a few of those are relatively new) +**\** on CLI? or between both CLI and GUI? +**\** CLI yes, but luigi also merged some stuff for the GUI +**\** any idea on what those things are? summary. +**\** vtnerd how's your stuff coming along? Everyone awaits with bated breath. +**\** You mean what kind of PRs were merged? +**\** dEBRUYNE yes. What'd they do. +**\** Just for anyone reading the logs. +**\** As far as I can see, mostly optmizations, bug fixes, readme additions +**\** IPv6 support got merged +**\** Cool deal. +**\** Also a few improvements to the deterministic build process +**\** I'd like additional review on a slightly older MLSAG PR: https://github.com/monero-project/monero/pull/5707 +**\** Bunch of new tests got added too +**\** (recently updated) +**\** ^ Perhaps luigi1111 can have another look at that? +**\** Im working on handling the mempool separation, which is a bit tough to separate the components cleanly +**\** You mean code separation? +**\** the first PR for white noise appears to not be hated at least - I rebased and tested against the ipv6 merge +**\** regarding the broken Travis builds - they were broken due to ncurses configuration, sent a PR that fixes the issue. +**\** Though now some builds are halt on libunwind build error. Did we change anythign related to libunwind recently? +**\** ideally dandelion++ and this covert sending technique have different mempools +**\** but its determining how to handle it thats the tricky part - whether the txes are stored in the lmdb file like normally, kept only in memory, or separately altogether +**\** its a very subtle leak of information if your tx is in the mempool stored on disk before appearing anywhere else, but this is monero so ... +**\** dandelion++ flat out suggests separate mempools because the information can be leaked externally through p2p or rpc calls +**\** so for both dandelion++ and my CCS I proposed a separate mempool that didn't return the tx until it was "spread" +**\** you don't foresee any of this being live in October, yeah? +**\** Or perhaps none of this necessitates a hard fork? +**\** none of these needs a fork +**\** \*this +**\** aight, so it can go live whenever. Would any of this need to be audited, you think? +**\** or is it not that simple? +**\** I'm guessing that's the answer. +**\** uh, its not the typical thing that gets audited, theres no cryptography involved really, but its wrong of me to push against it probably +**\** vtnerd: explanation makes sense, thanks +**\** dEBRUYNE now I have to step away. I should be back in a while, but I don't expect the meeting to last that long. Can you take over? +**\** Sure +**\** thanks +**\** vtnerd but it sounds like this could just be a flag on records in the single txpool +**\** yes, that is something that I thought about +**\** and you only need to control disclosure when a remote client is asking +**\** not e.g. the local CLI +**\** ^ you still need to do this even with separate mempools +**\** the only negative is that its recorded on disk to what is generally believed (or at least by me, perhaps not all) to not contain "sensitive" information. that flag would be recording that the tx origin was that machine +**\** and its mixed with what is otherwise public information +**\** ... no, that flag's meaning is not necessarily that. +**\** it might be something I end up doing - since its less work - and document that it can be updated as needed +**\** the flag is "broadcasted yet" - it would be false on intermediate nodes in the dandelion stem too +**\** yes +**\** my only concern about mixing was the small data leak to disk and making sure it wasn't easy to accidentally undo. +**\** I think its just going to use an existing flag or a new one, because its the easiest to get the bulk of the concern - the externally visible network traffic - up and running +**\** using a separate memory-only pool has the same dangers as why we switched to LMDB in the first place +**\** it can grow to ubnounded size +**\** and unless you use locked memory, it could just get swapped to disk anyway +**\** yeah I had been considering a separate lmdb file for this. No code was written for that, but I was going through it in my head to track how much work it was +**\** and if you use locked memory, you'll just run out +**\** its not terrible, but cleaning up the tx inspection process should probably be done first +**\** I was thinking of storing it to disk using lmdb, but letting the user specify a separate entry point for an encrypted volume, but its going to be too much work (as you are likely hinting at) +**\** This all is only relevant if you have a local attacker, right? +**\** I would think so, yes +**\** for the most part. I primarily wanted to do it because I still think its easier conceptually to have two separate pieces in code handling this, but its not trivial +**\** and a local attacker that can examine the disk can probably also examine monerod's memory +**\** Yes, and if your starting point is "no dandelion++ whatsoever", maybe implement that quick and worry about local attackers afterwards +**\** if the person is storing the blockchain to an unencrypted portion thinking its all public information +**\** arguably everyone is running monerod on a machine using disk encryption, but perhaps not always +**\** also storing txes in lmdb will help in case of casedandelion++ stem phase fail +**\** one could safely restart the daemon and don't bother that any outgoing tx will be lost +**\** theres also a small concern about getting information remotely via timing, but thats another advanced attack that I was merely going to document rather than code around (it aint easy) +**\** Good argument +**\** and Im not even sure how realistic that timing attack is, its going to vary from machine to machine a lot +**\** xiphon: thats probably pointless +**\** fwiw, a patch for page-level encryption in LMDB is available, works fine. I haven't released it yet because I wanted to add authenticated encryption +**\** because the embargo is almost certainly going to fire, and everyone in the chain is broadcasting at that point +**\** which requires eating up extra space for the encryption signature +**\** but we could go with the current patch immediatelym if it helps +**\** dvtnerd\_\_: oens't seem so to me +**\** if you restart the daemon right after sending a tx and choosen stem node fails, you tx will be lost +**\** its no worse than the current code, so I don't see a reason to rush +**\** and that won't happen with lmdb-stored txes +**\** and likely the timer from the origin node goes off by then anyway, its probably close +**\** although we could have it retry on connection loss to a backup node before doing the embargo timer thing +**\** with dandelion++ theres always the possibility of an intentional blackhole, so storing the stem txes to disk is not an obvious benefit +**\** the origin needs counter-measures either way +**\** something is wrong then, this sounds like we don't guarantee that tx will be broadcasted to the network +**\** you can't with dandelion++, thats how the protoocl works +**\** and to be fair, you cannot really guarantee it with the gossip protocol either +**\** theres no acking on this, its a fire and forget in monero +**\** D++ is intended to fail to the existing broadcast scheme, essentially +**\** yes, its one of the consequences of having a single outbound path +**\** ... we really should be using IP multicast +**\** btw, for those who aren't following this -dev channel all the time, I have a randomx testnet node on 206.127.12.163:28080 +**\** seems there are only 5 peers active at the moment +**\** Yeah, that was one of my questions, how that's going +**\** There were plans anyway to switch testnet soon, right? +**\** running uneventfully so far. mining, sending coins around +**\** official switch is waiting on fluffypony's availability +**\** +**\** But your well-running private testnet is a pro argument, then +**\** For such a switch +**\** With respect to binaries, what would the devs prefer? +**\** Would a first 0.15 release within a few weeks be a proper timeline? +**\** Nobody seems to push a release, funny +**\** there will be anissue with Ledger +**\** They hardcoded accepted Monero version in the ledger monero app - the firmware the is installed on ledger device +**\** it only accepts "0.14.1.0" string right now +**\** So they must plan to follow-up any Monero release quite closely, otherwise that does not make sense +**\** and (if i'm correct) it usually takes some time for them to push an app update +**\** all the better to get a 0.15RC out sooner then +**\** and get them to use a saner version check. like >= 0.14.1 +**\** Exactly +**\** They added the strict version check because of the change bug. +**\** as a fallback plan, i thoguh about doing a workaround on the monero side +**\** disabling this check by always supplying "0.14.1.0" version to the device +**\** yeesh... +**\** Oh, that's a straight road to hell +**\** See all the lying Windows does about the version numbers ... yikes +**\** They added the version check on purpose so we shouldn’t disable it like this. +**\** right, i'm not saying it is good +**\** but, we will loose ledger support with the new version if they won't manage to patch their code +**\** They managed to do it in time with the v0.14.1.2 release. +**\** That's why hyc's argument of early 15.x release is good +**\** yes, give them more advance warning, more time to respond +**\** The earlier before the hardfork itself that is out, the better +**\** The white noise stuff will most likely be in the october release. +**\** Before a 0.15 release, the v12 changes should be reviewed and merged. +**\** xiphon: I presume they will release a new version in conjunction with our v0.15 release +**\** That's 5823. +**\** So 5823 and the RandomX PR are the consensus changes that need to go in before we do an RC right? +**\** sounds right +**\** randomx is 5549 +**\** so we are doing an RC release this time? +**\** because i remember many were against last hard fork +**\** dEBRUYNE: hopefully they will implement version >= check, so the user won't need to update the ledger app with every monero release +**\** Plan was to add >= for minor point releases. +**\** ErCiccione[m]: I guess we could also do a straight 0.15 and then work out any bugs via point releases +**\** moneromooo, hyc, vtnerd\_\_: thoughts? +**\** also xiphon +**\** well thats how its been done the last few releases +**\** i mean, i would totally go for an RC release +**\** Isn't that mostly only an issue with labels? +**\** If you're asking about version numbers, my preference is to have increasing version numbers. It mkaes things so much easier. IIRC pony prefers to have "rc" labels instead. +**\** I'm not gonna fight that, just moan from time to time and say "told you so" if it bites us later. +**\** vtnerd\_\_: Right +**\** Yeah, but also, how would an RC be effectively different from a release? +**\** And not just called any other way +**\** I guess we can release earlier now though because randomx and the other consensus changes are already ready +**\** As long as it contains all the needed consensus changes. +**\** You are not moaning, you are moooing +**\** That's randomx and 5823 AFAIK. If there's something else, say so. +**\** rbrunner: indeed! +**\** rbrunner: "but also, how would an RC be effectively different from a release?" - i think the difference is in the official press release statement +**\** we won't do one for -RC +**\** so it will be for testing purposes +**\** randomx has 1 PR pending: https://github.com/tevador/RandomX/pull/118 +**\** Hmmm, ok, but with the risk that less people test then +**\** rbrunner: if that's is not how it is supposed to be, i'm lost +**\** I see what you mean, yes, it's a trade-off of course +**\** sech1: An audit result, then, this RandomX PR +**\** that PR appears (so far) to have no downside +**\** about the RC thing. Since there are many contrasting opinions, maybe better keep the old system. +**\** "Everybody builds their own" ? +**\** The old system does not really look broken, either, so why fix +**\** well, would be nice to have more testing before a proper release, but at this point i think it doesn't worth it. +**\** I suppose, if we don't do that last-minute advance-by-1-month release, it should work out fine +**\** Readline is still broken with reproducible builds. +**\** that has to get fixed with v0.15 +**\** isn't there already a PR for that? +**\** I haven’t seen one. +**\** We could reverse the commit that broke it I guess? +**\** Reversing it would mean no readline at all But that’s better than broken readline I guess. +**\** hm, can't find one, must be misremembering +**\** I think the original problem is linking readline without its curses dependencies. the next problem is that curses has different dependencies on different OSs +**\** So I guess that is added to the list of things that need to go in before we tag +**\** Would a target of tagging in 2 weeks be reasonable? +**\** terminfo vs termcap vs ... something else +**\** Any vote against the pay-for-rpc going in ? +**\** (I have a wip patch to make it use randomx, not pushed yet) +**\** I have nothing oposing +**\** It's reviewed well, after all +**\** would be nice to have it in the 0.15 +**\** I guess we can conclude the meeting then diff --git a/_posts/2019-08-26-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-08-26.md b/_posts/2019-08-26-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-08-26.md new file mode 100644 index 00000000..38100910 --- /dev/null +++ b/_posts/2019-08-26-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-08-26.md @@ -0,0 +1,96 @@ +--- +layout: post +title: Logs for the Monero Research Lab Meeting Held on 2019-08-26 +summary: Surae work, Sarang work, and miscellaneous +tags: [dev diaries, community, crypto, research] +author: el00ruobuob / sarang +--- + +# Logs + +**\** All righty! +**\** Let's begin our meeting +**\** Agenda: https://github.com/monero-project/meta/issues/385 +**\** Logs will be posted there after the meeting +**\** GREETINGS +**\** hi +**\** hello +**\** good morning +**\** Let's move to ROUNDTABLE +**\** suraeNoether: care to go first? +**\** sure, last week I made a commit to my buttercup branch with some matching algorithm fixes, which is now operating as far as i can tell 100% smoothly +**\** Nice! Looking forward to reviewing it +**\** i also have the framework for a markov chain simulator of a basic ledger almost ready to push later today, which we will be using to identify best practices while churning, etc +**\** in addition to that, I discovered a discrete distribution over the weekend that could be very helpful in working with output selection +**\** that's pretty much it. not tremendously eventful, except the matching algo unit tests +**\** Will be neat to see if we can adjust output selection to such a distribution efficiently and robustly +**\** Low priority in the grand scheme of things, but intriguing nonetheless +**\** I am finishing preparation of the CLSAG paper for submission to Financial Cryptography 2020 +**\** definitely, will be nice to have some exploration of churning that we can document +**\** PR 5707 has been updated to simplify the hashing code +**\** oh, sarang and i decided we should also submit the thring signature paper to FinCrypt2020 also, sort of doubling our chances (but not really, it's nonlinear :P) +**\** Note that this removes `hashToPointSimple` and moves its functionality directly into the relevant unit test +**\** `hashToPointSimple` is only used to produce a Pedersen generator, but it's brittle on arbitrary input and not useful elsewhere +**\** (unless we updated how we do hash-to-points to use an iterated index, but this is not backwards-compatible) +**\** Additional eyes on PR 5707 would be welcome +**\** And: Stanford announced the dates and CFP of their next blockchain conference +**\** TBH it's probably not worth our time to submit a paper/presentation, given their acceptance rate +**\** Unless anyone has an idea for something something zero knowledge ethereum =p +**\** I kid, I kid +**\** \*cough\* +**\** but not +**\** lol +**\** Finally, I continue analysis work on proving systems +**\** 5707 is for how the second basepoint in our pedersen commitments are selected. if i recall from my conversation with sarang earlier, this PR will make the monero codebase slightly more robust, less brittle, more consistent with the way it works, and more importantly \*more easily verified to be correct\* by new users, even though it's a relatively small change +**\** RingCT3.0 is exploitable in its current form, but I'm told a forthcoming fix likely solves the problem (unclear if provably at this point) with little impact on efficiency +**\** suraeNoether: the change only makes it harder to use the wrong hashing method :) +**\** and enables slightly more efficient hash-to-point operations under some constructions +**\** Anyway, a new preprint (IACR/944) discusses a new proving system for more general constraint systems +**\** And there will be a forthcoming preprint with a proving system on pairing groups, which simplifies cleanly to non-pairing groups too +**\** I've been looking over that one, since the authors graciously provided an advance copy +**\** What will be interesting is whether the Omniring prover relations can be efficiently moved into a more general proving system +**\** Making it easier (in theory) to do future changes +**\** Could you comment on the computational complexity when you simplify the proving system to a non-pairing group? +**\** Eventually =p +**\** I've only just begun working through that paper +**\** FWIW I'm told the preprint is quite imminent +**\** Ahh alright, any idea when it will be released? +**\** ^^ +**\** Oh and suraeNoether: the primary purpose of 5707 is to speed up MLSAG by removing redundant operations... this led to simplifications of the available hashing operations as a side effect +**\** thanks for correcting that! i didn't realize the larger scope (just started going through it) +**\** and at that point it seemed like a good idea to remove the brittle `hashToPointSimple` and put it directly into the unit test that enables verification of how `H` was derived +**\** There are two commits: the second commit moves the hash stuff around +**\** the first commit alters the MLSAG code +**\** gotcha +**\** All righty +**\** Does anyone else wish to share interesting research work? +**\** :/ if I were that smart, sure +**\** Don't underestimate yourself! +**\** While we're at it, we can also do GENERAL QUESTIONS for anyone +**\** well, I did read a recent paper on hormesis as it relates to beetles. +**\** lol +**\** my skills are not going to be helpful here :P +**\** oh, you just reminded me of that stream of tweets from Sarah Jamie Lewis yesterday, about ants and alarm pheromones +**\** Regarding CLSAG, the plan is to submit to several relevant conferences/journals (in sequence) and hope for acceptance +**\** the relevance was to illustrating how localized decision making can be gamed / subverted +**\** It falls into an awkward spot: it's a neat improvement on earlier work with good security model/proofs, but isn't profoundly new +**\** And unfortunately you can't do simultaneous submissions :/ +**\** (and thus an argument why you need global consensus) +**\** The FC deadline is in September, with notification by November 15 +**\** lots of stuff isn't profoundly new, but the imporvement still is worth talking about +**\** Yeah, but that's tough for publication +**\** maybe different forums then. heck, chip manufacturers give big presentations on ~5-10% gains +**\** Hence doing a fair bit of rewriting for better context +**\** cool. yes, expanding the scope of applicability is also a good angle +**\** and page limits (grumble grumble stupid wide margins) +**\** Aaaaanyway +**\** Perhaps on to ACTION ITEMS +**\** I have several, and I don't expect to complete them all this week +**\** CLSAG revisions, in preparation for submission +**\** My doctoral adviser always recommended putting down a paper for a week after your revisions, so you can revisit it with fresh eyes before submission +**\** Second is a better understanding of the reduction of this forthcoming proving system to non-pairing groups +**\** Third is going over suraeNoether's completed matching code +**\** Since suraeNoether had to step away for a few minutes, I assume his action items are applications of his test-passing matching code, and preparation of the thring signature paper for its submission (he can correct me later) +**\** Any last comments or questions or information from anyone? +**\** OK, we can adjourn! Thanks to everyone for joining in +**\** Logs will be posted shortly to the agenda issue diff --git a/_posts/2019-08-31-logs-for-the-Community-meeting-held-on-2019-08-31.md b/_posts/2019-08-31-logs-for-the-Community-meeting-held-on-2019-08-31.md new file mode 100644 index 00000000..5ad2c3af --- /dev/null +++ b/_posts/2019-08-31-logs-for-the-Community-meeting-held-on-2019-08-31.md @@ -0,0 +1,190 @@ +--- +layout: post +title: Logs for the Community Meeting Held on 2019-08-31 +summary: Community highlights, CCS updates, Workgroup report, Action Items, and miscellaneous +tags: [dev diaries, community, crypto] +author: el00ruobuob / SamsungGalaxyPlayer +--- + +# Logs + + +**\** 0. Introduction +**\** We would like to welcome everyone to this Monero Community Workgroup Meeting! +**\** Link to agenda on GitHub: https://github.com/monero-project/meta/issues/387 +**\** Monero Community meetings are a discussion place for anything going on in the Monero Community, including other Monero workgroups. We use meetings to encourage the community to share ideas and provide support. +**\** 1. Greetings +**\** Hi folks +**\** Hola +**\** thanks for joining +**\** 2. Community highlights +**\** See Monero weekly highlights at https://revuo-monero.com/ +**\** I was mostly off this week at the BTC2019 conference. I spoke about the dangers of transparency and the need for mandatory privacy in decentralized cryptocurrencies. I think it went well, and I can request a copy of my video recordings +**\** I used an activity which went quite well: +**\** I gave each person a notecard, which sorta represented an output. Then I asked people to trade cards, writing a record of the "transactions" on the card. Then I asked for a volunteer to be "suspicious" and finally debriefed by asking who accepted the "tainted" cards +**\** You should be able to see how it went in the recording, which I will hopefully receive soon +**\** Does anyone have community (non-workgroup) updates to share? +**\** Sorry. IRC issues. Matrix coming through? +**\** Somebody is finally working on an integration Bisq-Monero, should be ready in some weeks according to the guy. See https://github.com/bisq-network/proposals/issues/110 +**\** DiegorehrarSalaz: yes I see you now +**\** has niyid done any Monero work before? +**\** yep, been following ErCiccione, very cool. +**\** sgp\_: not that i'm aware of +**\** kinghat: cool indeed. Monero and bisq are a perfect match +**\** Anything else worthy of mention before proceeding? Thanks for sharing +**\** 3. CCS updates +**\** ErCiccione posted a new idea: +**\** “ErCiccione: Installation and configuration of Weblate, the new localization platform” https://repo.getmonero.org/monero-project/ccs-proposals/merge\_requests/94 +**\** thanks for being here ErCiccione to discuss it +**\** :) +**\** it's the proposal i made some time ago during a community meeting (after a dedicated localization workgroup meeting). Now weblate is basically ready. I only need a merged pr then we will start with the testing +**\** within the localization workgroup, after that will be ready for anybody to use. +**\** we will use it to translate next release, that's sure +**\** (unless something crazy happens obviously :P) +**\** thanks a lot to the people who already submitted their support. If anybody have questions i'm happy to answer +**\** hey, all +**\** I have no been able to voice my support on GitLab for ErCiccione's proposal so I am doing so here +**\** thank you nioc :) +**\** looks like a reasonable direction to me +**\** I'm going to take the silence as general agreement :) +**\** All other proposals previously in funding required are now funded :D +**\** Any final CCS comments before we move on to another section? +**\** 4. Workgroup report +**\** a. Daemon/CLI workgroup +**\** vtnerd’s Tor/i2p noise PR was recently merged +**\** moneromooo is back from vacation, and many miscellaneous bug fixes and improvements have been made since last meeting +**\** any other dev updates? +**\** b. Localization workgroup +**\** I received a full Chinese-translated copy of Mastering Monero. We’re discussing internally on how we would like to proceed with it. We want to make it available, but we need to work out the terms. +**\** We're considering options that will make PDFs available for free, but we need to determine how to handle the paid sales +**\** isn't the book already available for free? +**\** We also need to review the translation to assess the quality +**\** ErCiccione: the English version is yes +**\** what's the problem with publishing the translated version? the license allows it right? +**\** the license doesn't allow derivatives +**\** since we have the license, we can grant exceptions. but I just need to make sure everyone who contributed is ok with that +**\** got it. I think make it freely translatable is extremely important +**\** so, i hope it will happen :) +**\** we're working on it :) +**\** c. GUI workgroup +**\** dsc\_ has been working on the wallet i2p integration. It has been decided for now that the wallet will only support broadcasting transactions over i2p, not full sync. This will not impact most users' privacy a lot. The broadcast is the most important part +**\** dsc\_: does it allow i2p connections when using a remote node? +**\** I don't recall if a decision was made there yet +**\** dsc\_ mentioned earlier he wouldn't make it for this meeting +**\** dsc is afk as far as I know, but initially it will only be for tx broadcast as far as I can see +**\** oh yes, I'll need to follow up later +**\** beyond the networking settings, the design is being simplified, while adding new features including sending to multiple recipients +**\** d. Monero Research Lab +**\** I think that is a good way to put it :) +**\** Sarang recently posted his monthly update: https://www.reddit.com/r/Monero/comments/cx3gxp/august\_monthly\_report\_from\_sarang\_noether/ +**\** Surae has been working on matching and churning analysis. There has been some development progress. He finally has a working model to play with +**\** stop by the meeting Monday in #monero-research-lab to learn more and ask questions +**\** before open ideas time, I want to test out a new section on the fly: +**\** 5. Action Items +**\** In this section, please outline some of the tasks you would like to work on before the next meeting +**\** Here's mine for example: +**\** 1. work on the networking press release explaining what happened to Kovri and documenting the progress of i2p-zero and tini2p 2. wrap up the StackExchange moderator election 3. publish the conference talk recording I gave yesterday +**\** would anyone else like to share? +**\** cool +**\** i'm making some very needed changes and updates to the website, don't know what will be new for next update but i will write a post on reddit. +**\** some of the MR still need to be reviewed, so please take a look at https://repo.getmonero.org/monero-project/monero-site/merge\_requests +**\** i also want to introduce a labelling system i had in mind to prioritize issues. +**\** oh, since we are all here, would be ok for everybody if the "meeting logs" link of the website shows all meting log and not just dev meetings? +**\** imo yes +**\** come on, someone else has a list of things they want to work on :) +**\** Busy. Sorry. :( +**\** Will come back after meeting for logs and action item. +**\** ok, we have 2, maybe 3 people who work on stuff :p +**\** we can move on to open ideas time +**\** 6. Open ideas time +**\** It’s open ideas time! Feel free to propose your ideas to this discussion group, and feel free to comment on others’ ideas. If you disagree with the idea, please reply with constructive criticism. Thank you! +**\** I watched a talk about customer support at the conference, and it reminded me that we have been kinda trying to get one started for some time to supplement r/monerosupport and #monero-support +**\** there are only 3 accounts in #monero-support right now, which is a testament to the fact no one uses it +**\** having a training process for volunteers to provide live support could be a great way for people to get more involved. It would teach them the main pain points people have, and it would allow them to become even more familiar with Monero and how people use it +**\** the infrastructure is something I need to talk about with Diego on though, but I'd like to keep working on this project +**\** that's my idea. does anyone have others? +**\** can we discuss konferenco 2019 (europe)? +**\** sure +**\** i know there was discussions at DefCon surrounding holding it in conjunction with RIAT +**\** but i haven't heard anything, and was wondering if anybody else had. As it is something that will need to start planning at some point +**\** Did I miss it +**\** I have not heard much in that regard. But I think that hosting it at a university makes a LOT of sense +**\** was that their plan? +**\** I don't know +**\** anyway, i wanted to just say (as i mentioned potentially helping with organisation) Provenance Events were asking if there was an update from the community with regards to what they thought +**\** keep it cheap +**\** so i guess i wanted to say that the offer from Provenence is still there. but i thnk that RIAT is a better first option (provided they are still interested) +**\** OK I'm caught up +**\** Hey guys, sorry for the late entrance. +**\** but as surae nor anybody from RIAT is here, i guess we can't discuss much right now +**\** Ive got a few items to discuss +**\** that's all from me +**\** midipoet: want to make a list of student cryptocurrency clubs in Europe? They are our best "in" to the area and would know about planning, booking rooms, etc +**\** First would be the recent rule change on /r/Monero. Minor, but should be brought up here for logging purposes. +**\** Rule 6 was modified from disallowing downvotes, to making people self-identify if they have a conflict of interest on a particular product or service +**\** Additionally, I discovered new and old reddit have discrete rulesets, and the rules between the two versions were misordered. I imagine this led to some confusion. I fixed that up, the two should show the same rulesets now. +**\** Let's see what else +**\** Oh, the community has a minecraft server we've been hanging/chatting on. That's been cool. I think this is the right place to mention it. +**\** oh that's pretty cool. I only like to play in creative though :/ +**\** I like building things +**\** I can get you all the materials you need :D +**\** I strip mine +**\** Anyways +**\** Uhm what else +**\** midipoet: here is an example for the US: https://medium.com/michiganfintech/the-15-us-student-organizations-leading-fintech-movements-at-their-universities-fa2543cdcbd8 +**\** Oh, xmrtrader had a rule change too +**\** sgp\_: yes, i think that a Uni might be a good idea. i don't think finding a host would be difficult, but i don't want to give go ahead for planning, if RIAT are serious about hosting, as they have their own venue +**\** Altcoin talk is no longer entirely banned +**\** You can speak about the top 20 now, just keep opinion out of it. Which has really been nice +**\** midipoet: their venue is a little small for a conference setting. Great for a meetup setting +**\** finally I can shill XLM +**\** sgp\_: ah, i haven't seen it. but they said they had a newer space. but i may be incorrect about this +**\** midipoet, sgp\_: RIAT is Vienna right? +**\** yes +**\** We're over, so leave any final thoughts that you would like added to the logs +**\** As capital of Austria it should be relatively easy to access, might want to check in advance though +**\** We preferably want a city that is directly accessible for Americans too +**\** sgp\_ thanks as always for hosting, you do a fantastic job. +**\** +1 +**\** needmonero90: How many people are on the server? +**\** "for the record, I think needmonero90 is ugly" :) +**\** :'( +**\** dEBRUYNE: yes, at the moment it seems to be either Vienna (RIAT), or Dublin (Provenance Events) +**\** 6 I think that you would know +**\** Me included +**\** So far +**\** Make that 7 when lh joins today +**\** Vienna in summer should be decent weather too I guess +**\** Perhaps we should add a location near the sea though? May be more attractive for people +**\** dEBRUYNE join us!!! +**\ \** 6 I think that you would know \<= How would I know? +**\** :D +**\** :-P\* +**\** sgp too +**\** And midipoet +**\** And erciccione +**\** It's just to chill and have fun. +**\** Which we don't do enough of. +**\** minecraft? +**\** Yes. +**\** Yes +**\** I will do some digging this afternoon to see if there are any universities that could be open to hosting +**\** i would, but my laptop would fry +**\** can you get mincraft for Linux? +**\** We have a server sgp +**\** Oh wait +**\** Dude, the graphics don't require much. +**\** Dero +**\** sgp\_: I guess using an university should also significantly reduce the cost? +**\** It's literally blocks +**\** ErCiccione: I've played Minecraft on laptops >5 years old +**\** midipoet, yes. +**\** sgp\_: you can try - but i think the pressing issue is more who will organise - not where +**\** Dero = ignore me +**\** Screw autocorrect +**\** Idk how it got that out of what I typed +**\** 7. Confirm next meeting date/time +**\** The next community meeting will be in 2 weeks on 14 September at 17:00 UTC. The next Coffee Chat will be on 21 September at 16:00 UTC. +**\** sgp\_: i have a much older 2nd hand lenovo :P +**\** 8. Conclusion +**\** That’s all! Thanks for attending this Monero Community meeting, and we hope to see you on r/MoneroCommunity and #monero-community. Take care, and know that change starts with YOU. diff --git a/_posts/2019-09-02-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-09-02.md b/_posts/2019-09-02-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-09-02.md new file mode 100644 index 00000000..a86abe43 --- /dev/null +++ b/_posts/2019-09-02-logs-for-the-Monero-Research-Lab-meeting-held-on-2019-09-02.md @@ -0,0 +1,67 @@ +--- +layout: post +title: Logs for the Monero Research Lab Meeting Held on 2019-09-02 +summary: Surae work, Sarang work, and miscellaneous +tags: [dev diaries, community, crypto, research] +author: el00ruobuob / sarang +--- + +# Logs + +**\** Agenda: https://github.com/monero-project/meta/issues/388 +**\** (logs posted there afterward) +**\** good morning everyone +**\** GREETINGS +**\** Hola. +**\** Happy Labor Day to those celebrating it +**\** Happy Monday to all others +**\** Let's do our ROUNDTABLE +**\** suraeNoether: care to go first? +**\** sure. This past week i've been coding my economarkov chain simulating a fake Monero economy to apply matching to. this is slow-going, but steady progress. in addition to that, I started reading 3 separate papers for a new-ish idea... +**\** https://eprint.iacr.org/2016/583.pdf , https://www.microsoft.com/en-us/research/wp-content/uploads/2008/02/tcc2008.pdf , and https://link.springer.com/chapter/10.1007/3-540-36413-7\_20 +**\** the idea is new-ish to me but not the e-cash community, which is to demonstrate not a valid signature on a public message m, but \*knowledge of\* a valid signature on a public message m, without revealing the signature information like signer +**\** that 583 paper presents a trustless way of doing so with hash functions that can be described with a boolean circuit, and presents zk proofs of knowledge of RSA, DSA, and ECDSA signatures +**\** the idea is to replace ring signatures with something that is trustless and signer ambiguous +**\** Interesting +**\** that way, instead of saying "Either A, B, or C signed this m with key image J," the statement being proven is "I have seen a valid signature on m with key image J" +**\** Requires efficient trustless accumulator? +**\** coupling this together with a zk proof of membership in a strong dynamic accumulator allows for a "signature" scheme that does away with the explicit anonymity sets of ring signatures +**\** i think i'm onto a method for doing this with key images that are compatible with our current approaches +**\** Nice! +**\** but I need, probably, 2-3 additional pairs of eyes helping me out, so I'll be writing some stuff up and possibly starting a github issue for discussion on the matter +**\** roger +**\** other than that, i've been offline with family for a reunion + a 100-years-olds birthday party :D +**\** My monthly report details my recent activities, and is available now: https://repo.getmonero.org/monero-project/ccs-proposals/merge\_requests/77#note\_7105 +**\** Matching simulation review, updating papers, etc. +**\** Nothing earth-shattering over the past few days +**\** Very neat to hear about kenshamir[m]'s work on IACR/944 +**\** yes, i would like to hear more about that +**\** Is kenshamir[m] still here? +**\** Hi +**\** I’m here +**\** Anything specific you'd be interested to share about your recent work on proving systems? +**\** (no obligation to do so) +**\** I think the most notable contribution from 944 that can be applied to bulletproofs straight away is the improved inner product argument +**\** There are benchmarks which show that it gives significant improvements in verifier and prover efficiency +**\** Is there no meeting today? +**\** In the general circuit case, correct? +**\** (the meeting is happening now) +**\** Not the optimized range proof application AFAICT +**\** Yeah for 944s proving system it was the general case +**\** I think if that if we tailored the proof to be specific for 944s proving system, we may be able to get a more efficient rangeproof. This is only a conjecture though and I’m unsure of how to do it at the moment +**\** The general case remains extremely interesting +**\** since the range proofs are quite efficient +**\** For the general case asymptotically it is the same as the tailored bulletproofs rangeproofs from what I’ve seen +**\** Yeah I agree. It will be really interesting to see what optimisations can be made with this language +**\** \*Quadratic Equation Sat +**\** That’s all I’ve discovered so far from 944 +**\** Thanks kenshamir[m] +**\** Does anyone else have interesting work to share? +**\** Or, for that matter, general questions +**\** Righto! +**\** We can also move to ACTION ITEMS, if there's nothing else urgent to discuss +**\** my action items are short and simple. economarkov chain work, reading more on proofs of knowledge of valid signatures (which i'm considering calling redacted signatures), and my end of month work report. +**\** I will be doing some code review, continued work on proving systems, and ongoing work with suraeNoether on his recent updates to graph matching as needed +**\** Well, a short meeting today, but that's ok +**\** Anything final before we formally adjourn? +**\** Adjourned! Thanks to everyone for participating diff --git a/_posts/2019-09-05-logs-for-the-tini2p-dev-meeting-held-on-2019-09-05.md b/_posts/2019-09-05-logs-for-the-tini2p-dev-meeting-held-on-2019-09-05.md new file mode 100644 index 00000000..cdb42370 --- /dev/null +++ b/_posts/2019-09-05-logs-for-the-tini2p-dev-meeting-held-on-2019-09-05.md @@ -0,0 +1,94 @@ +--- +layout: post +title: Overview and Logs for the tini2p Dev Meeting Held on 2019-09-05 +summary: Current project status, Roadmap, Meta issues, and miscellaneous +tags: [dev diaries, i2p, crypto] +author: el00ruobuob / oneiric +--- + +# Logs + +**\** meeting time! +**\** 0: Greetings +**\** l +**\** :wave: +**\** :) +**\** 1: What's been done +**\** opened merge request for tunnels implementation: https://gitlab.com/tini2p/tini2p/merge\_requests/15 +**\** it's a large amount of work (around a month's worth), so I'm going to leave it up for a bit (few days) +**\** going to take a day away from that code, and come back to it for manual review +**\** Awesome! Is there anyone from i2p actively reviewing it? If not, I'll review with what little knowledge I have +**\** remember how I said "hopefully, no more major refactors", well so much for that. I overlooked some parts of OutboundEndpoint and InboundGateway processing, and had to refactor how I extract I2NP fragments from tunnel messages +**\** @DavidBurkett many thanks! I'm the only active reviewer, so any input from you is very welcome +**\** fresh eyes are always helpful +**\** :thumbsup: I'll take a look +**\** there are still some aspects of peer selection that remain, mostly around restrictions of peers from the same /16 IPv4, and any given peer only participating in ~33% of active tunnels +**\** not sure what layer of abstraction I should enforce those restrictions. right now, those restrictions make sense at the RouterContext layer for my impl, but TBD +**\** the RouterContext will ultimately be pulling peers from NetDB, and feeding them into the PoolManager +**\** so the work in that PR represents what I've been working since last meeting +**\** a lot of time was spent on peer profiling and tunnel testing +**\** and the refactors for the OutboundEndpoint sending a TunnelGateway message when the delivery is to another tunnel +**\** from the existing I2P docs, it's not very clear when the different tunnel delivery types are used (Local, Router, Tunnel) +**\** it took me implementing the things, and thinking about how the pieces fit together to really make sense of it +**\** basically, afaiu, Local is used by the InboundGateway to tell the InboundEndpoint, "this message is for you" +**\** Router is used by the OutboundGateway to tell the OutboundEndpoint (and maybe IBGW to IBEP) that the I2NP message should be directly delivered to a router +**\** e.g. for DatabaseStore and DatabaseLookup messages +**\** Tunnel delivery is used by the OutboundGateway to tell the OutboundEndpoint (and maybe IBGW to IBEP) that the I2NP message should be delivered to the InboundGateway of another tunnel +**\** Router and Tunnel don't make sense to me for inbound tunnels, unless some form of chaining is used. not clear that it ever is from the specs +**\** for example, if Alice sends an I2NP message through an outbound tunnel to the IBGW of another tunnel (with some indicator for chaining), and that IBGW uses Router or Tunnel delivery to tell the IBEP to deliver the I2NP message to the IBGW of yet another tunnel +**\** maybe that exists, but I've implemented IBGW only using Local delivery to send I2NP messages to the IBEP +**\** Local delivery is never used for outbound tunnels +**\** anyway, figuring all that out took a bit of time, and I may send spec diffs upstream to clarify the use of the different delivery types +**\** 2: What's next +**\** RouterContext +**\** and associated classes +**\** this set of classes will be the main brains tying everything together +**\** RouterContext will use the transport (NTCP2) to talk directly to other routers +**\** it will use an I2NP handler to either pass messages to the NetDB or Tunnel PoolManager for further processing +**\** similarly, resulting messages from NetDB and Tunnel processing will be returned to the RouterContext, and sent back out over NTCP2 to the appropriate router +**\** the RouterContext will also be the main owner of the router's RouterInfo +**\** LeaseSets for local InboundTunnels will also be compiled by the RouterContext, and stored in the NetDB +**\** setting a goal for myself to have the RouterContext finished (in a minimally working sense) by next Thursday (2019-09-12) +**\** with RouterContext finished/merged, I will tag a release candidate +**\** I will be implementing a Docker/container test network for integration/end-to-end testing, to ensure all the pieces work together +**\** I will also make changes to match the latest updates to ECIES-X25519, posted by zzz this past weekend +**\** ECIES-X25519 changes will also go into the alpha release candidate +**\** with RouterContext and ECIES-X25519 changes in place, tini2p will have an internally consistent implementation of I2P +**\** and I will tag the alpha release a week after the release candidate +**\** after alpha release, I will focus on ElGamal tunnel building, and integration tests with Java I2P and i2pd +**\** end-to-end sessions will still be tini2p-to-tini2p, but tunnel building should be possible through Java I2P and i2pd +**\** the Docker/container setup should be a nice testbed for inter-implementation testing, so hopefully it will be useful for other implementations as well +**\** TBD +**\** post-alpha release will also get some (a huge amount) of fuzz tests +**\** basically every class with a `deserialize`method or buffer input interface, will be getting a fuzz driver attached to it +**\** I may also be taking a small break from tini2p post-alpha release to preemptively prevent burnout +**\** these past nine months have been basically coding tini2p everyday, often 10-12+ hours a day +**\** 3: Questions/comments +**\** This project structure is really clean, and code easy to follow. Working on building now. You're doing great work +**\** aww :3 thanks @DavidBurkett that means a lot, very kind +**\** still needs a lot of work to be production-ready, but I'm doing my best to code well +**\** some of the structure is heavily influenced by portions of Java I2P, i2pd and ire. there are some really good bits in those codebases +**\** Well I'm just talking your cmake files, your handling of dependencies, etc. Very clean +**\** And I've seen i2pd. This is night and day better (although i2pd is pretty easy to work with) +**\** [edit] And I've seen i2pd. This is night and day better (although i2pd is also pretty easy to work with) +**\** i2pd has very different project goals and design. i2pd aims to be a one-stop-shop router, tini2p aims for use as an I2P library by other projects +**\** Ah, that makes sense +**\** I assumed i2pd was also meant to be used as a library +**\** the CMake and dependencies took influence from Kovri (and by extension i2pd) +**\** i2pd can also be used as a library +**\** what I mean is that i2pd contains an HTTP server, router console, bundled client, all-in-one. somewhat similar to Java I2P, though with less apps bundled in +**\** :thumbsup: Understood +**\** tini2p moves away from that singleton design, into something highly modular +**\** a future goal is to split tini2p up further, having common structures be its own repo, with separate core and client libs +**\** Makes sense. Yea, I pulled i2pd into Grin++ at one point, but I had to decouple a bunch of things to be able to just pull in what I want. It wasn't a straightforward task +**\** that's somewhat far down the line though, but it would support stuff like pluggable end-to-end and signing crypto +**\** That's awesome, you'll get there for sure. +**\** :) thank you +**\** alright, think that's about all for this meeting. unless you have something else @DavidBurkett? +**\** Nothing from me +**\** for sure +**\** 4: Next meeting +**\** 2019-09-19 18:00 UTC +**\** thanks all for attending (that means you @DavidBurkett ;) +**\** :smile: +**\** @tini2p\_gitlab stares intently at the gaffer, wondering if it feels