From 55a287c311078f7531afe215dae9fbf47d0ff345 Mon Sep 17 00:00:00 2001 From: antanst Date: Sun, 3 May 2015 18:27:10 +0300 Subject: [PATCH 1/3] Add more information in the transaction moneropedia section. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The in-depth information text was taken from a fluffypony’s post in bitcointalk. --- knowledge-base/moneropedia/transaction.md | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/knowledge-base/moneropedia/transaction.md b/knowledge-base/moneropedia/transaction.md index 1f7556f9..7f159797 100644 --- a/knowledge-base/moneropedia/transaction.md +++ b/knowledge-base/moneropedia/transaction.md @@ -7,4 +7,15 @@ summary: "a cryptographically signed container that details the transfer of Mone ### The Basics -{{ page.summary | capitalize }}. \ No newline at end of file +{{ page.summary | capitalize }}. + +A transaction's inputs 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 is uniquely identified by a Transaction ID, which is usually represented as 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 the wallet is scanning for incoming transactions, every transaction is actually 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 the corresponding private view key. + +In order to spend the funds you have to compute a one-time private spend key for that output. From 070e80fbd04a76189bba9fb016286d82c42718e6 Mon Sep 17 00:00:00 2001 From: antanst Date: Sun, 3 May 2015 20:19:14 +0300 Subject: [PATCH 2/3] s/inputs/parameters to avoid confusion --- knowledge-base/moneropedia/transaction.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/knowledge-base/moneropedia/transaction.md b/knowledge-base/moneropedia/transaction.md index 7f159797..66a26e20 100644 --- a/knowledge-base/moneropedia/transaction.md +++ b/knowledge-base/moneropedia/transaction.md @@ -9,7 +9,7 @@ summary: "a cryptographically signed container that details the transfer of Mone {{ page.summary | capitalize }}. -A transaction's inputs 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. A transaction is uniquely identified by a Transaction ID, which is usually represented as a 32-byte string (64 hexadecimal characters). From 75619e82428620116ea54882c3921e3b1323f878 Mon Sep 17 00:00:00 2001 From: antanst Date: Sat, 9 May 2015 15:00:38 +0300 Subject: [PATCH 3/3] Use @ for terms --- knowledge-base/moneropedia/transaction.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/knowledge-base/moneropedia/transaction.md b/knowledge-base/moneropedia/transaction.md index 66a26e20..a958288b 100644 --- a/knowledge-base/moneropedia/transaction.md +++ b/knowledge-base/moneropedia/transaction.md @@ -14,7 +14,7 @@ A transaction's parameters are one or more recipient addresses with the correspo A transaction is uniquely identified by a Transaction ID, which is usually represented as 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. +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 the wallet is scanning for incoming transactions, every transaction is actually 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 the corresponding private view key.