monero-project/monero-site
monero-project/monero-site
1
0
Fork 0
mirror of https://github.com/monero-project/monero-site.git synced 2024-12-23 12:09:49 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Merge pull request #487 from dEBRUYNE-1/master

Browse source 
Overview and Logs for the Dev Meeting Held on 2017-11-19 & Community Meeting (2017-11-25) & Monero Research Lab Meeting (2017-11-27)
This commit is contained in:
luigi1111 2017-12-04 09:52:00 -06:00 committed by GitHub
commit 479012a4c2
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
3 changed files with 756 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

265
_posts/2017-11-19-overview-and-logs-for-the-dev-meeting-held-on-2017-11-19.md Normal file
View file

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

311
_posts/2017-11-25-logs-for-the-Community-meeting-held-on-2017-11-25.md Normal file
View file

@ -0,0 +1,311 @@
---
layout: post
title: Logs for the Community Meeting Held on 2017-11-25
summary: Community highlights, Forum Funding System updates, RFC-HWALLET-1, Monero integrations, Malware Response Workgroup, Monero Coffee Chat, and miscellaneous
tags: [community, crypto]
author: dEBRUYNE / fluffypony
---
# Logs
**\<sgp>** We would like to welcome everyone to this Monero Community Meeting!
**\<sgp>** Link to agenda on GitHub: https://github.com/monero-project/meta/issues/137
**\<sgp>** Monero Community meetings are a discussion place for anything going on in the Monero Community. We use meetings to encourage the community to share ideas and provide support.
**\<sgp>** 1. Greetings
**\<rehrar>** What up kids?
**\<cryptochangement>** hey all!
**\<ErCiccione>** Hi!
**\<sgp>** Don't be shy :)
**\<msvb-lab>** Hello.
**\<sgp>** 2. Community highlights
**\<sgp>** For a great weekly summary, please read the Monero Observer: http://monero-observer.com/
**\<sgp>** 3. FFS updates
**\<sgp>** To those who haven't heard of the FFS before, it stands for the "Forum Funding System"
**\<sgp>** a. RFC-HWALLET-1 project progress
**\<sgp>** msvb-lab: do you have any updates you want to talk about?
**\<serhack>** hii :)
**\<msvb-lab>** Sorry, delay...
**\<msvb-lab>** We had a great Munich Monero meeting, where we mostly talked about forming a local group, regular meetings, the (nearby) Vienna event(s) of December, and the hardware team's efforts (with a few boards passed around.)
**\<msvb-lab>** As far as hardware goes, there's nothing organised to say. Lots of ordering of parts and waiting for them to arrive, some porting of designs to the EDA CAD application we're using.
**\<msvb-lab>** Laser cutter considerations, and so on.
**\<msvb-lab>** Any questions about hardware wallets?
**\<msvb-lab>** We have three designs being worked on in parallel, I could talk an hour but will spare the bore.
**\<ErCiccione>** the local group with regular meetings sounds great
**\<msvb-lab>** It's important for whoever would like to test a real device in their hands to sign up as a team member by clicking 'Contact the project' on the site:
**\<msvb-lab>** https://taiga.getmonero.org/project/michael-rfc-hwallet-1-implementation/
**\<msvb-lab>** ErCiccione: We had about twenty people there, and passed around artwork from Deborah.
**\<msvb-lab>** So we've definitely reached critical mass in Munich, Berlin was there long ago.
**\<serhack>** great, this is Monero community
**\<sgp>** msvb-lab: learning about these three designs would be a good read. If you want to work with me on writing something about these, I think the community would appreciate it
**\<cryptochangement>** yes we would :)
**\<serhack>** sgp: ;)
**\<msvb-lab>** A good place to put the informatino about the various device types is:
**\<msvb-lab>** https://taiga.getmonero.org/project/michael-rfc-hwallet-1-implementation/wiki/protos
**\<msvb-lab>** So one is called 'MCUDev' (now renamed to 'Monezor'), another is 'Breakneck', we need a name for the device that resembles Ledger Blue's design.
**\<msvb-lab>** ...and so on.
**\<serhack>** nice
**\<sgp>** Ok, good to know
**\<sgp>** Anything else on the hardware wallet front?
**\<msvb-lab>** Not from me.
**\<sgp>** b. Monero Integrations
**\<sgp>** cryptochangement, want to take it from here?
**\<cryptochangement>** serhack, you wanna go first?
**\<serhack>** yes, thanks
**\<cryptochangement>** ok cool
**\<serhack>** okay guys, the latest update before today was 1 month ago so more surprise are coming
**\<serhack>** first of all we have redesigned the payment box
**\<cryptochangement>** serhack: im actually pretty sure i talked about that last meeting ;)
**\<serhack>** second, a helpful security engineer have helped them in order to fix a potentially sql injection on payment id
**\<serhack>** (I mean on reddit, it seems only few people read community meeting cryptochangements)
**\<cryptochangement>** thats fair :p
**\<serhack>** https://imgur.com/a/MUV72
**\<serhack>** this is the new payment box
**\<serhack>** third, I have already contacted OpenBazaar team for implementing Monero
**\<serhack>** We should wait for multisig
**\<serhack>** that's all from me, go cryptochangements :)
**\<cryptochangement>** Okay so good news here
**\<cryptochangement>** Our second milestone, the Magento plugin is finished and ready to be used by merchants!
**\<cryptochangement>** Its all on GitHub here: https://github.com/monero-integrations/moneromagento
**\<sgp>** hooray!
**\<cryptochangement>** and here is a screenshot of the checkout: https://taiga.getmonero.org/media/attachments/6/0/a/5/72f4eb66138e7efd76c4abd6e7d52df16806cdc441788e61c3c8e20ec676/improvedmagento.png
**\<serhack>** yeah, cool announcement cryptochangements!!
**\<cryptochangement>** i should also mention that you can track a lot of our progress on taiga: https://taiga.getmonero.org/project/serhack-monero-integrations/
**\<rehrar>** Yay Taiga!!
**\<cryptochangement>** rehrar ive actually became rather fond of it :p
**\<cryptochangement>** thats pretty much all, unless there are any questions
**\<msvb-lab>** Which of these technologies resembles Bitpay most?
**\<msvb-lab>** There are ten repositories besides magento.
**\<serhack>** I think we should mark a thing
**\<msvb-lab>** So if I'm a vendor who wants to be able to 'Bitpay' with XMR, which github should I look at?
**\<serhack>** no offense to you msvb lab
**\<cryptochangement>** msvb-lab: they all have the same design/setup they are just for different cms
**\<serhack>** The goal of Monero integrations is removing the middleman
**\<msvb-lab>** Oh, that makes sense.
**\<cryptochangement>** globee is actually close to bitpay... because they actually use bitpay
**\<msvb-lab>** I thought there was a more complex architecture. So for three different vendors with three different CMSs, they will be served by referring to the correct implementation.
**\<msvb-lab>** That's quite good.
**\<serhack>** yeah, msvb-lab, different e-shops but they are using the same methods in order to accept monero
**\<sgp>** Exactly msvb-lab
**\<sgp>** They all provide the same functionality for different systems
**\<msvb-lab>** Is it still forbidden to talk about Globee (are there still secrets?)
**\<cryptochangement>** the main difference between us and globee is that we dont deal with fiat. all funds go directly to your wallet with no 3rd party
**\<msvb-lab>** Seems it would be relevant to this chapter of our meeting?
**\<serhack>** I don't know anything about the Globee secret project
**\<cryptochangement>** idk fluffy isnt here so you probably dont want to go spilling all of his secrets :p
**\<rehrar>** Globee can be talked about freely. The secret project being done by Globee is best kept under wraps for now.
**\<msvb-lab>** Okay, fine if the Globee deal or technology is still (partly) secret.
**\<msvb-lab>** rehrar: They probably need some time still to get the design done.
**\<sgp>** Any other updates cryptochangement/serhack? Can you remind me what integration is next?
**\<endogenic>** well, it's just not out yet, so please don't spread confidential info
**\<serhack>** the next is opencart
**\<cryptochangement>** next is opencart, which is in the works
**\<cryptochangement>** and now i think we can pass the baton
**\<sgp>** Cool
**\<serhack>** yes
**\<sgp>** Thanks cryptochangement and serhack
**\<serhack>** your welcome
**\<sgp>** Does anyone else have a FFS update?
**\<ErCiccione>** i wanted to say a couple of yhings
**\<sgp>** Go ahead ErCiccione
**\<endogenic>** also have a quick update
**\<endogenic>** after you ErCiccione
**\<ErCiccione>** i'll be quick endogenic
**\<endogenic>** no need, we have 30 mins :P
**\<ErCiccione>** I just wanted to say my FFS is in the process of being moved from Ideas to funding required, thanks to all the community for the support!
**\<sgp>** It's a very worthy proposal imo
**\<sgp>** From the other community feedback, it seems that other people think so too
**\<msvb-lab>** What is the URL?
**\<serhack>** serhack is going to donate
**\<msvb-lab>** I can't find it.
**\<ErCiccione>** 1 sec
**\<ErCiccione>** https://forum.getmonero.org/6/ideas/89232/coordinator-for-localization-group-various-maintenance
**\<ErCiccione>** it's still under ideas,but the pony said he is going to move it tonight/tomorrow
**\<rehrar>** I have something to say about FFS in general that the people here really need to be involved with. I'll speak after ErCiccione and endogenic
**\<ErCiccione>** thanks serhack :) and thanks sgp
**\<endogenic>** +1 rehrar
**\<sgp>** @ErCiccione is that all?
**\<sgp>** Go ahead endogenic
**\<ErCiccione>** no 1 sec
**\<ErCiccione>** also I reorganized the Taiga of the localization project, now is easier to add a translation (there also a quick guide "how to translate the GUI")
**\<ErCiccione>** https://taiga.getmonero.org/project/erciccione-monero-localization/
**\<ErCiccione>** Will integrate it soon with github
**\<ErCiccione>** that's all from me
**\<sgp>** Great thanks
**\<ErCiccione>** endogenic, your turn
**\<endogenic>** so i've been speaking with sgp and some members of the monero research lab about educational hackathons, and we think a corporate sponsored kovri hackathon could be brilliant (basically, you must build something using kovri plus one or more of the libraries from the sponsors)
**\<endogenic>** so I'd like to encourage everyone in the Monero community who is interested in getting involved with kovri or hackathons to get in touch with sgp and/or the noethers and chat with them about how you'd like to be involved
**\<endogenic>** doesn' have to be corp sponsored but it's probably a good idea
**\<endogenic>** they buy the food too :P
**\<endogenic>** and they supply venue, often
**\<endogenic>** unless it's done at a library or a school like NYU
**\<endogenic>** who has hosted such things before
**\<endogenic>** that is all
**\<sgp>** Ok endogenic. We can discuss this more during the open ideas time
**\<endogenic>** oops
**\<sgp>** Rehrar?
**\<sgp>** No worries :)
**\<rehrar>** Yay. My turn.
**\<serhack>** go rehrar, make this community cool
**\<rehrar>** Ok, as the Community workgroup, our job is several things (as you all may know). We want to make the community a good, educational, friendly place to be. And many of us head our own smaller workgroups and stuff.
**\<rehrar>** I think we need to add something onto the goals, specifically regarding the FFS
**\<rehrar>** The community workgroup needs to brainstorm ways that we can increase FFS giving involvement, and rely less on individuals that donate large sums.
**\<rehrar>** There was a large push on Surae's FFS, and it was awesome to see. It's slowed down a bit, which is totally fine, and I'm sure one final Reddit post would finish it up.
**\<rehrar>** We need to aim for getting community involvement with the FFS. Something like 0.1 XMR per person.
**\<rehrar>** We can find ways to incentivize if we'd like, but that's not the only way.
**\<rehrar>** We can discuss this in open ideas time, but building a culture of generosity and giving within the community should be a large priority, since the project relies on donations.
**\<rehrar>** end
**\<sgp>** Thanks rehrar
**\<endogenic>** what is the cause that sarang's proposal was quickly funded while surae's was not?
**\<rehrar>** a large donation
**\<cryptochangement>** 0.1 XMR per person would be a dream
**\<sgp>** I can make discussion groups for the hackathon and FFS projects in Mattermost
**\<endogenic>** rehrar: not quite my question
**\<endogenic>** why sarang and not surae?
**\<rehrar>** ah, ok then
**\<endogenic>** was there a difference in the quality of the proposals?
**\<sgp>** @endogenic it may have been as simple as sarang's being listed first in a Reddit post or something
**\<cryptochangement>** sgp thats what i was thinking
**\<serhack>** I have a little idea rehrar
**\<rehrar>** we can discuss it serhack. :)
**\<rehrar>** Meeting continue?
**\<endogenic>** rehrar: is your point up for further debate?
**\<sgp>** Yeah, I would like to make sure we finish the next point
**\<endogenic>** ok
**\<rehrar>** I'm thinking Open Ideas time of this meeting we can discuss further
**\<rehrar>** but of course we can debate it
**\<sgp>** I would like to discuss rehrar's ideas later in the meeting
**\<sgp>** 4. Discuss formation of Malware Response Group
**\<sgp>** Fluffypony and tuckerpreston asked me to reserve some time to discuss the response to malware and botnets.
**\<sgp>** Is anyone here to speak about this now?
**\<mattcode>** yeah
**\<sgp>** @mattcode great! Go ahead
**\<mattcode>** lots of angry administrators come into #monero-pools complaining that their servers have been compromised by a miner
**\<mattcode>** and they get even more upset when they're told that a monero address can't easily be traced back to an individual
**\<serhack>** oh, I didn't know anything about that, mattcode
**\<mattcode>** i don't really think that there's a solution to that
**\<mattcode>** and the other issue is websites getting hacked and web miners being silently inserted, which again there's nothing we can do about that
**\<serhack>** yes, it's like "someone stealed my monero. my email address pass is 1234"
**\<mattcode>** if monero didn't exist, the hacked servers and websites would just be used for spam/ddos/stealing passwords instead
**\<serhack>** +1 mattcode
**\<msvb-lab>** mattcode: And your or Fluffy's idea about a task force should serve as a support center, right?
**\<mattcode>** maybe there could be a page on the website explaining the harsh truth to administrators that have been hacked
**\<DaveyJones>** also isnt it a SysAdmins job to keep his security top of the state? :D
**\<sgp>** I think there's definitely room for a more formal response to web/server admins
**\<mattcode>** but a task force isn't too useful because they're just going to end up saying "sorry, there's nothing we can do to help. re-image your server and fix your vulnerabilities"
**\<sgp>** Ultimately it's up to them to fix/secure their stuff as we should say, but there could still be a page about it
**\<sgp>** Like "here's what you can do with the mining pool and address. Try contacting them. Otherwise, check your logs"
**\<rehrar>** I wonder if there's any way we can turn this into a net positive
**\<msvb-lab>** mattcode: So you believe having a group of support crew is not effective, but maybe a specially labeled web page right?
**\<serhack>** yep
**\<mattcode>** yeah I think that would be better. right now they end up in #monero-pools and just end up getting ignored or abused
**\<DaveyJones>** i think thats a solution
**\<serhack>** why should we spend efforts on websites when the default password is admin ?
**\<sgp>** It's good to at least have something serhack. Some of these attacks are more complex, or from an internal employee
**\<ErCiccione>** Honestly i don't like the idea of the page on the website, i prefer the idea of the team
**\<mattcode>** rehrar: the positive is that monero has a high network hashrate that doesn't dip when the price dips. i don't have any numbers but when ETN became (briefly) more profitable to mine than XMR, the XMR net hash barely dropped
**\<serhack>** yep, we should setup a tutorial/website
**\<rehrar>** I mean turning the third-party server getting hacked into a positive for the administrator. I mean obviously it's not a positive thing...
**\<rehrar>** but through education and stuff
**\<rehrar>** We can have ready-made resources (written, video, or otherwise) to hand off to people who experience this
**\<rehrar>** because this may apply to individual users too, not just servers
**\<rehrar>** that way, we are not taking responsibility for these people's security, but we are giving tools and resources that people can take hold of their own security
**\<sgp>** I can write something up as an example and see if it's a good draft. I'll link it in this channel
**\<serhack>** okay, good sgp
**\<sgp>** Mattcode, do you want to help me with this?
**\<mattcode>** most desktop antiviruses pick up the miners and delete them, so i don't think it's too much of an issue for desktop individuals
**\<ErCiccione>** yeah, much better this way
**\<sgp>** rehrar that's what I'm thinking
**\<rehrar>** The task force team can be working on this instead of on-demand support
**\<rehrar>** This is very in the spirit of The Monero Project, which is all about providing tools and resources for people to take back what's theirs
**\<sgp>** I just think on-demand support is overkill. It would literally tell people the info on the page we would make
**\<mattcode>** I don't think we should be writing things like cleanup guides, because all of the different pieces of malware and server configurations make that impossible.
**\<sgp>** Oh, you want to provide that level of support?
**\<mattcode>** also organisations usually have their own procedures for when things get compromised
**\<pigeons>** the support they are looking for is please pool, don't payout to this address etc
**\<rehrar>** lel
**\<pigeons>** yes
**\<rehrar>** they can redirect payment to me instead
**\<mattcode>** I think the best thing would just be explaining that it's not the Monero project, the pool operator or the miner developer that has hacked your server.
**\<sgp>** mattcode, are you happy with me making a Mattermost workgroup chat so that we can discuss this further after the meeting?
**\<pigeons>** yes help them waste less time
**\<mattcode>** sgp: sure
**\<sgp>** Great
**\<serhack>** +1 sgp
**\<sgp>** Anything else you want to discuss during the meeting?
**\<sgp>** We are going over today, sorry
**\<sgp>** 5. Monero Coffee Chat
**\<sgp>** The next Monero Coffee Chat will be next Saturday on 2 December https://github.com/monero-project/meta/issues/139
**\<sgp>** During the Coffee Chat, we will go through Taiga so that people become more aware and more familiar with it.
**\<sgp>** It would be nice if the website is refreshed before then so that the Mattermost/Taiga announcement gets published.
**\<sgp>** Beyond this, the format of the Monero Coffee Chat will be about the same. If anyone would like to participate, please send me a PM. Otherwise, you can always join us on YouTube.
**\<rehrar>** Twas lonely last time with just me and sgp and fp (for a bit)
**\<sgp>** Skipping open ideas time for now, but of course #monero-community can always function as open ideas time even outside meeting time
**\<sgp>** Yes, it was a bit lonely :)
**\<serhack>** okay, sgp
**\<sgp>** We need more volunteers
**\<sgp>** 7. Confirm next meeting date/time
**\<sgp>** The next meeting will two weeks from today on 9 December at 17:00 UTC.
**\<sgp>** 8. Conclusion
**\<sgp>** 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.
**\<sgp>** Now, we can continue conversations from endogenic, mattcode, and rehrar
**\<rehrar>** endogenic watchoo wanna debate?
**\<endogenic>** well so just about the kovri thing real quick
**\<endogenic>** i remember on the coffee open hours thing there was discussion about kovri needing a good testing ground
**\<endogenic>** less life or death than monero would be good. plus more exposure for kovri would be good
**\<endogenic>** as for the FFS thing…
**\<mattcode>** just to add onto the botnet thing, i don't think pool ops ever ban addresses after somebody has claimed that their server has been hacked. it would be too easy to fabricate. they only seem to ban big botnets, but only because they place a heavy load on the server :p
**\<endogenic>** people naturally won't donate to something they consciously think is bad…
**\<serhack>** +1
**\<endogenic>** and they tend to donate to things they feel are good for them
**\<endogenic>** even charity donation for example is thought to return to oneself
**\<sgp>** mattcode can you create an account on Mattermost please? https://mattermost.getmonero.org
**\<endogenic>** in monero, it's just supposed to be a little more concrete
**\<cryptochangement>** now that we are in open tiem, i should probably mention that i posted our FFS update to reddit too so people can see it there: https://www.reddit.com/r/Monero/comments/7fgl4o/monero_integrations_update_12/
**\<sgp>** #monero-vulne-response
**\<endogenic>** one thing at at time guys
**\<cryptochangement>** sgp: vulne or vuln?
**\<serhack>** vulne
**\<serhack>** on mattermost
**\<rehrar>** XD
**\<sgp>** vulne. It's only on MM now, not IRC
**\<endogenic>** so if people are not made to undrestand what a proposal is important
**\<endogenic>** how can you expect them to donate to it?
**\<sgp>** Sorry
**\<cryptochangement>** ah ok. i just thought vulne sounded funny ^\_^
**\<endogenic>** you guys seem to be talking about something else anyway… :P rehrar feel free to ping me
**\<cryptochangement>** sorry endogenic
**\<sgp>** You can discuss this now. I'll wait
**\<sgp>** @endogenic I also made #monero-hackathons on Mattermost
**\<sgp>** @rehrar on second thought, I think we should have the discussion about the FFS crowdfunding initiative here. Do we need another channel for this?
**\<ErCiccione>** sgp i think it would be better to talk about it here, much many possible inputs
**\<sgp>** It's important for the community to survive with small donations, rather than a few wealthy individuals
**\<sgp>** Of course, having a few people who can help out is both convenient and very generous
**\<sgp>** But if for some reason these people lost interest, the community should be able to raise significant money from many small donors
**\<ErCiccione>** i read somwhere the idea of a mining pool managed by the community, where a percent go to the FFS project. doesn't sound too crazy if there's somebody willing to manage everything
**\<msvb-lab>** ErCiccione: Don't forget promoting the Monero donation address, which could make the third leg of the tuple (many|wealthy|donation.)
**\<msvb-lab>** Like Kovri does at the bottom of their website.
**\<msvb-lab>** That could be instrumental for folks that generally appreciate Monero and would donate but don't hang out enough to stay informed.
**\<serhack>** a "donate now" popup box before downloading?
**\<sgp>** Most mining pools who donate do so to the Monero project itself
**\<sgp>** Which in turn often donates to FFS projects
**\<ErCiccione>** sgp sure, but with a pool you can give the choice to reserve part of your hashrate and decide to put it directly tu support ffs (maybe with subaddresses might be possible to choose the single ffs)
**\<sgp>** Perhaps
**\<ErCiccione>** msv-lab: true, but that is mostly everywhere (wallet, website, reddit ecc)
**\<sgp>** We could change how/when Monero asks for donations
**\<ErCiccione>** what happens if somebody makes a donation directly to the address of the FFS wallet with no payment id? because if it's possible to evenly distribute that amount to all the actives ffs, we could just spread that address if people doesn't care of the proposal itself, but would like to contribute
**\<ErCiccione>** an ipothetical 'community pool' could point to that address, distributing equally the mined moneros
**\<mattcode>** doesn't money from the general development fund make its way into FFS requests?
**\<ErCiccione>** mattcode: yes, sgp pointed that early, but with a pool you move that choice directly to whom is willing to donate (i mean to send the money directly to fund community's proposals)
**\<ErCiccione>** s/proposals/FFS
**\<monerobux>** ErCiccione meant to say: mattcode: yes, sgp pointed that early, but with a pool you move that choice directly to whom is willing to donate (i mean to send the money directly to fund community's FFS)
**\<ErCiccione>** so nice of you monerobux
**\<ErCiccione>** :)
**\<rehrar>** Sorry, out of the house atm. But we need to remember two factors. One, some people like to choose which proposals their XMR goes to. This ensures that Monero evolves in the way they desire.
**\<rehrar>** These people will not like the General Fund option, as the General Fund is managed by the Core Team to spend on whatever they see fit that benefits Monero (obviously coming to consensus within themselves)
**\<rehrar>** There are some people who prefer to choose things themselves, and not trust anyone, even the Core Team. And that's fine.
**\<rehrar>** We're not trying to get everyone to donate to EVERY proposal.
**\<rehrar>** We're trying to get people to donate to what they believe in.
**\<rehrar>** So if someone agrees with funding Surae and not myself, they need to have the freedom to not give to me without shame
**\<rehrar>** but the cultural ideal should be, if you believe in a proposal, you should seriously consider donating something small to it
**\<ErCiccione>** rehrar: yes, totally agree, that can be solved using subadresses instead of payment's id. could be even better, you would be able to choose the project to contribute to directly from the pool
**\<ErCiccione>** this is for me a good way to give also to people who cannot afford it, a way to donate, but require the use of subadresses, are they stable right now?

180
_posts/2017-11-27-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-11-27.md Normal file
View file

@ -0,0 +1,180 @@
---
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]
author: dEBRUYNE / fluffypony
---
# Logs
**\<suraeNoether>** anyway, agenda for the day: 1) Greetings, 2) Sarang's work 3) my work 4) open discussion. The new zksnark paper will presumably take up some of 4. :P
**\<suraeNoether>** 1) is done i guess. :\
**\<suraeNoether>** 2) Sarang want to bring us up to speed?
**\<sarang>** roger
**\<sarang>** I have working code for both linear and logarithmic bulletproofs that tests correctly
**\<sarang>** I'm finishing up a few small optimizations to reduce the curve op count
**\<suraeNoether>** nice
**\<sarang>** and then it'll be ready for C++
**\<sarang>** moneromooo already has the linear version up and running
**\<suraeNoether>** fantastic!
**\<sarang>** That's been my big project
**\<suraeNoether>** page 8 of the new zksnark paper talks about dot product proof protocols
**\<sarang>** orly
**\<sarang>** That's the big shiny toy of bulletproofs
**\<suraeNoether>** literally caught my eye
**\<suraeNoether>** or rather
**\<suraeNoether>** metaphorically? well
**\<suraeNoether>** anyway, my point is i have done nothing but skim the paper (in the past 10 minutes) and that popped out at me
**\<suraeNoether>** you have also been helping me on multisig, as well, don't discount that
**\<sarang>** I shan't
**\<suraeNoether>** anything else?
**\<suraeNoether>** gratz on getting it working
**\<sarang>** Thanks to everyone who offered support in the most recent fund drive
**\<sarang>** I remain humbled
**\<suraeNoether>** thank you, sarang! thanks again
**\* sarang** takes a small bow
**\<suraeNoether>** As for my work, I've been working on the multisig paper, which is intended to 1) present a formal model of our threshold ringct, and 2) show how our current implementation compares to that formal model. there are differences that i'm hunting down one by one
**\<suraeNoether>** JollyMort[m] has found several already, and we've been having discussions about it the past few days
**\<suraeNoether>** That has represented the vast majority of my time
**\<suraeNoether>** In addition to that, I believe I may have a problematic example case of SPECTRE. the original authors sweep my concern aside, but i wanted to bring it up and see if anyone had any thoughts
**\<sarang>** I'm intrigued
**\<suraeNoether>** if two transactions using the same input are relayed nearly simultaneously, they will find their way into two separate blocks. they will appear as conflicting transactions until the spectre algorithm arranges one block to precede the other
**\<suraeNoether>** or stay conflicting forever if spectre can never linearly order them
**\<suraeNoether>** this can happen with a simple example of a "mostly linear" blockchain, except with a single block in the chain replaced with a pair of blocks like a diamond shape:
**\<suraeNoether>** \_\_\_\/\\_\_\_
**\<suraeNoether>** \/
**\<suraeNoether>** something that looks like that
**\<suraeNoether>** then any transactions that conflict in the pair of non-linearly-ordered blocks will appear to conflict forever
**\<suraeNoether>** this allows a clumsy user who re-sends a transaction twice becuase he's foolish to lose his funds.
**\<sarang>** Can we back this up with a simulation?
**\<suraeNoether>** i mean, we could, but there's a solid chain of lemmas that lead to a theorem i can write up later if you like
**\<suraeNoether>** using the theorems about how rapidly sets in spectre get finalized
**\<sarang>** Even better
**\<sarang>** \*lemmata
**\<suraeNoether>** now, the spectre authors said "the only reason someone would relay two transactions like this is to attempt a double spend, so it's okay that the funds are lost."
**\<sarang>** lolwut
**\<suraeNoether>** well
**\<suraeNoether>** the idea is that htey are *two* transactions with valid signatures using the same input
**\<suraeNoether>** or rather, using at least one of the same inputs
**\<suraeNoether>** so by definition, it's a double spend
**\<suraeNoether>** and i can't really think of a scenario where someone would compute two signatures separately like that, then relay them nearly simultaneously like that... on accident
**\<suraeNoether>** BUT
**\<suraeNoether>** it's enough of a leap for me to be concerned
**\<suraeNoether>** moreover
**\<suraeNoether>** i'm not sure if that sort of "double spend implies money lost forever instead of "eventually one of the two spends is accepted."
**\<suraeNoether>** and what's really crazy
**\<suraeNoether>** is that if block arrival times are very fast, like 10/s as in the original spectre paper... this problem is solved *with high probability*
**\<suraeNoether>** so, that's where SPECTRE is sitting.
**\<suraeNoether>** and lastly, my viewkey proposal
**\<suraeNoether>** s/lost forever/lost forever" philosophy instead of...
**\<scoobybejesus>** I own address A, B, and C. I simultaneously send the same output as an input in txns A ->** B and A ->** C. Free coins? Or B and C each now have unspendable outputs?
**\<suraeNoether>** a miner would see two conflicting transactions, so neither would be considered valid
**\<suraeNoether>** and constructing another transaction later A->**D will also be considered invalid
**\<scoobybejesus>** Ah. Thanks.
**\<suraeNoether>** so until spectre re-orgs the block-DAG so that the transaction A->**B precedes A->**C or vice versa, it's locked forever
**\<gingeropolous>** right, i was wondering that... i though eventually it resolves to a bloclchain
**\<gingeropolous>** or blockchain
**\<suraeNoether>** actually, that's the problem: if block arrival rate is slow and you have a fork
**\<suraeNoether>** the next block to arrive will point to both blocks as parents
**\<sarang>** yeah
**\<suraeNoether>** and if all blocks from there on out point to that common child block, those two blocks will never be linearly ordered
**\<suraeNoether>** so, this would also be solved by simply telling people to try to avoid making more than 1 transaction per target block arrival rate *personally*
**\<suraeNoether>** otherwise they are burning their own money, in a sense
**\<sarang>** that's quite the kludge
**\<gingeropolous>** so dbl spends are punished... kinda
**\<suraeNoether>** gingeropolous: yes, it provides a strong incentive against making a double spend attack
**\<suraeNoether>** which is nice
**\<suraeNoether>** i just don't want to make it so that badly informed users of Monero don't accidentally burn their money
**\<gingeropolous>** i wonder if we could protocolize an incubate function, where a tx has to sit in the txpool for n blocks
**\<suraeNoether>** sarang it's not too much of a kludge, if our block arrival rate is 1/second or something
**\<sarang>** hmm
**\<suraeNoether>** gingeropolous: ooooh
**\<gingeropolous>** kind of a bitch because timestamping and all..
**\<suraeNoether>** it's worth thinking about though!
**\<suraeNoether>** that's a good idea
**\<suraeNoether>** okay, so does anyone else have anything they want to share about their work?
**\<sarang>** I could add that I've posted my monthly report: https://www.reddit.com/r/Monero/comments/7frn7i/november_monthly_report_from_sarang_noether/
**\<sarang>** Comments welcome
**\<suraeNoether>** Also, I'd like to thank the community for funding me as well
**\<suraeNoether>** It's astonishing
**\<suraeNoether>** In other announcements....
**\<suraeNoether>** rehrar is working on the next Monero Revuo
**\<suraeNoether>** I'm not sure what the publication timeline on that is supposed to be
**\<suraeNoether>** but it's the quarterly newsletter wherein he sort of interviews the teams at MRL in charge of various projects
**\<sarang>** Any other discussion items?
**\<suraeNoether>** he and Sarang and I are going to have a sit-down and talk about the direction MRL is heading. I am interested in writing up current standards for Monero, I know Sarang is also, and I want to start on that as soon as Multisig is done.
**\<sarang>** ah yes
**\<suraeNoether>** For each Monero standard, I also want to write up at least one proposal for replacing the standard in the case that the security of that standard is compromised
**\<suraeNoether>** I also want to compile arguments for and against replacing certain standards sooner rather than later, for example, our "nonstandard" hash function
**\<suraeNoether>** oh man, i should ping andytoshi too
**\<suraeNoether>** this includes our proof of work standard
**\<sarang>** That strikes me as our least-standard "thing"
**\<suraeNoether>** cryptonight has some value, but it's as homebrew as can be
**\<suraeNoether>** yeah
**\<suraeNoether>** i wouldn't mind putting up a portion of my funding for this period toward a Proof of Work contest for Monero's replacement proof of work scheme
**\<suraeNoether>** hmm
**\* iDunk** reaches for a pitchfork
**\<suraeNoether>** ?
**\<suraeNoether>** cryptonight has value because of asic resistance. i'm okay with asics if they are commoditized. i'm not married to cryptonight in any way
**\<suraeNoether>** i'm in a non-monogamous relationship with cryptonight
**\<suraeNoether>** ok, well
**\<suraeNoether>** anything else to discuss?
**\<dEBRUYNE>** <suraeNoether> i wouldn't mind putting up a portion of my funding for this period toward a Proof of Work contest for Monero's replacement proof of work scheme \<= I think othe already has some back up plans
**\<silur>** apparently V wants ringCT in EVM2
**\<dEBRUYNE>** You might want to talk to him about it
**\<suraeNoether>** othe are you around?
**\<othe>** Yes
**\<suraeNoether>** silur V = vitalik?
**\<silur>** yep
**\<suraeNoether>** othe you've been thinking about POW?
**\<othe>** Yea
**\<othe>** Slight changes we can implement will break all asics
**\<silur>** I introduced stringCT/ruffCT PoC code in our research channel hope it will go somewhere
**\<othe>** Trivial to implement in cpu and gpu
**\<suraeNoether>** oooh, that's fantastic! fluffypony sent me at least one recommendation for that a few weeks ago
**\<suraeNoether>** but i haven't had time to look into it
**\<othe>** Yeah that one is an example
**\<silur>** what is this new POW?
**\<suraeNoether>** ok, but you aren't talking about *replacing cryptonight* but modifying it
**\<suraeNoether>** silur othe has apparently been looking at the cryptonight code very closely and determining how to swap bits around or mess with the implementation to improve asic resistance without harming gpu or cpu performance
**\<othe>** Just modifying it randomly
**\<silur>** I thought cryptonight is asic resistant by design O.o
**\<othe>** Takes like 5 lines of code in gpu miner
**\<silur>** I knew that it's not like... cuckoo cycle hard but still
**\<othe>** Cuckoo is not hard at all
**\<suraeNoether>** yeah cuckoo isn't asic resistant at all
**\<suraeNoether>** i have a paper around here about it
**\<silur>** dayum
**\<suraeNoether>** silur cryptonight takes up L3 cache like crazy, so the asic resistance comes from forcing it through a bottleneck
**\<suraeNoether>** but you could still have an asic on the back end of the bottleneck
**\<othe>** There's really nothing asic resistant if u hsve money
**\<suraeNoether>** so if someone creatively designed a computer with a huge L3 cache or something like that...
**\<suraeNoether>** which normally you wouldn't have to worry about for something like SHA256
**\<suraeNoether>** then the asic is still technically possible, we're just... resistant to it
**\<suraeNoether>** because it requires novel computer architecture and design
**\<suraeNoether>** othe i'm very glad to hear you have been working on this
**\<suraeNoether>** ended the meeting a little too early, sarang. :\
**\<sarang>** I'm following along on the bus
**\<sarang>** The bus smells like ass today
**\<suraeNoether>** http://www.cs.cmu.edu/~dga/crypto/cuckoo/analysis.pdf
**\<othe>** Well i don't have a problem with asics but sth like shitmain has to be killed of when trying
**\<suraeNoether>** nope, that's not the paper i was looking at
**\<suraeNoether>** othe my primary concern is decentralization, whether it's through asic resistance or asic commoditization. the idea of cpu mining is great in some ways, but i like andytoshi's paper on the thermodynamic minimum *a whole lot.*
**\<suraeNoether>** like, his paper made me realize that proof-of-storage or something like that? the universal minimum will be determined by the speed of light
**\<suraeNoether>** so instead of commoditized hardware mining, you would see massive massive data centers all with fiber optic cables of *exactly the same length* to avoid time effects from light speed, etc etc
**\<suraeNoether>** so anyway
**\<unknownids>** this is probably useless info at this point as its all rumors, but https://rmc.one/ has said they are working on a cryptonight asic
**\<suraeNoether>** oh yes, that is the paper. :P http://www.cs.cmu.edu/~dga/crypto/cuckoo/analysis.pdf
**\<suraeNoether>** unknownids: eh, the minute they blow a million on taping out a few asics, we'll implement the first of othe's list of changes. :P they'll have to retape, best case scenario... and then we do it again...
**\<othe>** Rmc one are idiots but rwal companies might be
**\<suraeNoether>** it's easier for us to change the algo than it is for them to pump out asics
**\<suraeNoether>** tbh if i were in the asic business i wouldn't make a move without blessings and guidance from the developers of the coin
**\<unknownids>** good to know othe
**\<suraeNoether>** because they'll just change their code if they don't like what you are doing
**\<silur>** ^
**\<suraeNoether>** whoever is designing asics for monero are preparing to burn their fiat. but hey, they probably have fiat to burn
**\<suraeNoether>** joker.jpg
**\<suraeNoether>** ok guys
**\<suraeNoether>** i'll be back later today
**\<JollyMort[m]>** entrepreneurs will always find a way to get above others; be it ASIC or botnets or webminers; what's important is that there's no barrier to entry for new players so that nobody's position is forever assured