From 0c9c9110910f485a292f331e3377382c8b76df86 Mon Sep 17 00:00:00 2001 From: Eric Szeto Date: Tue, 5 Dec 2017 07:02:47 -0800 Subject: [PATCH 01/43] Add new Goods and Artist Store merchants --- _data/merchants.yml | 99 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 99 insertions(+) diff --git a/_data/merchants.yml b/_data/merchants.yml index 7ce3f701..80276eea 100644 --- a/_data/merchants.yml +++ b/_data/merchants.yml @@ -189,6 +189,8 @@ merchants: - name: All For Crypto url: https://allforcrypto.com + - name: Cannabis Cup + url: https://shop.cannabiscup.com/ - name: Cellphone and laptop repair online store in Sweden url: http://www.LagaiPhone.se - name: CryptoMercado - coffee and snacks @@ -209,6 +211,10 @@ url: http://investmentart.org/ - name: Mushroom cultures, mushroom growing supplies, seeds url: https://www.vesp.co/Fungible + - name: Plazmatic + url: http://www.plazmatic.com + - name: Project Coral Reef Store + url: https://shop.projectcoralreef.com - name: SecPoint IT Security Products url: https://shop.secpoint.com/shop/frontpage.html - name: SilverRound.com - Gold and Silver Dealer @@ -228,3 +234,96 @@ url: https://safedice.com - name: XMRLotto.com url: https://xmrlotto.com +- category: Artist Stores + id: stores + merchants: + - name: A Perfect Circle + url: https://store.aperfectcircle.com + - name: Alice Cooper + url: https://shop.alicecooper.com + - name: Anthrax + url: https://shop.anthrax.com + - name: Awolnation + url: https://store.awolnationmusic.com + - name: Backstreet Boys + url: https://store.backstreetboys.com + - name: Butch Walker + url: https://store.butchwalker.com + - name: BUSH + url: https://official-bush-store.myshopify.com + - name: Crosses + url: https://shop.crossesmusic.com + - name: Dixie Chicks + url: https://shop.dixiechicks.com + - name: Dolly Parton + url: https://shop.dollyparton.com + - name: Fall Out Boy + url: https://store.falloutboy.com + - name: Fare Thee Well (Grateful Dead) + url: https://www.faretheewellmerch.com + - name: Five Finger Death Punch + url: https://fivefingerdeathpunch.com/collections/everything + - name: G Eazy + url: https://g-eazystore.com + - name: Ghost + url: https://shop.ghost-official.com + - name: Godsmack + url: http://shop.godsmack.com + - name: HIM + url: https://shop.heartagram.com + - name: Jason Aldean + url: https://store.jasonaldean.com + - name: Judas Priest + url: https://www.shopjudaspriest.com + - name: Kaskade + url: https://shopkaskade.com + - name: L2M + url: https://store.l2mofficial.com + - name: Lamb of God + url: https://shop.lamb-of-god.com + - name: Lana Del Rey + url: https://store.lanadelrey.com + - name: Lumineers + url: https://store.thelumineers.com + - name: Mariah Carey + url: https://mariahpride.com + - name: Marilyn Manson + url: https://store.marilynmanson.com + - name: Mastodon + url: https://shop.mastodonrocks.com + - name: Ministry + url: https://store.ministryband.com + - name: Morrissey + url: https://us.mporium.org + - name: Motley Crue + url: https://store.motley.com + - name: Motorhead + url: https://shop.imotorhead.com + - name: Panic! at the Disco + url: https://store.panicatthedisco.com + - name: Purism + url: https://puri.sm + - name: Rival Sons + url: https://rivalsons.myshopify.com + - name: Rob Zombie + url: https://shop.robzombie.com + - name: Roger Waters + url: https://store.roger-waters.com + - name: Scorpions + url: https://store.the-scorpions.com + - name: SIA + url: https://shop.siamusic.net + - name: Sixx:A.M. + url: https://store.sixxammusic.com + - name: Slayer + url: https://store.slayer.net + - name: The B-52s + url: https://theb52s.manheadmerch.com + - name: Thomas Rhett + url: https://thomasrhettstore.com + - name: Toby Keith + url: https://toby-keith-store.myshopify.com + - name: Train + url: https://store.savemesanfrancisco.com + - name: Weezer + url: https://weezerwebstore.com \ No newline at end of file -- GitLab From 145b93de1b808a96c2de5ec688201ff80b24166a Mon Sep 17 00:00:00 2001 From: Eric Szeto Date: Tue, 12 Dec 2017 11:35:29 -0800 Subject: [PATCH 02/43] Revert "Add new Goods and Artist Store merchants" This reverts commit 0c9c9110910f485a292f331e3377382c8b76df86. --- _data/merchants.yml | 99 --------------------------------------------- 1 file changed, 99 deletions(-) diff --git a/_data/merchants.yml b/_data/merchants.yml index 80276eea..7ce3f701 100644 --- a/_data/merchants.yml +++ b/_data/merchants.yml @@ -189,8 +189,6 @@ merchants: - name: All For Crypto url: https://allforcrypto.com - - name: Cannabis Cup - url: https://shop.cannabiscup.com/ - name: Cellphone and laptop repair online store in Sweden url: http://www.LagaiPhone.se - name: CryptoMercado - coffee and snacks @@ -211,10 +209,6 @@ url: http://investmentart.org/ - name: Mushroom cultures, mushroom growing supplies, seeds url: https://www.vesp.co/Fungible - - name: Plazmatic - url: http://www.plazmatic.com - - name: Project Coral Reef Store - url: https://shop.projectcoralreef.com - name: SecPoint IT Security Products url: https://shop.secpoint.com/shop/frontpage.html - name: SilverRound.com - Gold and Silver Dealer @@ -234,96 +228,3 @@ url: https://safedice.com - name: XMRLotto.com url: https://xmrlotto.com -- category: Artist Stores - id: stores - merchants: - - name: A Perfect Circle - url: https://store.aperfectcircle.com - - name: Alice Cooper - url: https://shop.alicecooper.com - - name: Anthrax - url: https://shop.anthrax.com - - name: Awolnation - url: https://store.awolnationmusic.com - - name: Backstreet Boys - url: https://store.backstreetboys.com - - name: Butch Walker - url: https://store.butchwalker.com - - name: BUSH - url: https://official-bush-store.myshopify.com - - name: Crosses - url: https://shop.crossesmusic.com - - name: Dixie Chicks - url: https://shop.dixiechicks.com - - name: Dolly Parton - url: https://shop.dollyparton.com - - name: Fall Out Boy - url: https://store.falloutboy.com - - name: Fare Thee Well (Grateful Dead) - url: https://www.faretheewellmerch.com - - name: Five Finger Death Punch - url: https://fivefingerdeathpunch.com/collections/everything - - name: G Eazy - url: https://g-eazystore.com - - name: Ghost - url: https://shop.ghost-official.com - - name: Godsmack - url: http://shop.godsmack.com - - name: HIM - url: https://shop.heartagram.com - - name: Jason Aldean - url: https://store.jasonaldean.com - - name: Judas Priest - url: https://www.shopjudaspriest.com - - name: Kaskade - url: https://shopkaskade.com - - name: L2M - url: https://store.l2mofficial.com - - name: Lamb of God - url: https://shop.lamb-of-god.com - - name: Lana Del Rey - url: https://store.lanadelrey.com - - name: Lumineers - url: https://store.thelumineers.com - - name: Mariah Carey - url: https://mariahpride.com - - name: Marilyn Manson - url: https://store.marilynmanson.com - - name: Mastodon - url: https://shop.mastodonrocks.com - - name: Ministry - url: https://store.ministryband.com - - name: Morrissey - url: https://us.mporium.org - - name: Motley Crue - url: https://store.motley.com - - name: Motorhead - url: https://shop.imotorhead.com - - name: Panic! at the Disco - url: https://store.panicatthedisco.com - - name: Purism - url: https://puri.sm - - name: Rival Sons - url: https://rivalsons.myshopify.com - - name: Rob Zombie - url: https://shop.robzombie.com - - name: Roger Waters - url: https://store.roger-waters.com - - name: Scorpions - url: https://store.the-scorpions.com - - name: SIA - url: https://shop.siamusic.net - - name: Sixx:A.M. - url: https://store.sixxammusic.com - - name: Slayer - url: https://store.slayer.net - - name: The B-52s - url: https://theb52s.manheadmerch.com - - name: Thomas Rhett - url: https://thomasrhettstore.com - - name: Toby Keith - url: https://toby-keith-store.myshopify.com - - name: Train - url: https://store.savemesanfrancisco.com - - name: Weezer - url: https://weezerwebstore.com \ No newline at end of file -- GitLab From 9172438400b06b996cdebf315a34b28d7ad5c051 Mon Sep 17 00:00:00 2001 From: Eric Szeto Date: Tue, 12 Dec 2017 11:45:24 -0800 Subject: [PATCH 03/43] Add Project Coral Reef Store to goods category --- _data/merchants.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/_data/merchants.yml b/_data/merchants.yml index 7ce3f701..0b448d09 100644 --- a/_data/merchants.yml +++ b/_data/merchants.yml @@ -209,6 +209,8 @@ url: http://investmentart.org/ - name: Mushroom cultures, mushroom growing supplies, seeds url: https://www.vesp.co/Fungible + - name: Project Coral Reef Store + url: http://www.projectcoralreef.com/all-stores - name: SecPoint IT Security Products url: https://shop.secpoint.com/shop/frontpage.html - name: SilverRound.com - Gold and Silver Dealer -- GitLab From a2047a346df637f45a43ac7a32eac4ef6a609f99 Mon Sep 17 00:00:00 2001 From: Eric Szeto Date: Tue, 5 Dec 2017 07:02:47 -0800 Subject: [PATCH 04/43] Add new Goods and Artist Store merchants --- _data/merchants.yml | 99 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 99 insertions(+) diff --git a/_data/merchants.yml b/_data/merchants.yml index 00543bcd..549182e6 100644 --- a/_data/merchants.yml +++ b/_data/merchants.yml @@ -195,6 +195,8 @@ merchants: - name: All For Crypto url: https://allforcrypto.com + - name: Cannabis Cup + url: https://shop.cannabiscup.com/ - name: Cellphone and laptop repair online store in Sweden url: http://www.LagaiPhone.se - name: Crypto Armory - ammunition for cryptocurrency at a competitive rate @@ -219,6 +221,10 @@ url: http://investmentart.org/ - name: Mushroom cultures, mushroom growing supplies, seeds url: https://www.vesp.co/Fungible + - name: Plazmatic + url: http://www.plazmatic.com + - name: Project Coral Reef Store + url: https://shop.projectcoralreef.com - name: SecPoint IT Security Products url: https://shop.secpoint.com/shop/frontpage.html - name: SilverRound.com - Gold and Silver Dealer @@ -240,3 +246,96 @@ url: https://safedice.com - name: XMRLotto.com url: https://xmrlotto.com +- category: Artist Stores + id: stores + merchants: + - name: A Perfect Circle + url: https://store.aperfectcircle.com + - name: Alice Cooper + url: https://shop.alicecooper.com + - name: Anthrax + url: https://shop.anthrax.com + - name: Awolnation + url: https://store.awolnationmusic.com + - name: Backstreet Boys + url: https://store.backstreetboys.com + - name: Butch Walker + url: https://store.butchwalker.com + - name: BUSH + url: https://official-bush-store.myshopify.com + - name: Crosses + url: https://shop.crossesmusic.com + - name: Dixie Chicks + url: https://shop.dixiechicks.com + - name: Dolly Parton + url: https://shop.dollyparton.com + - name: Fall Out Boy + url: https://store.falloutboy.com + - name: Fare Thee Well (Grateful Dead) + url: https://www.faretheewellmerch.com + - name: Five Finger Death Punch + url: https://fivefingerdeathpunch.com/collections/everything + - name: G Eazy + url: https://g-eazystore.com + - name: Ghost + url: https://shop.ghost-official.com + - name: Godsmack + url: http://shop.godsmack.com + - name: HIM + url: https://shop.heartagram.com + - name: Jason Aldean + url: https://store.jasonaldean.com + - name: Judas Priest + url: https://www.shopjudaspriest.com + - name: Kaskade + url: https://shopkaskade.com + - name: L2M + url: https://store.l2mofficial.com + - name: Lamb of God + url: https://shop.lamb-of-god.com + - name: Lana Del Rey + url: https://store.lanadelrey.com + - name: Lumineers + url: https://store.thelumineers.com + - name: Mariah Carey + url: https://mariahpride.com + - name: Marilyn Manson + url: https://store.marilynmanson.com + - name: Mastodon + url: https://shop.mastodonrocks.com + - name: Ministry + url: https://store.ministryband.com + - name: Morrissey + url: https://us.mporium.org + - name: Motley Crue + url: https://store.motley.com + - name: Motorhead + url: https://shop.imotorhead.com + - name: Panic! at the Disco + url: https://store.panicatthedisco.com + - name: Purism + url: https://puri.sm + - name: Rival Sons + url: https://rivalsons.myshopify.com + - name: Rob Zombie + url: https://shop.robzombie.com + - name: Roger Waters + url: https://store.roger-waters.com + - name: Scorpions + url: https://store.the-scorpions.com + - name: SIA + url: https://shop.siamusic.net + - name: Sixx:A.M. + url: https://store.sixxammusic.com + - name: Slayer + url: https://store.slayer.net + - name: The B-52s + url: https://theb52s.manheadmerch.com + - name: Thomas Rhett + url: https://thomasrhettstore.com + - name: Toby Keith + url: https://toby-keith-store.myshopify.com + - name: Train + url: https://store.savemesanfrancisco.com + - name: Weezer + url: https://weezerwebstore.com \ No newline at end of file -- GitLab From 7859a57cd9abbd64087d57656c16922fde4c64ce Mon Sep 17 00:00:00 2001 From: Eric Szeto Date: Tue, 12 Dec 2017 11:35:29 -0800 Subject: [PATCH 05/43] Add Project Coral Reef Store to goods category --- _data/merchants.yml | 99 +-------------------------------------------- 1 file changed, 1 insertion(+), 98 deletions(-) diff --git a/_data/merchants.yml b/_data/merchants.yml index 549182e6..0c11c8ee 100644 --- a/_data/merchants.yml +++ b/_data/merchants.yml @@ -195,8 +195,6 @@ merchants: - name: All For Crypto url: https://allforcrypto.com - - name: Cannabis Cup - url: https://shop.cannabiscup.com/ - name: Cellphone and laptop repair online store in Sweden url: http://www.LagaiPhone.se - name: Crypto Armory - ammunition for cryptocurrency at a competitive rate @@ -221,10 +219,8 @@ url: http://investmentart.org/ - name: Mushroom cultures, mushroom growing supplies, seeds url: https://www.vesp.co/Fungible - - name: Plazmatic - url: http://www.plazmatic.com - name: Project Coral Reef Store - url: https://shop.projectcoralreef.com + url: http://www.projectcoralreef.com/all-stores - name: SecPoint IT Security Products url: https://shop.secpoint.com/shop/frontpage.html - name: SilverRound.com - Gold and Silver Dealer @@ -246,96 +242,3 @@ url: https://safedice.com - name: XMRLotto.com url: https://xmrlotto.com -- category: Artist Stores - id: stores - merchants: - - name: A Perfect Circle - url: https://store.aperfectcircle.com - - name: Alice Cooper - url: https://shop.alicecooper.com - - name: Anthrax - url: https://shop.anthrax.com - - name: Awolnation - url: https://store.awolnationmusic.com - - name: Backstreet Boys - url: https://store.backstreetboys.com - - name: Butch Walker - url: https://store.butchwalker.com - - name: BUSH - url: https://official-bush-store.myshopify.com - - name: Crosses - url: https://shop.crossesmusic.com - - name: Dixie Chicks - url: https://shop.dixiechicks.com - - name: Dolly Parton - url: https://shop.dollyparton.com - - name: Fall Out Boy - url: https://store.falloutboy.com - - name: Fare Thee Well (Grateful Dead) - url: https://www.faretheewellmerch.com - - name: Five Finger Death Punch - url: https://fivefingerdeathpunch.com/collections/everything - - name: G Eazy - url: https://g-eazystore.com - - name: Ghost - url: https://shop.ghost-official.com - - name: Godsmack - url: http://shop.godsmack.com - - name: HIM - url: https://shop.heartagram.com - - name: Jason Aldean - url: https://store.jasonaldean.com - - name: Judas Priest - url: https://www.shopjudaspriest.com - - name: Kaskade - url: https://shopkaskade.com - - name: L2M - url: https://store.l2mofficial.com - - name: Lamb of God - url: https://shop.lamb-of-god.com - - name: Lana Del Rey - url: https://store.lanadelrey.com - - name: Lumineers - url: https://store.thelumineers.com - - name: Mariah Carey - url: https://mariahpride.com - - name: Marilyn Manson - url: https://store.marilynmanson.com - - name: Mastodon - url: https://shop.mastodonrocks.com - - name: Ministry - url: https://store.ministryband.com - - name: Morrissey - url: https://us.mporium.org - - name: Motley Crue - url: https://store.motley.com - - name: Motorhead - url: https://shop.imotorhead.com - - name: Panic! at the Disco - url: https://store.panicatthedisco.com - - name: Purism - url: https://puri.sm - - name: Rival Sons - url: https://rivalsons.myshopify.com - - name: Rob Zombie - url: https://shop.robzombie.com - - name: Roger Waters - url: https://store.roger-waters.com - - name: Scorpions - url: https://store.the-scorpions.com - - name: SIA - url: https://shop.siamusic.net - - name: Sixx:A.M. - url: https://store.sixxammusic.com - - name: Slayer - url: https://store.slayer.net - - name: The B-52s - url: https://theb52s.manheadmerch.com - - name: Thomas Rhett - url: https://thomasrhettstore.com - - name: Toby Keith - url: https://toby-keith-store.myshopify.com - - name: Train - url: https://store.savemesanfrancisco.com - - name: Weezer - url: https://weezerwebstore.com \ No newline at end of file -- GitLab From 86c6bd3ca088a988755a0fa033d21a3e2b618ed7 Mon Sep 17 00:00:00 2001 From: Eric Szeto Date: Tue, 12 Dec 2017 11:45:24 -0800 Subject: [PATCH 06/43] Add Project Coral Reef Store to goods category --- _data/merchants.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/_data/merchants.yml b/_data/merchants.yml index 00543bcd..0c11c8ee 100644 --- a/_data/merchants.yml +++ b/_data/merchants.yml @@ -219,6 +219,8 @@ url: http://investmentart.org/ - name: Mushroom cultures, mushroom growing supplies, seeds url: https://www.vesp.co/Fungible + - name: Project Coral Reef Store + url: http://www.projectcoralreef.com/all-stores - name: SecPoint IT Security Products url: https://shop.secpoint.com/shop/frontpage.html - name: SilverRound.com - Gold and Silver Dealer -- GitLab From a058b962fed35ddd39152c325f8d814815c7bb79 Mon Sep 17 00:00:00 2001 From: rehrar Date: Mon, 13 Nov 2017 18:20:10 -0700 Subject: [PATCH 07/43] Added blog post on Workgroups and Resources --- _posts/2017-11-13-workgroups-and-resources.md | 44 +++++++++++++++++++ 1 file changed, 44 insertions(+) create mode 100644 _posts/2017-11-13-workgroups-and-resources.md diff --git a/_posts/2017-11-13-workgroups-and-resources.md b/_posts/2017-11-13-workgroups-and-resources.md new file mode 100644 index 00000000..a1708cea --- /dev/null +++ b/_posts/2017-11-13-workgroups-and-resources.md @@ -0,0 +1,44 @@ +--- +layout: post +title: Workgroups and Resources +summary: A brief overview of workgroups in Monero and the resources that are provided for them to succeed. +author: rehrar +--- + +### Introduction + +The Monero Project differs from many, if not most, projects in the cryptospace by being, at its core, a grassroots community project. Some cryptocurrency enthusiasts may be surprised to know that open source does not inherently mean community-driven. One has only to look at several major coins to see many have official foundations (many times corporations) behind them that guide the development process, with the weight given to community input varying from project to project. These foundations generally comprise of departments, such as developers, marketers, stakeholders, PR representatives, and more, with the amount of external contribution (i.e that doesn't come from one of the foundation's internal departments), once again, varying depending on the project in question. + +As with most things in life, there are pros and cons to the aforementioned approach, with one of the greater strengths being everyone (generally) knows who's in charge of what, leading to ease of communication, and clarity for newcomers on where to direct questions or contributions of their own. A disadvantage to this method is it is a form of centralization, with the question of whether or not the project would survive should the foundation shut down for any reason. + +The Monero Project has chosen a different approach to contribution, namely making all of it 'external'. While there is a [Core Team](https://getmonero.org/team) in place, they are, at best, an informally affiliated group who have proven to have Monero's best interests in mind, and view their role as 'stewards' rather than CEOs or managers. This approach is powerful, in that it leads to minimal centralization, while still enabling the community to have a trusted group that can set a philosophy and direction for Monero, as well as, on a practical level, facilitate project critical transactions (Forum Funding System or FFS), mediate disputes, merge code, and be trusted with funds to be used on Project matters [(the general donation fund)](https://doante.getmonero.org). + +One of the drawbacks of such an approach however, is that if the Core Team is not directly responsible for development, marketing, and support, then who is? The answer is: you! + +The Monero community is in complete control of all forms of contribution. Nobody is anybody's boss, and, with the exception of individuals funded by the FFS, nobody reports to anyone. This can, at times, be frustrating to the community as an individual might want to see some work done, but nobody is doing it, and it seems there is nobody to talk to about getting it done. The beauty of this system however, is that nobody needs to be talked to to get it done. The same individual that would like to see an area of Monero improved can take the initiative to see their idea to completion by doing it themselves, either alone or with a group. + + +### Workgroups +A Monero workgroup is defined as any small group of contributors that work together to see an idea (beneficial to Monero in some fashion) become reality. Workgroups can vary wildly in members, governance structure, ideals and goals, and marketing. The [Monero Economy Workgroup (MEW)](https://bitcointalk.org/index.php?topic=776479.0) was one such workgroup that existed in the past, with a very formalized structure, including dues, elections, and more (this workgroup ultimately disbanded). Read the BitcoinTalk thread for more information about what their stated goals were, and how they wanted to accomplish them. Some workgroups may choose to take a more informal approach, with fluidity in membership and utilizing donations instead of dues. + +While the name 'Monero Workgroups' may be fairly new, the idea has been in practice for some time. A non-comprehensive list of existing workgroups as of this writing are: [Kovri](https://getkovri.org), [Monerujo](https://monerujo.io), [Translation](irc://chat.freenode.net/#monero-translations), the [Monero Meetup Kit](https://taiga.getmonero.org/project/sgp-monero-meetup-kit/) and [Community](https://reddit.com/r/monerocommunity). Each of the aforementioned workgroups has its own structure, preferred meeting places, subculture, and more. + +In order to facilitate the organic creation and growth of workgroups, the Core Team saw fit to invest in resources that will be freely available to any aspiring contributor or workgroup, so as to make the transition from idea to finished contribution as smooth as possible. + +### Resources + +#### [Taiga](https://taiga.getmonero.org) + +[Taiga](https://taiga.io) is an open-source, self-hosted project management platform with an emphasis on agile development. It can be used to organize teams, solve issues, set User Stories, track progress, and host files. It utilizes such [Agile](https://www.youtube.com/watch?v=Z9QbYZh1YXY) tools as [Kanban boards](https://www.youtube.com/watch?v=R8dYLbJiTUE), [Scrum](https://www.youtube.com/watch?v=XU0llRltyFM&t=4s), and Epics. + +Taiga is meant to be the non-developers alternative to Github (although it can be useful for software development too), by providing a common environment with an easy-to-use interface where workgroups can track productivity. + +#### [Mattermost](https://mattermost.getmonero.org) +[Mattermost](https://about.mattermost.com/) is an open-source, self-hosted Slack alternative. While Monero has a Slack (with relays into IRC), many in the community voiced that it was not in the spirit of Monero to so heavily utilize a proprietary software wherein you don't control the data. For this reason, a Mattermost instance was launched, with the same relays into IRC channels (more actually), as well as integration with Monero's Taiga instance (updates to User Stories are sent via a bot to a specified channel). + +### The first success story: Monerujo! +The Taiga and Mattermost instances have been deployed for a couple months now (big round of applause to `pigeons` for deploying everything), but have been kept in a sort of 'beta period' where things could be fine-tuned, integrated, and fixed should the need arise (another big round of applause to `pigeons` for his integrations and fixes). But this didn't stop one brave workgroup from being the beta testers. + +The Monerujo team has their own [Taiga project](https://taiga.getmonero.org/project/m2049r-monerujo/) as well as several private Mattermost channels where they conduct weekly meetings, share files, and, many times, just have fun! + +You (yes, you!) are invited to do the same. Brainstorm, envision what you want Monero to be, make a project, turn your ideas into reality, and have fun! Monero depends on you. \ No newline at end of file -- GitLab From 5ff512966cab49c6910158309d53604dc5cbaeea Mon Sep 17 00:00:00 2001 From: dEBRUYNE-1 Date: Tue, 21 Nov 2017 20:35:08 +0100 Subject: [PATCH 08/43] Overview and Logs for the Dev Meeting Held on 2017-11-19 --- ...-for-the-dev-meeting-held-on-2017-11-19.md | 265 ++++++++++++++++++ 1 file changed, 265 insertions(+) create mode 100644 _posts/2017-11-19-overview-and-logs-for-the-dev-meeting-held-on-2017-11-19.md diff --git a/_posts/2017-11-19-overview-and-logs-for-the-dev-meeting-held-on-2017-11-19.md b/_posts/2017-11-19-overview-and-logs-for-the-dev-meeting-held-on-2017-11-19.md new file mode 100644 index 00000000..3f79d793 --- /dev/null +++ b/_posts/2017-11-19-overview-and-logs-for-the-dev-meeting-held-on-2017-11-19.md @@ -0,0 +1,265 @@ +--- +layout: post +title: Overview and Logs for the Dev Meeting Held on 2017-11-19 +summary: Discussion of open PRs and issues, Bulletproofs, Monero Research Lab, Monero integrations, dedicated Monero hardware wallet, multisig, and miscellaneous +tags: [dev diaries, core, crypto] +author: dEBRUYNE / fluffypony +--- + +# Overview + +An overview can be found on [MoneroBase](https://monerobase.com/wiki/DevMeeting_2017-11-19). + +# Logs + +**\** Hey everyone! I don't know if fluffypony will be here today, but let's see about getting this thing started. +**\** Hello to everyone idling in the peanut gallery +**\** Hello. +**\** 2. Brief review of what's been completed since the previous meeting +**\** Can we get a mini-update from dev, gui, hardware, and mrl? +**\** I can speak for MRL +**\** We've been thoroughly investigated bulletproofs, a new form of CT range proofs +**\** is moneromooo here? +**\** Yes +**\** have one thing to bring up +**\** when there's time +**\** They should function as essentially a drop-in replacement that is 10% the size of the original proofs (for one output; even smaller for multiple outputs) +**\** with about the same verification time; possibly a teensy bit faster +**\** Kudos to andytoshi for a lot of great help on those, and others +**\** it's like a TARDIS! the bigger the input the smaller the output! /s +**\** So it's looking really promising that it'd be good for us? +**\** yes +**\** We'll start translating the Java test code over to C/C++ for more detailed work +**\** it's a win-win: smaller-spaced range-proofs, with the same verification time +**\** There were some doubts about ver time, but we literally just had a convo over in MRL that pointed out a simple caching that helps us +**\** MRL, folks. Let's give 'em a hand. +**\** It was pointed out, though, that there's very little randomness hanging around, which could affect storing stuff "in the randomness" +**\** That may be a deepe discussion for later +**\** yeah, using these range proofs makes encrypting messages with range proofs far less do-able +**\** \*deeper +**\** eh who cares +**\** MRL is excellent, nice. +**\** andytoshi is really the one who nailed it, btw +**\** aye +**\** aaaaand all his co-authors +**\** Can we send them a fruit basket? +**\** +1 +**\** which has included, for a second time, Jonathan Bootle +**\** rehrar set up an FFS for it +**\** 0.2 XMR +**\** and for the N^th time, greg maxwell +**\** 100 XMR requested +**\** biggest fruit basket ever +**\** Anyhoo, that's the big news from MRL right now, I suppose +**\** awesome. Thanks so much. +**\** multisig is looking like i will be ready to hand it off to sarang by the end of the month, as hoped. +**\** and thats it for now +**\** Anyone else have an update since the last meeting two weeks ago? +**\** This is huge from a scaling perspective +**\** absolutely +**\** dev has done a tone of PR merges latelt +**\** lately +**\** can you summarize them? +**\** there's still been build issues with readline dependencies but I think they're pretty much sorted by now +**\** we've isolated readline from GUI dependencies, etc. +**\** mooo can probably summarize better +**\** vtnerd says "oh good" +**\** "woo" +**\** Hmm. I can go look at github: +**\** (mostly small things anyway) +**\** FP confirmed he can't make it today. He sends his apologies. +**\** disguising password length in prompt I guess is still a small thing, but user visible +**\** less unnecessary locking in some DB readers, which should speed up some RPC +**\** Fixes for BSD build +**\** The wallet does not fetch unneeded hashes anymore (ie, starts direct from 1.4e6) +**\** CORS (for those who know what it is) +**\** A fix for show\_transfers missing more than one incoming input in a tx +**\** And I think the rest is either prior to last meeting, or small/internal stuff. +**\** yeah but it comprises a couple dozen PRs between then and now +**\** Alright, awesome. Thanks moneromooo. +**\** hardware, I know you give updates in community, but I think most of us that know are excited about the rapid progress you're making +**\** care to share something small about what's been going down? +**\** Hardware; we've settled our initial workflows and have built a twenty strong team. Journals are taking notice (see press) and the project is moving along. +**\** https://taiga.getmonero.org/project/michael-rfc-hwallet-1-implementation/wiki/press/ +**\** I'll mark our forum proposal milestone 1 as concluded today probably. +**\** We now have an open call to any interested in a hardware wallet, become part of the project and possibly test a prototype. See: +**\** https://taiga.getmonero.org/project/michael-rfc-hwallet-1-implementation/wiki/preview/ +**\** I'll demonstrate our two current working protoypes at this week's first ever Monero Munich meeting. +**\** That's all, any questions? +**\** What do you expect those who receive the prototypes to test? +**\** Very weak expectations, hopefully each finds their own way to contribute and strengthen the project. +**\** There's a test plan page, where people can make comments while testing. +**\** But that is just one of many choices, each individual can make on their own. +**\** Pretty lame answer no? +**\** Alright, thanks msvb-lab! +**\** Thanks for the opportunity. +**\** Sounds like pretty nice stuff is going on there, congrats :) +**\** (I counted 72 PRs merged since last dev meeting) +**\** hyc: Who make most of the merges, fluffy? +**\** So, we've got Code + ticket discussion / Q & A time available for the devs to discuss dev-y things. But all the mergy stuff may have to wait because of FP absence, but if there's other business to take care of, devs you have the floor +**\** yes he does all the merges +**\** we didn't get a report from GUI +**\** oh, right! so sorry. +**\** Anybody working on GUI have stuff to talk about. +**\** ping Jaquee ? +**\** so i've been chatting with mooo, Jaquee, and vtnerd recently about integrating MyMonero with the native mainline libwallet +**\** sorry. i'm on the run +**\** signs point to integrating with wallet\_api +**\** I may end up tackling a small portion of factoring wallet2 +**\** ok, no worries Jaquee. +**\** As long as not too many gratuitous changes ^\_^ +**\** 100% mooo +**\** all variable and class names being filtered thru pig-latin +**\** dsc, in here :) +**\** :) +**\** Is our GUI crew considered only monero-gui, or are mymonero.com and Moneruj (Android) included as well? +**\** has it started? +**\** lol hyc +**\** I think GUI crew is people who work on the monero-gui repo +**\** mymonero and Monerujo are their own thing +**\** dsc has what started? +**\** the meeting :D +**\** oh, yeah. We're about half hour in. :) +**\** oh - that's worth mentioning too - the repo is now properly named monero-gui, no longer monero-core +**\** rehrar: So Monerujo communicate on a different channel, right? +**\** That rename is a milestone :) +**\** Monerujo utilizes the Mattermost where they have a private channel for the devs and core team, and a public channel for questions. They've also got a Taiga to track progress. +**\** aight, so I'm working on a black theme for `monero-gui` (qt5) .. learning QML in the process. Trying to get some more UX developers involved and generally just trying to document things as I go +**\** I can rep Monerujo though, as I'm heavily involved with them +**\** they've got some exciting stuff coming +**\** yes, can you link your thread dsc? +**\** sure +**\** The one you made a few days ago. +**\** https://www.reddit.com/r/Monero/comments/7dvwq0/contributing_to_monero_as_an_ux_developer_short/ +**\** in the comments there are the various proposals for redesigning the GUI. Are there any thoughts on any of those? +**\** well, first dsc you wanted to say something, go ahead. :) +**\** No I was finished :P +**\** but to answer your question: There are 3 UI proposals of which I picked the one that was most trivial to implement +**\** seeing as I'm just one guy with zero QML experience, hehe. +**\** rehrar: Basically we're first kind of going for the dark theme, which will have a light mode as well +**\** Because it's most trivial to implement +**\** (only requires minor changes to the current design) +**\** https://github.com/monero-project/monero-core/issues/419 +**\** https://github.com/monero-project/monero-core/issues/869 +**\** https://github.com/monero-project/monero-core/issues/949 +**\** Some screenshots -> https://i.imgur.com/89YFUj7.png +**\** for those interested +**\** Ok. Cool deal! +**\** To clarify, the dark theme is #949 +**\** cool +**\** dsc also made a PR which should make the GUI more responsive +**\** cant make any predictions as to when I have some tangible, taking quite some time...! +**\** s/some/something/ +**\** Also, we're aiming to include subaddresses and multisig somewhere in the future^tm +**\** And, once there is a core appstore account, we'll start testing the ios port of the GUI +**\** There'll be an android port as well, fwiw +**\** dEBRUYNE: Is Qt5 easy to port to mobile? +**\** Is there a new android APK to test? I last saw one months ago +**\** sgp: Buildbot produces APKs iirc +**\** Let me check +**\** No that isn't setup now +**\** msvb-lab: Jaquee did it, so better to ask him :P +**\** I can't promise next week even, very busy +**\** rehrar: To give you an idea, right now I have this: https://i.imgur.com/iLwupdB.png +**\** or to give anyone an idea for that matter :) +**\** Hello +**\** looks pretty chill imo :D +**\** aye aye +**\** WIP ofc :) +**\** I personally think there needs to be a bit of a restructuring of some info, but this is a good meantime +**\** agreed +**\** good stuff +**\** would be nice to get a more recent android build up for people to test +**\** Alright. That's it from GUI? No other opinions on dEBRUYNE and dsc stuff either? +**\** looks like we can move on to ticket Q/A +**\** ok Code + ticket discussion / Q & A +**\** hyc moneromooo can you two take the lead for this? +**\** Well, if anyone has questions about them, please ask. +**\** I'd leave it to mooo. I'm not aware of any open questions +**\** ^^ +**\** ticket Q/A \!= discussing open PR's, right? +**\** sure +**\** ask away +**\** low hanging fruit PRs (that can probably be merged): #919, #954, #963 on monero-gui +**\** not so much a question ^\_^ +**\** probably ask luigi to merge them if fluffy is unavailable +**\** luigi merges GUI PRs anyway :) +**\** alright +**\** I think luigi is out for a few days, so be patient. (: +**\** Alrighty, shall we move on? +**\** FFS Formalization: https://github.com/monero-project/meta/pull/87 +**\** Is there meeting? +**\** serhack started 40 minutes ago +**\** we probably don't have time for a large discussion (if at all), but I just wanted to encourage the devs to take a look at the PR +**\** Oh +**\** I forgot it +**\** The idea of having a set of formalized guidelines for FFS proposals going forward has been thrown around a lot. It'd be good to get some opinions on how this is laid out and any concerns that may arise from it. +**\** I didn't understand well: is the project funded by ffs an Official project? +**\** Does the current system work? +**\** There's been hiccups ArticMine. fireice and guzzi come to mind. +**\** those seem like complete outliers :P +**\** not exactly legit claims to issues imo +**\** Largely based on de facto expectations that are not actually formalized. +**\** How do we learn about the hickups mentioned (in order to understand context?) +**\** but proposals could stand to be more concrete, specific, detailed, +**\** rehrar: formalization can be a bit of a rabbit hole as well +**\** sometimes humans need to be involved +**\** ppl need to recognize the situation before a formal plan can be applied +**\** indeed. current US political situation reflects this - institutions are designed assuming good faith in all participants +**\** but if the situation is not able to be recognized by ppl then how can it be applied for the desired result? +**\** nobody can take all the time needed to identify every possible abusable loophole +**\** What we have currently is a Core Team centered way of resolving disputes that, to my knowledge, hasn't really been utilized since I've been here +**\** since we've got that right now, maybe we stick with it? +**\** but identifying loopholes and plugging them is not a bad thing +**\** it's just that they need to be done by humans imo +**\** We may need some tweaking to deal with the hiccups; but as afar as I can see at a fundamental level the system is working +**\** don't know where else the graphic is, so I'll just link it here: https://getkovri.org/contributing.html +**\** bottom of the page +**\** This has not been formally replaced, so it is currently active. We can discuss that at a later time though. Let's move on. +**\** 5. Any additional meeting items +**\** If anyone has anything, speak up. :) +**\** If anyone wants to test multisig, feel free. PR 2134. +**\** is there a set date for the next code freeze? +**\** A little update by me about Monero Integrations +**\** go for it serhack +**\** So we (I and cryptochangements) are going to release Magento Plugin, In the past few weeks, we worked on a new cool payment box for Monero Integrations. +**\** +**\** I am currently working on OpenCart too so I think we can release Magento payment box the next week.. +**\** +**\** I have talked to OpenBazaar too and they have told me that Monero + Openbazaar would be nice.. it will be a difficult task but I think I can do it +**\** you can go on, rehrar +**\** Everytime I read OpenBazaar, it makes me want to punch that scammer from a few years back... +**\** alright, thanks man :) +**\** atrides? +**\** That's the one. +**\** doesn't he still run Dwarfpool? +**\** yeah, and ppl still mine on it +**\** We should encourage them not to +**\** Either way: 6. Confirm next meeting date/time +**\** December 3rd? Same time? +**\** so no freeze date, eh? +**\** Should we move time because daylight savings? +**\** About mid december +**\** word. +**\** Please do not move the time +**\** Or january. Unclear. +**\** ok, time not moved +**\** FP would have a better answer? +**\** isn't a release due in January? +**\** and we're supposed to freeze a month before +**\** March +**\** well dec or jan gives us 3 months +**\** ok +**\** There's a new freeze/release schedule isn't there? +**\** mebbe someone can open a meta issue and set some dates into it +**\** i thought we had 3 months of freeze for more testing / fixing than before .... +**\** 3 months of freeze is gonna make me punch someone else :P +**\** It's branch, then release from the brnch aftrer 2-3 months. +**\** It's already painful when stuff doens't get merged after a month. +**\** The big one is the bullet proofs +**\** right. i thought branch is a freeze... i.e., feature freeze.... i.e., freeze on adding wacky new stuff that requires bandaloots and warples +**\** That's not likely to be ready by then. +**\** but yeah... perhaps that should be documented somewhere +**\** (Not to interrupt, but meeting is over for those who need to go, discussion can of course continue) +**\** Alright. You guys are the best! thanks for being a part of this community, and developing the software we all know and love as Morono +**\** rehrar: Thanks, good flow of topics, great moderation. \ No newline at end of file -- GitLab From 27342dfa0a52e400be8523a082c9ace6fa6a7a57 Mon Sep 17 00:00:00 2001 From: dEBRUYNE-1 Date: Mon, 27 Nov 2017 19:28:24 +0100 Subject: [PATCH 09/43] Logs for the Community Meeting Held on 2017-11-25 & the Monero Research Lab Meeting Held on 2017-11-27 --- ...he-Community-meeting-held-on-2017-11-25.md | 311 ++++++++++++++++++ ...Research-Lab-meeting-held-on-2017-11-27.md | 180 ++++++++++ 2 files changed, 491 insertions(+) create mode 100644 _posts/2017-11-25-logs-for-the-Community-meeting-held-on-2017-11-25.md create mode 100644 _posts/2017-11-27-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-11-27.md diff --git a/_posts/2017-11-25-logs-for-the-Community-meeting-held-on-2017-11-25.md b/_posts/2017-11-25-logs-for-the-Community-meeting-held-on-2017-11-25.md new file mode 100644 index 00000000..9591d4a5 --- /dev/null +++ b/_posts/2017-11-25-logs-for-the-Community-meeting-held-on-2017-11-25.md @@ -0,0 +1,311 @@ +--- +layout: post +title: Logs for the Community Meeting Held on 2017-11-25 +summary: Community highlights, Forum Funding System updates, RFC-HWALLET-1, Monero integrations, Malware Response Workgroup, Monero Coffee Chat, and miscellaneous +tags: [community, crypto] +author: dEBRUYNE / fluffypony +--- + +# Logs + +**\** We would like to welcome everyone to this Monero Community Meeting! +**\** Link to agenda on GitHub: https://github.com/monero-project/meta/issues/137 +**\** 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. +**\** 1. Greetings +**\** What up kids? +**\** hey all! +**\** Hi! +**\** Don't be shy :) +**\** Hello. +**\** 2. Community highlights +**\** For a great weekly summary, please read the Monero Observer: http://monero-observer.com/ +**\** 3. FFS updates +**\** To those who haven't heard of the FFS before, it stands for the "Forum Funding System" +**\** a. RFC-HWALLET-1 project progress +**\** msvb-lab: do you have any updates you want to talk about? +**\** hii :) +**\** Sorry, delay... +**\** We had a great Munich Monero meeting, where we mostly talked about forming a local group, regular meetings, the (nearby) Vienna event(s) of December, and the hardware team's efforts (with a few boards passed around.) +**\** As far as hardware goes, there's nothing organised to say. Lots of ordering of parts and waiting for them to arrive, some porting of designs to the EDA CAD application we're using. +**\** Laser cutter considerations, and so on. +**\** Any questions about hardware wallets? +**\** We have three designs being worked on in parallel, I could talk an hour but will spare the bore. +**\** the local group with regular meetings sounds great +**\** It's important for whoever would like to test a real device in their hands to sign up as a team member by clicking 'Contact the project' on the site: +**\** https://taiga.getmonero.org/project/michael-rfc-hwallet-1-implementation/ +**\** ErCiccione: We had about twenty people there, and passed around artwork from Deborah. +**\** So we've definitely reached critical mass in Munich, Berlin was there long ago. +**\** great, this is Monero community +**\** msvb-lab: learning about these three designs would be a good read. If you want to work with me on writing something about these, I think the community would appreciate it +**\** yes we would :) +**\** sgp: ;) +**\** A good place to put the informatino about the various device types is: +**\** https://taiga.getmonero.org/project/michael-rfc-hwallet-1-implementation/wiki/protos +**\** So one is called 'MCUDev' (now renamed to 'Monezor'), another is 'Breakneck', we need a name for the device that resembles Ledger Blue's design. +**\** ...and so on. +**\** nice +**\** Ok, good to know +**\** Anything else on the hardware wallet front? +**\** Not from me. +**\** b. Monero Integrations +**\** cryptochangement, want to take it from here? +**\** serhack, you wanna go first? +**\** yes, thanks +**\** ok cool +**\** okay guys, the latest update before today was 1 month ago so more surprise are coming +**\** first of all we have redesigned the payment box +**\** serhack: im actually pretty sure i talked about that last meeting ;) +**\** second, a helpful security engineer have helped them in order to fix a potentially sql injection on payment id +**\** (I mean on reddit, it seems only few people read community meeting cryptochangements) +**\** thats fair :p +**\** https://imgur.com/a/MUV72 +**\** this is the new payment box +**\** third, I have already contacted OpenBazaar team for implementing Monero +**\** We should wait for multisig +**\** that's all from me, go cryptochangements :) +**\** Okay so good news here +**\** Our second milestone, the Magento plugin is finished and ready to be used by merchants! +**\** Its all on GitHub here: https://github.com/monero-integrations/moneromagento +**\** hooray! +**\** and here is a screenshot of the checkout: https://taiga.getmonero.org/media/attachments/6/0/a/5/72f4eb66138e7efd76c4abd6e7d52df16806cdc441788e61c3c8e20ec676/improvedmagento.png +**\** yeah, cool announcement cryptochangements!! +**\** i should also mention that you can track a lot of our progress on taiga: https://taiga.getmonero.org/project/serhack-monero-integrations/ +**\** Yay Taiga!! +**\** rehrar ive actually became rather fond of it :p +**\** thats pretty much all, unless there are any questions +**\** Which of these technologies resembles Bitpay most? +**\** There are ten repositories besides magento. +**\** I think we should mark a thing +**\** So if I'm a vendor who wants to be able to 'Bitpay' with XMR, which github should I look at? +**\** no offense to you msvb lab +**\** msvb-lab: they all have the same design/setup they are just for different cms +**\** The goal of Monero integrations is removing the middleman +**\** Oh, that makes sense. +**\** globee is actually close to bitpay... because they actually use bitpay +**\** I thought there was a more complex architecture. So for three different vendors with three different CMSs, they will be served by referring to the correct implementation. +**\** That's quite good. +**\** yeah, msvb-lab, different e-shops but they are using the same methods in order to accept monero +**\** Exactly msvb-lab +**\** They all provide the same functionality for different systems +**\** Is it still forbidden to talk about Globee (are there still secrets?) +**\** the main difference between us and globee is that we dont deal with fiat. all funds go directly to your wallet with no 3rd party +**\** Seems it would be relevant to this chapter of our meeting? +**\** I don't know anything about the Globee secret project +**\** idk fluffy isnt here so you probably dont want to go spilling all of his secrets :p +**\** Globee can be talked about freely. The secret project being done by Globee is best kept under wraps for now. +**\** Okay, fine if the Globee deal or technology is still (partly) secret. +**\** rehrar: They probably need some time still to get the design done. +**\** Any other updates cryptochangement/serhack? Can you remind me what integration is next? +**\** well, it's just not out yet, so please don't spread confidential info +**\** the next is opencart +**\** next is opencart, which is in the works +**\** and now i think we can pass the baton +**\** Cool +**\** yes +**\** Thanks cryptochangement and serhack +**\** your welcome +**\** Does anyone else have a FFS update? +**\** i wanted to say a couple of yhings +**\** Go ahead ErCiccione +**\** also have a quick update +**\** after you ErCiccione +**\** i'll be quick endogenic +**\** no need, we have 30 mins :P +**\** I just wanted to say my FFS is in the process of being moved from Ideas to funding required, thanks to all the community for the support! +**\** It's a very worthy proposal imo +**\** From the other community feedback, it seems that other people think so too +**\** What is the URL? +**\** serhack is going to donate +**\** I can't find it. +**\** 1 sec +**\** https://forum.getmonero.org/6/ideas/89232/coordinator-for-localization-group-various-maintenance +**\** it's still under ideas,but the pony said he is going to move it tonight/tomorrow +**\** I have something to say about FFS in general that the people here really need to be involved with. I'll speak after ErCiccione and endogenic +**\** thanks serhack :) and thanks sgp +**\** +1 rehrar +**\** @ErCiccione is that all? +**\** Go ahead endogenic +**\** no 1 sec +**\** also I reorganized the Taiga of the localization project, now is easier to add a translation (there also a quick guide "how to translate the GUI") +**\** https://taiga.getmonero.org/project/erciccione-monero-localization/ +**\** Will integrate it soon with github +**\** that's all from me +**\** Great thanks +**\** endogenic, your turn +**\** so i've been speaking with sgp and some members of the monero research lab about educational hackathons, and we think a corporate sponsored kovri hackathon could be brilliant (basically, you must build something using kovri plus one or more of the libraries from the sponsors) +**\** so I'd like to encourage everyone in the Monero community who is interested in getting involved with kovri or hackathons to get in touch with sgp and/or the noethers and chat with them about how you'd like to be involved +**\** doesn' have to be corp sponsored but it's probably a good idea +**\** they buy the food too :P +**\** and they supply venue, often +**\** unless it's done at a library or a school like NYU +**\** who has hosted such things before +**\** that is all +**\** Ok endogenic. We can discuss this more during the open ideas time +**\** oops +**\** Rehrar? +**\** No worries :) +**\** Yay. My turn. +**\** go rehrar, make this community cool +**\** Ok, as the Community workgroup, our job is several things (as you all may know). We want to make the community a good, educational, friendly place to be. And many of us head our own smaller workgroups and stuff. +**\** I think we need to add something onto the goals, specifically regarding the FFS +**\** The community workgroup needs to brainstorm ways that we can increase FFS giving involvement, and rely less on individuals that donate large sums. +**\** There was a large push on Surae's FFS, and it was awesome to see. It's slowed down a bit, which is totally fine, and I'm sure one final Reddit post would finish it up. +**\** We need to aim for getting community involvement with the FFS. Something like 0.1 XMR per person. +**\** We can find ways to incentivize if we'd like, but that's not the only way. +**\** We can discuss this in open ideas time, but building a culture of generosity and giving within the community should be a large priority, since the project relies on donations. +**\** end +**\** Thanks rehrar +**\** what is the cause that sarang's proposal was quickly funded while surae's was not? +**\** a large donation +**\** 0.1 XMR per person would be a dream +**\** I can make discussion groups for the hackathon and FFS projects in Mattermost +**\** rehrar: not quite my question +**\** why sarang and not surae? +**\** ah, ok then +**\** was there a difference in the quality of the proposals? +**\** @endogenic it may have been as simple as sarang's being listed first in a Reddit post or something +**\** sgp thats what i was thinking +**\** I have a little idea rehrar +**\** we can discuss it serhack. :) +**\** Meeting continue? +**\** rehrar: is your point up for further debate? +**\** Yeah, I would like to make sure we finish the next point +**\** ok +**\** I'm thinking Open Ideas time of this meeting we can discuss further +**\** but of course we can debate it +**\** I would like to discuss rehrar's ideas later in the meeting +**\** 4. Discuss formation of Malware Response Group +**\** Fluffypony and tuckerpreston asked me to reserve some time to discuss the response to malware and botnets. +**\** Is anyone here to speak about this now? +**\** yeah +**\** @mattcode great! Go ahead +**\** lots of angry administrators come into #monero-pools complaining that their servers have been compromised by a miner +**\** and they get even more upset when they're told that a monero address can't easily be traced back to an individual +**\** oh, I didn't know anything about that, mattcode +**\** i don't really think that there's a solution to that +**\** and the other issue is websites getting hacked and web miners being silently inserted, which again there's nothing we can do about that +**\** yes, it's like "someone stealed my monero. my email address pass is 1234" +**\** if monero didn't exist, the hacked servers and websites would just be used for spam/ddos/stealing passwords instead +**\** +1 mattcode +**\** mattcode: And your or Fluffy's idea about a task force should serve as a support center, right? +**\** maybe there could be a page on the website explaining the harsh truth to administrators that have been hacked +**\** also isnt it a SysAdmins job to keep his security top of the state? :D +**\** I think there's definitely room for a more formal response to web/server admins +**\** but a task force isn't too useful because they're just going to end up saying "sorry, there's nothing we can do to help. re-image your server and fix your vulnerabilities" +**\** Ultimately it's up to them to fix/secure their stuff as we should say, but there could still be a page about it +**\** Like "here's what you can do with the mining pool and address. Try contacting them. Otherwise, check your logs" +**\** I wonder if there's any way we can turn this into a net positive +**\** mattcode: So you believe having a group of support crew is not effective, but maybe a specially labeled web page right? +**\** yep +**\** yeah I think that would be better. right now they end up in #monero-pools and just end up getting ignored or abused +**\** i think thats a solution +**\** why should we spend efforts on websites when the default password is admin ? +**\** It's good to at least have something serhack. Some of these attacks are more complex, or from an internal employee +**\** Honestly i don't like the idea of the page on the website, i prefer the idea of the team +**\** rehrar: the positive is that monero has a high network hashrate that doesn't dip when the price dips. i don't have any numbers but when ETN became (briefly) more profitable to mine than XMR, the XMR net hash barely dropped +**\** yep, we should setup a tutorial/website +**\** I mean turning the third-party server getting hacked into a positive for the administrator. I mean obviously it's not a positive thing... +**\** but through education and stuff +**\** We can have ready-made resources (written, video, or otherwise) to hand off to people who experience this +**\** because this may apply to individual users too, not just servers +**\** that way, we are not taking responsibility for these people's security, but we are giving tools and resources that people can take hold of their own security +**\** I can write something up as an example and see if it's a good draft. I'll link it in this channel +**\** okay, good sgp +**\** Mattcode, do you want to help me with this? +**\** most desktop antiviruses pick up the miners and delete them, so i don't think it's too much of an issue for desktop individuals +**\** yeah, much better this way +**\** rehrar that's what I'm thinking +**\** The task force team can be working on this instead of on-demand support +**\** This is very in the spirit of The Monero Project, which is all about providing tools and resources for people to take back what's theirs +**\** I just think on-demand support is overkill. It would literally tell people the info on the page we would make +**\** I don't think we should be writing things like cleanup guides, because all of the different pieces of malware and server configurations make that impossible. +**\** Oh, you want to provide that level of support? +**\** also organisations usually have their own procedures for when things get compromised +**\** the support they are looking for is please pool, don't payout to this address etc +**\** lel +**\** yes +**\** they can redirect payment to me instead +**\** I think the best thing would just be explaining that it's not the Monero project, the pool operator or the miner developer that has hacked your server. +**\** mattcode, are you happy with me making a Mattermost workgroup chat so that we can discuss this further after the meeting? +**\** yes help them waste less time +**\** sgp: sure +**\** Great +**\** +1 sgp +**\** Anything else you want to discuss during the meeting? +**\** We are going over today, sorry +**\** 5. Monero Coffee Chat +**\** The next Monero Coffee Chat will be next Saturday on 2 December https://github.com/monero-project/meta/issues/139 +**\** During the Coffee Chat, we will go through Taiga so that people become more aware and more familiar with it. +**\** It would be nice if the website is refreshed before then so that the Mattermost/Taiga announcement gets published. +**\** Beyond this, the format of the Monero Coffee Chat will be about the same. If anyone would like to participate, please send me a PM. Otherwise, you can always join us on YouTube. +**\** Twas lonely last time with just me and sgp and fp (for a bit) +**\** Skipping open ideas time for now, but of course #monero-community can always function as open ideas time even outside meeting time +**\** Yes, it was a bit lonely :) +**\** okay, sgp +**\** We need more volunteers +**\** 7. Confirm next meeting date/time +**\** The next meeting will two weeks from today on 9 December at 17:00 UTC. +**\** 8. Conclusion +**\** That’s all! Thanks for attending this Monero Community meeting, and we hope to see you on /r/MoneroCommunity and #monero-community. Take care, and know that change starts with YOU. +**\** Now, we can continue conversations from endogenic, mattcode, and rehrar +**\** endogenic watchoo wanna debate? +**\** well so just about the kovri thing real quick +**\** i remember on the coffee open hours thing there was discussion about kovri needing a good testing ground +**\** less life or death than monero would be good. plus more exposure for kovri would be good +**\** as for the FFS thing… +**\** just to add onto the botnet thing, i don't think pool ops ever ban addresses after somebody has claimed that their server has been hacked. it would be too easy to fabricate. they only seem to ban big botnets, but only because they place a heavy load on the server :p +**\** people naturally won't donate to something they consciously think is bad… +**\** +1 +**\** and they tend to donate to things they feel are good for them +**\** even charity donation for example is thought to return to oneself +**\** mattcode can you create an account on Mattermost please? https://mattermost.getmonero.org +**\** in monero, it's just supposed to be a little more concrete +**\** now that we are in open tiem, i should probably mention that i posted our FFS update to reddit too so people can see it there: https://www.reddit.com/r/Monero/comments/7fgl4o/monero_integrations_update_12/ +**\** #monero-vulne-response +**\** one thing at at time guys +**\** sgp: vulne or vuln? +**\** vulne +**\** on mattermost +**\** XD +**\** vulne. It's only on MM now, not IRC +**\** so if people are not made to undrestand what a proposal is important +**\** how can you expect them to donate to it? +**\** Sorry +**\** ah ok. i just thought vulne sounded funny ^\_^ +**\** you guys seem to be talking about something else anyway… :P rehrar feel free to ping me +**\** sorry endogenic +**\** You can discuss this now. I'll wait +**\** @endogenic I also made #monero-hackathons on Mattermost +**\** @rehrar on second thought, I think we should have the discussion about the FFS crowdfunding initiative here. Do we need another channel for this? +**\** sgp i think it would be better to talk about it here, much many possible inputs +**\** It's important for the community to survive with small donations, rather than a few wealthy individuals +**\** Of course, having a few people who can help out is both convenient and very generous +**\** But if for some reason these people lost interest, the community should be able to raise significant money from many small donors +**\** i read somwhere the idea of a mining pool managed by the community, where a percent go to the FFS project. doesn't sound too crazy if there's somebody willing to manage everything +**\** ErCiccione: Don't forget promoting the Monero donation address, which could make the third leg of the tuple (many|wealthy|donation.) +**\** Like Kovri does at the bottom of their website. +**\** That could be instrumental for folks that generally appreciate Monero and would donate but don't hang out enough to stay informed. +**\** a "donate now" popup box before downloading? +**\** Most mining pools who donate do so to the Monero project itself +**\** Which in turn often donates to FFS projects +**\** sgp sure, but with a pool you can give the choice to reserve part of your hashrate and decide to put it directly tu support ffs (maybe with subaddresses might be possible to choose the single ffs) +**\** Perhaps +**\** msv-lab: true, but that is mostly everywhere (wallet, website, reddit ecc) +**\** We could change how/when Monero asks for donations +**\** what happens if somebody makes a donation directly to the address of the FFS wallet with no payment id? because if it's possible to evenly distribute that amount to all the actives ffs, we could just spread that address if people doesn't care of the proposal itself, but would like to contribute +**\** an ipothetical 'community pool' could point to that address, distributing equally the mined moneros +**\** doesn't money from the general development fund make its way into FFS requests? +**\** mattcode: yes, sgp pointed that early, but with a pool you move that choice directly to whom is willing to donate (i mean to send the money directly to fund community's proposals) +**\** s/proposals/FFS +**\** ErCiccione meant to say: mattcode: yes, sgp pointed that early, but with a pool you move that choice directly to whom is willing to donate (i mean to send the money directly to fund community's FFS) +**\** so nice of you monerobux +**\** :) +**\** Sorry, out of the house atm. But we need to remember two factors. One, some people like to choose which proposals their XMR goes to. This ensures that Monero evolves in the way they desire. +**\** These people will not like the General Fund option, as the General Fund is managed by the Core Team to spend on whatever they see fit that benefits Monero (obviously coming to consensus within themselves) +**\** There are some people who prefer to choose things themselves, and not trust anyone, even the Core Team. And that's fine. +**\** We're not trying to get everyone to donate to EVERY proposal. +**\** We're trying to get people to donate to what they believe in. +**\** So if someone agrees with funding Surae and not myself, they need to have the freedom to not give to me without shame +**\** but the cultural ideal should be, if you believe in a proposal, you should seriously consider donating something small to it +**\** rehrar: yes, totally agree, that can be solved using subadresses instead of payment's id. could be even better, you would be able to choose the project to contribute to directly from the pool +**\** this is for me a good way to give also to people who cannot afford it, a way to donate, but require the use of subadresses, are they stable right now? \ No newline at end of file diff --git a/_posts/2017-11-27-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-11-27.md b/_posts/2017-11-27-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-11-27.md new file mode 100644 index 00000000..f311620e --- /dev/null +++ b/_posts/2017-11-27-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-11-27.md @@ -0,0 +1,180 @@ +--- +layout: post +title: Logs for the Monero Research Lab Meeting Held on 2017-11-27 +summary: SPECTRE, multisig, Bulletproofs (range proofs), ZKStarks, ASIC resistance, and miscellaneous +tags: [community, crypto] +author: dEBRUYNE / fluffypony +--- + +# Logs + +**\** anyway, agenda for the day: 1) Greetings, 2) Sarang's work 3) my work 4) open discussion. The new zksnark paper will presumably take up some of 4. :P +**\** 1) is done i guess. :\ +**\** 2) Sarang want to bring us up to speed? +**\** roger +**\** I have working code for both linear and logarithmic bulletproofs that tests correctly +**\** I'm finishing up a few small optimizations to reduce the curve op count +**\** nice +**\** and then it'll be ready for C++ +**\** moneromooo already has the linear version up and running +**\** fantastic! +**\** That's been my big project +**\** page 8 of the new zksnark paper talks about dot product proof protocols +**\** orly +**\** That's the big shiny toy of bulletproofs +**\** literally caught my eye +**\** or rather +**\** metaphorically? well +**\** anyway, my point is i have done nothing but skim the paper (in the past 10 minutes) and that popped out at me +**\** you have also been helping me on multisig, as well, don't discount that +**\** I shan't +**\** anything else? +**\** gratz on getting it working +**\** Thanks to everyone who offered support in the most recent fund drive +**\** I remain humbled +**\** thank you, sarang! thanks again +**\* sarang** takes a small bow +**\** As for my work, I've been working on the multisig paper, which is intended to 1) present a formal model of our threshold ringct, and 2) show how our current implementation compares to that formal model. there are differences that i'm hunting down one by one +**\** JollyMort[m] has found several already, and we've been having discussions about it the past few days +**\** That has represented the vast majority of my time +**\** In addition to that, I believe I may have a problematic example case of SPECTRE. the original authors sweep my concern aside, but i wanted to bring it up and see if anyone had any thoughts +**\** I'm intrigued +**\** if two transactions using the same input are relayed nearly simultaneously, they will find their way into two separate blocks. they will appear as conflicting transactions until the spectre algorithm arranges one block to precede the other +**\** or stay conflicting forever if spectre can never linearly order them +**\** this can happen with a simple example of a "mostly linear" blockchain, except with a single block in the chain replaced with a pair of blocks like a diamond shape: +**\** \_\_\_\/\\_\_\_ +**\** \/ +**\** something that looks like that +**\** then any transactions that conflict in the pair of non-linearly-ordered blocks will appear to conflict forever +**\** this allows a clumsy user who re-sends a transaction twice becuase he's foolish to lose his funds. +**\** Can we back this up with a simulation? +**\** i mean, we could, but there's a solid chain of lemmas that lead to a theorem i can write up later if you like +**\** using the theorems about how rapidly sets in spectre get finalized +**\** Even better +**\** \*lemmata +**\** now, the spectre authors said "the only reason someone would relay two transactions like this is to attempt a double spend, so it's okay that the funds are lost." +**\** lolwut +**\** well +**\** the idea is that htey are *two* transactions with valid signatures using the same input +**\** or rather, using at least one of the same inputs +**\** so by definition, it's a double spend +**\** and i can't really think of a scenario where someone would compute two signatures separately like that, then relay them nearly simultaneously like that... on accident +**\** BUT +**\** it's enough of a leap for me to be concerned +**\** moreover +**\** i'm not sure if that sort of "double spend implies money lost forever instead of "eventually one of the two spends is accepted." +**\** and what's really crazy +**\** is that if block arrival times are very fast, like 10/s as in the original spectre paper... this problem is solved *with high probability* +**\** so, that's where SPECTRE is sitting. +**\** and lastly, my viewkey proposal +**\** s/lost forever/lost forever" philosophy instead of... +**\** I own address A, B, and C. I simultaneously send the same output as an input in txns A ->** B and A ->** C. Free coins? Or B and C each now have unspendable outputs? +**\** a miner would see two conflicting transactions, so neither would be considered valid +**\** and constructing another transaction later A->**D will also be considered invalid +**\** Ah. Thanks. +**\** so until spectre re-orgs the block-DAG so that the transaction A->**B precedes A->**C or vice versa, it's locked forever +**\** right, i was wondering that... i though eventually it resolves to a bloclchain +**\** or blockchain +**\** actually, that's the problem: if block arrival rate is slow and you have a fork +**\** the next block to arrive will point to both blocks as parents +**\** yeah +**\** and if all blocks from there on out point to that common child block, those two blocks will never be linearly ordered +**\** so, this would also be solved by simply telling people to try to avoid making more than 1 transaction per target block arrival rate *personally* +**\** otherwise they are burning their own money, in a sense +**\** that's quite the kludge +**\** so dbl spends are punished... kinda +**\** gingeropolous: yes, it provides a strong incentive against making a double spend attack +**\** which is nice +**\** i just don't want to make it so that badly informed users of Monero don't accidentally burn their money +**\** i wonder if we could protocolize an incubate function, where a tx has to sit in the txpool for n blocks +**\** sarang it's not too much of a kludge, if our block arrival rate is 1/second or something +**\** hmm +**\** gingeropolous: ooooh +**\** kind of a bitch because timestamping and all.. +**\** it's worth thinking about though! +**\** that's a good idea +**\** okay, so does anyone else have anything they want to share about their work? +**\** I could add that I've posted my monthly report: https://www.reddit.com/r/Monero/comments/7frn7i/november_monthly_report_from_sarang_noether/ +**\** Comments welcome +**\** Also, I'd like to thank the community for funding me as well +**\** It's astonishing +**\** In other announcements.... +**\** rehrar is working on the next Monero Revuo +**\** I'm not sure what the publication timeline on that is supposed to be +**\** but it's the quarterly newsletter wherein he sort of interviews the teams at MRL in charge of various projects +**\** Any other discussion items? +**\** he and Sarang and I are going to have a sit-down and talk about the direction MRL is heading. I am interested in writing up current standards for Monero, I know Sarang is also, and I want to start on that as soon as Multisig is done. +**\** ah yes +**\** For each Monero standard, I also want to write up at least one proposal for replacing the standard in the case that the security of that standard is compromised +**\** I also want to compile arguments for and against replacing certain standards sooner rather than later, for example, our "nonstandard" hash function +**\** oh man, i should ping andytoshi too +**\** this includes our proof of work standard +**\** That strikes me as our least-standard "thing" +**\** cryptonight has some value, but it's as homebrew as can be +**\** yeah +**\** i wouldn't mind putting up a portion of my funding for this period toward a Proof of Work contest for Monero's replacement proof of work scheme +**\** hmm +**\* iDunk** reaches for a pitchfork +**\** ? +**\** cryptonight has value because of asic resistance. i'm okay with asics if they are commoditized. i'm not married to cryptonight in any way +**\** i'm in a non-monogamous relationship with cryptonight +**\** ok, well +**\** anything else to discuss? +**\** i wouldn't mind putting up a portion of my funding for this period toward a Proof of Work contest for Monero's replacement proof of work scheme \<= I think othe already has some back up plans +**\** apparently V wants ringCT in EVM2 +**\** You might want to talk to him about it +**\** othe are you around? +**\** Yes +**\** silur V = vitalik? +**\** yep +**\** othe you've been thinking about POW? +**\** Yea +**\** Slight changes we can implement will break all asics +**\** I introduced stringCT/ruffCT PoC code in our research channel hope it will go somewhere +**\** Trivial to implement in cpu and gpu +**\** oooh, that's fantastic! fluffypony sent me at least one recommendation for that a few weeks ago +**\** but i haven't had time to look into it +**\** Yeah that one is an example +**\** what is this new POW? +**\** ok, but you aren't talking about *replacing cryptonight* but modifying it +**\** silur othe has apparently been looking at the cryptonight code very closely and determining how to swap bits around or mess with the implementation to improve asic resistance without harming gpu or cpu performance +**\** Just modifying it randomly +**\** I thought cryptonight is asic resistant by design O.o +**\** Takes like 5 lines of code in gpu miner +**\** I knew that it's not like... cuckoo cycle hard but still +**\** Cuckoo is not hard at all +**\** yeah cuckoo isn't asic resistant at all +**\** i have a paper around here about it +**\** dayum +**\** silur cryptonight takes up L3 cache like crazy, so the asic resistance comes from forcing it through a bottleneck +**\** but you could still have an asic on the back end of the bottleneck +**\** There's really nothing asic resistant if u hsve money +**\** so if someone creatively designed a computer with a huge L3 cache or something like that... +**\** which normally you wouldn't have to worry about for something like SHA256 +**\** then the asic is still technically possible, we're just... resistant to it +**\** because it requires novel computer architecture and design +**\** othe i'm very glad to hear you have been working on this +**\** ended the meeting a little too early, sarang. :\ +**\** I'm following along on the bus +**\** The bus smells like ass today +**\** http://www.cs.cmu.edu/~dga/crypto/cuckoo/analysis.pdf +**\** Well i don't have a problem with asics but sth like shitmain has to be killed of when trying +**\** nope, that's not the paper i was looking at +**\** othe my primary concern is decentralization, whether it's through asic resistance or asic commoditization. the idea of cpu mining is great in some ways, but i like andytoshi's paper on the thermodynamic minimum *a whole lot.* +**\** like, his paper made me realize that proof-of-storage or something like that? the universal minimum will be determined by the speed of light +**\** so instead of commoditized hardware mining, you would see massive massive data centers all with fiber optic cables of *exactly the same length* to avoid time effects from light speed, etc etc +**\** so anyway +**\** this is probably useless info at this point as its all rumors, but https://rmc.one/ has said they are working on a cryptonight asic +**\** oh yes, that is the paper. :P http://www.cs.cmu.edu/~dga/crypto/cuckoo/analysis.pdf +**\** unknownids: eh, the minute they blow a million on taping out a few asics, we'll implement the first of othe's list of changes. :P they'll have to retape, best case scenario... and then we do it again... +**\** Rmc one are idiots but rwal companies might be +**\** it's easier for us to change the algo than it is for them to pump out asics +**\** tbh if i were in the asic business i wouldn't make a move without blessings and guidance from the developers of the coin +**\** good to know othe +**\** because they'll just change their code if they don't like what you are doing +**\** ^ +**\** whoever is designing asics for monero are preparing to burn their fiat. but hey, they probably have fiat to burn +**\** joker.jpg +**\** ok guys +**\** i'll be back later today +**\** entrepreneurs will always find a way to get above others; be it ASIC or botnets or webminers; what's important is that there's no barrier to entry for new players so that nobody's position is forever assured \ No newline at end of file -- GitLab From 45985c48cf478d73ec51c9145b59105bd418459d Mon Sep 17 00:00:00 2001 From: erciccione Date: Wed, 1 Nov 2017 11:33:46 +0100 Subject: [PATCH 10/43] add merchants to list --- _data/merchants.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/_data/merchants.yml b/_data/merchants.yml index 402f997a..49d9d16d 100644 --- a/_data/merchants.yml +++ b/_data/merchants.yml @@ -146,6 +146,8 @@ url: http://www.guitartheoryrevolution.info/blog/guitar-theory-revolution-store/ - name: Infield Loan Services - Atlanta, Construction Consulting, Contract review, Feasibility, Funds Escrow url: mailto:info@loandraw.com + - name: K9 Satisfaction - Premium dog training + url: http://www.k9satisfaction.com/ - name: KoDDoS.net - DDoS Protection url: https://koddos.net - name: Marcos Aguayo - Programmer and Web Developer -- GitLab From 9c7eac1cb46c97a11417e820b04ff19b21d69a82 Mon Sep 17 00:00:00 2001 From: erciccione Date: Wed, 8 Nov 2017 23:34:07 +0100 Subject: [PATCH 11/43] add merchant gameofcryptos --- _data/merchants.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/_data/merchants.yml b/_data/merchants.yml index 49d9d16d..ec521f6c 100644 --- a/_data/merchants.yml +++ b/_data/merchants.yml @@ -193,6 +193,8 @@ url: http://directvoltage.com - name: Fine Art from Jeanine King ~ Artwork of Home/Archtecture, Pets, Potraits, Caricatures ~ International Shipping url: http://art2unlimited.webs.com/ + - name: Game of Cryptos + url: https://gameofcryptos.com/ - name: Handcrafted goods url: https://mychain.store/ - name: InvestmentArt -- GitLab From 2cd70431dd0661285da304dfeaf38fcd8c0608c1 Mon Sep 17 00:00:00 2001 From: erciccione Date: Thu, 9 Nov 2017 19:56:12 +0100 Subject: [PATCH 12/43] add monerowallet --- _data/merchants.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/_data/merchants.yml b/_data/merchants.yml index ec521f6c..2ccae5ec 100644 --- a/_data/merchants.yml +++ b/_data/merchants.yml @@ -170,6 +170,8 @@ url: https://www.thebigcoin.io - name: Tuxcon Hosting - Mail and Web Hosting url: https://tuxcon.com + - name: WalletMonero - Online Wallet + url: https://walletmonero.com?utm_source=getmonero_org&utm_medium=list&utm_content=monero_list&utm_campaign=getmonero_org - name: Web Developer - Python with Django web framework url: http://www.voteforrodneylewis.com - name: Web Developer - Stefanos -- GitLab From 9a07b8602491ec056ac08ea72a76193e277851dc Mon Sep 17 00:00:00 2001 From: erciccione Date: Mon, 20 Nov 2017 04:10:21 +0100 Subject: [PATCH 13/43] add merchant changenow --- _data/merchants.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/_data/merchants.yml b/_data/merchants.yml index 2ccae5ec..78aec5a7 100644 --- a/_data/merchants.yml +++ b/_data/merchants.yml @@ -15,6 +15,8 @@ url: https://www.bittrex.com/Market/Index?MarketName=BTC-XMR - name: Bter url: https://bter.com/ + - name: ChangeNOW + url: https://changenow.io?utm_source=monero&utm_medium=link&utm_term=merchants&utm_campaign=monero - name: CoinCut (OTC) url: https://www.coincut.com - name: Cryptopia -- GitLab From 8fd2e27a717db062d3de4dcd2a0f1d57bb02bcff Mon Sep 17 00:00:00 2001 From: erciccione Date: Tue, 21 Nov 2017 02:51:50 +0100 Subject: [PATCH 14/43] add merchant go forward software --- _data/merchants.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/_data/merchants.yml b/_data/merchants.yml index 78aec5a7..be3036a1 100644 --- a/_data/merchants.yml +++ b/_data/merchants.yml @@ -144,6 +144,8 @@ url: https://flokinet.is - name: Fork Networking, Inc. - Colocation, Dedicated Servers, VPS url: http://www.forked.net/ + - name: Go Forward Software + url: https://www.goforwardsoftware.com - name: Guitar Music Theory course w/ 30% XMR discount url: http://www.guitartheoryrevolution.info/blog/guitar-theory-revolution-store/ - name: Infield Loan Services - Atlanta, Construction Consulting, Contract review, Feasibility, Funds Escrow -- GitLab From 04115cde16fc9e4322953e8b242daf7076225eac Mon Sep 17 00:00:00 2001 From: serhack <27734319+serhack@users.noreply.github.com> Date: Mon, 20 Nov 2017 14:36:09 +0100 Subject: [PATCH 15/43] Fix a little bug --- blog/index.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/blog/index.html b/blog/index.html index e7835423..fd3bad68 100644 --- a/blog/index.html +++ b/blog/index.html @@ -9,7 +9,7 @@ title: All Blog Posts {{ post.summary }} {% t blog.tagged %}: {% for tag in post.tags %} - [{{ tag }}] + [{{ tag }}] {% endfor %}

