diff --git a/.gitignore b/.gitignore
index e8b7275b2fe77a9f52b792a3578d81f961c962b0..cd3c9c3cb86fb84d85944f9c0930f495070ee9d7 100644
--- a/.gitignore
+++ b/.gitignore
@@ -2,4 +2,3 @@ ietemplates/
_site/*
.idea/
*.swp
-tags
diff --git a/Gemfile b/Gemfile
index b74ac8cdaabd1c1a2009e1c9c03a28b17099af4f..205752b7bc0b3fc60472a8ea3a999fcbb80440f8 100644
--- a/Gemfile
+++ b/Gemfile
@@ -5,3 +5,4 @@ gem 'jekyll-paginate'
gem 'builder'
gem 'rubysl-rexml'
gem 'wdm', '>= 0.1.0' if Gem.win_platform?
+gem 'jekyll-multiple-languages-plugin'
diff --git a/Gemfile.lock b/Gemfile.lock
index 4fa6f3fea618e9070f68f385dcf3821f69d96062..8725b914bda936a661f60e04f985226c1f0e1070 100644
--- a/Gemfile.lock
+++ b/Gemfile.lock
@@ -18,6 +18,8 @@ GEM
pathutil (~> 0.9)
rouge (~> 1.7)
safe_yaml (~> 1.0)
+ jekyll-multiple-languages-plugin (1.5.1)
+ jekyll (>= 2.0, < 4.0)
jekyll-paginate (1.1.0)
jekyll-sass-converter (1.5.0)
sass (~> 3.4)
@@ -50,6 +52,7 @@ PLATFORMS
DEPENDENCIES
builder
jekyll
+ jekyll-multiple-languages-plugin
jekyll-paginate
rubysl-rexml
diff --git a/README.md b/README.md
index a7e616d3cfed9d20f058b845e8e28f4105ca05ba..3f48957fa677d368cd8709e1c3ad0763fabf6f5d 100644
--- a/README.md
+++ b/README.md
@@ -1,6 +1,9 @@
# Monero Website Instructions
-Copyright (c) 2014-2017, The Monero Project
+Copyright (c) 2014-2018, The Monero Project
+
+## IMPORTANT MULTILANGUAGE UPDATE NOTICE
+The multilingual update has recently been rolled out. The website now requires more steps to update so everyone can have a smooth experience. Please read all instructions carefully and follow them all! If they are not all followed, this leads to a ton of work for the website maintainers. A warning will be issued to repeat offenders. If you need help/support, you can find it on `#monero-translations` and [Taiga](https://taiga.getmonero.org/project/erciccione-monero-localization/wiki/home)
## Table of Contents
@@ -28,11 +31,15 @@ Copyright (c) 2014-2017, The Monero Project
12.0 How to add a question to the FAQ
-13.0 License
+13.0 How to translate a page
+
+14.0 How to add a new language
+
+15.0 License
## 1.0 Introduction
-This README here to walk you through everything you need to know to make changes, edits, or even completely new pages for the new [getmonero.org website](https://getmonero.org/). It'll definitely be a bit of a ride, so strap yourself in. Please note that translations are not available yet, but when they are added, this document will be updated with instructions on how to translate the content of [getmonero.org website](https://getmonero.org/). In the meantime, any help translating this document into another language is greatly appreciated.
+This README here to walk you through everything you need to know to make changes, edits, or even completely new pages for the new [getmonero.org website](https://getmonero.org/). It'll definitely be a bit of a ride, so strap yourself in.
Feel free to skip down to a relevant section if you already know what you need. So to go to the 'How to make a User Guide' section use your find function and type '5.0'.
@@ -71,10 +78,16 @@ Every section from here on out will talk about how to make a specific type of we
A few random points of note:
- All external links must have http:// or https:// in front of them or they will not redirect properly.
-- If you want to add a new page to the navigation, you should note that there are two menus in `header.html`. One for mobile and one for desktop. Your page must be added in the appropriate place in BOTH navigations.
+- If you want to add a new page to the navigation, you should go to ALL LANGUAGES in the `_data/lang` folder including `template` and add the page.
- It is strongly strongly STRONGLY encouraged that you if you make a change, you - at the minimum - test it on your local machine before submitting a PR. Sometimes unexpected things may happen due to a change. If you change a page, check the whole page on multiple screen sizes and browsers to make sure there wasn't any collateral damage.
### 3.1 Housekeeping
+
+#### Editing the Site
+When you make an edit to ANY page on the English language of this website, PLEASE copy your changes into the corresponding `/_i18n/template/` file as well.
+
+The Monero Translation workgroup will do their best to keep tabs on all changes of the site, but it'd be nice to notify them that you've changed a page so they can make sure the equivalent pages are changed accordingly in the other languages.
+
#### GitHub Issues
We ask that if you open an issue on the site that you remain available for clarifying questions or corrections. We do our best to close issues that are resolved when we make changes to the site, but If your issue is resolved by a contributer and the issue is not closed we ask that you close it in a timely manner. A contributer (rehrar, SamsungGalaxyPlayer, or other community members, etc) may ask you to close an issue after it's confirmed fixed. Please review the changes to the site and close your issue if you can verify that it's fixed.
@@ -119,42 +132,63 @@ You're all done. Submit a PR and wait for it to be reviewed and merged. Be sure
### 5.1 Quick Start
-* Make file in /resources/user-guides with an .md ending and no spaces in filename.
-* Front Matter as in 5.3
+* Create file in /resources/user-guides with an .md ending and no spaces in filename.
+* File content as in 5.3
+* Create file in /_i18n/en/resources/user-guides with the exact same filename as above ending in .md
* Write User Guide
-* Add guide using markdown in the correct category in /resources/user-guides/index.md being careful not to mess with any indentation
+* Copy User Guide file to ALL LANGUAGES in /_i18n/[ALL LANGUAGES]/resources/user-guides
+* Paste `{% include untranslated.html %}` into the top of each language version of your User Guide, except the original language
+* Add guide using markdown in the correct category in ALL LANGUAGES to /_i18n/[ALL LANGUAGES]/resources/user-guides/index.md being careful not to mess with any indentation
* Test/Build
* Submit PR
### 5.2 Make a file
Navigate to the /resources/user-guides folder and make a new file. Be sure the file name has no spaces and the ending is .md
-### 5.3 Front Matter
+### 5.3 Content of file
```
---
-layout: static_page
+layout: user-guide
title: TITLE OF YOUR USER GUIDE
+permalink: /resources/user-guides/NAME-OF-FILE-GOES-HERE.html
---
+
+{% tf resources/user-guides/NAME-OF-FILE-GOES-HERE.md %}
```
-### 5.4 Write
+Copy this exactly and merely change the files names where indicated.
+
+### 5.4 Create file in localization folders
+Navigate to the /i18n/ folder and choose the correct folder for your language. Navigate further into the `resources/user-guides` folders and make a .md file with the EXACT SAME filename as the you made before.
+
+### 5.5 Write
Write your user guide. Be succinct but thorough. Remember, people will be using your guides when they need help. Make sure all the information is there. Feel free to use images or screenshots if necessary to help get your point across.
-### 5.5 Add Guide to the 'User Guide' landing page
-In the /resources/user-guides folder, find the file labeled index.md and open it.
+The title should be at the top of the User Guide using a single `#` for an H1 tag. Titles will not be automatically put on these pages as with other pages. There should be NO front matter on this file.
+
+### 5.6 Copy User Guide file into all languages
+Copy your file and navigate to each language file in the /i18n folder. In each language folder (INCLUDING template) go to the resources/user-guides folder and paste your user guide (don't worry, you don't have to translate it) there. This is very important, and the site will not build if the file with the same name is not in each language folder.
+
+As you paste into each folder, open up the file and paste the following snippet at the top of the file (before your title):
+`{% include untranslated.html %}`. This does not need to be done in the original language that the User Guide was written in.
+
+### 5.7 Add Guide to the 'User Guide' landing page of EACH LANGUAGE
+In the /_i18n/[ORIGINAL LANGUAGE OF USER GUIDE]/resources/user-guides folder, find the file labeled index.md and open it.
DO NOT CHANGE ANYTHING IN THIS DOCUMENT BESIDES WHAT YOU ARE INSTRUCTED TO.
This file will look quite different because it's HTML. Don't panic. Simply Ctrl + F (i.e. the find feature) and search for the category that you want to put your User Guide in. You will see there are some sections that are not indented like the others. They are flush with the left side of the screen. **Do not change the indentation.** You can put markdown in these areas.
-Once you've identified the non-indented area under the category you would like your User Guide to be under, you can use markdown to insert your link underneath the others. `[TITLE OF USER GUIDE](LINK-TO-USER-GUIDE.html)`. Please note that the file name in between the parentheses must be EXACTLY the same name as the file name you made in step 5.2, but with a `.html` at the end instead of `.md`.
+Once you've identified the non-indented area under the category you would like your User Guide to be under, you can use markdown to insert your link underneath the others. `[TITLE OF USER GUIDE]({{site.baseurl}}/LINK-TO-USER-GUIDE.html)`. Please note that the file name in between the parentheses must be EXACTLY the same name as the permalink you made in step 5.3, but with a `.html` at the end instead of `.md` and the snippet `{{site.baseurl}}/` before the link.
In the event that you think your User Guide should be in a new Category that doesn't exist yet, contact rehrar to make one for you.
-### 5.6 Build/Test
+Repeat the above process for each language version of this index page INCLUDING THE template.
+
+### 5.8 Build/Test
Build your website using `jekyll serve` if it's not rebuilding automatically and test that your link appears in the correct category and that it leads to your User Guide when clicked. Test your User Guide in the browser and contact rehrar if there are any bugs.
-### 5.7 Submit Pull Request
+### 5.9 Submit Pull Request
You're all done. Submit a PR and wait for it to be reviewed and merged. Be sure to make any changes if requested.
## 6.0 How to make a Moneropedia Entry
@@ -422,7 +456,67 @@ Build your website using `jekyll serve` if it's not rebuilding automatically. If
### 12.3 Submit a Pull Request
You're all done. Submit a PR and wait for it to be reviewed and merged. Be sure to make any changes if requested.
-## 13.0 Website License
+## 13.0 How to translate a page
+In this section you'll find the info you need to translate a page and add a new translation, but keep in mind that Monero has a [Localization Workgroup](https://taiga.getmonero.org/project/erciccione-monero-localization/) who coordinate and give support to translators-volunteers. You can find an updated guide and an example of the workflow we use on our [Guide on Taiga](https://taiga.getmonero.org/project/erciccione-monero-localization/wiki/translating-monero-website) (frequently updated), also, for live support/request of infos, come chat on `#monero-translations` (Freenode/IRC, riot/matrix, MatterMost).
+
+### 13.1 Quickstart
+* Navigate to the correct language in the /i18n folder and find the page you wish to translate
+* Click the file and translate the page, not touching any HTML or markdown.
+* Remove `{% include untranslated.html %}` from the page
+* Test/Build
+* Submit PR
+
+### 13.2 Naviate to correct file
+Go to the /i18n folder and find the two letter code for the language you wish to translate for. Enter that folder and find the file you wish to translate. The filenames are all in English and MUST NOT BE CHANGED.
+
+### 13.3 Translate the file
+Here you can do your translation. Depending on the page, you may have to maneuver around some HTML or markdown. In general, anything between two tags (such as `<p>TRANSLATE THIS</p>`) should be fine. Testing is VERY important, so do NOT skip step 13.4. If during testing, the page appears different from the original English page (besides the translated text of course), you did something wrong and may have to start again.
+
+### 13.4 Remove the 'untranslated' snippet
+Somewhere on the page (usually the top) should be a snippet that says `{% include untranslated.html %}`. Simply delete this completely from the file. This will remove the orange bar from the bottom saying the page is untranslated.
+
+### 13.5 Build/Test
+Build your website using `jekyll serve` if it's not rebuilding automatically.
+
+If the build is successful, go to the correct page in the correct language and check to see that everything is translated, and that the page looks identical to the original English page (besides the translated text). Test the page and let rehrar know if there are any bugs.
+
+### 13.6 Submit a Pull Request
+You're all done. Submit a PR and wait for it to be reviewed and merged. Be sure to make any changes if requested.
+
+## 14.0 How to add a new language
+Whoo boy, this is the big one. Please follow all directions exactly.
+
+### 14.1 _config.yml file
+Navigate to the root folder of the whole website and find the file labeled `_config.yml`. Open it and find the line that says `languages:`. Add your two letter language code (Google it if you don't know it) in between the brackets after the others already present. You will need to put a comma after the previous last one.
+
+Example:
+```
+languages: ["en", "es", "NEW LANG HERE"]
+```
+Save and exit the file.
+
+### 14.2 _data folder
+Navigate to the `_data/lang` folder and copy the `template` folder. Paste it into the same folder and the copy renamed to the two letter language code of the language you will be translated to.
+**The template folder itself should still be there. It should not be renamed. There should be a new folder in addition to the ones that were already there.**
+
+Translate the content of the files. Do not touch anything labeled `url`, and in the roadmap.yml ONLY translate the `name:` content.
+
+### 14.3 _i18n folder
+Navigate to the _i18n folder and duplicate the template.yml file. Rename the duplicate to the two letter language code of your language with a `.yml` at the end. Repeat this process with the `template` folder as well.
+**The template folder and yml file themselves should still be there. They should not be renamed. There should be a new folder and yml file in addition to the ones that were already there.**
+
+Enter the .yml file and translate everything there.
+
+### 14.3 Translate
+If you will be translating the content, please refer to section 13.0 in this README for instructions on translating pages.
+
+### 14.4 Build/Test
+Build your website using `jekyll serve`. If the build is successful, navigate to any page on the site and check to make sure that your language is appearing in the dropdown for languages on both mobile and desktop.
+
+### 14.5 Submit a Pull Request
+You're all done. Submit a PR and wait for it to be reviewed and merged. Be sure to make any changes if requested.
+
+## 15.0 Website License
Copyright (c) 2014-2017, The Monero Project
diff --git a/_config.yml b/_config.yml
index b0cb1cebc8131e6a3782c32260538a34199e5f81..2e37b6aa0f11ced2fe88de80c5d86da248d98363 100644
--- a/_config.yml
+++ b/_config.yml
@@ -14,10 +14,22 @@ kramdown:
input: GFM
exclude: ["README.md"]
-gems: [jekyll-paginate]
+
+# paginate
paginate: 10
paginate_path: blog/page:num/
+gems:
+ - jekyll-paginate
+ - jekyll-multiple-languages-plugin
+
+# jekyll-multiple-languages-plugin settings:
+languages: ["en", "es"]
+
+exclude_from_localizations: ["img", "css", "fonts", "media", "404", "feed.xml", "404", "meta", "forum-funding-system", "_posts", "legal"]
+
+
+
# Windows live tiles config
ie_tile_color: eeeeee
ie_tile_small: https://static.getmonero.org/images/live-tiles/small.png
diff --git a/_config/nginx.conf b/_config/nginx.conf
index d345224921d0646d1d717f32225d5d173cdc0ef0..b5748a71384bfab8bab08c1af61a50711add219a 100644
--- a/_config/nginx.conf
+++ b/_config/nginx.conf
@@ -55,58 +55,72 @@ server {
}
# End of general restrictions
+ rewrite ^/home / permanent;
+ rewrite ^/knowledge-base / permanent;
+ rewrite ^/knowledge-base/projects /resources/merchants/ permanent;
+ rewrite ^/knowledge-base/user-guides /resources/user-guides/ permanent;
+ rewrite ^/knowledge-base/developer-guides /resources/developer-guides/ permanent;
+ rewrite ^/knowledge-base/moneropedia /resources/moneropedia/ permanent;
+ rewrite ^/knowledge-base/people /community/team/ permanent;
+ rewrite ^/knowledge-base/open-alias /the-monero-project/ permanent;
+ rewrite ^/knowledge-base/about /resources/about/ permanent;
+ rewrite ^/getting-started/donate /get-started/contributing/ permanent;
+ rewrite ^/getting-started/accepting /get-started/accepting/ permanent;
+ rewrite ^/getting-started/merchants /community/merchants/ permanent;
+ rewrite ^/getting-started/running /get-started/using/ permanent;
+
# Downloads!
location /win64 {
- rewrite ^ /cli/monero-win-x64-v0.10.3.1.zip redirect;
+ rewrite ^ /cli/monero-win-x64-v0.11.1.0.zip redirect;
}
location /win32 {
- rewrite ^ /cli/monero-win-x86-v0.10.3.1.zip redirect;
+ rewrite ^ /cli/monero-win-x86-v0.11.1.0.zip redirect;
}
location /mac64 {
- rewrite ^ /cli/monero-mac-x64-v0.10.3.1.tar.bz2 redirect;
+ rewrite ^ /cli/monero-mac-x64-v0.11.1.0.tar.bz2 redirect;
}
location /linux64 {
- rewrite ^ /cli/monero-linux-x64-v0.10.3.1.tar.bz2 redirect;
+ rewrite ^ /cli/monero-linux-x64-v0.11.1.0.tar.bz2 redirect;
}
location /linux32 {
- rewrite ^ /cli/monero-linux-x86-v0.10.3.1.tar.bz2 redirect;
+ rewrite ^ /cli/monero-linux-x86-v0.11.1.0.tar.bz2 redirect;
}
location /linuxarm7 {
- rewrite ^ /cli/monero-linux-armv7-v0.10.3.1.tar.bz2 redirect;
+ rewrite ^ /cli/monero-linux-armv7-v0.11.1.0.tar.bz2 redirect;
}
location /linuxarm8 {
- rewrite ^ /cli/monero-linux-armv8-v0.10.3.1.tar.bz2 redirect;
+ rewrite ^ /cli/monero-linux-armv8-v0.11.1.0.tar.bz2 redirect;
}
location /freebsd64 {
- rewrite ^ /cli/monero-freebsd-x64-v0.10.3.1.tar.bz2 redirect;
+ rewrite ^ /cli/monero-freebsd-x64-v0.11.1.0.tar.bz2 redirect;
}
location /dragonflybsd64 {
- rewrite ^ /cli/monero-dragonflybsd-x64-v0.10.3.1.tar.bz2 redirect;
+ rewrite ^ /cli/monero-dragonflybsd-x64-v0.11.1.0.tar.bz2 redirect;
}
# GUI downloads
location /gui/win64 {
- rewrite ^ /gui/monero-win-x64-v0.10.3.1.zip redirect;
+ rewrite ^ /gui/monero-gui-win-x64-v0.11.1.0.zip redirect;
}
location /gui/mac64 {
- rewrite ^ /gui/monero-mac-x64-v0.10.3.1.tar.bz2 redirect;
+ rewrite ^ /gui/monero-gui-mac-x64-v0.11.1.0.tar.bz2 redirect;
}
location /gui/linux64 {
- rewrite ^ /gui/monero-linux-x64-v0.10.3.1.tar.bz2 redirect;
+ rewrite ^ /gui/monero-gui-linux-x64-v0.11.1.0.tar.bz2 redirect;
}
location /gui/linux32 {
- rewrite ^ /gui/monero-linux-x86-v0.10.3.1.tar.bz2 redirect;
+ rewrite ^ /gui/monero-gui-linux-x86-v0.11.1.0.tar.bz2 redirect;
}
# Other download redirects
diff --git a/_data/lang/en/footer-1.yml b/_data/lang/en/footer-1.yml
new file mode 100644
index 0000000000000000000000000000000000000000..2d0408f8e0f920fc623ae00cbe0c185bf9c57486
--- /dev/null
+++ b/_data/lang/en/footer-1.yml
@@ -0,0 +1,50 @@
+- title: Resources
+ subfolderitems:
+ - name: About Monero
+ url: resources/about/
+ - name: Moneropedia
+ url: resources/moneropedia/
+ - name: Developer Guides
+ url: resources/developer-guides/
+ - name: User Guides
+ url: resources/user-guides/
+ - name: RSS Feed
+ url: https://getmonero.org/feed.xml
+- title: IRC Channels
+ subfolderitems:
+ - name: monero
+ url: irc://chat.freenode.net/#monero
+ - name: monero-dev
+ url: irc://chat.freenode.net/#monero-dev
+ - name: monero-markets
+ url: irc://chat.freenode.net/#monero-markets
+ - name: monero-pools
+ url: irc://chat.freenode.net/#monero-pools
+ - name: monero-community
+ url: irc://chat.freenode.net/#monero-community
+ - name: monero-translations
+ url: irc://chat.freenode.net/#monero-translations
+ - name: monero-hardware
+ url: irc://chat.freenode.net/#monero-hardware
+- title: Community
+ subfolderitems:
+ - name: Reddit
+ url: https://reddit.com/r/monero
+ - name: Stack Exchange
+ url: https://monero.stackexchange.com/
+ - name: BitcoinTalk Thread
+ url: https://bitcointalk.org/index.php?topic=583449.0
+ - name: Mattermost Chat
+ url: https://mattermost.getmonero.org/
+ - name: Telegram Chat
+ url: https://telegram.me/bitmonero
+- title: The Monero Project
+ subfolderitems:
+ - name: Open Alias
+ url: https://openalias.org/
+ - name: Kovri
+ url: https://getkovri.org/
+ - name: Monero Research Lab
+ url: resources/research-lab/
+ - name: Monero Press Kit
+ url: press-kit
\ No newline at end of file
diff --git a/_data/lang/en/footer-2.yml b/_data/lang/en/footer-2.yml
new file mode 100644
index 0000000000000000000000000000000000000000..5f750fc1f94657807595f2addee22012b1903352
--- /dev/null
+++ b/_data/lang/en/footer-2.yml
@@ -0,0 +1,6 @@
+- name: Legal
+ url: legal
+- name: Source Code
+ url: https://github.com/monero-project
+- name: Technical Specs
+ url: technical-specs/
\ No newline at end of file
diff --git a/_data/lang/en/navigation.yml b/_data/lang/en/navigation.yml
new file mode 100644
index 0000000000000000000000000000000000000000..18681a7e206611b252688f01805c56596269abf6
--- /dev/null
+++ b/_data/lang/en/navigation.yml
@@ -0,0 +1,54 @@
+- title: Get Started
+ subfolderitems:
+ - page: What is Monero?
+ url: get-started/what-is-monero
+ - page: Using
+ url: get-started/using
+ - page: Accepting
+ url: get-started/accepting
+ - page: Contributing
+ url: get-started/contributing
+ - page: Mining
+ url: get-started/mining
+ - page: FAQ
+ url: get-started/faq
+- title: Downloads
+ url: downloads/
+- title: Recent News
+ subfolderitems:
+ - page: All Posts
+ url: blog
+ - page: Missives
+ url: blog/tags/monero%20missives.html
+ - page: Meeting Logs
+ url: blog/tags/dev%20diaries.html
+ - page: Releases
+ url: blog/tags/releases.html
+- title: Community
+ subfolderitems:
+ - page: Team
+ url: community/team
+ - page: Hangouts
+ url: community/hangouts
+ - page: Events
+ url: community/events
+ - page: Sponsorships
+ url: community/sponsorships
+ - page: Merchants
+ url: community/merchants
+- title: Resources
+ subfolderitems:
+ - page: About
+ url: resources/about
+ - page: Roadmap
+ url: resources/roadmap
+ - page: Research Lab
+ url: resources/research-lab
+ - page: Moneropedia
+ url: resources/moneropedia
+ - page: User Guides
+ url: resources/user-guides
+ - page: Developer Guides
+ url: resources/developer-guides
+ - page: Technical Specs
+ url: technical-specs
\ No newline at end of file
diff --git a/_data/roadmap.yml b/_data/lang/en/roadmap.yml
similarity index 100%
rename from _data/roadmap.yml
rename to _data/lang/en/roadmap.yml
diff --git a/_data/lang/es/footer-1.yml b/_data/lang/es/footer-1.yml
new file mode 100644
index 0000000000000000000000000000000000000000..2d0408f8e0f920fc623ae00cbe0c185bf9c57486
--- /dev/null
+++ b/_data/lang/es/footer-1.yml
@@ -0,0 +1,50 @@
+- title: Resources
+ subfolderitems:
+ - name: About Monero
+ url: resources/about/
+ - name: Moneropedia
+ url: resources/moneropedia/
+ - name: Developer Guides
+ url: resources/developer-guides/
+ - name: User Guides
+ url: resources/user-guides/
+ - name: RSS Feed
+ url: https://getmonero.org/feed.xml
+- title: IRC Channels
+ subfolderitems:
+ - name: monero
+ url: irc://chat.freenode.net/#monero
+ - name: monero-dev
+ url: irc://chat.freenode.net/#monero-dev
+ - name: monero-markets
+ url: irc://chat.freenode.net/#monero-markets
+ - name: monero-pools
+ url: irc://chat.freenode.net/#monero-pools
+ - name: monero-community
+ url: irc://chat.freenode.net/#monero-community
+ - name: monero-translations
+ url: irc://chat.freenode.net/#monero-translations
+ - name: monero-hardware
+ url: irc://chat.freenode.net/#monero-hardware
+- title: Community
+ subfolderitems:
+ - name: Reddit
+ url: https://reddit.com/r/monero
+ - name: Stack Exchange
+ url: https://monero.stackexchange.com/
+ - name: BitcoinTalk Thread
+ url: https://bitcointalk.org/index.php?topic=583449.0
+ - name: Mattermost Chat
+ url: https://mattermost.getmonero.org/
+ - name: Telegram Chat
+ url: https://telegram.me/bitmonero
+- title: The Monero Project
+ subfolderitems:
+ - name: Open Alias
+ url: https://openalias.org/
+ - name: Kovri
+ url: https://getkovri.org/
+ - name: Monero Research Lab
+ url: resources/research-lab/
+ - name: Monero Press Kit
+ url: press-kit
\ No newline at end of file
diff --git a/_data/lang/es/footer-2.yml b/_data/lang/es/footer-2.yml
new file mode 100644
index 0000000000000000000000000000000000000000..5f750fc1f94657807595f2addee22012b1903352
--- /dev/null
+++ b/_data/lang/es/footer-2.yml
@@ -0,0 +1,6 @@
+- name: Legal
+ url: legal
+- name: Source Code
+ url: https://github.com/monero-project
+- name: Technical Specs
+ url: technical-specs/
\ No newline at end of file
diff --git a/_data/lang/es/navigation.yml b/_data/lang/es/navigation.yml
new file mode 100644
index 0000000000000000000000000000000000000000..a37f92f30181fd35703f241a5b4d679280ebac4a
--- /dev/null
+++ b/_data/lang/es/navigation.yml
@@ -0,0 +1,54 @@
+- title: Inicio
+ subfolderitems:
+ - page: ¿Qué es Monero?
+ url: get-started/what-is-monero
+ - page: Usar Monero
+ url: get-started/using
+ - page: Aceptar Monero
+ url: get-started/accepting
+ - page: Contribuir a Monero
+ url: get-started/contributing
+ - page: Minar Monero
+ url: get-started/mining
+ - page: FAQ
+ url: get-started/faq
+- title: Descargas
+ url: downloads
+- title: Noticias
+ subfolderitems:
+ - page: Todas publicaciones
+ url: blog
+ - page: Misivas
+ url: blog/tags/monero%20missives.html
+ - page: Transcripciones de reuniones
+ url: blog/tags/dev%20diaries.html
+ - page: Lanzamientos
+ url: blog/tags/releases.html
+- title: Comunidad
+ subfolderitems:
+ - page: Equipo
+ url: community/team
+ - page: Canales de comunicación
+ url: community/hangouts
+ - page: Eventos
+ url: community/events
+ - page: Patrocinios
+ url: community/sponsorships
+ - page: Comerciantes
+ url: community/merchants
+- title: Recursos
+ subfolderitems:
+ - page: Sobre Monero
+ url: resources/about
+ - page: Hoja de ruta
+ url: resources/roadmap
+ - page: Laboratorio de investigación
+ url: resources/research-lab
+ - page: Moneropedia
+ url: resources/moneropedia
+ - page: GuÃas de usuario
+ url: resources/user-guides
+ - page: GuÃas de desarrolladores
+ url: resources/developer-guides
+ - page: Especificaciones técnicas
+ url: technical-specs
\ No newline at end of file
diff --git a/_data/lang/es/roadmap.yml b/_data/lang/es/roadmap.yml
new file mode 100644
index 0000000000000000000000000000000000000000..4852b209e32cfa043346b2fd0022564112af61fa
--- /dev/null
+++ b/_data/lang/es/roadmap.yml
@@ -0,0 +1,109 @@
+- year: 2014
+ accomplishments:
+ - name: Launched on Bitcointalk
+ date: 2014-04-18
+ status: completed
+ - name: Renamed from Bitmonero to Monero
+ date: 2014-04-23
+ status: completed
+ - name: Recovered from a spam attack
+ date: 2014-09-04
+ status: completed
+ - name: Monero Research Lab Papers 1 and 2 published
+ date: 2014-09-12
+ status: completed
+ - name: Monero Research Lab Paper 3 published
+ date: 2014-09-25
+ status: completed
+ - name: 0.8.8.6 released
+ date: 2014-12-08
+ status: completed
+- year: 2015
+ accomplishments:
+ - name: Monero Research Lab Paper 4 published
+ date: 2015-01-26
+ status: completed
+- year: 2016
+ accomplishments:
+ - name: 0.9.0 Hydrogen Helix released
+ date: 2016-01-01
+ status: completed
+ - name: Monero Research Lab Paper 5 published
+ date: 2016-02-10
+ status: completed
+ - name: Hardfork to require minimum ringsize of 3 on all transactions
+ date: 2016-03-22
+ status: completed
+ - name: 0.10.0 Wolfram Warptangent released
+ date: 2016-09-18
+ status: completed
+ - name: Hardfork to split coinbase into denominations
+ date: 2016-09-21
+ status: completed
+ - name: 0.10.1 Wolfram Warptangent released
+ date: 2016-12-14
+ status: completed
+ - name: Official GUI Beta 1 released
+ date: 2016-12-22
+ status: completed
+- year: 2017
+ accomplishments:
+ - name: Hardfork to enable RingCT transactions
+ date: 2017-01-05
+ status: completed
+ - name: 0.10.2 released; critical vulnerability patched
+ date: 2017-02-22
+ status: completed
+ - name: 0.10.3.1 Wolfram Warptangent released
+ date: 2017-03-27
+ status: completed
+ - name: Hardfork to adjust minimum blocksize and dynamic fee algorithm
+ date: 2017-04-15
+ status: completed
+ - name: Website redesigned
+ date: 2017-07-04
+ status: completed
+ - name: 0.11.0.0 Helium Hydra released
+ date: 2017-09-07
+ status: completed
+ - name: Fluffy blocks
+ date: 2017-09-07
+ status: completed
+ - name: GUI out of beta
+ date: 2017-09-10
+ status: completed
+ - name: Hardfork to increase minimum ringsize to 5 and require RingCT transactions
+ date: 2017-09-15
+ status: completed
+ - name: 0MQ/ZeroMQ
+ date: September, 2017
+ status: completed
+ - name: Fluffy blocks
+ date:
+ status: ongoing
+ - name: GUI port to android
+ date:
+ status: ongoing
+ - name: Forum Funding System redesign
+ date:
+ status: ongoing
+ - name: Subaddresses
+ date:
+ status: ongoing
+ - name: Multi-signatures (multisig)
+ date:
+ status: ongoing
+ - name: Kovri alpha release
+ date:
+ status: upcoming
+- year: 2018
+ accomplishments:
+ - name: Additional MRL research papers
+ date:
+ status: upcoming
+ - name: Second-layer solutions for speed and scalability
+ date:
+ status: upcoming
+ - name: More efficient range proofs for RingCT to reduce transaction sizes
+ date:
+ status: upcoming
diff --git a/_data/lang/template/footer-1.yml b/_data/lang/template/footer-1.yml
new file mode 100644
index 0000000000000000000000000000000000000000..2d0408f8e0f920fc623ae00cbe0c185bf9c57486
--- /dev/null
+++ b/_data/lang/template/footer-1.yml
@@ -0,0 +1,50 @@
+- title: Resources
+ subfolderitems:
+ - name: About Monero
+ url: resources/about/
+ - name: Moneropedia
+ url: resources/moneropedia/
+ - name: Developer Guides
+ url: resources/developer-guides/
+ - name: User Guides
+ url: resources/user-guides/
+ - name: RSS Feed
+ url: https://getmonero.org/feed.xml
+- title: IRC Channels
+ subfolderitems:
+ - name: monero
+ url: irc://chat.freenode.net/#monero
+ - name: monero-dev
+ url: irc://chat.freenode.net/#monero-dev
+ - name: monero-markets
+ url: irc://chat.freenode.net/#monero-markets
+ - name: monero-pools
+ url: irc://chat.freenode.net/#monero-pools
+ - name: monero-community
+ url: irc://chat.freenode.net/#monero-community
+ - name: monero-translations
+ url: irc://chat.freenode.net/#monero-translations
+ - name: monero-hardware
+ url: irc://chat.freenode.net/#monero-hardware
+- title: Community
+ subfolderitems:
+ - name: Reddit
+ url: https://reddit.com/r/monero
+ - name: Stack Exchange
+ url: https://monero.stackexchange.com/
+ - name: BitcoinTalk Thread
+ url: https://bitcointalk.org/index.php?topic=583449.0
+ - name: Mattermost Chat
+ url: https://mattermost.getmonero.org/
+ - name: Telegram Chat
+ url: https://telegram.me/bitmonero
+- title: The Monero Project
+ subfolderitems:
+ - name: Open Alias
+ url: https://openalias.org/
+ - name: Kovri
+ url: https://getkovri.org/
+ - name: Monero Research Lab
+ url: resources/research-lab/
+ - name: Monero Press Kit
+ url: press-kit
\ No newline at end of file
diff --git a/_data/lang/template/footer-2.yml b/_data/lang/template/footer-2.yml
new file mode 100644
index 0000000000000000000000000000000000000000..5f750fc1f94657807595f2addee22012b1903352
--- /dev/null
+++ b/_data/lang/template/footer-2.yml
@@ -0,0 +1,6 @@
+- name: Legal
+ url: legal
+- name: Source Code
+ url: https://github.com/monero-project
+- name: Technical Specs
+ url: technical-specs/
\ No newline at end of file
diff --git a/_data/lang/template/navigation.yml b/_data/lang/template/navigation.yml
new file mode 100644
index 0000000000000000000000000000000000000000..18681a7e206611b252688f01805c56596269abf6
--- /dev/null
+++ b/_data/lang/template/navigation.yml
@@ -0,0 +1,54 @@
+- title: Get Started
+ subfolderitems:
+ - page: What is Monero?
+ url: get-started/what-is-monero
+ - page: Using
+ url: get-started/using
+ - page: Accepting
+ url: get-started/accepting
+ - page: Contributing
+ url: get-started/contributing
+ - page: Mining
+ url: get-started/mining
+ - page: FAQ
+ url: get-started/faq
+- title: Downloads
+ url: downloads/
+- title: Recent News
+ subfolderitems:
+ - page: All Posts
+ url: blog
+ - page: Missives
+ url: blog/tags/monero%20missives.html
+ - page: Meeting Logs
+ url: blog/tags/dev%20diaries.html
+ - page: Releases
+ url: blog/tags/releases.html
+- title: Community
+ subfolderitems:
+ - page: Team
+ url: community/team
+ - page: Hangouts
+ url: community/hangouts
+ - page: Events
+ url: community/events
+ - page: Sponsorships
+ url: community/sponsorships
+ - page: Merchants
+ url: community/merchants
+- title: Resources
+ subfolderitems:
+ - page: About
+ url: resources/about
+ - page: Roadmap
+ url: resources/roadmap
+ - page: Research Lab
+ url: resources/research-lab
+ - page: Moneropedia
+ url: resources/moneropedia
+ - page: User Guides
+ url: resources/user-guides
+ - page: Developer Guides
+ url: resources/developer-guides
+ - page: Technical Specs
+ url: technical-specs
\ No newline at end of file
diff --git a/_data/lang/template/roadmap.yml b/_data/lang/template/roadmap.yml
new file mode 100644
index 0000000000000000000000000000000000000000..4852b209e32cfa043346b2fd0022564112af61fa
--- /dev/null
+++ b/_data/lang/template/roadmap.yml
@@ -0,0 +1,109 @@
+- year: 2014
+ accomplishments:
+ - name: Launched on Bitcointalk
+ date: 2014-04-18
+ status: completed
+ - name: Renamed from Bitmonero to Monero
+ date: 2014-04-23
+ status: completed
+ - name: Recovered from a spam attack
+ date: 2014-09-04
+ status: completed
+ - name: Monero Research Lab Papers 1 and 2 published
+ date: 2014-09-12
+ status: completed
+ - name: Monero Research Lab Paper 3 published
+ date: 2014-09-25
+ status: completed
+ - name: 0.8.8.6 released
+ date: 2014-12-08
+ status: completed
+- year: 2015
+ accomplishments:
+ - name: Monero Research Lab Paper 4 published
+ date: 2015-01-26
+ status: completed
+- year: 2016
+ accomplishments:
+ - name: 0.9.0 Hydrogen Helix released
+ date: 2016-01-01
+ status: completed
+ - name: Monero Research Lab Paper 5 published
+ date: 2016-02-10
+ status: completed
+ - name: Hardfork to require minimum ringsize of 3 on all transactions
+ date: 2016-03-22
+ status: completed
+ - name: 0.10.0 Wolfram Warptangent released
+ date: 2016-09-18
+ status: completed
+ - name: Hardfork to split coinbase into denominations
+ date: 2016-09-21
+ status: completed
+ - name: 0.10.1 Wolfram Warptangent released
+ date: 2016-12-14
+ status: completed
+ - name: Official GUI Beta 1 released
+ date: 2016-12-22
+ status: completed
+- year: 2017
+ accomplishments:
+ - name: Hardfork to enable RingCT transactions
+ date: 2017-01-05
+ status: completed
+ - name: 0.10.2 released; critical vulnerability patched
+ date: 2017-02-22
+ status: completed
+ - name: 0.10.3.1 Wolfram Warptangent released
+ date: 2017-03-27
+ status: completed
+ - name: Hardfork to adjust minimum blocksize and dynamic fee algorithm
+ date: 2017-04-15
+ status: completed
+ - name: Website redesigned
+ date: 2017-07-04
+ status: completed
+ - name: 0.11.0.0 Helium Hydra released
+ date: 2017-09-07
+ status: completed
+ - name: Fluffy blocks
+ date: 2017-09-07
+ status: completed
+ - name: GUI out of beta
+ date: 2017-09-10
+ status: completed
+ - name: Hardfork to increase minimum ringsize to 5 and require RingCT transactions
+ date: 2017-09-15
+ status: completed
+ - name: 0MQ/ZeroMQ
+ date: September, 2017
+ status: completed
+ - name: Fluffy blocks
+ date:
+ status: ongoing
+ - name: GUI port to android
+ date:
+ status: ongoing
+ - name: Forum Funding System redesign
+ date:
+ status: ongoing
+ - name: Subaddresses
+ date:
+ status: ongoing
+ - name: Multi-signatures (multisig)
+ date:
+ status: ongoing
+ - name: Kovri alpha release
+ date:
+ status: upcoming
+- year: 2018
+ accomplishments:
+ - name: Additional MRL research papers
+ date:
+ status: upcoming
+ - name: Second-layer solutions for speed and scalability
+ date:
+ status: upcoming
+ - name: More efficient range proofs for RingCT to reduce transaction sizes
+ date:
+ status: upcoming
diff --git a/_data/merchants.yml b/_data/merchants.yml
index 402f997ae3aa9834e776ff963803d71b429e0094..b4d770fdf97deda8419009a9ef02acf4f5ad2c37 100644
--- a/_data/merchants.yml
+++ b/_data/merchants.yml
@@ -5,6 +5,8 @@
url: https://webchat.freenode.net?channels=%23monero-otc
- name: Alfacashier
url: https://www.alfacashier.com/
+ - name: Binance
+ url: https://www.binance.com/trade.html?symbol=XMR_BTC
- name: Bitfinex (XMRUSD, XMRBTC)
url: https://www.bitfinex.com/
- name: Bisq; decentralized exchange (previously Bitsquare)
@@ -15,12 +17,16 @@
url: https://www.bittrex.com/Market/Index?MarketName=BTC-XMR
- name: Bter
url: https://bter.com/
+ - name: ChangeNOW
+ url: https://changenow.io
- name: CoinCut (OTC)
url: https://www.coincut.com
- name: Cryptopia
url: https://www.cryptopia.co.nz/Exchange?market=XMR_BTC
- name: Evercoin
url: https://evercoin.com
+ - name: Godex
+ url: https://godex.io
- name: Kaiserex
url: https://www.kaiserex.com/
- name: Karsha
@@ -37,6 +43,8 @@
url: https://localmonero.co/
- name: Magnetic Exchange
url: https://magneticexchange.com
+ - name: MegaChange.is (P2P exchange)
+ url: https://megachange.is
- name: MoneroDirect (Euro only)
url: https://monerodirect.com
- name: Poloniex
@@ -45,6 +53,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:
@@ -86,6 +96,8 @@
url: https://github.com/PsychicCat/monero-php
- name: MoneroPy (Python)
url: https://github.com/bigreddmachine/MoneroPy
+ - name: monero-python (Python)
+ url: https://github.com/emesik/monero-python
- name: PHP-Monero (PHP)
url: https://github.com/MalMen/PHP-Monero
- name: python-monero (Python)
@@ -99,6 +111,8 @@
merchants:
- name: Atesti Data Timestamping
url: http://atesti.mooo.com:8081
+ - name: Atomox - Converter
+ url: http://atomox.net/1/XMR/USD
- name: ForkGuard Network Monitoring
url: http://forkguard.com
- name: MoneroBase Price Charts and Tools
@@ -116,12 +130,20 @@
- category: Services
id: services
merchants:
+ - name: 99Stack Hosting
+ url: https://www.99stack.com
+ - name: Abaco Hosting
+ url: https://abacohosting.com/
+ - name: Ablative Hosting
+ url: https://ablative.hosting
- name: AirVPN
url: https://airvpn.org/
- name: algoStrategic - Internet Marketing and Web Development
url: https://algostrategic.com
- name: Azur Samui - Luxury Apartment and Villa Development, Koh, Samui, Thailand
url: http://www.azursamui.com
+ - name: BunkerVPN (Ethical VPN Provider)
+ url: https://bunkervpn.com
- name: California Fintech Network
url: https://www.californiafintech.org/plans/
name: Computer Lab - React, Django, Security Consultancy in NYC
@@ -142,16 +164,32 @@
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: Gomojomarketing - Web app developers
+ url: https://www.gomojomarketing.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
- url: mailto:info@loandraw.com
+ - name: IdeaSoft - Full-cycle Software Development
+ url: https://i-deasoft.com
+ - name: Incognito Deals
+ url: https://www.incognitodeals.com
+ - name: Ink Rebels
+ url: https://ink-rebels.com
+ - name: Jeffscondos - Vacation rentals
+ url: http://jeffscondos.com/
+ - name: K9 Satisfaction - Premium dog training
+ url: http://www.k9satisfaction.com/
- name: KoDDoS.net - DDoS Protection
url: https://koddos.net
+ - name: INST.US Instagram Service
+ url: http://inst.us
- name: Marcos Aguayo - Programmer and Web Developer
url: http://marcosaguayo.com/
- name: MSvB Hardware Design (using a secure element)
url: mailto:monerodev+sitesvcs@encambio.com?subject=Monero%20Services%20Hardware%20Design%20Request
+ - name: Midwestminers - Mining equipment
+ url: https://midwestminers.com/
- name: MyMonero Web-based Wallet
url: https://mymonero.com
- name: Nerdzy Lawn Care
@@ -162,16 +200,32 @@
url: https://njal.la/
- name: Pradeep Atluri, Psychiatrist, New York
url: http://dr.mindsci.com/
+ - name: Ray Luechtefeld, PhD, Leadership & Team Coaching and Development
+ url: https://clarity.fm/rayluechtefeld
+ - name: Red/Cedar websites - digital marketing company
+ url: http://redcedarwebsites.com/
+ - name: Rohan Law - Criminal defense firm (Georgia)
+ url: http://www.rohan.law
- name: Rootbox; Simple, no non-sense hosting
url: https://rootbox.host/
- name: TheBigCoin - Spend Monero Anywhere
url: https://www.thebigcoin.io
+ - name: TorGuard - VPN, proxy and email service
+ url: https://torguard.net
- name: Tuxcon Hosting - Mail and Web Hosting
url: https://tuxcon.com
+ - name: WalletMonero - Online Wallet
+ url: https://walletmonero.com
+ - name: Web4Crypto - Website development
+ url: https://web4crypto.xyz/
+ - name: Webbdo Hosting (se)
+ url: https://www.webbdo.se/webbhotell/
- name: Web Developer - Python with Django web framework
url: http://www.voteforrodneylewis.com
- name: Web Developer - Stefanos
url: http://www.stefanosioannou.com/web-development-monero-accepted
+ - name: Whattheserver - Web hosting
+ url: https://Whattheserver.me
- name: XMR.to Monero to Bitcoin Payment Service
url: https://xmr.to/
- category: Goods
@@ -181,33 +235,87 @@
url: https://allforcrypto.com
- name: Cellphone and laptop repair online store in Sweden
url: http://www.LagaiPhone.se
+ - name: Check-coin - Online store
+ url: https://check-coin.com/
+ - name: CoinBought - Buy anything from Amazon
+ url: https://coinbought.com/
+ - name: Congrevape - e-cigarette products
+ url: https://Congrevape.com/shop
+ - name: Crypto Armory - ammunition for cryptocurrency at a competitive rate
+ url: https://www.crypto-armory.com
+ - name: Crypto Whale Clothing - Crypto themed clothing
+ url: https://cryptowhaleclothing.com
- name: CryptoMercado - coffee and snacks
url: https://www.cryptomercado.com/
- name: Cryptonic Physical Monero & Bitcoin coins
url: https://cryptonic.net
+ - name: DeepWebVPN
+ url: https://deepwebvpn.net
- name: Digital gift cards
url: https://giftoff.com/
- name: Directvoltage
url: http://directvoltage.com
+ - name: Fierce Edge
+ url: https://fierceedge.com/
- name: Fine Art from Jeanine King ~ Artwork of Home/Archtecture, Pets, Potraits, Caricatures ~ International Shipping
url: http://art2unlimited.webs.com/
+ - name: Franc Vila - Watchmaking and Jewelry
+ url: http://www.francvila.com
+ - name: Game of Cryptos
+ url: https://gameofcryptos.com/
+ - name: Giacobbe & Co. - Diamond and gemstone jewelry
+ url: https://giacobbeandco.com/
+ - name: Hammock Universe
+ url: https://www.hammockuniverseusa.com/
- name: Handcrafted goods
url: https://mychain.store/
+ - name: Hodlmonkey - Crypto T-Shirts
+ url: https://hodlmonkey.com/
- name: InvestmentArt
url: http://investmentart.org/
+ - name: Kidsweet - All-Natural Zero-Calorie Sweetener
+ url: https://www.kidsweet.com/
+ - name: Loja do Cabelo - Hair extensions (pt)
+ url: https://lojadocabelo.com/
+ - name: Max5dollars - Online shop
+ url: https://www.max5dollars.com/
+ - name: MetaDope - Patch & lapel pin manufacturing services
+ url: https://metado.pe/
- name: Mushroom cultures, mushroom growing supplies, seeds
url: https://www.vesp.co/Fungible
+ - name: One Stop NY
+ url: http://onestopny.com
+ - name: Project Coral Reef Store
+ url: http://www.projectcoralreef.com/all-stores
+ - name: Renjer Snacks
+ url: http://www.renjer.ky
+ - name: Reservoir Mugs - Roasted gourmet coffees, mugs, t-shirts
+ url: https://reservoirmugs.com/
+ - name: Revolution Microelectronics
+ url: https://revolutionmicro.com/
+ - 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
url: https://synntechgaming.com
+ - name: Stamp Monero
+ url: https://stampmonero.com/
+ - name: The Kava Society - Kava tea
+ url: https://kavasociety.nz/
+ - name: Toys4sex - Adult toys
+ url: https://toys4sex.com.au/
- name: Xusah Boutique
url: https://xusah.boutique/
+ - name: Judit Mátyus - Jewelry
+ url: https://www.juditmatyus.com/
- category: Entertainment
id: entertainment
merchants:
- name: Crypto Games
url: https://www.crypto-games.net/
+ - name: CryptoLotto
+ url: https://cryptolotto.info
- name: MoneroDice
url: https://monerodice.net
- name: SafeDice
diff --git a/_data/tags.yml b/_data/tags.yml
index de837b447fcc99de119309f8e834e3d77a79932d..3d9e4f4a5dffaa92ebd4b3d51c58e8188415edab 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/_strings_en.yml b/_i18n/en.yml
similarity index 76%
rename from _strings_en.yml
rename to _i18n/en.yml
index 5e065e8cd36e6d88493baded03fb15aa59763851..610e1035b24310fcd8afee1eb854c8e5ab15b5b2 100644
--- a/_strings_en.yml
+++ b/_i18n/en.yml
@@ -1,97 +1,96 @@
-global:
- date: '%Y/%m/%d'
- monero: Monero
- getting_started: Getting Started
- copyright: Copyright
- monero_project: The Monero Project
- sitename: getmonero.org, The Monero Project
- wiki: Moneropedia
- tags: Articles By Tag
- wikimeta: on Moneropedia, the open encyclopedia of Monero knowledge
- tagsmeta: All Monero blog articles that are tagged
- titlemeta: on the home of Monero, a digital currency that is secure, private, and untraceable
- terms: Terms
- privacy: Privacy
- copyright: Copyright
- edit: Edit This Page
-menu:
- forum: Forum
- blog: Blog
- knowledge_base: Knowledge Base
- community: Community
- bitcointalk: Bitcointalk Thread
- reddit: Reddit
- allblog: All Blog Posts
- devdiaries: Dev Diaries
- missives: Monero Missives
- uncategorised: Uncategorized
- choose: How to Choose a Monero Client
- running: How to Run a Monero Node
- donations: Donating and Sponsorships
- contribute: Contributing to Monero
- downloads: All Monero Downloads
- github: GitHub
- merchants: Merchants and Services Directory
- accepting: Accepting Monero Payments
- about: About Monero
- people: The People Behind Monero
- userguides: User Guides
- developerguides: Developer Guides
- vrp: Vulnerability Response Process
- goals: Design & Development Goals
- openalias: The OpenAlias Project
- lab: Monero Research Lab
- alternative: Alternative Clients
- projects: External Projects
- stackexchange: StackExchange Q&A
- slack: Slack Chat
- telegram: Telegram Chat
- irc: IRC on Freenode
- irc-general: "#monero (General)"
- irc-development: "#monero-dev (Development)"
- irc-trading: "#monero-otc (OTC Trading)"
- irc-markets: "#monero-markets (Markets)"
- irc-mining: "#monero-pools (Mining)"
-index:
- page_title: "Monero - secure, private, untraceable"
- what_is_1: What is
- what_is_2: " ?"
- what_is_orange_block: "Monero is a secure, private, untraceable currency that is open-source and freely available for anyone to use."
- what_is_text_block_1: "With Monero, you are your own bank; You have complete control over your funds. With Monero, your accounts and transactions are kept private."
- what_is_text_block_2: "Want to find out more? An overview of Monero's main features are below. If you'd like to try Monero for yourself the"
- what_is_text_block_3: "Getting Started"
- what_is_text_block_4: "section is an excellent launching point."
- news: News
- the_latest: The Latest
- private: Private
- secure: Secure
- untraceable: Untraceable
- private_text: "Monero uses hidden amounts, origins and destinations of @transactions. This means that nobody knows how much you're sending in a transaction except you. This ensures that your purchases and other transfers remain private by default."
- untraceable_text: "By taking advantage of @ring-signatures, Monero allows you to send and receive funds privately. Even though your transactions are publicly verifiable on the @blockchain, transactions use digital signatures that specify a group of signers such that the person verifying can’t tell which person actually produced the signature. Because it's ambiguous which funds have been spent, your transaction remains private and cannot be traced back to you."
- secure_text: "Monero uses a distributed peer-to-peer @consensus network and every transaction is cryptographically signed. Your coins are safely stored on the @blockchain and can be restored at any time with the use of a 25 word @mnemonic-seed on any computer with the Monero software. Wallet files are encrypted on disk and locked with a passphrase, rendering them useless if stolen."
- how_do_i_1: "How do I "
- how_do_i_2: " ?"
- get_started: get started
- get_started_1: "The fastest way to start using Monero is with a web @account manager such as "
- mymonero: "MyMonero"
- get_started_2: "."
- get_started_3: "Alternatively, if you would like to run a [full Monero node](/getting-started/running) you can download the client and a kick-starter @blockchain (to bring your local client up to speed) using the download link on the right."
- where_can_i: Where can I
- download_1: download
- download_2: " ?"
- different_os: "Need it for a different operating system?"
- all_downloads: View all available downloads here
- c_download: Download
- monero_for: Monero for
- latest_blockchain: Latest @Blockchain
-blog:
- title_1: All
- title_2: Blog
- title_3: Posts
- tagged: Tagged under
- author: Posted by
- date: Posted at
- forum: Click here to join the discussion for this entry on the Monero Forum
-tags:
- all: Articles by Tag
- notags: There are no posts for this tag.
+langs:
+ en: English
+ es: Español
+
+global:
+ date: '%Y/%m/%d'
+ monero: Monero
+ getting_started: Getting Started
+ copyright: Copyright
+ monero_project: The Monero Project
+ sitename: getmonero.org, The Monero Project
+ wiki: Moneropedia
+ tags: Articles By Tag
+ wikimeta: on Moneropedia, the open encyclopedia of Monero knowledge
+ tagsmeta: All Monero blog articles that are tagged
+ titlemeta: on the home of Monero, a digital currency that is secure, private, and untraceable
+ terms: Terms
+ privacy: Privacy
+ copyright: Copyright
+ edit: Edit This Page
+ untranslated: This page is not yet translated. If you would like to help translate it, please see the
+titles:
+ index: Home
+ whatismonero: What is Monero (XMR)?
+ using: Using Monero
+ accepting: Accepting Monero
+ contributing: Improving Monero
+ mining: Mining Monero
+ faq: FAQ
+ downloads: Downloads
+ allposts: All Blog Posts
+ team: Monero Team
+ hangouts: Hangouts
+ events: Events
+ sponsorships: Sponsorships
+ merchants: Merchants & Services
+ about: About Monero
+ roadmap: Roadmap
+ researchlab: Monero Research Lab
+ moneropedia: Moneropedia
+ userguides: User Guides
+ developerguides: Developer Guides
+ technicalspecs: Technical Specs
+ themoneroproject: The Monero Project
+ presskit: Monero Press Kit
+ legal: Legal
+ ffs: Forum Funding System
+ ffs-cp: Completed Proposals
+ ffs-fr: Funding Required
+ ffs-ideas: Ideas
+ ffs-ot: Open Tasks
+ ffs-wip: Work in Progress
+ blogbytag: Blog by Tag
+index:
+ page_title: "Monero - secure, private, untraceable"
+ what_is_1: What is
+ what_is_2: " ?"
+ what_is_orange_block: "Monero is a secure, private, untraceable currency that is open-source and freely available for anyone to use."
+ what_is_text_block_1: "With Monero, you are your own bank; You have complete control over your funds. With Monero, your accounts and transactions are kept private."
+ what_is_text_block_2: "Want to find out more? An overview of Monero's main features are below. If you'd like to try Monero for yourself the"
+ what_is_text_block_3: "Getting Started"
+ what_is_text_block_4: "section is an excellent launching point."
+ news: News
+ the_latest: The Latest
+ private: Private
+ secure: Secure
+ untraceable: Untraceable
+ private_text: "Monero uses hidden amounts, origins and destinations of @transactions. This means that nobody knows how much you're sending in a transaction except you. This ensures that your purchases and other transfers remain private by default."
+ untraceable_text: "By taking advantage of @ring-signatures, Monero allows you to send and receive funds privately. Even though your transactions are publicly verifiable on the @blockchain, transactions use digital signatures that specify a group of signers such that the person verifying can’t tell which person actually produced the signature. Because it's ambiguous which funds have been spent, your transaction remains private and cannot be traced back to you."
+ secure_text: "Monero uses a distributed peer-to-peer @consensus network and every transaction is cryptographically signed. Your coins are safely stored on the @blockchain and can be restored at any time with the use of a 25 word @mnemonic-seed on any computer with the Monero software. Wallet files are encrypted on disk and locked with a passphrase, rendering them useless if stolen."
+ how_do_i_1: "How do I "
+ how_do_i_2: " ?"
+ get_started: get started
+ get_started_1: "The fastest way to start using Monero is with a web @account manager such as "
+ mymonero: "MyMonero"
+ get_started_2: "."
+ get_started_3: "Alternatively, if you would like to run a [full Monero node](/getting-started/running) you can download the client and a kick-starter @blockchain (to bring your local client up to speed) using the download link on the right."
+ where_can_i: Where can I
+ download_1: download
+ download_2: " ?"
+ different_os: "Need it for a different operating system?"
+ all_downloads: View all available downloads here
+ c_download: Download
+ monero_for: Monero for
+ latest_blockchain: Latest @Blockchain
+blog:
+ title_1: All
+ title_2: Blog
+ title_3: Posts
+ tagged: Tagged under
+ author: Posted by
+ date: Posted at
+ forum: Click here to join the discussion for this entry on the Monero Forum
+tags:
+ all: Articles by Tag
+ notags: There are no posts for this tag.
diff --git a/_i18n/en/community/events.md b/_i18n/en/community/events.md
new file mode 100644
index 0000000000000000000000000000000000000000..f24325d366186ac3fabff2600a6e1eb248b8b7fc
--- /dev/null
+++ b/_i18n/en/community/events.md
@@ -0,0 +1,27 @@
+<div markdown="1" class="text-center container description">
+Monero people are always down to get together and have a good time. Check below to see Monero-related events happening in your area.
+</div>
+
+{% for toplevel in site.data.events %}
+
+<div class="events">
+ <div class="container full col-xs-12">
+ <div class="info-block text-adapt">
+ <div class="row">
+ <div class="col-xs-12">
+ <h2>{{toplevel.event}}</h2>
+ <h3>Where</h3>
+ <p>{{toplevel.where}}</p>
+ <h3>When</h3>
+ <p>{{toplevel.when}}</p>
+ <h3>Description</h3>
+ <p>{{toplevel.description}}</p>
+ <h3>Link</h3>
+ <a>{{toplevel.link}}</a>
+ </div>
+ </div>
+ </div>
+ </div>
+</div>
+
+{%endfor%}
\ No newline at end of file
diff --git a/_i18n/en/community/hangouts.md b/_i18n/en/community/hangouts.md
new file mode 100644
index 0000000000000000000000000000000000000000..bea95be87f38d979f0f057d50d4860bafc11b5d1
--- /dev/null
+++ b/_i18n/en/community/hangouts.md
@@ -0,0 +1,96 @@
+<div markdown="1" class="text-center container description">
+The Monero community is diverse and varied. We come from all over, but we definitely have some places we like to hang out together. You'll find most of them below. Join us!
+</div>
+
+<div class="hangouts">
+ <section class="container">
+ <ul class="row center-xs">
+ <li>
+ <a href="https://twitter.com/monerocurrency" target="_blank" rel="noreferrer noopener"><div class="social-icon twitter"></div></a>
+ </li>
+ <li>
+ <a href="https://reddit.com/r/monero" target="_blank" rel="noreferrer noopener"><div class="social-icon reddit"></div></a>
+ </li>
+ <li>
+ <a href="https://www.facebook.com/monerocurrency/" target="_blank" rel="noreferrer noopener"><div class="social-icon facebook"></div></a>
+ </li>
+ <li>
+ <a href="https://github.com/monero-project" target="_blank" rel="noreferrer noopener"><div class="social-icon github"></div></a>
+ </li>
+ </ul>
+ </section>
+
+ <section class="container">
+ <div class="row">
+ <!-- left two-thirds block-->
+ <div class="left two-thirds col-lg-8 col-md-8 col-sm-12 col-xs-12">
+ <div class="col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Workgroup Resources</h2>
+ </div>
+ </div>
+ <div class="row center-xs">
+ <p>In an effort to support organic workgroups, Monero has several resources that the community can use to meet and plan projects. Mattermost even has relays into the most popular Monero-related IRC channels.</p>
+ </div>
+ <div class="row relays around-xs">
+ <div class="col-md-4 col-sm-4 col-xs-4">
+ <p><a href="https://monero.slack.com/" class="btn-link btn-fixed">Slack</a></p>
+ </div>
+ <div class="col-md-4 col-sm-4 col-xs-4">
+ <p><a href="https://mattermost.getmonero.org/" class="btn-link btn-fixed">Mattermost</a></p>
+ </div>
+ <div class="col-md-4 col-sm-4 col-xs-4">
+ <p><a href="https://taiga.getmonero.org/" class="btn-link btn-fixed">Taiga</a></p>
+ </div>
+ </div>
+ </div>
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>IRC Channels</h2>
+ </div>
+ </div>
+ <div class="row start-xs">
+ <p>The Monero community utilizes a lot of IRC channels that each serve different purposes. Some to work, and some just to hang out. You'll find the more popular ones below.</p>
+ </div>
+ <div class="row irc">
+ {% for channel in site.data.irc %}
+ <div class="col-md-4 col-xs-12">
+ <a href="irc://chat.freenode.net/#{{ channel.channel }}">#{{ channel.channel }}</a>
+ <p>{{ channel.description }}</p>
+ </div>
+ {% endfor %}
+ </div>
+ </div>
+ </div>
+ </div>
+ <!-- end left two-thirds block-->
+
+ <!-- right one-third block-->
+ <div class="right one-third col-lg-4 col-md-4 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col"><h2>Stack Exchange</h2></div>
+ </div>
+ <div class="row start-xs">
+ <p>The Monero Stack Exchange is a quick and easy way to ask questions and get answers. Below you'll find some high quality question/answer pairs to some frequently asked questions.</p>
+ </div>
+ <div class="row start-xs sequestions">
+ <a href="https://monero.stackexchange.com/questions/4277/why-does-monero-have-higher-transaction-fees-than-bitcoin">Why does monero have higher transaction fees than bitcoin?</a>
+ <a href="https://monero.stackexchange.com/questions/4335/what-does-moneros-scaling-roadmap-look-like">What does Monero's scaling roadmap look like?</a>
+ <a href="https://monero.stackexchange.com/questions/4302/what-cryptography-primitives-concepts-other-than-the-basic-ones-does-monero-us">What cryptography primitives/concepts, other than the basic ones, does Monero use?</a>
+ <a href="https://monero.stackexchange.com/questions/4242/how-to-extract-data-from-local-blockchain">How to extract data from local blockchain?</a>
+ <a href="https://monero.stackexchange.com/questions/4302/what-cryptography-primitives-concepts-other-than-the-basic-ones-does-monero-us">Hiding TCP traffic for Monero miners?</a>
+ </div>
+ <div class="row center-xs">
+ <p><a href="https://monero.stackexchange.com" class="btn-link btn-auto">Visit Stack Exchange</a></p>
+ </div>
+ </div>
+ </div>
+ <!-- end right one-third block-->
+ </div>
+ </section>
+
+</div>
diff --git a/_i18n/en/community/merchants.md b/_i18n/en/community/merchants.md
new file mode 100644
index 0000000000000000000000000000000000000000..07047110f71db99dc0d80302fa273c7d1a5da56d
--- /dev/null
+++ b/_i18n/en/community/merchants.md
@@ -0,0 +1,26 @@
+<div markdown="1" class="text-center container description">
+Merchants of all kinds have come to value the financial privacy that Monero brings. Below is a list of the merchants that we know of that currently accept Monero for their goods and services. If a company no longer accepts Monero or you would like your business to be listed, please [open a GitHub issue and let us know](https://github.com/monero-project/monero-site/issues).
+</div>
+<div class="merchants">
+{% for toplevel in site.data.merchants %}
+<div class="container full" id="{{toplevel.id}}">
+ <div class="info-block">
+ <h2>{{toplevel.category}}</h2>
+ <div class="row">
+ {% assign sortedMerchants = toplevel.merchants | sort: 'name' %}
+ {% for merchants in sortedMerchants %}
+ <div class="col-md-4 col-sm-6 col-xs-12">
+ <a href="{{merchants.url}}">{{merchants.name}}</a>
+ </div>
+ {% endfor %}
+ </div>
+ </div>
+</div>
+{%endfor%}
+
+
+</div>
+
+<div markdown="1" class="text-center container description">
+*Please note: these links are being provided as a convenience and for informational purposes only; they do not constitute an endorsement by the Monero community of any products, services or opinions of the corporations or organizations or individuals listed. The Monero community bears no responsibility for the accuracy, legality, or content of these external sites. Contact the external site for answers to questions regarding its content. As always, caveat emptor ("buyer beware"); you are responsible for doing your own research. Always use judgement when making online purchases.*
+</div>
diff --git a/_i18n/en/community/sponsorships.md b/_i18n/en/community/sponsorships.md
new file mode 100644
index 0000000000000000000000000000000000000000..e742f5a16255077538ae3b1e6dfd6e1c2413db35
--- /dev/null
+++ b/_i18n/en/community/sponsorships.md
@@ -0,0 +1,96 @@
+<div markdown="1" class="text-center container description">
+The following businesses have supported the Monero Project in its goal to bring financial privacy to the world. We couldn't be more grateful for their contributions. If you would like to sponsor the Monero Project and be listed on this page, please send an email to dev@getmonero.org.
+</div>
+
+<div>
+ <section class="container sponsors">
+ <div class="row">
+ <div class="left one-third no-pad-sm col-lg-4 col-md-4 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>My Monero</h2>
+ <a href="https://mymonero.com/#/" target="_blank" rel="noreferrer noopener"><img src="/img/mymonero.png"></a>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="center one-third no-pad-sm col-lg-4 col-md-4 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>JetBrains</h2>
+ <a href="http://www.jetbrains.com/"><img src="/img/jetbrains.png"></a>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="right one-third no-pad-sm col-lg-4 col-md-4 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Dome9 Security</h2>
+ <a href="https://dome9.com/"><img src="/img/dome9.png"></a>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="row">
+ <div class="left one-third no-pad-sm col-lg-4 col-md-4 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Kitware</h2>
+ <a href="https://www.kitware.com/"><img src="/img/kitware.png"></a>
+ </div>
+ </div>
+ </div>
+ </div>
+
+ <div class="center one-third no-pad-sm col-lg-4 col-md-4 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Fork Networking</h2>
+ <a href="https://www.forked.net"><img src="/img/forked_logo.png"></a>
+ </div>
+ </div>
+ </div>
+ </div>
+
+ <div class="right one-third no-pad-sm col-lg-4 col-md-4 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Araxis</h2>
+ <a href="https://www.araxis.com/"><img src="/img/araxis.png"></a>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="row">
+ <div class="left half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Navicat</h2>
+ <a href="https://www.navicat.com"><img src="/img/navicat.png"></a>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="right half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Symas</h2>
+ <a href="https://symas.com/"><img src="/img/symas.png"></a>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ </section>
+</div>
\ No newline at end of file
diff --git a/_i18n/en/community/team.md b/_i18n/en/community/team.md
new file mode 100644
index 0000000000000000000000000000000000000000..a654cb9a8d7b1469626f5314c5e0f16fd24e6722
--- /dev/null
+++ b/_i18n/en/community/team.md
@@ -0,0 +1,180 @@
+<div class="team">
+
+ <section class="container">
+ <div class="row">
+ <div class="col-xs-12">
+ <div class="tabPanel-widget">
+ <label for="tab-1" tabindex="0"></label>
+ <input id="tab-1" type="radio" name="tabs" aria-hidden="true" checked>
+ <h2>Core</h2>
+ <div class="tabPanel-content">
+ <div class="row">
+ {% for toplevel in site.data.team %}
+ {% if toplevel.area == "Core" %}
+ {% for member in toplevel.member %}
+ <div class="half col-lg-6 col-md-6 col-sm-6 col-xs-6">
+ <div class="info-block">
+ <div class="row center-xs">
+ <h3>{{member.name}}</h3>
+ </div>
+ <div class="row center-xs">
+ <p>{{member.email}}</p>
+ </div>
+ <div class="row center-xs icons">
+ {% if member.github %}
+ <a href="{{member.github}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon github"></div></a>
+ {%endif%}
+ {% if member.twitter %}
+ <a href="{{member.twitter}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon twitter"></div></a>
+ {%endif%}
+ {% if member.reddit %}
+ <a href="{{member.reddit}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon reddit"></div></a>
+ {%endif%}
+ </div>
+ </div>
+ </div>
+ {%endfor%}
+ {%endif%}
+ {%endfor%}
+ </div>
+ </div>
+ <label for="tab-2" tabindex="0"></label>
+ <input id="tab-2" type="radio" name="tabs" aria-hidden="true">
+ <h2>Developers</h2>
+ <div class="tabPanel-content">
+ <div class="container full">
+ <div class="info-block text-adapt">
+ <div class="row">
+ <div class="col-xs-12 text-adapt">
+ <p>The Monero Project has had well over 200 contributors over the life of the project. For a complete list, please see the <a href="https://www.openhub.net/p/monero/contributors">OpenHub contributors page</a>. Below you'll find some individuals that have gone above and beyond for Monero.</p>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="row">
+ {% for toplevel in site.data.team %}
+ {% if toplevel.area == "Developers" %}
+ {% for member in toplevel.member %}
+ <div class="half col-lg-6 col-md-6 col-sm-6 col-xs-6">
+ <div class="info-block">
+ <div class="row center-xs">
+ <h3>{{member.name}}</h3>
+ </div>
+ <div class="row center-xs icons">
+ {% if member.github %}
+ <a href="{{member.github}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon github"></div></a>
+ {%endif%}
+ {% if member.twitter %}
+ <a href="{{member.twitter}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon twitter"></div></a>
+ {%endif%}
+ {% if member.reddit %}
+ <a href="{{member.reddit}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon reddit"></div></a>
+ {%endif%}
+ </div>
+ </div>
+ </div>
+ {%endfor%}
+ {%endif%}
+ {%endfor%}
+ </div>
+ </div>
+ <label for="tab-3" tabindex="0"></label>
+ <input id="tab-3" type="radio" name="tabs" aria-hidden="true">
+ <h2>Community</h2>
+ <div class="tabPanel-content">
+ <div class="row">
+ {% for toplevel in site.data.team %}
+ {% if toplevel.area == "Community" %}
+ {% for member in toplevel.member %}
+ <div class="half col-lg-6 col-md-6 col-sm-6 col-xs-6">
+ <div class="info-block">
+ <div class="row center-xs">
+ <h3>{{member.name}}</h3>
+ </div>
+ <div class="row center-xs icons">
+ {% if member.github %}
+ <a href="{{member.github}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon github"></div></a>
+ {%endif%}
+ {% if member.twitter %}
+ <a href="{{member.twitter}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon twitter"></div></a>
+ {%endif%}
+ {% if member.reddit %}
+ <a href="{{member.reddit}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon reddit"></div></a>
+ {%endif%}
+ </div>
+ </div>
+ </div>
+ {%endfor%}
+ {%endif%}
+ {%endfor%}
+ </div>
+ </div>
+ <label for="tab-4" tabindex="0"></label>
+ <input id="tab-4" type="radio" name="tabs" aria-hidden="true">
+ <h2>Research Lab</h2>
+ <div class="tabPanel-content">
+ <div class="row">
+ {% for toplevel in site.data.team %}
+ {% if toplevel.area == "Monero Research Lab" %}
+ {% for member in toplevel.member %}
+ <div class="half col-lg-6 col-md-6 col-sm-12 col-xs-6">
+ <div class="info-block">
+ <div class="row center-xs">
+ <h3>{{member.name}}</h3>
+ </div>
+ <div class="row center-xs icons">
+ {% if member.github %}
+ <a href="{{member.github}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon github"></div></a>
+ {%endif%}
+ {% if member.twitter %}
+ <a href="{{member.twitter}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon twitter"></div></a>
+ {%endif%}
+ {% if member.reddit %}
+ <a href="{{member.reddit}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon reddit"></div></a>
+ {%endif%}
+ </div>
+ </div>
+ </div>
+ {%endfor%}
+ {%endif%}
+ {%endfor%}
+ </div>
+ </div>
+ <label for="tab-5" tabindex="0"></label>
+ <input id="tab-5" type="radio" name="tabs" aria-hidden="true">
+ <h2>Special Thanks</h2>
+ <div class="tabPanel-content">
+ <div class="row">
+ {% for toplevel in site.data.team %}
+ {% if toplevel.area == "Special Thanks" %}
+ {% for member in toplevel.member %}
+ <div class="half col-lg-6 col-md-6 col-sm-12 col-xs-6">
+ <div class="info-block">
+ <div class="row center-xs">
+ <h3>{{member.name}}</h3>
+ </div>
+ <div class="row center-xs icons">
+ {% if member.github %}
+ <a href="{{member.github}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon github"></div></a>
+ {%endif%}
+ {% if member.twitter %}
+ <a href="{{member.twitter}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon twitter"></div></a>
+ {%endif%}
+ {% if member.reddit %}
+ <a href="{{member.reddit}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon reddit"></div></a>
+ {%endif%}
+ </div>
+ </div>
+ </div>
+ {%endfor%}
+ {%endif%}
+ {%endfor%}
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+</section>
+
+
+</div>
\ No newline at end of file
diff --git a/_i18n/en/downloads.md b/_i18n/en/downloads.md
new file mode 100644
index 0000000000000000000000000000000000000000..7590aa6fe564e32f2fc78cac0664ea6000442363
--- /dev/null
+++ b/_i18n/en/downloads.md
@@ -0,0 +1,141 @@
+<div class="downloads">
+
+<div class="container description" markdown="1">
+
+If you need help choosing the correct application, please click [here](https://www.reddit.com/r/Monero/comments/64b5lf/what_is_the_best_monero_wallet/) for a quick answer, then select the appropriate release for your operating system below.
+Note: the SHA256 hashes are listed by the downloads for convenience, but a GPG-signed list of the hashes is at [getmonero.org/downloads/hashes.txt](https://getmonero.org/downloads/hashes.txt) and should be treated as canonical, with the signature checked against the appropriate GPG key in the source code (in /utils/gpg_keys).
+
+</div>
+<div class="container full downdropdown">
+<div class="info-block download-nav row middle-xs between-xs" id="selections">
+
+ <div class="col"><a href="#windows">Windows</a></div>
+ <div class="col"><a href="#mac">Mac</a></div>
+ <div class="col"><a href="#linux">Linux</a></div>
+ <div class="col"><a href="#arm">Arm (v7 & 8)</a></div>
+ <div class="col"><a href="#bsd">BSD</a></div>
+ <div class="col"><a href="#source">Source & Blockchain</a></div>
+ <div class="col"><a href="#mobilelight">Mobile & Light</a></div>
+ <div class="col"><a href="#hardware">Hardware</a></div>
+
+</div>
+</div>
+
+<div class="container full">
+ <div class="info-block row center-xs" id="pick-platform">
+ <div class="mob dropdowndrop">
+ <input id="check01" type="checkbox" name="menu"/>
+ <label for="check01">Choose your OS</label>
+ <ul id="menu">
+ <li><a href="#windows">Windows</a></li>
+ <li><a href="#mac">Mac</a></li>
+ <li><a href="#linux">Linux</a></li>
+ <li><a href="#arm">Arm (v7 & 8)</a></li>
+ <li><a href="#bsd">BSD</a></li>
+ <li><a href="#source">Source & Blockchain</a></li>
+ <li><a href="#mobilelight">Mobile & Light</a></li>
+ <li><a href="#hardware">Hardware</a></li>
+ </ul>
+ </div>
+ </div>
+</div>
+
+
+<div class="download-platforms">
+
+{% for data_downloads in site.data.downloads %}
+
+<section class="container full" id="{{ data_downloads.id}}">
+ <div class="info-block">
+ <h2>
+ {% if data_downloads.icon != null %}
+ <span class="{{data_downloads.icon}}"></span>
+ {% endif %}
+ {{data_downloads.platform}}
+ </h2>
+ {% if data_downloads.version != null %}
+ <p class="text-center">Current Version: {{ data_downloads.version }} {{ data_downloads.tag }}</p>
+ {%endif%}
+
+
+
+{% if data_downloads.cli_hash == "source" %}
+<div class="row">
+<div class="col-md-8 col-md-offset-2 col-sm-12 col-xs-12">
+<h4 id="{{ data_downloads.platform | slugify }}">
+ <a href="{{ data_downloads.cli_url }}">Source Code</a>
+</h4>
+</div>
+<div class="col-md-8 col-md-offset-2 col-sm-12 col-xs-12" markdown="1">
+If you'd prefer to use a blockchain bootstrap, instead of syncing from scratch, you can [use this link for the most current bootstrap](https://downloads.getmonero.org/blockchain.raw). It is typically much faster to sync from scratch, however, and it also takes a lot less RAM (import is very greedy).
+</div>
+</div>
+{% elsif data_downloads.id == "hardware" %}
+<div class="row">
+<div class="col-md-8 col-md-offset-2 col-sm-12 col-xs-12">
+<p>The Monero community has just funded a <a href="https://forum.getmonero.org/9/work-in-progress/88149/dedicated-monero-hardware-wallet" target="_blank" rel="noreferrer, noopener">Dedicated Hardware Wallet</a> which is now in progress. As well, Ledger is working on <a href="https://github.com/LedgerHQ/blue-app-monero" target="_blank" rel="noreferrer, noopener">integrating Monero into their hardware wallets</a>.</p>
+</div></div>
+
+{% elsif data_downloads.id == "mobilelight" %}
+<div class="row">
+<div class="col-md-8 col-md-offset-2 col-sm-12 col-xs-12">
+<p>The following are mobile or light wallets that are deemed safe by trusted members of the community. If there is a wallet that is not on here, you can request the community check it out. Go to our <a href="/community/hangouts/">Hangouts</a> page to see where we are.</p>
+</div>
+</div>
+<div class="row center-xs">
+ <div class="col-xs-6">
+ <a href="https://mymonero.com"><img src="/img/mymonero.png" alt="MyMonero Logo"></a>
+ </div>
+ <div class="col-xs-6">
+ <a href="https://monerujo.io"><img style="height: 115px;" src="/img/Monerujo-wallet.png" alt="Monerujo Logo"></a>
+ </div>
+</div>
+
+
+{% elsif data_downloads.gui_hash == nil and data_downloads.cli_hash != nil %}
+<div class="row"><div class="col-md-8 col-md-offset-2 col-sm-12 col-xs-12"><h4 id="{{ data_downloads.platform | slugify }}">
+ <a href="//downloads.getmonero.org/cli/{{ data_downloads.cli_url }}"> {{ data_downloads.platform }} (Command-line Tools Only)</a>
+ </h4></div></div>
+ <div class="row"><div class="col-md-8 col-md-offset-2 col-sm-12 col-xs-12">
+ <p><strong>SHA256 Hash:</strong></p> <p class="hash"> {{ data_downloads.cli_hash }}</p></div>
+</div>
+{% elsif data_downloads.gui_hash != nil and data_downloads.cli_hash == nil %}
+<div class="row">
+
+<h4 id="{{ data_downloads.platform | slugify }}">
+ <a href="//downloads.getmonero.org/gui/{{ data_downloads.gui_url }}">{{ data_downloads.platform }}</a>
+ </h4></div>
+<div class="row">
+<p><strong>SHA256 Hash:</strong></p> <p class="hash"> {{ data_downloads.gui_hash }}</p>
+</div>
+{% elsif data_downloads.gui_hash != nil and data_downloads.cli_hash != nil %}
+<div class="row start-md">
+<div class="col-md-6 col-sm-12" >
+
+<h4 id="{{ data_downloads.platform | slugify }}">
+ <a href="//downloads.getmonero.org/gui/{{ data_downloads.gui_url }}">{{ data_downloads.platform }}</a>
+</h4>
+<p><strong>SHA256 Hash (GUI):</strong></p> <p class="hash"> {{ data_downloads.gui_hash }}</p>
+
+</div>
+
+<div class="col-md-6 col-sm-12">
+<h4>
+ <a href="//downloads.getmonero.org/cli/{{ data_downloads.cli_url }}">{{ data_downloads.platform }} (Command-Line Tools Only)</a>
+</h4>
+<p><strong>SHA256 Hash (CLI):</strong></p> <p class="hash"> {{ data_downloads.cli_hash }}</p>
+</div>
+</div>
+{% endif %}
+ </div>
+</section>
+
+{% endfor %}
+
+</div>
+<a href="#" class="arrow-up"><i></i></a>
+
+</div>
+
+
+
diff --git a/_i18n/en/get-started/accepting.md b/_i18n/en/get-started/accepting.md
new file mode 100644
index 0000000000000000000000000000000000000000..4c9656cef8738bc4c456d38530f92ba8592cdd6b
--- /dev/null
+++ b/_i18n/en/get-started/accepting.md
@@ -0,0 +1,89 @@
+<section class="container">
+ <div class="row">
+ <!-- left two-thirds block-->
+ <div class="full">
+ <div class="info-block text-adapt">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Instructions for the Command-Line Interface</h2>
+ </div>
+ </div>
+<div markdown="1">
+
+### The Basics
+
+Monero works a little differently to what you may have become accustomed to from other @cryptocurrencies. In the case of a digital currency like Bitcoin and its many derivatives merchant payment systems will usually create a new recipient @address for each payment or user.
+
+However, because Monero has @stealth-addresses there is no need to have separate recipient addresses for each payment or user, and a single @account address can be published. Instead, when receiving payments a merchant will provide the person paying with a "payment ID".
+
+A @payment-ID is a hexadecimal string that is 64 characters long, and is normally randomly created by the merchant. An example of a payment ID is:
+```
+666c75666679706f6e7920697320746865206265737420706f6e792065766572
+```
+
+### Checking for a Payment in monero-wallet-cli
+
+If you want to check for a payment using monero-wallet-cli you can use the "payments" command followed by the payment ID or payment IDs you want to check. For example:
+
+```
+[wallet 49VNLa]: payments 666c75666679706f6e7920697320746865206265737420706f6e792065766572
+ payment transaction height amount unlock time
+ 666c75666679706f6e79206973207 7ba4cd810c9b4096869849458181e98e 441942 30.00000 0
+[wallet 49VNLa]: â–ˆ
+```
+
+If you need to check for payments programmatically, then details follow the next section.
+
+### Receiving a Payment Step-by-Step
+
+* Generate a random 64 character hexadecimal string for the payment
+* Communicate the payment ID and Monero address to the individual who is making payment
+* Check for the payment using the "payments" command in monero-wallet-cli
+
+### Checking for a Payment Programmatically
+
+In order to check for a payment programmatically you can use the get_payments or get_bulk_payments JSON RPC API calls.
+
+*get_payments*: this requires a payment_id parameter with a single payment ID.
+
+*get_bulk_payments*: this is the preferred method, and requires two parameters, payment_ids - a JSON array of payment IDs - and an optional min_block_height - the block height to scan from.
+
+An example of returned data is as follows:
+
+```
+[ monero->~ ]$ curl -X POST http://127.0.0.1:18500/json_rpc -d '{"jsonrpc":"2.0","method":"get_bulk_payments","id":"test", "params":{"payment_ids": ["666c75666679706f6e7920697320746865206265737420706f6e792065766572"]}}' -H "Content-Type: application/json"
+{
+ "id": "test",
+ "jsonrpc": "2.0",
+ "result": {
+ "payments": [{
+ "amount": 30000000000000,
+ "block_height": 441942,
+ "payment_id": "666c75666679706f6e7920697320746865206265737420706f6e792065766572",
+ "tx_hash": "7ba4cd810c9b4096869849458181e98e18b6474ab66415de0f4ccf7ab1162fdf",
+ "unlock_time": 0
+ }]
+ }
+}
+```
+
+It is important to note that the amounts returned are in base Monero units and not in the display units normally used in end-user applications. Also, since a transaction will typically have multiple outputs that add up to the total required for the payment, the amounts should be grouped by the tx_hash or the payment_id and added together. Additionally, as multiple outputs can have the same amount, it is imperative not to try and filter out the returned data from a single get_bulk_payments call.
+
+Before scanning for payments it is useful to check against the daemon RPC API (the get_info RPC call) to see if additional blocks have been received. Typically you would want to then scan only from that received block on by specifying it as the min_block_height to get_bulk_payments.
+
+### Programatically Scanning for Payments
+
+* Get the current block height from the daemon, only proceed if it has increased since our last scan
+* Call the get_bulk_payments RPC API call with our last scanned height and the list of all payment IDs in our system
+* Store the current block height as our last scanned height
+* Remove duplicates based on transaction hashes we have already received and processed
+
+</div>
+ </div>
+ </div>
+
+
+ <!-- end right one-third block-->
+ </div>
+ </section>
+
\ No newline at end of file
diff --git a/_i18n/en/get-started/contributing.md b/_i18n/en/get-started/contributing.md
new file mode 100644
index 0000000000000000000000000000000000000000..c2785c786a2a220bf32af509be462a635899437d
--- /dev/null
+++ b/_i18n/en/get-started/contributing.md
@@ -0,0 +1,92 @@
+<div markdown="1" class="text-center container description">
+Monero is an open-source, community-driven project. Described below are several ways to support the project.
+</div>
+
+<div class="contribute">
+ <section class="container">
+ <div class="row">
+ <!-- full block-->
+ <div class="full col-lg-12 col-md-12 col-sm-12 col-xs-12">
+ <div class="info-block text-adapt">
+ <div class="row center-xs">
+ <div class="col"><h2>Support the Network</h2></div>
+ </div>
+<div class="row start-xs" markdown="1">
+
+### Develop
+Monero is primarily written in C++. As it is a decentralized project, anyone is welcome to add or make changes to existing code. Pull requests are merged based on community consensus. See the <a href="https://github.com/monero-project"> repositories</a> and outstanding <a href="https://github.com/monero-project/monero/issues">issues</a>.
+
+### Run a Full Node
+Run monerod with port 18080 open. Running a full node ensures maximum privacy when transacting with Monero. It also improves distribution of the blockchain to new users.
+
+### Mine
+Mining ensures the Monero network remains decentralized and secure. In the Monero graphical user interface and command-line interface, background mining may be activated. Additional resources for mining may be viewed [here](https://reddit.com/r/MoneroMining).
+
+</div>
+ </div>
+ </div>
+ <!-- end full block-->
+ <!-- full block-->
+ <div class="full col-lg-12 col-md-12 col-sm-12 col-xs-12">
+ <div class="info-block text-adapt">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>View the Forum Funding System</h2>
+ </div>
+ </div>
+ <div class="row start-xs">
+ <p>Monero utilizes a <a href="https://forum.getmonero.org">forum funding system</a> whereby projects are proposed for development and community-funded. Funding is held in escrow and remunerated to developers once programming milestones are achieved. Anyone may generate new proposals or fund existing ones.</p>
+ </div>
+ </div>
+ </div>
+ <!-- full block-->
+ <!-- full block-->
+ <div class="full col-lg-12 col-md-12 col-sm-12 col-xs-12">
+ <div class="info-block text-adapt">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Donate</h2>
+ </div>
+ </div>
+ <div class="row start-xs">
+ <p>Ongoing development is supported by donations and <a href="{{site.baseurl}}/community/sponsorships/">sponsorships</a>.</p>
+ </div>
+ <div class="row center-xs">
+ <div class="col-lg-6">
+ <img src="/img/donate-monero.png" alt=""/>
+ </div>
+ <div class="col-lg-6">
+ <img src="/img/donate-bitcoin.png" alt=""/>
+ </div>
+ </div>
+ <div class="row start-xs">
+ <div class="col-xs-12">
+ <h3>Donating Monero</h3>
+ <p>Donations may be sent to donate.getmonero.org or 44AFFq5kSiGBoZ4NMDwYtN18obc8AemS33DBLWs3H7otXft3XjrpDtQGv7SqSsaBYBb98uNbr2VBBEt7f2wfn3RVGQBEP3A</p>
+ </div>
+ </div>
+ <div class="row start-xs">
+ <div class="col-xs-12">
+ <h3>Donating Bitcoin</h3>
+ <p>Donations may be sent to donate.getmonero.org or 1KTexdemPdxSBcG55heUuTjDRYqbC5ZL8H</p>
+ </div>
+ </div>
+ <div class="row start-xs">
+ <div class="col-xs-12">
+ <h3>Other</h3>
+ <p>E-mail <a href="mailto:dev@getmonero.org">dev@getmonero.org</a> for alternative means of donating or if you would like to become a sponsor for the Monero Project.</p>
+ </div>
+ </div>
+ </div>
+ </div>
+ <!-- full block-->
+
+
+
+
+
+
+ </div>
+ </section>
+
+</div>
diff --git a/_i18n/en/get-started/faq.md b/_i18n/en/get-started/faq.md
new file mode 100644
index 0000000000000000000000000000000000000000..c6b2d17581d0c62e1128d10a9a877fa4d26a4c64
--- /dev/null
+++ b/_i18n/en/get-started/faq.md
@@ -0,0 +1,135 @@
+<div class="tab">
+ <input id="tab-one" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-one" class="accordion">How does Monero have value?</label>
+
+<div class="tab-content" markdown="1">
+
+Monero has value because people are willing to buy it. If no one is willing to buy Monero, then it will not have any value. Monero’s price increases if demand exceeds supply, and it decreases if supply exceeds demand.
+
+</div>
+
+</div>
+
+<div class="tab">
+ <input id="tab-two" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-two" class="accordion">How can I get Monero?</label>
+
+<div class="tab-content" markdown="1">
+
+You can buy Monero from an exchange or from an individual. Alternatively, you can try mining Monero to get coins from the block reward.
+</div>
+
+</div>
+
+<div class="tab">
+ <input id="tab-three" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-three" class="accordion">What is a mnemonic seed?</label>
+
+<div class="tab-content" markdown="1">
+
+A mnemonic seed is a set of 25 words that can be used to restore your account anywhere. Keep these words safe and do not share them with someone else. You can use this seed to restore your account, even if your computer crashes.
+</div>
+
+</div>
+
+<div class="tab">
+ <input id="tab-four" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-four" class="accordion">How is Monero’s privacy different from other coins?</label>
+
+<div class="tab-content" markdown="1">
+
+Monero uses three different privacy technologies: ring signatures, ring confidential transactions (RingCT), and stealth addresses. These hide the sender, amount, and receiver in the transaction, respectively. All transactions on the network are private by mandate; there is no way to accidentally send a transparent transaction. This feature is exclusive to Monero. You do not need to trust anyone else with your privacy.
+</div>
+
+</div>
+
+<div class="tab">
+ <input id="tab-five" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-five" class="accordion">Why is my wallet taking so long to sync?</label>
+
+<div class="tab-content" markdown="1">
+
+If you are running a full node locally, you need to copy the entire blockchain to your computer. This can take a long time, especially on an old hard drive or slow internet connection. If you are using a remote node, your computer still needs to request a copy of all the outputs, which can take several hours. Be patient, and if you would like to sacrifice some privacy for faster sync times, consider using a lightweight wallet instead.
+</div>
+
+</div>
+
+<div class="tab">
+ <input id="tab-six" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-six" class="accordion">What is the different between a lightweight and a normal wallet?</label>
+
+<div class="tab-content" markdown="1">
+
+For a lightweight wallet, you give your view key to a node, who scans the blockchain and looks for incoming transactions to your account on your behalf. This node will know when you receive money, but it will not know how much you receive, who you received it from, or who you are sending money to. Depending on your wallet software, you may be able to use a node you control to avoid privacy leaks. For more privacy, use a normal wallet, which can be used with your own node.
+</div>
+
+</div>
+
+<div class="tab">
+ <input id="tab-seven" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-seven" class="accordion">How is Monero different from Bitcoin?</label>
+
+<div class="tab-content" markdown="1">
+
+Monero is not based on Bitcoin. It is based on the CryptoNote protocol. Bitcoin is a completely transparent system, where people can see exactly how much money is being sent from one user to another. Monero hides this information to protect user privacy in all transactions. It also has a dynamic block size and dynamic fees, an ASIC-resistant proof of work, and a tail coin emission, among several other changes.
+</div>
+
+</div>
+
+<div class="tab">
+ <input id="tab-eight" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-eight" class="accordion">Does Monero have a block size limit?</label>
+
+<div class="tab-content" markdown="1">
+
+No, Monero does not have a hard block size limit. Instead, the block size can increase or decrease over time based on demand. It is capped at a certain growth rate to prevent outrageous growth.
+</div>
+
+</div>
+
+<div class="tab">
+ <input id="tab-nine" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-nine" class="accordion">What is a blockchain?</label>
+
+<div class="tab-content" markdown="1">
+
+A blockchain is a system that stores a copy of all transaction history on the Monero network. Every two minutes, a new block with the latest transaction information is added to the blockchain. This chain allows the network to verify the amount of money accounts have and make it resilient to attacks and centralization attempts.
+</div>
+
+</div>
+
+<div class="tab">
+ <input id="tab-ten" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-ten" class="accordion">What is Kovri?</label>
+
+<div class="tab-content" markdown="1">
+
+Kovri is an I2P router written in C++. I2P is a hidden network like Tor with several technical differences. Kovri is an independent project of Monero, but it will work with Monero and several other projects. Kovri hides the transaction broadcast, so other nodes do not know who created transactions. In adversarial conditions, Kovri can be used to hide all Monero traffic through I2P, which would prevent people from knowing Monero is being used. Kovri is currently in alpha, and it is not yet fully integrated in Monero. Learn more about Kovri at the [project website.](https://getkovri.org)
+</div>
+
+</div>
+
+<div class="tab">
+ <input id="tab-eleven" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-eleven" class="accordion">What is fungibility, and why is it important?</label>
+
+<div class="tab-content" markdown="1">
+
+Fungibility is a simple property of money such that there are no differences between two amounts of the same value. If two people exchanged a 10 and two 5’s, then no one would lose out. However, let’s suppose that everyone knows the 10 was previously used in a ransomware attack. Is the other person still going to make the trade? Probably not, even if the person with the 10 has no connection with the ransomware. This is a problem, since the receiver of money needs to constantly check the money they are receiving to not end up with tainted coins. Monero is fungible, which means people do not need to go through this effort.
+</div>
+
+</div>
+
+<div class="tab">
+ <input id="tab-twelve" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-twelve" class="accordion">If Monero is so private how do we know they're not being created out of thin air?</label>
+
+<div class="tab-content" markdown="1">
+In Monero, every transaction output is uniquely associated with a key image that can only be generated by the holder of that output. Key images that are used more than once are rejected by the miners as double-spends and cannot be added to a valid block. When a new transaction is received, miners verify that the key image does not already exist for a previous transaction to ensure it's not a double-spend.
+
+We can also know that transaction amounts are valid even though the value of the inputs that you are spending and the value of the outputs you are sending are encrypted (these are hidden to everyone except the recipient). Because the amounts are encrypted using Pedersen commitments what this means is that no observers can tell the amounts of the inputs and outputs, but they can do math on the Pedersen commitments to determine that no Monero was created out of thin air.
+
+As long as the encrypted output amounts you create is equal to the sum of the inputs that are being spent (which include an output for the recipient and a change output back to yourself and the unencrypted transaction fee), then you have a legitimate transaction and know no Monero is being created out of thin air. 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.
+</div>
+
+</div>
diff --git a/_i18n/en/get-started/mining.md b/_i18n/en/get-started/mining.md
new file mode 100644
index 0000000000000000000000000000000000000000..2a94422954da115ceb0bbe83c0f6653bf79d8934
--- /dev/null
+++ b/_i18n/en/get-started/mining.md
@@ -0,0 +1,86 @@
+<div class="mining">
+<div class="center-xs container description">
+<p>Monero is a cryptocurrency that relies on proof-of-work mining to achieve distributed consensus. Below you'll find some information and resources on how to begin mining.</p>
+
+<p><strong>The Monero Project does not endorse any particular pool, software, or hardware, and the content below is provided for informational purposes only.</strong></p>
+</div>
+
+<section class="container">
+ <div class="row">
+ <!-- full block-->
+ <div class="full col-lg-12 col-md-12 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Support</h2>
+ </div>
+ </div>
+ <div class="row center-xs">
+ <p>See <a href="{{site.baseurl}}/community/hangouts/"> Hangouts</a>, <a href="https://www.reddit.com/r/MoneroMining/" target="_blank" rel="noreferrer noopener">/r/moneromining</a> and <a href="irc://chat.freenode.net/#monero-pools" target="_blank" rel="noreferrer noopener">#monero-pools</a>.</p>
+ </div>
+ </div>
+ </div>
+ <!-- end full block -->
+ </div>
+ </section>
+<section class="container">
+ <div class="row">
+ <div class="left half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Pools</h2>
+ </div>
+ </div>
+ <div class="row center-xs">
+ <p>A listing of trusted Monero pools is found <a href="http://moneropools.com/"> here</a>.</p>
+ </div>
+ </div>
+ </div>
+ <div class="right half col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Hardware Benchmarking</h2>
+ </div>
+ </div>
+ <div class="row center-xs">
+ <p>See <a href="http://monerobenchmarks.info/">here</a> for a listing of GPUs/CPUs and their respective hashrates.</p>
+ </div>
+ </div>
+ </div>
+ </div>
+ </section>
+ <section class="container">
+ <div class="row">
+ <!-- full block-->
+ <div class="full col-lg-12 col-md-12 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Mining Software</h2>
+ </div>
+ </div>
+ <div class="row center-xs">
+ <p>Note that some miners may have developer fees.</p>
+ </div>
+ <div class="row center-xs">
+ <p><a href="https://github.com/fireice-uk/xmr-stak" target="_blank" rel="noreferrer noopener">XMR Stak</a></p>
+ </div>
+ <div class="row center-xs">
+ <p><a href="https://github.com/xmrig/xmrig" target="_blank" rel="noreferrer noopener">XMRig</a></p>
+ </div>
+ <div class="row center-xs">
+ <p><a href="https://github.com/xmrig/xmrig-amd" target="_blank" rel="noreferrer noopener">XMRig AMD</a></p>
+ </div>
+ <div class="row center-xs">
+ <p><a href="https://github.com/xmrig/xmrig-nvidia" target="_blank" rel="noreferrer noopener">XMRig NVIDIA</a></p>
+ </div>
+ </div>
+ </div>
+ <!-- end full block -->
+ </div>
+ </section>
+
+
+</div>
\ No newline at end of file
diff --git a/_i18n/en/get-started/using.md b/_i18n/en/get-started/using.md
new file mode 100644
index 0000000000000000000000000000000000000000..efe4a18c1a2ee1cc71d4d165333470cd27702750
--- /dev/null
+++ b/_i18n/en/get-started/using.md
@@ -0,0 +1,98 @@
+<div class="text-center container description">
+ <p>Transacting with Monero can be made easy. This page is designed to guide users in that process.</p>
+</div>
+<div class="using">
+ <section class="container">
+ <div class="row">
+ <!-- full block-->
+ <div class="full col-lg-12 col-md-12 col-sm-12 col-xs-12">
+ <div class="info-block text-adapt">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>1. Learn</h2>
+ </div>
+ </div>
+ <div class="row start-xs">
+ <p>Monero is a secure, private, and untraceable cryptocurrency. The developers and community are committed to protecting these values. Learn more by reading the <a href="{{site.baseurl}}/get-started/what-is-monero/">What is Monero</a> page. The <a href="https://github.com/monero-project">source code</a> is also available for review and discussion.</p>
+ </div>
+ </div>
+ </div>
+ <!-- end full block -->
+ </div>
+ </section>
+ <section class="container">
+ <div class="row">
+ <div class="left half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>2. Request Support</h2>
+ </div>
+ </div>
+ <div class="row start-xs">
+ <p>There is a large and supportive community that will assist if you experience any difficulty. See the <a href="{{site.baseurl}}/community/hangouts/">Hangouts</a> page for more information.</p>
+ </div>
+ </div>
+ </div>
+ <div class="right half col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>3. Generate a Wallet</h2>
+ </div>
+ </div>
+ <div class="row start-xs">
+ <p>A Monero wallet is required to secure your own funds. See the <a href="{{site.baseurl}}/downloads/">Downloads</a> page for a listing of available wallets.</p>
+ <p>The easiest way to run a Monero node, without affecting your home bandwidth, is to purchase a VPS (Virtual Private Server). We strongly recommend <a href="https://interserver.net/dock/vps-231552.html">InterServer.net</a> using the 'MONERO' coupon code to get a discount over and above their already cheap $6/month VPS. Using this coupon code and/or <a href="https://interserver.net/dock/vps-231552.html">our affiliate link</a> will also assist in the ongoing funding of Monero development.</p>
+ </div>
+ </div>
+ </div>
+ </div>
+ </section>
+ <section class="container">
+ <div class="row">
+ <!-- full block-->
+ <div class="full col-lg-12 col-md-12 col-sm-12 col-xs-12">
+ <div class="info-block text-adapt">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>4. Acquire Monero</h2>
+ </div>
+ </div>
+ <div class="row start-xs">
+ <p>Monero may be purchased on an <a href="{{site.baseurl}}/community/merchants#exchanges">exchange</a> with fiat or other cryptocurrencies. An alternate way of acquiring Monero is via <a href="{{site.baseurl}}/get-started/mining/">mining</a>, the computationally-complex process whereby transactions are immutably recorded on the blockchain.</p>
+ </div>
+ </div>
+ </div>
+ <!-- end full block -->
+ </div>
+ </section>
+ <section class="container">
+ <div class="row">
+ <div class="left half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>5. Send and Receive Monero</h2>
+ </div>
+ </div>
+ <div class="row start-xs">
+ <p>Learn how to send and receive Monero by viewing the <a href="{{site.baseurl}}/get-started/accepting/">guide</a>.</p>
+ </div>
+ </div>
+ </div>
+ <div class="right half col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>6. Transact with Monero</h2>
+ </div>
+ </div>
+ <div class="row start-xs">
+ <p>Monero may be used to purchase many goods and services. For a listing, see the <a href="{{site.baseurl}}/community/merchants/">Merchants</a> page. </p>
+ </div>
+ </div>
+ </div>
+ </div>
+ </section>
+</div>
diff --git a/_i18n/en/get-started/what-is-monero.md b/_i18n/en/get-started/what-is-monero.md
new file mode 100644
index 0000000000000000000000000000000000000000..89588bbd426245c3cc96aa2925d61014c934d6f3
--- /dev/null
+++ b/_i18n/en/get-started/what-is-monero.md
@@ -0,0 +1,119 @@
+<div class="site-wrap">
+ <section class="container">
+ <div class="row">
+ <section class="container about-monero full col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col"><h2>What you need to know</h2></div>
+ </div>
+ <div class="row middle-xs info-block-row private">
+ <div class="col-lg-7 col-md-6 col-sm-8 col-xs-12 why-text">
+ <h3>Monero is the leading cryptocurrency with a focus on private and censorship-resistant transactions.</h3>
+ <p>Most existing cryptocurrencies, including Bitcoin and Ethereum, have transparent blockchains, meaning that transactions are openly verifiable and traceable by anyone in the world. Furthermore, sending and receiving addresses for these transactions may potentially be linkable to a person's real-world identity. </p>
+ <p>Monero uses cryptography to shield sending and receiving addresses, as well as transacted amounts.</p>
+ </div>
+ <div class="col-lg-5 col-md-6 col-sm-4 col-xs-12 last-sm first-xs center-xs">
+ <img src="/img/crypto-lock.png" alt="Encrypted lock" class="main-icon">
+ </div>
+ </div>
+ <div class="row middle-xs info-block-row">
+ <div class="col-lg-5 col-md-6 col-sm-4 col-xs-12 center-xs">
+ <img src="/img/monero-classified.png" alt="Classified document" class="main-icon">
+ </div>
+ <div class="col-lg-7 col-md-6 col-sm-8 col-xs-12 why-text">
+ <h3>Monero transactions are confidential and untraceable.</h3>
+ <p>Every Monero transaction, by default, obfuscates sending and receiving addresses as well as transacted amounts. This always-on privacy means that every Monero user's activity enhances the privacy of all other users, unlike selectively transparent cryptocurrencies (e.g. Z-Cash).</p>
+ <p>Monero is fungible. By virtue of obfuscation, Monero cannot become tainted through participation in previous transactions. This means Monero will always be accepted without the risk of censorship.</p>
+ <p>The Kovri Project, <a href="https://getkovri.org/">currently in development</a>, will route and encrypt transactions via I2P Invisible Internet Project nodes. This will obfuscate a transactor's IP address and provide further protection against network monitoring.</p>
+ </div>
+
+ </div>
+ <div class="row middle-xs info-block-row">
+ <div class="col-lg-7 col-md-6 col-sm-8 col-xs-12 why-text">
+ <h3>Monero is a grassroots community attracting the world's best cryptocurrency researchers and engineering talent.</h3>
+ <p>Over <a href="https://www.openhub.net/p/monero" target="_blank" rel="noreferrer noopener">240 developers</a> have contributed to the Monero project, including 30 core developers. Forums and chat channels are welcoming and active.</p>
+ <p>Monero's Research Lab, Core Development Team and Community Developers are constantly pushing the frontier of what is possible with cryptocurrency privacy and security.</p>
+ <p>Monero is not a corporation. It is developed by cryptography and distributed systems experts from all over the world that donate their time or are funded by community donations. This means that Monero can't be shut down by any one country and is not constrained by any particular legal jurisdiction.</p>
+ </div>
+ <div class="col-lg-5 col-md-6 col-sm-4 col-xs-12 last-sm first-xs center-xs">
+ <img src="/img/academic-growth.png" alt="Academic growth" class="main-icon">
+ </div>
+ </div>
+ <div class="row middle-xs info-block-row">
+ <div class="col-lg-5 col-md-6 col-sm-4 col-xs-12 center-xs">
+ <img src="/img/monero-electronic-cash.png" alt="Electronic cash" class="main-icon">
+ </div>
+ <div class="col-lg-7 col-md-6 col-sm-8 col-xs-12 why-text">
+ <h3>Monero is electronic cash that allows fast, inexpensive payments to and from anywhere in the world.</h3>
+ <p>There are no multi-day holding periods and no risk of fraudulent chargebacks. It is safe from ‘capital controls’ - these are measures that restrict the flow of traditional currencies, sometimes to an extreme degree, in countries experiencing economic instability.</p>
+ </div>
+ </div>
+ </div>
+ </section>
+ <section class="full col-xs-12 monero-vid">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col"><h2>Monero Videos</h2></div>
+ </div>
+ <div class="row center-xs">
+ <div class="col-xs-12 carousel-container">
+ <ul class="carousel my-carousel">
+ <input class="carousel-activator" type="radio" id="A" name="activator" checked="checked"/>
+ <input class="carousel-activator" type="radio" id="B" name="activator"/>
+ <input class="carousel-activator" type="radio" id="C" name="activator"/>
+ <input class="carousel-activator" type="radio" id="D" name="activator"/>
+ <div class="carousel-controls">
+ <label class="carousel-control carousel-control-backward" for="D"></label>
+ <label class="carousel-control carousel-control-forward" for="B"></label>
+ </div>
+ <div class="carousel-controls">
+ <label class="carousel-control carousel-control-backward" for="A"></label>
+ <label class="carousel-control carousel-control-forward" for="C"></label>
+ </div>
+ <div class="carousel-controls">
+ <label class="carousel-control carousel-control-backward" for="B"></label>
+ <label class="carousel-control carousel-control-forward" for="D"></label>
+ </div>
+ <div class="carousel-controls">
+ <label class="carousel-control carousel-control-backward" for="C"></label>
+ <label class="carousel-control carousel-control-forward" for="A"></label>
+ </div>
+ <li class="carousel-slide ms">
+ <h3>Monero Promo</h3>
+ <video controls poster="/img/monero-community.png" onclick="this.paused ? this.play() : this.pause();" preload="none">
+ <source src="/media/Monero_Promo.m4v">
+ </video>
+ </li>
+ <li class="carousel-slide">
+ <h3>Monero: The Essentials</h3>
+ <video controls poster="/img/monero-cash-video-poster.png" onclick="this.paused ? this.play() : this.pause();" preload="none">
+ <source src="/media/Monero%20-%20The%20Essentials.m4v">
+ </video>
+ </li>
+ <li class="carousel-slide">
+ <h3>Stealth Addresses</h3>
+ <video controls poster="/img/stealth-address-poster.png" onclick="this.paused ? this.play() : this.pause();" preload="none">
+ <source src="/media/Monero%20-%20Stealth%20Addresses.m4v">
+ </video>
+ </li>
+ <li class="carousel-slide">
+ <h3>Ring Signatures</h3>
+ <video controls poster="/img/ring-signatures-poster.png" onclick="this.paused ? this.play() : this.pause();" preload="none">
+ <source src="/media/Monero%20-%20Ring%20Signatures.m4v">
+ </video>
+ </li>
+ <li class="carousel-slide">
+ <h3>RingCT</h3>
+ <video controls poster="/img/ringct-poster.png" onclick="this.paused ? this.play() : this.pause();" preload="none">
+ <source src="/media/Monero%20-%20RingCT.m4v">
+ </video>
+ </li>
+ </ul>
+ </div>
+ </div>
+ </div>
+ </section>
+
+ </div>
+ </section>
+</div>
\ No newline at end of file
diff --git a/_i18n/en/index.md b/_i18n/en/index.md
new file mode 100644
index 0000000000000000000000000000000000000000..de178c7125896b3289a8a7d3568620ac3c0203d1
--- /dev/null
+++ b/_i18n/en/index.md
@@ -0,0 +1,190 @@
+<div class="site-wrap">
+ <section class="container full col-xs-12">
+ <div class="info-block info-block-main">
+ <div class="row middle-xs">
+ <div class="col-lg-7 col-md-7 col-xs-12 main-video">
+ <div class="monero-video">
+ <!--iframe width="560" height="315" src="https://www.youtube.com/embed/TZi9xx6aiuY" frameborder="0" allowfullscreen></iframe-->
+ <video controls poster="img/monero-community.png" onclick="this.paused ? this.play() : this.pause();" preload="none">
+ <source src="/media/Monero_Promo.m4v">
+ </video>
+ </div>
+
+ </div>
+ <div class="col-lg-5 col-md-5 col-xs-12">
+ <div class="main-info">
+ <h1 id="main-h1">Monero</h1>
+ <h2 id="main-h2">Private Digital Currency</h2>
+ <p id="main-text">Monero is cash for a connected world. It’s fast, private, and secure. With Monero, you are your own bank. You can spend safely, knowing that others cannot see your balances or track your activity.</p>
+ <p><a href="{{site.baseurl}}/get-started/using/" class="btn-link btn-auto btn-primary">Get Started</a></p>
+ </div>
+ </div>
+ </div>
+ </div>
+ </section>
+
+ <!-- FULL WIDTH BLOCK -->
+
+ <section class="container about-main full col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col"><h2>Why Monero is different</h2></div>
+ </div>
+ <div class="row middle-xs info-block-row private">
+ <div class="col-lg-6 col-md-6 col-sm-8 col-xs-12 why-text">
+ <h3>Monero is secure</h3>
+ <p>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. </p>
+ </div>
+ <div class="col-lg-6 col-md-6 col-sm-4 col-xs-12 last-sm first-xs center-xs">
+ <img src="/img/secure-monero.png" alt="Secure safe" class="main-icon">
+ </div>
+ </div>
+ <div class="row middle-xs info-block-row">
+ <div class="col-lg-6 col-md-6 col-sm-4 col-xs-12 center-xs">
+ <img src="/img/private-monero.png" alt="No surveillance" class="main-icon">
+ </div>
+ <div class="col-lg-6 col-md-6 col-sm-8 col-xs-12 why-text">
+ <h3>Monero is private</h3>
+ <p>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. </p>
+ </div>
+
+ </div>
+ <div class="row middle-xs info-block-row">
+ <div class="col-lg-6 col-md-6 col-sm-8 col-xs-12 why-text">
+ <h3>Monero is untraceable</h3>
+ <p>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.</p>
+ </div>
+ <div class="col-lg-6 col-md-6 col-sm-4 col-xs-12 last-sm first-xs center-xs">
+ <img src="/img/untraceable-monero.png" alt="Untraceable Monero paths" class="main-icon">
+ </div>
+ </div>
+ <div class="row middle-xs info-block-row">
+ <div class="col-lg-6 col-md-6 col-sm-4 col-xs-12 center-xs">
+ <img src="/img/fungible-monero.png" alt="Monero gold" class="main-icon">
+ </div>
+ <div class="col-lg-6 col-md-6 col-sm-8 col-xs-12 why-text">
+ <h3>Monero is fungible</h3>
+ <p> Monero is <a href="{{site.baseurl}}/resources/moneropedia/fungibility.html">fungible</a> because it is private by default. Units of Monero cannot be blacklisted by vendors or exchanges due to their association in previous transactions.</p>
+ </div>
+ </div>
+ </div>
+ </section>
+
+ <!-- END FULL WIDTH BLOCK -->
+
+
+
+ <!-- TWO THIRDS & ONE THIRD BLOCKS ROW -->
+
+ <section class="container">
+ <div class="row">
+ <!-- left two-thirds block-->
+ <div class="left two-thirds col-lg-8 col-md-8 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col"><h2>Downloads</h2></div>
+ </div>
+ <div class="row around-xs">
+ <div class="col">
+ <p><a href="{{site.baseurl}}/downloads#windows" class="btn-link btn-fixed"><span class="icon-windows"></span>Monero for Windows</a></p>
+ </div>
+ <div class="col">
+ <p><a href="{{site.baseurl}}/downloads#mac" class="btn-link btn-fixed"><span class="icon-apple"></span>Monero for Mac</a></p>
+ </div>
+ </div>
+ <div class="row around-xs">
+ <div class="col">
+ <p><a href="{{site.baseurl}}/downloads#linux" class="btn-link btn-fixed"><span class="icon-linux"></span>Monero for Linux</a></p>
+ </div>
+ <div class="col">
+ <p><a href="{{site.baseurl}}/downloads#source" class="btn-link btn-fixed"><span class="icon-blockchain"></span>Latest Blockchain</a></p>
+ </div>
+ </div>
+ <div class="row">
+ <div class="col-xs-12"><p class="main-downloads">Need it for a different operating system? <a href="{{site.baseurl}}/downloads/">View all available downloads here.</a></p>
+ </div>
+ </div>
+ </div>
+ </div>
+ <!-- end left two-thirds block-->
+
+ <!-- right one-third block-->
+ <div class="right one-third col-lg-4 col-md-4 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col"><h2>Latest News</h2></div>
+ </div>
+ <div class="info-block-row">
+ {% for post in site.posts limit:2 %}
+ <div class="row start-xs">
+ <div class="col">
+ <p><a href="{{site.baseurl}}{{ post.url }}">{{ post.title }}</a></p>
+ </div>
+ </div>
+ {% endfor %}
+
+
+ <div class="row end-xs">
+ <div class="col">
+ <p><a href="{{site.baseurl}}/blog/">More news</a></p>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ <!-- end right one-third block-->
+ </div>
+ </section>
+
+ <!-- END TWO THIRDS & ONE THIRD BLOCKS ROW -->
+
+ <!-- 3 ONE-THIRD BLOCKS ROW -->
+
+ <section class="container">
+ <div class="row">
+ <!-- left one-third block-->
+ <div class="left one-third col-lg-4 col-md-4 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Moneropedia</h2>
+ <p class="main-resources">Would you like to look up the meanings of the terms and concepts used in Monero? Here you will find an alphabetical guide to terms and their meanings from both the Monero and Kovri projects.</p>
+ <p><a href="{{site.baseurl}}/resources/moneropedia/" class="btn-link btn-auto">Read Moneropedia</a></p>
+ </div>
+ </div>
+ </div>
+ </div>
+ <!-- end left one-third block-->
+
+ <!-- center one-third block-->
+ <div class="center one-third col-lg-4 col-md-4 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>User Guides</h2>
+ <p class="main-resources">Step-by-step guides to all things Monero are separated by category and cover everything from creating a wallet to supporting the network, and even how to edit this website.</p>
+ <p><a href="{{site.baseurl}}/resources/user-guides/" class="btn-link btn-auto">Read user guides</a></p>
+ </div>
+ </div>
+ </div>
+ </div>
+ <!-- end center one-third block-->
+
+ <!-- right one-third block-->
+ <div class="right one-third col-lg-4 col-md-4 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>FAQ</h2>
+ <p class="main-resources">We've heard a lot of questions over the years and have compiled, for your convenience, a thorough and varied FAQ. Don't worry, if your questions are not on here, you can always ask the community.</p>
+ <p><a href="{{site.baseurl}}/get-started/faq/" class="btn-link btn-auto">Read answers</a></p>
+ </div>
+ </div>
+ </div>
+ </div>
+ <!-- end right one-third block-->
+ </div>
+ </section>
+
+ <!-- END 3 ONE-THIRD BLOCKS ROW -->
+</div>
diff --git a/_i18n/en/press-kit.md b/_i18n/en/press-kit.md
new file mode 100644
index 0000000000000000000000000000000000000000..0f6e7b2855e8a696a3c74b7fe7af8b86fbb173d5
--- /dev/null
+++ b/_i18n/en/press-kit.md
@@ -0,0 +1,69 @@
+<div class="text-center container description">
+<p>Here you'll find the Monero symbol and logo below. You can choose any size that you want, or download the .ai file to mess with the logo yourself. <strong>Note that the white background options have a white background under the Monero symbol ONLY, not as a background to the whole image.</strong> Lastly, you can download everything on this page in one zip file by clicking <a href="/press-kit/monero-press-kit.zip">here</a>.</p>
+</div>
+<section class="container">
+ <div class="row">
+ <div class="left half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Monero Symbol</h2>
+ </div>
+ </div>
+ <div class="row center-xs">
+ <img src="/press-kit/symbols/monero-symbol-480.png" alt="Monero Symbol" class="symbol-logo">
+ </div>
+ <div class="row center-xs press">
+ <div class="col-md-6">
+ <p>No background (PNG)</p>
+ <a href="/press-kit/symbols/monero-symbol-480.png">Small</a>
+ <a href="/press-kit/symbols/monero-symbol-800.png">Medium</a>
+ <a href="/press-kit/symbols/monero-symbol-1280.png">Large</a>
+ </div>
+ <div class="col-md-6">
+ <p>White background (PNG)</p>
+ <a href="/press-kit/symbols/monero-symbol-on-white-480.png">Small</a>
+ <a href="/press-kit/symbols/monero-symbol-on-white-800.png">Medium</a>
+ <a href="/press-kit/symbols/monero-symbol-on-white-1280.png">Large</a>
+ </div>
+ </div>
+ <div class="row center-xs press">
+ <a href="/press-kit/symbols/monero-symbol.ai" class="adi">Symbol .ai file</a>
+ </div>
+ </div>
+ </div>
+ <div class="right half col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Monero Logo</h2>
+ </div>
+ </div>
+ <div class="row center-xs">
+ <div class="col-xs-12">
+ <img src="/press-kit/logos/monero-logo-480.png" alt="Monero Logo" class="monero-symbol-logo">
+ </div>
+ </div>
+ <div class="row center-xs press">
+ <div class="col-md-6">
+ <p>No background (PNG)</p>
+ <a href="/press-kit/logos/monero-logo-480.png">Small</a>
+ <a href="/press-kit/logos/monero-logo-800.png">Medium</a>
+ <a href="/press-kit/logos/monero-logo-1280.png">Large</a>
+ </div>
+ <div class="col-md-6">
+ <p>White background (PNG)</p>
+ <a href="/press-kit/logos/monero-logo-symbol-on-white-480.png">Small</a>
+ <a href="/press-kit/logos/monero-logo-symbol-on-white-800.png">Medium</a>
+ <a href="/press-kit/logos/monero-logo-symbol-on-white-1280.png">Large</a>
+ </div>
+ </div>
+ <div class="row center-xs press">
+ <div class="col-xs-12">
+ <a href="/press-kit/logos/monero-logo.ai" class="adi">Logo .ai file</a>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+</section>
\ No newline at end of file
diff --git a/_i18n/en/resources/about.md b/_i18n/en/resources/about.md
new file mode 100644
index 0000000000000000000000000000000000000000..d978ad6ee7c8fb45b31fa331602f8a9c822f11f7
--- /dev/null
+++ b/_i18n/en/resources/about.md
@@ -0,0 +1,56 @@
+<div class="about-monero">
+ <section class="container">
+ <div class="row">
+ <!-- left two-thirds block-->
+ <div class="full col-xs-12">
+ <div class="info-block text-adapt">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>A Brief History</h2>
+ </div>
+ </div>
+<div markdown="1">
+
+Monero was launched in April 2014. It was a fair, pre-announced launch of the CryptoNote reference code. There was no premine or instamine, and no portion of the block reward goes to development. See the original Bitcointalk thread here. The founder, thankful_for_today, proposed some controversial changes that the community disagreed with. A fallout ensued, and the Monero Core Team forked the project with the community following this new Core Team. This Core Team has provided oversight since.
+
+Monero has made several large improvements since launch. The blockchain was migrated to a different database structure to provide greater efficiency and flexibility, minimum ring signature sizes were set so that all transactions were private by mandate, and RingCT was implemented to hide the transaction amounts. Nearly all improvements have provided improvements to security or privacy, or they have facilitated use. Monero continues to develop with goals of privacy and security first, ease of use and efficiency second.
+
+</div>
+ </div>
+ </div>
+ <!-- end right one-third block-->
+ </div>
+ <div class="row">
+ <!-- left two-thirds block-->
+ <div class="full col-xs-12">
+ <div class="info-block text-adapt">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Our Values</h2>
+ </div>
+ </div>
+
+<div markdown="1">
+
+Monero is more than just a technology. It’s also what the technology stands for. Some of the important guiding philosophies are listed below.
+
+### Security
+
+Users must be able to trust Monero with their transactions, without risk of error or attack. Monero gives the full block reward to the miners, who are the most critical members of the network who provide this security. Transactions are cryptographically secure using the latest and most resilient encryption tools available.
+
+### Privacy
+
+Monero takes privacy seriously. Monero needs to be able to protect users in a court of law and, in extreme cases, from the death penalty. This level of privacy must be completely accessible to all users, whether they are technologically competent or have no idea how Monero works. A user needs to confidently trust Monero in a way that this person does not feel pressured into changing their spending habits for risk of others finding out.
+
+### Decentralization
+
+Monero is committed to providing the maximum amount of decentralization. With Monero, you do not have to trust anyone else on the network, and it is not run by any large group. An accessible “Proof of Work†algorithm makes it easy to mine Monero on normal computers, which makes it more difficult for someone to purchase a large amount of mining power. Nodes connect to each other with I2P to lower the risks of revealing sensitive transaction information and censorship (tba). Development decisions are extremely clear and open to public discussion. Developer meeting logs are published online in their entirety and visible by all.
+
+</div>
+ </div>
+ </div>
+
+
+ <!-- end right one-third block-->
+ </div>
+ </section>
\ No newline at end of file
diff --git a/_i18n/en/resources/developer-guides.md b/_i18n/en/resources/developer-guides.md
new file mode 100644
index 0000000000000000000000000000000000000000..01f64533b34883fa82af5ebddc22abf1ad5c6d06
--- /dev/null
+++ b/_i18n/en/resources/developer-guides.md
@@ -0,0 +1,19 @@
+<div class="guides">
+
+<div class="center-xs container description">
+<p class="text-center">Please note: the guides below are currently out of date, but are considered a good starting point for most calls. </p>
+</div>
+
+<section class="container full">
+ <div class="info-block">
+ <h2>RPC Documetation</h2>
+<div markdown="1">
+
+[Daemon RPC Documentation](daemon-rpc.html)
+[Wallet RPC Documentation](wallet-rpc.html)
+
+More coming soon...
+</div>
+ </div>
+</section>
+</div>
\ No newline at end of file
diff --git a/_i18n/en/resources/developer-guides/daemon-rpc.md b/_i18n/en/resources/developer-guides/daemon-rpc.md
new file mode 100644
index 0000000000000000000000000000000000000000..fe53aaed3a1089732ac561a79b9f4cfd1d3d9da6
--- /dev/null
+++ b/_i18n/en/resources/developer-guides/daemon-rpc.md
@@ -0,0 +1,831 @@
+## Introduction
+
+This is a list of the monerod daemon RPC calls, their inputs and outputs, and examples of each.
+
+Many RPC calls use the daemon's JSON RPC interface while others use their own interfaces, as demonstrated below.
+
+Note: "atomic units" refer to the smallest fraction of 1 XMR according to the monerod implementation. **1 XMR = 1e12 atomic units.**
+
+### [JSON RPC Methods](#json-rpc-methods):
+
+* [getblockcount](#getblockcount)
+* [on_getblockhash](#on_getblockhash)
+* [getblocktemplate](#getblocktemplate)
+* [submitblock](#submitblock)
+* [getlastblockheader](#getlastblockheader)
+* [getblockheaderbyhash](#getblockheaderbyhash)
+* [getblockheaderbyheight](#getblockheaderbyheight)
+* [getblock](#getblock)
+* [get_connections](#get_connections)
+* [get_info](#get_info)
+* [hard_fork_info](#hard_fork_info)
+* [setbans](#setbans)
+* [getbans](#getbans)
+
+### [Other RPC Methods](#other-daemon-rpc-calls):
+
+* [/getheight](#getheight)
+* [/gettransactions](#gettransactions)
+* [/is_key_image_spent](#is_key_image_spent)
+* [/sendrawtransaction](#sendrawtransaction)
+* [/get_transaction_pool](#get_transaction_pool)
+* [/stop_daemon](#stop_daemon)
+
+
+---
+
+## JSON RPC Methods
+
+The majority of monerod RPC calls use the daemon's `json_rpc` interface to request various bits of information. These methods all follow a similar structure, for example:
+
+```
+IP=127.0.0.1
+PORT=18081
+METHOD='getblockheaderbyheight'
+PARAMS='{"height":912345}'
+curl \
+ -X POST http://$IP:$PORT/json_rpc \
+ -d '{"jsonrpc":"2.0","id":"0","method":"'$METHOD'","params":'$PARAMS'}' \
+ -H 'Content-Type: application/json'
+```
+
+Some methods include parameters, while others do not. Examples of each JSON RPC method follow.
+
+### **getblockcount**
+
+Look up how many blocks are in the longest chain known to the node.
+
+Inputs: *None*.
+
+Outputs:
+
+* *count* - unsigned int; Number of blocks in longest chain seen by the node.
+* *status* - string; General RPC error code. "OK" means everything looks good.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getblockcount"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "count": 993163,
+ "status": "OK"
+ }
+}
+```
+
+
+### **on_getblockhash**
+
+Look up a block's hash by its height.
+
+Inputs:
+
+* block height (int array of length 1)
+
+Outputs:
+
+* block hash (string)
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"on_getblockhash","params":[912345]}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": "e22cf75f39ae720e8b71b3d120a5ac03f0db50bba6379e2850975b4859190bc6"
+}
+```
+
+
+### **getblocktemplate**
+
+Inputs:
+
+* *wallet_address* - string; Address of wallet to receive coinbase transactions if block is successfully mined.
+* *reserve_size* - unsigned int; Reserve size.
+
+Outputs:
+
+* *blocktemplate_blob* - string; Blob on which to try to mine a new block.
+* *difficulty* - unsigned int; Difficulty of next block.
+* *height* - unsigned int; Height on which to mine.
+* *prev_hash* - string; Hash of the most recent block on which to mine the next block.
+* *reserved_offset* - unsigned int; Reserved offset.
+* *status* - string; General RPC error code. "OK" means everything looks good.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getblocktemplate","params":{"wallet_address":"44GBHzv6ZyQdJkjqZje6KLZ3xSyN1hBSFAnLP6EAqJtCRVzMzZmeXTC2AHKDS9aEDTRKmo6a6o9r9j86pYfhCWDkKjbtcns","reserve_size":60}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "blocktemplate_blob": "01029af88cb70568b84a11dc9406ace9e635918ca03b008f7728b9726b327c1b482a98d81ed83000000000018bd03c01ffcfcf3c0493d7cec7020278dfc296544f139394e5e045fcda1ba2cca5b69b39c9ddc90b7e0de859fdebdc80e8eda1ba01029c5d518ce3cc4de26364059eadc8220a3f52edabdaf025a9bff4eec8b6b50e3d8080dd9da417021e642d07a8c33fbe497054cfea9c760ab4068d31532ff0fbb543a7856a9b78ee80c0f9decfae01023ef3a7182cb0c260732e7828606052a0645d3686d7a03ce3da091dbb2b75e5955f01ad2af83bce0d823bf3dbbed01ab219250eb36098c62cbb6aa2976936848bae53023c00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001f12d7c87346d6b84e17680082d9b4a1d84e36dd01bd2c7f3b3893478a8d88fb3",
+ "difficulty": 982540729,
+ "height": 993231,
+ "prev_hash": "68b84a11dc9406ace9e635918ca03b008f7728b9726b327c1b482a98d81ed830",
+ "reserved_offset": 246,
+ "status": "OK"
+ }
+}
+```
+
+
+### **submitblock**
+
+Submit a mined block to the network.
+
+Inputs:
+
+* Block blob data - string
+
+Outputs:
+
+* *status* - string; Block submit status.
+
+
+### **getlastblockheader**
+
+Block header information for the most recent block is easily retrieved with this method. No inputs are needed.
+
+Inputs: *None*.
+
+Outputs:
+
+* *block_header* - A structure containing block header information.
+ * *depth* - unsigned int; The number of blocks succeeding this block on the blockchain. A larger number means an older block.
+ * *difficulty* - unsigned int; The strength of the Monero network based on mining power.
+ * *hash* - string; The hash of this block.
+ * *height* - unsigned int; The number of blocks preceding this block on the blockchain.
+ * *major_version* - unsigned int; The major version of the monero protocol at this block height.
+ * *minor_version* - unsigned int; The minor version of the monero protocol at this block height.
+ * *nonce* - unsigned int; a cryptographic random one-time number used in mining a Monero block.
+ * *orphan_status* - boolean; Usually `false`. If `true`, this block is not part of the longest chain.
+ * *prev_hash* - string; The hash of the block immediately preceding this block in the chain.
+ * *reward* - unsigned int; The amount of new atomic units generated in this block and rewarded to the miner. Note: 1 XMR = 1e12 atomic units.
+ * *timestamp* - unsigned int; The time the block was recorded into the blockchain.
+* *status* - string; General RPC error code. "OK" means everything looks good.
+
+In this example, the most recent block (990793 at the time) is returned:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getlastblockheader"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "block_header": {
+ "depth": 0,
+ "difficulty": 746963928,
+ "hash": "ac0f1e226268d45c99a16202fdcb730d8f7b36ea5e5b4a565b1ba1a8fc252eb0",
+ "height": 990793,
+ "major_version": 1,
+ "minor_version": 1,
+ "nonce": 1550,
+ "orphan_status": false,
+ "prev_hash": "386575e3b0b004ed8d458dbd31bff0fe37b280339937f971e06df33f8589b75c",
+ "reward": 6856609225169,
+ "timestamp": 1457589942
+ },
+ "status": "OK"
+ }
+}
+```
+
+
+### **getblockheaderbyhash**
+
+Block header information can be retrieved using either a block's hash or height. This method includes a block's hash as an input parameter to retrieve basic information about the block.
+
+Inputs:
+
+* *hash* - string; The block's sha256 hash.
+
+Outputs:
+
+* *block_header* - A structure containing block header information. See [getlastblockheader](#getlastblockheader).
+
+In this example, block 912345 is looked up by its hash:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getblockheaderbyhash","params":{"hash":"e22cf75f39ae720e8b71b3d120a5ac03f0db50bba6379e2850975b4859190bc6"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "block_header": {
+ "depth": 78376,
+ "difficulty": 815625611,
+ "hash": "e22cf75f39ae720e8b71b3d120a5ac03f0db50bba6379e2850975b4859190bc6",
+ "height": 912345,
+ "major_version": 1,
+ "minor_version": 2,
+ "nonce": 1646,
+ "orphan_status": false,
+ "prev_hash": "b61c58b2e0be53fad5ef9d9731a55e8a81d972b8d90ed07c04fd37ca6403ff78",
+ "reward": 7388968946286,
+ "timestamp": 1452793716
+ },
+ "status": "OK"
+ }
+}
+```
+
+
+### **getblockheaderbyheight**
+
+Similar to `getblockheaderbyhash` above, this method includes a block's height as an input parameter to retrieve basic information about the block.
+
+Inputs:
+
+* *height* - unsigned int; The block's height.
+
+Outputs:
+
+* *block_header* - A structure containing block header information. See [getlastblockheader](#getlastblockheader).
+
+In this example, block 912345 is looked up by its height (notice that the returned information is the save as in the previous example):
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getblockheaderbyheight","params":{"height":912345}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "block_header": {
+ "depth": 78376,
+ "difficulty": 815625611,
+ "hash": "e22cf75f39ae720e8b71b3d120a5ac03f0db50bba6379e2850975b4859190bc6",
+ "height": 912345,
+ "major_version": 1,
+ "minor_version": 2,
+ "nonce": 1646,
+ "orphan_status": false,
+ "prev_hash": "b61c58b2e0be53fad5ef9d9731a55e8a81d972b8d90ed07c04fd37ca6403ff78",
+ "reward": 7388968946286,
+ "timestamp": 1452793716
+ },
+ "status": "OK"
+ }
+}
+```
+
+
+### **getblock**
+
+Full block information can be retrieved by either block height or hash, like with the above block header calls. For full block information, both lookups use the same method, but with different input parameters.
+
+Inputs (pick one of the following):
+
+* *height* - unsigned int; The block's height.
+* *hash* - string; The block's hash.
+
+Outputs:
+
+* *blob* - string; Hexadecimal blob of block information.
+* *block_header* - A structure containing block header information. See [getlastblockheader](#getlastblockheader).
+* *json* - json string; JSON formatted block details:
+ * *major_version* - Same as in block header.
+ * *minor_version* - Same as in block header.
+ * *timestamp* - Same as in block header.
+ * *prev_id* - Same as `prev_hash` in block header.
+ * *nonce* - Same as in block header.
+ * *miner_tx* - Miner transaction information
+ * *version* - Transaction version number.
+ * *unlock_time* - The block height when the coinbase transaction becomes spendable.
+ * *vin* - List of transaction inputs:
+ * *gen* - Miner txs are coinbase txs, or "gen".
+ * *height* - This block height, a.k.a. when the coinbase is generated.
+ * *vout* - List of transaction outputs. Each output contains:
+ * *amount* - The amount of the output, in atomic units.
+ * *target* -
+ * *key* -
+ * *extra* - Usually called the "transaction ID" but can be used to include any random 32 byte/64 character hex string.
+ * *signatures* - Contain signatures of tx signers. Coinbased txs do not have signatures.
+ * *tx_hashes* - List of hashes of non-coinbase transactions in the block. If there are no other transactions, this will be an empty list.
+* *status* - string; General RPC error code. "OK" means everything looks good.
+
+**Look up by height:**
+
+In the following example, block 912345 is looked up by its height. Note that block 912345 does not have any non-coinbase transactions. (See the next example for a block with extra transactions):
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getblock","params":{"height":912345}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "blob": "...",
+ "block_header": {
+ "depth": 80694,
+ "difficulty": 815625611,
+ "hash": "e22cf75f39ae720e8b71b3d120a5ac03f0db50bba6379e2850975b4859190bc6",
+ "height": 912345,
+ "major_version": 1,
+ "minor_version": 2,
+ "nonce": 1646,
+ "orphan_status": false,
+ "prev_hash": "b61c58b2e0be53fad5ef9d9731a55e8a81d972b8d90ed07c04fd37ca6403ff78",
+ "reward": 7388968946286,
+ "timestamp": 1452793716
+ },
+ "json": "{\n \"major_version\": 1, \n \"minor_version\": 2, \n \"timestamp\": 1452793716, \n \"prev_id\": \"b61c58b2e0be53fad5ef9d9731a55e8a81d972b8d90ed07c04fd37ca6403ff78\", \n \"nonce\": 1646, \n \"miner_tx\": {\n \"version\": 1, \n \"unlock_time\": 912405, \n \"vin\": [ {\n \"gen\": {\n \"height\": 912345\n }\n }\n ], \n \"vout\": [ {\n \"amount\": 8968946286, \n \"target\": {\n \"key\": \"378b043c1724c92c69d923d266fe86477d3a5ddd21145062e148c64c57677008\"\n }\n }, {\n \"amount\": 80000000000, \n \"target\": {\n \"key\": \"73733cbd6e6218bda671596462a4b062f95cfe5e1dbb5b990dacb30e827d02f2\"\n }\n }, {\n \"amount\": 300000000000, \n \"target\": {\n \"key\": \"47a5dab669770da69a860acde21616a119818e1a489bb3c4b1b6b3c50547bc0c\"\n }\n }, {\n \"amount\": 7000000000000, \n \"target\": {\n \"key\": \"1f7e4762b8b755e3e3c72b8610cc87b9bc25d1f0a87c0c816ebb952e4f8aff3d\"\n }\n }\n ], \n \"extra\": [ 1, 253, 10, 119, 137, 87, 244, 243, 16, 58, 131, 138, 253, 164, 136, 195, 205, 173, 242, 105, 123, 61, 52, 173, 113, 35, 66, 130, 178, 250, 217, 16, 14, 2, 8, 0, 0, 0, 11, 223, 194, 193, 108\n ], \n \"signatures\": [ ]\n }, \n \"tx_hashes\": [ ]\n}",
+ "status": "OK"
+ }
+}
+```
+
+**Look up by hash:**
+
+In the following example, block 993056 is looked up by its hash. Note that block 993056 has 3 non-coinbase transactions:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getblock","params":{"hash":"510ee3c4e14330a7b96e883c323a60ebd1b5556ac1262d0bc03c24a3b785516f"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "blob": "...",
+ "block_header": {
+ "depth": 12,
+ "difficulty": 964985344,
+ "hash": "510ee3c4e14330a7b96e883c323a60ebd1b5556ac1262d0bc03c24a3b785516f",
+ "height": 993056,
+ "major_version": 1,
+ "minor_version": 2,
+ "nonce": 2036,
+ "orphan_status": false,
+ "prev_hash": "0ea4af6547c05c965afc8df6d31509ff3105dc7ae6b10172521d77e09711fd6d",
+ "reward": 6932043647005,
+ "timestamp": 1457720227
+ },
+ "json": "{\n \"major_version\": 1, \n \"minor_version\": 2, \n \"timestamp\": 1457720227, \n \"prev_id\": \"0ea4af6547c05c965afc8df6d31509ff3105dc7ae6b10172521d77e09711fd6d\", \n \"nonce\": 2036, \n \"miner_tx\": {\n \"version\": 1, \n \"unlock_time\": 993116, \n \"vin\": [ {\n \"gen\": {\n \"height\": 993056\n }\n }\n ], \n \"vout\": [ {\n \"amount\": 2043647005, \n \"target\": {\n \"key\": \"59e9d685b3484886bc7b47c133e6099ecdf212d5eaa16ce19cd58e8c3c1e590a\"\n }\n }, {\n \"amount\": 30000000000, \n \"target\": {\n \"key\": \"4c5e2f542d25513c46b9e3b7d40140a22d0ae5314bfcae492ad9f56fff8185f0\"\n }\n }, {\n \"amount\": 900000000000, \n \"target\": {\n \"key\": \"13dd8ffdac9e6a2f71e327dad65328198dc879a492d145eae72677c0703a3515\"\n }\n }, {\n \"amount\": 6000000000000, \n \"target\": {\n \"key\": \"62bda00341681dccbc066757862da593734395745bdfe1fdc89b5948c86a5d4c\"\n }\n }\n ], \n \"extra\": [ 1, 182, 145, 133, 28, 240, 87, 185, 195, 2, 163, 219, 202, 135, 158, 28, 186, 76, 196, 80, 97, 202, 85, 170, 166, 224, 60, 220, 103, 171, 158, 69, 80, 2, 8, 0, 0, 0, 12, 97, 127, 223, 22\n ], \n \"signatures\": [ ]\n }, \n \"tx_hashes\": [ \"79c6b9f00db027bde151705aafe85c495883aae2597d5cb8e1adb2e0f3ae1d07\", \"d715db73331abc3ec588ef07c7bb195786a4724b08dff431b51ffa32a4ce899b\", \"b197066426c0ed89f0b431fe171f7fd62bc95dd29943daa7cf3585cf1fdfc99d\"\n ]\n}",
+ "status": "OK",
+ "tx_hashes": ["79c6b9f00db027bde151705aafe85c495883aae2597d5cb8e1adb2e0f3ae1d07","d715db73331abc3ec588ef07c7bb195786a4724b08dff431b51ffa32a4ce899b","b197066426c0ed89f0b431fe171f7fd62bc95dd29943daa7cf3585cf1fdfc99d"]
+ }
+}
+```
+
+
+### **get_connections**
+
+Retrieve information about incoming and outgoing connections to your node.
+
+Inputs: *None*.
+
+Outputs:
+
+* *connections* - List of all connections and their info:
+ * *avg_download* - unsigned int; Average bytes of data downloaded by node.
+ * *avg_upload* - unsigned int; Average bytes of data uploaded by node.
+ * *current_download* - unsigned int; Current bytes downloaded by node.
+ * *current_upload* - unsigned int; Current bytes uploaded by node.
+ * *incoming* - boolean; Is the node getting information from your node?
+ * *ip* - string; The node's IP address.
+ * *live_time* - unsigned int
+ * *local_ip* - boolean
+ * *localhost* - boolean
+ * *peer_id* - string; The node's ID on the network.
+ * *port* - string; The port that the node is using to connect to the network.
+ * *recv_count* - unsigned int
+ * *recv_idle_time* - unsigned int
+ * *send_count* - unsigned int
+ * *send_idle_time* - unsigned int
+ * *state* - string
+
+Following is an example of `get_connections` and it's return:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_connections"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "connections": [{
+ "avg_download": 0,
+ "avg_upload": 0,
+ "current_download": 0,
+ "current_upload": 0,
+ "incoming": false,
+ "ip": "76.173.170.133",
+ "live_time": 1865,
+ "local_ip": false,
+ "localhost": false,
+ "peer_id": "3bfe29d6b1aa7c4c",
+ "port": "18080",
+ "recv_count": 116396,
+ "recv_idle_time": 23,
+ "send_count": 176893,
+ "send_idle_time": 1457726610,
+ "state": "state_normal"
+ },{
+ ...
+ }],
+ "status": "OK"
+ }
+}
+```
+
+
+### **get_info**
+
+Retrieve general information about the state of your node and the network.
+
+Inputs: *None*.
+
+Outputs:
+
+* *alt_blocks_count* - unsigned int; Number of alternative blocks to main chain.
+* *difficulty* - unsigned int; Network difficulty (analogous to the strength of the network)
+* *grey_peerlist_size* - unsigned int; Grey Peerlist Size
+* *height* - unsigned int; Current length of longest chain known to daemon.
+* *incoming_connections_count* - unsigned int; Number of peers connected to and pulling from your node.
+* *outgoing_connections_count* - unsigned int; Number of peers that you are connected to and getting information from.
+* *status* - string; General RPC error code. "OK" means everything looks good.
+* *target* - unsigned int; Current target for next proof of work.
+* *target_height* - unsigned int; The height of the next block in the chain.
+* *testnet* - boolean; States if the node is on the testnet (true) or mainnet (false).
+* *top_block_hash* - string; Hash of the highest block in the chain.
+* *tx_count* - unsigned int; Total number of non-coinbase transaction in the chain.
+* *tx_pool_size* - unsigned int; Number of transactions that have been broadcast but not included in a block.
+* *white_peerlist_size* - unsigned int; White Peerlist Size
+
+Following is an example `get_info` call and its return:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_info"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "alt_blocks_count": 5,
+ "difficulty": 972165250,
+ "grey_peerlist_size": 2280,
+ "height": 993145,
+ "incoming_connections_count": 0,
+ "outgoing_connections_count": 8,
+ "status": "OK",
+ "target": 60,
+ "target_height": 993137,
+ "testnet": false,
+ "top_block_hash": "",
+ "tx_count": 564287,
+ "tx_pool_size": 45,
+ "white_peerlist_size": 529
+ }
+}
+```
+
+
+### **hard_fork_info**
+
+Look up information regarding hard fork voting and readiness.
+
+Inputs: *None*.
+
+Outputs:
+
+* *earliest_height* - unsigned int; Block height at which hard fork would be enabled if voted in.
+* *enabled* - boolean; Tells if hard fork is enforced.
+* *state* - unsigned int; Current hard fork state: 0 (There is likely a hard fork), 1 (An update is needed to fork properly), or 2 (Everything looks good).
+* *status* - string; General RPC error code. "OK" means everything looks good.
+* *threshold* - unsigned int; Minimum percent of votes to trigger hard fork. Default is 80.
+* *version* - unsigned int; The major block version for the fork.
+* *votes* - unsigned int; Number of votes towards hard fork.
+* *voting* - unsigned int; Hard fork voting status.
+* *window* - unsigned int; Number of blocks over which current votes are cast. Default is 10080 blocks.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"hard_fork_info"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "earliest_height": 1009827,
+ "enabled": false,
+ "state": 2,
+ "status": "OK",
+ "threshold": 0,
+ "version": 1,
+ "votes": 7277,
+ "voting": 2,
+ "window": 10080
+ }
+}
+```
+
+
+### **setbans**
+
+Ban another node by IP.
+
+Inputs:
+
+* *bans* - A list of nodes to ban:
+ * *ip* - unsigned int; IP address to ban, in Int format.
+ * *ban* - boolean; Set `true` to ban.
+ * *seconds* - unsigned int; Number of seconds to ban node.
+
+Outputs:
+
+* *status* - string; General RPC error code. "OK" means everything looks good.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"setbans","params":{"bans":[{"ip":838969536,"ban":true,"seconds":30}]}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "status": "OK"
+ }
+}
+```
+
+
+### **getbans**
+
+Inputs: *None*.
+
+Outputs:
+
+* *bans* - List of banned nodes:
+ * *ip* - unsigned int; Banned IP address, in Int format.
+ * *seconds* - unsigned int; Local Unix time that IP is banned until.
+* *status* - string; General RPC error code. "OK" means everything looks good.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getbans"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "bans": [{
+ "ip": 838969536,
+ "seconds": 1457748792
+ }],
+ "status": "OK"
+ }
+}
+```
+
+
+---
+
+## Other Daemon RPC Calls
+
+Not all daemon RPC calls use the JSON_RPC interface. This section gives examples of these calls.
+
+The data structure for these calls is different than the JSON RPC calls. Whereas the JSON RPC methods were called using the `/json_rpc` extension and specifying a method, these methods are called at their own extensions. For example:
+
+ IP=127.0.0.1
+ PORT=18081
+ METHOD='gettransactions'
+ PARAMS='{"txs_hashes":["d6e48158472848e6687173a91ae6eebfa3e1d778e65252ee99d7515d63090408"]}'
+ curl \
+ -X POST http://$IP:$PORT/$METHOD \
+ -d $PARAMS \
+ -H 'Content-Type: application/json'
+
+Note: It is recommended to use JSON RPC where such alternatives exist, rather than the following methods. For example, the recommended way to get a node's height is via the JSON RPC methods [get_info](#getinfo) or [getlastblockheader](#getlastblockheader), rather than [getheight](#getheight) below.
+
+
+### **/getheight**
+
+Get the node's current height.
+
+Inputs: *None*.
+
+Outputs:
+
+* *height* - unsigned int; Current length of longest chain known to daemon.
+
+```
+$ curl -X POST http://127.0.0.1:18081/getheight -H 'Content-Type: application/json'
+
+{
+ "height": 993488,
+ "status": "OK"
+}
+```
+
+
+### **/gettransactions**
+
+Look up one or more transactions by hash.
+
+Inputs:
+
+* *txs_hashes* - string list; List of transaction hashes to look up.
+* *decode_as_json* - boolean; Optional. If set `true`, the returned transaction information will be decoded rather than binary.
+
+Outputs:
+
+* *status* - General RPC error code. "OK" means everything looks good.
+* *txs_as_hex* - string; Full transaction information as a hex string.
+* *txs_as_json* - json string; (Optional - returned if set in inputs.) List of transaction info:
+ * *version* - Transaction version
+ * *unlock_time* - If not 0, this tells when a transaction output is spendable.
+ * *vin* - List of inputs into transaction:
+ * *key* - The public key of the previous output spent in this transaction.
+ * *amount* - The amount of the input, in atomic units.
+ * *key_offsets* - A list of integer offets to the input.
+ * *k_image* - The key image for the given input
+ * *vout* - List of outputs from transaction:
+ * *amount* - Amount of transaction output, in atomic units.
+ * *target* - Output destination information:
+ * *key* - The stealth public key of the receiver. Whoever owns the private key associated with this key controls this transaction output.
+ * *extra* - Usually called the "payment ID" but can be used to include any random 32 bytes.
+ * *signatures* - List of ignatures used in ring signature to hide the true origin of the transaction.
+Example 1: Return transaction information in binary format.
+
+```
+$ curl -X POST http://127.0.0.1:18081/gettransactions -d '{"txs_hashes":["d6e48158472848e6687173a91ae6eebfa3e1d778e65252ee99d7515d63090408"]}' -H 'Content-Type: application/json'
+
+{
+ "status": "OK",
+ "txs_as_hex": ["..."]
+}
+```
+
+
+Example 2: Decode returned transaction information in JSON format. Note: the "vout" list has been truncated in the displayed return for space considerations.
+
+```
+$ curl -X POST http://127.0.0.1:18081/gettransactions -d '{"txs_hashes":["d6e48158472848e6687173a91ae6eebfa3e1d778e65252ee99d7515d63090408"],"decode_as_json":true}' -H 'Content-Type: application/json'
+
+{
+ "status": "OK",
+ "txs_as_hex": ["..."],
+ "txs_as_json": ["{\n \"version\": 1, \n \"unlock_time\": 0, \n \"vin\": [ {\n \"key\": {\n \"amount\": 70000000, \n \"key_offsets\": [ 35952\n ], \n \"k_image\": \"d16908468dff9438a9814fe96bdaa575f06fe8da85772b72e54926428712293d\"\n }\n }, {\n \"key\": {\n \"amount\": 400000000000000, \n \"key_offsets\": [ 6830\n ], \n \"k_image\": \"c7a7024b763df1181ae6fe821b70669735e38a68162ac02362e33acbe829b605\"\n }\n }\n ], \n \"vout\": [ {\n \"amount\": 50000, \n \"target\": {\n \"key\": \"f6be43f7be4f06adcb1d06f4a07c637c7359e009cf3e57bb32b8c9ea636509c3\"\n }\n }, {\n \"amount\": 200000, \n \"target\": {\n \"key\": \"b0a7a8e32f2b5302552bcd8d85112c62838b1f56cccd844eb9b63e0a732d0353\"\n }\n }, ... \n ], \n \"extra\": [ 1, 225, 240, 98, 34, 169, 73, 47, 237, 117, 192, 30, 192, 60, 155, 47, 4, 115, 20, 21, 11, 13, 252, 219, 129, 13, 174, 37, 36, 78, 191, 141, 109\n ], \n \"signatures\": [ \"e6a3be8003d481d2855c8127f56871de3d28a4fb52385b999eb986c831c5cc08361c126b0db24a21b6c4299b438ee2be201d44d57a371230b9cd04395ab8c400\", \"8309851abaf2cf2a7091e0cdb9c83704fa7d68838a7a8ef8c178bb55a1e93a038dd18bb4a7549dc056b7a70e037cabd80911a03f427e36f712756d4c00f38f0b\"]\n}"]
+}
+```
+
+
+### **/is_key_image_spent**
+
+Check if outputs have been spent using the key image associated with the output.
+
+Inputs:
+
+* *key_images* - string list; List of key image hex strings to check.
+
+Outputs:
+
+* *spent_status* - unsigned int list; List of statuses for each image checked. Statuses are follows: 0 = unspent, 1 = spent in blockchain, 2 = spent in transaction pool
+* *status* - string; General RPC error code. "OK" means everything looks good.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/is_key_image_spent -d '{"key_images":["8d1bd8181bf7d857bdb281e0153d84cd55a3fcaa57c3e570f4a49f935850b5e3","7319134bfc50668251f5b899c66b005805ee255c136f0e1cecbb0f3a912e09d4"]}' -H 'Content-Type: application/json'
+
+{
+ "spent_status": [1,2],
+ "status": "OK"
+}
+```
+
+
+### **/sendrawtransaction**
+
+Broadcast a raw transaction to the network.
+
+Inputs:
+
+* *tx_as_hex* - string; Full transaction information as hexidecimal string.
+
+Outputs:
+
+* *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.):
+
+
+```
+$ curl -X POST http://127.0.0.1:18081/sendrawtransaction -d '{"tx_as_hex":"de6a3..."}' -H 'Content-Type: application/json'
+```
+
+
+### **/get_transaction_pool**
+
+Show information about valid transactions seen by the node but not yet mined into a block, as well as spent key image information in the node's memory.
+
+Inputs: *None*.
+
+Outputs:
+
+* *spent_key_images* - List of spent output key images:
+ * *id_hash* - string; Key image ID hash.
+ * *txs_hashes* - string list; Key image transaction hashes.
+* *status* - string; General RPC error code. "OK" means everything looks good.
+* *transactions* - List of transactions in the mempool that have not been included in a block:
+ * *blob_size* - unsigned int; The size of the full transaction blob.
+ * *fee* - unsigned int; The amount of the mining fee included in the transaction, in atomic units.
+ * *id_hash* - string; The transaction ID hash.
+ * *kept_by_block* - boolean; We do not accept transactions that timed out before, unless set `true`.
+ * *last_failed_height* - unsigned int; If the transaction has previously timed out, this tells at what height that occured.
+ * *last_failed_id_hash* - string; Like the previous, this tells the previous transaction ID hash.
+ * *max_used_block_height* - unsigned int; Tells the height of the most recent block with an output used in this transaction.
+ * *max_used_block_hash* - string; Tells the hash of the most recent block with an output used in this transaction.
+ * *receive_time* - unsigned int; The Unix time that the transaction was first seen on the network by the node.
+ * *tx_json* - json string; JSON structure of all information in the transaction:
+ * *version* - Transaction version
+ * *unlock_time* - If not 0, this tells when a transaction output is spendable.
+ * *vin* - List of inputs into transaction:
+ * *key* - The public key of the previous output spent in this transaction.
+ * *amount* - The amount of the input, in atomic units.
+ * *key_offsets* - A list of integer offets to the input.
+ * *k_image* - The key image for the given input
+ * *vout* - List of outputs from transaction:
+ * *amount* - Amount of transaction output, in atomic units.
+ * *target* - Output destination information:
+ * *key* - The stealth public key of the receiver. Whoever owns the private key associated with this key controls this transaction output.
+ * *extra* - Usually called the "transaction ID" but can be used to include any random 32 bytes.
+ * *signatures* - List of ignatures used in ring signature to hide the true origin of the transaction.
+
+Example (Note: Some lists in the returned information have been truncated for display reasons):
+
+```
+$ curl -X POST http://127.0.0.1:18081/get_transaction_pool -H 'Content-Type: application/json'
+
+{
+ "spent_key_images": [{
+ "id_hash": "1edb9ecc39602040282d326070ad22cb473c952c0d6280c9c4c3b853fb34f3bc",
+ "txs_hashes": ["409911b2be02e3f0e930b326c67ab9e74675885ce23d71bb3bd28b62bc3e7803"]
+ },{
+ "id_hash": "4adb4bb63b3397027340ca4e6c45f4ce2147dfb3a4e0fafdec18834ae594a05e",
+ "txs_hashes": ["946f1f4c52e3426a41959c93b60078f314813bc4bdebcf69b8ee11d593b2bd14"]
+ },
+ ...],
+ "status": "OK",
+ "transactions": [{
+ "blob_size": 25761,
+ "fee": 290000000000,
+ "id_hash": "11d4cff23e610fac6a2b89187ad61d429a5e226652693dcac5d83d506eb92b96",
+ "kept_by_block": false,
+ "last_failed_height": 0,
+ "last_failed_id_hash": "0000000000000000000000000000000000000000000000000000000000000000",
+ "max_used_block_height": 954508,
+ "max_used_block_id_hash": "03f96b374778bc059e47b96e2beec2e6d4d9e0ad39afeabdbcd77e1bd5a62f81",
+ "receive_time": 1457676127,
+ "tx_json": "{\n \"version\": 1, \n \"unlock_time\": 0, \n \"vin\": [ {\n \"key\": {\n \"amount\": 70000000000, \n \"key_offsets\": [ 63408, 18978, 78357, 16560\n ], \n \"k_image\": \"7319134bfc50668251f5b899c66b005805ee255c136f0e1cecbb0f3a912e09d4\"\n }\n }, ... ], \n \"vout\": [ {\n \"amount\": 80000000000, \n \"target\": {\n \"key\": \"094e6a1b187385533665f89db741149f42d95fdc50bdd2a2384bcd1dc5209c55\"\n }\n }, ... ], \n \"extra\": [ 2, 33, 0, 15, 56, 190, 21, 169, 77, 13, 182, 209, 51, 35, 54, 96, 89, 237, 96, 23, 24, 107, 240, 79, 40, 86, 64, 68, 45, 166, 119, 192, 17, 225, 23, 1, 31, 159, 145, 15, 173, 255, 165, 192, 55, 84, 127, 154, 163, 25, 85, 204, 212, 127, 147, 133, 118, 218, 166, 52, 78, 188, 131, 235, 9, 159, 105, 158\n ], \n \"signatures\": [ \"966e5a67fbdbf72d7dc0364b705121a58e0ced7e2ab45747b6b154c05a1afe04fac4aac7f64faa2dc6dd4d51b8277f11e2f2ec7729fac225088befe3b8399c0b71a4cb55b9d0e20f93d305c78cebceff1bcfcfaf225428dfcfaaec630c88720ab65bf5d3399dd1ac82ea0ecf308b3f80d9780af7742fb157692cd60515a7e2086878f082117fa80fff3d257de7d3a2e9cc8b3472ef4a5e545d90e1159523a60f38d16cece783579627124776813334bdb2a2df4171ef1fa12bf415da338ce5085c01e7a715638ef5505aebec06a0625aaa72d13839838f7d4f981673c8f05f08408e8b372f900af7227c49cfb1e1febab6c07dd42b7c26f921cf010832841205\", ... ]\n}"
+ },
+ ...]
+}
+```
+
+
+### **/stop_daemon**
+
+Send a command to the daemon to safely disconnect and shut down.
+
+Inputs: *None*.
+
+Outputs:
+
+* *status* - string; General RPC error code. "OK" means everything looks good.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/stop_daemon -H 'Content-Type: application/json'
+
+{
+ "status": "OK"
+}
+```
\ No newline at end of file
diff --git a/_i18n/en/resources/developer-guides/wallet-rpc.md b/_i18n/en/resources/developer-guides/wallet-rpc.md
new file mode 100644
index 0000000000000000000000000000000000000000..e2cf8bc97fe8271eedf56d29aea11b3e4a1360e8
--- /dev/null
+++ b/_i18n/en/resources/developer-guides/wallet-rpc.md
@@ -0,0 +1,1215 @@
+## Introduction
+
+This is a list of the monero-wallet-rpc calls, their inputs and outputs, and examples of each. The program monero-wallet-rpc replaced the rpc interface that was in simplewallet and then monero-wallet-cli.
+
+All monero-wallet-rpc methods use the same JSON RPC interface. For example:
+
+```
+IP=127.0.0.1
+PORT=18082
+METHOD="make_integrated_address"
+PARAMS="{\"payment_id\":\"1234567890123456789012345678900012345678901234567890123456789000\"}"
+curl \
+ -X POST http://$IP:$PORT/json_rpc \
+ -d '{"jsonrpc":"2.0","id":"0","method":"'$METHOD'","params":'"$PARAMS"'}' \
+ -H 'Content-Type: application/json'
+```
+
+If the monero-wallet-rpc was executed with the `--rpc-login` argument as `username:password`, then follow this example:
+
+```
+IP=127.0.0.1
+PORT=18082
+METHOD="make_integrated_address"
+PARAMS="{\"payment_id\":\"1234567890123456789012345678900012345678901234567890123456789000\"}"
+curl \
+ -u username:password --digest \
+ -X POST http://$IP:$PORT/json_rpc \
+ -d '{"jsonrpc":"2.0","id":"0","method":"'$METHOD'","params":'"$PARAMS"'}' \
+ -H 'Content-Type: application/json'
+```
+
+Note: "atomic units" refer to the smallest fraction of 1 XMR according to the monerod implementation. **1 XMR = 1e12 atomic units.**
+
+### Index of JSON RPC Methods:
+
+* [getbalance](#getbalance)
+* [getaddress](#getaddress)
+* [getheight](#getheight)
+* [transfer](#transfer)
+* [transfer_split](#transfer_split)
+* [sweep_dust](#sweep_dust)
+* [sweep_all](#sweep_all)
+* [store](#store)
+* [get_payments](#get_payments)
+* [get_bulk_payments](#get_bulk_payments)
+* [get_transfers](#get_transfers)
+* [get_transfer_by_txid](#get_transfer_by_txid)
+* [incoming_transfers](#incoming_transfers)
+* [query_key](#query_key)
+* [make_integrated_address](#make_integrated_address)
+* [split_integrated_address](#split_integrated_address)
+* [stop_wallet](#stop_wallet)
+* [make_uri](#make_uri)
+* [parse_uri](#parse_uri)
+* [rescan_blockchain](#rescan_blockchain)
+* [set_tx_notes](#set_tx_notes)
+* [get_tx_notes](#get_tx_notes)
+* [sign](#sign)
+* [verify](#verify)
+* [export_key_images](#export_key_images)
+* [import_key_images](#import_key_images)
+* [get_address_book](#get_address_book)
+* [add_address_book](#add_address_book)
+* [delete_address_book](#delete_address_book)
+* [rescan_spent](#rescan_spent)
+* [start_mining](#start_mining)
+* [stop_mining](#stop_mining)
+* [get_languages](#get_languages)
+* [create_wallet](#create_wallet)
+* [open_wallet](#open_wallet)
+
+---
+
+## JSON RPC Methods:
+
+### **getbalance**
+
+Return the wallet's balance.
+
+Inputs: *None*.
+
+Outputs:
+
+* *balance* - unsigned int; The total balance of the current monero-wallet-rpc in session.
+* *unlocked_balance* - unsigned int; Unlocked funds are those funds that are sufficiently deep enough in the Monero blockchain to be considered safe to spend.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getbalance"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "balance": 140000000000,
+ "unlocked_balance": 50000000000
+ }
+}
+```
+
+
+### **getaddress**
+
+Return the wallet's address.
+
+Inputs: *None*.
+
+Outputs:
+
+* *address* - string; The 95-character hex address string of the monero-wallet-rpc in session.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getaddress"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "address": "427ZuEhNJQRXoyJAeEoBaNW56ScQaLXyyQWgxeRL9KgAUhVzkvfiELZV7fCPBuuB2CGuJiWFQjhnhhwiH1FsHYGQGaDsaBA"
+ }
+}
+```
+
+
+### **getheight**
+
+Returns the wallet's current block height.
+
+Inputs: *None*.
+
+Outputs:
+
+* *height* - unsigned int; The current monero-wallet-rpc's blockchain height. If the wallet has been offline for a long time, it may need to catch up with the daemon.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getheight"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "height": 994310
+ }
+}
+```
+
+
+### **transfer**
+
+Send monero to a number of recipients.
+
+Inputs:
+
+* *destinations* - array of destinations to receive XMR:
+ * *amount* - unsigned int; Amount to send to each destination, in atomic units.
+ * *address* - string; Destination public address.
+* *fee* - unsigned int; Ignored, will be automatically calculated.
+* *mixin* - unsigned int; Number of outpouts from the blockchain to mix with (0 means no mixing).
+* *unlock_time* - unsigned int; Number of blocks before the monero can be spent (0 to not add a lock).
+* *payment_id* - string; (Optional) Random 32-byte/64-character hex string to identify a transaction.
+* *get_tx_key* - boolean; (Optional) Return the transaction key after sending.
+* *priority* - unsigned int; Set a priority for the transaction. Accepted Values are: 0-3 for: default, unimportant, normal, elevated, priority.
+* *do_not_relay* - boolean; (Optional) If true, the newly created transaction will not be relayed to the monero network. (Defaults to false)
+* *get_tx_hex* - boolean; Return the transaction as hex string after sending
+
+
+Outputs:
+
+* *fee* - Integer value of the fee charged for the txn.
+* *tx_hash* - String for the publically searchable transaction hash
+* *tx_key* - String for the transaction key if get_tx_key is true, otherwise, blank string.
+* *tx_blob* - Transaction as hex string if get_tx_hex is true
+
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"transfer","params":{"destinations":[{"amount":100000000,"address":"9wNgSYy2F9qPZu7KBjvsFgZLTKE2TZgEpNFbGka9gA5zPmAXS35QzzYaLKJRkYTnzgArGNX7TvSqZC87tBLwtaC5RQgJ8rm"},{"amount":200000000,"address":"9vH5D7Fv47mbpCpdcthcjU34rqiiAYRCh1tYywmhqnEk9iwCE9yppgNCXAyVHG5qJt2kExa42TuhzQfJbmbpeGLkVbg8xit"}],"mixin":4,"get_tx_key": true}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "fee": 48958481211,
+ "tx_hash": "985180f468637bc6d2f72ee054e1e34b8d5097988bb29a2e0cb763e4464db23c",
+ "tx_key": "8d62e5637f1fcc9a8904057d6bed6c697618507b193e956f77c31ce662b2ee07"
+ }
+}
+```
+
+
+### **transfer_split**
+
+Same as transfer, but can split into more than one tx if necessary.
+
+Inputs:
+
+* *destinations* - array of destinations to receive XMR:
+ * *amount* - unsigned int; Amount to send to each destination, in atomic units.
+ * *address* - string; Destination public address.
+* *fee* - unsigned int; Ignored, will be automatically calculated.
+* *mixin* - unsigned int; Number of outpouts from the blockchain to mix with (0 means no mixing).
+* *unlock_time* - unsigned int; Number of blocks before the monero can be spent (0 to not add a lock).
+* *payment_id* - string; (Optional) Random 32-byte/64-character hex string to identify a transaction.
+* *get_tx_keys* - boolean; (Optional) Return the transaction keys after sending. -- Ignored
+* *priority* - unsigned int; Set a priority for the transactions. Accepted Values are: 0-3 for: default, unimportant, normal, elevated, priority.
+* *do_not_relay* - boolean; (Optional) If true, the newly created transaction will not be relayed to the monero network. (Defaults to false)
+* *get_tx_hex* - boolean; Return the transactions as hex string after sending
+* *new_algorithm* - boolean; True to use the new transaction construction algorithm, defaults to false.
+
+Outputs:
+
+* *fee_list* - array of: integer. The amount of fees paid for every transaction.
+* *tx_hash_list* - array of: string. The tx hashes of every transaction.
+* *tx_blob_list* - array of: string. The tx as hex string for every transaction.
+* *amount_list* - array of: integer. The amount transferred for every transaction..
+* *tx_key_list* - array of: string. The transaction keys for every transaction.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"transfer_split","params":{"destinations":[{"amount":100000000,"address":"9wNgSYy2F9qPZu7KBjvsFgZLTKE2TZgEpNFbGka9gA5zPmAXS35QzzYaLKJRkYTnzgArGNX7TvSqZC87tBwtaC5RQgJ8rm"},{"amount":200000000,"address":"9vH5D7Fv47mbpCpdcthcjU34rqiiAYRCh1tYywmhqnEk9iwCE9yppgNCXAyVHG5qJt2kExa42TuhzQfJbmbpeGLkVbg8xit"},{"amount":200000000,"address":"9vC5Q25cR1d3WzKX6dpTaLJaqZyDrtTnfadTmVuB1Wue2tyFGxUhiE4RGa74pEDJv7gSySzcd1Ao6G1nzSaqp78vLfP6MPj"},{"amount":200000000,"address":"A2MSrn49ziBPJBh8ZNEhhbfyLMou6mao4C1F5TLGUatmUnCxZArDYkcbAnVkVEopWVeak2rKDrmc8JpoS7n5dvfN9YDPBTG"},{"amount":200000000,"address":"9tEDyVQ8zgRQbDYiykTdpw5kZ6qWQWcKfExEj9eQshjpGb3sdr3UyWE2AHWzUGzJjaH9HN1DdGBdyQQ4AqGMc7rr5xYwZWW"}],"mixin":4,"get_tx_key": true, "new_algorithm": true}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "fee_list": [97916962422],
+ "tx_hash_list": ["c5c389846e701c27aaf1f7ab8b9dc457b471fcea5bc9710e8020d51275afbc54"]
+ }
+}
+```
+
+
+### **sweep_dust**
+
+Send all dust outputs back to the wallet's, to make them easier to spend (and mix).
+
+Inputs: *None*.
+
+Outputs:
+
+* *tx_hash_list* - list of: string
+
+Example (In this example, `sweep_dust` returns an error due to insufficient funds to sweep):
+
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"sweep_dust"}' -H 'Content-Type: application/json'
+
+{
+ "error": {
+ "code": -4,
+ "message": "not enough money"
+ },
+ "id": "0",
+ "jsonrpc": "2.0"
+}
+```
+
+### **sweep_all**
+
+Send all unlocked balance to an address.
+
+Inputs:
+
+* *address* - string; Destination public address.
+* *priority* - unsigned int; (Optional)
+* *mixin* - unsigned int; Number of outpouts from the blockchain to mix with (0 means no mixing).
+* *unlock_time* - unsigned int; Number of blocks before the monero can be spent (0 to not add a lock).
+* *payment_id* - string; (Optional) Random 32-byte/64-character hex string to identify a transaction.
+* *get_tx_keys* - boolean; (Optional) Return the transaction keys after sending.
+* *below_amount* - unsigned int; (Optional)
+* *do_not_relay* - boolean; (Optional)
+* *get_tx_hex* - boolean; (Optional) return the transactions as hex encoded string.
+
+Outputs:
+
+* *tx_hash_list* - array of string;
+* *tx_key_list* - array of string;
+* *tx_blob_list* - array of string;
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"sweep_all","params":{"address":"9sS8eRU2b5ZbN2FPSrpkiab1bjbHE5XtL6Ti6We3Fhw5aQPudRfVVypjgzKDNkxtvTQSPs122NKggb2mqcqkKSeMNVu59S","mixin":2,"unlock_time":0,"get_tx_keys":true}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "tx_hash_list": ["53a3648797d5524dd037d4105e067fa61468faecab41927fc43adbb26c202d22"],
+ "tx_key_list": ["e83b3b78235e36cd7e4d9695efd81a3b3e64c7d1f1ebd61892f0a7add6a50301"]
+ }
+}
+```
+
+### **store**
+
+Save the blockchain.
+
+Inputs: *None*.
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"store"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **get_payments**
+
+Get a list of incoming payments using a given payment id.
+
+Inputs:
+
+* *payment_id* - string
+
+Outputs:
+
+* *payments* - list of:
+ * *payment_id* - string
+ * *tx_hash* - string
+ * *amount* - unsigned int
+ * *block_height* - unsigned int
+ * *unlock_time* - unsigned int
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_payments","params":{"payment_id":"4279257e0a20608e25dba8744949c9e1caff4fcdafc7d5362ecf14225f3d9030"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "payments": [{
+ "amount": 10350000000000,
+ "block_height": 994327,
+ "payment_id": "4279257e0a20608e25dba8744949c9e1caff4fcdafc7d5362ecf14225f3d9030",
+ "tx_hash": "c391089f5b1b02067acc15294e3629a463412af1f1ed0f354113dd4467e4f6c1",
+ "unlock_time": 0
+ }]
+ }
+}
+```
+
+
+### **get_bulk_payments**
+
+Get a list of incoming payments using a given payment id, or a list of payments ids, from a given height. This method is the preferred method over `get_payments` because it has the same functionality but is more extendable. Either is fine for looking up transactions by a single payment ID.
+
+Inputs:
+
+* *payment_ids* - array of: string
+ * *min_block_height* - unsigned int; The block height at which to start looking for payments.
+
+Outputs:
+
+* *payments* - list of:
+ * *payment_id* - string
+ * *tx_hash* - string
+ * *amount* - unsigned int
+ * *block_height* - unsigned int
+ * *unlock_time* - unsigned int
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_bulk_payments","params":{"payment_ids":["4279257e0a20608e25dba8744949c9e1caff4fcdafc7d5362ecf14225f3d9030"],"min_block_height":990000}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "payments": [{
+ "amount": 10350000000000,
+ "block_height": 994327,
+ "payment_id": "4279257e0a20608e25dba8744949c9e1caff4fcdafc7d5362ecf14225f3d9030",
+ "tx_hash": "c391089f5b1b02067acc15294e3629a463412af1f1ed0f354113dd4467e4f6c1",
+ "unlock_time": 0
+ }]
+ }
+}
+```
+
+
+### **get_transfers**
+
+Returns a list of transfers.
+
+Inputs:
+
+* *in* - boolean;
+* *out* - boolean;
+* *pending* - boolean;
+* *failed* - boolean;
+* *pool* - boolean;
+* *filter_by_height* - boolean;
+* *min_height* - unsigned int;
+* *max_height* - unsigned int;
+
+Outputs:
+
+* *in* array of transfers:
+ * *txid* - string;
+ * *payment_id* - string;
+ * *height* - unsigned int;
+ * *timestamp* - unsigned int;
+ * *amount* - unsigned int;
+ * *fee* - unsigned int;
+ * *note* - string;
+ * *destinations* - std::list<transfer_destination>;
+ * *type* - string;
+* *out* array of transfers
+* *pending* array of transfers
+* *failed* array of transfers
+* *pool* array of transfers
+
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_transfers","params":{"pool":true}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "pool": [{
+ "amount": 500000000000,
+ "fee": 0,
+ "height": 0,
+ "note": "",
+ "payment_id": "758d9b225fda7b7f",
+ "timestamp": 1488312467,
+ "txid": "da7301d5423efa09fabacb720002e978d114ff2db6a1546f8b820644a1b96208",
+ "type": "pool"
+ }]
+ }
+}
+```
+
+### **get_transfer_by_txid**
+
+Show information about a transfer to/from this address.
+
+Inputs:
+
+* *txid* - string
+
+Outputs:
+
+* *transfer* - JSON object containing parment information:
+ * *amount* - unsigned int
+ * *fee* - unsigned int
+ * *height* - unsigned int
+ * *note* - string
+ * *payment_id* - string
+ * *timestamp* - unsigned int
+ * *txid* - string
+ * *type* - string
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_transfer_by_txid","params":{"txid":"f2d33ba969a09941c6671e6dfe7e9456e5f686eca72c1a94a3e63ac6d7f27baf"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "transfer": {
+ "amount": 10000000000000,
+ "fee": 0,
+ "height": 1316388,
+ "note": "",
+ "payment_id": "0000000000000000",
+ "timestamp": 1495539310,
+ "txid": "f2d33ba969a09941c6671e6dfe7e9456e5f686eca72c1a94a3e63ac6d7f27baf",
+ "type": "in"
+ }
+ }
+}
+```
+
+
+### **incoming_transfers**
+
+Return a list of incoming transfers to the wallet.
+
+Inputs:
+
+* *transfer_type* - string; "all": all the transfers, "available": only transfers which are not yet spent, OR "unavailable": only transfers which are already spent.
+
+Outputs:
+
+* *transfers* - list of:
+ * *amount* - unsigned int
+ * *spent* - boolean
+ * *global_index* - unsigned int; Mostly internal use, can be ignored by most users.
+ * *tx_hash* - string; Several incoming transfers may share the same hash if they were in the same transaction.
+ * *tx_size* - unsigned int
+
+Example (Return "all" transaction types):
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"incoming_transfers","params":{"transfer_type":"all"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "transfers": [{
+ "amount": 10000000000000,
+ "global_index": 711506,
+ "spent": false,
+ "tx_hash": "<c391089f5b1b02067acc15294e3629a463412af1f1ed0f354113dd4467e4f6c1>",
+ "tx_size": 5870
+ },{
+ "amount": 300000000000,
+ "global_index": 794232,
+ "spent": false,
+ "tx_hash": "<c391089f5b1b02067acc15294e3629a463412af1f1ed0f354113dd4467e4f6c1>",
+ "tx_size": 5870
+ },{
+ "amount": 50000000000,
+ "global_index": 213659,
+ "spent": false,
+ "tx_hash": "<c391089f5b1b02067acc15294e3629a463412af1f1ed0f354113dd4467e4f6c1>",
+ "tx_size": 5870
+ }]
+ }
+}
+```
+
+Example (Return "available" transactions):
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"incoming_transfers","params":{"transfer_type":"available"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "transfers": [{
+ "amount": 10000000000000,
+ "global_index": 711506,
+ "spent": false,
+ "tx_hash": "<c391089f5b1b02067acc15294e3629a463412af1f1ed0f354113dd4467e4f6c1>",
+ "tx_size": 5870
+ },{
+ "amount": 300000000000,
+ "global_index": 794232,
+ "spent": false,
+ "tx_hash": "<c391089f5b1b02067acc15294e3629a463412af1f1ed0f354113dd4467e4f6c1>",
+ "tx_size": 5870
+ },{
+ "amount": 50000000000,
+ "global_index": 213659,
+ "spent": false,
+ "tx_hash": "<c391089f5b1b02067acc15294e3629a463412af1f1ed0f354113dd4467e4f6c1>",
+ "tx_size": 5870
+ }]
+ }
+}
+```
+
+Example (Return "unavailable" transaction. Note that this particular example returns 0 unavailable transactions):
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"incoming_transfers","params":{"transfer_type":"unavailable"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **query_key**
+
+Return the spend or view private key.
+
+Inputs:
+
+* *key_type* - string; Which key to retrieve: "mnemonic" - the mnemonic seed (older wallets do not have one) OR "view_key" - the view key
+
+Outputs:
+
+* *key* - string; The view key will be hex encoded, while the mnemonic will be a string of words.
+
+Example (Query view key):
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"query_key","params":{"key_type":"view_key"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "key": "7e341d..."
+ }
+}
+```
+
+Example (Query mnemonic key):
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"query_key","params":{"key_type":"mnemonic"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "key": "adapt adapt nostril ..."
+ }
+}
+```
+
+
+### **make_integrated_address**
+
+Make an integrated address from the wallet address and a payment id.
+
+Inputs:
+
+* *payment_id* - string; hex encoded; can be empty, in which case a random payment id is generated
+
+Outputs:
+
+* *integrated_address* - string
+
+Example (Payment ID is empty, use a random ID):
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"make_integrated_address","params":{"payment_id":""}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "integrated_address": "4BpEv3WrufwXoyJAeEoBaNW56ScQaLXyyQWgxeRL9KgAUhVzkvfiELZV7fCPBuuB2CGuJiWFQjhnhhwiH1FsHYGQQ8H2RRJveAtUeiFs6J"
+ }
+}
+```
+
+
+### **split_integrated_address**
+
+Retrieve the standard address and payment id corresponding to an integrated address.
+
+Inputs:
+
+* *integrated_address* - string
+
+Outputs:
+
+* *standard_address* - string
+* *payment* - string; hex encoded
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"split_integrated_address","params":{"integrated_address": "4BpEv3WrufwXoyJAeEoBaNW56ScQaLXyyQWgxeRL9KgAUhVzkvfiELZV7fCPBuuB2CGuJiWFQjhnhhwiH1FsHYGQQ8H2RRJveAtUeiFs6J"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "payment_id": "<420fa29b2d9a49f5>",
+ "standard_address": "427ZuEhNJQRXoyJAeEoBaNW56ScQaLXyyQWgxeRL9KgAUhVzkvfiELZV7fCPBuuB2CGuJiWFQjhnhhwiH1FsHYGQGaDsaBA"
+ }
+}
+```
+
+
+### **stop_wallet**
+
+Stops the wallet, storing the current state.
+
+Inputs: *None*.
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"stop_wallet"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **make_uri**
+
+Create a payment URI using the official URI spec.
+
+Inputs:
+
+* *address* - wallet address string
+* *amount* (optional) - the integer amount to receive, in **atomic** units
+* *payment_id* (optional) - 16 or 64 character hexadecimal payment id string
+* *recipient_name* (optional) - string name of the payment recipient
+* *tx_description* (optional) - string describing the reason for the tx
+
+Outputs:
+
+* *uri* - a string containing all the payment input information as a properly formatted payment URI
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"make_uri","params":{"address":"44AFFq5kSiGBoZ4NMDwYtN18obc8AemS33DBLWs3H7otXft3XjrpDtQGv7SqSsaBYBb98uNbr2VBBEt7f2wfn3RVGQBEP3A","amount":10,"payment_id":"0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef","tx_description":"Testing out the make_uri function.","recipient_name":"Monero Project donation address"}}' -H 'Content-Type: application/json'
+
+{
+ "id": 0,
+ "jsonrpc": "2.0",
+ "result": {
+ "uri": "monero:44AFFq5kSiGBoZ4NMDwYtN18obc8AemS33DBLWs3H7otXft3XjrpDtQGv7SqSsaBYBb98uNbr2VBBEt7f2wfn3RVGQBEP3A?tx_payment_id=0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef&tx_amount=0.000000000010&recipient_name=Monero%20Project%20donation%20address&tx_description=Testing%20out%20the%20make_uri%20function."
+ }
+}
+```
+
+
+### **parse_uri**
+
+Parse a payment URI to get payment information.
+
+Inputs:
+
+* *uri* - a string containing all the payment input information as a properly formatted payment URI
+
+Outputs:
+
+* *uri* - JSON object containing payment information:
+ * *address* - wallet address string
+ * *amount* - the decimal amount to receive, in **coin** units (0 if not provided)
+ * *payment_id* - 16 or 64 character hexadecimal payment id string (empty if not provided)
+ * *recipient_name* - string name of the payment recipient (empty if not provided)
+ * *tx_description* - string describing the reason for the tx (empty if not provided)
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"parse_uri","params":{"uri":"monero:44AFFq5kSiGBoZ4NMDwYtN18obc8AemS33DBLWs3H7otXft3XjrpDtQGv7SqSsaBYBb98uNbr2VBBEt7f2wfn3RVGQBEP3A?tx_payment_id=0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef&tx_amount=0.000000000010&recipient_name=Monero%20Project%20donation%20address&tx_description=Testing%20out%20the%20make_uri%20function."}}' -H 'Content-Type: application/json'
+
+{
+ "id": 0,
+ "jsonrpc": "2.0",
+ "result": {
+ "uri": {
+ "address": "44AFFq5kSiGBoZ4NMDwYtN18obc8AemS33DBLWs3H7otXft3XjrpDtQGv7SqSsaBYBb98uNbr2VBBEt7f2wfn3RVGQBEP3A",
+ "amount": 10,
+ "payment_id": "0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef",
+ "recipient_name": "Monero Project donation address",
+ "tx_description": "Testing out the make_uri function."
+ }
+ }
+}
+```
+
+
+### **rescan_blockchain**
+
+Rescan blockchain from scratch.
+
+Inputs: *None*.
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"rescan_blockchain" -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **set_tx_notes**
+
+Set arbitrary string notes for transactions.
+
+Inputs:
+
+* *txids* - array of string; transaction ids
+* *notes* - array of string; notes for the transactions
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"set_tx_notes","params":{"txids":["6a1a100c079c236e2cbf36f7760e8ef1a9e8357c434aa790a8c78de653ec4cf2"],"notes":["This is an example"]}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **get_tx_notes**
+
+Get string notes for transactions.
+
+Inputs:
+
+* *txids* - array of string; transaction ids
+
+Outputs:
+
+* *notes* - array of string; notes for the transactions
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_tx_notes","params":{"txids":["6a1a100c079c236e2cbf36f7760e8ef1a9e8357c434aa790a8c78de653ec4cf2"]}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "notes": ["This is an example"]
+ }
+}
+```
+
+
+### **sign**
+
+Sign a string.
+
+Inputs:
+
+* *data* - string;
+
+Outputs:
+
+* *signature* - string;
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"sign","params":{"data":"This is sample data to be signed"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "signature": "SigV1Xp61ZkGguxSCHpkYEVw9eaWfRfSoAf36PCsSCApx4DUrKWHEqM9CdNwjeuhJii6LHDVDFxvTPijFsj3L8NDQp1TV"
+ }
+}
+```
+
+
+### **verify**
+
+Verify a signature on a string.
+
+Inputs:
+
+* *data* - string;
+* *address* - string;
+* *signature* - string;
+
+Outputs:
+
+* *good* - boolean;
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"verify","params":{"data":"This is sample data to be signed","address":"9sS8eRU2b5ZbN2FPSrpkiab1bjbHE5XtL6Ti6We3Fhw5aQPudRfVVypjgzKDNkxtvTQZSPs122NKggb2mqcqkKSeMNVu59S","signature":"SigV1Xp61ZkGguxSCHpkYEVw9eaWfRfSoAf36PCsSCApx4DUrKWHEqM9CdNwjeuhJii6LHDVDFxvTPijFsj3L8NDQp1TV"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "good": true
+ }
+}
+```
+
+
+### **export_key_images**
+
+Export a signed set of key images.
+
+Inputs: *None*.
+
+Outputs:
+
+* *signed_key_images* - array of signed key images:
+ * *key_image* - string;
+ * *signature* - string;
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"export_key_images"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "signed_key_images": [{
+ "key_image": "62b83df78baad99e23b5ad3f667bc6f8d388a13d9e84c7bb6c223a556dfd34af",
+ "signature": "b87b7e989aa85aa3a2a7cd8adcb3a848d3512ff718b168e15217ff3e5da29c0183c0328b97cc052fcb5ee3548aa5e41e530ba9d854199ea19d7ddaf6a54a4c0a"
+ }]
+ }
+}
+```
+
+
+### **import_key_images**
+
+Import signed key images list and verify their spent status.
+
+Inputs:
+
+* *signed_key_images* - array of signed key images:
+ * *key_image* - string;
+ * *signature* - string;
+
+Outputs:
+
+* *height* - unsigned int;
+* *spent* - unsigned int;
+* *unspent* - unsigned int;
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"import_key_images", "params":{"signed_key_images":[{"key_image":"63b83df78cafd99e23b5ad3f667bc6f8d38813d9e84c7bb6c223a556dfd34af","signature":"b87b7e989aa86aa2a7a7cd8adcb3a848d3512ff718b168e15217ff3e5da29c0183c0328b97cc052fcb5ee3548aa5e41e530ba9d854199ea19d7ddaf6a54a4c0a"},{"key_image":"44ec12fbc56c533a30b09de8ae26febd515528c4957dfe875430377a7e212b4e","signature":"91105f15be0b25bc2a94bd78a7e261608974d6d888080b9f1815655b98af190340325ea1a0840a5951dacf913d4de1b2bd33ea59c1cb7bce1b6648afa7133d03"}]}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "height": 986050,
+ "spent": 10000100000000,
+ "unspent": 4979852760000
+ }
+}
+```
+
+
+### **get_address_book**
+
+Retrieves entries from the address book.
+
+Inputs:
+
+* *entries* - array of unsigned int; indices of the requested address book entries
+
+Outputs:
+
+* *entries* - array of entries:
+ * *address* - string;
+ * *description* - string;
+ * *index* - unsigned int;
+ * *payment_id* - string;
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_address_book","params":{"entries":[1,2]}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "entries": [{
+ "address": "A135xq3GVMdU5qtAm4hN7zjPgz8bRaiSUQmtuDdjZ6CgXayvQruJy3WPe95qj873JhK4YdTQjoR39Leg6esznQk8PckhjRN",
+ "description": "",
+ "index": 1,
+ "payment_id": "0000000000000000000000000000000000000000000000000000000000000000"
+ },{
+ "address": "A135xq3GVMdU5qtAm4hN7zjPgz8bRaiSUQmtuDdjZ6CgXayvQruJy3WPe95qj873JhK4YdTQjoR39Leg6esznQk8PckhjRN",
+ "description": "",
+ "index": 2,
+ "payment_id": "0000000000000000000000000000000000000000000000000000000000000000"
+ }]
+ }
+}
+```
+
+
+### **add_address_book**
+
+Add an entry to the address book.
+
+Inputs:
+
+* *address* - string;
+* *payment_id* - (optional) string, defaults to "0000000000000000000000000000000000000000000000000000000000000000";
+* *description* - (optional) string, defaults to "";
+
+Outputs:
+
+* *index* - unsigned int; The index of the address book entry.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"add_address_book","params":{"address":"44AFFq5kSiGBoZ4NMDwYtN18obc8AemS33DBLWs3H7otXft3XjrpDtQGv7SqSsBYBb98uNbr2VBBEt7f2wfn3RVGQBEP3A","description":"Donation address for the Monero project"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "index": 2
+ }
+}
+```
+
+
+### **delete_address_book**
+
+Delete an entry from the address book.
+
+Inputs:
+
+* *index* - unsigned int; The index of the address book entry.
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"delete_address_book","params":{"index":0}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **rescan_spent**
+
+Rescan the blockchain for spent outputs.
+
+Inputs: *None*.
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"rescan_spent"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **start_mining**
+
+Start mining in the Monero daemon.
+
+Inputs:
+
+* *threads_count* - unsigned int; Number of threads created for mining
+* *do_background_mining* - boolean;
+* *ignore_battery* - boolean;
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"start_mining","params":{"threads_count":1,"do_background_mining":true,"ignore_battery":true}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **stop_mining**
+
+Stop mining in the Monero daemon.
+
+Inputs: *None*.
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"stop_mining"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **get_languages**
+
+Get a list of available languages for your wallet's seed.
+
+Inputs: *None*.
+
+Outputs:
+
+* *languages* - array of string; List of available languages
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_languages"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "languages": ["Deutsch","English","Español","Français","Italiano","Nederlands","Português","руÑÑкий Ñзык","日本語","简体ä¸æ–‡ (ä¸å›½)","Esperanto"]
+ }
+}
+```
+
+
+### **create_wallet**
+
+Create a new wallet. You need to have set the argument "--wallet-dir" when launching monero-wallet-rpc to make this work.
+
+Inputs:
+
+* *filename* - string;
+* *password* - string;
+* *language* - string; Language for your wallets' seed.
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"create_wallet","params":{"filename":"mytestwallet","password":"mytestpassword","language":"English"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **open_wallet**
+
+Open a wallet. You need to have set the argument "--wallet-dir" when launching monero-wallet-rpc to make this work.
+
+Inputs:
+
+* *filename* - string;
+* *password* - string;
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"open_wallet","params":{"filename":"mytestwallet","password":"mytestpassword"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
diff --git a/_i18n/en/resources/moneropedia/00-base-00 b/_i18n/en/resources/moneropedia/00-base-00
new file mode 100644
index 0000000000000000000000000000000000000000..ccfa17812230473e626c898f7f40e50c1938a8de
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/00-base-00
@@ -0,0 +1,10 @@
+---
+layout: moneropedia
+entry: ""
+terms: ["", ""]
+summary: ""
+---
+
+### The Basics
+
+{{ page.summary | capitalize }}.
\ No newline at end of file
diff --git a/_i18n/en/resources/moneropedia/account.md b/_i18n/en/resources/moneropedia/account.md
new file mode 100644
index 0000000000000000000000000000000000000000..8014c8ee5015268c05066097bcc1a3f3324220c7
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/account.md
@@ -0,0 +1,82 @@
+---
+layout: moneropedia
+entry: "Account"
+terms: ["account", "accounts", "wallet", "wallets"]
+summary: "similar in function to a bank account, contains all of your sent and received transactions"
+---
+
+### The Basics
+
+Those familiar with Monero's predecessors will be more familiar with the term *wallet* to describe this. In Monero we call this an account, and it is a private account owned and operated by a Monero user.
+
+Your account contains all of the Monero @transactions you have sent and received. Your account balance is a sum of all the Monero you've received, less the Monero you've sent. When using Monero you may notice that your account has two balances, a locked and an unlocked balance. The unlocked balance contains funds that can be spent immediately, and the locked balance contains funds that you can't spend right now. You may receive a transaction that has an @unlock-time set, or you may have sent some Monero and are waiting for the @change to come back to your wallet, both situations that could lead to those funds being locked for a time.
+
+A key difference between traditional electronic currency and Monero is that your account resides only under your control, normally on your computer, and cannot be accessed by anyone else if you [practice good security](#practicing-good-security).
+
+### Multiple Accounts
+
+There are no costs attached to creating a Monero account, and there are no fees charged except for individual @transaction fees that go to @miners.
+
+This means that individuals can easily create a Monero account for themselves as well as a joint account to share with their partner, and individual accounts for their children. Similarly, a business could create separate accounts for each division or group. Since Monero's @transaction fees are quite low, moving funds between accounts is not an expensive exercise.
+
+### Cryptographic Keys
+
+Monero relies heavily on a cryptography principle known as *public/private key cryptography* or *asymmetric cryptography*, which is thoroughly detailed in [this Wikipedia article](https://en.wikipedia.org/wiki/Public-key_cryptography).
+
+Your account is based on two keys, a @spend-key and a @view-key. The @spend-key is special in that it is the single key required to spend your Monero funds, whereas the @view-key allows you to reveal your @transactions to a third party, for example for auditing or accounting purposes. These keys in your account also play an important role in Monero's @transaction-privacy.
+
+The private keys for both of these must be protected by you in order to retain your account privacy. On the other hand, the public keys are obviously public (they are part of your Monero account address). For normal public/private key cryptography someone could send you a private message by encrypting it with either of your public keys, and you would then be the only one able to decrypt it with your private keys.
+
+### Backing Up Your Account
+
+When you manage your own Monero Account with the private @spend-key, you are solely responsible for the security of your funds. Thankfully, Monero makes it very easy to backup your account. When creating a Monero account for the first time you will be given a unique @mnemonic-seed for your account that consists of 13 or 25 words in the language of your choosing. **This seed is the only thing you need to backup for your account**, and so it is imperative that it is written down and stored securely. Never store this seed in a form or location that would allow someone else to see it!
+
+```
+List of available languages for your wallet's seed:
+0 : Deutsch
+1 : English
+2 : Español
+3 : Français
+4 : Italiano
+5 : Nederlands
+6 : Português
+7 : руÑÑкий Ñзык
+8 : 日本語
+9 : 简体ä¸æ–‡ (ä¸å›½)
+10 : Esperanto
+Enter the number corresponding to the language of your choice: 1
+Generated new wallet: 4B15ZjveuttEaTmfZjLVioPVw7bfSmRLpSgB33CJbuC6BoGtZrug9TDAmhZEWD6XoFDGz55bgzisT9Dnv61sbsA6Sa47TYu
+view key: 4130fa26463d9451781771a8baa5d0b8085c47c4500cefe4746bab48f1d15903
+**********************************************************************
+Your wallet has been generated.
+To start synchronizing with the daemon, use "refresh" command.
+Use "help" command to see the list of available commands.
+Always use "exit" command when closing monero-wallet-cli to save your
+current session's state. Otherwise, you might need to synchronize
+your wallet again (your wallet keys are NOT at risk in any case).
+
+PLEASE NOTE: the following 25 words can be used to recover access to your wallet. Please write them down and store them somewhere safe and secure. Please do not store them in your email or on file storage services outside of your immediate control.
+
+aunt knuckle italics moisture hawk thorn iris abort
+chlorine smog uphill glass aptitude nowhere sewage plywood
+dual relic fierce divers anvil nodes bubble cabin abort
+**********************************************************************
+Starting refresh...
+Refresh done, blocks received: 21939
+Balance: 0.000000000000, unlocked balance: 0.000000000000
+Background refresh thread started
+[wallet 4B15Zj]: â–ˆ
+
+```
+
+As the example above indicates, it is incredibly important to store these words in safe locations. If you are concerned about the risk of critical loss at your home, for instance, you may want to store a second copy of your seed with your attorney or in a safety deposit box. It is also recommended that it is stored in a way that does not make it obvious that it is your seed, so writing it into a letter or as part of other notes is advisable.
+
+### Practicing Good Security
+
+Over and above backing up your @mnemonic-seed so that you have access to your account in the event of critical data loss, it is also important to practice good security. Use a secure password when creating a local Monero account (not used on [MyMonero](https://mymonero.com) or other web-based account systems).
+
+Don't ever give your Monero account password to anyone, as this can be used to access the Monero on your computer without knowing your @mnemonic-seed. Similarly, make sure you have running and up-to-date antivirus, especially on Windows computers. Finally, be careful when clicking links in emails or on unknown and untrusted websites, as malware installed on your computer can sit and wait for you to access your Monero account before taking the funds from it.
+
+### Leaving Your Account to Next of Kin
+
+Providing access to your Monero account to your next of kin is just as easy as it is to backup your Monero account. Simply leave your @mnemonic-seed to them in your will, or store it somewhere safe where it will be given to them upon the execution of your will. A key advantage to this is that your next of kin won't have to wait for months for a third party to release the funds to them.
diff --git a/_i18n/en/resources/moneropedia/address-book.md b/_i18n/en/resources/moneropedia/address-book.md
new file mode 100644
index 0000000000000000000000000000000000000000..43b159c94ef29d9f8deb12af5b1294c5e2268b28
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/address-book.md
@@ -0,0 +1,35 @@
+---
+layout: moneropedia
+entry: "Address Book"
+tags: ["kovri"]
+terms: ["Address-Book"]
+summary: "Allows you to visit I2P websites/services that have the .i2p domain"
+---
+
+### The Basics
+
+In order to browse @I2P sites or services with @Kovri, you'll need an address book. An address book will allow you to translate @I2P websites/services that use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain) into an address that @I2P network will understand.
+
+Without an address book, you would be stuck using a @base32-address every time you visit an @I2P website/service - and that's not fun!
+
+### In-depth information
+
+Since [DNS](https://en.wikipedia.org/wiki/DNS) does not exist on the @I2P network, @Kovri also does **not** use DNS or any sort of @canonically-unique-host resolution. Instead, Kovri pairs a @locally-unique-host to a @base64-address @destination in a @subscription. Once your address book is filled with a @subscription, you can resolve your favorite `.i2p` domain site into a usable @I2P destination.
+
+### Creating an Address Book
+
+By default, your installation will come with a default public @subscription called `hosts.txt` in your @data-directory. When @Kovri starts, it loads this subscription and fetches any other subscriptions you've specified. Once loaded, your address book will be appropriately filled. For details on how to manage subscriptions, see @subscription.
+
+### Updating the Address Book
+
+Currently, there are several ways to update your address book:
+
+1. Use a @jump-service to insert I2P addresses into your address book
+2. Use a @jump-service to copy/paste an address into your private @subscription
+3. Manually add or subtract from a private @subscription
+
+**Note: Kovri is in heavy development. In the future there *will* be easier ways to update the address book**
+
+### Address Book / Naming specification
+
+For specification details and more, visit the [Address Book and Naming Specification](https://geti2p.net/en/docs/naming)
diff --git a/_i18n/en/resources/moneropedia/address.md b/_i18n/en/resources/moneropedia/address.md
new file mode 100644
index 0000000000000000000000000000000000000000..ed33f15a69c0969f7f85287f85caadf6e8e6c14d
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/address.md
@@ -0,0 +1,22 @@
+---
+layout: moneropedia
+entry: "Address"
+terms: ["address", "addresses"]
+summary: "either an alias, such as donate.getmonero.org, or a set of 95 characters starting with a 4"
+---
+
+### The Basics
+
+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 <span class="long-term">44AFFq5kSiGBoZ4NMDwYtN18obc8AemS33DBLWs3H7otXft3XjrpDtQGv7SqSsaBYBb98uNbr2VBBEt7f2wfn3RVGQBEP3A</span>.
+
+Because those addresses are long and complex you will often encounter an @OpenAlias address instead. For example, Monero donations can be sent to <span class="long-term">donate@getmonero.org</span> or <span class="long-term">donate.getmonero.org</span>.
+
+If you would like to get an @OpenAlias address of your own then there is some information on the [OpenAlias page](/knowledge-base/openalias).
+
+### Integrated address
+
+An integrated address is an address combined with an encrypted 64-bit @payment-ID. A raw integrated address is 106 characters long.
+
+### In-depth Information
+
+The address is actually the concatenation, in Base58 format, of the *public* @spend-key and the *public* @view-key, prefixed with the network byte (the number 18 for Monero) and suffixed with the first four bytes of the Keccac-256 hash of the whole string (used as a checksum).
diff --git a/_i18n/en/resources/moneropedia/airgap.md b/_i18n/en/resources/moneropedia/airgap.md
new file mode 100644
index 0000000000000000000000000000000000000000..f3107cf267768067e02d7bfab15ddadaadcceaf9
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/airgap.md
@@ -0,0 +1,12 @@
+---
+layout: moneropedia
+entry: "Airgap"
+terms: ["airgap"]
+summary: "An airgap is a security measure to physically separate a computer or device from all other networks, such as the Internet."
+---
+
+### The Basics
+
+"An air gap, air wall or air gapping is a network security measure employed on one or more computers to ensure that a secure computer network is physically isolated from unsecured networks, such as the public Internet or an unsecured local area network.[2] The name arises from the technique of creating a network that is physically separated (with a conceptual air gap) from all other networks. The air gap may not be completely literal, as networks employing the use of dedicated cryptographic devices that can tunnel packets over untrusted networks while avoiding packet rate or size variation can be considered air gapped, as there is no ability for computers on opposite sides of the gap to communicate."
+
+Taken from https://en.wikipedia.org/wiki/Air_gap_(networking)
diff --git a/_i18n/en/resources/moneropedia/base32-address.md b/_i18n/en/resources/moneropedia/base32-address.md
new file mode 100644
index 0000000000000000000000000000000000000000..ef38e41458c635cad73a7328d69f849b73d41c28
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/base32-address.md
@@ -0,0 +1,27 @@
+---
+layout: moneropedia
+entry: "Base32 address"
+tags: ["kovri"]
+terms: ["Base32-address", "Base32-addresses"]
+summary: "Base32 encoded hash of a Base64 address"
+---
+
+### The Basics
+
+A Base32 address is a shortened, encoded version of an @I2P address. The Base32 address is the first part in a `.b32.i2p` hostname.
+
+Example:
+
+`i35yftyyb22xhcvghmev46t5knefur5v66qzekkajatwfwhyklvq.b32.i2p`
+
+where
+
+`i35yftyyb22xhcvghmev46t5knefur5v66qzekkajatwfwhyklvq` is the Base32 address.
+
+### In-depth Information
+
+Ultimately, a Base32 address is a 52 character [Base32 encoded representation](https://en.wikipedia.org/wiki/Base32) of the full SHA-256 hash of an @I2P @base64-address.
+
+### Notes
+
+**Note: `.b32` is not a sub-domain of `.i2p`**
diff --git a/_i18n/en/resources/moneropedia/base64-address.md b/_i18n/en/resources/moneropedia/base64-address.md
new file mode 100644
index 0000000000000000000000000000000000000000..edd345932dd6ae7c5358a4d642b097c00e129d7e
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/base64-address.md
@@ -0,0 +1,22 @@
+---
+layout: moneropedia
+entry: "Base64 address"
+tags: ["kovri"]
+terms: ["Base64-address", "Base64-addresses"]
+summary: "Base64 encoded I2P destination"
+---
+
+### The Basics
+
+A @base64-address is a 516-character [Base64 encoded](https://en.wikipedia.org/wiki/Base64) @I2P @destination. @base64-addresses are primarily used for @address-book, @jump-service, and also internally.
+
+Example:
+
+```
+AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLEov~usVliTSXCSHuRBOCIwIOuDNU0AbVa4BpIx~2sU4TxKhoaA3zQ6VzINoduTdR2IJhPvI5xzezp7dR21CEQGGTbenDslXeQ4iLHFA2~bzp1f7etSl9T2W9RID-KH78sRQmzWnv7dbhNodMbpO6xsf1vENf6bMRzqD5vgHEHZu2aSoNuPyYxDU1eM6--61b2xp9mt1k3ud-5WvPVg89RaU9ugU5cxaHgR927lHMCAEU2Ax~zUb3DbrvgQBOTHnJEx2Fp7pOK~PnP6ylkYKQMfLROosLDXinxOoSKP0UYCh2WgIUPwE7WzJH3PiJVF0~WZ1dZ9mg00c~gzLgmkOxe1NpFRNg6XzoARivNVB5NuWqNxr5WKWMLBGQ9YHvHO1OHhUJTowb9X90BhtHnLK2AHwO6fV-iHWxRJyDabhSMj1kuYpVUBQAEAAcAAA==
+```
+
+
+### In-depth Information
+
+See @destination for details behind @base64-address
diff --git a/_i18n/en/resources/moneropedia/block.md b/_i18n/en/resources/moneropedia/block.md
new file mode 100644
index 0000000000000000000000000000000000000000..cadae194672eb5adacdb1c849d64e0c72ba0bb43
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/block.md
@@ -0,0 +1,16 @@
+---
+layout: moneropedia
+entry: "Block"
+terms: ["block", "blocks"]
+summary: "a container of transactions, a sequence of which forms a blockchain"
+---
+
+### The Basics
+
+A block is a container of @transactions, with a new block being added to the @blockchain once every 2 minutes (see constant `DIFFICULTY_TARGET_V2` defined as 120 seconds), on average.
+
+Blocks also contain a special type of transaction, the @coinbase-transaction, which add newly created Monero to the network.
+
+Blocks are created through the process of @mining, and the @node that successfully mines the block then broadcasts it to each of the @nodes connected to it, who subsequently re-broadcast the block until the entire Monero network has received it.
+
+Fake or bad blocks generally cannot be created, as @nodes that receive blocks always verify the @transactions they contain against a set of consensus rules that all nodes adhere to, including validating the cryptographic @signatures on each transaction.
diff --git a/_i18n/en/resources/moneropedia/blockchain.md b/_i18n/en/resources/moneropedia/blockchain.md
new file mode 100644
index 0000000000000000000000000000000000000000..d20e8cf7753231002d833ad6c1e8f047cce365e3
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/blockchain.md
@@ -0,0 +1,13 @@
+---
+layout: moneropedia
+entry: "Blockchain"
+terms: ["blockchain", "blockchains"]
+summary: "a distributed ledger of all transactions both past and present, without revealing who the funds came from or went to"
+
+---
+
+### 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.
+
+### 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.
diff --git a/_i18n/en/resources/moneropedia/canonically-unique-host.md b/_i18n/en/resources/moneropedia/canonically-unique-host.md
new file mode 100644
index 0000000000000000000000000000000000000000..c11389923934a4dd0ef8ff86017a0c41d9d9835d
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/canonically-unique-host.md
@@ -0,0 +1,23 @@
+---
+layout: moneropedia
+entry: "Canonically-unique host"
+tags: ["kovri"]
+terms: ["Canonically-unique-host"]
+summary: "A host that is canonically resolved to an address or set of addresses"
+---
+
+### The Basics
+
+A Canonically-unique host is a [FQDN](https://en.wikipedia.org/wiki/FQDN) that will canonically resolve to a designated address or set of addresses. Not to be confused with a @locally-unique-host.
+
+### In-depth information
+
+A Canonically-unique host is defined by remote authoritative sources; usually through [DNS](https://en.wikipedia.org/wiki/DNS). When resolving a peer's hostname, you will most likely use an external source for resolution unless you have the following implemented:
+
+- a database file similar to a [hosts file](https://en.wikipedia.org/wiki/etc/hosts)
+- an internal-network resolver (which eventually pulls from external sources)
+
+### Notes
+
+- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
+- @I2P's and @Kovri's self-assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
diff --git a/_i18n/en/resources/moneropedia/change.md b/_i18n/en/resources/moneropedia/change.md
new file mode 100644
index 0000000000000000000000000000000000000000..08163292b111e745bf5cad98c7812f7e6f3ce992
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/change.md
@@ -0,0 +1,16 @@
+---
+layout: moneropedia
+entry: "Change"
+terms: ["change"]
+summary: "Monero sent as part of a transaction, that returns to your account instead of going to another recipient"
+---
+
+### The Basics
+
+{{ page.summary | capitalize }}.
+
+### 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.
+
+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/_i18n/en/resources/moneropedia/clearnet.md b/_i18n/en/resources/moneropedia/clearnet.md
new file mode 100644
index 0000000000000000000000000000000000000000..9200e69a48b0447cad2ba21cbbc085e5cc7af0ab
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/clearnet.md
@@ -0,0 +1,33 @@
+---
+layout: moneropedia
+entry: "Clearnet"
+tags: ["kovri"]
+terms: ["Clearnet"]
+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:
+
+- your [ISP](https://en.wikipedia.org/wiki/ISP)
+- the website/service/person you're communicating with
+- possibly a [Five Eyes](https://en.wikipedia.org/wiki/5_Eyes) capable entity
+
+and even if you use [HTTPS](https://en.wikipedia.org/wiki/HTTPS) or similar (which *encrypts* your transmission), your route is not hidden nor is it anonymous, thus; it is in the *clear*.
+
+### In-depth information
+
+Since a traditional [VPN](https://en.wikipedia.org/wiki/VPN) cannot save you from clearnet (as you are still using *clearnet* (though you are more proxied than without a VPN)), you should use an *anonymous overlay network* to avoid using clearnet directly:
+
+- @Kovri
+- @Java-I2P
+- [Tor](https://torproject.org/)
+
+These technologies protect you from clearnet by building an anonymous network **over** clearnet to keep your transmissions both encrypted **and** anonymous.
+
+Here is an accurate, [interactive diagram](https://www.eff.org/pages/tor-and-https) provided by the [EFF](https://www.eff.org/) which describes *clearnet* as it relates to **Tor**. The concept also (somewhat) applies to @Kovri and @I2P in terms of anonymity with the exception that:
+
+- @Kovri does not use exit nodes when connecting to an @eepsite
+- Your traffic never need to leave the @I2P network
+- You do not need HTTPS to use @Kovri (with the exception of @reseed)
diff --git a/_i18n/en/resources/moneropedia/coinbase.md b/_i18n/en/resources/moneropedia/coinbase.md
new file mode 100644
index 0000000000000000000000000000000000000000..4c564e4ba0e63ac25108c49e8c9332a34c0dac28
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/coinbase.md
@@ -0,0 +1,10 @@
+---
+layout: moneropedia
+entry: "Coinbase Transaction"
+terms: ["coinbase-transaction"]
+summary: "a special type of transaction included in each block, which contains a small amount of Monero sent to the miner as a reward for their mining work"
+---
+
+### The Basics
+
+{{ page.summary | capitalize }}.
\ No newline at end of file
diff --git a/_i18n/en/resources/moneropedia/consensus.md b/_i18n/en/resources/moneropedia/consensus.md
new file mode 100644
index 0000000000000000000000000000000000000000..192e9d9eb4e932068d5bbbab5fb8ceb7f9164f67
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/consensus.md
@@ -0,0 +1,10 @@
+---
+layout: moneropedia
+entry: "Consensus"
+terms: ["consensus", "consensus-network"]
+summary: "consensus describes a property of distributed networks like Monero where most of the participants follow the rules, and thus reject bad participants"
+---
+
+### The Basics
+
+{{ page.summary | capitalize }}.
\ No newline at end of file
diff --git a/_i18n/en/resources/moneropedia/cryptocurrency.md b/_i18n/en/resources/moneropedia/cryptocurrency.md
new file mode 100644
index 0000000000000000000000000000000000000000..45d736c217de532757e9cff5f7a33ddd20367ef5
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/cryptocurrency.md
@@ -0,0 +1,22 @@
+---
+layout: moneropedia
+entry: "Cryptocurrency"
+terms: ["cryptocurrency", "cryptocurrencies", "altcoin", "altcoins"]
+summary: "a digital currency in which encryption techniques are used to regulate the generation of units of currency and verify the transfer of funds, usually operating independently of a central bank"
+---
+
+### The Basics
+
+{{ page.summary | capitalize }}.
+
+### 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).
+
+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).
+
+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.
+
+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/_i18n/en/resources/moneropedia/data-directory.md b/_i18n/en/resources/moneropedia/data-directory.md
new file mode 100644
index 0000000000000000000000000000000000000000..e66f6959ee451482316151ca5a9417aabbb20d76
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/data-directory.md
@@ -0,0 +1,22 @@
+---
+layout: moneropedia
+entry: "Data Directory"
+tags: ["kovri"]
+terms: ["Data-Directory"]
+summary: "Where essential kovri data for runtime is stored"
+---
+
+### The Basics
+
+Depending on your OS, @Kovri currently stores all run-time data in the following directory:
+
+- Linux/FreeBSD:
+ - `$HOME/.kovri`
+
+- OSX:
+ - `$HOME/Library/Application\ Support/Kovri`
+
+- Windows:
+ - `"$APPDATA"\\Kovri`
+
+This includes all configuration files, @address-book, certificates, and resources.
diff --git a/_i18n/en/resources/moneropedia/denominations.md b/_i18n/en/resources/moneropedia/denominations.md
new file mode 100644
index 0000000000000000000000000000000000000000..24bda2415ab2f79ad93f1ab59685842ca589ad44
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/denominations.md
@@ -0,0 +1,36 @@
+---
+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.)"
+---
+
+### 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).
+
+### Denominations of Monero
+
+|------------+----------+-------------------|
+| Name | Base 10 | Amount |
+|-----------:|:--------:| -----------------:|
+| piconero | 10^-12 | 0.000000000001 |
+| nanonero | 10^-9 | 0.000000001 |
+| micronero | 10^-6 | 0.000001 |
+| millinero | 10^-3 | 0.001 |
+| centinero | 10^-2 | 0.01 |
+| decinero | 10^-1 | 0.1 |
+|============+==========+===================|
+| **monero** | **10^0** | **1** |
+|============+==========+===================|
+| decanero | 10^1 | 10 |
+| hectonero | 10^2 | 100 |
+| kilonero | 10^3 | 1,000 |
+| meganero | 10^6 | 1,000,000 |
+|------------+----------+-------------------|
+
+### 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 }}.
diff --git a/_i18n/en/resources/moneropedia/destination.md b/_i18n/en/resources/moneropedia/destination.md
new file mode 100644
index 0000000000000000000000000000000000000000..a999bebfba3fecd61acf623c719ce40a14b780a7
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/destination.md
@@ -0,0 +1,19 @@
+---
+layout: moneropedia
+entry: "Destination"
+tags: ["kovri"]
+terms: ["Destination", "Destinations"]
+summary: "A in-net address that serves as a final endpoint (either local or remote)"
+---
+
+### The Basics
+
+A @destination is the @I2P @in-net address of the final endpoint you are trying to connect to (example: an @I2P website, service, or Monero node). This can also include a *local destination* of which *other* peers need to connect to in order to make contact for communication (similar to how, in @clearnet, your IP address is given to a website when you connect so it knows *where* to send the information back to).
+
+### 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:
+
+`256-byte public key + 128-byte signing key + a null certificate = 516 bytes in Base64 representation`
+
+Note: certificates are not used now but, if they were, the keys would be longer.
diff --git a/_i18n/en/resources/moneropedia/eepsite.md b/_i18n/en/resources/moneropedia/eepsite.md
new file mode 100644
index 0000000000000000000000000000000000000000..5fbb9545d5e7695ea063407cc5f5e880e07a7df4
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/eepsite.md
@@ -0,0 +1,30 @@
+---
+layout: moneropedia
+entry: "Eepsite"
+tags: ["kovri"]
+terms: ["Eepsite", "Hidden-Service", "Garlic-Site", "Garlic-Service"]
+summary: "A website or service hosted within the I2P network"
+---
+
+### The Basics
+
+Is it [**EEP!** *(in response to the site's content)*](https://en.wikipedia.org/wiki/Onomatopoeia), or **end-to-end protocol**, or something else entirely different?
+
+While the original definition of eepsite has been lost with time, its use-case remains: an eepsite is a website or service that is hosted within (and only accessible by) the @I2P network.
+
+### In-depth Information
+
+Alternate names include:
+
+1. *Hidden Service*
+ - because the site/service is *hidden* within the @I2P network and can only be visited within the network
+2. *Garlic Site*
+ - because the website utilizes @I2P's @garlic-routing technology as a means of communicating with a client
+ - because the service is hosted as a website and not any other type of service
+3. *Garlic Service*
+ - because the service utilizes @I2P's @garlic-routing technology as a means of communicating with a client
+ - because the service is specific to services like IRC, email, or a Monero peer (but may also include websites)
+
+### Notes
+
+To learn how to setup an Eepsite (Hidden Service, Garlic Site, Garlic Service) visit the @Kovri [user-guide](https://github.com/monero-project/kovri/blob/master/doc/USER_GUIDE.md).
diff --git a/_i18n/en/resources/moneropedia/encryption.md b/_i18n/en/resources/moneropedia/encryption.md
new file mode 100644
index 0000000000000000000000000000000000000000..d9356c4b15ea16aca56fcf4ae8c00537e87a3dd4
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/encryption.md
@@ -0,0 +1,35 @@
+---
+layout: moneropedia
+entry: "Encryption"
+tags: ["kovri"]
+terms: ["encryption", "encrypted", "encrypting", "decryption", "decrypted", "decrypting"]
+summary: "The process of encoding messages or information in a way that only authorized parties can decode and read"
+---
+
+### The Basics
+
+From [Encryption](https://en.wikipedia.org/wiki/Encryption):
+
+>
+In cryptography, encryption is the process of encoding messages or information in such a way that only authorized parties can decode and read what is sent. Encryption does not of itself prevent interception, but denies the message content to the interceptor.
+
+### In-depth information
+
+From [Encryption](https://en.wikipedia.org/wiki/Encryption):
+
+>
+ In an encryption scheme, the intended communication information or message (referred to as *plaintext*), is encrypted using an encryption algorithm, generating ciphertext that can only be read if decrypted. For technical reasons, an encryption scheme usually uses a pseudo-random encryption key generated by an algorithm. It is in principle possible to decrypt the message without possessing the key, but, for a well-designed encryption scheme, large computational resources and skill are required. An authorized recipient can easily decrypt the message with the key provided by the originator to recipients, but not to unauthorized interceptors.
+
+>
+The purpose of encryption is to ensure that only somebody who is authorized to access data (e.g. a text message or a file), will be able to read it, using the decryption key. Somebody who is not authorized can be excluded, because he or she does not have the required key, without which it is impossible to read the encrypted information.
+
+### Kovri
+
+@Kovri implements various types of encryption in *at least* 4 essential capacities:
+
+- @Reseed for bootstrapping
+- @Garlic-routing: three layers of encryption (@garlic-encryption) are used to verify the secure delivery of @messages to the recipient/peer/@destination
+- @Tunnel encryption: garlic messages are passed through a @tunnel and encrypted by the @tunnel gateway to the @tunnel endpoint
+- @Transport layer encryption prevents the ability to decrypt @messages at the [media layer](https://en.wikipedia.org/wiki/OSI_model)
+
+For details on the types of encryption and cryptographic @signatures used in @Kovri and @I2P, visit @Java-I2P's [Cryptography](https://geti2p.net/spec/cryptography)
diff --git a/_i18n/en/resources/moneropedia/floodfill.md b/_i18n/en/resources/moneropedia/floodfill.md
new file mode 100644
index 0000000000000000000000000000000000000000..e3fbf54f6cbea9a5496f73a15a71222454971430
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/floodfill.md
@@ -0,0 +1,15 @@
+---
+layout: moneropedia
+entry: "Floodfill"
+tags: ["kovri"]
+terms: ["Floodfill"]
+summary: "An I2P router which maintains a distributed network-database"
+---
+
+### The Basics
+
+By actively managing a distributed network-database, a router with *floodfill* capability has the ability to help maintain network stability and resiliancy while also being decentralized and trust-less.
+
+### In-depth information
+
+Though floodfill itself is a simple storage system, the technical underpinnings of floodfill as it relates to @network-database and other protocols within @I2P are much more complex. Visit the [Network Database](https://geti2p.net/en/docs/how/network-database) page for details.
diff --git a/_i18n/en/resources/moneropedia/fungibility.md b/_i18n/en/resources/moneropedia/fungibility.md
new file mode 100644
index 0000000000000000000000000000000000000000..47ca7d01e0f76ec37a736b3638a49e341e59b6f0
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/fungibility.md
@@ -0,0 +1,16 @@
+---
+layout: moneropedia
+entry: "Fungibility"
+terms: ["fungibility"]
+summary: "property of a currency whereby two units can be substituted in place of one another"
+---
+
+### 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.
+
+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.
+
+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.
+
+{{ page.summary | capitalize }}.
diff --git a/_i18n/en/resources/moneropedia/garlic-encryption.md b/_i18n/en/resources/moneropedia/garlic-encryption.md
new file mode 100644
index 0000000000000000000000000000000000000000..3364f521c3ba5f6aa275ec1ec252756c29d40e84
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/garlic-encryption.md
@@ -0,0 +1,25 @@
+---
+layout: moneropedia
+entry: "Garlic-Encryption"
+tags: ["kovri"]
+terms: ["Garlic-Encryption", "Layered-Encryption"]
+summary: "Layered encryption as implemented in Kovri / I2P"
+---
+
+### The Basics
+
+@garlic-encryption is @I2P's implementation of @message based @layered-encryption (similar to flow-based [Onion-Routing](https://en.wikipedia.org/wiki/Onion_routing)).
+
+By @encrypting @messages in layers, this allows a @message to be routed through a sequence of proxies without allowing the proxies (or any intermediaries) to read the contents of the @message. @Layered-Encryption is a fundamental feature in @Kovri, @I2P, and [Tor](https://torproject.org) and is the cornerstone for securing anonymity within these overlay-networks.
+
+### In-depth information
+
+For @garlic-encryption, the primary difference between @Kovri/@I2P and Tor is:
+
+- @Kovri/@I2P bundles multiple @messages together to form garlic "cloves"
+ - any number of messages can be contained in a "clove" instead of *only* a single message
+- @Kovri/@I2P uses [ElGamal](https://en.wikipedia.org/wiki/ElGamal)/[AES](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard) @encryption for @messages and @transports
+
+### Notes
+
+For details, see @garlic-routing.
diff --git a/_i18n/en/resources/moneropedia/garlic-routing.md b/_i18n/en/resources/moneropedia/garlic-routing.md
new file mode 100644
index 0000000000000000000000000000000000000000..55cd2122f0393c9a1b0d3e8559e7a709be21e5d6
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/garlic-routing.md
@@ -0,0 +1,45 @@
+---
+layout: moneropedia
+entry: "Garlic Routing"
+tags: ["kovri"]
+terms: ["Garlic-Routing"]
+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 @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).
+
+### History
+
+In written form, the term *@garlic-routing* can be seen as early as June of 2000 in Roger Dingledine's [Free Haven Master's thesis](http://www.freehaven.net/papers.html) (Section 8.1.1) as derived from the term Onion Routing.
+
+As recent as October of 2016, [#tor-dev](https://oftc.net/WebChat/) has offered insight into the creation of the term *@garlic-routing*:
+
+[Nick Mathewson](https://en.wikipedia.org/wiki/The_Tor_Project,_Inc):
+>[I think that there was some attempt to come up with a plant whose structure resembled the 'leaky-pipe' topology of tor, but I don't believe we ever settled on one.]
+
+[Roger Dingledine](https://en.wikipedia.org/wiki/Roger_Dingledine):
+>during the free haven brainstorming, there was a moment where we described a routing mechanism, and somebody said "garlic routing!", and everybody laughed.
+so we for sure thought we had invented the name, at the time.
+
+*Note: permission to use the aforementioned quotes was granted by Nick Mathewson and Roger Dingledine*
+
+### In-depth Information
+
+In technical terms, for @Kovri and @I2P, *@garlic-routing* translates to any/all of the following:
+
+- @Layered-Encryption (similar to the @layered-encryption in Onion Routing)
+- Bundling multiple @messages together (garlic cloves)
+- ElGamal/AES @encryption
+
+*Note: though [Tor](https://torproject.org/) uses @layered-encryption, Tor does not use ElGamal and is not message-based.*
+
+**Read more in @garlic-encryption.**
+
+### Notes
+
+- In terms of Onion/Garlic Routing, another way to envision layered @encryption is by replacing the onion/garlic with a [Matryoshka doll](https://en.wikipedia.org/wiki/Matryoshka_doll) - with each outer/inner doll having a lock and public key to the next/previous doll
+- For more technical details on Garlic Routing, read the @Java-I2P entry on [Garlic Routing](https://geti2p.net/en/docs/how/garlic-routing)
diff --git a/_i18n/en/resources/moneropedia/i2np.md b/_i18n/en/resources/moneropedia/i2np.md
new file mode 100644
index 0000000000000000000000000000000000000000..d05c17aab63a037c98932257c714f93285f1151d
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/i2np.md
@@ -0,0 +1,28 @@
+---
+layout: moneropedia
+entry: "I2NP"
+tags: ["kovri"]
+terms: ["I2NP"]
+summary: "The I2P Network Protocol: the mechanism in which I2NP messages are sent over the I2P network"
+---
+
+### The Basics
+
+From @Java-I2P:
+
+>
+@I2NP manages the routing and mixing of messages between routers, as well as the selection of what transports to use when communicating with a peer for which there are multiple common transports supported
+
+### In-depth information
+
+From @Java-I2P:
+
+>
+@I2NP (@I2P Network Protocol) @messages can be used for one-hop, router-to-router, point-to-point @messages. By @encrypting and wrapping @messages in other @messages, they can be sent in a secure way through multiple hops to the ultimate @destination. @I2NP does not specify nor require any particular @transport layer but does require at least one @transport in use.
+
+>
+Whenever a @destination wants to send a message to to another @destination, it provides its local router with both the @destination structure and the raw bytes of the message to be sent. The router then determines where to send it, delivers it through outbound @tunnels, instructing the end point to pass it along to the appropriate inbound @tunnel, where it is passed along again to that @tunnel's end point and made available to the target for reception.
+
+### Notes
+
+Read more about the @I2NP [protocol](https://geti2p.net/en/docs/protocol/i2np) and [specification](https://geti2p.net/spec/i2np).
diff --git a/_i18n/en/resources/moneropedia/i2p.md b/_i18n/en/resources/moneropedia/i2p.md
new file mode 100644
index 0000000000000000000000000000000000000000..2778db301a50271acafe3eead81b704ae4ff333b
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/i2p.md
@@ -0,0 +1,31 @@
+---
+layout: moneropedia
+entry: "I2P"
+tags: ["kovri"]
+terms: ["I2P"]
+summary: "The Invisible Internet Project: an anonymizing overlay network"
+---
+
+### Monero
+
+For Monero's implementation of @I2P, see @Kovri. For a comparison of @I2P to [Tor](https://torproject.org/), read the [Comparison](https://geti2p.net/en/comparison/tor) page.
+
+### The Basics
+
+From @Java-I2P:
+
+>The I2P network provides strong privacy protections for communication over the Internet. Many activities that would risk your privacy on the public Internet can be conducted anonymously inside I2P.
+
+### In-depth information
+
+From @Java-I2P:
+
+>I2P is an anonymous overlay network - a network within a network. It is intended to protect communication from dragnet surveillance and monitoring by third parties such as ISPs.
+
+>I2P is used by many people who care about their privacy: activists, oppressed people, journalists and whistleblowers, as well as the average person.
+
+>No network can be "perfectly anonymous". The continued goal of I2P is to make attacks more and more difficult to mount. Its anonymity will get stronger as the size of the network increases and with ongoing academic review.
+
+### Notes
+
+@I2P documentation and specifications are available [here](https://geti2p.net/docs/).
diff --git a/_i18n/en/resources/moneropedia/i2pcontrol.md b/_i18n/en/resources/moneropedia/i2pcontrol.md
new file mode 100644
index 0000000000000000000000000000000000000000..481d9eae6f086f719e8e57ab5651d2c039875069
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/i2pcontrol.md
@@ -0,0 +1,17 @@
+---
+layout: moneropedia
+entry: "I2PControl"
+tags: ["kovri"]
+terms: ["I2PControl"]
+summary: "An API inteface for Kovri and Java-I2P that allows simple remote control"
+---
+
+### 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.
+
+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.
+
+### In-depth information
+
+Details and specification available on the [I2PControl](https://geti2p.net/en/docs/api/i2pcontrol) page.
diff --git a/_i18n/en/resources/moneropedia/in-net.md b/_i18n/en/resources/moneropedia/in-net.md
new file mode 100644
index 0000000000000000000000000000000000000000..92404f08b6ed21a2181c4ac5c843df89a77544c2
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/in-net.md
@@ -0,0 +1,15 @@
+---
+layout: moneropedia
+entry: "In-net"
+tags: ["kovri"]
+terms: ["In-net"]
+summary: "Within the I2P network"
+---
+
+### The Basics
+
+**In-net** is a [colloquial](https://en.wikipedia.org/wiki/Colloquial) term of which describes activities, protocols, or functionality that exist *only* within the @I2P network.
+
+### In-depth information
+
+Example: *in-net download* would be defined as downloading *only* within @I2P.
diff --git a/_i18n/en/resources/moneropedia/index.md b/_i18n/en/resources/moneropedia/index.md
new file mode 100644
index 0000000000000000000000000000000000000000..4489586c05835703abe0ed61bd85827a223a8986
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/index.md
@@ -0,0 +1,21 @@
+---
+layout: full
+title: "Moneropedia"
+title-pre-kick: "Moneropedia - The "
+title-kick: "Monero Wiki"
+title-post-kick: ""
+kick-class: "softyellow-kicks"
+icon: "icon_wiki"
+attribution: "<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->"
+---
+
+
+<div class="row">
+
+@moneropedia
+
+</div>
+
+<p><a href="https://github.com/monero-project/monero-site/new/master/knowledge-base/moneropedia" class="btn-link btn-auto btn-primary">Add New Entry</a></p>
+
+If there is an entry you'd like to modify or be added, please [open an issue on this website's Github repository](https://github.com/monero-project/monero-site/issues) or submit changes via pull request.
\ No newline at end of file
diff --git a/_i18n/en/resources/moneropedia/java-i2p.md b/_i18n/en/resources/moneropedia/java-i2p.md
new file mode 100644
index 0000000000000000000000000000000000000000..e040579b58e2dd421a585c3c2ef0bc2098770479
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/java-i2p.md
@@ -0,0 +1,15 @@
+---
+layout: moneropedia
+entry: "Java I2P"
+tags: ["kovri"]
+terms: ["Java-I2P"]
+summary: "The original implementation of I2P - written in Java"
+---
+
+### The Basics
+
+The term "Java I2P" is often used to describe the original @I2P implementation currently most known and used today. There are various other @I2P implementations, including @Kovri; all of which look up to the original Java implementation.
+
+### Notes
+
+To download/learn more about the Java implementation, visit their [website](https://geti2p.net/).
diff --git a/_i18n/en/resources/moneropedia/jump-service.md b/_i18n/en/resources/moneropedia/jump-service.md
new file mode 100644
index 0000000000000000000000000000000000000000..228ebb989d41589751aae44bccd3e1dc6fb3fa0d
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/jump-service.md
@@ -0,0 +1,34 @@
+---
+layout: moneropedia
+entry: "Jump Service"
+tags: ["kovri"]
+terms: ["Jump-Service"]
+summary: "An I2P website service that adds addresses to your address book"
+---
+
+### The Basics
+
+In your @I2P configured web browser, you can use a Jump Service to *jump* to an @I2P address that you don't have in your @address-book. Once you've *jumped* to the address, the address will be saved into your @address-book.
+
+### In-depth Information
+
+In an @I2P configured browser, visit: http://stats.i2p/i2p/lookup.html (courtesy of @Java-I2P's lead developer *zzz*)
+
+Then, you'll have two options:
+
+1. *Hostname lookup* the address you wish to visit and then manually copy/paste the result
+2. *Jump* to the @I2P website by entering the @I2P hostname (**recommended**)
+
+### Using hostname lookup
+
+For example, entering `pinkpaste.i2p` into the *Hostname lookup* box (and then submitting) will return:
+
+```
+pinkpaste.i2p=m-HrPrIAsdxts0WM~P4mE8mt9P7g-QTaBvu7Gc6Nl0UX7Vwck-i~RvOPfK6W~kfdRvwhNTqevkBL2UF5l36We02Aiywu7kB2xOHRkze68h-Tg2ewvRVwokohguCD2G3wwAEz~7FVda2avYDCb9-N6TfuzxKLnmhPMvbNSjGL7ZsD2p-h207R3-2kvuMV9bfu-K~w9NI9XJhIyufvUnFYc2jnTVg8PbaR4UP57cNaOO2YIMPkbr6~yTcIu9B1sUfHK6-N~6virQDOxW4M-62rjnZkLpaCtkOsXslmCwZI--TkZ6hKi1kXZvNmJRE1rYfffYRFn38zhaqszeETX8HiIvahZhXF5fNumBziYdmLdw8hkuN1A~emU6Xz9g~a1Ixfsq1Qr~guYoOtaw-0rOFxNRS9yMehE-2LCb8c-cAg6z5OdlN4qJDl~ZHgru4d~EHp~BpAK3v7u2Gi-8l1ygVW-1CHVna~fwnbOPN3ANPwh6~~yUit0Cx1f54XiNRn6-nPBQAEAAcAAA==
+```
+
+Copy/paste this host=@base64-address pairing into your **private** @subscription.
+
+### Directly jumping
+
+For example, entering `pinkpaste.i2p` into the *Jump* box (and then submitting) will automatically redirect you to the website **and** insert the @locally-unique-host into @address-book.
diff --git a/_i18n/en/resources/moneropedia/kovri.md b/_i18n/en/resources/moneropedia/kovri.md
new file mode 100644
index 0000000000000000000000000000000000000000..6002cdd6b71750cae566c3d83759f8e04f02463b
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/kovri.md
@@ -0,0 +1,62 @@
+---
+layout: moneropedia
+entry: "Kovri"
+tags: ["kovri"]
+terms: ["Kovri"]
+summary: "Monero's C++ router implementation of the I2P network"
+---
+
+### The Basics
+
+[Kovri](https://github.com/monero-project/kovri/) is a C++ implementation of the @I2P network. @Kovri is currently in heavy, active development and not yet integrated with Monero. When Kovri is integrated into your Monero @node, your transactions will be more secure than ever before.
+
+### In-depth information
+
+Kovri will protect you and Monero from:
+
+- @Node partitioning attacks
+- Associations between a particular txid and your IP address
+- Mining and/or running a node in highly adversarial environments
+- Metadata leakage (e.g., @OpenAlias lookups)
+
+...and much more.
+
+Read [anonimal's FFS proposal](https://forum.getmonero.org/9/work-in-progress/86967/anonimal-s-kovri-full-time-development-funding-thread) for more details and for reasoning behind the project. Also read the FAQ and User Guide in the [Kovri repository](https://github.com/monero-project/kovri/).
+
+### @Kovri / @I2P Terminology
+
+#### Client + API
+
+- @Address-Book
+- @Base32-address
+- @Base64-address
+- @Canonically-unique-host
+- @Eepsite (@Hidden-Service, @Garlic-Site, @Garlic-Service)
+- @I2PControl
+- @Jump-Service
+- @Locally-unique-host
+- @Reseed
+- @Subscription
+
+#### Core + Router
+
+- @Clearnet
+- @Data-Directory
+- @Destination
+- @Encryption
+- @Floodfill
+- @Garlic-Encryption
+- @Garlic-Routing
+- @I2NP
+- @In-net
+- @Java-I2P
+- @Layered-Encryption
+- @Lease
+- @LeaseSet
+- @Message @Messages
+- @NTCP
+- @Network-Database
+- @Router-Info
+- @SSU
+- @Transports
+- @Tunnel
diff --git a/_i18n/en/resources/moneropedia/lease-set.md b/_i18n/en/resources/moneropedia/lease-set.md
new file mode 100644
index 0000000000000000000000000000000000000000..99165a037191f77094473ec8628120eeee9dfcd6
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/lease-set.md
@@ -0,0 +1,25 @@
+---
+layout: moneropedia
+entry: "Lease-Set"
+tags: ["kovri"]
+terms: ["LeaseSet", "LeaseSets"]
+summary: "Contains all currently authorized Leases for a particular I2P Destination"
+---
+
+### The Basics
+
+A Lease-Set contains a set of authorized @leases (and other related information) for a particular @destination.
+
+### In-depth information
+
+A Lease-Set contains:
+
+- all of the currently authorized @leases for a particular @destination
+- the public key to which garlic messages can be encrypted (see @garlic-routing)
+- the signing public key that can be used to revoke this particular version of the structure
+
+The Lease-Set is one of the two structures stored in the @network-database (the other being @router-info), and is keyed under the SHA256 of the contained @destination.
+
+### Notes
+
+For further details, read @Java-I2P's [LeaseSet](https://geti2p.net/en/docs/how/network-database#leaseSet)
diff --git a/_i18n/en/resources/moneropedia/lease.md b/_i18n/en/resources/moneropedia/lease.md
new file mode 100644
index 0000000000000000000000000000000000000000..d3cdc5451462953f08a56740ec3dec345e87849d
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/lease.md
@@ -0,0 +1,15 @@
+---
+layout: moneropedia
+entry: "Lease"
+tags: ["kovri"]
+terms: ["Lease", "Leases"]
+summary: "Authorizes an I2P tunnel to receive messages targeting a destination"
+---
+
+### The Basics
+
+A lease defines the authorization for a particular @I2P @tunnel to receive a @messages targeting a @destination.
+
+### In-depth information
+
+For further details, read @Java-I2P's [Lease](https://geti2p.net/spec/common-structures#lease)
diff --git a/_i18n/en/resources/moneropedia/locally-unique-host.md b/_i18n/en/resources/moneropedia/locally-unique-host.md
new file mode 100644
index 0000000000000000000000000000000000000000..3ce7f8605a072da5eb42b562f7284329d998312a
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/locally-unique-host.md
@@ -0,0 +1,22 @@
+---
+layout: moneropedia
+entry: "Locally-unique host"
+tags: ["kovri"]
+terms: ["Locally-unique-host"]
+summary: "A host defined by you and resolved only by you"
+---
+
+### The Basics
+
+A locally-unique host is a [FQDN](https://en.wikipedia.org/wiki/FQDN) defined by **you** and resolved only by you; similar to how a [hosts file](https://en.wikipedia.org/wiki/etc/hosts) is implemented. Not to be confused with @canonically-unique-host.
+
+### In-depth information
+
+You have the option to share your interpretation of how the host is resolved (e.g., `localhost` always resolves to `127.0.0.1`) but the resolution is not canonically enforced (e.g., someone else can map `localhost` to any arbitrary IP address).
+
+Hosts in a public subscription can be considered @canonically-unique-host's within the @I2P network but, ultimately, you are free to re-define them as you wish.
+
+### Notes
+
+- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
+- @I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
diff --git a/_i18n/en/resources/moneropedia/message.md b/_i18n/en/resources/moneropedia/message.md
new file mode 100644
index 0000000000000000000000000000000000000000..c9504d54ef3cf16bf9a2f9f94d589e9543e294a1
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/message.md
@@ -0,0 +1,33 @@
+---
+layout: moneropedia
+entry: "Message"
+tags: ["kovri"]
+terms: ["Message", "Messages"]
+summary: "The mechanisms in which information travels within I2P"
+---
+
+### The Basics
+
+*Messages* (which exist on top of the @transports layer), contain varying types of information that are needed for the network but, most importantly, everything you see, do, send, or receive, will come and go in the form of *messages*.
+
+There are 2 essential types of *messages* in @I2P:
+
+- @Tunnel messages
+- @I2NP messages
+
+Essentially: *@tunnel messages* **contain** @I2NP **message fragments** which are then [reassembled](https://geti2p.net/en/docs/tunnels/implementation) at certain points within a @tunnel's path.
+
+### In-depth information
+
+@I2NP messages have a close relationship with @tunnel @messages so it is easy to get the term *messages* confused when reading @Java-I2P specifications:
+
+>
+1. First, the tunnel gateway accumulates a number of I2NP messages and preprocesses them into tunnel messages for delivery.
+2. Next, that gateway encrypts that preprocessed data, then forwards it to the first hop.
+3. That peer, and subsequent tunnel participants, unwrap a layer of the encryption, verifying that it isn't a duplicate, then forward it on to the next peer.
+4. Eventually, the tunnel messages arrive at the endpoint where the I2NP messages originally bundled by the gateway are reassembled and forwarded on as requested.
+
+### Notes
+
+- @I2NP @messages need to be fragmented because they are variable in size (from 0 to almost 64 KB) and @tunnel @messages are fixed-size (approximately 1 KB).
+- For details and specifications, visit the [I2NP spec](https://geti2p.net/spec/i2np) and [Tunnel Message spec](https://geti2p.net/spec/tunnel-message)
diff --git a/resources/moneropedia/miners.md b/_i18n/en/resources/moneropedia/miners.md
similarity index 100%
rename from resources/moneropedia/miners.md
rename to _i18n/en/resources/moneropedia/miners.md
diff --git a/_i18n/en/resources/moneropedia/mnemonicseed.md b/_i18n/en/resources/moneropedia/mnemonicseed.md
new file mode 100644
index 0000000000000000000000000000000000000000..608f8d8bd28fc88dbdf27cc667856d95536f5506
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/mnemonicseed.md
@@ -0,0 +1,20 @@
+---
+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"
+---
+
+### The Basics
+
+{{ page.summary | capitalize }}. This 25-word phrase (13 words in the case of MyMonero) has all the information needed to view and spend funds from a Monero @account.
+
+### In-depth Information
+
+In the official wallet, the mnemonic seed comprises 25 words with the last word being used as a checksum. Those words correspond to a 256-bit integer, which is the account's *private* @spend-key. The *private* @view-key is derived by hashing the private spend key with Keccak-256, producing a second 256-bit integer. The corresponding *public* keys are then derived from the private keys.
+
+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!
+
+By creating a cold, or @paper-wallet you can safely store Moneroj.
diff --git a/_i18n/en/resources/moneropedia/network-database.md b/_i18n/en/resources/moneropedia/network-database.md
new file mode 100644
index 0000000000000000000000000000000000000000..a5bb078c35c3e207f6d2862d45d7b8661a7a837d
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/network-database.md
@@ -0,0 +1,25 @@
+---
+layout: moneropedia
+entry: "Network Database"
+tags: ["kovri"]
+terms: ["Network-Database"]
+summary: "A distributed database which contains needed router information so the network can stay intact"
+---
+
+### The Basics
+
+@network-database is a [distributed database](https://en.wikipedia.org/wiki/Distributed_database) which contains router information that peers must use so the network can stay intact.
+
+### In-depth information
+
+From @Java-I2P:
+
+>
+@I2P's @network-database is a specialized distributed database, containing just two types of data - router contact information (@Router-Infos) and @destination contact information (@LeaseSets). Each piece of data is signed by the appropriate party and verified by anyone who uses or stores it. In addition, the data has liveliness information within it, allowing irrelevant entries to be dropped, newer entries to replace older ones, and protection against certain classes of attack.
+
+>
+The @network-database is distributed with a simple technique called "@floodfill", where a subset of all routers, called "@floodfill routers", maintains the distributed database.
+
+### Notes
+
+Read [Network-Database](https://geti2p.net/en/docs/how/network-database) for details.
diff --git a/_i18n/en/resources/moneropedia/node.md b/_i18n/en/resources/moneropedia/node.md
new file mode 100644
index 0000000000000000000000000000000000000000..dde76903ff7400e62eb556a8b8faa7ec348825f0
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/node.md
@@ -0,0 +1,25 @@
+---
+layout: moneropedia
+entry: "Node"
+terms: ["node", "nodes", "full-node", "full-nodes"]
+summary: "a device on the Internet running the Monero software, with a full copy of the Monero blockchain, actively assisting the Monero network"
+---
+
+### The Basics
+
+{{ page.summary | capitalize }}.
+
+### 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).
+
+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.
+
+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.
+
+---
+
+##### Other Resources
+<sub>1. *Fluffypony gives a great explanation of why mandatory hardforks are good for Monero.* ([Monero Missives for the Week of 2016-06-20](https://getmonero.org/2016/06/20/monero-missive-for-the-week-of-2016-06-20.html))</sub>
diff --git a/_i18n/en/resources/moneropedia/ntcp.md b/_i18n/en/resources/moneropedia/ntcp.md
new file mode 100644
index 0000000000000000000000000000000000000000..69f3152c0be355a7ab283d2a9f15dd90aed73e66
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/ntcp.md
@@ -0,0 +1,34 @@
+---
+layout: moneropedia
+entry: "NTCP"
+tags: ["kovri"]
+terms: ["NTCP"]
+summary: "NIO-Based TCP (Non-blocking I/O based TCP): one of two Kovri transports"
+---
+
+### The Basics
+
+*NIO-Based TCP (Non-blocking I/O based TCP)* is one of two encrypted @transports for @Kovri.
+
+Similar to @SSU, @NTCP's *primary* purpose is to securely transmit @in-net @I2NP messages through @tunnels but, unlike @SSU, @NTCP functions solely over encrypted [TCP](https://en.wikipedia.org/wiki/Transmission_Control_Protocol).
+
+### In-depth information
+
+ - Passes along individual @I2NP messages (both Standard and Time Sync) after:
+ - TCP has been established
+ - Establishment Sequence has been completed
+ - Uses the following @encryption:
+ - 2048-bit [Diffie-Hellman](https://en.wikipedia.org/wiki/Diffie-hellman)
+ - [AES-256](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard)/[CBC](https://en.wikipedia.org/wiki/Block_cipher_modes_of_operation)
+ - Establishment Sequence has the following *states*:
+ - Pre-establishment
+ - Establishment
+ - Post-establishment or "Established"
+ - Uses the following from the @network-database:
+ - Transport name: NTCP
+ - Host: IP (IPv4 or IPv6) or host name (shortened IPv6 address (with "::") is allowed)
+ - Port: 1024 - 65535
+
+### Notes
+
+For further details, read @Java-I2P's [NTCP](https://geti2p.net/en/docs/transport/ntcp)
diff --git a/resources/openalias.md b/_i18n/en/resources/moneropedia/openalias.md
similarity index 59%
rename from resources/openalias.md
rename to _i18n/en/resources/moneropedia/openalias.md
index 8834105019289331ef0ad17099bebf7f770b00e3..2410130cb910285cdf3ab0f02371d44cdd63183a 100644
--- a/resources/openalias.md
+++ b/_i18n/en/resources/moneropedia/openalias.md
@@ -1,15 +1,13 @@
---
-layout: static_page
-title: "The OpenAlias Project"
-title-pre-kick: "The "
-title-kick: "OpenAlias "
-title-post-kick: "Project"
-kick-class: "oa-kicks"
-icon: "icon_openalias"
-attribution: "<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->"
+layout: moneropedia
+entry: "OpenAlias"
+terms: ["OpenAlias"]
+summary: "a standard that allows you to use an email or domain syntax to pay someone instead of an address, eg. donate@getmonero.org or donate.getmonero.org"
---
-### What is OpenAlias?
+### The Basics
+
+The Monero Core Team released a standard called OpenAlias which permits much more human-readable addresses and "squares" the Zooko's triangle. OpenAlias can be used for any cryptocurrency and is already implemented in Monero, Bitcoin (in latest Electrum versions) and HyperStake.
OpenAlias seeks to provide a way to simplify aliasing amidst a rapidly shifting technology climate. Users are trying to cross the bridge to private and cryptographically secure infrastructure and systems, but many of them have just barely started remembering the email addresses of their friends and family.
@@ -17,4 +15,6 @@ As part of the ongoing development of the Monero cryptocurrency project, we aske
At its most basic, OpenAlias is a TXT DNS record on a FQDN (fully qualified domain name). By combining this with DNS-related technologies we have created an aliasing standard that is extensible for developers, intuitive and familiar for users, and can interoperate with both centralized and decentralized domain systems.
-For more info, visit [www.openalias.org](https://www.openalias.org).
+{{ page.summary | capitalize }}.
+
+More information can be found on the [OpenAlias page](/knowledge-base/openalias) or on the [OpenAlias website](https://openalias.org)
diff --git a/_i18n/en/resources/moneropedia/paperwallet.md b/_i18n/en/resources/moneropedia/paperwallet.md
new file mode 100644
index 0000000000000000000000000000000000000000..95ff00baa4b55b875a45d3c487b1c3abb097753c
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/paperwallet.md
@@ -0,0 +1,7 @@
+---
+layout: moneropedia
+entry: "Paper Wallet"
+terms: ["paperwallet", "paperwallets", "paper-wallet", "paper-wallets"]
+summary: "A paper wallet stores the information necessary to send and receive Monero"
+---
+
diff --git a/_i18n/en/resources/moneropedia/paymentid.md b/_i18n/en/resources/moneropedia/paymentid.md
new file mode 100644
index 0000000000000000000000000000000000000000..fba888fa972960f62a18a47dd5c0404f6cc21d37
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/paymentid.md
@@ -0,0 +1,25 @@
+---
+layout: moneropedia
+entry: "Payment ID"
+terms: ["payment-ID", "payment-IDs"]
+summary: "an optional flag that is added to identify transactions to merchants, consisting of 64 hexadecimal characters"
+---
+
+### The Basics
+
+Payment ID is an **arbitrary** and **optional** transaction attachment that consists of 32 bytes (64 hexadecimal characters) or 8 bytes (in the case of integrated addresses).
+
+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
+
+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.
+
+### 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:
+
+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/_i18n/en/resources/moneropedia/pedersen-commitment.md b/_i18n/en/resources/moneropedia/pedersen-commitment.md
new file mode 100644
index 0000000000000000000000000000000000000000..a7ff98bab804cd9a190ae9dcea0c77fe349f4631
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/pedersen-commitment.md
@@ -0,0 +1,24 @@
+---
+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."
+---
+
+### The Basics
+
+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
+
+As long as the encrypted output amounts created, which include an output for the recipient and a change output back to the sender, and the unencrypted transaction fee is equal to the sum of the inputs that are being spent, it is a legitimate transaction and can be confirmed to not be creating Monero out of thin air.
+
+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.
+
+### 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/_i18n/en/resources/moneropedia/reseed.md b/_i18n/en/resources/moneropedia/reseed.md
new file mode 100644
index 0000000000000000000000000000000000000000..eb3b5d986adfd149d0e58eb9098682154136d6ef
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/reseed.md
@@ -0,0 +1,17 @@
+---
+layout: moneropedia
+entry: "Reseed"
+tags: ["kovri"]
+terms: ["Reseed"]
+summary: "The method of which Kovri uses to bootstrap into the I2P network"
+---
+
+### The Basics
+
+When you start @Kovri for the first time (or if it's been offline for a long time), @Kovri will need a list of peers to connect to so it can [bootstrap](https://en.wikipedia.org/wiki/Bootstrap) into the @I2P network. @Kovri gets these peers from a special file stored on a reseed server. On this file are all the various pieces of information @Kovri needs in order to connect with @I2P peers.
+
+### In-depth information
+
+@Kovri has a list of [hard-coded](https://en.wikipedia.org/wiki/Hard-coded) reseed servers available to fetch from. These servers securely serve an [SU3](https://geti2p.net/spec/updates#su3) file (signed with a cryptographic @signature) over @clearnet with [HTTPS](https://en.wikipedia.org/wiki/HTTPS). This SU3 file contains information that's used to verify both the integrity of the file and its content.
+
+Aside from the technical elements needed to verify and process the file, the file's main contents consist of a series of @router-info files which @Kovri and @I2P routers use to locate and communicate with other @I2P peers. These peers are then stored into a @network-database.
diff --git a/_i18n/en/resources/moneropedia/ring-size.md b/_i18n/en/resources/moneropedia/ring-size.md
new file mode 100644
index 0000000000000000000000000000000000000000..a1601651b0994211d852fae4354b65fb86a36cc4
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/ring-size.md
@@ -0,0 +1,11 @@
+---
+layout: moneropedia
+entry: "Ring Size"
+terms: ["ring-size"]
+summary: "total number of possible signers in a ring signature"
+---
+
+### The Basics
+Ring size refers to the total number of possible signers in a @ring-signature. If a ring size of 4 is selected for a given @transaction, this means that there are 3 foreign outputs in addition to your “real†output. A higher ring size number will typically provide more privacy than a lower number. However, reusing an odd, recognizable ring size number for transactions could possibly make transactions stand out.
+
+`Ring size = foreign outputs + 1 (your output)`
\ No newline at end of file
diff --git a/_i18n/en/resources/moneropedia/ringCT.md b/_i18n/en/resources/moneropedia/ringCT.md
new file mode 100644
index 0000000000000000000000000000000000000000..77b9bf3297b0ad2eb2aae23896f6ed936799f792
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/ringCT.md
@@ -0,0 +1,24 @@
+---
+layout: moneropedia
+entry: "Ring CT"
+terms: ["ringCT", "ring-CT"]
+summary: "a way to hide the amount sent in a Monero transaction"
+---
+
+### The Basics
+RingCT, short for Ring Confidential Transactions, is how transaction amounts are hidden in Monero.
+
+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.
+
+For more information, please read the creator Shen Noether's paper [here](https://eprint.iacr.org/2015/1098).
+
+
+{{ page.summary | capitalize }}.
+
+
+
+
+
+
diff --git a/_i18n/en/resources/moneropedia/ringsignatures.md b/_i18n/en/resources/moneropedia/ringsignatures.md
new file mode 100644
index 0000000000000000000000000000000000000000..fee368c89b6b6f1be32b1edf6213fdd1c56b75b3
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/ringsignatures.md
@@ -0,0 +1,18 @@
+---
+layout: moneropedia
+entry: "Ring Signature"
+terms: ["ring-signature", "ring-signatures"]
+summary: "a group of cryptographic signatures with at least one real participant, but no way to tell which in the group is the real one as they all appear valid"
+---
+
+### The Basics
+
+In cryptography, a ring signature is a type of digital signature that can be performed by any member of a group of users that each have keys. Therefore, a message signed with a ring signature is endorsed by someone in a particular group of people. One of the security properties of a ring signature is that it should be computationally infeasible to determine *which* of the group members' keys was used to produce the signature.
+
+For instance, a ring signature could be used to provide an anonymous signature from "a high-ranking White House official", without revealing which official signed the message. Ring signatures are right for this application because the anonymity of a ring signature cannot be revoked, and because the group for a ring signature can be improvised (requires no prior setup).
+
+### 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).
+
+To read how Monero gives you privacy by default (unlinkability), see @stealth-addresses.
\ No newline at end of file
diff --git a/_i18n/en/resources/moneropedia/router-info.md b/_i18n/en/resources/moneropedia/router-info.md
new file mode 100644
index 0000000000000000000000000000000000000000..f7c45c0608fb4337aa81a2d7f00fed97752387c1
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/router-info.md
@@ -0,0 +1,68 @@
+---
+layout: moneropedia
+entry: "Router-Info"
+tags: ["kovri"]
+terms: ["Router-Info", "Router-infos"]
+summary: "A data structure or file which contains an I2P peer's needed network information"
+---
+
+### The Basics
+
+@Router-Info is a data structure (periodically written to a [binary file](https://en.wikipedia.org/wiki/Binary_file)) which contains all needed information to locate, identify, and communicate with an @I2P peer. @Router-Info includes IP address, router identity, other misc. technical details; is needed for @network-database and is published to @floodfill routers.
+
+### In-depth information
+
+In human-readable form, Router-Info may look like this:
+
+```
+Identity: [RouterIdentity:
+Hash: nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=
+Certificate: [Certificate: type: Key certificate
+Crypto type: 0
+Sig type: 7 (EdDSA_SHA512_Ed25519)]
+PublicKey: [PublicKey: size: 256]
+SigningPublicKey: [SigningPublicKey EdDSA_SHA512_Ed25519: size: 32]
+Padding: 96 bytes]
+Signature: [Signature EdDSA_SHA512_Ed25519: size: 64]
+Published: Sun Oct 09 01:34:59 UTC 2016
+Options (5):
+ [caps] = [LfR]
+ [netId] = [2]
+ [netdb.knownLeaseSets] = [37]
+ [netdb.knownRouters] = [2435]
+ [router.version] = [0.9.26]
+Addresses (4):
+[RouterAddress:
+Type: SSU
+Cost: 4
+Options (5):
+ [caps] = [BC]
+ [host] = [2a01:e35:8b5c:b240:71a2:6750:8d4:47fa]
+ [key] = [nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=]
+ [mtu] = [1472]
+ [port] = [22244]]
+[RouterAddress:
+Type: NTCP
+Cost: 9
+Options (2):
+ [host] = [2a01:e35:8b5c:b240:71a2:6750:8d4:47fa]
+ [port] = [22244]]
+[RouterAddress:
+Type: SSU
+Cost: 6
+Options (4):
+ [caps] = [BC]
+ [host] = [88.181.203.36]
+ [key] = [nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=]
+ [port] = [22244]]
+[RouterAddress:
+Type: NTCP
+Cost: 11
+Options (2):
+ [host] = [88.181.203.36]
+ [port] = [22244]]]
+```
+
+### Notes
+
+For details and specification, visit @Java-I2P [Network Database](https://geti2p.net/en/docs/how/network-database) page.
diff --git a/_i18n/en/resources/moneropedia/scalability.md b/_i18n/en/resources/moneropedia/scalability.md
new file mode 100644
index 0000000000000000000000000000000000000000..efce0202090b89cfc7536cfbfe2e80286ff4209d
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/scalability.md
@@ -0,0 +1,10 @@
+---
+layout: moneropedia
+entry: "Scalability"
+terms: ["scalability"]
+summary: "Growth potential of Monero, resources required, and methods of increasing efficiency"
+---
+
+### The Basics
+
+Monero has no hardcoded maximum block size, which means that unlike Bitcoin it does not have a 1 MB block size limit preventing scaling. However, a block reward penalty mechanism is built into the protocol to avoid a too excessive block size increase: The new block's size (NBS) is compared to the median size M100 of the last 100 blocks. If NBS>M100, the block reward gets reduced in quadratic dependency of how much NBS exceeds M100. E.g. if NBS is [10%, 50%, 80%, 100%] greater than M100, the nominal block reward gets reduced by [1%, 25%, 64%, 100%]. Generally, blocks greater than 2*M100 are not allowed, and blocks <= 60kB are always free of any block reward penalties.
diff --git a/_i18n/en/resources/moneropedia/signature.md b/_i18n/en/resources/moneropedia/signature.md
new file mode 100644
index 0000000000000000000000000000000000000000..638b7c5bb26130703eead4b6f5585c6c18bef847
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/signature.md
@@ -0,0 +1,10 @@
+---
+layout: moneropedia
+entry: "Cryptographic Signature"
+terms: ["signature", "signatures"]
+summary: "a cryptographic method for proving ownership of a piece of information, as well as proving that the information has not been modified after being signed"
+---
+
+### The Basics
+
+{{ page.summary | capitalize }}.
\ No newline at end of file
diff --git a/_i18n/en/resources/moneropedia/smartmining.md b/_i18n/en/resources/moneropedia/smartmining.md
new file mode 100644
index 0000000000000000000000000000000000000000..c4f7a6d2e6af487b0dc8a7c205515539eb653f36
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/smartmining.md
@@ -0,0 +1,17 @@
+---
+layout: moneropedia
+entry: "Smart Mining"
+terms: ["smart-mining"]
+summary: "a process of having a throttled miner mine when it otherwise does not cause drawbacks"
+---
+
+### The Basics
+
+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/_i18n/en/resources/moneropedia/spendkey.md b/_i18n/en/resources/moneropedia/spendkey.md
new file mode 100644
index 0000000000000000000000000000000000000000..d57544d1ad9e636ad97f998ff3df4b66182fc39b
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/spendkey.md
@@ -0,0 +1,16 @@
+---
+layout: moneropedia
+entry: "Spend Key"
+terms: ["spend-key", "spend-keys"]
+summary: "one of the two pairs of private and public cryptographic keys that each account has, with the *private* spend key used to spend any funds in the account"
+---
+
+### The Basics
+
+{{ page.summary | capitalize }}.
+
+### In-depth Information
+
+The *private* spend key is a 256-bit integer that is used to sign Monero transactions. With the current deterministic key derivation method of the official wallet, the private spend key is also an alternate representation of the @mnemonic-seed. It can be used to derive all other account keys.
+
+
diff --git a/_i18n/en/resources/moneropedia/ssu.md b/_i18n/en/resources/moneropedia/ssu.md
new file mode 100644
index 0000000000000000000000000000000000000000..665f9c443a42ae39f281fb0b135145100c5a45c3
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/ssu.md
@@ -0,0 +1,26 @@
+---
+layout: moneropedia
+entry: "SSU"
+tags: ["kovri"]
+terms: ["SSU"]
+summary: "Secure Semi-reliable UDP: one of two Kovri transports"
+---
+
+### The Basics
+
+*Secure Semi-reliable UDP* is one of two encrypted @transports for @Kovri.
+
+Similar to @NTCP, @SSU's *primary* purpose is to securely transmit @in-net @I2NP messages through @tunnels but, unlike @NTCP, @SSU functions solely over encrypted [UDP](https://en.wikipedia.org/wiki/User_Datagram_Protocol).
+
+### In-depth information
+
+- Like @NTCP, @SSU is a connection-oriented, point-to-point data transport
+- Termed *semi-reliable* because @SSU will repeatedly retransmit *unacknowledged* messages (up to maximum number then dropped)
+- @SSU also provides several unique services (in addition to its function as a @transport layer):
+ - IP detection (local inspection or with [peer testing](https://geti2p.net/en/docs/transport/ssu#peerTesting))
+ - [NAT](https://en.wikipedia.org/wiki/Network_address_translation) traversal (using [introducers](https://geti2p.net/en/docs/transport/ssu#introduction))
+ - [Firewall](https://en.wikipedia.org/wiki/Firewall_%28computing%29) status and, if implemented, @SSU can notify @NTCP if the external address or firewall status changes
+
+### Notes
+
+For further details, read @Java-I2P's [SSU](https://geti2p.net/en/docs/transport/ssu)
diff --git a/_i18n/en/resources/moneropedia/stealthaddress.md b/_i18n/en/resources/moneropedia/stealthaddress.md
new file mode 100644
index 0000000000000000000000000000000000000000..61892d1b23c3bb0cb7d751f8191bccfab9ba90aa
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/stealthaddress.md
@@ -0,0 +1,16 @@
+---
+layout: moneropedia
+entry: "Stealth Address"
+terms: ["stealth-address", "stealth-addresses"]
+summary: "automatic one-time addresses for every transaction"
+---
+
+### The Basics
+
+Stealth addresses are an important part of Monero's inherent privacy. They allow and require the sender to create random one-time addresses for every @transaction on behalf of the recipient. The recipient can publish just one address, yet have all of his/her incoming payments go to unique addresses on the @blockchain, where they cannot be linked back to either the recipient's published address or any other transactions' addresses. By using stealth addresses, only the sender and receiver can determine where a payment was sent.
+
+When you create a Monero account you’ll have a private @view-key, a private @spend-key, and a Public Address. The @spend-key is used to send payments, the @view-key is used to display incoming transactions destined for your account, and the Public Address is for receiving payments. Both the @spend-key and @view-key are used to build your Monero address. You can have a “watch only†wallet that only uses the @view-key. This feature can be used for accounting or auditing purposes but is currently unreliable due to the inability to track outgoing transactions. You can decide who can see your Monero balance by sharing your @view-key. Monero is private by default and optionally semi-transparent!
+
+When using the Monero Wallet all this is handled by the software. Sending Monero is as easy as entering the destination address, the amount, and pressing Send. To recieve Monero, simply provide the sender your Public Address.
+
+To learn how Monero prevents tracking history (untraceability), see @ring-signatures.
diff --git a/_i18n/en/resources/moneropedia/subscription.md b/_i18n/en/resources/moneropedia/subscription.md
new file mode 100644
index 0000000000000000000000000000000000000000..b7411df5bec058a8baae7346e610cfe1f307501f
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/subscription.md
@@ -0,0 +1,47 @@
+---
+layout: moneropedia
+entry: "Subscription"
+tags: ["kovri"]
+terms: ["Subscription"]
+summary: "A file used by address book which contains I2P hosts paired with I2P destinations"
+---
+
+### The Basics
+
+A subscription is a file which contains a list of `.i2p` hosts paired with their respective @destination. Subscriptions are used by the @address-book.
+
+### 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`
+
+More specifically, a subscription pairs a @locally-unique-host to @base64-address.
+
+Example:
+
+```
+anonimal.i2p=AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLEov~usVliTSXCSHuRBOCIwIOuDNU0AbVa4BpIx~2sU4TxKhoaA3zQ6VzINoduTdR2IJhPvI5xzezp7dR21CEQGGTbenDslXeQ4iLHFA2~bzp1f7etSl9T2W9RID-KH78sRQmzWnv7dbhNodMbpO6xsf1vENf6bMRzqD5vgHEHZu2aSoNuPyYxDU1eM6--61b2xp9mt1k3ud-5WvPVg89RaU9ugU5cxaHgR927lHMCAEU2Ax~zUb3DbrvgQBOTHnJEx2Fp7pOK~PnP6ylkYKQMfLROosLDXinxOoSKP0UYCh2WgIUPwE7WzJH3PiJVF0~WZ1dZ9mg00c~gzLgmkOxe1NpFRNg6XzoARivNVB5NuWqNxr5WKWMLBGQ9YHvHO1OHhUJTowb9X90BhtHnLK2AHwO6fV-iHWxRJyDabhSMj1kuYpVUBQAEAAcAAA==
+```
+
+1. `anonimal.i2p` is the @locally-unique-host
+2. `=` is the separator
+3. Everything that remains is the @base64-address
+
+### Subscription types
+
+For @Kovri, there are two types of subscription files: *public* and *private*.
+
+A *public* subscription:
+- is used when bootstrapping to use essential services (IRC, email, Monero, etc.)
+- is static and is refreshed every 12 hours from Monero's @address-book server
+- allows you to safely share the subscription with everyone as it is publically available (anyone who shares the same public subscription will also be able to resolve the same hostname to the same destination as you)
+
+A *private* subscription:
+- is used exclusively by you and is not shared with others unless you explicitly choose to share the file
+- default file is `private_hosts.txt` in your @data-directory
+
+### Updating a private subscription
+
+You can use a @jump-service to manually update your private subscription. The updated subscription will then be fed into the @address-book for you to use.
+
+### Notes
+To learn how to subscribe to multiple subscriptions, see the [user-guide](https://github.com/monero-project/kovri/blob/master/doc/USER_GUIDE.md).
diff --git a/_i18n/en/resources/moneropedia/tail-emission.md b/_i18n/en/resources/moneropedia/tail-emission.md
new file mode 100644
index 0000000000000000000000000000000000000000..019e6fe14fef7e3ea22c02c1a9c995d7b3aa45a7
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/tail-emission.md
@@ -0,0 +1,16 @@
+---
+layout: moneropedia
+entry: "Tail Emission"
+terms: ["Tail-Emission"]
+summary: "the block reward at the end of the emission curve"
+---
+
+### The Basics
+
+Monero block rewards will never drop to zero. Block rewards will gradually drop until tail emission commences at the end of May 2022. At this point, rewards will be fixed at 0.6 XMR per block.
+
+### 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.
+
+Tail emission ensures that a dynamic block size and fee market can develop.
diff --git a/_i18n/en/resources/moneropedia/transaction.md b/_i18n/en/resources/moneropedia/transaction.md
new file mode 100644
index 0000000000000000000000000000000000000000..0064cb50bc7ead40d1fbfc398545cd6b8e1ccbf0
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/transaction.md
@@ -0,0 +1,21 @@
+---
+layout: moneropedia
+entry: "Transactions"
+terms: ["transaction", "transactions"]
+summary: "a cryptographically signed container that details the transfer of Monero to a recipient (or recipients)"
+---
+
+### The Basics
+
+{{ 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.
+
+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).
+
+### In-depth Information
+Every transaction involves two keys: a public @spend-key, and a public @view-key. The destination for an output in a transaction is actually a one-time public key computed from these two keys.
+
+When a wallet is scanning for incoming transactions, every transaction is scanned to see if it is for "you". This only requires your private view key and your public spend key, and this check is immutable and cannot be faked. You cannot receive transactions and identify them without a corresponding private view key.
+
+In order to spend the funds you have to compute a one-time private spend key for that output. This is almost always done automatically by the Monero Wallet software.
diff --git a/_i18n/en/resources/moneropedia/transports.md b/_i18n/en/resources/moneropedia/transports.md
new file mode 100644
index 0000000000000000000000000000000000000000..59504f99c58bc7205dd3283870de2f26f7205494
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/transports.md
@@ -0,0 +1,20 @@
+---
+layout: moneropedia
+entry: "Transports"
+tags: ["kovri"]
+terms: ["Transports", "Transport"]
+summary: "The two encrypted transport layers for Kovri"
+---
+
+### The Basics
+
+@I2P comes with two encrypted transport layer technologies that allow @Kovri to securely use [TCP/IP](https://en.wikipedia.org/wiki/Tcp/ip) connections. These technologies (@SSU and @NTCP) are called *@transports*.
+
+### In-depth information
+
+@SSU is encrypted [UDP](https://en.wikipedia.org/wiki/User_Datagram_Protocol) and @NTCP is encrypted [TCP](https://en.wikipedia.org/wiki/Transmission_Control_Protocol). They provide @encryption at the [transport layer](https://en.wikipedia.org/wiki/Transport_layer) so higher level @messages can be sent through @tunnels across the @I2P network.
+
+### Notes
+
+- Read about @I2P's transports on the [Transport](https://geti2p.net/en/docs/transport) page
+- Read about the transports layer within the [OSI model](https://en.wikipedia.org/wiki/OSI_model)
diff --git a/_i18n/en/resources/moneropedia/tunnel.md b/_i18n/en/resources/moneropedia/tunnel.md
new file mode 100644
index 0000000000000000000000000000000000000000..d22e2b944ab72596fe894d41a941b6c2f5f9d85e
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/tunnel.md
@@ -0,0 +1,37 @@
+---
+layout: moneropedia
+entry: "Tunnel"
+tags: ["kovri"]
+terms: ["Tunnel", "Tunnels"]
+summary: "Uni-directional virtual paths that pass messages through a defined sequence of I2P routers"
+---
+
+### The Basics
+
+When you communicate over @I2P (visit an @eepsite / use a @garlic-service), you'll first need to connect to a peer by using @transports and then build virtual *tunnels*. These virtual tunnels are temporary, uni-directional paths that pass information through a defined sequence of @I2P routers to your @destination. Tunnels are built, and then used, with layered @garlic-encryption and are a general-purpose mechanism to transport all @I2NP @messages.
+
+Each peer builds, at a minimum, *two* uni-directional tunnels: one for **outbound traffic**, and one for **inbound traffic**. These tunnels are classified as either **inbound tunnels** (where @messages come toward the creator of the tunnel) or **outbound tunnels** (where the tunnel creator sends @messages away from the creator of the tunnel). Thus, *four* tunnels are required for a single round-trip @message and reply to your @destination (two for your, two for your destination).
+
+### In-depth information
+
+From @Java-I2P:
+
+>
+Within I2P, @messages are passed in one direction through a virtual tunnel of peers, using whatever means are available to pass the @message on to the next hop. Messages arrive at the tunnel's gateway, get bundled up and/or fragmented into fixed-size @tunnel @messages, and are forwarded on to the next hop in the tunnel, which processes and verifies the validity of the @message and sends it on to the next hop, and so on, until it reaches the @tunnel endpoint. That endpoint takes the messages bundled up by the gateway and forwards them as instructed - either to another router, to another tunnel on another router, or locally.
+
+>
+Tunnels all work the same, but can be segmented into two different groups - inbound tunnels and outbound tunnels. The inbound tunnels have an untrusted gateway which passes messages down towards the tunnel creator, which serves as the tunnel endpoint. For outbound tunnels, the tunnel creator serves as the gateway, passing messages out to the remote endpoint.
+
+>
+The tunnel's creator selects exactly which peers will participate in the tunnel, and provides each with the necessary configuration data. They may have any number of hops. It is the intent to make it hard for either participants or third parties to determine the length of a tunnel, or even for colluding participants to determine whether they are a part of the same tunnel at all (barring the situation where colluding peers are next to each other in the tunnel).
+
+### Notes
+
+From @Java-I2P:
+
+>
+@I2P is an inherently packet switched network, even with these tunnels, allowing it to take advantage of multiple tunnels running in parallel, increasing resilience and balancing load. Even though the tunnels within I2P bear a resemblance to a circuit switched network, everything within I2P is strictly message based - tunnels are merely accounting tricks to help organize the delivery of messages. No assumptions are made regarding reliability or ordering of messages, and retransmissions are left to higher levels (e.g. I2P's client layer streaming library).
+
+### Documentation
+
+For specification and detailed documentation, visit the [Tunnel-Routing](https://geti2p.net/en/docs/how/tunnel-routing) and [Tunnel-Implementation](https://geti2p.net/en/docs/tunnels/implementation) page.
diff --git a/_i18n/en/resources/moneropedia/unlocktime.md b/_i18n/en/resources/moneropedia/unlocktime.md
new file mode 100644
index 0000000000000000000000000000000000000000..08a35f8e0025aa2f825b7f931b04707b8eba7818
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/unlocktime.md
@@ -0,0 +1,14 @@
+---
+layout: moneropedia
+entry: "Transaction Unlock Time"
+terms: ["unlock-time"]
+summary: "a special transaction where the recipient can only spend the funds after a future date, as set by the sender"
+---
+
+### The Basics
+
+{{ page.summary | capitalize }}.
+
+Unlock time allows you to send a transaction to someone, such that they can not spend it until after a certain number of blocks, or until a certain time.
+
+Note that this works differently than Bitcoin's [nLockTime](https://en.bitcoin.it/wiki/NLockTime), in which the transaction is not valid until the given time.
diff --git a/_i18n/en/resources/moneropedia/viewkey.md b/_i18n/en/resources/moneropedia/viewkey.md
new file mode 100644
index 0000000000000000000000000000000000000000..719a96b9943755f98cd661bacc25147cdd3a8957
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/viewkey.md
@@ -0,0 +1,16 @@
+---
+layout: moneropedia
+entry: "View Key"
+terms: ["view-key", "view-keys"]
+summary: "one of two sets of private and public cryptographic keys that each account has, with the private view key required to view all transactions related to the account"
+---
+
+### 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 }}.
diff --git a/_i18n/en/resources/moneropedia/wallet.md b/_i18n/en/resources/moneropedia/wallet.md
new file mode 100644
index 0000000000000000000000000000000000000000..759b018d3d36a750800687d1e14266927a77092f
--- /dev/null
+++ b/_i18n/en/resources/moneropedia/wallet.md
@@ -0,0 +1,19 @@
+---
+layout: moneropedia
+entry: "Wallet"
+terms: ["wallet", "wallets"]
+summary: "A wallet stores the information necessary to send and receive Monero"
+---
+
+### The Basics
+
+A Monero account, or wallet, stores the information necessary to send and receive Moneroj. In addition to sending and receiving, the Monero Wallet software keeps a private history of your transactions and allows you to cryptographically sign messages. It also includes Monero mining software and an address book.
+
+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 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.
+
+Monero accounts and paper-wallets can be stored on any media - paper, USB drive, CD/DVD, or a hardware wallet device (none available for Monero as of June 2017).
+
diff --git a/_i18n/en/resources/research-lab.md b/_i18n/en/resources/research-lab.md
new file mode 100644
index 0000000000000000000000000000000000000000..6b257e05d6861a1cd9751b8ebce310e8357e9b5c
--- /dev/null
+++ b/_i18n/en/resources/research-lab.md
@@ -0,0 +1,163 @@
+<div class="container description">
+<p>Monero is not only committed to making a fungible currency, but also to continued research into the realm of financial privacy as it involves cryptocurrencies. Below you'll find the work of our very own Monero Research Lab, with more papers to come.</p>
+</div>
+
+<section class="container">
+ <div class="row">
+ <!-- left two-thirds block-->
+ <div class="left two-thirds col-lg-8 col-md-8 col-sm-12 col-xs-12">
+ <div class="info-block research-paper">
+ <div class="row center-xs">
+ <div class="col"><h2>Monero Research Lab Papers</h2></div>
+ </div>
+ <div class="tab">
+ <input id="tab-one" type="checkbox" name="tabs" class="accordion" checked="checked">
+ <label for="tab-one" class="accordion">MRL-0001: A Note on Chain Reactions in Traceability in CryptoNote 2.0</label>
+ <div class="tab-content">
+ <p><strong>Abstract:</strong> This research bulletin describes a plausible attack on a ring-signature based
+ anonymity system. We use as motivation the cryptocurrency protocol CryptoNote
+ 2.0 ostensibly published by Nicolas van Saberhagen in 2012. It has been
+ previously demonstrated that the untraceability obscuring a one-time key pair can
+ be dependent upon the untraceability of all of the keys used in composing that
+ ring signature. This allows for the possibility of chain reactions in traceability
+ between ring signatures, causing a critical loss in untraceability across the whole
+ network if parameters are poorly chosen and if an attacker owns a sufficient
+ percentage of the network. The signatures are still one-time, however, and any
+ such attack will still not necessarily violate the anonymity of users. However, such
+ an attack could plausibly weaken the resistance CryptoNote demonstrates against
+ blockchain analysis. This research bulletin has not undergone peer review, and
+ reflects only the results of internal investigation.
+ <br>
+ <br>
+ <a target="_blank" rel="noreferrer noopener" href="https://lab.getmonero.org/pubs/MRL-0001.pdf">Read Paper</a>
+ </p>
+ </div>
+ </div>
+ <div class="tab">
+ <input id="tab-two" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-two" class="accordion">MRL-0002: Counterfeiting via Merkle Tree Exploits within Virtual Currencies Employing the CryptoNote Protocol</label>
+ <div class="tab-content">
+ <p><strong>Abstract:</strong> On 4 September 2014, an unusual and novel attack was executed against the
+ Monero cryptocurrency network. This attack partitioned the network into two
+ distinct subsets which refused to accept the legitimacy of the other subset. This
+ had myriad effects, not all of which are yet known. The attacker had a short
+ window of time during which a sort of counterfeiting could occur, for example.
+ This research bulletin describes deficiencies in the CryptoNote reference code
+ allowing for this attack, describes the solution initially put forth by Rafal Freeman
+ from Tigusoft.pl and subsequently by the CryptoNote team, describes the current
+ fix in the Monero code base, and elaborates upon exactly what the offending
+ block did to the network. This research bulletin has not undergone peer review,
+ and reflects only the results of internal investigation.<br>
+ <br>
+ <a target="_blank" rel="noreferrer noopener" href="https://lab.getmonero.org/pubs/MRL-0002.pdf">Read Paper</a></p>
+
+ </div>
+ </div>
+ <div class="tab">
+ <input id="tab-three" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-three" class="accordion">MRL-0003: Monero is Not That Mysterious</label>
+ <div class="tab-content">
+ <p><strong>Introduction:</strong> Recently, there have been some vague fears about the CryptoNote source code and
+ protocol floating around the internet based on the fact that it is a more complicated
+ protocol than, for instance, Bitcoin. The purpose of this note is to try and clear
+ up some misconceptions, and hopefully remove some of the mystery surrounding
+ Monero Ring Signatures. I will start by comparing the mathematics involved in
+ CryptoNote ring signatures (as described in [CN]) to the mathematics in [FS], on
+ which CryptoNote is based. After this, I will compare the mathematics of the ring
+ signature to what is actually in the CryptoNote codebase.<br>
+ <br>
+ <a target="_blank" rel="noreferrer noopener" href="https://lab.getmonero.org/pubs/MRL-0003.pdf">Read Paper</a></p>
+ </div>
+ </div>
+ <div class="tab">
+ <input id="tab-four" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-four" class="accordion">MRL-0004: Improving Obfuscation in the CryptoNote Protocol</label>
+ <div class="tab-content">
+ <p><strong>Abstract:</strong> We identify several blockchain analysis attacks available to degrade the
+untraceability of the CryptoNote 2.0 protocol. We analyze possible solutions,
+discuss the relative merits and drawbacks to those solutions, and recommend
+improvements to the Monero protocol that will hopefully provide long-term
+resistance of the cryptocurrency against blockchain analysis. Our recommended
+improvements to Monero include a protocol-level network-wide minimum mix-in
+policy of
+n
+= 2
+foreign outputs per ring signature, a protocol-level increase of this
+value to
+n
+= 4
+after two years, and a wallet-level default value of
+n
+= 4
+in the
+interim. We also recommend a torrent-style method of sending Monero output.
+We also discuss a non-uniform, age-dependent mix-in selection method to
+mitigate the other forms of blockchain analysis identified herein, but we make no
+formal recommendations on implementation for a variety of reasons. The
+ramifications following these improvements are also discussed in some detail.
+This research bulletin has not undergone peer review, and reflects only the
+results of internal investigation.<br>
+ <br>
+ <a target="_blank" rel="noreferrer noopener" href="https://lab.getmonero.org/pubs/MRL-0004.pdf">Read Paper</a></p>
+ </div>
+ </div>
+ <div class="tab">
+ <input id="tab-five" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-five" class="accordion">MRL-0005: Ring Signature Confidential Transactions</label>
+ <div class="tab-content">
+ <p><strong>Abstract:</strong> This article introduces a method of hiding transaction amounts in the strongly
+decentralized anonymous cryptocurrency Monero. Similar to Bitcoin, Monero is a
+cryptocurrency which is distributed through a proof of work “mining†process.
+The original Monero protocol was based on CryptoNote, which uses ring
+signatures and one-time keys to hide the destination and origin of transactions.
+Recently the technique of using a commitment scheme to hide the amount of a
+transaction has been discussed and implemented by Bitcoin Core Developer
+Gregory Maxwell. In this article, a new type of ring signature, A Multi-layered
+Linkable Spontaneous Anonymous Group signature is described which allows for
+hidden amounts, origins and destinations of transactions with reasonable
+efficiency and verifiable, trustless coin generation. Some extensions of the
+protocol are provided, such as Aggregate Schnorr Range Proofs, and Ring
+Multisignature. The author would like to note that early drafts of this were
+publicized in the Monero Community and on the bitcoin research irc channel.
+Blockchain hashed drafts are available in [14] showing that this work was started
+in Summer 2015, and completed in early October 2015. An eprint is also
+available at
+http://eprint.iacr.org/2015/1098
+.<br>
+ <br>
+ <a href="https://lab.getmonero.org/pubs/MRL-0005.pdf" target="_blank" rel="noreferrer noopener">Read Paper</a></p>
+ </div>
+ </div>
+ </div>
+ </div>
+ <!-- end left two-thirds block-->
+
+ <!-- right one-third block-->
+ <div class="right one-third col-lg-4 col-md-4 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Cryptonote Whitepapers</h2>
+ </div>
+
+ </div>
+<div markdown="1">
+
+[Cryptonote Whitepaper](https://cryptonote.org/whitepaper.pdf)
+
+This is the original cryptonote paper written by the cryptonote team. Reading it will give an understanding about how the cryptonote algorithm works in general.
+
+[Annotated Whitepaper](https://downloads.getmonero.org/whitepaper_annotated.pdf)
+
+The Monero Research Lab released an annotated version of the cryptonote whitepaper. This is sort of like an informal review of the claims that are made line-by-line of the whitepaper. It also explains some of the harder concepts in relatively easy to understand terms.
+
+[Brandon Goodell's Whitepaper Review](https://downloads.getmonero.org/whitepaper_review.pdf)
+
+This paper is a formal review of the original cryptonote paper by MRL researcher Brandon Goodell. He takes an in-depth look at the claims and mathematics presented in the cryptonote paper.
+
+</div>
+ </div>
+ </div>
+ <!-- end right one-third block-->
+ </div>
+</section>
diff --git a/_i18n/en/resources/roadmap.md b/_i18n/en/resources/roadmap.md
new file mode 100644
index 0000000000000000000000000000000000000000..270031bc149346e4a52ad991de233f6603b001b5
--- /dev/null
+++ b/_i18n/en/resources/roadmap.md
@@ -0,0 +1,129 @@
+<div class="roadmap">
+<div class="text-center pre-roadmap container">
+ <div class="row">
+ <div class="col-xs-4">
+ <li class="completed"></li>
+ <p>Completed task</p>
+ </div>
+ <div class="col-xs-4">
+ <li class="ongoing"></li>
+ <p>Ongoing task</p>
+ </div>
+ <div class="col-xs-4">
+ <li class="upcoming"></li>
+ <p>Upcoming task</p>
+ </div>
+ </div>
+</div>
+<section class="container">
+ <div class="row">
+ <div class="col-lg-12 col-md-12 col-sm-12 col-xs-12">
+ <div class="tabPanel-widget">
+ <label for="tab-1" tabindex="0"></label>
+ <input id="tab-1" type="radio" name="tabs" aria-hidden="true">
+ <h2>2014</h2>
+ <div class="tabPanel-content">
+ {% for toplevel in site.data.lang[site.lang].roadmap %}
+ {% if toplevel.year == 2014 %}
+ {% for roadlist in toplevel.accomplishments %}
+ <div class="row start-xs middle-xs">
+ <div class="col-xs-1">
+ <span class="{{roadlist.status}}"></span>
+ </div>
+ <div class="col-xs-11">
+ <p>{{roadlist.date}}: {{roadlist.name}}</p>
+ </div>
+ </div>
+ {%endfor%}
+ {%endif%}
+ {%endfor%}
+ </div>
+ <label for="tab-2" tabindex="0"></label>
+ <input id="tab-2" type="radio" name="tabs" aria-hidden="true">
+ <h2>2015</h2>
+ <div class="tabPanel-content">
+ {% for toplevel in site.data.lang[site.lang].roadmap %}
+ {% if toplevel.year == 2015 %}
+ {% for roadlist in toplevel.accomplishments %}
+ <div class="row start-xs middle-xs">
+ <div class="col-xs-1">
+ <span class="{{roadlist.status}}"></span>
+ </div>
+ <div class="col-xs-11">
+ <p>{{roadlist.date}}: {{roadlist.name}}</p>
+ </div>
+ </div>
+ {%endfor%}
+ {%endif%}
+ {%endfor%}
+ </div>
+ <label for="tab-3" tabindex="0"></label>
+ <input id="tab-3" type="radio" name="tabs" aria-hidden="true">
+ <h2>2016</h2>
+ <div class="tabPanel-content">
+ {% for toplevel in site.data.lang[site.lang].roadmap %}
+ {% if toplevel.year == 2016 %}
+ {% for roadlist in toplevel.accomplishments %}
+ <div class="row start-xs middle-xs">
+ <div class="col-xs-1">
+ <span class="{{roadlist.status}}"></span>
+ </div>
+ <div class="col-xs-11">
+ <p>{{roadlist.date}}: {{roadlist.name}}</p>
+ </div>
+ </div>
+ {%endfor%}
+ {%endif%}
+ {%endfor%}
+ </div>
+ <label for="tab-4" tabindex="0"></label>
+ <input id="tab-4" type="radio" name="tabs" aria-hidden="true" checked>
+ <h2>2017</h2>
+ <div class="tabPanel-content">
+ {% for toplevel in site.data.lang[site.lang].roadmap %}
+ {% if toplevel.year == 2017 %}
+ {% for roadlist in toplevel.accomplishments %}
+ <div class="row start-xs middle-xs">
+ <div class="col-xs-1">
+ <span class="{{roadlist.status}}"></span>
+ </div>
+ <div class="col-xs-11">
+ {% if roadlist.date %}
+ <p>{{roadlist.date}}: {{roadlist.name}}</p>
+ {%else%}
+ <p>{{roadlist.name}}</p>
+ {%endif%}
+ </div>
+ </div>
+ {%endfor%}
+ {%endif%}
+ {%endfor%}
+ </div>
+ <label for="tab-5" tabindex="0"></label>
+ <input id="tab-5" type="radio" name="tabs" aria-hidden="true">
+ <h2>Future</h2>
+ <div class="tabPanel-content">
+ {% for toplevel in site.data.lang[site.lang].roadmap %}
+ {% if toplevel.year == 2018 %}
+ {% for roadlist in toplevel.accomplishments %}
+ <div class="row start-xs">
+ <div class="col-xs-1">
+ <span class="{{roadlist.status}}"></span>
+ </div>
+ <div class="col-xs-11">
+ {% if roadlist.date %}
+ <p>{{roadlist.date}}: {{roadlist.name}}</p>
+ {%else%}
+ <p>{{roadlist.name}}</p>
+ {%endif%}
+ </div>
+ </div>
+ {%endfor%}
+ {%endif%}
+ {%endfor%}
+ </div>
+ </div>
+ </div>
+ </div>
+</section>
+</div>
\ No newline at end of file
diff --git a/_i18n/en/resources/user-guides/How-to-mine-Monero-XMR-without-a-mining-equipment.md b/_i18n/en/resources/user-guides/How-to-mine-Monero-XMR-without-a-mining-equipment.md
new file mode 100644
index 0000000000000000000000000000000000000000..4e130bf73994bc58f61f88fe9b003928853e5845
--- /dev/null
+++ b/_i18n/en/resources/user-guides/How-to-mine-Monero-XMR-without-a-mining-equipment.md
@@ -0,0 +1,48 @@
+## How to mine Monero (XMR) without a mining equipment?
+
+If you don’t have a profitable mining equipment, nor time or
+money to invest into building it, you can still mine Monero with NiceHash.
+
+NiceHash is a hashing power marketplace. Sellers of hashing
+power, i.e. miners, provide the hashing power for buyers (those who want to buy
+a service of mining a certain coin). Hence, NiceHash can provide you a massive
+hashing power in short amount of time. You won’t have to wait for years to see
+if you will make a profit or not and you can control which coin, at which pool,
+and for how long you want to mine.
+
+### **Step 1:** Create new account at NiceHash
+
+Visit [registration
+page](https://www.nicehash.com/?p=register) and register with your e-mail address.
+
+### **Step 2:** Deposit some Bitcoins to your account
+
+You will mine Monero, but you can buy hashing power at
+NiceHash only with Bitcoins. You can always withdraw unspent Bitcoins from your
+account back to any Bitcoin wallet.
+
+Visit your [wallet
+page](https://www.nicehash.com/?p=wallet) and make a deposit. Note that the minimum price for placing an order
+equals 0.01 BTC.
+
+### **Step 3:** Find a suitable pool for mining and add it to your pool list
+
+Selection of the pool plays a big role in the final amount
+of mined cryptocurrency. Make sure the pool you have selected can handle
+massive hashing rate and loads of shares, especially from a single connection.
+You can find a list of Monero pools [here](https://bitcointalk.org/index.php?topic=583449.0).
+
+Note that you will probably have to register an account at
+selected pool as well. The pool will provide you with all the information you need.
+You can save your favorite pools at [this page](https://www.nicehash.com/?p=managepools).
+
+### **Step 4:** Create new order and start mining
+
+When creating a [new order](https://www.nicehash.com/?p=orders&new), make sure you
+select CryptoNight algorithm for mining Monero. If you want to first learn more
+about placing an order with NiceHash, we recommend you to read this [frequently asked question](https://www.nicehash.com/?p=faq#faqb0).
+
+If you want to bid on
+hashing power select Standard (bidding) order type and if you want a fixed
+order that cannot be outbid, select Fixed order type. The status of marketplace
+and approximate prices of mining can be checked at [live marketplace](https://www.nicehash.com/index.jsp?p=orders).Â
\ No newline at end of file
diff --git a/_i18n/en/resources/user-guides/Offline_Backup.md b/_i18n/en/resources/user-guides/Offline_Backup.md
new file mode 100644
index 0000000000000000000000000000000000000000..c9dd879cea5aa2b43e79835ec579c72c12f6a52a
--- /dev/null
+++ b/_i18n/en/resources/user-guides/Offline_Backup.md
@@ -0,0 +1,36 @@
+## Operating Systems: Various versions of Linux and Windows 7, 8
+
+### Wallet Software: Simplewallet
+
+#### Resource for Creating Bootable Disks: [Linux](http://www.pendrivelinux.com/), [Windows](https://www.microsoft.com/en-us/download/windows-usb-dvd-download-tool)
+
+#### Resource for Monero Binaries: [Monero Binaries](https://getmonero.org/downloads/)
+
+- Take any computer you have lying around, even your normal workstation. You may find it easier to use an older computer that has no wifi or bluetooth if you're particularly paranoid
+
+- Create a Linux or Windows bootable disk, and make sure you have the Monero binaries on the same disk or on a second disk (for Linux make sure you have also downloaded copies of the dependencies you will need, libboost1.55 and miniupnpc for instance)
+
+- Disconnect the network and/or Internet cables from your computer, physically remove the wifi card or switch the wifi/bluetooth off on a laptop if possible
+
+- Boot into your bootable OS, install the dependencies if necessary
+
+- Copy the Monero binaries to a RAM disk (/dev/shm in Linux, Windows bootable ISOs normally have a Z: drive or something)
+
+- Don't run the Monero daemon. Instead, using the command line, use monero-wallet-cli to create a new Monero @account
+
+- When prompted for a name, give it any name, it doesn't really matter
+
+- When prompted for a password, type in like 50 - 100 random characters. Don't worry that you don't know the password, just make it LONG
+
+- **CRITICAL STEP**: Write down (on paper) your 25 word @mnemonic-seed
+**WARNING**: If you forget to write down this information your funds may be lost forever
+
+- Write down (on your phone, on paper, on another computer, wherever you want) your address and view key
+
+- Switch off the computer, remove the battery if there is one, and leave it physically off for a few hours
+
+The account you've created was created in RAM, and the digital files are now inaccessible. If some adversary manages to somehow obtain the data, they will lack the long password to open it. If you need to receive payments, you have your public address, and you have the view key if needed. If you need access to it, you have your 25 word @mnemonic-seed, and you can now write out several copies of it, including an offsite copy (e.g. a bank deposit box).
+
+Credit: Riccardo Spagni
+
+Related: [Offline Account Generator](http://moneroaddress.org/)
diff --git a/_i18n/en/resources/user-guides/create_wallet.md b/_i18n/en/resources/user-guides/create_wallet.md
new file mode 100644
index 0000000000000000000000000000000000000000..a4e7222b572471773d04be1922ab124afb96bad3
--- /dev/null
+++ b/_i18n/en/resources/user-guides/create_wallet.md
@@ -0,0 +1,60 @@
+### Operating Systems: Ubuntu
+
+- Download the [official binaries](https://getmonero.org/downloads/) or compile the last source available on [Github](https://github.com/monero-project/bitmonero)
+
+
+
+
+- Extract the files with the archive manager (same as Winzip on Windows). Note the path where the files "monerod" and "monero-wallet-cli" are
+
+
+
+
+- You only need to do this step once : open a terminal (ctrl+alt+t) and install the required dependencies by typing : "*sudo apt-get install libboost-all-dev libssl-dev libevent-dev libdb++-dev*". When asked, press the Y key and then Enter to continue
+
+
+
+
+- Open a terminal and load the path where your binaries are extracted (cf. step 2) by typing : "*cd yourPathFromStep2*"
+
+
+
+- Load monerod by typing in your terminal : "*./monerod*". Wait for the synchronization with the network (monerod is updating the blockchain you have downloaded in step 4 or is downloading it from scratch). This can take a lot of time the first time, so be patient
+
+
+
+
+
+
+- Once monerod is synchronized with the network, open a new terminal, change the directory (cf. step 5), and launch monero-wallet-cli by typing "*./monero-wallet-cli*"
+
+
+
+- Enter the name you want for your portfolio and follow the instructions from the terminal
+
+
+
+
+
+
+*This is your private key. Write it down and keep it in a safe place!*
+
+
+
+*This is your view key. You need it to create a view only wallet (cf. associated user guide)*
+
+
+
+*This is the address of your wallet*
+
+
+
+
+
+
+
+- To exit monerod or monero-wallet-cli just type "*exit*" in the associated terminal
+
+Now to access the portfolio you have just created you will have to launch monerod, wait for it to be synchronized with the network, launch monero-wallet-cli, and type the name of your portfolio and your password.
+
+
diff --git a/_i18n/en/resources/user-guides/easiest_buy.md b/_i18n/en/resources/user-guides/easiest_buy.md
new file mode 100644
index 0000000000000000000000000000000000000000..d5b6ce4fec5a3da63c75543e49f5241b098d8964
--- /dev/null
+++ b/_i18n/en/resources/user-guides/easiest_buy.md
@@ -0,0 +1,64 @@
+## How to obtain Monero
+
+This is a guide to obtain your own Monero as of 20150919. This is perhaps the easiest way to purchase and hold Monero.
+
+####Step 1: Buy Bitcoin
+
+There are many ways to buy Bitcoin. Perhaps the easiest way is through circle.com. Once you have purchased some Bitcoin, you are ready to buy some Monero! Buying Bitcoin is straightforward. Please goto circle.com and just follow the instructions there.
+
+####Step 2: Set up a mymonero.com account
+
+MyMonero.com is an online wallet for Monero, maintained by Monero Core Developer Ricardo Spagni (fluffpony). It is the easiest wallet to use. Simply go to MyMonero.com and click on the "Create an Account" button.
+
+
+
+After clicking the button, you will see your private key. This key is what gives you access to your funds. Never share this key with anyone!
+
+### WRITE DOWN THIS KEY IMMEDIATELY!
+
+
+
+Type in your private key in the box below, and click the button.
+
+On the next page, you will see your address.
+
+
+
+Copy your address to the clipboard by highlighting the whole thing and hitting ctrl+c (or edit menu, copy), or clicking the little icon next to your address. Save your address somewhere. This is how others will send Monero to you, and what you will use to deposit Monero into your account!
+
+#### Step 3: Buy Monero and transfer the Monero to your new address
+
+Go to www.shapeshift.io . On the righthand side, of the screen, click icon under "Receive" to select Monero.
+
+
+
+
+Paste your address into the field under the Monero logo. Select the "agree to terms" button, then hit "Start"
+
+
+
+In the new screen that pops up, copy the Deposit Address into your clipboard (select and hit ctrl+c or edit-copy)
+
+
+
+Go back to your circle.com page, hit the "transfer" button, and paste the Bitcoin address into the field
+Enter the amount of Bitcoin you would like to spend.
+
+
+
+
+You will get a text message verification code. Enter code and hit send.
+
+
+
+You will see the shapeshift change to "awaiting exchange"
+
+
+
+Then it will change to COMPLETE!
+
+
+
+After a while you will see it in your Monero account
+
+
diff --git a/_i18n/en/resources/user-guides/howto_fix_stuck_funds.md b/_i18n/en/resources/user-guides/howto_fix_stuck_funds.md
new file mode 100644
index 0000000000000000000000000000000000000000..17a16d7cf3e2ddb4a5e8e429ebfda510583a831c
--- /dev/null
+++ b/_i18n/en/resources/user-guides/howto_fix_stuck_funds.md
@@ -0,0 +1,30 @@
+Sometimes, your funds will become stuck - you will have some locked funds that never become unlocked. This is how you fix it.
+
+- Load your wallet in monero-wallet-cli.
+
+- Type
+
+> seed
+
+into the command prompt. Write down your 25 word seed, if you haven't already. This is the best way to make sure you don't loose access to your funds.
+
+- Close monero-wallet-cli by typing
+
+> exit
+
+- Backup all of your wallet related files. These include:
+
+> yourwalletname.bin
+> yourwalletname.bin.keys
+> yourwalletname.bin.address.txt
+
+This can be done by copying the files to a new folder.
+
+Sometimes, when creating your wallet, you might have named it something without the .bin part. In that case, the wallet file will be called yourwalletname without the .bin at the end.
+
+- Delete yourwallet.bin
+
+- Load monero-wallet-cli, type in the name of the wallet you just deleted
+
+- Enter password. The wallet will now refresh and hopefully your locked funds will now become unlocked.
+
diff --git a/_i18n/en/resources/user-guides/importing_blockchain.md b/_i18n/en/resources/user-guides/importing_blockchain.md
new file mode 100644
index 0000000000000000000000000000000000000000..c1c2f55cf90912c62e813fa64cedfa1fd7c66fbd
--- /dev/null
+++ b/_i18n/en/resources/user-guides/importing_blockchain.md
@@ -0,0 +1,56 @@
+# Importing the Blockchain to Monero GUI wallet (Windows)
+
+### Step 1
+
+Download the Current bootstrap from https://downloads.getmonero.org/blockchain.raw; you can skip this step if you are importing the Blockchain from another source.
+
+### Step 2
+
+Find the path of your Monero wallet (the folder where you extracted your wallet). For example mine is:
+
+`D:\monero-gui-0.10.3.1`
+
+Your path may be different depending on where you decided to download your wallet and what version of the Monero wallet you have.
+
+### Step 3
+
+Find the path of your downloaded Blockchain for example mine was:
+
+`C:\Users\KeeJef\Downloads\blockchain.raw`
+
+Yours might be different depending on where you downloaded the Blockchain to.
+
+### Step 4
+
+Open a Command Prompt window. You can do this by pressing the Windows key + R, and then typing in the popup box `CMD`
+
+### Step 5
+
+Now you need to navigate using the CMD window to the path of your Monero wallet. You can do this by typing:
+
+`cd C:\YOUR\MONERO\WALLET\FILE\PATH\HERE`
+
+It should look something like:
+
+`cd D:\monero-gui-0.10.3.1`
+
+If your Monero wallet is on another drive you can use `DriveLetter:` for example if your Monero wallet was on your D drive then before using the cd command you would do `D:`
+
+### Step 6
+
+Now type in your command prompt window:
+
+`monero-blockchain-import --verify 1 --input-file C:\YOUR\BLOCKCHAIN\FILE\PATH\HERE`
+
+For example I would type :
+
+`monero-blockchain-import --verify 1 --input-file C:\Users\KeeJef\Downloads\blockchain.raw`
+
+If you downloaded the Blockchain from a trusted, reputable source you may set `verify 0` this will reduce the amount of time to sync the Blockchain.
+
+### Step 7
+
+After the 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/_i18n/en/resources/user-guides/index.md b/_i18n/en/resources/user-guides/index.md
new file mode 100644
index 0000000000000000000000000000000000000000..1887545084a6359a337b0958dbcf6a9fb0a3eb41
--- /dev/null
+++ b/_i18n/en/resources/user-guides/index.md
@@ -0,0 +1,82 @@
+<div class="guides">
+<section class="container">
+ <div class="row">
+ <div class="left half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>General</h2>
+ </div>
+ </div>
+<div class="row start-xs" markdown="1">
+
+[Monero Tools]({{site.baseurl}}/resources/user-guides/monero_tools.html)
+[How to make an offline backup]({{site.baseurl}}/resources/user-guides/Offline_Backup.html)
+[Importing the Monero blockchain]({{site.baseurl}}/resources/user-guides/importing_blockchain.html)
+[How to run a node on VPS]({{site.baseurl}}/resources/user-guides/vps_run_node.html)
+[Securely purchasing and storing Monero]({{site.baseurl}}/resources/user-guides/securely_purchase.html)
+
+</div>
+ </div>
+ </div>
+ <div class="right half col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Wallets</h2>
+ </div>
+ </div>
+<div class="row start-xs" markdown="1">
+
+[Getting started with the CLI wallet]({{site.baseurl}}/resources/user-guides/monero-wallet-cli.html)
+[How to make a view-only wallet]({{site.baseurl}}/resources/user-guides/view_only.html)
+[How to prove payment]({{site.baseurl}}/resources/user-guides/prove-payment.html)
+[Restoring wallet from keys]({{site.baseurl}}/resources/user-guides/restore_from_keys.html)
+[How to connect to a remote node within GUI wallet]({{site.baseurl}}/resources/user-guides/remote_node_gui.html)
+[CLI wallet/daemon isolation with Qubes + Whonix]({{site.baseurl}}/resources/user-guides/cli_wallet_daemon_isolation_qubes_whonix.html)
+
+</div>
+ </div>
+ </div>
+ </div>
+</section>
+
+<section class="container">
+ <div class="row">
+ <div class="left half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Recovery</h2>
+ </div>
+ </div>
+<div class="row start-xs" markdown="1">
+
+[How to fix locked up funds]({{site.baseurl}}/resources/user-guides/howto_fix_stuck_funds.html)
+[How to restore your account]({{site.baseurl}}/resources/user-guides/restore_account.html)
+
+</div>
+ </div>
+ </div>
+ <div class="right half col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Mining</h2>
+ </div>
+ </div>
+<div class="row start-xs" markdown="1">
+
+[How to solo mine with the GUI]({{site.baseurl}}/resources/user-guides/solo_mine_GUI.html)
+[How to mine on a pool with xmr-stak-cpu]({{site.baseurl}}/resources/user-guides/mine-to-pool.html)
+[Mining with Docker and XMRig]({{site.baseurl}}/resources/user-guides/mining_with_xmrig_and_docker.html)
+
+</div>
+ </div>
+ </div>
+ </div>
+
+
+
+</section>
+</div>
diff --git a/_i18n/en/resources/user-guides/mine-to-pool.md b/_i18n/en/resources/user-guides/mine-to-pool.md
new file mode 100644
index 0000000000000000000000000000000000000000..d59f4f3a65baa11fa3cc3bc6b0335291cf0cf883
--- /dev/null
+++ b/_i18n/en/resources/user-guides/mine-to-pool.md
@@ -0,0 +1,113 @@
+# Selecting a pool
+
+There are many pools to choose from, a list is available at
+[moneropools.com](https://moneropools.com). Mining on a larger pool could mean
+more frequent payouts, but mining on a smaller pool helps to keep the network
+decentralized.
+
+# Selecting a CPU miner
+
+Just like pools, there are a lot of miners to choose from. The one that you
+should pick depends on the hardware you want to mine on. This guide will only
+use a CPU miner, and will be using
+[xmr-stak-cpu](https://github.com/fireice-uk/xmr-stak-cpu). Alternatives include
+[wolf's CPUMiner](https://github.com/wolf9466/cpuminer-multi) and
+[sgminer-gm](https://github.com/genesismining/sgminer-gm). However, their
+configuration is slightly different and will not be covered in this guide.
+
+## For Windows Systems
+
+If you are using a Windows system, the developer of xmr-stak-cpu provides
+binaries to download on the
+[GitHub release page](https://github.com/fireice-uk/xmr-stak-cpu/releases).
+
+Download `xmr-stak-cpu-win64.zip` and extract it somewhere you'll be able to
+find it again.
+
+## For Other Operating Systems
+
+If you're not using Windows, you will have to compile xmr-stak-cpu for yourself,
+luckily this isn't as hard as it sounds. Before you can compile the miner, you
+will need to install some of its prerequisites.
+
+For Debian-based distros:
+
+ sudo apt-get install libmicrohttpd-dev libssl-dev cmake build-essential
+
+For Red Hat based distros:
+
+ sudo yum install openssl-devel cmake gcc-c++ libmicrohttpd-devel
+
+<!-- TODO: Add dependencies for other operating systems? -->
+
+Following this, you just need to use cmake to generate the build files, run
+make and copy the config file:
+
+ mkdir build-$(gcc -dumpmachine)
+ cd $_
+ cmake ../
+ make -j$(nproc)
+ cp ../config.txt bin/
+ cd bin
+
+Don't celebrate just yet, as the miner needs to be configured. Running the miner
+now should give you a block of text to copy and paste:
+
+
+
+Open `config.txt` and *replace* the two `"cpu_threads_conf"` lines with the text
+you just copied. It should look something like this afterwards:
+
+
+
+Scroll down in the file until you see the lines containing `"pool_address"`.
+*Replace* the contents of the second set of quotes with the address and port of
+the pool you chose earlier. You can find this information on the pool's website.
+
+Put your wallet address between the quotes on the wallet address. You may leave
+the password blank unless the pool specifies otherwise.
+
+After this, your config should look something like this:
+
+
+
+# Running the miner
+
+**Save the config** file and run the miner!
+
+
+
+Some pools allow you to monitor your hashrate by pasting your address into their
+website. You can also monitor your hashrate by pressing the `h` key.
+
+# Tuning the miner
+
+You might see nasty messages like this:
+
+ [2017-07-09 12:04:02] : MEMORY ALLOC FAILED: mmap failed
+
+This means that you can get around a 20% hashrate boost by enabling large pages.
+
+## Large pages on Linux
+
+Firstly stop the miner (if it's running), run the following commands to enable
+large pages and then start the miner as root:
+
+ sudo sysctl -w vm.nr_hugepages=128
+ sudo ./xmr-stak-cpu
+
+## Large pages on Windows
+
+Taken from `config.txt`:
+
+>By default we will try to allocate large pages. This means you need to "Run As Administrator" on Windows
+You need to edit your system's group policies to enable locking large pages. Here are the steps from MSDN
+1. On the Start menu, click Run. In the Open box, type gpedit.msc.
+2. On the Local Group Policy Editor console, expand Computer Configuration, and then expand Windows Settings.
+3. Expand Security Settings, and then expand Local Policies.
+4. Select the User Rights Assignment folder.
+5. The policies will be displayed in the details pane.
+6. In the pane, double-click Lock pages in memory.
+7. In the Local Security Setting – Lock pages in memory dialog box, click Add User or Group.
+8. In the Select Users, Service Accounts, or Groups dialog box, add an account that you will run the miner on
+9. Reboot for change to take effect.
diff --git a/_i18n/en/resources/user-guides/mining_with_xmrig_and_docker.md b/_i18n/en/resources/user-guides/mining_with_xmrig_and_docker.md
new file mode 100644
index 0000000000000000000000000000000000000000..840dcabd3aa74c50e53afb40f0b9a8852eea20ea
--- /dev/null
+++ b/_i18n/en/resources/user-guides/mining_with_xmrig_and_docker.md
@@ -0,0 +1,36 @@
+## Introduction
+
+This guide is two fold, ease of use for mining on Linux distributions and some extra security around mining as most of these miners have not had security auditing.
+
+At the end of this guide you will be able to sleep a little easier knowing that if the miner gets exploited it will not migrate to your OS.
+
+### Why Docker
+
+[Docker](https://www.docker.com/) is being used as it is the most well known and has the biggest chance to be already installed.
+
+The container I an using is [alpine-xmrig](https://hub.docker.com/r/bitnn/alpine-xmrig/) as per the name it is built on the [Alpine Linux](https://www.alpinelinux.org/) image.
+
+If you are interested in getting started with Docker, here are some really good starting references.
+* Arch Linux Wiki [Docker Page](https://wiki.archlinux.org/index.php/Docker)
+* Container Solutions [Security Cheat Sheet](http://container-solutions.com/content/uploads/2015/06/15.06.15_DockerCheatSheet_A2.pdf)
+* Digital Oceans [Dockerfile Howto](https://www.digitalocean.com/community/tutorials/docker-explained-using-dockerfiles-to-automate-building-of-images).
+
+For distribution specific installation please refer to the [Docker Docs](https://docs.docker.com/engine/installation/) website.
+
+### Why XMRig
+
+[XMRig](https://github.com/xmrig/xmrig) is just a really solid miner to me. Nice output and statistics, no flashy web-ui's or dependencies. The XMRig container is only ~4MB what makes it extremely portable.
+
+#### Step 1: Mining with XMRig
+
+Run the following
+
+```bash
+# docker run --restart unless-stopped --read-only -m 50M -c 512 bitnn/alpine-xmrig -o POOL01 -o POOL02 -u WALLET -p PASSWORD -k
+# docker run --restart unless-stopped --read-only -m 50M -c 512 bitnn/alpine-xmrig -o pool.supportxmr.com:7777 -u 45CJVagd6WwQAQfAkS91EHiTyfVaJn12uM4Su8iz6S2SHZ3QthmFM9BSPHVZY388ASWx8G9Wbz4BA24RQZUpGczb35fnnJz -p docker:secret -k
+```
+
+#### Step 2: There is no Step 2
+
+You have already done everything you need to do. You are now mining in a docker container with XMRig `ctrl+c` to exit the miner or add `-d` just after `docker run` to background the miner.
+
diff --git a/_i18n/en/resources/user-guides/monero-wallet-cli.md b/_i18n/en/resources/user-guides/monero-wallet-cli.md
new file mode 100644
index 0000000000000000000000000000000000000000..64e3a0582df94e7cac4e34b4da303ee6fcc637c3
--- /dev/null
+++ b/_i18n/en/resources/user-guides/monero-wallet-cli.md
@@ -0,0 +1,145 @@
+# monero-wallet-cli
+
+`monero-wallet-cli` is the wallet software that ships with the Monero tree. It is a console program,
+and manages an account. While a bitcoin wallet manages both an account and the blockchain,
+Monero separates these: `monerod` handles the blockchain, and `monero-wallet-cli` handles the account.
+
+This guide will show how to perform various operations from the `monero-wallet-cli` UI. The guide assumes you are using the most recent version of Monero and have already created an account according to the other guides.
+
+
+## Checking your balance
+
+Since the blockchain handling and the wallet are separate programs, many uses of `monero-wallet-cli`
+need to work with the daemon. This includes looking for incoming transactions to your address.
+Once you are running both `monero-wallet-cli` and `monerod`, enter `balance`.
+
+Example:
+
+This will pull blocks from the daemon the wallet did not yet see, and update your balance
+to match. This process will normally be done in the background every minute or so. To see the
+balance without refreshing:
+
+ balance
+ Balance: 64.526198850000, unlocked balance: 44.526198850000, including unlocked dust: 0.006198850000
+
+In this example, `Balance` is your total balance. The `unlocked balance` is the amount currently available to spend. Newly received transactions require 10 confirmations on the blockchain before being unlocked. `unlocked dust` refers to very small amounts of unspent outputs that may have accumulated in your account.
+
+## Sending monero
+
+You will need the standard address you want to send to (a long string starting with '4'), and
+possibly a payment ID, if the receiving party requires one. In that latter case, that party
+may instead give you an integrated address, which is both of these packed into a single address.
+
+### Sending to a standard address:
+
+ transfer ADDRESS AMOUNT PAYMENTID
+
+Replace `ADDRESS` with the address you want to send to, `AMOUNT` with how many monero you want to send,
+and `PAYMENTID` with the payment ID you were given. Payment ID's are optional. If the receiving party doesn't need one, just
+omit it.
+
+### Sending to an integrated address:
+
+ transfer ADDRESS AMOUNT
+
+The payment ID is implicit in the integrated address in that case.
+
+### Specify the number of outputs for a transaction:
+
+ transfer MIXIN ADDRESS AMOUNT
+
+Replace `MIXIN` with the number of outputs you wish to use. **If not specified, the default is 4.** It's a good idea to use the default, but you can increase the number if you want to include more outputs. The higher the number, the larger the transaction, and higher fees are needed.
+
+
+## Receiving monero
+
+If you have your own Monero address, you just need to give your standard address to someone.
+
+You can find out your address with:
+
+ address
+
+Since Monero is anonymous, you won't see the origin address the funds you receive came from. If you
+want to know, for instance to credit a particular customer, you'll have to tell the sender to use
+a payment ID, which is an arbitrary optional tag which gets attached to a transaction. To make life
+easier, you can generate an address that already includes a random payment ID:
+
+ integrated_address
+
+This will generate a random payment ID, and give you the address that includes your own account
+and that payment ID. If you want to select a particular payment ID, you can do that too:
+
+ integrated_address 12346780abcdef00
+
+Payments made to an integrated address generated from your account will go to your account,
+with that payment id attached, so you can tell payments apart.
+
+
+## Proving to a third party you paid someone
+
+If you pay a merchant, and the merchant claims to not have received the funds, you may need
+to prove to a third party you did send the funds - or even to the merchant, if it is a honest
+mistake. Monero is private, so you can't just point to your transaction in the blockchain,
+as you can't tell who sent it, and who received it. However, by supplying the per-transaction
+private key to a party, that party can tell whether that transaction sent monero to that
+particular address. Note that storing these per-transaction keys is disabled by default, and
+you will have to enable it before sending, if you think you may need it:
+
+ set store-tx-info 1
+
+You can retrieve the tx key from an earlier transaction:
+
+ get_tx_key 1234567890123456789012345678901212345678901234567890123456789012
+
+Pass in the transaction ID you want the key for. Remember that a payment might have been
+split in more than one transaction, so you may need several keys. You can then send that key,
+or these keys, to whoever you want to provide proof of your transaction, along with the
+transaction id and the address you sent to. Note that this third party, if knowing your
+own address, will be able to see how much change was returned to you as well.
+
+If you are the third party (that is, someone wants to prove to you that they sent monero
+to an address), then you can check this way:
+
+ check_tx_key TXID TXKEY ADDRESS
+
+Replace `TXID`, `TXKEY` and `ADDRESS` with the transaction ID, per-transaction key, and destination
+address which were supplied to you, respectively. monero-wallet-cli will check that transaction
+and let you know how much monero this transaction paid to the given address.
+
+
+## Getting a chance to confirm/cancel payments
+
+If you want to get a last chance confirmation when sending a payment:
+
+ set always-confirm-transfers 1
+
+
+## How to find a payment to you
+
+If you received a payment using a particular payment ID, you can look it up:
+
+ payments PAYMENTID
+
+You can give more than one payment ID too.
+
+More generally, you can review incoming and outgoing payments:
+
+ show_transfers
+
+You can give an optional height to list only recent transactions, and request
+only incoming or outgoing transactions. For example,
+
+ show_transfers in 650000
+
+will only incoming transfers after block 650000. You can also give a height
+range.
+
+If you want to mine, you can do so from the wallet:
+
+ start_mining 2
+
+This will start mining on the daemon usin two threads. Note that this is solo mining,
+and may take a while before you find a block. To stop mining:
+
+ stop_mining
+
diff --git a/_i18n/en/resources/user-guides/monero_tools.md b/_i18n/en/resources/user-guides/monero_tools.md
new file mode 100644
index 0000000000000000000000000000000000000000..3f88806bf7834654710e08422623d22ca6d98021
--- /dev/null
+++ b/_i18n/en/resources/user-guides/monero_tools.md
@@ -0,0 +1,17 @@
+# Monero tools
+
+These tools can be used to gain information about the Monero network or your transaction data in the blockchain.
+
+### [Check that a recipient has received your funds](http://xmrtests.llcoins.net/checktx.html)
+
+### [Tools for monero address generation](https://xmr.llcoins.net/)
+
+### [Monero node count](http://moneronodes.i2p.xyz/)
+
+### [Monero node map](https://monerohash.com/nodes-distribution.html)
+
+### [Monero offline wallet generator](http://moneroaddress.org/)
+
+### [Monero network statistics](http://moneroblocks.info/stats)
+
+### [Monero.how statistics](https://www.monero.how/)
\ No newline at end of file
diff --git a/_i18n/en/resources/user-guides/png/create_wallet/1.png b/_i18n/en/resources/user-guides/png/create_wallet/1.png
new file mode 100644
index 0000000000000000000000000000000000000000..44acf51b19ea9435af2dc466ed05514b7543564d
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/create_wallet/1.png differ
diff --git a/_i18n/en/resources/user-guides/png/create_wallet/10.png b/_i18n/en/resources/user-guides/png/create_wallet/10.png
new file mode 100644
index 0000000000000000000000000000000000000000..2f248c9dda4ce97441e68d65923f4d74feb2a7c3
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/create_wallet/10.png differ
diff --git a/_i18n/en/resources/user-guides/png/create_wallet/11.png b/_i18n/en/resources/user-guides/png/create_wallet/11.png
new file mode 100644
index 0000000000000000000000000000000000000000..f8bb9989a3dfac8d717ae20c23b14aaaf987876d
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/create_wallet/11.png differ
diff --git a/_i18n/en/resources/user-guides/png/create_wallet/12.png b/_i18n/en/resources/user-guides/png/create_wallet/12.png
new file mode 100644
index 0000000000000000000000000000000000000000..2e1f69d63c25cf308989596187d55adf10fcc6d2
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/create_wallet/12.png differ
diff --git a/_i18n/en/resources/user-guides/png/create_wallet/13.png b/_i18n/en/resources/user-guides/png/create_wallet/13.png
new file mode 100644
index 0000000000000000000000000000000000000000..2db5d603ab699581e9755c369602d9088b688f53
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/create_wallet/13.png differ
diff --git a/_i18n/en/resources/user-guides/png/create_wallet/14.png b/_i18n/en/resources/user-guides/png/create_wallet/14.png
new file mode 100644
index 0000000000000000000000000000000000000000..bf2906e280f00193aef3b19f430bcac8c7cedee6
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/create_wallet/14.png differ
diff --git a/_i18n/en/resources/user-guides/png/create_wallet/15.png b/_i18n/en/resources/user-guides/png/create_wallet/15.png
new file mode 100644
index 0000000000000000000000000000000000000000..7c675edfb7b174ed45fac544d26762f822cf3881
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/create_wallet/15.png differ
diff --git a/_i18n/en/resources/user-guides/png/create_wallet/16.png b/_i18n/en/resources/user-guides/png/create_wallet/16.png
new file mode 100644
index 0000000000000000000000000000000000000000..ab23b572fa33fbf019440ba419d9adfe9f9ce9b3
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/create_wallet/16.png differ
diff --git a/_i18n/en/resources/user-guides/png/create_wallet/17.png b/_i18n/en/resources/user-guides/png/create_wallet/17.png
new file mode 100644
index 0000000000000000000000000000000000000000..97ea15bcad6ce467ba36202ebf28dd6f987a6244
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/create_wallet/17.png differ
diff --git a/_i18n/en/resources/user-guides/png/create_wallet/18.png b/_i18n/en/resources/user-guides/png/create_wallet/18.png
new file mode 100644
index 0000000000000000000000000000000000000000..20546a9ab5e547b73c0b58164537cba6e4b911d4
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/create_wallet/18.png differ
diff --git a/_i18n/en/resources/user-guides/png/create_wallet/19.png b/_i18n/en/resources/user-guides/png/create_wallet/19.png
new file mode 100644
index 0000000000000000000000000000000000000000..5a7088e259addd15157a27aa917bcaebe92e2d5d
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/create_wallet/19.png differ
diff --git a/_i18n/en/resources/user-guides/png/create_wallet/2.png b/_i18n/en/resources/user-guides/png/create_wallet/2.png
new file mode 100644
index 0000000000000000000000000000000000000000..164aa6b689364ad1ed04f2388653f0c844006649
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/create_wallet/2.png differ
diff --git a/_i18n/en/resources/user-guides/png/create_wallet/20.png b/_i18n/en/resources/user-guides/png/create_wallet/20.png
new file mode 100644
index 0000000000000000000000000000000000000000..c5169249b22e6a26c56d11a86c76e900d4ec467b
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/create_wallet/20.png differ
diff --git a/_i18n/en/resources/user-guides/png/create_wallet/21.png b/_i18n/en/resources/user-guides/png/create_wallet/21.png
new file mode 100644
index 0000000000000000000000000000000000000000..090ff767ae613d71f2cf0d7390dd204b34ec1ccf
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/create_wallet/21.png differ
diff --git a/_i18n/en/resources/user-guides/png/create_wallet/22.png b/_i18n/en/resources/user-guides/png/create_wallet/22.png
new file mode 100644
index 0000000000000000000000000000000000000000..8c7a7669afdb1b9fc670589184214fe029280f5c
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/create_wallet/22.png differ
diff --git a/_i18n/en/resources/user-guides/png/create_wallet/23.png b/_i18n/en/resources/user-guides/png/create_wallet/23.png
new file mode 100644
index 0000000000000000000000000000000000000000..e2dfc0c4ed20d73ba9341b83195020068716a5c8
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/create_wallet/23.png differ
diff --git a/_i18n/en/resources/user-guides/png/create_wallet/3.png b/_i18n/en/resources/user-guides/png/create_wallet/3.png
new file mode 100644
index 0000000000000000000000000000000000000000..f4f4436e27849c8c3ac3025626a7d5be4a9c6667
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/create_wallet/3.png differ
diff --git a/_i18n/en/resources/user-guides/png/create_wallet/4.png b/_i18n/en/resources/user-guides/png/create_wallet/4.png
new file mode 100644
index 0000000000000000000000000000000000000000..36be1be0518f8d1aee145740d4928092690ae9c9
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/create_wallet/4.png differ
diff --git a/_i18n/en/resources/user-guides/png/create_wallet/5.png b/_i18n/en/resources/user-guides/png/create_wallet/5.png
new file mode 100644
index 0000000000000000000000000000000000000000..56c6733aabd3ea7a213e4b16bb3b3244631b82a5
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/create_wallet/5.png differ
diff --git a/_i18n/en/resources/user-guides/png/create_wallet/6.png b/_i18n/en/resources/user-guides/png/create_wallet/6.png
new file mode 100644
index 0000000000000000000000000000000000000000..8e0d7950fb9225541f455a24330a36ff7357f252
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/create_wallet/6.png differ
diff --git a/_i18n/en/resources/user-guides/png/create_wallet/7.png b/_i18n/en/resources/user-guides/png/create_wallet/7.png
new file mode 100644
index 0000000000000000000000000000000000000000..c18527827bd6dcfdf4257fcb46c82e754f61121b
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/create_wallet/7.png differ
diff --git a/_i18n/en/resources/user-guides/png/create_wallet/8.png b/_i18n/en/resources/user-guides/png/create_wallet/8.png
new file mode 100644
index 0000000000000000000000000000000000000000..ce02508b7d912855670066aec22ebef824b0d986
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/create_wallet/8.png differ
diff --git a/_i18n/en/resources/user-guides/png/create_wallet/9.png b/_i18n/en/resources/user-guides/png/create_wallet/9.png
new file mode 100644
index 0000000000000000000000000000000000000000..cac31479b11bbad5907d984c8e81bdf50fcb2a8d
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/create_wallet/9.png differ
diff --git a/_i18n/en/resources/user-guides/png/easiest_way/01.png b/_i18n/en/resources/user-guides/png/easiest_way/01.png
new file mode 100644
index 0000000000000000000000000000000000000000..17c55b2d6a024f3245055975b654681265812d2d
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/easiest_way/01.png differ
diff --git a/_i18n/en/resources/user-guides/png/easiest_way/02.png b/_i18n/en/resources/user-guides/png/easiest_way/02.png
new file mode 100644
index 0000000000000000000000000000000000000000..91e1bfd16f7843310fc59c84c4aff2e03aa13181
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/easiest_way/02.png differ
diff --git a/_i18n/en/resources/user-guides/png/easiest_way/03.png b/_i18n/en/resources/user-guides/png/easiest_way/03.png
new file mode 100644
index 0000000000000000000000000000000000000000..dded71ade21780fe14fd63fb7aab11bddcd635b1
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/easiest_way/03.png differ
diff --git a/_i18n/en/resources/user-guides/png/easiest_way/04.png b/_i18n/en/resources/user-guides/png/easiest_way/04.png
new file mode 100644
index 0000000000000000000000000000000000000000..e657d4315e459c4b18648d417c539193fce5376d
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/easiest_way/04.png differ
diff --git a/_i18n/en/resources/user-guides/png/easiest_way/05.png b/_i18n/en/resources/user-guides/png/easiest_way/05.png
new file mode 100644
index 0000000000000000000000000000000000000000..00d2b26a05fb2fae413d4853c1f9e5159428d1c6
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/easiest_way/05.png differ
diff --git a/_i18n/en/resources/user-guides/png/easiest_way/06.png b/_i18n/en/resources/user-guides/png/easiest_way/06.png
new file mode 100644
index 0000000000000000000000000000000000000000..4d55286ce0e83da7051dc8070847a729f04c72fe
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/easiest_way/06.png differ
diff --git a/_i18n/en/resources/user-guides/png/easiest_way/07.png b/_i18n/en/resources/user-guides/png/easiest_way/07.png
new file mode 100644
index 0000000000000000000000000000000000000000..715245b2239d4ed7882c0c6e933cc13aa9173e82
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/easiest_way/07.png differ
diff --git a/_i18n/en/resources/user-guides/png/easiest_way/08.png b/_i18n/en/resources/user-guides/png/easiest_way/08.png
new file mode 100644
index 0000000000000000000000000000000000000000..bfc459a89582d8791f3cd2b1b1a013e2004e638a
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/easiest_way/08.png differ
diff --git a/_i18n/en/resources/user-guides/png/easiest_way/09.png b/_i18n/en/resources/user-guides/png/easiest_way/09.png
new file mode 100644
index 0000000000000000000000000000000000000000..e632bbb82e533b6fb205baf4edd5b86f153a9229
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/easiest_way/09.png differ
diff --git a/_i18n/en/resources/user-guides/png/easiest_way/10.png b/_i18n/en/resources/user-guides/png/easiest_way/10.png
new file mode 100644
index 0000000000000000000000000000000000000000..3a9337336bf1c34e7980da562a63f987d4781232
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/easiest_way/10.png differ
diff --git a/_i18n/en/resources/user-guides/png/easiest_way/11.png b/_i18n/en/resources/user-guides/png/easiest_way/11.png
new file mode 100644
index 0000000000000000000000000000000000000000..eaa4a5b989cc6463a29285bae4d0e7688b595ce4
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/easiest_way/11.png differ
diff --git a/_i18n/en/resources/user-guides/png/easiest_way/12.png b/_i18n/en/resources/user-guides/png/easiest_way/12.png
new file mode 100644
index 0000000000000000000000000000000000000000..e38159ec6fa34c74408f27ee6b5792f337bfacb2
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/easiest_way/12.png differ
diff --git a/_i18n/en/resources/user-guides/png/easiest_way/13.png b/_i18n/en/resources/user-guides/png/easiest_way/13.png
new file mode 100644
index 0000000000000000000000000000000000000000..ed3b707d01f87f3376b134ede6477b01b684bac3
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/easiest_way/13.png differ
diff --git a/_i18n/en/resources/user-guides/png/mine_to_pool/1.png b/_i18n/en/resources/user-guides/png/mine_to_pool/1.png
new file mode 100644
index 0000000000000000000000000000000000000000..a6e7652877110b793894d9ae627c7466a56b7b0c
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/mine_to_pool/1.png differ
diff --git a/_i18n/en/resources/user-guides/png/mine_to_pool/2.png b/_i18n/en/resources/user-guides/png/mine_to_pool/2.png
new file mode 100644
index 0000000000000000000000000000000000000000..83a7dd163530cfe1a9d5c9c44b4482c7cdb40458
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/mine_to_pool/2.png differ
diff --git a/_i18n/en/resources/user-guides/png/mine_to_pool/3.png b/_i18n/en/resources/user-guides/png/mine_to_pool/3.png
new file mode 100644
index 0000000000000000000000000000000000000000..70aeea2aaa91a34285fd0a0162f858a9b0bc76c6
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/mine_to_pool/3.png differ
diff --git a/_i18n/en/resources/user-guides/png/mine_to_pool/4.png b/_i18n/en/resources/user-guides/png/mine_to_pool/4.png
new file mode 100644
index 0000000000000000000000000000000000000000..13361a0e85a8b82a374917df939bb97f4529ff32
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/mine_to_pool/4.png differ
diff --git a/_i18n/en/resources/user-guides/png/remote_node/remote-node-screenshot.png b/_i18n/en/resources/user-guides/png/remote_node/remote-node-screenshot.png
new file mode 100644
index 0000000000000000000000000000000000000000..a32bf5088c040273bef87448b049c5bc112be196
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/remote_node/remote-node-screenshot.png differ
diff --git a/_i18n/en/resources/user-guides/png/solo_mine_GUI/01.PNG b/_i18n/en/resources/user-guides/png/solo_mine_GUI/01.PNG
new file mode 100644
index 0000000000000000000000000000000000000000..7ca5f7c247ee06462a549ca4a6b5c6380b9f257f
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/solo_mine_GUI/01.PNG differ
diff --git a/_i18n/en/resources/user-guides/png/solo_mine_GUI/02.PNG b/_i18n/en/resources/user-guides/png/solo_mine_GUI/02.PNG
new file mode 100644
index 0000000000000000000000000000000000000000..42a5290e0733dedb0f397e50a86215b0887039a5
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/solo_mine_GUI/02.PNG differ
diff --git a/_i18n/en/resources/user-guides/png/solo_mine_GUI/03.PNG b/_i18n/en/resources/user-guides/png/solo_mine_GUI/03.PNG
new file mode 100644
index 0000000000000000000000000000000000000000..ab7b8c2a2143d0ab46fae3294a09fe01b0bd61f4
Binary files /dev/null and b/_i18n/en/resources/user-guides/png/solo_mine_GUI/03.PNG differ
diff --git a/_i18n/en/resources/user-guides/prove-payment.md b/_i18n/en/resources/user-guides/prove-payment.md
new file mode 100644
index 0000000000000000000000000000000000000000..89a52e6b235e39bca3eec44367e03d0603a28518
--- /dev/null
+++ b/_i18n/en/resources/user-guides/prove-payment.md
@@ -0,0 +1,51 @@
+When you send money to a party who then disputes the payment was made, you need to be able to prove the payment was made.
+
+With Bitcoin, this is typically done by looking up the transaction ID, where the origin and destination addresses are
+shown, along with the amount transacted.
+
+Monero, however, is private: that information is not available publicly on the blockchain. The steps are therefore a bit
+more involved.
+
+To prove to Charlie that she made a payment to Bob, Alice must supply Charlie three pieces of information:
+
+- the transaction ID, as is done in Bitcoin
+- Bob's address, as is done with Bitcoin
+- the transaction's key, which is new with Monero and other CryptoNote currencies
+
+When Alice made the transaction, a one time key was automatically generated just for this transaction. Alice can
+query it thus in monero-wallet-cli (new name for the old simplewallet):
+
+> get_tx_key TXID
+
+Alice would plug in her actual transaction ID instead of this TXID placeholder. All being well, the one time transaction key
+will be displayed.
+
+Note that this will only work if monero-wallet-cli is set to save transaction keys. To double check:
+
+> set
+
+If it's set to 0, set it to 1:
+
+> set store-tx-info 1
+
+Alice can now send Charlie the transaction key along with transaction ID and Bob's address.
+
+Note: if several transactions were made, this needs repeating for each such transaction.
+
+
+---
+
+Charlie now received those three pieces of information, and wants to check Alice is telling the truth: on an up to date
+blockchain, Charlie types in monero-wallet-cli:
+
+> check_tx_key TXID TXKEY ADDRESS
+
+The information supplied by Alice plugs neatly instead of the placeholders. monero-wallet-cli will use the transaction
+key to decode the transaction, and display how much this particular transaction sent to this address. Obviously,
+Charlie will want to double check with Bob the address is really his - same as with Bitcoin.
+
+Alternatively, the transaction key can be obtained in the GUI in the History tab. Click on details for each individual transaction to get the key.
+
+Note: if several transactions were made, this needs repeating for each such transaction.
+
+
diff --git a/_i18n/en/resources/user-guides/remote_node_gui.md b/_i18n/en/resources/user-guides/remote_node_gui.md
new file mode 100644
index 0000000000000000000000000000000000000000..bea8f8f813dea6cce155840417d7cc254f4a0d0c
--- /dev/null
+++ b/_i18n/en/resources/user-guides/remote_node_gui.md
@@ -0,0 +1,10 @@
+## Finding a node
+First things first, you need to find a node to connect to! [moneroworld.com](https://moneroworld.com/#nodes) has some great resources for finding nodes. One of the easiest methods
+would be to use a node run by moneroworld, but they have a tool for finding random nodes too.
+
+## Connecting to the node from the GUI wallet
+After you enter your password for your wallet, you will see a pop up that will give you the option to "use custom settings". Click on it. You will then be
+sent to the "Settings" page in the GUI. At this point you should see two text boxes to the right of a label that says "Daemon address". In the first box (the one to the left) you need to enter the address of the node that you want to
+connect to. This address might look like `node.moneroworld.com` or it could look like any old ip address. The smaller box to the right is where you enter the node's port. The default port is `18081` but if you are using a random node the port that is used will vary. The port for node.moneroworld.com uses 18089.
+### Your screen should look a bit like this
+<img src="{{site.baseurl}}/resources/user-guides/png/remote_node/remote-node-screenshot.png" width="600">
diff --git a/_i18n/en/resources/user-guides/restore_account.md b/_i18n/en/resources/user-guides/restore_account.md
new file mode 100644
index 0000000000000000000000000000000000000000..caa36ca8aac09bf90f824af70b6b382ccd1b7101
--- /dev/null
+++ b/_i18n/en/resources/user-guides/restore_account.md
@@ -0,0 +1,22 @@
+## Operating Systems: Windows, Linux, Mac
+
+### Account Software: monero-wallet-cli
+
+- Retrieve your 25 word @mnemonic-seed that you saved when creating your old Monero @wallet
+
+- Open a command prompt and navigate to the drive and directory that contains monero-wallet-cli
+
+- At the command prompt type: `monero-wallet-cli --restore-deterministic-wallet`
+
+- Once you press enter you will be prompted for a wallet file name. Give your wallet a new name, any name will do
+
+- Press enter again and you will be prompted for a password. Give your wallet a new and long password
+
+- Press enter again you will be prompted to repeat the password
+
+- Press enter again and you will be prompted for the 25 word electrum style mnemonic seed that you retrieved earlier
+
+- You will then be prompted with "Restore from specific blockchain height (optional, default 0):" Default will start the restore process from the beginning of the Monero blockchain. If you don't know the specific blockchain height, just hit enter. (Specifying a specific blockchain height will start the restore process from that specific height. This will save a bit of time in scanning, if you know what starting blockchain height your initial funds were transacted for this specific account.)
+
+After you have entered the 25 word mnemonic seed and have chosen your specific blockchain height, monero-wallet-cli will generate the same public address and view key as your old wallet and begin the refresh process automatically. (Please be patient as the refresh process may take a while.)
+
diff --git a/_i18n/en/resources/user-guides/restore_from_keys.md b/_i18n/en/resources/user-guides/restore_from_keys.md
new file mode 100644
index 0000000000000000000000000000000000000000..99917f88776f6088425e489ca217c5cbb72d0efe
--- /dev/null
+++ b/_i18n/en/resources/user-guides/restore_from_keys.md
@@ -0,0 +1,18 @@
+Restoring a wallet from private keys (via the command line) is pretty simple. If you have the necessary information, with this guide you can completely restore your wallet. Note: you do NOT have to have your password to restore from keys.
+
+You need to have 3 pieces of data from your wallet, or your .keys file which holds this info and the password to decrypt it. The 3 wallet components that you need are:
+
+1. **Address**
+2. **Secret Spendkey**
+3. **Secret Viewkey**
+
+
+Then run the wallet command:
+
+`./monero-wallet-cli --generate-from-keys New_Wallet_Name.abc`
+
+Next, you'll be asked for the Address, the spendkey, the viewkey, and finally the new password for the re-generated wallet.
+
+Running this with the correct parameters will re-generate your wallet files for you and allow you to set a new password.
+
+If you run into any trouble, running `./monero-wallet-cli --help` will show you the options available to you at wallet startup. Once you're inside your wallet, running the `help` command will list the help for the commands available to you within the wallet.
diff --git a/_i18n/en/resources/user-guides/securely_purchase.md b/_i18n/en/resources/user-guides/securely_purchase.md
new file mode 100644
index 0000000000000000000000000000000000000000..eb0de22a849d8a077986ab25b497cf01d8b7dab7
--- /dev/null
+++ b/_i18n/en/resources/user-guides/securely_purchase.md
@@ -0,0 +1,81 @@
+## How to purchase Monero and securely store it.
+
+This is a guide to purchase and securely store Monero as of June 2017.
+
+#### Step 1: Buy Bitcoin
+
+There are many ways to buy Bitcoin. Two semi-reliable companies at this time are Xapo <http://www.xapo.com/> and Coinbase <http://www.coinbase.com/>. The process will involve uploading your personal identification (State ID, Passport, etc.) and will take anywhere from 2 to 10 days (or longer). Verify their reputation on Reddit before making a large purchase. Xapo uses Wire Transfer and Coinbase uses Bank Transfer (ACH in the USA). Xapo should be faster than Coinbase. Coinbase also allows small "instant" buys via a debit card but adds a large fee for this option. Once you have purchased Bitcoin, you are ready to convert it to Monero!
+
+#### Step 2: Download and create a Paper Wallet on a secure and air-gapped computer.
+
+Download the paper wallet generator at: https://moneroaddress.org and copy it to a USB stick (Direct link: https://github.com/moneromooo-monero/monero-wallet-generator/archive/master.zip).
+
+Unzip and open the paper wallet generator (monero-wallet-generator.html) into a web browser on an air-gapped computer that hasn't been used before, or has had a clean installation of the OS.
+
+Your paper wallet will have four important items:
+
+Monero Public Address
+The public address is used to receive funds to the wallet. You give this to anyone who will be sending funds to your wallet.
+
+Monero Mnemonic Seed
+The mnemonic seed is a method of storing the entire wallet that is easily recognizable to humans. This is all you need to restore your wallet at a later date.
+
+Monero Private Spend Key
+The private spend key is used to send funds from the wallet.
+
+Monero Private View Key
+The private view key is to view transactions entering the wallet. Commonly this is used to setup a view-only wallet which can see incoming transactions live on the blockchain as they are sent to a cold storage wallet.
+
+At this point you have many options. You can print the wallet on paper, save it as a PDF or text on a USB stick, burn it to CD/DVD, etc. Most likely you will want at least two or three copies, stored securely in different locations. If storing digitally, encrypt everything with a strong password. If storing on paper, do not show the wallet to anyone else who can memorize your 25 word key, or take a picture of the wallet without your permission. Sending someone a picture of the wallet is the same as giving away all of your funds.
+
+Whichever method you chose, be sure there's no copy of the Monero wallet left over on the device you used. You may need to securely delete the Monero wallet if you saved it to a disk, or make sure your printer does not save a copy in memory.
+
+*If you lose access to your Monero paper wallet the Monero will not be available to you or anyone else, ever. You wont be able to recover them!
+
+#### Side Note
+Option to encrypt an XMR mnemonic seed:
+https://xmr.llcoins.net/
+Download the html page and place it on your airgapped computer. Check the part "Encrypt/Decrypt Mnemonic Seed" and make sure you use "CN Add" with a decent password. Thanks manicminer5.
+
+
+
+#### Step 3: Convert your Bitcoin to Monero and have it sent to your Monero Paper Wallet
+
+Switch to your internet connected computer and go to www.shapeshift.io. Choose "Deposit Bitcoin" and "Receive Monero" (quick).
+
+Press Continue.
+
+Your Monero Address (the Monero Public Address on your Monero Paper Wallet)
+Paste the Monero Public address from your paper wallet where it says "Your Monero Address". But wait, since your Monero Public Address is on an airgapped computer (right?), you can't copy and paste anything... Copy it over by hand, or get a blank USB drive and copy only the Public Address to it.
+
+Refund Address (Bitcoin Public Address you can receive funds at)
+Enter a Bitcoin address that you control where a refund can be sent in case there's a problem with the transaction. It's very important that you enter a Bitcoin Public Address you control or can receive funds at. At Xapo and Coinbase this is called a Receive Address and it may change periodically.
+
+Payment ID
+Leave Payment ID blank if you are sending to your own Monero wallet or Monero paper wallet.
+
+Agree to the Terms and hit the slider to make this a "Reusable Address".
+
+Press "Start Transaction".
+
+Deposit Address (Shapeshift.io's Public Bitcoin Address created only to receive your funds)
+In the new screen that pops up, copy the Deposit Address into your clipboard (select and hit ctrl+c or edit-copy). You will send Bitcoin from Xapo/Coinbase to Shapeshift.io via this address.
+
+Go to your Xapo or Circle account, and find a Transfer or Send button. Paste the Bitcoin Deposit address into the Destination field and enter the amount of bitcoin you would like to have converted to Monero. It must be within the Deposit Min and Deposit Max range specified by Shapeshift.io. Press Send and authorize the transaction, if required.
+
+Once the send has been initiated by Xapo/Coinbase there will be a delay while the transaction enters the Bitcoin blockchain and awaits confirmation. This may be minutes or hours. You can check if the payment has been sent by looking up the Shapeshift.io Deposit address at blockchain.info. Your transaction to Shapeshift.io will show up there.
+
+When your Bitcoin transaction has been confirmed, Shapeshift.io will then begin exchanging Bitcoin (BTC) for Monero (XMR) at one of the exchanges and when it's complete, send the Monero to the address of your Cold Storage Paper Wallet! This can take minutes to hours. If there's an issue, contact Shapeshift.io. They have good support.
+
+When the Shapehift.io webpage says your transaction has been completed, you should now have Monero in your Paper Wallet!
+
+
+#### Notes and How to Verify Funds
+Because the Monero blockchain is private and untraceable, you won't be able to lookup your Monero Public Address and confirm that the funds have arrived like you might with Bitcoin. This is good for privacy, but bad for convenience.
+
+To securely verify the funds have arrived at your wallet, you will need to setup a View Only wallet. This is where that view-key comes in. To create a view-only wallet see the entry: [View Only Wallets]({{site.baseurl}}/resources/user-guides/view_only.html)
+
+To verify the funds are *still in* your wallet and have not been spent you need to create a Cold Wallet with your mnemonic key (all your funds) on an airgapped computer with an up-to-date copy of the Monero Blockchain. When finished you will have to securely erase the wallet or connect it to the internet and it becomes a Hot Wallet.
+
+
+
diff --git a/_i18n/en/resources/user-guides/solo_mine_GUI.md b/_i18n/en/resources/user-guides/solo_mine_GUI.md
new file mode 100644
index 0000000000000000000000000000000000000000..dc637fe80462eff52353125b752e1b1cb3288af1
--- /dev/null
+++ b/_i18n/en/resources/user-guides/solo_mine_GUI.md
@@ -0,0 +1,15 @@
+It is very easy to solo mine with the official GUI. If you have not done so already, go to the <a href="{{site.baseurl}}/downloads/">Monero downloads page</a> and download the official GUI for your operating system. Then, run the setup and be patient as Monero synchronizes with the network. You should see that it displays "Connected" in the lower left corner.
+
+<img src="/resources/user-guides/png/solo_mine_GUI/01.PNG" style="width: 600px;"/>
+
+Click on the "Advanced" tab. You should see that several other options appear. Now click on the "Mining" sub-tab.
+
+<img src="/resources/user-guides/png/solo_mine_GUI/02.PNG" style="width: 600px;"/>
+
+You should now have an option to start mining. You can optionally change the number of threads to mine with. For optimal efficiency, you should mine with your CPU's cache divided by 2. You will need to look up your CPU's specs on the manufacturer's website. If you are unsure, leave the number of threads at 1. Click the "Start mining" button.
+
+<img src="/resources/user-guides/png/solo_mine_GUI/03.PNG" style="width: 600px;"/>
+
+You are now mining with the network, as you can see on the bottom of the image. In this example, the computer is contributing 23 H/s to the Monero network. Mining helps keep the network secure, and you may get lucky and receive a reward for protecting the network.
+
+To stop mining, simply click the "Stop mining" button.
diff --git a/_i18n/en/resources/user-guides/view_only.md b/_i18n/en/resources/user-guides/view_only.md
new file mode 100644
index 0000000000000000000000000000000000000000..18839c4c4d90802c3cad14e921af6cec9813f13b
--- /dev/null
+++ b/_i18n/en/resources/user-guides/view_only.md
@@ -0,0 +1,12 @@
+A view-only wallet can only see which incoming transactions belong to you. It can not spend any of your Monero, in fact it can't even see outgoing transactions from this wallet. This makes view-only wallets particularly interesting for
+
+* Developers writing libraries to validate payments
+* End users validating incoming transactions to cold wallets
+
+### Creating A View-Only Wallet
+
+You can create a view-only wallet from any existing wallet.
+
+Open an existing wallet or create a new one using `monero-wallet-cli`. In the wallet, type `address` and `viewkey` to display the wallet's address and secret viewkey. Type `exit` to close the wallet.
+
+Next, create your view-only wallet by typing `monero-wallet-cli --generate-from-view-key wallet-name`. The last argument will be your new wallet's file name. You will be prompted for `Standard address` and `View key` by the wallet. Paste in your original wallet's address and secret view key. Next, enter and confirm a password for your new wallet and you're done.
diff --git a/_i18n/en/resources/user-guides/vps_run_node.md b/_i18n/en/resources/user-guides/vps_run_node.md
new file mode 100644
index 0000000000000000000000000000000000000000..1910e06f55b6cae01c969a31714c6af44b5014da
--- /dev/null
+++ b/_i18n/en/resources/user-guides/vps_run_node.md
@@ -0,0 +1,47 @@
+# monerod
+
+`monerod` is the daemon software that ships with the Monero tree. It is a console program, and manages the blockchain. While a bitcoin wallet manages both an account and the blockchain, Monero separates these: `monerod` handles the blockchain, and `monero-wallet-cli` handles the account.
+
+This guide assumes you have already set up your VPS account and are using SSH to tunnel into the server console.
+
+## Linux, 64-bit (Ubuntu 16.04 LTS)
+
+### Make sure that port 18080 is open
+`monerod` uses this port to communicate with other nodes on the Monero network.
+
+Example if using `ufw`: `sudo ufw allow 18080`
+Example if using `iptables`: `sudo iptables -A INPUT -p tcp --dport 18080 -j ACCEPT`
+
+### Download the current Monero Core binaries
+
+ wget https://downloads.getmonero.org/linux64
+
+### Make a directory and extract the files.
+
+ mkdir monero
+ tar -xjvf linux64 -C monero
+
+### Launch the daemon
+
+ cd monero
+ ./monerod
+
+### Options:
+
+Show list of all options and settings:
+
+ ./monerod --help
+
+Launch the daemon as a background process:
+
+ ./monerod --detach
+
+Monitor the output of `monerod` if running as daemon:
+
+ tail -f ~/.bitmonero/bitmonero.log
+
+Keep the VPS secure with autoupdate:
+
+https://help.ubuntu.com/community/AutomaticSecurityUpdates
+
+
diff --git a/_i18n/en/technical-specs.md b/_i18n/en/technical-specs.md
new file mode 100644
index 0000000000000000000000000000000000000000..bc87f7c6789e2816fbe61cbe90d956320a0479cc
--- /dev/null
+++ b/_i18n/en/technical-specs.md
@@ -0,0 +1,132 @@
+<div class="about-monero">
+ <section class="container">
+ <div class="row">
+ <!-- left two-thirds block-->
+ <div class="full col-xs-12">
+ <div class="info-block text-adapt">
+
+ <div class="row">
+ <div class="col">
+ <h3>No premine, no instamine, no token</h3>
+ </div>
+ </div>
+
+<div markdown="1">
+* Monero had no premine or instamine
+* Monero did not sell any token
+* Monero had no presale of any kind
+</div>
+
+ <div class="row">
+ <div class="col">
+ <h3>Proof of Work</h3>
+ </div>
+ </div>
+
+<div markdown="1">
+* CryptoNight
+* may change in the future
+</div>
+
+ <div class="row">
+ <div class="col">
+ <h3>Difficulty retarget</h3>
+ </div>
+ </div>
+
+<div markdown="1">
+* every block
+* based on the last 720 blocks, excluding 20% of the timestamp outliers
+</div>
+
+ <div class="row">
+ <div class="col">
+ <h3>Block time</h3>
+ </div>
+ </div>
+
+<div markdown="1">
+* 2 minutes
+* may change in the future as long as emission curve is preserved
+</div>
+
+ <div class="row">
+ <div class="col">
+ <h3>Block reward</h3>
+ </div>
+ </div>
+
+<div markdown="1">
+* smoothly decreasing and subject to penalties for blocks greater than median size of the last 100 blocks (M100)
+* see the [latest block](https://moneroblocks.info/) coinbase transaction amount for current reward
+</div>
+
+ <div class="row">
+ <div class="col">
+ <h3>Block size</h3>
+ </div>
+ </div>
+
+<div markdown="1">
+* dynamic, maximum of 2 * M100
+</div>
+
+ <div class="row">
+ <div class="col">
+ <h3>Emission curve</h3>
+ </div>
+ </div>
+
+<div markdown="1">
+* first, main curve: ~18.132 million coins by the end of May 2022
+* then, tail curve: 0.6 XMR per 2-minute block, kicks in once main emission is done, translates to <1% inflation decreasing over time
+* see [charts and details](https://www.reddit.com/r/Monero/comments/512kwh/useful_for_learning_about_monero_coin_emission/)
+</div>
+
+ <div class="row">
+ <div class="col">
+ <h3>Max supply</h3>
+ </div>
+ </div>
+
+<div markdown="1">
+* infinite
+</div>
+
+ <div class="row">
+ <div class="col">
+ <h3>Sender privacy</h3>
+ </div>
+ </div>
+
+<div markdown="1">
+* Ring signatures
+</div>
+
+ <div class="row">
+ <div class="col">
+ <h3>Recipient privacy</h3>
+ </div>
+ </div>
+
+<div markdown="1">
+* Stealth addresses
+</div>
+
+ <div class="row">
+ <div class="col">
+ <h3>Amount obfuscation</h3>
+ </div>
+ </div>
+
+<div markdown="1">
+* Ring confidential transactions
+</div>
+
+ </div>
+ </div>
+ <!-- end right one-third block-->
+ </div>
+
+ </section>
+</div>
diff --git a/_i18n/en/the-monero-project.md b/_i18n/en/the-monero-project.md
new file mode 100644
index 0000000000000000000000000000000000000000..e3fb357d8a53546c3ba7cc952d384ea0a836733c
--- /dev/null
+++ b/_i18n/en/the-monero-project.md
@@ -0,0 +1,44 @@
+<div class="site-wrap">
+<section class="container">
+ <div class="row">
+ <div class="left half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Kovri</h2>
+ </div>
+ </div>
+<div class="row start-xs monero-project" markdown="1">
+
+The Kovri project uses end-to-end encryption so that neither the sender nor receiver of a Monero transaction need to reveal their IP address to the other side or to third-party observers (the blockchain). This is done using the same technology that powers the dark net, i2p (Invisible Internet Protocol). The project is currently in heavy, active development and is not yet integrated with Monero.
+
+</div>
+ <div class="row center-xs">
+ <p><a href="https://www.getkovri.org" class="btn-link btn-fixed">Visit Kovri Website</a></p>
+ </div>
+ </div>
+ </div>
+ <div class="right half col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Open Alias</h2>
+ </div>
+ </div>
+<div class="row start-xs monero-project" markdown="1">
+
+The OpenAlias project simplifies cryptocurrency payments by providing FQDNs (Fully Qualified Domain Names, i.e. example.openalias.org) for Monero wallet addresses in a way that ensures everyone's privacy is secure. The project is well underway and has already been implemented in many Monero wallets.
+
+
+
+</div>
+
+ <div class="row center-xs">
+ <p><a href="https://www.openalias.org" class="btn-link btn-fixed">Visit OpenAlias Website</a></p>
+ </div>
+
+ </div>
+ </div>
+ </div>
+</section>
+</div>
\ No newline at end of file
diff --git a/_i18n/es.yml b/_i18n/es.yml
new file mode 100644
index 0000000000000000000000000000000000000000..64f18818a2e1fbc8c9401cc19d2ab868a042b877
--- /dev/null
+++ b/_i18n/es.yml
@@ -0,0 +1,96 @@
+langs:
+ en: English
+ es: Español
+
+global:
+ date: '%Y/%m/%d'
+ monero: Monero
+ getting_started: Getting Started
+ copyright: Copyright
+ monero_project: The Monero Project
+ sitename: getmonero.org, The Monero Project
+ wiki: Moneropedia
+ tags: Articles By Tag
+ wikimeta: on Moneropedia, the open encyclopedia of Monero knowledge
+ tagsmeta: All Monero blog articles that are tagged
+ titlemeta: on the home of Monero, a digital currency that is secure, private, and untraceable
+ terms: Terms
+ privacy: Privacy
+ copyright: Copyright
+ edit: Edit This Page
+ untranslated: Esta pagina is not yet translated. If you would like to help translate it, please see the
+titles:
+ index: Inicio
+ whatismonero: ¿Qué es Monero (XMR)?
+ using: Usar Monero
+ accepting: Aceptar Monero
+ contributing: Mejorar Monero
+ mining: Minar Monero
+ faq: FAQ
+ downloads: Descargas
+ allposts: All Blog Posts
+ team: Equipo
+ hangouts: Canales de comunicación
+ events: Eventos
+ sponsorships: Patrocinios
+ merchants: Comerciantes y Servicios
+ about: Sobre Monero
+ roadmap: Hoja de ruta
+ researchlab: Laboratorio de investigación de Monero (MRL)
+ moneropedia: Moneropedia
+ userguides: GuÃas de usuario
+ developerguides: GuÃas de desarrolladores
+ technicalspecs: Especificaciones técnicas
+ themoneroproject: The Monero Project
+ presskit: Monero Press Kit
+ legal: Legal
+ ffs: Forum Funding System
+ ffs-cp: Completed Proposals
+ ffs-fr: Funding Required
+ ffs-ideas: Ideas
+ ffs-ot: Open Tasks
+ ffs-wip: Work in Progress
+ blogbytag: Blog by Tag
+index:
+ page_title: "Monero - secure, private, untraceable"
+ what_is_1: What is
+ what_is_2: " ?"
+ what_is_orange_block: "Monero is a secure, private, untraceable currency that is open-source and freely available for anyone to use."
+ what_is_text_block_1: "With Monero, you are your own bank; You have complete control over your funds. With Monero, your accounts and transactions are kept private."
+ what_is_text_block_2: "Want to find out more? An overview of Monero's main features are below. If you'd like to try Monero for yourself the"
+ what_is_text_block_3: "Getting Started"
+ what_is_text_block_4: "section is an excellent launching point."
+ news: News
+ the_latest: The Latest
+ private: Private
+ secure: Secure
+ untraceable: Untraceable
+ private_text: "Monero uses hidden amounts, origins and destinations of @transactions. This means that nobody knows how much you're sending in a transaction except you. This ensures that your purchases and other transfers remain private by default."
+ untraceable_text: "By taking advantage of @ring-signatures, Monero allows you to send and receive funds privately. Even though your transactions are publicly verifiable on the @blockchain, transactions use digital signatures that specify a group of signers such that the person verifying can’t tell which person actually produced the signature. Because it's ambiguous which funds have been spent, your transaction remains private and cannot be traced back to you."
+ secure_text: "Monero uses a distributed peer-to-peer @consensus network and every transaction is cryptographically signed. Your coins are safely stored on the @blockchain and can be restored at any time with the use of a 25 word @mnemonic-seed on any computer with the Monero software. Wallet files are encrypted on disk and locked with a passphrase, rendering them useless if stolen."
+ how_do_i_1: "How do I "
+ how_do_i_2: " ?"
+ get_started: get started
+ get_started_1: "The fastest way to start using Monero is with a web @account manager such as "
+ mymonero: "MyMonero"
+ get_started_2: "."
+ get_started_3: "Alternatively, if you would like to run a [full Monero node](/getting-started/running) you can download the client and a kick-starter @blockchain (to bring your local client up to speed) using the download link on the right."
+ where_can_i: Where can I
+ download_1: download
+ download_2: " ?"
+ different_os: "Need it for a different operating system?"
+ all_downloads: View all available downloads here
+ c_download: Download
+ monero_for: Monero for
+ latest_blockchain: Latest @Blockchain
+blog:
+ title_1: All
+ title_2: Blog
+ title_3: Posts
+ tagged: Tagged under
+ author: Posted by
+ date: Posted at
+ forum: Click here to join the discussion for this entry on the Monero Forum
+tags:
+ all: Articles by Tag
+ notags: There are no posts for this tag.
diff --git a/_i18n/es/community/events.md b/_i18n/es/community/events.md
new file mode 100644
index 0000000000000000000000000000000000000000..417d806152056646f8fcd384f1dffbf0f922efe4
--- /dev/null
+++ b/_i18n/es/community/events.md
@@ -0,0 +1,28 @@
+{% include untranslated.html %}
+<div markdown="1" class="text-center container description">
+Monero people are always down to get together and have a good time. Check below to see Monero-related events happening in your area.
+</div>
+
+{% for toplevel in site.data.events %}
+
+<div class="events">
+ <div class="container full col-xs-12">
+ <div class="info-block text-adapt">
+ <div class="row">
+ <div class="col-xs-12">
+ <h2>{{toplevel.event}}</h2>
+ <h3>Where</h3>
+ <p>{{toplevel.where}}</p>
+ <h3>When</h3>
+ <p>{{toplevel.when}}</p>
+ <h3>Description</h3>
+ <p>{{toplevel.description}}</p>
+ <h3>Link</h3>
+ <a>{{toplevel.link}}</a>
+ </div>
+ </div>
+ </div>
+ </div>
+</div>
+
+{%endfor%}
\ No newline at end of file
diff --git a/_i18n/es/community/hangouts.md b/_i18n/es/community/hangouts.md
new file mode 100644
index 0000000000000000000000000000000000000000..35e6a3f58b0bbea0670b855cbaa984d380df8111
--- /dev/null
+++ b/_i18n/es/community/hangouts.md
@@ -0,0 +1,97 @@
+{% include untranslated.html %}
+<div markdown="1" class="text-center container description">
+The Monero community is diverse and varied. We come from all over, but we definitely have some places we like to hang out together. You'll find most of them below. Join us!
+</div>
+
+<div class="hangouts">
+ <section class="container">
+ <ul class="row center-xs">
+ <li>
+ <a href="https://twitter.com/monerocurrency" target="_blank" rel="noreferrer noopener"><div class="social-icon twitter"></div></a>
+ </li>
+ <li>
+ <a href="https://reddit.com/r/monero" target="_blank" rel="noreferrer noopener"><div class="social-icon reddit"></div></a>
+ </li>
+ <li>
+ <a href="https://www.facebook.com/monerocurrency/" target="_blank" rel="noreferrer noopener"><div class="social-icon facebook"></div></a>
+ </li>
+ <li>
+ <a href="https://github.com/monero-project" target="_blank" rel="noreferrer noopener"><div class="social-icon github"></div></a>
+ </li>
+ </ul>
+ </section>
+
+ <section class="container">
+ <div class="row">
+ <!-- left two-thirds block-->
+ <div class="left two-thirds col-lg-8 col-md-8 col-sm-12 col-xs-12">
+ <div class="col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Workgroup Resources</h2>
+ </div>
+ </div>
+ <div class="row center-xs">
+ <p>In an effort to support organic workgroups, Monero has several resources that the community can use to meet and plan projects. Mattermost even has relays into the most popular Monero-related IRC channels.</p>
+ </div>
+ <div class="row relays around-xs">
+ <div class="col-md-4 col-sm-4 col-xs-4">
+ <p><a href="https://monero.slack.com/" class="btn-link btn-fixed">Slack</a></p>
+ </div>
+ <div class="col-md-4 col-sm-4 col-xs-4">
+ <p><a href="https://mattermost.getmonero.org/" class="btn-link btn-fixed">Mattermost</a></p>
+ </div>
+ <div class="col-md-4 col-sm-4 col-xs-4">
+ <p><a href="https://taiga.getmonero.org/" class="btn-link btn-fixed">Taiga</a></p>
+ </div>
+ </div>
+ </div>
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>IRC Channels</h2>
+ </div>
+ </div>
+ <div class="row start-xs">
+ <p>The Monero community utilizes a lot of IRC channels that each serve different purposes. Some to work, and some just to hang out. You'll find the more popular ones below.</p>
+ </div>
+ <div class="row irc">
+ {% for channel in site.data.irc %}
+ <div class="col-md-4 col-xs-12">
+ <a href="irc://chat.freenode.net/#{{ channel.channel }}">#{{ channel.channel }}</a>
+ <p>{{ channel.description }}</p>
+ </div>
+ {% endfor %}
+ </div>
+ </div>
+ </div>
+ </div>
+ <!-- end left two-thirds block-->
+
+ <!-- right one-third block-->
+ <div class="right one-third col-lg-4 col-md-4 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col"><h2>Stack Exchange</h2></div>
+ </div>
+ <div class="row start-xs">
+ <p>The Monero Stack Exchange is a quick and easy way to ask questions and get answers. Below you'll find some high quality question/answer pairs to some frequently asked questions.</p>
+ </div>
+ <div class="row start-xs sequestions">
+ <a href="https://monero.stackexchange.com/questions/4277/why-does-monero-have-higher-transaction-fees-than-bitcoin">Why does monero have higher transaction fees than bitcoin?</a>
+ <a href="https://monero.stackexchange.com/questions/4335/what-does-moneros-scaling-roadmap-look-like">What does Monero's scaling roadmap look like?</a>
+ <a href="https://monero.stackexchange.com/questions/4302/what-cryptography-primitives-concepts-other-than-the-basic-ones-does-monero-us">What cryptography primitives/concepts, other than the basic ones, does Monero use?</a>
+ <a href="https://monero.stackexchange.com/questions/4242/how-to-extract-data-from-local-blockchain">How to extract data from local blockchain?</a>
+ <a href="https://monero.stackexchange.com/questions/4302/what-cryptography-primitives-concepts-other-than-the-basic-ones-does-monero-us">Hiding TCP traffic for Monero miners?</a>
+ </div>
+ <div class="row center-xs">
+ <p><a href="https://monero.stackexchange.com" class="btn-link btn-auto">Visit Stack Exchange</a></p>
+ </div>
+ </div>
+ </div>
+ <!-- end right one-third block-->
+ </div>
+ </section>
+
+</div>
diff --git a/_i18n/es/community/merchants.md b/_i18n/es/community/merchants.md
new file mode 100644
index 0000000000000000000000000000000000000000..41e4816cbbe037c5768a73394d2b45dcb1a79901
--- /dev/null
+++ b/_i18n/es/community/merchants.md
@@ -0,0 +1,27 @@
+{% include untranslated.html %}
+<div markdown="1" class="text-center container description">
+Merchants of all kinds have come to value the financial privacy that Monero brings. Below is a list of the merchants that we know of that currently accept Monero for their goods and services. If a company no longer accepts Monero or you would like your business to be listed, please [open a GitHub issue and let us know](https://github.com/monero-project/monero-site/issues).
+</div>
+<div class="merchants">
+{% for toplevel in site.data.merchants %}
+<div class="container full" id="{{toplevel.id}}">
+ <div class="info-block">
+ <h2>{{toplevel.category}}</h2>
+ <div class="row">
+ {% assign sortedMerchants = toplevel.merchants | sort: 'name' %}
+ {% for merchants in sortedMerchants %}
+ <div class="col-md-4 col-sm-6 col-xs-12">
+ <a href="{{merchants.url}}">{{merchants.name}}</a>
+ </div>
+ {% endfor %}
+ </div>
+ </div>
+</div>
+{%endfor%}
+
+
+</div>
+
+<div markdown="1" class="text-center container description">
+*Please note: these links are being provided as a convenience and for informational purposes only; they do not constitute an endorsement by the Monero community of any products, services or opinions of the corporations or organizations or individuals listed. The Monero community bears no responsibility for the accuracy, legality, or content of these external sites. Contact the external site for answers to questions regarding its content. As always, caveat emptor ("buyer beware"); you are responsible for doing your own research. Always use judgement when making online purchases.*
+</div>
diff --git a/_i18n/es/community/sponsorships.md b/_i18n/es/community/sponsorships.md
new file mode 100644
index 0000000000000000000000000000000000000000..d301dcf84a89c4ca0d1c78ebea16d1c3cbe23b37
--- /dev/null
+++ b/_i18n/es/community/sponsorships.md
@@ -0,0 +1,97 @@
+{% include untranslated.html %}
+<div markdown="1" class="text-center container description">
+The following businesses have supported the Monero Project in its goal to bring financial privacy to the world. We couldn't be more grateful for their contributions. If you would like to sponsor the Monero Project and be listed on this page, please send an email to dev@getmonero.org.
+</div>
+
+<div>
+ <section class="container sponsors">
+ <div class="row">
+ <div class="left one-third no-pad-sm col-lg-4 col-md-4 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>My Monero</h2>
+ <a href="https://mymonero.com/#/" target="_blank" rel="noreferrer noopener"><img src="/img/mymonero.png"></a>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="center one-third no-pad-sm col-lg-4 col-md-4 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Araxis</h2>
+ <a href="https://www.araxis.com/"><img src="/img/araxis.png"></a>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="right one-third no-pad-sm col-lg-4 col-md-4 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Dome9 Security</h2>
+ <a href="https://dome9.com/"><img src="/img/dome9.png"></a>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="row">
+ <div class="left one-third no-pad-sm col-lg-4 col-md-4 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Kitware</h2>
+ <a href="https://www.kitware.com/"><img src="/img/kitware.png"></a>
+ </div>
+ </div>
+ </div>
+ </div>
+
+ <div class="center one-third no-pad-sm col-lg-4 col-md-4 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Fork Networking</h2>
+ <a href="https://www.forked.net"><img src="/img/forked_logo.png"></a>
+ </div>
+ </div>
+ </div>
+ </div>
+
+ <div class="right one-third no-pad-sm col-lg-4 col-md-4 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>JetBrains</h2>
+ <a href="http://www.jetbrains.com/"><img src="/img/jetbrains.png"></a>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="row">
+ <div class="left half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Navicat</h2>
+ <a href="https://www.navicat.com"><img src="/img/navicat.png"></a>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="right half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Symas</h2>
+ <a href="https://symas.com/"><img src="/img/symas.png"></a>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ </section>
+</div>
\ No newline at end of file
diff --git a/_i18n/es/community/team.md b/_i18n/es/community/team.md
new file mode 100644
index 0000000000000000000000000000000000000000..341d2a1941f701cf2206ba544e04c079f8fb2da8
--- /dev/null
+++ b/_i18n/es/community/team.md
@@ -0,0 +1,181 @@
+{% include untranslated.html %}
+<div class="team">
+
+ <section class="container">
+ <div class="row">
+ <div class="col-xs-12">
+ <div class="tabPanel-widget">
+ <label for="tab-1" tabindex="0"></label>
+ <input id="tab-1" type="radio" name="tabs" aria-hidden="true" checked>
+ <h2>Core</h2>
+ <div class="tabPanel-content">
+ <div class="row">
+ {% for toplevel in site.data.team %}
+ {% if toplevel.area == "Core" %}
+ {% for member in toplevel.member %}
+ <div class="half col-lg-6 col-md-6 col-sm-6 col-xs-6">
+ <div class="info-block">
+ <div class="row center-xs">
+ <h3>{{member.name}}</h3>
+ </div>
+ <div class="row center-xs">
+ <p>{{member.email}}</p>
+ </div>
+ <div class="row center-xs icons">
+ {% if member.github %}
+ <a href="{{member.github}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon github"></div></a>
+ {%endif%}
+ {% if member.twitter %}
+ <a href="{{member.twitter}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon twitter"></div></a>
+ {%endif%}
+ {% if member.reddit %}
+ <a href="{{member.reddit}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon reddit"></div></a>
+ {%endif%}
+ </div>
+ </div>
+ </div>
+ {%endfor%}
+ {%endif%}
+ {%endfor%}
+ </div>
+ </div>
+ <label for="tab-2" tabindex="0"></label>
+ <input id="tab-2" type="radio" name="tabs" aria-hidden="true">
+ <h2>Developers</h2>
+ <div class="tabPanel-content">
+ <div class="container full">
+ <div class="info-block text-adapt">
+ <div class="row">
+ <div class="col-xs-12 text-adapt">
+ <p>The Monero Project has had well over 200 contributors over the life of the project. For a complete list, please see the <a href="https://www.openhub.net/p/monero/contributors">OpenHub contributors page</a>. Below you'll find some individuals that have gone above and beyond for Monero.</p>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="row">
+ {% for toplevel in site.data.team %}
+ {% if toplevel.area == "Developers" %}
+ {% for member in toplevel.member %}
+ <div class="half col-lg-6 col-md-6 col-sm-6 col-xs-6">
+ <div class="info-block">
+ <div class="row center-xs">
+ <h3>{{member.name}}</h3>
+ </div>
+ <div class="row center-xs icons">
+ {% if member.github %}
+ <a href="{{member.github}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon github"></div></a>
+ {%endif%}
+ {% if member.twitter %}
+ <a href="{{member.twitter}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon twitter"></div></a>
+ {%endif%}
+ {% if member.reddit %}
+ <a href="{{member.reddit}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon reddit"></div></a>
+ {%endif%}
+ </div>
+ </div>
+ </div>
+ {%endfor%}
+ {%endif%}
+ {%endfor%}
+ </div>
+ </div>
+ <label for="tab-3" tabindex="0"></label>
+ <input id="tab-3" type="radio" name="tabs" aria-hidden="true">
+ <h2>Community</h2>
+ <div class="tabPanel-content">
+ <div class="row">
+ {% for toplevel in site.data.team %}
+ {% if toplevel.area == "Community" %}
+ {% for member in toplevel.member %}
+ <div class="half col-lg-6 col-md-6 col-sm-6 col-xs-6">
+ <div class="info-block">
+ <div class="row center-xs">
+ <h3>{{member.name}}</h3>
+ </div>
+ <div class="row center-xs icons">
+ {% if member.github %}
+ <a href="{{member.github}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon github"></div></a>
+ {%endif%}
+ {% if member.twitter %}
+ <a href="{{member.twitter}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon twitter"></div></a>
+ {%endif%}
+ {% if member.reddit %}
+ <a href="{{member.reddit}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon reddit"></div></a>
+ {%endif%}
+ </div>
+ </div>
+ </div>
+ {%endfor%}
+ {%endif%}
+ {%endfor%}
+ </div>
+ </div>
+ <label for="tab-4" tabindex="0"></label>
+ <input id="tab-4" type="radio" name="tabs" aria-hidden="true">
+ <h2>Research Lab</h2>
+ <div class="tabPanel-content">
+ <div class="row">
+ {% for toplevel in site.data.team %}
+ {% if toplevel.area == "Monero Research Lab" %}
+ {% for member in toplevel.member %}
+ <div class="half col-lg-6 col-md-6 col-sm-12 col-xs-6">
+ <div class="info-block">
+ <div class="row center-xs">
+ <h3>{{member.name}}</h3>
+ </div>
+ <div class="row center-xs icons">
+ {% if member.github %}
+ <a href="{{member.github}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon github"></div></a>
+ {%endif%}
+ {% if member.twitter %}
+ <a href="{{member.twitter}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon twitter"></div></a>
+ {%endif%}
+ {% if member.reddit %}
+ <a href="{{member.reddit}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon reddit"></div></a>
+ {%endif%}
+ </div>
+ </div>
+ </div>
+ {%endfor%}
+ {%endif%}
+ {%endfor%}
+ </div>
+ </div>
+ <label for="tab-5" tabindex="0"></label>
+ <input id="tab-5" type="radio" name="tabs" aria-hidden="true">
+ <h2>Special Thanks</h2>
+ <div class="tabPanel-content">
+ <div class="row">
+ {% for toplevel in site.data.team %}
+ {% if toplevel.area == "Special Thanks" %}
+ {% for member in toplevel.member %}
+ <div class="half col-lg-6 col-md-6 col-sm-12 col-xs-6">
+ <div class="info-block">
+ <div class="row center-xs">
+ <h3>{{member.name}}</h3>
+ </div>
+ <div class="row center-xs icons">
+ {% if member.github %}
+ <a href="{{member.github}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon github"></div></a>
+ {%endif%}
+ {% if member.twitter %}
+ <a href="{{member.twitter}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon twitter"></div></a>
+ {%endif%}
+ {% if member.reddit %}
+ <a href="{{member.reddit}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon reddit"></div></a>
+ {%endif%}
+ </div>
+ </div>
+ </div>
+ {%endfor%}
+ {%endif%}
+ {%endfor%}
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+</section>
+
+
+</div>
\ No newline at end of file
diff --git a/_i18n/es/downloads.md b/_i18n/es/downloads.md
new file mode 100644
index 0000000000000000000000000000000000000000..ae8003b289a624579b2584ddb983fcb130faedbc
--- /dev/null
+++ b/_i18n/es/downloads.md
@@ -0,0 +1,142 @@
+{% include untranslated.html %}
+<div class="downloads">
+
+<div class="container description" markdown="1">
+
+If you need help choosing the correct application, please click [here](https://www.reddit.com/r/Monero/comments/64b5lf/what_is_the_best_monero_wallet/) for a quick answer, then select the appropriate release for your operating system below.
+Note: the SHA256 hashes are listed by the downloads for convenience, but a GPG-signed list of the hashes is at [getmonero.org/downloads/hashes.txt](https://getmonero.org/downloads/hashes.txt) and should be treated as canonical, with the signature checked against the appropriate GPG key in the source code (in /utils/gpg_keys).
+
+</div>
+<div class="container full downdropdown">
+<div class="info-block download-nav row middle-xs between-xs" id="selections">
+
+ <div class="col"><a href="#windows">Windows</a></div>
+ <div class="col"><a href="#mac">Mac</a></div>
+ <div class="col"><a href="#linux">Linux</a></div>
+ <div class="col"><a href="#arm">Arm (v7 & 8)</a></div>
+ <div class="col"><a href="#bsd">BSD</a></div>
+ <div class="col"><a href="#source">Source & Blockchain</a></div>
+ <div class="col"><a href="#mobilelight">Mobile & Light</a></div>
+ <div class="col"><a href="#hardware">Hardware</a></div>
+
+</div>
+</div>
+
+<div class="container full">
+ <div class="info-block row center-xs" id="pick-platform">
+ <div class="mob dropdowndrop">
+ <input id="check01" type="checkbox" name="menu"/>
+ <label for="check01">Choose your OS</label>
+ <ul id="menu">
+ <li><a href="#windows">Windows</a></li>
+ <li><a href="#mac">Mac</a></li>
+ <li><a href="#linux">Linux</a></li>
+ <li><a href="#arm">Arm (v7 & 8)</a></li>
+ <li><a href="#bsd">BSD</a></li>
+ <li><a href="#source">Source & Blockchain</a></li>
+ <li><a href="#mobilelight">Mobile & Light</a></li>
+ <li><a href="#hardware">Hardware</a></li>
+ </ul>
+ </div>
+ </div>
+</div>
+
+
+<div class="download-platforms">
+
+{% for data_downloads in site.data.downloads %}
+
+<section class="container full" id="{{ data_downloads.id}}">
+ <div class="info-block">
+ <h2>
+ {% if data_downloads.icon != null %}
+ <span class="{{data_downloads.icon}}"></span>
+ {% endif %}
+ {{data_downloads.platform}}
+ </h2>
+ {% if data_downloads.version != null %}
+ <p class="text-center">Current Version: {{ data_downloads.version }} {{ data_downloads.tag }}</p>
+ {%endif%}
+
+
+
+{% if data_downloads.cli_hash == "source" %}
+<div class="row">
+<div class="col-md-8 col-md-offset-2 col-sm-12 col-xs-12">
+<h4 id="{{ data_downloads.platform | slugify }}">
+ <a href="{{ data_downloads.cli_url }}">Source Code</a>
+</h4>
+</div>
+<div class="col-md-8 col-md-offset-2 col-sm-12 col-xs-12" markdown="1">
+If you'd prefer to use a blockchain bootstrap, instead of syncing from scratch, you can [use this link for the most current bootstrap](https://downloads.getmonero.org/blockchain.raw). It is typically much faster to sync from scratch, however, and it also takes a lot less RAM (import is very greedy).
+</div>
+</div>
+{% elsif data_downloads.id == "hardware" %}
+<div class="row">
+<div class="col-md-8 col-md-offset-2 col-sm-12 col-xs-12">
+<p>The Monero community has just funded a <a href="https://forum.getmonero.org/9/work-in-progress/88149/dedicated-monero-hardware-wallet" target="_blank" rel="noreferrer, noopener">Dedicated Hardware Wallet</a> which is now in progress. As well, Ledger is working on <a href="https://github.com/LedgerHQ/blue-app-monero" target="_blank" rel="noreferrer, noopener">integrating Monero into their hardware wallets</a>.</p>
+</div></div>
+
+{% elsif data_downloads.id == "mobilelight" %}
+<div class="row">
+<div class="col-md-8 col-md-offset-2 col-sm-12 col-xs-12">
+<p>The following are mobile or light wallets that are deemed safe by trusted members of the community. If there is a wallet that is not on here, you can request the community check it out. Go to our <a href="/community/hangouts/">Hangouts</a> page to see where we are.</p>
+</div>
+</div>
+<div class="row center-xs">
+ <div class="col-xs-6">
+ <a href="https://mymonero.com"><img src="/img/mymonero.png" alt="MyMonero Logo"></a>
+ </div>
+ <div class="col-xs-6">
+ <a href="https://monerujo.io"><img style="height: 115px;" src="/img/Monerujo-wallet.png" alt="Monerujo Logo"></a>
+ </div>
+</div>
+
+
+{% elsif data_downloads.gui_hash == nil and data_downloads.cli_hash != nil %}
+<div class="row"><div class="col-md-8 col-md-offset-2 col-sm-12 col-xs-12"><h4 id="{{ data_downloads.platform | slugify }}">
+ <a href="//downloads.getmonero.org/cli/{{ data_downloads.cli_url }}"> {{ data_downloads.platform }} (Command-line Tools Only)</a>
+ </h4></div></div>
+ <div class="row"><div class="col-md-8 col-md-offset-2 col-sm-12 col-xs-12">
+ <p><strong>SHA256 Hash:</strong></p> <p class="hash"> {{ data_downloads.cli_hash }}</p></div>
+</div>
+{% elsif data_downloads.gui_hash != nil and data_downloads.cli_hash == nil %}
+<div class="row">
+
+<h4 id="{{ data_downloads.platform | slugify }}">
+ <a href="//downloads.getmonero.org/gui/{{ data_downloads.gui_url }}">{{ data_downloads.platform }}</a>
+ </h4></div>
+<div class="row">
+<p><strong>SHA256 Hash:</strong></p> <p class="hash"> {{ data_downloads.gui_hash }}</p>
+</div>
+{% elsif data_downloads.gui_hash != nil and data_downloads.cli_hash != nil %}
+<div class="row start-md">
+<div class="col-md-6 col-sm-12" >
+
+<h4 id="{{ data_downloads.platform | slugify }}">
+ <a href="//downloads.getmonero.org/gui/{{ data_downloads.gui_url }}">{{ data_downloads.platform }}</a>
+</h4>
+<p><strong>SHA256 Hash (GUI):</strong></p> <p class="hash"> {{ data_downloads.gui_hash }}</p>
+
+</div>
+
+<div class="col-md-6 col-sm-12">
+<h4>
+ <a href="//downloads.getmonero.org/cli/{{ data_downloads.cli_url }}">{{ data_downloads.platform }} (Command-Line Tools Only)</a>
+</h4>
+<p><strong>SHA256 Hash (CLI):</strong></p> <p class="hash"> {{ data_downloads.cli_hash }}</p>
+</div>
+</div>
+{% endif %}
+ </div>
+</section>
+
+{% endfor %}
+
+</div>
+<a href="#" class="arrow-up"><i></i></a>
+
+</div>
+
+
+
diff --git a/_i18n/es/get-started/accepting.md b/_i18n/es/get-started/accepting.md
new file mode 100644
index 0000000000000000000000000000000000000000..1a6f315f00a7cd51739ee788f35b365a4f61243c
--- /dev/null
+++ b/_i18n/es/get-started/accepting.md
@@ -0,0 +1,90 @@
+{% include untranslated.html %}
+<section class="container">
+ <div class="row">
+ <!-- left two-thirds block-->
+ <div class="full">
+ <div class="info-block text-adapt">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Instructions for the Command-Line Interface</h2>
+ </div>
+ </div>
+<div markdown="1">
+
+### The Basics
+
+Monero works a little differently to what you may have become accustomed to from other @cryptocurrencies. In the case of a digital currency like Bitcoin and its many derivatives merchant payment systems will usually create a new recipient @address for each payment or user.
+
+However, because Monero has @stealth-addresses there is no need to have separate recipient addresses for each payment or user, and a single @account address can be published. Instead, when receiving payments a merchant will provide the person paying with a "payment ID".
+
+A @payment-ID is a hexadecimal string that is 64 characters long, and is normally randomly created by the merchant. An example of a payment ID is:
+```
+666c75666679706f6e7920697320746865206265737420706f6e792065766572
+```
+
+### Checking for a Payment in monero-wallet-cli
+
+If you want to check for a payment using monero-wallet-cli you can use the "payments" command followed by the payment ID or payment IDs you want to check. For example:
+
+```
+[wallet 49VNLa]: payments 666c75666679706f6e7920697320746865206265737420706f6e792065766572
+ payment transaction height amount unlock time
+ 666c75666679706f6e79206973207 7ba4cd810c9b4096869849458181e98e 441942 30.00000 0
+[wallet 49VNLa]: â–ˆ
+```
+
+If you need to check for payments programmatically, then details follow the next section.
+
+### Receiving a Payment Step-by-Step
+
+* Generate a random 64 character hexadecimal string for the payment
+* Communicate the payment ID and Monero address to the individual who is making payment
+* Check for the payment using the "payments" command in monero-wallet-cli
+
+### Checking for a Payment Programmatically
+
+In order to check for a payment programmatically you can use the get_payments or get_bulk_payments JSON RPC API calls.
+
+*get_payments*: this requires a payment_id parameter with a single payment ID.
+
+*get_bulk_payments*: this is the preferred method, and requires two parameters, payment_ids - a JSON array of payment IDs - and an optional min_block_height - the block height to scan from.
+
+An example of returned data is as follows:
+
+```
+[ monero->~ ]$ curl -X POST http://127.0.0.1:18500/json_rpc -d '{"jsonrpc":"2.0","method":"get_bulk_payments","id":"test", "params":{"payment_ids": ["666c75666679706f6e7920697320746865206265737420706f6e792065766572"]}}' -H "Content-Type: application/json"
+{
+ "id": "test",
+ "jsonrpc": "2.0",
+ "result": {
+ "payments": [{
+ "amount": 30000000000000,
+ "block_height": 441942,
+ "payment_id": "666c75666679706f6e7920697320746865206265737420706f6e792065766572",
+ "tx_hash": "7ba4cd810c9b4096869849458181e98e18b6474ab66415de0f4ccf7ab1162fdf",
+ "unlock_time": 0
+ }]
+ }
+}
+```
+
+It is important to note that the amounts returned are in base Monero units and not in the display units normally used in end-user applications. Also, since a transaction will typically have multiple outputs that add up to the total required for the payment, the amounts should be grouped by the tx_hash or the payment_id and added together. Additionally, as multiple outputs can have the same amount, it is imperative not to try and filter out the returned data from a single get_bulk_payments call.
+
+Before scanning for payments it is useful to check against the daemon RPC API (the get_info RPC call) to see if additional blocks have been received. Typically you would want to then scan only from that received block on by specifying it as the min_block_height to get_bulk_payments.
+
+### Programatically Scanning for Payments
+
+* Get the current block height from the daemon, only proceed if it has increased since our last scan
+* Call the get_bulk_payments RPC API call with our last scanned height and the list of all payment IDs in our system
+* Store the current block height as our last scanned height
+* Remove duplicates based on transaction hashes we have already received and processed
+
+</div>
+ </div>
+ </div>
+
+
+ <!-- end right one-third block-->
+ </div>
+ </section>
+
\ No newline at end of file
diff --git a/_i18n/es/get-started/contributing.md b/_i18n/es/get-started/contributing.md
new file mode 100644
index 0000000000000000000000000000000000000000..ac8467a14fdb8887c90008a8dc4f7617e6100c71
--- /dev/null
+++ b/_i18n/es/get-started/contributing.md
@@ -0,0 +1,93 @@
+{% include untranslated.html %}
+<div markdown="1" class="text-center container description">
+Monero is an open-source, community-driven project. Described below are several ways to support the project.
+</div>
+
+<div class="contribute">
+ <section class="container">
+ <div class="row">
+ <!-- full block-->
+ <div class="full col-lg-12 col-md-12 col-sm-12 col-xs-12">
+ <div class="info-block text-adapt">
+ <div class="row center-xs">
+ <div class="col"><h2>Support the Network</h2></div>
+ </div>
+<div class="row start-xs" markdown="1">
+
+### Develop
+Monero is primarily written in C++. As it is a decentralized project, anyone is welcome to add or make changes to existing code. Pull requests are merged based on community consensus. See the <a href="https://github.com/monero-project"> repositories</a> and outstanding <a href="https://github.com/monero-project/monero/issues">issues</a>.
+
+### Run a Full Node
+Run monerod with port 18080 open. Running a full node ensures maximum privacy when transacting with Monero. It also improves distribution of the blockchain to new users.
+
+### Mine
+Mining ensures the Monero network remains decentralized and secure. In the Monero graphical user interface and command-line interface, background mining may be activated. Additional resources for mining may be viewed [here](https://reddit.com/r/MoneroMining).
+
+</div>
+ </div>
+ </div>
+ <!-- end full block-->
+ <!-- full block-->
+ <div class="full col-lg-12 col-md-12 col-sm-12 col-xs-12">
+ <div class="info-block text-adapt">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>View the Forum Funding System</h2>
+ </div>
+ </div>
+ <div class="row start-xs">
+ <p>Monero utilizes a <a href="https://forum.getmonero.org">forum funding system</a> whereby projects are proposed for development and community-funded. Funding is held in escrow and remunerated to developers once programming milestones are achieved. Anyone may generate new proposals or fund existing ones.</p>
+ </div>
+ </div>
+ </div>
+ <!-- full block-->
+ <!-- full block-->
+ <div class="full col-lg-12 col-md-12 col-sm-12 col-xs-12">
+ <div class="info-block text-adapt">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Donate</h2>
+ </div>
+ </div>
+ <div class="row start-xs">
+ <p>Ongoing development is supported by donations and <a href="{{site.baseurl}}/community/sponsorships/">sponsorships</a>.</p>
+ </div>
+ <div class="row center-xs">
+ <div class="col-lg-6">
+ <img src="/img/donate-monero.png" alt=""/>
+ </div>
+ <div class="col-lg-6">
+ <img src="/img/donate-bitcoin.png" alt=""/>
+ </div>
+ </div>
+ <div class="row start-xs">
+ <div class="col-xs-12">
+ <h3>Donating Monero</h3>
+ <p>Donations may be sent to donate.getmonero.org or 44AFFq5kSiGBoZ4NMDwYtN18obc8AemS33DBLWs3H7otXft3XjrpDtQGv7SqSsaBYBb98uNbr2VBBEt7f2wfn3RVGQBEP3A</p>
+ </div>
+ </div>
+ <div class="row start-xs">
+ <div class="col-xs-12">
+ <h3>Donating Bitcoin</h3>
+ <p>Donations may be sent to donate.getmonero.org or 1KTexdemPdxSBcG55heUuTjDRYqbC5ZL8H</p>
+ </div>
+ </div>
+ <div class="row start-xs">
+ <div class="col-xs-12">
+ <h3>Other</h3>
+ <p>E-mail <a href="mailto:dev@getmonero.org">dev@getmonero.org</a> for alternative means of donating or if you would like to become a sponsor for the Monero Project.</p>
+ </div>
+ </div>
+ </div>
+ </div>
+ <!-- full block-->
+
+
+
+
+
+
+ </div>
+ </section>
+
+</div>
diff --git a/_i18n/es/get-started/faq.md b/_i18n/es/get-started/faq.md
new file mode 100644
index 0000000000000000000000000000000000000000..4aa8d532ac4f994d0a2cda4390f3394bc76dbfe8
--- /dev/null
+++ b/_i18n/es/get-started/faq.md
@@ -0,0 +1,136 @@
+{% include untranslated.html %}
+<div class="tab">
+ <input id="tab-one" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-one" class="accordion">How does Monero have value?</label>
+
+<div class="tab-content" markdown="1">
+
+Monero has value because people are willing to buy it. If no one is willing to buy Monero, then it will not have any value. Monero’s price increases if demand exceeds supply, and it decreases if supply exceeds demand.
+
+</div>
+
+</div>
+
+<div class="tab">
+ <input id="tab-two" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-two" class="accordion">How can I get Monero?</label>
+
+<div class="tab-content" markdown="1">
+
+You can buy Monero from an exchange or from an individual. Alternatively, you can try mining Monero to get coins from the block reward.
+</div>
+
+</div>
+
+<div class="tab">
+ <input id="tab-three" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-three" class="accordion">What is a mnemonic seed?</label>
+
+<div class="tab-content" markdown="1">
+
+A mnemonic seed is a set of 25 words that can be used to restore your account anywhere. Keep these words safe and do not share them with someone else. You can use this seed to restore your account, even if your computer crashes.
+</div>
+
+</div>
+
+<div class="tab">
+ <input id="tab-four" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-four" class="accordion">How is Monero’s privacy different from other coins?</label>
+
+<div class="tab-content" markdown="1">
+
+Monero uses three different privacy technologies: ring signatures, ring confidential transactions (RingCT), and stealth addresses. These hide the sender, amount, and receiver in the transaction, respectively. All transactions on the network are private by mandate; there is no way to accidentally send a transparent transaction. This feature is exclusive to Monero. You do not need to trust anyone else with your privacy.
+</div>
+
+</div>
+
+<div class="tab">
+ <input id="tab-five" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-five" class="accordion">Why is my wallet taking so long to sync?</label>
+
+<div class="tab-content" markdown="1">
+
+If you are running a full node locally, you need to copy the entire blockchain to your computer. This can take a long time, especially on an old hard drive or slow internet connection. If you are using a remote node, your computer still needs to request a copy of all the outputs, which can take several hours. Be patient, and if you would like to sacrifice some privacy for faster sync times, consider using a lightweight wallet instead.
+</div>
+
+</div>
+
+<div class="tab">
+ <input id="tab-six" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-six" class="accordion">What is the different between a lightweight and a normal wallet?</label>
+
+<div class="tab-content" markdown="1">
+
+For a lightweight wallet, you give your view key to a node, who scans the blockchain and looks for incoming transactions to your account on your behalf. This node will know when you receive money, but it will not know how much you receive, who you received it from, or who you are sending money to. Depending on your wallet software, you may be able to use a node you control to avoid privacy leaks. For more privacy, use a normal wallet, which can be used with your own node.
+</div>
+
+</div>
+
+<div class="tab">
+ <input id="tab-seven" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-seven" class="accordion">How is Monero different from Bitcoin?</label>
+
+<div class="tab-content" markdown="1">
+
+Monero is not based on Bitcoin. It is based on the CryptoNote protocol. Bitcoin is a completely transparent system, where people can see exactly how much money is being sent from one user to another. Monero hides this information to protect user privacy in all transactions. It also has a dynamic block size and dynamic fees, an ASIC-resistant proof of work, and a tail coin emission, among several other changes.
+</div>
+
+</div>
+
+<div class="tab">
+ <input id="tab-eight" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-eight" class="accordion">Does Monero have a block size limit?</label>
+
+<div class="tab-content" markdown="1">
+
+No, Monero does not have a hard block size limit. Instead, the block size can increase or decrease over time based on demand. It is capped at a certain growth rate to prevent outrageous growth.
+</div>
+
+</div>
+
+<div class="tab">
+ <input id="tab-nine" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-nine" class="accordion">What is a blockchain?</label>
+
+<div class="tab-content" markdown="1">
+
+A blockchain is a system that stores a copy of all transaction history on the Monero network. Every two minutes, a new block with the latest transaction information is added to the blockchain. This chain allows the network to verify the amount of money accounts have and make it resilient to attacks and centralization attempts.
+</div>
+
+</div>
+
+<div class="tab">
+ <input id="tab-ten" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-ten" class="accordion">What is Kovri?</label>
+
+<div class="tab-content" markdown="1">
+
+Kovri is an I2P router written in C++. I2P is a hidden network like Tor with several technical differences. Kovri is an independent project of Monero, but it will work with Monero and several other projects. Kovri hides the transaction broadcast, so other nodes do not know who created transactions. In adversarial conditions, Kovri can be used to hide all Monero traffic through I2P, which would prevent people from knowing Monero is being used. Kovri is currently in alpha, and it is not yet fully integrated in Monero. Learn more about Kovri at the [project website.](https://getkovri.org)
+</div>
+
+</div>
+
+<div class="tab">
+ <input id="tab-eleven" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-eleven" class="accordion">What is fungibility, and why is it important?</label>
+
+<div class="tab-content" markdown="1">
+
+Fungibility is a simple property of money such that there are no differences between two amounts of the same value. If two people exchanged a 10 and two 5’s, then no one would lose out. However, let’s suppose that everyone knows the 10 was previously used in a ransomware attack. Is the other person still going to make the trade? Probably not, even if the person with the 10 has no connection with the ransomware. This is a problem, since the receiver of money needs to constantly check the money they are receiving to not end up with tainted coins. Monero is fungible, which means people do not need to go through this effort.
+</div>
+
+</div>
+
+<div class="tab">
+ <input id="tab-twelve" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-twelve" class="accordion">If Monero is so private how do we know they're not being created out of thin air?</label>
+
+<div class="tab-content" markdown="1">
+In Monero, every transaction output is uniquely associated with a key image that can only be generated by the holder of that output. Key images that are used more than once are rejected by the miners as double-spends and cannot be added to a valid block. When a new transaction is received, miners verify that the key image does not already exist for a previous transaction to ensure it's not a double-spend.
+
+We can also know that transaction amounts are valid even though the value of the inputs that you are spending and the value of the outputs you are sending are encrypted (these are hidden to everyone except the recipient). Because the amounts are encrypted using Pedersen commitments what this means is that no observers can tell the amounts of the inputs and outputs, but they can do math on the Pedersen commitments to determine that no Monero was created out of thin air.
+
+As long as the encrypted output amounts you create is equal to the sum of the inputs that are being spent (which include an output for the recipient and a change output back to yourself and the unencrypted transaction fee), then you have a legitimate transaction and know no Monero is being created out of thin air. 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.
+</div>
+
+</div>
diff --git a/_i18n/es/get-started/mining.md b/_i18n/es/get-started/mining.md
new file mode 100644
index 0000000000000000000000000000000000000000..2a94422954da115ceb0bbe83c0f6653bf79d8934
--- /dev/null
+++ b/_i18n/es/get-started/mining.md
@@ -0,0 +1,86 @@
+<div class="mining">
+<div class="center-xs container description">
+<p>Monero is a cryptocurrency that relies on proof-of-work mining to achieve distributed consensus. Below you'll find some information and resources on how to begin mining.</p>
+
+<p><strong>The Monero Project does not endorse any particular pool, software, or hardware, and the content below is provided for informational purposes only.</strong></p>
+</div>
+
+<section class="container">
+ <div class="row">
+ <!-- full block-->
+ <div class="full col-lg-12 col-md-12 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Support</h2>
+ </div>
+ </div>
+ <div class="row center-xs">
+ <p>See <a href="{{site.baseurl}}/community/hangouts/"> Hangouts</a>, <a href="https://www.reddit.com/r/MoneroMining/" target="_blank" rel="noreferrer noopener">/r/moneromining</a> and <a href="irc://chat.freenode.net/#monero-pools" target="_blank" rel="noreferrer noopener">#monero-pools</a>.</p>
+ </div>
+ </div>
+ </div>
+ <!-- end full block -->
+ </div>
+ </section>
+<section class="container">
+ <div class="row">
+ <div class="left half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Pools</h2>
+ </div>
+ </div>
+ <div class="row center-xs">
+ <p>A listing of trusted Monero pools is found <a href="http://moneropools.com/"> here</a>.</p>
+ </div>
+ </div>
+ </div>
+ <div class="right half col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Hardware Benchmarking</h2>
+ </div>
+ </div>
+ <div class="row center-xs">
+ <p>See <a href="http://monerobenchmarks.info/">here</a> for a listing of GPUs/CPUs and their respective hashrates.</p>
+ </div>
+ </div>
+ </div>
+ </div>
+ </section>
+ <section class="container">
+ <div class="row">
+ <!-- full block-->
+ <div class="full col-lg-12 col-md-12 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Mining Software</h2>
+ </div>
+ </div>
+ <div class="row center-xs">
+ <p>Note that some miners may have developer fees.</p>
+ </div>
+ <div class="row center-xs">
+ <p><a href="https://github.com/fireice-uk/xmr-stak" target="_blank" rel="noreferrer noopener">XMR Stak</a></p>
+ </div>
+ <div class="row center-xs">
+ <p><a href="https://github.com/xmrig/xmrig" target="_blank" rel="noreferrer noopener">XMRig</a></p>
+ </div>
+ <div class="row center-xs">
+ <p><a href="https://github.com/xmrig/xmrig-amd" target="_blank" rel="noreferrer noopener">XMRig AMD</a></p>
+ </div>
+ <div class="row center-xs">
+ <p><a href="https://github.com/xmrig/xmrig-nvidia" target="_blank" rel="noreferrer noopener">XMRig NVIDIA</a></p>
+ </div>
+ </div>
+ </div>
+ <!-- end full block -->
+ </div>
+ </section>
+
+
+</div>
\ No newline at end of file
diff --git a/_i18n/es/get-started/using.md b/_i18n/es/get-started/using.md
new file mode 100644
index 0000000000000000000000000000000000000000..74fed473139e40f5da00d08411344a813a395aa1
--- /dev/null
+++ b/_i18n/es/get-started/using.md
@@ -0,0 +1,99 @@
+{% include untranslated.html %}
+<div class="text-center container description">
+ <p>Transacting with Monero can be made easy. This page is designed to guide users in that process.</p>
+</div>
+<div class="using">
+ <section class="container">
+ <div class="row">
+ <!-- full block-->
+ <div class="full col-lg-12 col-md-12 col-sm-12 col-xs-12">
+ <div class="info-block text-adapt">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>1. Learn</h2>
+ </div>
+ </div>
+ <div class="row start-xs">
+ <p>Monero is a secure, private, and untraceable cryptocurrency. The developers and community are committed to protecting these values. Learn more by reading the <a href="{{site.baseurl}}/get-started/what-is-monero/">What is Monero</a> page. The <a href="https://github.com/monero-project">source code</a> is also available for review and discussion.</p>
+ </div>
+ </div>
+ </div>
+ <!-- end full block -->
+ </div>
+ </section>
+ <section class="container">
+ <div class="row">
+ <div class="left half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>2. Request Support</h2>
+ </div>
+ </div>
+ <div class="row start-xs">
+ <p>There is a large and supportive community that will assist if you experience any difficulty. See the <a href="{{site.baseurl}}/community/hangouts/">Hangouts</a> page for more information.</p>
+ </div>
+ </div>
+ </div>
+ <div class="right half col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>3. Generate a Wallet</h2>
+ </div>
+ </div>
+ <div class="row start-xs">
+ <p>A Monero wallet is required to secure your own funds. See the <a href="{{site.baseurl}}/downloads/">Downloads</a> page for a listing of available wallets.</p>
+ <p>The easiest way to run a Monero node, without affecting your home bandwidth, is to purchase a VPS (Virtual Private Server). We strongly recommend <a href="https://interserver.net/dock/vps-231552.html">InterServer.net</a> using the 'MONERO' coupon code to get a discount over and above their already cheap $6/month VPS. Using this coupon code and/or <a href="https://interserver.net/dock/vps-231552.html">our affiliate link</a> will also assist in the ongoing funding of Monero development.</p>
+ </div>
+ </div>
+ </div>
+ </div>
+ </section>
+ <section class="container">
+ <div class="row">
+ <!-- full block-->
+ <div class="full col-lg-12 col-md-12 col-sm-12 col-xs-12">
+ <div class="info-block text-adapt">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>4. Acquire Monero</h2>
+ </div>
+ </div>
+ <div class="row start-xs">
+ <p>Monero may be purchased on an <a href="{{site.baseurl}}/community/merchants#exchanges">exchange</a> with fiat or other cryptocurrencies. An alternate way of acquiring Monero is via <a href="{{site.baseurl}}/get-started/mining/">mining</a>, the computationally-complex process whereby transactions are immutably recorded on the blockchain.</p>
+ </div>
+ </div>
+ </div>
+ <!-- end full block -->
+ </div>
+ </section>
+ <section class="container">
+ <div class="row">
+ <div class="left half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>5. Send and Receive Monero</h2>
+ </div>
+ </div>
+ <div class="row start-xs">
+ <p>Learn how to send and receive Monero by viewing the <a href="{{site.baseurl}}/get-started/accepting/">guide</a>.</p>
+ </div>
+ </div>
+ </div>
+ <div class="right half col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>6. Transact with Monero</h2>
+ </div>
+ </div>
+ <div class="row start-xs">
+ <p>Monero may be used to purchase many goods and services. For a listing, see the <a href="{{site.baseurl}}/community/merchants/">Merchants</a> page. </p>
+ </div>
+ </div>
+ </div>
+ </div>
+ </section>
+</div>
diff --git a/_i18n/es/get-started/what-is-monero.md b/_i18n/es/get-started/what-is-monero.md
new file mode 100644
index 0000000000000000000000000000000000000000..cb8f0c303936c1d1cf6e0552e8505b7278c45eb0
--- /dev/null
+++ b/_i18n/es/get-started/what-is-monero.md
@@ -0,0 +1,120 @@
+{% include untranslated.html %}
+<div class="site-wrap">
+ <section class="container">
+ <div class="row">
+ <section class="container about-monero full col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col"><h2>What you need to know</h2></div>
+ </div>
+ <div class="row middle-xs info-block-row private">
+ <div class="col-lg-7 col-md-6 col-sm-8 col-xs-12 why-text">
+ <h3>Monero is the leading cryptocurrency with a focus on private and censorship-resistant transactions.</h3>
+ <p>Most existing cryptocurrencies, including Bitcoin and Ethereum, have transparent blockchains, meaning that transactions are openly verifiable and traceable by anyone in the world. Furthermore, sending and receiving addresses for these transactions may potentially be linkable to a person's real-world identity. </p>
+ <p>Monero uses cryptography to shield sending and receiving addresses, as well as transacted amounts.</p>
+ </div>
+ <div class="col-lg-5 col-md-6 col-sm-4 col-xs-12 last-sm first-xs center-xs">
+ <img src="/img/crypto-lock.png" alt="Encrypted lock" class="main-icon">
+ </div>
+ </div>
+ <div class="row middle-xs info-block-row">
+ <div class="col-lg-5 col-md-6 col-sm-4 col-xs-12 center-xs">
+ <img src="/img/monero-classified.png" alt="Classified document" class="main-icon">
+ </div>
+ <div class="col-lg-7 col-md-6 col-sm-8 col-xs-12 why-text">
+ <h3>Monero transactions are confidential and untraceable.</h3>
+ <p>Every Monero transaction, by default, obfuscates sending and receiving addresses as well as transacted amounts. This always-on privacy means that every Monero user's activity enhances the privacy of all other users, unlike selectively transparent cryptocurrencies (e.g. Z-Cash).</p>
+ <p>Monero is fungible. By virtue of obfuscation, Monero cannot become tainted through participation in previous transactions. This means Monero will always be accepted without the risk of censorship.</p>
+ <p>The Kovri Project, <a href="https://getkovri.org/">currently in development</a>, will route and encrypt transactions via I2P Invisible Internet Project nodes. This will obfuscate a transactor's IP address and provide further protection against network monitoring.</p>
+ </div>
+
+ </div>
+ <div class="row middle-xs info-block-row">
+ <div class="col-lg-7 col-md-6 col-sm-8 col-xs-12 why-text">
+ <h3>Monero is a grassroots community attracting the world's best cryptocurrency researchers and engineering talent.</h3>
+ <p>Over <a href="https://www.openhub.net/p/monero" target="_blank" rel="noreferrer noopener">240 developers</a> have contributed to the Monero project, including 30 core developers. Forums and chat channels are welcoming and active.</p>
+ <p>Monero's Research Lab, Core Development Team and Community Developers are constantly pushing the frontier of what is possible with cryptocurrency privacy and security.</p>
+ <p>Monero is not a corporation. It is developed by cryptography and distributed systems experts from all over the world that donate their time or are funded by community donations. This means that Monero can't be shut down by any one country and is not constrained by any particular legal jurisdiction.</p>
+ </div>
+ <div class="col-lg-5 col-md-6 col-sm-4 col-xs-12 last-sm first-xs center-xs">
+ <img src="/img/academic-growth.png" alt="Academic growth" class="main-icon">
+ </div>
+ </div>
+ <div class="row middle-xs info-block-row">
+ <div class="col-lg-5 col-md-6 col-sm-4 col-xs-12 center-xs">
+ <img src="/img/monero-electronic-cash.png" alt="Electronic cash" class="main-icon">
+ </div>
+ <div class="col-lg-7 col-md-6 col-sm-8 col-xs-12 why-text">
+ <h3>Monero is electronic cash that allows fast, inexpensive payments to and from anywhere in the world.</h3>
+ <p>There are no multi-day holding periods and no risk of fraudulent chargebacks. It is safe from ‘capital controls’ - these are measures that restrict the flow of traditional currencies, sometimes to an extreme degree, in countries experiencing economic instability.</p>
+ </div>
+ </div>
+ </div>
+ </section>
+ <section class="full col-xs-12 monero-vid">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col"><h2>Monero Videos</h2></div>
+ </div>
+ <div class="row center-xs">
+ <div class="col-xs-12 carousel-container">
+ <ul class="carousel my-carousel">
+ <input class="carousel-activator" type="radio" id="A" name="activator" checked="checked"/>
+ <input class="carousel-activator" type="radio" id="B" name="activator"/>
+ <input class="carousel-activator" type="radio" id="C" name="activator"/>
+ <input class="carousel-activator" type="radio" id="D" name="activator"/>
+ <div class="carousel-controls">
+ <label class="carousel-control carousel-control-backward" for="D"></label>
+ <label class="carousel-control carousel-control-forward" for="B"></label>
+ </div>
+ <div class="carousel-controls">
+ <label class="carousel-control carousel-control-backward" for="A"></label>
+ <label class="carousel-control carousel-control-forward" for="C"></label>
+ </div>
+ <div class="carousel-controls">
+ <label class="carousel-control carousel-control-backward" for="B"></label>
+ <label class="carousel-control carousel-control-forward" for="D"></label>
+ </div>
+ <div class="carousel-controls">
+ <label class="carousel-control carousel-control-backward" for="C"></label>
+ <label class="carousel-control carousel-control-forward" for="A"></label>
+ </div>
+ <li class="carousel-slide ms">
+ <h3>Monero Promo</h3>
+ <video controls poster="/img/monero-community.png" onclick="this.paused ? this.play() : this.pause();" preload="none">
+ <source src="/media/Monero_Promo.m4v">
+ </video>
+ </li>
+ <li class="carousel-slide">
+ <h3>Monero: The Essentials</h3>
+ <video controls poster="/img/monero-cash-video-poster.png" onclick="this.paused ? this.play() : this.pause();" preload="none">
+ <source src="/media/Monero%20-%20The%20Essentials.m4v">
+ </video>
+ </li>
+ <li class="carousel-slide">
+ <h3>Stealth Addresses</h3>
+ <video controls poster="/img/stealth-address-poster.png" onclick="this.paused ? this.play() : this.pause();" preload="none">
+ <source src="/media/Monero%20-%20Stealth%20Addresses.m4v">
+ </video>
+ </li>
+ <li class="carousel-slide">
+ <h3>Ring Signatures</h3>
+ <video controls poster="/img/ring-signatures-poster.png" onclick="this.paused ? this.play() : this.pause();" preload="none">
+ <source src="/media/Monero%20-%20Ring%20Signatures.m4v">
+ </video>
+ </li>
+ <li class="carousel-slide">
+ <h3>RingCT</h3>
+ <video controls poster="/img/ringct-poster.png" onclick="this.paused ? this.play() : this.pause();" preload="none">
+ <source src="/media/Monero%20-%20RingCT.m4v">
+ </video>
+ </li>
+ </ul>
+ </div>
+ </div>
+ </div>
+ </section>
+
+ </div>
+ </section>
+</div>
\ No newline at end of file
diff --git a/_i18n/es/index.md b/_i18n/es/index.md
new file mode 100644
index 0000000000000000000000000000000000000000..f72e3d6524155b28d17efcc2b09fe353da2120c2
--- /dev/null
+++ b/_i18n/es/index.md
@@ -0,0 +1,186 @@
+<div class="site-wrap">
+ <section class="container full col-xs-12">
+ <div class="info-block info-block-main">
+ <div class="row middle-xs">
+ <div class="col-lg-7 col-md-7 col-xs-12 main-video">
+ <div class="monero-video">
+ <!--iframe width="560" height="315" src="https://www.youtube.com/embed/TZi9xx6aiuY" frameborder="0" allowfullscreen></iframe-->
+ <video controls poster="/img/monero-community.png" onclick="this.paused ? this.play() : this.pause();" preload="none">
+ <source src="/media/Monero_Promo.m4v">
+ </video>
+ </div>
+ </div>
+ <div class="col-lg-5 col-md-5 col-xs-12">
+ <div class="main-info">
+ <h1 id="main-h1">Monero</h1>
+ <h2 id="main-h2">Moneda digital privada</h2>
+ <p id="main-text">Monero es una moneda privada, segura y no rastreable. Es de código abierto y está disponible para todos. Con Monero, tú eres tu propio banco. Sólo tú controlas tus finanzas. Tus cuentas y transacciones están protegidas de ojos curiosos.</p>
+ <p><a href="{{site.baseurl}}/get-started/using/" class="btn-link btn-auto btn-primary">Comenzar</a></p>
+ </div>
+ </div>
+ </div>
+ </div>
+ </section>
+ <!-- FULL WIDTH BLOCK -->
+ <section class="container about-main full col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col"><h2>Por qué Monero es diferente</h2></div>
+ </div>
+ <div class="row middle-xs info-block-row private">
+ <div class="col-lg-6 col-md-6 col-sm-8 col-xs-12 why-text">
+ <h3>Monero es segura</h3>
+ <p>Monero es una criptomoneda descentralizada. Es decir, es dinero digital seguro operado por su propia red de usuarios. Las transacciones son confirmadas por consenso distribuido y luego registradas inmutablemente en la cadena de bloques. De esta manera, mantiene tu dinero seguro sin necesidad de terceras partes.</p>
+ </div>
+ <div class="col-lg-6 col-md-6 col-sm-4 col-xs-12 last-sm first-xs center-xs">
+ <img src="/img/secure-monero.png" alt="Secure safe" class="main-icon">
+ </div>
+ </div>
+ <div class="row middle-xs info-block-row">
+ <div class="col-lg-6 col-md-6 col-sm-4 col-xs-12 center-xs">
+ <img src="/img/private-monero.png" alt="No surveillance" class="main-icon">
+ </div>
+ <div class="col-lg-6 col-md-6 col-sm-8 col-xs-12 why-text">
+ <h3>Monero es privada</h3>
+ <p>Monero usa las tecnologÃas de firmas de cÃrculo y transacciones confidenciales de cÃrculo (RingCT) para ofuscar el importe, orÃgen y destino cada transacción. Monero ofrece los beneficios de una criptomoneda descentralizada sin comprometer la privacidad.</p>
+ </div>
+ </div>
+ <div class="row middle-xs info-block-row">
+ <div class="col-lg-6 col-md-6 col-sm-8 col-xs-12 why-text">
+ <h3>Monero is untraceable</h3>
+ <p>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.</p>
+ </div>
+ <div class="col-lg-6 col-md-6 col-sm-4 col-xs-12 last-sm first-xs center-xs">
+ <img src="/img/untraceable-monero.png" alt="Untraceable Monero paths" class="main-icon">
+ </div>
+ </div>
+ <div class="row middle-xs info-block-row">
+ <div class="col-lg-6 col-md-6 col-sm-4 col-xs-12 center-xs">
+ <img src="/img/fungible-monero.png" alt="Monero gold" class="main-icon">
+ </div>
+ <div class="col-lg-6 col-md-6 col-sm-8 col-xs-12 why-text">
+ <h3>Monero es fungible</h3>
+ <p> Monero es fungible porque es privada por defecto. Eso provoca que unidades de Monero no pueden ser etiquetadas o deprivadas de su valor por provenir de transacciones especÃficas.</p>
+ </div>
+ </div>
+ </div>
+ </section>
+
+ <!-- END FULL WIDTH BLOCK -->
+
+
+
+ <!-- TWO THIRDS & ONE THIRD BLOCKS ROW -->
+
+ <section class="container">
+ <div class="row">
+ <!-- left two-thirds block-->
+ <div class="left two-thirds col-lg-8 col-md-8 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col"><h2>Downloads</h2></div>
+ </div>
+ <div class="row around-xs">
+ <div class="col">
+ <p><a href="{{site.baseurl}}/downloads#windows" class="btn-link btn-fixed"><span class="icon-windows"></span>Monero para Windows</a></p>
+ </div>
+ <div class="col">
+ <p><a href="{{site.baseurl}}/downloads#mac" class="btn-link btn-fixed"><span class="icon-apple"></span>Monero para Mac</a></p>
+ </div>
+ </div>
+ <div class="row around-xs">
+ <div class="col">
+ <p><a href="{{site.baseurl}}/downloads#linux" class="btn-link btn-fixed"><span class="icon-linux"></span>Monero para Linux</a></p>
+ </div>
+ <div class="col">
+ <p><a href="{{site.baseurl}}/downloads#source" class="btn-link btn-fixed"><span class="icon-blockchain"></span>Cadena de bloques</a></p>
+ </div>
+ </div>
+ <div class="row">
+ <div class="col-xs-12"><p class="main-downloads">¿Usas otro sistema operativo? <a href="{{site.baseurl}}/downloads/">Mira todas las descargas disponibles aquÃ.</a></p>
+ </div>
+ </div>
+ </div>
+ </div>
+ <!-- end left two-thirds block-->
+
+ <!-- right one-third block-->
+ <div class="right one-third col-lg-4 col-md-4 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col"><h2>Noticias recientes</h2></div>
+ </div>
+ <div class="info-block-row">
+ {% for post in site.posts limit:2 %}
+ <div class="row start-xs">
+ <div class="col">
+ <p><a href="{{site.baseurl}}/{{ post.url }}">{{ post.title }}</a></p>
+ </div>
+ </div>
+ {% endfor %}
+
+
+ <div class="row end-xs">
+ <div class="col">
+ <p><a href="{{site.baseurl}}/blog/">Más noticias</a></p>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ <!-- end right one-third block-->
+ </div>
+ </section>
+
+ <!-- END TWO THIRDS & ONE THIRD BLOCKS ROW -->
+
+ <!-- 3 ONE-THIRD BLOCKS ROW -->
+
+ <section class="container">
+ <div class="row">
+ <!-- left one-third block-->
+ <div class="left one-third col-lg-4 col-md-4 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Moneropedia</h2>
+ <p class="main-resources">¿Quieres ver las definiciones de términos y conceptos usados en Monero? Aquà encontrarás una lista alfabética de términos de los proyectos Monero y Kovri y sus significados.</p>
+ <p><a href="{{site.baseurl}}/resources/moneropedia/" class="btn-link btn-auto">Leer Moneropedia</a></p>
+ </div>
+ </div>
+ </div>
+ </div>
+ <!-- end left one-third block-->
+
+ <!-- center one-third block-->
+ <div class="center one-third col-lg-4 col-md-4 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>GuÃas de usuario</h2>
+ <p class="main-resources">GuÃas que describen varios procesos paso a paso, separadas por categorÃa. Cubren todo desde cómo crear una billetera, a cómo editar este mismo sitio web.</p>
+ <p><a href="{{site.baseurl}}/resources/user-guides/" class="btn-link btn-auto">Ver guÃas de usuario</a></p>
+ </div>
+ </div>
+ </div>
+ </div>
+ <!-- end center one-third block-->
+
+ <!-- right one-third block-->
+ <div class="right one-third col-lg-4 col-md-4 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Preguntas frecuentes</h2>
+ <p class="main-resources">Hemos escuchado muchas preguntas a lo largo de los años y hemos compilado un FAQ variado y detallado para tu conveniencia. No te preocupes, si tus preguntas no están aquÃ, puedes hacerlas por los canales de comunicación de la comunidad.</p>
+ <p><a href="{{site.baseurl}}/get-started/faq/" class="btn-link btn-auto">Ver respuestas</a></p>
+ </div>
+ </div>
+ </div>
+ </div>
+ <!-- end right one-third block-->
+ </div>
+ </section>
+
+ <!-- END 3 ONE-THIRD BLOCKS ROW -->
+</div>
\ No newline at end of file
diff --git a/_i18n/es/press-kit.md b/_i18n/es/press-kit.md
new file mode 100644
index 0000000000000000000000000000000000000000..b7bf3e2f69b59b0917517ac789fade3960736421
--- /dev/null
+++ b/_i18n/es/press-kit.md
@@ -0,0 +1,70 @@
+{% include untranslated.html %}
+<div class="text-center container description">
+<p>Here you'll find the Monero symbol and logo below. You can choose any size that you want, or download the .ai file to mess with the logo yourself. <strong>Note that the white background options have a white background under the Monero symbol ONLY, not as a background to the whole image.</strong> Lastly, you can download everything on this page in one zip file by clicking <a href="/press-kit/monero-press-kit.zip">here</a>.</p>
+</div>
+<section class="container">
+ <div class="row">
+ <div class="left half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Monero Symbol</h2>
+ </div>
+ </div>
+ <div class="row center-xs">
+ <img src="/press-kit/symbols/monero-symbol-480.png" alt="Monero Symbol" class="symbol-logo">
+ </div>
+ <div class="row center-xs press">
+ <div class="col-md-6">
+ <p>No background (PNG)</p>
+ <a href="/press-kit/symbols/monero-symbol-480.png">Small</a>
+ <a href="/press-kit/symbols/monero-symbol-800.png">Medium</a>
+ <a href="/press-kit/symbols/monero-symbol-1280.png">Large</a>
+ </div>
+ <div class="col-md-6">
+ <p>White background (PNG)</p>
+ <a href="/press-kit/symbols/monero-symbol-on-white-480.png">Small</a>
+ <a href="/press-kit/symbols/monero-symbol-on-white-800.png">Medium</a>
+ <a href="/press-kit/symbols/monero-symbol-on-white-1280.png">Large</a>
+ </div>
+ </div>
+ <div class="row center-xs press">
+ <a href="/press-kit/symbols/monero-symbol.ai" class="adi">Symbol .ai file</a>
+ </div>
+ </div>
+ </div>
+ <div class="right half col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Monero Logo</h2>
+ </div>
+ </div>
+ <div class="row center-xs">
+ <div class="col-xs-12">
+ <img src="/press-kit/logos/monero-logo-480.png" alt="Monero Logo" class="monero-symbol-logo">
+ </div>
+ </div>
+ <div class="row center-xs press">
+ <div class="col-md-6">
+ <p>No background (PNG)</p>
+ <a href="/press-kit/logos/monero-logo-480.png">Small</a>
+ <a href="/press-kit/logos/monero-logo-800.png">Medium</a>
+ <a href="/press-kit/logos/monero-logo-1280.png">Large</a>
+ </div>
+ <div class="col-md-6">
+ <p>White background (PNG)</p>
+ <a href="/press-kit/logos/monero-logo-symbol-on-white-480.png">Small</a>
+ <a href="/press-kit/logos/monero-logo-symbol-on-white-800.png">Medium</a>
+ <a href="/press-kit/logos/monero-logo-symbol-on-white-1280.png">Large</a>
+ </div>
+ </div>
+ <div class="row center-xs press">
+ <div class="col-xs-12">
+ <a href="/press-kit/logos/monero-logo.ai" class="adi">Logo .ai file</a>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+</section>
\ No newline at end of file
diff --git a/_i18n/es/resources/about.md b/_i18n/es/resources/about.md
new file mode 100644
index 0000000000000000000000000000000000000000..ada9fe4c2e35ecdd227e96ea05e6a02d193ec3e8
--- /dev/null
+++ b/_i18n/es/resources/about.md
@@ -0,0 +1,57 @@
+{% include untranslated.html %}
+<div class="about-monero">
+ <section class="container">
+ <div class="row">
+ <!-- left two-thirds block-->
+ <div class="full col-xs-12">
+ <div class="info-block text-adapt">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>A Brief History</h2>
+ </div>
+ </div>
+<div markdown="1">
+
+Monero was launched in April 2014. It was a fair, pre-announced launch of the CryptoNote reference code. There was no premine or instamine, and no portion of the block reward goes to development. See the original Bitcointalk thread here. The founder, thankful_for_today, proposed some controversial changes that the community disagreed with. A fallout ensued, and the Monero Core Team forked the project with the community following this new Core Team. This Core Team has provided oversight since.
+
+Monero has made several large improvements since launch. The blockchain was migrated to a different database structure to provide greater efficiency and flexibility, minimum ring signature sizes were set so that all transactions were private by mandate, and RingCT was implemented to hide the transaction amounts. Nearly all improvements have provided improvements to security or privacy, or they have facilitated use. Monero continues to develop with goals of privacy and security first, ease of use and efficiency second.
+
+</div>
+ </div>
+ </div>
+ <!-- end right one-third block-->
+ </div>
+ <div class="row">
+ <!-- left two-thirds block-->
+ <div class="full col-xs-12">
+ <div class="info-block text-adapt">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Our Values</h2>
+ </div>
+ </div>
+
+<div markdown="1">
+
+Monero is more than just a technology. It’s also what the technology stands for. Some of the important guiding philosophies are listed below.
+
+### Security
+
+Users must be able to trust Monero with their transactions, without risk of error or attack. Monero gives the full block reward to the miners, who are the most critical members of the network who provide this security. Transactions are cryptographically secure using the latest and most resilient encryption tools available.
+
+### Privacy
+
+Monero takes privacy seriously. Monero needs to be able to protect users in a court of law and, in extreme cases, from the death penalty. This level of privacy must be completely accessible to all users, whether they are technologically competent or have no idea how Monero works. A user needs to confidently trust Monero in a way that this person does not feel pressured into changing their spending habits for risk of others finding out.
+
+### Decentralization
+
+Monero is committed to providing the maximum amount of decentralization. With Monero, you do not have to trust anyone else on the network, and it is not run by any large group. An accessible “Proof of Work†algorithm makes it easy to mine Monero on normal computers, which makes it more difficult for someone to purchase a large amount of mining power. Nodes connect to each other with I2P to lower the risks of revealing sensitive transaction information and censorship (tba). Development decisions are extremely clear and open to public discussion. Developer meeting logs are published online in their entirety and visible by all.
+
+</div>
+ </div>
+ </div>
+
+
+ <!-- end right one-third block-->
+ </div>
+ </section>
\ No newline at end of file
diff --git a/_i18n/es/resources/developer-guides.md b/_i18n/es/resources/developer-guides.md
new file mode 100644
index 0000000000000000000000000000000000000000..d219203a1722b8a2d7eac5ab37c6cfeafecc110a
--- /dev/null
+++ b/_i18n/es/resources/developer-guides.md
@@ -0,0 +1,20 @@
+{% include untranslated.html %}
+<div class="guides">
+
+<div class="center-xs container description">
+<p class="text-center">Please note: the guides below are currently out of date, but are considered a good starting point for most calls. </p>
+</div>
+
+<section class="container full">
+ <div class="info-block">
+ <h2>RPC Documetation</h2>
+<div markdown="1">
+
+[Daemon RPC Documentation](daemon-rpc.html)
+[Wallet RPC Documentation](wallet-rpc.html)
+
+More coming soon...
+</div>
+ </div>
+</section>
+</div>
\ No newline at end of file
diff --git a/_i18n/es/resources/developer-guides/daemon-rpc.md b/_i18n/es/resources/developer-guides/daemon-rpc.md
new file mode 100644
index 0000000000000000000000000000000000000000..8f341d0debb7ebf2442e946f529a9eb0309d2fed
--- /dev/null
+++ b/_i18n/es/resources/developer-guides/daemon-rpc.md
@@ -0,0 +1,832 @@
+{% include untranslated.html %}
+## Introduction
+
+This is a list of the monerod daemon RPC calls, their inputs and outputs, and examples of each.
+
+Many RPC calls use the daemon's JSON RPC interface while others use their own interfaces, as demonstrated below.
+
+Note: "atomic units" refer to the smallest fraction of 1 XMR according to the monerod implementation. **1 XMR = 1e12 atomic units.**
+
+### [JSON RPC Methods](#json-rpc-methods):
+
+* [getblockcount](#getblockcount)
+* [on_getblockhash](#on_getblockhash)
+* [getblocktemplate](#getblocktemplate)
+* [submitblock](#submitblock)
+* [getlastblockheader](#getlastblockheader)
+* [getblockheaderbyhash](#getblockheaderbyhash)
+* [getblockheaderbyheight](#getblockheaderbyheight)
+* [getblock](#getblock)
+* [get_connections](#get_connections)
+* [get_info](#get_info)
+* [hard_fork_info](#hard_fork_info)
+* [setbans](#setbans)
+* [getbans](#getbans)
+
+### [Other RPC Methods](#other-daemon-rpc-calls):
+
+* [/getheight](#getheight)
+* [/gettransactions](#gettransactions)
+* [/is_key_image_spent](#is_key_image_spent)
+* [/sendrawtransaction](#sendrawtransaction)
+* [/get_transaction_pool](#get_transaction_pool)
+* [/stop_daemon](#stop_daemon)
+
+
+---
+
+## JSON RPC Methods
+
+The majority of monerod RPC calls use the daemon's `json_rpc` interface to request various bits of information. These methods all follow a similar structure, for example:
+
+```
+IP=127.0.0.1
+PORT=18081
+METHOD='getblockheaderbyheight'
+PARAMS='{"height":912345}'
+curl \
+ -X POST http://$IP:$PORT/json_rpc \
+ -d '{"jsonrpc":"2.0","id":"0","method":"'$METHOD'","params":'$PARAMS'}' \
+ -H 'Content-Type: application/json'
+```
+
+Some methods include parameters, while others do not. Examples of each JSON RPC method follow.
+
+### **getblockcount**
+
+Look up how many blocks are in the longest chain known to the node.
+
+Inputs: *None*.
+
+Outputs:
+
+* *count* - unsigned int; Number of blocks in longest chain seen by the node.
+* *status* - string; General RPC error code. "OK" means everything looks good.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getblockcount"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "count": 993163,
+ "status": "OK"
+ }
+}
+```
+
+
+### **on_getblockhash**
+
+Look up a block's hash by its height.
+
+Inputs:
+
+* block height (int array of length 1)
+
+Outputs:
+
+* block hash (string)
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"on_getblockhash","params":[912345]}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": "e22cf75f39ae720e8b71b3d120a5ac03f0db50bba6379e2850975b4859190bc6"
+}
+```
+
+
+### **getblocktemplate**
+
+Inputs:
+
+* *wallet_address* - string; Address of wallet to receive coinbase transactions if block is successfully mined.
+* *reserve_size* - unsigned int; Reserve size.
+
+Outputs:
+
+* *blocktemplate_blob* - string; Blob on which to try to mine a new block.
+* *difficulty* - unsigned int; Difficulty of next block.
+* *height* - unsigned int; Height on which to mine.
+* *prev_hash* - string; Hash of the most recent block on which to mine the next block.
+* *reserved_offset* - unsigned int; Reserved offset.
+* *status* - string; General RPC error code. "OK" means everything looks good.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getblocktemplate","params":{"wallet_address":"44GBHzv6ZyQdJkjqZje6KLZ3xSyN1hBSFAnLP6EAqJtCRVzMzZmeXTC2AHKDS9aEDTRKmo6a6o9r9j86pYfhCWDkKjbtcns","reserve_size":60}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "blocktemplate_blob": "01029af88cb70568b84a11dc9406ace9e635918ca03b008f7728b9726b327c1b482a98d81ed83000000000018bd03c01ffcfcf3c0493d7cec7020278dfc296544f139394e5e045fcda1ba2cca5b69b39c9ddc90b7e0de859fdebdc80e8eda1ba01029c5d518ce3cc4de26364059eadc8220a3f52edabdaf025a9bff4eec8b6b50e3d8080dd9da417021e642d07a8c33fbe497054cfea9c760ab4068d31532ff0fbb543a7856a9b78ee80c0f9decfae01023ef3a7182cb0c260732e7828606052a0645d3686d7a03ce3da091dbb2b75e5955f01ad2af83bce0d823bf3dbbed01ab219250eb36098c62cbb6aa2976936848bae53023c00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001f12d7c87346d6b84e17680082d9b4a1d84e36dd01bd2c7f3b3893478a8d88fb3",
+ "difficulty": 982540729,
+ "height": 993231,
+ "prev_hash": "68b84a11dc9406ace9e635918ca03b008f7728b9726b327c1b482a98d81ed830",
+ "reserved_offset": 246,
+ "status": "OK"
+ }
+}
+```
+
+
+### **submitblock**
+
+Submit a mined block to the network.
+
+Inputs:
+
+* Block blob data - string
+
+Outputs:
+
+* *status* - string; Block submit status.
+
+
+### **getlastblockheader**
+
+Block header information for the most recent block is easily retrieved with this method. No inputs are needed.
+
+Inputs: *None*.
+
+Outputs:
+
+* *block_header* - A structure containing block header information.
+ * *depth* - unsigned int; The number of blocks succeeding this block on the blockchain. A larger number means an older block.
+ * *difficulty* - unsigned int; The strength of the Monero network based on mining power.
+ * *hash* - string; The hash of this block.
+ * *height* - unsigned int; The number of blocks preceding this block on the blockchain.
+ * *major_version* - unsigned int; The major version of the monero protocol at this block height.
+ * *minor_version* - unsigned int; The minor version of the monero protocol at this block height.
+ * *nonce* - unsigned int; a cryptographic random one-time number used in mining a Monero block.
+ * *orphan_status* - boolean; Usually `false`. If `true`, this block is not part of the longest chain.
+ * *prev_hash* - string; The hash of the block immediately preceding this block in the chain.
+ * *reward* - unsigned int; The amount of new atomic units generated in this block and rewarded to the miner. Note: 1 XMR = 1e12 atomic units.
+ * *timestamp* - unsigned int; The time the block was recorded into the blockchain.
+* *status* - string; General RPC error code. "OK" means everything looks good.
+
+In this example, the most recent block (990793 at the time) is returned:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getlastblockheader"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "block_header": {
+ "depth": 0,
+ "difficulty": 746963928,
+ "hash": "ac0f1e226268d45c99a16202fdcb730d8f7b36ea5e5b4a565b1ba1a8fc252eb0",
+ "height": 990793,
+ "major_version": 1,
+ "minor_version": 1,
+ "nonce": 1550,
+ "orphan_status": false,
+ "prev_hash": "386575e3b0b004ed8d458dbd31bff0fe37b280339937f971e06df33f8589b75c",
+ "reward": 6856609225169,
+ "timestamp": 1457589942
+ },
+ "status": "OK"
+ }
+}
+```
+
+
+### **getblockheaderbyhash**
+
+Block header information can be retrieved using either a block's hash or height. This method includes a block's hash as an input parameter to retrieve basic information about the block.
+
+Inputs:
+
+* *hash* - string; The block's sha256 hash.
+
+Outputs:
+
+* *block_header* - A structure containing block header information. See [getlastblockheader](#getlastblockheader).
+
+In this example, block 912345 is looked up by its hash:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getblockheaderbyhash","params":{"hash":"e22cf75f39ae720e8b71b3d120a5ac03f0db50bba6379e2850975b4859190bc6"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "block_header": {
+ "depth": 78376,
+ "difficulty": 815625611,
+ "hash": "e22cf75f39ae720e8b71b3d120a5ac03f0db50bba6379e2850975b4859190bc6",
+ "height": 912345,
+ "major_version": 1,
+ "minor_version": 2,
+ "nonce": 1646,
+ "orphan_status": false,
+ "prev_hash": "b61c58b2e0be53fad5ef9d9731a55e8a81d972b8d90ed07c04fd37ca6403ff78",
+ "reward": 7388968946286,
+ "timestamp": 1452793716
+ },
+ "status": "OK"
+ }
+}
+```
+
+
+### **getblockheaderbyheight**
+
+Similar to `getblockheaderbyhash` above, this method includes a block's height as an input parameter to retrieve basic information about the block.
+
+Inputs:
+
+* *height* - unsigned int; The block's height.
+
+Outputs:
+
+* *block_header* - A structure containing block header information. See [getlastblockheader](#getlastblockheader).
+
+In this example, block 912345 is looked up by its height (notice that the returned information is the save as in the previous example):
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getblockheaderbyheight","params":{"height":912345}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "block_header": {
+ "depth": 78376,
+ "difficulty": 815625611,
+ "hash": "e22cf75f39ae720e8b71b3d120a5ac03f0db50bba6379e2850975b4859190bc6",
+ "height": 912345,
+ "major_version": 1,
+ "minor_version": 2,
+ "nonce": 1646,
+ "orphan_status": false,
+ "prev_hash": "b61c58b2e0be53fad5ef9d9731a55e8a81d972b8d90ed07c04fd37ca6403ff78",
+ "reward": 7388968946286,
+ "timestamp": 1452793716
+ },
+ "status": "OK"
+ }
+}
+```
+
+
+### **getblock**
+
+Full block information can be retrieved by either block height or hash, like with the above block header calls. For full block information, both lookups use the same method, but with different input parameters.
+
+Inputs (pick one of the following):
+
+* *height* - unsigned int; The block's height.
+* *hash* - string; The block's hash.
+
+Outputs:
+
+* *blob* - string; Hexadecimal blob of block information.
+* *block_header* - A structure containing block header information. See [getlastblockheader](#getlastblockheader).
+* *json* - json string; JSON formatted block details:
+ * *major_version* - Same as in block header.
+ * *minor_version* - Same as in block header.
+ * *timestamp* - Same as in block header.
+ * *prev_id* - Same as `prev_hash` in block header.
+ * *nonce* - Same as in block header.
+ * *miner_tx* - Miner transaction information
+ * *version* - Transaction version number.
+ * *unlock_time* - The block height when the coinbase transaction becomes spendable.
+ * *vin* - List of transaction inputs:
+ * *gen* - Miner txs are coinbase txs, or "gen".
+ * *height* - This block height, a.k.a. when the coinbase is generated.
+ * *vout* - List of transaction outputs. Each output contains:
+ * *amount* - The amount of the output, in atomic units.
+ * *target* -
+ * *key* -
+ * *extra* - Usually called the "transaction ID" but can be used to include any random 32 byte/64 character hex string.
+ * *signatures* - Contain signatures of tx signers. Coinbased txs do not have signatures.
+ * *tx_hashes* - List of hashes of non-coinbase transactions in the block. If there are no other transactions, this will be an empty list.
+* *status* - string; General RPC error code. "OK" means everything looks good.
+
+**Look up by height:**
+
+In the following example, block 912345 is looked up by its height. Note that block 912345 does not have any non-coinbase transactions. (See the next example for a block with extra transactions):
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getblock","params":{"height":912345}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "blob": "...",
+ "block_header": {
+ "depth": 80694,
+ "difficulty": 815625611,
+ "hash": "e22cf75f39ae720e8b71b3d120a5ac03f0db50bba6379e2850975b4859190bc6",
+ "height": 912345,
+ "major_version": 1,
+ "minor_version": 2,
+ "nonce": 1646,
+ "orphan_status": false,
+ "prev_hash": "b61c58b2e0be53fad5ef9d9731a55e8a81d972b8d90ed07c04fd37ca6403ff78",
+ "reward": 7388968946286,
+ "timestamp": 1452793716
+ },
+ "json": "{\n \"major_version\": 1, \n \"minor_version\": 2, \n \"timestamp\": 1452793716, \n \"prev_id\": \"b61c58b2e0be53fad5ef9d9731a55e8a81d972b8d90ed07c04fd37ca6403ff78\", \n \"nonce\": 1646, \n \"miner_tx\": {\n \"version\": 1, \n \"unlock_time\": 912405, \n \"vin\": [ {\n \"gen\": {\n \"height\": 912345\n }\n }\n ], \n \"vout\": [ {\n \"amount\": 8968946286, \n \"target\": {\n \"key\": \"378b043c1724c92c69d923d266fe86477d3a5ddd21145062e148c64c57677008\"\n }\n }, {\n \"amount\": 80000000000, \n \"target\": {\n \"key\": \"73733cbd6e6218bda671596462a4b062f95cfe5e1dbb5b990dacb30e827d02f2\"\n }\n }, {\n \"amount\": 300000000000, \n \"target\": {\n \"key\": \"47a5dab669770da69a860acde21616a119818e1a489bb3c4b1b6b3c50547bc0c\"\n }\n }, {\n \"amount\": 7000000000000, \n \"target\": {\n \"key\": \"1f7e4762b8b755e3e3c72b8610cc87b9bc25d1f0a87c0c816ebb952e4f8aff3d\"\n }\n }\n ], \n \"extra\": [ 1, 253, 10, 119, 137, 87, 244, 243, 16, 58, 131, 138, 253, 164, 136, 195, 205, 173, 242, 105, 123, 61, 52, 173, 113, 35, 66, 130, 178, 250, 217, 16, 14, 2, 8, 0, 0, 0, 11, 223, 194, 193, 108\n ], \n \"signatures\": [ ]\n }, \n \"tx_hashes\": [ ]\n}",
+ "status": "OK"
+ }
+}
+```
+
+**Look up by hash:**
+
+In the following example, block 993056 is looked up by its hash. Note that block 993056 has 3 non-coinbase transactions:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getblock","params":{"hash":"510ee3c4e14330a7b96e883c323a60ebd1b5556ac1262d0bc03c24a3b785516f"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "blob": "...",
+ "block_header": {
+ "depth": 12,
+ "difficulty": 964985344,
+ "hash": "510ee3c4e14330a7b96e883c323a60ebd1b5556ac1262d0bc03c24a3b785516f",
+ "height": 993056,
+ "major_version": 1,
+ "minor_version": 2,
+ "nonce": 2036,
+ "orphan_status": false,
+ "prev_hash": "0ea4af6547c05c965afc8df6d31509ff3105dc7ae6b10172521d77e09711fd6d",
+ "reward": 6932043647005,
+ "timestamp": 1457720227
+ },
+ "json": "{\n \"major_version\": 1, \n \"minor_version\": 2, \n \"timestamp\": 1457720227, \n \"prev_id\": \"0ea4af6547c05c965afc8df6d31509ff3105dc7ae6b10172521d77e09711fd6d\", \n \"nonce\": 2036, \n \"miner_tx\": {\n \"version\": 1, \n \"unlock_time\": 993116, \n \"vin\": [ {\n \"gen\": {\n \"height\": 993056\n }\n }\n ], \n \"vout\": [ {\n \"amount\": 2043647005, \n \"target\": {\n \"key\": \"59e9d685b3484886bc7b47c133e6099ecdf212d5eaa16ce19cd58e8c3c1e590a\"\n }\n }, {\n \"amount\": 30000000000, \n \"target\": {\n \"key\": \"4c5e2f542d25513c46b9e3b7d40140a22d0ae5314bfcae492ad9f56fff8185f0\"\n }\n }, {\n \"amount\": 900000000000, \n \"target\": {\n \"key\": \"13dd8ffdac9e6a2f71e327dad65328198dc879a492d145eae72677c0703a3515\"\n }\n }, {\n \"amount\": 6000000000000, \n \"target\": {\n \"key\": \"62bda00341681dccbc066757862da593734395745bdfe1fdc89b5948c86a5d4c\"\n }\n }\n ], \n \"extra\": [ 1, 182, 145, 133, 28, 240, 87, 185, 195, 2, 163, 219, 202, 135, 158, 28, 186, 76, 196, 80, 97, 202, 85, 170, 166, 224, 60, 220, 103, 171, 158, 69, 80, 2, 8, 0, 0, 0, 12, 97, 127, 223, 22\n ], \n \"signatures\": [ ]\n }, \n \"tx_hashes\": [ \"79c6b9f00db027bde151705aafe85c495883aae2597d5cb8e1adb2e0f3ae1d07\", \"d715db73331abc3ec588ef07c7bb195786a4724b08dff431b51ffa32a4ce899b\", \"b197066426c0ed89f0b431fe171f7fd62bc95dd29943daa7cf3585cf1fdfc99d\"\n ]\n}",
+ "status": "OK",
+ "tx_hashes": ["79c6b9f00db027bde151705aafe85c495883aae2597d5cb8e1adb2e0f3ae1d07","d715db73331abc3ec588ef07c7bb195786a4724b08dff431b51ffa32a4ce899b","b197066426c0ed89f0b431fe171f7fd62bc95dd29943daa7cf3585cf1fdfc99d"]
+ }
+}
+```
+
+
+### **get_connections**
+
+Retrieve information about incoming and outgoing connections to your node.
+
+Inputs: *None*.
+
+Outputs:
+
+* *connections* - List of all connections and their info:
+ * *avg_download* - unsigned int; Average bytes of data downloaded by node.
+ * *avg_upload* - unsigned int; Average bytes of data uploaded by node.
+ * *current_download* - unsigned int; Current bytes downloaded by node.
+ * *current_upload* - unsigned int; Current bytes uploaded by node.
+ * *incoming* - boolean; Is the node getting information from your node?
+ * *ip* - string; The node's IP address.
+ * *live_time* - unsigned int
+ * *local_ip* - boolean
+ * *localhost* - boolean
+ * *peer_id* - string; The node's ID on the network.
+ * *port* - string; The port that the node is using to connect to the network.
+ * *recv_count* - unsigned int
+ * *recv_idle_time* - unsigned int
+ * *send_count* - unsigned int
+ * *send_idle_time* - unsigned int
+ * *state* - string
+
+Following is an example of `get_connections` and it's return:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_connections"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "connections": [{
+ "avg_download": 0,
+ "avg_upload": 0,
+ "current_download": 0,
+ "current_upload": 0,
+ "incoming": false,
+ "ip": "76.173.170.133",
+ "live_time": 1865,
+ "local_ip": false,
+ "localhost": false,
+ "peer_id": "3bfe29d6b1aa7c4c",
+ "port": "18080",
+ "recv_count": 116396,
+ "recv_idle_time": 23,
+ "send_count": 176893,
+ "send_idle_time": 1457726610,
+ "state": "state_normal"
+ },{
+ ...
+ }],
+ "status": "OK"
+ }
+}
+```
+
+
+### **get_info**
+
+Retrieve general information about the state of your node and the network.
+
+Inputs: *None*.
+
+Outputs:
+
+* *alt_blocks_count* - unsigned int; Number of alternative blocks to main chain.
+* *difficulty* - unsigned int; Network difficulty (analogous to the strength of the network)
+* *grey_peerlist_size* - unsigned int; Grey Peerlist Size
+* *height* - unsigned int; Current length of longest chain known to daemon.
+* *incoming_connections_count* - unsigned int; Number of peers connected to and pulling from your node.
+* *outgoing_connections_count* - unsigned int; Number of peers that you are connected to and getting information from.
+* *status* - string; General RPC error code. "OK" means everything looks good.
+* *target* - unsigned int; Current target for next proof of work.
+* *target_height* - unsigned int; The height of the next block in the chain.
+* *testnet* - boolean; States if the node is on the testnet (true) or mainnet (false).
+* *top_block_hash* - string; Hash of the highest block in the chain.
+* *tx_count* - unsigned int; Total number of non-coinbase transaction in the chain.
+* *tx_pool_size* - unsigned int; Number of transactions that have been broadcast but not included in a block.
+* *white_peerlist_size* - unsigned int; White Peerlist Size
+
+Following is an example `get_info` call and its return:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_info"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "alt_blocks_count": 5,
+ "difficulty": 972165250,
+ "grey_peerlist_size": 2280,
+ "height": 993145,
+ "incoming_connections_count": 0,
+ "outgoing_connections_count": 8,
+ "status": "OK",
+ "target": 60,
+ "target_height": 993137,
+ "testnet": false,
+ "top_block_hash": "",
+ "tx_count": 564287,
+ "tx_pool_size": 45,
+ "white_peerlist_size": 529
+ }
+}
+```
+
+
+### **hard_fork_info**
+
+Look up information regarding hard fork voting and readiness.
+
+Inputs: *None*.
+
+Outputs:
+
+* *earliest_height* - unsigned int; Block height at which hard fork would be enabled if voted in.
+* *enabled* - boolean; Tells if hard fork is enforced.
+* *state* - unsigned int; Current hard fork state: 0 (There is likely a hard fork), 1 (An update is needed to fork properly), or 2 (Everything looks good).
+* *status* - string; General RPC error code. "OK" means everything looks good.
+* *threshold* - unsigned int; Minimum percent of votes to trigger hard fork. Default is 80.
+* *version* - unsigned int; The major block version for the fork.
+* *votes* - unsigned int; Number of votes towards hard fork.
+* *voting* - unsigned int; Hard fork voting status.
+* *window* - unsigned int; Number of blocks over which current votes are cast. Default is 10080 blocks.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"hard_fork_info"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "earliest_height": 1009827,
+ "enabled": false,
+ "state": 2,
+ "status": "OK",
+ "threshold": 0,
+ "version": 1,
+ "votes": 7277,
+ "voting": 2,
+ "window": 10080
+ }
+}
+```
+
+
+### **setbans**
+
+Ban another node by IP.
+
+Inputs:
+
+* *bans* - A list of nodes to ban:
+ * *ip* - unsigned int; IP address to ban, in Int format.
+ * *ban* - boolean; Set `true` to ban.
+ * *seconds* - unsigned int; Number of seconds to ban node.
+
+Outputs:
+
+* *status* - string; General RPC error code. "OK" means everything looks good.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"setbans","params":{"bans":[{"ip":838969536,"ban":true,"seconds":30}]}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "status": "OK"
+ }
+}
+```
+
+
+### **getbans**
+
+Inputs: *None*.
+
+Outputs:
+
+* *bans* - List of banned nodes:
+ * *ip* - unsigned int; Banned IP address, in Int format.
+ * *seconds* - unsigned int; Local Unix time that IP is banned until.
+* *status* - string; General RPC error code. "OK" means everything looks good.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getbans"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "bans": [{
+ "ip": 838969536,
+ "seconds": 1457748792
+ }],
+ "status": "OK"
+ }
+}
+```
+
+
+---
+
+## Other Daemon RPC Calls
+
+Not all daemon RPC calls use the JSON_RPC interface. This section gives examples of these calls.
+
+The data structure for these calls is different than the JSON RPC calls. Whereas the JSON RPC methods were called using the `/json_rpc` extension and specifying a method, these methods are called at their own extensions. For example:
+
+ IP=127.0.0.1
+ PORT=18081
+ METHOD='gettransactions'
+ PARAMS='{"txs_hashes":["d6e48158472848e6687173a91ae6eebfa3e1d778e65252ee99d7515d63090408"]}'
+ curl \
+ -X POST http://$IP:$PORT/$METHOD \
+ -d $PARAMS \
+ -H 'Content-Type: application/json'
+
+Note: It is recommended to use JSON RPC where such alternatives exist, rather than the following methods. For example, the recommended way to get a node's height is via the JSON RPC methods [get_info](#getinfo) or [getlastblockheader](#getlastblockheader), rather than [getheight](#getheight) below.
+
+
+### **/getheight**
+
+Get the node's current height.
+
+Inputs: *None*.
+
+Outputs:
+
+* *height* - unsigned int; Current length of longest chain known to daemon.
+
+```
+$ curl -X POST http://127.0.0.1:18081/getheight -H 'Content-Type: application/json'
+
+{
+ "height": 993488,
+ "status": "OK"
+}
+```
+
+
+### **/gettransactions**
+
+Look up one or more transactions by hash.
+
+Inputs:
+
+* *txs_hashes* - string list; List of transaction hashes to look up.
+* *decode_as_json* - boolean; Optional. If set `true`, the returned transaction information will be decoded rather than binary.
+
+Outputs:
+
+* *status* - General RPC error code. "OK" means everything looks good.
+* *txs_as_hex* - string; Full transaction information as a hex string.
+* *txs_as_json* - json string; (Optional - returned if set in inputs.) List of transaction info:
+ * *version* - Transaction version
+ * *unlock_time* - If not 0, this tells when a transaction output is spendable.
+ * *vin* - List of inputs into transaction:
+ * *key* - The public key of the previous output spent in this transaction.
+ * *amount* - The amount of the input, in atomic units.
+ * *key_offsets* - A list of integer offets to the input.
+ * *k_image* - The key image for the given input
+ * *vout* - List of outputs from transaction:
+ * *amount* - Amount of transaction output, in atomic units.
+ * *target* - Output destination information:
+ * *key* - The stealth public key of the receiver. Whoever owns the private key associated with this key controls this transaction output.
+ * *extra* - Usually called the "payment ID" but can be used to include any random 32 bytes.
+ * *signatures* - List of ignatures used in ring signature to hide the true origin of the transaction.
+Example 1: Return transaction information in binary format.
+
+```
+$ curl -X POST http://127.0.0.1:18081/gettransactions -d '{"txs_hashes":["d6e48158472848e6687173a91ae6eebfa3e1d778e65252ee99d7515d63090408"]}' -H 'Content-Type: application/json'
+
+{
+ "status": "OK",
+ "txs_as_hex": ["..."]
+}
+```
+
+
+Example 2: Decode returned transaction information in JSON format. Note: the "vout" list has been truncated in the displayed return for space considerations.
+
+```
+$ curl -X POST http://127.0.0.1:18081/gettransactions -d '{"txs_hashes":["d6e48158472848e6687173a91ae6eebfa3e1d778e65252ee99d7515d63090408"],"decode_as_json":true}' -H 'Content-Type: application/json'
+
+{
+ "status": "OK",
+ "txs_as_hex": ["..."],
+ "txs_as_json": ["{\n \"version\": 1, \n \"unlock_time\": 0, \n \"vin\": [ {\n \"key\": {\n \"amount\": 70000000, \n \"key_offsets\": [ 35952\n ], \n \"k_image\": \"d16908468dff9438a9814fe96bdaa575f06fe8da85772b72e54926428712293d\"\n }\n }, {\n \"key\": {\n \"amount\": 400000000000000, \n \"key_offsets\": [ 6830\n ], \n \"k_image\": \"c7a7024b763df1181ae6fe821b70669735e38a68162ac02362e33acbe829b605\"\n }\n }\n ], \n \"vout\": [ {\n \"amount\": 50000, \n \"target\": {\n \"key\": \"f6be43f7be4f06adcb1d06f4a07c637c7359e009cf3e57bb32b8c9ea636509c3\"\n }\n }, {\n \"amount\": 200000, \n \"target\": {\n \"key\": \"b0a7a8e32f2b5302552bcd8d85112c62838b1f56cccd844eb9b63e0a732d0353\"\n }\n }, ... \n ], \n \"extra\": [ 1, 225, 240, 98, 34, 169, 73, 47, 237, 117, 192, 30, 192, 60, 155, 47, 4, 115, 20, 21, 11, 13, 252, 219, 129, 13, 174, 37, 36, 78, 191, 141, 109\n ], \n \"signatures\": [ \"e6a3be8003d481d2855c8127f56871de3d28a4fb52385b999eb986c831c5cc08361c126b0db24a21b6c4299b438ee2be201d44d57a371230b9cd04395ab8c400\", \"8309851abaf2cf2a7091e0cdb9c83704fa7d68838a7a8ef8c178bb55a1e93a038dd18bb4a7549dc056b7a70e037cabd80911a03f427e36f712756d4c00f38f0b\"]\n}"]
+}
+```
+
+
+### **/is_key_image_spent**
+
+Check if outputs have been spent using the key image associated with the output.
+
+Inputs:
+
+* *key_images* - string list; List of key image hex strings to check.
+
+Outputs:
+
+* *spent_status* - unsigned int list; List of statuses for each image checked. Statuses are follows: 0 = unspent, 1 = spent in blockchain, 2 = spent in transaction pool
+* *status* - string; General RPC error code. "OK" means everything looks good.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/is_key_image_spent -d '{"key_images":["8d1bd8181bf7d857bdb281e0153d84cd55a3fcaa57c3e570f4a49f935850b5e3","7319134bfc50668251f5b899c66b005805ee255c136f0e1cecbb0f3a912e09d4"]}' -H 'Content-Type: application/json'
+
+{
+ "spent_status": [1,2],
+ "status": "OK"
+}
+```
+
+
+### **/sendrawtransaction**
+
+Broadcast a raw transaction to the network.
+
+Inputs:
+
+* *tx_as_hex* - string; Full transaction information as hexidecimal string.
+
+Outputs:
+
+* *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.):
+
+
+```
+$ curl -X POST http://127.0.0.1:18081/sendrawtransaction -d '{"tx_as_hex":"de6a3..."}' -H 'Content-Type: application/json'
+```
+
+
+### **/get_transaction_pool**
+
+Show information about valid transactions seen by the node but not yet mined into a block, as well as spent key image information in the node's memory.
+
+Inputs: *None*.
+
+Outputs:
+
+* *spent_key_images* - List of spent output key images:
+ * *id_hash* - string; Key image ID hash.
+ * *txs_hashes* - string list; Key image transaction hashes.
+* *status* - string; General RPC error code. "OK" means everything looks good.
+* *transactions* - List of transactions in the mempool that have not been included in a block:
+ * *blob_size* - unsigned int; The size of the full transaction blob.
+ * *fee* - unsigned int; The amount of the mining fee included in the transaction, in atomic units.
+ * *id_hash* - string; The transaction ID hash.
+ * *kept_by_block* - boolean; We do not accept transactions that timed out before, unless set `true`.
+ * *last_failed_height* - unsigned int; If the transaction has previously timed out, this tells at what height that occured.
+ * *last_failed_id_hash* - string; Like the previous, this tells the previous transaction ID hash.
+ * *max_used_block_height* - unsigned int; Tells the height of the most recent block with an output used in this transaction.
+ * *max_used_block_hash* - string; Tells the hash of the most recent block with an output used in this transaction.
+ * *receive_time* - unsigned int; The Unix time that the transaction was first seen on the network by the node.
+ * *tx_json* - json string; JSON structure of all information in the transaction:
+ * *version* - Transaction version
+ * *unlock_time* - If not 0, this tells when a transaction output is spendable.
+ * *vin* - List of inputs into transaction:
+ * *key* - The public key of the previous output spent in this transaction.
+ * *amount* - The amount of the input, in atomic units.
+ * *key_offsets* - A list of integer offets to the input.
+ * *k_image* - The key image for the given input
+ * *vout* - List of outputs from transaction:
+ * *amount* - Amount of transaction output, in atomic units.
+ * *target* - Output destination information:
+ * *key* - The stealth public key of the receiver. Whoever owns the private key associated with this key controls this transaction output.
+ * *extra* - Usually called the "transaction ID" but can be used to include any random 32 bytes.
+ * *signatures* - List of ignatures used in ring signature to hide the true origin of the transaction.
+
+Example (Note: Some lists in the returned information have been truncated for display reasons):
+
+```
+$ curl -X POST http://127.0.0.1:18081/get_transaction_pool -H 'Content-Type: application/json'
+
+{
+ "spent_key_images": [{
+ "id_hash": "1edb9ecc39602040282d326070ad22cb473c952c0d6280c9c4c3b853fb34f3bc",
+ "txs_hashes": ["409911b2be02e3f0e930b326c67ab9e74675885ce23d71bb3bd28b62bc3e7803"]
+ },{
+ "id_hash": "4adb4bb63b3397027340ca4e6c45f4ce2147dfb3a4e0fafdec18834ae594a05e",
+ "txs_hashes": ["946f1f4c52e3426a41959c93b60078f314813bc4bdebcf69b8ee11d593b2bd14"]
+ },
+ ...],
+ "status": "OK",
+ "transactions": [{
+ "blob_size": 25761,
+ "fee": 290000000000,
+ "id_hash": "11d4cff23e610fac6a2b89187ad61d429a5e226652693dcac5d83d506eb92b96",
+ "kept_by_block": false,
+ "last_failed_height": 0,
+ "last_failed_id_hash": "0000000000000000000000000000000000000000000000000000000000000000",
+ "max_used_block_height": 954508,
+ "max_used_block_id_hash": "03f96b374778bc059e47b96e2beec2e6d4d9e0ad39afeabdbcd77e1bd5a62f81",
+ "receive_time": 1457676127,
+ "tx_json": "{\n \"version\": 1, \n \"unlock_time\": 0, \n \"vin\": [ {\n \"key\": {\n \"amount\": 70000000000, \n \"key_offsets\": [ 63408, 18978, 78357, 16560\n ], \n \"k_image\": \"7319134bfc50668251f5b899c66b005805ee255c136f0e1cecbb0f3a912e09d4\"\n }\n }, ... ], \n \"vout\": [ {\n \"amount\": 80000000000, \n \"target\": {\n \"key\": \"094e6a1b187385533665f89db741149f42d95fdc50bdd2a2384bcd1dc5209c55\"\n }\n }, ... ], \n \"extra\": [ 2, 33, 0, 15, 56, 190, 21, 169, 77, 13, 182, 209, 51, 35, 54, 96, 89, 237, 96, 23, 24, 107, 240, 79, 40, 86, 64, 68, 45, 166, 119, 192, 17, 225, 23, 1, 31, 159, 145, 15, 173, 255, 165, 192, 55, 84, 127, 154, 163, 25, 85, 204, 212, 127, 147, 133, 118, 218, 166, 52, 78, 188, 131, 235, 9, 159, 105, 158\n ], \n \"signatures\": [ \"966e5a67fbdbf72d7dc0364b705121a58e0ced7e2ab45747b6b154c05a1afe04fac4aac7f64faa2dc6dd4d51b8277f11e2f2ec7729fac225088befe3b8399c0b71a4cb55b9d0e20f93d305c78cebceff1bcfcfaf225428dfcfaaec630c88720ab65bf5d3399dd1ac82ea0ecf308b3f80d9780af7742fb157692cd60515a7e2086878f082117fa80fff3d257de7d3a2e9cc8b3472ef4a5e545d90e1159523a60f38d16cece783579627124776813334bdb2a2df4171ef1fa12bf415da338ce5085c01e7a715638ef5505aebec06a0625aaa72d13839838f7d4f981673c8f05f08408e8b372f900af7227c49cfb1e1febab6c07dd42b7c26f921cf010832841205\", ... ]\n}"
+ },
+ ...]
+}
+```
+
+
+### **/stop_daemon**
+
+Send a command to the daemon to safely disconnect and shut down.
+
+Inputs: *None*.
+
+Outputs:
+
+* *status* - string; General RPC error code. "OK" means everything looks good.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/stop_daemon -H 'Content-Type: application/json'
+
+{
+ "status": "OK"
+}
+```
\ No newline at end of file
diff --git a/_i18n/es/resources/developer-guides/wallet-rpc.md b/_i18n/es/resources/developer-guides/wallet-rpc.md
new file mode 100644
index 0000000000000000000000000000000000000000..59776a56a1b6a81da0200b8a80534bca9249fe61
--- /dev/null
+++ b/_i18n/es/resources/developer-guides/wallet-rpc.md
@@ -0,0 +1,1216 @@
+{% include untranslated.html %}
+## Introduction
+
+This is a list of the monero-wallet-rpc calls, their inputs and outputs, and examples of each. The program monero-wallet-rpc replaced the rpc interface that was in simplewallet and then monero-wallet-cli.
+
+All monero-wallet-rpc methods use the same JSON RPC interface. For example:
+
+```
+IP=127.0.0.1
+PORT=18082
+METHOD="make_integrated_address"
+PARAMS="{\"payment_id\":\"1234567890123456789012345678900012345678901234567890123456789000\"}"
+curl \
+ -X POST http://$IP:$PORT/json_rpc \
+ -d '{"jsonrpc":"2.0","id":"0","method":"'$METHOD'","params":'"$PARAMS"'}' \
+ -H 'Content-Type: application/json'
+```
+
+If the monero-wallet-rpc was executed with the `--rpc-login` argument as `username:password`, then follow this example:
+
+```
+IP=127.0.0.1
+PORT=18082
+METHOD="make_integrated_address"
+PARAMS="{\"payment_id\":\"1234567890123456789012345678900012345678901234567890123456789000\"}"
+curl \
+ -u username:password --digest \
+ -X POST http://$IP:$PORT/json_rpc \
+ -d '{"jsonrpc":"2.0","id":"0","method":"'$METHOD'","params":'"$PARAMS"'}' \
+ -H 'Content-Type: application/json'
+```
+
+Note: "atomic units" refer to the smallest fraction of 1 XMR according to the monerod implementation. **1 XMR = 1e12 atomic units.**
+
+### Index of JSON RPC Methods:
+
+* [getbalance](#getbalance)
+* [getaddress](#getaddress)
+* [getheight](#getheight)
+* [transfer](#transfer)
+* [transfer_split](#transfer_split)
+* [sweep_dust](#sweep_dust)
+* [sweep_all](#sweep_all)
+* [store](#store)
+* [get_payments](#get_payments)
+* [get_bulk_payments](#get_bulk_payments)
+* [get_transfers](#get_transfers)
+* [get_transfer_by_txid](#get_transfer_by_txid)
+* [incoming_transfers](#incoming_transfers)
+* [query_key](#query_key)
+* [make_integrated_address](#make_integrated_address)
+* [split_integrated_address](#split_integrated_address)
+* [stop_wallet](#stop_wallet)
+* [make_uri](#make_uri)
+* [parse_uri](#parse_uri)
+* [rescan_blockchain](#rescan_blockchain)
+* [set_tx_notes](#set_tx_notes)
+* [get_tx_notes](#get_tx_notes)
+* [sign](#sign)
+* [verify](#verify)
+* [export_key_images](#export_key_images)
+* [import_key_images](#import_key_images)
+* [get_address_book](#get_address_book)
+* [add_address_book](#add_address_book)
+* [delete_address_book](#delete_address_book)
+* [rescan_spent](#rescan_spent)
+* [start_mining](#start_mining)
+* [stop_mining](#stop_mining)
+* [get_languages](#get_languages)
+* [create_wallet](#create_wallet)
+* [open_wallet](#open_wallet)
+
+---
+
+## JSON RPC Methods:
+
+### **getbalance**
+
+Return the wallet's balance.
+
+Inputs: *None*.
+
+Outputs:
+
+* *balance* - unsigned int; The total balance of the current monero-wallet-rpc in session.
+* *unlocked_balance* - unsigned int; Unlocked funds are those funds that are sufficiently deep enough in the Monero blockchain to be considered safe to spend.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getbalance"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "balance": 140000000000,
+ "unlocked_balance": 50000000000
+ }
+}
+```
+
+
+### **getaddress**
+
+Return the wallet's address.
+
+Inputs: *None*.
+
+Outputs:
+
+* *address* - string; The 95-character hex address string of the monero-wallet-rpc in session.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getaddress"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "address": "427ZuEhNJQRXoyJAeEoBaNW56ScQaLXyyQWgxeRL9KgAUhVzkvfiELZV7fCPBuuB2CGuJiWFQjhnhhwiH1FsHYGQGaDsaBA"
+ }
+}
+```
+
+
+### **getheight**
+
+Returns the wallet's current block height.
+
+Inputs: *None*.
+
+Outputs:
+
+* *height* - unsigned int; The current monero-wallet-rpc's blockchain height. If the wallet has been offline for a long time, it may need to catch up with the daemon.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getheight"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "height": 994310
+ }
+}
+```
+
+
+### **transfer**
+
+Send monero to a number of recipients.
+
+Inputs:
+
+* *destinations* - array of destinations to receive XMR:
+ * *amount* - unsigned int; Amount to send to each destination, in atomic units.
+ * *address* - string; Destination public address.
+* *fee* - unsigned int; Ignored, will be automatically calculated.
+* *mixin* - unsigned int; Number of outpouts from the blockchain to mix with (0 means no mixing).
+* *unlock_time* - unsigned int; Number of blocks before the monero can be spent (0 to not add a lock).
+* *payment_id* - string; (Optional) Random 32-byte/64-character hex string to identify a transaction.
+* *get_tx_key* - boolean; (Optional) Return the transaction key after sending.
+* *priority* - unsigned int; Set a priority for the transaction. Accepted Values are: 0-3 for: default, unimportant, normal, elevated, priority.
+* *do_not_relay* - boolean; (Optional) If true, the newly created transaction will not be relayed to the monero network. (Defaults to false)
+* *get_tx_hex* - boolean; Return the transaction as hex string after sending
+
+
+Outputs:
+
+* *fee* - Integer value of the fee charged for the txn.
+* *tx_hash* - String for the publically searchable transaction hash
+* *tx_key* - String for the transaction key if get_tx_key is true, otherwise, blank string.
+* *tx_blob* - Transaction as hex string if get_tx_hex is true
+
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"transfer","params":{"destinations":[{"amount":100000000,"address":"9wNgSYy2F9qPZu7KBjvsFgZLTKE2TZgEpNFbGka9gA5zPmAXS35QzzYaLKJRkYTnzgArGNX7TvSqZC87tBLwtaC5RQgJ8rm"},{"amount":200000000,"address":"9vH5D7Fv47mbpCpdcthcjU34rqiiAYRCh1tYywmhqnEk9iwCE9yppgNCXAyVHG5qJt2kExa42TuhzQfJbmbpeGLkVbg8xit"}],"mixin":4,"get_tx_key": true}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "fee": 48958481211,
+ "tx_hash": "985180f468637bc6d2f72ee054e1e34b8d5097988bb29a2e0cb763e4464db23c",
+ "tx_key": "8d62e5637f1fcc9a8904057d6bed6c697618507b193e956f77c31ce662b2ee07"
+ }
+}
+```
+
+
+### **transfer_split**
+
+Same as transfer, but can split into more than one tx if necessary.
+
+Inputs:
+
+* *destinations* - array of destinations to receive XMR:
+ * *amount* - unsigned int; Amount to send to each destination, in atomic units.
+ * *address* - string; Destination public address.
+* *fee* - unsigned int; Ignored, will be automatically calculated.
+* *mixin* - unsigned int; Number of outpouts from the blockchain to mix with (0 means no mixing).
+* *unlock_time* - unsigned int; Number of blocks before the monero can be spent (0 to not add a lock).
+* *payment_id* - string; (Optional) Random 32-byte/64-character hex string to identify a transaction.
+* *get_tx_keys* - boolean; (Optional) Return the transaction keys after sending. -- Ignored
+* *priority* - unsigned int; Set a priority for the transactions. Accepted Values are: 0-3 for: default, unimportant, normal, elevated, priority.
+* *do_not_relay* - boolean; (Optional) If true, the newly created transaction will not be relayed to the monero network. (Defaults to false)
+* *get_tx_hex* - boolean; Return the transactions as hex string after sending
+* *new_algorithm* - boolean; True to use the new transaction construction algorithm, defaults to false.
+
+Outputs:
+
+* *fee_list* - array of: integer. The amount of fees paid for every transaction.
+* *tx_hash_list* - array of: string. The tx hashes of every transaction.
+* *tx_blob_list* - array of: string. The tx as hex string for every transaction.
+* *amount_list* - array of: integer. The amount transferred for every transaction..
+* *tx_key_list* - array of: string. The transaction keys for every transaction.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"transfer_split","params":{"destinations":[{"amount":100000000,"address":"9wNgSYy2F9qPZu7KBjvsFgZLTKE2TZgEpNFbGka9gA5zPmAXS35QzzYaLKJRkYTnzgArGNX7TvSqZC87tBwtaC5RQgJ8rm"},{"amount":200000000,"address":"9vH5D7Fv47mbpCpdcthcjU34rqiiAYRCh1tYywmhqnEk9iwCE9yppgNCXAyVHG5qJt2kExa42TuhzQfJbmbpeGLkVbg8xit"},{"amount":200000000,"address":"9vC5Q25cR1d3WzKX6dpTaLJaqZyDrtTnfadTmVuB1Wue2tyFGxUhiE4RGa74pEDJv7gSySzcd1Ao6G1nzSaqp78vLfP6MPj"},{"amount":200000000,"address":"A2MSrn49ziBPJBh8ZNEhhbfyLMou6mao4C1F5TLGUatmUnCxZArDYkcbAnVkVEopWVeak2rKDrmc8JpoS7n5dvfN9YDPBTG"},{"amount":200000000,"address":"9tEDyVQ8zgRQbDYiykTdpw5kZ6qWQWcKfExEj9eQshjpGb3sdr3UyWE2AHWzUGzJjaH9HN1DdGBdyQQ4AqGMc7rr5xYwZWW"}],"mixin":4,"get_tx_key": true, "new_algorithm": true}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "fee_list": [97916962422],
+ "tx_hash_list": ["c5c389846e701c27aaf1f7ab8b9dc457b471fcea5bc9710e8020d51275afbc54"]
+ }
+}
+```
+
+
+### **sweep_dust**
+
+Send all dust outputs back to the wallet's, to make them easier to spend (and mix).
+
+Inputs: *None*.
+
+Outputs:
+
+* *tx_hash_list* - list of: string
+
+Example (In this example, `sweep_dust` returns an error due to insufficient funds to sweep):
+
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"sweep_dust"}' -H 'Content-Type: application/json'
+
+{
+ "error": {
+ "code": -4,
+ "message": "not enough money"
+ },
+ "id": "0",
+ "jsonrpc": "2.0"
+}
+```
+
+### **sweep_all**
+
+Send all unlocked balance to an address.
+
+Inputs:
+
+* *address* - string; Destination public address.
+* *priority* - unsigned int; (Optional)
+* *mixin* - unsigned int; Number of outpouts from the blockchain to mix with (0 means no mixing).
+* *unlock_time* - unsigned int; Number of blocks before the monero can be spent (0 to not add a lock).
+* *payment_id* - string; (Optional) Random 32-byte/64-character hex string to identify a transaction.
+* *get_tx_keys* - boolean; (Optional) Return the transaction keys after sending.
+* *below_amount* - unsigned int; (Optional)
+* *do_not_relay* - boolean; (Optional)
+* *get_tx_hex* - boolean; (Optional) return the transactions as hex encoded string.
+
+Outputs:
+
+* *tx_hash_list* - array of string;
+* *tx_key_list* - array of string;
+* *tx_blob_list* - array of string;
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"sweep_all","params":{"address":"9sS8eRU2b5ZbN2FPSrpkiab1bjbHE5XtL6Ti6We3Fhw5aQPudRfVVypjgzKDNkxtvTQSPs122NKggb2mqcqkKSeMNVu59S","mixin":2,"unlock_time":0,"get_tx_keys":true}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "tx_hash_list": ["53a3648797d5524dd037d4105e067fa61468faecab41927fc43adbb26c202d22"],
+ "tx_key_list": ["e83b3b78235e36cd7e4d9695efd81a3b3e64c7d1f1ebd61892f0a7add6a50301"]
+ }
+}
+```
+
+### **store**
+
+Save the blockchain.
+
+Inputs: *None*.
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"store"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **get_payments**
+
+Get a list of incoming payments using a given payment id.
+
+Inputs:
+
+* *payment_id* - string
+
+Outputs:
+
+* *payments* - list of:
+ * *payment_id* - string
+ * *tx_hash* - string
+ * *amount* - unsigned int
+ * *block_height* - unsigned int
+ * *unlock_time* - unsigned int
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_payments","params":{"payment_id":"4279257e0a20608e25dba8744949c9e1caff4fcdafc7d5362ecf14225f3d9030"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "payments": [{
+ "amount": 10350000000000,
+ "block_height": 994327,
+ "payment_id": "4279257e0a20608e25dba8744949c9e1caff4fcdafc7d5362ecf14225f3d9030",
+ "tx_hash": "c391089f5b1b02067acc15294e3629a463412af1f1ed0f354113dd4467e4f6c1",
+ "unlock_time": 0
+ }]
+ }
+}
+```
+
+
+### **get_bulk_payments**
+
+Get a list of incoming payments using a given payment id, or a list of payments ids, from a given height. This method is the preferred method over `get_payments` because it has the same functionality but is more extendable. Either is fine for looking up transactions by a single payment ID.
+
+Inputs:
+
+* *payment_ids* - array of: string
+ * *min_block_height* - unsigned int; The block height at which to start looking for payments.
+
+Outputs:
+
+* *payments* - list of:
+ * *payment_id* - string
+ * *tx_hash* - string
+ * *amount* - unsigned int
+ * *block_height* - unsigned int
+ * *unlock_time* - unsigned int
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_bulk_payments","params":{"payment_ids":["4279257e0a20608e25dba8744949c9e1caff4fcdafc7d5362ecf14225f3d9030"],"min_block_height":990000}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "payments": [{
+ "amount": 10350000000000,
+ "block_height": 994327,
+ "payment_id": "4279257e0a20608e25dba8744949c9e1caff4fcdafc7d5362ecf14225f3d9030",
+ "tx_hash": "c391089f5b1b02067acc15294e3629a463412af1f1ed0f354113dd4467e4f6c1",
+ "unlock_time": 0
+ }]
+ }
+}
+```
+
+
+### **get_transfers**
+
+Returns a list of transfers.
+
+Inputs:
+
+* *in* - boolean;
+* *out* - boolean;
+* *pending* - boolean;
+* *failed* - boolean;
+* *pool* - boolean;
+* *filter_by_height* - boolean;
+* *min_height* - unsigned int;
+* *max_height* - unsigned int;
+
+Outputs:
+
+* *in* array of transfers:
+ * *txid* - string;
+ * *payment_id* - string;
+ * *height* - unsigned int;
+ * *timestamp* - unsigned int;
+ * *amount* - unsigned int;
+ * *fee* - unsigned int;
+ * *note* - string;
+ * *destinations* - std::list<transfer_destination>;
+ * *type* - string;
+* *out* array of transfers
+* *pending* array of transfers
+* *failed* array of transfers
+* *pool* array of transfers
+
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_transfers","params":{"pool":true}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "pool": [{
+ "amount": 500000000000,
+ "fee": 0,
+ "height": 0,
+ "note": "",
+ "payment_id": "758d9b225fda7b7f",
+ "timestamp": 1488312467,
+ "txid": "da7301d5423efa09fabacb720002e978d114ff2db6a1546f8b820644a1b96208",
+ "type": "pool"
+ }]
+ }
+}
+```
+
+### **get_transfer_by_txid**
+
+Show information about a transfer to/from this address.
+
+Inputs:
+
+* *txid* - string
+
+Outputs:
+
+* *transfer* - JSON object containing parment information:
+ * *amount* - unsigned int
+ * *fee* - unsigned int
+ * *height* - unsigned int
+ * *note* - string
+ * *payment_id* - string
+ * *timestamp* - unsigned int
+ * *txid* - string
+ * *type* - string
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_transfer_by_txid","params":{"txid":"f2d33ba969a09941c6671e6dfe7e9456e5f686eca72c1a94a3e63ac6d7f27baf"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "transfer": {
+ "amount": 10000000000000,
+ "fee": 0,
+ "height": 1316388,
+ "note": "",
+ "payment_id": "0000000000000000",
+ "timestamp": 1495539310,
+ "txid": "f2d33ba969a09941c6671e6dfe7e9456e5f686eca72c1a94a3e63ac6d7f27baf",
+ "type": "in"
+ }
+ }
+}
+```
+
+
+### **incoming_transfers**
+
+Return a list of incoming transfers to the wallet.
+
+Inputs:
+
+* *transfer_type* - string; "all": all the transfers, "available": only transfers which are not yet spent, OR "unavailable": only transfers which are already spent.
+
+Outputs:
+
+* *transfers* - list of:
+ * *amount* - unsigned int
+ * *spent* - boolean
+ * *global_index* - unsigned int; Mostly internal use, can be ignored by most users.
+ * *tx_hash* - string; Several incoming transfers may share the same hash if they were in the same transaction.
+ * *tx_size* - unsigned int
+
+Example (Return "all" transaction types):
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"incoming_transfers","params":{"transfer_type":"all"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "transfers": [{
+ "amount": 10000000000000,
+ "global_index": 711506,
+ "spent": false,
+ "tx_hash": "<c391089f5b1b02067acc15294e3629a463412af1f1ed0f354113dd4467e4f6c1>",
+ "tx_size": 5870
+ },{
+ "amount": 300000000000,
+ "global_index": 794232,
+ "spent": false,
+ "tx_hash": "<c391089f5b1b02067acc15294e3629a463412af1f1ed0f354113dd4467e4f6c1>",
+ "tx_size": 5870
+ },{
+ "amount": 50000000000,
+ "global_index": 213659,
+ "spent": false,
+ "tx_hash": "<c391089f5b1b02067acc15294e3629a463412af1f1ed0f354113dd4467e4f6c1>",
+ "tx_size": 5870
+ }]
+ }
+}
+```
+
+Example (Return "available" transactions):
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"incoming_transfers","params":{"transfer_type":"available"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "transfers": [{
+ "amount": 10000000000000,
+ "global_index": 711506,
+ "spent": false,
+ "tx_hash": "<c391089f5b1b02067acc15294e3629a463412af1f1ed0f354113dd4467e4f6c1>",
+ "tx_size": 5870
+ },{
+ "amount": 300000000000,
+ "global_index": 794232,
+ "spent": false,
+ "tx_hash": "<c391089f5b1b02067acc15294e3629a463412af1f1ed0f354113dd4467e4f6c1>",
+ "tx_size": 5870
+ },{
+ "amount": 50000000000,
+ "global_index": 213659,
+ "spent": false,
+ "tx_hash": "<c391089f5b1b02067acc15294e3629a463412af1f1ed0f354113dd4467e4f6c1>",
+ "tx_size": 5870
+ }]
+ }
+}
+```
+
+Example (Return "unavailable" transaction. Note that this particular example returns 0 unavailable transactions):
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"incoming_transfers","params":{"transfer_type":"unavailable"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **query_key**
+
+Return the spend or view private key.
+
+Inputs:
+
+* *key_type* - string; Which key to retrieve: "mnemonic" - the mnemonic seed (older wallets do not have one) OR "view_key" - the view key
+
+Outputs:
+
+* *key* - string; The view key will be hex encoded, while the mnemonic will be a string of words.
+
+Example (Query view key):
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"query_key","params":{"key_type":"view_key"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "key": "7e341d..."
+ }
+}
+```
+
+Example (Query mnemonic key):
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"query_key","params":{"key_type":"mnemonic"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "key": "adapt adapt nostril ..."
+ }
+}
+```
+
+
+### **make_integrated_address**
+
+Make an integrated address from the wallet address and a payment id.
+
+Inputs:
+
+* *payment_id* - string; hex encoded; can be empty, in which case a random payment id is generated
+
+Outputs:
+
+* *integrated_address* - string
+
+Example (Payment ID is empty, use a random ID):
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"make_integrated_address","params":{"payment_id":""}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "integrated_address": "4BpEv3WrufwXoyJAeEoBaNW56ScQaLXyyQWgxeRL9KgAUhVzkvfiELZV7fCPBuuB2CGuJiWFQjhnhhwiH1FsHYGQQ8H2RRJveAtUeiFs6J"
+ }
+}
+```
+
+
+### **split_integrated_address**
+
+Retrieve the standard address and payment id corresponding to an integrated address.
+
+Inputs:
+
+* *integrated_address* - string
+
+Outputs:
+
+* *standard_address* - string
+* *payment* - string; hex encoded
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"split_integrated_address","params":{"integrated_address": "4BpEv3WrufwXoyJAeEoBaNW56ScQaLXyyQWgxeRL9KgAUhVzkvfiELZV7fCPBuuB2CGuJiWFQjhnhhwiH1FsHYGQQ8H2RRJveAtUeiFs6J"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "payment_id": "<420fa29b2d9a49f5>",
+ "standard_address": "427ZuEhNJQRXoyJAeEoBaNW56ScQaLXyyQWgxeRL9KgAUhVzkvfiELZV7fCPBuuB2CGuJiWFQjhnhhwiH1FsHYGQGaDsaBA"
+ }
+}
+```
+
+
+### **stop_wallet**
+
+Stops the wallet, storing the current state.
+
+Inputs: *None*.
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"stop_wallet"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **make_uri**
+
+Create a payment URI using the official URI spec.
+
+Inputs:
+
+* *address* - wallet address string
+* *amount* (optional) - the integer amount to receive, in **atomic** units
+* *payment_id* (optional) - 16 or 64 character hexadecimal payment id string
+* *recipient_name* (optional) - string name of the payment recipient
+* *tx_description* (optional) - string describing the reason for the tx
+
+Outputs:
+
+* *uri* - a string containing all the payment input information as a properly formatted payment URI
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"make_uri","params":{"address":"44AFFq5kSiGBoZ4NMDwYtN18obc8AemS33DBLWs3H7otXft3XjrpDtQGv7SqSsaBYBb98uNbr2VBBEt7f2wfn3RVGQBEP3A","amount":10,"payment_id":"0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef","tx_description":"Testing out the make_uri function.","recipient_name":"Monero Project donation address"}}' -H 'Content-Type: application/json'
+
+{
+ "id": 0,
+ "jsonrpc": "2.0",
+ "result": {
+ "uri": "monero:44AFFq5kSiGBoZ4NMDwYtN18obc8AemS33DBLWs3H7otXft3XjrpDtQGv7SqSsaBYBb98uNbr2VBBEt7f2wfn3RVGQBEP3A?tx_payment_id=0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef&tx_amount=0.000000000010&recipient_name=Monero%20Project%20donation%20address&tx_description=Testing%20out%20the%20make_uri%20function."
+ }
+}
+```
+
+
+### **parse_uri**
+
+Parse a payment URI to get payment information.
+
+Inputs:
+
+* *uri* - a string containing all the payment input information as a properly formatted payment URI
+
+Outputs:
+
+* *uri* - JSON object containing payment information:
+ * *address* - wallet address string
+ * *amount* - the decimal amount to receive, in **coin** units (0 if not provided)
+ * *payment_id* - 16 or 64 character hexadecimal payment id string (empty if not provided)
+ * *recipient_name* - string name of the payment recipient (empty if not provided)
+ * *tx_description* - string describing the reason for the tx (empty if not provided)
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"parse_uri","params":{"uri":"monero:44AFFq5kSiGBoZ4NMDwYtN18obc8AemS33DBLWs3H7otXft3XjrpDtQGv7SqSsaBYBb98uNbr2VBBEt7f2wfn3RVGQBEP3A?tx_payment_id=0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef&tx_amount=0.000000000010&recipient_name=Monero%20Project%20donation%20address&tx_description=Testing%20out%20the%20make_uri%20function."}}' -H 'Content-Type: application/json'
+
+{
+ "id": 0,
+ "jsonrpc": "2.0",
+ "result": {
+ "uri": {
+ "address": "44AFFq5kSiGBoZ4NMDwYtN18obc8AemS33DBLWs3H7otXft3XjrpDtQGv7SqSsaBYBb98uNbr2VBBEt7f2wfn3RVGQBEP3A",
+ "amount": 10,
+ "payment_id": "0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef",
+ "recipient_name": "Monero Project donation address",
+ "tx_description": "Testing out the make_uri function."
+ }
+ }
+}
+```
+
+
+### **rescan_blockchain**
+
+Rescan blockchain from scratch.
+
+Inputs: *None*.
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"rescan_blockchain" -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **set_tx_notes**
+
+Set arbitrary string notes for transactions.
+
+Inputs:
+
+* *txids* - array of string; transaction ids
+* *notes* - array of string; notes for the transactions
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"set_tx_notes","params":{"txids":["6a1a100c079c236e2cbf36f7760e8ef1a9e8357c434aa790a8c78de653ec4cf2"],"notes":["This is an example"]}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **get_tx_notes**
+
+Get string notes for transactions.
+
+Inputs:
+
+* *txids* - array of string; transaction ids
+
+Outputs:
+
+* *notes* - array of string; notes for the transactions
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_tx_notes","params":{"txids":["6a1a100c079c236e2cbf36f7760e8ef1a9e8357c434aa790a8c78de653ec4cf2"]}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "notes": ["This is an example"]
+ }
+}
+```
+
+
+### **sign**
+
+Sign a string.
+
+Inputs:
+
+* *data* - string;
+
+Outputs:
+
+* *signature* - string;
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"sign","params":{"data":"This is sample data to be signed"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "signature": "SigV1Xp61ZkGguxSCHpkYEVw9eaWfRfSoAf36PCsSCApx4DUrKWHEqM9CdNwjeuhJii6LHDVDFxvTPijFsj3L8NDQp1TV"
+ }
+}
+```
+
+
+### **verify**
+
+Verify a signature on a string.
+
+Inputs:
+
+* *data* - string;
+* *address* - string;
+* *signature* - string;
+
+Outputs:
+
+* *good* - boolean;
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"verify","params":{"data":"This is sample data to be signed","address":"9sS8eRU2b5ZbN2FPSrpkiab1bjbHE5XtL6Ti6We3Fhw5aQPudRfVVypjgzKDNkxtvTQZSPs122NKggb2mqcqkKSeMNVu59S","signature":"SigV1Xp61ZkGguxSCHpkYEVw9eaWfRfSoAf36PCsSCApx4DUrKWHEqM9CdNwjeuhJii6LHDVDFxvTPijFsj3L8NDQp1TV"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "good": true
+ }
+}
+```
+
+
+### **export_key_images**
+
+Export a signed set of key images.
+
+Inputs: *None*.
+
+Outputs:
+
+* *signed_key_images* - array of signed key images:
+ * *key_image* - string;
+ * *signature* - string;
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"export_key_images"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "signed_key_images": [{
+ "key_image": "62b83df78baad99e23b5ad3f667bc6f8d388a13d9e84c7bb6c223a556dfd34af",
+ "signature": "b87b7e989aa85aa3a2a7cd8adcb3a848d3512ff718b168e15217ff3e5da29c0183c0328b97cc052fcb5ee3548aa5e41e530ba9d854199ea19d7ddaf6a54a4c0a"
+ }]
+ }
+}
+```
+
+
+### **import_key_images**
+
+Import signed key images list and verify their spent status.
+
+Inputs:
+
+* *signed_key_images* - array of signed key images:
+ * *key_image* - string;
+ * *signature* - string;
+
+Outputs:
+
+* *height* - unsigned int;
+* *spent* - unsigned int;
+* *unspent* - unsigned int;
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"import_key_images", "params":{"signed_key_images":[{"key_image":"63b83df78cafd99e23b5ad3f667bc6f8d38813d9e84c7bb6c223a556dfd34af","signature":"b87b7e989aa86aa2a7a7cd8adcb3a848d3512ff718b168e15217ff3e5da29c0183c0328b97cc052fcb5ee3548aa5e41e530ba9d854199ea19d7ddaf6a54a4c0a"},{"key_image":"44ec12fbc56c533a30b09de8ae26febd515528c4957dfe875430377a7e212b4e","signature":"91105f15be0b25bc2a94bd78a7e261608974d6d888080b9f1815655b98af190340325ea1a0840a5951dacf913d4de1b2bd33ea59c1cb7bce1b6648afa7133d03"}]}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "height": 986050,
+ "spent": 10000100000000,
+ "unspent": 4979852760000
+ }
+}
+```
+
+
+### **get_address_book**
+
+Retrieves entries from the address book.
+
+Inputs:
+
+* *entries* - array of unsigned int; indices of the requested address book entries
+
+Outputs:
+
+* *entries* - array of entries:
+ * *address* - string;
+ * *description* - string;
+ * *index* - unsigned int;
+ * *payment_id* - string;
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_address_book","params":{"entries":[1,2]}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "entries": [{
+ "address": "A135xq3GVMdU5qtAm4hN7zjPgz8bRaiSUQmtuDdjZ6CgXayvQruJy3WPe95qj873JhK4YdTQjoR39Leg6esznQk8PckhjRN",
+ "description": "",
+ "index": 1,
+ "payment_id": "0000000000000000000000000000000000000000000000000000000000000000"
+ },{
+ "address": "A135xq3GVMdU5qtAm4hN7zjPgz8bRaiSUQmtuDdjZ6CgXayvQruJy3WPe95qj873JhK4YdTQjoR39Leg6esznQk8PckhjRN",
+ "description": "",
+ "index": 2,
+ "payment_id": "0000000000000000000000000000000000000000000000000000000000000000"
+ }]
+ }
+}
+```
+
+
+### **add_address_book**
+
+Add an entry to the address book.
+
+Inputs:
+
+* *address* - string;
+* *payment_id* - (optional) string, defaults to "0000000000000000000000000000000000000000000000000000000000000000";
+* *description* - (optional) string, defaults to "";
+
+Outputs:
+
+* *index* - unsigned int; The index of the address book entry.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"add_address_book","params":{"address":"44AFFq5kSiGBoZ4NMDwYtN18obc8AemS33DBLWs3H7otXft3XjrpDtQGv7SqSsBYBb98uNbr2VBBEt7f2wfn3RVGQBEP3A","description":"Donation address for the Monero project"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "index": 2
+ }
+}
+```
+
+
+### **delete_address_book**
+
+Delete an entry from the address book.
+
+Inputs:
+
+* *index* - unsigned int; The index of the address book entry.
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"delete_address_book","params":{"index":0}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **rescan_spent**
+
+Rescan the blockchain for spent outputs.
+
+Inputs: *None*.
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"rescan_spent"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **start_mining**
+
+Start mining in the Monero daemon.
+
+Inputs:
+
+* *threads_count* - unsigned int; Number of threads created for mining
+* *do_background_mining* - boolean;
+* *ignore_battery* - boolean;
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"start_mining","params":{"threads_count":1,"do_background_mining":true,"ignore_battery":true}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **stop_mining**
+
+Stop mining in the Monero daemon.
+
+Inputs: *None*.
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"stop_mining"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **get_languages**
+
+Get a list of available languages for your wallet's seed.
+
+Inputs: *None*.
+
+Outputs:
+
+* *languages* - array of string; List of available languages
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_languages"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "languages": ["Deutsch","English","Español","Français","Italiano","Nederlands","Português","руÑÑкий Ñзык","日本語","简体ä¸æ–‡ (ä¸å›½)","Esperanto"]
+ }
+}
+```
+
+
+### **create_wallet**
+
+Create a new wallet. You need to have set the argument "--wallet-dir" when launching monero-wallet-rpc to make this work.
+
+Inputs:
+
+* *filename* - string;
+* *password* - string;
+* *language* - string; Language for your wallets' seed.
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"create_wallet","params":{"filename":"mytestwallet","password":"mytestpassword","language":"English"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **open_wallet**
+
+Open a wallet. You need to have set the argument "--wallet-dir" when launching monero-wallet-rpc to make this work.
+
+Inputs:
+
+* *filename* - string;
+* *password* - string;
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"open_wallet","params":{"filename":"mytestwallet","password":"mytestpassword"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
diff --git a/_i18n/es/resources/moneropedia/00-base-00 b/_i18n/es/resources/moneropedia/00-base-00
new file mode 100644
index 0000000000000000000000000000000000000000..ccfa17812230473e626c898f7f40e50c1938a8de
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/00-base-00
@@ -0,0 +1,10 @@
+---
+layout: moneropedia
+entry: ""
+terms: ["", ""]
+summary: ""
+---
+
+### The Basics
+
+{{ page.summary | capitalize }}.
\ No newline at end of file
diff --git a/_i18n/es/resources/moneropedia/account.md b/_i18n/es/resources/moneropedia/account.md
new file mode 100644
index 0000000000000000000000000000000000000000..8014c8ee5015268c05066097bcc1a3f3324220c7
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/account.md
@@ -0,0 +1,82 @@
+---
+layout: moneropedia
+entry: "Account"
+terms: ["account", "accounts", "wallet", "wallets"]
+summary: "similar in function to a bank account, contains all of your sent and received transactions"
+---
+
+### The Basics
+
+Those familiar with Monero's predecessors will be more familiar with the term *wallet* to describe this. In Monero we call this an account, and it is a private account owned and operated by a Monero user.
+
+Your account contains all of the Monero @transactions you have sent and received. Your account balance is a sum of all the Monero you've received, less the Monero you've sent. When using Monero you may notice that your account has two balances, a locked and an unlocked balance. The unlocked balance contains funds that can be spent immediately, and the locked balance contains funds that you can't spend right now. You may receive a transaction that has an @unlock-time set, or you may have sent some Monero and are waiting for the @change to come back to your wallet, both situations that could lead to those funds being locked for a time.
+
+A key difference between traditional electronic currency and Monero is that your account resides only under your control, normally on your computer, and cannot be accessed by anyone else if you [practice good security](#practicing-good-security).
+
+### Multiple Accounts
+
+There are no costs attached to creating a Monero account, and there are no fees charged except for individual @transaction fees that go to @miners.
+
+This means that individuals can easily create a Monero account for themselves as well as a joint account to share with their partner, and individual accounts for their children. Similarly, a business could create separate accounts for each division or group. Since Monero's @transaction fees are quite low, moving funds between accounts is not an expensive exercise.
+
+### Cryptographic Keys
+
+Monero relies heavily on a cryptography principle known as *public/private key cryptography* or *asymmetric cryptography*, which is thoroughly detailed in [this Wikipedia article](https://en.wikipedia.org/wiki/Public-key_cryptography).
+
+Your account is based on two keys, a @spend-key and a @view-key. The @spend-key is special in that it is the single key required to spend your Monero funds, whereas the @view-key allows you to reveal your @transactions to a third party, for example for auditing or accounting purposes. These keys in your account also play an important role in Monero's @transaction-privacy.
+
+The private keys for both of these must be protected by you in order to retain your account privacy. On the other hand, the public keys are obviously public (they are part of your Monero account address). For normal public/private key cryptography someone could send you a private message by encrypting it with either of your public keys, and you would then be the only one able to decrypt it with your private keys.
+
+### Backing Up Your Account
+
+When you manage your own Monero Account with the private @spend-key, you are solely responsible for the security of your funds. Thankfully, Monero makes it very easy to backup your account. When creating a Monero account for the first time you will be given a unique @mnemonic-seed for your account that consists of 13 or 25 words in the language of your choosing. **This seed is the only thing you need to backup for your account**, and so it is imperative that it is written down and stored securely. Never store this seed in a form or location that would allow someone else to see it!
+
+```
+List of available languages for your wallet's seed:
+0 : Deutsch
+1 : English
+2 : Español
+3 : Français
+4 : Italiano
+5 : Nederlands
+6 : Português
+7 : руÑÑкий Ñзык
+8 : 日本語
+9 : 简体ä¸æ–‡ (ä¸å›½)
+10 : Esperanto
+Enter the number corresponding to the language of your choice: 1
+Generated new wallet: 4B15ZjveuttEaTmfZjLVioPVw7bfSmRLpSgB33CJbuC6BoGtZrug9TDAmhZEWD6XoFDGz55bgzisT9Dnv61sbsA6Sa47TYu
+view key: 4130fa26463d9451781771a8baa5d0b8085c47c4500cefe4746bab48f1d15903
+**********************************************************************
+Your wallet has been generated.
+To start synchronizing with the daemon, use "refresh" command.
+Use "help" command to see the list of available commands.
+Always use "exit" command when closing monero-wallet-cli to save your
+current session's state. Otherwise, you might need to synchronize
+your wallet again (your wallet keys are NOT at risk in any case).
+
+PLEASE NOTE: the following 25 words can be used to recover access to your wallet. Please write them down and store them somewhere safe and secure. Please do not store them in your email or on file storage services outside of your immediate control.
+
+aunt knuckle italics moisture hawk thorn iris abort
+chlorine smog uphill glass aptitude nowhere sewage plywood
+dual relic fierce divers anvil nodes bubble cabin abort
+**********************************************************************
+Starting refresh...
+Refresh done, blocks received: 21939
+Balance: 0.000000000000, unlocked balance: 0.000000000000
+Background refresh thread started
+[wallet 4B15Zj]: â–ˆ
+
+```
+
+As the example above indicates, it is incredibly important to store these words in safe locations. If you are concerned about the risk of critical loss at your home, for instance, you may want to store a second copy of your seed with your attorney or in a safety deposit box. It is also recommended that it is stored in a way that does not make it obvious that it is your seed, so writing it into a letter or as part of other notes is advisable.
+
+### Practicing Good Security
+
+Over and above backing up your @mnemonic-seed so that you have access to your account in the event of critical data loss, it is also important to practice good security. Use a secure password when creating a local Monero account (not used on [MyMonero](https://mymonero.com) or other web-based account systems).
+
+Don't ever give your Monero account password to anyone, as this can be used to access the Monero on your computer without knowing your @mnemonic-seed. Similarly, make sure you have running and up-to-date antivirus, especially on Windows computers. Finally, be careful when clicking links in emails or on unknown and untrusted websites, as malware installed on your computer can sit and wait for you to access your Monero account before taking the funds from it.
+
+### Leaving Your Account to Next of Kin
+
+Providing access to your Monero account to your next of kin is just as easy as it is to backup your Monero account. Simply leave your @mnemonic-seed to them in your will, or store it somewhere safe where it will be given to them upon the execution of your will. A key advantage to this is that your next of kin won't have to wait for months for a third party to release the funds to them.
diff --git a/_i18n/es/resources/moneropedia/address-book.md b/_i18n/es/resources/moneropedia/address-book.md
new file mode 100644
index 0000000000000000000000000000000000000000..43b159c94ef29d9f8deb12af5b1294c5e2268b28
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/address-book.md
@@ -0,0 +1,35 @@
+---
+layout: moneropedia
+entry: "Address Book"
+tags: ["kovri"]
+terms: ["Address-Book"]
+summary: "Allows you to visit I2P websites/services that have the .i2p domain"
+---
+
+### The Basics
+
+In order to browse @I2P sites or services with @Kovri, you'll need an address book. An address book will allow you to translate @I2P websites/services that use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain) into an address that @I2P network will understand.
+
+Without an address book, you would be stuck using a @base32-address every time you visit an @I2P website/service - and that's not fun!
+
+### In-depth information
+
+Since [DNS](https://en.wikipedia.org/wiki/DNS) does not exist on the @I2P network, @Kovri also does **not** use DNS or any sort of @canonically-unique-host resolution. Instead, Kovri pairs a @locally-unique-host to a @base64-address @destination in a @subscription. Once your address book is filled with a @subscription, you can resolve your favorite `.i2p` domain site into a usable @I2P destination.
+
+### Creating an Address Book
+
+By default, your installation will come with a default public @subscription called `hosts.txt` in your @data-directory. When @Kovri starts, it loads this subscription and fetches any other subscriptions you've specified. Once loaded, your address book will be appropriately filled. For details on how to manage subscriptions, see @subscription.
+
+### Updating the Address Book
+
+Currently, there are several ways to update your address book:
+
+1. Use a @jump-service to insert I2P addresses into your address book
+2. Use a @jump-service to copy/paste an address into your private @subscription
+3. Manually add or subtract from a private @subscription
+
+**Note: Kovri is in heavy development. In the future there *will* be easier ways to update the address book**
+
+### Address Book / Naming specification
+
+For specification details and more, visit the [Address Book and Naming Specification](https://geti2p.net/en/docs/naming)
diff --git a/_i18n/es/resources/moneropedia/address.md b/_i18n/es/resources/moneropedia/address.md
new file mode 100644
index 0000000000000000000000000000000000000000..ed33f15a69c0969f7f85287f85caadf6e8e6c14d
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/address.md
@@ -0,0 +1,22 @@
+---
+layout: moneropedia
+entry: "Address"
+terms: ["address", "addresses"]
+summary: "either an alias, such as donate.getmonero.org, or a set of 95 characters starting with a 4"
+---
+
+### The Basics
+
+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 <span class="long-term">44AFFq5kSiGBoZ4NMDwYtN18obc8AemS33DBLWs3H7otXft3XjrpDtQGv7SqSsaBYBb98uNbr2VBBEt7f2wfn3RVGQBEP3A</span>.
+
+Because those addresses are long and complex you will often encounter an @OpenAlias address instead. For example, Monero donations can be sent to <span class="long-term">donate@getmonero.org</span> or <span class="long-term">donate.getmonero.org</span>.
+
+If you would like to get an @OpenAlias address of your own then there is some information on the [OpenAlias page](/knowledge-base/openalias).
+
+### Integrated address
+
+An integrated address is an address combined with an encrypted 64-bit @payment-ID. A raw integrated address is 106 characters long.
+
+### In-depth Information
+
+The address is actually the concatenation, in Base58 format, of the *public* @spend-key and the *public* @view-key, prefixed with the network byte (the number 18 for Monero) and suffixed with the first four bytes of the Keccac-256 hash of the whole string (used as a checksum).
diff --git a/_i18n/es/resources/moneropedia/airgap.md b/_i18n/es/resources/moneropedia/airgap.md
new file mode 100644
index 0000000000000000000000000000000000000000..f3107cf267768067e02d7bfab15ddadaadcceaf9
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/airgap.md
@@ -0,0 +1,12 @@
+---
+layout: moneropedia
+entry: "Airgap"
+terms: ["airgap"]
+summary: "An airgap is a security measure to physically separate a computer or device from all other networks, such as the Internet."
+---
+
+### The Basics
+
+"An air gap, air wall or air gapping is a network security measure employed on one or more computers to ensure that a secure computer network is physically isolated from unsecured networks, such as the public Internet or an unsecured local area network.[2] The name arises from the technique of creating a network that is physically separated (with a conceptual air gap) from all other networks. The air gap may not be completely literal, as networks employing the use of dedicated cryptographic devices that can tunnel packets over untrusted networks while avoiding packet rate or size variation can be considered air gapped, as there is no ability for computers on opposite sides of the gap to communicate."
+
+Taken from https://en.wikipedia.org/wiki/Air_gap_(networking)
diff --git a/_i18n/es/resources/moneropedia/base32-address.md b/_i18n/es/resources/moneropedia/base32-address.md
new file mode 100644
index 0000000000000000000000000000000000000000..ef38e41458c635cad73a7328d69f849b73d41c28
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/base32-address.md
@@ -0,0 +1,27 @@
+---
+layout: moneropedia
+entry: "Base32 address"
+tags: ["kovri"]
+terms: ["Base32-address", "Base32-addresses"]
+summary: "Base32 encoded hash of a Base64 address"
+---
+
+### The Basics
+
+A Base32 address is a shortened, encoded version of an @I2P address. The Base32 address is the first part in a `.b32.i2p` hostname.
+
+Example:
+
+`i35yftyyb22xhcvghmev46t5knefur5v66qzekkajatwfwhyklvq.b32.i2p`
+
+where
+
+`i35yftyyb22xhcvghmev46t5knefur5v66qzekkajatwfwhyklvq` is the Base32 address.
+
+### In-depth Information
+
+Ultimately, a Base32 address is a 52 character [Base32 encoded representation](https://en.wikipedia.org/wiki/Base32) of the full SHA-256 hash of an @I2P @base64-address.
+
+### Notes
+
+**Note: `.b32` is not a sub-domain of `.i2p`**
diff --git a/_i18n/es/resources/moneropedia/base64-address.md b/_i18n/es/resources/moneropedia/base64-address.md
new file mode 100644
index 0000000000000000000000000000000000000000..edd345932dd6ae7c5358a4d642b097c00e129d7e
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/base64-address.md
@@ -0,0 +1,22 @@
+---
+layout: moneropedia
+entry: "Base64 address"
+tags: ["kovri"]
+terms: ["Base64-address", "Base64-addresses"]
+summary: "Base64 encoded I2P destination"
+---
+
+### The Basics
+
+A @base64-address is a 516-character [Base64 encoded](https://en.wikipedia.org/wiki/Base64) @I2P @destination. @base64-addresses are primarily used for @address-book, @jump-service, and also internally.
+
+Example:
+
+```
+AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLEov~usVliTSXCSHuRBOCIwIOuDNU0AbVa4BpIx~2sU4TxKhoaA3zQ6VzINoduTdR2IJhPvI5xzezp7dR21CEQGGTbenDslXeQ4iLHFA2~bzp1f7etSl9T2W9RID-KH78sRQmzWnv7dbhNodMbpO6xsf1vENf6bMRzqD5vgHEHZu2aSoNuPyYxDU1eM6--61b2xp9mt1k3ud-5WvPVg89RaU9ugU5cxaHgR927lHMCAEU2Ax~zUb3DbrvgQBOTHnJEx2Fp7pOK~PnP6ylkYKQMfLROosLDXinxOoSKP0UYCh2WgIUPwE7WzJH3PiJVF0~WZ1dZ9mg00c~gzLgmkOxe1NpFRNg6XzoARivNVB5NuWqNxr5WKWMLBGQ9YHvHO1OHhUJTowb9X90BhtHnLK2AHwO6fV-iHWxRJyDabhSMj1kuYpVUBQAEAAcAAA==
+```
+
+
+### In-depth Information
+
+See @destination for details behind @base64-address
diff --git a/_i18n/es/resources/moneropedia/block.md b/_i18n/es/resources/moneropedia/block.md
new file mode 100644
index 0000000000000000000000000000000000000000..cadae194672eb5adacdb1c849d64e0c72ba0bb43
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/block.md
@@ -0,0 +1,16 @@
+---
+layout: moneropedia
+entry: "Block"
+terms: ["block", "blocks"]
+summary: "a container of transactions, a sequence of which forms a blockchain"
+---
+
+### The Basics
+
+A block is a container of @transactions, with a new block being added to the @blockchain once every 2 minutes (see constant `DIFFICULTY_TARGET_V2` defined as 120 seconds), on average.
+
+Blocks also contain a special type of transaction, the @coinbase-transaction, which add newly created Monero to the network.
+
+Blocks are created through the process of @mining, and the @node that successfully mines the block then broadcasts it to each of the @nodes connected to it, who subsequently re-broadcast the block until the entire Monero network has received it.
+
+Fake or bad blocks generally cannot be created, as @nodes that receive blocks always verify the @transactions they contain against a set of consensus rules that all nodes adhere to, including validating the cryptographic @signatures on each transaction.
diff --git a/_i18n/es/resources/moneropedia/blockchain.md b/_i18n/es/resources/moneropedia/blockchain.md
new file mode 100644
index 0000000000000000000000000000000000000000..d20e8cf7753231002d833ad6c1e8f047cce365e3
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/blockchain.md
@@ -0,0 +1,13 @@
+---
+layout: moneropedia
+entry: "Blockchain"
+terms: ["blockchain", "blockchains"]
+summary: "a distributed ledger of all transactions both past and present, without revealing who the funds came from or went to"
+
+---
+
+### 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.
+
+### 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.
diff --git a/_i18n/es/resources/moneropedia/canonically-unique-host.md b/_i18n/es/resources/moneropedia/canonically-unique-host.md
new file mode 100644
index 0000000000000000000000000000000000000000..c11389923934a4dd0ef8ff86017a0c41d9d9835d
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/canonically-unique-host.md
@@ -0,0 +1,23 @@
+---
+layout: moneropedia
+entry: "Canonically-unique host"
+tags: ["kovri"]
+terms: ["Canonically-unique-host"]
+summary: "A host that is canonically resolved to an address or set of addresses"
+---
+
+### The Basics
+
+A Canonically-unique host is a [FQDN](https://en.wikipedia.org/wiki/FQDN) that will canonically resolve to a designated address or set of addresses. Not to be confused with a @locally-unique-host.
+
+### In-depth information
+
+A Canonically-unique host is defined by remote authoritative sources; usually through [DNS](https://en.wikipedia.org/wiki/DNS). When resolving a peer's hostname, you will most likely use an external source for resolution unless you have the following implemented:
+
+- a database file similar to a [hosts file](https://en.wikipedia.org/wiki/etc/hosts)
+- an internal-network resolver (which eventually pulls from external sources)
+
+### Notes
+
+- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
+- @I2P's and @Kovri's self-assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
diff --git a/_i18n/es/resources/moneropedia/change.md b/_i18n/es/resources/moneropedia/change.md
new file mode 100644
index 0000000000000000000000000000000000000000..08163292b111e745bf5cad98c7812f7e6f3ce992
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/change.md
@@ -0,0 +1,16 @@
+---
+layout: moneropedia
+entry: "Change"
+terms: ["change"]
+summary: "Monero sent as part of a transaction, that returns to your account instead of going to another recipient"
+---
+
+### The Basics
+
+{{ page.summary | capitalize }}.
+
+### 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.
+
+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/_i18n/es/resources/moneropedia/clearnet.md b/_i18n/es/resources/moneropedia/clearnet.md
new file mode 100644
index 0000000000000000000000000000000000000000..9200e69a48b0447cad2ba21cbbc085e5cc7af0ab
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/clearnet.md
@@ -0,0 +1,33 @@
+---
+layout: moneropedia
+entry: "Clearnet"
+tags: ["kovri"]
+terms: ["Clearnet"]
+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:
+
+- your [ISP](https://en.wikipedia.org/wiki/ISP)
+- the website/service/person you're communicating with
+- possibly a [Five Eyes](https://en.wikipedia.org/wiki/5_Eyes) capable entity
+
+and even if you use [HTTPS](https://en.wikipedia.org/wiki/HTTPS) or similar (which *encrypts* your transmission), your route is not hidden nor is it anonymous, thus; it is in the *clear*.
+
+### In-depth information
+
+Since a traditional [VPN](https://en.wikipedia.org/wiki/VPN) cannot save you from clearnet (as you are still using *clearnet* (though you are more proxied than without a VPN)), you should use an *anonymous overlay network* to avoid using clearnet directly:
+
+- @Kovri
+- @Java-I2P
+- [Tor](https://torproject.org/)
+
+These technologies protect you from clearnet by building an anonymous network **over** clearnet to keep your transmissions both encrypted **and** anonymous.
+
+Here is an accurate, [interactive diagram](https://www.eff.org/pages/tor-and-https) provided by the [EFF](https://www.eff.org/) which describes *clearnet* as it relates to **Tor**. The concept also (somewhat) applies to @Kovri and @I2P in terms of anonymity with the exception that:
+
+- @Kovri does not use exit nodes when connecting to an @eepsite
+- Your traffic never need to leave the @I2P network
+- You do not need HTTPS to use @Kovri (with the exception of @reseed)
diff --git a/_i18n/es/resources/moneropedia/coinbase.md b/_i18n/es/resources/moneropedia/coinbase.md
new file mode 100644
index 0000000000000000000000000000000000000000..4c564e4ba0e63ac25108c49e8c9332a34c0dac28
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/coinbase.md
@@ -0,0 +1,10 @@
+---
+layout: moneropedia
+entry: "Coinbase Transaction"
+terms: ["coinbase-transaction"]
+summary: "a special type of transaction included in each block, which contains a small amount of Monero sent to the miner as a reward for their mining work"
+---
+
+### The Basics
+
+{{ page.summary | capitalize }}.
\ No newline at end of file
diff --git a/_i18n/es/resources/moneropedia/consensus.md b/_i18n/es/resources/moneropedia/consensus.md
new file mode 100644
index 0000000000000000000000000000000000000000..192e9d9eb4e932068d5bbbab5fb8ceb7f9164f67
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/consensus.md
@@ -0,0 +1,10 @@
+---
+layout: moneropedia
+entry: "Consensus"
+terms: ["consensus", "consensus-network"]
+summary: "consensus describes a property of distributed networks like Monero where most of the participants follow the rules, and thus reject bad participants"
+---
+
+### The Basics
+
+{{ page.summary | capitalize }}.
\ No newline at end of file
diff --git a/_i18n/es/resources/moneropedia/cryptocurrency.md b/_i18n/es/resources/moneropedia/cryptocurrency.md
new file mode 100644
index 0000000000000000000000000000000000000000..45d736c217de532757e9cff5f7a33ddd20367ef5
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/cryptocurrency.md
@@ -0,0 +1,22 @@
+---
+layout: moneropedia
+entry: "Cryptocurrency"
+terms: ["cryptocurrency", "cryptocurrencies", "altcoin", "altcoins"]
+summary: "a digital currency in which encryption techniques are used to regulate the generation of units of currency and verify the transfer of funds, usually operating independently of a central bank"
+---
+
+### The Basics
+
+{{ page.summary | capitalize }}.
+
+### 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).
+
+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).
+
+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.
+
+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/_i18n/es/resources/moneropedia/data-directory.md b/_i18n/es/resources/moneropedia/data-directory.md
new file mode 100644
index 0000000000000000000000000000000000000000..e66f6959ee451482316151ca5a9417aabbb20d76
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/data-directory.md
@@ -0,0 +1,22 @@
+---
+layout: moneropedia
+entry: "Data Directory"
+tags: ["kovri"]
+terms: ["Data-Directory"]
+summary: "Where essential kovri data for runtime is stored"
+---
+
+### The Basics
+
+Depending on your OS, @Kovri currently stores all run-time data in the following directory:
+
+- Linux/FreeBSD:
+ - `$HOME/.kovri`
+
+- OSX:
+ - `$HOME/Library/Application\ Support/Kovri`
+
+- Windows:
+ - `"$APPDATA"\\Kovri`
+
+This includes all configuration files, @address-book, certificates, and resources.
diff --git a/_i18n/es/resources/moneropedia/denominations.md b/_i18n/es/resources/moneropedia/denominations.md
new file mode 100644
index 0000000000000000000000000000000000000000..24bda2415ab2f79ad93f1ab59685842ca589ad44
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/denominations.md
@@ -0,0 +1,36 @@
+---
+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.)"
+---
+
+### 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).
+
+### Denominations of Monero
+
+|------------+----------+-------------------|
+| Name | Base 10 | Amount |
+|-----------:|:--------:| -----------------:|
+| piconero | 10^-12 | 0.000000000001 |
+| nanonero | 10^-9 | 0.000000001 |
+| micronero | 10^-6 | 0.000001 |
+| millinero | 10^-3 | 0.001 |
+| centinero | 10^-2 | 0.01 |
+| decinero | 10^-1 | 0.1 |
+|============+==========+===================|
+| **monero** | **10^0** | **1** |
+|============+==========+===================|
+| decanero | 10^1 | 10 |
+| hectonero | 10^2 | 100 |
+| kilonero | 10^3 | 1,000 |
+| meganero | 10^6 | 1,000,000 |
+|------------+----------+-------------------|
+
+### 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 }}.
diff --git a/_i18n/es/resources/moneropedia/destination.md b/_i18n/es/resources/moneropedia/destination.md
new file mode 100644
index 0000000000000000000000000000000000000000..a999bebfba3fecd61acf623c719ce40a14b780a7
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/destination.md
@@ -0,0 +1,19 @@
+---
+layout: moneropedia
+entry: "Destination"
+tags: ["kovri"]
+terms: ["Destination", "Destinations"]
+summary: "A in-net address that serves as a final endpoint (either local or remote)"
+---
+
+### The Basics
+
+A @destination is the @I2P @in-net address of the final endpoint you are trying to connect to (example: an @I2P website, service, or Monero node). This can also include a *local destination* of which *other* peers need to connect to in order to make contact for communication (similar to how, in @clearnet, your IP address is given to a website when you connect so it knows *where* to send the information back to).
+
+### 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:
+
+`256-byte public key + 128-byte signing key + a null certificate = 516 bytes in Base64 representation`
+
+Note: certificates are not used now but, if they were, the keys would be longer.
diff --git a/_i18n/es/resources/moneropedia/eepsite.md b/_i18n/es/resources/moneropedia/eepsite.md
new file mode 100644
index 0000000000000000000000000000000000000000..5fbb9545d5e7695ea063407cc5f5e880e07a7df4
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/eepsite.md
@@ -0,0 +1,30 @@
+---
+layout: moneropedia
+entry: "Eepsite"
+tags: ["kovri"]
+terms: ["Eepsite", "Hidden-Service", "Garlic-Site", "Garlic-Service"]
+summary: "A website or service hosted within the I2P network"
+---
+
+### The Basics
+
+Is it [**EEP!** *(in response to the site's content)*](https://en.wikipedia.org/wiki/Onomatopoeia), or **end-to-end protocol**, or something else entirely different?
+
+While the original definition of eepsite has been lost with time, its use-case remains: an eepsite is a website or service that is hosted within (and only accessible by) the @I2P network.
+
+### In-depth Information
+
+Alternate names include:
+
+1. *Hidden Service*
+ - because the site/service is *hidden* within the @I2P network and can only be visited within the network
+2. *Garlic Site*
+ - because the website utilizes @I2P's @garlic-routing technology as a means of communicating with a client
+ - because the service is hosted as a website and not any other type of service
+3. *Garlic Service*
+ - because the service utilizes @I2P's @garlic-routing technology as a means of communicating with a client
+ - because the service is specific to services like IRC, email, or a Monero peer (but may also include websites)
+
+### Notes
+
+To learn how to setup an Eepsite (Hidden Service, Garlic Site, Garlic Service) visit the @Kovri [user-guide](https://github.com/monero-project/kovri/blob/master/doc/USER_GUIDE.md).
diff --git a/_i18n/es/resources/moneropedia/encryption.md b/_i18n/es/resources/moneropedia/encryption.md
new file mode 100644
index 0000000000000000000000000000000000000000..d9356c4b15ea16aca56fcf4ae8c00537e87a3dd4
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/encryption.md
@@ -0,0 +1,35 @@
+---
+layout: moneropedia
+entry: "Encryption"
+tags: ["kovri"]
+terms: ["encryption", "encrypted", "encrypting", "decryption", "decrypted", "decrypting"]
+summary: "The process of encoding messages or information in a way that only authorized parties can decode and read"
+---
+
+### The Basics
+
+From [Encryption](https://en.wikipedia.org/wiki/Encryption):
+
+>
+In cryptography, encryption is the process of encoding messages or information in such a way that only authorized parties can decode and read what is sent. Encryption does not of itself prevent interception, but denies the message content to the interceptor.
+
+### In-depth information
+
+From [Encryption](https://en.wikipedia.org/wiki/Encryption):
+
+>
+ In an encryption scheme, the intended communication information or message (referred to as *plaintext*), is encrypted using an encryption algorithm, generating ciphertext that can only be read if decrypted. For technical reasons, an encryption scheme usually uses a pseudo-random encryption key generated by an algorithm. It is in principle possible to decrypt the message without possessing the key, but, for a well-designed encryption scheme, large computational resources and skill are required. An authorized recipient can easily decrypt the message with the key provided by the originator to recipients, but not to unauthorized interceptors.
+
+>
+The purpose of encryption is to ensure that only somebody who is authorized to access data (e.g. a text message or a file), will be able to read it, using the decryption key. Somebody who is not authorized can be excluded, because he or she does not have the required key, without which it is impossible to read the encrypted information.
+
+### Kovri
+
+@Kovri implements various types of encryption in *at least* 4 essential capacities:
+
+- @Reseed for bootstrapping
+- @Garlic-routing: three layers of encryption (@garlic-encryption) are used to verify the secure delivery of @messages to the recipient/peer/@destination
+- @Tunnel encryption: garlic messages are passed through a @tunnel and encrypted by the @tunnel gateway to the @tunnel endpoint
+- @Transport layer encryption prevents the ability to decrypt @messages at the [media layer](https://en.wikipedia.org/wiki/OSI_model)
+
+For details on the types of encryption and cryptographic @signatures used in @Kovri and @I2P, visit @Java-I2P's [Cryptography](https://geti2p.net/spec/cryptography)
diff --git a/_i18n/es/resources/moneropedia/floodfill.md b/_i18n/es/resources/moneropedia/floodfill.md
new file mode 100644
index 0000000000000000000000000000000000000000..e3fbf54f6cbea9a5496f73a15a71222454971430
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/floodfill.md
@@ -0,0 +1,15 @@
+---
+layout: moneropedia
+entry: "Floodfill"
+tags: ["kovri"]
+terms: ["Floodfill"]
+summary: "An I2P router which maintains a distributed network-database"
+---
+
+### The Basics
+
+By actively managing a distributed network-database, a router with *floodfill* capability has the ability to help maintain network stability and resiliancy while also being decentralized and trust-less.
+
+### In-depth information
+
+Though floodfill itself is a simple storage system, the technical underpinnings of floodfill as it relates to @network-database and other protocols within @I2P are much more complex. Visit the [Network Database](https://geti2p.net/en/docs/how/network-database) page for details.
diff --git a/_i18n/es/resources/moneropedia/fungibility.md b/_i18n/es/resources/moneropedia/fungibility.md
new file mode 100644
index 0000000000000000000000000000000000000000..47ca7d01e0f76ec37a736b3638a49e341e59b6f0
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/fungibility.md
@@ -0,0 +1,16 @@
+---
+layout: moneropedia
+entry: "Fungibility"
+terms: ["fungibility"]
+summary: "property of a currency whereby two units can be substituted in place of one another"
+---
+
+### 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.
+
+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.
+
+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.
+
+{{ page.summary | capitalize }}.
diff --git a/_i18n/es/resources/moneropedia/garlic-encryption.md b/_i18n/es/resources/moneropedia/garlic-encryption.md
new file mode 100644
index 0000000000000000000000000000000000000000..3364f521c3ba5f6aa275ec1ec252756c29d40e84
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/garlic-encryption.md
@@ -0,0 +1,25 @@
+---
+layout: moneropedia
+entry: "Garlic-Encryption"
+tags: ["kovri"]
+terms: ["Garlic-Encryption", "Layered-Encryption"]
+summary: "Layered encryption as implemented in Kovri / I2P"
+---
+
+### The Basics
+
+@garlic-encryption is @I2P's implementation of @message based @layered-encryption (similar to flow-based [Onion-Routing](https://en.wikipedia.org/wiki/Onion_routing)).
+
+By @encrypting @messages in layers, this allows a @message to be routed through a sequence of proxies without allowing the proxies (or any intermediaries) to read the contents of the @message. @Layered-Encryption is a fundamental feature in @Kovri, @I2P, and [Tor](https://torproject.org) and is the cornerstone for securing anonymity within these overlay-networks.
+
+### In-depth information
+
+For @garlic-encryption, the primary difference between @Kovri/@I2P and Tor is:
+
+- @Kovri/@I2P bundles multiple @messages together to form garlic "cloves"
+ - any number of messages can be contained in a "clove" instead of *only* a single message
+- @Kovri/@I2P uses [ElGamal](https://en.wikipedia.org/wiki/ElGamal)/[AES](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard) @encryption for @messages and @transports
+
+### Notes
+
+For details, see @garlic-routing.
diff --git a/_i18n/es/resources/moneropedia/garlic-routing.md b/_i18n/es/resources/moneropedia/garlic-routing.md
new file mode 100644
index 0000000000000000000000000000000000000000..55cd2122f0393c9a1b0d3e8559e7a709be21e5d6
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/garlic-routing.md
@@ -0,0 +1,45 @@
+---
+layout: moneropedia
+entry: "Garlic Routing"
+tags: ["kovri"]
+terms: ["Garlic-Routing"]
+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 @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).
+
+### History
+
+In written form, the term *@garlic-routing* can be seen as early as June of 2000 in Roger Dingledine's [Free Haven Master's thesis](http://www.freehaven.net/papers.html) (Section 8.1.1) as derived from the term Onion Routing.
+
+As recent as October of 2016, [#tor-dev](https://oftc.net/WebChat/) has offered insight into the creation of the term *@garlic-routing*:
+
+[Nick Mathewson](https://en.wikipedia.org/wiki/The_Tor_Project,_Inc):
+>[I think that there was some attempt to come up with a plant whose structure resembled the 'leaky-pipe' topology of tor, but I don't believe we ever settled on one.]
+
+[Roger Dingledine](https://en.wikipedia.org/wiki/Roger_Dingledine):
+>during the free haven brainstorming, there was a moment where we described a routing mechanism, and somebody said "garlic routing!", and everybody laughed.
+so we for sure thought we had invented the name, at the time.
+
+*Note: permission to use the aforementioned quotes was granted by Nick Mathewson and Roger Dingledine*
+
+### In-depth Information
+
+In technical terms, for @Kovri and @I2P, *@garlic-routing* translates to any/all of the following:
+
+- @Layered-Encryption (similar to the @layered-encryption in Onion Routing)
+- Bundling multiple @messages together (garlic cloves)
+- ElGamal/AES @encryption
+
+*Note: though [Tor](https://torproject.org/) uses @layered-encryption, Tor does not use ElGamal and is not message-based.*
+
+**Read more in @garlic-encryption.**
+
+### Notes
+
+- In terms of Onion/Garlic Routing, another way to envision layered @encryption is by replacing the onion/garlic with a [Matryoshka doll](https://en.wikipedia.org/wiki/Matryoshka_doll) - with each outer/inner doll having a lock and public key to the next/previous doll
+- For more technical details on Garlic Routing, read the @Java-I2P entry on [Garlic Routing](https://geti2p.net/en/docs/how/garlic-routing)
diff --git a/_i18n/es/resources/moneropedia/i2np.md b/_i18n/es/resources/moneropedia/i2np.md
new file mode 100644
index 0000000000000000000000000000000000000000..d05c17aab63a037c98932257c714f93285f1151d
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/i2np.md
@@ -0,0 +1,28 @@
+---
+layout: moneropedia
+entry: "I2NP"
+tags: ["kovri"]
+terms: ["I2NP"]
+summary: "The I2P Network Protocol: the mechanism in which I2NP messages are sent over the I2P network"
+---
+
+### The Basics
+
+From @Java-I2P:
+
+>
+@I2NP manages the routing and mixing of messages between routers, as well as the selection of what transports to use when communicating with a peer for which there are multiple common transports supported
+
+### In-depth information
+
+From @Java-I2P:
+
+>
+@I2NP (@I2P Network Protocol) @messages can be used for one-hop, router-to-router, point-to-point @messages. By @encrypting and wrapping @messages in other @messages, they can be sent in a secure way through multiple hops to the ultimate @destination. @I2NP does not specify nor require any particular @transport layer but does require at least one @transport in use.
+
+>
+Whenever a @destination wants to send a message to to another @destination, it provides its local router with both the @destination structure and the raw bytes of the message to be sent. The router then determines where to send it, delivers it through outbound @tunnels, instructing the end point to pass it along to the appropriate inbound @tunnel, where it is passed along again to that @tunnel's end point and made available to the target for reception.
+
+### Notes
+
+Read more about the @I2NP [protocol](https://geti2p.net/en/docs/protocol/i2np) and [specification](https://geti2p.net/spec/i2np).
diff --git a/_i18n/es/resources/moneropedia/i2p.md b/_i18n/es/resources/moneropedia/i2p.md
new file mode 100644
index 0000000000000000000000000000000000000000..2778db301a50271acafe3eead81b704ae4ff333b
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/i2p.md
@@ -0,0 +1,31 @@
+---
+layout: moneropedia
+entry: "I2P"
+tags: ["kovri"]
+terms: ["I2P"]
+summary: "The Invisible Internet Project: an anonymizing overlay network"
+---
+
+### Monero
+
+For Monero's implementation of @I2P, see @Kovri. For a comparison of @I2P to [Tor](https://torproject.org/), read the [Comparison](https://geti2p.net/en/comparison/tor) page.
+
+### The Basics
+
+From @Java-I2P:
+
+>The I2P network provides strong privacy protections for communication over the Internet. Many activities that would risk your privacy on the public Internet can be conducted anonymously inside I2P.
+
+### In-depth information
+
+From @Java-I2P:
+
+>I2P is an anonymous overlay network - a network within a network. It is intended to protect communication from dragnet surveillance and monitoring by third parties such as ISPs.
+
+>I2P is used by many people who care about their privacy: activists, oppressed people, journalists and whistleblowers, as well as the average person.
+
+>No network can be "perfectly anonymous". The continued goal of I2P is to make attacks more and more difficult to mount. Its anonymity will get stronger as the size of the network increases and with ongoing academic review.
+
+### Notes
+
+@I2P documentation and specifications are available [here](https://geti2p.net/docs/).
diff --git a/_i18n/es/resources/moneropedia/i2pcontrol.md b/_i18n/es/resources/moneropedia/i2pcontrol.md
new file mode 100644
index 0000000000000000000000000000000000000000..481d9eae6f086f719e8e57ab5651d2c039875069
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/i2pcontrol.md
@@ -0,0 +1,17 @@
+---
+layout: moneropedia
+entry: "I2PControl"
+tags: ["kovri"]
+terms: ["I2PControl"]
+summary: "An API inteface for Kovri and Java-I2P that allows simple remote control"
+---
+
+### 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.
+
+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.
+
+### In-depth information
+
+Details and specification available on the [I2PControl](https://geti2p.net/en/docs/api/i2pcontrol) page.
diff --git a/_i18n/es/resources/moneropedia/in-net.md b/_i18n/es/resources/moneropedia/in-net.md
new file mode 100644
index 0000000000000000000000000000000000000000..92404f08b6ed21a2181c4ac5c843df89a77544c2
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/in-net.md
@@ -0,0 +1,15 @@
+---
+layout: moneropedia
+entry: "In-net"
+tags: ["kovri"]
+terms: ["In-net"]
+summary: "Within the I2P network"
+---
+
+### The Basics
+
+**In-net** is a [colloquial](https://en.wikipedia.org/wiki/Colloquial) term of which describes activities, protocols, or functionality that exist *only* within the @I2P network.
+
+### In-depth information
+
+Example: *in-net download* would be defined as downloading *only* within @I2P.
diff --git a/_i18n/es/resources/moneropedia/index.md b/_i18n/es/resources/moneropedia/index.md
new file mode 100644
index 0000000000000000000000000000000000000000..4489586c05835703abe0ed61bd85827a223a8986
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/index.md
@@ -0,0 +1,21 @@
+---
+layout: full
+title: "Moneropedia"
+title-pre-kick: "Moneropedia - The "
+title-kick: "Monero Wiki"
+title-post-kick: ""
+kick-class: "softyellow-kicks"
+icon: "icon_wiki"
+attribution: "<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->"
+---
+
+
+<div class="row">
+
+@moneropedia
+
+</div>
+
+<p><a href="https://github.com/monero-project/monero-site/new/master/knowledge-base/moneropedia" class="btn-link btn-auto btn-primary">Add New Entry</a></p>
+
+If there is an entry you'd like to modify or be added, please [open an issue on this website's Github repository](https://github.com/monero-project/monero-site/issues) or submit changes via pull request.
\ No newline at end of file
diff --git a/_i18n/es/resources/moneropedia/java-i2p.md b/_i18n/es/resources/moneropedia/java-i2p.md
new file mode 100644
index 0000000000000000000000000000000000000000..e040579b58e2dd421a585c3c2ef0bc2098770479
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/java-i2p.md
@@ -0,0 +1,15 @@
+---
+layout: moneropedia
+entry: "Java I2P"
+tags: ["kovri"]
+terms: ["Java-I2P"]
+summary: "The original implementation of I2P - written in Java"
+---
+
+### The Basics
+
+The term "Java I2P" is often used to describe the original @I2P implementation currently most known and used today. There are various other @I2P implementations, including @Kovri; all of which look up to the original Java implementation.
+
+### Notes
+
+To download/learn more about the Java implementation, visit their [website](https://geti2p.net/).
diff --git a/_i18n/es/resources/moneropedia/jump-service.md b/_i18n/es/resources/moneropedia/jump-service.md
new file mode 100644
index 0000000000000000000000000000000000000000..228ebb989d41589751aae44bccd3e1dc6fb3fa0d
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/jump-service.md
@@ -0,0 +1,34 @@
+---
+layout: moneropedia
+entry: "Jump Service"
+tags: ["kovri"]
+terms: ["Jump-Service"]
+summary: "An I2P website service that adds addresses to your address book"
+---
+
+### The Basics
+
+In your @I2P configured web browser, you can use a Jump Service to *jump* to an @I2P address that you don't have in your @address-book. Once you've *jumped* to the address, the address will be saved into your @address-book.
+
+### In-depth Information
+
+In an @I2P configured browser, visit: http://stats.i2p/i2p/lookup.html (courtesy of @Java-I2P's lead developer *zzz*)
+
+Then, you'll have two options:
+
+1. *Hostname lookup* the address you wish to visit and then manually copy/paste the result
+2. *Jump* to the @I2P website by entering the @I2P hostname (**recommended**)
+
+### Using hostname lookup
+
+For example, entering `pinkpaste.i2p` into the *Hostname lookup* box (and then submitting) will return:
+
+```
+pinkpaste.i2p=m-HrPrIAsdxts0WM~P4mE8mt9P7g-QTaBvu7Gc6Nl0UX7Vwck-i~RvOPfK6W~kfdRvwhNTqevkBL2UF5l36We02Aiywu7kB2xOHRkze68h-Tg2ewvRVwokohguCD2G3wwAEz~7FVda2avYDCb9-N6TfuzxKLnmhPMvbNSjGL7ZsD2p-h207R3-2kvuMV9bfu-K~w9NI9XJhIyufvUnFYc2jnTVg8PbaR4UP57cNaOO2YIMPkbr6~yTcIu9B1sUfHK6-N~6virQDOxW4M-62rjnZkLpaCtkOsXslmCwZI--TkZ6hKi1kXZvNmJRE1rYfffYRFn38zhaqszeETX8HiIvahZhXF5fNumBziYdmLdw8hkuN1A~emU6Xz9g~a1Ixfsq1Qr~guYoOtaw-0rOFxNRS9yMehE-2LCb8c-cAg6z5OdlN4qJDl~ZHgru4d~EHp~BpAK3v7u2Gi-8l1ygVW-1CHVna~fwnbOPN3ANPwh6~~yUit0Cx1f54XiNRn6-nPBQAEAAcAAA==
+```
+
+Copy/paste this host=@base64-address pairing into your **private** @subscription.
+
+### Directly jumping
+
+For example, entering `pinkpaste.i2p` into the *Jump* box (and then submitting) will automatically redirect you to the website **and** insert the @locally-unique-host into @address-book.
diff --git a/_i18n/es/resources/moneropedia/kovri.md b/_i18n/es/resources/moneropedia/kovri.md
new file mode 100644
index 0000000000000000000000000000000000000000..6002cdd6b71750cae566c3d83759f8e04f02463b
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/kovri.md
@@ -0,0 +1,62 @@
+---
+layout: moneropedia
+entry: "Kovri"
+tags: ["kovri"]
+terms: ["Kovri"]
+summary: "Monero's C++ router implementation of the I2P network"
+---
+
+### The Basics
+
+[Kovri](https://github.com/monero-project/kovri/) is a C++ implementation of the @I2P network. @Kovri is currently in heavy, active development and not yet integrated with Monero. When Kovri is integrated into your Monero @node, your transactions will be more secure than ever before.
+
+### In-depth information
+
+Kovri will protect you and Monero from:
+
+- @Node partitioning attacks
+- Associations between a particular txid and your IP address
+- Mining and/or running a node in highly adversarial environments
+- Metadata leakage (e.g., @OpenAlias lookups)
+
+...and much more.
+
+Read [anonimal's FFS proposal](https://forum.getmonero.org/9/work-in-progress/86967/anonimal-s-kovri-full-time-development-funding-thread) for more details and for reasoning behind the project. Also read the FAQ and User Guide in the [Kovri repository](https://github.com/monero-project/kovri/).
+
+### @Kovri / @I2P Terminology
+
+#### Client + API
+
+- @Address-Book
+- @Base32-address
+- @Base64-address
+- @Canonically-unique-host
+- @Eepsite (@Hidden-Service, @Garlic-Site, @Garlic-Service)
+- @I2PControl
+- @Jump-Service
+- @Locally-unique-host
+- @Reseed
+- @Subscription
+
+#### Core + Router
+
+- @Clearnet
+- @Data-Directory
+- @Destination
+- @Encryption
+- @Floodfill
+- @Garlic-Encryption
+- @Garlic-Routing
+- @I2NP
+- @In-net
+- @Java-I2P
+- @Layered-Encryption
+- @Lease
+- @LeaseSet
+- @Message @Messages
+- @NTCP
+- @Network-Database
+- @Router-Info
+- @SSU
+- @Transports
+- @Tunnel
diff --git a/_i18n/es/resources/moneropedia/lease-set.md b/_i18n/es/resources/moneropedia/lease-set.md
new file mode 100644
index 0000000000000000000000000000000000000000..99165a037191f77094473ec8628120eeee9dfcd6
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/lease-set.md
@@ -0,0 +1,25 @@
+---
+layout: moneropedia
+entry: "Lease-Set"
+tags: ["kovri"]
+terms: ["LeaseSet", "LeaseSets"]
+summary: "Contains all currently authorized Leases for a particular I2P Destination"
+---
+
+### The Basics
+
+A Lease-Set contains a set of authorized @leases (and other related information) for a particular @destination.
+
+### In-depth information
+
+A Lease-Set contains:
+
+- all of the currently authorized @leases for a particular @destination
+- the public key to which garlic messages can be encrypted (see @garlic-routing)
+- the signing public key that can be used to revoke this particular version of the structure
+
+The Lease-Set is one of the two structures stored in the @network-database (the other being @router-info), and is keyed under the SHA256 of the contained @destination.
+
+### Notes
+
+For further details, read @Java-I2P's [LeaseSet](https://geti2p.net/en/docs/how/network-database#leaseSet)
diff --git a/_i18n/es/resources/moneropedia/lease.md b/_i18n/es/resources/moneropedia/lease.md
new file mode 100644
index 0000000000000000000000000000000000000000..d3cdc5451462953f08a56740ec3dec345e87849d
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/lease.md
@@ -0,0 +1,15 @@
+---
+layout: moneropedia
+entry: "Lease"
+tags: ["kovri"]
+terms: ["Lease", "Leases"]
+summary: "Authorizes an I2P tunnel to receive messages targeting a destination"
+---
+
+### The Basics
+
+A lease defines the authorization for a particular @I2P @tunnel to receive a @messages targeting a @destination.
+
+### In-depth information
+
+For further details, read @Java-I2P's [Lease](https://geti2p.net/spec/common-structures#lease)
diff --git a/_i18n/es/resources/moneropedia/locally-unique-host.md b/_i18n/es/resources/moneropedia/locally-unique-host.md
new file mode 100644
index 0000000000000000000000000000000000000000..3ce7f8605a072da5eb42b562f7284329d998312a
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/locally-unique-host.md
@@ -0,0 +1,22 @@
+---
+layout: moneropedia
+entry: "Locally-unique host"
+tags: ["kovri"]
+terms: ["Locally-unique-host"]
+summary: "A host defined by you and resolved only by you"
+---
+
+### The Basics
+
+A locally-unique host is a [FQDN](https://en.wikipedia.org/wiki/FQDN) defined by **you** and resolved only by you; similar to how a [hosts file](https://en.wikipedia.org/wiki/etc/hosts) is implemented. Not to be confused with @canonically-unique-host.
+
+### In-depth information
+
+You have the option to share your interpretation of how the host is resolved (e.g., `localhost` always resolves to `127.0.0.1`) but the resolution is not canonically enforced (e.g., someone else can map `localhost` to any arbitrary IP address).
+
+Hosts in a public subscription can be considered @canonically-unique-host's within the @I2P network but, ultimately, you are free to re-define them as you wish.
+
+### Notes
+
+- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
+- @I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
diff --git a/_i18n/es/resources/moneropedia/message.md b/_i18n/es/resources/moneropedia/message.md
new file mode 100644
index 0000000000000000000000000000000000000000..c9504d54ef3cf16bf9a2f9f94d589e9543e294a1
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/message.md
@@ -0,0 +1,33 @@
+---
+layout: moneropedia
+entry: "Message"
+tags: ["kovri"]
+terms: ["Message", "Messages"]
+summary: "The mechanisms in which information travels within I2P"
+---
+
+### The Basics
+
+*Messages* (which exist on top of the @transports layer), contain varying types of information that are needed for the network but, most importantly, everything you see, do, send, or receive, will come and go in the form of *messages*.
+
+There are 2 essential types of *messages* in @I2P:
+
+- @Tunnel messages
+- @I2NP messages
+
+Essentially: *@tunnel messages* **contain** @I2NP **message fragments** which are then [reassembled](https://geti2p.net/en/docs/tunnels/implementation) at certain points within a @tunnel's path.
+
+### In-depth information
+
+@I2NP messages have a close relationship with @tunnel @messages so it is easy to get the term *messages* confused when reading @Java-I2P specifications:
+
+>
+1. First, the tunnel gateway accumulates a number of I2NP messages and preprocesses them into tunnel messages for delivery.
+2. Next, that gateway encrypts that preprocessed data, then forwards it to the first hop.
+3. That peer, and subsequent tunnel participants, unwrap a layer of the encryption, verifying that it isn't a duplicate, then forward it on to the next peer.
+4. Eventually, the tunnel messages arrive at the endpoint where the I2NP messages originally bundled by the gateway are reassembled and forwarded on as requested.
+
+### Notes
+
+- @I2NP @messages need to be fragmented because they are variable in size (from 0 to almost 64 KB) and @tunnel @messages are fixed-size (approximately 1 KB).
+- For details and specifications, visit the [I2NP spec](https://geti2p.net/spec/i2np) and [Tunnel Message spec](https://geti2p.net/spec/tunnel-message)
diff --git a/_i18n/es/resources/moneropedia/miners.md b/_i18n/es/resources/moneropedia/miners.md
new file mode 100644
index 0000000000000000000000000000000000000000..5937ce6d5ec07ce27cd31fe4250d8facb96e07ff
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/miners.md
@@ -0,0 +1,20 @@
+---
+layout: moneropedia
+entry: "Mining"
+terms: ["mining", "miner", "miners"]
+summary: "the process of cryptographically computing a mathematical proof for a block, containing a number of transactions, which is then added to the blockchain"
+---
+
+### 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.
+
+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.
+
+
+
+{{ page.summary | capitalize }}.
diff --git a/_i18n/es/resources/moneropedia/mnemonicseed.md b/_i18n/es/resources/moneropedia/mnemonicseed.md
new file mode 100644
index 0000000000000000000000000000000000000000..608f8d8bd28fc88dbdf27cc667856d95536f5506
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/mnemonicseed.md
@@ -0,0 +1,20 @@
+---
+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"
+---
+
+### The Basics
+
+{{ page.summary | capitalize }}. This 25-word phrase (13 words in the case of MyMonero) has all the information needed to view and spend funds from a Monero @account.
+
+### In-depth Information
+
+In the official wallet, the mnemonic seed comprises 25 words with the last word being used as a checksum. Those words correspond to a 256-bit integer, which is the account's *private* @spend-key. The *private* @view-key is derived by hashing the private spend key with Keccak-256, producing a second 256-bit integer. The corresponding *public* keys are then derived from the private keys.
+
+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!
+
+By creating a cold, or @paper-wallet you can safely store Moneroj.
diff --git a/_i18n/es/resources/moneropedia/network-database.md b/_i18n/es/resources/moneropedia/network-database.md
new file mode 100644
index 0000000000000000000000000000000000000000..a5bb078c35c3e207f6d2862d45d7b8661a7a837d
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/network-database.md
@@ -0,0 +1,25 @@
+---
+layout: moneropedia
+entry: "Network Database"
+tags: ["kovri"]
+terms: ["Network-Database"]
+summary: "A distributed database which contains needed router information so the network can stay intact"
+---
+
+### The Basics
+
+@network-database is a [distributed database](https://en.wikipedia.org/wiki/Distributed_database) which contains router information that peers must use so the network can stay intact.
+
+### In-depth information
+
+From @Java-I2P:
+
+>
+@I2P's @network-database is a specialized distributed database, containing just two types of data - router contact information (@Router-Infos) and @destination contact information (@LeaseSets). Each piece of data is signed by the appropriate party and verified by anyone who uses or stores it. In addition, the data has liveliness information within it, allowing irrelevant entries to be dropped, newer entries to replace older ones, and protection against certain classes of attack.
+
+>
+The @network-database is distributed with a simple technique called "@floodfill", where a subset of all routers, called "@floodfill routers", maintains the distributed database.
+
+### Notes
+
+Read [Network-Database](https://geti2p.net/en/docs/how/network-database) for details.
diff --git a/_i18n/es/resources/moneropedia/node.md b/_i18n/es/resources/moneropedia/node.md
new file mode 100644
index 0000000000000000000000000000000000000000..dde76903ff7400e62eb556a8b8faa7ec348825f0
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/node.md
@@ -0,0 +1,25 @@
+---
+layout: moneropedia
+entry: "Node"
+terms: ["node", "nodes", "full-node", "full-nodes"]
+summary: "a device on the Internet running the Monero software, with a full copy of the Monero blockchain, actively assisting the Monero network"
+---
+
+### The Basics
+
+{{ page.summary | capitalize }}.
+
+### 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).
+
+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.
+
+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.
+
+---
+
+##### Other Resources
+<sub>1. *Fluffypony gives a great explanation of why mandatory hardforks are good for Monero.* ([Monero Missives for the Week of 2016-06-20](https://getmonero.org/2016/06/20/monero-missive-for-the-week-of-2016-06-20.html))</sub>
diff --git a/_i18n/es/resources/moneropedia/ntcp.md b/_i18n/es/resources/moneropedia/ntcp.md
new file mode 100644
index 0000000000000000000000000000000000000000..69f3152c0be355a7ab283d2a9f15dd90aed73e66
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/ntcp.md
@@ -0,0 +1,34 @@
+---
+layout: moneropedia
+entry: "NTCP"
+tags: ["kovri"]
+terms: ["NTCP"]
+summary: "NIO-Based TCP (Non-blocking I/O based TCP): one of two Kovri transports"
+---
+
+### The Basics
+
+*NIO-Based TCP (Non-blocking I/O based TCP)* is one of two encrypted @transports for @Kovri.
+
+Similar to @SSU, @NTCP's *primary* purpose is to securely transmit @in-net @I2NP messages through @tunnels but, unlike @SSU, @NTCP functions solely over encrypted [TCP](https://en.wikipedia.org/wiki/Transmission_Control_Protocol).
+
+### In-depth information
+
+ - Passes along individual @I2NP messages (both Standard and Time Sync) after:
+ - TCP has been established
+ - Establishment Sequence has been completed
+ - Uses the following @encryption:
+ - 2048-bit [Diffie-Hellman](https://en.wikipedia.org/wiki/Diffie-hellman)
+ - [AES-256](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard)/[CBC](https://en.wikipedia.org/wiki/Block_cipher_modes_of_operation)
+ - Establishment Sequence has the following *states*:
+ - Pre-establishment
+ - Establishment
+ - Post-establishment or "Established"
+ - Uses the following from the @network-database:
+ - Transport name: NTCP
+ - Host: IP (IPv4 or IPv6) or host name (shortened IPv6 address (with "::") is allowed)
+ - Port: 1024 - 65535
+
+### Notes
+
+For further details, read @Java-I2P's [NTCP](https://geti2p.net/en/docs/transport/ntcp)
diff --git a/_i18n/es/resources/moneropedia/openalias.md b/_i18n/es/resources/moneropedia/openalias.md
new file mode 100644
index 0000000000000000000000000000000000000000..2410130cb910285cdf3ab0f02371d44cdd63183a
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/openalias.md
@@ -0,0 +1,20 @@
+---
+layout: moneropedia
+entry: "OpenAlias"
+terms: ["OpenAlias"]
+summary: "a standard that allows you to use an email or domain syntax to pay someone instead of an address, eg. donate@getmonero.org or donate.getmonero.org"
+---
+
+### The Basics
+
+The Monero Core Team released a standard called OpenAlias which permits much more human-readable addresses and "squares" the Zooko's triangle. OpenAlias can be used for any cryptocurrency and is already implemented in Monero, Bitcoin (in latest Electrum versions) and HyperStake.
+
+OpenAlias seeks to provide a way to simplify aliasing amidst a rapidly shifting technology climate. Users are trying to cross the bridge to private and cryptographically secure infrastructure and systems, but many of them have just barely started remembering the email addresses of their friends and family.
+
+As part of the ongoing development of the Monero cryptocurrency project, we asked ourselves: how can we simplify payments for users unfamiliar with cryptocurrency? Monero stealth addresses are at least 95 characters long - memorizing them is not an option, and asking someone to send a payment to <95-character-string> is only going to lead to confusion.
+
+At its most basic, OpenAlias is a TXT DNS record on a FQDN (fully qualified domain name). By combining this with DNS-related technologies we have created an aliasing standard that is extensible for developers, intuitive and familiar for users, and can interoperate with both centralized and decentralized domain systems.
+
+{{ page.summary | capitalize }}.
+
+More information can be found on the [OpenAlias page](/knowledge-base/openalias) or on the [OpenAlias website](https://openalias.org)
diff --git a/_i18n/es/resources/moneropedia/paperwallet.md b/_i18n/es/resources/moneropedia/paperwallet.md
new file mode 100644
index 0000000000000000000000000000000000000000..95ff00baa4b55b875a45d3c487b1c3abb097753c
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/paperwallet.md
@@ -0,0 +1,7 @@
+---
+layout: moneropedia
+entry: "Paper Wallet"
+terms: ["paperwallet", "paperwallets", "paper-wallet", "paper-wallets"]
+summary: "A paper wallet stores the information necessary to send and receive Monero"
+---
+
diff --git a/_i18n/es/resources/moneropedia/paymentid.md b/_i18n/es/resources/moneropedia/paymentid.md
new file mode 100644
index 0000000000000000000000000000000000000000..fba888fa972960f62a18a47dd5c0404f6cc21d37
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/paymentid.md
@@ -0,0 +1,25 @@
+---
+layout: moneropedia
+entry: "Payment ID"
+terms: ["payment-ID", "payment-IDs"]
+summary: "an optional flag that is added to identify transactions to merchants, consisting of 64 hexadecimal characters"
+---
+
+### The Basics
+
+Payment ID is an **arbitrary** and **optional** transaction attachment that consists of 32 bytes (64 hexadecimal characters) or 8 bytes (in the case of integrated addresses).
+
+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
+
+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.
+
+### 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:
+
+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/_i18n/es/resources/moneropedia/pedersen-commitment.md b/_i18n/es/resources/moneropedia/pedersen-commitment.md
new file mode 100644
index 0000000000000000000000000000000000000000..a7ff98bab804cd9a190ae9dcea0c77fe349f4631
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/pedersen-commitment.md
@@ -0,0 +1,24 @@
+---
+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."
+---
+
+### The Basics
+
+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
+
+As long as the encrypted output amounts created, which include an output for the recipient and a change output back to the sender, and the unencrypted transaction fee is equal to the sum of the inputs that are being spent, it is a legitimate transaction and can be confirmed to not be creating Monero out of thin air.
+
+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.
+
+### 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/_i18n/es/resources/moneropedia/reseed.md b/_i18n/es/resources/moneropedia/reseed.md
new file mode 100644
index 0000000000000000000000000000000000000000..eb3b5d986adfd149d0e58eb9098682154136d6ef
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/reseed.md
@@ -0,0 +1,17 @@
+---
+layout: moneropedia
+entry: "Reseed"
+tags: ["kovri"]
+terms: ["Reseed"]
+summary: "The method of which Kovri uses to bootstrap into the I2P network"
+---
+
+### The Basics
+
+When you start @Kovri for the first time (or if it's been offline for a long time), @Kovri will need a list of peers to connect to so it can [bootstrap](https://en.wikipedia.org/wiki/Bootstrap) into the @I2P network. @Kovri gets these peers from a special file stored on a reseed server. On this file are all the various pieces of information @Kovri needs in order to connect with @I2P peers.
+
+### In-depth information
+
+@Kovri has a list of [hard-coded](https://en.wikipedia.org/wiki/Hard-coded) reseed servers available to fetch from. These servers securely serve an [SU3](https://geti2p.net/spec/updates#su3) file (signed with a cryptographic @signature) over @clearnet with [HTTPS](https://en.wikipedia.org/wiki/HTTPS). This SU3 file contains information that's used to verify both the integrity of the file and its content.
+
+Aside from the technical elements needed to verify and process the file, the file's main contents consist of a series of @router-info files which @Kovri and @I2P routers use to locate and communicate with other @I2P peers. These peers are then stored into a @network-database.
diff --git a/_i18n/es/resources/moneropedia/ring-size.md b/_i18n/es/resources/moneropedia/ring-size.md
new file mode 100644
index 0000000000000000000000000000000000000000..a1601651b0994211d852fae4354b65fb86a36cc4
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/ring-size.md
@@ -0,0 +1,11 @@
+---
+layout: moneropedia
+entry: "Ring Size"
+terms: ["ring-size"]
+summary: "total number of possible signers in a ring signature"
+---
+
+### The Basics
+Ring size refers to the total number of possible signers in a @ring-signature. If a ring size of 4 is selected for a given @transaction, this means that there are 3 foreign outputs in addition to your “real†output. A higher ring size number will typically provide more privacy than a lower number. However, reusing an odd, recognizable ring size number for transactions could possibly make transactions stand out.
+
+`Ring size = foreign outputs + 1 (your output)`
\ No newline at end of file
diff --git a/_i18n/es/resources/moneropedia/ringCT.md b/_i18n/es/resources/moneropedia/ringCT.md
new file mode 100644
index 0000000000000000000000000000000000000000..77b9bf3297b0ad2eb2aae23896f6ed936799f792
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/ringCT.md
@@ -0,0 +1,24 @@
+---
+layout: moneropedia
+entry: "Ring CT"
+terms: ["ringCT", "ring-CT"]
+summary: "a way to hide the amount sent in a Monero transaction"
+---
+
+### The Basics
+RingCT, short for Ring Confidential Transactions, is how transaction amounts are hidden in Monero.
+
+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.
+
+For more information, please read the creator Shen Noether's paper [here](https://eprint.iacr.org/2015/1098).
+
+
+{{ page.summary | capitalize }}.
+
+
+
+
+
+
diff --git a/_i18n/es/resources/moneropedia/ringsignatures.md b/_i18n/es/resources/moneropedia/ringsignatures.md
new file mode 100644
index 0000000000000000000000000000000000000000..fee368c89b6b6f1be32b1edf6213fdd1c56b75b3
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/ringsignatures.md
@@ -0,0 +1,18 @@
+---
+layout: moneropedia
+entry: "Ring Signature"
+terms: ["ring-signature", "ring-signatures"]
+summary: "a group of cryptographic signatures with at least one real participant, but no way to tell which in the group is the real one as they all appear valid"
+---
+
+### The Basics
+
+In cryptography, a ring signature is a type of digital signature that can be performed by any member of a group of users that each have keys. Therefore, a message signed with a ring signature is endorsed by someone in a particular group of people. One of the security properties of a ring signature is that it should be computationally infeasible to determine *which* of the group members' keys was used to produce the signature.
+
+For instance, a ring signature could be used to provide an anonymous signature from "a high-ranking White House official", without revealing which official signed the message. Ring signatures are right for this application because the anonymity of a ring signature cannot be revoked, and because the group for a ring signature can be improvised (requires no prior setup).
+
+### 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).
+
+To read how Monero gives you privacy by default (unlinkability), see @stealth-addresses.
\ No newline at end of file
diff --git a/_i18n/es/resources/moneropedia/router-info.md b/_i18n/es/resources/moneropedia/router-info.md
new file mode 100644
index 0000000000000000000000000000000000000000..f7c45c0608fb4337aa81a2d7f00fed97752387c1
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/router-info.md
@@ -0,0 +1,68 @@
+---
+layout: moneropedia
+entry: "Router-Info"
+tags: ["kovri"]
+terms: ["Router-Info", "Router-infos"]
+summary: "A data structure or file which contains an I2P peer's needed network information"
+---
+
+### The Basics
+
+@Router-Info is a data structure (periodically written to a [binary file](https://en.wikipedia.org/wiki/Binary_file)) which contains all needed information to locate, identify, and communicate with an @I2P peer. @Router-Info includes IP address, router identity, other misc. technical details; is needed for @network-database and is published to @floodfill routers.
+
+### In-depth information
+
+In human-readable form, Router-Info may look like this:
+
+```
+Identity: [RouterIdentity:
+Hash: nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=
+Certificate: [Certificate: type: Key certificate
+Crypto type: 0
+Sig type: 7 (EdDSA_SHA512_Ed25519)]
+PublicKey: [PublicKey: size: 256]
+SigningPublicKey: [SigningPublicKey EdDSA_SHA512_Ed25519: size: 32]
+Padding: 96 bytes]
+Signature: [Signature EdDSA_SHA512_Ed25519: size: 64]
+Published: Sun Oct 09 01:34:59 UTC 2016
+Options (5):
+ [caps] = [LfR]
+ [netId] = [2]
+ [netdb.knownLeaseSets] = [37]
+ [netdb.knownRouters] = [2435]
+ [router.version] = [0.9.26]
+Addresses (4):
+[RouterAddress:
+Type: SSU
+Cost: 4
+Options (5):
+ [caps] = [BC]
+ [host] = [2a01:e35:8b5c:b240:71a2:6750:8d4:47fa]
+ [key] = [nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=]
+ [mtu] = [1472]
+ [port] = [22244]]
+[RouterAddress:
+Type: NTCP
+Cost: 9
+Options (2):
+ [host] = [2a01:e35:8b5c:b240:71a2:6750:8d4:47fa]
+ [port] = [22244]]
+[RouterAddress:
+Type: SSU
+Cost: 6
+Options (4):
+ [caps] = [BC]
+ [host] = [88.181.203.36]
+ [key] = [nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=]
+ [port] = [22244]]
+[RouterAddress:
+Type: NTCP
+Cost: 11
+Options (2):
+ [host] = [88.181.203.36]
+ [port] = [22244]]]
+```
+
+### Notes
+
+For details and specification, visit @Java-I2P [Network Database](https://geti2p.net/en/docs/how/network-database) page.
diff --git a/_i18n/es/resources/moneropedia/scalability.md b/_i18n/es/resources/moneropedia/scalability.md
new file mode 100644
index 0000000000000000000000000000000000000000..efce0202090b89cfc7536cfbfe2e80286ff4209d
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/scalability.md
@@ -0,0 +1,10 @@
+---
+layout: moneropedia
+entry: "Scalability"
+terms: ["scalability"]
+summary: "Growth potential of Monero, resources required, and methods of increasing efficiency"
+---
+
+### The Basics
+
+Monero has no hardcoded maximum block size, which means that unlike Bitcoin it does not have a 1 MB block size limit preventing scaling. However, a block reward penalty mechanism is built into the protocol to avoid a too excessive block size increase: The new block's size (NBS) is compared to the median size M100 of the last 100 blocks. If NBS>M100, the block reward gets reduced in quadratic dependency of how much NBS exceeds M100. E.g. if NBS is [10%, 50%, 80%, 100%] greater than M100, the nominal block reward gets reduced by [1%, 25%, 64%, 100%]. Generally, blocks greater than 2*M100 are not allowed, and blocks <= 60kB are always free of any block reward penalties.
diff --git a/_i18n/es/resources/moneropedia/signature.md b/_i18n/es/resources/moneropedia/signature.md
new file mode 100644
index 0000000000000000000000000000000000000000..638b7c5bb26130703eead4b6f5585c6c18bef847
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/signature.md
@@ -0,0 +1,10 @@
+---
+layout: moneropedia
+entry: "Cryptographic Signature"
+terms: ["signature", "signatures"]
+summary: "a cryptographic method for proving ownership of a piece of information, as well as proving that the information has not been modified after being signed"
+---
+
+### The Basics
+
+{{ page.summary | capitalize }}.
\ No newline at end of file
diff --git a/_i18n/es/resources/moneropedia/smartmining.md b/_i18n/es/resources/moneropedia/smartmining.md
new file mode 100644
index 0000000000000000000000000000000000000000..c4f7a6d2e6af487b0dc8a7c205515539eb653f36
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/smartmining.md
@@ -0,0 +1,17 @@
+---
+layout: moneropedia
+entry: "Smart Mining"
+terms: ["smart-mining"]
+summary: "a process of having a throttled miner mine when it otherwise does not cause drawbacks"
+---
+
+### The Basics
+
+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/_i18n/es/resources/moneropedia/spendkey.md b/_i18n/es/resources/moneropedia/spendkey.md
new file mode 100644
index 0000000000000000000000000000000000000000..d57544d1ad9e636ad97f998ff3df4b66182fc39b
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/spendkey.md
@@ -0,0 +1,16 @@
+---
+layout: moneropedia
+entry: "Spend Key"
+terms: ["spend-key", "spend-keys"]
+summary: "one of the two pairs of private and public cryptographic keys that each account has, with the *private* spend key used to spend any funds in the account"
+---
+
+### The Basics
+
+{{ page.summary | capitalize }}.
+
+### In-depth Information
+
+The *private* spend key is a 256-bit integer that is used to sign Monero transactions. With the current deterministic key derivation method of the official wallet, the private spend key is also an alternate representation of the @mnemonic-seed. It can be used to derive all other account keys.
+
+
diff --git a/_i18n/es/resources/moneropedia/ssu.md b/_i18n/es/resources/moneropedia/ssu.md
new file mode 100644
index 0000000000000000000000000000000000000000..665f9c443a42ae39f281fb0b135145100c5a45c3
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/ssu.md
@@ -0,0 +1,26 @@
+---
+layout: moneropedia
+entry: "SSU"
+tags: ["kovri"]
+terms: ["SSU"]
+summary: "Secure Semi-reliable UDP: one of two Kovri transports"
+---
+
+### The Basics
+
+*Secure Semi-reliable UDP* is one of two encrypted @transports for @Kovri.
+
+Similar to @NTCP, @SSU's *primary* purpose is to securely transmit @in-net @I2NP messages through @tunnels but, unlike @NTCP, @SSU functions solely over encrypted [UDP](https://en.wikipedia.org/wiki/User_Datagram_Protocol).
+
+### In-depth information
+
+- Like @NTCP, @SSU is a connection-oriented, point-to-point data transport
+- Termed *semi-reliable* because @SSU will repeatedly retransmit *unacknowledged* messages (up to maximum number then dropped)
+- @SSU also provides several unique services (in addition to its function as a @transport layer):
+ - IP detection (local inspection or with [peer testing](https://geti2p.net/en/docs/transport/ssu#peerTesting))
+ - [NAT](https://en.wikipedia.org/wiki/Network_address_translation) traversal (using [introducers](https://geti2p.net/en/docs/transport/ssu#introduction))
+ - [Firewall](https://en.wikipedia.org/wiki/Firewall_%28computing%29) status and, if implemented, @SSU can notify @NTCP if the external address or firewall status changes
+
+### Notes
+
+For further details, read @Java-I2P's [SSU](https://geti2p.net/en/docs/transport/ssu)
diff --git a/_i18n/es/resources/moneropedia/stealthaddress.md b/_i18n/es/resources/moneropedia/stealthaddress.md
new file mode 100644
index 0000000000000000000000000000000000000000..61892d1b23c3bb0cb7d751f8191bccfab9ba90aa
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/stealthaddress.md
@@ -0,0 +1,16 @@
+---
+layout: moneropedia
+entry: "Stealth Address"
+terms: ["stealth-address", "stealth-addresses"]
+summary: "automatic one-time addresses for every transaction"
+---
+
+### The Basics
+
+Stealth addresses are an important part of Monero's inherent privacy. They allow and require the sender to create random one-time addresses for every @transaction on behalf of the recipient. The recipient can publish just one address, yet have all of his/her incoming payments go to unique addresses on the @blockchain, where they cannot be linked back to either the recipient's published address or any other transactions' addresses. By using stealth addresses, only the sender and receiver can determine where a payment was sent.
+
+When you create a Monero account you’ll have a private @view-key, a private @spend-key, and a Public Address. The @spend-key is used to send payments, the @view-key is used to display incoming transactions destined for your account, and the Public Address is for receiving payments. Both the @spend-key and @view-key are used to build your Monero address. You can have a “watch only†wallet that only uses the @view-key. This feature can be used for accounting or auditing purposes but is currently unreliable due to the inability to track outgoing transactions. You can decide who can see your Monero balance by sharing your @view-key. Monero is private by default and optionally semi-transparent!
+
+When using the Monero Wallet all this is handled by the software. Sending Monero is as easy as entering the destination address, the amount, and pressing Send. To recieve Monero, simply provide the sender your Public Address.
+
+To learn how Monero prevents tracking history (untraceability), see @ring-signatures.
diff --git a/_i18n/es/resources/moneropedia/subscription.md b/_i18n/es/resources/moneropedia/subscription.md
new file mode 100644
index 0000000000000000000000000000000000000000..b7411df5bec058a8baae7346e610cfe1f307501f
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/subscription.md
@@ -0,0 +1,47 @@
+---
+layout: moneropedia
+entry: "Subscription"
+tags: ["kovri"]
+terms: ["Subscription"]
+summary: "A file used by address book which contains I2P hosts paired with I2P destinations"
+---
+
+### The Basics
+
+A subscription is a file which contains a list of `.i2p` hosts paired with their respective @destination. Subscriptions are used by the @address-book.
+
+### 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`
+
+More specifically, a subscription pairs a @locally-unique-host to @base64-address.
+
+Example:
+
+```
+anonimal.i2p=AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLEov~usVliTSXCSHuRBOCIwIOuDNU0AbVa4BpIx~2sU4TxKhoaA3zQ6VzINoduTdR2IJhPvI5xzezp7dR21CEQGGTbenDslXeQ4iLHFA2~bzp1f7etSl9T2W9RID-KH78sRQmzWnv7dbhNodMbpO6xsf1vENf6bMRzqD5vgHEHZu2aSoNuPyYxDU1eM6--61b2xp9mt1k3ud-5WvPVg89RaU9ugU5cxaHgR927lHMCAEU2Ax~zUb3DbrvgQBOTHnJEx2Fp7pOK~PnP6ylkYKQMfLROosLDXinxOoSKP0UYCh2WgIUPwE7WzJH3PiJVF0~WZ1dZ9mg00c~gzLgmkOxe1NpFRNg6XzoARivNVB5NuWqNxr5WKWMLBGQ9YHvHO1OHhUJTowb9X90BhtHnLK2AHwO6fV-iHWxRJyDabhSMj1kuYpVUBQAEAAcAAA==
+```
+
+1. `anonimal.i2p` is the @locally-unique-host
+2. `=` is the separator
+3. Everything that remains is the @base64-address
+
+### Subscription types
+
+For @Kovri, there are two types of subscription files: *public* and *private*.
+
+A *public* subscription:
+- is used when bootstrapping to use essential services (IRC, email, Monero, etc.)
+- is static and is refreshed every 12 hours from Monero's @address-book server
+- allows you to safely share the subscription with everyone as it is publically available (anyone who shares the same public subscription will also be able to resolve the same hostname to the same destination as you)
+
+A *private* subscription:
+- is used exclusively by you and is not shared with others unless you explicitly choose to share the file
+- default file is `private_hosts.txt` in your @data-directory
+
+### Updating a private subscription
+
+You can use a @jump-service to manually update your private subscription. The updated subscription will then be fed into the @address-book for you to use.
+
+### Notes
+To learn how to subscribe to multiple subscriptions, see the [user-guide](https://github.com/monero-project/kovri/blob/master/doc/USER_GUIDE.md).
diff --git a/_i18n/es/resources/moneropedia/tail-emission.md b/_i18n/es/resources/moneropedia/tail-emission.md
new file mode 100644
index 0000000000000000000000000000000000000000..019e6fe14fef7e3ea22c02c1a9c995d7b3aa45a7
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/tail-emission.md
@@ -0,0 +1,16 @@
+---
+layout: moneropedia
+entry: "Tail Emission"
+terms: ["Tail-Emission"]
+summary: "the block reward at the end of the emission curve"
+---
+
+### The Basics
+
+Monero block rewards will never drop to zero. Block rewards will gradually drop until tail emission commences at the end of May 2022. At this point, rewards will be fixed at 0.6 XMR per block.
+
+### 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.
+
+Tail emission ensures that a dynamic block size and fee market can develop.
diff --git a/_i18n/es/resources/moneropedia/transaction.md b/_i18n/es/resources/moneropedia/transaction.md
new file mode 100644
index 0000000000000000000000000000000000000000..0064cb50bc7ead40d1fbfc398545cd6b8e1ccbf0
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/transaction.md
@@ -0,0 +1,21 @@
+---
+layout: moneropedia
+entry: "Transactions"
+terms: ["transaction", "transactions"]
+summary: "a cryptographically signed container that details the transfer of Monero to a recipient (or recipients)"
+---
+
+### The Basics
+
+{{ 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.
+
+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).
+
+### In-depth Information
+Every transaction involves two keys: a public @spend-key, and a public @view-key. The destination for an output in a transaction is actually a one-time public key computed from these two keys.
+
+When a wallet is scanning for incoming transactions, every transaction is scanned to see if it is for "you". This only requires your private view key and your public spend key, and this check is immutable and cannot be faked. You cannot receive transactions and identify them without a corresponding private view key.
+
+In order to spend the funds you have to compute a one-time private spend key for that output. This is almost always done automatically by the Monero Wallet software.
diff --git a/_i18n/es/resources/moneropedia/transports.md b/_i18n/es/resources/moneropedia/transports.md
new file mode 100644
index 0000000000000000000000000000000000000000..59504f99c58bc7205dd3283870de2f26f7205494
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/transports.md
@@ -0,0 +1,20 @@
+---
+layout: moneropedia
+entry: "Transports"
+tags: ["kovri"]
+terms: ["Transports", "Transport"]
+summary: "The two encrypted transport layers for Kovri"
+---
+
+### The Basics
+
+@I2P comes with two encrypted transport layer technologies that allow @Kovri to securely use [TCP/IP](https://en.wikipedia.org/wiki/Tcp/ip) connections. These technologies (@SSU and @NTCP) are called *@transports*.
+
+### In-depth information
+
+@SSU is encrypted [UDP](https://en.wikipedia.org/wiki/User_Datagram_Protocol) and @NTCP is encrypted [TCP](https://en.wikipedia.org/wiki/Transmission_Control_Protocol). They provide @encryption at the [transport layer](https://en.wikipedia.org/wiki/Transport_layer) so higher level @messages can be sent through @tunnels across the @I2P network.
+
+### Notes
+
+- Read about @I2P's transports on the [Transport](https://geti2p.net/en/docs/transport) page
+- Read about the transports layer within the [OSI model](https://en.wikipedia.org/wiki/OSI_model)
diff --git a/_i18n/es/resources/moneropedia/tunnel.md b/_i18n/es/resources/moneropedia/tunnel.md
new file mode 100644
index 0000000000000000000000000000000000000000..d22e2b944ab72596fe894d41a941b6c2f5f9d85e
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/tunnel.md
@@ -0,0 +1,37 @@
+---
+layout: moneropedia
+entry: "Tunnel"
+tags: ["kovri"]
+terms: ["Tunnel", "Tunnels"]
+summary: "Uni-directional virtual paths that pass messages through a defined sequence of I2P routers"
+---
+
+### The Basics
+
+When you communicate over @I2P (visit an @eepsite / use a @garlic-service), you'll first need to connect to a peer by using @transports and then build virtual *tunnels*. These virtual tunnels are temporary, uni-directional paths that pass information through a defined sequence of @I2P routers to your @destination. Tunnels are built, and then used, with layered @garlic-encryption and are a general-purpose mechanism to transport all @I2NP @messages.
+
+Each peer builds, at a minimum, *two* uni-directional tunnels: one for **outbound traffic**, and one for **inbound traffic**. These tunnels are classified as either **inbound tunnels** (where @messages come toward the creator of the tunnel) or **outbound tunnels** (where the tunnel creator sends @messages away from the creator of the tunnel). Thus, *four* tunnels are required for a single round-trip @message and reply to your @destination (two for your, two for your destination).
+
+### In-depth information
+
+From @Java-I2P:
+
+>
+Within I2P, @messages are passed in one direction through a virtual tunnel of peers, using whatever means are available to pass the @message on to the next hop. Messages arrive at the tunnel's gateway, get bundled up and/or fragmented into fixed-size @tunnel @messages, and are forwarded on to the next hop in the tunnel, which processes and verifies the validity of the @message and sends it on to the next hop, and so on, until it reaches the @tunnel endpoint. That endpoint takes the messages bundled up by the gateway and forwards them as instructed - either to another router, to another tunnel on another router, or locally.
+
+>
+Tunnels all work the same, but can be segmented into two different groups - inbound tunnels and outbound tunnels. The inbound tunnels have an untrusted gateway which passes messages down towards the tunnel creator, which serves as the tunnel endpoint. For outbound tunnels, the tunnel creator serves as the gateway, passing messages out to the remote endpoint.
+
+>
+The tunnel's creator selects exactly which peers will participate in the tunnel, and provides each with the necessary configuration data. They may have any number of hops. It is the intent to make it hard for either participants or third parties to determine the length of a tunnel, or even for colluding participants to determine whether they are a part of the same tunnel at all (barring the situation where colluding peers are next to each other in the tunnel).
+
+### Notes
+
+From @Java-I2P:
+
+>
+@I2P is an inherently packet switched network, even with these tunnels, allowing it to take advantage of multiple tunnels running in parallel, increasing resilience and balancing load. Even though the tunnels within I2P bear a resemblance to a circuit switched network, everything within I2P is strictly message based - tunnels are merely accounting tricks to help organize the delivery of messages. No assumptions are made regarding reliability or ordering of messages, and retransmissions are left to higher levels (e.g. I2P's client layer streaming library).
+
+### Documentation
+
+For specification and detailed documentation, visit the [Tunnel-Routing](https://geti2p.net/en/docs/how/tunnel-routing) and [Tunnel-Implementation](https://geti2p.net/en/docs/tunnels/implementation) page.
diff --git a/_i18n/es/resources/moneropedia/unlocktime.md b/_i18n/es/resources/moneropedia/unlocktime.md
new file mode 100644
index 0000000000000000000000000000000000000000..08a35f8e0025aa2f825b7f931b04707b8eba7818
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/unlocktime.md
@@ -0,0 +1,14 @@
+---
+layout: moneropedia
+entry: "Transaction Unlock Time"
+terms: ["unlock-time"]
+summary: "a special transaction where the recipient can only spend the funds after a future date, as set by the sender"
+---
+
+### The Basics
+
+{{ page.summary | capitalize }}.
+
+Unlock time allows you to send a transaction to someone, such that they can not spend it until after a certain number of blocks, or until a certain time.
+
+Note that this works differently than Bitcoin's [nLockTime](https://en.bitcoin.it/wiki/NLockTime), in which the transaction is not valid until the given time.
diff --git a/_i18n/es/resources/moneropedia/viewkey.md b/_i18n/es/resources/moneropedia/viewkey.md
new file mode 100644
index 0000000000000000000000000000000000000000..719a96b9943755f98cd661bacc25147cdd3a8957
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/viewkey.md
@@ -0,0 +1,16 @@
+---
+layout: moneropedia
+entry: "View Key"
+terms: ["view-key", "view-keys"]
+summary: "one of two sets of private and public cryptographic keys that each account has, with the private view key required to view all transactions related to the account"
+---
+
+### 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 }}.
diff --git a/_i18n/es/resources/moneropedia/wallet.md b/_i18n/es/resources/moneropedia/wallet.md
new file mode 100644
index 0000000000000000000000000000000000000000..759b018d3d36a750800687d1e14266927a77092f
--- /dev/null
+++ b/_i18n/es/resources/moneropedia/wallet.md
@@ -0,0 +1,19 @@
+---
+layout: moneropedia
+entry: "Wallet"
+terms: ["wallet", "wallets"]
+summary: "A wallet stores the information necessary to send and receive Monero"
+---
+
+### The Basics
+
+A Monero account, or wallet, stores the information necessary to send and receive Moneroj. In addition to sending and receiving, the Monero Wallet software keeps a private history of your transactions and allows you to cryptographically sign messages. It also includes Monero mining software and an address book.
+
+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 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.
+
+Monero accounts and paper-wallets can be stored on any media - paper, USB drive, CD/DVD, or a hardware wallet device (none available for Monero as of June 2017).
+
diff --git a/_i18n/es/resources/research-lab.md b/_i18n/es/resources/research-lab.md
new file mode 100644
index 0000000000000000000000000000000000000000..61b4617ce4512e40cdf792e9f6c693a72a24f31c
--- /dev/null
+++ b/_i18n/es/resources/research-lab.md
@@ -0,0 +1,164 @@
+{% include untranslated.html %}
+<div class="container description">
+<p>Monero is not only committed to making a fungible currency, but also to continued research into the realm of financial privacy as it involves cryptocurrencies. Below you'll find the work of our very own Monero Research Lab, with more papers to come.</p>
+</div>
+
+<section class="container">
+ <div class="row">
+ <!-- left two-thirds block-->
+ <div class="left two-thirds col-lg-8 col-md-8 col-sm-12 col-xs-12">
+ <div class="info-block research-paper">
+ <div class="row center-xs">
+ <div class="col"><h2>Monero Research Lab Papers</h2></div>
+ </div>
+ <div class="tab">
+ <input id="tab-one" type="checkbox" name="tabs" class="accordion" checked="checked">
+ <label for="tab-one" class="accordion">MRL-0001: A Note on Chain Reactions in Traceability in CryptoNote 2.0</label>
+ <div class="tab-content">
+ <p><strong>Abstract:</strong> This research bulletin describes a plausible attack on a ring-signature based
+ anonymity system. We use as motivation the cryptocurrency protocol CryptoNote
+ 2.0 ostensibly published by Nicolas van Saberhagen in 2012. It has been
+ previously demonstrated that the untraceability obscuring a one-time key pair can
+ be dependent upon the untraceability of all of the keys used in composing that
+ ring signature. This allows for the possibility of chain reactions in traceability
+ between ring signatures, causing a critical loss in untraceability across the whole
+ network if parameters are poorly chosen and if an attacker owns a sufficient
+ percentage of the network. The signatures are still one-time, however, and any
+ such attack will still not necessarily violate the anonymity of users. However, such
+ an attack could plausibly weaken the resistance CryptoNote demonstrates against
+ blockchain analysis. This research bulletin has not undergone peer review, and
+ reflects only the results of internal investigation.
+ <br>
+ <br>
+ <a target="_blank" rel="noreferrer noopener" href="https://lab.getmonero.org/pubs/MRL-0001.pdf">Read Paper</a>
+ </p>
+ </div>
+ </div>
+ <div class="tab">
+ <input id="tab-two" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-two" class="accordion">MRL-0002: Counterfeiting via Merkle Tree Exploits within Virtual Currencies Employing the CryptoNote Protocol</label>
+ <div class="tab-content">
+ <p><strong>Abstract:</strong> On 4 September 2014, an unusual and novel attack was executed against the
+ Monero cryptocurrency network. This attack partitioned the network into two
+ distinct subsets which refused to accept the legitimacy of the other subset. This
+ had myriad effects, not all of which are yet known. The attacker had a short
+ window of time during which a sort of counterfeiting could occur, for example.
+ This research bulletin describes deficiencies in the CryptoNote reference code
+ allowing for this attack, describes the solution initially put forth by Rafal Freeman
+ from Tigusoft.pl and subsequently by the CryptoNote team, describes the current
+ fix in the Monero code base, and elaborates upon exactly what the offending
+ block did to the network. This research bulletin has not undergone peer review,
+ and reflects only the results of internal investigation.<br>
+ <br>
+ <a target="_blank" rel="noreferrer noopener" href="https://lab.getmonero.org/pubs/MRL-0002.pdf">Read Paper</a></p>
+
+ </div>
+ </div>
+ <div class="tab">
+ <input id="tab-three" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-three" class="accordion">MRL-0003: Monero is Not That Mysterious</label>
+ <div class="tab-content">
+ <p><strong>Introduction:</strong> Recently, there have been some vague fears about the CryptoNote source code and
+ protocol floating around the internet based on the fact that it is a more complicated
+ protocol than, for instance, Bitcoin. The purpose of this note is to try and clear
+ up some misconceptions, and hopefully remove some of the mystery surrounding
+ Monero Ring Signatures. I will start by comparing the mathematics involved in
+ CryptoNote ring signatures (as described in [CN]) to the mathematics in [FS], on
+ which CryptoNote is based. After this, I will compare the mathematics of the ring
+ signature to what is actually in the CryptoNote codebase.<br>
+ <br>
+ <a target="_blank" rel="noreferrer noopener" href="https://lab.getmonero.org/pubs/MRL-0003.pdf">Read Paper</a></p>
+ </div>
+ </div>
+ <div class="tab">
+ <input id="tab-four" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-four" class="accordion">MRL-0004: Improving Obfuscation in the CryptoNote Protocol</label>
+ <div class="tab-content">
+ <p><strong>Abstract:</strong> We identify several blockchain analysis attacks available to degrade the
+untraceability of the CryptoNote 2.0 protocol. We analyze possible solutions,
+discuss the relative merits and drawbacks to those solutions, and recommend
+improvements to the Monero protocol that will hopefully provide long-term
+resistance of the cryptocurrency against blockchain analysis. Our recommended
+improvements to Monero include a protocol-level network-wide minimum mix-in
+policy of
+n
+= 2
+foreign outputs per ring signature, a protocol-level increase of this
+value to
+n
+= 4
+after two years, and a wallet-level default value of
+n
+= 4
+in the
+interim. We also recommend a torrent-style method of sending Monero output.
+We also discuss a non-uniform, age-dependent mix-in selection method to
+mitigate the other forms of blockchain analysis identified herein, but we make no
+formal recommendations on implementation for a variety of reasons. The
+ramifications following these improvements are also discussed in some detail.
+This research bulletin has not undergone peer review, and reflects only the
+results of internal investigation.<br>
+ <br>
+ <a target="_blank" rel="noreferrer noopener" href="https://lab.getmonero.org/pubs/MRL-0004.pdf">Read Paper</a></p>
+ </div>
+ </div>
+ <div class="tab">
+ <input id="tab-five" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-five" class="accordion">MRL-0005: Ring Signature Confidential Transactions</label>
+ <div class="tab-content">
+ <p><strong>Abstract:</strong> This article introduces a method of hiding transaction amounts in the strongly
+decentralized anonymous cryptocurrency Monero. Similar to Bitcoin, Monero is a
+cryptocurrency which is distributed through a proof of work “mining†process.
+The original Monero protocol was based on CryptoNote, which uses ring
+signatures and one-time keys to hide the destination and origin of transactions.
+Recently the technique of using a commitment scheme to hide the amount of a
+transaction has been discussed and implemented by Bitcoin Core Developer
+Gregory Maxwell. In this article, a new type of ring signature, A Multi-layered
+Linkable Spontaneous Anonymous Group signature is described which allows for
+hidden amounts, origins and destinations of transactions with reasonable
+efficiency and verifiable, trustless coin generation. Some extensions of the
+protocol are provided, such as Aggregate Schnorr Range Proofs, and Ring
+Multisignature. The author would like to note that early drafts of this were
+publicized in the Monero Community and on the bitcoin research irc channel.
+Blockchain hashed drafts are available in [14] showing that this work was started
+in Summer 2015, and completed in early October 2015. An eprint is also
+available at
+http://eprint.iacr.org/2015/1098
+.<br>
+ <br>
+ <a href="https://lab.getmonero.org/pubs/MRL-0005.pdf" target="_blank" rel="noreferrer noopener">Read Paper</a></p>
+ </div>
+ </div>
+ </div>
+ </div>
+ <!-- end left two-thirds block-->
+
+ <!-- right one-third block-->
+ <div class="right one-third col-lg-4 col-md-4 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Cryptonote Whitepapers</h2>
+ </div>
+
+ </div>
+<div markdown="1">
+
+[Cryptonote Whitepaper](https://cryptonote.org/whitepaper.pdf)
+
+This is the original cryptonote paper written by the cryptonote team. Reading it will give an understanding about how the cryptonote algorithm works in general.
+
+[Annotated Whitepaper](https://downloads.getmonero.org/whitepaper_annotated.pdf)
+
+The Monero Research Lab released an annotated version of the cryptonote whitepaper. This is sort of like an informal review of the claims that are made line-by-line of the whitepaper. It also explains some of the harder concepts in relatively easy to understand terms.
+
+[Brandon Goodell's Whitepaper Review](https://downloads.getmonero.org/whitepaper_review.pdf)
+
+This paper is a formal review of the original cryptonote paper by MRL researcher Brandon Goodell. He takes an in-depth look at the claims and mathematics presented in the cryptonote paper.
+
+</div>
+ </div>
+ </div>
+ <!-- end right one-third block-->
+ </div>
+</section>
diff --git a/_i18n/es/resources/roadmap.md b/_i18n/es/resources/roadmap.md
new file mode 100644
index 0000000000000000000000000000000000000000..267b386742f187ac792183bc1c7cb44c946f8421
--- /dev/null
+++ b/_i18n/es/resources/roadmap.md
@@ -0,0 +1,130 @@
+{% include untranslated.html %}
+<div class="roadmap">
+<div class="text-center pre-roadmap container">
+ <div class="row">
+ <div class="col-xs-4">
+ <li class="completed"></li>
+ <p>Completed task</p>
+ </div>
+ <div class="col-xs-4">
+ <li class="ongoing"></li>
+ <p>Ongoing task</p>
+ </div>
+ <div class="col-xs-4">
+ <li class="upcoming"></li>
+ <p>Upcoming task</p>
+ </div>
+ </div>
+</div>
+<section class="container">
+ <div class="row">
+ <div class="col-lg-12 col-md-12 col-sm-12 col-xs-12">
+ <div class="tabPanel-widget">
+ <label for="tab-1" tabindex="0"></label>
+ <input id="tab-1" type="radio" name="tabs" aria-hidden="true">
+ <h2>2014</h2>
+ <div class="tabPanel-content">
+ {% for toplevel in site.data.lang[site.lang].roadmap %}
+ {% if toplevel.year == 2014 %}
+ {% for roadlist in toplevel.accomplishments %}
+ <div class="row start-xs middle-xs">
+ <div class="col-xs-1">
+ <span class="{{roadlist.status}}"></span>
+ </div>
+ <div class="col-xs-11">
+ <p>{{roadlist.date}}: {{roadlist.name}}</p>
+ </div>
+ </div>
+ {%endfor%}
+ {%endif%}
+ {%endfor%}
+ </div>
+ <label for="tab-2" tabindex="0"></label>
+ <input id="tab-2" type="radio" name="tabs" aria-hidden="true">
+ <h2>2015</h2>
+ <div class="tabPanel-content">
+ {% for toplevel in site.data.lang[site.lang].roadmap %}
+ {% if toplevel.year == 2015 %}
+ {% for roadlist in toplevel.accomplishments %}
+ <div class="row start-xs middle-xs">
+ <div class="col-xs-1">
+ <span class="{{roadlist.status}}"></span>
+ </div>
+ <div class="col-xs-11">
+ <p>{{roadlist.date}}: {{roadlist.name}}</p>
+ </div>
+ </div>
+ {%endfor%}
+ {%endif%}
+ {%endfor%}
+ </div>
+ <label for="tab-3" tabindex="0"></label>
+ <input id="tab-3" type="radio" name="tabs" aria-hidden="true">
+ <h2>2016</h2>
+ <div class="tabPanel-content">
+ {% for toplevel in site.data.lang[site.lang].roadmap %}
+ {% if toplevel.year == 2016 %}
+ {% for roadlist in toplevel.accomplishments %}
+ <div class="row start-xs middle-xs">
+ <div class="col-xs-1">
+ <span class="{{roadlist.status}}"></span>
+ </div>
+ <div class="col-xs-11">
+ <p>{{roadlist.date}}: {{roadlist.name}}</p>
+ </div>
+ </div>
+ {%endfor%}
+ {%endif%}
+ {%endfor%}
+ </div>
+ <label for="tab-4" tabindex="0"></label>
+ <input id="tab-4" type="radio" name="tabs" aria-hidden="true" checked>
+ <h2>2017</h2>
+ <div class="tabPanel-content">
+ {% for toplevel in site.data.lang[site.lang].roadmap %}
+ {% if toplevel.year == 2017 %}
+ {% for roadlist in toplevel.accomplishments %}
+ <div class="row start-xs middle-xs">
+ <div class="col-xs-1">
+ <span class="{{roadlist.status}}"></span>
+ </div>
+ <div class="col-xs-11">
+ {% if roadlist.date %}
+ <p>{{roadlist.date}}: {{roadlist.name}}</p>
+ {%else%}
+ <p>{{roadlist.name}}</p>
+ {%endif%}
+ </div>
+ </div>
+ {%endfor%}
+ {%endif%}
+ {%endfor%}
+ </div>
+ <label for="tab-5" tabindex="0"></label>
+ <input id="tab-5" type="radio" name="tabs" aria-hidden="true">
+ <h2>Future</h2>
+ <div class="tabPanel-content">
+ {% for toplevel in site.data.lang[site.lang].roadmap %}
+ {% if toplevel.year == 2018 %}
+ {% for roadlist in toplevel.accomplishments %}
+ <div class="row start-xs">
+ <div class="col-xs-1">
+ <span class="{{roadlist.status}}"></span>
+ </div>
+ <div class="col-xs-11">
+ {% if roadlist.date %}
+ <p>{{roadlist.date}}: {{roadlist.name}}</p>
+ {%else%}
+ <p>{{roadlist.name}}</p>
+ {%endif%}
+ </div>
+ </div>
+ {%endfor%}
+ {%endif%}
+ {%endfor%}
+ </div>
+ </div>
+ </div>
+ </div>
+</section>
+</div>
\ No newline at end of file
diff --git a/_i18n/es/resources/user-guides/How-to-mine-Monero-XMR-without-a-mining-equipment.md b/_i18n/es/resources/user-guides/How-to-mine-Monero-XMR-without-a-mining-equipment.md
new file mode 100644
index 0000000000000000000000000000000000000000..ca382b6a892a0e411a687fba4d3373b0ed274b98
--- /dev/null
+++ b/_i18n/es/resources/user-guides/How-to-mine-Monero-XMR-without-a-mining-equipment.md
@@ -0,0 +1,49 @@
+{% include untranslated.html %}
+## How to mine Monero (XMR) without a mining equipment?
+
+If you don’t have a profitable mining equipment, nor time or
+money to invest into building it, you can still mine Monero with NiceHash.
+
+NiceHash is a hashing power marketplace. Sellers of hashing
+power, i.e. miners, provide the hashing power for buyers (those who want to buy
+a service of mining a certain coin). Hence, NiceHash can provide you a massive
+hashing power in short amount of time. You won’t have to wait for years to see
+if you will make a profit or not and you can control which coin, at which pool,
+and for how long you want to mine.
+
+### **Step 1:** Create new account at NiceHash
+
+Visit [registration
+page](https://www.nicehash.com/?p=register) and register with your e-mail address.
+
+### **Step 2:** Deposit some Bitcoins to your account
+
+You will mine Monero, but you can buy hashing power at
+NiceHash only with Bitcoins. You can always withdraw unspent Bitcoins from your
+account back to any Bitcoin wallet.
+
+Visit your [wallet
+page](https://www.nicehash.com/?p=wallet) and make a deposit. Note that the minimum price for placing an order
+equals 0.01 BTC.
+
+### **Step 3:** Find a suitable pool for mining and add it to your pool list
+
+Selection of the pool plays a big role in the final amount
+of mined cryptocurrency. Make sure the pool you have selected can handle
+massive hashing rate and loads of shares, especially from a single connection.
+You can find a list of Monero pools [here](https://bitcointalk.org/index.php?topic=583449.0).
+
+Note that you will probably have to register an account at
+selected pool as well. The pool will provide you with all the information you need.
+You can save your favorite pools at [this page](https://www.nicehash.com/?p=managepools).
+
+### **Step 4:** Create new order and start mining
+
+When creating a [new order](https://www.nicehash.com/?p=orders&new), make sure you
+select CryptoNight algorithm for mining Monero. If you want to first learn more
+about placing an order with NiceHash, we recommend you to read this [frequently asked question](https://www.nicehash.com/?p=faq#faqb0).
+
+If you want to bid on
+hashing power select Standard (bidding) order type and if you want a fixed
+order that cannot be outbid, select Fixed order type. The status of marketplace
+and approximate prices of mining can be checked at [live marketplace](https://www.nicehash.com/index.jsp?p=orders).Â
\ No newline at end of file
diff --git a/_i18n/es/resources/user-guides/Offline_Backup.md b/_i18n/es/resources/user-guides/Offline_Backup.md
new file mode 100644
index 0000000000000000000000000000000000000000..089d20fc0c65105b1b6ed0f904e95cb6d8d3df1a
--- /dev/null
+++ b/_i18n/es/resources/user-guides/Offline_Backup.md
@@ -0,0 +1,37 @@
+{% include untranslated.html %}
+## Operating Systems: Various versions of Linux and Windows 7, 8
+
+### Wallet Software: Simplewallet
+
+#### Resource for Creating Bootable Disks: [Linux](http://www.pendrivelinux.com/), [Windows](https://www.microsoft.com/en-us/download/windows-usb-dvd-download-tool)
+
+#### Resource for Monero Binaries: [Monero Binaries](https://getmonero.org/downloads/)
+
+- Take any computer you have lying around, even your normal workstation. You may find it easier to use an older computer that has no wifi or bluetooth if you're particularly paranoid
+
+- Create a Linux or Windows bootable disk, and make sure you have the Monero binaries on the same disk or on a second disk (for Linux make sure you have also downloaded copies of the dependencies you will need, libboost1.55 and miniupnpc for instance)
+
+- Disconnect the network and/or Internet cables from your computer, physically remove the wifi card or switch the wifi/bluetooth off on a laptop if possible
+
+- Boot into your bootable OS, install the dependencies if necessary
+
+- Copy the Monero binaries to a RAM disk (/dev/shm in Linux, Windows bootable ISOs normally have a Z: drive or something)
+
+- Don't run the Monero daemon. Instead, using the command line, use monero-wallet-cli to create a new Monero @account
+
+- When prompted for a name, give it any name, it doesn't really matter
+
+- When prompted for a password, type in like 50 - 100 random characters. Don't worry that you don't know the password, just make it LONG
+
+- **CRITICAL STEP**: Write down (on paper) your 25 word @mnemonic-seed
+**WARNING**: If you forget to write down this information your funds may be lost forever
+
+- Write down (on your phone, on paper, on another computer, wherever you want) your address and view key
+
+- Switch off the computer, remove the battery if there is one, and leave it physically off for a few hours
+
+The account you've created was created in RAM, and the digital files are now inaccessible. If some adversary manages to somehow obtain the data, they will lack the long password to open it. If you need to receive payments, you have your public address, and you have the view key if needed. If you need access to it, you have your 25 word @mnemonic-seed, and you can now write out several copies of it, including an offsite copy (e.g. a bank deposit box).
+
+Credit: Riccardo Spagni
+
+Related: [Offline Account Generator](http://moneroaddress.org/)
diff --git a/_i18n/es/resources/user-guides/create_wallet.md b/_i18n/es/resources/user-guides/create_wallet.md
new file mode 100644
index 0000000000000000000000000000000000000000..8386529ef68d9043717b909989a0b62590bb04bb
--- /dev/null
+++ b/_i18n/es/resources/user-guides/create_wallet.md
@@ -0,0 +1,61 @@
+{% include untranslated.html %}
+### Operating Systems: Ubuntu
+
+- Download the [official binaries](https://getmonero.org/downloads/) or compile the last source available on [Github](https://github.com/monero-project/bitmonero)
+
+
+
+
+- Extract the files with the archive manager (same as Winzip on Windows). Note the path where the files "monerod" and "monero-wallet-cli" are
+
+
+
+
+- You only need to do this step once : open a terminal (ctrl+alt+t) and install the required dependencies by typing : "*sudo apt-get install libboost-all-dev libssl-dev libevent-dev libdb++-dev*". When asked, press the Y key and then Enter to continue
+
+
+
+
+- Open a terminal and load the path where your binaries are extracted (cf. step 2) by typing : "*cd yourPathFromStep2*"
+
+
+
+- Load monerod by typing in your terminal : "*./monerod*". Wait for the synchronization with the network (monerod is updating the blockchain you have downloaded in step 4 or is downloading it from scratch). This can take a lot of time the first time, so be patient
+
+
+
+
+
+
+- Once monerod is synchronized with the network, open a new terminal, change the directory (cf. step 5), and launch monero-wallet-cli by typing "*./monero-wallet-cli*"
+
+
+
+- Enter the name you want for your portfolio and follow the instructions from the terminal
+
+
+
+
+
+
+*This is your private key. Write it down and keep it in a safe place!*
+
+
+
+*This is your view key. You need it to create a view only wallet (cf. associated user guide)*
+
+
+
+*This is the address of your wallet*
+
+
+
+
+
+
+
+- To exit monerod or monero-wallet-cli just type "*exit*" in the associated terminal
+
+Now to access the portfolio you have just created you will have to launch monerod, wait for it to be synchronized with the network, launch monero-wallet-cli, and type the name of your portfolio and your password.
+
+
diff --git a/_i18n/es/resources/user-guides/easiest_buy.md b/_i18n/es/resources/user-guides/easiest_buy.md
new file mode 100644
index 0000000000000000000000000000000000000000..4b360c5a4b5e138c7e0d1f6200805c9aab90e26b
--- /dev/null
+++ b/_i18n/es/resources/user-guides/easiest_buy.md
@@ -0,0 +1,65 @@
+{% include untranslated.html %}
+## How to obtain Monero
+
+This is a guide to obtain your own Monero as of 20150919. This is perhaps the easiest way to purchase and hold Monero.
+
+####Step 1: Buy Bitcoin
+
+There are many ways to buy Bitcoin. Perhaps the easiest way is through circle.com. Once you have purchased some Bitcoin, you are ready to buy some Monero! Buying Bitcoin is straightforward. Please goto circle.com and just follow the instructions there.
+
+####Step 2: Set up a mymonero.com account
+
+MyMonero.com is an online wallet for Monero, maintained by Monero Core Developer Ricardo Spagni (fluffpony). It is the easiest wallet to use. Simply go to MyMonero.com and click on the "Create an Account" button.
+
+
+
+After clicking the button, you will see your private key. This key is what gives you access to your funds. Never share this key with anyone!
+
+### WRITE DOWN THIS KEY IMMEDIATELY!
+
+
+
+Type in your private key in the box below, and click the button.
+
+On the next page, you will see your address.
+
+
+
+Copy your address to the clipboard by highlighting the whole thing and hitting ctrl+c (or edit menu, copy), or clicking the little icon next to your address. Save your address somewhere. This is how others will send Monero to you, and what you will use to deposit Monero into your account!
+
+#### Step 3: Buy Monero and transfer the Monero to your new address
+
+Go to www.shapeshift.io . On the righthand side, of the screen, click icon under "Receive" to select Monero.
+
+
+
+
+Paste your address into the field under the Monero logo. Select the "agree to terms" button, then hit "Start"
+
+
+
+In the new screen that pops up, copy the Deposit Address into your clipboard (select and hit ctrl+c or edit-copy)
+
+
+
+Go back to your circle.com page, hit the "transfer" button, and paste the Bitcoin address into the field
+Enter the amount of Bitcoin you would like to spend.
+
+
+
+
+You will get a text message verification code. Enter code and hit send.
+
+
+
+You will see the shapeshift change to "awaiting exchange"
+
+
+
+Then it will change to COMPLETE!
+
+
+
+After a while you will see it in your Monero account
+
+
diff --git a/_i18n/es/resources/user-guides/howto_fix_stuck_funds.md b/_i18n/es/resources/user-guides/howto_fix_stuck_funds.md
new file mode 100644
index 0000000000000000000000000000000000000000..5320044670c307207ce2c4ab69cb817fbed45a61
--- /dev/null
+++ b/_i18n/es/resources/user-guides/howto_fix_stuck_funds.md
@@ -0,0 +1,31 @@
+{% include untranslated.html %}
+Sometimes, your funds will become stuck - you will have some locked funds that never become unlocked. This is how you fix it.
+
+- Load your wallet in monero-wallet-cli.
+
+- Type
+
+> seed
+
+into the command prompt. Write down your 25 word seed, if you haven't already. This is the best way to make sure you don't loose access to your funds.
+
+- Close monero-wallet-cli by typing
+
+> exit
+
+- Backup all of your wallet related files. These include:
+
+> yourwalletname.bin
+> yourwalletname.bin.keys
+> yourwalletname.bin.address.txt
+
+This can be done by copying the files to a new folder.
+
+Sometimes, when creating your wallet, you might have named it something without the .bin part. In that case, the wallet file will be called yourwalletname without the .bin at the end.
+
+- Delete yourwallet.bin
+
+- Load monero-wallet-cli, type in the name of the wallet you just deleted
+
+- Enter password. The wallet will now refresh and hopefully your locked funds will now become unlocked.
+
diff --git a/_i18n/es/resources/user-guides/importing_blockchain.md b/_i18n/es/resources/user-guides/importing_blockchain.md
new file mode 100644
index 0000000000000000000000000000000000000000..43eb5823a0abff340735fb5de634255f000d7c27
--- /dev/null
+++ b/_i18n/es/resources/user-guides/importing_blockchain.md
@@ -0,0 +1,57 @@
+{% include untranslated.html %}
+# Importing the Blockchain to Monero GUI wallet (Windows)
+
+### Step 1
+
+Download the Current bootstrap from https://downloads.getmonero.org/blockchain.raw; you can skip this step if you are importing the Blockchain from another source.
+
+### Step 2
+
+Find the path of your Monero wallet (the folder where you extracted your wallet). For example mine is:
+
+`D:\monero-gui-0.10.3.1`
+
+Your path may be different depending on where you decided to download your wallet and what version of the Monero wallet you have.
+
+### Step 3
+
+Find the path of your downloaded Blockchain for example mine was:
+
+`C:\Users\KeeJef\Downloads\blockchain.raw`
+
+Yours might be different depending on where you downloaded the Blockchain to.
+
+### Step 4
+
+Open a Command Prompt window. You can do this by pressing the Windows key + R, and then typing in the popup box `CMD`
+
+### Step 5
+
+Now you need to navigate using the CMD window to the path of your Monero wallet. You can do this by typing:
+
+`cd C:\YOUR\MONERO\WALLET\FILE\PATH\HERE`
+
+It should look something like:
+
+`cd D:\monero-gui-0.10.3.1`
+
+If your Monero wallet is on another drive you can use `DriveLetter:` for example if your Monero wallet was on your D drive then before using the cd command you would do `D:`
+
+### Step 6
+
+Now type in your command prompt window:
+
+`monero-blockchain-import --verify 1 --input-file C:\YOUR\BLOCKCHAIN\FILE\PATH\HERE`
+
+For example I would type :
+
+`monero-blockchain-import --verify 1 --input-file C:\Users\KeeJef\Downloads\blockchain.raw`
+
+If you downloaded the Blockchain from a trusted, reputable source you may set `verify 0` this will reduce the amount of time to sync the Blockchain.
+
+### Step 7
+
+After the 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/_i18n/es/resources/user-guides/index.md b/_i18n/es/resources/user-guides/index.md
new file mode 100644
index 0000000000000000000000000000000000000000..0eb5cb29e59f47c86b33194360847e8ac2a28930
--- /dev/null
+++ b/_i18n/es/resources/user-guides/index.md
@@ -0,0 +1,83 @@
+{% include untranslated.html %}
+<div class="guides">
+<section class="container">
+ <div class="row">
+ <div class="left half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>General</h2>
+ </div>
+ </div>
+<div class="row start-xs" markdown="1">
+
+[Monero Tools]({{site.baseurl}}/resources/user-guides/monero_tools.html)
+[How to make an offline backup]({{site.baseurl}}/resources/user-guides/Offline_Backup.html)
+[Importing the Monero blockchain]({{site.baseurl}}/resources/user-guides/importing_blockchain.html)
+[How to run a node on VPS]({{site.baseurl}}/resources/user-guides/vps_run_node.html)
+[Securely purchasing and storing Monero]({{site.baseurl}}/resources/user-guides/securely_purchase.html)
+
+</div>
+ </div>
+ </div>
+ <div class="right half col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Wallets</h2>
+ </div>
+ </div>
+<div class="row start-xs" markdown="1">
+
+[Getting started with the CLI wallet]({{site.baseurl}}/resources/user-guides/monero-wallet-cli.html)
+[How to make a view-only wallet]({{site.baseurl}}/resources/user-guides/view_only.html)
+[How to prove payment]({{site.baseurl}}/resources/user-guides/prove-payment.html)
+[Restoring wallet from keys]({{site.baseurl}}/resources/user-guides/restore_from_keys.html)
+[How to connect to a remote node within GUI wallet]({{site.baseurl}}/resources/user-guides/remote_node_gui.html)
+[CLI wallet/daemon isolation with Qubes + Whonix]({{site.baseurl}}/resources/user-guides/cli_wallet_daemon_isolation_qubes_whonix.html)
+
+</div>
+ </div>
+ </div>
+ </div>
+</section>
+
+<section class="container">
+ <div class="row">
+ <div class="left half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Recovery</h2>
+ </div>
+ </div>
+<div class="row start-xs" markdown="1">
+
+[How to fix locked up funds]({{site.baseurl}}/resources/user-guides/howto_fix_stuck_funds.html)
+[How to restore your account]({{site.baseurl}}/resources/user-guides/restore_account.html)
+
+</div>
+ </div>
+ </div>
+ <div class="right half col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Mining</h2>
+ </div>
+ </div>
+<div class="row start-xs" markdown="1">
+
+[How to solo mine with the GUI]({{site.baseurl}}/resources/user-guides/solo_mine_GUI.html)
+[How to mine on a pool with xmr-stak-cpu]({{site.baseurl}}/resources/user-guides/mine-to-pool.html)
+[Mining with Docker and XMRig]({{site.baseurl}}/resources/user-guides/mining_with_xmrig_and_docker.html)
+
+</div>
+ </div>
+ </div>
+ </div>
+
+
+
+</section>
+</div>
diff --git a/_i18n/es/resources/user-guides/mine-to-pool.md b/_i18n/es/resources/user-guides/mine-to-pool.md
new file mode 100644
index 0000000000000000000000000000000000000000..d39075d2b3e77c9a9126e499bc1316646ae18e54
--- /dev/null
+++ b/_i18n/es/resources/user-guides/mine-to-pool.md
@@ -0,0 +1,114 @@
+{% include untranslated.html %}
+# Selecting a pool
+
+There are many pools to choose from, a list is available at
+[moneropools.com](https://moneropools.com). Mining on a larger pool could mean
+more frequent payouts, but mining on a smaller pool helps to keep the network
+decentralized.
+
+# Selecting a CPU miner
+
+Just like pools, there are a lot of miners to choose from. The one that you
+should pick depends on the hardware you want to mine on. This guide will only
+use a CPU miner, and will be using
+[xmr-stak-cpu](https://github.com/fireice-uk/xmr-stak-cpu). Alternatives include
+[wolf's CPUMiner](https://github.com/wolf9466/cpuminer-multi) and
+[sgminer-gm](https://github.com/genesismining/sgminer-gm). However, their
+configuration is slightly different and will not be covered in this guide.
+
+## For Windows Systems
+
+If you are using a Windows system, the developer of xmr-stak-cpu provides
+binaries to download on the
+[GitHub release page](https://github.com/fireice-uk/xmr-stak-cpu/releases).
+
+Download `xmr-stak-cpu-win64.zip` and extract it somewhere you'll be able to
+find it again.
+
+## For Other Operating Systems
+
+If you're not using Windows, you will have to compile xmr-stak-cpu for yourself,
+luckily this isn't as hard as it sounds. Before you can compile the miner, you
+will need to install some of its prerequisites.
+
+For Debian-based distros:
+
+ sudo apt-get install libmicrohttpd-dev libssl-dev cmake build-essential
+
+For Red Hat based distros:
+
+ sudo yum install openssl-devel cmake gcc-c++ libmicrohttpd-devel
+
+<!-- TODO: Add dependencies for other operating systems? -->
+
+Following this, you just need to use cmake to generate the build files, run
+make and copy the config file:
+
+ mkdir build-$(gcc -dumpmachine)
+ cd $_
+ cmake ../
+ make -j$(nproc)
+ cp ../config.txt bin/
+ cd bin
+
+Don't celebrate just yet, as the miner needs to be configured. Running the miner
+now should give you a block of text to copy and paste:
+
+
+
+Open `config.txt` and *replace* the two `"cpu_threads_conf"` lines with the text
+you just copied. It should look something like this afterwards:
+
+
+
+Scroll down in the file until you see the lines containing `"pool_address"`.
+*Replace* the contents of the second set of quotes with the address and port of
+the pool you chose earlier. You can find this information on the pool's website.
+
+Put your wallet address between the quotes on the wallet address. You may leave
+the password blank unless the pool specifies otherwise.
+
+After this, your config should look something like this:
+
+
+
+# Running the miner
+
+**Save the config** file and run the miner!
+
+
+
+Some pools allow you to monitor your hashrate by pasting your address into their
+website. You can also monitor your hashrate by pressing the `h` key.
+
+# Tuning the miner
+
+You might see nasty messages like this:
+
+ [2017-07-09 12:04:02] : MEMORY ALLOC FAILED: mmap failed
+
+This means that you can get around a 20% hashrate boost by enabling large pages.
+
+## Large pages on Linux
+
+Firstly stop the miner (if it's running), run the following commands to enable
+large pages and then start the miner as root:
+
+ sudo sysctl -w vm.nr_hugepages=128
+ sudo ./xmr-stak-cpu
+
+## Large pages on Windows
+
+Taken from `config.txt`:
+
+>By default we will try to allocate large pages. This means you need to "Run As Administrator" on Windows
+You need to edit your system's group policies to enable locking large pages. Here are the steps from MSDN
+1. On the Start menu, click Run. In the Open box, type gpedit.msc.
+2. On the Local Group Policy Editor console, expand Computer Configuration, and then expand Windows Settings.
+3. Expand Security Settings, and then expand Local Policies.
+4. Select the User Rights Assignment folder.
+5. The policies will be displayed in the details pane.
+6. In the pane, double-click Lock pages in memory.
+7. In the Local Security Setting – Lock pages in memory dialog box, click Add User or Group.
+8. In the Select Users, Service Accounts, or Groups dialog box, add an account that you will run the miner on
+9. Reboot for change to take effect.
diff --git a/_i18n/es/resources/user-guides/mining_with_xmrig_and_docker.md b/_i18n/es/resources/user-guides/mining_with_xmrig_and_docker.md
new file mode 100644
index 0000000000000000000000000000000000000000..fcad1cf4feaff2d0dc5a8363f7544b9c820c0dbb
--- /dev/null
+++ b/_i18n/es/resources/user-guides/mining_with_xmrig_and_docker.md
@@ -0,0 +1,37 @@
+{% include untranslated.html %}
+## Introduction
+
+This guide is two fold, ease of use for mining on Linux distributions and some extra security around mining as most of these miners have not had security auditing.
+
+At the end of this guide you will be able to sleep a little easier knowing that if the miner gets exploited it will not migrate to your OS.
+
+### Why Docker
+
+[Docker](https://www.docker.com/) is being used as it is the most well known and has the biggest chance to be already installed.
+
+The container I an using is [alpine-xmrig](https://hub.docker.com/r/bitnn/alpine-xmrig/) as per the name it is built on the [Alpine Linux](https://www.alpinelinux.org/) image.
+
+If you are interested in getting started with Docker, here are some really good starting references.
+* Arch Linux Wiki [Docker Page](https://wiki.archlinux.org/index.php/Docker)
+* Container Solutions [Security Cheat Sheet](http://container-solutions.com/content/uploads/2015/06/15.06.15_DockerCheatSheet_A2.pdf)
+* Digital Oceans [Dockerfile Howto](https://www.digitalocean.com/community/tutorials/docker-explained-using-dockerfiles-to-automate-building-of-images).
+
+For distribution specific installation please refer to the [Docker Docs](https://docs.docker.com/engine/installation/) website.
+
+### Why XMRig
+
+[XMRig](https://github.com/xmrig/xmrig) is just a really solid miner to me. Nice output and statistics, no flashy web-ui's or dependencies. The XMRig container is only ~4MB what makes it extremely portable.
+
+#### Step 1: Mining with XMRig
+
+Run the following
+
+```bash
+# docker run --restart unless-stopped --read-only -m 50M -c 512 bitnn/alpine-xmrig -o POOL01 -o POOL02 -u WALLET -p PASSWORD -k
+# docker run --restart unless-stopped --read-only -m 50M -c 512 bitnn/alpine-xmrig -o pool.supportxmr.com:7777 -u 45CJVagd6WwQAQfAkS91EHiTyfVaJn12uM4Su8iz6S2SHZ3QthmFM9BSPHVZY388ASWx8G9Wbz4BA24RQZUpGczb35fnnJz -p docker:secret -k
+```
+
+#### Step 2: There is no Step 2
+
+You have already done everything you need to do. You are now mining in a docker container with XMRig `ctrl+c` to exit the miner or add `-d` just after `docker run` to background the miner.
+
diff --git a/_i18n/es/resources/user-guides/monero-wallet-cli.md b/_i18n/es/resources/user-guides/monero-wallet-cli.md
new file mode 100644
index 0000000000000000000000000000000000000000..155a82d1485447d81d05167a4a61893d44e77fef
--- /dev/null
+++ b/_i18n/es/resources/user-guides/monero-wallet-cli.md
@@ -0,0 +1,146 @@
+{% include untranslated.html %}
+# monero-wallet-cli
+
+`monero-wallet-cli` is the wallet software that ships with the Monero tree. It is a console program,
+and manages an account. While a bitcoin wallet manages both an account and the blockchain,
+Monero separates these: `monerod` handles the blockchain, and `monero-wallet-cli` handles the account.
+
+This guide will show how to perform various operations from the `monero-wallet-cli` UI. The guide assumes you are using the most recent version of Monero and have already created an account according to the other guides.
+
+
+## Checking your balance
+
+Since the blockchain handling and the wallet are separate programs, many uses of `monero-wallet-cli`
+need to work with the daemon. This includes looking for incoming transactions to your address.
+Once you are running both `monero-wallet-cli` and `monerod`, enter `balance`.
+
+Example:
+
+This will pull blocks from the daemon the wallet did not yet see, and update your balance
+to match. This process will normally be done in the background every minute or so. To see the
+balance without refreshing:
+
+ balance
+ Balance: 64.526198850000, unlocked balance: 44.526198850000, including unlocked dust: 0.006198850000
+
+In this example, `Balance` is your total balance. The `unlocked balance` is the amount currently available to spend. Newly received transactions require 10 confirmations on the blockchain before being unlocked. `unlocked dust` refers to very small amounts of unspent outputs that may have accumulated in your account.
+
+## Sending monero
+
+You will need the standard address you want to send to (a long string starting with '4'), and
+possibly a payment ID, if the receiving party requires one. In that latter case, that party
+may instead give you an integrated address, which is both of these packed into a single address.
+
+### Sending to a standard address:
+
+ transfer ADDRESS AMOUNT PAYMENTID
+
+Replace `ADDRESS` with the address you want to send to, `AMOUNT` with how many monero you want to send,
+and `PAYMENTID` with the payment ID you were given. Payment ID's are optional. If the receiving party doesn't need one, just
+omit it.
+
+### Sending to an integrated address:
+
+ transfer ADDRESS AMOUNT
+
+The payment ID is implicit in the integrated address in that case.
+
+### Specify the number of outputs for a transaction:
+
+ transfer MIXIN ADDRESS AMOUNT
+
+Replace `MIXIN` with the number of outputs you wish to use. **If not specified, the default is 4.** It's a good idea to use the default, but you can increase the number if you want to include more outputs. The higher the number, the larger the transaction, and higher fees are needed.
+
+
+## Receiving monero
+
+If you have your own Monero address, you just need to give your standard address to someone.
+
+You can find out your address with:
+
+ address
+
+Since Monero is anonymous, you won't see the origin address the funds you receive came from. If you
+want to know, for instance to credit a particular customer, you'll have to tell the sender to use
+a payment ID, which is an arbitrary optional tag which gets attached to a transaction. To make life
+easier, you can generate an address that already includes a random payment ID:
+
+ integrated_address
+
+This will generate a random payment ID, and give you the address that includes your own account
+and that payment ID. If you want to select a particular payment ID, you can do that too:
+
+ integrated_address 12346780abcdef00
+
+Payments made to an integrated address generated from your account will go to your account,
+with that payment id attached, so you can tell payments apart.
+
+
+## Proving to a third party you paid someone
+
+If you pay a merchant, and the merchant claims to not have received the funds, you may need
+to prove to a third party you did send the funds - or even to the merchant, if it is a honest
+mistake. Monero is private, so you can't just point to your transaction in the blockchain,
+as you can't tell who sent it, and who received it. However, by supplying the per-transaction
+private key to a party, that party can tell whether that transaction sent monero to that
+particular address. Note that storing these per-transaction keys is disabled by default, and
+you will have to enable it before sending, if you think you may need it:
+
+ set store-tx-info 1
+
+You can retrieve the tx key from an earlier transaction:
+
+ get_tx_key 1234567890123456789012345678901212345678901234567890123456789012
+
+Pass in the transaction ID you want the key for. Remember that a payment might have been
+split in more than one transaction, so you may need several keys. You can then send that key,
+or these keys, to whoever you want to provide proof of your transaction, along with the
+transaction id and the address you sent to. Note that this third party, if knowing your
+own address, will be able to see how much change was returned to you as well.
+
+If you are the third party (that is, someone wants to prove to you that they sent monero
+to an address), then you can check this way:
+
+ check_tx_key TXID TXKEY ADDRESS
+
+Replace `TXID`, `TXKEY` and `ADDRESS` with the transaction ID, per-transaction key, and destination
+address which were supplied to you, respectively. monero-wallet-cli will check that transaction
+and let you know how much monero this transaction paid to the given address.
+
+
+## Getting a chance to confirm/cancel payments
+
+If you want to get a last chance confirmation when sending a payment:
+
+ set always-confirm-transfers 1
+
+
+## How to find a payment to you
+
+If you received a payment using a particular payment ID, you can look it up:
+
+ payments PAYMENTID
+
+You can give more than one payment ID too.
+
+More generally, you can review incoming and outgoing payments:
+
+ show_transfers
+
+You can give an optional height to list only recent transactions, and request
+only incoming or outgoing transactions. For example,
+
+ show_transfers in 650000
+
+will only incoming transfers after block 650000. You can also give a height
+range.
+
+If you want to mine, you can do so from the wallet:
+
+ start_mining 2
+
+This will start mining on the daemon usin two threads. Note that this is solo mining,
+and may take a while before you find a block. To stop mining:
+
+ stop_mining
+
diff --git a/_i18n/es/resources/user-guides/monero_tools.md b/_i18n/es/resources/user-guides/monero_tools.md
new file mode 100644
index 0000000000000000000000000000000000000000..67d60a0469674229a9622350df431681cc655462
--- /dev/null
+++ b/_i18n/es/resources/user-guides/monero_tools.md
@@ -0,0 +1,18 @@
+{% include untranslated.html %}
+# Monero tools
+
+These tools can be used to gain information about the Monero network or your transaction data in the blockchain.
+
+### [Check that a recipient has received your funds](http://xmrtests.llcoins.net/checktx.html)
+
+### [Tools for monero address generation](https://xmr.llcoins.net/)
+
+### [Monero node count](http://moneronodes.i2p.xyz/)
+
+### [Monero node map](https://monerohash.com/nodes-distribution.html)
+
+### [Monero offline wallet generator](http://moneroaddress.org/)
+
+### [Monero network statistics](http://moneroblocks.info/stats)
+
+### [Monero.how statistics](https://www.monero.how/)
\ No newline at end of file
diff --git a/_i18n/es/resources/user-guides/png/create_wallet/1.png b/_i18n/es/resources/user-guides/png/create_wallet/1.png
new file mode 100644
index 0000000000000000000000000000000000000000..44acf51b19ea9435af2dc466ed05514b7543564d
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/create_wallet/1.png differ
diff --git a/_i18n/es/resources/user-guides/png/create_wallet/10.png b/_i18n/es/resources/user-guides/png/create_wallet/10.png
new file mode 100644
index 0000000000000000000000000000000000000000..2f248c9dda4ce97441e68d65923f4d74feb2a7c3
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/create_wallet/10.png differ
diff --git a/_i18n/es/resources/user-guides/png/create_wallet/11.png b/_i18n/es/resources/user-guides/png/create_wallet/11.png
new file mode 100644
index 0000000000000000000000000000000000000000..f8bb9989a3dfac8d717ae20c23b14aaaf987876d
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/create_wallet/11.png differ
diff --git a/_i18n/es/resources/user-guides/png/create_wallet/12.png b/_i18n/es/resources/user-guides/png/create_wallet/12.png
new file mode 100644
index 0000000000000000000000000000000000000000..2e1f69d63c25cf308989596187d55adf10fcc6d2
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/create_wallet/12.png differ
diff --git a/_i18n/es/resources/user-guides/png/create_wallet/13.png b/_i18n/es/resources/user-guides/png/create_wallet/13.png
new file mode 100644
index 0000000000000000000000000000000000000000..2db5d603ab699581e9755c369602d9088b688f53
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/create_wallet/13.png differ
diff --git a/_i18n/es/resources/user-guides/png/create_wallet/14.png b/_i18n/es/resources/user-guides/png/create_wallet/14.png
new file mode 100644
index 0000000000000000000000000000000000000000..bf2906e280f00193aef3b19f430bcac8c7cedee6
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/create_wallet/14.png differ
diff --git a/_i18n/es/resources/user-guides/png/create_wallet/15.png b/_i18n/es/resources/user-guides/png/create_wallet/15.png
new file mode 100644
index 0000000000000000000000000000000000000000..7c675edfb7b174ed45fac544d26762f822cf3881
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/create_wallet/15.png differ
diff --git a/_i18n/es/resources/user-guides/png/create_wallet/16.png b/_i18n/es/resources/user-guides/png/create_wallet/16.png
new file mode 100644
index 0000000000000000000000000000000000000000..ab23b572fa33fbf019440ba419d9adfe9f9ce9b3
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/create_wallet/16.png differ
diff --git a/_i18n/es/resources/user-guides/png/create_wallet/17.png b/_i18n/es/resources/user-guides/png/create_wallet/17.png
new file mode 100644
index 0000000000000000000000000000000000000000..97ea15bcad6ce467ba36202ebf28dd6f987a6244
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/create_wallet/17.png differ
diff --git a/_i18n/es/resources/user-guides/png/create_wallet/18.png b/_i18n/es/resources/user-guides/png/create_wallet/18.png
new file mode 100644
index 0000000000000000000000000000000000000000..20546a9ab5e547b73c0b58164537cba6e4b911d4
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/create_wallet/18.png differ
diff --git a/_i18n/es/resources/user-guides/png/create_wallet/19.png b/_i18n/es/resources/user-guides/png/create_wallet/19.png
new file mode 100644
index 0000000000000000000000000000000000000000..5a7088e259addd15157a27aa917bcaebe92e2d5d
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/create_wallet/19.png differ
diff --git a/_i18n/es/resources/user-guides/png/create_wallet/2.png b/_i18n/es/resources/user-guides/png/create_wallet/2.png
new file mode 100644
index 0000000000000000000000000000000000000000..164aa6b689364ad1ed04f2388653f0c844006649
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/create_wallet/2.png differ
diff --git a/_i18n/es/resources/user-guides/png/create_wallet/20.png b/_i18n/es/resources/user-guides/png/create_wallet/20.png
new file mode 100644
index 0000000000000000000000000000000000000000..c5169249b22e6a26c56d11a86c76e900d4ec467b
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/create_wallet/20.png differ
diff --git a/_i18n/es/resources/user-guides/png/create_wallet/21.png b/_i18n/es/resources/user-guides/png/create_wallet/21.png
new file mode 100644
index 0000000000000000000000000000000000000000..090ff767ae613d71f2cf0d7390dd204b34ec1ccf
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/create_wallet/21.png differ
diff --git a/_i18n/es/resources/user-guides/png/create_wallet/22.png b/_i18n/es/resources/user-guides/png/create_wallet/22.png
new file mode 100644
index 0000000000000000000000000000000000000000..8c7a7669afdb1b9fc670589184214fe029280f5c
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/create_wallet/22.png differ
diff --git a/_i18n/es/resources/user-guides/png/create_wallet/23.png b/_i18n/es/resources/user-guides/png/create_wallet/23.png
new file mode 100644
index 0000000000000000000000000000000000000000..e2dfc0c4ed20d73ba9341b83195020068716a5c8
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/create_wallet/23.png differ
diff --git a/_i18n/es/resources/user-guides/png/create_wallet/3.png b/_i18n/es/resources/user-guides/png/create_wallet/3.png
new file mode 100644
index 0000000000000000000000000000000000000000..f4f4436e27849c8c3ac3025626a7d5be4a9c6667
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/create_wallet/3.png differ
diff --git a/_i18n/es/resources/user-guides/png/create_wallet/4.png b/_i18n/es/resources/user-guides/png/create_wallet/4.png
new file mode 100644
index 0000000000000000000000000000000000000000..36be1be0518f8d1aee145740d4928092690ae9c9
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/create_wallet/4.png differ
diff --git a/_i18n/es/resources/user-guides/png/create_wallet/5.png b/_i18n/es/resources/user-guides/png/create_wallet/5.png
new file mode 100644
index 0000000000000000000000000000000000000000..56c6733aabd3ea7a213e4b16bb3b3244631b82a5
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/create_wallet/5.png differ
diff --git a/_i18n/es/resources/user-guides/png/create_wallet/6.png b/_i18n/es/resources/user-guides/png/create_wallet/6.png
new file mode 100644
index 0000000000000000000000000000000000000000..8e0d7950fb9225541f455a24330a36ff7357f252
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/create_wallet/6.png differ
diff --git a/_i18n/es/resources/user-guides/png/create_wallet/7.png b/_i18n/es/resources/user-guides/png/create_wallet/7.png
new file mode 100644
index 0000000000000000000000000000000000000000..c18527827bd6dcfdf4257fcb46c82e754f61121b
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/create_wallet/7.png differ
diff --git a/_i18n/es/resources/user-guides/png/create_wallet/8.png b/_i18n/es/resources/user-guides/png/create_wallet/8.png
new file mode 100644
index 0000000000000000000000000000000000000000..ce02508b7d912855670066aec22ebef824b0d986
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/create_wallet/8.png differ
diff --git a/_i18n/es/resources/user-guides/png/create_wallet/9.png b/_i18n/es/resources/user-guides/png/create_wallet/9.png
new file mode 100644
index 0000000000000000000000000000000000000000..cac31479b11bbad5907d984c8e81bdf50fcb2a8d
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/create_wallet/9.png differ
diff --git a/_i18n/es/resources/user-guides/png/easiest_way/01.png b/_i18n/es/resources/user-guides/png/easiest_way/01.png
new file mode 100644
index 0000000000000000000000000000000000000000..17c55b2d6a024f3245055975b654681265812d2d
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/easiest_way/01.png differ
diff --git a/_i18n/es/resources/user-guides/png/easiest_way/02.png b/_i18n/es/resources/user-guides/png/easiest_way/02.png
new file mode 100644
index 0000000000000000000000000000000000000000..91e1bfd16f7843310fc59c84c4aff2e03aa13181
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/easiest_way/02.png differ
diff --git a/_i18n/es/resources/user-guides/png/easiest_way/03.png b/_i18n/es/resources/user-guides/png/easiest_way/03.png
new file mode 100644
index 0000000000000000000000000000000000000000..dded71ade21780fe14fd63fb7aab11bddcd635b1
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/easiest_way/03.png differ
diff --git a/_i18n/es/resources/user-guides/png/easiest_way/04.png b/_i18n/es/resources/user-guides/png/easiest_way/04.png
new file mode 100644
index 0000000000000000000000000000000000000000..e657d4315e459c4b18648d417c539193fce5376d
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/easiest_way/04.png differ
diff --git a/_i18n/es/resources/user-guides/png/easiest_way/05.png b/_i18n/es/resources/user-guides/png/easiest_way/05.png
new file mode 100644
index 0000000000000000000000000000000000000000..00d2b26a05fb2fae413d4853c1f9e5159428d1c6
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/easiest_way/05.png differ
diff --git a/_i18n/es/resources/user-guides/png/easiest_way/06.png b/_i18n/es/resources/user-guides/png/easiest_way/06.png
new file mode 100644
index 0000000000000000000000000000000000000000..4d55286ce0e83da7051dc8070847a729f04c72fe
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/easiest_way/06.png differ
diff --git a/_i18n/es/resources/user-guides/png/easiest_way/07.png b/_i18n/es/resources/user-guides/png/easiest_way/07.png
new file mode 100644
index 0000000000000000000000000000000000000000..715245b2239d4ed7882c0c6e933cc13aa9173e82
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/easiest_way/07.png differ
diff --git a/_i18n/es/resources/user-guides/png/easiest_way/08.png b/_i18n/es/resources/user-guides/png/easiest_way/08.png
new file mode 100644
index 0000000000000000000000000000000000000000..bfc459a89582d8791f3cd2b1b1a013e2004e638a
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/easiest_way/08.png differ
diff --git a/_i18n/es/resources/user-guides/png/easiest_way/09.png b/_i18n/es/resources/user-guides/png/easiest_way/09.png
new file mode 100644
index 0000000000000000000000000000000000000000..e632bbb82e533b6fb205baf4edd5b86f153a9229
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/easiest_way/09.png differ
diff --git a/_i18n/es/resources/user-guides/png/easiest_way/10.png b/_i18n/es/resources/user-guides/png/easiest_way/10.png
new file mode 100644
index 0000000000000000000000000000000000000000..3a9337336bf1c34e7980da562a63f987d4781232
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/easiest_way/10.png differ
diff --git a/_i18n/es/resources/user-guides/png/easiest_way/11.png b/_i18n/es/resources/user-guides/png/easiest_way/11.png
new file mode 100644
index 0000000000000000000000000000000000000000..eaa4a5b989cc6463a29285bae4d0e7688b595ce4
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/easiest_way/11.png differ
diff --git a/_i18n/es/resources/user-guides/png/easiest_way/12.png b/_i18n/es/resources/user-guides/png/easiest_way/12.png
new file mode 100644
index 0000000000000000000000000000000000000000..e38159ec6fa34c74408f27ee6b5792f337bfacb2
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/easiest_way/12.png differ
diff --git a/_i18n/es/resources/user-guides/png/easiest_way/13.png b/_i18n/es/resources/user-guides/png/easiest_way/13.png
new file mode 100644
index 0000000000000000000000000000000000000000..ed3b707d01f87f3376b134ede6477b01b684bac3
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/easiest_way/13.png differ
diff --git a/_i18n/es/resources/user-guides/png/mine_to_pool/1.png b/_i18n/es/resources/user-guides/png/mine_to_pool/1.png
new file mode 100644
index 0000000000000000000000000000000000000000..a6e7652877110b793894d9ae627c7466a56b7b0c
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/mine_to_pool/1.png differ
diff --git a/_i18n/es/resources/user-guides/png/mine_to_pool/2.png b/_i18n/es/resources/user-guides/png/mine_to_pool/2.png
new file mode 100644
index 0000000000000000000000000000000000000000..83a7dd163530cfe1a9d5c9c44b4482c7cdb40458
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/mine_to_pool/2.png differ
diff --git a/_i18n/es/resources/user-guides/png/mine_to_pool/3.png b/_i18n/es/resources/user-guides/png/mine_to_pool/3.png
new file mode 100644
index 0000000000000000000000000000000000000000..70aeea2aaa91a34285fd0a0162f858a9b0bc76c6
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/mine_to_pool/3.png differ
diff --git a/_i18n/es/resources/user-guides/png/mine_to_pool/4.png b/_i18n/es/resources/user-guides/png/mine_to_pool/4.png
new file mode 100644
index 0000000000000000000000000000000000000000..13361a0e85a8b82a374917df939bb97f4529ff32
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/mine_to_pool/4.png differ
diff --git a/_i18n/es/resources/user-guides/png/remote_node/remote-node-screenshot.png b/_i18n/es/resources/user-guides/png/remote_node/remote-node-screenshot.png
new file mode 100644
index 0000000000000000000000000000000000000000..a32bf5088c040273bef87448b049c5bc112be196
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/remote_node/remote-node-screenshot.png differ
diff --git a/_i18n/es/resources/user-guides/png/solo_mine_GUI/01.PNG b/_i18n/es/resources/user-guides/png/solo_mine_GUI/01.PNG
new file mode 100644
index 0000000000000000000000000000000000000000..7ca5f7c247ee06462a549ca4a6b5c6380b9f257f
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/solo_mine_GUI/01.PNG differ
diff --git a/_i18n/es/resources/user-guides/png/solo_mine_GUI/02.PNG b/_i18n/es/resources/user-guides/png/solo_mine_GUI/02.PNG
new file mode 100644
index 0000000000000000000000000000000000000000..42a5290e0733dedb0f397e50a86215b0887039a5
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/solo_mine_GUI/02.PNG differ
diff --git a/_i18n/es/resources/user-guides/png/solo_mine_GUI/03.PNG b/_i18n/es/resources/user-guides/png/solo_mine_GUI/03.PNG
new file mode 100644
index 0000000000000000000000000000000000000000..ab7b8c2a2143d0ab46fae3294a09fe01b0bd61f4
Binary files /dev/null and b/_i18n/es/resources/user-guides/png/solo_mine_GUI/03.PNG differ
diff --git a/_i18n/es/resources/user-guides/prove-payment.md b/_i18n/es/resources/user-guides/prove-payment.md
new file mode 100644
index 0000000000000000000000000000000000000000..08a92584fb9d14971fdcd1eeb80d0bb4369b6c84
--- /dev/null
+++ b/_i18n/es/resources/user-guides/prove-payment.md
@@ -0,0 +1,52 @@
+{% include untranslated.html %}
+When you send money to a party who then disputes the payment was made, you need to be able to prove the payment was made.
+
+With Bitcoin, this is typically done by looking up the transaction ID, where the origin and destination addresses are
+shown, along with the amount transacted.
+
+Monero, however, is private: that information is not available publicly on the blockchain. The steps are therefore a bit
+more involved.
+
+To prove to Charlie that she made a payment to Bob, Alice must supply Charlie three pieces of information:
+
+- the transaction ID, as is done in Bitcoin
+- Bob's address, as is done with Bitcoin
+- the transaction's key, which is new with Monero and other CryptoNote currencies
+
+When Alice made the transaction, a one time key was automatically generated just for this transaction. Alice can
+query it thus in monero-wallet-cli (new name for the old simplewallet):
+
+> get_tx_key TXID
+
+Alice would plug in her actual transaction ID instead of this TXID placeholder. All being well, the one time transaction key
+will be displayed.
+
+Note that this will only work if monero-wallet-cli is set to save transaction keys. To double check:
+
+> set
+
+If it's set to 0, set it to 1:
+
+> set store-tx-info 1
+
+Alice can now send Charlie the transaction key along with transaction ID and Bob's address.
+
+Note: if several transactions were made, this needs repeating for each such transaction.
+
+
+---
+
+Charlie now received those three pieces of information, and wants to check Alice is telling the truth: on an up to date
+blockchain, Charlie types in monero-wallet-cli:
+
+> check_tx_key TXID TXKEY ADDRESS
+
+The information supplied by Alice plugs neatly instead of the placeholders. monero-wallet-cli will use the transaction
+key to decode the transaction, and display how much this particular transaction sent to this address. Obviously,
+Charlie will want to double check with Bob the address is really his - same as with Bitcoin.
+
+Alternatively, the transaction key can be obtained in the GUI in the History tab. Click on details for each individual transaction to get the key.
+
+Note: if several transactions were made, this needs repeating for each such transaction.
+
+
diff --git a/_i18n/es/resources/user-guides/remote_node_gui.md b/_i18n/es/resources/user-guides/remote_node_gui.md
new file mode 100644
index 0000000000000000000000000000000000000000..c63f85e1bde160bc79a14cb9df3d64d8b3338721
--- /dev/null
+++ b/_i18n/es/resources/user-guides/remote_node_gui.md
@@ -0,0 +1,11 @@
+{% include untranslated.html %}
+## Finding a node
+First things first, you need to find a node to connect to! [moneroworld.com](https://moneroworld.com/#nodes) has some great resources for finding nodes. One of the easiest methods
+would be to use a node run by moneroworld, but they have a tool for finding random nodes too.
+
+## Connecting to the node from the GUI wallet
+After you enter your password for your wallet, you will see a pop up that will give you the option to "use custom settings". Click on it. You will then be
+sent to the "Settings" page in the GUI. At this point you should see two text boxes to the right of a label that says "Daemon address". In the first box (the one to the left) you need to enter the address of the node that you want to
+connect to. This address might look like `node.moneroworld.com` or it could look like any old ip address. The smaller box to the right is where you enter the node's port. The default port is `18081` but if you are using a random node the port that is used will vary. The port for node.moneroworld.com uses 18089.
+### Your screen should look a bit like this
+<img src="{{site.baseurl}}/resources/user-guides/png/remote_node/remote-node-screenshot.png" width="600">
diff --git a/_i18n/es/resources/user-guides/restore_account.md b/_i18n/es/resources/user-guides/restore_account.md
new file mode 100644
index 0000000000000000000000000000000000000000..e79cc1f0cc6700cec213fea4c7d1b3d9fb54fbf9
--- /dev/null
+++ b/_i18n/es/resources/user-guides/restore_account.md
@@ -0,0 +1,23 @@
+{% include untranslated.html %}
+## Operating Systems: Windows, Linux, Mac
+
+### Account Software: monero-wallet-cli
+
+- Retrieve your 25 word @mnemonic-seed that you saved when creating your old Monero @wallet
+
+- Open a command prompt and navigate to the drive and directory that contains monero-wallet-cli
+
+- At the command prompt type: `monero-wallet-cli --restore-deterministic-wallet`
+
+- Once you press enter you will be prompted for a wallet file name. Give your wallet a new name, any name will do
+
+- Press enter again and you will be prompted for a password. Give your wallet a new and long password
+
+- Press enter again you will be prompted to repeat the password
+
+- Press enter again and you will be prompted for the 25 word electrum style mnemonic seed that you retrieved earlier
+
+- You will then be prompted with "Restore from specific blockchain height (optional, default 0):" Default will start the restore process from the beginning of the Monero blockchain. If you don't know the specific blockchain height, just hit enter. (Specifying a specific blockchain height will start the restore process from that specific height. This will save a bit of time in scanning, if you know what starting blockchain height your initial funds were transacted for this specific account.)
+
+After you have entered the 25 word mnemonic seed and have chosen your specific blockchain height, monero-wallet-cli will generate the same public address and view key as your old wallet and begin the refresh process automatically. (Please be patient as the refresh process may take a while.)
+
diff --git a/_i18n/es/resources/user-guides/restore_from_keys.md b/_i18n/es/resources/user-guides/restore_from_keys.md
new file mode 100644
index 0000000000000000000000000000000000000000..bba53a400c3c70898e2d12d7982736d6b9f9fa07
--- /dev/null
+++ b/_i18n/es/resources/user-guides/restore_from_keys.md
@@ -0,0 +1,19 @@
+{% include untranslated.html %}
+Restoring a wallet from private keys (via the command line) is pretty simple. If you have the necessary information, with this guide you can completely restore your wallet. Note: you do NOT have to have your password to restore from keys.
+
+You need to have 3 pieces of data from your wallet, or your .keys file which holds this info and the password to decrypt it. The 3 wallet components that you need are:
+
+1. **Address**
+2. **Secret Spendkey**
+3. **Secret Viewkey**
+
+
+Then run the wallet command:
+
+`./monero-wallet-cli --generate-from-keys New_Wallet_Name.abc`
+
+Next, you'll be asked for the Address, the spendkey, the viewkey, and finally the new password for the re-generated wallet.
+
+Running this with the correct parameters will re-generate your wallet files for you and allow you to set a new password.
+
+If you run into any trouble, running `./monero-wallet-cli --help` will show you the options available to you at wallet startup. Once you're inside your wallet, running the `help` command will list the help for the commands available to you within the wallet.
diff --git a/_i18n/es/resources/user-guides/securely_purchase.md b/_i18n/es/resources/user-guides/securely_purchase.md
new file mode 100644
index 0000000000000000000000000000000000000000..508119ea0cd0c01b862ac5853aa696b866b25bb1
--- /dev/null
+++ b/_i18n/es/resources/user-guides/securely_purchase.md
@@ -0,0 +1,82 @@
+{% include untranslated.html %}
+## How to purchase Monero and securely store it.
+
+This is a guide to purchase and securely store Monero as of June 2017.
+
+#### Step 1: Buy Bitcoin
+
+There are many ways to buy Bitcoin. Two semi-reliable companies at this time are Xapo <http://www.xapo.com/> and Coinbase <http://www.coinbase.com/>. The process will involve uploading your personal identification (State ID, Passport, etc.) and will take anywhere from 2 to 10 days (or longer). Verify their reputation on Reddit before making a large purchase. Xapo uses Wire Transfer and Coinbase uses Bank Transfer (ACH in the USA). Xapo should be faster than Coinbase. Coinbase also allows small "instant" buys via a debit card but adds a large fee for this option. Once you have purchased Bitcoin, you are ready to convert it to Monero!
+
+#### Step 2: Download and create a Paper Wallet on a secure and air-gapped computer.
+
+Download the paper wallet generator at: https://moneroaddress.org and copy it to a USB stick (Direct link: https://github.com/moneromooo-monero/monero-wallet-generator/archive/master.zip).
+
+Unzip and open the paper wallet generator (monero-wallet-generator.html) into a web browser on an air-gapped computer that hasn't been used before, or has had a clean installation of the OS.
+
+Your paper wallet will have four important items:
+
+Monero Public Address
+The public address is used to receive funds to the wallet. You give this to anyone who will be sending funds to your wallet.
+
+Monero Mnemonic Seed
+The mnemonic seed is a method of storing the entire wallet that is easily recognizable to humans. This is all you need to restore your wallet at a later date.
+
+Monero Private Spend Key
+The private spend key is used to send funds from the wallet.
+
+Monero Private View Key
+The private view key is to view transactions entering the wallet. Commonly this is used to setup a view-only wallet which can see incoming transactions live on the blockchain as they are sent to a cold storage wallet.
+
+At this point you have many options. You can print the wallet on paper, save it as a PDF or text on a USB stick, burn it to CD/DVD, etc. Most likely you will want at least two or three copies, stored securely in different locations. If storing digitally, encrypt everything with a strong password. If storing on paper, do not show the wallet to anyone else who can memorize your 25 word key, or take a picture of the wallet without your permission. Sending someone a picture of the wallet is the same as giving away all of your funds.
+
+Whichever method you chose, be sure there's no copy of the Monero wallet left over on the device you used. You may need to securely delete the Monero wallet if you saved it to a disk, or make sure your printer does not save a copy in memory.
+
+*If you lose access to your Monero paper wallet the Monero will not be available to you or anyone else, ever. You wont be able to recover them!
+
+#### Side Note
+Option to encrypt an XMR mnemonic seed:
+https://xmr.llcoins.net/
+Download the html page and place it on your airgapped computer. Check the part "Encrypt/Decrypt Mnemonic Seed" and make sure you use "CN Add" with a decent password. Thanks manicminer5.
+
+
+
+#### Step 3: Convert your Bitcoin to Monero and have it sent to your Monero Paper Wallet
+
+Switch to your internet connected computer and go to www.shapeshift.io. Choose "Deposit Bitcoin" and "Receive Monero" (quick).
+
+Press Continue.
+
+Your Monero Address (the Monero Public Address on your Monero Paper Wallet)
+Paste the Monero Public address from your paper wallet where it says "Your Monero Address". But wait, since your Monero Public Address is on an airgapped computer (right?), you can't copy and paste anything... Copy it over by hand, or get a blank USB drive and copy only the Public Address to it.
+
+Refund Address (Bitcoin Public Address you can receive funds at)
+Enter a Bitcoin address that you control where a refund can be sent in case there's a problem with the transaction. It's very important that you enter a Bitcoin Public Address you control or can receive funds at. At Xapo and Coinbase this is called a Receive Address and it may change periodically.
+
+Payment ID
+Leave Payment ID blank if you are sending to your own Monero wallet or Monero paper wallet.
+
+Agree to the Terms and hit the slider to make this a "Reusable Address".
+
+Press "Start Transaction".
+
+Deposit Address (Shapeshift.io's Public Bitcoin Address created only to receive your funds)
+In the new screen that pops up, copy the Deposit Address into your clipboard (select and hit ctrl+c or edit-copy). You will send Bitcoin from Xapo/Coinbase to Shapeshift.io via this address.
+
+Go to your Xapo or Circle account, and find a Transfer or Send button. Paste the Bitcoin Deposit address into the Destination field and enter the amount of bitcoin you would like to have converted to Monero. It must be within the Deposit Min and Deposit Max range specified by Shapeshift.io. Press Send and authorize the transaction, if required.
+
+Once the send has been initiated by Xapo/Coinbase there will be a delay while the transaction enters the Bitcoin blockchain and awaits confirmation. This may be minutes or hours. You can check if the payment has been sent by looking up the Shapeshift.io Deposit address at blockchain.info. Your transaction to Shapeshift.io will show up there.
+
+When your Bitcoin transaction has been confirmed, Shapeshift.io will then begin exchanging Bitcoin (BTC) for Monero (XMR) at one of the exchanges and when it's complete, send the Monero to the address of your Cold Storage Paper Wallet! This can take minutes to hours. If there's an issue, contact Shapeshift.io. They have good support.
+
+When the Shapehift.io webpage says your transaction has been completed, you should now have Monero in your Paper Wallet!
+
+
+#### Notes and How to Verify Funds
+Because the Monero blockchain is private and untraceable, you won't be able to lookup your Monero Public Address and confirm that the funds have arrived like you might with Bitcoin. This is good for privacy, but bad for convenience.
+
+To securely verify the funds have arrived at your wallet, you will need to setup a View Only wallet. This is where that view-key comes in. To create a view-only wallet see the entry: [View Only Wallets]({{site.baseurl}}/resources/user-guides/view_only.html)
+
+To verify the funds are *still in* your wallet and have not been spent you need to create a Cold Wallet with your mnemonic key (all your funds) on an airgapped computer with an up-to-date copy of the Monero Blockchain. When finished you will have to securely erase the wallet or connect it to the internet and it becomes a Hot Wallet.
+
+
+
diff --git a/_i18n/es/resources/user-guides/solo_mine_GUI.md b/_i18n/es/resources/user-guides/solo_mine_GUI.md
new file mode 100644
index 0000000000000000000000000000000000000000..3f14c7c738efe2b7da98cdb67e28dbb50b489ec7
--- /dev/null
+++ b/_i18n/es/resources/user-guides/solo_mine_GUI.md
@@ -0,0 +1,16 @@
+{% include untranslated.html %}
+It is very easy to solo mine with the official GUI. If you have not done so already, go to the <a href="{{site.baseurl}}/downloads/">Monero downloads page</a> and download the official GUI for your operating system. Then, run the setup and be patient as Monero synchronizes with the network. You should see that it displays "Connected" in the lower left corner.
+
+<img src="/resources/user-guides/png/solo_mine_GUI/01.PNG" style="width: 600px;"/>
+
+Click on the "Advanced" tab. You should see that several other options appear. Now click on the "Mining" sub-tab.
+
+<img src="/resources/user-guides/png/solo_mine_GUI/02.PNG" style="width: 600px;"/>
+
+You should now have an option to start mining. You can optionally change the number of threads to mine with. For optimal efficiency, you should mine with your CPU's cache divided by 2. You will need to look up your CPU's specs on the manufacturer's website. If you are unsure, leave the number of threads at 1. Click the "Start mining" button.
+
+<img src="/resources/user-guides/png/solo_mine_GUI/03.PNG" style="width: 600px;"/>
+
+You are now mining with the network, as you can see on the bottom of the image. In this example, the computer is contributing 23 H/s to the Monero network. Mining helps keep the network secure, and you may get lucky and receive a reward for protecting the network.
+
+To stop mining, simply click the "Stop mining" button.
diff --git a/_i18n/es/resources/user-guides/view_only.md b/_i18n/es/resources/user-guides/view_only.md
new file mode 100644
index 0000000000000000000000000000000000000000..993bc39f30bb7c41524eaf84f0d9c4931dc1f4f8
--- /dev/null
+++ b/_i18n/es/resources/user-guides/view_only.md
@@ -0,0 +1,13 @@
+{% include untranslated.html %}
+A view-only wallet can only see which incoming transactions belong to you. It can not spend any of your Monero, in fact it can't even see outgoing transactions from this wallet. This makes view-only wallets particularly interesting for
+
+* Developers writing libraries to validate payments
+* End users validating incoming transactions to cold wallets
+
+### Creating A View-Only Wallet
+
+You can create a view-only wallet from any existing wallet.
+
+Open an existing wallet or create a new one using `monero-wallet-cli`. In the wallet, type `address` and `viewkey` to display the wallet's address and secret viewkey. Type `exit` to close the wallet.
+
+Next, create your view-only wallet by typing `monero-wallet-cli --generate-from-view-key wallet-name`. The last argument will be your new wallet's file name. You will be prompted for `Standard address` and `View key` by the wallet. Paste in your original wallet's address and secret view key. Next, enter and confirm a password for your new wallet and you're done.
diff --git a/_i18n/es/resources/user-guides/vps_run_node.md b/_i18n/es/resources/user-guides/vps_run_node.md
new file mode 100644
index 0000000000000000000000000000000000000000..fa928dea2d868450f58e75e71dcd539b0bc1b22d
--- /dev/null
+++ b/_i18n/es/resources/user-guides/vps_run_node.md
@@ -0,0 +1,48 @@
+{% include untranslated.html %}
+# monerod
+
+`monerod` is the daemon software that ships with the Monero tree. It is a console program, and manages the blockchain. While a bitcoin wallet manages both an account and the blockchain, Monero separates these: `monerod` handles the blockchain, and `monero-wallet-cli` handles the account.
+
+This guide assumes you have already set up your VPS account and are using SSH to tunnel into the server console.
+
+## Linux, 64-bit (Ubuntu 16.04 LTS)
+
+### Make sure that port 18080 is open
+`monerod` uses this port to communicate with other nodes on the Monero network.
+
+Example if using `ufw`: `sudo ufw allow 18080`
+Example if using `iptables`: `sudo iptables -A INPUT -p tcp --dport 18080 -j ACCEPT`
+
+### Download the current Monero Core binaries
+
+ wget https://downloads.getmonero.org/linux64
+
+### Make a directory and extract the files.
+
+ mkdir monero
+ tar -xjvf linux64 -C monero
+
+### Launch the daemon
+
+ cd monero
+ ./monerod
+
+### Options:
+
+Show list of all options and settings:
+
+ ./monerod --help
+
+Launch the daemon as a background process:
+
+ ./monerod --detach
+
+Monitor the output of `monerod` if running as daemon:
+
+ tail -f ~/.bitmonero/bitmonero.log
+
+Keep the VPS secure with autoupdate:
+
+https://help.ubuntu.com/community/AutomaticSecurityUpdates
+
+
diff --git a/resources/technical-specs/index.md b/_i18n/es/technical-specs.md
similarity index 98%
rename from resources/technical-specs/index.md
rename to _i18n/es/technical-specs.md
index 7ff96c8562e6627db54c5fb3867dd130364a8a16..57224b681073f29262170d5ae1201e023bd857d8 100644
--- a/resources/technical-specs/index.md
+++ b/_i18n/es/technical-specs.md
@@ -1,8 +1,4 @@
----
-layout: custom
-title: "Technical Specs"
----
-
+{% include untranslated.html %}
<div class="about-monero">
<section class="container">
<div class="row">
diff --git a/_i18n/es/the-monero-project.md b/_i18n/es/the-monero-project.md
new file mode 100644
index 0000000000000000000000000000000000000000..06fac4f50d729242bcd34f0d8b04cda9c4c92152
--- /dev/null
+++ b/_i18n/es/the-monero-project.md
@@ -0,0 +1,45 @@
+{% include untranslated.html %}
+<div class="site-wrap">
+<section class="container">
+ <div class="row">
+ <div class="left half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Kovri</h2>
+ </div>
+ </div>
+<div class="row start-xs monero-project" markdown="1">
+
+The Kovri project uses end-to-end encryption so that neither the sender nor receiver of a Monero transaction need to reveal their IP address to the other side or to third-party observers (the blockchain). This is done using the same technology that powers the dark net, i2p (Invisible Internet Protocol). The project is currently in heavy, active development and is not yet integrated with Monero.
+
+</div>
+ <div class="row center-xs">
+ <p><a href="https://www.getkovri.org" class="btn-link btn-fixed">Visit Kovri Website</a></p>
+ </div>
+ </div>
+ </div>
+ <div class="right half col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Open Alias</h2>
+ </div>
+ </div>
+<div class="row start-xs monero-project" markdown="1">
+
+The OpenAlias project simplifies cryptocurrency payments by providing FQDNs (Fully Qualified Domain Names, i.e. example.openalias.org) for Monero wallet addresses in a way that ensures everyone's privacy is secure. The project is well underway and has already been implemented in many Monero wallets.
+
+
+
+</div>
+
+ <div class="row center-xs">
+ <p><a href="https://www.openalias.org" class="btn-link btn-fixed">Visit OpenAlias Website</a></p>
+ </div>
+
+ </div>
+ </div>
+ </div>
+</section>
+</div>
\ No newline at end of file
diff --git a/_i18n/template.yml b/_i18n/template.yml
new file mode 100644
index 0000000000000000000000000000000000000000..e7f5d1aef103cd9335aa31fac1473e6690ecb1fd
--- /dev/null
+++ b/_i18n/template.yml
@@ -0,0 +1,96 @@
+langs:
+ en: English
+ es: Español
+
+global:
+ date: '%Y/%m/%d'
+ monero: Monero
+ getting_started: Getting Started
+ copyright: Copyright
+ monero_project: The Monero Project
+ sitename: getmonero.org, The Monero Project
+ wiki: Moneropedia
+ tags: Articles By Tag
+ wikimeta: on Moneropedia, the open encyclopedia of Monero knowledge
+ tagsmeta: All Monero blog articles that are tagged
+ titlemeta: on the home of Monero, a digital currency that is secure, private, and untraceable
+ terms: Terms
+ privacy: Privacy
+ copyright: Copyright
+ edit: Edit This Page
+ untranslated: This page is not yet translated. If you would like to help translate it, please see the
+titles:
+ index: Home
+ whatismonero: What is Monero (XMR)?
+ using: Using Monero
+ accepting: Accepting Monero
+ contributing: Improing Monero
+ mining: Mining Monero
+ faq: FAQ
+ downloads: Downloads
+ allposts: All Blog Posts
+ team: Monero Team
+ hangouts: Hangouts
+ events: Events
+ sponsorships: Sponsorships
+ merchants: Merchants & Services
+ about: About Monero
+ roadmap: Roadmap
+ researchlab: Monero Research Lab
+ moneropedia: Moneropedia
+ userguides: User Guides
+ developerguides: Developer Guides
+ technicalspecs: Technical Specs
+ themoneroproject: The Monero Project
+ presskit: Monero Press Kit
+ legal: Legal
+ ffs: Forum Funding System
+ ffs-cp: Completed Proposals
+ ffs-fr: Funding Required
+ ffs-ideas: Ideas
+ ffs-ot: Open Tasks
+ ffs-wip: Work in Progress
+ blogbytag: Blog by Tag
+index:
+ page_title: "Monero - secure, private, untraceable"
+ what_is_1: What is
+ what_is_2: " ?"
+ what_is_orange_block: "Monero is a secure, private, untraceable currency that is open-source and freely available for anyone to use."
+ what_is_text_block_1: "With Monero, you are your own bank; You have complete control over your funds. With Monero, your accounts and transactions are kept private."
+ what_is_text_block_2: "Want to find out more? An overview of Monero's main features are below. If you'd like to try Monero for yourself the"
+ what_is_text_block_3: "Getting Started"
+ what_is_text_block_4: "section is an excellent launching point."
+ news: News
+ the_latest: The Latest
+ private: Private
+ secure: Secure
+ untraceable: Untraceable
+ private_text: "Monero uses hidden amounts, origins and destinations of @transactions. This means that nobody knows how much you're sending in a transaction except you. This ensures that your purchases and other transfers remain private by default."
+ untraceable_text: "By taking advantage of @ring-signatures, Monero allows you to send and receive funds privately. Even though your transactions are publicly verifiable on the @blockchain, transactions use digital signatures that specify a group of signers such that the person verifying can’t tell which person actually produced the signature. Because it's ambiguous which funds have been spent, your transaction remains private and cannot be traced back to you."
+ secure_text: "Monero uses a distributed peer-to-peer @consensus network and every transaction is cryptographically signed. Your coins are safely stored on the @blockchain and can be restored at any time with the use of a 25 word @mnemonic-seed on any computer with the Monero software. Wallet files are encrypted on disk and locked with a passphrase, rendering them useless if stolen."
+ how_do_i_1: "How do I "
+ how_do_i_2: " ?"
+ get_started: get started
+ get_started_1: "The fastest way to start using Monero is with a web @account manager such as "
+ mymonero: "MyMonero"
+ get_started_2: "."
+ get_started_3: "Alternatively, if you would like to run a [full Monero node](/getting-started/running) you can download the client and a kick-starter @blockchain (to bring your local client up to speed) using the download link on the right."
+ where_can_i: Where can I
+ download_1: download
+ download_2: " ?"
+ different_os: "Need it for a different operating system?"
+ all_downloads: View all available downloads here
+ c_download: Download
+ monero_for: Monero for
+ latest_blockchain: Latest @Blockchain
+blog:
+ title_1: All
+ title_2: Blog
+ title_3: Posts
+ tagged: Tagged under
+ author: Posted by
+ date: Posted at
+ forum: Click here to join the discussion for this entry on the Monero Forum
+tags:
+ all: Articles by Tag
+ notags: There are no posts for this tag.
diff --git a/_i18n/template/community/events.md b/_i18n/template/community/events.md
new file mode 100644
index 0000000000000000000000000000000000000000..417d806152056646f8fcd384f1dffbf0f922efe4
--- /dev/null
+++ b/_i18n/template/community/events.md
@@ -0,0 +1,28 @@
+{% include untranslated.html %}
+<div markdown="1" class="text-center container description">
+Monero people are always down to get together and have a good time. Check below to see Monero-related events happening in your area.
+</div>
+
+{% for toplevel in site.data.events %}
+
+<div class="events">
+ <div class="container full col-xs-12">
+ <div class="info-block text-adapt">
+ <div class="row">
+ <div class="col-xs-12">
+ <h2>{{toplevel.event}}</h2>
+ <h3>Where</h3>
+ <p>{{toplevel.where}}</p>
+ <h3>When</h3>
+ <p>{{toplevel.when}}</p>
+ <h3>Description</h3>
+ <p>{{toplevel.description}}</p>
+ <h3>Link</h3>
+ <a>{{toplevel.link}}</a>
+ </div>
+ </div>
+ </div>
+ </div>
+</div>
+
+{%endfor%}
\ No newline at end of file
diff --git a/_i18n/template/community/hangouts.md b/_i18n/template/community/hangouts.md
new file mode 100644
index 0000000000000000000000000000000000000000..35e6a3f58b0bbea0670b855cbaa984d380df8111
--- /dev/null
+++ b/_i18n/template/community/hangouts.md
@@ -0,0 +1,97 @@
+{% include untranslated.html %}
+<div markdown="1" class="text-center container description">
+The Monero community is diverse and varied. We come from all over, but we definitely have some places we like to hang out together. You'll find most of them below. Join us!
+</div>
+
+<div class="hangouts">
+ <section class="container">
+ <ul class="row center-xs">
+ <li>
+ <a href="https://twitter.com/monerocurrency" target="_blank" rel="noreferrer noopener"><div class="social-icon twitter"></div></a>
+ </li>
+ <li>
+ <a href="https://reddit.com/r/monero" target="_blank" rel="noreferrer noopener"><div class="social-icon reddit"></div></a>
+ </li>
+ <li>
+ <a href="https://www.facebook.com/monerocurrency/" target="_blank" rel="noreferrer noopener"><div class="social-icon facebook"></div></a>
+ </li>
+ <li>
+ <a href="https://github.com/monero-project" target="_blank" rel="noreferrer noopener"><div class="social-icon github"></div></a>
+ </li>
+ </ul>
+ </section>
+
+ <section class="container">
+ <div class="row">
+ <!-- left two-thirds block-->
+ <div class="left two-thirds col-lg-8 col-md-8 col-sm-12 col-xs-12">
+ <div class="col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Workgroup Resources</h2>
+ </div>
+ </div>
+ <div class="row center-xs">
+ <p>In an effort to support organic workgroups, Monero has several resources that the community can use to meet and plan projects. Mattermost even has relays into the most popular Monero-related IRC channels.</p>
+ </div>
+ <div class="row relays around-xs">
+ <div class="col-md-4 col-sm-4 col-xs-4">
+ <p><a href="https://monero.slack.com/" class="btn-link btn-fixed">Slack</a></p>
+ </div>
+ <div class="col-md-4 col-sm-4 col-xs-4">
+ <p><a href="https://mattermost.getmonero.org/" class="btn-link btn-fixed">Mattermost</a></p>
+ </div>
+ <div class="col-md-4 col-sm-4 col-xs-4">
+ <p><a href="https://taiga.getmonero.org/" class="btn-link btn-fixed">Taiga</a></p>
+ </div>
+ </div>
+ </div>
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>IRC Channels</h2>
+ </div>
+ </div>
+ <div class="row start-xs">
+ <p>The Monero community utilizes a lot of IRC channels that each serve different purposes. Some to work, and some just to hang out. You'll find the more popular ones below.</p>
+ </div>
+ <div class="row irc">
+ {% for channel in site.data.irc %}
+ <div class="col-md-4 col-xs-12">
+ <a href="irc://chat.freenode.net/#{{ channel.channel }}">#{{ channel.channel }}</a>
+ <p>{{ channel.description }}</p>
+ </div>
+ {% endfor %}
+ </div>
+ </div>
+ </div>
+ </div>
+ <!-- end left two-thirds block-->
+
+ <!-- right one-third block-->
+ <div class="right one-third col-lg-4 col-md-4 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col"><h2>Stack Exchange</h2></div>
+ </div>
+ <div class="row start-xs">
+ <p>The Monero Stack Exchange is a quick and easy way to ask questions and get answers. Below you'll find some high quality question/answer pairs to some frequently asked questions.</p>
+ </div>
+ <div class="row start-xs sequestions">
+ <a href="https://monero.stackexchange.com/questions/4277/why-does-monero-have-higher-transaction-fees-than-bitcoin">Why does monero have higher transaction fees than bitcoin?</a>
+ <a href="https://monero.stackexchange.com/questions/4335/what-does-moneros-scaling-roadmap-look-like">What does Monero's scaling roadmap look like?</a>
+ <a href="https://monero.stackexchange.com/questions/4302/what-cryptography-primitives-concepts-other-than-the-basic-ones-does-monero-us">What cryptography primitives/concepts, other than the basic ones, does Monero use?</a>
+ <a href="https://monero.stackexchange.com/questions/4242/how-to-extract-data-from-local-blockchain">How to extract data from local blockchain?</a>
+ <a href="https://monero.stackexchange.com/questions/4302/what-cryptography-primitives-concepts-other-than-the-basic-ones-does-monero-us">Hiding TCP traffic for Monero miners?</a>
+ </div>
+ <div class="row center-xs">
+ <p><a href="https://monero.stackexchange.com" class="btn-link btn-auto">Visit Stack Exchange</a></p>
+ </div>
+ </div>
+ </div>
+ <!-- end right one-third block-->
+ </div>
+ </section>
+
+</div>
diff --git a/_i18n/template/community/merchants.md b/_i18n/template/community/merchants.md
new file mode 100644
index 0000000000000000000000000000000000000000..41e4816cbbe037c5768a73394d2b45dcb1a79901
--- /dev/null
+++ b/_i18n/template/community/merchants.md
@@ -0,0 +1,27 @@
+{% include untranslated.html %}
+<div markdown="1" class="text-center container description">
+Merchants of all kinds have come to value the financial privacy that Monero brings. Below is a list of the merchants that we know of that currently accept Monero for their goods and services. If a company no longer accepts Monero or you would like your business to be listed, please [open a GitHub issue and let us know](https://github.com/monero-project/monero-site/issues).
+</div>
+<div class="merchants">
+{% for toplevel in site.data.merchants %}
+<div class="container full" id="{{toplevel.id}}">
+ <div class="info-block">
+ <h2>{{toplevel.category}}</h2>
+ <div class="row">
+ {% assign sortedMerchants = toplevel.merchants | sort: 'name' %}
+ {% for merchants in sortedMerchants %}
+ <div class="col-md-4 col-sm-6 col-xs-12">
+ <a href="{{merchants.url}}">{{merchants.name}}</a>
+ </div>
+ {% endfor %}
+ </div>
+ </div>
+</div>
+{%endfor%}
+
+
+</div>
+
+<div markdown="1" class="text-center container description">
+*Please note: these links are being provided as a convenience and for informational purposes only; they do not constitute an endorsement by the Monero community of any products, services or opinions of the corporations or organizations or individuals listed. The Monero community bears no responsibility for the accuracy, legality, or content of these external sites. Contact the external site for answers to questions regarding its content. As always, caveat emptor ("buyer beware"); you are responsible for doing your own research. Always use judgement when making online purchases.*
+</div>
diff --git a/_i18n/template/community/sponsorships.md b/_i18n/template/community/sponsorships.md
new file mode 100644
index 0000000000000000000000000000000000000000..d301dcf84a89c4ca0d1c78ebea16d1c3cbe23b37
--- /dev/null
+++ b/_i18n/template/community/sponsorships.md
@@ -0,0 +1,97 @@
+{% include untranslated.html %}
+<div markdown="1" class="text-center container description">
+The following businesses have supported the Monero Project in its goal to bring financial privacy to the world. We couldn't be more grateful for their contributions. If you would like to sponsor the Monero Project and be listed on this page, please send an email to dev@getmonero.org.
+</div>
+
+<div>
+ <section class="container sponsors">
+ <div class="row">
+ <div class="left one-third no-pad-sm col-lg-4 col-md-4 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>My Monero</h2>
+ <a href="https://mymonero.com/#/" target="_blank" rel="noreferrer noopener"><img src="/img/mymonero.png"></a>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="center one-third no-pad-sm col-lg-4 col-md-4 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Araxis</h2>
+ <a href="https://www.araxis.com/"><img src="/img/araxis.png"></a>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="right one-third no-pad-sm col-lg-4 col-md-4 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Dome9 Security</h2>
+ <a href="https://dome9.com/"><img src="/img/dome9.png"></a>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="row">
+ <div class="left one-third no-pad-sm col-lg-4 col-md-4 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Kitware</h2>
+ <a href="https://www.kitware.com/"><img src="/img/kitware.png"></a>
+ </div>
+ </div>
+ </div>
+ </div>
+
+ <div class="center one-third no-pad-sm col-lg-4 col-md-4 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Fork Networking</h2>
+ <a href="https://www.forked.net"><img src="/img/forked_logo.png"></a>
+ </div>
+ </div>
+ </div>
+ </div>
+
+ <div class="right one-third no-pad-sm col-lg-4 col-md-4 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>JetBrains</h2>
+ <a href="http://www.jetbrains.com/"><img src="/img/jetbrains.png"></a>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="row">
+ <div class="left half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Navicat</h2>
+ <a href="https://www.navicat.com"><img src="/img/navicat.png"></a>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="right half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Symas</h2>
+ <a href="https://symas.com/"><img src="/img/symas.png"></a>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ </section>
+</div>
\ No newline at end of file
diff --git a/_i18n/template/community/team.md b/_i18n/template/community/team.md
new file mode 100644
index 0000000000000000000000000000000000000000..341d2a1941f701cf2206ba544e04c079f8fb2da8
--- /dev/null
+++ b/_i18n/template/community/team.md
@@ -0,0 +1,181 @@
+{% include untranslated.html %}
+<div class="team">
+
+ <section class="container">
+ <div class="row">
+ <div class="col-xs-12">
+ <div class="tabPanel-widget">
+ <label for="tab-1" tabindex="0"></label>
+ <input id="tab-1" type="radio" name="tabs" aria-hidden="true" checked>
+ <h2>Core</h2>
+ <div class="tabPanel-content">
+ <div class="row">
+ {% for toplevel in site.data.team %}
+ {% if toplevel.area == "Core" %}
+ {% for member in toplevel.member %}
+ <div class="half col-lg-6 col-md-6 col-sm-6 col-xs-6">
+ <div class="info-block">
+ <div class="row center-xs">
+ <h3>{{member.name}}</h3>
+ </div>
+ <div class="row center-xs">
+ <p>{{member.email}}</p>
+ </div>
+ <div class="row center-xs icons">
+ {% if member.github %}
+ <a href="{{member.github}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon github"></div></a>
+ {%endif%}
+ {% if member.twitter %}
+ <a href="{{member.twitter}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon twitter"></div></a>
+ {%endif%}
+ {% if member.reddit %}
+ <a href="{{member.reddit}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon reddit"></div></a>
+ {%endif%}
+ </div>
+ </div>
+ </div>
+ {%endfor%}
+ {%endif%}
+ {%endfor%}
+ </div>
+ </div>
+ <label for="tab-2" tabindex="0"></label>
+ <input id="tab-2" type="radio" name="tabs" aria-hidden="true">
+ <h2>Developers</h2>
+ <div class="tabPanel-content">
+ <div class="container full">
+ <div class="info-block text-adapt">
+ <div class="row">
+ <div class="col-xs-12 text-adapt">
+ <p>The Monero Project has had well over 200 contributors over the life of the project. For a complete list, please see the <a href="https://www.openhub.net/p/monero/contributors">OpenHub contributors page</a>. Below you'll find some individuals that have gone above and beyond for Monero.</p>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="row">
+ {% for toplevel in site.data.team %}
+ {% if toplevel.area == "Developers" %}
+ {% for member in toplevel.member %}
+ <div class="half col-lg-6 col-md-6 col-sm-6 col-xs-6">
+ <div class="info-block">
+ <div class="row center-xs">
+ <h3>{{member.name}}</h3>
+ </div>
+ <div class="row center-xs icons">
+ {% if member.github %}
+ <a href="{{member.github}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon github"></div></a>
+ {%endif%}
+ {% if member.twitter %}
+ <a href="{{member.twitter}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon twitter"></div></a>
+ {%endif%}
+ {% if member.reddit %}
+ <a href="{{member.reddit}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon reddit"></div></a>
+ {%endif%}
+ </div>
+ </div>
+ </div>
+ {%endfor%}
+ {%endif%}
+ {%endfor%}
+ </div>
+ </div>
+ <label for="tab-3" tabindex="0"></label>
+ <input id="tab-3" type="radio" name="tabs" aria-hidden="true">
+ <h2>Community</h2>
+ <div class="tabPanel-content">
+ <div class="row">
+ {% for toplevel in site.data.team %}
+ {% if toplevel.area == "Community" %}
+ {% for member in toplevel.member %}
+ <div class="half col-lg-6 col-md-6 col-sm-6 col-xs-6">
+ <div class="info-block">
+ <div class="row center-xs">
+ <h3>{{member.name}}</h3>
+ </div>
+ <div class="row center-xs icons">
+ {% if member.github %}
+ <a href="{{member.github}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon github"></div></a>
+ {%endif%}
+ {% if member.twitter %}
+ <a href="{{member.twitter}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon twitter"></div></a>
+ {%endif%}
+ {% if member.reddit %}
+ <a href="{{member.reddit}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon reddit"></div></a>
+ {%endif%}
+ </div>
+ </div>
+ </div>
+ {%endfor%}
+ {%endif%}
+ {%endfor%}
+ </div>
+ </div>
+ <label for="tab-4" tabindex="0"></label>
+ <input id="tab-4" type="radio" name="tabs" aria-hidden="true">
+ <h2>Research Lab</h2>
+ <div class="tabPanel-content">
+ <div class="row">
+ {% for toplevel in site.data.team %}
+ {% if toplevel.area == "Monero Research Lab" %}
+ {% for member in toplevel.member %}
+ <div class="half col-lg-6 col-md-6 col-sm-12 col-xs-6">
+ <div class="info-block">
+ <div class="row center-xs">
+ <h3>{{member.name}}</h3>
+ </div>
+ <div class="row center-xs icons">
+ {% if member.github %}
+ <a href="{{member.github}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon github"></div></a>
+ {%endif%}
+ {% if member.twitter %}
+ <a href="{{member.twitter}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon twitter"></div></a>
+ {%endif%}
+ {% if member.reddit %}
+ <a href="{{member.reddit}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon reddit"></div></a>
+ {%endif%}
+ </div>
+ </div>
+ </div>
+ {%endfor%}
+ {%endif%}
+ {%endfor%}
+ </div>
+ </div>
+ <label for="tab-5" tabindex="0"></label>
+ <input id="tab-5" type="radio" name="tabs" aria-hidden="true">
+ <h2>Special Thanks</h2>
+ <div class="tabPanel-content">
+ <div class="row">
+ {% for toplevel in site.data.team %}
+ {% if toplevel.area == "Special Thanks" %}
+ {% for member in toplevel.member %}
+ <div class="half col-lg-6 col-md-6 col-sm-12 col-xs-6">
+ <div class="info-block">
+ <div class="row center-xs">
+ <h3>{{member.name}}</h3>
+ </div>
+ <div class="row center-xs icons">
+ {% if member.github %}
+ <a href="{{member.github}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon github"></div></a>
+ {%endif%}
+ {% if member.twitter %}
+ <a href="{{member.twitter}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon twitter"></div></a>
+ {%endif%}
+ {% if member.reddit %}
+ <a href="{{member.reddit}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon reddit"></div></a>
+ {%endif%}
+ </div>
+ </div>
+ </div>
+ {%endfor%}
+ {%endif%}
+ {%endfor%}
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+</section>
+
+
+</div>
\ No newline at end of file
diff --git a/_i18n/template/downloads.md b/_i18n/template/downloads.md
new file mode 100644
index 0000000000000000000000000000000000000000..ae8003b289a624579b2584ddb983fcb130faedbc
--- /dev/null
+++ b/_i18n/template/downloads.md
@@ -0,0 +1,142 @@
+{% include untranslated.html %}
+<div class="downloads">
+
+<div class="container description" markdown="1">
+
+If you need help choosing the correct application, please click [here](https://www.reddit.com/r/Monero/comments/64b5lf/what_is_the_best_monero_wallet/) for a quick answer, then select the appropriate release for your operating system below.
+Note: the SHA256 hashes are listed by the downloads for convenience, but a GPG-signed list of the hashes is at [getmonero.org/downloads/hashes.txt](https://getmonero.org/downloads/hashes.txt) and should be treated as canonical, with the signature checked against the appropriate GPG key in the source code (in /utils/gpg_keys).
+
+</div>
+<div class="container full downdropdown">
+<div class="info-block download-nav row middle-xs between-xs" id="selections">
+
+ <div class="col"><a href="#windows">Windows</a></div>
+ <div class="col"><a href="#mac">Mac</a></div>
+ <div class="col"><a href="#linux">Linux</a></div>
+ <div class="col"><a href="#arm">Arm (v7 & 8)</a></div>
+ <div class="col"><a href="#bsd">BSD</a></div>
+ <div class="col"><a href="#source">Source & Blockchain</a></div>
+ <div class="col"><a href="#mobilelight">Mobile & Light</a></div>
+ <div class="col"><a href="#hardware">Hardware</a></div>
+
+</div>
+</div>
+
+<div class="container full">
+ <div class="info-block row center-xs" id="pick-platform">
+ <div class="mob dropdowndrop">
+ <input id="check01" type="checkbox" name="menu"/>
+ <label for="check01">Choose your OS</label>
+ <ul id="menu">
+ <li><a href="#windows">Windows</a></li>
+ <li><a href="#mac">Mac</a></li>
+ <li><a href="#linux">Linux</a></li>
+ <li><a href="#arm">Arm (v7 & 8)</a></li>
+ <li><a href="#bsd">BSD</a></li>
+ <li><a href="#source">Source & Blockchain</a></li>
+ <li><a href="#mobilelight">Mobile & Light</a></li>
+ <li><a href="#hardware">Hardware</a></li>
+ </ul>
+ </div>
+ </div>
+</div>
+
+
+<div class="download-platforms">
+
+{% for data_downloads in site.data.downloads %}
+
+<section class="container full" id="{{ data_downloads.id}}">
+ <div class="info-block">
+ <h2>
+ {% if data_downloads.icon != null %}
+ <span class="{{data_downloads.icon}}"></span>
+ {% endif %}
+ {{data_downloads.platform}}
+ </h2>
+ {% if data_downloads.version != null %}
+ <p class="text-center">Current Version: {{ data_downloads.version }} {{ data_downloads.tag }}</p>
+ {%endif%}
+
+
+
+{% if data_downloads.cli_hash == "source" %}
+<div class="row">
+<div class="col-md-8 col-md-offset-2 col-sm-12 col-xs-12">
+<h4 id="{{ data_downloads.platform | slugify }}">
+ <a href="{{ data_downloads.cli_url }}">Source Code</a>
+</h4>
+</div>
+<div class="col-md-8 col-md-offset-2 col-sm-12 col-xs-12" markdown="1">
+If you'd prefer to use a blockchain bootstrap, instead of syncing from scratch, you can [use this link for the most current bootstrap](https://downloads.getmonero.org/blockchain.raw). It is typically much faster to sync from scratch, however, and it also takes a lot less RAM (import is very greedy).
+</div>
+</div>
+{% elsif data_downloads.id == "hardware" %}
+<div class="row">
+<div class="col-md-8 col-md-offset-2 col-sm-12 col-xs-12">
+<p>The Monero community has just funded a <a href="https://forum.getmonero.org/9/work-in-progress/88149/dedicated-monero-hardware-wallet" target="_blank" rel="noreferrer, noopener">Dedicated Hardware Wallet</a> which is now in progress. As well, Ledger is working on <a href="https://github.com/LedgerHQ/blue-app-monero" target="_blank" rel="noreferrer, noopener">integrating Monero into their hardware wallets</a>.</p>
+</div></div>
+
+{% elsif data_downloads.id == "mobilelight" %}
+<div class="row">
+<div class="col-md-8 col-md-offset-2 col-sm-12 col-xs-12">
+<p>The following are mobile or light wallets that are deemed safe by trusted members of the community. If there is a wallet that is not on here, you can request the community check it out. Go to our <a href="/community/hangouts/">Hangouts</a> page to see where we are.</p>
+</div>
+</div>
+<div class="row center-xs">
+ <div class="col-xs-6">
+ <a href="https://mymonero.com"><img src="/img/mymonero.png" alt="MyMonero Logo"></a>
+ </div>
+ <div class="col-xs-6">
+ <a href="https://monerujo.io"><img style="height: 115px;" src="/img/Monerujo-wallet.png" alt="Monerujo Logo"></a>
+ </div>
+</div>
+
+
+{% elsif data_downloads.gui_hash == nil and data_downloads.cli_hash != nil %}
+<div class="row"><div class="col-md-8 col-md-offset-2 col-sm-12 col-xs-12"><h4 id="{{ data_downloads.platform | slugify }}">
+ <a href="//downloads.getmonero.org/cli/{{ data_downloads.cli_url }}"> {{ data_downloads.platform }} (Command-line Tools Only)</a>
+ </h4></div></div>
+ <div class="row"><div class="col-md-8 col-md-offset-2 col-sm-12 col-xs-12">
+ <p><strong>SHA256 Hash:</strong></p> <p class="hash"> {{ data_downloads.cli_hash }}</p></div>
+</div>
+{% elsif data_downloads.gui_hash != nil and data_downloads.cli_hash == nil %}
+<div class="row">
+
+<h4 id="{{ data_downloads.platform | slugify }}">
+ <a href="//downloads.getmonero.org/gui/{{ data_downloads.gui_url }}">{{ data_downloads.platform }}</a>
+ </h4></div>
+<div class="row">
+<p><strong>SHA256 Hash:</strong></p> <p class="hash"> {{ data_downloads.gui_hash }}</p>
+</div>
+{% elsif data_downloads.gui_hash != nil and data_downloads.cli_hash != nil %}
+<div class="row start-md">
+<div class="col-md-6 col-sm-12" >
+
+<h4 id="{{ data_downloads.platform | slugify }}">
+ <a href="//downloads.getmonero.org/gui/{{ data_downloads.gui_url }}">{{ data_downloads.platform }}</a>
+</h4>
+<p><strong>SHA256 Hash (GUI):</strong></p> <p class="hash"> {{ data_downloads.gui_hash }}</p>
+
+</div>
+
+<div class="col-md-6 col-sm-12">
+<h4>
+ <a href="//downloads.getmonero.org/cli/{{ data_downloads.cli_url }}">{{ data_downloads.platform }} (Command-Line Tools Only)</a>
+</h4>
+<p><strong>SHA256 Hash (CLI):</strong></p> <p class="hash"> {{ data_downloads.cli_hash }}</p>
+</div>
+</div>
+{% endif %}
+ </div>
+</section>
+
+{% endfor %}
+
+</div>
+<a href="#" class="arrow-up"><i></i></a>
+
+</div>
+
+
+
diff --git a/_i18n/template/get-started/accepting.md b/_i18n/template/get-started/accepting.md
new file mode 100644
index 0000000000000000000000000000000000000000..1a6f315f00a7cd51739ee788f35b365a4f61243c
--- /dev/null
+++ b/_i18n/template/get-started/accepting.md
@@ -0,0 +1,90 @@
+{% include untranslated.html %}
+<section class="container">
+ <div class="row">
+ <!-- left two-thirds block-->
+ <div class="full">
+ <div class="info-block text-adapt">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Instructions for the Command-Line Interface</h2>
+ </div>
+ </div>
+<div markdown="1">
+
+### The Basics
+
+Monero works a little differently to what you may have become accustomed to from other @cryptocurrencies. In the case of a digital currency like Bitcoin and its many derivatives merchant payment systems will usually create a new recipient @address for each payment or user.
+
+However, because Monero has @stealth-addresses there is no need to have separate recipient addresses for each payment or user, and a single @account address can be published. Instead, when receiving payments a merchant will provide the person paying with a "payment ID".
+
+A @payment-ID is a hexadecimal string that is 64 characters long, and is normally randomly created by the merchant. An example of a payment ID is:
+```
+666c75666679706f6e7920697320746865206265737420706f6e792065766572
+```
+
+### Checking for a Payment in monero-wallet-cli
+
+If you want to check for a payment using monero-wallet-cli you can use the "payments" command followed by the payment ID or payment IDs you want to check. For example:
+
+```
+[wallet 49VNLa]: payments 666c75666679706f6e7920697320746865206265737420706f6e792065766572
+ payment transaction height amount unlock time
+ 666c75666679706f6e79206973207 7ba4cd810c9b4096869849458181e98e 441942 30.00000 0
+[wallet 49VNLa]: â–ˆ
+```
+
+If you need to check for payments programmatically, then details follow the next section.
+
+### Receiving a Payment Step-by-Step
+
+* Generate a random 64 character hexadecimal string for the payment
+* Communicate the payment ID and Monero address to the individual who is making payment
+* Check for the payment using the "payments" command in monero-wallet-cli
+
+### Checking for a Payment Programmatically
+
+In order to check for a payment programmatically you can use the get_payments or get_bulk_payments JSON RPC API calls.
+
+*get_payments*: this requires a payment_id parameter with a single payment ID.
+
+*get_bulk_payments*: this is the preferred method, and requires two parameters, payment_ids - a JSON array of payment IDs - and an optional min_block_height - the block height to scan from.
+
+An example of returned data is as follows:
+
+```
+[ monero->~ ]$ curl -X POST http://127.0.0.1:18500/json_rpc -d '{"jsonrpc":"2.0","method":"get_bulk_payments","id":"test", "params":{"payment_ids": ["666c75666679706f6e7920697320746865206265737420706f6e792065766572"]}}' -H "Content-Type: application/json"
+{
+ "id": "test",
+ "jsonrpc": "2.0",
+ "result": {
+ "payments": [{
+ "amount": 30000000000000,
+ "block_height": 441942,
+ "payment_id": "666c75666679706f6e7920697320746865206265737420706f6e792065766572",
+ "tx_hash": "7ba4cd810c9b4096869849458181e98e18b6474ab66415de0f4ccf7ab1162fdf",
+ "unlock_time": 0
+ }]
+ }
+}
+```
+
+It is important to note that the amounts returned are in base Monero units and not in the display units normally used in end-user applications. Also, since a transaction will typically have multiple outputs that add up to the total required for the payment, the amounts should be grouped by the tx_hash or the payment_id and added together. Additionally, as multiple outputs can have the same amount, it is imperative not to try and filter out the returned data from a single get_bulk_payments call.
+
+Before scanning for payments it is useful to check against the daemon RPC API (the get_info RPC call) to see if additional blocks have been received. Typically you would want to then scan only from that received block on by specifying it as the min_block_height to get_bulk_payments.
+
+### Programatically Scanning for Payments
+
+* Get the current block height from the daemon, only proceed if it has increased since our last scan
+* Call the get_bulk_payments RPC API call with our last scanned height and the list of all payment IDs in our system
+* Store the current block height as our last scanned height
+* Remove duplicates based on transaction hashes we have already received and processed
+
+</div>
+ </div>
+ </div>
+
+
+ <!-- end right one-third block-->
+ </div>
+ </section>
+
\ No newline at end of file
diff --git a/_i18n/template/get-started/contributing.md b/_i18n/template/get-started/contributing.md
new file mode 100644
index 0000000000000000000000000000000000000000..ac8467a14fdb8887c90008a8dc4f7617e6100c71
--- /dev/null
+++ b/_i18n/template/get-started/contributing.md
@@ -0,0 +1,93 @@
+{% include untranslated.html %}
+<div markdown="1" class="text-center container description">
+Monero is an open-source, community-driven project. Described below are several ways to support the project.
+</div>
+
+<div class="contribute">
+ <section class="container">
+ <div class="row">
+ <!-- full block-->
+ <div class="full col-lg-12 col-md-12 col-sm-12 col-xs-12">
+ <div class="info-block text-adapt">
+ <div class="row center-xs">
+ <div class="col"><h2>Support the Network</h2></div>
+ </div>
+<div class="row start-xs" markdown="1">
+
+### Develop
+Monero is primarily written in C++. As it is a decentralized project, anyone is welcome to add or make changes to existing code. Pull requests are merged based on community consensus. See the <a href="https://github.com/monero-project"> repositories</a> and outstanding <a href="https://github.com/monero-project/monero/issues">issues</a>.
+
+### Run a Full Node
+Run monerod with port 18080 open. Running a full node ensures maximum privacy when transacting with Monero. It also improves distribution of the blockchain to new users.
+
+### Mine
+Mining ensures the Monero network remains decentralized and secure. In the Monero graphical user interface and command-line interface, background mining may be activated. Additional resources for mining may be viewed [here](https://reddit.com/r/MoneroMining).
+
+</div>
+ </div>
+ </div>
+ <!-- end full block-->
+ <!-- full block-->
+ <div class="full col-lg-12 col-md-12 col-sm-12 col-xs-12">
+ <div class="info-block text-adapt">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>View the Forum Funding System</h2>
+ </div>
+ </div>
+ <div class="row start-xs">
+ <p>Monero utilizes a <a href="https://forum.getmonero.org">forum funding system</a> whereby projects are proposed for development and community-funded. Funding is held in escrow and remunerated to developers once programming milestones are achieved. Anyone may generate new proposals or fund existing ones.</p>
+ </div>
+ </div>
+ </div>
+ <!-- full block-->
+ <!-- full block-->
+ <div class="full col-lg-12 col-md-12 col-sm-12 col-xs-12">
+ <div class="info-block text-adapt">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Donate</h2>
+ </div>
+ </div>
+ <div class="row start-xs">
+ <p>Ongoing development is supported by donations and <a href="{{site.baseurl}}/community/sponsorships/">sponsorships</a>.</p>
+ </div>
+ <div class="row center-xs">
+ <div class="col-lg-6">
+ <img src="/img/donate-monero.png" alt=""/>
+ </div>
+ <div class="col-lg-6">
+ <img src="/img/donate-bitcoin.png" alt=""/>
+ </div>
+ </div>
+ <div class="row start-xs">
+ <div class="col-xs-12">
+ <h3>Donating Monero</h3>
+ <p>Donations may be sent to donate.getmonero.org or 44AFFq5kSiGBoZ4NMDwYtN18obc8AemS33DBLWs3H7otXft3XjrpDtQGv7SqSsaBYBb98uNbr2VBBEt7f2wfn3RVGQBEP3A</p>
+ </div>
+ </div>
+ <div class="row start-xs">
+ <div class="col-xs-12">
+ <h3>Donating Bitcoin</h3>
+ <p>Donations may be sent to donate.getmonero.org or 1KTexdemPdxSBcG55heUuTjDRYqbC5ZL8H</p>
+ </div>
+ </div>
+ <div class="row start-xs">
+ <div class="col-xs-12">
+ <h3>Other</h3>
+ <p>E-mail <a href="mailto:dev@getmonero.org">dev@getmonero.org</a> for alternative means of donating or if you would like to become a sponsor for the Monero Project.</p>
+ </div>
+ </div>
+ </div>
+ </div>
+ <!-- full block-->
+
+
+
+
+
+
+ </div>
+ </section>
+
+</div>
diff --git a/_i18n/template/get-started/faq.md b/_i18n/template/get-started/faq.md
new file mode 100644
index 0000000000000000000000000000000000000000..4aa8d532ac4f994d0a2cda4390f3394bc76dbfe8
--- /dev/null
+++ b/_i18n/template/get-started/faq.md
@@ -0,0 +1,136 @@
+{% include untranslated.html %}
+<div class="tab">
+ <input id="tab-one" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-one" class="accordion">How does Monero have value?</label>
+
+<div class="tab-content" markdown="1">
+
+Monero has value because people are willing to buy it. If no one is willing to buy Monero, then it will not have any value. Monero’s price increases if demand exceeds supply, and it decreases if supply exceeds demand.
+
+</div>
+
+</div>
+
+<div class="tab">
+ <input id="tab-two" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-two" class="accordion">How can I get Monero?</label>
+
+<div class="tab-content" markdown="1">
+
+You can buy Monero from an exchange or from an individual. Alternatively, you can try mining Monero to get coins from the block reward.
+</div>
+
+</div>
+
+<div class="tab">
+ <input id="tab-three" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-three" class="accordion">What is a mnemonic seed?</label>
+
+<div class="tab-content" markdown="1">
+
+A mnemonic seed is a set of 25 words that can be used to restore your account anywhere. Keep these words safe and do not share them with someone else. You can use this seed to restore your account, even if your computer crashes.
+</div>
+
+</div>
+
+<div class="tab">
+ <input id="tab-four" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-four" class="accordion">How is Monero’s privacy different from other coins?</label>
+
+<div class="tab-content" markdown="1">
+
+Monero uses three different privacy technologies: ring signatures, ring confidential transactions (RingCT), and stealth addresses. These hide the sender, amount, and receiver in the transaction, respectively. All transactions on the network are private by mandate; there is no way to accidentally send a transparent transaction. This feature is exclusive to Monero. You do not need to trust anyone else with your privacy.
+</div>
+
+</div>
+
+<div class="tab">
+ <input id="tab-five" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-five" class="accordion">Why is my wallet taking so long to sync?</label>
+
+<div class="tab-content" markdown="1">
+
+If you are running a full node locally, you need to copy the entire blockchain to your computer. This can take a long time, especially on an old hard drive or slow internet connection. If you are using a remote node, your computer still needs to request a copy of all the outputs, which can take several hours. Be patient, and if you would like to sacrifice some privacy for faster sync times, consider using a lightweight wallet instead.
+</div>
+
+</div>
+
+<div class="tab">
+ <input id="tab-six" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-six" class="accordion">What is the different between a lightweight and a normal wallet?</label>
+
+<div class="tab-content" markdown="1">
+
+For a lightweight wallet, you give your view key to a node, who scans the blockchain and looks for incoming transactions to your account on your behalf. This node will know when you receive money, but it will not know how much you receive, who you received it from, or who you are sending money to. Depending on your wallet software, you may be able to use a node you control to avoid privacy leaks. For more privacy, use a normal wallet, which can be used with your own node.
+</div>
+
+</div>
+
+<div class="tab">
+ <input id="tab-seven" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-seven" class="accordion">How is Monero different from Bitcoin?</label>
+
+<div class="tab-content" markdown="1">
+
+Monero is not based on Bitcoin. It is based on the CryptoNote protocol. Bitcoin is a completely transparent system, where people can see exactly how much money is being sent from one user to another. Monero hides this information to protect user privacy in all transactions. It also has a dynamic block size and dynamic fees, an ASIC-resistant proof of work, and a tail coin emission, among several other changes.
+</div>
+
+</div>
+
+<div class="tab">
+ <input id="tab-eight" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-eight" class="accordion">Does Monero have a block size limit?</label>
+
+<div class="tab-content" markdown="1">
+
+No, Monero does not have a hard block size limit. Instead, the block size can increase or decrease over time based on demand. It is capped at a certain growth rate to prevent outrageous growth.
+</div>
+
+</div>
+
+<div class="tab">
+ <input id="tab-nine" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-nine" class="accordion">What is a blockchain?</label>
+
+<div class="tab-content" markdown="1">
+
+A blockchain is a system that stores a copy of all transaction history on the Monero network. Every two minutes, a new block with the latest transaction information is added to the blockchain. This chain allows the network to verify the amount of money accounts have and make it resilient to attacks and centralization attempts.
+</div>
+
+</div>
+
+<div class="tab">
+ <input id="tab-ten" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-ten" class="accordion">What is Kovri?</label>
+
+<div class="tab-content" markdown="1">
+
+Kovri is an I2P router written in C++. I2P is a hidden network like Tor with several technical differences. Kovri is an independent project of Monero, but it will work with Monero and several other projects. Kovri hides the transaction broadcast, so other nodes do not know who created transactions. In adversarial conditions, Kovri can be used to hide all Monero traffic through I2P, which would prevent people from knowing Monero is being used. Kovri is currently in alpha, and it is not yet fully integrated in Monero. Learn more about Kovri at the [project website.](https://getkovri.org)
+</div>
+
+</div>
+
+<div class="tab">
+ <input id="tab-eleven" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-eleven" class="accordion">What is fungibility, and why is it important?</label>
+
+<div class="tab-content" markdown="1">
+
+Fungibility is a simple property of money such that there are no differences between two amounts of the same value. If two people exchanged a 10 and two 5’s, then no one would lose out. However, let’s suppose that everyone knows the 10 was previously used in a ransomware attack. Is the other person still going to make the trade? Probably not, even if the person with the 10 has no connection with the ransomware. This is a problem, since the receiver of money needs to constantly check the money they are receiving to not end up with tainted coins. Monero is fungible, which means people do not need to go through this effort.
+</div>
+
+</div>
+
+<div class="tab">
+ <input id="tab-twelve" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-twelve" class="accordion">If Monero is so private how do we know they're not being created out of thin air?</label>
+
+<div class="tab-content" markdown="1">
+In Monero, every transaction output is uniquely associated with a key image that can only be generated by the holder of that output. Key images that are used more than once are rejected by the miners as double-spends and cannot be added to a valid block. When a new transaction is received, miners verify that the key image does not already exist for a previous transaction to ensure it's not a double-spend.
+
+We can also know that transaction amounts are valid even though the value of the inputs that you are spending and the value of the outputs you are sending are encrypted (these are hidden to everyone except the recipient). Because the amounts are encrypted using Pedersen commitments what this means is that no observers can tell the amounts of the inputs and outputs, but they can do math on the Pedersen commitments to determine that no Monero was created out of thin air.
+
+As long as the encrypted output amounts you create is equal to the sum of the inputs that are being spent (which include an output for the recipient and a change output back to yourself and the unencrypted transaction fee), then you have a legitimate transaction and know no Monero is being created out of thin air. 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.
+</div>
+
+</div>
diff --git a/_i18n/template/get-started/mining.md b/_i18n/template/get-started/mining.md
new file mode 100644
index 0000000000000000000000000000000000000000..2a94422954da115ceb0bbe83c0f6653bf79d8934
--- /dev/null
+++ b/_i18n/template/get-started/mining.md
@@ -0,0 +1,86 @@
+<div class="mining">
+<div class="center-xs container description">
+<p>Monero is a cryptocurrency that relies on proof-of-work mining to achieve distributed consensus. Below you'll find some information and resources on how to begin mining.</p>
+
+<p><strong>The Monero Project does not endorse any particular pool, software, or hardware, and the content below is provided for informational purposes only.</strong></p>
+</div>
+
+<section class="container">
+ <div class="row">
+ <!-- full block-->
+ <div class="full col-lg-12 col-md-12 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Support</h2>
+ </div>
+ </div>
+ <div class="row center-xs">
+ <p>See <a href="{{site.baseurl}}/community/hangouts/"> Hangouts</a>, <a href="https://www.reddit.com/r/MoneroMining/" target="_blank" rel="noreferrer noopener">/r/moneromining</a> and <a href="irc://chat.freenode.net/#monero-pools" target="_blank" rel="noreferrer noopener">#monero-pools</a>.</p>
+ </div>
+ </div>
+ </div>
+ <!-- end full block -->
+ </div>
+ </section>
+<section class="container">
+ <div class="row">
+ <div class="left half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Pools</h2>
+ </div>
+ </div>
+ <div class="row center-xs">
+ <p>A listing of trusted Monero pools is found <a href="http://moneropools.com/"> here</a>.</p>
+ </div>
+ </div>
+ </div>
+ <div class="right half col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Hardware Benchmarking</h2>
+ </div>
+ </div>
+ <div class="row center-xs">
+ <p>See <a href="http://monerobenchmarks.info/">here</a> for a listing of GPUs/CPUs and their respective hashrates.</p>
+ </div>
+ </div>
+ </div>
+ </div>
+ </section>
+ <section class="container">
+ <div class="row">
+ <!-- full block-->
+ <div class="full col-lg-12 col-md-12 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Mining Software</h2>
+ </div>
+ </div>
+ <div class="row center-xs">
+ <p>Note that some miners may have developer fees.</p>
+ </div>
+ <div class="row center-xs">
+ <p><a href="https://github.com/fireice-uk/xmr-stak" target="_blank" rel="noreferrer noopener">XMR Stak</a></p>
+ </div>
+ <div class="row center-xs">
+ <p><a href="https://github.com/xmrig/xmrig" target="_blank" rel="noreferrer noopener">XMRig</a></p>
+ </div>
+ <div class="row center-xs">
+ <p><a href="https://github.com/xmrig/xmrig-amd" target="_blank" rel="noreferrer noopener">XMRig AMD</a></p>
+ </div>
+ <div class="row center-xs">
+ <p><a href="https://github.com/xmrig/xmrig-nvidia" target="_blank" rel="noreferrer noopener">XMRig NVIDIA</a></p>
+ </div>
+ </div>
+ </div>
+ <!-- end full block -->
+ </div>
+ </section>
+
+
+</div>
\ No newline at end of file
diff --git a/_i18n/template/get-started/using.md b/_i18n/template/get-started/using.md
new file mode 100644
index 0000000000000000000000000000000000000000..74fed473139e40f5da00d08411344a813a395aa1
--- /dev/null
+++ b/_i18n/template/get-started/using.md
@@ -0,0 +1,99 @@
+{% include untranslated.html %}
+<div class="text-center container description">
+ <p>Transacting with Monero can be made easy. This page is designed to guide users in that process.</p>
+</div>
+<div class="using">
+ <section class="container">
+ <div class="row">
+ <!-- full block-->
+ <div class="full col-lg-12 col-md-12 col-sm-12 col-xs-12">
+ <div class="info-block text-adapt">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>1. Learn</h2>
+ </div>
+ </div>
+ <div class="row start-xs">
+ <p>Monero is a secure, private, and untraceable cryptocurrency. The developers and community are committed to protecting these values. Learn more by reading the <a href="{{site.baseurl}}/get-started/what-is-monero/">What is Monero</a> page. The <a href="https://github.com/monero-project">source code</a> is also available for review and discussion.</p>
+ </div>
+ </div>
+ </div>
+ <!-- end full block -->
+ </div>
+ </section>
+ <section class="container">
+ <div class="row">
+ <div class="left half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>2. Request Support</h2>
+ </div>
+ </div>
+ <div class="row start-xs">
+ <p>There is a large and supportive community that will assist if you experience any difficulty. See the <a href="{{site.baseurl}}/community/hangouts/">Hangouts</a> page for more information.</p>
+ </div>
+ </div>
+ </div>
+ <div class="right half col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>3. Generate a Wallet</h2>
+ </div>
+ </div>
+ <div class="row start-xs">
+ <p>A Monero wallet is required to secure your own funds. See the <a href="{{site.baseurl}}/downloads/">Downloads</a> page for a listing of available wallets.</p>
+ <p>The easiest way to run a Monero node, without affecting your home bandwidth, is to purchase a VPS (Virtual Private Server). We strongly recommend <a href="https://interserver.net/dock/vps-231552.html">InterServer.net</a> using the 'MONERO' coupon code to get a discount over and above their already cheap $6/month VPS. Using this coupon code and/or <a href="https://interserver.net/dock/vps-231552.html">our affiliate link</a> will also assist in the ongoing funding of Monero development.</p>
+ </div>
+ </div>
+ </div>
+ </div>
+ </section>
+ <section class="container">
+ <div class="row">
+ <!-- full block-->
+ <div class="full col-lg-12 col-md-12 col-sm-12 col-xs-12">
+ <div class="info-block text-adapt">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>4. Acquire Monero</h2>
+ </div>
+ </div>
+ <div class="row start-xs">
+ <p>Monero may be purchased on an <a href="{{site.baseurl}}/community/merchants#exchanges">exchange</a> with fiat or other cryptocurrencies. An alternate way of acquiring Monero is via <a href="{{site.baseurl}}/get-started/mining/">mining</a>, the computationally-complex process whereby transactions are immutably recorded on the blockchain.</p>
+ </div>
+ </div>
+ </div>
+ <!-- end full block -->
+ </div>
+ </section>
+ <section class="container">
+ <div class="row">
+ <div class="left half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>5. Send and Receive Monero</h2>
+ </div>
+ </div>
+ <div class="row start-xs">
+ <p>Learn how to send and receive Monero by viewing the <a href="{{site.baseurl}}/get-started/accepting/">guide</a>.</p>
+ </div>
+ </div>
+ </div>
+ <div class="right half col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>6. Transact with Monero</h2>
+ </div>
+ </div>
+ <div class="row start-xs">
+ <p>Monero may be used to purchase many goods and services. For a listing, see the <a href="{{site.baseurl}}/community/merchants/">Merchants</a> page. </p>
+ </div>
+ </div>
+ </div>
+ </div>
+ </section>
+</div>
diff --git a/_i18n/template/get-started/what-is-monero.md b/_i18n/template/get-started/what-is-monero.md
new file mode 100644
index 0000000000000000000000000000000000000000..cb8f0c303936c1d1cf6e0552e8505b7278c45eb0
--- /dev/null
+++ b/_i18n/template/get-started/what-is-monero.md
@@ -0,0 +1,120 @@
+{% include untranslated.html %}
+<div class="site-wrap">
+ <section class="container">
+ <div class="row">
+ <section class="container about-monero full col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col"><h2>What you need to know</h2></div>
+ </div>
+ <div class="row middle-xs info-block-row private">
+ <div class="col-lg-7 col-md-6 col-sm-8 col-xs-12 why-text">
+ <h3>Monero is the leading cryptocurrency with a focus on private and censorship-resistant transactions.</h3>
+ <p>Most existing cryptocurrencies, including Bitcoin and Ethereum, have transparent blockchains, meaning that transactions are openly verifiable and traceable by anyone in the world. Furthermore, sending and receiving addresses for these transactions may potentially be linkable to a person's real-world identity. </p>
+ <p>Monero uses cryptography to shield sending and receiving addresses, as well as transacted amounts.</p>
+ </div>
+ <div class="col-lg-5 col-md-6 col-sm-4 col-xs-12 last-sm first-xs center-xs">
+ <img src="/img/crypto-lock.png" alt="Encrypted lock" class="main-icon">
+ </div>
+ </div>
+ <div class="row middle-xs info-block-row">
+ <div class="col-lg-5 col-md-6 col-sm-4 col-xs-12 center-xs">
+ <img src="/img/monero-classified.png" alt="Classified document" class="main-icon">
+ </div>
+ <div class="col-lg-7 col-md-6 col-sm-8 col-xs-12 why-text">
+ <h3>Monero transactions are confidential and untraceable.</h3>
+ <p>Every Monero transaction, by default, obfuscates sending and receiving addresses as well as transacted amounts. This always-on privacy means that every Monero user's activity enhances the privacy of all other users, unlike selectively transparent cryptocurrencies (e.g. Z-Cash).</p>
+ <p>Monero is fungible. By virtue of obfuscation, Monero cannot become tainted through participation in previous transactions. This means Monero will always be accepted without the risk of censorship.</p>
+ <p>The Kovri Project, <a href="https://getkovri.org/">currently in development</a>, will route and encrypt transactions via I2P Invisible Internet Project nodes. This will obfuscate a transactor's IP address and provide further protection against network monitoring.</p>
+ </div>
+
+ </div>
+ <div class="row middle-xs info-block-row">
+ <div class="col-lg-7 col-md-6 col-sm-8 col-xs-12 why-text">
+ <h3>Monero is a grassroots community attracting the world's best cryptocurrency researchers and engineering talent.</h3>
+ <p>Over <a href="https://www.openhub.net/p/monero" target="_blank" rel="noreferrer noopener">240 developers</a> have contributed to the Monero project, including 30 core developers. Forums and chat channels are welcoming and active.</p>
+ <p>Monero's Research Lab, Core Development Team and Community Developers are constantly pushing the frontier of what is possible with cryptocurrency privacy and security.</p>
+ <p>Monero is not a corporation. It is developed by cryptography and distributed systems experts from all over the world that donate their time or are funded by community donations. This means that Monero can't be shut down by any one country and is not constrained by any particular legal jurisdiction.</p>
+ </div>
+ <div class="col-lg-5 col-md-6 col-sm-4 col-xs-12 last-sm first-xs center-xs">
+ <img src="/img/academic-growth.png" alt="Academic growth" class="main-icon">
+ </div>
+ </div>
+ <div class="row middle-xs info-block-row">
+ <div class="col-lg-5 col-md-6 col-sm-4 col-xs-12 center-xs">
+ <img src="/img/monero-electronic-cash.png" alt="Electronic cash" class="main-icon">
+ </div>
+ <div class="col-lg-7 col-md-6 col-sm-8 col-xs-12 why-text">
+ <h3>Monero is electronic cash that allows fast, inexpensive payments to and from anywhere in the world.</h3>
+ <p>There are no multi-day holding periods and no risk of fraudulent chargebacks. It is safe from ‘capital controls’ - these are measures that restrict the flow of traditional currencies, sometimes to an extreme degree, in countries experiencing economic instability.</p>
+ </div>
+ </div>
+ </div>
+ </section>
+ <section class="full col-xs-12 monero-vid">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col"><h2>Monero Videos</h2></div>
+ </div>
+ <div class="row center-xs">
+ <div class="col-xs-12 carousel-container">
+ <ul class="carousel my-carousel">
+ <input class="carousel-activator" type="radio" id="A" name="activator" checked="checked"/>
+ <input class="carousel-activator" type="radio" id="B" name="activator"/>
+ <input class="carousel-activator" type="radio" id="C" name="activator"/>
+ <input class="carousel-activator" type="radio" id="D" name="activator"/>
+ <div class="carousel-controls">
+ <label class="carousel-control carousel-control-backward" for="D"></label>
+ <label class="carousel-control carousel-control-forward" for="B"></label>
+ </div>
+ <div class="carousel-controls">
+ <label class="carousel-control carousel-control-backward" for="A"></label>
+ <label class="carousel-control carousel-control-forward" for="C"></label>
+ </div>
+ <div class="carousel-controls">
+ <label class="carousel-control carousel-control-backward" for="B"></label>
+ <label class="carousel-control carousel-control-forward" for="D"></label>
+ </div>
+ <div class="carousel-controls">
+ <label class="carousel-control carousel-control-backward" for="C"></label>
+ <label class="carousel-control carousel-control-forward" for="A"></label>
+ </div>
+ <li class="carousel-slide ms">
+ <h3>Monero Promo</h3>
+ <video controls poster="/img/monero-community.png" onclick="this.paused ? this.play() : this.pause();" preload="none">
+ <source src="/media/Monero_Promo.m4v">
+ </video>
+ </li>
+ <li class="carousel-slide">
+ <h3>Monero: The Essentials</h3>
+ <video controls poster="/img/monero-cash-video-poster.png" onclick="this.paused ? this.play() : this.pause();" preload="none">
+ <source src="/media/Monero%20-%20The%20Essentials.m4v">
+ </video>
+ </li>
+ <li class="carousel-slide">
+ <h3>Stealth Addresses</h3>
+ <video controls poster="/img/stealth-address-poster.png" onclick="this.paused ? this.play() : this.pause();" preload="none">
+ <source src="/media/Monero%20-%20Stealth%20Addresses.m4v">
+ </video>
+ </li>
+ <li class="carousel-slide">
+ <h3>Ring Signatures</h3>
+ <video controls poster="/img/ring-signatures-poster.png" onclick="this.paused ? this.play() : this.pause();" preload="none">
+ <source src="/media/Monero%20-%20Ring%20Signatures.m4v">
+ </video>
+ </li>
+ <li class="carousel-slide">
+ <h3>RingCT</h3>
+ <video controls poster="/img/ringct-poster.png" onclick="this.paused ? this.play() : this.pause();" preload="none">
+ <source src="/media/Monero%20-%20RingCT.m4v">
+ </video>
+ </li>
+ </ul>
+ </div>
+ </div>
+ </div>
+ </section>
+
+ </div>
+ </section>
+</div>
\ No newline at end of file
diff --git a/_i18n/template/index.md b/_i18n/template/index.md
new file mode 100644
index 0000000000000000000000000000000000000000..9589e09aa29f15db5a3c884c7466b347007e5cc0
--- /dev/null
+++ b/_i18n/template/index.md
@@ -0,0 +1,191 @@
+{% include untranslated.html %}
+<div class="site-wrap">
+ <section class="container full col-xs-12">
+ <div class="info-block info-block-main">
+ <div class="row middle-xs">
+ <div class="col-lg-7 col-md-7 col-xs-12 main-video">
+ <div class="monero-video">
+ <!--iframe width="560" height="315" src="https://www.youtube.com/embed/TZi9xx6aiuY" frameborder="0" allowfullscreen></iframe-->
+ <video controls poster="/img/monero-community.png" onclick="this.paused ? this.play() : this.pause();" preload="none">
+ <source src="/media/Monero_Promo.m4v">
+ </video>
+ </div>
+
+ </div>
+ <div class="col-lg-5 col-md-5 col-xs-12">
+ <div class="main-info">
+ <h1 id="main-h1">Monero</h1>
+ <h2 id="main-h2">Private Digital Currency</h2>
+ <p id="main-text">Monero is cash for a connected world. It’s fast, private, and secure. With Monero, you are your own bank. You can spend safely, knowing that others cannot see your balances or track your activity.</p>
+ <p><a href="{{site.baseurl}}/get-started/using/" class="btn-link btn-auto btn-primary">Get Started</a></p>
+ </div>
+ </div>
+ </div>
+ </div>
+ </section>
+
+ <!-- FULL WIDTH BLOCK -->
+
+ <section class="container about-main full col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col"><h2>Why Monero is different</h2></div>
+ </div>
+ <div class="row middle-xs info-block-row private">
+ <div class="col-lg-6 col-md-6 col-sm-8 col-xs-12 why-text">
+ <h3>Monero is secure</h3>
+ <p>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. </p>
+ </div>
+ <div class="col-lg-6 col-md-6 col-sm-4 col-xs-12 last-sm first-xs center-xs">
+ <img src="/img/secure-monero.png" alt="Secure safe" class="main-icon">
+ </div>
+ </div>
+ <div class="row middle-xs info-block-row">
+ <div class="col-lg-6 col-md-6 col-sm-4 col-xs-12 center-xs">
+ <img src="/img/private-monero.png" alt="No surveillance" class="main-icon">
+ </div>
+ <div class="col-lg-6 col-md-6 col-sm-8 col-xs-12 why-text">
+ <h3>Monero is private</h3>
+ <p>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. </p>
+ </div>
+
+ </div>
+ <div class="row middle-xs info-block-row">
+ <div class="col-lg-6 col-md-6 col-sm-8 col-xs-12 why-text">
+ <h3>Monero is untraceable</h3>
+ <p>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.</p>
+ </div>
+ <div class="col-lg-6 col-md-6 col-sm-4 col-xs-12 last-sm first-xs center-xs">
+ <img src="/img/untraceable-monero.png" alt="Untraceable Monero paths" class="main-icon">
+ </div>
+ </div>
+ <div class="row middle-xs info-block-row">
+ <div class="col-lg-6 col-md-6 col-sm-4 col-xs-12 center-xs">
+ <img src="/img/fungible-monero.png" alt="Monero gold" class="main-icon">
+ </div>
+ <div class="col-lg-6 col-md-6 col-sm-8 col-xs-12 why-text">
+ <h3>Monero is fungible</h3>
+ <p> Monero is <a href="{{site.baseurl}}/resources/moneropedia/fungibility.html">fungible</a> because it is private by default. Units of Monero cannot be blacklisted by vendors or exchanges due to their association in previous transactions.</p>
+ </div>
+ </div>
+ </div>
+ </section>
+
+ <!-- END FULL WIDTH BLOCK -->
+
+
+
+ <!-- TWO THIRDS & ONE THIRD BLOCKS ROW -->
+
+ <section class="container">
+ <div class="row">
+ <!-- left two-thirds block-->
+ <div class="left two-thirds col-lg-8 col-md-8 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col"><h2>Downloads</h2></div>
+ </div>
+ <div class="row around-xs">
+ <div class="col">
+ <p><a href="{{site.baseurl}}/downloads#windows" class="btn-link btn-fixed"><span class="icon-windows"></span>Monero for Windows</a></p>
+ </div>
+ <div class="col">
+ <p><a href="{{site.baseurl}}/downloads#mac" class="btn-link btn-fixed"><span class="icon-apple"></span>Monero for Mac</a></p>
+ </div>
+ </div>
+ <div class="row around-xs">
+ <div class="col">
+ <p><a href="{{site.baseurl}}/downloads#linux" class="btn-link btn-fixed"><span class="icon-linux"></span>Monero for Linux</a></p>
+ </div>
+ <div class="col">
+ <p><a href="{{site.baseurl}}/downloads#source" class="btn-link btn-fixed"><span class="icon-blockchain"></span>Latest Blockchain</a></p>
+ </div>
+ </div>
+ <div class="row">
+ <div class="col-xs-12"><p class="main-downloads">Need it for a different operating system? <a href="{{site.baseurl}}/downloads/">View all available downloads here.</a></p>
+ </div>
+ </div>
+ </div>
+ </div>
+ <!-- end left two-thirds block-->
+
+ <!-- right one-third block-->
+ <div class="right one-third col-lg-4 col-md-4 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col"><h2>Latest News</h2></div>
+ </div>
+ <div class="info-block-row">
+ {% for post in site.posts limit:2 %}
+ <div class="row start-xs">
+ <div class="col">
+ <p><a href="{{site.baseurl}}/{{ post.url }}">{{ post.title }}</a></p>
+ </div>
+ </div>
+ {% endfor %}
+
+
+ <div class="row end-xs">
+ <div class="col">
+ <p><a href="{{site.baseurl}}/blog/">More news</a></p>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ <!-- end right one-third block-->
+ </div>
+ </section>
+
+ <!-- END TWO THIRDS & ONE THIRD BLOCKS ROW -->
+
+ <!-- 3 ONE-THIRD BLOCKS ROW -->
+
+ <section class="container">
+ <div class="row">
+ <!-- left one-third block-->
+ <div class="left one-third col-lg-4 col-md-4 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Moneropedia</h2>
+ <p class="main-resources">Would you like to look up the meanings of the terms and concepts used in Monero? Here you will find an alphabetical guide to terms and their meanings from both the Monero and Kovri projects.</p>
+ <p><a href="{{site.baseurl}}/resources/moneropedia/" class="btn-link btn-auto">Read Moneropedia</a></p>
+ </div>
+ </div>
+ </div>
+ </div>
+ <!-- end left one-third block-->
+
+ <!-- center one-third block-->
+ <div class="center one-third col-lg-4 col-md-4 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>User Guides</h2>
+ <p class="main-resources">Step-by-step guides to all things Monero are separated by category and cover everything from creating a wallet to supporting the network, and even how to edit this website.</p>
+ <p><a href="{{site.baseurl}}/resources/user-guides/" class="btn-link btn-auto">Read user guides</a></p>
+ </div>
+ </div>
+ </div>
+ </div>
+ <!-- end center one-third block-->
+
+ <!-- right one-third block-->
+ <div class="right one-third col-lg-4 col-md-4 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>FAQ</h2>
+ <p class="main-resources">We've heard a lot of questions over the years and have compiled, for your convenience, a thorough and varied FAQ. Don't worry, if your questions are not on here, you can always ask the community.</p>
+ <p><a href="{{site.baseurl}}/get-started/faq/" class="btn-link btn-auto">Read answers</a></p>
+ </div>
+ </div>
+ </div>
+ </div>
+ <!-- end right one-third block-->
+ </div>
+ </section>
+
+ <!-- END 3 ONE-THIRD BLOCKS ROW -->
+</div>
diff --git a/_i18n/template/press-kit.md b/_i18n/template/press-kit.md
new file mode 100644
index 0000000000000000000000000000000000000000..b7bf3e2f69b59b0917517ac789fade3960736421
--- /dev/null
+++ b/_i18n/template/press-kit.md
@@ -0,0 +1,70 @@
+{% include untranslated.html %}
+<div class="text-center container description">
+<p>Here you'll find the Monero symbol and logo below. You can choose any size that you want, or download the .ai file to mess with the logo yourself. <strong>Note that the white background options have a white background under the Monero symbol ONLY, not as a background to the whole image.</strong> Lastly, you can download everything on this page in one zip file by clicking <a href="/press-kit/monero-press-kit.zip">here</a>.</p>
+</div>
+<section class="container">
+ <div class="row">
+ <div class="left half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Monero Symbol</h2>
+ </div>
+ </div>
+ <div class="row center-xs">
+ <img src="/press-kit/symbols/monero-symbol-480.png" alt="Monero Symbol" class="symbol-logo">
+ </div>
+ <div class="row center-xs press">
+ <div class="col-md-6">
+ <p>No background (PNG)</p>
+ <a href="/press-kit/symbols/monero-symbol-480.png">Small</a>
+ <a href="/press-kit/symbols/monero-symbol-800.png">Medium</a>
+ <a href="/press-kit/symbols/monero-symbol-1280.png">Large</a>
+ </div>
+ <div class="col-md-6">
+ <p>White background (PNG)</p>
+ <a href="/press-kit/symbols/monero-symbol-on-white-480.png">Small</a>
+ <a href="/press-kit/symbols/monero-symbol-on-white-800.png">Medium</a>
+ <a href="/press-kit/symbols/monero-symbol-on-white-1280.png">Large</a>
+ </div>
+ </div>
+ <div class="row center-xs press">
+ <a href="/press-kit/symbols/monero-symbol.ai" class="adi">Symbol .ai file</a>
+ </div>
+ </div>
+ </div>
+ <div class="right half col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Monero Logo</h2>
+ </div>
+ </div>
+ <div class="row center-xs">
+ <div class="col-xs-12">
+ <img src="/press-kit/logos/monero-logo-480.png" alt="Monero Logo" class="monero-symbol-logo">
+ </div>
+ </div>
+ <div class="row center-xs press">
+ <div class="col-md-6">
+ <p>No background (PNG)</p>
+ <a href="/press-kit/logos/monero-logo-480.png">Small</a>
+ <a href="/press-kit/logos/monero-logo-800.png">Medium</a>
+ <a href="/press-kit/logos/monero-logo-1280.png">Large</a>
+ </div>
+ <div class="col-md-6">
+ <p>White background (PNG)</p>
+ <a href="/press-kit/logos/monero-logo-symbol-on-white-480.png">Small</a>
+ <a href="/press-kit/logos/monero-logo-symbol-on-white-800.png">Medium</a>
+ <a href="/press-kit/logos/monero-logo-symbol-on-white-1280.png">Large</a>
+ </div>
+ </div>
+ <div class="row center-xs press">
+ <div class="col-xs-12">
+ <a href="/press-kit/logos/monero-logo.ai" class="adi">Logo .ai file</a>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+</section>
\ No newline at end of file
diff --git a/_i18n/template/resources/about.md b/_i18n/template/resources/about.md
new file mode 100644
index 0000000000000000000000000000000000000000..ada9fe4c2e35ecdd227e96ea05e6a02d193ec3e8
--- /dev/null
+++ b/_i18n/template/resources/about.md
@@ -0,0 +1,57 @@
+{% include untranslated.html %}
+<div class="about-monero">
+ <section class="container">
+ <div class="row">
+ <!-- left two-thirds block-->
+ <div class="full col-xs-12">
+ <div class="info-block text-adapt">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>A Brief History</h2>
+ </div>
+ </div>
+<div markdown="1">
+
+Monero was launched in April 2014. It was a fair, pre-announced launch of the CryptoNote reference code. There was no premine or instamine, and no portion of the block reward goes to development. See the original Bitcointalk thread here. The founder, thankful_for_today, proposed some controversial changes that the community disagreed with. A fallout ensued, and the Monero Core Team forked the project with the community following this new Core Team. This Core Team has provided oversight since.
+
+Monero has made several large improvements since launch. The blockchain was migrated to a different database structure to provide greater efficiency and flexibility, minimum ring signature sizes were set so that all transactions were private by mandate, and RingCT was implemented to hide the transaction amounts. Nearly all improvements have provided improvements to security or privacy, or they have facilitated use. Monero continues to develop with goals of privacy and security first, ease of use and efficiency second.
+
+</div>
+ </div>
+ </div>
+ <!-- end right one-third block-->
+ </div>
+ <div class="row">
+ <!-- left two-thirds block-->
+ <div class="full col-xs-12">
+ <div class="info-block text-adapt">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Our Values</h2>
+ </div>
+ </div>
+
+<div markdown="1">
+
+Monero is more than just a technology. It’s also what the technology stands for. Some of the important guiding philosophies are listed below.
+
+### Security
+
+Users must be able to trust Monero with their transactions, without risk of error or attack. Monero gives the full block reward to the miners, who are the most critical members of the network who provide this security. Transactions are cryptographically secure using the latest and most resilient encryption tools available.
+
+### Privacy
+
+Monero takes privacy seriously. Monero needs to be able to protect users in a court of law and, in extreme cases, from the death penalty. This level of privacy must be completely accessible to all users, whether they are technologically competent or have no idea how Monero works. A user needs to confidently trust Monero in a way that this person does not feel pressured into changing their spending habits for risk of others finding out.
+
+### Decentralization
+
+Monero is committed to providing the maximum amount of decentralization. With Monero, you do not have to trust anyone else on the network, and it is not run by any large group. An accessible “Proof of Work†algorithm makes it easy to mine Monero on normal computers, which makes it more difficult for someone to purchase a large amount of mining power. Nodes connect to each other with I2P to lower the risks of revealing sensitive transaction information and censorship (tba). Development decisions are extremely clear and open to public discussion. Developer meeting logs are published online in their entirety and visible by all.
+
+</div>
+ </div>
+ </div>
+
+
+ <!-- end right one-third block-->
+ </div>
+ </section>
\ No newline at end of file
diff --git a/_i18n/template/resources/developer-guides.md b/_i18n/template/resources/developer-guides.md
new file mode 100644
index 0000000000000000000000000000000000000000..d219203a1722b8a2d7eac5ab37c6cfeafecc110a
--- /dev/null
+++ b/_i18n/template/resources/developer-guides.md
@@ -0,0 +1,20 @@
+{% include untranslated.html %}
+<div class="guides">
+
+<div class="center-xs container description">
+<p class="text-center">Please note: the guides below are currently out of date, but are considered a good starting point for most calls. </p>
+</div>
+
+<section class="container full">
+ <div class="info-block">
+ <h2>RPC Documetation</h2>
+<div markdown="1">
+
+[Daemon RPC Documentation](daemon-rpc.html)
+[Wallet RPC Documentation](wallet-rpc.html)
+
+More coming soon...
+</div>
+ </div>
+</section>
+</div>
\ No newline at end of file
diff --git a/_i18n/template/resources/developer-guides/daemon-rpc.md b/_i18n/template/resources/developer-guides/daemon-rpc.md
new file mode 100644
index 0000000000000000000000000000000000000000..8f341d0debb7ebf2442e946f529a9eb0309d2fed
--- /dev/null
+++ b/_i18n/template/resources/developer-guides/daemon-rpc.md
@@ -0,0 +1,832 @@
+{% include untranslated.html %}
+## Introduction
+
+This is a list of the monerod daemon RPC calls, their inputs and outputs, and examples of each.
+
+Many RPC calls use the daemon's JSON RPC interface while others use their own interfaces, as demonstrated below.
+
+Note: "atomic units" refer to the smallest fraction of 1 XMR according to the monerod implementation. **1 XMR = 1e12 atomic units.**
+
+### [JSON RPC Methods](#json-rpc-methods):
+
+* [getblockcount](#getblockcount)
+* [on_getblockhash](#on_getblockhash)
+* [getblocktemplate](#getblocktemplate)
+* [submitblock](#submitblock)
+* [getlastblockheader](#getlastblockheader)
+* [getblockheaderbyhash](#getblockheaderbyhash)
+* [getblockheaderbyheight](#getblockheaderbyheight)
+* [getblock](#getblock)
+* [get_connections](#get_connections)
+* [get_info](#get_info)
+* [hard_fork_info](#hard_fork_info)
+* [setbans](#setbans)
+* [getbans](#getbans)
+
+### [Other RPC Methods](#other-daemon-rpc-calls):
+
+* [/getheight](#getheight)
+* [/gettransactions](#gettransactions)
+* [/is_key_image_spent](#is_key_image_spent)
+* [/sendrawtransaction](#sendrawtransaction)
+* [/get_transaction_pool](#get_transaction_pool)
+* [/stop_daemon](#stop_daemon)
+
+
+---
+
+## JSON RPC Methods
+
+The majority of monerod RPC calls use the daemon's `json_rpc` interface to request various bits of information. These methods all follow a similar structure, for example:
+
+```
+IP=127.0.0.1
+PORT=18081
+METHOD='getblockheaderbyheight'
+PARAMS='{"height":912345}'
+curl \
+ -X POST http://$IP:$PORT/json_rpc \
+ -d '{"jsonrpc":"2.0","id":"0","method":"'$METHOD'","params":'$PARAMS'}' \
+ -H 'Content-Type: application/json'
+```
+
+Some methods include parameters, while others do not. Examples of each JSON RPC method follow.
+
+### **getblockcount**
+
+Look up how many blocks are in the longest chain known to the node.
+
+Inputs: *None*.
+
+Outputs:
+
+* *count* - unsigned int; Number of blocks in longest chain seen by the node.
+* *status* - string; General RPC error code. "OK" means everything looks good.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getblockcount"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "count": 993163,
+ "status": "OK"
+ }
+}
+```
+
+
+### **on_getblockhash**
+
+Look up a block's hash by its height.
+
+Inputs:
+
+* block height (int array of length 1)
+
+Outputs:
+
+* block hash (string)
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"on_getblockhash","params":[912345]}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": "e22cf75f39ae720e8b71b3d120a5ac03f0db50bba6379e2850975b4859190bc6"
+}
+```
+
+
+### **getblocktemplate**
+
+Inputs:
+
+* *wallet_address* - string; Address of wallet to receive coinbase transactions if block is successfully mined.
+* *reserve_size* - unsigned int; Reserve size.
+
+Outputs:
+
+* *blocktemplate_blob* - string; Blob on which to try to mine a new block.
+* *difficulty* - unsigned int; Difficulty of next block.
+* *height* - unsigned int; Height on which to mine.
+* *prev_hash* - string; Hash of the most recent block on which to mine the next block.
+* *reserved_offset* - unsigned int; Reserved offset.
+* *status* - string; General RPC error code. "OK" means everything looks good.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getblocktemplate","params":{"wallet_address":"44GBHzv6ZyQdJkjqZje6KLZ3xSyN1hBSFAnLP6EAqJtCRVzMzZmeXTC2AHKDS9aEDTRKmo6a6o9r9j86pYfhCWDkKjbtcns","reserve_size":60}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "blocktemplate_blob": "01029af88cb70568b84a11dc9406ace9e635918ca03b008f7728b9726b327c1b482a98d81ed83000000000018bd03c01ffcfcf3c0493d7cec7020278dfc296544f139394e5e045fcda1ba2cca5b69b39c9ddc90b7e0de859fdebdc80e8eda1ba01029c5d518ce3cc4de26364059eadc8220a3f52edabdaf025a9bff4eec8b6b50e3d8080dd9da417021e642d07a8c33fbe497054cfea9c760ab4068d31532ff0fbb543a7856a9b78ee80c0f9decfae01023ef3a7182cb0c260732e7828606052a0645d3686d7a03ce3da091dbb2b75e5955f01ad2af83bce0d823bf3dbbed01ab219250eb36098c62cbb6aa2976936848bae53023c00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001f12d7c87346d6b84e17680082d9b4a1d84e36dd01bd2c7f3b3893478a8d88fb3",
+ "difficulty": 982540729,
+ "height": 993231,
+ "prev_hash": "68b84a11dc9406ace9e635918ca03b008f7728b9726b327c1b482a98d81ed830",
+ "reserved_offset": 246,
+ "status": "OK"
+ }
+}
+```
+
+
+### **submitblock**
+
+Submit a mined block to the network.
+
+Inputs:
+
+* Block blob data - string
+
+Outputs:
+
+* *status* - string; Block submit status.
+
+
+### **getlastblockheader**
+
+Block header information for the most recent block is easily retrieved with this method. No inputs are needed.
+
+Inputs: *None*.
+
+Outputs:
+
+* *block_header* - A structure containing block header information.
+ * *depth* - unsigned int; The number of blocks succeeding this block on the blockchain. A larger number means an older block.
+ * *difficulty* - unsigned int; The strength of the Monero network based on mining power.
+ * *hash* - string; The hash of this block.
+ * *height* - unsigned int; The number of blocks preceding this block on the blockchain.
+ * *major_version* - unsigned int; The major version of the monero protocol at this block height.
+ * *minor_version* - unsigned int; The minor version of the monero protocol at this block height.
+ * *nonce* - unsigned int; a cryptographic random one-time number used in mining a Monero block.
+ * *orphan_status* - boolean; Usually `false`. If `true`, this block is not part of the longest chain.
+ * *prev_hash* - string; The hash of the block immediately preceding this block in the chain.
+ * *reward* - unsigned int; The amount of new atomic units generated in this block and rewarded to the miner. Note: 1 XMR = 1e12 atomic units.
+ * *timestamp* - unsigned int; The time the block was recorded into the blockchain.
+* *status* - string; General RPC error code. "OK" means everything looks good.
+
+In this example, the most recent block (990793 at the time) is returned:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getlastblockheader"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "block_header": {
+ "depth": 0,
+ "difficulty": 746963928,
+ "hash": "ac0f1e226268d45c99a16202fdcb730d8f7b36ea5e5b4a565b1ba1a8fc252eb0",
+ "height": 990793,
+ "major_version": 1,
+ "minor_version": 1,
+ "nonce": 1550,
+ "orphan_status": false,
+ "prev_hash": "386575e3b0b004ed8d458dbd31bff0fe37b280339937f971e06df33f8589b75c",
+ "reward": 6856609225169,
+ "timestamp": 1457589942
+ },
+ "status": "OK"
+ }
+}
+```
+
+
+### **getblockheaderbyhash**
+
+Block header information can be retrieved using either a block's hash or height. This method includes a block's hash as an input parameter to retrieve basic information about the block.
+
+Inputs:
+
+* *hash* - string; The block's sha256 hash.
+
+Outputs:
+
+* *block_header* - A structure containing block header information. See [getlastblockheader](#getlastblockheader).
+
+In this example, block 912345 is looked up by its hash:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getblockheaderbyhash","params":{"hash":"e22cf75f39ae720e8b71b3d120a5ac03f0db50bba6379e2850975b4859190bc6"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "block_header": {
+ "depth": 78376,
+ "difficulty": 815625611,
+ "hash": "e22cf75f39ae720e8b71b3d120a5ac03f0db50bba6379e2850975b4859190bc6",
+ "height": 912345,
+ "major_version": 1,
+ "minor_version": 2,
+ "nonce": 1646,
+ "orphan_status": false,
+ "prev_hash": "b61c58b2e0be53fad5ef9d9731a55e8a81d972b8d90ed07c04fd37ca6403ff78",
+ "reward": 7388968946286,
+ "timestamp": 1452793716
+ },
+ "status": "OK"
+ }
+}
+```
+
+
+### **getblockheaderbyheight**
+
+Similar to `getblockheaderbyhash` above, this method includes a block's height as an input parameter to retrieve basic information about the block.
+
+Inputs:
+
+* *height* - unsigned int; The block's height.
+
+Outputs:
+
+* *block_header* - A structure containing block header information. See [getlastblockheader](#getlastblockheader).
+
+In this example, block 912345 is looked up by its height (notice that the returned information is the save as in the previous example):
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getblockheaderbyheight","params":{"height":912345}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "block_header": {
+ "depth": 78376,
+ "difficulty": 815625611,
+ "hash": "e22cf75f39ae720e8b71b3d120a5ac03f0db50bba6379e2850975b4859190bc6",
+ "height": 912345,
+ "major_version": 1,
+ "minor_version": 2,
+ "nonce": 1646,
+ "orphan_status": false,
+ "prev_hash": "b61c58b2e0be53fad5ef9d9731a55e8a81d972b8d90ed07c04fd37ca6403ff78",
+ "reward": 7388968946286,
+ "timestamp": 1452793716
+ },
+ "status": "OK"
+ }
+}
+```
+
+
+### **getblock**
+
+Full block information can be retrieved by either block height or hash, like with the above block header calls. For full block information, both lookups use the same method, but with different input parameters.
+
+Inputs (pick one of the following):
+
+* *height* - unsigned int; The block's height.
+* *hash* - string; The block's hash.
+
+Outputs:
+
+* *blob* - string; Hexadecimal blob of block information.
+* *block_header* - A structure containing block header information. See [getlastblockheader](#getlastblockheader).
+* *json* - json string; JSON formatted block details:
+ * *major_version* - Same as in block header.
+ * *minor_version* - Same as in block header.
+ * *timestamp* - Same as in block header.
+ * *prev_id* - Same as `prev_hash` in block header.
+ * *nonce* - Same as in block header.
+ * *miner_tx* - Miner transaction information
+ * *version* - Transaction version number.
+ * *unlock_time* - The block height when the coinbase transaction becomes spendable.
+ * *vin* - List of transaction inputs:
+ * *gen* - Miner txs are coinbase txs, or "gen".
+ * *height* - This block height, a.k.a. when the coinbase is generated.
+ * *vout* - List of transaction outputs. Each output contains:
+ * *amount* - The amount of the output, in atomic units.
+ * *target* -
+ * *key* -
+ * *extra* - Usually called the "transaction ID" but can be used to include any random 32 byte/64 character hex string.
+ * *signatures* - Contain signatures of tx signers. Coinbased txs do not have signatures.
+ * *tx_hashes* - List of hashes of non-coinbase transactions in the block. If there are no other transactions, this will be an empty list.
+* *status* - string; General RPC error code. "OK" means everything looks good.
+
+**Look up by height:**
+
+In the following example, block 912345 is looked up by its height. Note that block 912345 does not have any non-coinbase transactions. (See the next example for a block with extra transactions):
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getblock","params":{"height":912345}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "blob": "...",
+ "block_header": {
+ "depth": 80694,
+ "difficulty": 815625611,
+ "hash": "e22cf75f39ae720e8b71b3d120a5ac03f0db50bba6379e2850975b4859190bc6",
+ "height": 912345,
+ "major_version": 1,
+ "minor_version": 2,
+ "nonce": 1646,
+ "orphan_status": false,
+ "prev_hash": "b61c58b2e0be53fad5ef9d9731a55e8a81d972b8d90ed07c04fd37ca6403ff78",
+ "reward": 7388968946286,
+ "timestamp": 1452793716
+ },
+ "json": "{\n \"major_version\": 1, \n \"minor_version\": 2, \n \"timestamp\": 1452793716, \n \"prev_id\": \"b61c58b2e0be53fad5ef9d9731a55e8a81d972b8d90ed07c04fd37ca6403ff78\", \n \"nonce\": 1646, \n \"miner_tx\": {\n \"version\": 1, \n \"unlock_time\": 912405, \n \"vin\": [ {\n \"gen\": {\n \"height\": 912345\n }\n }\n ], \n \"vout\": [ {\n \"amount\": 8968946286, \n \"target\": {\n \"key\": \"378b043c1724c92c69d923d266fe86477d3a5ddd21145062e148c64c57677008\"\n }\n }, {\n \"amount\": 80000000000, \n \"target\": {\n \"key\": \"73733cbd6e6218bda671596462a4b062f95cfe5e1dbb5b990dacb30e827d02f2\"\n }\n }, {\n \"amount\": 300000000000, \n \"target\": {\n \"key\": \"47a5dab669770da69a860acde21616a119818e1a489bb3c4b1b6b3c50547bc0c\"\n }\n }, {\n \"amount\": 7000000000000, \n \"target\": {\n \"key\": \"1f7e4762b8b755e3e3c72b8610cc87b9bc25d1f0a87c0c816ebb952e4f8aff3d\"\n }\n }\n ], \n \"extra\": [ 1, 253, 10, 119, 137, 87, 244, 243, 16, 58, 131, 138, 253, 164, 136, 195, 205, 173, 242, 105, 123, 61, 52, 173, 113, 35, 66, 130, 178, 250, 217, 16, 14, 2, 8, 0, 0, 0, 11, 223, 194, 193, 108\n ], \n \"signatures\": [ ]\n }, \n \"tx_hashes\": [ ]\n}",
+ "status": "OK"
+ }
+}
+```
+
+**Look up by hash:**
+
+In the following example, block 993056 is looked up by its hash. Note that block 993056 has 3 non-coinbase transactions:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getblock","params":{"hash":"510ee3c4e14330a7b96e883c323a60ebd1b5556ac1262d0bc03c24a3b785516f"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "blob": "...",
+ "block_header": {
+ "depth": 12,
+ "difficulty": 964985344,
+ "hash": "510ee3c4e14330a7b96e883c323a60ebd1b5556ac1262d0bc03c24a3b785516f",
+ "height": 993056,
+ "major_version": 1,
+ "minor_version": 2,
+ "nonce": 2036,
+ "orphan_status": false,
+ "prev_hash": "0ea4af6547c05c965afc8df6d31509ff3105dc7ae6b10172521d77e09711fd6d",
+ "reward": 6932043647005,
+ "timestamp": 1457720227
+ },
+ "json": "{\n \"major_version\": 1, \n \"minor_version\": 2, \n \"timestamp\": 1457720227, \n \"prev_id\": \"0ea4af6547c05c965afc8df6d31509ff3105dc7ae6b10172521d77e09711fd6d\", \n \"nonce\": 2036, \n \"miner_tx\": {\n \"version\": 1, \n \"unlock_time\": 993116, \n \"vin\": [ {\n \"gen\": {\n \"height\": 993056\n }\n }\n ], \n \"vout\": [ {\n \"amount\": 2043647005, \n \"target\": {\n \"key\": \"59e9d685b3484886bc7b47c133e6099ecdf212d5eaa16ce19cd58e8c3c1e590a\"\n }\n }, {\n \"amount\": 30000000000, \n \"target\": {\n \"key\": \"4c5e2f542d25513c46b9e3b7d40140a22d0ae5314bfcae492ad9f56fff8185f0\"\n }\n }, {\n \"amount\": 900000000000, \n \"target\": {\n \"key\": \"13dd8ffdac9e6a2f71e327dad65328198dc879a492d145eae72677c0703a3515\"\n }\n }, {\n \"amount\": 6000000000000, \n \"target\": {\n \"key\": \"62bda00341681dccbc066757862da593734395745bdfe1fdc89b5948c86a5d4c\"\n }\n }\n ], \n \"extra\": [ 1, 182, 145, 133, 28, 240, 87, 185, 195, 2, 163, 219, 202, 135, 158, 28, 186, 76, 196, 80, 97, 202, 85, 170, 166, 224, 60, 220, 103, 171, 158, 69, 80, 2, 8, 0, 0, 0, 12, 97, 127, 223, 22\n ], \n \"signatures\": [ ]\n }, \n \"tx_hashes\": [ \"79c6b9f00db027bde151705aafe85c495883aae2597d5cb8e1adb2e0f3ae1d07\", \"d715db73331abc3ec588ef07c7bb195786a4724b08dff431b51ffa32a4ce899b\", \"b197066426c0ed89f0b431fe171f7fd62bc95dd29943daa7cf3585cf1fdfc99d\"\n ]\n}",
+ "status": "OK",
+ "tx_hashes": ["79c6b9f00db027bde151705aafe85c495883aae2597d5cb8e1adb2e0f3ae1d07","d715db73331abc3ec588ef07c7bb195786a4724b08dff431b51ffa32a4ce899b","b197066426c0ed89f0b431fe171f7fd62bc95dd29943daa7cf3585cf1fdfc99d"]
+ }
+}
+```
+
+
+### **get_connections**
+
+Retrieve information about incoming and outgoing connections to your node.
+
+Inputs: *None*.
+
+Outputs:
+
+* *connections* - List of all connections and their info:
+ * *avg_download* - unsigned int; Average bytes of data downloaded by node.
+ * *avg_upload* - unsigned int; Average bytes of data uploaded by node.
+ * *current_download* - unsigned int; Current bytes downloaded by node.
+ * *current_upload* - unsigned int; Current bytes uploaded by node.
+ * *incoming* - boolean; Is the node getting information from your node?
+ * *ip* - string; The node's IP address.
+ * *live_time* - unsigned int
+ * *local_ip* - boolean
+ * *localhost* - boolean
+ * *peer_id* - string; The node's ID on the network.
+ * *port* - string; The port that the node is using to connect to the network.
+ * *recv_count* - unsigned int
+ * *recv_idle_time* - unsigned int
+ * *send_count* - unsigned int
+ * *send_idle_time* - unsigned int
+ * *state* - string
+
+Following is an example of `get_connections` and it's return:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_connections"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "connections": [{
+ "avg_download": 0,
+ "avg_upload": 0,
+ "current_download": 0,
+ "current_upload": 0,
+ "incoming": false,
+ "ip": "76.173.170.133",
+ "live_time": 1865,
+ "local_ip": false,
+ "localhost": false,
+ "peer_id": "3bfe29d6b1aa7c4c",
+ "port": "18080",
+ "recv_count": 116396,
+ "recv_idle_time": 23,
+ "send_count": 176893,
+ "send_idle_time": 1457726610,
+ "state": "state_normal"
+ },{
+ ...
+ }],
+ "status": "OK"
+ }
+}
+```
+
+
+### **get_info**
+
+Retrieve general information about the state of your node and the network.
+
+Inputs: *None*.
+
+Outputs:
+
+* *alt_blocks_count* - unsigned int; Number of alternative blocks to main chain.
+* *difficulty* - unsigned int; Network difficulty (analogous to the strength of the network)
+* *grey_peerlist_size* - unsigned int; Grey Peerlist Size
+* *height* - unsigned int; Current length of longest chain known to daemon.
+* *incoming_connections_count* - unsigned int; Number of peers connected to and pulling from your node.
+* *outgoing_connections_count* - unsigned int; Number of peers that you are connected to and getting information from.
+* *status* - string; General RPC error code. "OK" means everything looks good.
+* *target* - unsigned int; Current target for next proof of work.
+* *target_height* - unsigned int; The height of the next block in the chain.
+* *testnet* - boolean; States if the node is on the testnet (true) or mainnet (false).
+* *top_block_hash* - string; Hash of the highest block in the chain.
+* *tx_count* - unsigned int; Total number of non-coinbase transaction in the chain.
+* *tx_pool_size* - unsigned int; Number of transactions that have been broadcast but not included in a block.
+* *white_peerlist_size* - unsigned int; White Peerlist Size
+
+Following is an example `get_info` call and its return:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_info"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "alt_blocks_count": 5,
+ "difficulty": 972165250,
+ "grey_peerlist_size": 2280,
+ "height": 993145,
+ "incoming_connections_count": 0,
+ "outgoing_connections_count": 8,
+ "status": "OK",
+ "target": 60,
+ "target_height": 993137,
+ "testnet": false,
+ "top_block_hash": "",
+ "tx_count": 564287,
+ "tx_pool_size": 45,
+ "white_peerlist_size": 529
+ }
+}
+```
+
+
+### **hard_fork_info**
+
+Look up information regarding hard fork voting and readiness.
+
+Inputs: *None*.
+
+Outputs:
+
+* *earliest_height* - unsigned int; Block height at which hard fork would be enabled if voted in.
+* *enabled* - boolean; Tells if hard fork is enforced.
+* *state* - unsigned int; Current hard fork state: 0 (There is likely a hard fork), 1 (An update is needed to fork properly), or 2 (Everything looks good).
+* *status* - string; General RPC error code. "OK" means everything looks good.
+* *threshold* - unsigned int; Minimum percent of votes to trigger hard fork. Default is 80.
+* *version* - unsigned int; The major block version for the fork.
+* *votes* - unsigned int; Number of votes towards hard fork.
+* *voting* - unsigned int; Hard fork voting status.
+* *window* - unsigned int; Number of blocks over which current votes are cast. Default is 10080 blocks.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"hard_fork_info"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "earliest_height": 1009827,
+ "enabled": false,
+ "state": 2,
+ "status": "OK",
+ "threshold": 0,
+ "version": 1,
+ "votes": 7277,
+ "voting": 2,
+ "window": 10080
+ }
+}
+```
+
+
+### **setbans**
+
+Ban another node by IP.
+
+Inputs:
+
+* *bans* - A list of nodes to ban:
+ * *ip* - unsigned int; IP address to ban, in Int format.
+ * *ban* - boolean; Set `true` to ban.
+ * *seconds* - unsigned int; Number of seconds to ban node.
+
+Outputs:
+
+* *status* - string; General RPC error code. "OK" means everything looks good.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"setbans","params":{"bans":[{"ip":838969536,"ban":true,"seconds":30}]}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "status": "OK"
+ }
+}
+```
+
+
+### **getbans**
+
+Inputs: *None*.
+
+Outputs:
+
+* *bans* - List of banned nodes:
+ * *ip* - unsigned int; Banned IP address, in Int format.
+ * *seconds* - unsigned int; Local Unix time that IP is banned until.
+* *status* - string; General RPC error code. "OK" means everything looks good.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getbans"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "bans": [{
+ "ip": 838969536,
+ "seconds": 1457748792
+ }],
+ "status": "OK"
+ }
+}
+```
+
+
+---
+
+## Other Daemon RPC Calls
+
+Not all daemon RPC calls use the JSON_RPC interface. This section gives examples of these calls.
+
+The data structure for these calls is different than the JSON RPC calls. Whereas the JSON RPC methods were called using the `/json_rpc` extension and specifying a method, these methods are called at their own extensions. For example:
+
+ IP=127.0.0.1
+ PORT=18081
+ METHOD='gettransactions'
+ PARAMS='{"txs_hashes":["d6e48158472848e6687173a91ae6eebfa3e1d778e65252ee99d7515d63090408"]}'
+ curl \
+ -X POST http://$IP:$PORT/$METHOD \
+ -d $PARAMS \
+ -H 'Content-Type: application/json'
+
+Note: It is recommended to use JSON RPC where such alternatives exist, rather than the following methods. For example, the recommended way to get a node's height is via the JSON RPC methods [get_info](#getinfo) or [getlastblockheader](#getlastblockheader), rather than [getheight](#getheight) below.
+
+
+### **/getheight**
+
+Get the node's current height.
+
+Inputs: *None*.
+
+Outputs:
+
+* *height* - unsigned int; Current length of longest chain known to daemon.
+
+```
+$ curl -X POST http://127.0.0.1:18081/getheight -H 'Content-Type: application/json'
+
+{
+ "height": 993488,
+ "status": "OK"
+}
+```
+
+
+### **/gettransactions**
+
+Look up one or more transactions by hash.
+
+Inputs:
+
+* *txs_hashes* - string list; List of transaction hashes to look up.
+* *decode_as_json* - boolean; Optional. If set `true`, the returned transaction information will be decoded rather than binary.
+
+Outputs:
+
+* *status* - General RPC error code. "OK" means everything looks good.
+* *txs_as_hex* - string; Full transaction information as a hex string.
+* *txs_as_json* - json string; (Optional - returned if set in inputs.) List of transaction info:
+ * *version* - Transaction version
+ * *unlock_time* - If not 0, this tells when a transaction output is spendable.
+ * *vin* - List of inputs into transaction:
+ * *key* - The public key of the previous output spent in this transaction.
+ * *amount* - The amount of the input, in atomic units.
+ * *key_offsets* - A list of integer offets to the input.
+ * *k_image* - The key image for the given input
+ * *vout* - List of outputs from transaction:
+ * *amount* - Amount of transaction output, in atomic units.
+ * *target* - Output destination information:
+ * *key* - The stealth public key of the receiver. Whoever owns the private key associated with this key controls this transaction output.
+ * *extra* - Usually called the "payment ID" but can be used to include any random 32 bytes.
+ * *signatures* - List of ignatures used in ring signature to hide the true origin of the transaction.
+Example 1: Return transaction information in binary format.
+
+```
+$ curl -X POST http://127.0.0.1:18081/gettransactions -d '{"txs_hashes":["d6e48158472848e6687173a91ae6eebfa3e1d778e65252ee99d7515d63090408"]}' -H 'Content-Type: application/json'
+
+{
+ "status": "OK",
+ "txs_as_hex": ["..."]
+}
+```
+
+
+Example 2: Decode returned transaction information in JSON format. Note: the "vout" list has been truncated in the displayed return for space considerations.
+
+```
+$ curl -X POST http://127.0.0.1:18081/gettransactions -d '{"txs_hashes":["d6e48158472848e6687173a91ae6eebfa3e1d778e65252ee99d7515d63090408"],"decode_as_json":true}' -H 'Content-Type: application/json'
+
+{
+ "status": "OK",
+ "txs_as_hex": ["..."],
+ "txs_as_json": ["{\n \"version\": 1, \n \"unlock_time\": 0, \n \"vin\": [ {\n \"key\": {\n \"amount\": 70000000, \n \"key_offsets\": [ 35952\n ], \n \"k_image\": \"d16908468dff9438a9814fe96bdaa575f06fe8da85772b72e54926428712293d\"\n }\n }, {\n \"key\": {\n \"amount\": 400000000000000, \n \"key_offsets\": [ 6830\n ], \n \"k_image\": \"c7a7024b763df1181ae6fe821b70669735e38a68162ac02362e33acbe829b605\"\n }\n }\n ], \n \"vout\": [ {\n \"amount\": 50000, \n \"target\": {\n \"key\": \"f6be43f7be4f06adcb1d06f4a07c637c7359e009cf3e57bb32b8c9ea636509c3\"\n }\n }, {\n \"amount\": 200000, \n \"target\": {\n \"key\": \"b0a7a8e32f2b5302552bcd8d85112c62838b1f56cccd844eb9b63e0a732d0353\"\n }\n }, ... \n ], \n \"extra\": [ 1, 225, 240, 98, 34, 169, 73, 47, 237, 117, 192, 30, 192, 60, 155, 47, 4, 115, 20, 21, 11, 13, 252, 219, 129, 13, 174, 37, 36, 78, 191, 141, 109\n ], \n \"signatures\": [ \"e6a3be8003d481d2855c8127f56871de3d28a4fb52385b999eb986c831c5cc08361c126b0db24a21b6c4299b438ee2be201d44d57a371230b9cd04395ab8c400\", \"8309851abaf2cf2a7091e0cdb9c83704fa7d68838a7a8ef8c178bb55a1e93a038dd18bb4a7549dc056b7a70e037cabd80911a03f427e36f712756d4c00f38f0b\"]\n}"]
+}
+```
+
+
+### **/is_key_image_spent**
+
+Check if outputs have been spent using the key image associated with the output.
+
+Inputs:
+
+* *key_images* - string list; List of key image hex strings to check.
+
+Outputs:
+
+* *spent_status* - unsigned int list; List of statuses for each image checked. Statuses are follows: 0 = unspent, 1 = spent in blockchain, 2 = spent in transaction pool
+* *status* - string; General RPC error code. "OK" means everything looks good.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/is_key_image_spent -d '{"key_images":["8d1bd8181bf7d857bdb281e0153d84cd55a3fcaa57c3e570f4a49f935850b5e3","7319134bfc50668251f5b899c66b005805ee255c136f0e1cecbb0f3a912e09d4"]}' -H 'Content-Type: application/json'
+
+{
+ "spent_status": [1,2],
+ "status": "OK"
+}
+```
+
+
+### **/sendrawtransaction**
+
+Broadcast a raw transaction to the network.
+
+Inputs:
+
+* *tx_as_hex* - string; Full transaction information as hexidecimal string.
+
+Outputs:
+
+* *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.):
+
+
+```
+$ curl -X POST http://127.0.0.1:18081/sendrawtransaction -d '{"tx_as_hex":"de6a3..."}' -H 'Content-Type: application/json'
+```
+
+
+### **/get_transaction_pool**
+
+Show information about valid transactions seen by the node but not yet mined into a block, as well as spent key image information in the node's memory.
+
+Inputs: *None*.
+
+Outputs:
+
+* *spent_key_images* - List of spent output key images:
+ * *id_hash* - string; Key image ID hash.
+ * *txs_hashes* - string list; Key image transaction hashes.
+* *status* - string; General RPC error code. "OK" means everything looks good.
+* *transactions* - List of transactions in the mempool that have not been included in a block:
+ * *blob_size* - unsigned int; The size of the full transaction blob.
+ * *fee* - unsigned int; The amount of the mining fee included in the transaction, in atomic units.
+ * *id_hash* - string; The transaction ID hash.
+ * *kept_by_block* - boolean; We do not accept transactions that timed out before, unless set `true`.
+ * *last_failed_height* - unsigned int; If the transaction has previously timed out, this tells at what height that occured.
+ * *last_failed_id_hash* - string; Like the previous, this tells the previous transaction ID hash.
+ * *max_used_block_height* - unsigned int; Tells the height of the most recent block with an output used in this transaction.
+ * *max_used_block_hash* - string; Tells the hash of the most recent block with an output used in this transaction.
+ * *receive_time* - unsigned int; The Unix time that the transaction was first seen on the network by the node.
+ * *tx_json* - json string; JSON structure of all information in the transaction:
+ * *version* - Transaction version
+ * *unlock_time* - If not 0, this tells when a transaction output is spendable.
+ * *vin* - List of inputs into transaction:
+ * *key* - The public key of the previous output spent in this transaction.
+ * *amount* - The amount of the input, in atomic units.
+ * *key_offsets* - A list of integer offets to the input.
+ * *k_image* - The key image for the given input
+ * *vout* - List of outputs from transaction:
+ * *amount* - Amount of transaction output, in atomic units.
+ * *target* - Output destination information:
+ * *key* - The stealth public key of the receiver. Whoever owns the private key associated with this key controls this transaction output.
+ * *extra* - Usually called the "transaction ID" but can be used to include any random 32 bytes.
+ * *signatures* - List of ignatures used in ring signature to hide the true origin of the transaction.
+
+Example (Note: Some lists in the returned information have been truncated for display reasons):
+
+```
+$ curl -X POST http://127.0.0.1:18081/get_transaction_pool -H 'Content-Type: application/json'
+
+{
+ "spent_key_images": [{
+ "id_hash": "1edb9ecc39602040282d326070ad22cb473c952c0d6280c9c4c3b853fb34f3bc",
+ "txs_hashes": ["409911b2be02e3f0e930b326c67ab9e74675885ce23d71bb3bd28b62bc3e7803"]
+ },{
+ "id_hash": "4adb4bb63b3397027340ca4e6c45f4ce2147dfb3a4e0fafdec18834ae594a05e",
+ "txs_hashes": ["946f1f4c52e3426a41959c93b60078f314813bc4bdebcf69b8ee11d593b2bd14"]
+ },
+ ...],
+ "status": "OK",
+ "transactions": [{
+ "blob_size": 25761,
+ "fee": 290000000000,
+ "id_hash": "11d4cff23e610fac6a2b89187ad61d429a5e226652693dcac5d83d506eb92b96",
+ "kept_by_block": false,
+ "last_failed_height": 0,
+ "last_failed_id_hash": "0000000000000000000000000000000000000000000000000000000000000000",
+ "max_used_block_height": 954508,
+ "max_used_block_id_hash": "03f96b374778bc059e47b96e2beec2e6d4d9e0ad39afeabdbcd77e1bd5a62f81",
+ "receive_time": 1457676127,
+ "tx_json": "{\n \"version\": 1, \n \"unlock_time\": 0, \n \"vin\": [ {\n \"key\": {\n \"amount\": 70000000000, \n \"key_offsets\": [ 63408, 18978, 78357, 16560\n ], \n \"k_image\": \"7319134bfc50668251f5b899c66b005805ee255c136f0e1cecbb0f3a912e09d4\"\n }\n }, ... ], \n \"vout\": [ {\n \"amount\": 80000000000, \n \"target\": {\n \"key\": \"094e6a1b187385533665f89db741149f42d95fdc50bdd2a2384bcd1dc5209c55\"\n }\n }, ... ], \n \"extra\": [ 2, 33, 0, 15, 56, 190, 21, 169, 77, 13, 182, 209, 51, 35, 54, 96, 89, 237, 96, 23, 24, 107, 240, 79, 40, 86, 64, 68, 45, 166, 119, 192, 17, 225, 23, 1, 31, 159, 145, 15, 173, 255, 165, 192, 55, 84, 127, 154, 163, 25, 85, 204, 212, 127, 147, 133, 118, 218, 166, 52, 78, 188, 131, 235, 9, 159, 105, 158\n ], \n \"signatures\": [ \"966e5a67fbdbf72d7dc0364b705121a58e0ced7e2ab45747b6b154c05a1afe04fac4aac7f64faa2dc6dd4d51b8277f11e2f2ec7729fac225088befe3b8399c0b71a4cb55b9d0e20f93d305c78cebceff1bcfcfaf225428dfcfaaec630c88720ab65bf5d3399dd1ac82ea0ecf308b3f80d9780af7742fb157692cd60515a7e2086878f082117fa80fff3d257de7d3a2e9cc8b3472ef4a5e545d90e1159523a60f38d16cece783579627124776813334bdb2a2df4171ef1fa12bf415da338ce5085c01e7a715638ef5505aebec06a0625aaa72d13839838f7d4f981673c8f05f08408e8b372f900af7227c49cfb1e1febab6c07dd42b7c26f921cf010832841205\", ... ]\n}"
+ },
+ ...]
+}
+```
+
+
+### **/stop_daemon**
+
+Send a command to the daemon to safely disconnect and shut down.
+
+Inputs: *None*.
+
+Outputs:
+
+* *status* - string; General RPC error code. "OK" means everything looks good.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/stop_daemon -H 'Content-Type: application/json'
+
+{
+ "status": "OK"
+}
+```
\ No newline at end of file
diff --git a/_i18n/template/resources/developer-guides/wallet-rpc.md b/_i18n/template/resources/developer-guides/wallet-rpc.md
new file mode 100644
index 0000000000000000000000000000000000000000..59776a56a1b6a81da0200b8a80534bca9249fe61
--- /dev/null
+++ b/_i18n/template/resources/developer-guides/wallet-rpc.md
@@ -0,0 +1,1216 @@
+{% include untranslated.html %}
+## Introduction
+
+This is a list of the monero-wallet-rpc calls, their inputs and outputs, and examples of each. The program monero-wallet-rpc replaced the rpc interface that was in simplewallet and then monero-wallet-cli.
+
+All monero-wallet-rpc methods use the same JSON RPC interface. For example:
+
+```
+IP=127.0.0.1
+PORT=18082
+METHOD="make_integrated_address"
+PARAMS="{\"payment_id\":\"1234567890123456789012345678900012345678901234567890123456789000\"}"
+curl \
+ -X POST http://$IP:$PORT/json_rpc \
+ -d '{"jsonrpc":"2.0","id":"0","method":"'$METHOD'","params":'"$PARAMS"'}' \
+ -H 'Content-Type: application/json'
+```
+
+If the monero-wallet-rpc was executed with the `--rpc-login` argument as `username:password`, then follow this example:
+
+```
+IP=127.0.0.1
+PORT=18082
+METHOD="make_integrated_address"
+PARAMS="{\"payment_id\":\"1234567890123456789012345678900012345678901234567890123456789000\"}"
+curl \
+ -u username:password --digest \
+ -X POST http://$IP:$PORT/json_rpc \
+ -d '{"jsonrpc":"2.0","id":"0","method":"'$METHOD'","params":'"$PARAMS"'}' \
+ -H 'Content-Type: application/json'
+```
+
+Note: "atomic units" refer to the smallest fraction of 1 XMR according to the monerod implementation. **1 XMR = 1e12 atomic units.**
+
+### Index of JSON RPC Methods:
+
+* [getbalance](#getbalance)
+* [getaddress](#getaddress)
+* [getheight](#getheight)
+* [transfer](#transfer)
+* [transfer_split](#transfer_split)
+* [sweep_dust](#sweep_dust)
+* [sweep_all](#sweep_all)
+* [store](#store)
+* [get_payments](#get_payments)
+* [get_bulk_payments](#get_bulk_payments)
+* [get_transfers](#get_transfers)
+* [get_transfer_by_txid](#get_transfer_by_txid)
+* [incoming_transfers](#incoming_transfers)
+* [query_key](#query_key)
+* [make_integrated_address](#make_integrated_address)
+* [split_integrated_address](#split_integrated_address)
+* [stop_wallet](#stop_wallet)
+* [make_uri](#make_uri)
+* [parse_uri](#parse_uri)
+* [rescan_blockchain](#rescan_blockchain)
+* [set_tx_notes](#set_tx_notes)
+* [get_tx_notes](#get_tx_notes)
+* [sign](#sign)
+* [verify](#verify)
+* [export_key_images](#export_key_images)
+* [import_key_images](#import_key_images)
+* [get_address_book](#get_address_book)
+* [add_address_book](#add_address_book)
+* [delete_address_book](#delete_address_book)
+* [rescan_spent](#rescan_spent)
+* [start_mining](#start_mining)
+* [stop_mining](#stop_mining)
+* [get_languages](#get_languages)
+* [create_wallet](#create_wallet)
+* [open_wallet](#open_wallet)
+
+---
+
+## JSON RPC Methods:
+
+### **getbalance**
+
+Return the wallet's balance.
+
+Inputs: *None*.
+
+Outputs:
+
+* *balance* - unsigned int; The total balance of the current monero-wallet-rpc in session.
+* *unlocked_balance* - unsigned int; Unlocked funds are those funds that are sufficiently deep enough in the Monero blockchain to be considered safe to spend.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getbalance"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "balance": 140000000000,
+ "unlocked_balance": 50000000000
+ }
+}
+```
+
+
+### **getaddress**
+
+Return the wallet's address.
+
+Inputs: *None*.
+
+Outputs:
+
+* *address* - string; The 95-character hex address string of the monero-wallet-rpc in session.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getaddress"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "address": "427ZuEhNJQRXoyJAeEoBaNW56ScQaLXyyQWgxeRL9KgAUhVzkvfiELZV7fCPBuuB2CGuJiWFQjhnhhwiH1FsHYGQGaDsaBA"
+ }
+}
+```
+
+
+### **getheight**
+
+Returns the wallet's current block height.
+
+Inputs: *None*.
+
+Outputs:
+
+* *height* - unsigned int; The current monero-wallet-rpc's blockchain height. If the wallet has been offline for a long time, it may need to catch up with the daemon.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getheight"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "height": 994310
+ }
+}
+```
+
+
+### **transfer**
+
+Send monero to a number of recipients.
+
+Inputs:
+
+* *destinations* - array of destinations to receive XMR:
+ * *amount* - unsigned int; Amount to send to each destination, in atomic units.
+ * *address* - string; Destination public address.
+* *fee* - unsigned int; Ignored, will be automatically calculated.
+* *mixin* - unsigned int; Number of outpouts from the blockchain to mix with (0 means no mixing).
+* *unlock_time* - unsigned int; Number of blocks before the monero can be spent (0 to not add a lock).
+* *payment_id* - string; (Optional) Random 32-byte/64-character hex string to identify a transaction.
+* *get_tx_key* - boolean; (Optional) Return the transaction key after sending.
+* *priority* - unsigned int; Set a priority for the transaction. Accepted Values are: 0-3 for: default, unimportant, normal, elevated, priority.
+* *do_not_relay* - boolean; (Optional) If true, the newly created transaction will not be relayed to the monero network. (Defaults to false)
+* *get_tx_hex* - boolean; Return the transaction as hex string after sending
+
+
+Outputs:
+
+* *fee* - Integer value of the fee charged for the txn.
+* *tx_hash* - String for the publically searchable transaction hash
+* *tx_key* - String for the transaction key if get_tx_key is true, otherwise, blank string.
+* *tx_blob* - Transaction as hex string if get_tx_hex is true
+
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"transfer","params":{"destinations":[{"amount":100000000,"address":"9wNgSYy2F9qPZu7KBjvsFgZLTKE2TZgEpNFbGka9gA5zPmAXS35QzzYaLKJRkYTnzgArGNX7TvSqZC87tBLwtaC5RQgJ8rm"},{"amount":200000000,"address":"9vH5D7Fv47mbpCpdcthcjU34rqiiAYRCh1tYywmhqnEk9iwCE9yppgNCXAyVHG5qJt2kExa42TuhzQfJbmbpeGLkVbg8xit"}],"mixin":4,"get_tx_key": true}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "fee": 48958481211,
+ "tx_hash": "985180f468637bc6d2f72ee054e1e34b8d5097988bb29a2e0cb763e4464db23c",
+ "tx_key": "8d62e5637f1fcc9a8904057d6bed6c697618507b193e956f77c31ce662b2ee07"
+ }
+}
+```
+
+
+### **transfer_split**
+
+Same as transfer, but can split into more than one tx if necessary.
+
+Inputs:
+
+* *destinations* - array of destinations to receive XMR:
+ * *amount* - unsigned int; Amount to send to each destination, in atomic units.
+ * *address* - string; Destination public address.
+* *fee* - unsigned int; Ignored, will be automatically calculated.
+* *mixin* - unsigned int; Number of outpouts from the blockchain to mix with (0 means no mixing).
+* *unlock_time* - unsigned int; Number of blocks before the monero can be spent (0 to not add a lock).
+* *payment_id* - string; (Optional) Random 32-byte/64-character hex string to identify a transaction.
+* *get_tx_keys* - boolean; (Optional) Return the transaction keys after sending. -- Ignored
+* *priority* - unsigned int; Set a priority for the transactions. Accepted Values are: 0-3 for: default, unimportant, normal, elevated, priority.
+* *do_not_relay* - boolean; (Optional) If true, the newly created transaction will not be relayed to the monero network. (Defaults to false)
+* *get_tx_hex* - boolean; Return the transactions as hex string after sending
+* *new_algorithm* - boolean; True to use the new transaction construction algorithm, defaults to false.
+
+Outputs:
+
+* *fee_list* - array of: integer. The amount of fees paid for every transaction.
+* *tx_hash_list* - array of: string. The tx hashes of every transaction.
+* *tx_blob_list* - array of: string. The tx as hex string for every transaction.
+* *amount_list* - array of: integer. The amount transferred for every transaction..
+* *tx_key_list* - array of: string. The transaction keys for every transaction.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"transfer_split","params":{"destinations":[{"amount":100000000,"address":"9wNgSYy2F9qPZu7KBjvsFgZLTKE2TZgEpNFbGka9gA5zPmAXS35QzzYaLKJRkYTnzgArGNX7TvSqZC87tBwtaC5RQgJ8rm"},{"amount":200000000,"address":"9vH5D7Fv47mbpCpdcthcjU34rqiiAYRCh1tYywmhqnEk9iwCE9yppgNCXAyVHG5qJt2kExa42TuhzQfJbmbpeGLkVbg8xit"},{"amount":200000000,"address":"9vC5Q25cR1d3WzKX6dpTaLJaqZyDrtTnfadTmVuB1Wue2tyFGxUhiE4RGa74pEDJv7gSySzcd1Ao6G1nzSaqp78vLfP6MPj"},{"amount":200000000,"address":"A2MSrn49ziBPJBh8ZNEhhbfyLMou6mao4C1F5TLGUatmUnCxZArDYkcbAnVkVEopWVeak2rKDrmc8JpoS7n5dvfN9YDPBTG"},{"amount":200000000,"address":"9tEDyVQ8zgRQbDYiykTdpw5kZ6qWQWcKfExEj9eQshjpGb3sdr3UyWE2AHWzUGzJjaH9HN1DdGBdyQQ4AqGMc7rr5xYwZWW"}],"mixin":4,"get_tx_key": true, "new_algorithm": true}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "fee_list": [97916962422],
+ "tx_hash_list": ["c5c389846e701c27aaf1f7ab8b9dc457b471fcea5bc9710e8020d51275afbc54"]
+ }
+}
+```
+
+
+### **sweep_dust**
+
+Send all dust outputs back to the wallet's, to make them easier to spend (and mix).
+
+Inputs: *None*.
+
+Outputs:
+
+* *tx_hash_list* - list of: string
+
+Example (In this example, `sweep_dust` returns an error due to insufficient funds to sweep):
+
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"sweep_dust"}' -H 'Content-Type: application/json'
+
+{
+ "error": {
+ "code": -4,
+ "message": "not enough money"
+ },
+ "id": "0",
+ "jsonrpc": "2.0"
+}
+```
+
+### **sweep_all**
+
+Send all unlocked balance to an address.
+
+Inputs:
+
+* *address* - string; Destination public address.
+* *priority* - unsigned int; (Optional)
+* *mixin* - unsigned int; Number of outpouts from the blockchain to mix with (0 means no mixing).
+* *unlock_time* - unsigned int; Number of blocks before the monero can be spent (0 to not add a lock).
+* *payment_id* - string; (Optional) Random 32-byte/64-character hex string to identify a transaction.
+* *get_tx_keys* - boolean; (Optional) Return the transaction keys after sending.
+* *below_amount* - unsigned int; (Optional)
+* *do_not_relay* - boolean; (Optional)
+* *get_tx_hex* - boolean; (Optional) return the transactions as hex encoded string.
+
+Outputs:
+
+* *tx_hash_list* - array of string;
+* *tx_key_list* - array of string;
+* *tx_blob_list* - array of string;
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"sweep_all","params":{"address":"9sS8eRU2b5ZbN2FPSrpkiab1bjbHE5XtL6Ti6We3Fhw5aQPudRfVVypjgzKDNkxtvTQSPs122NKggb2mqcqkKSeMNVu59S","mixin":2,"unlock_time":0,"get_tx_keys":true}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "tx_hash_list": ["53a3648797d5524dd037d4105e067fa61468faecab41927fc43adbb26c202d22"],
+ "tx_key_list": ["e83b3b78235e36cd7e4d9695efd81a3b3e64c7d1f1ebd61892f0a7add6a50301"]
+ }
+}
+```
+
+### **store**
+
+Save the blockchain.
+
+Inputs: *None*.
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"store"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **get_payments**
+
+Get a list of incoming payments using a given payment id.
+
+Inputs:
+
+* *payment_id* - string
+
+Outputs:
+
+* *payments* - list of:
+ * *payment_id* - string
+ * *tx_hash* - string
+ * *amount* - unsigned int
+ * *block_height* - unsigned int
+ * *unlock_time* - unsigned int
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_payments","params":{"payment_id":"4279257e0a20608e25dba8744949c9e1caff4fcdafc7d5362ecf14225f3d9030"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "payments": [{
+ "amount": 10350000000000,
+ "block_height": 994327,
+ "payment_id": "4279257e0a20608e25dba8744949c9e1caff4fcdafc7d5362ecf14225f3d9030",
+ "tx_hash": "c391089f5b1b02067acc15294e3629a463412af1f1ed0f354113dd4467e4f6c1",
+ "unlock_time": 0
+ }]
+ }
+}
+```
+
+
+### **get_bulk_payments**
+
+Get a list of incoming payments using a given payment id, or a list of payments ids, from a given height. This method is the preferred method over `get_payments` because it has the same functionality but is more extendable. Either is fine for looking up transactions by a single payment ID.
+
+Inputs:
+
+* *payment_ids* - array of: string
+ * *min_block_height* - unsigned int; The block height at which to start looking for payments.
+
+Outputs:
+
+* *payments* - list of:
+ * *payment_id* - string
+ * *tx_hash* - string
+ * *amount* - unsigned int
+ * *block_height* - unsigned int
+ * *unlock_time* - unsigned int
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_bulk_payments","params":{"payment_ids":["4279257e0a20608e25dba8744949c9e1caff4fcdafc7d5362ecf14225f3d9030"],"min_block_height":990000}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "payments": [{
+ "amount": 10350000000000,
+ "block_height": 994327,
+ "payment_id": "4279257e0a20608e25dba8744949c9e1caff4fcdafc7d5362ecf14225f3d9030",
+ "tx_hash": "c391089f5b1b02067acc15294e3629a463412af1f1ed0f354113dd4467e4f6c1",
+ "unlock_time": 0
+ }]
+ }
+}
+```
+
+
+### **get_transfers**
+
+Returns a list of transfers.
+
+Inputs:
+
+* *in* - boolean;
+* *out* - boolean;
+* *pending* - boolean;
+* *failed* - boolean;
+* *pool* - boolean;
+* *filter_by_height* - boolean;
+* *min_height* - unsigned int;
+* *max_height* - unsigned int;
+
+Outputs:
+
+* *in* array of transfers:
+ * *txid* - string;
+ * *payment_id* - string;
+ * *height* - unsigned int;
+ * *timestamp* - unsigned int;
+ * *amount* - unsigned int;
+ * *fee* - unsigned int;
+ * *note* - string;
+ * *destinations* - std::list<transfer_destination>;
+ * *type* - string;
+* *out* array of transfers
+* *pending* array of transfers
+* *failed* array of transfers
+* *pool* array of transfers
+
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_transfers","params":{"pool":true}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "pool": [{
+ "amount": 500000000000,
+ "fee": 0,
+ "height": 0,
+ "note": "",
+ "payment_id": "758d9b225fda7b7f",
+ "timestamp": 1488312467,
+ "txid": "da7301d5423efa09fabacb720002e978d114ff2db6a1546f8b820644a1b96208",
+ "type": "pool"
+ }]
+ }
+}
+```
+
+### **get_transfer_by_txid**
+
+Show information about a transfer to/from this address.
+
+Inputs:
+
+* *txid* - string
+
+Outputs:
+
+* *transfer* - JSON object containing parment information:
+ * *amount* - unsigned int
+ * *fee* - unsigned int
+ * *height* - unsigned int
+ * *note* - string
+ * *payment_id* - string
+ * *timestamp* - unsigned int
+ * *txid* - string
+ * *type* - string
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_transfer_by_txid","params":{"txid":"f2d33ba969a09941c6671e6dfe7e9456e5f686eca72c1a94a3e63ac6d7f27baf"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "transfer": {
+ "amount": 10000000000000,
+ "fee": 0,
+ "height": 1316388,
+ "note": "",
+ "payment_id": "0000000000000000",
+ "timestamp": 1495539310,
+ "txid": "f2d33ba969a09941c6671e6dfe7e9456e5f686eca72c1a94a3e63ac6d7f27baf",
+ "type": "in"
+ }
+ }
+}
+```
+
+
+### **incoming_transfers**
+
+Return a list of incoming transfers to the wallet.
+
+Inputs:
+
+* *transfer_type* - string; "all": all the transfers, "available": only transfers which are not yet spent, OR "unavailable": only transfers which are already spent.
+
+Outputs:
+
+* *transfers* - list of:
+ * *amount* - unsigned int
+ * *spent* - boolean
+ * *global_index* - unsigned int; Mostly internal use, can be ignored by most users.
+ * *tx_hash* - string; Several incoming transfers may share the same hash if they were in the same transaction.
+ * *tx_size* - unsigned int
+
+Example (Return "all" transaction types):
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"incoming_transfers","params":{"transfer_type":"all"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "transfers": [{
+ "amount": 10000000000000,
+ "global_index": 711506,
+ "spent": false,
+ "tx_hash": "<c391089f5b1b02067acc15294e3629a463412af1f1ed0f354113dd4467e4f6c1>",
+ "tx_size": 5870
+ },{
+ "amount": 300000000000,
+ "global_index": 794232,
+ "spent": false,
+ "tx_hash": "<c391089f5b1b02067acc15294e3629a463412af1f1ed0f354113dd4467e4f6c1>",
+ "tx_size": 5870
+ },{
+ "amount": 50000000000,
+ "global_index": 213659,
+ "spent": false,
+ "tx_hash": "<c391089f5b1b02067acc15294e3629a463412af1f1ed0f354113dd4467e4f6c1>",
+ "tx_size": 5870
+ }]
+ }
+}
+```
+
+Example (Return "available" transactions):
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"incoming_transfers","params":{"transfer_type":"available"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "transfers": [{
+ "amount": 10000000000000,
+ "global_index": 711506,
+ "spent": false,
+ "tx_hash": "<c391089f5b1b02067acc15294e3629a463412af1f1ed0f354113dd4467e4f6c1>",
+ "tx_size": 5870
+ },{
+ "amount": 300000000000,
+ "global_index": 794232,
+ "spent": false,
+ "tx_hash": "<c391089f5b1b02067acc15294e3629a463412af1f1ed0f354113dd4467e4f6c1>",
+ "tx_size": 5870
+ },{
+ "amount": 50000000000,
+ "global_index": 213659,
+ "spent": false,
+ "tx_hash": "<c391089f5b1b02067acc15294e3629a463412af1f1ed0f354113dd4467e4f6c1>",
+ "tx_size": 5870
+ }]
+ }
+}
+```
+
+Example (Return "unavailable" transaction. Note that this particular example returns 0 unavailable transactions):
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"incoming_transfers","params":{"transfer_type":"unavailable"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **query_key**
+
+Return the spend or view private key.
+
+Inputs:
+
+* *key_type* - string; Which key to retrieve: "mnemonic" - the mnemonic seed (older wallets do not have one) OR "view_key" - the view key
+
+Outputs:
+
+* *key* - string; The view key will be hex encoded, while the mnemonic will be a string of words.
+
+Example (Query view key):
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"query_key","params":{"key_type":"view_key"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "key": "7e341d..."
+ }
+}
+```
+
+Example (Query mnemonic key):
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"query_key","params":{"key_type":"mnemonic"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "key": "adapt adapt nostril ..."
+ }
+}
+```
+
+
+### **make_integrated_address**
+
+Make an integrated address from the wallet address and a payment id.
+
+Inputs:
+
+* *payment_id* - string; hex encoded; can be empty, in which case a random payment id is generated
+
+Outputs:
+
+* *integrated_address* - string
+
+Example (Payment ID is empty, use a random ID):
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"make_integrated_address","params":{"payment_id":""}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "integrated_address": "4BpEv3WrufwXoyJAeEoBaNW56ScQaLXyyQWgxeRL9KgAUhVzkvfiELZV7fCPBuuB2CGuJiWFQjhnhhwiH1FsHYGQQ8H2RRJveAtUeiFs6J"
+ }
+}
+```
+
+
+### **split_integrated_address**
+
+Retrieve the standard address and payment id corresponding to an integrated address.
+
+Inputs:
+
+* *integrated_address* - string
+
+Outputs:
+
+* *standard_address* - string
+* *payment* - string; hex encoded
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"split_integrated_address","params":{"integrated_address": "4BpEv3WrufwXoyJAeEoBaNW56ScQaLXyyQWgxeRL9KgAUhVzkvfiELZV7fCPBuuB2CGuJiWFQjhnhhwiH1FsHYGQQ8H2RRJveAtUeiFs6J"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "payment_id": "<420fa29b2d9a49f5>",
+ "standard_address": "427ZuEhNJQRXoyJAeEoBaNW56ScQaLXyyQWgxeRL9KgAUhVzkvfiELZV7fCPBuuB2CGuJiWFQjhnhhwiH1FsHYGQGaDsaBA"
+ }
+}
+```
+
+
+### **stop_wallet**
+
+Stops the wallet, storing the current state.
+
+Inputs: *None*.
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"stop_wallet"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **make_uri**
+
+Create a payment URI using the official URI spec.
+
+Inputs:
+
+* *address* - wallet address string
+* *amount* (optional) - the integer amount to receive, in **atomic** units
+* *payment_id* (optional) - 16 or 64 character hexadecimal payment id string
+* *recipient_name* (optional) - string name of the payment recipient
+* *tx_description* (optional) - string describing the reason for the tx
+
+Outputs:
+
+* *uri* - a string containing all the payment input information as a properly formatted payment URI
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"make_uri","params":{"address":"44AFFq5kSiGBoZ4NMDwYtN18obc8AemS33DBLWs3H7otXft3XjrpDtQGv7SqSsaBYBb98uNbr2VBBEt7f2wfn3RVGQBEP3A","amount":10,"payment_id":"0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef","tx_description":"Testing out the make_uri function.","recipient_name":"Monero Project donation address"}}' -H 'Content-Type: application/json'
+
+{
+ "id": 0,
+ "jsonrpc": "2.0",
+ "result": {
+ "uri": "monero:44AFFq5kSiGBoZ4NMDwYtN18obc8AemS33DBLWs3H7otXft3XjrpDtQGv7SqSsaBYBb98uNbr2VBBEt7f2wfn3RVGQBEP3A?tx_payment_id=0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef&tx_amount=0.000000000010&recipient_name=Monero%20Project%20donation%20address&tx_description=Testing%20out%20the%20make_uri%20function."
+ }
+}
+```
+
+
+### **parse_uri**
+
+Parse a payment URI to get payment information.
+
+Inputs:
+
+* *uri* - a string containing all the payment input information as a properly formatted payment URI
+
+Outputs:
+
+* *uri* - JSON object containing payment information:
+ * *address* - wallet address string
+ * *amount* - the decimal amount to receive, in **coin** units (0 if not provided)
+ * *payment_id* - 16 or 64 character hexadecimal payment id string (empty if not provided)
+ * *recipient_name* - string name of the payment recipient (empty if not provided)
+ * *tx_description* - string describing the reason for the tx (empty if not provided)
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"parse_uri","params":{"uri":"monero:44AFFq5kSiGBoZ4NMDwYtN18obc8AemS33DBLWs3H7otXft3XjrpDtQGv7SqSsaBYBb98uNbr2VBBEt7f2wfn3RVGQBEP3A?tx_payment_id=0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef&tx_amount=0.000000000010&recipient_name=Monero%20Project%20donation%20address&tx_description=Testing%20out%20the%20make_uri%20function."}}' -H 'Content-Type: application/json'
+
+{
+ "id": 0,
+ "jsonrpc": "2.0",
+ "result": {
+ "uri": {
+ "address": "44AFFq5kSiGBoZ4NMDwYtN18obc8AemS33DBLWs3H7otXft3XjrpDtQGv7SqSsaBYBb98uNbr2VBBEt7f2wfn3RVGQBEP3A",
+ "amount": 10,
+ "payment_id": "0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef",
+ "recipient_name": "Monero Project donation address",
+ "tx_description": "Testing out the make_uri function."
+ }
+ }
+}
+```
+
+
+### **rescan_blockchain**
+
+Rescan blockchain from scratch.
+
+Inputs: *None*.
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"rescan_blockchain" -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **set_tx_notes**
+
+Set arbitrary string notes for transactions.
+
+Inputs:
+
+* *txids* - array of string; transaction ids
+* *notes* - array of string; notes for the transactions
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"set_tx_notes","params":{"txids":["6a1a100c079c236e2cbf36f7760e8ef1a9e8357c434aa790a8c78de653ec4cf2"],"notes":["This is an example"]}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **get_tx_notes**
+
+Get string notes for transactions.
+
+Inputs:
+
+* *txids* - array of string; transaction ids
+
+Outputs:
+
+* *notes* - array of string; notes for the transactions
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_tx_notes","params":{"txids":["6a1a100c079c236e2cbf36f7760e8ef1a9e8357c434aa790a8c78de653ec4cf2"]}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "notes": ["This is an example"]
+ }
+}
+```
+
+
+### **sign**
+
+Sign a string.
+
+Inputs:
+
+* *data* - string;
+
+Outputs:
+
+* *signature* - string;
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"sign","params":{"data":"This is sample data to be signed"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "signature": "SigV1Xp61ZkGguxSCHpkYEVw9eaWfRfSoAf36PCsSCApx4DUrKWHEqM9CdNwjeuhJii6LHDVDFxvTPijFsj3L8NDQp1TV"
+ }
+}
+```
+
+
+### **verify**
+
+Verify a signature on a string.
+
+Inputs:
+
+* *data* - string;
+* *address* - string;
+* *signature* - string;
+
+Outputs:
+
+* *good* - boolean;
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"verify","params":{"data":"This is sample data to be signed","address":"9sS8eRU2b5ZbN2FPSrpkiab1bjbHE5XtL6Ti6We3Fhw5aQPudRfVVypjgzKDNkxtvTQZSPs122NKggb2mqcqkKSeMNVu59S","signature":"SigV1Xp61ZkGguxSCHpkYEVw9eaWfRfSoAf36PCsSCApx4DUrKWHEqM9CdNwjeuhJii6LHDVDFxvTPijFsj3L8NDQp1TV"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "good": true
+ }
+}
+```
+
+
+### **export_key_images**
+
+Export a signed set of key images.
+
+Inputs: *None*.
+
+Outputs:
+
+* *signed_key_images* - array of signed key images:
+ * *key_image* - string;
+ * *signature* - string;
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"export_key_images"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "signed_key_images": [{
+ "key_image": "62b83df78baad99e23b5ad3f667bc6f8d388a13d9e84c7bb6c223a556dfd34af",
+ "signature": "b87b7e989aa85aa3a2a7cd8adcb3a848d3512ff718b168e15217ff3e5da29c0183c0328b97cc052fcb5ee3548aa5e41e530ba9d854199ea19d7ddaf6a54a4c0a"
+ }]
+ }
+}
+```
+
+
+### **import_key_images**
+
+Import signed key images list and verify their spent status.
+
+Inputs:
+
+* *signed_key_images* - array of signed key images:
+ * *key_image* - string;
+ * *signature* - string;
+
+Outputs:
+
+* *height* - unsigned int;
+* *spent* - unsigned int;
+* *unspent* - unsigned int;
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"import_key_images", "params":{"signed_key_images":[{"key_image":"63b83df78cafd99e23b5ad3f667bc6f8d38813d9e84c7bb6c223a556dfd34af","signature":"b87b7e989aa86aa2a7a7cd8adcb3a848d3512ff718b168e15217ff3e5da29c0183c0328b97cc052fcb5ee3548aa5e41e530ba9d854199ea19d7ddaf6a54a4c0a"},{"key_image":"44ec12fbc56c533a30b09de8ae26febd515528c4957dfe875430377a7e212b4e","signature":"91105f15be0b25bc2a94bd78a7e261608974d6d888080b9f1815655b98af190340325ea1a0840a5951dacf913d4de1b2bd33ea59c1cb7bce1b6648afa7133d03"}]}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "height": 986050,
+ "spent": 10000100000000,
+ "unspent": 4979852760000
+ }
+}
+```
+
+
+### **get_address_book**
+
+Retrieves entries from the address book.
+
+Inputs:
+
+* *entries* - array of unsigned int; indices of the requested address book entries
+
+Outputs:
+
+* *entries* - array of entries:
+ * *address* - string;
+ * *description* - string;
+ * *index* - unsigned int;
+ * *payment_id* - string;
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_address_book","params":{"entries":[1,2]}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "entries": [{
+ "address": "A135xq3GVMdU5qtAm4hN7zjPgz8bRaiSUQmtuDdjZ6CgXayvQruJy3WPe95qj873JhK4YdTQjoR39Leg6esznQk8PckhjRN",
+ "description": "",
+ "index": 1,
+ "payment_id": "0000000000000000000000000000000000000000000000000000000000000000"
+ },{
+ "address": "A135xq3GVMdU5qtAm4hN7zjPgz8bRaiSUQmtuDdjZ6CgXayvQruJy3WPe95qj873JhK4YdTQjoR39Leg6esznQk8PckhjRN",
+ "description": "",
+ "index": 2,
+ "payment_id": "0000000000000000000000000000000000000000000000000000000000000000"
+ }]
+ }
+}
+```
+
+
+### **add_address_book**
+
+Add an entry to the address book.
+
+Inputs:
+
+* *address* - string;
+* *payment_id* - (optional) string, defaults to "0000000000000000000000000000000000000000000000000000000000000000";
+* *description* - (optional) string, defaults to "";
+
+Outputs:
+
+* *index* - unsigned int; The index of the address book entry.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"add_address_book","params":{"address":"44AFFq5kSiGBoZ4NMDwYtN18obc8AemS33DBLWs3H7otXft3XjrpDtQGv7SqSsBYBb98uNbr2VBBEt7f2wfn3RVGQBEP3A","description":"Donation address for the Monero project"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "index": 2
+ }
+}
+```
+
+
+### **delete_address_book**
+
+Delete an entry from the address book.
+
+Inputs:
+
+* *index* - unsigned int; The index of the address book entry.
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"delete_address_book","params":{"index":0}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **rescan_spent**
+
+Rescan the blockchain for spent outputs.
+
+Inputs: *None*.
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"rescan_spent"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **start_mining**
+
+Start mining in the Monero daemon.
+
+Inputs:
+
+* *threads_count* - unsigned int; Number of threads created for mining
+* *do_background_mining* - boolean;
+* *ignore_battery* - boolean;
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"start_mining","params":{"threads_count":1,"do_background_mining":true,"ignore_battery":true}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **stop_mining**
+
+Stop mining in the Monero daemon.
+
+Inputs: *None*.
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"stop_mining"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **get_languages**
+
+Get a list of available languages for your wallet's seed.
+
+Inputs: *None*.
+
+Outputs:
+
+* *languages* - array of string; List of available languages
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_languages"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "languages": ["Deutsch","English","Español","Français","Italiano","Nederlands","Português","руÑÑкий Ñзык","日本語","简体ä¸æ–‡ (ä¸å›½)","Esperanto"]
+ }
+}
+```
+
+
+### **create_wallet**
+
+Create a new wallet. You need to have set the argument "--wallet-dir" when launching monero-wallet-rpc to make this work.
+
+Inputs:
+
+* *filename* - string;
+* *password* - string;
+* *language* - string; Language for your wallets' seed.
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"create_wallet","params":{"filename":"mytestwallet","password":"mytestpassword","language":"English"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **open_wallet**
+
+Open a wallet. You need to have set the argument "--wallet-dir" when launching monero-wallet-rpc to make this work.
+
+Inputs:
+
+* *filename* - string;
+* *password* - string;
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"open_wallet","params":{"filename":"mytestwallet","password":"mytestpassword"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
diff --git a/_i18n/template/resources/moneropedia/00-base-00 b/_i18n/template/resources/moneropedia/00-base-00
new file mode 100644
index 0000000000000000000000000000000000000000..ccfa17812230473e626c898f7f40e50c1938a8de
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/00-base-00
@@ -0,0 +1,10 @@
+---
+layout: moneropedia
+entry: ""
+terms: ["", ""]
+summary: ""
+---
+
+### The Basics
+
+{{ page.summary | capitalize }}.
\ No newline at end of file
diff --git a/_i18n/template/resources/moneropedia/account.md b/_i18n/template/resources/moneropedia/account.md
new file mode 100644
index 0000000000000000000000000000000000000000..8014c8ee5015268c05066097bcc1a3f3324220c7
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/account.md
@@ -0,0 +1,82 @@
+---
+layout: moneropedia
+entry: "Account"
+terms: ["account", "accounts", "wallet", "wallets"]
+summary: "similar in function to a bank account, contains all of your sent and received transactions"
+---
+
+### The Basics
+
+Those familiar with Monero's predecessors will be more familiar with the term *wallet* to describe this. In Monero we call this an account, and it is a private account owned and operated by a Monero user.
+
+Your account contains all of the Monero @transactions you have sent and received. Your account balance is a sum of all the Monero you've received, less the Monero you've sent. When using Monero you may notice that your account has two balances, a locked and an unlocked balance. The unlocked balance contains funds that can be spent immediately, and the locked balance contains funds that you can't spend right now. You may receive a transaction that has an @unlock-time set, or you may have sent some Monero and are waiting for the @change to come back to your wallet, both situations that could lead to those funds being locked for a time.
+
+A key difference between traditional electronic currency and Monero is that your account resides only under your control, normally on your computer, and cannot be accessed by anyone else if you [practice good security](#practicing-good-security).
+
+### Multiple Accounts
+
+There are no costs attached to creating a Monero account, and there are no fees charged except for individual @transaction fees that go to @miners.
+
+This means that individuals can easily create a Monero account for themselves as well as a joint account to share with their partner, and individual accounts for their children. Similarly, a business could create separate accounts for each division or group. Since Monero's @transaction fees are quite low, moving funds between accounts is not an expensive exercise.
+
+### Cryptographic Keys
+
+Monero relies heavily on a cryptography principle known as *public/private key cryptography* or *asymmetric cryptography*, which is thoroughly detailed in [this Wikipedia article](https://en.wikipedia.org/wiki/Public-key_cryptography).
+
+Your account is based on two keys, a @spend-key and a @view-key. The @spend-key is special in that it is the single key required to spend your Monero funds, whereas the @view-key allows you to reveal your @transactions to a third party, for example for auditing or accounting purposes. These keys in your account also play an important role in Monero's @transaction-privacy.
+
+The private keys for both of these must be protected by you in order to retain your account privacy. On the other hand, the public keys are obviously public (they are part of your Monero account address). For normal public/private key cryptography someone could send you a private message by encrypting it with either of your public keys, and you would then be the only one able to decrypt it with your private keys.
+
+### Backing Up Your Account
+
+When you manage your own Monero Account with the private @spend-key, you are solely responsible for the security of your funds. Thankfully, Monero makes it very easy to backup your account. When creating a Monero account for the first time you will be given a unique @mnemonic-seed for your account that consists of 13 or 25 words in the language of your choosing. **This seed is the only thing you need to backup for your account**, and so it is imperative that it is written down and stored securely. Never store this seed in a form or location that would allow someone else to see it!
+
+```
+List of available languages for your wallet's seed:
+0 : Deutsch
+1 : English
+2 : Español
+3 : Français
+4 : Italiano
+5 : Nederlands
+6 : Português
+7 : руÑÑкий Ñзык
+8 : 日本語
+9 : 简体ä¸æ–‡ (ä¸å›½)
+10 : Esperanto
+Enter the number corresponding to the language of your choice: 1
+Generated new wallet: 4B15ZjveuttEaTmfZjLVioPVw7bfSmRLpSgB33CJbuC6BoGtZrug9TDAmhZEWD6XoFDGz55bgzisT9Dnv61sbsA6Sa47TYu
+view key: 4130fa26463d9451781771a8baa5d0b8085c47c4500cefe4746bab48f1d15903
+**********************************************************************
+Your wallet has been generated.
+To start synchronizing with the daemon, use "refresh" command.
+Use "help" command to see the list of available commands.
+Always use "exit" command when closing monero-wallet-cli to save your
+current session's state. Otherwise, you might need to synchronize
+your wallet again (your wallet keys are NOT at risk in any case).
+
+PLEASE NOTE: the following 25 words can be used to recover access to your wallet. Please write them down and store them somewhere safe and secure. Please do not store them in your email or on file storage services outside of your immediate control.
+
+aunt knuckle italics moisture hawk thorn iris abort
+chlorine smog uphill glass aptitude nowhere sewage plywood
+dual relic fierce divers anvil nodes bubble cabin abort
+**********************************************************************
+Starting refresh...
+Refresh done, blocks received: 21939
+Balance: 0.000000000000, unlocked balance: 0.000000000000
+Background refresh thread started
+[wallet 4B15Zj]: â–ˆ
+
+```
+
+As the example above indicates, it is incredibly important to store these words in safe locations. If you are concerned about the risk of critical loss at your home, for instance, you may want to store a second copy of your seed with your attorney or in a safety deposit box. It is also recommended that it is stored in a way that does not make it obvious that it is your seed, so writing it into a letter or as part of other notes is advisable.
+
+### Practicing Good Security
+
+Over and above backing up your @mnemonic-seed so that you have access to your account in the event of critical data loss, it is also important to practice good security. Use a secure password when creating a local Monero account (not used on [MyMonero](https://mymonero.com) or other web-based account systems).
+
+Don't ever give your Monero account password to anyone, as this can be used to access the Monero on your computer without knowing your @mnemonic-seed. Similarly, make sure you have running and up-to-date antivirus, especially on Windows computers. Finally, be careful when clicking links in emails or on unknown and untrusted websites, as malware installed on your computer can sit and wait for you to access your Monero account before taking the funds from it.
+
+### Leaving Your Account to Next of Kin
+
+Providing access to your Monero account to your next of kin is just as easy as it is to backup your Monero account. Simply leave your @mnemonic-seed to them in your will, or store it somewhere safe where it will be given to them upon the execution of your will. A key advantage to this is that your next of kin won't have to wait for months for a third party to release the funds to them.
diff --git a/_i18n/template/resources/moneropedia/address-book.md b/_i18n/template/resources/moneropedia/address-book.md
new file mode 100644
index 0000000000000000000000000000000000000000..43b159c94ef29d9f8deb12af5b1294c5e2268b28
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/address-book.md
@@ -0,0 +1,35 @@
+---
+layout: moneropedia
+entry: "Address Book"
+tags: ["kovri"]
+terms: ["Address-Book"]
+summary: "Allows you to visit I2P websites/services that have the .i2p domain"
+---
+
+### The Basics
+
+In order to browse @I2P sites or services with @Kovri, you'll need an address book. An address book will allow you to translate @I2P websites/services that use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain) into an address that @I2P network will understand.
+
+Without an address book, you would be stuck using a @base32-address every time you visit an @I2P website/service - and that's not fun!
+
+### In-depth information
+
+Since [DNS](https://en.wikipedia.org/wiki/DNS) does not exist on the @I2P network, @Kovri also does **not** use DNS or any sort of @canonically-unique-host resolution. Instead, Kovri pairs a @locally-unique-host to a @base64-address @destination in a @subscription. Once your address book is filled with a @subscription, you can resolve your favorite `.i2p` domain site into a usable @I2P destination.
+
+### Creating an Address Book
+
+By default, your installation will come with a default public @subscription called `hosts.txt` in your @data-directory. When @Kovri starts, it loads this subscription and fetches any other subscriptions you've specified. Once loaded, your address book will be appropriately filled. For details on how to manage subscriptions, see @subscription.
+
+### Updating the Address Book
+
+Currently, there are several ways to update your address book:
+
+1. Use a @jump-service to insert I2P addresses into your address book
+2. Use a @jump-service to copy/paste an address into your private @subscription
+3. Manually add or subtract from a private @subscription
+
+**Note: Kovri is in heavy development. In the future there *will* be easier ways to update the address book**
+
+### Address Book / Naming specification
+
+For specification details and more, visit the [Address Book and Naming Specification](https://geti2p.net/en/docs/naming)
diff --git a/_i18n/template/resources/moneropedia/address.md b/_i18n/template/resources/moneropedia/address.md
new file mode 100644
index 0000000000000000000000000000000000000000..ed33f15a69c0969f7f85287f85caadf6e8e6c14d
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/address.md
@@ -0,0 +1,22 @@
+---
+layout: moneropedia
+entry: "Address"
+terms: ["address", "addresses"]
+summary: "either an alias, such as donate.getmonero.org, or a set of 95 characters starting with a 4"
+---
+
+### The Basics
+
+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 <span class="long-term">44AFFq5kSiGBoZ4NMDwYtN18obc8AemS33DBLWs3H7otXft3XjrpDtQGv7SqSsaBYBb98uNbr2VBBEt7f2wfn3RVGQBEP3A</span>.
+
+Because those addresses are long and complex you will often encounter an @OpenAlias address instead. For example, Monero donations can be sent to <span class="long-term">donate@getmonero.org</span> or <span class="long-term">donate.getmonero.org</span>.
+
+If you would like to get an @OpenAlias address of your own then there is some information on the [OpenAlias page](/knowledge-base/openalias).
+
+### Integrated address
+
+An integrated address is an address combined with an encrypted 64-bit @payment-ID. A raw integrated address is 106 characters long.
+
+### In-depth Information
+
+The address is actually the concatenation, in Base58 format, of the *public* @spend-key and the *public* @view-key, prefixed with the network byte (the number 18 for Monero) and suffixed with the first four bytes of the Keccac-256 hash of the whole string (used as a checksum).
diff --git a/_i18n/template/resources/moneropedia/airgap.md b/_i18n/template/resources/moneropedia/airgap.md
new file mode 100644
index 0000000000000000000000000000000000000000..f3107cf267768067e02d7bfab15ddadaadcceaf9
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/airgap.md
@@ -0,0 +1,12 @@
+---
+layout: moneropedia
+entry: "Airgap"
+terms: ["airgap"]
+summary: "An airgap is a security measure to physically separate a computer or device from all other networks, such as the Internet."
+---
+
+### The Basics
+
+"An air gap, air wall or air gapping is a network security measure employed on one or more computers to ensure that a secure computer network is physically isolated from unsecured networks, such as the public Internet or an unsecured local area network.[2] The name arises from the technique of creating a network that is physically separated (with a conceptual air gap) from all other networks. The air gap may not be completely literal, as networks employing the use of dedicated cryptographic devices that can tunnel packets over untrusted networks while avoiding packet rate or size variation can be considered air gapped, as there is no ability for computers on opposite sides of the gap to communicate."
+
+Taken from https://en.wikipedia.org/wiki/Air_gap_(networking)
diff --git a/_i18n/template/resources/moneropedia/base32-address.md b/_i18n/template/resources/moneropedia/base32-address.md
new file mode 100644
index 0000000000000000000000000000000000000000..ef38e41458c635cad73a7328d69f849b73d41c28
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/base32-address.md
@@ -0,0 +1,27 @@
+---
+layout: moneropedia
+entry: "Base32 address"
+tags: ["kovri"]
+terms: ["Base32-address", "Base32-addresses"]
+summary: "Base32 encoded hash of a Base64 address"
+---
+
+### The Basics
+
+A Base32 address is a shortened, encoded version of an @I2P address. The Base32 address is the first part in a `.b32.i2p` hostname.
+
+Example:
+
+`i35yftyyb22xhcvghmev46t5knefur5v66qzekkajatwfwhyklvq.b32.i2p`
+
+where
+
+`i35yftyyb22xhcvghmev46t5knefur5v66qzekkajatwfwhyklvq` is the Base32 address.
+
+### In-depth Information
+
+Ultimately, a Base32 address is a 52 character [Base32 encoded representation](https://en.wikipedia.org/wiki/Base32) of the full SHA-256 hash of an @I2P @base64-address.
+
+### Notes
+
+**Note: `.b32` is not a sub-domain of `.i2p`**
diff --git a/_i18n/template/resources/moneropedia/base64-address.md b/_i18n/template/resources/moneropedia/base64-address.md
new file mode 100644
index 0000000000000000000000000000000000000000..edd345932dd6ae7c5358a4d642b097c00e129d7e
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/base64-address.md
@@ -0,0 +1,22 @@
+---
+layout: moneropedia
+entry: "Base64 address"
+tags: ["kovri"]
+terms: ["Base64-address", "Base64-addresses"]
+summary: "Base64 encoded I2P destination"
+---
+
+### The Basics
+
+A @base64-address is a 516-character [Base64 encoded](https://en.wikipedia.org/wiki/Base64) @I2P @destination. @base64-addresses are primarily used for @address-book, @jump-service, and also internally.
+
+Example:
+
+```
+AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLEov~usVliTSXCSHuRBOCIwIOuDNU0AbVa4BpIx~2sU4TxKhoaA3zQ6VzINoduTdR2IJhPvI5xzezp7dR21CEQGGTbenDslXeQ4iLHFA2~bzp1f7etSl9T2W9RID-KH78sRQmzWnv7dbhNodMbpO6xsf1vENf6bMRzqD5vgHEHZu2aSoNuPyYxDU1eM6--61b2xp9mt1k3ud-5WvPVg89RaU9ugU5cxaHgR927lHMCAEU2Ax~zUb3DbrvgQBOTHnJEx2Fp7pOK~PnP6ylkYKQMfLROosLDXinxOoSKP0UYCh2WgIUPwE7WzJH3PiJVF0~WZ1dZ9mg00c~gzLgmkOxe1NpFRNg6XzoARivNVB5NuWqNxr5WKWMLBGQ9YHvHO1OHhUJTowb9X90BhtHnLK2AHwO6fV-iHWxRJyDabhSMj1kuYpVUBQAEAAcAAA==
+```
+
+
+### In-depth Information
+
+See @destination for details behind @base64-address
diff --git a/_i18n/template/resources/moneropedia/block.md b/_i18n/template/resources/moneropedia/block.md
new file mode 100644
index 0000000000000000000000000000000000000000..cadae194672eb5adacdb1c849d64e0c72ba0bb43
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/block.md
@@ -0,0 +1,16 @@
+---
+layout: moneropedia
+entry: "Block"
+terms: ["block", "blocks"]
+summary: "a container of transactions, a sequence of which forms a blockchain"
+---
+
+### The Basics
+
+A block is a container of @transactions, with a new block being added to the @blockchain once every 2 minutes (see constant `DIFFICULTY_TARGET_V2` defined as 120 seconds), on average.
+
+Blocks also contain a special type of transaction, the @coinbase-transaction, which add newly created Monero to the network.
+
+Blocks are created through the process of @mining, and the @node that successfully mines the block then broadcasts it to each of the @nodes connected to it, who subsequently re-broadcast the block until the entire Monero network has received it.
+
+Fake or bad blocks generally cannot be created, as @nodes that receive blocks always verify the @transactions they contain against a set of consensus rules that all nodes adhere to, including validating the cryptographic @signatures on each transaction.
diff --git a/_i18n/template/resources/moneropedia/blockchain.md b/_i18n/template/resources/moneropedia/blockchain.md
new file mode 100644
index 0000000000000000000000000000000000000000..d20e8cf7753231002d833ad6c1e8f047cce365e3
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/blockchain.md
@@ -0,0 +1,13 @@
+---
+layout: moneropedia
+entry: "Blockchain"
+terms: ["blockchain", "blockchains"]
+summary: "a distributed ledger of all transactions both past and present, without revealing who the funds came from or went to"
+
+---
+
+### 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.
+
+### 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.
diff --git a/_i18n/template/resources/moneropedia/canonically-unique-host.md b/_i18n/template/resources/moneropedia/canonically-unique-host.md
new file mode 100644
index 0000000000000000000000000000000000000000..c11389923934a4dd0ef8ff86017a0c41d9d9835d
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/canonically-unique-host.md
@@ -0,0 +1,23 @@
+---
+layout: moneropedia
+entry: "Canonically-unique host"
+tags: ["kovri"]
+terms: ["Canonically-unique-host"]
+summary: "A host that is canonically resolved to an address or set of addresses"
+---
+
+### The Basics
+
+A Canonically-unique host is a [FQDN](https://en.wikipedia.org/wiki/FQDN) that will canonically resolve to a designated address or set of addresses. Not to be confused with a @locally-unique-host.
+
+### In-depth information
+
+A Canonically-unique host is defined by remote authoritative sources; usually through [DNS](https://en.wikipedia.org/wiki/DNS). When resolving a peer's hostname, you will most likely use an external source for resolution unless you have the following implemented:
+
+- a database file similar to a [hosts file](https://en.wikipedia.org/wiki/etc/hosts)
+- an internal-network resolver (which eventually pulls from external sources)
+
+### Notes
+
+- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
+- @I2P's and @Kovri's self-assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
diff --git a/_i18n/template/resources/moneropedia/change.md b/_i18n/template/resources/moneropedia/change.md
new file mode 100644
index 0000000000000000000000000000000000000000..08163292b111e745bf5cad98c7812f7e6f3ce992
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/change.md
@@ -0,0 +1,16 @@
+---
+layout: moneropedia
+entry: "Change"
+terms: ["change"]
+summary: "Monero sent as part of a transaction, that returns to your account instead of going to another recipient"
+---
+
+### The Basics
+
+{{ page.summary | capitalize }}.
+
+### 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.
+
+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/_i18n/template/resources/moneropedia/clearnet.md b/_i18n/template/resources/moneropedia/clearnet.md
new file mode 100644
index 0000000000000000000000000000000000000000..9200e69a48b0447cad2ba21cbbc085e5cc7af0ab
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/clearnet.md
@@ -0,0 +1,33 @@
+---
+layout: moneropedia
+entry: "Clearnet"
+tags: ["kovri"]
+terms: ["Clearnet"]
+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:
+
+- your [ISP](https://en.wikipedia.org/wiki/ISP)
+- the website/service/person you're communicating with
+- possibly a [Five Eyes](https://en.wikipedia.org/wiki/5_Eyes) capable entity
+
+and even if you use [HTTPS](https://en.wikipedia.org/wiki/HTTPS) or similar (which *encrypts* your transmission), your route is not hidden nor is it anonymous, thus; it is in the *clear*.
+
+### In-depth information
+
+Since a traditional [VPN](https://en.wikipedia.org/wiki/VPN) cannot save you from clearnet (as you are still using *clearnet* (though you are more proxied than without a VPN)), you should use an *anonymous overlay network* to avoid using clearnet directly:
+
+- @Kovri
+- @Java-I2P
+- [Tor](https://torproject.org/)
+
+These technologies protect you from clearnet by building an anonymous network **over** clearnet to keep your transmissions both encrypted **and** anonymous.
+
+Here is an accurate, [interactive diagram](https://www.eff.org/pages/tor-and-https) provided by the [EFF](https://www.eff.org/) which describes *clearnet* as it relates to **Tor**. The concept also (somewhat) applies to @Kovri and @I2P in terms of anonymity with the exception that:
+
+- @Kovri does not use exit nodes when connecting to an @eepsite
+- Your traffic never need to leave the @I2P network
+- You do not need HTTPS to use @Kovri (with the exception of @reseed)
diff --git a/_i18n/template/resources/moneropedia/coinbase.md b/_i18n/template/resources/moneropedia/coinbase.md
new file mode 100644
index 0000000000000000000000000000000000000000..4c564e4ba0e63ac25108c49e8c9332a34c0dac28
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/coinbase.md
@@ -0,0 +1,10 @@
+---
+layout: moneropedia
+entry: "Coinbase Transaction"
+terms: ["coinbase-transaction"]
+summary: "a special type of transaction included in each block, which contains a small amount of Monero sent to the miner as a reward for their mining work"
+---
+
+### The Basics
+
+{{ page.summary | capitalize }}.
\ No newline at end of file
diff --git a/_i18n/template/resources/moneropedia/consensus.md b/_i18n/template/resources/moneropedia/consensus.md
new file mode 100644
index 0000000000000000000000000000000000000000..192e9d9eb4e932068d5bbbab5fb8ceb7f9164f67
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/consensus.md
@@ -0,0 +1,10 @@
+---
+layout: moneropedia
+entry: "Consensus"
+terms: ["consensus", "consensus-network"]
+summary: "consensus describes a property of distributed networks like Monero where most of the participants follow the rules, and thus reject bad participants"
+---
+
+### The Basics
+
+{{ page.summary | capitalize }}.
\ No newline at end of file
diff --git a/_i18n/template/resources/moneropedia/cryptocurrency.md b/_i18n/template/resources/moneropedia/cryptocurrency.md
new file mode 100644
index 0000000000000000000000000000000000000000..45d736c217de532757e9cff5f7a33ddd20367ef5
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/cryptocurrency.md
@@ -0,0 +1,22 @@
+---
+layout: moneropedia
+entry: "Cryptocurrency"
+terms: ["cryptocurrency", "cryptocurrencies", "altcoin", "altcoins"]
+summary: "a digital currency in which encryption techniques are used to regulate the generation of units of currency and verify the transfer of funds, usually operating independently of a central bank"
+---
+
+### The Basics
+
+{{ page.summary | capitalize }}.
+
+### 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).
+
+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).
+
+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.
+
+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/_i18n/template/resources/moneropedia/data-directory.md b/_i18n/template/resources/moneropedia/data-directory.md
new file mode 100644
index 0000000000000000000000000000000000000000..e66f6959ee451482316151ca5a9417aabbb20d76
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/data-directory.md
@@ -0,0 +1,22 @@
+---
+layout: moneropedia
+entry: "Data Directory"
+tags: ["kovri"]
+terms: ["Data-Directory"]
+summary: "Where essential kovri data for runtime is stored"
+---
+
+### The Basics
+
+Depending on your OS, @Kovri currently stores all run-time data in the following directory:
+
+- Linux/FreeBSD:
+ - `$HOME/.kovri`
+
+- OSX:
+ - `$HOME/Library/Application\ Support/Kovri`
+
+- Windows:
+ - `"$APPDATA"\\Kovri`
+
+This includes all configuration files, @address-book, certificates, and resources.
diff --git a/_i18n/template/resources/moneropedia/denominations.md b/_i18n/template/resources/moneropedia/denominations.md
new file mode 100644
index 0000000000000000000000000000000000000000..24bda2415ab2f79ad93f1ab59685842ca589ad44
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/denominations.md
@@ -0,0 +1,36 @@
+---
+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.)"
+---
+
+### 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).
+
+### Denominations of Monero
+
+|------------+----------+-------------------|
+| Name | Base 10 | Amount |
+|-----------:|:--------:| -----------------:|
+| piconero | 10^-12 | 0.000000000001 |
+| nanonero | 10^-9 | 0.000000001 |
+| micronero | 10^-6 | 0.000001 |
+| millinero | 10^-3 | 0.001 |
+| centinero | 10^-2 | 0.01 |
+| decinero | 10^-1 | 0.1 |
+|============+==========+===================|
+| **monero** | **10^0** | **1** |
+|============+==========+===================|
+| decanero | 10^1 | 10 |
+| hectonero | 10^2 | 100 |
+| kilonero | 10^3 | 1,000 |
+| meganero | 10^6 | 1,000,000 |
+|------------+----------+-------------------|
+
+### 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 }}.
diff --git a/_i18n/template/resources/moneropedia/destination.md b/_i18n/template/resources/moneropedia/destination.md
new file mode 100644
index 0000000000000000000000000000000000000000..a999bebfba3fecd61acf623c719ce40a14b780a7
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/destination.md
@@ -0,0 +1,19 @@
+---
+layout: moneropedia
+entry: "Destination"
+tags: ["kovri"]
+terms: ["Destination", "Destinations"]
+summary: "A in-net address that serves as a final endpoint (either local or remote)"
+---
+
+### The Basics
+
+A @destination is the @I2P @in-net address of the final endpoint you are trying to connect to (example: an @I2P website, service, or Monero node). This can also include a *local destination* of which *other* peers need to connect to in order to make contact for communication (similar to how, in @clearnet, your IP address is given to a website when you connect so it knows *where* to send the information back to).
+
+### 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:
+
+`256-byte public key + 128-byte signing key + a null certificate = 516 bytes in Base64 representation`
+
+Note: certificates are not used now but, if they were, the keys would be longer.
diff --git a/_i18n/template/resources/moneropedia/eepsite.md b/_i18n/template/resources/moneropedia/eepsite.md
new file mode 100644
index 0000000000000000000000000000000000000000..5fbb9545d5e7695ea063407cc5f5e880e07a7df4
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/eepsite.md
@@ -0,0 +1,30 @@
+---
+layout: moneropedia
+entry: "Eepsite"
+tags: ["kovri"]
+terms: ["Eepsite", "Hidden-Service", "Garlic-Site", "Garlic-Service"]
+summary: "A website or service hosted within the I2P network"
+---
+
+### The Basics
+
+Is it [**EEP!** *(in response to the site's content)*](https://en.wikipedia.org/wiki/Onomatopoeia), or **end-to-end protocol**, or something else entirely different?
+
+While the original definition of eepsite has been lost with time, its use-case remains: an eepsite is a website or service that is hosted within (and only accessible by) the @I2P network.
+
+### In-depth Information
+
+Alternate names include:
+
+1. *Hidden Service*
+ - because the site/service is *hidden* within the @I2P network and can only be visited within the network
+2. *Garlic Site*
+ - because the website utilizes @I2P's @garlic-routing technology as a means of communicating with a client
+ - because the service is hosted as a website and not any other type of service
+3. *Garlic Service*
+ - because the service utilizes @I2P's @garlic-routing technology as a means of communicating with a client
+ - because the service is specific to services like IRC, email, or a Monero peer (but may also include websites)
+
+### Notes
+
+To learn how to setup an Eepsite (Hidden Service, Garlic Site, Garlic Service) visit the @Kovri [user-guide](https://github.com/monero-project/kovri/blob/master/doc/USER_GUIDE.md).
diff --git a/_i18n/template/resources/moneropedia/encryption.md b/_i18n/template/resources/moneropedia/encryption.md
new file mode 100644
index 0000000000000000000000000000000000000000..d9356c4b15ea16aca56fcf4ae8c00537e87a3dd4
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/encryption.md
@@ -0,0 +1,35 @@
+---
+layout: moneropedia
+entry: "Encryption"
+tags: ["kovri"]
+terms: ["encryption", "encrypted", "encrypting", "decryption", "decrypted", "decrypting"]
+summary: "The process of encoding messages or information in a way that only authorized parties can decode and read"
+---
+
+### The Basics
+
+From [Encryption](https://en.wikipedia.org/wiki/Encryption):
+
+>
+In cryptography, encryption is the process of encoding messages or information in such a way that only authorized parties can decode and read what is sent. Encryption does not of itself prevent interception, but denies the message content to the interceptor.
+
+### In-depth information
+
+From [Encryption](https://en.wikipedia.org/wiki/Encryption):
+
+>
+ In an encryption scheme, the intended communication information or message (referred to as *plaintext*), is encrypted using an encryption algorithm, generating ciphertext that can only be read if decrypted. For technical reasons, an encryption scheme usually uses a pseudo-random encryption key generated by an algorithm. It is in principle possible to decrypt the message without possessing the key, but, for a well-designed encryption scheme, large computational resources and skill are required. An authorized recipient can easily decrypt the message with the key provided by the originator to recipients, but not to unauthorized interceptors.
+
+>
+The purpose of encryption is to ensure that only somebody who is authorized to access data (e.g. a text message or a file), will be able to read it, using the decryption key. Somebody who is not authorized can be excluded, because he or she does not have the required key, without which it is impossible to read the encrypted information.
+
+### Kovri
+
+@Kovri implements various types of encryption in *at least* 4 essential capacities:
+
+- @Reseed for bootstrapping
+- @Garlic-routing: three layers of encryption (@garlic-encryption) are used to verify the secure delivery of @messages to the recipient/peer/@destination
+- @Tunnel encryption: garlic messages are passed through a @tunnel and encrypted by the @tunnel gateway to the @tunnel endpoint
+- @Transport layer encryption prevents the ability to decrypt @messages at the [media layer](https://en.wikipedia.org/wiki/OSI_model)
+
+For details on the types of encryption and cryptographic @signatures used in @Kovri and @I2P, visit @Java-I2P's [Cryptography](https://geti2p.net/spec/cryptography)
diff --git a/_i18n/template/resources/moneropedia/floodfill.md b/_i18n/template/resources/moneropedia/floodfill.md
new file mode 100644
index 0000000000000000000000000000000000000000..e3fbf54f6cbea9a5496f73a15a71222454971430
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/floodfill.md
@@ -0,0 +1,15 @@
+---
+layout: moneropedia
+entry: "Floodfill"
+tags: ["kovri"]
+terms: ["Floodfill"]
+summary: "An I2P router which maintains a distributed network-database"
+---
+
+### The Basics
+
+By actively managing a distributed network-database, a router with *floodfill* capability has the ability to help maintain network stability and resiliancy while also being decentralized and trust-less.
+
+### In-depth information
+
+Though floodfill itself is a simple storage system, the technical underpinnings of floodfill as it relates to @network-database and other protocols within @I2P are much more complex. Visit the [Network Database](https://geti2p.net/en/docs/how/network-database) page for details.
diff --git a/_i18n/template/resources/moneropedia/fungibility.md b/_i18n/template/resources/moneropedia/fungibility.md
new file mode 100644
index 0000000000000000000000000000000000000000..47ca7d01e0f76ec37a736b3638a49e341e59b6f0
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/fungibility.md
@@ -0,0 +1,16 @@
+---
+layout: moneropedia
+entry: "Fungibility"
+terms: ["fungibility"]
+summary: "property of a currency whereby two units can be substituted in place of one another"
+---
+
+### 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.
+
+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.
+
+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.
+
+{{ page.summary | capitalize }}.
diff --git a/_i18n/template/resources/moneropedia/garlic-encryption.md b/_i18n/template/resources/moneropedia/garlic-encryption.md
new file mode 100644
index 0000000000000000000000000000000000000000..3364f521c3ba5f6aa275ec1ec252756c29d40e84
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/garlic-encryption.md
@@ -0,0 +1,25 @@
+---
+layout: moneropedia
+entry: "Garlic-Encryption"
+tags: ["kovri"]
+terms: ["Garlic-Encryption", "Layered-Encryption"]
+summary: "Layered encryption as implemented in Kovri / I2P"
+---
+
+### The Basics
+
+@garlic-encryption is @I2P's implementation of @message based @layered-encryption (similar to flow-based [Onion-Routing](https://en.wikipedia.org/wiki/Onion_routing)).
+
+By @encrypting @messages in layers, this allows a @message to be routed through a sequence of proxies without allowing the proxies (or any intermediaries) to read the contents of the @message. @Layered-Encryption is a fundamental feature in @Kovri, @I2P, and [Tor](https://torproject.org) and is the cornerstone for securing anonymity within these overlay-networks.
+
+### In-depth information
+
+For @garlic-encryption, the primary difference between @Kovri/@I2P and Tor is:
+
+- @Kovri/@I2P bundles multiple @messages together to form garlic "cloves"
+ - any number of messages can be contained in a "clove" instead of *only* a single message
+- @Kovri/@I2P uses [ElGamal](https://en.wikipedia.org/wiki/ElGamal)/[AES](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard) @encryption for @messages and @transports
+
+### Notes
+
+For details, see @garlic-routing.
diff --git a/_i18n/template/resources/moneropedia/garlic-routing.md b/_i18n/template/resources/moneropedia/garlic-routing.md
new file mode 100644
index 0000000000000000000000000000000000000000..55cd2122f0393c9a1b0d3e8559e7a709be21e5d6
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/garlic-routing.md
@@ -0,0 +1,45 @@
+---
+layout: moneropedia
+entry: "Garlic Routing"
+tags: ["kovri"]
+terms: ["Garlic-Routing"]
+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 @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).
+
+### History
+
+In written form, the term *@garlic-routing* can be seen as early as June of 2000 in Roger Dingledine's [Free Haven Master's thesis](http://www.freehaven.net/papers.html) (Section 8.1.1) as derived from the term Onion Routing.
+
+As recent as October of 2016, [#tor-dev](https://oftc.net/WebChat/) has offered insight into the creation of the term *@garlic-routing*:
+
+[Nick Mathewson](https://en.wikipedia.org/wiki/The_Tor_Project,_Inc):
+>[I think that there was some attempt to come up with a plant whose structure resembled the 'leaky-pipe' topology of tor, but I don't believe we ever settled on one.]
+
+[Roger Dingledine](https://en.wikipedia.org/wiki/Roger_Dingledine):
+>during the free haven brainstorming, there was a moment where we described a routing mechanism, and somebody said "garlic routing!", and everybody laughed.
+so we for sure thought we had invented the name, at the time.
+
+*Note: permission to use the aforementioned quotes was granted by Nick Mathewson and Roger Dingledine*
+
+### In-depth Information
+
+In technical terms, for @Kovri and @I2P, *@garlic-routing* translates to any/all of the following:
+
+- @Layered-Encryption (similar to the @layered-encryption in Onion Routing)
+- Bundling multiple @messages together (garlic cloves)
+- ElGamal/AES @encryption
+
+*Note: though [Tor](https://torproject.org/) uses @layered-encryption, Tor does not use ElGamal and is not message-based.*
+
+**Read more in @garlic-encryption.**
+
+### Notes
+
+- In terms of Onion/Garlic Routing, another way to envision layered @encryption is by replacing the onion/garlic with a [Matryoshka doll](https://en.wikipedia.org/wiki/Matryoshka_doll) - with each outer/inner doll having a lock and public key to the next/previous doll
+- For more technical details on Garlic Routing, read the @Java-I2P entry on [Garlic Routing](https://geti2p.net/en/docs/how/garlic-routing)
diff --git a/_i18n/template/resources/moneropedia/i2np.md b/_i18n/template/resources/moneropedia/i2np.md
new file mode 100644
index 0000000000000000000000000000000000000000..d05c17aab63a037c98932257c714f93285f1151d
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/i2np.md
@@ -0,0 +1,28 @@
+---
+layout: moneropedia
+entry: "I2NP"
+tags: ["kovri"]
+terms: ["I2NP"]
+summary: "The I2P Network Protocol: the mechanism in which I2NP messages are sent over the I2P network"
+---
+
+### The Basics
+
+From @Java-I2P:
+
+>
+@I2NP manages the routing and mixing of messages between routers, as well as the selection of what transports to use when communicating with a peer for which there are multiple common transports supported
+
+### In-depth information
+
+From @Java-I2P:
+
+>
+@I2NP (@I2P Network Protocol) @messages can be used for one-hop, router-to-router, point-to-point @messages. By @encrypting and wrapping @messages in other @messages, they can be sent in a secure way through multiple hops to the ultimate @destination. @I2NP does not specify nor require any particular @transport layer but does require at least one @transport in use.
+
+>
+Whenever a @destination wants to send a message to to another @destination, it provides its local router with both the @destination structure and the raw bytes of the message to be sent. The router then determines where to send it, delivers it through outbound @tunnels, instructing the end point to pass it along to the appropriate inbound @tunnel, where it is passed along again to that @tunnel's end point and made available to the target for reception.
+
+### Notes
+
+Read more about the @I2NP [protocol](https://geti2p.net/en/docs/protocol/i2np) and [specification](https://geti2p.net/spec/i2np).
diff --git a/_i18n/template/resources/moneropedia/i2p.md b/_i18n/template/resources/moneropedia/i2p.md
new file mode 100644
index 0000000000000000000000000000000000000000..2778db301a50271acafe3eead81b704ae4ff333b
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/i2p.md
@@ -0,0 +1,31 @@
+---
+layout: moneropedia
+entry: "I2P"
+tags: ["kovri"]
+terms: ["I2P"]
+summary: "The Invisible Internet Project: an anonymizing overlay network"
+---
+
+### Monero
+
+For Monero's implementation of @I2P, see @Kovri. For a comparison of @I2P to [Tor](https://torproject.org/), read the [Comparison](https://geti2p.net/en/comparison/tor) page.
+
+### The Basics
+
+From @Java-I2P:
+
+>The I2P network provides strong privacy protections for communication over the Internet. Many activities that would risk your privacy on the public Internet can be conducted anonymously inside I2P.
+
+### In-depth information
+
+From @Java-I2P:
+
+>I2P is an anonymous overlay network - a network within a network. It is intended to protect communication from dragnet surveillance and monitoring by third parties such as ISPs.
+
+>I2P is used by many people who care about their privacy: activists, oppressed people, journalists and whistleblowers, as well as the average person.
+
+>No network can be "perfectly anonymous". The continued goal of I2P is to make attacks more and more difficult to mount. Its anonymity will get stronger as the size of the network increases and with ongoing academic review.
+
+### Notes
+
+@I2P documentation and specifications are available [here](https://geti2p.net/docs/).
diff --git a/_i18n/template/resources/moneropedia/i2pcontrol.md b/_i18n/template/resources/moneropedia/i2pcontrol.md
new file mode 100644
index 0000000000000000000000000000000000000000..481d9eae6f086f719e8e57ab5651d2c039875069
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/i2pcontrol.md
@@ -0,0 +1,17 @@
+---
+layout: moneropedia
+entry: "I2PControl"
+tags: ["kovri"]
+terms: ["I2PControl"]
+summary: "An API inteface for Kovri and Java-I2P that allows simple remote control"
+---
+
+### 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.
+
+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.
+
+### In-depth information
+
+Details and specification available on the [I2PControl](https://geti2p.net/en/docs/api/i2pcontrol) page.
diff --git a/_i18n/template/resources/moneropedia/in-net.md b/_i18n/template/resources/moneropedia/in-net.md
new file mode 100644
index 0000000000000000000000000000000000000000..92404f08b6ed21a2181c4ac5c843df89a77544c2
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/in-net.md
@@ -0,0 +1,15 @@
+---
+layout: moneropedia
+entry: "In-net"
+tags: ["kovri"]
+terms: ["In-net"]
+summary: "Within the I2P network"
+---
+
+### The Basics
+
+**In-net** is a [colloquial](https://en.wikipedia.org/wiki/Colloquial) term of which describes activities, protocols, or functionality that exist *only* within the @I2P network.
+
+### In-depth information
+
+Example: *in-net download* would be defined as downloading *only* within @I2P.
diff --git a/_i18n/template/resources/moneropedia/index.md b/_i18n/template/resources/moneropedia/index.md
new file mode 100644
index 0000000000000000000000000000000000000000..4489586c05835703abe0ed61bd85827a223a8986
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/index.md
@@ -0,0 +1,21 @@
+---
+layout: full
+title: "Moneropedia"
+title-pre-kick: "Moneropedia - The "
+title-kick: "Monero Wiki"
+title-post-kick: ""
+kick-class: "softyellow-kicks"
+icon: "icon_wiki"
+attribution: "<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->"
+---
+
+
+<div class="row">
+
+@moneropedia
+
+</div>
+
+<p><a href="https://github.com/monero-project/monero-site/new/master/knowledge-base/moneropedia" class="btn-link btn-auto btn-primary">Add New Entry</a></p>
+
+If there is an entry you'd like to modify or be added, please [open an issue on this website's Github repository](https://github.com/monero-project/monero-site/issues) or submit changes via pull request.
\ No newline at end of file
diff --git a/_i18n/template/resources/moneropedia/java-i2p.md b/_i18n/template/resources/moneropedia/java-i2p.md
new file mode 100644
index 0000000000000000000000000000000000000000..e040579b58e2dd421a585c3c2ef0bc2098770479
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/java-i2p.md
@@ -0,0 +1,15 @@
+---
+layout: moneropedia
+entry: "Java I2P"
+tags: ["kovri"]
+terms: ["Java-I2P"]
+summary: "The original implementation of I2P - written in Java"
+---
+
+### The Basics
+
+The term "Java I2P" is often used to describe the original @I2P implementation currently most known and used today. There are various other @I2P implementations, including @Kovri; all of which look up to the original Java implementation.
+
+### Notes
+
+To download/learn more about the Java implementation, visit their [website](https://geti2p.net/).
diff --git a/_i18n/template/resources/moneropedia/jump-service.md b/_i18n/template/resources/moneropedia/jump-service.md
new file mode 100644
index 0000000000000000000000000000000000000000..228ebb989d41589751aae44bccd3e1dc6fb3fa0d
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/jump-service.md
@@ -0,0 +1,34 @@
+---
+layout: moneropedia
+entry: "Jump Service"
+tags: ["kovri"]
+terms: ["Jump-Service"]
+summary: "An I2P website service that adds addresses to your address book"
+---
+
+### The Basics
+
+In your @I2P configured web browser, you can use a Jump Service to *jump* to an @I2P address that you don't have in your @address-book. Once you've *jumped* to the address, the address will be saved into your @address-book.
+
+### In-depth Information
+
+In an @I2P configured browser, visit: http://stats.i2p/i2p/lookup.html (courtesy of @Java-I2P's lead developer *zzz*)
+
+Then, you'll have two options:
+
+1. *Hostname lookup* the address you wish to visit and then manually copy/paste the result
+2. *Jump* to the @I2P website by entering the @I2P hostname (**recommended**)
+
+### Using hostname lookup
+
+For example, entering `pinkpaste.i2p` into the *Hostname lookup* box (and then submitting) will return:
+
+```
+pinkpaste.i2p=m-HrPrIAsdxts0WM~P4mE8mt9P7g-QTaBvu7Gc6Nl0UX7Vwck-i~RvOPfK6W~kfdRvwhNTqevkBL2UF5l36We02Aiywu7kB2xOHRkze68h-Tg2ewvRVwokohguCD2G3wwAEz~7FVda2avYDCb9-N6TfuzxKLnmhPMvbNSjGL7ZsD2p-h207R3-2kvuMV9bfu-K~w9NI9XJhIyufvUnFYc2jnTVg8PbaR4UP57cNaOO2YIMPkbr6~yTcIu9B1sUfHK6-N~6virQDOxW4M-62rjnZkLpaCtkOsXslmCwZI--TkZ6hKi1kXZvNmJRE1rYfffYRFn38zhaqszeETX8HiIvahZhXF5fNumBziYdmLdw8hkuN1A~emU6Xz9g~a1Ixfsq1Qr~guYoOtaw-0rOFxNRS9yMehE-2LCb8c-cAg6z5OdlN4qJDl~ZHgru4d~EHp~BpAK3v7u2Gi-8l1ygVW-1CHVna~fwnbOPN3ANPwh6~~yUit0Cx1f54XiNRn6-nPBQAEAAcAAA==
+```
+
+Copy/paste this host=@base64-address pairing into your **private** @subscription.
+
+### Directly jumping
+
+For example, entering `pinkpaste.i2p` into the *Jump* box (and then submitting) will automatically redirect you to the website **and** insert the @locally-unique-host into @address-book.
diff --git a/_i18n/template/resources/moneropedia/kovri.md b/_i18n/template/resources/moneropedia/kovri.md
new file mode 100644
index 0000000000000000000000000000000000000000..6002cdd6b71750cae566c3d83759f8e04f02463b
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/kovri.md
@@ -0,0 +1,62 @@
+---
+layout: moneropedia
+entry: "Kovri"
+tags: ["kovri"]
+terms: ["Kovri"]
+summary: "Monero's C++ router implementation of the I2P network"
+---
+
+### The Basics
+
+[Kovri](https://github.com/monero-project/kovri/) is a C++ implementation of the @I2P network. @Kovri is currently in heavy, active development and not yet integrated with Monero. When Kovri is integrated into your Monero @node, your transactions will be more secure than ever before.
+
+### In-depth information
+
+Kovri will protect you and Monero from:
+
+- @Node partitioning attacks
+- Associations between a particular txid and your IP address
+- Mining and/or running a node in highly adversarial environments
+- Metadata leakage (e.g., @OpenAlias lookups)
+
+...and much more.
+
+Read [anonimal's FFS proposal](https://forum.getmonero.org/9/work-in-progress/86967/anonimal-s-kovri-full-time-development-funding-thread) for more details and for reasoning behind the project. Also read the FAQ and User Guide in the [Kovri repository](https://github.com/monero-project/kovri/).
+
+### @Kovri / @I2P Terminology
+
+#### Client + API
+
+- @Address-Book
+- @Base32-address
+- @Base64-address
+- @Canonically-unique-host
+- @Eepsite (@Hidden-Service, @Garlic-Site, @Garlic-Service)
+- @I2PControl
+- @Jump-Service
+- @Locally-unique-host
+- @Reseed
+- @Subscription
+
+#### Core + Router
+
+- @Clearnet
+- @Data-Directory
+- @Destination
+- @Encryption
+- @Floodfill
+- @Garlic-Encryption
+- @Garlic-Routing
+- @I2NP
+- @In-net
+- @Java-I2P
+- @Layered-Encryption
+- @Lease
+- @LeaseSet
+- @Message @Messages
+- @NTCP
+- @Network-Database
+- @Router-Info
+- @SSU
+- @Transports
+- @Tunnel
diff --git a/_i18n/template/resources/moneropedia/lease-set.md b/_i18n/template/resources/moneropedia/lease-set.md
new file mode 100644
index 0000000000000000000000000000000000000000..99165a037191f77094473ec8628120eeee9dfcd6
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/lease-set.md
@@ -0,0 +1,25 @@
+---
+layout: moneropedia
+entry: "Lease-Set"
+tags: ["kovri"]
+terms: ["LeaseSet", "LeaseSets"]
+summary: "Contains all currently authorized Leases for a particular I2P Destination"
+---
+
+### The Basics
+
+A Lease-Set contains a set of authorized @leases (and other related information) for a particular @destination.
+
+### In-depth information
+
+A Lease-Set contains:
+
+- all of the currently authorized @leases for a particular @destination
+- the public key to which garlic messages can be encrypted (see @garlic-routing)
+- the signing public key that can be used to revoke this particular version of the structure
+
+The Lease-Set is one of the two structures stored in the @network-database (the other being @router-info), and is keyed under the SHA256 of the contained @destination.
+
+### Notes
+
+For further details, read @Java-I2P's [LeaseSet](https://geti2p.net/en/docs/how/network-database#leaseSet)
diff --git a/_i18n/template/resources/moneropedia/lease.md b/_i18n/template/resources/moneropedia/lease.md
new file mode 100644
index 0000000000000000000000000000000000000000..d3cdc5451462953f08a56740ec3dec345e87849d
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/lease.md
@@ -0,0 +1,15 @@
+---
+layout: moneropedia
+entry: "Lease"
+tags: ["kovri"]
+terms: ["Lease", "Leases"]
+summary: "Authorizes an I2P tunnel to receive messages targeting a destination"
+---
+
+### The Basics
+
+A lease defines the authorization for a particular @I2P @tunnel to receive a @messages targeting a @destination.
+
+### In-depth information
+
+For further details, read @Java-I2P's [Lease](https://geti2p.net/spec/common-structures#lease)
diff --git a/_i18n/template/resources/moneropedia/locally-unique-host.md b/_i18n/template/resources/moneropedia/locally-unique-host.md
new file mode 100644
index 0000000000000000000000000000000000000000..3ce7f8605a072da5eb42b562f7284329d998312a
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/locally-unique-host.md
@@ -0,0 +1,22 @@
+---
+layout: moneropedia
+entry: "Locally-unique host"
+tags: ["kovri"]
+terms: ["Locally-unique-host"]
+summary: "A host defined by you and resolved only by you"
+---
+
+### The Basics
+
+A locally-unique host is a [FQDN](https://en.wikipedia.org/wiki/FQDN) defined by **you** and resolved only by you; similar to how a [hosts file](https://en.wikipedia.org/wiki/etc/hosts) is implemented. Not to be confused with @canonically-unique-host.
+
+### In-depth information
+
+You have the option to share your interpretation of how the host is resolved (e.g., `localhost` always resolves to `127.0.0.1`) but the resolution is not canonically enforced (e.g., someone else can map `localhost` to any arbitrary IP address).
+
+Hosts in a public subscription can be considered @canonically-unique-host's within the @I2P network but, ultimately, you are free to re-define them as you wish.
+
+### Notes
+
+- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
+- @I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
diff --git a/_i18n/template/resources/moneropedia/message.md b/_i18n/template/resources/moneropedia/message.md
new file mode 100644
index 0000000000000000000000000000000000000000..c9504d54ef3cf16bf9a2f9f94d589e9543e294a1
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/message.md
@@ -0,0 +1,33 @@
+---
+layout: moneropedia
+entry: "Message"
+tags: ["kovri"]
+terms: ["Message", "Messages"]
+summary: "The mechanisms in which information travels within I2P"
+---
+
+### The Basics
+
+*Messages* (which exist on top of the @transports layer), contain varying types of information that are needed for the network but, most importantly, everything you see, do, send, or receive, will come and go in the form of *messages*.
+
+There are 2 essential types of *messages* in @I2P:
+
+- @Tunnel messages
+- @I2NP messages
+
+Essentially: *@tunnel messages* **contain** @I2NP **message fragments** which are then [reassembled](https://geti2p.net/en/docs/tunnels/implementation) at certain points within a @tunnel's path.
+
+### In-depth information
+
+@I2NP messages have a close relationship with @tunnel @messages so it is easy to get the term *messages* confused when reading @Java-I2P specifications:
+
+>
+1. First, the tunnel gateway accumulates a number of I2NP messages and preprocesses them into tunnel messages for delivery.
+2. Next, that gateway encrypts that preprocessed data, then forwards it to the first hop.
+3. That peer, and subsequent tunnel participants, unwrap a layer of the encryption, verifying that it isn't a duplicate, then forward it on to the next peer.
+4. Eventually, the tunnel messages arrive at the endpoint where the I2NP messages originally bundled by the gateway are reassembled and forwarded on as requested.
+
+### Notes
+
+- @I2NP @messages need to be fragmented because they are variable in size (from 0 to almost 64 KB) and @tunnel @messages are fixed-size (approximately 1 KB).
+- For details and specifications, visit the [I2NP spec](https://geti2p.net/spec/i2np) and [Tunnel Message spec](https://geti2p.net/spec/tunnel-message)
diff --git a/_i18n/template/resources/moneropedia/miners.md b/_i18n/template/resources/moneropedia/miners.md
new file mode 100644
index 0000000000000000000000000000000000000000..5937ce6d5ec07ce27cd31fe4250d8facb96e07ff
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/miners.md
@@ -0,0 +1,20 @@
+---
+layout: moneropedia
+entry: "Mining"
+terms: ["mining", "miner", "miners"]
+summary: "the process of cryptographically computing a mathematical proof for a block, containing a number of transactions, which is then added to the blockchain"
+---
+
+### 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.
+
+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.
+
+
+
+{{ page.summary | capitalize }}.
diff --git a/_i18n/template/resources/moneropedia/mnemonicseed.md b/_i18n/template/resources/moneropedia/mnemonicseed.md
new file mode 100644
index 0000000000000000000000000000000000000000..608f8d8bd28fc88dbdf27cc667856d95536f5506
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/mnemonicseed.md
@@ -0,0 +1,20 @@
+---
+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"
+---
+
+### The Basics
+
+{{ page.summary | capitalize }}. This 25-word phrase (13 words in the case of MyMonero) has all the information needed to view and spend funds from a Monero @account.
+
+### In-depth Information
+
+In the official wallet, the mnemonic seed comprises 25 words with the last word being used as a checksum. Those words correspond to a 256-bit integer, which is the account's *private* @spend-key. The *private* @view-key is derived by hashing the private spend key with Keccak-256, producing a second 256-bit integer. The corresponding *public* keys are then derived from the private keys.
+
+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!
+
+By creating a cold, or @paper-wallet you can safely store Moneroj.
diff --git a/_i18n/template/resources/moneropedia/network-database.md b/_i18n/template/resources/moneropedia/network-database.md
new file mode 100644
index 0000000000000000000000000000000000000000..a5bb078c35c3e207f6d2862d45d7b8661a7a837d
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/network-database.md
@@ -0,0 +1,25 @@
+---
+layout: moneropedia
+entry: "Network Database"
+tags: ["kovri"]
+terms: ["Network-Database"]
+summary: "A distributed database which contains needed router information so the network can stay intact"
+---
+
+### The Basics
+
+@network-database is a [distributed database](https://en.wikipedia.org/wiki/Distributed_database) which contains router information that peers must use so the network can stay intact.
+
+### In-depth information
+
+From @Java-I2P:
+
+>
+@I2P's @network-database is a specialized distributed database, containing just two types of data - router contact information (@Router-Infos) and @destination contact information (@LeaseSets). Each piece of data is signed by the appropriate party and verified by anyone who uses or stores it. In addition, the data has liveliness information within it, allowing irrelevant entries to be dropped, newer entries to replace older ones, and protection against certain classes of attack.
+
+>
+The @network-database is distributed with a simple technique called "@floodfill", where a subset of all routers, called "@floodfill routers", maintains the distributed database.
+
+### Notes
+
+Read [Network-Database](https://geti2p.net/en/docs/how/network-database) for details.
diff --git a/_i18n/template/resources/moneropedia/node.md b/_i18n/template/resources/moneropedia/node.md
new file mode 100644
index 0000000000000000000000000000000000000000..dde76903ff7400e62eb556a8b8faa7ec348825f0
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/node.md
@@ -0,0 +1,25 @@
+---
+layout: moneropedia
+entry: "Node"
+terms: ["node", "nodes", "full-node", "full-nodes"]
+summary: "a device on the Internet running the Monero software, with a full copy of the Monero blockchain, actively assisting the Monero network"
+---
+
+### The Basics
+
+{{ page.summary | capitalize }}.
+
+### 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).
+
+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.
+
+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.
+
+---
+
+##### Other Resources
+<sub>1. *Fluffypony gives a great explanation of why mandatory hardforks are good for Monero.* ([Monero Missives for the Week of 2016-06-20](https://getmonero.org/2016/06/20/monero-missive-for-the-week-of-2016-06-20.html))</sub>
diff --git a/_i18n/template/resources/moneropedia/ntcp.md b/_i18n/template/resources/moneropedia/ntcp.md
new file mode 100644
index 0000000000000000000000000000000000000000..69f3152c0be355a7ab283d2a9f15dd90aed73e66
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/ntcp.md
@@ -0,0 +1,34 @@
+---
+layout: moneropedia
+entry: "NTCP"
+tags: ["kovri"]
+terms: ["NTCP"]
+summary: "NIO-Based TCP (Non-blocking I/O based TCP): one of two Kovri transports"
+---
+
+### The Basics
+
+*NIO-Based TCP (Non-blocking I/O based TCP)* is one of two encrypted @transports for @Kovri.
+
+Similar to @SSU, @NTCP's *primary* purpose is to securely transmit @in-net @I2NP messages through @tunnels but, unlike @SSU, @NTCP functions solely over encrypted [TCP](https://en.wikipedia.org/wiki/Transmission_Control_Protocol).
+
+### In-depth information
+
+ - Passes along individual @I2NP messages (both Standard and Time Sync) after:
+ - TCP has been established
+ - Establishment Sequence has been completed
+ - Uses the following @encryption:
+ - 2048-bit [Diffie-Hellman](https://en.wikipedia.org/wiki/Diffie-hellman)
+ - [AES-256](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard)/[CBC](https://en.wikipedia.org/wiki/Block_cipher_modes_of_operation)
+ - Establishment Sequence has the following *states*:
+ - Pre-establishment
+ - Establishment
+ - Post-establishment or "Established"
+ - Uses the following from the @network-database:
+ - Transport name: NTCP
+ - Host: IP (IPv4 or IPv6) or host name (shortened IPv6 address (with "::") is allowed)
+ - Port: 1024 - 65535
+
+### Notes
+
+For further details, read @Java-I2P's [NTCP](https://geti2p.net/en/docs/transport/ntcp)
diff --git a/_i18n/template/resources/moneropedia/openalias.md b/_i18n/template/resources/moneropedia/openalias.md
new file mode 100644
index 0000000000000000000000000000000000000000..2410130cb910285cdf3ab0f02371d44cdd63183a
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/openalias.md
@@ -0,0 +1,20 @@
+---
+layout: moneropedia
+entry: "OpenAlias"
+terms: ["OpenAlias"]
+summary: "a standard that allows you to use an email or domain syntax to pay someone instead of an address, eg. donate@getmonero.org or donate.getmonero.org"
+---
+
+### The Basics
+
+The Monero Core Team released a standard called OpenAlias which permits much more human-readable addresses and "squares" the Zooko's triangle. OpenAlias can be used for any cryptocurrency and is already implemented in Monero, Bitcoin (in latest Electrum versions) and HyperStake.
+
+OpenAlias seeks to provide a way to simplify aliasing amidst a rapidly shifting technology climate. Users are trying to cross the bridge to private and cryptographically secure infrastructure and systems, but many of them have just barely started remembering the email addresses of their friends and family.
+
+As part of the ongoing development of the Monero cryptocurrency project, we asked ourselves: how can we simplify payments for users unfamiliar with cryptocurrency? Monero stealth addresses are at least 95 characters long - memorizing them is not an option, and asking someone to send a payment to <95-character-string> is only going to lead to confusion.
+
+At its most basic, OpenAlias is a TXT DNS record on a FQDN (fully qualified domain name). By combining this with DNS-related technologies we have created an aliasing standard that is extensible for developers, intuitive and familiar for users, and can interoperate with both centralized and decentralized domain systems.
+
+{{ page.summary | capitalize }}.
+
+More information can be found on the [OpenAlias page](/knowledge-base/openalias) or on the [OpenAlias website](https://openalias.org)
diff --git a/_i18n/template/resources/moneropedia/paperwallet.md b/_i18n/template/resources/moneropedia/paperwallet.md
new file mode 100644
index 0000000000000000000000000000000000000000..95ff00baa4b55b875a45d3c487b1c3abb097753c
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/paperwallet.md
@@ -0,0 +1,7 @@
+---
+layout: moneropedia
+entry: "Paper Wallet"
+terms: ["paperwallet", "paperwallets", "paper-wallet", "paper-wallets"]
+summary: "A paper wallet stores the information necessary to send and receive Monero"
+---
+
diff --git a/_i18n/template/resources/moneropedia/paymentid.md b/_i18n/template/resources/moneropedia/paymentid.md
new file mode 100644
index 0000000000000000000000000000000000000000..fba888fa972960f62a18a47dd5c0404f6cc21d37
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/paymentid.md
@@ -0,0 +1,25 @@
+---
+layout: moneropedia
+entry: "Payment ID"
+terms: ["payment-ID", "payment-IDs"]
+summary: "an optional flag that is added to identify transactions to merchants, consisting of 64 hexadecimal characters"
+---
+
+### The Basics
+
+Payment ID is an **arbitrary** and **optional** transaction attachment that consists of 32 bytes (64 hexadecimal characters) or 8 bytes (in the case of integrated addresses).
+
+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
+
+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.
+
+### 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:
+
+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/_i18n/template/resources/moneropedia/pedersen-commitment.md b/_i18n/template/resources/moneropedia/pedersen-commitment.md
new file mode 100644
index 0000000000000000000000000000000000000000..a7ff98bab804cd9a190ae9dcea0c77fe349f4631
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/pedersen-commitment.md
@@ -0,0 +1,24 @@
+---
+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."
+---
+
+### The Basics
+
+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
+
+As long as the encrypted output amounts created, which include an output for the recipient and a change output back to the sender, and the unencrypted transaction fee is equal to the sum of the inputs that are being spent, it is a legitimate transaction and can be confirmed to not be creating Monero out of thin air.
+
+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.
+
+### 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/_i18n/template/resources/moneropedia/reseed.md b/_i18n/template/resources/moneropedia/reseed.md
new file mode 100644
index 0000000000000000000000000000000000000000..eb3b5d986adfd149d0e58eb9098682154136d6ef
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/reseed.md
@@ -0,0 +1,17 @@
+---
+layout: moneropedia
+entry: "Reseed"
+tags: ["kovri"]
+terms: ["Reseed"]
+summary: "The method of which Kovri uses to bootstrap into the I2P network"
+---
+
+### The Basics
+
+When you start @Kovri for the first time (or if it's been offline for a long time), @Kovri will need a list of peers to connect to so it can [bootstrap](https://en.wikipedia.org/wiki/Bootstrap) into the @I2P network. @Kovri gets these peers from a special file stored on a reseed server. On this file are all the various pieces of information @Kovri needs in order to connect with @I2P peers.
+
+### In-depth information
+
+@Kovri has a list of [hard-coded](https://en.wikipedia.org/wiki/Hard-coded) reseed servers available to fetch from. These servers securely serve an [SU3](https://geti2p.net/spec/updates#su3) file (signed with a cryptographic @signature) over @clearnet with [HTTPS](https://en.wikipedia.org/wiki/HTTPS). This SU3 file contains information that's used to verify both the integrity of the file and its content.
+
+Aside from the technical elements needed to verify and process the file, the file's main contents consist of a series of @router-info files which @Kovri and @I2P routers use to locate and communicate with other @I2P peers. These peers are then stored into a @network-database.
diff --git a/_i18n/template/resources/moneropedia/ring-size.md b/_i18n/template/resources/moneropedia/ring-size.md
new file mode 100644
index 0000000000000000000000000000000000000000..a1601651b0994211d852fae4354b65fb86a36cc4
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/ring-size.md
@@ -0,0 +1,11 @@
+---
+layout: moneropedia
+entry: "Ring Size"
+terms: ["ring-size"]
+summary: "total number of possible signers in a ring signature"
+---
+
+### The Basics
+Ring size refers to the total number of possible signers in a @ring-signature. If a ring size of 4 is selected for a given @transaction, this means that there are 3 foreign outputs in addition to your “real†output. A higher ring size number will typically provide more privacy than a lower number. However, reusing an odd, recognizable ring size number for transactions could possibly make transactions stand out.
+
+`Ring size = foreign outputs + 1 (your output)`
\ No newline at end of file
diff --git a/_i18n/template/resources/moneropedia/ringCT.md b/_i18n/template/resources/moneropedia/ringCT.md
new file mode 100644
index 0000000000000000000000000000000000000000..77b9bf3297b0ad2eb2aae23896f6ed936799f792
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/ringCT.md
@@ -0,0 +1,24 @@
+---
+layout: moneropedia
+entry: "Ring CT"
+terms: ["ringCT", "ring-CT"]
+summary: "a way to hide the amount sent in a Monero transaction"
+---
+
+### The Basics
+RingCT, short for Ring Confidential Transactions, is how transaction amounts are hidden in Monero.
+
+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.
+
+For more information, please read the creator Shen Noether's paper [here](https://eprint.iacr.org/2015/1098).
+
+
+{{ page.summary | capitalize }}.
+
+
+
+
+
+
diff --git a/_i18n/template/resources/moneropedia/ringsignatures.md b/_i18n/template/resources/moneropedia/ringsignatures.md
new file mode 100644
index 0000000000000000000000000000000000000000..fee368c89b6b6f1be32b1edf6213fdd1c56b75b3
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/ringsignatures.md
@@ -0,0 +1,18 @@
+---
+layout: moneropedia
+entry: "Ring Signature"
+terms: ["ring-signature", "ring-signatures"]
+summary: "a group of cryptographic signatures with at least one real participant, but no way to tell which in the group is the real one as they all appear valid"
+---
+
+### The Basics
+
+In cryptography, a ring signature is a type of digital signature that can be performed by any member of a group of users that each have keys. Therefore, a message signed with a ring signature is endorsed by someone in a particular group of people. One of the security properties of a ring signature is that it should be computationally infeasible to determine *which* of the group members' keys was used to produce the signature.
+
+For instance, a ring signature could be used to provide an anonymous signature from "a high-ranking White House official", without revealing which official signed the message. Ring signatures are right for this application because the anonymity of a ring signature cannot be revoked, and because the group for a ring signature can be improvised (requires no prior setup).
+
+### 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).
+
+To read how Monero gives you privacy by default (unlinkability), see @stealth-addresses.
\ No newline at end of file
diff --git a/_i18n/template/resources/moneropedia/router-info.md b/_i18n/template/resources/moneropedia/router-info.md
new file mode 100644
index 0000000000000000000000000000000000000000..f7c45c0608fb4337aa81a2d7f00fed97752387c1
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/router-info.md
@@ -0,0 +1,68 @@
+---
+layout: moneropedia
+entry: "Router-Info"
+tags: ["kovri"]
+terms: ["Router-Info", "Router-infos"]
+summary: "A data structure or file which contains an I2P peer's needed network information"
+---
+
+### The Basics
+
+@Router-Info is a data structure (periodically written to a [binary file](https://en.wikipedia.org/wiki/Binary_file)) which contains all needed information to locate, identify, and communicate with an @I2P peer. @Router-Info includes IP address, router identity, other misc. technical details; is needed for @network-database and is published to @floodfill routers.
+
+### In-depth information
+
+In human-readable form, Router-Info may look like this:
+
+```
+Identity: [RouterIdentity:
+Hash: nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=
+Certificate: [Certificate: type: Key certificate
+Crypto type: 0
+Sig type: 7 (EdDSA_SHA512_Ed25519)]
+PublicKey: [PublicKey: size: 256]
+SigningPublicKey: [SigningPublicKey EdDSA_SHA512_Ed25519: size: 32]
+Padding: 96 bytes]
+Signature: [Signature EdDSA_SHA512_Ed25519: size: 64]
+Published: Sun Oct 09 01:34:59 UTC 2016
+Options (5):
+ [caps] = [LfR]
+ [netId] = [2]
+ [netdb.knownLeaseSets] = [37]
+ [netdb.knownRouters] = [2435]
+ [router.version] = [0.9.26]
+Addresses (4):
+[RouterAddress:
+Type: SSU
+Cost: 4
+Options (5):
+ [caps] = [BC]
+ [host] = [2a01:e35:8b5c:b240:71a2:6750:8d4:47fa]
+ [key] = [nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=]
+ [mtu] = [1472]
+ [port] = [22244]]
+[RouterAddress:
+Type: NTCP
+Cost: 9
+Options (2):
+ [host] = [2a01:e35:8b5c:b240:71a2:6750:8d4:47fa]
+ [port] = [22244]]
+[RouterAddress:
+Type: SSU
+Cost: 6
+Options (4):
+ [caps] = [BC]
+ [host] = [88.181.203.36]
+ [key] = [nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=]
+ [port] = [22244]]
+[RouterAddress:
+Type: NTCP
+Cost: 11
+Options (2):
+ [host] = [88.181.203.36]
+ [port] = [22244]]]
+```
+
+### Notes
+
+For details and specification, visit @Java-I2P [Network Database](https://geti2p.net/en/docs/how/network-database) page.
diff --git a/_i18n/template/resources/moneropedia/scalability.md b/_i18n/template/resources/moneropedia/scalability.md
new file mode 100644
index 0000000000000000000000000000000000000000..efce0202090b89cfc7536cfbfe2e80286ff4209d
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/scalability.md
@@ -0,0 +1,10 @@
+---
+layout: moneropedia
+entry: "Scalability"
+terms: ["scalability"]
+summary: "Growth potential of Monero, resources required, and methods of increasing efficiency"
+---
+
+### The Basics
+
+Monero has no hardcoded maximum block size, which means that unlike Bitcoin it does not have a 1 MB block size limit preventing scaling. However, a block reward penalty mechanism is built into the protocol to avoid a too excessive block size increase: The new block's size (NBS) is compared to the median size M100 of the last 100 blocks. If NBS>M100, the block reward gets reduced in quadratic dependency of how much NBS exceeds M100. E.g. if NBS is [10%, 50%, 80%, 100%] greater than M100, the nominal block reward gets reduced by [1%, 25%, 64%, 100%]. Generally, blocks greater than 2*M100 are not allowed, and blocks <= 60kB are always free of any block reward penalties.
diff --git a/_i18n/template/resources/moneropedia/signature.md b/_i18n/template/resources/moneropedia/signature.md
new file mode 100644
index 0000000000000000000000000000000000000000..638b7c5bb26130703eead4b6f5585c6c18bef847
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/signature.md
@@ -0,0 +1,10 @@
+---
+layout: moneropedia
+entry: "Cryptographic Signature"
+terms: ["signature", "signatures"]
+summary: "a cryptographic method for proving ownership of a piece of information, as well as proving that the information has not been modified after being signed"
+---
+
+### The Basics
+
+{{ page.summary | capitalize }}.
\ No newline at end of file
diff --git a/_i18n/template/resources/moneropedia/smartmining.md b/_i18n/template/resources/moneropedia/smartmining.md
new file mode 100644
index 0000000000000000000000000000000000000000..c4f7a6d2e6af487b0dc8a7c205515539eb653f36
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/smartmining.md
@@ -0,0 +1,17 @@
+---
+layout: moneropedia
+entry: "Smart Mining"
+terms: ["smart-mining"]
+summary: "a process of having a throttled miner mine when it otherwise does not cause drawbacks"
+---
+
+### The Basics
+
+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/_i18n/template/resources/moneropedia/spendkey.md b/_i18n/template/resources/moneropedia/spendkey.md
new file mode 100644
index 0000000000000000000000000000000000000000..d57544d1ad9e636ad97f998ff3df4b66182fc39b
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/spendkey.md
@@ -0,0 +1,16 @@
+---
+layout: moneropedia
+entry: "Spend Key"
+terms: ["spend-key", "spend-keys"]
+summary: "one of the two pairs of private and public cryptographic keys that each account has, with the *private* spend key used to spend any funds in the account"
+---
+
+### The Basics
+
+{{ page.summary | capitalize }}.
+
+### In-depth Information
+
+The *private* spend key is a 256-bit integer that is used to sign Monero transactions. With the current deterministic key derivation method of the official wallet, the private spend key is also an alternate representation of the @mnemonic-seed. It can be used to derive all other account keys.
+
+
diff --git a/_i18n/template/resources/moneropedia/ssu.md b/_i18n/template/resources/moneropedia/ssu.md
new file mode 100644
index 0000000000000000000000000000000000000000..665f9c443a42ae39f281fb0b135145100c5a45c3
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/ssu.md
@@ -0,0 +1,26 @@
+---
+layout: moneropedia
+entry: "SSU"
+tags: ["kovri"]
+terms: ["SSU"]
+summary: "Secure Semi-reliable UDP: one of two Kovri transports"
+---
+
+### The Basics
+
+*Secure Semi-reliable UDP* is one of two encrypted @transports for @Kovri.
+
+Similar to @NTCP, @SSU's *primary* purpose is to securely transmit @in-net @I2NP messages through @tunnels but, unlike @NTCP, @SSU functions solely over encrypted [UDP](https://en.wikipedia.org/wiki/User_Datagram_Protocol).
+
+### In-depth information
+
+- Like @NTCP, @SSU is a connection-oriented, point-to-point data transport
+- Termed *semi-reliable* because @SSU will repeatedly retransmit *unacknowledged* messages (up to maximum number then dropped)
+- @SSU also provides several unique services (in addition to its function as a @transport layer):
+ - IP detection (local inspection or with [peer testing](https://geti2p.net/en/docs/transport/ssu#peerTesting))
+ - [NAT](https://en.wikipedia.org/wiki/Network_address_translation) traversal (using [introducers](https://geti2p.net/en/docs/transport/ssu#introduction))
+ - [Firewall](https://en.wikipedia.org/wiki/Firewall_%28computing%29) status and, if implemented, @SSU can notify @NTCP if the external address or firewall status changes
+
+### Notes
+
+For further details, read @Java-I2P's [SSU](https://geti2p.net/en/docs/transport/ssu)
diff --git a/_i18n/template/resources/moneropedia/stealthaddress.md b/_i18n/template/resources/moneropedia/stealthaddress.md
new file mode 100644
index 0000000000000000000000000000000000000000..61892d1b23c3bb0cb7d751f8191bccfab9ba90aa
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/stealthaddress.md
@@ -0,0 +1,16 @@
+---
+layout: moneropedia
+entry: "Stealth Address"
+terms: ["stealth-address", "stealth-addresses"]
+summary: "automatic one-time addresses for every transaction"
+---
+
+### The Basics
+
+Stealth addresses are an important part of Monero's inherent privacy. They allow and require the sender to create random one-time addresses for every @transaction on behalf of the recipient. The recipient can publish just one address, yet have all of his/her incoming payments go to unique addresses on the @blockchain, where they cannot be linked back to either the recipient's published address or any other transactions' addresses. By using stealth addresses, only the sender and receiver can determine where a payment was sent.
+
+When you create a Monero account you’ll have a private @view-key, a private @spend-key, and a Public Address. The @spend-key is used to send payments, the @view-key is used to display incoming transactions destined for your account, and the Public Address is for receiving payments. Both the @spend-key and @view-key are used to build your Monero address. You can have a “watch only†wallet that only uses the @view-key. This feature can be used for accounting or auditing purposes but is currently unreliable due to the inability to track outgoing transactions. You can decide who can see your Monero balance by sharing your @view-key. Monero is private by default and optionally semi-transparent!
+
+When using the Monero Wallet all this is handled by the software. Sending Monero is as easy as entering the destination address, the amount, and pressing Send. To recieve Monero, simply provide the sender your Public Address.
+
+To learn how Monero prevents tracking history (untraceability), see @ring-signatures.
diff --git a/_i18n/template/resources/moneropedia/subscription.md b/_i18n/template/resources/moneropedia/subscription.md
new file mode 100644
index 0000000000000000000000000000000000000000..b7411df5bec058a8baae7346e610cfe1f307501f
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/subscription.md
@@ -0,0 +1,47 @@
+---
+layout: moneropedia
+entry: "Subscription"
+tags: ["kovri"]
+terms: ["Subscription"]
+summary: "A file used by address book which contains I2P hosts paired with I2P destinations"
+---
+
+### The Basics
+
+A subscription is a file which contains a list of `.i2p` hosts paired with their respective @destination. Subscriptions are used by the @address-book.
+
+### 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`
+
+More specifically, a subscription pairs a @locally-unique-host to @base64-address.
+
+Example:
+
+```
+anonimal.i2p=AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLEov~usVliTSXCSHuRBOCIwIOuDNU0AbVa4BpIx~2sU4TxKhoaA3zQ6VzINoduTdR2IJhPvI5xzezp7dR21CEQGGTbenDslXeQ4iLHFA2~bzp1f7etSl9T2W9RID-KH78sRQmzWnv7dbhNodMbpO6xsf1vENf6bMRzqD5vgHEHZu2aSoNuPyYxDU1eM6--61b2xp9mt1k3ud-5WvPVg89RaU9ugU5cxaHgR927lHMCAEU2Ax~zUb3DbrvgQBOTHnJEx2Fp7pOK~PnP6ylkYKQMfLROosLDXinxOoSKP0UYCh2WgIUPwE7WzJH3PiJVF0~WZ1dZ9mg00c~gzLgmkOxe1NpFRNg6XzoARivNVB5NuWqNxr5WKWMLBGQ9YHvHO1OHhUJTowb9X90BhtHnLK2AHwO6fV-iHWxRJyDabhSMj1kuYpVUBQAEAAcAAA==
+```
+
+1. `anonimal.i2p` is the @locally-unique-host
+2. `=` is the separator
+3. Everything that remains is the @base64-address
+
+### Subscription types
+
+For @Kovri, there are two types of subscription files: *public* and *private*.
+
+A *public* subscription:
+- is used when bootstrapping to use essential services (IRC, email, Monero, etc.)
+- is static and is refreshed every 12 hours from Monero's @address-book server
+- allows you to safely share the subscription with everyone as it is publically available (anyone who shares the same public subscription will also be able to resolve the same hostname to the same destination as you)
+
+A *private* subscription:
+- is used exclusively by you and is not shared with others unless you explicitly choose to share the file
+- default file is `private_hosts.txt` in your @data-directory
+
+### Updating a private subscription
+
+You can use a @jump-service to manually update your private subscription. The updated subscription will then be fed into the @address-book for you to use.
+
+### Notes
+To learn how to subscribe to multiple subscriptions, see the [user-guide](https://github.com/monero-project/kovri/blob/master/doc/USER_GUIDE.md).
diff --git a/_i18n/template/resources/moneropedia/tail-emission.md b/_i18n/template/resources/moneropedia/tail-emission.md
new file mode 100644
index 0000000000000000000000000000000000000000..019e6fe14fef7e3ea22c02c1a9c995d7b3aa45a7
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/tail-emission.md
@@ -0,0 +1,16 @@
+---
+layout: moneropedia
+entry: "Tail Emission"
+terms: ["Tail-Emission"]
+summary: "the block reward at the end of the emission curve"
+---
+
+### The Basics
+
+Monero block rewards will never drop to zero. Block rewards will gradually drop until tail emission commences at the end of May 2022. At this point, rewards will be fixed at 0.6 XMR per block.
+
+### 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.
+
+Tail emission ensures that a dynamic block size and fee market can develop.
diff --git a/_i18n/template/resources/moneropedia/transaction.md b/_i18n/template/resources/moneropedia/transaction.md
new file mode 100644
index 0000000000000000000000000000000000000000..0064cb50bc7ead40d1fbfc398545cd6b8e1ccbf0
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/transaction.md
@@ -0,0 +1,21 @@
+---
+layout: moneropedia
+entry: "Transactions"
+terms: ["transaction", "transactions"]
+summary: "a cryptographically signed container that details the transfer of Monero to a recipient (or recipients)"
+---
+
+### The Basics
+
+{{ 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.
+
+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).
+
+### In-depth Information
+Every transaction involves two keys: a public @spend-key, and a public @view-key. The destination for an output in a transaction is actually a one-time public key computed from these two keys.
+
+When a wallet is scanning for incoming transactions, every transaction is scanned to see if it is for "you". This only requires your private view key and your public spend key, and this check is immutable and cannot be faked. You cannot receive transactions and identify them without a corresponding private view key.
+
+In order to spend the funds you have to compute a one-time private spend key for that output. This is almost always done automatically by the Monero Wallet software.
diff --git a/_i18n/template/resources/moneropedia/transports.md b/_i18n/template/resources/moneropedia/transports.md
new file mode 100644
index 0000000000000000000000000000000000000000..59504f99c58bc7205dd3283870de2f26f7205494
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/transports.md
@@ -0,0 +1,20 @@
+---
+layout: moneropedia
+entry: "Transports"
+tags: ["kovri"]
+terms: ["Transports", "Transport"]
+summary: "The two encrypted transport layers for Kovri"
+---
+
+### The Basics
+
+@I2P comes with two encrypted transport layer technologies that allow @Kovri to securely use [TCP/IP](https://en.wikipedia.org/wiki/Tcp/ip) connections. These technologies (@SSU and @NTCP) are called *@transports*.
+
+### In-depth information
+
+@SSU is encrypted [UDP](https://en.wikipedia.org/wiki/User_Datagram_Protocol) and @NTCP is encrypted [TCP](https://en.wikipedia.org/wiki/Transmission_Control_Protocol). They provide @encryption at the [transport layer](https://en.wikipedia.org/wiki/Transport_layer) so higher level @messages can be sent through @tunnels across the @I2P network.
+
+### Notes
+
+- Read about @I2P's transports on the [Transport](https://geti2p.net/en/docs/transport) page
+- Read about the transports layer within the [OSI model](https://en.wikipedia.org/wiki/OSI_model)
diff --git a/_i18n/template/resources/moneropedia/tunnel.md b/_i18n/template/resources/moneropedia/tunnel.md
new file mode 100644
index 0000000000000000000000000000000000000000..d22e2b944ab72596fe894d41a941b6c2f5f9d85e
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/tunnel.md
@@ -0,0 +1,37 @@
+---
+layout: moneropedia
+entry: "Tunnel"
+tags: ["kovri"]
+terms: ["Tunnel", "Tunnels"]
+summary: "Uni-directional virtual paths that pass messages through a defined sequence of I2P routers"
+---
+
+### The Basics
+
+When you communicate over @I2P (visit an @eepsite / use a @garlic-service), you'll first need to connect to a peer by using @transports and then build virtual *tunnels*. These virtual tunnels are temporary, uni-directional paths that pass information through a defined sequence of @I2P routers to your @destination. Tunnels are built, and then used, with layered @garlic-encryption and are a general-purpose mechanism to transport all @I2NP @messages.
+
+Each peer builds, at a minimum, *two* uni-directional tunnels: one for **outbound traffic**, and one for **inbound traffic**. These tunnels are classified as either **inbound tunnels** (where @messages come toward the creator of the tunnel) or **outbound tunnels** (where the tunnel creator sends @messages away from the creator of the tunnel). Thus, *four* tunnels are required for a single round-trip @message and reply to your @destination (two for your, two for your destination).
+
+### In-depth information
+
+From @Java-I2P:
+
+>
+Within I2P, @messages are passed in one direction through a virtual tunnel of peers, using whatever means are available to pass the @message on to the next hop. Messages arrive at the tunnel's gateway, get bundled up and/or fragmented into fixed-size @tunnel @messages, and are forwarded on to the next hop in the tunnel, which processes and verifies the validity of the @message and sends it on to the next hop, and so on, until it reaches the @tunnel endpoint. That endpoint takes the messages bundled up by the gateway and forwards them as instructed - either to another router, to another tunnel on another router, or locally.
+
+>
+Tunnels all work the same, but can be segmented into two different groups - inbound tunnels and outbound tunnels. The inbound tunnels have an untrusted gateway which passes messages down towards the tunnel creator, which serves as the tunnel endpoint. For outbound tunnels, the tunnel creator serves as the gateway, passing messages out to the remote endpoint.
+
+>
+The tunnel's creator selects exactly which peers will participate in the tunnel, and provides each with the necessary configuration data. They may have any number of hops. It is the intent to make it hard for either participants or third parties to determine the length of a tunnel, or even for colluding participants to determine whether they are a part of the same tunnel at all (barring the situation where colluding peers are next to each other in the tunnel).
+
+### Notes
+
+From @Java-I2P:
+
+>
+@I2P is an inherently packet switched network, even with these tunnels, allowing it to take advantage of multiple tunnels running in parallel, increasing resilience and balancing load. Even though the tunnels within I2P bear a resemblance to a circuit switched network, everything within I2P is strictly message based - tunnels are merely accounting tricks to help organize the delivery of messages. No assumptions are made regarding reliability or ordering of messages, and retransmissions are left to higher levels (e.g. I2P's client layer streaming library).
+
+### Documentation
+
+For specification and detailed documentation, visit the [Tunnel-Routing](https://geti2p.net/en/docs/how/tunnel-routing) and [Tunnel-Implementation](https://geti2p.net/en/docs/tunnels/implementation) page.
diff --git a/_i18n/template/resources/moneropedia/unlocktime.md b/_i18n/template/resources/moneropedia/unlocktime.md
new file mode 100644
index 0000000000000000000000000000000000000000..08a35f8e0025aa2f825b7f931b04707b8eba7818
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/unlocktime.md
@@ -0,0 +1,14 @@
+---
+layout: moneropedia
+entry: "Transaction Unlock Time"
+terms: ["unlock-time"]
+summary: "a special transaction where the recipient can only spend the funds after a future date, as set by the sender"
+---
+
+### The Basics
+
+{{ page.summary | capitalize }}.
+
+Unlock time allows you to send a transaction to someone, such that they can not spend it until after a certain number of blocks, or until a certain time.
+
+Note that this works differently than Bitcoin's [nLockTime](https://en.bitcoin.it/wiki/NLockTime), in which the transaction is not valid until the given time.
diff --git a/_i18n/template/resources/moneropedia/viewkey.md b/_i18n/template/resources/moneropedia/viewkey.md
new file mode 100644
index 0000000000000000000000000000000000000000..719a96b9943755f98cd661bacc25147cdd3a8957
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/viewkey.md
@@ -0,0 +1,16 @@
+---
+layout: moneropedia
+entry: "View Key"
+terms: ["view-key", "view-keys"]
+summary: "one of two sets of private and public cryptographic keys that each account has, with the private view key required to view all transactions related to the account"
+---
+
+### 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 }}.
diff --git a/_i18n/template/resources/moneropedia/wallet.md b/_i18n/template/resources/moneropedia/wallet.md
new file mode 100644
index 0000000000000000000000000000000000000000..759b018d3d36a750800687d1e14266927a77092f
--- /dev/null
+++ b/_i18n/template/resources/moneropedia/wallet.md
@@ -0,0 +1,19 @@
+---
+layout: moneropedia
+entry: "Wallet"
+terms: ["wallet", "wallets"]
+summary: "A wallet stores the information necessary to send and receive Monero"
+---
+
+### The Basics
+
+A Monero account, or wallet, stores the information necessary to send and receive Moneroj. In addition to sending and receiving, the Monero Wallet software keeps a private history of your transactions and allows you to cryptographically sign messages. It also includes Monero mining software and an address book.
+
+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 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.
+
+Monero accounts and paper-wallets can be stored on any media - paper, USB drive, CD/DVD, or a hardware wallet device (none available for Monero as of June 2017).
+
diff --git a/_i18n/template/resources/research-lab.md b/_i18n/template/resources/research-lab.md
new file mode 100644
index 0000000000000000000000000000000000000000..61b4617ce4512e40cdf792e9f6c693a72a24f31c
--- /dev/null
+++ b/_i18n/template/resources/research-lab.md
@@ -0,0 +1,164 @@
+{% include untranslated.html %}
+<div class="container description">
+<p>Monero is not only committed to making a fungible currency, but also to continued research into the realm of financial privacy as it involves cryptocurrencies. Below you'll find the work of our very own Monero Research Lab, with more papers to come.</p>
+</div>
+
+<section class="container">
+ <div class="row">
+ <!-- left two-thirds block-->
+ <div class="left two-thirds col-lg-8 col-md-8 col-sm-12 col-xs-12">
+ <div class="info-block research-paper">
+ <div class="row center-xs">
+ <div class="col"><h2>Monero Research Lab Papers</h2></div>
+ </div>
+ <div class="tab">
+ <input id="tab-one" type="checkbox" name="tabs" class="accordion" checked="checked">
+ <label for="tab-one" class="accordion">MRL-0001: A Note on Chain Reactions in Traceability in CryptoNote 2.0</label>
+ <div class="tab-content">
+ <p><strong>Abstract:</strong> This research bulletin describes a plausible attack on a ring-signature based
+ anonymity system. We use as motivation the cryptocurrency protocol CryptoNote
+ 2.0 ostensibly published by Nicolas van Saberhagen in 2012. It has been
+ previously demonstrated that the untraceability obscuring a one-time key pair can
+ be dependent upon the untraceability of all of the keys used in composing that
+ ring signature. This allows for the possibility of chain reactions in traceability
+ between ring signatures, causing a critical loss in untraceability across the whole
+ network if parameters are poorly chosen and if an attacker owns a sufficient
+ percentage of the network. The signatures are still one-time, however, and any
+ such attack will still not necessarily violate the anonymity of users. However, such
+ an attack could plausibly weaken the resistance CryptoNote demonstrates against
+ blockchain analysis. This research bulletin has not undergone peer review, and
+ reflects only the results of internal investigation.
+ <br>
+ <br>
+ <a target="_blank" rel="noreferrer noopener" href="https://lab.getmonero.org/pubs/MRL-0001.pdf">Read Paper</a>
+ </p>
+ </div>
+ </div>
+ <div class="tab">
+ <input id="tab-two" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-two" class="accordion">MRL-0002: Counterfeiting via Merkle Tree Exploits within Virtual Currencies Employing the CryptoNote Protocol</label>
+ <div class="tab-content">
+ <p><strong>Abstract:</strong> On 4 September 2014, an unusual and novel attack was executed against the
+ Monero cryptocurrency network. This attack partitioned the network into two
+ distinct subsets which refused to accept the legitimacy of the other subset. This
+ had myriad effects, not all of which are yet known. The attacker had a short
+ window of time during which a sort of counterfeiting could occur, for example.
+ This research bulletin describes deficiencies in the CryptoNote reference code
+ allowing for this attack, describes the solution initially put forth by Rafal Freeman
+ from Tigusoft.pl and subsequently by the CryptoNote team, describes the current
+ fix in the Monero code base, and elaborates upon exactly what the offending
+ block did to the network. This research bulletin has not undergone peer review,
+ and reflects only the results of internal investigation.<br>
+ <br>
+ <a target="_blank" rel="noreferrer noopener" href="https://lab.getmonero.org/pubs/MRL-0002.pdf">Read Paper</a></p>
+
+ </div>
+ </div>
+ <div class="tab">
+ <input id="tab-three" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-three" class="accordion">MRL-0003: Monero is Not That Mysterious</label>
+ <div class="tab-content">
+ <p><strong>Introduction:</strong> Recently, there have been some vague fears about the CryptoNote source code and
+ protocol floating around the internet based on the fact that it is a more complicated
+ protocol than, for instance, Bitcoin. The purpose of this note is to try and clear
+ up some misconceptions, and hopefully remove some of the mystery surrounding
+ Monero Ring Signatures. I will start by comparing the mathematics involved in
+ CryptoNote ring signatures (as described in [CN]) to the mathematics in [FS], on
+ which CryptoNote is based. After this, I will compare the mathematics of the ring
+ signature to what is actually in the CryptoNote codebase.<br>
+ <br>
+ <a target="_blank" rel="noreferrer noopener" href="https://lab.getmonero.org/pubs/MRL-0003.pdf">Read Paper</a></p>
+ </div>
+ </div>
+ <div class="tab">
+ <input id="tab-four" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-four" class="accordion">MRL-0004: Improving Obfuscation in the CryptoNote Protocol</label>
+ <div class="tab-content">
+ <p><strong>Abstract:</strong> We identify several blockchain analysis attacks available to degrade the
+untraceability of the CryptoNote 2.0 protocol. We analyze possible solutions,
+discuss the relative merits and drawbacks to those solutions, and recommend
+improvements to the Monero protocol that will hopefully provide long-term
+resistance of the cryptocurrency against blockchain analysis. Our recommended
+improvements to Monero include a protocol-level network-wide minimum mix-in
+policy of
+n
+= 2
+foreign outputs per ring signature, a protocol-level increase of this
+value to
+n
+= 4
+after two years, and a wallet-level default value of
+n
+= 4
+in the
+interim. We also recommend a torrent-style method of sending Monero output.
+We also discuss a non-uniform, age-dependent mix-in selection method to
+mitigate the other forms of blockchain analysis identified herein, but we make no
+formal recommendations on implementation for a variety of reasons. The
+ramifications following these improvements are also discussed in some detail.
+This research bulletin has not undergone peer review, and reflects only the
+results of internal investigation.<br>
+ <br>
+ <a target="_blank" rel="noreferrer noopener" href="https://lab.getmonero.org/pubs/MRL-0004.pdf">Read Paper</a></p>
+ </div>
+ </div>
+ <div class="tab">
+ <input id="tab-five" type="checkbox" name="tabs" class="accordion">
+ <label for="tab-five" class="accordion">MRL-0005: Ring Signature Confidential Transactions</label>
+ <div class="tab-content">
+ <p><strong>Abstract:</strong> This article introduces a method of hiding transaction amounts in the strongly
+decentralized anonymous cryptocurrency Monero. Similar to Bitcoin, Monero is a
+cryptocurrency which is distributed through a proof of work “mining†process.
+The original Monero protocol was based on CryptoNote, which uses ring
+signatures and one-time keys to hide the destination and origin of transactions.
+Recently the technique of using a commitment scheme to hide the amount of a
+transaction has been discussed and implemented by Bitcoin Core Developer
+Gregory Maxwell. In this article, a new type of ring signature, A Multi-layered
+Linkable Spontaneous Anonymous Group signature is described which allows for
+hidden amounts, origins and destinations of transactions with reasonable
+efficiency and verifiable, trustless coin generation. Some extensions of the
+protocol are provided, such as Aggregate Schnorr Range Proofs, and Ring
+Multisignature. The author would like to note that early drafts of this were
+publicized in the Monero Community and on the bitcoin research irc channel.
+Blockchain hashed drafts are available in [14] showing that this work was started
+in Summer 2015, and completed in early October 2015. An eprint is also
+available at
+http://eprint.iacr.org/2015/1098
+.<br>
+ <br>
+ <a href="https://lab.getmonero.org/pubs/MRL-0005.pdf" target="_blank" rel="noreferrer noopener">Read Paper</a></p>
+ </div>
+ </div>
+ </div>
+ </div>
+ <!-- end left two-thirds block-->
+
+ <!-- right one-third block-->
+ <div class="right one-third col-lg-4 col-md-4 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Cryptonote Whitepapers</h2>
+ </div>
+
+ </div>
+<div markdown="1">
+
+[Cryptonote Whitepaper](https://cryptonote.org/whitepaper.pdf)
+
+This is the original cryptonote paper written by the cryptonote team. Reading it will give an understanding about how the cryptonote algorithm works in general.
+
+[Annotated Whitepaper](https://downloads.getmonero.org/whitepaper_annotated.pdf)
+
+The Monero Research Lab released an annotated version of the cryptonote whitepaper. This is sort of like an informal review of the claims that are made line-by-line of the whitepaper. It also explains some of the harder concepts in relatively easy to understand terms.
+
+[Brandon Goodell's Whitepaper Review](https://downloads.getmonero.org/whitepaper_review.pdf)
+
+This paper is a formal review of the original cryptonote paper by MRL researcher Brandon Goodell. He takes an in-depth look at the claims and mathematics presented in the cryptonote paper.
+
+</div>
+ </div>
+ </div>
+ <!-- end right one-third block-->
+ </div>
+</section>
diff --git a/_i18n/template/resources/roadmap.md b/_i18n/template/resources/roadmap.md
new file mode 100644
index 0000000000000000000000000000000000000000..267b386742f187ac792183bc1c7cb44c946f8421
--- /dev/null
+++ b/_i18n/template/resources/roadmap.md
@@ -0,0 +1,130 @@
+{% include untranslated.html %}
+<div class="roadmap">
+<div class="text-center pre-roadmap container">
+ <div class="row">
+ <div class="col-xs-4">
+ <li class="completed"></li>
+ <p>Completed task</p>
+ </div>
+ <div class="col-xs-4">
+ <li class="ongoing"></li>
+ <p>Ongoing task</p>
+ </div>
+ <div class="col-xs-4">
+ <li class="upcoming"></li>
+ <p>Upcoming task</p>
+ </div>
+ </div>
+</div>
+<section class="container">
+ <div class="row">
+ <div class="col-lg-12 col-md-12 col-sm-12 col-xs-12">
+ <div class="tabPanel-widget">
+ <label for="tab-1" tabindex="0"></label>
+ <input id="tab-1" type="radio" name="tabs" aria-hidden="true">
+ <h2>2014</h2>
+ <div class="tabPanel-content">
+ {% for toplevel in site.data.lang[site.lang].roadmap %}
+ {% if toplevel.year == 2014 %}
+ {% for roadlist in toplevel.accomplishments %}
+ <div class="row start-xs middle-xs">
+ <div class="col-xs-1">
+ <span class="{{roadlist.status}}"></span>
+ </div>
+ <div class="col-xs-11">
+ <p>{{roadlist.date}}: {{roadlist.name}}</p>
+ </div>
+ </div>
+ {%endfor%}
+ {%endif%}
+ {%endfor%}
+ </div>
+ <label for="tab-2" tabindex="0"></label>
+ <input id="tab-2" type="radio" name="tabs" aria-hidden="true">
+ <h2>2015</h2>
+ <div class="tabPanel-content">
+ {% for toplevel in site.data.lang[site.lang].roadmap %}
+ {% if toplevel.year == 2015 %}
+ {% for roadlist in toplevel.accomplishments %}
+ <div class="row start-xs middle-xs">
+ <div class="col-xs-1">
+ <span class="{{roadlist.status}}"></span>
+ </div>
+ <div class="col-xs-11">
+ <p>{{roadlist.date}}: {{roadlist.name}}</p>
+ </div>
+ </div>
+ {%endfor%}
+ {%endif%}
+ {%endfor%}
+ </div>
+ <label for="tab-3" tabindex="0"></label>
+ <input id="tab-3" type="radio" name="tabs" aria-hidden="true">
+ <h2>2016</h2>
+ <div class="tabPanel-content">
+ {% for toplevel in site.data.lang[site.lang].roadmap %}
+ {% if toplevel.year == 2016 %}
+ {% for roadlist in toplevel.accomplishments %}
+ <div class="row start-xs middle-xs">
+ <div class="col-xs-1">
+ <span class="{{roadlist.status}}"></span>
+ </div>
+ <div class="col-xs-11">
+ <p>{{roadlist.date}}: {{roadlist.name}}</p>
+ </div>
+ </div>
+ {%endfor%}
+ {%endif%}
+ {%endfor%}
+ </div>
+ <label for="tab-4" tabindex="0"></label>
+ <input id="tab-4" type="radio" name="tabs" aria-hidden="true" checked>
+ <h2>2017</h2>
+ <div class="tabPanel-content">
+ {% for toplevel in site.data.lang[site.lang].roadmap %}
+ {% if toplevel.year == 2017 %}
+ {% for roadlist in toplevel.accomplishments %}
+ <div class="row start-xs middle-xs">
+ <div class="col-xs-1">
+ <span class="{{roadlist.status}}"></span>
+ </div>
+ <div class="col-xs-11">
+ {% if roadlist.date %}
+ <p>{{roadlist.date}}: {{roadlist.name}}</p>
+ {%else%}
+ <p>{{roadlist.name}}</p>
+ {%endif%}
+ </div>
+ </div>
+ {%endfor%}
+ {%endif%}
+ {%endfor%}
+ </div>
+ <label for="tab-5" tabindex="0"></label>
+ <input id="tab-5" type="radio" name="tabs" aria-hidden="true">
+ <h2>Future</h2>
+ <div class="tabPanel-content">
+ {% for toplevel in site.data.lang[site.lang].roadmap %}
+ {% if toplevel.year == 2018 %}
+ {% for roadlist in toplevel.accomplishments %}
+ <div class="row start-xs">
+ <div class="col-xs-1">
+ <span class="{{roadlist.status}}"></span>
+ </div>
+ <div class="col-xs-11">
+ {% if roadlist.date %}
+ <p>{{roadlist.date}}: {{roadlist.name}}</p>
+ {%else%}
+ <p>{{roadlist.name}}</p>
+ {%endif%}
+ </div>
+ </div>
+ {%endfor%}
+ {%endif%}
+ {%endfor%}
+ </div>
+ </div>
+ </div>
+ </div>
+</section>
+</div>
\ No newline at end of file
diff --git a/_i18n/template/resources/user-guides/How-to-mine-Monero-XMR-without-a-mining-equipment.md b/_i18n/template/resources/user-guides/How-to-mine-Monero-XMR-without-a-mining-equipment.md
new file mode 100644
index 0000000000000000000000000000000000000000..ca382b6a892a0e411a687fba4d3373b0ed274b98
--- /dev/null
+++ b/_i18n/template/resources/user-guides/How-to-mine-Monero-XMR-without-a-mining-equipment.md
@@ -0,0 +1,49 @@
+{% include untranslated.html %}
+## How to mine Monero (XMR) without a mining equipment?
+
+If you don’t have a profitable mining equipment, nor time or
+money to invest into building it, you can still mine Monero with NiceHash.
+
+NiceHash is a hashing power marketplace. Sellers of hashing
+power, i.e. miners, provide the hashing power for buyers (those who want to buy
+a service of mining a certain coin). Hence, NiceHash can provide you a massive
+hashing power in short amount of time. You won’t have to wait for years to see
+if you will make a profit or not and you can control which coin, at which pool,
+and for how long you want to mine.
+
+### **Step 1:** Create new account at NiceHash
+
+Visit [registration
+page](https://www.nicehash.com/?p=register) and register with your e-mail address.
+
+### **Step 2:** Deposit some Bitcoins to your account
+
+You will mine Monero, but you can buy hashing power at
+NiceHash only with Bitcoins. You can always withdraw unspent Bitcoins from your
+account back to any Bitcoin wallet.
+
+Visit your [wallet
+page](https://www.nicehash.com/?p=wallet) and make a deposit. Note that the minimum price for placing an order
+equals 0.01 BTC.
+
+### **Step 3:** Find a suitable pool for mining and add it to your pool list
+
+Selection of the pool plays a big role in the final amount
+of mined cryptocurrency. Make sure the pool you have selected can handle
+massive hashing rate and loads of shares, especially from a single connection.
+You can find a list of Monero pools [here](https://bitcointalk.org/index.php?topic=583449.0).
+
+Note that you will probably have to register an account at
+selected pool as well. The pool will provide you with all the information you need.
+You can save your favorite pools at [this page](https://www.nicehash.com/?p=managepools).
+
+### **Step 4:** Create new order and start mining
+
+When creating a [new order](https://www.nicehash.com/?p=orders&new), make sure you
+select CryptoNight algorithm for mining Monero. If you want to first learn more
+about placing an order with NiceHash, we recommend you to read this [frequently asked question](https://www.nicehash.com/?p=faq#faqb0).
+
+If you want to bid on
+hashing power select Standard (bidding) order type and if you want a fixed
+order that cannot be outbid, select Fixed order type. The status of marketplace
+and approximate prices of mining can be checked at [live marketplace](https://www.nicehash.com/index.jsp?p=orders).Â
\ No newline at end of file
diff --git a/_i18n/template/resources/user-guides/Offline_Backup.md b/_i18n/template/resources/user-guides/Offline_Backup.md
new file mode 100644
index 0000000000000000000000000000000000000000..089d20fc0c65105b1b6ed0f904e95cb6d8d3df1a
--- /dev/null
+++ b/_i18n/template/resources/user-guides/Offline_Backup.md
@@ -0,0 +1,37 @@
+{% include untranslated.html %}
+## Operating Systems: Various versions of Linux and Windows 7, 8
+
+### Wallet Software: Simplewallet
+
+#### Resource for Creating Bootable Disks: [Linux](http://www.pendrivelinux.com/), [Windows](https://www.microsoft.com/en-us/download/windows-usb-dvd-download-tool)
+
+#### Resource for Monero Binaries: [Monero Binaries](https://getmonero.org/downloads/)
+
+- Take any computer you have lying around, even your normal workstation. You may find it easier to use an older computer that has no wifi or bluetooth if you're particularly paranoid
+
+- Create a Linux or Windows bootable disk, and make sure you have the Monero binaries on the same disk or on a second disk (for Linux make sure you have also downloaded copies of the dependencies you will need, libboost1.55 and miniupnpc for instance)
+
+- Disconnect the network and/or Internet cables from your computer, physically remove the wifi card or switch the wifi/bluetooth off on a laptop if possible
+
+- Boot into your bootable OS, install the dependencies if necessary
+
+- Copy the Monero binaries to a RAM disk (/dev/shm in Linux, Windows bootable ISOs normally have a Z: drive or something)
+
+- Don't run the Monero daemon. Instead, using the command line, use monero-wallet-cli to create a new Monero @account
+
+- When prompted for a name, give it any name, it doesn't really matter
+
+- When prompted for a password, type in like 50 - 100 random characters. Don't worry that you don't know the password, just make it LONG
+
+- **CRITICAL STEP**: Write down (on paper) your 25 word @mnemonic-seed
+**WARNING**: If you forget to write down this information your funds may be lost forever
+
+- Write down (on your phone, on paper, on another computer, wherever you want) your address and view key
+
+- Switch off the computer, remove the battery if there is one, and leave it physically off for a few hours
+
+The account you've created was created in RAM, and the digital files are now inaccessible. If some adversary manages to somehow obtain the data, they will lack the long password to open it. If you need to receive payments, you have your public address, and you have the view key if needed. If you need access to it, you have your 25 word @mnemonic-seed, and you can now write out several copies of it, including an offsite copy (e.g. a bank deposit box).
+
+Credit: Riccardo Spagni
+
+Related: [Offline Account Generator](http://moneroaddress.org/)
diff --git a/_i18n/template/resources/user-guides/create_wallet.md b/_i18n/template/resources/user-guides/create_wallet.md
new file mode 100644
index 0000000000000000000000000000000000000000..8386529ef68d9043717b909989a0b62590bb04bb
--- /dev/null
+++ b/_i18n/template/resources/user-guides/create_wallet.md
@@ -0,0 +1,61 @@
+{% include untranslated.html %}
+### Operating Systems: Ubuntu
+
+- Download the [official binaries](https://getmonero.org/downloads/) or compile the last source available on [Github](https://github.com/monero-project/bitmonero)
+
+
+
+
+- Extract the files with the archive manager (same as Winzip on Windows). Note the path where the files "monerod" and "monero-wallet-cli" are
+
+
+
+
+- You only need to do this step once : open a terminal (ctrl+alt+t) and install the required dependencies by typing : "*sudo apt-get install libboost-all-dev libssl-dev libevent-dev libdb++-dev*". When asked, press the Y key and then Enter to continue
+
+
+
+
+- Open a terminal and load the path where your binaries are extracted (cf. step 2) by typing : "*cd yourPathFromStep2*"
+
+
+
+- Load monerod by typing in your terminal : "*./monerod*". Wait for the synchronization with the network (monerod is updating the blockchain you have downloaded in step 4 or is downloading it from scratch). This can take a lot of time the first time, so be patient
+
+
+
+
+
+
+- Once monerod is synchronized with the network, open a new terminal, change the directory (cf. step 5), and launch monero-wallet-cli by typing "*./monero-wallet-cli*"
+
+
+
+- Enter the name you want for your portfolio and follow the instructions from the terminal
+
+
+
+
+
+
+*This is your private key. Write it down and keep it in a safe place!*
+
+
+
+*This is your view key. You need it to create a view only wallet (cf. associated user guide)*
+
+
+
+*This is the address of your wallet*
+
+
+
+
+
+
+
+- To exit monerod or monero-wallet-cli just type "*exit*" in the associated terminal
+
+Now to access the portfolio you have just created you will have to launch monerod, wait for it to be synchronized with the network, launch monero-wallet-cli, and type the name of your portfolio and your password.
+
+
diff --git a/_i18n/template/resources/user-guides/easiest_buy.md b/_i18n/template/resources/user-guides/easiest_buy.md
new file mode 100644
index 0000000000000000000000000000000000000000..4b360c5a4b5e138c7e0d1f6200805c9aab90e26b
--- /dev/null
+++ b/_i18n/template/resources/user-guides/easiest_buy.md
@@ -0,0 +1,65 @@
+{% include untranslated.html %}
+## How to obtain Monero
+
+This is a guide to obtain your own Monero as of 20150919. This is perhaps the easiest way to purchase and hold Monero.
+
+####Step 1: Buy Bitcoin
+
+There are many ways to buy Bitcoin. Perhaps the easiest way is through circle.com. Once you have purchased some Bitcoin, you are ready to buy some Monero! Buying Bitcoin is straightforward. Please goto circle.com and just follow the instructions there.
+
+####Step 2: Set up a mymonero.com account
+
+MyMonero.com is an online wallet for Monero, maintained by Monero Core Developer Ricardo Spagni (fluffpony). It is the easiest wallet to use. Simply go to MyMonero.com and click on the "Create an Account" button.
+
+
+
+After clicking the button, you will see your private key. This key is what gives you access to your funds. Never share this key with anyone!
+
+### WRITE DOWN THIS KEY IMMEDIATELY!
+
+
+
+Type in your private key in the box below, and click the button.
+
+On the next page, you will see your address.
+
+
+
+Copy your address to the clipboard by highlighting the whole thing and hitting ctrl+c (or edit menu, copy), or clicking the little icon next to your address. Save your address somewhere. This is how others will send Monero to you, and what you will use to deposit Monero into your account!
+
+#### Step 3: Buy Monero and transfer the Monero to your new address
+
+Go to www.shapeshift.io . On the righthand side, of the screen, click icon under "Receive" to select Monero.
+
+
+
+
+Paste your address into the field under the Monero logo. Select the "agree to terms" button, then hit "Start"
+
+
+
+In the new screen that pops up, copy the Deposit Address into your clipboard (select and hit ctrl+c or edit-copy)
+
+
+
+Go back to your circle.com page, hit the "transfer" button, and paste the Bitcoin address into the field
+Enter the amount of Bitcoin you would like to spend.
+
+
+
+
+You will get a text message verification code. Enter code and hit send.
+
+
+
+You will see the shapeshift change to "awaiting exchange"
+
+
+
+Then it will change to COMPLETE!
+
+
+
+After a while you will see it in your Monero account
+
+
diff --git a/_i18n/template/resources/user-guides/howto_fix_stuck_funds.md b/_i18n/template/resources/user-guides/howto_fix_stuck_funds.md
new file mode 100644
index 0000000000000000000000000000000000000000..5320044670c307207ce2c4ab69cb817fbed45a61
--- /dev/null
+++ b/_i18n/template/resources/user-guides/howto_fix_stuck_funds.md
@@ -0,0 +1,31 @@
+{% include untranslated.html %}
+Sometimes, your funds will become stuck - you will have some locked funds that never become unlocked. This is how you fix it.
+
+- Load your wallet in monero-wallet-cli.
+
+- Type
+
+> seed
+
+into the command prompt. Write down your 25 word seed, if you haven't already. This is the best way to make sure you don't loose access to your funds.
+
+- Close monero-wallet-cli by typing
+
+> exit
+
+- Backup all of your wallet related files. These include:
+
+> yourwalletname.bin
+> yourwalletname.bin.keys
+> yourwalletname.bin.address.txt
+
+This can be done by copying the files to a new folder.
+
+Sometimes, when creating your wallet, you might have named it something without the .bin part. In that case, the wallet file will be called yourwalletname without the .bin at the end.
+
+- Delete yourwallet.bin
+
+- Load monero-wallet-cli, type in the name of the wallet you just deleted
+
+- Enter password. The wallet will now refresh and hopefully your locked funds will now become unlocked.
+
diff --git a/_i18n/template/resources/user-guides/importing_blockchain.md b/_i18n/template/resources/user-guides/importing_blockchain.md
new file mode 100644
index 0000000000000000000000000000000000000000..43eb5823a0abff340735fb5de634255f000d7c27
--- /dev/null
+++ b/_i18n/template/resources/user-guides/importing_blockchain.md
@@ -0,0 +1,57 @@
+{% include untranslated.html %}
+# Importing the Blockchain to Monero GUI wallet (Windows)
+
+### Step 1
+
+Download the Current bootstrap from https://downloads.getmonero.org/blockchain.raw; you can skip this step if you are importing the Blockchain from another source.
+
+### Step 2
+
+Find the path of your Monero wallet (the folder where you extracted your wallet). For example mine is:
+
+`D:\monero-gui-0.10.3.1`
+
+Your path may be different depending on where you decided to download your wallet and what version of the Monero wallet you have.
+
+### Step 3
+
+Find the path of your downloaded Blockchain for example mine was:
+
+`C:\Users\KeeJef\Downloads\blockchain.raw`
+
+Yours might be different depending on where you downloaded the Blockchain to.
+
+### Step 4
+
+Open a Command Prompt window. You can do this by pressing the Windows key + R, and then typing in the popup box `CMD`
+
+### Step 5
+
+Now you need to navigate using the CMD window to the path of your Monero wallet. You can do this by typing:
+
+`cd C:\YOUR\MONERO\WALLET\FILE\PATH\HERE`
+
+It should look something like:
+
+`cd D:\monero-gui-0.10.3.1`
+
+If your Monero wallet is on another drive you can use `DriveLetter:` for example if your Monero wallet was on your D drive then before using the cd command you would do `D:`
+
+### Step 6
+
+Now type in your command prompt window:
+
+`monero-blockchain-import --verify 1 --input-file C:\YOUR\BLOCKCHAIN\FILE\PATH\HERE`
+
+For example I would type :
+
+`monero-blockchain-import --verify 1 --input-file C:\Users\KeeJef\Downloads\blockchain.raw`
+
+If you downloaded the Blockchain from a trusted, reputable source you may set `verify 0` this will reduce the amount of time to sync the Blockchain.
+
+### Step 7
+
+After the 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/_i18n/template/resources/user-guides/index.md b/_i18n/template/resources/user-guides/index.md
new file mode 100644
index 0000000000000000000000000000000000000000..0eb5cb29e59f47c86b33194360847e8ac2a28930
--- /dev/null
+++ b/_i18n/template/resources/user-guides/index.md
@@ -0,0 +1,83 @@
+{% include untranslated.html %}
+<div class="guides">
+<section class="container">
+ <div class="row">
+ <div class="left half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>General</h2>
+ </div>
+ </div>
+<div class="row start-xs" markdown="1">
+
+[Monero Tools]({{site.baseurl}}/resources/user-guides/monero_tools.html)
+[How to make an offline backup]({{site.baseurl}}/resources/user-guides/Offline_Backup.html)
+[Importing the Monero blockchain]({{site.baseurl}}/resources/user-guides/importing_blockchain.html)
+[How to run a node on VPS]({{site.baseurl}}/resources/user-guides/vps_run_node.html)
+[Securely purchasing and storing Monero]({{site.baseurl}}/resources/user-guides/securely_purchase.html)
+
+</div>
+ </div>
+ </div>
+ <div class="right half col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Wallets</h2>
+ </div>
+ </div>
+<div class="row start-xs" markdown="1">
+
+[Getting started with the CLI wallet]({{site.baseurl}}/resources/user-guides/monero-wallet-cli.html)
+[How to make a view-only wallet]({{site.baseurl}}/resources/user-guides/view_only.html)
+[How to prove payment]({{site.baseurl}}/resources/user-guides/prove-payment.html)
+[Restoring wallet from keys]({{site.baseurl}}/resources/user-guides/restore_from_keys.html)
+[How to connect to a remote node within GUI wallet]({{site.baseurl}}/resources/user-guides/remote_node_gui.html)
+[CLI wallet/daemon isolation with Qubes + Whonix]({{site.baseurl}}/resources/user-guides/cli_wallet_daemon_isolation_qubes_whonix.html)
+
+</div>
+ </div>
+ </div>
+ </div>
+</section>
+
+<section class="container">
+ <div class="row">
+ <div class="left half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Recovery</h2>
+ </div>
+ </div>
+<div class="row start-xs" markdown="1">
+
+[How to fix locked up funds]({{site.baseurl}}/resources/user-guides/howto_fix_stuck_funds.html)
+[How to restore your account]({{site.baseurl}}/resources/user-guides/restore_account.html)
+
+</div>
+ </div>
+ </div>
+ <div class="right half col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Mining</h2>
+ </div>
+ </div>
+<div class="row start-xs" markdown="1">
+
+[How to solo mine with the GUI]({{site.baseurl}}/resources/user-guides/solo_mine_GUI.html)
+[How to mine on a pool with xmr-stak-cpu]({{site.baseurl}}/resources/user-guides/mine-to-pool.html)
+[Mining with Docker and XMRig]({{site.baseurl}}/resources/user-guides/mining_with_xmrig_and_docker.html)
+
+</div>
+ </div>
+ </div>
+ </div>
+
+
+
+</section>
+</div>
diff --git a/_i18n/template/resources/user-guides/mine-to-pool.md b/_i18n/template/resources/user-guides/mine-to-pool.md
new file mode 100644
index 0000000000000000000000000000000000000000..d39075d2b3e77c9a9126e499bc1316646ae18e54
--- /dev/null
+++ b/_i18n/template/resources/user-guides/mine-to-pool.md
@@ -0,0 +1,114 @@
+{% include untranslated.html %}
+# Selecting a pool
+
+There are many pools to choose from, a list is available at
+[moneropools.com](https://moneropools.com). Mining on a larger pool could mean
+more frequent payouts, but mining on a smaller pool helps to keep the network
+decentralized.
+
+# Selecting a CPU miner
+
+Just like pools, there are a lot of miners to choose from. The one that you
+should pick depends on the hardware you want to mine on. This guide will only
+use a CPU miner, and will be using
+[xmr-stak-cpu](https://github.com/fireice-uk/xmr-stak-cpu). Alternatives include
+[wolf's CPUMiner](https://github.com/wolf9466/cpuminer-multi) and
+[sgminer-gm](https://github.com/genesismining/sgminer-gm). However, their
+configuration is slightly different and will not be covered in this guide.
+
+## For Windows Systems
+
+If you are using a Windows system, the developer of xmr-stak-cpu provides
+binaries to download on the
+[GitHub release page](https://github.com/fireice-uk/xmr-stak-cpu/releases).
+
+Download `xmr-stak-cpu-win64.zip` and extract it somewhere you'll be able to
+find it again.
+
+## For Other Operating Systems
+
+If you're not using Windows, you will have to compile xmr-stak-cpu for yourself,
+luckily this isn't as hard as it sounds. Before you can compile the miner, you
+will need to install some of its prerequisites.
+
+For Debian-based distros:
+
+ sudo apt-get install libmicrohttpd-dev libssl-dev cmake build-essential
+
+For Red Hat based distros:
+
+ sudo yum install openssl-devel cmake gcc-c++ libmicrohttpd-devel
+
+<!-- TODO: Add dependencies for other operating systems? -->
+
+Following this, you just need to use cmake to generate the build files, run
+make and copy the config file:
+
+ mkdir build-$(gcc -dumpmachine)
+ cd $_
+ cmake ../
+ make -j$(nproc)
+ cp ../config.txt bin/
+ cd bin
+
+Don't celebrate just yet, as the miner needs to be configured. Running the miner
+now should give you a block of text to copy and paste:
+
+
+
+Open `config.txt` and *replace* the two `"cpu_threads_conf"` lines with the text
+you just copied. It should look something like this afterwards:
+
+
+
+Scroll down in the file until you see the lines containing `"pool_address"`.
+*Replace* the contents of the second set of quotes with the address and port of
+the pool you chose earlier. You can find this information on the pool's website.
+
+Put your wallet address between the quotes on the wallet address. You may leave
+the password blank unless the pool specifies otherwise.
+
+After this, your config should look something like this:
+
+
+
+# Running the miner
+
+**Save the config** file and run the miner!
+
+
+
+Some pools allow you to monitor your hashrate by pasting your address into their
+website. You can also monitor your hashrate by pressing the `h` key.
+
+# Tuning the miner
+
+You might see nasty messages like this:
+
+ [2017-07-09 12:04:02] : MEMORY ALLOC FAILED: mmap failed
+
+This means that you can get around a 20% hashrate boost by enabling large pages.
+
+## Large pages on Linux
+
+Firstly stop the miner (if it's running), run the following commands to enable
+large pages and then start the miner as root:
+
+ sudo sysctl -w vm.nr_hugepages=128
+ sudo ./xmr-stak-cpu
+
+## Large pages on Windows
+
+Taken from `config.txt`:
+
+>By default we will try to allocate large pages. This means you need to "Run As Administrator" on Windows
+You need to edit your system's group policies to enable locking large pages. Here are the steps from MSDN
+1. On the Start menu, click Run. In the Open box, type gpedit.msc.
+2. On the Local Group Policy Editor console, expand Computer Configuration, and then expand Windows Settings.
+3. Expand Security Settings, and then expand Local Policies.
+4. Select the User Rights Assignment folder.
+5. The policies will be displayed in the details pane.
+6. In the pane, double-click Lock pages in memory.
+7. In the Local Security Setting – Lock pages in memory dialog box, click Add User or Group.
+8. In the Select Users, Service Accounts, or Groups dialog box, add an account that you will run the miner on
+9. Reboot for change to take effect.
diff --git a/_i18n/template/resources/user-guides/mining_with_xmrig_and_docker.md b/_i18n/template/resources/user-guides/mining_with_xmrig_and_docker.md
new file mode 100644
index 0000000000000000000000000000000000000000..fcad1cf4feaff2d0dc5a8363f7544b9c820c0dbb
--- /dev/null
+++ b/_i18n/template/resources/user-guides/mining_with_xmrig_and_docker.md
@@ -0,0 +1,37 @@
+{% include untranslated.html %}
+## Introduction
+
+This guide is two fold, ease of use for mining on Linux distributions and some extra security around mining as most of these miners have not had security auditing.
+
+At the end of this guide you will be able to sleep a little easier knowing that if the miner gets exploited it will not migrate to your OS.
+
+### Why Docker
+
+[Docker](https://www.docker.com/) is being used as it is the most well known and has the biggest chance to be already installed.
+
+The container I an using is [alpine-xmrig](https://hub.docker.com/r/bitnn/alpine-xmrig/) as per the name it is built on the [Alpine Linux](https://www.alpinelinux.org/) image.
+
+If you are interested in getting started with Docker, here are some really good starting references.
+* Arch Linux Wiki [Docker Page](https://wiki.archlinux.org/index.php/Docker)
+* Container Solutions [Security Cheat Sheet](http://container-solutions.com/content/uploads/2015/06/15.06.15_DockerCheatSheet_A2.pdf)
+* Digital Oceans [Dockerfile Howto](https://www.digitalocean.com/community/tutorials/docker-explained-using-dockerfiles-to-automate-building-of-images).
+
+For distribution specific installation please refer to the [Docker Docs](https://docs.docker.com/engine/installation/) website.
+
+### Why XMRig
+
+[XMRig](https://github.com/xmrig/xmrig) is just a really solid miner to me. Nice output and statistics, no flashy web-ui's or dependencies. The XMRig container is only ~4MB what makes it extremely portable.
+
+#### Step 1: Mining with XMRig
+
+Run the following
+
+```bash
+# docker run --restart unless-stopped --read-only -m 50M -c 512 bitnn/alpine-xmrig -o POOL01 -o POOL02 -u WALLET -p PASSWORD -k
+# docker run --restart unless-stopped --read-only -m 50M -c 512 bitnn/alpine-xmrig -o pool.supportxmr.com:7777 -u 45CJVagd6WwQAQfAkS91EHiTyfVaJn12uM4Su8iz6S2SHZ3QthmFM9BSPHVZY388ASWx8G9Wbz4BA24RQZUpGczb35fnnJz -p docker:secret -k
+```
+
+#### Step 2: There is no Step 2
+
+You have already done everything you need to do. You are now mining in a docker container with XMRig `ctrl+c` to exit the miner or add `-d` just after `docker run` to background the miner.
+
diff --git a/_i18n/template/resources/user-guides/monero-wallet-cli.md b/_i18n/template/resources/user-guides/monero-wallet-cli.md
new file mode 100644
index 0000000000000000000000000000000000000000..155a82d1485447d81d05167a4a61893d44e77fef
--- /dev/null
+++ b/_i18n/template/resources/user-guides/monero-wallet-cli.md
@@ -0,0 +1,146 @@
+{% include untranslated.html %}
+# monero-wallet-cli
+
+`monero-wallet-cli` is the wallet software that ships with the Monero tree. It is a console program,
+and manages an account. While a bitcoin wallet manages both an account and the blockchain,
+Monero separates these: `monerod` handles the blockchain, and `monero-wallet-cli` handles the account.
+
+This guide will show how to perform various operations from the `monero-wallet-cli` UI. The guide assumes you are using the most recent version of Monero and have already created an account according to the other guides.
+
+
+## Checking your balance
+
+Since the blockchain handling and the wallet are separate programs, many uses of `monero-wallet-cli`
+need to work with the daemon. This includes looking for incoming transactions to your address.
+Once you are running both `monero-wallet-cli` and `monerod`, enter `balance`.
+
+Example:
+
+This will pull blocks from the daemon the wallet did not yet see, and update your balance
+to match. This process will normally be done in the background every minute or so. To see the
+balance without refreshing:
+
+ balance
+ Balance: 64.526198850000, unlocked balance: 44.526198850000, including unlocked dust: 0.006198850000
+
+In this example, `Balance` is your total balance. The `unlocked balance` is the amount currently available to spend. Newly received transactions require 10 confirmations on the blockchain before being unlocked. `unlocked dust` refers to very small amounts of unspent outputs that may have accumulated in your account.
+
+## Sending monero
+
+You will need the standard address you want to send to (a long string starting with '4'), and
+possibly a payment ID, if the receiving party requires one. In that latter case, that party
+may instead give you an integrated address, which is both of these packed into a single address.
+
+### Sending to a standard address:
+
+ transfer ADDRESS AMOUNT PAYMENTID
+
+Replace `ADDRESS` with the address you want to send to, `AMOUNT` with how many monero you want to send,
+and `PAYMENTID` with the payment ID you were given. Payment ID's are optional. If the receiving party doesn't need one, just
+omit it.
+
+### Sending to an integrated address:
+
+ transfer ADDRESS AMOUNT
+
+The payment ID is implicit in the integrated address in that case.
+
+### Specify the number of outputs for a transaction:
+
+ transfer MIXIN ADDRESS AMOUNT
+
+Replace `MIXIN` with the number of outputs you wish to use. **If not specified, the default is 4.** It's a good idea to use the default, but you can increase the number if you want to include more outputs. The higher the number, the larger the transaction, and higher fees are needed.
+
+
+## Receiving monero
+
+If you have your own Monero address, you just need to give your standard address to someone.
+
+You can find out your address with:
+
+ address
+
+Since Monero is anonymous, you won't see the origin address the funds you receive came from. If you
+want to know, for instance to credit a particular customer, you'll have to tell the sender to use
+a payment ID, which is an arbitrary optional tag which gets attached to a transaction. To make life
+easier, you can generate an address that already includes a random payment ID:
+
+ integrated_address
+
+This will generate a random payment ID, and give you the address that includes your own account
+and that payment ID. If you want to select a particular payment ID, you can do that too:
+
+ integrated_address 12346780abcdef00
+
+Payments made to an integrated address generated from your account will go to your account,
+with that payment id attached, so you can tell payments apart.
+
+
+## Proving to a third party you paid someone
+
+If you pay a merchant, and the merchant claims to not have received the funds, you may need
+to prove to a third party you did send the funds - or even to the merchant, if it is a honest
+mistake. Monero is private, so you can't just point to your transaction in the blockchain,
+as you can't tell who sent it, and who received it. However, by supplying the per-transaction
+private key to a party, that party can tell whether that transaction sent monero to that
+particular address. Note that storing these per-transaction keys is disabled by default, and
+you will have to enable it before sending, if you think you may need it:
+
+ set store-tx-info 1
+
+You can retrieve the tx key from an earlier transaction:
+
+ get_tx_key 1234567890123456789012345678901212345678901234567890123456789012
+
+Pass in the transaction ID you want the key for. Remember that a payment might have been
+split in more than one transaction, so you may need several keys. You can then send that key,
+or these keys, to whoever you want to provide proof of your transaction, along with the
+transaction id and the address you sent to. Note that this third party, if knowing your
+own address, will be able to see how much change was returned to you as well.
+
+If you are the third party (that is, someone wants to prove to you that they sent monero
+to an address), then you can check this way:
+
+ check_tx_key TXID TXKEY ADDRESS
+
+Replace `TXID`, `TXKEY` and `ADDRESS` with the transaction ID, per-transaction key, and destination
+address which were supplied to you, respectively. monero-wallet-cli will check that transaction
+and let you know how much monero this transaction paid to the given address.
+
+
+## Getting a chance to confirm/cancel payments
+
+If you want to get a last chance confirmation when sending a payment:
+
+ set always-confirm-transfers 1
+
+
+## How to find a payment to you
+
+If you received a payment using a particular payment ID, you can look it up:
+
+ payments PAYMENTID
+
+You can give more than one payment ID too.
+
+More generally, you can review incoming and outgoing payments:
+
+ show_transfers
+
+You can give an optional height to list only recent transactions, and request
+only incoming or outgoing transactions. For example,
+
+ show_transfers in 650000
+
+will only incoming transfers after block 650000. You can also give a height
+range.
+
+If you want to mine, you can do so from the wallet:
+
+ start_mining 2
+
+This will start mining on the daemon usin two threads. Note that this is solo mining,
+and may take a while before you find a block. To stop mining:
+
+ stop_mining
+
diff --git a/_i18n/template/resources/user-guides/monero_tools.md b/_i18n/template/resources/user-guides/monero_tools.md
new file mode 100644
index 0000000000000000000000000000000000000000..67d60a0469674229a9622350df431681cc655462
--- /dev/null
+++ b/_i18n/template/resources/user-guides/monero_tools.md
@@ -0,0 +1,18 @@
+{% include untranslated.html %}
+# Monero tools
+
+These tools can be used to gain information about the Monero network or your transaction data in the blockchain.
+
+### [Check that a recipient has received your funds](http://xmrtests.llcoins.net/checktx.html)
+
+### [Tools for monero address generation](https://xmr.llcoins.net/)
+
+### [Monero node count](http://moneronodes.i2p.xyz/)
+
+### [Monero node map](https://monerohash.com/nodes-distribution.html)
+
+### [Monero offline wallet generator](http://moneroaddress.org/)
+
+### [Monero network statistics](http://moneroblocks.info/stats)
+
+### [Monero.how statistics](https://www.monero.how/)
\ No newline at end of file
diff --git a/_i18n/template/resources/user-guides/png/create_wallet/1.png b/_i18n/template/resources/user-guides/png/create_wallet/1.png
new file mode 100644
index 0000000000000000000000000000000000000000..44acf51b19ea9435af2dc466ed05514b7543564d
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/create_wallet/1.png differ
diff --git a/_i18n/template/resources/user-guides/png/create_wallet/10.png b/_i18n/template/resources/user-guides/png/create_wallet/10.png
new file mode 100644
index 0000000000000000000000000000000000000000..2f248c9dda4ce97441e68d65923f4d74feb2a7c3
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/create_wallet/10.png differ
diff --git a/_i18n/template/resources/user-guides/png/create_wallet/11.png b/_i18n/template/resources/user-guides/png/create_wallet/11.png
new file mode 100644
index 0000000000000000000000000000000000000000..f8bb9989a3dfac8d717ae20c23b14aaaf987876d
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/create_wallet/11.png differ
diff --git a/_i18n/template/resources/user-guides/png/create_wallet/12.png b/_i18n/template/resources/user-guides/png/create_wallet/12.png
new file mode 100644
index 0000000000000000000000000000000000000000..2e1f69d63c25cf308989596187d55adf10fcc6d2
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/create_wallet/12.png differ
diff --git a/_i18n/template/resources/user-guides/png/create_wallet/13.png b/_i18n/template/resources/user-guides/png/create_wallet/13.png
new file mode 100644
index 0000000000000000000000000000000000000000..2db5d603ab699581e9755c369602d9088b688f53
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/create_wallet/13.png differ
diff --git a/_i18n/template/resources/user-guides/png/create_wallet/14.png b/_i18n/template/resources/user-guides/png/create_wallet/14.png
new file mode 100644
index 0000000000000000000000000000000000000000..bf2906e280f00193aef3b19f430bcac8c7cedee6
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/create_wallet/14.png differ
diff --git a/_i18n/template/resources/user-guides/png/create_wallet/15.png b/_i18n/template/resources/user-guides/png/create_wallet/15.png
new file mode 100644
index 0000000000000000000000000000000000000000..7c675edfb7b174ed45fac544d26762f822cf3881
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/create_wallet/15.png differ
diff --git a/_i18n/template/resources/user-guides/png/create_wallet/16.png b/_i18n/template/resources/user-guides/png/create_wallet/16.png
new file mode 100644
index 0000000000000000000000000000000000000000..ab23b572fa33fbf019440ba419d9adfe9f9ce9b3
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/create_wallet/16.png differ
diff --git a/_i18n/template/resources/user-guides/png/create_wallet/17.png b/_i18n/template/resources/user-guides/png/create_wallet/17.png
new file mode 100644
index 0000000000000000000000000000000000000000..97ea15bcad6ce467ba36202ebf28dd6f987a6244
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/create_wallet/17.png differ
diff --git a/_i18n/template/resources/user-guides/png/create_wallet/18.png b/_i18n/template/resources/user-guides/png/create_wallet/18.png
new file mode 100644
index 0000000000000000000000000000000000000000..20546a9ab5e547b73c0b58164537cba6e4b911d4
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/create_wallet/18.png differ
diff --git a/_i18n/template/resources/user-guides/png/create_wallet/19.png b/_i18n/template/resources/user-guides/png/create_wallet/19.png
new file mode 100644
index 0000000000000000000000000000000000000000..5a7088e259addd15157a27aa917bcaebe92e2d5d
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/create_wallet/19.png differ
diff --git a/_i18n/template/resources/user-guides/png/create_wallet/2.png b/_i18n/template/resources/user-guides/png/create_wallet/2.png
new file mode 100644
index 0000000000000000000000000000000000000000..164aa6b689364ad1ed04f2388653f0c844006649
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/create_wallet/2.png differ
diff --git a/_i18n/template/resources/user-guides/png/create_wallet/20.png b/_i18n/template/resources/user-guides/png/create_wallet/20.png
new file mode 100644
index 0000000000000000000000000000000000000000..c5169249b22e6a26c56d11a86c76e900d4ec467b
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/create_wallet/20.png differ
diff --git a/_i18n/template/resources/user-guides/png/create_wallet/21.png b/_i18n/template/resources/user-guides/png/create_wallet/21.png
new file mode 100644
index 0000000000000000000000000000000000000000..090ff767ae613d71f2cf0d7390dd204b34ec1ccf
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/create_wallet/21.png differ
diff --git a/_i18n/template/resources/user-guides/png/create_wallet/22.png b/_i18n/template/resources/user-guides/png/create_wallet/22.png
new file mode 100644
index 0000000000000000000000000000000000000000..8c7a7669afdb1b9fc670589184214fe029280f5c
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/create_wallet/22.png differ
diff --git a/_i18n/template/resources/user-guides/png/create_wallet/23.png b/_i18n/template/resources/user-guides/png/create_wallet/23.png
new file mode 100644
index 0000000000000000000000000000000000000000..e2dfc0c4ed20d73ba9341b83195020068716a5c8
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/create_wallet/23.png differ
diff --git a/_i18n/template/resources/user-guides/png/create_wallet/3.png b/_i18n/template/resources/user-guides/png/create_wallet/3.png
new file mode 100644
index 0000000000000000000000000000000000000000..f4f4436e27849c8c3ac3025626a7d5be4a9c6667
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/create_wallet/3.png differ
diff --git a/_i18n/template/resources/user-guides/png/create_wallet/4.png b/_i18n/template/resources/user-guides/png/create_wallet/4.png
new file mode 100644
index 0000000000000000000000000000000000000000..36be1be0518f8d1aee145740d4928092690ae9c9
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/create_wallet/4.png differ
diff --git a/_i18n/template/resources/user-guides/png/create_wallet/5.png b/_i18n/template/resources/user-guides/png/create_wallet/5.png
new file mode 100644
index 0000000000000000000000000000000000000000..56c6733aabd3ea7a213e4b16bb3b3244631b82a5
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/create_wallet/5.png differ
diff --git a/_i18n/template/resources/user-guides/png/create_wallet/6.png b/_i18n/template/resources/user-guides/png/create_wallet/6.png
new file mode 100644
index 0000000000000000000000000000000000000000..8e0d7950fb9225541f455a24330a36ff7357f252
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/create_wallet/6.png differ
diff --git a/_i18n/template/resources/user-guides/png/create_wallet/7.png b/_i18n/template/resources/user-guides/png/create_wallet/7.png
new file mode 100644
index 0000000000000000000000000000000000000000..c18527827bd6dcfdf4257fcb46c82e754f61121b
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/create_wallet/7.png differ
diff --git a/_i18n/template/resources/user-guides/png/create_wallet/8.png b/_i18n/template/resources/user-guides/png/create_wallet/8.png
new file mode 100644
index 0000000000000000000000000000000000000000..ce02508b7d912855670066aec22ebef824b0d986
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/create_wallet/8.png differ
diff --git a/_i18n/template/resources/user-guides/png/create_wallet/9.png b/_i18n/template/resources/user-guides/png/create_wallet/9.png
new file mode 100644
index 0000000000000000000000000000000000000000..cac31479b11bbad5907d984c8e81bdf50fcb2a8d
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/create_wallet/9.png differ
diff --git a/_i18n/template/resources/user-guides/png/easiest_way/01.png b/_i18n/template/resources/user-guides/png/easiest_way/01.png
new file mode 100644
index 0000000000000000000000000000000000000000..17c55b2d6a024f3245055975b654681265812d2d
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/easiest_way/01.png differ
diff --git a/_i18n/template/resources/user-guides/png/easiest_way/02.png b/_i18n/template/resources/user-guides/png/easiest_way/02.png
new file mode 100644
index 0000000000000000000000000000000000000000..91e1bfd16f7843310fc59c84c4aff2e03aa13181
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/easiest_way/02.png differ
diff --git a/_i18n/template/resources/user-guides/png/easiest_way/03.png b/_i18n/template/resources/user-guides/png/easiest_way/03.png
new file mode 100644
index 0000000000000000000000000000000000000000..dded71ade21780fe14fd63fb7aab11bddcd635b1
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/easiest_way/03.png differ
diff --git a/_i18n/template/resources/user-guides/png/easiest_way/04.png b/_i18n/template/resources/user-guides/png/easiest_way/04.png
new file mode 100644
index 0000000000000000000000000000000000000000..e657d4315e459c4b18648d417c539193fce5376d
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/easiest_way/04.png differ
diff --git a/_i18n/template/resources/user-guides/png/easiest_way/05.png b/_i18n/template/resources/user-guides/png/easiest_way/05.png
new file mode 100644
index 0000000000000000000000000000000000000000..00d2b26a05fb2fae413d4853c1f9e5159428d1c6
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/easiest_way/05.png differ
diff --git a/_i18n/template/resources/user-guides/png/easiest_way/06.png b/_i18n/template/resources/user-guides/png/easiest_way/06.png
new file mode 100644
index 0000000000000000000000000000000000000000..4d55286ce0e83da7051dc8070847a729f04c72fe
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/easiest_way/06.png differ
diff --git a/_i18n/template/resources/user-guides/png/easiest_way/07.png b/_i18n/template/resources/user-guides/png/easiest_way/07.png
new file mode 100644
index 0000000000000000000000000000000000000000..715245b2239d4ed7882c0c6e933cc13aa9173e82
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/easiest_way/07.png differ
diff --git a/_i18n/template/resources/user-guides/png/easiest_way/08.png b/_i18n/template/resources/user-guides/png/easiest_way/08.png
new file mode 100644
index 0000000000000000000000000000000000000000..bfc459a89582d8791f3cd2b1b1a013e2004e638a
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/easiest_way/08.png differ
diff --git a/_i18n/template/resources/user-guides/png/easiest_way/09.png b/_i18n/template/resources/user-guides/png/easiest_way/09.png
new file mode 100644
index 0000000000000000000000000000000000000000..e632bbb82e533b6fb205baf4edd5b86f153a9229
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/easiest_way/09.png differ
diff --git a/_i18n/template/resources/user-guides/png/easiest_way/10.png b/_i18n/template/resources/user-guides/png/easiest_way/10.png
new file mode 100644
index 0000000000000000000000000000000000000000..3a9337336bf1c34e7980da562a63f987d4781232
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/easiest_way/10.png differ
diff --git a/_i18n/template/resources/user-guides/png/easiest_way/11.png b/_i18n/template/resources/user-guides/png/easiest_way/11.png
new file mode 100644
index 0000000000000000000000000000000000000000..eaa4a5b989cc6463a29285bae4d0e7688b595ce4
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/easiest_way/11.png differ
diff --git a/_i18n/template/resources/user-guides/png/easiest_way/12.png b/_i18n/template/resources/user-guides/png/easiest_way/12.png
new file mode 100644
index 0000000000000000000000000000000000000000..e38159ec6fa34c74408f27ee6b5792f337bfacb2
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/easiest_way/12.png differ
diff --git a/_i18n/template/resources/user-guides/png/easiest_way/13.png b/_i18n/template/resources/user-guides/png/easiest_way/13.png
new file mode 100644
index 0000000000000000000000000000000000000000..ed3b707d01f87f3376b134ede6477b01b684bac3
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/easiest_way/13.png differ
diff --git a/_i18n/template/resources/user-guides/png/mine_to_pool/1.png b/_i18n/template/resources/user-guides/png/mine_to_pool/1.png
new file mode 100644
index 0000000000000000000000000000000000000000..a6e7652877110b793894d9ae627c7466a56b7b0c
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/mine_to_pool/1.png differ
diff --git a/_i18n/template/resources/user-guides/png/mine_to_pool/2.png b/_i18n/template/resources/user-guides/png/mine_to_pool/2.png
new file mode 100644
index 0000000000000000000000000000000000000000..83a7dd163530cfe1a9d5c9c44b4482c7cdb40458
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/mine_to_pool/2.png differ
diff --git a/_i18n/template/resources/user-guides/png/mine_to_pool/3.png b/_i18n/template/resources/user-guides/png/mine_to_pool/3.png
new file mode 100644
index 0000000000000000000000000000000000000000..70aeea2aaa91a34285fd0a0162f858a9b0bc76c6
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/mine_to_pool/3.png differ
diff --git a/_i18n/template/resources/user-guides/png/mine_to_pool/4.png b/_i18n/template/resources/user-guides/png/mine_to_pool/4.png
new file mode 100644
index 0000000000000000000000000000000000000000..13361a0e85a8b82a374917df939bb97f4529ff32
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/mine_to_pool/4.png differ
diff --git a/_i18n/template/resources/user-guides/png/remote_node/remote-node-screenshot.png b/_i18n/template/resources/user-guides/png/remote_node/remote-node-screenshot.png
new file mode 100644
index 0000000000000000000000000000000000000000..a32bf5088c040273bef87448b049c5bc112be196
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/remote_node/remote-node-screenshot.png differ
diff --git a/_i18n/template/resources/user-guides/png/solo_mine_GUI/01.PNG b/_i18n/template/resources/user-guides/png/solo_mine_GUI/01.PNG
new file mode 100644
index 0000000000000000000000000000000000000000..7ca5f7c247ee06462a549ca4a6b5c6380b9f257f
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/solo_mine_GUI/01.PNG differ
diff --git a/_i18n/template/resources/user-guides/png/solo_mine_GUI/02.PNG b/_i18n/template/resources/user-guides/png/solo_mine_GUI/02.PNG
new file mode 100644
index 0000000000000000000000000000000000000000..42a5290e0733dedb0f397e50a86215b0887039a5
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/solo_mine_GUI/02.PNG differ
diff --git a/_i18n/template/resources/user-guides/png/solo_mine_GUI/03.PNG b/_i18n/template/resources/user-guides/png/solo_mine_GUI/03.PNG
new file mode 100644
index 0000000000000000000000000000000000000000..ab7b8c2a2143d0ab46fae3294a09fe01b0bd61f4
Binary files /dev/null and b/_i18n/template/resources/user-guides/png/solo_mine_GUI/03.PNG differ
diff --git a/_i18n/template/resources/user-guides/prove-payment.md b/_i18n/template/resources/user-guides/prove-payment.md
new file mode 100644
index 0000000000000000000000000000000000000000..08a92584fb9d14971fdcd1eeb80d0bb4369b6c84
--- /dev/null
+++ b/_i18n/template/resources/user-guides/prove-payment.md
@@ -0,0 +1,52 @@
+{% include untranslated.html %}
+When you send money to a party who then disputes the payment was made, you need to be able to prove the payment was made.
+
+With Bitcoin, this is typically done by looking up the transaction ID, where the origin and destination addresses are
+shown, along with the amount transacted.
+
+Monero, however, is private: that information is not available publicly on the blockchain. The steps are therefore a bit
+more involved.
+
+To prove to Charlie that she made a payment to Bob, Alice must supply Charlie three pieces of information:
+
+- the transaction ID, as is done in Bitcoin
+- Bob's address, as is done with Bitcoin
+- the transaction's key, which is new with Monero and other CryptoNote currencies
+
+When Alice made the transaction, a one time key was automatically generated just for this transaction. Alice can
+query it thus in monero-wallet-cli (new name for the old simplewallet):
+
+> get_tx_key TXID
+
+Alice would plug in her actual transaction ID instead of this TXID placeholder. All being well, the one time transaction key
+will be displayed.
+
+Note that this will only work if monero-wallet-cli is set to save transaction keys. To double check:
+
+> set
+
+If it's set to 0, set it to 1:
+
+> set store-tx-info 1
+
+Alice can now send Charlie the transaction key along with transaction ID and Bob's address.
+
+Note: if several transactions were made, this needs repeating for each such transaction.
+
+
+---
+
+Charlie now received those three pieces of information, and wants to check Alice is telling the truth: on an up to date
+blockchain, Charlie types in monero-wallet-cli:
+
+> check_tx_key TXID TXKEY ADDRESS
+
+The information supplied by Alice plugs neatly instead of the placeholders. monero-wallet-cli will use the transaction
+key to decode the transaction, and display how much this particular transaction sent to this address. Obviously,
+Charlie will want to double check with Bob the address is really his - same as with Bitcoin.
+
+Alternatively, the transaction key can be obtained in the GUI in the History tab. Click on details for each individual transaction to get the key.
+
+Note: if several transactions were made, this needs repeating for each such transaction.
+
+
diff --git a/_i18n/template/resources/user-guides/remote_node_gui.md b/_i18n/template/resources/user-guides/remote_node_gui.md
new file mode 100644
index 0000000000000000000000000000000000000000..c63f85e1bde160bc79a14cb9df3d64d8b3338721
--- /dev/null
+++ b/_i18n/template/resources/user-guides/remote_node_gui.md
@@ -0,0 +1,11 @@
+{% include untranslated.html %}
+## Finding a node
+First things first, you need to find a node to connect to! [moneroworld.com](https://moneroworld.com/#nodes) has some great resources for finding nodes. One of the easiest methods
+would be to use a node run by moneroworld, but they have a tool for finding random nodes too.
+
+## Connecting to the node from the GUI wallet
+After you enter your password for your wallet, you will see a pop up that will give you the option to "use custom settings". Click on it. You will then be
+sent to the "Settings" page in the GUI. At this point you should see two text boxes to the right of a label that says "Daemon address". In the first box (the one to the left) you need to enter the address of the node that you want to
+connect to. This address might look like `node.moneroworld.com` or it could look like any old ip address. The smaller box to the right is where you enter the node's port. The default port is `18081` but if you are using a random node the port that is used will vary. The port for node.moneroworld.com uses 18089.
+### Your screen should look a bit like this
+<img src="{{site.baseurl}}/resources/user-guides/png/remote_node/remote-node-screenshot.png" width="600">
diff --git a/_i18n/template/resources/user-guides/restore_account.md b/_i18n/template/resources/user-guides/restore_account.md
new file mode 100644
index 0000000000000000000000000000000000000000..e79cc1f0cc6700cec213fea4c7d1b3d9fb54fbf9
--- /dev/null
+++ b/_i18n/template/resources/user-guides/restore_account.md
@@ -0,0 +1,23 @@
+{% include untranslated.html %}
+## Operating Systems: Windows, Linux, Mac
+
+### Account Software: monero-wallet-cli
+
+- Retrieve your 25 word @mnemonic-seed that you saved when creating your old Monero @wallet
+
+- Open a command prompt and navigate to the drive and directory that contains monero-wallet-cli
+
+- At the command prompt type: `monero-wallet-cli --restore-deterministic-wallet`
+
+- Once you press enter you will be prompted for a wallet file name. Give your wallet a new name, any name will do
+
+- Press enter again and you will be prompted for a password. Give your wallet a new and long password
+
+- Press enter again you will be prompted to repeat the password
+
+- Press enter again and you will be prompted for the 25 word electrum style mnemonic seed that you retrieved earlier
+
+- You will then be prompted with "Restore from specific blockchain height (optional, default 0):" Default will start the restore process from the beginning of the Monero blockchain. If you don't know the specific blockchain height, just hit enter. (Specifying a specific blockchain height will start the restore process from that specific height. This will save a bit of time in scanning, if you know what starting blockchain height your initial funds were transacted for this specific account.)
+
+After you have entered the 25 word mnemonic seed and have chosen your specific blockchain height, monero-wallet-cli will generate the same public address and view key as your old wallet and begin the refresh process automatically. (Please be patient as the refresh process may take a while.)
+
diff --git a/_i18n/template/resources/user-guides/restore_from_keys.md b/_i18n/template/resources/user-guides/restore_from_keys.md
new file mode 100644
index 0000000000000000000000000000000000000000..bba53a400c3c70898e2d12d7982736d6b9f9fa07
--- /dev/null
+++ b/_i18n/template/resources/user-guides/restore_from_keys.md
@@ -0,0 +1,19 @@
+{% include untranslated.html %}
+Restoring a wallet from private keys (via the command line) is pretty simple. If you have the necessary information, with this guide you can completely restore your wallet. Note: you do NOT have to have your password to restore from keys.
+
+You need to have 3 pieces of data from your wallet, or your .keys file which holds this info and the password to decrypt it. The 3 wallet components that you need are:
+
+1. **Address**
+2. **Secret Spendkey**
+3. **Secret Viewkey**
+
+
+Then run the wallet command:
+
+`./monero-wallet-cli --generate-from-keys New_Wallet_Name.abc`
+
+Next, you'll be asked for the Address, the spendkey, the viewkey, and finally the new password for the re-generated wallet.
+
+Running this with the correct parameters will re-generate your wallet files for you and allow you to set a new password.
+
+If you run into any trouble, running `./monero-wallet-cli --help` will show you the options available to you at wallet startup. Once you're inside your wallet, running the `help` command will list the help for the commands available to you within the wallet.
diff --git a/_i18n/template/resources/user-guides/securely_purchase.md b/_i18n/template/resources/user-guides/securely_purchase.md
new file mode 100644
index 0000000000000000000000000000000000000000..508119ea0cd0c01b862ac5853aa696b866b25bb1
--- /dev/null
+++ b/_i18n/template/resources/user-guides/securely_purchase.md
@@ -0,0 +1,82 @@
+{% include untranslated.html %}
+## How to purchase Monero and securely store it.
+
+This is a guide to purchase and securely store Monero as of June 2017.
+
+#### Step 1: Buy Bitcoin
+
+There are many ways to buy Bitcoin. Two semi-reliable companies at this time are Xapo <http://www.xapo.com/> and Coinbase <http://www.coinbase.com/>. The process will involve uploading your personal identification (State ID, Passport, etc.) and will take anywhere from 2 to 10 days (or longer). Verify their reputation on Reddit before making a large purchase. Xapo uses Wire Transfer and Coinbase uses Bank Transfer (ACH in the USA). Xapo should be faster than Coinbase. Coinbase also allows small "instant" buys via a debit card but adds a large fee for this option. Once you have purchased Bitcoin, you are ready to convert it to Monero!
+
+#### Step 2: Download and create a Paper Wallet on a secure and air-gapped computer.
+
+Download the paper wallet generator at: https://moneroaddress.org and copy it to a USB stick (Direct link: https://github.com/moneromooo-monero/monero-wallet-generator/archive/master.zip).
+
+Unzip and open the paper wallet generator (monero-wallet-generator.html) into a web browser on an air-gapped computer that hasn't been used before, or has had a clean installation of the OS.
+
+Your paper wallet will have four important items:
+
+Monero Public Address
+The public address is used to receive funds to the wallet. You give this to anyone who will be sending funds to your wallet.
+
+Monero Mnemonic Seed
+The mnemonic seed is a method of storing the entire wallet that is easily recognizable to humans. This is all you need to restore your wallet at a later date.
+
+Monero Private Spend Key
+The private spend key is used to send funds from the wallet.
+
+Monero Private View Key
+The private view key is to view transactions entering the wallet. Commonly this is used to setup a view-only wallet which can see incoming transactions live on the blockchain as they are sent to a cold storage wallet.
+
+At this point you have many options. You can print the wallet on paper, save it as a PDF or text on a USB stick, burn it to CD/DVD, etc. Most likely you will want at least two or three copies, stored securely in different locations. If storing digitally, encrypt everything with a strong password. If storing on paper, do not show the wallet to anyone else who can memorize your 25 word key, or take a picture of the wallet without your permission. Sending someone a picture of the wallet is the same as giving away all of your funds.
+
+Whichever method you chose, be sure there's no copy of the Monero wallet left over on the device you used. You may need to securely delete the Monero wallet if you saved it to a disk, or make sure your printer does not save a copy in memory.
+
+*If you lose access to your Monero paper wallet the Monero will not be available to you or anyone else, ever. You wont be able to recover them!
+
+#### Side Note
+Option to encrypt an XMR mnemonic seed:
+https://xmr.llcoins.net/
+Download the html page and place it on your airgapped computer. Check the part "Encrypt/Decrypt Mnemonic Seed" and make sure you use "CN Add" with a decent password. Thanks manicminer5.
+
+
+
+#### Step 3: Convert your Bitcoin to Monero and have it sent to your Monero Paper Wallet
+
+Switch to your internet connected computer and go to www.shapeshift.io. Choose "Deposit Bitcoin" and "Receive Monero" (quick).
+
+Press Continue.
+
+Your Monero Address (the Monero Public Address on your Monero Paper Wallet)
+Paste the Monero Public address from your paper wallet where it says "Your Monero Address". But wait, since your Monero Public Address is on an airgapped computer (right?), you can't copy and paste anything... Copy it over by hand, or get a blank USB drive and copy only the Public Address to it.
+
+Refund Address (Bitcoin Public Address you can receive funds at)
+Enter a Bitcoin address that you control where a refund can be sent in case there's a problem with the transaction. It's very important that you enter a Bitcoin Public Address you control or can receive funds at. At Xapo and Coinbase this is called a Receive Address and it may change periodically.
+
+Payment ID
+Leave Payment ID blank if you are sending to your own Monero wallet or Monero paper wallet.
+
+Agree to the Terms and hit the slider to make this a "Reusable Address".
+
+Press "Start Transaction".
+
+Deposit Address (Shapeshift.io's Public Bitcoin Address created only to receive your funds)
+In the new screen that pops up, copy the Deposit Address into your clipboard (select and hit ctrl+c or edit-copy). You will send Bitcoin from Xapo/Coinbase to Shapeshift.io via this address.
+
+Go to your Xapo or Circle account, and find a Transfer or Send button. Paste the Bitcoin Deposit address into the Destination field and enter the amount of bitcoin you would like to have converted to Monero. It must be within the Deposit Min and Deposit Max range specified by Shapeshift.io. Press Send and authorize the transaction, if required.
+
+Once the send has been initiated by Xapo/Coinbase there will be a delay while the transaction enters the Bitcoin blockchain and awaits confirmation. This may be minutes or hours. You can check if the payment has been sent by looking up the Shapeshift.io Deposit address at blockchain.info. Your transaction to Shapeshift.io will show up there.
+
+When your Bitcoin transaction has been confirmed, Shapeshift.io will then begin exchanging Bitcoin (BTC) for Monero (XMR) at one of the exchanges and when it's complete, send the Monero to the address of your Cold Storage Paper Wallet! This can take minutes to hours. If there's an issue, contact Shapeshift.io. They have good support.
+
+When the Shapehift.io webpage says your transaction has been completed, you should now have Monero in your Paper Wallet!
+
+
+#### Notes and How to Verify Funds
+Because the Monero blockchain is private and untraceable, you won't be able to lookup your Monero Public Address and confirm that the funds have arrived like you might with Bitcoin. This is good for privacy, but bad for convenience.
+
+To securely verify the funds have arrived at your wallet, you will need to setup a View Only wallet. This is where that view-key comes in. To create a view-only wallet see the entry: [View Only Wallets]({{site.baseurl}}/resources/user-guides/view_only.html)
+
+To verify the funds are *still in* your wallet and have not been spent you need to create a Cold Wallet with your mnemonic key (all your funds) on an airgapped computer with an up-to-date copy of the Monero Blockchain. When finished you will have to securely erase the wallet or connect it to the internet and it becomes a Hot Wallet.
+
+
+
diff --git a/_i18n/template/resources/user-guides/solo_mine_GUI.md b/_i18n/template/resources/user-guides/solo_mine_GUI.md
new file mode 100644
index 0000000000000000000000000000000000000000..3f14c7c738efe2b7da98cdb67e28dbb50b489ec7
--- /dev/null
+++ b/_i18n/template/resources/user-guides/solo_mine_GUI.md
@@ -0,0 +1,16 @@
+{% include untranslated.html %}
+It is very easy to solo mine with the official GUI. If you have not done so already, go to the <a href="{{site.baseurl}}/downloads/">Monero downloads page</a> and download the official GUI for your operating system. Then, run the setup and be patient as Monero synchronizes with the network. You should see that it displays "Connected" in the lower left corner.
+
+<img src="/resources/user-guides/png/solo_mine_GUI/01.PNG" style="width: 600px;"/>
+
+Click on the "Advanced" tab. You should see that several other options appear. Now click on the "Mining" sub-tab.
+
+<img src="/resources/user-guides/png/solo_mine_GUI/02.PNG" style="width: 600px;"/>
+
+You should now have an option to start mining. You can optionally change the number of threads to mine with. For optimal efficiency, you should mine with your CPU's cache divided by 2. You will need to look up your CPU's specs on the manufacturer's website. If you are unsure, leave the number of threads at 1. Click the "Start mining" button.
+
+<img src="/resources/user-guides/png/solo_mine_GUI/03.PNG" style="width: 600px;"/>
+
+You are now mining with the network, as you can see on the bottom of the image. In this example, the computer is contributing 23 H/s to the Monero network. Mining helps keep the network secure, and you may get lucky and receive a reward for protecting the network.
+
+To stop mining, simply click the "Stop mining" button.
diff --git a/_i18n/template/resources/user-guides/view_only.md b/_i18n/template/resources/user-guides/view_only.md
new file mode 100644
index 0000000000000000000000000000000000000000..993bc39f30bb7c41524eaf84f0d9c4931dc1f4f8
--- /dev/null
+++ b/_i18n/template/resources/user-guides/view_only.md
@@ -0,0 +1,13 @@
+{% include untranslated.html %}
+A view-only wallet can only see which incoming transactions belong to you. It can not spend any of your Monero, in fact it can't even see outgoing transactions from this wallet. This makes view-only wallets particularly interesting for
+
+* Developers writing libraries to validate payments
+* End users validating incoming transactions to cold wallets
+
+### Creating A View-Only Wallet
+
+You can create a view-only wallet from any existing wallet.
+
+Open an existing wallet or create a new one using `monero-wallet-cli`. In the wallet, type `address` and `viewkey` to display the wallet's address and secret viewkey. Type `exit` to close the wallet.
+
+Next, create your view-only wallet by typing `monero-wallet-cli --generate-from-view-key wallet-name`. The last argument will be your new wallet's file name. You will be prompted for `Standard address` and `View key` by the wallet. Paste in your original wallet's address and secret view key. Next, enter and confirm a password for your new wallet and you're done.
diff --git a/_i18n/template/resources/user-guides/vps_run_node.md b/_i18n/template/resources/user-guides/vps_run_node.md
new file mode 100644
index 0000000000000000000000000000000000000000..fa928dea2d868450f58e75e71dcd539b0bc1b22d
--- /dev/null
+++ b/_i18n/template/resources/user-guides/vps_run_node.md
@@ -0,0 +1,48 @@
+{% include untranslated.html %}
+# monerod
+
+`monerod` is the daemon software that ships with the Monero tree. It is a console program, and manages the blockchain. While a bitcoin wallet manages both an account and the blockchain, Monero separates these: `monerod` handles the blockchain, and `monero-wallet-cli` handles the account.
+
+This guide assumes you have already set up your VPS account and are using SSH to tunnel into the server console.
+
+## Linux, 64-bit (Ubuntu 16.04 LTS)
+
+### Make sure that port 18080 is open
+`monerod` uses this port to communicate with other nodes on the Monero network.
+
+Example if using `ufw`: `sudo ufw allow 18080`
+Example if using `iptables`: `sudo iptables -A INPUT -p tcp --dport 18080 -j ACCEPT`
+
+### Download the current Monero Core binaries
+
+ wget https://downloads.getmonero.org/linux64
+
+### Make a directory and extract the files.
+
+ mkdir monero
+ tar -xjvf linux64 -C monero
+
+### Launch the daemon
+
+ cd monero
+ ./monerod
+
+### Options:
+
+Show list of all options and settings:
+
+ ./monerod --help
+
+Launch the daemon as a background process:
+
+ ./monerod --detach
+
+Monitor the output of `monerod` if running as daemon:
+
+ tail -f ~/.bitmonero/bitmonero.log
+
+Keep the VPS secure with autoupdate:
+
+https://help.ubuntu.com/community/AutomaticSecurityUpdates
+
+
diff --git a/_i18n/template/technical-specs.md b/_i18n/template/technical-specs.md
new file mode 100644
index 0000000000000000000000000000000000000000..57224b681073f29262170d5ae1201e023bd857d8
--- /dev/null
+++ b/_i18n/template/technical-specs.md
@@ -0,0 +1,133 @@
+{% include untranslated.html %}
+<div class="about-monero">
+ <section class="container">
+ <div class="row">
+ <!-- left two-thirds block-->
+ <div class="full col-xs-12">
+ <div class="info-block text-adapt">
+
+ <div class="row">
+ <div class="col">
+ <h3>No premine, no instamine, no token</h3>
+ </div>
+ </div>
+
+<div markdown="1">
+* Monero had no premine or instamine
+* Monero did not sell any token
+* Monero had no presale of any kind
+</div>
+
+ <div class="row">
+ <div class="col">
+ <h3>Proof of Work</h3>
+ </div>
+ </div>
+
+<div markdown="1">
+* CryptoNight
+* may change in the future
+</div>
+
+ <div class="row">
+ <div class="col">
+ <h3>Difficulty retarget</h3>
+ </div>
+ </div>
+
+<div markdown="1">
+* every block
+* based on the last 720 blocks, excluding 20% of the timestamp outliers
+</div>
+
+ <div class="row">
+ <div class="col">
+ <h3>Block time</h3>
+ </div>
+ </div>
+
+<div markdown="1">
+* 2 minutes
+* may change in the future as long as emission curve is preserved
+</div>
+
+ <div class="row">
+ <div class="col">
+ <h3>Block reward</h3>
+ </div>
+ </div>
+
+<div markdown="1">
+* smoothly decreasing and subject to penalties for blocks greater then median size of the last 100 blocks (M100)
+* see the [latest block](https://moneroblocks.info/) coinbase transaction amount for current reward
+</div>
+
+ <div class="row">
+ <div class="col">
+ <h3>Block size</h3>
+ </div>
+ </div>
+
+<div markdown="1">
+* dynamic, maximum of 2 * M100
+</div>
+
+ <div class="row">
+ <div class="col">
+ <h3>Emission curve</h3>
+ </div>
+ </div>
+
+<div markdown="1">
+* first, main curve: ~18.132 million coins by the end of May 2022
+* then, tail curve: 0.6 XMR per 2-minute block, kicks in once main emission is done, translates to <1% inflation decreasing over time
+* see [charts and details](https://www.reddit.com/r/Monero/comments/512kwh/useful_for_learning_about_monero_coin_emission/)
+</div>
+
+ <div class="row">
+ <div class="col">
+ <h3>Max supply</h3>
+ </div>
+ </div>
+
+<div markdown="1">
+* infinite
+</div>
+
+ <div class="row">
+ <div class="col">
+ <h3>Sender privacy</h3>
+ </div>
+ </div>
+
+<div markdown="1">
+* Ring signatures
+</div>
+
+ <div class="row">
+ <div class="col">
+ <h3>Recipient privacy</h3>
+ </div>
+ </div>
+
+<div markdown="1">
+* Stealth addresses
+</div>
+
+ <div class="row">
+ <div class="col">
+ <h3>Amount obfuscation</h3>
+ </div>
+ </div>
+
+<div markdown="1">
+* Ring confidential transactions
+</div>
+
+ </div>
+ </div>
+ <!-- end right one-third block-->
+ </div>
+
+ </section>
+</div>
diff --git a/_i18n/template/the-monero-project.md b/_i18n/template/the-monero-project.md
new file mode 100644
index 0000000000000000000000000000000000000000..06fac4f50d729242bcd34f0d8b04cda9c4c92152
--- /dev/null
+++ b/_i18n/template/the-monero-project.md
@@ -0,0 +1,45 @@
+{% include untranslated.html %}
+<div class="site-wrap">
+<section class="container">
+ <div class="row">
+ <div class="left half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Kovri</h2>
+ </div>
+ </div>
+<div class="row start-xs monero-project" markdown="1">
+
+The Kovri project uses end-to-end encryption so that neither the sender nor receiver of a Monero transaction need to reveal their IP address to the other side or to third-party observers (the blockchain). This is done using the same technology that powers the dark net, i2p (Invisible Internet Protocol). The project is currently in heavy, active development and is not yet integrated with Monero.
+
+</div>
+ <div class="row center-xs">
+ <p><a href="https://www.getkovri.org" class="btn-link btn-fixed">Visit Kovri Website</a></p>
+ </div>
+ </div>
+ </div>
+ <div class="right half col-lg-6 col-md-6 col-sm-12 col-xs-12">
+ <div class="info-block">
+ <div class="row center-xs">
+ <div class="col">
+ <h2>Open Alias</h2>
+ </div>
+ </div>
+<div class="row start-xs monero-project" markdown="1">
+
+The OpenAlias project simplifies cryptocurrency payments by providing FQDNs (Fully Qualified Domain Names, i.e. example.openalias.org) for Monero wallet addresses in a way that ensures everyone's privacy is secure. The project is well underway and has already been implemented in many Monero wallets.
+
+
+
+</div>
+
+ <div class="row center-xs">
+ <p><a href="https://www.openalias.org" class="btn-link btn-fixed">Visit OpenAlias Website</a></p>
+ </div>
+
+ </div>
+ </div>
+ </div>
+</section>
+</div>
\ No newline at end of file
diff --git a/_includes/footer.html b/_includes/footer.html
index d15590f6b18ac9b044056115eeaf0e2978269a04..48099ee48b153d41972a17529f34533922a9242a 100644
--- a/_includes/footer.html
+++ b/_includes/footer.html
@@ -1,60 +1,40 @@
<footer class="container-fluid">
<div class="container">
<div class="row around-xs footer-wrapper">
- <div class="col-sm-3 col-xs-6">
- <h3>Resources</h3>
- <ul class="list-unstyled">
- <li><a href="/resources/about/" class="white">About Monero</a></li>
- <li><a href="/resources/moneropedia/" class="white">Moneropedia</a></li>
- <li><a href="/resources/developer-guides/" class="white">Developer Guides</a></li>
- <li><a href="/resources/user-guides/" class="white">User Guides</a></li>
- <li><a href="https://getmonero.org/feed.xml" class="white">RSS Feed</a></li>
- </ul>
- </div>
- <div class="col-sm-3 col-xs-6">
- <h3>IRC Channels</h3>
- <ul class="list-unstyled">
- <li><a href="irc://chat.freenode.net/#monero" class="white">#monero (General)</a></li>
- <li><a href="irc://chat.freenode.net/#monero-dev" class="white">#monero-dev (Development)</a></li>
- <li><a href="irc://chat.freenode.net/#monero-markets" class="white">#monero-markets (Markets)</a></li>
- <li><a href="irc://chat.freenode.net/#monero-pools" class="white">#monero-pools (Mining)</a></li>
- <li><a href="irc://chat.freenode.net/#monero-community" class="white">#monero-community (Community)</a></li>
- <li><a href="irc://chat.freenode.net/#monero-translations" class="white">#monero-translations (Localization)</a></li>
- </ul>
- </div>
- <div class="col-sm-3 col-xs-6">
- <h3>Community</h3>
- <ul class="list-unstyled">
- <li><a href="https://reddit.com/r/monero" class="white">Reddit</a></li>
- <li><a href="https://monero.stackexchange.com" class="white">Stack Exchange</a></li>
- <li><a href="https://bitcointalk.org/index.php?topic=583449.0" class="white">BitcoinTalk Thread</a></li>
- <li><a href="https://mattermost.getmonero.org" class="white">MatterMost Chat</a></li>
- <li><a href="https://telegram.me/bitmonero" class="white">Telegram Chat</a></li>
- </ul>
- </div>
- <div class="col-sm-3 col-xs-6">
- <h3>The Monero Project</h3>
- <ul class="list-unstyled">
- <li><a href="https://openalias.org" class="white">Open Alias</a></li>
- <li><a href="https://getkovri.org" class="white">Kovri</a></li>
- <li><a href="/resources/research-lab/" class="white">Monero Research Lab</a></li>
- <li><a href="/press-kit/" class="white">Monero Press Kit</a></li>
- </ul>
- </div>
- </div>
+ {% for item in site.data.lang[site.lang].footer-1 %}
+ <div class="col-sm-3 col-xs-6">
+ <h3>{{item.title}}</h3>
+ <ul class="list-unstyled">
+ {% for entry in item.subfolderitems %}
+ {% if entry.url contains 'https://' %}
+ <li><a class="white" href="{{ entry.url }}">{{ entry.name }}</a></li>
+ {%elsif entry.url contains 'irc'%}
+ <li><a class="white" href="{{ entry.url }}">{{ entry.name }}</a></li>
+ {%else%}
+ <li><a class="white" href="{{site.baseurl}}/{{ entry.url }}">{{ entry.name }}</a></li>
+ {%endif%}
+ {% endfor %}
+ </ul>
+ </div>
+ {% endfor %}
<div class="row center-xs">
<div class="social-icons">
</div>
<div class="footer-links">
<ul class="list-unstyled list-inline">
- <li><a href="/legal/" class="white footer-link">Legal</a></li>
- <li><a href="https://github.com/monero-project" class="white footer-link">Source Code</a></li>
- <li><a href="/resources/technical-specs/" class="white footer-link">Technical Specs</a></li>
+ {% for item in site.data.lang[site.lang].footer-2 %}
+ {% if item.url contains 'https://' %}
+ <li><a href="{{item.url}}" class="white footer-link">{{item.name}}</a></li>
+ {%else%}
+ <li><a href="{{site.baseurl}}/{{item.url}}" class="white footer-link">{{item.name}}</a></li>
+ {%endif%}
+ {% endfor %}
</ul>
</div>
</div>
+ </div>
</div>
- </footer>
+</footer>
<!-- JS -->
diff --git a/_includes/head.html b/_includes/head.html
index 5e3b12e080b2a316396e7f1b8123fb88435b0761..a4217b0f4cea7a87f53c8a39f81276cf87beba14 100644
--- a/_includes/head.html
+++ b/_includes/head.html
@@ -3,7 +3,12 @@
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
- <title>{% if page.entry %}{{ page.entry }} | {% t global.wiki %} | {% t index.page_title %}{% elsif tag %}{% t global.tags %}: {{ tag.name }} | {% t index.page_title %}{% elsif page.title %}{{ page.title }} | {% t index.page_title %}{% else %}{% t index.page_title %}{% endif %}</title>
+ <title>
+ {% if page.entry %}{{ page.entry }} | {% t global.wiki %} | {% t index.page_title %}
+ {% elsif tag %}{% t global.tags %}: {{ tag.name }} | {% t index.page_title %}
+ {% elsif page.title contains "titles." %}{% t page.title %} | {% t index.page_title %}
+ {% elsif page.title %} {{page.title}} | {% t index.page_title %}
+ {% else %}{% t index.page_title %}{% endif %}</title>
<meta name="description" content="{% if page.entry %}{{ page.entry }}: {{ page.summary }} [{% t global.wikimeta %}]{% elsif tag %}{% t global.tagsmeta %}: {{ tag.name }}{% elsif page.meta %}{{ page.meta }}{% elsif page.title %}{{ page.title }} [{% t global.titlemeta %}]{% else %}{{ site.description }}{% endif %}">
<meta name="keywords" content="{{ site.keywords }}">
diff --git a/_includes/header.html b/_includes/header.html
index e71bf3dcb8ce27ad801ecd592d0e20bdfb382855..984f1587e08640371f8b5cd0b95d4a6d5c205de8 100644
--- a/_includes/header.html
+++ b/_includes/header.html
@@ -1,69 +1,27 @@
+{%assign counter=0%}
<div class="mob-nav">
<input class="burger-check" id="mobile-burger" type="checkbox"><label for="mobile-burger" class="burger"></label>
<div class="slide-in-nav">
<div class="container slide-in">
+ {% for item in site.data.lang[site.lang].navigation %}
<div class="row">
<div class="col-xs-12 dropdown text-center nav-item">
- <label for="drop1">Get Started<div class="arrow-down"></div></label>
- <input class="burger-checkdropdown" id="drop1" type="checkbox">
+ {% if item.subfolderitems %}
+ {%assign counter=counter | plus: 1%}
+ <label for="drop{{counter}}">{{item.title}}<div class="arrow-down"></div></label>
+ <input class="burger-checkdropdown" id="drop{{counter}}" type="checkbox">
<div class="dropdown-content">
- <a href="/get-started/what-is-monero/">What Is Monero?</a>
- <a href="/get-started/using/">Using</a>
- <a href="/get-started/accepting/">Accepting</a>
- <a href="/get-started/contributing/">Contributing</a>
- <a href="/get-started/mining/">Mining</a>
- <a href="/get-started/faq">FAQ</a>
+ {% for entry in item.subfolderitems %}
+ <a href="{{site.baseurl}}/{{ entry.url }}">{{ entry.page }}</a>
+ {% endfor %}
</div>
+ {% else %}
+ <a href="{{site.baseurl}}/{{item.url}}">{{item.title}}</a>
+ {% endif %}
</div>
</div>
- <div class="row">
- <div class="col-xs-12">
- <div class="text-center nav-item">
- <a href="/downloads/">Downloads</a>
- </div>
- </div>
- </div>
- <div class="row">
- <div class="col-xs-12 dropdown text-center nav-item">
- <label for="drop2">Recent News<div class="arrow-down"></div></label>
- <input class="burger-checkdropdown" id="drop2" type="checkbox">
- <div class="dropdown-content">
- <a href="/blog/">All Posts</a>
- <a href="/blog/tags/monero%20missives.html">Missives</a>
- <a href="/blog/tags/dev%20diaries.html">Meeting Logs</a>
- <a href="/blog/tags/releases.html">Releases</a>
- </div>
- </div>
- </div>
- <div class="row">
- <div class="col-xs-12 dropdown text-center nav-item">
- <label for="drop3">Community<div class="arrow-down"></div></label>
- <input class="burger-checkdropdown" id="drop3" type="checkbox">
- <div class="dropdown-content">
- <a href="/community/team/">Team</a>
- <a href="/community/hangouts/">Hangouts</a>
- <a href="/community/events/">Events</a>
- <a href="/community/sponsorships/">Sponsorships</a>
- <a href="/community/merchants/">Merchants</a>
- </div>
- </div>
- </div>
- <div class="row">
- <div class="col-xs-12 dropdown text-center nav-item">
- <label for="drop4">Resources<div class="arrow-down"></div></label>
- <input class="burger-checkdropdown" id="drop4" type="checkbox">
- <div class="dropdown-content">
- <a href="/resources/about/">About</a>
- <a href="/resources/roadmap/">Roadmap</a>
- <a href="/resources/research-lab/">Monero Research Lab</a>
- <a href="/resources/moneropedia/">Moneropedia</a>
- <a href="/resources/user-guides/">User Guides</a>
- <a href="/resources/developer-guides/">Developer Guides</a>
- <a href="/resources/technical-specs/">Technical Specs</a>
- </div>
- </div>
- </div>
+ {% endfor %}
<div class="row">
<div class="col-xs-12">
<div class="text-center nav-item mob">
@@ -81,7 +39,7 @@
<div class="row">
<div class="col-xs-12">
<div class="text-center nav-item mob">
- <a href="/the-monero-project/">The Monero Project</a>
+ <a href="{{site.baseurl}}/the-monero-project/">The Monero Project</a>
</div>
</div>
</div>
@@ -89,19 +47,51 @@
</div>
</div>
+
<div class="desktop-nav">
<nav class="container">
<div class="topnav">
<div class="row middle-xs">
<div class="col-lg-4 col-md-4 col-sm-4 col-xs-4">
- <a href="/"><img src="/img/monero-logo.png" alt="Monero Logo" class="monero-logo"></a>
+ <a href="{% if site.lang == 'en' %}
+
+ {{ site.baseurl_root }}/
+
+ {% else %}
+
+ {{ site.baseurl_root }}/{{site.lang}}
+
+ {% endif %}"><img src="/img/monero-logo.png" alt="Monero Logo" class="monero-logo"></a>
</div>
<div class="col-lg-8 col-md-8 col-sm-8 topnav-list end-xs">
- <div class="row end-xs">
+ <div class="row end-xs middle-xs">
<div class="col-md-12">
- <a href="https://forum.getmonero.org" class="mob top-link col-md-4">Forum Funding System</a>
- <a href="https://github.com/monero-project/meta/blob/master/VULNERABILITY_RESPONSE_PROCESS.md" class="mob top-link col-md-4">Vulnerability Response</a>
- <a href="/the-monero-project/" class="mob top-link col-md-3">The Monero Project</a>
+ <a href="https://forum.getmonero.org" class="top-link">Forum Funding System</a>
+ <a href="https://github.com/monero-project/meta/blob/master/VULNERABILITY_RESPONSE_PROCESS.md" class="top-link">Vulnerability Response</a>
+ <a href="{{site.baseurl}}/the-monero-project/" class="top-link">The Monero Project</a>
+ <div href="#" class="dropdown top-link language-change">
+ <input class="burger-checkdropdown" id="langdrop" type="checkbox">
+ <label for="langdrop">{% for lang in site.languages %}
+
+ {% if lang == site.lang %}
+
+ {% t langs.{{ lang }} %}
+
+ {%endif%}
+
+ {%endfor%}<div class="arrow-down"></div></label>
+ <div class="dropdown-content text-center">
+ {% for lang in site.languages %}
+ {% unless site.lang == lang %}
+ {% if lang == site.default_lang %}
+ <a href="{{ site.baseurl_root }}{{ page.url }}" >{% t langs.{{ lang }} %}</a>
+ {% else %}
+ <a href="{{ site.baseurl_root }}/{{ lang }}{{ page.url }}" >{% t langs.{{ lang }} %}</a>
+ {% endif %}
+ {% endunless %}
+ {% endfor %}
+ </div>
+ </div>
</div>
</div>
</div>
@@ -110,63 +100,61 @@
<div class="botnav white-nav">
<input class="burger-check" id="burger-check" type="checkbox"><label for="burger-check" class="burger"></label>
<div class="row between-xs nav-items">
+ {% for item in site.data.lang[site.lang].navigation %}
<div class="col dropdown nav-item">
- <label for="desktopdrop1">Get Started<div class="arrow-down"></div></label>
+ {% if item.subfolderitems %}
+ <label for="desktopdrop1">{{item.title}}<div class="arrow-down"></div></label>
<input class="burger-checkdropdown" id="desktopdrop1" type="checkbox">
<div class="dropdown-content">
- <a href="/get-started/what-is-monero/">What Is Monero?</a>
- <a href="/get-started/using/">Using</a>
- <a href="/get-started/accepting/">Accepting</a>
- <a href="/get-started/contributing/">Contributing</a>
- <a href="/get-started/mining/">Mining</a>
- <a href="/get-started/faq">FAQ</a>
+ {% for entry in item.subfolderitems %}
+ <a href="{{site.baseurl}}/{{ entry.url }}">{{ entry.page }}</a>
+ {% endfor %}
</div>
+ {% else %}
+ <a href="{{site.baseurl}}/{{item.url}}">{{item.title}}</a>
+ {% endif %}
</div>
- <div class="col nav-item">
- <a href="/downloads/">Downloads</a>
- </div>
- <div class="col dropdown nav-item">
- <label for="desktopdrop2">Recent News<div class="arrow-down"></div></label>
- <input class="burger-checkdropdown" id="desktopdrop2" type="checkbox">
- <div class="dropdown-content">
- <a href="/blog/">All Posts</a>
- <a href="/blog/tags/monero%20missives.html">Missives</a>
- <a href="/blog/tags/dev%20diaries.html">Meeting Logs</a>
- <a href="/blog/tags/releases.html">Releases</a>
- </div>
- </div>
- <div class="col dropdown nav-item">
- <label for="desktopdrop3">Community<div class="arrow-down"></div></label>
- <input class="burger-checkdropdown" id="desktopdrop3" type="checkbox">
- <div class="dropdown-content">
- <a href="/community/team/">Team</a>
- <a href="/community/hangouts/">Hangouts</a>
- <a href="/community/events/">Events</a>
- <a href="/community/sponsorships/">Sponsorships</a>
- <a href="/community/merchants/">Merchants</a>
- </div>
- </div>
- <div class="col dropdown nav-item">
- <label for="desktopdrop4">Resources<div class="arrow-down"></div></label>
- <input class="burger-checkdropdown" id="desktopdrop4" type="checkbox">
- <div class="dropdown-content">
- <a href="/resources/about/">About</a>
- <a href="/resources/roadmap/">Roadmap</a>
- <a href="/resources/research-lab/">Research Lab</a>
- <a href="/resources/moneropedia/">Moneropedia</a>
- <a href="/resources/user-guides/">User Guides</a>
- <a href="/resources/developer-guides/">Developer Guides</a>
- <a href="/resources/technical-specs/">Technical Specs</a>
- </div>
- </div>
+ {% endfor %}
</div>
</div>
</nav>
</div>
<div class="mob bot-nav white-nav">
- <div class="row center-xs">
+ <div class="row center-xs middle-xs">
<div class="col-xs-6">
- <a href="/"><img src="/img/monero-logo.png" alt="Monero Logo" class="monero-logo"></a>
+ <a href="{% if site.lang == 'en' %}
+
+ {{ site.baseurl_root }}/
+
+ {% else %}
+
+ {{ site.baseurl_root }}/{{site.lang}}
+
+ {% endif %}"><img src="/img/monero-logo.png" alt="Monero Logo" class="monero-logo"></a>
</div>
+ <div class="dropdown col-xs-6 text-center mob-language-change">
+ <input class="burger-checkdropdown" id="moblangdrop" type="checkbox">
+ <label for="moblangdrop"><img src="/img/language.png" alt="Lang" class="icon-language"/><div class="arrow-down"></div></label>
+ <div class="mob dropdown-content text-center">
+ <p class="mob-lang-change mob-lang-selected">
+
+ {% for lang in site.languages %}
+ {% if site.lang == lang %}
+ {% t langs.{{ lang }} %}
+ {% endif %}
+ {% endfor %}
+
+ </p>
+ {% for lang in site.languages %}
+ {% unless site.lang == lang %}
+ {% if lang == site.default_lang %}
+ <a class="mob-lang-change" href="{{ site.baseurl_root }}{{ page.url }}" >{% t langs.{{ lang }} %}</a>
+ {% else %}
+ <a class="mob-lang-change" href="{{ site.baseurl_root }}/{{ lang }}{{ page.url }}" >{% t langs.{{ lang }} %}</a>
+ {% endif %}
+ {% endunless %}
+ {% endfor %}
+ </div>
+ </div>
</div>
</div>
diff --git a/_includes/untranslated.html b/_includes/untranslated.html
new file mode 100644
index 0000000000000000000000000000000000000000..54ee4c19d461f88e9794bf293b79fe0744979d21
--- /dev/null
+++ b/_includes/untranslated.html
@@ -0,0 +1,3 @@
+<div class="untranslated">
+ <p>{% t global.untranslated %} <a class="untranslated-link" href="https://github.com/monero-project/monero-site/blob/master/README.md">README</a>.</p>
+</div>
\ No newline at end of file
diff --git a/_layouts/customnt.html b/_layouts/customnt.html
new file mode 100644
index 0000000000000000000000000000000000000000..8ed8b39e8c905154ec759b1b3c405993bbc62b1c
--- /dev/null
+++ b/_layouts/customnt.html
@@ -0,0 +1,7 @@
+---
+layout: base
+---
+
+<div class="site-wrap">
+ {{content}}
+</div>
\ No newline at end of file
diff --git a/_layouts/default.html b/_layouts/default.html
index 94ba7876ebc23fd607723364b819fcad35f72f4e..687f0d8af35b5299e6fcd9ff293a7a58fb43d76f 100644
--- a/_layouts/default.html
+++ b/_layouts/default.html
@@ -1,5 +1,5 @@
---
layout: base
---
-<h1 class="text-center">{{page.title}}</h1>
+<h1 class="text-center">{% t page.title %}</h1>
{{content}}
\ No newline at end of file
diff --git a/_layouts/static_page.html b/_layouts/static_page.html
index e224d0197f0661370119d1f28d6f3e69997df875..95eb68b0cf977e2a0597178e8ac680c7246e37e9 100644
--- a/_layouts/static_page.html
+++ b/_layouts/static_page.html
@@ -1,7 +1,7 @@
---
layout: base
---
-<h1 class="text-center">{{page.title}}</h1>
+<h1 class="text-center">{% t page.title %}</h1>
<div class="site-wrap">
<!-- FULL WIDTH BLOCK -->
<section class="container full">
diff --git a/_layouts/user-guide.html b/_layouts/user-guide.html
new file mode 100644
index 0000000000000000000000000000000000000000..2cde2d7eb8dde7ef0cc041190f0037c84b8b9050
--- /dev/null
+++ b/_layouts/user-guide.html
@@ -0,0 +1,14 @@
+---
+layout: base
+---
+ <div class="site-wrap">
+ <!-- FULL WIDTH BLOCK -->
+ <section class="container full">
+ <div class="info-block text-adapt">
+ <div>
+ {{content}}
+ </div>
+ </div>
+ </section>
+ <!-- END FULL WIDTH BLOCK -->
+ </div>
\ No newline at end of file
diff --git a/_plugins/plugin.rb b/_plugins/plugin.rb
deleted file mode 100644
index 90191af5b0aa77a6ced15e051cfae030b3518654..0000000000000000000000000000000000000000
--- a/_plugins/plugin.rb
+++ /dev/null
@@ -1,70 +0,0 @@
-# Just a placeholder plugin to do translated strings, gives us room and scope to get the
-# jekyll-multiple-languages-plugin to work correctly
-
-module Jekyll
- module Translated
- module Strings
- module Plugin
- VERSION = "0.1"
- end
- end
- end
-end
-
-module Jekyll
- class LocalizeTag < Liquid::Tag
-
- def initialize(tag_name, key, tokens)
- super
- @key = key.strip
- end
-
- def render(context)
- if "#{context[@key]}" != "" #Check for page variable
- key = "#{context[@key]}"
- else
- key = @key
- end
-
- site = context.registers[:site]
-
- stringsfile = File.join(site.source, '_strings_en.yml')
-
- strings_en = YAML.load_file(stringsfile)
-
- translation = strings_en.access(key) if key.is_a?(String)
- if translation.nil? || translation.empty?
- Jekyll.logger.abort_with "Missing key: #{key}"
- end
-
- # If we have an @, pass the string through the markdown converter, so that we hit the Moneropedia plugin
- if translation.include? '@'
- converter = site.find_converter_instance(::Jekyll::Converters::Markdown)
- translation = converter.convert(translation)[3..-6]
- end
-
- translation
- end
- end
-
-end
-
-unless Hash.method_defined? :access
- class Hash
- def access(path)
- ret = self
- path.split('.').each do |p|
- if p.to_i.to_s == p
- ret = ret[p.to_i]
- else
- ret = ret[p.to_s] || ret[p.to_sym]
- end
- break unless ret
- end
- ret
- end
- end
-end
-
-Liquid::Template.register_tag('t', Jekyll::LocalizeTag)
-Liquid::Template.register_tag('translate', Jekyll::LocalizeTag)
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 07821e60bfa2ca4dbc0a2386d192009b9a47657c..555d65d86979c5e62d9c5238081bd5b647160935 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 84e8ae52a0f6a568deffc8f9e943e3422494abb4..e2098ee945355caaf72a02d9d50544e2a087678f 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 84806679119b03c371a92a95b0ba5b2f3422f624..714f37987ffa3ac8e8df56476e8ea7c0384bf84d 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 4164a3fe530176b5ba7429164bf612bad5c920ad..d4ba9411aa5ce547686450b282f23852225d8955 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 db3e15e738f1f73d8b4ad3a30961b776c9735ea0..1b260c9ffd6f2a19cbd4a03e8936395f509fe831 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 f494e66f311d7dd96cdafe75a025e7ced7872b2e..a04ee8b74db36fdd8badb5c9a92f043defa7c52c 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 401336d85c1caf36639dc36c2a3e641390bccc9c..359d719e0970949bc0d9035304039d75097b6adc 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 ec5db22d67ba537fc6086bbdf54b7febdc86444f..8ed95be1c6b52efd7fa61db68a12f351c22a048a 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 b86ce36dff9ca168d904a236a93862ce75f68c85..a4197bd2a448cc972792232b4ae3494502b4eb68 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 76aea4dec6303ee8df9648458c0bd12d59a84eb6..4c7baf1c533fa8176a4e71d517c994e45d24064a 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 decf34db63d606f36675ca0abad96daca7ac4a3d..ad915dce73d11311dc9fd93ca142f323e05b8aff 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
new file mode 100644
index 0000000000000000000000000000000000000000..443469fc8525f0635bb860f08888759578a9f30b
--- /dev/null
+++ b/_posts/2017-11-13-workgroups-and-resources.md
@@ -0,0 +1,45 @@
+---
+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
+---
+
+### 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
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 0000000000000000000000000000000000000000..3f79d793c6500e494a9f428ff8e13693a739b23f
--- /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
+
+**\<rehrar>** Hey everyone! I don't know if fluffypony will be here today, but let's see about getting this thing started.
+**\<rehrar>** Hello to everyone idling in the peanut gallery
+**\<msvb-lab>** Hello.
+**\<rehrar>** 2. Brief review of what's been completed since the previous meeting
+**\<rehrar>** Can we get a mini-update from dev, gui, hardware, and mrl?
+**\<sarang>** I can speak for MRL
+**\<sarang>** We've been thoroughly investigated bulletproofs, a new form of CT range proofs
+**\<hyc>** is moneromooo here?
+**\<moneromooo>** Yes
+**\<endogenic>** have one thing to bring up
+**\<endogenic>** when there's time
+**\<sarang>** They should function as essentially a drop-in replacement that is 10% the size of the original proofs (for one output; even smaller for multiple outputs)
+**\<sarang>** with about the same verification time; possibly a teensy bit faster
+**\<sarang>** Kudos to andytoshi for a lot of great help on those, and others
+**\<hyc>** it's like a TARDIS! the bigger the input the smaller the output! /s
+**\<rehrar>** So it's looking really promising that it'd be good for us?
+**\<sarang>** yes
+**\<sarang>** We'll start translating the Java test code over to C/C++ for more detailed work
+**\<suraeNoether>** it's a win-win: smaller-spaced range-proofs, with the same verification time
+**\<sarang>** There were some doubts about ver time, but we literally just had a convo over in MRL that pointed out a simple caching that helps us
+**\<rehrar>** MRL, folks. Let's give 'em a hand.
+**\<sarang>** It was pointed out, though, that there's very little randomness hanging around, which could affect storing stuff "in the randomness"
+**\<sarang>** That may be a deepe discussion for later
+**\<suraeNoether>** yeah, using these range proofs makes encrypting messages with range proofs far less do-able
+**\<sarang>** \*deeper
+**\<gingeropolous>** eh who cares
+**\<msvb-lab>** MRL is excellent, nice.
+**\<suraeNoether>** andytoshi is really the one who nailed it, btw
+**\<sarang>** aye
+**\<suraeNoether>** aaaaand all his co-authors
+**\<rehrar>** Can we send them a fruit basket?
+**\<endogenic>** +1
+**\<suraeNoether>** which has included, for a second time, Jonathan Bootle
+**\<sarang>** rehrar set up an FFS for it
+**\<sarang>** 0.2 XMR
+**\<suraeNoether>** and for the N^th time, greg maxwell
+**\<rehrar>** 100 XMR requested
+**\<rehrar>** biggest fruit basket ever
+**\<sarang>** Anyhoo, that's the big news from MRL right now, I suppose
+**\<rehrar>** awesome. Thanks so much.
+**\<suraeNoether>** multisig is looking like i will be ready to hand it off to sarang by the end of the month, as hoped.
+**\<suraeNoether>** and thats it for now
+**\<rehrar>** Anyone else have an update since the last meeting two weeks ago?
+**\<ArticMine>** This is huge from a scaling perspective
+**\<hyc>** absolutely
+**\<hyc>** dev has done a tone of PR merges latelt
+**\<hyc>** lately
+**\<rehrar>** can you summarize them?
+**\<hyc>** there's still been build issues with readline dependencies but I think they're pretty much sorted by now
+**\<hyc>** we've isolated readline from GUI dependencies, etc.
+**\<hyc>** mooo can probably summarize better
+**\<endogenic>** vtnerd says "oh good"
+**\<endogenic>** "woo"
+**\<moneromooo>** Hmm. I can go look at github:
+**\<moneromooo>** (mostly small things anyway)
+**\<rehrar>** FP confirmed he can't make it today. He sends his apologies.
+**\<moneromooo>** disguising password length in prompt I guess is still a small thing, but user visible
+**\<moneromooo>** less unnecessary locking in some DB readers, which should speed up some RPC
+**\<moneromooo>** Fixes for BSD build
+**\<moneromooo>** The wallet does not fetch unneeded hashes anymore (ie, starts direct from 1.4e6)
+**\<moneromooo>** CORS (for those who know what it is)
+**\<moneromooo>** A fix for show\_transfers missing more than one incoming input in a tx
+**\<moneromooo>** And I think the rest is either prior to last meeting, or small/internal stuff.
+**\<hyc>** yeah but it comprises a couple dozen PRs between then and now
+**\<rehrar>** Alright, awesome. Thanks moneromooo.
+**\<rehrar>** hardware, I know you give updates in community, but I think most of us that know are excited about the rapid progress you're making
+**\<rehrar>** care to share something small about what's been going down?
+**\<msvb-lab>** Hardware; we've settled our initial workflows and have built a twenty strong team. Journals are taking notice (see press) and the project is moving along.
+**\<msvb-lab>** https://taiga.getmonero.org/project/michael-rfc-hwallet-1-implementation/wiki/press/
+**\<msvb-lab>** I'll mark our forum proposal milestone 1 as concluded today probably.
+**\<msvb-lab>** We now have an open call to any interested in a hardware wallet, become part of the project and possibly test a prototype. See:
+**\<msvb-lab>** https://taiga.getmonero.org/project/michael-rfc-hwallet-1-implementation/wiki/preview/
+**\<msvb-lab>** I'll demonstrate our two current working protoypes at this week's first ever Monero Munich meeting.
+**\<msvb-lab>** That's all, any questions?
+**\<sgp>** What do you expect those who receive the prototypes to test?
+**\<msvb-lab>** Very weak expectations, hopefully each finds their own way to contribute and strengthen the project.
+**\<msvb-lab>** There's a test plan page, where people can make comments while testing.
+**\<msvb-lab>** But that is just one of many choices, each individual can make on their own.
+**\<msvb-lab>** Pretty lame answer no?
+**\<rehrar>** Alright, thanks msvb-lab!
+**\<msvb-lab>** Thanks for the opportunity.
+**\<moneromooo>** Sounds like pretty nice stuff is going on there, congrats :)
+**\<hyc>** (I counted 72 PRs merged since last dev meeting)
+**\<msvb-lab>** hyc: Who make most of the merges, fluffy?
+**\<rehrar>** So, we've got Code + ticket discussion / Q & A time available for the devs to discuss dev-y things. But all the mergy stuff may have to wait because of FP absence, but if there's other business to take care of, devs you have the floor
+**\<hyc>** yes he does all the merges
+**\<hyc>** we didn't get a report from GUI
+**\<rehrar>** oh, right! so sorry.
+**\<rehrar>** Anybody working on GUI have stuff to talk about.
+**\<unknownids>** ping Jaquee ?
+**\<endogenic>** so i've been chatting with mooo, Jaquee, and vtnerd recently about integrating MyMonero with the native mainline libwallet
+**\<Jaquee>** sorry. i'm on the run
+**\<endogenic>** signs point to integrating with wallet\_api
+**\<endogenic>** I may end up tackling a small portion of factoring wallet2
+**\<rehrar>** ok, no worries Jaquee.
+**\<moneromooo>** As long as not too many gratuitous changes ^\_^
+**\<endogenic>** 100% mooo
+**\<hyc>** all variable and class names being filtered thru pig-latin
+**\<gingeropolous>** dsc, in here :)
+**\<dsc>** :)
+**\<msvb-lab>** Is our GUI crew considered only monero-gui, or are mymonero.com and Moneruj (Android) included as well?
+**\<dsc>** has it started?
+**\<endogenic>** lol hyc
+**\<rehrar>** I think GUI crew is people who work on the monero-gui repo
+**\<rehrar>** mymonero and Monerujo are their own thing
+**\<rehrar>** dsc has what started?
+**\<dsc>** the meeting :D
+**\<rehrar>** oh, yeah. We're about half hour in. :)
+**\<hyc>** oh - that's worth mentioning too - the repo is now properly named monero-gui, no longer monero-core
+**\<msvb-lab>** rehrar: So Monerujo communicate on a different channel, right?
+**\<rbrunner>** That rename is a milestone :)
+**\<rehrar>** Monerujo utilizes the Mattermost where they have a private channel for the devs and core team, and a public channel for questions. They've also got a Taiga to track progress.
+**\<dsc>** aight, so I'm working on a black theme for `monero-gui` (qt5) .. learning QML in the process. Trying to get some more UX developers involved and generally just trying to document things as I go
+**\<rehrar>** I can rep Monerujo though, as I'm heavily involved with them
+**\<rehrar>** they've got some exciting stuff coming
+**\<rehrar>** yes, can you link your thread dsc?
+**\<dsc>** sure
+**\<rehrar>** The one you made a few days ago.
+**\<dsc>** https://www.reddit.com/r/Monero/comments/7dvwq0/contributing_to_monero_as_an_ux_developer_short/
+**\<rehrar>** in the comments there are the various proposals for redesigning the GUI. Are there any thoughts on any of those?
+**\<rehrar>** well, first dsc you wanted to say something, go ahead. :)
+**\<dsc>** No I was finished :P
+**\<dsc>** but to answer your question: There are 3 UI proposals of which I picked the one that was most trivial to implement
+**\<dsc>** seeing as I'm just one guy with zero QML experience, hehe.
+**\<dEBRUYNE>** rehrar: Basically we're first kind of going for the dark theme, which will have a light mode as well
+**\<dEBRUYNE>** Because it's most trivial to implement
+**\<dEBRUYNE>** (only requires minor changes to the current design)
+**\<rehrar>** https://github.com/monero-project/monero-core/issues/419
+**\<rehrar>** https://github.com/monero-project/monero-core/issues/869
+**\<rehrar>** https://github.com/monero-project/monero-core/issues/949
+**\<dEBRUYNE>** Some screenshots -> https://i.imgur.com/89YFUj7.png
+**\<rehrar>** for those interested
+**\<rehrar>** Ok. Cool deal!
+**\<dEBRUYNE>** To clarify, the dark theme is #949
+**\<hyc>** cool
+**\<dEBRUYNE>** dsc also made a PR which should make the GUI more responsive
+**\<dsc>** cant make any predictions as to when I have some tangible, taking quite some time...!
+**\<dsc>** s/some/something/
+**\<dEBRUYNE>** Also, we're aiming to include subaddresses and multisig somewhere in the future^tm
+**\<dEBRUYNE>** And, once there is a core appstore account, we'll start testing the ios port of the GUI
+**\<dEBRUYNE>** There'll be an android port as well, fwiw
+**\<msvb-lab>** dEBRUYNE: Is Qt5 easy to port to mobile?
+**\<sgp>** Is there a new android APK to test? I last saw one months ago
+**\<dEBRUYNE>** sgp: Buildbot produces APKs iirc
+**\<dEBRUYNE>** Let me check
+**\<pigeons>** No that isn't setup now
+**\<dEBRUYNE>** msvb-lab: Jaquee did it, so better to ask him :P
+**\<pigeons>** I can't promise next week even, very busy
+**\<dsc>** rehrar: To give you an idea, right now I have this: https://i.imgur.com/iLwupdB.png
+**\<dsc>** or to give anyone an idea for that matter :)
+**\<serhack>** Hello
+**\<rehrar>** looks pretty chill imo :D
+**\<dsc>** aye aye
+**\<dsc>** WIP ofc :)
+**\<rehrar>** I personally think there needs to be a bit of a restructuring of some info, but this is a good meantime
+**\<dsc>** agreed
+**\<hyc>** good stuff
+**\<hyc>** would be nice to get a more recent android build up for people to test
+**\<rehrar>** Alright. That's it from GUI? No other opinions on dEBRUYNE and dsc stuff either?
+**\<hyc>** looks like we can move on to ticket Q/A
+**\<rehrar>** ok Code + ticket discussion / Q & A
+**\<rehrar>** hyc moneromooo can you two take the lead for this?
+**\<moneromooo>** Well, if anyone has questions about them, please ask.
+**\<hyc>** I'd leave it to mooo. I'm not aware of any open questions
+**\<hyc>** ^^
+**\<dsc>** ticket Q/A \!= discussing open PR's, right?
+**\<hyc>** sure
+**\<hyc>** ask away
+**\<dsc>** low hanging fruit PRs (that can probably be merged): #919, #954, #963 on monero-gui
+**\<dsc>** not so much a question ^\_^
+**\<hyc>** probably ask luigi to merge them if fluffy is unavailable
+**\<iDunk>** luigi merges GUI PRs anyway :)
+**\<dsc>** alright
+**\<rehrar>** I think luigi is out for a few days, so be patient. (:
+**\<rehrar>** Alrighty, shall we move on?
+**\<rehrar>** FFS Formalization: https://github.com/monero-project/meta/pull/87
+**\<serhack>** Is there meeting?
+**\<hyc>** serhack started 40 minutes ago
+**\<rehrar>** we probably don't have time for a large discussion (if at all), but I just wanted to encourage the devs to take a look at the PR
+**\<serhack>** Oh
+**\<serhack>** I forgot it
+**\<rehrar>** The idea of having a set of formalized guidelines for FFS proposals going forward has been thrown around a lot. It'd be good to get some opinions on how this is laid out and any concerns that may arise from it.
+**\<serhack>** I didn't understand well: is the project funded by ffs an Official project?
+**\<ArticMine>** Does the current system work?
+**\<rehrar>** There's been hiccups ArticMine. fireice and guzzi come to mind.
+**\<endogenic>** those seem like complete outliers :P
+**\<endogenic>** not exactly legit claims to issues imo
+**\<rehrar>** Largely based on de facto expectations that are not actually formalized.
+**\<msvb-lab>** How do we learn about the hickups mentioned (in order to understand context?)
+**\<endogenic>** but proposals could stand to be more concrete, specific, detailed,
+**\<endogenic>** rehrar: formalization can be a bit of a rabbit hole as well
+**\<endogenic>** sometimes humans need to be involved
+**\<endogenic>** ppl need to recognize the situation before a formal plan can be applied
+**\<hyc>** indeed. current US political situation reflects this - institutions are designed assuming good faith in all participants
+**\<endogenic>** but if the situation is not able to be recognized by ppl then how can it be applied for the desired result?
+**\<hyc>** nobody can take all the time needed to identify every possible abusable loophole
+**\<rehrar>** What we have currently is a Core Team centered way of resolving disputes that, to my knowledge, hasn't really been utilized since I've been here
+**\<rehrar>** since we've got that right now, maybe we stick with it?
+**\<endogenic>** but identifying loopholes and plugging them is not a bad thing
+**\<endogenic>** it's just that they need to be done by humans imo
+**\<ArticMine>** We may need some tweaking to deal with the hiccups; but as afar as I can see at a fundamental level the system is working
+**\<rehrar>** don't know where else the graphic is, so I'll just link it here: https://getkovri.org/contributing.html
+**\<rehrar>** bottom of the page
+**\<rehrar>** This has not been formally replaced, so it is currently active. We can discuss that at a later time though. Let's move on.
+**\<rehrar>** 5. Any additional meeting items
+**\<rehrar>** If anyone has anything, speak up. :)
+**\<moneromooo>** If anyone wants to test multisig, feel free. PR 2134.
+**\<gingeropolous>** is there a set date for the next code freeze?
+**\<serhack>** A little update by me about Monero Integrations
+**\<rehrar>** go for it serhack
+**\<serhack>** So we (I and cryptochangements) are going to release Magento Plugin, In the past few weeks, we worked on a new cool payment box for Monero Integrations.
+**\<serhack>**
+**\<serhack>** I am currently working on OpenCart too so I think we can release Magento payment box the next week..
+**\<serhack>**
+**\<serhack>** I have talked to OpenBazaar too and they have told me that Monero + Openbazaar would be nice.. it will be a difficult task but I think I can do it
+**\<serhack>** you can go on, rehrar
+**\<moneromooo>** Everytime I read OpenBazaar, it makes me want to punch that scammer from a few years back...
+**\<rehrar>** alright, thanks man :)
+**\<rehrar>** atrides?
+**\<moneromooo>** That's the one.
+**\<rehrar>** doesn't he still run Dwarfpool?
+**\<gingeropolous>** yeah, and ppl still mine on it
+**\<rehrar>** We should encourage them not to
+**\<rehrar>** Either way: 6. Confirm next meeting date/time
+**\<rehrar>** December 3rd? Same time?
+**\<gingeropolous>** so no freeze date, eh?
+**\<rehrar>** Should we move time because daylight savings?
+**\<moneromooo>** About mid december
+**\<gingeropolous>** word.
+**\<ArticMine>** Please do not move the time
+**\<moneromooo>** Or january. Unclear.
+**\<rehrar>** ok, time not moved
+**\<rehrar>** FP would have a better answer?
+**\<hyc>** isn't a release due in January?
+**\<hyc>** and we're supposed to freeze a month before
+**\<iDunk>** March
+**\<gingeropolous>** well dec or jan gives us 3 months
+**\<hyc>** ok
+**\<rehrar>** There's a new freeze/release schedule isn't there?
+**\<hyc>** mebbe someone can open a meta issue and set some dates into it
+**\<gingeropolous>** i thought we had 3 months of freeze for more testing / fixing than before ....
+**\<moneromooo>** 3 months of freeze is gonna make me punch someone else :P
+**\<moneromooo>** It's branch, then release from the brnch aftrer 2-3 months.
+**\<moneromooo>** It's already painful when stuff doens't get merged after a month.
+**\<ArticMine>** The big one is the bullet proofs
+**\<gingeropolous>** right. i thought branch is a freeze... i.e., feature freeze.... i.e., freeze on adding wacky new stuff that requires bandaloots and warples
+**\<moneromooo>** That's not likely to be ready by then.
+**\<gingeropolous>** but yeah... perhaps that should be documented somewhere
+**\<rehrar>** (Not to interrupt, but meeting is over for those who need to go, discussion can of course continue)
+**\<rehrar>** Alright. You guys are the best! thanks for being a part of this community, and developing the software we all know and love as Morono
+**\<msvb-lab>** rehrar: Thanks, good flow of topics, great moderation.
\ No newline at end of file
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 0000000000000000000000000000000000000000..c35b87e8e8ec024f90da81d9fa6ca28c10c936c6
--- /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]
+author: dEBRUYNE / fluffypony
+---
+
+# Logs
+
+**\<sgp>** We would like to welcome everyone to this Monero Community Meeting!
+**\<sgp>** Link to agenda on GitHub: https://github.com/monero-project/meta/issues/137
+**\<sgp>** Monero Community meetings are a discussion place for anything going on in the Monero Community. We use meetings to encourage the community to share ideas and provide support.
+**\<sgp>** 1. Greetings
+**\<rehrar>** What up kids?
+**\<cryptochangement>** hey all!
+**\<ErCiccione>** Hi!
+**\<sgp>** Don't be shy :)
+**\<msvb-lab>** Hello.
+**\<sgp>** 2. Community highlights
+**\<sgp>** For a great weekly summary, please read the Monero Observer: http://monero-observer.com/
+**\<sgp>** 3. FFS updates
+**\<sgp>** To those who haven't heard of the FFS before, it stands for the "Forum Funding System"
+**\<sgp>** a. RFC-HWALLET-1 project progress
+**\<sgp>** msvb-lab: do you have any updates you want to talk about?
+**\<serhack>** hii :)
+**\<msvb-lab>** Sorry, delay...
+**\<msvb-lab>** We had a great Munich Monero meeting, where we mostly talked about forming a local group, regular meetings, the (nearby) Vienna event(s) of December, and the hardware team's efforts (with a few boards passed around.)
+**\<msvb-lab>** As far as hardware goes, there's nothing organised to say. Lots of ordering of parts and waiting for them to arrive, some porting of designs to the EDA CAD application we're using.
+**\<msvb-lab>** Laser cutter considerations, and so on.
+**\<msvb-lab>** Any questions about hardware wallets?
+**\<msvb-lab>** We have three designs being worked on in parallel, I could talk an hour but will spare the bore.
+**\<ErCiccione>** the local group with regular meetings sounds great
+**\<msvb-lab>** It's important for whoever would like to test a real device in their hands to sign up as a team member by clicking 'Contact the project' on the site:
+**\<msvb-lab>** https://taiga.getmonero.org/project/michael-rfc-hwallet-1-implementation/
+**\<msvb-lab>** ErCiccione: We had about twenty people there, and passed around artwork from Deborah.
+**\<msvb-lab>** So we've definitely reached critical mass in Munich, Berlin was there long ago.
+**\<serhack>** great, this is Monero community
+**\<sgp>** msvb-lab: learning about these three designs would be a good read. If you want to work with me on writing something about these, I think the community would appreciate it
+**\<cryptochangement>** yes we would :)
+**\<serhack>** sgp: ;)
+**\<msvb-lab>** A good place to put the informatino about the various device types is:
+**\<msvb-lab>** https://taiga.getmonero.org/project/michael-rfc-hwallet-1-implementation/wiki/protos
+**\<msvb-lab>** So one is called 'MCUDev' (now renamed to 'Monezor'), another is 'Breakneck', we need a name for the device that resembles Ledger Blue's design.
+**\<msvb-lab>** ...and so on.
+**\<serhack>** nice
+**\<sgp>** Ok, good to know
+**\<sgp>** Anything else on the hardware wallet front?
+**\<msvb-lab>** Not from me.
+**\<sgp>** b. Monero Integrations
+**\<sgp>** cryptochangement, want to take it from here?
+**\<cryptochangement>** serhack, you wanna go first?
+**\<serhack>** yes, thanks
+**\<cryptochangement>** ok cool
+**\<serhack>** okay guys, the latest update before today was 1 month ago so more surprise are coming
+**\<serhack>** first of all we have redesigned the payment box
+**\<cryptochangement>** serhack: im actually pretty sure i talked about that last meeting ;)
+**\<serhack>** second, a helpful security engineer have helped them in order to fix a potentially sql injection on payment id
+**\<serhack>** (I mean on reddit, it seems only few people read community meeting cryptochangements)
+**\<cryptochangement>** thats fair :p
+**\<serhack>** https://imgur.com/a/MUV72
+**\<serhack>** this is the new payment box
+**\<serhack>** third, I have already contacted OpenBazaar team for implementing Monero
+**\<serhack>** We should wait for multisig
+**\<serhack>** that's all from me, go cryptochangements :)
+**\<cryptochangement>** Okay so good news here
+**\<cryptochangement>** Our second milestone, the Magento plugin is finished and ready to be used by merchants!
+**\<cryptochangement>** Its all on GitHub here: https://github.com/monero-integrations/moneromagento
+**\<sgp>** hooray!
+**\<cryptochangement>** and here is a screenshot of the checkout: https://taiga.getmonero.org/media/attachments/6/0/a/5/72f4eb66138e7efd76c4abd6e7d52df16806cdc441788e61c3c8e20ec676/improvedmagento.png
+**\<serhack>** yeah, cool announcement cryptochangements!!
+**\<cryptochangement>** i should also mention that you can track a lot of our progress on taiga: https://taiga.getmonero.org/project/serhack-monero-integrations/
+**\<rehrar>** Yay Taiga!!
+**\<cryptochangement>** rehrar ive actually became rather fond of it :p
+**\<cryptochangement>** thats pretty much all, unless there are any questions
+**\<msvb-lab>** Which of these technologies resembles Bitpay most?
+**\<msvb-lab>** There are ten repositories besides magento.
+**\<serhack>** I think we should mark a thing
+**\<msvb-lab>** So if I'm a vendor who wants to be able to 'Bitpay' with XMR, which github should I look at?
+**\<serhack>** no offense to you msvb lab
+**\<cryptochangement>** msvb-lab: they all have the same design/setup they are just for different cms
+**\<serhack>** The goal of Monero integrations is removing the middleman
+**\<msvb-lab>** Oh, that makes sense.
+**\<cryptochangement>** globee is actually close to bitpay... because they actually use bitpay
+**\<msvb-lab>** I thought there was a more complex architecture. So for three different vendors with three different CMSs, they will be served by referring to the correct implementation.
+**\<msvb-lab>** That's quite good.
+**\<serhack>** yeah, msvb-lab, different e-shops but they are using the same methods in order to accept monero
+**\<sgp>** Exactly msvb-lab
+**\<sgp>** They all provide the same functionality for different systems
+**\<msvb-lab>** Is it still forbidden to talk about Globee (are there still secrets?)
+**\<cryptochangement>** the main difference between us and globee is that we dont deal with fiat. all funds go directly to your wallet with no 3rd party
+**\<msvb-lab>** Seems it would be relevant to this chapter of our meeting?
+**\<serhack>** I don't know anything about the Globee secret project
+**\<cryptochangement>** idk fluffy isnt here so you probably dont want to go spilling all of his secrets :p
+**\<rehrar>** Globee can be talked about freely. The secret project being done by Globee is best kept under wraps for now.
+**\<msvb-lab>** Okay, fine if the Globee deal or technology is still (partly) secret.
+**\<msvb-lab>** rehrar: They probably need some time still to get the design done.
+**\<sgp>** Any other updates cryptochangement/serhack? Can you remind me what integration is next?
+**\<endogenic>** well, it's just not out yet, so please don't spread confidential info
+**\<serhack>** the next is opencart
+**\<cryptochangement>** next is opencart, which is in the works
+**\<cryptochangement>** and now i think we can pass the baton
+**\<sgp>** Cool
+**\<serhack>** yes
+**\<sgp>** Thanks cryptochangement and serhack
+**\<serhack>** your welcome
+**\<sgp>** Does anyone else have a FFS update?
+**\<ErCiccione>** i wanted to say a couple of yhings
+**\<sgp>** Go ahead ErCiccione
+**\<endogenic>** also have a quick update
+**\<endogenic>** after you ErCiccione
+**\<ErCiccione>** i'll be quick endogenic
+**\<endogenic>** no need, we have 30 mins :P
+**\<ErCiccione>** I just wanted to say my FFS is in the process of being moved from Ideas to funding required, thanks to all the community for the support!
+**\<sgp>** It's a very worthy proposal imo
+**\<sgp>** From the other community feedback, it seems that other people think so too
+**\<msvb-lab>** What is the URL?
+**\<serhack>** serhack is going to donate
+**\<msvb-lab>** I can't find it.
+**\<ErCiccione>** 1 sec
+**\<ErCiccione>** https://forum.getmonero.org/6/ideas/89232/coordinator-for-localization-group-various-maintenance
+**\<ErCiccione>** it's still under ideas,but the pony said he is going to move it tonight/tomorrow
+**\<rehrar>** I have something to say about FFS in general that the people here really need to be involved with. I'll speak after ErCiccione and endogenic
+**\<ErCiccione>** thanks serhack :) and thanks sgp
+**\<endogenic>** +1 rehrar
+**\<sgp>** @ErCiccione is that all?
+**\<sgp>** Go ahead endogenic
+**\<ErCiccione>** no 1 sec
+**\<ErCiccione>** also I reorganized the Taiga of the localization project, now is easier to add a translation (there also a quick guide "how to translate the GUI")
+**\<ErCiccione>** https://taiga.getmonero.org/project/erciccione-monero-localization/
+**\<ErCiccione>** Will integrate it soon with github
+**\<ErCiccione>** that's all from me
+**\<sgp>** Great thanks
+**\<ErCiccione>** endogenic, your turn
+**\<endogenic>** so i've been speaking with sgp and some members of the monero research lab about educational hackathons, and we think a corporate sponsored kovri hackathon could be brilliant (basically, you must build something using kovri plus one or more of the libraries from the sponsors)
+**\<endogenic>** so I'd like to encourage everyone in the Monero community who is interested in getting involved with kovri or hackathons to get in touch with sgp and/or the noethers and chat with them about how you'd like to be involved
+**\<endogenic>** doesn' have to be corp sponsored but it's probably a good idea
+**\<endogenic>** they buy the food too :P
+**\<endogenic>** and they supply venue, often
+**\<endogenic>** unless it's done at a library or a school like NYU
+**\<endogenic>** who has hosted such things before
+**\<endogenic>** that is all
+**\<sgp>** Ok endogenic. We can discuss this more during the open ideas time
+**\<endogenic>** oops
+**\<sgp>** Rehrar?
+**\<sgp>** No worries :)
+**\<rehrar>** Yay. My turn.
+**\<serhack>** go rehrar, make this community cool
+**\<rehrar>** Ok, as the Community workgroup, our job is several things (as you all may know). We want to make the community a good, educational, friendly place to be. And many of us head our own smaller workgroups and stuff.
+**\<rehrar>** I think we need to add something onto the goals, specifically regarding the FFS
+**\<rehrar>** The community workgroup needs to brainstorm ways that we can increase FFS giving involvement, and rely less on individuals that donate large sums.
+**\<rehrar>** There was a large push on Surae's FFS, and it was awesome to see. It's slowed down a bit, which is totally fine, and I'm sure one final Reddit post would finish it up.
+**\<rehrar>** We need to aim for getting community involvement with the FFS. Something like 0.1 XMR per person.
+**\<rehrar>** We can find ways to incentivize if we'd like, but that's not the only way.
+**\<rehrar>** We can discuss this in open ideas time, but building a culture of generosity and giving within the community should be a large priority, since the project relies on donations.
+**\<rehrar>** end
+**\<sgp>** Thanks rehrar
+**\<endogenic>** what is the cause that sarang's proposal was quickly funded while surae's was not?
+**\<rehrar>** a large donation
+**\<cryptochangement>** 0.1 XMR per person would be a dream
+**\<sgp>** I can make discussion groups for the hackathon and FFS projects in Mattermost
+**\<endogenic>** rehrar: not quite my question
+**\<endogenic>** why sarang and not surae?
+**\<rehrar>** ah, ok then
+**\<endogenic>** was there a difference in the quality of the proposals?
+**\<sgp>** @endogenic it may have been as simple as sarang's being listed first in a Reddit post or something
+**\<cryptochangement>** sgp thats what i was thinking
+**\<serhack>** I have a little idea rehrar
+**\<rehrar>** we can discuss it serhack. :)
+**\<rehrar>** Meeting continue?
+**\<endogenic>** rehrar: is your point up for further debate?
+**\<sgp>** Yeah, I would like to make sure we finish the next point
+**\<endogenic>** ok
+**\<rehrar>** I'm thinking Open Ideas time of this meeting we can discuss further
+**\<rehrar>** but of course we can debate it
+**\<sgp>** I would like to discuss rehrar's ideas later in the meeting
+**\<sgp>** 4. Discuss formation of Malware Response Group
+**\<sgp>** Fluffypony and tuckerpreston asked me to reserve some time to discuss the response to malware and botnets.
+**\<sgp>** Is anyone here to speak about this now?
+**\<mattcode>** yeah
+**\<sgp>** @mattcode great! Go ahead
+**\<mattcode>** lots of angry administrators come into #monero-pools complaining that their servers have been compromised by a miner
+**\<mattcode>** and they get even more upset when they're told that a monero address can't easily be traced back to an individual
+**\<serhack>** oh, I didn't know anything about that, mattcode
+**\<mattcode>** i don't really think that there's a solution to that
+**\<mattcode>** and the other issue is websites getting hacked and web miners being silently inserted, which again there's nothing we can do about that
+**\<serhack>** yes, it's like "someone stealed my monero. my email address pass is 1234"
+**\<mattcode>** if monero didn't exist, the hacked servers and websites would just be used for spam/ddos/stealing passwords instead
+**\<serhack>** +1 mattcode
+**\<msvb-lab>** mattcode: And your or Fluffy's idea about a task force should serve as a support center, right?
+**\<mattcode>** maybe there could be a page on the website explaining the harsh truth to administrators that have been hacked
+**\<DaveyJones>** also isnt it a SysAdmins job to keep his security top of the state? :D
+**\<sgp>** I think there's definitely room for a more formal response to web/server admins
+**\<mattcode>** but a task force isn't too useful because they're just going to end up saying "sorry, there's nothing we can do to help. re-image your server and fix your vulnerabilities"
+**\<sgp>** Ultimately it's up to them to fix/secure their stuff as we should say, but there could still be a page about it
+**\<sgp>** Like "here's what you can do with the mining pool and address. Try contacting them. Otherwise, check your logs"
+**\<rehrar>** I wonder if there's any way we can turn this into a net positive
+**\<msvb-lab>** mattcode: So you believe having a group of support crew is not effective, but maybe a specially labeled web page right?
+**\<serhack>** yep
+**\<mattcode>** yeah I think that would be better. right now they end up in #monero-pools and just end up getting ignored or abused
+**\<DaveyJones>** i think thats a solution
+**\<serhack>** why should we spend efforts on websites when the default password is admin ?
+**\<sgp>** It's good to at least have something serhack. Some of these attacks are more complex, or from an internal employee
+**\<ErCiccione>** Honestly i don't like the idea of the page on the website, i prefer the idea of the team
+**\<mattcode>** rehrar: the positive is that monero has a high network hashrate that doesn't dip when the price dips. i don't have any numbers but when ETN became (briefly) more profitable to mine than XMR, the XMR net hash barely dropped
+**\<serhack>** yep, we should setup a tutorial/website
+**\<rehrar>** I mean turning the third-party server getting hacked into a positive for the administrator. I mean obviously it's not a positive thing...
+**\<rehrar>** but through education and stuff
+**\<rehrar>** We can have ready-made resources (written, video, or otherwise) to hand off to people who experience this
+**\<rehrar>** because this may apply to individual users too, not just servers
+**\<rehrar>** that way, we are not taking responsibility for these people's security, but we are giving tools and resources that people can take hold of their own security
+**\<sgp>** I can write something up as an example and see if it's a good draft. I'll link it in this channel
+**\<serhack>** okay, good sgp
+**\<sgp>** Mattcode, do you want to help me with this?
+**\<mattcode>** most desktop antiviruses pick up the miners and delete them, so i don't think it's too much of an issue for desktop individuals
+**\<ErCiccione>** yeah, much better this way
+**\<sgp>** rehrar that's what I'm thinking
+**\<rehrar>** The task force team can be working on this instead of on-demand support
+**\<rehrar>** This is very in the spirit of The Monero Project, which is all about providing tools and resources for people to take back what's theirs
+**\<sgp>** I just think on-demand support is overkill. It would literally tell people the info on the page we would make
+**\<mattcode>** I don't think we should be writing things like cleanup guides, because all of the different pieces of malware and server configurations make that impossible.
+**\<sgp>** Oh, you want to provide that level of support?
+**\<mattcode>** also organisations usually have their own procedures for when things get compromised
+**\<pigeons>** the support they are looking for is please pool, don't payout to this address etc
+**\<rehrar>** lel
+**\<pigeons>** yes
+**\<rehrar>** they can redirect payment to me instead
+**\<mattcode>** I think the best thing would just be explaining that it's not the Monero project, the pool operator or the miner developer that has hacked your server.
+**\<sgp>** mattcode, are you happy with me making a Mattermost workgroup chat so that we can discuss this further after the meeting?
+**\<pigeons>** yes help them waste less time
+**\<mattcode>** sgp: sure
+**\<sgp>** Great
+**\<serhack>** +1 sgp
+**\<sgp>** Anything else you want to discuss during the meeting?
+**\<sgp>** We are going over today, sorry
+**\<sgp>** 5. Monero Coffee Chat
+**\<sgp>** The next Monero Coffee Chat will be next Saturday on 2 December https://github.com/monero-project/meta/issues/139
+**\<sgp>** During the Coffee Chat, we will go through Taiga so that people become more aware and more familiar with it.
+**\<sgp>** It would be nice if the website is refreshed before then so that the Mattermost/Taiga announcement gets published.
+**\<sgp>** Beyond this, the format of the Monero Coffee Chat will be about the same. If anyone would like to participate, please send me a PM. Otherwise, you can always join us on YouTube.
+**\<rehrar>** Twas lonely last time with just me and sgp and fp (for a bit)
+**\<sgp>** Skipping open ideas time for now, but of course #monero-community can always function as open ideas time even outside meeting time
+**\<sgp>** Yes, it was a bit lonely :)
+**\<serhack>** okay, sgp
+**\<sgp>** We need more volunteers
+**\<sgp>** 7. Confirm next meeting date/time
+**\<sgp>** The next meeting will two weeks from today on 9 December at 17:00 UTC.
+**\<sgp>** 8. Conclusion
+**\<sgp>** That’s all! Thanks for attending this Monero Community meeting, and we hope to see you on /r/MoneroCommunity and #monero-community. Take care, and know that change starts with YOU.
+**\<sgp>** Now, we can continue conversations from endogenic, mattcode, and rehrar
+**\<rehrar>** endogenic watchoo wanna debate?
+**\<endogenic>** well so just about the kovri thing real quick
+**\<endogenic>** i remember on the coffee open hours thing there was discussion about kovri needing a good testing ground
+**\<endogenic>** less life or death than monero would be good. plus more exposure for kovri would be good
+**\<endogenic>** as for the FFS thing…
+**\<mattcode>** just to add onto the botnet thing, i don't think pool ops ever ban addresses after somebody has claimed that their server has been hacked. it would be too easy to fabricate. they only seem to ban big botnets, but only because they place a heavy load on the server :p
+**\<endogenic>** people naturally won't donate to something they consciously think is bad…
+**\<serhack>** +1
+**\<endogenic>** and they tend to donate to things they feel are good for them
+**\<endogenic>** even charity donation for example is thought to return to oneself
+**\<sgp>** mattcode can you create an account on Mattermost please? https://mattermost.getmonero.org
+**\<endogenic>** in monero, it's just supposed to be a little more concrete
+**\<cryptochangement>** now that we are in open tiem, i should probably mention that i posted our FFS update to reddit too so people can see it there: https://www.reddit.com/r/Monero/comments/7fgl4o/monero_integrations_update_12/
+**\<sgp>** #monero-vulne-response
+**\<endogenic>** one thing at at time guys
+**\<cryptochangement>** sgp: vulne or vuln?
+**\<serhack>** vulne
+**\<serhack>** on mattermost
+**\<rehrar>** XD
+**\<sgp>** vulne. It's only on MM now, not IRC
+**\<endogenic>** so if people are not made to undrestand what a proposal is important
+**\<endogenic>** how can you expect them to donate to it?
+**\<sgp>** Sorry
+**\<cryptochangement>** ah ok. i just thought vulne sounded funny ^\_^
+**\<endogenic>** you guys seem to be talking about something else anyway… :P rehrar feel free to ping me
+**\<cryptochangement>** sorry endogenic
+**\<sgp>** You can discuss this now. I'll wait
+**\<sgp>** @endogenic I also made #monero-hackathons on Mattermost
+**\<sgp>** @rehrar on second thought, I think we should have the discussion about the FFS crowdfunding initiative here. Do we need another channel for this?
+**\<ErCiccione>** sgp i think it would be better to talk about it here, much many possible inputs
+**\<sgp>** It's important for the community to survive with small donations, rather than a few wealthy individuals
+**\<sgp>** Of course, having a few people who can help out is both convenient and very generous
+**\<sgp>** But if for some reason these people lost interest, the community should be able to raise significant money from many small donors
+**\<ErCiccione>** i read somwhere the idea of a mining pool managed by the community, where a percent go to the FFS project. doesn't sound too crazy if there's somebody willing to manage everything
+**\<msvb-lab>** ErCiccione: Don't forget promoting the Monero donation address, which could make the third leg of the tuple (many|wealthy|donation.)
+**\<msvb-lab>** Like Kovri does at the bottom of their website.
+**\<msvb-lab>** That could be instrumental for folks that generally appreciate Monero and would donate but don't hang out enough to stay informed.
+**\<serhack>** a "donate now" popup box before downloading?
+**\<sgp>** Most mining pools who donate do so to the Monero project itself
+**\<sgp>** Which in turn often donates to FFS projects
+**\<ErCiccione>** sgp sure, but with a pool you can give the choice to reserve part of your hashrate and decide to put it directly tu support ffs (maybe with subaddresses might be possible to choose the single ffs)
+**\<sgp>** Perhaps
+**\<ErCiccione>** msv-lab: true, but that is mostly everywhere (wallet, website, reddit ecc)
+**\<sgp>** We could change how/when Monero asks for donations
+**\<ErCiccione>** what happens if somebody makes a donation directly to the address of the FFS wallet with no payment id? because if it's possible to evenly distribute that amount to all the actives ffs, we could just spread that address if people doesn't care of the proposal itself, but would like to contribute
+**\<ErCiccione>** an ipothetical 'community pool' could point to that address, distributing equally the mined moneros
+**\<mattcode>** doesn't money from the general development fund make its way into FFS requests?
+**\<ErCiccione>** mattcode: yes, sgp pointed that early, but with a pool you move that choice directly to whom is willing to donate (i mean to send the money directly to fund community's proposals)
+**\<ErCiccione>** s/proposals/FFS
+**\<monerobux>** ErCiccione meant to say: mattcode: yes, sgp pointed that early, but with a pool you move that choice directly to whom is willing to donate (i mean to send the money directly to fund community's FFS)
+**\<ErCiccione>** so nice of you monerobux
+**\<ErCiccione>** :)
+**\<rehrar>** Sorry, out of the house atm. But we need to remember two factors. One, some people like to choose which proposals their XMR goes to. This ensures that Monero evolves in the way they desire.
+**\<rehrar>** These people will not like the General Fund option, as the General Fund is managed by the Core Team to spend on whatever they see fit that benefits Monero (obviously coming to consensus within themselves)
+**\<rehrar>** There are some people who prefer to choose things themselves, and not trust anyone, even the Core Team. And that's fine.
+**\<rehrar>** We're not trying to get everyone to donate to EVERY proposal.
+**\<rehrar>** We're trying to get people to donate to what they believe in.
+**\<rehrar>** So if someone agrees with funding Surae and not myself, they need to have the freedom to not give to me without shame
+**\<rehrar>** but the cultural ideal should be, if you believe in a proposal, you should seriously consider donating something small to it
+**\<ErCiccione>** rehrar: yes, totally agree, that can be solved using subadresses instead of payment's id. could be even better, you would be able to choose the project to contribute to directly from the pool
+**\<ErCiccione>** this is for me a good way to give also to people who cannot afford it, a way to donate, but require the use of subadresses, are they stable right now?
\ 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 0000000000000000000000000000000000000000..91b254fdca998bb7cb99fa561e2f603c473627b9
--- /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, research]
+author: dEBRUYNE / fluffypony
+---
+
+# Logs
+
+**\<suraeNoether>** anyway, agenda for the day: 1) Greetings, 2) Sarang's work 3) my work 4) open discussion. The new zksnark paper will presumably take up some of 4. :P
+**\<suraeNoether>** 1) is done i guess. :\
+**\<suraeNoether>** 2) Sarang want to bring us up to speed?
+**\<sarang>** roger
+**\<sarang>** I have working code for both linear and logarithmic bulletproofs that tests correctly
+**\<sarang>** I'm finishing up a few small optimizations to reduce the curve op count
+**\<suraeNoether>** nice
+**\<sarang>** and then it'll be ready for C++
+**\<sarang>** moneromooo already has the linear version up and running
+**\<suraeNoether>** fantastic!
+**\<sarang>** That's been my big project
+**\<suraeNoether>** page 8 of the new zksnark paper talks about dot product proof protocols
+**\<sarang>** orly
+**\<sarang>** That's the big shiny toy of bulletproofs
+**\<suraeNoether>** literally caught my eye
+**\<suraeNoether>** or rather
+**\<suraeNoether>** metaphorically? well
+**\<suraeNoether>** anyway, my point is i have done nothing but skim the paper (in the past 10 minutes) and that popped out at me
+**\<suraeNoether>** you have also been helping me on multisig, as well, don't discount that
+**\<sarang>** I shan't
+**\<suraeNoether>** anything else?
+**\<suraeNoether>** gratz on getting it working
+**\<sarang>** Thanks to everyone who offered support in the most recent fund drive
+**\<sarang>** I remain humbled
+**\<suraeNoether>** thank you, sarang! thanks again
+**\* sarang** takes a small bow
+**\<suraeNoether>** As for my work, I've been working on the multisig paper, which is intended to 1) present a formal model of our threshold ringct, and 2) show how our current implementation compares to that formal model. there are differences that i'm hunting down one by one
+**\<suraeNoether>** JollyMort[m] has found several already, and we've been having discussions about it the past few days
+**\<suraeNoether>** That has represented the vast majority of my time
+**\<suraeNoether>** In addition to that, I believe I may have a problematic example case of SPECTRE. the original authors sweep my concern aside, but i wanted to bring it up and see if anyone had any thoughts
+**\<sarang>** I'm intrigued
+**\<suraeNoether>** if two transactions using the same input are relayed nearly simultaneously, they will find their way into two separate blocks. they will appear as conflicting transactions until the spectre algorithm arranges one block to precede the other
+**\<suraeNoether>** or stay conflicting forever if spectre can never linearly order them
+**\<suraeNoether>** this can happen with a simple example of a "mostly linear" blockchain, except with a single block in the chain replaced with a pair of blocks like a diamond shape:
+**\<suraeNoether>** \_\_\_\/\\_\_\_
+**\<suraeNoether>** \/
+**\<suraeNoether>** something that looks like that
+**\<suraeNoether>** then any transactions that conflict in the pair of non-linearly-ordered blocks will appear to conflict forever
+**\<suraeNoether>** this allows a clumsy user who re-sends a transaction twice becuase he's foolish to lose his funds.
+**\<sarang>** Can we back this up with a simulation?
+**\<suraeNoether>** i mean, we could, but there's a solid chain of lemmas that lead to a theorem i can write up later if you like
+**\<suraeNoether>** using the theorems about how rapidly sets in spectre get finalized
+**\<sarang>** Even better
+**\<sarang>** \*lemmata
+**\<suraeNoether>** now, the spectre authors said "the only reason someone would relay two transactions like this is to attempt a double spend, so it's okay that the funds are lost."
+**\<sarang>** lolwut
+**\<suraeNoether>** well
+**\<suraeNoether>** the idea is that htey are *two* transactions with valid signatures using the same input
+**\<suraeNoether>** or rather, using at least one of the same inputs
+**\<suraeNoether>** so by definition, it's a double spend
+**\<suraeNoether>** and i can't really think of a scenario where someone would compute two signatures separately like that, then relay them nearly simultaneously like that... on accident
+**\<suraeNoether>** BUT
+**\<suraeNoether>** it's enough of a leap for me to be concerned
+**\<suraeNoether>** moreover
+**\<suraeNoether>** i'm not sure if that sort of "double spend implies money lost forever instead of "eventually one of the two spends is accepted."
+**\<suraeNoether>** and what's really crazy
+**\<suraeNoether>** is that if block arrival times are very fast, like 10/s as in the original spectre paper... this problem is solved *with high probability*
+**\<suraeNoether>** so, that's where SPECTRE is sitting.
+**\<suraeNoether>** and lastly, my viewkey proposal
+**\<suraeNoether>** s/lost forever/lost forever" philosophy instead of...
+**\<scoobybejesus>** I own address A, B, and C. I simultaneously send the same output as an input in txns A ->** B and A ->** C. Free coins? Or B and C each now have unspendable outputs?
+**\<suraeNoether>** a miner would see two conflicting transactions, so neither would be considered valid
+**\<suraeNoether>** and constructing another transaction later A->**D will also be considered invalid
+**\<scoobybejesus>** Ah. Thanks.
+**\<suraeNoether>** so until spectre re-orgs the block-DAG so that the transaction A->**B precedes A->**C or vice versa, it's locked forever
+**\<gingeropolous>** right, i was wondering that... i though eventually it resolves to a bloclchain
+**\<gingeropolous>** or blockchain
+**\<suraeNoether>** actually, that's the problem: if block arrival rate is slow and you have a fork
+**\<suraeNoether>** the next block to arrive will point to both blocks as parents
+**\<sarang>** yeah
+**\<suraeNoether>** and if all blocks from there on out point to that common child block, those two blocks will never be linearly ordered
+**\<suraeNoether>** so, this would also be solved by simply telling people to try to avoid making more than 1 transaction per target block arrival rate *personally*
+**\<suraeNoether>** otherwise they are burning their own money, in a sense
+**\<sarang>** that's quite the kludge
+**\<gingeropolous>** so dbl spends are punished... kinda
+**\<suraeNoether>** gingeropolous: yes, it provides a strong incentive against making a double spend attack
+**\<suraeNoether>** which is nice
+**\<suraeNoether>** i just don't want to make it so that badly informed users of Monero don't accidentally burn their money
+**\<gingeropolous>** i wonder if we could protocolize an incubate function, where a tx has to sit in the txpool for n blocks
+**\<suraeNoether>** sarang it's not too much of a kludge, if our block arrival rate is 1/second or something
+**\<sarang>** hmm
+**\<suraeNoether>** gingeropolous: ooooh
+**\<gingeropolous>** kind of a bitch because timestamping and all..
+**\<suraeNoether>** it's worth thinking about though!
+**\<suraeNoether>** that's a good idea
+**\<suraeNoether>** okay, so does anyone else have anything they want to share about their work?
+**\<sarang>** I could add that I've posted my monthly report: https://www.reddit.com/r/Monero/comments/7frn7i/november_monthly_report_from_sarang_noether/
+**\<sarang>** Comments welcome
+**\<suraeNoether>** Also, I'd like to thank the community for funding me as well
+**\<suraeNoether>** It's astonishing
+**\<suraeNoether>** In other announcements....
+**\<suraeNoether>** rehrar is working on the next Monero Revuo
+**\<suraeNoether>** I'm not sure what the publication timeline on that is supposed to be
+**\<suraeNoether>** but it's the quarterly newsletter wherein he sort of interviews the teams at MRL in charge of various projects
+**\<sarang>** Any other discussion items?
+**\<suraeNoether>** he and Sarang and I are going to have a sit-down and talk about the direction MRL is heading. I am interested in writing up current standards for Monero, I know Sarang is also, and I want to start on that as soon as Multisig is done.
+**\<sarang>** ah yes
+**\<suraeNoether>** For each Monero standard, I also want to write up at least one proposal for replacing the standard in the case that the security of that standard is compromised
+**\<suraeNoether>** I also want to compile arguments for and against replacing certain standards sooner rather than later, for example, our "nonstandard" hash function
+**\<suraeNoether>** oh man, i should ping andytoshi too
+**\<suraeNoether>** this includes our proof of work standard
+**\<sarang>** That strikes me as our least-standard "thing"
+**\<suraeNoether>** cryptonight has some value, but it's as homebrew as can be
+**\<suraeNoether>** yeah
+**\<suraeNoether>** i wouldn't mind putting up a portion of my funding for this period toward a Proof of Work contest for Monero's replacement proof of work scheme
+**\<suraeNoether>** hmm
+**\* iDunk** reaches for a pitchfork
+**\<suraeNoether>** ?
+**\<suraeNoether>** cryptonight has value because of asic resistance. i'm okay with asics if they are commoditized. i'm not married to cryptonight in any way
+**\<suraeNoether>** i'm in a non-monogamous relationship with cryptonight
+**\<suraeNoether>** ok, well
+**\<suraeNoether>** anything else to discuss?
+**\<dEBRUYNE>** suraeNoether: i wouldn't mind putting up a portion of my funding for this period toward a Proof of Work contest for Monero's replacement proof of work scheme \<= I think othe already has some back up plans
+**\<silur>** apparently V wants ringCT in EVM2
+**\<dEBRUYNE>** You might want to talk to him about it
+**\<suraeNoether>** othe are you around?
+**\<othe>** Yes
+**\<suraeNoether>** silur V = vitalik?
+**\<silur>** yep
+**\<suraeNoether>** othe you've been thinking about POW?
+**\<othe>** Yea
+**\<othe>** Slight changes we can implement will break all asics
+**\<silur>** I introduced stringCT/ruffCT PoC code in our research channel hope it will go somewhere
+**\<othe>** Trivial to implement in cpu and gpu
+**\<suraeNoether>** oooh, that's fantastic! fluffypony sent me at least one recommendation for that a few weeks ago
+**\<suraeNoether>** but i haven't had time to look into it
+**\<othe>** Yeah that one is an example
+**\<silur>** what is this new POW?
+**\<suraeNoether>** ok, but you aren't talking about *replacing cryptonight* but modifying it
+**\<suraeNoether>** silur othe has apparently been looking at the cryptonight code very closely and determining how to swap bits around or mess with the implementation to improve asic resistance without harming gpu or cpu performance
+**\<othe>** Just modifying it randomly
+**\<silur>** I thought cryptonight is asic resistant by design O.o
+**\<othe>** Takes like 5 lines of code in gpu miner
+**\<silur>** I knew that it's not like... cuckoo cycle hard but still
+**\<othe>** Cuckoo is not hard at all
+**\<suraeNoether>** yeah cuckoo isn't asic resistant at all
+**\<suraeNoether>** i have a paper around here about it
+**\<silur>** dayum
+**\<suraeNoether>** silur cryptonight takes up L3 cache like crazy, so the asic resistance comes from forcing it through a bottleneck
+**\<suraeNoether>** but you could still have an asic on the back end of the bottleneck
+**\<othe>** There's really nothing asic resistant if u hsve money
+**\<suraeNoether>** so if someone creatively designed a computer with a huge L3 cache or something like that...
+**\<suraeNoether>** which normally you wouldn't have to worry about for something like SHA256
+**\<suraeNoether>** then the asic is still technically possible, we're just... resistant to it
+**\<suraeNoether>** because it requires novel computer architecture and design
+**\<suraeNoether>** othe i'm very glad to hear you have been working on this
+**\<suraeNoether>** ended the meeting a little too early, sarang. :\
+**\<sarang>** I'm following along on the bus
+**\<sarang>** The bus smells like ass today
+**\<suraeNoether>** http://www.cs.cmu.edu/~dga/crypto/cuckoo/analysis.pdf
+**\<othe>** Well i don't have a problem with asics but sth like shitmain has to be killed of when trying
+**\<suraeNoether>** nope, that's not the paper i was looking at
+**\<suraeNoether>** othe my primary concern is decentralization, whether it's through asic resistance or asic commoditization. the idea of cpu mining is great in some ways, but i like andytoshi's paper on the thermodynamic minimum *a whole lot.*
+**\<suraeNoether>** like, his paper made me realize that proof-of-storage or something like that? the universal minimum will be determined by the speed of light
+**\<suraeNoether>** so instead of commoditized hardware mining, you would see massive massive data centers all with fiber optic cables of *exactly the same length* to avoid time effects from light speed, etc etc
+**\<suraeNoether>** so anyway
+**\<unknownids>** this is probably useless info at this point as its all rumors, but https://rmc.one/ has said they are working on a cryptonight asic
+**\<suraeNoether>** oh yes, that is the paper. :P http://www.cs.cmu.edu/~dga/crypto/cuckoo/analysis.pdf
+**\<suraeNoether>** unknownids: eh, the minute they blow a million on taping out a few asics, we'll implement the first of othe's list of changes. :P they'll have to retape, best case scenario... and then we do it again...
+**\<othe>** Rmc one are idiots but rwal companies might be
+**\<suraeNoether>** it's easier for us to change the algo than it is for them to pump out asics
+**\<suraeNoether>** tbh if i were in the asic business i wouldn't make a move without blessings and guidance from the developers of the coin
+**\<unknownids>** good to know othe
+**\<suraeNoether>** because they'll just change their code if they don't like what you are doing
+**\<silur>** ^
+**\<suraeNoether>** whoever is designing asics for monero are preparing to burn their fiat. but hey, they probably have fiat to burn
+**\<suraeNoether>** joker.jpg
+**\<suraeNoether>** ok guys
+**\<suraeNoether>** i'll be back later today
+**\<JollyMort[m]>** entrepreneurs will always find a way to get above others; be it ASIC or botnets or webminers; what's important is that there's no barrier to entry for new players so that nobody's position is forever assured
diff --git a/_posts/2017-12-03-overview-and-logs-for-the-dev-meeting-held-on-2017-12-03.md b/_posts/2017-12-03-overview-and-logs-for-the-dev-meeting-held-on-2017-12-03.md
new file mode 100644
index 0000000000000000000000000000000000000000..4f8a1172b03704e32721aa52b49e02c7f84cfa0c
--- /dev/null
+++ b/_posts/2017-12-03-overview-and-logs-for-the-dev-meeting-held-on-2017-12-03.md
@@ -0,0 +1,264 @@
+---
+layout: post
+title: Overview and Logs for the Dev Meeting Held on 2017-12-03
+summary: Discussion of open PRs and issues, Bulletproofs, Monero Research Lab, RNGs, 0MQ, and miscellaneous
+tags: [dev diaries, core, crypto]
+author: dEBRUYNE / fluffypony
+---
+
+# Overview
+
+An overview can be found on [MoneroBase](https://monerobase.com/wiki/DevMeeting_2017-12-03).
+
+# Logs
+
+**\<fluffypony>** 1. Greetings
+**\<fluffypony>** 2. Brief review of what's been completed since the previous meeting
+**\<fluffypony>** 3. Code + ticket discussion / Q & A
+**\<fluffypony>** 4. Any additional meeting items
+**\<fluffypony>** 5. Confirm next meeting date/time
+**\<fluffypony>** so 1. Greetings
+**\<fluffypony>** hi
+**\<ArticMine>** Hi
+**\<fluffypony>** luigi1111 (if you're back) / smooth / hyc / moneromooo etc.
+**\<moneromooo>** here
+**\<gingeropolous>** etc here
+**\<fluffypony>** 2. Brief review of what's been completed since the previous meeting
+**\<fluffypony>** lots of stuff
+**\<sarang>** MRL has working Java test code for complete multi-output bulletproofs
+**\<sarang>** It's being ported over to C++
+**\<moneromooo>** (not the multi output one)
+**\<sarang>** The Java part is complete
+**\<moneromooo>** Sorry, I meant just about the port ^\_^
+**\<sarang>** Discussions are ongoing about if/how the fee structure would be modified to prevent large-output txn DoS
+**\<fluffypony>** what's wrong with per-byte fees?
+**\<sarang>** You can load a txn with tons of outputs
+**\<sarang>** but verification is linear in the # of outputs
+**\<dEBRUYNE>** fluffypony: verification is linear, whilst size is log
+**\<dEBRUYNE>** basically
+**\<sarang>** So for low fees you can force the network to verify
+**\<fluffypony>** ah ok, makes sense
+**\<sarang>** So we need to incentivize the use of aggregate BPs while basically scaling the fee to the number of outputs etc.
+**\<sarang>** But things are looking good
+**\<sarang>** Verification is still quite efficient
+**\<sarang>** and with the multi-output setup, space savings are unreal
+**\<moneromooo>** In fact, the per byte fee needs to be done first, as per kB is way too coarse for this.
+**\<sarang>** Yeah a single output BP is about 704 bytes, while a 2-output BP is something like 768 bytes
+**\<sarang>** (including commitments)
+**\<sarang>** it's just too damn good
+**\<fluffypony>** nice
+**\<dEBRUYNE>** For clarification, a single output is currently \~ 6 kB, whereas a 2-output is \~ 12 kB
+**\<* hotoatmeal** was about to ask
+**\<sarang>** So we'll continue moving forward with porting and testing
+**\<manifest>** serhack here?
+**\<dEBRUYNE>** A typical Monero transaction has 2 ins + 2 outs
+**\<serhack>** yep manifest
+**\<manifest>** i was wondering who was the m8 that was gonna work on the go-library since i started on it myself a little bit swell
+**\<fluffypony>** dEBRUYNE: this would also be a major cost-saving for pool payments
+**\<fluffypony>** manifest: we're in a meeting
+**\<sarang>** For reference, the size of an M-output BP is 32\*(2\*log(64\*M)+9) bytes (this doesn't count the amount commitments)
+**\<sarang>** add 32 bytes for each of the M amount commitments if you want to include them
+**\<sarang>** (log is base 2)
+**\<rehrar>** manifest you can hop on mattermost.getmonero.org. Serhack is also there and you guys can PM and chat so as not to disrupt the meeting. Thanks. :)
+**\<ArticMine>** I have to give some thought to the fees to deal with the verification issue
+**\<fluffypony>** ok so beyond BP is there anything else worth noting?
+**\<sarang>** We do require a power of 2 in the # of outputs
+**\<pigeons>** So sometimes you just create an additional change output, or how do you cause always a power of 2?
+**\<sarang>** We'll need to either pad with dummy outputs or split into power-of-2 proofs
+**\<ArticMine>** Split the change into two tx
+**\<pigeons>** OK
+**\<sarang>** The dummy output doesn't need to actually represent anything
+**\<sarang>** It just needs to be there for the proof
+**\<sarang>** It can be amount 0
+**\<ArticMine>** that will work also
+**\<sarang>** Anyway, that's my 3 cents
+**\<luigi1111>** Better to split
+**\<luigi1111>** Space is cheap gp
+**\<luigi1111>** Cpu is expensive\*
+**\<ArticMine>** We will have to price cpu
+**\<moneromooo>** There's a possible optimization for "filler" outs AIUI.
+**\<luigi1111>** Probably not as good as not using them :)
+**\<sarang>** There aren't any security proofs for a non-power-of-2 proof
+**\<moneromooo>** I was led to think it was not inherent in the scheme, though ?
+**\<sarang>** It is
+**\<moneromooo>** aw...
+**\<sarang>** At least for right now
+**\<sarang>** There's a recursive step that split arrays in half
+**\<ArticMine>** The issue I see is that the penalty only prices space
+**\<sarang>** The authors of the paper are looking into a generalization, but it doesn't exist yet
+**\<luigi1111>** That's interesting
+**\<fluffypony>** ok so
+**\<fluffypony>** anything else from the last two weeks worth noting?
+**\<sarang>** suraeNoether is completing review for multisig
+**\<sarang>** He is unable to be here today
+**\<Gdhhyfjjs467>** Has a code freeze date for the next for been set yet?
+**\<fluffypony>** Gdhhyfjjs467: yeah we'll be branching towards the end of the month
+**\<fluffypony>** assuming our comfort levels are ok
+**\<rehrar>** This was discussed briefly in MRL channel with the idea that if BPs are not too far off, would it be worth delaying the next hard fork by a couple months so it can be in?
+**\<dEBRUYNE>** The plan is to include multisig right?
+**\<dEBRUYNE>** \^ fluffypony
+**\<luigi1111>** Yes
+**\<fluffypony>** no need to delay the hard fork
+**\<luigi1111>** I don't think the upcoming fork does anything useful though
+**\<luigi1111>** So there's that
+**\<fluffypony>** if BP is ready it'll go into the Sept fork
+**\<dEBRUYNE>** Should we fork if there's nothing to fork for?
+**\<luigi1111>** Who knows ^\_^
+**\<fluffypony>** luigi1111: consistency, then
+**\<fluffypony>** well, that's what we committed to with the fork schedule
+**\<fluffypony>** "even if it's just bumping the block version number"
+**\<dEBRUYNE>** Sure, but didn't we also discuss slowing things down once the ecosystem got bigger?
+**\<moneromooo>** We did not commit to an exact fork schedule.
+**\<luigi1111>** And who is this we :)
+**\<moneromooo>** I, at least, did not :P
+**\<hotoatmeal>** does the wallet release schedule track the protocol fork schedule exactly?
+**\<hotoatmeal>** or do they have different cadences
+**\<moneromooo>** The wallet needs to update for a fairly large subset of consensus changes.
+**\<pigeons>** the wallet-cli and wallet-rpc are included with the daemon release that supports the fork
+**\<moneromooo>** So it's convenient to release at the same time.
+**\<fluffypony>** dEBRUYNE: I don't think we're at a point where we can go to annual
+**\<moneromooo>** Besides, the wallet and daemon rely on the same libs.
+**\<rehrar>** Isn't ZMQ also in the new release? Or has that been there for a while now?
+**\<fluffypony>** yes ZMQ is in the new release
+**\<moneromooo>** There's some of it in, but some of it's still missing.
+**\<pigeons>** there is some support for zmq over rpc, and more is comming, like tx/block notify and some changes to the existing zmq rpc
+**\<pigeons>** \*rpc over zmq
+**\<hotoatmeal>** moneromooo: yeah, mainly thinking about when I need to spend time to get those two memwipe patches (and the third I haven't written yet) reviewed/merged
+**\<pigeons>** the notify is what the people i hear from are waiting for, and tewinget told me a few weeks ago he's got the basics worked out
+**\<rehrar>** Are we still waiting on him for stuff?
+**\<moneromooo>** There's a patch waiting on changes IIRC.
+**\<moneromooo>** (for 0mq)
+**\<rehrar>** *sigh* tewinget, can you please get this stuff done? Seriously.
+**\<moneromooo>** Especially as I think some of the large pool speedups were lost.
+**\<moneromooo>** (not 100% sure)
+**\<hotoatmeal>** is there a way to detect that the network has forked, and your client hasn't gone with it?
+**\<moneromooo>** Kinda.
+**\<hotoatmeal>** my local daemon got left behind on the last one, because I forgot to update
+**\<fluffypony>** you can make an educated guess
+**\<hotoatmeal>** cue colorful headscratching
+**\<moneromooo>** Current daemon should moan if it sees blocks with a higher version than what it knows about.
+**\<fluffypony>** and there's auto-update records that notify
+**\<moneromooo>** The block verison thing is a bit vulnerable to someone mining a bad block on purpose to make you think there's been a fork though.
+**\<fluffypony>** yeah
+**\<moneromooo>** Losing 10 monero in the process or whatever it is :)
+**\<fluffypony>** ok let's move it along, then
+**\<fluffypony>** 3. Code + ticket discussion / Q & A
+**\<fluffypony>** are there any issues that could do with some input / resolution?
+**\<moneromooo>** The handful of oldest ones.
+**\<moneromooo>** The PRNG one.
+**\<moneromooo>** ones.
+**\<moneromooo>** For multisig, I think it's pretty much ready to go in, stoffu's done a lot of careful reviewing.
+**\<fluffypony>** ok - what's the blocker on switching to the Bitcoin one?
+**\<hotoatmeal>** moneromooo: what still needs doing / deciding on your part of the memwipe ones, and how can I help there?
+**\<moneromooo>** Mainly deciding whether we want to, or not.
+**\<moneromooo>** And bitcoin has two RNGs, the one I ported, and one that's closer to what we have. so there's the possibility of entropy attrition using only the "good" one.
+**\<moneromooo>** hotoatmeal: the only thing left IIRC was switching from std::vector\<char> to std::unique\_ptr\<char[]> and I feel more confident getting it right with vector.
+**\<moneromooo>** Other than that, nothing I think.
+**\<fluffypony>** moneromooo: by "good" one you mean the ported one?
+**\<moneromooo>** That can be done later by someoine who's familiar with how the refcounting works with operators though.
+**\<moneromooo>** Yes. The one that uses getrandom, etc.
+**\<fluffypony>** ok so I think if they haven't hit entropy attrition problems over the past few years it's unlikely we will - thoughts?
+**\<moneromooo>** Let me rephrase:
+**\<moneromooo>** Bitcoin has two RNGs: a good one using HW, and a... hmmm, less good ? one similar to our keccak based one
+**\<moneromooo>** Using the keccak based one does not deplete entropy nearly as fast as using the good one. Monero can use a lot of entropy (eg, range proofs).
+**\<moneromooo>** Therefore, I'm wondering whether using the good one all the time is worse than not.
+**\<hotoatmeal>** moneromooo: ok, I'll pick up the vector vs unique\_ptr part of that later this month
+**\<moneromooo>** Thanks
+**\<fluffypony>** ok so what if we used the good one for critical stuff like privkey generation
+**\<fluffypony>** and output selection
+**\<hotoatmeal>** and if you give me some pointers, can look at whatever that refcounted operators thing is in Jan
+**\<fluffypony>** and the stream one for range proofs
+**\<moneromooo>** Well, if I knew that, I'd know the answer to my question, since they're opposites.
+**\<moneromooo>** Anyway, to go back to multisig, I tihnk it's good to go now. If you haven't yet reviewed it, and want to do so, do so now.
+**\* hotoatmeal** drops out
+**\<fluffypony>** ok
+**\<fluffypony>** 4. Any additional meeting items
+**\<moneromooo>** When do we want bulletproofs on testnet ?
+**\<dEBRUYNE>** Tomorrow!
+**\<fluffypony>** hah hah
+**\<moneromooo>** A day may be a bit short to get people to update in time.
+**\<fluffypony>** are we going to wait for the multi output stuff?
+**\<sarang>** I think we should
+**\<moneromooo>** Not sure. This is not quite finished (multiple of 2 requirement), and has a non trivial impact on fees.
+**\<sarang>** Hrmm true, the fee thing
+**\<sarang>** :/
+**\<moneromooo>** And I'd really, really like to get smaller txes double plus quick.
+**\<fluffypony>** ok so how would this work
+**\<ArticMine>** A lot of people do
+**\<sarang>** In case it's relevant, every single-output proof is still a valid multiproof
+**\<moneromooo>** That's nice.
+**\<sarang>** (provided we define the Gi and Hi in the same order)
+**\<sarang>** (not sure if my extended code addressed that, will check)
+**\<moneromooo>** So, no clear votes for or against. Except me ^\_^ so that's 100% of expressed votes :P
+**\* sarang** checks the math on that
+**\<fluffypony>** moneromooo: I asked how it would work
+**\<moneromooo>** The fork ? I imagine similar to rct. Allow bulletproofs at fork f, optionally disallow borromean at f+1.
+**\<moneromooo>** (the code currently does not do that second part)
+**\<moneromooo>** That might become a bit more complicated if we start allowing aggregated proofs at f+1.
+**\<moneromooo>** But not very much.
+**\<dEBRUYNE>** so moneromooo, you'd like to start with single output right? And then eventually switch to multioutput
+**\<moneromooo>** Yes.
+**\<rehrar>** Sorry if this was answered, but is there an ETA on multioutput port from Java?
+**\<moneromooo>** No. It doesn't appear to be a lot of work though.
+**\<fluffypony>** so then txs with more than 1 output would use borromean?
+**\<moneromooo>** No. They'd use two bulletproofs.
+**\<sarang>** yup
+**\<rehrar>** Which is still a savings.
+**\<sarang>** Still great space savings
+**\<sarang>** And no DoS issues
+**\<dEBRUYNE>** 2 bulletproofs is 1.3 kb give or take right?
+**\<fluffypony>** ok
+**\<dEBRUYNE>** And we can keep our current fee structure
+**\<sarang>** dEBRUYNE: yes
+**\<moneromooo>** Most of it, in fact. Txes are ~2.2 kB.
+**\<rehrar>** I think that's worth it. And then it can be enhanced even further with multioutput later. But the immediate savings would be appreciated.
+**\<rehrar>** And gives time for the fee dislogue
+**\<fluffypony>** and what's our confidence level like in this? like is it March-fork-worthy?
+**\<rehrar>** Dialogue\*
+**\<moneromooo>** Well, we can know better if we fork in a couple days on testnet :)
+**\<ArticMine>** I have an idea on the fee issue
+**\<rehrar>** It can be deployed to testnet asap no.
+**\<rehrar>** ?
+**\<moneromooo>** That's what I'm asking about, yes.
+**\<fluffypony>** could we fork testnet this coming weekend?
+**\<moneromooo>** Works for me. Gives time for review.
+**\<rehrar>** Exciting!
+**\<sarang>** Yes and the code should definitely be reviewed by others
+**\<endogenic>** who?
+**\<endogenic>** if you had your pick
+**\<JollyMort[m]>** could someone do me a favor and send me the log of this channel from 2017-04-18?
+**\<sarang>** Ideally andytoshi since he's a paper author
+**\<moneromooo>** If I had my pick...
+**\<sarang>** suraeNoether
+**\<fluffypony>** Satoshi
+**\<endogenic>** fluffypony: on it
+**\<sarang>** Someone who digs the maths
+**\<Gdhhyfjjs467>** So Evan duffield?
+**\<dEBRUYNE>** luigi1111 I guess
+**\<endogenic>** vtnerd hyc fyi
+**\<moneromooo>** Oh yeah, luigi1111 is a good one.
+**\<rehrar>** Let's just get all hands on deck for this?
+**\<endogenic>** ok that means you too rehrar
+**\<Gdhhyfjjs467>** Lol jk. I like andytoshi idea
+**\<sarang>** I'm sure we'll find additional optimizations... I know for a fact my implementation of scalar operations into vectors could be refactored
+**\<rehrar>** I will understand none of it, but I'll look at it and either nod approvingly or cringe based on a coin toss.
+**\<sarang>** but I didn't in Java in order to keep it clean and understandable
+**\<endogenic>** i move to instate rehrar as new RNG
+**\<moneromooo>** The slice op ? Yes, but I don't think it takes much time compared to the muls.
+**\<sarang>** Random Nod Generator?
+**\<sarang>** Well and operations involving many vector ops could run a single loop per element, instead of per operation
+**\<sarang>** but they're generally fast and it makes things clean
+**\<sarang>** I'm not a huge fan of sacrificing clarity for a tiny speedup
+**\<sarang>** I'd like to chat with moneromooo post-meeting about our basepoint selection, to ease the transition into multiproofs later
+**\<sarang>** For those who want to compare code to paper, this is the paper: http://web.stanford.edu/~buenz/pubs/bulletproofs.pdf
+**\<moneromooo>** I pushed the patch as 2883 if people want to start reviewing ^\_^
+**\<rehrar>** Can I make a Reddit post calling devs to review it?
+**\<moneromooo>** Reddit.. devs ?
+**\<dEBRUYNE>** \^ that lol
+**\<rehrar>** :P nvm then
+**\<dEBRUYNE>** The people able to review it will be watching Github
+**\<endogenic>** rehrar: answer is in the question :P
+**\<fluffypony>** oh
+**\<fluffypony>** I guess meeting ~done
+**\<fluffypony>** 5. Confirm next meeting date/time
+**\<fluffypony>** Sunday the 17th
\ No newline at end of file
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 0000000000000000000000000000000000000000..8bd368626e8979e93dc758c51d54a3b8ca494e9b
--- /dev/null
+++ b/_posts/2017-12-07-Monero-Compatible-Bulletproofs.md
@@ -0,0 +1,22 @@
+---
+layout: post
+title: Monero Compatible Bulletproofs
+tags: [crypto, research]
+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 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 ([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.
+
+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
diff --git a/_posts/2017-12-09-logs-for-the-Community-meeting-held-on-2017-12-09.md b/_posts/2017-12-09-logs-for-the-Community-meeting-held-on-2017-12-09.md
new file mode 100644
index 0000000000000000000000000000000000000000..381221649f2a968db7b4912f73be7536b34b2f5d
--- /dev/null
+++ b/_posts/2017-12-09-logs-for-the-Community-meeting-held-on-2017-12-09.md
@@ -0,0 +1,256 @@
+---
+layout: post
+title: Logs for the Community Meeting Held on 2017-12-09
+summary: Community highlights, Forum Funding System updates, RFC-HWALLET-1, Monero video series, Malware Response Workgroup, and miscellaneous
+tags: [community, crypto]
+author: dEBRUYNE / fluffypony
+---
+
+# Logs
+
+**\<sgp>** Thanks everyone for waiting
+**\<sgp>** 0. Introduction
+**\<sgp>** We would like to welcome everyone to this Monero Community Meeting!
+**\<sgp>** Link to agenda on GitHub: https://github.com/monero-project/meta/issues/141
+**\<sgp>** Monero Community meetings are a discussion place for anything going on in the Monero Community. We use meetings to encourage the community to share ideas and provide support.
+**\<sgp>** I have a presentation at noon, so this meeting will be a little shorter than normal. You are welcome to carry on the open ideas time even after I need to leave.
+**\<sgp>** 1. Greetings
+**\<cryptochangements>** hola amigos
+**\<serhack>** Hello
+**\<brendanmcmanus>** hey all!
+**\<ErCiccione>** Ciao everybody
+**\<msvb-fab>** Hello folks.
+**\<sgp>** 2. Community highlights
+**\<sgp>** For a great weekly summary, please read the Monero Observer: http://monero-observer.com/
+**\<sgp>** 3. FFS updates
+**\<sgp>** a. RFC-HWALLET-1 project progress
+**\<sgp>** @msvb-fab, you have the floor
+**\<rehrar>** Hi
+**\<ajs>** Hello
+**\<ArticMine>** hi
+**\<fluffypony>** ola
+**\<msvb-fab>** Oh okay.
+**\<xmr\_eric>** Hullo
+**\<msvb-fab>** Hardware wallet.
+**\<msvb-fab>** Dozens of parts have arrived including panelized PCBs, and some unplanned holiday goodies.
+**\<msvb-fab>** We'll be assembling in the next week, in order to deliver a end of year dividend to anybody who has contributed in even the smallest way.
+**\<msvb-fab>** Consider this the last chance to sign up as a tester and complete the one minute of duties required to receive the first ever Monero hardware wallet prototype.
+**\<msvb-fab>** Our star designer in this round is i\_a, who created the 'Julian Candy' release seen here:
+**\<msvb-fab>** https://taiga.getmonero.org/media/attachments/8/3/9/3/164be48259ead3bc4127f70a5c85bae7edf39227413cd0cef260b6ca1b4e/julianpanel-2.jpeg
+**\<msvb-fab>** But as you see from our main page, there are other parallel efforts as well:
+**\<msvb-fab>** https://taiga.getmonero.org/project/michael-rfc-hwallet-1-implementation/
+**\<msvb-fab>** To become a tester and get a board, I need your mailing address and a couple other 1 minute things. If you have 5 minutes, then read:
+**\<msvb-fab>** https://taiga.getmonero.org/project/michael-rfc-hwallet-1-implementation/wiki/preview/
+**\<msvb-fab>** We also had our first Monero hardware team meeting this week on #monero-hardware.
+**\<msvb-fab>** ...which went well for a first try. One hour long, we'll probably do one per month.
+**\<msvb-fab>** That's all unless other members of the Monero hardware team want to inform...?
+**\<ErCiccione>** msv-fab: the prototype only for americans, right? :(
+**\<msvb-fab>** ErCiccione: Heh? Actually we are three assemblers and all in different european countries.
+**\<serhack>** why americans Erciccione?
+**\<msvb-fab>** So all the south and north americans are lucky to get something.
+**\<sgp>** Thanks msvb-fab
+**\<msvb-fab>** This is universal, even for folks in the ISS space station they can get a prototype.
+**\<ErCiccione>** uh, really? i didn't subscrive because i was sure was only available in america. my bad, you have a new tester :)
+**\<msvb-fab>** Doesn't have to be planet earth.
+**\<sgp>** lol
+**\<sgp>** b. Monero Video Series
+**\<sgp>** We would like community comments on the final community script: https://github.com/alvinjoelsantos/promo-video/blob/master/community.md
+**\<sgp>** Please make comments on GitHub.
+**\<ErCiccione>** don't know why but i was absolutely sure :P
+**\<msvb-fab>** I'm on site at a fabricator right now cutting enclosure pieces, so please let me take a 5 minute break to adjust the laser okay?
+**\<sgp>** Let's make this video as good or better than the other ones
+**\<sgp>** c. Monero Meetup Kit
+**\<msvb-fab>** I'll be back in five minutes...
+**\<serhack>** I think monero video need translators for subtitles
+**\<sgp>** @serhack yes it does. Speak with ErCiccione after the meeting about these
+**\<ajs>** If you have any suggestions for script, PR welcomed.
+**\<serhack>** great, sgp
+**\<sgp>** I have finished all the milestones for the Meetup Kit. I will give the last of my stuff out during a meeting in Madison that starts in 40 mins
+**\<sgp>** Does anyone else have a FFS update?
+**\<serhack>** We are working hardly on Opencart.
+**\<serhack>** you can go on sgp
+**\<msvb-fab>** serhack: Working hard or hardly working?
+**\<serhack>** Working hard\*
+**\<sgp>** Great to hear
+**\<sgp>** 4. Discuss formation of Malware Response Group
+**\<sgp>** Fluffypony and tuckerpreston asked me to reserve some time to discuss the response to malware and botnets.
+**\<fluffypony>** ok
+**\<fluffypony>** so
+**\<fluffypony>** this is really an optics problem
+**\<sgp>** Fluffypony, welcome!
+**\<fluffypony>** basically the issue of poor optics with relation to Monero is going to be an increasing challenge
+**\<fluffypony>** some areas we don't have much influence / control over
+**\<fluffypony>** but with malware there is something we can do
+**\<fluffypony>** we can help people who are infected with malware
+**\<fluffypony>** so when someone has found a malicious miner, for instance, what can they do about it?
+**\<fluffypony>** well, a Malware Response Group can help that person
+**\<fluffypony>** they can provide them with a guide to clearing out the malware
+**\<dEBRUYNE>** Perhaps write a guide that shows how to remove malware and alternatively explains how to do a fresh OS install
+**\<fluffypony>** yes
+**\<fluffypony>** however
+**\<msvb-fab>** fluffypony: By optics, you mean how people perceive us right? Like regardless of quality, if folks believe Monero is high quality.
+**\<fluffypony>** msvb-fab: yes
+**\<fluffypony>** so the other thing that happens is that malware can be found in the wild
+**\<fluffypony>** and maybe it uses a particular mining pool
+**\<fluffypony>** the Malware Response Group can approach that pool's operator and ask them to please block that address
+**\<fluffypony>** which his good for the pool, too, because malware has a negative performance impact on pools
+**\<serhack>** what will Malware Response group do if a big company has malicious miner?
+**\<fluffypony>** serhack: they can do both - help the company figure out how to remove the malware, and try block it at a pool level
+**\<serhack>** cool
+**\<ArticMine>** It is a start.
+**\<ArticMine>** but I am not that optimistic
+**\<fluffypony>** ArticMine: it lets us answer the question reporters often ask: "what are you doing about cryptojacking / malicious miners?"
+**\<fluffypony>** then we can just point to the existence of the Malware Response Workgroup
+**\<ArticMine>** True
+**\<sgp>** ArticMine, it's not about stopping all malware. It's about optics and providing some level of help
+**\<fluffypony>** whether they are effective or not doesn't matter
+**\<serhack>** fluffypony: what do you mean by malicious miners? Coinhive could be a malicious miner.
+**\<ArticMine>** Yes this is the problem the gray area
+**\<fluffypony>** serhack: yes absolutely, as is botnet malware
+**\<xmr\_eric>** The solution doesn't need to be comprehensive. It just needs to address the basics.
+**\<msvb-fab>** fluffypony: Is part of the problem that the affected click on 'vulnerability response' and send email to you and Luigi?
+**\<msvb-fab>** ...thus overwhelming just a couple security officers?
+**\<fluffypony>** msvb-fab: nope, not at all
+**\<fluffypony>** this has nothing to do with the VRP
+**\<fluffypony>** this is about Monero being used in malware, typically via mining
+**\<QuickBASIC>** It's a nice thought, but if the MRW is ineffective at reducing the amount of malware then it's just going to be a big joke.
+**\<fluffypony>** but later on also ransomware
+**\<fluffypony>** QuickBASIC: how will anyone know if they're effective?
+**\<msvb-fab>** I'm imagining what I would do when going to getmonero.org and trying to find an easy way to solve my security problem.
+**\<msvb-fab>** I would click 'vulnerability respons' because I don't see anything else related.
+**\<fluffypony>** msvb-fab: we're mostly dealing with senior infosec people, they're not dumb enough to do that
+**\<msvb-fab>** We're dealing with senior cisos and they can't secure their mining rigs? that's surprising.
+**\<QuickBASIC>** My background is in IT support. I've done mostly internal IT for the last several decades... It's anecdotal, but a user that allows their box to be owned by malware to that degree is not going to be able to be assisted in removing their own malware... even if we had a call center full of folks walking them thru it.
+**\<fluffypony>** msvb-fab: no no, they're called in to clients who are infected, or they're researchers who find malware in the wild
+**\<fluffypony>** QuickBASIC: we're not going to provide assistance at that level
+**\<QuickBASIC>** fluffypony: I'll ask you a question to answer your question. How will people know that it IS effective?
+**\<fluffypony>** QuickBASIC: this is optics, the very existence of the MRW is enough
+**\<ErCiccione>** I agree with QuickBASIC, i see an high possibility of fighting windmill with live support, but create some kind of documentation sound good
+**\<QuickBASIC>** I wasn't suggesting we provide assistance at that level.
+**\<fluffypony>** we're not providing live support, guys, let's put that idea out of everyone's head right now
+**\<fluffypony>** this is almost entirely about how we interact with infosec researchers, and what we can say to reporters
+**\<QuickBASIC>** But a couple of guides on a webpage isn't going to *actually* help anyone... It's just window dressing.
+**\<ArticMine>** Exactly
+**\<sgp>** QuickBASIC: that's literally the point
+**\<netg>** i like the idea
+**\<ArticMine>** In fact it can make things worse
+**\<sgp>** @ArticMine how could it make things worse?
+**\<QuickBASIC>** Anyone with the level of competence to understand that they need assistance with removing malware is going to have the knowledge to seek out other resources that already provide that assistance.
+**\<ArticMine>** It can give a person wrong advice. There is no we can identify every king of malware based upon Monero
+**\<ArticMine>** I had to deal with Malware infected FLOSS that was distributed via Google ads
+**\<ArticMine>** It caught a very experienced Windows administrator
+**\<fluffypony>** this is the stuff we're fighting against
+**\<fluffypony>** https://twitter.com/MalwarePatrol/status/938130889401303040
+**\<QuickBASIC>** What happened to the party line "we can't control what people do with Monero". If we start having the appearance of taking ownership of what people do maliciously with Monero, it could be a bad look for the Monero community... i.e. Look they have a Malware workgroup and look how ineffective it is at making all the bad stuff in the world stop happening.
+**\<fluffypony>** https://twitter.com/acotino/status/938112236211658753
+**\<fluffypony>** https://twitter.com/ostinjohn/status/937735578619170816
+**\<ArticMine>** It was on a fresh install of Windows XP
+**\<fluffypony>** https://twitter.com/Wayne_Bridgeman/status/936782031933005824
+**\<fluffypony>** that's all in the past week
+**\<ArticMine>** The infected software was VLC
+**\<ArticMine>** I only caught it because of a GPL violation
+**\<ArticMine>** I had to reinstall XP in order to connect o Windows server
+**\<cryptochangements>** devil's advocate: if we start trying to "combat" malware does that mean we also have to help LE with DNMs since they give us a bad image?
+**\<QuickBASIC>** I understand that what you're proposing is supposed to diminish the negative views of Monero in the press, but I think it's the wrong tact... I think positive use cases will outweigh any kind of reduction in peoples view of Monero because of some people choosing to use it for malicious purposes.
+**\<ArticMine>** It is a huge problem in FLOSS F-Droid Android apps that are infected with malware and uploaded to goggle play
+**\<fluffypony>** cryptochangements: why do you think we don't allow DNM posts on /r/monero ?
+**\<msvb-fab>** DNM \=\= ?
+**\<fluffypony>** msvb-fab: darknet markets
+**\<dEBRUYNE>** fluffypony: fwiw, I remove any thread that somewhat reeks of illegality
+**\<fluffypony>** dEBRUYNE: yep I know
+**\<cryptochangements>** not allowing people to talk about something!= helping (more or less effectivly) people stop something
+**\<netg>** i mean having such a group and educating our own community is by itself positive
+**\<netg>** people getting ripped of their xmr by malware are mostly lost for the project
+**\<fluffypony>** netg: agreed
+**\<ErCiccione>** QuickBASIC and ArticMine have both good points, how can we provide some kind of assistance (at least minimal) but always "at distance"? The group could be the point of contact, but shouldn't give practical solutions (to avoid responsabilities of eventual mistakes) They can provide documentation and other kind of support (like suggesting who to speak with, more info about Monero's technology)
+**\<fluffypony>** ErCiccione: we write guides, and we make those guides available
+**\<cryptochangements>** i just dont want things to come off as hypocritical if we address one "bad" thing but not another
+**\<fluffypony>** the guides are non-specific
+**\<netg>** cryptochangements: malware would be an attack against the project (our users)
+**\<ArticMine>** The most effective tools I can think of are 1) A resource directory on malware that points to resources on malware removal 2) Having a working group as fluffypony has suggested 3) Aggressive trademark enforcement 4) I know this is controversial moving to a copyleft license
+**\<sgp>** I have the meetup and need to run, but please continue this discussion and move to open ideas time if there is some extra time
+**\<sgp>** The next meeting will two weeks from today on 23 December at 17:00 UTC.
+**\<ArticMine>** 3) and 4) allow us to use existing legal channels to go after the grey / white area
+**\<fluffypony>** ok sgp, all I really wanted to do in this meeting as well is find someone to head the workgroup up and run with the idea
+**\<ErCiccione>** fluffypony: beside guides, my point is that we should decide how deep the eventual support should be
+**\<fluffypony>** so if anyone wants to volunteer please ping me
+**\<ArticMine>** I am talking DMCA take downs etc
+**\<netg>** ArticMine: bitcoin, debian, tor never needed aggressive trademark enforcement
+**\<netg>** and wtf, people doing harm dont respect laws anyway
+**\<netg>** no free project needs that
+**\<netg>** super lame
+**\<ArticMine>** I mean the grey / white area not black
+**\<ArticMine>** Actually there has been a DMCA breakdown over Ubuntu against the MPAA
+**\<ArticMine>** about 11 years ago
+**\<ArticMine>** It was over GPL violations
+**\<sgp>** @fluffypony I am happy to work on this
+**\<fluffypony>** ok cool
+**\<ArticMine>** Matthew Garrett did ti
+**\<fluffypony>** so then if anyone else wants to volunteer for the MRW ping sgp :)
+**\<ArticMine>** What is interesting is any contributor can do it on their own
+**\<ErCiccione>** we have ten more minutes. Open ideas time?
+**\<serhack>** sgp what do you think?
+**\<ArticMine>** netg when targeting for profit entities and large corps it is not super lame. It is ust a does of their won medicine
+**\<ErCiccione>** ok my idea: I'm building a taiga bot, so we will have live updates from taiga on irc, will let know when ready so who needs it can use it
+**\<serhack>** my idea: Mastering Monero ebook. https://www.reddit.com/r/Monero/comments/7imsr9/hello_world_mastering_monero_is_coming_soon/ :)
+**\<ErCiccione>** (btw i think we still need to define better the MRW team's duties before starting the actual recruiting)
+**\<ErCiccione>** If we are considering the meeting over, the discussion about the MRL can restart
+**\<msvb-fab>** We still have five minutes left...
+**\<msvb-fab>** parasew[m] pablonero[m]: Any action with planning Monero December, what progress has been made in the first week of December?
+**\<msvb-fab>** We have quite a nice activities list in December, the Vienna RIAT group (I think that stands for Research Institute of Austria) is hosting.
+**\<rehrar>** Msvb, I'll fill out the stuff today soon. :)
+**\<msvb-fab>** A number of us will be travelling on Thursday 14 December, and spend the weekend.
+**\<msvb-fab>** rehrar: You mean about the RIAT hosted meetings in Vienna?
+**\<rehrar>** No. For wallet test.
+**\<msvb-fab>** rehrar: Oh, you mean I think... Yes. That's great, thanks.
+**\<msvb-fab>** I think the two who know most/best about the Vienna stuff are parasew[m] pablonero[m], so look for them on #monero-ccc for more information.
+**\<rehrar>** Sorry for not being here today. Wife graduating. :) If anyone needs something from me, send me a ping.
+**\<rehrar>** Will go over log soon.
+**\<msvb-fab>** ErCiccione: We can chat about MRW now?
+**\<ErCiccione>** ok, i'll do the sgp/rehrar of the situation :D [8] Meeting is over thanks everybody for partecipating!
+**\<ErCiccione>** let's talk about MRW now
+**\<netg>** what we always should highlight is what, separates monero from the rest of the projects, its is the mindset and strong belief, that an completely anonymous egalitarian cryptocurrencies is strongly needed, by alot of people world-wide, and if existing would improve whole humanity
+**\<ErCiccione>** This is what I was talking about with this comment: https://github.com/monero-project/meta/issues/141#issuecomment-350490380). Discussions rarely continue after the meeting. A very participated and important discussion died.
+**\<ErCiccione>** fluffypony ^^
+**\<fluffypony>** ErCiccione: further discussion about the MRW can happen within the MRW :)
+**\<fluffypony>** I unfortunately wouldn't have been able to continue the discussion anyway, I'm busy fixing MyMonero problems
+**\<ErCiccione>** sure, but this shows that the problem actually exist. This happened and will happen with other subjects. We need to find a way to optimize and don't cut these discussions
+**\<endogenic>** ErCiccione: can't anyone bring up the issue when they want and ping the involved parties?
+**\<endogenic>** involved -> interested even
+**\<ErCiccione>** that doesn't solve the problem. A discussion flows during a meeting, but if it gets interrupted is gonna be hard to remake the logical processes. Meetings are the place for this kind of discussions, it's psicologically hard to restart this conversations with the same intention, the feeling of "officiality" get lost. this means that another meeting will be necessary to make the discussion official. I don't know if i explained
+**\<ErCiccione>** well my point
+**\<ErCiccione>** but this is my opinion, if i'm the only one feeling the problem, we can just keep going like this. I still think a lot of time will be wasted though
+**\<endogenic>** sorry, what's the problem?
+**\<netg>** ErCiccione: monero development isnt super fast anyway, because its based on long-term considerations
+**\<ErCiccione>** endogenic: https://github.com/monero-project/meta/issues/141#issuecomment-350487067
+**\<endogenic>** no i know ErCiccione
+**\<endogenic>** i'll type somethin out
+**\<endogenic>** sec
+**\<netg>** its a top 10 coin, has a healthy community, is building the first infrastructure and is considered the best contender in its niche
+**\<endogenic>** the officiality aspect comes from people agreeing on the existence and importance of a problem…Â
+**\<netg>** what do you need more
+**\<endogenic>** ErCiccione: example then
+**\<endogenic>** did you see Jaquee post this? https://www.reddit.com/r/Monero/comments/7ingmi/transferred_3100_usd_to_mymonero_over_4_days_ago/dr01xy2/
+**\<endogenic>** i wanted to reply saying that this is a real foss project so someone must do it and if it's not he who will write the code or design the solutions and he still thinks he knows something then it's on him to inspire others to be the hero to solve it
+**\<endogenic>** now i would suggest that'd be an example of leadership for him
+**\<endogenic>** if i wanted to solve the problem he wanted to solve i'd just make it specific what the issue is, then take it to the people who are working on it, and show them it's real
+**\<endogenic>** if they don't think it's an issue then i can tell others "this person didn't think it was an issue"
+**\<endogenic>** it's just facts
+**\<endogenic>** wonder if that makes any sense?
+**\<Jaquee>** endogenic: he posted the same message in several places. i also wrote this answer: https://www.reddit.com/r/Monero/comments/7ingmi/transferred_3100_usd_to_mymonero_over_4_days_ago/dr02f7i/?st=jazoidya&sh=ca6b4e35
+**\<ErCiccione>** mmmh I think we went out of track, sorry I didn't explain myself well :) . My point is just: can we make meetings longer so we don't cut out important conversations? I think this is more about the conception each of us has of the meeting. For me all formal discussions should be done during meetings. But this is how I'm used to for my personal experience. if it's not perceived as a problem. Ok, fine for me :D
+**\<endogenic>** ErCiccione: have you ever heard the theory about how widening highways doesn't actually solve traffic problems?
+**\<endogenic>** i think it might be similar with meeting times
+**\<netg>** +1 for longer meetings
+**\<fluffypony>** why not just have meeting once a week instead of every 2 weeks?
+**\<ErCiccione>** I'm talking for my personal experience. I've been doing meetings for about 12 years and sometimes they lasted even 6 hours for that very reason. But i'm talking about a completely different environment
+**\<ErCiccione>** fluffypony: I would personally prefer longer meetings than more often, but that could be a solution
+**\<fluffypony>** I'd kill myself if I had to sit in a 6 hour meeting
+**\<ErCiccione>** and wasn't a friendly environment, I was very close to :)
+**\<netg>** i just think, we dont need a hard stop at the planed finishing time
+**\<netg>** 10 till 30 mins longer depending on if there is something left to talk
+**\<netg>** would be ok, IMHO
+**\<ErCiccione>** netg: I agree, that's basically what i suggested here: https://github.com/monero-project/meta/issues/141#issuecomment-350490380
+**\<DaveyJones>** some kind of meeting reflecting + discussion
+**\<DaveyJones>** reflection
+**\<netg>** like a sprint review in scrum?
\ No newline at end of file
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 0000000000000000000000000000000000000000..cbc7684a8e61d46fbcbfc81ee01e739e74bd37cf
--- /dev/null
+++ b/_posts/2017-12-11-A-note-on-fees.md
@@ -0,0 +1,123 @@
+---
+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
+- **Bitcoin Cash:** ~$0.07
+- **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 / M<sub>N</sub>) - 1)²**
+
+The new reward is:
+
+**NewReward = BaseReward - Penalty**
+
+Where:
+
+ - M<sub>N</sub> 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 2M<sub>N</sub>
+
+Note that the formula of the BaseReward is defined [as follows](https://bitcointalk.org/index.php?topic=583449.0):
+
+**BaseReward = 2 * ((S - A) * 2<sup>-20</sup> * 10<sup>-12</sup>)**
+
+Where:
+
+ - 2 is the adjustment factor for the switch to two minute blocks
+ - S is the initial number of atomic units is = 2<sup>64</sup> - 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 10<sup>12</sup> (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 M<sub>N</sub> 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 per kB = (R/R<sub>0</sub>) * (M<sub>0</sub>/M) * F<sub>0</sub> * (60/300) * 4**
+
+Where:
+
+- R is the base reward
+- R<sub>0</sub> is the reference base reward (10 XMR)
+- M is the block size limit
+- M<sub>0</sub> is the minimum block size limit (300 kB)
+- F<sub>0</sub> is 0.002 XMR
+- 60/300 is the adjustment factor to account for the increase of the minimum block size limit (60 kB -> 300 kB)
+- 4 is the adjustment factor to account for the default fee multiplier. That is, the lowest fee level uses a multiplier of 1, whereas the default fee level uses a multiplier of 4
+
+As a practical example, a few moons ago the median block size increased to approximately 400 kB and the default fee went down to ~0.0095. As we can see from the formula, this approximately matches the theoretical fee. That is:
+
+`Fee per kB` = (6.5/10) * (300/400) * 0.002 * (60/300) * 4 = ~0.0008
+
+Subsequently, multiply with the size of a typical transaction (~13 kB), which yields ~0.01 XMR.
+
+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
diff --git a/_posts/2017-12-11-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-12-11.md b/_posts/2017-12-11-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-12-11.md
new file mode 100644
index 0000000000000000000000000000000000000000..e86e2e16247bc040268df0aa3b20f756ebe86329
--- /dev/null
+++ b/_posts/2017-12-11-logs-for-the-Monero-Research-Lab-meeting-held-on-2017-12-11.md
@@ -0,0 +1,362 @@
+---
+layout: post
+title: Logs for the Monero Research Lab Meeting Held on 2017-12-11
+summary: Bulletproofs (range proofs), ASIC resistance, and miscellaneous
+tags: [community, crypto, research]
+author: dEBRUYNE / fluffypony
+---
+
+# Logs
+
+**\<suraeNoether>** yes we do
+**\<suraeNoether>** good morning everyone
+**\<suraeNoether>** moneromooo, smooth, andytoshi, ArticMine, stoffu, fluffypony, endogenic, gingeropolous
+**\<suraeNoether>** pero pigeons stoffu vtnerd unknownids
+**\<hyc>** pero is here?
+**\<suraeNoether>** *shrug* his name is on the list, but i haven't heard him say anything since before we funded sarang
+**\<sarang>** "He was never here, Trebek..."
+**\<suraeNoether>** hyc
+**\<suraeNoether>** research meeting in 11 minutes, plus or minus the time it takes people to show up
+**\<sarang>** I set out some coffee and muffins for the meeting, but nobody is taking any
+**\<sarang>** Might have wasted my moneys on that one
+**\<unknownids>** lol
+**\<suraeNoether>** someone had a nice diagram or flowchart of the multisig key usage... anyone remember where it may be stashed? i meant to save it
+**\<luigi1111>** JollyMort[m]: ^^
+**\<suraeNoether>** ah yes
+**\<suraeNoether>** now i can scan my logs for it
+**\<endogenic>** meeting adjourned
+**\<suraeNoether>** lol
+**\<suraeNoether>** Welcome everyone to the Nth MRL research meeting
+**\<sarang>** hullo
+**\<suraeNoether>** agenda: 1) hellos, 2) sarang's work recently, 3) my work recently, 4) a grander discussion of "what's next after the multisig paper"
+**\<suraeNoether>** oh, and actually insert between 3) and 4) above: any other interesting research anyone else is doing
+**\<ArticMine>** hi
+**\<suraeNoether>** i know that we have at least two (i think) computer science folks in here working on things.
+**\<suraeNoether>** howdy everyone
+**\<suraeNoether>** ok, well... sarang, you want to catch us up to speed on your past few weeks?
+**\<sarang>** Sure
+**\<sarang>** Updates to the BP code (both single- and multi-output) were completed for compatibility with our existing commitment formats
+**\<sarang>** initial unit testing looks good
+**\<sarang>** The single output case has been tossed over to testnet
+**\<sarang>** A blog post was made to getmonero.org to explain our two-stage process
+**\<sarang>** First single-output (SO), then multi-output (MO)
+**\<sarang>** Doing SO first will let us sidestep the fee question for now
+**\* suraeNoether** just got a phone call from the "tax crime investigation department of the IRS." Everyone be aware: the IRS contacts you by mail not phone!
+**\<sarang>** while still gaining a lot in terms of space and verification efficiency
+**\<sarang>** Now, there are still opportunities to speed up verification
+**\<suraeNoether>** that's great news to hear
+**\<sarang>** I want to get us a better multiexponent method
+**\<sarang>** andytoshi has been working up some code for his curve of choice with his collaborators
+**\<sarang>** I did some rough testing that didn't perform as well as expected, but that can be worked on going forward
+**\<suraeNoether>** if we can get it even faster, we can play a nice game optimizing a balance between RTRS RingCT sizes and transaction throughput
+**\<sarang>** Nice thing is that any verification optimization is a drop-in function replacement
+**\<sarang>** The savings will be more relevant when we move to MO
+**\<sarang>** since that increases the number of fixed curvepoints we use in the algorithm
+**\<sarang>** I also know there's good discussion happening about the best timetable for both SO and MO
+**\<sarang>** whether or not doing SO in March is too fast, or just right, etc.
+**\<suraeNoether>** what is your opinion on that, and what are the arguments for/against going slower/faster?
+**\<sarang>** Well, it's a new method, and there are arguments against using the absolute newest stuff
+**\<sarang>** But it's also very good
+**\<sarang>** I think having it in testnet makes sense
+**\<suraeNoether>** do we have an opinion on putting up a bounty for exploits before moving it to mainnet?
+**\<sarang>** and it does address major concerns that our public has about bloat and feez
+**\<suraeNoether>** i was just looking at our average fees on monero.how
+**\<sarang>** I think there'd be a bit of a PR hit if we kept it out of March (though that is *not* an endorsement against proper testing)
+**\<sarang>** My preference is to continue beating the bejeezuz out of it in testnet and determine where that takes us
+**\<suraeNoether>** yeah, PR is not relevant to security. thing is, unless price increases by an order of magnitude (we should be so lucky), I feel like fees still aren't a big deal. they are quite low in monero compared to bitcoin, in best, worst, and average case
+**\<sarang>** Hoping to hit March, but not making the testing dependent on that timeline
+**\<suraeNoether>** but thats measured in fiat
+**\<endogenic>** in that case, is a bounty a good idea?
+**\<endogenic>** seems it might incentivize some testing
+**\<suraeNoether>** i like the idea of bounty-ing bulletproofs
+**\<sarang>** As do I
+**\<endogenic>** may i bring up something related?
+**\<endogenic>** but not to bulletproofs specifically
+**\<sarang>** For better or worse, BPs have been hyped, and anything that gets them tested is a Good Thing
+**\<suraeNoether>** we can simply dump 2\^N bulletproofs into a file and challenge the community: if you can open even one without knowing our secret masks, we'll give you such and such amount of XMR
+**\<sarang>** Well, that's not the only thing we care about
+**\<suraeNoether>** endogenic yes, let's append that to the "other stuff people are working on"
+**\<suraeNoether>** yeah, also the computational waste
+**\<sarang>** e.g. choosing "random" values in a clever way, or generating edge cases
+**\<sarang>** Or gaining partial info about amounts w/o exact values
+**\<suraeNoether>** oh i see
+**\<sarang>** endogenic: fire away
+**\<endogenic>** ok, similarly, i've been wondering how much traditional pentesting etc has been done on Monero… i've heard some fuzzing has been done, but i'm wondering as well if a more organized effort will be valuable
+**\<endogenic>** i think it would be
+**\<sarang>** Well, we already have a bounty program, no?
+**\<sarang>** A general one?
+**\<sarang>** And there was a recent large FFS for bounty
+**\<suraeNoether>** do we have a set of formal security games for bulletproofs defined for the properties we are concerned about breaking on mainnet? i know that something like a spam attack isn't easily model-able that way, but there are other properties from my understanding.
+**\<endogenic>** i've been curious about that too \^
+**\<suraeNoether>** endogenic: can you elaborate?
+**\<endogenic>** er sorry, on which?
+**\<suraeNoether>** i feel like since monero is a cryptocurrency there is a large financial incentive for penetration
+**\<sarang>** suraeNoether: the paper establishes security definitions
+**\<sarang>** proved for MO, for which SO is a degenerate case
+**\<endogenic>** suraeNoether: yeah but there might also be disincentives to let us know about it :P
+**\<suraeNoether>** endogenic: true...
+**\<suraeNoether>** well in regards to the BP, does anyone have any strong opinions on this or are we just going back and forth on speed of implementation?
+**\<suraeNoether>** and by speed i mean how quickly we are moving to mainnet not verification time
+**\<suraeNoether>** ok, sarang, anything else for you?
+**\<suraeNoether>** from\*
+**\<ArticMine>** My only questions relate to pricing vs cost when there is a cost that does not scale the same way as size
+**\<sarang>** I'm assisting suraeNoether with finalizing his paper
+**\<sarang>** And doing background work on recent zk-snark developments
+**\<sarang>** More to discuss in our "future work" segment
+**\<suraeNoether>** ArticMine: can you elaborate?
+**\<suraeNoether>** sarang: yeah no kiding
+**\<ArticMine>** This would relate to the scaling of verification time
+**\<sarang>** ArticMine: yes, the discussions on fee/penalty structure have been around this
+**\<sarang>** Fortunately they only really apply to MO-BPs, and not SO-BPs
+**\<ArticMine>** I know this may be premature at this time
+**\<sarang>** No, it's good to discuss ASAP
+**\<sarang>** But in parallel to SO deployment
+**\<suraeNoether>** i think our fee structure needs to be evaluated so that it's properties hold more or less invariant over the longrun. if it's possible that our blockchain changes over the next few years so much that miners are getting massive fees for verifying super cheap bulletproofs, or vice versa, we should change the way we compute the fees (even if we think current fee amounts are fair... which, personally, i
+**\<suraeNoether>** don't see too much of a problem with current *amounts*
+**\<suraeNoether>** on the other hand
+**\<ArticMine>** It comes down to the cost of verification vs size
+**\<sarang>** yes
+**\<suraeNoether>** yep. however... what has been banging around in my head is to take all the improved cost of verification and dump it into larger ring signatures
+**\<suraeNoether>** using RTRS RingCT
+**\<sarang>** We want to encourage the use of MO-BPs (as opposed to multiple SO) while avoiding scaling differences
+**\<suraeNoether>** hmm
+**\<ArticMine>** But size alone will do that
+**\<suraeNoether>** i need to read up on BPs. now that sarang is working on the multisig paper, i have time to learn about them.
+**\<sarang>** The bottom line is that size scales as O(log2(M)) and verification scales as O(M)
+**\<sarang>** for M outputs
+**\<ArticMine>** At what point does verification become an issue
+**\<sarang>** Miners should prefer MOs (or protocol should enforce them vs multiple SOs)
+**\<suraeNoether>** is our fee structure based on size as opposed to verification time?
+**\<sarang>** yes
+**\<suraeNoether>** i think it is
+**\<suraeNoether>** yeah
+**\<suraeNoether>** hmm
+**\<ArticMine>** Our fee structure is currently only based upon size
+**\<sarang>** ArticMine: verifying multiple SOs already scales as O(M)
+**\<suraeNoether>** what if we merely take a joint model where we take A\*size + B\*verification time for appropriately chosen constants A and B?
+**\<suraeNoether>** as our fee
+**\<ArticMine>** So id the blocksize penalty
+**\<sarang>** It's actually a little less for an MO
+**\<suraeNoether>** pick A to determine how much the miner should be compensated for storing the BP, pick B to determine how much the miner should be compensated for burning verification time on something other than hashrate
+**\<ArticMine>** I have to give this a lot of thought
+**\<suraeNoether>** yeah, this is not a simple one-and-done discussion.
+**\<ArticMine>** because it also impact the question of exchange
+**\<suraeNoether>** what do you mean by that?
+**\<sarang>** And a solid general approach to it would help address future developments that affect size vs computation time
+**\<ArticMine>** Purchasing power of Monero should scale with the number to outputs
+**\<luigi1111w>** \<suraeNoether> yep. however... what has been banging around in my head is to take all the improved cost of verification and dump it into larger ring signatures \<= I disagree. Of course there's no perfect answer, but cpu cost is currently quite on the high side IMO, and I'd like to see it lower overall.
+**\<ArticMine>** So we may have to scale the output part of the fee with the total number of outputs in the block as opposed to the blocksize
+**\<ArticMine>** Essentially two fee components one size based and one output based
+**\<suraeNoether>** ArticMine: i will need to think about that. i think computing expected verification time of a transaction should be very simple, and is a more direct measurement of how much the miner is burning on that transaction
+**\<sarang>** Yes let's continue to think about and discuss this going forward
+**\<sarang>** suraeNoether this ends my report
+**\<ArticMine>** Yes it is an other "effective penalty"
+**\<hyc>** that's the obvious way forward - if you are accounting for both storage space and CPU cost, you need the two factors present in the fee
+**\<suraeNoether>** so, actually, i want to address luigi's point
+**\<suraeNoether>** because we are tugging at two ends of the rope, cpu efficiency versus privacy
+**\<suraeNoether>** i think if monero users want to enjoy privacy over the long run, we need either zk-stark whole-blockchain-like signatures, or we need very large ring sizes. and in both cases, we can't have authenticating data like signatures scale linearly in size, or we are sunk in the water.
+**\<suraeNoether>** i've been using the attitude that each gain in speed or performance can be matched with a bigger RTRS RingCT so that users don't necessarily notice any performance change, their privacy merely increases
+**\<suraeNoether>** on the other hand, we can make things faster while keeping monero's privacy where it's at
+**\<suraeNoether>** the goal is hopefully to meet in the middle somehow
+**\<suraeNoether>** underneath the entire BP discussion is which direction we are going to take Monero over the next few months or years
+**\<suraeNoether>** which was why I wanted to bring up point 4) before, about "the future."
+**\<hyc>** along the lines of that question - if CPUs get faster over time, that should mean we can increase ringsize in the future
+**\<endogenic>** imo better to prioritize privacy
+**\<luigi1111w>** or keep up with increased use
+**\<hyc>** since we're talking about linear increases in verification cost, is there a tradeoff in traceability?
+**\<ArticMine>** Yes but we also have to keep in mind blocksize
+**\<suraeNoether>** what's that one economic principle? make something more efficient and people just use more of them instead of the overall system using fewer things. Jevon's paradox?
+**\<hyc>** e.g. if CPUs get 2x faster, does it become 2x easier to analyze the blockchain?
+**\<sarang>** https://en.wikipedia.org/wiki/Snackwell_effect ?
+**\<luigi1111w>** hyc I don't think so
+**\<ArticMine>** It is starting to look like verification time rather than size becomes the dominant cost parameter
+**\<moneromooo>** If CPUs get faster, we have more users and larger blocks.
+**\<suraeNoether>** (by the way, for point (3): the past weeks I've been working on multisig and that's essentially all. After handing it off to sarang I am now extremely excited to read about BPs and the new zk-starks, which could simply make this whole discussion moot anyhow.)
+**\<luigi1111w>** that would be some entity data crunching. They'd just add as many cpus as needed
+**\<luigi1111w>** I guess technically it'd be cheaper too, but the cost is likely not high enough to matter one way or the other
+**\<ArticMine>** Yes but the cost of verification scales exponentially relative to size
+**\<suraeNoether>** ArticMine: the verification time does appear to have become the most important feature of new cryptoschemes, to me
+**\<ArticMine>** It could become dominant eventually because of the different scaling rates
+**\<suraeNoether>** hyc: if it's exponentially difficult (in # of blocks say O(2\^i)) to analyze the monero blockchain, and you double your blocks/s of analysis, you still have an exponential amount of time for analysis O(2\^(i-1))
+**\<hyc>** Ok so that implies we wouldn't need to increase ringsize very often in the future
+**\<ArticMine>** However we must keep in mind that not all users will move to large MO proofs
+**\<luigi1111w>** why wouldn't they?
+**\<sarang>** If the vast majority of txns are still 2 outputs, that wouldn't change
+**\<moneromooo>** Mymonero users ? :)
+**\<ArticMine>** It is only advantageous to very large payers
+**\<luigi1111w>** moneromooo I think endogenic is working on copying the c++ wallet code, so it'd likely include that
+**\<luigi1111w>** otherwise I'll add it to JS probably
+**\<moneromooo>** Great.
+**\<endogenic>** we may even be able to transpile that C++ back to JS for the new web wallet, but the rest will run on the C++ yes
+**\<luigi1111w>** well I'll add it to JS anyway, for my own stuff, but probably mymonero.com too if needed
+**\<suraeNoether>** so, in terms of "The Future:" sarang and I want to write up the Monero Standards, which we are excited about, and in those standards we simply want 1) to describe what the monero codebase currently does, 2) why those choices seem to have been made (if monero) or kept (if cryptonote reference), and 3) an outline of possible future algorithms for use in place of each piece. This whole discussion about
+**\<suraeNoether>** verification time, etc, goes back to a question of which algorithms we might in "possible future algorithms," and our motivations/design philosophies for doing so.
+**\<serhack>** suraeNoether: Monero standards will be helpful for me in order to write the ebook.
+**\<suraeNoether>** serhack: the Monero Standards are going to be extremely helpful to the community for a long time afterwards. they are going to be extremely un-sexy to the community
+**\<suraeNoether>** "Now unveiling... Monero Standards! Where we tell you what we are already doing!"
+**\<hyc>** lol
+**\<suraeNoether>** "Turns out we never had a manual all along!"
+**\<serhack>** thanks suraeNoether
+**\<suraeNoether>** but i suspect htey will be referenced over and over and over and over and over
+**\<suraeNoether>** so, this is obviously an ongoing discussion. anyway. I also had an idea for educational outreach
+**\<suraeNoether>** aaaand I'm not sure if I want to talk about it yet. just like the last idea fell through, I am glad I never mentioned a specific university.
+**\<suraeNoether>** buuuut I think the community will like the idea, and I'll be hopefully announcing something about it in the middle of next month
+**\<suraeNoether>** on another note, this POW contest idea
+**\<suraeNoether>** if it were used for message authentication or anything like that, cryptonight would be wildly dangerous as a home-brewed hash function
+**\<hyc>** why so?
+**\<sarang>** In terms of public scrutiny?
+**\<suraeNoether>** unlike other hash functions, it sort of rolls a die, picks a random hash function from a certain list based on that die, hashes its random data. then it swaps some bits around, i believe there is an AES stage, and then repeat. does this for a number of rounds
+**\<suraeNoether>** until the L3 cache is totally filled up with this randomness
+**\<suraeNoether>** I believe
+**\<hyc>** pretty much, yeah
+**\<hyc>** ok so it'd be crap for signatures
+**\<suraeNoether>** point is: in 2013, if you were a 19 year old sitting around smoking pot trying to come up with a way to invent an asic resistant hash function, and all you knew about computers was that L3 functions are slow and that these handful of hash functions are considered good, this is *EXACTLY* the hash function you would come up with.
+**\<suraeNoether>** s/L3 functions/L3 cache (oy)
+**\<suraeNoether>** so the POW alternative thing is something that has been niggling at my mind for awhile
+**\<suraeNoether>** and i'm thinking i'm willing to match the Monero community up to a certain amount in XMR for a nice, big, public contest on the matter
+**\<luigi1111w>** the dice is at the end btw
+**\<hyc>** L3 isn't that slow, and it's faster than main RAM. this was a pretty good approach to prevent trivial optimization (fitting into L2 or faster)
+**\<luigi1111w>** https://github.com/monero-project/monero/blob/master/src/crypto/slow-hash.c#L488
+**\<suraeNoether>** luigi1111w: ah, thanks, i thought i had the order mixed up
+**\<suraeNoether>** hyc yes, you are correct
+**\<sarang>** It'd be important to determine what you'd want out of a new PoW suraeNoether
+**\<suraeNoether>** right
+**\<suraeNoether>** we need a rubric for judging the submissions
+**\<suraeNoether>** we need a panel of judges that are more or less impartial
+**\<hyc>** you want another asymmetric function, like PKI. slow to prove, fast to verify.
+**\<suraeNoether>** yep
+**\<suraeNoether>** if it's ASIC-able, it should be commoditized already for improved egalitarian mining and for improved environmental impact
+**\<suraeNoether>** i'm not sold that Nakamoto hash-based PoW is "the best" idea, although I know that whatever "the best" process is, it should end up being a poisson process
+**\<suraeNoether>** i want provable security for every attacker % up to and including 50%
+**\<suraeNoether>** etc etc
+**\<suraeNoether>** i'm wondering if anyone else would be willing to match some XMR
+**\<sarang>** Well hash-based has the advantage of being extremely fast to verify
+**\<sarang>** and well understood if you use an accepted hash function
+**\<suraeNoether>** because a prize could get really hefty really fast if some folks promise matching.
+**\<suraeNoether>** yep sarang there are an enormous number of advantages with hash functions
+**\<suraeNoether>** by the way, my idea i talked about yesterday on using discrete log + nakamoto PoW... I later in the day proved that it was a bad idea
+**\<suraeNoether>** i have a nice little theorem "Do not implement this scheme."
+**\<suraeNoether>** provably true
+**\<hyc>** lol
+**\<luigi1111w>** fast to verify is important
+**\<luigi1111w>** slow to prove is pretty meh
+**\<hyc>** cryptographic hashes are designed to be fast. and they don't have the desired asymmetry
+**\<luigi1111w>** resistant to excessive speedup, sure
+**\<hyc>** slow to prove is an essential component of the original PoW definition
+**\<hyc>** applied to anti-spam email service
+**\<luigi1111w>** that is provided by difficulty though
+**\<suraeNoether>** it's sufficient to replace "slow to prove" with "exponential space-time tradeoff in proving time." This way, if someone can manage a speedup, they are paying the cost with necessary storage space.
+**\<suraeNoether>** so either way you have to sink cost into hardware to participate
+**\<hyc>** I would assume one of the goals is to be reasonable on existing deployed CPUs
+**\<hyc>** whether in PCs or smartphones
+**\<suraeNoether>** so, what are people's feelings on hosting such a contest? I think I would have a 3-6 month submission deadline or something along those lines. At least 3 months so that a student can spend a full semester working on the problem with their adviser, if they want.
+**\<suraeNoether>** hyc \^ this assumes we do POW on a CPU as opposed to proof-of-storage-and-retrieval on a hard drive... and i don't want to restrict the contest submissions to PoW only.
+**\<endogenic>** i'd be concerned to confirm strategy for handling technicalities with running the contest… deciding a singular winner… what happens if there is no winner…
+**\<endogenic>** i know you already mentioned it surae
+**\<sarang>** It'd be a highly nontrivial thing to do
+**\<sarang>** You need lots of external testing
+**\<sarang>** that's why the NIST contests take so freaking long
+**\<moneromooo>** I really don't like the idea of creating an expectation we'll change to whatever this unearths.
+**\<iDunk>** ^^
+**\<luigi1111w>** I don't think that is expected
+**\<luigi1111w>** or if it is, cancel that
+**\<luigi1111w>** (expectation)
+**\<sarang>** the incentive to test NIST standards is the understanding of widespread adoption
+**\<suraeNoether>** moneromooo: we can say the default entry is the cryptonight algorithm submitted by the general fund.
+**\<suraeNoether>** everyone is competing against htat
+**\<luigi1111w>** I would be curious to see the parameters I guess
+**\<suraeNoether>** to get into the second round of judging, if we have multiple rounds, requires outrunning the bear: cryptonight. to get into the third round of judging requires outrunning each other.
+**\<hyc>** and is ASIC-resistance part of the criteria?
+**\<sarang>** I'd think so
+**\<suraeNoether>** i'm okay with ASICs if they are already commoditized (somehow)
+**\<suraeNoether>** if they are asic-able and someone can come in and blow a million bucks to own the entire monero asic market, that's a losing proposal
+**\<endogenic>** but that requires ppl to buy new hardware just to compete in mining, no?
+**\<hyc>** that seems like a bad idea to me. it means everyone who wants to participate on a level playing field has to buy new hardware.
+**\<endogenic>** seems to change the asic resistence idea
+**\<hyc>** it leaves out the vast percentage of the world that has a smartphone in their pocket
+**\<luigi1111w>** if you can blow a million bucks to own the market, something is very wrong
+**\<luigi1111w>** why can't I come in and also blow a million to take half (and so on)
+**\<ArticMine>** There a patent risks with ASICs - ASIC boost in Bitcoin comes to mind
+**\<moneromooo>** I really like how people have started mining on CPUs for new reasons. This is only possible because mining on a CPU is feasible. Those are gimmicks, granted.
+**\<endogenic>** but they might become much more widespread soon
+**\<endogenic>** people are enabling web miners etc
+**\<ArticMine>** Coinhive opened a can of worms
+**\<endogenic>** ArticMine: passive mining in an app was mostly a matter of convenience then
+**\<endogenic>** bc ppl can still bundle a mining lib and run it in the bg
+**\<endogenic>** if they want to go to the effort
+**\<ArticMine>** The trouble is who controls the mining
+**\<suraeNoether>** hmm. interesting. the whole goal of ASIC resistance is egalitarian mining, in my mind. i don't really care so much about the asic resistance as the egalitarian mining.
+**\<suraeNoether>** so let me rephrase the above
+**\<ArticMine>** The user or the app developer
+**\<endogenic>** ArticMine: who controls the target of the reward, or who controls the algo, or who controls the % of cpu used..? not sure which you mean, or if all three, etc
+**\<ArticMine>** All three
+**\<ArticMine>** In a typical mobile device it is not the end user, and that is a problem
+**\<suraeNoether>** ok, so it sounds to me like people are willing to entertain the idea if the kinks of the governing contest judging body are ironed out, and as long as a rubric is publicly agreed upon. we are quibbling about details on the rubric right now, and that tells me people are receptive to the overall idea.
+**\<hyc>** well... if it ain't broke don't fix it. what's broken?
+**\<iDunk>** "So there is a chance" :D
+**\<moneromooo>** That argument is invalid.
+**\<suraeNoether>** lol iDunk
+**\<suraeNoether>** hyc: if it ain't broke, no one will come up with a better idea
+**\<suraeNoether>** and the money goes back to the general fund
+**\<luigi1111w>** in the schwarz
+**\<suraeNoether>** well
+**\<luigi1111w>** schwartz
+**\<luigi1111w>** idk
+**\<suraeNoether>** if i offer to match some amount of XMR, and the thing doesn't get funded... the contest doesn't go through, you know?
+**\<endogenic>** yeah but we'd hate to see money spent mistakenly
+**\<endogenic>** guess ppl are just saying we need to be cautious
+**\<ArticMine>** What are the advantages?
+**\<serhack>** fund what?
+**\<endogenic>** lol serhack just woke up
+**\<suraeNoether>** serhack see above, i was talking about a PoW replacement contest
+**\<luigi1111w>** the only thing missing from the current pow that I personally care about is verification speed
+**\<luigi1111w>** it's slow
+**\<serhack>** +1 suraeNoether
+**\<serhack>** hello endogenic
+**\<suraeNoether>** ArticMine: 1) coming up with a possibly more egalitarian POW, 2) coming up with a possibly faster verification POW, 3) avoiding an eerily-designed hash function that is essentially unique in its structure
+**\<luigi1111w>** and what does #1 mean? :)
+**\<suraeNoether>** honestly? i don't know yet. measuring egalitarian-ness... doesn't that go back to like ancient greece?
+**\<suraeNoether>** heh
+**\<endogenic>** but people are not equal
+**\<endogenic>** (i looked it up)
+**\<endogenic>** surae has better math ability than i
+**\<luigi1111w>** impossible
+**\<hyc>** I don't see #3 being detrimental in current cryptonight. it's using a bunch of heavily vetted hash algos in combination
+**\<luigi1111w>** ok #2 definitely
+**\<luigi1111w>** #3 I agree with hyc
+**\<suraeNoether>** I'm not terribly concerned about 3) because if cryptonote was designed by scammers, and if cryptonight was designed maliciously, it would be difficult to discern this and it would provide the original miners with a disproportionate hash rate compared to users with similar computers. i'm a little less concerned about 2). But overall? I'm just not convinced that cryptonight is a particularly
+**\<suraeNoether>** well-thought-out way to bring ASIC resistance/egalitarian mining into the hash computation world.
+**\<suraeNoether>** add: "and its not like the original cryptonote founders are a huge % of the mining network"
+**\<suraeNoether>** hit enter a little too soon
+**\<suraeNoether>** and i'm a little *more* concerned about 2). good heavens
+**\<suraeNoether>** seems like the community is more luke warm on the idea than i had hoped. that's cool. i'll shelve it for a few months
+**\<suraeNoether>** okay, does anyone have any other topics to bring up?
+**\<suraeNoether>** Okay, well, meeting adjourned I suppose. luigi, out of curiosity: could you do me a favor? can you come up with some numbers on per-output transaction verification times (total, including ring signatures and range proofs) and PoW verification times that you consider "worst case," we never want to go slower? it would help me figure out whether we can optimize BP + RTRS RingCT to get both large ring
+**\<suraeNoether>** sizes and get verification times down
+**\<suraeNoether>** i feel like per-transaction, we should be trying to keep verification time down under 50ms, but maybe that's too slow
+**\<endogenic>** who's on the monerophone? nobody.
+**\<endogenic>** or everybody.
+**\<endogenic>** or anybody?
+**\<sarang>** In the old days, it was a "party line"
+**\<luigi1111w>** for what hardware ^\_^
+**\<luigi1111w>** and yes definitely under 50ms
+**\<luigi1111w>** complicated question though
+**\<moneromooo>** Not my my hardware then ^\_^
+**\<suraeNoether>** luigi1111w: the question i suppose is for the average node.
+**\<suraeNoether>** and, again, just need upper bounds
+**\<suraeNoether>** i know how to optimize a problem "subject to some cost \<= max\_cost"
+**\<suraeNoether>** in this case verificaiton time
+**\<luigi1111w>** can just use 50 for now
+**\<gingeropolous>** re: i think it'd be nice if we had something waiting in the wings if a change in PoW *was* needed, because right now it seems there's a gestalt that the PoW would change if there was a miracle ASIC.
+**\<gingeropolous>** woops. that should have read re: PoW -
+**\<gingeropolous>** re:
+**\<gingeropolous>** gah, sorry. this ergonomic keyboard. Re: ringsize, privacy, computation time - I have a hunch that we can extract a very useful dynamic parameter from network difficulty.
+**\<suraeNoether>** gingeropolous: yeah, we don't even need to switch to the winner immediately. it could just be the one we put into our long-term piecemeal backup plans.
+**\<hyc>** we know that there are Cryptonight implementations for FPGA already
+**\<hyc>** and apparently they're profitable, now that XMR price has risen
+**\<hyc>** the other aspect of using industry-standard algorithms - you can get impls of them off the shelf, and lump them together as Cryptonight uses them, without much hassle
+**\<ArticMine>** So time may be of the essence to change the POW algorithm
+**\<ArticMine>** In any case this POW algorithm change seems positive to me
+**\<nioc>** othe has already stated that if an asic is produced, a few changes that would be simple to implement in mining software would make those asics useless
+**\<nioc>** I believe he has already done some work on this
+**\<unknownids>** \^ i recall that too
\ No newline at end of file
diff --git a/_posts/2017-12-17-overview-and-logs-for-the-dev-meeting-held-on-2017-12-17.md b/_posts/2017-12-17-overview-and-logs-for-the-dev-meeting-held-on-2017-12-17.md
new file mode 100644
index 0000000000000000000000000000000000000000..29e29b64db38e87cfd7d88a55904c2ffe4341566
--- /dev/null
+++ b/_posts/2017-12-17-overview-and-logs-for-the-dev-meeting-held-on-2017-12-17.md
@@ -0,0 +1,300 @@
+---
+layout: post
+title: Overview and Logs for the Dev Meeting Held on 2017-12-17
+summary: Discussion of open PRs and issues, Bulletproofs, March HF, dedicated HW wallet, and miscellaneous
+tags: [dev diaries, core, crypto]
+author: dEBRUYNE / fluffypony
+---
+
+# Overview
+
+An overview can be found on [MoneroBase](https://monerobase.com/wiki/DevMeeting_2017-12-17).
+
+# Logs
+
+**\<fluffypony>** 1. Greetings
+**\<fluffypony>** 2. Brief review of what's been completed since the previous meeting
+**\<fluffypony>** 3. March hardfork items + code freeze
+**\<fluffypony>** 4. Code + ticket discussion / Q & A
+**\<fluffypony>** 5. Any additional meeting items
+**\<fluffypony>** 6. Confirm next meeting date/time
+**\<fluffypony>** I think we've done 1. so we'll skip it
+**\<fluffypony>** 2. Brief review of what's been completed since the previous meeting
+**\<fluffypony>** well Bulletproofs went live on testnet
+**\<fluffypony>** so there's that
+**\<fluffypony>** and we merged some stuff
+**\<fluffypony>** moneromooo: anything in particular you want to highlight?
+**\<moneromooo>** Ah, whether to enable them for v7 or v8 on mainnet.
+**\<fluffypony>** that's the next point
+**\<fluffypony>** I meant anything in 2. you want to highlight :)
+**\<moneromooo>** Not in particular, no.
+**\<HUCK45>** Hey all, I just saw that awesome project recently and a question came to my mind- why there isn’t any option for GPU mining instead of CPU? Browsers these days allow that, by webgl for example (depending on the user settings, but on default it uses gpu)
+**\<fluffypony>** HUCK45: we're in a meeting - feel free to take that to #monero
+**\<rehrar>** HUCK45 we're in a dev meeting right now. :) This'll have to wait.
+**\<suraeNoether>** as far as MRL is concerned: the math on bulletproofs seems tight, but the best test for cryptography is time
+**\<fluffypony>** ok so I'll highlight a few PRs
+**\<fluffypony>** suraeNoether: not there yet
+**\<suraeNoether>** oh woops
+**\<fluffypony>** #2878 tightens up --offline mode by disabling DNS lookups
+**\<fluffypony>** #2877 refactors a bunch of p2p stuff
+**\<fluffypony>** and then the obvious bug fixes and improvements
+**\<fluffypony>** Bulletproofs on testnet is in #2883
+**\<fluffypony>** which brings us to 3. March hardfork items + code freeze
+**\<fluffypony>** so v7 already has sorted inputs
+**\<fluffypony>** moneromooo: do you want to explain that?
+**\<moneromooo>** Sorted inputs? Or bp ?
+**\<moneromooo>** I assume bp. They're just a smaller sized range proof system.
+**\<fluffypony>** sorted inputs
+**\<fluffypony>** I assume everyone knows what BP is
+**\<moneromooo>** Well, just... sort inputs by their key image. Nothing more.
+**\<iDunk>** Is it like unsorted inputs, but sorted ?
+**\<fluffypony>** iDunk: kinda
+**\<gingeropolous>** and why sort?
+**\<moneromooo>** Kinda :)
+**\<fluffypony>** gingeropolous: that's the big question
+**\<iDunk>** Cool :)
+**\<gingeropolous>** :)
+**\<fluffypony>** it's to prevent metadata leaking
+**\<fluffypony>** eg. the specific wallet used for a tx
+**\<moneromooo>** To avoid broken implementations leak stuff. It'd be better for outputs (ie, always put change last, etc), but unfortunately it doesn't work for outputs as the keys depend on their index.
+**\<moneromooo>** It has become hairy after subaddresses unfortunately, at least for the small benefit.
+**\<luigi1111w>** which?
+**\<moneromooo>** What is the question ?
+**\<luigi1111w>** what is "it"
+**\<fluffypony>** ordering outputs
+**\<moneromooo>** inputs.
+**\<luigi1111w>** subaddress or multisig?
+**\<moneromooo>** I'll rephrase:
+**\<moneromooo>** The input sorting code has become hairy after subaddresses unfortunately, at least for the small benefit.
+**\<luigi1111w>** yes that was clear, just not why
+**\<luigi1111w>** well was clear after \<moneromooo> inputs.
+**\<moneromooo>** Because the sorting was internal to construct\_tx before, now it's changed in the caller as well.
+**\<luigi1111w>** ok
+**\<moneromooo>** So that means you have to order selected\_transfers too, and possible something else, can't recall exactly.
+**\<moneromooo>** Anyway, it's just minutiae particular to our wallet code.
+**\<luigi1111w>** btw, change being last doesn't leak metadata
+**\<moneromooo>** It doesn't leak that change is that ?
+**\<moneromooo>** It doesn't leak that change is last ?
+**\<luigi1111w>** right
+**\<luigi1111w>** or what wallet was used
+**\<moneromooo>** OK, it leaks that change is more likely to be last than otherwise.
+**\<luigi1111w>** is it?
+**\<luigi1111w>** what if a popular wallet puts it first
+**\<moneromooo>** x+epsilon > x, even if epsilon is very small.
+**\<moneromooo>** (assuming epsilon is positive)
+**\<fluffypony>** luigi1111w: the onus is on wallets to follow the pattern
+**\<luigi1111w>** what pattern
+**\<luigi1111w>** why is there a pattern
+**\<moneromooo>** I'm lost here, I'll wait.
+**\<luigi1111w>** me too :)
+**\<moneromooo>** Maybe ask your question again, rephrased :)
+**\<pigeons>** I guess if there is an intentional pattern, there won't be several accidental identifying ones
+**\<rbrunner>** Fingerprinting wallets?
+**\<luigi1111w>** my point is chnage isn't a fingerprinting pattern for wallets
+**\<luigi1111w>** well my new point, whatever
+**\<luigi1111w>** anyway it doesn't really matter as we're not doing it anyway
+**\<fluffypony>** ok let's talk about Bulletproofs then
+**\<fluffypony>** suraeNoether: your turn :)
+**\<suraeNoether>** whelp, i pretty much had my piece in terms of bulletproofs: there isn't a research-oriented approach to answer if they are ready for implementation.
+**\<suraeNoether>** the best test for crypto is use and time.
+**\<suraeNoether>** the math has been reviewed, looks tight. it may feel like it's being put into production too soon, but...
+**\<suraeNoether>** any time we implement something new, we take some risks in that regard
+**\<suraeNoether>** it looks to me like a no-brainer drop-in replacement for our current range proofs, and to sarang it seems fine. the coding is done.
+**\<msvb-mob>** suraeNoether: Is there a way to merge new features on testnet only?
+**\<msvb-mob>** Maybe a risk reduction strategy I mean?
+**\<suraeNoether>** afaik BP is already on testnet as of ... today?
+**\<moneromooo>** As of a week back or so.
+**\<suraeNoether>** ah there you go
+**\<msvb-mob>** So we have at least that granularity, okay.
+**\<luigi1111w>** I'm going through the code and have some questions
+**\<suraeNoether>** yeah, i mean
+**\<suraeNoether>** luigi1111w: sarang will be able to answer them tomorrow afaik.
+**\<rehrar>** Is the chance of finding meaningful vulnerabilities that much greater if we extend it out to September hard fork? Like, would the extra six months be an adequate amount of time if it was determined that the three months between now and March hardfork wasn't sufficient?
+**\<suraeNoether>** \^ this is actually sort of the tough spot we find ourselves in
+**\<suraeNoether>** thing is, there isn't a real monetary incentive to attack something like BP while its on testnet
+**\<luigi1111w>** attacking it on mainnet is catastrophic, however
+**\<suraeNoether>** yep
+**\<suraeNoether>** its like designing a new parachute
+**\<rbrunner>** Well, we could put bounties for Testnet attacks, no?
+**\<luigi1111w>** meh
+**\<rehrar>** It's simple. We make testnetcoin a 3B dollar project.
+**\<fluffypony>** sure, but then we shouldn't ever deploy anything
+**\<fluffypony>** :-P
+**\<fluffypony>** LOL rehrar
+**\<suraeNoether>** lol
+**\<suraeNoether>** eventually someone has to strap it onto their own backs and jump
+**\<suraeNoether>** is what i mean
+**\<fluffypony>** yes
+**\<fluffypony>** so here's my thinking
+**\<luigi1111w>** the people that could review and attack are pretty small in number
+**\<fluffypony>** we code freeze via a 0.12 branch in the next 2-ish weeks
+**\<fluffypony>** we include BP for the March HF
+**\<fluffypony>** we release test bins in Jan
+**\<fluffypony>** we re-measure our confidence towards the end of Jan / beginning of Feb
+**\<fluffypony>** if we're not happy with it we change it to v8
+**\<fluffypony>** or the opposite - put it in v8 and move it to v7 towards the end of Jan if we're confident
+**\<luigi1111w>** much more comfortable with the latter
+**\<luigi1111w>** though there's plenty of support for delaying v7 as well
+**\<rehrar>** I think delaying v7 by a couple months would be well worth it?
+**\<rehrar>** and even if the next fork is still held to September, we will still have the multi-input BP to merge, which is exciting, no?
+**\<fluffypony>** I don't think we should move fork dates
+**\<rehrar>** or were both single and multi output BPs being discussed right now?
+**\<moneromooo>** Single only.
+**\<fluffypony>** it's becoming increasingly difficult, and sticking to the predictable fork schedule is advantageous for exchanges, merchants, and pools
+**\<fluffypony>** (emergency hard forks aside)
+**\<moneromooo>** I'm reasonably sure most don't know in advance when the fork is supposed to be anyway.
+**\<luigi1111w>** ^^
+**\<rehrar>** other loser coins: "oh btw mister exchange, we're forking in like two weeks, please update software"
+**\<fluffypony>** moneromooo: they're starting to know
+**\<dEBRUYNE>** As long as they are notified well in advance I don't see a problem with pushing it back 1-2 months
+**\<dEBRUYNE>** Like moneromooo says, most probably don't even know we have one scheduled for march
+**\<fluffypony>** pushing it back by 1-2 months isn't enough time
+**\<luigi1111w>** it might be
+**\<luigi1111w>** although
+**\<fluffypony>** imho we're either happy with March or we need 6 additional months of testing
+**\<moneromooo>** How about 12 ?
+**\<rehrar>** It may be that in the future FP you might be right, but I think we're still small enough that we can pull a stunt like this without too many consequences
+**\<fluffypony>** moneromooo: we might need that, if our confidence level is low
+**\<moneromooo>** The confidence will stay low until 3 months before the fork, when people will start looking.
+**\<moneromooo>** Before 3 months, (almost) nobody will look.
+**\<suraeNoether>** if we give ourselves 6 months of testing for BPs
+**\<suraeNoether>** i'll tell you what'll happen
+**\<fluffypony>** lol
+**\<suraeNoether>** 5 months an 2 weeks will go by
+**\<fluffypony>** so then March it is?
+**\<moneromooo>** Now, if people did look for 6 months... then yes.
+**\<suraeNoether>** and then testing will begin
+**\<dEBRUYNE>** Pushing it back 6 months might perhaps result in it going down the priority list
+**\<moneromooo>** I'm ready to go for september if there is a good reason (ie, someone says they need the 6 months).
+**\<dEBRUYNE>** And then we just get the same # of months of review
+**\<fluffypony>** I'm happy with March, but I'm also open to having my mind changed
+**\<fluffypony>** I'm also reaching out to the paper authors to see if any of them are able to do an implementation review
+**\<moneromooo>** smooth thinks it's too early, for the record.
+**\<rbrunner>** Main argument?
+**\<moneromooo>** At 9 txes per block (monthly average now), I think BPs save ~ 2 GB per month.
+**\<dEBRUYNE>** I think you'll see more transactions once fees drop to an acceptable level though
+**\<dEBRUYNE>** So savings might be even more
+**\<Vespco>** March with aggressive promotion of testnet usage starting now. We can highlight the need on reddit and provide clear stack exchange instructions and .bins to attract more users
+**\<luigi1111w>** I don't think that helps
+**\<luigi1111w>** you need math and code people
+**\<luigi1111w>** we may have enough (not now, I mean within the next 3 months)
+**\<rehrar>** Ok, just so the discussion doesn't go on forever, and to summarize for anyone reading logs afterwards, there's three main camps here: 1. Launch BPs in March HF, 2. Launch BP's in September HF, 3. Delay March HF to something like a May HF and launch BPs then.
+**\<rehrar>** Of those three, I'd say 3 is reasonable
+**\<luigi1111w>** there are two other non-forking changes that people would like to see in a release too, subaddresses and multisig
+**\<luigi1111w>** former is in already
+**\<dEBRUYNE>** As the fork height isn't set yet, can't we reasses in 2 months?
+**\<luigi1111w>** latter "should" be (IMO) in the next release
+**\<dEBRUYNE>** And see if there has been adequate review
+**\<fluffypony>** luigi1111w: agreed
+**\<luigi1111w>** dEBRUYNE no we are trying to get releases out in reasonable time
+**\<luigi1111w>** ie, not the week before
+**\<moneromooo>** MS is going in soon. Just after I fix the core tests after last rebase :)
+**\<dEBRUYNE>** No I meant whether BP go in or not
+**\<dEBRUYNE>** \^ luigi1111w
+**\<Vespco>** Is GUI ready for multisig and subaaddresses?
+**\<dEBRUYNE>** Or is two months to late for that to decide?
+**\<luigi1111w>** yes
+**\<dEBRUYNE>** too\*
+**\<dEBRUYNE>** Ok
+**\<fluffypony>** dEBRUYNE: basically-final bins need to be out by Feb
+**\<fluffypony>** beginning-ish of Feb
+**\<luigi1111w>** by the time you decide and build the release you're at like one week
+**\<luigi1111w>** agree
+**\<dEBRUYNE>** But also, if we push back the fork 1-2 months, we have more time to release basically-final bins
+**\<luigi1111w>** well 2 months imo
+**\<luigi1111w>** so whenever in march
+**\<suraeNoether>** i think MRL's opinion is 2 1 3, to vote for a september hard fork. because if we are wrong, the cost is large. if we are correct, we save 12 G
+**\<suraeNoether>** grand scheme of things
+**\<luigi1111w>** in grand scheme you don't really save anything
+**\<dEBRUYNE>** If we don't include BP in March 2018, I suppose we can at least fix the fees :-P
+**\<luigi1111w>** since we "might as well" prune that data
+**\<luigi1111w>** later
+**\<suraeNoether>** luigi1111w: yeah, on a long enough time horizon
+**\<vtnerd>** prune the range proofs?
+**\<luigi1111w>** yes
+**\<fluffypony>** if we did 2, any opinions on reducing the base fee in the March HF? we can increase it again later if we need
+**\<vtnerd>** how would some future user verify inflation?
+**\<luigi1111w>** vtnerd if you desire to do that for your trust model, of course you don't prune
+**\<dEBRUYNE>** fluffypony: we need to tweak the penalty
+**\<vtnerd>** oh so this is like the bitcoin prune old blocks option
+**\<luigi1111w>** well you don't lose the hashability
+**\<suraeNoether>** fluffypony: I think dEBRUYNE may have thought about fee structures more than anyone else
+**\<fluffypony>** yes
+**\<luigi1111w>** JollyMort[m] :)
+**\<dEBRUYNE>** \^ would certainly beat me :P
+**\<suraeNoether>** fair
+**\<endogenic>** is it worth writing a paper on fee structure modeling etc?
+**\<luigi1111w>** longer term I think yes
+**\<luigi1111w>** but we certainly don't have time for march
+**\<dEBRUYNE>** Perhaps we could change the penalty exponent to \^3 instead of \^2
+**\<fluffypony>** suraeNoether: what would your comfort level change to if one or more of the paper's authors reviewed the implementation?
+**\<suraeNoether>** fluffypony: no, the implementation isn't the concern at all, in my mind at least
+**\<suraeNoether>** assuming it's passing unit tests
+**\<suraeNoether>** (which i think it is, iirc)
+**\<moneromooo>** It is.
+**\<dEBRUYNE>** What if the paper itself is "broken"? Only time will tell that I guess
+**\<suraeNoether>** there ya go. the question is whether or not someone clever can divide by zero and cause a big monero bang with bullet proofs .
+**\<suraeNoether>** dEBRUYNE: \^ exactly
+**\<suraeNoether>** the best test for crypto is time
+**\<rehrar>** will an aggressive 'test bps on testnet' campaign do anything?
+**\<luigi1111w>** no
+**\<suraeNoether>** i don't think so
+**\<suraeNoether>** if someone found something
+**\<rehrar>** so then that's points for March HF isn't it?
+**\<suraeNoether>** it would be worht more for them to wait until it was implemented than to report it
+**\<rbrunner>** I think with no high-value target to attack nobody will aim at BP
+**\<luigi1111w>** I disagree with suraeNoether and would like the implementation reviewed
+**\<rehrar>** if we gain little value for waiting, then we shouldn't wait
+**\<suraeNoether>** luigi1111w: I dind't say i dind't want the implementation reviewed. fluffypony asked me if such a review would make me more comfortable with a March HF
+**\<luigi1111w>** then we still disagree
+**\<luigi1111w>** so it's fine :)
+**\<suraeNoether>** heh, okay. well at least we can agree that we both want the implementation reviewed one way or another
+**\<moneromooo>** (thanks stoffu btw, who did review it well)
+**\<suraeNoether>** stoffu is a silent hero
+**\<rehrar>** Meeting is coming to a close. Not necessarily to decide right now, but just to see where everyone is, can we have everyone that was in this conversation verbally state whether they prefer March or September for BPs?
+**\<fluffypony>** in terms of someone finding an issue in the math itself, I don't think that 6 months is a macro-enough timescale for that
+**\<fluffypony>** my preference would be March, pending peer review, or September + fee reduction failing that
+**\<rbrunner>** March: Only with BP live on mainnet you would ever get bright and bad people interested to break something
+**\<suraeNoether>** i have the reversed preference as fluffypony, plus i would like the authors to review the implementation in either case
+**\<suraeNoether>** i think sarang has the same preference as fluffypony though
+**\<vtnerd>** uh, so before meeting adjourns I'd like to prod https://github.com/monero-project/supercop/pull/1
+**\<moneromooo>** What we'd need is for people who may review it to tell is now when they would, and how much time they'd need... Not gonna happen most likely.
+**\<vtnerd>** unedited supercop code is all that is now
+**\<luigi1111w>** cool
+**\<pigeons>** pre-borromean ringct signature issue was found by 3rd party (and/after the monero team), so people do look at non-mainnet code. and also that incident shows how short timelines are scary
+**\<endogenic>** \^
+**\<fluffypony>** also msvb-mob wanted to say a couple of things about the HW wallet
+**\<suraeNoether>** pigeons: that's an extremely good point
+**\<msvb-mob>** Hardware team achieved a breakthrough today in manipulating the MCU factory bootloader without programming.
+**\<msvb-mob>** That means that future firmware developers can flash boards using DFU over USB.
+**\<msvb-mob>** DFU == Device Firmware Upgrade
+**\<fluffypony>** pigeons: good point
+**\<fluffypony>** msvb-mob: nice one!
+**\<msvb-mob>** In the near future we will ask for in depth advice from core development and MRL to confirm our design is on track.
+**\<msvb-mob>** Any questions? You can ask about 34C3 assembly as well.
+**\<moneromooo>** There is a factory bootloader ? As in, code you did not write ?
+**\<msvb-mob>** moneromooo: Yes, most hardware manufacturers (Nordic, STM, Maxim, TI) supply a default bootloader you can't get rid of.
+**\<msvb-mob>** And when they're nice, it's full of USB and DFU.
+**\<luigi1111w>** pigeons thanks, and that memory pushes me towards the wait camp
+**\<moneromooo>** That sounds like a great idea :/
+**\<msvb-mob>** Next topic.
+**\<luigi1111w>** meeting is basically over afaik
+**\<rbrunner>** Please don't forget the GUI wallet Windows installer and put it into service sometime after busy Christmas. I have a PR waiting that gives the last polish to the installer script, and after that it's really, really ready
+**\<fluffypony>** yep that's it
+**\<fluffypony>** one last thing
+**\<fluffypony>** next meeting would be Dec 31
+**\<fluffypony>** but I don't think anyone wants that
+**\<fluffypony>** so push out to Jan 14?
+**\<rehrar>** Monero New Year party?
+**\<msvb-mob>** If we do one week later, we synced again with community meetings.
+**\<luigi1111w>** is that what we want?
+**\<luigi1111w>** ok with both
+**\<rehrar>** you guys don't go anyways :P
+**\<luigi1111w>** and by ok I mean as not ok as normal
+**\<fluffypony>** msvb-mob: I'd prefer us unsynced, otherwise it's just too much on a weekend
+**\<fluffypony>** wife will murder me :-P
+**\<moneromooo>** Technically, that's still synced, but out of phase...
+**\* moneromooo** steps back
+**\<msvb-mob>** Nobody is protesting 14 Jan. I'm not opinionated, just wanted to mention the sync aspect.
+**\<fluffypony>** lol moneromooo
+**\<rehrar>** Ok 14 Jan it is
\ No newline at end of file
diff --git a/_posts/2017-12-23-logs-for-the-Community-meeting-held-on-2017-12-23.md b/_posts/2017-12-23-logs-for-the-Community-meeting-held-on-2017-12-23.md
new file mode 100644
index 0000000000000000000000000000000000000000..9cc0df309339b91bfaa6541363fb4508f3172276
--- /dev/null
+++ b/_posts/2017-12-23-logs-for-the-Community-meeting-held-on-2017-12-23.md
@@ -0,0 +1,147 @@
+---
+layout: post
+title: Logs for the Community Meeting Held on 2017-12-23
+summary: Community highlights, Forum Funding System updates, RFC-HWALLET-1, Malware Response Workgroup, Forum Funding System donor flairs, and miscellaneous
+tags: [community, crypto]
+author: dEBRUYNE / fluffypony
+---
+
+# Logs
+
+**\<sgp>** 0. Introduction
+**\<sgp>** We would like to welcome everyone to this Monero Community Meeting!
+**\<sgp>** Link to agenda on GitHub: https://github.com/monero-project/meta/issues/148
+**\<sgp>** Monero Community meetings are a discussion place for anything going on in the Monero Community. We use meetings to encourage the community to share ideas and provide support.
+**\<sgp>** 1. Greetings
+**\<rehrar>** Ye
+**\<ErCiccione>** hi ya
+**\<rehrar>** Perfect. Let's continue.
+**\<sgp>** 2. Community highlights
+**\<sgp>** For a great weekly summary, please read the Monero Observer: http://monero-observer.com/
+**\<sgp>** 3. FFS updates
+**\<sgp>** There are several FFS updates.
+**\<sgp>** a. RFC-HWALLET-1 project progress
+**\<sgp>** @msvb-lab @msvb-mob any updates?
+**\<ErCiccione>** i have some from the localization group
+**\<sgp>** Ok great, let's get to that in one sec
+**\<sgp>** Ok, well we can cover these if anyone from the hardware wallet team is present
+**\<sgp>** Their Taiga page is here: https://taiga.getmonero.org/project/michael-rfc-hwallet-1-implementation/
+**\<sgp>** b. localization
+**\<sgp>** Go ahead, ErCiccione
+**\<ErCiccione>** ok, thanks sgp
+**\<ErCiccione>** Nothing special btw, we are almost completely set with the structure of the localization workgroup. rehrar made a pr for making the website multilingual and we are getting ready for that, since it's gonna be my main concern for at least the next month
+**\<ErCiccione>** we now have guides for translating: GUI wallet, meetup kit, kovri, the future website (still wip) and soon a graphic tutorial for Git. And i'm really looking forward to that
+**\<sgp>** Anything else you would like to add?
+**\<ErCiccione>** we got many translations for the meetup kit and i'm happy to say we have almost completely filled the page containing the translations of the gui :)
+**\<ErCiccione>** just contacts:
+**\<ErCiccione>** any update can be found on our taiga project: https://taiga.getmonero.org/project/erciccione-monero-localization/ and #monero-translations is our support channel
+**\<ErCiccione>** if anybody have any question, i'm happy to answer
+**\<ErCiccione>** that's it from me
+**\<sgp>** Suppose I wanted to add language 'x'. How much time would it typically take one person to translate the website, and how much time for the GUI?
+**\<sgp>** I know it's a broad question; I'm just looking for very rough numbers
+**\<ErCiccione>** ading a language for the GUI is quite straightforward but depends how much a contributor knows about git. If he/she has a good knowledge, usually can be ready to get merged within the same day (of course, reviews aside). But usually a PR is ready in a couple of days, if the contributor needs support
+**\<ErCiccione>** about the website
+**\<ErCiccione>** i tested it and looks like quite easy, the main "issue" is that there are a lot of pages to translate, so i'm working on a workflow that will give priority to the most important pages
+**\<sgp>** Thanks
+**\<sgp>** Does anyone else have a FFS update?
+**\<ErCiccione>** that also shouldn't take long, i usually review and test the same day or the one after
+**\<sgp>** 4. Malware Response Workgroup
+**\<sgp>** I have taken on the initiative of organizing the Malware Response Workgroup. If you are interested, please go to #monero-malware-respon
+**\<sgp>** I have updated the Taiga wiki project with several help guides for web mining, system mining, and ransomware https://taiga.getmonero.org/project/sgp-monero-malware-response-workgroup/wiki/home
+**\<sgp>** These are still drafts, but it shows the general idea
+**\<sgp>** The goals of this project are to help those with compromised machines and to show others that many Monero community members discourage and help limit malware.
+**\<sgp>** We can use volunteers now to help review these documents, and later to help people
+**\<sgp>** Any questions?
+**\<ErCiccione>** looks quite today. (pinging: @serhack @needmoney90 dEBRUYNE gingeropulous)
+**\<ErCiccione>** (@pablonero mattcode xmrscott)
+**\<sgp>** It's close to a major holiday
+**\<sgp>** Well, that's all for the formal part of the meeting
+**\<sgp>** 5. Open ideas time
+**\<sgp>** It’s open ideas time! Feel free to propose your ideas to this discussion group, and feel free to comment on others’ ideas. If you disagree with the idea, please reply with constructive criticism. Thank you!
+**\<ErCiccione>** i do have one
+**\<netg>** u need to really build and develope the site with real users and their feedback
+**\<netg>** very important
+**\<netg>** we cant think like a non technical person who is infected
+**\<netg>** and what would help him
+**\<sgp>** @netg let's have erciccione go first, then we can discuss the website further
+**\<netg>** ok sorry
+**\<sgp>** no worries!
+**\<ErCiccione>** ok
+**\<ErCiccione>** basically i had an idea to increase the level of involvement of the community about participating in ffs funding, this using reddit's flairs (rehrar told him he and dEBRUYNE were thinking about something similar)
+**\<ErCiccione>** basically more FFS's you contribute to, higher is the "rank" of the flair. This is the system of ranking i had in mind:
+**\<ErCiccione>** 1 : Rookie Supporter
+**\<ErCiccione>** 2-3 : Supporter
+**\<ErCiccione>** 4-5-6 : Coach
+**\<ErCiccione>** 7-8-9 : Barolo Provider
+**\<ErCiccione>** 10+ : Maecenas (or Patron?)
+**\<ErCiccione>** The point here is that the amount donated doesn't matter, to get the best shiny flair the user is pushed to donate to many FFS, but according to his/her possibilities.
+**\<sgp>** I like this idea
+**\<sgp>** @ErCiccione there you have it, 100% community approval :p
+**\<rehrar>** Ye
+**\<sgp>** It may be a little difficult to implement though since you will need to have some way for people to say they donated and verify that
+**\<ErCiccione>** I never playied with reddit's flairs, i'd like to try to implement this myself if you guys agree. lol thanks community!
+**\<sgp>** tx IDs would probably be enough for something small like this
+**\<rehrar>** 1. Little tiny baby supporter 2. Toddler support 3. We note that you can be a beautiful being one day here 4. Puberty supporter 5. Young and strong (but not for long) supporter etc.
+**\<ErCiccione>** Yes, i guess it would. or we can enforce the use of the same nick you use on reddit for the forum, if you want the flair
+**\<rehrar>** Spreadsheet would be necessary.
+**\<sgp>** Yeah, just make something cool/cute and go with it
+**\<sgp>** Donate $1m to a single project -> "itsy bitsy supporter" :D
+**\<sgp>** Anything else you want to discuss about this idea?
+**\<ErCiccione>** lol, no should be enough.
+**\<sgp>** Ok @netg
+**\<sgp>** I think everyone agrees Monero should be more accessible
+**\<netg>** i dont know
+**\<netg>** kali linux or tor project
+**\<netg>** they lead their space 100% but they arent to super accessible
+**\<netg>** for me it would be ok if monereo just alive and healthy
+**\<rehrar>** Netg you talking about official website?
+**\<netg>** dont need to be mainstream coin , who has to offer to m mainstream
+**\<netg>** no, now about the project
+**\<netg>** i mean its the same question
+**\<netg>** if u go for the general public and usage of monero by non technical people
+**\<netg>** you have to do alot of work in your malware group
+**\<netg>** and before that in educating potential users and the community
+**\<netg>** its a question where the project is gonna heading to
+**\<sgp>** Have you looked at the meetup kit materials? Do you think those are good material for new users?
+**\<netg>** mainstream usage or usage by a educated, sophisticated crowd
+**\<sgp>** I think both
+**\<rehrar>** Monero has to be for everyone. There is no other option.
+**\<sgp>** Different wallets can tailor expereinces to different target audiences
+**\<rehrar>** Otherwise it simply becomes another tool for the rich, who historically are the educated.
+**\<sgp>** Or only a tool for the malicious :(
+**\<rehrar>** Who historically has been everybody. :P
+**\<sgp>** \@netg does that answer your question?
+**\<netg>** i mean, great approach from idealistic kind of view
+**\<rehrar>** Yes, netg, I agree a dichotomy exists between the sophisticated user and the non-technical, normal person. This will denote two different kinds of education, as you have alluded to.
+**\<netg>** it will be ALOT of work
+**\<rehrar>** I agree. It will be a lot of work. And it is work well invested in my opinion. And should nobody else want to do this work, I will. :)
+**\<rehrar>** But there are more. ;) No worries.
+**\<rehrar>** Bitcoin started out as something quite idealistic too.
+**\<netg>** yeah fuck , i mean monero historically always choosed the best approach and design
+**\<netg>** even if it was alot of work
+**\<netg>** maybe we should stay in that tradition
+**\<rehrar>** I see Monero as carrying on the touch Bitcoin dropped.
+**\<ErCiccione>** i agree it will worth it, even just for the public image of Monero
+**\<netg>** rehrar: obvious, thats the reason why alot of old school bitcoin supporters switched to monero , instantly after reading about it
+**\<sgp>** Any other questions?
+**\<netg>** When will Monero been moon? :)
+**\<netg>** \-en
+**\<rehrar>** Yesterday
+**\<sgp>** Hasn't it already? :)
+**\<rehrar>** You missed it. Sorry. :(
+**\<netg>** "cant tell you, the moons privacy needs to be respected"
+**\<sgp>** 6. Confirm next meeting date/time
+**\<sgp>** The next Monero Coffee Chat will be two weeks from today on 6 January. We need to decide when to have the next meeting. I suggest moving the next meeting to 13 January and then continuing biweekly from there to avoid another conflict in February.
+**\<rehrar>** Devs want to keep dev and community meetings on different weeks.
+**\<sgp>** Hmm, not sure what to do then
+**\<rehrar>** What conflict is in Feb?@
+**\<ErCiccione>** the week after or on a different day of the week
+**\<sgp>** If we stay with the current meeting schedule it will fall on the first Saturday of the month
+**\<sgp>** I suppose I could delay the Coffee Chat instead
+**\<rehrar>** Skip that one.
+**\<rehrar>** Or do that.
+**\<ErCiccione>** maybe delay it not skip
+**\<sgp>** Ok, let's plan for the next meeting to be two weeks from today on 6 January at 17:00 UTC
+**\<ErCiccione>** agreed
+**\<sgp>** 7. Conclusion
+**\<sgp>** That’s all! Thanks for attending this Monero Community meeting, and we hope to see you on /r/MoneroCommunity and #monero-community. Take care, and know that change starts with YOU.
\ No newline at end of file
diff --git a/_posts/2018-01-05-logs-for-the-Hardware-meeting-held-on-2018-01-05.md b/_posts/2018-01-05-logs-for-the-Hardware-meeting-held-on-2018-01-05.md
new file mode 100644
index 0000000000000000000000000000000000000000..3ec2355693a3d5429c582c30ccbe0c301e8b221f
--- /dev/null
+++ b/_posts/2018-01-05-logs-for-the-Hardware-meeting-held-on-2018-01-05.md
@@ -0,0 +1,382 @@
+---
+layout: post
+title: Logs for the Hardware Meeting Held on 2018-01-05
+summary: Poll conducted, Reddit summaries, status report(s), conclusion of name search, highlights of 34C3 in Leipzig, etherpads for groups, test plan discussion, recent firmware & FPGA research, mechanical engineering, recent logo contributions, and miscellaneous
+tags: [community, crypto]
+author: dEBRUYNE / fluffypony
+---
+
+# Logs
+
+**\<rehrar>** Hellooooo hardware peeps!
+**\<luigi1111w>** I thought next friday
+**\<msvb-lab>** luigi1111w: Yes, right now for an hour.
+**\<luigi1111w>** ok
+**\<nioc>** today and next Fri for software
+**\<msvb-lab>** General hw team meeting, but Friday may or may not (to be decided) be s focus seesion on firmware.
+**\<rehrar>** So we got a lot of ground to cover today, so let's hop into it.
+**\<msvb-lab>** https://taiga.getmonero.org/project/michael-rfc-hwallet-1-implementation/wiki/meet/
+**\<msvb-lab>** Is the agenda.
+**\<rehrar>** So from my understanding, because we'll be moving quite quickly, we'll have to not spend tons of time on discussion per topic
+**\<rehrar>** We can either talk after the meeting (if we want to continue conversation)
+**\<msvb-lab>** rehrar: Yes, that's right. In fact, #1 is already done.
+**\<rehrar>** or perhaps utilize another channel to have side conversations about stuff
+**\<msvb-lab>** And #2 is cancelled.
+**\<msvb-lab>** At the 30 minute mark we break into subgroups, that will be clear as we get to the point.
+**\<rehrar>** Well then, we're already scurrying along.
+**\<rehrar>** The third item on the agenda is the poll that is conducted?
+**\<i-a>** hello!
+**\<rehrar>** Are we talking about how it was conducted, or...? :)
+**\<msvb-lab>** Just that the poll is always conducted on doodle and we have a choice when to hold meetings.
+**\<msvb-lab>** This one there are at least three that can't make it due to time zone differences, too bad.
+**\<i-a>** luigi1111w: today its more about logo, enclosure and a lot of different stuff. Meeting about firmware is lanned to be next friday.
+**\<rehrar>** That's sad, indeed. Is there nothing that can be done?
+**\<i-a>** \*planned
+**\<luigi1111w>** ahh, ok
+**\<rehrar>** Maybe a terrible idea, but what if two meetings were held covering the same agenda?
+**\<msvb-lab>** We can try to build friendships with those folks in other timezones and keep them informed.
+**\<luigi1111w>** I will just watch then
+**\<rehrar>** One that is good for one set of timezones, and then next 12 hours later
+**\<rehrar>** Alright, either way, we can discuss that later. Moving on!
+**\<kamminke>** So, which item on the long agenda we discuss now first?
+**\<rehrar>** we're at 4. Reddit summaries
+**\<rehrar>** I was asked to go ahead and look through the Reddit threads that talk about Hardware
+**\<rehrar>** the provided links are just two examples, although they are some of the bigger ones
+**\<rehrar>** to give a brief summary: there is still a lot of people not understanding that the end result of this hardware project will not necessarily be this workgroup selling hardware wallets
+**\<rehrar>** Perhaps we can discuss at a later time whether (once firmware is complete) this workgroup would like to take on the task of making (funded via FFS of course) a number of hardware wallets for the community
+**\<m2049r[m]>** what are they understanding?
+**\<rehrar>** They're asking about pre-orders, how to order, etc.
+**\<rehrar>** They understand that at the end of this project will, the end result is a deliverable hardware wallet product
+**\<sebgus>** rehrar: Sounds like a good idea. I could assist in this task (hardware assembly).
+**\<dEBRUYNE>** There's a huge business opportunity though if you can actually deliver them for a decent price
+**\<sebgus>** But maybe we want something on a more mass-produced scale, msvb?
+**\<rehrar>** second thing I gleaned: tons of people want hardware wallet support yesterday. Comes as no surprise, but yeah. Thought I'd throw that in there.
+**\<rehrar>** Thirdly: People are very supportive and impressed with the progress and work of this workgroup
+**\<rehrar>** so congratulations are in order there
+**\<rehrar>** and lastly: the obvious comparisons that occur between the goals of this workgroup and ledger/trezor come up very very often
+**\<rehrar>** By reading the Reddit threads, this is the general pulse of how the community is viewing hardware development and this workgroup
+**\<anhdres>** I suppose we'll need to have as good as a mertic of how many wallets could be sold before thinking about mass producing
+**\<cslashm>** is there any sheet comparison of HW wallets projects?
+**\<kamminke>** And, IMHO we have to become more secure as competitors.
+**\<m2049r[m]>** (that & having a product which does something)
+**\<rehrar>** it's hard to gauge without getting preorders, which would require an ahead-of-time commitment to such a thing from a group or individual
+**\<rehrar>** It also does NOT have to be the job of this workgroup to produce and ship them
+**\<rehrar>** there can be another workgroup tasked with that
+**\<anhdres>** rehrar, yeah, a la kickstarter
+**\<i-a>** (please dont think too much about selling stuff which doesnt exist yet)
+**\<rehrar>** leaving this workgroup to continue to innovate and push forward in the hardware field
+**\<rehrar>** \^ a great point
+**\<anhdres>** agree
+**\<serhack>** +1
+**\<rehrar>** let's finish the tasks at hand first, then further discussions could commence
+**\<msvb-lab>** Sorry.
+**\<rehrar>** moving on
+**\<rehrar>** 5. Status reports
+**\<dEBRUYNE>** cslashm: There's Trezor, this group, and Ledger (you). Or didn't you mean it like that?
+**\<rehrar>** first up, board additions
+**\<msvb-lab>** We're still on track with two main editions.
+**\<msvb-lab>** A developer (D) edition, larger and more complex good for devs.
+**\<msvb-lab>** A consumer (C) edition, with excellent aesthetics and easy to use.
+**\<rehrar>** we can continue conversations on previous points in #monero-hardware-aside. It'll just be used temporarily for this meeting
+**\<msvb-lab>** Secure too, ahem.
+**\<cslashm>** dEBRUYNE: juste ask if what the differenciator of each project is written down
+**\<msvb-lab>** Is that okay with everyone else?
+**\<eruheran>** dEBRUYNE, cslashm there is also KeepKey
+**\<rehrar>** (I urge cslashm and dEBRUYNE to continue there :) )
+**\<msvb-lab>** And Digital Bitbox, my favourite.
+**\<msvb-lab>** The dividend results were namely that if folks were willing to give a mailing address, they got a play toy for the holiday season.
+**\<sebgus>** msvb: Sounds reasonable with two versions.
+**\<sebgus>** editions\*
+**\<msvb-lab>** Regarding secure elements, we've had a mix of failure and success with diverse vendors.
+**\<msvb-lab>** Most promising right now is ATECC608A, CEC1702, and nRF42850.
+**\<msvb-lab>** Gemalto and ST Micro are more or less out, and most other vendors have no offering.
+**\<msvb-lab>** Zylinkx sells a FPGA for 120 EUR.
+**\<msvb-lab>** Any questions about secure elements, enclaves, or hardware security modules?
+**\<tat>** hello i am a bit late to the meeting, my name is Morris and i meet Michael on the 34C3,
+**\<msvb-lab>** tat: Super that you made it, thanks for tuning in.
+**\<msvb-lab>** anhdres: Would you please announce our new repository/project name?
+**\<tat>** I have read up during the last days on ledger history and i have a idea about a secure element that would work without NDA and is very cheap to come by.
+**\<m2049r[m]>** yes - i doubt the need for a secure element
+**\<jbdatko>** Hi, I'm Josh, new to this group. I've worked with the ATECC series a lot and recently the Xilinx zynq so I can answer questions on those secure element options if y'all have any
+**\<m2049r[m]>** unless mabye it does curve25519 in hardware
+**\<anhdres>** msvb-lab, sure?
+**\<anhdres>** nah, you do it
+**\<msvb-lab>** jbdatko: So this is quite an honour. Josh is the creator (almost 100%) of our Breakneck board, the developer edition.
+**\<msvb-lab>** jbdatko: Welcome.
+**\<i-a>** jbdatko: hello, nice to see you here!
+**\* jbdatko** waves
+**\<kamminke>** Still the same questions - does the secure elements support the right curve for signing?
+**\<msvb-lab>** anhdres: Okay you nerd. I'll tell the world about our new mistake, the name for our sekura rejected repository is...
+**\<msvb-lab>** kamminke: Yes, they have the curves ed25519.
+**\<msvb-lab>** ...drummrolllll.
+**\<rehrar>** YAY, what a name!
+**\<rehrar>** oh
+**\<msvb-lab>** The name is drumroll.
+**\<rehrar>** I thought: kamminke: Yes, they have the curves ed25519. was it
+**\<i-a>** m2049r[m]: I am also skeptical about secure elements, but if we make hw wallet secure by design, we can still enhance it by adding a storage for keys (and store them encrypted there)
+**\* sarang** locates a drum
+**\<msvb-lab>** KASTRATELO!
+**\<msvb-lab>** Just joking. It's Katelo.
+**\<i-a>** :D
+**\<anhdres>** jaja
+**\<rehrar>** Kastelo :P
+**\<anhdres>** Kastelo
+**\<msvb-lab>** Crap, I mean Kastelo. rehrar yes.
+**\<rehrar>** this is why you don't let msvb-lab announce these things
+**\<msvb-lab>** Well that went over quite clearly.
+**\<tat>** My idea was a programmable smartcard that is embedded as a simcard within the wallet
+**\<m2049r[m]>** we can use any eeprom for that
+**\<serhack>** Kastratelo is a bad word in italy
+**\<rehrar>** Ok. Epic! luigi1111 and luigi1111w we would be thrilled if some changes to the Sekura repo could be made
+**\<cslashm>** About SE, you should consider the scope of HW and side channel attack. SE help for that
+**\<tat>** they are very secure, nxp states they use more then 4000 anty tempering technics in there curent generation of java smartcards
+**\<kamminke>** do you trust smartcards?
+**\<luigi1111w>** aren't we the same person
+**\<msvb-lab>** luigi1111w, yes you and the other luigi are the same person. Look in the mirror.
+**\<sarang>** I always figured luigi1111 was some kind of secret society
+**\<rehrar>** https://github.com/monero-project/meta/issues/136 is a good starting point
+**\<i-a>** The wallet must be secure by design, please lets use secure elements only to enhance allready secure design.
+**\<rehrar>** with the addition of changing the repo name to "Kastelo"
+**\<rehrar>** alright, moving on.
+**\<rehrar>** Again, conversation from older points can continue in #monero-hardware-aside
+**\<rehrar>** 7. Highlights of 34C3 in Leipzig
+**\<m2049r[m]>** an attack is only possible if you can make the device use your key - if you can do that ONCE, then you transfer the funds away and dont care about the key. no?
+**\<msvb-lab>** i-a: Good point. jbdatko Josh do you believe that we can make a hardware wallet that's secure by design in that even when running a roque firmware the secrets remain safe?
+**\<msvb-lab>** Ups, Josh not der.
+**\<msvb-lab>** Okay, who wants to give a 34C3 summary?
+**\<kamminke>** all algorithmen on CPUs you can easy attack with power analysis
+**\<jbdatko>** hmm, the ultimate question yes? ;) Secure elements (try) to keep the private key from leaking but unfortunately with rogue firmware you also have to worry about somebody using the key. Rephrased: you don't have to leak the key to lose money you just have leak control of the key
+**\<msvb-lab>** jbdatko: Interesting, and that's quite clear. So not the holy grail, yet possibly an instrument to use in securing.
+**\<jbdatko>** But combing user input with a KDF passhprase that unlocks the SE I think is the design pattern
+**\<cslashm>** Power Analysis is your enemi
+**\<i-a>** It is a tradeof, (1) having secure elements which could be accessible only through a binary blob uploaded in flash, or having code which could possibly be attacked by side channel. I am not sure how to handle this.
+**\<msvb-lab>** Does anyone want to give a summary about 34C3 in Leipzig?
+**\<tat>** jbdatko: make the user confirm every transaction in an way that can not be tempered with
+**\<cslashm>** I worked on cerfified product (ID)
+**\<msvb-lab>** rehrar: Let's skip 34C3, as I think most people don't know what it is.
+**\<rehrar>** sounds good
+**\<msvb-lab>** Really not that big a deal probably.
+**\<rehrar>** Well, next is Etherpads for the group
+**\<msvb-lab>** Yes, we're at #8 and half way through.
+**\<rehrar>** https://taiga.getmonero.org/project/michael-rfc-hwallet-1-implementation/wiki/meet
+**\<rehrar>** this is the agenda for the meeting if you missed it
+**\<anhdres>** I wish they released the videos from 34c3
+**\<anhdres>** they're taking ages
+**\<rehrar>** if you scroll down to item 8, you will see the different Etherpads set up for this group
+**\<msvb-lab>** Each of us now takes a moment and if we wish, we can devote part of the next half hour (like an extra open browser window) to one of the subgroups.
+**\<i-a>** 34c3 was incredibly good event, I have met many interesting people, I have given some boards and I am waiting for contributions! msvb-lab did a nice talk about hw wallet, also there was nice talk about monerujo android wallet, both should be online in a month.
+**\<rehrar>** They're topic specific, and just another way to communicate, talk, and exchange ideas
+**\<msvb-lab>** See the part after #8 Main project, QA test, Firmware...?
+**\<rehrar>** Choose your Etherpad, and start disucssion?
+**\<msvb-lab>** I'm going to click on Mechanics since I did meet more than a few interested in mechanical engineering.
+**\<msvb-lab>** rehrar: We continue here in parallel with Test plan I think. Do you think it will work?
+**\<rehrar>** *shrug* never tried it, but should be fun
+**\<msvb-lab>** In the right hand side chat of the etherpads, if you want to be named, click the top most 'people' button and add your name there.
+**\<i-a>** haha, how to make the crowd to disappear? show them etherpads:))
+**\<m2049r[m]>** what is the exact attack vector we are addressing with a secure element?
+**\<msvb-lab>** i-a: Yes, it seems this idea is either very good or very bad. No idea.
+**\<m2049r[m]>** i-a: btw. i did all you said - its still broken
+**\<msvb-lab>** Control over secrets is the attack vector.
+**\<m2049r[m]>** thats too vague for me. how?
+**\<i-a>** m2049r[m]: trying to PM you but i cannot, please could you try to pm me?
+**\<m2049r[m]>** someone has to have phsyical access to the device. then what?
+**\<msvb-lab>** m2049r[m]: Decapsulation is what I would attempt, it depends on many things.
+**\<i-a>** m2049r[m]: "You must log in with services to message this user"
+**\<kamminke>** We have to avoid, that someone, even with physical access to the hardware wallet, gets the key pair to sign transactions.
+**\<msvb-lab>** i-a: That usually means you haven't set up a password with chat.freenode.net.
+**\<rehrar>** i-a maybe you can try on the mattermost guys?
+**\<msvb-lab>** kamminke: That's right, according to Josh it's not enough to fool all attackers all the time, but it's certainly a goal for us to block access to stealing the actual secret away from silicon.
+**\<m2049r[m]>** decapsulation will not help you if the key is password-encoded
+**\<msvb-lab>** Seems mechanical engineers and quality assurance folks are not the chatting types?
+**\<msvb-lab>** Those etherpads are blowing crickets.
+**\<m2049r[m]>** i-a: come to mattermost
+**\<i-a>** m2049r[m]: I never did it, i am trying it now.
+**\<sarang>** How would the key be encrypted?
+**\<msvb-lab>** sarang: Symetric cypher.
+**\<msvb-lab>** I'm not sure if that's how other wallets do it, but that's how SSH does for example.
+**\<msvb-lab>** Wallets alway have these nasty mnemonic thingies, so that throws a curve.
+**\<msvb-lab>** But encrypting a key is no problem. Not that I agree it allows us to avoid a secure element.
+**\<jbdatko>** When in doubt, use libsodium (NaCl) based stuff -- there is a KDF and a PKDF function there that could be ported to bare-metal C (I think it's close already just some linux-y calls)
+**\<msvb-lab>** By that theory we could use a magnetic hard drive and be safe enough.
+**\<sarang>** If you want to avoid someone lifting the encrypted blob and hammering away at it, a simple symmetric cipher without a KDF would be very bad
+**\<sarang>** jbdatko: yes, a KDF is essential
+**\<msvb-lab>** jbdatko: To encrypt a ed25519 secret, we could use a ATECC608A because it has PKDF right?
+**\<jbdatko>** so the 608A does have HKDF so you could use it to create a key tree of sorts
+**\<msvb-lab>** sarang: It's golden when monero-hardware is teaming MRL folks a lesson. Har har har.
+**\<sarang>** PBKDF2 is useful for low-memory settings
+**\<sarang>** ?
+**\<jbdatko>** The biggest issue I would think for this project with the 608a, while I like it, is that it's a NDA datasheet :/
+**\<msvb-lab>** sarang: It's possible the sec eng IC mix we get can do quite a bit with low mem and low power.
+**\<sarang>** msvb-lab: ha, nice try
+**\<msvb-lab>** We won't get lucky enough to use an easy I2C IC for ed25519, but we can use one of those for a number of other security games.
+**\<jbdatko>** PBKD2 I don't think would do well on an ARM M4. I don't think it's memory bound but it takes seconds on a i7. to get the same number of rounds it might take a very long time
+**\<msvb-lab>** I shamelessly copied Josh's concepts to our proj mgmt task 166:
+**\<jbdatko>** Although TREZOR does some kinda of PBKDF so I might be mistaken
+**\<msvb-lab>** https://taiga.getmonero.org/project/michael-rfc-hwallet-1-implementation/task/166/
+**\<kamminke>** I would even prefer asymmetric crypto for the keys, the host encrypt with the public key the key to store, but only the right wallet with his private key can open the stored keyring.
+**\<i-a>** m2049r[m]: https://docs.mattermost.com/install/install-debian-88.html this, really?
+**\<msvb-lab>** jbdatko: A second on key generation, derivation, or verification?
+**\<msvb-lab>** I would assume those are all very different benchmarks.
+**\<jbdatko>** PBKDF2 on high end processors takes seconds by design to derive the key from the passphrase
+**\<m2049r[m]>** i-a: no! this: mattermost.getmonero.org
+**\<sarang>** you can the number of rounds to take as long as you want based on estimated processing speeds
+**\<sarang>** \*you can tune
+**\<rehrar>** alright everyone. Settle down. Settle down. I know it's been a crazy meeting so far, but we got more to get through.
+**\<msvb-lab>** There's plenty of crypto going on in #monero-hardware-aside, for extended discussion about that.
+**\<rehrar>** Let's wrap up our discussions on the Etherpads and come back here for:
+**\<rehrar>** 14. Free to choose topics (Q&A)
+**\<m2049r[m]>** i think what we are aiming for is preventing a casual thief and his hacker friends from access to your funds. anyone else will lock you in their cellar until you tell them the passphrase/key.
+**\<msvb-lab>** It would be nice to give folks a chance at asking 'how do I use my new holiday prototype device?'
+**\<msvb-lab>** I assume it's clear what's been given out in the package:
+**\<msvb-lab>** https://taiga.getmonero.org/media/attachments/0/9/e/f/c3076b82874b6d9805dfcabca2c31e78e884536d2e98b54d3b4abc4045d0/protojulcan-2.png
+**\<msvb-lab>** And that the screen plugs in this direction:
+**\<msvb-lab>** https://taiga.getmonero.org/media/attachments/8/b/a/e/9b16894e088ee64c505dbf0fbc15788e8c5bfb18b1e0ead7056d7acf6332/protoledjc-0b.png
+**\<anhdres>** m2049r[m]: there should be a second (fake) password that shows a decoy wallet
+**\<i-a>** m2049r[m]: trying pm mattermost
+**\<msvb-lab>** ...and that each of us who received a prototype must have read a disclaimer stating that it does not support hardware wallet functions.
+**\<msvb-lab>** It's useless for storing value.
+**\<msvb-lab>** rehrar: Do you have comments or questions for revuo?
+**\<rehrar>** I'm starting to block it out, so not yet.
+**\<rehrar>** Last month was completely monopolized with multilingual implementations on Kovri and Monero websites
+**\<rehrar>** *cough* luigi1111w almost time to merge?
+**\<rehrar>** I'll be back here in like two days though :P
+**\<rehrar>** I wish I had questions for this meeting, but I'm sorry that I don't atm.
+**\<rehrar>** I do have a question though:
+**\<rehrar>** I did (or didn't?) receive a prototype board, what now?
+**\<msvb-lab>** rehrar: It's clear a lot is going on in your corner, not to mention multisig work, globee, and ebooks.
+**\<msvb-lab>** Man.
+**\<sebgus>** rehrar: I'll hook you up with one.
+**\<msvb-lab>** My impression is that test folks don't take to IRC well, so it seems we don't get questions from them.
+**\<msvb-lab>** sebgus: rehrar was retyping the text out of the agenda.
+**\<msvb-lab>** Ha.
+**\<sebgus>** aha
+**\<rehrar>** And a followup question to that: How do I create a pull request in the official Github repository?
+**\<rehrar>** This is where msvb-lab says "I'm glad you asked," and then explains in song and dance
+**\<msvb-lab>** rehrar: Ah yes, we can do a pull request tutorial.
+**\<msvb-lab>** We even have the pro teacher right here with us.
+**\<msvb-lab>** Ms/Mr pro?
+**\<msvb-lab>** First of all, is there at least one person who wants to know how to get their sekura/kastelo changes into the official repository?
+**\<msvb-lab>** There needs to be at least one indication 'yes' or else we do no tutorial.
+**\<anhdres>** I already did once for the logos, I guess I'll do the same again in the future
+**\<tat>** msvb-lab: is this about how to make a PR ?
+**\<m2049r[m]>** yes
+**\<msvb-lab>** tat: Yes, have you ever made one before?
+**\<msvb-lab>** Okay, lesson starting.
+**\<msvb-lab>** Where is sebgus and i-a?
+**\<tat>** msvb-lab: i make about 3 a day, i work as a software developer in my day job.
+**\<rehrar>** lesson = https://try.github.io/levels/1/challenges/1
+**\<msvb-lab>** So if I want to make changes to the sekura/kastelo official repository, I first clone it to my own GitHub user account (I must be signed in to already.)
+**\<msvb-lab>** https://github.com/monero-project/sekura/
+**\<sebgus>** I'm here!
+**\<msvb-lab>** I clone it in the usual way.
+**\<msvb-lab>** Since I like the command line, for me this is:
+**\<m2049r[m]>** i another question; qhats the status of the self-destruct idea?
+**\<m2049r[m]>** have
+**\<msvb-lab>** \$ git clone https://github.com/monero-project/sekura.git
+**\<msvb-lab>** cd sekura
+**\<msvb-lab>** Now I make changes:
+**\<msvb-lab>** \$ vim weirdolameness.txt
+**\<msvb-lab>** Now I commit:
+**\<msvb-lab>** \$ git commit weirdolameness.txt
+**\<msvb-lab>** ...which puts changes into only my personal cloned copy of the official repo.
+**\<msvb-lab>** Actually I missed a step which is:
+**\<msvb-lab>** \$ git push
+**\<rehrar>** If you need more help with git or github, you can ask many people here
+**\<msvb-lab>** These things are all basic to any git (this is not yet GitHub pull request specific)
+**\<msvb-lab>** Now comes the specific part...
+**\<rehrar>** I'm sure we'd be happy to lend a hand
+**\<msvb-lab>** I navigate to the official repository:
+**\<msvb-lab>** https://github.com/monero-project/sekura/
+**\<msvb-lab>** and click next to 'Branch' on the left side the button 'New pull request.'
+**\<msvb-lab>** That means, click the 'New pull request' button.
+**\<msvb-lab>** Can somebody else explain the rest, I actually can't remember what follows.
+**\<rehrar>** After you click New Pull Request? You type your changes in the provided box, and click "Submit Pull Request" or something
+**\<rehrar>** there may be requested changes by the maintainer, but that's pretty much it
+**\<tat>** You should add a short title explaining the PR content and some meaningfull description of the changes.
+**\<rehrar>** alrighty peeps, we're 5 minutes after
+**\<tat>** The smaller a pull request the betterm usually one change at a time. It is easyer for people to review those changes.
+**\<msvb-lab>** rehrar: Yes, let's close the door.
+**\<msvb-lab>** Anyway, regarding PR, please read:
+**\<msvb-lab>** https://github.com/monero-project/sekura/blob/master/CONTRIBUTING.md
+**\<msvb-lab>** https://github.com/monero-project/sekura/blob/master/PULL_REQUEST_TEMPLATE.md
+**\<rehrar>** I think it's about time to wrap up so we can move on in this little ordeal we call life
+**\<rehrar>** Thanks for a fun, if not somewhat chaotic, hardware meeting
+**\<msvb-lab>** Kerchunck. Gavel landed.
+**\<rehrar>** We'll hopefully havae another one sometime soon. As needed basis? Once a month?
+**\<msvb-lab>** rehrar: Maybe, I guess regularity might be nice.
+**\<rehrar>** You are all released from servitude. Have a great rest of your day.
+**\<msvb-lab>** Not sure what others think. Should we just meet when there's a lot to talk about or regularly?
+**\<rehrar>** We can try for next month?
+**\<rehrar>** Regular XMR meetings happen once every two weeks. Think that's too much?
+**\<anhdres>** nice talk eveybody!
+**\<msvb-lab>** rehrar: Yes, we'll do that. But unlike sgp's flow it is not part of this meeting to decide the next.
+**\<rehrar>** it might help there not be so many topics and discussions to crunch into one meeting if it was regular
+**\<rehrar>** Meeting is technically over ;)
+**\<rehrar>** So we are outside meeting flow atm
+**\<msvb-lab>** rehrar: Cool beans.
+**\<rehrar>** and discussing this casually
+**\<kamminke>** every 2 weeks is fine - enough time to has something to show which is new
+**\<msvb-lab>** kamminke: I think you're right, and instead of a sgp style decide during meetings we'll keep the email/doodle vote. You think that's okay too?
+**\<i-a>** msvb-lab: I am here! Was setting up something on mattermost.
+**\<rehrar>** Ok. We can do another doodle
+**\<rehrar>** Alright, catch you all later.
+**\<i-a>** I like doodle voting also, but I will also try to make firmware meeting next friday. I will inform abut it in monero-friendly channels around.
+**\<m2049r[m]>** msvb-lab: hows the self-destruct idea maturing? i think thats the only way to be secure.
+**\<msvb-lab>** m2049r[m]: Thank you! You're the only one who has taken interest in my wild james bond action feature so far.
+**\<msvb-lab>** I think it's actually possible, but a number of research steps are needed.
+**\<tat>** msvb-lab: how would it be triggered ?
+**\<msvb-lab>** For example, it's going to be real hard to pass enough current through those tiny wires in order to destroy the whole die without simply burning a VCC line or something.
+**\<msvb-lab>** tat: I assume a combo of caps, fuses, and a relay will do the job.
+**\<msvb-lab>** That is the idio prehistoric concept though.
+**\<tat>** msvb-lab: but what is the triggering event
+**\<msvb-lab>** There may be a much more elegant solution, we just haven't started researching it enough yet to know.
+**\<msvb-lab>** The triggering event is typically a timer.
+**\<msvb-lab>** Use case is a honest person like you or me crosses a border and is searched.
+**\<msvb-lab>** But before doing so, we set a timer on the wallet.
+**\<msvb-lab>** Seven minutes, twenty, whatever.
+**\<msvb-lab>** After which time, the cap charges, discharges, and burnes an important circuit like the secure element.
+**\<msvb-lab>** Crazy no? I'm really not sure it will work.
+**\<tat>** msvb-lab: i have been reading up on stuff the last days, and there is virtually nothing really good without NDA to secure the keys, the only really good thing that is out there are smart cards.
+**\<i-a>** tat: could you please give me a link to some smart card element worth considering?
+**\<m2049r[m]>** cant be difficult to put a smartcard reader in there - they cant be attacked?
+**\<tat>** i-a: well there is allready a bitcoin implementation
+**\<tat>** https://www.ledgerwallet.com/products/6-ledger-unplugged
+**\<tat>** they discontinued that product because of NFC problems
+**\<msvb-lab>** tat i-a: Smartcards brings us into Javacard world, not sure we want to go there.
+**\<sarang>** when has java ever gone wrong
+**\<msvb-lab>** tat: Do you think those NFC problems could become ours as well?
+**\<tat>** msvb-lab: i know java sounds ugly, but it can be pretty safe
+**\<msvb-lab>** We need to learn from their mistakes.
+**\<tat>** msvb-lab: we wouldn't use NFC
+**\<tat>** we use the smartcard processor, there are plenty of wyays to cumminicate
+**\<kamminke>** Smartcards running a small OS, which runs a hypervisor, inside there is another OS and the JavaVM .. I thinks it is security through obscurity
+**\<tat>** i show you guyes something:
+**\<tat>** https://ftsafe.com/Products/BlockChain
+**\<tat>** you can call it security by obscurity, and when it comes to the die it always is, but these stuff has been hardened for decades.
+**\<tat>** It is very very difficult to build a good and reliable attack against that kind of devices.
+**\<kamminke>** Well, your passphrase you can lost in that moment the friendly border officer requested it - your fingerprint he gets with a twist of your arm..
+**\<i-a>** (I really LIKE so many opinions here, well done:)
+**\<msvb-lab>** i-a: Pretty cool, no?
+**\<msvb-lab>** And I even think the etherpads thingie went okay. We won't do it every time, but at least the seasoned meeting participants know how it works now.
+**\<msvb-lab>** And anyone can jump into those pads at any time before, during, or after a meeting.
+**\<msvb-lab>** I'm out of here, going afk. Have a good one everybody. Thanks again.
+**\<kamminke>** I like to investigate, how Lattice stores the configuration for the iCE40 FPGA on the die - we are talking about 40nm transistors, which is fair below the Abbe-limit, no optical microscope helps anymore.
+**\<msvb-lab>** @+ 73 chao pescado
+**\<msvb-lab>** I'll put minutes up later, unless somebody else wants to do it. See the wiki/meet/ page.
+**\<i-a>** kamminke: i am not sure if yu know clifford.at, but this guy seems to be incredibly aware of everything inside lattice FPGA, maybe ask him..
+**\<kamminke>** I already talked with him at 34c3 - he gives us support for Dual-Rail Logic while synthsis, if I give him a very good analysis how I can avoid power analysis with that technique
+**\<i-a>** ok,)
+**\<kamminke>** BTW, the faitian wallet use the smartcard from infineon - I remember this are the company with the weak random generation last month in the tech news, right?
+**\<jbdatko>** It was an RSA attack -- ROCA I beleive
+**\<i-a>** i must go, thank you all for nice inputs and see yu next time:)
+**\<m2049r[m]>** kamminke: please tell me why power analysis is relevant here?
+**\<tat>** m2049r[m]: could that be related to side channel attacks by listening to the power line?
+**\<tat>** And one more question, i have seen that there is some research into using an FPGA, isn't that kind of die horribly expensive compared to other options.
+**\<m2049r[m]>** tat: as i understand it, yes - but think it is irrelevant - because if this attack is useful, the attacker has already made the device do something with the key. so they might as well make the device transfer the funds out.
+**\<m2049r[m]>** other options seem to be thin.
+**\<tat>** i have one of the small devboards, and i connected the usb-c connector to my macbook power supply, it wouldn't work, only if i use an adapter with a regular usb power supply.
+**\<tat>** Is it possible that the usb is actually a usb interface with a usb type c plug, as far as i understood usb-c uses a protocol to handle the voltage needed
+**\<i-a>** tat: Yes, it is just normal usb rewired to usbc. Usbc funkcionalities are not implemented.
+**\<tat>** i-a: so usb-c plugs won't work then, you will always need a adapter to micro or something and a usb psu
+**\<tat>** i-a: i mean usb-c cables won't work
+**\<i-a>** no,I am using original usbc cable and it works.. probably there is something how apple handle usb, it probably recognises usbc and is expecting something different..
\ No newline at end of file
diff --git a/_posts/2018-01-06-logs-for-the-Community-meeting-held-on-2018-01-06.md b/_posts/2018-01-06-logs-for-the-Community-meeting-held-on-2018-01-06.md
new file mode 100644
index 0000000000000000000000000000000000000000..bb7362ee97701543f085f027793fea00c91a160a
--- /dev/null
+++ b/_posts/2018-01-06-logs-for-the-Community-meeting-held-on-2018-01-06.md
@@ -0,0 +1,320 @@
+---
+layout: post
+title: Logs for the Community Meeting Held on 2018-01-06
+summary: Community highlights, Forum Funding System updates, RFC-HWALLET-1, Rehrar's Kovri proposal, Serhack's integrations, Fondajo, community materials, and miscellaneous
+tags: [community, crypto]
+author: dEBRUYNE / fluffypony
+---
+
+# Logs
+
+**\<sgp>** 0. Introduction
+**\<sgp>** We would like to welcome everyone to this Monero Community Meeting!
+**\<sgp>** Link to agenda on GitHub: https://github.com/monero-project/meta/issues/155
+**\<sgp>** Monero Community meetings are a discussion place for anything going on in the Monero Community. We use meetings to encourage the community to share ideas and provide support.
+**\<sgp>** 1. Greetings
+**\<rehrar>** oy
+**\<ErCiccione>** Hi folks
+**\<ordtrogen>** yo
+**\<xmrscott[m]>** Salutations
+**\<Xil3>** hello
+**\<sarang>** yo
+**\<msvb-lab>** Oops, I was on the wrong channel. Hi folks.
+**\<sgp>** 2. Community highlights
+**\<sgp>** For a great weekly summary, please read the Monero Observer: http://monero-observer.com/
+**\<sgp>** 3. FFS updates
+**\<sgp>** There are several FFS updates.
+**\<sgp>** a. RFC-HWALLET-1 project progress
+**\<sgp>** @msvb-lab, your turn 😅
+**\<ArticMine>** Hi
+**\<msvb-lab>** Cool.
+**\<msvb-lab>** The Monero Hardware had a nice meeting yesterday of our own.
+**\<msvb-lab>** We chatted on #monero-hardware for about an hour on seventeen topics.
+**\<msvb-lab>** Highlights of the past couple weeks are:
+**\<msvb-lab>** Our hardware wallet GitHub repository 'sekura' will be renamed to 'kastelo'.
+**\<msvb-lab>** That's with a 'elo' not 'kastratelo'.
+**\<msvb-lab>** ;)
+**\<msvb-lab>** We delivered about thirty (?) holiday divident prototype boards.
+**\<msvb-lab>** Via post and face to face meetings, like for example at 34C3 in Leipzig.
+**\<msvb-lab>** ...and are working on the next prototype(s) design now.
+**\<msvb-lab>** That's about all, any questions?
+**\<msvb-lab>** A firmware effort is underway, I guess we'll have a more unique device than planned.
+**\<msvb-lab>** There is a lot of interest in the group to attract more people that know cryptography and can code.
+**\<msvb-lab>** Volunteers?
+**\<msvb-lab>** Crickets.
+**\<rehrar>** I can neither code, nor know cryptography well
+**\<msvb-lab>** sgp: Next topic.
+**\<sarang>** MRL remains available with any questions that come up
+**\<rehrar>** but I'll jump right on it
+**\<msvb-lab>** sarang: That's excellent, very generous as usual of MRL.
+**\<sgp>** Thanks msvb-lab
+**\<sgp>** b. Monero Integrations
+**\<sgp>** Serhack and cryptochangements posted an update: https://www.reddit.com/r/Monero/comments/7o3rx6/serhack_updates_for_the_ebook_and_integrations/
+**\<sgp>** Do any of them want to speak about this now?
+**\<cryptochangements>** oh crap im late
+**\<cryptochangements>** is serhack here?
+**\<rehrar>** doesn't seem so. It's all you cryptochangements
+**\<sgp>** I haven't seen him here today
+**\<sgp>** Is there anything you want to mention cryptochangements?
+**\<cryptochangements>** ok, pretty much all I have to say is that the opencart plugin, the third milestone, is being worked on and is on it's way
+**\<sgp>** Great, thanks for your work
+**\<cryptochangements>** you can see the code here: https://github.com/monero-integrations/monerocart
+**\<sgp>** Anything else cryptochangements?
+**\<cryptochangements>** nope, that's all
+**\<sgp>** c. Rehrar’s Kovri proposal
+**\<sgp>** Rehrar’s Kovri proposal has moved to funding required: https://forum.getmonero.org/8/funding-required/89677/rehrar-s-2018-q1-kovri-proposal
+**\<sgp>** Anything to add rehrar?
+**\<rehrar>** fudn it
+**\<rehrar>** \*fund
+**\<rehrar>** *bows* thank you
+**\<rehrar>** jk, thing is, I'm working on Kovri regardless, so work is not slowing in any capacity
+**\<rehrar>** even while this waits for funding
+**\<sgp>** Thanks rehrar. It means a lot for the project
+**\<sgp>** Does anyone else have a FFS update?
+**\<ErCiccione>** nothing from me but if anybody has question, here to answer about localizations
+**\<sgp>** I'll proceed then onto the next topic
+**\<ordtrogen>** I have a comment on localization, when topic's up
+**\<ordtrogen>** *the topic*
+**\<sgp>** @ordtrogen you can ask it now
+**\<ErCiccione>** sure, go ahead ordtrogen
+**\<ordtrogen>** (pasting some pre-written text ...)
+**\<ordtrogen>** I've only recently gotten more involved in translation/localization but pretty quickly I have discovered a couple of issues with the localizable strings, both in the CLI and GUI project. So I think it needs some polishing to look proper. (I am filing issues as we speak) There also doesn't seem to exist much in the way of help documentation. I know there is some texts on getmonero.org, but I'd argue there should fir
+comes with the installation, such as a man file for unix and maybe some other formats for Mac and Windows. Which makes me think we should spend a little more time on the "foundations" of the texts we write. Like improving the UI English. While @ercicciones work on the localization project obviously is fantastic, I'm thinking, what quality can the translations have unless the source (en) is correct?
+**\<rehrar>** Agree wholeheartedly.
+**\<rehrar>** As I work on the website here and there, most of the text is not written by me, except for the newer pages (and even that should be reviewed). Some of the copy does not read well, or is over flowery in some places, or other issues.
+**\<ErCiccione>** yes, a lot of good points. the source file has been polished not a month ago, but would be great to have a clean and reviewed text to work on
+**\<sgp>** I think most people agree documentation needs to be improved across the board
+**\<ErCiccione>** about documentation
+**\<ordtrogen>** I'm thinking a man file for monerod would be in order. Need not be too extensive
+**\<ordtrogen>** (linux)
+**\<ordtrogen>** And I'm not sure, what is displayed by $monerod --help is not localizable, right?
+**\<ErCiccione>** i'm working in creating a wiki with everything necessary for a translator, it can be found here https://taiga.getmonero.org/project/erciccione-monero-localization/wiki/home it need some improving, but following translators can take days some times, and i actually have no time, would be great to have some help on that side
+**\<ErCiccione>** @ordtrogen it is actually, you can find the references to the code in the .ts files
+**\<ordtrogen>** ok. I just wanted to bring up the issue. As soon as I have to write something, I will.
+**\<ErCiccione>** iirc a man file was partially done few days ago, but yes, there
+**\<ordtrogen>** Will try to finish the testing and issue reporting first
+**\<ErCiccione>** \* there is needing of a lot of clean documentation, thank you for bringing that up
+**\<ordtrogen>** Oh, a man file is somewhere in the repos?
+**\<ordtrogen>** CLI or GUI`?
+**\<dEBRUYNE>** Just dropping this here: https://www.reddit.com/r/Monero/comments/7nl38w/technical_documentation_for_monero/ds2nkfu/
+**\<ordtrogen>** Oh, great
+**\<ordtrogen>** I don't have time to follow r/monero too much
+**\<ErCiccione>** dEBRUYNE, uh that looks very good
+**\<sgp>** Anything else we need to discuss on this topic?
+**\<dEBRUYNE>** Perhaps reach out to the owner to collaborate
+**\<ordtrogen>** Oh, man, That site looks great!
+**\<sgp>** Ok, I'm going to move on. Thanks @dEBRUYNE @ErCiccione
+**\<sgp>** 4. Fondajo
+**\<sgp>** After months of progress, I am pleased to announce that I am proceeding with a 501(c)3 nonprofit cryptocurrency foundation called “Fondajoâ€. I have a great workgroup of people who are helping organize all the documents.
+**\<sgp>** This cryptocurrency nonprofit will promote education, research, and development. One of its values will be to promote privacy projects. The foundation will still be completely separate from Monero.
+**\<sgp>** When the nonprofit is officially incorporated, I will hand over the responsibilities of this workgroup to rehrar. I’m sure that we can use some help from other members who have been active these past several months.
+**\<sgp>** To be clear, this is not a Monero-specific foundation, but it will support many of Monero'
+**\<sgp>** \*many of Monero's projects
+**\<ArticMine>** This is a US base non profit?
+**\<sgp>** Yes, US-based
+**\<sgp>** Which will allow people in the US to make tax-deductible donations
+**\<ordtrogen>** TAlk about the name Fondajo
+**\<ordtrogen>** (now I see the meaning in espreanto)
+**\<sgp>** If you are interested in helping with the nonprofit, let me know in PM
+**\<sarang>** What are the practical types of projects/goals related to the mission?
+**\<sarang>** or some examples?
+**\<sgp>** Any published research in cryptocurrencies is fair game
+**\<sgp>** Educational outreach is prioritized for grants too
+**\<sgp>** I'm still seeing what can be done for development, but I'd like to support this as much as possible
+**\<sarang>** Nice, so it'd issue grants from its asset pool of donations?
+**\<sgp>** Exactly
+**\<sarang>** Excellent
+**\<dEBRUYNE>** As long as it doesn't end up like the Bitcoin foundation lol
+**\<sarang>** I assume the nonprofit status might make it easier to help support students as well
+**\<sgp>** It will be very different from the Bitcoin Foundation, even by registration
+**\<sgp>** Bitcoin Foundation is not a 501(c)3
+**\<dEBRUYNE>** I am just talking about their endeavors etc.
+**\<sgp>** Since this is a 501(c)3, the focus will be entirely on education, research, and (hopefully) development
+**\<cwcopz>** "Fondajo" sounds like an intersting project. Is there more information available? Is there a official homepage?
+**\<sgp>** I think it will really help raise money for projects that can benefit Monero and other privacy projects
+**\<sarang>** I know suraeNoether has toyed around with the idea of a nonprofit too, so I'll page him here
+**\<rehrar>** Privacy advocacy!
+**\<sgp>** cwcopz I have the domain but haven't made a website yet
+**\<rehrar>** Monero is just one tool in the opsec of a privacy focused person
+**\<cwcopz>** Is there a way to stay up to date? I would like to donate to this project as well.
+**\<sgp>** Any other questions?
+**\<sgp>** I want to assure everyone that Fondajo will remain completely separate from Monero itself
+**\<ordtrogen>** Did you get the .co domain?
+**\<dEBRUYNE>** Is anyone getting paid?
+**\<sgp>** @cwcopz I'll put all major updates in /r/Monero and /r/MoneroCommunity
+**\<cwcopz>** Okay, thanks. Sounds promising!
+**\<sgp>** @dEBRUYNE it's likely there will be overhead for some positions, but I want to keep it minimal
+**\<dEBRUYNE>** I am personally not a fan of people getting paid in a nonprofit, it should be done altruistically
+**\<sarang>** I think it depends on the level of work. If it's your full-time job, you should get compensated
+**\<sarang>** peeps gotta eat
+**\<sgp>** @dEBRUYNE it's sometimes better to be able to pay people to allow them to spend all their time working on improving the cryptocurrency ecosystem
+**\<rehrar>** what if they are paid in love?
+**\<sarang>** Will my landlord accept love as rent?
+**\<sarang>** That might be illegal
+**\<rehrar>** well, as in crypto, consensus is mandatory
+**\<rehrar>** moving on :P
+**\<ordtrogen>** Can't an organization be non-profit as a whole but still pay for services?
+**\<sgp>** Ok sarang, you're up
+**\<sarang>** 501(c)(3) orgs can pay their staff
+**\<sarang>** I thought I'd mention one FFS that's sorta kinda community related
+**\<sarang>** It was suggested that we send a couple of folks to some academic conferences for knowledge gains and community representation
+**\<sarang>** suraeNoether and I wish to attend the BPASE18 conference at Stanford later this month
+**\<sarang>** and suraeNoether plans to attend the RWC conference in Zurich with fluffypony
+**\<sarang>** So we have an open FFS for the usual expenses
+**\<rehrar>** 5 star hotel, caviar every night, the works
+**\<sarang>** I'm mainly looking for input from the group about how important y'all feel conferences are for the Monero group
+**\<sarang>** and if FFS should be the preferred way of sending folks to conferences that we agree are worthwhile
+**\<dEBRUYNE>** sgp, sarang: Let's discuss that another time :P
+**\<dEBRUYNE>** sarang: conferences are one of the main ways to network
+**\<sarang>** OK, wasn't sure if this was a good place for that discussion
+**\<dEBRUYNE>** As long as they aren't detrimental for day-to-day work
+**\<dEBRUYNE>** i.e. it leaves no time to work on "normal" stuff
+**\<rehrar>** To answer the first question: extremely important
+**\<rehrar>** The Monero Project needs to be a part of a larger conversation
+**\<sarang>** dEBRUYNE: the conference schedules are usually pretty packed, but BPASE is only 3 days
+**\<rehrar>** a conversation about privacy, human rights, cryptography, and more
+**\<rehrar>** going to these conferences is a way for representatives of The Monero Project to be a part of that conversation
+**\<rehrar>** I think The Monero Project has a unique voice, and unique things to add to such conversations as well, and our perspective will be helpful
+**\<ErCiccione>** sarang: link of the FFS?
+**\<sarang>** OK thanks for this perspective
+**\<rehrar>** https://forum.getmonero.org/8/funding-required/89695/funding-for-noether-brothers-to-attend-stanford-bpase18-conference
+**\<sarang>** We used a single FFS but listed the separate costs for reference: https://forum.getmonero.org/8/funding-required/89695/funding-for-noether-brothers-to-attend-stanford-bpase18-conference
+**\<ErCiccione>** uw... double, nice. Thanks guys
+**\<sarang>** I agree with rehrar that this should be part of a larger discussion about our involvement in the broader academic community
+**\<sarang>** I recommend interested persons take a look at the conference schedules and programs. Lots of excellent talks
+**\<sgp>** Anything else sarang? I have no issue with this FFS proposal
+**\<sarang>** Nope, just wanted to open the broader conversation
+**\<sarang>** Appreciate the insights from all of you
+**\<sgp>** 5. Community materials
+**\<sgp>** This section of the meeting was inspired by this post: https://www.reddit.com/r/Monero/comments/7obquf/wake_up_we_need_better_marketing_and_better/
+**\<sgp>** Let’s discuss how the Monero community can better market itself to others and what materials could be beneficial to newcomers.
+**\<sgp>** Anyone want to begin?
+**\<cryptochangements>** yesterday i saw a youtube ad for Bitcoin. I think we need one for monero with fluffypony in a lambo
+**\<cryptochangements>** \s
+**\<ordtrogen>** I keep seeing them for Dash!!!
+**\<ordtrogen>** yuck
+**\<Guest93332>** I want to know why is this community not communicated more on the official channels? i only heard about it as an comment on an reddit thread? This here should be more public.
+**\<sarang>** I find it interesting to watch the top coins by cap... so many that seem to rely on marketing
+**\<Guest93332>** \*this community chat not ..
+**\<sgp>** @guest93332 this is a workgroup. You can see what it does in /r/MoneroCommunity
+**\<rehrar>** It's on the Hangouts page and the Footer of the website also
+**\<sgp>** You're right though that we should probably encourage more people in /r/Monero and elsewhere to participate
+**\<Guest93332>** yeah for example - it should be on r/monero
+**\<rehrar>** like...the Community meeting announcement should be on /r/monero?
+**\<sgp>** I still think the best marketing is good documentation and beginner resources
+**\<sgp>** At least for now
+**\<cryptochangements>** well as people have discussed before, if we are going to market monero it has to be based on education. not stupid hype
+**\<rehrar>** agree cryptochangements, but we all have to recognize one thing
+**\<rehrar>** we can't tell anyone what to do, so if one person was to start a 'hype' focused marketing thing, we can't stop them
+**\<cryptochangements>** fair enough
+**\<rehrar>** And the clock is ticking until some initiative-filled person will do it
+**\<rehrar>** so the best way to prevent it
+**\<Guest93332>** i have another question, for beginners it is very hard to find out about irc and that stuff. could the whole communication change from irc to discord or is it like monero is for the cryptogeeks?
+**\<rehrar>** is to get a marketing team together that will focus on education and awareness
+**\<rehrar>** that way, when said initiative-filled person comes in
+**\<rehrar>** we can funnel him into the already underway marketing effort
+**\<rehrar>** and his/her skills will be with the community
+**\<rehrar>** the longer we wait for some form of marketing workgroup, the more likely it is that somebody that doesn't believe what we do about hype and education will start it
+**\<msvb-lab>** Guest93332: Discord would be nice to have. My impression is that the folks moderating the dozen or so current channels and bridges to channels aren't able to keep up.
+**\<cryptochangements>** Guest93332: can this be discussed after the meeting in open discussion in a few minutes?
+**\<msvb-lab>** There may not be a volunteer to configure and moderate Discord.
+**\<rehrar>** Guest93332: we have slack and mattermost connections also
+**\<rehrar>** mattermost.getmonero.org
+**\<Guest93332>** ok
+**\<ErCiccione>** and riot/matrix
+**\<rehrar>** believe me, I'm not a geek. :P Which is why I worked on getting other non-IRC things up here also so people like me could participate
+**\<cryptochangements>** i remember a r/moneromarketing did exist at one point, but then turned into monerocommintu
+**\<sgp>** Formalizing an actual marketing campaign is a topic for another day, but how can we encourage people to make these helpful user guides, videos, infographics, etc?
+**\<rehrar>** I still own it cryptochangements
+**\<cryptochangements>** and then the marketing ideas all kinda got shunned
+**\<sarang>** There's a saying that it's orders of magnitude harder to refute BS than to spew it
+**\<sarang>** We'll always have that working against us for hype
+**\<rehrar>** I think if we get some Monero merch
+**\<rehrar>** and have some giveaways based on competition of content creation
+**\<rehrar>** then that'd be a fun way to both engage the community, get some Monero marketing type merch out there, and incentivize quality content creation
+**\<cryptochangements>** sgp: i think we have to figure out what kind of marketing we want to encourage before we can start encouraging marketing at all
+**\<cryptochangements>** ooo good idea rehrar
+**\<sgp>** @rehrar I like that idea
+**\<ErCiccione>** I don't know if i like it, it's not ideal to compensate people for something they should do because they believe in it
+**\<sgp>** I think a Monero webcam cover is a good incentive. People seem to love them
+**\<rehrar>** ErCiccione this is indeed the balance of initiative-based projects
+**\<rehrar>** people with the most initiative will be (usually) people who believe in the project
+**\<cwcopz>** sgp Agree. Would buy one as well.
+**\<rehrar>** this will mean that the 98% who are on board for other reasons will rarely do something that requires their own initiative
+**\<cryptochangements>** ErCiccione a t-shirt or some webcam covers isnt like a fat cash prize. people who participate would still probably do it bc they like Monero. the incentives just kinda get the ball rolling and make it a little bit more fun
+**\<rehrar>** and make no mistake, while I do think Monero has a higher number of idealists, as the days pass, and more people join, Monero will be overrun by people who don't see the vision
+**\<cwcopz>** I've created a homepage to show some monero artwork. Can I post the link? It is WIP and at the moment a little bit outdated.
+**\<rehrar>** in a sense, we have to woo those people to the vision. In part by being a friendly-community and making them want to stick and around and stay, and the more they stay, the more they listen, the more they listen, the more they learn
+**\<sgp>** Sure
+**\<cwcopz>** WIP https://monero.gallery/
+**\<ErCiccione>** cryptochangements: yes, in those terms sounds fair, but i don't love it anyway :P
+**\<rehrar>** community engagement is the start of the process I just described
+**\<cwcopz>** Focus: Art, what is monero?, speading the word, privacy ...
+**\<cwcopz>** Do you think it is worth to work on in the future?
+**\<rehrar>** *shrug* we never know what will grab the community
+**\<ErCiccione>** rehrar: yes, but i want to make sure we don't push monero engagement giving for granted a future downfall of its community
+**\<rehrar>** I think it'd be a fun way for designers to hop on board, so why not cwcopz?
+**\<sgp>** @ErCiccione I obviously prefer if everyone does something for free, but if all they need is a free little piece of merch to contribute, it's probably worth it
+**\<cryptochangements>** unfortunatly rehrar is right. with the huge price pumps most people are here for the money, not the ideals. but im gonna share a secret: I found monero bc it was easy to mine and i was gonna convert it all to BTC. but once i found out monero is way better than BTC i kept my monero and eventually got more involved in the community. Like rehrar said, you kinda gotta woo people over to the id
+**\<ErCiccione>** i agree @sgp i only want to avoid it becomes a strategy, when we can also make promotional video to ask people to contribute, hackatons and stuff like that
+**\<rehrar>** there are human elements to the Monero community, and I realize the ideal is that we won't hvae to play to those human elements and the technology will speak for itself
+**\<rehrar>** this is honestly a kind of thinking that conveys a lack of understanding and appreciation for the intricacies of handling the social part of a project
+**\<cwcopz>** @rehrar I think the same. I am not a coder but possible a way to contribute to monero at all
+**\<rehrar>** many great projects break down for social reasons
+**\<sgp>** Does anyone else have marketing-specific discussion, or should I open it to the broader open ideas time?
+**\<rehrar>** we've kind of melded the two :P
+**\<sgp>** Ok, let's continue with open ideas time
+**\<sgp>** What does everyone think of the Coffee Chats? We often have a hard time getting enough people to join
+**\<cwcopz>** Coffee Chats?
+**\<cryptochangements>** I think that it is an awesome idea. But I don't think enough people know about them
+**\<rehrar>** these things start and gain momentum slowly
+**\<sgp>** https://www.youtube.com/watch?v=EcKgnjqSXpA&list=PLsSYUeVwrHBnzudI3KSSW4aVa_4Ty1Kew
+**\<cryptochangements>** they usually have great discussion, but have a turnout of like 60 viewers
+**\<Guest93332>** thats the problem. we need more commuication penetration in all activities
+**\<rehrar>** keep a schedule, and they will grow. imo, even if we help bring just one person closer to the vision, it was well worth it :D
+**\<cwcopz>** Thanks for the link. Didnt know that this exists.
+**\<sgp>** Since the next one is on the 20, how should I promote it differently to attract more viewers?
+**\<cryptochangements>** sgp: the coffechat seems like something r/cryptocurrency would go nuts over
+**\<Guest93332>** you should use all officials account with social media
+**\<sarang>** Remind me, are they advertised on places like r/monero or r/xmrtrader?
+**\<sgp>** I typically post on /r/monero yes
+**\<sgp>** I haven't posted about it in /r/xmrtrader before
+**\<ErCiccione>** sgp: i think it needs some more scheduled advertising, like 24 hours earlier and then a couple of hours before starting. And a massive use of social accounts a couple of hours before the chat
+**\<cryptochangements>** Personally, i think the coffechats are something that should be advertised everywhere
+**\<rehrar>** sarang: you should join up on this one
+**\<sgp>** We had the most views when fluffypony posted it on his Twitter
+**\<sarang>** Sure, I'd be glad to
+**\<Guest93332>** or the official @monerocurrency account
+**\<cryptochangements>** who is in the lineup for this next one?
+**\<sarang>** Oh yeah, an fp twitter post would be great
+**\<sgp>** @cryptochangements any active community member who wants to participate can
+**\<cryptochangements>** ok cool
+**\<rehrar>** the more the better. We just hang out and be losers together
+**\<cryptochangements>** sounds lit ðŸ‘
+**\<sgp>** Ok, I'll try to make sure the event has more 24 hr exposure
+**\<Guest93332>** who controls the official accounts? its all about being present and penetration. Especially in crypto - you have to be heard
+**\<sgp>** How much of the time should be dedicated to audience Q&A?
+**\<ordtrogen>** What about inviting a known guest
+**\<cryptochangements>** tbh i think it should just depend on audience turnout/how many questions people actually have
+**\<ordtrogen>** Like brighton36
+**\<sgp>** @ordtrogen I'm open to that idea
+**\<ordtrogen>** Or someone else favorable to our cause
+**\<rehrar>** alright, I gotta split
+**\<rehrar>** talk to you guys later :)
+**\<ErCiccione>** @sgp: i'd say as much as it takes, once you understand the discussion is not "spicy" anymore. I also like @ordtrogen idea, but i think sarang's presence will catch a lot of interest, if advertised before
+**\<sarang>** aw shucks
+**\<sarang>** I'm just a simple guy with a simple message
+**\<sarang>** https://media.giphy.com/media/A7WK7FddTxKfu/giphy.gif
+**\<ordtrogen>** my idea came just now. no thinking thru
+**\<sgp>** Thanks for the input everyone. I'd like to leverage this as much as possible
+**\<ordtrogen>** but maybe that person would bring part of her/his audience along?
+**\<sgp>** @ordtrogen let's come up with a list of possible people after the meeting
+**\<ordtrogen>** ok
+**\<sgp>** I imagine they would bring some of their audience on, yes
+**\<ErCiccione>** sarang: you are a monero research lab master! deal with it! lol for the gif
+**\<sgp>** 7. Confirm next meeting date/time
+**\<sgp>** The next community meeting will be two weeks from today on 20 January. The next Coffee Chat will be next week on 13 January: https://github.com/monero-project/meta/issues/156
+**\<sgp>** 8. Conclusion
+**\<sgp>** That’s all! Thanks for attending this Monero Community meeting, and we hope to see you on /r/MoneroCommunity and #monero-community. Take care, and know that change starts with YOU.
+**\<sgp>** I hope eveyone was ok with a longer meeting this time. People were open to it in previous meetings
+**\<sarang>** sgp: please send me a reminder for the chat =p
\ No newline at end of file
diff --git a/_posts/2018-01-12-logs-for-the-Hardware-firmware-meeting-held-on-2018-01-12.md b/_posts/2018-01-12-logs-for-the-Hardware-firmware-meeting-held-on-2018-01-12.md
new file mode 100644
index 0000000000000000000000000000000000000000..7cda4affd6623c6e29f818acaf6f878300ec5a93
--- /dev/null
+++ b/_posts/2018-01-12-logs-for-the-Hardware-firmware-meeting-held-on-2018-01-12.md
@@ -0,0 +1,386 @@
+---
+layout: post
+title: Logs for the Hardware Firmware Meeting Held on 2018-01-12
+summary: Discussion of the firmware for the dedicated hardware wallet and a discussion of Ledger's approach
+tags: [community, crypto]
+author: dEBRUYNE / fluffypony
+---
+
+# Logs
+
+**\<i-a>** Hello all, it is time for our firmware meeting to start. I am not sure if it is not too early to have a meeting like this, but let's see.
+**\<i-a>** Strange, there were so many people saying they have questions about code and now nobody is here:) So I will give a quick update on our project:
+**\<i-a>** Ok here is the quick update: USB communications is working, alse we can generate wallet by using internal random number generator (thanks god for m2049r, nice job)
+**\<i-a>** Maybe you have some recommendation how to move from here? My questions could look silly, but thats because I am personally just learning monero.
+**\<m2049r[m]>** :)
+**\<i-a>** On the other hand, there are other people working and maybe my questions could help also to them.
+**\<m2049r[m]>** is there anyone here who is actually taking part in this meeting besides us two?
+**\<hotoatmeal>** is the plan to use the same strategy that the ledger guy came up with, where private keys are sent (encrypted) from the device to the wallet?
+**\<qqitty>** CS noob looking to study xmr code this weekend. any design books/web guides to read like Huang's dissecting BTC?
+**\<hotoatmeal>** m2049r[m]: I'm mostly passively participating, until that question
+**\<dEBRUYNE>** m2049r[m]: Most people will probably just read until they want to say something :p
+**\<i-a>** hotoatmeal: We are here to speak about the plan.. I think if we want to do all the signing stuff in the device, we would need more memory.In case we need more memory, we will just setup a new device with bigger mcu.
+**\<m2049r[m]>** i would like an implementation where the keys never ever leave the device - we have to see if thats possible with the hardware constraints we have.
+**\<hotoatmeal>** I would like that too!
+**\<i-a>** It is still organic and you have perfect opportunity to bend the way how it is being developped:)
+**\<i-a>** Me too.
+**\<m2049r[m]>** there may be multiple implementations, with different roads to success.
+**\<hotoatmeal>** I don't yet understand how to find transaction outputs without revealing the view key
+**\<m2049r[m]>** without having studies the code i think it should be possible to hook into the code and have the device take over when keys are in play.
+**\<hotoatmeal>** if that's not possible, then the entire blockchain would have to be fed through the device over usb.... might be quite slow.
+**\<m2049r[m]>** (into the wallet client code)
+**\<m2049r[m]>** yes - but thats probably not a good idea - and were back to sending the keys to the client
+**\<hotoatmeal>** yeah :/
+**\<hotoatmeal>** too bad homeomorphic encryption systems are so slow
+**\<hotoatmeal>** otherwise you could trustlessly give the client an encrypted version of your view key, let it scan the blockchain for you, and provide the relevant txo's (also encrypted)
+**\<hotoatmeal>** and have the device decrypt the computed result
+**\<m2049r[m]>** i need to read up on how exactly the keys are used in the clients - any specific hint on where to get started?
+**\<hotoatmeal>** cryptonote paper is where I got started
+**\<hotoatmeal>** also looking at the ledger guy's patch
+**\<m2049r[m]>** i am not sure the communication to & from the device needs to be encrypted - are you worried about usb sniffers?
+**\<jbdatko>** hotoatmeal, can you link that patch?
+**\<m2049r[m]>** and if yes, whats the attack?
+**\<hotoatmeal>** so two separate things, both with different reasons for encryption
+**\<qqitty2>** Thanks @hotoatmeal. I'll go dive into the cryptonote WP
+**\<m2049r[m]>** cryptonote paper seems mostly vague
+**\<hotoatmeal>** ledger guy's patch encrypts the communication because it's transferring raw key data
+**\<hotoatmeal>** should be a no-brainer that that should be encrypted
+**\<luigi1111>** Paper is pretty clear unless you want implementation specifics
+**\<m2049r[m]>** heh yes
+**\<hotoatmeal>** this other thing about H-E, is a separate idea, and that's to allow someone else to scan the blockchain on your behalf, without revealing your view key to them (losing your privacy)
+**\<m2049r[m]>** paper is clear - i meant vague in the sense of implementation specifics
+**\<m2049r[m]>** H-E?
+**\<luigi1111>** I think you pretty much have to have client do the scanning
+**\<luigi1111>** Not the hw
+**\<hotoatmeal>** homeomorphic encryption
+**\<dEBRUYNE>** jbdatko: It's under open PRs on the monero repository
+**\<luigi1111>** Unless you have some hw acceleration it's just too slow
+**\<i-a>** luigi1111: yes but is there a way how to do it?
+**\<luigi1111>** How to do which
+**\<hotoatmeal>** i.e. someone else performs math on encrypted values that they can't see, and returns the result to you
+**\<i-a>** how to let PC scan the whole blockchain and prepare outgoing tx in a way, that the are sent to device just for signing.
+**\<luigi1111>** Sure
+**\<luigi1111>** The cold wallet signing basically does this already
+**\<hotoatmeal>** the problem is that H-E implementations of crypto algos are really really really slow
+**\<hotoatmeal>** like hours for a single round of AES
+**\<luigi1111>** That'd probably be slower than the device doing the scanning ^^
+**\<luigi1111>** :)
+**\<hotoatmeal>** yeah
+**\<i-a>** :(
+**\<hotoatmeal>** but in terms of mathematical purity / elegance... I really want that kind of solution to work :)
+**\<hotoatmeal>** jbdatko: https://github.com/monero-project/monero/pull/3095
+**\<i-a>** Ok, another question: If device did he whole scanning. How much memory we need on the device? I think that downlink from peers is usually slower than USB, so limitations is more in memory requirement at the device.
+**\<m2049r[m]>** how big of a problem would it be to reveal the viewkey to the client?
+**\<luigi1111>** Not memory
+**\<luigi1111>** Cpu
+**\<luigi1111>** I don't think it's an issue
+**\<luigi1111>** I mean it isn't perfect
+**\<luigi1111>** But it has the benefit of being workable
+**\<hotoatmeal>** revealing to the client just means that you can't have a non-daemon client
+**\<luigi1111>** Sure you can
+**\<i-a>** yes but it is fine for now I think.
+**\<luigi1111>** You could have a remote node
+**\<hotoatmeal>** well, yeah
+**\<luigi1111>** All the way to mymonero
+**\<m2049r[m]>** the client wallet cache - is that encrypted?
+**\<moneromooo>** Yes.
+**\<m2049r[m]>** thought so - so the device would need to do that as well.
+**\<hotoatmeal>** is it possible to give the client an image of the view key, and then have it search the blockchain for some subset of txo's that /might/ match (as a coarse filter)?
+**\<endogenic>** vtnerd
+**\<jbdatko>** hotoatmeal, thank you
+**\<hotoatmeal>** (reducing the amount of work the device has to do, but not giving up the full key data?)
+**\<m2049r[m]>** how would that work?
+**\<jbdatko>** AES accelerators on MCU are pretty good now, so depending on the MCU it might not be completely horrible (sorry I'm jumping in w/o knowing the full context)
+**\<endogenic>** hotoatmeal: mrl has been workin on this problem for some time
+**\<hotoatmeal>** endogenic: anything I'm saying known not to be worth pursuing? (by proofs that it doesn't work, or somesuch)
+**\<m2049r[m]>** we have space for secure elements on the board - things which can do aes and other things in hardware.
+**\<luigi1111w>** you need ed25519 acceleration
+**\<luigi1111w>** which I doubt exists
+**\<m2049r[m]>** yeah, except that.
+**\<hotoatmeal>** heh. now it needs an fpga
+**\<luigi1111w>** I don't really see any way around it
+**\<luigi1111w>** mymonero as a hw client would actually be quite desirable
+**\<luigi1111w>** and quite an upgrade
+**\<luigi1111w>** well it all depends on perspective :)
+**\<endogenic>** :)
+**\<luigi1111w>** the most secure/private arrangement would be user owned daemon -> wallet/client -> hw
+**\<luigi1111w>** but you can delegate the first two for privacy loss
+**\<luigi1111w>** well the first one isn't really privacy loss
+**\<i-a>** our nordic semiconductor candidate has ed25519 hw block, but we still didnt get them.
+**\<luigi1111w>** or a different type or of privacy
+**\<luigi1111w>** i-a that's interesting
+**\<luigi1111w>** I'd be curious to see perf numbers
+**\<m2049r[m]>** i-a but thats with an nda so we cant be open source, no?
+**\<luigi1111w>** for some usable ed25519 operation
+**\<i-a>** luigi1111w: nRF52840, it has secure crypto cell or something like that.
+**\<i-a>** Of course there are other problems, like a non open design and so on.
+**\<msvb-mob>** cryptocell is available without nda.
+**\<luigi1111w>** I mean something like signatures/sec
+**\<i-a>** another question is if this cryptocell ed25519 is fast enough to be usable.
+**\<luigi1111w>** that was my only question :)
+**\<i-a>** Unfortunately I dont know now. But I will try to find out. It seems like as-fast-as-possibe ed25529 od device is a must.
+**\<hotoatmeal>** do you have a ballpark for how fast it would have to be to be usable?
+**\<msvb-mob>** cec1702 has the cuve too.
+**\<i-a>** msvb-mob: nice, can we somehow determine their performance?
+**\<m2049r[m]>** they sortof claim its 10x a software solution but dont show numbers
+**\<luigi1111w>** software solution on that power of hw?
+**\<luigi1111w>** IDK, something similar to an older cpu
+**\<msvb-mob>** i-a: I don't know how to measure performance without testing the devices on real hardware, unfortunately.
+**\<i-a>** https://www.microchip.com/wwwproducts/en/CEC1702
+**\<i-a>** this is it \^
+**\<m2049r[m]>** thats the question luigi - its blabla
+**\<m2049r[m]>** can we GET real hardware?
+**\<luigi1111w>** :)
+**\<i-a>** msvb-mob: hmm:( are we going to have cec1702 to do some testing?
+**\<luigi1111w>** I think it would be really cool if such a device could be made
+**\<luigi1111w>** but I'm skeptical
+**\<msvb-mob>** m2049r[m]: I can send you a nRF52840-DK if you want.
+**\<luigi1111w>** we know the viewkey delegation works, at least
+**\<msvb-mob>** i-a: The nRF is easy (there's a devkit for that) but to test the CEC1702 we must make the boards ourselves first.
+**\<luigi1111w>** (mymonero and openmonero both use the exact same idea already)
+**\<msvb-mob>** I think the MCUs are already in my lab.
+**\<i-a>** msvb-mob: that is not a big deal, if you know the are comming, i can send you a board asap.
+**\<i-a>** (lets say gerbers on monday/tuesday)
+**\<i-a>** msvb-mob: what about nda on this cec1702? Or do they have some problem?
+**\<msvb-mob>** The CEC1702 is not NDA encumbered.
+**\<i-a>** perfect candidate -\_-
+**\<msvb-mob>** Yes, I think so too.
+**\<m2049r[m]>** the CEC1702 & the nRF52840 would replace our MCU?
+**\<i-a>** m2049r[m]: I think yes, because our mcu is lacking ed25519
+**\<msvb-mob>** m2049r[m]: They are both Cortex-M4 MCUs so they could do so. If they aren't large enough to contain transactions in memory or code in program storage we could use them as coprocessors probably.
+**\<msvb-mob>** Would be a bit weird.
+**\<m2049r[m]>** we have to see what they mean by ed25519. do we need just signing & verifying or do we also need curve arithmetic luigi1111w
+**\<luigi1111w>** signing and verifying sorta-mostly-ish include all the operations needed
+**\<luigi1111w>** I guess that's not really true
+**\<luigi1111w>** but the operations that need accelerated would be, mostly
+**\<m2049r[m]>** the data sheets says:
+**\<m2049r[m]>** Elliptic Curve point multiply with Curve25519
+**\<m2049r[m]>** The Edwards-curve Digital Signature Algorithm (EdDSA), using Curve25519
+**\<m2049r[m]>** (CEC1702)
+**\<iDunk>** ed25519 != Curve25519.
+**\<i-a>** nRF does both i think
+**\<i-a>** yes
+**\<i-a>** but cec1702 doesn't have ed25519:( or I cannot find it in datasheet.
+**\<m2049r[m]>** the nrf can create keys, sign & verify. "The generation is performed using EC Edwards ed25519 algorithm."
+**\<i-a>** cec1702 has only Curve25519
+**\<luigi1111w>** if they are going off of nacl or similar they have both
+**\<luigi1111w>** the signing is ed
+**\<luigi1111w>** and the box stuff is curve255
+**\<msvb-mob>** i-a: No ECDSA on CEC1702? I don't have the documents with me now.
+**\<i-a>** ok so to be clear:
+**\<i-a>** The Elliptic Curve Digital Signature Algorit
+**\<i-a>** hm (ECDSA), using all supported NIST curves
+**\<i-a>** he Edwards-curve Digital Signatur
+**\<i-a>** e Algorithm (EdDSA), using Curve25519
+**\<luigi1111w>** that could be naming issues though :)
+**\<i-a>** maybe ed25519 is hidden somewhere, but it isn explicitly mentioned, Curve25519 is mentioned.
+**\<i-a>** \*isnt
+**\<luigi1111w>** yeah they are often bundled together
+**\<m2049r[m]>** so you are saying we need new hardware in any case?
+**\<luigi1111w>** to attempt to "do everyone on device", yes (and I'm doubtful it's possible)
+**\<luigi1111w>** to do a client-delegated arrangement, no
+**\<hotoatmeal>** these slides say they can do ~1400 ECDH's /s on a cortex A8: https://cr.yp.to/talks/2012.11.29/slides.pdf
+**\<msvb-mob>** i-a: The ED25519 API is on pages 60-61 of the CEC/MEC Family Devices ROM API Users Guide.
+**\<i-a>** msvb-mob: thank you,)
+**\<msvb-mob>** For example ed25519\_valid\_sig (validate signature) is a function.
+**\<hotoatmeal>** and Ed25519 was only a bit slower
+**\<hotoatmeal>** what's the rough size of the blockchain, counted in txo's?
+**\<luigi1111w>** total size isn't that useful
+**\<luigi1111w>** size over past month much more so
+**\<hotoatmeal>** growth rate too
+**\<luigi1111w>** yeah with some assumed groth
+**\<luigi1111w>** growth
+**\<luigi1111w>** 200k txs last month
+**\<luigi1111w>** so maybe 450k outputs
+**\<luigi1111w>** double that at least gets you 1mi/mo
+**\<luigi1111w>** checking an output is something like 2x ECDH
+**\<hotoatmeal>** so it'll get slower by 20 mins, every month
+**\<hotoatmeal>** ouch
+**\<luigi1111w>** if you don't use it
+**\<luigi1111w>** but yeah
+**\<hotoatmeal>** (assuming you need to re-scan the entire chain each time... but maybe that can be cached)
+**\<luigi1111w>** there would be quite some catchup time
+**\<i-a>** not sure if relevant, but this could be ECDSA performance on CEC device: https://imgur.com/a/WQKqp ?
+**\<luigi1111w>** if you leave it unplugged for some time
+**\<luigi1111w>** oh
+**\<luigi1111w>** I would sure assume you cache
+**\<luigi1111w>** if you don't it
+**\<luigi1111w>** it's pretty unworkable
+**\<hotoatmeal>** yeah
+**\<luigi1111w>** you'd have to leave it plugged in a few hours before you could spend each time :)
+**\<hotoatmeal>** the worst case of initializing a new device though is pretty bad
+**\<hotoatmeal>** though I guess you could just sweep everything to it, and ignore all of the chain that happened before then
+**\<luigi1111w>** restored device
+**\<luigi1111w>** new device has no txs
+**\<hotoatmeal>** right
+**\<hotoatmeal>** at least the restore point is something you can make note of, encrypt, and then store like any other backup
+**\<m2049r[m]>** are you suggesting we keep the chain/cache on the device?
+**\<luigi1111w>** no
+**\<luigi1111w>** definitely not the chain
+**\<luigi1111w>** I'm still skeptical it's workable at all, just exploring the idea
+**\<m2049r[m]>** gottit
+**\<hotoatmeal>** do bulletproofs change the costs here?
+**\<hotoatmeal>** s.do.will.
+**\<m2049r[m]>** do we have constraints about how big the device may be?
+**\<endogenic>** yes
+**\<luigi1111w>** hotoatmeal no
+**\<endogenic>** :P
+**\<luigi1111w>** m2049r[m] just tote a computer around
+**\<luigi1111w>** NP
+**\<luigi1111w>** "this is my hardware wallet"
+**\<m2049r[m]>** what if we use a rpi3 to do all the work & store the caches for all the wallets onboard?
+**\<m2049r[m]>** :)
+**\<endogenic>** now we're cookin with gas
+**\<luigi1111w>** it's pretty slow too
+**\<luigi1111w>** normal client scanning on computer seems pretty ok to me
+**\<m2049r[m]>** how fast does it need to be? do we want full USB3 speeds?
+**\<luigi1111w>** by compromising your computer, the hacker now compromises just your privacy
+**\<luigi1111w>** rather than
+**\<luigi1111w>** you know
+**\<luigi1111w>** all your money
+**\<i-a>** you can run node on rp3, so it probably isnt so slow..?
+**\<hotoatmeal>** m2049r[m]: delegating the viewkey to the computer means it doesn't have to be very quick at all
+**\<luigi1111w>** i-a how long does initial sync take
+**\<hotoatmeal>** (the device / usb, that is)
+**\<luigi1111w>** how long would it take to scan a restored wallet
+**\<m2049r[m]>** that would have been the first path to explore
+**\<i-a>** luigi1111w: ok, got it:/
+**\<endogenic>** i-a no no that's just bc node is fast... because it's asynchronous (now it's my turn to troll)
+**\<luigi1111w>** is an rpi significantly better than a normal computer?
+**\<luigi1111w>** m2049r[m] if you slim the data down to close to minimum I don't think bandwidth is much concern
+**\<luigi1111w>** lemme see
+**\<m2049r[m]>** so bottleneck is always computation then. and we want it fast so we dont take forever to sync up again.
+**\<luigi1111w>** I'd guess around 240 bytes per tx
+**\<m2049r[m]>** if we keep cache on device (sdcard or whatnot) then it can be shared between clients.
+**\<luigi1111w>** so even .25MBps would overwhelm the device most likely
+**\<m2049r[m]>** 240 either way?
+**\<luigi1111w>** no just computer->**device
+**\<hotoatmeal>** another idea: put the viewkey on a separate device that's always connected to a computer
+**\<msvb-mob>** There have been some requests for SD cards, so it would be nice to try to put one on at least the developer edition board (since it has more space.)
+**\<m2049r[m]>** yes - use a viewonly wallet.
+**\<msvb-mob>** m2049r[m]: Shift devices makes quite a nice hardware wallet (Bitbox) with a SD card.
+**\<endogenic>** do you guys suppose there's any reason why this isn't a match for the mymonero lightwallet server you run alongside the daemon?
+**\<luigi1111w>** I don't
+**\<endogenic>** i might be misunderstanding
+**\<luigi1111w>** I think it's great
+**\<luigi1111w>** it's also great for existing mymonero users (privacy issues notwithstanding, of course)
+**\<luigi1111w>** but I guess we're discussing the edge of what's possible
+**\<luigi1111w>** for having a device that does basically no delegation for maximal security and privacy in all cases
+**\<m2049r[m]>** you are saying to have the device connect to an openmonero instance?
+**\<luigi1111w>** or maybe just rainbows and unicorns
+**\<endogenic>** m2049r[m]: no
+**\<endogenic>** i was envisioning some sort of stripped down protocol...vtnerd and i are working on that anyway in the api overhaul
+**\<m2049r[m]>** ok, what are you saying?
+**\<luigi1111w>** he's talking about mymonero not openmonero
+**\<endogenic>** so if you're running your own local server
+**\<luigi1111w>** though in theory they are similar
+**\<endogenic>** which is written in C++ and in the monero-cli repo alongside the official daemon
+**\<endogenic>** it almost seems like it's more a question of protocol and transport
+**\<endogenic>** that is
+**\<endogenic>** if we really are talking about delegating scanning
+**\<endogenic>** of course you have the view key disclosure tradeoff but that's why you run your own server locally
+**\<m2049r[m]>** i thought mymonero was closed source and not for anyone to run their own?
+**\<luigi1111w>** it is
+**\<luigi1111w>** but it won't be for much longer
+**\<luigi1111w>** supposedly :)
+**\<endogenic>** yep
+**\<endogenic>** vtnerd's prioritized it recently
+**\<m2049r[m]>** heh
+**\<endogenic>** he hadnt been able to before
+**\<endogenic>** too many pesky users!
+**\<endogenic>** but anyway
+**\<endogenic>** this idea does seem to overlap with simplewallet/monero-gui's job too
+**\<luigi1111w>** the theory of mymonero locally vs gui/cli is pretty similar
+**\<luigi1111w>** yes
+**\<endogenic>** does that count as a jinx?
+**\<luigi1111w>** slow motion
+**\<endogenic>** mm
+**\<endogenic>** anyway, whatever software we need, we can build
+**\<endogenic>** might be a good idea to just ask what the ideal situation is for the capabilities we have on the hardware side then fill the gaps
+**\<m2049r[m]>** we agree that we need lots of well-performing ed25519 operations on the device - no matter which road is taken?
+**\<m2049r[m]>** and possibly some form of storage (sdcard,eMMC?)
+**\<luigi1111w>** m2049r[m] more is better
+**\<luigi1111w>** but it doesn't need to be "a lot" for the delegated road
+**\<luigi1111w>** which includes basically everything that's not "do it all on device"
+**\<luigi1111w>** whether local client or some mymonero type
+**\<m2049r[m]>** signing would be on device for example - how large are the messages to be signed / verified?
+**\<luigi1111w>** it does need to be able to hash some KBs yes
+**\<luigi1111w>** 50 max, maybe
+**\<luigi1111w>** theoretically more, but shouldn't really happen anymore, in most cases
+**\<m2049r[m]>** the cec1702 has 24k of "cryptographic ram" which seems to be the ram where cryptomagic happens.
+**\<m2049r[m]>** "in most cases" - one case is enough to break it though - so for such cases we would need a software solution to kick in and have the hardware do 99% of cases.
+**\<m2049r[m]>** (this is not a problem)
+**\<m2049r[m]>** do you have a particular testcase i could run just to see how slow the current device is performing?
+**\<luigi1111w>** no I mean you can just disallow
+**\<luigi1111w>** would need some research to really know how annoying that would be though
+**\<luigi1111w>** (problem comes from having many inputs)
+**\<luigi1111w>** ((I guess mining to the wallet could cause it))
+**\<luigi1111w>** m2049r[m] well if you have ed25519 code working on it
+**\<m2049r[m]>** i do
+**\<luigi1111w>** a simple scalarmult
+**\<m2049r[m]>** regardless of parameters?
+**\<luigi1111w>** random secret key
+**\<luigi1111w>** public key needs to be valid at least
+**\<luigi1111w>** or a simple scalarmult\_base if you have that
+**\<m2049r[m]>** including convesion from/to 256-bit scalars or the mult by itself?
+**\<luigi1111w>** including
+**\<cslashm>** m2049r[m]: hotoatmeal: Yes All secret value are passed encrypted from device to PC. When PC need perform operation with those values, there are retransmitted to the device
+**\<luigi1111w>** https://github.com/monero-project/monero/blob/master/src/crypto/crypto.cpp#L127
+**\<luigi1111w>** if you can match that
+**\<m2049r[m]>** ok - like the operation need to make a public key out of a secret key (eg. viewkey)?
+**\<luigi1111w>** yes
+**\<luigi1111w>** that includes a conversion from fe to bytes at the end
+**\<m2049r[m]>** i can do that. need to add time measuring stuff.
+**\<m2049r[m]>** will do that tomorrow and get back with results.
+**\<luigi1111w>** cool
+**\<luigi1111w>** might as well do arbitrary base too if it's not much more work
+**\<luigi1111w>** https://github.com/monero-project/monero/blob/master/src/crypto/crypto.cpp#L127
+**\<luigi1111w>** you can use any valid point for the pubkey param
+**\<luigi1111w>** I can give you one in hex if you want
+**\<luigi1111w>** or you can just gen one from the above function
+**\<m2049r[m]>** will pm you for more details
+**\<m2049r[m]>** cslashm: what encryption is used for the transmission of the keys over usb?
+**\<cslashm>** It will be AES128
+**\<cslashm>** the key will new at each app usage and dedicated to session when transfer is performed
+**\<cslashm>** But I try to send even encrypted the view and spend key
+**\<cslashm>** *not send*
+**\<m2049r[m]>** and the key exchange is DH?
+**\<cslashm>** which DH? The AES key never leave the device
+**\<m2049r[m]>** maybe i dont understand aes. isnt that symmetric? how does the pc decode the ciphertext?
+**\<cslashm>** PC never decode, I try to explain
+**\<luigi1111w>** he's using the pc for encrypted cache only it sounds like
+**\<luigi1111w>** but I don't think you need to send spend key ever
+**\<luigi1111w>** device has enough memory for that, surely
+**\<cslashm>** voila. PC is just a encrypted holder
+**\<cslashm>** The advantage is that it keep the secret at the right place
+**\<m2049r[m]>** a storage.
+**\<cslashm>** for exemple in RCT, it request n secret key, store in the right vector place, and when it use it, it resend the encrypted secret key to device, which decrypt and do the op
+**\<cslashm>** @luigi1111w: yes spend/view key never leave the device
+**\<cslashm>** I use special value 00..00 and FF...FF for them on PC side
+**\<m2049r[m]>** ok, gotta go - it's been great :)
+**\<cslashm>** basic idea is to hav no memory restriction, on easly follow the PC code evolution with minimal code device modification
+**\<cslashm>** *and easly* (end of day in FR :) )
+**\<dEBRUYNE>** cslashm: I've been wondering. Did you run any performance tests? For example, how long does it take to scan / refresh 10k blocks?
+**\<cslashm>** for now it's a OMG part
+**\<cslashm>** I start some perf test yes but didnot remenber
+**\<dEBRUYNE>** Approximately? :p
+**\<cslashm>** It is just impossible to rescan the whole blockchain
+**\<cslashm>** holdon, deep search in paper on my desk
+**\<dEBRUYNE>** Yeah, but that won't be necessary for 99% of the users :P
+**\<cslashm>** 10 min for 20 000 block, but app in -0O and level 4 log
+**\<cslashm>** wallet cli also in O0
+**\<dEBRUYNE>** I see, that doesn't seem too bad tbh
+**\<luigi1111w>** that is scanning by cli, not ledger, right?
+**\<cslashm>** Its acceptable if you dont move in vacation for 1 month without refresh :D
+**\<cslashm>** no wallet cli scan the bc but delegate all keyderivation/keyimage computation to ledger to no disclose the view key
+**\<dEBRUYNE>** well, 1 month is 22k blocks give or take
+**\<cslashm>** So for each block, device compute some scalmul and hash
+**\<dEBRUYNE>** So that'd be 10 minutes wait
+**\<luigi1111w>** you can't really use blocks
+**\<luigi1111w>** you have to use txs
+**\<luigi1111w>** are those current numbers
+**\<luigi1111w>** what will it look like if usage goes up (which it historically has)
+**\<luigi1111w>** I personally don't really see a lot of benefit for disclosing the viewkey
+**\<cslashm>** yes for each txes. basically scan involves get\_key\_derivation and generate\_key\_image, those two op are done by the device. The rest is done by the PC as usual
+**\<cslashm>** view key is so never disclose
+**\<cslashm>** So, I need to leave. Be back on monday. you can mail, PM reddit or put githib issue if you need long tech desc
\ No newline at end of file
diff --git a/_posts/2018-01-14-logs-for-the-dev-meeting-held-on-2018-01-14.md b/_posts/2018-01-14-logs-for-the-dev-meeting-held-on-2018-01-14.md
new file mode 100644
index 0000000000000000000000000000000000000000..ff0a12f7cb8a58ce7c04f9174416452ce55f126b
--- /dev/null
+++ b/_posts/2018-01-14-logs-for-the-dev-meeting-held-on-2018-01-14.md
@@ -0,0 +1,412 @@
+---
+layout: post
+title: Logs for the Dev Meeting Held on 2018-01-14
+summary: Discussion of open PRs and issues, Bulletproofs, March HF, and miscellaneous
+tags: [dev diaries, core, crypto]
+author: dEBRUYNE / fluffypony
+---
+
+# Logs
+
+**\<rehrar>** https://github.com/monero-project/meta/issues/157
+**\<rehrar>** Here's the agenda.
+**\<rehrar>** We kinda did greetings, but if anyone else is present, please say "hi"
+**\<gingeropolous>** hi
+**\<jtgrassie>** hi!
+**\<pigeons>** hi!
+**\<Maxithi>** hi
+**\<pebx>** hi
+**\<ferretinjapan>** hi
+**\<binaryFate>** hi
+**\<rehrar>** alright, so let's get started then!
+**\<rehrar>** 2. Brief review of what's been completed since the previous meeting
+**\<rehrar>** Anyone have anything exciting or fun to report since our last meeting a month ago?
+**\<rehrar>** Get any fun gifts for the holidays maybe?
+**\<Maxithi>** 24 commits 4 days ago.
+**\<Maxithi>** On the main core. Nothing special. Maybe a little cheering for cslashm and hist first Ledger PR.
+**\<endogenic>** well we've made some progress with apple, fyi … confirmed there was an account mixup on their side with a human being and we're finally getting that sorted. will update you all as i hear things
+**\<rehrar>** that IS pretty exciting Maxithi
+**\<endogenic>** have to submit some docs, etc
+**\<hyc>** nothing much to report here
+**\<sgp>** hi
+**\<rehrar>** endogenic dude, that's gotta be thrilling to get some news finally
+**\<rehrar>** ArticMine, do you want to speak briefly about Kiev?
+**\<endogenic>** rehrar yeah i mean these things usually happen instantly so once i called them they were like yeah that's no good let'sget that sorted
+**\<ArticMine>** Sure, but it is not really dev related
+**\<rehrar>** just a brief four sentence thing should be alright
+**\<vtnerd>** after a discussion with luigi1111, I should be proposing an optimization for wallet scanning that mymonero is using - want to test with a standard wallet to give real world perf numbers before PR
+**\<vtnerd>** ah sorry ArticMine
+**\<rehrar>** no, go ahead vtnerd :) anyone and everyone with an update feel free to let us know
+**\<vtnerd>** ok, this optimization is separate from the ASM work in monero-project/supercop (still pending a PR), so it works with standard ref10 (i.e. all platforms)
+**\<vtnerd>** it will require a few changes to src/crypto.{h|c} so be on the lookout for that PR
+**\<gingeropolous>** is this just for your standard refresh? or related to remote viewkey scanning... or both?
+**\<vtnerd>** this is specifically for scanning receiving outputs on a primary address
+**\<vtnerd>** it does not benefit subaddresses, but does benefit simplewallet / GUI / anyone doing viewkey scanning
+**\<medusa>** lets talk about the elephant in the room ? bulletproof is in all varieties on testnet
+**\<rehrar>** Alright. Thanks. :) Anyone else? If not we'll move on.
+**\<rehrar>** Ye, that's next.
+**\<moneromooo>** Things of note since last time: build hardening (currently breaks static builds though), DNSSEC fix on windows, DB and sync hang fixes, secure memory wiping (wip), misc code review and fixes, updates now use HTTPS and can resume downloads
+**\<ArticMine>** In brief I attended BTC awards CIS and participated in the coins panel. There were two other coins present Dash, ZenCash. Overall it went very well and provided exposure to Monero among the CIS (Commonwealth of Independent state) crypto communities
+**\<endogenic>** medusa: last i heard MRL was looking for people to review and audit bulletproofs
+**\<endogenic>** sarang would be able to give you more information
+**\<ArticMine>** That is my brief update
+**\<ArticMine>** Whan it comes to bullteproof this has to move to September
+**\<endogenic>** moneromooo: beast mode
+**\<rehrar>** ArticMine, care to elaborate?
+**\<moneromooo>** Not all of this by me fwiw.
+**\<hyc>** Interesting ArticMine - CIS already has monero experience, thru the Karbo clone in Ukraine
+**\<medusa>** GUI is merging sub addresses finally, dsc is working on the black theme sucessfully and we hope to go live in march with 2 progress bars instead of 1 (sync and refresh separated). also we added a "change password" feature to the GUI
+**\<ArticMine>** FP spoke with Pieter Wuille who is recommending September
+**\<sarang>** Jumping in for any questions about BPs that I can answer
+**\<ArticMine>** Is there a plan for further review?
+**\<ArticMine>** of B
+**\<sarang>** Yes
+**\<ferretinjapan>** Are there any showstoppers on bullteproofs that would justify moving back rolling it out?
+**\<sarang>** Initiating contact w/ an audit group that fluffypony knows
+**\<sarang>** It's not fully clear what their scope of review can be, but I will find out shortly on a phone meeting with them
+**\<sarang>** The goal being additional third-party review
+**\<hyc>** ferretinjapan: there's no known problems. additional review is being planned to avoid unknown problems
+**\<rehrar>** Yeah, so we naturally moved onto third item on the agenda, which is code freeze, March hard fork. Bulletproof is the biggest one. Everyone's thoughts?
+**\<binaryFate>** beyond code review, sarang what is your opinion on the need of review of the math itself? I'm worried the paper has little time to go through peer-review. But maybe match checks out so obviously that it's not needed.
+**\<sarang>** The math is solid. Additional peer review is always a welcome thing, though with diminishing returns over time
+**\<binaryFate>** (talking about the BP paper -- not the Monero specific implementation)
+**\<sarang>** yes
+**\<sarang>** In the meantime, moneromooo and I have been working on some additional optimizations for proof verification that are independent of the math or specific proof implementation
+**\<ferretinjapan>** I guess thats the thing, how much "value adding" is an additional audit for now justified?
+**\<binaryFate>** nice
+**\<sarang>** We've had a select number of informal reviews
+**\<sarang>** but no formal third-party review yet
+**\<ArticMine>** ... but still this warrants a delay to September for BP
+**\<sarang>** To get the review done? Almost certainly
+**\<sarang>** The advantage to the delay is that we could bypass single-output BPs altogether
+**\<sarang>** figure out the multi-output fee structure, and release that
+**\<medusa>** multi output for march is a non option ?
+**\<sarang>** Correct
+**\<ferretinjapan>** seems incredibly wasteful :/
+**\<sarang>** It requires a change to the way fees are computed
+**\<hyc>** I'm in favor of skipping single-output. would be a lot of work for a very short-lived feature.
+**\<sarang>** Yes, though single-output proofs will verify with the multi-output code with no changes
+**\<ferretinjapan>** you'd be better served making sure that there is a fallback to BP instead of pushing back entirely.
+**\<rbrunner>** Isn't the work almost all done anyway?
+**\<ferretinjapan>** this is a classic case of perfect being the enemy of good.
+**\<endogenic>** realized we didnt ping anonimal
+**\<sarang>** We have multi code working now
+**\<sarang>** it's not in testnet yet
+**\<sarang>** and we don't have consensus about the fee structure
+**\<hyc>** ^^
+**\<binaryFate>** I lean towards satefy in general. The ringct bug was close enough
+**\<Maxithi>** hyc Same, better safe than sorry.
+**\<iDunk>** Agreed.
+**\<dEBRUYNE>** sarang: have you considered contacting the paper authors for review?
+**\<gingeropolous>** ferretinjapan, the push to sept is about additional code review, not really about multiout
+**\<dEBRUYNE>** \<binaryFate> I lean towards satefy in general. The ringct bug was close enough \<= I can't survive another mini heart-attack probably
+**\<sarang>** We've had informal review from one author, but the other authors are working on other implementations and I would not rely on them for a speedy review
+**\<hyc>** I suggested soliciting reviews on the Cryptography email list
+**\<endogenic>** nice idea
+**\<hyc>** could also solicit reviews on twitter
+**\<dEBRUYNE>** But presumably they would have some time somewhere between now and August?
+**\<endogenic>** that too
+**\<dEBRUYNE>** \^ sara
+**\<dEBRUYNE>** sarang\*
+**\<sarang>** hyc: are you ok with making such a solicitation?
+**\<sarang>** I could certainly try the other paper authors just in case
+**\<moneromooo>** bypass single-output BPs is not an advantage.
+**\<hyc>** Yes, can do. we need to decide if we'll offer a payment
+**\<sarang>** though they are much more of a long shot
+**\<moneromooo>** bypassing
+**\<ferretinjapan>** gingeropolous, yes, but noones really given a definitive reason to delay except for an overabundance of caution, and by then it'll be unnecessary to even release. :/
+**\<endogenic>** is there a blurb/call-to-actionabout the request to review which i can pass to my relevant mailing lists?
+**\<hyc>** moneromooo: waiting till sept means we can settle on the fees without rushing
+**\<sarang>** hyc: fluffypony indicated we could make funds available for the review, but you'll have to ask him for the details
+**\<moneromooo>** It's not a lot of work, since it exists now.
+**\<ArticMine>** We are only delaying single output not multi output
+**\<moneromooo>** Multi output bulletproofs are in C++, but not plugged into the consensus, which is the annoying part.
+**\<sarang>** Anyone interested in doing a review and wanting details can contact me at sarang.noether@protonmail.com
+**\<endogenic>** such as indicating where to look in the code or repo, background docs, review process, submission format, etc?
+**\<hyc>** endogenic I'll start drafting an email announcenemt
+**\<sarang>** I'll contact the other paper authors separately
+**\<sarang>** and will still press on with the audit group to see what their scope is
+**\<luigi1111w>** there's not much work saved by skipping single output BP
+**\<moneromooo>** waiting till sept does not change anything for fees, since multi out is september anyway.
+**\<luigi1111w>** but the review time is too close for my comfort for march
+**\<luigi1111w>** I think that's the general thought anyway though
+**\<hyc>** alternatively we could delay the March release into April
+**\<sarang>** fluffypony was very opposed to that idea hyc
+**\<hyc>** ok
+**\<ferretinjapan>** could always push back the march hard fork a month or two like last time for RCT.
+**\<sarang>** not saying that's the deciding factor though
+**\<luigi1111w>** rct was pushed forward actually
+**\<rbrunner>** What's fp's main argument?
+**\<ferretinjapan>** oops, I c.
+**\<sarang>** He thought that regular releases were an advantage
+**\<rehrar>** he says that people are getting used to the hard fork schedule
+**\<sarang>** due to predictability
+**\<endogenic>** rbrunner: for?
+**\<ferretinjapan>** rbrunner, probably his snity ;)
+**\<ferretinjapan>** \*sanity
+**\<rbrunner>** Against the 1 month delay
+**\<luigi1111w>** my own shed says 3 months with fork in June :D
+**\<endogenic>** bc it c hanges the hard fork periodicity etc
+**\<endogenic>** guessing
+**\<rehrar>** I think six months is not super long to wait for bulletproofs. It'd be another thing entirely if we were discussing putting it off for a year or so, but not much is lost by being a bit safe and waiting.
+**\<gingeropolous>** ^^
+**\<ferretinjapan>** 6 months is a looong time in crypto
+**\<luigi1111w>** did someone mention future pruning
+**\* luigi1111w** runs
+**\<sarang>** sigh
+**\<gingeropolous>** future pruning? you mean double blob?
+**\<endogenic>** ferretinjapan: better than there being no crypto bc we broke it
+**\* gingeropolous** runs
+**\<sarang>** People also want Lower Fees Now
+**\<sarang>** (tm)
+**\<vtnerd>** we all want ponies sarang
+**\<sarang>** or at least, a vocal minority does
+**\<dEBRUYNE>** \<rehrar> he says that people are getting used to the hard fork schedule \<= I doubt most of the economically sensitive nodes are aware of our schedule
+**\<ferretinjapan>** endogenic, touche, but there comes a point wher you gain nothing by waiting.
+**\<ErCiccione>** I think in this phase keeping the scheduled 6 months shouldn't be a priority. Agree with dEBRUYNE
+**\<rehrar>** If we were to push back by two months from March to May, would that be a good compromise in people's opinions?
+**\<luigi1111w>** no, but 3 months from March to June.....
+**\<sarang>** If we really want additional review, the timeline will need to be flexible to the reviewers
+**\<gingeropolous>** but not rushed
+**\<Maxithi>** I'd rather have 3 months than 6.
+**\<sarang>** academic review can be a frustratingly slow and unpredictable process
+**\<rehrar>** ok, from March to June then
+**\<endogenic>** i agree with sarang, we cant dictate when third parties deliver
+**\<iDunk>** This just looks like a repeat of the last meeting.
+**\<sarang>** basically
+**\<luigi1111w>** iDunk :)
+**\<rehrar>** it basically is :P
+**\<endogenic>** we also dont have enough info to know how long sufficient reviews would take at this stage
+**\<endogenic>** so not sure it's a good idea to judge things yet
+**\<ferretinjapan>** rehrar, I think so, but I think it's important to be realistic, rushing is bad I'll admit (we don't want stressed devs!), but unnecessarily putting it off is also bad
+**\<dEBRUYNE>** 8 months seems like ample time though
+**\<rehrar>** hard part of being decentralized with no leader is that consensus on stuff is hard
+**\<ArticMine>** Why not go ahead with March and if BP is ready then to an early September HF? for BP
+**\<endogenic>** oh yeah what about the meeting agenda?
+**\<luigi1111w>** well there's really nothing left for march
+**\<sarang>** Maybe best to wait to hear about potential reviewer interest
+**\<sarang>** otherwise this is all moot
+**\<luigi1111w>** but we can fork anyway to keep schedule
+**\<sarang>** a totally moo point
+**\<rehrar>** how long do we wait though, since code freeze is soon?
+**\<sgp>** Why not plan a hardfork a month after the BP review is ready, whenever that is?
+**\<endogenic>** mooot\*
+**\<ArticMine>** Multisig is in March
+**\<luigi1111w>** not forking
+**\<rehrar>** Multisig doesn't require a hard fork though
+**\<dEBRUYNE>** Multisig doesn't require a hard fork though
+**\<luigi1111w>** but in release yes
+**\<dEBRUYNE>** lol
+**\<luigi1111w>** you guys
+**\<rehrar>** lel dEBRUYNE
+**\<endogenic>** what the
+**\<rehrar>** of one mind
+**\<gingeropolous>** but still could provide bugs to squash
+**\<endogenic>** just got the heebies
+**\<dEBRUYNE>** bots rekt
+**\<pebx>** so we don't need any hard fork in march without bp?
+**\<ferretinjapan>** sgp, I think thats a solid idea, but "consistency" may be a factor in that.
+**\<luigi1111w>** pebx part of the idea of scheduled forks is to do them anyway
+**\<rehrar>** can we go through the rest of the meeting and come back to this topic?
+**\<sgp>** I think the rewards are so large it's worth considering breaking consistency
+**\<rehrar>** just so we make sure everything else gets done?
+**\<rehrar>** then we can discuss till the end of time at the end
+**\<luigi1111w>** or 1hr, whichever is less
+**\<endogenic>** rehrar: what are you, some kinda pragmatist?
+**\<ferretinjapan>** luigi1111w, noone said anything about FIXED schedules ;)
+**\<gingeropolous>** sgp, indeed, that was the logic begind the earlier than planned ringct fork
+**\<rehrar>** Some people gotta go or don't want more than an hour
+**\<luigi1111w>** lol
+**\<dEBRUYNE>** What else is there to discuss though
+**\<endogenic>** dEBRUYNE: how about what kind of soda you're going to get for rehrar?
+**\<iDunk>** Subaddresses and fees for the next fork.
+**\<rehrar>** *shrug* screw the agenda then. We're not beholden to it right. ;) Just trying to think of people who might want to discuss code or issues.
+**\<ArticMine>** I do not see a fee change without BP
+**\<pebx>** i'm not a mathematician, however i would prefer single output bp in march/april/may than waiting for multi output with the even more controversial change in fee structure
+**\<iDunk>** Even if the value has gone up ~40x since the last adjustment ?
+**\<endogenic>** rehrar: dont be silly, no one wants to discuss issues… :P
+**\<rehrar>** troo, ok BP it is
+**\<sarang>** pebx: the fee change shouldn't be that controversial
+**\<luigi1111w>** ArticMine smooth had some arguments for reducing fee
+**\<sarang>** the alternative is DOS
+**\<rehrar>** How soon should we be looking to come to a decision? This meeting? Next?
+**\<rbrunner>** What is DOS?
+**\<Maxithi>** endogenic: rehrar: dont be silly, no one wants to discuss issues… :P \<= I do, please label them so I don't have to make lists and have dEBRUYNE tag 150 of them at once ;)
+**\<endogenic>** rbrunner: denial of service?
+**\<rbrunner>** Regarding fees?
+**\<ArticMine>** WE can lower the min fee but people are not using it anyway
+**\<endogenic>** i.e. spam?
+**\<serhack>** hi
+**\<dEBRUYNE>** For the current range proofs you'd need to tweak the penalty
+**\<luigi1111w>** not gonna happen
+**\<luigi1111w>** by march
+**\<ArticMine>** Spam to the txpool is a risk if we go too low on the min fee
+**\<dEBRUYNE>** What's not going to happen by march luigi1111w?
+**\<luigi1111w>** tweaking the pentaly
+**\<pebx>** @ArticMine most users don't know about a minimum fee...
+**\<luigi1111w>** penalty
+**\<pebx>** I see this all day in the Telegram groups "why is the fee so high?"
+**\<ArticMine>** One option change the wallet default to the min fee
+**\<dEBRUYNE>** The per kB fee isn't even that high fwiw
+**\<pebx>** most services also use the default... like mymonero does
+**\<dEBRUYNE>** The transactions are just obscenely large
+**\<endogenic>** pebx: dont worry, i'm getting close to adding priority setting to new apps
+**\<pebx>** dEBURNE isn't that why bp is so important?
+**\<dEBRUYNE>** Right, but we shouldn't rush it
+**\<Maxithi>** @ArticMine: One option change the wallet default to the min fee \<= I actually consider that a good idea as no one uses that fee...
+**\<ErCiccione>** ^^
+**\<dEBRUYNE>** That's going to result in a clogged mempool if we want to expand
+**\<luigi1111w>** I use that fee
+**\<moneromooo>** Then noone would use the current fee once it's no longer the default.
+**\<iDunk>** So do I.
+**\<luigi1111w>** well I use both kinda depending
+**\<jtgrassie>** BP shoudnt be rushed but equally shouldnt be held back to a *schedule*
+**\<luigi1111w>** dEBRUYNE some of that is unavoidable
+**\<Maxithi>** Yeah but I mean none of the people here do used it. That's the issue
+**\<luigi1111w>** two opposing forces at work
+**\<rbrunner>** It's nice to have a fee level below default to be able to say "I can wait"
+**\<dEBRUYNE>** luigi1111w: According to smooth miners will just pick the default or higher fees and leave everything else in the mempool
+**\<dEBRUYNE>** Because they can only use the last transaction for the penalty
+**\<luigi1111w>** well I'm pretty sure that was originally according to me :)
+**\<dEBRUYNE>** So you can't have 23 min fee txes and then one default
+**\<binaryFate>** \<ArticMine> One option change the wallet default to the min fee \<-- +1
+**\<endogenic>** isn't that a bad idea? \^
+**\<moneromooo>** It is.
+**\<luigi1111w>** it's an idea
+**\<luigi1111w>** I'm not sure if it's bad or good
+**\<moneromooo>** Unless people don't use monero much for half a year.
+**\<endogenic>** hm it would be cool to model this
+**\<Maxithi>** got to go, see you guys
+**\<endogenic>** but Maxithi you didnt get to chat issues
+**\<luigi1111w>** sorry I got lunch gotta run too
+**\* luigi1111w** grumbles about meeting time, again
+**\<ArticMine>** It is the human herd mentality
+**\<Maxithi>** endogenic Yeah never mind, just wanted to ask people to label more issues to make it easier to know which one require assistance.
+**\* Maxithi** agrees with luigi1111w
+**\<dEBRUYNE>** What if the wallet changes the level dependent on the backlog?
+**\<endogenic>** Maxithi: maybe you could make an issue about that?
+**\<dEBRUYNE>** So it'd use min fee if mempool is \< 1000 kB and default if \> 1000 kB?
+**\<dEBRUYNE>** \^ just using arbitrary numbers
+**\<rbrunner>** Wouldn't that just result in a lot of angry people, like "Why the hell I paid so much"?
+**\<rbrunner>** If you don't make it *very* transparent
+**\<ArticMine>** dEBRUYNE What if the wallet changes the level dependent on the backlog? \<--- That would work
+**\<dEBRUYNE>** rbrunner: How so?
+**\<hyc>** endogenic, sarang: email draft https://pastebin.mozilla.org/9075994
+**\<dEBRUYNE>** You can add a note in the wallet
+**\<pebx>** isn't that even more confusing for users?
+**\<dEBRUYNE>** "changing fee level because of backlog"
+**\<rbrunner>** I am afraid people would not understand the mechanism
+**\<rbrunner>** compare fees, see that they are different for different people
+**\<rbrunner>** or different times
+**\<rbrunner>** and shout "scam" or so ...
+**\<ArticMine>** It is what Bitcoin does
+**\<endogenic>** hyc: term "output" used before definition
+**\<dEBRUYNE>** That seems a bit too far stretched
+**\<rbrunner>** Well, people now even don't "understand" they can go one level lower for the fee, right?
+**\<sarang>** hyc: I didn't see any Java code from the authors. I wrote our Java proto code
+**\<rbrunner>** Many of them, anyway
+**\<DaveyJones>** rbunner i don't think so ... most people arn't even schooled on default vs 0.25x fee
+**\<sarang>** hyc: line 5, I'd say "are confident" instead of "are pretty confident"
+**\<hyc>** sarang: ok
+**\<endogenic>** hyc: maybe capitalize 'Java' and add a 'Therefore, ' before "The Monero Project"
+**\<rbrunner>** Yes, how will they understand how that works if it get more complicated?
+**\<rbrunner>** That's my fear, basically
+**\<endogenic>** oops
+**\<endogenic>** "mainnet. The Monero Project"
+**\<rehrar>** I'm torn tbh. I see both sides.
+**\<pebx>** @ArticMine what bitcoin does is one of the major reasons, why people are looking into Monero... fees are one thing the average bitcoin user is always confused about
+**\<DaveyJones>** basically they don't need to understand most of people moaning about tax fee's are people just count the $ value of the fee... not how it was achieved
+**\<endogenic>** otherwise looks great, tyvm!
+**\<DaveyJones>** so they basically dont care about the mechanism but the price
+**\<DaveyJones>** and wasnt the proposed mempool fee sth that should happen automatic? or did i misunderstand that
+**\<ArticMine>** pebx Bitcoin has fundamental fee problems that have nothing to do with wallet choices.
+**\<sarang>** hyc: maybe state that we "recognize the value of independent third-party review" to assure other readers that we're doing this as a "belt and suspenders" approach, rather than a legitimate worry about correctness
+**\<binaryFate>** pebx Bitcoin is a clusterfuck of floating fees and fees competitiong for a fixed block size. Here it's just about choosing the default among the 4 different levels, that's it. Then flex block cap takes care of the rest so you don't have your transaction in mempool for 14 days
+**\<sarang>** I don't want some silly media report that we don't trust our own code
+**\<jtgrassie>** IMO default fees should derived from mempool size and be completely transparent to user
+**\<endogenic>** but sarang mass media never selectively reports
+**\<sarang>** -\_-
+**\<endogenic>** that wouldn't be true journalism!
+**\<ArticMine>** It can be done at he wallet level.
+**\<binaryFate>** It's just silly that when there is factually no backlog in the mempool, the fee does not default to low
+**\<rbrunner>** Can the wallet query tx pool size already?
+**\<endogenic>** binaryFate: simplewallet does warn at least
+**\<rbrunner>** Technically, is there a call?
+**\<endogenic>** "n block backlog at that fee"
+**\<endogenic>** oh, next meeting when? 2 wks?
+**\<sarang>** endogenic: I want to make it clear that we're taking a careful but confident approach that uses peer review, just as any good academic work does
+**\<rehrar>** It was suggested earlier that if single output BP's are not merged in March, that the fee should be adjusted. If we are saying that we don't want to adjust the fee in March, I think single output BPs should be merged
+**\<endogenic>** sarang: i completely agree
+**\<jtgrassie>** 13:02 **\< endogenic>** oh, next meeting when? 2 wks?
+**\<rehrar>** Ye, sorry. If anyone needs to leave. Next meeting two weeks.
+**\<rehrar>** 28th
+**\<binaryFate>** The warn makes people think "mmm should I use more fees", not the opposite. Who when using normal and seeing 0/1 block backlog cancels, and come back to use low fees? Nobody I guess, should be automatic maybe with just a y/n confirmation
+**\<sarang>** hyc endogenic: move discussion of BP review to #monero-research-lab after meeting?
+**\<endogenic>** yes good point
+**\<endogenic>** binaryFate
+**\<hyc>** ok
+**\<endogenic>** though i dont know about automatic, from a ux standpoint, but thats just me
+**\<rbrunner>** Automatic always takes away some choice, right?
+**\<endogenic>** not necessarily
+**\<endogenic>** if the result is displayed clearly so the user can confirm before implicitly agreeing
+**\<endogenic>** then it can be ok
+**\<endogenic>** question is
+**\<endogenic>** how do you do that in a CLI?
+**\<binaryFate>** What we're discussing is just selecting the default, not forcing the user
+**\<endogenic>** may end up needing some kind of prompt or to enhance it to update some kind of display in-place
+**\<endogenic>** yes
+**\<endogenic>** must be off, myself
+**\<endogenic>** o/
+**\<rehrar>** Can we maybe plan an "urgent" meeting sometime this week or next weekend?
+**\<rehrar>** Just to discuss BP's and make a decision?
+**\<endogenic>** rehrar i'll attend any meetings
+**\<rehrar>** Or is that not a good idea.
+**\<sarang>** rehrar: Do we want to wait on review feedback?
+**\<rbrunner>** It seems BP might merit that, a special meeting
+**\<sarang>** To at least see who if anyone will review?
+**\<endogenic>** sarang: personally i would
+**\<rehrar>** Sarang, do we have an ETA on that?
+**\<DaveyJones>** BP + fee talk ?
+**\<ArticMine>** I am fine with that say next Sunday
+**\<DaveyJones>** i guess both run a little short today
+**\<endogenic>** or else i would hold the meeting with the primary objective of resolving how we can solicit and accomplish the review
+**\<DaveyJones>** and need more thoughts
+**\<sarang>** rehrar: I have a phone meeting w/ the audit group on Tuesday
+**\<rehrar>** Perfect.
+**\<sarang>** I assume hyc can post the Call For Reviews after we finish proofreading it
+**\<rehrar>** I can make an issue depending on that.
+**\<sarang>** and I'll contact the other paper authors today
+**\<rehrar>** I will put a "tentative" next meeting for next Sunday
+**\<sarang>** roger
+**\<rbrunner>** Sounds good
+**\<rehrar>** And if anything changes, I'll change it.
+**\<sarang>** I'll post any updates on the research IRC as I hear back
+**\<rehrar>** You can comment on the GitHub issue too plz.
+**\<sarang>** sure thing
+**\<rbrunner>** I am sure companies would arrange meetings of whole days for something of the importance of BP
+**\<rbrunner>** Just saying :)
+**\<rbrunner>** Just to reach consensus
+**\<rehrar>** Good idea rbrunner. 4 hour meeting planned. Followed by a small snack break. Then another four hours.
+**\<rbrunner>** :)
+**\<ErCiccione>** can we talk about code freeze now? I really need to know the date for both the localization team and the GUI guide that will go in the binaries
+**\<rehrar>** Harder to discuss now that lots of people are gone unfortunately. :/
+**\<rehrar>** BPs took most of the time.
+**\<rbrunner>** With breakthrough still somewheat elusive, if you ask me ...
+**\<rbrunner>** But maybe that's a good thing.
+**\<ErCiccione>** rehrar: yep..but that mess things up a bit for me. still around mid February btw, right?
+**\<rehrar>** rbrunner, shows we're actually decentralized?
+**\<rehrar>** Dunno erciccione, I think it was supposed to be January, but don't quote me.
+**\<rbrunner>** rehrar: Yes.
+**\<sgp>** iirc it's supposed to be 2 months
+**\<sgp>** Before the hf
+**\<rbrunner>** Was one of the important points of fp's speech in Zurich that I could attend. Impressed folks, I think
+**\<ErCiccione>** rerhrar: it was, but last time i asked dEBRUYNE he said more or less around February. i guess i'll just wait to know more
+**\<binaryFate>** rbrunner what point?
+**\<sgp>** I think it's a good idea
+**\<rbrunner>** The good decentralization of Monero
+**\<binaryFate>** ErCiccione as long as hard fork date still somewhat open and discussed, I think it's fair to assume code freeze will not happen soon. That's probably the most you can get now.
+**\<sgp>** I think some localization stuff is low-risk though and could be merged a bit later as long as the binaries can be built with sufficient time. Not my deceion though
+**\<Billy>** I do think we need to resolve the BP issue ASAP. It needs a special meeting because these general meetings aren't going to do it.
+**\<rbrunner>** You could say that after two regular meetings, yes
+**\<rbrunner>** 1 hour is damn short, even if we don't have to emulate endless corporate meetings
+**\<ErCiccione>** ok, thanks binaryfate sgp the problem is that some translator keep asking that because they need to organize their time, but they don't want their work to be left out from the official release
\ No newline at end of file
diff --git a/_posts/2018-01-20-logs-for-the-Community-meeting-held-on-2018-01-20.md b/_posts/2018-01-20-logs-for-the-Community-meeting-held-on-2018-01-20.md
new file mode 100644
index 0000000000000000000000000000000000000000..3a9bd66091053a55eab17d28feb5329e50f49d42
--- /dev/null
+++ b/_posts/2018-01-20-logs-for-the-Community-meeting-held-on-2018-01-20.md
@@ -0,0 +1,243 @@
+---
+layout: post
+title: Logs for the Community Meeting Held on 2018-01-20
+summary: Community highlights, Forum Funding System updates, RFC-HWALLET-1, Kasisto, open ideas, and miscellaneous
+tags: [community, crypto]
+author: dEBRUYNE / fluffypony
+---
+
+# Logs
+
+**\<rehrar>** For newcomers, or those who don't know. The community meeting is a place where individuals or groups interested in making the Monero community a better, more helpful, more welcoming, and fun place can congregate and throw ideas around.
+**\<rehrar>** We've already sort of gone through 1. Greetings, but if there is anyone else out there in the peanut gallery that wants to say 'hi' and show your presence, by all means do so.
+**\<keledoro>** Heya!
+**\* ErCiccione** here but sick and getting worse, not going to be very communicative :(
+**\<rehrar>** you probably caught it from anonimal :/
+**\<vdo>** hi
+**\<suraeNoether>** howdy y'all
+**\<rehrar>** 2. Community highlights
+**\<vdo>** on mobile but here
+**\<rehrar>** You can see the Monero Observer for a good breakdown of what's happened in the past two bits of time since we've had our last meeting.
+**\<ErCiccione>** rehrar: lol. yeah, that germ spreader
+**\<rehrar>** But is there anything anyone wants to highlight in particular about the past couple weeks in regards to cool stuff our community (not necessarily just this workgroup) has done?
+**\<msvb-mob>** The Monero Observer is where? It sounds like revuo but is not.
+**\<rehrar>** http://monero-observer.com/
+**\<rehrar>** Observer is here, and covers more the day to day of Monero
+**\<serhack>** We are going to reach 100k subreddit users :O
+**\<cryptochangements>** the new Cake Wallet is out, and the dev intends to release source so that's exciting
+**\<rehrar>** The Revuo is coming! Promise. Just had to push back a bit since anonimal has been sick, but we're working on the Kovri part (the last part) this weekend hopefully.
+**\<rehrar>** Yes, I invited the Cake Wallet guys to the community meeting here when I chatted with him yesterday
+**\<rehrar>** hopefully he'll show :) He got on the mattermost
+**\<suraeNoether>** the community sent me to attend the conference RealWorldCrypto in Zurich, where I met up with Fluffypony, andytoshi, Peter Wuille (spelling?)
+**\<suraeNoether>** and is sending me and sarang to BPASE18 next week, too
+**\<onetwo22>** http://monero-observer.com/Monero%20Observer%20-%20Vol%2001%20No%2020.html
+**\<rehrar>** brief four sentences on your time in Zurich suraeNoether?
+**\<suraeNoether>** which is a really fantastic thing our community has done
+**\<monerodesigns>** oh, I'm featured in the Monero Observer :) nice. didn't even know this exists. cool project
+**\<rehrar>** oyoy, alright, we'll move on then :)
+**\<suraeNoether>** I attended Andrew Poelstra's talk (andytoshi) on MimbleWimble and scriptless scripts, which was the first talk of the conference that had any serious math in it, terrifying the venture capitalists. Fluffypony and I met up with several of the team members at Digital BitBox, a hardware wallet company that is doing some truly fantastic work, as well as the Operations Manager from Globee. The week was
+**\<suraeNoether>** productive, as andytoshi and I were able to discuss in person at least one idea I had for a rather crude refund transaction mechanism that could work in Monero. It was an honor to meet so many members of the cryptocurrency community, and it was fantastic to make new friends!
+**\<rehrar>** \^ thank you so much suraeNoether
+**\* suraeNoether** thumbs up
+**\<dEBRUYNE>** suraeNoether: BitBox is a hw wallet right? Did they have any intention to add Monero?
+**\<msvb-mob>** Shift Devices is now local to Zurich.
+**\<serhack>** cool suraeNoether!
+**\<suraeNoether>** dEBRUYNE: yes, monero stickers everywhere~
+**\<emesik>** transaction refund? sounds interesting
+**\<rehrar>** 3. FFS updates
+**\<msvb-mob>** dEBRUYNE: They want to add Monero and have no plans to add Monero (at the same time.)
+**\<rehrar>** Start with hardware wallet? msvb-mob, you wanna give us a thing or two?
+**\<msvb-mob>** Okay.
+**\<suraeNoether>** msvb-mob +1 yep exactly
+**\<msvb-mob>** We've made considerable progress in Firmware.
+**\<msvb-mob>** And USB logic, including obtaining Product IDs (provisionary.)
+**\<msvb-mob>** Work is ongoing to test a more anonymous distribution system (poste restante.)
+**\<monerodesigns>** nice
+**\<msvb-mob>** And another edition of BTC Manager is coming out reporting on us.
+**\<msvb-mob>** Bunch of stuff I found in China, like visiting a factory.
+**\<msvb-mob>** And we're planning a third hardware team meeting this week:
+**\<msvb-mob>** ...wait for it.
+**\<msvb-mob>** https://doodle.com/poll/c8hg5gs8kuvt92dp
+**\<msvb-mob>** rehrar: Thanks.
+**\<msvb-mob>** Any questions?
+**\<rehrar>** will we pull this off? or are we just a bunch of kids trying to play with the big boys?
+**\<rehrar>** but that may be for another time
+**\<rehrar>** serhack, my man. You wanted to speak a few words about Mastering Monero?
+**\<serhack>** oh, I thought about monero integrations too
+**\<rehrar>** do both
+**\<serhack>** Anyway for monero integrations, I am still working with cryptochangements for opencart gateway payment
+**\<rehrar>** you and cryptochangements
+**\<cryptochangements>** idk if there is much to say yey, but sure ;)
+**\<cryptochangements>** \*yet
+**\<serhack>** okay, let's talk about mastering monero now
+**\<cryptochangements>** sounds good
+**\<serhack>** I asked for FFS about Mastering Monero https://forum.getmonero.org/6/ideas/89797/mastering-monero-ffs
+**\<serhack>** At the moment, I have two chapters finished and the third is almost finished (exactly 47 pages)
+**\<serhack>** if you wanna tl;dr : Mastering Monero will be a book about the Monero world
+**\<serhack>** from Kovri to RingCT, mastering monero will have the answer for your questions about Monero!
+**\<serhack>** https://masteringmonero.com
+**\<serhack>** any questions?
+**\<rehrar>** You looking for illustrators?
+**\<rehrar>** for both infographics as well as general Monero illustrations?
+**\<serhack>** At the moment, I have baltsar as designer
+**\<zbert>** How many chapters are planned for now?
+**\<rehrar>** ok
+**\<msvb-mob>** Great choice, Baltsar makes super graphics. And nice to see a EPUB edition from the start.
+**\<serhack>** At the moment I planned about 7-8 chapters https://taiga.getmonero.org/project/serhack-mastering-monero/wiki/summary
+**\<serhack>** thanks msvb-mob
+**\<zbert>** serhack: thanks
+**\<serhack>** yw
+**\<monerodesigns>** who is the target audience?
+**\<monerodesigns>** everyman? or a crypto geek?
+**\<emesik>** from the summary it looks like addressing a broad audience
+**\<serhack>** expect the audience to be a mix of new, non-technical users and people who are more familiar with Monero and more technically advanced.
+**\<serhack>** I \*
+**\<rehrar>** alright, further questions can be fielded to serhack after the meeting, we've got more updates people
+**\<serhack>** emesik: sure!
+**\<monerodesigns>** a difficult target audience. great work so far!
+**\<serhack>** thanks a lot! :) send me a pm for questions
+**\<rehrar>** Now, it's time for: the man! the legend! amiuhle!!! *woooo* So tell us about Kasisto?
+**\<serhack>** go rehrar
+**\<amiuhle>** lol
+**\<amiuhle>** Kasisto in 22 seconds: https://imgur.com/a/aLFB3
+**\<serhack>** amiuhle the king whoaa!
+**\<amiuhle>** I'm done with Milestonen 1 / Alpha 2. Just wrapping things up with better documentation / overview in the README and technical details on how to set up the server
+**\<keledoro>** Awesome!
+**\<cryptochangements>** oh I havent yet got a chance to test out kasisto but that looks dope
+**\<serhack>** very good amiuhle! it's a perfect point of sale system
+**\<amiuhle>** I'll put that in the README. Maybe I'll do it again because it's a bit blurry
+**\<sarang>** That kasisto is faaaast
+**\<amiuhle>** Well to be fair, it's the same remote node
+**\<amiuhle>** So if it has to propagate through the network first it might be a bit slower
+**\<amiuhle>** Is anyone running a public v6 testnet node?
+**\<amiuhle>** binaryFate maybe?
+**\<emesik>** If there's a need for such node, I could set up one
+**\<amiuhle>** And Kasisto was tested at the last Berlin meetup and as I understand it's a permanent payment method there now
+**\<cryptochangements>** thats pretty awesome
+**\<amiuhle>** I think it'd be good to have a few of those, yes
+**\<vdo>** i'm running one and I'm organizing Barcelona meetup next wed
+**\<serhack>** For the new users, here it's kasisto : https://github.com/amiuhle/kasisto
+**\<vdo>** but the owner wants to use mobile wallet monerujo for now
+**\<rehrar>** dude, this is one of the things I am the most excited about.
+**\<phx[m]>** Yea very cool
+**\<amiuhle>** vdo: Have a testnet wallet ready so you can show the owner while you're there..
+**\<vdo>** yeah ok
+**\<amiuhle>** cool
+**\<vdo>** i need to explain view only wallets and such
+**\<rehrar>** alright, thanks so much!
+**\<rehrar>** Alright guys, let's sit back and relax. Take a breather. Put your thinking caps on.
+**\<amiuhle>** I'm hoping to wrap it all up and push the latest changes today / tomorrow and then I'll update the FFS post
+**\<rehrar>** Because it's time for 4. TBA
+**\<emesik>** wait
+**\<rehrar>** And we need to think what sgp wanted to put there
+**\<rehrar>** :P
+**\<rehrar>** what's up emesik?
+**\<emesik>** an update on python module FFS
+**\<serhack>** TBA ? The big algorithm? LoL
+**\<emesik>** so, basically the code for first release is almost ready
+**\<rehrar>** oh perfect. I'm so sorry. Go for it.
+**\<emesik>** I'm writing the docs, both API and tutorial
+**\<emesik>** I think the first release will be available in early february
+**\<rehrar>** awesome!
+**\<emesik>** it will already allow to read wallet data, retrieve list of transactions (in and out), and of course send them
+**\<emesik>** for sending I already have two ways, simple transfer by the wallet
+**\<emesik>** or retrieving a blob to be posted to daemon directly
+**\<emesik>** I'd be happy to add payment proofs to the first release
+**\<emesik>** but will see if time allows for that
+**\<emesik>** anyway, the development won't stop with the FFS milestone completed
+**\<emesik>** there's a lot of things to do further on
+**\<emesik>** multisig for example, or libwallet
+**\<emesik>** the code is here: https://github.com/emesik/monero-python
+**\<amiuhle>** Good to see a tests folder there :+1:
+**\<emesik>** and good news, the module is going to be ahead of Monero itself, already handling accounts and subaddresses
+**\<emesik>** any questions?
+**\<rehrar>** this conglomerate of passionate individuals is honestly the most inspiring thing. It may even inspire me to get involved and do something.
+**\<rehrar>** thank you emesik for the update!
+**\<rehrar>** Just a fun FFS to look at. If you liked the Monero Cat comics, the guy who made them opened a FFS proposal to make more (bigger): https://forum.getmonero.org/6/ideas/89764/i-d-like-to-develop-a-new-webcomic-series-starring-monerocat-and-the-justice-league-of-crypto
+**\<rehrar>** feel free to read it through and comment on it
+**\<rehrar>** Alright, we can move into 5. Open ideas time
+**\<rehrar>** This is a time where we as a community workgroup put our heads together and throw ideas out there about how to improve Monero, the community, and more.
+**\<rehrar>** So, have at it. Any ideas or things you want to say?
+**\<monerodesigns>** ok, i don't know if this is the best time, I just wanted to say hi... I'm the guy behind the Monero Designs wallpapers and those pizzaboy images...
+**\<monerodesigns>** and I just wanted to say thanks to everyone for the cool feedback and everything
+**\<serhack>** Hi monerodesigns and welcome to Monero community!
+**\<monerodesigns>** I have a couple of new ideas in the works... if there's ever anyone that wants to reach out or anything, I'm very excited about monero... been following the project since january last year
+**\<serhack>** I would like to mark a little thing: Mastering Monero is basically a Monero Marketing Campaign by a book
+**\<serhack>** so if you have any ideas about marketing, please let us know!
+**\<emesik>** #dontbuymonero stickers on your local ATM ;)
+**\<monerodesigns>** anyway, just wanted to say that what made me start doing this was a reddit post a couple of months ago about how there aren't any posters like there are for bitcoin
+**\<monerodesigns>** that's it, rant over :)
+**\<emesik>** monerodesigns: coul you paste a link to your works, please?
+**\<monerodesigns>** i think what the community is doing now is the best thing it can be doing... just making others aware of this awesome project, without any hype or anything
+**\<cryptochangements>** gingeropolous made this reddit post https://www.reddit.com/r/Monero/comments/7rn6el/moneroworld_remote_nodes_geo_lists/?utm_source=reddit-android about moneroworld remote nodes. in there he mentions funding powerful servers for nodes. It looks like the general donation fund on moneroworld.com is where we can direct donations for anybody thay wants to.
+**\<monerodesigns>** monerodesigns.com (the website is a mess... this is just something I'm doing on the side... lol)
+**\<emesik>** monerodesigns: thx!
+**\<emesik>** I like them!
+**\<monerodesigns>** i liked that whole "run your own node." campaign by the bitcoin community. i think that's a good thing... it was what made me start a monero node a couple of months ago
+**\<monerodesigns>** (ironically, it was the bitcoin posters that made me start my monero node lol)
+**\<rehrar>** I'm thinking of holding another mini-privacy conference over youtube like I did before. I think most everyone missed it because it the circumstances around it were...different. :P
+**\<monerodesigns>** @michalthanks!
+**\<cryptochangements>** more personal nodes totally helps oit the network, but unfortunatly remote nodes that new users use is kinda centralized at the moment
+**\<monerodesigns>** where are they located?
+**\<rehrar>** I just pop online and talk about privacy and get to do my infamous 'rehrar rants' without any interruption. Most people don't know how hard real privacy is in this day and age, and they think it's as easy as using one or two tools or doing one or two things
+**\<monerodesigns>** or are there just not enough?
+**\<cryptochangements>** rehrar i missed that! you got a link?
+**\<miziel>** there will be a need for some poster/sticker campaign after the new slogan will be "forged"
+**\<keledoro>** I'd watch it @rehrar. Make sure to announce it a couple of days before you're going to livestream it
+**\<monerodesigns>** I run my node on my miner, and it barely takes away any hashrate... i think if lots of miners ran their nodes...
+**\<rehrar>** link to last one: https://www.youtube.com/watch?v=GRZzyvN_gS0
+**\<emesik>** monerodesigns: Opposite here. I had to buy a bigger VPS to accommodate the blockchain. As result I got 3 spare cores that are hashing right now :)
+**\<phx[m]>** monerodesigns: good to see some memes. People tend to underestimate their power
+**\<vdo>** scaleway.com is working quite well for me
+**\<rehrar>** alright, if there's not that much more to discuss, then maybe we can call it early, unless someone wants to share an idea
+**\<vdo>** at a reasonable price for ssd
+**\<keledoro>** With the latest increase in merchants adoption, how about we setup a new fancy, "browsable" directory instead of listing all merchants on one page (getmonero.org/community/merchants)? Making it possible to browse by product category, type of service etc. Also making it easier to add new merchants, because right now you need a github acc. in order to add a new one
+**\<keledoro>** What do you guys think?
+**\<rehrar>** moneromerchants.com?
+**\<serhack>** why not updating css style on https://forum.getmonero.org/ rehrar?
+**\<vdo>** there's one list at monero.how
+**\<rehrar>** it's supposed to be replaced serhack with getmonero.org/forum-funding-system
+**\<keledoro>** just had to check if moneromerchants.com is a thing :D
+**\<rehrar>** waiting on fp for a couple things for this to move forward, and I can't move forward without it
+**\<rehrar>** someone can buy moneromerchants.com if it's not taken already
+**\<rehrar>** and the community can throw together something like that. I'd be willing to help contribute as a web dev
+**\<serhack>** moneromerchants.com is taken :/
+**\<monerodesigns>** yeah, thanks... I have a couple of ideas in the works at the moment... It's just hard to get some of the nuance of fungibility across in a short meme-like format
+**\<cryptochangements>** i think that's a good idea to clean it up, but I think it should still be done by github PRs if youre gonna use getmonero otherwise it will just get filled with spam
+**\<amiuhle>** Does anyone know who runs dis.gratis? I'd like to have a clone for the v6 testnet
+**\<rehrar>** monerodirectory.com?
+**\<emesik>** amiuhle: how actually can we choose the testnet version right now?
+**\<emesik>** if I understand, there are 2 forks
+**\<amiuhle>** Depends on the binary you're running
+**\<emesik>** always latest master
+**\<keledoro>** Would be available
+**\<amiuhle>** Release binaries with --testnet is the v6 fork, master build is v7
+**\<emesik>** ok!
+**\<keledoro>** Well, anyway I just wanted to start a conversation about having a more organized merchants directory
+**\<keledoro>** Maybe it's a bit too early, since it all still fits on one page
+**\<amiuhle>** I like the idea, could come with a map for POS
+**\<monerodesigns>** @keledoro I think it's a good idea
+**\<emesik>** keledoro: Merchants are precious now, we should take care to promote them
+**\<monerodesigns>** @michal I agree!
+**\<vdo>** is something like xmr.to with LN support planned?
+**\<emesik>** btw, do you think we should mention darknet markets accepting monero on the official project pages?
+**\<rehrar>** no
+**\<amiuhle>** no
+**\<monerodesigns>** no :)
+**\<emesik>** ok :D
+**\<rehrar>** alright everyone, I think we'll call it
+**\<rehrar>** so, next meeting date/time
+**\<rehrar>** two weeks from now
+**\<rehrar>** the third of Febz
+**\<rehrar>** Thanks for coming by the meeting. It's good to hear all the progress that's being made.
+**\<monerodesigns>** same time yeah?
+**\<rehrar>** Ye.
+**\<keledoro>** See you around!
+**\<rehrar>** Meeting over. Have good lives.
+**\<monerodesigns>** (i wont be able to attend, but see around at the next one)
+**\<emesik>** see you!
+**\<amiuhle>** See you guys!
+**\<monerodesigns>** see ya
+**\<cryptochangements>** see y'all
+**\<serhack>** Bye
+**\<vdo>** bye
\ No newline at end of file
diff --git a/_posts/2018-01-21-logs-for-the-Bulletproofs-meeting-held-on-2018-01-21.md b/_posts/2018-01-21-logs-for-the-Bulletproofs-meeting-held-on-2018-01-21.md
new file mode 100644
index 0000000000000000000000000000000000000000..c61f5f139bb989d38cc5d8e37bbcbdd76d93da31
--- /dev/null
+++ b/_posts/2018-01-21-logs-for-the-Bulletproofs-meeting-held-on-2018-01-21.md
@@ -0,0 +1,698 @@
+---
+layout: post
+title: Logs for the Bulletproofs Meeting Held on 2018-01-21
+summary: Bulletproofs, fees, hardforks, and miscellaneous
+tags: [community, crypto, research]
+author: dEBRUYNE / fluffypony
+---
+
+# Logs
+
+**\<rehrar>** heyo everyone! Meeting time.
+**\<rehrar>** https://github.com/monero-project/meta/issues/161
+**\<rbrunner>** Hi, was already afraid nobody around or wrong time :)
+**\<rehrar>** this meeting is all about Bulletproofs, and discussing when/how, audit stuff, finance stuff, and more
+**\<rehrar>** fluffypony smooth ArticMine luigi1111 luigi1111w hyc (said he can't be here though) moneromooo gingeropolous endogenic anonimal
+**\<rehrar>** binaryFate sarang suraeNoether stoffu
+**\<sarang>** this channel?
+**\<rehrar>** and feel free to ping anyone else
+**\<rehrar>** oh, we doing it in MRL? We can if that's what we want.
+**\<sarang>** Either. I couldn't recall which
+**\<sarang>** Your pick
+**\<rehrar>** The Github issue says #monero-dev
+**\<sarang>** k
+**\<rehrar>** and more people can see in Slack and Mattermost since MRL is not relayed
+**\<sarang>** roger
+**\<rehrar>** so first order of business, as always, is 1. Greetings.
+**\<rehrar>** If you're here, say hi. :)
+**\<sarang>** yo
+**\<rbrunner>** Hi
+**\<sgp>** Hi
+**\<dsc>** Hi
+**\<pigeons1[m]>** Hi
+**\<geozdr>** hi
+**\<rehrar>** well, that's a decent group so far. Perhaps a few others will join as time passes.
+**\<rehrar>** dEBRUYNE, Jaquee, vtnerd
+**\<dEBRUYNE>** I am here
+**\<rehrar>** In the meantime, let's begin discussion.
+**\<rehrar>** Does MRL have an update for us regarding audit outreach?
+**\<sarang>** Yes
+**\<suraeNoether>** howdy
+**\<sarang>** So
+**\<rehrar>** and I know hyc isn't here atm, but does someone know about how the mailing list outreach went also?
+**\<rehrar>** (sorry, go ahead sarang)
+**\<sarang>** There are three groups to whom we are reaching out
+**\<sarang>** One is professional auditing/security roups
+**\<sarang>** \*groups
+**\<sarang>** Second is targeted individuals who know the material
+**\<sarang>** Third is volunteers without necessarily any particular credentials, but who want to help the project
+**\<sarang>** All are valuable
+**\<Maxithi>** Perhaps a few others will join as time passes. \<= Joined
+**\<sarang>** Let's start with targeted individuals
+**\<sarang>** Benedikt Buenz is an author on the original paper. He may be available after Feb 20 and has shown interest but not a commitment yet
+**\<sarang>** Jonathan Bootle is another author. He is unavailable but will pass on word to his colleagues
+**\<sarang>** I reached out to Greg Maxwell who's newly independent, and haven't heard back
+**\<sarang>** It was assumed that we would offer compensation to these individuals for their time, with no details on amount
+**\<sarang>** Next up is volunteers
+**\<sarang>** I've heard from ~5 people who'd like to help out
+**\<sarang>** I'm setting them loose with as much information as I can
+**\<sarang>** This would be on a volunteer basis, but we'd credit them publicly for their help
+**\<sarang>** Finally is the pro groups
+**\<sarang>** fluffypony put me in touch with one group that has given me a quote of $40K
+**\<sarang>** Downsides: it'd be for internal-only reports, but obviously any changes would become public right away
+**\<sarang>** We also couldn't credit them by name
+**\<sarang>** I'm having them check with their attorneys on exactly what we could share
+**\<sarang>** OSTIF works with a lot of different groups, and has been in contact with several, quotes pending
+**\<sarang>** OSTIF's policy is only to work with groups that allow public disclosure
+**\<sarang>** They are also willing to accept XMR (which they transfer to the groups in their currency of choice) and has agreed not to take a cut
+**\<sarang>** Any questions from the group on this wall of info?
+**\<suraeNoether>** were we also not contacted in a cold-call situation?
+**\<sarang>** Yes, one pro group did a cold-call. Turns out OSTIF was in contact with them too, so I'm lumping them in with OSTIF
+**\<sarang>** That cold-call group's rough estimate was $25-35K
+**\<suraeNoether>** oh ok
+**\<rbrunner>** Is that USD 40K in the right ballpark for work like that, from a "pro group"?
+**\<sarang>** So I had expected less, but only because of the limited scope of the BP code; it's relatively small and self-contained
+**\<sarang>** But the quotes are reasonably consistent with each other
+**\<suraeNoether>** rbrunner: it's in line with similar quotes obtained back when we pushed ringct, which was around 50k iirc. so somewhere between 40 and 50k is sort of what i expected, personally... the 25-35k was a little bit of a surprise
+**\<sarang>** and assumes $1-2K per person-day
+**\<rbrunner>** Ok
+**\<sarang>** The timeline would be between 10-25 work days once it starts
+**\<sarang>** Again, OSTIF is still waiting on additional quotes and will report to me when they have them
+**\<rehrar>** So there is at least some interest being generated.
+**\<sarang>** So for now, assume that we definitely have options for pro audits in the range of $25-40K
+**\<sarang>** I also love the idea of getting Buenz or Maxwell to audit individually
+**\<sarang>** but there are no commitments from them, and may not be. They have a lot going on
+**\<sarang>** But
+**\<sarang>** We need to know how to fund this shiz
+**\<rehrar>** alright, and this doesn't include hyc's outreach stuff too, correct?
+**\<suraeNoether>** i believe that's the case rehrar.
+**\<Maxithi>** How did BP get funded?
+**\<sarang>** hyc's outreach to the list has generated a few contacts within the groups I mentioned
+**\<Maxithi>** \*RCT
+**\<rehrar>** ok, great
+**\<suraeNoether>** Maxithi: I believe we chose to not do the audit back then
+**\<sarang>** The RingCT audit didn't happen, IIUC
+**\<rehrar>** maybe MRL can do RingCT audit? :P What would you guys quote us?
+**\<rbrunner>** That about RingCT is ... surprising
+**\<suraeNoether>** rbrunner the math was a lot more straightforward for original RingCT
+**\<rehrar>** Wasn't that one of the reasons for bad blood with Shen?
+**\<rehrar>** anyways, off-topic.
+**\<sarang>** It was suggested that perhaps some general funding might be available, but otherwise an FFS
+**\<suraeNoether>** i think it would be nice to get buenz, but since he's on the late-feb timeline, that conflicts with our hard fork
+**\<rehrar>** I think we should try to raise the full amount with FFS, and anything that is not covered in reasonable time can be covered with the General Fund
+**\<sarang>** We'd be cutting it close to March with any group
+**\<sarang>** And there's no guarantee of an immediate start
+**\<rehrar>** suraeNoether it only conflicts if we try to roll out BP in March, no?
+**\<suraeNoether>** rehrar yes
+**\<rehrar>** I think this info gives strong pushes to rolling out in September
+**\<sarang>** Also, in terms of scope I've asked them to only review the multi-BP code
+**\<rehrar>** Because we also need the time to raise the requested funds
+**\<dEBRUYNE>** \<rehrar> Wasn't that one of the reasons for bad blood with Shen? \<= No.
+**\<suraeNoether>** IMO, if we can't reasonably expect an audit to be completed before the march hard fork
+**\<rehrar>** \<dEBRUYNE> \<rehrar> Wasn't that one of the reasons for bad blood with Shen? \<= No. \<= K. Thanks.
+**\<dEBRUYNE>** We should just put the "include it in the March HF" out of our heads tbh
+**\<suraeNoether>** dEBRUYNE: +1
+**\<rehrar>** agreed
+**\<suraeNoether>** in that case, I think we should just go with Buenz and Maxwell
+**\<suraeNoether>** and/or
+**\<sgp>** Unless there is a strong reason to hardfork in March, why not delay it until whenever the review is ready?
+**\<suraeNoether>** continue to try to talk to them
+**\<suraeNoether>** sgp: because delaying hard forks sets a very disagreeable precedent
+**\<sarang>** Keep in mind there's no guarantee that Buenz and Maxwell are even going to be available to do it
+**\<sarang>** We'll have professional options available for sure
+**\<suraeNoether>** sarang: ok, if they turn us down then we go with one of the other options: what you are saying is that no one has committed, so that statement is not really helpful for any of our optiosn rihgt now. :P
+**\<sarang>** Heck, I have a contract from the non-public group already
+**\<rbrunner>** You mean ready to sign?
+**\<dEBRUYNE>** \<suraeNoether> sarang: ok, if they turn us down then we go with one of the other options: \<= Imo should just take on multiple options
+**\<rehrar>** non-public group doesn't sound quite so useful tbh. But maybe I just don't understand how these things work. But they're like: "We can't share hardly anything publicly." So what's the point?
+**\<dEBRUYNE>** re: funding, the general dev fund could kickstart it and then the community could fund the remainder
+**\<sgp>** @surae RingCT warranted moving the fork. I'd hate to have the review done in May but have to wait until September to include this important code
+**\<sarang>** rbrunner: they're ready to sign if/when we are, but we're under no obligation with them
+**\<suraeNoether>** dEBRUYNE: i'm fine with that too, assuming we have infinite funding available
+**\<dEBRUYNE>** rehrar: they can still disclose vulnerabilities privately
+**\<dEBRUYNE>** and we can fix them
+**\<rehrar>** ah, k. Don't know why that didn't cross my mind. :P
+**\<suraeNoether>** rehrar: we can share whether they have recommended changes, and if they do recommended change, we will end up communicating all of them to the community. they just don't want their company name or the report itself to be made public afaik?
+**\<sarang>** dEBRUYNE: rehrar: the changes are all public, and we can likely discuss the vulnerabilities
+**\<sarang>** just not release their review
+**\<Maxithi>** What I fear with internal report is that the community would be less willing to support it as they haven't any view on how the funds were used.
+**\<sarang>** And we can't say who did the review. They can do a more public audit but they said it'd be a lot more $ and time
+**\<dEBRUYNE>** assuming we have infinite funding available \<= not infinite, but if the community can raise 450k $ for globee, I am sure we can raise a few hunderd k $ for this too
+**\<sarang>** Again, I'm working with them and their lawyers to get as much public as possible
+**\<rehrar>** And it gives 'poking power' to naysayers of Monero who say that we don't release the name of people who did the audit. It could have been Joe Schmoe
+**\<rbrunner>** Why do they work so secretly? In a few words ...?
+**\<sarang>** Fortunately all of the OSTIF quotes will be for fully public audits
+**\<sarang>** rbrunner: it's not working in secret
+**\<sarang>** It's not wanting to be seen as an endorsement
+**\<sarang>** They do either internal audits (like this one), or much more comprehensive public-facing ones
+**\<pigeons1[m]>** Do they not want to be blamed for what they miss?
+**\<sgp>** pigeons I'm sure that's part of it
+**\<rehrar>** I see the not wanting to be viewed as an endorsement unless they are adequately compensated for that
+**\<sarang>** Fortunately they won't be the only option, just the first to prepare a quote and contract
+**\<suraeNoether>** sgp: moving HF dates is not on the table, in my mind. 6 months of data on the blockchain is marginal in the long run; delaying HFs sets an unfortunate precedent.
+**\<sarang>** I think the community will appreciate the openness of an OSTIF group
+**\<rehrar>** but because Monero always prides itself in doing most things in the open, I think we should try the other more public options first
+**\<sarang>** and/or Buenz and/or Maxwell
+**\<sarang>** rehrar: I agree
+**\<rbrunner>** Agree also
+**\<Maxithi>** Agree
+**\<suraeNoether>** rehrar sarang +1
+**\<sarang>** We should get a sense of how much we think is reasonable to raise in funds
+**\<sarang>** since that determines how many groups/peeps we can get
+**\<rehrar>** well, it should also be said that perhaps we should raise a 'vetting pool' of funds for not just BP, but any future work that needs to be looked at
+**\<suraeNoether>** rehrar great minds, buddy
+**\<suraeNoether>** i was just thinking about that
+**\<rehrar>** could be managed by MRL how they see fit, and reported to the community
+**\<Maxithi>** That would be great!
+**\<rehrar>** suraeNoether, in Russia the saying is: "Two fools are of the same mind."
+**\<sarang>** We have the bounty funds, but those can't be used for reviews
+**\<sarang>** So this would need to be separate
+**\<suraeNoether>** rehrar: I don't know about MRL being exclusively in control of vetting funds... i think multisig would be a better option :P
+**\<sarang>** But any reported flaws could be bountied
+**\<rehrar>** The stipulations of the pool would be that MRL manages, gets counsel from the Core Team, and reports spending to the community
+**\<rehrar>** or something along those lines anyways
+**\<suraeNoether>** right
+**\<sarang>** I'm sure someone will complain "isn't review what MRL is for????!?!?111!?"
+**\<rehrar>** I think reported flaws would go through the HackerOne bounty system, and the pool would be for formal review compensation
+**\<sarang>** But you can't do first-person peer review =p
+**\<sarang>** rehrar: yes
+**\<suraeNoether>** sarang +1
+**\<suraeNoether>** i was wondering what a good snappy response to that should be
+**\<suraeNoether>** thank you for that. :P it's been on my mind
+**\<sarang>** I like to think of it as belt and suspenders
+**\<rehrar>** Raise half a million. Increase as necessary. Sound good?
+**\<Maxithi>** isn't review what MRL is for????!?!?111!? \<= Nope, the R stands for Research not Review
+**\<rbrunner>** Somebody always complains :)
+**\<sarang>** and that I've had spinach caught in my teeth and not noticed for hours
+**\<geozdr>** maybe not set public targets for raising funds before you get all the quotes? that would hurt our negotiating position.
+**\<suraeNoether>** geozdr +1 also
+**\<Maxithi>** Can you have "private funding" on the forum?
+**\<sarang>** We certainly don't have numbers for paying targeted individuals
+**\<rehrar>** geozdr, but not all funds will be for BP, so we can internally set a 'BP budget' that is not advertised to potential reviewers
+**\<suraeNoether>** they'll also have to provide us with a quote sarang imo
+**\<sarang>** Yes, and I asked Buenz about thi
+**\<sarang>** \*this
+**\<sarang>** didn't hear back yet
+**\<rehrar>** just because we raise a public amount, doesn't mean all of that amount is available for Bulletproof review, and if anyone tries to negotiate based on total amount raised, we push back with that fact, and that BP has a budget
+**\<rehrar>** *cracks knuckles* and I'll let those tech nerds know that we like our money here, and it will not be easily parted with
+**\<rehrar>** what about andytoshie, wasn't he approached about review also?
+**\<rehrar>** \*andytoshi
+**\<suraeNoether>** sarang do you think that since andytoshi sort of helped with the development, he falls into the "self-peer-review" category
+**\<suraeNoether>** ?
+**\<sarang>** andytoshi has provided useful guidance on bulletproofs but I don't believe he's available for a formal audit
+**\<suraeNoether>** ah, that answers that question
+**\<sarang>** He's also expressed that he doesn't necessarily want to be seen as endorsing particular projects, but I don't want to put words into his mouth
+**\<rehrar>** So...since it's pretty much unanimously agreed that BP should not be in March, do you think MRL can put together a formal little news bulletin (I can help), explaining that and why?
+**\<rehrar>** It'd be helpful to the community, and could help with explaining to some grumblers the benefits and reasons for waiting
+**\<rbrunner>** Other "heavyweights" are known to be against March?
+**\<rbrunner>** Not present now
+**\<rehrar>** luigi and ArticMine both come to mind
+**\<suraeNoether>** rbrunner: I have a text message from fluffypony describing his position on it, but that's hearsay without a PGP signature. :P
+**\<rehrar>** I think smooth as well, but don't quote me on that
+**\<suraeNoether>** so, it seems like there is a weak consensus here that we should start an FFS to fund up a general "new scheme and code" auditing fund. either for MRL to spend as we feel we need to (with as much transparency as possible) or with several core members on board with distribution of those funds also.
+**\<rbrunner>** Yes, and with a catchy name
+**\<rehrar>** Yes.
+**\<sarang>** Setting up a more general fund is also really good optics against the naysayers
+**\<rbrunner>** as this review stuff is quite dry :)
+**\<suraeNoether>** if we are going to assume the march HF is out the window, then we can spend another few weeks working out the details on that
+**\<pebx>** suraeNoether I think we trust you that you don't fake a message from fluffy...
+**\<sarang>** It shows that we have a plan for BPs, and also for future big changes that need audits
+**\<rehrar>** Monero Auditing Interest Department So Audits Frequently get Done or MAIDSAFE for short
+**\<rbrunner>** Monero security fund, or so
+**\<Maxithi>** MAIDSAFE lol
+**\<rehrar>** oops, fail on that last letter though
+**\<suraeNoether>** pebx: heh, well he basically said we shouldn't worry about the optics of pushing it back or about the added blockchain space. in the long run, those things become quite marginal
+**\<rbrunner>** Did you come up with that right now? Wow
+**\<sgp>** @rehrar is now a good time to discuss the hard fork schedule? I want to express some dissenting opinion
+**\<suraeNoether>** fluffypony \^
+**\<rehrar>** of pushing back March hardfork you mean?
+**\<rehrar>** oh, of pushing back BPs
+**\<rehrar>** sgp, speak my child.
+**\<rehrar>** (So Audits Frequently Execute, there's the E)
+**\<sgp>** I'm totally fine not including BPs in the March hard fork since it seems a review will not be completed yet. I get that
+**\<sgp>** If people want to stick with the March harkfork for precedent reasons, I'm fine with that too
+**\<sgp>** But I really think it's a bad idea to wait until September to add the BP code once it has passed review
+**\<sarang>** Why?
+**\<sgp>** There are many practical reasons to have another hardfork
+**\<sarang>** Blockchain waste?
+**\<sgp>** Smaller transaction sizes, smaller fees, smaller blockchain
+**\<rehrar>** Sumokoin will implement, then we're screwed
+**\<sgp>** Yes, basically
+**\<sgp>** And I think the precedent argument is pretty weak. Last year, the community agreed upon moving the date of one hardfork and adding another
+**\<gingeropolous>** y are we screwed?
+**\<rehrar>** I was joking
+**\<gingeropolous>** :)
+**\<rehrar>** thought of another name for the fund btw, but I'll save it for after meeting
+**\<rbrunner>** rehrar, MAIDSAFE is great
+**\<medusa>** initially it was planned to use the general dev fund for reviews afaik
+**\<pebx>** I'm totally with sgp
+**\<medusa>** if there is no money left we can run an ffs, but that should be checked first in my opinion
+**\<sgp>** So my vote is to either have another hardfork after the BP review, or to push back the March hardfork if there's no real reason to have a hardfork in March for another feature
+**\<pebx>** as far as i know there is no other feature which needs a hard fork actually
+**\<rehrar>** rbrunner, not as good as Ze Cryptography Auditing Software Hoard Foundation
+**\<rbrunner>** Might not be a bad idea, with so many thing into service waiting
+**\<sarang>** -\_-
+**\<sgp>** @pebx exactly, unless there was consensus on a larger ringsize or something
+**\<rbrunner>** I know, some things do not technically need a hard fork, but a hard fork forces updates, which is nice
+**\<medusa>** we use hardforks to force ppl to upgrade the software..this has an effect on support work on redit, relegram etc. thats the main reason
+**\<sgp>** Which I don't think will happen
+**\<suraeNoether>** "And I think the precedent argument is pretty weak. Last year, the community agreed upon moving the date of one hardfork and adding another" \<-- you just used precedent to demonstrate that precedents don't matter?
+**\<suraeNoether>** and btw this is exactly the discussion that we wanted to avoid with the HFs... "So my vote is to either have another hardfork after the BP review, or to push back the March hardfork if there's no real reason to have a hardfork in March for another feature" \<--- we hard fork twice a year, how much is enough?
+**\<pebx>** i can say you as of telegram: people are really expecting BP or at least lower fees... but lowering the fees manually is in my opinion some kind of doctoring around without a real scop
+**\<sgp>** I'm saying your argument of needing to stick with precedent should be more flexible
+**\<pebx>** \*scope
+**\<rbrunner>** Well, the reaction on the Monero subreddit in face of a move into September was surprisingly subdued
+**\<rehrar>** delaying until September has other benefits not related to the Monero implementation
+**\<suraeNoether>** sgp and you are using precedents of previous moving HF schedules to show why it's not a big deal to move HFs... but the entire point is *these precedents need to be avoided*
+**\<rehrar>** it lets the BP paper itself have more time in existence
+**\<sarang>** And the audits specifically are not testing the BP math/paper
+**\<rehrar>** and there may be some people interested in reviewing the paper itself (Without carin about the Monero implementation) that would be useful to us
+**\<sarang>** It's way out of scope for those groups
+**\<sgp>** Why? If there's a legitimate reason to, what's the harm?
+**\<suraeNoether>** just the code
+**\<sarang>** sgp: you mean why are they not reviewing the math?
+**\<sarang>** Because it's an entirely different kind of review, altogether
+**\<suraeNoether>** i think sgp means "why not have three HFs this year
+**\<sgp>** No, not that
+**\<sarang>** k
+**\<pebx>** but let's be realistic: probably most interested people start to look into it only 1-2 weeks before it will be implemented anyway
+**\<sgp>** If we don't add another hardfork, we're committing at least 12 GB of extra blockchain data, assuming transaction volume stays the same
+**\<rehrar>** that was the argument before pebx, yes
+**\<pebx>** i would rather prefer to move the hard fork to april or may with BP than hard forking in march just for the case
+**\<rehrar>** but now there is demonstrated interest in getting the reviews done for financial compensation
+**\<suraeNoether>** sgp: we have to freeze the code 3+ weeks before each HF and begin implementation. HFing monero to implement BPs is not simple as creating a new email account.
+**\<suraeNoether>** think of each HF as rolling out a new year/model of car.
+**\<sgp>** I understand that surae
+**\<sgp>** But you could easily schedule a hardfork a month after you felt comfortable with the review
+**\<suraeNoether>** and if that happens to be August
+**\<suraeNoether>** does that mean we then HF immediately again in September, or also put that one off?
+**\<suraeNoether>** etc
+**\<suraeNoether>** etc
+**\<sarang>** So to move this talk forward... really the question is between (a) doing March and then BP when it's ready, (b) doing no fork until BP is ready, or (c) doing March and waiting on BP until Sept
+**\<sgp>** Then don't add another one in that case
+**\<sgp>** But it seems like from your estimate the review should take less than a month
+**\<pebx>** sarang i'm for b
+**\* iDunk** likes how MRL is making sense
+**\<suraeNoether>** sarang no, this is not the question
+**\<pebx>** i really don't see a need for the march hard fork
+**\<suraeNoether>** not to mention
+**\<suraeNoether>** screwing with HF schedules
+**\<suraeNoether>** completely BLOWS for HW wallet developers
+**\<iDunk>** Postpones subaddresses
+**\<suraeNoether>** sarang: we had a weak agreement, even sgp agreed... that the March HF should go forward, and BPs should probably not be included.
+**\<rehrar>** suraeNoether, you say that the best thing for new cryptography is time
+**\<medusa>** C is the only option
+**\<rehrar>** correct?
+**\<suraeNoether>** agreed with medusa
+**\<suraeNoether>** rehrar: always yes
+**\<sgp>** I've expressed my support for A or B
+**\<rehrar>** then C is the only option
+**\<rbrunner>** Maybe the least bad
+**\<thrmo>** second B
+**\<rehrar>** we are responsible for people's money, freedom, and lives, remember?
+**\<iDunk>** I'm for C.
+**\<suraeNoether>** any concerns about getting BPs implemented *quickly* are not thinking about what Monero is going to look like in 2022
+**\<Maxithi>** Mind to make a quick run up to explain in one sentence A, B and C?
+**\<thrmo>** suraeNoether, B doesn't have to be quickly
+**\<sarang>** The real downside in a March/Sept is the blockchain size
+**\<thrmo>** Maxithi, **\<sarang>** So to move this talk forward... really the question is between (a) doing March and then BP when it's ready, (b) doing no fork until BP is ready, or (c) doing March and waiting on BP until Sept
+**\<sarang>** if that's something you care about
+**\<pebx>** i somehow miss smooth, moneromoo and fluffypony in this discussion... i know, i have been late today but what's their opinion?
+**\<suraeNoether>** fluffypony is in Miami right now iirc, so he's probably sleeping on a pile of money and hookers
+**\<endogenic>** sarang: without bps coming along we wouldnt hve been able to avoid that
+**\<Maxithi>** thrmo Thx
+**\<pebx>** sarang the real downside in september is the community which is expecting it
+**\<pebx>** even more after fluffy announced it on twitter
+**\<iDunk>** Why are they expectiong it ?
+**\<pebx>** to be in march
+**\<medusa>** that not an argument rly
+**\<medusa>** ofc they want it
+**\<iDunk>** Who told them it would be in March ?
+**\<endogenic>** i want 0kb transactions and i want them now
+**\<rbrunner>** It was "word on the street" for a long time
+**\<sgp>** It just means we need a press release saying why the decision changed
+**\<rehrar>** I'm sure they also want other things asap.
+**\<suraeNoether>** sgp: we never announced any decisions on bulletproofs
+**\<rehrar>** hence my suggestion for MRL to put out a little news bulletin with a formal recommendation to wait
+**\<thrmo>** Without BP what consensus rules changes NEED an hardfork by march?
+**\<sarang>** We said March if it was ready
+**\<sarang>** We should do a press thing, yes
+**\<dEBRUYNE>** \<rbrunner> It was "word on the street" for a long time \<= Not really
+**\<pebx>** iDunk fluffy announced it to be implemented in march hard fork. that's also the reason why i miss him in the whole discussion
+**\<suraeNoether>** so our bulletin announcemennt that rehrar suggested will be the *first* formal announcmenet about BPs coming from monero.
+**\<sarang>** regardless of our choice
+**\<rehrar>** if community whines, we point to the bulletin
+**\<rbrunner>** Pushing people to update needs a hardfork in any case, IMHO
+**\<iDunk>** Well, fluffypony jumped the gun then.
+**\<rehrar>** if they REALLY disagree, I'm sorry to say, they can fork :P
+**\<dEBRUYNE>** fluffypony strongly favors adherence to the schedule fwiw
+**\<suraeNoether>** pebx: where did he announce that? can you send me a link?
+**\<pebx>** one second, i have to search on twitter...
+**\<thrmo>** dEBRUYNE, the schedule was never meant to be set in stone
+**\<gingeropolous>** was double blob brought up at all as an option? or am i just chasing windmills
+**\<thrmo>** It will eventually be changed, maybe now would be a good time to do it.
+**\<rbrunner>** double blob?
+**\<dEBRUYNE>** thrmo: need a source on that
+**\<iDunk>** You are chasing windmills :)
+**\<suraeNoether>** gingeropolous: not brought up at all. care to explain how that would work?
+**\<suraeNoether>** one thing i want to make perfectly clear to everyone in this room
+**\<endogenic>** thrmo: what necessitates breaking the existing schedule?
+**\<thrmo>** dEBRUYNE, fluffy mentioned it several times iirc (and others) that eventually the scheduled would be changed and the rate of HFs diminished.
+**\<Maxithi>** Double Blob https://github.com/monero-project/monero/issues/3154
+**\<gingeropolous>** u make a transaction with a borromean and a bullet proof. You only work with the borromean for n months. Eventually, bulletproofs are trusted. You can then prune the borromean from the chain.
+**\<dEBRUYNE>** thrmo: Then we'd change to once a year probably
+**\<dEBRUYNE>** and either march or september would be thrown out
+**\<suraeNoether>** gingeropolous: ah, there could be some security issues with that
+**\<endogenic>** thrmo: he mentioned that in the context of monero stabilizing in the future didnt he
+**\<rehrar>** thrmo, this is true when we get to a point that Monero has so many users that HFs become more and more difficult to pull off, not as a result of new tech as I understand it
+**\<thrmo>** endogenic, unnecessary blockchain growth for one, and why exactly do we NEED to hardfork in march?
+**\<gingeropolous>** in various conversations it seems that the issues aren't as severe as they seem.
+**\<endogenic>** thrmo: a hard fork causes blockchain growth?
+**\<rehrar>** to force upgrades to newer, more stable software is as good a reason for me as any
+**\<thrmo>** endogenic, adopting BPs later rather than sooner.
+**\<suraeNoether>** gingeropolous: it would take more time for us to vet the double blob technique than it would for us to audit the BP code alone and push it. :P
+**\<rehrar>** suraeNoether, what did you want to make perfectly clear?
+**\<thrmo>** rehrar, why do you need to fork for that?
+**\<suraeNoether>** so what i wanted to make clear: if you are hoping to get BPs implemented before September in order to get a price bump, or to avoid a price crash in Monero...
+**\<gingeropolous>** suraeNoether, perhaps.. but here I tried to fully explain it: https://github.com/monero-project/monero/issues/3154
+**\<medusa>** we usually use the fork to roll out cleints, so we just have 1 version to support
+**\<gingeropolous>** and furthermore, this isn't going to be the last time some amazing tech comes through to reduce transaction size
+**\<endogenic>** thrmo: changing the existing schedule needs to be justified more than not doing so in the absence of a problem making it necessary, and people agree that bulletproofs and its implementation needs to be audited right?
+**\<thrmo>** medusa, i know, it doesn't need to be that though.
+**\<rehrar>** can I speak bluntly?
+**\<gingeropolous>** so it'd be great if we had a mechanism to transition to fresh tech without wondering if the whole thing'll come crashing down
+**\<suraeNoether>** then your logic is already flawed... if you think Monero will hit 10,000 USD faster if we get BPs implemented in June instead of September, you are... well, i can't say for sure that you are wrong, but your logic circuits may need some dusting.
+**\<endogenic>** agree surae
+**\<endogenic>** also fees
+**\<thrmo>** endogenic, I do agree too, I just don't think that adherence to the schedule is as a big thing as it's been portrayed.
+**\<suraeNoether>** fees are going to be changing in this HF either way
+**\<sgp>** @surae please, I've been in the community for several years. I don't care about the price nearly as much as I care about the practical benefits of lower transaction fees and reduced blockchain bloat
+**\<endogenic>** if they are lowered at the expense of monero's security
+**\<endogenic>** what's even the point
+**\<gingeropolous>** ^^
+**\<suraeNoether>** sgp: *good* but our fees are going to be reduced anyway, and blockchain bloat is literally going to be marginal as time goes on
+**\<rehrar>** this is a moot conversation honestly, and it's silly that we are having it. Again, the responsibility on our shoulders is very large. Money, freedom, and lives. And if the best thing for this new crypto is time, then the LEAST we can do is give it an extra six months.
+**\<thrmo>** I couldn't care less about the price either.
+**\<endogenic>** i dunno thrmo imo it's a matter of what precedent we implicitly accept by agreeing to an action even if we arent aware of the consequences
+**\<endogenic>** people will use that precedent for their own reasons
+**\<endogenic>** just my two cents :p
+**\<sgp>** @rehrar we would be at the point though where the review(s) would have already been completed
+**\<suraeNoether>** sgp: and please don't take my comment as accusing you of being only interested in monero's price, i know that you are a long-time member of the community and we have had several good discussions in the past. i value your opinion
+**\<rehrar>** again sgp, it's not just the code that needs time to be
+**\<rehrar>** it's also the paper of BP itself
+**\<suraeNoether>** i just wanted to make that clear to anyone who ends up reading the logs later, or any lurkers who are thinking "but oh man i could totally get rich if they push this in June."
+**\<rehrar>** what if there is an exploitation in the crypto itself that has gone unnoticed at this point in time
+**\<rehrar>** the reviews will review our code implementation, not the paper
+**\<suraeNoether>** *nod* similar to the ASNL ring signatures in the original ringct paper
+**\<rehrar>** the crypto itself needs time to breathe
+**\<thrmo>** endogenic, there are some costs for "unnecessary" hardforks too, even if they are on schedule.
+**\<suraeNoether>** \*which wasn't caught until after the paper was published, put through peer review, and after I believe we had gone live with code.\*
+**\<rehrar>** this itself is an argument to wait
+**\<rehrar>** as I said before, there may be third parties that will review the BP paper itself (not our implementation of it) for their own reasons
+**\<iDunk>** It was live on testnet, not in mainnet.
+**\<rehrar>** and we can benefit from that
+**\<thrmo>** Hard forks momentarily weaken the security of the network, so doing it because of no other good reason than schedule seems silly to me.
+**\<endogenic>** thrmo to say they are technically unnecessary only speaks to part of the hypothetical necessity which must be evaluated. that's everything i'm saying
+**\<pigeons1[m]>** The code was only live on testnet
+**\<sarang>** We're definitely not the only ones interested in BPs, so there will be good eyes on it going forward
+**\<thrmo>** as rehrar pointed above, money, freedom and lives are at stake.
+**\<sgp>** We discussed this in previous meetings. There's always an argument to wait. If the community wants more review on the math, we should get an audit of that too
+**\<gingeropolous>** \<thrmo> Hard forks momentarily weaken the security of the network \<= what?
+**\<thrmo>** gingeropolous, Node count drops, hashrate drops, etc
+**\<suraeNoether>** thrmo we are modifying fees in the next hf so its not merely to accommodate schedules
+**\<sgp>** If we knew of researchers in the process of looking at the math I would agree with you, but it seems odd to wait in hopes someone is looking at it
+**\<rehrar>** sorry sgp, but the argument is not to wait indefinitely, it's to wait until September
+**\<rehrar>** it was mentioned in a previous meeting
+**\<gingeropolous>** and what if there aren't any reviews by then?
+**\<rehrar>** if we wait until September, that more than doubles the time that the BP paper has been in existence
+**\<dEBRUYNE>** sgp: Waiting until August / September literally triples the time the paper has been out in existence
+**\<dEBRUYNE>** That's a convex pay off
+**\<pebx>** https://twitter.com/fluffypony/status/945706717421195266
+**\<rehrar>** dEBRUYNE is more right than me \^ :P
+**\<pebx>** sorry took me longer than i thought, twitter search is unfortunately not the best
+**\<rehrar>** although I guess triples is technically "more than doubles"
+**\<thrmo>** pebx, fluffypony doesn't decide the community does.
+**\<rehrar>** also, the second time me and dEBRUYNE said remarkably similar things. Just a thought.
+**\<dEBRUYNE>** rehrar: :P
+**\<rbrunner>** Yes, but that was word on the street :)
+**\<gingeropolous>** nonsense! He is our god! Such blasphemy!
+**\<pebx>** i know, but the community expects this now... that's why i miss fluffy in the discussion
+**\<sgp>** He was just finding the tweet that others asked for
+**\<dEBRUYNE>** Whether the community expects BP in March is at most ambigous imo
+**\<rehrar>** ok, let's end this conversation with one question
+**\<suraeNoether>** pebx thanks for finding that. He shouldn't have said that, number one
+**\<dEBRUYNE>** at best\*
+**\<rehrar>** MRL: what is your formal recommendation to us at this point?
+**\<iDunk>** That tweet was unfortunate.
+**\<pebx>** suraeNoether that's the thing i'm talking about...
+**\<endogenic>** the code IS merged though
+**\<endogenic>** to master
+**\<sarang>** single output
+**\<pebx>** he is still some kind of project leader, but he missed last sunday's discussion and now too
+**\<iDunk>** And is live on testnet :)
+**\<rbrunner>** Yes, and live on Testnet
+**\<sarang>** multi is not yet
+**\<sarang>** and that's what we want audited
+**\<endogenic>** yes but aside from tagging an old commit
+**\<endogenic>** does this raise the issue of whether it should have been merged?
+**\<suraeNoether>** rehrar: Sarang, correct me on this if need be: our formal recommendation to pay an OSTIF group to audit the code, funded through a new acronym, and to include BPs in September.
+**\<dEBRUYNE>** I wouldn't confine the audit to the OSTIF group
+**\<rehrar>** sarang? you second this?
+**\<suraeNoether>** dEBRUYNE: just my recommendation based on what we've seen and heard so far. if another group feels more right, we can goi with them instead.
+**\<sarang>** I don't have a particular opinion on September vs pushing the March, since there are many other parties involved and I don't work closely enough with them to fully appreciate their needs
+**\<sarang>** I agree on the rest from a research perspective
+**\<rehrar>** ignoring needs of others for the time being, just think of the crypto
+**\<suraeNoether>** the delay of HF schedules, etc, this is all not even really MRL's job to make decisions about. the quesiton is: will BPs be implemented in the next scheduled HF for May? And I dont' think the answer to that is yes, from either me or sarang
+**\<suraeNoether>** and by "will" i mean "should"
+**\<sarang>** I consider the crypto pretty independent from the fork schedule
+**\<gingeropolous>** and by may u mean march
+**\<suraeNoether>** yeah the one starting with "ma"
+**\<rehrar>** and by dont', you mean "don't"
+**\<sarang>** Using the double blob method would be a good way to mitigate issues
+**\<sarang>** but we haven't used it before
+**\<suraeNoether>** sarang do you have expectations of security if two range proofs for the same masked amount are provided? because I can imagine at least two different ways that could go wrong if done incorrectly.
+**\<suraeNoether>** but that's highly dependent on the algebra and boosting negligible event probabilities into more likely events.
+**\<sarang>** suraeNoether: I am not worried about the two-proof method in that way
+**\<dEBRUYNE>** suraeNoether: we can go with multiple groups as well
+**\<suraeNoether>** sarang: ok we should talk more about it later then i guess
+**\<sarang>** yes
+**\<rehrar>** well, hard fork times aside, it's agreed it shouldn't be in March, and that's enough for the time being
+**\<sarang>** yes
+**\<rehrar>** good updates on the audit front
+**\<rbrunner>** But a HF in March is not entirely agreed, it seems to me ...
+**\<sarang>** But he means BPs will not be in March
+**\<sarang>** Too many audit steps before then
+**\<suraeNoether>** rbrunner: this meeting was never about HF schedules
+**\<sarang>** I'll keep everyone updated in #monero-research-lab on the OSTIF quotes
+**\<pebx>** sarang what's a real timeframe to be ready with audits?
+**\<rehrar>** MRL, let's talk about the Z.C.A.S.H (name pending) fund later today?
+**\<sarang>** Once the funds are raised and the group has a start date? A month, maybe 25 biz days
+**\<sarang>** But start dates depend on the groups' availabilities
+**\<pebx>** okay, so i'm still for delaying the hf to april or may but then with bp
+**\<rehrar>** last question, should we still have dev meeting next week, or push to three weeks from now?
+**\<pebx>** otherwise some sumo will have it before monero
+**\<janeropicasso>** Hi guys I'm new been reading along. I'd just like to say one thing. I think keeping an eye on the long term view is much better than any short term benefits unless the situation is dire. In my experience hard deadlines on things never work. Security, Privacy and Untraceability is what separates Monero high tx fees can wait.
+**\<iDunk>** I don't see this as a dev meeting.
+**\<pebx>** i would be for a dev meeting next week, but who i am...
+**\<rehrar>** alright, I'll make an issue for it on the Githubz
+**\<rbrunner>** Meet again next week, I would say, in any case.
+**\<dEBRUYNE>** janeropicasso: There will be a partial solution for fees in the next release
+**\<iDunk>** Next week is the normal schedule.
+**\<rehrar>** just don't want burnout
+**\<rbrunner>** Critical times
+**\<pebx>** rbrunner this.
+**\<rehrar>** Alright. Anything anyone else wants to say on this?
+**\<rehrar>** dEBRUYNE, can we get the logs for this too?
+**\<dEBRUYNE>** Sure
+**\<dEBRUYNE>** No ETA though :P
+**\<sgp>** I suppose I'd like to hear a bit more about fees
+**\<gingeropolous>** so, just throwing it out there - could we get one of the clones to implement? Then there's a worthy target to exploit ..
+**\<rehrar>** sgp outside the scope of this meeting I think?
+**\<rbrunner>** Yes, I don't fear Sumo implementing it at all
+**\<rbrunner>** Our fall guys :)
+**\<endogenic>** janeropicasso: i do wonder what people will prioritize. history is scary
+**\<sgp>** "Bulletproof/fees meeting" lol
+**\<rehrar>** Ah, good point.
+**\<rbrunner>** Just think that currencies normally work within time frames of decades
+**\<pebx>** rbrunner well it's some kind of an issue if someone will implement monero developed code before monero does...
+**\<sarang>** That's part of what we're trying to avoid
+**\<pebx>** at least for observers
+**\<sgp>** @dEBUYNE can you speak about what you meant by "partial fix"?
+**\<sgp>** @dEBRUYNE
+**\<rbrunner>** pebx: Reminds me of my Windows installer and the X12 coin :)
+**\<gingeropolous>** pebx, what do u mean by observers?
+**\<dEBRUYNE>** So the wallet will use low priority by default when there's no or low backlog and the last N blocks are below X size
+**\<dEBRUYNE>** Then switch to the old default once activity picks up
+**\<dEBRUYNE>** And we reasonably assume miners are going to expand the blocksize
+**\<dEBRUYNE>** It's still a bit crude and there's no perfect solution, but at least we got something going
+**\<rbrunner>** Throwing people a bone
+**\<sgp>** @dEBRUYNE, ok cool. Just curious if there was something else I missed
+**\<dEBRUYNE>** Some talk about whether we should lower the unimportant level, because it's arbitrary anyway
+**\<sarang>** So any action items before next meeting?
+**\<sarang>** Besides carry on w/ audit and start to plan funding?
+**\<sarang>** We'll need more input from core folks about the role of general funds
+**\<pebx>** gingeropolous people out of the community and people trying to attack monero and spreading disinformation...
+**\<rehrar>** hmmmm...
+**\<pebx>** i am moderating the groups on telegram so i see the "normal people talk"
+**\<rehrar>** nothing else from me on this meeting?
+**\<rehrar>** sarang even with availability of general funds, I'd like to try at least some with FFS. It's just good 'marketing'.
+**\<pebx>** but i wouldn't like to rush it either into march if it's not ready to be released...
+**\<rehrar>** Monero raises grassroots money for review
+**\<sarang>** In that case we should at least set a goal amount for this review fund
+**\<pebx>** that's a good point rehrar
+**\<sgp>** Is $50k a good goal?
+**\<rehrar>** So much is said in that Monero crowdfunds two full time researchers, two full time coders, and other stuff
+**\<rehrar>** I think add a zero to that sgp
+**\<rehrar>** if this will be used for multiple reviews over multiple years
+**\<sarang>** $50K would fund a pro audit and maybe one individual
+**\<sgp>** Ok, thought that was initial goal scope
+**\<suraeNoether>** rehrar i think if we shoot for 75-100k, and we have to pay, say, 50k this year... well... that's 25k in monero that could be worth several extra zeros by the next time we need an audit going
+**\<rehrar>** or could be worth several less zeros :P
+**\<pebx>** 500k is quite a figure... but if we can raise that for some merchandise stores to accept monero, it should be possible to do so for the tech
+**\<suraeNoether>** yeah, we can always FFS again to refresh the fund
+**\<suraeNoether>** pebx +1
+**\<sgp>** I think 100k is manageable. 500k is unrealistic to start imo. GloBee is an exception, not the norm
+**\<rehrar>** but if we think 100k is good enough to start, we can shoot for that
+**\<gingeropolous>** f'real
+**\<suraeNoether>** sgp: +1 also on that
+**\<suraeNoether>** if we need to re-up, we can
+**\<rehrar>** it can also be like the HackerOne fund
+**\<rbrunner>** Yes, it's not sexy enough for 500K
+**\<rehrar>** the goal has been met and extended a few times
+**\<sarang>** OK, I'm out for now but will keep everyone informed on audit progress
+**\<rehrar>** ok, thanks sarang
+**\<rehrar>** thanks everyone for coming. Was fairly productive I think.
+**\<pebx>** thanks sarang!
+**\<rbrunner>** Certainly interesting. Thanks!
+**\<suraeNoether>** rehrar shoot me an email at my protonmail address and cc sarang on it and we'll start talking about a review fund and the FFS post for it
+**\<rehrar>** sure thing
+**\<sarang>** or in the MRL IRC if you want it public
+**\<rehrar>** I prefer sneaking behind closed doors
+**\<suraeNoether>** hmm. i was thinking its not totally on topic for #monero-research-lab but maybe it is...
+**\<dEBRUYNE>** 100k seems a bit on the lower end, whereas 500k seems a bit on the high end
+**\<rehrar>** the research lounge
+**\<dEBRUYNE>** Perhaps something in between would be best
+**\<rehrar>** discuss it over a vape
+**\<sarang>** $133,700
+**\<rehrar>** $250k? dEBRUYNE?
+**\<pebx>** 222.222
+**\<rehrar>** sarang: and fifty two cents
+**\<rbrunner>** Don't we have any nice prime number somewhere there?
+**\<pebx>** however, why are we talking in fiat?
+**\<dEBRUYNE>** rehrar: something like that
+**\<sarang>** pebx because The Man has taught me to think in fiat
+**\<rehrar>** wonder how many of these reviewers would accept XMR directly
+**\<suraeNoether>** the OSTIF accepts crypto apparently
+**\<suraeNoether>** but they pay the groups in fiat
+**\<sarang>** OSTIF will do the exchange for us fee-free
+**\<suraeNoether>** that's nice
+**\<sarang>** and OSTIF agreed to take no cut themselves if we credit them
+**\<rehrar>** they want the Monrus
+**\<sarang>** they want to drum up publicity for a larger upcoming audit
+**\<pebx>** 727 XMR would be a prime number ;)
+**\<rehrar>** alright friends, Imma kick rocks. Catch you all later.
+**\<manifest>** there probably isnt a tool for monero where you could monitor and control multiple wallets easily for testing purposes
+**\<fluffypony>** pebx: I was arguing with a BCash shill, and it was at a time when we were more confident about March
+**\<sarang>** We can still present the delay positively
+**\<sarang>** We're trailblazing but doing it correctly
+**\<fluffypony>** was there a reasonable sense of consensus on the way forward wrt the HF schedule?
+**\<Maxithi>** fluffypony Not really, there are two main options and we didn't find an global agreement.
+**\<fluffypony>** we're starting to run tight on time
+**\<Maxithi>** fluffypony Yeah, however everyone did agree that by postponing BP we still have 2-3 weeks to find a consensus on the HF.
+**\<fluffypony>** in situations like this the best thing to do is the thing that isn't controversial, which means not including it until it's ready
+**\<fluffypony>** we wanted to do code freeze at the end of Dec / beginning of Jan
+**\<fluffypony>** so not really
+**\<iDunk>** Is there going to be a new branch for the new release ?
+**\<Maxithi>** Main arguments were PRO: HF forces community to update software. AGAINST: No protocol update requires HF.
+**\<fluffypony>** yes
+**\<Maxithi>** And then the fact that HF are "supposed" to be on a regular basis (based on HF history).
+**\<Maxithi>** And again some Pro and Against
+**\<fluffypony>** we've always maintained that the HF should happen even if there's no protocol update
+**\<fluffypony>** to keep active versions in line
+**\<fluffypony>** and prevent things like the Bitcoin leveldb / bdb bug
+**\<Maxithi>** @fluffypony: we've always maintained that the HF should happen even if there's no protocol update \<= No one brought that argument up, would have been a good one.
+**\<iDunk>** In this case, using subaddresses and multisig will require using the new release.
+**\<endogenic>** yes i did :P
+**\<iDunk>** And having people be forced to upgrade avoids support nightmares.
+**\<fluffypony>** yep
+**\<fluffypony>** I mean, unless there's a strong reason NOT to do a March fork we should go ahead with it
+**\<Maxithi>** endogenic: yes i did :P \<= Than it is my mistake. Didn't understand that it was stated as a previous consensus. I read it rather as a habbit.
+**\<endogenic>** Maxithi: i was just being more socratic about it :P
+**\<endogenic>** Maxithi: since i dont know what i know yet
+**\<Maxithi>** endogenic You should have been more straight forward.
+**\<fluffypony>** and then leave it open-ended for Bulletproofs
+**\<endogenic>** Maxithi: i was
+**\<endogenic>** Maxithi: i was responding to someone else and he understood and agreed with me
+**\<Maxithi>** Why hasn't this been written down already? We should put up these kind of consensus rules and drop them on git to prevent future disagreements.
+**\<Maxithi>** endogenic My bad, didn't catch that through the lines.
+**\<endogenic>** Maxithi: arent consensus rules derived from people not documents
+**\<endogenic>** besides who wants to prevent discussion
+**\<fluffypony>** it's a good idea to at least write down how we generally feel things should be handled
+**\<fluffypony>** almost like a doctrine, not really a list of rules
+**\<Maxithi>** endogenic Agree but this could prevent from turning 1 meeting into 4
+**\<Maxithi>** Doesn't mean we can't change it ;) Only that we take what we previously achieved and discuss on top of that
+**\<endogenic>** now that BPs have been merged, can a new release which excludes BPs be done?
+**\<endogenic>** single output , if specificity is needed
+**\<fluffypony>** endogenic: they're merged but dormant
+**\<endogenic>** ah, of course, that makes sense
+**\<rbrunner>** But we probably new a second, non-BP testnet
+**\<fluffypony>** yes I agree on the testnet / devnet thing
+**\<rbrunner>** Ah, yes, those were the proposed names
+**\<fluffypony>** I think the real problem here is that Bulletproofs doesn't have a cool name
+**\<fluffypony>** I mean, it's reasonably cool
+**\<fluffypony>** but how can we compete with VVraith Protocol?
+**\<rbrunner>** :)
+**\<chachasmooth>** is wraith the guy who claimed to be satoshi?
+**\<fluffypony>** chachasmooth: no, it's the stealth addresses thing that Verge is doing
+**\<chachasmooth>** oh, right. both are shit, that's what I remember
+**\<chachasmooth>** wraith is still not implemented?
+**\* fluffypony** shrugs
+**\<chachasmooth>** fluffypony what happened to the majority of forum posts? did you take them offline on purpose?
+**\<fluffypony>** censored by Blockstream
+**\<fluffypony>** kidding, we disabled them because of the spam, I'll fiddle with the settings so that they're still visible
+**\<Maxithi>** fluffypony About spam, the forum has some https://forum.getmonero.org/6/ideas/89759/advice-for-you-to-get-free-600m-swtor-credits-cheap-on-swtor2credits-jan-17
+**\<Maxithi>** Who can remove these?
+**\<fluffypony>** tks
+**\<fluffypony>** any of the mods
+**\<fluffypony>** but I'm pretty much the only one active
+**\<Maxithi>** I'm sure your schedule is empty and you love handling this kind of stuff ;)
+**\<fluffypony>** lol
+**\<rbrunner>** Just checked: Wraith is really, finally online, but seems to have some teething problems: https://steemit.com/bitcoin/@siddm96/verge-hardfork-for-stealth-transaction-3a0509e274618
+**\<rbrunner>** See? Other coins can hardfork just like that. Why can't we?
+**\<rbrunner>** Was checking about 30 transactions on the Verge blockchain and did not encounter a single one with stealth addresses. Roaring success, it seems
+**\<fluffypony>** lol
+**\<iDunk>** Imagine if subaddresses were being without a hard fork :)
+**\<iDunk>** Major clusterfuck.
+**\<rbrunner>** That's my opinion: We need the March hardfork just to force lazy people to update their software
+**\<iDunk>** Exactly.
+**\* sgp** sent a long message: https://matrix.org/_matrix/media/v1/download/matrix.org/BarHGxHdPoPajSqUqUpcKEFm
+**\<gingeropolous>** thanks matrix
+**\<bibble>** lol
+**\<bibble>** guess #3 would mean more pumps, more money ??
+**\<sarang>** That's not quite correct. We aren't planning on having single-output audited
+**\<sarang>** If there's a pressing need for single, we restrict transactions to a single-output proof within the multi code
+**\<sarang>** A single-output proof is just the degenerate case of a multi-output
+**\<chachasmooth>** what benefits do regular hard forks bring?
+**\<jorko>** regular upgrades. avoids the Bitcoin clusterfuck where consensus = no protocol upgrades, ever.
+**\<gingeropolous>** it also helps improve the software, because everyone is running the same thing. So we all have the same bugs if they are present.
+**\<sgp>** @sarang my apologies, I didn't know that
+**\<sgp>** I'll have to think harder about this
+**\<sarang>** When we think about single vs multi output proofs from now on, we should consider that they're really different cases of the same final code
+**\<sarang>** The difference is really in whatever we decide to do for the corresponding fee structure
+**\<sarang>** Yes, the original "single only" code is on testnet, but moneromooo has the multi code worked up now
+**\<sgp>** @sarang once the multi-output code has been reviewed, is there a reason to add it separately from single-output, or would you feel comfortable adding both at the same time?
+**\<sarang>** The multi code completely replaces the single code
+**\<sarang>** development was done separately in case we finished single first and wanted to deploy sooner
+**\<sarang>** a single-output proof is just a multi-output proof with one output
+**\<sgp>** So realistically the community has decided that single-output is a waste of time because multi-output is basically done and the community wants it audited
+**\<sarang>** Given the desire for an audit, it makes sense to jump straight to multi and have the fee discussion surrounding it
+**\<sgp>** Ok, makes sense
+**\<sgp>** So it's basically just a question of whether Monero hardforks soon after the code is complete and reviewed or in September
+**\<sgp>** For some reason I still thought single and multi-output would be rolled out separately
+**\<sarang>** Single doesn't require that the fee structure be switched away from size-based, but that's about it
+**\<sarang>** Might as well pay for only one audit
+**\<sgp>** I understand skipping single-output bulletproofs
+**\<sarang>** What it does mean is that the BP code on testnet is NOT the code that will be audited or eventually deployed
+**\<sarang>** for whatever that's worth
+**\<sarang>** Multi is here: https://github.com/moneromooo-monero/bitmonero/tree/bp-multi/src/ringct
+
\ No newline at end of file
diff --git a/_posts/2018-01-28-overview-and-logs-for-the-dev-meeting-held-on-2018-01-28.md b/_posts/2018-01-28-overview-and-logs-for-the-dev-meeting-held-on-2018-01-28.md
new file mode 100644
index 0000000000000000000000000000000000000000..b0f4720a597b01c80478586a119b58d807f0bc0d
--- /dev/null
+++ b/_posts/2018-01-28-overview-and-logs-for-the-dev-meeting-held-on-2018-01-28.md
@@ -0,0 +1,218 @@
+---
+layout: post
+title: Overview and Logs for the Dev Meeting Held on 2018-01-28
+summary: Discussion of open PRs and issues, Bulletproofs, March HF, fees, Debian package, GUI update, and miscellaneous
+tags: [dev diaries, core, crypto]
+author: dEBRUYNE / fluffypony
+---
+
+# Overview
+
+An overview can be found on [MoneroBase](https://monerobase.com/wiki/DevMeeting_2018-01-28).
+
+# Logs
+
+**\<hyc>** meeting time
+**\<rehrar>** ye
+**\<rehrar>** agenda: https://github.com/monero-project/meta/issues/166
+**\<rehrar>** as always, start with 1. Greetings
+**\<sarang>** yo
+**\<msvb-lab>** Hi there.
+**\<hyc>** hey
+**\<rbrunner>** Hoi zämme
+**\<iDunk>** Hi
+**\<pebx>** hi
+**\<rehrar>** ArticMine fluffypony luigi1111 luigi1111w smooth NoodleDoodle anonimal anonimobile endogenic gingeropolous vtnerd pigeons
+**\<pigeons>** hi
+**\<vtnerd>** hi
+**\<rehrar>** dEBRUYNE Jaquee dsc dsc2 ?
+**\<gingeropolous>** oh theres a meeting?
+**\<rehrar>** anyone else?
+**\<endogenic>** no ginger
+**\<iDunk>** moneromooo
+**\<dEBRUYNE>** I am her
+**\<dEBRUYNE>** e
+**\<rehrar>** medusa moneromooo othe
+**\<smooth>** 1
+**\<rehrar>** Well, welcome everyone! :)
+**\<rehrar>** 2. Brief review of what's been completed since the previous meeting
+**\<rehrar>** Anyone have any exciting stuff to report for development?
+**\<medusa>** hi
+**\<sarang>** MRL Goes To Stanford
+**\<sarang>** It was observed that bulletproofs can have batch verification, which will be great time savings even between separate transaction
+**\<ArticMine>** hi
+**\<bearretinjapan>** hi
+**\<hyc>** batching is always interesting. have to balance batch size vs latency, waiting for enough txs to arrive to fill a batch
+**\<sarang>** This can be useful for new nodes
+**\<smooth>** currently the code waits for all the txs before doing anythign with them anyway, although that could change
+**\<sarang>** Initial testing by andytoshi indicated that subsequent proofs were only ~15% of the time complexity of a separate verification
+**\<hyc>** nice
+**\<sarang>** Yeah, it merges all the multiexp operations into one
+**\<sarang>** effectively replacing group operations with scalar operations
+**\<sarang>** So the time savings really depend on the relative timing between those ops
+**\<sarang>** Anyway, mostly excellent talks at the conference, and good lessons learned
+**\* sarang** will be quiet now
+**\<rehrar>** Anyone else? :) GUI have anything?
+**\<medusa>** the GUI project has merged sub addresses. also we removed the ability for the user to generate payment ids and integrated addresses
+**\<medusa>** in addition, there is a new monerod start up flag, called --boostrap daemon https://github.com/monero-project/monero/pull/3165
+**\<hyc>** ^^ this looks very good. I wonder if the GUI should use that by default
+**\<medusa>** the GUi will make use of this too, so there dont exist several implementations of the same thing
+**\<gingeropolous>** is that supplanting Jaquee 's thing?
+**\<medusa>** PR is allready here hyc https://github.com/monero-project/monero-gui/pull/1091
+**\<medusa>** gingeropolous:as far as i understand it, yes
+**\<rehrar>** I'll repaste xmrscott[m]'s message so people who don't want to click don't have to
+**\<rehrar>** David Mirza Ahmad, president of Subgraph OS, has put together a byte-for-byte matching Debian package and is requesting comment on some final pieces: "There some decisions to make for us, like: where does the blockchain data go? Do we start the daemon with systemd by default (feeling like no, as it can be started in GUI)? Appreciate thoughts on this." No one has provided comments on these matters so if anyone here could do so it woul
+**\<rehrar>** d be appreciated. https://github.com/monero-project/monero/issues/2395
+**\<rehrar>** \^
+**\<pebx>** thanks for the update medusa! this looks very good. we shouldn't forget that GUI is the interface to the rest of the world...
+**\<msvb-lab>** rehrar: Byte for byte matching, you mean as in reproducible build? Gitian?
+**\* rehrar** applauds the GUI people for their consistent quality work
+**\<pigeons>** I looked at his repo and i didnt see the debian control files to reproduce
+**\<rehrar>** xmrscott[m] \^ msvb-lab's question
+**\<ArticMine>** Any idea on timeline from an update at out end to the repo?
+**\<xmrscott[m]>** I believe so. I'm not familliar with build terminoogy,
+**\<xmrscott[m]>** The sha256 sums match: d5b0295d55f9951a6995e2ecc1516898799b22686ed81ca07b05b493175f2f66
+**\<xmrscott[m]>** (THis is shown on the comments in the GitHub issue)
+**\<rehrar>** Any answer for ArticMine's question?
+**\<hyc>** unknowable
+**\<rehrar>** bam
+**\<hyc>** distro release schedules are seldom anywhere near upstream release cycles
+**\<ArticMine>** My concern is stale Monero in the distro
+**\<hyc>** yes
+**\<hyc>** it's a frequent occurrence in distro packages
+**\<ArticMine>** With a six month hard for cycle
+**\<ArticMine>** fork
+**\<hyc>** which is why I've never put much priority on distrok packaging. reproducible builds are a good thing in and of themself though.
+**\<rehrar>** Alright, if nothing else, we can move on to 3. March hardfork items + code freeze
+**\<rehrar>** Anything to be discussed about the upcoming hard fork? Is there a code freeze date yet?
+**\<dEBRUYNE>** Preferably very soon. Then we don't have to rush stuff
+**\<ArticMine>** ... and bulletproofs
+**\<sarang>** What about BPs?
+**\<hyc>** seems they're off the table for March, since audits haven't been completed
+**\<hyc>** 3rd party audits
+**\<sarang>** Correct
+**\<rehrar>** missed the meeting last week ArticMine
+**\<rbrunner>** Have any been *started* in the meantime?
+**\<sarang>** I'm waiting on a formal SoW from one of the groups
+**\<sarang>** Then I'll present my recommendations among all groups
+**\<medusa>** since BP seems to be off the table, is the new wallet option the only planned change to address current high fee situation ?
+**\<sarang>** We're looking at ~40K per professional audit
+**\<sarang>** and hopefully get benedikt to do a review of at least the Java since he wrote the damn thing
+**\<sarang>** for $
+**\<rehrar>** medusa: we should crash the price in the meantime
+**\<sarang>** Should we include batch BP verification in the audited code?
+**\<sarang>** Or put that aside
+**\<endogenic>** rehrar: was that a preannouncement? :)
+**\<endogenic>** sarang: perhaps as optional extra credit?
+**\<hyc>** we should audit whatever we hope to release in Sept.
+**\<hyc>** otherwise we'll just need to do all this again for each incremental improvement. ??
+**\<sarang>** It'll be included in an updated whitepaper in Feb
+**\<sarang>** by benedikt et al., not by me
+**\<rbrunner>** Well, maybe plan in a way that makes pretty damn sure we will be ready in September :)
+**\<pebx>** what about the fees medusa mentioned? it's also something the average user sees first and complains about... if we don't release BPs there should be some lowering of fees beside the low to standard thing
+**\<dEBRUYNE>** I suppose we can discuss lowering the low priority level since it's arbitrary anyway, but we can't lower the default because we'd have to tweak the penalty as well
+**\<ferretinjapan>** BPs being released in March was also cited as a reason for onot loweiring fees.
+**\<smooth>** we can lower the default a little i think, but no one has taken the time to study it
+**\<smooth>** so actually no, we can't
+**\<sarang>** As to BP funding, I plan to open an FFS with "checkpoints" for an amount covering at least one pro audit and another for a review by one of the paper authors
+**\<endogenic>** i was just going to ask about that, smooth
+**\<smooth>** 'default' isn't really the right term though. the pending PR changes the 'default' to be dynamic
+**\<dEBRUYNE>** old default then? :P
+**\<smooth>** yeah "medium" whatever you want to call it
+**\<smooth>** "normal"
+**\<rbrunner>** base fee?
+**\<dEBRUYNE>** smooth: any opinion about lowering the lowest level?
+**\<smooth>** etc.
+**\<rehrar>** Base fee sounds good
+**\<smooth>** base fee doesn't seem like the best term to me
+**\<smooth>** implies that is actually the fee you pay
+**\<smooth>** it is more like a 'fee reference value' or something
+**\<rehrar>** I think it should be more than 'medium' though, because it's the one that will increase the block size. Something a little more souped up than 'medium'?
+**\<ferretinjapan>** floating reference fee?
+**\<rehrar>** Either way, thoughts on lowering the arbitrary 'Low Fee'?
+**\<ArticMine>** We have to be careful with the low fee level relative to the 1 tx at penalty (default)
+**\<ArticMine>** Spam attacks becomes possible if the probability of mining becomes too low
+**\<pebx>** the crypto "market" might crash in the meantime, but it also might not and what if monero's market price until september rises like within the last 8 months?
+**\<smooth>** ArticMine: but doesn't the probability of mining just depend on how many of each there are and not the fee amount?
+**\<pebx>** the minimum fee is a good protection but also a pain...
+**\<smooth>** the issue i see with too much of a gap between levels is the incentive to circumvent (just bump up your own fee a little so you are above all the others in the same level but not all the way to the next level)
+**\<dEBRUYNE>** pebx: I'd leave any price predictions out of this discussion. Tomorrow's price is most likely today's price
+**\<smooth>** the more gap the greater the incentive to do that
+**\<pebx>** dEBU
+**\<pebx>** is it not about price when it comes to fees?
+**\<smooth>** other than that the low level seems aalmost comletely arbitrary to me
+**\<dEBRUYNE>** Price surely influence fees (as they are denominated in XMR). I was just saying that we should leave *price* prediction out of it
+**\<rehrar>** Well if we want a code freeze "soon", we should try to decide this "soon" too, no? Or would this not be affected really by the freeze?
+**\<dEBRUYNE>** *prediction*
+**\<ArticMine>** I mean how low on the min fee do people want to go?
+**\<endogenic>** can we put together a study on fees and spam? having a shared model (and simulated results) we can reference and improve collectively would be great… certainly would ease the knowledge gap
+**\<pebx>** i didn't want to include any prediction, so i told it might continue or not
+**\<dEBRUYNE>** smooth: I guess if we had 1/5th or 1/6th (current is 1/4th) the gap would be still sufficiently small? Also people would have to tweak the code and compile it themselves to make use of the gap
+**\<smooth>** endogenic: it has been done. we can do another one but until it is done we can't rely on it
+**\<endogenic>** smooth: do you mean the recent writeup?
+**\<smooth>** endogenic: that one, the older one. whatever is done we can rely on. we can't rely on something that is 'can we do' especially with an imminent freeze
+**\<smooth>** of course we can do more studies
+**\<endogenic>** smooth: i would only suggest inaction until after study/ confirmation
+**\<ArticMine>** and then nothing for March, after which we will have BP
+**\<rehrar>** Which brings us full circle :P
+**\<moneromooo>** Can we finish the meeting first, and go back to the fee stuff ?
+**\<endogenic>** lol mooo
+**\<rehrar>** Alright. Moving on then! 4. Code + ticket discussion / Q & A
+**\<pebx>** nice to see you, mooo
+**\<dEBRUYNE>** pebx: Your sentence sounded like that, hence my statement. I could've misinterpreted you though.
+**\<ArticMine>** I sugest we leave fees aslon for March or at most introduce the wallet side adaptive fee between default and min
+**\<ArticMine>** alone
+**\<medusa>** thats allready merged afaik ArticMine
+**\<smooth>** the adaptive should go in if at all possible from a stability perspective imo
+**\<smooth>** oh i didn't know it was merged. great
+**\<pebx>** dEBRUYNE my point is, that at some point fees can get insane like they have been / are in bitcoin
+**\<ArticMine>** Then if it is merged that is all
+**\<gingeropolous>** ^^
+**\<medusa>** this one no ? https://github.com/monero-project/monero/pull/3123
+**\<smooth>** yes. lets move on: rehrar>** Alright. Moving on then! 4. Code + ticket discussion / Q & A
+**\<rbrunner>** I have a little thing: The Windows installer missed the Fall releases. But surely the March release is a perfect opportunity to finally put it into service ...?
+**\<hyc>** yeah sounds like we're fine for now on fee
+**\<gingeropolous>** all this code and ticket discussion
+**\<iDunk>** 3186 and 3198 need merging to fix some builds.
+**\<rbrunner>** I hope it's not itself controversial that having a Windows installer would be nice
+**\<medusa>** absolutely rbrunner, the worlk load regarding that is mostly on the shoulder of the binary builder (pony). we cant really do anything to speed it up i fear
+**\<rbrunner>** Ah well, March is early enough :)
+**\<rbrunner>** Just do not forget it :)
+**\<luigi1111>** I personally prefer portable exe but both are fine with me
+**\<moneromooo>** "portable" and "exe", hmmm :)
+**\<hyc>** lol
+**\<dEBRUYNE>** pebx: I surely hope the dynamic fee algo has kicked in by then. Anyway, I'll refrain from commenting on fees now.
+**\<luigi1111>** :)
+**\<pebx>** dEBRUYNE hope is good... but i'll also not comment fees in this meeting any more.
+**\<rehrar>** Anything else for code and ticket discussion?
+**\<rehrar>** 5. Any additional meeting items (besides fees)?
+**\<msvb-lab>** Or hardware questions.
+**\<rehrar>** did you want to share something msvb-lab?
+**\<msvb-lab>** Nothing to share. We're working on the next gen prototype.
+**\<msvb-lab>** Questions are welcome in any case.
+**\<rehrar>** Alright then.
+**\<rehrar>** 6. Confirm next meeting date/time
+**\<rehrar>** Feb 11th?
+**\<hyc>** sounds right
+**\<rehrar>** luigi has mentioned a couple times about switching the time
+**\<hyc>** btw, I'll be at FOSDEM next week. anyone else going?
+**\<medusa>** i want to thank everyone that is working on making the build envs green. you guys are heros **\<3
+**\<rehrar>** don't know if he was serious, but does anyone else agree?
+**\<hyc>** switch to what time?
+**\<msvb-lab>** hyc: I'll be there too, at FOSDEM in Bruxelles.
+**\<rehrar>** luigi1111 luigi1111w?
+**\<rehrar>** I guess just as a general question, is this time inconvenient for other people?
+**\<hyc>** seems ok to me
+**\<rehrar>** hyc has spoken
+**\<moneromooo>** IIRC ArticMine objected.
+**\<rehrar>** I'll probably open a meta issue and ask for opinions.
+**\<ArticMine>** I would prefer an hour earlier
+**\<hyc>** good idea
+**\<rehrar>** For now we can have next dev meeting same time, and see about moving others.
+**\<endogenic>** i'm fine with an hour earlier
+**\<rehrar>** Sound ok for everyone?
+**\<pebx>** hyc can't wait for your talk to see it at least online!
+**\<rbrunner>** Yes, one hour earlier is ok as well
+**\<rehrar>** Hmmm...ok, tentative next meeting time Feb 11 at 16:00 UTC
+**\<rehrar>** The time will be open for discussion on the meeting issue
+**\<rehrar>** Meeting over. Thanks for coming everyone. You're all the best, and don't let anyone tell you otherwise.
\ No newline at end of file
diff --git a/_posts/2018-01-29-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-01-29.md b/_posts/2018-01-29-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-01-29.md
new file mode 100644
index 0000000000000000000000000000000000000000..6b49f79409789c80e02df196acc2ac5058a9f674
--- /dev/null
+++ b/_posts/2018-01-29-logs-for-the-Monero-Research-Lab-meeting-held-on-2018-01-29.md
@@ -0,0 +1,256 @@
+---
+layout: post
+title: Logs for the Monero Research Lab Meeting Held on 2018-01-29
+summary: MRL direction, ideas for research, and miscellaneous
+tags: [community, crypto, research]
+author: dEBRUYNE / fluffypony
+---
+
+# Logs
+
+**\<sarang>** Let us begin
+**\<suraeNoether>** howdy everyone!
+**\<suraeNoether>** maybe we should ping people
+**\<endogenic>** vtnerd smooth fluffypony othe stoffu knaccc ArticMine kenshi84 pigeons gingeropolous dEBRUYNE
+**\<endogenic>** :P
+**\<endogenic>** ferretinjapan
+**\<endogenic>** silur (absent?)
+**\<endogenic>** hyc
+**\<endogenic>** endogenic
+**\<suraeNoether>** fluffypony luigi1111 andytoshi anonimal dEBRUYNE endogenic ErCiccione gingeropolous hyc vtnerd smooth othe stoffu silur ArticMine kenshi84 pigeons john\_alan medusa Mouchicc nioc unknownids
+**\* andytoshi** breakfast meeting, afk, sorry
+**\<anonimal>** Hello
+**\<ErCiccione>** Hi! (thanks for the ping)
+**\<suraeNoether>** So, today I want Sarang and I to give an account of our experience at BPASE18, and then talk about the January roadmap
+**\<hyc>** hey
+**\<suraeNoether>** and our overall work for this year
+**\<suraeNoether>** if anyone is curious, I live-tweeted the majority of talks at BPASE
+**\<sarang>** Several talks highlighted topics relating to smart contracts that have little relevance to us
+**\<sarang>** However, there were talks on SPECTRE/PHANTOM and bulletproofs that were well presented and well received
+**\<sarang>** among many others
+**\<sarang>** We'll be able to integrate a brand-new batch verification technique for bulletproofs
+**\<suraeNoether>** yes, that was big news
+**\<suraeNoether>** PHANTOM is sort of an interesting layer on top of SPECTRE, which leads to probabilistically picking only honest blocks, interesting analysis led to that
+**\<suraeNoether>** also, it turns out bulletproofs are crazy adaptible
+**\<suraeNoether>** like, you can put SHA256 into a bulletproof and proof that you know the pre-image to a hash
+**\<suraeNoether>** without revealing the pre-image
+**\<suraeNoether>** etc
+**\<suraeNoether>** very interesting stuff
+**\<sarang>** Mhmm, it's a general tool for arithmetic circuits
+**\<sarang>** Anyone else working on fun research they wish to share as well?
+**\<hyc>** very cool... all of this raises a question in my mind - when do we consider "new" technology to be "mature" ?
+**\<hyc>** we're taking extra care integrating BPs because they're "new"
+**\<anonimal>** When we stop saying sha256 ;)
+**\<anonimal>** How does sha384/512 fit into the picture?
+**\<sarang>** Maybe when people stop being excited about it and consider it just a tool?
+**\<suraeNoether>** that's a good question hyc
+**\<suraeNoether>** here's the thing: our current impelmentation of bullet proofs is specifically a range proof implementation
+**\<suraeNoether>** iirc
+**\<sarang>** yes
+**\<suraeNoether>** so in order ot make it to other things, we need to make new implementations
+**\<suraeNoether>** so the failure model or threat model for each implementation will be different
+**\<sarang>** Not necessarily. The security model for ACs is pretty well defined
+**\<sarang>** We just happen to only be using these for range proof
+**\<suraeNoether>** the reason it is so important to validate our implemenation of BP-range-proofs is because if that breaks, then people can mint money. but if we implement some other NIZK proof of knowledge with a BP, we may not need to be so nervous, because the failure of the new implementation may be small in scale, as opposed to "free-mint-ALLTHEMONEY" sort of failure model
+**\<suraeNoether>** sarang yeah: for a general AC the implementation analysis i usppose will boil down to analyzing the AC
+**\<sarang>** yes
+**\<hyc>** ok, makes sense. thanks surae
+**\* suraeNoether** thumbs up
+**\<suraeNoether>** In addition to that, gmaxwell had a brilliant idea on bug bounties
+**\<suraeNoether>** but it only kind of works for their implementation of libsecp256k1, because they have a super robust test suite
+**\<suraeNoether>** the idea is to put a bug bounty up for altering the test suite in a way such that all current tests *still pass* but you have uploaded some sort of other test that fails despite that
+**\<suraeNoether>** so if I can put a new test into the test suite, call it D, and the test suite already has tests A, B, and C... if D is a failure but A,B,C still pass, then you essentially found a new test and a new weakness, so boom, you get the bug bounty
+**\<suraeNoether>** not super helpful in our situation because our test suites are not yet robust
+**\<suraeNoether>** but it's an interesting model of bug bounties and unit tests
+**\<sarang>** Perhaps we should move on to the roadmap to allow plenty of time to discuss?
+**\<suraeNoether>** yep
+**\<suraeNoether>** So, here's the deal
+**\<suraeNoether>** well one of many deals
+**\<suraeNoether>** sarang and I are sort of trying to figure out which direction MRL should go over the next year
+**\<suraeNoether>** and we need input. Other htan writing up the Monero Standards, and finishing the multisig paper... we sort of suffer a problem where work is done in jerks and starts
+**\<sarang>** It's partly the unfortunate nature of research
+**\<suraeNoether>** like a few weeks will go by with apparently not too much to get done, then BOOM all of a sudden it's time to implement and review bulletproofs or BOOM, rtrs ringct or whatever
+**\<sarang>** I mean, I want to continue a deeper investigation of DAG structures and consensus models
+**\<suraeNoether>** and that makes it feel like we're *reactive* instead of proactive
+**\<sarang>** I think that will become increasingly more important
+**\<suraeNoether>** yeah, i do too
+**\<suraeNoether>** i've been working on an adaptable population-driven model of a cryptocurrency network to assess dynamics and how various algorithms affect them. for example, if we want to study a different consensus model or a different PoW algorithm or if we want to study how difficulty metrics respond to changes in hashrate, etc
+**\<suraeNoether>** so we can model long-term scaling issues on a controlled simulation
+**\<sarang>** Smaller things include broader implementation of curve/scalar optimizations, but that's just housekeeping stuff
+**\<suraeNoether>** I also have been working on SPECTRE and finishing up the multisig paper
+**\<sarang>** Developing outreach curricula is a non-research side of things, of course, but I believe still important for this group
+**\<suraeNoether>** which, btw, after speaking with pietr wuille in Zurich and Stanford, two separate routes an attacker could take have been made clear to me. One of them our code already accounts for. The other is something I need to speak with luigi1111 and moneromooo about
+**\<sarang>** In what regard?
+**\<hyc>** multisig?
+**\<suraeNoether>** yes for multisig i mean
+**\<suraeNoether>** there is a simple-ish fix too
+**\<suraeNoether>** it's not a huge deal, but it's a big enough deal that I want to speak in private with folks about it before proceeding
+**\<gingeropolous>** would it be worth investing time in a network simulator? i know there are various blockchain / p2p sims out there, and it might be more of a technical issue (more admin than research) ....
+**\<sarang>** Depends on what we want to model
+**\<suraeNoether>** gingeropolous: that's sort of what i'm coding. i'm dissatisfied with several of the other pieces of simulation software out there
+**\<hyc>** are you talking open source projects that we can tweak to suit ourselves?
+**\<suraeNoether>** of course
+**\<hyc>** \^ to ginger actually
+**\<suraeNoether>** oh i see what you mean hyc
+**\<suraeNoether>** yeah my mistake
+**\<gingeropolous>** im imagining something public facing, with a GUI so an average user can go "oh lets drop the fee to 0.0001 and see what happens"
+**\<gingeropolous>** some web interface
+**\<suraeNoether>** ah so gingeropolous
+**\<gingeropolous>** but that could be phase 2
+**\<suraeNoether>** forget about fees, because i'm oinly looking at block dynamics
+**\<sarang>** You'd need a much deeper understanding of how nodes/users respond to such factors though?
+**\<suraeNoether>** not transaction dynamics
+**\<suraeNoether>** but the point is to eventually build it up to do that sort of thing
+**\<gingeropolous>** cool
+**\<hyc>** quite a lot of variables to model
+**\<suraeNoether>** animate it with ggplot or something to make pretty videos
+**\<suraeNoether>** hyc yep, it's a very general model, makes it suitable for arbitrary plug-n-play sort of analyses
+**\<suraeNoether>** but back to the roadmap
+**\<suraeNoether>** i guess what i'm asking is:
+**\<suraeNoether>** what do people want to see out of MRL over the next 6 months?
+**\<suraeNoether>** other than the completed multisig paper
+**\<sarang>** To be honest, I don't think the broader Monero community really has specific opinions on research directions, if that's what you mean
+**\<suraeNoether>** hyc you are never opinion-less
+**\<hyc>** lol
+**\<hyc>** All the things you already outlined sound like important goals to me. some of it sounds like we need more people.
+**\<moneromooo>** Modelling of spent output age. Take real distribution since last release, subtract the distribution we use, get the real distribution. See if it matches miller et al.
+**\<hyc>** "get the real distribution" --> how?
+**\<moneromooo>** Then try to do that at several historical times, every month maybe. And then deduce a formula to vary gamma function over time to use a new fake outdistribution.
+**\<moneromooo>** By subtracting the fake outs distribution from the real+fake one.
+**\<moneromooo>** May or may not be good enough, I don't know.
+**\<suraeNoether>** moneromooo: if we can get a bayesian estimate that updates each hard fork, that'd be great, but it requires being able to "unmask" transactions to see their real spendable output, or to base the estimate on transactions that have already been "unmasked", or to base the estimate on another currency. Each of these have obstacles, obviously
+**\<suraeNoether>** we need some ground truth underlying data to make an estimate, and monero doesn't really allow for that
+**\<ErCiccione>** The community is pushing a lot the "fee are too high" thing and i feel will be worst with time passing. Is it possible to produce some documentation to instruct people about how Monero fees work and what are the plans for the future on this matter?
+**\<moneromooo>** I was suggesting deducing the real outs distribution.
+**\<ErCiccione>** i also agree with hyc, er should search fore more researchers
+**\<sarang>** I hear gmaxwell is unattached =p
+**\<moneromooo>** This would be assuming all txes since last release use our fake outs distribution, though, which mymonero might not. Damn.
+**\<hyc>** to some extent, that's all good news - it means the system is no longer analyzable.
+**\<dEBRUYNE>** ErCiccione: I wrote a blog about it, you can link that
+**\<suraeNoether>** so, ErCiccione: yes, fees are an important part of the discussion around bulletproofs. you are corredct that we should at least put out a statement
+**\<suraeNoether>** hyc: without access to KYC/AML data from an exchange, anyway :D
+**\<suraeNoether>** i suppose we could ask for some sanitized data from one of the exchanges...
+**\<suraeNoether>** actually that's the first time that i've been hopeful about deducing true age distribution
+**\<suraeNoether>** but here's the REAL problem
+**\<ferretinjapan>** does the current research on multisig cover more complex things like assurance contracts? I think people would definitely be keen to help fund research in enabling those types of things.
+**\<suraeNoether>** ferretinjapan: the current paper will not cover that except lightly, but i would loooove to write up a document on "applications of multisig in nearly-smart contracts."
+**\<suraeNoether>** let's say there's a really massive anonymity set: the probability of picking any one of them out for usage in a ring is really really small
+**\<ferretinjapan>** Because that could mean 100% decentralised FFS :)
+**\<suraeNoether>** and if you pulled randomly from the whole blockchain...
+**\<suraeNoether>** then the true output you are signing with *probably* hasn't been used in a signature before
+**\<suraeNoether>** and more people got into monero recently rather than in 2014
+**\<suraeNoether>** so the output being spent is *probably* the youngest one
+**\<hyc>** true
+**\<suraeNoether>** and this will *always* be the case, unless we make wallet software actively try to de-anonymize the blockchain and we publish a blacklist of known-spent outputs
+**\<suraeNoether>** or unless we make wallet software that tries to pick as many transactions from "recently" that have not yet been used in any ring signature
+**\<suraeNoether>** another way of looking at this: the first ring signature an output appears in *is likely* to be the one that actually spends it
+**\<suraeNoether>** it's not so much a matter of the age of the output
+**\<ErCiccione>** dEBRUYNE: right, i forgot about that, but i still think we should be more informative about fees, i see a lot of confusion in the average user, at least on reddit,
+**\<suraeNoether>** but how many other ring signatures already reference it
+**\<suraeNoether>** ErCiccione: absolutely +1
+**\<suraeNoether>** okay, so fees are going on my list
+**\<suraeNoether>** for analysis and a nice big public explanation, probably drawing heavily on the blog post by dEBRUYNE
+**\<suraeNoether>** speaking of which dEBRUYNE send us all a link :D
+**\<dEBRUYNE>** https://getmonero.org/2017/12/11/A-note-on-fees.html
+**\<suraeNoether>** awesome thanks
+**\<dEBRUYNE>** re: spent age of outputs, perhaps we could take a look at other chains as well?
+**\<suraeNoether>** silur has been working on a C implementation of RTRS ringct
+**\<ferretinjapan>** dEBRUYNE, aeon could be a decent model, unless it requires 100% transparency...
+**\<suraeNoether>** dEBRUYNE: that comes with its own set of assumptions. i'm actually (I think) more comfortable asking "how long does an average 50 euro bill stay in someone's wallet before being spent?" than "bitcoin"
+**\<suraeNoether>** ferretinjapan: aeon suffers the same problem we do i think
+**\<ferretinjapan>** ah
+**\<suraeNoether>** has anyone else been working on anything they want to talk about?
+**\<dEBRUYNE>** ferretinjapan: was more thinking about LTC, BTC
+**\<dEBRUYNE>** suraeNoether: whislt that it true, it may be good for pointers
+**\<ferretinjapan>** yeah, LTC is actually a good one, had a similar mining start to monero.
+**\<suraeNoether>** even if we had a good estimate of true velocity of money, it changes over time so we would need something like a bayesian updating. https://en.wikipedia.org/wiki/Velocity_of_money
+**\<suraeNoether>** sarang, do you have anything else you want to chat about?
+**\<ferretinjapan>** suraeNoether, true, but I'd wager that LTC and XMR's normal distribution after a year is probably very similar. It's probably clsest you'd get without cracking open monero proper and looking inside.
+**\<sarang>** Assembling the formal audit materials as they become available
+**\<sarang>** I still wish we had a more concrete guideline for if/when/how we'll do such things in the future
+**\<sarang>** But for now this is a Good Thing
+**\<suraeNoether>** ferretinjapan: you are assuming it's normal... it isn't, it's heavy-tailed and possibly non-unimodal. :D but you are probably correct that LTC would be a better metric than BTC imho
+**\<suraeNoether>** i am curious about one thing
+**\<suraeNoether>** Up to your concerns about opsec/privacy, gimme a +1 if you are currently an undergraduate university student
+**\<ferretinjapan>** yeah, I'm definitely not saying it's perfect just close-ish compared to the rest of the premined coins out there ;)
+**\<suraeNoether>** ferretinjapan: i agree that litecoin could be a good proxy for monero for estimating otherwise unestimable statistics
+**\<suraeNoether>** i'd also be in favor of doing it for all transparent coins and obtaining a confidence interval
+**\* anonimal** question regarding the MRL over the next 6 months
+**\<anonimal>** I first got in contact with sarang back in late August about kovri work but nothing came of it.
+**\<anonimal>** That then lead to a late October chat about said kovri work but nothing came of it.
+**\<anonimal>** Should I just not count any kovri collaboration from the Noethers? I understand, no hard feelings.
+**\<anonimal>** We simply need more researchers.
+**\<ferretinjapan>** yeah, do some box plots on a couple dozen and you might get a ballpark figure that helps.
+**\<sarang>** anonimal to be honest I didn't think we'd have so much work with RingCT and BPs occupying time
+**\<suraeNoether>** i think you are right anonimal
+**\<sarang>** It has nothing to do with lack of interest
+**\<suraeNoether>** i recall that contact
+**\<sarang>** but I apologize if it seemed that way
+**\<suraeNoether>** anonimal: is there either an explanatory text or a link or something you would you mind giving us for a look?
+**\<suraeNoether>** depending on exactly what sort of questions you are asking, there may be intersection with other work we are doing
+**\<anonimal>** What explanatory text would you like exactly?
+**\<suraeNoether>** is there a thread someplace that birthed the idea behind kovri?
+**\<anonimal>** Oh. Well those IRC logs were unfortunately pasted to a now-defunct website. I can give TL;DRs if needed though.
+**\<anonimal>** Ideally our website/docs would explain everything you need to know but rehrar and I are still WIP with them.
+**\<suraeNoether>** ok, so i'll devote a few hours this week to learning about kovri to see *whether* i can help
+**\<suraeNoether>** keeping in mind the halting problem
+**\<suraeNoether>** (can never really know how long something is going to take until you do it).
+**\<anonimal>** How realistic/effective would a noether tweetnacl review be?
+**\<anonimal>** tweetnacl has had a lot of eyes
+**\<sarang>** You want additional eyes on it?
+**\<anonimal>** (relatively speaking, imo)
+**\<anonimal>** No, just asking your professional opinion on if that would be a cost-effective use of your time.
+**\<anonimal>** IIRC fluffypony wanted teetnacl in monero as some point. I'm not sure where that conversation ended though.
+**\<selsta>** some other “newsâ€. Sumokoin team member confirmed me today that they will donate to the BP audit with some of the premine money. i don’t really believe it yet though lol
+**\<anonimal>** Crypto++ has recently implemented tweetnacl and, once they implement a crypto++-friendly interface, kovri will drop ref10 supercop for tweetnacl.
+**\<suraeNoether>** let me learn a little about tweetnacl, and then i can assess wheter going deeper will be a rabbit hole or ... not
+**\<anonimal>** ok
+**\<suraeNoether>** i haven't tried to ignore it
+**\<suraeNoether>** squeaky wheels and all that
+**\<suraeNoether>** i'm curious about how it works
+**\<suraeNoether>** but i don't want to go on a two month bender learning a new tech while current projects languish either
+**\<suraeNoether>** i think hiring an additional person would be fantastic, for the record
+**\<sarang>** Well it does the basic ed25519 operations suraeNoether as well as hashing operations
+**\<suraeNoether>** we could get a mathjobs.org employer account and put out a *real* call for applications
+**\<suraeNoether>** sarang: well that's nice
+**\<suraeNoether>** ok, anonimal thank you so much for bringing this up
+**\<suraeNoether>** one hard part about this job
+**\<sarang>** yes indeed
+**\<anonimal>** You're welcome. I'm just really excited to finally get to use it.
+**\<suraeNoether>** is that everyone has their personal pet project they want to see analyzed, some of them are important like multisig and kovri and some not so much, and so it's difficult to figure out where priorities should go to avoid context-switching, etc
+**\<suraeNoether>** sometimes it feels like no one knows what job sarang and i have. :P
+**\<suraeNoether>** we need a suresh noether
+**\<suraeNoether>** Okay, well
+**\<anonimal>** I think this tweetnacl business would come at the end of 6 months if even within the next 6 months. Too many other priorities imho
+**\<suraeNoether>** any other concerns, questions, gentle or not so gentle priority nudges folks want to bring up?
+**\<sarang>** If anything I'd like to devote time to a review of existing analyses of tweetnacl anonimal
+**\<sarang>** to at least get a better sense of its current place
+**\<anonimal>** ok awesome
+**\<dEBRUYNE>** \<suraeNoether> we could get a mathjobs.org employer account and put out a *real* call for applications \<= I don't think this will be efficient
+**\<dEBRUYNE>** Preferably you need someone that already has a passion for Monero
+**\<ferretinjapan>** I'll just say you guys are doing a great job keeping up with all these moving targets :)
+**\<suraeNoether>** dEBRUYNE: true
+**\<suraeNoether>** thanks ferretinjapan
+**\<suraeNoether>** oh my god tweetnacl is kind of crazy, i like it ...just reading a quick description
+**\<suraeNoether>** i love the idea of a hyper compact auditable li-berry
+**\<anonimal>** +1
+**\<sarang>** Yeah the key is auditable
+**\<suraeNoether>** well, we probably can't hire andytoshi out from under blockstream. :P
+**\<suraeNoether>** or rather, i'd rather not attempt that sort of game
+**\<suraeNoether>** i'd rather find someone who is very interested in monero and may be late grad school
+**\<suraeNoether>** hmm
+**\<suraeNoether>** i can construct a call for applications e-mail and send it to a few specific departments that are crypto + CS heavy in their math programs
+**\<ErCiccione>** suraeNoether: can you make a post somwhere public with the skills you guys need from a researcher? so i can directly link that to people who may be interested
+**\<suraeNoether>** yeah, i will make the call for applications public, probably, ErCiccione
+**\<suraeNoether>** anyway
+**\<suraeNoether>** I am probably going to hold off on that for at least two weeks, though
+**\<ErCiccione>** ok thanks
+**\<suraeNoether>** to think about what it is we will need 6 months from now
+**\<suraeNoether>** in a new researcher
+**\<suraeNoether>** it's a tough question, and if anyone has any thoughts, shoot me a line at suraeNoether@gmail.com
+**\<ErCiccione>** ok, so, in case, will directly give your contact for now
+**\<suraeNoether>** okay, so without further ado, I suppose we can bid adieu on this meeting.
+**\* suraeNoether** cringes
+**\<anonimal>** Thanks noethers, thanks everyone.
+**\<ErCiccione>** thank you for the updates guys, and awesome job as always :)
+**\<ferretinjapan>** same \^
\ No newline at end of file
diff --git a/_posts/2018-02-11-PoW-change-and-key-reuse.md b/_posts/2018-02-11-PoW-change-and-key-reuse.md
new file mode 100644
index 0000000000000000000000000000000000000000..6d05c578e9c755a7a7c7dfbb7ddc5b3e1d6ad242
--- /dev/null
+++ b/_posts/2018-02-11-PoW-change-and-key-reuse.md
@@ -0,0 +1,41 @@
+---
+layout: post
+title: PoW change and key reuse
+summary: Monero will tweak Cryptonight, and how key reuse can compromise your privacy
+tags: [mining, protocol upgrade, crypto]
+author: dEBRYUNE, dnaleor and the Monero project
+---
+
+
+# PoW change
+
+Lately, a common reoccurring subject has been ASIC resistance and how we should react to any (potential) threat from ASICs. This blog post sets out our (somewhat) formal stance on ASIC resistance and our intention to maintain ASIC resistance by swiftly reacting to any potential threat from ASICs and considering slightly modifying the PoW at every hardfork.
+
+An ASIC (Application Specific Integrated Circuit) is custom mining hardware that is specialized for a particular use. For example, Bitcoin ASICs are specialized to mine cryptocurrencies utilizing a SHA256 hash algorithm. Due to the fact that they are designed for a specific use, they will typically have a large performance advantage over hardware that is intended for general-purpose use like CPUs, GPUs, and even FPGAs. Thus, any newly developed ASIC will obtain a significant majority of the network hashrate and introduce centralization.
+
+The Monero code was forked from the CryptoNote reference implementation. In the CryptoNote whitepaper (https://cryptonote.org/whitepaper.pdf), one of the identified deficiencies of Bitcoin is the Proof of Work due to its centralizing nature, as we will discuss below. In order to create a more egalitarian mining network and foster decentralization, the original CryptoNote developers created the Cryptonight Proof of Work function to "close the gap between CPU (majority) and GPU/FPGA/ASIC (minority) miners." While the CryptoNote authors admit that "It is appropriate that some users can have a certain advantage over others," they propose that "their investments should grow at least linearly with the power." Thus, it is recognized that ASICs may be an inevitable development for any Proof of Work. We also concede that ASICs may be inevitable, but we feel that any transition to an ASIC-dominated network needs to be as egalitarian as possible in order to foster decentralization. At this point in time, we suspect that any newly developed Cryptonight ASIC will not be egalitarian and will not foster a decentralized network.
+
+The drawback of Bitcoin's (SHA256) proof-of-work system is the easy migration from CPUs to GPUs, to FPGAs, and finally to ASICs, where each step came with huge efficiency improvements. Thus, there is a large gap between CPU mining and ASIC mining, which resulted in ASICs being the only viable way to mine. In essence, this causes centralization, because only those with access to specialized hardware (ASICs) are still able to mine, and these typically come from one or very few manufacturers. Cryptonight (Monero's proof-of-work system) intends to close the gap between CPU and GPU, FPGA, and ASIC mining by using a proof-of-work system that is memory bound over a moderate amount of memory. As a result, ASICs get significantly more expensive to build. This proof-of-work system intends to foster egalitarian mining, which yields the following benefits: First, if mining is decentralized (because CPUs and GPUs are still usable for mining), it will be very difficult to pressure miners into not confirming a certain transaction, or otherwise act as a censor to the Monero blockchain. Second, it will lessen the pressure towards centralization of mining in large data centers (as can be seen in Bitcoin). Third, it is quite difficult for governments to regulate companies selling general-purpose hardware (as opposed to companies selling specialized hardware).
+
+Let's further discuss this last point. Specialized hardware will, most likely, only be designed by a few companies. As we can see from Bitcoin, the majority of ASICs are designed and shipped by Bitmain. As Peter Todd said:
+
+>"There's only a tiny number of companies in the world that are capable of building performance/cost competitive ASICs, basically the likes of Intel, ASMC, GlobalFoundries, etc."
+
+This creates a single point of failure. For instance, a government could require these ASIC manufacturers to add a "kill-switch" which allows them to shut down a miner remotely or otherwise control it. This threat has the potential to destroy the whole network. In a similar fashion, governments could require miners to have a license to buy and operate ASICs, thereby confining ASICs to a certain group of licensed people. Furthermore, licensing could ultimately lead to blacklisting certain transactions, i.e., governments can require miners to *not* mine certain transactions, where disobedience would result in miners having their license revoked. By contrast, introducing a license to operate general purpose hardware is probably an infeasible endeavor.
+
+Mining, in general, is also prone to the rich-get-richer effect, which ultimately leads to centralization. For example, a large miner may have significant economies of scale which allows him to grow his share of the hashrate. The Cryptonight algorithm, due to its egalitarian design, somewhat mitigates this effect because miners have competition from (i) miners that have virtually no costs (e.g. botnets), (ii) hobbyist miners, who use their CPUs and GPUs to support the network and aren't predominantly profit driven, and (iii) web miners. Note that web miners have both illegitimate (e.g. mining via ads without consent) and legitimate use cases (e.g. mining to solve CAPTCHAs or mining to reduce/replace advertisements). By contrast, ASICs accelerate the rich-get-richer effect, because ASIC miners have no competition from the aforementioned mining "groups".
+
+In sum, we strongly believe that it's beneficial to preserve our ASIC resistance. Therefore, we will perform an emergency hard fork to curb any potential threat from ASICs if needed. Furthermore, in order to maintain its goal of decentralization and to provide a deterrent for ASIC development and to protect against unknown or undetectable ASIC development, the Monero team proposes modifying the Cryptonight PoW hash every scheduled fork, twice a year. The modifications will be light, and should not change performance profiles much. The first change is now being tested, and will happen in the coming March fork. Finally, we will continue to research alternative Proof of Work functions that may provide better ASIC resistance than Cryptonight.
+
+Patches will be available for the following software: zone117x's pool, Snipa's pool, Lucas Jones' CPU miner, wolf0's CPU miner, ccminer-cryptonight, sgminer-gm, xmr-stak, xmrig-nvidia, wolf-xmr-miner.
+
+# Key reuse
+
+It is important to realize that the security of the Monero network and your own Monero is dependent on the security of your Monero keys. Your Monero keys are *MONERO* keys. Do NOT use them for any other purpose, including claiming coins from a Monero fork. Using your keys to spend the same outputs twice on different forked blockchains will damage your privacy, and others', as both spends will bear the same key image, but different rings, with only your spent output in common (this does not impact stealth addresses nor confidential transactions, just ring signatures). Moreover, by using such a "same keys" fork, the security of your Monero private keys now depends on those third parties.
+
+ - Forkers, if you're forking Monero, DO NOT ask users to reuse their Monero keys, but have them create new keys for your fork.
+
+ - Users, if a forker asks you to use your Monero keys for their fork (after this notification is published), they're trying to manipulate you into being part of a large scale attack on Monero.
+
+Be safe, and don't reuse your Monero keys for any other purpose than using Monero.
+
diff --git a/_posts/2018-03-01-core-team-announcement.md b/_posts/2018-03-01-core-team-announcement.md
new file mode 100644
index 0000000000000000000000000000000000000000..f3824c332a3e834062a5770015f9c215eea1cbef
--- /dev/null
+++ b/_posts/2018-03-01-core-team-announcement.md
@@ -0,0 +1,34 @@
+---
+layout: post
+title: Core Team Announcement
+summary: Small elaboration on the Core Team's role and an announcement on its membership
+tags: [monero, core]
+author: The Core Team
+---
+
+The year 2018 is well underway, with many exciting new technologies on the horizon for Monero. Technology is not the only thing that needs to adapt if Monero is to stay at the forefront of privacy and blockchain technologies, however. With that in mind, the Core Team would like to remind the community about their role in regards to Monero followed by an announcement regarding the membership of the Core Team.
+
+The role of the Core Team can often be a confusing topic, especially with the various leadership structures employed by other cryptocurrencies. As the technology for a completely trustless society is not yet a reality, all projects, even decentralized ones, benefit from having individuals that can carry out tasks that require trust. A quick example of this is owning a domain name (like getmonero.org) or maintaining servers (on which getmonero.org is hosted). Ultimately, there is not yet a way for a domain name to be owned by a decentralized community, so someone has to be the name holding this domain. It's in scenarios like this where the Core Team are able to work on bridging the decentralized world we are trying to bring about with the centralized reality in which we are currently living.
+
+The responsibilities of the Core Team are as follows (in no particular order):
+- Act as primary trusted arbiters of the Forum Funding System on behalf of the community, so as to ensure the completion of all projects to the satisfaction of the community.
+- Manage the codebase of the Monero Project, which includes merging code on Github, keeping backups, and ensuring the safety, security, and free access of the code from any party.
+- Steward the general donation fund, and spending the Monero there on anything they see fit to further the Monero Project.
+- Act as trusted signers and distributors of reference clients for the Monero coin, and other related technologies.
+- Set a direction and vision for the Monero Project
+
+In the event that the community deems the Core Team unworthy or lax in their duties, they are free to fork the project away from the current Core Team, as happened with thankful_for_today.
+
+There are some things that the Core Team are NOT responsible for, despite misconceptions from the community. Some of the more common misconceptions are listed below:
+- Members of the Core Team are NOT anyone's boss, and no permission is needed from them to do anything.
+- The Core Team does NOT act as a centralized point of failure, but encourages organic, self-started initiatives that further the ecosystem of Monero.
+- The Core Team does NOT equal Monero. In the event that one, or all of the Core Team goes rogue, we are to remember that Monero is a movement. A global initiative to further privacy globally, and provide real, fungible, digital money for everyone. This can happen even without the presence of the Core Team.
+
+Another requirement that the Core Team has internally however, is that each member be sufficiently active. In the event that someone is not able to be active in Monero, they are expected to step down from their position and the remaining members elect another person to replace them. For the aforementioned reason, tacotime is stepping down effective immediately. Those that were not present for the first few months of Monero will probably not remember tacotime, and will not understand the large role that he played in making Monero what it is today. Together, he and smooth championed the early days of bitmonero, and helped the budding community to navigate the project post-thankfulfortoday. He acted as the lead maintainer of the codebase, a role now filled by fluffypony. It's safe to say that Monero would not be what it is today without the early leadership and work of tacotime, and the members of the Core Team are very thankful for his past dedication, and wish him well for all future endeavors.
+
+But every change brings new opportunity, and the Core Team is delighted to welcome Jeremie "binaryFate" Dubois-Lacoste on board as the newest member. binaryFate holds a PhD in computer science, with academic expertise in combinatorial systems and optimization algorithms. After working for a couple of years in academic research, he made the decision to become a full-time entrepreneur in the cryptocurrency space. He has been actively investing, trading, and creating businesses in that field since 2012. He has been involved with Monero since May 2014, and has been an active advocate of privacy and fungibility-protecting technologies ever since, both online and in real life
+
+All members of the Core Team, past and present want to thank all volunteers and contributors for their consistent and tireless work. We look forward to what 2018 has in store for us as a project, and as a community.
+
+
+Image credit: [helloluis](https://cryptopop.net/)
\ No newline at end of file
diff --git a/blog/index.html b/blog/index.html
index e7835423f031d8ea6368fda7c6a824356f0be988..5f056a91bd4b94a9d36ccbc487078470cc3179f1 100644
--- a/blog/index.html
+++ b/blog/index.html
@@ -1,6 +1,6 @@
---
layout: full-text
-title: All Blog Posts
+title: titles.allposts
---
{% for post in paginator.posts %}
@@ -9,7 +9,7 @@ title: All Blog Posts
{{ post.summary }}
<small>{% t blog.tagged %}:
{% for tag in post.tags %}
- [<a href="/blog/tags/{{ tag }}.html">{{ tag }}]</a>
+ <a href="/blog/tags/{{ tag }}.html">[{{ tag }}]</a>
{% endfor %}
</small>
</p>
@@ -40,4 +40,4 @@ title: All Blog Posts
<span>Next »</span>
{% endif %}
</h4></div>
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/blog/tags/0mq.md b/blog/tags/0mq.md
index 320028d508d1c18c7fa5c93e6b86123a66b3926a..7a43f52c0c527cc274329c090fdf54aac7126ca2 100644
--- a/blog/tags/0mq.md
+++ b/blog/tags/0mq.md
@@ -1,3 +1,4 @@
---
layout: blog_by_tag
+title: titles.blogbytag
---
\ No newline at end of file
diff --git a/blog/tags/accounts.md b/blog/tags/accounts.md
index 320028d508d1c18c7fa5c93e6b86123a66b3926a..7a43f52c0c527cc274329c090fdf54aac7126ca2 100644
--- a/blog/tags/accounts.md
+++ b/blog/tags/accounts.md
@@ -1,3 +1,4 @@
---
layout: blog_by_tag
+title: titles.blogbytag
---
\ No newline at end of file
diff --git a/blog/tags/blockchaindb.md b/blog/tags/blockchaindb.md
index 320028d508d1c18c7fa5c93e6b86123a66b3926a..7a43f52c0c527cc274329c090fdf54aac7126ca2 100644
--- a/blog/tags/blockchaindb.md
+++ b/blog/tags/blockchaindb.md
@@ -1,3 +1,4 @@
---
layout: blog_by_tag
+title: titles.blogbytag
---
\ No newline at end of file
diff --git a/blog/tags/branding.md b/blog/tags/branding.md
index 320028d508d1c18c7fa5c93e6b86123a66b3926a..7a43f52c0c527cc274329c090fdf54aac7126ca2 100644
--- a/blog/tags/branding.md
+++ b/blog/tags/branding.md
@@ -1,3 +1,4 @@
---
layout: blog_by_tag
+title: titles.blogbytag
---
\ No newline at end of file
diff --git a/blog/tags/compliance.md b/blog/tags/compliance.md
index 320028d508d1c18c7fa5c93e6b86123a66b3926a..7a43f52c0c527cc274329c090fdf54aac7126ca2 100644
--- a/blog/tags/compliance.md
+++ b/blog/tags/compliance.md
@@ -1,3 +1,4 @@
---
layout: blog_by_tag
+title: titles.blogbytag
---
\ No newline at end of file
diff --git a/blog/tags/conferences.md b/blog/tags/conferences.md
index 320028d508d1c18c7fa5c93e6b86123a66b3926a..7a43f52c0c527cc274329c090fdf54aac7126ca2 100644
--- a/blog/tags/conferences.md
+++ b/blog/tags/conferences.md
@@ -1,3 +1,4 @@
---
layout: blog_by_tag
+title: titles.blogbytag
---
\ No newline at end of file
diff --git a/blog/tags/core.md b/blog/tags/core.md
index 320028d508d1c18c7fa5c93e6b86123a66b3926a..7a43f52c0c527cc274329c090fdf54aac7126ca2 100644
--- a/blog/tags/core.md
+++ b/blog/tags/core.md
@@ -1,3 +1,4 @@
---
layout: blog_by_tag
+title: titles.blogbytag
---
\ No newline at end of file
diff --git a/blog/tags/crypto.md b/blog/tags/crypto.md
index 320028d508d1c18c7fa5c93e6b86123a66b3926a..7a43f52c0c527cc274329c090fdf54aac7126ca2 100644
--- a/blog/tags/crypto.md
+++ b/blog/tags/crypto.md
@@ -1,3 +1,4 @@
---
layout: blog_by_tag
+title: titles.blogbytag
---
\ No newline at end of file
diff --git a/blog/tags/dev diaries.md b/blog/tags/dev diaries.md
index 320028d508d1c18c7fa5c93e6b86123a66b3926a..7a43f52c0c527cc274329c090fdf54aac7126ca2 100644
--- a/blog/tags/dev diaries.md
+++ b/blog/tags/dev diaries.md
@@ -1,3 +1,4 @@
---
layout: blog_by_tag
+title: titles.blogbytag
---
\ No newline at end of file
diff --git a/blog/tags/docs.md b/blog/tags/docs.md
index 320028d508d1c18c7fa5c93e6b86123a66b3926a..7a43f52c0c527cc274329c090fdf54aac7126ca2 100644
--- a/blog/tags/docs.md
+++ b/blog/tags/docs.md
@@ -1,3 +1,4 @@
---
layout: blog_by_tag
+title: titles.blogbytag
---
\ No newline at end of file
diff --git a/blog/tags/exchanges.md b/blog/tags/exchanges.md
index 320028d508d1c18c7fa5c93e6b86123a66b3926a..7a43f52c0c527cc274329c090fdf54aac7126ca2 100644
--- a/blog/tags/exchanges.md
+++ b/blog/tags/exchanges.md
@@ -1,3 +1,4 @@
---
layout: blog_by_tag
+title: titles.blogbytag
---
\ No newline at end of file
diff --git a/blog/tags/external.md b/blog/tags/external.md
index 320028d508d1c18c7fa5c93e6b86123a66b3926a..7a43f52c0c527cc274329c090fdf54aac7126ca2 100644
--- a/blog/tags/external.md
+++ b/blog/tags/external.md
@@ -1,3 +1,4 @@
---
layout: blog_by_tag
+title: titles.blogbytag
---
\ No newline at end of file
diff --git a/blog/tags/forkguard.md b/blog/tags/forkguard.md
index 320028d508d1c18c7fa5c93e6b86123a66b3926a..7a43f52c0c527cc274329c090fdf54aac7126ca2 100644
--- a/blog/tags/forkguard.md
+++ b/blog/tags/forkguard.md
@@ -1,3 +1,4 @@
---
layout: blog_by_tag
+title: titles.blogbytag
---
\ No newline at end of file
diff --git a/blog/tags/funding.md b/blog/tags/funding.md
index 320028d508d1c18c7fa5c93e6b86123a66b3926a..7a43f52c0c527cc274329c090fdf54aac7126ca2 100644
--- a/blog/tags/funding.md
+++ b/blog/tags/funding.md
@@ -1,3 +1,4 @@
---
layout: blog_by_tag
+title: titles.blogbytag
---
\ No newline at end of file
diff --git a/blog/tags/gui.md b/blog/tags/gui.md
index 320028d508d1c18c7fa5c93e6b86123a66b3926a..7a43f52c0c527cc274329c090fdf54aac7126ca2 100644
--- a/blog/tags/gui.md
+++ b/blog/tags/gui.md
@@ -1,3 +1,4 @@
---
layout: blog_by_tag
+title: titles.blogbytag
---
\ No newline at end of file
diff --git a/blog/tags/i2p.md b/blog/tags/i2p.md
index 320028d508d1c18c7fa5c93e6b86123a66b3926a..7a43f52c0c527cc274329c090fdf54aac7126ca2 100644
--- a/blog/tags/i2p.md
+++ b/blog/tags/i2p.md
@@ -1,3 +1,4 @@
---
layout: blog_by_tag
+title: titles.blogbytag
---
\ No newline at end of file
diff --git a/blog/tags/i8n.md b/blog/tags/i8n.md
index 320028d508d1c18c7fa5c93e6b86123a66b3926a..7a43f52c0c527cc274329c090fdf54aac7126ca2 100644
--- a/blog/tags/i8n.md
+++ b/blog/tags/i8n.md
@@ -1,3 +1,4 @@
---
layout: blog_by_tag
+title: titles.blogbytag
---
\ No newline at end of file
diff --git a/blog/tags/mining.md b/blog/tags/mining.md
index 320028d508d1c18c7fa5c93e6b86123a66b3926a..7a43f52c0c527cc274329c090fdf54aac7126ca2 100644
--- a/blog/tags/mining.md
+++ b/blog/tags/mining.md
@@ -1,3 +1,4 @@
---
layout: blog_by_tag
+title: titles.blogbytag
---
\ No newline at end of file
diff --git a/blog/tags/monero missives.md b/blog/tags/monero missives.md
index 320028d508d1c18c7fa5c93e6b86123a66b3926a..7a43f52c0c527cc274329c090fdf54aac7126ca2 100644
--- a/blog/tags/monero missives.md
+++ b/blog/tags/monero missives.md
@@ -1,3 +1,4 @@
---
layout: blog_by_tag
+title: titles.blogbytag
---
\ No newline at end of file
diff --git a/blog/tags/mymonero.md b/blog/tags/mymonero.md
index 320028d508d1c18c7fa5c93e6b86123a66b3926a..7a43f52c0c527cc274329c090fdf54aac7126ca2 100644
--- a/blog/tags/mymonero.md
+++ b/blog/tags/mymonero.md
@@ -1,3 +1,4 @@
---
layout: blog_by_tag
+title: titles.blogbytag
---
\ No newline at end of file
diff --git a/blog/tags/platforms.md b/blog/tags/platforms.md
index 320028d508d1c18c7fa5c93e6b86123a66b3926a..7a43f52c0c527cc274329c090fdf54aac7126ca2 100644
--- a/blog/tags/platforms.md
+++ b/blog/tags/platforms.md
@@ -1,3 +1,4 @@
---
layout: blog_by_tag
+title: titles.blogbytag
---
\ No newline at end of file
diff --git a/blog/tags/kovri.md b/blog/tags/protocol upgrade.md
similarity index 52%
rename from blog/tags/kovri.md
rename to blog/tags/protocol upgrade.md
index 320028d508d1c18c7fa5c93e6b86123a66b3926a..7a43f52c0c527cc274329c090fdf54aac7126ca2 100644
--- a/blog/tags/kovri.md
+++ b/blog/tags/protocol upgrade.md
@@ -1,3 +1,4 @@
---
layout: blog_by_tag
+title: titles.blogbytag
---
\ No newline at end of file
diff --git a/blog/tags/releases.md b/blog/tags/releases.md
index 320028d508d1c18c7fa5c93e6b86123a66b3926a..7a43f52c0c527cc274329c090fdf54aac7126ca2 100644
--- a/blog/tags/releases.md
+++ b/blog/tags/releases.md
@@ -1,3 +1,4 @@
---
layout: blog_by_tag
+title: titles.blogbytag
---
\ No newline at end of file
diff --git a/blog/tags/research.md b/blog/tags/research.md
index 320028d508d1c18c7fa5c93e6b86123a66b3926a..7a43f52c0c527cc274329c090fdf54aac7126ca2 100644
--- a/blog/tags/research.md
+++ b/blog/tags/research.md
@@ -1,3 +1,4 @@
---
layout: blog_by_tag
+title: titles.blogbytag
---
\ No newline at end of file
diff --git a/blog/tags/rpc.md b/blog/tags/rpc.md
index 320028d508d1c18c7fa5c93e6b86123a66b3926a..7a43f52c0c527cc274329c090fdf54aac7126ca2 100644
--- a/blog/tags/rpc.md
+++ b/blog/tags/rpc.md
@@ -1,3 +1,4 @@
---
layout: blog_by_tag
+title: titles.blogbytag
---
\ No newline at end of file
diff --git a/blog/tags/usability.md b/blog/tags/usability.md
index 320028d508d1c18c7fa5c93e6b86123a66b3926a..7a43f52c0c527cc274329c090fdf54aac7126ca2 100644
--- a/blog/tags/usability.md
+++ b/blog/tags/usability.md
@@ -1,3 +1,4 @@
---
layout: blog_by_tag
+title: titles.blogbytag
---
\ No newline at end of file
diff --git a/blog/tags/year in review.md b/blog/tags/year in review.md
index 320028d508d1c18c7fa5c93e6b86123a66b3926a..7a43f52c0c527cc274329c090fdf54aac7126ca2 100644
--- a/blog/tags/year in review.md
+++ b/blog/tags/year in review.md
@@ -1,3 +1,4 @@
---
layout: blog_by_tag
+title: titles.blogbytag
---
\ No newline at end of file
diff --git a/community/events/index.md b/community/events/index.md
index 2b3580be5698679a529d847aa89ac16513f69ded..9a5885879e9a902b4e7c86862ac3ea42e6f9ea7e 100644
--- a/community/events/index.md
+++ b/community/events/index.md
@@ -1,32 +1,6 @@
---
layout: custom
-title: Events
+title: titles.events
+permalink: /community/events/index.html
---
-
-<div markdown="1" class="text-center container description">
-Monero people are always down to get together and have a good time. Check below to see Monero-related events happening in your area.
-</div>
-
-{% for toplevel in site.data.events %}
-
-<div class="events">
- <div class="container full col-xs-12">
- <div class="info-block text-adapt">
- <div class="row">
- <div class="col-xs-12">
- <h2>{{toplevel.event}}</h2>
- <h3>Where</h3>
- <p>{{toplevel.where}}</p>
- <h3>When</h3>
- <p>{{toplevel.when}}</p>
- <h3>Description</h3>
- <p>{{toplevel.description}}</p>
- <h3>Link</h3>
- <a>{{toplevel.link}}</a>
- </div>
- </div>
- </div>
- </div>
-</div>
-
-{%endfor%}
\ No newline at end of file
+{% tf community/events.md %}
\ No newline at end of file
diff --git a/community/hangouts/index.md b/community/hangouts/index.md
index 32e5796cedb31e41bd8ddc36b7b9d9dd4898a63d..bff887844754a806308bb31e83719ec5b695811c 100644
--- a/community/hangouts/index.md
+++ b/community/hangouts/index.md
@@ -1,100 +1,6 @@
---
layout: custom
-title: Hangouts
+title: titles.hangouts
+permalink: /community/hangouts/index.html
---
-<div markdown="1" class="text-center container description">
-The Monero community is diverse and varied. We come from all over, but we definitely have some places we like to hang out together. You'll find most of them below. Join us!
-</div>
-
-<div class="hangouts">
- <section class="container">
- <ul class="row center-xs">
- <li>
- <a href="https://twitter.com/monerocurrency" target="_blank" rel="noreferrer noopener"><div class="social-icon twitter"></div></a>
- </li>
- <li>
- <a href="https://reddit.com/r/monero" target="_blank" rel="noreferrer noopener"><div class="social-icon reddit"></div></a>
- </li>
- <li>
- <a href="https://www.facebook.com/monerocurrency/" target="_blank" rel="noreferrer noopener"><div class="social-icon facebook"></div></a>
- </li>
- <li>
- <a href="https://github.com/monero-project" target="_blank" rel="noreferrer noopener"><div class="social-icon github"></div></a>
- </li>
- </ul>
- </section>
-
- <section class="container">
- <div class="row">
- <!-- left two-thirds block-->
- <div class="left two-thirds col-lg-8 col-md-8 col-sm-12 col-xs-12">
- <div class="col-xs-12">
- <div class="info-block">
- <div class="row center-xs">
- <div class="col">
- <h2>Workgroup Resources</h2>
- </div>
- </div>
- <div class="row center-xs">
- <p>In an effort to support organic workgroups, Monero has several resources that the community can use to meet and plan projects. Mattermost even has relays into the most popular Monero-related IRC channels.</p>
- </div>
- <div class="row relays around-xs">
- <div class="col-md-4 col-sm-4 col-xs-4">
- <p><a href="https://monero.slack.com/" class="btn-link btn-fixed">Slack</a></p>
- </div>
- <div class="col-md-4 col-sm-4 col-xs-4">
- <p><a href="https://mattermost.getmonero.org/" class="btn-link btn-fixed">Mattermost</a></p>
- </div>
- <div class="col-md-4 col-sm-4 col-xs-4">
- <p><a href="https://taiga.getmonero.org/" class="btn-link btn-fixed">Taiga</a></p>
- </div>
- </div>
- </div>
- <div class="info-block">
- <div class="row center-xs">
- <div class="col">
- <h2>IRC Channels</h2>
- </div>
- </div>
- <div class="row start-xs">
- <p>The Monero community utilizes a lot of IRC channels that each serve different purposes. Some to work, and some just to hang out. You'll find the more popular ones below.</p>
- </div>
- <div class="row irc">
- {% for channel in site.data.irc %}
- <div class="col-md-4 col-xs-12">
- <a href="irc://chat.freenode.net/#{{ channel.channel }}">#{{ channel.channel }}</a>
- <p>{{ channel.description }}</p>
- </div>
- {% endfor %}
- </div>
- </div>
- </div>
- </div>
- <!-- end left two-thirds block-->
-
- <!-- right one-third block-->
- <div class="right one-third col-lg-4 col-md-4 col-sm-12 col-xs-12">
- <div class="info-block">
- <div class="row center-xs">
- <div class="col"><h2>Stack Exchange</h2></div>
- </div>
- <div class="row start-xs">
- <p>The Monero Stack Exchange is a quick and easy way to ask questions and get answers. Below you'll find some high quality question/answer pairs to some frequently asked questions.</p>
- </div>
- <div class="row start-xs sequestions">
- <a href="https://monero.stackexchange.com/questions/4277/why-does-monero-have-higher-transaction-fees-than-bitcoin">Why does monero have higher transaction fees than bitcoin?</a>
- <a href="https://monero.stackexchange.com/questions/4335/what-does-moneros-scaling-roadmap-look-like">What does Monero's scaling roadmap look like?</a>
- <a href="https://monero.stackexchange.com/questions/4302/what-cryptography-primitives-concepts-other-than-the-basic-ones-does-monero-us">What cryptography primitives/concepts, other than the basic ones, does Monero use?</a>
- <a href="https://monero.stackexchange.com/questions/4242/how-to-extract-data-from-local-blockchain">How to extract data from local blockchain?</a>
- <a href="https://monero.stackexchange.com/questions/4302/what-cryptography-primitives-concepts-other-than-the-basic-ones-does-monero-us">Hiding TCP traffic for Monero miners?</a>
- </div>
- <div class="row center-xs">
- <p><a href="https://monero.stackexchange.com" class="btn-link btn-auto">Visit Stack Exchange</a></p>
- </div>
- </div>
- </div>
- <!-- end right one-third block-->
- </div>
- </section>
-
-</div>
+{% tf community/hangouts.md %}
\ No newline at end of file
diff --git a/community/merchants/index.md b/community/merchants/index.md
index fc2a0b9a54cefdb9ebe124c3c17d54af6ecda3af..d9efd03064053018f4be6c88072a6dd2c62a6b9c 100644
--- a/community/merchants/index.md
+++ b/community/merchants/index.md
@@ -1,30 +1,6 @@
---
layout: custom
-title: Merchants & Services
+title: titles.merchants
+permalink: /community/merchants/index.html
---
-<div markdown="1" class="text-center container description">
-Merchants of all kinds have come to value the financial privacy that Monero brings. Below is a list of the merchants that we know of that currently accept Monero for their goods and services. If a company no longer accepts Monero or you would like your business to be listed, please [open a GitHub issue and let us know](https://github.com/monero-project/monero-site/issues).
-</div>
-<div class="merchants">
-{% for toplevel in site.data.merchants %}
-<div class="container full" id="{{toplevel.id}}">
- <div class="info-block">
- <h2>{{toplevel.category}}</h2>
- <div class="row">
- {% assign sortedMerchants = toplevel.merchants | sort: 'name' %}
- {% for merchants in sortedMerchants %}
- <div class="col-md-4 col-sm-6 col-xs-12">
- <a href="{{merchants.url}}">{{merchants.name}}</a>
- </div>
- {% endfor %}
- </div>
- </div>
-</div>
-{%endfor%}
-
-
-</div>
-
-<div markdown="1" class="text-center container description">
-*Please note: these links are being provided as a convenience and for informational purposes only; they do not constitute an endorsement by the Monero community of any products, services or opinions of the corporations or organizations or individuals listed. The Monero community bears no responsibility for the accuracy, legality, or content of these external sites. Contact the external site for answers to questions regarding its content. As always, caveat emptor ("buyer beware"); you are responsible for doing your own research. Always use judgement when making online purchases.*
-</div>
+{% tf community/merchants.md %}
\ No newline at end of file
diff --git a/community/sponsorships/index.md b/community/sponsorships/index.md
index d2097431741a8ae16467e202af9747de3d130384..628d6575962126a230cfe3c880181f26003a43a5 100644
--- a/community/sponsorships/index.md
+++ b/community/sponsorships/index.md
@@ -1,101 +1,7 @@
---
layout: custom
-title: Sponsorships
+title: titles.sponsorships
+permalink: /community/sponsorships/index.html
---
-<div markdown="1" class="text-center container description">
-The following businesses have supported the Monero Project in its goal to bring financial privacy to the world. We couldn't be more grateful for their contributions. If you would like to sponsor the Monero Project and be listed on this page, please send an email to dev@getmonero.org.
-</div>
-
-<div>
- <section class="container sponsors">
- <div class="row">
- <div class="left one-third no-pad-sm col-lg-4 col-md-4 col-sm-12 col-xs-12">
- <div class="info-block">
- <div class="row center-xs">
- <div class="col">
- <h2>My Monero</h2>
- <a href="https://mymonero.com/#/" target="_blank" rel="noreferrer noopener"><img src="/img/mymonero.png"></a>
- </div>
- </div>
- </div>
- </div>
- <div class="center one-third no-pad-sm col-lg-4 col-md-4 col-sm-12 col-xs-12">
- <div class="info-block">
- <div class="row center-xs">
- <div class="col">
- <h2>Araxis</h2>
- <a href="https://www.araxis.com/"><img src="/img/araxis.png"></a>
- </div>
- </div>
- </div>
- </div>
- <div class="right one-third no-pad-sm col-lg-4 col-md-4 col-sm-12 col-xs-12">
- <div class="info-block">
- <div class="row center-xs">
- <div class="col">
- <h2>Dome9 Security</h2>
- <a href="https://dome9.com/"><img src="/img/dome9.png"></a>
- </div>
- </div>
- </div>
- </div>
- </div>
- <div class="row">
- <div class="left one-third no-pad-sm col-lg-4 col-md-4 col-sm-12 col-xs-12">
- <div class="info-block">
- <div class="row center-xs">
- <div class="col">
- <h2>Kitware</h2>
- <a href="https://www.kitware.com/"><img src="/img/kitware.png"></a>
- </div>
- </div>
- </div>
- </div>
-
- <div class="center one-third no-pad-sm col-lg-4 col-md-4 col-sm-12 col-xs-12">
- <div class="info-block">
- <div class="row center-xs">
- <div class="col">
- <h2>Fork Networking</h2>
- <a href="https://www.forked.net"><img src="/img/forked_logo.png"></a>
- </div>
- </div>
- </div>
- </div>
-
- <div class="right one-third no-pad-sm col-lg-4 col-md-4 col-sm-12 col-xs-12">
- <div class="info-block">
- <div class="row center-xs">
- <div class="col">
- <h2>JetBrains</h2>
- <a href="http://www.jetbrains.com/"><img src="/img/jetbrains.png"></a>
- </div>
- </div>
- </div>
- </div>
- </div>
- <div class="row">
- <div class="left half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
- <div class="info-block">
- <div class="row center-xs">
- <div class="col">
- <h2>Navicat</h2>
- <a href="https://www.navicat.com"><img src="/img/navicat.png"></a>
- </div>
- </div>
- </div>
- </div>
- <div class="right half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
- <div class="info-block">
- <div class="row center-xs">
- <div class="col">
- <h2>Symas</h2>
- <a href="https://symas.com/"><img src="/img/symas.png"></a>
- </div>
- </div>
- </div>
- </div>
- </div>
- </section>
-</div>
\ No newline at end of file
+{% tf community/sponsorships.md %}
\ No newline at end of file
diff --git a/community/team/index.md b/community/team/index.md
index 04a993a177b2cdadb1d59a5dcf8832cf7c9ff79c..7604b737fd1d45e16f08da4581915d147958b2d3 100644
--- a/community/team/index.md
+++ b/community/team/index.md
@@ -1,184 +1,6 @@
---
layout: custom
-title: Monero Team
+title: titles.team
+permalink: /community/team/index.html
---
-<div class="team">
-
- <section class="container">
- <div class="row">
- <div class="col-xs-12">
- <div class="tabPanel-widget">
- <label for="tab-1" tabindex="0"></label>
- <input id="tab-1" type="radio" name="tabs" aria-hidden="true" checked>
- <h2>Core</h2>
- <div class="tabPanel-content">
- <div class="row">
- {% for toplevel in site.data.team %}
- {% if toplevel.area == "Core" %}
- {% for member in toplevel.member %}
- <div class="half col-lg-6 col-md-6 col-sm-6 col-xs-6">
- <div class="info-block">
- <div class="row center-xs">
- <h3>{{member.name}}</h3>
- </div>
- <div class="row center-xs">
- <p>{{member.email}}</p>
- </div>
- <div class="row center-xs icons">
- {% if member.github %}
- <a href="{{member.github}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon github"></div></a>
- {%endif%}
- {% if member.twitter %}
- <a href="{{member.twitter}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon twitter"></div></a>
- {%endif%}
- {% if member.reddit %}
- <a href="{{member.reddit}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon reddit"></div></a>
- {%endif%}
- </div>
- </div>
- </div>
- {%endfor%}
- {%endif%}
- {%endfor%}
- </div>
- </div>
- <label for="tab-2" tabindex="0"></label>
- <input id="tab-2" type="radio" name="tabs" aria-hidden="true">
- <h2>Developers</h2>
- <div class="tabPanel-content">
- <div class="container full">
- <div class="info-block text-adapt">
- <div class="row">
- <div class="col-xs-12 text-adapt">
- <p>The Monero Project has had well over 200 contributors over the life of the project. For a complete list, please see the <a href="https://www.openhub.net/p/monero/contributors">OpenHub contributors page</a>. Below you'll find some individuals that have gone above and beyond for Monero.</p>
- </div>
- </div>
- </div>
- </div>
- <div class="row">
- {% for toplevel in site.data.team %}
- {% if toplevel.area == "Developers" %}
- {% for member in toplevel.member %}
- <div class="half col-lg-6 col-md-6 col-sm-6 col-xs-6">
- <div class="info-block">
- <div class="row center-xs">
- <h3>{{member.name}}</h3>
- </div>
- <div class="row center-xs icons">
- {% if member.github %}
- <a href="{{member.github}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon github"></div></a>
- {%endif%}
- {% if member.twitter %}
- <a href="{{member.twitter}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon twitter"></div></a>
- {%endif%}
- {% if member.reddit %}
- <a href="{{member.reddit}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon reddit"></div></a>
- {%endif%}
- </div>
- </div>
- </div>
- {%endfor%}
- {%endif%}
- {%endfor%}
- </div>
- </div>
- <label for="tab-3" tabindex="0"></label>
- <input id="tab-3" type="radio" name="tabs" aria-hidden="true">
- <h2>Community</h2>
- <div class="tabPanel-content">
- <div class="row">
- {% for toplevel in site.data.team %}
- {% if toplevel.area == "Community" %}
- {% for member in toplevel.member %}
- <div class="half col-lg-6 col-md-6 col-sm-6 col-xs-6">
- <div class="info-block">
- <div class="row center-xs">
- <h3>{{member.name}}</h3>
- </div>
- <div class="row center-xs icons">
- {% if member.github %}
- <a href="{{member.github}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon github"></div></a>
- {%endif%}
- {% if member.twitter %}
- <a href="{{member.twitter}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon twitter"></div></a>
- {%endif%}
- {% if member.reddit %}
- <a href="{{member.reddit}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon reddit"></div></a>
- {%endif%}
- </div>
- </div>
- </div>
- {%endfor%}
- {%endif%}
- {%endfor%}
- </div>
- </div>
- <label for="tab-4" tabindex="0"></label>
- <input id="tab-4" type="radio" name="tabs" aria-hidden="true">
- <h2>Research Lab</h2>
- <div class="tabPanel-content">
- <div class="row">
- {% for toplevel in site.data.team %}
- {% if toplevel.area == "Monero Research Lab" %}
- {% for member in toplevel.member %}
- <div class="half col-lg-6 col-md-6 col-sm-12 col-xs-6">
- <div class="info-block">
- <div class="row center-xs">
- <h3>{{member.name}}</h3>
- </div>
- <div class="row center-xs icons">
- {% if member.github %}
- <a href="{{member.github}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon github"></div></a>
- {%endif%}
- {% if member.twitter %}
- <a href="{{member.twitter}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon twitter"></div></a>
- {%endif%}
- {% if member.reddit %}
- <a href="{{member.reddit}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon reddit"></div></a>
- {%endif%}
- </div>
- </div>
- </div>
- {%endfor%}
- {%endif%}
- {%endfor%}
- </div>
- </div>
- <label for="tab-5" tabindex="0"></label>
- <input id="tab-5" type="radio" name="tabs" aria-hidden="true">
- <h2>Special Thanks</h2>
- <div class="tabPanel-content">
- <div class="row">
- {% for toplevel in site.data.team %}
- {% if toplevel.area == "Special Thanks" %}
- {% for member in toplevel.member %}
- <div class="half col-lg-6 col-md-6 col-sm-12 col-xs-6">
- <div class="info-block">
- <div class="row center-xs">
- <h3>{{member.name}}</h3>
- </div>
- <div class="row center-xs icons">
- {% if member.github %}
- <a href="{{member.github}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon github"></div></a>
- {%endif%}
- {% if member.twitter %}
- <a href="{{member.twitter}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon twitter"></div></a>
- {%endif%}
- {% if member.reddit %}
- <a href="{{member.reddit}}" target="_blank" rel="noreferrer, noopener"><div class="col social-icon reddit"></div></a>
- {%endif%}
- </div>
- </div>
- </div>
- {%endfor%}
- {%endif%}
- {%endfor%}
- </div>
- </div>
- </div>
- </div>
- </div>
-</section>
-
-
-</div>
\ No newline at end of file
+{% tf community/team.md %}
\ No newline at end of file
diff --git a/css/custom.css b/css/custom.css
index 0e7bebfa29f0467b9814692b5eda4cce4b49f737..13fccf1709752a3f7b7e24f0774dbc0910bf5cf7 100644
--- a/css/custom.css
+++ b/css/custom.css
@@ -1075,6 +1075,23 @@ pre.highlight>code {
border-top: 3px solid #393939;
}
+.untranslated {
+ background-color: #ff7519;
+ position: fixed;
+ bottom: 0;
+ left: 0;
+ z-index: 4;
+ width: 100%;
+ text-align: center;
+ color: white;
+ padding-bottom: 1rem;
+}
+
+.untranslated-link {
+ color: white;
+ text-decoration: underline;
+}
+
@media only screen and (max-width: 75rem) {
body p, body blockquote, body ul {
@@ -1102,6 +1119,9 @@ body {font-size: 1rem;}
.page-wrapper {
padding-top: 4rem;
}
+ .untranslated p {
+ font-size: 0.6rem;
+ }
}
@@ -1580,54 +1600,75 @@ img.monero-logo {
transition: all ease-out .1s;
}
-/*.topnav .topnav-list .language-change {
+.topnav .topnav-list .language-change, .topnav .topnav-list .top-link {
+ font-size: 0.9rem;
+}
+
+.topnav .topnav-list .top-link {
+ padding: 0.8rem 1rem;
+}
+
+.topnav .topnav-list .top-link.language-change {
position: relative;
+ display: inline-block;
+ padding: 0;
+ margin-right: 3.5rem;
+}
+
+.topnav .topnav-list .language-change label {
+ height: 100%;
+ /*width: 100%;*/
+ padding: 0.8rem 1rem;
display: block;
}
-.topnav .topnav-list .language-change,*/ .topnav .topnav-list .top-link {
- padding-top: 0.8rem;
- padding-bottom: 0.8rem;
- padding-right: 4.5rem;
- font-size: 0.9rem;
-}
+.topnav .topnav-list .language-change label:hover {
+ color: #ff7519;
+ cursor: pointer;
+}
-/*.topnav .topnav-list .language-change:hover {
+.topnav .topnav-list .language-change input:checked + label {
background-color: #fcfcfc;
+ -moz-box-shadow: 0 3px 5px rgba(50,50,93,.1);
+ -webkit-box-shadow: 0 3px 5px rgba(50,50,93,.1);
+ box-shadow: 0 3px 5px rgba(50,50,93,.1);
}
-.topnav .topnav-list .language-change:hover>.dropdown-content {
- opacity: 1;
- visibility: visible;
+.topnav .topnav-list .language-change input:checked ~ .dropdown-content {
+ display: block;
}
.topnav .topnav-list .language-change label div.arrow-down {
display: inline-block;
margin-bottom: 0.25rem;
- margin-left: 0.1rem;
+ margin-left: 0.2rem;
border-top: 3px solid #7a7a7a;
+}
+.topnav .topnav-list .language-change label:hover div.arrow-down {
+ border-top: 3px solid #ff7519;
}
.topnav .topnav-list .language-change .dropdown-content {
+ display: none;
position: absolute;
left: 0;
- top: 99.5%;
+ top: 2.8rem;
text-align: left;
background: #fcfcfc;
- width: 100%;
+ width: 100%;
-webkit-box-sizing: border-box;
-moz-box-sizing: border-box;
box-sizing: border-box;
- opacity: 0;
- visibility: hidden;
z-index: 1;
-webkit-transition: all .3s ease;
-moz-transition: all .3s ease;
-ms-transition: all .3s ease;
-o-transition: all .3s ease;
transition: all .3s ease;
-
+ -moz-box-shadow: 0 3px 5px rgba(50,50,93,.1);
+ -webkit-box-shadow: 0 3px 5px rgba(50,50,93,.1);
+ box-shadow: 0 3px 5px rgba(50,50,93,.1);
}
.topnav .topnav-list .language-change .dropdown-content a {
@@ -1636,11 +1677,12 @@ img.monero-logo {
.topnav .topnav-list .language-change .dropdown-content a:hover, .topnav .topnav-list .language-change .dropdown-content a:focus {
text-decoration: none;
+ /*background-color: #f9f9fa;*/
}
.topnav .topnav-list .language-change .dropdown-content a.active {
color: #ff7519;
-}*/
+}
.topnav .topnav-list a:hover, .topnav .topnav-list a:focus, .topnav .topnav-list a:active {
@@ -1744,13 +1786,12 @@ img.monero-logo {
font-family: 'Hind', sans-serif;
font-weight: 500;
font-size: 0.99rem;
- padding: 0.8rem 3.4rem 0.8rem 3.5rem;
+ padding: 0.8rem 3rem 0.8rem 3.5rem;
-webkit-transition: all ease-out .2s;
-moz-transition: all ease-out .2s;
-o-transition: all ease-out .2s;
transition: all ease-out .2s;
line-height: 1.3;
- white-space: nowrap;
}
.nav-item>.dropdown-content>a:hover {
@@ -1767,9 +1808,13 @@ img.monero-logo {
}
@media only screen and (max-width: 75rem) {
-
+
+.topnav .topnav-list .top-link.language-change {
+ margin-right: 3.1rem;
+ font-size: 0.85rem;
+}
+
.topnav .topnav-list .top-link {
- padding-right: 4.1rem;
font-size: 0.85rem;
}
@@ -1777,6 +1822,14 @@ img.monero-logo {
padding-left: 3.1rem;
}
+.topnav .topnav-list .top-link {
+ padding: 0.8rem 0.5rem;
+}
+
+.topnav .topnav-list .language-change .dropdown-content {
+ top: 1.9rem;
+}
+
.nav-items>.nav-item>label, .nav-item>.dropdown-content>a {
padding-left: 2.7rem;
}
@@ -1786,8 +1839,8 @@ img.monero-logo {
}
.nav-item>.dropdown-content>a {
- font-size: 1rem;
- padding-right: 2.7rem;
+ font-size: 0.9rem;
+ padding-right: 2.2rem;
}
.nav-items>.nav-item:first-of-type>label, .white-nav .nav-item:first-of-type .dropdown-content a {
@@ -1821,11 +1874,15 @@ img.monero-logo {
@media only screen and (max-width: 62rem) {
+
+/*.mob.bot-nav.white-nav .col-xs-6 a {
+ display: inline-block;
+}*/
img.monero-logo {
position: inherit;
width: 10rem;
- padding: 0.39rem 0 0 0;
+ padding: 0.39rem 0 0.39rem 0;
}
.white-nav {
@@ -2096,17 +2153,94 @@ label[for="mobile-burger"] {
#drop1:checked ~ .dropdown-content, #drop2:checked ~ .dropdown-content, #drop3:checked ~ .dropdown-content, #drop4:checked ~ .dropdown-content {
background-color: #fcfcfc;
}
+
+.mob-language-change, .mob-language-change label {
+ cursor: pointer;
+}
+
+.mob-language-change img.icon-language{
+ width: 1.5rem;
+}
-/*#langdrop:checked ~ .dropdown-content {
- position: absolute;
- top: 100%;
- width: 100vw;
- height: 100vh;
+#moblangdrop:checked ~ .dropdown-content {
display: block;
+ position: inherit;
opacity: 1;
visibility: visible;
box-shadow: none;
-}*/
+ top: 2.92rem;
+ left: 0;
+ right: 0;
+ text-align: center;
+ width: inherit;
+ margin-top: 0.6rem;
+ background-color: #fff;
+}
+label[for="moblangdrop"] {
+ display: block;
+ margin-right: 0.5rem;
+ padding: 0.5rem;
+}
+
+label[for="moblangdrop"], label[for="moblangdrop"]:checked, #moblangdrop, #moblangdrop:checked {
+ -webkit-tap-highlight-color: rgba(0,0,0,0);
+ -webkit-tap-highlight-color: transparent;
+}
+
+#moblangdrop:checked ~ label {
+ background-color: transparent;
+}
+
+#moblangdrop ~ label .arrow-down {
+ display: inline-block;
+ margin-left: 0.2rem;
+ margin-bottom: 0.6rem;
+ border-top: 3px solid #393939;
+}
+
+#moblangdrop:checked ~ label .arrow-down {
+ border-bottom: 3px solid #393939;
+ border-top: 0;
+}
+
+.burger-check:checked + label {
+ position: fixed;
+}
+
+.nav-item > label {
+ display: flex;
+}
+
+.white-nav .mob-language-change {
+ position: fixed;
+ right: 0;
+ align-self: center;
+ font-family: 'Open Sans', sans-serif;
+}
+
+.white-nav .mob-language-change label {
+ color: #393939;
+}
+
+p.mob-lang-change {
+ padding: 0.8rem;
+ color: #d7d7d7;
+ border-bottom: 1px solid #d7d7d7;
+ border-top: 1px solid #d7d7d7;
+ cursor: default;
+}
+
+a.mob-lang-change {
+ padding: 0.8rem;
+ color: #393939;
+ border-bottom: 1px solid #e8ebef;
+ line-height: 1.7;
+}
+
+a.mob-lang-change:hover, a.mob-lang-change.active, a.mob-lang-change:focus {
+ color: #ff7519;
+ text-decoration: none;
+}
}
@@ -2211,7 +2345,7 @@ img.monero-logo {
}
p.main-resources {
- height: 11rem;
+ height: 12rem;
}
p.main-downloads {
@@ -2362,16 +2496,16 @@ body {
.page-wrapper {
position: relative;
- min-height: 100vh;
+ /*min-height: 100vh;*/
}
-.site-wrap {
+/*.site-wrap {
padding-bottom: 435px;
padding-bottom: 27.1875rem;
-}
+}*/
footer {
- position: absolute;
+ /*position: absolute;*/
bottom: 0;
width: 100%;
background-color: #4c4c4c;
diff --git a/design-goals/index.md b/design-goals/index.md
index 6ba089237f4ab6c848b69b32d2737c2c4f01dbdb..3445fd8dafb7d86cfa646941b9608d8834db9815 100644
--- a/design-goals/index.md
+++ b/design-goals/index.md
@@ -1,5 +1,5 @@
---
-layout: default
+layout: user-guide
title: "Design and Development Goals"
title-pre-kick: "Design and Development "
title-kick: "Goals"
diff --git a/downloads/index.md b/downloads/index.md
index 604848cb8ca69e98fbbdd9dd0332070f4312de57..40b571190f469bdcbc456c311dd531ed08d53e3d 100644
--- a/downloads/index.md
+++ b/downloads/index.md
@@ -1,143 +1,6 @@
---
layout: custom
-title: "Downloads"
+title: titles.downloads
+permalink: /downloads/index.html
---
-
-<div class="downloads">
-
-<div class="container description" markdown="1">
-
-If you need help choosing the correct application, please click [here](https://www.reddit.com/r/Monero/comments/64b5lf/what_is_the_best_monero_wallet/) for a quick answer, then select the appropriate release for your operating system below.
-Note: the SHA256 hashes are listed by the downloads for convenience, but a GPG-signed list of the hashes is at [getmonero.org/downloads/hashes.txt](https://getmonero.org/downloads/hashes.txt) and should be treated as canonical, with the signature checked against the appropriate GPG key in the source code (in /utils/gpg_keys).
-
-</div>
-<div class="container full downdropdown">
-<div class="info-block download-nav row middle-xs between-xs" id="selections">
-
- <div class="col"><a href="#windows">Windows</a></div>
- <div class="col"><a href="#mac">Mac</a></div>
- <div class="col"><a href="#linux">Linux</a></div>
- <div class="col"><a href="#arm">Arm (v7 & 8)</a></div>
- <div class="col"><a href="#bsd">BSD</a></div>
- <div class="col"><a href="#source">Source & Blockchain</a></div>
- <div class="col"><a href="#mobilelight">Mobile & Light</a></div>
- <div class="col"><a href="#hardware">Hardware</a></div>
-
-</div>
-</div>
-
-<div class="container full">
- <div class="info-block row center-xs" id="pick-platform">
- <div class="mob dropdowndrop">
- <input id="check01" type="checkbox" name="menu"/>
- <label for="check01">Choose your OS</label>
- <ul id="menu">
- <li><a href="#windows">Windows</a></li>
- <li><a href="#mac">Mac</a></li>
- <li><a href="#linux">Linux</a></li>
- <li><a href="#arm">Arm (v7 & 8)</a></li>
- <li><a href="#bsd">BSD</a></li>
- <li><a href="#source">Source & Blockchain</a></li>
- <li><a href="#mobilelight">Mobile & Light</a></li>
- <li><a href="#hardware">Hardware</a></li>
- </ul>
- </div>
- </div>
-</div>
-
-
-<div class="download-platforms">
-
-{% for data_downloads in site.data.downloads %}
-
-<section class="container full" id="{{ data_downloads.id}}">
- <div class="info-block">
- <h2>
- {% if data_downloads.icon != null %}
- <span class="{{data_downloads.icon}}"></span>
- {% endif %}
- {{data_downloads.platform}}
- </h2>
- {% if data_downloads.version != null %}
- <p class="text-center">Current Version: {{ data_downloads.version }} {{ data_downloads.tag }}</p>
- {%endif%}
-
-
-
-{% if data_downloads.cli_hash == "source" %}
-<div class="row">
-<div class="col-md-8 col-md-offset-2 col-sm-12 col-xs-12">
-<h4 id="{{ data_downloads.platform | slugify }}">
- <a href="{{ data_downloads.cli_url }}">Source Code</a>
-</h4>
-</div>
-<div class="col-md-8 col-md-offset-2 col-sm-12 col-xs-12" markdown="1">
-If you'd prefer to use a blockchain bootstrap, instead of syncing from scratch, you can [use this link for the most current bootstrap](https://downloads.getmonero.org/blockchain.raw). It is typically much faster to sync from scratch, however, and it also takes a lot less RAM (import is very greedy).
-</div>
-</div>
-{% elsif data_downloads.id == "hardware" %}
-<div class="row">
-<div class="col-md-8 col-md-offset-2 col-sm-12 col-xs-12">
-<p>The Monero community has just funded a <a href="https://forum.getmonero.org/9/work-in-progress/88149/dedicated-monero-hardware-wallet" target="_blank" rel="noreferrer, noopener">Dedicated Hardware Wallet</a> which is now in progress. As well, Ledger is working on <a href="https://github.com/LedgerHQ/blue-app-monero" target="_blank" rel="noreferrer, noopener">integrating Monero into their hardware wallets</a>.</p>
-</div></div>
-
-{% elsif data_downloads.id == "mobilelight" %}
-<div class="row">
-<div class="col-md-8 col-md-offset-2 col-sm-12 col-xs-12">
-<p>The following are mobile or light wallets that are deemed safe by trusted members of the community. If there is a wallet that is not on here, you can request the community check it out. Go to our <a href="/community/hangouts/">Hangouts</a> page to see where we are.</p>
-</div>
-</div>
-<div class="row center-xs">
- <div class="col-xs-12">
- <a href="https://mymonero.com"><img src="/img/mymonero.png" alt="MyMonero Logo"></a>
- </div>
-</div>
-
-
-{% elsif data_downloads.gui_hash == nil and data_downloads.cli_hash != nil %}
-<div class="row"><div class="col-md-8 col-md-offset-2 col-sm-12 col-xs-12"><h4 id="{{ data_downloads.platform | slugify }}">
- <a href="//downloads.getmonero.org/cli/{{ data_downloads.cli_url }}"> {{ data_downloads.platform }} (Command-line Tools Only)</a>
- </h4></div></div>
- <div class="row"><div class="col-md-8 col-md-offset-2 col-sm-12 col-xs-12">
- <p><strong>SHA256 Hash:</strong></p> <p class="hash"> {{ data_downloads.cli_hash }}</p></div>
-</div>
-{% elsif data_downloads.gui_hash != nil and data_downloads.cli_hash == nil %}
-<div class="row">
-
-<h4 id="{{ data_downloads.platform | slugify }}">
- <a href="//downloads.getmonero.org/gui/{{ data_downloads.gui_url }}">{{ data_downloads.platform }}</a>
- </h4></div>
-<div class="row">
-<p><strong>SHA256 Hash:</strong></p> <p class="hash"> {{ data_downloads.gui_hash }}</p>
-</div>
-{% elsif data_downloads.gui_hash != nil and data_downloads.cli_hash != nil %}
-<div class="row start-md">
-<div class="col-md-6 col-sm-12" >
-
-<h4 id="{{ data_downloads.platform | slugify }}">
- <a href="//downloads.getmonero.org/gui/{{ data_downloads.gui_url }}">{{ data_downloads.platform }}</a>
-</h4>
-<p><strong>SHA256 Hash (GUI):</strong></p> <p class="hash"> {{ data_downloads.gui_hash }}</p>
-
-</div>
-
-<div class="col-md-6 col-sm-12">
-<h4>
- <a href="//downloads.getmonero.org/cli/{{ data_downloads.cli_url }}">{{ data_downloads.platform }} (Command-Line Tools Only)</a>
-</h4>
-<p><strong>SHA256 Hash (CLI):</strong></p> <p class="hash"> {{ data_downloads.cli_hash }}</p>
-</div>
-</div>
-{% endif %}
- </div>
-</section>
-
-{% endfor %}
-
-</div>
-<a href="#" class="arrow-up"><i></i></a>
-
-</div>
-
-
-
+{% tf downloads.md %}
\ No newline at end of file
diff --git a/forum-funding-system/completed-proposals/index.html b/forum-funding-system/completed-proposals/index.html
index 29aa9eb079a5fd394ea55f1d01ab614677347914..00fac6b1e0a1b4e3ba963e52f8493c5f2b78ba63 100644
--- a/forum-funding-system/completed-proposals/index.html
+++ b/forum-funding-system/completed-proposals/index.html
@@ -1,6 +1,6 @@
---
layout: custom
-title: Completed Proposals
+title: titles.ffs-cp
---
<div class="container ffs-backlink">
diff --git a/forum-funding-system/funding-required/index.html b/forum-funding-system/funding-required/index.html
index c27d7419177cd82d2d8274b606d9e65f08694f96..d74324678ad6ecefcb853b50b6280d21c335f9ea 100644
--- a/forum-funding-system/funding-required/index.html
+++ b/forum-funding-system/funding-required/index.html
@@ -1,6 +1,6 @@
---
layout: custom
-title: Funding Required
+title: titles.ffs-fr
---
<div class="container ffs-backlink">
diff --git a/forum-funding-system/ideas/index.html b/forum-funding-system/ideas/index.html
index 0f3ef3f07de3327159233a28d36f5b1e9a0bf792..628f2abf7944b634e42eca60b045fef61c4d027d 100644
--- a/forum-funding-system/ideas/index.html
+++ b/forum-funding-system/ideas/index.html
@@ -1,6 +1,6 @@
---
layout: custom
-title: Ideas
+title: titles.ffs-ideas
---
<div class="container ffs-backlink">
diff --git a/forum-funding-system/index.md b/forum-funding-system/index.md
index 29a15dd67b256ba2c562239b5a7e3e6af799ae01..74aad5ba97134fcc2fd29b5cd93338e13d609e87 100644
--- a/forum-funding-system/index.md
+++ b/forum-funding-system/index.md
@@ -1,6 +1,6 @@
---
layout: custom
-title: Forum Funding System
+title: titles.ffs
---
<div class="ffs">
<div class="desktop">
@@ -18,14 +18,14 @@ title: Forum Funding System
{% for toplevel in site.data.ffs %}
{% if toplevel.stage == "Ideas" %}
{% for proposal in toplevel.proposals limit:2 %}
- <h3><a href="{{proposal.url}}">{{proposal.name}}</a></h3>
+ <h3><a href="{{site.baseurl}}/{{proposal.url}}">{{proposal.name}}</a></h3>
<p>Summary: {{proposal.summary}}</p>
<p>Author: {{proposal.author}}</p>
{%endfor%}
{%endif%}
{%endfor%}
<div class="row center-xs">
- <p><a href="/forum-funding-system/ideas/" class="btn-link btn-fixed">See all Ideas</a></p>
+ <p><a href="{{site.baseurl}}/forum-funding-system/ideas/" class="btn-link btn-fixed">See all Ideas</a></p>
</div>
</div>
<label for="tab-2" tabindex="0"></label>
@@ -35,13 +35,13 @@ title: Forum Funding System
{% for toplevel in site.data.ffs %}
{% if toplevel.stage == "Open Tasks" %}
{% for proposal in toplevel.proposals limit:2 %}
- <h3><a href="{{proposal.url}}">{{proposal.name}}</a></h3>
+ <h3><a href="{{site.baseurl}}/{{proposal.url}}">{{proposal.name}}</a></h3>
<p>Summary: {{proposal.summary}}</p>
<p>Author: {{proposal.author}}</p>
{%endfor%}
{%endif%}
{%endfor%}
- <div class="row center-xs"><p><a href="/forum-funding-system/open-tasks/" class="btn-link btn-fixed">See all Open Tasks</a></p>
+ <div class="row center-xs"><p><a href="{{site.baseurl}}/forum-funding-system/open-tasks/" class="btn-link btn-fixed">See all Open Tasks</a></p>
</div>
</div>
<label for="tab-3" tabindex="0"></label>
@@ -51,14 +51,14 @@ title: Forum Funding System
{% for toplevel in site.data.ffs %}
{% if toplevel.stage == "Funding Required" %}
{% for proposal in toplevel.proposals limit:2 %}
- <h3><a href="{{proposal.url}}">{{proposal.name}}</a></h3>
+ <h3><a href="{{site.baseurl}}/{{proposal.url}}">{{proposal.name}}</a></h3>
<p>Summary: {{proposal.summary}}</p>
<p>Author: {{proposal.author}}</p>
{%endfor%}
{%endif%}
{%endfor%}
<div class="row center-xs">
- <p><a href="/forum-funding-system/funding-required/" class="btn-link btn-fixed">See all Funding Required</a></p>
+ <p><a href="{{site.baseurl}}/forum-funding-system/funding-required/" class="btn-link btn-fixed">See all Funding Required</a></p>
</div>
</div>
<label for="tab-4" tabindex="0"></label>
@@ -68,14 +68,14 @@ title: Forum Funding System
{% for toplevel in site.data.ffs %}
{% if toplevel.stage == "Work in Progress" %}
{% for proposal in toplevel.proposals limit:2 %}
- <h3><a href="{{proposal.url}}">{{proposal.name}}</a></h3>
+ <h3><a href="{{site.baseurl}}/{{proposal.url}}">{{proposal.name}}</a></h3>
<p>Summary: {{proposal.summary}}</p>
<p>Author: {{proposal.author}}</p>
{%endfor%}
{%endif%}
{%endfor%}
<div class="row center-xs">
- <p><a href="/forum-funding-system/work-in-progress/" class="btn-link btn-fixed">See all Work in Progress</a></p>
+ <p><a href="{{site.baseurl}}/forum-funding-system/work-in-progress/" class="btn-link btn-fixed">See all Work in Progress</a></p>
</div>
</div>
<label for="tab-5" tabindex="0"></label>
@@ -85,14 +85,14 @@ title: Forum Funding System
{% for toplevel in site.data.ffs %}
{% if toplevel.stage == "Completed Proposals" %}
{% for proposal in toplevel.proposals limit:2 %}
- <h3><a href="{{proposal.url}}">{{proposal.name}}</a></h3>
+ <h3><a href="{{site.baseurl}}/{{proposal.url}}">{{proposal.name}}</a></h3>
<p>Summary: {{proposal.summary}}</p>
<p>Author: {{proposal.author}}</p>
{%endfor%}
{%endif%}
{%endfor%}
<div class="row center-xs">
- <p><a href="/forum-funding-system/completed-proposals/" class="btn-link btn-fixed">See Completed Proposals</a></p>
+ <p><a href="{{site.baseurl}}/forum-funding-system/completed-proposals/" class="btn-link btn-fixed">See Completed Proposals</a></p>
</div>
</div>
</div>
@@ -105,7 +105,7 @@ title: Forum Funding System
<div class="row">
<div class="col-md-6 col-sm-6 col-xs-6">
<div class="ffs-btn-wrap">
- <a id="ffs-ideas" class="ffs-btn" href="/forum-funding-system/ideas/">Ideas
+ <a id="ffs-ideas" class="ffs-btn" href="{{site.baseurl}}/forum-funding-system/ideas/">Ideas
</a>
</div>
</div>
@@ -113,7 +113,7 @@ title: Forum Funding System
<div class="col-md-6 col-sm-6 col-xs-6">
<div class="ffs-btn-wrap">
- <a id="ffs-opentasks" class="ffs-btn" href="/forum-funding-system/open-tasks/">Open Tasks</a>
+ <a id="ffs-opentasks" class="ffs-btn" href="{{site.baseurl}}/forum-funding-system/open-tasks/">Open Tasks</a>
</div>
</div>
@@ -124,7 +124,7 @@ title: Forum Funding System
<div class="col-md-6 col-sm-6 col-xs-6">
<div class="ffs-btn-wrap">
- <a id="ffs-fundingrequired" class="ffs-btn" href="/forum-funding-system/funding-required/">Funding Required</a>
+ <a id="ffs-fundingrequired" class="ffs-btn" href="{{site.baseurl}}/forum-funding-system/funding-required/">Funding Required</a>
</div>
</div>
@@ -132,7 +132,7 @@ title: Forum Funding System
<div class="col-md-6 col-sm-6 col-xs-6">
<div class="ffs-btn-wrap">
- <a id="ffs-workinprogress" class="ffs-btn" href="/forum-funding-system/work-in-progress/">Work in Progress</a>
+ <a id="ffs-workinprogress" class="ffs-btn" href="{{site.baseurl}}/forum-funding-system/work-in-progress/">Work in Progress</a>
</div>
</div>
@@ -144,7 +144,7 @@ title: Forum Funding System
<div class="col-xs-12">
<div class="ffs-btn-wrap">
- <a id="ffs-completedproposals" class="ffs-btn" href="/forum-funding-system/completed-proposals/">Completed Proposals</a>
+ <a id="ffs-completedproposals" class="ffs-btn" href="{{site.baseurl}}/forum-funding-system/completed-proposals/">Completed Proposals</a>
</div>
</div>
diff --git a/forum-funding-system/open-tasks/index.html b/forum-funding-system/open-tasks/index.html
index 73ab28d7e2c7ae395fbeeea0dd4e1749b3713684..c5204d354c8f0c9850e51117a79d15872728ec09 100644
--- a/forum-funding-system/open-tasks/index.html
+++ b/forum-funding-system/open-tasks/index.html
@@ -1,6 +1,6 @@
---
layout: custom
-title: Open Tasks
+title: titles.ffs-ot
---
<div class="container ffs-backlink">
diff --git a/forum-funding-system/work-in-progress/index.html b/forum-funding-system/work-in-progress/index.html
index 16725f2fe65c0dc272708ddb8f4cdef7985c06d8..343e3f9215c3473dd1bf61d434c6943d4d2bf290 100644
--- a/forum-funding-system/work-in-progress/index.html
+++ b/forum-funding-system/work-in-progress/index.html
@@ -1,6 +1,6 @@
---
layout: custom
-title: Work in Progress
+title: titles.ffs-wip
---
<div class="container ffs-backlink">
diff --git a/get-started/accepting/index.md b/get-started/accepting/index.md
index 9b6935ebf50caaea0ee560a909cd0c0bf63d7e78..5c11f4b8335d1a454edd4f0f7555aa7ee79bae86 100644
--- a/get-started/accepting/index.md
+++ b/get-started/accepting/index.md
@@ -1,94 +1,6 @@
---
layout: custom
-title: "Accepting Monero"
+title: titles.accepting
+permalink: /get-started/accepting/index.html
---
-
-<section class="container">
- <div class="row">
- <!-- left two-thirds block-->
- <div class="full">
- <div class="info-block text-adapt">
- <div class="row center-xs">
- <div class="col">
- <h2>Instructions for the Command-Line Interface</h2>
- </div>
- </div>
-<div markdown="1">
-
-### The Basics
-
-Monero works a little differently to what you may have become accustomed to from other @cryptocurrencies. In the case of a digital currency like Bitcoin and its many derivatives merchant payment systems will usually create a new recipient @address for each payment or user.
-
-However, because Monero has @stealth-addresses there is no need to have separate recipient addresses for each payment or user, and a single @account address can be published. Instead, when receiving payments a merchant will provide the person paying with a "payment ID".
-
-A @payment-ID is a hexadecimal string that is 64 characters long, and is normally randomly created by the merchant. An example of a payment ID is:
-```
-666c75666679706f6e7920697320746865206265737420706f6e792065766572
-```
-
-### Checking for a Payment in monero-wallet-cli
-
-If you want to check for a payment using monero-wallet-cli you can use the "payments" command followed by the payment ID or payment IDs you want to check. For example:
-
-```
-[wallet 49VNLa]: payments 666c75666679706f6e7920697320746865206265737420706f6e792065766572
- payment transaction height amount unlock time
- 666c75666679706f6e79206973207 7ba4cd810c9b4096869849458181e98e 441942 30.00000 0
-[wallet 49VNLa]: â–ˆ
-```
-
-If you need to check for payments programmatically, then details follow the next section.
-
-### Receiving a Payment Step-by-Step
-
-* Generate a random 64 character hexadecimal string for the payment
-* Communicate the payment ID and Monero address to the individual who is making payment
-* Check for the payment using the "payments" command in monero-wallet-cli
-
-### Checking for a Payment Programmatically
-
-In order to check for a payment programmatically you can use the get_payments or get_bulk_payments JSON RPC API calls.
-
-*get_payments*: this requires a payment_id parameter with a single payment ID.
-
-*get_bulk_payments*: this is the preferred method, and requires two parameters, payment_ids - a JSON array of payment IDs - and an optional min_block_height - the block height to scan from.
-
-An example of returned data is as follows:
-
-```
-[ monero->~ ]$ curl -X POST http://127.0.0.1:18500/json_rpc -d '{"jsonrpc":"2.0","method":"get_bulk_payments","id":"test", "params":{"payment_ids": ["666c75666679706f6e7920697320746865206265737420706f6e792065766572"]}}' -H "Content-Type: application/json"
-{
- "id": "test",
- "jsonrpc": "2.0",
- "result": {
- "payments": [{
- "amount": 30000000000000,
- "block_height": 441942,
- "payment_id": "666c75666679706f6e7920697320746865206265737420706f6e792065766572",
- "tx_hash": "7ba4cd810c9b4096869849458181e98e18b6474ab66415de0f4ccf7ab1162fdf",
- "unlock_time": 0
- }]
- }
-}
-```
-
-It is important to note that the amounts returned are in base Monero units and not in the display units normally used in end-user applications. Also, since a transaction will typically have multiple outputs that add up to the total required for the payment, the amounts should be grouped by the tx_hash or the payment_id and added together. Additionally, as multiple outputs can have the same amount, it is imperative not to try and filter out the returned data from a single get_bulk_payments call.
-
-Before scanning for payments it is useful to check against the daemon RPC API (the get_info RPC call) to see if additional blocks have been received. Typically you would want to then scan only from that received block on by specifying it as the min_block_height to get_bulk_payments.
-
-### Programatically Scanning for Payments
-
-* Get the current block height from the daemon, only proceed if it has increased since our last scan
-* Call the get_bulk_payments RPC API call with our last scanned height and the list of all payment IDs in our system
-* Store the current block height as our last scanned height
-* Remove duplicates based on transaction hashes we have already received and processed
-
-</div>
- </div>
- </div>
-
-
- <!-- end right one-third block-->
- </div>
- </section>
-
\ No newline at end of file
+{% tf get-started/accepting.md %}
\ No newline at end of file
diff --git a/get-started/contributing/index.md b/get-started/contributing/index.md
index 88b077552482890a257647dd78b8d6aba061ebf7..dd195ec93b63ac726094a9908d4c1056a14e6f83 100644
--- a/get-started/contributing/index.md
+++ b/get-started/contributing/index.md
@@ -1,96 +1,6 @@
---
layout: custom
-title: Improving Monero
+title: titles.contributing
+permalink: /get-started/contributing/index.html
---
-<div markdown="1" class="text-center container description">
-Monero is an open-source, community-driven project. Described below are several ways to support the project.
-</div>
-
-<div class="contribute">
- <section class="container">
- <div class="row">
- <!-- full block-->
- <div class="full col-lg-12 col-md-12 col-sm-12 col-xs-12">
- <div class="info-block text-adapt">
- <div class="row center-xs">
- <div class="col"><h2>Support the Network</h2></div>
- </div>
-<div class="row start-xs" markdown="1">
-
-### Develop
-Monero is primarily written in C++. As it is a decentralized project, anyone is welcome to add or make changes to existing code. Pull requests are merged based on community consensus. See the <a href="https://github.com/monero-project"> repositories</a> and outstanding <a href="https://github.com/monero-project/monero/issues">issues</a>.
-
-### Run a Full Node
-Run monerod with port 18080 open. Running a full node ensures maximum privacy when transacting with Monero. It also improves distribution of the blockchain to new users.
-
-### Mine
-Mining ensures the Monero network remains decentralized and secure. In the Monero graphical user interface and command-line interface, background mining may be activated. Additional resources for mining may be viewed [here](https://reddit.com/r/MoneroMining).
-
-</div>
- </div>
- </div>
- <!-- end full block-->
- <!-- full block-->
- <div class="full col-lg-12 col-md-12 col-sm-12 col-xs-12">
- <div class="info-block text-adapt">
- <div class="row center-xs">
- <div class="col">
- <h2>View the Forum Funding System</h2>
- </div>
- </div>
- <div class="row start-xs">
- <p>Monero utilizes a <a href="https://forum.getmonero.org">forum funding system</a> whereby projects are proposed for development and community-funded. Funding is held in escrow and remunerated to developers once programming milestones are achieved. Anyone may generate new proposals or fund existing ones.</p>
- </div>
- </div>
- </div>
- <!-- full block-->
- <!-- full block-->
- <div class="full col-lg-12 col-md-12 col-sm-12 col-xs-12">
- <div class="info-block text-adapt">
- <div class="row center-xs">
- <div class="col">
- <h2>Donate</h2>
- </div>
- </div>
- <div class="row start-xs">
- <p>Ongoing development is supported by donations and <a href="/community/sponsorships/">sponsorships</a>.</p>
- </div>
- <div class="row center-xs">
- <div class="col-lg-6">
- <img src="/img/donate-monero.png" alt=""/>
- </div>
- <div class="col-lg-6">
- <img src="/img/donate-bitcoin.png" alt=""/>
- </div>
- </div>
- <div class="row start-xs">
- <div class="col-xs-12">
- <h3>Donating Monero</h3>
- <p>Donations may be sent to donate.getmonero.org or 44AFFq5kSiGBoZ4NMDwYtN18obc8AemS33DBLWs3H7otXft3XjrpDtQGv7SqSsaBYBb98uNbr2VBBEt7f2wfn3RVGQBEP3A</p>
- </div>
- </div>
- <div class="row start-xs">
- <div class="col-xs-12">
- <h3>Donating Bitcoin</h3>
- <p>Donations may be sent to donate.getmonero.org or 1KTexdemPdxSBcG55heUuTjDRYqbC5ZL8H</p>
- </div>
- </div>
- <div class="row start-xs">
- <div class="col-xs-12">
- <h3>Other</h3>
- <p>E-mail <a href="mailto:dev@getmonero.org">dev@getmonero.org</a> for alternative means of donating or if you would like to become a sponsor for the Monero Project.</p>
- </div>
- </div>
- </div>
- </div>
- <!-- full block-->
-
-
-
-
-
-
- </div>
- </section>
-
-</div>
+{% tf get-started/contributing.md %}
\ No newline at end of file
diff --git a/get-started/faq/index.md b/get-started/faq/index.md
index d37d559c724ecb523dc6d130138352383ede58a0..37a0746d642ad5209142b67e4455b0350f7fee6d 100644
--- a/get-started/faq/index.md
+++ b/get-started/faq/index.md
@@ -1,140 +1,6 @@
---
layout: full-text
-title: FAQ
+title: titles.faq
+permalink: /get-started/faq/index.html
---
-
-<div class="tab">
- <input id="tab-one" type="checkbox" name="tabs" class="accordion">
- <label for="tab-one" class="accordion">How does Monero have value?</label>
-
-<div class="tab-content" markdown="1">
-
-Monero has value because people are willing to buy it. If no one is willing to buy Monero, then it will not have any value. Monero’s price increases if demand exceeds supply, and it decreases if supply exceeds demand.
-
-</div>
-
-</div>
-
-<div class="tab">
- <input id="tab-two" type="checkbox" name="tabs" class="accordion">
- <label for="tab-two" class="accordion">How can I get Monero?</label>
-
-<div class="tab-content" markdown="1">
-
-You can buy Monero from an exchange or from an individual. Alternatively, you can try mining Monero to get coins from the block reward.
-</div>
-
-</div>
-
-<div class="tab">
- <input id="tab-three" type="checkbox" name="tabs" class="accordion">
- <label for="tab-three" class="accordion">What is a mnemonic seed?</label>
-
-<div class="tab-content" markdown="1">
-
-A mnemonic seed is a set of 25 words that can be used to restore your account anywhere. Keep these words safe and do not share them with someone else. You can use this seed to restore your account, even if your computer crashes.
-</div>
-
-</div>
-
-<div class="tab">
- <input id="tab-four" type="checkbox" name="tabs" class="accordion">
- <label for="tab-four" class="accordion">How is Monero’s privacy different from other coins?</label>
-
-<div class="tab-content" markdown="1">
-
-Monero uses three different privacy technologies: ring signatures, ring confidential transactions (RingCT), and stealth addresses. These hide the sender, amount, and receiver in the transaction, respectively. All transactions on the network are private by mandate; there is no way to accidentally send a transparent transaction. This feature is exclusive to Monero. You do not need to trust anyone else with your privacy.
-</div>
-
-</div>
-
-<div class="tab">
- <input id="tab-five" type="checkbox" name="tabs" class="accordion">
- <label for="tab-five" class="accordion">Why is my wallet taking so long to sync?</label>
-
-<div class="tab-content" markdown="1">
-
-If you are running a full node locally, you need to copy the entire blockchain to your computer. This can take a long time, especially on an old hard drive or slow internet connection. If you are using a remote node, your computer still needs to request a copy of all the outputs, which can take several hours. Be patient, and if you would like to sacrifice some privacy for faster sync times, consider using a lightweight wallet instead.
-</div>
-
-</div>
-
-<div class="tab">
- <input id="tab-six" type="checkbox" name="tabs" class="accordion">
- <label for="tab-six" class="accordion">What is the different between a lightweight and a normal wallet?</label>
-
-<div class="tab-content" markdown="1">
-
-For a lightweight wallet, you give your view key to a node, who scans the blockchain and looks for incoming transactions to your account on your behalf. This node will know when you receive money, but it will not know how much you receive, who you received it from, or who you are sending money to. Depending on your wallet software, you may be able to use a node you control to avoid privacy leaks. For more privacy, use a normal wallet, which can be used with your own node.
-</div>
-
-</div>
-
-<div class="tab">
- <input id="tab-seven" type="checkbox" name="tabs" class="accordion">
- <label for="tab-seven" class="accordion">How is Monero different from Bitcoin?</label>
-
-<div class="tab-content" markdown="1">
-
-Monero is not based on Bitcoin. It is based on the CryptoNote protocol. Bitcoin is a completely transparent system, where people can see exactly how much money is being sent from one user to another. Monero hides this information to protect user privacy in all transactions. It also has a dynamic block size and dynamic fees, an ASIC-resistant proof of work, and a tail coin emission, among several other changes.
-</div>
-
-</div>
-
-<div class="tab">
- <input id="tab-eight" type="checkbox" name="tabs" class="accordion">
- <label for="tab-eight" class="accordion">Does Monero have a block size limit?</label>
-
-<div class="tab-content" markdown="1">
-
-No, Monero does not have a hard block size limit. Instead, the block size can increase or decrease over time based on demand. It is capped at a certain growth rate to prevent outrageous growth.
-</div>
-
-</div>
-
-<div class="tab">
- <input id="tab-nine" type="checkbox" name="tabs" class="accordion">
- <label for="tab-nine" class="accordion">What is a blockchain?</label>
-
-<div class="tab-content" markdown="1">
-
-A blockchain is a system that stores a copy of all transaction history on the Monero network. Every two minutes, a new block with the latest transaction information is added to the blockchain. This chain allows the network to verify the amount of money accounts have and make it resilient to attacks and centralization attempts.
-</div>
-
-</div>
-
-<div class="tab">
- <input id="tab-ten" type="checkbox" name="tabs" class="accordion">
- <label for="tab-ten" class="accordion">What is Kovri?</label>
-
-<div class="tab-content" markdown="1">
-
-Kovri is an I2P router written in C++. I2P is a hidden network like Tor with several technical differences. Kovri is an independent project of Monero, but it will work with Monero and several other projects. Kovri hides the transaction broadcast, so other nodes do not know who created transactions. In adversarial conditions, Kovri can be used to hide all Monero traffic through I2P, which would prevent people from knowing Monero is being used. Kovri is currently in alpha, and it is not yet fully integrated in Monero. Learn more about Kovri at the [project website.](https://getkovri.org)
-</div>
-
-</div>
-
-<div class="tab">
- <input id="tab-eleven" type="checkbox" name="tabs" class="accordion">
- <label for="tab-eleven" class="accordion">What is fungibility, and why is it important?</label>
-
-<div class="tab-content" markdown="1">
-
-Fungibility is a simple property of money such that there are no differences between two amounts of the same value. If two people exchanged a 10 and two 5’s, then no one would lose out. However, let’s suppose that everyone knows the 10 was previously used in a ransomware attack. Is the other person still going to make the trade? Probably not, even if the person with the 10 has no connection with the ransomware. This is a problem, since the receiver of money needs to constantly check the money they are receiving to not end up with tainted coins. Monero is fungible, which means people do not need to go through this effort.
-</div>
-
-</div>
-
-<div class="tab">
- <input id="tab-twelve" type="checkbox" name="tabs" class="accordion">
- <label for="tab-twelve" class="accordion">If Monero is so private how do we know they're not being created out of thin air?</label>
-
-<div class="tab-content" markdown="1">
-In Monero, every transaction output is uniquely associated with a key image that can only be generated by the holder of that output. Key images that are used more than once are rejected by the miners as double-spends and cannot be added to a valid block. When a new transaction is received, miners verify that the key image does not already exist for a previous transaction to ensure it's not a double-spend.
-
-We can also know that transaction amounts are valid even though the value of the inputs that you are spending and the value of the outputs you are sending are encrypted (these are hidden to everyone except the recipient). Because the amounts are encrypted using Pedersen commitments what this means is that no observers can tell the amounts of the inputs and outputs, but they can do math on the Pedersen commitments to determine that no Monero was created out of thin air.
-
-As long as the encrypted output amounts you create is equal to the sum of the inputs that are being spent (which include an output for the recipient and a change output back to yourself and the unencrypted transaction fee), then you have a legitimate transaction and know no Monero is being created out of thin air. 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.
-</div>
-
-</div>
+{% tf get-started/faq.md %}
\ No newline at end of file
diff --git a/get-started/mining/index.md b/get-started/mining/index.md
index 361ee67da3dfd95f11b0ae9158affaadc51f5e64..d9a921c7e91833adae38d090907a1583ad7679d9 100644
--- a/get-started/mining/index.md
+++ b/get-started/mining/index.md
@@ -1,97 +1,6 @@
---
layout: custom
-title: Mining Monero
+title: titles.mining
+permalink: /get-started/mining/index.html
---
-<div class="mining">
-<div class="center-xs container description">
-<p>Monero is a cryptocurrency that relies on proof-of-work mining to achieve distributed consensus. Below you'll find some information and resources on how to begin mining.</p>
-
-<p><strong>The Monero Project does not endorse any particular pool, software, or hardware, and the content below is provided for informational purposes only.</strong></p>
-</div>
-
-<section class="container">
- <div class="row">
- <!-- full block-->
- <div class="full col-lg-12 col-md-12 col-sm-12 col-xs-12">
- <div class="info-block">
- <div class="row center-xs">
- <div class="col">
- <h2>Support</h2>
- </div>
- </div>
- <div class="row center-xs">
- <p>See <a href="/community/hangouts/"> Hangouts</a>, <a href="https://www.reddit.com/r/MoneroMining/" target="_blank" rel="noreferrer noopener">/r/moneromining</a> and <a href="irc://chat.freenode.net/#monero-pools" target="_blank" rel="noreferrer noopener">#monero-pools</a>.</p>
- </div>
- </div>
- </div>
- <!-- end full block -->
- </div>
- </section>
-<section class="container">
- <div class="row">
- <div class="left half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
- <div class="info-block">
- <div class="row center-xs">
- <div class="col">
- <h2>Pools</h2>
- </div>
- </div>
- <div class="row center-xs">
- <p>A listing of trusted Monero pools is found <a href="http://moneropools.com/"> here</a>.</p>
- </div>
- </div>
- </div>
- <div class="right half col-lg-6 col-md-6 col-sm-12 col-xs-12">
- <div class="info-block">
- <div class="row center-xs">
- <div class="col">
- <h2>Hardware Benchmarking</h2>
- </div>
- </div>
- <div class="row center-xs">
- <p>See <a href="http://monerobenchmarks.info/">here</a> for a listing of GPUs/CPUs and their respective hashrates.</p>
- </div>
- </div>
- </div>
- </div>
- </section>
- <section class="container">
- <div class="row">
- <!-- full block-->
- <div class="full col-lg-12 col-md-12 col-sm-12 col-xs-12">
- <div class="info-block">
- <div class="row center-xs">
- <div class="col">
- <h2>Mining Software</h2>
- </div>
- </div>
- <div class="row center-xs">
- <p>Note that some miners may have developer fees.</p>
- </div>
- <div class="row miners">
- <div class="col-md-4 col-xs-12 center-xs">
- <h3>AMD Miners</h3>
- <p><a href="https://github.com/fireice-uk/xmr-stak-amd" target="_blank" rel="noreferrer noopener">XMR Stak AMD</a></p>
- <p><a href="https://github.com/OhGodAPet/wolf-xmr-miner" target="_blank" rel="noreferrer noopener">Wolf's AMD Miner</a></p>
- </div>
- <div class="col-md-4 col-xs-12 center-xs">
- <h3>CPU Miners</h3>
- <p><a href="https://github.com/jwinterm/monerospelunker/releases" target="_blank" rel="noreferrer noopener">Monero Spelunker (Windows)</a></p>
- <p><a href="https://github.com/fireice-uk/xmr-stak-cpu" target="_blank" rel="noreferrer noopener">XMR Stak CPU</a></p>
- <p><a href="https://github.com/OhGodAPet/cpuminer-multi" target="_blank" rel="noreferrer noopener">Wolf's CPU Miner</a></p>
- </div>
- <div class="col-md-4 col-xs-12 center-xs">
- <h3>NVidia Miners</h3>
- <p><a href="https://github.com/fireice-uk/xmr-stak-nvidia" target="_blank" rel="noreferrer noopener">XMR Stak NVidia</a></p>
- <p><a href="https://github.com/tsiv/ccminer-cryptonight" target="_blank" rel="noreferrer noopener">CC Miner</a></p>
- <p><a href="https://github.com/xmrMiner/xmrMiner-Win64" target="_blank" rel="noreferrer noopener">XMR Miner (Windows)</a></p>
- </div>
- </div>
- </div>
- </div>
- <!-- end full block -->
- </div>
- </section>
-
-
-</div>
+{% tf get-started/mining.md %}
\ No newline at end of file
diff --git a/get-started/using/index.md b/get-started/using/index.md
index 3049fb60550f1cc0fdb2d8554816cd87505c22ca..4e543413373d7677956aaf465ef3dbb697df006f 100644
--- a/get-started/using/index.md
+++ b/get-started/using/index.md
@@ -1,101 +1,6 @@
---
layout: custom
-title: Using Monero
+title: titles.using
+permalink: /get-started/using/index.html
---
-<div class="text-center container description">
- <p>Transacting with Monero can be made easy. This page is designed to guide users in that process.</p>
-</div>
-<div class="using">
- <section class="container">
- <div class="row">
- <!-- full block-->
- <div class="full col-lg-12 col-md-12 col-sm-12 col-xs-12">
- <div class="info-block text-adapt">
- <div class="row center-xs">
- <div class="col">
- <h2>1. Learn</h2>
- </div>
- </div>
- <div class="row start-xs">
- <p>Monero is a secure, private, and untraceable cryptocurrency. The developers and community are committed to protecting these values. Learn more by reading the <a href="/get-started/what-is-monero/">What is Monero</a> page. The <a href="https://github.com/monero-project">source code</a> is also available for review and discussion.</p>
- </div>
- </div>
- </div>
- <!-- end full block -->
- </div>
- </section>
- <section class="container">
- <div class="row">
- <div class="left half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
- <div class="info-block">
- <div class="row center-xs">
- <div class="col">
- <h2>2. Request Support</h2>
- </div>
- </div>
- <div class="row start-xs">
- <p>There is a large and supportive community that will assist if you experience any difficulty. See the <a href="/community/hangouts/">Hangouts</a> page for more information.</p>
- </div>
- </div>
- </div>
- <div class="right half col-lg-6 col-md-6 col-sm-12 col-xs-12">
- <div class="info-block">
- <div class="row center-xs">
- <div class="col">
- <h2>3. Generate a Wallet</h2>
- </div>
- </div>
- <div class="row start-xs">
- <p>A Monero wallet is required to secure your own funds. See the <a href="/downloads/">Downloads</a> page for a listing of available wallets.</p>
- </div>
- </div>
- </div>
- </div>
- </section>
- <section class="container">
- <div class="row">
- <!-- full block-->
- <div class="full col-lg-12 col-md-12 col-sm-12 col-xs-12">
- <div class="info-block text-adapt">
- <div class="row center-xs">
- <div class="col">
- <h2>4. Acquire Monero</h2>
- </div>
- </div>
- <div class="row start-xs">
- <p>Monero may be purchased on an <a href="/community/merchants#exchanges">exchange</a> with fiat or other cryptocurrencies. An alternate way of acquiring Monero is via <a href="https://getmonero.org/get-started/mining/">mining</a>, the computationally-complex process whereby transactions are immutably recorded on the blockchain.</p>
- </div>
- </div>
- </div>
- <!-- end full block -->
- </div>
- </section>
- <section class="container">
- <div class="row">
- <div class="left half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
- <div class="info-block">
- <div class="row center-xs">
- <div class="col">
- <h2>5. Send and Receive Monero</h2>
- </div>
- </div>
- <div class="row start-xs">
- <p>Learn how to send and receive Monero by viewing the <a href="/get-started/accepting/">guide</a>.</p>
- </div>
- </div>
- </div>
- <div class="right half col-lg-6 col-md-6 col-sm-12 col-xs-12">
- <div class="info-block">
- <div class="row center-xs">
- <div class="col">
- <h2>6. Transact with Monero</h2>
- </div>
- </div>
- <div class="row start-xs">
- <p>Monero may be used to purchase many goods and services. For a listing, see the <a href="/community/merchants/">Merchants</a> page. </p>
- </div>
- </div>
- </div>
- </div>
- </section>
-</div>
+{% tf get-started/using.md %}
\ No newline at end of file
diff --git a/get-started/what-is-monero/index.md b/get-started/what-is-monero/index.md
index ccbe3b43f551287a14e12dbd53ae3f715c3b5308..78035704893fd9c76949a0113685939ec90da8f1 100644
--- a/get-started/what-is-monero/index.md
+++ b/get-started/what-is-monero/index.md
@@ -1,118 +1,7 @@
---
layout: default
-title: "What Is Monero (XMR)?"
+title: titles.whatismonero
+permalink: /get-started/what-is-monero/index.html
---
-<div class="site-wrap">
- <section class="container">
- <div class="row">
- <section class="container about-monero full col-xs-12">
- <div class="info-block">
- <div class="row center-xs">
- <div class="col"><h2>What you need to know</h2></div>
- </div>
- <div class="row middle-xs info-block-row private">
- <div class="col-lg-7 col-md-6 col-sm-8 col-xs-12 why-text">
- <h3>Monero is the leading cryptocurrency with a focus on private and censorship-resistant transactions.</h3>
- <p>Most existing cryptocurrencies, including Bitcoin and Ethereum, have transparent blockchains, meaning that transactions are openly verifiable and traceable by anyone in the world. Furthermore, sending and receiving addresses for these transactions may potentially be linkable to a person's real-world identity. </p>
- <p>Monero uses cryptography to shield sending and receiving addresses, as well as transacted amounts.</p>
- </div>
- <div class="col-lg-5 col-md-6 col-sm-4 col-xs-12 last-sm first-xs center-xs">
- <img src="/img/crypto-lock.png" alt="Encrypted lock" class="main-icon">
- </div>
- </div>
- <div class="row middle-xs info-block-row">
- <div class="col-lg-5 col-md-6 col-sm-4 col-xs-12 center-xs">
- <img src="/img/monero-classified.png" alt="Classified document" class="main-icon">
- </div>
- <div class="col-lg-7 col-md-6 col-sm-8 col-xs-12 why-text">
- <h3>Monero transactions are confidential and untraceable.</h3>
- <p>Every Monero transaction, by default, obfuscates sending and receiving addresses as well as transacted amounts. This always-on privacy means that every Monero user's activity enhances the privacy of all other users, unlike selectively transparent cryptocurrencies (e.g. Z-Cash).</p>
- <p>Monero is fungible. By virtue of obfuscation, Monero cannot become tainted through participation in previous transactions. This means Monero will always be accepted without the risk of censorship.</p>
- <p>The Kovri Project, <a href="https://getkovri.org/">currently in development</a>, will route and encrypt transactions via I2P Invisible Internet Project nodes. This will obfuscate a transactor's IP address and provide further protection against network monitoring.</p>
- </div>
-
- </div>
- <div class="row middle-xs info-block-row">
- <div class="col-lg-7 col-md-6 col-sm-8 col-xs-12 why-text">
- <h3>Monero is a grassroots community attracting the world's best cryptocurrency researchers and engineering talent.</h3>
- <p>Over <a href="https://www.openhub.net/p/monero" target="_blank" rel="noreferrer noopener">240 developers</a> have contributed to the Monero project, including 30 core developers. Forums and chat channels are welcoming and active.</p>
- <p>Monero's Research Lab, Core Development Team and Community Developers are constantly pushing the frontier of what is possible with cryptocurrency privacy and security.</p>
- <p>Monero is not a corporation. It is developed by cryptography and distributed systems experts from all over the world that donate their time or are funded by community donations. This means that Monero can't be shut down by any one country and is not constrained by any particular legal jurisdiction.</p>
- </div>
- <div class="col-lg-5 col-md-6 col-sm-4 col-xs-12 last-sm first-xs center-xs">
- <img src="/img/academic-growth.png" alt="Academic growth" class="main-icon">
- </div>
- </div>
- <div class="row middle-xs info-block-row">
- <div class="col-lg-5 col-md-6 col-sm-4 col-xs-12 center-xs">
- <img src="/img/monero-electronic-cash.png" alt="Electronic cash" class="main-icon">
- </div>
- <div class="col-lg-7 col-md-6 col-sm-8 col-xs-12 why-text">
- <h3>Monero is electronic cash that allows fast, inexpensive payments to and from anywhere in the world.</h3>
- <p>There are no multi-day holding periods and no risk of fraudulent chargebacks. It is safe from ‘capital controls’ - these are measures that restrict the flow of traditional currencies, sometimes to an extreme degree, in countries experiencing economic instability.</p>
- </div>
- </div>
- </div>
- </section>
- <section class="full col-xs-12 monero-vid">
- <div class="info-block">
- <div class="row center-xs">
- <div class="col"><h2>Monero Videos</h2></div>
- </div>
- <div class="row center-xs">
- <div class="col-xs-12 carousel-container">
- <ul class="carousel my-carousel">
- <input class="carousel-activator" type="radio" id="A" name="activator" checked="checked"/>
- <input class="carousel-activator" type="radio" id="B" name="activator"/>
- <input class="carousel-activator" type="radio" id="C" name="activator"/>
- <input class="carousel-activator" type="radio" id="D" name="activator"/>
- <div class="carousel-controls">
- <label class="carousel-control carousel-control-backward" for="D"></label>
- <label class="carousel-control carousel-control-forward" for="B"></label>
- </div>
- <div class="carousel-controls">
- <label class="carousel-control carousel-control-backward" for="A"></label>
- <label class="carousel-control carousel-control-forward" for="C"></label>
- </div>
- <div class="carousel-controls">
- <label class="carousel-control carousel-control-backward" for="B"></label>
- <label class="carousel-control carousel-control-forward" for="D"></label>
- </div>
- <div class="carousel-controls">
- <label class="carousel-control carousel-control-backward" for="C"></label>
- <label class="carousel-control carousel-control-forward" for="A"></label>
- </div>
- <li class="carousel-slide ms">
- <h3>Monero Promo</h3>
- <video controls poster="/img/monero-community.png" onclick="this.paused ? this.play() : this.pause();" preload="none">
- <source src="/media/Monero_Promo.m4v">
- </video>
- </li>
- <li class="carousel-slide">
- <h3>Monero: The Essentials</h3>
- <video controls poster="/img/monero-cash-video-poster.png" onclick="this.paused ? this.play() : this.pause();" preload="none">
- <source src="/media/Monero%20-%20The%20Essentials.m4v">
- </video>
- </li>
- <li class="carousel-slide">
- <h3>Stealth Addresses</h3>
- <video controls poster="/img/stealth-address-poster.png" onclick="this.paused ? this.play() : this.pause();" preload="none">
- <source src="/media/Monero%20-%20Stealth%20Addresses.m4v">
- </video>
- </li>
- <li class="carousel-slide">
- <h3>Ring Signatures</h3>
- <video controls poster="/img/ring-signatures-poster.png" onclick="this.paused ? this.play() : this.pause();" preload="none">
- <source src="/media/Monero%20-%20Ring%20Signatures.m4v">
- </video>
- </li>
- </ul>
- </div>
- </div>
- </div>
- </section>
-
- </div>
- </section>
-</div>
+{% tf get-started/what-is-monero.md %}
\ No newline at end of file
diff --git a/img/Monerujo-wallet.png b/img/Monerujo-wallet.png
new file mode 100644
index 0000000000000000000000000000000000000000..d6c29a495221a592f4d599e88b133cecd61d2b8d
Binary files /dev/null and b/img/Monerujo-wallet.png differ
diff --git a/img/jetbrains.png b/img/jetbrains.png
index 9dcf238723e6f5bbca9e0867a85257210bd98fb0..75430c4b04a49e32220fbfbfa3d7a4e1e868db62 100644
Binary files a/img/jetbrains.png and b/img/jetbrains.png differ
diff --git a/img/language-active.png b/img/language-active.png
new file mode 100644
index 0000000000000000000000000000000000000000..c4527ea768eea779a5cf2e975a19edeca85080cd
Binary files /dev/null and b/img/language-active.png differ
diff --git a/img/language.png b/img/language.png
new file mode 100644
index 0000000000000000000000000000000000000000..17ba0ab1d91454061e7b4de27d4b44157be6d8e0
Binary files /dev/null and b/img/language.png differ
diff --git a/img/monero-core.jpg b/img/monero-core.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6e54483cee0829d854f9c7b3379a95969046aa15
Binary files /dev/null and b/img/monero-core.jpg differ
diff --git a/img/monero-spritesheet.png b/img/monero-spritesheet.png
index d145ffad6d769a6b216d86eeb359ba03c0742ada..91e7984810beb706143f74a06c786801de6ef1a7 100644
Binary files a/img/monero-spritesheet.png and b/img/monero-spritesheet.png differ
diff --git a/img/ringct-poster.png b/img/ringct-poster.png
new file mode 100644
index 0000000000000000000000000000000000000000..ff6f9c5d28eb7719e6a231c0999781f4ad49f649
Binary files /dev/null and b/img/ringct-poster.png differ
diff --git a/index.html b/index.html
index 4ee8af9d0696b27590235d4b16dceae5539440da..00e270f5f32a64ca51250a276039588f7a9acca8 100644
--- a/index.html
+++ b/index.html
@@ -1,195 +1,6 @@
---
layout: base
-Title: Home
+title: Home
+permalink: index.html
---
-
-<div class="site-wrap">
- <section class="container full col-xs-12">
- <div class="info-block info-block-main">
- <div class="row middle-xs">
- <div class="col-lg-7 col-md-7 col-xs-12 main-video">
- <div class="monero-video">
- <!--iframe width="560" height="315" src="https://www.youtube.com/embed/TZi9xx6aiuY" frameborder="0" allowfullscreen></iframe-->
- <video controls poster="img/monero-community.png" onclick="this.paused ? this.play() : this.pause();" preload="none">
- <source src="/media/Monero_Promo.m4v">
- </video>
- </div>
-
- </div>
- <div class="col-lg-5 col-md-5 col-xs-12">
- <div class="main-info">
- <h1 id="main-h1">Monero</h1>
- <h2 id="main-h2">Private Digital Currency</h2>
- <p id="main-text">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.</p>
- <p><a href="/get-started/using/" class="btn-link btn-auto btn-primary">Get Started</a></p>
- </div>
- </div>
- </div>
- </div>
- </section>
-
- <!-- FULL WIDTH BLOCK -->
-
- <section class="container about-main full col-xs-12">
- <div class="info-block">
- <div class="row center-xs">
- <div class="col"><h2>Why Monero is different</h2></div>
- </div>
- <div class="row middle-xs info-block-row private">
- <div class="col-lg-6 col-md-6 col-sm-8 col-xs-12 why-text">
- <h3>Monero is secure.</h3>
- <p>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. </p>
- </div>
- <div class="col-lg-6 col-md-6 col-sm-4 col-xs-12 last-sm first-xs center-xs">
- <img src="/img/secure-monero.png" alt="Secure safe" class="main-icon">
- </div>
- </div>
- <div class="row middle-xs info-block-row">
- <div class="col-lg-6 col-md-6 col-sm-4 col-xs-12 center-xs">
- <img src="/img/private-monero.png" alt="No surveillance" class="main-icon">
- </div>
- <div class="col-lg-6 col-md-6 col-sm-8 col-xs-12 why-text">
- <h3>Monero is private.</h3>
- <p>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. </p>
- </div>
-
- </div>
- <div class="row middle-xs info-block-row">
- <div class="col-lg-6 col-md-6 col-sm-8 col-xs-12 why-text">
- <h3>Monero is untraceable.</h3>
- <p>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.</p>
- </div>
- <div class="col-lg-6 col-md-6 col-sm-4 col-xs-12 last-sm first-xs center-xs">
- <img src="/img/untraceable-monero.png" alt="Untraceable Monero paths" class="main-icon">
- </div>
- </div>
- <div class="row middle-xs info-block-row">
- <div class="col-lg-6 col-md-6 col-sm-4 col-xs-12 center-xs">
- <img src="/img/fungible-monero.png" alt="Monero gold" class="main-icon">
- </div>
- <div class="col-lg-6 col-md-6 col-sm-8 col-xs-12 why-text">
- <h3>Monero is fungible.</h3>
- <p> 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.</p>
- </div>
- </div>
- </div>
- </section>
-
- <!-- END FULL WIDTH BLOCK -->
-
-
-
- <!-- TWO THIRDS & ONE THIRD BLOCKS ROW -->
-
- <section class="container">
- <div class="row">
- <!-- left two-thirds block-->
- <div class="left two-thirds col-lg-8 col-md-8 col-sm-12 col-xs-12">
- <div class="info-block">
- <div class="row center-xs">
- <div class="col"><h2>Downloads</h2></div>
- </div>
- <div class="row around-xs">
- <div class="col">
- <p><a href="/downloads#windows" class="btn-link btn-fixed"><span class="icon-windows"></span>Monero for Windows</a></p>
- </div>
- <div class="col">
- <p><a href="/downloads#mac" class="btn-link btn-fixed"><span class="icon-apple"></span>Monero for Mac</a></p>
- </div>
- </div>
- <div class="row around-xs">
- <div class="col">
- <p><a href="/downloads#linux" class="btn-link btn-fixed"><span class="icon-linux"></span>Monero for Linux</a></p>
- </div>
- <div class="col">
- <p><a href="/downloads#source" class="btn-link btn-fixed"><span class="icon-blockchain"></span>Latest Blockchain</a></p>
- </div>
- </div>
- <div class="row">
- <div class="col-xs-12"><p class="main-downloads">Need it for a different operating system? <a href="/downloads/">View all available downloads here.</a></p>
- </div>
- </div>
- </div>
- </div>
- <!-- end left two-thirds block-->
-
- <!-- right one-third block-->
- <div class="right one-third col-lg-4 col-md-4 col-sm-12 col-xs-12">
- <div class="info-block">
- <div class="row center-xs">
- <div class="col"><h2>Latest News</h2></div>
- </div>
- <div class="info-block-row">
- {% for post in site.posts limit:2 %}
- <div class="row start-xs">
- <div class="col">
- <p><a href="{{ post.url }}">{{ post.title }}</a></p>
- </div>
- </div>
- {% endfor %}
-
-
- <div class="row end-xs">
- <div class="col">
- <p><a href="/blog/">More news</a></p>
- </div>
- </div>
- </div>
- </div>
- </div>
- <!-- end right one-third block-->
- </div>
- </section>
-
- <!-- END TWO THIRDS & ONE THIRD BLOCKS ROW -->
-
- <!-- 3 ONE-THIRD BLOCKS ROW -->
-
- <section class="container">
- <div class="row">
- <!-- left one-third block-->
- <div class="left one-third col-lg-4 col-md-4 col-sm-12 col-xs-12">
- <div class="info-block">
- <div class="row center-xs">
- <div class="col">
- <h2>Moneropedia</h2>
- <p class="main-resources">Would you like to look up the meanings of the terms and concepts used in Monero? Here you will find an alphabetical guide to terms and their meanings from both the Monero and Kovri projects.</p>
- <p><a href="/resources/moneropedia/" class="btn-link btn-auto">Read Moneropedia</a></p>
- </div>
- </div>
- </div>
- </div>
- <!-- end left one-third block-->
-
- <!-- center one-third block-->
- <div class="center one-third col-lg-4 col-md-4 col-sm-12 col-xs-12">
- <div class="info-block">
- <div class="row center-xs">
- <div class="col">
- <h2>User Guides</h2>
- <p class="main-resources">Step-by-step guides to all things Monero are separated by category and cover everything from creating a wallet to supporting the network, and even how to edit this website.</p>
- <p><a href="/resources/user-guides/" class="btn-link btn-auto">Read user guides</a></p>
- </div>
- </div>
- </div>
- </div>
- <!-- end center one-third block-->
-
- <!-- right one-third block-->
- <div class="right one-third col-lg-4 col-md-4 col-sm-12 col-xs-12">
- <div class="info-block">
- <div class="row center-xs">
- <div class="col">
- <h2>FAQ</h2>
- <p class="main-resources">We've heard a lot of questions over the years and have compiled, for your convenience, a thorough and varied FAQ. Don't worry, if your questions are not on here, you can always ask the community.</p>
- <p><a href="/get-started/faq/" class="btn-link btn-auto">Read answers</a></p>
- </div>
- </div>
- </div>
- </div>
- <!-- end right one-third block-->
- </div>
- </section>
-
- <!-- END 3 ONE-THIRD BLOCKS ROW -->
-</div>
+{% tf index.md %}
\ No newline at end of file
diff --git a/legal/copyright.md b/legal/copyright.md
deleted file mode 100644
index 7522b7f893f4a9bea557252ea6eb2907b060866b..0000000000000000000000000000000000000000
--- a/legal/copyright.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-layout: custom
-title: Legal
----
-
-### The Monero Project
-
-The majority of the content on this website, including the Monero logo and our Monero Missive podcast, is released under the CC BY-SA 4.0 license (the [Creative Commons Attribution-ShareAlike 4.0 International license](https://creativecommons.org/licenses/by-sa/4.0/)). This means that you can copy and redistribute the material in any medium or format, and remix, transform, and build upon the material for any purpose, even commercially. However when doing so, you must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests The Monero Project endorses you or your use.
-
-### Icons and Other Attributed Items
-
-Where an icon is used we have attempted to find an icon in public domain or covered by a Creative Commons license. Attribution for the icon is given in HTML comments in the page source where appropriate and possible.
-
-Certain logos, such as those for the operating systems and platforms we support as well as those of our sponsors, are copyrighted by their owners. The Monero Project does not own these copyrights, and use these logos either with permission or in an unambiguous and unharmful way.
-
-### List of Icon Authors
-
-This is a list of original authors of some of the icons used on this website:
-
-- Freepik (<http://www.freepik.com>)
-- Icomoon (<http://www.icomoon.io>)
-- Bogdan Rosu (<http://www.bogdanrosu.com>)
-- Yannick (<http://yanlu.de>)
-- Icons8 (<http://www.icons8.com>)
diff --git a/legal/index.md b/legal/index.md
index 7c6ac2f0e6d04f773eda2fd9de83e64a18bd63b6..84c1646781e2145005b0dd770b8e94aade9a84de 100644
--- a/legal/index.md
+++ b/legal/index.md
@@ -1,6 +1,6 @@
---
layout: custom
-title: Legal
+title: titles.legal
---
<div class="legal">
diff --git a/legal/privacy.md b/legal/privacy.md
deleted file mode 100644
index 1909ff1559833057c3fd73271a577312b17a56a9..0000000000000000000000000000000000000000
--- a/legal/privacy.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-layout: static_page
-title: "Privacy"
-title-pre-kick: "Privacy "
-title-kick: "Policy"
-title-post-kick: ""
-kick-class: "green-kicks"
-icon: "icon_privacy"
-attribution: ""
----
-
-### What We Collect
-
-The Monero Project uses Google Analytics to collect usage and visitor data for this website. This is enabled via a small piece of JavaScript code, and will not run if you have JavaScript disabled.
-
-We also collect standard server logs from our webserver. We do not collect cookies anywhere on the site except when using the Monero forum (located at [forum.getmonero.org](https://forum.getmonero.org)).
-
-### What We Use the Data For
-
-The Google Analytics data is used to provide statistics on the website and help us to improve the content and the information flow.
-
-Server logs are used to analyse errors and diagnose requests to dead links. A portion of the server logs are used to gather statistics on Monero downloads in order to help us better understand our user's needs.
-
-The cookies used on the Monero forum are used to identify returning users who have opted in to have their user session active for a period of time, as well as logged in users actively using the forum.
diff --git a/legal/terms.md b/legal/terms.md
deleted file mode 100644
index 0d6a55c5d284b0dada91ed32525b7b250a69c994..0000000000000000000000000000000000000000
--- a/legal/terms.md
+++ /dev/null
@@ -1,105 +0,0 @@
----
-layout: static_page
-title: "Terms of Use"
-title-pre-kick: "Terms of "
-title-kick: "Use"
-title-post-kick: ""
-kick-class: "red-kicks"
-icon: "icon_terms"
-attribution: ""
----
-
-### Terms of Use
-
-*Last revised: February 18th, 2014*
-
-This website is operated by The Monero Project, a loose collective of individuals behind Monero. By visiting and using this website you will be accepting these Terms of Use ("TOU"). Please read them carefully and if you disagree with the TOU in any way, then do not use this website. The Monero Project reserves the right to post changes to the TOU on this website at any time, and by your continuing to use the website thereafter, you agree to be bound by the new version of the TOU. If any TOU changes are not acceptable, you must stop your use of this website. In these TOU, "The Monero Project" and "we" refers to The Monero Project, and "User" or "you" refers to each visitor to this website. "Monero" refers to the digital currency that can be used by the software available on this website.
-
-#### Sites and Services
-
-We do not guarantee that access to or use of this website or any services will be uninterrupted or error free, and The Monero Project shall not be liable for any feature not being accessible or for any unavailability of its website and services. The website and its features may be expanded, limited or modified at any time by The Monero Project to meet the needs of its Users, or for technical or other reasons, without advance notice or reason. We may also in our sole discretion, and at any time, discontinue providing, temporarily or permanently, any or all of the website, without notice. To access some of the content or features of the website or its services, Users may need to enhance or update the hardware or software in their computer systems. The Monero Project assumes no responsibility for any failure to access the website or any services, partially or fully, whether due to the User's system, the Internet network or any other cause.
-
-#### Minors
-
-We do not provide information or services to minors, and if you are under 18 you may only use this site with the active involvement of a parent, guardian or other supervising adult.
-
-#### No Investment Advice
-
-This website does not provide individual or customized legal, tax, financial, or investment services. Since each individual's situation is unique, a qualified professional should be consulted before making financial decisions. Since Monero is meant to be used as a medium of exchange, nothing on this website constitutes investment advice or a solicitation to buy, hold, invest in, own, or use Monero.
-
-#### Content Limitations
-
-We make no guarantees as to the accuracy, thoroughness or quality of the information on this website, which is provided only on an "AS-IS" and "AS AVAILABLE" basis at User's sole risk. This information may be provided by third parties and The Monero Project shall not be responsible or liable for any errors, omissions or inaccuracies in the website content. The information provided at this site are neither comprehensive nor appropriate for every individual. Some of the information is relevant only in certain parts of the world, and may not be relevant to or compliant with the laws, regulations or other legal requirements of other countries. It is your responsibility to determine whether, how and to what extent your intended use of the information and services will be technically and legally possible in the areas of the world where you intend to use them. You are advised to verify any information before using it for any personal, financial or business purpose. In addition, the opinions and views expressed in any forum post on this website are solely those of the author(s) of the article and do not reflect the opinions of The Monero Project. The website content and services may be modified at any time by us, without advance notice or reason, and The Monero Project shall have no obligation to notify you of any corrections or changes to any website content.
-
-#### Proprietary Rights and License
-
-This website and its content are protected by copyright, trademark and other proprietary laws. For details please refer to our [Copyrights notice](/legal/copyright).
-
-#### Third Party Content
-
-Any testimonials, opinions, advice, product or service offers, or other information or content made available on or through this website by third parties ("Third Party Content") are solely those of their respective providers and not of The Monero Project which does not guarantee the accuracy, completeness, reliability or usefulness of Third Party Content. It is the responsibility of the User to evaluate Third Party Content and The Monero Project shall not be liable for any damage or loss caused by Users' reliance on or other use of Third Party Content.
-
-#### Materials Posted by Users
-
-By posting or submitting any material to this website, including on the forum, you will be (a) granting The Monero Project a world-wide fully paid-up non-exclusive license to allow your materials to be edited and displayed by The Monero Project on its website, and accessed by Users, for the purposes and on the terms in these TOU, (b) agreeing to indemnify and hold harmless The Monero Project and its Users from any claim or demand made by any third party due to or arising out of your materials, and (c) representing that you own or otherwise have the right to post the materials, that the materials are accurate, that use of the materials on the The Monero Project website does not violate any laws, and that the materials will not cause injury to any person. The Monero Project shall have the right to use your name in connection with your posted materials.
-
-#### Viruses and Malware
-
-The Monero Project takes many precautions to ensure the files available for downloading through this website are not tampered with, and where appropriate SHA hashes are provided for end users to confirm they have downloaded the correct file. Nonetheless, The Monero Project does not guarantee that files available for downloading through this website will be free of infection or viruses or other code that may have contaminating or destructive properties. You are responsible for implementing sufficient procedures and checkpoints to satisfy your particular requirements for integrity, security and accuracy of data input and output, and for maintaining a means external to the site for the reconstruction of any lost data. It is almost always advisable to check the SHA hashes of the files you have downloaded, and if in any doubt consider [compiling Monero from the source code](https://github.com/monero-project/bitmonero).
-
-#### Sponsors and Advertisers are Not Endorsed
-
-Though we seek to partner with quality companies, we are not responsible for the claims or representations made by sponsors and advertisers. The Monero Project does not review, endorse or recommend the products or services of any company mentioned on our site. We will not be liable in any way for damages of any kind resulting out of the misuse of any personal information or data submitted by you to an sponsor or advertiser.
-
-#### Offsite Links
-
-As a convenience to Users, the The Monero Project website and services may provide links to other sites or resources. Because we do not review or have no control over such sites and resources, The Monero Project shall not be responsible or liable for use of or reliance on any content, products, services or information at such sites or resources. Inclusion of any links does not imply any endorsement, affiliation, approval, association or sponsorship by The Monero Project of the linked websites, resources, their operators or owners. When you select a link, you may be leaving our website. The information available on Third Parties' websites may have certain restrictions on its use or distribution which differ from these TOU.
-
-#### Password Protected Areas
-
-Some areas of the The Monero Project site ("Password Protected Areas"), primarily the Monero forum, are password protected and available only to Users who are registered on the Monero forum. Registration requires Users to fully complete the account registration process. The Monero Project reserves the right to deny or revoke registration or access to Password Protected Areas for any User. The Monero Project takes reasonable measures to ensure the security of the Password Protected Areas but cannot guarantee the absolute security of information or communications in such Password Protected Areas. Users are responsible for maintaining the security of the password they set and must notify us if they believe that the security of their password or account has been breached or subject to unauthorized use. Additional account security is available through the use of GPG authentication, and all users of any Password Protected Areas are encouraged to take advantage of this layer of protection. The Monero Project will not be liable for any loss or liability incurred as a result of an unauthorized person using a User's password.
-
-#### Prohibited Conduct
-
-The following activities are strictly prohibited:
-
-- Spamming, advertising, soliciting or political campaigning
-- Personal attacks on or abuse of any members, moderators, or administrators of the forum
-- Postings for any unlawful or fraudulent purpose (including links)
-- Posting of personal information (for yourself or anyone else)
-- Phishing
-- Posting materials containing viruses or other malicious or destructive code
-- Posting of offensive content including profanity, obscenity, racist or pornographic material
-- Posting of any materials that are defamatory or infringe any person's rights
-
-#### Privacy
-
-This website may collect personal information from some Users. Because The Monero Project respects the privacy of its Users and their personal information, it has established the [Privacy Policy](/legal/privacy) to protect your personal information.
-
-#### Communications
-
-When you visit our website or send us email, our responses to your communications will be by e-mail. All agreements, notices and communications that we provide to you by email will satisfy all legal requirements that they be in writing and delivered to you. The Monero Project will have the right to disclose any email sent by a User, or any objectionable material, to comply with legal process or to protect the rights or property of The Monero Project, its customers, suppliers and Users.
-
-#### No Monero Financial Services
-
-This website does not store, sell, buy, send, or receive Monero. All activities related to the ownership and transfer of Monero currency units is done on the decentralized Monero network, of which this website is not an active participant.
-
-#### No Liability for Monero Loss
-
-The Monero Project will not be responsible for any damages, claims, or losses arising from the use of Monero, including the actions or inactions or events related to third parties, security problems during the use of any Monero-related software or service, technical failures during the use of any Monero-related software or service, software or data corruption problems during the use of any Monero-related software or service, or user errors during the use of any Monero-related software or service.
-
-#### DISCLAIMER OF WARRANTIES
-
-THE MONERO PROJECT DISCLAIMS ALL WARRANTIES, REPRESENTATIONS AND CONDITIONS OF ANY KIND, WHETHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT, WITH RESPECT TO THE USE OF THIS WEBSITE AND ITS SERVICES, OR THE ACCURACY, COMPLETENESS, TIMELINESS OR CURRENTNESS OF ITS CONTENT, IN ANY WAY AND FOR ANY PURPOSE.
-
-#### EXCLUSION OF CONSEQUENTIAL DAMAGES
-
-IN NO EVENT WILL THE MONERO PROJECT BE LIABLE FOR ANY INCIDENTAL, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY OR INDIRECT DAMAGES ARISING OUT OF THE USE OF OR INABILITY TO USE THIS WEBSITE OR ANY OF ITS SERVICES OR CONTENT, OR LOSS OF DATA, EVEN IF THE MONERO PROJECT HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, AND WHETHER BASED ON CONTRACT, TORT, NEGLIGENCE, PRODUCT LIABILITY, STRICT LIABILITY OR OTHERWISE.
-
-#### EXCLUSION OF LIMITATIONS AND DISCLAIMERS
-
-BECAUSE SOME JURISDICTIONS DO NOT ALLOW THE DISCLAIMER OF WARRANTIES, OR THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, IN SUCH JURISDICTIONS THE MONERO PROJECT'S LIABILITY IS LIMITED TO THE GREATEST EXTENT PERMITTED BY LAW.
-
-#### General
-
-These TOU, and any applicable TOS, constitute the entire agreement between each User and The Monero Project governing the User's access to and use of the website and its services, and supersede all prior agreements regarding its subject matter. The TOU shall be governed by the laws of the Republic of South Africa without giving effect to any principles of conflicts of laws. Each User hereby attorns and agrees to the non-exclusive jurisdiction of the courts of the Western Cape, South Africa. The failure by a User or The Monero Project to exercise any right or to enforce any provision of the TOU shall not constitute a waiver of such right or provision. If any provision of the TOU is found by a court of competent jurisdiction to be invalid or unenforceable, the court shall give effect to the intentions reflected in the provision to the degree possible, and the other provisions of the TOU will remain in full force and effect. It is the express will of The Monero Project and each User that the TOU and any applicable TOS have been prepared in English.
diff --git a/media/Monero - RingCT.m4v b/media/Monero - RingCT.m4v
new file mode 100644
index 0000000000000000000000000000000000000000..d174c45799ff1293623bb9afd228294692d84e87
Binary files /dev/null and b/media/Monero - RingCT.m4v differ
diff --git a/press-kit/index.md b/press-kit/index.md
index fae2cdb82c3045a814c6ea4953549c63b13ea97b..30c619cd1a49776c0aeea008618c481fca318f90 100644
--- a/press-kit/index.md
+++ b/press-kit/index.md
@@ -1,74 +1,6 @@
---
layout: custom
-title: "Monero Press Kit"
+title: titles.presskit
+permalink: /press-kit/index.html
---
-
-<div class="text-center container description">
-<p>Here you'll find the Monero symbol and logo below. You can choose any size that you want, or download the .ai file to mess with the logo yourself. <strong>Note that the white background options have a white background under the Monero symbol ONLY, not as a background to the whole image.</strong> Lastly, you can download everything on this page in one zip file by clicking <a href="/press-kit/monero-press-kit.zip">here</a>.</p>
-</div>
-<section class="container">
- <div class="row">
- <div class="left half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
- <div class="info-block">
- <div class="row center-xs">
- <div class="col">
- <h2>Monero Symbol</h2>
- </div>
- </div>
- <div class="row center-xs">
- <img src="/press-kit/symbols/monero-symbol-480.png" alt="Monero Symbol" class="symbol-logo">
- </div>
- <div class="row center-xs press">
- <div class="col-md-6">
- <p>No background (PNG)</p>
- <a href="/press-kit/symbols/monero-symbol-480.png">Small</a>
- <a href="/press-kit/symbols/monero-symbol-800.png">Medium</a>
- <a href="/press-kit/symbols/monero-symbol-1280.png">Large</a>
- </div>
- <div class="col-md-6">
- <p>White background (PNG)</p>
- <a href="/press-kit/symbols/monero-symbol-on-white-480.png">Small</a>
- <a href="/press-kit/symbols/monero-symbol-on-white-800.png">Medium</a>
- <a href="/press-kit/symbols/monero-symbol-on-white-1280.png">Large</a>
- </div>
- </div>
- <div class="row center-xs press">
- <a href="/press-kit/symbols/monero-symbol.ai" class="adi">Symbol .ai file</a>
- </div>
- </div>
- </div>
- <div class="right half col-lg-6 col-md-6 col-sm-12 col-xs-12">
- <div class="info-block">
- <div class="row center-xs">
- <div class="col">
- <h2>Monero Logo</h2>
- </div>
- </div>
- <div class="row center-xs">
- <div class="col-xs-12">
- <img src="/press-kit/logos/monero-logo-480.png" alt="Monero Logo" class="monero-symbol-logo">
- </div>
- </div>
- <div class="row center-xs press">
- <div class="col-md-6">
- <p>No background (PNG)</p>
- <a href="/press-kit/logos/monero-logo-480.png">Small</a>
- <a href="/press-kit/logos/monero-logo-800.png">Medium</a>
- <a href="/press-kit/logos/monero-logo-1280.png">Large</a>
- </div>
- <div class="col-md-6">
- <p>White background (PNG)</p>
- <a href="/press-kit/logos/monero-logo-symbol-on-white-480.png">Small</a>
- <a href="/press-kit/logos/monero-logo-symbol-on-white-800.png">Medium</a>
- <a href="/press-kit/logos/monero-logo-symbol-on-white-1280.png">Large</a>
- </div>
- </div>
- <div class="row center-xs press">
- <div class="col-xs-12">
- <a href="/press-kit/logos/monero-logo.ai" class="adi">Logo .ai file</a>
- </div>
- </div>
- </div>
- </div>
- </div>
-</section>
\ No newline at end of file
+{% tf press-kit.md %}
\ No newline at end of file
diff --git a/resources/about.md b/resources/about.md
deleted file mode 100644
index e800f5b8522e436ecaed43e9672c296980703d71..0000000000000000000000000000000000000000
--- a/resources/about.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-layout: static_page
-title: "About Monero"
-title-pre-kick: "About "
-title-kick: "Monero"
-title-post-kick: ""
-kick-class: "kicks"
-icon: "icon_about"
-attribution: "<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->"
----
-
-<iframe width="560" height="315" src="https://www.youtube.com/embed/TZi9xx6aiuY" frameborder="0" allowfullscreen></iframe>
-<!-- Source code for this video can be found at https://github.com/savandra/Monero_Promo_Video/blob/master/README.md -->
-
-## About Monero
-
-To most people, financial privacy is very important. Yet in recent years, we have seen a staggering amount of big corporations, banks and governments have their records compromised, each time leaking information about their users, their practices, and their balance sheets. The unfortunate but undeniable conclusion is that there is no safe place to conduct private transactions.
-There *was* no safe place to conduct private transactions. Monero provides a place where your financial activities are private. Monero is one of the leading cryptocurrencies in the post-Bitcoin world, and it is built on principles of privacy, decentralization, and scalability.
-From an economic point of view, a currency needs to be fungible. Fungibility is a property of money that makes all units "equal." Without fungibility, money flows can be tracked and tainted, making it very difficult to use the digital tokens as money.
-
-Monero is a secure, private, untraceable currency. It is open source, freely available to all, and was fairly launched on April 18th, 2014, without premine or instamine.
-The technology behind Monero has already spiked the interest of several established people in the Bitcoin development world and the cryptography community.
-Monero development is completely donation-based and community-driven, with a strong focus on decentralization and scalability.
-With Monero, you are your own bank. Only you control and are responsible for your funds, and your accounts and transactions are kept private from prying eyes.
-
-Read on to find out how Monero is helping to solve real problems and limitations of existing cryptocurrencies, and building a more private blockchain.
-
-## PRIVACY
-
-Monero seeks to provide absolute transactional privacy in an effort to create true electronic cash. With Bitcoin, as well as with the vast majority of cryptocurrencies that have been established since, any and all transactions are entirely traceable. Any casual observer can read through the Bitcoin blockchain, and for any transaction, this observer can find out the exact amount that was transacted, as well as the precise transaction origin (sender address) and destination (recipient address).
-
-With Monero, for any private transaction, the same observer has no means to uncover the origin, destination, or amount transacted. As such, transactions on the Monero blockchain, are private and fundamentally untraceable.
-But Monero is more than a currency. Driving the official slogan - “secure, private, untraceable†- are a multitude of applications where the parties involved wish to remain private. The Monero blockchain can keep confidential contracts confidential. Since the forthcoming, blockchain-powered internet of things will place the cloud all around us, it is then increasingly important that open access tools like Monero exist to provide a secure boundary for private settlements.
-
-An often overlooked, but nonetheless important layer of privacy in a connected world, is that of the networking infrastructure. We have teamed up with Privacy Solutions, and development is well underway to incorporate an i2p router in Monero. In a world where ill-intentioned governments and ISPs can void an individual’s basic privacy rights on a whim, it then becomes necessary to establish a private communication platform.
-
-The underlying technologies and cryptography upon which Monero is built, has been (and continues to be) the subject of extensive analysis and review by numerous individuals and research groups. It has garnered favorable attention by some of the most prominent figures of the Bitcoin and cryptography world, such as Andrew Poelstra (andytoshi), Gregory Maxwell, and Nicolas Courtois.
-
-With Monero, transactions are private by default. However, each user has the ability to select different levels of privacy, optionally disclosing their transaction information, or even provide audit access (view only) to their full Monero account.
-
-## DECENTRALIZATION
-While most cryptocurrencies align to theoretical principles of decentralization, the reality is that most fall short of such a claim. More often than not, it is not just one branch of a cryptocurrency system that is centralized in one form or another, it is that many branches are so.
-
-With Proof of Stake currencies, irregular emission and distribution models cause most of the staking power to end up in the hands of a privileged few. Participants of lesser weight are reduced to second class citizens, with little chance of ever obtaining similar returns.
-
-With Proof of Work currencies, of which Bitcoin remains the most significant reference, the mining process is largely concentrated in a handful of pools. This centralization of mining power, combined with a transparent blockchain, has already lead to various occurrences of transaction censorship.
-
-Other currencies opt for a closed development model, thus centralizing the invention process itself. These closed platforms commonly fail to meet any form of public audit or expert review. More importantly, these are platforms that will at anytime swing left and right, in order to satisfy the interests of the restricted group that holds control of development.
-
-Monero contrasts with these examples in various and meaningful ways. Monero is powered strictly by Proof of Work, but specifically, it employs a mining algorithm that has the potential to be efficiently tasked to billions of existing devices (any modern x86 CPU).
-This very characteristic, and more so once it is coupled with @Smart Mining, has the potential to ensure that for long years to come, the process of mining new Monero coins is within reach of the common individual, not an exclusive opportunity to the owners of large mining operations.
-
-Furthermore, as transactions are private by default on the Monero blockchain, transaction censorship is inherently void.
-The Monero development landscape, on the other hand, is very much the opposite of a closed or restricted access model. The core branch currently enjoys more than 30 contributors, pushing 1000+ commits over the past year. The project is happy to take on new contributors and any future plans, long-term direction and priorities are openly discussed with the community. Indeed, the policy that governs contribution to the Monero codebase is exhaustingly inclusive - all contributions are accepted into the development branch, where new code can be scrutinized and tested by the entire community.
-
-Most contributors in the Monero development landscape are quite passionate for an open source philosophy, and in this rich creative environment, new projects have sparked to life. @OpenAlias is one notable example, which has seen adoption by (amongst others) a major Bitcoin-related software product.
-
-## SCALEABILITY
-One of the problems with cryptocurrencies is scaleability. Most cryptocurrencies are derived from the Bitcoin codebase and thus have a "block size limit." This limit has become a big issue in the Bitcoin community and led to fierce discussions.
-Monero doesn't suffer from this block size debate, because it has a dynamic block size limit. This limit is automatically recalculated regularly based on a look-back window. A penalty system prevents out of control growth of the block size.
-Another issue with most cryptocurrencies is the development of a fee market. This issue is somewhat linked to the block size debate: the narrative is that when you limit the block size, a fee market will eventually develop. But this claim is highly debatable. When the transaction fees are supposed to be the main incentive for miners to secure the blockchain, it is possible the current consensus model will not be sustainable. At the moment, miners still act as they are expected: they mine on the longest chain. When they don't do that, they risk losing the block reward. But when that block reward becomes small compared to the mining fees, it's possible miners will have an incentive to not mine on the longest chain and start a fork trying to "steal" high transaction fees which were included in the latest blocks. Therefore, Monero implements a "permanent block reward." The block reward will never drop below 0.3 XMR, making Monero a disinflationary currency: the inflation will be roughly 1% in 2022 and go down forever, but the nominal inflation will stay at 0.3 XMR per minute. This means that there will always be an incentive for miners to mine Monero and thus keeping the blockchain secure, with or without a fee market.
-
-## FUNGIBILITY
-Fungibility is an important property of any functioning currency. You can try to hide your bitcoins as much as you want, if you tried to mix your non-fungible coins using a mixer, coinjoin or another type of "anonymity enhancing feature," these transactions can still be flagged as "possible suspicious activity on the blockchain," even if you are anonymous. Using non-fungible tokens as currency can eventually lead to blacklisting/whitelisting either by governments or through self-censorship. Some examples of these measures could be payment processors or exchanges refusing your tainted coins as a payment or deposit or miners refusing to include your suspicious transaction.
-On the other hand, Monero transaction outputs have "plausible deniability" about their state: you can't tell if they are spent or unspent in a certain transaction or not. This leads to an opaque (non-transparent) blockchain making all coins "equal." @Fungibility is built into Monero at protocol level, making it real "digital cash."
diff --git a/resources/about/index.md b/resources/about/index.md
index 125e13addd00a71f3124116833f242cc2a929615..84ae5ccb7cd407b34f01349018a58aa72b43e356 100644
--- a/resources/about/index.md
+++ b/resources/about/index.md
@@ -1,61 +1,7 @@
---
layout: custom
-title: "About Monero"
+title: titles.about
+permalink: /resources/about/index.html
---
-<div class="about-monero">
- <section class="container">
- <div class="row">
- <!-- left two-thirds block-->
- <div class="full col-xs-12">
- <div class="info-block text-adapt">
- <div class="row center-xs">
- <div class="col">
- <h2>A Brief History</h2>
- </div>
- </div>
-<div markdown="1">
-
-Monero was launched in April 2014. It was a fair, pre-announced launch of the CryptoNote reference code. There was no premine or instantmine, and no portion of the block reward goes to development. See the original Bitcointalk thread here. The founder, thankful_for_today, proposed some controversial changes that the community disagreed with. A fallout ensued, and the Monero Core Team forked the project with the community following this new Core Team. This Core Team has provided oversight since.
-
-Monero has made several large improvements since launch. The blockchain was migrated to a different database structure to provide greater efficiency and flexibility, minimum ring signature sizes were set so that all transactions were private by mandate, and RingCT was implemented to hide the transaction amounts. Nearly all improvements have provided improvements to security or privacy, or they have facilitated use. Monero continues to develop with goals of privacy and security first, ease of use and efficiency second.
-
-</div>
- </div>
- </div>
- <!-- end right one-third block-->
- </div>
- <div class="row">
- <!-- left two-thirds block-->
- <div class="full col-xs-12">
- <div class="info-block text-adapt">
- <div class="row center-xs">
- <div class="col">
- <h2>Our Values</h2>
- </div>
- </div>
-
-<div markdown="1">
-
-Monero is more than just a technology. It’s also what the technology stands for. Some of the important guiding philosophies are listed below.
-
-### Security
-
-Users must be able to trust Monero with their transactions, without risk of error or attack. Monero gives the full block reward to the miners, who are the most critical members of the network who provide this security. Transactions are cryptographically secure using the latest and most resilient encryption tools available.
-
-### Privacy
-
-Monero takes privacy seriously. Monero needs to be able to protect users in a court of law and, in extreme cases, from the death penalty. This level of privacy must be completely accessible to all users, whether they are technologically competent or have no idea how Monero works. A user needs to confidently trust Monero in a way that this person does not feel pressured into changing their spending habits for risk of others finding out.
-
-### Decentralization
-
-Monero is committed to providing the maximum amount of decentralization. With Monero, you do not have to trust anyone else on the network, and it is not run by any large group. An accessible “Proof of Work†algorithm makes it easy to mine Monero on normal computers, which makes it more difficult for someone to purchase a large amount of mining power. Nodes connect to each other with I2P to lower the risks of revealing sensitive transaction information and censorship (tba). Development decisions are extremely clear and open to public discussion. Developer meeting logs are published online in their entirety and visible by all.
-
-</div>
- </div>
- </div>
-
-
- <!-- end right one-third block-->
- </div>
- </section>
\ No newline at end of file
+{% tf resources/about.md %}
\ No newline at end of file
diff --git a/resources/about2.md b/resources/about2.md
deleted file mode 100644
index a85c5e3598b7e8b77a452f185533831aee326d23..0000000000000000000000000000000000000000
--- a/resources/about2.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-layout: static_page
-title: "About Monero"
-title-pre-kick: "About "
-title-kick: "Monero"
-title-post-kick: ""
-kick-class: "kicks"
-icon: "icon_about"
-attribution: "<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->"
----
-## About Monero
-
-To most people, financial privacy is very important. Yet in recent years, we have seen a staggering amount of big corporations, banks and governments having their records compromised, at every time leaking information about their users, their practices, their balance sheets. The unfortunate but undeniable conclusion is that there is no safe place to conduct private transactions.
-There was no safe place to conduct private transactions. Monero provides a place where your financial activities are private.
-Monero is one of the leading cryptocurrencies in the post-Bitcoin world, and it is built on principles of privacy, decentralization, and scalability.
-Read on to find out how Monero is helping to solve real problems and limitations of existing cryptocurrencies, and building a more private blockchain.
-
-## PRIVACY
-
-Monero seeks to provide absolute transactional privacy in an effort to create true electronic cash.
-With Bitcoin, as well as with the vast majority of cryptocurrencies that have been established since, any and all transactions are entirely traceable. Any casual observer can read through the Bitcoin blockchain, and for any transaction, this observer can find out the exact amount that was transacted, as well as the precise transaction origin (sender address) and destination (recipient address).
-With Monero, for any private transaction[1], the same observer has no means to uncover the origin, destination, or amount transacted. As such, transactions on the Monero blockchain, are private and fundamentally untraceable.
-But Monero is more than a currency. Driving the official slogan: “secure, private, untraceableâ€, there are a multitude of applications where the parties involved wish to remain private. The Monero blockchain can keep confidential contracts, well… confidential. While the forthcoming, blockchain-powered internet of things will certainly place the cloud all around us, it is then increasingly important that open access tools exist to provide a secure boundary for private settlements.
-An often overlooked, but nonetheless important layer of privacy in a connected world, is that of the networking infrastructure. We have teamed up with Privacy Solutions, and development is well underway to incorporate an i2p router in Monero. In a world where ill intentioned governments and ISPs can void an individual’s basic privacy rights on a whim, it then becomes necessary to establish a private communication platform.
-The underlying technologies and cryptography upon which Monero is built, has been (and continues to be) the subject of extensive analysis and review by numerous individuals and research groups. It has garnered favorable attention by some of the most prominent figures of the Bitcoin & cryptography world, such as Andrew Poelstra (andytoshi), Gregory Maxwell & Nicolas Courtois.
-[1] With Monero, transactions are private by default. However, each user has the ability to select different levels of privacy, optionally exposing the amount of a given (own) transaction, or even provide audit access (view only) to his full Monero account.
-
-## DECENTRALIZATION
-While most cryptocurrencies align to theoretical principles of decentralization, the reality is, that most fall short of such a claim. More often than not, it is not just one branch of a cryptocurrency system that is centralized in one form or another, is that that many branches are so.
-With Proof of Stake currencies, irregular emission and distribution models cause most of the staking power to end up in the hand of a privileged few. Participants of lesser weight are reduced to second class citizens, with little chance of ever obtaining similar returns.
-With Proof of Work currencies, of which Bitcoin remains the most significant reference, the mining process is largely concentrated in a handful of pools. This centralization of mining power, combined with a transparent blockchain, has already lead to various occurrences of transaction censorship.
-Other currencies opt for a closed development model, thus centralizing the invention process itself. These closed platforms commonly fail to meet any form of public audit or expert review. More importantly, these are platforms that will anytime swing left and right, in order to satisfy the interests of the restricted group that holds control of development.
-Monero contrasts with these examples in various and meaningful ways.
-Monero is powered strictly by Proof of Work, but specifically, it employs a mining algorithm that has the potential to be efficiently tasked to billions of existing devices (any modern x86 CPU).
-This very characteristic, and more so once it is coupled with Smart Mining[2], has the potential to ensure that for long years to come, the process of mining new Monero coins is within reach of the common individual, and not an exclusive opportunity to the owners of large mining operations.
-Further, as transactions are private by default on the Monero blockchain, transaction censorship is inherently void.
-The Monero development landscape on the other hand, is very much the opposite of a closed or restricted access model. The core branch currently enjoys more than 30 contributors, pushing 1000+ commits over the past year {there has to be better stats to put in there}. The project is happy to take on new contributors and any future plans, long term direction and priorities are openly discussed with the community. Indeed, the policy that governs contribution to the Monero codebase is exhaustingly inclusive - all contributions are accepted into the development branch, where new code can be scrutinized and tested by the entire community.
-Most contributors in the Monero development landscape are quite passionate for an open source philosophy, and in this rich creative environment, new projects have sparked to life. OpenAlias[3] is one notable example, which has seen adoption by (amongst others) a major Bitcoin related software product.
-
-[2] {Insert a neat description of Smart Mining here.}
-[3] {Insert a neat description of Open Alias here.}
\ No newline at end of file
diff --git a/resources/developer-guides/daemon-rpc.md b/resources/developer-guides/daemon-rpc.md
index 31d16a6d15368c9e957ff6575494f44a1e00fef7..8584f3e0978d83a7bef7dc5cf099ea06a3b1ec20 100644
--- a/resources/developer-guides/daemon-rpc.md
+++ b/resources/developer-guides/daemon-rpc.md
@@ -1,832 +1,7 @@
---
-layout: static_page
+layout: user-guide
title: "Daemon RPC documentation"
-title-pre-kick: "Developer Guide: "
-title-kick: "Daemon RPC documentation "
-title-post-kick: ""
-kick-class: "green-kicks"
-icon: "icon_client"
-attribution: "<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->"
+permalink: /resources/developer-guides/daemon-rpc.html
---
-## Introduction
-
-This is a list of the monerod daemon RPC calls, their inputs and outputs, and examples of each.
-
-Many RPC calls use the daemon's JSON RPC interface while others use their own interfaces, as demonstrated below.
-
-Note: "atomic units" refer to the smallest fraction of 1 XMR according to the monerod implementation. **1 XMR = 1e12 atomic units.**
-
-### [JSON RPC Methods](#json-rpc-methods):
-
-* [getblockcount](#getblockcount)
-* [on_getblockhash](#on_getblockhash)
-* [getblocktemplate](#getblocktemplate)
-* [submitblock](#submitblock)
-* [getlastblockheader](#getlastblockheader)
-* [getblockheaderbyhash](#getblockheaderbyhash)
-* [getblockheaderbyheight](#getblockheaderbyheight)
-* [getblock](#getblock)
-* [get_connections](#get_connections)
-* [get_info](#get_info)
-* [hard_fork_info](#hard_fork_info)
-* [setbans](#setbans)
-* [getbans](#getbans)
-
-### [Other RPC Methods](#other-daemon-rpc-calls):
-
-* [/getheight](#getheight)
-* [/gettransactions](#gettransactions)
-* [/is_key_image_spent](#is_key_image_spent)
-* [/sendrawtransaction](#sendrawtransaction)
-* [/get_transaction_pool](#get_transaction_pool)
-* [/stop_daemon](#stop_daemon)
-
-
----
-
-## JSON RPC Methods
-
-The majority of monerod RPC calls use the daemon's `json_rpc` interface to request various bits of information. These methods all follow a similar structure, for example:
-
-```
-IP=127.0.0.1
-PORT=18081
-METHOD='getblockheaderbyheight'
-PARAMS='{"height":912345}'
-curl \
- -X POST http://$IP:$PORT/json_rpc \
- -d '{"jsonrpc":"2.0","id":"0","method":"'$METHOD'","params":'$PARAMS'}' \
- -H 'Content-Type: application/json'
-```
-
-Some methods include parameters, while others do not. Examples of each JSON RPC method follow.
-
-### **getblockcount**
-
-Look up how many blocks are in the longest chain known to the node.
-
-Inputs: *None*.
-
-Outputs:
-
-* *count* - unsigned int; Number of blocks in longest chain seen by the node.
-* *status* - string; General RPC error code. "OK" means everything looks good.
-
-Example:
-
-```
-$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getblockcount"}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- "count": 993163,
- "status": "OK"
- }
-}
-```
-
-
-### **on_getblockhash**
-
-Look up a block's hash by its height.
-
-Inputs:
-
-* block height (int array of length 1)
-
-Outputs:
-
-* block hash (string)
-
-Example:
-
-```
-$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"on_getblockhash","params":[912345]}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": "e22cf75f39ae720e8b71b3d120a5ac03f0db50bba6379e2850975b4859190bc6"
-}
-```
-
-
-### **getblocktemplate**
-
-Inputs:
-
-* *wallet_address* - string; Address of wallet to receive coinbase transactions if block is successfully mined.
-* *reserve_size* - unsigned int; Reserve size.
-
-Outputs:
-
-* *blocktemplate_blob* - string; Blob on which to try to mine a new block.
-* *difficulty* - unsigned int; Difficulty of next block.
-* *height* - unsigned int; Height on which to mine.
-* *prev_hash* - string; Hash of the most recent block on which to mine the next block.
-* *reserved_offset* - unsigned int; Reserved offset.
-* *status* - string; General RPC error code. "OK" means everything looks good.
-
-Example:
-
-```
-$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getblocktemplate","params":{"wallet_address":"44GBHzv6ZyQdJkjqZje6KLZ3xSyN1hBSFAnLP6EAqJtCRVzMzZmeXTC2AHKDS9aEDTRKmo6a6o9r9j86pYfhCWDkKjbtcns","reserve_size":60}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- "blocktemplate_blob": "01029af88cb70568b84a11dc9406ace9e635918ca03b008f7728b9726b327c1b482a98d81ed83000000000018bd03c01ffcfcf3c0493d7cec7020278dfc296544f139394e5e045fcda1ba2cca5b69b39c9ddc90b7e0de859fdebdc80e8eda1ba01029c5d518ce3cc4de26364059eadc8220a3f52edabdaf025a9bff4eec8b6b50e3d8080dd9da417021e642d07a8c33fbe497054cfea9c760ab4068d31532ff0fbb543a7856a9b78ee80c0f9decfae01023ef3a7182cb0c260732e7828606052a0645d3686d7a03ce3da091dbb2b75e5955f01ad2af83bce0d823bf3dbbed01ab219250eb36098c62cbb6aa2976936848bae53023c00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001f12d7c87346d6b84e17680082d9b4a1d84e36dd01bd2c7f3b3893478a8d88fb3",
- "difficulty": 982540729,
- "height": 993231,
- "prev_hash": "68b84a11dc9406ace9e635918ca03b008f7728b9726b327c1b482a98d81ed830",
- "reserved_offset": 246,
- "status": "OK"
- }
-}
-```
-
-
-### **submitblock**
-
-Submit a mined block to the network.
-
-Inputs:
-
-* Block blob data - string
-
-Outputs:
-
-* *status* - string; Block submit status.
-
-
-### **getlastblockheader**
-
-Block header information for the most recent block is easily retrieved with this method. No inputs are needed.
-
-Inputs: *None*.
-
-Outputs:
-
-* *block_header* - A structure containing block header information.
- * *depth* - unsigned int; The number of blocks succeeding this block on the blockchain. A larger number means an older block.
- * *difficulty* - unsigned int; The strength of the Monero network based on mining power.
- * *hash* - string; The hash of this block.
- * *height* - unsigned int; The number of blocks preceding this block on the blockchain.
- * *major_version* - unsigned int; The major version of the monero protocol at this block height.
- * *minor_version* - unsigned int; The minor version of the monero protocol at this block height.
- * *nonce* - unsigned int; a cryptographic random one-time number used in mining a Monero block.
- * *orphan_status* - boolean; Usually `false`. If `true`, this block is not part of the longest chain.
- * *prev_hash* - string; The hash of the block immediately preceding this block in the chain.
- * *reward* - unsigned int; The amount of new atomic units generated in this block and rewarded to the miner. Note: 1 XMR = 1e12 atomic units.
- * *timestamp* - unsigned int; The time the block was recorded into the blockchain.
-* *status* - string; General RPC error code. "OK" means everything looks good.
-
-In this example, the most recent block (990793 at the time) is returned:
-
-```
-$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getlastblockheader"}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- "block_header": {
- "depth": 0,
- "difficulty": 746963928,
- "hash": "ac0f1e226268d45c99a16202fdcb730d8f7b36ea5e5b4a565b1ba1a8fc252eb0",
- "height": 990793,
- "major_version": 1,
- "minor_version": 1,
- "nonce": 1550,
- "orphan_status": false,
- "prev_hash": "386575e3b0b004ed8d458dbd31bff0fe37b280339937f971e06df33f8589b75c",
- "reward": 6856609225169,
- "timestamp": 1457589942
- },
- "status": "OK"
- }
-}
-```
-
-
-### **getblockheaderbyhash**
-
-Block header information can be retrieved using either a block's hash or height. This method includes a block's hash as an input parameter to retrieve basic information about the block.
-
-Inputs:
-
-* *hash* - string; The block's sha256 hash.
-
-Outputs:
-
-* *block_header* - A structure containing block header information. See [getlastblockheader](#getlastblockheader).
-
-In this example, block 912345 is looked up by its hash:
-
-```
-$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getblockheaderbyhash","params":{"hash":"e22cf75f39ae720e8b71b3d120a5ac03f0db50bba6379e2850975b4859190bc6"}}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- "block_header": {
- "depth": 78376,
- "difficulty": 815625611,
- "hash": "e22cf75f39ae720e8b71b3d120a5ac03f0db50bba6379e2850975b4859190bc6",
- "height": 912345,
- "major_version": 1,
- "minor_version": 2,
- "nonce": 1646,
- "orphan_status": false,
- "prev_hash": "b61c58b2e0be53fad5ef9d9731a55e8a81d972b8d90ed07c04fd37ca6403ff78",
- "reward": 7388968946286,
- "timestamp": 1452793716
- },
- "status": "OK"
- }
-}
-```
-
-
-### **getblockheaderbyheight**
-
-Similar to `getblockheaderbyhash` above, this method includes a block's height as an input parameter to retrieve basic information about the block.
-
-Inputs:
-
-* *height* - unsigned int; The block's height.
-
-Outputs:
-
-* *block_header* - A structure containing block header information. See [getlastblockheader](#getlastblockheader).
-
-In this example, block 912345 is looked up by its height (notice that the returned information is the save as in the previous example):
-
-```
-$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getblockheaderbyheight","params":{"height":912345}}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- "block_header": {
- "depth": 78376,
- "difficulty": 815625611,
- "hash": "e22cf75f39ae720e8b71b3d120a5ac03f0db50bba6379e2850975b4859190bc6",
- "height": 912345,
- "major_version": 1,
- "minor_version": 2,
- "nonce": 1646,
- "orphan_status": false,
- "prev_hash": "b61c58b2e0be53fad5ef9d9731a55e8a81d972b8d90ed07c04fd37ca6403ff78",
- "reward": 7388968946286,
- "timestamp": 1452793716
- },
- "status": "OK"
- }
-}
-```
-
-
-### **getblock**
-
-Full block information can be retrieved by either block height or hash, like with the above block header calls. For full block information, both lookups use the same method, but with different input parameters.
-
-Inputs (pick one of the following):
-
-* *height* - unsigned int; The block's height.
-* *hash* - string; The block's hash.
-
-Outputs:
-
-* *blob* - string; Hexadecimal blob of block information.
-* *block_header* - A structure containing block header information. See [getlastblockheader](#getlastblockheader).
-* *json* - json string; JSON formatted block details:
- * *major_version* - Same as in block header.
- * *minor_version* - Same as in block header.
- * *timestamp* - Same as in block header.
- * *prev_id* - Same as `prev_hash` in block header.
- * *nonce* - Same as in block header.
- * *miner_tx* - Miner transaction information
- * *version* - Transaction version number.
- * *unlock_time* - The block height when the coinbase transaction becomes spendable.
- * *vin* - List of transaction inputs:
- * *gen* - Miner txs are coinbase txs, or "gen".
- * *height* - This block height, a.k.a. when the coinbase is generated.
- * *vout* - List of transaction outputs. Each output contains:
- * *amount* - The amount of the output, in atomic units.
- * *target* -
- * *key* -
- * *extra* - Usually called the "transaction ID" but can be used to include any random 32 byte/64 character hex string.
- * *signatures* - Contain signatures of tx signers. Coinbased txs do not have signatures.
- * *tx_hashes* - List of hashes of non-coinbase transactions in the block. If there are no other transactions, this will be an empty list.
-* *status* - string; General RPC error code. "OK" means everything looks good.
-
-**Look up by height:**
-
-In the following example, block 912345 is looked up by its height. Note that block 912345 does not have any non-coinbase transactions. (See the next example for a block with extra transactions):
-
-```
-$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getblock","params":{"height":912345}}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- "blob": "...",
- "block_header": {
- "depth": 80694,
- "difficulty": 815625611,
- "hash": "e22cf75f39ae720e8b71b3d120a5ac03f0db50bba6379e2850975b4859190bc6",
- "height": 912345,
- "major_version": 1,
- "minor_version": 2,
- "nonce": 1646,
- "orphan_status": false,
- "prev_hash": "b61c58b2e0be53fad5ef9d9731a55e8a81d972b8d90ed07c04fd37ca6403ff78",
- "reward": 7388968946286,
- "timestamp": 1452793716
- },
- "json": "{\n \"major_version\": 1, \n \"minor_version\": 2, \n \"timestamp\": 1452793716, \n \"prev_id\": \"b61c58b2e0be53fad5ef9d9731a55e8a81d972b8d90ed07c04fd37ca6403ff78\", \n \"nonce\": 1646, \n \"miner_tx\": {\n \"version\": 1, \n \"unlock_time\": 912405, \n \"vin\": [ {\n \"gen\": {\n \"height\": 912345\n }\n }\n ], \n \"vout\": [ {\n \"amount\": 8968946286, \n \"target\": {\n \"key\": \"378b043c1724c92c69d923d266fe86477d3a5ddd21145062e148c64c57677008\"\n }\n }, {\n \"amount\": 80000000000, \n \"target\": {\n \"key\": \"73733cbd6e6218bda671596462a4b062f95cfe5e1dbb5b990dacb30e827d02f2\"\n }\n }, {\n \"amount\": 300000000000, \n \"target\": {\n \"key\": \"47a5dab669770da69a860acde21616a119818e1a489bb3c4b1b6b3c50547bc0c\"\n }\n }, {\n \"amount\": 7000000000000, \n \"target\": {\n \"key\": \"1f7e4762b8b755e3e3c72b8610cc87b9bc25d1f0a87c0c816ebb952e4f8aff3d\"\n }\n }\n ], \n \"extra\": [ 1, 253, 10, 119, 137, 87, 244, 243, 16, 58, 131, 138, 253, 164, 136, 195, 205, 173, 242, 105, 123, 61, 52, 173, 113, 35, 66, 130, 178, 250, 217, 16, 14, 2, 8, 0, 0, 0, 11, 223, 194, 193, 108\n ], \n \"signatures\": [ ]\n }, \n \"tx_hashes\": [ ]\n}",
- "status": "OK"
- }
-}
-```
-
-**Look up by hash:**
-
-In the following example, block 993056 is looked up by its hash. Note that block 993056 has 3 non-coinbase transactions:
-
-```
-$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getblock","params":{"hash":"510ee3c4e14330a7b96e883c323a60ebd1b5556ac1262d0bc03c24a3b785516f"}}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- "blob": "...",
- "block_header": {
- "depth": 12,
- "difficulty": 964985344,
- "hash": "510ee3c4e14330a7b96e883c323a60ebd1b5556ac1262d0bc03c24a3b785516f",
- "height": 993056,
- "major_version": 1,
- "minor_version": 2,
- "nonce": 2036,
- "orphan_status": false,
- "prev_hash": "0ea4af6547c05c965afc8df6d31509ff3105dc7ae6b10172521d77e09711fd6d",
- "reward": 6932043647005,
- "timestamp": 1457720227
- },
- "json": "{\n \"major_version\": 1, \n \"minor_version\": 2, \n \"timestamp\": 1457720227, \n \"prev_id\": \"0ea4af6547c05c965afc8df6d31509ff3105dc7ae6b10172521d77e09711fd6d\", \n \"nonce\": 2036, \n \"miner_tx\": {\n \"version\": 1, \n \"unlock_time\": 993116, \n \"vin\": [ {\n \"gen\": {\n \"height\": 993056\n }\n }\n ], \n \"vout\": [ {\n \"amount\": 2043647005, \n \"target\": {\n \"key\": \"59e9d685b3484886bc7b47c133e6099ecdf212d5eaa16ce19cd58e8c3c1e590a\"\n }\n }, {\n \"amount\": 30000000000, \n \"target\": {\n \"key\": \"4c5e2f542d25513c46b9e3b7d40140a22d0ae5314bfcae492ad9f56fff8185f0\"\n }\n }, {\n \"amount\": 900000000000, \n \"target\": {\n \"key\": \"13dd8ffdac9e6a2f71e327dad65328198dc879a492d145eae72677c0703a3515\"\n }\n }, {\n \"amount\": 6000000000000, \n \"target\": {\n \"key\": \"62bda00341681dccbc066757862da593734395745bdfe1fdc89b5948c86a5d4c\"\n }\n }\n ], \n \"extra\": [ 1, 182, 145, 133, 28, 240, 87, 185, 195, 2, 163, 219, 202, 135, 158, 28, 186, 76, 196, 80, 97, 202, 85, 170, 166, 224, 60, 220, 103, 171, 158, 69, 80, 2, 8, 0, 0, 0, 12, 97, 127, 223, 22\n ], \n \"signatures\": [ ]\n }, \n \"tx_hashes\": [ \"79c6b9f00db027bde151705aafe85c495883aae2597d5cb8e1adb2e0f3ae1d07\", \"d715db73331abc3ec588ef07c7bb195786a4724b08dff431b51ffa32a4ce899b\", \"b197066426c0ed89f0b431fe171f7fd62bc95dd29943daa7cf3585cf1fdfc99d\"\n ]\n}",
- "status": "OK",
- "tx_hashes": ["79c6b9f00db027bde151705aafe85c495883aae2597d5cb8e1adb2e0f3ae1d07","d715db73331abc3ec588ef07c7bb195786a4724b08dff431b51ffa32a4ce899b","b197066426c0ed89f0b431fe171f7fd62bc95dd29943daa7cf3585cf1fdfc99d"]
- }
-}
-```
-
-
-### **get_connections**
-
-Retrieve information about incoming and outgoing connections to your node.
-
-Inputs: *None*.
-
-Outputs:
-
-* *connections* - List of all connections and their info:
- * *avg_download* - unsigned int; Average bytes of data downloaded by node.
- * *avg_upload* - unsigned int; Average bytes of data uploaded by node.
- * *current_download* - unsigned int; Current bytes downloaded by node.
- * *current_upload* - unsigned int; Current bytes uploaded by node.
- * *incoming* - boolean; Is the node getting information from your node?
- * *ip* - string; The node's IP address.
- * *live_time* - unsigned int
- * *local_ip* - boolean
- * *localhost* - boolean
- * *peer_id* - string; The node's ID on the network.
- * *port* - stringl The port that the node is using to connect to the network.
- * *recv_count* - unsigned int
- * *recv_idle_time* - unsigned int
- * *send_count* - unsigned int
- * *send_idle_time* - unsigned int
- * *state* - string
-
-Following is an example of `get_connections` and it's return:
-
-```
-$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_connections"}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- "connections": [{
- "avg_download": 0,
- "avg_upload": 0,
- "current_download": 0,
- "current_upload": 0,
- "incoming": false,
- "ip": "76.173.170.133",
- "live_time": 1865,
- "local_ip": false,
- "localhost": false,
- "peer_id": "3bfe29d6b1aa7c4c",
- "port": "18080",
- "recv_count": 116396,
- "recv_idle_time": 23,
- "send_count": 176893,
- "send_idle_time": 1457726610,
- "state": "state_normal"
- },{
- ...
- }],
- "status": "OK"
- }
-}
-```
-
-
-### **get_info**
-
-Retrieve general information about the state of your node and the network.
-
-Inputs: *None*.
-
-Outputs:
-
-* *alt_blocks_count* - unsigned int; Number of alternative blocks to main chain.
-* *difficulty* - unsigned int; Network difficulty (analogous to the strength of the network)
-* *grey_peerlist_size* - unsigned int; Grey Peerlist Size
-* *height* - unsigned int; Current length of longest chain known to daemon.
-* *incoming_connections_count* - unsigned int; Number of peers connected to and pulling from your node.
-* *outgoing_connections_count* - unsigned int; Number of peers that you are connected to and getting information from.
-* *status* - string; General RPC error code. "OK" means everything looks good.
-* *target* - unsigned int; Current target for next proof of work.
-* *target_height* - unsigned int; The height of the next block in the chain.
-* *testnet* - boolean; States if the node is on the testnet (true) or mainnet (false).
-* *top_block_hash* - string; Hash of the highest block in the chain.
-* *tx_count* - unsigned int; Total number of non-coinbase transaction in the chain.
-* *tx_pool_siz* - unsigned int; Number of transactions that have been broadcast but not included in a block.
-* *white_peerlist_size* - unsigned int; White Peerlist Size
-
-Following is an example `get_info` call and its return:
-
-```
-$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_info"}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- "alt_blocks_count": 5,
- "difficulty": 972165250,
- "grey_peerlist_size": 2280,
- "height": 993145,
- "incoming_connections_count": 0,
- "outgoing_connections_count": 8,
- "status": "OK",
- "target": 60,
- "target_height": 993137,
- "testnet": false,
- "top_block_hash": "",
- "tx_count": 564287,
- "tx_pool_size": 45,
- "white_peerlist_size": 529
- }
-}
-```
-
-
-### **hard_fork_info**
-
-Look up information regarding hard fork voting and readiness.
-
-Inputs: *None*.
-
-Outputs:
-
-* *earliest_height* - unsigned int; Block height at which hard fork would be enabled if voted in.
-* *enabled* - boolean; Tells if hard fork is enforced.
-* *state* - unsigned int; Current hard fork state: 0 (There is likely a hard fork), 1 (An update is needed to fork properly), or 2 (Everything looks good).
-* *status* - string; General RPC error code. "OK" means everything looks good.
-* *threshold* - unsigned int; Minimum percent of votes to trigger hard fork. Default is 80.
-* *version* - unsigned int; The major block version for the fork.
-* *votes* - unsigned int; Number of votes towards hard fork.
-* *voting* - unsigned int; Hard fork voting status.
-* *window* - unsigned int; Number of blocks over which current votes are cast. Default is 10080 blocks.
-
-Example:
-
-```
-$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"hard_fork_info"}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- "earliest_height": 1009827,
- "enabled": false,
- "state": 2,
- "status": "OK",
- "threshold": 0,
- "version": 1,
- "votes": 7277,
- "voting": 2,
- "window": 10080
- }
-}
-```
-
-
-### **setbans**
-
-Ban another node by IP.
-
-Inputs:
-
-* *bans* - A list of nodes to ban:
- * *ip* - unsigned int; IP address to ban, in Int format.
- * *ban* - boolean; Set `true` to ban.
- * *seconds* - unsigned int; Number of seconds to ban node.
-
-Outputs:
-
-* *status* - string; General RPC error code. "OK" means everything looks good.
-
-Example:
-
-```
-$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"setbans","params":{"bans":[{"ip":838969536,"ban":true,"seconds":30}]}}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- "status": "OK"
- }
-}
-```
-
-
-### **getbans**
-
-Inputs: *None*.
-
-Outputs:
-
-* *bans* - List of banned nodes:
- * *ip* - unsigned int; Banned IP address, in Int format.
- * *seconds* - unsigned int; Local Unix time that IP is banned until.
-* *status* - string; General RPC error code. "OK" means everything looks good.
-
-Example:
-
-```
-$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getbans"}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- "bans": [{
- "ip": 838969536,
- "seconds": 1457748792
- }],
- "status": "OK"
- }
-}
-```
-
-
----
-
-## Other Daemon RPC Calls
-
-Not all daemon RPC calls use the JSON_RPC interface. This section gives examples of these calls.
-
-The data structure for these calls is different than the JSON RPC calls. Whereas the JSON RPC methods were called using the `/json_rpc` extension and specifying a method, these methods are called at their own extensions. For example:
-
- IP=127.0.0.1
- PORT=18081
- METHOD='gettransactions'
- PARAMS='{"txs_hashes":["d6e48158472848e6687173a91ae6eebfa3e1d778e65252ee99d7515d63090408"]}'
- curl \
- -X POST http://$IP:$PORT/$METHOD \
- -d $PARAMS \
- -H 'Content-Type: application/json'
-
-Note: It is recommended to use JSON RPC where such alternatives exist, rather than the following methods. For example, the recommended way to get a node's height is via the JSON RPC methods [get_info](#getinfo) or [getlastblockheader](#getlastblockheader), rather than [getheight](#getheight) below.
-
-
-### **/getheight**
-
-Get the node's current height.
-
-Inputs: *None*.
-
-Outputs:
-
-* *height* - unsigned int; Current length of longest chain known to daemon.
-
-```
-$ curl -X POST http://127.0.0.1:18081/getheight -H 'Content-Type: application/json'
-
-{
- "height": 993488,
- "status": "OK"
-}
-```
-
-
-### **/gettransactions**
-
-Look up one or more transactions by hash.
-
-Inputs:
-
-* *txs_hashes* - string list; List of transaction hashes to look up.
-* *decode_as_json* - boolean; Optional. If set `true`, the returned transaction information will be decoded rather than binary.
-
-Outputs:
-
-* *status* - General RPC error code. "OK" means everything looks good.
-* *txs_as_hex* - string; Full transaction information as a hex string.
-* *txs_as_json* - json string; (Optional - returned if set in inputs.) List of transaction info:
- * *version* - Transaction version
- * *unlock_time* - If not 0, this tells when a transaction output is spendable.
- * *vin* - List of inputs into transaction:
- * *key* - The public key of the previous output spent in this transaction.
- * *amount* - The amount of the input, in atomic units.
- * *key_offsets* - A list of integer offets to the input.
- * *k_image* - The key image for the given input
- * *vout* - List of outputs from transaction:
- * *amount* - Amount of transaction output, in atomic units.
- * *target* - Output destination information:
- * *key* - The stealth public key of the receiver. Whoever owns the private key associated with this key controls this transaction output.
- * *extra* - Usually called the "payment ID" but can be used to include any random 32 bytes.
- * *signatures* - List of ignatures used in ring signature to hide the true origin of the transaction.
-Example 1: Return transaction information in binary format.
-
-```
-$ curl -X POST http://127.0.0.1:18081/gettransactions -d '{"txs_hashes":["d6e48158472848e6687173a91ae6eebfa3e1d778e65252ee99d7515d63090408"]}' -H 'Content-Type: application/json'
-
-{
- "status": "OK",
- "txs_as_hex": ["..."]
-}
-```
-
-
-Example 2: Decode returned transaction information in JSON format. Note: the "vout" list has been truncated in the displayed return for space considerations.
-
-```
-$ curl -X POST http://127.0.0.1:18081/gettransactions -d '{"txs_hashes":["d6e48158472848e6687173a91ae6eebfa3e1d778e65252ee99d7515d63090408"],"decode_as_json":true}' -H 'Content-Type: application/json'
-
-{
- "status": "OK",
- "txs_as_hex": ["..."],
- "txs_as_json": ["{\n \"version\": 1, \n \"unlock_time\": 0, \n \"vin\": [ {\n \"key\": {\n \"amount\": 70000000, \n \"key_offsets\": [ 35952\n ], \n \"k_image\": \"d16908468dff9438a9814fe96bdaa575f06fe8da85772b72e54926428712293d\"\n }\n }, {\n \"key\": {\n \"amount\": 400000000000000, \n \"key_offsets\": [ 6830\n ], \n \"k_image\": \"c7a7024b763df1181ae6fe821b70669735e38a68162ac02362e33acbe829b605\"\n }\n }\n ], \n \"vout\": [ {\n \"amount\": 50000, \n \"target\": {\n \"key\": \"f6be43f7be4f06adcb1d06f4a07c637c7359e009cf3e57bb32b8c9ea636509c3\"\n }\n }, {\n \"amount\": 200000, \n \"target\": {\n \"key\": \"b0a7a8e32f2b5302552bcd8d85112c62838b1f56cccd844eb9b63e0a732d0353\"\n }\n }, ... \n ], \n \"extra\": [ 1, 225, 240, 98, 34, 169, 73, 47, 237, 117, 192, 30, 192, 60, 155, 47, 4, 115, 20, 21, 11, 13, 252, 219, 129, 13, 174, 37, 36, 78, 191, 141, 109\n ], \n \"signatures\": [ \"e6a3be8003d481d2855c8127f56871de3d28a4fb52385b999eb986c831c5cc08361c126b0db24a21b6c4299b438ee2be201d44d57a371230b9cd04395ab8c400\", \"8309851abaf2cf2a7091e0cdb9c83704fa7d68838a7a8ef8c178bb55a1e93a038dd18bb4a7549dc056b7a70e037cabd80911a03f427e36f712756d4c00f38f0b\"]\n}"]
-}
-```
-
-
-### **/is_key_image_spent**
-
-Check if outputs have been spent using the key image associated with the output.
-
-Inputs:
-
-* *key_images* - string list; List of key image hex strings to check.
-
-Outputs:
-
-* *spent_status* - unsigned int list; List of statuses for each image checked. Statuses are follows: 0 = unspent, 1 = spent in blockchain, 2 = spent in transaction pool
-* *status* - string; General RPC error code. "OK" means everything looks good.
-
-Example:
-
-```
-$ curl -X POST http://127.0.0.1:18081/is_key_image_spent -d '{"key_images":["8d1bd8181bf7d857bdb281e0153d84cd55a3fcaa57c3e570f4a49f935850b5e3","7319134bfc50668251f5b899c66b005805ee255c136f0e1cecbb0f3a912e09d4"]}' -H 'Content-Type: application/json'
-
-{
- "spent_status": [1,2],
- "status": "OK"
-}
-```
-
-
-### **/sendrawtransaction**
-
-Broadcast a raw transaction to the network.
-
-Inputs:
-
-* *tx_as_hex* - string; Full transaction information as hexidecimal string.
-
-Outputs:
-
-* *status* - string; General RPC error code. "OK" means everything looks good.
-
-Example (No return information included here.):
-
-
-```
-$ curl -X POST http://127.0.0.1:18081/sendrawtransaction -d '{"tx_as_hex":"de6a3..."}' -H 'Content-Type: application/json'
-```
-
-
-### **/get_transaction_pool**
-
-Show information about valid transactions seen by the node but not yet mined into a block, as well as spent key image information in the node's memory.
-
-Inputs: *None*.
-
-Outputs:
-
-* *spent_key_images* - List of spent output key images:
- * *id_hash* - string; Key image ID hash.
- * *txs_hashes* - string list; Key image transaction hashes.
-* *status* - string; General RPC error code. "OK" means everything looks good.
-* *transactions* - List of transactions in the mempool that have not been included in a block:
- * *blob_size* - unsigned int; The size of the full transaction blob.
- * *fee* - unsigned int; The amount of the mining fee included in the transaction, in atomic units.
- * *id_hash* - string; The transaction ID hash.
- * *kept_by_block* - boolean; We do not accept transactions that timed out before, unless set `true`.
- * *last_failed_height* - unsigned int; If the transaction has previously timed out, this tells at what height that occured.
- * *last_failed_id_hash* - string; Like the previous, this tells the previous transaction ID hash.
- * *max_used_block_height* - unsigned int; Tells the height of the most recent block with an output used in this transaction.
- * *max_used_block_hash* - string; Tells the hash of the most recent block with an output used in this transaction.
- * *receive_time* - unsigned int; The Unix time that the transaction was first seen on the network by the node.
- * *tx_json* - json string; JSON structure of all information in the transaction:
- * *version* - Transaction version
- * *unlock_time* - If not 0, this tells when a transaction output is spendable.
- * *vin* - List of inputs into transaction:
- * *key* - The public key of the previous output spent in this transaction.
- * *amount* - The amount of the input, in atomic units.
- * *key_offsets* - A list of integer offets to the input.
- * *k_image* - The key image for the given input
- * *vout* - List of outputs from transaction:
- * *amount* - Amount of transaction output, in atomic units.
- * *target* - Output destination information:
- * *key* - The stealth public key of the receiver. Whoever owns the private key associated with this key controls this transaction output.
- * *extra* - Usually called the "transaction ID" but can be used to include any random 32 bytes.
- * *signatures* - List of ignatures used in ring signature to hide the true origin of the transaction.
-
-Example (Note: Some lists in the returned information have been truncated for display reasons):
-
-```
-$ curl -X POST http://127.0.0.1:18081/get_transaction_pool -H 'Content-Type: application/json'
-
-{
- "spent_key_images": [{
- "id_hash": "1edb9ecc39602040282d326070ad22cb473c952c0d6280c9c4c3b853fb34f3bc",
- "txs_hashes": ["409911b2be02e3f0e930b326c67ab9e74675885ce23d71bb3bd28b62bc3e7803"]
- },{
- "id_hash": "4adb4bb63b3397027340ca4e6c45f4ce2147dfb3a4e0fafdec18834ae594a05e",
- "txs_hashes": ["946f1f4c52e3426a41959c93b60078f314813bc4bdebcf69b8ee11d593b2bd14"]
- },
- ...],
- "status": "OK",
- "transactions": [{
- "blob_size": 25761,
- "fee": 290000000000,
- "id_hash": "11d4cff23e610fac6a2b89187ad61d429a5e226652693dcac5d83d506eb92b96",
- "kept_by_block": false,
- "last_failed_height": 0,
- "last_failed_id_hash": "0000000000000000000000000000000000000000000000000000000000000000",
- "max_used_block_height": 954508,
- "max_used_block_id_hash": "03f96b374778bc059e47b96e2beec2e6d4d9e0ad39afeabdbcd77e1bd5a62f81",
- "receive_time": 1457676127,
- "tx_json": "{\n \"version\": 1, \n \"unlock_time\": 0, \n \"vin\": [ {\n \"key\": {\n \"amount\": 70000000000, \n \"key_offsets\": [ 63408, 18978, 78357, 16560\n ], \n \"k_image\": \"7319134bfc50668251f5b899c66b005805ee255c136f0e1cecbb0f3a912e09d4\"\n }\n }, ... ], \n \"vout\": [ {\n \"amount\": 80000000000, \n \"target\": {\n \"key\": \"094e6a1b187385533665f89db741149f42d95fdc50bdd2a2384bcd1dc5209c55\"\n }\n }, ... ], \n \"extra\": [ 2, 33, 0, 15, 56, 190, 21, 169, 77, 13, 182, 209, 51, 35, 54, 96, 89, 237, 96, 23, 24, 107, 240, 79, 40, 86, 64, 68, 45, 166, 119, 192, 17, 225, 23, 1, 31, 159, 145, 15, 173, 255, 165, 192, 55, 84, 127, 154, 163, 25, 85, 204, 212, 127, 147, 133, 118, 218, 166, 52, 78, 188, 131, 235, 9, 159, 105, 158\n ], \n \"signatures\": [ \"966e5a67fbdbf72d7dc0364b705121a58e0ced7e2ab45747b6b154c05a1afe04fac4aac7f64faa2dc6dd4d51b8277f11e2f2ec7729fac225088befe3b8399c0b71a4cb55b9d0e20f93d305c78cebceff1bcfcfaf225428dfcfaaec630c88720ab65bf5d3399dd1ac82ea0ecf308b3f80d9780af7742fb157692cd60515a7e2086878f082117fa80fff3d257de7d3a2e9cc8b3472ef4a5e545d90e1159523a60f38d16cece783579627124776813334bdb2a2df4171ef1fa12bf415da338ce5085c01e7a715638ef5505aebec06a0625aaa72d13839838f7d4f981673c8f05f08408e8b372f900af7227c49cfb1e1febab6c07dd42b7c26f921cf010832841205\", ... ]\n}"
- },
- ...]
-}
-```
-
-
-### **/stop_daemon**
-
-Send a command to the daemon to safely disconnect and shut down.
-
-Inputs: *None*.
-
-Outputs:
-
-* *status* - string; General RPC error code. "OK" means everything looks good.
-
-Example:
-
-```
-$ curl -X POST http://127.0.0.1:18081/stop_daemon -H 'Content-Type: application/json'
-
-{
- "status": "OK"
-}
-```
-
+{% tf resources/developer-guides/daemon-rpc.md %}
diff --git a/resources/developer-guides/index.md b/resources/developer-guides/index.md
index 8068df6d10ec6d2df9435256279bdd2fe9f737ef..a453750cc6b18b0892fde0fdb695c7c7d6438802 100644
--- a/resources/developer-guides/index.md
+++ b/resources/developer-guides/index.md
@@ -1,24 +1,6 @@
---
layout: custom
-title: "Developer Guides"
+title: titles.developerguides
+permalink: /resources/developer-guides/index.html
---
-
-<div class="guides">
-
-<div class="center-xs container description">
-<p class="text-center">Please note: the guides below are currently out of date, but are considered a good starting point for most calls. </p>
-</div>
-
-<section class="container full">
- <div class="info-block">
- <h2>RPC Documetation</h2>
-<div markdown="1">
-
-[Daemon RPC Documentation](daemon-rpc.html)
-[Wallet RPC Documentation](wallet-rpc.html)
-
-More coming soon...
-</div>
- </div>
-</section>
-</div>
\ No newline at end of file
+{% tf resources/developer-guides.md %}
\ No newline at end of file
diff --git a/resources/developer-guides/wallet-rpc.md b/resources/developer-guides/wallet-rpc.md
index d99fdb19ac376b7d2a4218f6fdd5a01f147e09e7..c8aaa23ce9554d5979e8084d68d28d3b17be4717 100644
--- a/resources/developer-guides/wallet-rpc.md
+++ b/resources/developer-guides/wallet-rpc.md
@@ -1,1226 +1,6 @@
---
-layout: static_page
+layout: user-guide
title: "Wallet RPC documentation"
-title-pre-kick: "Developer Guide: "
-title-kick: "Wallet RPC documentation "
-title-post-kick: ""
-kick-class: "green-kicks"
-icon: "icon_client"
-attribution: "<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->"
+permalink: /resources/developer-guides/wallet-rpc.html
---
-
-## Introduction
-
-This is a list of the monero-wallet-rpc calls, their inputs and outputs, and examples of each. The program monero-wallet-rpc replaced the rpc interface that was in simplewallet and then monero-wallet-cli.
-
-All monero-wallet-rpc methods use the same JSON RPC interface. For example:
-
-```
-IP=127.0.0.1
-PORT=18082
-METHOD="make_integrated_address"
-PARAMS="{\"payment_id\":\"1234567890123456789012345678900012345678901234567890123456789000\"}"
-curl \
- -X POST http://$IP:$PORT/json_rpc \
- -d '{"jsonrpc":"2.0","id":"0","method":"'$METHOD'","params":'"$PARAMS"'}' \
- -H 'Content-Type: application/json'
-```
-
-If the monero-wallet-rpc was executed with the `--rpc-login` argument as `username:password`, then follow this example:
-
-```
-IP=127.0.0.1
-PORT=18082
-METHOD="make_integrated_address"
-PARAMS="{\"payment_id\":\"1234567890123456789012345678900012345678901234567890123456789000\"}"
-curl \
- -u username:password --digest \
- -X POST http://$IP:$PORT/json_rpc \
- -d '{"jsonrpc":"2.0","id":"0","method":"'$METHOD'","params":'"$PARAMS"'}' \
- -H 'Content-Type: application/json'
-```
-
-Note: "atomic units" refer to the smallest fraction of 1 XMR according to the monerod implementation. **1 XMR = 1e12 atomic units.**
-
-### Index of JSON RPC Methods:
-
-* [getbalance](#getbalance)
-* [getaddress](#getaddress)
-* [getheight](#getheight)
-* [transfer](#transfer)
-* [transfer_split](#transfer_split)
-* [sweep_dust](#sweep_dust)
-* [sweep_all](#sweep_all)
-* [store](#store)
-* [get_payments](#get_payments)
-* [get_bulk_payments](#get_bulk_payments)
-* [get_transfers](#get_transfers)
-* [get_transfer_by_txid](#get_transfer_by_txid)
-* [incoming_transfers](#incoming_transfers)
-* [query_key](#query_key)
-* [make_integrated_address](#make_integrated_address)
-* [split_integrated_address](#split_integrated_address)
-* [stop_wallet](#stop_wallet)
-* [make_uri](#make_uri)
-* [parse_uri](#parse_uri)
-* [rescan_blockchain](#rescan_blockchain)
-* [set_tx_notes](#set_tx_notes)
-* [get_tx_notes](#get_tx_notes)
-* [sign](#sign)
-* [verify](#verify)
-* [export_key_images](#export_key_images)
-* [import_key_images](#import_key_images)
-* [get_address_book](#get_address_book)
-* [add_address_book](#add_address_book)
-* [delete_address_book](#delete_address_book)
-* [rescan_spent](#rescan_spent)
-* [start_mining](#start_mining)
-* [stop_mining](#stop_mining)
-* [get_languages](#get_languages)
-* [create_wallet](#create_wallet)
-* [open_wallet](#open_wallet)
-
----
-
-## JSON RPC Methods:
-
-### **getbalance**
-
-Return the wallet's balance.
-
-Inputs: *None*.
-
-Outputs:
-
-* *balance* - unsigned int; The total balance of the current monero-wallet-rpc in session.
-* *unlocked_balance* - unsigned int; Unlocked funds are those funds that are sufficiently deep enough in the Monero blockchain to be considered safe to spend.
-
-Example:
-
-```
-$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getbalance"}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- "balance": 140000000000,
- "unlocked_balance": 50000000000
- }
-}
-```
-
-
-### **getaddress**
-
-Return the wallet's address.
-
-Inputs: *None*.
-
-Outputs:
-
-* *address* - string; The 95-character hex address string of the monero-wallet-rpc in session.
-
-Example:
-
-```
-$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getaddress"}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- "address": "427ZuEhNJQRXoyJAeEoBaNW56ScQaLXyyQWgxeRL9KgAUhVzkvfiELZV7fCPBuuB2CGuJiWFQjhnhhwiH1FsHYGQGaDsaBA"
- }
-}
-```
-
-
-### **getheight**
-
-Returns the wallet's current block height.
-
-Inputs: *None*.
-
-Outputs:
-
-* *height* - unsigned int; The current monero-wallet-rpc's blockchain height. If the wallet has been offline for a long time, it may need to catch up with the daemon.
-
-Example:
-
-```
-$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getheight"}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- "height": 994310
- }
-}
-```
-
-
-### **transfer**
-
-Send monero to a number of recipients.
-
-Inputs:
-
-* *destinations* - array of destinations to receive XMR:
- * *amount* - unsigned int; Amount to send to each destination, in atomic units.
- * *address* - string; Destination public address.
-* *fee* - unsigned int; Ignored, will be automatically calculated.
-* *mixin* - unsigned int; Number of outpouts from the blockchain to mix with (0 means no mixing).
-* *unlock_time* - unsigned int; Number of blocks before the monero can be spent (0 to not add a lock).
-* *payment_id* - string; (Optional) Random 32-byte/64-character hex string to identify a transaction.
-* *get_tx_key* - boolean; (Optional) Return the transaction key after sending.
-* *priority* - unsigned int; Set a priority for the transaction. Accepted Values are: 0-3 for: default, unimportant, normal, elevated, priority.
-* *do_not_relay* - boolean; (Optional) If true, the newly created transaction will not be relayed to the monero network. (Defaults to false)
-* *get_tx_hex* - boolean; Return the transaction as hex string after sending
-
-
-Outputs:
-
-* *fee* - Integer value of the fee charged for the txn.
-* *tx_hash* - String for the publically searchable transaction hash
-* *tx_key* - String for the transaction key if get_tx_key is true, otherwise, blank string.
-* *tx_blob* - Transaction as hex string if get_tx_hex is true
-
-
-Example:
-
-```
-$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"transfer","params":{"destinations":[{"amount":100000000,"address":"9wNgSYy2F9qPZu7KBjvsFgZLTKE2TZgEpNFbGka9gA5zPmAXS35QzzYaLKJRkYTnzgArGNX7TvSqZC87tBLwtaC5RQgJ8rm"},{"amount":200000000,"address":"9vH5D7Fv47mbpCpdcthcjU34rqiiAYRCh1tYywmhqnEk9iwCE9yppgNCXAyVHG5qJt2kExa42TuhzQfJbmbpeGLkVbg8xit"}],"mixin":4,"get_tx_key": true}}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- "fee": 48958481211,
- "tx_hash": "985180f468637bc6d2f72ee054e1e34b8d5097988bb29a2e0cb763e4464db23c",
- "tx_key": "8d62e5637f1fcc9a8904057d6bed6c697618507b193e956f77c31ce662b2ee07"
- }
-}
-```
-
-
-### **transfer_split**
-
-Same as transfer, but can split into more than one tx if necessary.
-
-Inputs:
-
-* *destinations* - array of destinations to receive XMR:
- * *amount* - unsigned int; Amount to send to each destination, in atomic units.
- * *address* - string; Destination public address.
-* *fee* - unsigned int; Ignored, will be automatically calculated.
-* *mixin* - unsigned int; Number of outpouts from the blockchain to mix with (0 means no mixing).
-* *unlock_time* - unsigned int; Number of blocks before the monero can be spent (0 to not add a lock).
-* *payment_id* - string; (Optional) Random 32-byte/64-character hex string to identify a transaction.
-* *get_tx_keys* - boolean; (Optional) Return the transaction keys after sending. -- Ignored
-* *priority* - unsigned int; Set a priority for the transactions. Accepted Values are: 0-3 for: default, unimportant, normal, elevated, priority.
-* *do_not_relay* - boolean; (Optional) If true, the newly created transaction will not be relayed to the monero network. (Defaults to false)
-* *get_tx_hex* - boolean; Return the transactions as hex string after sending
-* *new_algorithm* - boolean; True to use the new transaction construction algorithm, defaults to false.
-
-Outputs:
-
-* *fee_list* - array of: integer. The amount of fees paid for every transaction.
-* *tx_hash_list* - array of: string. The tx hashes of every transaction.
-* *tx_blob_list* - array of: string. The tx as hex string for every transaction.
-* *amount_list* - array of: integer. The amount transferred for every transaction..
-* *tx_key_list* - array of: string. The transaction keys for every transaction.
-
-Example:
-
-```
-$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"transfer_split","params":{"destinations":[{"amount":100000000,"address":"9wNgSYy2F9qPZu7KBjvsFgZLTKE2TZgEpNFbGka9gA5zPmAXS35QzzYaLKJRkYTnzgArGNX7TvSqZC87tBwtaC5RQgJ8rm"},{"amount":200000000,"address":"9vH5D7Fv47mbpCpdcthcjU34rqiiAYRCh1tYywmhqnEk9iwCE9yppgNCXAyVHG5qJt2kExa42TuhzQfJbmbpeGLkVbg8xit"},{"amount":200000000,"address":"9vC5Q25cR1d3WzKX6dpTaLJaqZyDrtTnfadTmVuB1Wue2tyFGxUhiE4RGa74pEDJv7gSySzcd1Ao6G1nzSaqp78vLfP6MPj"},{"amount":200000000,"address":"A2MSrn49ziBPJBh8ZNEhhbfyLMou6mao4C1F5TLGUatmUnCxZArDYkcbAnVkVEopWVeak2rKDrmc8JpoS7n5dvfN9YDPBTG"},{"amount":200000000,"address":"9tEDyVQ8zgRQbDYiykTdpw5kZ6qWQWcKfExEj9eQshjpGb3sdr3UyWE2AHWzUGzJjaH9HN1DdGBdyQQ4AqGMc7rr5xYwZWW"}],"mixin":4,"get_tx_key": true, "new_algorithm": true}}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- "fee_list": [97916962422],
- "tx_hash_list": ["c5c389846e701c27aaf1f7ab8b9dc457b471fcea5bc9710e8020d51275afbc54"]
- }
-}
-```
-
-
-### **sweep_dust**
-
-Send all dust outputs back to the wallet's, to make them easier to spend (and mix).
-
-Inputs: *None*.
-
-Outputs:
-
-* *tx_hash_list* - list of: string
-
-Example (In this example, `sweep_dust` returns an error due to insufficient funds to sweep):
-
-
-```
-$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"sweep_dust"}' -H 'Content-Type: application/json'
-
-{
- "error": {
- "code": -4,
- "message": "not enough money"
- },
- "id": "0",
- "jsonrpc": "2.0"
-}
-```
-
-### **sweep_all**
-
-Send all unlocked balance to an address.
-
-Inputs:
-
-* *address* - string; Destination public address.
-* *priority* - unsigned int; (Optional)
-* *mixin* - unsigned int; Number of outpouts from the blockchain to mix with (0 means no mixing).
-* *unlock_time* - unsigned int; Number of blocks before the monero can be spent (0 to not add a lock).
-* *payment_id* - string; (Optional) Random 32-byte/64-character hex string to identify a transaction.
-* *get_tx_keys* - boolean; (Optional) Return the transaction keys after sending.
-* *below_amount* - unsigned int; (Optional)
-* *do_not_relay* - boolean; (Optional)
-* *get_tx_hex* - boolean; (Optional) return the transactions as hex encoded string.
-
-Outputs:
-
-* *tx_hash_list* - array of string;
-* *tx_key_list* - array of string;
-* *tx_blob_list* - array of string;
-
-Example:
-
-```
-$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"sweep_all","params":{"address":"9sS8eRU2b5ZbN2FPSrpkiab1bjbHE5XtL6Ti6We3Fhw5aQPudRfVVypjgzKDNkxtvTQSPs122NKggb2mqcqkKSeMNVu59S","mixin":2,"unlock_time":0,"get_tx_keys":true}}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- "tx_hash_list": ["53a3648797d5524dd037d4105e067fa61468faecab41927fc43adbb26c202d22"],
- "tx_key_list": ["e83b3b78235e36cd7e4d9695efd81a3b3e64c7d1f1ebd61892f0a7add6a50301"]
- }
-}
-```
-
-### **store**
-
-Save the blockchain.
-
-Inputs: *None*.
-
-Outputs: *None*.
-
-Example:
-
-```
-$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"store"}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- }
-}
-```
-
-
-### **get_payments**
-
-Get a list of incoming payments using a given payment id.
-
-Inputs:
-
-* *payment_id* - string
-
-Outputs:
-
-* *payments* - list of:
- * *payment_id* - string
- * *tx_hash* - string
- * *amount* - unsigned int
- * *block_height* - unsigned int
- * *unlock_time* - unsigned int
-
-Example:
-
-```
-$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_payments","params":{"payment_id":"4279257e0a20608e25dba8744949c9e1caff4fcdafc7d5362ecf14225f3d9030"}}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- "payments": [{
- "amount": 10350000000000,
- "block_height": 994327,
- "payment_id": "4279257e0a20608e25dba8744949c9e1caff4fcdafc7d5362ecf14225f3d9030",
- "tx_hash": "c391089f5b1b02067acc15294e3629a463412af1f1ed0f354113dd4467e4f6c1",
- "unlock_time": 0
- }]
- }
-}
-```
-
-
-### **get_bulk_payments**
-
-Get a list of incoming payments using a given payment id, or a list of payments ids, from a given height. This method is the preferred method over `get_payments` because it has the same functionality but is more extendable. Either is fine for looking up transactions by a single payment ID.
-
-Inputs:
-
-* *payment_ids* - array of: string
- * *min_block_height* - unsigned int; The block height at which to start looking for payments.
-
-Outputs:
-
-* *payments* - list of:
- * *payment_id* - string
- * *tx_hash* - string
- * *amount* - unsigned int
- * *block_height* - unsigned int
- * *unlock_time* - unsigned int
-
-Example:
-
-```
-$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_bulk_payments","params":{"payment_ids":["4279257e0a20608e25dba8744949c9e1caff4fcdafc7d5362ecf14225f3d9030"],"min_block_height":990000}}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- "payments": [{
- "amount": 10350000000000,
- "block_height": 994327,
- "payment_id": "4279257e0a20608e25dba8744949c9e1caff4fcdafc7d5362ecf14225f3d9030",
- "tx_hash": "c391089f5b1b02067acc15294e3629a463412af1f1ed0f354113dd4467e4f6c1",
- "unlock_time": 0
- }]
- }
-}
-```
-
-
-### **get_transfers**
-
-Returns a list of transfers.
-
-Inputs:
-
-* *in* - boolean;
-* *out* - boolean;
-* *pending* - boolean;
-* *failed* - boolean;
-* *pool* - boolean;
-* *filter_by_height* - boolean;
-* *min_height* - unsigned int;
-* *max_height* - unsigned int;
-
-Outputs:
-
-* *in* array of transfers:
- * *txid* - string;
- * *payment_id* - string;
- * *height* - unsigned int;
- * *timestamp* - unsigned int;
- * *amount* - unsigned int;
- * *fee* - unsigned int;
- * *note* - string;
- * *destinations* - std::list<transfer_destination>;
- * *type* - string;
-* *out* array of transfers
-* *pending* array of transfers
-* *failed* array of transfers
-* *pool* array of transfers
-
-
-Example:
-
-```
-$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_transfers","params":{"pool":true}}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- "pool": [{
- "amount": 500000000000,
- "fee": 0,
- "height": 0,
- "note": "",
- "payment_id": "758d9b225fda7b7f",
- "timestamp": 1488312467,
- "txid": "da7301d5423efa09fabacb720002e978d114ff2db6a1546f8b820644a1b96208",
- "type": "pool"
- }]
- }
-}
-```
-
-### **get_transfer_by_txid**
-
-Show information about a transfer to/from this address.
-
-Inputs:
-
-* *txid* - string
-
-Outputs:
-
-* *transfer* - JSON object containing parment information:
- * *amount* - unsigned int
- * *fee* - unsigned int
- * *height* - unsigned int
- * *note* - string
- * *payment_id* - string
- * *timestamp* - unsigned int
- * *txid* - string
- * *type* - string
-
-Example:
-
-```
-$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_transfer_by_txid","params":{"txid":"f2d33ba969a09941c6671e6dfe7e9456e5f686eca72c1a94a3e63ac6d7f27baf"}}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- "transfer": {
- "amount": 10000000000000,
- "fee": 0,
- "height": 1316388,
- "note": "",
- "payment_id": "0000000000000000",
- "timestamp": 1495539310,
- "txid": "f2d33ba969a09941c6671e6dfe7e9456e5f686eca72c1a94a3e63ac6d7f27baf",
- "type": "in"
- }
- }
-}
-```
-
-
-### **incoming_transfers**
-
-Return a list of incoming transfers to the wallet.
-
-Inputs:
-
-* *transfer_type* - string; "all": all the transfers, "available": only transfers which are not yet spent, OR "unavailable": only transfers which are already spent.
-
-Outputs:
-
-* *transfers* - list of:
- * *amount* - unsigned int
- * *spent* - boolean
- * *global_index* - unsigned int; Mostly internal use, can be ignored by most users.
- * *tx_hash* - string; Several incoming transfers may share the same hash if they were in the same transaction.
- * *tx_size* - unsigned int
-
-Example (Return "all" transaction types):
-
-```
-$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"incoming_transfers","params":{"transfer_type":"all"}}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- "transfers": [{
- "amount": 10000000000000,
- "global_index": 711506,
- "spent": false,
- "tx_hash": "<c391089f5b1b02067acc15294e3629a463412af1f1ed0f354113dd4467e4f6c1>",
- "tx_size": 5870
- },{
- "amount": 300000000000,
- "global_index": 794232,
- "spent": false,
- "tx_hash": "<c391089f5b1b02067acc15294e3629a463412af1f1ed0f354113dd4467e4f6c1>",
- "tx_size": 5870
- },{
- "amount": 50000000000,
- "global_index": 213659,
- "spent": false,
- "tx_hash": "<c391089f5b1b02067acc15294e3629a463412af1f1ed0f354113dd4467e4f6c1>",
- "tx_size": 5870
- }]
- }
-}
-```
-
-Example (Return "available" transactions):
-
-```
-$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"incoming_transfers","params":{"transfer_type":"available"}}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- "transfers": [{
- "amount": 10000000000000,
- "global_index": 711506,
- "spent": false,
- "tx_hash": "<c391089f5b1b02067acc15294e3629a463412af1f1ed0f354113dd4467e4f6c1>",
- "tx_size": 5870
- },{
- "amount": 300000000000,
- "global_index": 794232,
- "spent": false,
- "tx_hash": "<c391089f5b1b02067acc15294e3629a463412af1f1ed0f354113dd4467e4f6c1>",
- "tx_size": 5870
- },{
- "amount": 50000000000,
- "global_index": 213659,
- "spent": false,
- "tx_hash": "<c391089f5b1b02067acc15294e3629a463412af1f1ed0f354113dd4467e4f6c1>",
- "tx_size": 5870
- }]
- }
-}
-```
-
-Example (Return "unavailable" transaction. Note that this particular example returns 0 unavailable transactions):
-
-```
-$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"incoming_transfers","params":{"transfer_type":"unavailable"}}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- }
-}
-```
-
-
-### **query_key**
-
-Return the spend or view private key.
-
-Inputs:
-
-* *key_type* - string; Which key to retrieve: "mnemonic" - the mnemonic seed (older wallets do not have one) OR "view_key" - the view key
-
-Outputs:
-
-* *key* - string; The view key will be hex encoded, while the mnemonic will be a string of words.
-
-Example (Query view key):
-
-```
-$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"query_key","params":{"key_type":"view_key"}}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- "key": "7e341d..."
- }
-}
-```
-
-Example (Query mnemonic key):
-
-```
-$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"query_key","params":{"key_type":"mnemonic"}}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- "key": "adapt adapt nostril ..."
- }
-}
-```
-
-
-### **make_integrated_address**
-
-Make an integrated address from the wallet address and a payment id.
-
-Inputs:
-
-* *payment_id* - string; hex encoded; can be empty, in which case a random payment id is generated
-
-Outputs:
-
-* *integrated_address* - string
-
-Example (Payment ID is empty, use a random ID):
-
-```
-$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"make_integrated_address","params":{"payment_id":""}}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- "integrated_address": "4BpEv3WrufwXoyJAeEoBaNW56ScQaLXyyQWgxeRL9KgAUhVzkvfiELZV7fCPBuuB2CGuJiWFQjhnhhwiH1FsHYGQQ8H2RRJveAtUeiFs6J"
- }
-}
-```
-
-
-### **split_integrated_address**
-
-Retrieve the standard address and payment id corresponding to an integrated address.
-
-Inputs:
-
-* *integrated_address* - string
-
-Outputs:
-
-* *standard_address* - string
-* *payment* - string; hex encoded
-
-Example:
-
-```
-$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"split_integrated_address","params":{"integrated_address": "4BpEv3WrufwXoyJAeEoBaNW56ScQaLXyyQWgxeRL9KgAUhVzkvfiELZV7fCPBuuB2CGuJiWFQjhnhhwiH1FsHYGQQ8H2RRJveAtUeiFs6J"}}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- "payment_id": "<420fa29b2d9a49f5>",
- "standard_address": "427ZuEhNJQRXoyJAeEoBaNW56ScQaLXyyQWgxeRL9KgAUhVzkvfiELZV7fCPBuuB2CGuJiWFQjhnhhwiH1FsHYGQGaDsaBA"
- }
-}
-```
-
-
-### **stop_wallet**
-
-Stops the wallet, storing the current state.
-
-Inputs: *None*.
-
-Outputs: *None*.
-
-Example:
-
-```
-$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"stop_wallet"}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- }
-}
-```
-
-
-### **make_uri**
-
-Create a payment URI using the official URI spec.
-
-Inputs:
-
-* *address* - wallet address string
-* *amount* (optional) - the integer amount to receive, in **atomic** units
-* *payment_id* (optional) - 16 or 64 character hexadecimal payment id string
-* *recipient_name* (optional) - string name of the payment recipient
-* *tx_description* (optional) - string describing the reason for the tx
-
-Outputs:
-
-* *uri* - a string containing all the payment input information as a properly formatted payment URI
-
-Example:
-
-```
-$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"make_uri","params":{"address":"44AFFq5kSiGBoZ4NMDwYtN18obc8AemS33DBLWs3H7otXft3XjrpDtQGv7SqSsaBYBb98uNbr2VBBEt7f2wfn3RVGQBEP3A","amount":10,"payment_id":"0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef","tx_description":"Testing out the make_uri function.","recipient_name":"Monero Project donation address"}}' -H 'Content-Type: application/json'
-
-{
- "id": 0,
- "jsonrpc": "2.0",
- "result": {
- "uri": "monero:44AFFq5kSiGBoZ4NMDwYtN18obc8AemS33DBLWs3H7otXft3XjrpDtQGv7SqSsaBYBb98uNbr2VBBEt7f2wfn3RVGQBEP3A?tx_payment_id=0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef&tx_amount=0.000000000010&recipient_name=Monero%20Project%20donation%20address&tx_description=Testing%20out%20the%20make_uri%20function."
- }
-}
-```
-
-
-### **parse_uri**
-
-Parse a payment URI to get payment information.
-
-Inputs:
-
-* *uri* - a string containing all the payment input information as a properly formatted payment URI
-
-Outputs:
-
-* *uri* - JSON object containing payment information:
- * *address* - wallet address string
- * *amount* - the decimal amount to receive, in **coin** units (0 if not provided)
- * *payment_id* - 16 or 64 character hexadecimal payment id string (empty if not provided)
- * *recipient_name* - string name of the payment recipient (empty if not provided)
- * *tx_description* - string describing the reason for the tx (empty if not provided)
-
-Example:
-
-```
-$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"parse_uri","params":{"uri":"monero:44AFFq5kSiGBoZ4NMDwYtN18obc8AemS33DBLWs3H7otXft3XjrpDtQGv7SqSsaBYBb98uNbr2VBBEt7f2wfn3RVGQBEP3A?tx_payment_id=0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef&tx_amount=0.000000000010&recipient_name=Monero%20Project%20donation%20address&tx_description=Testing%20out%20the%20make_uri%20function."}}' -H 'Content-Type: application/json'
-
-{
- "id": 0,
- "jsonrpc": "2.0",
- "result": {
- "uri": {
- "address": "44AFFq5kSiGBoZ4NMDwYtN18obc8AemS33DBLWs3H7otXft3XjrpDtQGv7SqSsaBYBb98uNbr2VBBEt7f2wfn3RVGQBEP3A",
- "amount": 10,
- "payment_id": "0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef",
- "recipient_name": "Monero Project donation address",
- "tx_description": "Testing out the make_uri function."
- }
- }
-}
-```
-
-
-### **rescan_blockchain**
-
-Rescan blockchain from scratch.
-
-Inputs: *None*.
-
-Outputs: *None*.
-
-Example:
-
-```
-$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"rescan_blockchain" -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- }
-}
-```
-
-
-### **set_tx_notes**
-
-Set arbitrary string notes for transactions.
-
-Inputs:
-
-* *txids* - array of string; transaction ids
-* *notes* - array of string; notes for the transactions
-
-Outputs: *None*.
-
-Example:
-
-```
-$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"set_tx_notes","params":{"txids":["6a1a100c079c236e2cbf36f7760e8ef1a9e8357c434aa790a8c78de653ec4cf2"],"notes":["This is an example"]}}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- }
-}
-```
-
-
-### **get_tx_notes**
-
-Get string notes for transactions.
-
-Inputs:
-
-* *txids* - array of string; transaction ids
-
-Outputs:
-
-* *notes* - array of string; notes for the transactions
-
-Example:
-
-```
-$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_tx_notes","params":{"txids":["6a1a100c079c236e2cbf36f7760e8ef1a9e8357c434aa790a8c78de653ec4cf2"]}}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- "notes": ["This is an example"]
- }
-}
-```
-
-
-### **sign**
-
-Sign a string.
-
-Inputs:
-
-* *data* - string;
-
-Outputs:
-
-* *signature* - string;
-
-Example:
-
-```
-$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"sign","params":{"data":"This is sample data to be signed"}}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- "signature": "SigV1Xp61ZkGguxSCHpkYEVw9eaWfRfSoAf36PCsSCApx4DUrKWHEqM9CdNwjeuhJii6LHDVDFxvTPijFsj3L8NDQp1TV"
- }
-}
-```
-
-
-### **verify**
-
-Verify a signature on a string.
-
-Inputs:
-
-* *data* - string;
-* *address* - string;
-* *signature* - string;
-
-Outputs:
-
-* *good* - boolean;
-
-Example:
-
-```
-$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"verify","params":{"data":"This is sample data to be signed","address":"9sS8eRU2b5ZbN2FPSrpkiab1bjbHE5XtL6Ti6We3Fhw5aQPudRfVVypjgzKDNkxtvTQZSPs122NKggb2mqcqkKSeMNVu59S","signature":"SigV1Xp61ZkGguxSCHpkYEVw9eaWfRfSoAf36PCsSCApx4DUrKWHEqM9CdNwjeuhJii6LHDVDFxvTPijFsj3L8NDQp1TV"}}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- "good": true
- }
-}
-```
-
-
-### **export_key_images**
-
-Export a signed set of key images.
-
-Inputs: *None*.
-
-Outputs:
-
-* *signed_key_images* - array of signed key images:
- * *key_image* - string;
- * *signature* - string;
-
-Example:
-
-```
-$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"export_key_images"}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- "signed_key_images": [{
- "key_image": "62b83df78baad99e23b5ad3f667bc6f8d388a13d9e84c7bb6c223a556dfd34af",
- "signature": "b87b7e989aa85aa3a2a7cd8adcb3a848d3512ff718b168e15217ff3e5da29c0183c0328b97cc052fcb5ee3548aa5e41e530ba9d854199ea19d7ddaf6a54a4c0a"
- }]
- }
-}
-```
-
-
-### **import_key_images**
-
-Import signed key images list and verify their spent status.
-
-Inputs:
-
-* *signed_key_images* - array of signed key images:
- * *key_image* - string;
- * *signature* - string;
-
-Outputs:
-
-* *height* - unsigned int;
-* *spent* - unsigned int;
-* *unspent* - unsigned int;
-
-Example:
-
-```
-$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"import_key_images", "params":{"signed_key_images":[{"key_image":"63b83df78cafd99e23b5ad3f667bc6f8d38813d9e84c7bb6c223a556dfd34af","signature":"b87b7e989aa86aa2a7a7cd8adcb3a848d3512ff718b168e15217ff3e5da29c0183c0328b97cc052fcb5ee3548aa5e41e530ba9d854199ea19d7ddaf6a54a4c0a"},{"key_image":"44ec12fbc56c533a30b09de8ae26febd515528c4957dfe875430377a7e212b4e","signature":"91105f15be0b25bc2a94bd78a7e261608974d6d888080b9f1815655b98af190340325ea1a0840a5951dacf913d4de1b2bd33ea59c1cb7bce1b6648afa7133d03"}]}}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- "height": 986050,
- "spent": 10000100000000,
- "unspent": 4979852760000
- }
-}
-```
-
-
-### **get_address_book**
-
-Retrieves entries from the address book.
-
-Inputs:
-
-* *entries* - array of unsigned int; indices of the requested address book entries
-
-Outputs:
-
-* *entries* - array of entries:
- * *address* - string;
- * *description* - string;
- * *index* - unsigned int;
- * *payment_id* - string;
-
-Example:
-
-```
-$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_address_book","params":{"entries":[1,2]}}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- "entries": [{
- "address": "A135xq3GVMdU5qtAm4hN7zjPgz8bRaiSUQmtuDdjZ6CgXayvQruJy3WPe95qj873JhK4YdTQjoR39Leg6esznQk8PckhjRN",
- "description": "",
- "index": 1,
- "payment_id": "0000000000000000000000000000000000000000000000000000000000000000"
- },{
- "address": "A135xq3GVMdU5qtAm4hN7zjPgz8bRaiSUQmtuDdjZ6CgXayvQruJy3WPe95qj873JhK4YdTQjoR39Leg6esznQk8PckhjRN",
- "description": "",
- "index": 2,
- "payment_id": "0000000000000000000000000000000000000000000000000000000000000000"
- }]
- }
-}
-```
-
-
-### **add_address_book**
-
-Add an entry to the address book.
-
-Inputs:
-
-* *address* - string;
-* *payment_id* - (optional) string, defaults to "0000000000000000000000000000000000000000000000000000000000000000";
-* *description* - (optional) string, defaults to "";
-
-Outputs:
-
-* *index* - unsigned int; The index of the address book entry.
-
-Example:
-
-```
-$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"add_address_book","params":{"address":"44AFFq5kSiGBoZ4NMDwYtN18obc8AemS33DBLWs3H7otXft3XjrpDtQGv7SqSsBYBb98uNbr2VBBEt7f2wfn3RVGQBEP3A","description":"Donation address for the Monero project"}}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- "index": 2
- }
-}
-```
-
-
-### **delete_address_book**
-
-Delete an entry from the address book.
-
-Inputs:
-
-* *index* - unsigned int; The index of the address book entry.
-
-Outputs: *None*.
-
-Example:
-
-```
-$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"delete_address_book","params":{"index":0}}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- }
-}
-```
-
-
-### **rescan_spent**
-
-Rescan the blockchain for spent outputs.
-
-Inputs: *None*.
-
-Outputs: *None*.
-
-Example:
-
-```
-$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"rescan_spent"}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- }
-}
-```
-
-
-### **start_mining**
-
-Start mining in the Monero daemon.
-
-Inputs:
-
-* *threads_count* - unsigned int; Number of threads created for mining
-* *do_background_mining* - boolean;
-* *ignore_battery* - boolean;
-
-Outputs: *None*.
-
-Example:
-
-```
-$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"start_mining","params":{"threads_count":1,"do_background_mining":true,"ignore_battery":true}}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- }
-}
-```
-
-
-### **stop_mining**
-
-Stop mining in the Monero daemon.
-
-Inputs: *None*.
-
-Outputs: *None*.
-
-Example:
-
-```
-$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"stop_mining"}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- }
-}
-```
-
-
-### **get_languages**
-
-Get a list of available languages for your wallet's seed.
-
-Inputs: *None*.
-
-Outputs:
-
-* *languages* - array of string; List of available languages
-
-Example:
-
-```
-$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_languages"}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- "languages": ["Deutsch","English","Español","Français","Italiano","Nederlands","Português","руÑÑкий Ñзык","日本語","简体ä¸æ–‡ (ä¸å›½)","Esperanto"]
- }
-}
-```
-
-
-### **create_wallet**
-
-Create a new wallet. You need to have set the argument "--wallet-dir" when launching monero-wallet-rpc to make this work.
-
-Inputs:
-
-* *filename* - string;
-* *password* - string;
-* *language* - string; Language for your wallets' seed.
-
-Outputs: *None*.
-
-Example:
-
-```
-$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"create_wallet","params":{"filename":"mytestwallet","password":"mytestpassword","language":"English"}}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- }
-}
-```
-
-
-### **open_wallet**
-
-Open a wallet. You need to have set the argument "--wallet-dir" when launching monero-wallet-rpc to make this work.
-
-Inputs:
-
-* *filename* - string;
-* *password* - string;
-
-Outputs: *None*.
-
-Example:
-
-```
-$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"open_wallet","params":{"filename":"mytestwallet","password":"mytestpassword"}}' -H 'Content-Type: application/json'
-
-{
- "id": "0",
- "jsonrpc": "2.0",
- "result": {
- }
-}
-```
+{% tf resources/developer-guides/wallet-rpc.md %}
\ No newline at end of file
diff --git a/resources/moneropedia/address.md b/resources/moneropedia/address.md
index ed33f15a69c0969f7f85287f85caadf6e8e6c14d..0e62f86d68b6358b276d77fffeecd947ab2f92a4 100644
--- a/resources/moneropedia/address.md
+++ b/resources/moneropedia/address.md
@@ -9,9 +9,9 @@ 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 <span class="long-term">44AFFq5kSiGBoZ4NMDwYtN18obc8AemS33DBLWs3H7otXft3XjrpDtQGv7SqSsaBYBb98uNbr2VBBEt7f2wfn3RVGQBEP3A</span>.
-Because those addresses are long and complex you will often encounter an @OpenAlias address instead. For example, Monero donations can be sent to <span class="long-term">donate@getmonero.org</span> or <span class="long-term">donate.getmonero.org</span>.
+Because those addresses are long and complex, you will often encounter an @OpenAlias address instead. For example, Monero donations can be sent to <span class="long-term">donate@getmonero.org</span> or <span class="long-term">donate.getmonero.org</span>.
-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/blockchain.md b/resources/moneropedia/blockchain.md
index d20e8cf7753231002d833ad6c1e8f047cce365e3..3a2a9a213c9673636086acda7ec682ad6999c463 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. 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 08163292b111e745bf5cad98c7812f7e6f3ce992..7516cf94344c9732c282aac3e1a71d83bc392270 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.
+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/clearnet.md b/resources/moneropedia/clearnet.md
index 9200e69a48b0447cad2ba21cbbc085e5cc7af0ab..1ac9ec1968aa347db4e6aae2810755a8cb84eb32 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/cryptocurrency.md b/resources/moneropedia/cryptocurrency.md
index 45d736c217de532757e9cff5f7a33ddd20367ef5..9aa2831bfb9b8a42411cd680b7a923d95e166462 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/denominations.md b/resources/moneropedia/denominations.md
index 24bda2415ab2f79ad93f1ab59685842ca589ad44..e03c2ecdf042b851dc40b907c889a2367906d1af 100644
--- a/resources/moneropedia/denominations.md
+++ b/resources/moneropedia/denominations.md
@@ -2,12 +2,14 @@
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).
+{{ 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.
diff --git a/resources/moneropedia/destination.md b/resources/moneropedia/destination.md
index a999bebfba3fecd61acf623c719ce40a14b780a7..e7263f9a24ee4e75c161fe5d204a2e51139d5993 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/fluffyblocks.md b/resources/moneropedia/fluffyblocks.md
new file mode 100644
index 0000000000000000000000000000000000000000..36437ecb369c17db59f30ac3d319cc4ba946a9b0
--- /dev/null
+++ b/resources/moneropedia/fluffyblocks.md
@@ -0,0 +1,19 @@
+---
+layout: moneropedia
+entry: "Fluffy Blocks"
+terms: ["fluffy blocks", "fluffyblocks"]
+summary: "a way of saving bandwidth when sending new blocks around the network"
+---
+
+### The Basics
+
+A @block is made up of a header and @transactions. Fluffy Blocks only contain
+a header, a list of transaction indices, and any transactions that the node
+recieving the block may be missing. This saves bandwidth because nodes might
+already know about most or all of the transactions in the block and they don't
+need to be sent them again.
+
+### See Also
+
+* [BIP152 "Compact Block Relay"](https://github.com/bitcoin/bips/blob/master/bip-0152.mediawiki)
+* [Xthin](https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/release/doc/bu-xthin-protocol.md)
diff --git a/resources/moneropedia/fungibility.md b/resources/moneropedia/fungibility.md
index 47ca7d01e0f76ec37a736b3638a49e341e59b6f0..87bd683922907732ea5f32c85bead0d95919f508 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/garlic-routing.md b/resources/moneropedia/garlic-routing.md
index 55cd2122f0393c9a1b0d3e8559e7a709be21e5d6..a2afbacb6f142e6bdeaee4c6588fc703e7ecbf55 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/i2pcontrol.md b/resources/moneropedia/i2pcontrol.md
index 481d9eae6f086f719e8e57ab5651d2c039875069..285e130279573d5dbc5732e51581a7d5a825e83a 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/index.md b/resources/moneropedia/index.md
index 4489586c05835703abe0ed61bd85827a223a8986..fdece926efe07c1b5362516a0999cbf04f66830c 100644
--- a/resources/moneropedia/index.md
+++ b/resources/moneropedia/index.md
@@ -1,12 +1,6 @@
---
layout: full
-title: "Moneropedia"
-title-pre-kick: "Moneropedia - The "
-title-kick: "Monero Wiki"
-title-post-kick: ""
-kick-class: "softyellow-kicks"
-icon: "icon_wiki"
-attribution: "<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->"
+title: titles.moneropedia
---
diff --git a/resources/moneropedia/mining.md b/resources/moneropedia/mining.md
new file mode 100644
index 0000000000000000000000000000000000000000..5b73ba54083e151a3f040f3d71b1e668831f09cc
--- /dev/null
+++ b/resources/moneropedia/mining.md
@@ -0,0 +1,16 @@
+---
+layout: moneropedia
+entry: "Mining"
+terms: ["mining", "miner", "miners"]
+summary: "the process of cryptographically computing a mathematical proof for a block, containing a number of transactions, which is then added to the blockchain"
+---
+
+### The Basics
+
+{{ page.summary | capitalize }}.
+
+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.
diff --git a/resources/moneropedia/mnemonicseed.md b/resources/moneropedia/mnemonicseed.md
index 608f8d8bd28fc88dbdf27cc667856d95536f5506..4a1d80984e0b9b2a2d48272c04017f5193494c7e 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/node.md b/resources/moneropedia/node.md
index dde76903ff7400e62eb556a8b8faa7ec348825f0..9b5a68162e3f6c5846101fd535f73deb8f60c0e2 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/openalias.md b/resources/moneropedia/openalias.md
index 2410130cb910285cdf3ab0f02371d44cdd63183a..c2e68d7a818fa21829d891ddc5f3fcc5894b8ef9 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)
diff --git a/resources/moneropedia/paymentid.md b/resources/moneropedia/paymentid.md
index fba888fa972960f62a18a47dd5c0404f6cc21d37..bac6dc73eea9f91d1e0d9c3157174d5fddacb7cb 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 a7ff98bab804cd9a190ae9dcea0c77fe349f4631..e39a1215528ee621ea6c26a0a7e57af5f56f66a6 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. 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 77b9bf3297b0ad2eb2aae23896f6ed936799f792..a5f4c1aada863ba0c753bc7bafa218196b1baeb5 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 fee368c89b6b6f1be32b1edf6213fdd1c56b75b3..b10480df9d66510e4bef46f27806ed173e579065 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 c4f7a6d2e6af487b0dc8a7c205515539eb653f36..9145421ffea160f6854d1dad8ecee067b061459f 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/subscription.md b/resources/moneropedia/subscription.md
index b7411df5bec058a8baae7346e610cfe1f307501f..77e81ff5a63b7c12827ec67ced08d823897c4c6d 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/tail-emission.md b/resources/moneropedia/tail-emission.md
index 019e6fe14fef7e3ea22c02c1a9c995d7b3aa45a7..b5a9c6be6a73bf02c26ec68916f10b9c7985e99b 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 0064cb50bc7ead40d1fbfc398545cd6b8e1ccbf0..266428356d22e700f8a96bb4285e960b4a0d7fe4 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, 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 719a96b9943755f98cd661bacc25147cdd3a8957..ee2c1536c065a931de5317a13433bb427976b979 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.
diff --git a/resources/moneropedia/wallet.md b/resources/moneropedia/wallet.md
index 759b018d3d36a750800687d1e14266927a77092f..1641a2de3541ae1695409ddd1a91d145397c6673 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.
diff --git a/resources/people.md b/resources/people.md
deleted file mode 100644
index bc9250a541363dcb00527379965f970e2a453e77..0000000000000000000000000000000000000000
--- a/resources/people.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-layout: static_page
-title: "The People Behind Monero"
-title-pre-kick: "The "
-title-kick: "People Behind "
-title-post-kick: "Monero"
-kick-class: "kicks"
-icon: "icon_people"
-attribution: "<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->"
----
-
-### The Monero Core Team
-
-Monero is not governed by any foundation or central body, but ongoing development, maintenance, and research is primarily directed and often funded by a core team of seven individuals.
-
-Five members of the Core Team prefer to stay pseudonymous at this time, but two of them are more public and have revealed their real identities. For ease of reference those two members (Riccardo and Francisco) are at the top of the list below, but beyond that the list is presented in no particular order:
-
-- **Riccardo "fluffypony" Spagni** (*ric@getmonero.org* / [@fluffypony](https://twitter.com/fluffypony))**:** Based out of South Africa, Riccardo brings a strong business acumen and a deep understanding of cryptocurrency, software development, and cryptography to the table. He has been involved with cryptocurrency-related projects since 2012.
-- **Francisco "ArticMine" Cabañas** (*articmine@getmonero.org*)**:** Based in Canada, Francisco holds a PhD in Physics and brings extensive business and non-profit experience to the table. He has actively researched and invested in cryptocurrencies, since 2011, and focuses on the economic, social, regulatory and long-term viability aspects of cryptocurrencies.
-- **smooth** (*smooth@getmonero.org*)**:** A software developer, entrepreneur, and investor, smooth has been involved in several cryptocurrency projects since 2011, including development of the first multicurrency exchange (initially supporting Bitcoin and Namecoin). By virtue of his long-standing involvement in the cryptocurrency community, he is well known and trusted by many.
-- **othe** (*othe@getmonero.org*)**:** Based in Germany, othe has been interested in cryptocurrency since early 2011. Currently he works as an independent consultant for various cryptocurrency-related businesses. He is known for his previous work as a core Vertcoin developer.
-- **luigi1111** (*luigi1111@getmonero.org*)**:** Hailing from the Midwest, USA, luigi1111 is a sysadmin by day. He has been actively involved in several cryptocurrencies since 2013, and loves cryptography, probability, and English grammar.
-- **tacotime** (*tacotime@getmonero.org*)**:** A bioinformatics enthusiast and software developer from Toronto, tacotime has been involved in cryptocurrency since 2011. He is well known for his work on MC2, a hybrid PoS/PoW cryptocurrency, and his contributions to various Conformal projects such as btcd.
-- **NoodleDoodle** (*noodledoodle@getmonero.org*)**:** A former Silicon Valley engineer, NoodleDoodle is a seasoned hardware and software developer. He started his involvement with cryptocurrencies in 2012 and currently spends his time working on "cool aerospace stuff" for a university.
-
-### Development Contributors
-
-There have been many individuals that have contributed to the Monero Project; a complete list of which can be found on our [Github Contributors page](https://github.com/monero-project/bitmonero/graphs/contributors).
-
-Some that have made outstanding contributions include: [moneromooo](http://github.com/moneromooo-monero/bitmonero/branches), [Thomas Winget](https://github.com/tewinget), [Howard Chu](https://github.com/hyc), [mikezackles](https://github.com/mikezackles), [oranjuice](https://github.com/oranjuice), [warptangent](https://github.com/warptangent), [rfree](https://github.com/rfree2monero), [jakoblind](https://github.com/jakoblind), [tomerkon](https://github.com/tomerkon), and [anonimal (Kovri)](https://github.com/monero-project/kovri).
-
-### The Monero Research Lab
-
-The Core Team forms an integral part of the Monero Research Lab, but the researchers, scientists, and academics that are primarily focused on Monero research are listed below. They have chosen to remain pseudonymous for the moment. They are:
-
-- **Surae Noether:** Lead researcher for the Monero Research Lab, Surae holds a PhD in Mathematical Sciences and brings a rich understanding of cryptography and homological algebra to the mix.
-- **Sarang Noether:** Having completed his Masters in Mathematical Sciences, Sarang is currently completing his doctoral degree in Physics, while devoting time on the side to the advancement of Monero research.
-- **Shen Noether (previously)** A graduate student focused on algebraic geometry.
-
-### Other Contributors
-
-There have been massive contributions to Monero from its inception from so many people, including: zone117x, LucasJones, wolf`, Professor David Andersen, wallet42, Neozaru, Gingeropolous, cAPSLOCK, and many, many others.
diff --git a/resources/projects.md b/resources/projects.md
deleted file mode 100644
index ae743ed118a442546ba5c8371a2a183478ebdfa1..0000000000000000000000000000000000000000
--- a/resources/projects.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-layout: static_page
-title: "External Projects"
-title-pre-kick: "External "
-title-kick: "Projects"
-title-post-kick: ""
-kick-class: "yellow-kicks"
-icon: "icon_projects"
-attribution: "<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->"
----
-
-### Crypto-Kingdom
-A MMORPG with a real-world economy with monero as native currency. You can make trades, start an in-game company or develop real estate on your path to becoming a land baron. And when you're done building your empire, you can sit back, pour a beer and chat with your friends. It's Second Life, Wall Street and social networking rolled into one game.
-Visit [http://cryptokingdom.me](http://cryptokingdom.me), [Bitcointalk](https://bitcointalk.org/index.php?topic=819073.0) and [Reddit](https://www.reddit.com/r/cryptokingdom) for more info.
-
-### Monerodice
-A Monero gambling site.
-Visit [http://www.monerodice.net](http://www.monerodice.net) for more info.
-
-### XMR.TO
-A website designed to pay any BTC address using monero.
-Visit [http://www.xmr.to](http://www.xmr.to) for more info.
-
-
-
-
diff --git a/resources/protocol_explanation.md b/resources/protocol_explanation.md
deleted file mode 100644
index 40807a82f0340002d2cd60ae11d125f3f39ce606..0000000000000000000000000000000000000000
--- a/resources/protocol_explanation.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-layout: static_page
-title: "Protocol Explanation"
-title-pre-kick: "Protocol "
-title-kick: "Explanation"
-title-post-kick: ""
-kick-class: "kicks"
-icon: "icon_about"
-attribution: "<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->"
----
-
-(insert that protocol image here)
-
-### Bob wants to spend XMR he received in his account and send it to Carol.
-
-#### How is the transaction made?
-
-A: Bob gets access to his "real input" that was send to his "stealth address"
-
-1. Bob needs the public key from the transaction that contains the output he received and wants to send - Bob needs to @ECDH this key with his private view key.
-2. Bob also selects the exact number of the output from the transaction that contains the output he wants to send. The other output(s) in this transaction is/are change (Bob doesn't have the private key for those other outputs) Note: typically, due to @auto-denomination, Bob will have more than one output per transaction that belongs to him.
-3. Bob needs the "master" private key of his account - private spend key, to be precise.
-4. Points A 1,2 and 3 are used to calculate the private key for the specific output he wants to send. (the public key for the transaction can be calculated from this private key - This is correct, but the public key is also stored on the blockchain.)
-
-B: To protects Carol's identity, Bob will do the following to generate a "one time" public key for this transaction, making it impossible for others to link all transactions send to Carol to the same "stealth address"
-
-1. Bob generates a random number scalar, this one isn't clear from the graphic at all.
-2. This random number is hashed into the transaction public key the transaction private key, and is scalar mult'd into the transaction public key.
-3. He selects the number associated with the outputs (due to auto-denom) that Carol will receive, the other output(s) is/are change that goes back to Bob.
-4. He needs the "master" public key from Carol to be able to send it to her stealth address - Carol's public view key.
-5. Points B 2,3 and 4 are used to calculate the public key for the specific outputs he wants to send.
-
-C: to "mix" the inputs, Bob creates a ring signature
-
-1. He selects the actual public key (+ that output's private key) from the output he wants to send, but he also adds other public keys into the mix.
-2. To prevent double spending, Bob needs to send a valid "key image" together with the public keys of the outputs (or inputs if you prefer).
-3. He signs the combination of inputs and the key image with his private key, proving the key image is valid (Bob owns the private key associated with the key image) and that (somehow? I don't know how this works) one of the public keys is used to generate this key image, but as a spectator of the blockchain, we can't know which of the used outputs is "the real one that is being transferred". His private key and the other chosen public key(s) are used to create a ring signature; they'll be one signature for each input, collectively making a ring signature. The key image is an additional public key computed from the output private key (not public key) that's actually being spent.
-4. This is the collection of outputs that is signed. He grabbed the "fake ones" from the blockchain. He doesn't need permission from the owners for that. This isn't quite right: those are the outputs that are doing the signing. A hash of the TX prefix is "what" is actually being signed.
-5. This is the key image he signed. If Bob ever tries to send the same output again, the exact same key image will be generated and thus the double spend will be detected.
-6. This "ring signature" is added to the transaction containing the public keys that are used in the transaction and proving Bob's ownership of one of those inputs.
diff --git a/resources/research-lab/index.md b/resources/research-lab/index.md
index 1ba20b034a950ce90a25adb0884945eebf549c58..4bd24dc46e918ffde74231b08ddbe5f0f4408626 100644
--- a/resources/research-lab/index.md
+++ b/resources/research-lab/index.md
@@ -1,167 +1,6 @@
---
layout: custom
-title: "Monero Research Lab"
+title: titles.researchlab
+permalink: /resources/research-lab/index.html
---
-<div class="container description">
-<p>Monero is not only committed to making a fungible currency, but also to continued research into the realm of financial privacy as it involves cryptocurrencies. Below you'll find the work of our very own Monero Research Lab, with more papers to come.</p>
-</div>
-
-<section class="container">
- <div class="row">
- <!-- left two-thirds block-->
- <div class="left two-thirds col-lg-8 col-md-8 col-sm-12 col-xs-12">
- <div class="info-block research-paper">
- <div class="row center-xs">
- <div class="col"><h2>Monero Research Lab Papers</h2></div>
- </div>
- <div class="tab">
- <input id="tab-one" type="checkbox" name="tabs" class="accordion" checked="checked">
- <label for="tab-one" class="accordion">MRL-0001: A Note on Chain Reactions in Traceability in CryptoNote 2.0</label>
- <div class="tab-content">
- <p><strong>Abstract:</strong> This research bulletin describes a plausible attack on a ring-signature based
- anonymity system. We use as motivation the cryptocurrency protocol CryptoNote
- 2.0 ostensibly published by Nicolas van Saberhagen in 2012. It has been
- previously demonstrated that the untraceability obscuring a one-time key pair can
- be dependent upon the untraceability of all of the keys used in composing that
- ring signature. This allows for the possibility of chain reactions in traceability
- between ring signatures, causing a critical loss in untraceability across the whole
- network if parameters are poorly chosen and if an attacker owns a sufficient
- percentage of the network. The signatures are still one-time, however, and any
- such attack will still not necessarily violate the anonymity of users. However, such
- an attack could plausibly weaken the resistance CryptoNote demonstrates against
- blockchain analysis. This research bulletin has not undergone peer review, and
- reflects only the results of internal investigation.
- <br>
- <br>
- <a target="_blank" rel="noreferrer noopener" href="https://lab.getmonero.org/pubs/MRL-0001.pdf">Read Paper</a>
- </p>
- </div>
- </div>
- <div class="tab">
- <input id="tab-two" type="checkbox" name="tabs" class="accordion">
- <label for="tab-two" class="accordion">MRL-0002: Counterfeiting via Merkle Tree Exploits within Virtual Currencies Employing the CryptoNote Protocol</label>
- <div class="tab-content">
- <p><strong>Abstract:</strong> On 4 September 2014, an unusual and novel attack was executed against the
- Monero cryptocurrency network. This attack partitioned the network into two
- distinct subsets which refused to accept the legitimacy of the other subset. This
- had myriad effects, not all of which are yet known. The attacker had a short
- window of time during which a sort of counterfeiting could occur, for example.
- This research bulletin describes deficiencies in the CryptoNote reference code
- allowing for this attack, describes the solution initially put forth by Rafal Freeman
- from Tigusoft.pl and subsequently by the CryptoNote team, describes the current
- fix in the Monero code base, and elaborates upon exactly what the offending
- block did to the network. This research bulletin has not undergone peer review,
- and reflects only the results of internal investigation.<br>
- <br>
- <a target="_blank" rel="noreferrer noopener" href="https://lab.getmonero.org/pubs/MRL-0002.pdf">Read Paper</a></p>
-
- </div>
- </div>
- <div class="tab">
- <input id="tab-three" type="checkbox" name="tabs" class="accordion">
- <label for="tab-three" class="accordion">MRL-0003: Monero is Not That Mysterious</label>
- <div class="tab-content">
- <p><strong>Introduction:</strong> Recently, there have been some vague fears about the CryptoNote source code and
- protocol floating around the internet based on the fact that it is a more complicated
- protocol than, for instance, Bitcoin. The purpose of this note is to try and clear
- up some misconceptions, and hopefully remove some of the mystery surrounding
- Monero Ring Signatures. I will start by comparing the mathematics involved in
- CryptoNote ring signatures (as described in [CN]) to the mathematics in [FS], on
- which CryptoNote is based. After this, I will compare the mathematics of the ring
- signature to what is actually in the CryptoNote codebase.<br>
- <br>
- <a target="_blank" rel="noreferrer noopener" href="https://lab.getmonero.org/pubs/MRL-0003.pdf">Read Paper</a></p>
- </div>
- </div>
- <div class="tab">
- <input id="tab-four" type="checkbox" name="tabs" class="accordion">
- <label for="tab-four" class="accordion">MRL-0004: Improving Obfuscation in the CryptoNote Protocol</label>
- <div class="tab-content">
- <p><strong>Abstract:</strong> We identify several blockchain analysis attacks available to degrade the
-untraceability of the CryptoNote 2.0 protocol. We analyze possible solutions,
-discuss the relative merits and drawbacks to those solutions, and recommend
-improvements to the Monero protocol that will hopefully provide long-term
-resistance of the cryptocurrency against blockchain analysis. Our recommended
-improvements to Monero include a protocol-level network-wide minimum mix-in
-policy of
-n
-= 2
-foreign outputs per ring signature, a protocol-level increase of this
-value to
-n
-= 4
-after two years, and a wallet-level default value of
-n
-= 4
-in the
-interim. We also recommend a torrent-style method of sending Monero output.
-We also discuss a non-uniform, age-dependent mix-in selection method to
-mitigate the other forms of blockchain analysis identified herein, but we make no
-formal recommendations on implementation for a variety of reasons. The
-ramifications following these improvements are also discussed in some detail.
-This research bulletin has not undergone peer review, and reflects only the
-results of internal investigation.<br>
- <br>
- <a target="_blank" rel="noreferrer noopener" href="https://lab.getmonero.org/pubs/MRL-0004.pdf">Read Paper</a></p>
- </div>
- </div>
- <div class="tab">
- <input id="tab-five" type="checkbox" name="tabs" class="accordion">
- <label for="tab-five" class="accordion">MRL-0005: Ring Signature Confidential Transactions</label>
- <div class="tab-content">
- <p><strong>Abstract:</strong> This article introduces a method of hiding transaction amounts in the strongly
-decentralized anonymous cryptocurrency Monero. Similar to Bitcoin, Monero is a
-cryptocurrency which is distributed through a proof of work “mining†process.
-The original Monero protocol was based on CryptoNote, which uses ring
-signatures and one-time keys to hide the destination and origin of transactions.
-Recently the technique of using a commitment scheme to hide the amount of a
-transaction has been discussed and implemented by Bitcoin Core Developer
-Gregory Maxwell. In this article, a new type of ring signature, A Multi-layered
-Linkable Spontaneous Anonymous Group signature is described which allows for
-hidden amounts, origins and destinations of transactions with reasonable
-efficiency and verifiable, trustless coin generation. Some extensions of the
-protocol are provided, such as Aggregate Schnorr Range Proofs, and Ring
-Multisignature. The author would like to note that early drafts of this were
-publicized in the Monero Community and on the bitcoin research irc channel.
-Blockchain hashed drafts are available in [14] showing that this work was started
-in Summer 2015, and completed in early October 2015. An eprint is also
-available at
-http://eprint.iacr.org/2015/1098
-.<br>
- <br>
- <a href="https://lab.getmonero.org/pubs/MRL-0005.pdf" target="_blank" rel="noreferrer noopener">Read Paper</a></p>
- </div>
- </div>
- </div>
- </div>
- <!-- end left two-thirds block-->
-
- <!-- right one-third block-->
- <div class="right one-third col-lg-4 col-md-4 col-sm-12 col-xs-12">
- <div class="info-block">
- <div class="row center-xs">
- <div class="col">
- <h2>Cryptonote Whitepapers</h2>
- </div>
-
- </div>
-<div markdown="1">
-
-[Cryptonote Whitepaper](https://cryptonote.org/whitepaper.pdf)
-
-This is the original cryptonote paper written by the cryptonote team. Reading it will give an understanding about how the cryptonote algorithm works in general.
-
-[Annotated Whitepaper](https://downloads.getmonero.org/whitepaper_annotated.pdf)
-
-The Monero Research Lab released an annotated version of the cryptonote whitepaper. This is sort of like an informal review of the claims that are made line-by-line of the whitepaper. It also explains some of the harder concepts in relatively easy to understand terms.
-
-[Brandon Goodell's Whitepaper Review](https://downloads.getmonero.org/whitepaper_review.pdf)
-
-This paper is a formal review of the original cryptonote paper by MRL researcher Brandon Goodell. He takes an in-depth look at the claims and mathematics presented in the cryptonote paper.
-
-</div>
- </div>
- </div>
- <!-- end right one-third block-->
- </div>
-</section>
+{% tf resources/research-lab.md %}
\ No newline at end of file
diff --git a/resources/roadmap/index.md b/resources/roadmap/index.md
index b768d9ac4a0249706fad5d87cc4978c88b32019c..b961868957e54da652cf6b46865b37456e3ef627 100644
--- a/resources/roadmap/index.md
+++ b/resources/roadmap/index.md
@@ -1,147 +1,6 @@
---
layout: custom
-title: Roadmap
+title: titles.roadmap
+permalink: /resources/roadmap/index.html
---
-<div class="roadmap">
-<div class="text-center pre-roadmap container">
- <div class="row">
- <div class="col-xs-4">
- <li class="completed"></li>
- <p>Completed task</p>
- </div>
- <div class="col-xs-4">
- <li class="ongoing"></li>
- <p>Ongoing task</p>
- </div>
- <div class="col-xs-4">
- <li class="upcoming"></li>
- <p>Upcoming task</p>
- </div>
- </div>
-</div>
-<section class="container">
- <div class="row">
- <div class="col-lg-12 col-md-12 col-sm-12 col-xs-12">
- <div class="tabPanel-widget">
- <label for="tab-1" tabindex="0"></label>
- <input id="tab-1" type="radio" name="tabs" aria-hidden="true">
- <h2>2014</h2>
- <div class="tabPanel-content">
- {% for toplevel in site.data.roadmap %}
- {% if toplevel.year == 2014 %}
- {% for roadlist in toplevel.accomplishments %}
- <div class="row start-xs middle-xs">
- <div class="col-xs-1">
- <span class="{{roadlist.status}}"></span>
- </div>
- <div class="col-xs-11">
- <p>{{roadlist.date}}: {{roadlist.name}}</p>
- </div>
- </div>
- {%endfor%}
- {%endif%}
- {%endfor%}
- </div>
- <label for="tab-2" tabindex="0"></label>
- <input id="tab-2" type="radio" name="tabs" aria-hidden="true">
- <h2>2015</h2>
- <div class="tabPanel-content">
- {% for toplevel in site.data.roadmap %}
-
- {% if toplevel.year == 2015 %}
- {% for roadlist in toplevel.accomplishments %}
- <div class="row start-xs middle-xs">
- <div class="col-xs-1">
- <span class="{{roadlist.status}}"></span>
- </div>
- <div class="col-xs-11">
- <p>{{roadlist.date}}: {{roadlist.name}}</p>
- </div>
- </div>
-
- {%endfor%}
- {%endif%}
-
- {%endfor%}
- </div>
- <label for="tab-3" tabindex="0"></label>
- <input id="tab-3" type="radio" name="tabs" aria-hidden="true">
- <h2>2016</h2>
- <div class="tabPanel-content">
- {% for toplevel in site.data.roadmap %}
-
- {% if toplevel.year == 2016 %}
- {% for roadlist in toplevel.accomplishments %}
- <div class="row start-xs middle-xs">
- <div class="col-xs-1">
- <span class="{{roadlist.status}}"></span>
- </div>
- <div class="col-xs-11">
- <p>{{roadlist.date}}: {{roadlist.name}}</p>
- </div>
- </div>
-
- {%endfor%}
- {%endif%}
-
- {%endfor%}
- </div>
- <label for="tab-4" tabindex="0"></label>
- <input id="tab-4" type="radio" name="tabs" aria-hidden="true" checked>
- <h2>2017</h2>
- <div class="tabPanel-content">
- {% for toplevel in site.data.roadmap %}
-
- {% if toplevel.year == 2017 %}
- {% for roadlist in toplevel.accomplishments %}
- <div class="row start-xs middle-xs">
- <div class="col-xs-1">
- <span class="{{roadlist.status}}"></span>
- </div>
- <div class="col-xs-11">
- {% if roadlist.date %}
- <p>{{roadlist.date}}: {{roadlist.name}}</p>
- {%else%}
- <p>{{roadlist.name}}</p>
- {%endif%}
- </div>
- </div>
-
- {%endfor%}
- {%endif%}
-
- {%endfor%}
- </div>
- <label for="tab-5" tabindex="0"></label>
- <input id="tab-5" type="radio" name="tabs" aria-hidden="true">
- <h2>Future</h2>
- <div class="tabPanel-content">
- {% for toplevel in site.data.roadmap %}
-
- {% if toplevel.year == 2018 %}
- {% for roadlist in toplevel.accomplishments %}
- <div class="row start-xs">
- <div class="col-xs-1">
- <span class="{{roadlist.status}}"></span>
- </div>
- <div class="col-xs-11">
- {% if roadlist.date %}
- <p>{{roadlist.date}}: {{roadlist.name}}</p>
- {%else%}
- <p>{{roadlist.name}}</p>
- {%endif%}
- </div>
- </div>
-
- {%endfor%}
- {%endif%}
-
- {%endfor%}
- </div>
- </div>
- </div>
- </div>
-</section>
-
-
-</div>
\ No newline at end of file
+{% tf resources/roadmap.md %}
\ No newline at end of file
diff --git a/resources/user-guides/Offline_Backup.md b/resources/user-guides/Offline_Backup.md
index 73669dd24f8d3920982686a67a58cf2bb86df056..307cacecd7952a9131ffacb526af3ccd4178d0be 100644
--- a/resources/user-guides/Offline_Backup.md
+++ b/resources/user-guides/Offline_Backup.md
@@ -1,47 +1,7 @@
---
-layout: static_page
+layout: user-guide
title: "Creating an Offline Backup of your Monero Account"
-title-pre-kick: "Creating an Offline Backup "
-title-kick: "of your Monero "
-title-post-kick: "Account"
-kick-class: "purple-kicks"
-icon: "icon_userguides"
-attribution: "<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->"
+permalink: /resources/user-guides/Offline_Backup.html
---
-## Operating Systems: Various versions of Linux and Windows 7, 8
-
-### Wallet Software: Simplewallet
-
-#### Resource for Creating Bootable Disks: [Linux](http://www.pendrivelinux.com/), [Windows](https://www.microsoft.com/en-us/download/windows-usb-dvd-download-tool)
-
-#### Resource for Monero Binaries: [Monero Binaries](https://getmonero.org/downloads/)
-
-- Take any computer you have lying around, even your normal workstation. You may find it easier to use an older computer that has no wifi or bluetooth if you're particularly paranoid
-
-- Create a Linux or Windows bootable disk, and make sure you have the Monero binaries on the same disk or on a second disk (for Linux make sure you have also downloaded copies of the dependencies you will need, libboost1.55 and miniupnpc for instance)
-
-- Disconnect the network and/or Internet cables from your computer, physically remove the wifi card or switch the wifi/bluetooth off on a laptop if possible
-
-- Boot into your bootable OS, install the dependencies if necessary
-
-- Copy the Monero binaries to a RAM disk (/dev/shm in Linux, Windows bootable ISOs normally have a Z: drive or something)
-
-- Don't run the Monero daemon. Instead, using the command line, use monero-wallet-cli to create a new Monero @account
-
-- When prompted for a name, give it any name, it doesn't really matter
-
-- When prompted for a password, type in like 50 - 100 random characters. Don't worry that you don't know the password, just make it LONG
-
-- **CRITICAL STEP**: Write down (on paper) your 25 word @mnemonic-seed
-**WARNING**: If you forget to write down this information your funds may be lost forever
-
-- Write down (on your phone, on paper, on another computer, wherever you want) your address and view key
-
-- Switch off the computer, remove the battery if there is one, and leave it physically off for a few hours
-
-The account you've created was created in RAM, and the digital files are now inaccessible. If some adversary manages to somehow obtain the data, they will lack the long password to open it. If you need to receive payments, you have your public address, and you have the view key if needed. If you need access to it, you have your 25 word @mnemonic-seed, and you can now write out several copies of it, including an offsite copy (e.g. a bank deposit box).
-
-Credit: Riccardo Spagni
-
-Related: [Offline Account Generator](http://moneroaddress.org/)
+{% tf resources/user-guides/Offline_Backup.md %}
\ No newline at end of file
diff --git a/resources/user-guides/cli_wallet_daemon_isolation_qubes_whonix.md b/resources/user-guides/cli_wallet_daemon_isolation_qubes_whonix.md
index 5497cd26fd4f15dba5313393140fa27a1eea22a1..2342db02dc7534da1ee678e68896507ee6382aff 100644
--- a/resources/user-guides/cli_wallet_daemon_isolation_qubes_whonix.md
+++ b/resources/user-guides/cli_wallet_daemon_isolation_qubes_whonix.md
@@ -1,152 +1,7 @@
---
layout: static_page
title: CLI Wallet/Daemon Isolation with Qubes + Whonix
+permalink: /resources/user-guides/cli_wallet_daemon_isolation_qubes_whonix.html
---
-With [Qubes](https://qubes-os.org) + [Whonix](https://whonix.org) you can have a Monero wallet that is without networking and running on a virtually isolated system from the Monero daemon which has all of its traffic forced over [Tor](https://torproject.org).
-
-Qubes gives the flexibility to easily create separate VMs for different purposes. First you will create a Whonix workstation for the wallet with no networking. Next, another Whonix workstation for the daemon which will use your Whonix gateway as it's NetVM. For communication between the wallet and daemon you can make use of Qubes [qrexec](https://www.qubes-os.org/doc/qrexec3/).
-
-This is safer than other approaches which route the wallets rpc over a Tor hidden service, or that use physical isolation but still have networking to connect to the daemon. In this way you don't need any network connection on the wallet, you preserve resources of the Tor network, and there is less latency.
-
-
-## 1. [Create Whonix AppVMs](https://www.whonix.org/wiki/Qubes/Install):
-
-+ Using a Whonix workstation template, create two workstations as follows:
-
- - The first workstation will be used for your wallet, it will referred to as `monero-wallet-ws`. You will have `NetVM` set to `none`.
-
- - The second workstation will be for the `monerod` daemon, it will be referred to as `monerod-ws`. You will have `NetVM` set to the Whonix gateway `sys-whonix`.
-
-## 2. In the AppVM `monerod-ws`:
-
-+ Download, verify, and install Monero software.
-
-```
-user@host:~$ curl -O "https://downloads.getmonero.org/cli/monero-linux-x64-v0.11.1.0.tar.bz2" -O "https://getmonero.org/downloads/hashes.txt"
-user@host:~$ gpg --recv-keys BDA6BD7042B721C467A9759D7455C5E3C0CDCEB9
-user@host:~$ gpg --verify hashes.txt
-gpg: Signature made Wed 01 Nov 2017 10:01:41 AM UTC
-gpg: using RSA key 0x55432DF31CCD4FCD
-gpg: Good signature from "Riccardo Spagni <ric@spagni.net>" [unknown]
-gpg: WARNING: This key is not certified with a trusted signature!
-gpg: There is no indication that the signature belongs to the owner.
-Primary key fingerprint: BDA6 BD70 42B7 21C4 67A9 759D 7455 C5E3 C0CD CEB9
- Subkey fingerprint: 94B7 38DD 3501 32F5 ACBE EA1D 5543 2DF3 1CCD 4FCD
-user@host:~$ echo '6581506f8a030d8d50b38744ba7144f2765c9028d18d990beb316e13655ab248 monero-linux-x64-v0.11.1.0.tar.bz2' | shasum -c
-monero-linux-x64-v0.11.1.0.tar.bz2: OK
-user@host:~$ tar xf monero-linux-x64-v0.11.1.0.tar.bz2
-user@host:~$ sudo cp monero-v0.11.1.0/monerod /usr/local/bin/
-```
-+ Create a `systemd` file.
-
-```
-user@host:~$ sudo gedit /home/user/monerod.service
-```
-
-Paste the following contents:
-
-```
-[Unit]
-Description=Monero Full Node
-After=network.target
-
-[Service]
-User=user
-Group=user
-
-Type=forking
-PIDFile=/home/user/.bitmonero/monerod.pid
-
-ExecStart=/usr/local/bin/monerod --detach --data-dir=/home/user/.bitmonero \
- --no-igd --pidfile=/home/user/.bitmonero/monerod.pid \
- --log-file=/home/user/.bitmonero/bitmonero.log --p2p-bind-ip=127.0.0.1
-
-Restart=always
-PrivateTmp=true
-
-[Install]
-WantedBy=multi-user.target
-```
-
-+ Copy `monero-wallet-cli` executable to the `monero-wallet-ws` VM.
-
-```
-user@host:~$ qvm-copy-to-vm monero-wallet-ws monero-v0.11.1.0/monero-wallet-cli
-```
-
-+ Make `monerod` daemon run on startup by editing the file `/rw/config/rc.local`.
-
-```
-user@host:~$ sudo gedit /rw/config/rc.local
-```
-
-Add these lines to the bottom:
-
-```
-cp /home/user/monerod.service /lib/systemd/system/
-systemctl start monerod.service
-```
-
-Make file executable.
-
-```
-user@host:~$ sudo chmod +x /rw/config/rc.local
-```
-
-+ Create rpc action file.
-
-```
-user@host:~$ sudo mkdir /rw/usrlocal/etc/qubes-rpc
-user@host:~$ sudo gedit /rw/usrlocal/etc/qubes-rpc/user.monerod
-```
-
-Add this line:
-
-```
-socat STDIO TCP:localhost:18081
-```
-
-+ Shutdown `monerod-ws`.
-
-## 3. In the AppVM `monero-wallet-ws`:
-
-+ Move the `monero-wallet-cli` executable.
-
-```
-user@host:~$ sudo mv QubesIncoming/monerod-ws/monero-wallet-cli /usr/local/bin/
-```
-
-+ Edit the file `/rw/config/rc.local`.
-
-```
-user@host:~$ sudo gedit /rw/config/rc.local
-```
-
-Add the following line to the bottom:
-
-```
-socat TCP-LISTEN:18081,fork,bind=127.0.0.1 EXEC:"qrexec-client-vm monerod-ws user.monerod"
-```
-
-Make file executable.
-
-```
-user@host:~$ sudo chmod +x /rw/config/rc.local
-```
-
-+ Shutdown `monero-wallet-ws`.
-
-## 4. In `dom0`:
-
-+ Create the file `/etc/qubes-rpc/policy/user.monerod`:
-
-```
-[user@dom0 ~]$ sudo nano /etc/qubes-rpc/policy/user.monerod
-```
-
-Add the following line:
-
-```
-monero-wallet-ws monerod-ws allow
-```
+{% tf resources/user-guides/cli_wallet_daemon_isolation_qubes_whonix.md %}
diff --git a/resources/user-guides/create_wallet.md b/resources/user-guides/create_wallet.md
index fc61a0b01fdf4f174c42e5a65099bf74e7124534..dc717e3befd4b4bda2b952e735f50992b2b24cb4 100644
--- a/resources/user-guides/create_wallet.md
+++ b/resources/user-guides/create_wallet.md
@@ -1,71 +1,7 @@
---
-layout: static_page
+layout: user-guide
title: "Creating a Monero wallet"
-title-pre-kick: "Creating a Monero wallet "
-title-kick: "on Ubuntu "
-title-post-kick: ""
-kick-class: "purple-kicks"
-icon: "icon_userguides"
-attribution: "<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->"
+permalink: /resources/user-guides/create_wallet.html
---
-### Operating Systems: Ubuntu
-
-- Download the [official binaries](https://getmonero.org/downloads/) or compile the last source available on [Github](https://github.com/monero-project/bitmonero)
-
-
-
-
-- Extract the files with the archive manager (same as Winzip on Windows). Note the path where the files "monerod" and "monero-wallet-cli" are
-
-
-
-
-- You only need to do this step once : open a terminal (ctrl+alt+t) and install the required dependencies by typing : "*sudo apt-get install libboost-all-dev libssl-dev libevent-dev libdb++-dev*". When asked, press the Y key and then Enter to continue
-
-
-
-
-- Open a terminal and load the path where your binaries are extracted (cf. step 2) by typing : "*cd yourPathFromStep2*"
-
-
-
-- Load monerod by typing in your terminal : "*./monerod*". Wait for the synchronization with the network (monerod is updating the blockchain you have downloaded in step 4 or is downloading it from scratch). This can take a lot of time the first time, so be patient
-
-
-
-
-
-
-- Once monerod is synchronized with the network, open a new terminal, change the directory (cf. step 5), and launch monero-wallet-cli by typing "*./monero-wallet-cli*"
-
-
-
-- Enter the name you want for your portfolio and follow the instructions from the terminal
-
-
-
-
-
-
-*This is your private key. Write it down and keep it in a safe place!*
-
-
-
-*This is your view key. You need it to create a view only wallet (cf. associated user guide)*
-
-
-
-*This is the address of your wallet*
-
-
-
-
-
-
-
-- To exit monerod or monero-wallet-cli just type "*exit*" in the associated terminal
-
-Now to access the portfolio you have just created you will have to launch monerod, wait for it to be synchronized with the network, launch monero-wallet-cli, and type the name of your portfolio and your password.
-
-
+{% tf resources/user-guides/create_wallet.md %}
\ No newline at end of file
diff --git a/resources/user-guides/easiest_buy.md b/resources/user-guides/easiest_buy.md
index 02c0f660d90cf0d2ddeb71f04d88b829ab8673d5..6d4b32f63d53fa95b24323b6c33e7ec1a51cf55c 100644
--- a/resources/user-guides/easiest_buy.md
+++ b/resources/user-guides/easiest_buy.md
@@ -1,75 +1,7 @@
---
-layout: static_page
+layout: user-guide
title: "Easiest way to buy Monero"
-title-pre-kick: "Easiest way"
-title-kick: "to buy Monero"
-title-post-kick: ""
-kick-class: "purple-kicks"
-icon: "icon_userguides"
-attribution: "<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->"
+permalink: /resources/user-guides/easiest_buy.html
---
-## How to obtain Monero
-
-This is a guide to obtain your own Monero as of 20150919. This is perhaps the easiest way to purchase and hold Monero.
-
-####Step 1: Buy Bitcoin
-
-There are many ways to buy Bitcoin. Perhaps the easiest way is through circle.com. Once you have purchased some Bitcoin, you are ready to buy some Monero! Buying Bitcoin is straightforward. Please goto circle.com and just follow the instructions there.
-
-####Step 2: Set up a mymonero.com account
-
-MyMonero.com is an online wallet for Monero, maintained by Monero Core Developer Ricardo Spagni (fluffpony). It is the easiest wallet to use. Simply go to MyMonero.com and click on the "Create an Account" button.
-
-
-
-After clicking the button, you will see your private key. This key is what gives you access to your funds. Never share this key with anyone!
-
-### WRITE DOWN THIS KEY IMMEDIATELY!
-
-
-
-Type in your private key in the box below, and click the button.
-
-On the next page, you will see your address.
-
-
-
-Copy your address to the clipboard by highlighting the whole thing and hitting ctrl+c (or edit menu, copy), or clicking the little icon next to your address. Save your address somewhere. This is how others will send Monero to you, and what you will use to deposit Monero into your account!
-
-#### Step 3: Buy Monero and transfer the Monero to your new address
-
-Go to www.shapeshift.io . On the righthand side, of the screen, click icon under "Receive" to select Monero.
-
-
-
-
-Paste your address into the field under the Monero logo. Select the "agree to terms" button, then hit "Start"
-
-
-
-In the new screen that pops up, copy the Deposit Address into your clipboard (select and hit ctrl+c or edit-copy)
-
-
-
-Go back to your circle.com page, hit the "transfer" button, and paste the Bitcoin address into the field
-Enter the amount of Bitcoin you would like to spend.
-
-
-
-
-You will get a text message verification code. Enter code and hit send.
-
-
-
-You will see the shapeshift change to "awaiting exchange"
-
-
-
-Then it will change to COMPLETE!
-
-
-
-After a while you will see it in your Monero account
-
-
+{% tf resources/user-guides/easiest_buy.md %}
\ No newline at end of file
diff --git a/resources/user-guides/howto_fix_stuck_funds.md b/resources/user-guides/howto_fix_stuck_funds.md
index b25165f45f3d16d85a10f4cc55d27b22259f52a0..d07c2839bf8e9e53f4967f2365679ec396c0da2c 100644
--- a/resources/user-guides/howto_fix_stuck_funds.md
+++ b/resources/user-guides/howto_fix_stuck_funds.md
@@ -1,41 +1,7 @@
---
-layout: static_page
+layout: user-guide
title: "How to fix stuck funds"
-title-pre-kick: "Fix "
-title-kick: "Stuck funds"
-title-post-kick: ""
-kick-class: "kicks"
-icon: "icon_about"
-attribution: "<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->"
+permalink: /resources/user-guides/howto_fix_stuck_funds.html
---
-Sometimes, your funds will become stuck - you will have some locked funds that never become unlocked. This is how you fix it.
-
-- Load your wallet in monero-wallet-cli.
-
-- Type
-
-> seed
-
-into the command prompt. Write down your 25 word seed, if you haven't already. This is the best way to make sure you don't loose access to your funds.
-
-- Close monero-wallet-cli by typing
-
-> exit
-
-- Backup all of your wallet related files. These include:
-
-> yourwalletname.bin
-> yourwalletname.bin.keys
-> yourwalletname.bin.address.txt
-
-This can be done by copying the files to a new folder.
-
-Sometimes, when creating your wallet, you might have named it something without the .bin part. In that case, the wallet file will be called yourwalletname without the .bin at the end.
-
-- Delete yourwallet.bin
-
-- Load monero-wallet-cli, type in the name of the wallet you just deleted
-
-- Enter password. The wallet will now refresh and hopefully your locked funds will now become unlocked.
-
+{% tf resources/user-guides/howto_fix_stuck_funds.md %}
\ No newline at end of file
diff --git a/resources/user-guides/importing_blockchain.md b/resources/user-guides/importing_blockchain.md
index 3396a690804ad580936f55f42673a7e19e3d342c..41c6d0b2589c2527493ead60dffe26d5bd3b5ed3 100644
--- a/resources/user-guides/importing_blockchain.md
+++ b/resources/user-guides/importing_blockchain.md
@@ -1,61 +1,7 @@
---
-layout: static_page
-title: Importing the Monero Blockchain from an outside source
+layout: user-guide
+title: Importing the Monero Blockchain from an outside source
+permalink: /resources/user-guides/importing_blockchain.html
---
-# Importing the Blockchain to Monero GUI wallet (Windows)
-
-### Step 1
-
-Download the Current bootstrap from https://downloads.getmonero.org/blockchain.raw; you can skip this step if you are importing the Blockchain from another source.
-
-### Step 2
-
-Find the path of your Monero wallet (the folder where you extracted your wallet). For example mine is:
-
-`D:\monero-gui-0.10.3.1`
-
-Your path may be different depending on where you decided to download your wallet and what version of the Monero wallet you have.
-
-### Step 3
-
-Find the path of your downloaded Blockchain for example mine was:
-
-`C:\Users\KeeJef\Downloads\blockchain.raw`
-
-Yours might be different depending on where you downloaded the Blockchain to.
-
-### Step 4
-
-Open a Command Prompt window. You can do this by pressing the Windows key + R, and then typing in the popup box `CMD`
-
-### Step 5
-
-Now you need to navigate using the CMD window to the path of your Monero wallet. You can do this by typing:
-
-`cd C:\YOUR\MONERO\WALLET\FILE\PATH\HERE`
-
-It should look something like:
-
-`cd D:\monero-gui-0.10.3.1`
-
-If your Monero wallet is on another drive you can use `DriveLetter:` for example if your Monero wallet was on your D drive then before using the cd command you would do `D:`
-
-### Step 6
-
-Now type in your command prompt window:
-
-`monero-blockchain-import --verify 1 --input-file C:\YOUR\BLOCKCHAIN\FILE\PATH\HERE`
-
-For example I would type :
-
-`monero-blockchain-import --verify 1 --input-file C:\Users\KeeJef\Downloads\blockchain.raw`
-
-If you downloaded the Blockchain from a trusted, reputable source you may set `verify 0` this will reduce the amount of time to sync the Blockchain.
-
-### Step 7
-
-After the 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
+{% tf resources/user-guides/importing_blockchain.md %}
\ No newline at end of file
diff --git a/resources/user-guides/index.md b/resources/user-guides/index.md
index 0034675dd3fdee55e844228f35ca86954b2ebf3b..c5bc7792ef72e5ffc0fa7d3076decfff7e7b6f2c 100644
--- a/resources/user-guides/index.md
+++ b/resources/user-guides/index.md
@@ -1,128 +1,5 @@
---
layout: custom
-title: "User Guides"
+title: titles.userguides
---
-<div class="guides">
-<section class="container">
- <div class="row">
- <div class="left half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
- <div class="info-block">
- <div class="row center-xs">
- <div class="col">
- <h2>General</h2>
- </div>
- </div>
-<div class="row start-xs" markdown="1">
-
-[Monero Tools](monero_tools.html)
-[How to make an offline backup](Offline_Backup.html)
-[Importing the Monero blockchain](importing_blockchain.html)
-[How to run a node on VPS](vps_run_node.html)
-[Securely purchasing and storing Monero](securely_purchase.html)
-
-</div>
- </div>
- </div>
- <div class="right half col-lg-6 col-md-6 col-sm-12 col-xs-12">
- <div class="info-block">
- <div class="row center-xs">
- <div class="col">
- <h2>Wallets</h2>
- </div>
- </div>
-<div class="row start-xs" markdown="1">
-
-[Getting started with the CLI wallet](monero-wallet-cli.html)
-[How to make a view-only wallet](view_only.html)
-[How to prove payment](prove-payment.html)
-[Restoring wallet from keys](restore_from_keys.html)
-[How to connect to a remote node within GUI wallet](remote_node_gui.html)
-[CLI wallet/daemon isolation with Qubes+Whonix](cli_wallet_daemon_isolation_qubes_whonix.html)
-
-</div>
- </div>
- </div>
- </div>
-</section>
-
-<section class="container">
- <div class="row">
- <div class="left half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
- <div class="info-block">
- <div class="row center-xs">
- <div class="col">
- <h2>Recovery</h2>
- </div>
- </div>
-<div class="row start-xs" markdown="1">
-
-[How to fix locked up funds](howto_fix_stuck_funds.html)
-[How to restore your account](restore_account.html)
-
-</div>
- </div>
- </div>
- <div class="right half col-lg-6 col-md-6 col-sm-12 col-xs-12">
- <div class="info-block">
- <div class="row center-xs">
- <div class="col">
- <h2>Mining</h2>
- </div>
- </div>
-<div class="row start-xs" markdown="1">
-
-[How to solo mine with the GUI](solo_mine_GUI.html)
-[How to mine on a pool with xmr-stak-cpu](mine-to-pool.html)
-[Mining with Docker and XMRig](mining_with_xmrig_and_docker.html)
-
-</div>
- </div>
- </div>
- </div>
-
-
-
-</section>
-<section class="container">
- <div class="row">
- <div class="left half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
- <div class="info-block">
- <div class="row center-xs">
- <div class="col">
- <h2>Website</h2>
- </div>
- </div>
-<div class="row start-xs" markdown="1">
-
-[General Web Edit Instructions (READ FIRST!)](website-general.html)
-[How to make a blog post](website-blog.html)
-[How to make a User Guide](website-user-guide.html)
-[How to make a Moneropedia entry](website-moneropedia.html)
-[How to make a FFS proposal](website-ffs.html)
-[How to update the Team page](website-team.html)
-[How to add update Events page](website-events.html)
-[How to update the Roadmap](website-roadmap.html)
-[How to add a new Merchant](website-merchants.html)
-[How to add a new question to the FAQ](website-faq.html)
-
-</div>
- </div>
- </div>
- <div class="right half col-lg-6 col-md-6 col-sm-12 col-xs-12">
- <div class="info-block">
- <div class="row center-xs">
- <div class="col">
- <h2>Miscellaneous</h2>
- </div>
- </div>
-<div class="row start-xs" markdown="1">
-Coming Soon
-</div>
- </div>
- </div>
- </div>
-
-
-
-</section>
-</div>
+{% tf resources/user-guides/index.md %}
diff --git a/resources/user-guides/mine-to-pool.md b/resources/user-guides/mine-to-pool.md
index 43f8616eda5451fee721e7c2e6d4ef695839a6e7..d64f187f00471db2587744729379e9ed9d9d6815 100644
--- a/resources/user-guides/mine-to-pool.md
+++ b/resources/user-guides/mine-to-pool.md
@@ -1,117 +1,6 @@
---
-layout: static_page
+layout: user-guide
title: How to mine on a pool with xmr-stak-cpu
+permalink: /resources/user-guides/mine-to-pool.html
---
-# Selecting a pool
-
-There are many pools to choose from, a list is available at
-[moneropools.com](https://moneropools.com). Mining on a larger pool could mean
-more frequent payouts, but mining on a smaller pool helps to keep the network
-decentralized.
-
-# Selecting a CPU miner
-
-Just like pools, there are a lot of miners to choose from. The one that you
-should pick depends on the hardware you want to mine on. This guide will only
-use a CPU miner, and will be using
-[xmr-stak-cpu](https://github.com/fireice-uk/xmr-stak-cpu). Alternatives include
-[wolf's CPUMiner](https://github.com/wolf9466/cpuminer-multi) and
-[sgminer-gm](https://github.com/genesismining/sgminer-gm). However, their
-configuration is slightly different and will not be covered in this guide.
-
-## For Windows Systems
-
-If you are using a Windows system, the developer of xmr-stak-cpu provides
-binaries to download on the
-[GitHub release page](https://github.com/fireice-uk/xmr-stak-cpu/releases).
-
-Download `xmr-stak-cpu-win64.zip` and extract it somewhere you'll be able to
-find it again.
-
-## For Other Operating Systems
-
-If you're not using Windows, you will have to compile xmr-stak-cpu for yourself,
-luckily this isn't as hard as it sounds. Before you can compile the miner, you
-will need to install some of its prerequisites.
-
-For Debian-based distros:
-
- sudo apt-get install libmicrohttpd-dev libssl-dev cmake build-essential
-
-For Red Hat based distros:
-
- sudo yum install openssl-devel cmake gcc-c++ libmicrohttpd-devel
-
-<!-- TODO: Add dependencies for other operating systems? -->
-
-Following this, you just need to use cmake to generate the build files, run
-make and copy the config file:
-
- mkdir build-$(gcc -dumpmachine)
- cd $_
- cmake ../
- make -j$(nproc)
- cp ../config.txt bin/
- cd bin
-
-Don't celebrate just yet, as the miner needs to be configured. Running the miner
-now should give you a block of text to copy and paste:
-
-
-
-Open `config.txt` and *replace* the two `"cpu_threads_conf"` lines with the text
-you just copied. It should look something like this afterwards:
-
-
-
-Scroll down in the file until you see the lines containing `"pool_address"`.
-*Replace* the contents of the second set of quotes with the address and port of
-the pool you chose earlier. You can find this information on the pool's website.
-
-Put your wallet address between the quotes on the wallet address. You may leave
-the password blank unless the pool specifies otherwise.
-
-After this, your config should look something like this:
-
-
-
-# Running the miner
-
-**Save the config** file and run the miner!
-
-
-
-Some pools allow you to monitor your hashrate by pasting your address into their
-website. You can also monitor your hashrate by pressing the `h` key.
-
-# Tuning the miner
-
-You might see nasty messages like this:
-
- [2017-07-09 12:04:02] : MEMORY ALLOC FAILED: mmap failed
-
-This means that you can get around a 20% hashrate boost by enabling large pages.
-
-## Large pages on Linux
-
-Firstly stop the miner (if it's running), run the following commands to enable
-large pages and then start the miner as root:
-
- sudo sysctl -w vm.nr_hugepages=128
- sudo ./xmr-stak-cpu
-
-## Large pages on Windows
-
-Taken from `config.txt`:
-
->By default we will try to allocate large pages. This means you need to "Run As Administrator" on Windows
-You need to edit your system's group policies to enable locking large pages. Here are the steps from MSDN
-1. On the Start menu, click Run. In the Open box, type gpedit.msc.
-2. On the Local Group Policy Editor console, expand Computer Configuration, and then expand Windows Settings.
-3. Expand Security Settings, and then expand Local Policies.
-4. Select the User Rights Assignment folder.
-5. The policies will be displayed in the details pane.
-6. In the pane, double-click Lock pages in memory.
-7. In the Local Security Setting – Lock pages in memory dialog box, click Add User or Group.
-8. In the Select Users, Service Accounts, or Groups dialog box, add an account that you will run the miner on
-9. Reboot for change to take effect.
+{% tf resources/user-guides/mine-to-pool.md %}
\ No newline at end of file
diff --git a/resources/user-guides/mining_with_xmrig_and_docker.md b/resources/user-guides/mining_with_xmrig_and_docker.md
index 90ef44513dcac156960ad3a07efb4771323865ca..5dd93f0ad11e7e8381f92772332df64e73715dc9 100644
--- a/resources/user-guides/mining_with_xmrig_and_docker.md
+++ b/resources/user-guides/mining_with_xmrig_and_docker.md
@@ -1,47 +1,6 @@
---
-layout: static_page
+layout: user-guide
title: "Mining with XMRig and Docker"
-title-pre-kick: "Mining XMR"
-title-kick: "With XMRig and DOcker"
-title-post-kick: ""
-kick-class: "purple-kicks"
-icon: "icon_userguides"
-attribution: "<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->"
+permalink: /resources/user-guides/mining_with_xmrig_and_docker.html
---
-
-## Introduction
-
-This guide is two fold, ease of use for mining on Linux distributions and some extra security around mining as most of these miners have not had security auditing.
-
-At the end of this guide you will be able to sleep a little easier knowing that if the miner gets exploited it will not migrate to your OS.
-
-### Why Docker
-
-[Docker](https://www.docker.com/) is being used as it is the most well known and has the biggest chance to be already installed.
-
-The container I an using is [alpine-xmrig](https://hub.docker.com/r/bitnn/alpine-xmrig/) as per the name it is built on the [Alpine Linux](https://www.alpinelinux.org/) image.
-
-If you are interested in getting started with Docker, here are some really good starting references.
-* Arch Linux Wiki [Docker Page](https://wiki.archlinux.org/index.php/Docker)
-* Container Solutions [Security Cheat Sheet](http://container-solutions.com/content/uploads/2015/06/15.06.15_DockerCheatSheet_A2.pdf)
-* Digital Oceans [Dockerfile Howto](https://www.digitalocean.com/community/tutorials/docker-explained-using-dockerfiles-to-automate-building-of-images).
-
-For distribution specific installation please refer to the [Docker Docs](https://docs.docker.com/engine/installation/) website.
-
-### Why XMRig
-
-[XMRig](https://github.com/xmrig/xmrig) is just a really solid miner to me. Nice output and statistics, no flashy web-ui's or dependencies. The XMRig container is only ~4MB what makes it extremely portable.
-
-#### Step 1: Mining with XMRig
-
-Run the following
-
-```bash
-# docker run --restart unless-stopped --read-only -m 50M -c 512 bitnn/alpine-xmrig -o POOL01 -o POOL02 -u WALLET -p PASSWORD -k
-# docker run --restart unless-stopped --read-only -m 50M -c 512 bitnn/alpine-xmrig -o pool.supportxmr.com:7777 -u 45CJVagd6WwQAQfAkS91EHiTyfVaJn12uM4Su8iz6S2SHZ3QthmFM9BSPHVZY388ASWx8G9Wbz4BA24RQZUpGczb35fnnJz -p docker:secret -k
-```
-
-#### Step 2: There is no Step 2
-
-You have already done everything you need to do. You are now mining in a docker container with XMRig `ctrl+c` to exit the miner or add `-d` just after `docker run` to background the miner.
-
+{% tf resources/user-guides/mining_with_xmrig_and_docker.md %}
\ No newline at end of file
diff --git a/resources/user-guides/monero-wallet-cli.md b/resources/user-guides/monero-wallet-cli.md
index 58667ad189e7036ae89014b2c6b0f2ab4ea716cc..c1cb3e69911ac08a9aaff821e96308dd5848cdd2 100644
--- a/resources/user-guides/monero-wallet-cli.md
+++ b/resources/user-guides/monero-wallet-cli.md
@@ -1,155 +1,6 @@
---
-layout: static_page
+layout: user-guide
title: "Monero tools"
-title-pre-kick: "Monero tools "
-title-kick: "for the network "
-title-post-kick: ""
-kick-class: "purple-kicks"
-icon: "icon_userguides"
-attribution: "<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->"
+permalink: /resources/user-guides/monero-wallet-cli.html
---
-# monero-wallet-cli
-
-`monero-wallet-cli` is the wallet software that ships with the Monero tree. It is a console program,
-and manages an account. While a bitcoin wallet manages both an account and the blockchain,
-Monero separates these: `monerod` handles the blockchain, and `monero-wallet-cli` handles the account.
-
-This guide will show how to perform various operations from the `monero-wallet-cli` UI. The guide assumes you are using the most recent version of Monero and have already created an account according to the other guides.
-
-
-## Checking your balance
-
-Since the blockchain handling and the wallet are separate programs, many uses of `monero-wallet-cli`
-need to work with the daemon. This includes looking for incoming transactions to your address.
-Once you are running both `monero-wallet-cli` and `monerod`, enter `balance`.
-
-Example:
-
-This will pull blocks from the daemon the wallet did not yet see, and update your balance
-to match. This process will normally be done in the background every minute or so. To see the
-balance without refreshing:
-
- balance
- Balance: 64.526198850000, unlocked balance: 44.526198850000, including unlocked dust: 0.006198850000
-
-In this example, `Balance` is your total balance. The `unlocked balance` is the amount currently available to spend. Newly received transactions require 10 confirmations on the blockchain before being unlocked. `unlocked dust` refers to very small amounts of unspent outputs that may have accumulated in your account.
-
-## Sending monero
-
-You will need the standard address you want to send to (a long string starting with '4'), and
-possibly a payment ID, if the receiving party requires one. In that latter case, that party
-may instead give you an integrated address, which is both of these packed into a single address.
-
-### Sending to a standard address:
-
- transfer ADDRESS AMOUNT PAYMENTID
-
-Replace `ADDRESS` with the address you want to send to, `AMOUNT` with how many monero you want to send,
-and `PAYMENTID` with the payment ID you were given. Payment ID's are optional. If the receiving party doesn't need one, just
-omit it.
-
-### Sending to an integrated address:
-
- transfer ADDRESS AMOUNT
-
-The payment ID is implicit in the integrated address in that case.
-
-### Specify the number of outputs for a transaction:
-
- transfer MIXIN ADDRESS AMOUNT
-
-Replace `MIXIN` with the number of outputs you wish to use. **If not specified, the default is 4.** It's a good idea to use the default, but you can increase the number if you want to include more outputs. The higher the number, the larger the transaction, and higher fees are needed.
-
-
-## Receiving monero
-
-If you have your own Monero address, you just need to give your standard address to someone.
-
-You can find out your address with:
-
- address
-
-Since Monero is anonymous, you won't see the origin address the funds you receive came from. If you
-want to know, for instance to credit a particular customer, you'll have to tell the sender to use
-a payment ID, which is an arbitrary optional tag which gets attached to a transaction. To make life
-easier, you can generate an address that already includes a random payment ID:
-
- integrated_address
-
-This will generate a random payment ID, and give you the address that includes your own account
-and that payment ID. If you want to select a particular payment ID, you can do that too:
-
- integrated_address 12346780abcdef00
-
-Payments made to an integrated address generated from your account will go to your account,
-with that payment id attached, so you can tell payments apart.
-
-
-## Proving to a third party you paid someone
-
-If you pay a merchant, and the merchant claims to not have received the funds, you may need
-to prove to a third party you did send the funds - or even to the merchant, if it is a honest
-mistake. Monero is private, so you can't just point to your transaction in the blockchain,
-as you can't tell who sent it, and who received it. However, by supplying the per-transaction
-private key to a party, that party can tell whether that transaction sent monero to that
-particular address. Note that storing these per-transaction keys is disabled by default, and
-you will have to enable it before sending, if you think you may need it:
-
- set store-tx-info 1
-
-You can retrieve the tx key from an earlier transaction:
-
- get_tx_key 1234567890123456789012345678901212345678901234567890123456789012
-
-Pass in the transaction ID you want the key for. Remember that a payment might have been
-split in more than one transaction, so you may need several keys. You can then send that key,
-or these keys, to whoever you want to provide proof of your transaction, along with the
-transaction id and the address you sent to. Note that this third party, if knowing your
-own address, will be able to see how much change was returned to you as well.
-
-If you are the third party (that is, someone wants to prove to you that they sent monero
-to an address), then you can check this way:
-
- check_tx_key TXID TXKEY ADDRESS
-
-Replace `TXID`, `TXKEY` and `ADDRESS` with the transaction ID, per-transaction key, and destination
-address which were supplied to you, respectively. monero-wallet-cli will check that transaction
-and let you know how much monero this transaction paid to the given address.
-
-
-## Getting a chance to confirm/cancel payments
-
-If you want to get a last chance confirmation when sending a payment:
-
- set always-confirm-transfers 1
-
-
-## How to find a payment to you
-
-If you received a payment using a particular payment ID, you can look it up:
-
- payments PAYMENTID
-
-You can give more than one payment ID too.
-
-More generally, you can review incoming and outgoing payments:
-
- show_transfers
-
-You can give an optional height to list only recent transactions, and request
-only incoming or outgoing transactions. For example,
-
- show_transfers in 650000
-
-will only incoming transfers after block 650000. You can also give a height
-range.
-
-If you want to mine, you can do so from the wallet:
-
- start_mining 2
-
-This will start mining on the daemon usin two threads. Note that this is solo mining,
-and may take a while before you find a block. To stop mining:
-
- stop_mining
-
+{% tf resources/user-guides/monero-wallet-cli.md %}
\ No newline at end of file
diff --git a/resources/user-guides/monero_tools.md b/resources/user-guides/monero_tools.md
index 0e46c8802dbf48f79c57d2d4b51f628e577ed7d3..fdce0b29f4c6ddebeec6385376f21139c40cb938 100644
--- a/resources/user-guides/monero_tools.md
+++ b/resources/user-guides/monero_tools.md
@@ -1,27 +1,6 @@
---
-layout: static_page
+layout: user-guide
title: "Monero tools"
-title-pre-kick: "Monero tools "
-title-kick: "for the network "
-title-post-kick: ""
-kick-class: "purple-kicks"
-icon: "icon_userguides"
-attribution: "<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->"
+permalink: /resources/user-guides/monero_tools.html
---
-# Monero tools
-
-These tools can be used to gain information about the Monero network or your transaction data in the blockchain.
-
-### [Check that a recipient has received your funds](http://xmrtests.llcoins.net/checktx.html)
-
-### [Tools for monero address generation](https://xmr.llcoins.net/)
-
-### [Monero node count](http://moneronodes.i2p.xyz/)
-
-### [Monero node map](https://monerohash.com/nodes-distribution.html)
-
-### [Monero offline wallet generator](http://moneroaddress.org/)
-
-### [Monero network statistics](http://moneroblocks.info/stats)
-
-### [Monero.how statistics](https://www.monero.how/)
\ No newline at end of file
+{% tf resources/user-guides/monero_tools.md %}
\ No newline at end of file
diff --git a/resources/user-guides/prove-payment.md b/resources/user-guides/prove-payment.md
index bc2de7581046603f949160d2e819cee1eb7c4eb1..268fbe69421204e454e335b615bda6159e1a1cf2 100644
--- a/resources/user-guides/prove-payment.md
+++ b/resources/user-guides/prove-payment.md
@@ -1,62 +1,7 @@
---
-layout: static_page
+layout: user-guide
title: "How to prove payment"
-title-pre-kick: "Prove "
-title-kick: "payment"
-title-post-kick: ""
-kick-class: "kicks"
-icon: "icon_about"
-attribution: "<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->"
+permalink: /resources/user-guides/prove-payment.html
---
-When you send money to a party who then disputes the payment was made, you need to be able to prove the payment was made.
-
-With Bitcoin, this is typically done by looking up the transaction ID, where the origin and destination addresses are
-shown, along with the amount transacted.
-
-Monero, however, is private: that information is not available publicly on the blockchain. The steps are therefore a bit
-more involved.
-
-To prove to Charlie that she made a payment to Bob, Alice must supply Charlie three pieces of information:
-
-- the transaction ID, as is done in Bitcoin
-- Bob's address, as is done with Bitcoin
-- the transaction's key, which is new with Monero and other CryptoNote currencies
-
-When Alice made the transaction, a one time key was automatically generated just for this transaction. Alice can
-query it thus in monero-wallet-cli (new name for the old simplewallet):
-
-> get_tx_key TXID
-
-Alice would plug in her actual transaction ID instead of this TXID placeholder. All being well, the one time transaction key
-will be displayed.
-
-Note that this will only work if monero-wallet-cli is set to save transaction keys. To double check:
-
-> set
-
-If it's set to 0, set it to 1:
-
-> set store-tx-info 1
-
-Alice can now send Charlie the transaction key along with transaction ID and Bob's address.
-
-Note: if several transactions were made, this needs repeating for each such transaction.
-
-
----
-
-Charlie now received those three pieces of information, and wants to check Alice is telling the truth: on an up to date
-blockchain, Charlie types in monero-wallet-cli:
-
-> check_tx_key TXID TXKEY ADDRESS
-
-The information supplied by Alice plugs neatly instead of the placeholders. monero-wallet-cli will use the transaction
-key to decode the transaction, and display how much this particular transaction sent to this address. Obviously,
-Charlie will want to double check with Bob the address is really his - same as with Bitcoin.
-
-Alternatively, the transaction key can be obtained in the GUI in the History tab. Click on details for each individual transaction to get the key.
-
-Note: if several transactions were made, this needs repeating for each such transaction.
-
-
+{% tf resources/user-guides/prove-payment.md %}
\ No newline at end of file
diff --git a/resources/user-guides/remote_node_gui.md b/resources/user-guides/remote_node_gui.md
index 365cdc66f97905d3588eeeb980499a18cd138478..56c1b308a22e5264e2215d1c43e16c72f6f9e84e 100644
--- a/resources/user-guides/remote_node_gui.md
+++ b/resources/user-guides/remote_node_gui.md
@@ -1,15 +1,7 @@
---
-layout: static_page
+layout: user-guide
title: How to use a remote node in the GUI wallet
+permalink: /resources/user-guides/remote_node_gui.html
---
-## Finding a node
-First things first, you need to find a node to connect to! [moneroworld.com](https://moneroworld.com/#nodes) has some great resources for finding nodes. One of the easiest methods
-would be to use a node run by moneroworld, but they have a tool for finding random nodes too.
-
-## Connecting to the node from the GUI wallet
-After you enter your password for your wallet, you will see a pop up that will give you the option to "use custom settings". Click on it. You will then be
-sent to the "Settings" page in the GUI. At this point you should see two text boxes to the right of a label that says "Daemon address". In the first box (the on to the left) you need to enter the address of the node that you want to
-connect to. This address might look like `node.moneroworld.com` or it could look like any old ip address. The smaller box to the right is where you enter the node's port. The default port is `18081` but if you are using a random node the port that is used will vary. The port for node.moneroworld.com uses 18089.
-### Your screen should look a bit like this
-<img src="/resources/user-guides/png/remote_node/remote-node-screenshot.png" width="600">
+{% tf resources/user-guides/remote_node_gui.md %}
\ No newline at end of file
diff --git a/resources/user-guides/restore_account.md b/resources/user-guides/restore_account.md
index f9ead4bbb50e188c1c72b1a29dae76d5776d91b6..c88297b77419bbfc653406ec4c43305925ec24a4 100644
--- a/resources/user-guides/restore_account.md
+++ b/resources/user-guides/restore_account.md
@@ -1,33 +1,7 @@
---
-layout: static_page
+layout: user-guide
title: "Restoring your Monero Wallet"
-title-pre-kick: "Restoring your "
-title-kick: "Monero "
-title-post-kick: "Wallet"
-kick-class: "purple-kicks"
-icon: "icon_userguides"
-attribution: "<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->"
+permalink: /resources/user-guides/restore_account.html
---
-## Operating Systems: Windows, Linux, Mac
-
-### Account Software: monero-wallet-cli
-
-- Retrieve your 25 word @mnemonic-seed that you saved when creating your old Monero @wallet
-
-- Open a command prompt and navigate to the drive and directory that contains monero-wallet-cli
-
-- At the command prompt type: `monero-wallet-cli --restore-deterministic-wallet`
-
-- Once you press enter you will be prompted for a wallet file name. Give your wallet a new name, any name will do
-
-- Press enter again and you will be prompted for a password. Give your wallet a new and long password
-
-- Press enter again you will be prompted to repeat the password
-
-- Press enter again and you will be prompted for the 25 word electrum style mnemonic seed that you retrieved earlier
-
-- You will then be prompted with "Restore from specific blockchain height (optional, default 0):" Default will start the restore process from the beginning of the Monero blockchain. If you don't know the specific blockchain height, just hit enter. (Specifying a specific blockchain height will start the restore process from that specific height. This will save a bit of time in scanning, if you know what starting blockchain height your initial funds were transacted for this specific account.)
-
-After you have entered the 25 word mnemonic seed and have chosen your specific blockchain height, monero-wallet-cli will generate the same public address and view key as your old wallet and begin the refresh process automatically. (Please be patient as the refresh process may take a while.)
-
+{% tf resources/user-guides/restore_account.md %}
\ No newline at end of file
diff --git a/resources/user-guides/restore_from_keys.md b/resources/user-guides/restore_from_keys.md
index 134ca4beae4b63017c11c31492203e58bf65b29c..9bbfd5dfa4b1eee95f0ac4ab974d6773f69d6ec3 100644
--- a/resources/user-guides/restore_from_keys.md
+++ b/resources/user-guides/restore_from_keys.md
@@ -1,25 +1,6 @@
---
-layout: static_page
+layout: user-guide
title: "Restoring a wallet from private keys"
+permalink: /resources/user-guides/restore_from_keys.html
---
-
-
-
-Restoring a wallet from private keys (via the command line) is pretty simple. If you have the necessary information, with this guide you can completely restore your wallet. Note: you do NOT have to have your password to restore from keys.
-
-You need to have 3 pieces of data from your wallet, or your .keys file which holds this info and the password to decrypt it. The 3 wallet components that you need are:
-
-1. **Address**
-2. **Secret Spendkey**
-3. **Secret Viewkey**
-
-
-Then run the wallet command:
-
-`./monero-wallet-cli --generate-from-keys New_Wallet_Name.abc`
-
-Next, you'll be asked for the Address, the spendkey, the viewkey, and finally the new password for the re-generated wallet.
-
-Running this with the correct parameters will re-generate your wallet files for you and allow you to set a new password.
-
-If you run into any trouble, running `./monero-wallet-cli --help` will show you the options available to you at wallet startup. Once you're inside your wallet, running the `help` command will list the help for the commands available to you within the wallet.
+{% tf resources/user-guides/restore_from_keys.md %}
\ No newline at end of file
diff --git a/resources/user-guides/securely_purchase.md b/resources/user-guides/securely_purchase.md
index 6fd700ce9722f8f750d60ace0eda29bc5c55f950..da9bf4d7d3f5f440b5935bb09fcb3a66bf021e74 100644
--- a/resources/user-guides/securely_purchase.md
+++ b/resources/user-guides/securely_purchase.md
@@ -1,87 +1,7 @@
---
-layout: static_page
+layout: user-guide
title: Securely purchasing and storing Monero
+permalink: /resources/user-guides/securely_purchase.html
---
-
-## How to purchase Monero and securely store it.
-
-This is a guide to purchase and securely store Monero as of June 2017.
-
-#### Step 1: Buy Bitcoin
-
-There are many ways to buy Bitcoin. Two semi-reliable companies at this time are Xapo <http://www.xapo.com/> and Coinbase <http://www.coinbase.com/>. The process will involve uploading your personal identification (State ID, Passport, etc.) and will take anywhere from 2 to 10 days (or longer). Verify their reputation on Reddit before making a large purchase. Xapo uses Wire Transfer and Coinbase uses Bank Transfer (ACH in the USA). Xapo should be faster than Coinbase. Coinbase also allows small "instant" buys via a debit card but adds a large fee for this option. Once you have purchased Bitcoin, you are ready to convert it to Monero!
-
-#### Step 2: Download and create a Paper Wallet on a secure and air-gapped computer.
-
-Download the paper wallet generator at: https://moneroaddress.org and copy it to a USB stick (Direct link: https://github.com/moneromooo-monero/monero-wallet-generator/archive/master.zip).
-
-Unzip and open the paper wallet generator (monero-wallet-generator.html) into a web browser on an air-gapped computer that hasn't been used before, or has had a clean installation of the OS.
-
-Your paper wallet will have four important items:
-
-Monero Public Address
-The public address is used to receive funds to the wallet. You give this to anyone who will be sending funds to your wallet.
-
-Monero Mnemonic Seed
-The mnemonic seed is a method of storing the entire wallet that is easily recognizable to humans. This is all you need to restore your wallet at a later date.
-
-Monero Private Spend Key
-The private spend key is used to send funds from the wallet.
-
-Monero Private View Key
-The private view key is to view transactions entering the wallet. Commonly this is used to setup a view-only only wallet which can see incoming transactions live on the blockchain as they are sent to a cold storage wallet.
-
-At this point you have many options. You can print the wallet on paper, save it as a PDF or text on a USB stick, burn it to CD/DVD, etc. Most likely you will want at least two or three copies, stored securely in different locations. If storing digitally, encrypt everything with a strong password. If storing on paper, do not show the wallet to anyone else who can memorize your 25 word key, or take a picture of the wallet without your permission. Sending someone a picture of the wallet is the same as giving away all of your funds.
-
-Whichever method you chose, be sure there's no copy of the Monero wallet left over on the device you used. You may need to securely delete the Monero wallet if you saved it to a disk, or make sure your printer does not save a copy in memory.
-
-*If you lose access to your Monero paper wallet the Monero will not be available to you or anyone else, ever. You wont be able to recover them!
-
-#### Side Note
-Option to encrypt an XMR mnemonic seed:
-https://xmr.llcoins.net/
-Download the html page and place it on your airgapped computer. Check the part "Encrypt/Decrypt Mnemonic Seed" and make sure you use "CN Add" with a decent password. Thanks manicminer5.
-
-
-
-#### Step 3: Convert your Bitcoin to Monero and have it sent to your Monero Paper Wallet
-
-Switch to your internet connected computer and go to www.shapeshift.io. Choose "Deposit Bitcoin" and "Receive Monero" (quick).
-
-Press Continue.
-
-Your Monero Address (the Monero Public Address on your Monero Paper Wallet)
-Paste the Monero Public address from your paper wallet where it says "Your Monero Address". But wait, since your Monero Public Address is on an airgapped computer (right?), you can't copy and paste anything... Copy it over by hand, or get a blank USB drive and copy only the Public Address to it.
-
-Refund Address (Bitcoin Public Address you can receive funds at)
-Enter a Bitcoin address that you control where a refund can be sent in case there's a problem with the transaction. It's very important that you enter a Bitcoin Public Address you control or can receive funds at. At Xapo and Coinbase this is called a Receive Address and it may change periodically.
-
-Payment ID
-Leave Payment ID blank if you are sending to your own Monero wallet or Monero paper wallet.
-
-Agree to the Terms and hit the slider to make this a "Reusable Address".
-
-Press "Start Transaction".
-
-Deposit Address (Shapeshift.io's Public Bitcoin Address created only to receive your funds)
-In the new screen that pops up, copy the Deposit Address into your clipboard (select and hit ctrl+c or edit-copy). You will send Bitcoin from Xapo/Coinbase to Shapeshift.io via this address.
-
-Go to your Xapo or Circle account, and find a Transfer or Send button. Paste the Bitcoin Deposit address into the Destination field and enter the amount of bitcoin you would like to have converted to Monero. It must be within the Deposit Min and Deposit Max range specified by Shapeshift.io. Press Send and authorize the transaction, if required.
-
-Once the send has been initiated by Xapo/Coinbase there will be a delay while the transaction enters the Bitcoin blockchain and awaits confirmation. This may be minutes or hours. You can check if the payment has been sent by looking up the Shapeshift.io Deposit address at blockchain.info. Your transaction to Shapeshift.io will show up there.
-
-When your Bitcoin transaction has been confirmed, Shapeshift.io will then begin exchanging Bitcoin (BTC) for Monero (XMR) at one of the exchanges and when it's complete, send the Monero to the address of your Cold Storage Paper Wallet! This can take minutes to hours. If there's an issue, contact Shapeshift.io. They have good support.
-
-When the Shapehift.io webpage says your transaction has been completed, you should now have Monero in your Paper Wallet!
-
-
-#### Notes and How to Verify Funds
-Because the Monero blockchain is private and untraceable, you won't be able to lookup your Monero Public Address and confirm that the funds have arrived like you might with Bitcoin. This is good for privacy, but bad for convenience.
-
-To securely verify the funds have arrived at your wallet, you will need to setup a View Only wallet. This is where that view-key comes in. To create a view-only wallet see the entry: @view-only
-
-To verify the funds are *still in* your wallet and have not been spent you need to create a Cold Wallet with your mnemonic key (all your funds) on an airgapped computer with an up-to-date copy of the Monero Blockchain. When finished you will have to securely erase the wallet or connect it to the internet and it becomes a Hot Wallet.
-
-
-
+{% tf resources/user-guides/securely_purchase.md %}
\ No newline at end of file
diff --git a/resources/user-guides/solo_mine_GUI.md b/resources/user-guides/solo_mine_GUI.md
index 5c92663d02daa4c3e255ce800e5a6176ffb17fb6..073e21b01ef650d3f3c573f2619e57ed8354c8d7 100644
--- a/resources/user-guides/solo_mine_GUI.md
+++ b/resources/user-guides/solo_mine_GUI.md
@@ -1,26 +1,7 @@
---
-layout: static_page
+layout: user-guide
title: "How to solo mine with the GUI"
-title-pre-kick: "Solo mining with the GUI"
-title-kick: ""
-title-post-kick: ""
-kick-class: ""
-icon: "icon_userguides"
-attribution: "<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->"
+permalink: /resources/user-guides/solo_mine_GUI.html
---
-It is very easy to solo mine with the official GUI. If you have not done so already, go to the <a href="/downloads/">Monero downloads page</a> and download the official GUI for your operating system. Then, run the setup and be patient as Monero synchronizes with the network. You should see that it displays "Connected" in the lower left corner.
-
-<img src="/resources/user-guides/png/solo_mine_GUI/01.PNG" style="width: 600px;"/>
-
-Click on the "Advanced" tab. You should see that several other options appear. Now click on the "Mining" sub-tab.
-
-<img src="/resources/user-guides/png/solo_mine_GUI/02.PNG" style="width: 600px;"/>
-
-You should now have an option to start mining. You can optionally change the number of threads to mine with. For optimal efficiency, you should mine with your CPU's cache divided by 2. You will need to look up your CPU's specs on the manufacturer's website. If you are unsure, leave the number of threads at 1. Click the "Start mining" button.
-
-<img src="/resources/user-guides/png/solo_mine_GUI/03.PNG" style="width: 600px;"/>
-
-You are now mining with the network, as you can see on the bottom of the image. In this example, the computer is contributing 23 H/s to the Monero network. Mining helps keep the network secure, and you may get lucky and receive a reward for protecting the network.
-
-To stop mining, simply click the "Stop mining" button.
+{% tf resources/user-guides/solo_mine_GUI.md %}
\ No newline at end of file
diff --git a/resources/user-guides/view_only.md b/resources/user-guides/view_only.md
index 53dc6a67d27d888b84ec8897a90c1a881a9939e9..987bd9f73595007253f3d9693f11c8559d0c2a99 100644
--- a/resources/user-guides/view_only.md
+++ b/resources/user-guides/view_only.md
@@ -1,23 +1,7 @@
---
-layout: static_page
+layout: user-guide
title: "View Only Wallets"
-title-pre-kick: "Creating a view only wallet "
-title-kick: ""
-title-post-kick: ""
-kick-class: ""
-icon: "icon_userguides"
-attribution: "<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->"
+permalink: /resources/user-guides/view_only.html
---
-A view-only wallet can only see which incoming transactions belong to you. It can not spend any of your Monero, in fact it can't even see outgoing transactions from this wallet. This makes view-only wallets particularly interesting for
-
-* Developers writing libraries to validate payments
-* End users validating incoming transactions to cold wallets
-
-### Creating A View-Only Wallet
-
-You can create a view-only wallet from any existing wallet.
-
-Open an existing wallet or create a new one using `monero-wallet-cli`. In the wallet, type `address` and `viewkey` to display the wallet's address and secret viewkey. Type `exit` to close the wallet.
-
-Next, create your view-only wallet by typing `monero-wallet-cli --generate-from-view-key wallet-name`. The last argument will be your new wallet's file name. You will be prompted for `Standard address` and `View key` by the wallet. Paste in your original wallet's address and secret view key. Next, enter and confirm a password for your new wallet and you're done.
+{% tf resources/user-guides/view_only.md %}
\ No newline at end of file
diff --git a/resources/user-guides/vps_run_node.md b/resources/user-guides/vps_run_node.md
index bb03191c10169b4286135c2cd49c6bafecd80cdf..502e2b777bc6cb84bedcd9d421b22aded68da8de 100644
--- a/resources/user-guides/vps_run_node.md
+++ b/resources/user-guides/vps_run_node.md
@@ -1,57 +1,6 @@
---
-layout: static_page
+layout: user-guide
title: "Monero tools"
-title-pre-kick: "Monero tools "
-title-kick: "for the network "
-title-post-kick: ""
-kick-class: "purple-kicks"
-icon: "icon_userguides"
-attribution: "<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->"
+permalink: /resources/user-guides/vps_run_node.html
---
-# monerod
-
-`monerod` is the daemon software that ships with the Monero tree. It is a console program, and manages the blockchain. While a bitcoin wallet manages both an account and the blockchain, Monero separates these: `monerod` handles the blockchain, and `monero-wallet-cli` handles the account.
-
-This guide assumes you have already set up your VPS account and are using SSH to tunnel into the server console.
-
-## Linux, 64-bit (Ubuntu 16.04 LTS)
-
-### Make sure that port 18080 is open
-`monerod` uses this port to communicate with other nodes on the Monero network.
-
-Example if using `ufw`: `sudo ufw allow 18080`
-Example if using `iptables`: `sudo iptables -A INPUT -p tcp --dport 18080 -j ACCEPT`
-
-### Download the current Monero Core binaries
-
- wget https://downloads.getmonero.org/linux64
-
-### Make a directory and extract the files.
-
- mkdir monero
- tar -xjvf linux64 -C monero
-
-### Launch the daemon
-
- cd monero
- ./monerod
-
-### Options:
-
-Show list of all options and settings:
-
- ./monerod --help
-
-Launch the daemon as a background process:
-
- ./monerod --detach
-
-Monitor the output of `monerod` if running as daemon:
-
- tail -f ~/.bitmonero/bitmonero.log
-
-Keep the VPS secure with autoupdate:
-
-https://help.ubuntu.com/community/AutomaticSecurityUpdates
-
-
+{% tf resources/user-guides/vps_run_node.md %}
\ No newline at end of file
diff --git a/resources/user-guides/website-blog.md b/resources/user-guides/website-blog.md
deleted file mode 100644
index cb56123e328ea6a752e2ac6369873a492e53279c..0000000000000000000000000000000000000000
--- a/resources/user-guides/website-blog.md
+++ /dev/null
@@ -1,34 +0,0 @@
----
-layout: static_page
-title: How to make a blog post
----
-
-### Quick Start
-* Make new .md file in _posts (named whatever, no spaces)
-* Front Matter (below)
-* Write Blog Post
-* Test/Build
-* Submit PR
-
-### Make a file
-Navigate to the _posts folder of the website and make a new file. Be sure the file name has no spaces and the ending is .md
-
-### Front Matter
-```
----
-layout: post
-title: CHANGE TO YOUR TITLE
-summary: A BRIEF ONE OR TWO SENTENCE SUMMARY
-tags: [CHOOSE, RELEVANT, TAGS, AND, SEPARATE, THEM, BY, COMMAS, KEEP, THE, BRACKETS]
-author: YOUR NAME OR HANDLE HERE
----
-```
-
-### Write
-After the front matter is finished you are free to write the remainder of your blog post in markdown.
-
-### Build/Test
-Build your website using `jekyll serve` if it's not rebuilding automatically and test that your page appears in the 'News' section of the website, as well as the sidebars.
-
-### Submit Pull Request
-You're all done. Submit a PR and wait for it to be reviewed and merged. Be sure to make any changes if requested.
\ No newline at end of file
diff --git a/resources/user-guides/website-events.md b/resources/user-guides/website-events.md
deleted file mode 100644
index a5f3a495b6c0ba2e08840189592e4a4d69fcd698..0000000000000000000000000000000000000000
--- a/resources/user-guides/website-events.md
+++ /dev/null
@@ -1,38 +0,0 @@
----
-layout: static_page
-title: How to add an event
----
-
-### 9.1 Edit the .yml file
-Navigate to the `/_data/` folder and open `events.yml`. You will notice a list separated by hyphenated `-event` tags.
-
-**DO NOT MESS WITH THE FORMATTING OR INDENTATION OF ANYTHING OR JEKYLL WILL NOT BUILD PROPERLY!**
-
-Find the area that you want to update and copy the code below:
-```
-- event:
- where:
- when:
- description:
- link:
-```
-and paste it IN THE CHRONOLOGICAL ORDER that it will be in. So if there is an event happening before yours, make sure it is higher up than yours. If there is an event happening AFTER yours, make sure it is after your event.
-
-Fill in the data as follows:
-* `event:` The name of the event goes here as well as the date. The recommended format is: `Event Name - January 1st, 2000`
-* `where:` Where the event will take place. Vanue name and address are recommended.
-* `when:` Date and time
-* `description:` Descriptoin of the happenings of your event
-* `link:` The website of your event (if applicable, this can be left blank and everything will be ok). This link must have http:// 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.**
-
-Save the file.
-
-### 9.2 Build/Test
-Build your website using `jekyll serve` if it's not rebuilding automatically. If the build fails and you receive an error, you may have messed up somewhere in the `events.yml` file back in 9.1. Go back to that section and check the indentation. Yes, it's stupid. Yes, it has to be perfect.
-
-If the build is successful, go to the Events page `/community/events/` and check to see that the event is showing up in the correct place. Click their Event url link (if applicable) and make sure it redirects correctly. Test the page and let rehrar know if there are any bugs.
-
-### 9.3 Submit a Pull Request
-You're all done. Submit a PR and wait for it to be reviewed and merged. Be sure to make any changes if requested.
\ No newline at end of file
diff --git a/resources/user-guides/website-faq.md b/resources/user-guides/website-faq.md
deleted file mode 100644
index c49e46aa6c753108e8112a6efbdf2c5283db5a8c..0000000000000000000000000000000000000000
--- a/resources/user-guides/website-faq.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-layout: static_page
-title: How to add a question to the FAQ
----
-
-### Copy/Paste Code
-Navigate to the `/get-started/faq` folder and open the `index.md` file. Inside you will see HTML code, but you will see it is very repetetive.
-
-Copy the code below:
-```
-<div class="tab">
- <input id="tab-CHANGETHIS" type="checkbox" name="tabs" class="accordian">
- <label for="tab-CHANGETHIS" class="accordian">CHANGE QUESTION</label>
-
-<div class="tab-content" markdown="1">
-
-CHANGE ANSWER
-
-</div>
-
-</div>
-```
-And paste it at the very bottom of the file. Literally underneath everything else.
-
-Now we're going to change just a couple of things. Find the section with:
-```
-<input id="tab-CHANGETHIS" type="checkbox" name="tabs" class="accordian">
-<label for="tab-CHANGETHIS" class="accordian">CHANGE QUESTION</label>
-```
-
-and change the sections in between the quotes that say 'CHANGETHIS'. Leave the first part `tab-` alone. You can change it to anything really, as long as they are identical in the input and label, but it's good to see what number is on the last FAQ question (i.e. `tab-nine`) and make it the next number.
-
-Now inside the label tag you're going to find where it says 'CHANGE QUESTION' and change it to the Question you want answered.
-
-Lastly, find the words 'CHANGE ANSWER' and change it to the answer of your question.
-
-**DO NOT MESS WITH THE INDENTATION HERE. The div that has `markdown=1` MUST be flush with the left side, the answer to the question must start flush with the left side, and the `</div>` MUST be flush with the left side. **
-
-### Build/Test
-Build your website using `jekyll serve` if it's not rebuilding automatically. If the build is successful, go to the FAQ page `/get-started/faq/` and check to see that your question is showing up and, when clicked, the answer drops down. If not, check to make sure that the `id="tab-CHANGETHIS"` in the input and the `for="CHANGETHIS"` in the label are identical to each other. Test the page and let rehrar know if there are any bugs.
-
-### Submit a Pull Request
-You're all done. Submit a PR and wait for it to be reviewed and merged. Be sure to make any changes if requested.
\ No newline at end of file
diff --git a/resources/user-guides/website-ffs.md b/resources/user-guides/website-ffs.md
deleted file mode 100644
index 062a321bb23909db33ea1399d92dd2ac9f5cdbcd..0000000000000000000000000000000000000000
--- a/resources/user-guides/website-ffs.md
+++ /dev/null
@@ -1,72 +0,0 @@
----
-layout: static_page
-title: How to make a FFS proposal
----
-
-### Quick Start
-
-* Read [How the Forum Funding System works](#) and the [Forum Funding System Terms and Guidelines](#).
-* Make the .md file in the /forum-funding-system/proposals folder. Remember the name.
-* Choose your front matter layout based on whether your proposal is an Idea (`ffs-ideas`) or Open Task (`ffs-ot`) as specified in the above reading
-* Fill out the rest of the Front Matter below, leaving the `address` and `paymentid` sections empty
-* Edit the ffs.yml file. I strongly recommend you read this section.
-* Write the proposal
-* Test/Build
-* Submit PR
-
-### Make the proposal
-
-Navigate to the /forum-funding-system/proposals folder and make a new file. Be sure the file name has no spaces and the ending is .md. It is very important that you remember the EXACT name of this file.
-
-### Front Matter
-
-```
----
-layout: ffs-ideas OR ffs-ot
-title: NAME OF YOUR PROPOSAL
-summary: A BRIEF SUMMARY OF YOUR PROPOSAL
-author: YOUR NAME OR HANDLE
-address:
-paymentid:
----
-```
-
-The layout will depend on if you are simply presenting an idea that you do not plan to do yourself or if you are presenting an idea that you are capable and willing to do, the chosen layout will be `ffs-ideas` or `ffs-ot` respectively. You can get more information in the [How the Forum Funding System works](#) User Guide. Fill out the next three sections as normal (title, summary, author), but leave the last two (address, paymentid) blank. Again, DO NOT PUT ANYTHING HERE.
-
-### Editing the .yml file
-
-Navigate to the /_data folder and open the file titled `ffs.yml`. In this file you will find a long list of FFS proposals.
-
-**DO NOT MESS WITH THE FORMATTING OR INDENTATION OF ANYTHING OR JEKYLL WILL NOT BUILD PROPERLY!**
-
-Identify the section you will be placing your proposal in. If you used `ffs-ideas` in the layout variable in the front matter then you will be putting your proposal in `stage: ideas`, and if you used `ffs-ot` in the layout, then you will be putting your proposal in the `stage: Open Tasks`. Copy the following code:
-
-```
-- name:
- url: /forum-funding-system/proposals/
- summary:
- author:
-```
-
-and paste it as the very top underneath the `proposals:`.
-
-**Make sure the indentation is EXACTLY the same as the other proposals in the area. If it's not the jekyll build WILL fail. If in doubt, put the line with the hyphen (-name) all the way to the left and press space four time, and then put the remainder of the variables all the way to the left and press space six times.**
-
-Fill in the information.
-* `name:` should be the same as the title chosen in 7.3
-* for `url:` you should append the EXACT name of the file as chosen in 7.2 to the current string but with `.html` at the end instead of `.md`. So it should look like `/forum-funding-system/proposals/YOUR-FILE-NAME.html`
-* `summary:` should be the same summary copy and pasted from the front matter in 7.3
-* `author:` should be your name or handle, again the same as the front matter in 7.3
-
-Sorry for the repetition here, but it's how Jekyll is working to put things correctly.
-
-### Write the proposal
-Go ahead and write your proposal now. Go back to your .md file in `/forum-funding-system/proposals`. Be sure to follow the [Forum Funding System Terms and Guidelines](#). Let me be the first to thank you for wanting to contribute your time and energy to better Monero.
-
-### Build/Test
-Build your website using `jekyll serve` if it's not rebuilding automatically. If the build fails and you receive an error, you may have messed up somewhere in the `ffs.yml` file back in 7.4. Go back to that section and check the indentation. Yes, it's stupid. Yes, it has to be perfect.
-
-If the build is successful, go to the Forum Funding System section of the website and make sure that your proposal is showing up in the correct areas, and that when the linked is clicked it takes you to the correct page with your proposal. Use this time to read everything for accuracy and make any changes. If not, you will have to do multiple PRs to make edits and updates. It is this way by design so we can keep track of edits made by authors.
-
-### Submit a Pull Request
-You're all done. Submit a PR and wait for it to be reviewed and merged. Be sure to make any changes if requested.
\ No newline at end of file
diff --git a/resources/user-guides/website-general.md b/resources/user-guides/website-general.md
deleted file mode 100644
index c686b6297ee2e39ed5cd14b33010d87bccc64703..0000000000000000000000000000000000000000
--- a/resources/user-guides/website-general.md
+++ /dev/null
@@ -1,58 +0,0 @@
----
-layout: static_page
-title: General Website Instructions
----
-
-### Introduction
-
-This README here to walk you through everything you need to know to make changes, edits, or even completely new pages for the new getmonero.org website. It'll definitely be a bit of a ride, so strap yourself in. Please note that translations are not available yet, but when they are added, this document will be updated with instructions on how to translate the content of getmonero.org. In the meantime, any help translating this document into another language is greatly appreciated.
-
-Feel free to skip down to a relevant section if you already know what you need. So to go to the 'How to make a User Guide' section use your find function and type '5.0'.
-
-If for any reason you have questions or need to contact us, you can find us on the IRC channel #monero. We'll do whatever we can to help you.
-
-### What you'll need
-
-* Jekyll: Getmonero.org is made using a simple, static website generator called [Jekyll](https://jekyllrb.com/). You will need it installed on your system to test any changes that you made. If you're using Windows, you will want to check out [this site](http://jekyll-windows.juthilo.com/) for instructions on how to get Jekyll working on your system. If you're using a Linux-based system you can just follow the instructions on the website to get up and going:
- * Install Ruby
- * Install Bundler: `gem install bundler`
- * Install Jekyll with all dependencies (run from the project directory): `bundle`
-
-* GitHub: Pretty much everything in Monero is hosted on [GitHub](https://github.com) and uses Git as the primary version control system. If you're not familiar with how to use Git, you can check out [this tutorial](https://guides.github.com/activities/hello-world/) for a good overview. It will take you through pretty much everything you'll need to know to edit the website. If you haven't already, register for GitHub and fork the [Monero Website repository](https://github.com/monero-project/monero-site).
-
-* Markdown experience: To write pages, you're going to need to know how to use Markdown. It's basically an in-between language that enables people who don't know HTML to just write, and it will be compiled into HTML for you. You can find a great Markdown cheat sheet with examples [here](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet). IF you need more help, Google and YouTube are great resources.
-
-*Note: If you're confused, feel free to click other files in the same directory (folder) that you are in for the step that you are on to see some working examples. Compare them to the instructions and you should understand better.*
-
-Once you have the above list of things, it's typically a good idea to build the website from your local computer to make sure it works before you make any changes. To do this, complete the following steps:
-
-1. Navigate to your local `monero-site` repository.
-2. Serve the website: `jekyll serve`
-3. Open a browser and go to [http://127.0.0.1:4000](http://127.0.0.1:4000).
-4. If all went well, you should see the Monero website and you're ready to make changes.
-
-### General change recommendations
-
-The average Monero user that will want to contribute to the website should probably stick with making blog posts, user guides, Moneropedia entries, or a Forum Funding System proposal, all of which are covered in this document. If this is all you want to do, don't worry, it's actually not a daunting task at all. If you are not well versed in web development however, it is not recommended you try to do anything beyond that.
-
-If you are a web developer and would like to make large macro-level changes, it would be best to get in contact with rehrar. The HTML/CSS framework is custom, though quite easy to use for a seasoned developer. Still, there are some pages that are more complicated than others and would require fair amounts of styling changes should the structure change significantly.
-
-This website is completely open-source however and anything and everything is available for changing should the community deem it necessary.
-
-Every section from here on out will talk about how to make a specific type of web page. It will start with a bullet point list of what to do for the advanced among you that just want a quick overview. For those who are still learning this list is followed by a detailed explanation, starting with example front matter. Any variable in the front matter written in all caps you are expected to change (make sure your changes are not all caps though). It will then lead you through the rest of the process until it's time to type your content.
-
-A few random points of note:
-
-- All external links must have http:// or https:// in front of them or they will not redirect properly.
-- If you want to add a new page to the navigation, you should note that there are two menus in `header.html`. One for mobile and one for desktop. Your page must be added in the appropriate place in BOTH navigations.
-- It is strongly strongly STRONGLY encouraged that you if you make a change, you - at the minimum - test it on your local machine before submitting a PR. Sometimes unexpected things may happen due to a change. If you change a page, check the whole page on multiple screen sizes and browsers to make sure there wasn't any collateral damage.
-
-### Housekeeping
-
-#### GitHub Issues
-We ask that if you open an issue on the site that you remain available for clarifying questions or corrections. We do our best to close issues that are resolved when we make changes to the site, but If your issue is resolved by a contributer and the issue is not closed we ask that you close it in a timely manner. A contributer (rehrar, SamsungGalaxyPlayer, or other community members, etc) may ask you to close an issue after it's confirmed fixed. Please review the changes to the site and close your issue if you can verify that it's fixed.
-
-#### Pull Requests
-Contributers should use [issue keywords](https://help.github.com/articles/closing-issues-using-keywords/) to make it easier for maintainers to close issues when they merge. Include close, closes, closed, fix, fixes, fixed, resolve, resolves, resolved, etc in the commit message or pull request description, so that the correct issue can be closed if your PR is merged. (Example: 'fixes #1234' could close Issue 1234 when merged.)
-
-Pull requests allow others to make comments or review your changes to the site. We ask that you remain available to comment or make changes to your PR. Pull requests with pending changes for more than 30 days will be closed and need to be resubmitted in the future. Sometimes someone else's changes might make your changes conflict with the current site. If that happens you may need to rebase your PR. (If you're unsure about how to do so, you can reach out to other contributers on IRC (freenode #monero) and someone should be able to walk you through it.
\ No newline at end of file
diff --git a/resources/user-guides/website-merchants.md b/resources/user-guides/website-merchants.md
deleted file mode 100644
index cdc4497a33e85556a6edd2ff7fde9c7483d63a25..0000000000000000000000000000000000000000
--- a/resources/user-guides/website-merchants.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-layout: static_page
-title: How to add a new merchant
----
-
-### Edit the .yml file
-Navigate to the `/_data/` folder and open `merchants.yml`. You will notice a list separated by hyphenated `-category` tags.
-
-**DO NOT MESS WITH THE FORMATTING OR INDENTATION OF ANYTHING OR JEKYLL WILL NOT BUILD PROPERLY!**
-
-Find the category that best describes your business/service and copy the code below:
-```
-- name:
- url:
-```
-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.
-* `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.**
-
-Save the file.
-
-### Build/Test
-Build your website using `jekyll serve` if it's not rebuilding automatically. If the build fails and you receive an error, you may have messed up somewhere in the `merchants.yml` file back in 10.1. Go back to that section and check the indentation. Yes, it's stupid. Yes, it has to be perfect.
-
-If the build is successful, go to the Merchants page `/community/merchants/` and check to see that the business is showing up in the correct category and that the link is redirecting correctly. Test the page and let rehrar know if there are any bugs.
-
-### Submit a Pull Request
-You're all done. Submit a PR and wait for it to be reviewed and merged. Be sure to make any changes if requested.
\ No newline at end of file
diff --git a/resources/user-guides/website-moneropedia.md b/resources/user-guides/website-moneropedia.md
deleted file mode 100644
index 68919677e6c150693543b83cc1143311a2ba875d..0000000000000000000000000000000000000000
--- a/resources/user-guides/website-moneropedia.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-layout: static_page
-title: How to add a Moneropedia entry
----
-
-### Make a file
-Navigate to the /resources/moneropedia folder and make a new file. Be sure the file name has no spaces and the ending is .md
-
-### Front Matter
-```
----
-layout: moneropedia
-entry: "PUT THE NAME OF THE TERM HERE IN QUOTE, THIS IS HOW IT WILL SHOW UP ON THE LANDING PAGE"
-terms: ["PUT", "TERMS", "HERE", "EXPLAINED", "BELOW"]
-summary: "PUT SUMMARY OF YOUR ENTRY HERE IN QUOTES"
----
-```
-
-There is one thing to highlight. The `terms:` section of the front matter can be filled with as many terms as you would like. This is how other Moneropedia entries will link to this page. You can link to other Moneropedia entries as well in your page by putting an ampersand before the term used, i.e. `@THE-TERM-USED`. This will make an automatic link in the Moneropedia entry to the referred term, replace the @term with the word used in that terms `entry:` area of the front matter, and on hover it will show the summary. How cool is that?
-
-### Write
-Write your Moneropedia entry. Remember that you can link to other Moneropedia entries using `@term-used-in-entry` as described above. Just go to the .md file of the Moneropedia entry you want to link to and use any of the terms in the `terms:` field of the front matter. Be sure to write whichever one you choose EXACTLY as shown and preceded by an ampersand.
-
-### Build/Test
-Build your website using `jekyll serve` if it's not rebuilding automatically and test check the link to your entry is appearing on the alphabetical list of Moneropedia entries and that it leads to your entry when clicked. Test your Moneropedia entry in the browser and contact rehrar if there are any bugs.
-
-### Submit Pull Request
-You're all done. Submit a PR and wait for it to be reviewed and merged. Be sure to make any changes if requested.
\ No newline at end of file
diff --git a/resources/user-guides/website-roadmap.md b/resources/user-guides/website-roadmap.md
deleted file mode 100644
index 4b2f40911d331e70f559c011a6939e9b9a318bc2..0000000000000000000000000000000000000000
--- a/resources/user-guides/website-roadmap.md
+++ /dev/null
@@ -1,34 +0,0 @@
----
-layout: static_page
-title: How to update the Roadmap
----
-
-### Edit the .yml file
-Navigate to the `/_data/` folder and open `roadmap.yml`. You will notice a list separated by hyphenated `-year` tags.
-
-**DO NOT MESS WITH THE FORMATTING OR INDENTATION OF ANYTHING OR JEKYLL WILL NOT BUILD PROPERLY!**
-
-Find the year that you want to update and copy the code below:
-```
-- name:
- date:
- status:
-```
-and paste it in the correct years `accomplishments:` section IN THE CHRONOLOGICAL ORDER that it will be in. So if there is a accomplishment that happened/is happening before the one you are inputting, make sure it is higher up than yours. If there is an accomplishment that happened/is happening AFTER yours, make sure it is after yours. If you don't have exact dates, just do your best to estimate.
-
-Fill in the data as follows:
-* `name:` The name of the accomplishment. Try to keep it short, a sentence or two at most.
-* `date:` When the accomplishment happened (past) or when it is expected to happen (future)
-* `status:` If the task is done, put `completed`, if the task is currently in the works put `ongoing`, and if work on the task has not yet started to your knowledge, but is expected to, put `upcoming`.
-
-**Make sure the indentation is EXACTLY the same as the other proposals in the area. If it's not the jekyll build WILL fail.**
-
-Save the file.
-
-### Build/Test
-Build your website using `jekyll serve` if it's not rebuilding automatically. If the build fails and you receive an error, you may have messed up somewhere in the `roadmap.yml` file back in 10.1. Go back to that section and check the indentation. Yes, it's stupid. Yes, it has to be perfect.
-
-If the build is successful, go to the Events page `/resources/roadmap/` and check to see that the newly added accomplishment is showing up in the correct place in the correct year. Test the page and let rehrar know if there are any bugs.
-
-### Submit a Pull Request
-You're all done. Submit a PR and wait for it to be reviewed and merged. Be sure to make any changes if requested.
\ No newline at end of file
diff --git a/resources/user-guides/website-team.md b/resources/user-guides/website-team.md
deleted file mode 100644
index a9fb3fcbe3a53b693df4724fcd78083ab6700dd0..0000000000000000000000000000000000000000
--- a/resources/user-guides/website-team.md
+++ /dev/null
@@ -1,30 +0,0 @@
----
-layout: static_page
-title: How to update the Team page
----
-
-If you are acting on behalf of another individual, please make sure you get their permission first before adding them onto the Team page.
-
-### Change the .yml file
-Navigate to the `/_data/` folder and open `team.yml`. You will notice a long list separated by main `-area:` tags.
-
-**DO NOT MESS WITH THE FORMATTING OR INDENTATION OF ANYTHING OR JEKYLL WILL NOT BUILD PROPERLY!**
-
-Find the area that you want to update and copy the code below:
-```
-- name:
- url:
-```
-Put the name or handle of the person in the `name` section and in the `url:` section put the link to their GitHub URL (it must have https:// at the beginning). If they have no GitHub, then you may leave it blank, it won't mess anything up.
-
-**Make sure the indentation is EXACTLY the same as the other proposals in the area. If it's not the jekyll build WILL fail.**
-
-Save the file.
-
-### Build/Test
-Build your website using `jekyll serve` if it's not rebuilding automatically. If the build fails and you receive an error, you may have messed up somewhere in the `team.yml` file back in 8.1. Go back to that section and check the indentation. Yes, it's stupid. Yes, it has to be perfect.
-
-If the build is successful, go to the Team page `/community/team/` and check to see that the contributor is showing up in the correct place. Click their GitHub link (if applicable) and make sure it redirects correctly. Test the page and let rehrar know if there are any bugs.
-
-### Submit a Pull Request
-You're all done. Submit a PR and wait for it to be reviewed and merged. Be sure to make any changes if requested.
\ No newline at end of file
diff --git a/resources/user-guides/website-user-guide.md b/resources/user-guides/website-user-guide.md
deleted file mode 100644
index 5b35c6cf7bc7d4197be9d122bfb354e7d16846ab..0000000000000000000000000000000000000000
--- a/resources/user-guides/website-user-guide.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-layout: static_page
-title: How to make a User Guide
----
-
-### Quick Start
-
-* Make file in /resources/user-guides with a .md ending and no spaces in filename.
-* Front Matter as in 5.3
-* Write User Guide
-* Add guide using markdown in the correct category in /resources/user-guides/index.md being careful not to mess with any indentation
-* Test/Build
-* Submit PR
-
-### Make a file
-Navigate to the /resources/user-guides folder and make a new file. Be sure the file name has no spaces and the ending is .md
-
-### Front Matter
-```
----
-layout: static_page
-title: TITLE OF YOUR USER GUIDE
----
-```
-
-### Write
-Write your user guide. Be succinct but thorough. Remember, people will be using your guides when they need help. Make sure all the information is there. Feel free to use images or screenshots if necessary to help get your point across.
-
-### Add Guide to the 'User Guide' landing page
-In the /resources/user-guides folder, find the file labeled index.md and open it.
-
-DO NOT CHANGE ANYTHING IN THIS DOCUMENT BESIDES WHAT YOU ARE INSTRUCTED TO.
-
-This file will look quite different because it's HTML. Don't panic. Simply Ctrl + F (i.e. the find feature) and search for the category that you want to put your User Guide in. You will see there are some sections that are not indented like the others. They are flush with the left side of the screen. **Do not change the indentation.** You can put markdown in these areas.
-
-Once you've identified the non-indented area under the category you would like your User Guide to be under, you can use markdown to insert your link underneath the others. `[TITLE OF USER GUIDE](LINK-TO-USER-GUIDE.html)`. Please note that the file name in between the paranthases must be EXACTLY the same name as the file name you made in step 5.2, but with a `.html` at the end instead of `.md`.
-
-In the event that you think your User Guide should be in a new Category that doesn't exist yet, contact rehrar to make one for you.
-
-### Build/Test
-Build your website using `jekyll serve` if it's not rebuilding automatically and test that your link appears in the correct category and that it leads to your User Guide when clicked. Test your User Guide in the browser and contact rehrar if there are any bugs.
-
-### Submit Pull Request
-You're all done. Submit a PR and wait for it to be reviewed and merged. Be sure to make any changes if requested.
\ No newline at end of file
diff --git a/technical-specs/index.md b/technical-specs/index.md
new file mode 100644
index 0000000000000000000000000000000000000000..01cd7912c85f70251cbb1d602c39e5062f93a919
--- /dev/null
+++ b/technical-specs/index.md
@@ -0,0 +1,6 @@
+---
+layout: custom
+title: titles.technicalspecs
+permalink: /technical-specs/index.html
+---
+{% tf technical-specs.md %}
\ No newline at end of file
diff --git a/the-monero-project/index.md b/the-monero-project/index.md
index 4124a45595a825e2ee031852ddc53207c717fe2e..dd7c51dc517838ac60faa0a893bd552004ccf592 100644
--- a/the-monero-project/index.md
+++ b/the-monero-project/index.md
@@ -1,49 +1,6 @@
---
layout: default
-title: "The Monero Project"
+title: titles.themoneroproject
+permalink: /the-monero-project/index.html
---
-
-<div class="site-wrap">
-<section class="container">
- <div class="row">
- <div class="left half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
- <div class="info-block">
- <div class="row center-xs">
- <div class="col">
- <h2>Kovri</h2>
- </div>
- </div>
-<div class="row start-xs monero-project" markdown="1">
-
-The Kovri project uses end-to-end encryption so that neither the sender nor receiver of a Monero transaction need to reveal their IP address to the other side or to third-party observers (the blockchain). This is done using the same technology that powers the dark net, i2p (Invisible Internet Protocol). The project is currently in heavy, active development and is not yet integrated with Monero.
-
-</div>
- <div class="row center-xs">
- <p><a href="https://www.getkovri.org" class="btn-link btn-fixed">Visit Kovri Website</a></p>
- </div>
- </div>
- </div>
- <div class="right half col-lg-6 col-md-6 col-sm-12 col-xs-12">
- <div class="info-block">
- <div class="row center-xs">
- <div class="col">
- <h2>Open Alias</h2>
- </div>
- </div>
-<div class="row start-xs monero-project" markdown="1">
-
-The OpenAlias project simplifies cryptocurrency payments by providing FQDNs (Fully Qualified Domain Names, i.e. example.openalias.org) for Monero wallet addresses in a way that ensures everyone's privacy is secure. The project is well underway and has already been implemented in many Monero wallets.
-
-
-
-</div>
-
- <div class="row center-xs">
- <p><a href="https://www.openalias.org" class="btn-link btn-fixed">Visit OpenAlias Website</a></p>
- </div>
-
- </div>
- </div>
- </div>
-</section>
-</div>
\ No newline at end of file
+{% tf the-monero-project.md %}
\ No newline at end of file