mirror of
https://github.com/monero-project/monero-site.git
synced 2024-11-16 15:58:16 +00:00
moneropedia: uniform structure of paymentid.md and add config file
This commit is contained in:
erciccione
parent
b2775d5316
commit
4905963499
15 changed files with 249 additions and 68 deletions
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
summary: 'an optional flag that is added to identify transactions to merchants, consisting of 64 hexadecimal characters'
|
||||
terms: ["payment-ID", "payment-IDs"]
|
||||
summary: "an optional flag that is added to identify transactions to merchants, consisting of 64 hexadecimal characters"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
|
|
@ -9,16 +9,28 @@ summary: "an optional flag that is added to identify transactions to merchants,
|
|||
|
||||
### The Basics
|
||||
|
||||
Payment ID is an **arbitrary** and **optional** transaction attachment that consists of 32 bytes (64 hexadecimal characters) or 8 bytes (in the case of integrated addresses).
|
||||
Payment ID is an **arbitrary** and **optional** transaction attachment that
|
||||
consists of 32 bytes (64 hexadecimal characters) or 8 bytes (in the case of
|
||||
integrated addresses).
|
||||
|
||||
The Payment ID is usually used to identify transactions to merchants and exchanges: Given the intrinsic privacy features built into Monero, where a single public address is usually used for incoming transactions, the Payment ID is especially useful to tie incoming payments with user accounts.
|
||||
The Payment ID is usually used to identify transactions to merchants and
|
||||
exchanges: Given the intrinsic privacy features built into Monero, where a
|
||||
single public address is usually used for incoming transactions, the Payment
|
||||
ID is especially useful to tie incoming payments with user accounts.
|
||||
|
||||
### Compact Payment IDs and Integrated Addresses
|
||||
|
||||
Since the 0.9 Hydrogen Helix version, Payment IDs can be encrypted and embedded in a payment address. The Payment IDs of this type should be 64-bits and are encrypted with a random one-time key known only to the sender and receiver.
|
||||
Since the 0.9 Hydrogen Helix version, Payment IDs can be encrypted and
|
||||
embedded in a payment address. The Payment IDs of this type should be
|
||||
64-bits and are encrypted with a random one-time key known only to the
|
||||
sender and receiver.
|
||||
|
||||
### Creating a Payment ID
|
||||
It is recommended to use the official wallet's `integrated_address` command to automatically generate Integrated Addresses that contain Compact Payment IDs. If you want to use the command line, you can generate Payment IDs as follows:
|
||||
|
||||
It is recommended to use the official wallet's `integrated_address` command
|
||||
to automatically generate Integrated Addresses that contain Compact Payment
|
||||
IDs. If you want to use the command line, you can generate Payment IDs as
|
||||
follows:
|
||||
|
||||
Creating a compact Payment ID for an Integrated Address:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
summary: 'Optionales Flag, welches zur Identifizierung von Transaktionen an Händler hinzugefügt wird und aus 64 Hexadezimalzeichen besteht'
|
||||
terms: ["payment-ID", "payment-IDs", "Zahlungs-ID", "Zahlungs-IDs"]
|
||||
summary: "Optionales Flag, welches zur Identifizierung von Transaktionen an Händler hinzugefügt wird und aus 64 Hexadezimalzeichen besteht"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="yes" translationOutdated="no" %}
|
||||
|
|
@ -9,16 +9,31 @@ summary: "Optionales Flag, welches zur Identifizierung von Transaktionen an Hän
|
|||
|
||||
### Grundlagen
|
||||
|
||||
Eine Zahlungs-ID ist ein **beliebiger** und **optionaler** Transaktionsanhang, der aus 32 Bytes (64 Hexadezimalzeichen) oder (im Falle integrierter Adressen) acht Bytes besteht.
|
||||
Eine Zahlungs-ID ist ein **beliebiger** und **optionaler**
|
||||
Transaktionsanhang, der aus 32 Bytes (64 Hexadezimalzeichen) oder (im Falle
|
||||
integrierter Adressen) acht Bytes besteht.
|
||||
|
||||
Für gewöhnlich wird die Zahlungs-ID zur Identifizierung von an Händler und Börsen gehenden Transaktionen verwendet. In Anbetracht der in Monero integrierten immanenten Privatsphärefunktionen (normalerweise wird für eingehende Transaktionen eine einzelne öffentliche Adresse genutzt) ist die Zahlungs-ID besonders nützlich, um eingehende Zahlungen mit Nutzerkonten zu verknüpfen.
|
||||
Für gewöhnlich wird die Zahlungs-ID zur Identifizierung von an Händler und
|
||||
Börsen gehenden Transaktionen verwendet. In Anbetracht der in Monero
|
||||
integrierten immanenten Privatsphärefunktionen (normalerweise wird für
|
||||
eingehende Transaktionen eine einzelne öffentliche Adresse genutzt) ist die
|
||||
Zahlungs-ID besonders nützlich, um eingehende Zahlungen mit Nutzerkonten zu
|
||||
verknüpfen.
|
||||
|
||||
### Kompakte Zahlungs-IDs und integrierte Adressen
|
||||
|
||||
Seit der 0.9-Hydrogen-Helix-Version können Zahlungs-IDs verschlüsselt und in eine Zahlungsadresse eingebunden werden. Zahlungs-IDs dieser Art sollten eine Länge von 64 Bits haben; sie sind mit einem zufälligen Einmal-Schlüssel, der nur dem Sender und dem Empfänger bekannt ist, verschlüsselt.
|
||||
Seit der 0.9-Hydrogen-Helix-Version können Zahlungs-IDs verschlüsselt und in
|
||||
eine Zahlungsadresse eingebunden werden. Zahlungs-IDs dieser Art sollten
|
||||
eine Länge von 64 Bits haben; sie sind mit einem zufälligen
|
||||
Einmal-Schlüssel, der nur dem Sender und dem Empfänger bekannt ist,
|
||||
verschlüsselt.
|
||||
|
||||
### Erstellen einer Zahlungs-ID
|
||||
Es wird empfohlen, den `integrated_address`-Befehl des offiziellen Wallets zu verwenden, welcher automatisch integrierte Adressen generiert, die eine kompakte Zahlungs-ID enthalten. Wenn du die Befehlszeile nutzen möchtest, kannst du Zahlungs-IDs wie folgt generieren:
|
||||
|
||||
Es wird empfohlen, den `integrated_address`-Befehl des offiziellen Wallets
|
||||
zu verwenden, welcher automatisch integrierte Adressen generiert, die eine
|
||||
kompakte Zahlungs-ID enthalten. Wenn du die Befehlszeile nutzen möchtest,
|
||||
kannst du Zahlungs-IDs wie folgt generieren:
|
||||
|
||||
Erstellen einer kompakten Zahlungs-ID für eine integrierte Adresse:
|
||||
|
||||
|
|
@ -26,4 +41,4 @@ Erstellen einer kompakten Zahlungs-ID für eine integrierte Adresse:
|
|||
|
||||
Erstellen einer herkömmlichen Zahlungs-ID:
|
||||
|
||||
```# openssl rand -hex 32```
|
||||
```# openssl rand -hex 32```
|
||||
|
|
|
|||
|
|
@ -4,6 +4,7 @@ summary: "an optional flag that is added to identify transactions to merchants,
|
|||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
|
||||
*Note:* Long Payment IDs have been removed since release 0.15; it's not possible to use them anymore. More info in the [blog post]({{ site.baseurl_root }}/2019/06/04/Long-Payment-ID-Deprecation.html) that announced their deprecation.
|
||||
|
||||
### The Basics
|
||||
|
|
@ -17,6 +18,7 @@ The Payment ID is usually used to identify transactions to merchants and exchang
|
|||
Since the 0.9 Hydrogen Helix version, Payment IDs can be encrypted and embedded in a payment address. The Payment IDs of this type should be 64-bits and are encrypted with a random one-time key known only to the sender and receiver.
|
||||
|
||||
### Creating a Payment ID
|
||||
|
||||
It is recommended to use the official wallet's `integrated_address` command to automatically generate Integrated Addresses that contain Compact Payment IDs. If you want to use the command line, you can generate Payment IDs as follows:
|
||||
|
||||
Creating a compact Payment ID for an Integrated Address:
|
||||
|
|
|
|||
|
|
@ -1,24 +1,36 @@
|
|||
---
|
||||
summary: 'an optional flag that is added to identify transactions to merchants, consisting of 64 hexadecimal characters'
|
||||
terms: ["payment-ID", "payment-IDs"]
|
||||
summary: "an optional flag that is added to identify transactions to merchants, consisting of 64 hexadecimal characters"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
|
||||
*Note:* Long Payment IDs have been removed since release 0.15; it's not possible to use them anymore. More info in the [blog post]({{ site.baseurl_root }}/2019/06/04/Long-Payment-ID-Deprecation.html) that announced their deprecation.
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
Payment ID is an **arbitrary** and **optional** transaction attachment that consists of 32 bytes (64 hexadecimal characters) or 8 bytes (in the case of integrated addresses).
|
||||
Payment ID is an **arbitrary** and **optional** transaction attachment that
|
||||
consists of 32 bytes (64 hexadecimal characters) or 8 bytes (in the case of
|
||||
integrated addresses).
|
||||
|
||||
The Payment ID is usually used to identify transactions to merchants and exchanges: Given the intrinsic privacy features built into Monero, where a single public address is usually used for incoming transactions, the Payment ID is especially useful to tie incoming payments with user accounts.
|
||||
The Payment ID is usually used to identify transactions to merchants and
|
||||
exchanges: Given the intrinsic privacy features built into Monero, where a
|
||||
single public address is usually used for incoming transactions, the Payment
|
||||
ID is especially useful to tie incoming payments with user accounts.
|
||||
|
||||
### Compact Payment IDs and Integrated Addresses
|
||||
|
||||
Since the 0.9 Hydrogen Helix version, Payment IDs can be encrypted and embedded in a payment address. The Payment IDs of this type should be 64-bits and are encrypted with a random one-time key known only to the sender and receiver.
|
||||
Since the 0.9 Hydrogen Helix version, Payment IDs can be encrypted and
|
||||
embedded in a payment address. The Payment IDs of this type should be
|
||||
64-bits and are encrypted with a random one-time key known only to the
|
||||
sender and receiver.
|
||||
|
||||
### Creating a Payment ID
|
||||
It is recommended to use the official wallet's `integrated_address` command to automatically generate Integrated Addresses that contain Compact Payment IDs. If you want to use the command line, you can generate Payment IDs as follows:
|
||||
|
||||
It is recommended to use the official wallet's `integrated_address` command
|
||||
to automatically generate Integrated Addresses that contain Compact Payment
|
||||
IDs. If you want to use the command line, you can generate Payment IDs as
|
||||
follows:
|
||||
|
||||
Creating a compact Payment ID for an Integrated Address:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,23 +1,38 @@
|
|||
---
|
||||
summary: 'Une option supplémentaire que est ajouté pour identifier les transactions avec les commerçants, se composant de 64 caractères hexadécimaux'
|
||||
terms: ["payment-ID", "payment-IDs", "ID-de-paiement", IDs-de-paiement]
|
||||
summary: "Une option supplémentaire que est ajouté pour identifier les transactions avec les commerçants, se composant de 64 caractères hexadécimaux"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="yes" translationOutdated="yes" %}
|
||||
|
||||
*Note:* Long Payment IDs have been removed since release 0.15; it's not possible to use them anymore. More info in the [blog post]({{ site.baseurl_root }}/2019/06/04/Long-Payment-ID-Deprecation.html) that announced their deprecation.
|
||||
|
||||
### Les Bases
|
||||
|
||||
L'ID de transaction est une annexe **arbitraire** et **optionnelle** d'une transaction qui se compose de 32 octets (64 caractères hexadécimaux) ou 8 octets (dans le cas d'une adresse intégrée).
|
||||
L'ID de transaction est une annexe **arbitraire** et **optionnelle** d'une
|
||||
transaction qui se compose de 32 octets (64 caractères hexadécimaux) ou 8
|
||||
octets (dans le cas d'une adresse intégrée).
|
||||
|
||||
L'ID de paiement est habituellement utilisé pour identifier des transactions auprès de commerçants ou bourses : A cause des fonctionnalité de confidentialités intrinsèques de Monero, ou une seule adresse publique est habituellement utilisée pour les transactions entrantes, l'ID de paiement est particulièrement utile pour lier les paiements entrant à des comptes utilisateurs.
|
||||
L'ID de paiement est habituellement utilisé pour identifier des transactions
|
||||
auprès de commerçants ou bourses : A cause des fonctionnalité de
|
||||
confidentialités intrinsèques de Monero, ou une seule adresse publique est
|
||||
habituellement utilisée pour les transactions entrantes, l'ID de paiement
|
||||
est particulièrement utile pour lier les paiements entrant à des comptes
|
||||
utilisateurs.
|
||||
|
||||
### IDs de paiement compactes et adresses intégrées
|
||||
|
||||
Depuis la version 0.9 Hydrogen Helix, les IDs de paiement peuvent être chiffrés et incorporés dans une adresse de paiement. Les IDs de paiement de ce type devraient être de 64 octets et son chiffrés avec une clef à usage unique aléatoire connue uniquement de l'émetteur et du destinataire.
|
||||
Depuis la version 0.9 Hydrogen Helix, les IDs de paiement peuvent être
|
||||
chiffrés et incorporés dans une adresse de paiement. Les IDs de paiement de
|
||||
ce type devraient être de 64 octets et son chiffrés avec une clef à usage
|
||||
unique aléatoire connue uniquement de l'émetteur et du destinataire.
|
||||
|
||||
### Créer un ID de paiement
|
||||
Il est recommandé d'utilisé la commande `integrated_address` du portefeuille officiel pour générer automatiquement les adresses intégrées qui contiennent les IDs de paiement compacts. Si vous voulez utilisez la ligne de commande, vous pouvez générer des IDs de paiement comme suit :
|
||||
|
||||
Il est recommandé d'utilisé la commande `integrated_address` du portefeuille
|
||||
officiel pour générer automatiquement les adresses intégrées qui contiennent
|
||||
les IDs de paiement compacts. Si vous voulez utilisez la ligne de commande,
|
||||
vous pouvez générer des IDs de paiement comme suit :
|
||||
|
||||
Créer un ID de paiement compact pour une adresse intégrée :
|
||||
|
||||
|
|
|
|||
|
|
@ -1,23 +1,36 @@
|
|||
---
|
||||
summary: 'an optional flag that is added to identify transactions to merchants, consisting of 64 hexadecimal characters'
|
||||
terms: ["payment-ID", "payment-IDs"]
|
||||
summary: "an optional flag that is added to identify transactions to merchants, consisting of 64 hexadecimal characters"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
|
||||
*Note:* Long Payment IDs have been removed since release 0.15; it's not possible to use them anymore. More info in the [blog post]({{ site.baseurl_root }}/2019/06/04/Long-Payment-ID-Deprecation.html) that announced their deprecation.
|
||||
|
||||
### The Basics
|
||||
|
||||
Payment ID is an **arbitrary** and **optional** transaction attachment that consists of 32 bytes (64 hexadecimal characters) or 8 bytes (in the case of integrated addresses).
|
||||
Payment ID is an **arbitrary** and **optional** transaction attachment that
|
||||
consists of 32 bytes (64 hexadecimal characters) or 8 bytes (in the case of
|
||||
integrated addresses).
|
||||
|
||||
The Payment ID is usually used to identify transactions to merchants and exchanges: Given the intrinsic privacy features built into Monero, where a single public address is usually used for incoming transactions, the Payment ID is especially useful to tie incoming payments with user accounts.
|
||||
The Payment ID is usually used to identify transactions to merchants and
|
||||
exchanges: Given the intrinsic privacy features built into Monero, where a
|
||||
single public address is usually used for incoming transactions, the Payment
|
||||
ID is especially useful to tie incoming payments with user accounts.
|
||||
|
||||
### Compact Payment IDs and Integrated Addresses
|
||||
|
||||
Since the 0.9 Hydrogen Helix version, Payment IDs can be encrypted and embedded in a payment address. The Payment IDs of this type should be 64-bits and are encrypted with a random one-time key known only to the sender and receiver.
|
||||
Since the 0.9 Hydrogen Helix version, Payment IDs can be encrypted and
|
||||
embedded in a payment address. The Payment IDs of this type should be
|
||||
64-bits and are encrypted with a random one-time key known only to the
|
||||
sender and receiver.
|
||||
|
||||
### Creating a Payment ID
|
||||
It is recommended to use the official wallet's `integrated_address` command to automatically generate Integrated Addresses that contain Compact Payment IDs. If you want to use the command line, you can generate Payment IDs as follows:
|
||||
|
||||
It is recommended to use the official wallet's `integrated_address` command
|
||||
to automatically generate Integrated Addresses that contain Compact Payment
|
||||
IDs. If you want to use the command line, you can generate Payment IDs as
|
||||
follows:
|
||||
|
||||
Creating a compact Payment ID for an Integrated Address:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,23 +1,37 @@
|
|||
---
|
||||
summary: 'et valgfritt flagg bestående av 64 heksadesimaltegn som er lagt til for å identifisere transaksjoner til forhandlere'
|
||||
terms: ["payment-ID", "payment-IDs", "betalings-ID", "betalings-ID-er"]
|
||||
summary: "et valgfritt flagg bestående av 64 heksadesimaltegn som er lagt til for å identifisere transaksjoner til forhandlere."
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="yes" translationOutdated="no" %}
|
||||
|
||||
*Merknad:* Lange betalings-ID-er har blitt fjernet etter 0.15-utgivelsen, så det er ikke mulig å bruke dem lenger. Mer informasjon kan du finne i [blogginnlegget]({{ site.baseurl_root }}/2019/06/04/Long-Payment-ID-Deprecation.html) som kunngjorde at det ble avskrevet.
|
||||
|
||||
### Det grunnleggende
|
||||
|
||||
Betalings-ID er et **vilkårlig** og **valgfritt** transaksjonsvedlegg som består av 32 bytes (64 heksadesimaltegn) eller 8 bytes (i tilfelle ved integrerte adresser).
|
||||
Betalings-ID er et **vilkårlig** og **valgfritt** transaksjonsvedlegg som
|
||||
består av 32 bytes (64 heksadesimaltegn) eller 8 bytes (i tilfelle ved
|
||||
integrerte adresser).
|
||||
|
||||
Betalings-ID-en brukes vanligvis til å identifisere transaksjoner til forhandlere og børser: Gitt de intrinsiske personvernfunksjonene som er bygget inn i Monero, der en enkel offentlig adresse vanligvis brukes for innkommende transaksjoner, er betalings-ID-en spesielt nyttig når det kommer til å knytte innkommende betalinger med brukerkontoer.
|
||||
Betalings-ID-en brukes vanligvis til å identifisere transaksjoner til
|
||||
forhandlere og børser: Gitt de intrinsiske personvernfunksjonene som er
|
||||
bygget inn i Monero, der en enkel offentlig adresse vanligvis brukes for
|
||||
innkommende transaksjoner, er betalings-ID-en spesielt nyttig når det kommer
|
||||
til å knytte innkommende betalinger med brukerkontoer.
|
||||
|
||||
### Kompakte betalings-ID-er og integrerte adresser
|
||||
|
||||
Siden 0.9 Hydrogen Helix-versjonen, kan betalings-ID-er krypteres og bygges inn i en betalingsadresse. Betalings-ID-er av denne typen bør være 64-bits og er kryptert med en tilfeldig éngangsnøkkel som kun senderen og mottakeren kjenner til.
|
||||
Siden 0.9 Hydrogen Helix-versjonen, kan betalings-ID-er krypteres og bygges
|
||||
inn i en betalingsadresse. Betalings-ID-er av denne typen bør være 64-bits
|
||||
og er kryptert med en tilfeldig éngangsnøkkel som kun senderen og mottakeren
|
||||
kjenner til.
|
||||
|
||||
### Å opprette en betalings-ID
|
||||
Det er anbefalt å bruke den offisielle lommebokens `integrated_address`-kommando for å automatisk generere integrerte adresser som inneholder kompakte betalings-ID-er. Hvis du vil bruke kommandolinjen, kan du generere betalings-ID-er på følgende måte:
|
||||
|
||||
Det er anbefalt å bruke den offisielle lommebokens
|
||||
`integrated_address`-kommando for å automatisk generere integrerte adresser
|
||||
som inneholder kompakte betalings-ID-er. Hvis du vil bruke kommandolinjen,
|
||||
kan du generere betalings-ID-er på følgende måte:
|
||||
|
||||
Å opprette en kompakt betalings-ID for en integrert adresse:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,24 +1,36 @@
|
|||
---
|
||||
summary: 'an optional flag that is added to identify transactions to merchants, consisting of 64 hexadecimal characters'
|
||||
terms: ["payment-ID", "payment-IDs"]
|
||||
summary: "an optional flag that is added to identify transactions to merchants, consisting of 64 hexadecimal characters"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
|
||||
*Note:* Long Payment IDs have been removed since release 0.15; it's not possible to use them anymore. More info in the [blog post]({{ site.baseurl_root }}/2019/06/04/Long-Payment-ID-Deprecation.html) that announced their deprecation.
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
Payment ID is an **arbitrary** and **optional** transaction attachment that consists of 32 bytes (64 hexadecimal characters) or 8 bytes (in the case of integrated addresses).
|
||||
Payment ID is an **arbitrary** and **optional** transaction attachment that
|
||||
consists of 32 bytes (64 hexadecimal characters) or 8 bytes (in the case of
|
||||
integrated addresses).
|
||||
|
||||
The Payment ID is usually used to identify transactions to merchants and exchanges: Given the intrinsic privacy features built into Monero, where a single public address is usually used for incoming transactions, the Payment ID is especially useful to tie incoming payments with user accounts.
|
||||
The Payment ID is usually used to identify transactions to merchants and
|
||||
exchanges: Given the intrinsic privacy features built into Monero, where a
|
||||
single public address is usually used for incoming transactions, the Payment
|
||||
ID is especially useful to tie incoming payments with user accounts.
|
||||
|
||||
### Compact Payment IDs and Integrated Addresses
|
||||
|
||||
Since the 0.9 Hydrogen Helix version, Payment IDs can be encrypted and embedded in a payment address. The Payment IDs of this type should be 64-bits and are encrypted with a random one-time key known only to the sender and receiver.
|
||||
Since the 0.9 Hydrogen Helix version, Payment IDs can be encrypted and
|
||||
embedded in a payment address. The Payment IDs of this type should be
|
||||
64-bits and are encrypted with a random one-time key known only to the
|
||||
sender and receiver.
|
||||
|
||||
### Creating a Payment ID
|
||||
It is recommended to use the official wallet's `integrated_address` command to automatically generate Integrated Addresses that contain Compact Payment IDs. If you want to use the command line, you can generate Payment IDs as follows:
|
||||
|
||||
It is recommended to use the official wallet's `integrated_address` command
|
||||
to automatically generate Integrated Addresses that contain Compact Payment
|
||||
IDs. If you want to use the command line, you can generate Payment IDs as
|
||||
follows:
|
||||
|
||||
Creating a compact Payment ID for an Integrated Address:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,27 +1,44 @@
|
|||
---
|
||||
summary: 'Opcjonalny znacznik dodawany w celu identyfikacji transakcji pomiędzy użytkownikami, składający się z 64 heksadecymalnych znaków'
|
||||
terms: ["payment-ID", "payment-IDs", "numer-identyfikacyjny-płatności", "numeru-identyfikacyjnego-płatności", "numerem-identyfikacyjnym-płatności", "numerze-identyfikacyjnym-płatności", "numery-identyfikacyjne-płatności", "numerom-identyfikacyjnym-płatności", "numerach-identyfikacyjnych-płatności"]
|
||||
summary: "Opcjonalny znacznik dodawany w celu identyfikacji transakcji pomiędzy użytkownikami, składający się z 64 heksadecymalnych znaków."
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="yes" translationOutdated="yes" %}
|
||||
|
||||
*Note:* Long Payment IDs have been removed since release 0.15; it's not possible to use them anymore. More info in the [blog post]({{ site.baseurl_root }}/2019/06/04/Long-Payment-ID-Deprecation.html) that announced their deprecation.
|
||||
|
||||
### Podstawy
|
||||
|
||||
Numer identyfikacyjny płatności jest **arbitralnym** i **opcjonalnym** załącznikiem transakcji składającym się z 32 bitów (64 heksadecymalnych znaków) lub z 8 bitów (w przypadku adresów zintegrowanych).
|
||||
Numer identyfikacyjny płatności jest **arbitralnym** i **opcjonalnym**
|
||||
załącznikiem transakcji składającym się z 32 bitów (64 heksadecymalnych
|
||||
znaków) lub z 8 bitów (w przypadku adresów zintegrowanych).
|
||||
|
||||
Numer identyfikacyjny płatności jest zazwyczaj używany do identyfikacji transakcji pomiędzy użytkownikami oraz na giełdzie. Ze względu na nieodłączną charakterystykę Monero polegającą na korzystaniu z pojedynczego adresu publicznego do transakcji przychodzących, numer identyfikacyjny płatności jest szczególnie użyteczny w łączeniu płatności przychodzących z kontem użytkownika.
|
||||
Numer identyfikacyjny płatności jest zazwyczaj używany do identyfikacji
|
||||
transakcji pomiędzy użytkownikami oraz na giełdzie. Ze względu na
|
||||
nieodłączną charakterystykę Monero polegającą na korzystaniu z pojedynczego
|
||||
adresu publicznego do transakcji przychodzących, numer identyfikacyjny
|
||||
płatności jest szczególnie użyteczny w łączeniu płatności przychodzących z
|
||||
kontem użytkownika.
|
||||
|
||||
### Kompaktowy numer identyfikacyjny płatności a adresy zintegrowane
|
||||
|
||||
Począwszy od wersji 0.9 Hydrogen Helix, numery identyfikacyjne płatności mogą zostać zaszyfrowane i włączone do adresu płatności. Numery identyfikacyjne tego rodzaju powinny być 64-bitowe oraz muszą być zaszyfrowane losowym jednorazowym kluczem, znanym jedynie nadawcy i odbiorcy.
|
||||
Począwszy od wersji 0.9 Hydrogen Helix, numery identyfikacyjne płatności
|
||||
mogą zostać zaszyfrowane i włączone do adresu płatności. Numery
|
||||
identyfikacyjne tego rodzaju powinny być 64-bitowe oraz muszą być
|
||||
zaszyfrowane losowym jednorazowym kluczem, znanym jedynie nadawcy i
|
||||
odbiorcy.
|
||||
|
||||
### Tworzenie numeru identyfikacyjnego płatności
|
||||
|
||||
Zaleca się korzystanie z oficjalnej funkcji portfela `integrated_address` do automatycznego wygenerowania adresu zintegrowanego zawierającego kompaktowy numer identyfikacyjny płatności. Jeśli chcesz użyć wiersza poleceń, postępuj jak poniżej:
|
||||
Zaleca się korzystanie z oficjalnej funkcji portfela `integrated_address` do
|
||||
automatycznego wygenerowania adresu zintegrowanego zawierającego kompaktowy
|
||||
numer identyfikacyjny płatności. Jeśli chcesz użyć wiersza poleceń, postępuj
|
||||
jak poniżej:
|
||||
|
||||
Tworzenie kompaktowego numeru identyfikacyjnego dla adresu zintegrowanego:
|
||||
|
||||
```# openssl rand -hex 8```
|
||||
|
||||
Tworzenie tradycyjnego numeru identyfikacyjnego:
|
||||
|
||||
```# openssl rand -hex 32```
|
||||
|
|
|
|||
|
|
@ -1,24 +1,36 @@
|
|||
---
|
||||
summary: 'an optional flag that is added to identify transactions to merchants, consisting of 64 hexadecimal characters'
|
||||
terms: ["payment-ID", "payment-IDs"]
|
||||
summary: "an optional flag that is added to identify transactions to merchants, consisting of 64 hexadecimal characters"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
|
||||
*Note:* Long Payment IDs have been removed since release 0.15; it's not possible to use them anymore. More info in the [blog post]({{ site.baseurl_root }}/2019/06/04/Long-Payment-ID-Deprecation.html) that announced their deprecation.
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
Payment ID is an **arbitrary** and **optional** transaction attachment that consists of 32 bytes (64 hexadecimal characters) or 8 bytes (in the case of integrated addresses).
|
||||
Payment ID is an **arbitrary** and **optional** transaction attachment that
|
||||
consists of 32 bytes (64 hexadecimal characters) or 8 bytes (in the case of
|
||||
integrated addresses).
|
||||
|
||||
The Payment ID is usually used to identify transactions to merchants and exchanges: Given the intrinsic privacy features built into Monero, where a single public address is usually used for incoming transactions, the Payment ID is especially useful to tie incoming payments with user accounts.
|
||||
The Payment ID is usually used to identify transactions to merchants and
|
||||
exchanges: Given the intrinsic privacy features built into Monero, where a
|
||||
single public address is usually used for incoming transactions, the Payment
|
||||
ID is especially useful to tie incoming payments with user accounts.
|
||||
|
||||
### Compact Payment IDs and Integrated Addresses
|
||||
|
||||
Since the 0.9 Hydrogen Helix version, Payment IDs can be encrypted and embedded in a payment address. The Payment IDs of this type should be 64-bits and are encrypted with a random one-time key known only to the sender and receiver.
|
||||
Since the 0.9 Hydrogen Helix version, Payment IDs can be encrypted and
|
||||
embedded in a payment address. The Payment IDs of this type should be
|
||||
64-bits and are encrypted with a random one-time key known only to the
|
||||
sender and receiver.
|
||||
|
||||
### Creating a Payment ID
|
||||
It is recommended to use the official wallet's `integrated_address` command to automatically generate Integrated Addresses that contain Compact Payment IDs. If you want to use the command line, you can generate Payment IDs as follows:
|
||||
|
||||
It is recommended to use the official wallet's `integrated_address` command
|
||||
to automatically generate Integrated Addresses that contain Compact Payment
|
||||
IDs. If you want to use the command line, you can generate Payment IDs as
|
||||
follows:
|
||||
|
||||
Creating a compact Payment ID for an Integrated Address:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,24 +1,38 @@
|
|||
---
|
||||
summary: 'Необязательное примечание, добавляемое для идентификации транзакций продавцом и состоящая из 64 символов'
|
||||
terms: ["payment-ID", "payment-IDs", "идентификатором-платежа", "идентификатор-платежа"]
|
||||
summary: "Необязательное примечание, добавляемое для идентификации транзакций продавцом и состоящая из 64 символов"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="yes" translationOutdated="no" %}
|
||||
|
||||
*Примечание:* Длинные идентификаторы платежей (Payment ID) были удалены в релизе 0.15. Дополнительная информация содержится в [сообщении блога]({{ site.baseurl_root }}/2019/06/04/Long-Payment-ID-Deprecation.html), где подробно описаны предшествующие события для данного решения.
|
||||
|
||||
### Основная информация
|
||||
|
||||
Идентификатор платежа представляет собой **случайное** и **опциональное** приложение к транзакции размером 32 байта (64 шестнадцатеричных символа) или 8 байт (в случае с интегрированными адресами).
|
||||
Идентификатор платежа представляет собой **случайное** и **опциональное**
|
||||
приложение к транзакции размером 32 байта (64 шестнадцатеричных символа) или
|
||||
8 байт (в случае с интегрированными адресами).
|
||||
|
||||
Идентификатор платежа обычно используется для идентификации транзакции для предпринимателей или бирж. Учитывая присущие Monero свойства анонимности, как правило, предполагающие использование одного публичного адреса для входящих транзакций, идентификатор платежа является особенно полезным с точки зрения связывания входящих платежей со счетами пользователя.
|
||||
Идентификатор платежа обычно используется для идентификации транзакции для
|
||||
предпринимателей или бирж. Учитывая присущие Monero свойства анонимности,
|
||||
как правило, предполагающие использование одного публичного адреса для
|
||||
входящих транзакций, идентификатор платежа является особенно полезным с
|
||||
точки зрения связывания входящих платежей со счетами пользователя.
|
||||
|
||||
### Компактные идентификаторы платежей и интегрированные адреса
|
||||
|
||||
Начиная с версии 0.9 Hydrogen Helix, идентификаторы платежей можно шифровать и включать в адреса платежей. Идентификаторы платежей такого типа должны иметь размер 64 бита и должны быть зашифрованы при помощи случайного одноразового ключа, известного только отправителю и получателю.
|
||||
Начиная с версии 0.9 Hydrogen Helix, идентификаторы платежей можно шифровать
|
||||
и включать в адреса платежей. Идентификаторы платежей такого типа должны
|
||||
иметь размер 64 бита и должны быть зашифрованы при помощи случайного
|
||||
одноразового ключа, известного только отправителю и получателю.
|
||||
|
||||
### Создание идентификатора платежа
|
||||
|
||||
Чтобы сгенерировать интегрированные адреса, содержащие компактные идентификаторы платежей, рекомендуется использовать команду `integrated_address` официального кошелька. Если вы хотите использовать командную строку, то вы можете сгенерировать идентификаторы платежей следующим образом:
|
||||
Чтобы сгенерировать интегрированные адреса, содержащие компактные
|
||||
идентификаторы платежей, рекомендуется использовать команду
|
||||
`integrated_address` официального кошелька. Если вы хотите использовать
|
||||
командную строку, то вы можете сгенерировать идентификаторы платежей
|
||||
следующим образом:
|
||||
|
||||
Создание компактного идентификатора платежа для интегрированного адреса
|
||||
|
||||
|
|
|
|||
|
|
@ -1,23 +1,36 @@
|
|||
---
|
||||
summary: 'an optional flag that is added to identify transactions to merchants, consisting of 64 hexadecimal characters'
|
||||
terms: ["payment-ID", "payment-IDs"]
|
||||
summary: "an optional flag that is added to identify transactions to merchants, consisting of 64 hexadecimal characters"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
|
||||
*Note:* Long Payment IDs have been removed since release 0.15; it's not possible to use them anymore. More info in the [blog post]({{ site.baseurl_root }}/2019/06/04/Long-Payment-ID-Deprecation.html) that announced their deprecation.
|
||||
|
||||
### The Basics
|
||||
|
||||
Payment ID is an **arbitrary** and **optional** transaction attachment that consists of 32 bytes (64 hexadecimal characters) or 8 bytes (in the case of integrated addresses).
|
||||
Payment ID is an **arbitrary** and **optional** transaction attachment that
|
||||
consists of 32 bytes (64 hexadecimal characters) or 8 bytes (in the case of
|
||||
integrated addresses).
|
||||
|
||||
The Payment ID is usually used to identify transactions to merchants and exchanges: Given the intrinsic privacy features built into Monero, where a single public address is usually used for incoming transactions, the Payment ID is especially useful to tie incoming payments with user accounts.
|
||||
The Payment ID is usually used to identify transactions to merchants and
|
||||
exchanges: Given the intrinsic privacy features built into Monero, where a
|
||||
single public address is usually used for incoming transactions, the Payment
|
||||
ID is especially useful to tie incoming payments with user accounts.
|
||||
|
||||
### Compact Payment IDs and Integrated Addresses
|
||||
|
||||
Since the 0.9 Hydrogen Helix version, Payment IDs can be encrypted and embedded in a payment address. The Payment IDs of this type should be 64-bits and are encrypted with a random one-time key known only to the sender and receiver.
|
||||
Since the 0.9 Hydrogen Helix version, Payment IDs can be encrypted and
|
||||
embedded in a payment address. The Payment IDs of this type should be
|
||||
64-bits and are encrypted with a random one-time key known only to the
|
||||
sender and receiver.
|
||||
|
||||
### Creating a Payment ID
|
||||
It is recommended to use the official wallet's `integrated_address` command to automatically generate Integrated Addresses that contain Compact Payment IDs. If you want to use the command line, you can generate Payment IDs as follows:
|
||||
|
||||
It is recommended to use the official wallet's `integrated_address` command
|
||||
to automatically generate Integrated Addresses that contain Compact Payment
|
||||
IDs. If you want to use the command line, you can generate Payment IDs as
|
||||
follows:
|
||||
|
||||
Creating a compact Payment ID for an Integrated Address:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,9 +1,12 @@
|
|||
---
|
||||
summary: 'an optional flag that is added to identify transactions to merchants, consisting of 64 hexadecimal characters'
|
||||
terms: ["payment-ID", "payment-IDs"]
|
||||
summary: "an optional flag that is added to identify transactions to merchants, consisting of 64 hexadecimal characters"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="yes" translationOutdated="no" %}
|
||||
{% include disclaimer.html translated="yes" translationOutdated="yes" %}
|
||||
|
||||
*Note:* Long Payment IDs have been removed since release 0.15; it's not possible to use them anymore. More info in the [blog post]({{ site.baseurl_root }}/2019/06/04/Long-Payment-ID-Deprecation.html) that announced their deprecation.
|
||||
|
||||
### 基础知识
|
||||
|
||||
支付ID是一个**任意**和**可选**交易附件，包含32字节（64个十六进制字符）或8字节（在集成地址的情况下）。
|
||||
|
|
@ -12,7 +15,8 @@ summary: "an optional flag that is added to identify transactions to merchants,
|
|||
|
||||
### 紧凑的支付ID和集成地址
|
||||
|
||||
自0.9 Hydrogen Helix 版本以来，支付ID可以加密并嵌入到一个支付地址中。这种类型的支付ID应该是64位的，并且使用只有发送方和接收方知道的随机一次性密钥进行加密。
|
||||
自0.9 Hydrogen Helix
|
||||
版本以来，支付ID可以加密并嵌入到一个支付地址中。这种类型的支付ID应该是64位的，并且使用只有发送方和接收方知道的随机一次性密钥进行加密。
|
||||
|
||||
### 创建一个支付ID
|
||||
|
||||
|
|
|
|||
|
|
@ -1,23 +1,36 @@
|
|||
---
|
||||
summary: 'an optional flag that is added to identify transactions to merchants, consisting of 64 hexadecimal characters'
|
||||
terms: ["payment-ID", "payment-IDs"]
|
||||
summary: "an optional flag that is added to identify transactions to merchants, consisting of 64 hexadecimal characters"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
|
||||
*Note:* Long Payment IDs have been removed since release 0.15; it's not possible to use them anymore. More info in the [blog post]({{ site.baseurl_root }}/2019/06/04/Long-Payment-ID-Deprecation.html) that announced their deprecation.
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
Payment ID is an **arbitrary** and **optional** transaction attachment that consists of 32 bytes (64 hexadecimal characters) or 8 bytes (in the case of integrated addresses).
|
||||
Payment ID is an **arbitrary** and **optional** transaction attachment that
|
||||
consists of 32 bytes (64 hexadecimal characters) or 8 bytes (in the case of
|
||||
integrated addresses).
|
||||
|
||||
The Payment ID is usually used to identify transactions to merchants and exchanges: Given the intrinsic privacy features built into Monero, where a single public address is usually used for incoming transactions, the Payment ID is especially useful to tie incoming payments with user accounts.
|
||||
The Payment ID is usually used to identify transactions to merchants and
|
||||
exchanges: Given the intrinsic privacy features built into Monero, where a
|
||||
single public address is usually used for incoming transactions, the Payment
|
||||
ID is especially useful to tie incoming payments with user accounts.
|
||||
|
||||
### Compact Payment IDs and Integrated Addresses
|
||||
|
||||
Since the 0.9 Hydrogen Helix version, Payment IDs can be encrypted and embedded in a payment address. The Payment IDs of this type should be 64-bits and are encrypted with a random one-time key known only to the sender and receiver.
|
||||
Since the 0.9 Hydrogen Helix version, Payment IDs can be encrypted and
|
||||
embedded in a payment address. The Payment IDs of this type should be
|
||||
64-bits and are encrypted with a random one-time key known only to the
|
||||
sender and receiver.
|
||||
|
||||
### Creating a Payment ID
|
||||
It is recommended to use the official wallet's `integrated_address` command to automatically generate Integrated Addresses that contain Compact Payment IDs. If you want to use the command line, you can generate Payment IDs as follows:
|
||||
|
||||
It is recommended to use the official wallet's `integrated_address` command
|
||||
to automatically generate Integrated Addresses that contain Compact Payment
|
||||
IDs. If you want to use the command line, you can generate Payment IDs as
|
||||
follows:
|
||||
|
||||
Creating a compact Payment ID for an Integrated Address:
|
||||
|
||||
|
|
|
|||
13
po/moneropedia/paymentid.config
Normal file
13
po/moneropedia/paymentid.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/paymentid.pot $lang:../_i18n/$lang/resources/moneropedia/weblate/paymentid.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/paymentid.md $lang:../_i18n/$lang/resources/moneropedia/paymentid.md
|
||||
Loading…
Reference in a new issue