@@ -40,4 +40,4 @@ title: All Blog Posts Next » {% endif %} -{% endif %} \ No newline at end of file +{% endif %} -- GitLab From a1370e669b1a070e5c1a390d0d130b73e19cade0 Mon Sep 17 00:00:00 2001 From: Matt Smith Date: Wed, 22 Nov 2017 16:16:06 +0000 Subject: [PATCH 16/43] Add 99Stack.com Fix #488 --- _data/merchants.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/_data/merchants.yml b/_data/merchants.yml index be3036a1..b16eb779 100644 --- a/_data/merchants.yml +++ b/_data/merchants.yml @@ -118,6 +118,8 @@ - category: Services id: services merchants: + - name: 99Stack Hosting + url: https://www.99stack.com - name: AirVPN url: https://airvpn.org/ - name: algoStrategic - Internet Marketing and Web Development -- GitLab From e7eb33f6cc6ec0d000d78d6a516950cdcc67abab Mon Sep 17 00:00:00 2001 From: Leon Klingele Date: Tue, 7 Nov 2017 01:52:45 +0100 Subject: [PATCH 17/43] Fix link to OpenAlias page --- resources/moneropedia/address.md | 2 +- resources/moneropedia/openalias.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/resources/moneropedia/address.md b/resources/moneropedia/address.md index ed33f15a..54492c65 100644 --- a/resources/moneropedia/address.md +++ b/resources/moneropedia/address.md @@ -11,7 +11,7 @@ When you send Monero to someone you only need one piece of information, and that Because those addresses are long and complex you will often encounter an @OpenAlias address instead. For example, Monero donations can be sent to donate@getmonero.org or donate.getmonero.org. -If you would like to get an @OpenAlias address of your own then there is some information on the [OpenAlias page](/knowledge-base/openalias). +If you would like to get an @OpenAlias address of your own then there is some information on the [OpenAlias page](/resources/openalias). ### Integrated address diff --git a/resources/moneropedia/openalias.md b/resources/moneropedia/openalias.md index 2410130c..c2e68d7a 100644 --- a/resources/moneropedia/openalias.md +++ b/resources/moneropedia/openalias.md @@ -17,4 +17,4 @@ At its most basic, OpenAlias is a TXT DNS record on a FQDN (fully qualified doma {{ page.summary | capitalize }}. -More information can be found on the [OpenAlias page](/knowledge-base/openalias) or on the [OpenAlias website](https://openalias.org) +More information can be found on the [OpenAlias page](/resources/openalias) or on the [OpenAlias website](https://openalias.org) -- GitLab From 28361e92693835fce301089f60345a0b073a6fe9 Mon Sep 17 00:00:00 2001 From: Leon Klingele Date: Tue, 7 Nov 2017 01:53:14 +0100 Subject: [PATCH 18/43] Remove duplicate 'the' --- resources/moneropedia/change.md | 2 +- resources/user-guides/importing_blockchain.md | 2 +- resources/user-guides/website-merchants.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/resources/moneropedia/change.md b/resources/moneropedia/change.md index 08163292..066cfa6a 100644 --- a/resources/moneropedia/change.md +++ b/resources/moneropedia/change.md @@ -11,6 +11,6 @@ summary: "Monero sent as part of a transaction, that returns to your account ins ### More Information -The @wallet in the the Monero software makes change automatically, but when you send a transaction, you are taking an @input that you control and telling the Monero network what to do with it. The @input is a "deposit" to your account that you are able to spend. @Outputs are the part of the transaction that tells the Monero network where to send the funds. +The @wallet in the Monero software makes change automatically, but when you send a transaction, you are taking an @input that you control and telling the Monero network what to do with it. The @input is a "deposit" to your account that you are able to spend. @Outputs are the part of the transaction that tells the Monero network where to send the funds. You might have multiple inputs in your account, in many different denominations (For example: you deposited 0.5 XMR on Friday, and 0.75 XMR on Saturday). So, when have a transaction with an input of 0.5 XMR, but you only want to send 0.1 XMR, your transaction will include a @fee to pay the @miner, an output for 0.1 XMR to send to the recipient, and the rest that you want to send back to yourself will be an output back to you (this is called "change"). Once the transaction is completed, the change becomes available to you as an input that you can again split and send with a new transaction. diff --git a/resources/user-guides/importing_blockchain.md b/resources/user-guides/importing_blockchain.md index 3396a690..8d7c1a7a 100644 --- a/resources/user-guides/importing_blockchain.md +++ b/resources/user-guides/importing_blockchain.md @@ -55,7 +55,7 @@ If you downloaded the Blockchain from a trusted, reputable source you may set `v ### Step 7 -After the the Blockchain has finished syncing up you can open your Monero wallet normally. Your downloaded blockchain.raw can be deleted. +After the Blockchain has finished syncing up you can open your Monero wallet normally. Your downloaded blockchain.raw can be deleted. Author: Kee Jefferys \ No newline at end of file diff --git a/resources/user-guides/website-merchants.md b/resources/user-guides/website-merchants.md index cdc4497a..b7056ae0 100644 --- a/resources/user-guides/website-merchants.md +++ b/resources/user-guides/website-merchants.md @@ -16,7 +16,7 @@ Find the category that best describes your business/service and copy the code be and paste it in the correct category under the `merchants:` section. Fill in the data as follows: -* `name:` The name of the the business/service. +* `name:` The name of the business/service. * `url:` The external url of the business/service. This link must have http:// (or https://) at the beginning if it is an external link. **Make sure the indentation is EXACTLY the same as the other proposals in the area. If it's not the jekyll build WILL fail.** -- GitLab From e966a2ea67aa56cfb69a610148b98689ec893fba Mon Sep 17 00:00:00 2001 From: Leon Klingele Date: Tue, 7 Nov 2017 23:53:08 +0100 Subject: [PATCH 19/43] Remove redundant 'a' --- resources/moneropedia/denominations.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/resources/moneropedia/denominations.md b/resources/moneropedia/denominations.md index 24bda241..f6ed8eb3 100644 --- a/resources/moneropedia/denominations.md +++ b/resources/moneropedia/denominations.md @@ -2,12 +2,12 @@ layout: moneropedia entry: "Denominations" terms: ["denominations", "subunits", "tacoshi", "piconero", "nanonero", "micronero", "millinero", "centinero", "decinero","decanero","hectonero","kilonero","meganero","giganero"] -summary: "A denomination is a proper description of a currency amount. It is oftentimes a sub-unit of the currency. For example, traditionally a cent is 1/100th of a a particular unit of currency.)" +summary: "A denomination is a proper description of a currency amount. It is oftentimes a sub-unit of the currency. For example, traditionally a cent is 1/100th of a particular unit of currency.)" --- ### The Basics -A denomination is a proper description of a currency amount, oftentimes a sub-unit of the currency (for example, traditionally a cent is 1/100th of a a unit of currency). Monero denomination names add SI prefixes after dropping the initial "mo" for ease of use. The smallest unit of Monero is 1 piconero (0.000000000001 XMR). +A denomination is a proper description of a currency amount, oftentimes a sub-unit of the currency (for example, traditionally a cent is 1/100th of a unit of currency). Monero denomination names add SI prefixes after dropping the initial "mo" for ease of use. The smallest unit of Monero is 1 piconero (0.000000000001 XMR). ### Denominations of Monero -- GitLab From 1a1e89f00bca669a34c2b108d181e343e7a9eddf Mon Sep 17 00:00:00 2001 From: Leon Klingele Date: Tue, 7 Nov 2017 23:56:58 +0100 Subject: [PATCH 20/43] moneropedia/denominations: Reuse summary instead of repeating ourself --- resources/moneropedia/denominations.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/resources/moneropedia/denominations.md b/resources/moneropedia/denominations.md index f6ed8eb3..e03c2ecd 100644 --- a/resources/moneropedia/denominations.md +++ b/resources/moneropedia/denominations.md @@ -7,7 +7,9 @@ summary: "A denomination is a proper description of a currency amount. It is oft ### The Basics -A denomination is a proper description of a currency amount, oftentimes a sub-unit of the currency (for example, traditionally a cent is 1/100th of a unit of currency). Monero denomination names add SI prefixes after dropping the initial "mo" for ease of use. The smallest unit of Monero is 1 piconero (0.000000000001 XMR). +{{ page.summary | capitalize }}. + +Monero denomination names add SI prefixes after dropping the initial "mo" for ease of use. The smallest unit of Monero is 1 piconero (0.000000000001 XMR). ### Denominations of Monero @@ -31,6 +33,4 @@ A denomination is a proper description of a currency amount, oftentimes a sub-un ### In-depth Information -Support for input using SI prefixes was [added to the Monero codebase](https://github.com/monero-project/monero/pull/1826) on March 3, 2017 by [Moneromooo](https://github.com/moneromooo-monero). The smallest unit of monero (10^-12 XMR) was originally called a tacoshi in honor of user [Tacotime](https://bitcointalk.org/index.php?action=profile;u=19270), an early Monero contributor and was later renamed for ease of use and consistancy. - -{{ page.summary | capitalize }}. +Support for input using SI prefixes was [added to the Monero codebase](https://github.com/monero-project/monero/pull/1826) on March 3, 2017 by [Moneromooo](https://github.com/moneromooo-monero). The smallest unit of Monero (10^-12 XMR) was originally called a tacoshi in honor of user [Tacotime](https://bitcointalk.org/index.php?action=profile;u=19270), an early Monero contributor and was later renamed for ease of use and consistancy. -- GitLab From b5923ac62e2d4b668543e46b3fca337a364dc3a5 Mon Sep 17 00:00:00 2001 From: Leon Klingele Date: Wed, 8 Nov 2017 00:50:45 +0100 Subject: [PATCH 21/43] Fix other stuff I didn't like / was incorrect Sorry for throwing everything into one commit, splitting my changes to individual will probably take ages. --- resources/moneropedia/blockchain.md | 2 +- resources/moneropedia/change.md | 4 ++-- resources/moneropedia/cryptocurrency.md | 10 +++++----- resources/moneropedia/destination.md | 2 +- resources/moneropedia/fungibility.md | 9 +++++---- resources/moneropedia/i2pcontrol.md | 2 +- resources/moneropedia/miners.md | 12 +++++------- resources/moneropedia/mnemonicseed.md | 2 +- resources/moneropedia/node.md | 8 ++++---- resources/moneropedia/paymentid.md | 8 +++++--- resources/moneropedia/pedersen-commitment.md | 8 ++++---- resources/moneropedia/ringCT.md | 11 +---------- resources/moneropedia/ringsignatures.md | 2 +- resources/moneropedia/smartmining.md | 4 +--- resources/moneropedia/tail-emission.md | 2 +- resources/moneropedia/transaction.md | 4 +++- resources/moneropedia/viewkey.md | 8 +++----- 17 files changed, 44 insertions(+), 54 deletions(-) diff --git a/resources/moneropedia/blockchain.md b/resources/moneropedia/blockchain.md index d20e8cf7..5b4d8fd9 100644 --- a/resources/moneropedia/blockchain.md +++ b/resources/moneropedia/blockchain.md @@ -10,4 +10,4 @@ summary: "a distributed ledger of all transactions both past and present, withou A @blockchain is a distributed database that continuously grows with a record of all of the transactions that have occurred with a given cryptocurrency. This database is often referred to as a ledger because the data contains a large list of transactions that have taken place. In Monero, these transactions are packaged together into 'blocks' every 2 minutes (on average) and all miners and nodes on the network have copies of these blocks. ### Monero's @Blockchain -Unlike Bitcoin and other cryptocurrencies, transactions in the Monero @blockchain do not reveal where funds came from or went to, providing anonymity and making the currency completely @fungible. Additionally, the amounts of all transactions are hidden by @RingCT, a feature of Monero. For auditing or other transparency purposes a user can share a @view-key to prove they control certain amounts of @Moneroj. +Unlike Bitcoin and other cryptocurrencies, transactions in the Monero @blockchain do not reveal where funds came from or went to, providing anonymity and making the currency completely [fungible](fungibility). Additionally, the amounts of all transactions are hidden by @RingCT, a feature of Monero. For auditing or other transparency purposes a user can share a @view-key to prove they control certain amounts of Moneroj. diff --git a/resources/moneropedia/change.md b/resources/moneropedia/change.md index 066cfa6a..7516cf94 100644 --- a/resources/moneropedia/change.md +++ b/resources/moneropedia/change.md @@ -11,6 +11,6 @@ summary: "Monero sent as part of a transaction, that returns to your account ins ### More Information -The @wallet in the Monero software makes change automatically, but when you send a transaction, you are taking an @input that you control and telling the Monero network what to do with it. The @input is a "deposit" to your account that you are able to spend. @Outputs are the part of the transaction that tells the Monero network where to send the funds. +The @wallet in the Monero software makes change automatically, but when you send a transaction, you are taking an input that you control and telling the Monero network what to do with it. The input is a "deposit" to your account that you are able to spend. Outputs are the part of the transaction that tells the Monero network where to send the funds. -You might have multiple inputs in your account, in many different denominations (For example: you deposited 0.5 XMR on Friday, and 0.75 XMR on Saturday). So, when have a transaction with an input of 0.5 XMR, but you only want to send 0.1 XMR, your transaction will include a @fee to pay the @miner, an output for 0.1 XMR to send to the recipient, and the rest that you want to send back to yourself will be an output back to you (this is called "change"). Once the transaction is completed, the change becomes available to you as an input that you can again split and send with a new transaction. +You might have multiple inputs in your account, in many different denominations (For example: you deposited 0.5 XMR on Friday, and 0.75 XMR on Saturday). So, when have a transaction with an input of 0.5 XMR, but you only want to send 0.1 XMR, your transaction will include a fee to pay the @miner, an output for 0.1 XMR to send to the recipient, and the rest that you want to send back to yourself will be an output back to you (this is called "change"). Once the transaction is completed, the change becomes available to you as an input that you can again split and send with a new transaction. diff --git a/resources/moneropedia/cryptocurrency.md b/resources/moneropedia/cryptocurrency.md index 45d736c2..9aa2831b 100644 --- a/resources/moneropedia/cryptocurrency.md +++ b/resources/moneropedia/cryptocurrency.md @@ -11,12 +11,12 @@ summary: "a digital currency in which encryption techniques are used to regulate ### More Information -Cryptocurrency is the generic term for a large set of digital assets that use encryption techniques to generate units of currency, verify the transactions, and transfer value. Generally, cryptocurrencies are considered to be decentralized. Cryptocurrency should not be confused with virtual currency which is a type of digital money that is usually controlled by it's creators or developers. (Some examples of virtual currency are gametime in World of Warcraft, ROBUX in Roblox, reward points programs, or Ripple, all of which can be exchanged for currency or cash value, but are not considered cryptocurrency because they are centalized and controlled/issued by a single entity). +Cryptocurrency is the generic term for a large set of digital assets that use encryption techniques to generate units of currency, verify the transactions, and transfer value. Generally, cryptocurrencies are considered to be decentralized. Cryptocurrency should not be confused with virtual currency which is a type of digital money that is usually controlled by its creators or developers. Some examples of virtual currency are gametime in World of Warcraft, ROBUX in Roblox, reward points programs, or Ripple, all of which can be exchanged for currency or cash value, but are not considered cryptocurrency because they are centalized and controlled/issued by a single entity. -Monero is one of many cryptocurrencies currently available. Other examples are Bitcoin, Litecoin, Dogecoin, Dash, Zcash, etc, but nearly all other cryptocurrencies lack features that make them a true money (most importantly @fungability which is a requirement for it to be a @store-of-value). +Monero is one of many cryptocurrencies currently available. Other examples are Bitcoin, Litecoin, Dogecoin, Dash, Zcash, etc, but nearly all other cryptocurrencies lack features that make them a true money (most importantly @fungibility which is a requirement for it to be a store-of-value). -Not all cryptocurrencies operate the same, but they usually share the properties of @decentralization, encryption, and the ability to send and receive transactions. Most are irreversible, pseudonymous, global, and permissionless. Most aim to be a @store-of-value or be digital cash that allows you to transact. +Not all cryptocurrencies operate the same, but they usually share the properties of decentralization, encryption, and the ability to send and receive transactions. Most are irreversible, pseudonymous, global, and permissionless. Most aim to be a store-of-value or be digital cash that allows you to transact. -Most cryptocurrencies (including Monero) use a distributed ledger (called a @blockchain) to keep track of previous transactions . The blockchain serves to tell other users on the network that transactions have happened. There are many different ways for cryptocurrencies to create their blockchain, and not all are the same. Monero uses @proof-of-work to craft blocks, where other cryptocurrencies may use proof-of-stake or other consolidated methods. +Most cryptocurrencies (including Monero) use a distributed ledger (called a @blockchain) to keep track of previous transactions. The blockchain serves to tell other users on the network that transactions have happened. There are many different ways for cryptocurrencies to create their blockchain, and not all are the same. Monero uses proof-of-work to craft blocks, where other cryptocurrencies may use proof-of-stake or other consolidated methods. -Ultimately, cryptocurrency is an attempt to create @trustless value; that is free from borders, governments, and banks. Whether that be to transact or to be digital gold is up to the users of each. +Ultimately, cryptocurrency is an attempt to create trustless value; that is free from borders, governments, and banks. Whether that be to transact or to be digital gold is up to the users of each. diff --git a/resources/moneropedia/destination.md b/resources/moneropedia/destination.md index a999bebf..e7263f9a 100644 --- a/resources/moneropedia/destination.md +++ b/resources/moneropedia/destination.md @@ -12,7 +12,7 @@ A @destination is the @I2P @in-net address of the final endpoint you are trying ### In-depth Information -An @I2P destination can be encoded into a @base32-address or @base64-address. Most users will only care about @base32-address or a `.i2p` hostname while, internally, @Kovri / @I2P @address-book uses @base64-addresses. Ultimately, all @destinations in @I2P are 516-byte (or longer) keys: +An @I2P destination can be encoded into a @base32-address or @base64-address. Most users will only care about @base32-addresses or a `.i2p` hostname while, internally, @Kovri / @I2P @address-book uses @base64-addresses. Ultimately, all @destinations in @I2P are 516-byte (or longer) keys: `256-byte public key + 128-byte signing key + a null certificate = 516 bytes in Base64 representation` diff --git a/resources/moneropedia/fungibility.md b/resources/moneropedia/fungibility.md index 47ca7d01..87bd6839 100644 --- a/resources/moneropedia/fungibility.md +++ b/resources/moneropedia/fungibility.md @@ -7,10 +7,11 @@ summary: "property of a currency whereby two units can be substituted in place o ### The Basics -Fungibility means that two units of a currency can be mutually substituted and the substituted currency is equal to another unit of the same size. For example, two $10 bills can be exchanged and they are functionally identical to any other $10 bills in circulation (although $10 bills have unique ID numbers and are therefore not completely fungible). Gold is probably a closer example of true fungibility, where any 1 oz. of gold of the same grade is worth the same as another 1 oz of gold. Monero is fungible due to the nature of the currency which provides no way to link transactions together nor trace the history of any particular XMR. 1 XMR is functionally identical to any other 1 XMR. +{{ page.summary | capitalize }}. -Fungibility is an advantage Monero has over Bitcoin and almost every other cryptocurrency, due to the privacy inherent in the Monero @blockchain and the permanently traceable nature of the Bitcoin blockchain. With Bitcoin, any BTC can be tracked by anyone back to it's creation @coinbase-transaction. Therefore, if a coin has been used for an illegal purpose in the past, this history will be contained in the @blockchain in perpetuity. This lack of fungibility means that certain businesses will be obligated to avoid accepting BTC that have been previously used for purposes which are illegal, or simply run afoul of their Terms of Service. Currently some large Bitcoin companies are blocking, suspending, or closing accounts that have received Bitcoin used in online gambling or other purposes deemed unsavory by said companies. +Fungibility means that two units of a currency can be mutually substituted and the substituted currency is equal to another unit of the same size. For example, two $10 bills can be exchanged and they are functionally identical to any other $10 bill in circulation (although $10 bills have unique ID numbers and are therefore not completely fungible). Gold is probably a closer example of true fungibility, where any 1 oz. of gold of the same grade is worth the same as another 1 oz. of gold. Monero is fungible due to the nature of the currency which provides no way to link transactions together nor trace the history of any particular XMR. 1 XMR is functionally identical to any other 1 XMR. -Monero has been built specifically to address the problem of traceability and non-fungability inherent in other cryptocurrencies. By having completely private transactions Monero is truly fungible and there can be no blacklisting of certain XMR, while at the same time providing all the benefits of a secure, decentralized, permanent blockchain. +Fungibility is an advantage Monero has over Bitcoin and almost every other cryptocurrency, due to the privacy inherent in the Monero @blockchain and the permanently traceable nature of the Bitcoin blockchain. With Bitcoin, any BTC can be tracked by anyone back to its creation @coinbase-transaction. Therefore, if a coin has been used for an illegal purpose in the past, this history will be contained in the @blockchain in perpetuity. This lack of fungibility means that certain businesses will be obligated to avoid accepting BTC that have been previously used for purposes which are illegal, or simply run afoul of their Terms of Service. Currently some large Bitcoin companies are blocking, suspending, or closing accounts that have received Bitcoin used in online gambling or other purposes deemed unsavory by said companies. + +Monero has been built specifically to address the problem of traceability and non-fungibility inherent in other cryptocurrencies. By having completely private transactions Monero is truly fungible and there can be no blacklisting of certain XMR, while at the same time providing all the benefits of a secure, decentralized, permanent blockchain. -{{ page.summary | capitalize }}. diff --git a/resources/moneropedia/i2pcontrol.md b/resources/moneropedia/i2pcontrol.md index 481d9eae..285e1302 100644 --- a/resources/moneropedia/i2pcontrol.md +++ b/resources/moneropedia/i2pcontrol.md @@ -8,7 +8,7 @@ summary: "An API inteface for Kovri and Java-I2P that allows simple remote contr ### The Basics -@I2Pcontrol is [JSONRPC2](https://en.wikipedia.org/wiki/JSON-RPC) [API](https://en.wikipedia.org/wiki/Application_programming_interface) for @Kovri and @Java-I2P which allows an @I2PControl client to remote control/monitor a running instance. +@I2Pcontrol is a [JSONRPC2](https://en.wikipedia.org/wiki/JSON-RPC) [API](https://en.wikipedia.org/wiki/Application_programming_interface) for @Kovri and @Java-I2P which allows an @I2PControl client to remote control/monitor a running instance. Two available @I2PControl clients are: [qtoopie](https://github.com/EinMByte/qtoopie) (C++ client) and [itoopie](https://github.com/i2p/i2p.itoopie) (Java client). Read `kovri.conf` to configure @I2PControl for @Kovri. diff --git a/resources/moneropedia/miners.md b/resources/moneropedia/miners.md index 5937ce6d..9638dd48 100644 --- a/resources/moneropedia/miners.md +++ b/resources/moneropedia/miners.md @@ -7,14 +7,12 @@ summary: "the process of cryptographically computing a mathematical proof for a ### The Basics -Mining is the distributed process of confirming transactions on the public ledger of all transactions, aka @blockchain. Monero nodes use the block chain to distinguish legitimate transactions from attempts to re-spend coins that have already been spent elsewhere. - -Monero is powered strictly by Proof of Work. It employs a mining algorithm that has the potential to be efficiently tasked to billions of existing devices (any modern x86 CPU and many GPU's). Monero uses the @CryptoNight Proof of Work (@PoW) algorithm, which is designed for use in ordinary CPUs and GPUs. - -The smart mining feature allows transparent CPU mining on the user's computer, far from the de facto centralization of mining farms and pool mining, pursuing Satoshi Nakamoto's original vision of a true P2P currency. +{{ page.summary | capitalize }}. -As of June 2017, botnets made of hacked computers account for a not-insignificant portion of the miners on the Monero network. This is due to the profitability of mining on CPUs via the @CryptoNight algorithm. +Mining is the distributed process of confirming transactions on the public ledger of all transactions, aka @blockchain. Monero nodes use the blockchain to distinguish legitimate transactions from attempts to re-spend coins that have already been spent elsewhere. +Monero is powered strictly by Proof of Work. It employs a mining algorithm that has the potential to be efficiently tasked to billions of existing devices (any modern x86 CPU and many GPUs). Monero uses the CryptoNight Proof of Work (PoW) algorithm, which is designed for use in ordinary CPUs and GPUs. +The smart mining feature allows transparent CPU mining on the user's computer, far from the de facto centralization of mining farms and pool mining, pursuing Satoshi Nakamoto's original vision of a true P2P currency. -{{ page.summary | capitalize }}. +As of June 2017, botnets made of hacked computers account for a not-insignificant portion of the miners on the Monero network. This is due to the profitability of mining on CPUs via the CryptoNight algorithm. diff --git a/resources/moneropedia/mnemonicseed.md b/resources/moneropedia/mnemonicseed.md index 608f8d8b..57ab9aaa 100644 --- a/resources/moneropedia/mnemonicseed.md +++ b/resources/moneropedia/mnemonicseed.md @@ -2,7 +2,7 @@ layout: moneropedia entry: "Mnemonic Seed" terms: ["mnemonic-seed", "mnemonic"] -summary: "a 13 or 25 word phrase used to backup a Monero account, available in a number of languages" +summary: "a 13 or 25 word phrase used to back up a Monero account, available in a number of languages" --- ### The Basics diff --git a/resources/moneropedia/node.md b/resources/moneropedia/node.md index dde76903..46a0bcbe 100644 --- a/resources/moneropedia/node.md +++ b/resources/moneropedia/node.md @@ -11,13 +11,13 @@ summary: "a device on the Internet running the Monero software, with a full copy ### More Information -Nodes participate in the Monero network and secure @transactions by enforcing the rules of the network. Nodes download the entire @blockchain to know what transactions have taken place. Nodes assist the network by relaying transactions to other nodes on the network. Nodes may also choose contribute to the Monero network by participating in crafting @blocks (this is called @mining). +Nodes participate in the Monero network and secure @transactions by enforcing the rules of the network. Nodes download the entire @blockchain to know what transactions have taken place. Nodes assist the network by relaying transactions to other nodes on the network. Nodes may also choose to contribute to the Monero network by participating in crafting @blocks (this is called @mining). -Mining is the process by which nodes create a block from the previously accepted block, transactions that are waiting to be processed in the @tx-pool, and the @coinbase. When a node believes it has crafted a valid block it will transmit the completed block to other nodes on the network and those nodes signal agreement by working on the next block in the chain. +Mining is the process by which nodes create a block from the previously accepted block, transactions that are waiting to be processed in the Transaction Pool, and the @coinbase-transaction. When a node believes it has crafted a valid block it will transmit the completed block to other nodes on the network and those nodes signal agreement by working on the next block in the chain. -The rules that nodes follow are built into the Monero software; When all nodes agree about the rules to follow this is called @consensus). Consensus is necessary for a cryptocurrency because it is how the blockchain is built; If nodes don't agree about which blocks are valid, for example people who have not updated their Monero software, those nodes that don't agree will no longer be able to participate in the Monero network. +The rules that nodes follow are built into the Monero software; When all nodes agree about the rules to follow this is called @consensus. Consensus is necessary for a cryptocurrency because it is how the blockchain is built; If nodes don't agree about which blocks are valid, for example people who have not updated their Monero software, those nodes that don't agree will no longer be able to participate in the Monero network. -The Monero Core Team plans for a @hardforks every 6 months, to occur in September and March of each year. At that time, if you are running a node it must be updated to the most recent version of the Monero software or it will no longer be able to participate in the network. +The Monero Core Team plans for a hardfork every 6 months, to occur in September and March of each year. At that time, if you are running a node it must be updated to the most recent version of the Monero software or it will no longer be able to participate in the network. --- diff --git a/resources/moneropedia/paymentid.md b/resources/moneropedia/paymentid.md index fba888fa..bac6dc73 100644 --- a/resources/moneropedia/paymentid.md +++ b/resources/moneropedia/paymentid.md @@ -11,15 +11,17 @@ Payment ID is an **arbitrary** and **optional** transaction attachment that cons The Payment ID is usually used to identify transactions to merchants and exchanges: Given the intrinsic privacy features built into Monero, where a single public address is usually used for incoming transactions, the Payment ID is especially useful to tie incoming payments with user accounts. -### Compact Payment ID's and Integrated Addresses +### Compact Payment IDs and Integrated Addresses -Since the 0.9 Hydrogen Helix version, the Payment IDs can be encrypted and embedded in a payment address. The payment ID's of this type should be 64-bits and are encrypted with a random one-time key known only to the sender and receiver. +Since the 0.9 Hydrogen Helix version, Payment IDs can be encrypted and embedded in a payment address. The Payment IDs of this type should be 64-bits and are encrypted with a random one-time key known only to the sender and receiver. ### Creating a Payment ID -It is recommended to use the official wallet's `integrated_address` command to automatically generate Integrated Addresses that contain Compact Payment ID's. If you want to use the command line, you can generate Payment ID's as follows: +It is recommended to use the official wallet's `integrated_address` command to automatically generate Integrated Addresses that contain Compact Payment IDs. If you want to use the command line, you can generate Payment IDs as follows: Creating a compact Payment ID for an Integrated Address: + ```# openssl rand -hex 8``` Creating an old-style Payment ID: + ```# openssl rand -hex 32``` diff --git a/resources/moneropedia/pedersen-commitment.md b/resources/moneropedia/pedersen-commitment.md index a7ff98ba..d44faf00 100644 --- a/resources/moneropedia/pedersen-commitment.md +++ b/resources/moneropedia/pedersen-commitment.md @@ -2,11 +2,13 @@ layout: moneropedia entry: "Pedersen Commitment" terms: ["commitments", "commitment", "pedersen"] -summary: "Pedersen commitments are cryptographic algorythms that allow a prover to commit to a certain value without revealing it or being able to change it." +summary: "Pedersen commitments are cryptographic algorythms that allow a prover to commit to a certain value without revealing it or being able to change it" --- ### The Basics +{{ page.summary | capitalize }}. + When you spend Monero, the value of the inputs that you are spending and the value of the outputs you are sending are encrypted and opaque to everyone except the recipient of each of those outputs. Pedersen commitments allow you to send Monero without revealing the value of the transactions. Pedersen commitments also make it possible for people to verify that transactions on the blockchain are valid and not creating Monero out of thin air. ### What It Means @@ -15,10 +17,8 @@ As long as the encrypted output amounts created, which include an output for the Pedersen commitments mean that the sums can be verified as being equal, but the Monero value of each of the sums and the Monero value of the inputs and outputs individually are undeterminable. Pedersen commitments also mean that even the ratio of one input to another, or one output to another is undeterminable. -Even though it's unclear which inputs are really being spent (the ring signature lists both the real inputs being spent and decoy inputs therefore you don't actually know which input Pedersen commitments you need to sum) that's okay, because the RingCT ring signature only has to prove is that for one combination of the inputs the outputs are equal to the sum of the inputs. For mathematical reasons, this is impossible to forge. +It is unclear which inputs are really being spent as the ring signature lists both the real inputs being spent and decoy inputs, therefore you don't actually know which input Pedersen commitments need to be summed up. That's okay, because the @RingCT ring signature only has to prove that for one combination of the inputs the outputs are equal to the sum of the inputs. For mathematical reasons, this is impossible to forge. ### In-depth Information See information in [Ring Confidential Transactions paper](https://eprint.iacr.org/2015/1098.pdf) by Shen Noether of the Monero Research Lab. - -{{ page.summary | capitalize }}. diff --git a/resources/moneropedia/ringCT.md b/resources/moneropedia/ringCT.md index 77b9bf32..a5f4c1aa 100644 --- a/resources/moneropedia/ringCT.md +++ b/resources/moneropedia/ringCT.md @@ -10,15 +10,6 @@ RingCT, short for Ring Confidential Transactions, is how transaction amounts are Ring CT was implemented in block #1220516 in January 2017. After September 2017, this feature became mandatory for all transactions on the network. -RingCT introduces an improved version of @ring-signatures called A Multi-layered Linkable Spontaneous Anonymous Group signature, which allows for hidden amounts, origins and destinations of transactions with reasonable efficiency and verifiable, trustless coin generation. +RingCT introduces an improved version of @ring-signatures called "A Multi-layered Linkable Spontaneous Anonymous Group signature", which allows for hidden amounts, origins and destinations of transactions with reasonable efficiency and verifiable, trustless coin generation. For more information, please read the creator Shen Noether's paper [here](https://eprint.iacr.org/2015/1098). - - -{{ page.summary | capitalize }}. - - - - - - diff --git a/resources/moneropedia/ringsignatures.md b/resources/moneropedia/ringsignatures.md index fee368c8..b10480df 100644 --- a/resources/moneropedia/ringsignatures.md +++ b/resources/moneropedia/ringsignatures.md @@ -13,6 +13,6 @@ For instance, a ring signature could be used to provide an anonymous signature f ### Application to Monero -A ring signature makes use of your @account keys and a number of public keys (also known as outputs) pulled from the @blockchain using a triangular distribution method. Over the course of time, past outputs could be used multiple times to form possible signer participants. In a "ring" of possible signers, all ring members are equal and valid. There is no way an outside observer can tell which of the possible signers in a signature group belongs to your @account. So, ring signatures ensure that transaction outputs are untraceable. Moreover, there are no fungibility issues with Monero given that every transaction output has plausible deniability (e.g. the network can not tell which outputs are spent or unspent). +A ring signature makes use of your @account keys and a number of public keys (also known as outputs) pulled from the @blockchain using a triangular distribution method. Over the course of time, past outputs could be used multiple times to form possible signer participants. In a "ring" of possible signers, all ring members are equal and valid. There is no way an outside observer can tell which of the possible signers in a signature group belongs to your @account. So, ring signatures ensure that transaction outputs are untraceable. Moreover, there are no @fungibility issues with Monero given that every transaction output has plausible deniability (e.g. the network can not tell which outputs are spent or unspent). To read how Monero gives you privacy by default (unlinkability), see @stealth-addresses. \ No newline at end of file diff --git a/resources/moneropedia/smartmining.md b/resources/moneropedia/smartmining.md index c4f7a6d2..9145421f 100644 --- a/resources/moneropedia/smartmining.md +++ b/resources/moneropedia/smartmining.md @@ -7,11 +7,9 @@ summary: "a process of having a throttled miner mine when it otherwise does not ### The Basics -Smart mining is the process of having a throttled miner mine when it otherwise does not cause drawbacks. +Smart mining is the process of having a throttled @miner mine when it otherwise does not cause drawbacks. Drawbacks include increases heat, slower machine, depleting battery, etc. The intent of smart mining is to increase network security by allowing as many people as possible to let the smart miner on all the time. For this to work, the miner must prove unobtrusive, or it will be turned off, depriving the Monero network from a little bit of security. As such, it is likely that a smart miner will mine slower than a normal miner on the same hardware. Smart mining is available in the official CLI and GUI wallet, which are available in the [downloads page](https://getmonero.org/downloads/). It is hoped that the relative slowness of a smart miner (especially on low-power machines) will be offset by the large amount of people running a miner for a possible "lottery win", and thus increase the Monero network security by a non trivial amount. The increased hash rate from many different sources helps keep the Monero network decentralized. - -{{ page.summary | capitalize }}. diff --git a/resources/moneropedia/tail-emission.md b/resources/moneropedia/tail-emission.md index 019e6fe1..b5a9c6be 100644 --- a/resources/moneropedia/tail-emission.md +++ b/resources/moneropedia/tail-emission.md @@ -11,6 +11,6 @@ Monero block rewards will never drop to zero. Block rewards will gradually drop ### Why -Miners need an incentive to mine. Because of the dynamic blocksize, competition between miners will cause fees to decrease. If mining is not profitable due to a high cost and low reward, miners lose their incentive and will stop mining, reducing the security of the network. +Miners need an incentive to mine. Because of the dynamic blocksize, competition between @miners will cause fees to decrease. If mining is not profitable due to a high cost and low reward, miners lose their incentive and will stop mining, reducing the security of the network. Tail emission ensures that a dynamic block size and fee market can develop. diff --git a/resources/moneropedia/transaction.md b/resources/moneropedia/transaction.md index 0064cb50..5b5d0781 100644 --- a/resources/moneropedia/transaction.md +++ b/resources/moneropedia/transaction.md @@ -9,7 +9,9 @@ summary: "a cryptographically signed container that details the transfer of Mone {{ page.summary | capitalize }}. -The parameters of a transaction contain one or more recipient addresses with corresponding amounts of funds and a `mixin_count` parameter that specifies the number of foreign outputs bound to the transaction. The more outputs that are used, a higher degree of obfuscation is possible, but that comes with a cost. Since a transaction gets larger with more outputs, the transaction fee would be higher. It is possible to form a transaction offline, which is a huge benefit for privacy. +The parameters of a transaction contain one or more recipient addresses with corresponding amounts of funds and a `mixin_count` parameter that specifies the number of foreign outputs bound to the transaction (see @ring-size). The more outputs that are used, a higher degree of obfuscation is possible, but that comes with a cost. Since a transaction gets larger with more outputs, the transaction fee will be higher. + +It is possible to form a transaction offline, which is a huge benefit for privacy. A transaction can be uniquely identified with the use of an optional Transaction ID, which is usually represented by a 32-byte string (64 hexadecimal characters). diff --git a/resources/moneropedia/viewkey.md b/resources/moneropedia/viewkey.md index 719a96b9..0ff95d73 100644 --- a/resources/moneropedia/viewkey.md +++ b/resources/moneropedia/viewkey.md @@ -7,10 +7,8 @@ summary: "one of two sets of private and public cryptographic keys that each acc ### The Basics -Monero features an opaque blockchain (with an explicit allowance system called the @view-key), in sharp contrast with transparent blockchains used by any other cryptocurrency not based on @CryptoNote. Thus, Monero is said to be "private, optionally transparent". - -Every Monero address has a private viewkey which can be shared. By sharing a viewkey a person is allowing access to view every incoming transaction for that address. However, outgoing transactions cannot be reliably viewed as of June 2017. Therefore the balance of a Monero address as shown via a viewkey should not be relied upon. - +{{ page.summary | capitalize }}. +Monero features an opaque blockchain (with an explicit allowance system called the @view-key), in sharp contrast with transparent blockchains used by any other cryptocurrency not based on CryptoNote. Thus, Monero is said to be "private, optionally transparent". -{{ page.summary | capitalize }}. +Every Monero address has a private viewkey which can be shared. By sharing a viewkey a person is allowing access to view every incoming transaction for that address. However, outgoing transactions cannot be reliably viewed as of June 2017. Therefore the balance of a Monero address as shown via a viewkey should not be relied upon. -- GitLab From 6d20a64017da4951ca47035d9b21b1cfe820103e Mon Sep 17 00:00:00 2001 From: Leon Klingele Date: Fri, 10 Nov 2017 18:05:36 +0100 Subject: [PATCH 22/43] Updates based on feedback --- resources/moneropedia/address.md | 2 +- resources/moneropedia/blockchain.md | 2 +- resources/moneropedia/mnemonicseed.md | 2 +- resources/moneropedia/node.md | 2 +- resources/moneropedia/pedersen-commitment.md | 2 +- resources/moneropedia/transaction.md | 2 +- resources/moneropedia/viewkey.md | 2 +- 7 files changed, 7 insertions(+), 7 deletions(-) diff --git a/resources/moneropedia/address.md b/resources/moneropedia/address.md index 54492c65..0e62f86d 100644 --- a/resources/moneropedia/address.md +++ b/resources/moneropedia/address.md @@ -9,7 +9,7 @@ summary: "either an alias, such as donate.getmonero.org, or a set of 95 characte When you send Monero to someone you only need one piece of information, and that is their Monero address. A *raw* Monero address is a set of 95 characters starting with a '4'. The Monero donation address, for instance, is 44AFFq5kSiGBoZ4NMDwYtN18obc8AemS33DBLWs3H7otXft3XjrpDtQGv7SqSsaBYBb98uNbr2VBBEt7f2wfn3RVGQBEP3A. -Because those addresses are long and complex you will often encounter an @OpenAlias address instead. For example, Monero donations can be sent to donate@getmonero.org or donate.getmonero.org. +Because those addresses are long and complex, you will often encounter an @OpenAlias address instead. For example, Monero donations can be sent to donate@getmonero.org or donate.getmonero.org. If you would like to get an @OpenAlias address of your own then there is some information on the [OpenAlias page](/resources/openalias). diff --git a/resources/moneropedia/blockchain.md b/resources/moneropedia/blockchain.md index 5b4d8fd9..3a2a9a21 100644 --- a/resources/moneropedia/blockchain.md +++ b/resources/moneropedia/blockchain.md @@ -7,7 +7,7 @@ summary: "a distributed ledger of all transactions both past and present, withou --- ### The Basics -A @blockchain is a distributed database that continuously grows with a record of all of the transactions that have occurred with a given cryptocurrency. This database is often referred to as a ledger because the data contains a large list of transactions that have taken place. In Monero, these transactions are packaged together into 'blocks' every 2 minutes (on average) and all miners and nodes on the network have copies of these blocks. +A @blockchain is a distributed database that continuously grows with a record of all of the transactions that have occurred with a given cryptocurrency. This database is often referred to as a ledger because the data contains a large list of transactions that have taken place. In Monero, these transactions are packaged together into 'blocks' every 2 minutes (on average), and all miners and nodes on the network have copies of these blocks. ### Monero's @Blockchain Unlike Bitcoin and other cryptocurrencies, transactions in the Monero @blockchain do not reveal where funds came from or went to, providing anonymity and making the currency completely [fungible](fungibility). Additionally, the amounts of all transactions are hidden by @RingCT, a feature of Monero. For auditing or other transparency purposes a user can share a @view-key to prove they control certain amounts of Moneroj. diff --git a/resources/moneropedia/mnemonicseed.md b/resources/moneropedia/mnemonicseed.md index 57ab9aaa..608f8d8b 100644 --- a/resources/moneropedia/mnemonicseed.md +++ b/resources/moneropedia/mnemonicseed.md @@ -2,7 +2,7 @@ layout: moneropedia entry: "Mnemonic Seed" terms: ["mnemonic-seed", "mnemonic"] -summary: "a 13 or 25 word phrase used to back up a Monero account, available in a number of languages" +summary: "a 13 or 25 word phrase used to backup a Monero account, available in a number of languages" --- ### The Basics diff --git a/resources/moneropedia/node.md b/resources/moneropedia/node.md index 46a0bcbe..9b5a6816 100644 --- a/resources/moneropedia/node.md +++ b/resources/moneropedia/node.md @@ -13,7 +13,7 @@ summary: "a device on the Internet running the Monero software, with a full copy Nodes participate in the Monero network and secure @transactions by enforcing the rules of the network. Nodes download the entire @blockchain to know what transactions have taken place. Nodes assist the network by relaying transactions to other nodes on the network. Nodes may also choose to contribute to the Monero network by participating in crafting @blocks (this is called @mining). -Mining is the process by which nodes create a block from the previously accepted block, transactions that are waiting to be processed in the Transaction Pool, and the @coinbase-transaction. When a node believes it has crafted a valid block it will transmit the completed block to other nodes on the network and those nodes signal agreement by working on the next block in the chain. +Mining is the process by which nodes create a block from the previously accepted block, transactions that are waiting to be processed in the transaction pool, and the @coinbase-transaction. When a node believes it has crafted a valid block it will transmit the completed block to other nodes on the network and those nodes signal agreement by working on the next block in the chain. The rules that nodes follow are built into the Monero software; When all nodes agree about the rules to follow this is called @consensus. Consensus is necessary for a cryptocurrency because it is how the blockchain is built; If nodes don't agree about which blocks are valid, for example people who have not updated their Monero software, those nodes that don't agree will no longer be able to participate in the Monero network. diff --git a/resources/moneropedia/pedersen-commitment.md b/resources/moneropedia/pedersen-commitment.md index d44faf00..e39a1215 100644 --- a/resources/moneropedia/pedersen-commitment.md +++ b/resources/moneropedia/pedersen-commitment.md @@ -17,7 +17,7 @@ As long as the encrypted output amounts created, which include an output for the Pedersen commitments mean that the sums can be verified as being equal, but the Monero value of each of the sums and the Monero value of the inputs and outputs individually are undeterminable. Pedersen commitments also mean that even the ratio of one input to another, or one output to another is undeterminable. -It is unclear which inputs are really being spent as the ring signature lists both the real inputs being spent and decoy inputs, therefore you don't actually know which input Pedersen commitments need to be summed up. That's okay, because the @RingCT ring signature only has to prove that for one combination of the inputs the outputs are equal to the sum of the inputs. For mathematical reasons, this is impossible to forge. +It is unclear which inputs are really being spent as the ring signature lists both the real inputs being spent and decoy inputs, therefore you don't actually know which input Pedersen commitments need to be summed. That's okay, because the @RingCT ring signature only has to prove that for one combination of the inputs the outputs are equal to the sum of the inputs. For mathematical reasons, this is impossible to forge. ### In-depth Information diff --git a/resources/moneropedia/transaction.md b/resources/moneropedia/transaction.md index 5b5d0781..26642835 100644 --- a/resources/moneropedia/transaction.md +++ b/resources/moneropedia/transaction.md @@ -11,7 +11,7 @@ summary: "a cryptographically signed container that details the transfer of Mone The parameters of a transaction contain one or more recipient addresses with corresponding amounts of funds and a `mixin_count` parameter that specifies the number of foreign outputs bound to the transaction (see @ring-size). The more outputs that are used, a higher degree of obfuscation is possible, but that comes with a cost. Since a transaction gets larger with more outputs, the transaction fee will be higher. -It is possible to form a transaction offline, which is a huge benefit for privacy. +It is possible to form a transaction offline, offline, which offers additional privacy benefits. A transaction can be uniquely identified with the use of an optional Transaction ID, which is usually represented by a 32-byte string (64 hexadecimal characters). diff --git a/resources/moneropedia/viewkey.md b/resources/moneropedia/viewkey.md index 0ff95d73..ee2c1536 100644 --- a/resources/moneropedia/viewkey.md +++ b/resources/moneropedia/viewkey.md @@ -11,4 +11,4 @@ summary: "one of two sets of private and public cryptographic keys that each acc Monero features an opaque blockchain (with an explicit allowance system called the @view-key), in sharp contrast with transparent blockchains used by any other cryptocurrency not based on CryptoNote. Thus, Monero is said to be "private, optionally transparent". -Every Monero address has a private viewkey which can be shared. By sharing a viewkey a person is allowing access to view every incoming transaction for that address. However, outgoing transactions cannot be reliably viewed as of June 2017. Therefore the balance of a Monero address as shown via a viewkey should not be relied upon. +Every Monero address has a private viewkey which can be shared. By sharing a viewkey, a person is allowing access to view every incoming transaction for that address. However, outgoing transactions cannot be reliably viewed as of June 2017. Therefore, the balance of a Monero address as shown via a viewkey should not be relied upon. -- GitLab From 5a861489ec76fb8bb6de709166549a310e0affb5 Mon Sep 17 00:00:00 2001 From: Leon Klingele Date: Fri, 10 Nov 2017 18:08:03 +0100 Subject: [PATCH 23/43] Uppercase 'Internet' --- resources/moneropedia/clearnet.md | 4 ++-- resources/moneropedia/garlic-routing.md | 2 +- resources/moneropedia/mnemonicseed.md | 2 +- resources/moneropedia/subscription.md | 2 +- resources/moneropedia/wallet.md | 2 +- 5 files changed, 6 insertions(+), 6 deletions(-) diff --git a/resources/moneropedia/clearnet.md b/resources/moneropedia/clearnet.md index 9200e69a..1ac9ec19 100644 --- a/resources/moneropedia/clearnet.md +++ b/resources/moneropedia/clearnet.md @@ -3,12 +3,12 @@ layout: moneropedia entry: "Clearnet" tags: ["kovri"] terms: ["Clearnet"] -summary: "The internet in which anonymous overlay networks are built upon" +summary: "The Internet in which anonymous overlay networks are built upon" --- ### The Basics -When you use the internet for things like news, email, social media, and even Monero, you are most likely using a clearnet connection. This means that *all* of your connections can be tracked, traced, and monitored by: +When you use the Internet for things like news, email, social media, and even Monero, you are most likely using a clearnet connection. This means that *all* of your connections can be tracked, traced, and monitored by: - your [ISP](https://en.wikipedia.org/wiki/ISP) - the website/service/person you're communicating with diff --git a/resources/moneropedia/garlic-routing.md b/resources/moneropedia/garlic-routing.md index 55cd2122..a2afbacb 100644 --- a/resources/moneropedia/garlic-routing.md +++ b/resources/moneropedia/garlic-routing.md @@ -8,7 +8,7 @@ summary: "Routing technology as implemented in Kovri" ### The Basics -The term *@garlic-routing* has a diverse history of varying interpretations. As it currently stands, Monero defines *@garlic-routing* as the method in which @Kovri and @I2P create a @message-based anonymous overlay network of internet peers. +The term *@garlic-routing* has a diverse history of varying interpretations. As it currently stands, Monero defines *@garlic-routing* as the method in which @Kovri and @I2P create a @message-based anonymous overlay network of Internet peers. The @Garlic-Encryption of @Garlic-Routing is similar to the @Layered-Encryption of [Onion Routing](https://en.wikipedia.org/wiki/Onion_routing) and effectively conceals the IP address of the sender and secures information sent from the sender to its @destination (and vice-versa). diff --git a/resources/moneropedia/mnemonicseed.md b/resources/moneropedia/mnemonicseed.md index 608f8d8b..4a1d8098 100644 --- a/resources/moneropedia/mnemonicseed.md +++ b/resources/moneropedia/mnemonicseed.md @@ -15,6 +15,6 @@ In the official wallet, the mnemonic seed comprises 25 words with the last word By storing the 25 word mnemonic key in a secure location, you have a backup of your private keys and hence all of your Moneroj. Sharing this 25 word key is the equivalent of allowing another person complete access to your funds. -It's not a good idea to store more than you want to lose in a "hot wallet" aka a wallet which is currently or has ever been connected to the internet or loaded onto any device that has or may in the future be connected to the internet or any untrusted source! +It's not a good idea to store more than you want to lose in a "hot wallet" aka a wallet which is currently or has ever been connected to the Internet or loaded onto any device that has or may in the future be connected to the Internet or any untrusted source! By creating a cold, or @paper-wallet you can safely store Moneroj. diff --git a/resources/moneropedia/subscription.md b/resources/moneropedia/subscription.md index b7411df5..77e81ff5 100644 --- a/resources/moneropedia/subscription.md +++ b/resources/moneropedia/subscription.md @@ -12,7 +12,7 @@ A subscription is a file which contains a list of `.i2p` hosts paired with their ### In-depth information -Similar to how a [hosts file](https://en.wikipedia.org/wiki/etc/hosts) can map an internet hostname to a specified address, a subscription matches a `.i2p` address to @base64-address by using the following format (no spaces allowed): `host=address` +Similar to how a [hosts file](https://en.wikipedia.org/wiki/etc/hosts) can map an Internet hostname to a specified address, a subscription matches a `.i2p` address to @base64-address by using the following format (no spaces allowed): `host=address` More specifically, a subscription pairs a @locally-unique-host to @base64-address. diff --git a/resources/moneropedia/wallet.md b/resources/moneropedia/wallet.md index 759b018d..1641a2de 100644 --- a/resources/moneropedia/wallet.md +++ b/resources/moneropedia/wallet.md @@ -11,7 +11,7 @@ A Monero account, or wallet, stores the information necessary to send and receiv The term "hot wallet" describes a Monero @account which is connected to the Internet. You can send funds easily but security is much lower than a cold wallet. Never store large amounts of cryptocurrency in a hot wallet! -A cold wallet is generated on a trusted device or computer via an @airgap. If the device is to be reused, the data storage should be securely overwritten. As soon as a cold wallet is connected to the internet or its mnemonic phrase or @spend-key is entered on an internet-connected device, it's no longer "cold" and should be considered "hot". +A cold wallet is generated on a trusted device or computer via an @airgap. If the device is to be reused, the data storage should be securely overwritten. As soon as a cold wallet is connected to the Internet or its mnemonic phrase or @spend-key is entered on an Internet-connected device, it's no longer "cold" and should be considered "hot". A Monero @paper-wallet can be generated by downloading the source code of https://moneroaddress.org/. Verify the signature of the code on a trusted airgapped device. Create the wallet and print or store it on the media of your choice. -- GitLab From dcfb156d116956cfd1c5a592720ab7312cfdcd1a Mon Sep 17 00:00:00 2001 From: Leon Klingele Date: Fri, 10 Nov 2017 18:10:07 +0100 Subject: [PATCH 24/43] Rename file: 'miners' -> 'mining' --- resources/moneropedia/{miners.md => mining.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename resources/moneropedia/{miners.md => mining.md} (100%) diff --git a/resources/moneropedia/miners.md b/resources/moneropedia/mining.md similarity index 100% rename from resources/moneropedia/miners.md rename to resources/moneropedia/mining.md -- GitLab From 38fa69c30db73f62333980937c7cb3afcf66f131 Mon Sep 17 00:00:00 2001 From: Leon Klingele Date: Fri, 10 Nov 2017 20:22:41 +0100 Subject: [PATCH 25/43] More feedback --- resources/moneropedia/mining.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/resources/moneropedia/mining.md b/resources/moneropedia/mining.md index 9638dd48..5b73ba54 100644 --- a/resources/moneropedia/mining.md +++ b/resources/moneropedia/mining.md @@ -14,5 +14,3 @@ Mining is the distributed process of confirming transactions on the public ledge Monero is powered strictly by Proof of Work. It employs a mining algorithm that has the potential to be efficiently tasked to billions of existing devices (any modern x86 CPU and many GPUs). Monero uses the CryptoNight Proof of Work (PoW) algorithm, which is designed for use in ordinary CPUs and GPUs. The smart mining feature allows transparent CPU mining on the user's computer, far from the de facto centralization of mining farms and pool mining, pursuing Satoshi Nakamoto's original vision of a true P2P currency. - -As of June 2017, botnets made of hacked computers account for a not-insignificant portion of the miners on the Monero network. This is due to the profitability of mining on CPUs via the CryptoNight algorithm. -- GitLab From bcdf2616ac1648c07c3c179f701a8ff246df5458 Mon Sep 17 00:00:00 2001 From: Matt Smith Date: Sat, 18 Nov 2017 20:36:49 +0000 Subject: [PATCH 26/43] Add secpoint.com to merchants.yml Fix #481 --- _data/merchants.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/_data/merchants.yml b/_data/merchants.yml index b16eb779..7ce3f701 100644 --- a/_data/merchants.yml +++ b/_data/merchants.yml @@ -209,6 +209,8 @@ url: http://investmentart.org/ - name: Mushroom cultures, mushroom growing supplies, seeds url: https://www.vesp.co/Fungible + - name: SecPoint IT Security Products + url: https://shop.secpoint.com/shop/frontpage.html - name: SilverRound.com - Gold and Silver Dealer url: https://silverround.com/ - name: Synntech Gaming -- GitLab From c798168b52bd62c4a9f54eab233f4fca2a363977 Mon Sep 17 00:00:00 2001 From: dEBRUYNE-1 Date: Wed, 6 Dec 2017 18:41:08 +0100 Subject: [PATCH 27/43] Monero Compatible Bulletproofs --- ...17-12-07-Monero-Compatible-Bulletproofs.md | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 _posts/2017-12-07-Monero-Compatible-Bulletproofs.md diff --git a/_posts/2017-12-07-Monero-Compatible-Bulletproofs.md b/_posts/2017-12-07-Monero-Compatible-Bulletproofs.md new file mode 100644 index 00000000..799d96b6 --- /dev/null +++ b/_posts/2017-12-07-Monero-Compatible-Bulletproofs.md @@ -0,0 +1,22 @@ +--- +layout: post +title: Monero Compatible Bulletproofs +tags: [crypto, mrl, dev] +author: Sarang Noether +--- + +Here is a quick update on Bulletproofs and their role in Monero. Bottom line: they're awesome, they work, the fees are lower, and they're moving into testnet. + +Monero's confidential transactions hide the amounts involved. To ensure that inputs and outputs balance properly in a way that can be verified by anyone, we use commitments that have useful algebraic properties. However, this isn't enough. We also need to ensure that each amount is a positive value that won't risk an overflow, and this is where range proofs come in. A range proof allows anyone to verify that a commitment represents an amount within a specified range, without revealing anything else about its value. Our current range proofs scale linearly in size with the number of outputs and the number of bits in the range (currently 64 bits), meaning they make up the bulk of a transaction's size. Further, this means that a transaction with multiple outputs needs multiple separate range proofs. Not great. + +Thanks to a fantastic new paper by Bünz, Bootle, and others (freely available at https://web.stanford.edu/~buenz/pubs/bulletproofs.pdf), there is a more efficient way to handle range proofs. The size of a bulletproof increases only logarithmically with both the size of the range and the number of outputs. This gives us two related types of bulletproofs: single-output and multiple-output. A transaction with multiple outputs can either include several single-output proofs or one multiple-output proof (which is smaller than the separate proofs). + +Let's look at the typical two-output transaction, where I send you some XMR and direct the change back to myself. With our current range proofs, the transaction is around 13.2 kB in size. If I used single-output bulletproofs, the transaction reduces in size to only around 2.5 kB! This is, approximately, an 80% reduction in transaction size, which then translates to an 80% reduction in fees as well. The space savings are even better with multiple-output proofs. This represents a significant decrease in transaction sizes. Further, our initial testing shows that the time to verify a bulletproof is lower than for the existing range proofs, meaning speedier blockchain validation. + +We have working Java test code for bulletproofs available now (https://github.com/b-g-goodell/research-lab/tree/master/source-code/StringCT-java/src/how/monero/hodl/bulletproof) for both single and multiple outputs. The code for single-output bulletproofs has been ported to C++ by moneromooo (https://github.com/monero-project/monero/pull/2883) and will be available on testnet shortly. The code is being reviewed and tested thoroughly. + +Multiple outputs raise some issues that need further thought. Because bulletproof verification is linear in the number of outputs (while the size scales logarithmically), an attacker could pack a transaction with many outputs; this tiny transaction would require low fees but would be computationally expensive to verify, opening the door to denial-of-service attacks. Because of this, we will need to adjust the fee structure away from transaction size and take into account the verification scaling. This doesn't mean fees go up, though! It just means that the fees will scale properly and in a safe way. + +To avoid any problems, we're deploying bulletproofs in two stages. You'll first see only the single-output proofs. A two-output transaction will initially use two separate proofs, which still offers massive savings from what we have now. You'll see lower fees and faster verification times. We'll continue discussions about fee structure while we test multiple-output proofs, and later deploy them as a second stage. We want to encourage miners to use multiple-output proofs while being safe about fee scaling. + +Overall, bulletproofs represent a huge advancement in Monero transactions. We get massive space savings, better verification times, and lower fees. If you're a fan of testnet, keep an eye out for bulletproofs! \ No newline at end of file -- GitLab From 60be8c7810efb01ca34e71de8732a117fb4f1dba Mon Sep 17 00:00:00 2001 From: tyrionmcmaster <31110358+tyrionmcmaster@users.noreply.github.com> Date: Tue, 21 Nov 2017 13:13:57 -0500 Subject: [PATCH 28/43] Slight modifications to wording on home page --- index.html | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/index.html b/index.html index 4ee8af9d..25b36404 100644 --- a/index.html +++ b/index.html @@ -37,7 +37,7 @@ Title: Home
-

