mirror of
https://github.com/monero-project/monero-site.git
synced 2024-12-04 23:51:11 +02:00
Revamp of the FAQ
- Added anchors. Visible when hovering on the tabs - Added "More info:", which links to related sections on getmonero (contributing, user guides, etc) - Added toc - Added links to related Moneropedia entries in the answers - Added side box with more resources and info - 10 new questions/answers: - Can I avoid to download the entire blockchain? - why my wallet needs to be scanned everytime I open it? - Is it dangerous to run a personal node? - Is it dangerous to use a remote node? what's the data a node operator can get from me? - How can I contribute? - What's the meaning of [technical word]? - What wallet should I use? - Can't see funds. Did I just lose all my Monero? - How can I connect my node via Tor? - Why does the blockchain need so much space?
This commit is contained in:
erciccione
parent
8d36587390
commit
6dd7c60006
68
_i18n/en.yml
68
_i18n/en.yml
@ -331,39 +331,73 @@ contributing:
|
||||
donate-other_para2: for alternative means of donating or if you would like to become a sponsor for the Monero Project.
|
||||
|
||||
faq:
|
||||
intro: List of common questions with relative answers and resources
|
||||
toc: Table Of Contents
|
||||
general: General
|
||||
advanced: Advanced
|
||||
nodeandwallet: Node and Wallet
|
||||
additional: "More Info:"
|
||||
resandhelp: Resources & Help
|
||||
stackexchange: One of the most complete resources about Monero. If you have a question which is not in this FAQ, you will likely find the answer on the Monero StackExchange.
|
||||
userguides: A collection of documents to help users interact with the Monero network and its components.
|
||||
devguides: Guides and resources for developers.
|
||||
monerosupport: The subreddit dedicated to help monero users. Basically community members helping each others. Use the search option.
|
||||
monerohow: "Old and known resources with a good number of guides and howto's"
|
||||
qword: "What's the meaning of [technical word]?"
|
||||
aword: "The terminology used in Monero can be quite complex, for this reason we have the"
|
||||
aword1: "A comprehensive list of terms that you often see and their explanation. If you don't know what a world means or you would like to have more info about it, just visit the Moneropedia. Some example of often searched terms are: @node, @fungibility, @view-key, @pruning."
|
||||
qcontribute: How can I contribute?
|
||||
acontribute: "Monero is an open source community project. Meaning that there is no company who runs it and there is no CEO who hires people. Everything is built by volunteers or community-funded contributors who dedicate their time to the project. There are many ways to contribute:"
|
||||
acontribute1: Translations. It's easy and anybody speaking a language beside English can help. Translations happen mostly on
|
||||
acontribute2: "Contact a Workgroup. Almost everything in Monero is managed by workgroups, which are groups of contributors (often lead by a coordinator) working on some specific aspect of the development. Some examples are: the localization workgroup (translations), the community workgroup, the GUI workgroup, the Outreach workgroup and so on. Workgroups are mostly independent and have their own structure. Contact the workgroup that interests you and ask how you can help. for a list of contacts see the"
|
||||
acontribute3: Do what you can do best. Are you a designer? create Monero related images and spread them around. Are you a writer? Write about Monero. The only limit is your imagination. Find what you like to do and do it for Monero!
|
||||
acontribute4: "The Outreach workgroup wrote a useful article to help newcomers:"
|
||||
q1: How does Monero have value?
|
||||
a1: Monero has value because people are willing to buy it. If no one is willing to buy Monero, then it will not have any value. Monero’s price increases if demand exceeds supply, and it decreases if supply exceeds demand.
|
||||
q2: How can I get Monero?
|
||||
a2: You can buy Monero from an exchange or from an individual. Alternatively, you can try mining Monero to get coins from the block reward.
|
||||
q3: What is a mnemonic seed?
|
||||
a3: A mnemonic seed is a set of 25 words that can be used to restore your account anywhere. Keep these words safe and do not share them with someone else. You can use this seed to restore your account, even if your computer crashes.
|
||||
a2: You can buy Monero from an exchange or from an individual. Alternatively, you can try mining Monero to get coins from the @block reward.
|
||||
q3: Why is the Mnemonic Seed important?
|
||||
a3: A @mnemonic-seed is a set of 25 words that can be used to restore your account anywhere. Keep these words safe and do not share them with someone else. You can use this seed to restore your account, even if your computer crashes.
|
||||
q4: How is Monero’s privacy different from other coins?
|
||||
a4: |
|
||||
Monero uses three different privacy technologies: ring signatures, ring confidential transactions (RingCT), and stealth addresses. These hide the sender, amount, and receiver in the transaction, respectively. All transactions on the network are private by mandate; there is no way to accidentally send a transparent transaction. This feature is exclusive to Monero. You do not need to trust anyone else with your privacy.
|
||||
a4: "Monero uses three different privacy technologies: @ring-signatures, ring confidential transactions (@RingCT), and @stealth-addresses. These hide the sender, amount, and receiver in the @transaction, respectively. All transactions on the network are private by mandate; there is no way to accidentally send a transparent transaction. This feature is exclusive to Monero. You do not need to trust anyone else with your privacy."
|
||||
q5: Why is my wallet taking so long to sync?
|
||||
a5: If you are running a full node locally, you need to copy the entire blockchain to your computer. This can take a long time, especially on an old hard drive or slow internet connection. If you are using a remote node, your computer still needs to request a copy of all the outputs, which can take several hours. Be patient, and if you would like to sacrifice some privacy for faster sync times, consider using a lightweight wallet instead.
|
||||
a5: If you are running a full @node locally, you need to copy the entire @blockchain to your computer. This can take a long time, especially on an old hard drive or slow internet connection. If you are using a @remote-node, your computer still needs to request a copy of all the outputs, which can take several hours. Be patient, and if you would like to sacrifice some privacy for faster sync times, consider using a remote node or lightweight @wallet instead.
|
||||
q6: What is the difference between a lightweight and a normal wallet?
|
||||
a6: For a lightweight wallet, you give your view key to a node, who scans the blockchain and looks for incoming transactions to your account on your behalf. This node will know when you receive money, but it will not know how much you receive, who you received it from, or who you are sending money to. Depending on your wallet software, you may be able to use a node you control to avoid privacy leaks. For more privacy, use a normal wallet, which can be used with your own node.
|
||||
q7: How is Monero different from Bitcoin?
|
||||
a7: Monero is not based on Bitcoin. It is based on the CryptoNote protocol. Bitcoin is a completely transparent system, where people can see exactly how much money is being sent from one user to another. Monero hides this information to protect user privacy in all transactions. It also has a dynamic block size and dynamic fees, an ASIC-resistant proof of work, and a tail coin emission, among several other changes.
|
||||
a7: Monero is not based on Bitcoin. It is based on the CryptoNote protocol. Bitcoin is a completely transparent system, where people can see exactly how much money is being sent from one user to another. Monero hides this information to protect user privacy in all transactions. It also has a dynamic @block size and dynamic fees, an ASIC-resistant proof of work (RandomX), and a @tail-emission, among several other changes.
|
||||
q8: Does Monero have a block size limit?
|
||||
a8: No, Monero does not have a hard block size limit. Instead, the block size can increase or decrease over time based on demand. It is capped at a certain growth rate to prevent outrageous growth.
|
||||
q9: What is a blockchain?
|
||||
a9: A blockchain is a system that stores a copy of all transaction history on the Monero network. Every two minutes, a new block with the latest transaction information is added to the blockchain. This chain allows the network to verify the amount of money accounts have and make it resilient to attacks and centralization attempts.
|
||||
q10: What is Kovri?
|
||||
a10: Kovri is an I2P router written in C++. I2P is a hidden network like Tor with several technical differences. Kovri is an independent project of Monero, but it will work with Monero and several other projects. Kovri hides the transaction broadcast, so other nodes do not know who created transactions. In adversarial conditions, Kovri can be used to hide all Monero traffic through I2P, which would prevent people from knowing Monero is being used. Kovri is currently in alpha, and it is not yet fully integrated in Monero. Learn more about Kovri at the <a href="https://kovri.io">project website.</a>
|
||||
a8: No, Monero does not have a hard @block size limit. Instead, the block size can increase or decrease over time based on demand. It is capped at a certain growth rate to prevent outrageous growth (@scalability).
|
||||
q11: What is fungibility, and why is it important?
|
||||
a11: Fungibility is a simple property of money such that there are no differences between two amounts of the same value. If two people exchanged a 10 and two 5’s, then no one would lose out. However, let’s suppose that everyone knows the 10 was previously used in a ransomware attack. Is the other person still going to make the trade? Probably not, even if the person with the 10 has no connection with the ransomware. This is a problem, since the receiver of money needs to constantly check the money they are receiving to not end up with tainted coins. Monero is fungible, which means people do not need to go through this effort.
|
||||
a11: "@Fungibility is a simple property of money such that there are no differences between two amounts of the same value. If two people exchanged a 10 and two 5’s, then no one would lose out. However, let’s suppose that everyone knows the 10 was previously used in a ransomware attack. Is the other person still going to make the trade? Probably not, even if the person with the 10 has no connection with the ransomware. This is a problem, since the receiver of money needs to constantly check the money they are receiving to not end up with tainted coins. Monero is fungible, which means people do not need to go through this effort."
|
||||
q12: If Monero is so private how do we know they're not being created out of thin air?
|
||||
a12-1: In Monero, every transaction output is uniquely associated with a key image that can only be generated by the holder of that output. Key images that are used more than once are rejected by the miners as double-spends and cannot be added to a valid block. When a new transaction is received, miners verify that the key image does not already exist for a previous transaction to ensure it's not a double-spend.
|
||||
a12-2: We can also know that transaction amounts are valid even though the value of the inputs that you are spending and the value of the outputs you are sending are encrypted (these are hidden to everyone except the recipient). Because the amounts are encrypted using Pedersen commitments what this means is that no observers can tell the amounts of the inputs and outputs, but they can do math on the Pedersen commitments to determine that no Monero was created out of thin air.
|
||||
a12-1: In Monero, every @transaction output is uniquely associated with a key image that can only be generated by the holder of that output. Key images that are used more than once are rejected by the miners as double-spends and cannot be added to a valid @block. When a new transaction is received, miners verify that the key image does not already exist for a previous transaction to ensure it's not a double-spend.
|
||||
a12-2: We can also know that transaction amounts are valid even though the value of the inputs that you are spending and the value of the outputs you are sending are encrypted (these are hidden to everyone except the recipient). Because the amounts are encrypted using @Pedersen-commitments what this means is that no observers can tell the amounts of the inputs and outputs, but they can do math on the Pedersen commitments to determine that no Monero was created out of thin air.
|
||||
a12-3: As long as the encrypted output amounts you create is equal to the sum of the inputs that are being spent (which include an output for the recipient and a change output back to yourself and the unencrypted transaction fee), then you have a legitimate transaction and know no Monero is being created out of thin air. Pedersen commitments mean that the sums can be verified as being equal, but the Monero value of each of the sums and the Monero value of the inputs and outputs individually are undeterminable.
|
||||
q13: Is Monero magic and protect my privacy no matter what I do ?
|
||||
q13: Is Monero magic and protect my privacy no matter what I do?
|
||||
a13: Monero is not magic. If you use Monero but give your name and address to another party, the other party will not magically forget your name and address. If you give out your secret keys, others will know what you've done. If you get compromised, others will be able to keylog you. If you use a weak password, others will be able to brute force your keys file. If you backup your seed in the cloud, you'll be poorer soon.
|
||||
q14: Is Monero 100% anonymous ?
|
||||
q14: Is Monero 100% anonymous?
|
||||
a14: There is no such thing as 100% anonymous. If nothing else, your anonymity set is the set of people using Monero. Some people don't use Monero. Monero may also have bugs. Even if not, ways may exist to infer some information through Monero's privacy layers, either now or later. Attacks only get better. If you wear a seatbelt, you can still die in a car crash. Use common sense, prudence and defense in depth.
|
||||
q15: Is Monero a mixer or mixing service?
|
||||
a15: No. Monero uses a completely non-interactive, non-custodial, and automatic process to create private transactions. By contrast for mixing services, users opt-in to participate.
|
||||
qwallet: What wallet should I use?
|
||||
awallet: There are multiple wallets available for a vast number of platforms. On this website you'll find the wallets released by the Core Team (GUI and CLI) and a list of widely trusted and open source third party wallets for desktop and mobile.
|
||||
qnofunds: I can't see my funds. Did I just lose all my Monero?
|
||||
anofunds: "You probably didn't. It's very hard to simply 'lose' your coins, since they are technically nowhere. Your coins 'live' on the blockchain and are linked to your account through a system of public and private keys secured by cryptography. That's why if you don't see your funds, it's probably because of a technical issue. Take a look at the 'Resources & Help' section at the top of this page for a list of useful resources that will help you identify and fix your problem."
|
||||
qnodetor: How can I connect my node via Tor?
|
||||
anodetor: Support for Tor is still in its infancies, but it's already possible to natively send transactions through the network and to run a Monero daemon on the Tor network. Better Tor and I2P integrations are in progress.
|
||||
qfullpruned: How do I decide if I should run a full node or a pruned node?
|
||||
afullpruned: "A full @node requires a considerable amount of storage and could take a long time to download and verify the entire blockchain, especially on older hardware. If you have limited storage, a pruned node is recommended. It only stores 1/8th of unnecessary blockchain data while keeping the full transaction history. If plenty of storages is available, a full node is recommended but a pruned node still greatly contributes to the network and improves your privacy."
|
||||
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."
|
||||
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?
|
||||
ascanned: Because new @transactions have been recorded on the @blockchain from the last time you opened your wallet, which needs to scan all of them to make sure non of those transaction is yours. This process is not necessary in a mymonero-style (openmonero) wallet, a central server (which could be managed by you) does this work for you.
|
||||
qdangernode: Is it dangerous to run a personal node?
|
||||
adangernode: "Running a personal @node is the safest way to interact with the Monero network, because you are in full control and you don't need to rely on third parties. From a general point of view running a node is not dangerous, but keep in mind that your ISP can see you are running a Monero node."
|
||||
qdangerrnode: Is it dangerous to use a remote node? What's the data a node operator can get from me?
|
||||
adangerrnode: "It's always advisable, especially for privacy-conscious users, to use a personal node when transacting on the network to achieve the highest rate of privacy. Some people for convenience prefer to use @remote-node which are not under their control (public nodes). The convenience of not having to deal with a personal copy of the @blockchain comes at a cost: lessened privacy. A remote node operator is able to see from what IP address a transaction comes from (even if cannot see the recipient nor the amount) and in some extreme cases, can make attacks able to reduce your privacy. Some dangers can be mitigated by using remote nodes on the Tor or I2P networks or using a VPN."
|
||||
|
||||
mining:
|
||||
intro1: Monero is a cryptocurrency that relies on proof-of-work mining to achieve distributed consensus. Below you'll find some information and resources on how to begin mining.
|
||||
|
||||
@ -4347,13 +4347,102 @@ p.hangouts-social {
|
||||
|
||||
}
|
||||
|
||||
/*************************FAQ********************************/
|
||||
|
||||
.faq h2 {
|
||||
margin-bottom: 1rem;
|
||||
}
|
||||
|
||||
.faq ul {
|
||||
margin-bottom: 1rem;
|
||||
list-style-type: none;
|
||||
}
|
||||
|
||||
.faq ul.logo {
|
||||
list-style-image: url('/img/logo-list.svg');
|
||||
}
|
||||
|
||||
.faq li.category {
|
||||
font-size: 1.3rem;
|
||||
margin-bottom: 1rem;
|
||||
}
|
||||
|
||||
.faq .tab {
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.faq .tab-answer {
|
||||
margin: 0 1rem 1rem 1rem;
|
||||
}
|
||||
|
||||
.faq .tab h3 {
|
||||
font-weight: bold;
|
||||
}
|
||||
|
||||
.faq a.arrow-up {
|
||||
border: 1px solid #d26e2b;
|
||||
border-radius: 50%;
|
||||
height: 3rem;
|
||||
width: 3rem;
|
||||
position: fixed;
|
||||
bottom: 2rem;
|
||||
right: 2rem;
|
||||
background-color: #ffffff;
|
||||
z-index: 5;
|
||||
}
|
||||
|
||||
.faq a.arrow-up:hover, .downloads a.arrow-up:focus {
|
||||
border: none;
|
||||
background-color: #d26e2b;
|
||||
}
|
||||
|
||||
.faq a.arrow-up i {
|
||||
border: solid #d26e2b;
|
||||
border-width: 0 3px 3px 0;
|
||||
padding: 0.5rem;
|
||||
position: absolute;
|
||||
top: 1.02rem;
|
||||
left: 0.88rem;
|
||||
transform: rotate(-135deg);
|
||||
-webkit-transform: rotate(-135deg);
|
||||
-webkit-transition: all ease-out .2s;
|
||||
-moz-transition: all ease-out .2s;
|
||||
-o-transition: all ease-out .2s;
|
||||
transition: all ease-out .2s;
|
||||
}
|
||||
|
||||
.faq a.arrow-up:hover i, .faq a.arrow-up:focus i {
|
||||
border-color: #ffffff;
|
||||
}
|
||||
|
||||
.tab .anchor {
|
||||
height: 2rem;
|
||||
width: 2rem;
|
||||
display: inline-block;
|
||||
visibility: hidden;
|
||||
position: absolute;
|
||||
left: -2rem;
|
||||
border-bottom: none;
|
||||
z-index: 1;
|
||||
line-height: unset;
|
||||
padding-left: 0.5rem;
|
||||
}
|
||||
|
||||
.tab .anchor:before {
|
||||
content: "\01F517";
|
||||
}
|
||||
|
||||
.tab:hover .anchor {
|
||||
visibility: visible;
|
||||
border-bottom: none;
|
||||
}
|
||||
|
||||
/*************************accordion********************************/
|
||||
|
||||
.tab {
|
||||
position: relative;
|
||||
width: 100%;
|
||||
color: #4c4c4c;
|
||||
overflow: hidden;
|
||||
border-top: 1px solid #edeef0;
|
||||
}
|
||||
|
||||
@ -4400,11 +4489,11 @@ label.accordion {
|
||||
|
||||
.tab-content {
|
||||
max-height: 0;
|
||||
overflow: hidden;
|
||||
border-radius: 3px;
|
||||
-webkit-transition: max-height 0.3s;
|
||||
-o-transition: max-height 0.3s;
|
||||
transition: max-height 0.3s;
|
||||
overflow: hidden;
|
||||
}
|
||||
|
||||
.tab-content p {
|
||||
@ -4413,7 +4502,6 @@ label.accordion {
|
||||
|
||||
input.accordion:checked ~ .tab-content {
|
||||
max-height: 100rem;
|
||||
overflow: visible;
|
||||
}
|
||||
|
||||
label.accordion::after {
|
||||
|
||||
@ -1,113 +1,252 @@
|
||||
---
|
||||
layout: full-text
|
||||
layout: custom
|
||||
title: titles.faq
|
||||
permalink: /get-started/faq/index.html
|
||||
---
|
||||
{% t global.lang_tag %}
|
||||
<div class="tab">
|
||||
<input id="tab-one" type="checkbox" name="tabs" class="accordion">
|
||||
<label for="tab-one" class="accordion">{% t faq.q1 %}</label>
|
||||
<div class="tab-content">
|
||||
<p>{% t faq.a1 %}</p>
|
||||
</div>
|
||||
<div class="container description">
|
||||
<p>{% t faq.intro %}</p>
|
||||
</div>
|
||||
<div class="tab">
|
||||
<input id="tab-two" type="checkbox" name="tabs" class="accordion">
|
||||
<label for="tab-two" class="accordion">{% t faq.q2 %}</label>
|
||||
<div class="tab-content">
|
||||
<p>{% t faq.a2 %}</p>
|
||||
<section class="container">
|
||||
<div class="row faq">
|
||||
<!-- left two-thirds block-->
|
||||
<div class="left two-thirds col-lg-8 col-md-8 col-sm-12 col-xs-12">
|
||||
<div class="info-block">
|
||||
<div class="row center-xs">
|
||||
<div class="col">
|
||||
<h2>{% t faq.toc %}</h2>
|
||||
</div>
|
||||
</div>
|
||||
<ul>
|
||||
<li class="category">{% t faq.general %}</li>
|
||||
<ul class="logo">
|
||||
<li><a href="#anchor-word">{% t faq.qword %}</a></li>
|
||||
<li><a href="#anchor-contribute">{% t faq.qcontribute %}</a></li>
|
||||
<li><a href="#anchor-value">{% t faq.q1 %}</a></li>
|
||||
<li><a href="#anchor-buy">{% t faq.q2 %}</a></li>
|
||||
<li><a href="#anchor-different">{% t faq.q4 %}</a></li>
|
||||
<li><a href="#anchor-btc-difference">{% t faq.q7 %}</a></li>
|
||||
<li><a href="#anchor-fungibility">{% t faq.q11 %}</a></li>
|
||||
<li><a href="#anchor-magic">{% t faq.q13 %}</a></li>
|
||||
<li><a href="#anchor-anonymous">{% t faq.q14 %}</a></li>
|
||||
</ul>
|
||||
<li class="category">{% t faq.advanced %}</li>
|
||||
<ul class="logo">
|
||||
<li><a href="#anchor-thin-air">{% t faq.q12 %}</a></li>
|
||||
<li><a href="#anchor-light-normal">{% t faq.q6 %}</a></li>
|
||||
<li><a href="#anchor-block-limit">{% t faq.q8 %}</a></li>
|
||||
<li><a href="#anchor-mixing">{% t faq.q15 %}</a></li>
|
||||
</ul>
|
||||
<li class="category">{% t faq.nodeandwallet %}</li>
|
||||
<ul class="logo">
|
||||
<li><a href="#anchor-wallet">{% t faq.qwallet %}</a></li>
|
||||
<li><a href="#anchor-lost-funds">{% t faq.qnofunds %}</a></li>
|
||||
<li><a href="#anchor-tor-node">{% t faq.qnodetor %}</a></li>
|
||||
<li><a href="#anchor-long-sync">{% t faq.q5 %}</a></li>
|
||||
<li><a href="#anchor-full-pruned">{% t faq.qfullpruned %}</a></li>
|
||||
<li><a href="#anchor-block-space">{% t faq.qblockspace %}</a></li>
|
||||
<li><a href="#anchor-avoid-bc">{% t faq.qavoidbc %}</a></li>
|
||||
<li><a href="#anchor-scanned-wallet">{% t faq.qscanned %}</a></li>
|
||||
<li><a href="#anchor-danger-node">{% t faq.qdangernode %}</a></li>
|
||||
<li><a href="#anchor-danger-rnode">{% t faq.qdangerrnode %}</a></li>
|
||||
</ul>
|
||||
</ul>
|
||||
</div>
|
||||
</div>
|
||||
<!-- END left two-thirds block-->
|
||||
<!-- Right one-third block -->
|
||||
<div class="right one-third col-lg-4 col-md-4 col-sm-12 col-xs-12">
|
||||
<div class="info-block">
|
||||
<div class="row center-xs">
|
||||
<div class="col">
|
||||
<h2>{% t faq.resandhelp %}</h2>
|
||||
</div>
|
||||
</div>
|
||||
<h3><a href="https://monero.stackexchange.com/">StackExchange</a></h3>
|
||||
<p>{% t faq.stackexchange %}</p>
|
||||
<h3><a href="{{ site.baseurl }}/resources/user-guides/">{% t titles.userguides %}</a></h3>
|
||||
<p>{% t faq.userguides %}</p>
|
||||
<h3><a href="{{ site.baseurl }}/resources/developer-guides/">{% t titles.developerguides %}</a></h3>
|
||||
<p>{% t faq.devguides %}</p>
|
||||
<h3><a href="https://www.reddit.com/r/monerosupport/">r/monerosupport</a></h3>
|
||||
<p>{% t faq.monerosupport %}</p>
|
||||
<h3><a href="https://www.monero.how/">Monero.how</a></h3>
|
||||
<p>{% t faq.monerohow %}</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="tab">
|
||||
<input id="tab-three" type="checkbox" name="tabs" class="accordion">
|
||||
<label for="tab-three" class="accordion">{% t faq.q3 %}</label>
|
||||
<div class="tab-content">
|
||||
<p>{% t faq.a3 %}</p>
|
||||
<!-- END Right one-third block -->
|
||||
</section>
|
||||
<section class="container">
|
||||
<div class="row faq">
|
||||
<!-- full block-->
|
||||
<div class="full col-lg-12 col-md-12 col-sm-12 col-xs-12">
|
||||
<div class="info-block">
|
||||
<div class="row center-xs">
|
||||
<!-- 'General' section-->
|
||||
<div class="col"><h2>{% t faq.general %}</h2></div>
|
||||
</div>
|
||||
<div class="tab" id="anchor-word">
|
||||
<h3><a class="anchor" href="#anchor-word"></a>{% t faq.qword %}</h3>
|
||||
<div class="tab-answer">
|
||||
<p>{% t faq.aword %} <a href="{{ site.baseurl }}/resources/moneropedia/">Moneropedia</a>. {% t faq.aword1 %}
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="tab" id="anchor-contribute">
|
||||
<h3><a class="anchor" href="#anchor-contribute"></a>{% t faq.qcontribute %}</h3>
|
||||
<div class="tab-answer">
|
||||
<p>{% t faq.acontribute %}</p>
|
||||
<p>{% t faq.acontribute1 %} <a href="https://translate.getmonero.org">Weblate</a>.</p>
|
||||
<p>{% t faq.acontribute2 %} <a href="{{ site.baseurl }}/community/hangouts/">Hangouts</a>.</p>
|
||||
<p>{% t faq.acontribute3 %}</p>
|
||||
<p>{% t faq.acontribute4 %} <a href="https://www.monerooutreach.org/stories/getting-started-helping-monero.html">Getting started with Monero</a>.</p>
|
||||
<p>{% t faq.additional %} <a href="{{ site.baseurl }}/get-started/accepting/">{% t titles.contributing %}</a></p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="tab" id="anchor-value">
|
||||
<h3><a class="anchor" href="#anchor-value"></a>{% t faq.q1 %}</h3>
|
||||
<div class="tab-answer">
|
||||
<p>{% t faq.a1 %}</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="tab" id="anchor-buy">
|
||||
<h3><a class="anchor" href="#anchor-buy"></a>{% t faq.q2 %}</h3>
|
||||
<div class="tab-answer">
|
||||
<p>{% t faq.a2 %}</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="tab" id="anchor-different">
|
||||
<h3><a class="anchor" href="#anchor-different"></a>{% t faq.q4 %}</h3>
|
||||
<div class="tab-answer" id="anchor-different">
|
||||
<p>{% t faq.a4 %}</p>
|
||||
<p>{% t faq.additional %} <a href="{{ site.baseurl }}/resources/about/">{% t titles.about %}</a></p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="tab" id="anchor-btc-difference">
|
||||
<h3><a class="anchor" href="#anchor-btc-difference"></a>{% t faq.q7 %}</h3>
|
||||
<div class="tab-answer">
|
||||
<p>{% t faq.a7 %}</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="tab" id="anchor-fungibility">
|
||||
<h3><a class="anchor" href="#anchor-fungibility"></a>{% t faq.q11 %}</h3>
|
||||
<div class="tab-answer">
|
||||
<p>{% t faq.a11 %}</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="tab" id="anchor-magic">
|
||||
<h3><a class="anchor" href="#anchor-magic"></a>{% t faq.q13 %}</h3>
|
||||
<div class="tab-answer">
|
||||
<p>{% t faq.a13 %}</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="tab" id="anchor-anonymous">
|
||||
<h3><a class="anchor" href="#anchor-anonymous"></a>{% t faq.q14 %}</h3>
|
||||
<div class="tab-answer">
|
||||
<p>{% t faq.a14 %}</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="row center-xs">
|
||||
<!-- 'Advanced' section-->
|
||||
<div class="col"><h2>{% t faq.advanced %}</h2></div>
|
||||
</div>
|
||||
<div class="tab" id="anchor-thin-air">
|
||||
<h3><a class="anchor" href="#anchor-thin-air"></a>{% t faq.q12 %}</h3>
|
||||
<div class="tab-answer">
|
||||
<p>{% t faq.a12-1 %}</p>
|
||||
<p>{% t faq.a12-2 %}</p>
|
||||
<p>{% t faq.a12-3 %}</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="tab" id="anchor-light-normal">
|
||||
<h3><a class="anchor" href="#anchor-light-normal"></a>{% t faq.q6 %}</h3>
|
||||
<div class="tab-answer">
|
||||
<p>{% t faq.a6 %}</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="tab" id="anchor-block-limit">
|
||||
<h3><a class="anchor" href="#anchor-block-limit"></a>{% t faq.q8 %}</h3>
|
||||
<div class="tab-answer">
|
||||
<p>{% t faq.a8 %}</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="tab" id="anchor-mixing">
|
||||
<h3><a class="anchor" href="#anchor-mixing"></a>{% t faq.q15 %}</h3>
|
||||
<div class="tab-answer">
|
||||
<p>{% t faq.a15 %}</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="row center-xs">
|
||||
<!-- 'Node and Wallet' section-->
|
||||
<div class="col"><h2>{% t faq.nodeandwallet %}</h2></div>
|
||||
</div>
|
||||
<div class="tab" id="anchor-wallet">
|
||||
<h3><a class="anchor" href="#anchor-wallet"></a>{% t faq.qwallet %}</h3>
|
||||
<div class="tab-answer">
|
||||
<p>{% t faq.awallet %}</p>
|
||||
<p>{% t faq.additional %} <a href="{{ site.baseurl }}/downloads">{% t titles.downloads %}</a></p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="tab" id="anchor-lost-funds">
|
||||
<h3><a class="anchor" href="#anchor-lost-funds"></a>{% t faq.qnofunds %}</h3>
|
||||
<div class="tab-answer">
|
||||
<p>{% t faq.anofunds %}</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="tab" id="anchor-tor-node">
|
||||
<h3><a class="anchor" href="#anchor-tor-node"></a>{% t faq.qnodetor %}</h3>
|
||||
<div class="tab-answer">
|
||||
<p>{% t faq.anodetor %}</p>
|
||||
<p>{% t faq.additional %} <a href="{{ site.baseurl }}/resources/user-guides/tor_wallet.html">{% t user-guides.tor_wallet %}</a></p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="tab" id="anchor-long-sync">
|
||||
<h3><a class="anchor" href="#anchor-long-sync"></a>{% t faq.q5 %}</h3>
|
||||
<div class="tab-answer">
|
||||
<p>{% t faq.a5 %}</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="tab" id="anchor-full-pruned">
|
||||
<h3><a class="anchor" href="#anchor-full-pruned"></a>{% t faq.qfullpruned %}</h3>
|
||||
<div class="tab-answer">
|
||||
<p>{% t faq.afullpruned %}</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="tab" id="anchor-block-space">
|
||||
<h3><a class="anchor" href="#anchor-block-space"></a>{% t faq.qblockspace %}</h3>
|
||||
<div class="tab-answer">
|
||||
<p>{% t faq.ablockspace %}</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="tab" id="anchor-avoid-bc">
|
||||
<h3><a class="anchor" href="#anchor-avoid-bc"></a>{% t faq.qavoidbc %}</h3>
|
||||
<div class="tab-answer">
|
||||
<p>{% t faq.aavoidbc %}</p>
|
||||
<p>{% t faq.additional %} <a href="{{ site.baseurl }}/resources/user-guides/remote_node_gui.html">{% t user-guides.remote-node-gui %}</a></p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="tab" id="anchor-scanned-wallet">
|
||||
<h3><a class="anchor" href="#anchor-scanned-wallet"></a>{% t faq.qscanned %}</h3>
|
||||
<div class="tab-answer">
|
||||
<p>{% t faq.ascanned %}</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="tab" id="anchor-danger-node">
|
||||
<h3><a class="anchor" href="#anchor-danger-node"></a>{% t faq.qdangernode %}</h3>
|
||||
<div class="tab-answer">
|
||||
<p>{% t faq.adangernode %}</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="tab" id="anchor-danger-rnode">
|
||||
<h3><a class="anchor" href="#anchor-danger-rnode"></a>{% t faq.qdangerrnode %}</h3>
|
||||
<div class="tab-answer">
|
||||
<p>{% t faq.adangerrnode %}</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<!-- END full block-->
|
||||
<a href="#" class="arrow-up"><i></i></a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="tab">
|
||||
<input id="tab-four" type="checkbox" name="tabs" class="accordion">
|
||||
<label for="tab-four" class="accordion">{% t faq.q4 %}</label>
|
||||
<div class="tab-content">
|
||||
<p>{% t faq.a4 %}</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="tab">
|
||||
<input id="tab-five" type="checkbox" name="tabs" class="accordion">
|
||||
<label for="tab-five" class="accordion">{% t faq.q5 %}</label>
|
||||
<div class="tab-content">
|
||||
<p>{% t faq.a5 %}</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="tab">
|
||||
<input id="tab-six" type="checkbox" name="tabs" class="accordion">
|
||||
<label for="tab-six" class="accordion">{% t faq.q6 %}</label>
|
||||
<div class="tab-content">
|
||||
<p>{% t faq.a6 %}</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="tab">
|
||||
<input id="tab-seven" type="checkbox" name="tabs" class="accordion">
|
||||
<label for="tab-seven" class="accordion">{% t faq.q7 %}</label>
|
||||
<div class="tab-content">
|
||||
<p>{% t faq.a7 %}</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="tab">
|
||||
<input id="tab-eight" type="checkbox" name="tabs" class="accordion">
|
||||
<label for="tab-eight" class="accordion">{% t faq.q8 %}</label>
|
||||
<div class="tab-content">
|
||||
<p>{% t faq.a8 %}</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="tab">
|
||||
<input id="tab-nine" type="checkbox" name="tabs" class="accordion">
|
||||
<label for="tab-nine" class="accordion">{% t faq.q9 %}</label>
|
||||
<div class="tab-content">
|
||||
<p>{% t faq.a9 %}</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="tab">
|
||||
<input id="tab-ten" type="checkbox" name="tabs" class="accordion">
|
||||
<label for="tab-ten" class="accordion">{% t faq.q10 %}</label>
|
||||
<div class="tab-content">
|
||||
<p>{% t faq.a10 %}</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="tab">
|
||||
<input id="tab-eleven" type="checkbox" name="tabs" class="accordion">
|
||||
<label for="tab-eleven" class="accordion">{% t faq.q11 %}</label>
|
||||
<div class="tab-content">
|
||||
<p>{% t faq.a11 %}</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="tab">
|
||||
<input id="tab-twelve" type="checkbox" name="tabs" class="accordion">
|
||||
<label for="tab-twelve" class="accordion">{% t faq.q12 %}</label>
|
||||
<div class="tab-content">
|
||||
<p>{% t faq.a12-1 %}</p>
|
||||
<p>{% t faq.a12-2 %}</p>
|
||||
<p>{% t faq.a12-3 %}</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="tab">
|
||||
<input id="tab-thirteen" type="checkbox" name="tabs" class="accordion">
|
||||
<label for="tab-thirteen" class="accordion">{% t faq.q13 %}</label>
|
||||
<div class="tab-content">
|
||||
<p>{% t faq.a13 %}</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="tab">
|
||||
<input id="tab-fourteen" type="checkbox" name="tabs" class="accordion">
|
||||
<label for="tab-fourteen" class="accordion">{% t faq.q14 %}</label>
|
||||
<div class="tab-content">
|
||||
<p>{% t faq.a14 %}</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="tab">
|
||||
<input id="tab-fifteen" type="checkbox" name="tabs" class="accordion">
|
||||
<label for="tab-fifteen" class="accordion">{% t faq.q15 %}</label>
|
||||
<div class="tab-content">
|
||||
<p>{% t faq.a15 %}</p>
|
||||
</div>
|
||||
</div>
|
||||
</section>
|
||||
1
img/logo-list.svg
Normal file
1
img/logo-list.svg
Normal file
@ -0,0 +1 @@
|
||||
<svg width="10" height="10" viewBox="0 0 256 256" xmlns="http://www.w3.org/2000/svg" preserveAspectRatio="xMidYMid"><path d="M127.998 0C57.318 0 0 57.317 0 127.999c0 14.127 2.29 27.716 6.518 40.43H44.8V60.733l83.2 83.2 83.198-83.2v107.695h38.282c4.231-12.714 6.521-26.303 6.521-40.43C256 57.314 198.681 0 127.998 0" fill="#F60"/><path d="M108.867 163.062l-36.31-36.311v67.765H18.623c22.47 36.863 63.051 61.48 109.373 61.48s86.907-24.617 109.374-61.48h-53.933V126.75l-36.31 36.31-19.13 19.129-19.128-19.128h-.002z" fill="#4C4C4C"/></svg>
|
||||
|
After Width: | Height: | Size: 536 B |
Loading…
Reference in New Issue
Block a user