Skip to content

Commit

Permalink
Merge pull request #2346 from HardenedSteel/inflation-bug
Browse files Browse the repository at this point in the history
faq: update the inflation bug question
  • Loading branch information
plowsof authored Oct 15, 2024
2 parents 04dcf1f + 2285c3c commit 710388d
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 1 deletion.
2 changes: 2 additions & 0 deletions _i18n/en.yml
Original file line number Diff line number Diff line change
Expand Up @@ -495,6 +495,8 @@ faq:
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.
aabout-auditability: More about supply auditability
adetailed-auditability: Deeper analysis of supply auditability
q13: Is Monero magic and protects 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?
Expand Down
3 changes: 2 additions & 1 deletion get-started/faq/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -253,7 +253,8 @@ meta_descr: faq.intro
<p>{% t faq.a12-1 %}</p>
<p>{% t faq.a12-2 %}</p>
<p>{% t faq.a12-3 %}</p>
<p>{% t faq.additional %} <a href="{{ site.baseurl_root }}/2020/01/17/auditability.html">About supply auditability</a></p>
<p>{% t faq.additional %} <a href="{{ site.baseurl_root }}/2020/01/17/auditability.html">{% t faq.aabout-auditability %}</a></p>
<p>{% t faq.additional %} <a href="https://moneroinflation.com">{% t faq.adetailed-auditability %}</a></p>
</div>
</div>
<div class="tab" id="max-supply">
Expand Down

0 comments on commit 710388d

Please sign in to comment.