Monero is secure.

+

Monero is secure

Monero is a decentralized cryptocurrency, meaning it is secure digital cash operated by a network of users. Transactions are confirmed by distributed consensus, and then immutably recorded on the blockchain. Third-parties do not need to be trusted to keep your Monero safe.

@@ -49,14 +49,14 @@ Title: Home No surveillance
-

Monero is private.

-

Monero uses ring signatures and ring confidential transactions to obfuscate the amounts, origins, and destinations of all transactions. Monero provides all the benefits of a decentralized cryptocurrency, without any of the typical privacy concessions.

+

Monero is private

+

Monero uses ring signatures, ring confidential transactions, and stealth addresses to obfuscate the origins, amounts and destinations of all transactions. Monero provides all the benefits of a decentralized cryptocurrency, without any of the typical privacy concessions.

-

Monero is untraceable.

+

Monero is untraceable

Sending and receiving addresses as well as transacted amounts are obfuscated by default. Transactions on the Monero blockchain cannot be linked to a particular user or real-world identity.

@@ -68,8 +68,8 @@ Title: Home Monero gold
-

Monero is fungible.

-

Monero is fungible because it is private by default. In its current state, it is extremely unlikely that Monero will ever be blacklisted by exchanges or vendors due to its association in previous transactions.

+

