Merge pull request #118 from dEBRUYNE-1/master

Add logs for 7th dev meeting and Kovri meeting

_posts/2016-05-22-logs-for-the-kovri-dev-meeting-held-on-2016-05-22.md

+---
+layout: post
+title: Logs for the Kovri Dev Meeting Held on 2016-05-22
+summary: Review assigned open tickets: status, code ideas (if applicable), etc. and some additional meeting items
+tags: [dev diaries, i2p, crypto]
+author: dEBRUYNE / fluffypony
+---
+ 
+*May 22nd, 2016*
+ 
+# Logs
+ 
+**\<fluffypony>** ok starting the meeting relay for the Kovri meeting
+**\<meeting-bot>** [anonimal] Hello.
+**\<fluffypony>** anonimal: all yours :)
+**\<i2p-relay> {-anonimal}** From https://github.com/monero-project/kovri/issues/177
+**\<i2p-relay> {-anonimal}** Proposed meeting items:
+**\<i2p-relay> {-anonimal}** 17:00 (UTC)
+**\<i2p-relay> {-anonimal}** 1. Review assigned open tickets: status, code ideas (if applicable), etc.
+**\<i2p-relay> {-anonimal}** 2. Any additional meeting items
+**\<i2p-relay> {-anonimal}** 3. Confirm next meeting date/time
+**\<i2p-relay> {-anonimal}** Starting with 1., as discussed in private with fluffypony, let's tackle https://github.com/monero-project/kovri/issues/assigned/fluffypony
+**\<fluffypony>** hokay - should we do them one at a time ?
+**\<meeting-bot> [anonimal]** Sure, #105.
+**\<fluffypony>** sec, just opening it up
+**\<meeting-bot> [anonimal]** I'm more curious about status updates and if we'll pursue some of these ideas.
+**\<fluffypony>** ok 107
+**\<fluffypony>** I asked dEBRUYNE and the rest of the social media guys about that in January last
+**\<fluffypony>** dEBRUYNE: have you guys looked at that at all ?
+**\<dEBRUYNE>** I think xmrpromotions was handling that
+**\<meeting-bot> [anonimal]** JFTR: s/107/105/
+**\<dEBRUYNE>** I honestly cannot remember you asking me :-P
+**\* fluffypony** has the IRC logs to prove it :-P
+**\<dEBRUYNE>** regardless, I think xmrpromotions was handling most of that :-P
+**\<fluffypony>** ok - xmrpromotions, did you have a chance to look at GNU Social ?
+**\<ArticMine>** I am looking at GNU social right now
+**\<xmrpromotions>** I am sorry but I have not
+**\<meeting-bot> [anonimal]** Can I ask everone, candidly, what they think of the idea?
+**\<meeting-bot> [anonimal]** Is it something worth pursuing?
+**\<ArticMine>** My initial instinct is yes
+**\<fluffypony>** tbh I had hardly heard about GNU Social till you brought it up
+**\<xmrpromotions>** Are there more details I can read about it? https://github.com/monero-project/kovri/issues/105
+**\<fluffypony>** but I think in terms of providing a more freedom-friendly social presence it's advantageous
+**\<fluffypony>** plus if we can spend the energy maintaining a Facebook page we can definitely justify this... :-P
+**\<ArticMine>** Way better than a Facebook page
+**\<ArticMine>** There are many who dislike the corporate centralization of Facebook in social media
+**\<meeting-bot> [anonimal]** xmrpromotions: A great example of a working instance is https://quitter.se/
+**\<__uguu__>** facebook is currently actively banning users that talk about the censorship too so...
+**\<meeting-bot> [anonimal]** xmrpromortions: For technical details, https://gnu.io/social/
+**\<meeting-bot> [anonimal]** lol, sorry, not auto-completion here
+**\<meeting-bot> [anonimal]** Yes, recent news items re: censorship just get crazier and crazier.
+**\<xmrpromotions>** Thank you I will read the details and be ready to comment later. It is too early for me to commit to anything quite yet
+**\<meeting-bot> [anonimal]** And the social monopolies are finally showing their true colors.
+**\<meeting-bot> [anonimal]** Ok, so #105 is on hold pending xmrpromotions' review?
+**\<fluffypony>** yup
+**\<meeting-bot> [anonimal]** Ok, next ticket.
+**\<fluffypony>** ok
+**\<meeting-bot> [anonimal]** #46
+**\<meeting-bot> [anonimal]** The Kovri website.
+**\<fluffypony>** #46 - does anyone have any strong opinions on whether it should be a page on the Monero website, or a separate site that matches the Monero site's look and feel (maybe with different colours), or a completely unrelated site ?
+**\<fluffypony>** anonimal: and your input on this would be appreciated too
+**\<fluffypony>** I think the relay is wonky
+**\<meeting-bot> [anonimal]** What's the time-cost in terms of managing two sites?
+**\<meeting-bot> [anonimal]** Yes, missed almost everything it looks like.
+**\<fluffypony>** anonimal: it's mostly just the initial work, after that I mostly go hands-off and let the community run with the content
+**\<meeting-bot> [anonimal]** Can anyone read this?
+**\<meeting-bot> [anonimal]** Ok, so could we start small with a page on the website, or maybe subdomain/ and if things get bigger move onto another site?
+**\<fluffypony>** that would be my recommendation
+**\<fluffypony>** we start with a sub-section on the Monero site
+**\<fluffypony>** and forward the kovri site through to it
+**\<fluffypony>** if we feel the need later on we can create a separate site on its own
+**\<meeting-bot> [anonimal]** Ok, sounds good to me. Anyone else?
+**\<xmrpromotions>** Of the three options mentioned a separate site that matches the Monero site's look and feel may help draw a wider audience than a page on the Monero site while at the same time anyone who visits the Kovri page knows that Monero is associated with it
+**\<xmrpromotions>** It seems like a judgement call to me. Either plan sounds reasonable
+**\<fluffypony>** restarting meeting bot
+**\<fluffypony>** in fact, if you want to write up some content for me I'll do it on the plane on Tuesday
+**\<fluffypony>** in fact, I can probably take most of it from the readme
+**\<fluffypony>** in fact, if I say in fact again I'll summon the in-fact-bot
+**\<meeting-bot> [anonimal]** Ok, ideas for content? I can blabber but ideas are welcome.
+**\<meeting-bot> [anonimal]** ping in-fact-bot
+**\<xmrpromotions>** Any thoughts on creating a stackexchange proposal for I2P? Tor has a page now https://area51.stackexchange.com/proposals/56447/tor and we should be able to reach the commitment stage quickly with the same supporters behind the Monero proposal?
+**\<fluffypony>** xmrpromotions: we'd have to run it past zzz, at the very least
+**\<meeting-bot> [fluffypony]** zzz ^^
+**\<xmrpromotions>** sorry for off topic idea. I can table it for later if appropriate
+**\<fluffypony> no I think it's an excellent idea, if the i2p community at large is interested then now is definitely the time
+**\<meeting-bot> [anonimal]** From what I've seen, alot of great ideas come and go through #i2p-dev but it always comes down to resources.
+**\<meeting-bot> [anonimal]** I think we'd all love that but someone will have to take the initiative.
+**\<xmrpromotions>** I will take the initiative on that
+**\<meeting-bot> [anonimal]** AFAICT all i2p-related dev (including Kovri) is in a bit of a dry spell so, priorities.
+**\<meeting-bot> [anonimal]** I like the idea though.
+**\<fluffypony>** anonimal: the advantage is that we can basically get everyone who's committed to the Monero proposal to also back an i2p proposal
+**\<fluffypony>** but now is the time to do so
+**\<fluffypony>** whilst everyone's excited
+**\<meeting-bot> [anonimal]** Ok, so what's the next step?
+**\<xmrpromotions>** If the I2P communty supports it. As fluffypony said now is the time as the synergy will help both I2P and Monero proposals pass faster for REP related reasons
+**\<fluffypony>** so basically next step on the website is let's get a bit of content and I'll put it together on the plane on Tuesday
+**\<fluffypony>** next step on the StackExchange proposal is to wait for feedback from zzz
+**\<xmrpromotions>** sounds good. I wont act until I hear confirmation that zzz is ready to proceed
+**\<meeting-bot> [anonimal]** I dropped a line in #i2p-dev.
+**\<meeting-bot> [anonimal]** We'll see who bites.
+**\<meeting-bot> [anonimal]** Ok, so #46: 1) create content 2) On Tuesday, fluffypony will put something together 3) ETA after that?
+**\<fluffypony>** ok next ticket ?
+**\<fluffypony>** oh
+**\<fluffypony>** once it's pushed to the repo it goes live
+**\<fluffypony>** there's no ETA beyond that
+**\<fluffypony>** or no steps beyond pulling it and rebuilding the Jekyll site
+**\<meeting-bot> [anonimal]** Ok great, I'll paste a note in ticket.
+**\<meeting-bot> [anonimal]** Moving on, #43.
+**\<fluffypony>** ok - can we just use the Monero addresses, or do we want separate addresses?
+**\<meeting-bot> [anonimal]** I'm fine with Monero addresses.
+**\<fluffypony>** ok then they're avialable here, anonimal: http://donate.getmonero.org
+**\<fluffypony>** *available
+**\<meeting-bot> [anonimal]** Ok. Also, I can apply for FFS when needed or include my address somewhere or we can simply put a note in README to donate to either. Sound fair?
+**\<meeting-bot> [anonimal]** Or no?
+**\<othe>** ffs is prolly more efficient
+**\<fluffypony>** FFS is better than direct donations
+**\<fluffypony>** and it's generally more trustworthy because you raise funds for a specific piece of work, and then get paid out on milestones
+**\<meeting-bot> [anonimal]** Ok, we should put a note in README directing to FFS and donation page or just FFS?
+**\<fluffypony>** the readme just needs the donation page
+**\<fluffypony>** if we get large donations we redistribute them to active FFS proposals anyway
+**\<meeting-bot> [anonimal]** fluffypony: Ok, would you like to add that with your wording to the README? Or should I?
+**\<fluffypony>** anonimal: I have to pack tomorrow, and have a bunch of things to do, so if you could that would be appreciated
+**\<meeting-bot> [anonimal]** Ok
+**\<meeting-bot> [anonimal]** Moving on, #27
+**\<fluffypony>** ok #27 is going to have to hold for a week or two, we're busy moving email providers on getmonero.org so I'll sort it out on the new provider
+**\<meeting-bot> [anonimal]** Ok, I'll paste that note.
+**\<meeting-bot> [anonimal]** Onward to #20.
+**\<fluffypony>** 20 - I can try Coverity again, let's see if it gives me the same issue
+**\<fluffypony>** I've not heard from them despite opening tickets etc.
+**\<meeting-bot> [anonimal]** Links? Maybe I can comment/ping them too.
+**\<fluffypony>** anonimal: screenshots and process I followed is in that ticket
+**\<fluffypony>** issue I mean
+**\<meeting-bot> [anonimal]** Ok, well, it may come down to a phone call or two.
+**\<meeting-bot> [anonimal]** Is that something you'd be willing to do?
+**\<meeting-bot> [anonimal]** If not, we can skip the integration and try to do it manually.
+**\<fluffypony>** sure
+**\<meeting-bot> [anonimal]** Ok, next. #90 is not assigned to you but I remember you said you would assign yourself.
+**\<fluffypony>** one second just checking coverity
+**\<meeting-bot> [anonimal]** Is #90 still of interest?
+**\<fluffypony>** oooooh it works
+**\<fluffypony>** they must've fixed it and just not let us know
+**\<fluffypony>** anonimal: I'll PM you with coverity details
+**\<meeting-bot> [anonimal]** Fantastic!
+**\<meeting-bot> [anonimal]** Yay, great. This should be interesting.
+**\<gingeropolous>** will I break things if I create a bridge by connecting simplewallet to the daemon over an i2p tunnel?
+**\<fluffypony>** doubtful
+**\<meeting-bot>** [anonimal] fluffypony: #90?
+**\<fluffypony>** 90 will happen automagically when our GitLab mirror is up
+**\<fluffypony>** it'll have clearnet / Tor / i2p mirrors
+**\<meeting-bot> [anonimal]** Ok then. I've missed any discussions about that in the past, is there an ETA?
+**\<fluffypony>** not at the moment - it's one of those "on the list" things, I lack the time to knuckle down and do it
+**\<fluffypony>** we need a devops team :-P
+**\<meeting-bot> [anonimal]** Indeed. Ok, I'll add a note in ticket.
+**\<meeting-bot> [anonimal]** To whom should we assign #90 then?
+**\<fluffypony>** me
+**\<meeting-bot> [anonimal]** Ok, will do.
+**\<meeting-bot> [anonimal]** Yay, hour long of fluffypony tickets finally tackled! I'm glad we finally had the time. Any other comments them?
+**\<fluffypony>** none from my side
+**\<meeting-bot> [anonimal]** So, since this was the "fluffypony show" meeting, for time-sake I'll sum up my part of 1. with one line:
+**\<meeting-bot> [anonimal]** I'm not working on any tickets ATM but what will most likely be a new ticket soon as I'm working on Transports (mostly NTCP, little SSU): debugging/refactoring/c++14 refactoring where appropriate/some rewrite/some new code/documentation/improved logging
+**\<meeting-bot> [anonimal]** So, that's that for now, I'm sure more code talk can be at the next meeting.
+**\<meeting-bot> [anonimal]** Any additional meeting items (quickly)?
+**\<fluffypony>** nothing more from me
+**\<meeting-bot> [anonimal]** Re: StackExchange, what tl;dr can I give to #i2p-dev?
+**\<meeting-bot> [anonimal]** Aside from pointing a link to the meeting log.
+**\<meeting-bot> [anonimal]** (I've been out of the loop re: the initiative)
+**\<xmrpromotions>** Just say that we are willing to cross promote it to XMR community and expect it to reach the commitment stage fairly fasy
+**\<xmrpromotions>** fast
+**\<meeting-bot> [fluffypony]** just that it's a proposal to have an i2p-specific StackExchange area
+**\<meeting-bot> [anonimal]** So, what should we expect from them?
+**\<xmrpromotions>** from there the I2P and XMR communities can help each other ensure both site reach beta
+**\<hyc>** if kovri mtg is done, a comment on monero perf auto-convert. we know that for 32bit the conversion will fail due to a too-large txn when deleting one of the txs indices
+**\<xmrpromotions>** Hard for me to make an ETA on that. End result would be an I2P site similar to what Tor has now
+**\<hyc>** aside from that has anyone determined whether the convert errors were only in the old migrator code, or have they had problems with the newest code?
+**\<meeting-bot> [anonimal]** fluffypony: should we end meeting?
+**\<meeting-bot> [anonimal]** (or has it ended?)
+**\<meeting-bot> [fluffypony]** yes I think so
+**\<meeting-bot> [fluffypony]** I'll take the bot down
+**\<xmrpromotions>** We need I2P experts to appear during the proposal stage once created to ask good questions
+**\<xmrpromotions>** early questions attract a lot more votes and rise to the top, so quality matters
+**\<meeting-bot> [anonimal]** Ok, I'll chat in #monero-dev.
+**\<fluffypony>** hyc: there were two people who encountered issues after we merged into master, and I don't think they were testing anything pre-merge
+**\<fluffypony>** so newest code
+**\<hyc>** ok
+**\<i2p-relay> {-anonimal}** * thinking
+**\<i2p-relay> {-anonimal}** xmrpromotions: I can commit to both pages. How many I2P 'experts' would need to commit?
+**\<xmrpromotions>** well we need 40 good questions. each person can only ask 5
+**\<fluffypony>** well before commitment it's just the voting section
+**\<xmrpromotions>** Our initial 40 questions will help with SEO after launch
+**\<fluffypony>** where we need not only good questions asked, but also good questions have to get 10 votes each
+**\<xmrpromotions>** Yes I mean we need to create quality questions to vote on
+**\<xmrpromotions>** If someone wants to create a list of 40 great questions that would be perfect
+**\<i2p-relay>** {-anonimal} 40 great I2P questions, I could do that.
+**\<fluffypony>** they still have to post them though
+**\<xmrpromotions>** then we can divide it up and ask 5 each to make sure no silly questions gain a lot of votes early in the process
+**\<xmrpromotions>** we can find 8 people to post 5 questions each easily
+**\<fluffypony>** yup
+**\<fluffypony>** yeah, then we need a bunch of people to upvote :)
+**\<xmrpromotions>** I dont think voting will be a problem either. XMR users with no rep can be assigned to ask the questions... that will give them 5x10x5 rep (250 each)
+**\<xmrpromotions>** which will give them more than enough for the 200 rep area 51 cutoff for the SE 100 rep account association bonus
+**\<fluffypony>** strategyyyy
+**\<xmrpromotions>** 5q with 10 votes each will earn 5 rep per vote
+**\<i2p-relay> {-anonimal}** Ok, sounds great. Right now, I need to finish post-meeting wrap-up, take a break, get my brain in order and bbl.
+**\<fluffypony>** ok cool
+**\<xmrpromotions>** I will make a post in the getmonero forums. Maybe we can create and agree on a list of 40 questions there before we start
+**\<xmrpromotions>** thanks everyone. have a great weekend
+**\<fluffypony>** cheers
\ No newline at end of file

