diff options
-rw-r--r-- | content/misc_docs.md | 3 | ||||
-rw-r--r-- | content/transaction_docs.md | 3 |
2 files changed, 5 insertions, 1 deletions
diff --git a/content/misc_docs.md b/content/misc_docs.md index 695119b..47b5287 100644 --- a/content/misc_docs.md +++ b/content/misc_docs.md | |||
@@ -11,3 +11,6 @@ A fingerprint is a 256 bit 64 character hexadecimal user identifier for users. F | |||
11 | 11 | ||
12 | ## Fingerprint Generation | 12 | ## Fingerprint Generation |
13 | A user's finger print is generated via applying SHA256 sum of the user's public RSA key. | 13 | A user's finger print is generated via applying SHA256 sum of the user's public RSA key. |
14 | |||
15 | # Config | ||
16 | The [/config](/config) endpoint will return the current parameters that Gradecoin uses. | ||
diff --git a/content/transaction_docs.md b/content/transaction_docs.md index f9e8947..72c1ef7 100644 --- a/content/transaction_docs.md +++ b/content/transaction_docs.md | |||
@@ -35,7 +35,8 @@ Or; without any whitespace, separated with `:` and `,`. | |||
35 | 35 | ||
36 | # Transaction Rules | 36 | # Transaction Rules |
37 | - Transactions should be sent from your account (`source`) to any other account (`target`). | 37 | - Transactions should be sent from your account (`source`) to any other account (`target`). |
38 | - No two transaction with the same `source`/`target` pair can appear on the pending transaction list [/transactions](/transaction). | ||
38 | - 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 the target. | 39 | - 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 the target. |
39 | - Don't worry if your transaction goes unaccepted! Transactions do not disappear until they are committed into the ledger with a block. | 40 | - Don't worry if your transaction goes unaccepted! Transactions do not disappear until they are committed into the ledger with a block. |
40 | - Every transaction has a unique ID generated from the `source` and `target` fields. No two transaction with the same ID can appear on the pending transaction list [/transactions](/transaction) | 41 | - Every transaction has a unique ID generated using the `source`, `target` and `timestamp` fields. |
41 | - Transactions have an upper amount limit. | 42 | - Transactions have an upper amount limit. |