Monero is fungible

+

Monero is fungible because it is private by default. Units of Monero cannot be blacklisted by vendors or exchanges due to their association in previous transactions.

-- GitLab From aaf95c7596f177862debec05295c4561115ae387 Mon Sep 17 00:00:00 2001 From: tyrionmcmaster <31110358+tyrionmcmaster@users.noreply.github.com> Date: Tue, 21 Nov 2017 18:22:44 -0500 Subject: [PATCH 29/43] Update index.html --- index.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/index.html b/index.html index 25b36404..fa5022f2 100644 --- a/index.html +++ b/index.html @@ -20,7 +20,7 @@ Title: Home

Monero

Private Digital Currency

-

Monero is a secure, private, and untraceable cryptocurrency. It is open-source and accessible to all. With Monero, you are your own bank. Only you control and are responsible for your funds. Your accounts and transactions are kept private from prying eyes.

+

Monero is a secure, private and untraceable cryptocurrency. It is open-source and accessible to all. With Monero, you are your own bank. Only you control and are responsible for your funds. Your accounts and transactions are kept private from prying eyes.

Get Started

@@ -38,7 +38,7 @@ Title: Home

Monero is secure

-

Monero is a decentralized cryptocurrency, meaning it is secure digital cash operated by a network of users. Transactions are confirmed by distributed consensus, and then immutably recorded on the blockchain. Third-parties do not need to be trusted to keep your Monero safe.

