aboutsummaryrefslogtreecommitdiffstats
path: root/content/transaction_docs.md
diff options
context:
space:
mode:
authorYigit Sever2022-04-23 21:54:56 +0300
committerYigit Sever2022-04-23 21:54:56 +0300
commite01cfdbc00694b92192320a1061acea5904c7523 (patch)
treec1b979db656594f8b3576e42becc33f3b26c50bb /content/transaction_docs.md
parent47f9877fa34a187e332cfa175e4aac5b7b1c8dba (diff)
downloadgradecoin-site-e01cfdbc00694b92192320a1061acea5904c7523.tar.gz
gradecoin-site-e01cfdbc00694b92192320a1061acea5904c7523.tar.bz2
gradecoin-site-e01cfdbc00694b92192320a1061acea5904c7523.zip
Config endpoint docs and new tx hash rule
Diffstat (limited to 'content/transaction_docs.md')
-rw-r--r--content/transaction_docs.md3
1 files changed, 2 insertions, 1 deletions
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.