diff options
Diffstat (limited to 'content/transaction_docs.md')
-rw-r--r-- | content/transaction_docs.md | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/content/transaction_docs.md b/content/transaction_docs.md index c521afd..3b4c2a1 100644 --- a/content/transaction_docs.md +++ b/content/transaction_docs.md | |||
@@ -40,6 +40,7 @@ Here's an example demostrating how your JSON string should look like: | |||
40 | - Transactions generate traffic which is something we desperately need in Gradecoin, so for every transaction you send, some Gradecoin will be generated out of thin air and will appear on your account. | 40 | - Transactions generate traffic which is something we desperately need in Gradecoin, so for every transaction you send, some Gradecoin will be generated out of thin air and will appear on your account. |
41 | - The amount of Gradecoin that will be generated is given by `tx_traffic_reward` field of [`/config`](/config). | 41 | - The amount of Gradecoin that will be generated is given by `tx_traffic_reward` field of [`/config`](/config). |
42 | - For example, if `tx_traffic_reward` is 1 and you send 2 coins, only 1 coin will be deduced from your account since you will be given 1 coin for generating traffic. The target will receive 2 coins. | 42 | - For example, if `tx_traffic_reward` is 1 and you send 2 coins, only 1 coin will be deduced from your account since you will be given 1 coin for generating traffic. The target will receive 2 coins. |
43 | - On the other hand, transactions have to be processed which requires valuable CPU power. So, an amount named `tx_gas_fee` of [`/config`](/config) is deducted from the user on every transaction proposal to cover the cost. | ||
43 | - Don't worry if your transaction goes unaccepted! Transactions do not disappear until they are committed into the ledger with a block. | 44 | - Don't worry if your transaction goes unaccepted! Transactions do not disappear until they are committed into the ledger with a block. |
44 | - Every transaction has a unique ID generated using the `source`, `target` and `timestamp` fields. | 45 | - Every transaction has a unique ID generated using the `source`, `target` and `timestamp` fields. |
45 | - Transactions have a lower and upper amount limit. | 46 | - Transactions have a lower and upper amount limit. |