+

Monero is a decentralized cryptocurrency, meaning it is secure digital cash operated by a network of users. Transactions are confirmed by distributed consensus and then immutably recorded on the blockchain. Third-parties do not need to be trusted to keep your Monero safe.

Secure safe @@ -50,7 +50,7 @@ Title: Home

Monero is private

-

Monero uses ring signatures, ring confidential transactions, and stealth addresses to obfuscate the origins, amounts and destinations of all transactions. Monero provides all the benefits of a decentralized cryptocurrency, without any of the typical privacy concessions.

+

Monero uses ring signatures, ring confidential transactions and stealth addresses to obfuscate the origins, amounts and destinations of all transactions. Monero provides all the benefits of a decentralized cryptocurrency, without any of the typical privacy concessions.

@@ -69,7 +69,7 @@ Title: Home

Monero is fungible

-

Monero is fungible because it is private by default. Units of Monero cannot be blacklisted by vendors or exchanges due to their association in previous transactions.

+

Monero is fungible because it is private by default. Units of Monero cannot be blacklisted by vendors or exchanges due to their association in previous transactions.

-- GitLab From b310c79c2760238a8930d6cbd5a106ea503a8dac Mon Sep 17 00:00:00 2001 From: tyrionmcmaster <31110358+tyrionmcmaster@users.noreply.github.com> Date: Wed, 22 Nov 2017 09:46:46 -0500 Subject: [PATCH 30/43] Update index.html --- index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.html b/index.html index fa5022f2..647b1968 100644 --- a/index.html +++ b/index.html @@ -69,7 +69,7 @@ Title: Home

