diff --git a/_config.yml b/_config.yml
index 6d6b05d4..f35acfed 100644
--- a/_config.yml
+++ b/_config.yml
@@ -24,7 +24,8 @@ plugins:
- jekyll-multiple-languages-plugin
# jekyll-multiple-languages-plugin settings:
-languages: ["en", "es", "it", "pl", "fr", "ar", "ru", "de"]
+languages: ["en", "es", "it", "pl", "fr", "ar", "ru", "de", "nl"]
+
exclude_from_localizations: ["img", "css", "fonts", "media", "404", "feed.xml", "404", "meta", "forum-funding-system", "_posts", "legal"]
diff --git a/_data/lang/nl/footer-1.yml b/_data/lang/nl/footer-1.yml
new file mode 100644
index 00000000..bf23153c
--- /dev/null
+++ b/_data/lang/nl/footer-1.yml
@@ -0,0 +1,52 @@
+- title: Informatie
+ subfolderitems:
+ - name: Over Monero
+ url: resources/about/
+ - name: Moneropedia
+ url: resources/moneropedia/
+ - name: Handleidingen voor ontwikkelaars
+ url: resources/developer-guides/
+ - name: Gebruikershandleidingen
+ url: resources/user-guides/
+ - name: Bibliotheek
+ url: library
+ - name: RSS-kanaal
+ url: https://getmonero.org/feed.xml
+- title: IRC-kanalen
+ 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
+ url: https://bitcointalk.org/index.php?topic=583449.0
+ - name: Mattermost
+ url: https://mattermost.getmonero.org/
+ - name: Telegram
+ url: https://telegram.me/bitmonero
+- title: Het Monero-project
+ subfolderitems:
+ - name: OpenAlias
+ url: https://openalias.org/
+ - name: Kovri
+ url: https://kovri.io/
+ - name: Monero Research Lab
+ url: resources/research-lab/
+ - name: Monero Press Kit
+ url: press-kit
diff --git a/_data/lang/nl/footer-2.yml b/_data/lang/nl/footer-2.yml
new file mode 100644
index 00000000..a2752a9d
--- /dev/null
+++ b/_data/lang/nl/footer-2.yml
@@ -0,0 +1,6 @@
+- name: Juridisch
+ url: legal
+- name: Broncode
+ url: https://github.com/monero-project
+- name: Technische specificaties
+ url: technical-specs/
diff --git a/_data/lang/nl/navigation.yml b/_data/lang/nl/navigation.yml
new file mode 100644
index 00000000..f02cdcf6
--- /dev/null
+++ b/_data/lang/nl/navigation.yml
@@ -0,0 +1,54 @@
+- title: Aan de slag
+ subfolderitems:
+ - page: Wat is Monero?
+ url: get-started/what-is-monero
+ - page: Gebruiken
+ url: get-started/using
+ - page: Accepteren
+ url: get-started/accepting
+ - page: Bijdragen
+ url: get-started/contributing
+ - page: Minen
+ url: get-started/mining
+ - page: FAQ
+ url: get-started/faq
+- title: Downloads
+ url: downloads/
+- title: Nieuws
+ subfolderitems:
+ - page: Alles
+ url: blog
+ - page: Missives
+ url: blog/tags/monero%20missives.html
+ - page: Vergaderingen
+ url: blog/tags/dev%20diaries.html
+ - page: Releases
+ url: blog/tags/releases.html
+- title: Community
+ subfolderitems:
+ - page: Team
+ url: community/team
+ - page: Ontmoetingsplekken
+ url: community/hangouts
+ - page: Sponsors
+ url: community/sponsorships
+ - page: Verkopers
+ url: community/merchants
+- title: Informatie
+ subfolderitems:
+ - page: Over Monero
+ url: resources/about/
+ - page: Planning
+ url: resources/roadmap
+ - page: Research Lab
+ url: resources/research-lab
+ - page: Moneropedia
+ url: resources/moneropedia
+ - page: Gebruikershandleidingen
+ url: resources/user-guides
+ - page: Handleidingen voor ontwikkelaars
+ url: resources/developer-guides
+ - page: Technische specificaties
+ url: technical-specs
+ - page: Bibliotheek
+ url: library
diff --git a/_data/lang/nl/roadmap.yml b/_data/lang/nl/roadmap.yml
new file mode 100644
index 00000000..54c9e71e
--- /dev/null
+++ b/_data/lang/nl/roadmap.yml
@@ -0,0 +1,120 @@
+- year: 2014
+ accomplishments:
+ - name: Gestart op Bitcointalk
+ date: 2014-04-18
+ status: completed
+ - name: Naam veranderd van Bitmonero in Monero
+ date: 2014-04-23
+ status: completed
+ - name: Hersteld van een spamaanval
+ date: 2014-09-04
+ status: completed
+ - name: Papers 1 en 2 van het Monero Research Lab gepubliceerd
+ date: 2014-09-12
+ status: completed
+ - name: Paper 3 van het Monero Research Lab gepubliceerd
+ date: 2014-09-25
+ status: completed
+ - name: Versie 0.8.8.6
+ date: 2014-12-08
+ status: completed
+- year: 2015
+ accomplishments:
+ - name: Paper 4 van het Monero Research Lab gepubliceerd
+ date: 2015-01-26
+ status: completed
+- year: 2016
+ accomplishments:
+ - name: Versie 0.9.0 Hydrogen Helix
+ date: 2016-01-01
+ status: completed
+ - name: Paper 5 van het Monero Research Lab gepubliceerd
+ date: 2016-02-10
+ status: completed
+ - name: Netwerkupgrade waardoor minimale ringgrootte van 3 verplicht wordt voor alle transacties
+ date: 2016-03-22
+ status: completed
+ - name: Versie 0.10.0 Wolfram Warptangent
+ date: 2016-09-18
+ status: completed
+ - name: Netwerkupgrade om coinbase te splitsen in coupures
+ date: 2016-09-21
+ status: completed
+ - name: Versie 0.10.1 Wolfram Warptangent
+ date: 2016-12-14
+ status: completed
+ - name: Officile GUI bta 1
+ date: 2016-12-22
+ status: completed
+- year: 2017
+ accomplishments:
+ - name: Netwerkupgrade om RingCT-transacties mogelijk te maken
+ date: 2017-01-05
+ status: completed
+ - name: Versie 0.10.2, met een patch voor een kritiek beveiligingsprobleem
+ date: 2017-02-22
+ status: completed
+ - name: Versie 0.10.3.1 Wolfram Warptangent
+ date: 2017-03-27
+ status: completed
+ - name: Netwerkupgrade om minimale blokgrootte en dynamische transactiekosten aan te passen
+ date: 2017-04-15
+ status: completed
+ - name: Nieuw ontwerp van de website
+ date: 2017-07-04
+ status: completed
+ - name: Versie 0.11.0.0 Helium Hydra
+ date: 2017-09-07
+ status: completed
+ - name: Fluffy blocks
+ date: 2017-09-07
+ status: completed
+ - name: GUI niet meer bta
+ date: 2017-09-10
+ status: completed
+ - name: Netwerkupgrade voor minimale ringgrootte van 5 en verplichte RingCT-transacties
+ date: 2017-09-15
+ status: completed
+ - name: 0MQ/ZeroMQ
+ date: September 2017
+ status: completed
+ - name: Subadressen
+ date: Oktober 2017
+ status: completed
+ - name: Meerdere handtekeningen (multisig)
+ date: December 2017
+ status: completed
+- year: 2018
+ accomplishments:
+ - name: Nieuw proof-of-workalgoritme CryptoNoteV7
+ date: 2018-04-06
+ status: completed
+ - name: Netwerkupgrade: minimale ringgrootte verhogen naar 7, multisig integreren, subadressen, PoW-algoritme wijzigen
+ date: 2018-04-06
+ status: completed
+ - name: Getmonero.org vertaald in het Frans en Pools
+ date: 2018-04-24
+ status: completed
+ - name: Ondersteuning van de hardwarewallet Ledger
+ date: 2018-06-04
+ status: completed
+ - name: Alfa-release van Kovri
+ date: 2018-08-01
+ status: completed
+ - name: Nieuw ontwerp Forum Funding System
+ date:
+ status: ongoing
+ - name: Implementatie van BulletProofs in plaats van RingCT om transacties kleiner te maken
+ date:
+ status: ongoing
+ - name: Integratie van Kovri
+ date:
+ status: upcoming
+- year: 2019
+ accomplishments:
+ - name: Oplossingen op de tweede laag voor snelheid en schaalbaarheid
+ date:
+ status: upcoming
+ - name: Meer onderzoeksartikelen van MRL
+ date:
+ status: upcoming
diff --git a/_i18n/ar.yml b/_i18n/ar.yml
index d1a2f7ac..d98874b3 100644
--- a/_i18n/ar.yml
+++ b/_i18n/ar.yml
@@ -7,6 +7,7 @@ langs:
ar: Arabic
ru: Русский
de: Deutsch
+ nl: Nederlands
global:
date: '%Y/%m/%d'
diff --git a/_i18n/de.yml b/_i18n/de.yml
index 546d7cd8..3d6ac2b1 100644
--- a/_i18n/de.yml
+++ b/_i18n/de.yml
@@ -7,6 +7,7 @@ langs:
ar: العربية
ru: Русский
de: Deutsch
+ nl: Nederlands
global:
date: '%Y/%m/%d'
diff --git a/_i18n/en.yml b/_i18n/en.yml
index 9e2e66b4..08b978ab 100644
--- a/_i18n/en.yml
+++ b/_i18n/en.yml
@@ -7,6 +7,7 @@ langs:
ar: العربية
ru: Русский
de: Deutsch
+ nl: Nederlands
global:
date: '%Y/%m/%d'
diff --git a/_i18n/es.yml b/_i18n/es.yml
index b9288986..a7d2c70a 100644
--- a/_i18n/es.yml
+++ b/_i18n/es.yml
@@ -7,6 +7,7 @@
ar: العربية
ru: Русский
de: Deutsch
+ nl: Nederlands
global:
date: '%d/%m/%Y'
diff --git a/_i18n/fr.yml b/_i18n/fr.yml
index f6a11b84..5a8df08c 100644
--- a/_i18n/fr.yml
+++ b/_i18n/fr.yml
@@ -7,6 +7,7 @@ langs:
ar: العربية
ru: Русский
de: Deutsch
+ nl: Nederlands
global:
date: '%d/%m/%Y'
diff --git a/_i18n/it.yml b/_i18n/it.yml
index 3a31b2a5..2dbafa6d 100644
--- a/_i18n/it.yml
+++ b/_i18n/it.yml
@@ -7,6 +7,7 @@ langs:
ar: العربية
ru: Русский
de: Deutsch
+ nl: Nederlands
global:
date: '%Y/%m/%d'
diff --git a/_i18n/nl.yml b/_i18n/nl.yml
new file mode 100644
index 00000000..7bbfbf27
--- /dev/null
+++ b/_i18n/nl.yml
@@ -0,0 +1,641 @@
+langs:
+ en: English
+ es: Español
+ it: Italiano
+ pl: Polski
+ fr: Français
+ ar: العربية
+ ru: Русский
+ de: Deutsch
+ nl: Nederlands
+
+global:
+ date: '%Y/%m/%d'
+ monero: Monero
+ getting_started: Aan de slag
+ copyright: Copyright
+ monero_project: Het Monero-project
+ sitename: getmonero.org, het Monero-project
+ wiki: Moneropedia
+ tags: Artikelen per tag
+ wikimeta: in de Moneropedia, de open encyclopedie van Monero-knowhow
+ tagsmeta: Alle artikelen op het Monero-blog met tags
+ titlemeta: op de site van Monero, een veilige, vertrouwelijke en niet-traceerbare digitale valuta
+ terms: Termen
+ privacy: Privacy
+ copyright: Copyright
+ untranslated: Deze pagina is nog niet vertaald. Wil je deze pagina vertalen? Lees dan de
+ outdatedMax: Deze pagina is verouderd. We raden je af hier gebruik van te maken. Lees in plaats daarvan de
+ outdatedVersion: Engelse versie
+ outdatedMin: Deze pagina is bijgewerkt nadat er een vertaling van is gemaakt. Je kunt deze versie gebruiken, maar die kan onvolledig zijn.
+ upgrade: Zorg dat je software is bijgewerkt voor de netwerkupgrade van 18 oktober, zodat je Monero kunt blijven gebruiken.
+ moreinfo: Meer informatie
+ lang_tag: "@lang_tag_nl"
+
+titles:
+ index: Start
+ whatismonero: Wat is Monero (XMR)?
+ using: Monero gebruiken
+ accepting: Monero accepteren
+ contributing: Monero verbeteren
+ mining: Monero minen
+ faq: Veelgestelde vragen
+ downloads: Downloads
+ allposts: Alle blogposts
+ team: Monero-team
+ hangouts: Ontmoetingsplekken
+ events: Evenementen
+ sponsorships: Sponsors
+ merchants: Winkels en services
+ about: Over Monero
+ roadmap: Planning
+ researchlab: Monero Research Lab
+ moneropedia: Moneropedia
+ userguides: Gebruikershandleidingen
+ developerguides: Handleidingen voor ontwikkelaars
+ technicalspecs: Technische specificaties
+ themoneroproject: Het Monero-project
+ presskit: Monero Press Kit
+ legal: Juridisch
+ 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 per tag
+ library: Bibliotheek
+
+index:
+ page_title: "Monero - veilig, vertrouwelijk, onvolgbaar"
+
+home:
+ translated: "yes"
+ heading2: Vertrouwelijke digitale valuta
+ monero_is_cash: Monero is contant geld voor een verbonden wereld. Het is snel, vertrouwelijk en veilig. Met Monero ben je je eigen bank. Je kunt het veilig uitgeven, want niemand anders kan je saldo bekijken of je activiteit volgen.
+ get_started: Aan de slag
+ why_monero_is_different: Wat Monero anders maakt
+ monero_is_secure: Monero is veilig
+ monero_is_secure_para: Monero is een gedecentraliseerde cryptovaluta, een veilige vorm van digitaal geld, beheerd door een netwerk van gebruikers. Transacties worden bevestigd door verspreide consensus en vervolgens onveranderlijk vastgelegd op de blockchain. Je hoeft geen derde partijen te vertrouwen om je Monero veilig te bewaren.
+ monero_is_private: Monero is vertrouwelijk
+ monero_is_private_para: Monero gebruikt ring-handtekeningen, vertrouwelijke ring-transacties en verborgen adressen om de herkomst, bedragen en bestemmingen van alle transacties te verbergen. Monero biedt alle voordelen van een gedecentraliseerde cryptovaluta, zonder de gebruikelijke nadelen op het gebied van privacy.
+ monero_is_untraceable: Monero is onvolgbaar
+ monero_is_untraceable_para: Zowel verzendende en ontvangende adressen als overgemaakte bedragen worden standaard versleuteld. Transacties op de Monero-blockchain kunnen niet aan een bepaalde gebruiker of identiteit worden gekoppeld.
+ monero_is_fungible: Monero is inwisselbaar
+ monero_is_fungible_para1: Monero is
+ monero_is_fungible_para2: inwisselbaar
+ monero_is_fungible_para3: (fungibel) omdat het standaard vertrouwelijk is. Er kunnen niet bepaalde eenheden Monero worden geblokkeerd door verkopers of exchanges omdat ze betrokken waren bij eerdere transacties.
+ downloads: Downloads
+ downloads_windows: Monero voor Windows
+ downloads_mac: Monero voor Mac
+ downloads_linux: Monero voor Linux
+ downloads_blockchain: Nieuwste blockchain
+ different_system: Heb je een ander besturingssysteem?
+ view_all_downloads: Bekijk hier alle beschikbare downloads.
+ latest_news: Laatste nieuws
+ more_news: Meer nieuws
+ moneropedia: Moneropedia
+ moneropedia_para: Wil je de betekenissen van termen en begrippen die in Monero worden gebruikt opzoeken? Hier vind je een uitleg in alfabetische volgorde van termen die in de projecten Monero en Kovri worden gebruikt.
+ moneropedia_button: Moneropedia lezen
+ user_guides: Gebruikershandleidingen
+ user_guides_para: Stapsgewijze instructies verdeeld in categoriëen voor allerlei Monero-gerelateerde onderwerpen, van het aanmaken van een portemonnee tot het ondersteunen van het netwerk, en zelfs hoe je deze website bewerkt.
+ user_guides_button: Gebruikershandleidingen lezen
+ faq: Veelgestelde vragen
+ faq_para: In de loop van de jaren zijn er veel vragen aan ons gesteld. We hebben ze voor het gemak verzameld in een diepgravende en gevarieerde FAQ. En als je vragen hier niet bij staan, kun je altijd vragen stellen aan de community.
+ faq_button: Antwoorden lezen
+
+hangouts:
+ translated: "yes"
+ intro: De Monero-community bestaat uit allerlei soorten mensen. Waar we ook vandaan komen, we ontmoeten elkaar op bepaalde plekken online. De belangrijkste staan hieronder. Kom eens langs!
+ resources: Voor werkgroepen
+ resources_para: Voor het ondersteunen van werkgroepen die zichzelf organiseren zijn er verschillende communicatiekanalen waarin de Monero-community contact kan houden en projecten kan plannen. Er zijn zelfs relays van Mattermost naar de populairste Monero-kanalen op IRC.
+ irc: IRC-kanalen
+ irc_para: De Monero-community gebruikt allerlei IRC-kanalen, voor verschillende doelen. Sommige zijn bedoeld voor werkoverleg, sommige gewoon om te chatten. Hieronder staan de populairste kanalen.
+ stack_exchange: Stack Exchange
+ stack_exchange_para: De Monero Stack Exchange is een handige plek waar je snel vragen kunt stellen en antwoorden krijgt. Hieronder vind je een aantal voorbeelden van goed geformuleerde vragen een antwoorden over veel voorkomende problemen.
+ stack_exchange_link: Bezoek Stack Exchange
+ irc_channels:
+ - kanaal: monero
+ description: In dit kanaal bespreken we alle Monero-gerelateerde zaken.
+ - channel: monero-community
+ description: Hier komt de Monero-community bijeen en worden ideeën besproken.
+ - channel: monero-dev
+ description: Hier bespreken onze vele bijdragers en ontwikkelaars het ontwikkelen van Monero.
+ - channel: monero-markets
+ description: Hier wordt de prijs van Monero en andere coins besproken.
+ - channel: monero-offtopic
+ description: Hier kun je met andere Monero-gebruikers chatten over dingen die niet met Monero te maken hebben.
+ - channel: monero-otc
+ description: OTC = over the counter. Hier kun je onderhands XMR kopen of verkopen.
+ - channel: monero-pools
+ description: Dit is de plek voor vragen en discussie over minen.
+ - channel: monero-research-lab
+ description: Onderzoek naar financiële privacy met cryptovaluta.
+ - channel: monero-translations
+ description: Over het lokaliseren van Monero in andere talen.
+ - channel: monero-hardware
+ description: Hardware wallets maken om je Monero veilig te bewaren.
+ - channel: kovri
+ description: In dit kanaal bespreken we alle Kovri-gerelateerde zaken.
+ - channel: kovri-dev
+ description: Hier bespreken onze vele bijdragers en ontwikkelaars het ontwikkelen van Kovri.
+
+merchants:
+ translated: "yes"
+ intro1: Allerlei soorten verkopers stellen de financiële privacy die Monero biedt op prijs. Hieronder volgt een lijst met de verkopers die momenteel Monero accepteren voor goederen en diensten, voorzover we weten. Accepteert een bedrijf geen Monero meer, of wil je jouw bedrijf laten vermelden?
+ intro2: Open een GitLab-issue en laat het ons weten.
+ disclaimer: |
+ "Disclaimer: deze links worden uitsluitend aangeboden ter informatie en voor het gemak van de lezer; ze vormen geen goedkeuring door de Monero-community van enige producten, diensten of standpunten van de vermelde bedrijven, organisaties en personen. De Monero-community is niet aansprakelijk voor de juistheid, de wettigheid of de inhoud van deze externe websites. Neem contact op met de beheerder van een externe website voor vragen over de inhoud ervan. Volg altijd het principe *caveat emptor* (let op, koper): je bent zelf verantwoordelijk voor het controleren van verkopers. Wees altijd voorzichtig bij het doen van aankopen op internet."
+
+sponsorships:
+ translated: "yes"
+ intro: De volgende bedrijven ondersteunen het Monero-project om ons te helpen financiële privacy voor iedereen mogelijk te maken. We zijn dankbaar voor hun bijdragen. Stuur een e-mail naar dev@getmonero.org als je het Monero-project wilt sponsoren en op deze pagina vermeld wilt worden.
+
+team:
+ translated: "yes"
+ core: Kernteam
+ developers: Ontwikkelaars
+ developers_para1: Meer dan 500 personen hebben in de loop van de tijd bijgedragen aan het Monero-project. Zie voor een complete lijst de
+ developers_para2: pagina met bijdragers bij OpenHub.
+ developers_para3: De volgende personen hebben meer dan hun best gedaan voor Monero
+ community: Community
+ mrl: Research Lab
+ thanks: Bijzondere dank
+
+downloads:
+ translated: "yes"
+ choose: Kies je systeem
+ sourceblockchain: Code & blockchain
+ mobilelight: Mobiel & licht
+ hardware: Hardware
+ intro1: Heb je hulp nodig bij het kiezen van de juiste applicatie? Kies dan
+ intro2: hier
+ intro3: voor een kort antwoord en selecteer de geschikte versie voor je besturingssysteem hieronder.
+ note1: "Let op: de SHA256-hashes worden voor het gemak bij de downloads weergegeven, maar je vindt een met GPG ondertekende lijst van de hashes op"
+ note2: en die vormt de officiële lijst, waarbij je de ondertekening controleert op basis van de toepasselijke GPG-sleutel in de broncode (in /utils/gpg_keys).
+ currentversion: Huidige versie
+ sourcecode: Broncode
+ blockchain1: Als je de blockchain liever niet vanaf het begin synchroniseert maar een bootstrap-bestand wil downloaden, kun je
+ blockchain2: via deze link de meest recente bootstrap vinden.
+ blockchain3: Maar het is meestal veel sneller om vanaf het begin te synchroniseren, en dit kost ook veel minder RAM (het importeren vreet werkgeheugen).
+ hardware1: De Monero-community heeft geld ingezameld voor een
+ hardware2: gespecialiseerde hardware-wallet
+ hardware3: waar nu aan gewerkt wordt. Bovendien heeft Ledger sinds CLI 0.12.1 en GUI 0.12.3
+ hardware4: Monero geïntegreerd in hun hardware-wallets.
+ mobilelight1: Dit zijn mobiele portemonnees of light wallets die veilig worden geacht door vertrouwde leden van de community. Als een portemonnee hier niet bij staat, kun je de community vragen om ernaar te kijken. Op de pagina
+ mobilelight2: Ontmoetingsplekken
+ mobilelight3: staat waar je ons kunt vinden.
+ clionly: Alleen opdrachtregeltools
+
+monero-project:
+ translated: "yes"
+ kovri: Het Kovri-project past end-to-endversleuteling toe, zodat noch de afzender, noch de ontvanger van een Monero-transactie zijn of haar IP-adres hoeft te laten zien aan de andere partij, of aan een derde partij (via de blockchain). Hiervoor wordt i2p gebruikt, dezelfde technologie gebruikt die de basis vormt van het darknet (Invisible Internet Protocol). Het project wordt actief ontwikkeld en is nog niet geïntegreerd met Monero.
+ kovri_button: Website van Kovri
+ openalias: Het OpenAlias-project vereenvoudigt cryptovaluta-betalingen met FQDN's (Fully Qualified Domain Names, bijvoorbeeld example.openalias.org) voor Monero-adressen op een manier waarbij de privacy van iedereen beschermd blijft. DIt project is al goed gevorderd en is al geïmplementeerd in veel Monero-portemonnees.
+ openalias_button: Website van OpenAlias
+
+press-kit:
+ translated: "yes"
+ intro1: Hieronder vind je het symbool en logo van Monero. Je kunt de gewenste grootte kiezen of het .ai-bestand downloaden om het logo zelf te bewerken.
+ intro2: Let op: de opties met een witte achtergrond hebben ALLEEN een witte achtergrond onder het Monero-symbool, niet als achtergrond voor de hele afbeelding.
+ intro3: Tenslotte kun je alles op deze pagina in een zip downloaden door
+ intro4: hier te klikken.
+ noback: Geen achtergrond
+ whiteback: Witte achtergrond
+ symbol: Monero-symbool
+ logo: Monero-logo
+ small: Klein
+ medium: Normaal
+ large: Groot
+ symbol_file: .ai-bestand symbool
+ logo_file: .ai-bestand logo
+ documents:
+ - category: Persmap
+ publications:
+ - name: "Quick-Facts Sheet"
+ url_file: "http://www.monerooutreach.org/pubs/2018/QuickFacts/QuickFacts.pdf"
+ abstract: >
+ Een vlot leesbaar document waarin de hoofdpunten van Monero worden uitgelegd: geschiedenis, unieke eigenschappen, technische basis en functies die nog worden ontwikkeld.
+ Zie de website Monero Outreach voor meer informatie.
+
+accepting:
+ translated: "yes"
+ title: Instructies voor de opdrachtregel-interface (CLI)
+ basics: De basis
+ basics_para1: Monero werkt anders dan je misschien gewend bent van andere cryptovaluta (zie @cryptocurrencies). Voor digitale valuta zoals Bitcoin en de vele altcoins die daarvan zijn afgeleid maken betalingssystemen voor verkopers meestal een nieuw ontvangstadres (@address) voor iedere betaling of gebruiker.
+ basics_para2: Maar omdat Monero @stealth-addresses heeft, is het niet nodig om afzonderlijke ontvangstadressen te gebruiken voor elke betaling of gebruiker. Je kunt gewoon één adres als rekening (@account) publiceren. Verkopers die betalingen ontvangen geven de klant een "betalings-ID".
+ basics_para3: "Een @payment-ID is een hexadecimale tekenreeks van 64 tekens, die normaal gesproken door de verkoper wordt gegenereerd. Een voorbeeld van een betalings-ID is:"
+ controleren: Een betaling opzoeken in monero-wallet-cli
+ checking_para1: |
+ Als je een betaling wilt opzoeken met monero-wallet-cli, gebruik je de opdracht "payments" gevolgd door de betalings-ID(s) die je wilt opzoeken. Bijvoorbeeld:
+ checking_para2: Uitleg van het geautomatiseerd opzoeken van betalingen volgt hieronder.
+ receiving: Stap voor stap een betaling ontvangen
+ receiving_list1: Genereer een willekeurige hexadecimale tekenreeks van 64 tekens voor de betaling.
+ receiving_list2: Geef de betalings-ID en het Monero-adres door aan de persoon door wie je wordt betaald.
+ receiving_list3: Zoek de betaling op met de opdracht "payments" in monero-wallet-cli.
+ program: Een betaling geautomatiseerd opzoeken
+ program_para1: Om met een script een betaling op te zoeken, gebruik je de JSON RPC API call get_payments of get_bulk_payments.
+ program_para2: vereist de parameter payment_id met één betalings-ID.
+ program_para3: deze methode heeft de voorkeur en accepteert twee parameters, payment_ids (een JSON-array van betalings-ID's) en een optionele min_block_height (de blokhoogte waar je begint te zoeken).
+ program_para4: |
+ Hier is een voorbeeld van de gegevens die je ontvangt:
+ program_para5: Het is belangrijk om er rekening mee te houden dat de bedragen worden uitgedrukt in de basiseenheden van Monero en niet in de weergave-eenheden die worden gebruikt in applicaties voor eindgebruikers. En omdat een transactie meestal meerdere outputs bevat die bij elkaar het vereiste totaal voor de betaling vormen, moeten de bedragen worden gegroepeerd op de tx_hash of de payment_id en worden opgeteld. Verder kunnen meerdere outputs hetzelfde bedrag hebben, dus probeer nooit de geretourneerde gegevens van één call get_bulk_payments te filteren.
+ program_para6: Voordat je betalingen opzoekt, kun je het beste eerst via de RPC API van de node (de call get_info) opvragen of er nieuwe blokken zijn ontvangen. Meestal zul je dan alleen het laatste ontvangen blok willen scannen door dat blok op te geven als de min_block_height bij get_bulk_payments.
+ scanning: Geautomatiseerd recente betalingen opzoeken
+ scanning_list1: Haal de huidige blokhoogte op van de node en ga alleen verder als deze groter is dan bij de vorige scan
+ scanning_list2: Voer de RPC API call get_bulk_payments uit met je laatste gescande hoogte en de lijst van alle betalings-ID's op je systeem.
+ scanning_list3: Sla de huidige blokhoogte op als de laatste gescande hoogte
+ scanning_list4: Verwijder dubbele treffers op basis van transactiehashes die je al hebt ontvangen en verwerkt.
+
+contributing:
+ translated: "yes"
+ intro: Monero is een door de community gecreëerd open-sourceproject. Hier volgen verschillende manier om het project te steunen.
+ network: Bijdragen aan het netwerk
+ develop: Programmeren
+ develop_para1: Monero is grotendeels geschreven in C++. Het is een gedecentraliseerd project, dus iedereen kan de bestaande code wijzigen of er code aan toevoegen. Pull requests worden toegevoegd op basis van consensus in de community. Zie de pagina
+ develop_para2: repository's
+ develop_para3: en de openstaande
+ develop_para4: issues.
+ full-node: Een volledige node draaien
+ full-node_para: Voer monerod uit met poort 18080 geopend. Als je een volledige node draait, heb je de beste privacy voor je eigen Monero-transacties. Het helpt ook om de blockchain te verspreiden naar nieuwe gebruikers.
+ mine: Minen
+ mine_para1: Minen zorgt ervoor dat het Monero-netwerk gedecentraliseerd en veilig blijft. Minen op de achtergrond kun je inschakelen in de grafische interface en de opdrachtregel-interface van Monero. Meer informatie over minen vind je
+ mine_para2: hier
+ ffs: Bekijk het Forum Funding System
+ ffs_para1: Monero gebruikt een
+ ffs_para2: forum funding system
+ waarbij projecten worden voorgesteld en door de community gefinancierd. De financiering wordt in bewaring gehouden en uitgekeerd aan de ontwikkelaars nadat ze een mijlpaal hebben bereikt. Iedereen kan een nieuw voorstel doen of projecten financieren.
+ donate: Doneren
+ donate_para1: Het ontwikkelen van Monero wordt ondersteund door giften en
+ donate_para2: sponsoring.
+ donate-xmr: Monero doneren
+ donate-xmr_para: Giften kun je verzenden naar
+ or: of
+ donate-btc: Bitcoin doneren
+ donate-btc_para: Giften kun je verzenden naar
+ donate-other: Overig
+ donate-other_para1: E-mail
+ donate-other_para2: voor andere manieren om geld te geven of als je een sponsor van het Monero-project wilt worden.
+
+faq:
+ translated: "yes"
+ q1: Waardoor heeft Monero waarde?
+ a1: Monero heeft waarde omdat mensen het willen kopen. Als niemand Monero zou willen kopen, dan zou het geen waarde hebben. De prijs van Monero stijgt als de vraag groter is dan het aanbod en daalt als het aanbod groter is dan de vraag.
+ q2: Hoe kan ik Monero kopen?
+ a2: Je kunt Monero kopen op een exchange of van een particulier. Maar je kunt ook proberen om de beloning per blok te verdienen door Monero te minen.
+ q3: Wat is een hersteltekst?
+ a3: Een hersteltekst is een reeks van 25 woorden waarmee je overal je account kunt herstellen. Bewaar deze woorden veilig een laat ze aan niemand anders zien. Met de hersteltekst kun je je account herstellen, zelfs als je computer crasht.
+ q4: Hoe is de privacy van Monero anders dan andere cryptovaluta?
+ a4: |
+ Monero gebruikt drie verschillende privacytechnieken: ring signatures (ring-handtekeningen), ring confidential transactions (RingCT, vertrouwelijke ringtransacties) en stealth addresses (verborgen adressen). Hiermee worden respectievelijk de afzender, het bedrag en de ontvanger in een transactie verborgen. Alle transacties op het netwerk zijn verplicht vertrouwelijk. Het is onmogelijk om per ongeluk een openbare transactie te versturen. Deze eigenschap is uniek voor Monero. Je hoeft niemand anders te vertrouwen om je privacy te beschermen.
+ q5: Waarom duurt het zo lang voordat mijn portemonnee is gesynchroniseerd?
+ a5: Als je een lokaal een volledige node draait, moet je de hele blockchain naar je computer downloaden. Dit kan lang duren, vooral op een oude harde schijf of via een langzame internetverbinding. Als je een externe node gebruikt, moet je computer nog steeds een kopie van alle outputs opvragen. Dat kan een paar uur duren. Even geduld alsjeblieft. Als je een beetje privacy wilt opofferen voor sneller synchroniseren, zou je een 'light wallet' (lichte portemonnee) kunnen gebruiken.
+ q6: Wat is het verschil tussen een light wallet en een normale portemonnee?
+ a6: Bij een light wallet geef je je alleen-lezen sleutel aan een node, die namens jou op de blockchain binnenkomende transacties voor jouw adres zoekt. Deze node weet wanneer je geld ontvangt, maar niet hoeveel je ontvangt, van wie je het ontvangt of naar wie je geld stuurt. Afhankelijk van je portemonneesoftware kun je een eigen node gebruiken om je privacy te beschermen. Voor meer privacy gebruik je een normale portemonnee die je met je eigen node kunt gebruiken.
+ q7: Wat is het verschil tussen Monero en Bitcoin?
+ a7: Monero is niet gebaseerd op Bitcoin. Het is gebaseerd op het CryptoNote-protocol. Bitcoin is een volledig transparant systeem, waarbij iedereen precies kan zien hoeveel geld van de ene gebruiker naar de andere wordt verzonden. Monero verbergt deze informatie in alle transacties om de privacy van de gebruiker te beschermen. Er zijn ook andere verschillen, bijvoorbeeld een dynamische blokgrootte en dynamische transactiekosten, het onbruikbaar maken van gespecialiseerde mininghardware en een blijvende uitgifte van munten.
+ q8: Heeft Monero een maximale blokgrootte?
+ a8: Nee, er is in Monero geen harde limiet aan de grootte van blokken. De blokgrootte kan in de loop van de tijd groeien of afnemen op basis van de vraag. Het groeitempo is echter beperkt, zodat het niet uit de hand kan lopen.
+ q9: Wat is een blockchain?
+ a9: Een blockchain is een systeem waarin een kopie van alle transacties op het Monero-netwerk wordt opgeslagen. Om de twee minuten wordt een nieuw blok met de gegevens van de nieuwste transacties toegevoegd aan de blockchain. Met deze keten kan het netwerk verifiëren hoeveel geld de verschillende accounts hebben. Dankzij de blockchain is het netwerk bestand tegen aanvallen en pogingen tot centralisatie.
+ q10: Wat is Kovri?
+ a10: Kovri is I2P-router die in C++ is geschreven. I2P is een verborgen netwerk, net als Tor, maar met een aantal technische verschillen. Kovri is een zelfstandig project, maar werkt samen met Monero en andere projecten. Kovri verbergt het verspreiden van transacties, zodat andere nodes niet kunnen zien wie een transactie heeft gecreëerd. In vijandige omstandigheden kan Kovri worden gebruikt om al het Monero-verkeer via I2P te leiden, zodat anderen niet kunnen zien dat Monero wordt gebruikt. Kovri is momenteel in alfa en is nog niet volledig geïntegreerd met Monero. Lees meer over Kovri op de website van het project.
+ q11: Wat is inwisselbaarheid en waarom is het belangrijk?
+ a11: Inwisselbaarheid (fungibiliteit) is een basiseigenschap van geld, namelijk dat er geen verschil is tussen twee hoeveelheden met dezelfde waarde. Als je een tientje voor twee vijfjes ruilt, dan is dat een gelijke ruil. Maar stel dat iedereen weet dat het tientje eerder is gebruikt om mensen af te persen met ransomware. Zal de ander dan nog steeds willen ruilen? Waarschijnlijk niet, zelfs niet als de eigenaar van het tientje zelf niet bij de ransomware was betrokken. Dit is een probleem, want wie geld ontvangt, zou voortdurend moeten controleren of het ontvangen geld niet besmet is. Monero is inwisselbaar, zodat gebruikers zich hier geen zorgen over hoeven te maken.
+ q12: Als Monero zo vertrouwelijk is, hoe weten we dan dat er niet ongezien XMR bijgemaakt wordt?
+ a12-1: In Monero is elke transactie-output gekoppeld aan een unieke key image die alleen door de houder van die output kan worden gegenereerd. Key images die meer dan één keer worden gebruikt, worden als dubbele uitgaven geweigerd door de miners en kunnen niet worden toegevoegd aan een geldig blok. Wanneer een nieuwe transactie wordt ontvangen, verifiëren de miners dat de key image niet al bestaat voor een eerdere transactie, om dubbele uitgaven te voorkomen.
+ a12-2: We weten ook dat transactiebedragen geldig zijn, ook al is de waarde van de inputs die je besteedt en de waarde van de outputs die je verzendt versleuteld. (Deze waarden worden verborgen voor iedereen behalve de ontvanger.) De bedragen zijn versleuteld met *Pedersen commitments*. Dit betekent dat waarnemers de bedragen van inputs en outputs niet kunnen zien, maar wel berekeningen met de Pedersen commitments kunnen uitvoeren om vast te stellen dat er geen Monero uit het niets is gemaakt.
+ a12-3: Als de versleutelde output-bedragen die je creëert gelijk zijn aan de som van de inputs die je uitgeeft (inclusief een output voor de ontvanger, een output met wisselgeld voor jezelf en de niet-versleutelde transactiekosten), heb je een geldige transactie en weten we dat er geen Monero uit het niets wordt gemaakt. Met Pedersen commitments kan worden geverifieerd dat deze sommen gelijk zijn, maar de waarde in Monero van de beide sommen en van de afzonderlijke inputs en outputs kunnen niet worden bepaald.
+ q13: Is Monero magisch en beschermt het mijn privacy, wat ik ook doe?
+ a13: Monero is niet magisch. Als je Monero gebruikt maar je naam en adres aan een andere partij geeft, zal die niet door toverkracht je naam en adres vergeten. Als je je geheime sleutels weggeeft, kunnen anderen zien wat je hebt gedaan. Als je computer wordt gehackt, kunnen anderen een keylogger installeren. Als je een zwak wachtwoord gebruikt, kan je sleutelbestand met grof geweld worden gekraakt. Als je een back-up in de cloud hebt gemaakt van je hersteltekst, zal je geld in de lucht verdwijnen.
+ q14: Is Monero 100% anoniem?
+ a14: 100% anonimiteit bestaat niet. Je *anonymity set* (de groep mensen waarin je je verstopt) is hooguit de mensen die Monero gebruiken. Sommige mensen gebruiken Monero niet. Er kunnen ook bugs in Monero zitten. Zelfs als er geen bugs in zitten, kunnen er manieren zijn om informatie af te leiden ondanks de privacylagen van Monero. Aanvallen worden alleen maar beter. Ook als je een gordel draagt, kun je nog steeds een dodelijk auto-ongeluk krijgen. Gebruik gezond verstand, wees voorzichtig en pas een verdediging met meerdere lagen toe.
+
+mining:
+ translated: "yes"
+ intro1: Monero is een cryptovaluta die mining voor *proof-of-work* nodig heeft om verspreide consensus te bereiken. Hieronder vind je informatie en hulpmiddelen waarmee je kunt beginnen te minen.
+ intro2: Het Monero-project ondersteunt niet een bepaalde pool, software of hardware. De onderstaande gegevens worden alleen ter informatie aangeboden.
+ support: Ondersteuning
+ support_para1: Zie
+ support_para2: Ontmoetingsplekken
+ support_para3: /r/moneromining (Engels)
+ support_para4: en
+ pools: Pools
+ pools_para1: Een lijst van betrouwbare Monero-pools vind je
+ pools_para2: hier.
+ benchmarking: Benchmarks voor hardware
+ benchmarking_para1: Kijk hier
+ benchmarking_para2: voor een lijst met videokaarten/CPU's en de bijbehorende hashrate.
+ software: Miningsoftware
+ software_para: Let op: bij sommige miningprogramma's krijgen de ontwikkelaars een vergoeding.
+
+using:
+ translated: "yes"
+ intro: Betalen met Monero kan heel makkelijk zijn. Deze pagina helpt je daarbij.
+ learn: 1. Leren
+ learn_para1: Monero is een veilige, vertrouwelijke en niet volgbare cryptovaluta. De ontwikkelaars en de community staan voor het handhaven van deze waarden. Je kunt meer leren door de pagina
+ learn_para2: Wat is Monero?
+ learn_para3: te lezen. De
+ learn_para4: broncode
+ learn_para5: is ook beschikbaar voor controle en discussie.
+ support: 2. Hulp vragen
+ support_para1: Er is een grote, behulpzame community die je graag helpt als je een probleem tegenkomt. Zie de pagina
+ support_para2: Ontmoetingsplekken
+ support_para3: voor meer informatie.
+ generate: 3. Een portemonnee genereren
+ generate_para1: Een Monero-portemonnee is nodig om je eigen geld veilig te bewaren. Zie de pagina
+ generate_para2: Downloadpagina
+ generate_para3: voor een lijst met beschikbare portemonnee-software.
+ generate_para4: De makkelijkste manier om een Monero-node te draaien, zonder de bandbreedte van je thuisaansluiting te gebruiken, is door een VPS (Virtual Private Server) aan te schaffen. We raden je aan om
+ generate_para5: gebruik te maken van de
+ generate_para6: boncode om een korting te krijgen op deze VPS die met $6 per maand al voordelig is. Als je deze kortingscode en/of
+ generate_para7: onze partnerlink
+ generate_para8: gebruikt, draag je ook bij aan het financieren van Monero-ontwikkelaars.
+ acquire: 4. Monero kopen
+ acquire_para1: Monero kun je kopen bij een
+ acquire_para2: exchange
+ acquire_para3: met euro's, dollars of andere cryptovaluta. Een andere manier om aan Monero te komen is door te
+ acquire_para4: minen
+ - het uitvoeren van uitvoerige berekeningen waardoor transacties onveranderlijk worden vastgelegd op de blockchain.
+ send-receive: 5. Monero verzenden en ontvangen
+ send-receive_para1: Hoe je Monero verzendt en ontvangt lees je in de
+ send-receive_para2: handleiding.
+ transact: 6. Betalen met Monero
+ transact_para1: Je kunt allerlei goederen en diensten kopen met Monero. Er staat een lijst op de
+ transact_para2: pagina Verkopers.
+
+what-is-monero:
+ translated: "yes"
+ need-to-know: Wat je moet weten
+ leading: Monero is de beste van de cryptovaluta's die zich richten op vertrouwelijke en censuurbestendige transacties.
+ leading_para1: De meeste bestaande cryptovaluta, zoals Bitcoin en Ethereum, hebben transparante blockchains, zodat de hele wereld transacties openlijk kan verifiëren en volgen. Bovendien kunnen verzend- en ontvangstadressen voor die transacties mogelijk worden gekoppeld aan de echte identiteit van mensen.
+ leading_para2: Monero gebruikt cryptografie om zowel verzend- en ontvangstadressen als de verzonden bedragen te verbergen.
+ confidential: Monero-transacties zijn vertrouwelijk en niet volgbaar.
+ confidential_para1: In elke Monero-transactie worden standaard zowel de verzend- en ontvangstadressen als de verzonden bedragen verborgen. Door de verplichte privacy verbetert de activiteit van elke Monero-gebruiker de privacy van alle andere gebruikers, in tegenstelling tot optioneel transparante cryptovaluta (bijvoorbeeld Zcash).
+ confidential_para2: Monero is inwisselbaar. Doordat we alles verbergen, kan je Monero niet 'besmet' worden verklaard als het eerder in verdachte transacties is gebruikt. Dit betekent dat je Monero altijd wordt geaccepteerd en censuur niet mogelijk is.
+ confidential_para3: Met het Kovri-project,
+ confidential_para4: dat momenteel wordt ontwikkeld
+ confidential_para5: ", worden transacties omgeleid en versleuteld via nodes van I2P, het Invisible Internet Project. Hierdoor wordt het IP-adres van de afzender verborgen, om nog meer bescherming te bieden tegen observatie van het netwerk."
+ grassroots: Monero is een community van vrijwilligers waar de beste onderzoekers en programmeurs van cryptovaluta op af komen.
+ grassroots_para1: Meer dan
+ grassroots_para2: 500 ontwikkelaars
+ grassroots_para3: hebben bijgedragen aan het Monero-project, waaronder 30 *core developers*. Forums en chatkanalen zijn gastvrij en actief.
+ grassroots_para4: Het Monero Research Lab, het Core Development Team en de andere ontwikkelaars verleggen steeds de grenzen van wat mogelijk is met privacy en beveiliging van cryptovaluta.
+ grassroots_para5: Monero is geen bedrijf. Het wordt ontwikkeld door experts in cryptografie en gedistribueerde systemen van over de hele wereld, die zonder vergoeding werken of worden gefinancierd door giften van de community. Hierdoor kan Monero niet worden verboden door een bepaald land of beperkt in een bepaald rechtsgebied.
+ electronic: Monero is elektronisch geld voor wereldwijde snelle, goedkope betalingen.
+ electronic_para1: Er zijn geen 'valutadagen' en er is geen risico van frauduleuze terugboekingen. Er zijn geen kapitaalrestricties mogelijk: maatregelen die het gebruik van traditionele valuta's beperken, soms in extreme mate, in landen met een instabiele economie.
+ videos: Video's over Monero (Engels)
+
+about:
+ translated: "yes"
+ history: Korte geschiedenis
+ history_para1: Monero is gestart in april 2014. Het was een eerlijke, vooraf aangekondigde toepassing van de CryptoNote-referentiecode. Er was geen premine of instamine en ontwikkelaars ontvangen geen deel van de beloning per blok. Zie de oorspronkelijke discussie
+ history_para2: op Bitcointalk.
+ history_para3: De oprichter, thankful_for_today, stelde een aantal controversiële wijzigingen voor waar de community het niet mee eens was. Er volgde een conflict en het Monero Core Team maakte een fork van het project. De community volgde dit nieuwe kernteam. Sindsdien leidt het Core Team het project.
+ history_para4: Monero is sinds de start op verschillende punten verbeterd. De blockchain is gemigreerd naar een andere databasestructuur die efficiënter is en meer flexibiliteit biedt, een minimale grootte van ring-handtekeningen is ingesteld zodat alle transacties verplicht vertrouwelijk zijn, en RingCT is ingevoerd om de transactiebedragen te verbergen. Bijna alle veranderingen betekenden verbeteringen van de veiligheid en privacy of maakten het gebruik makkelijker. Monero wordt nog steeds ontwikkeld met privacy en veiligheid als eerste doel. Gebruiksgemak komt op de tweede plaats.
+ values: Onze waarden
+ values_para: Monero is meer dan een technologie. Het is ook waar de technologie voor staat. Hieronder volgen een paar belangrijke principes.
+ security: Veiligheid
+ security_para: Gebruikers moeten Monero kunnen vertrouwen met hun transacties, zonder het risico van fouten of aanvallen. Monero geeft de volledige beloning voor elk blok aan de miners, de belangrijkste deelnemers van het netwerk die voor deze beveiliging zorgen. Transacties zijn cryptografisch beveiligd met de nieuwste en meest robuuste versleutelingstechnieken die beschikbaar zijn.
+ privacy: Privacy
+ privacy_para: Monero neemt privacy serieus. Monero moet gebruikers in een rechtszaak kunnen beschermen en in extreme gevallen zelfs tegen de doodstraf. Dit niveau van privacy moet volledig toegankelijk zijn voor alle gebruikers, of ze nu technologisch begaafd zijn of geen idee hebben hoe Monero werkt. Gebruikers moeten zoveel vertrouwen in Monero kunnen hebben dat ze zich niet gedwongen voelen om hun uitgavenpatroon te veranderen uit angst dat anderen er achter komen.
+ decentralization: Decentralisatie
+ decentralization_para: We doen er alles aan om Monero zo gedecentaliseerd mogelijk te maken. Je hoeft niemand op het netwerk te vertrouwen en Monero wordt niet door één grote groep uitgevoerd. Dankzij een toegankelijk *Proof of Work*-algoritme kun je Monero makkelijk minen op normale computers. Dat maakt het voor één partij moeilijk om een grote invloed als miner te kopen. In de toekomst zullen nodes contact met elkaar maken via I2P om censuur te vermijden en te voorkomen dat gevoelige informatie bekend wordt. Beslissingen over het ontwikkelen van Monero zijn volledig openbaar en iedereen kan erover meepraten. Er worden volledige logs gepubliceerd van de online vergaderingen van ontwikkelaars.
+
+
+developer-guides:
+ translated: "no"
+ outdated: "Let op: de onderstaande handleidingen zijn onlangs vernieuwd en worden door de community bijna up-to-date gehouden. Maar methoden worden vaak toegevoegd, verwijderd of bijgewerkt, dus het is mogelijk dat ze hier niet allemaal correct worden beschreven."
+ rpc: RPC-documentatie
+ daemonrpc: Daemon RPC Documentation
+ walletrpc: Wallet RPC Documentation
+ soon: Binnenkort meer...
+
+user-guides:
+ translated: "yes"
+ general: Algemeen
+ mining: Mining
+ recovery: Herstellen
+ wallets: Portemonnees
+ offline-backup: Een offline back-up maken
+ vps-node: Een node op een VPS draaien
+ import-blockchain: De Monero-blockchain importeren
+ monero-tools: Monero-tools
+ purchasing-storing: Monero kopen en veilig opslaan
+ verify-allos: Binaries verifiëren op een opdrachtregel in Linux, Mac of Windows (geavanceerd)
+ verify-windows: Binaries verifiëren in Windows (voor beginners)
+ mine-on-pool: Minen via een pool met xmr-stak-cpu
+ solo-mine: Solo minen met de grafische interface (GUI)
+ mine-docker: Minen met Docker en XMRig
+ locked-funds: Vergrendeld geld ontgrendelen
+ restore-account: Je account herstellen
+ qubes: CLI-portemonnee isoleren van node met Qubes en Whonix
+ cli-wallet: Aan de slag met de portemonnee in de opdrachtregel (CLI)
+ remote-node-gui: Verbinding maken met een externe node in de grafische interface (GUI)
+ view-only: Een alleen-lezen portemonnee maken
+ prove-payment: Betalingen bewijzen
+ restore-from-keys: Portemonnee herstellen met sleutels
+ nicehash: Monero (XMR) minen zonder miningapparatuur
+ ledger-wallet-cli: Een Monero-portemonnee op een Ledger maken met de opdrachtregel (monero-wallet-cli)
+
+roadmap:
+ translated: "yes"
+ completed: Voltooide taak
+ ongoing: Lopende taak
+ upcoming: Komende taak
+ future: Toekomst
+
+
+research-lab:
+ translated: "yes"
+ intro: Monero werkt niet alleen aan een inwisselbare valuta, maar doet ook onderzoek naar financiële privacy op het gebied van cryptovaluta. Hieronder vind je het werk van ons eigen Monero Research Lab. En er komen nog meer papers aan.
+ mrl_papers: Monero Research Lab Papers (Engels)
+ abstract: Samenvatting
+ introduction: Inleiding
+ read-paper: Paper lezen
+ mrl1: A Note on Chain Reactions in Traceability in CryptoNote 2.0
+ mrl1_abstract: Dit onderzoeksbulletin beschrijft een plausibele aanval op een anonimiteitssysteem dat is gebaseerd op ring-handtekeningen. Als aanleiding gebruiken we het cryptovaluta-protocol CryptoNote 2.0, dat onder de naam Nicolas van Saberhagen is gepubliceerd, waarbij 2012 als jaar van publicatie is vermeld. Eerder is aangetoond dat de onvolgbaarheid waarmee een eenmalig sleutelpaar wordt verborgen kan afhangen van de onvolgbaarheid van alle sleutels waarmee die ring-handtekening wordt gemaakt. Hierdoor zou er een kettingreactie van volgbaarheid tussen ring-handtekeningen kunnen optreden, met als gevolg een gevaarlijk verminderde onvolgbaarheid in het hele netwerk als parameters slecht zijn gekozen en een aanvaller een bepaald percentage van het netwerk bezit. De handtekeningen zijn echter nog steeds eenmalig, dus een dergelijke aanval is niet per se schadelijk voor de anonimiteit van gebruikers. Maar zo'n aanval zou CryptoNote wel minder bestendig tegen blockchain-analyse kunnen maken. Dit onderzoeksbulletin is niet onderworpen aan peer review en geeft alleen de resultaten van intern onderzoek weer.
+ mrl2: Counterfeiting via Merkle Tree Exploits within Virtual Currencies Employing the CryptoNote Protocol
+ mrl2_abstract: Op 4 september 2014 werd een ongebruikelijke en originele aanval op het cryptovaluta-netwerk van Monero uitgevoerd. Door deze aanval werd het netwerk verdeeld in twee afzonderlijke delen die de geldigheid van het andere deel niet erkenden. Dit had allerlei gevolgen, die nog niet allemaal bekend zijn. Er was bijvoorbeeld een korte periode waarin de aanvaller een soort van valsemunterij kon uitvoeren. Dit onderzoeksbulletin beschrijft tekortkomingen in de CryptoNote-referentiecode waardoor deze aanval mogelijk is, het beschrijft de oplossing die aanvankelijk is voorgesteld door Rafal Freeman van Tigusoft.pl en vervolgens door het CryptoNote-team, het beschrijft de huidige oplossing in de Monero-broncode en het legt uit wat het schadelijke blok precies met het netwerk heeft gedaan. Dit onderzoeksbulletin is niet onderworpen aan peer review en geeft alleen de resultaten van intern onderzoek weer.
+ mrl3: Monero is Not That Mysterious
+ mrl3_abstract: Er is onlangs her en der op het internet angst gezaaid over de CryptoNote-broncode en het CryptoNote-protocol, op grond van het feit dat het ingewikkelder is dan bijvoorbeeld Bitcoin. Met deze notitie is wil ik enkele misverstanden ophelderen en hopelijk iets van het mysterie rond de ring-handtekeningen van Monero wegnemen. Om te beginnen vergelijk ik de wiskunde in de ring-handtekeningen van CryptoNote (zoals beschreven in [CN]) met de wiskunde in [FS] waarop CryptoNote is gebaseerd. Vervolgens vergelijk ik de wiskunde van de ring-handtekening met wat werkelijk in de CryptoNote-broncode staat.
+ mrl4: Improving Obfuscation in the CryptoNote Protocol
+ mrl4_abstract: We beschrijven verschillende aanvallen met blockchain-analyse waarmee de onvolgbaarheid van het protocol CryptoNote 2.0 zou kunnen worden aangetast. We analyseren mogelijke oplossingen, bespreken de voor- en nadelen van deze oplossingen en we raden verbeteringen van het Monero-protocol aan waarmee deze cryptovaluta op de lange termijn hopelijk beter bestand zal zijn tegen blockchain-analyse. Onze aanbevolen verbeteringen van Monero zijn onder meer: een minimale mixin van n = 2 externe outputs per ring-handtekening op protocolniveau voor het hele netwerk, een verhoging van deze waarde tot n = 4 op protocolniveau na twee jaar, en voorlopig een standaardwaarde van n = 4 op het niveau van de portemonnee. We raden ook aan om Monero-uitvoer te verzenden in de vorm van een torrent. Verder bespreken we een niet-uniforme, leeftijdsafhankelijke methode om mixins te selecteren, waarmee de andere vormen van blockchain-analyse die hier zijn vermeld, kunnen worden vermeden, maar om verschillende redenen doen we geen formele aanbevelingen over het implementeren hiervan. De consequenties van deze verbeteringen worden ook uitgelegd. Dit onderzoeksbulletin is niet onderworpen aan peer review en geeft alleen de resultaten van intern onderzoek weer.
+ mrl5: Ring Signature Confidential Transactions
+ mrl5_abstract: In dit artikel wordt een methode geïntroduceerd voor het verbergen van transactiebedragen in de sterk gedecentraliseerde anonieme cryptovaluta Monero. Net als Bitcoin is Monero een cryptovaluta die wordt verspreid via een proces van *mining* voor *proof of work*. Het oorspronkelijke Monero-protocol was gebaseerd op CryptoNote, waarin ring-handtekeningen en eenmalige sleutels worden gebruikt om de herkomst en bestemming van transacties te verbergen. Onlangs heeft Bitcoin Core-ontwikkelaar Gregory Maxwell een methode besproken en geïmplementeerd om het bedrag van een transactie te verbergen met een *commitment scheme* (verbintenis). In dit artikel wordt een nieuw type ring-handtekening beschreven: een *Multi-layered Linkable Spontaneous Anonymous Group*. Hiermee kunnen bedragen, afzenders en ontvangers worden verborgen met redelijke efficiëntie, terwijl de hoeveelheid gegenereerde coins kan worden gecontroleerd zonder dat je iemand hoeft te vertrouwen. Er worden een aantal uitbreidingen van het protocol voorgesteld, namelijk *Aggregate Schnorr Range Proofs* en *Ring Multisignature*. De auteur wil hierbij aantekenen dat vroege schetsen van dit artikel zijn gepubliceerd binnen de Monero-community en op het IRC-kanaal bitcoin-research. Hashes op de blockchain van schetsen zijn beschikbaar in [14], waaruit blijkt dat dit werk is begonnen in de zomer van 2015 en voltooid in het begin van oktober 2015. Er is ook een e-print beschikbaar op http://eprint.iacr.org/2015/1098.
+ mrl6: An Efficient Implementation of Monero Subadresses
+ mrl6_abstract: Gebruikers van de cryptovaluta Monero die adressen willen hergebruiken zonder dat ze aan elkaar kunnen worden gekoppeld, moeten afzonderlijke portemonnees gebruiken. Daarvoor moeten ze binnenkomende transacties voor elke portemonnee opzoeken. We documenteren een nieuw systeem van adressen waarbij een gebruiker één hoofdadres voor een portemonnee heeft en een onbeperkt aantal subadressen die niet aan elkaar gekoppeld kunnen worden. Elke transactie hoeft maar één keer gescand te worden om te bepalen of deze bestemd is voor een van de subadressen van de gebruiker. Dit systeem ondersteunt ook meerdere outputs naar andere subadressen en is net zo efficiënt als traditionele transacties.
+ mrl7: Sets of Spent Outputs
+ mrl7_abstract: In deze technische notitie wordt het begrip 'uitgegeven outputs' gegeneraliseerd volgens de elementaire verzamelingenleer. We vatten allerlei eerder onderzoek naar het aanwijzen van dergelijke outputs samen. We kwantificeren de gevolgen van deze analyse op de Monero-blockchain en geven een kort overzicht van tegenmaatregelen.
+ mrl8: Dual Linkable Ring Signatures
+ mrl8_abstract: Dit bulletin beschrijft een aanpassing van het koppelen van ring-handtekeningen in Monero waardoor outputs met een dubbele sleutel worden toegestaan als deelnemers aan een ring. Key images worden gekoppeld aan de eenmalige openbare sleutels van beide outputs, waardoor wordt voorkomen dat de beide sleutels in de transactie afzonderlijk kunnen worden uitgegeven. Deze methode kan worden toegepast in niet-interactieve terugbetalingen. We bespreken de gevolgen van het systeem voor de veiligheid.
+ mrl9: Thring Signatures and their Applications to Spender-Ambiguous Digital Currencies
+ mrl9_abstract: We presenteren ring multi-signatures met een drempel (thring signatures) voor gezamenlijke berekening van ring-handtekeningen, we presenteren een spel met existentiële vervalsing voor thring signatures en we bespreken toepassingen van thring signatures in digitale valuta met atomic swaps tussen blockchains waarbij de afzender ambigu is voor vertrouwelijke bedragen zonder trusted setup. We presenteren een implementatie van thring signatures onder de naam 'linkable spontaneous threshold anonymous group signatures', en we bewijzen dat deze implementatie niet existentieel vervalst kan worden.
+ mrl10: Discrete Logarithm Equality Across Groups
+ mrl10_abstract: Deze technische notitie beschrijft een algoritme waarmee kennis van hetzelfde discrete logaritme tussen verschillende groepen kan worden bewezen. Hierin wordt de gedeelde waarde uitgedrukt als een scalaire weergave van bits, en wordt een verzameling ring-handtekeningen gebruikt om te bewijzen dat alle bits een geldige waarde hebben die hetzelfde is (tot een bepaalde equivalentie) in beide scalaire groepen.
+ cryptonote: Cryptonote-whitepapers
+ cryptonote-whitepaper: Cryptonote Whitepaper
+ cryptonote-whitepaper_para: Dit is het oorspronkelijke Cryptonote-paper, geschreven door het Cryptonote-team. Het geeft een indruk van hoe het Cryptonote-algoritme in het algemeen werkt.
+ annotated: Geannoteerd whitepaper
+ annotated_para: Het Monero Research Lab heeft een geannoteerde versie van het Cryptonote-whitepaper gepubliceerd. Dit is een soort informele review per regel van de beweringen die in het whitepaper worden gedaan. Sommige van de moeilijkste begrippen worden ook in relatief begrijpelijke termen uitgelegd.
+ brandon: Review van het whitepaper door Brandon Goodell
+ brandon_para: Dit is een formele review van het oorspronkelijke Cryptonote-paper door MRL-onderzoeker Brandon Goodell. Hij maakt een diepgaande analyse van de beweringen en berekeningen in het Cryptonote-paper.
+
+
+specs:
+ translated: "yes"
+ fair_title: Geen premine, geen instamine, geen token
+ fair_premine: Er is geen premine of instamine van Monero geweest
+ fair_token: Monero heeft nooit een token verkocht
+ fair_presale: Er is geen enkele presale of voorverkoop van Monero geweest
+ pow_title: Proof of Work
+ pow_name: CryptoNight
+ pow_disclaimer: Kan in de toekomst veranderen
+ diff_title: Herberekening moeilijkheidsgraad
+ diff_freq: Ieder blok
+ diff_base: Gebaseerd op de laatste 720 blokken, maar zonder de 20% kortste en langste tijden
+ block_time_title: Bloktijd
+ block_time_duration: 2 minuten
+ block_time_disclaimer: Kan in de toekomst veranderen, maar de uitgiftecurve verandert niet
+ block_reward_title: Beloning per blok
+ block_reward_amount: Neemt gelijkmatig af, met een malus voor blokken die groter zijn dan de mediaan van de laatste 100 blokken (M100)
+ block_reward_example1: Zie de coinbase-transactie in het
+ block_reward_example_link: laatste blok
+ block_reward_example2: voor de huidige beloning
+ block_size_title: Blokgrootte
+ block_size: Dynamisch, maximaal 2 * M100
+ block_emission_title: Uitgiftecurve
+ block_emission_main: "Eerst de gewone curve: ~18.132 miljoen coins eind mei 2022"
+ block_emission_tail: "Daarna de blijvende uitgifte: 0,6 XMR per blok om de 2 minuten, nadat de gewone uitgifte klaar is, wat een steeds verder dalende inflatie van < 1% oplevert.
+ block_emission_disclaimer1: Zie
+ block_emission_disclaimer_link: grafieken en details
+ supply_title: Maximale geldhoeveelheid
+ supply_amount: Oneindig
+ sender_privacy_title: Privacy afzender
+ sender_privacy_mode: Ring-handtekeningen
+ recipient_privacy_title: Privacy ontvanger
+ recipient_privacy_mode: Stealth addresses
+ amount_hidden_title: Verborgen bedragen
+ amount_hidden_mode: Vertrouwelijke ring-transacties
+
+library:
+ translated: "yes"
+ description: "Hier volgen publicaties, boeken en tijdschriften die je kunt downloaden."
+ books:
+ - category: Boeken
+ publications:
+ - name: "Zero to Monero"
+ file: "Zero-to-Monero-1-0-0.pdf"
+ abstract: >
+ Een uitgebreide conceptuele en technische uitleg van Monero.
+ We proberen voor iedereen die elementaire algebra en eenvoudige informaticabegrippen zoals de weergave van cijfers in bits begrijpt, diepgaand en compleet uit te leggen hoe Monero werkt en hoe nuttig en mooi cryptografie kan zijn.
+ - name: "Mastering Monero (preview)"
+ file: "Mastering-Monero-Preview.pdf"
+ abstract: >
+ Een handleiding tot de schijnbaar ingewikkelde wereld van Monero.
+ Met onder meer:
+
- Een algemene inleiding tot blockchains en het belang van privacy, geschikt voor niet-technische lezers.
+ - Bespreking van de tekortkomingen van Bitcoin en specifieke oplossingen die worden geboden door Monero.
+ - User stories (scenario's waarin wordt geïllustreerd hoe Monero je privacy beschermt), vergelijkingen, voorbeelden, juridische en ethische discussies, en codefragmenten om technische kernbegrippen te demonstreren.
+ - Details over het gedecentraliseerde netwerk van Monero, de architectuur van het peer-to-peernetwerk, de levenscyclus van een transactie en beveilingsprincipes.
+ - Inleiding tot de technische grondslagen van Monero, bedoeld voor ontwikkelaars, programmeurs, software-architecten en nieuwsgierige gebruikers.
+ - Nieuwe ontwikkelingen zoals Kovri, Bulletproofs, multisignature, hardware wallets etc.
+ Zie de website Mastering Monero voor informatie over de volledige versie.
+ - category: Tijdschriften
+ publications:
+ - name: "Revuo Monero Q4 2017"
+ file: "Revuo-2017-Q4.pdf"
+ abstract: >
+ Kwartaalblad over Monero, vierde kwartaal 2017.
+ In dit nummer nieuws over: ontwikkeling, Monero Research Lab, Kovri en de community.
+ - name: "Revuo Monero Q3 2017"
+ file: "Monero-Revuo-3Q-2017.pdf"
+ abstract: >
+ Kwartaalblad over Monero, derde kwartaal 2017.
+ In dit nummer nieuws over: ontwikkeling, Monero Research Lab, Kovri, community, hardware en Monerujo.
+
+moneropedia:
+ translated: "yes"
+ add_new_button: Nieuw trefwoord toevoegen
+ add_new_text1: Wil je een trefwoord bewerken of een nieuw trefwoord toevoegen?
+ add_new_link: Open dan een issue op de GitLab-repository van deze website
+ add_new_text2: of stel wijzigingen voor via een merge request
+ entries:
+ account: Account
+ address-book: Address Book
+ address: Address
+ airgap: Airgap
+ atomic-units: Atomic Units
+ base32-address: Base32 address
+ base64-address: Base64 address
+ blockchain: Blockchain
+ block: Block
+ bootstrap-node: Bootstrap-node
+ canonically-unique-host: Canonically-unique host
+ change: Change
+ clearnet: Clearnet
+ coinbase: Coinbase Transaction
+ consensus: Consensus
+ cryptocurrency: Cryptocurrency
+ data-directory: Data Directory
+ denominations: Denominations
+ destination: Destination
+ eepsite: Eepsite
+ encryption: Encryption
+ floodfill: Floodfill
+ fluffyblocks: Fluffy Blocks
+ fungibility: Fungibility
+ garlic-encryption: Garlic-Encryption
+ garlic-routing: Garlic Routing
+ i2np: I2NP
+ i2pcontrol: I2PControl
+ i2p: I2P
+ in-net: In-net
+ java-i2p: Java I2P
+ jump-service: Jump Service
+ kovri: Kovri
+ lease: Lease
+ lease-set: Lease-Set
+ locally-unique-host: Locally-unique host
+ message: Message
+ mining: Mining
+ mnemonicseed: Mnemonic Seed
+ network-database: Network Database
+ node: Node
+ ntcp: NTCP
+ openalias: OpenAlias
+ paperwallet: Paper Wallet
+ paymentid: Payment ID
+ pedersen-commitment: Pedersen Commitment
+ reseed: Reseed
+ ringCT: Ring CT
+ ringsignatures: Ring Signature
+ ring-size: Ring Size
+ router-info: Router-Info
+ scalability: Scalability
+ signature: Cryptographic Signature
+ smartmining: Smart Mining
+ spendkey: Spend Key
+ ssu: SSU
+ stealthaddress: Stealth Address
+ subscription: Subscription
+ tail-emission: Tail Emission
+ transaction: Transactions
+ transports: Transports
+ tunnel: Tunnel
+ unlocktime: Transaction Unlock Time
+ viewkey: View Key
+ wallet: Wallet
+
+blog:
+ title_1: Alles
+ title_2: Blog
+ title_3: Posts
+ tagged: Met tag
+ author: Geplaatst door
+ date: Geplaatst op
+ forum: Klik hier om dit trefwoord te bespreken op het Monero-forum
+
+tags:
+ all: Artikelen per tag
+ notags: Er zijn geen posts voor deze tag.
diff --git a/_i18n/nl/resources/developer-guides/daemon-rpc.md b/_i18n/nl/resources/developer-guides/daemon-rpc.md
new file mode 100644
index 00000000..d143bf1f
--- /dev/null
+++ b/_i18n/nl/resources/developer-guides/daemon-rpc.md
@@ -0,0 +1,2377 @@
+{% assign version = '2.3.0' | split: '.' %}
+{% include disclaimer.html translated="true" version=page.version %}
+## 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.**
+
+Note2: Guide updated as of network height of 1,562,465.
+
+### [JSON RPC Methods](#json-rpc-methods):
+
+* [get_block_count](#get_block_count)
+* [on_get_block_hash](#on_get_block_hash)
+* [get_block_template](#get_block_template)
+* [submit_block](#submit_block)
+* [get_last_block_header](#get_last_block_header)
+* [get_block_header_by_hash](#get_block_header_by_hash)
+* [get_block_header_by_height](#get_block_header_by_height)
+* [get_block_headers_range](#get_block_headers_range)
+* [get_block](#get_block)
+* [get_connections](#get_connections)
+* [get_info](#get_info)
+* [hard_fork_info](#hard_fork_info)
+* [set_bans](#set_bans)
+* [get_bans](#get_bans)
+* [flush_txpool](#flush_txpool)
+* [get_output_histogram](#get_output_histogram)
+* [get_version](#get_version)
+* [get_coinbase_tx_sum](#get_coinbase_tx_sum)
+* [get_fee_estimate](#get_fee_estimate)
+* [get_alternate_chains](#get_alternate_chains)
+* [relay_tx](#relay_tx)
+* [sync_info](#sync_info)
+* [get_txpool_backlog](#get_txpool_backlog)
+* [get_output_distribution](#get_output_distribution)
+
+### [Other RPC Methods](#other-daemon-rpc-calls):
+
+* [/get_height](#get_height)
+* [/get_blocks.bin](#get_blocksbin)
+* [/get_blocks_by_height.bin](#get_blocks_by_heightbin)
+* [/get_hashes.bin](#get_hashesbin)
+* [/get_o_indexes.bin](#get_o_indexesbin)
+* [/get_outs.bin](#get_outsbin)
+* [/get_transactions](#get_transactions)
+* [/get_alt_blocks_hashes](#get_alt_blocks_hashes)
+* [/is_key_image_spent](#is_key_image_spent)
+* [/send_raw_transaction](#send_raw_transaction)
+* [/start_mining](#start_mining)
+* [/stop_mining](#stop_mining)
+* [/mining_status](#mining_status)
+* [/save_bc](#save_bc)
+* [/get_peer_list](#get_peer_list)
+* [/set_log_hash_rate](#set_log_hash_rate)
+* [/set_log_level](#set_log_level)
+* [/set_log_categories](#set_log_categories)
+* [/get_transaction_pool](#get_transaction_pool)
+* [/get_transaction_pool_hashes.bin](#get_transaction_pool_hashesbin)
+* [/get_transaction_pool_stats](#get_transaction_pool_stats)
+* [/stop_daemon](#stop_daemon)
+* [/get_info (not JSON)](#get_info-not-json)
+* [/get_limit](#get_limit)
+* [/set_limit](#set_limit)
+* [/out_peers](#out_peers)
+* [/in_peers](#in_peers)
+* [/start_save_graph](#start_save_graph)
+* [/stop_save_graph](#stop_save_graph)
+* [/get_outs](#get_outs)
+* [/update](#update)
+
+
+---
+
+## 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='get_block_header_by_height'
+ALIAS='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.
+
+### **get_block_count**
+
+Look up how many blocks are in the longest chain known to the node.
+
+Alias: *getblockcount*.
+
+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":"get_block_count"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "count": 993163,
+ "status": "OK"
+ }
+}
+```
+
+
+### **on_get_block_hash**
+
+Look up a block's hash by its height.
+
+Alias: *on_getblockhash*.
+
+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_get_block_hash","params":[912345]}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": "e22cf75f39ae720e8b71b3d120a5ac03f0db50bba6379e2850975b4859190bc6"
+}
+```
+
+
+### **get_block_template**
+
+Get a block template on which mining a new block.
+
+Alias: *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.
+* *blockhashing_blob* - string; Blob on which to try to find a valid nonce.
+* *difficulty* - unsigned int; Difficulty of next block.
+* *expected_reward* - unsigned int; Coinbase reward expected to be received if block is successfully mined.
+* *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.
+* *untrusted* - boolean; States if the result is obtained using the bootstrap mode, and is therefore not trusted (`true`), or when the daemon is fully synced (`false`).
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_block_template","params":{"wallet_address":"44GBHzv6ZyQdJkjqZje6KLZ3xSyN1hBSFAnLP6EAqJtCRVzMzZmeXTC2AHKDS9aEDTRKmo6a6o9r9j86pYfhCWDkKjbtcns","reserve_size":60}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "blockhashing_blob": "070786a498d705f8dc58791266179087907a2ff4cd883615216749b97d2f12173171c725a6f84a00000000fc751ea4a94c2f840751eaa36138eee66dda15ef554e7d6594395827994e31da10",
+ "blocktemplate_blob": "070786a498d705f8dc58791266179087907a2ff4cd883615216749b97d2f12173171c725a6f84a0000000002aeab5f01fff2aa5f01e0a9d0f2f08a01028fdb3d5b5a2c363d36ea17a4add99a23a3ec7935b4c3e1e0364fcc4295c7a2ef5f01f912b15f5d17c1539d4722f79d8856d8654c5af87f54cfb3a4ff7f6b512b2a08023c000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000f1755090c809421d69873c161e7969b8bf33cee3b451dd4859bfc244a705f0b4900498f804b6023e13fa023a0fb759e8b7c9a39506a21442bc47077beeedc6b78d34c4ebdae91bd96097ccc9a882bc5056568b0d2f1f06559368fea4acba8e745444e883e53156d5083c1fd260edf05292934c8b40c098b81fe4e261720bdd272b209e317247a1d2c55dc4718891af0d16273c5a610f36f382a3bf50f54808aaa6a508e51d4601dd0d8fbf8b3b1685066ce121666a1409e8ac7a4d673c1cc36d10b825f764af647441f53230518e4d2efbcf8791c6060912c76e90db4982a66d51bbd96290bbb34db8080b216c2940cec407260bf5e2c3a5ee280835f15298f0801e9d98c4d414792282fbc2c28c3e20bc0fcb1829b5c3ad8f8d20847be8fdb2a949fd96f0205fbd6d271c880c5d8c83e9813606cd803a44d377fdeae45bfa67112132af601e9b3b0613ba7dff2ec3d4b935c447b47bfe39f7b950981b2f4c66c0d853e2218f1f69229a9b608c3d98be09b6d4d640a9f6ff0e920dbacf7e58b59554c0b398b1ae4b1d497104b4e4e745d850eed7eddb8aa93437427bf442ae5beb22cbf10a8fa738ea38cfa5d86dfd30675d4be11a38016e36936fd5601e52643e8b8bc433702ea7ae6149309c95b898cc854850e73fe0b95c5b8879b7325ecd4",
+ "difficulty": 61043624293,
+ "expected_reward": 4771949057248,
+ "height": 1561970,
+ "prev_hash": "f8dc58791266179087907a2ff4cd883615216749b97d2f12173171c725a6f84a",
+ "reserved_offset": 129,
+ "status": "OK",
+ "untrusted": false
+ }
+}
+```
+
+
+### **submit_block**
+
+Submit a mined block to the network.
+
+Alias: *submitblock*.
+
+Inputs:
+
+* Block blob data - array of strings; list of block blobs which have been mined. See [get_block_template](#get_block_template) to get a blob on which to mine.
+
+Outputs:
+
+* *status* - string; Block submit status.
+
+In this example, a block blob which has not been mined is submitted:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"submit_block","params":["0707e6bdfedc053771512f1bc27c62731ae9e8f2443db64ce742f4e57f5cf8d393de28551e441a0000000002fb830a01ffbf830a018cfe88bee283060274c0aae2ef5730e680308d9c00b6da59187ad0352efe3c71d36eeeb28782f29f2501bd56b952c3ddc3e350c2631d3a5086cac172c56893831228b17de296ff4669de020200000000"]' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "error": {
+ "code": -7,
+ "message": "Block not accepted"
+ }
+}
+```
+
+
+### **get_last_block_header**
+
+Block header information for the most recent block is easily retrieved with this method. No inputs are needed.
+
+Alias: *getlastblockheader*.
+
+Inputs: *None*.
+
+Outputs:
+
+* *block_header* - A structure containing block header information.
+ * *block_size* - unsigned int; The block size in bytes.
+ * *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.
+ * *num_txes* - unsigned int; Number of transactions in the block, not counting the coinbase tx.
+ * *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 unix time at which the block was recorded into the blockchain.
+* *status* - string; General RPC error code. "OK" means everything looks good.
+* *untrusted* - boolean; States if the result is obtained using the bootstrap mode, and is therefore not trusted (`true`), or when the daemon is fully synced (`false`).
+
+In this example, the most recent block (1562023 at the time) is returned:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_last_block_header"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "block_header": {
+ "block_size": 62774,
+ "depth": 0,
+ "difficulty": 60097900840,
+ "hash": "3a289b8fa88b10e2163826c230b45d79f2be37d14fa3153ee58ff8a427782d14",
+ "height": 1562023,
+ "major_version": 7,
+ "minor_version": 7,
+ "nonce": 3789681204,
+ "num_txes": 5,
+ "orphan_status": false,
+ "prev_hash": "743e5d0a26849efe27b96086f2c4ecc39a0bc744bf21473dad6710221aff6ac3",
+ "reward": 4724029079703,
+ "timestamp": 1525029411
+ },
+ "status": "OK",
+ "untrusted": false
+ }
+}
+```
+
+
+### **get_block_header_by_hash**
+
+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.
+
+Alias: *getblockheaderbyhash*.
+
+Inputs:
+
+* *hash* - string; The block's sha256 hash.
+
+Outputs:
+
+* *block_header* - A structure containing block header information. See [get_last_block_header](#get_last_block_header).
+* *status* - string; General RPC error code. "OK" means everything looks good.
+* *untrusted* - boolean; States if the result is obtained using the bootstrap mode, and is therefore not trusted (`true`), or when the daemon is fully synced (`false`).
+
+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":"get_block_header_by_hash","params":{"hash":"e22cf75f39ae720e8b71b3d120a5ac03f0db50bba6379e2850975b4859190bc6"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "block_header": {
+ "block_size": 210,
+ "depth": 649717,
+ "difficulty": 815625611,
+ "hash": "e22cf75f39ae720e8b71b3d120a5ac03f0db50bba6379e2850975b4859190bc6",
+ "height": 912345,
+ "major_version": 1,
+ "minor_version": 2,
+ "nonce": 1646,
+ "num_txes": 0,
+ "orphan_status": false,
+ "prev_hash": "b61c58b2e0be53fad5ef9d9731a55e8a81d972b8d90ed07c04fd37ca6403ff78",
+ "reward": 7388968946286,
+ "timestamp": 1452793716
+ },
+ "status": "OK",
+ "untrusted": false
+ }
+}
+```
+
+
+### **get_block_header_by_height**
+
+Similar to [get_block_header_by_hash](#get_block_header_by_hash) above, this method includes a block's height as an input parameter to retrieve basic information about the block.
+
+Alias: *getblockheaderbyheight*.
+
+Inputs:
+
+* *height* - unsigned int; The block's height.
+
+Outputs:
+
+* *block_header* - A structure containing block header information. See [get_last_block_header](#get_last_block_header).
+* *status* - string; General RPC error code. "OK" means everything looks good.
+* *untrusted* - boolean; States if the result is obtained using the bootstrap mode, and is therefore not trusted (`true`), or when the daemon is fully synced (`false`).
+
+In this example, block 912345 is looked up by its height (notice that the returned information is the same as in the previous example):
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_block_header_by_height","params":{"height":912345}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "block_header": {
+ "block_size": 210,
+ "depth": 649721,
+ "difficulty": 815625611,
+ "hash": "e22cf75f39ae720e8b71b3d120a5ac03f0db50bba6379e2850975b4859190bc6",
+ "height": 912345,
+ "major_version": 1,
+ "minor_version": 2,
+ "nonce": 1646,
+ "num_txes": 0,
+ "orphan_status": false,
+ "prev_hash": "b61c58b2e0be53fad5ef9d9731a55e8a81d972b8d90ed07c04fd37ca6403ff78",
+ "reward": 7388968946286,
+ "timestamp": 1452793716
+ },
+ "status": "OK",
+ "untrusted": false
+ }
+}
+```
+
+### **get_block_headers_range**
+
+Similar to [get_block_header_by_height](#get_block_header_by_height) above, but for a range of blocks. This method includes a starting block height and an ending block height as parameters to retrieve basic information about the range of blocks.
+
+Alias: *getblockheadersrange*.
+
+Inputs:
+
+* *start_height* - unsigned int; The starting block's height.
+* *end_height* - unsigned int; The ending block's height.
+
+Outputs:
+
+* *headers* - array of `block_header` (a structure containing block header information. See [get_last_block_header](#get_last_block_header)).
+* *status* - string; General RPC error code. "OK" means everything looks good.
+* *untrusted* - boolean; States if the result is obtained using the bootstrap mode, and is therefore not trusted (`true`), or when the daemon is fully synced (`false`).
+
+In this example, blocks range from height 1545999 to 1546000 is looked up (notice that the returned informations are ascending order and that it is at the April 2018 network upgrade time):
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_block_headers_range","params":{"start_height":1545999,"end_height":1546000}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "headers": [{
+ "block_size": 301413,
+ "depth": 16085,
+ "difficulty": 134636057921,
+ "hash": "86d1d20a40cefcf3dd410ff6967e0491613b77bf73ea8f1bf2e335cf9cf7d57a",
+ "height": 1545999,
+ "major_version": 6,
+ "minor_version": 6,
+ "nonce": 3246403956,
+ "num_txes": 20,
+ "orphan_status": false,
+ "prev_hash": "0ef6e948f77b8f8806621003f5de24b1bcbea150bc0e376835aea099674a5db5",
+ "reward": 5025593029981,
+ "timestamp": 1523002893
+ },{
+ "block_size": 13322,
+ "depth": 16084,
+ "difficulty": 134716086238,
+ "hash": "b408bf4cfcd7de13e7e370c84b8314c85b24f0ba4093ca1d6eeb30b35e34e91a",
+ "height": 1546000,
+ "major_version": 7,
+ "minor_version": 7,
+ "nonce": 3737164176,
+ "num_txes": 1,
+ "orphan_status": false,
+ "prev_hash": "86d1d20a40cefcf3dd410ff6967e0491613b77bf73ea8f1bf2e335cf9cf7d57a",
+ "reward": 4851952181070,
+ "timestamp": 1523002931
+ }],
+ "status": "OK",
+ "untrusted": false
+ }
+}
+```
+
+
+### **get_block**
+
+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.
+
+Alias: *getblock*.
+
+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 [get_last_block_header](#get_last_block_header).
+* *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.
+* *untrusted* - boolean; States if the result is obtained using the bootstrap mode, and is therefore not trusted (`true`), or when the daemon is fully synced (`false`).
+
+**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":"get_block","params":{"height":912345}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "blob": "0102f4bedfb405b61c58b2e0be53fad5ef9d9731a55e8a81d972b8d90ed07c04fd37ca6403ff786e0600000195d83701ffd9d73704ee84ddb42102378b043c1724c92c69d923d266fe86477d3a5ddd21145062e148c64c5767700880c0fc82aa020273733cbd6e6218bda671596462a4b062f95cfe5e1dbb5b990dacb30e827d02f280f092cbdd080247a5dab669770da69a860acde21616a119818e1a489bb3c4b1b6b3c50547bc0c80e08d84ddcb01021f7e4762b8b755e3e3c72b8610cc87b9bc25d1f0a87c0c816ebb952e4f8aff3d2b01fd0a778957f4f3103a838afda488c3cdadf2697b3d34ad71234282b2fad9100e02080000000bdfc2c16c00",
+ "block_header": {
+ "block_size": 210,
+ "depth": 649772,
+ "difficulty": 815625611,
+ "hash": "e22cf75f39ae720e8b71b3d120a5ac03f0db50bba6379e2850975b4859190bc6",
+ "height": 912345,
+ "major_version": 1,
+ "minor_version": 2,
+ "nonce": 1646,
+ "num_txes": 0,
+ "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}",
+ "miner_tx_hash": "c7da3965f25c19b8eb7dd8db48dcd4e7c885e2491db77e289f0609bf8e08ec30",
+ "status": "OK",
+ "untrusted": false
+ }
+}
+```
+
+**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":"get_block","params":{"hash":"510ee3c4e14330a7b96e883c323a60ebd1b5556ac1262d0bc03c24a3b785516f"}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "blob": "0102a3978cb7050ea4af6547c05c965afc8df6d31509ff3105dc7ae6b10172521d77e09711fd6df407000001dcce3c01ffa0ce3c049da8bece070259e9d685b3484886bc7b47c133e6099ecdf212d5eaa16ce19cd58e8c3c1e590a80d88ee16f024c5e2f542d25513c46b9e3b7d40140a22d0ae5314bfcae492ad9f56fff8185f080d0b8e1981a0213dd8ffdac9e6a2f71e327dad65328198dc879a492d145eae72677c0703a351580c0f9decfae010262bda00341681dccbc066757862da593734395745bdfe1fdc89b5948c86a5d4c2b01b691851cf057b9c302a3dbca879e1cba4cc45061ca55aaa6e03cdc67ab9e455002080000000c617fdf160379c6b9f00db027bde151705aafe85c495883aae2597d5cb8e1adb2e0f3ae1d07d715db73331abc3ec588ef07c7bb195786a4724b08dff431b51ffa32a4ce899bb197066426c0ed89f0b431fe171f7fd62bc95dd29943daa7cf3585cf1fdfc99d",
+ "block_header": {
+ "block_size": 3981,
+ "depth": 569068,
+ "difficulty": 964985344,
+ "hash": "510ee3c4e14330a7b96e883c323a60ebd1b5556ac1262d0bc03c24a3b785516f",
+ "height": 993056,
+ "major_version": 1,
+ "minor_version": 2,
+ "nonce": 2036,
+ "num_txes": 3,
+ "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}",
+ "miner_tx_hash": "372395aeac5e5ad2c40b4c546b0bad00c4242fb2bd88e2e25f4e43231876f81e",
+ "status": "OK",
+ "tx_hashes": ["79c6b9f00db027bde151705aafe85c495883aae2597d5cb8e1adb2e0f3ae1d07","d715db73331abc3ec588ef07c7bb195786a4724b08dff431b51ffa32a4ce899b","b197066426c0ed89f0b431fe171f7fd62bc95dd29943daa7cf3585cf1fdfc99d"],
+ "untrusted": false
+ }
+}
+```
+
+
+### **get_connections**
+
+Retrieve information about incoming and outgoing connections to your node.
+
+Alias: *None*.
+
+Inputs: *None*.
+
+Outputs:
+
+* *connections* - List of all connections and their info:
+ * *address* - string; The peer's address, actually IPv4 & port
+ * *avg_download* - unsigned int; Average bytes of data downloaded by node.
+ * *avg_upload* - unsigned int; Average bytes of data uploaded by node.
+ * *connection_id* - string; The connection ID
+ * *current_download* - unsigned int; Current bytes downloaded by node.
+ * *current_upload* - unsigned int; Current bytes uploaded by node.
+ * *height*- unsigned int; The peer height
+ * *host* - string; The peer host
+ * *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
+ * *support_flags* - unsigned int
+
+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": [{
+ "address": "173.90.69.136:62950",
+ "avg_download": 0,
+ "avg_upload": 2,
+ "connection_id": "083c301a3030329a487adb12ad981d2c",
+ "current_download": 0,
+ "current_upload": 2,
+ "height": 1562127,
+ "host": "173.90.69.136",
+ "incoming": true,
+ "ip": "173.90.69.136",
+ "live_time": 8,
+ "local_ip": false,
+ "localhost": false,
+ "peer_id": "c959fbfbed9e44fb",
+ "port": "62950",
+ "recv_count": 259,
+ "recv_idle_time": 8,
+ "send_count": 24342,
+ "send_idle_time": 8,
+ "state": "state_normal",
+ "support_flags": 0
+ },{
+ ...
+ }],
+ "status": "OK"
+ }
+}
+```
+
+
+### **get_info**
+
+Retrieve general information about the state of your node and the network.
+
+Alias:
+
+* */get_info*
+* */getinfo*
+
+See other RPC Methods [/get_info (not JSON)](#get_info-not-json)
+
+Inputs: *None*.
+
+Outputs:
+
+* *alt_blocks_count* - unsigned int; Number of alternative blocks to main chain.
+* *block_size_limit* - unsigned int; Maximum allowed block size
+* *block_size_median* - unsigned int; Median block size of latest 100 blocks
+* *bootstrap_daemon_address* - string; @Bootstrap-node to give immediate usability to wallets while syncing by proxying RPC to it. (Note: the replies may be untrustworthy).
+* *cumulative_difficulty* - unsigned int; Cumulative difficulty of all blocks in the blockchain.
+* *difficulty* - unsigned int; Network difficulty (analogous to the strength of the network)
+* *free_space* - unsigned int; Available disk space on the node.
+* *grey_peerlist_size* - unsigned int; Grey Peerlist Size
+* *height* - unsigned int; Current length of longest chain known to daemon.
+* *height_without_bootstrap* - unsigned int; Current length of the local chain of the daemon.
+* *incoming_connections_count* - unsigned int; Number of peers connected to and pulling from your node.
+* *mainnet* - boolean; States if the node is on the mainnet (`true`) or not (`false`).
+* *offline* - boolean; States if the node is offline (`true`) or online (`false`).
+* *outgoing_connections_count* - unsigned int; Number of peers that you are connected to and getting information from.
+* *rpc_connections_count* - unsigned int; Number of RPC client connected to the daemon (Including this RPC request).
+* *stagenet* - boolean; States if the node is on the stagenet (`true`) or not (`false`).
+* *start_time* - unsigned int; Start time of the daemon, as UNIX time.
+* *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 not (`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.
+* *untrusted* - boolean; States if the result is obtained using the bootstrap mode, and is therefore not trusted (`true`), or when the daemon is fully synced (`false`).
+* *was_bootstrap_ever_used* - boolean; States if a bootstrap node has ever been used since the daemon started.
+* *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": 6,
+ "block_size_limit": 600000,
+ "block_size_median": 129017,
+ "bootstrap_daemon_address": "",
+ "cumulative_difficulty": 14121125493385685,
+ "difficulty": 60580751777,
+ "free_space": 138758750208,
+ "grey_peerlist_size": 4998,
+ "height": 1562168,
+ "height_without_bootstrap": 1562168,
+ "incoming_connections_count": 2,
+ "mainnet": true,
+ "offline": false,
+ "outgoing_connections_count": 8,
+ "rpc_connections_count": 2,
+ "stagenet": false,
+ "start_time": 1524751757,
+ "status": "OK",
+ "target": 120,
+ "target_height": 1562063,
+ "testnet": false,
+ "top_block_hash": "7a7ba647080844073fdd8e3a069e00554c773d6e6863354dba1dec45a43f5592",
+ "tx_count": 2759894,
+ "tx_pool_size": 755,
+ "untrusted": false,
+ "was_bootstrap_ever_used": false,
+ "white_peerlist_size": 1000
+ }
+}
+```
+
+
+### **hard_fork_info**
+
+Look up information regarding hard fork voting and readiness.
+
+Alias: *None*.
+
+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
+ }
+}
+```
+
+
+### **set_bans**
+
+Ban another node by IP.
+
+Alias: *None*.
+
+Inputs:
+
+* *bans* - A list of nodes to ban:
+ * *host* - string; Host to ban (IP in A.B.C.D form - will support I2P address in the future).
+ * *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.
+
+Examples:
+
+**banning by host**
+
+In the following example, host is banned with its IP address string-formatted as A.B.C.D:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"set_bans","params":{"bans":[{"host":"192.168.1.51","ban":true,"seconds":30}]}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "status": "OK"
+ }
+}
+```
+
+**banning by ip**
+
+In the following example, integer-formatted IP is banned:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"set_bans","params":{"bans":[{"ip":838969536,"ban":true,"seconds":30}]}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "status": "OK"
+ }
+}
+```
+
+
+### **get_bans**
+
+Get list of banned IPs.
+
+Alias: *None*.
+
+Inputs: *None*.
+
+Outputs:
+
+* *bans* - List of banned nodes:
+ * *host* - string; Banned host (IP in A.B.C.D form).
+ * *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":"get_bans"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "bans": [{
+ "host": "102.168.1.51",
+ "ip": 855746662,
+ "seconds": 22
+ },{
+ "host": "192.168.1.50",
+ "ip": 838969536,
+ "seconds": 28
+ }],
+ "status": "OK"
+ }
+}
+```
+
+
+### **flush_txpool**
+
+Flush tx ids from transaction pool
+
+Alias: *None*.
+
+Inputs:
+
+* *txids* - array of strings; Optional, list of transactions IDs to flush from pool (all tx ids flushed if empty).
+
+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":"flush_txpool","params":{"txids":["dc16fa8eaffe1484ca9014ea050e13131d3acf23b419f33bb4cc0b32b6c49308",""]}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "status": "OK"
+ }
+}
+```
+
+### **get_output_histogram**
+
+Get a histogram of output amounts. For all amounts (possibly filtered by parameters), gives the number of outputs on the chain for that amount.
+RingCT outputs counts as 0 amount.
+
+Inputs:
+
+* *amounts* - list of unsigned int
+* *min_count* - unsigned int
+* *max_count* - unsigned int
+* *unlocked* - boolean
+* *recent_cutoff* - unsigned int
+
+Outputs:
+
+* *histogram* - list of histogram entries, in the following structure:
+ * *amount* - unsigned int; Output amount in @atomic-units
+ * *total_instances* - unsigned int;
+ * *unlocked_instances* - unsigned int;
+ * *recent_instances* - unsigned int;
+* *status* - string; General RPC error code. "OK" means everything looks good.
+* *untrusted* - boolean; States if the result is obtained using the bootstrap mode, and is therefore not trusted (`true`), or when the daemon is fully synced (`false`).
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_output_histogram","params":{"amounts":[20000000000]}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "histogram": [{
+ "amount": 20000000000,
+ "recent_instances": 0,
+ "total_instances": 381458,
+ "unlocked_instances": 0
+ }],
+ "status": "OK",
+ "untrusted": false
+ }
+}
+```
+
+
+### **get_coinbase_tx_sum**
+
+Get the coinbase ammount and the fees ammount for n last blocks starting at particular height
+
+Alias: *None*.
+
+Inputs:
+
+* *height* - unsigned int; Block height from which getting the amounts
+* *count* - unsigned int; number of blocks to include in the sum
+
+Outputs:
+
+* *emission_amount* - unsigned int; amount of coinbase reward in @atomic-units
+* *fee_amount* - unsigned int; amount of fees in @atomic-units
+* *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":"get_coinbase_tx_sum","params":{"height":1563078,"count":2}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "emission_amount": 9387854817320,
+ "fee_amount": 83981380000,
+ "status": "OK"
+ }
+}
+```
+
+
+### **get_version**
+
+Give the node current version
+
+Alias: *None*.
+
+Inputs: *None*.
+
+Outputs:
+
+* *status* - string; General RPC error code. "OK" means everything looks good.
+* *untrusted* - boolean; States if the result is obtained using the bootstrap mode, and is therefore not trusted (`true`), or when the daemon is fully synced (`false`).
+* *version* - unsigned int;
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_version"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "status": "OK",
+ "untrusted": false,
+ "version": 65555
+ }
+}
+```
+
+
+### **get_fee_estimate**
+
+Gives an estimation on fees per kB.
+
+Alias: *None*.
+
+Inputs:
+
+* *grace_blocks* - unsigned int; Optional
+
+Outputs:
+
+* *fee* - unsigned int; Amount of fees estimated per kB in @atomic-units
+* *status* - string; General RPC error code. "OK" means everything looks good.
+* *untrusted* - boolean; States if the result is obtained using the bootstrap mode, and is therefore not trusted (`true`), or when the daemon is fully synced (`false`).
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_fee_estimate"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "fee": 187610000,
+ "status": "OK",
+ "untrusted": false
+ }
+}
+```
+
+
+### **get_alternate_chains**
+
+Display alternative chains seen by the node.
+
+Alias: *None*.
+
+Inputs: *None*.
+
+Outputs:
+
+* *chains* - array of chains, the following structure:
+ * *block_hash* - string; the block hash of the first diverging block of this alternative chain.
+ * *difficulty* - unsigned int; the cumulative difficulty of all blocks in the alternative chain.
+ * *height* - unsigned int; the block height of the first diverging block of this alternative chain.
+ * *length* - unsigned int; the length in blocks of this alternative chain, after divergence.
+* *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":"get_alternate_chains"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "chains": [{
+ "block_hash": "697cf03c89a9b118f7bdf11b1b3a6a028d7b3617d2d0ed91322c5709acf75625",
+ "difficulty": 14114729638300280,
+ "height": 1562062,
+ "length": 2
+ }],
+ "status": "OK"
+ }
+}
+```
+
+
+### **relay_tx**
+
+Relay a list of transaction IDs.
+
+Alias: *None*.
+
+Inputs:
+
+* *txids* - array of string; list of transaction IDs to relay
+
+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":"relay_tx","params":{"txids":[9fd75c429cbe52da9a52f2ffc5fbd107fe7fd2099c0d8de274dc8a67e0c98613]}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "status": "OK"
+ }
+}
+```
+
+
+### **sync_info**
+
+Get synchronisation informations
+
+Alias: *None*.
+
+Inputs: *None*.
+
+Outputs:
+
+* *height* - unsigned int;
+* *peers* - array of peer structure, defined as follows:
+ * *info* - structure of connection info, as defined in [get_connections](#get_connections)
+* *spans* - array of span structure, defined as follows (optional, absent if node is fully synced):
+ * *connection_id* - string; Id of connection
+ * *nblocks* - unsigned int; number of blocks in that span
+ * *rate* - unsigned int; connection rate
+ * *remote_address* - string; peer address the node is downloading (or has downloaded) than span from
+ * *size* - unsigned int; total number of bytes in that span's blocks (including txes)
+ * *speed* - unsigned int; connection speed
+ * *start_block_height* - unsigned int; block height of the first block in that span
+* *status* - string; General RPC error code. "OK" means everything looks good.
+* *target_height* - unsigned int; target height the node is syncing from (optional, absent if node is fully synced)
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"sync_info"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "height": 1563543,
+ "peers": [{
+ "info": {
+ "address": "70.109.53.128:60064",
+ "avg_download": 0,
+ "avg_upload": 5,
+ "connection_id": "204067223b9b3415c265dd25ad29ee48",
+ "current_download": 0,
+ "current_upload": 1,
+ "height": 1559975,
+ "host": "70.109.53.128",
+ "incoming": true,
+ "ip": "70.109.53.128",
+ "live_time": 38,
+ "local_ip": false,
+ "localhost": false,
+ "peer_id": "96b8545dbc7a8866",
+ "port": "60064",
+ "recv_count": 1580,
+ "recv_idle_time": 28,
+ "send_count": 203603,
+ "send_idle_time": 8,
+ "state": "state_normal",
+ "support_flags": 1
+ }
+ },{
+ "info": {
+ ...
+ }
+ },{
+ ...
+ },{
+ ...
+ },{
+ ...
+ }],
+ "status": "OK",
+ "target_height": 1564067
+ }
+}
+```
+
+
+### **get_txpool_backlog**
+
+Get all transaction pool backlog
+
+Alias: *None*.
+
+Inputs: *None*.
+
+Outputs:
+
+* *backlog*: array of structures *tx_backlog_entry* (in binary form):
+ * *blob_size* - unsigned int (in binary form)
+ * *fee* - unsigned int (in binary form)
+ * *time_in_pool* - unsigned int (in binary form)
+* *status* - string; General RPC error code. "OK" means everything looks good.
+* *untrusted* - boolean; States if the result is obtained using the bootstrap mode, and is therefore not trusted (`true`), or when the daemon is fully synced (`false`).
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_txpool_backlog"}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "backlog": "...Binary...",
+ "status": "OK",
+ "untrusted": false
+ }
+}
+```
+
+
+### **get_output_distribution**
+
+
+
+Alias: *None*.
+
+Inputs:
+
+* *amounts* - array of unsigned int; amounts to look for
+* *cumulative* - boolean; (optional, default is `false`) States if the result should be cumulative (`true`) or not (`false`)
+* *from_height* - unsigned int; (optional, default is 0) starting height to check from
+* *to_height* - unsigned int; (optional, default is 0) ending height to check up to
+
+Outputs:
+
+* *distributions* - array of structure distribution as follows:
+ * *amount* - unsigned int
+ * *base* - unsigned int
+ * *distribution* - array of unsigned int
+ * *start_height* - unsigned int
+* *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":"get_output_distribution","params":{"amounts":[628780000],"from_height":1462078}}' -H 'Content-Type: application/json'
+
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "distributions": [{
+ "amount": 2628780000,
+ "base": 0,
+ "distribution": "",
+ "start_height": 1462078
+ }],
+ "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 [get_last_block_header](#get_last_block_header), rather than [getheight](#getheight) below.
+
+For calls that end with **.bin**, the data is exchanged in the form of binary, serialized objects, as defined in the [Core RPC Server](https://github.com/monero-project/monero/blob/master/src/rpc/core_rpc_server_commands_defs.h).
+
+
+### **/get_height**
+
+Get the node's current height.
+
+Alias: */getheight*.
+
+Inputs: *None*.
+
+Outputs:
+
+* *height* - unsigned int; Current length of longest chain known to daemon.
+* *status* - string; General RPC error code. "OK" means everything looks good.
+* *untrusted* - boolean; States if the result is obtained using the bootstrap mode, and is therefore not trusted (`true`), or when the daemon is fully synced (`false`).
+
+```
+$ curl -X POST http://127.0.0.1:18081/get_height -H 'Content-Type: application/json'
+
+{
+ "height": 1564055,
+ "status": "OK",
+ "untrusted": false
+}
+```
+
+
+
+### **/get_blocks.bin**
+
+Get all blocks info. Binary request.
+
+Alias: */getblocks.bin*.
+
+Inputs:
+
+* *block_ids* - binary array of hashes; first 10 blocks id goes sequential, next goes in pow(2,n) offset, like 2, 4, 8, 16, 32, 64 and so on, and the last one is always genesis block
+* *start_height* - unsigned int
+* *prune* - boolean
+
+Outputs:
+
+* *blocks* - array of block complete entries
+* *current_height* - unsigned int
+* *output_indices* - structure as follows:
+ * *indices* - array of tx output indices, structure as follows:
+ * *indices* - array of unsigned int
+* *start_height* - unsigned int
+* *status* - string; General RPC error code. "OK" means everything looks good.
+* *untrusted* - boolean; States if the result is obtained using the bootstrap mode, and is therefore not trusted (`true`), or when the daemon is fully synced (`false`).
+
+
+
+### **/get_blocks_by_height.bin**
+
+Get blocks by height. Binary request.
+
+Alias: */getblocks_by_height.bin*.
+
+Inputs:
+
+* *heights* - array of unsigned int; list of block heights
+
+Outputs:
+
+* *blocks* - array of block complete entries
+* *status* - string; General RPC error code. "OK" means everything looks good.
+* *untrusted* - boolean; States if the result is obtained using the bootstrap mode, and is therefore not trusted (`true`), or when the daemon is fully synced (`false`).
+
+
+
+
+### **/get_hashes.bin**
+
+Get hashes. Binary request.
+
+Alias: */gethashes.bin*.
+
+Inputs:
+
+* *block_ids* - binary array of hashes; first 10 blocks id goes sequential, next goes in pow(2,n) offset, like 2, 4, 8, 16, 32, 64 and so on, and the last one is always genesis block
+* *start_height* - unsigned int
+
+Outputs:
+
+* *current_height* - unsigned int
+* *m_block_ids* - binary array of hashes; see *block_ids* above.
+* *start_height* - unsigned int
+* *status* - string; General RPC error code. "OK" means everything looks good.
+* *untrusted* - boolean; States if the result is obtained using the bootstrap mode, and is therefore not trusted (`true`), or when the daemon is fully synced (`false`).
+
+
+
+
+### **/get_o_indexes.bin**
+
+Get global outputs of transactions. Binary request.
+
+Alias: *None*.
+
+Inputs:
+
+* *txid* - binary txid
+
+Outputs:
+
+* *o_indexes* - array of unsigned int; List of output indexes
+* *status* - string; General RPC error code. "OK" means everything looks good.
+* *untrusted* - boolean; States if the result is obtained using the bootstrap mode, and is therefore not trusted (`true`), or when the daemon is fully synced (`false`).
+
+
+
+
+### **/get_outs.bin**
+
+Get outputs. Binary request.
+
+Alias: *None*.
+
+Inputs:
+
+* *outputs* - array of structure *get_outputs_out* as follows:
+ * *amount* - unsigned int;
+ * *index* - unsigned int;
+
+Outputs:
+
+* *outs* - array of structure *outkey* as follows:
+ * *amount* - unsigned int;
+ * *height* - unsigned int; block height of the output
+ * *key* - the public key of the output
+ * *mask*
+ * *txid* - transaction id
+ * *unlocked* - boolean; States if output is locked (`false`) or not (`true`)
+* *status* - string; General RPC error code. "OK" means everything looks good.
+* *untrusted* - boolean; States if the result is obtained using the bootstrap mode, and is therefore not trusted (`true`), or when the daemon is fully synced (`false`).
+
+
+
+
+### **/get_transactions**
+
+Look up one or more transactions by hash.
+
+Alias: */gettransactions*.
+
+Inputs:
+
+* *txs_hashes* - string list; List of transaction hashes to look up.
+* *decode_as_json* - boolean; Optional (`false` by default). If set `true`, the returned transaction information will be decoded rather than binary.
+* *prune* - boolean; Optional (`false` by default).
+
+Outputs:
+
+* *missed_tx* - array of strings. (Optional - returned if not empty) Transaction hashes that could not be found.
+* *status* - General RPC error code. "OK" means everything looks good.
+* *txs* - array of structure *entry* as follows:
+ * *as_hex* - string; Full transaction information as a hex string.
+ * *as_json* - json string; 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 signatures used in ring signature to hide the true origin of the transaction.
+ * *block_height* - unsigned int; block height including the transaction
+ * *block_timestamp* - unsigned int; Unix time at chich the block has been added to the blockchain
+ * *double_spend_seen* - boolean; States if the transaction is a double-spend (`true`) or not (`false`)
+ * *in_pool* - boolean; States if the transaction is in pool (`true`) or included in a block (`false`)
+ * *output_indices* - array of unsigned int; transaction indexes
+ * *tx_hash* - string; transaction hash
+* *txs_as_hex* - string; Full transaction information as a hex string (old compatibility parameter)
+* *txs_as_json* - json string; (Optional - returned if set in inputs. Old compatibility parameter) List of transaction as in *as_json* above:
+
+Example 1: Return transaction information in binary format.
+
+```
+$ curl -X POST http://127.0.0.1:18081/get_transactions -d '{"txs_hashes":["d6e48158472848e6687173a91ae6eebfa3e1d778e65252ee99d7515d63090408"]}' -H 'Content-Type: application/json'
+
+{
+ "status": "OK",
+ "txs": [{
+ "as_hex": "...",
+ "as_json": "",
+ "block_height": 993442,
+ "block_timestamp": 1457749396,
+ "double_spend_seen": false,
+ "in_pool": false,
+ "output_indices": [198769,418598,176616,50345,509],
+ "tx_hash": "d6e48158472848e6687173a91ae6eebfa3e1d778e65252ee99d7515d63090408"
+ }],
+ "txs_as_hex": ["..."],
+ "untrusted": false
+}
+```
+
+Example 2: Decode returned transaction information in JSON format. Note: the "vin", "vout" and "signatures" list have been truncated in the displayed return for space considerations.
+
+```
+$ curl -X POST http://127.0.0.1:18081/get_transactions -d '{"txs_hashes":["d6e48158472848e6687173a91ae6eebfa3e1d778e65252ee99d7515d63090408"],"decode_as_json":true}' -H 'Content-Type: application/json'
+
+{
+ "status": "OK",
+ "txs": [{
+ "as_hex": "...",
+ "as_json": "{\n \"version\": 1, \n \"unlock_time\": 0, \n \"vin\": [ {\n \"key\": {\n \"amount\": 9999999999, \n \"key_offsets\": [ 691\n ], \n \"k_image\": \"6ebee1b651a8da723462b4891d471b990ddc226049a0866d3029b8e2f75b7012\"\n }\n }, {\n \"key\": {\n \"amount\": 9000000000000, \n \"key_offsets\": [ 175760\n ], \n \"k_image\": \"200bd02b70ee707441a8863c5279b4e4d9f376dc97a140b1e5bc7d72bc508069\"\n }\n }, ... \n ], \n \"vout\": [ {\n \"amount\": 60000000000, \n \"target\": {\n \"key\": \"8c792dea94dab48160e067fb681edd6247ba375281fbcfedc03cb970f3b98e2d\"\n }\n }, {\n \"amount\": 700000000000, \n \"target\": {\n \"key\": \"1ab33e69737e157d23e33274c42793be06a8711670e73fa10ecebc604f87cc71\"\n }\n }, ... \n ], \n \"extra\": [ 1, 3, 140, 109, 156, 205, 47, 148, 153, 9, 17, 93, 83, 33, 162, 110, 152, 1, 139, 70, 121, 19, 138, 10, 44, 6, 55, 140, 242, 124, 143, 219, 172\n ], \n \"signatures\": [ \"fd82214a59c99d9251fa00126d353f9cf502a80d8993a6c223e3c802a40ab405555637f495903d3ba558312881e586d452e6e95826d8e128345f6c0a8f9f350e\", \"8c04ef50cf34afa3a9ec19c457143496f8cf7045ed869b581f9efa2f1d65e30f1cec5272b00e9c61a34bdd3c78cf82ae8ef4df3132f70861391069b9c255cd08\", ... ]\n}",
+ "block_height": 993442,
+ "block_timestamp": 1457749396,
+ "double_spend_seen": false,
+ "in_pool": false,
+ "output_indices": [198769,418598,176616,50345,509],
+ "tx_hash": "d6e48158472848e6687173a91ae6eebfa3e1d778e65252ee99d7515d63090408"
+ }],
+ "txs_as_hex": ["..."],
+ "txs_as_json": ["{\n \"version\": 1, \n \"unlock_time\": 0, \n \"vin\": [ {\n \"key\": {\n \"amount\": 9999999999, \n \"key_offsets\": [ 691\n ], \n \"k_image\": \"6ebee1b651a8da723462b4891d471b990ddc226049a0866d3029b8e2f75b7012\"\n }\n }, {\n \"key\": {\n \"amount\": 9000000000000, \n \"key_offsets\": [ 175760\n ], \n \"k_image\": \"200bd02b70ee707441a8863c5279b4e4d9f376dc97a140b1e5bc7d72bc508069\"\n }\n }, ... \n ], \n \"vout\": [ {\n \"amount\": 60000000000, \n \"target\": {\n \"key\": \"8c792dea94dab48160e067fb681edd6247ba375281fbcfedc03cb970f3b98e2d\"\n }\n }, {\n \"amount\": 700000000000, \n \"target\": {\n \"key\": \"1ab33e69737e157d23e33274c42793be06a8711670e73fa10ecebc604f87cc71\"\n }\n }, ... \n ], \n \"extra\": [ 1, 3, 140, 109, 156, 205, 47, 148, 153, 9, 17, 93, 83, 33, 162, 110, 152, 1, 139, 70, 121, 19, 138, 10, 44, 6, 55, 140, 242, 124, 143, 219, 172\n ], \n \"signatures\": [ \"fd82214a59c99d9251fa00126d353f9cf502a80d8993a6c223e3c802a40ab405555637f495903d3ba558312881e586d452e6e95826d8e128345f6c0a8f9f350e\", \"8c04ef50cf34afa3a9ec19c457143496f8cf7045ed869b581f9efa2f1d65e30f1cec5272b00e9c61a34bdd3c78cf82ae8ef4df3132f70861391069b9c255cd08\", ... ]\n}"],
+ "untrusted": false
+}
+```
+
+Example 3: Returned a missed (unexisting) transaction.
+
+```
+curl -X POST http://127.0.0.1:18081/get_transactions -d '{"txs_hashes":["d6e48158472848e6687173a91ae6eebfa3e1d778e65252ee99d7515d63090409"]}' -H 'Content-Type: application/json'
+
+{
+ "missed_tx": ["d6e48158472848e6687173a91ae6eebfa3e1d778e65252ee99d7515d63090409"],
+ "status": "OK",
+ "untrusted": false
+}
+```
+
+
+### **/get_alt_blocks_hashes**
+
+Get the known blocks hashes which are not on the main chain.
+
+Alias: *None*.
+
+Inputs: *None*
+
+Outputs:
+
+* *blks_hashes* - array of strings; list of alternative blocks hashes to main chain
+* *status* - string; General RPC error code. "OK" means everything looks good.
+* *untrusted* - boolean; States if the result is obtained using the bootstrap mode, and is therefore not trusted (`true`), or when the daemon is fully synced (`false`).
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/get_alt_blocks_hashes -H 'Content-Type: application/json'
+
+{
+ "blks_hashes": ["9c2277c5470234be8b32382cdf8094a103aba4fcd5e875a6fc159dc2ec00e011","637c0e0f0558e284493f38a5fcca3615db59458d90d3a5eff0a18ff59b83f46f","6f3adc174a2e8082819ebb965c96a095e3e8b63929ad9be2d705ad9c086a6b1c","697cf03c89a9b118f7bdf11b1b3a6a028d7b3617d2d0ed91322c5709acf75625","d99b3cf3ac6f17157ac7526782a3c3b9537f89d07e069f9ce7821d74bd9cad0e","e97b62109a6303233dcd697fa8545c9fcbc0bf8ed2268fede57ddfc36d8c939c","70ff822066a53ad64b04885c89bbe5ce3e537cdc1f7fa0dc55317986f01d1788","b0d36b209bd0d4442b55ea2f66b5c633f522401f921f5a85ea6f113fd2988866"],
+ "status": "OK",
+ "untrusted": false
+}
+```
+
+
+### **/is_key_image_spent**
+
+Check if outputs have been spent using the key image associated with the output.
+
+Alias: *None*.
+
+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.
+* *untrusted* - boolean; States if the result is obtained using the bootstrap mode, and is therefore not trusted (`true`), or when the daemon is fully synced (`false`).
+
+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"
+ "untrusted": false
+}
+```
+
+
+### **/send_raw_transaction**
+
+Broadcast a raw transaction to the network.
+
+Alias: */sendrawtransaction*.
+
+Inputs:
+
+* *tx_as_hex* - string; Full transaction information as hexidecimal string.
+* *do_not_relay* - boolean; Stop relaying transaction to other nodes (default is `false`).
+
+Outputs:
+
+* *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 a standard ring transaction (`true`) or a ring confidential 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.
+* *status* - string; General RPC error code. "OK" means everything looks good. Any other value means that something went wrong.
+* *too_big* - boolean; Transaction size is too big (`true`) or OK (`false`).
+* *untrusted* - boolean; States if the result is obtained using the bootstrap mode, and is therefore not trusted (`true`), or when the daemon is fully synced (`false`).
+
+
+Example (No return information included here.):
+
+
+```
+$ curl -X POST http://127.0.0.1:18081/send_raw_transaction -d '{"tx_as_hex":"de6a3...", "do_not_relay":false}' -H 'Content-Type: application/json'
+```
+
+
+### **/start_mining**
+
+Start mining on the daemon.
+
+Alias: *None*.
+
+Inputs:
+
+* *do_background_mining* - boolean; States if the mining should run in background (`true`) or foreground (`false`).
+* *ignore_battery* - boolean; States if batery state (on laptop) should be ignored (`true`) or not (`false`).
+* *miner_address* - string; Account address to mine to.
+* *threads_count* - unsigned int; Number of mining thread to run.
+
+Outputs:
+
+* *status* - string; General RPC error code. "OK" means everything looks good. Any other value means that something went wrong.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/start_mining -d '{"do_background_mining":false,"ignore_battery":true,"miner_address":"47xu3gQpF569au9C2ajo5SSMrWji6xnoE5vhr94EzFRaKAGw6hEGFXYAwVADKuRpzsjiU1PtmaVgcjUJF89ghGPhUXkndHc","threads_count":1}' -H 'Content-Type: application/json'
+
+{
+ "status": "OK"
+}
+```
+
+
+### **/stop_mining**
+
+Stop mining on the daemon.
+
+Alias: *None*.
+
+Inputs: *None*.
+
+Outputs:
+
+* *status* - string; General RPC error code. "OK" means everything looks good. Any other value means that something went wrong.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/stop_mining -H 'Content-Type: application/json'
+
+{
+ "status": "OK"
+}
+```
+
+
+### **/mining_status**
+
+Get the mining status of the daemon.
+
+Alias: *None*.
+
+Inputs: *None*.
+
+Outputs:
+
+* *active* - boolean; States if mining is enabled (`true`) or disabled (`false`).
+* *address* - string; Account address daemon is mining to. Empty if not mining.
+* *is_background_mining_enabled* - boolean; States if the mining is running in background (`true`) or foreground (`false`).
+* *speed* - unsigned int; Mining power in hashes per seconds.
+* *status* - string; General RPC error code. "OK" means everything looks good. Any other value means that something went wrong.
+* *threads_count* - unsigned int; Number of running mining threads.
+
+Example while mining:
+
+```
+$ curl -X POST http://127.0.0.1:18081/mining_status -H 'Content-Type: application/json'
+
+{
+ "active": true,
+ "address": "47xu3gQpF569au9C2ajo5SSMrWji6xnoE5vhr94EzFRaKAGw6hEGFXYAwVADKuRpzsjiU1PtmaVgcjUJF89ghGPhUXkndHc",
+ "is_background_mining_enabled": false,
+ "speed": 20,
+ "status": "OK",
+ "threads_count": 1
+}
+```
+
+Example while not mining:
+
+```
+$ curl -X POST http://127.0.0.1:18081/mining_status -H 'Content-Type: application/json'
+
+{
+ "active": false,
+ "address": "",
+ "is_background_mining_enabled": false,
+ "speed": 0,
+ "status": "OK",
+ "threads_count": 0
+}
+```
+
+
+### **/save_bc**
+
+Save the blockchain. The blockchain does not need saving and is always saved when modified, however it does a sync to flush the filesystem cache onto the disk for safety purposes against Operating System or Harware crashes.
+
+Alias: *None*.
+
+Inputs: *None*.
+
+Outputs:
+
+* *status* - string; General RPC error code. "OK" means everything looks good. Any other value means that something went wrong.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/save_bc -H 'Content-Type: application/json'
+
+{
+ "status": "OK"
+}
+```
+
+
+### **/get_peer_list**
+
+Get the known peers list.
+
+Alias: *None*.
+
+Inputs: *None*.
+
+Outputs:
+
+* *gray_list* - array of offline *peer* structure as follows:
+ * *host* - unsigned int; IP address in integer format
+ * *id* - string; Peer id
+ * *ip* - unsigned int; IP address in integer format
+ * *last_seen* - unsigned int; unix time at which the peer has been seen for the last time
+ * *port* - unsigned int; TCP port the peer is using to connect to monero network.
+* *status* - string; General RPC error code. "OK" means everything looks good. Any other value means that something went wrong.
+* *white_list* - array of online *peer* structure, as above.
+
+Example (truncated lists):
+
+```
+$ curl -X POST http://127.0.0.1:18081/get_peer_list -H 'Content-Type: application/json'
+
+{
+ "gray_list": [{
+ "host": "640304833",
+ "id": 5345237316225602120,
+ "ip": 640304833,
+ "last_seen": 1525540510,
+ "port": 18080
+ },{
+ "host": "2183731038",
+ "id": 14955030573998424430,
+ "ip": 2183731038,
+ "last_seen": 1525540499,
+ "port": 28080
+ }, ...
+ ],
+ "status": "OK",
+ "white_list": [{
+ "host": "1221637955",
+ "id": 10354694710033118926,
+ "ip": 1221637955,
+ "last_seen": 1525540511,
+ "port": 18080
+ },{
+ "host": "1780407354",
+ "id": 17193661050352240890,
+ "ip": 1780407354,
+ "last_seen": 1525540510,
+ "port": 18080
+ }, ...
+ ]
+}
+```
+
+
+### **/set_log_hash_rate**
+
+Set the log hash rate display mode.
+
+Alias: *None*.
+
+Inputs:
+
+* *visible* - boolean; States if hash rate logs should be visible (`true`) or hidden (`false`)
+
+Outputs:
+
+* *status* - string; General RPC error code. "OK" means everything looks good. Any other value means that something went wrong.
+
+Example while mining:
+
+```
+$ curl -X POST http://127.0.0.1:18081/set_log_hash_rate -d '{"visible":true}' -H 'Content-Type: application/json'
+
+{
+ "status": "OK"
+}
+```
+
+Error while not mining:
+
+```
+$ curl -X POST http://127.0.0.1:18081/set_log_hash_rate -d '{"visible":true}' -H 'Content-Type: application/json'
+
+{
+ "status": "NOT MINING"
+}
+```
+
+
+### **/set_log_level**
+
+Set the daemon log level.
+By default, log level is set to `0`.
+
+Alias: *None*.
+
+Inputs:
+
+* *level* - integer; daemon log level to set from `0` (less verbose) to `4` (most verbose)
+
+Outputs:
+
+* *status* - string; General RPC error code. "OK" means everything looks good. Any other value means that something went wrong.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/set_log_level -d '{"level":1}' -H 'Content-Type: application/json'
+
+{
+ "status": "OK"
+}
+```
+
+
+### **/set_log_categories**
+
+Set the daemon log categories.
+Categories are represented as a comma separated list of `:` (similarly to syslog standard `:`), where:
+* *Category* is one of the following:
+ * *\** - All facilities
+ * *default*
+ * *net*
+ * *net.http*
+ * *net.p2p*
+ * *logging*
+ * *net.throttle*
+ * *blockchain.db*
+ * *blockchain.db.lmdb*
+ * *bcutil*
+ * *checkpoints*
+ * *net.dns*
+ * *net.dl*
+ * *i18n*
+ * *perf*
+ * *stacktrace*
+ * *updates*
+ * *account*
+ * *cn*
+ * *difficulty*
+ * *hardfork*
+ * *miner*
+ * *blockchain*
+ * *txpool*
+ * *cn.block_queue*
+ * *net.cn*
+ * *daemon*
+ * *debugtools.deserialize*
+ * *debugtools.objectsizes*
+ * *device.ledger*
+ * *wallet.gen_multisig*
+ * *multisig*
+ * *bulletproofs*
+ * *ringct*
+ * *daemon.rpc*
+ * *wallet.simplewallet*
+ * *WalletAPI*
+ * *wallet.ringdb*
+ * *wallet.wallet2*
+ * *wallet.rpc*
+ * *tests.core*
+* *Level* is one of the following:
+ * *FATAL* - higher level
+ * *ERROR*
+ * *WARNING*
+ * *INFO*
+ * *DEBUG*
+ * *TRACE* - lower level
+A level automatically includes higher level.
+By default, categories are set to `*:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO,logging:INFO,msgwriter:INFO`.
+Setting the categories to "" prevent any logs to be outputed.
+
+Alias: *None*.
+
+Inputs:
+
+* *categories* - string; Optional, daemon log categories to enable
+
+Outputs:
+
+* *categories* - string; daemon log enabled categories
+* *status* - string; General RPC error code. "OK" means everything looks good. Any other value means that something went wrong.
+
+Example to set all facilities to Security Level `Info`:
+
+```
+$ curl -X POST http://127.0.0.1:18081/set_log_categories -d '{"categories": "*:INFO"}' -H 'Content-Type: application/json'
+
+{
+ "categories": "*:INFO",
+ "status": "OK"
+}
+```
+
+Example without input to set the default categories:
+
+```
+$ curl -X POST http://127.0.0.1:18081/set_log_categories -H 'Content-Type: application/json'
+
+{
+ "categories": "*:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO,logging:INFO,msgwriter:INFO",
+ "status": "OK"
+}
+```
+
+
+### **/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 for the txpool in the node's memory.
+
+Alias: *None*.
+
+Inputs: *None*.
+
+Outputs:
+
+* *spent_key_images* - List of spent output key images:
+ * *id_hash* - string; Key image.
+ * *txs_hashes* - string list; tx hashes of the txes (usually one) spending that key image.
+* *status* - string; General RPC error code. "OK" means everything looks good.
+* *transactions* - List of transactions in the mempool are not in a block on the main chain at the moment:
+ * *blob_size* - unsigned int; The size of the full transaction blob.
+ * *double_spend_seen* - boolean; States if this transaction has been seen as double spend.
+ * *do_not_relay*; boolean; States if this transaction should not be relayed
+ * *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; States if the tx was included in a block at least once (`true`) or not (`false`).
+ * *last_failed_height* - unsigned int; If the transaction validation has previously failed, this tells at what height that occured.
+ * *last_failed_id_hash* - string; Like the previous, this tells the previous transaction ID hash.
+ * *last_relayed_time* - unsigned int; Last unix time at which the transaction has been relayed.
+ * *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.
+ * *relayed* - boolean; States if this transaction has been relayed
+ * *tx_blob* - unsigned int; Hexadecimal blob represnting the transaction.
+ * *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.
+ * *rct_signatures* - Ring signatures:
+ * *type*
+ * *txnFee*
+ * *ecdhInfo* - array of Diffie Helman Elipctic curves structures as follows:
+ * *mask* - String
+ * *amount* - String
+ * *outPk*
+ * *rctsig_prunable*
+ * *rangeSigs* - array of structures as follows:
+ * *asig*
+ * *Ci*
+ * *MGs* - array of structures as follows:
+ * *ss* - array of arrays of two strings.
+ * *cc* - String
+
+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": "a2af919609db4ff5ab8d4ba18502e647d521760e1cbc30288f06fa87bf9a0c1c",
+ "txs_hashes": ["1ee6a4873b638711795fc3b0b73fc7146505a09a7f4749534fd408d571a273cf"]
+ },{
+ "id_hash": "02d5f6559e9bca5ae5a335130aeeb05df2db518ab9837fa64ebbab276c100792",
+ "txs_hashes": ["531aacc0ceb8514cdde5f104285202ccc3e969c77584e3c6fa614c987c583965"]
+ },
+ ...],
+ "status": "OK",
+ "transactions": [{
+ "blob_size": 13193,
+ "do_not_relay": false,
+ "double_spend_seen": false,
+ "fee": 9694360000,
+ "id_hash": "f8fb875cfc9e2e59bcf96a42474c79e01d50b69e6548d445d45984f7db66e50f",
+ "kept_by_block": false,
+ "last_failed_height": 0,
+ "last_failed_id_hash": "0000000000000000000000000000000000000000000000000000000000000000",
+ "last_relayed_time": 1525615049,
+ "max_used_block_height": 1564924,
+ "max_used_block_id_hash": "4bae7856979f46c7de31f3fb58cac36d4dfd2765bf33f876edf33d0e05ebb4a7",
+ "receive_time": 1525615049,
+ "relayed": true,
+ "tx_blob": " ... ",
+ "tx_json": "{\n \"version\": 2, \n \"unlock_time\": 0, \n \"vin\": [ {\n \"key\": {\n \"amount\": 0, \n \"key_offsets\": [ 2630347, 594429, 1047509, 758973, 464501, 61971, 22268\n ], \n \"k_image\": \"0731363c58dd4492f031fa20c82fe6ddcb9cc070d73938afe8a5f7f77897f8b4\"\n }\n }\n ], \n \"vout\": [ {\n \"amount\": 0, \n \"target\": {\n \"key\": \"f3b3dd09483616e343b9866eed50a0ce01d5c0d0f2612ce2c4d0e9cce5c218cd\"\n }\n }, {\n \"amount\": 0, \n \"target\": {\n \"key\": \"9796f2d477a696b6282bf3cb1a41cefba0c4604eedcc2e7a44904d7033643e0e\"\n }\n }\n ], \n \"extra\": [ 1, 25, 228, 80, 5, 214, 117, 150, 9, 125, 98, 17, 113, 208, 89, 223, 242, 227, 188, 197, 141, 190, 135, 140, 152, 117, 240, 150, 21, 93, 62, 108, 124\n ], \n \"rct_signatures\": {\n \"type\": 1, \n \"txnFee\": 9694360000, \n \"ecdhInfo\": [ {\n \"mask\": \"645f06a2816aecf83d5041c3320eb31092b994fb2733bb74c8c47e288d452c04\", \n \"amount\": \"3908f14d39dcb3831331cb255eeadc5b0aea0143645b9cd3034abf613995740d\"\n }, {\n \"mask\": \"0785b5df0a994b14d59da810503a022721d8f629720f526e15bd848ad3c2c509\", \n \"amount\": \"fbd81cf2368dcd742905ded5287457030467aaf5bc9939e13f1d6bf8d4c8ca09\"\n }], \n \"outPk\": [ \"c19f5fa052859126e0eed0e3c860aadab049677b2b3dd14cc74d02f92f1d013f\", \"1581ef6368de1608ea366566b88272db220479cf215f6d88d7b60ec221d11e0a\"]\n }, \n \"rctsig_prunable\": {\n \"rangeSigs\": [ {\n \"asig\": \" ... \", \n \"Ci\": \" .. \"\n }, {\n \"asig\": \" ... \", \n \"Ci\": \" ... \"\n }], \n \"MGs\": [ {\n \"ss\": [ [ \"218a10a29e0f66e5a324af67b7734708a8a4cc8f16b28acd8cda538aaa495a02\", \"b368b4e956df5808c5c257f0dc3f7eff8c28463d0bb20759d19977fa02d6f205\"], [ \"f741d2c96bc23b362b4155a03fb6f1351ab5bf4445a43b3e52ba776f526af305\", \"a10ad1ee80dce3f311dd3dc141803daeecaa4d2a25a390cd9c35e4161b7c9e0c\"],
+ ...], \n \"cc\": \"e93801b707261ca76e146fdf2085abae71ad9203a00edc843c74f4ead8a39601\"\n }]\n }\n}"
+ },
+ ...]
+}
+```
+
+
+### **/get_transaction_pool_hashes.bin**
+
+Get hashes from transaction pool. Binary request.
+
+Alias: *None*.
+
+Inputs: *None*.
+
+Outputs:
+
+* *status* - string; General RPC error code. "OK" means everything looks good.
+* *tx_hashes* - binary array of transaction hashes.
+* *untrusted* - boolean; States if the result is obtained using the bootstrap mode, and is therefore not trusted (`true`), or when the daemon is fully synced (`false`).
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/get_transaction_pool_hashes.bin -H 'Content-Type: application/json'
+
+{
+ "status": "OK",
+ "tx_hashes": " ... ",
+ "untrusted": false
+}
+```
+
+
+### **/get_transaction_pool_stats**
+
+Get the transaction pool statistics.
+
+Alias: *None*.
+
+Inputs: *None*.
+
+Outputs:
+
+* *pool_stats* - Structure as follows:
+ * *bytes_max* - unsigned int; Max transaction size in pool
+ * *bytes_med* - unsigned int; Median transaction size in pool
+ * *bytes_min* - unsigned int; Min transaction size in pool
+ * *bytes_total* - unsigned int; total size of all transactions in pool
+ * *histo* - structure *txpool_histo* as follows:
+ * *txs* - unsigned int; number of transactions
+ * *bytes* - unsigned int; size in bytes.
+ * *histo_98pc* unsigned int; the time 98% of txes are "younger" than
+ * *num_10m* unsigned int; number of transactions in pool for more than 10 minutes
+ * *num_double_spends* unsigned int; number of double spend transactions
+ * *num_failing* unsigned int; number of failing transactions
+ * *num_not_relayed* unsigned int; number of non-relayed transactions
+ * *oldest* unsigned int; unix time of the oldest transaction in the pool
+ * *txs_total* unsigned int; total number of transactions.
+* *status* - string; General RPC error code. "OK" means everything looks good.
+* *untrusted* - boolean; States if the result is obtained using the bootstrap mode, and is therefore not trusted (`true`), or when the daemon is fully synced (`false`).
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/get_transaction_pool_stats -H 'Content-Type: application/json'
+
+{
+ "pool_stats": {
+ "bytes_max": 47222,
+ "bytes_med": 13290,
+ "bytes_min": 13092,
+ "bytes_total": 449511,
+ "fee_total": 289715320000,
+ "histo": "\t▒'▒5▒4▒\/▒▒▒$3",
+ "histo_98pc": 0,
+ "num_10m": 18,
+ "num_double_spends": 1,
+ "num_failing": 17,
+ "num_not_relayed": 0,
+ "oldest": 1525457001,
+ "txs_total": 26
+ },
+ "status": "OK",
+ "untrusted": false
+}
+```
+
+
+### **/stop_daemon**
+
+Send a command to the daemon to safely disconnect and shut down.
+
+Alias: *None*.
+
+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"
+}
+```
+
+
+### **/get_info (not JSON)**
+
+This method is a convenient backward support and should not be used anymore. See [get_info](#get_info) JSON RPC for details.
+
+Alias:
+
+* */getinfo*
+* *get_info*
+
+
+### **/get_limit**
+
+Get daemon bandwidth limits.
+
+Alias: *None*.
+
+Inputs: *None*.
+
+Outputs:
+
+* *limit_down* - unsigned int; Download limit in kBytes per second
+* *limit_up* - unsigned int; Upload limit in kBytes per second
+* *status* - string; General RPC error code. "OK" means everything looks good.
+* *untrusted* - boolean; States if the result is obtained using the bootstrap mode, and is therefore not trusted (`true`), or when the daemon is fully synced (`false`).
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/get_limit -H 'Content-Type: application/json'
+
+{
+ "limit_down": 8192,
+ "limit_up": 128,
+ "status": "OK",
+ "untrusted": false
+}
+```
+
+
+### **/set_limit**
+
+Set daemon bandwidth limits.
+
+Alias: *None*.
+
+Inputs:
+
+* *limit_down* - signed int; Download limit in kBytes per second (-1 reset to default, 0 don't change the current limit)
+* *limit_up* - signed int; Upload limit in kBytes per second (-1 reset to default, 0 don't change the current limit)
+
+Outputs:
+
+* *limit_down* - unsigned int; Download limit in kBytes per second
+* *limit_up* - unsigned int; Upload limit in kBytes per second
+* *status* - string; General RPC error code. "OK" means everything looks good.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/set_limit -d '{"limit_down": 1024}' -H 'Content-Type: application/json'
+
+{
+ "limit_down": 1024,
+ "limit_up": 128,
+ "status": "OK"
+}
+```
+
+
+### **/out_peers**
+
+Limit number of Outgoing peers.
+
+Alias: *None*.
+
+Inputs:
+
+* *out_peers* - unsigned int; Max number of outgoing peers
+
+Outputs:
+
+* *status* - string; General RPC error code. "OK" means everything looks good.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/out_peers -d '{"out_peers": 3232235535}' -H 'Content-Type: application/json'
+
+{
+ "status": "OK"
+}
+```
+
+
+### **/in_peers**
+
+Limit number of Incoming peers.
+
+Alias: *None*.
+
+Inputs:
+
+* *in_peers* - unsigned int; Max number of incoming peers
+
+Outputs:
+
+* *status* - string; General RPC error code. "OK" means everything looks good.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/out_peers -d '{"in_peers": 3232235535}' -H 'Content-Type: application/json'
+
+{
+ "status": "OK"
+}
+```
+
+
+### **/start_save_graph**
+
+Obsolete. Conserved here for reference.
+
+Alias: *None*.
+
+Inputs: *None*.
+
+Outputs:
+
+* *status* - string; General RPC error code. "OK" means everything looks good.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/start_save_graph -H 'Content-Type: application/json'
+
+{
+ "status": "OK"
+}
+```
+
+
+### **/stop_save_graph**
+
+Obsolete. Conserved here for reference.
+
+Alias: *None*.
+
+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_save_graph -H 'Content-Type: application/json'
+
+{
+ "status": "OK"
+}
+```
+
+
+### **/get_outs**
+
+Get outputs.
+
+Alias: *None*.
+
+Inputs:
+
+* *outputs* array of *get_outputs_out* structure as follows:
+ * *amount* - unsigned int;
+ * *index* - unsigned int;
+
+Outputs:
+
+* *outs* - array of structure *outkey* as follows:
+ * *height* - unsigned int; block height of the output
+ * *key* - String; the public key of the output
+ * *mask* - String
+ * *txid* - String; transaction id
+ * *unlocked* - boolean; States if output is locked (`false`) or not (`true`)
+* *status* - string; General RPC error code. "OK" means everything looks good.
+* *untrusted* - boolean; States if the result is obtained using the bootstrap mode, and is therefore not trusted (`true`), or when the daemon is fully synced (`false`).
+
+
+### **/update**
+
+Update daemon.
+
+Alias: *None*.
+
+Inputs:
+
+* *command* - String; command to use, either `check` or `download`
+* *path* - String; Optional, path where to download the update.
+
+Outputs:
+
+* *auto_uri* - string;
+* *hash* - string;
+* *path* - String; path to download the update
+* *status* - string; General RPC error code. "OK" means everything looks good.
+* *update* - boolean; States if an update is available to download (`true`) or not (`false`)
+* *user_uri* - string;
+* *version* - string; Version available for download.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18081/update -d '{"command":"check"}' -H 'Content-Type: application/json'
+
+{
+ "auto_uri": "",
+ "hash": "",
+ "path": "",
+ "status": "OK",
+ "update": false,
+ "user_uri": "",
+ "version": ""
+}
+```
+
diff --git a/_i18n/nl/resources/developer-guides/wallet-rpc.md b/_i18n/nl/resources/developer-guides/wallet-rpc.md
new file mode 100644
index 00000000..cc441cc8
--- /dev/null
+++ b/_i18n/nl/resources/developer-guides/wallet-rpc.md
@@ -0,0 +1,2733 @@
+{% assign version = '2.1.0' | split: '.' %}
+{% include disclaimer.html translated="true" version=page.version %}
+## 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.**
+
+This list has been updated on a frozen code on 2018-09-14 after merged commit bb30a7236725e456138f055f96a634c75ce2b491 (Wallet RPC version 1.3), and at block height 1643308.
+
+### Index of JSON RPC Methods:
+
+* [get_balance](#get_balance)
+* [get_address](#get_address)
+* [get_address_index](#get_address_index)
+* [create_address](#create_address)
+* [label_address](#label_address)
+* [get_accounts](#get_accounts)
+* [create_account](#create_account)
+* [label_account](#label_account)
+* [get_account_tags](#get_account_tags)
+* [tag_accounts](#tag_accounts)
+* [untag_accounts](#untag_accounts)
+* [set_account_tag_description](#set_account_tag_description)
+* [get_height](#get_height)
+* [transfer](#transfer)
+* [transfer_split](#transfer_split)
+* [sign_transfer](#sign_transfer)
+* [submit_transfer](#submit_transfer)
+* [sweep_dust](#sweep_dust)
+* [sweep_all](#sweep_all)
+* [sweep_single](#sweep_single)
+* [relay_tx](#relay_tx)
+* [store](#store)
+* [get_payments](#get_payments)
+* [get_bulk_payments](#get_bulk_payments)
+* [incoming_transfers](#incoming_transfers)
+* [query_key](#query_key)
+* [make_integrated_address](#make_integrated_address)
+* [split_integrated_address](#split_integrated_address)
+* [stop_wallet](#stop_wallet)
+* [rescan_blockchain](#rescan_blockchain)
+* [set_tx_notes](#set_tx_notes)
+* [get_tx_notes](#get_tx_notes)
+* [set_attribute](#set_attribute)
+* [get_attribute](#get_attribute)
+* [get_tx_key](#get_tx_key)
+* [check_tx_key](#check_tx_key)
+* [get_tx_proof](#get_tx_proof)
+* [check_tx_proof](#check_tx_proof)
+* [get_spend_proof](#get_spend_proof)
+* [check_spend_proof](#check_spend_proof)
+* [get_reserve_proof](#get_reserve_proof)
+* [check_reserve_proof](#check_reserve_proof)
+* [get_transfers](#get_transfers)
+* [get_transfer_by_txid](#get_transfer_by_txid)
+* [sign](#sign)
+* [verify](#verify)
+* [export_outputs](#export_outputs)
+* [import_outputs](#import_outputs)
+* [export_key_images](#export_key_images)
+* [import_key_images](#import_key_images)
+* [make_uri](#make_uri)
+* [parse_uri](#parse_uri)
+* [get_address_book](#get_address_book)
+* [add_address_book](#add_address_book)
+* [delete_address_book](#delete_address_book)
+* [refresh](#refresh)
+* [rescan_spent](#rescan_spent)
+* [start_mining](#start_mining)
+* [stop_mining](#stop_mining)
+* [get_languages](#get_languages)
+* [create_wallet](#create_wallet)
+* [open_wallet](#open_wallet)
+* [close_wallet](#close_wallet)
+* [change_wallet_password](#change_wallet_password)
+* [is_multisig](#is_multisig)
+* [prepare_multisig](#prepare_multisig)
+* [make_multisig](#make_multisig)
+* [export_multisig_info](#export_multisig_info)
+* [import_multisig_info](#import_multisig_info)
+* [finalize_multisig](#finalize_multisig)
+* [sign_multisig](#sign_multisig)
+* [submit_multisig](#submit_multisig)
+* [get_version](#get_version)
+
+---
+
+## JSON RPC Methods:
+
+### **get_balance**
+
+Return the wallet's balance.
+
+Alias: *getbalance*.
+
+Inputs:
+
+* *account_index* - unsigned int; Return balance for this account.
+* *address_indices* - array of unsigned int; (Optional) Return balance detail for those subaddresses.
+
+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.
+* *multisig_import_needed* - boolean; True if importing multisig data is needed for returning a correct balance.
+* *per_subaddress* - array of subaddress information; Balance information for each subaddress in an account.
+ * *address_index* - unsigned int; Index of the subaddress in the account.
+ * *address* - string; Address at this index. Base58 representation of the public keys.
+ * *balance* - unsigned int; Balance for the subaddress (locked or unlocked).
+ * *unlocked_balance* - unsigned int; Unlocked balance for the subaddress.
+ * *label* - string; Label for the subaddress.
+ * *num_unspent_outputs* - unsigned int; Number of unspent outputs available for the subaddress.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_balance","params":{"account_index":0,"address_indices":[0,1]}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "balance": 157443303037455077,
+ "multisig_import_needed": false,
+ "per_subaddress": [{
+ "address": "55LTR8KniP4LQGJSPtbYDacR7dz8RBFnsfAKMaMuwUNYX6aQbBcovzDPyrQF9KXF9tVU6Xk3K8no1BywnJX6GvZX8yJsXvt",
+ "address_index": 0,
+ "balance": 157360317826255077,
+ "label": "Primary account",
+ "num_unspent_outputs": 5281,
+ "unlocked_balance": 157360317826255077
+ },{
+ "address": "7BnERTpvL5MbCLtj5n9No7J5oE5hHiB3tVCK5cjSvCsYWD2WRJLFuWeKTLiXo5QJqt2ZwUaLy2Vh1Ad51K7FNgqcHgjW85o",
+ "address_index": 1,
+ "balance": 59985211200000,
+ "label": "",
+ "num_unspent_outputs": 1,
+ "unlocked_balance": 59985211200000
+ }],
+ "unlocked_balance": 157443303037455077
+ }
+}
+```
+
+
+### **get_address**
+
+Return the wallet's addresses for an account. Optionally filter for specific set of subaddresses.
+
+Alias: *getaddress*.
+
+Inputs:
+
+* *account_index* - unsigned int; Return subaddresses for this account.
+* *address_index* - array of unsigned int; (Optional) List of subaddresses to return from an account.
+
+Outputs:
+
+* *address* - string; The 95-character hex address string of the monero-wallet-rpc in session.
+* *addresses* array of addresses informations
+ * *address* string; The 95-character hex (sub)address string.
+ * *label* string; Label of the (sub)address
+ * *address_index* unsigned int; index of the subaddress
+ * *used* boolean; states if the (sub)address has already received funds
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_address","params":{"account_index":0,"address_index":[0,1,4]}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "address": "55LTR8KniP4LQGJSPtbYDacR7dz8RBFnsfAKMaMuwUNYX6aQbBcovzDPyrQF9KXF9tVU6Xk3K8no1BywnJX6GvZX8yJsXvt",
+ "addresses": [{
+ "address": "55LTR8KniP4LQGJSPtbYDacR7dz8RBFnsfAKMaMuwUNYX6aQbBcovzDPyrQF9KXF9tVU6Xk3K8no1BywnJX6GvZX8yJsXvt",
+ "address_index": 0,
+ "label": "Primary account",
+ "used": true
+ },{
+ "address": "7BnERTpvL5MbCLtj5n9No7J5oE5hHiB3tVCK5cjSvCsYWD2WRJLFuWeKTLiXo5QJqt2ZwUaLy2Vh1Ad51K7FNgqcHgjW85o",
+ "address_index": 1,
+ "label": "",
+ "used": true
+ },{
+ "address": "77xa6Dha7kzCQuvmd8iB5VYoMkdenwCNRU9khGhExXQ8KLL3z1N1ZATBD1sFPenyHWT9cm4fVFnCAUApY53peuoZFtwZiw5",
+ "address_index": 4,
+ "label": "test2",
+ "used": true
+ }]
+ }
+}
+```
+
+
+
+### **get_address_index**
+
+Get account and address indexes from a specific (sub)address
+
+Alias: *None*.
+
+Inputs:
+
+* *address* - String; (sub)address to look for.
+
+Outputs:
+
+* *index* - subaddress informations
+ * *major* unsigned int; Account index.
+ * *minor* unsigned int; Address index.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_address_index","params":{"address":"7BnERTpvL5MbCLtj5n9No7J5oE5hHiB3tVCK5cjSvCsYWD2WRJLFuWeKTLiXo5QJqt2ZwUaLy2Vh1Ad51K7FNgqcHgjW85o"}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "index": {
+ "major": 0,
+ "minor": 1
+ }
+ }
+}
+```
+
+
+### **create_address**
+
+Create a new address for an account. Optionally, label the new address.
+
+Alias: *None*.
+
+Inputs:
+
+* *account_index* - unsigned int; Create a new address for this account.
+* *label* - string; (Optional) Label for the new address.
+
+Outputs:
+
+* *address* - string; Newly created address. Base58 representation of the public keys.
+* *address_index* - unsigned int; Index of the new address under the input account.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"create_address","params":{"account_index":0,"label":"new-sub"}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "address": "7BG5jr9QS5sGMdpbBrZEwVLZjSKJGJBsXdZLt8wiXyhhLjy7x2LZxsrAnHTgD8oG46ZtLjUGic2pWc96GFkGNPQQDA3Dt7Q",
+ "address_index": 5
+ }
+}
+```
+
+
+### **label_address**
+
+Label an address.
+
+Alias: *None*.
+
+Inputs:
+
+* *index* - subaddress index; JSON Object containing the major & minor address index:
+ * *major* - unsigned int; Account index for the subaddress.
+ * *minor* - unsigned int; Index of the subaddress in the account.
+* *label* - string; Label for the address.
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"label_address","params":{"index":{"major":0,"minor":5},"label":"myLabel"}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+### **get_accounts**
+
+Get all accounts for a wallet. Optionally filter accounts by tag.
+
+Alias: *None*.
+
+Inputs:
+
+* *tag* - string; (Optional) Tag for filtering accounts.
+
+Outputs:
+
+* *subaddress_accounts* - array of subaddress account information:
+ * *account_index* - unsigned int; Index of the account.
+ * *balance* - unsigned int; Balance of the account (locked or unlocked).
+ * *base_address* - string; Base64 representation of the first subaddress in the account.
+ * *label* - string; (Optional) Label of the account.
+ * *tag* - string; (Optional) Tag for filtering accounts.
+ * *unlocked_balance* - unsigned int; Unlocked balance for the account.
+* *total_balance* - unsigned int; Total balance of the selected accounts (locked or unlocked).
+* *total_unlocked_balance* - unsigned int; Total unlocked balance of the selected accounts.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_accounts","params":{"tag":"myTag"}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "subaddress_accounts": [{
+ "account_index": 0,
+ "balance": 157663195572433688,
+ "base_address": "55LTR8KniP4LQGJSPtbYDacR7dz8RBFnsfAKMaMuwUNYX6aQbBcovzDPyrQF9KXF9tVU6Xk3K8no1BywnJX6GvZX8yJsXvt",
+ "label": "Primary account",
+ "tag": "myTag",
+ "unlocked_balance": 157443303037455077
+ },{
+ "account_index": 1,
+ "balance": 0,
+ "base_address": "77Vx9cs1VPicFndSVgYUvTdLCJEZw9h81hXLMYsjBCXSJfUehLa9TDW3Ffh45SQa7xb6dUs18mpNxfUhQGqfwXPSMrvKhVp",
+ "label": "Secondary account",
+ "tag": "myTag",
+ "unlocked_balance": 0
+ }],
+ "total_balance": 157663195572433688,
+ "total_unlocked_balance": 157443303037455077
+ }
+}
+```
+
+
+### **create_account**
+
+Create a new account with an optional label.
+
+Alias: *None*.
+
+Inputs:
+
+* *label* - string; (Optional) Label for the account.
+
+Outputs:
+
+* *account_index* - unsigned int; Index of the new account.
+* *address* - string; Address for this account. Base58 representation of the public keys.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"create_account","params":{"label":"Secondary account"}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "account_index": 1,
+ "address": "77Vx9cs1VPicFndSVgYUvTdLCJEZw9h81hXLMYsjBCXSJfUehLa9TDW3Ffh45SQa7xb6dUs18mpNxfUhQGqfwXPSMrvKhVp"
+ }
+}
+```
+
+
+### **label_account**
+
+Label an account.
+
+Alias: *None*.
+
+Inputs:
+
+* *account_index* - unsigned int; Apply label to account at this index.
+* *label* - string; Label for the account.
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"label_account","params":{"account_index":0,"label":"Primary account"}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "account_tags": [{
+ "accounts": [0,1],
+ "label": "",
+ "tag": "myTag"
+ }]
+ }
+}
+```
+
+
+### **get_account_tags**
+
+Get a list of user-defined account tags.
+
+Alias: *None*.
+
+Inputs: *None*.
+
+Outputs:
+
+* *account_tags* - array of account tag information:
+ * *tag* - string; Filter tag.
+ * *label* - string; Label for the tag.
+ * *accounts* - array of int; List of tagged account indices.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_account_tags","params":""}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "account_tags": [{
+ "accounts": [0],
+ "label": "Test tag",
+ "tag": "myTag"
+ }]
+ }
+}
+```
+
+
+### **tag_accounts**
+
+Apply a filtering tag to a list of accounts.
+
+Alias: *None*.
+
+Inputs:
+
+* *tag* - string; Tag for the accounts.
+* *accounts* - array of unsigned int; Tag this list of accounts.
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"tag_accounts","params":{"tag":"myTag","accounts":[0,1]}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **untag_accounts**
+
+Remove filtering tag from a list of accounts.
+
+Alias: *None*.
+
+Inputs:
+
+* *accounts* - array of unsigned int; Remove tag from this list of accounts.
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"untag_accounts","params":{"accounts":[1]}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **set_account_tag_description**
+
+Set description for an account tag.
+
+Alias: *None*.
+
+Inputs:
+
+* *tag* - string; Set a description for this tag.
+* *description* - string; Description for the tag.
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"set_account_tag_description","params":{"tag":"myTag","description":"Test tag"}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **get_height**
+
+Returns the wallet's current block height.
+
+Alias: *getheight*.
+
+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":"get_height"}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "height": 145545
+ }
+}
+```
+
+
+### **transfer**
+
+Send monero to a number of recipients.
+
+Alias: *None*.
+
+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.
+* *account_index* - unsigned int; (Optional) Transfer from this account index. (Defaults to 0)
+* *subaddr_indices* - array of unsigned int; (Optional) Transfer from this set of subaddresses. (Defaults to 0)
+* *priority* - unsigned int; Set a priority for the transaction. Accepted Values are: 0-3 for: default, unimportant, normal, elevated, priority.
+* *mixin* - unsigned int; Number of outputs from the blockchain to mix with (0 means no mixing).
+* *ring_size* - unsigned int; Number of outputs to mix in the transaction (this output + N decoys from the blockchain).
+* *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.
+* *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 (Defaults to false)
+* *get_tx_metadata* - boolean; Return the metadata needed to relay the transaction. (Defaults to false)
+
+
+Outputs:
+
+* *amount* - Amount transferred for the transaction.
+* *fee* - Integer value of the fee charged for the txn.
+* *multisig_txset* - Set of multisig transactions in the process of being signed (empty for non-multisig).
+* *tx_blob* - Raw transaction represented as hex string, if get_tx_hex is true.
+* *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_metadata* - Set of transaction metadata needed to relay this transfer later, if get_tx_metadata is true.
+* *unsigned_txset* - String. Set of unsigned tx for cold-signing purposes.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"transfer","params":{"destinations":[{"amount":100000000000,"address":"7BnERTpvL5MbCLtj5n9No7J5oE5hHiB3tVCK5cjSvCsYWD2WRJLFuWeKTLiXo5QJqt2ZwUaLy2Vh1Ad51K7FNgqcHgjW85o"},{"amount":200000000000,"address":"75sNpRwUtekcJGejMuLSGA71QFuK1qcCVLZnYRTfQLgFU5nJ7xiAHtR5ihioS53KMe8pBhH61moraZHyLoG4G7fMER8xkNv"}],"account_index":0,"subaddr_indices":[0],"priority":0,"ring_size":7,"get_tx_key": true}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "amount": 300000000000,
+ "fee": 86897600000,
+ "multisig_txset": "",
+ "tx_blob": "",
+ "tx_hash": "7663438de4f72b25a0e395b770ea9ecf7108cd2f0c4b75be0b14a103d3362be9",
+ "tx_key": "25c9d8ec20045c80c93d665c9d3684aab7335f8b2cd02e1ba2638485afd1c70e236c4bdd7a2f1cb511dbf466f13421bdf8df988b7b969c448ca6239d7251490e4bf1bbf9f6ffacffdcdc93b9d1648ec499eada4d6b4e02ce92d4a1c0452e5d009fbbbf15b549df8856205a4c7bda6338d82c823f911acd00cb75850b198c5803",
+ "tx_metadata": "",
+ "unsigned_txset": ""
+ }
+}
+```
+
+
+### **transfer_split**
+
+Same as transfer, but can split into more than one tx if necessary.
+
+Alias: *None*.
+
+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.
+* *account_index* - unsigned int; (Optional) Transfer from this account index. (Defaults to 0)
+* *subaddr_indices* - array of unsigned int; (Optional) Transfer from this set of subaddresses. (Defaults to 0)
+* *mixin* - unsigned int; Number of outputs from the blockchain to mix with (0 means no mixing).
+* *ring_size* - unsigned int; Sets ringsize to n (mixin + 1).
+* *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.
+* *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.
+* *get_tx_metadata* - boolean; Return list of transaction metadata needed to relay the transfer later.
+
+Outputs:
+
+* *tx_hash_list* - array of: string. The tx hashes of every transaction.
+* *tx_key_list* - array of: string. The transaction keys for every transaction.
+* *amount_list* - array of: integer. The amount transferred for every transaction.
+* *fee_list* - array of: integer. The amount of fees paid for every transaction.
+* *tx_blob_list* - array of: string. The tx as hex string for every transaction.
+* *tx_metadata_list* - array of: string. List of transaction metadata needed to relay the transactions later.
+* *multisig_txset* - string. The set of signing keys used in a multisig transaction (empty for non-multisig).
+* *unsigned_txset* - string. Set of unsigned tx for cold-signing purposes.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"transfer_split","params":{"destinations":[{"amount":1000000000000,"address":"7BnERTpvL5MbCLtj5n9No7J5oE5hHiB3tVCK5cjSvCsYWD2WRJLFuWeKTLiXo5QJqt2ZwUaLy2Vh1Ad51K7FNgqcHgjW85o"},{"amount":2000000000000,"address":"75sNpRwUtekcJGejMuLSGA71QFuK1qcCVLZnYRTfQLgFU5nJ7xiAHtR5ihioS53KMe8pBhH61moraZHyLoG4G7fMER8xkNv"}],"account_index":0,"subaddr_indices":[0],"priority":0,"ring_size":7,"get_tx_key": true}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "amount_list": [3000000000000],
+ "fee_list": [85106400000],
+ "multisig_txset": "",
+ "tx_hash_list": ["c8d815f48f27d53fdaf198a74b292a91bfaf87529a9a9a9ee66079a890b3b58b"],
+ "unsigned_txset": ""
+ }
+}
+```
+
+
+### **sign_transfer**
+
+Sign a transaction created on a read-only wallet (in cold-signing process)
+
+Alias: *None*.
+
+Inputs:
+
+* *unsigned_txset* - string. Set of unsigned tx returned by "transfer" or "transfer_split" methods.
+* *export_raw* - boolean; (Optional) If true, return the raw transaction data. (Defaults to false)
+
+Outputs:
+
+* *signed_txset* - string. Set of signed tx to be used for submitting transfer.
+* *tx_hash_list* - array of: string. The tx hashes of every transaction.
+* *tx_raw_list* - array of: string. The tx raw data of every transaction.
+
+In the example below, we first generate an unsigned_txset on a read only wallet before signing it:
+
+Generate unsigned_txset using the above "transfer" method on read-only wallet:
+```
+curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"transfer","params":{"destinations":[{"amount":1000000000000,"address":"7BnERTpvL5MbCLtj5n9No7J5oE5hHiB3tVCK5cjSvCsYWD2WRJLFuWeKTLiXo5QJqt2ZwUaLy2Vh1Ad51K7FNgqcHgjW85o"}],"account_index":0,"subaddr_indices":[0],"priority":0,"ring_size":7,"do_not_relay":true,"get_tx_hex":true}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "amount": 1000000000000,
+ "fee": 15202740000,
+ "multisig_txset": "",
+ "tx_blob": "...long_hex...",
+ "tx_hash": "c648ba0a049e5ce4ec21361dbf6e4b21eac0f828eea9090215de86c76b31d0a4",
+ "tx_key": "",
+ "tx_metadata": "",
+ "unsigned_txset": "...long_hex..."
+ }
+}
+```
+
+Sign tx using the previously generated unsigned_txset
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"sign_transfer","params":{"unsigned_txset":...long_hex..."}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "signed_txset": "...long_hex...",
+ "tx_hash_list": ["ff2e2d49fbfb1c9a55754f786576e171c8bf21b463a74438df604b7fa6cebc6d"]
+ }
+}
+```
+
+
+### **submit_transfer**
+
+Submit a previously signed transaction on a read-only wallet (in cold-signing process).
+
+Alias: *None*.
+
+Inputs:
+
+* *tx_data_hex* - string; Set of signed tx returned by "sign_transfer"
+
+Outputs:
+
+* *tx_hash_list* - array of: string. The tx hashes of every transaction.
+
+In the example below, we submit the transfer using the signed_txset generated above:
+```
+curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"submit_transfer","params":{"tx_data_hex":...long_hex..."}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "tx_hash_list": ["40fad7c828bb383ac02648732f7afce9adc520ba5629e1f5d9c03f584ac53d74"]
+ }
+}
+```
+
+### **sweep_dust**
+
+Send all dust outputs back to the wallet's, to make them easier to spend (and mix).
+
+Alias: *sweep_unmixable*.
+
+Inputs:
+
+* *get_tx_keys* - boolean; (Optional) Return the transaction keys after sending.
+* *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; (Optional) Return the transactions as hex string after sending. (Defaults to false)
+* *get_tx_metadata* - boolean; (Optional) Return list of transaction metadata needed to relay the transfer later. (Defaults to false)
+
+Outputs:
+
+* *tx_hash_list* - array of: string. The tx hashes of every transaction.
+* *tx_key_list* - array of: string. The transaction keys for every transaction.
+* *amount_list* - array of: integer. The amount transferred for every transaction.
+* *fee_list* - array of: integer. The amount of fees paid for every transaction.
+* *tx_blob_list* - array of: string. The tx as hex string for every transaction.
+* *tx_metadata_list* - array of: string. List of transaction metadata needed to relay the transactions later.
+* *multisig_txset* - string. The set of signing keys used in a multisig transaction (empty for non-multisig).
+* *unsigned_txset* - string. Set of unsigned tx for cold-signing purposes.
+
+Example (In this example, `sweep_dust` returns nothing because there are no funds to sweep):
+
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"sweep_dust","params":{"get_tx_keys":true}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "multisig_txset": "",
+ "unsigned_txset": ""
+ }
+}
+```
+
+
+### **sweep_all**
+
+Send all unlocked balance to an address.
+
+Alias: *None*.
+
+Inputs:
+
+* *address* - string; Destination public address.
+* *account_index* - unsigned int; Sweep transactions from this account.
+* *subaddr_indices* - array of unsigned int; (Optional) Sweep from this set of subaddresses in the account.
+* *priority* - unsigned int; (Optional) Priority for sending the sweep transfer, partially determines fee.
+* *mixin* - unsigned int; Number of outputs from the blockchain to mix with (0 means no mixing).
+* *ring_size* - unsigned int; Sets ringsize to n (mixin + 1).
+* *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) Include outputs below this amount.
+* *do_not_relay* - boolean; (Optional) If true, do not relay this sweep transfer. (Defaults to false)
+* *get_tx_hex* - boolean; (Optional) return the transactions as hex encoded string. (Defaults to false)
+* *get_tx_metadata* - boolean; (Optional) return the transaction metadata as a string. (Defaults to false)
+
+Outputs:
+
+* *tx_hash_list* - array of: string. The tx hashes of every transaction.
+* *tx_key_list* - array of: string. The transaction keys for every transaction.
+* *amount_list* - array of: integer. The amount transferred for every transaction.
+* *fee_list* - array of: integer. The amount of fees paid for every transaction.
+* *tx_blob_list* - array of: string. The tx as hex string for every transaction.
+* *tx_metadata_list* - array of: string. List of transaction metadata needed to relay the transactions later.
+* *multisig_txset* - string. The set of signing keys used in a multisig transaction (empty for non-multisig).
+* *unsigned_txset* - string. Set of unsigned tx for cold-signing purposes.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"sweep_all","params":{"address":"55LTR8KniP4LQGJSPtbYDacR7dz8RBFnsfAKMaMuwUNYX6aQbBcovzDPyrQF9KXF9tVU6Xk3K8no1BywnJX6GvZX8yJsXvt","subaddr_indices":[4],"ring_size":7,"unlock_time":0,"get_tx_keys":true}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "amount_list": [9985885770000],
+ "fee_list": [14114230000],
+ "multisig_txset": "",
+ "tx_hash_list": ["ab4b6b65cc8cd8c9dd317d0b90d97582d68d0aa1637b0065b05b61f9a66ea5c5"],
+ "tx_key_list": ["b9b4b39d3bb3062ddb85ec0266d4df39058f4c86077d99309f218ce4d76af607"],
+ "unsigned_txset": ""
+ }
+}
+```
+
+
+### **sweep_single**
+
+Send all of a specific unlocked output to an address.
+
+Alias: *None*.
+
+Inputs:
+
+* *address* - string; Destination public address.
+* *account_index* - unsigned int; Sweep transactions from this account.
+* *subaddr_indices* - array of unsigned int; (Optional) Sweep from this set of subaddresses in the account.
+* *priority* - unsigned int; (Optional) Priority for sending the sweep transfer, partially determines fee.
+* *mixin* - unsigned int; Number of outputs from the blockchain to mix with (0 means no mixing).
+* *ring_size* - unsigned int; Sets ringsize to n (mixin + 1).
+* *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.
+* *key_image* - string; Key image of specific output to sweep.
+* *below_amount* - unsigned int; (Optional) Include outputs below this amount.
+* *do_not_relay* - boolean; (Optional) If true, do not relay this sweep transfer. (Defaults to false)
+* *get_tx_hex* - boolean; (Optional) return the transactions as hex encoded string. (Defaults to false)
+* *get_tx_metadata* - boolean; (Optional) return the transaction metadata as a string. (Defaults to false)
+
+Outputs:
+
+* *tx_hash_list* - array of: string. The tx hashes of every transaction.
+* *tx_key_list* - array of: string. The transaction keys for every transaction.
+* *amount_list* - array of: integer. The amount transferred for every transaction.
+* *fee_list* - array of: integer. The amount of fees paid for every transaction.
+* *tx_blob_list* - array of: string. The tx as hex string for every transaction.
+* *tx_metadata_list* - array of: string. List of transaction metadata needed to relay the transactions later.
+* *multisig_txset* - string. The set of signing keys used in a multisig transaction (empty for non-multisig).
+* *unsigned_txset* - string. Set of unsigned tx for cold-signing purposes.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"sweep_single","params":{"address":"74Jsocx8xbpTBEjm3ncKE5LBQbiJouyCDaGhgSiebpvNDXZnTAbW2CmUR5SsBeae2pNk9WMVuz6jegkC4krUyqRjA6VjoLD","ring_size":7,"unlock_time":0,"key_image":"a7834459ef795d2efb6f665d2fd758c8d9288989d8d4c712a68f8023f7804a5e","get_tx_keys":true}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "amount": 27126892247503,
+ "fee": 14111630000,
+ "multisig_txset": "",
+ "tx_blob": "",
+ "tx_hash": "106d4391a031e5b735ded555862fec63233e34e5fa4fc7edcfdbe461c275ae5b",
+ "tx_key": "",
+ "tx_metadata": "",
+ "unsigned_txset": ""
+ }
+}
+```
+
+
+### **relay_tx**
+
+Relay a transaction previously created with `"do_not_relay":true`.
+
+Alias: *None*.
+
+Inputs:
+
+* *hex* - string; transaction metadata returned from a `transfer` method with `get_tx_metadata` set to `true`.
+
+Outputs:
+
+* *tx_hash* - String for the publically searchable transaction hash.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"relay_tx","params":{"hex":"...tx_metadata..."}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "tx_hash": "1c42dcc5672bb09bccf33fb1e9ab4a498af59a6dbd33b3d0cfb289b9e0e25fa5"
+ }
+}
+```
+
+
+### **store**
+
+Save the wallet file.
+
+Alias: *None*.
+
+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.
+
+Alias: *None*.
+
+Inputs:
+
+* *payment_id* - string; Payment ID used to find the payments (16 characters hex).
+
+Outputs:
+
+* *payments* - list of:
+ * *payment_id* - string; Payment ID matching the input parameter.
+ * *tx_hash* - string; Transaction hash used as the transaction ID.
+ * *amount* - unsigned int; Amount for this payment.
+ * *block_height* - unsigned int; Height of the block that first confirmed this payment.
+ * *unlock_time* - unsigned int; Time (in block height) until this payment is safe to spend.
+ * *subaddr_index* - subaddress index:
+ * *major* - unsigned int; Account index for the subaddress.
+ * *minor* - unsigned int; Index of the subaddress in the account.
+ * *address* - string; Address receiving the payment; Base58 representation of the public keys.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_payments","params":{"payment_id":"60900e5603bf96e3"}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "payments": [{
+ "address": "55LTR8KniP4LQGJSPtbYDacR7dz8RBFnsfAKMaMuwUNYX6aQbBcovzDPyrQF9KXF9tVU6Xk3K8no1BywnJX6GvZX8yJsXvt",
+ "amount": 1000000000000,
+ "block_height": 127606,
+ "payment_id": "60900e5603bf96e3",
+ "subaddr_index": {
+ "major": 0,
+ "minor": 0
+ },
+ "tx_hash": "3292e83ad28fc1cc7bc26dbd38862308f4588680fbf93eae3e803cddd1bd614f",
+ "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.
+
+Alias: *None*.
+
+Inputs:
+
+* *payment_ids* - array of: string; Payment IDs used to find the payments (16 characters hex).
+* *min_block_height* - unsigned int; The block height at which to start looking for payments.
+
+Outputs:
+
+* *payments* - list of:
+ * *payment_id* - string; Payment ID matching one of the input IDs.
+ * *tx_hash* - string; Transaction hash used as the transaction ID.
+ * *amount* - unsigned int; Amount for this payment.
+ * *block_height* - unsigned int; Height of the block that first confirmed this payment.
+ * *unlock_time* - unsigned int; Time (in block height) until this payment is safe to spend.
+ * *subaddr_index* - subaddress index:
+ * *major* - unsigned int; Account index for the subaddress.
+ * *minor* - unsigned int; Index of the subaddress in the account.
+ * *address* - string; Address receiving the payment; Base58 representation of the public keys.
+
+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":["60900e5603bf96e3"],"min_block_height":"120000"}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "payments": [{
+ "address": "55LTR8KniP4LQGJSPtbYDacR7dz8RBFnsfAKMaMuwUNYX6aQbBcovzDPyrQF9KXF9tVU6Xk3K8no1BywnJX6GvZX8yJsXvt",
+ "amount": 1000000000000,
+ "block_height": 127606,
+ "payment_id": "60900e5603bf96e3",
+ "subaddr_index": {
+ "major": 0,
+ "minor": 0
+ },
+ "tx_hash": "3292e83ad28fc1cc7bc26dbd38862308f4588680fbf93eae3e803cddd1bd614f",
+ "unlock_time": 0
+ }]
+ }
+}
+```
+
+
+### **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.
+* *account_index* - unsigned int; (Optional) Return transfers for this account. (defaults to 0)
+* *subaddr_indices* - array of unsigned int; (Optional) Return transfers sent to these subaddresses.
+* *verbose* - boolean; (Optional) Enable verbose output, return key image if true.
+
+Outputs:
+
+* *transfers* - list of:
+ * *amount* - unsigned int; Amount of this transfer.
+ * *global_index* - unsigned int; Mostly internal use, can be ignored by most users.
+ * *key_image* - string; Key image for the incoming transfer's unspent output (empty unless verbose is true).
+ * *spent* - boolean; Indicates if this transfer has been spent.
+ * *subaddr_index* - unsigned int; Subaddress index for incoming transfer.
+ * *tx_hash* - string; Several incoming transfers may share the same hash if they were in the same transaction.
+ * *tx_size* - unsigned int; Size of transaction in bytes.
+
+Example, get all transfers:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"incoming_transfers","params":{"transfer_type":"all","account_index":0,"subaddr_indices":[3],"verbose":true}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "transfers": [{
+ "amount": 60000000000000,
+ "global_index": 122405,
+ "key_image": "768f5144777eb23477ab7acf83562581d690abaf98ca897c03a9d2b900eb479b",
+ "spent": true,
+ "subaddr_index": 3,
+ "tx_hash": "f53401f21c6a43e44d5dd7a90eba5cf580012ad0e15d050059136f8a0da34f6b",
+ "tx_size": 159
+ },{
+ "amount": 27126892247503,
+ "global_index": 594994,
+ "key_image": "7e561394806afd1be61980cc3431f6ef3569fa9151cd8d234f8ec13aa145695e",
+ "spent": false,
+ "subaddr_index": 3,
+ "tx_hash": "106d4391a031e5b735ded555862fec63233e34e5fa4fc7edcfdbe461c275ae5b",
+ "tx_size": 157
+ },{
+ "amount": 27169374733655,
+ "global_index": 594997,
+ "key_image": "e76c0a3bfeaae35e4173712f782eb34011198e26b990225b71aa787c8ba8a157",
+ "spent": false,
+ "subaddr_index": 3,
+ "tx_hash": "0bd959b59117ee1254bd8e5aa8e77ec04ef744144a1ffb2d5c1eb9380a719621",
+ "tx_size": 158
+ }]
+ }
+}
+```
+
+Example, get available transfers:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"incoming_transfers","params":{"transfer_type":"available","account_index":0,"subaddr_indices":[3],"verbose":true}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "transfers": [{
+ "amount": 27126892247503,
+ "global_index": 594994,
+ "key_image": "7e561394806afd1be61980cc3431f6ef3569fa9151cd8d234f8ec13aa145695e",
+ "spent": false,
+ "subaddr_index": 3,
+ "tx_hash": "106d4391a031e5b735ded555862fec63233e34e5fa4fc7edcfdbe461c275ae5b",
+ "tx_size": 157
+ },{
+ "amount": 27169374733655,
+ "global_index": 594997,
+ "key_image": "e76c0a3bfeaae35e4173712f782eb34011198e26b990225b71aa787c8ba8a157",
+ "spent": false,
+ "subaddr_index": 3,
+ "tx_hash": "0bd959b59117ee1254bd8e5aa8e77ec04ef744144a1ffb2d5c1eb9380a719621",
+ "tx_size": 158
+ }]
+ }
+}
+```
+
+Example, get unavailable transfers:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"incoming_transfers","params":{"transfer_type":"unavailable","account_index":0,"subaddr_indices":[3],"verbose":true}}' -H 'Content-Type: application/json'
+{
+"id": "0",
+"jsonrpc": "2.0",
+"result": {
+ "transfers": [{
+ "amount": 60000000000000,
+ "global_index": 122405,
+ "key_image": "768f5144777eb23477ab7acf83562581d690abaf98ca897c03a9d2b900eb479b",
+ "spent": true,
+ "subaddr_index": 3,
+ "tx_hash": "f53401f21c6a43e44d5dd7a90eba5cf580012ad0e15d050059136f8a0da34f6b",
+ "tx_size": 159
+ }]
+}
+}
+```
+
+
+### **query_key**
+
+Return the spend or view private key.
+
+Alias: *None*.
+
+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": "0a1a38f6d246e894600a3e27238a064bf5e8d91801df47a17107596b1378e501"
+ }
+}
+```
+
+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": "vocal either anvil films dolphin zeal bacon cuisine quote syndrome rejoices envy okay pancakes tulips lair greater petals organs enmity dedicated oust thwart tomorrow tomorrow"
+ }
+}
+```
+
+
+### **make_integrated_address**
+
+Make an integrated address from the wallet address and a payment id.
+
+Alias: *None*.
+
+Inputs:
+
+* *standard_address* - string; (Optional, defaults to primary address) Destination public address.
+* *payment_id* - string; (Optional, defaults to a random ID) 16 characters hex encoded.
+
+Outputs:
+
+* *integrated_address* - string
+* *payment_id* - string; hex encoded;
+
+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":{"standard_address":"55LTR8KniP4LQGJSPtbYDacR7dz8RBFnsfAKMaMuwUNYX6aQbBcovzDPyrQF9KXF9tVU6Xk3K8no1BywnJX6GvZX8yJsXvt"}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "integrated_address": "5F38Rw9HKeaLQGJSPtbYDacR7dz8RBFnsfAKMaMuwUNYX6aQbBcovzDPyrQF9KXF9tVU6Xk3K8no1BywnJX6GvZXCkbHUXdPHyiUeRyokn",
+ "payment_id": "420fa29b2d9a49f5"
+ }
+}
+```
+
+
+### **split_integrated_address**
+
+Retrieve the standard address and payment id corresponding to an integrated address.
+
+Alias: *None*.
+
+Inputs:
+
+* *integrated_address* - string
+
+Outputs:
+
+* *is_subaddress* - boolean; States if the address is a subaddress
+* *payment* - string; hex encoded
+* *standard_address* - string
+
+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": "5F38Rw9HKeaLQGJSPtbYDacR7dz8RBFnsfAKMaMuwUNYX6aQbBcovzDPyrQF9KXF9tVU6Xk3K8no1BywnJX6GvZXCkbHUXdPHyiUeRyokn"}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "is_subaddress": false,
+ "payment_id": "420fa29b2d9a49f5",
+ "standard_address": "55LTR8KniP4LQGJSPtbYDacR7dz8RBFnsfAKMaMuwUNYX6aQbBcovzDPyrQF9KXF9tVU6Xk3K8no1BywnJX6GvZX8yJsXvt"
+ }
+}
+```
+
+
+### **stop_wallet**
+
+Stops the wallet, storing the current state.
+
+Alias: *None*.
+
+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": {
+ }
+}
+```
+
+
+### **rescan_blockchain**
+
+Rescan the blockchain from scratch, losing any information which can not be recovered from the blockchain itself.
+This includes destination addresses, tx secret keys, tx notes, etc.
+
+Alias: *None*.
+
+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.
+
+Alias: *None*.
+
+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":["3292e83ad28fc1cc7bc26dbd38862308f4588680fbf93eae3e803cddd1bd614f"],"notes":["This is an example"]}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **get_tx_notes**
+
+Get string notes for transactions.
+
+Alias: *None*.
+
+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":["3292e83ad28fc1cc7bc26dbd38862308f4588680fbf93eae3e803cddd1bd614f"]}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "notes": ["This is an example"]
+ }
+}
+```
+
+
+### **set_attribute**
+
+Set arbitrary attribute.
+
+Alias: *None*.
+
+Inputs:
+
+* *key* - string; attribute name
+* *value* - string; attribute value
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"set_attribute","params":{"key":"my_attribute","value":"my_value"}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **get_attribute**
+
+Get attribute value by name.
+
+Alias: *None*.
+
+Inputs:
+
+* *key* - string; attribute name
+
+Outputs:
+
+* *value* - string; attribute value
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_attribute","params":{"key":"my_attribute"}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "value": "my_value"
+ }
+}
+```
+
+
+### **get_tx_key**
+
+Get transaction secret key from transaction id.
+
+Alias: *None*.
+
+Inputs:
+
+* *txid* - string; transaction id.
+
+Outputs:
+
+* *tx_key* - string; transaction secret key.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_tx_key","params":{"txid":"19d5089f9469db3d90aca9024dfcb17ce94b948300101c8345a5e9f7257353be"}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "tx_key": "feba662cf8fb6d0d0da18fc9b70ab28e01cc76311278fdd7fe7ab16360762b06"
+ }
+}
+```
+
+
+### **check_tx_key**
+
+Check a transaction in the blockchain with its secret key.
+
+Alias: *None*.
+
+Inputs:
+
+* *txid* - string; transaction id.
+* *tx_key* - string; transaction secret key.
+* *address* - string; destination public address of the transaction.
+
+Outputs:
+
+* *confirmations* - unsigned int; Number of block mined after the one with the transaction.
+* *in_pool* - boolean; States if the transaction is still in pool or has been added to a block.
+* *received* - unsigned int; Amount of the transaction.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"check_tx_key","params":{"txid":"19d5089f9469db3d90aca9024dfcb17ce94b948300101c8345a5e9f7257353be","tx_key":"feba662cf8fb6d0d0da18fc9b70ab28e01cc76311278fdd7fe7ab16360762b06","address":"7BnERTpvL5MbCLtj5n9No7J5oE5hHiB3tVCK5cjSvCsYWD2WRJLFuWeKTLiXo5QJqt2ZwUaLy2Vh1Ad51K7FNgqcHgjW85o"}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "confirmations": 0,
+ "in_pool": false,
+ "received": 1000000000000
+ }
+}
+```
+
+
+### **get_tx_proof**
+
+Get transaction signature to prove it.
+
+Alias: *None*.
+
+Inputs:
+
+* *txid* - string; transaction id.
+* *address* - string; destination public address of the transaction.
+* *message* - string; (Optional) add a message to the signature to further authenticate the prooving process.
+
+Outputs:
+
+* *signature* - string; transaction signature.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_tx_proof","params":{"txid":"19d5089f9469db3d90aca9024dfcb17ce94b948300101c8345a5e9f7257353be","address":"7BnERTpvL5MbCLtj5n9No7J5oE5hHiB3tVCK5cjSvCsYWD2WRJLFuWeKTLiXo5QJqt2ZwUaLy2Vh1Ad51K7FNgqcHgjW85o","message":"this is my transaction"}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "signature": "InProofV13vqBCT6dpSAXkypZmSEMPGVnNRFDX2vscUYeVS4WnSVnV5BwLs31T9q6Etfj9Wts6tAxSAS4gkMeSYzzLS7Gt4vvCSQRh9niGJMUDJsB5hTzb2XJiCkUzWkkcjLFBBRVD5QZ"
+ }
+}
+```
+
+
+### **check_tx_proof**
+
+Prove a transaction by checking its signature.
+
+Alias: *None*.
+
+Inputs:
+
+* *txid* - string; transaction id.
+* *address* - string; destination public address of the transaction.
+* *message* - string; (Optional) Should be the same message used in `get_tx_proof`.
+* *signature* - string; transaction signature to confirm.
+
+Outputs:
+
+* *confirmations* - unsigned int; Number of block mined after the one with the transaction.
+* *good* - boolean; States if the inputs proves the transaction.
+* *in_pool* - boolean; States if the transaction is still in pool or has been added to a block.
+* *received* - unsigned int; Amount of the transaction.
+
+In the example below, the transaction has been proven:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"check_tx_proof","params":{"txid":"19d5089f9469db3d90aca9024dfcb17ce94b948300101c8345a5e9f7257353be","address":"7BnERTpvL5MbCLtj5n9No7J5oE5hHiB3tVCK5cjSvCsYWD2WRJLFuWeKTLiXo5QJqt2ZwUaLy2Vh1Ad51K7FNgqcHgjW85o","message":"this is my transaction","signature":"InProofV13vqBCT6dpSAXkypZmSEMPGVnNRFDX2vscUYeVS4WnSVnV5BwLs31T9q6Etfj9Wts6tAxSAS4gkMeSYzzLS7Gt4vvCSQRh9niGJMUDJsB5hTzb2XJiCkUzWkkcjLFBBRVD5QZ"}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "confirmations": 482,
+ "good": true,
+ "in_pool": false,
+ "received": 1000000000000
+ }
+}
+```
+
+In the example below, the wrong message is used, avoiding the transaction to be proved:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"check_tx_proof","params":{"txid":"19d5089f9469db3d90aca9024dfcb17ce94b948300101c8345a5e9f7257353be","address":"7BnERTpvL5MbCLtj5n9No7J5oE5hHiB3tVCK5cjSvCsYWD2WRJLFuWeKTLiXo5QJqt2ZwUaLy2Vh1Ad51K7FNgqcHgjW85o","message":"wrong message","signature":"InProofV13vqBCT6dpSAXkypZmSEMPGVnNRFDX2vscUYeVS4WnSVnV5BwLs31T9q6Etfj9Wts6tAxSAS4gkMeSYzzLS7Gt4vvCSQRh9niGJMUDJsB5hTzb2XJiCkUzWkkcjLFBBRVD5QZ"}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "confirmations": 0,
+ "good": false,
+ "in_pool": false,
+ "received": 0
+ }
+}
+```
+
+
+### **get_spend_proof**
+
+Generate a signature to prove a spend. Unlike proving a transaction, it does not requires the destination public address.
+
+Alias: *None*.
+
+Inputs:
+
+* *txid* - string; transaction id.
+* *message* - string; (Optional) add a message to the signature to further authenticate the prooving process.
+
+Outputs:
+
+* *signature* - string; spend signature.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_spend_proof","params":{"txid":"19d5089f9469db3d90aca9024dfcb17ce94b948300101c8345a5e9f7257353be","message":"this is my transaction"}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "signature": "SpendProofV1aSh8Todhk54736iXgV6vJAFP7egxByuMWZeyNDaN2JY737S95X5zz5mNMQSuCNSLjjhi5HJCsndpNWSNVsuThxwv285qy1KkUrLFRkxMSCjfL6bbycYN33ScZ5UB4Fzseceo1ndpL393T1q638VmcU3a56dhNHF1RPZFiGPS61FA78nXFSqE9uoKCCoHkEz83M1dQVhxZV5CEPF2P6VioGTKgprLCH9vvj9k1ivd4SX19L2VSMc3zD1u3mkR24ioETvxBoLeBSpxMoikyZ6inhuPm8yYo9YWyFtQK4XYfAV9mJ9knz5fUPXR8vvh7KJCAg4dqeJXTVb4mbMzYtsSZXHd6ouWoyCd6qMALdW8pKhgMCHcVYMWp9X9WHZuCo9rsRjRpg15sJUw7oJg1JoGiVgj8P4JeGDjnZHnmLVa5bpJhVCbMhyM7JLXNQJzFWTGC27TQBbthxCfQaKdusYnvZnKPDJWSeceYEFzepUnsWhQtyhbb73FzqgWC4eKEFKAZJqT2LuuSoxmihJ9acnFK7Ze23KTVYgDyMKY61VXADxmSrBvwUtxCaW4nQtnbMxiPMNnDMzeixqsFMBtN72j5UqhiLRY99k6SE7Qf5f29haNSBNSXCFFHChPKNTwJrehkofBdKUhh2VGPqZDNoefWUwfudeu83t85bmjv8Q3LrQSkFgFjRT5tLo8TMawNXoZCrQpyZrEvnodMDDUUNf3NL7rxyv3gM1KrTWjYaWXFU2RAsFee2Q2MTwUW7hR25cJvSFuB1BX2bfkoCbiMk923tHZGU2g7rSKF1GDDkXAc1EvFFD4iGbh1Q5t6hPRhBV8PEncdcCWGq5uAL5D4Bjr6VXG8uNeCy5oYWNgbZ5JRSfm7QEhPv8Fy9AKMgmCxDGMF9dVEaU6tw2BAnJavQdfrxChbDBeQXzCbCfep6oei6n2LZdE5Q84wp7eoQFE5Cwuo23tHkbJCaw2njFi3WGBbA7uGZaGHJPyB2rofTWBiSUXZnP2hiE9bjJghAcDm1M4LVLfWvhZmFEnyeru3VWMETnetz1BYLUC5MJGFXuhnHwWh7F6r74FDyhdswYop4eWPbyrXMXmUQEccTGd2NaT8g2VHADZ76gMC6BjWESvcnz2D4n8XwdmM7ZQ1jFwhuXrBfrb1dwRasyXxxHMGAC2onatNiExyeQ9G1W5LwqNLAh9hvcaNTGaYKYXoceVzLkgm6e5WMkLsCwuZXvB"
+ }
+}
+```
+
+
+### **check_spend_proof**
+
+Prove a spend using a signature. Unlike proving a transaction, it does not requires the destination public address.
+
+Alias: *None*.
+
+Inputs:
+
+* *txid* - string; transaction id.
+* *message* - string; (Optional) Should be the same message used in `get_spend_proof`.
+* *signature* - string; spend signature to confirm.
+
+Outputs:
+
+* *good* - boolean; States if the inputs proves the spend.
+
+In the example below, the spend has been proven:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"check_spend_proof","params":{"txid":"19d5089f9469db3d90aca9024dfcb17ce94b948300101c8345a5e9f7257353be","message":"this is my transaction","signature":"SpendProofV1aSh8Todhk54736iXgV6vJAFP7egxByuMWZeyNDaN2JY737S95X5zz5mNMQSuCNSLjjhi5HJCsndpNWSNVsuThxwv285qy1KkUrLFRkxMSCjfL6bbycYN33ScZ5UB4Fzseceo1ndpL393T1q638VmcU3a56dhNHF1RPZFiGPS61FA78nXFSqE9uoKCCoHkEz83M1dQVhxZV5CEPF2P6VioGTKgprLCH9vvj9k1ivd4SX19L2VSMc3zD1u3mkR24ioETvxBoLeBSpxMoikyZ6inhuPm8yYo9YWyFtQK4XYfAV9mJ9knz5fUPXR8vvh7KJCAg4dqeJXTVb4mbMzYtsSZXHd6ouWoyCd6qMALdW8pKhgMCHcVYMWp9X9WHZuCo9rsRjRpg15sJUw7oJg1JoGiVgj8P4JeGDjnZHnmLVa5bpJhVCbMhyM7JLXNQJzFWTGC27TQBbthxCfQaKdusYnvZnKPDJWSeceYEFzepUnsWhQtyhbb73FzqgWC4eKEFKAZJqT2LuuSoxmihJ9acnFK7Ze23KTVYgDyMKY61VXADxmSrBvwUtxCaW4nQtnbMxiPMNnDMzeixqsFMBtN72j5UqhiLRY99k6SE7Qf5f29haNSBNSXCFFHChPKNTwJrehkofBdKUhh2VGPqZDNoefWUwfudeu83t85bmjv8Q3LrQSkFgFjRT5tLo8TMawNXoZCrQpyZrEvnodMDDUUNf3NL7rxyv3gM1KrTWjYaWXFU2RAsFee2Q2MTwUW7hR25cJvSFuB1BX2bfkoCbiMk923tHZGU2g7rSKF1GDDkXAc1EvFFD4iGbh1Q5t6hPRhBV8PEncdcCWGq5uAL5D4Bjr6VXG8uNeCy5oYWNgbZ5JRSfm7QEhPv8Fy9AKMgmCxDGMF9dVEaU6tw2BAnJavQdfrxChbDBeQXzCbCfep6oei6n2LZdE5Q84wp7eoQFE5Cwuo23tHkbJCaw2njFi3WGBbA7uGZaGHJPyB2rofTWBiSUXZnP2hiE9bjJghAcDm1M4LVLfWvhZmFEnyeru3VWMETnetz1BYLUC5MJGFXuhnHwWh7F6r74FDyhdswYop4eWPbyrXMXmUQEccTGd2NaT8g2VHADZ76gMC6BjWESvcnz2D4n8XwdmM7ZQ1jFwhuXrBfrb1dwRasyXxxHMGAC2onatNiExyeQ9G1W5LwqNLAh9hvcaNTGaYKYXoceVzLkgm6e5WMkLsCwuZXvB"}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "good": true
+ }
+}
+```
+
+In the example below, the wrong message is used, avoiding the spend to be proved:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"check_spend_proof","params":{"txid":"19d5089f9469db3d90aca9024dfcb17ce94b948300101c8345a5e9f7257353be","message":"wrong message","signature":"SpendProofV1aSh8Todhk54736iXgV6vJAFP7egxByuMWZeyNDaN2JY737S95X5zz5mNMQSuCNSLjjhi5HJCsndpNWSNVsuThxwv285qy1KkUrLFRkxMSCjfL6bbycYN33ScZ5UB4Fzseceo1ndpL393T1q638VmcU3a56dhNHF1RPZFiGPS61FA78nXFSqE9uoKCCoHkEz83M1dQVhxZV5CEPF2P6VioGTKgprLCH9vvj9k1ivd4SX19L2VSMc3zD1u3mkR24ioETvxBoLeBSpxMoikyZ6inhuPm8yYo9YWyFtQK4XYfAV9mJ9knz5fUPXR8vvh7KJCAg4dqeJXTVb4mbMzYtsSZXHd6ouWoyCd6qMALdW8pKhgMCHcVYMWp9X9WHZuCo9rsRjRpg15sJUw7oJg1JoGiVgj8P4JeGDjnZHnmLVa5bpJhVCbMhyM7JLXNQJzFWTGC27TQBbthxCfQaKdusYnvZnKPDJWSeceYEFzepUnsWhQtyhbb73FzqgWC4eKEFKAZJqT2LuuSoxmihJ9acnFK7Ze23KTVYgDyMKY61VXADxmSrBvwUtxCaW4nQtnbMxiPMNnDMzeixqsFMBtN72j5UqhiLRY99k6SE7Qf5f29haNSBNSXCFFHChPKNTwJrehkofBdKUhh2VGPqZDNoefWUwfudeu83t85bmjv8Q3LrQSkFgFjRT5tLo8TMawNXoZCrQpyZrEvnodMDDUUNf3NL7rxyv3gM1KrTWjYaWXFU2RAsFee2Q2MTwUW7hR25cJvSFuB1BX2bfkoCbiMk923tHZGU2g7rSKF1GDDkXAc1EvFFD4iGbh1Q5t6hPRhBV8PEncdcCWGq5uAL5D4Bjr6VXG8uNeCy5oYWNgbZ5JRSfm7QEhPv8Fy9AKMgmCxDGMF9dVEaU6tw2BAnJavQdfrxChbDBeQXzCbCfep6oei6n2LZdE5Q84wp7eoQFE5Cwuo23tHkbJCaw2njFi3WGBbA7uGZaGHJPyB2rofTWBiSUXZnP2hiE9bjJghAcDm1M4LVLfWvhZmFEnyeru3VWMETnetz1BYLUC5MJGFXuhnHwWh7F6r74FDyhdswYop4eWPbyrXMXmUQEccTGd2NaT8g2VHADZ76gMC6BjWESvcnz2D4n8XwdmM7ZQ1jFwhuXrBfrb1dwRasyXxxHMGAC2onatNiExyeQ9G1W5LwqNLAh9hvcaNTGaYKYXoceVzLkgm6e5WMkLsCwuZXvB"}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "good": false
+ }
+}
+```
+
+
+### **get_reserve_proof**
+
+Generate a signature to prove of an available amount in a wallet.
+
+Alias: *None*.
+
+Inputs:
+
+* *all* - boolean; Proves all wallet balance to be disposable.
+* *account_index* - unsigned int; Specify the account from witch to prove reserve. (ignored if `all` is set to true)
+* *amount* - unsigned int; Amount (in @atomic-units) to prove the account has for reserve. (ignored if `all` is set to true)
+* *message* - string; (Optional) add a message to the signature to further authenticate the prooving process.
+
+Outputs:
+
+* *signature* - string; reserve signature.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_reserve_proof","params":{"all":false,"account_index":0,"amount":100000000000}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "signature": "ReserveProofV11BZ23sBt9sZJeGccf84mzyAmNCP3KzYbE1111112VKmH111118NfCYJQjZ6c46gT2kXgcHCaSSZeL8sRdzqjqx7i1e7FQfQGu2o113UYFVdwzHQi3iENDPa76Kn1BvywbKz3bMkXdZkBEEhBSF4kjjGaiMJ1ucKb6wvMVC4A8sA4nZEdL2Mk3wBucJCYTZwKqA8i1M113kqakDkG25FrjiDqdQTCYz2wDBmfKxF3eQiV5FWzZ6HmAyxnqTWUiMWukP9A3Edy3ZXqjP1b23dhz7Mbj39bBxe3ZeDNu9HnTSqYvHNRyqCkeUMJpHyQweqjGUJ1DSfFYr33J1E7MkhMnEi1o7trqWjVix32XLetYfePG73yvHbS24837L7Q64i5n1LSpd9yMiQZ3Dyaysi5y6jPx7TpAvnSqBFtuCciKoNzaXoA3dqt9cuVFZTXzdXKqdt3cXcVJMNxY8RvKPVQHhUur94Lpo1nSpxf7BN5a5rHrbZFqoZszsZmiWikYPkLX72XUdw6NWjLrTBxSy7KuPYH86c6udPEXLo2xgN6XHMBMBJzt8FqqK7EcpNUBkuHm2AtpGkf9CABY3oSjDQoRF5n4vNLd3qUaxNsG4XJ12L9gJ7GrK273BxkfEA8fDdxPrb1gpespbgEnCTuZHqj1A"
+ }
+}
+```
+
+
+### **check_reserve_proof**
+
+Proves a wallet has a disposable reserve using a signature.
+
+Alias: *None*.
+
+Inputs:
+
+* *address* - string; Public address of the wallet.
+* *message* - string; (Optional) Should be the same message used in `get_reserve_proof`.
+* *signature* - string; reserve signature to confirm.
+
+Outputs:
+
+* *good* - boolean; States if the inputs proves the reserve.
+
+In the example below, the reserve has been proven:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"check_reserve_proof","params":{"address":"55LTR8KniP4LQGJSPtbYDacR7dz8RBFnsfAKMaMuwUNYX6aQbBcovzDPyrQF9KXF9tVU6Xk3K8no1BywnJX6GvZX8yJsXvt","signature":"ReserveProofV11BZ23sBt9sZJeGccf84mzyAmNCP3KzYbE1111112VKmH111118NfCYJQjZ6c46gT2kXgcHCaSSZeL8sRdzqjqx7i1e7FQfQGu2o113UYFVdwzHQi3iENDPa76Kn1BvywbKz3bMkXdZkBEEhBSF4kjjGaiMJ1ucKb6wvMVC4A8sA4nZEdL2Mk3wBucJCYTZwKqA8i1M113kqakDkG25FrjiDqdQTCYz2wDBmfKxF3eQiV5FWzZ6HmAyxnqTWUiMWukP9A3Edy3ZXqjP1b23dhz7Mbj39bBxe3ZeDNu9HnTSqYvHNRyqCkeUMJpHyQweqjGUJ1DSfFYr33J1E7MkhMnEi1o7trqWjVix32XLetYfePG73yvHbS24837L7Q64i5n1LSpd9yMiQZ3Dyaysi5y6jPx7TpAvnSqBFtuCciKoNzaXoA3dqt9cuVFZTXzdXKqdt3cXcVJMNxY8RvKPVQHhUur94Lpo1nSpxf7BN5a5rHrbZFqoZszsZmiWikYPkLX72XUdw6NWjLrTBxSy7KuPYH86c6udPEXLo2xgN6XHMBMBJzt8FqqK7EcpNUBkuHm2AtpGkf9CABY3oSjDQoRF5n4vNLd3qUaxNsG4XJ12L9gJ7GrK273BxkfEA8fDdxPrb1gpespbgEnCTuZHqj1A"}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "good": true,
+ "spent": 0,
+ "total": 100000000000
+ }
+}
+```
+
+In the example below, all wallet reserve has been proven:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"check_reserve_proof","params":{"address":"55LTR8KniP4LQGJSPtbYDacR7dz8RBFnsfAKMaMuwUNYX6aQbBcovzDPyrQF9KXF9tVU6Xk3K8no1BywnJX6GvZX8yJsXvt","message":"I have 10 at least","signature":"...signature..."}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "good": true,
+ "spent": 0,
+ "total": 164113855714662789
+ }
+}
+```
+
+In the example below, the wrong message is used, avoiding the reserve to be proved:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"check_spend_proof","params":{"txid":"19d5089f9469db3d90aca9024dfcb17ce94b948300101c8345a5e9f7257353be","message":"wrong message","signature":"SpendProofV1aSh8Todhk54736iXgV6vJAFP7egxByuMWZeyNDaN2JY737S95X5zz5mNMQSuCNSLjjhi5HJCsndpNWSNVsuThxwv285qy1KkUrLFRkxMSCjfL6bbycYN33ScZ5UB4Fzseceo1ndpL393T1q638VmcU3a56dhNHF1RPZFiGPS61FA78nXFSqE9uoKCCoHkEz83M1dQVhxZV5CEPF2P6VioGTKgprLCH9vvj9k1ivd4SX19L2VSMc3zD1u3mkR24ioETvxBoLeBSpxMoikyZ6inhuPm8yYo9YWyFtQK4XYfAV9mJ9knz5fUPXR8vvh7KJCAg4dqeJXTVb4mbMzYtsSZXHd6ouWoyCd6qMALdW8pKhgMCHcVYMWp9X9WHZuCo9rsRjRpg15sJUw7oJg1JoGiVgj8P4JeGDjnZHnmLVa5bpJhVCbMhyM7JLXNQJzFWTGC27TQBbthxCfQaKdusYnvZnKPDJWSeceYEFzepUnsWhQtyhbb73FzqgWC4eKEFKAZJqT2LuuSoxmihJ9acnFK7Ze23KTVYgDyMKY61VXADxmSrBvwUtxCaW4nQtnbMxiPMNnDMzeixqsFMBtN72j5UqhiLRY99k6SE7Qf5f29haNSBNSXCFFHChPKNTwJrehkofBdKUhh2VGPqZDNoefWUwfudeu83t85bmjv8Q3LrQSkFgFjRT5tLo8TMawNXoZCrQpyZrEvnodMDDUUNf3NL7rxyv3gM1KrTWjYaWXFU2RAsFee2Q2MTwUW7hR25cJvSFuB1BX2bfkoCbiMk923tHZGU2g7rSKF1GDDkXAc1EvFFD4iGbh1Q5t6hPRhBV8PEncdcCWGq5uAL5D4Bjr6VXG8uNeCy5oYWNgbZ5JRSfm7QEhPv8Fy9AKMgmCxDGMF9dVEaU6tw2BAnJavQdfrxChbDBeQXzCbCfep6oei6n2LZdE5Q84wp7eoQFE5Cwuo23tHkbJCaw2njFi3WGBbA7uGZaGHJPyB2rofTWBiSUXZnP2hiE9bjJghAcDm1M4LVLfWvhZmFEnyeru3VWMETnetz1BYLUC5MJGFXuhnHwWh7F6r74FDyhdswYop4eWPbyrXMXmUQEccTGd2NaT8g2VHADZ76gMC6BjWESvcnz2D4n8XwdmM7ZQ1jFwhuXrBfrb1dwRasyXxxHMGAC2onatNiExyeQ9G1W5LwqNLAh9hvcaNTGaYKYXoceVzLkgm6e5WMkLsCwuZXvB"}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "good": false
+ }
+}
+```
+
+
+### **get_transfers**
+
+Returns a list of transfers.
+
+Alias: *None*.
+
+Inputs:
+
+* *in* - boolean; (Optional) Include incoming transfers.
+* *out* - boolean; (Optional) Include outgoing transfers.
+* *pending* - boolean; (Optional) Include pending transfers.
+* *failed* - boolean; (Optional) Include failed transfers.
+* *pool* - boolean; (Optional) Include transfers from the daemon's transaction pool.
+* *filter_by_height* - boolean; (Optional) Filter transfers by block height.
+* *min_height* - unsigned int; (Optional) Minimum block height to scan for transfers, if filtering by height is enabled.
+* *max_height* - unsigned int; (Opional) Maximum block height to scan for transfers, if filtering by height is enabled (defaults to max block height).
+* *account_index* - unsigned int; (Optional) Index of the account to query for transfers. (defaults to 0)
+* *subaddr_indices* - array of unsigned int; (Optional) List of subaddress indices to query for transfers. (defaults to 0)
+
+Outputs:
+
+* *in* array of transfers:
+ * *address* - string; Public address of the transfer.
+ * *amount* - unsigned int; Amount transferred.
+ * *confirmations* - unsigned int; Number of block mined since the block containing this transaction (or block height at which the transaction should be added to a block if not yet confirmed).
+ * *double_spend_seen* - boolean; True if the key image(s) for the transfer have been seen before.
+ * *fee* - unsigned int; Transaction fee for this transfer.
+ * *height* - unsigned int; Height of the first block that confirmed this transfer (0 if not mined yet).
+ * *note* - string; Note about this transfer.
+ * *payment_id* - string; Payment ID for this transfer.
+ * *subaddr_index* - JSON object containing the major & minor subaddress index:
+ * *major* - unsigned int; Account index for the subaddress.
+ * *minor* - unsigned int; Index of the subaddress under the account.
+ * *suggested_confirmations_threshold* - unsigned int; Estimation of the confirmations needed for the transaction to be included in a block.
+ * *timestamp* - unsigned int; POSIX timestamp for when this transfer was first confirmed in a block (or timestamp submission if not mined yet).
+ * *txid* - string; Transaction ID for this transfer.
+ * *type* - string; Transfer type: "in"
+ * *unlock_time* - unsigned int; Number of blocks until transfer is safely spendable.
+* *out* array of transfers (see above).
+* *pending* array of transfers (see above).
+* *failed* array of transfers (see above).
+* *pool* array of transfers (see above).
+
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_transfers","params":{"in":true,"account_index":1}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "in": [{
+ "address": "77Vx9cs1VPicFndSVgYUvTdLCJEZw9h81hXLMYsjBCXSJfUehLa9TDW3Ffh45SQa7xb6dUs18mpNxfUhQGqfwXPSMrvKhVp",
+ "amount": 200000000000,
+ "confirmations": 1,
+ "double_spend_seen": false,
+ "fee": 21650200000,
+ "height": 153624,
+ "note": "",
+ "payment_id": "0000000000000000",
+ "subaddr_index": {
+ "major": 1,
+ "minor": 0
+ },
+ "suggested_confirmations_threshold": 1,
+ "timestamp": 1535918400,
+ "txid": "c36258a276018c3a4bc1f195a7fb530f50cd63a4fa765fb7c6f7f49fc051762a",
+ "type": "in",
+ "unlock_time": 0
+ }]
+ }
+}
+```
+
+### **get_transfer_by_txid**
+
+Show information about a transfer to/from this address.
+
+Alias: *None*.
+
+Inputs:
+
+* *txid* - string; Transaction ID used to find the transfer.
+* *account_index* - unsigned int; (Optional) Index of the account to query for the transfer.
+
+Outputs:
+
+* *transfer* - JSON object containing payment information:
+ * *address* - string; Address that transferred the funds. Base58 representation of the public keys.
+ * *amount* - unsigned int; Amount of this transfer.
+ * *confirmations* - unsigned int; Number of block mined since the block containing this transaction (or block height at which the transaction should be added to a block if not yet confirmed).
+ * *destinations* - array of JSON objects containing transfer destinations:
+ * *amount* - unsigned int; Amount transferred to this destination.
+ * *address* - string; Address for this destination. Base58 representation of the public keys.
+ * *double_spend_seen* - boolean; True if the key image(s) for the transfer have been seen before.
+ * *fee* - unsigned int; Transaction fee for this transfer.
+ * *height* - unsigned int; Height of the first block that confirmed this transfer.
+ * *note* - string; Note about this transfer.
+ * *payment_id* - string; Payment ID for this transfer.
+ * *subaddr_index* - JSON object containing the major & minor subaddress index:
+ * *major* - unsigned int; Account index for the subaddress.
+ * *minor* - unsigned int; Index of the subaddress under the account.
+ * *suggested_confirmations_threshold* - unsigned int; Estimation of the confirmations needed for the transaction to be included in a block.
+ * *timestamp* - unsigned int; POSIX timestamp for the block that confirmed this transfer (or timestamp submission if not mined yet).
+ * *txid* - string; Transaction ID of this transfer (same as input TXID).
+ * *type* - string; Type of transfer, one of the following: "in", "out", "pending", "failed", "pool"
+ * *unlock_time* - unsigned int; Number of blocks until transfer is safely spendable.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_transfer_by_txid","params":{"txid":"c36258a276018c3a4bc1f195a7fb530f50cd63a4fa765fb7c6f7f49fc051762a"}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "transfer": {
+ "address": "55LTR8KniP4LQGJSPtbYDacR7dz8RBFnsfAKMaMuwUNYX6aQbBcovzDPyrQF9KXF9tVU6Xk3K8no1BywnJX6GvZX8yJsXvt",
+ "amount": 300000000000,
+ "confirmations": 1,
+ "destinations": [{
+ "address": "7BnERTpvL5MbCLtj5n9No7J5oE5hHiB3tVCK5cjSvCsYWD2WRJLFuWeKTLiXo5QJqt2ZwUaLy2Vh1Ad51K7FNgqcHgjW85o",
+ "amount": 100000000000
+ },{
+ "address": "77Vx9cs1VPicFndSVgYUvTdLCJEZw9h81hXLMYsjBCXSJfUehLa9TDW3Ffh45SQa7xb6dUs18mpNxfUhQGqfwXPSMrvKhVp",
+ "amount": 200000000000
+ }],
+ "double_spend_seen": false,
+ "fee": 21650200000,
+ "height": 153624,
+ "note": "",
+ "payment_id": "0000000000000000",
+ "subaddr_index": {
+ "major": 0,
+ "minor": 0
+ },
+ "suggested_confirmations_threshold": 1,
+ "timestamp": 1535918400,
+ "txid": "c36258a276018c3a4bc1f195a7fb530f50cd63a4fa765fb7c6f7f49fc051762a",
+ "type": "out",
+ "unlock_time": 0
+ }
+ }
+}
+```
+
+
+### **sign**
+
+Sign a string.
+
+Alias: *None*.
+
+Inputs:
+
+* *data* - string; Anything you need to sign.
+
+Outputs:
+
+* *signature* - string; Signature generated against the "data" and the account public address.
+
+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": "SigV14K6G151gycjiGxjQ74tKX6A2LwwghvuHjcDeuRFQio5LS6Gb27BNxjYQY1dPuUvXkEbGQUkiHSVLPj4nJAHRrrw3"
+ }
+}
+```
+
+
+### **verify**
+
+Verify a signature on a string.
+
+Alias: *None*.
+
+Inputs:
+
+* *data* - string; What should have been signed.
+* *address* - string; Public address of the wallet used to `sign` the data.
+* *signature* - string; signature generated by `sign` method.
+
+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":"55LTR8KniP4LQGJSPtbYDacR7dz8RBFnsfAKMaMuwUNYX6aQbBcovzDPyrQF9KXF9tVU6Xk3K8no1BywnJX6GvZX8yJsXvt","signature":"SigV14K6G151gycjiGxjQ74tKX6A2LwwghvuHjcDeuRFQio5LS6Gb27BNxjYQY1dPuUvXkEbGQUkiHSVLPj4nJAHRrrw3"}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "good": true
+ }
+}
+```
+
+
+### **export_outputs**
+
+Export all outputs in hex format.
+
+Alias: *None*.
+
+Inputs: *None*.
+
+Outputs:
+
+* *outputs_data_hex* - string; wallet outputs in hex format.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"export_outputs"}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "outputs_data_hex": "...outputs..."
+ }
+}
+```
+
+
+### **import_outputs**
+
+Import outputs in hex format.
+
+Alias: *None*.
+
+Inputs:
+
+* *outputs_data_hex* - string; wallet outputs in hex format.
+
+Outputs:
+
+* *num_imported* - unsigned int; number of outputs imported.
+
+Example:
+
+```
+$ curl -X POST http://127.0.0.1:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"import_outputs","params":{"outputs_data_hex":"...outputs..."}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "num_imported": 6400
+ }
+}
+```
+
+
+### **export_key_images**
+
+Export a signed set of key images.
+
+Alias: *None*.
+
+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": "cd35239b72a35e26a57ed17400c0b66944a55de9d5bda0f21190fed17f8ea876",
+ "signature": "c9d736869355da2538ab4af188279f84138c958edbae3c5caf388a63cd8e780b8c5a1aed850bd79657df659422c463608ea4e0c730ba9b662c906ae933816d00"
+ },{
+ "key_image": "65158a8ee5a3b32009b85a307d85b375175870e560e08de313531c7dbbe6fc19",
+ "signature": "c96e40d09dfc45cfc5ed0b76bfd7ca793469588bb0cf2b4d7b45ef23d40fd4036057b397828062e31700dc0c2da364f50cd142295a8405b9fe97418b4b745d0c"
+ },...]
+ }
+}
+```
+
+
+### **import_key_images**
+
+Import signed key images list and verify their spent status.
+
+Alias: *None*.
+
+Inputs:
+
+* *signed_key_images* - array of signed key images:
+ * *key_image* - string;
+ * *signature* - string;
+
+Outputs:
+
+* *height* - unsigned int;
+* *spent* - unsigned int; Amount (in @atomic-units) spent from those key images.
+* *unspent* - unsigned int; Amount (in @atomic-units) still available from those key images.
+
+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":"cd35239b72a35e26a57ed17400c0b66944a55de9d5bda0f21190fed17f8ea876","signature":"c9d736869355da2538ab4af188279f84138c958edbae3c5caf388a63cd8e780b8c5a1aed850bd79657df659422c463608ea4e0c730ba9b662c906ae933816d00"},{"key_image":"65158a8ee5a3b32009b85a307d85b375175870e560e08de313531c7dbbe6fc19","signature":"c96e40d09dfc45cfc5ed0b76bfd7ca793469588bb0cf2b4d7b45ef23d40fd4036057b397828062e31700dc0c2da364f50cd142295a8405b9fe97418b4b745d0c"}]}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "height": 76428,
+ "spent": 62708953408711,
+ "unspent": 0
+ }
+}
+```
+
+
+### **make_uri**
+
+Create a payment URI using the official URI spec.
+
+Alias: *None*.
+
+Inputs:
+
+* *address* - string; Wallet address
+* *amount* - unsigned int; (optional) the integer amount to receive, in **atomic** units
+* *payment_id* - string; (optional) 16 or 64 character hexadecimal payment id
+* *recipient_name* - string; (optional) name of the payment recipient
+* *tx_description* - string; (optional) Description of the reason for the tx
+
+Outputs:
+
+* *uri* - string; This contains 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":"55LTR8KniP4LQGJSPtbYDacR7dz8RBFnsfAKMaMuwUNYX6aQbBcovzDPyrQF9KXF9tVU6Xk3K8no1BywnJX6GvZX8yJsXvt","amount":10,"payment_id":"420fa29b2d9a49f5","tx_description":"Testing out the make_uri function.","recipient_name":"el00ruobuob Stagenet wallet"}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "uri": "monero:55LTR8KniP4LQGJSPtbYDacR7dz8RBFnsfAKMaMuwUNYX6aQbBcovzDPyrQF9KXF9tVU6Xk3K8no1BywnJX6GvZX8yJsXvt?tx_payment_id=420fa29b2d9a49f5&tx_amount=0.000000000010&recipient_name=el00ruobuob%20Stagenet%20wallet&tx_description=Testing%20out%20the%20make_uri%20function."
+ }
+}
+```
+
+
+### **parse_uri**
+
+Parse a payment URI to get payment information.
+
+Alias: *None*.
+
+Inputs:
+
+* *uri* - string; This contains all the payment input information as a properly formatted payment URI
+
+Outputs:
+
+* *uri* - JSON object containing payment information:
+ * *address* - string; Wallet address
+ * *amount* - unsigned int; Decimal amount to receive, in **coin** units (0 if not provided)
+ * *payment_id* - string; 16 or 64 character hexadecimal payment id (empty if not provided)
+ * *recipient_name* - string; Name of the payment recipient (empty if not provided)
+ * *tx_description* - string; Description of 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:55LTR8KniP4LQGJSPtbYDacR7dz8RBFnsfAKMaMuwUNYX6aQbBcovzDPyrQF9KXF9tVU6Xk3K8no1BywnJX6GvZX8yJsXvt?tx_payment_id=420fa29b2d9a49f5&tx_amount=0.000000000010&recipient_name=el00ruobuob%20Stagenet%20wallet&tx_description=Testing%20out%20the%20make_uri%20function."}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "uri": {
+ "address": "55LTR8KniP4LQGJSPtbYDacR7dz8RBFnsfAKMaMuwUNYX6aQbBcovzDPyrQF9KXF9tVU6Xk3K8no1BywnJX6GvZX8yJsXvt",
+ "amount": 10,
+ "payment_id": "420fa29b2d9a49f5",
+ "recipient_name": "el00ruobuob Stagenet wallet",
+ "tx_description": "Testing out the make_uri function."
+ }
+ }
+}
+```
+
+
+### **get_address_book**
+
+Retrieves entries from the address book.
+
+Alias: *None*.
+
+Inputs:
+
+* *entries* - array of unsigned int; indices of the requested address book entries
+
+Outputs:
+
+* *entries* - array of entries:
+ * *address* - string; Public address of the entry
+ * *description* - string; Description of this address entry
+ * *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":[0,1]}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "entries": [{
+ "address": "77Vx9cs1VPicFndSVgYUvTdLCJEZw9h81hXLMYsjBCXSJfUehLa9TDW3Ffh45SQa7xb6dUs18mpNxfUhQGqfwXPSMrvKhVp",
+ "description": "Second account",
+ "index": 0,
+ "payment_id": "0000000000000000000000000000000000000000000000000000000000000000"
+ },{
+ "address": "78P16M3XmFRGcWFCcsgt1WcTntA1jzcq31seQX1Eg92j8VQ99NPivmdKam4J5CKNAD7KuNWcq5xUPgoWczChzdba5WLwQ4j",
+ "description": "Third account",
+ "index": 1,
+ "payment_id": "0000000000000000000000000000000000000000000000000000000000000000"
+ }]
+ }
+}
+```
+
+
+### **add_address_book**
+
+Add an entry to the address book.
+
+Alias: *None*.
+
+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":"78P16M3XmFRGcWFCcsgt1WcTntA1jzcq31seQX1Eg92j8VQ99NPivmdKam4J5CKNAD7KuNWcq5xUPgoWczChzdba5WLwQ4j","description":"Third account"}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "index": 1
+ }
+}
+```
+
+
+### **delete_address_book**
+
+Delete an entry from the address book.
+
+Alias: *None*.
+
+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":1}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **refresh**
+
+Refresh a wallet after openning.
+
+Alias: *None*.
+
+Inputs:
+
+* *start_height* - unsigned int; (Optional) The block height from which to start refreshing.
+
+Outputs:
+
+* *blocks_fetched* - unsigned int; Number of new blocks scanned.
+* *received_money* - boolean; States if transactions to the wallet have been found in the blocks.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"refresh","params":{"start_height":100000}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "blocks_fetched": 24,
+ "received_money": true
+ }
+}
+```
+
+
+### **rescan_spent**
+
+Rescan the blockchain for spent outputs.
+
+Alias: *None*.
+
+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.
+
+Alias: *None*.
+
+Inputs:
+
+* *threads_count* - unsigned int; Number of threads created for mining.
+* *do_background_mining* - boolean; Allow to start the miner in @smart-mining mode.
+* *ignore_battery* - boolean; Ignore battery status (for @smart-mining only)
+
+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":false}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **stop_mining**
+
+Stop mining in the Monero daemon.
+
+Alias: *None*.
+
+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.
+
+Alias: *None*.
+
+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","Lojban"]
+ }
+}
+```
+
+
+### **create_wallet**
+
+Create a new wallet. You need to have set the argument "--wallet-dir" when launching monero-wallet-rpc to make this work.
+
+Alias: *None*.
+
+Inputs:
+
+* *filename* - string; Wallet file name.
+* *password* - string; (Optional) password to protect the wallet.
+* *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.
+
+Alias: *None*.
+
+Inputs:
+
+* *filename* - string; wallet name stored in --wallet-dir.
+* *password* - string; (Optional) only needed if the wallet has a password defined.
+
+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": {
+ }
+}
+```
+
+
+### **close_wallet**
+
+Close the currently opened wallet, after trying to save it.
+
+Alias: *None*.
+
+Inputs: *None*.
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"close_wallet"}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **change_wallet_password**
+
+Change a wallet password.
+
+Alias: *None*.
+
+Inputs:
+
+* *old_password* - string; (Optional) Current wallet password, if defined.
+* *new_password* - string; (Optional) New wallet password, if not blank.
+
+Outputs: *None*.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"change_wallet_password","params":{"old_password":"theCurrentSecretPassPhrase","new_password":"theNewSecretPassPhrase"}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ }
+}
+```
+
+
+### **is_multisig**
+
+Check if a wallet is a multisig one.
+
+Alias: *None*.
+
+Inputs: *None*.
+
+Outputs:
+
+* *multisig* - boolean; States if the wallet is multisig
+* *ready* - boolean;
+* *threshold* - unsigned int; Amount of signature needed to sign a transfer.
+* *total* - unsigned int; Total amount of signature in the multisig wallet.
+
+Example for a non-multisig wallet:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"is_multisig"}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "multisig": false,
+ "ready": false,
+ "threshold": 0,
+ "total": 0
+ }
+}
+```
+Example for a multisig wallet:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"is_multisig"}' -H 'Content-Type: application/json' {
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "multisig": true,
+ "ready": true,
+ "threshold": 2,
+ "total": 2
+ }
+}
+```
+
+
+### **prepare_multisig**
+
+Prepare a wallet for multisig by generating a multisig string to share with peers.
+
+Alias: *None*.
+
+Inputs: *None*.
+
+Outputs:
+
+* *multisig_info* - string; Multisig string to share with peers to create the multisig wallet.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"prepare_multisig"}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "multisig_info": "MultisigV1BFdxQ653cQHB8wsj9WJQd2VdnjxK89g5M94dKPBNw22reJnyJYKrz6rJeXdjFwJ3Mz6n4qNQLd6eqUZKLiNzJFi3UPNVcTjtkG2aeSys9sYkvYYKMZ7chCxvoEXVgm74KKUcUu4V8xveCBFadFuZs8shnxBWHbcwFr5AziLr2mE7KHJT"
+ }
+}
+```
+
+
+### **make_multisig**
+
+Make a wallet multisig by importing peers multisig string.
+
+Alias: *None*.
+
+Inputs:
+
+* *multisig_info* - array of string; List of multisig string from peers.
+* *threshold* - unsigned int; Amount of signatures needed to sign a transfer. Must be less or equal than the amount of signature in `multisig_info`.
+* *password* - string; Wallet password
+
+Outputs:
+
+* *address* - string; multisig wallet address.
+* *multisig_info* - string; Multisig string to share with peers to create the multisig wallet (extra step for N-1/N wallets).
+
+Example for 2/2 Multisig Wallet:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"make_multisig","params":{"multisig_info":["MultisigV1K4tGGe8QirZdHgTYoBZMumSug97fdDyM3Z63M3ZY5VXvAdoZvx16HJzPCP4Rp2ABMKUqLD2a74ugMdBfrVpKt4BwD8qCL5aZLrsYWoHiA7JJwDESuhsC3eF8QC9UMvxLXEMsMVh16o98GnKRYz1HCKXrAEWfcrCHyz3bLW1Pdggyowop"],"threshold":2}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "address": "55SoZTKH7D39drxfgT62k8T4adVFjmDLUXnbzEKYf1MoYwnmTNKKaqGfxm4sqeKCHXQ5up7PVxrkoeRzXu83d8xYURouMod",
+ "multisig_info": ""
+ }
+}
+```
+
+Example for 2/3 Multisig Wallet:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"make_multisig","params":{"multisig_info":["MultisigV1MTVm4DZAdJw1PyVutpSy8Q4WisZBCFRAaZY7hhQnMwr5AZ4swzThyaSiVVQM5FHj1JQi3zPKhQ4k81BZkPSEaFjwRJtbfqfJcVvCqRnmBVcWVxhnihX5s8fZWBCjKrzT3CS95spG4dzNzJSUcjheAkLzCpVmSzGtgwMhAS3Vuz9Pas24","MultisigV1TEx58ycKCd6ADCfxF8hALpcdSRAkhZTi1bu4Rs6FdRC98EdB1LY7TAkMxasM55khFgcxrSXivaSr5FCMyJGHmojm1eE4HpGWPeZKv6cgCTThRzC4u6bkkSoFQdbzWN92yn1XEjuP2XQrGHk81mG2LMeyB51MWKJAVF99Pg9mX2BpmYFj"],"threshold":2}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "address": "51sLpF8fWaK1111111111111111111111111111111111ABVbHNf1JFWJyFp5YZgZRQ44RiviJi1sPHgLVMbckRsDkTRgKS",
+ "multisig_info": "MultisigxV18jCaYAQQvzCMUJaAWMCaAbAoHpAD6WPmYDmLtBtazD654E8RWkLaGRf29fJ3stU471MELKxwufNYeigP7LoE4tn2Sscwn5g7PyCfcBc1V4ffRHY3Kxqq6VocSCUTncpVeUskaDKuTAWtdB9VTBGW7iG1cd7Zm1dYgur3CiemkGjRUAj9bL3xTEuyaKGYSDhtpFZFp99HQX57EawhiRHk3qq4hjWX"
+ }
+}
+```
+
+
+### **export_multisig_info**
+
+Export multisig info for other participants.
+
+Alias: *None*.
+
+Inputs: *None*.
+
+Outputs:
+
+* *info* - string; Multisig info in hex format for other participants.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"export_multisig_info"}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "info": "4d6f6e65726f206d756c7469736967206578706f72740105cf6442b09b75f5eca9d846771fe1a879c9a97ab0553ffbcec64b1148eb7832b51e7898d7944c41cee000415c5a98f4f80dc0efdae379a98805bb6eacae743446f6f421cd03e129eb5b27d6e3b73eb6929201507c1ae706c1a9ecd26ac8601932415b0b6f49cbbfd712e47d01262c59980a8f9a8be776f2bf585f1477a6df63d6364614d941ecfdcb6e958a390eb9aa7c87f056673d73bc7c5f0ab1f74a682e902e48a3322c0413bb7f6fd67404f13fb8e313f70a0ce568c853206751a334ef490068d3c8ca0e"
+ }
+}
+```
+
+
+### **import_multisig_info**
+
+Import multisig info from other participants.
+
+Alias: *None*.
+
+Inputs:
+
+* *info* - array of string; List of multisig info in hex format from other participants.
+
+Outputs:
+
+* *n_outputs* - unsigned int; Number of outputs signed with those multisig info.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"import_multisig_info","params":{"info":["...multisig_info..."]}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "n_outputs": 35
+ }
+}
+```
+
+
+### **finalize_multisig**
+
+Turn this wallet into a multisig wallet, extra step for N-1/N wallets.
+
+Alias: *None*.
+
+Inputs:
+
+* *multisig_info* - array of string; List of multisig string from peers.
+* *password* - string; Wallet password
+
+Outputs:
+
+* *address* - string; multisig wallet address.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"finalize_multisig","params":{"multisig_info":["MultisigxV1JNC6Ja2oBt5Sqea9LN2YEF7WYZCpHqr2EKvPG89Trf3X4E8RWkLaGRf29fJ3stU471MELKxwufNYeigP7LoE4tn2McPr4SbL9q15xNvZT5uwC9YRr7UwjXqSZHmTWN9PBuZEKVAQ4HPPyQciSCdNjgwsuFRBzrskMdMUwNMgKst1debYfm37i6PSzDoS2tk4kYTYj83kkAdR7kdshet1axQPd6HQ","MultisigxV1Unma7Ko4zdd8Ps3Af4oZwtj2JdWKzwNfP6s2G9ZvXhMoSscwn5g7PyCfcBc1V4ffRHY3Kxqq6VocSCUTncpVeUskMcPr4SbL9q15xNvZT5uwC9YRr7UwjXqSZHmTWN9PBuZE1LTpWxLoC3vPMSrqVVcjnmL9LYfdCZz3fECjNZbCEDq3PHDiUuY5jurQTcNoGhDTio5WM9xaAdim9YByiS5KyqF4"]}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "address": "5B9gZUTDuHTcGGuY3nL3t8K2tDnEHeRVHSBQgLZUTQxtFYVLnho5JJjWJyFp5YZgZRQ44RiviJi1sPHgLVMbckRsDqDx1gV"
+ }
+}
+```
+
+
+### **sign_multisig**
+
+Sign a transaction in multisig.
+
+Alias: *None*.
+
+Inputs:
+
+* *tx_data_hex* - string; Multisig transaction in hex format, as returned by `transfer` under `multisig_txset`.
+
+Outputs:
+
+* *tx_data_hex* - string; Multisig transaction in hex format.
+* *tx_hash_list* - array of string; List of transaction Hash.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"sign_multisig","params":{"tx_data_hex":"...multisig_txset..."}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "tx_data_hex": "...multisig_txset...",
+ "tx_hash_list": ["4996091b61c1be112c1097fd5e97d8ff8b28f0e5e62e1137a8c831bacf034f2d"]
+ }
+}
+```
+
+
+### **submit_multisig**
+
+Submit a signed multisig transaction.
+
+Alias: *None*.
+
+Inputs:
+
+* *tx_data_hex* - string; Multisig transaction in hex format, as returned by `sign_multisig` under `tx_data_hex`.
+
+Outputs:
+
+* *tx_hash_list* - array of string; List of transaction Hash.
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"submit_multisig","params":{"tx_data_hex":"...tx_data_hex..."}}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "tx_hash_list": ["4996091b61c1be112c1097fd5e97d8ff8b28f0e5e62e1137a8c831bacf034f2d"]
+ }
+}
+```
+
+
+### **get_version**
+
+Get RPC version Major & Minor integer-format, where Major is the first 16 bits and Minor the last 16 bits.
+
+Alias: *None*.
+
+Inputs: *None*.
+
+Outputs:
+
+* *version* - unsigned int; RPC version, formatted with `Major * 2^16 + Minor` (Major encoded over the first 16 bits, and Minor over the last 16 bits).
+
+Example:
+
+```
+$ curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_version"}' -H 'Content-Type: application/json'
+{
+ "id": "0",
+ "jsonrpc": "2.0",
+ "result": {
+ "version": 65539
+ }
+}
+```
\ No newline at end of file
diff --git a/_i18n/nl/resources/moneropedia/00-base-00 b/_i18n/nl/resources/moneropedia/00-base-00
new file mode 100644
index 00000000..51195ddc
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/00-base-00
@@ -0,0 +1,8 @@
+---
+terms: ["", ""]
+summary: ""
+---
+
+### The Basics
+
+
\ No newline at end of file
diff --git a/_i18n/nl/resources/moneropedia/account.md b/_i18n/nl/resources/moneropedia/account.md
new file mode 100644
index 00000000..37268bf6
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/account.md
@@ -0,0 +1,80 @@
+---
+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's 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/nl/resources/moneropedia/address-book.md b/_i18n/nl/resources/moneropedia/address-book.md
new file mode 100644
index 00000000..39cd58db
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/address-book.md
@@ -0,0 +1,33 @@
+---
+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/nl/resources/moneropedia/address.md b/_i18n/nl/resources/moneropedia/address.md
new file mode 100644
index 00000000..d283e399
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/address.md
@@ -0,0 +1,20 @@
+---
+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 44AFFq5kSiGBoZ4NMDwYtN18obc8AemS33DBLWs3H7otXft3XjrpDtQGv7SqSsaBYBb98uNbr2VBBEt7f2wfn3RVGQBEP3A.
+
+Because those addresses are long and complex, you will often encounter an @OpenAlias address instead. For example, Monero donations can be sent to donate@getmonero.org or donate.getmonero.org.
+
+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
+
+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/nl/resources/moneropedia/airgap.md b/_i18n/nl/resources/moneropedia/airgap.md
new file mode 100644
index 00000000..9565484c
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/airgap.md
@@ -0,0 +1,10 @@
+---
+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/nl/resources/moneropedia/atomic-units.md b/_i18n/nl/resources/moneropedia/atomic-units.md
new file mode 100644
index 00000000..057b5727
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/atomic-units.md
@@ -0,0 +1,10 @@
+---
+terms: ["atomic-units", "atomic-unit"]
+summary: "Atomic Units refer to the smallest fraction of 1 XMR."
+---
+
+### The Basics
+
+Atomic Units refer to the smallest fraction of 1 XMR.
+One atomic unit is currently 1e-12 XMR (0.000000000001 XMR, or one @piconero).
+It may be changed in the future.
diff --git a/_i18n/nl/resources/moneropedia/base32-address.md b/_i18n/nl/resources/moneropedia/base32-address.md
new file mode 100644
index 00000000..9737f7c0
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/base32-address.md
@@ -0,0 +1,25 @@
+---
+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/nl/resources/moneropedia/base64-address.md b/_i18n/nl/resources/moneropedia/base64-address.md
new file mode 100644
index 00000000..56a0589a
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/base64-address.md
@@ -0,0 +1,20 @@
+---
+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/nl/resources/moneropedia/block.md b/_i18n/nl/resources/moneropedia/block.md
new file mode 100644
index 00000000..61cc6c80
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/block.md
@@ -0,0 +1,14 @@
+---
+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/nl/resources/moneropedia/blockchain.md b/_i18n/nl/resources/moneropedia/blockchain.md
new file mode 100644
index 00000000..9e97181e
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/blockchain.md
@@ -0,0 +1,10 @@
+---
+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/nl/resources/moneropedia/bootstrap-node.md b/_i18n/nl/resources/moneropedia/bootstrap-node.md
new file mode 100644
index 00000000..38291250
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/bootstrap-node.md
@@ -0,0 +1,12 @@
+---
+terms: ["bootstrap-node", "bootstrap-nodes"]
+summary: "A node to which a daemon connects to give immediate usability to wallets while syncing"
+---
+
+### The Basics
+
+The daemon running on a local @node has to sync with other (remote) @nodes. While it is not fully synced, @wallet may still be connected to the local node. Therefore, the @wallet cannot access the @blocks that are bot yet synced on the local @node.
+
+To allow the @wallet to be immediately usable, the daemon on the local @node uses a bootstrap node to which the RPC request are proxying to, giving access to the missing @blocks.
+
+Note: the replies from the bootstrap node may be untrustworthy.
diff --git a/_i18n/nl/resources/moneropedia/bulletproofs.md b/_i18n/nl/resources/moneropedia/bulletproofs.md
new file mode 100644
index 00000000..5946cd00
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/bulletproofs.md
@@ -0,0 +1,30 @@
+---
+terms: ["bulletproofs", "bulletproof"]
+summary: "a new kind of range proofs replacing RingCT in transactions to obfuscate the amounts sent"
+---
+
+### The Basics
+@RingCT was introduced to obfuscate transaction amounts. One goal of @RingCT was to prove the sum of inputs - outputs in the @transaction was equal to 0, and all outputs were positive numbers.
+To accomplish this, two kind of ring signatures were constructed: One ring signature for the whole transaction (to prove the sum is 0), and a set of ring signatures for the subsets of transaction bits (to prove the outputs are positive numbers), then combined together using originally Schnorr signatures (and later replaced by Borromean ring signature).
+While it was doing the job, a big drawback was the huge size of such a ringCT transaction.
+
+### Where it comes to bulletproofs
+Back in 2017, a [Standford applied crypto group](https://crypto.stanford.edu/bulletproofs/) wrote a [paper](https://eprint.iacr.org/2017/1066.pdf) presenting a new kind of range proofs, called bulletproofs.
+
+> Bulletproofs are short non-interactive zero-knowledge proofs that require no trusted setup.
+
+Bulletproofs, unlike Borromean or Schnorr signatures, are very efficient as range proofs. Proving a big set of data only generates a small proof, and the size of this proofs grows logarithmically with the size of the data being proved.
+It means that increasing the number of outputs in a transaction will, with bulletproofs only slightly increase the size of the proof.
+Bulletproofs also have the advantage to allow to prove that multiple committed amounts are in the desired range at once. No need to prove each output to each destination in separate proofs; the whole transaction amounts could be proven in one bigger (but still very small) bulletproof.
+
+### Thorough audit process and implementation
+As bulletproofs were really new, and the initial implementation made by the group, while thoroughly done, needed a rewrite focused on our specific use-case, implementing bulletproof in Monero was not a simple thing.
+The code has been written and rewritten to follow the new version of bulletproofs which was still being developed, but once this Monero implementation was finalized, the resulting deployment should be taken with extreme care.
+Therefore, the community started an auditing process. Researchers reached out to Benedikt Bünz, lead author of the Bulletproofs paper, and to [OSTIF](https://ostif.org/) an organization which helps open source technologies to improve and secure themselves.
+OSTIF directed the group to several organizations with the skills required to perform the audit. While one of them asked to be kept unnamed and was therefore put away from the process that needed to be public, two others (QuarksLab & Kudelski Security) were choosen to conduct the audit.
+Our 3 auditors were funded by the community to check out the if the implementation did not did not contain critical bugs, and if it did not have any exploits.
+The final reports were released during the summer of 2018, with several useful corrections and fixes suggested, and the final bulletproof implementation has been added first to Monero Stagenet, and then to the main Monero network during the October 2018 network upgrade.
+
+Since the bulletproofs deployment, the size of an average transaction has dropped by at least 80%, as well as the transaction fees.
+
+More explanations on Monero's implementation of bulletproofs could be found on youtube fondajo channel in a [conversation with Sarang Noether](https://www.youtube.com/watch?v=6lEWqIMLzUU).
diff --git a/_i18n/nl/resources/moneropedia/canonically-unique-host.md b/_i18n/nl/resources/moneropedia/canonically-unique-host.md
new file mode 100644
index 00000000..329887df
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/canonically-unique-host.md
@@ -0,0 +1,21 @@
+---
+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/Hosts_(file))
+- 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/nl/resources/moneropedia/change.md b/_i18n/nl/resources/moneropedia/change.md
new file mode 100644
index 00000000..12db7382
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/change.md
@@ -0,0 +1,14 @@
+---
+terms: ["change"]
+summary: "Monero sent as part of a transaction, that returns to your account instead of going to another recipient"
+---
+
+### The Basics
+
+Monero sent as part of a transaction, that returns to your account instead of going to another recipient.
+
+### More Information
+
+The @wallet in the Monero software makes change automatically, but when you send a transaction, you are taking an input that you control and telling the Monero network what to do with it. The input is a "deposit" to your account that you are able to spend. Outputs are the part of the transaction that tells the Monero network where to send the funds.
+
+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/nl/resources/moneropedia/clearnet.md b/_i18n/nl/resources/moneropedia/clearnet.md
new file mode 100644
index 00000000..836bbf01
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/clearnet.md
@@ -0,0 +1,31 @@
+---
+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/nl/resources/moneropedia/coinbase.md b/_i18n/nl/resources/moneropedia/coinbase.md
new file mode 100644
index 00000000..ee935871
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/coinbase.md
@@ -0,0 +1,8 @@
+---
+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
+
+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.
\ No newline at end of file
diff --git a/_i18n/nl/resources/moneropedia/consensus.md b/_i18n/nl/resources/moneropedia/consensus.md
new file mode 100644
index 00000000..a4484c63
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/consensus.md
@@ -0,0 +1,8 @@
+---
+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
+
+Consensus describes a property of distributed networks like Monero where most of the participants follow the rules, and thus reject bad participants.
\ No newline at end of file
diff --git a/_i18n/nl/resources/moneropedia/cryptocurrency.md b/_i18n/nl/resources/moneropedia/cryptocurrency.md
new file mode 100644
index 00000000..8d291380
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/cryptocurrency.md
@@ -0,0 +1,20 @@
+---
+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
+
+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.
+
+### 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 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 @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.
+
+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/nl/resources/moneropedia/data-directory.md b/_i18n/nl/resources/moneropedia/data-directory.md
new file mode 100644
index 00000000..abe307f2
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/data-directory.md
@@ -0,0 +1,20 @@
+---
+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/nl/resources/moneropedia/denominations.md b/_i18n/nl/resources/moneropedia/denominations.md
new file mode 100644
index 00000000..23475766
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/denominations.md
@@ -0,0 +1,38 @@
+---
+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 particular unit of currency.)"
+---
+
+### The Basics
+
+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.).
+
+Monero denomination names add SI prefixes after dropping the initial "mo" for ease of use. Actually, 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.
+
+### Monerod Implementation
+
+The smallest fraction of Monero in the current monerod implementation is also known as the @atomic-unit, which is currently one piconero.
diff --git a/_i18n/nl/resources/moneropedia/destination.md b/_i18n/nl/resources/moneropedia/destination.md
new file mode 100644
index 00000000..176fd37d
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/destination.md
@@ -0,0 +1,17 @@
+---
+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-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`
+
+Note: certificates are not used now but, if they were, the keys would be longer.
diff --git a/_i18n/nl/resources/moneropedia/eepsite.md b/_i18n/nl/resources/moneropedia/eepsite.md
new file mode 100644
index 00000000..efb16e1a
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/eepsite.md
@@ -0,0 +1,28 @@
+---
+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://gitlab.com/kovri-project/kovri-docs/blob/master/i18n/en/user_guide.md).
diff --git a/_i18n/nl/resources/moneropedia/encryption.md b/_i18n/nl/resources/moneropedia/encryption.md
new file mode 100644
index 00000000..0e7e0146
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/encryption.md
@@ -0,0 +1,33 @@
+---
+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/nl/resources/moneropedia/floodfill.md b/_i18n/nl/resources/moneropedia/floodfill.md
new file mode 100644
index 00000000..f2cb5f04
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/floodfill.md
@@ -0,0 +1,13 @@
+---
+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/nl/resources/moneropedia/fluffyblocks.md b/_i18n/nl/resources/moneropedia/fluffyblocks.md
new file mode 100644
index 00000000..ade4ee39
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/fluffyblocks.md
@@ -0,0 +1,17 @@
+---
+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/_i18n/nl/resources/moneropedia/fungibility.md b/_i18n/nl/resources/moneropedia/fungibility.md
new file mode 100644
index 00000000..98fa7137
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/fungibility.md
@@ -0,0 +1,15 @@
+---
+terms: ["fungibility", "fungible"]
+summary: "property of a currency whereby two units can be substituted in place of one another"
+---
+
+### The Basics
+
+Property of a currency whereby two units can be substituted in place of one another.
+
+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.
+
+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.
+
diff --git a/_i18n/nl/resources/moneropedia/garlic-encryption.md b/_i18n/nl/resources/moneropedia/garlic-encryption.md
new file mode 100644
index 00000000..271d7f0c
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/garlic-encryption.md
@@ -0,0 +1,23 @@
+---
+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/nl/resources/moneropedia/garlic-routing.md b/_i18n/nl/resources/moneropedia/garlic-routing.md
new file mode 100644
index 00000000..6e4865e3
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/garlic-routing.md
@@ -0,0 +1,43 @@
+---
+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/nl/resources/moneropedia/i2np.md b/_i18n/nl/resources/moneropedia/i2np.md
new file mode 100644
index 00000000..556f59ee
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/i2np.md
@@ -0,0 +1,26 @@
+---
+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/nl/resources/moneropedia/i2p.md b/_i18n/nl/resources/moneropedia/i2p.md
new file mode 100644
index 00000000..26ef9c46
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/i2p.md
@@ -0,0 +1,29 @@
+---
+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/nl/resources/moneropedia/i2pcontrol.md b/_i18n/nl/resources/moneropedia/i2pcontrol.md
new file mode 100644
index 00000000..5491fc4e
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/i2pcontrol.md
@@ -0,0 +1,15 @@
+---
+tags: ["kovri"]
+terms: ["I2PControl"]
+summary: "An API inteface for Kovri and Java-I2P that allows simple remote control"
+---
+
+### The Basics
+
+@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.
+
+### In-depth information
+
+Details and specification available on the [I2PControl](https://geti2p.net/en/docs/api/i2pcontrol) page.
diff --git a/_i18n/nl/resources/moneropedia/in-net.md b/_i18n/nl/resources/moneropedia/in-net.md
new file mode 100644
index 00000000..884d40f0
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/in-net.md
@@ -0,0 +1,13 @@
+---
+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/nl/resources/moneropedia/java-i2p.md b/_i18n/nl/resources/moneropedia/java-i2p.md
new file mode 100644
index 00000000..ede62818
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/java-i2p.md
@@ -0,0 +1,13 @@
+---
+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/nl/resources/moneropedia/jump-service.md b/_i18n/nl/resources/moneropedia/jump-service.md
new file mode 100644
index 00000000..60619ede
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/jump-service.md
@@ -0,0 +1,32 @@
+---
+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/nl/resources/moneropedia/kovri.md b/_i18n/nl/resources/moneropedia/kovri.md
new file mode 100644
index 00000000..e97707d5
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/kovri.md
@@ -0,0 +1,60 @@
+---
+tags: ["kovri"]
+terms: ["Kovri"]
+summary: "Monero's C++ router implementation of the I2P network"
+---
+
+### The Basics
+
+[Kovri](https://gitlab.com/kovri-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://gitlab.com/kovri-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/nl/resources/moneropedia/lease-set.md b/_i18n/nl/resources/moneropedia/lease-set.md
new file mode 100644
index 00000000..dc1c4a24
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/lease-set.md
@@ -0,0 +1,23 @@
+---
+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/nl/resources/moneropedia/lease.md b/_i18n/nl/resources/moneropedia/lease.md
new file mode 100644
index 00000000..c5a78058
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/lease.md
@@ -0,0 +1,13 @@
+---
+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/nl/resources/moneropedia/locally-unique-host.md b/_i18n/nl/resources/moneropedia/locally-unique-host.md
new file mode 100644
index 00000000..fecc2c48
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/locally-unique-host.md
@@ -0,0 +1,20 @@
+---
+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/Hosts_(file)) 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/nl/resources/moneropedia/message.md b/_i18n/nl/resources/moneropedia/message.md
new file mode 100644
index 00000000..5cce553b
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/message.md
@@ -0,0 +1,31 @@
+---
+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/nl/resources/moneropedia/mining.md b/_i18n/nl/resources/moneropedia/mining.md
new file mode 100644
index 00000000..82c1aeb8
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/mining.md
@@ -0,0 +1,14 @@
+---
+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
+
+The process of cryptographically computing a mathematical proof for a block, containing a number of transactions, which is then added to the blockchain.
+
+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 a variant of 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/_i18n/nl/resources/moneropedia/mnemonicseed.md b/_i18n/nl/resources/moneropedia/mnemonicseed.md
new file mode 100644
index 00000000..0aaecb97
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/mnemonicseed.md
@@ -0,0 +1,18 @@
+---
+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
+
+A 13 or 25 word phrase used to backup a Monero account, available in a number of languages. 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/nl/resources/moneropedia/network-database.md b/_i18n/nl/resources/moneropedia/network-database.md
new file mode 100644
index 00000000..eb3925cd
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/network-database.md
@@ -0,0 +1,23 @@
+---
+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/nl/resources/moneropedia/node.md b/_i18n/nl/resources/moneropedia/node.md
new file mode 100644
index 00000000..68029fa2
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/node.md
@@ -0,0 +1,24 @@
+---
+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
+
+A device on the Internet running the Monero software, with a full copy of the Monero blockchain, actively assisting the Monero network.
+
+### 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 to contribute to the Monero network by participating in crafting @blocks (this is called @mining).
+
+Mining is the process by which nodes create a block from the previously accepted block, transactions that are waiting to be processed in the transaction pool, and the @coinbase-transaction. When a node believes it has crafted a valid block it will transmit the completed block to other nodes on the network and those nodes signal agreement by working on the next block in the chain.
+
+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 network upgrade every 6 months, to occur in October and April 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
+1. *Fluffypony gives a great explanation of why mandatory network upgrades 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))
+
diff --git a/_i18n/nl/resources/moneropedia/ntcp.md b/_i18n/nl/resources/moneropedia/ntcp.md
new file mode 100644
index 00000000..69d10a3f
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/ntcp.md
@@ -0,0 +1,32 @@
+---
+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/nl/resources/moneropedia/openalias.md b/_i18n/nl/resources/moneropedia/openalias.md
new file mode 100644
index 00000000..b714128a
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/openalias.md
@@ -0,0 +1,18 @@
+---
+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.
+
+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.
+
+More information can be found on the [OpenAlias page](/resources/openalias) or on the [OpenAlias website](https://openalias.org)
diff --git a/_i18n/nl/resources/moneropedia/paperwallet.md b/_i18n/nl/resources/moneropedia/paperwallet.md
new file mode 100644
index 00000000..db1a35c8
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/paperwallet.md
@@ -0,0 +1,8 @@
+---
+terms: ["paperwallet", "paperwallets", "paper-wallet", "paper-wallets"]
+summary: "A paper wallet stores the information necessary to send and receive Monero"
+---
+
+### The Basics
+
+A paper wallet stores the information necessary to send and receive Monero.
diff --git a/_i18n/nl/resources/moneropedia/paymentid.md b/_i18n/nl/resources/moneropedia/paymentid.md
new file mode 100644
index 00000000..3e220e68
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/paymentid.md
@@ -0,0 +1,25 @@
+---
+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 IDs and Integrated Addresses
+
+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 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/_i18n/nl/resources/moneropedia/pedersen-commitment.md b/_i18n/nl/resources/moneropedia/pedersen-commitment.md
new file mode 100644
index 00000000..0f4e255a
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/pedersen-commitment.md
@@ -0,0 +1,22 @@
+---
+terms: ["commitments", "commitment", "pedersen", "pedersen-commitment", "pedersen-commitments"]
+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
+
+Pedersen commitments are cryptographic algorythms that allow a prover to commit to a certain value without revealing it or being able to change it.
+
+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.
+
+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.
diff --git a/_i18n/nl/resources/moneropedia/reseed.md b/_i18n/nl/resources/moneropedia/reseed.md
new file mode 100644
index 00000000..59727311
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/reseed.md
@@ -0,0 +1,15 @@
+---
+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/nl/resources/moneropedia/ring-size.md b/_i18n/nl/resources/moneropedia/ring-size.md
new file mode 100644
index 00000000..4ad33ddd
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/ring-size.md
@@ -0,0 +1,9 @@
+---
+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/nl/resources/moneropedia/ringCT.md b/_i18n/nl/resources/moneropedia/ringCT.md
new file mode 100644
index 00000000..3ebaae17
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/ringCT.md
@@ -0,0 +1,13 @@
+---
+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).
diff --git a/_i18n/nl/resources/moneropedia/ringsignatures.md b/_i18n/nl/resources/moneropedia/ringsignatures.md
new file mode 100644
index 00000000..b5db207f
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/ringsignatures.md
@@ -0,0 +1,16 @@
+---
+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/nl/resources/moneropedia/router-info.md b/_i18n/nl/resources/moneropedia/router-info.md
new file mode 100644
index 00000000..ad50c13f
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/router-info.md
@@ -0,0 +1,66 @@
+---
+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/nl/resources/moneropedia/scalability.md b/_i18n/nl/resources/moneropedia/scalability.md
new file mode 100644
index 00000000..97a9536a
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/scalability.md
@@ -0,0 +1,8 @@
+---
+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/nl/resources/moneropedia/signature.md b/_i18n/nl/resources/moneropedia/signature.md
new file mode 100644
index 00000000..7ad1e27d
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/signature.md
@@ -0,0 +1,8 @@
+---
+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
+
+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.
\ No newline at end of file
diff --git a/_i18n/nl/resources/moneropedia/smartmining.md b/_i18n/nl/resources/moneropedia/smartmining.md
new file mode 100644
index 00000000..0a1aa8ee
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/smartmining.md
@@ -0,0 +1,13 @@
+---
+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.
diff --git a/_i18n/nl/resources/moneropedia/spendkey.md b/_i18n/nl/resources/moneropedia/spendkey.md
new file mode 100644
index 00000000..893328c5
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/spendkey.md
@@ -0,0 +1,14 @@
+---
+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
+
+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.
+
+### 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/nl/resources/moneropedia/ssu.md b/_i18n/nl/resources/moneropedia/ssu.md
new file mode 100644
index 00000000..a7b2eb5b
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/ssu.md
@@ -0,0 +1,24 @@
+---
+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/nl/resources/moneropedia/stealthaddress.md b/_i18n/nl/resources/moneropedia/stealthaddress.md
new file mode 100644
index 00000000..46d908be
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/stealthaddress.md
@@ -0,0 +1,14 @@
+---
+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/nl/resources/moneropedia/subscription.md b/_i18n/nl/resources/moneropedia/subscription.md
new file mode 100644
index 00000000..78ef1bf4
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/subscription.md
@@ -0,0 +1,45 @@
+---
+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/Hosts_(file)) 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://gitlab.com/kovri-project/kovri-docs/blob/master/i18n/en/user_guide.md).
diff --git a/_i18n/nl/resources/moneropedia/tail-emission.md b/_i18n/nl/resources/moneropedia/tail-emission.md
new file mode 100644
index 00000000..ade85309
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/tail-emission.md
@@ -0,0 +1,14 @@
+---
+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/nl/resources/moneropedia/transaction.md b/_i18n/nl/resources/moneropedia/transaction.md
new file mode 100644
index 00000000..95c68703
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/transaction.md
@@ -0,0 +1,21 @@
+---
+terms: ["transaction", "transactions"]
+summary: "a cryptographically signed container that details the transfer of Monero to a recipient (or recipients)"
+---
+
+### The Basics
+
+A cryptographically signed container that details the transfer of Monero to a recipient (or recipients).
+
+The parameters of a transaction contain one or more recipient addresses with corresponding amounts of funds and a @ring-size parameter that specifies the number 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 will be higher.
+
+It is possible to form a transaction 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).
+
+### 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/nl/resources/moneropedia/transports.md b/_i18n/nl/resources/moneropedia/transports.md
new file mode 100644
index 00000000..01225e66
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/transports.md
@@ -0,0 +1,18 @@
+---
+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/nl/resources/moneropedia/tunnel.md b/_i18n/nl/resources/moneropedia/tunnel.md
new file mode 100644
index 00000000..94369ad2
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/tunnel.md
@@ -0,0 +1,35 @@
+---
+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/nl/resources/moneropedia/unlocktime.md b/_i18n/nl/resources/moneropedia/unlocktime.md
new file mode 100644
index 00000000..335a946b
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/unlocktime.md
@@ -0,0 +1,12 @@
+---
+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
+
+A special transaction where the recipient can only spend the funds after a future date, as set by the sender.
+
+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/nl/resources/moneropedia/viewkey.md b/_i18n/nl/resources/moneropedia/viewkey.md
new file mode 100644
index 00000000..469fc02a
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/viewkey.md
@@ -0,0 +1,12 @@
+---
+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
+
+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.
+
+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.
diff --git a/_i18n/nl/resources/moneropedia/wallet.md b/_i18n/nl/resources/moneropedia/wallet.md
new file mode 100644
index 00000000..078033d4
--- /dev/null
+++ b/_i18n/nl/resources/moneropedia/wallet.md
@@ -0,0 +1,17 @@
+---
+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 (Ledger available since June 2018).
+
diff --git a/_i18n/nl/resources/technical-specs.md b/_i18n/nl/resources/technical-specs.md
new file mode 100644
index 00000000..4e379f27
--- /dev/null
+++ b/_i18n/nl/resources/technical-specs.md
@@ -0,0 +1,132 @@
+
+
+
+
+
+
+
+
+
+
Geen premine, geen instamine, geen token
+
+
+
+
+* Er is geen premine of instamine van Monero geweest
+* Monero heeft nooit een token verkocht
+* Er is geen enkele presale of voorverkoop van Monero geweest
+
+
+
+
+
+* CryptoNight
+* Kan in de toekomst veranderen
+
+
+
+
+
Herberekening moeilijkheidsgraad
+
+
+
+
+* Ieder blok
+* Gebaseerd op de laatste 720 blokken, maar zonder de 20% kortste en langste tijden
+
+
+
+
+
+* 2 minuten
+* Kan in de toekomst veranderen, maar de uitgiftecurve verandert niet
+
+
+
+
+
Beloning per blok
+
+
+
+
+* Neemt gelijkmatig af, met een malus voor blokken die groter zijn dan de mediaan van de laatste 100 blokken (M100)
+Zie de coinbase-transactie in het [laatste blok](https://moneroblocks.info/) voor de huidige beloning
+
+
+
+
+
+* Dynamisch, maximaal 2 * M100
+
+
+
+
+
+* Eerst de gewone curve: ~18.132 miljoen coins eind mei 2022
+* Daarna de blijvende uitgifte: 0,6 XMR per blok om de 2 minuten, nadat de gewone uitgifte klaar is, wat een steeds verder dalende inflatie van < 1% oplevert
+* Zie [grafieken en details](https://www.reddit.com/r/Monero/comments/512kwh/useful_for_learning_about_monero_coin_emission/)
+
+
+
+
+
Maximale geldhoeveelheid
+
+
+
+
+* Oneindig
+
+
+
+
+
+* Ring-handtekeningen
+
+
+
+
+
Privacy ontvanger
+
+
+
+
+* Stealth addresses
+
+
+
+
+
Verborgen bedragen
+
+
+
+
+* Vertrouwelijke ring-transacties
+
+
+
+
+
+
+
+
+
diff --git a/_i18n/nl/resources/user-guides/How-to-mine-Monero-XMR-without-a-mining-equipment.md b/_i18n/nl/resources/user-guides/How-to-mine-Monero-XMR-without-a-mining-equipment.md
new file mode 100644
index 00000000..0918d01c
--- /dev/null
+++ b/_i18n/nl/resources/user-guides/How-to-mine-Monero-XMR-without-a-mining-equipment.md
@@ -0,0 +1,50 @@
+{% assign version = '1.1.0' | split: '.' %}
+{% include disclaimer.html translated="true" version=page.version %}
+## Monero (XMR) minen zonder miningapparatuur
+
+Als je geen rendabele apparatuur om te minen hebt, en geen tijd of
+geen geld om te besteden aan het bouwen ervan, kun je toch Monero minen via NiceHash.
+
+NiceHash is een marktplaats voor hashpower. Verkopers van hashpower,
+miners dus, leveren hashpower aan kopers (die het minen van
+een bepaalde munt willen aanschaffen als een dienst). NiceHash kan je dus in korte tijd
+een enorme hoeveelheid hashpower leveren. Je hoeft niet jaren af te wachten
+of je winst maakt of niet, en je kunt bepalen hoe lang je welke munt
+bij welke pool wilt minen.
+
+### **Stap 1.** Maak een account bij NiceHash aan
+
+Ga naar de
+[registratiepagina](https://www.nicehash.com/?p=register) en registreer je met je e-mailadres.
+
+### **Stap 2.** Stort een bedrag in Bitcoin op je account
+
+Je gaat Monero minen, maar je kunt hashpower bij
+NiceHash alleen met Bitcoins aanschaffen. Bitcoins die je niet uitgeeft kun je later weer
+overboeken naar een Bitcoin-portemonnee.
+
+Ga naar je
+[portemonneepagina](https://www.nicehash.com/?p=wallet) en stort een bedrag. Het minimumbedrag voor het plaatsen van een order
+is 0,01 BTC.
+
+### **Stap 3.** Zoek een geschikte mining pool en voeg die toe aan je lijst met pools
+
+Het selecteren van een pool speelt heeft een grote invloed op hoeveel
+van een cryptovaluta je uiteindelijk kunt minen. Zorg dat de pool die je hebt geselecteerd een hoge hashrate
+en veel shares kan verwerken, met name via n verbinding.
+[Hier](https://bitcointalk.org/index.php?topic=583449.0) vind je een lijst met Monero-pools.
+
+Waarschijnlijk moet je bij de pool die je kiest ook een account
+registreren. De pool geeft je alle gegevens die je nodig hebt.
+Je kunt je favoriete pools op [deze pagina](https://www.nicehash.com/?p=managepools) opslaan.
+
+### **Stap 4.** Geef een nieuwe order op en begin te minen
+
+Let bij het opgeven van een [nieuwe order](https://www.nicehash.com/?p=orders&new) op dat je
+het algoritme CryptoNightV8 voor het minen van Monero selecteert. (De nieuwe variant van het algoritme sinds 18 oktober 2018.) Als je eerst meer wilt weten over
+hoe je een order opgeeft bij NiceHash, raden we je aan [het antwoord op deze vraag](https://www.nicehash.com/?p=faq#faqb0) te lezen.
+
+Als je wilt bieden op
+hashpower, selecteer je het ordertype *Standard (bidding)*, en als je een vaste
+order wilt geven waar anderen niet overheen kunnen bieden, selecteer je het ordertype *Fixed order*. De status van de marktplaats
+en een schatting van de prijzen van het minen kun je controleren op de [live marktplaats](https://www.nicehash.com/index.jsp?p=orders).
diff --git a/_i18n/nl/resources/user-guides/Offline_Backup.md b/_i18n/nl/resources/user-guides/Offline_Backup.md
new file mode 100644
index 00000000..3b02079e
--- /dev/null
+++ b/_i18n/nl/resources/user-guides/Offline_Backup.md
@@ -0,0 +1,38 @@
+{% assign version = '1.1.0' | split: '.' %}
+{% include disclaimer.html translated="true" version=page.version %}
+## Besturingssystemen: diverse Linux-versies en Windows 7/8
+
+### Portemonneesoftware Simplewallet
+
+### Tool voor het maken van opstartbare schijven: [Linux](http://www.pendrivelinux.com/), [Windows](https://www.microsoft.com/en-us/download/windows-usb-dvd-download-tool)
+
+### Monero-binaries downloaden: [Binaire bestanden voor Monero](https://getmonero.org/downloads/)
+
+- Gebruik een willekeurige computer, desnoods de computer waar je normaal op werkt. Als je extra voorzichtig bent, is het handig om een oudere computer te gebruiken zonder wifi of bluetooth.
+
+- Maak een opstartbare schijf voor Linux of Windows, en zet de Monero-binaries op dezelfde schijf of een tweede schrijf. (Maak voor Linux ook kopien van de gedownloade afhankelijkheden die je nodig hebt, bijvoorbeeld libboost1.55 en miniupnpc.)
+
+- Maak de netwerk-/internetkabels los van de computer, haal de wifi-kaart eruit of schakel de wifi en bluetooth uit op een laptop, voor zover dat mogelijk is.
+
+- Start op met het besturingssysteem op de schijf en installeer eventueel de afhankelijkheden.
+
+- Kopieer de Monero-binaries naar een RAM-schijf (/dev/shm in Linux, in Windows meestal een station Z: of zoiets op een opstartbare ISO).
+
+- Voer de Monero-daemon niet uit. Gebruik in plaats daarvan monero-wallet-cli in een opdrachtregelvenster om een nieuw Monero-@account aan te maken.
+
+- Geef een naam uit wanneer daarom gevraagd wordt. Het maakt niet uit wat voor naam.
+
+- Typ 50 tot 100 willekeurige tekens wanneer om een wachtwoord wordt gevraagd. Maak je geen zorgen, je hoeft het wachtwoord niet te onthouden, als het maar LANG is.
+
+- **ONMISBARE STAP**: Schrijf je hersteltekst (@mnemonic-seed) van 25 woorden op (op papier).
+**LET OP**: Als je vergeet deze gegevens op te schrijven, kun je je geld voor altijd kwijtraken.
+
+- Noteer je adres en je alleen-lezen sleutel (op je telefoon, op papier, op een andere computer, of waar je maar wilt).
+
+- Schakel de computer uit, haal de accu eruit als die erin zit, en laat de computer een paar uur zonder stroom uit staan.
+
+Je nieuwe account is in RAM gemaakt en de digitale bestanden zijn nu verdwenen. Zelfs een aanvaller die op een of andere manier deze gegevens zou krijgen, zou het lange wachtwoord missen om de portemonnee te openen. Voor het ontvangen van betalingen heb je je openbare adres, en je alleen-lezen sleutel om ze te bekijken. Voor toegang tot je portemonnee heb je je hersteltekst (@mnemonic-seed) van 25 woorden. Je kunt nu meerdere exemplaren hiervan opschrijven, waaronder een om elders te bewaren (bijvoorbeeld in een bankkluis).
+
+Geschreven door: Riccardo Spagni
+
+Gerelateerd: [Offline account-generator](http://moneroaddress.org/)
diff --git a/_i18n/nl/resources/user-guides/cli_wallet_daemon_isolation_qubes_whonix.md b/_i18n/nl/resources/user-guides/cli_wallet_daemon_isolation_qubes_whonix.md
new file mode 100644
index 00000000..d19d3f9a
--- /dev/null
+++ b/_i18n/nl/resources/user-guides/cli_wallet_daemon_isolation_qubes_whonix.md
@@ -0,0 +1,151 @@
+{% assign version = '1.1.0' | split: '.' %}
+{% include disclaimer.html translated="true" version=page.version %}
+# Portemonnee isoleren van node met Qubes en Whonix
+
+Met [Qubes](https://qubes-os.org) en [Whonix](https://whonix.org) kun je een Monero-portemonnee zonder netwerkverbinding uitvoeren op een virtueel systeem, gesoleerd van de Monero-node, waarvan al het verkeer verplicht via [Tor](https://torproject.org) loopt.
+
+Qubes biedt de flexibiliteit om eenvoudig afzonderlijke virtual machines voor verschillende doeleinden te maken. Eerst maak je een Whonix-werkstation voor de portemonnee, zonder netwerkverbinding. Vervolgens maak je een ander Whonix-werkstation dat je Whonix-gateway gebruikt als NetVM. Voor communicatie tussen de portemonnee en de node kun je gebruik maken van Qubes [qrexec](https://www.qubes-os.org/doc/qrexec3/).
+
+Dit is veiliger dan andere benaderingen, waarbij de RPC van de portemonnee via een verborgen Tor-service wordt geleid, of fysieke isolatie wordt gebruikt, maar er nog steeds een netwerkverbinding nodig is voor communicatie met de node. Met deze methode is er helemaal geen netwerkverbinding nodig voor de portemonnee, ga je zuiniger om met het Tor-netwerk en is er minder vertraging.
+
+
+## 1. [Maak Whonix AppVM's](https://www.whonix.org/wiki/Qubes/Install):
+
++ Met een sjabloon voor Whonix-werkstations maak je op de volgende manier twee werkstations:
+
+ - Het eerste werkstation wordt gebruikt voor je portemonnee. We noemen het `monero-wallet-ws`. Hier stel je `NetVM` in op `none`.
+
+ - Het tweede werkstation wordt gebruikt voor `monerod`, de daemon voor de node. We noemen het `monerod-ws`. Hier stel je `NetVM` in op de Whonix-gateway `sys-whonix`.
+
+## 2. In de AppVM `monerod-ws`:
+
++ Download, verifieer en installeer de 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 " [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/
+```
++ Maak een `systemd`-bestand.
+
+```
+user@host:~$ sudo gedit /home/user/monerod.service
+```
+
+Plak de volgende gegevens:
+
+```
+[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
+```
+
++ Kopieer het uitvoerbare bestand `monero-wallet-cli` naar de VM `monero-wallet-ws`.
+
+```
+user@host:~$ qvm-copy-to-vm monero-wallet-ws monero-v0.11.1.0/monero-wallet-cli
+```
+
++ Zorg dat de daemon `monerod` wordt uitgevoerd bij het opstarten door het bestand `/rw/config/rc.local` te bewerken.
+
+```
+user@host:~$ sudo gedit /rw/config/rc.local
+```
+
+Voeg onderaan deze regels toe:
+
+```
+cp /home/user/monerod.service /lib/systemd/system/
+systemctl start monerod.service
+```
+
+Maak het bestand uitvoerbaar.
+
+```
+user@host:~$ sudo chmod +x /rw/config/rc.local
+```
+
++ Maak het RPC-actiebestand.
+
+```
+user@host:~$ sudo mkdir /rw/usrlocal/etc/qubes-rpc
+user@host:~$ sudo gedit /rw/usrlocal/etc/qubes-rpc/user.monerod
+```
+
+Voeg deze regel toe:
+
+```
+socat STDIO TCP:localhost:18081
+```
+
++ Sluit `monerod-ws` af.
+
+## 3. In de AppVM `monero-wallet-ws`:
+
++ Verplaats het uitvoerbare bestand `monero-wallet-cli`.
+
+```
+user@host:~$ sudo mv QubesIncoming/monerod-ws/monero-wallet-cli /usr/local/bin/
+```
+
++ Bewerk het bestand `/rw/config/rc.local`.
+
+```
+user@host:~$ sudo gedit /rw/config/rc.local
+```
+
+Voeg onderaan deze regel toe:
+
+```
+socat TCP-LISTEN:18081,fork,bind=127.0.0.1 EXEC:"qrexec-client-vm monerod-ws user.monerod"
+```
+
+Maak het bestand uitvoerbaar.
+
+```
+user@host:~$ sudo chmod +x /rw/config/rc.local
+```
+
++ Sluit `monero-wallet-ws` af.
+
+## 4. In `dom0`:
+
++ Maak het bestand `/etc/qubes-rpc/policy/user.monerod`:
+
+```
+[user@dom0 ~]$ sudo nano /etc/qubes-rpc/policy/user.monerod
+```
+
+Voeg deze regel toe:
+
+```
+monero-wallet-ws monerod-ws allow
+```
diff --git a/_i18n/nl/resources/user-guides/create_wallet.md b/_i18n/nl/resources/user-guides/create_wallet.md
new file mode 100644
index 00000000..fa54dfab
--- /dev/null
+++ b/_i18n/nl/resources/user-guides/create_wallet.md
@@ -0,0 +1,62 @@
+{% assign version = '1.1.0' | split: '.' %}
+{% include disclaimer.html translated="true" version=page.version %}
+### Besturingssystemen: Ubuntu
+
+- Download de [officile binaries](https://getmonero.org/downloads/) of compileer de nieuwste broncode die beschikbaar is op [Github](https://github.com/monero-project/bitmonero).
+
+![image1](https://github.com/luuul/monero-site/blob/master/knowledge-base/user-guides/png/create_wallet/1.png)
+![image2](https://github.com/luuul/monero-site/blob/master/knowledge-base/user-guides/png/create_wallet/2.png)
+
+- Pak de bestanden uit met Archiefbeheer (hetzelfde als Winzip in Windows). Noteer het pad waar de bestanden "monerod" en "monero-wallet-cli" staan.
+
+![image3](https://github.com/luuul/monero-site/blob/master/knowledge-base/user-guides/png/create_wallet/3.png)
+![image4](https://github.com/luuul/monero-site/blob/master/knowledge-base/user-guides/png/create_wallet/4.png)
+
+Deze stap hoef je maar n keer uit te voeren. Open een terminal (Ctrl+Alt+T) en installeer de vereiste afhankelijkheden door het volgende te typen: "*sudo apt-get install libboost-all-dev libssl-dev libevent-dev libdb++-dev*". Druk wanneer erom gevraagd wordt op de toets Y en vervolgens op Enter om door te gaan.
+
+![image5](https://github.com/luuul/monero-site/blob/master/knowledge-base/user-guides/png/create_wallet/5.png)
+![image6](https://github.com/luuul/monero-site/blob/master/knowledge-base/user-guides/png/create_wallet/6.png)
+
+- Open een terminal en laad het pad waar de binaries zijn uitgepakt (zie stap 2) door het volgende te typen: "*cd jePadUitStap2*"
+
+![image7](https://github.com/luuul/monero-site/blob/master/knowledge-base/user-guides/png/create_wallet/7.png)
+
+- Laad monerod door dit in je terminal te typen: "*./monerod*". Wacht totdat monerod is gesynchroniseerd met het netwerk. (De blockchain die je bij stap 4 hebt gedownload wordt bijgewerkt, of de blockchain wordt vanaf het begin gedownload.) De eerste keer kan dit lang duren. Even geduld alsjeblieft.
+
+![image8](https://github.com/luuul/monero-site/blob/master/knowledge-base/user-guides/png/create_wallet/8.png)
+![image9](https://github.com/luuul/monero-site/blob/master/knowledge-base/user-guides/png/create_wallet/9.png)
+![image10](https://github.com/luuul/monero-site/blob/master/knowledge-base/user-guides/png/create_wallet/10.png)
+![image11](https://github.com/luuul/monero-site/blob/master/knowledge-base/user-guides/png/create_wallet/11.png)
+
+- Wanneer monerod is gesynchroniseerd met het netwerk, open je een nieuwe terminal, wijzig je de directory (zie stap 5) en start je monero-wallet-cli door "*./monero-wallet-cli*" te typen.
+
+![image12](https://github.com/luuul/monero-site/blob/master/knowledge-base/user-guides/png/create_wallet/12.png)
+
+- Voer een naam in voor je portemonnee en volg de instructies in de terminal.
+
+![image13](https://github.com/luuul/monero-site/blob/master/knowledge-base/user-guides/png/create_wallet/13.png)
+![image14](https://github.com/luuul/monero-site/blob/master/knowledge-base/user-guides/png/create_wallet/14.png)
+![image15](https://github.com/luuul/monero-site/blob/master/knowledge-base/user-guides/png/create_wallet/15.png)
+![image16](https://github.com/luuul/monero-site/blob/master/knowledge-base/user-guides/png/create_wallet/16.png)
+
+*Dit is je privsleutel. Schrijf deze sleutel op en bewaar deze op een veilige plek!*
+
+![image17](https://github.com/luuul/monero-site/blob/master/knowledge-base/user-guides/png/create_wallet/17.png)
+
+*Dit is je alleen-lezen sleutel. Deze heb je nodig om een alleen-lezen portemonnee te maken (zie de gebruikershandleiding daarover)*
+
+![image18](https://github.com/luuul/monero-site/blob/master/knowledge-base/user-guides/png/create_wallet/18.png)
+
+*Dit is het adres van je portemonnee.*
+
+![image19](https://github.com/luuul/monero-site/blob/master/knowledge-base/user-guides/png/create_wallet/19.png)
+![image20](https://github.com/luuul/monero-site/blob/master/knowledge-base/user-guides/png/create_wallet/20.png)
+![image21](https://github.com/luuul/monero-site/blob/master/knowledge-base/user-guides/png/create_wallet/21.png)
+![image22](https://github.com/luuul/monero-site/blob/master/knowledge-base/user-guides/png/create_wallet/22.png)
+![image23](https://github.com/luuul/monero-site/blob/master/knowledge-base/user-guides/png/create_wallet/23.png)
+
+Typ "*exit*" in de gebruikte terminal om monerod of monero-wallet-cli af te sluiten.
+
+Je kunt de portemonnee die je net hebt gemaakt als volgt openen: start monerod, wacht totdat de node is gesynchroniseerd met het netwerk, en typ de naam van je portemonnee en je wachtwoord.
+
+
diff --git a/_i18n/nl/resources/user-guides/easiest_buy.md b/_i18n/nl/resources/user-guides/easiest_buy.md
new file mode 100644
index 00000000..c9496d0d
--- /dev/null
+++ b/_i18n/nl/resources/user-guides/easiest_buy.md
@@ -0,0 +1,66 @@
+{% assign version = '1.1.0' | split: '.' %}
+{% include disclaimer.html translated="true" version=page.version %}
+## Hoe koop je Monero?
+
+Dit is een handleiding voor het aanschaffen van je eigen Monero, geschreven op 19 september 2015. Dit is wellicht de eenvoudigste methode om Monero aan te schaffen en te bewaren.
+
+#### Stap 1. Koop Bitcoin
+
+Je kunt op allerlei manieren Bitcoin kopen. De makkelijkste manier is wellicht via circle.com. Nadat je Bitcoin hebt gekocht, kun je Monero gaan kopen. Bitcoin kopen is niet moeilijk. Ga gewoon naar circle.com en volg de instructies daar.
+
+#### Stap 2. Open een account by mymonero.com
+
+MyMonero.com is een online portemonnee voor Monero, beheerd door Monero Core-ontwikkelaar Ricardo Spagni (fluffypony). Het is de gemakkelijkste portemonnee om te gebruiken. Ga gewoon naar MyMonero.com en klik op de knop "Create an Account".
+
+![image1](https://github.com/luuul/monero-site/blob/master/knowledge-base/user-guides/png/easiest_way/01.png)
+
+Nadat je op de knop klikt, wordt je privsleutel weergegeven. Deze sleutel geeft je toegang tot je geld. Geef deze sleutel nooit aan iemand anders!
+
+### SCHRIJF DEZE SLEUTEL METEEN OP!
+
+![image2](https://github.com/luuul/monero-site/blob/master/knowledge-base/user-guides/png/easiest_way/02.png)
+
+Typ je privsleutel in het onderstaand vak en klik op de knop.
+
+Op de volgende pagina wordt je adres weergegeven.
+
+![image3](https://github.com/luuul/monero-site/blob/master/knowledge-base/user-guides/png/easiest_way/03.png)
+
+Kopieer je adres naar het klembord door het te selecteren en op Ctrl+C te drukken (of menu Bewerken en Kopiren) of door op het kleine pictogram naast je adres te klikken. Sla je adres ergens op. Hiermee kunnen anderen Monero naar je verzenden en kun je Monero in je eigen account storten.
+
+#### Stap 3. Koop Monero en boek het over naar je nieuwe adres.
+
+Ga naar www.shapeshift.io. Klik aan de rechterkant van het scherm op het pictogram onder "Doel" om Monero te selecteren.
+
+![image5](https://github.com/luuul/monero-site/blob/master/knowledge-base/user-guides/png/easiest_way/05.png)
+![image6](https://github.com/luuul/monero-site/blob/master/knowledge-base/user-guides/png/easiest_way/06.png)
+
+Plak je adres in het veld onder het Monero-logo. Schakel het selectievakje "Ik ga akkoord met de voorwaarden" in en klik op "Transactie starten".
+
+![image7](https://github.com/luuul/monero-site/blob/master/knowledge-base/user-guides/png/easiest_way/07.png)
+
+In het nieuwe scherm dat wordt weergegeven kopieer je het stortingsadres.
+
+![image8](https://github.com/luuul/monero-site/blob/master/knowledge-base/user-guides/png/easiest_way/08.png)
+
+Ga terug naar de pagina op circle.com, klik op de knop "Transfer" en plak het Bitcoin-adres in dit veld.
+Voer in hoeveel Bitcoin je wilt besteden.
+
+![image4](https://github.com/luuul/monero-site/blob/master/knowledge-base/user-guides/png/easiest_way/04.png)
+![image9](https://github.com/luuul/monero-site/blob/master/knowledge-base/user-guides/png/easiest_way/09.png)
+
+Je ontvangt een verificatiecode in een SMS-bericht. Voer de code in en klik op Send.
+
+![image10](https://github.com/luuul/monero-site/blob/master/knowledge-base/user-guides/png/easiest_way/10.png)
+
+Je zult zien dat de status van Shapeshift verandert in "In afwachting van omwisseling".
+
+![image11](https://github.com/luuul/monero-site/blob/master/knowledge-base/user-guides/png/easiest_way/11.png)
+
+Daarna verandert het in "VOLTOOID!"
+
+![image12](https://github.com/luuul/monero-site/blob/master/knowledge-base/user-guides/png/easiest_way/12.png)
+
+Een tijdje later zul je de betaling in je Monero-account zien.
+
+![image13](https://github.com/luuul/monero-site/blob/master/knowledge-base/user-guides/png/easiest_way/13.png)
diff --git a/_i18n/nl/resources/user-guides/howto_fix_stuck_funds.md b/_i18n/nl/resources/user-guides/howto_fix_stuck_funds.md
new file mode 100644
index 00000000..83315639
--- /dev/null
+++ b/_i18n/nl/resources/user-guides/howto_fix_stuck_funds.md
@@ -0,0 +1,32 @@
+{% assign version = '1.1.0' | split: '.' %}
+{% include disclaimer.html translated="true" version=page.version %}
+Het kan gebeuren dat je geld vast komt te zitten. Je Monero wordt vergrendeld maar nooit ontgrendeld. Dat kun je op de volgende manier oplossen.
+
+- Laad je portemonnee in monero-wallet-cli.
+
+- Typ
+
+> seed
+
+op de opdrachtregel. Schrijf je hersteltekst van 25 woorden op, als je dat nog niet eerder hebt gedaan. Dit is de beste manier om ervoor te zorgen dat je over je geld kunt blijven beschikken.
+
+- Typ het volgende om monero-wallet-cli af te sluiten:
+
+> exit
+
+- Maak een back-up van alle bestanden die bij je portemonnee horen. Dit zijn:
+
+> portemonnee.bin
+> portemonnee.bin.keys
+> portemonnee.bin.address.txt
+
+Dit kun je doen door de bestanden naar een nieuwe map te kopiren.
+
+Het is mogelijk dat je je portemonnee een naam hebt gegeven zonder de toevoeging .bin. In dat geval heet het portemonneebestand portemonnee zonder .bin erachter.
+
+- Verwijder portemonnee.bin
+
+- Laad monero-wallet-cli en typ daarbij de naam in van de portemonnee die je net hebt verwijderd.
+
+- Voer je wachtwoord in. De portemonnee wordt nu vernieuwd. Hopelijk wordt je vergrendelde geld daardoor ontgrendeld.
+
diff --git a/_i18n/nl/resources/user-guides/importing_blockchain.md b/_i18n/nl/resources/user-guides/importing_blockchain.md
new file mode 100644
index 00000000..0122e43c
--- /dev/null
+++ b/_i18n/nl/resources/user-guides/importing_blockchain.md
@@ -0,0 +1,58 @@
+{% assign version = '1.1.0' | split: '.' %}
+{% include disclaimer.html translated="true" version=page.version %}
+# De blockchain importeren in de grafische Monero-portemonnee (Windows)
+
+### Stap 1
+
+Download het huidige bootstrap-bestand van https://downloads.getmonero.org/blockchain.raw. Deze stap kun je overslaan als je de blockchain uit een andere bron importeert.
+
+### Stap 2
+
+Zoek het pad van je Monero-portemonnee op (de map waar je de Monero-software hebt uitgepakt). Mijn pad is bijvoorbeeld:
+
+`D:\monero-gui-0.10.3.1`
+
+Je kunt een ander pad hebben, afhankelijk van waar je de portemonnee hebt gedownload en welke versie van de Monero-portemonnee je gebruikt.
+
+### Stap 3
+
+Zoek het pad op van de blockchain die je hebt gedownload. Voor mij is het bijvoorbeeld:
+
+`C:\Users\KeeJef\Downloads\blockchain.raw`
+
+Voor jou kan het anders zijn, afhankelijk van waar je de blockchain hebt gedownload.
+
+### Stap 4
+
+Open een opdrachtregelvenster. Dit kun je doen door op de Windows-toets + R te drukken en vervolgens in het pop-upvenster `CMD` te typen.
+
+### Stap 5
+
+Nu moet je in het CMD-venster naar het pad van je Monero-portemonnee navigeren. Dit kun je doen door het volgende te typen:
+
+`cd C:\HIER\HET\BESTANDSPAD\VAN\JE\MONERO-PORTEMONNEE`
+
+Bijvoorbeeld zoiets:
+
+`cd D:\monero-gui-0.10.3.1`
+
+Als je Monero-portemonnee op een ander station staat, gebruik je `Stationsletter:`. Bijvoorbeeld: als je portemonnee op station D staat, voer je `D:` in voordat je de `cd`-opdracht gebruikt.
+
+### Stap 6
+
+Typ nu het volgende in het opdrachtregelvenster:
+
+`monero-blockchain-import --input-file C:\HIER\HET\BESTANDSPAD\VAN\JE\BLOCKCHAIN`
+
+Ik zou bijvoorbeeld het volgende typen:
+
+`monero-blockchain-import --input-file C:\Users\KeeJef\Downloads\blockchain.raw`
+
+Als je de blockchain hebt gedownload van een bron die je vertrouwt, kun je de instelling `verify 0` opgeven. Hiermee wordt de blockchain sneller gesynchroniseerd.
+
+### Stap 7
+
+Nadat de blockchain is gesynchroniseerd, kun je je Monero-portemonnee op de normale manier openen. Het gedownloade bestand blockchain.raw kun je verwijderen.
+
+
+Geschreven door: Kee Jefferys.
diff --git a/_i18n/nl/resources/user-guides/ledger-wallet-cli.md b/_i18n/nl/resources/user-guides/ledger-wallet-cli.md
new file mode 100644
index 00000000..22b69e03
--- /dev/null
+++ b/_i18n/nl/resources/user-guides/ledger-wallet-cli.md
@@ -0,0 +1,165 @@
+{% assign version = '1.1.0' | split: '.' %}
+{% include disclaimer.html translated="true" version=page.version %}
+## Een Monero-portemonnee op een Ledger maken met de opdrachtregel (monero-wallet-cli)
+
+## Inhoud
+
+* [1. Windows](#1-windows)
+* [2. MacOS](#2-macos)
+* [3. Linux](#3-linux)
+* [4. Ten slotte](#4-ten-slotte)
+
+### 1. Windows
+
+Eerst moeten we ons voldoende voorbereiden. Daar is het volgende voor nodig:
+
+1. We gaan ervan uit dat je je Ledger al hebt genitialiseerd en dus een hersteltekst van 24 woorden hebt gegenereerd.
+
+2. Je moet versie CLI v0.12.2.0 of hoger van de opdrachtregel-interface (CLI) gebruiken. Die vind je hier.
+
+3. Je moet de Monero-app voor de Ledger installeren en je systeem configureren. Instructies vind je [hier](https://github.com/LedgerHQ/blue-app-monero/blob/master/doc/user/bolos-app-monero.pdf) (met name de paragrafen 3.1.1 en 3.2.3). Zorg er verder voor dat het netwerk is ingesteld op `Mainnet`.
+
+4. Je Ledger moet zijn aangesloten en de Monero-app voor de Ledger moet worden uitgevoerd.
+
+5. De daemon (`monerod.exe`) moet worden uitgevoerd en liefst volledig gesynchroniseerd zijn - of je maakt verbinding met een externe node.
+
+Nu we ons voldoende hebben voorbereid, kunnen we beginnen.
+
+1. Ga naar de directory/map waar monerod.exe en monero-wallet-cli.exe staan.
+
+2. Open een nieuw venster voor de opdrachtregel/PowerShell. Dit doe je door met de rechtermuisknop in het venster te klikken, maar niet op een bestand, terwijl je de SHIFT-toets ingedrukt houdt. Dan krijg je de optie "Opdrachtvenster hier openen" in het contextmenu. Als je de nieuwste versie van Windows 10 gebruikt, krijg je de optie "Powershell-venster hier openen" te zien.
+
+3. Typ nu het volgende:
+
+`monero-wallet-cli.exe --generate-from-device --subaddress-lookahead 3:200` (Win 7 + 8)
+
+`.\monero-wallet-cli.exe --generate-from-device --subaddress-lookahead 3:200` (Win 10)
+
+De tekst tussen punthaken staat voor de naam die je aan de portemonnee geeft. Dus als je de portemonnee bijvoorbeeld `MoneroPortemonnee` noemt, ziet opdracht er als volgt uit:
+
+`monero-wallet-cli.exe --generate-from-device MoneroPortemonnee --subaddress-lookahead 3:200` (Win 7 + 8)
+
+`.\monero-wallet-cli.exe --generate-from-device MoneroPortemonnee --subaddress-lookahead 3:200` (Win 10)
+
+4. Nadat je deze opdracht hebt uitgevoerd, wordt je gevraagd een wachtwoord in te voeren. Zorg dat je een sterk wachtwoord kiest en bevestig het nog een keer.
+
+5. Vervolgens vraagt de Ledger of je de privsleutel wilt exporteren of niet. Allereerst: je geld kan niet worden ontvreemd met alleen de alleen-lezen privsleutel. Als je de alleen-lezen privsleutel exporteert, kan de client (op de computer - Monero v0.12.2.0) blokken doorzoeken om transacties te vinden die bij jouw portemonnee/adres horen. Als je deze optie niet inschakelt, zal de Ledger zelf in blokken zoeken. Dat werkt beduidend langzamer. Hier moeten we wel n waarschuwing bij geven. Als je systeem wordt gehackt, zou de aanvaller ook toegang kunnen krijgen tot je alleen-lezen privsleutel. Dat zou schadelijk voor je privacy zijn. Dit is praktisch onmogelijk als je de alleen-lezen privsleutel niet exporteert.
+
+6. Mogelijk moet je twee keer op Bevestigen klikken om verder te gaan.
+
+7. Nu wordt je Monero-portemonnee voor de Ledger gegenereerd. Dit kan 5 tot 10 minuten duren. Hierbij krijg je niet direct feedback in de CLI of op de Ledger.
+
+8. `monero-wallet-cli` begint te vernieuwen. Wacht totdat het klaar is met vernieuwen.
+
+Gefeliciteerd! Nu kun je je Monero-portemonnee voor de Ledger samen met de CLI gebruiken.
+
+### 2. MacOS
+Eerst moeten we ons voldoende voorbereiden. Daar is het volgende voor nodig:
+
+1. We gaan ervan uit dat je je Ledger al hebt genitialiseerd en dus een hersteltekst van 24 woorden hebt gegenereerd.
+
+2. Je moet versie CLI v0.12.2.0 of hoger van de opdrachtregel-interface (CLI) gebruiken. Die vind je hier.
+
+3. Je moet de Monero-app voor de Ledger installeren en je systeem configureren. Instructies vind je [hier](https://github.com/LedgerHQ/blue-app-monero/blob/master/doc/user/bolos-app-monero.pdf) (met name de paragrafen 3.1.1 en 3.2.2). Zorg er verder voor dat het netwerk is ingesteld op `Mainnet`.
+
+4. De instructies voor het configureren van het systeem (paragraaf 3.2.2) op macOS zijn nogal uitgebreid - misschien ingewikkelder dan nodig is. Gelukkig kun je ook [de handleiding](https://monero.stackexchange.com/questions/8438/how-do-i-make-my-macos-detect-my-ledger-nano-s-when-plugged-in) van tficharmers raadplegen.
+
+5. Je Ledger moet zijn aangesloten en de Monero-app voor de Ledger moet worden uitgevoerd.
+
+6. De daemon (`monerod`) moet worden uitgevoerd en liefst volledig gesynchroniseerd zijn - of je maakt verbinding met een externe node.
+
+Nu we ons voldoende hebben voorbereid, kunnen we beginnen.
+
+1. Gebruik Finder om naar de directory/map te gaan waar `monero-wallet-cli` (CLI v0.12.2.0) staat.
+
+2. Ga naar je bureaublad.
+
+3. Open een nieuwe terminal (kijk [hier](https://apple.stackexchange.com/a/256263) als je niet weet hoe je een terminal opent).
+
+4. Sleep `monero-wallet-cli` naar de terminal. Als het goed is, wordt het volledige pad nu in de terminal weergegeven. Druk niet op Enter.
+
+5. Typ nu het volgende:
+
+`--generate-from-device --subaddress-lookahead 3:200`
+
+De tekst tussen punthaken staat voor de naam die je aan de portemonnee geeft. Dus als je de portemonnee bijvoorbeeld `MoneroPortemonnee` noemt, ziet opdracht er als volgt uit:
+
+`--generate-from-device MoneroPortemonnee --subaddress-lookahead 3:200`
+
+De bovenstaande tekst wordt toegevoegd aan het pad van `monero-wallet-cli`. Dus je terminal moet er als volgt uitzien voordat je op Enter drukt:
+
+`/volledig/pad/naar/monero-wallet-cli --generate-from-device --subaddress-lookahead 3:200`
+
+Daarbij is het volledige pad uiteraard het werkelijke pad op je Mac.
+
+7. Nadat je deze opdracht hebt uitgevoerd, wordt je gevraagd een wachtwoord in te voeren. Zorg dat je een sterk wachtwoord kiest en bevestig het nog een keer.
+
+8. Vervolgens vraagt de Ledger of je de privsleutel wilt exporteren of niet. Allereerst: je geld kan niet worden ontvreemd met alleen de alleen-lezen privsleutel. Als je de alleen-lezen privsleutel exporteert, kan de client (op de computer - Monero v0.12.2.0) blokken doorzoeken om transacties te vinden die bij jouw portemonnee/adres horen. Als je deze optie niet inschakelt, zal de Ledger zelf in blokken zoeken. Dat werkt beduidend langzamer. Hier moeten we wel n waarschuwing bij geven. Als je systeem wordt gehackt, zou de aanvaller ook toegang kunnen krijgen tot je alleen-lezen privsleutel. Dat zou schadelijk voor je privacy zijn. Dit is praktisch onmogelijk als je de alleen-lezen privsleutel niet exporteert.
+
+9. Mogelijk moet je twee keer op Bevestigen klikken om verder te gaan.
+
+10. Nu wordt je Monero-portemonnee voor de Ledger gegenereerd. Dit kan 5 tot 10 minuten duren. Hierbij krijg je niet direct feedback in de CLI of op de Ledger.
+
+11. `monero-wallet-cli` begint te vernieuwen. Wacht totdat het klaar is met vernieuwen.
+
+12. Gefeliciteerd! Nu kun je je Monero-portemonnee voor de Ledger samen met de CLI gebruiken.
+
+### 3. Linux
+Eerst moeten we ons voldoende voorbereiden. Daar is het volgende voor nodig:
+
+1. We gaan ervan uit dat je je Ledger al hebt genitialiseerd en dus een hersteltekst van 24 woorden hebt gegenereerd.
+
+2. Je moet versie CLI v0.12.2.0 of hoger van de opdrachtregel-interface (CLI) gebruiken. Die vind je hier.
+
+3. Je moet de Monero-app voor de Ledger installeren en je systeem configureren. Instructies vind je [hier](https://github.com/LedgerHQ/blue-app-monero/blob/master/doc/user/bolos-app-monero.pdf) (met name de paragrafen 3.1.1 en 3.2.1). Zorg er verder voor dat het netwerk is ingesteld op `Mainnet`.
+
+4. Je Ledger moet zijn aangesloten en de Monero-app voor de Ledger moet worden uitgevoerd.
+
+5. De daemon (`monerod`) moet worden uitgevoerd en liefst volledig gesynchroniseerd zijn - of je maakt verbinding met een externe node.
+
+Nu we ons voldoende hebben voorbereid, kunnen we beginnen.
+
+1. Ga naar de directory/map waar monero-wallet-cli en monerod staan.
+
+2. Open een nieuwe terminal.
+
+3. Typ nu het volgende:
+
+`./monero-wallet-cli --generate-from-device --subaddress-lookahead 3:200`
+
+De tekst tussen punthaken staat voor de naam die je aan de portemonnee geeft. Dus als je de portemonnee bijvoorbeeld `MoneroPortemonnee` noemt, ziet opdracht er als volgt uit:
+
+`./monero-wallet-cli --generate-from-device MoneroPortemonnee --subaddress-lookahead 3:200`
+
+4. Nadat je deze opdracht hebt uitgevoerd, wordt je gevraagd een wachtwoord in te voeren. Zorg dat je een sterk wachtwoord kiest en bevestig het nog een keer.
+
+5. Vervolgens vraagt de Ledger of je de privsleutel wilt exporteren of niet. Allereerst: je geld kan niet worden ontvreemd met alleen de alleen-lezen privsleutel. Als je de alleen-lezen privsleutel exporteert, kan de client (op de computer - Monero v0.12.2.0) blokken doorzoeken om transacties te vinden die bij jouw portemonnee/adres horen. Als je deze optie niet inschakelt, zal de Ledger zelf in blokken zoeken. Dat werkt beduidend langzamer. Hier moeten we wel n waarschuwing bij geven. Als je systeem wordt gehackt, zou de aanvaller ook toegang kunnen krijgen tot je alleen-lezen privsleutel. Dat zou schadelijk voor je privacy zijn. Dit is praktisch onmogelijk als je de alleen-lezen privsleutel niet exporteert.
+
+6. Mogelijk moet je twee keer op Bevestigen klikken om verder te gaan.
+
+7. Nu wordt je Monero-portemonnee voor de Ledger gegenereerd. Dit kan 5 tot 10 minuten duren. Hierbij krijg je niet direct feedback in de CLI of op de Ledger.
+
+8. `monero-wallet-cli` begint te vernieuwen. Wacht totdat het klaar is met vernieuwen.
+
+Gefeliciteerd! Nu kun je je Monero-portemonnee voor de Ledger samen met de CLI gebruiken.
+
+### 4. Ten slotte
+
+1. We raden je dringend aan het hele proces eerst te testen. Verzend een klein bedrag naar de Ledger en herstel het vervolgens (volgens de bovengenoemde handleiding) om te controleren of je de portemonnee kunt herstellen. Opmerking: bij het herstellen van de portemonnee moet je de parameter `--restore-height` (met een bloknummer vr de hoogte van je eerste transactie naar de portemonnee) toevoegen aan de opdracht in stap 3 (Windows), stap 5 (macOS) of stap 3 (Linux). Meer informatie over de herstelhoogte en hoe je die kunt schatten vind je [hier](https://monero.stackexchange.com/questions/7581/what-is-the-relevance-of-the-restore-height).
+
+2. Als je een externe node gebruikt, voeg je de parameter `--daemon-address host:port` toe aan de opdracht in stap 3 (Windows), stap 5 (macOS) of stap 3 (Linux).
+
+3. Eventueel kun je de waarde voor `--subaddress-lookahead` handmatig afstellen. De eerste waarde is het aantal accounts en de tweede waarde is het aantal subadressen per account. Dus als je bijvoorbeeld 5 accounts met 100 subadressen vooraf wilt genereren, geef je `--subaddress-lookahead 5:100` op. Houd er rekening mee dat de Ledger er langer over doet om je portemonnee te maken naarmate je meer subadressen vooraf laat genereren.
+
+4. Je hoeft de parameter `--generate-from-device` maar n keer te gebruiken (bij het aanmaken van een portemonnee). Daarna gebruik je de portemonnee net zoals je de CLI normaal zou gebruiken. Dat wil zeggen:
+ 1. Zorg dat je Ledger is aangesloten en dat de Monero-app wordt uitgevoerd.
+ 2. Open `monero-wallet-cli`.
+ 3. Voer de naam van je Monero-portemonnee voor de Ledger in.
+ 4. Voer het wachtwoord in om de portemonnee te openen.
+
+ Als de portemonneebestanden op de Ledger niet in dezelfde directory staan als `monero-wallet-cli`, moet je `monero-wallet-cli` openen met de parameter `--wallet-file /pad/naar/bestand/portemonnee.keys`. Maar je kunt de bestanden van de Ledger-portemonnee ook kopiren naar dezelfde directory als `monero-wallet-cli`.
+
+5. Als je nog meer vragen hebt of hulp nodig hebt, kun je een reactie achterlaten op het oorspronkelijke [antwoord op StackExchange](https://monero.stackexchange.com/questions/8503/how-do-i-generate-a-ledger-monero-wallet-with-the-cli-monero-wallet-cli).
+
+Auteur: dEBRUYNE
+Bewerkt door: el00ruobuob
diff --git a/_i18n/nl/resources/user-guides/mine-to-pool.md b/_i18n/nl/resources/user-guides/mine-to-pool.md
new file mode 100644
index 00000000..2cbd004b
--- /dev/null
+++ b/_i18n/nl/resources/user-guides/mine-to-pool.md
@@ -0,0 +1,115 @@
+{% assign version = '1.1.0' | split: '.' %}
+{% include disclaimer.html translated="true" version=page.version %}
+# Een pool selecteren
+
+Je kunt uit allerlei pools kiezen. Er staat een lijst op
+[moneropools.com](https://moneropools.com). Als je bij een grotere pool minet, kun je
+vaker betaald worden, maar als je bij een kleinere pool minet, help je het netwerk
+gedecentraliseerd te houden.
+
+# Een CPU-miningprogramma selecteren
+
+Net als pools zijn er veel miningprogramma's waaruit je kunt kiezen. Welke soort software
+je nodig hebt hangt af van de hardware waarop je wilt minen. Deze handleiding gaat over
+minen op een CPU, en daarvoor gebruiken we
+[xmr-stak-cpu](https://github.com/fireice-uk/xmr-stak-cpu). Andere mogelijkheden zijn onder meer
+[wolf's CPUMiner](https://github.com/wolf9466/cpuminer-multi) en
+[sgminer-gm](https://github.com/genesismining/sgminer-gm). Maar de
+configuratie daarvan is net iets anders en wordt hier niet behandeld.
+
+## Voor Windows-systemen
+
+Als je een Windows-systeem gebruikt, kun je de binaries van xmr-stak-cpu
+downloaden op de
+[release-pagina op GitHub](https://github.com/fireice-uk/xmr-stak-cpu/releases).
+
+Download `xmr-stak-cpu-win64.zip` en pak het uit op een plek waar je
+het kunt terugvinden.
+
+## Voor andere besturingssystemen
+
+Als je niet Windows gebruikt, moet je zelf xmr-stak-cpu compileren.
+Gelukkig is dat niet zo moeilijk als het klinkt. Voordat je het miningprogramma kunt compileren,
+moet je een paar vereiste onderdelen installeren.
+
+Voor distributies op basis van Debian:
+
+ sudo apt-get install libmicrohttpd-dev libssl-dev cmake build-essential
+
+Voor distributies op basis van Red Hat:
+
+ sudo yum install openssl-devel cmake gcc-c++ libmicrohttpd-devel
+
+
+
+Hierna hoef je alleen nog de build-bestanden te maken met cmake,
+make uit te voeren en het configuratiebestand te kopiren:
+
+ mkdir build-$(gcc -dumpmachine)
+ cd $_
+ cmake ../
+ make -j$(nproc)
+ cp ../config.txt bin/
+ cd bin
+
+Juich niet te vroeg, want het miningprogramma moet nog worden geconfigureerd. Als je het miningprogramma nu uitvoert,
+wordt er een blok tekst weergegeven om te kopiren en plakken:
+
+![image1](png/mine_to_pool/1.png)
+
+Open `config.txt` en *vervang* de twee regels `"cpu_threads_conf"` met de tekst
+die je net hebt gekopieerd. Daarna zou het er ongeveer zo uit moeten zien:
+
+![image2](png/mine_to_pool/2.png)
+
+Schuif omlaag in het bestand tot je bij de regels met `"pool_address"` bent.
+*Vervang* de inhoud van het tweede stel aanhalingstekens met het adres en de poort van
+de pool die je eerder hebt gekozen. Je kunt deze informatie op de website van de pool vinden.
+
+Plak het adres van je portemonnee tussen de aanhalingstekens bij `wallet_address`. Je kunt het
+wachtwoord leeg laten, tenzij de pool een wachtwoord vereist.
+
+Hierna zou je configuratie er ongeveer zo uit moeten zien:
+
+![image3](png/mine_to_pool/3.png)
+
+# Het miningprogramma uitvoeren
+
+**Sla het configuratiebestand op** en voer het miningprogramma uit.
+
+![image4](png/mine_to_pool/4.png)
+
+Bij sommige pools kun je je hashrate volgen door je adres in te voeren op hun
+website. Je kunt de hashrate ook zien door op de toets `h` te drukken.
+
+# Het miningprogramma afstellen
+
+Mogelijk krijg je vervelende meldingen als deze te zien:
+
+ [2017-07-09 12:04:02] : MEMORY ALLOC FAILED: mmap failed
+
+Dit betekent dat je je hashrate met ongeveer 20% kunt verhogen door grote pagina's in te schakelen.
+
+## Grote pagina's in Linux
+
+Stop eerst het miningprogramma (als het aan staat), voer de volgende opdrachten uit om
+grote pagina's in te schakelen en start vervolgens het miningprogramma als root:
+
+ sudo sysctl -w vm.nr_hugepages=128
+ sudo ./xmr-stak-cpu
+
+## Grote pagina's in Windows
+
+Geciteerd uit `config.txt`:
+
+Standaard proberen we grote pagina's toe te wijzen. Hiervoor moet je het programma als Administrator uitvoeren in Windows.
+Je moet het vergrendelen van grote pagina's inschakelen in het groepsbeleid van je systeem. Dit zijn de stappen volgens MSDN:
+1. Klik in het Startmenu op `Uitvoeren`. Typ gpedit.msc in het vak `Openen`.
+2. In de console van de `Editor voor lokaal groepsbeleid` vouw je `Computerconfiguratie` uit, en vervolgens `Windows-instellingen`.
+3. Vouw `Beveiligingsinstellingen` uit, en vervolgens `Lokaal beleid`.
+4. Selecteer de map `Toewijzing van gebruikersrechten`.
+5. De beleidsregels worden weergegeven in het detailvenster.
+6. Dubbelklik in het deelvenster op `Pagina's in het geheugen vergrendelen`.
+7. Klik in het dialoogvenster `Lokale beveiligingsinstelling` – `Pagina's in het geheugen vergrendelen` op `Gebruiker of groep toevoegen`.
+8. Voeg in het dialoogvenster `Gebruikers of groepen selecteren` een account toe waarop u het miningprogramma wilt uitvoeren.
+9. Start de computer opnieuw op om de wijziging door te voeren.
diff --git a/_i18n/nl/resources/user-guides/mining_with_xmrig_and_docker.md b/_i18n/nl/resources/user-guides/mining_with_xmrig_and_docker.md
new file mode 100644
index 00000000..3e30fd69
--- /dev/null
+++ b/_i18n/nl/resources/user-guides/mining_with_xmrig_and_docker.md
@@ -0,0 +1,38 @@
+{% assign version = '1.1.0' | split: '.' %}
+{% include disclaimer.html translated="true" version=page.version %}
+## Inleiding
+
+Deze handleiding heeft twee doelen: gebruiksgemak bij het minen op Linux-distributies en extra veiligheid rondom het minen, aangezien de meeste miningprogramma's niet zijn gecontroleerd op veiligheid.
+
+Aan het eind van deze handleiding kun je er gerust op zijn dat je besturingssysteem niet wordt aangetast als het miningprogramma wordt gehackt.
+
+### Waarom Docker?
+
+Hierbij gebruiken we [Docker](https://www.docker.com/), want dat is de bekendste containertechnologie, met de grootste kans dat het al is genstalleerd.
+
+De container die ik gebruik is [alpine-xmrig](https://hub.docker.com/r/bitnn/alpine-xmrig/). Zoals de naam aangeeft, is deze gebaseerd op de distributie [Alpine Linux](https://www.alpinelinux.org/).
+
+Hier zijn een paar goede informatiebronnen als je met Docker wilt leren werken:
+* [Arch Linux Wiki over Docker](https://wiki.archlinux.org/index.php/Docker)
+* [Security Cheat Sheet](http://container-solutions.com/content/uploads/2015/06/15.06.15_DockerCheatSheet_A2.pdf) van Container Solutions
+* Digital Ocean's [Dockerfile Howto](https://www.digitalocean.com/community/tutorials/docker-explained-using-dockerfiles-to-automate-building-of-images).
+
+Zie de [Docker-documentatie](https://docs.docker.com/engine/installation/)-website voor de installatie op specifieke distributies.
+
+### Waarom XMRig?
+
+[XMRig](https://github.com/xmrig/xmrig) is gewoon een degelijk miningprogramma. Prima uitvoer en statistieken, geen flitsende webinterface of afhankelijkheden. De XMRig-container is slechts ~4 MB, zodat hij op allerlei hardware kan worden gebruikt.
+
+#### Stap 1. Minen met XMRig
+
+Voer het volgende uit:
+
+```bash
+# docker run --restart unless-stopped --read-only -m 50M -c 512 bitnn/alpine-xmrig -o POOL01 -o POOL02 -u PORTEMONNEE -p WACHTWOORD -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
+```
+
+#### Stap 2. Er is geen stap 2.
+
+Je hebt alles wat je moet doen al gedaan. Je bent nu aan het minen in een Docker-container met XMRig. Typ `Ctrl+C` om XMRig af te sluiten of voeg `-d` direct na `docker run` toe om het miningprogramma in de achtergrond uit te voeren.
+
diff --git a/_i18n/nl/resources/user-guides/monero-wallet-cli.md b/_i18n/nl/resources/user-guides/monero-wallet-cli.md
new file mode 100644
index 00000000..967ef177
--- /dev/null
+++ b/_i18n/nl/resources/user-guides/monero-wallet-cli.md
@@ -0,0 +1,147 @@
+{% assign version = '1.1.0' | split: '.' %}
+{% include disclaimer.html translated="true" version=page.version %}
+# monero-wallet-cli
+
+`monero-wallet-cli` is de portemonnee-software die onderdeel uitmaakt van de Monero-code. Het is een consoleprogramma
+waarmee je een account beheert. Terwijl een Bitcoin-portemonnee zowel een account als de blockchain beheert,
+worden deze functies in Monero gescheiden: `monerod` beheert de blockchain en `monero-wallet-cli` beheert het account.
+
+In deze handleiding wordt uitgelegd hoe je verschillende bewerking uitvoert met de interface van `monero-wallet-cli`. We nemen aan dat je de nieuwste versie van Monero gebruikt en al een account hebt gemaakt met behulp van andere handleidingen.
+
+
+## Je saldo bekijken
+
+Omdat we een ander programma dan de portemonnee gebruiken om met de blockchain te werken, moet `monero-wallet-cli` voor veel toepassingen
+samenwerken met de node. Dit is bijvoorbeeld nodig om binnenkomende transacties voor je adres op te zoeken.
+Wanneer `monero-wallet-cli` en `monerod` beide worden uitgevoerd, voer je `balance` in.
+
+Voorbeeld:
+
+Hiermee worden blokken uit de node opgehaald die de portemonnee nog niet gezien heeft, en wordt je saldo navenant
+bijgewerkt. Dit proces wordt normaal ongeveer n keer per minuut in de achtergrond uitgevoerd. Zo geef je het saldo weer
+zonder te vernieuwen:
+
+ balance
+ Balance: 64.526198850000, unlocked balance: 44.526198850000, including unlocked dust: 0.006198850000
+
+In dit voorbeeld is `Balance` je totale saldo. De `unlocked balance` is het bedrag dat momenteel beschikbaar is om uit te geven. Voor nieuw ontvangen transacties zijn 10 bevestigingen op de blockchain nodig om ze te ontgrendelen. Met `unlocked dust` worden minuscule hoeveelheden *unspent outputs* bedoeld die als een soort stof in je account zijn terechtgekomen.
+
+## Monero verzenden
+
+Wat je nodig hebt is het standaardadres waaraan je wilt betalen (een lange tekenreeks die begint met een 4), en
+eventueel een betalings-ID als de ontvangende partij daarom vraagt. In dat geval kan de begunstigde
+ook een gentegreerd adres opgeven, waarbij het standaardadres en de betalings-ID in n adres worden verpakt.
+
+### Verzenden naar een standaardadres:
+
+ transfer ADRES BEDRAG BETALINGSID
+
+Vervang `ADRES` door het adres waaraan je wilt betalen, `BEDRAG` door hoeveel Monero je wilt betalen
+en `BETALINGSID` door de betalings-ID die je hebt ontvangen. Betalings-ID's zijn optioneel. Als de ontvangende partij er geen nodig heeft, kun je
+de ID gewoon weglaten.
+
+### Verzenden naar een gentegreerd adres:
+
+ transfer ADRES BEDRAG
+
+Hier is de betalings-ID opgenomen in het gentegreerde adres.
+
+### Het aantal outputs in een transactie opgeven:
+
+ transfer RINGGROOTTE ADRES BEDRAG
+
+Vervang `RINGGROOTTE` door het aantal outputs dat je wilt gebruiken. **Als je niets opgeeft is de standaardwaarde 11.** Het is beter om de standaardwaarde te gebruiken, maar je kunt eventueel een hoger aantal opgeven als ze meer outputs wilt meenemen. Hoe hoger het aantal, des te groter de transactie en des te hoger de transactiekosten.
+
+
+## Monero ontvangen
+
+Als je zelf een Monero-adres hebt, kun je gewoon je standaardadres aan iemand doorgeven.
+
+Met de volgende opdracht krijg je je adres te zien:
+
+ address
+
+Aangezien Monero anoniem is, kun je niet zien van welk adres het geld dat je ontvangt afkomstig is. Als je
+dat wilt weten, bijvoorbeeld om een betaling aan een klant te koppelen, moet je de afzender vragen
+een betalings-ID te gebruiken. Dat is een willekeurige optionele tekenreeks dat wordt toegevoegd aan een transactie. Voor het gemak
+kun je een adres genereren dat al een willekeurige betalings-ID bevat:
+
+ integrated_address
+
+Hierdoor wordt een willekeurige betalings-ID gegenereerd en krijg je een adres waarin je eigen account en de
+betalings-ID worden samengevat. Het is ook mogelijk om een bepaalde betalings-ID te kiezen als je dat wilt:
+
+ integrated_address 12346780abcdef00
+
+Betalingen aan een gentegreerd adres dat jij hebt gegenereerd gaan naar jouw account
+met vermelding van die betalings-ID, zodat je betalingen kunt onderscheiden.
+
+
+## Aan een derde bewijzen dat je iemand hebt betaald
+
+Als je een verkoper betaalt, en de verkoper beweert dat hij/zij het geld niet heeft ontvangen, wil je misschien
+aan een derde bewijzen dat je het geld wel degelijk hebt verzonden - of aan de verkoper zelf, als het een eerlijke
+vergissing is. Monero is vertrouwelijk, dus je kunt niet zomaar je transactie aanwijzen op de blockchain,
+want daar is niet te zien wie een transactie heeft verzonden of ontvangen. Maar je kunt iemand wel de privsleutel van een transactie
+geven, zodat die kan zien of die transactie Monero naar dat
+adres heeft verzonden. Houd er rekening mee dat het opslaan van deze transactiesleutels standaard is uitgeschakeld.
+Je moet deze functie voor het verzenden inschakelen als je denkt dat je deze misschien nodig hebt:
+
+ set store-tx-info 1
+
+Je kunt de transactiesleutel van een eerdere transactie ophalen:
+
+ get_tx_key 1234567890123456789012345678901212345678901234567890123456789012
+
+Voer hierbij de ID in van de transactie waarvoor u de sleutel wilt hebben. Houd er rekening mee dat een betaling kan zijn gesplitst
+in meer dan n transactie, zodat je meerdere sleutels nodig hebt. Vervolgens kun je de sleutel
+of sleutels opsturen naar wie je het bewijs van je transactie wilt laten zien, met de
+transactie-ID en het adres van de ontvanger erbij. Opmerking: als deze partij ook je eigen
+adres kent, kan deze ook zien hoeveel wisselgeld je hebt teruggekregen.
+
+Als je zelf de derde partij bent (dus als iemand aan jou wilt bewijzen dat hij/zij Monero naar een bepaald
+adres heeft verzonden), kun je dat op deze manier controleren:
+
+ check_tx_key TXID SLEUTEL ADRES
+
+Vervang `TXID` door de transactie-ID, `SLEUTEL` door de transactiesleutel en `ADRES` door het doeladres
+dat je hebt ontvangen. Vervolgens controleert monero-wallet-cli die transactie
+en laat het weten hoeveel door deze transactie aan het opgegeven adres is betaald.
+
+
+## Instellen dat je betalingen kunt bevestigen/annuleren
+
+Als je een laatste kans wilt krijgen om een betaling te bevestigen of annuleren:
+
+ set always-confirm-transfers 1
+
+
+## Een betaling aan jou vinden
+
+Als je een betaling met een bepaalde betalings-ID hebt ontvangen, kun je deze opzoeken:
+
+ payments BETALINGSID
+
+Je kunt ook meer dan n betalings-ID opgeven.
+
+In het algemeen kun je binnenkomende en uitgaande betalingen bekijken:
+
+ show_transfers
+
+Je kunt een optionele blokhoogte opgeven om alleen recente transacties te ontvangen, en je kunt
+alleen binnenkomende of uitgaande transactie opvragen. Bijvoorbeeld:
+
+ show_transfers in 650000
+
+levert alleen binnenkomende overboekingen na blok 650.000 op. Je kunt ook een bereik van blokhoogten
+opgeven.
+
+Als je wilt minen, kun je dat ook vanuit de portemonnee doen:
+
+ start_mining 2
+
+Hiermee gebruik je twee CPU-threads om te minen via de daemon. Let op: dit is solo minen;
+het kan lang duren voordat je een blok vindt. Om te stoppen met minen:
+
+ stop_mining
+
diff --git a/_i18n/nl/resources/user-guides/monero_tools.md b/_i18n/nl/resources/user-guides/monero_tools.md
new file mode 100644
index 00000000..678ba565
--- /dev/null
+++ b/_i18n/nl/resources/user-guides/monero_tools.md
@@ -0,0 +1,19 @@
+{% assign version = '1.1.0' | split: '.' %}
+{% include disclaimer.html translated="true" version=page.version %}
+# Monero-tools
+
+Met deze hulpmiddelen kun je informatie vinden over het Monero-netwerk of over je transactiegegevens op de blockchain.
+
+### [Controleren of een geadresseerde je geld heeft ontvangen](http://xmrtests.llcoins.net/checktx.html)
+
+### [Tools voor het genereren van Monero-adressen](https://xmr.llcoins.net/)
+
+### [Het aantal Monero-nodes](http://moneronodes.i2p.xyz/)
+
+### [Kaart van Monero-nodes](https://monerohash.com/nodes-distribution.html)
+
+### [Offline generator van Monero-portemonnees](http://moneroaddress.org/)
+
+### [Monero-netwerkstatistieken](http://moneroblocks.info/stats)
+
+### [Statistieken van Monero.how](https://www.monero.how/)
diff --git a/_i18n/nl/resources/user-guides/png/create_wallet/1.png b/_i18n/nl/resources/user-guides/png/create_wallet/1.png
new file mode 100644
index 00000000..44acf51b
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/create_wallet/1.png differ
diff --git a/_i18n/nl/resources/user-guides/png/create_wallet/10.png b/_i18n/nl/resources/user-guides/png/create_wallet/10.png
new file mode 100644
index 00000000..2f248c9d
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/create_wallet/10.png differ
diff --git a/_i18n/nl/resources/user-guides/png/create_wallet/11.png b/_i18n/nl/resources/user-guides/png/create_wallet/11.png
new file mode 100644
index 00000000..f8bb9989
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/create_wallet/11.png differ
diff --git a/_i18n/nl/resources/user-guides/png/create_wallet/12.png b/_i18n/nl/resources/user-guides/png/create_wallet/12.png
new file mode 100644
index 00000000..2e1f69d6
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/create_wallet/12.png differ
diff --git a/_i18n/nl/resources/user-guides/png/create_wallet/13.png b/_i18n/nl/resources/user-guides/png/create_wallet/13.png
new file mode 100644
index 00000000..2db5d603
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/create_wallet/13.png differ
diff --git a/_i18n/nl/resources/user-guides/png/create_wallet/14.png b/_i18n/nl/resources/user-guides/png/create_wallet/14.png
new file mode 100644
index 00000000..bf2906e2
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/create_wallet/14.png differ
diff --git a/_i18n/nl/resources/user-guides/png/create_wallet/15.png b/_i18n/nl/resources/user-guides/png/create_wallet/15.png
new file mode 100644
index 00000000..7c675edf
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/create_wallet/15.png differ
diff --git a/_i18n/nl/resources/user-guides/png/create_wallet/16.png b/_i18n/nl/resources/user-guides/png/create_wallet/16.png
new file mode 100644
index 00000000..ab23b572
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/create_wallet/16.png differ
diff --git a/_i18n/nl/resources/user-guides/png/create_wallet/17.png b/_i18n/nl/resources/user-guides/png/create_wallet/17.png
new file mode 100644
index 00000000..97ea15bc
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/create_wallet/17.png differ
diff --git a/_i18n/nl/resources/user-guides/png/create_wallet/18.png b/_i18n/nl/resources/user-guides/png/create_wallet/18.png
new file mode 100644
index 00000000..20546a9a
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/create_wallet/18.png differ
diff --git a/_i18n/nl/resources/user-guides/png/create_wallet/19.png b/_i18n/nl/resources/user-guides/png/create_wallet/19.png
new file mode 100644
index 00000000..5a7088e2
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/create_wallet/19.png differ
diff --git a/_i18n/nl/resources/user-guides/png/create_wallet/2.png b/_i18n/nl/resources/user-guides/png/create_wallet/2.png
new file mode 100644
index 00000000..164aa6b6
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/create_wallet/2.png differ
diff --git a/_i18n/nl/resources/user-guides/png/create_wallet/20.png b/_i18n/nl/resources/user-guides/png/create_wallet/20.png
new file mode 100644
index 00000000..c5169249
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/create_wallet/20.png differ
diff --git a/_i18n/nl/resources/user-guides/png/create_wallet/21.png b/_i18n/nl/resources/user-guides/png/create_wallet/21.png
new file mode 100644
index 00000000..090ff767
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/create_wallet/21.png differ
diff --git a/_i18n/nl/resources/user-guides/png/create_wallet/22.png b/_i18n/nl/resources/user-guides/png/create_wallet/22.png
new file mode 100644
index 00000000..8c7a7669
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/create_wallet/22.png differ
diff --git a/_i18n/nl/resources/user-guides/png/create_wallet/23.png b/_i18n/nl/resources/user-guides/png/create_wallet/23.png
new file mode 100644
index 00000000..e2dfc0c4
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/create_wallet/23.png differ
diff --git a/_i18n/nl/resources/user-guides/png/create_wallet/3.png b/_i18n/nl/resources/user-guides/png/create_wallet/3.png
new file mode 100644
index 00000000..f4f4436e
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/create_wallet/3.png differ
diff --git a/_i18n/nl/resources/user-guides/png/create_wallet/4.png b/_i18n/nl/resources/user-guides/png/create_wallet/4.png
new file mode 100644
index 00000000..36be1be0
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/create_wallet/4.png differ
diff --git a/_i18n/nl/resources/user-guides/png/create_wallet/5.png b/_i18n/nl/resources/user-guides/png/create_wallet/5.png
new file mode 100644
index 00000000..56c6733a
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/create_wallet/5.png differ
diff --git a/_i18n/nl/resources/user-guides/png/create_wallet/6.png b/_i18n/nl/resources/user-guides/png/create_wallet/6.png
new file mode 100644
index 00000000..8e0d7950
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/create_wallet/6.png differ
diff --git a/_i18n/nl/resources/user-guides/png/create_wallet/7.png b/_i18n/nl/resources/user-guides/png/create_wallet/7.png
new file mode 100644
index 00000000..c1852782
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/create_wallet/7.png differ
diff --git a/_i18n/nl/resources/user-guides/png/create_wallet/8.png b/_i18n/nl/resources/user-guides/png/create_wallet/8.png
new file mode 100644
index 00000000..ce02508b
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/create_wallet/8.png differ
diff --git a/_i18n/nl/resources/user-guides/png/create_wallet/9.png b/_i18n/nl/resources/user-guides/png/create_wallet/9.png
new file mode 100644
index 00000000..cac31479
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/create_wallet/9.png differ
diff --git a/_i18n/nl/resources/user-guides/png/easiest_way/01.png b/_i18n/nl/resources/user-guides/png/easiest_way/01.png
new file mode 100644
index 00000000..17c55b2d
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/easiest_way/01.png differ
diff --git a/_i18n/nl/resources/user-guides/png/easiest_way/02.png b/_i18n/nl/resources/user-guides/png/easiest_way/02.png
new file mode 100644
index 00000000..91e1bfd1
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/easiest_way/02.png differ
diff --git a/_i18n/nl/resources/user-guides/png/easiest_way/03.png b/_i18n/nl/resources/user-guides/png/easiest_way/03.png
new file mode 100644
index 00000000..dded71ad
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/easiest_way/03.png differ
diff --git a/_i18n/nl/resources/user-guides/png/easiest_way/04.png b/_i18n/nl/resources/user-guides/png/easiest_way/04.png
new file mode 100644
index 00000000..e657d431
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/easiest_way/04.png differ
diff --git a/_i18n/nl/resources/user-guides/png/easiest_way/05.png b/_i18n/nl/resources/user-guides/png/easiest_way/05.png
new file mode 100644
index 00000000..00d2b26a
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/easiest_way/05.png differ
diff --git a/_i18n/nl/resources/user-guides/png/easiest_way/06.png b/_i18n/nl/resources/user-guides/png/easiest_way/06.png
new file mode 100644
index 00000000..4d55286c
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/easiest_way/06.png differ
diff --git a/_i18n/nl/resources/user-guides/png/easiest_way/07.png b/_i18n/nl/resources/user-guides/png/easiest_way/07.png
new file mode 100644
index 00000000..715245b2
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/easiest_way/07.png differ
diff --git a/_i18n/nl/resources/user-guides/png/easiest_way/08.png b/_i18n/nl/resources/user-guides/png/easiest_way/08.png
new file mode 100644
index 00000000..bfc459a8
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/easiest_way/08.png differ
diff --git a/_i18n/nl/resources/user-guides/png/easiest_way/09.png b/_i18n/nl/resources/user-guides/png/easiest_way/09.png
new file mode 100644
index 00000000..e632bbb8
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/easiest_way/09.png differ
diff --git a/_i18n/nl/resources/user-guides/png/easiest_way/10.png b/_i18n/nl/resources/user-guides/png/easiest_way/10.png
new file mode 100644
index 00000000..3a933733
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/easiest_way/10.png differ
diff --git a/_i18n/nl/resources/user-guides/png/easiest_way/11.png b/_i18n/nl/resources/user-guides/png/easiest_way/11.png
new file mode 100644
index 00000000..eaa4a5b9
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/easiest_way/11.png differ
diff --git a/_i18n/nl/resources/user-guides/png/easiest_way/12.png b/_i18n/nl/resources/user-guides/png/easiest_way/12.png
new file mode 100644
index 00000000..e38159ec
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/easiest_way/12.png differ
diff --git a/_i18n/nl/resources/user-guides/png/easiest_way/13.png b/_i18n/nl/resources/user-guides/png/easiest_way/13.png
new file mode 100644
index 00000000..ed3b707d
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/easiest_way/13.png differ
diff --git a/_i18n/nl/resources/user-guides/png/mine_to_pool/1.png b/_i18n/nl/resources/user-guides/png/mine_to_pool/1.png
new file mode 100644
index 00000000..a6e76528
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/mine_to_pool/1.png differ
diff --git a/_i18n/nl/resources/user-guides/png/mine_to_pool/2.png b/_i18n/nl/resources/user-guides/png/mine_to_pool/2.png
new file mode 100644
index 00000000..83a7dd16
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/mine_to_pool/2.png differ
diff --git a/_i18n/nl/resources/user-guides/png/mine_to_pool/3.png b/_i18n/nl/resources/user-guides/png/mine_to_pool/3.png
new file mode 100644
index 00000000..70aeea2a
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/mine_to_pool/3.png differ
diff --git a/_i18n/nl/resources/user-guides/png/mine_to_pool/4.png b/_i18n/nl/resources/user-guides/png/mine_to_pool/4.png
new file mode 100644
index 00000000..13361a0e
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/mine_to_pool/4.png differ
diff --git a/_i18n/nl/resources/user-guides/png/prove-payment/check-payment.png b/_i18n/nl/resources/user-guides/png/prove-payment/check-payment.png
new file mode 100644
index 00000000..48bc49a9
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/prove-payment/check-payment.png differ
diff --git a/_i18n/nl/resources/user-guides/png/prove-payment/history.png b/_i18n/nl/resources/user-guides/png/prove-payment/history.png
new file mode 100644
index 00000000..bad5adde
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/prove-payment/history.png differ
diff --git a/_i18n/nl/resources/user-guides/png/prove-payment/payment-checked.png b/_i18n/nl/resources/user-guides/png/prove-payment/payment-checked.png
new file mode 100644
index 00000000..e858ea01
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/prove-payment/payment-checked.png differ
diff --git a/_i18n/nl/resources/user-guides/png/prove-payment/payment-proof.png b/_i18n/nl/resources/user-guides/png/prove-payment/payment-proof.png
new file mode 100644
index 00000000..76f626ea
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/prove-payment/payment-proof.png differ
diff --git a/_i18n/nl/resources/user-guides/png/remote_node/remote-node-screenshot.png b/_i18n/nl/resources/user-guides/png/remote_node/remote-node-screenshot.png
new file mode 100644
index 00000000..fe34784f
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/remote_node/remote-node-screenshot.png differ
diff --git a/_i18n/nl/resources/user-guides/png/restore_account/all-set-up.png b/_i18n/nl/resources/user-guides/png/restore_account/all-set-up.png
new file mode 100644
index 00000000..aebc5e4c
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/restore_account/all-set-up.png differ
diff --git a/_i18n/nl/resources/user-guides/png/restore_account/cancel-opening.png b/_i18n/nl/resources/user-guides/png/restore_account/cancel-opening.png
new file mode 100644
index 00000000..1d987435
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/restore_account/cancel-opening.png differ
diff --git a/_i18n/nl/resources/user-guides/png/restore_account/choose-language.png b/_i18n/nl/resources/user-guides/png/restore_account/choose-language.png
new file mode 100644
index 00000000..d49f8ffa
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/restore_account/choose-language.png differ
diff --git a/_i18n/nl/resources/user-guides/png/restore_account/choose-restore.png b/_i18n/nl/resources/user-guides/png/restore_account/choose-restore.png
new file mode 100644
index 00000000..fbba0bb0
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/restore_account/choose-restore.png differ
diff --git a/_i18n/nl/resources/user-guides/png/restore_account/daemon-settings.png b/_i18n/nl/resources/user-guides/png/restore_account/daemon-settings.png
new file mode 100644
index 00000000..0f70dee0
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/restore_account/daemon-settings.png differ
diff --git a/_i18n/nl/resources/user-guides/png/restore_account/restore-wallet.png b/_i18n/nl/resources/user-guides/png/restore_account/restore-wallet.png
new file mode 100644
index 00000000..690b363e
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/restore_account/restore-wallet.png differ
diff --git a/_i18n/nl/resources/user-guides/png/restore_account/wallet-password.png b/_i18n/nl/resources/user-guides/png/restore_account/wallet-password.png
new file mode 100644
index 00000000..110a1fb3
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/restore_account/wallet-password.png differ
diff --git a/_i18n/nl/resources/user-guides/png/restore_from_keys/all-set-up.png b/_i18n/nl/resources/user-guides/png/restore_from_keys/all-set-up.png
new file mode 100644
index 00000000..aebc5e4c
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/restore_from_keys/all-set-up.png differ
diff --git a/_i18n/nl/resources/user-guides/png/restore_from_keys/cancel-opening.png b/_i18n/nl/resources/user-guides/png/restore_from_keys/cancel-opening.png
new file mode 100644
index 00000000..1d987435
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/restore_from_keys/cancel-opening.png differ
diff --git a/_i18n/nl/resources/user-guides/png/restore_from_keys/choose-language.png b/_i18n/nl/resources/user-guides/png/restore_from_keys/choose-language.png
new file mode 100644
index 00000000..d49f8ffa
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/restore_from_keys/choose-language.png differ
diff --git a/_i18n/nl/resources/user-guides/png/restore_from_keys/choose-restore.png b/_i18n/nl/resources/user-guides/png/restore_from_keys/choose-restore.png
new file mode 100644
index 00000000..fbba0bb0
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/restore_from_keys/choose-restore.png differ
diff --git a/_i18n/nl/resources/user-guides/png/restore_from_keys/daemon-settings.png b/_i18n/nl/resources/user-guides/png/restore_from_keys/daemon-settings.png
new file mode 100644
index 00000000..0f70dee0
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/restore_from_keys/daemon-settings.png differ
diff --git a/_i18n/nl/resources/user-guides/png/restore_from_keys/restore-wallet.png b/_i18n/nl/resources/user-guides/png/restore_from_keys/restore-wallet.png
new file mode 100644
index 00000000..20b4c3b7
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/restore_from_keys/restore-wallet.png differ
diff --git a/_i18n/nl/resources/user-guides/png/restore_from_keys/wallet-password.png b/_i18n/nl/resources/user-guides/png/restore_from_keys/wallet-password.png
new file mode 100644
index 00000000..bed1c313
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/restore_from_keys/wallet-password.png differ
diff --git a/_i18n/nl/resources/user-guides/png/solo_mine_GUI/01.PNG b/_i18n/nl/resources/user-guides/png/solo_mine_GUI/01.PNG
new file mode 100644
index 00000000..37493162
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/solo_mine_GUI/01.PNG differ
diff --git a/_i18n/nl/resources/user-guides/png/solo_mine_GUI/02.PNG b/_i18n/nl/resources/user-guides/png/solo_mine_GUI/02.PNG
new file mode 100644
index 00000000..1f576566
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/solo_mine_GUI/02.PNG differ
diff --git a/_i18n/nl/resources/user-guides/png/solo_mine_GUI/03.PNG b/_i18n/nl/resources/user-guides/png/solo_mine_GUI/03.PNG
new file mode 100644
index 00000000..ac259e59
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/solo_mine_GUI/03.PNG differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_binary-cmd-cd.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_binary-cmd-cd.png
new file mode 100644
index 00000000..8fb3b91e
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_binary-cmd-cd.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_binary-cmd-certutil.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_binary-cmd-certutil.png
new file mode 100644
index 00000000..935446eb
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_binary-cmd-certutil.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_binary-cmd-launch.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_binary-cmd-launch.png
new file mode 100644
index 00000000..8c2919f1
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_binary-cmd-launch.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_binary-getmonero-save-file.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_binary-getmonero-save-file.png
new file mode 100644
index 00000000..2b84180c
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_binary-getmonero-save-file.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_binary-getmonero-save-location.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_binary-getmonero-save-location.png
new file mode 100644
index 00000000..fc02f962
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_binary-getmonero-save-location.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_binary-getmonero-windowsfiles.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_binary-getmonero-windowsfiles.png
new file mode 100644
index 00000000..36adfc6e
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_binary-getmonero-windowsfiles.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_binary-word-cmd-compare.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_binary-word-cmd-compare.png
new file mode 100644
index 00000000..057d9c5c
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_binary-word-cmd-compare.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_binary-word-hashfile.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_binary-word-hashfile.png
new file mode 100644
index 00000000..06917e0a
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_binary-word-hashfile.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_getkey-rightclick.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_getkey-rightclick.png
new file mode 100644
index 00000000..58a8d1f7
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_getkey-rightclick.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_getkey-savefilename.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_getkey-savefilename.png
new file mode 100644
index 00000000..64be96cf
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_getkey-savefilename.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_getmonero-hashes-savefilename.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_getmonero-hashes-savefilename.png
new file mode 100644
index 00000000..d47c404c
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_getmonero-hashes-savefilename.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_getmonero-hasheslink.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_getmonero-hasheslink.png
new file mode 100644
index 00000000..90100511
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_getmonero-hasheslink.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_getmonero-hashespage-rightclick.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_getmonero-hashespage-rightclick.png
new file mode 100644
index 00000000..6b8d86c9
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_getmonero-hashespage-rightclick.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-components.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-components.png
new file mode 100644
index 00000000..2217caef
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-components.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-install-complete.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-install-complete.png
new file mode 100644
index 00000000..49f23de2
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-install-complete.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-install-finish.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-install-finish.png
new file mode 100644
index 00000000..6f1b5bea
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-install-finish.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-install-language.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-install-language.png
new file mode 100644
index 00000000..94796396
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-install-language.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-install-security.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-install-security.png
new file mode 100644
index 00000000..0a056dfb
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-install-security.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-install-welcome.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-install-welcome.png
new file mode 100644
index 00000000..da4313b5
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-install-welcome.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-install.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-install.png
new file mode 100644
index 00000000..21466e18
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-install.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-launch.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-launch.png
new file mode 100644
index 00000000..ac58bea6
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-launch.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-site-donation.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-site-donation.png
new file mode 100644
index 00000000..1748fb71
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-site-donation.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-site-downloadbutton.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-site-downloadbutton.png
new file mode 100644
index 00000000..64525563
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-site-downloadbutton.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-site-savefile-location.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-site-savefile-location.png
new file mode 100644
index 00000000..31a3924d
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-site-savefile-location.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-site-savefile-openfolder.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-site-savefile-openfolder.png
new file mode 100644
index 00000000..a51893db
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-site-savefile-openfolder.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-site-savefile.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-site-savefile.png
new file mode 100644
index 00000000..75bd79d7
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_gpg4win-site-savefile.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_hashes-getmonero-rightclick.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_hashes-getmonero-rightclick.png
new file mode 100644
index 00000000..1452776b
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_hashes-getmonero-rightclick.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_hashes-getmonero-savename.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_hashes-getmonero-savename.png
new file mode 100644
index 00000000..8bbd7995
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_hashes-getmonero-savename.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_hashes-kleo-badsig.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_hashes-kleo-badsig.png
new file mode 100644
index 00000000..8a89f0ab
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_hashes-kleo-badsig.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_hashes-kleo-goodsig.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_hashes-kleo-goodsig.png
new file mode 100644
index 00000000..ea92fef4
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_hashes-kleo-goodsig.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_hashes-kleo-verify-button-filename.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_hashes-kleo-verify-button-filename.png
new file mode 100644
index 00000000..0a021ca8
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_hashes-kleo-verify-button-filename.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_hashes-kleo-verify-button.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_hashes-kleo-verify-button.png
new file mode 100644
index 00000000..852a2948
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_hashes-kleo-verify-button.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-certify-fingerprint.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-certify-fingerprint.png
new file mode 100644
index 00000000..713cc08b
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-certify-fingerprint.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-certify-finish.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-certify-finish.png
new file mode 100644
index 00000000..aa760389
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-certify-finish.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-certify-forself.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-certify-forself.png
new file mode 100644
index 00000000..5ad6ae59
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-certify-forself.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-certify-pinentry.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-certify-pinentry.png
new file mode 100644
index 00000000..6184e406
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-certify-pinentry.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-decryptverifybutton.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-decryptverifybutton.png
new file mode 100644
index 00000000..3a5e0c6d
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-decryptverifybutton.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-firstrun-createkeydetails.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-firstrun-createkeydetails.png
new file mode 100644
index 00000000..6bc04035
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-firstrun-createkeydetails.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-firstrun-createkeys-pinentry.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-firstrun-createkeys-pinentry.png
new file mode 100644
index 00000000..3d29e1d2
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-firstrun-createkeys-pinentry.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-firstrun-createkeysnow.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-firstrun-createkeysnow.png
new file mode 100644
index 00000000..c9509ee6
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-firstrun-createkeysnow.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-firstrun-import-location.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-firstrun-import-location.png
new file mode 100644
index 00000000..1ecb720b
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-firstrun-import-location.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-firstrun-importkey.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-firstrun-importkey.png
new file mode 100644
index 00000000..dfc56298
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-firstrun-importkey.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-firstrun-keycreate-success.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-firstrun-keycreate-success.png
new file mode 100644
index 00000000..31292975
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-firstrun-keycreate-success.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-firstrun-startverifyprocess.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-firstrun-startverifyprocess.png
new file mode 100644
index 00000000..dfe905bc
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-firstrun-startverifyprocess.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-firstrun-verifykeydetails.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-firstrun-verifykeydetails.png
new file mode 100644
index 00000000..63b300d1
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-firstrun-verifykeydetails.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-launch.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-launch.png
new file mode 100644
index 00000000..fd12e487
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_kleopatra-launch.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_verify-selecthashesfile-rightclick.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_verify-selecthashesfile-rightclick.png
new file mode 100644
index 00000000..4e3e7aa8
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_verify-selecthashesfile-rightclick.png differ
diff --git a/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_verify-successfulverify.png b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_verify-successfulverify.png
new file mode 100644
index 00000000..1320ca7a
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/verify_binary_windows_beginner/verify-win_verify-successfulverify.png differ
diff --git a/_i18n/nl/resources/user-guides/png/view-only/Success.png b/_i18n/nl/resources/user-guides/png/view-only/Success.png
new file mode 100644
index 00000000..4aedb694
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/view-only/Success.png differ
diff --git a/_i18n/nl/resources/user-guides/png/view-only/create-view-only.png b/_i18n/nl/resources/user-guides/png/view-only/create-view-only.png
new file mode 100644
index 00000000..f63adccd
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/view-only/create-view-only.png differ
diff --git a/_i18n/nl/resources/user-guides/png/view-only/settings.png b/_i18n/nl/resources/user-guides/png/view-only/settings.png
new file mode 100644
index 00000000..4d820969
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/view-only/settings.png differ
diff --git a/_i18n/nl/resources/user-guides/png/view-only/wallet-password.png b/_i18n/nl/resources/user-guides/png/view-only/wallet-password.png
new file mode 100644
index 00000000..27c9a45f
Binary files /dev/null and b/_i18n/nl/resources/user-guides/png/view-only/wallet-password.png differ
diff --git a/_i18n/nl/resources/user-guides/prove-payment.md b/_i18n/nl/resources/user-guides/prove-payment.md
new file mode 100644
index 00000000..ec848846
--- /dev/null
+++ b/_i18n/nl/resources/user-guides/prove-payment.md
@@ -0,0 +1,86 @@
+{% assign version = '1.1.0' | split: '.' %}
+{% include disclaimer.html translated="true" version=page.version %}
+### Betalingen bewijzen
+
+Wanneer iemand naar wie je geld hebt gestuurd beweert dat de betaling niet is uitgevoerd, moet je kunnen bewijzen dat je hebt betaald.
+
+Met Bitcoin wordt dit meestal gedaan door de transactie-ID op te zoeken waarbij de bron- en doeladressen
+en het betaalde bedrag worden weergegeven.
+
+Monero is echter vertrouwelijk, dus die informatie is niet openbaar beschikbaar op de blockchain. Er zijn dus iets meer
+stappen nodig.
+
+Om aan Charlie te bewijzen dat ze een betaling heeft gedaan aan Bob moet Alice drie gegevens aan Charlie laten zien:
+
+- de transactie-ID, net als bij Bitcoin
+- het adres van Bob, net als bij Bitcoin
+- de transactiesleutel, een nieuwe uitvinding bij Monero en andere Cryptonote-coins
+
+Toen Alice de transactie uitvoerde, is er automatisch een sleutel speciaal voor deze transactie gegenereerd.
+
+#### Opdrachtregel
+
+Alice kan deze sleutel als volgt opvragen in monero-wallet-cli (voorheen simplewallet):
+
+> get_tx_key TXID
+
+Daarbij voert Alice haar transactie-ID in in plaats van TXID. Als het goed is, wordt de eenmalige transactiesleutel
+weergegeven.
+
+Dit werkt alleen als monero-wallet-cli is ingesteld op het bewaren van transactiesleutels. Controleer dit als volgt:
+
+> set
+
+Stel het in op 1 als de instelling 0 is:
+
+> set store-tx-info 1
+
+#### Grafische interface
+
+Alice kan haar monero-wallet-gui openen en haar transactiedetails bekijken op de pagina Geschiedenis:
+
+![Geschiedenis](png/prove-payment/history.png)
+
+Hier kan ze de transactie-ID en het adres van Bob kopiren door erop te klikken.
+Vervolgens kan ze op `P` klikken voor het bewijs van een betaling (de transactiesleutel):
+
+![Bewijs van betaling](png/prove-payment/payment-proof.png)
+
+
+---
+
+Nu kan Alice de transactiesleutel, de transactie-ID en het adres van Bob naar Charlie sturen.
+
+Opmerking: als het om meerdere transacties gaat, moeten deze stappen worden herhaald voor elke transactie.
+
+### Betalingen controleren
+
+Nu heeft Charlie die drie gegevens ontvangen en wil hij controleren of Alice de waarheid vertelt. Daarvoor heeft hij een bijgewerkte
+blockchain nodig.
+
+#### Opdrachtregel
+
+Charlie typt het volgende in monero-wallet-cli:
+
+> check_tx_key TXID SLEUTEL ADRES
+
+Daarbij vult hij de door Alice verstrekte gegevens in plaats van de variabelen in. monero-wallet-cli gebruikt de transactiesleutel
+om de transactie te ontsleutelen en geeft weer hoeveel in deze transactie naar dit adres is verzonden. Uiteraard
+zal Charlie bij Bob willen navragen of het adres inderdaad van hem is, net als bij Bitcoin.
+
+#### Grafische interface
+
+Charlie opent monero-wallet-gui en gaat naar de pagina Geavanceerd > Bewijzen/controleren om de gegevens van Alice in te vullen in het gedeelte Transactie controleren.
+
+![Check payment](png/prove-payment/check-payment.png)
+
+Vervolgens klikt Charlie op Controleren om te zien hoeveel door deze transactie naar dit adres is verzonden, en hoeveel bevestigingen de transactie heeft.
+
+![Betaling gecontroleerd](png/prove-payment/payment-checked.png)
+
+
+---
+
+Uiteraard zal Charlie bij Bob willen navragen of het adres inderdaad van hem is, net als bij Bitcoin.
+
+Opmerking: als het om meerdere transacties gaat, moeten deze stappen worden herhaald voor elke transactie.
diff --git a/_i18n/nl/resources/user-guides/remote_node_gui.md b/_i18n/nl/resources/user-guides/remote_node_gui.md
new file mode 100644
index 00000000..2430b190
--- /dev/null
+++ b/_i18n/nl/resources/user-guides/remote_node_gui.md
@@ -0,0 +1,11 @@
+{% assign version = '1.2.0' | split: '.' %}
+{% include disclaimer.html translated="true" version=page.version %}
+## Een node vinden
+Eerst moet je natuurlijk een node vinden om verbinding mee te maken! [moneroworld.com](https://moneroworld.com/#nodes) biedt uitstekende hulpmiddelen voor het vinden van nodes. Een van de eenvoudigste methoden
+is een node van moneroworld zelf gebruiken, maar ze bieden ook een hulpmiddel aan voor het vinden van willekeurige nodes.
+
+## Verbinding maken met de node vanuit de grafische interface
+Nadat je het wachtwoord voor je portemonnee hebt ingevoerd, wordt een scherm weergegeven waarin de optie "Gebruik aangepaste instellingen" staat. Klik op die optie. Dan word je
+doorgeleid naar de pagina "Instellingen > Node" van de grafische interface (GUI). Hier kun je de optie 'Externe node' kiezen. Dan zie je vier tekstvakken met de labels "Address", "Port", "Daemon username" en "Daemon password". Voer het adres in van de node waarmee je verbinding wilt maken. Het adres kan eruitzien als `node.moneroworld.com`, of het is een IP-adres. Vul vervolgens in het vak "Poort" de poort van de node in. De standaardpoort is `18081`, maar als je een willekeurige node gebruikt, kan die node een andere poort gebruiken. De poort voor node.moneroworld.com is 18089. Eventueel kun je een gebruikersnaam en wachtwoord invullen als dat nodig is voor deze node.
+### Het scherm hoort er ongeveer zo uit te zien
+
diff --git a/_i18n/nl/resources/user-guides/restore_account.md b/_i18n/nl/resources/user-guides/restore_account.md
new file mode 100644
index 00000000..3de4108e
--- /dev/null
+++ b/_i18n/nl/resources/user-guides/restore_account.md
@@ -0,0 +1,53 @@
+{% assign version = '1.1.0' | split: '.' %}
+{% include disclaimer.html translated="true" version=page.version %}
+## Besturingssystemen: Windows, Linux, Mac
+
+- Neem je hersteltekst (zie @mnemonic-seed) erbij die je hebt opgeslagen bij het maken van je oude Monero-portemonnee (zie @wallet).
+
+### Software: monero-wallet-cli
+
+- Open een opdrachtregel en ga naar het station en de directory waar monero-wallet-cli staat
+
+- Typ het volgende op de opdrachtregel: `monero-wallet-cli --restore-deterministic-wallet`
+
+- Nadat je op Enter hebt gedrukt, wordt er gevraagd een bestandsnaam voor je portemonnee op te geven. Geef je portemonnee een nieuwe naam. Het maakt niet uit welke naam.
+
+- Druk opnieuw op Enter. Er wordt gevraagd naar een wachtwoord. Geef je portemonnee een nieuw, lang wachtwoord.
+
+- Druk opnieuw op Enter. Er wordt gevraagd het wachtwoord te herhalen.
+
+- Druk opnieuw op Enter. Je wordt gevraagd de hersteltekst van 25 woorden die je eerder hebt opgezocht in te voeren.
+
+- Vervolgens wordt er gevraagd of je een herstelpunt wilt opgeven: "Restore from specific blockchain height (optional, default 0):" Het herstelproces begint standaard bij het begin van de Monero-blockchain. Als je geen specifieke hoogte van de blockchain weet, druk je gewoon op Enter. (Als je een herstelpunt opgeeft, wordt het herstelproces gestart vanaf die specifieke hoogte. Hiermee bespaar je tijd bij het opzoeken, als je weet op welke hoogte van de blockchain er voor het eerst geld is overgemaakt naar dit specifieke account.)
+
+Nadat je de hersteltekst van 25 woorden hebt ingevoerd en een specifieke hoogte van de blockchain hebt opgegeven, wordt het openbare adres van je oude portemonnee gegenereerd en begint het vernieuwingsproces automatisch. (Even geduld alsjeblieft, want het vernieuwen kan een tijdje duren.)
+
+### Software: monero-wallet-gui
+
+Start `monero-wallet-gui`. Als dit de eerste keer is dat je het start, ga dan naar de volgende stap. Zo niet, klik dan op `Annuleren`:
+
+![openen annuleren](png/restore_account/cancel-opening.png)
+
+Selecteer de gewenste taal `Nederlands`:
+
+![taal kiezen](png/restore_account/choose-language.png)
+
+Klik op `Een portemonnee herstellen met uw hersteltekst of sleutels`:
+
+![herstellen kiezen](png/restore_account/choose-restore.png)
+
+Zorg dat `Herstel met hersteltekst` is ingeschakeld, geef een name en opslaglocatie op voor de portemonnee en vul het veld `Voer uw hersteltekst van 25 (of 24) woorden in` in. Eventueel kun je een `Herstelpunt (optioneel)` opgeven, zodat er niet hoeft te worden gezocht in oudere blokken. Klik vervolgens op de pijl naar rechts:
+
+![portemonnee herstellen](png/restore_account/restore-wallet.png)
+
+Geef je portemonnee op de volgende pagina een sterk wachtwoord en bevestig dit voordat je op de pijl naar rechts klikt:
+
+![wachtwoord portemonnee](png/restore_account/wallet-password.png)
+
+Geef de instellingen voor je node op en klik op de pijl naar rechts:
+
+![instellingen node](png/restore_account/daemon-settings.png)
+
+Klik op `GEBRUIK MONERO` om je herstelde portemonnee te gebruiken:
+
+![klaar is kees](png/restore_account/all-set-up.png)
diff --git a/_i18n/nl/resources/user-guides/restore_from_keys.md b/_i18n/nl/resources/user-guides/restore_from_keys.md
new file mode 100644
index 00000000..5e978433
--- /dev/null
+++ b/_i18n/nl/resources/user-guides/restore_from_keys.md
@@ -0,0 +1,54 @@
+{% assign version = '1.1.0' | split: '.' %}
+{% include disclaimer.html translated="true" version=page.version %}
+### Herstellen met sleutels
+
+Je kunt een portemonnee makkelijk herstellen met je privsleutels. Als je de benodigde gegevens hebt, kun je met deze handleiding je portemonnee volledig herstellen. Je hebt je wachtwoord NIET nodig voor herstellen met sleutels.
+
+Wat je nodig hebt zijn ofwel 3 gegevens uit je portemonnee, ofwel het bestand met de extensie .keys waarin deze gegevens staan, plus het wachtwoord waarmee dit bestand is versleuteld. Je hebt deze 3 onderdelen van je portemonnee nodig:
+
+1. **Adres**
+2. **Geheime bestedingssleutel**
+3. **Geheime alleen-lezen sleutel**
+
+
+#### Opdrachtregel
+
+Voer vervolgens deze opdracht uit:
+
+`./monero-wallet-cli --generate-from-keys Nieuwe_Portemonnee.abc`
+
+Vervolgens wordt er gevraagd gegevens in te voeren: het adres, de bestedingssleutel, de alleen-lezen sleutel en het nieuwe wachtwoord voor de opnieuw gegenereerde portemonnee.
+
+Als je dit uitvoert met de juiste parameters, worden je portemonneebestanden opnieuw voor je gegenereerd en kun je een nieuw wachtwoord instellen.
+
+Als je problemen tegenkomt, kun je `./monero-wallet-cli --help` uitvoeren om te zien welke opties beschikbaar zijn bij het starten van een portemonnee. Nadat je de portemonnee hebt geopend, kun je de opdracht `help` uitvoeren om de opdrachten weer te geven die beschikbaar zijn in de portemonnee.
+
+#### Grafische interface
+
+Start `monero-wallet-gui`. Als dit de eerste keer is dat je het start, ga dan naar de volgende stap. Zo niet, klik dan op `Annuleren`:
+
+![openen annuleren](png/restore_from_keys/cancel-opening.png)
+
+Selecteer de gewenste taal `Nederlands`:
+
+![taal kiezen](png/restore_from_keys/choose-language.png)
+
+Klik op `Een portemonnee herstellen met uw hersteltekst of sleutels`:
+
+![herstellen kiezen](png/restore_from_keys/choose-restore.png)
+
+Selecteer `Herstel met sleutels`, geef een name en opslaglocatie op voor de portemonnee en vul de velden `Adres van account (openbaar)`, `Alleen-lezen sleutel (priv)` en `Bestedingssleutel (priv)` in. Eventueel kun je een `Herstelpunt (optioneel)` opgeven, zodat er niet hoeft te worden gezocht in oudere blokken. Klik vervolgens op de pijl naar rechts:
+
+![portemonnee herstellen](png/restore_from_keys/restore-wallet.png)
+
+Geef je portemonnee op de volgende pagina een sterk wachtwoord en bevestig dit voordat je op de pijl naar rechts klikt:
+
+![wachtwoord portemonnee](png/restore_from_keys/wallet-password.png)
+
+Geef de instellingen voor je node op en klik op de pijl naar rechts:
+
+![instellingen node](png/restore_from_keys/daemon-settings.png)
+
+Klik op `GEBRUIK MONERO` om je herstelde portemonnee te gebruiken:
+
+![klaar is kees](png/restore_from_keys/all-set-up.png)
diff --git a/_i18n/nl/resources/user-guides/securely_purchase.md b/_i18n/nl/resources/user-guides/securely_purchase.md
new file mode 100644
index 00000000..30ee7b65
--- /dev/null
+++ b/_i18n/nl/resources/user-guides/securely_purchase.md
@@ -0,0 +1,83 @@
+{% assign version = '1.1.0' | split: '.' %}
+{% include disclaimer.html translated="true" version=page.version %}
+## Monero kopen en veilig opslaan
+
+Dit is een handleiding voor het aanschaffen en veilig opslaan van Monero, geschreven in juni 2017.
+
+#### Stap 1. Koop Bitcoin
+
+Je kunt op allerlei manieren Bitcoin kopen. Twee min of meer betrouwbare bedrijven zijn op dit moment Xapo en Coinbase . Hiervoor is het nodig om een kopie van je identiteitsbewijs (paspoort, rijbewijs of identiteitskaart) te uploaden. Verificatie van je identiteit kan 2 tot 10 dagen duren (of langer). Controleer de reputatie van een exchange voordat je een grote aankoop doet. Xapo gebruikt elektronische overboekingen en Coinbase gebruikt bankoverschrijvingen (ACH in de VS). Xapo zal waarschijnlijk sneller werken dan Coinbase. Coinbase biedt ook de mogelijkheid om "instant" kleine bedragen te kopen met een betaalpas, maar rekent hoge kosten voor deze optie. Nadat je Bitcoin hebt gekocht, kun je ze omwisselen voor Monero.
+
+#### Stap 2. Download en maak een papieren portemonnee (paper wallet) op een veilige computer die niet verbonden is met internet.
+
+Download de *paper wallet generator* op https://moneroaddress.org en kopieer deze naar een USB-stick. (Directe link: https://github.com/moneromooo-monero/monero-wallet-generator/archive/master.zip).
+
+Pak de *paper wallet generator* uit en open deze (monero-wallet-generator.html) in een browser op een offline computer die nog nooit is gebruikt, of waarop het besturingssysteem opnieuw is genstalleerd.
+
+De papieren portemonnee bestaat uit vier belangrijke onderdelen:
+
+Openbaar Monero-adres
+Het openbare adres wordt gebruikt om geld in de portemonnee te ontvangen. Je kunt dit adres aan iedereen geven die jou wil betalen.
+
+Monero-hersteltekst
+Met de hersteltekst wordt de hele portemonnee opgeslagen op een manier die begrijpelijk is voor mensen. Dit is alles wat je nodig hebt om later je portemonnee te herstellen.
+
+Priv-bestedingssleutel
+De priv-bestedingssleutel wordt gebruikt om geld vanuit de portemonnee te verzenden.
+
+Priv alleen-lezen sleutel
+De priv alleen-lezen sleutel is bedoeld om te bekijken welke transacties worden ontvangen door de portemonnee. Deze wordt vaak gebruikt om een alleen-lezen portemonnee voor *cold storage* (koude opslag) te maken, zodat je direct op de blockchain kunt zien welke transacties daar binnenkomen.
+
+Op dit punt heb je allerlei opties. Je kunt de portemonnee op papier afdrukken, opslaan als een PDF of een tekstbestand op een USB-stick, op een cd of dvd branden enzovoort. Het wordt aangeraden om tenminste twee of drie exemplaren op verschillende plekken op te slaan. Versleutel alles met een sterk wachtwoord als je de portemonnee digitaal bewaart. Als je de portemonnee op papier bewaart, laat hem dan niet zien aan iemand die je hersteltekst van 25 woorden kan onthouden of zonder je toestemming een foto van de portemonnee kan maken. Iemand een foto van de portemonnee sturen is hetzelfde als al het geld weggeven.
+
+Welke methode je ook kiest, zorg ervoor dat er geen exemplaar van de Monero-portemonnee achterblijft op het apparaat dat je hebt gebruikt. Eventueel moet je de Monero-portemonnee veilig verwijderen als je hem op een schijf hebt opgeslagen, of controleren of je printer geen exemplaar heeft opgeslagen in zijn geheugen.
+
+*Als je de toegang tot je papieren Monero-portemonnee kwijtraakt, ben je de Monero die erop staan voorgoed kwijt. Niemand kan je helpen om ze terug te krijgen!*
+
+#### Kanttekening
+Je kunt een XMR-hersteltekst versleutelen met:
+https://xmr.llcoins.net/
+Download de html-pagina en breng die naar je offline computer. Vink de optie "Encrypt/Decrypt Mnemonic Seed" aan en gebruik "CN Add" met een degelijk wachtwoord. Met dank aan manicminer5.
+
+
+
+#### Stap 3. Wissel je Bitcoin om voor Monero en laat je Monero naar je papieren portemonnee sturen.
+
+Ga op je computer met een internetverbinding naar www.shapeshift.io. Kies "Bron: Bitcoin", "Doel: Monero" en "Snel".
+
+Klik op Doorgaan.
+
+Je Monero adres (bestemmingsadres)
+Plak hier het openbare Monero-adres uit je papieren portemonnee in het tekstvak waar "Je Monero adres" staat. Maar wacht even: je openbare Monero-adres staat op een offline computer (toch?) dus je kunt het niet kopiren en plakken. Kopieer het met de hand, of kopieer alleen het openbare adres naar een lege USB-stick.
+
+Je Bitcoin adres voor het omgewisselde bedrag
+Voer een Bitcoin-adres in dat eigendom van jou is, zodat je daar een terugbetaling kunt ontvangen als er een probleem is met de transactie. Het is erg belangrijk dat je een openbaar Bitcoin-adres invoert dat eigendom van jou is en waar je geld kunt ontvangen. Bij Xapo en Coinbase heet dit een Receive Address (ontvangstadres). Het kan af en toe gewijzigd worden.
+
+Payment Id
+Laat Payment Id (Betalings-ID) leeg als je Monero naar je eigen portemonnee of papieren portemonnee verzendt.
+
+Ga akkoord met de voorwaarden en klik op de schuifknop "Bewaren Adres?" om er een herbruikbaar adres van te maken.
+
+Klik op "Transactie starten".
+
+Stortingsadres (het openbare Bitcoin-adres van Shapeshift.io dat alleen is bestemd voor het ontvangen van je geld)
+In het nieuwe scherm dat wordt weergegeven kopieer je het stortingsadres onder "Verzonden naar dit adres" naar je klembord (selecteer het en druk op Ctrl-C of klik op Bewerken - Plakken). Via dit adres verzend je Bitcoin van Xapo/Coinbase naar Shapeshift.io.
+
+Ga naar je Xapo- of Circle-account en zoek de knop Transfer of Send op. Plak het Bitcoin-stortingsadres in het veld Destination en voer in hoeveel Bitcoin je wilt laten omwisselen voor Monero. Het bedrag moet binnen het door Shapeshift.io opgegeven bereik voor Minimaal inlegbedrag en Maximaal inlegbedrag vallen. Klik op Send en autoriseer indien nodig de transactie.
+
+Nadat het verzenden is gestart door Xapo/Coinbase, moet je wachten terwijl de transactie op de Bitcoin-blockchain wordt vastgelegd en bevestigd. Dit kan minuten of uren duren. Je kunt controleren of de betaling is verzonden door het stortingsadres bij Shapeshift.io op te zoeken op blockchain.info. Daar wordt je transactie naar Shapeshift.io weergegeven.
+
+Nadat je Bitcoin-transactie is bevestigd, begint Shapeshift.io met het omwisselen van Bitcoin (BTC) voor Monero (XMR) op een van de exchanges. Wanneer dat klaar is, wordt je Monero verzonden naar het adres van je papieren portemonnee voor cold storage. Dit kan minuten tot uren duren. Neem contact op met Shapeshift.io als er een probleem is. Hun ondersteuning is goed.
+
+Wanneer de transactie volgens de webpagina van Shapeshift.io is voltooid, zou je Monero in je papieren portemonnee moeten hebben.
+
+
+### Opmerkingen en het verifiren van je saldo
+Omdat de Monero-blockchain vertrouwelijk en niet volgbaar is, kun je niet je openbare Monero-adres opzoeken om te bevestigen dat het geld is aangekomen, zoals je met Bitcoin zou kunnen doen. Dit is goed voor je privacy, maar minder gemakkelijk.
+
+Je hebt een alleen-lezen portemonnee nodig om veilig te controleren of je geld is aangekomen in je portemonnee. Daarvoor heb je die alleen-lezen sleutel bewaard. Zie de handleiding voor het maken van een alleen-lezen portemonnee: [Een alleen-lezen portemonnee maken]({{site.baseurl}}/resources/user-guides/view_only.html)
+
+Om te controleren of het geld *nog steeds in* je portemonnee zit en niet uitgegeven is, moet je een 'koude' portemonnee (cold wallet) maken met je hersteltekst (voor al je geld) op een offline computer waar een bijgewerkt exemplaar van de Monero-blockchain op staat. Wanneer je daarmee klaar bent, moet je de portemonnee veilig wissen of met internet verbinden zodat het een 'hot wallet' wordt.
+
+
+
diff --git a/_i18n/nl/resources/user-guides/solo_mine_GUI.md b/_i18n/nl/resources/user-guides/solo_mine_GUI.md
new file mode 100644
index 00000000..4cbdceeb
--- /dev/null
+++ b/_i18n/nl/resources/user-guides/solo_mine_GUI.md
@@ -0,0 +1,17 @@
+{% assign version = '1.1.0' | split: '.' %}
+{% include disclaimer.html translated="true" version=page.version %}
+Het is heel makkelijk om solo te minen met de officile grafische interface (GUI). Als je het nog niet gedaan hebt, ga dan naar de pagina Monero-downloads en download de officile GUI voor je besturingssysteem. Voer de installatie uit en wacht terwijl Monero wordt gesynchroniseerd met het netwerk. Als het goed is, staat er "Verbonden" in de linkerbenedenhoek.
+
+
+
+Klik op het tabblad "Geavanceerd". Dan verschijnen er verschillende opties. Klik hier op het subtabblad "Minen".
+
+
+
+Daar vind je een optie om te beginnen met minen. Eventueel kun je aanpassen met hoeveel threads je minet. De meest effectieve instelling is de cache van je CPU gedeeld door 2. Hiervoor moet je de specificaties van je CPU opzoeken op de website van de fabrikant. Laat het aantal threads op 1 staan als je het niet zeker weet. Klik op de knop "Start het minen".
+
+
+
+Je bent nu aan het minen voor het netwerk, zoals je onderaan de afbeelding kunt zien. In dit voorbeeld draagt je computer 23 H/s (hashes per seconde) bij aan het Monero-netwerk. Minen helpt het netwerk te beveiligen, en misschien heb je zoveel geluk dat je een beloning voor het beschermen van het netwerk krijgt.
+
+Als je wilt stoppen met minen, klik je gewoon op de knop "Stop het minen".
diff --git a/_i18n/nl/resources/user-guides/verification-allos-advanced.md b/_i18n/nl/resources/user-guides/verification-allos-advanced.md
new file mode 100644
index 00000000..24f06b19
--- /dev/null
+++ b/_i18n/nl/resources/user-guides/verification-allos-advanced.md
@@ -0,0 +1,185 @@
+{% assign version = '1.1.0' | split: '.' %}
+{% include disclaimer.html translated="true" version=page.version %}
+# Binary verifiren: Linux, Mac of Windows via opdrachtregel (geavanceerd)
+
+Voordat je de Monero-software uitpakt, installeert en gebruikt, moet je de binaire bestanden van Monero verifiren. Dit is de enige manier om er zeker van te zijn dat je de officile Monero-software gebruikt. Als je een onecht Monero-binary ontvangt (bijvoorbeeld via phishing of een *man-in-the-middle attack*), voorkomt deze methode dat je er gebruik van maakt.
+
+Het Monero-team stelt een cryptografisch ondertekende lijst beschikbaar met alle [SHA256](https://en.wikipedia.org/wiki/SHA-2)-hashes, om de integriteit van de binaries te garanderen. Als er met het gedownloade binaire bestand is geknoeid, levert het een [andere hash](https://nl.wikipedia.org/wiki/Hashfunctie) op dan in de lijst.
+
+Dit is een geavanceerde handleiding voor de besturingssystemen Linux, Mac en Windows. Hierbij wordt de opdrachtregel gebruikt. We leggen stap voor stap uit hoe je de vereiste software installeert, de ondertekeningssleutel importeert, de benodigde bestanden downloadt en uiteindelijk verifieert dat je binaire bestand authentiek is.
+
+## Inhoud
+
+### [1. GnuPG installeren](#1-installing-gnupg)
+### [2. Ondertekeningssleutel verifiren en importeren](#2-verify-and-import-signing-key)
+ + [2.1. Ondertekeningssleutel ophalen](#21-get-signing-key)
+ + [2.2. Ondertekeningssleutel verifiren](#22-verify-signing-key)
+ + [2.3. Ondertekeningssleutel importeren](#23-import-signing-key)
+### [3. Hashbestand downloaden en verifiren](#3-download-and-verify-hash-file)
+ + [3.1. Hashbestand ophalen](#31-get-hash-file)
+ + [3.2. Hashbestand verifiren](#32-verify-hash-file)
+### [4. Binary downloaden en verifiren](#4-download-and-verify-binary)
+ + [4.1. Monero-binary ophalen](#41-get-monero-binary)
+ + [4.2. Binary verifiren op Linux of Mac](#42-binary-verification-on-linux-or-mac)
+ + [4.3. Binary verifiren op Windows](#43-binary-verification-on-windows)
+
+## 1. GnuPG installeren
+
++ Op Windows ga je naar de [downloadpagina voor Gpg4win](https://gpg4win.org/download.html) en volg je de instructies voor het installeren.
+
++ Op een Mac ga je naar de [downloadpagina voor Gpgtools](https://gpgtools.org/) en volg je de instructies voor het installeren.
+
++ Op Linux is GnuPG standaard genstalleerd.
+
+## 2. Ondertekeningssleutel verifiren en importeren
+
+In dit gedeelte leggen we uit hoe je de Monero-ondertekeningssleutel ophaalt, controleert of deze correct is en de sleutel importeert in GnuPG.
+
+### 2.1. Ondertekeningssleutel ophalen
+
+Op Windows of een Mac: ga naar [Fluffypony's GPG-sleutel](https://raw.githubusercontent.com/monero-project/monero/master/utils/gpg_keys/fluffypony.asc), waarmee hij de Monero-binaries ondertekent, en sla de pagina op als `fluffypony.asc` in je homedirectory.
+
+Op Linux kun je de ondertekeningssleutel van Fluffypony downloaden door de volgende opdracht op te geven:
+
+```
+wget -O fluffypony.asc https://raw.githubusercontent.com/monero-project/monero/master/utils/gpg_keys/fluffypony.asc
+```
+
+### 2.2. Ondertekeningssleutel verifiren
+
+Op alle besturingssystemen kun je de vingerafdruk van `fluffypony.asc` controleren door de volgende opdracht te geven in een terminal:
+
+```
+gpg --keyid-format long --with-fingerprint fluffypony.asc
+```
+
+
+Controleer of de vingerafdruk overeenkomt:
+
+```
+pub 2048R/7455C5E3C0CDCEB9 2013-04-08 Riccardo Spagni
+ Key fingerprint = BDA6 BD70 42B7 21C4 67A9 759D 7455 C5E3 C0CD CEB9
+sub 2048R/55432DF31CCD4FCD 2013-04-08
+```
+
+Als de vingerafdruk **WEL** overeenkomt, kun je verder gaan.
+
+**GA NIET VERDER** als de vingerafdruk **NIET** overeenkomt. Verwijder dan het bestand `fluffypony.asc` en ga terug naar [paragraaf 2.1](#21-get-signing-key).
+
+### 2.3. Ondertekeningssleutel importeren
+
+Importeer de ondertekeningssleutel in een terminal:
+
+```
+gpg --import fluffypony.asc
+```
+
+Als dit de eerste keer is dat je de sleutel hebt gemporteerd, ziet de uitvoer er als volgt uit:
+
+```
+gpg: key 0x7455C5E3C0CDCEB9: 2 signatures not checked due to missing keys
+gpg: key 0x7455C5E3C0CDCEB9: public key "Riccardo Spagni " importe
+d
+gpg: Total number processed: 1
+gpg: imported: 1
+gpg: no ultimately trusted keys found
+```
+
+Als je de sleutel eerder hebt gemporteerd, ziet de uitvoer er als volgt uit:
+
+```
+gpg: key 0x7455C5E3C0CDCEB9: "Riccardo Spagni " not changed
+gpg: Total number processed: 1
+gpg: unchanged: 1
+```
+
+## 3. Hashbestand downloaden en verifiren
+
+In dit gedeelte leggen we uit hoe je het hashbestand downloadt en de authenticiteit verifieert.
+
+### 3.1. Hashbestand ophalen
+
+Op Windows of een Mac ga je naar het [hashbestand op getmonero.org](https://getmonero.org/downloads/hashes.txt) en sla je de pagina op als `hashes.txt` in je homedirectory.
+
+Op Linux kun je het ondertekende hashbestand downloaden door de volgende opdracht op te geven:
+
+```
+wget -O hashes.txt https://getmonero.org/downloads/hashes.txt
+```
+
+### 3.2. Hashbestand verifiren
+
+Het hashbestand is ondertekend met de sleutel `94B7 38DD 3501 32F5 ACBE EA1D 5543 2DF3 1CCD 4FCD`, een subsleutel van de sleutel `BDA6 BD70 42B7 21C4 67A9 759D 7455 C5E3 C0CD CEB9` (zoals weergegeven in de uitvoer hieronder).
+
+Op alle besturingssystemen kun je de ondertekening van het hasbestand controleren door de volgende opdracht te geven in een terminal:
+
+```
+gpg --verify hashes.txt
+```
+
+Als het bestand authentiek is, ziet de uitvoer er als volgt uit:
+
+```
+gpg: Signature made Thu 05 Apr 2018 06:07:35 AM MDT
+gpg: using RSA key 94B738DD350132F5ACBEEA1D55432DF31CCD4FCD
+gpg: Good signature from "Riccardo Spagni " [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
+```
+
+Als er **Good signature** in de uitvoer staat, zoals in het voorbeeld, kun je verder gaan.
+
+**GA NIET VERDER** als er **BAD signature** in de uitvoer staat. Verwijder dan het bestand `hashes.txt` en ga terug naar [paragraaf 3.1](#31-get-hash-file).
+
+## 4. Binary downloaden en verifiren
+
+In dit gedeelte leggen we uit hoe je de Monero-binary voor je besturingssysteem downloadt, de `SHA256`-hash van je download ophaalt en verifieert dat deze correct is.
+
+### 4.1. Monero-binary ophalen
+
+Op Windows of een Mac ga je naar [getmonero.org](https://getmonero.org/downloads/) en download je het juiste bestand voor je besturingssysteem. Sla het bestand op in je homedirectory. **Pak de bestanden nog niet uit.**
+
+Op Linux kun je de opdrachtregelversie downloaden door de volgende opdracht op te geven:
+
+```
+wget -O monero-linux-x64-v0.12.0.0.tar.bz2 https://downloads.getmonero.org/cli/linux64
+```
+
+### 4.2. Binary verifiren op Linux of Mac
+
+De stappen op zowel Linux als Mac zijn hetzelfde. In een terminal bereken je de `SHA256`-hash van je gedownloade Monero-binary. Als voorbeeld gebruiken we hier het binaire bestand voor 64-bits Linux. Vervang `monero-gui-linux-x64-v0.12.0.0.tar.bz2` door de naam van het binaire bestand dat je hebt gedownload in [paragraaf 4.1](#41-get-monero-binary).
+
+```
+shasum -a 256 monero-gui-linux-x64-v0.12.0.0.tar.bz2
+```
+
+De uitvoer ziet er uit als volgt, maar met verschillende details per binair bestand. Je `SHA256`-hash moet overeenkomen met de hash in het bestand `hashes.txt` van je binaire bestand.
+
+```
+fb0f43387b31202f381c918660d9bc32a3d28a4733d391b1625a0e15737c5388 monero-gui-linux-x64-v0.12.0.0.tar.bz2
+```
+
+Als de hash **WEL** overeenkomt, ben je klaar met deze handleiding! Dan kun je de bestanden uitpakken en installeren.
+
+**GA NIET VERDER** als de hash **NIET** overeenkomt. Verwijder dan de binary die je hebt gedowload en ga terug naar [paragraaf 4.1](#41-get-monero-binary).
+
+### 4.3. Binary verifiren op Windows
+
+In een terminal bereken je de `SHA256`-hash van je gedownloade Monero-binary. Als voorbeeld gebruiken we hier het binaire bestand voor de 64-bits Windows GUI. Vervang `monero-gui-win-x64-v0.12.0.0.zip` door de naam van het binaire bestand dat je hebt gedownload in [paragraaf 4.1](#41-get-monero-binary).
+
+```
+certUtil -hashfile monero-gui-win-x64-v0.12.0.0.zip SHA256
+```
+De uitvoer ziet er uit als volgt, maar met verschillende details per binair bestand. Je `SHA256`-hash moet overeenkomen met de hash in het bestand `hashes.txt` van je binaire bestand.
+
+```
+SHA256 hash of file monero-gui-win-x64-v0.12.0.0.zip:
+4b 9f 31 68 6e ca ad 97 cd b1 75 e6 57 4b f3 07 f8 d1 c4 10 42 78 25 f4 30 4c 21 da 8a ac 18 64
+CertUtil: -hashfile command completed successfully.
+```
+
+Als de hash **WEL** overeenkomt, ben je klaar met deze handleiding! Dan kun je de bestanden uitpakken en installeren.
+
+**GA NIET VERDER** als de hash **NIET** overeenkomt. Verwijder dan de binary die je hebt gedowload en ga terug naar [paragraaf 4.1](#41-get-monero-binary).
diff --git a/_i18n/nl/resources/user-guides/verification-windows-beginner.md b/_i18n/nl/resources/user-guides/verification-windows-beginner.md
new file mode 100644
index 00000000..ef5544cb
--- /dev/null
+++ b/_i18n/nl/resources/user-guides/verification-windows-beginner.md
@@ -0,0 +1,255 @@
+{% assign version = '1.1.0' | split: '.' %}
+{% include disclaimer.html translated="true" version=page.version %}
+Binaries verifiren Windows (beginner)
+
+Voordat je de Monero-software uitpakt, installeert en gebruikt, moet je de binaire bestanden van Monero verifiren. Dit is de enige manier om er zeker van te zijn dat je de officile Monero-binaries gebruikt. Als je een onecht binair bestand ontvangt (bijvoorbeeld via phishing of een *man-in-the-middle attack*), voorkomt deze methode dat je er gebruik van maakt.
+
+Het Monero-team stelt een cryptografisch ondertekende lijst beschikbaar met alle [SHA256](https://en.wikipedia.org/wiki/SHA-2)-hashes, om de integriteit van de binaries te garanderen. Als er met het gedownloade binaire bestand is geknoeid, levert het een [andere hash](https://nl.wikipedia.org/wiki/Hashfunctie) op dan in de lijst.
+
+Dit is een handleiding voor beginners die Windows als besturingssysteem gebruiken. Bijna alle gebruikte software heeft een grafische interface. We leggen stap voor stap uit hoe je de vereiste software installeert, de ondertekeningssleutel importeert, de benodigde bestanden downloadt en uiteindelijk verifieert dat je binaire bestand authentiek is.
+
+## Inhoud
+
+### [1. Gpg4win-installatieprogramma](#1-using-gpg4win-installer)
+ - [1.1. Gpg4win-installatieprogramma ophalen](#11-getting-gpg4win-installer)
+ + [1.1.1. Gpg4win downloaden](#111-download-gpg4win)
+ + [1.1.2. Gpg4win starten](#112-launch-gpg4win)
+ - [1.2. Gpg4win-installatieprogramma gebruiken](#12-use-gpg4win-installer)
+### [2. Ondertekeningssleutel importeren](#2-monero-signing-key)
+ - [2.1. Ondertekeningssleutel downloaden](#21-download-signing-key)
+ - [2.2. Kleopatra initialiseren](#22-initialize-kleopatra)
+ + [2.2.1. Ondertekeningssleutel importeren](#221-import-signing-key)
+ + [2.2.2. Sleutelpaar aanmaken](#222-create-key-pair)
+ - [2.3. Ondertekeningssleutel verifiren](#23-verify-signing-key)
+### [3. Hashbestand verifiren](#3-hash-file-verification)
+ - [3.1. Hashbestand downloaden](#31-download-hash-file)
+ - [3.2. Hashbestand verifiren](#32-verify-hash-file)
+### [4. Binair bestand verifiren](#4-binary-file-verification)
+ - [4.1. Binary downloaden](#41-download-binary)
+ - [4.2. Binary verifiren](#42-verify-binary)
+
+## 1. Gpg4win-installatieprogramma gebruiken
+
+In dit gedeelte leggen we uit hoe je de cryptografische software gebruikt. De hulpmiddelen die je nodig hebt om binaries te verifiren worden niet meegeleverd met Windows. Met het Gpg4win-installatieprogramma kun je deze tools installeren.
+
+### 1.1. Gpg4win-installatieprogramma ophalen
+
+#### 1.1.1. Gpg4win downloaden
+
+Ga in een browser naar [gpg4win.org](https://gpg4win.org) en download het installatieprogramma door op de groene knop te klikken.
+
+![downloadknop gpg4win](png/verify_binary_windows_beginner/verify-win_gpg4win-site-downloadbutton.png)
+
+Er wordt een donatiepagina geopend. Als je niets wilt doneren, selecteer je `$0`. Daarna kun je op `Download` klikken.
+
+![gpg4win site donatie](png/verify_binary_windows_beginner/verify-win_gpg4win-site-donation.png)
+
+Klik op `Bestand opslaan`.
+
+![gpg4win site bestand opslaan](png/verify_binary_windows_beginner/verify-win_gpg4win-site-savefile.png)
+
+Kies een opslaglocatie en klik op `Opslaan`.
+
+![gpg4win site locatie download](png/verify_binary_windows_beginner/verify-win_gpg4win-site-savefile-location.png)
+
+#### 1.1.2. Gpg4win starten
+
+Open de map met het bestand wanneer het downloaden klaar is.
+
+![gpg4win site map openen](png/verify_binary_windows_beginner/verify-win_gpg4win-site-savefile-openfolder.png)
+
+Dubbelklik op het uitvoerbare bestand gpg4win.exe om het te starten.
+
+![gpg4win starten](png/verify_binary_windows_beginner/verify-win_gpg4win-launch.png)
+
+### 1.2. Gpg4win-installatieprogramma gebruiken
+
+Er wordt een scherm met een beveiligingswaarschuwing weergegeven. Klik hier op `Uitvoeren`.
+
+![gpg4win installatie beveiliging](png/verify_binary_windows_beginner/verify-win_gpg4win-install-security.png)
+
+Selecteer je taal en klik op `OK`.
+
+![gpg4win installatie taal](png/verify_binary_windows_beginner/verify-win_gpg4win-install-language.png)
+
+Er wordt een welkomstscherm weergegeven. Klik op `Volgende`.
+
+![gpg4win installatie welkom](png/verify_binary_windows_beginner/verify-win_gpg4win-install-welcome.png)
+
+Nu krijg je een scherm te zien voor het selecteren van onderdelen. Laat in ieder geval `Kleopatra` aangevinkt staan voor deze handleiding. Geef je keuze aan en klik op `Volgende`.
+
+![gpg4win installatie onderdelen](png/verify_binary_windows_beginner/verify-win_gpg4win-components.png)
+
+Je kunt het beste de standaard-installatielocatie laten staan, tenzij je weet wat je doet. Geef je keuze aan en klik op `Installeren`.
+
+![gpg4win installatie locatie](png/verify_binary_windows_beginner/verify-win_gpg4win-install.png)
+
+De installatie is voltooid. Klik op `Volgende`.
+
+![gpg4win installatie voltooid](png/verify_binary_windows_beginner/verify-win_gpg4win-install-complete.png)
+
+Klik op `Finish`.
+
+![gpg4win installatie voltooien](png/verify_binary_windows_beginner/verify-win_gpg4win-install-finish.png)
+
+## 2. Monero-ondertekeningssleutel
+
+In dit gedeelte leggen we uit hoe je de Monero-ondertekeningssleutel downloadt, verifieert dat de sleutel correct is en de sleutel importeert in je sleutelring. Het hashbestand wordt gebruikt om te verifiren dat je binaire bestand cryptografisch is ondertekend met de Monero-ondertekeningssleutel. Om de geldigheid van dit hashbestand te controleren heb je de openbare versie van de ondertekeningssleutel nodig.
+
+### 2.1. Ondertekeningssleutel downloaden
+
+Ga in een browser naar de [de GPG-sleutel van Fluffypony](https://raw.githubusercontent.com/monero-project/monero/master/utils/gpg_keys/fluffypony.asc), waarmee hij de Monero-binaries ondertekent. Klik met de rechtermuisknop op de pagina en klik vervolgens op `Pagina opslaan als`.
+
+![sleutel ophalen contextmenu](png/verify_binary_windows_beginner/verify-win_getkey-rightclick.png)
+
+Laat de standaardlocatie staan en klik op `Opslaan`.
+
+![sleutel ophalen bestand opslaan](png/verify_binary_windows_beginner/verify-win_getkey-savefilename.png)
+
+### 2.2. Kleopatra initialiseren
+
+Als dit de eerste keer is dat je Kleopatra gebruikt, moet je een sleutelpaar voor jezelf maken.
+
+Start Kleopatra.
+
+![kleo starten](png/verify_binary_windows_beginner/verify-win_kleopatra-launch.png)
+
+#### 2.2.1. Ondertekeningssleutel importeren
+
+Klik op `Importeren`.
+
+![kleo eerste keer importeren](png/verify_binary_windows_beginner/verify-win_kleopatra-firstrun-importkey.png)
+
+Open de map `Downloads`, selecteer `fluffypony` en klik op `Openen`.
+
+![kleo eerste keer locatie sleutel](png/verify_binary_windows_beginner/verify-win_kleopatra-firstrun-import-location.png)
+
+Start het certificeren van de sleutel door op `Ja` te klikken.
+
+![kleo eerste keer proces starten](png/verify_binary_windows_beginner/verify-win_kleopatra-firstrun-startverifyprocess.png)
+
+#### 2.2.2. Sleutelpaar aanmaken
+
+Start het aanmaken van de sleutel door op `Ja` te klikken.
+
+![kleo eerste keer sleutel aanmaken starten](png/verify_binary_windows_beginner/verify-win_kleopatra-firstrun-createkeysnow.png)
+
+Vul iets in voor `Naam` en `E-mail` en klik op `Volgende`.
+
+![kleo eerste keer gegevens sleutel](png/verify_binary_windows_beginner/verify-win_kleopatra-firstrun-createkeydetails.png)
+
+Verifieer de details en klik op `Aanmaken`.
+
+![kleo eerste keer gegevens sleutel verifiren](png/verify_binary_windows_beginner/verify-win_kleopatra-firstrun-verifykeydetails.png)
+
+Stel een wachtwoord in en klik op `OK`.
+
+![kleo eerste keer wachtwoord sleutel instellen](png/verify_binary_windows_beginner/verify-win_kleopatra-firstrun-createkeys-pinentry.png)
+
+Klik op `Finish`.
+
+![kleo eerste keer sleutel aanmaken voltooien](png/verify_binary_windows_beginner/verify-win_kleopatra-firstrun-keycreate-success.png)
+
+### 2.3. Ondertekeningssleutel verifiren
+
+Controleer visueel dat de sleutel van Riccardo Spagni de vingerafdruk `BDA6BD7042B721C467A9759D7455C5E3C0CDCEB9` heeft.
+
+![kleo vingerafdruk certificeren](png/verify_binary_windows_beginner/verify-win_kleopatra-certify-fingerprint.png)
+
+Klik op `Next` als de vingerafdruk **WEL** overeenkomt.
+
+**GA NIET VERDER** als de vingerafdruk van deze sleutel **NIET** overeenkomt. Verwijder dan het bestand `fluffypony` uit de map `Downloads` en ga terug naar [paragraaf 2.1](#21-download-signing-key).
+
+Laat `Certificeer alleen voor mijzelf` geselecteerd en klik op `Certifeer`.
+
+![kleo certificeren voor jezelf](png/verify_binary_windows_beginner/verify-win_kleopatra-certify-forself.png)
+
+Voer je wachtwoord in en klik op `OK`.
+
+![kleo certificeren wachtwoord](png/verify_binary_windows_beginner/verify-win_kleopatra-certify-pinentry.png)
+
+Klik op `Finish`.
+
+![kleo certificeren voltooien](png/verify_binary_windows_beginner/verify-win_kleopatra-certify-finish.png)
+
+## 3. Hashbestand verifiren
+
+In dit gedeelte leggen we uit hoe je het ondertekende bestand met bekende goede hashes downloadt en de authenticiteit verifieert.
+
+### 3.1. Hashbestand downloaden
+
+Ga in een browser naar de [hashpagina op getmonero.org](https://getmonero.org/downloads/hashes.txt). Klik met de rechtermuisknop op de pagina en klik vervolgens op `Pagina opslaan als`.
+
+![hashes contextmenu](png/verify_binary_windows_beginner/verify-win_hashes-getmonero-rightclick.png)
+
+Laat de standaardlocatie staan en klik op `Opslaan`.
+
+![hashes bestand opslaan](png/verify_binary_windows_beginner/verify-win_hashes-getmonero-savename.png)
+
+### 3.2. Hashbestand verifiren
+
+Klik in Kleopatra op de knop `Ontcijferen/verifiren`.
+
+![hashes kleo knop verifiren](png/verify_binary_windows_beginner/verify-win_hashes-kleo-verify-button.png)
+
+Ga naar de map `Downloads`. Selecteer het bestand `hashes` en klik op `Openen`.
+
+![hashes kleo bestand openen](png/verify_binary_windows_beginner/verify-win_hashes-kleo-verify-button-filename.png)
+
+Kleopatra geeft nu aan of de ondertekening van de bestanden geldig is.
+
+Als de ondertekening **GELDIG** is, zie je het volgende:
+
+![hashes kleo goede handtekening](png/verify_binary_windows_beginner/verify-win_hashes-kleo-goodsig.png)
+
+Als de ondertekening **ONGELDIG** is, zie je het volgende:
+
+![hashes kleo foute handtekening](png/verify_binary_windows_beginner/verify-win_hashes-kleo-badsig.png)
+
+Als je een **GELDIGE** ondertekening hebt ontvangen, klik je op `Discard` en ga je verder.
+
+**GA NIET VERDER** als je een **ONGELDIGE** ondertekening hebt ontvangen. Verwijder dan het bestand `hashes` uit de map `Downloads` en ga terug naar [paragraaf 3.1](#31-download-hash-file).
+
+## 4. Binair bestand verifiren
+
+In dit gedeelte leggen we uit hoe je de Monero-binary downloadt en de authenticiteit verifieert.
+
+### 4.1. Binary downloaden
+
+Ga in een browser naar de [downloadpagina op getmonero.org](https://getmonero.org/downloads/#windows). Selecteer het juiste binaire bestand voor je systeem.
+
+![binary getmonero](png/verify_binary_windows_beginner/verify-win_binary-getmonero-windowsfiles.png)
+
+Laat `Bestand opslaan` ingeschakeld en klik op `OK`.
+
+![binary getmonero opslaan](png/verify_binary_windows_beginner/verify-win_binary-getmonero-save-file.png)
+
+Laat de standaardlocatie staan en klik op `Opslaan`.
+
+![binary getmonero opslaan locatie](png/verify_binary_windows_beginner/verify-win_binary-getmonero-save-location.png)
+
+### 4.2. Binary verifiren
+
+Ga in een bestandenverkenner naar de map `Downloads`. Open het bestand `hashes` in een tekstverwerker.
+
+![binary hashes.txt openen](png/verify_binary_windows_beginner/verify-win_binary-word-hashfile.png)
+
+Open een opdrachtregel (`cmd.exe`).
+
+![binary opdrachtregel openen](png/verify_binary_windows_beginner/verify-win_binary-cmd-launch.png)
+
+Ga naar de map `Downloads` met de opdracht: `cd Downloads`.
+
+![binary cmd cd](png/verify_binary_windows_beginner/verify-win_binary-cmd-cd.png)
+
+Bereken de hash van de Monero-binary met de opdracht: `certUtil -hashfile monero-gui-win-x64-v0.11.1.0.zip SHA256` (of vervang `monero-gui-win-x64-v0.11.1.0.zip` door een andere bestandsnaam als je de opdrachtregelversie hebt gedownload).
+
+![binary cmd certutil](png/verify_binary_windows_beginner/verify-win_binary-cmd-certutil.png)
+
+Vergelijk de hash in de opdrachtregel met de hash in het hashbestand. De hashes horen hetzelfde te zijn. De spaties kun je negeren.
+
+![binary hashes vergelijken](png/verify_binary_windows_beginner/verify-win_binary-word-cmd-compare.png)
+
+Als de hash **WEL** overeenkomt, ben je klaar met de verificatie! Dan ben je er zeker van dat de Monero-bestanden die je hebt ontvangen authentiek zijn. Je kunt de bestanden verder op de normale manier uitpakken, installeren en gebruiken.
+
+**GA NIET VERDER** als de hash **NIET** overeenkomt. Verwijder dan de Monero-binary uit de map `Downloads` en ga terug naar [paragraaf 4.1](#41-download-binary).
diff --git a/_i18n/nl/resources/user-guides/view_only.md b/_i18n/nl/resources/user-guides/view_only.md
new file mode 100644
index 00000000..6af52243
--- /dev/null
+++ b/_i18n/nl/resources/user-guides/view_only.md
@@ -0,0 +1,34 @@
+{% assign version = '1.2.0' | split: '.' %}
+{% include disclaimer.html translated="true" version=page.version %}
+Met een alleen-lezen portemonnee kun je alleen zien welke binnenkomende transacties van jou zijn. Je kunt er geen Monero mee uitgeven. Sterker nog, je kunt zelfs uitgaande transacties vanuit deze portemonnee niet zien. Alleen-lezen portemonnees zijn daarom interessant voor:
+
+* Ontwikkelaars die libraries voor het valideren van betalingen programmeren
+* Eindgebruikers die binnenkomende transacties van een offline portemonnee (*cold wallet*) willen valideren
+
+### Een alleen-lezen portemonnee maken
+
+Je kunt in elke bestaande portemonnee een alleen-lezen portemonnee maken.
+
+#### Opdrachtregel
+
+Open een bestaande portemonnee of maak een nieuwe met `monero-wallet-cli`. Typ in de portemonnee `address` en `viewkey` om het adres en de geheime alleen-lezen sleutel weer te geven. Typ `exit` om de portemonnee af te sluiten.
+
+Vervolgens kun je je alleen-lezen portemonnee aanmaken door het volgende te typen: `monero-wallet-cli --generate-from-view-key wallet-name`. Het laatste argument is de bestandsnaam van je nieuwe portemonnee. Het programma vraagt naar een `Standard address` (standaardadres) en `View key` (alleen-lezen sleutel). Voer het adres en de geheime alleen-lezen sleutel van je oorspronkelijke portemonnee in. Voer daarna een wachtwoord in voor je nieuwe portemonnee, en klaar is Kees.
+
+#### Grafische interface
+
+Open een bestaande portemonnee of maak een nieuwe met `monero-wallet-gui`. Ga in de portemonnee naar de pagina `Instellingen` > `Portemonnee`:
+
+![settings](png/view-only/settings.png)
+
+Klik op `Maak een alleen-lezen portemonnee aan` > `Portemonnee maken`, geef een naam en een opslaglocatie op, en klik daarna op de pijl naar rechts:
+
+![create-view-only](png/view-only/create-view-only.png)
+
+Geef je alleen-lezen portemonnee een sterk wachtwoord en bevestig dit voordat je op `Portemonnee maken` klikt:
+
+![wallet-password](png/view-only/wallet-password.png)
+
+Dubbelklik eventueel op het scherm `Geslaagd` om het bericht te kopiren en klik vervolgens op `OK` om het te sluiten:
+
+![Success](png/view-only/Success.png)
diff --git a/_i18n/nl/resources/user-guides/vps_run_node.md b/_i18n/nl/resources/user-guides/vps_run_node.md
new file mode 100644
index 00000000..a261d4ff
--- /dev/null
+++ b/_i18n/nl/resources/user-guides/vps_run_node.md
@@ -0,0 +1,49 @@
+{% assign version = '1.1.0' | split: '.' %}
+{% include disclaimer.html translated="true" version=page.version %}
+# monerod
+
+`monerod` is de daemon-software die onderdeel uitmaakt van de Monero-code. Het is een console-programma waarmee de blockchain wordt beheerd. Terwijl een Bitcoin-portemonnee zowel een account als de blockchain beheert, worden deze functies in Monero gescheiden: `monerod` beheert de blockchain en `monero-wallet-cli` beheert het account.
+
+Deze handleiding gaat ervan uit dat je al een VPS-account hebt ingesteld en SSH gebruikt als tunnel om te communiceren met de serverconsole.
+
+## Linux, 64-bits (Ubuntu 16.04 LTS)
+
+### Zorg dat poort 18080 open staat
+`monerod` gebruikt deze poort om te communiceren met andere nodes op het Monero-netwerk.
+
+Voorbeeld als je `ufw` gebruikt: `sudo ufw allow 18080`
+Voorbeeld als je `iptables` gebruikt: `sudo iptables -A INPUT -p tcp --dport 18080 -j ACCEPT`
+
+### Download de huidige Monero Core-binaries
+
+ wget https://downloads.getmonero.org/linux64
+
+### Maak een directory aan en pak de bestanden uit.
+
+ mkdir monero
+ tar -xjvf linux64 -C monero
+
+### Start de daemon
+
+ cd monero
+ ./monerod
+
+### Opties:
+
+Een lijst met alle opties en instellingen weergeven:
+
+ ./monerod --help
+
+De daemon starten als een achtergrondproces:
+
+ ./monerod --detach
+
+De uitvoer van `monerod` als achtergrondproces loggen:
+
+ tail -f ~/.bitmonero/bitmonero.log
+
+De VPS beveiligen met automatische updates:
+
+https://help.ubuntu.com/community/AutomaticSecurityUpdates
+
+
diff --git a/_i18n/nl/technical-specs.md b/_i18n/nl/technical-specs.md
new file mode 100644
index 00000000..4e379f27
--- /dev/null
+++ b/_i18n/nl/technical-specs.md
@@ -0,0 +1,132 @@
+
+
+
+
+
+
+
+
+
+
Geen premine, geen instamine, geen token
+
+
+
+
+* Er is geen premine of instamine van Monero geweest
+* Monero heeft nooit een token verkocht
+* Er is geen enkele presale of voorverkoop van Monero geweest
+
+
+
+
+
+* CryptoNight
+* Kan in de toekomst veranderen
+
+
+
+
+
Herberekening moeilijkheidsgraad
+
+
+
+
+* Ieder blok
+* Gebaseerd op de laatste 720 blokken, maar zonder de 20% kortste en langste tijden
+
+
+
+
+
+* 2 minuten
+* Kan in de toekomst veranderen, maar de uitgiftecurve verandert niet
+
+
+
+
+
Beloning per blok
+
+
+
+
+* Neemt gelijkmatig af, met een malus voor blokken die groter zijn dan de mediaan van de laatste 100 blokken (M100)
+Zie de coinbase-transactie in het [laatste blok](https://moneroblocks.info/) voor de huidige beloning
+
+
+
+
+
+* Dynamisch, maximaal 2 * M100
+
+
+
+
+
+* Eerst de gewone curve: ~18.132 miljoen coins eind mei 2022
+* Daarna de blijvende uitgifte: 0,6 XMR per blok om de 2 minuten, nadat de gewone uitgifte klaar is, wat een steeds verder dalende inflatie van < 1% oplevert
+* Zie [grafieken en details](https://www.reddit.com/r/Monero/comments/512kwh/useful_for_learning_about_monero_coin_emission/)
+
+
+
+
+
Maximale geldhoeveelheid
+
+
+
+
+* Oneindig
+
+
+
+
+
+* Ring-handtekeningen
+
+
+
+
+
Privacy ontvanger
+
+
+
+
+* Stealth addresses
+
+
+
+
+
Verborgen bedragen
+
+
+
+
+* Vertrouwelijke ring-transacties
+
+
+
+
+
+
+
+
+
diff --git a/_i18n/pl.yml b/_i18n/pl.yml
index 3c5b23b1..a8ff0c17 100644
--- a/_i18n/pl.yml
+++ b/_i18n/pl.yml
@@ -7,6 +7,7 @@ langs:
ar: العربية
ru: Русский
de: Deutsch
+ nl: Nederlands
global:
date: '%Y/%m/%d'
diff --git a/_i18n/ru.yml b/_i18n/ru.yml
index e036bd77..23680908 100644
--- a/_i18n/ru.yml
+++ b/_i18n/ru.yml
@@ -7,6 +7,7 @@ langs:
ar: العربية
ru: Русский
de: Deutsch
+ nl: Nederlands
global:
date: '%Y/%m/%d'