_posts/2016-05-22-overview-and-logs-for-the-dev-meeting-held-on-2016-05-22.md

+---
+layout: post
+title: Overview and Logs for the Dev Meeting Held on 2016-05-22
+summary: Clarification regarding documentation (i.e. Github wiki, consolidating information), bit on Ring CT, discussion of open PRs
+tags: [dev diaries, core, crypto]
+author: dEBRUYNE / fluffypony
+---
+
+*May 22nd, 2016*
+
+# Logs
+
+**\<fluffypony>** ok
+**\<fluffypony>** das meeting
+**\<ArticMine>** has started
+**\<fluffypony>** heh heh
+**\<xmrpromotions>** let the fun begin
+**\<fluffypony>** hyc, smooth, moneromooo, dEBRUYNE, gingeropolous, luigi1112, luigi1114, anyone I've missed
+**\<fluffypony>** hokay so
+**\<fluffypony>** first up: for those that haven't done so, please commit to the StackExchange proposal: http://area51.stackexchange.com/proposals/98617/monero
+**\<gingeropolous>** oooh i get pinged for dev meetings? :)
+**\<xmrpromotions>** and earn rep: https://forum.getmonero.org/20/general-discussion/2542/stack-exchange-commitment-requirements
+**\<fluffypony>** you're basically just committing to asking / answering a total of 10 questions over 3 months
+**\<fluffypony>** also it would be advantageous if you have over 200 rep on another StackExchange site, as xmrpromotions said
+**\<fluffypony>** I earned over 200 rep on bitcoin.stackexchange by answering like 4 questions, so it's not hard
+**\<fluffypony>** ok maybe like 6 questions, but still, not hard
+**\<fluffypony>** I think getting 200 committers in total will be easy, but having 100 committers with sufficient rep might be a little harder
+**\<fluffypony>** ok so
+**\<fluffypony>** PRs
+**\<fluffypony>** over the last couple of weeks we've merged a few PRs
+**\<fluffypony>** obviously
+**\<fluffypony>** the biggest one being the performance branch
+**\<fluffypony>** which was what warptangent was working on before he passed away
+**\<fluffypony>** and which was completed by hyc and everyone else
+**\* dEBRUYNE** pages tewinget, NoodleDoodle, ArticMine, othe
+**\<dEBRUYNE>** probably missed someone
+**\<fluffypony>** we are seeing some latent issues with auto-conversions, or that appear to be coming from the auto-conversion
+**\<fluffypony>** if users hit issues with that the fastest route is for them to sync from scratch
+**\<fluffypony>** iirc smooth has a broken conversion that we can use to analyse the issue
+**\<fluffypony>** 810 and 775 are dangling
+**\<fluffypony>** moneromooo: do you want those to stay open at present ?
+**\<moneromooo>** 810 might be cancelled, not sure.
+**\<fluffypony>** ok
+**\<moneromooo>** 775 is ready AFAIK.,
+**\<fluffypony>** ok will test it
+**\<fluffypony>** 818 is in a holding pattern pending some discussion; based on what shen has been doing lately my feeling is that we leave that till after RingCT is done
+**\<fluffypony>** on that note, RingCT seems to be pushing ahead quite nicely
+**\<fluffypony>** moneromooo: how's it looking from your side ?
+**\<moneromooo>** I'm not a cryptographer, so I got no clue really :P
+**\<fluffypony>** hah hah
+**\<moneromooo>** Once I figure out what goes where, it's just code after that.
+**\<fluffypony>** I know you're waiting for input from shen, but is it starting to make a bit of sense ?
+**\<moneromooo>** Though a lot of it I think
+**\<fluffypony>** kk
+**\<moneromooo>** Mot yet, but I've not spent a lot of time on it today (and yesterday I was out).
+**\<fluffypony>** alright
+**\<saddam>** moneromooo: I want to decrypt it manually so I can detect transactions sent to an integrated address of mine in the tx pool. Is there another way to do it?
+**\<fluffypony>** then next weekend I'll be at Bitcoin in Use in Arnhem, Netherlands
+**\<moneromooo>** How will you know it's an integrated address of yours in the first place ?
+**\<fluffypony>** and there will be several other Monero-er-ains there as well
+**\<fluffypony>** including some devs, most notably hyc
+**\<xmrpromotions>** a few ppl told me they want to meet you there:)
+**\<saddam>** oh it's the meeting, sorry. I'll wait to discuss that later moneromooo
+**\<fluffypony>** if anyone else is going to be there please let me know, we can do a Monero supper on the Saturday or something
+**\<fluffypony>** next up is a chat about documentation
+**\<fluffypony>** wallet42 has raised the idea of opening up the wiki on Github
+**\<xmrpromotions>** https://twitter.com/Falkvinge/status/731833882102910977 wants to meet you too
+**\<fluffypony>** the advantages of this is that it keeps the documentation close to the code
+**\<fluffypony>** and you can PR to the wiki or (I think) edit it inline
+**\<fluffypony>** xmrpromotions: oh neat
+**\<fluffypony>** in fact, the wiki creates a .wiki.git project that's invisible-ish
+**\<fluffypony>** so it makes syncing to GitLab easy (setting up a GitLab mirror is on the list of things to do)
+**\<fluffypony>** downside is that you can't edit it anonymously, although creating a GH account is trivial
+**\<fluffypony>** and the other downside is that we have tons of scattered documentation right now
+**\<fluffypony>** so my thinking is that the wiki is a good idea for documentation, BUT then we need to kill off all these other sources of info
+**\<dEBRUYNE>** ^ I don't mind putting part of it together
+**\<fluffypony>** so the Monero wikia has to be shuttered and that info moved over
+**\<ArticMine>** There is information all over BCT
+**\<dEBRUYNE>** we could put the guides from Moneroexamples over there too, but he doesn't necessarily have to shutdown his "source" imo
+**\<fluffypony>** same goes for dev guides etc. on the website - we should instead spend the effort writing a small Ruby plugin for the site that pulls in info from the wiki and formats it appropriately
+**\<fluffypony>** then the wiki becomes a primary source of info
+**\<fluffypony>** dEBRUYNE: yeah we could do the same thing with MoneroExamples
+**\<fluffypony>** just have a plugin that grabs it from his repos and formats it
+**\<fluffypony>** if anyone has an issue with this speak now or forever hold your peace
+**\<i2p-relay>** {-anonimal} Such consolidation sounds like a good idea.
+**\<dEBRUYNE>** fluffypony: Yeah that'd be fine too
+**\<dEBRUYNE>** as long as it consolidates the information to a central place it's fine
+**\<fluffypony>** I'll leave the question open till the start of the Kovri meeting, if nobody has major objections raised by then I'll consider the decision in favour of the GitHub wiki
+**\<ArticMine>** It is actually really needed We have info all over the place
+**\<fluffypony>** (we discussed this here a few days ago as well, and everyone generally seemed in favour of it)
+**\<fluffypony>** ArticMine: agreed
+**\<xmrpromotions>** I like the idea. Consolidation and simplification should hopefully encourage more people to contribute to it
+**\<fluffypony>** that's it from my side - next meeting will be on the 5th of May, same time
+**\<fluffypony>** if anyone has anything they want to discuss, or any other points they want to bring up, now's the time
+**\<fluffypony>** we have 20-ish minutes till the Kovri meeting
+**\<ArticMine>** I am looking at the fee structure
+**\<moneromooo>** Does anyone fancy hacking the pool code to check top hash ?
+**\<moneromooo>** It shold be fairly easy.
+**\<i2p-relay>** {-anonimal} fluffypony: s/May/June/
+**\<dEBRUYNE>** ArticMine: Is your research going to be put in a somewhat formal paper?
+**\<moneromooo>** er, s/hacking/amending/ for the peanut gallery.
+**\<ArticMine>** I'll start with a post on getmonero forum to get feedback ideas
+**\<ArticMine>** then one can develop a paper
+**\<dEBRUYNE>** all right
+**\<ArticMine>** Along the lined of my prior post on BCT regarding the adaptive block limit and penalty function. There are issues with respect to to many options in fees with RingCT
+**\<dEBRUYNE>** Is anyone willing to work on adding Monero to Bitsquare? Afaik it's only a few minor tweaks in the UI code, see issue here -> https://github.com/bitsquare/bitsquare/issues/392 | I might be able to try if I got some more time, emphasis on try though
+**\<fluffypony>** anonimal: thanks, lol
+**\<moneromooo>** To th UI of... ?
+**\<dEBRUYNE>** Bitsquare itself
+**\<dEBRUYNE>** It needs an additional field for the tx key
+**\<moneromooo>** Ah, I just saw the screenshot.
+**\<dEBRUYNE>** It's mainly to resolve disputes, if any occur
+**\<dEBRUYNE>** Btw fluffypony, any ETA on a new point release that includes the performance branch? Or are we awaiting any more PRs?
+**\<gingeropolous>** ArticMine, i look forward to the adaptive fee structure thread
+**\<luigi1112>** Oh high team
+**\<luigi1112>** Hi team too
+**\<gingeropolous>** hi luigi1112
+**\<fluffypony>** dEBRUYNE: more PRs, also gives us time to see if there are issues with auto-convert
+**\<fluffypony>** *more issues
+**\<xmrpromotions>** hi luigi1112
+**\<moneromooo>** What would I do if I wanted to try and repro that problem ? just pull, build, run ?
+**\<dEBRUYNE>** fluffypony: all right
+**\<gingeropolous>** im just curious... is 0mq gonna happen before ringCT? or ... or all at once?
+**\<fluffypony>** moneromooo: yeah
+**\<fluffypony>** gingeropolous: no clue
+**\<moneromooo>** I'm certainly doing nothing about it.
+**\<gingeropolous>** well there's months until the next hardfork... though i guess 0mq doesn't affect consensus protocols?
+**\<dEBRUYNE>** well it was either Ring CT or 0MQ for you afaik moneromooo and I think we decided last time that Ring CT was the priority (this is just to clarify to anyone reading)
+**\<fluffypony>** ok starting the meeting relay for the Kovri meeting
\ No newline at end of file