monero-project/monero-site
monero-project/monero-site
1
0
Fork 0
mirror of https://github.com/monero-project/monero-site.git synced 2025-01-11 21:34:32 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Merge pull request #66 from dnaleor/patch-1

Browse source 
Patch 1
This commit is contained in:
Riccardo Spagni 2015-10-26 17:55:31 +02:00
commit 433afb648b
2 changed files with 5 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
knowledge-base/moneropedia/ringsignatures.md
View file

@ -6,5 +6,8 @@ summary: "a group of cryptographic signatures with at least one real participant
---
### The Basics
Ring signatures make sure individual transaction outputs on the blockchain can’t be traced. A ring signature is a group of cryptographic signatures with at least one real participant, but there is no way to tell which in the group is the real one as they all appear valid, while the key image prevents double spends. When sending a transaction, you select some random transaction outputs on the blockchain and mix those with your own “real coins”. Mixing of coins is enforced across the network, making all coins “equal”. Because every transaction output has plausible deniability on their state (spent or unspent), there are no fungibility issues with monero
{{ page.summary | capitalize }}.
To read how Monero gives you a privacy by default (unlinkability), see @stealth-addresses.
{{ page.summary | capitalize }}.

2
knowledge-base/moneropedia/transaction.md
View file

@ -9,7 +9,7 @@ summary: "a cryptographically signed container that details the transfer of Mone
{{ page.summary | capitalize }}.
A transaction's parameters are one or more recipient addresses with the corresponding amounts of funds to send to them, and a `mixin_count` parameter that specifies the amount of outputs the transaction will have mixed in. Higher amounts of `mixin_count` offer more anonymity, but that comes with a cost, since the transaction gets larger and therefore the transaction fees get higher as well.
A transaction's parameters are one or more recipient addresses with the corresponding amounts of funds to send to them, and a `mixin_count` parameter that specifies the amount of outputs the transaction will have mixed in. Higher amounts of `mixin_count` offer more anonymity, but that comes with a cost, since the transaction gets larger and therefore the transaction fees get higher as well. The fact that this mixing can be done offline is a huge benefit for privacy.
A transaction is uniquely identified by a Transaction ID, which is usually represented as a 32-byte string (64 hexadecimal characters).