mirror of
https://github.com/monero-project/monero-site.git
synced 2024-12-23 03:59:26 +00:00
moneropedia: uniform structure of transaction.md and add cofnig file
This commit is contained in:
erciccione
parent
1f4d65c222
commit
8c4170a6a5
15 changed files with 361 additions and 101 deletions
|
|
@ -1,22 +1,41 @@
|
|||
---
|
||||
summary: 'a cryptographically signed container that details the transfer of Monero to a recipient (or recipients)'
|
||||
terms: ["transaction", "transactions"]
|
||||
summary: "a cryptographically signed container that details the transfer of Monero to a recipient (or recipients)"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
|
||||
### The Basics
|
||||
|
||||
A cryptographically signed container that details the transfer of Monero to a recipient (or recipients).
|
||||
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.
|
||||
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.
|
||||
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).
|
||||
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.
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
|
|
|||
|
|
@ -1,23 +1,44 @@
|
|||
---
|
||||
summary: 'Ein kryptografisch signierter Behälter, der einen Monero-Transfer einem (oder mehreren) Empfänger(n) zuweist.'
|
||||
terms: ["transaction", "transactions", "Transaktion", "Transaktionen"]
|
||||
summary: "Ein kryptografisch signierter Behälter, der einen Monero-Transfer einem (oder mehreren) Empfänger(n) zuweist"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="yes" translationOutdated="no" %}
|
||||
|
||||
### Grundlagen
|
||||
|
||||
Ein kryptografisch signierter Behälter, der einen Monero-Transfer einem (oder mehreren) Empfänger(n) zuweist.
|
||||
Ein kryptografisch signierter Behälter, der einen Monero-Transfer einem
|
||||
(oder mehreren) Empfänger(n) zuweist.
|
||||
|
||||
Die Parameter einer Transaktion enthalten eine oder mehrere Empfängeradressen mit entsprechenden Geldbeträgen und einen Parameter bezüglich der @Ringgröße, welcher die Anzahl der an die Transaktion gebundenen Outputs festlegt. Je mehr Outputs verwendet werden, desto höher kann der Grad an Verschleierung sein. Dies hat jedoch seinen Preis: Da eine Transaktion durch mehr Outputs größer wird, werden die Transaktionsgebühren höher ausfallen.
|
||||
Die Parameter einer Transaktion enthalten eine oder mehrere
|
||||
Empfängeradressen mit entsprechenden Geldbeträgen und einen Parameter
|
||||
bezüglich der @Ringgröße, welcher die Anzahl der an die Transaktion
|
||||
gebundenen Outputs festlegt. Je mehr Outputs verwendet werden, desto höher
|
||||
kann der Grad an Verschleierung sein. Dies hat jedoch seinen Preis: Da eine
|
||||
Transaktion durch mehr Outputs größer wird, werden die Transaktionsgebühren
|
||||
höher ausfallen.
|
||||
|
||||
Die Offline-Erstellung einer Transaktion ist möglich und bietet zusätzliche, die Privatsphäre begünstigende Vorteile.
|
||||
Die Offline-Erstellung einer Transaktion ist möglich und bietet zusätzliche,
|
||||
die Privatsphäre begünstigende Vorteile.
|
||||
|
||||
Eine Transaktion kann durch den Gebrauch einer optionalen Transaktions-ID eindeutig gekennzeichnet werden. Diese wird in der Regel durch einen 32-Byte-Zeichenkette (oder 64 Hexadezimalzeichen) verkörpert.
|
||||
Eine Transaktion kann durch den Gebrauch einer optionalen Transaktions-ID
|
||||
eindeutig gekennzeichnet werden. Diese wird in der Regel durch einen
|
||||
32-Byte-Zeichenkette (oder 64 Hexadezimalzeichen) verkörpert.
|
||||
|
||||
### Ausführliche Informationen
|
||||
|
||||
Jede Transaktion involviert zwei Schlüssel: Einen öffentlichen @Spend-Key und einen öffentlichen @View-Key. Das Ziel eines Outputs einer Transaktion ist genau genommen ein öffentlicher Einmal-Schlüssel, der aus diesen zwei Schlüsseln berechnet wurde.
|
||||
Jede Transaktion involviert zwei Schlüssel: Einen öffentlichen @Spend-Key
|
||||
und einen öffentlichen @View-Key. Das Ziel eines Outputs einer Transaktion
|
||||
ist genau genommen ein öffentlicher Einmal-Schlüssel, der aus diesen zwei
|
||||
Schlüsseln berechnet wurde.
|
||||
|
||||
Wenn ein Wallet nach eingehenden Zahlungen sucht, scannt es jegliche Transaktionen und schaut dabei, ob eine davon für "dich" ist. Dafür werden lediglich dein privater View-Key und dein öffentlicher Spend-Key benötigt. Diese Überprüfung ist unveränderlich und kann nicht gefälscht werden. Du kannst keine Transaktionen empfangen und diese ohne einen zugehörigen privaten View-Key identifizieren.
|
||||
Wenn ein Wallet nach eingehenden Zahlungen sucht, scannt es jegliche
|
||||
Transaktionen und schaut dabei, ob eine davon für "dich" ist. Dafür werden
|
||||
lediglich dein privater View-Key und dein öffentlicher Spend-Key
|
||||
benötigt. Diese Überprüfung ist unveränderlich und kann nicht gefälscht
|
||||
werden. Du kannst keine Transaktionen empfangen und diese ohne einen
|
||||
zugehörigen privaten View-Key identifizieren.
|
||||
|
||||
Um deine Gelder auszugeben, musst du einen privaten Einmal-Spend-Key für diesen Output berechnen. Dies wird fast immer automatisch von der Software der Monero-Wallets übernommen.
|
||||
Um deine Gelder auszugeben, musst du einen privaten Einmal-Spend-Key für
|
||||
diesen Output berechnen. Dies wird fast immer automatisch von der Software
|
||||
der Monero-Wallets übernommen.
|
||||
|
|
|
|||
|
|
@ -4,6 +4,7 @@ summary: "a cryptographically signed container that details the transfer of Mone
|
|||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
|
||||
### The Basics
|
||||
|
||||
A cryptographically signed container that details the transfer of Monero to a recipient (or recipients).
|
||||
|
|
@ -15,6 +16,7 @@ It is possible to form a transaction offline, which offers additional privacy be
|
|||
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.
|
||||
|
|
|
|||
|
|
@ -1,22 +1,41 @@
|
|||
---
|
||||
summary: 'a cryptographically signed container that details the transfer of Monero to a recipient (or recipients)'
|
||||
terms: ["transaction", "transactions"]
|
||||
summary: "a cryptographically signed container that details the transfer of Monero to a recipient (or recipients)"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
|
||||
### The Basics
|
||||
|
||||
A cryptographically signed container that details the transfer of Monero to a recipient (or recipients).
|
||||
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.
|
||||
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.
|
||||
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).
|
||||
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.
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
|
|
|||
|
|
@ -1,22 +1,44 @@
|
|||
---
|
||||
summary: 'Un conteneur signé cryptographiquement qui détaille le transfert de Moneroj à un destinataire (ou des destinataires).'
|
||||
terms: ["transaction", "transactions"]
|
||||
summary: "un conteneur signé cryptographiquement qui détaille le transfert de Moneroj à un destinataire (ou des destinataires)"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="yes" translationOutdated="no" %}
|
||||
|
||||
### Les Bases
|
||||
|
||||
Un conteneur signé cryptographiquement qui détaille le transfert de Moneroj à un destinataire (ou des destinataires).
|
||||
Un conteneur signé cryptographiquement qui détaille le transfert de Moneroj
|
||||
à un destinataire (ou des destinataires).
|
||||
|
||||
Les paramètres d'une transaction contiennent une ou plusieurs adresses de destinataires avec le montant des fonds correspondants et un paramètre de @taille-de-cercle qui spécifie le nombre de sorties attachées à la transaction. Plus le nombre de sorties est important, plus grand est le degré d'obscurcissement possible, mais cela a un coût. Comme une transaction devient plus grande avec plus de sorties, les frais de transaction seront plus élevés.
|
||||
Les paramètres d'une transaction contiennent une ou plusieurs adresses de
|
||||
destinataires avec le montant des fonds correspondants et un paramètre de
|
||||
@taille-de-cercle qui spécifie le nombre de sorties attachées à la
|
||||
transaction. Plus le nombre de sorties est important, plus grand est le
|
||||
degré d'obscurcissement possible, mais cela a un coût. Comme une transaction
|
||||
devient plus grande avec plus de sorties, les frais de transaction seront
|
||||
plus élevés.
|
||||
|
||||
Il est possible de concevoir une transaction hors-ligne, ce qui permet une confidentialité supplémentaire.
|
||||
Il est possible de concevoir une transaction hors-ligne, ce qui permet une
|
||||
confidentialité supplémentaire.
|
||||
|
||||
Une transaction peut être identifiée de façon unique en utilisant un ID de transaction optionnel, qui est habituellement représenté par une chaîne de caractères de 32 octets (64 caractères hexadécimaux).
|
||||
Une transaction peut être identifiée de façon unique en utilisant un ID de
|
||||
transaction optionnel, qui est habituellement représenté par une chaîne de
|
||||
caractères de 32 octets (64 caractères hexadécimaux).
|
||||
|
||||
### Informations détaillées
|
||||
Chaque transaction nécessite deux clefs : une @clef-de-dépense publique et une @clef-d'audit publique. La destination d'une sortie de transaction est en réalité une clef publique à usage unique calculée à partir de ces deux clefs.
|
||||
|
||||
Lorsqu'un portefeuille est à la recherche de transactions entrantes, chaque transaction est scannée pour voir si elle est pour "vous". Cela ne nécessite que votre clef privée d'autit et votre clef de dépense publique, et cette vérification est immuable et ne peut pas être falsifiée. Vous ne pouvez pas recevoir de transactions et les identifier sans la clef privée d'audit correspondante.
|
||||
Chaque transaction nécessite deux clefs : une @clef-de-dépense publique et
|
||||
une @clef-d'audit publique. La destination d'une sortie de transaction est
|
||||
en réalité une clef publique à usage unique calculée à partir de ces deux
|
||||
clefs.
|
||||
|
||||
Afin de dépenser les fonds que vous avez, vous devez calculer une clef de dépense privée à usage unique pour cette sortie. Ce qui est la plupart du temps fait automatiquement par le logiciel de portefeuille Monero.
|
||||
Lorsqu'un portefeuille est à la recherche de transactions entrantes, chaque
|
||||
transaction est scannée pour voir si elle est pour "vous". Cela ne nécessite
|
||||
que votre clef privée d'autit et votre clef de dépense publique, et cette
|
||||
vérification est immuable et ne peut pas être falsifiée. Vous ne pouvez pas
|
||||
recevoir de transactions et les identifier sans la clef privée d'audit
|
||||
correspondante.
|
||||
|
||||
Afin de dépenser les fonds que vous avez, vous devez calculer une clef de
|
||||
dépense privée à usage unique pour cette sortie. Ce qui est la plupart du
|
||||
temps fait automatiquement par le logiciel de portefeuille Monero.
|
||||
|
|
|
|||
|
|
@ -1,22 +1,41 @@
|
|||
---
|
||||
terms: ["transaction", "transactions", "transazione", "transazioni"]
|
||||
summary: "a cryptographically signed container that details the transfer of Monero to a recipient (or recipients)"
|
||||
summary: 'a cryptographically signed container that details the transfer of Monero to a recipient (or recipients)'
|
||||
terms: ["transaction", "transactions"]
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
|
||||
### The Basics
|
||||
|
||||
A cryptographically signed container that details the transfer of Monero to a recipient (or recipients).
|
||||
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.
|
||||
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.
|
||||
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).
|
||||
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.
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
|
|
|||
|
|
@ -1,23 +1,40 @@
|
|||
---
|
||||
summary: 'En kryptografisk signert beholder som redegjør for overføringen av Monero til en mottaker (eller mottakere).'
|
||||
terms: ["transaction", "transactions", "transaksjon", "transaksjoner"]
|
||||
summary: "en kryptografisk signert beholder som redegjør for overføringen av Monero til en mottaker (eller mottakere)"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="yes" translationOutdated="no" %}
|
||||
|
||||
### Det grunnleggende
|
||||
|
||||
En kryptografisk signert beholder som redegjør for overføringen av Monero til en mottaker (eller mottakere).
|
||||
En kryptografisk signert beholder som redegjør for overføringen av Monero
|
||||
til en mottaker (eller mottakere).
|
||||
|
||||
Parameterne til en transaksjon innholder én eller flere mottakeradresser med
|
||||
tilhørende beløp og én parameter i @ringstørrelse som spesifiserer antall
|
||||
utdata som er bundet til transaksjonen. Jo flere utdata som brukes, jo
|
||||
høyere grad av forkludring er mulig – men det har sin pris. Siden en
|
||||
transaksjon blir større med mer utdata, blir transaksjonskostnaden høyere.
|
||||
|
||||
Parameterne til en transaksjon innholder én eller flere mottakeradresser med tilhørende beløp og én parameter i @ringstørrelse som spesifiserer antall utdata som er bundet til transaksjonen. Jo flere utdata som brukes, jo høyere grad av forkludring er mulig – men det har sin pris. Siden en transaksjon blir større med mer utdata, blir transaksjonskostnaden høyere.
|
||||
Det er mulig å lage en transaksjon i frakoblet tilstand, noe som tilbyr
|
||||
ytterligere personvernfordeler.
|
||||
|
||||
Det er mulig å lage en transaksjon i frakoblet tilstand, noe som tilbyr ytterligere personvernfordeler.
|
||||
|
||||
En transaksjon kan identifiseres unikt ved å bruke en valgfri transaksjons-ID, som vanligvis representeres av en 32-bits streng (64 heksadesimale tegn).
|
||||
En transaksjon kan identifiseres unikt ved å bruke en valgfri
|
||||
transaksjons-ID, som vanligvis representeres av en 32-bits streng (64
|
||||
heksadesimale tegn).
|
||||
|
||||
### Inngående informasjon
|
||||
Hver transaksjon trekker inn to nøkler: en offentlig @forbruksnøkkel og en offentlig @visningsnøkkel. Destinasjonen for en utdata i en transaksjon er faktisk en engangs offentlig nøkkel som er bereget ut fra disse to nøklene.
|
||||
|
||||
Når en lommebok skanner etter innkommende transaksjoner, skannes hver transaksjon for å se om den er til «deg». Dette krever kun din private visningsnøkkel og din offentlige forbruksnøkkel, og denne sjekken er uforanderlig og kan ikke forfalskes. Du kan ikke motta transaksjoner og identifisere dem uten en tilhørende privat visningsnøkkel.
|
||||
Hver transaksjon trekker inn to nøkler: en offentlig @forbruksnøkkel og en
|
||||
offentlig @visningsnøkkel. Destinasjonen for en utdata i en transaksjon er
|
||||
faktisk en engangs offentlig nøkkel som er bereget ut fra disse to nøklene.
|
||||
|
||||
For å bruke midlene, må du kalkulere en engangs privat forbruksnøkkel for den utdataen. Dette gjøres nesten alltid automatisk av programvaren i Monero-lommeboken din.
|
||||
Når en lommebok skanner etter innkommende transaksjoner, skannes hver
|
||||
transaksjon for å se om den er til «deg». Dette krever kun din private
|
||||
visningsnøkkel og din offentlige forbruksnøkkel, og denne sjekken er
|
||||
uforanderlig og kan ikke forfalskes. Du kan ikke motta transaksjoner og
|
||||
identifisere dem uten en tilhørende privat visningsnøkkel.
|
||||
|
||||
For å bruke midlene, må du kalkulere en engangs privat forbruksnøkkel for
|
||||
den utdataen. Dette gjøres nesten alltid automatisk av programvaren i
|
||||
Monero-lommeboken din.
|
||||
|
|
|
|||
|
|
@ -1,22 +1,41 @@
|
|||
---
|
||||
summary: 'a cryptographically signed container that details the transfer of Monero to a recipient (or recipients)'
|
||||
terms: ["transaction", "transactions"]
|
||||
summary: "a cryptographically signed container that details the transfer of Monero to a recipient (or recipients)"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
|
||||
### The Basics
|
||||
|
||||
A cryptographically signed container that details the transfer of Monero to a recipient (or recipients).
|
||||
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.
|
||||
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.
|
||||
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).
|
||||
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.
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
|
|
|||
|
|
@ -1,21 +1,42 @@
|
|||
---
|
||||
summary: 'Kryptograficznie podpisany zbiornik, który wyszczególnia transfer Monero do odbiorcy lub odbiorców.'
|
||||
terms: ["transaction", "transactions", "transakcja", "transakcję", "transakcji", "transakcją", "transakcje", "transakcjom", "transakcjami"]
|
||||
summary: "Kryptograficznie podpisany zbiornik, który wyszczególnia transfer Monero do odbiorcy lub odbiorców."
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="yes" translationOutdated="no" %}
|
||||
|
||||
### Podstawy
|
||||
|
||||
Kryptograficznie podpisany zbiornik, który wyszczególnia transfer Monero do odbiorcy lub odbiorców.
|
||||
Kryptograficznie podpisany zbiornik, który wyszczególnia transfer Monero do
|
||||
odbiorcy lub odbiorców.
|
||||
|
||||
Parametry transakcji zawierają jeden lub więcej adresów odbiorcy wraz z odpowiednimi kwotami oraz parametr @rozmiar-pierścienia, który określa liczbę obcych wyjść powiązanych z transakcją. Im więcej wyjść, tym bardziej możliwy wyższy poziom maskowania, jednak wiąże się to z pewnym kosztem. Ponieważ transakcje stają się coraz większe i z większą liczbą wyjść, opłaty za nie rosną. Możliwe jest także tworzenie transakcji off-line, które daje ogromną korzyść dla prywatności.
|
||||
Parametry transakcji zawierają jeden lub więcej adresów odbiorcy wraz z
|
||||
odpowiednimi kwotami oraz parametr @rozmiar-pierścienia, który określa
|
||||
liczbę obcych wyjść powiązanych z transakcją. Im więcej wyjść, tym bardziej
|
||||
możliwy wyższy poziom maskowania, jednak wiąże się to z pewnym
|
||||
kosztem. Ponieważ transakcje stają się coraz większe i z większą liczbą
|
||||
wyjść, opłaty za nie rosną.
|
||||
|
||||
Transakcja może być zidentyfikowana jedynie przy użyciu opcjonalnego numeru identyfikacji transakcji, który przeważnie jest 32-bajtowym ciągiem (64 znaków heksadecymalnych).
|
||||
Możliwe jest także tworzenie transakcji off-line, które daje ogromną korzyść
|
||||
dla prywatności.
|
||||
|
||||
Transakcja może być zidentyfikowana jedynie przy użyciu opcjonalnego numeru
|
||||
identyfikacji transakcji, który przeważnie jest 32-bajtowym ciągiem (64
|
||||
znaków heksadecymalnych).
|
||||
|
||||
### Szczegółowe informacje
|
||||
|
||||
Każda transakcja wiąże się z dwoma kluczami: publicznym @kluczem-wydawania i publicznym @kluczem-widoczności. Celem wyjścia w transakcji jest jednorazowy klucz publiczny, złożony z tych dwóch kluczy.
|
||||
Każda transakcja wiąże się z dwoma kluczami: publicznym @kluczem-wydawania i
|
||||
publicznym @kluczem-widoczności. Celem wyjścia w transakcji jest jednorazowy
|
||||
klucz publiczny, złożony z tych dwóch kluczy.
|
||||
|
||||
Gdy portfel dokonuje skanowania w poszukiwaniu płatności przychodzących, wszystkie transakcje są weryfikowane czy są przeznaczone dla ciebie. Wymaga to jedynie twojego prywatnego klucza widoczności i twojego publicznego klucza wydawania, a sprawdzanie to jest niezmienne i nie może być sfałszowane. Nie możesz otrzymać płatności i zidentyfikować jej bez odpowiedniego prywatnego klucza widoczności.
|
||||
Gdy portfel dokonuje skanowania w poszukiwaniu płatności przychodzących,
|
||||
wszystkie transakcje są weryfikowane czy są przeznaczone dla ciebie. Wymaga
|
||||
to jedynie twojego prywatnego klucza widoczności i twojego publicznego
|
||||
klucza wydawania, a sprawdzanie to jest niezmienne i nie może być
|
||||
sfałszowane. Nie możesz otrzymać płatności i zidentyfikować jej bez
|
||||
odpowiedniego prywatnego klucza widoczności.
|
||||
|
||||
Aby wydać środki ze swojego konta, musisz stworzyć jednorazowy prywatny klucz wydawania dla konkretnego wyjścia. Prawie zawsze jest to wykonywane automatycznie przez oprogramowanie portfela Monero.
|
||||
Aby wydać środki ze swojego konta, musisz stworzyć jednorazowy prywatny
|
||||
klucz wydawania dla konkretnego wyjścia. Prawie zawsze jest to wykonywane
|
||||
automatycznie przez oprogramowanie portfela Monero.
|
||||
|
|
|
|||
|
|
@ -1,22 +1,41 @@
|
|||
---
|
||||
terms: ["transaction", "transactions", "transazione", "transazioni"]
|
||||
summary: "a cryptographically signed container that details the transfer of Monero to a recipient (or recipients)"
|
||||
summary: 'a cryptographically signed container that details the transfer of Monero to a recipient (or recipients)'
|
||||
terms: ["transaction", "transactions"]
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
|
||||
### The Basics
|
||||
|
||||
A cryptographically signed container that details the transfer of Monero to a recipient (or recipients).
|
||||
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.
|
||||
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.
|
||||
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).
|
||||
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.
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
|
|
|||
|
|
@ -1,22 +1,44 @@
|
|||
---
|
||||
summary: 'Криптографически подписанный контейнер, в котором содержится подробная информация по передаче Monero получателю (или получателям).'
|
||||
terms: ["transaction", "transactions", "транзакций", "транзакции", "транзакция"]
|
||||
summary: "Криптографически подписанный контейнер, в котором содержится подробная информация по передаче Monero получателю (или получателям)."
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="yes" translationOutdated="no" %}
|
||||
|
||||
### Основная информация
|
||||
|
||||
Криптографически подписанный контейнер, в котором содержится подробная информация по передаче Monero получателю (или получателям).
|
||||
Криптографически подписанный контейнер, в котором содержится подробная
|
||||
информация по передаче Monero получателю (или получателям).
|
||||
|
||||
Среди параметров транзакции содержатся один или несколько адресов получателя с соответствующими суммами средств, а также параметр размера кольца, который указывает количество выходов, связанных с транзакцией. Чем больше выходов используется, тем выше уровень защиты. Но это имеет свою цену. Так как при включении большего количества выходов транзакция становится больше, растёт и размер комиссии за проведение транзакции.
|
||||
Среди параметров транзакции содержатся один или несколько адресов получателя
|
||||
с соответствующими суммами средств, а также параметр размера кольца, который
|
||||
указывает количество выходов, связанных с транзакцией. Чем больше выходов
|
||||
используется, тем выше уровень защиты. Но это имеет свою цену. Так как при
|
||||
включении большего количества выходов транзакция становится больше, растёт и
|
||||
размер комиссии за проведение транзакции.
|
||||
|
||||
Можно создать офлайн транзакцию, что даёт дополнительные преимущества с точки зрения анонимности.
|
||||
Можно создать офлайн транзакцию, что даёт дополнительные преимущества с
|
||||
точки зрения анонимности.
|
||||
|
||||
Транзакция может быть уникально идентифицирована. Для этого используется опциональный идентификатор транзакции (Transaction ID), который, как правило, представляет собой 32-байтную строку (64 шестнадцатеричных символа).
|
||||
Транзакция может быть уникально идентифицирована. Для этого используется
|
||||
опциональный идентификатор транзакции (Transaction ID), который, как
|
||||
правило, представляет собой 32-байтную строку (64 шестнадцатеричных
|
||||
символа).
|
||||
|
||||
### Углублённая информация
|
||||
При проведении каждой транзакции используется два ключа: публичный @ключ-траты и публичный @ключ-просмотра. Адрес назначения для выхода транзакции фактически является одноразовым публичным ключом, который вычисляется на основе этих двух ключей.
|
||||
|
||||
Когда кошелёк сканирует входящие транзакции, то каждая транзакция сканируется на предмет того, направлена ли она именно вам. Для этого необходимы только ваш приватный ключ просмотра и ваш публичный ключ траты. Такая проверка проводится неизменно, и её нельзя подделать. Вы не можете принять транзакции и идентифицировать их, не имея соответствующего приватного ключа просмотра.
|
||||
При проведении каждой транзакции используется два ключа: публичный
|
||||
@ключ-траты и публичный @ключ-просмотра. Адрес назначения для выхода
|
||||
транзакции фактически является одноразовым публичным ключом, который
|
||||
вычисляется на основе этих двух ключей.
|
||||
|
||||
Чтобы потратить средства, вам понадобится вычислить одноразовый приватный ключ траты для данного конкретного выхода. Это практически всегда делается автоматически программным обеспечением кошелька Monero.
|
||||
Когда кошелёк сканирует входящие транзакции, то каждая транзакция
|
||||
сканируется на предмет того, направлена ли она именно вам. Для этого
|
||||
необходимы только ваш приватный ключ просмотра и ваш публичный ключ
|
||||
траты. Такая проверка проводится неизменно, и её нельзя подделать. Вы не
|
||||
можете принять транзакции и идентифицировать их, не имея соответствующего
|
||||
приватного ключа просмотра.
|
||||
|
||||
Чтобы потратить средства, вам понадобится вычислить одноразовый приватный
|
||||
ключ траты для данного конкретного выхода. Это практически всегда делается
|
||||
автоматически программным обеспечением кошелька Monero.
|
||||
|
|
|
|||
|
|
@ -1,22 +1,41 @@
|
|||
---
|
||||
summary: 'a cryptographically signed container that details the transfer of Monero to a recipient (or recipients)'
|
||||
terms: ["transaction", "transactions"]
|
||||
summary: "a cryptographically signed container that details the transfer of Monero to a recipient (or recipients)"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
|
||||
### The Basics
|
||||
|
||||
A cryptographically signed container that details the transfer of Monero to a recipient (or recipients).
|
||||
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.
|
||||
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.
|
||||
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).
|
||||
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.
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
|
|
|||
|
|
@ -1,14 +1,23 @@
|
|||
---
|
||||
summary: 交易的参数包含一个或多个具有相应资金数额的收件人地址和一个@环尺寸参数，该参数指定绑定到交易的输出数量。使用的输出越多，混淆的程度就越高，但这是有代价的。因为交易越大输出越多，交易费也就越高。
|
||||
terms: ["transaction", "transactions"]
|
||||
summary: "a cryptographically signed container that details the transfer of Monero to a recipient (or recipients)"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="yes" translationOutdated="no" %}
|
||||
{% include disclaimer.html translated="yes" translationOutdated="yes" %}
|
||||
|
||||
### 基础知识
|
||||
|
||||
交易的参数包含一个或多个具有相应资金数额的收件人地址和一个@环尺寸参数，该参数指定绑定到交易的输出数量。使用的输出越多，混淆的程度就越高，但这是有代价的。因为交易越大输出越多，交易费也就越高。
|
||||
|
||||
可以离线产生交易，这提供了额外的隐私性效益。
|
||||
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.
|
||||
|
||||
惟一识别交易的方法是使用可选的支付ID，该ID通常由32字节字符串（64个十六进制字符）。
|
||||
|
||||
|
|
|
|||
|
|
@ -1,22 +1,41 @@
|
|||
---
|
||||
summary: 'a cryptographically signed container that details the transfer of Monero to a recipient (or recipients)'
|
||||
terms: ["transaction", "transactions"]
|
||||
summary: "a cryptographically signed container that details the transfer of Monero to a recipient (or recipients)"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
|
||||
### The Basics
|
||||
|
||||
A cryptographically signed container that details the transfer of Monero to a recipient (or recipients).
|
||||
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.
|
||||
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.
|
||||
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).
|
||||
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.
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
|
|
|||
13
po/moneropedia/transaction.config
Normal file
13
po/moneropedia/transaction.config
Normal file
|
|
@ -0,0 +1,13 @@
|
|||
[po4a_langs] es it pl fr ar ru de nl pt-br tr zh-cn zh-tw nb-no
|
||||
[po4a_paths] ../_i18n/en/resources/moneropedia/weblate/transaction.pot $lang:../_i18n/$lang/resources/moneropedia/weblate/transaction.po
|
||||
|
||||
[options] opt:"--keep=0"
|
||||
[options] opt:"--localized-charset=UTF-8"
|
||||
[options] opt:"--master-charset=UTF-8"
|
||||
[options] opt:"--master-language=en_US"
|
||||
[options] opt:"--msgmerge-opt='--no-wrap'"
|
||||
[options] opt:"--wrap-po=newlines"
|
||||
|
||||
[po4a_alias:markdown] text opt:"--option markdown"
|
||||
|
||||
[type: markdown] ../_i18n/en/resources/moneropedia/transaction.md $lang:../_i18n/$lang/resources/moneropedia/transaction.md
|
||||
Loading…
Reference in a new issue