mirror of
https://github.com/monero-project/monero-site.git
synced 2025-01-18 23:53:42 +02:00
Merge branch 'master' of https://github.com/monero-project/monero-site
This commit is contained in:
Riccardo Spagni
commit
22c637da40
@ -21,14 +21,66 @@
|
|||||||
|
|
||||||
- stage: Work in Progress
|
- stage: Work in Progress
|
||||||
proposals:
|
proposals:
|
||||||
|
|
||||||
|
- stage: Completed Proposals
|
||||||
|
proposals:
|
||||||
|
- name: Documentation and cleanup of source code
|
||||||
|
url: /forum-funding-system/proposals/documentation-cleanup.html
|
||||||
|
summary: Clean up and properly document (doxygen) the monero source code
|
||||||
|
author: tewinget
|
||||||
|
- name: What is Monero? is produced and open-sourced
|
||||||
|
url: /forum-funding-system/proposals/whatismonero-produced.html
|
||||||
|
summary: Make an introduction video to Monero.
|
||||||
|
author: savandra
|
||||||
|
- name: Improving Developer Guides to include Simplewallet examples and Bitmonerod methods and examples
|
||||||
|
url: /forum-funding-system/proposals/improve-devguides-simplewallet.html
|
||||||
|
summary: Add examples to Developer Guides
|
||||||
|
author: bigredmachine
|
||||||
|
- name: A continuation for all purpose programming of what needs to get done in monero
|
||||||
|
url: /forum-funding-system/proposals/mooo-continuation-programming.html
|
||||||
|
summary: moneromooo continue coding for Monero
|
||||||
|
author: moneromooo
|
||||||
|
- name: Create End-User Kovri documentation
|
||||||
|
url: /forum-funding-system/proposals/kovri-end-user-docs.html
|
||||||
|
summary: The idea is to create user-friendly non-technical Kovri documentation.
|
||||||
|
author: anonimal
|
||||||
|
- name: fluffypony's Conference Circuit Jan 2017 Edition
|
||||||
|
url: /forum-funding-system/proposals/fp-conference-2017.html
|
||||||
|
summary: Cover fluffypony's expenses for January Monero speaking
|
||||||
|
author: fluffypony
|
||||||
|
- name: The official Qt GUI Project
|
||||||
|
url: /forum-funding-system/proposals/official-qt-gui.html
|
||||||
|
summary: Funding for the creation of the GUI
|
||||||
|
author: othe
|
||||||
|
- name: Justin's Local Meetup Talks Proposal 1
|
||||||
|
url: /forum-funding-system/proposals/justin-local-meetups-1.html
|
||||||
|
summary: Cover sgp's travel expenses for Monero speaking
|
||||||
|
author: samsunggalaxyplayer
|
||||||
|
- name: Justin's Local Meetup Talks Proposal 2
|
||||||
|
url: /forum-funding-system/proposals/justin-local-meetups-2.html
|
||||||
|
summary: Cover sgp's other travel expenses for Monero speaking
|
||||||
|
author: samsunggalaxyplayer
|
||||||
|
- name: More mooo coding goodness
|
||||||
|
url: /forum-funding-system/proposals/more-mooo-coding-goodness.html
|
||||||
|
summary: Moneromooo coding October 2016
|
||||||
|
author: moneromooo
|
||||||
|
- name: Funding for a Monero subforum on the largest chinese BTC forum 8BTC
|
||||||
|
url: /forum-funding-system/proposals/monero-subforum-8btc.html
|
||||||
|
summary: Make subforum on China's largest Bitcoin forum 8BTC
|
||||||
|
author: firperfect
|
||||||
|
- name: Additional GUI Developer
|
||||||
|
url: /forum-funding-system/proposals/additional-gui-dev.html
|
||||||
|
summary: Hire Jaquee as an additional GUI developer
|
||||||
|
author: Jaquee
|
||||||
- name: Getmonero.org Redesign
|
- name: Getmonero.org Redesign
|
||||||
url: /forum-funding-system/proposals/getmonero-redesign.html
|
url: /forum-funding-system/proposals/getmonero-redesign.html
|
||||||
summary: Redesign the official getmonero.org website to make it more accessible and aesthetically pleasing.
|
summary: Redesign the official getmonero.org website to make it more accessible and aesthetically pleasing.
|
||||||
author: rehrar
|
author: rehrar
|
||||||
|
- name: Release of new/updated pool software
|
||||||
- stage: Completed Proposals
|
url: /forum-funding-system/proposals/release-pool-software.html
|
||||||
proposals:
|
summary: An updated pool for usage within the XMR community
|
||||||
- name: What is Monero? is produced and open-sourced
|
author: Snipa22
|
||||||
url: /forum-funding-system/proposals/whatismonero-produced.html
|
- name: Monero integrations with web apps
|
||||||
summary: Make an introduction video to Monero.
|
url: /forum-funding-system/proposals/monero-integrations.html
|
||||||
author: savandra
|
summary: Make open-source payment gateways for Monero on popular web apps
|
||||||
|
author: serhack
|
||||||
@ -5,8 +5,8 @@
|
|||||||
<div class="container slide-in">
|
<div class="container slide-in">
|
||||||
<div class="row">
|
<div class="row">
|
||||||
<div class="col-xs-12 dropdown text-center nav-item">
|
<div class="col-xs-12 dropdown text-center nav-item">
|
||||||
<label for="slidedrop1">Get Started<div class="arrow-down"></div></label>
|
<label for="drop1">Get Started<div class="arrow-down"></div></label>
|
||||||
<input class="burger-checkdropdown" id="slidedrop1" type="checkbox">
|
<input class="burger-checkdropdown" id="drop1" type="checkbox">
|
||||||
<div class="dropdown-content">
|
<div class="dropdown-content">
|
||||||
<a href="/get-started/what-is-monero/">What Is Monero?</a>
|
<a href="/get-started/what-is-monero/">What Is Monero?</a>
|
||||||
<a href="/get-started/using/">Using</a>
|
<a href="/get-started/using/">Using</a>
|
||||||
@ -26,8 +26,8 @@
|
|||||||
</div>
|
</div>
|
||||||
<div class="row">
|
<div class="row">
|
||||||
<div class="col-xs-12 dropdown text-center nav-item">
|
<div class="col-xs-12 dropdown text-center nav-item">
|
||||||
<label for="slidedrop2">Recent News<div class="arrow-down"></div></label>
|
<label for="drop2">Recent News<div class="arrow-down"></div></label>
|
||||||
<input class="burger-checkdropdown" id="slidedrop2" type="checkbox">
|
<input class="burger-checkdropdown" id="drop2" type="checkbox">
|
||||||
<div class="dropdown-content">
|
<div class="dropdown-content">
|
||||||
<a href="/blog/">All Posts</a>
|
<a href="/blog/">All Posts</a>
|
||||||
<a href="/blog/tags/monero%20missives.html">Missives</a>
|
<a href="/blog/tags/monero%20missives.html">Missives</a>
|
||||||
@ -38,8 +38,8 @@
|
|||||||
</div>
|
</div>
|
||||||
<div class="row">
|
<div class="row">
|
||||||
<div class="col-xs-12 dropdown text-center nav-item">
|
<div class="col-xs-12 dropdown text-center nav-item">
|
||||||
<label for="slidedrop3">Community<div class="arrow-down"></div></label>
|
<label for="drop3">Community<div class="arrow-down"></div></label>
|
||||||
<input class="burger-checkdropdown" id="slidedrop3" type="checkbox">
|
<input class="burger-checkdropdown" id="drop3" type="checkbox">
|
||||||
<div class="dropdown-content">
|
<div class="dropdown-content">
|
||||||
<a href="/community/team/">Team</a>
|
<a href="/community/team/">Team</a>
|
||||||
<a href="/community/hangouts/">Hangouts</a>
|
<a href="/community/hangouts/">Hangouts</a>
|
||||||
@ -51,8 +51,8 @@
|
|||||||
</div>
|
</div>
|
||||||
<div class="row">
|
<div class="row">
|
||||||
<div class="col-xs-12 dropdown text-center nav-item">
|
<div class="col-xs-12 dropdown text-center nav-item">
|
||||||
<label for="slidedrop4">Resources<div class="arrow-down"></div></label>
|
<label for="drop4">Resources<div class="arrow-down"></div></label>
|
||||||
<input class="burger-checkdropdown" id="slidedrop4" type="checkbox">
|
<input class="burger-checkdropdown" id="drop4" type="checkbox">
|
||||||
<div class="dropdown-content">
|
<div class="dropdown-content">
|
||||||
<a href="/resources/about/">About</a>
|
<a href="/resources/about/">About</a>
|
||||||
<a href="/resources/roadmap/">Roadmap</a>
|
<a href="/resources/roadmap/">Roadmap</a>
|
||||||
|
|||||||
@ -17,8 +17,8 @@ layout: base
|
|||||||
</div>
|
</div>
|
||||||
<div class="row center-xs">
|
<div class="row center-xs">
|
||||||
<div class="col-xs-12 progress-numbers">
|
<div class="col-xs-12 progress-numbers">
|
||||||
<p class="progress-number-funded">100 XMR </p><span> /</span>
|
<p class="progress-number-funded">{{page.amount}} XMR</p><span> /</span>
|
||||||
<p class="progress-number-goal">100 XMR</p>
|
<p class="progress-number-goal">{{page.amount}} XMR</p>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
<div class="row">
|
<div class="row">
|
||||||
@ -60,7 +60,8 @@ layout: base
|
|||||||
<div class="row center-xs">
|
<div class="row center-xs">
|
||||||
<div class="col">
|
<div class="col">
|
||||||
<h2>{{page.title}}</h2>
|
<h2>{{page.title}}</h2>
|
||||||
<p>by {{page.author}}</p>
|
<p>by <strong>{{page.author}}</strong></p>
|
||||||
|
<p><em>{{page.date}}</em></p>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
<div>
|
<div>
|
||||||
|
|||||||
@ -70,7 +70,8 @@ layout: base
|
|||||||
<div class="row center-xs">
|
<div class="row center-xs">
|
||||||
<div class="col">
|
<div class="col">
|
||||||
<h2>{{page.title}}</h2>
|
<h2>{{page.title}}</h2>
|
||||||
<p>by {{page.author}}</p>
|
<p>by <strong>{{page.author}}</strong></p>
|
||||||
|
<p><em>{{page.date}}</em></p>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
<div>
|
<div>
|
||||||
|
|||||||
@ -13,7 +13,8 @@ layout: base
|
|||||||
<div class="row center-xs">
|
<div class="row center-xs">
|
||||||
<div class="col">
|
<div class="col">
|
||||||
<h2>{{page.title}}</h2>
|
<h2>{{page.title}}</h2>
|
||||||
<p>{{page.author}}</p>
|
<p>by <strong>{{page.author}}</strong></p>
|
||||||
|
<p><em>{{page.date}}</em></p>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
<div>
|
<div>
|
||||||
|
|||||||
@ -14,7 +14,8 @@ layout: base
|
|||||||
<div class="row center-xs">
|
<div class="row center-xs">
|
||||||
<div class="col">
|
<div class="col">
|
||||||
<h2>{{page.title}}</h2>
|
<h2>{{page.title}}</h2>
|
||||||
<p>{{page.author}}</p>
|
<p>by <strong>{{page.author}}</strong></p>
|
||||||
|
<p><em>{{page.date}}</em></p>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
<div>
|
<div>
|
||||||
|
|||||||
@ -62,7 +62,8 @@ layout: base
|
|||||||
<div class="row center-xs">
|
<div class="row center-xs">
|
||||||
<div class="col">
|
<div class="col">
|
||||||
<h2>{{page.title}}</h2>
|
<h2>{{page.title}}</h2>
|
||||||
<p>by {{page.author}}</p>
|
<p>by <strong>{{page.author}}</strong></p>
|
||||||
|
<p><em>{{page.date}}</em></p>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
<div>
|
<div>
|
||||||
|
|||||||
@ -0,0 +1,208 @@
|
|||||||
|
---
|
||||||
|
layout: post
|
||||||
|
title: Logs for the Community Meeting Held on 2017-10-28
|
||||||
|
summary: Community highlights, Forum Funding System updates, Monero meetup kit, 34C3, RFC-HWALLET-1, Monero integrations, upcoming meetups, community survey, and miscellaneous
|
||||||
|
tags: [community, crypto]
|
||||||
|
author: dEBRUYNE / fluffypony
|
||||||
|
---
|
||||||
|
|
||||||
|
*October 28th, 2017*
|
||||||
|
|
||||||
|
# Logs
|
||||||
|
|
||||||
|
**\<sgp>** Meeting is starting
|
||||||
|
**\<sgp>** 0. Introduction
|
||||||
|
**\<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/132
|
||||||
|
**\<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
|
||||||
|
**\<vp11>** hey there lovely people
|
||||||
|
**\<erciccione>** hi
|
||||||
|
**\<xmrscott[m]>** Salutations
|
||||||
|
**\<endogenic>** o/
|
||||||
|
**\<sgp>** 2. Community highlights
|
||||||
|
**\<sgp>** For a great weekly summary, please read the Monero Observer: http://monero-observer.com/
|
||||||
|
**\<sgp>** The Monero Observer’s FFS proposal has been fully-funded!
|
||||||
|
**\<sgp>** 3. FFS updates
|
||||||
|
**\<sgp>** There are several FFS updates.
|
||||||
|
**\<sgp>** a. Monero Meetup Kit
|
||||||
|
**\<sgp>** I don’t have anything to add here except that it is now in Funding Required: https://forum.getmonero.org/8/funding-required/88374/monero-meetup-kit
|
||||||
|
**\<sgp>** b. 34C3 congress preparations
|
||||||
|
**\<sgp>** @msvb-lab would you like to comment about this?
|
||||||
|
**\<michael>** Minute?
|
||||||
|
**\<sgp>** Anyone have anything to discuss regarding this event?
|
||||||
|
**\<sgp>** Ok, well if they join us, we can go back
|
||||||
|
**\<vp11>** i have a question
|
||||||
|
**\<vp11>** for the monero meetup kit
|
||||||
|
**\<sgp>** @vp11 go ahead
|
||||||
|
**\<vp11>** how the groups are going to be selected to receive the kit? do you already have an application draft?
|
||||||
|
**\<vp11>** i wouldn't apply because brazil is far away :P but I was just curious
|
||||||
|
**\<vp11>** and this gave enough time to msvb-lab to join :)
|
||||||
|
**\<sgp>** I will create an application form once the webcam covers arrive. For these first few kits, it will only be for groups in the US
|
||||||
|
**\<sgp>** serhack and I will discuss these. If anyone else would like to help also, PM me and you can help too
|
||||||
|
**\<msvb-lab>** Travelling a bit and screwey Internet. Sorry, I'm here now.
|
||||||
|
**\<vp11>** but are there minimum requirements that you have in mind? like number of people who will join the event, etc etc, or you're still brainstorming how it will work?
|
||||||
|
**\<vp11>** oh nice
|
||||||
|
**\<vp11>** that's cool
|
||||||
|
**\<sgp>** Target of 50 people at the event
|
||||||
|
**\<sgp>** So preference towards groups that have consistently had strong attendance
|
||||||
|
**\<vp11>** makes sense, thanks!
|
||||||
|
**\<sgp>** @msvb-lab feel free to jump in. I know you have several items you want to discuss
|
||||||
|
**\<msvb-lab>** sgp: Yes cool, parasew[m] are we talking about 34C3 here now?
|
||||||
|
**\<sgp>** Yeah
|
||||||
|
**\<msvb-lab>** We don't have anything concrete about 34C3 (the end of year large conferernce in Leipzig.)
|
||||||
|
**\<sgp>** Then you can talk about the hardware wallet after too
|
||||||
|
**\<msvb-lab>** Just want to announce we'll be present as Monero in the Cryptocurrency assembly.
|
||||||
|
**\<msvb-lab>** The hardware wallet forum post mandates that we do progress status reports in monero-dev meetings.
|
||||||
|
**\<msvb-lab>** ...but we moved away from them, so the question is if we're at home here?
|
||||||
|
**\<sgp>** I say you can have some, but don't get too technical here
|
||||||
|
**\<msvb-lab>** Some wanted to keep the monero-dev meetings software only.
|
||||||
|
**\<msvb-lab>** sgp: Then if nobody objects, we'll keep things neat and basic, and do status reporting here.
|
||||||
|
**\<sgp>** Anyone have any thoughts? Are high-level updates cool for everyone?
|
||||||
|
**\<vp11>** the community funded the project so it makes sense to share progress reports here, I don't see a problem with that. as @sgp said, just take care to not go super technical.
|
||||||
|
**\<msvb-lab>** Like now I can say that we're becoming a stable team and have created together a first prototype.
|
||||||
|
**\<msvb-lab>** https://taiga.getmonero.org/media/attachments/1/e/2/5/ee5db3efec91a39cab0f35f243f54513ac8437d56bd18cc8e5a2910f7c4c/assembled_flashed.jpg
|
||||||
|
**\<msvb-lab>** Photos are good for non technical discussion fodder, no?
|
||||||
|
**\<vp11>** cool pic
|
||||||
|
**\<msvb-lab>** A question, does anyone know where the source code went for the last state of Trezor Monero firmware port?
|
||||||
|
**\<sgp>** Photos are especially good
|
||||||
|
**\<vp11>** yeah, photos are great!
|
||||||
|
**\<msvb-lab>** Like this post basically killed the Trezor port:
|
||||||
|
**\<msvb-lab>** https://forum.getmonero.org/9/work-in-progress/265/adding-monero-support-for-trezor?page=&noscroll=1#post-1520
|
||||||
|
**\<msvb-lab>** ...but we can't find the firmware that was created up until that point.
|
||||||
|
**\<nioc>** msvb-lab: I forget who has the trezor "snap shot" but they might know in dev
|
||||||
|
**\<sgp>** @msvb-lab this is all I have, and the links are dead https://forum.getmonero.org/4/academic-and-technical/2495/experimental-trezor-firmware-testing
|
||||||
|
**\<vp11>** it's proprietary, right? does someone have it?
|
||||||
|
**\<msvb-lab>** sgp: Yes, we found lots of dead links too.
|
||||||
|
**\<msvb-lab>** vp11: Trezor firmware is Opensource.
|
||||||
|
**\<msvb-lab>** ...as we are of course.
|
||||||
|
**\<msvb-lab>** nioc: Hey cool, thanks for the advice. I'll check again in -dev.
|
||||||
|
**\<sgp>** It was NoodleDoodle
|
||||||
|
**\<msvb-lab>** sgp: NoodleDoodle still hangs out here, or mostly in -dev?
|
||||||
|
**\<vp11>** msvb-lab, didn't know that, thanks for the education
|
||||||
|
**\<sgp>** Mostly in -dev
|
||||||
|
**\<msvb-lab>** sgp: Okay cool, so this weeks 'status update' is rather unorganised due to travel, sorry.
|
||||||
|
**\<msvb-lab>** But that's all I have an can of course answer questions if folks are curious.
|
||||||
|
**\<sgp>** @msvb-lab no worries, we've all been there
|
||||||
|
**\<sgp>** Any questions for him?
|
||||||
|
**\<vp11>** no questions but I'm excited for this project :)
|
||||||
|
**\<vp11>** the progress reports will be welcome
|
||||||
|
**\<msvb-lab>** vp11: Cool, check out:
|
||||||
|
**\<msvb-lab>** https://taiga.getmonero.org/project/michael-rfc-hwallet-1-implementation/
|
||||||
|
**\<nioc>** sgp: somebody besides noodledoodle has it, I don't think he wants anything to do with it now
|
||||||
|
**\<msvb-lab>** ...and sign up as a tester or something.
|
||||||
|
**\<vp11>** amazing, will do!
|
||||||
|
**\<msvb-lab>** nioc: What would your strategy be for finding it, since 'somebody besides' == many people?
|
||||||
|
**\<msvb-lab>** ask on monero-dev right? If that's the strategy then I understood correctly.
|
||||||
|
**\<sgp>** -dev is the best place to ask
|
||||||
|
**\<nioc>** msvb-lab: I just remember it being disclosed in -dev
|
||||||
|
**\<msvb-lab>** nioc: Cool, thanks again.
|
||||||
|
**\<dEBRUYNE>** msvb-lab: https://github.com/prusnak/trezor-xmr/commits/master
|
||||||
|
**\<dEBRUYNE>** This is part of it
|
||||||
|
**\<nioc>** it might not be a dev but an long time community member
|
||||||
|
**\<msvb-lab>** dEBRUYNE: Interesting, that looks very good. Might be what we're after.
|
||||||
|
**\<vp11>** dEBRUYNE always comes to save the day
|
||||||
|
**\<sgp>** Yup :)
|
||||||
|
**\<sgp>** @msvb-lab anything else you want to discuss before we move on?
|
||||||
|
**\<msvb-lab>** sgp: No, thanks for giving me the chance to speak.
|
||||||
|
**\<sgp>** d. Monero Integrations
|
||||||
|
**\<sgp>** Serhack is busy today, but you can see the latest update on the work here: https://www.reddit.com/r/Monero/comments/7938pb/monero_integrations_update_10/
|
||||||
|
**\<serhack>** Hey :)
|
||||||
|
**\<sgp>** Oh, apparently he can still drop by!
|
||||||
|
**\<sgp>** @serhack anything else you want to add?
|
||||||
|
**\<serhack>** No :)
|
||||||
|
**\<serhack>** Expect some news soon
|
||||||
|
**\<sgp>** Cool. Everyone read the linked update if interested
|
||||||
|
**\<sgp>** 4. Upcoming Meetups
|
||||||
|
**\<rehrar>** Yay
|
||||||
|
**\<sgp>** There will be a Monero Meetup in LA on November 7th: https://www.meetup.com/preview/Monero-Los-Angeles/events/242968913
|
||||||
|
**\<sgp>** Does anyone know of other events coming up?
|
||||||
|
**\<serhack>** A secret project is cooming soon
|
||||||
|
**\<dEBRUYNE>** msvb-lab: there's these two too: https://github.com/jedigras/noodledoodle_xmr_trezor/commits/master & https://github.com/jedigras/trezor-xmr/commits/master
|
||||||
|
**\<vp11>** ohhhh these secret projects!!
|
||||||
|
**\<serhack>** Expect a b ... ops :)
|
||||||
|
**\<sgp>** I'll let serhack discuss it when he's ready, but it will require many volunteers
|
||||||
|
**\<sgp>** 5. Community Survey
|
||||||
|
**\<sgp>** xmr\_eric posted the results from his third survey, with over 500 responses: https://www.reddit.com/r/Monero/comments/794v43/monero_community_survey_3_results_over_500/
|
||||||
|
**\<sgp>** I want to take a few minutes and discuss the results.
|
||||||
|
**\<serhack>** Yeah @sgp. Not now
|
||||||
|
**\<serhack>** Monero community is awesome
|
||||||
|
**\<sgp>** We have a lot of active people!
|
||||||
|
**\<notcreative>** anyone know if there is an official remote note that I can connect to rather than local copy?
|
||||||
|
**\<sgp>** Did anyone find any of the results surprising?
|
||||||
|
**\<serhack>** But there are some "devs" that don't/ can't contribute
|
||||||
|
**\<serhack>** That's interesting
|
||||||
|
**\<vp11>** I did find the results very interesting
|
||||||
|
**\<sgp>** notcreative: no official ones, but check out moneroworld.com
|
||||||
|
**\<vp11>** I wanted even to discuss if we could do something to promote OpenAlias more.
|
||||||
|
**\<vp11>** I find it's a great feature for newcomers into the cryptocurrency scene.
|
||||||
|
**\<notcreative>** @sgp - Thanks
|
||||||
|
**\<sgp>** @vp11 I think we should promote it more to businesses
|
||||||
|
**\<sgp>** Most people don't own their own domain
|
||||||
|
**\<vp11>** indeed, business would love having their "main hot wallet" with something easy like monero@domain.com for payments.
|
||||||
|
**\<vp11>** I know there's a tutorial on monero.how
|
||||||
|
**\<vp11>** but maybe do a more graphic tutorial and promote it? I don't know. anyway, it's only one of the interesting points from the community survey.
|
||||||
|
**\<sgp>** I think OpenAlias is something people will not typically know of by name but understand how it works when they use it
|
||||||
|
**\<sgp>** Like not many normal people understand how DNS works but they know how to go to getmonero.org
|
||||||
|
**\<vp11>** exactly
|
||||||
|
**\<sgp>** Also, OpenAlias gets kinda messy if you need payment IDs
|
||||||
|
**\<sgp>** Poloniex couldn't use deposit.poloniex.com since they need a payment ID/integrated address
|
||||||
|
**\<vp11>** hmm that makes sense. I guess that while normal email providers don't support the option this will be something for "niche" only?
|
||||||
|
**\<vp11>** like institutions or websites asking for donation (no need for payment id)
|
||||||
|
**\<vp11>** or normal people with their own domains
|
||||||
|
**\<sgp>** It may be. I don't think it makes sense for anything requiring a payment ID
|
||||||
|
**\<vp11>** indeed
|
||||||
|
**\<sgp>** Anyone else have any thoughts?
|
||||||
|
**\<sgp>** Thanks xmr\_eric for making the survey, and thanks everyone who took the time to respond
|
||||||
|
**\<sgp>** 6. Open ideas time
|
||||||
|
**\<sgp>** It’s open ideas time! Feel free to propose your ideas to this discussion group, and feel free to comment on others’ ideas. If you disagree with the idea, please reply with constructive criticism. Thank you!
|
||||||
|
**\<msvb-lab>** I really like the monero.how site, didn't know it existed until today.
|
||||||
|
**\<sgp>** It's been some time since we've had an adequate discussion time during a meeting
|
||||||
|
**\<vp11>** monero.how is so good, seriously one of the best websites for monero out there
|
||||||
|
**\<sgp>** @msvb-lab knaccc has done a great job with it, hasn't he?
|
||||||
|
**\<msvb-lab>** I wonder if part of the meetup kit could be text based.
|
||||||
|
**\<msvb-lab>** Like a card with four links, a paragraph description, some simple stuff, a few diagrams.
|
||||||
|
**\<msvb-lab>** ...if I have stickers and stuff then I would keep this card together with them.
|
||||||
|
**\<sgp>** It will include flyers and this infographic (https://www.monero.how/monero-infographic). What do you think it missing?
|
||||||
|
**\<msvb-lab>** sgp: Cool, no that's most precicely what I had in mind.
|
||||||
|
**\<sgp>** Great
|
||||||
|
**\<msvb-lab>** Good to see that others have covered the need.
|
||||||
|
**\<vp11>** as I said yesterday, I'll donate the getmonero.com.br domain for the Monero Project once we get the localisation project for the website going. just wanted to say it here to make it official and logged on github :)
|
||||||
|
**\<vp11>** I'll use another domain for the brazilian community initiative
|
||||||
|
**\<sgp>** @vp11 keeping yourself accountable :P
|
||||||
|
**\<sgp>** I can't wait until the website is localized. Lots of work being done
|
||||||
|
**\<sgp>** Can anyone make a plush Monero cat? I would totally buy one https://www.reddit.com/r/xmrtrader/comments/791w4r/daily_discussion_friday_october_27th/doystjw/
|
||||||
|
**\<sgp>** Also a Monero sweater
|
||||||
|
**\<msvb-lab>** We don't really have a mascot do we? Maybe it should be a cat.
|
||||||
|
**\<vp11>** msvb-lab, we kinda have
|
||||||
|
**\<vp11>** it's monero cat
|
||||||
|
**\<msvb-lab>** vp11: How does one know this?
|
||||||
|
**\<sgp>** https://ip.bitcointalk.org/?u=http%3A%2F%2Fi.imgur.com%2FFpEboZL.png&t=581&c=fHuK94WKFrPfhg
|
||||||
|
**\<sgp>** From an old Bitcointalk post
|
||||||
|
**\<msvb-lab>** Wow, very nice.
|
||||||
|
**\<sgp>** From hitbtc lmao https://bitcointalk.org/index.php?topic=583449.msg7527905#msg7527905
|
||||||
|
**\<vp11>** msvb-lab, there's even comics about Monero Cat, come on man.
|
||||||
|
**\<vp11>** https://www.reddit.com/r/Monero/comments/78wctn/who_is_monero_cat_episode_6_for_oct_26_is_out/
|
||||||
|
**\<vp11>** I want a Monero sweater, gonna ask my mother to make me one.
|
||||||
|
**\<sgp>** I created this really long post earlier this week: https://steemit.com/monero/@sgp/7yjqso-a-monero-introduction-for-beginners
|
||||||
|
**\<sgp>** Does anyone have constructive criticism of it?
|
||||||
|
**\<vp11>** only destructive ;) not really, I thought it was a good read.
|
||||||
|
**\<msvb-lab>** sgp: You saved that until the end? Nice thing to read, I'll definitely be checking it out. Diagrams are great.
|
||||||
|
**\<msvb-lab>** Speaking of saving until the end, I forgot to mention that anonimal and I were interviewed by BTCManager:
|
||||||
|
**\<msvb-lab>** https://btcmanager.com/interview-monero-hardware-wallet-pioneer-michael-schloh-and-kovri-dev-anonimal/
|
||||||
|
**\<vp11>** cool, I really like btcmanager, it's one of my favorites website. will surely check it out, thanks for sharing msvb-lab
|
||||||
|
**\<sgp>** Yeah, btcmanager has written some solid articles lately
|
||||||
|
**\<msvb-lab>** We have a journalist there on our side.
|
||||||
|
**\<rehrar>** Yeah
|
||||||
|
**\<sgp>** Does anyone have any final remarks?
|
||||||
|
**\<rehrar>** Nah
|
||||||
|
**\<vp11>** love you all guys :)
|
||||||
|
**\<sgp>** 7. Confirm next meeting date/time
|
||||||
|
**\<sgp>** The next meeting will two weeks from today on 10 November at 17:00 UTC.
|
||||||
|
**\<sgp>** Keep in mind that the second Monero Coffee Chat is next Saturday 4 November
|
||||||
|
**\<msvb-lab>** Thanks for moderating sgp[m], see you all later.
|
||||||
|
**\<sgp>** In future discussions, I would like to focus the conversation around using social media and getting some new faces involved here
|
||||||
|
**\<vp11>** nice, do we already know what platform we will be using next time?
|
||||||
|
**\<sgp>** I've been in dicussion with Jitsi and they're convinced our bug is incredibly rare, so we will use that again. However, it will actually be streamed to YouTube this time for most people to view
|
||||||
|
**\<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.
|
||||||
@ -0,0 +1,256 @@
|
|||||||
|
---
|
||||||
|
layout: post
|
||||||
|
title: Logs for the Monero Research Lab Meeting Held on 2017-10-30
|
||||||
|
summary: Multisig, hash-based accumulators, blockchain protocols, quantum-hard shuffle PRNG, educational outreach, and miscellaneous
|
||||||
|
tags: [community, crypto]
|
||||||
|
author: dEBRUYNE / fluffypony
|
||||||
|
---
|
||||||
|
|
||||||
|
*October 30th, 2017*
|
||||||
|
|
||||||
|
# Logs
|
||||||
|
|
||||||
|
**\<sarang>** Let's go
|
||||||
|
**\<suraeNoether>** Welcome everyone, to our second official (third unofficial) research meeting. fluffypony dEBRUYNE luigi1111 knaccc
|
||||||
|
**\<suraeNoether>** uhm... ArcticMine... uhm... who else should we ping? moneromooo
|
||||||
|
**\<luigi1111w>** official counts toward unofficial?
|
||||||
|
**\<suraeNoether>** endogenic
|
||||||
|
**\<suraeNoether>** is an official meeting also unofficial? is it a subset relation? anyway
|
||||||
|
**\<suraeNoether>** kenshi84 too
|
||||||
|
**\<suraeNoether>** ok so, I don't really have an agenda. I want me and sarang to share with the group what we've been doing these past few weeks, and if anyone else has been doing any interesting research, let's talk about it
|
||||||
|
**\<suraeNoether>** sarang, you wanna go first?
|
||||||
|
**\<sarang>** Sure
|
||||||
|
**\<sarang>** I've been working a lot of readings mainly on some interesting new stuff
|
||||||
|
**\<sarang>** Hash-based accumulators are becoming a thing
|
||||||
|
**\<sarang>** where you can use interesting pairing relations to prove membership or nonmembership in a set
|
||||||
|
**\<sarang>** the nifty part is that the manager of the set is untrusted
|
||||||
|
**\<suraeNoether>** you've mentioned those several times. are all hash-based accumulators based on pairings crypto?
|
||||||
|
**\<suraeNoether>** or are you using pairing differently
|
||||||
|
**\<sarang>** Oh, I mean the structure involves pairs of elements as opposed to single elements
|
||||||
|
**\<suraeNoether>** ah, ok
|
||||||
|
**\<sarang>** This is a newer structure that gives nice efficiencies
|
||||||
|
**\<suraeNoether>** so can we use a hash-based accumulator without a trusted set-up to do something *akin* to ring signatures?
|
||||||
|
**\<sarang>** That's my interest
|
||||||
|
**\<sarang>** The security models would have to be analyzed in that new context
|
||||||
|
**\<silur>** sarang does the order of these pairs have any effect on the security?
|
||||||
|
**\<sarang>** None
|
||||||
|
**\<silur>** okay
|
||||||
|
**\<sarang>** What it does
|
||||||
|
**\<sarang>** is give you a fast way of demonstrating membership or nonmembership
|
||||||
|
**\<sarang>** by using the pairings akin to an ordering
|
||||||
|
**\<hyc>** ... reminds me of bloom filters, fast set membership
|
||||||
|
**\<suraeNoether>** hyc i'm sorry i forgot to ping you
|
||||||
|
**\<hyc>** no prob
|
||||||
|
**\<sarang>** I've also been continuing investigations into aggregate signatures, something surae brought to my attention a while back
|
||||||
|
**\<sarang>** the idea being that you can compress a set of signatures down to a single one
|
||||||
|
**\<suraeNoether>** hyc bloom filters do fast set non-membership, not fast set membership, but both are based on hashes
|
||||||
|
**\<sarang>** Verification is still linear
|
||||||
|
**\<sarang>** but space is constant
|
||||||
|
**\<sarang>** There is of course a downside, which is that it requires a bilinear map between groups with particular properties
|
||||||
|
**\<sarang>** It's apparently still an open question whether it's possible to construct an aggregate that doesn't require full linear verification
|
||||||
|
**\<suraeNoether>** i didn't realize agg sigs used pairings
|
||||||
|
**\<sarang>** The ones I've seen use bilinear maps to allow for third-party verification
|
||||||
|
**\<sarang>** It's a clever and fairly simple setup
|
||||||
|
**\<suraeNoether>** i found a few new sorts of signatures we maybe could look into, i have a list
|
||||||
|
**\<sarang>** What gets into the weeds is the way the security models account for it all
|
||||||
|
**\<sarang>** And there are some caveats dealing with repeated messages
|
||||||
|
**\<sarang>** Of course, subaddys went out already
|
||||||
|
**\<sarang>** SPECTRE is something that's on the radar for surae and I
|
||||||
|
**\<suraeNoether>** andytoshi linked his slides about atomic swaps and at least one type of sig i'm not totally familiar with was mentioned, and I forget what it's called. Aggregator signatures? or something like that.
|
||||||
|
**\<sarang>** And I'm still working on new work on proofs of proof-of-work
|
||||||
|
**\<sarang>** that, if implemented ideally, could offer significant savings in blockchain space/analysis
|
||||||
|
**\<sarang>** Logarithmically
|
||||||
|
**\<suraeNoether>** the past several weeks, i've been putting several hours a day into multisig... current version I will link tomorrow. I have had to modify the scheme to take into account multiple outputs, which isn't a huge deal, but changed notation throughout the paper pretty significantly, so
|
||||||
|
**\<sarang>** It's an ever-moving target
|
||||||
|
**\<suraeNoether>** i will link the current version tomorrow after i give it yet another read-through
|
||||||
|
**\<suraeNoether>** yeah, ring multisignatures are delicate
|
||||||
|
**\<suraeNoether>** but i've also been looking into spectre, as sarang mentioned
|
||||||
|
**\<suraeNoether>** i have a current working implementation on my github... but it takes quadratic time N^2 to organize N blocks
|
||||||
|
**\<suraeNoether>** which is not scalable
|
||||||
|
**\<sarang>** You wanna mention that email?
|
||||||
|
**\<suraeNoether>** i contacted Sompolinsky, one of the authors
|
||||||
|
**\<suraeNoether>** yeah
|
||||||
|
**\<suraeNoether>** I asked about the constant-time implementation they claim, and he got back to me
|
||||||
|
**\<suraeNoether>** my intuition about how to make this constant time was correct.... the algorithm can determine the order of leaves without any input from parents, grandparents, or grand\*parents of those leaves
|
||||||
|
**\<suraeNoether>** so working from the leaves backwards, and only organizing a constant number of blocks is sufficient to get computation time down to constant
|
||||||
|
**\<sarang>** But at a yet-to-be-analyzed cost
|
||||||
|
**\<suraeNoether>** which is sort of a cheat
|
||||||
|
**\<suraeNoether>** yes
|
||||||
|
**\<suraeNoether>** there is an attack where someone purposely chooses a block deep into the blockDAG
|
||||||
|
**\<suraeNoether>** this forces each node on the network to organize deeply into the blockDAG, which best case is a quadratic experience. pretty nasty.
|
||||||
|
**\<suraeNoether>** my first thought was our traditional split between full nodes and lightweight nodes
|
||||||
|
**\<sarang>** So it struck me as basically a DoS?
|
||||||
|
**\<suraeNoether>** uhm... kinda. it's DoS in the sense that ostensibly *honest* blocks can be used in the attack
|
||||||
|
**\<suraeNoether>** and it's not really an attack in a security sense, it's an attack that forces miners to blow CPU power
|
||||||
|
**\<sarang>** Right
|
||||||
|
**\<sarang>** That's what I mean
|
||||||
|
**\<suraeNoether>** so my first thought was full nodes that organize the top 2% of the blockDAG all the time, and lightweight nodes that only go back a certain \# of generations from the leaves and avoid blocks too close to the genesis block
|
||||||
|
**\<suraeNoether>** both sorts of nodes can do their thing in constant time. the full nodes will have larger constants, the lightweights will have smaller constants
|
||||||
|
**\<sarang>** So this reminded me of the discussion from a while back about ignoring blocks that are old enough
|
||||||
|
**\<sarang>** and the pros and cons of doing so...
|
||||||
|
**\<suraeNoether>** well we already reject blocks if their timestamps are outliers
|
||||||
|
**\<sarang>** So you think maybe the attack is irrelevant due to the time constraint?
|
||||||
|
**\<suraeNoether>** the timestamp isn't really the problem, it's where the block is placed in the tree. and we can't really reject blocks that are too deep into the blockDAG, because I don't see a good way for two different miners to agree what "too deep" means
|
||||||
|
**\<suraeNoether>** i think doing a full/light sort of split as above will avoid the attack for the most part, but it will tweak incentives
|
||||||
|
**\<suraeNoether>** but it's ... tricky
|
||||||
|
**\<suraeNoether>** anyway
|
||||||
|
**\<suraeNoether>** that's what i've been doing
|
||||||
|
**\<suraeNoether>** oh, on multisig, I mentioned this earlier this week, but i'm getting quite confident we'll be done with it pretty soon. code review is moving forward bit by bit (heh)
|
||||||
|
**\<suraeNoether>** is anyone else working on any interesting projects? i know that we've had discussions in here recently about PRNG and such, and I'm curious about what people are working on
|
||||||
|
**\<sarang>** Oooh yes, PRNG
|
||||||
|
**\<sarang>** I have no further updates, since I'm not sure if the devs took any definitive action it
|
||||||
|
**\<sarang>** There was also an observation about the use of keccak vs. SHA-3
|
||||||
|
**\<silur>** I'm working on a quantum-hard shuffle that can be used to construct PRNG-s
|
||||||
|
**\<suraeNoether>** silur: freaking awesome. by "working on" do you mean... writing a paper? working on code?
|
||||||
|
**\<silur>** writing a paper
|
||||||
|
**\<suraeNoether>** and what makes a shuffle "hard"? trying to un-shuffle?
|
||||||
|
**\<sarang>** Determining the end state w/o going through all steps?
|
||||||
|
**\<silur>** trying to reveal the previous state of the elements of the set
|
||||||
|
**\<silur>** or "peeking under the cards"
|
||||||
|
**\<sarang>** Nice, so it's a one-way function
|
||||||
|
**\<suraeNoether>** yup
|
||||||
|
**\<suraeNoether>** very cool
|
||||||
|
**\<suraeNoether>** are you a student, a professor, a hobbyist, silur?
|
||||||
|
**\<suraeNoether>** i still haven't read that shuffle paper you sent me :(
|
||||||
|
**\<silur>** I'll be a prof from next september on crypto
|
||||||
|
**\<sarang>** Congrats!
|
||||||
|
**\<suraeNoether>** congratulations!
|
||||||
|
**\<silur>** I'm at the edge of leaving ethereum foundation currently
|
||||||
|
**\<silur>** thanks :)
|
||||||
|
**\<sarang>** Any other interesting projects?
|
||||||
|
**\<sarang>** Or suggestions on directions to go?
|
||||||
|
**\<unknownids>** congrats!
|
||||||
|
**\<suraeNoether>** i'm also reading up on succinct posets, which are ... a new datastructure. btw for anyone curious, every DAG induces a poset and every poset is a DAG
|
||||||
|
**\<suraeNoether>** data structure\*
|
||||||
|
**\<sarang>** Yeah, that poset paper looks quite interesting
|
||||||
|
**\<suraeNoether>** they are significantly more compact than representing a DAG using upper triangular matrices, and they allow for constant time to determine whether one item precedes another
|
||||||
|
**\<sarang>** I find the tradeoffs between storage and time to be always fascinating
|
||||||
|
**\<suraeNoether>** so using those instead of the data structures i was coidng is going to lead to about a 75% reduction in computation time (but that's still quadratic...)
|
||||||
|
**\<silur>** wow
|
||||||
|
**\<suraeNoether>** https://arxiv.org/pdf/1204.1957.pdf
|
||||||
|
**\<suraeNoether>** and lastly, one more thing i'm kind of casually thinking about is andytoshi's idea for outputs where "addresses change." my best idea so far is to have each output be addressed to a *set* of destination addresses, each with their own timelock, but all sharing a key image (somehow)(
|
||||||
|
**\<suraeNoether>** really the challenge is to come up with a representation of a single key image for a single output but with multiple destination addresses each with their own timelock
|
||||||
|
**\<suraeNoether>** or rather: this would be one possible solution to the atomic swap refund transaction problem andytoshi brought up the other day.
|
||||||
|
**\<suraeNoether>** and that's all i have been working on
|
||||||
|
**\<suraeNoether>** other than silur, is anyone working on anything fun?
|
||||||
|
**\<suraeNoether>** or not fun as the case may be
|
||||||
|
**\<sarang>** http://nick.mtvnimages.com/nick/promos-thumbs/videos/spongebob-squarepants/spongebob-squarepants-fun-song-16x9.jpg?maxdimension=&quality=0.60
|
||||||
|
**\<suraeNoether>** okay
|
||||||
|
**\<moneromooo>** About PRNG: I ported the Bitcoin PRNG to monero, it's on github if anyone is curious.
|
||||||
|
**\<moneromooo>** I added a contentious patch, so that one will either go, or be modified.
|
||||||
|
**\<suraeNoether>** is the PRNG the contentious part or?
|
||||||
|
**\<moneromooo>** I added seeding from /dev/random at startup.
|
||||||
|
**\<sarang>** Can you link moneromooo ?
|
||||||
|
**\<suraeNoether>** oh i see heh
|
||||||
|
**\<moneromooo>** smooth thinks it should only be done if getrandom is not used, so I'll probably do this.
|
||||||
|
**\<suraeNoether>** i don't know enough about the various pros and cons of that approach to have an opinion
|
||||||
|
**\<suraeNoether>** on an administrative level, sarang: any word on the weekend course for talented high school students thing? i'm going to contact folks at the local universities around me this week to feel out the possibilities for a 2018 1-week summer workshop for undergraduates.
|
||||||
|
**\<moneromooo>** https://github.com/monero-project/monero/pull/2731
|
||||||
|
**\<suraeNoether>** thanks moneromooo
|
||||||
|
**\<sarang>** Ah yes, thanks for the reminder surae
|
||||||
|
**\<sarang>** So there has been interest expressed in two school programs
|
||||||
|
**\<suraeNoether>** if you want we can collab on the proposal for the springtime one
|
||||||
|
**\<sarang>** One would be a longer-term effort to work with North Carolina STEM students
|
||||||
|
**\<sarang>** A shorter but logistically-simpler one is with Duke University for a spring weekend course for gifted high schoolers
|
||||||
|
**\<sarang>** That's a bit tougher due to the extremely short course time
|
||||||
|
**\<suraeNoether>** yeah, i like the idea of spending a week or three with undergrads to teach them about crypto and maybe fork bitcoin or monero and mess with the code or something.... but i'm not so sure how much we can even do over one weekend with high school students
|
||||||
|
**\<sarang>** So maybe it's better to nix the weekend course idea and try for the longer course?
|
||||||
|
**\<sarang>** I don't have a good sense of the logistics required for that
|
||||||
|
**\<sarang>** But I'm investigating still
|
||||||
|
**\<sarang>** Another option is to do a Duke summer program that's 3 weeks long
|
||||||
|
**\<suraeNoether>** sarang let's try to set aside a few hours this week to figure out logistics of this. i would love for the monero community to fund up some education programs. that's good PR for everyone, and starts a pipeline of education into the cryptocurrency world... but i don't want to burden the monero community unnecessarily (for one thing) and if we can get a university to devote some money to this too, it
|
||||||
|
**\<suraeNoether>** adds legitimacy
|
||||||
|
**\<sarang>** The Duke summer one wouldn't require any funding from the community
|
||||||
|
**\<sarang>** since students are paying to go to it
|
||||||
|
**\<suraeNoether>** ok, so we have the Duke TIPP thing as a possibility there to reduce the burden on the community
|
||||||
|
**\<sarang>** Yep, and because they already have a supply of gifted students identified
|
||||||
|
**\<suraeNoether>** and maybe the first summer we should do something like that rather than taking point ourselves on organizing the program
|
||||||
|
**\<sarang>** Let's talk about that option
|
||||||
|
**\<suraeNoether>** cool
|
||||||
|
**\<sarang>** I've proposed new summer courses before. It's more involved than the weekend ones, but not bad at all
|
||||||
|
**\<sarang>** We both meet the instructor qualifications
|
||||||
|
**\<suraeNoether>** can you put out feelers in that direction and then we can talk about the responses you receive later this week?
|
||||||
|
**\<sarang>** Can do
|
||||||
|
**\<suraeNoether>** cool
|
||||||
|
**\<sarang>** I need to find the timeline for new course proposals for the summer. We may have missed it already
|
||||||
|
**\<suraeNoether>** oh, that would suck
|
||||||
|
**\<sarang>** Yeah, I'll check
|
||||||
|
**\<sarang>** They're always hunting for new STEM courses though
|
||||||
|
**\<sarang>** So they might make an exception
|
||||||
|
**\<sarang>** especially for me :D
|
||||||
|
**\<suraeNoether>** ok, maybe make a call or shoot an email today then, keep me updated
|
||||||
|
**\<suraeNoether>** okay, anyone else have anything they want to discuss?
|
||||||
|
**\<sarang>** Just emailed the bosses
|
||||||
|
**\<suraeNoether>** cool
|
||||||
|
**\<suraeNoether>** Okay, well if no one has anything else for now
|
||||||
|
**\<knaccc>** I was kinda wondering if you could give a brief explanation of whether bileanear pairings might be good for the future, for people like me who have no idea what it means
|
||||||
|
**\<suraeNoether>** aha
|
||||||
|
**\<sarang>** Surae, wanna take this?
|
||||||
|
**\<suraeNoether>** actually not at all
|
||||||
|
**\<knaccc>** hehe
|
||||||
|
**\<suraeNoether>** ha
|
||||||
|
**\<suraeNoether>** okay i will
|
||||||
|
**\<sarang>** lol
|
||||||
|
**\<suraeNoether>** ok knaccc so... bilinear crypto is essentially a way of taking an easy group and gluing it with hard group into a pair. And you do operations on the pair of curve points instead of an individual curve point. tthis is on it's own, useless
|
||||||
|
**\<silur>** surae you just opened a world before me saying that posets are isomorphic to DAGs how I didn't notice this \<3
|
||||||
|
**\<suraeNoether>** silur my dissertation is aaaaaal about po-groups
|
||||||
|
**\<suraeNoether>** if, however, you have a "bilinear pairing"
|
||||||
|
**\<suraeNoether>** you can move stuff from one of these two groups to the other
|
||||||
|
**\<knaccc>** so bilinear pairingss still use e.g. curve25519/ed25519?
|
||||||
|
**\<sarang>** One useful case is aggregate signatures that use exponentiation
|
||||||
|
**\<suraeNoether>** afaik there are not many curves compatible with bilinear pairing
|
||||||
|
**\<sarang>** The transfer between groups is what allows for verification
|
||||||
|
**\<suraeNoether>** hence CSW's weird meltdown on twitter
|
||||||
|
**\<knaccc>** ah so it'd be a diffferent curve that would have to be used then?
|
||||||
|
**\<sarang>** Yeah, it's an idealization right now
|
||||||
|
**\<suraeNoether>** so, a really dumb way to describe it is: if i need to know something about (A,B+C), I can hit it with the bilinear pairing e and treat that like (A+C,B)
|
||||||
|
**\<suraeNoether>** or rather
|
||||||
|
**\<knaccc>** and what's an easy group vs hard group?
|
||||||
|
**\<suraeNoether>** oh, like Zq versus X25519
|
||||||
|
**\<knaccc>** oh i see
|
||||||
|
**\<suraeNoether>** with bilinear pairings, the DDH problem is trivial to solve
|
||||||
|
**\<sarang>** You can also look at hardness as meaning hardness assumptions of problems
|
||||||
|
**\<sarang>** yeah
|
||||||
|
**\<suraeNoether>** *nod*
|
||||||
|
**\<sarang>** So the security definitions get really picky, for good reason
|
||||||
|
**\<knaccc>** are you aware of any performance implications of bilinear pairings
|
||||||
|
**\<suraeNoether>** yeah so, a linear function is one that behaves like this: f(a\*X + b\*Y) = a\*f(X) + b\*f(Y). a *bilinear* function has two inputs instead of one, (a\*X+b\*Y, c\*Z + d\*W), and it behaves linearly in each coordinate
|
||||||
|
**\<suraeNoether>** knaccc i am not
|
||||||
|
**\<sarang>** It would depend on the groups and the mapping
|
||||||
|
**\<sarang>** I think the current implementation limitations mean there hasn't been solid analysis on that yet
|
||||||
|
**\<suraeNoether>** did everyone see Craig Wright embarassing himself about this stuff, btw? on reddit and twitter
|
||||||
|
**\<sarang>** Also depends on our use case
|
||||||
|
**\<sarang>** Signature aggregation is just one application that sparked our interest
|
||||||
|
**\<sarang>** No!
|
||||||
|
**\<sarang>** Link plz surae
|
||||||
|
**\<knaccc>** can you define signature aggregation?
|
||||||
|
**\<suraeNoether>** oh haha
|
||||||
|
**\<suraeNoether>** https://www.reddit.com/r/Bitcoin/comments/79bnox/vitalik_and_uandytoshi_calling_out_csw_for_his/?utm_term=7fd17439-49d1-4d0f-90c7-a42272b3f896&utm_medium=search&utm_source=reddit&utm_name=frontpage&utm_content=1
|
||||||
|
**\<suraeNoether>** CSW claims he invented bitcoin and he used the secp256k1 curve because it's compatible with bilinear pairings
|
||||||
|
**\<silur>** ahahhaha :D
|
||||||
|
**\<suraeNoether>** and while that is kind of technically true, you need to store 10^70 or more bits, you know, a number comparable to the number of particles in the universe
|
||||||
|
**\<suraeNoether>** very entertaining read
|
||||||
|
**\<suraeNoether>** knaccc sig aggregation is a way of taking one or more signatures and combining them into a single signature, aggregating them
|
||||||
|
**\<knaccc>** for the purposes of saving space, verification time, both?
|
||||||
|
**\<sarang>** knaccc you save space
|
||||||
|
**\<sarang>** it's constant in the \# of sigs
|
||||||
|
**\<sarang>** verification is currently linear
|
||||||
|
**\<sarang>** there are implications for things like certificate chains etc.
|
||||||
|
**\<knaccc>** ah that leads me to my last quick question: i think someone mentioned that it was 'provable' that verification time had to be always linear
|
||||||
|
**\<suraeNoether>** well, ruffing proved that a ring sig scheme is linear in verification time
|
||||||
|
**\<sarang>** Agg. sigs are not ring sigs
|
||||||
|
**\<knaccc>** ah ok that was my question. it's ring signature specific then
|
||||||
|
**\<knaccc>** aha
|
||||||
|
**\<sarang>** They can be completely independent sigs
|
||||||
|
**\<silur>** do we have the updated ruffCT paper?
|
||||||
|
**\<knaccc>** i see
|
||||||
|
**\<sarang>** and in fact the messages have to be distinct
|
||||||
|
**\<knaccc>** cool thanks sarang suraeNoether
|
||||||
|
**\<silur>** I started on overview on that but sarang and surae told me it's outdated
|
||||||
|
**\<suraeNoether>** silur i can email you the copy i received from ruffing, but the bootle paper isn't private and ruffing's scheme is "Bootle + regular old multisig"
|
||||||
|
**\<suraeNoether>** https://eprint.iacr.org/2015/643
|
||||||
|
**\<suraeNoether>** silur the ruffCT scheme basically does this: for each output used in the signature, build a row of a matrix, entries are ring members. for each column of your resulting matrix, you should have a commitment to an amount, and the signature is essentially proving with an NIZK proof that you can open one of the commitments to zero
|
||||||
|
**\<suraeNoether>** the idea is that you know the actual keys in one of those columns
|
||||||
|
**\<suraeNoether>** but the code on the github is functional and up to date, and if you compare it to the bootle paper i'm pretty sure you'll be able to figure it out without me needing to ask ruffing for more permission to share his paper that says "DO NOT SHARE" on the top lol
|
||||||
|
**\<silur>** okay thanks
|
||||||
|
**\<suraeNoether>** okay, everyone, I think I'm going to call this meeting (seems like knaccc ran out of questions)
|
||||||
41
forum-funding-system/proposals/additional-gui-dev.md
Normal file
41
forum-funding-system/proposals/additional-gui-dev.md
Normal file
@ -0,0 +1,41 @@
|
|||||||
|
---
|
||||||
|
layout: ffs-cp
|
||||||
|
title: Additional GUI Developer
|
||||||
|
author: Jaquee
|
||||||
|
amount: 2,475
|
||||||
|
date: November 22, 2016
|
||||||
|
---
|
||||||
|
|
||||||
|
### What
|
||||||
|
|
||||||
|
Additional GUI developer.
|
||||||
|
|
||||||
|
### Who
|
||||||
|
|
||||||
|
I’m Jaquee. I have 10+ yrs experience of various kinds of coding. I’m new to the crypto world. Have only been around for a couple of months and i like what i see. I’ve been contributing to Monero for about a month now and this is what i’ve come up with so far:
|
||||||
|
|
||||||
|
[https://github.com/monero-project/monero-core/commits/master?author=Jaqueeee](https://github.com/monero-project/monero-core/commits/master?author=Jaqueeee)
|
||||||
|
|
||||||
|
[https://github.com/monero-project/monero/commits/master?author=jaqueeee](https://github.com/monero-project/monero/commits/master?author=jaqueeee)
|
||||||
|
|
||||||
|
### Why
|
||||||
|
|
||||||
|
I love the fundamentals of Monero and want to get more involved in the community. I believe an official GUI will help Monero go mainstream. Ilya has done a terrific job so far, but his time is limited and I’m happy to help out. The public beta is soon to be released but a lot of features such as daemon integration (start/stop), better remote node support, ux improvements, porting to smartphones, third party plugin system etc. are not finished yet.
|
||||||
|
|
||||||
|
### The Proposal and Milestones
|
||||||
|
|
||||||
|
Hourly pay: 4.5 xmr (~$25)
|
||||||
|
|
||||||
|
10-20 hours per week over 6 months. ~550 hours
|
||||||
|
|
||||||
|
Total: 2475 XMR
|
||||||
|
|
||||||
|
Milestones: I’ll write reports every 50 hours and will be working on the missing features and future requests from community.
|
||||||
|
|
||||||
|
Payments: 11 payments of 225 XMR, one for each 50 hour milestone (paid in XMR)
|
||||||
|
|
||||||
|
### Expiration
|
||||||
|
|
||||||
|
9 months
|
||||||
|
|
||||||
|
Edit: Changed xml.to integration in examples -> third party plugin system.
|
||||||
33
forum-funding-system/proposals/documentation-cleanup.md
Normal file
33
forum-funding-system/proposals/documentation-cleanup.md
Normal file
@ -0,0 +1,33 @@
|
|||||||
|
---
|
||||||
|
layout: ffs-cp
|
||||||
|
title: Documentation and cleanup of source code
|
||||||
|
author: tewinget
|
||||||
|
amount: 3,600
|
||||||
|
date: September 11, 2015
|
||||||
|
---
|
||||||
|
### What
|
||||||
|
Clean up and properly document (doxygen) the monero source code, and handle any merges necessary to do so seamlessly with other concurrent development efforts.
|
||||||
|
|
||||||
|
### Who
|
||||||
|
I'm Thomas Winget, and I've been contributing to the Monero codebase since around June 2014. My largest contribution is the migration from storing the blockchain in a static, binary format to storing the blockchain using a database API, as well as two BlockchainDB implementations (LMDB and BerkeleyDB). Other contributions of mine can be found via the network graph on github or simply looking at my fork.
|
||||||
|
|
||||||
|
As a side effect of the work I've done already on Monero, I'm rather familiar with most of the codebase. This puts me in a good position to write down how everything works and fits together, as I've had to sort that out already for many parts.
|
||||||
|
|
||||||
|
As a side effect of this effort, I will further cement the knowledge I have of the codebase and gain knowledge in areas I'm less familiar with, enabling me to efficiently implement new features in the future and guide others who may have questions regarding a specific module. In addition, documenting the code will function as a sort of code review, allowing the possibility of spotting any bugs (minor or otherwise).
|
||||||
|
|
||||||
|
### Why
|
||||||
|
In my time developing on Monero, there have been countless instances where I need to reference what another piece of code does in order to work with it, and having all the code documented properly in an easily accessible manner (doxygen) would be helpful for that for anyone working in Monero's codebase. I have also come across areas where the code could be made more efficient or clear without changing any functionality, as well as many typographical errors (though these are minor, I think we can all agree they're annoying if nothing else).
|
||||||
|
|
||||||
|
Documentation is by far not a glamorous task (probably why it's a bit sparse in Monero), but every development effort benefits immensely from properly documented code.
|
||||||
|
|
||||||
|
### Proposals and Milestones
|
||||||
|
I would like to spend about 20 hours per week working on the above, at a rate of 45 XMR per hour (just over $20/hr USD at the time of writing this), paid out every week. I am unsure whether or not 80 hours of work will be enough to cover the entire codebase. There are over 70,000 lines of source in the src/ folder alone, and there is code in other folders that brings the total to over 100k, so this is no small task!
|
||||||
|
|
||||||
|
Milestones would be as follows:
|
||||||
|
|
||||||
|
- First 20 hours (900/3600 XMR)
|
||||||
|
- Second 20 hours (1800/3600 XMR)
|
||||||
|
- Third 20 hours (2700/3600 XMR)
|
||||||
|
- Fourth 20 hours (3600/3600 XMR)
|
||||||
|
|
||||||
|
After each milestone (and during), I will be available for comment, so anything that seems unclear in my documentation can be addressed and dealt with accordingly.
|
||||||
49
forum-funding-system/proposals/fp-conference-2017.md
Normal file
49
forum-funding-system/proposals/fp-conference-2017.md
Normal file
@ -0,0 +1,49 @@
|
|||||||
|
---
|
||||||
|
layout: ffs-cp
|
||||||
|
title: fluffyponys Conference Circuit Jan 2017 Edition
|
||||||
|
author: fluffypony
|
||||||
|
amount: 590
|
||||||
|
date: December 9, 2016
|
||||||
|
---
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
### Introduction
|
||||||
|
|
||||||
|
As you know, I've spent a fair amount of time, energy, and money, travelling overseas to speak about Monero over the last 2.5 years. At the time the community simply couldn't afford to cover my expenses, and it was a burden I happily bore as it raised a great deal of awareness of Monero. At this time I'd like to raise funds to cover my Jan 2017 conference trip.
|
||||||
|
|
||||||
|
### The Trip
|
||||||
|
|
||||||
|
*2016-12-26 to 2017-01-01*: Hamburg, Germany, for 33c3 (not being funded, for my own costs)
|
||||||
|
* 2017-01-01 to 2017-01-05 *: Amsterdam, The Netherlands, I'll be talking at Bitcoin Wednesday on 2017-01-04
|
||||||
|
* 2017-01-06 to 2017-01-09 *: San Francisco, USA, I'll be talking at Coinbase (note: not open to public attendance) on 2017-01-06, and I'll be at the Monero Silicon Valley Meetup on 2017-01-07
|
||||||
|
* 2017-01-10 to 2017-01-16 *: Florida, USA, where the wife and I will take a few day's break and explore the Keys (not being funded, for my own costs)
|
||||||
|
* 2017-01-16 to 2017-01-20 *: Miami, USA, where I'll be talking at The North American Bitcoin Conference on 2017-01-17 / 2017-01-18
|
||||||
|
* 2017-01-20 to 2017-01-30 *: Secret Location, where I'll once again be representing Monero at the Satoshi Roundtable (note: not open to public attendance)
|
||||||
|
|
||||||
|
### Funding Structure
|
||||||
|
|
||||||
|
A few points of order:
|
||||||
|
|
||||||
|
- 33c3's costs are not included in this, as we are not hosting a Monero assembly at 33c3 this year due to how difficult it was to get tickets - only 3 members of the Monero community will be in attendance, that I know, besides myself.
|
||||||
|
- I'm not expecting to raise the full amount, and anything not raised by the end of January will be for my expense.
|
||||||
|
- All the expenses are calculated on basic 3-star hotels (excluding hostels) and economy flights. I will cover upgrades, as well as my wife's tickets and costs, of my own volition.
|
||||||
|
- I have not factored in food and drink costs, and there is no per diem, as that's largely not a big deal and I don't want to bankrupt the community.
|
||||||
|
- All of my travel is already 100% booked and even mostly paid for (discounts on up-front hotel payments), so my trip is not contingent on fundraising.
|
||||||
|
- Due to the nature of international travel, jet lag, flight availability, conference timing, and the need to prepare, I always give myself a few days on either side of a speaking engagement.
|
||||||
|
- I am not paying to speak at any of the conferences / events, nor am I being paid - it's all 100% free and at the cost of the community and myself.
|
||||||
|
- Flight pricing was done using Kiwi's multicity search, and a reasonable combination was selected (note that for some flights I couldn't take the cheapest due to extremely tight time constraints between Bitcoin Wednesday and Coinbase, but I can't reflect this on Kiwi easily).
|
||||||
|
- Hotel pricing was done using BookingComplete's multicity search.
|
||||||
|
|
||||||
|
Note that if the proposal is over-funded I will take a reasonable portion of the over-fund for food / drink / taxis / per-diem, and the rest I will reapportion to other fundraisers as needed.
|
||||||
|
|
||||||
|
### Costs Breakdown
|
||||||
|
|
||||||
|
Flights come to $2963, all in.
|
||||||
|
Accommodation in Amsterdam comes to $362.
|
||||||
|
Accommodation in San Francisco comes to $540.
|
||||||
|
Accommodation in Miami comes to $413.
|
||||||
|
Accommodation in the Satoshi Roundtable Location comes to $297 (can't show the screenshot for that:)
|
||||||
|
|
||||||
|
Total fundraiser is, therefore, for $4575. Monero is currently sitting at $7.75, so the fundraiser is for 590 XMR.
|
||||||
|
|
||||||
@ -1,9 +1,9 @@
|
|||||||
---
|
---
|
||||||
layout: ffs-wip
|
layout: ffs-cp
|
||||||
title: Getmonero.org Redesign
|
title: Getmonero.org Redesign
|
||||||
address: 4445
|
|
||||||
paymentid: 3xj3
|
|
||||||
author: rehrar
|
author: rehrar
|
||||||
|
date: February 24, 2017
|
||||||
|
amount: 100
|
||||||
milestones:
|
milestones:
|
||||||
- name: Milestone 1 - Front page & restructure
|
- name: Milestone 1 - Front page & restructure
|
||||||
funds: 10% (~XMR 10.70)
|
funds: 10% (~XMR 10.70)
|
||||||
|
|||||||
@ -0,0 +1,28 @@
|
|||||||
|
---
|
||||||
|
layout: ffs-cp
|
||||||
|
title: Improving Developer Guides to include Simplewallet examples and Bitmonerod methods and examples
|
||||||
|
author: bigreddmachine
|
||||||
|
amount: 90
|
||||||
|
date: March 8, 2016
|
||||||
|
---
|
||||||
|
### What do I want to do and why?
|
||||||
|
For some time, the Developer Guides under Knowledge Base have been quite short on material. There is some documentation of simplewallet JSON RPC methods, but no complete examples. In addition, there is no information on bitmonerod methods.
|
||||||
|
|
||||||
|
Recently, I have been working on building out a Python package for Monero. My initial focus has been to build a comprehensive package for talking with the daemon and simplewallet via RPC methods. As a result, I have had to pull information from many different sources so that I can flesh out my package (primarily working from other packages, example sites, BitcoinTalk, reddit, and the main bitmonero GitHub source code).
|
||||||
|
|
||||||
|
I would like to turn my efforts around and compile all of this information into the getmonero.org Knowledge Base so that future developers will not have to go through the same struggle. This is separate from the work I am already doing on my Python package.
|
||||||
|
|
||||||
|
### Who Am I?
|
||||||
|
I am a PhD student and graduate researcher in engineering, and have been in the cryptocurrency space for a little over two years. I have contributed in small amounts to various cryptocurrency projects. Most relevantly, I am the creator of the [Monero Monitor Chrome Extension](https://chrome.google.com/webstore/detail/monero-monitor/ojekadcfnkkihlleaafggfgbggdckpgo) and am currently working on [Pymonero](https://github.com/Monero-Monitor/pymonero).
|
||||||
|
|
||||||
|
### Proposed Milestones:
|
||||||
|
1. Add examples (with return examples) to the [Simplewallet RPC information already available](https://getmonero.org/knowledge-base/developer-guides/wallet-rpc).
|
||||||
|
2. Create a similar page for the Bitmonero daemon RPC interface, including both the JSON RPC methods and other methods such as ```/gettransactions``` and ```/is_key_image_spent```.
|
||||||
|
|
||||||
|
|
||||||
|
### Funding:
|
||||||
|
In total, I anticipate this task will take me 6 hours, including creating examples of both valid and invalid method calls. This is on top of the time that I am spending on my own to continue to develop Pymonero to be a comprehensive Python tool. I anticipate that I will be able to complete both milestones over a two week period during evenings after my actual job.
|
||||||
|
|
||||||
|
I am asking to raise 90 XMR, or 15 XMR/hr. Please let me know if this seems reasonable.
|
||||||
|
|
||||||
|
**-Mike, a.k.a. BRM**
|
||||||
65
forum-funding-system/proposals/justin-local-meetups-1.md
Normal file
65
forum-funding-system/proposals/justin-local-meetups-1.md
Normal file
@ -0,0 +1,65 @@
|
|||||||
|
---
|
||||||
|
layout: ffs-cp
|
||||||
|
title: Justin's Local Meetup Talks Proposal #1: Valencia, Graz, and Zagreb
|
||||||
|
author: samsunggalaxyplayer
|
||||||
|
amount: 66
|
||||||
|
date: March 20, 2017
|
||||||
|
---
|
||||||
|
|
||||||
|
** UPDATE: NOW INCLUDES ROME AND ATHENS **
|
||||||
|
|
||||||
|
### Introduction
|
||||||
|
|
||||||
|
I am studying abroad at the University of Vienna, and I think I should take the opportunity to speak about Monero around Europe at local cryptocurrency meetups. This is the first proposal of what I hope to be many, depending on the success of this one. Since I have a lot of free time in Europe, I would love to speak about Monero in many cities. This proposal is just for four, two of which are free to this community.
|
||||||
|
|
||||||
|
[Valencia](https://twitter.com/vbotecom/status/842305872856514560): March 15th (not collecting donations; was on vacation)
|
||||||
|
|
||||||
|
Graz: March 27th (graciously paid for by [BlockchainHub Graz](https://www.meetup.com/BlockchainHub-Graz/events/238204566/))
|
||||||
|
|
||||||
|
[Zagreb](https://www.meetup.com/Bitcoin-Group-Zagreb/events/238616297/): April 3rd (asking for reimbursement)
|
||||||
|
|
||||||
|
[Athens](https://www.meetup.com/BlockchainGreece-0/events/236892446/): April 28th (asking for reimbursement)
|
||||||
|
|
||||||
|
[Rome](https://www.meetup.com/Bitcoin-Generation-Roma/events/238585056/): May 27th (asking for reimbursement)
|
||||||
|
|
||||||
|
### About Me
|
||||||
|
|
||||||
|
I have been an active contributor in the Monero community for two years now. While the best program I wrote was for my calculator, I have worked to contribute to the Monero project in several other ways. [I am among the most active StackExchange users on the Monero site](http://area51.stackexchange.com/proposals/98617?phase=beta&users=mostactive#tab-top), I am a moderator on the /r/MoneroMining subreddit, and I have spoken about Monero [several](http://imgur.com/a/XbMuX) [times](http://imgur.com/a/xyUKc) at my home university. [I am a president](http://imgur.com/a/Ye85G) of the [University of Minnesota Cryptocurrency Club](https://forum.getmonero.org/22/completed-tasks/87610/www.cryptoumn.com), and we have approximately 50 active members. When I am back in the states, our group typically has two meetings a month, and I play a large role in the meeting presentations. Although I am interested in several cryptocurrencies, Monero has received the majority of my time and effort outside of the club's efforts.
|
||||||
|
|
||||||
|
I am working with other groups to speak in Athens, Rome, Budapest, Edinburgh, Dublin, Cologne, Warsaw, Paris, Riga, Oslo, Stockholm, and others. If this is successful, expect talks in many other cities. I am purposefully avoiding speaking at places that Riccardo Spagni has already spoken at to increase the reach of these talks.
|
||||||
|
|
||||||
|
The meeting will cover the history of privacy and fungibility in Bitcoin, discuss several approaches to the problems, and discuss how Monero achieves its privacy in detail. I will discuss the next steps in development going forward and limitations compared to other coins. It will be similar to Riccardo Spagni's speeches, but I have tried to make the presentation my own. The Valencia speech was very similar to Riccardo's, and I hope to make some improvements to my presentation before the Graz and Zagreb meetups. My speeches are in English.
|
||||||
|
|
||||||
|
I am speaking about Monero, but I will not function as a "salesperson" for the currency. I will address the work in progress with Monero and the drawbacks it has compared to some other coins. While I definitely do not want to make the presentation strictly a comparison of coins, I want to make it clear that I will try to give the most factual information about Monero. I am doing these speeches to raise awareness of Monero, not to trick people into buying some.
|
||||||
|
|
||||||
|
### Funding Structure
|
||||||
|
|
||||||
|
- I am not being paid to speak at this location.
|
||||||
|
- Flight and hotel search was completed with Google Flights and Google, respectively.
|
||||||
|
- If the proposal is over-funded, I would suggest that a reasonable amount is used for food costs (~$25). If the price of Monero falls suddenly before the trip, the extra amount will make up the difference in dollars. I am okay taking a slight loss, but I cannot afford to carry out future proposals if the value of Monero falls by a large amount. This decision is ultimately up to the moderators.
|
||||||
|
- Flights are the cheapest I could find that fit in the available time window. Some exceptions may be made to substantially shorten travel time or layovers. Hotels are basic and 2 or 3-star.
|
||||||
|
- In some instances, I will take a train or a bus if it saves time and/or money. For instance, I plan on taking a train to Budapest to save money. To get to Zagreb, the train routes are not as direct, and a bus would take many hours. That's why I am taking a flight to Zagreb this time.
|
||||||
|
|
||||||
|
### Costs Breakdown
|
||||||
|
|
||||||
|
Zagreb Flight (round trip): $256
|
||||||
|
|
||||||
|
Zagreb Hotel (2 nights): $120
|
||||||
|
|
||||||
|
Transportation to/from airports: $40
|
||||||
|
|
||||||
|
Athens Flight (round trip): $280
|
||||||
|
|
||||||
|
Athens Hotel (2 nights): $130
|
||||||
|
|
||||||
|
Transportation to/from airports: $40
|
||||||
|
|
||||||
|
Rome Flight (round trip): $160
|
||||||
|
|
||||||
|
Rome Hotel (3 nights): $245
|
||||||
|
|
||||||
|
Transportation to/from arports: $40
|
||||||
|
|
||||||
|
Total: $1311 (66 XMR)
|
||||||
|
|
||||||
|
I got excited and booked my flights and hotels before this gets funded. Thus, I am going to speak at these locations whether this proposal gets funded or not.
|
||||||
48
forum-funding-system/proposals/justin-local-meetups-2.md
Normal file
48
forum-funding-system/proposals/justin-local-meetups-2.md
Normal file
@ -0,0 +1,48 @@
|
|||||||
|
---
|
||||||
|
layout: ffs-cp
|
||||||
|
title: Justin's Local Meetup Talks Proposal #2: April to June
|
||||||
|
author: samsunggalaxyplayer
|
||||||
|
amount: 26
|
||||||
|
date: June 28, 2017
|
||||||
|
---
|
||||||
|
|
||||||
|
Hey everyone! Justin here. Based on the success of [my first proposal](https://forum.getmonero.org/22/completed-tasks/87610/justin-s-local-meetup-talks-proposal-1-valencia-graz-and-zagreb), I have continued to travel through Europe and speak to others about Monero. With this proposal, I am including travel costs for the following locations where I have already spoken at:
|
||||||
|
|
||||||
|
- [Warsaw, Poland: April 11](https://www.meetup.com/Warsaw-Bitcoin-Meetup-Group/events/238739999/)
|
||||||
|
- [Riga, Latvia: April 12](https://www.meetup.com/Riga-Bitcoin-Meetup/events/238920812/)
|
||||||
|
- [Wroclaw, Poland: April 13](https://www.meetup.com/Wroclaw-Blockchain-Meetup/events/238876892/)
|
||||||
|
- [Budapest, Hungary: May 12](https://www.meetup.com/BitcoinBudapest/events/239828785/)
|
||||||
|
- [Cologne, Germany: June 5](https://www.meetup.com/Bitcoin-Cologne/events/238950862/)
|
||||||
|
- [Bucharest, Romania: June 15](https://twitter.com/JEhrenhofer/status/875463371826487297)
|
||||||
|
- [Istanbul, Turkey: June 18](https://www.meetup.com/monero-turkey/events/240414046/)
|
||||||
|
- [Dublin, Ireland: June 26](https://www.meetup.com/Bitcoin-Dublin/events/240152422/)
|
||||||
|
|
||||||
|
I had a really fun time speaking at all these events. You can see PDFs of the used presentations here. Feel free to message me for the PowerPoint versions. You can view some of the recordings [here](https://www.youtube.com/playlist?list=PLBwW3kFqHdFg72DeOcNQ552W607ATQURq).
|
||||||
|
|
||||||
|
### Summary of Costs
|
||||||
|
|
||||||
|
I would like to allow for donations to cover some of the travel costs that I have incurred in the process of speaking about Monero. I was never paid to speak at any of these locations. Flights, trains, and hotels were the cheapest reasonable options.
|
||||||
|
|
||||||
|
Warsaw/Riga/Wroclaw: $750
|
||||||
|
|
||||||
|
Budapest: $145
|
||||||
|
|
||||||
|
Cologne: $380
|
||||||
|
|
||||||
|
Bucharest: $330
|
||||||
|
|
||||||
|
Istanbul: $325
|
||||||
|
|
||||||
|
Dublin: $725
|
||||||
|
|
||||||
|
NOT INCLUDED: Edinburgh, UK (Meetup cancelled)
|
||||||
|
|
||||||
|
Subtotal: $2,655
|
||||||
|
|
||||||
|
Minus Difference in Last Proposal's Gains (as promised): $1,612.53
|
||||||
|
|
||||||
|
Grand Total: $1,042.47 (asking amount)
|
||||||
|
|
||||||
|
Asking for 26 XMR.
|
||||||
|
|
||||||
|
Thank you everyone who donated to the previous proposal, and to those who donate to this one. If all things go according to plan, there should be one more proposal from me around the end of July.
|
||||||
41
forum-funding-system/proposals/kovri-end-user-docs.md
Normal file
41
forum-funding-system/proposals/kovri-end-user-docs.md
Normal file
@ -0,0 +1,41 @@
|
|||||||
|
---
|
||||||
|
layout: ffs-cp
|
||||||
|
title: Create End-User Kovri documentation
|
||||||
|
author: anonimal
|
||||||
|
amount: 100
|
||||||
|
date: July 15, 2016
|
||||||
|
---
|
||||||
|
|
||||||
|
<strong> \> What - describe the idea and how you plan to develop it </strong>
|
||||||
|
|
||||||
|
The idea is to create user-friendly non-technical Kovri documentation. Something that helps new users (who aren't necessarily developers) better understand what Kovri is and how it can/will be used.
|
||||||
|
|
||||||
|
I plan to develop this by implementing new documentation directly into my fork of the monero-site repository via Moneropedia entries (a similar, successful and completed proposal can be seen here) and then sending a pull-request when completed.
|
||||||
|
|
||||||
|
<strong> \> Who - who are you? Why do you think you can develop it, and why should the Monero community believe you can? </strong>
|
||||||
|
|
||||||
|
I am anonimal; and I am presently the lead developer of The Kovri I2P Router Project. With the help, guidance, and contributions of both I2P and Monero developers, myself and a handful of others came together to create Kovri.
|
||||||
|
|
||||||
|
This documentation proposal is yet another aspect of development that we have been tackling since the inception of Kovri. I believe that I can implement this proposal because of my experience with Kovri.
|
||||||
|
|
||||||
|
The Monero community should believe that I can implement this proposal for the following reasons:
|
||||||
|
|
||||||
|
- My tireless commitment to Kovri as proven over the passed 8+ months
|
||||||
|
- My recent contributions to bitmonero
|
||||||
|
- My contributions to the Monero project as a whole
|
||||||
|
|
||||||
|
<strong> \> Why - Why do you want to develop this? </strong>
|
||||||
|
|
||||||
|
I would like to see a robust documentation system that improves the lives of everyone in the Monero ecosystem. Something that provides a firm foundation for the most novice to the most experienced of users to use and understand Kovri technology. I believe that user-friendly Monerpedia can help build that foundation.
|
||||||
|
|
||||||
|
<strong> \> The Proposal and Milestones - It is difficult to describe how each proposal should be broken down into milestones, but only you (the developer) knows how long things can take, and knows how to break the task apart. Expiration - Make it apparent that a time limit exists for the proposal. </strong>
|
||||||
|
|
||||||
|
I propose a two milestones, 50 XMR for each milestone, for a total of 100 XMR. The first milestone being a completed first draft that I will keep in my fork. The second milestone being completed, uploaded, and verified content.
|
||||||
|
|
||||||
|
This proposal can, technically, be finished using my free time on the weekend. Realistically, because of scheduling, I need to vastly overestimate and give two weeks maximum for the first milestone and two weeks maximum for the 2nd milestone for a total of 1 month.
|
||||||
|
|
||||||
|
Realistically, this can be completed in less time than proposed - but I'd rather have this buffer for the sake of scheduling.
|
||||||
|
|
||||||
|
All feedback is welcome. I would like to hear any specifics or requests from the community before I dive into this.
|
||||||
|
|
||||||
|
Edit: also see https://www.reddit.com/r/Monero/comments/4sx825/kovri_enduser_documentation_proposal_now_open_for/
|
||||||
45
forum-funding-system/proposals/monero-integrations.md
Normal file
45
forum-funding-system/proposals/monero-integrations.md
Normal file
@ -0,0 +1,45 @@
|
|||||||
|
---
|
||||||
|
layout: ffs-cp
|
||||||
|
title: Monero integrations with web apps
|
||||||
|
author: serhack
|
||||||
|
amount: 126
|
||||||
|
date: May 30, 2017
|
||||||
|
---
|
||||||
|
|
||||||
|
|
||||||
|
### WHAT: MONERO INTEGRATIONS IN WEB-APPS
|
||||||
|
|
||||||
|
UPDATED: ADDED 1ST MILESTONE
|
||||||
|
|
||||||
|
We are living in a world that have a lot of integrations with web-apps: you should think slack, github.. Every web app has integrations. I think monero will be popular if we develop some plugins like for Wordpress, Prestashop.
|
||||||
|
|
||||||
|
My plan is developing integrations (plugins, add-ons) for monero; My goal is everyone will support monero as payment.
|
||||||
|
|
||||||
|
At the moment I'm discussing with community about how plugin can communicate with daemon of Monero. The plugins/addons will developed by me and with PHP, html and the framework of Web App. Please if you have an idea about this, please post it! I will implement best ideas.
|
||||||
|
|
||||||
|
### WHO
|
||||||
|
|
||||||
|
Hello, I'm Nico aka SerHack. I am a web developer freelancer, sysadmin and I worked in the past as marketing coordinator for IT company. I'm from Italy and this project is one of the best project that I never see. I believe in open source projects like Monero :) If anyone doubts of my job, here a list of my work:
|
||||||
|
|
||||||
|
SerNico Website (I need to update it :p ) SerWebHost Shared Hosting company Fabrizio Cotugno Graphic Freelancer
|
||||||
|
|
||||||
|
Warning: I have worked in a lot of websites, I can't post fully list here. If you wanna it, please pm me :)
|
||||||
|
|
||||||
|
### WHY
|
||||||
|
|
||||||
|
I would pay in a shop by XMR, as easy as bitcoin payment. Monero will become a great project with integration! I would help some merchants that haven't got any php skills I'm working as a freelancer: actually I need only 0.75 XMR /hours (currently like 15 dollars). For each intregration, there will be a milestone.
|
||||||
|
|
||||||
|
I can work on Monero for roughly 3-4 hours per day. I will write a full log of my activity. So you can follow my progress. I will go to St. Moritz and Cesenatico for 20 days in total during June :).
|
||||||
|
|
||||||
|
Milestone #1: Days: around 16
|
||||||
|
16 x 3-4 hours x 0.75 = around 36 XMR
|
||||||
|
- PHP Library
|
||||||
|
- JSON API
|
||||||
|
|
||||||
|
Milestone #2: Days: around 30
|
||||||
|
30 x 3-4 hours x 0.75 = around 90 XMR - Starting Wordpress plugin
|
||||||
|
- Starting Prestashop plugin
|
||||||
|
|
||||||
|
**Funding needed: 126 XMR**
|
||||||
|
|
||||||
|
Feedbacks: https://www.reddit.com/r/Monero/comments/6g9ps5/web_integrations_update/
|
||||||
43
forum-funding-system/proposals/monero-subforum-8btc.md
Normal file
43
forum-funding-system/proposals/monero-subforum-8btc.md
Normal file
@ -0,0 +1,43 @@
|
|||||||
|
---
|
||||||
|
layout: ffs-cp
|
||||||
|
title: Funding for a Monero subforum on the largest chinese BTC forum 8BTC
|
||||||
|
author: firperfect
|
||||||
|
amount: 570
|
||||||
|
date: June 6, 2017
|
||||||
|
---
|
||||||
|
|
||||||
|
|
||||||
|
### who am i:
|
||||||
|
|
||||||
|
translate gui wallet to Simplified Chinese [monero-core pull 670](https://github.com/monero-project/monero-core/pull/670)
|
||||||
|
|
||||||
|
admin of china xmr-chat group, 2000+ followers (tencent qq group number: 605809242, 584465213)
|
||||||
|
|
||||||
|
### what:
|
||||||
|
|
||||||
|
There is no Chinese discussion forum and bbs specifically for monero. Monero only occasionally appears in a discussion or an article regarding the anonymity of Bitcoin. Currently, most of monero beginners in China have no technical background and poor English proficiency, which greatly limits their participation in the monero.
|
||||||
|
|
||||||
|
To increase monero's media exposure while allowing more people to know monero, I propose to cooperate with 8btc, which is china's most well-known cryptocurrencies discussion forum, and open a separate forum for monero on the 8btc.
|
||||||
|
|
||||||
|
Currently, 8btc has more than 50K registered members and the 3000+ number of active people per day.
|
||||||
|
|
||||||
|
Cooperating with 8btc can gain wide attentions for XMR to the largest extent.
|
||||||
|
|
||||||
|
I will be the administrator of the discussion forum for monero. At the same time, I will write a series of posts about FAQ, user guide for wallet and mining, translate for roadmap and news...
|
||||||
|
|
||||||
|
Moreover, as for any Chinese localization need of the monero community, I can organize people to translate. Thus, the progress of the monero can spread to the Chinese community at the highest speed.
|
||||||
|
|
||||||
|
Here are all important advantages short summarized which 8BTC and China would bring to Monero:
|
||||||
|
|
||||||
|
- More nodes, stronger network
|
||||||
|
- Need for chinese exchanges (Okcoin, Huobi) to offer XMR for trade
|
||||||
|
- Price and liquidity rise through new investors
|
||||||
|
- More developers, bigger community, more donations, more development
|
||||||
|
|
||||||
|
Here are all important advantages summarized which 8BTC would bring to Monero: [https://www.reddit.com/r/Monero/comments/6flqvd/lets_fund_xmr_adoptation_in_china_monero_on_the/](https://www.reddit.com/r/Monero/comments/6flqvd/lets_fund_xmr_adoptation_in_china_monero_on_the/)
|
||||||
|
|
||||||
|
### price:
|
||||||
|
|
||||||
|
The costs for the forum are 170.000 chinese Yuan, around 570 XMR for 12 months as the 8BTC.com service is not free.
|
||||||
|
|
||||||
|
this is donation monero address: wait for the FFS proposal then we will start to collect the fund for this, the XMR core team can then collect the funds, act as escrow and provide the XMR to 8BTC.
|
||||||
@ -0,0 +1,22 @@
|
|||||||
|
---
|
||||||
|
layout: ffs-cp
|
||||||
|
title: A continuation for all purpose programming of what needs to get done in monero
|
||||||
|
author: moneromooo
|
||||||
|
amount: 18,000
|
||||||
|
date: October 31, 2015
|
||||||
|
---
|
||||||
|
|
||||||
|
|
||||||
|
I have now finished the second to last milestone in my current contract. I'd originally committed to a short enough time in case it wouldn't work out well, but I think this has worked quite well, so I'm proposing a new contract to follow as soon as the last milestone is done. I have had several requests about applying for an extension, so I think some people at least are keen to see that happening :)
|
||||||
|
|
||||||
|
This extension will be a pretty similar deal, but for a longer time period: a set amount of time spent working on monero. I will up the price a bit (both because it's been taking so much of my free time, and because the price of monero has gone down since then), and I will commit to more time in total, with the same average weekly time target. Even though I consistently managed at least equal to the target 10 hours a week so far, this may or may not continue.
|
||||||
|
|
||||||
|
I propose the following:
|
||||||
|
|
||||||
|
- 450 hours spent working on monero (previous was 260)
|
||||||
|
- A guideline of about 10 hours a week, as previously, but this is only indicative
|
||||||
|
- 40 monero per hour (previous was 30, but monero was also valued about a quarter higher in fiat terms)
|
||||||
|
- 10 milestones, at regular 45 hours intervals (previous was 6 every 45)
|
||||||
|
so a total of 18000 monero (previous was 7800)
|
||||||
|
|
||||||
|
To be started as milestones get funded. There's a 12.92 leftover in the previous fund, it can probably be used to seed this one.
|
||||||
25
forum-funding-system/proposals/more-mooo-coding-goodness.md
Normal file
25
forum-funding-system/proposals/more-mooo-coding-goodness.md
Normal file
@ -0,0 +1,25 @@
|
|||||||
|
---
|
||||||
|
layout: ffs-cp
|
||||||
|
title: More mooo coding goodness
|
||||||
|
author: moneromooo
|
||||||
|
amount: 1800
|
||||||
|
date: October 8, 2016
|
||||||
|
---
|
||||||
|
|
||||||
|
As most of you know, I am one of the main contributors to Monero.
|
||||||
|
|
||||||
|
My previous contract finished in july, and I have since continued contributing, mostly to finish off the RingCT integration, as well as various other bits and bobs.
|
||||||
|
|
||||||
|
As I said, "Once the summer is out, I might go for another similar contract.". I have to admit I was kind of browbeaten by rct and was looking forward to sunshine with no pressure. I'm now ready to commit to more work to make Monero better, if the community wants it, with a new contract along the lines of the previous one:
|
||||||
|
|
||||||
|
- 450 hours spent working on monero (previous was 450)
|
||||||
|
- A guideline of about 10 hours a week, as previously, but this is only indicative [1]
|
||||||
|
- 4 monero per hour (previous was 40 [2])
|
||||||
|
- 10 milestones, at regular 45 hours intervals (previous was 10 every 45)
|
||||||
|
- so a total of 1800 monero (previous was 18000)
|
||||||
|
|
||||||
|
[1] Over the last two contracts I have averaged a bit above that, but the variance is high-ish.
|
||||||
|
|
||||||
|
[2] Monero was cheaper then. The fiat rate is also a bit higher (~26 USD/hour vs ~19 USD/hour, but I have shown I do good work, the previous rate was pretty low, and the downside risk is a lot higher now).
|
||||||
|
|
||||||
|
As before, I will not commit to any particular piece of work, but will work on whatever needs doing to further Monero. Currently, my target is rct verification performance, and then there is multisig, though I will need help for someone who understands the crypto well to guide me.
|
||||||
63
forum-funding-system/proposals/official-qt-gui.md
Normal file
63
forum-funding-system/proposals/official-qt-gui.md
Normal file
@ -0,0 +1,63 @@
|
|||||||
|
---
|
||||||
|
layout: ffs-cp
|
||||||
|
title: The official Qt GUI Project
|
||||||
|
author: othe
|
||||||
|
amount: 14,000
|
||||||
|
date: February 2, 2016
|
||||||
|
---
|
||||||
|
|
||||||
|
First of all, this idea is posted on behalf of the developer.
|
||||||
|
|
||||||
|
### What will be done?
|
||||||
|
|
||||||
|
Initially, the hours that are funded will be used to complete the official GUI, of which the sneak peaks have been around for a while now -> https://imgur.com/a/ERheR. In addition, one of the goals is to make the architecture such that it will be fairly easy allow plugins. For example, this architecture will allow xmr.to to be plugged into the GUI such that you can pay every Bitcoin address from your Monero (GUI) wallet. Another goal is to make the GUI portable to smartphones. The hours that remain after having completed the GUI will be used to work on other features. There should be a better estimate of hours needed to complete the GUI once the work really has started.
|
||||||
|
|
||||||
|
This is going to be a lot of work as we want to have a really flexible UI with a great plugin architecture and useability that is lacking all current cryptocurrency GUIs.
|
||||||
|
|
||||||
|
### Who will work on this task?
|
||||||
|
|
||||||
|
mbg033 (Ilya Kitaev) will work on this. Ilya is a cross-platform C/C++/Qt software developer 7+ years of experience in software development for Linux and Windows platforms. Furthermore, he is familiar with the following additional skills/technologies: CEF (Chromium Embedded Framework), Python, Lua, Ruby, Objective-C, PHP, Java, Javascript, SQL, WinAPI, posix API, EPICS, Modbus, OPC, networking, multi-threading, make, cmake, automake, autoconf.
|
||||||
|
|
||||||
|
### Why?
|
||||||
|
|
||||||
|
The CLI has long been seen as a hurdle to adoption. The new Hydrogen Helix release (mainly the database) and the 0MQ work allows for a GUI implementation to be completed. In other words, the codebase is stable enough for a GUI release. With this official GUI, Monero will be better usable and accessible for the average Joe. Also, it will make promoting Monero more easy and will allow us to expand the user base.
|
||||||
|
|
||||||
|
### The Proposal and Milestones
|
||||||
|
|
||||||
|
The proposal is to raise 14,000 XMR for 280 hours of work, which is approximately 25.00$ per hour. Ilya will work 10 hours per week at the beginning, expanding into more hours per week later when some other project is finished. We will will make a bi-weekly summary of what he has done. Optionally, an extension can be discussed / proposed once his contract ends.
|
||||||
|
|
||||||
|
** His work and the activity can be followed on: **
|
||||||
|
|
||||||
|
[https://github.com/mbg033?tab=activity](https://github.com/mbg033?tab=activity)
|
||||||
|
|
||||||
|
[https://github.com/mbg033/monero-core](https://github.com/mbg033/monero-core)
|
||||||
|
|
||||||
|
[https://github.com/monero-project/monero-core](https://github.com/monero-project/monero-core)
|
||||||
|
|
||||||
|
Fluffypony and me will help him and work together on the implementation and will oversee everything - as always unpaid :P.
|
||||||
|
|
||||||
|
So far we already did some stuff like completing the language selection in the wizard: 
|
||||||
|
|
||||||
|
### Some more screenshots:
|
||||||
|
|
||||||
|
https://www.evernote.com/l/AhBiaAEvDzhHd5p2l4Vg90Ff3PmnxzUCzPA
|
||||||
|
|
||||||
|
https://www.evernote.com/l/AhAvGRmGZzZC7I5-VBmaMMr9LazAAsP6VPE
|
||||||
|
|
||||||
|
https://www.evernote.com/l/AhDu23hm5y1B652JSUuWd5iip96kRHPJrGE
|
||||||
|
|
||||||
|
https://www.evernote.com/l/AhAFgFgjW0tJUpiTaJjw1-DvdSgkQ0n2w1o
|
||||||
|
|
||||||
|
https://www.evernote.com/l/AhCZGE9r-3hERpy1pvYVgMEj_yZ4pxQyE4I
|
||||||
|
|
||||||
|
https://www.evernote.com/l/AhD0SgwPv5ZN64VbkL3RNvq2b-Ikt4xtzfY
|
||||||
|
|
||||||
|
https://www.evernote.com/l/AhBrep2IOE1Fl6q0x0HD5DUsvQlRcQ9mKRk
|
||||||
|
|
||||||
|
https://www.evernote.com/l/AhBCfYAqKaBEHrzbK_owLA-CFvJA5wNgreE
|
||||||
|
|
||||||
|
https://www.evernote.com/l/AhB8sCz8qJpPWIq2_Wayss2fCy9Iq5SOLhA
|
||||||
|
|
||||||
|
https://www.evernote.com/l/AhCrtvSWmvdLQpSLkZb34pD3a1zEDSsMQAc
|
||||||
|
|
||||||
|
https://www.evernote.com/l/AhApVs-0GQZIzYcWA_Lb0Gfjzu8G1I7-kUU
|
||||||
57
forum-funding-system/proposals/release-pool-software.md
Normal file
57
forum-funding-system/proposals/release-pool-software.md
Normal file
@ -0,0 +1,57 @@
|
|||||||
|
---
|
||||||
|
layout: ffs-cp
|
||||||
|
title: Release of new/updated pool software
|
||||||
|
author: Snipa22
|
||||||
|
amount: 800
|
||||||
|
date: February 2, 2017
|
||||||
|
---
|
||||||
|
|
||||||
|
### What
|
||||||
|
|
||||||
|
An updated pool for usage within the XMR community in order to help continue growing smaller pools within the Monero Community. This project was originally spawned off of the project by Wolf0 & OhGodAGirl to replace and improve the XMR Stratum, but provides a baseline to work from for more modern implementations of the pool software.
|
||||||
|
|
||||||
|
This also includes many features that are valuable to miners at this time, including support for Integrated Addresses, Payment ID Based payouts, Per-Worker Monitoring, and Per-Worker E-mail Notifications.
|
||||||
|
|
||||||
|
### Who
|
||||||
|
|
||||||
|
I'm Snipa on IRC, I've been a professional Linux sysadmin for the past 10-ish years, developing python based software for the past 4-5, and work primarily as a DevOps engineer in my full time position, maintaining servers and backend code, while providing project guidance for our main workflow at my FT position.
|
||||||
|
|
||||||
|
This has been my first serious foray into the XMR community, as well, into NodeJS, and while I've stumbled quite a bit, I feel like this is a product I am pleased to release to the community to play with and see how they like it as well.
|
||||||
|
|
||||||
|
I am a regular in the #monero-pools channel, and have provided assistance with things such as interim-pool fixes for the 127 transaction bug, information about the Claymore SSL implementation, and the certs (Unsigned certs ftw!) required for this implementation. I've also provided assistance to new pool ops looking to get up and going. I thoroughly believe that XMR is stronger for the small pool ops, and it's my goal to get this code out to make it easier and simpler to setup. I've also provided first-pass documentation on the current pool API's, as they're undocumented: [https://cryptonote-xmr-pool-api.restlet.io](https://cryptonote-xmr-pool-api.restlet.io/)
|
||||||
|
|
||||||
|
### Why
|
||||||
|
|
||||||
|
This was spawned as a pool target to replace the issues with Proportional payouts, such as pool hoppers, as used by Clintar and Zone117x's pools, allowing for better payouts for miners who are interested in long-term profit. This was also to be the target for the new Stratum Protocol as to be developed by Wolf0 & OhGodAGirl. This code leverages many stable NodeJS libraries, fixes to versions, and uses the current 6.x.x LTS release. This also offers a number of new ways to setup mining pools, including PPS and Solo mining, for miners who like to know exactly what they'll get paid, and miners who want to gamble and roll the dice while mining.
|
||||||
|
|
||||||
|
### The Proposal/Milestones
|
||||||
|
|
||||||
|
The bulk of this code is complete at this time, and is running a live pool at [https://xmrpool.net](https://xmrpool.net), which serves as the living, breathing example of what this pool is able to accomplish.
|
||||||
|
|
||||||
|
#### Milestone 1
|
||||||
|
|
||||||
|
Target: Release of the pool source in it's current form, including SQL schemas and all things required to setup and run the pool with minimal documentation.
|
||||||
|
|
||||||
|
At this point, I've put approximately 40-60 hours of work into the development of this pool, lost a small chunk of XMR to double-payout bugs (Which have been fixed), ordered approximately 1 BTC worth of NH hash time to stress test, load-test, and verify functionality of the pool on the production network. The API is decently well documented at: [https://cryptonote-pool-api.restlet.io/](https://cryptonote-pool-api.restlet.io/) and will be released in full Swagger format for anyone looking to integrate with the pool API.
|
||||||
|
|
||||||
|
As such, I'm setting a target of 600 XMR for this milestone, while high, this has been a very time consuming project. This is also conditionally to assist in paying out Mesh00 for his work on the frontend, and Wolf0 & OhGodAGirl to release the AES-NI sped-up version of the multi-hashing library that this pool takes full advantage of, allowing it to run on much smaller servers (VPS) while still doing extensive share verification and validation.
|
||||||
|
|
||||||
|
#### Milestone 2
|
||||||
|
|
||||||
|
Target: Finishing admin-related APIs and Frontend, moving to Websockets for statistical information and frontend data pushes, rather than pulls
|
||||||
|
|
||||||
|
At this time, the pool does not provide a dedicated admin interface or APIs, I have found these to be largely not-needed, as I am a full time system administrator. Overall, these should be fairly simple, as they're mostly accessing data that's in SQL anyway, as well as verifing wallet-state, etc. Adding websockets is non-trivial to a project of this nature, as the current architecture is not specifically designed to accept websockets, however, due to the use of LMDB and it's zero-copy systems, all of the core daemons share a universal cache that can be used readily to deal with passing data back and forth between applications.
|
||||||
|
|
||||||
|
As such, I am setting a target of 150 XMR for this milestone, to fund both frontend and backend work on this project.
|
||||||
|
|
||||||
|
#### Milestone 3
|
||||||
|
|
||||||
|
Target: Documenting and polishing the installation process
|
||||||
|
|
||||||
|
While not complex, and I have scripts for the deployment of this system in my multi-server environment, this would allow a new user to execute a single script to bring online a pool with a minimum of questions being asked. The goal here is to allow small pool ops to bring online pools more quickly. This is not required, and installation support will always be provided in #monero-pools
|
||||||
|
|
||||||
|
As such, I am setting a target of 50 XMR for this milestone.
|
||||||
|
|
||||||
|
### Closing
|
||||||
|
|
||||||
|
This FFS is mostly to help me recoup the time, funding provided into this project, and provide funding to those who have opted to help through this process.
|
||||||
@ -2,6 +2,8 @@
|
|||||||
layout: ffs-cp
|
layout: ffs-cp
|
||||||
title: What is Monero? is produced and open-sourced
|
title: What is Monero? is produced and open-sourced
|
||||||
author: savandra
|
author: savandra
|
||||||
|
amount: 72
|
||||||
|
date: October 12, 2016
|
||||||
---
|
---
|
||||||
|
|
||||||
Hello everyone!
|
Hello everyone!
|
||||||
|
|||||||
Binary file not shown.
Loading…
Reference in New Issue
Block a user