Monero is fungible

-

Monero is fungible because it is private by default. Units of Monero cannot be blacklisted by vendors or exchanges due to their association in previous transactions.

+

Monero is fungible because it is private by default. Units of Monero cannot be blacklisted by vendors or exchanges due to their association in previous transactions.

-- GitLab From 1f10e4ccae135ff55c7c69efaaed8ce41456f86a Mon Sep 17 00:00:00 2001 From: tyrionmcmaster <31110358+tyrionmcmaster@users.noreply.github.com> Date: Mon, 4 Dec 2017 22:31:17 -0500 Subject: [PATCH 31/43] Update index.html --- index.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/index.html b/index.html index 647b1968..d13e7272 100644 --- a/index.html +++ b/index.html @@ -20,7 +20,7 @@ Title: Home

Monero

Private Digital Currency

-

Monero is a secure, private and untraceable cryptocurrency. It is open-source and accessible to all. With Monero, you are your own bank. Only you control and are responsible for your funds. Your accounts and transactions are kept private from prying eyes.

+

Monero is a secure, private, and untraceable cryptocurrency. It is open-source and accessible to all. With Monero, you are your own bank. Only you control and are responsible for your funds. Your accounts and transactions are kept private from prying eyes.

Get Started

@@ -50,7 +50,7 @@ Title: Home

