@@ -58,4 +58,4 @@
- {% include hostflag.html %}
\ No newline at end of file
+ {% include hostflag.html %}
diff --git a/_includes/header.html b/_includes/header.html
index 34280034..2c618299 100644
--- a/_includes/header.html
+++ b/_includes/header.html
@@ -61,6 +61,7 @@
User GuidesDeveloper GuidesVulnerability Response
+ Technical Specs
@@ -148,6 +149,7 @@
MoneropediaUser GuidesDeveloper Guides
+ Technical SpecsVulnerability Response
diff --git a/_layouts/post.html b/_layouts/post.html
index 56d09299..1235329a 100644
--- a/_layouts/post.html
+++ b/_layouts/post.html
@@ -28,7 +28,9 @@ layout: base
{{ page.title }}
-
{% t blog.author %}: {% if page.author %}{{page.author}}{% else %}{{site.author}}{% endif%}
+
{% t blog.author %}: {% if page.author %}{{page.author}}{% else %}{{site.author}}{% endif%}
+
{% t blog.date %} : {{ page.date }}
+
{{content}}
@@ -75,4 +77,4 @@ layout: base
-
\ No newline at end of file
+
diff --git a/_posts/2016-03-05-overview-and-logs-for-the-dev-meeting-held-on-2016-03-05.md b/_posts/2016-03-05-overview-and-logs-for-the-dev-meeting-held-on-2016-03-05.md
new file mode 100644
index 00000000..c138898a
--- /dev/null
+++ b/_posts/2016-03-05-overview-and-logs-for-the-dev-meeting-held-on-2016-03-05.md
@@ -0,0 +1,29 @@
+---
+layout: post
+title: Overview for the Dev Meeting Held on 2016-03-05
+summary: 0.9.2 Discussion, db fixes, unit test fixes, threading fixes, RingCT development discussion.
+tags: [dev diaries, core, crypto]
+author: gingeropolous
+---
+
+*March 5th, 2016*
+
+# Overview
+
+Open pull requests mostly just DB stuff by warptangent and hyc, and will be merged within next couple of hours. In the last couple of weeks, unit test fixes, threading fixes, "lots of little things". Hyc had some readtxn changes. Hyc's performance changes need to wait until some kind of migration system is implemented / developed.
+
+Fees are fine. Too soon for adjustment. Talk of "magic number automation" - fees will autoadjust one day! ArcticMine takes on researching / developing a proposal for automatically adjusting fees.
+
+Dev Branch - the buck stops here. Moneromoo is waiting for 0.9.2 to be tagged "so that no new patches go there". So once we have 0.9.2, dev branch goes upstream (to master).
+
+We need a library that plays well with HTTPS and support authentication and is compatible with our license.
+
+RingCT - WarpTangent becoming familiar with what needs to be done, and RingCT development will go on newer database branch. There's some "floating point or fixed" issue that needs to be decided. Forum threads will be opened for that. Warptanget steps up to the plate to make the thread.
+
+Changing mixin to something else is a thing that might happen, but "its a community thing, not a dev thing"
+
+Everybody shakes hands, gives themselves pats on the back and "attaboys", and venture off into the night to go meditate on the metaphysics of mixin 0 transactions.
+
+# Logs
+
+Logs for this dev meeting no longer exist or were lost.
diff --git a/_posts/2017-08-20-logs-for-the-Kovri-dev-meeting-held-on-2017-08-20.md b/_posts/2017-08-20-logs-for-the-Kovri-dev-meeting-held-on-2017-08-20.md
new file mode 100644
index 00000000..45b3a1fb
--- /dev/null
+++ b/_posts/2017-08-20-logs-for-the-Kovri-dev-meeting-held-on-2017-08-20.md
@@ -0,0 +1,172 @@
+---
+layout: post
+title: Logs for the Kovri Dev Meeting Held on 2017-08-20
+summary: Brief review of what has been completed since last meeting, discussion of meta issues, and code & open tickets discussion
+tags: [dev diaries, i2p, crypto]
+author: dEBRUYNE / fluffypony
+---
+
+*August 20th, 2017*
+
+# Logs
+
+**\** 1. Greetings
+**\** 2. Brief review of what's been completed since the previous meeting
+**\** 3. Contributor FFS check-in / status
+**\** 4. Code + ticket discussion / Q & A
+**\** 5. Any additional meeting items
+**\** 6. Confirm next meeting date/time
+**\** Well hello
+**\** hi
+**\** Just you and me, eh MoroccanMalinois?
+**\** I'm here too, but I'm just reading.
+**\** I'm here
+**\** here
+**\** bam, attendance more than doubled
+**\** Well there you go
+**\** 2. Brief review of what's been completed since the previous meeting
+**\** We had the 96boards webcast this past Thursday, so that was certainly a highlight.
+**\** It was nice to have that done since I had started coordinating it toward the beginning of this year.
+**\** I continued work on the new Kovri logo, but that has been put on hold indefinitely. I switched gears and started working on the Reddits. Got good amounts of work done and we are fixing to release the Monero subreddit new CSS here pretty soon. Kovri isn't far behind it. Then recently I'm also working on redoing the website a bit. Just a small restructure. Putting together some new wires for the pages.
+**\** I've finally back to NTCP work (yay). Various fixes and rewriting. Now working on a phaser implementation and separating messaging from session code.
+**\** I passed along information to Pigeons about the irc server set up. He is looking into putting it up on a vps.
+**\** I've noticed various little issues along the way that will be fixed along the way
+**\** rehrar ajs: awesome
+**\** No not a vps a vm on a dedicated machine we just got
+**\** Oh even better
+**\** cool
+**\** pigeons1[m]: fluffypony, any update on the infrastructure? :)
+**\** oh, maybe that was just the update :P sorry
+**\** rehrar: we got the machines and are moving things and configuring things. You can send me config info
+**\** I'll talk to Snipa and get them. He did the setting up and debugging.
+**\** I'm assuming it'd be too big a breach to have him help out?
+**\** Let's stay on track here
+**\** k sorry
+**\** re: brief review, I've been playing PM tag with sarang but finally have began email comms
+**\** I had sent him/her/it (assuming him) a list of various research related issues
+**\** but will now work him to hone in on specific areas of research.
+**\** I'm looking forward to this very much +1
+**\** Anything else for brief review?
+**\** Alrighty, 3. Contributor FFS check-in / status
+**\** I'm here. Busy as usual.
+**\** nothing for this time
+**\** (was mostly on vacation)
+**\** A well-deserved one too, I'm sure.
+**\** Back in full swing. Wife healed nicely.
+**\** :)
+**\** MoroccanMalinois: was milestone 2 settled (payment, etc.)?
+**\** nope
+**\** rehrar: good to hear
+**\** Uh oh, why not MoroccanMalinois?
+**\** Not enough work :)
+**\** anonimal: re sarang i'm pleased to hear that
+**\** Oh, when I say milestone 2 I mean *your* milestone 1.
+**\** Because the FFS proposal is in 3 tranches, you took up the 2nd one (though it was your first).
+**\** \*2nd one and 3rd one (because 1st one was completed)
+**\** ah
+**\** i thought u were talking about the 3rd milestone
+**\** that will be done tomorrow
+**\** re: sarang, my thanks to endogenic for coordinating our first connection
+**\** didn't do anything :P
+**\** MoroccanMalinois: ok so 2nd is all settled?
+**\** No i have not contacted luigi yet (will do it tonight)
+**\** ok
+**\** Anything else on FFS check-in/status?
+**\** (I'm here, nothing to report on the ff extension side, been very busy IRL)
+**\** I haven't read sarang's FFS (I hear he put out a new prorposal?)
+**\** Hi bigreddmachine, good to hear from you
+**\** re: FFS topic, does anyone have any specific input on what they'd want sarang to work on/look at re: kovri?
+**\** I had a healthy list for him but I think he'll want me to narrow down things.
+**\** I don't see a new one.
+**\* anonimal** has no idea, I probably shouldn't assume that
+**\** he's a network + crypto dude so i figured it might be possible to collaborate with him to produce a more elegant and simple form of i2p
+**\** You talked on Thursday about simplifying the crypto smorgasbord in kovri... That might be a good place for sarang to focus at some point
+**\** Well when I was playing tag with him, I did ask him if he wanted to work on the anonymity system aspect or crypto; and he did say crypto.
+**\** But he's also more of a math guy, and the reduction of kovri crypto is almost entirely implementation defined (so he wouldn't need to do any work on that).
+**\** The cryptosystems we use could be looked at though, yes, for sure.
+**\** yeah i bet he could help vet the water tightness of existing or new schemes
+**\** and probably suggest alternate techniques for elements
+**\** just guessing
+**\** We'll see. Maybe he'll work on something before the next meeting.
+**\** I'd like him to look at our DSA prime for example. I'm sure that's something he could do.
+**\** But since we use libraries for most of our crypto, he may end up reviewing them.
+**\* anonimal** shrugs, we'll see
+**\** Anything else on FFS check-in?
+**\** k, 4. Code + ticket discussion / Q & A
+**\** i have almost finished fixing #684. Will push later today
+**\** Cool +1
+**\** I'll merge #690. re: #690, I asked surae to look at my algo for aes-256 expanded key size but he didn't have time to look too deeply
+**\** The constant doesn't change, so it's not a huge deal, but things like this would be nice for sarang to review/chime-in with from time-to-time.
+**\** (yes, I said surae for first sentence and sarang for second)
+**\** (so confusing!)
+**\** Anything else on point 4.? I want to get to other points that rehrar and bigreddmachine were talking about.
+**\** MoroccanMalinois: \^
+**\** nope
+**\** k
+**\** 5. Any additional meeting items
+**\** bigreddmachine: are you still planning on doing a podcast?
+**\** Yes. I've had a busy summer so had to tick off some low hanging fruit with episodes. But I really think a talk with you (and any other key contribs) would be super.
+**\** Maybe time it to be right around alpha release date?
+**\** Ok sure. Do you have a link to previous episodes (I didn't know you did them regularly/semi-regularly)?
+**\** MoneroMonitor.com
+**\ {-pigeons}** cool I didn't know about that one.
+**\** Some probably more interesting that others to this crowd :)
+**\** Wow cool!
+**\** Do we have a podcast section on the monero site?
+**\** Not sure. The Monero Missives were once the pseudo-official podcast
+**\** But that's at least a year defunct now.
+**\** It would be nice to have links to things like this so they don't get flushed down the memory hole.
+**\** I'm not sure where they'd go though. Somewhere in the community section I imagine.
+**\** rehrar \^
+**\** Yes I agree. But haven't been sure where either so haven't done a PR.
+**\** bigreddmachine: what's the best way to get in contact with you?
+**\** I'll think about it and see if we can't squeeze you into a place. :)
+**\** In the near future I was to do episodrs on Love, Mimblewimble, with Surae, and probably Zooko on Zcash. And rehrar and I had discussed one too
+**\** Indeed.
+**\** Anonimal, Securely or no?
+**\** Either or is fine. Secure by default? Over the months I've tried pinging you on IRC but you weren't around (I just wanted to ask about the podcast).
+**\** moneromonitor@tutanota.com is a good email
+**\** Yeah I can't log into irc at work... Got in trouble for that hah
+**\** oops!
+**\** Ok, will email you there when needed.
+**\** If you ping me on irc with an "@" in front then slack should notify me though on my phone.
+**\** Imma hafta split here pretty soon. What do we need from me? :)
+**\** @bigreddmachine alright
+**\** Yeah that worked perfect
+**\** rehrar: meeting ends in 4 minutes. You started talking infrastructure so if you had any more comments/questions?
+**\** And then I can log into irc with encryption on that you taught me.
+**\** Oh, no. Not unless pigeons has anything more for me.
+**\** bigreddmachine: that fantabulous cryptos!
+**\** Oh, my question regarding Snipa. I'm assuming you'd just rather us shoot you config thingies? :)
+**\** (you \=\= pigeons?)
+**\** Oh, yes. Sorry for the confusion.
+**\** There's not much config needed for mattermost. I pretty well did a basic clean install, then setup matterbridge with the guides on the site.
+**\** Hardest part was getting the webhooks to play nicely with each other, and seeing how they integrated.
+**\** The man himself, ladies and gentlemen!
+**\** Hi Snipa
+**\** And the Taiga? And then the Taiga / MatterMost connection?
+**\** So we're 100% doing mattermost? I saw a few comments from people questioning/complaining.
+**\** That's the webhooks. If there's a specific question, I'll be glad to answer it of course, but a direct copy of the configs won't be useful, as I very much deployed them quick and dirty.
+**\** As far as I know, yes. We got a second successful test and everything worked perfectly.
+**\** k
+**\** And we'll make a push to get people away from Slack
+**\** +1
+**\** Any other additional meeting items?
+**\** Not from me for the time being.
+**\** Nope
+**\** nope
+**\** hey anonimal
+**\** Hi hyc
+**\** on the 96boards mtg you suggested that only rsa4096 was needed
+**\** why that instead of one of the EC mechs?
+**\** For reseed, yes.
+**\** I'll need to see what the reseed servers are capable of / require.
+**\** afaik EC is smaller/faster/better
+**\* anonimal** agrees
+**\** ok, just wondered and wanted to make sure
+**\** Awesome, thanks for the question :) I'll put on my TODO list
+**\** 6. Confirm next meeting date/time
+**\** Same time, two weeks from now?
+**\** Sure I won't be there but thats not a big deal. I'll catch up with the minutes.
+**\** Ok
+**\** Thank you again everyone!
\ No newline at end of file
diff --git a/_posts/2017-08-20-overview-and-logs-for-the-dev-meeting-held-on-2017-08-20.md b/_posts/2017-08-20-overview-and-logs-for-the-dev-meeting-held-on-2017-08-20.md
new file mode 100644
index 00000000..b728ec91
--- /dev/null
+++ b/_posts/2017-08-20-overview-and-logs-for-the-dev-meeting-held-on-2017-08-20.md
@@ -0,0 +1,502 @@
+---
+layout: post
+title: Overview and Logs for the Dev Meeting Held on 2017-08-20
+summary: Discussion of open PRs and issues, RuffCT, mobile wallets, upcoming release + scheduled protocol upgrade, dedicated hardware wallet, and miscellaneous
+tags: [dev diaries, core, crypto]
+author: dEBRUYNE / fluffypony
+---
+
+*August 20th, 2017*
+
+# Overview
+
+An overview can be found on [MoneroBase](https://monerobase.com/wiki/DevMeeting_2017-08-20).
+
+# Logs
+
+**\** 1. Greetings
+**\** 2. Brief review of what's been completed since the previous meeting
+**\** 3. Code + ticket discussion / Q & A
+**\** 4. Any additional meeting items
+**\** 5. Confirm next meeting date/time
+**\** rehrar can do it next time :)
+**\** I can, sorry for the confusion
+**\** 1. Greetings
+**\** can all the people who aren't here just say nay
+**\** :-P
+**\** neigh
+**\** we never get past this part :
+**\** it's a fun part
+**\** we can move on to 2
+**\** 2. Brief review of what's been completed since the previous meeting
+**\** I guess the big thing is that we've branched
+**\** well
+**\** from MRL
+**\** we got contacted by RingCT2.0 people, and we got contacted by a rsearcher named Tim Ruffing, each of them presenting improved set-ups for our current implementations
+**\** not sure if I should just jump in or what..
+**\** Yeah go ahead
+**\** sure, go
+**\** ok so
+**\** I have a .txt file describing the pseudocode of Ruffing's sublinear ring sig + CT set-up
+**\** knaccc has been going through it and implementing it in Java
+**\** we have a surprising amount of it debugged
+**\** \^ note, we're walking away from the RingCT2.0 stuff because it requires a trusted setup
+**\** Ah, I didn't look into it because Ruffing's doesn't have a trusted set-up or any "new" crytpo. it just doubles all our key lengths
+**\** surae: fpaste.org or pastebin.mozilla.org
+**\** has the meeting started?
+**\** yes
+**\** where does it say it started? jesus
+**\** iDunk is 0bin not good enough? :P
+**\** It requires java.
+**\** js actually
+**\** I think it needs to be encrypted due to agreement with Tim Ruffing.
+**\** oh i didn't realize that
+**\** surae ... the mooo wants javaless paste
+**\** moneromooo no, just habit
+**\** ok one sec
+**\** Oh, ok. I'm dying to see it then :D
+**\** ty
+**\** we are in the midst of debugging knaccc's java code
+**\** surae: Could you perhaps give an ELI5 (for anyone that reads the logs later) how RuffCT will improve our protocol?
+**\** well, roughly, (ruffly)
+**\** lol
+**\** signature sizes are O(N) right now. So signature sizes take up "as much space" as the number of public keys implicated in the signature
+**\** Ruffing's set-up, for N=n\^m, has signature sizes O(n\*m). Verification and computation *it appears* to be on the same order. so, for example, to sign a ring signature with N=10\^17 signers, which is freaking absurd, you would need "as much space" as 10*17 = 170 public keys
+**\** there are constants and stuff, so it's not exact, but at the very least, Ruffing's set-up is looking at really absurdly large ring signatures
+**\** ... without taking absurdly large amount of space
+**\** with a set-up like this, there should be no good reason to not simply sign every transaction with the top half of the blockchain every time
+**\** or taking absurdly large amounts of time to verify or compute
+**\** So we can easily use ring size 100k for instance?
+**\** Or even higher
+**\** even higher
+**\** EVEN HIGHER
+**\** assuming his set-up actually works (the math seems tight) and assuming his security proofs hold up (I am going to try to make independent security proofs and then later compare them), and after six months to a year of testing, etc etc
+**\** i mean
+**\** UNLIMITED RINGSIZE
+**\** fluffypony: what does the scouter say about monero's ringsize level?
+**\** log(infinity) is infinity...
+**\** in a certain sense, this is like an alien came down and gifted us faster than light travel. yeah, we can go out there and start traveling around, but we have to consider consequences for the timeline. :P haha
+**\** endogenic: I give up?
+**\** it's over 9000
+**\** lol
+**\** the puns are ruff today
+**\** also to add to what surae's said
+**\** Would be need (pretty much) all pubkeys/commitments in RAM all the time, in order to verify such sigs ?
+**\** Or can some precomp be done ?
+**\** multisig isn't baked in right now, it would need to be re-done from scratch
+**\** the room fell silent
+**\** I'll precompute it all for ya. trust me.
+**\** fluffypony: Are we certain it has to be re-done from scratch or would it possible to just tweak the current implementation?
+**\** moneromooo the signature itself only uses the commitments from the column of the signer
+**\** dEBRUYNE: we're certain
+**\** k
+**\** fluffypony - can it be dual run like pre-ct and ring-ct till the fork?
+**\** I think we shouldn't forego the current implementation, because we're already quite far in
+**\** debruyne the shen-luigi multisig set-up which is a version of the schnorr multisig, might lead us to a similar set-up for RuffCT, but it's not a simple gluing like one would hope
+**\** In addition, it may take a year before RuffCT is actually implemented
+**\** so that we could keep luigi ms till ruff ms is done ?
+**\** And even longer before we have a multisig that is compatible with ruffct
+**\** you can always convert later
+**\** DaveyJones: I don't think so, at least not trivially
+**\** i mean if we have to do RCT->RuffCT
+**\** dEBRUYNE I'm actually with you on that. chances are good RuffCT is about 1 year out from being live, and I wouldn't be *shocked* if we could make a threshold scheme out of it before that year is up
+**\** same can be done for wallets
+**\** RCT multisig -> RuffCT multisig
+**\** well, basically this isn't going in to a hardfork until we have multisig
+**\** JollyMort[m]: hardware or software wallets?
+**\** i agree with the majority, that multisig pre-ruffct should be implemented for the time being
+**\** and shen/luigi multisig can work regardless of consensus rules
+**\** \ JollyMort[m]: hardware or software wallets? \<= Doesn't matter
+**\** by means of one-time multisig wallets
+**\** so i'm happy finsihing up the shen-luigi multisig scheme, letting wallets use it until RuffCT goes live, they'll still be able to use it for whatever RCT outputs are still floating around if they like... and maybe users may miss out on threshold signatures for one hardfork, but probably not two.
+**\** that sounds decent
+**\