From 43adc7dbb0ac68b9faa952eae526d82197544947 Mon Sep 17 00:00:00 2001 From: Elliot Wirrick Date: Tue, 16 Mar 2021 23:35:08 -0400 Subject: [PATCH] faq: fix capitalization of moneropedia links --- _i18n/en.yml | 4 ++-- get-started/faq/index.md | 6 +++--- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/_i18n/en.yml b/_i18n/en.yml index 5b8a4fba..6603c875 100644 --- a/_i18n/en.yml +++ b/_i18n/en.yml @@ -435,7 +435,7 @@ faq: qblocksize: How big is the Monero blockchain? ablocksize: "The Monero @blockchain is always growing so there is no fixed size. As of 2021, the full blockchain is around 95-100GB. A pruned blockchain is about 30GB. Check out Moneropedia entry @pruning to learn the difference between a full and a pruned blockchain." qblockspace: Why does the blockchain need so much space? - ablockspace: "When you download the @blockchain, you are downloading the entire history of the @transactions that happened in the Monero network since it was created. The transactions and the related data are heavy and the entire history must be kept by every node to ensure it's the same for everybody. @pruning a blockchain allows to run a node which keeps only 1/8 of not strictly necessary blockchain data. This results in a blockchain 2/3 smaller than a full one. Convenient for people with limited disk space. Check out the Moneropedia entries @node and @remote-node for more details." + ablockspace: "When you download the @blockchain, you are downloading the entire history of the @transactions that happened in the Monero network since it was created. The transactions and the related data are heavy and the entire history must be kept by every node to ensure it's the same for everybody. @Pruning a blockchain allows to run a node which keeps only 1/8 of not strictly necessary blockchain data. This results in a blockchain 2/3 smaller than a full one. Convenient for people with limited disk space. Check out the Moneropedia entries @node and @remote-node for more details." qavoidbc: Can I avoid downloading the entire blockchain? aavoidbc: "Yes. You don't need to download the @blockchain to transact on the network. You can connect to a @remote-node, which stores the blockchain for you. All the most common @wallets (including GUI and CLI) allow to use remote nodes to transact on the network. There are multiple ways to take advantage of this functionality. For example GUI and CLI offer a 'bootstrap node' feature, which allow people to download their own blockchain while using a remote node to immediately use the network. Ways to improve the usability of the Monero network are constantly being explored." qscanned: Why my wallet needs to be scanned everytime I open it? @@ -454,7 +454,7 @@ faq: Yes, you can, but you probably shouldn't. Importing an external @blockchain is very resource intensive and forces you to trust the entity providing you with the blockchain. It's usually faster to download it the normal way: running a node and letting it synchronize with the other @nodes in the network. If you really need to import an external blockchain, you can download one in the 'Downloads' page of this website. Follow the guide below if you are using Windows. If you are a linux user, you can use the tool "monero-blockchain-import", which is included in the archive when you download the GUI or CLI wallets. Start syncing the imported blockchain with this command: "monero-blockchain-import --input-file blockchain.raw". qhf: Is it true that Monero has a hard fork every 6 months? ahf: Monero used to have 2 network upgrades (hard forks) a year, but this is not the case anymore. The choice of the biannual hard forks was taken in order to be able to introduce important consensus changes, which added privacy features and network-wide improvements (For example @bulletproofs and CLSAG both required a hard fork) and avoid the ossification of the protocol. Recently, the biannual hard forks included changes to the PoW algorithm, to preserve ASIC-resistance. - ahf1: The dev community and the Core Team agree that the protocol is stable and mature enough and biannual hard forks are not necessary anymore. Furthermore, the ecosystem around Monero has grown exponentially during the years and frequent protocol changes would be increasingly hard to coordinate, could be detrimental to the growth of the ecosystem and to the user experience. Cherry on the top, the new algorithm @randomx is ensuring long term ASIC-resistance, so regular changes are not needed anymore. Network upgrades will still be used to add important protocol improvements and consensus changes, but at a lower and less strict frequency (every 9-12 months). + ahf1: The dev community and the Core Team agree that the protocol is stable and mature enough and biannual hard forks are not necessary anymore. Furthermore, the ecosystem around Monero has grown exponentially during the years and frequent protocol changes would be increasingly hard to coordinate, could be detrimental to the growth of the ecosystem and to the user experience. Cherry on the top, the new algorithm @RandomX is ensuring long term ASIC-resistance, so regular changes are not needed anymore. Network upgrades will still be used to add important protocol improvements and consensus changes, but at a lower and less strict frequency (every 9-12 months). qvideos: Are there videos I can watch to learn about Monero? avideos: > During the years the community has created a vast amount of informative content like articles and videos. Most of these videos are publicly available on platforms like YouTube. On this website we host a few videos that explain the fundamentals of Monero. To optimize their effectiveness, they should be viewed in sequence: diff --git a/get-started/faq/index.md b/get-started/faq/index.md index 30273332..bf27f733 100644 --- a/get-started/faq/index.md +++ b/get-started/faq/index.md @@ -185,9 +185,9 @@ permalink: /get-started/faq/index.html
  1. {% t faq.video_intro %} ({% t faq.aavailable %} Russian {% t faq.and %} Brazilian Portuguese)
  2. {% t faq.video_essentials %}
    3. -
  3. {% t faq.video_sa %} - {% t faq.mvideos %} @stealth-addresses
    4. -
  4. {% t faq.video_ringsig %} - {% t faq.mvideos %} @ring-signatures
    5. -
  5. {% t faq.video_ringct %} - {% t faq.mvideos %} @ring-ct
    6. +
  6. {% t faq.video_sa %} - {% t faq.mvideos %} @Stealth-Addresses
    7. +
  7. {% t faq.video_ringsig %} - {% t faq.mvideos %} @Ring-Signatures
    8. +
  8. {% t faq.video_ringct %} - {% t faq.mvideos %} @RingCT