Monero is private

-

Monero uses ring signatures, ring confidential transactions and stealth addresses to obfuscate the origins, amounts and destinations of all transactions. Monero provides all the benefits of a decentralized cryptocurrency, without any of the typical privacy concessions.

+

Monero uses ring signatures, ring confidential transactions, and stealth addresses to obfuscate the origins, amounts, and destinations of all transactions. Monero provides all the benefits of a decentralized cryptocurrency, without any of the typical privacy concessions.

-- GitLab From a57c2eff48b1d39ad06c69a9634183aef02f780f Mon Sep 17 00:00:00 2001 From: cryptoshrimpi Date: Mon, 6 Nov 2017 10:35:36 +0000 Subject: [PATCH 32/43] Add doc for sendrawtransaction in daemon-rpc guide Describe return fields of RPC call 'sendrawtransaction' closes #224 --- resources/developer-guides/daemon-rpc.md | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/resources/developer-guides/daemon-rpc.md b/resources/developer-guides/daemon-rpc.md index 31d16a6d..5cc2aec5 100644 --- a/resources/developer-guides/daemon-rpc.md +++ b/resources/developer-guides/daemon-rpc.md @@ -731,7 +731,18 @@ Inputs: Outputs: -* *status* - string; General RPC error code. "OK" means everything looks good. +* *status* - string; General RPC error code. "OK" means everything looks good. Any other value means that something went wrong. +* *double_spend* - boolean; Transaction is a double spend (`true`) or not (`false`). +* *fee_too_low* - boolean; Fee is too low (`true`) or OK (`false`). +* *invalid_input* - boolean; Input is invalid (`true`) or valid (`false`). +* *invalid_output* - boolean; Output is invalid (`true`) or valid (`false`). +* *low_mixin* - boolean; Mixin count is too low (`true`) or OK (`false`). +* *not_rct* - boolean; Transaction is not a ring transaction (`true`) or a ring transaction (`false`). +* *not_relayed* - boolean; Transaction was not relayed (`true`) or relayed (`false`). +* *overspend* - boolean; Transaction uses more money than available (`true`) or not (`false`). +* *reason* - string; Additional information. Currently empty or "Not relayed" if transaction was accepted but not relayed. +* *too_big* - boolean; Transaction size is too big (`true`) or OK (`false`). + Example (No return information included here.): -- GitLab From d42aaf4bb7fe3e590710e6558799410f17efe4fe Mon Sep 17 00:00:00 2001 From: Riccardo Spagni Date: Thu, 7 Dec 2017 21:16:46 +0200 Subject: [PATCH 33/43] fix links in bulletproofs post --- _posts/2017-12-07-Monero-Compatible-Bulletproofs.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_posts/2017-12-07-Monero-Compatible-Bulletproofs.md b/_posts/2017-12-07-Monero-Compatible-Bulletproofs.md index 799d96b6..e78f579d 100644 --- a/_posts/2017-12-07-Monero-Compatible-Bulletproofs.md +++ b/_posts/2017-12-07-Monero-Compatible-Bulletproofs.md @@ -9,11 +9,11 @@ Here is a quick update on Bulletproofs and their role in Monero. Bottom line: th Monero's confidential transactions hide the amounts involved. To ensure that inputs and outputs balance properly in a way that can be verified by anyone, we use commitments that have useful algebraic properties. However, this isn't enough. We also need to ensure that each amount is a positive value that won't risk an overflow, and this is where range proofs come in. A range proof allows anyone to verify that a commitment represents an amount within a specified range, without revealing anything else about its value. Our current range proofs scale linearly in size with the number of outputs and the number of bits in the range (currently 64 bits), meaning they make up the bulk of a transaction's size. Further, this means that a transaction with multiple outputs needs multiple separate range proofs. Not great. -Thanks to a fantastic new paper by Bünz, Bootle, and others (freely available at https://web.stanford.edu/~buenz/pubs/bulletproofs.pdf), there is a more efficient way to handle range proofs. The size of a bulletproof increases only logarithmically with both the size of the range and the number of outputs. This gives us two related types of bulletproofs: single-output and multiple-output. A transaction with multiple outputs can either include several single-output proofs or one multiple-output proof (which is smaller than the separate proofs). +Thanks to a fantastic new paper by Bünz, Bootle, and others ([freely available here](https://web.stanford.edu/~buenz/pubs/bulletproofs.pdf)), there is a more efficient way to handle range proofs. The size of a bulletproof increases only logarithmically with both the size of the range and the number of outputs. This gives us two related types of bulletproofs: single-output and multiple-output. A transaction with multiple outputs can either include several single-output proofs or one multiple-output proof (which is smaller than the separate proofs). Let's look at the typical two-output transaction, where I send you some XMR and direct the change back to myself. With our current range proofs, the transaction is around 13.2 kB in size. If I used single-output bulletproofs, the transaction reduces in size to only around 2.5 kB! This is, approximately, an 80% reduction in transaction size, which then translates to an 80% reduction in fees as well. The space savings are even better with multiple-output proofs. This represents a significant decrease in transaction sizes. Further, our initial testing shows that the time to verify a bulletproof is lower than for the existing range proofs, meaning speedier blockchain validation. -We have working Java test code for bulletproofs available now (https://github.com/b-g-goodell/research-lab/tree/master/source-code/StringCT-java/src/how/monero/hodl/bulletproof) for both single and multiple outputs. The code for single-output bulletproofs has been ported to C++ by moneromooo (https://github.com/monero-project/monero/pull/2883) and will be available on testnet shortly. The code is being reviewed and tested thoroughly. +We have working Java test code for bulletproofs available now ([at this GitHub repo](https://github.com/b-g-goodell/research-lab/tree/master/source-code/StringCT-java/src/how/monero/hodl/bulletproof)) for both single and multiple outputs. The code for single-output bulletproofs has been ported to C++ by moneromooo ([found at this pull request](https://github.com/monero-project/monero/pull/2883)) and will be available on testnet shortly. The code is being reviewed and tested thoroughly. Multiple outputs raise some issues that need further thought. Because bulletproof verification is linear in the number of outputs (while the size scales logarithmically), an attacker could pack a transaction with many outputs; this tiny transaction would require low fees but would be computationally expensive to verify, opening the door to denial-of-service attacks. Because of this, we will need to adjust the fee structure away from transaction size and take into account the verification scaling. This doesn't mean fees go up, though! It just means that the fees will scale properly and in a safe way. -- GitLab From 6a1dee78bc09efb62a87405f03bcd16bd0cddb6f Mon Sep 17 00:00:00 2001 From: erciccione Date: Thu, 7 Dec 2017 14:37:16 +0100 Subject: [PATCH 34/43] add merchant ink-rebels --- _data/merchants.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/_data/merchants.yml b/_data/merchants.yml index 7ce3f701..ac98f13c 100644 --- a/_data/merchants.yml +++ b/_data/merchants.yml @@ -152,6 +152,8 @@ url: http://www.guitartheoryrevolution.info/blog/guitar-theory-revolution-store/ - name: Infield Loan Services - Atlanta, Construction Consulting, Contract review, Feasibility, Funds Escrow url: mailto:info@loandraw.com + - name: Ink Rebels + url: https://ink-rebels.com - name: K9 Satisfaction - Premium dog training url: http://www.k9satisfaction.com/ - name: KoDDoS.net - DDoS Protection -- GitLab From 87943bea5a4401772cad0bb0403649ce9f04b6de Mon Sep 17 00:00:00 2001 From: erciccione Date: Fri, 8 Dec 2017 12:29:09 +0100 Subject: [PATCH 35/43] add merchant 'hammock universe' --- _data/merchants.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/_data/merchants.yml b/_data/merchants.yml index ac98f13c..025c1fe9 100644 --- a/_data/merchants.yml +++ b/_data/merchants.yml @@ -205,6 +205,8 @@ url: http://art2unlimited.webs.com/ - name: Game of Cryptos url: https://gameofcryptos.com/ + - name: Hammock Universe + url: https://www.hammockuniverseusa.com/ - name: Handcrafted goods url: https://mychain.store/ - name: InvestmentArt -- GitLab From 7a88e7ce114fa2da1821d88230f2afff28e9dacc Mon Sep 17 00:00:00 2001 From: erciccione Date: Fri, 8 Dec 2017 12:42:37 +0100 Subject: [PATCH 36/43] fix broken formatting of blog post (research lab meeting 2017-11-27) --- ...-for-the-Monero-Research-Lab-meeting-held-on-2017-11-27.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_posts/2017-11-27-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-11-27.md b/_posts/2017-11-27-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-11-27.md index f311620e..fe6d8b63 100644 --- a/_posts/2017-11-27-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-11-27.md +++ b/_posts/2017-11-27-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-11-27.md @@ -120,7 +120,7 @@ author: dEBRUYNE / fluffypony **\** i'm in a non-monogamous relationship with cryptonight **\** ok, well **\** anything else to discuss? -**\** i wouldn't mind putting up a portion of my funding for this period toward a Proof of Work contest for Monero's replacement proof of work scheme \<= I think othe already has some back up plans +**\** suraeNoether: i wouldn't mind putting up a portion of my funding for this period toward a Proof of Work contest for Monero's replacement proof of work scheme \<= I think othe already has some back up plans **\** apparently V wants ringCT in EVM2 **\** You might want to talk to him about it **\** othe are you around? @@ -177,4 +177,4 @@ author: dEBRUYNE / fluffypony **\** joker.jpg **\** ok guys **\** i'll be back later today -**\** entrepreneurs will always find a way to get above others; be it ASIC or botnets or webminers; what's important is that there's no barrier to entry for new players so that nobody's position is forever assured \ No newline at end of file +**\** entrepreneurs will always find a way to get above others; be it ASIC or botnets or webminers; what's important is that there's no barrier to entry for new players so that nobody's position is forever assured -- GitLab From 1fe9ce5cffe274bca5a7dcf62a9f6bef656a1059 Mon Sep 17 00:00:00 2001 From: MaxXor Date: Fri, 8 Dec 2017 09:39:02 +0100 Subject: [PATCH 37/43] Update blog post tags --- _data/tags.yml | 4 ++-- ...verview-and-logs-for-the-dev-meeting-held-on-2016-07-03.md | 2 +- ...verview-and-logs-for-the-dev-meeting-held-on-2016-07-31.md | 2 +- ...08-13-logs-for-the-Community-meeting-held-on-2017-08-13.md | 2 +- ...09-02-logs-for-the-Community-meeting-held-on-2017-09-02.md | 2 +- ...09-16-logs-for-the-Community-meeting-held-on-2017-09-16.md | 2 +- ...09-30-logs-for-the-Community-meeting-held-on-2017-09-30.md | 2 +- ...10-14-logs-for-the-Community-meeting-held-on-2017-10-14.md | 2 +- ...10-28-logs-for-the-Community-meeting-held-on-2017-10-28.md | 2 +- ...-for-the-Monero-Research-Lab-meeting-held-on-2017-10-30.md | 2 +- ...11-11-logs-for-the-Community-meeting-held-on-2017-11-11.md | 2 +- ...-for-the-Monero-Research-Lab-meeting-held-on-2017-11-13.md | 2 +- _posts/2017-11-13-workgroups-and-resources.md | 1 + ...11-25-logs-for-the-Community-meeting-held-on-2017-11-25.md | 2 +- ...-for-the-Monero-Research-Lab-meeting-held-on-2017-11-27.md | 2 +- _posts/2017-12-07-Monero-Compatible-Bulletproofs.md | 2 +- blog/tags/kovri.md | 3 --- 17 files changed, 17 insertions(+), 19 deletions(-) delete mode 100644 blog/tags/kovri.md diff --git a/_data/tags.yml b/_data/tags.yml index de837b44..3d9e4f4a 100644 --- a/_data/tags.yml +++ b/_data/tags.yml @@ -20,7 +20,7 @@ name: Mining - slug: i2p - name: i2p + name: Kovri I2P Router - slug: i8n name: Internationalization @@ -63,7 +63,7 @@ - slug: funding name: Funding and Donations - + - slug: research name: Monero Research Lab diff --git a/_posts/2016-07-03-overview-and-logs-for-the-dev-meeting-held-on-2016-07-03.md b/_posts/2016-07-03-overview-and-logs-for-the-dev-meeting-held-on-2016-07-03.md index 07821e60..555d65d8 100644 --- a/_posts/2016-07-03-overview-and-logs-for-the-dev-meeting-held-on-2016-07-03.md +++ b/_posts/2016-07-03-overview-and-logs-for-the-dev-meeting-held-on-2016-07-03.md @@ -2,7 +2,7 @@ layout: post title: Overview and Logs for the Dev Meeting Held on 2016-07-03 summary: OTF, open PRs and issues, and brief update on Ring CT -tags: [dev diaries, core, crypto, 0mq] +tags: [dev diaries, core, crypto] author: dEBRUYNE / fluffypony --- diff --git a/_posts/2016-07-31-overview-and-logs-for-the-dev-meeting-held-on-2016-07-31.md b/_posts/2016-07-31-overview-and-logs-for-the-dev-meeting-held-on-2016-07-31.md index 84e8ae52..e2098ee9 100644 --- a/_posts/2016-07-31-overview-and-logs-for-the-dev-meeting-held-on-2016-07-31.md +++ b/_posts/2016-07-31-overview-and-logs-for-the-dev-meeting-held-on-2016-07-31.md @@ -2,7 +2,7 @@ layout: post title: Overview and Logs for the Dev Meeting Held on 2016-07-31 summary: Monero Project repository, and brief update on Ring CT -tags: [dev diaries, core, crypto, 0mq] +tags: [dev diaries, core, crypto] author: dEBRUYNE / fluffypony --- diff --git a/_posts/2017-08-13-logs-for-the-Community-meeting-held-on-2017-08-13.md b/_posts/2017-08-13-logs-for-the-Community-meeting-held-on-2017-08-13.md index 84806679..714f3798 100644 --- a/_posts/2017-08-13-logs-for-the-Community-meeting-held-on-2017-08-13.md +++ b/_posts/2017-08-13-logs-for-the-Community-meeting-held-on-2017-08-13.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2017-08-13 summary: Monero Meetups, Serhack's web integrations, PoW discussion, eSport sponsoring, and miscellaneous -tags: [community, crypto] +tags: [community] author: dEBRUYNE / fluffypony --- diff --git a/_posts/2017-09-02-logs-for-the-Community-meeting-held-on-2017-09-02.md b/_posts/2017-09-02-logs-for-the-Community-meeting-held-on-2017-09-02.md index 4164a3fe..d4ba9411 100644 --- a/_posts/2017-09-02-logs-for-the-Community-meeting-held-on-2017-09-02.md +++ b/_posts/2017-09-02-logs-for-the-Community-meeting-held-on-2017-09-02.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2017-09-02 summary: Community highlights, Forum Funding System updates and discussion of new proposals, translations, Monero Meetup kit, and miscellaneous -tags: [community, crypto] +tags: [community] author: dEBRUYNE / fluffypony --- diff --git a/_posts/2017-09-16-logs-for-the-Community-meeting-held-on-2017-09-16.md b/_posts/2017-09-16-logs-for-the-Community-meeting-held-on-2017-09-16.md index db3e15e7..1b260c9f 100644 --- a/_posts/2017-09-16-logs-for-the-Community-meeting-held-on-2017-09-16.md +++ b/_posts/2017-09-16-logs-for-the-Community-meeting-held-on-2017-09-16.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2017-09-16 summary: Community highlights, Forum Funding System discussions, workgroups and resources, Monero support, translations, open ideas time, and miscellaneous -tags: [community, crypto] +tags: [community] author: dEBRUYNE / fluffypony --- diff --git a/_posts/2017-09-30-logs-for-the-Community-meeting-held-on-2017-09-30.md b/_posts/2017-09-30-logs-for-the-Community-meeting-held-on-2017-09-30.md index f494e66f..a04ee8b7 100644 --- a/_posts/2017-09-30-logs-for-the-Community-meeting-held-on-2017-09-30.md +++ b/_posts/2017-09-30-logs-for-the-Community-meeting-held-on-2017-09-30.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2017-09-30 summary: Community highlights, Forum Funding System updates, Monero Q&A sessions, Monero support, Monero meetups, Taiga projects, open ideas time, and miscellaneous -tags: [community, crypto] +tags: [community] author: dEBRUYNE / fluffypony --- diff --git a/_posts/2017-10-14-logs-for-the-Community-meeting-held-on-2017-10-14.md b/_posts/2017-10-14-logs-for-the-Community-meeting-held-on-2017-10-14.md index 401336d8..359d719e 100644 --- a/_posts/2017-10-14-logs-for-the-Community-meeting-held-on-2017-10-14.md +++ b/_posts/2017-10-14-logs-for-the-Community-meeting-held-on-2017-10-14.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2017-10-14 summary: Community highlights, Forum Funding System updates, Monero Coffee Chat debrief, Monero meetups & meetup kit, open ideas time, and miscellaneous -tags: [community, crypto] +tags: [community] author: dEBRUYNE / fluffypony --- diff --git a/_posts/2017-10-28-logs-for-the-Community-meeting-held-on-2017-10-28.md b/_posts/2017-10-28-logs-for-the-Community-meeting-held-on-2017-10-28.md index ec5db22d..8ed95be1 100644 --- a/_posts/2017-10-28-logs-for-the-Community-meeting-held-on-2017-10-28.md +++ b/_posts/2017-10-28-logs-for-the-Community-meeting-held-on-2017-10-28.md @@ -2,7 +2,7 @@ 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] +tags: [community] author: dEBRUYNE / fluffypony --- diff --git a/_posts/2017-10-30-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-10-30.md b/_posts/2017-10-30-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-10-30.md index b86ce36d..a4197bd2 100644 --- a/_posts/2017-10-30-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-10-30.md +++ b/_posts/2017-10-30-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-10-30.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2017-10-30 summary: Multisig, hash-based accumulators, blockchain protocols, quantum-hard shuffle PRNG, educational outreach, and miscellaneous -tags: [community, crypto] +tags: [community, crypto, research] author: dEBRUYNE / fluffypony --- diff --git a/_posts/2017-11-11-logs-for-the-Community-meeting-held-on-2017-11-11.md b/_posts/2017-11-11-logs-for-the-Community-meeting-held-on-2017-11-11.md index 76aea4de..4c7baf1c 100644 --- a/_posts/2017-11-11-logs-for-the-Community-meeting-held-on-2017-11-11.md +++ b/_posts/2017-11-11-logs-for-the-Community-meeting-held-on-2017-11-11.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2017-11-11 summary: Community highlights, Forum Funding System updates, RFC-HWALLET-1, Monero December, upcoming meetups, growing involvement, and miscellaneous -tags: [community, crypto] +tags: [community] author: dEBRUYNE / fluffypony --- diff --git a/_posts/2017-11-13-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-11-13.md b/_posts/2017-11-13-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-11-13.md index decf34db..ad915dce 100644 --- a/_posts/2017-11-13-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-11-13.md +++ b/_posts/2017-11-13-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-11-13.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2017-11-13 summary: Educational outreach, multisig, Bulletproofs (range proofs), RuffCT, and miscellaneous -tags: [community, crypto] +tags: [community, crypto, research] author: dEBRUYNE / fluffypony --- diff --git a/_posts/2017-11-13-workgroups-and-resources.md b/_posts/2017-11-13-workgroups-and-resources.md index a1708cea..443469fc 100644 --- a/_posts/2017-11-13-workgroups-and-resources.md +++ b/_posts/2017-11-13-workgroups-and-resources.md @@ -2,6 +2,7 @@ layout: post title: Workgroups and Resources summary: A brief overview of workgroups in Monero and the resources that are provided for them to succeed. +tags: [community] author: rehrar --- diff --git a/_posts/2017-11-25-logs-for-the-Community-meeting-held-on-2017-11-25.md b/_posts/2017-11-25-logs-for-the-Community-meeting-held-on-2017-11-25.md index 9591d4a5..c35b87e8 100644 --- a/_posts/2017-11-25-logs-for-the-Community-meeting-held-on-2017-11-25.md +++ b/_posts/2017-11-25-logs-for-the-Community-meeting-held-on-2017-11-25.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Community Meeting Held on 2017-11-25 summary: Community highlights, Forum Funding System updates, RFC-HWALLET-1, Monero integrations, Malware Response Workgroup, Monero Coffee Chat, and miscellaneous -tags: [community, crypto] +tags: [community] author: dEBRUYNE / fluffypony --- diff --git a/_posts/2017-11-27-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-11-27.md b/_posts/2017-11-27-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-11-27.md index fe6d8b63..91b254fd 100644 --- a/_posts/2017-11-27-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-11-27.md +++ b/_posts/2017-11-27-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-11-27.md @@ -2,7 +2,7 @@ layout: post title: Logs for the Monero Research Lab Meeting Held on 2017-11-27 summary: SPECTRE, multisig, Bulletproofs (range proofs), ZKStarks, ASIC resistance, and miscellaneous -tags: [community, crypto] +tags: [community, crypto, research] author: dEBRUYNE / fluffypony --- diff --git a/_posts/2017-12-07-Monero-Compatible-Bulletproofs.md b/_posts/2017-12-07-Monero-Compatible-Bulletproofs.md index e78f579d..8bd36862 100644 --- a/_posts/2017-12-07-Monero-Compatible-Bulletproofs.md +++ b/_posts/2017-12-07-Monero-Compatible-Bulletproofs.md @@ -1,7 +1,7 @@ --- layout: post title: Monero Compatible Bulletproofs -tags: [crypto, mrl, dev] +tags: [crypto, research] author: Sarang Noether --- diff --git a/blog/tags/kovri.md b/blog/tags/kovri.md deleted file mode 100644 index 320028d5..00000000 --- a/blog/tags/kovri.md +++ /dev/null @@ -1,3 +0,0 @@ ---- -layout: blog_by_tag ---- \ No newline at end of file -- GitLab From c860bb18c06580bb79e4ebb035856e4be02753c5 Mon Sep 17 00:00:00 2001 From: Matt Smith Date: Wed, 29 Nov 2017 22:30:03 +0000 Subject: [PATCH 38/43] Add MegaChange.is exchange Fix #466 --- _data/merchants.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/_data/merchants.yml b/_data/merchants.yml index 025c1fe9..21d9e7c9 100644 --- a/_data/merchants.yml +++ b/_data/merchants.yml @@ -39,6 +39,8 @@ url: https://localmonero.co/ - name: Magnetic Exchange url: https://magneticexchange.com + - name: MegaChange.is + url: https://megachange.is - name: MoneroDirect (Euro only) url: https://monerodirect.com - name: Poloniex -- GitLab From 7dc0640669b42f62bf3cb24e0122c6de8a2b3a34 Mon Sep 17 00:00:00 2001 From: Mike Justman Date: Thu, 30 Nov 2017 06:25:39 -0500 Subject: [PATCH 39/43] Add merchants --- _data/merchants.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/_data/merchants.yml b/_data/merchants.yml index 21d9e7c9..bb1cd9c8 100644 --- a/_data/merchants.yml +++ b/_data/merchants.yml @@ -49,6 +49,8 @@ url: https://shapeshift.io/ - name: Tux Exchange url: https://www.tuxexchange.com/trade?coin=XMR&market=BTC + - name: Trovemat.com (ATM) + url: https://trovemat.com/ - category: Block Explorers id: block-explorers merchants: @@ -223,6 +225,8 @@ url: https://synntechgaming.com - name: Xusah Boutique url: https://xusah.boutique/ + - name: Judit Mátyus - Jewelry + url: https://www.juditmatyus.com/ - category: Entertainment id: entertainment merchants: -- GitLab From 33ed80297320c2a4272fc743a800186cbdfa242c Mon Sep 17 00:00:00 2001 From: MaxXor Date: Fri, 8 Dec 2017 22:56:16 +0100 Subject: [PATCH 40/43] Fix missing protocol upgrade tag --- blog/tags/protocol upgrade.md | 3 +++ 1 file changed, 3 insertions(+) create mode 100644 blog/tags/protocol upgrade.md diff --git a/blog/tags/protocol upgrade.md b/blog/tags/protocol upgrade.md new file mode 100644 index 00000000..320028d5 --- /dev/null +++ b/blog/tags/protocol upgrade.md @@ -0,0 +1,3 @@ +--- +layout: blog_by_tag +--- \ No newline at end of file -- GitLab From b1189d0ba3856e1507bf430c6a2150fffa021736 Mon Sep 17 00:00:00 2001 From: MaxXor Date: Sat, 9 Dec 2017 10:06:59 +0100 Subject: [PATCH 41/43] Remove unnecessary entries from .gitignore --- .gitignore | 1 - 1 file changed, 1 deletion(-) diff --git a/.gitignore b/.gitignore index e8b7275b..cd3c9c3c 100644 --- a/.gitignore +++ b/.gitignore @@ -2,4 +2,3 @@ ietemplates/ _site/* .idea/ *.swp -tags -- GitLab From d9d56cd1e74c7d2e0006acf38ebabb9892a9a104 Mon Sep 17 00:00:00 2001 From: Matt Smith Date: Sat, 9 Dec 2017 08:56:52 +0000 Subject: [PATCH 42/43] Add Crypto Armory merchant --- _data/merchants.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/_data/merchants.yml b/_data/merchants.yml index bb1cd9c8..00543bcd 100644 --- a/_data/merchants.yml +++ b/_data/merchants.yml @@ -197,6 +197,8 @@ url: https://allforcrypto.com - name: Cellphone and laptop repair online store in Sweden url: http://www.LagaiPhone.se + - name: Crypto Armory - ammunition for cryptocurrency at a competitive rate + url: https://www.crypto-armory.com - name: CryptoMercado - coffee and snacks url: https://www.cryptomercado.com/ - name: Cryptonic Physical Monero & Bitcoin coins -- GitLab From 4d7962bb923ceb3c162e7b6fba4026e31bf40433 Mon Sep 17 00:00:00 2001 From: dEBRUYNE-1 Date: Sun, 10 Dec 2017 20:26:38 +0100 Subject: [PATCH 43/43] A note on fees Fix tags Remove redundant text Fix current emission variable Fix calculations --- _posts/2017-12-11-A-note-on-fees.md | 118 ++++++++++++++++++++++++++++ 1 file changed, 118 insertions(+) create mode 100644 _posts/2017-12-11-A-note-on-fees.md diff --git a/_posts/2017-12-11-A-note-on-fees.md b/_posts/2017-12-11-A-note-on-fees.md new file mode 100644 index 00000000..a322247e --- /dev/null +++ b/_posts/2017-12-11-A-note-on-fees.md @@ -0,0 +1,118 @@ +--- +layout: post +title: A note on fees +tags: [crypto, research] +author: dEBRUYNE / ArticMine +--- + +Lately, a common reoccurring complaint has been that fees are too expensive. Whilst we don't disagree with that statement, we have to thoroughly analyze the situation first. Furthermore, the notion of devs having to release new binaries with lower fees is myopic, because (i) it'd merely kick the can down the road, (ii) changing the constants or formulas requires a hard fork, i.e., they are enforced on a consensus level, and (iii) constantly intervening would be contradictory to our grass-roots, decentralized nature. + +Let's start by comparing Monero's per kB fees to the per kB fees of other (hybrid) proof-of-work coins. Fees per kB for a typical transaction (2 inputs + 2 outputs): + +- **Bitcoin:** ~$26.90 +- **Ethereum:** ~$2.91 +- **Litecoin:** ~$0.10 +- **Dash:** ~$0.07 +- **Monero:** ~$0.24 + +As you can see, the per kB fee of Monero is fairly low. However, due to the high transaction size, the absolute default fee (in $ terms) is quite high. Note that the transaction size is this big due to Monero's inherent default privacy, i.e., the range proofs, which mask the amount values, make up ~12 kB of a single transaction. RingCT, however, was absolutely necessary to strengthen the privacy of the network. More specifically, there were a lot of privacy "leaks" when Monero didn't mask amounts yet. Fortunately, [Bulletproofs](https://getmonero.org/2017/12/07/Monero-Compatible-Bulletproofs.html) will reduce transaction sizes by at least 80%. + +----------------- + +To thoroughly analyze the situation, let's continue with examining the constants. We start with examining the penalty function and the dynamic block size algorithm. The formula is as follows: + +**Penalty = BaseReward * ((BlockSize / MN) - 1)²** + +The new reward is: + +**NewReward = BaseReward - Penalty** + +Where: + + - MN is the median of the block size over the last N blocks, with N being [100](https://github.com/monero-project/bitmonero/blob/master/src/cryptonote_config.h#L57) in Monero + - BlockSize is the size of the current block + - BaseReward is the reward as per the emission curve or where applicable the tail emission + - NewReward is the actual reward paid to the miner + - The maximum allowed block size is 2MN + +Note that the formula of the BaseReward is defined [as follows](https://bitcointalk.org/index.php?topic=583449.0): + +**BaseReward = 2 * ((S - A) * 2-20 * 10-12)** + +Where: + + - 2 is the adjustment factor for the switch to two minute blocks + - S is the initial number of atomic units is = 264 - 1 + - A is the current circulation, which can be found [here](https://moneroblocks.info/). In addition, the current circulation (emission) displayed on the block explorer has to be multiplied with 1012 (Monero uses 12 decimal places) to convert it to atomic units. + +Note that the minimum block size limit is 300 kB. Thus, miners are able to construct blocks up to 300 kB without incurring a penalty. In other words, aforementioned penalty function only "kicks in" for blocks bigger than 300 kB. + +Now, a default transaction in Monero, i.e., one that has two inputs and two outputs, is approximately 13.2 kB. Let's plug this into the formula: + +Assuming a current `BaseReward` of 5.7 XMR: + +`Penalty` = (5.7 * ((313.2/300)-1)², which yields ~0.011 XMR. + +Note that the `BaseReward` was significantly higher 6-12 months ago, which translates to a higher penalty. + +Now, miners need incentive to expand the block size. Therefore, the fee from including one additional transaction (above 300 kB) needs to outweigh the penalty. Otherwise, miners will simply fill blocks until 300 kB and exclude any other transactions, which would lead to a congested network and a large mempool. In sum, the current default fee (~0.013) was set to incentivize miners to include one additional transaction in their blocks without losing revenue. + +As you can see from aforementioned penalty function, the penalty will go down when the base reward decreases. Furthermore, as can be easily spotted by graphing the function, the penalty function is more "lenient" in the beginning of the function. This means that any decrease in transaction size translates to a bigger than equal decrease in fees. Put differently, for example, an 80% reduction in transaction size could lead to an 90% reduction in fees. Let's play around with the formula to get some more concrete numbers. Assuming single-output bulletproofs, the transaction size of a typical transaction would be ~2.5 kB. Now, let's also assume that we want to incentivize miners to expand the block size with two transactions without losing revenue. That is, they will be able to include two additional transactions (above the minimum block size limit) without the penalty outweighing the fees. Plugging in the numbers, we get: + +`Penalty` = (5.7 * ((305/300)-1)², which yields ~0.0016 XMR or ~0.0008 XMR per typical transaction. + +Reducing the transaction size with approximately 80%, but keeping the same minimum block size limit might be a bit blunt. Therefore, it could be that the minimum block size limit would be lowered to 100, 150, 200, or 250 kB. Let's plug in the numbers again: + +`Penalty` = (5.7 * ((255/250)-1)², which yields ~0.0023 XMR or ~0.00115 XMR per typical transaction. + +`Penalty` = (5.7 * ((205/200)-1)², which yields ~0.0036 XMR or ~0.0018 XMR per typical transaction. + +`Penalty` = (5.7 * ((155/150)-1)², which yields ~0.0063 XMR or ~0.00315 XMR per typical transaction. + +`Penalty` = (5.7 * ((105/100)-1)², which yields ~0.014 XMR or ~0.007 XMR per typical transaction. + +You can graph all the outcomes by setting MN to `x` and `BlockSize` to `x+5`. + +----------------- + +One might ask oneself, how does the dynamic fee algorithm come into play? First, to clarify, the default fee is set to account for the penalty in a bare minimum case. That is, a case where miners expand the block size with one additional transaction above the minimum block size limit. More specifically, in the current situation it would mean creating a block of 313 kB (to reiterate, the minimum block size is 300 kB). Once the median block size (of the last 100 blocks) significantly diverges from the minimum block size, the dynamic fee algorithm comes into play. + +Let's examine the dynamic fee algorithm: + +**Fee = (R/R0) * (M0/M) * F0** + +Where: + +- R is the base reward +- R0 is the reference base reward (10 XMR) +- M is the block size limit +- M0 is the minimum block size limit (300 kB) +- F0 is 0.002 XMR + +As a practical example, a few moons ago the median block size increased to approximately 400 kB and thhe default fee went down to ~0.0095. As we can see from the formula, this approximately matches the theoretical fee. That is: + +`Fee` = (6.5/10) * (300/400) * 0.002 = 0.00975 + +Basically the inverse of the percentage increase of the median block size (against a base of the minimum block size) translates to the percentage reduction in fees. More specifically, a 600 kB median block size, which is a 100% (or factor 2) increase translates to a 50% (1/2) reduction in fees. + +So why did the significant price increase not lead to a significant reduction in absolute fees, i.e., fees in XMR terms? Well, basically, the factor increase in price was significantly higher than the factor increase in usage. Furthermore, the median block size needs to be constantly above 300 kB in order for the dynamic fee algorithm to work properly. Moreover, the algorithm was designed to correlate with price, but, as we can see, price is imperfectly correlated with usage. In sum, whilst usage has grown a lot, it hasn't grown as much as the price and therefore fees (in XMR terms) have not declined yet. + +------------- + +From combining the penalty formula and the dynamic block size formula with the dynamic fee formula we can infer that a higher minimum block size limit (for example, 300 kB) leads to lower initial default fees, but fee reduction (by the dynamic fee algorithm) being somewhat "slow". By contrast, a lower minimum block size limit (for example, 150 kB) leads to higher initial default fees, but faster fee reduction. + +In conclusion, whilst fees are currently too high, they, most likely, won't be anymore in the future. In addition, more research has to be conducted on the topic of the minimum block size limit, because, preferably, we'd like to use a limit that doesn't require future intervention anymore. + +---------------- + +**A few remaining notes:** + +1. *Median* fees were taken from [Bitinfocharts](https://bitinfocharts.com/). + +2. A more in depth analysis (by ArticMine) of the penalty function can be found [here](https://bitcointalk.org/index.php?topic=753252.msg13591241#msg13591241). + +3. The penalty function in the original [CryptoNote whitepaper](cryptonote.org/whitepaper.pdf) is somewhat different. More information can be found [here](https://monero.stackexchange.com/questions/1067/block-reward-penalties-and-dynamic-block-size). + +4. Code details and the actual implementation of the dynamic block size algorithm can be found [here](https://github.com/monero-project/monero/blob/master/src/cryptonote_basic/cryptonote_basic_impl.cpp). + +5. Code details and the actual implementation of the dynamic fee algorithm can be found [here](https://github.com/monero-project/monero/commit/82dbba10d467e28e56929e2e7f3b1f04d4635da4). \ No newline at end of file -- GitLab